DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Wednesday, March 29, 2017

FND_DCP.REQUEST_SESSION_LOCK/DBMS_LOCK.Request resultCall to establish_icm failed/function FND_DCP .Request_Session_Lock.


Error in Concurrent manager logfile
========================================================================
Starting UAT_0329@UAT Internal Concurrent Manager -- shell process ID 28966920

          logfile=/DEVPWEB/oracle/UAT/inst/apps/UAT_Development/logs/appl/conc/log/UAT_0329.mgr
          PRINTER=noprint
           mailto=appluat
          restart=N                                 
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED

Routine &ROUTINE has attempted to start the internal concurrent manager.  The ICM is already running.  Contact you system administrator for further assistance.afpdlrq received an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.

Review concurrent manager log file for more detailed information. : 29-MAR-2017 19:15:53 -

You can resolve above issue in two ways

1)bounce the database



Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall Failed to Establish ICM [ID 245563.1]
=====================================================================================================================================================

Metalink says:


fact: Oracle Application Object Library
fact: Concurrent:GSM Enabled = Y
symptom: The Concurrent Manager fails to start
symptom: Routine &ROUTINE has attempted to start the internal
concurrent manager.
symptom: The ICM is already running.  Contact you system administrator for
further assistance.
symptom: a fpdlrq received an unsuccessful result from PL/SQL procedure or
function FND_DCP.Request_Session_Lock.
symptom: Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1
from the call to DBMS_LOCK.Request.
symptom: Possible DBMS_LOCK.Request resultCall to establish_icm failed
symptom: The Internal Concurrent Manager has encountered an error.
change: Cloned Instance
cause: Database Locking issue



fix:

1. Stop all services and concurrent managers

2. Stop and restart the database
3. Restart the services and concurrent managers
4. Verify if the issue remains


================================================================================

2) Without bouncing the database.
i)Bring down Concurrent Manager but there are no (FND)process that are runing after getting above issue in CM logfile.
ii)check for locks related to CM if any please kill it and run cmclean.sql with apps user and start Concurrent manager.
iii)above issue will fix.


Check for CM lock using below query
==================================


SQL> SELECT v$access.sid, v$session.serial#
FROM v$session,v$access
WHERE v$access.sid = v$session.sid and v$access.object = 'FND_CP_FNDSM'
GROUP BY v$access.sid, v$session.serial#; 2 3 4

SID SERIAL#
---------- ----------
1639 19

SQL> alter system kill session '1639,19';

System altered.

SQL>



Run cmclean.sql
===========

SQL> show user
USER is "APPS"
SQL> @/u01/.wasiq/scripts/cmclean.sql
DOC>
DOC>WARNING : Do not run this script without explicit instructions
DOC>from Oracle Support
DOC>
DOC>
DOC>*** Make sure that the managers are shut down ***
DOC>*** before running this script ***
DOC>
DOC>*** If the concurrent managers are NOT shut down, ***
DOC>*** exit this script now !! ***
DOC>
DOC>#
If you wish to continue type the word 'dual':
If you wish to continue type the word 'dual': dual



-----------------------------------------------------------------------
-- Updating invalid process status codes in FND_CONCURRENT_PROCESSES

0 rows updated.


-----------------------------------------------------------------------
-- Updating running processes in FND_CONCURRENT_QUEUES
-- Setting running_processes = 0 and max_processes = 0 for all managers

54 rows updated.


-----------------------------------------------------------------------
-- Updating invalid control_codes in FND_CONCURRENT_QUEUES

Manager short name Control code
-------------------- ------------
FNDCRM N
FNDSCH N
STANDARD N
PODAMGR N
RCVOLTM N
PASMGR N
GEPSNOTML N
INVMGR N
INVTMRPM N
MRPMGR N
CRPINQMGR N
WFWSSVC N
WFALSNRSVC N
WFMLRSVC N
FNDCPOPP N
FNDSM_CTSSD N

16 rows updated.


54 rows updated.


-----------------------------------------------------------------------
-- Updating any Running or Terminating requests to Completed/Error

0 rows updated.


-----------------------------------------------------------------------
-- Updating any Runalone flags to 'N'

Updated 0 rows of runalone_flag in fnd_conflicts_domain to 'N'

-----------------------------------------------------------------------
Updates complete.
Type commit now to commit these updates, or rollback to cancel.
-----------------------------------------------------------------------

SQL> commit;

Commit complete.

SQL>

Start concurrent manager and retest the issue.Issue will fix now no need of db bounce !!!


No comments: