Oracle EBS 12.2 - adop - collection of various snippets and scripts

 

EBS 12.2 docs :  https://docs.oracle.com/cd/E51111_01/current/html/docset.html


Checkout the maintenance guide :  https://docs.oracle.com/cd/E51111_01/current/acrobat/122ebsmt.zip



What happens during adop phase=cutover ?

The phase adop phase=cutover , has many tasks.  
  • Validations: First on primary node and then on all slave nodes in parallel
  • Shutdown of services: Parallel on all slave nodes followed by primary node
  • DB Cutover: Only on primary node, rest all slave nodes wait
  • FS Cutover: Parallel on all nodes
  • Startup of services: First on primary node and then on all slave nodes in parallel
Note that all these subtasks are completed sequentially one after the other i.e. each subtask should be complete on all nodes before proceeding to the subsequent subtask.

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


Patch not applied on XYZ node during Cutover

In this blog, we will be discussing an unusual situation where cutover fails with “Patch not applied on XYZ Node”

Background:  We have 12.2.5 instance with three nodes.

Node 1 – Primary Node (Forms and Web)
Node 2 – Secondary Node (Batch Processing)
Node 2 – External Node (iStore)

We have applied a couple of patches which went fine, during cutover, ADOP failed saying One of the Patch 12345678 is not applied to Node 3 and suggested to either apply it or abandon the node.

Observation: We observed that there were no log files created on Node 3 for the Patch 12345678, and on Node 1 & 2, the patch seems to have already applied on previous ADOP Session and log file stated that, it is skipping the patch on the current node and proceeding on other nodes.

Verification: We ran below query to get complete information about the patch. Status showed that applying the patch 12345678 skipped on Node 3, as its already applied on Node 1, Strange !!!

SELECT adop_session_id, bug_number, session_type, 
 DECODE(status,'N','Applied on other nodes',
 'R','Running',
 'H','Failed (Hard)',
 'F','Failed (Jobs Skipped)',
 'S','Success (Jobs Skipped)',
 'Y','Success',
 'C','Clone Complete') status,
 applied_file_system_base, patch_file_system_base,
 node_name, start_date, end_date, 
 ROUND((end_date - start_date) * 24*60,2) exec_time,
 adpatch_options, autoconfig_status, driver_file_name
FROM ad_adop_session_patches
WHERE session_type IN ('ADPATCH','HOTPATCH','DOWNTIME','ONLINE')
ORDER BY adop_session_id, start_date, end_date;
Action Plan: Apply the missing patch on Node 3 with force option


adop phase=apply patches=12345678 allnodes=NO action=nodb options=forceapply

After force applying the patch on Node 3, cutover finished without any issues.

Comments

Post a Comment