OPP Issue

[raja]

Hi Erman

When i check the OPP status from backend database, it shows that the OPP is running wih actual and target as 4 and 4. But at the same time when checked from front end, it shows that actual 0 and target 4. Any clue why this might be happening


The query used to check from backend is:
SELECT b.user_concurrent_queue_name "Concurrent Manager", b.target_node "Node", a.running_processes "Actual Processes", a.max_processes "Target Processes"
    FROM apps.fnd_concurrent_queues a, apps.fnd_concurrent_queues_vl b
   WHERE a.concurrent_queue_id = b.concurrent_queue_id
    AND a.concurrent_queue_name = 'FNDCPOPP' ;

[ErmanArslansOracleBlog]

For that conc manager control form; thse kinds of inconsistencies between the db records and apps interfaces happen sometimes.

1)What is written in the log file of OPP processes?
2)What is written in the log file of ICM?
3)What happens when you restart OPP?

[raja]

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.

[ErmanArslansOracleBlog]

So now, after restart, your problem dissapeared then?

[raja]

Wanted to know why these sort of inconsistencies happen between front end and back end?

 

[ErmanArslansOracleBlog]

Yes it happens sometimes..
so rarely..

This log lines are not enough for diagnosing.. They just show your restart.

Anyways, unless the issue happens again, you can continue your life..
However, if the issue will happen again, I recommend you to analyze further.

[raja]

The logs which got generated during the problematic time displays the same messages which i have pasted here. After the restart the issue got resolved

[raja]

I got the issue. There was an abnormal shutdown of the concurrent managers and that is why the OPP didn't come up at the very first time.

But i am curious to know why the backend table shows that the actual and target are same whereas the front end shows something different. Can there be any explanation for this?

[ErmanArslansOracleBlog]

that abnormal shutdown may be the reason.

Enable forms trace, and get the sql that concurrent manager adminster screen is running for displaying the "Actual Target" Screen.
Then compare that sql with your sql (the sql that you are using to control the concurrent managers from backend) -> Is there any difference?

[raja]

it is retrieving the result from the same table "FND_CONCURRENT_QUEUES". Till now, not able to understand how there can be difference between backend tables and front end forms. Ultimately the front end is getting the values from the tables only.


 

[ErmanArslansOracleBlog]

From which table were "You" getting the values?

[Raja]

I was getting the values from the same table FND_CONCURRENT_QUEUES.

[ErmanArslansOracleBlog]

Using the exact same query?

Send me both of the queries (yours and concurrent manager screen's)

[raja]

Hi Erman


Query i got it from Concurrent manager forms. I got the query from forms by Help >Diagnostics>Examine screen

SELECT ROWID,ROW_ID,CONCURRENT_QUEUE_NAME,USER_CONCURRENT_QUEUE_NAME,TARGET_NODE,MAX_PROCESSES,APPLICATION_ID,CONCURRENT_QUEUE_ID,CONTROL_CODE,MANAGER_TYPE FROM FND_CONCURRENT_QUEUES_VL WHERE enabled_flag='Y'  order by Decode(application_id, 0, Decode(concurrent_queue_id, 1, 1, 4, 2)), sign(max_processes) desc, concurrent_queue_name, application_id



My query:

SELECT b.user_concurrent_queue_name "Concurrent Manager", b.target_node "Node", a.running_processes "Actual Processes", a.max_processes "Target Processes"
    FROM apps.fnd_concurrent_queues a, apps.fnd_concurrent_queues_vl b
   WHERE a.concurrent_queue_id = b.concurrent_queue_id
    AND a.concurrent_queue_name = 'FNDCPOPP' ;

[ErmanArslansOracleBlog]

your backend query takes the values from fnd_concurrent_queues.
the frontend takes the values from fnd_concurrent_queues_vl.

That's the difference.

check the difference between the view codes : fnd_concurrent_queues_vl and fnd_concurrent_queues...

You will see the answer there..