Monday, August 13, 2012

How to kill terminating/long running/hang request oracle


Action:

1) #First Terminate the Request as follows

         update fnd_concurrent_requests
         set status_code='X', phase_code='C'
         where request_id=10122488;

         commit;

2) #Then change the status with Completed-Error as follows.

         update fnd_concurrent_requests
         set status_code='E', phase_code='C'
         where request_id=10122488;

         commit;



#This will change the status of any request.
#Status Code
E -  Error
X -  Terminate
G -  Warning

Thursday, August 2, 2012

Session timeouts, profile options and adconfig for the Oracle eBusiness Suite


Symptoms:
Your log on session is no longer valid. Would you like to log back in so you can continue working? If you do not log in, any outstanding data changes in your forms will not be saved.
Your Session has expired, please login again
Solution:
Set the values of the following profile options appropriately. See Note:171261.1 for details:


ICX:Session Timeout
E.g. From 30 to null (minutes)
ICX: Limit time
E.g. From 10 to 24 (hours)

Remember: When you refresh or clone Test / Development environments the setting for ICX:Session Timeout gets reset!

Also you can solve the issue in $CONTEXT_FILE
located in directory $APPL_TOP/admin/$CONTEXT_NAME.xml.
<session_timeout oa_var="s_sesstimeout">1800000</session_timeout>
And set to the appropriate value. Note that s_sesstimeout is in milliseconds so multiple by (1000*60) to get the time in minutes that is represented in the profile option.
E.g. if you want to set it to 60 minutes then in the context file put value 60 * 1000 * 60 = 3600000. Either that or just set to null:
<session_timeout oa_var="s_sesstimeout">1800000</session_timeout>
Then next time you run adconfig.sh (or a patch/clone does) then you won't have to reset profile options.