T2P PasteConfig fails at Admin server startup, 'FMWT2PPasteConfigException'

(Doc ID 2134150.1)

Last updated on OCTOBER 24, 2017

Applies to:

Oracle BAM (Business Activity Monitoring) - Version and later
Oracle SOA Suite - Version and later
Information in this document applies to any platform.


When attempting to move Test to Production using the T2P scripts, the pasteConfig script fails while starting the Admin server with the following error:

SEVERE : Apr 21, 2016 4:19:13 PM - ERROR - CLONE-20362 Connection to AdminServer failed.
SEVERE : Apr 21, 2016 4:19:13 PM - CAUSE - CLONE-20362 AdminServer start failed. Make sure that AdminServer parameters specified in the moveplan are correct.
SEVERE : Apr 21, 2016 4:19:13 PM - ACTION - CLONE-20362 Check the AdminServer logs.
SEVERE : Apr 21, 2016 4:19:13 PM - SEVERE - CLONE-20937 "pasteConfig" operation of J2EE domain failed. Check clone log and error files for more details.
SEVERE : Apr 21, 2016 4:19:13 PM - ERROR - CLONE-20218 Cloning is not successful.
SEVERE : Apr 21, 2016 4:19:13 PM - CAUSE - CLONE-20218 An internal operation failed.
SEVERE : Apr 21, 2016 4:19:13 PM - ACTION - CLONE-20218 Check clone log and error file for detailed information.
oracle.as.t2p.sdk.model.exception.FMWT2PPasteConfigException: Paste config in online mode failed.
at oracle.as.t2p.framework.cloner.config.j2ee.J2EEComponentApplyCloner.doClone(J2EEComponentApplyCloner.java:340)
at oracle.as.t2p.framework.cloner.Cloner.doFinalClone(Cloner.java:65)
at oracle.as.t2p.framework.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:127)
at oracle.as.t2p.framework.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:62)
at oracle.as.t2p.framework.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:131)
at oracle.as.t2p.framework.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:114)
at oracle.as.t2p.framework.client.CloningClient.executeT2PCommand(CloningClient.java:230)
at oracle.as.t2p.framework.client.CloningClient.main(CloningClient.java:106)

 When attempting to start the Admin server manually the following error is generated:

<Apr 21, 2016 8:36:40 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing failure in config.xml: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.management.configuration.MigratableTargetMBeanImpl@30031ab2([soa12_domain]/MigratableTargets[bam_server1 (migratable)])".>
<Apr 21, 2016 8:36:40 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms