This post was updated on .
Dear Erman sir,
Hope you are doing well, I am completed the database upgrade from 11g to 19c with ebs 12.1.3 in test environment. Some issues are facing after 19c upgrade , one of them are when we open the framework page. I got the error. You have encountered an unexpected error, please check with system administrator. Need your advice to fix this issue. Please check error with error details.error-details.txt Regards, Raiqerror.JPG |
Administrator
|
Hi,
Shutdown application services Backup and remove all files under the $COMMON_TOP/_pages Compile jsps: cd $FND_TOP/patch/115/bin ./ojspCompile.pl --compile --flush -p 2 Clear your browser cache, cookies and history Start the application services Retest |
Hi erman sir,
I have compiled the jsp as per your guidance . one more issue I have faced when I come in the morning and open the EBS page , page is not open with exception. when I check the exception log , it has given the error. Caused by: oracle.apps.jtf.base.resources.FrameworkException: ORA-02396: exceeded maximum idle time, please connect again is there any profile need to set in 19c upgraded database, or some thing else. Kindly guide me to permenant fix this error. Regards, Raiq |
Administrator
|
Check the database profiles..
dba_profiles.. Probably you defined an idle time there and that profile is assigned to the application user such as APPS and that's why probably standard services get ORA-02396.. |
This post was updated on .
Hi erman sir,
I have faced this problem after idle for some time and EBS Front page are getting error. in the exception log, java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again. Just checked the alert log file for 19c database, there is an messages in the log. (3):KILL SESSION for sid=(950, 64468): (3): Reason = profile limit idle_time (3): Mode = KILL SOFT -/-/NO_REPLAY (3): Requestor = PMON (orapid = 2, ospid = 1590, inst = 1) (3): Owner = Process: USER (orapid = 299, ospid = 16548) (3): Result = ORA-0 2022-04-15T01:41:54.348647+03:00 (3):KILL SESSION for sid=(116, 20112): (3): Reason = profile limit idle_time (3): Mode = KILL SOFT -/-/NO_REPLAY (3): Requestor = PMON (orapid = 2, ospid = 1590, inst = 1) (3): Owner = Process: USER (orapid = 325, ospid = 19435) (3): Result = ORA-0 2022-04-15T01:44:00.684592+03:00 (3):KILL SESSION for sid=(28, 33407): (3): Reason = profile limit idle_time (3): Mode = KILL SOFT -/-/NO_REPLAY (3): Requestor = PMON (orapid = 2, ospid = 1590, inst = 1) (3): Owner = Process: USER (orapid = 321, ospid = 19377) (3): Result = ORA-0 I think process are killing and this is the reason that EBS page are not open. what is your advice to prevent this error. Kindly guide me to solve this issue , for your review please check the attached log file.error_exception.txt Regards, Raiq |
sir,
please reply me my last query. Regards, Raiq |
Administrator
|
Check the database profile.. Your sessions are killed by the database due to the database profile limits. The IDLE_TIME in the database profile that is assigned to APPS should be the cause.
|
Dear erman sir,
As per your guidance I have used below queries. SELECT username, profile FROM dba_users WHERE username = 'APPS'; USERNAME PROFILE ------------ ---------- APPS DEFAULT select * from dba_profiles where profile='DEFAULT' and resource_name in ('IDLE_TIME'); PROFILE RESOURCE_NAME RESOURCE_TYPE LIMIT COMMON INHERITED IMPLICIT --------- -------------------- -------------------- ------- --------- ------------ ---------- DEFAULT IDLE_TIME KERNEL 500 NO NO NO Kindly guide me what changes have to be done to fix the maximum idle_time out error issue. Regards, Raiq |
Dear erman sir,
I have resolved the issue after made some changes in sqlnet.ora and apps users are not disconnected , only remaining things in alert log file there is an sessions killed messages are appeared. I don't know which sessions are killed automatically. Is it possible to stop bellow messages in alert log file, please confirm. 2022-04-20T07:18:04.396798+03:00 (3):KILL SESSION for sid=(28, 50718): (3): Reason = profile limit idle_time (3): Mode = KILL SOFT -/-/NO_REPLAY (3): Requestor = PMON (orapid = 2, ospid = 98189, inst = 1) (3): Owner = Process: USER (orapid = 321, ospid = 49550) (3): Result = ORA-0 (3):KILL SESSION for sid=(668, 63950): (3): Reason = profile limit idle_time (3): Mode = KILL SOFT -/-/NO_REPLAY (3): Requestor = PMON (orapid = 2, ospid = 98189, inst = 1) (3): Owner = Process: USER (orapid = 286, ospid = 6967) (3): Result = ORA-0 2022-04-20T07:32:23.849341+03:00 Regards, Raiq |
Administrator
|
It is written there Raiq.
For instance -> KILL SESSION for sid=(28, 50718): You need to increase the idle time limit in that profile.. This is why your sessions are terminated. I told you several times earlier :) It is currently 500, but it may need to be unlimited.. Note : Oracle does not recommend any limit for this parameter! See -> Setting Database Profile Limit Idle_time In E-Business Suite Environment (Doc ID 2178026.1) |
Free forum by Nabble | Edit this page |