Script to Diagnose adop and Other AD-TXK Issues in EBS R12.2

Section 1: Overview

The diagnostic script described here is used to collect logs, configuration values, and other information that is typically required to identify the causes of issues with adop and other AD-TXK utilities. The information is then sent to Oracle and used to diagnose and resolve the issues.
Note: The script will not validate the collected information or detect any issues. The script collects the basic information from the instance required for Oracle to start diagnosing the issue.

Section 2: Information Gathered by the Script

The script collects the following information:
General adop log information:
· Dump of AD_ZD_LOGS table given by ADZDSHOWLOG.sql
· Contents of the most recent 3 sessions in $APPL_TOP_NE/../log/adop where adop logs are stored
· Contents of AD_ZD_DDL_HANDLER table
· Output of adop -status
Verification if information used by adop is correct:
· Dump of AD_ADOP_SESSIONS table
· Query used by adop to find the list of nodes, appltop_id and in an instance
· Dump of FND_NODES table
· Dump of ADOP_VALID_NODES table
· Dump of FND_APPLICATION table
· Dump of FND_ORACLE_USERID table
· Run and patch context file.
Database configuration information:
· The values of all database parameters
· Services registered with the listener
· tnsnames.ora file from both run and patch file systems
· listener.ora file from both run and patch file systems
· Source run environment file, connect to DB and print Run edition Value, current edition value and Patch edition value
· Source patch environment file and try to connect to DB
· If patch edition exists get run edition, current edition and patch edition values after connecting to patch edition
· Run database dictionary corruption query
Customer code level information:
· AD and TXK code level from AD_TRACKABLE_ENTITIES table
· Ident of all files in $AU_TOP/perl/adop in Run file system
· Ident of AD_ZD packages in both run and patch edition obtained from compiled version in database and verify they are valid.
· Ident of all AD C files in both run and patch file system.
Check DB objects required by adop:
· Check if Service ebs_patch started and enabled
· Check if log on trigger exists and enabled
· Check AD and EBS CUP 4 is applied.
· AUTHID privileges of SYS packages we are using and AD_ZD packages.
· Check grants on SYS packages used by adop, such as DBMS_OBJECTS_APPS_UTILS, XDB_MIGRATESCHEMA, XDB$MOVESCHEMATAB.
Techstack information:
· Display the status of all the managed servers and their ports, from the context files uploaded in the database.
· Display the location of all the context files uploaded in the database.
· Technology Stack Inventory Report
· Domain configuration file – config.xml
Inventory information:
· Location of central inventory
· Copy of inventory.xml
· copy of /etc/hosts file
Instance specific logfiles:
· Contents of $LOG_HOME directory.
· Copy of remote_execution_result.xml of all the nodes.
· List of seed data tables prepared in the instance and if all DB objects required by seed manager are proper
· Details of running adop, adpatch and adworker processes

Section 3: Execution Procedure

Follow these steps to run the script.

3.1 Check prerequisites

The Oracle E-Business Suite Release 12.2 dual file system must be available as a pre-requisite to the script. Customers using releases lower than 12.2.x should be able to run the script when they are facing issues trying to upgrade to 12.2. Summarizing, the script can be run if at least one of the following is true:
· Fresh install customers after Rapid Install has completed.
· Upgrade customers at the stage after Rapid Install’s actions to lay down the upgrade file system have completed.

3.2 Perform installation

The steps have to be followed in all application tier nodes in the Oracle E-Business Suite instance
1. Download patch 19045166:R12.AD.C from My Oracle Support.
2. Unzip the patch in a new folder.
3. Confirm the following files are present after unzipping:
4. Source the application tier run file system environment file.
5. Run the master perl script,
6. When prompted by the script, supply the apps database user password.
7. Provide the “diagnostic_info_.tar” file (created in the working directory) to Oracle for analysis.

Section 4: Troubleshooting

Provide the “diagnostic_info_.tar” file (created in the working directory) to Oracle for analysis.
  • September 25, 2018 | 20 views
  • Comments