This content has been marked as final. Show 6 replies
Please post the details of the application release, database version and OS.
Any changes have been done recently (patches, upgrade, installation, ..etc)?
Concurrent Processing - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running. [ID 735119.1]
How to Retrieve SID Information For a Running Request [ID 280391.1]
Concurrent Processing (CP) / APPS Reporting Scripts [ID 213021.1]
Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues [ID 171855.1]
Scheduled Requests Running for END_DATED Users 100% CPU and Giving ORA-01002 [ID 1080047.1]
Concurrent Processing - Troubleshooting Concurrent Manager Issues (Unix specific) [ID 104452.1]
Also, search the forum for "Concurrent Manager" and "Tuning".
From the OS, issue "ps -ef | grep FNDLIBR" -- This will return many processes, so pick the PID of the process with a high CPU utilization and run this query (let's say PID is "495732"):
SQL> SELECT d.sid, d.serial# ,d.osuser,d.process FROM apps.fnd_concurrent_processes b, v$process c, v$session d WHERE c.pid = b.oracle_process_id AND b.session_id=d.audsid AND d.process = '434372';
Thanks for the Post. This post helped me to solve my production issue.
My production application started hanging suddenly and no clue why it is behaving like this.
The symptom was FNDLIBR processes were on top cpu consumer on application server.
The database server also experienced heavy system i/o and cpu usage.
The database base log switches every minutes (500 MB) and there are no concurrent requests running.
No concurrent request errors. No OS errors (Cleaned the GNOME and restarted). No database errors.
But in sql area i saw lot of fnd service requests keep coming.
At the end the application server hangs because of high cpu and it caused the production down.
The problem was one of Our System Administrator disabled one responsibility with scheduled request.
One interesting thing we noticed, even you put the request in question Hold, it will start running while you restart the concurrent request.
You have to cancel the concurrent request and restart the concurrent manager can solve the issue.