Verifying existence of context files in database.
Checking if adop can continue with available nodes in the configuration.
Log: /u01/install/APPS/fs_ne/EBSapps/log/adop/7/20221108_074858/fs_clone/am501amerap0005
txkADOPEvalSrvStatus.pl returned SUCCESS
Validating configuration on admin node: [
![image][pasted-2022.11.08-15.57.05.png]
am501amerap0005].
Output: /u01/install/APPS/fs_ne/EBSapps/log/adop/7/20221108_074858/fs_clone/validate/remote_execution_result_level1.xml
[ERROR] txkADOPValidation failed on Node: “am501amerap0005”
[ERROR] txkADOPValidation failed or is incomplete on Admin node: am501amerap0005
[ERROR] Unable to continue processing on other available nodes: am501amerap0006
[UNEXPECTED]Error running “txkADOPValidation” on node(s): am501amerap0005.
Summary report for current adop session:
Node am501amerap0005:
– Fs_clone status: Failed
Node am501amerap0006:
– Fs_clone status: Not Started
For more details, run the command: adop -status -detail
[STATEMENT] Please run adopscanlog utility, using the command
“adopscanlog -latest=yes”
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 2 (Fail)
[applmgr@AM501AMERAP0005 ~]$
Cause
The global inventory on secondary node was corrupt or missing on secondary node(s) where the txkADOPValidation was failing. ADOPValidation Log files showed below error for secondary node
ERROR: Either /u01/app/oraInventory/ContentsXML/inventory.xml file doesn’t exist or doesn’t have READ permission.
Solution
Copy the contents of /etc/oraInst.loc from Primary to Secondary. Take a tar ball of global inventory from Primary to Secondary nodes. Ensure permissions are same as primary node.
Re-run the fs_clone
Orama.blog 