Data Dictionary Curruption error in R12.2 - TS Mistmatch

 Data Dictionary Curruption error in R12.2 - TS Mistmatch

Wwhile running adop prepare step fails. in EBSR12.2 using adop you might observe some dictionary corruption interms of TS mismatch

Data dictionary corruption errorThe data dictionary corruption error might occur when the adop prepare step fails.

ERROR

The following error might vary for different environments.

[EVENT]     Verifying data dictionary.

[UNEXPECTED]Data dictionary corrupted:

[UNEXPECTED]Data dictionary corruption - missing parent

.1 Check for Data Dictionary Corruption

1. Run the $AD_TOP/patch/115/sql/adzddtsfix.sql script, following the usage instructions provided.
2. Run the $AD_TOP/sql/ADZDDBCC.sql script to identify whether logical data dictionary corruption is present.
   1. If no corruption is found, proceed with the upgrade.
   2. If corruption is present, follow Step 3.2 below.

3.2 Fix Data Dictionary Corruption (Conditional)

Note: Follow these steps only as a fix when logical data dictionary corruption (missing parent) is present.

1. Copy the script $AD_TOP/patch/115/sql/adzddmpfix.sql to the database tier.
   
   
2. On the database tier, connect to the database as SYSDBA.
   
   
   Note: If you are on Oracle E-Business Suite Release 12.1.3 or Release 12.2 with a multitenant architecture, to connect to a multitenant architecture database as SYSDBA, run the following commands to set the database SID field to <EBS_PDB_Name>, the pluggable database name for your Oracle E-Business Suite database:
   $ source <CDB_NAME>_<NODE_NAME>.env
$ export ORACLE_PDB_SID=<EBS_PDB_Name>;
$ sqlplus "/ as sysdba"


3. Run the $AD_TOP/patch/115/sql/adzddmpfix.sql script.
   
   
4. On the application tier, run the $AD_TOP/sql/ADZDDBCC.sql script again to identify whether data dictionary corruption is still present.
   1. If no corruption is found, proceed with the upgrade or patching cycle.
   2. If corruption is still present, proceed to Step 3.3 below.

3.3 Additional Actions for Data Dictionary Corruption (Conditional)

Note: Follow these steps only when data dictionary corruption is present after following the steps in 3.2 above.

1. On the database tier, go to the $ORACLE_HOME/rdbms/admin directory.
   
   
2. Run the utlirp.sql script , following the usage instructions provided.
   
   
3. Run the utlrp.sql script, following the usage instructions provided.
   
   
4. On the application tier, run the $AD_TOP/sql/ADZDDBCC.sql script again to identify whether data dictionary corruption is still present.
1. If no corruption is found, proceed with the upgrade or patching cycle.
2. If corruption is still present, contact Oracle Support and request a bug to be logged.

AFTER THE ISSUE IS RESOLVED RETRY - PREPARE STEP

REF - (Doc ID 1531121.1)