My Oracle Support Banner

EBS 12.2 adcfgclone.pl on AP Tier failed with ERROR: Script failed, exit code 255 when creating new wls domain (Doc ID 1986208.1)

Last updated on JUNE 07, 2021

Applies to:

Oracle E-Business Suite Technology Stack - Version 12.2 to 12.2.4 [Release 12.2]
Oracle Applications Manager - Version 12.2 to 12.2.4 [Release 12.2Cloud]
Information in this document applies to any platform.

Symptoms

On: 12.2 version, Rapidclone

When attempting to clone, the following error occurs.

ERROR

Creating new WLS domain.
Running /app/xxx/fs1/FMW_Home/oracle_common/bin/pasteConfig.sh -javaHome /app/xxx/fs1/EBSapps/comn/clone/FMW/t2pjdk -al /app/xxx/fs1/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /app/xxx/fs1/FMW_Home/user_projects/domains/EBS_domain_xxx -tmw /app/xxx/fs1/FMW_Home -mpl /app/xxx/fs1/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /app/xxx/fs1/inst/apps/xxx_xxx/admin/log/clone/wlsT2PApply -silent true -domainAdminPassword /app/xxx/fs1/EBSapps/comn/clone/FMW/tempinfo.txt
Script Executed in 4712761 milliseconds, returning status 255
Script failed, exit code 255

 

CLONE2015-03-04_xx-xx-xxPM.error

SEVERE : Feb 20, 2015 3:48:12 PM - ERROR - CLONE-20362  Connection to AdminServer failed.
SEVERE : Feb 20, 2015 3:48:12 PM - CAUSE - CLONE-20362  AdminServer start failed. Make sure that AdminServer parameters specified in the move plan are correct.
SEVERE : Feb 20, 2015 3:48:12 PM - ACTION - CLONE-20362  Check the AdminServer logs.
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:262)
at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:61)
at oracle.as.clone.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:188)
at oracle.as.clone.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:69)
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:238)
at oracle.as.clone.client.CloningClient.main(CloningClient.java:115)
SEVERE : Feb 20, 2015 3:48:12 PM - ERROR - CLONE-20237   Restoring the sourceid "J2EECOMPONENT@EBS_domain" has failed.
SEVERE : Feb 20, 2015 3:48:12 PM - CAUSE - CLONE-20237   An internal operation failed.
SEVERE : Feb 20, 2015 3:48:12 PM - ACTION - CLONE-20237   Check the clone log and error file for more details.

 

CLONE2015-03-04_xx-xx-xxPM.log

FINE : Feb 20, 2015 3:48:12 PM - [GenericPasteConfigSteps:executeOnlineScripts] AdminServer is down. Cannot execute online config changes.
FINE : Feb 20, 2015 3:48:12 PM - CLONE-22264   Time taken to restore sourceid "J2EECOMPONENT@EBS_domain_gouf" is "4,465,671" milliseconds.
FINE : Feb 20, 2015 3:48:12 PM - [ApplyCloneRequest:applyArchive] One cloner object was not executed properly, so rest were not executed.
INFO : Feb 20, 2015 3:48:12 PM - CLONE-21037   Time taken to restore all cloners from archive was "4,465" seconds.
INFO : Feb 20, 2015 3:48:12 PM - CLONE-21006   Total time taken by T2P process was 4,465 seconds.

Changes

 Run adcfgclone on AP Tier.

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.