EBS Compliance Checker

Fix data dictionary or time stamp mismatch

Apply the correct Online Patching Readiness and GSCC Report Patch for the code level from which you are upgrading, if not already applied. (Follow first section of the same document for this)

Step 1

1. Run the file $AD_TOP/patch/115/sql/adzddtsfix.sql (Following the usage instructions provided in it).
2. Run the $AD_TOP/sql/ADZDDBCC.sql script to identify whether the data dictionary corruption is still present.
a. If no corruption is found, proceed with the upgrade.
b. If corruption is still present, follow Step 2 below.

Step 2

Fix Logical data dictionary corruption (missing-parent)

Follow this step only when logical data-dictionary corruption is present.
1. Connect to database as "SYSDBA". 2. Run the $AD_TOP/patch/115/sql/adzddmpfix.sql 3. Run the $AD_TOP/sql/ADZDDBCC.sql script again to identify whether the logical data dictionary corruption is still present.
a. If no corruption is found, proceed with the upgrade or adop patching-cycle.
b. If corruption is still present, contact Oracle Support and log a bug.

Step 3

Follow this step only when data dictionary corruption is still present after following Step 1 above.
1. On database node, go to $ORACLE_HOME/rdbms/admin directory.
2. Run utlirp.sql (following the usage instructions provided).
3. Run utlrp.sql (following the usage instructions provided).
4. Run the $AD_TOP/sql/ADZDDBCC.sql script again to identify whether the data dictionary corruption is still present.
a. If no corruption is found, proceed with the upgrade.
b. If corruption is still present, contact Oracle Support and log a bug.

adop phase=cleanup loosing columns on a table.

When doing an adop cycle users complain that a table has lost its columns

Solution:

exec ad_zd_table.upgrade(<TABLE NAME>);



SQL> exec ad_zd_table.upgrade('MONT','MONT_EXPLODED_BOM');

SQL> exec ad_zd_table.patch('MONT','MONT_EXPLODED_BOM');

PL/SQL procedure successfully completed.