Tag Archives: solution

R12.2 eBusiness Suite EBS – During ADOP phase = prepare data dictionary corruption missing parent

Adop-PrepareDuring an online patching session with ADOP, when the prepare phase checks the data dictionary integrity, you receive the following error:

R12.2 eBusiness Suite EBS – During ADOP phase = prepare data dictionary corruption missing parent:
Verifying data dictionary.
[UNEXPECTED]Data dictionary corrupted:
[UNEXPECTED]Data dictionary corruption – missing parent
1416131 ORA$BASE APPS BPA_GUIDED_PICKING SYNONYM
1416121 ORA$BASE APPS CO_CLIPPERSHIP_INTERFACE SYNONYM
1416132 ORA$BASE APPS BPA_PRINT_GUIDED_PICK_LABELS SYNONYM
1416128 ORA$BASE APPS GEM_ESIG_INQUIRY_CORE SYNONYM
[UNEXPECTED]Data dictionary corruption detected. Provide details to
[UNEXPECTED]Oracle Support and ask for a bug to be opened against the
[UNEXPECTED]Online Patching component of Oracle Application Install.

[STATEMENT] Please run adopscanlog utility, using the command

“adopscanlog -latest=yes”

Issue:

The corruption is detected with the $AD_TOP/sql/ADZDDBCC.sql scriptis executed just prior to setting up the ADOP session.  This is also a mandatory check performed during pre-upgrade readiness checking for R12.2 upgrades.

Solution:

There is a rudimentary, but effective script supplied in $AD_TOP/patch/115/sql named adzddmpfix.sql (and a number of other adzd___ named scripts that address other data dictionary issues, such as the common TimeZone timestamp issues (Doc ID 2017686.1))

This script is run as SYS and requires all middle-tier services to be shutdown because it’s rebuilding all of the APPS synonyms for objects and recompiling afterwards.

sqlplus “/ as sysdba” @$AD_TOP/patch/115/sql/adzddmpfix.sql

REM $Header: adzddmpfix.sql 120.0.12020000.3 2015/09/14 10:10:32 sstomar noship$
REM dbdrv: none
REM +======================================================================+
REM | Copyright (c) 2005, 2015 Oracle and/or its affiliates. |
REM | All rights reserved. |
REM | Version 12.0.0 |
REM +======================================================================+
REM | FILENAME
REM | adzddmpfix.sql
REM |
REM | DESCRIPTION
REM | Warning: this script is an experimental workaround to the Oracle
REM | Database data Dictionary “missing parent” corruption described in
REM | Bug 20627866. This bug currently has no other known fix, but this
REM | script will repair the problem sufficiently to allow adop to continue
REM | executing.
REM |
REM | Warning: You must be connected as SYSDBA with application services
REM | shutdown to run this script
REM | Usage:
REM | sqlplus / as sysdba
REM | @adzddmpfix.sql
REM |
REM |
REM +=======================================================================+

Sample output:

SQL> @adzddmpfix.sql
“—- Fixing Data Dictionary Corruptions (missing parent) —-”

4 rows deleted.

Commit complete.

System altered.

“—- Compiling invalids —-”

Don’t forget to re-run the $AD_TOP/sql/ADZDDBCC.sql script to identify whether the data dictionary corruption is still present afterwards.

 

Advertisements

R12.1.3 Patch Warnings during AutoPatch – Fixed

If you’ve been bothered by these warning messages that come up during every AutoPatch (adpatch) session in Oracle e-Business Release 12.1.x:

AutoPatch warning:
Product Data File
/ptcharmk/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product “zfa”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

AutoPatch warning:
Product Data File
/ptcharmk/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product “zsa”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

AutoPatch warning:
Product Data File
/ptcharmk/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product “jts”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

AutoPatch warning:
Territory Data File
/ptcharmk/apps/apps_st/appl/admin/zfaterr.txt
does not exist for product “zfa”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

AutoPatch warning:
Territory Data File
/ptcharmk/apps/apps_st/appl/admin/zsaterr.txt
does not exist for product “zsa”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AutoPatch warning:
Territory Data File
/ptcharmk/apps/apps_st/appl/admin/jtsterr.txt
does not exist for product “jts”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

Simply Create the following text files. The contents should be respectively:

$APPL_TOP/admin/jtsprod.txt
%%% Single-product product data file format 12.0.A
jts 875
END_OF_PRODUCT_ABBREVIATIONS -999
875 jts JTS APP
No No No No
Yes Yes
875 JTS JTS
0
1.0.0 1.0.0
none
none
none
none
END_OF_PRODUCTS
Release 12.0.0
12.0.0
R120 R120_ additional-this-mpl
JTS 12.0.0
END_OF_RELEASE 0.0.0

$APPL_TOP/admin/jtsterr.txt (or substitute your own NLS_LANG and NLS_CHARACTERSET settings localized for your instance)
%%% Single-product territory data file format 12.0.A
R120
0 usaeng US AMERICAN EN US American_English
appltape.txt appltape.txt AL32UTF8
Yes Standard Data_Group
none
none
none
none
none
c jts Oracle_CRM_Self_Service_Admin
END_OF_PRODUCT_NAMES
END_OF_LANGUAGE_INFO

$APPL_TOP/admin/zsaprod.txt
%%% Single-product product data file format 12.0.A
zsa 506
END_OF_PRODUCT_ABBREVIATIONS -999
506 zsa ZSA APP
No No No No
Yes Yes
506 ZSA ZSA
0
1.0.0 1.0.0
none
none
none
none
END_OF_PRODUCTS
Release 12.0.0
12.0.0
R120 R120_ additional-this-mpl
ZSA 12.0.0
END_OF_RELEASE 0.0.0

$APPL_TOP/admin/zsaterr.txt
%%% Single-product territory data file format 12.0.A
R120
0 usaeng US AMERICAN EN US American_English
appltape.txt appltape.txt AL32UTF8
Yes Standard Data_Group
none
none
none
none
none
c zsa Oracle_Sales_Analyzer
END_OF_PRODUCT_NAMES
END_OF_LANGUAGE_INFO

$APPL_TOP/admin/zfaprod.txt
%%% Single-product product data file format 12.0.A
zfa 505
END_OF_PRODUCT_ABBREVIATIONS -999
505 zfa ZFA APP
No No No No
Yes Yes
505 ZFA ZFA
0
1.0.0 1.0.0
none
none
none
none
END_OF_PRODUCTS
Release 12.0.0
12.0.0
R120 R120_ additional-this-mpl
ZFA 12.0.0
END_OF_RELEASE 0.0.0

$APPL_TOP/admin/zfaterr.txt
%%% Single-product territory data file format 12.0.A
R120
0 usaeng US AMERICAN EN US American_English
appltape.txt appltape.txt AL32UTF8
Yes Standard Data_Group
none
none
none
none
none
c zfa Oracle_Financial_Analyzer
END_OF_PRODUCT_NAMES
END_OF_LANGUAGE_INFO

Repeat the following dummy file creations for each product you’re registering above:

Create directory $APPL_TOP/zfa/12.0.0/admin

Create directory $APPL_TOP/zfa/12.0.0/admin/driver

Create directory $APPL_TOP/zfa/12.0.0/admin/sql

Create file $APPL_TOP/zfa/12.0.0/admin/driver/zfafile.drv with following contents:
# Dummy xxadfile.drv

Create file $APPL_TOP/zfa/12.0.0/sql/ZFANLINS.sql with following contents:
commit;
exit;

Create file $APPL_TOP/zfa/12.0.0/admin/sql/ZFANLADD.sql with following contents:
commit;
exit;

 

That’s it – no more warnings during AutoPatch. (they are all legacy products anyway)