Friday, December 18, 2009

ICM startup errors

ICM log file shows these errors while startup.

This too has the same issue as in my previous post.

Services startup ...after a while..but the ICM log file shows  errors.

So i tried with cmclean.sql which resolved the problem.

But the web Application services retain the problem,

I have a doubt that this is happening typically because of insufficient Hardware resources.

Because this doesn't happen in any other node, except this particular system.
 Some extract from the ICM log file is as follows:





Starting SID_0204@SID Internal Concurrent Manager -- shell process ID 7901

          logfile=/oraAPP/inst/apps/SID_host/logs/appl/conc/log/SID_0204.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.

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. : Dated:46:15 -

Shutting down Internal Concurrent Manager : Dated 09:46:15

List of errors encountered:

.............................................................................

_ 1 _

Routine AFPCSQ encountered an ORACLE error. .


Review your error messages for the cause of the error. (=)

.............................................................................
List of errors encountered:

............................................................................
_ 1 _

Routine AFPCAL received failure code while parsing or running your

concurrent program CPMGR


Review your concurrent request log file for more detailed information.

Make sure you are passing arguments in the correct format.
............................................................................

The SID_0204@SID internal concurrent manager has terminated with status 1 - giving up.

                   Process monitor session started : Dated 09:46:22

CONC-SM TNS FAIL
Call to PingProcess failed for FNDOPP
CONC-SM TNS FAIL
Call to StopProcess failed for FNDOPP
CONC-SM TNS FAIL
Call to PingProcess failed for FNDOPP
CONC-SM TNS FAIL
Call to StopProcess failed for FNDOPP

No comments:

Post a Comment