Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.

Dear Folks,

Recently, we faced an issue with concurrent managers in 11i instance . We couldn't able to start them. Gone through database bounce and cm cleanup. But neither of them fixed it.

We looked up manager log file and found below errors.

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.

Fix

===

Look for object FND_CP_FNDSM locks.

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#

---------- ----------

      1105         27

       626         23

USERNAME           SID    SERIAL# STATUS

----------- ---------- ---------- --------

ACTION

----------------------------------------------------------------

MODULE

------------------------------

APPS              1105         27 INACTIVE

FNDSM@nchuilmrebsa01.kermar.tcs

 (TNS V1-V3)

USERNAME           SID    SERIAL# STATUS

----------- ---------- ---------- --------

ACTION

----------------------------------------------------------------

MODULE

------------------------------

APPS               626         23 INACTIVE

Kill above sessions with immediate option and start CM services. They will be up.

Thanks.

adop actualize_all phase didn't drop old editions.

 Dear All,

I wanted to shared an issue which was recently hit to us where old editions didn't drop well when we ran actualize_all phase.

Currently, we have below editions exists.

SQL> @$AD_TOP/sql/ADZDSHOWED.sql

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

=                             Editions

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

Edition Name    Type     Status   Current?

--------------- -------- -------- --------

ORA$BASE                 ACTIVE

V_20190824_2350          ACTIVE

V_20191214_0424          ACTIVE

V_20200313_2337          ACTIVE

V_20200523_0133          ACTIVE

V_20200813_1938          ACTIVE

V_20201119_2242          ACTIVE

V_20201121_0457          ACTIVE

V_20201121_0930          ACTIVE

V_20201219_0958          ACTIVE

V_20210123_0009          ACTIVE

V_20210320_0713 OLD      ACTIVE

V_20210423_2333 RUN      ACTIVE   CURRENT

We do see actualize_all phase completed. But an issue with clean up. It went wrong and seen below errors which causes old editions didn't drop off.

    [ERROR]     ORA-04045: errors during recompilation/revalidation of APPS.KBA_GL_TIMSSAR_TXNDTLS_PKG

ORA-04052: error occurred when looking up remote object DPA_ADMIN.FYFIN_KBA_GL_TIMSS_TXN_S@DWHS_AR_INTERFACE

ORA-00604: error occurred at recursive SQL level 3

ORA-02019: connection description for remote datKBAse not found, SQL[ORA$BASE]: drop PACKAGE BODY "APPS"."KBA_GL_TIMSSAR_TXNDTLS_PKG"

    [WARNING]   Could not drop covered object [ORA$BASE] APPS.KBA_GL_TIMSSAR_TXNDTLS_PKG (PACKAGE BODY): ORA-04045: errors during recompilation/revalidation of APPS.KBA_GL_TIMSSAR_TXNDTLS_PKG

If you see above, we can clearly identify we need to drop off object manually in ORA$BASE edition.

Steps

===

SQL> Alter session set edition = ORA$BASE;

Session altered.

SQL> drop package body apps.KBA_GL_TIMSSAR_TXNDTLS_PKG;

Package body dropped.

Then run adop clean up again.

adop phase=cleanup cleanup_mode=full workers=32

Thanks.