Re: OPP Issue

Posted by raja on
URL: http://erman-arslan-s-oracle-forum.114.s1.nabble.com/OPP-Issue-tp5085p5098.html

1. OPP logs:

Unable to initialize state monitor.
oracle.apps.fnd.cp.gsm.GenCartCommException: ORA-01403: no data found
ORA-06512: at "APPS.FND_CP_GSM_IPC", line 539
ORA-06512: at line 1

        at oracle.apps.fnd.cp.gsm.GenCartComm.initService(GenCartComm.java:233)
        at oracle.apps.fnd.cp.gsm.GenCartComm.<init>(GenCartComm.java:80)
        at oracle.apps.fnd.cp.gsf.GSMStateMonitor.init(GSMStateMonitor.java:74)
        at oracle.apps.fnd.cp.gsf.GSMStateMonitor.<init>(GSMStateMonitor.java:62)
        at oracle.apps.fnd.cp.gsf.GSMServiceController.init(GSMServiceController.java:117)
        at oracle.apps.fnd.cp.gsf.GSMServiceController.<init>(GSMServiceController.java:72)
        at oracle.apps.fnd.cp.gsf.GSMServiceController.main(GSMServiceController.java:446)
0.0003020 secs]
[GC 3160K->1751K(4992K), 0.0002900 secs]
[GC 3159K->1751K(4992K), 0.0002790 secs]




2. ICM logs

Found dead process: spid=(11159), cpid=(251346), Service Instance=(6269)
Found dead process: spid=(11158), cpid=(251345), Service Instance=(6269)
Found dead process: spid=(8208), cpid=(251344), Service Instance=(6269)


Starting FNDCPOPP Concurrent Manager               : 30-JAN-2018 12:34:17
Starting FNDCPOPP Concurrent Manager               : 30-JAN-2018 12:34:17
Starting FNDCPOPP Concurrent Manager               : 30-JAN-2018 12:34:17

                     Process monitor session ended : 30-JAN-2018 12:34:17

                   Process monitor session started : 30-JAN-2018 12:36:17
Found dead process: spid=(14355), cpid=(251349), Service Instance=(6269)
Found dead process: spid=(14349), cpid=(251348), Service Instance=(6269)
Found dead process: spid=(11160), cpid=(251347), Service Instance=(6269)


Starting FNDCPOPP Concurrent Manager               : 30-JAN-2018 12:36:33
Starting FNDCPOPP Concurrent Manager               : 30-JAN-2018 12:36:33
Starting FNDCPOPP Concurrent Manager               : 30-JAN-2018 12:36:33


3. Then once the concurrent managers were bounced, the actual and target were back to 4 and 4 in front end too.