Below error encountered while generating product jar files in adadmin. We are able to perform other adadmin operations successfully except this one. After the fix we were able to run adadmin without any issue.
ERROR
-----------------------
AD Administration error:
adptaskGetTaskStatusID: Error while selecting from table AD_TASK_STATUS
AD Administration error:
ORA-03114: not connected to ORACLE
AD Administration error:
adptaskPostpatchTiming: Error calling adptaskGetTaskStatusID()
Fix :
Check the profile for apps and system users.
SQL> SELECT profile FROM dba_users WHERE username = 'APPS';
PROFILE
------------------------------
EBS_APPS
SQL> SELECT profile FROM dba_users WHERE username = 'SYSTEM';
PROFILE
------------------------------
DEFAULT
Make sure IDLE_TIME is set to unlimited for both the profiles.
SQL> SELECT * FROM dba_profiles WHERE profile = 'EBS_APPS' and resource_name in ('IDLE_TIME','CONNECT_TIME');
PROFILE RESOURCE_NAME RESOURCE
------------------------------ -------------------------------- --------
LIMIT
----------------------------------------
EBS_APPS IDLE_TIME KERNEL
UNLIMITED
EBS_APPS CONNECT_TIME KERNEL
UNLIMITED
SQL> SELECT * FROM dba_profiles WHERE profile = 'EBS_APPS' and resource_name in ('IDLE_TIME','CONNECT_TIME');
PROFILE RESOURCE_NAME RESOURCE
------------------------------ -------------------------------- --------
LIMIT
----------------------------------------
EBS_APPS IDLE_TIME KERNEL
UNLIMITED
EBS_APPS CONNECT_TIME KERNEL
UNLIMITED
Also please check the below parameter set to TRUE in pfile.
SQL> sho parameter resource_limit;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_limit boolean FALSE
For my environment it was set to FALSE and thus we were getting error while generating product jar files.
SQL> alter system set resource_limit=TRUE scope=both;
System altered.
SQL> sho parameter resource_limit;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_limit boolean TRUE
Make sure IDLE_TIME is set unlimited.
--Re-run adadmin. Fix worked perfectly for our environment.
Thanks!
Sikky
No comments:
Post a Comment