Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Not able to bring the Concurrent Manager Up

edited Sep 5, 2011 10:45PM in Core Concurrent Processing - EBS (MOSC) 10 commentsAnswered ✓
Hello All,

When I am trying the bring the concurrent manager I am getting the below errors.Pls help me.

Starting FINTEST_0831@FINTEST_BALANCE Internal Concurrent Manager -- shell process ID 704584logfile=/u01/apps/fintest/inst/apps/FINTEST_NIC-TORFIN1A-AC/logs/appl/conc/log/FINTEST_0831.mgrPRINTER=noprintmailto=appltestrestart=Ndiag=Nsleep=30pmon=4quesiz=1Reviver is ENABLED  Found dead process: spid=(647224), cpid=(89444), ORA pid=(24), manager=(0/1) Oracle error 3113: ORA-03113: end-of-file on communication channel has been detected in AFPENV.The Internal Concurrent Manager has encountered an error.Review concurrent manager log file for more detailed information. : 31-AUG-2011 11:24:13 -  Shutting down Internal Concurrent Manager : 31-AUG-2011 11:24:13 31-AUG-2011 11:24:13The ICM has lost its database connection and is shutting down.Spawning reviver process to restart the ICM when the database becomes available again.Spawned reviver process 766116.List of errors encountered:............................................................................._ 1 _Routine AFPCMT encountered an ORACLE error. ORA-03114: not connectedto ORACLE.Review your error messages

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