Oracle EBS 12.2 ADOP utility error

ADOP exiting with status = 255 (Fail)

In this Document

Symptoms 

Cause

Solution

Applies to:

Oracle Applications DBA - Version 12.2 and later. This can be applies to all platforms.

Symptoms

E-Business Suite 12.2, Online Patching ADOP Utility related issues

 $adop phase=apply patches=25820806,26720905 merge=yes hotpatch=yes

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Validating credentials.

Initializing.

Run Edition context  : /u02/ebsappl/SID/fs1/inst/apps/FRESH_test/appl/admin/SID_host.xml      Patch edition context: /u02/ebsappl/SID/fs2/inst/apps/FRESH_test/appl/admin/SID_host.xml 

                                           

Cause

An invalid server name was specified in the context file.

The applications context file, SID_host.xml, contains the following incorrect entries for parameters

s_apps_jdbc_connect_descriptor  and

s_apps_jdbc_patch_connect_descriptor

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=ora.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SID)))

 jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ebs_patch)(INSTANCE_NAME=SID)))

Solution

To resolve the issue test the following steps in a development instance and then migrate accordingly

1. The applications context file, SID_host.xml, contains the following incorrect entries for parameters

s_apps_jdbc_connect_descriptor   and

s_apps_jdbc_patch_connect_descriptor

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=ora12.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SID)))

 jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora12.<domain name>.com)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ebs_patch)(INSTANCE_NAME=SID)))

Use the OAM context editor to remove the second host definition, which is incorrect.

The part to be removed from each is

  (ADDRESS=(PROTOCOL=tcp)(HOST=<domain name>.<domain name>.com)(PORT=1521)).

2. Once the context file has been set correctly, run autoconfig on the apps tier and run 

adop phase=fs_clone

    Then stop and start the apps services, and log out / login as the applmgr user to ensure the new autoconfig environment variables are picked up by the system.

3. Test the adop utility again to confirm that the error has been resolved.

ADOP Fails With Error: Unable to Find Appltop_id In this Document Symptoms Cause Solution Symptoms  When running ADOP with phase=apply, restart=yes it fails with following error: [UNEXPECTED]Unable to find appltop_id for host test in database Node registry is valid. [WARNING]   MTCC has not been run. Apply Patch 17537119 and run checkMTpatch.sh Checking for existing adop sessions.     [UNEXPECTED]Unable to find appltop_id for host test in database     [UNEXPECTED]Invalid APPL_TOP ID: "".     [UNEXPECTED]Unrecoverable error occurred. Exiting current adop session.     adop exiting with status = 2 (Fail) Cause  The SQL statement ADOP uses to get the admin node name is:    select node_name from FND_OAM_CONTEXT_FILES    where NAME not in ('TEMPLATE','METADATA','config.txt') and    CTX_TYPE='A' and (status is null or upper(status) in ('S','F'))    and EXTRACTVALUE(XMLType(TEXT),'//file_edition_type') = 'run'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_group_status[@oa_var=''s_web_admin_status'']')='enabled'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_list/oa_service[@type=''admin_server'']/oa_service_status')='enabled'; Execute above SQL statement manually, it returns: node_name appltest appltest The problem is due to the table FND_OAM_CONTEXT_FILES has duplicate entries. Solution Test the following steps in a non critical development instance where the issue can be reproduced and then migrate according if the problem is resolved: 1. Back up the table FND_OAM_CONTEXT_FILES table. 2. Delete the duplicate record in table FND_OAM_CONTEXT_FILES reflected in the following select: select node_name from FND_OAM_CONTEXT_FILES    where NAME not in ('TEMPLATE','METADATA','config.txt') and    CTX_TYPE='A' and (status is null or upper(status) in ('S','F'))    and EXTRACTVALUE(XMLType(TEXT),'//file_edition_type') = 'run'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_group_status[@oa_var=''s_web_admin_status'']')='enabled'    and EXTRACTVALUE(XMLType(TEXT),'//oa_service_list/oa_service[@type=''admin_server'']/oa_service_status')='enabled'; Please check the column "NAME" and "PATH" to identify the duplicate records. The duplicate record may come from the source environment. Then use statement "delete from FND_OAM_CONTEXT_FILES where <duplicate record conditions>" to delete the record and commit. Please note, the standard process to populate the table FND_OAM_CONTEXT_FILES  is to run autoconfig. Since in this case ADOP cycle is running, above action plan is a workaround. Please perform above action under Oracle support's instruction. 3. Re-run the select above to ensure it returns the correct value. 4. Retest the issue. 12.2 EBS Patch 25820806 (R12.AD.C.Delta.10) fails when merged and applied with Patch 26720905:R12.AD.C with ORA-01400: cannot insert NULL into ("APPLSYS"."AD_TIMESTAMPS"."ATTRIBUTE") error (Doc ID 2361013.1) To Bottom In this Document Symptoms Changes Cause Solution References Symptoms While applying the R12.AD.C.Delta.10 Patch 25820806 using the following command, it fails with error: adop phase=apply patches=25820806,26720905 merge=yes hotpatch=yes INSERT INTO fnd_install_processes (worker_id, control_code, status,  context, pdi_product, pdi_username, command, file_product, subdirectory,  filename, phase, install_group_num, arguments,  symbolic_arguments,machine_name) VALUES (1, 'W', 'W', 'UNDEF', 'UNDEF',  'UNDEF', 'UNDEF', 'UNDEF', 'UNDEF', 'UNDEF', 0, 0,  rpad('-',100,'-'),rpad('-',100,'-'),'UNDEF') Connecting to APPS......Connected successfully. AutoPatch error: Error while inserting row in AD_TIMESTAMPS AutoPatch error: ORA-01400: cannot insert NULL into ("APPLSYS"."AD_TIMESTAMPS"."ATTRIBUTE") AutoPatch error: aijhip(): Error calling aijmgrInsertHangingRowInAdTmStmp() AutoPatch error: Failed running aidinv() in adprim() AutoPatch error: Failed running Invoker's Rights maintanance logic Changes  Fresh Installation of 12.2 followed by latest AD/TXK Delta 10 patches Cause Patch 25525148 (Rapid Install consolidated one-off bundle on top of startCD51) was not used while installing the Oracle E-Business Suite Release 12.2 system Solution Test the following in development instance and migrate the solution accordingly: 1. Considering that the hotpatch has failed, there isn't a way to restore and abort cannot be run 2. If a backup prior to AD.C.Delta.10 is available, you may restire (OR) re-do the Fresh 12.2.0 installation and ensure all steps are complete to the point where AD.C.Delta.10 has to be applied. 3. If Patch 25525148 (Rapid Install consolidated one-off bundle on top of startCD51) was not used while installing your Oracle E-Business Suite Release 12.2 system, apply the patches in the following order: Apply Patch 25820806 (R12.AD.C.Delta.10) adop phase=apply patches=25820806 hotpatch=yes Apply Patch 26720905:R12.AD.C adop phase=apply patches=26720905 hotpatch=yes 4. Continue with the upgrade as per "Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)" References NOTE:1907419.1 - ADOP Fails With Error Unable to Find Appltop_id NOTE:1320300.1 - Oracle E-Business Suite Release Notes, Release 12.2 NOTE:1617461.1 - Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 NOTE:2064223.1 - How to Synchronize FND_NODES, ADOP_VALID_NODES, and FND_OAM_CONTEXT_FILES in 12.2 When ADOP Phase=Prepare Fails with Error 'not able to detect any valid application tier nodes in ADOP_VALID_NODES table. ' NOTE:1901242.1 - Script to Diagnose adop and Other AD-TXK Issues in Oracle E-Business Suite Release 12.2 Patch 19045166:R12.AD.C

Posted by: Anil Bandi
Oracle Apps DBA.