FS_CLONE Is Failed with Sync Error Running txkADOPValidation In Multi Node Environment
(Doc ID 2305466.1)
Last updated on JULY 03, 2024
Applies to:
Oracle Applications DBA - Version 12.2.4 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.4 version, Online Patching - OP
When attempting to do fs_clone on multi nodes the following error occurs.
Running "txkADOPValidation" actions on node(s): xxxxxx4
Remote execution results xml output file: /<path>/fs_ne/EBSapps/log/adop/29/<timestamp>/fs_clone/validate/remote_execution_result_level3.xml
[ERROR] Node: "xxxxxx4" Status: "failed"
[ERROR] txkADOPValidation failed on Node: "xxxxxx4"
[STATEMENT] SQL Statment : " update ad_adop_session_patches
set status='F' ,end_date=to_date('','DD-MM-YYYY HH24:MI:SS')
where applied_file_system_base='/<path>/fs2'
and patch_file_system_base='/<path>/fs1'
and bug_number IN ('CLONE','CONFIG_CLONE')
and status NOT IN ('Y','X')
and appltop_id=1195
and node_name IN ('xxxxxx4')
"
[PROCEDURE] [START <timestamp>] Checking if adop can continue with available nodes
[PROCEDURE] Calling: /<path>/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPEvalSrvStatus.pl
[EVENT] Log: /<path>/fs_ne/EBSapps/log/adop/29/<timestamp>/fs_clone/xxxxxx2
[PROCEDURE] [END <timestamp>] Checking if adop can continue with available nodes
Continuing with processing on node(s): xxxxxx1,xxxxxx2
The issue can be reproduced at will with the following steps:
1. Log on to application tier
2. Source environment file
3. run adop phase=fs_clone
adop phase was failed, hence unable to complete patching cycle.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |