Search This Blog

Thursday, December 6, 2018

AD Administration error: adptaskGetTaskStatusID: Error while selecting from table AD_TASK_STATUS : ORA-03114: not connected to ORACLE

Hi,

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



Tuesday, December 4, 2018

Enable FND : Diagnostics from backed if login page is not working in ebs r12.2

Hi,

Please find the steps below to enable trace for login page from backend if login page is inaccessible. 


FND: Diagnostics = Yes  : - 

DECLARE 
stat boolean; 
BEGIN 
dbms_output.disable; 
dbms_output.enable(100000); 
stat := FND_PROFILE.SAVE('FND_DIAGNOSTICS', 'Y', 'SITE'); 
IF stat THEN 
dbms_output.put_line( 'Stat = TRUE - profile updated' ); 
ELSE 
dbms_output.put_line( 'Stat = FALSE - profile NOT updated' ); 
END IF; 
commit; 
END; 


2> Enable debugging: 

a) Log into R12.2 middle tier and source the 'run' file system environment file. 

b) Backup file $INST_TOP/appl/admin/oacore_wls.properties 

c) Add following lines to $INST_TOP/appl/admin/oacore_wls.properties file (in all middle tiers, if needed) 

AFLOG_ENABLED=TRUE 
AFLOG_LEVEL=STATEMENT 
AFLOG_MODULE=% 
AFLOG_FILENAME=/tmp/Login.log (this is an example; just make sure that this is a writable directory) 

d) Bounce all middle tier services for change in steps #2 and #4 to take effect: 

$INST_TOP/admin/scripts/adstpall.sh 

$INST_TOP/admin/scripts/adstrtal.sh 

3> Reproduce the issue. This time you will receive "details" below the error message from the screenshot uploaded by you. 
Click on that and update the complete error message. 


Trace will be logged in "/tmp/Login.log" and you can check this file for error details.

You cannot complete this task because one of the following events caused a loss of page data: A system failure has occurred "Front end is locked after 12.2 upgrade"

  If you have upgraded to Oracle E-Business Suite 12.2.10 Release Update Pack from Oracle E-Business Suite 12.2.6 Release Update Pack (or ea...