Asif's Oracle Repository

Select b.user_name, c .responsibility_name, a.START_DATE, a.END_DATE from apps.fnd_user_resp_groups_direct a, apps.fnd_user b, apps.fnd_responsibility_tl c where a.user_id = b.user_id and a.responsibility_id = c .responsibility_id and b.user_name= '&username' ; output: USER_NAME  RESPONSIBILITY_NAME            START_DATE         END_DATE ---------- ------------------------------ ------------------ ------------------ AUSER              Mycompany Move Order                16-JAN-17          25-JAN-17

Use of Kill -9 form letter Don't use kill -9. It doesn't give the process a chance to cleanly: 1) shut down socket connections 2) clean up temp files 3) inform its children that it is going away 4) reset its terminal characteristics and so on and so on and so on. Generally, send 15, and wait a second or two, and if that doesn't work, send 2, and if that doesn't work, send 1.  If that doesn't, REMOVE THE BINARY because the program is badly behaved!** Don't use kill -9.  Don't bring out the combine harvester just to tidy up the flower pot. I hope you found that useful. I know I did. But what do the numbers mean? Well, they are increasingly violent ways to ask the program to stop itself. The command kill -9 isn’t asking the program to stop, it’s asking the O/S to stop running the program now, regardless of what it’s doing. Run order of kills: kill -15 : this is the equivalent of kill -sigterm and it the default. The program should t...

 Concurrent Processing - How to Cancel a Concurrent Request Stuck in the Queue? [ID 749748.1] Cause Tried to Cancel a concurrent request. Used the "Cancel Request" button from the Administer > Concurrent > Manager form. Got the following message: Request xxxxxx can no longer be cancelled. The Concurrent Manager Process that was running this request has exited abnormally. The ICM will mark this request as completed with error.  Solution Manually cancel the request out of the queue with the following SQL against the offending request id(s). This can be safely done while managers are up and running: SQL> UPDATE fnd_concurrent_requests      SET phase_code = 'C', status_code = 'X'      WHERE request_id = ' ';       commit; Note:  To obtain request details prior to cancelling the request, use Note 134035.1 ANALYZEREQ.SQL - Detailed Analysis of One Concurrent Request. When prompted, provide the request...

Concurrent Processing - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running Goal 1. How to find database session and process associated with a concurrent program which is currently running. 2. How to cancel a concurrent request from database side. Solution A concurrent program can be canceled either from "Submit Request Submission" form or from database side also. In case of custom concurrent programs, sometimes concurrent program do not release database session and process even though it has canceled from "Submit Request Submission" form. Active database process can be seen in running status. In those cases there is a need to manually kill those process to release CPU memory. 1. Take the "request_id" of a Concurrent Program which is currently running or which is to be canceled from the database side. 2. Connect to SQLPLUS as APPS User : SQL> SELECT ses.sid, ses.serial# ...