6 Replies Latest reply on Jul 12, 2018 5:12 PM by Beauty_and_dBest

    Confusing document (Doc ID 1531121.1)

    Beauty_and_dBest

      Upgrading    EBS 12.1.3  to 12.2.0

       

      Hi ALL,

       

      Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1)

       

       

      I am now applying Online Patching Readiness and GSCC Report Patch for

      • 26086707:R12.AD.C Release 12.2 or higher

       

      I already applied the patch and its readme instruct to run the following sql scripts.

      $AD_TOP/sql/ADZDPSUM.sql

      $AD_TOP/sql/ADZDPAUT.sql

      $AD_TOP/sql/ADZDPMAN.sql

      $AD_TOP/sql/ADZDDBCC.sql

      $AD_TOP/sql/ADZDPCUST.sql

       


      Do I need to run all the above?

       

      When do I run these set of tasks below?

       

      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.

       

      Step 4

      ADZDMVREFRESHNEEDED.SQL

      =======================

      This script is optional but if customers want to reduce the overall upgrade

      time, then this script needs to be run before starting the 12.2.0 upgrade

      driver.

       

       

      I am comparing above with the process taken by this blog >>>  Oracle APPS DBA pieces: Oracle E-Business Suite upgrade from 12.1.1 to 12.2.7

       

      I can see it has registered custom schema?  >> sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> GAUTAMS

       

      I do not see any ADZDREG.sql above

      Where do I get this register scripts?

       

       

       

      Please help....

       

      Kind regards,

      jc