12.2 Applications DBA Upgrade ADOP Online Enablement Patch 13543062 Completes Successfully But Script ADZDSHOWDDLS.sql Shows CUTOVER And CLEANUP Stages As ‘Not Executed’

Symptoms:

The enablement patch application may take several hours to finish. You can monitor its progress at any time by running the DDL Status Report  (ADZDSHOWDDLS.sql) as follows

$ cd $LOG_HOME/appl/op

$ mv adzdshowddls.out adzdshowddls.outbkp

$ sqlplus apps @$AD_TOP/sql/ADZDSHOWDDLS.sql

This report lists a count of the DDL statements that are required to EBR enable your environment. The report is organized by outcome of execution: ‘Successfully Executed’, ‘Not Executed’, and ‘Failed Execution’. At the end of the patch application the report should have a zero count in the sections: ‘Not Executed’ and  ‘Failed Execution’. If the report contains ‘Not Executed’ and ‘Failed Execution’ items, then report these failures to Oracle Support. You will be asked to provide the output from the report, the patch log and all worker logs, and the online patching enablement status report output. If there is any worker failure during the Online Enablement patch, you should not ignore or skip the failed error. The issue should be addressed before restarting the worker. Ignoring or skipping the error can cause database corruption.

Note: In addition to the above outcomes, some DDL statements may complete with a ‘Warning’ status.

DOC>#

Phase                     Count Status

——————– ——- ——————————

DROP_UNUSED_OBJECT         24 S – Successfully Executed

COPY_TYPE                   45 S – Successfully Executed

COMPILE_TYPE                         1 S – Successfully Executed

COPY_EVOLVED_TYPE              1 S – Successfully Executed

FIX_COLUMN                2 S – Successfully Executed

FIX_TYPE                      23 S – Successfully Executed

FIX_PUBLIC_SYNONYM        6730 S – Successfully Executed

RECREATE_AQ_OBJECT           13 S – Successfully Executed

DROP_OBJECT                           9 S – Successfully Executed

ENABLE_EDITIONING           175 S – Successfully Executed

UPGRADE_TABLE              20025 S – Successfully Executed

                                       2 E – Error

UPGRADE_SEED                     2681 S – Successfully Executed

COLLECT_STATS                     2681 S – Successfully Executed

UPGRADE_MVIEW                 113 S – Successfully Executed

                                       1 E – Error

CLEANUP                       1 N – Not Executed

17 rows selected.

DOC>

$ grep -i failed adzdshowddls.out

prodapp(oracle):/dodiapps/prod/prodapps/fs1/inst/apps/PROD_prodapp/logs/appl/op

$

prodapp(oracle):/dodiapps/prod/prodapps/fs1/inst/apps/PROD_prodapp/logs/appl/op

$ grep -i not adzdshowddls.out

CLEANUP                    1 N – Not Executed

prodapp(oracle):/dodiapps/prod/prodapps/fs1/inst/apps/PROD_prodapp/logs/appl/op

$

Solution:

No technical changes are required, as it is the intended functionality for hotpatch to skip Cleanup and Cutover phases.

Users should verify the ADOP enablement Patch 13543062 completes successfully without any errors or skipped workers.

If no issues are found then users may proceed with the upgrade.

The CLEANUP and CUTOVER will show as “Not Executed”, and this informational and can be ignored.

Metalink Reference:

12.2 Applications DBA Upgrade ADOP Online Enablement Patch 13543062 Completes Successfully But Script ADZDSHOWDDLS.sql Shows CUTOVER And CLEANUP Stages As ‘Not Executed’ (Doc ID 2352746.1)