Oracle EBS 12.2 ADOP Troubleshooting Guide: Fix Online Patching Failures and Recovery Strategies

Why Oracle EBS 12.2 ADOP Troubleshooting Matters

Are you running Oracle EBS 12.2 patches but facing unexpected failures?

In real production environments, Oracle EBS 12.2 ADOP troubleshooting becomes critical when:

• Patch workers fail

• Sessions hang

• Cutover does not complete

Understanding how to diagnose and recover from these issues is essential for any Apps DBA.

If you are new to patching, read:
/blog/oracle-ebs-12-2-online-patching-deep-dive

Understanding ADOP Failure Points

Before troubleshooting, you need to identify where failures occur.

Common ADOP Failure Phases

ADOP Log Analysis (First Step in Troubleshooting)

Log Location

$APPL_TOP/admin/log/adop/

Session Logs

$APPL_TOP/admin/log/adop/<session_id>/

Important Log Files

• adop.log → Main process

• adwork*.log → Worker-level errors

• adpatch.log → Patch execution

• adzd*.log → Online patching details

Always start troubleshooting from logs.

Scenario 1 – Worker Failure During Apply Phase

Problem

Worker failed with error code

Solution Steps

Step 1: Open Worker Control

adctrl

Step 2: Check Worker Log

vi adworkXXX.log

Step 3: Restart Failed Worker

adctrl

Select: Restart failed job

Best Practice

Do not restart the full patch immediately.

Fix only failed workers first.

Scenario 2 – ADOP Patch Hanging or Slow

Symptoms

• No progress

• Low CPU usage

• Patch appears stuck

Check Database Blocking

SELECT blocking_session, sid, serial#
FROM v$session
WHERE blocking_session IS NOT NULL;

Kill Blocking Session (if required)

ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;

Always validate before killing sessions.

Scenario 3 – Invalid Objects After Finalize

Check Invalid Objects

SELECT owner, object_name
FROM dba_objects
WHERE status='INVALID';

Recompile Objects

EXEC UTL_RECOMP.RECOMP_PARALLEL(8);

Retry Finalize

adop phase=finalize

Scenario 4 – Cutover Failure (High Risk Issue)

Problem

Cutover fails or services do not start.

Restart Services

adstpall.sh apps/apps_password
adstrtal.sh apps/apps_password

Restart Cutover Safely

adop phase=cutover restart=yes

Key Insight

Never restart the full patch cycle.

Always use restart options.

Scenario 5 – Failed ADOP Session Recovery

Check Status

adop -status

Abort Session (Last Option)

adop phase=abort

Restart New Cycle

adop phase=prepare

Abort should only be used when recovery is not possible.

Scenario 6 – File System Synchronization Issues

Fix Sync Issues

adop phase=prepare force=yes

Verify File System

echo $FILE_EDITION

Performance Optimization for ADOP

Increase Workers

adop phase=apply workers=16

Enable Parallel Execution

ALTER SESSION ENABLE PARALLEL DDL;

Monitor Logs Live

tail -f $APPL_TOP/admin/log/adop/*.log

Advanced Debugging Techniques

Check ADOP Sessions

SELECT session_id, status, phase
FROM ad_adop_sessions;

Check Patch History

SELECT bug_number, creation_date
FROM ad_bugs;

Best Practices for Stable Oracle EBS 12.2 ADOP Troubleshooting

• Run prepare phase early

• Always validate before cutover

• Monitor logs continuously

• Perform regular cleanup

• Keep environments consistent

Conclusion

Oracle EBS 12.2 ADOP troubleshooting is a critical skill for Apps DBAs working in production environments.

By understanding failure scenarios, recovery techniques, and performance optimization strategies, you can ensure stable patching with minimal downtime.