ERROR - CLONE-20372 Server port validation failed
This error is reported in logs when adcfgclone.pl run for a R12.2.5 appsTier where many instances are running on same server.
It seems the ports reported are using by some other instance in the same server. Searching on support.oracle.com I found three articles:
EBS 12.2.2.4 RAPID CLONE FAILS WITH ERROR - CLONE-20372 SERVER PORT VALIDATION(Bug ID 20147454)
12.2: N->1 CLONING TO SAME APPS TIER FAILING DUE TO PORT CONFLICT(Bug ID 20389864)
FS_CLONE IS NOT ABLE TO COMPLETE FOR MULTI-NODE SETUP(Bug ID 18460148)
The situation described in the first two bugs is same. The articles reference each other but don't provide any solution.
Logically thinking, adcfgclone.pl is picking this up from source configuration that is in $COMMON_TOP/clone directory. So we did grep on subdirectories of $COMMON_TOP/clone:
cd $COMMON_TOP/clone
find . -type f -print | xargs grep 7214
7214 is the port that failed validation as per logfile.
It is present in
CTXORIG.xml and
FMW/ohs/moveplan.xml
FMW/wls/moveplan.xml
We tried changing the port numbers in CTXORIG.xml and re-tried adcfgclone.pl and it failed again.
So we changed the port numbers of the ports that failed validation in
$COMMON_TOP/clone/FMW/ohs/moveplan.xml and
$COMMON_TOP/clone/FMW/wls/moveplan.xml
cd $FMW_HOME
find . -name detachHome.sh |grep -v Template
The above command returns the detachHome.sh scripts for all the ORACLE_HOMEs inside FMW_HOME. Executed this to detach all of them.
Removed the FMW_HOME directory
Re-executed
adcfgclone.pl appsTier
It succeeded this time. Till we get a patch for this bug, we will continue to use this workaround to complete clones.
SEVERE : Aug 7, 2017 16:36:36 - ERROR - CLONE-20372 Server port validation failed.
SEVERE : Aug 7, 2017 16:36:36 - CAUSE - CLONE-20372 Possible causes were :Ports of following servers - oacore_server3(7214) - were not available.
SEVERE : Aug 7, 2017 16:36:36 - ACTION - CLONE-20372 Provide valid free ports or if those servers are targeted to non admin host, then use temporary port range mechanism.
java.lang.Exception: Error in validating "SERVER_CONFIG" parameters in "moveplan".
at oracle.as.clone.cloner.component.j2ee.util.J2EEGenericValidationUtil.validateServerConfig(J2EEGenericValidationUtil.java:218)
at oracle.as.clone.cloner.component.j2ee.config.GenericPasteConfigSteps.getServerConfig(GenericPasteConfigSteps.java:922)
at oracle.as.clone.cloner.component.j2ee.config.GenericPasteConfigSteps.executeGenericPasteConfig(GenericPasteConfigSteps.java:385)
at oracle.as.clone.cloner.component.J2EEComponentApplyCloner.doClone(J2EEComponentApplyCloner.java:259)
at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:63)
at oracle.as.clone.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:198)
at oracle.as.clone.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:77)
at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:131)
at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:114)
at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)
at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct.
at oracle.as.clone.cloner.component.J2EEComponentApplyCloner.doClone(J2EEComponentApplyCloner.java:314)
at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:63)
at oracle.as.clone.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:198)
at oracle.as.clone.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:77)
at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:131)
at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:114)
at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)
at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)
SEVERE : Aug 7, 2017 16:36:36 - SEVERE - CLONE-20937 "pasteConfig" operation of J2EE domain failed. Check clone log and error files for more details.
SEVERE : Aug 7, 2017 16:36:36 - ERROR - CLONE-20237 Restoring the sourceid "J2EECOMPONENT@EBS_domain_FLRPRD" has failed.
SEVERE : Aug 7, 2017 16:36:36 - CAUSE - CLONE-20237 An internal operation failed.
SEVERE : Aug 7, 2017 16:36:36 - ACTION - CLONE-20237 Check the clone log for more details.
SEVERE : Aug 7, 2017 16:36:36 - ERROR - CLONE-20218 Cloning is not successful.
SEVERE : Aug 7, 2017 16:36:36 - CAUSE - CLONE-20218 An internal operation failed.
SEVERE : Aug 7, 2017 16:36:36 - ACTION - CLONE-20218 Provide the clone log and error file for investigation.
It seems the ports reported are using by some other instance in the same server. Searching on support.oracle.com I found three articles:
EBS 12.2.2.4 RAPID CLONE FAILS WITH ERROR - CLONE-20372 SERVER PORT VALIDATION(Bug ID 20147454)
12.2: N->1 CLONING TO SAME APPS TIER FAILING DUE TO PORT CONFLICT(Bug ID 20389864)
FS_CLONE IS NOT ABLE TO COMPLETE FOR MULTI-NODE SETUP(Bug ID 18460148)
The situation described in the first two bugs is same. The articles reference each other but don't provide any solution.
Logically thinking, adcfgclone.pl is picking this up from source configuration that is in $COMMON_TOP/clone directory. So we did grep on subdirectories of $COMMON_TOP/clone:
cd $COMMON_TOP/clone
find . -type f -print | xargs grep 7214
7214 is the port that failed validation as per logfile.
It is present in
CTXORIG.xml and
FMW/ohs/moveplan.xml
FMW/wls/moveplan.xml
We tried changing the port numbers in CTXORIG.xml and re-tried adcfgclone.pl and it failed again.
So we changed the port numbers of the ports that failed validation in
$COMMON_TOP/clone/FMW/ohs/moveplan.xml and
$COMMON_TOP/clone/FMW/wls/moveplan.xml
cd $FMW_HOME
find . -name detachHome.sh |grep -v Template
The above command returns the detachHome.sh scripts for all the ORACLE_HOMEs inside FMW_HOME. Executed this to detach all of them.
Removed the FMW_HOME directory
Re-executed
adcfgclone.pl appsTier
It succeeded this time. Till we get a patch for this bug, we will continue to use this workaround to complete clones.
Happy EBS Learning !!