System Crashed While adop in Running State Oracle Apps R12.2

Restart adop session:  My system crashed While adop phase is in Running State while applying patches on Oracle Apps R12.2:

1. When I restart my system, Database, and Applications; adop status is still showing APPLY Phase as RUNNING as below:

[oracle@appsdbatraining scripts]$ adop -status

Enter the APPS username: apps
Enter the APPS password:
Current Patching Session ID: 2

Node Name Node Type Phase Status
————— ————— ———– —————
apps master APPLY RUNNING
PREPARE NOT APPLICABLE
CUTOVER NOT APPLICABLE
CLEANUP NOT STARTED

File System Synchronization Used in this Patching Cycle: None

For more information, see the full ADOP Status Report.
Generating full ADOP Status Report at location: /u01/ebiz/apps/TEST/fs_ne/EBSapps/log/status_20141121_172303/adzdshowstatus.out

2. Login to Database as apps user and query the sessions which are running as below:

[oracle@appsdbatraining ~]$ sqlplus apps/apps

SQL*Plus: Release 10.1.0.5.0 – Production on Fri Nov 21 17:25:08 2014

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select adop_session_id from ad_adop_sessions where status=’R’;

ADOP_SESSION_ID
—————
2

3. As one session is showing as active, make it Completed as below:

SQL> update ad_adop_sessions set status=’C’ where status=’R’;

1 row updated.

SQL> commit;

4. Check the adop status again:

[oracle@apps ~]$ adop -status

Enter the APPS username: apps
Enter the APPS password:

Current Patching Session ID: 2

Node Name Node Type Phase Status
————— ————— ———– —————
apps master APPLY ACTIVE
PREPARE NOT APPLICABLE
CUTOVER NOT APPLICABLE
CLEANUP NOT STARTED

File System Synchronization Used in this Patching Cycle: None

For more information, see the full ADOP Status Report.
Generating full ADOP Status Report at location: /u01/ebiz/apps/TEST/fs_ne/EBSapps/log/status_20141121_173047/adzdshowstatus.out
Please wait…
Done…!

5. Even though the APPLY Phase is showing as ACTIVE, you can try to apply the patch again with option as forceapply:

[oracle@appsdbatraining ~]$ adop phase=apply patches=17204589 hotpatch=yes options=forceapply

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Patch will be applied successfully 🙂

Nagulu Polagani

"We are all apprentices in a craft where no one ever becomes a master."