How to fix fs_clone failed due to node was abandoned in previous patching cycle.

by

Introduction:-

In this article, we will resolve fs_clone failed error after successfully add external node still showing Node was abandoned in previous patching cycle.

fs_clone failed due to node was abandoned.

After successfully add external node still showing Node was abandoned in previous

patching cycle during fs_clone. In my case external(secondary) node working fine

and no any issue. But fs_clone failed, because earlier external node was

abandoned after that deleted and re-added successfully.

how to run adop phase=fs_clone

$adop phase=fs_clone

The node was abandoned during cutover session 26, see below error for fs_clone issues:

START 2021/08/23 16:57:15] Arguments passed to adop
phase=cutover mtrestart=no
[END 2021/08/23 16:57:15] Arguments passed to adop
[STATEMENT] Verifying parameters
[STATEMENT] Sourcing Run edition environment /oracle/prd/EBSFS/fs2/EBSapps/appl/APPSprd_prdsrv.env
 
[EVENT] Validating system setup.
[STATEMENT] Checking for required environment
[PROCEDURE] Running: adpawc -nodisp
[STATEMENT] Using 40 workers (Default: 40, Recommended maximum limit: 400)
[PROCEDURE] [START 2021/08/23 16:57:53] Identifying Admin server node
[STATEMENT] Admin node : "prdsrv"
[PROCEDURE] [END 2021/08/23 16:57:54] Identifying Admin server node
[EVENT] Node registry is valid.
[STATEMENT] Value of nodes : "prdisupplier,prdsrv"
 
..snip...
[UNEXPECTED]txkADOPValidation failed on node(s) : prdisupplier
If you choose to proceed with cutover, node(s) <prdisupplier> will be marked as abandoned.
Do you want adop to continue processing on completed nodes [y/n]?
Continuing with processing on node(s): prdsrv

You will need to remove the node and re-add it in via the cloning note:

Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone ( Doc ID 1383621.1 ) Delta 7


5.4 Deleting an Application Tier Node:-

To check the adop_sessions.


SQL>SELECT adop_session_id "SESSION ID" ,NODE_NAME,NODE_TYPE,DECODE 
(prepare_status,'Y' , 'PHASE IS DONE', 'N' , 'NOT COMPLETED', 'X' , 'NOT 
APPLICABLE', 'R' , 'PHASE IS RUNNING', 'F' , 'PHASE FAILED', 'C' , 
'COMPLETED') "PREPARE STATUS" ,DECODE (apply_status,'Y' , 'PHASE IS DONE', 'N' , 'NOT COMPLETED', 'X' , 'NOT APPLICABLE', 'R' , 'PHASE IS RUNNING', 'F' , 'PHASE FAILED', 'P','AT LEAST ONE PATCH APPLIED' , 'C' , 'COMPLETED') "APPLY STATUS" ,DECODE(cutover_status,'N' , 'NOT STARTED', 'R' , 'RUNNING', 'F' , 'FAILED', 'C' , 'COMPLETED', 'P' , 'ACTIVE', 'Y' , 'COMPLETED', 'X' , 'NOT APPLICABLE', '0' , 'FORCE_SHUTDOWN_BEGIN', '1' ,'FORCE_SHUTDOWN_COMPLETED_DB_CUTOVER_BEGIN', '3' , 'DB_CUTOVER_COMPLETED_FLIP_SNAPSHOTS_BEGIN', 'D' , 'FLIP_SNAPSHOTS_COMPLETED_FS_CUTOVER_BEGIN', '4' , 'FS_CUTOVER_COMPLETED_ADMIN_STARTUP_BEGIN', '5' , 'ADMIN_STARTUP_COMPLETED_FORCE_STARTUP_BEGIN', '6' , 'FORCE_STARTUP_COMPLETED') "CUTOVER STATUS" ,DECODE (abort_status,'Y' , 'PHASE IS DONE', 'N' , 'NOT COMPLETED', 'X' , 'NOT APPLICABLE', 'R' , 'PHASE IS RUNNING', 'F' , 'PHASE FAILED', 'C' , 'COMPLETED') "ABORT STATUS" ,DECODE (cleanup_status,'Y' , 'PHASE IS DONE', 'N' , 'NOT COMPLETED', 'X' , 'NOT APPLICABLE', 'R' , 'PHASE IS RUNNING', 'F' , 'PHASE FAILED', 'C' , 'COMPLETED') "CLEANUP STATUS" ,DECODE (status,'Y' , 'PHASE IS DONE', 'N' , 'NOT COMPLETED', 'X' , 'NOT APPLICABLE', 'R' , 'PHASE IS RUNNING', 'F' , 'PHASE FAILED', 'C' , 'COMPLETED') "STATUS" ,ABANDON_FLAG FROM ad_adop_sessions ORDER BY adop_session_id DESC;

You might have to try the following but be aware this is just a workaround that has not been tested and therefore we cannot guarantee it will produce the expected results and you will need to make sure to have a valid backup of your system before proceeding.

  • Confirm secondary node is properly registered in fnd_nodes and adop_valid_nodes table
  • Then, update ad_adop_sessions table for session 26.

SESSION ID NODE_NAME NODE_TYPE PREPARE STATUS APPLY STATUS CUTOVER STATUS ABORT STATUS CLEANUP STATUS STATUS ABANDON_FLAG
26 prdsrv master PHASE IS DONE PHASE IS DONE COMPLETED NOT APPLICABLE PHASE IS DONE COMPLETED
26 prdisupplier slave PHASE IS DONE PHASE IS DONE FS_CUTOVER_COMPLETED_ADMIN_STARTUP_BEGIN NOT APPLICABLE NOT COMPLETED PHASE 
 
FAILED 26 <--------

1. Backup Table.

create table ad_adop_sessions_bk as select *
from ad_adop_sessions

2. Update table

SQL>update ad_adop_sessions set abandon_flag=null where node_name="prdisupplier" and session_id = 26;
SQL> Commit;

3. Retest  the issue.

After above action now fs_clone will complete successfully.

Adding another very informative article, click here.

Leave a Comment