After AD.C.Delta.6 and TXK.6,
when running
$adop phase=fs_clone,
we hit with an issue:
Validating system setup...
Node registry is valid.
Checking for pending adop sessions...
No pending session exists.
Staging new adop session...
[ERROR] Failed to execute SQL statement :
begin
ad_zd_adop.INSERT_ADD_NODE_RECORDS;
end;
[ERROR] Error Message :
[ERROR] ORA-20010: ORA-01403: no data found
[ERROR] ORA-06512: at "APPS.AD_ZD_ADOP", line 2790
[ERROR] ORA-06512: at line 2 (DBD ERROR: OCIStmtExecute)
[UNEXPECTED]Error occurred while adding new node information
[UNEXPECTED]Unrecoverable error occured. Exiting the current session.
[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)
When we open the AD_ZD_ADOP package body and changed the lines
From this
cursor new_nodes is
select node_name
from adop_valid_nodes
where node_name not in (select node_name from ad_adop_sessions
where adop_session_id = (select max(adop_session_id) from
ad_adop_sessions));
cursor available_nodes is
select node_name from ad_adop_sessions
where adop_session_id = (select max(adop_session_id) from
ad_adop_sessions)
and node_name in (select node_name from
adop_valid_nodes)
order by node_name;
to
cursor new_nodes is
select UPPER(node_name) node_name
from adop_valid_nodes
where node_name not in (select node_name from ad_adop_sessions
where adop_session_id = (select max(adop_session_id) from
ad_adop_sessions));
cursor available_nodes is
select node_name from ad_adop_sessions
where adop_session_id = (select max(adop_session_id) from
ad_adop_sessions)
and node_name in (select UPPER(node_name) from
adop_valid_nodes)
order by node_name;
and compile the package and package body.
We were able to complete the fs_clone successfully.
Generating log report...
Output: /u01/install/APPS/fs_ne/EBSapps/log/adop/26/fs_clone_20150909_040049/PRD12241_LO64BLWPA1/adzdshowlog.out
adop phase=fs_clone - Completed Successfully
Issue identified,
May be because of our hostname all in caps.
No comments:
Post a Comment