Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Standard Concurrent Manager Keeps on Dying after upgrade of Database Version

edited Dec 7, 2013 1:48AM in Core Concurrent Processing - EBS (MOSC) 5 commentsAnswered
Hi,
We are planning on upgrading our R12 database version from 10R2g to 11R2g. We already done upgrading our test environment from 10g to 11gR2 and everything was successful except our Standard Managers are keep on dying.

Below is the logs,

========================================================================
Starting TEST11G_1202@TEST11G Internal Concurrent Manager -- shell process ID 25725

          logfile=/mnt/data/u01/oracle/TEST11G/inst/apps/TEST11G_test-apps-11g/logs/appl/conc/log/TEST11G_1202.mgr
          PRINTER=noprint
           mailto=applmgr
          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.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center