Quantcast
Channel: Doyensys Allappsdba Blog..
Viewing all articles
Browse latest Browse all 1640

Article 1

$
0
0
Adop Finalize phase has failed with Data dictionary corruption - timestamp mismatch.


While running Finalize phase in Adop cycle , we encounter with the following error Data dictionary corruption - timestamp mismatch.

 Error message :
---------------------

UNEXPECTED]Data dictionary corrupted:
[UNEXPECTED]Data dictionary corruption - timestamp mismatch
APPS GME_PENDING_PRODUCT_LOTS_DBL V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS BMT_SUPPLIER_BANKS_PK V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS EAM_ASSET_MOVE_PUB V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS PSP_ER_WORKFLOW V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS JAI_CMN_ST_FORMS_PKG V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS PAY_DK_PAYMENT_PROCESS_PKG V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS PA_ENDECA_INTEGRATION V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS MSD_DEM_CTO V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
APPS PAY_CA_RL1_MAG V_20170621_1401 APPS APPS V_20170621_1401 P Status: 5
[UNEXPECTED] Follow the instructions in the "Fix data dictionary corruption"


Soultion: 
------------
Fix data dictionary or time stamp mismatch

Step 1
-------
1. Run the file $AD_TOP/patch/115/sql/adzddtsfix.sql
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
3. Run utlrp.sql
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.

Ref: Doc ID 1531121.1






Viewing all articles
Browse latest Browse all 1640

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>