ERROR: Failed to configure the target system – Failed to enable EBS_LOGON trigger
The clone procedure for EBS R12.2 is quite different when compared with EBS R12.1. This post covers very generic issues we may encounter while configuring the target server as a part of clone Process.
ERROR : 1
Checking the port pool 6
done: Port Pool 6 is free
Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst
The new APPL_TOP context file has been created :
/u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml
Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811105848.log for details.
FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check…
ERROR: Run file system configuration has failed
Check the logfile /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111059.log
ERROR: Failed to configure the target system,
please check the logfile in : /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone
Enter the APPS password : Enter the APPS password : Error while executing /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/alter_ebs_logon_trigger.sql
Failed to enable EBS_LOGON trigger
When we check the logfile its mentioning FMW_Home already exists.
[root@erpnode3 run]# tail -100f /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111059.log
#############################################################
Started RCloneApplyAppstier at Thu Aug 11 10:59:37 AST 2016
Version:
RCloneApplyAppstier.java : 120.0.12020000.4
#############################################################
Found the directory : /u01/appl_PROD/PROD/fs1/FMW_Home
Exiting cloning as FMW Home already exists..
Solution:
We must remove the directory FMW_Home. If the directory is empty also we should remove it, else rapidclone will exit out with status Error.
ERROR : 2
The error message is almost identical to the previous error in the clone configuration output.
Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst
The new APPL_TOP context file has been created :
/u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml
Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811110821.log for details.
FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check…
Configuring: Run file system….
LogFile located at /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111108.log
ERROR: Failed to configure the target system,
please check the logfile in : /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone
Error while executing /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/alter_ebs_logon_trigger.sql
Failed to enable EBS_LOGON trigger
[applerp@erpnode3 bin]$
But this time the message in error log is different:
[root@erpnode3 inst]# more /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/RCloneApplyAppstier_08111108.log
#############################################################
Started RCloneApplyAppstier at Thu Aug 11 11:08:36 AST 2016
Version:
RCloneApplyAppstier.java : 120.0.12020000.4
#############################################################
START: Calling ApplyAppsTier…
START: Creating the FMW Home from ApplyAppsTier
FMW JDK version in use: 1.7.0_85
START: Creating FMW Home.
Running /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/pasteBinary.sh -javaHome /u01/appl_PROD/PROD/fs1/EBSapps/comn/util/jdk64 -al /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -tl /
u01/appl_PROD/PROD/fs1/FMW_Home -invPtrLoc /etc/oraInst.loc -ldl /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/log/clone/run/fmwT2PApply -silent true -debug true -executeSysPrereqs false
Script Executed in 7558 milliseconds, returning status 255
ERROR: Script failed, exit code 255
[root@erpnode3 inst]#
Solution:
usually we will recieve this error when there are no proper privileges granted on oraInventory (or) the oraInventory is not empty. To avoid this issue we should verify “oraInventory” directory has appropriate privileges and its empty.
[root@erpnode3 u01]# mkdir -p /u01/ora_prod/oraInventory
[root@erpnode3 u01]# chmod -R 755 /u01/ora_prod/oraInventory
[root@erpnode3 u01]# chown -R applerp:dbaerp /u01/ora_prod/oraInventory
[root@erpnode3 u01]# cat /etc/oraInst.loc
inventory_loc=/u01/ora_prod/oraInventory
inst_group=dba
[root@erpnode3 u01]#
During the R12.2 cloning process adcfgclone fails with below error message:
ERROR : 3
Below Oracle Homes are already registered in the global inventory:
/u01/oracle/R122/fs1/FMW_Home/oracle_common
/u01/oracle/R122/fs1/FMW_Home/webtier
/u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1
Solution:
Make sure that the above Oracle Homes are unregistered from the global inventory. we should always clean the oraInventory directory by using the following commands.
cd $ORACLE_HOME/oui/bin (/u01/oracle/R122/fs1/EBSapps/10.1.2/oui/bin)
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1”}
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/oracle_common”}
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/webtier”}
Then restart the adcfgclone.pl appsTier
https://www.toadworld.com/platforms/oracle/b/weblog/archive/2016/08/11/rror-failed-to-configure-the-target-system-failed-to-enable-ebs-logon-trigger
