While running the CUTOVER phase the option appears to abandon or cut off the slave node and if we press n, it will exit out of this and then we have to rectify the error first and restart the prepare phase again by
adop phase=prepare allnodes=yes
The same goes for apply phase.
But for cutover phase, the situation is little different. ADOP will just continue by just skipping the problematic node(the problematic node has to be secondary) and this problematic node will be marked as abandoned after cut-over. If the abandoned node is meant for imporant ebs Services such as conc processing then skipping this will impact the availability of concurrent processing. So it is not advisable to skip any errors during patching. And also the admin node cannot have a status abandoned, so if an error occurs in admin node, it cannot be skipped and has to be corrected before proceeding with patching. The abandoned nodes has to be removed and recreated using rapid clone.
12.2 Adtstartal.sh Fails with "This Is An Abandoned/lagging Node. Services Cannot Be Started Up On This Node" (Doc ID 1918038.1)
1. And if user says no ('n') to above prompt, then adop will exit out with error, so then user can run the adop prepare phase again (using allnodes=yes) from primary node to recover failed nodes.
2. If user says no 'n' to the above prompt, then adop will exit with error. The user can reapply the failed patch from the primary node using allnode=yes for failed patches to recover failed node (N2).
Note: The primary node is not eligible to be counted as an abandoned node. If the primary node appears on the list of abandoned nodes, you should contact Oracle Support.
Identifying Abandoned Nodes:
1. Check the $ADOP_LOG_HOME/<latest_session_id>/adop_latest_timestamp.log log file on primary node, where adop prints the summary report for all the available nodes at the end. This report gives information about the phases completed or failed on a particular node in that cycle, and the node's status (completed or abandoned).
2. In next prepare, apply or fs_clone phase, adop displays the following error message for abandoned nodes and then exits.
Node(s) <abandoned_node_list> were abandoned in a previous patching cycle.
To recover these node(s), follow the instructions in My Oracle Support Knowledge Document 1677498.1.
Restoring Abandoned Nodes
To bring an abandoned node back into the system, you must first delete it and then restore it
1. Delete the abandoned node
To delete an abandoned node from the configuration, follow the steps in Section 5.4 of My Oracle Support Knowledge <Document 1383621.1>, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone.
2. Run fs_clone on the primary node
You can learn about running fs_clone in the Oracle E-Business Suite Maintenance Guide, Part No. E22954.
3. Restore the abandoned node
To add an abandoned node back into the configuration, follow the steps in Section 5.3 of My Oracle Support Knowledge <Document 1383621.1>, Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone.
