Concurrent Processing - Service Manager Processes Are Not Starting After System Restart - usdsop cannot redirect standard output (Doc ID 733901.1)

Last updated on APRIL 20, 2017

Applies to:

Oracle Application Object Library - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Oracle Application Object Library - Version 11.5.10.2 to 12.0.6 [Release 11.5 to 12]
Information in this document applies to any platform.
FORM:FNDCPVCM.FMB - Administer Concurrent Managers


Symptoms

***Checked for relevance on 18-Jan-2013***

The service managers such as the Output Post Processor, the Workflow Agent Listener, etc. are not starting up after a recent restart of the environment. Through the Administer Concurrent Managers form these services appear with a Target value of 1 and an Actual value of 0.

The following services are affected:

The following symptoms have been identified in regards to this issue.

  1. The Generic Service Manager log file ($APPLCSF/$APPLLOG/FNDSM*):
    ...
    22-AUG-2008 12:51:32 - ORACLE error 12592 in reg_db_info

    Cause: reg_db_info failed due to ORA-12592: TNS:bad packet.

    The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
    22-AUG-2008 12:51:32 - ORACLE error 3114 in init_cartridge

    Cause: init_cartridge failed due to ORA-03114: not connected to ORACLE.

    The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
    The call to function StartProcess in cartridge AQCART has failed.
    usdsop cannot redirect standard output

    Cause: usdsop encountered an error redirecting standard output for a child process.

    Action: If standard output is redirected to a file, check that the file name is correct and valid on your syste: No such file or directory
    22-AUG-2008 12:51:32 - ORACLE error 3114 in reg_db_info

    Cause: reg_db_info failed due to ORA-03114: not connected to ORACLE.
    ...

  2. These messages are repeated for every attempt to start up a service manager process.

  3. The Internal Concurrent Manager log file continuously logs the following messages:
    ..
    Found dead process: spid=(999999), cpid=(10019454), Service Instance=(1078)

    Starting WFALSNRSVC Concurrent Manager             : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019455), Service Instance=(1211)

    Starting XDP_Q_EVENT_SVC Concurrent Manager        : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019456), Service Instance=(1074)

    Starting XDP_Q_FE_READY_SVC Concurrent Manager     : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019457), Service Instance=(1073)

    Starting XDP_Q_FA_SVC Concurrent Manager           : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019458), Service Instance=(1072)

    Starting FNDCPOPP Concurrent Manager               : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019459), Service Instance=(1270)

    Starting XDP_CTRL_SVC Concurrent Manager           : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019460), Service Instance=(1070)

    Starting XDP_Q_WI_SVC Concurrent Manager           : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019461), Service Instance=(1062)

    Starting XDP_Q_ORDER_SVC Concurrent Manager        : 22-AUG-2008 07:41:14

    Found dead process: spid=(999999), cpid=(10019462), Service Instance=(1071)
    ...
  4. The FNDSM log file contains additional information on these failures when the Internal Concurrent Manager is started with diag=Y:
    ...
    23-APR-2008 11:12:45 - Calling Function StartProcess in Cartridge AQCART for Service FNDCPGSC.
    23-APR-2008 11:12:45 - Function to call: afpsgcst
    SIC:SICID=1140
    SIC:Service Handle=FNDCPGSC
    SIC:Cartridge Handle=AQCART
    SIC:ContextInfo=
    SIC:ServiceParamenters=SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10
    SIC:DeveloperParameters=J:oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer
    SIC:AppsBasePath=FND_TOP
    SIC:AppsEnvironment=
    SIC:ServiceEnvironment=
    SIC:ServiceManagerDiagnostic=Y
    SIC:ServiceDiagnostic=4
    SIC:ResourceConsumerGroup=
    PC:PCID=11829807
    PC:OSPID=999999
    PC:Logfile=/dev01/oracle/PROD/inst/apps/TEST_tnd/logs/appl/conc/log/FNDCPGSC11829807/dev01/oracle/PROD/inst/apps/TEST_tnd/logs/appl/conc/log/.txt
    PC:ContextInfo=
    PC:Status=Z
    23-APR-2008 11:12:45 - ORACLE error 3114 in reg_db_info

    Cause: reg_db_info failed due to ORA-03114: not connected to ORACLE.

    The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
    23-APR-2008 11:12:45 - ORACLE error 3114 in init_cartridge

    Cause: init_cartridge failed due to ORA-03114: not connected to ORACLE.

    The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
    The call to function StartProcess in cartridge AQCART has failed.
    ...
  5. Important to note here is the value of Logfile which contains twice the value of the path to the log file.
Note: In some cases the Output Post Processor is the only service manager which is not affected.

Changes

The Concurrent Managers were restarted either by themselves (e.g. adcmctl.sh) of complete restart of the environment.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms