To BottomTo Bottom
In this Document
Symptoms
Cause
Solution
References

APPLIES TO:

Oracle Applications Manager - Version 12.2 and later
Information in this document applies to any platform.

SYMPTOMS

E-Business Suite 12.2 Applications Manager, Rapidclone Related issues



When creating to clone E-Business Suite adcfgclone.pl fails with the following error:

WARNING : Nov 20, 2016 01:00:05 - WARNING - CLONE-20454 Execution of wlst script is not successful.
WARNING : Nov 20, 2016 01:00:05 - CAUSE - CLONE-20454 An internal operation failed while executing /fs1/inst/apps/<CONTEXT_Name>/logs/appl/rgf/TXK/CLONINGCLIENT573700/tmp14795960.py wlst script.
WARNING : Nov 20, 2016 01:00:05 - ACTION - CLONE-20454 Check clone log and error file for detailed information.
SEVERE : Nov 20, 2016 01:00:05 - ERROR - CLONE-20365 Error in executing WebLogic script while updating server, cluster , datasource , machine, and authenticator in packed domain template.
SEVERE : Nov 20, 2016 01:00:05 - CAUSE - CLONE-20365 The possible causes were :
 1. The values specified in the moveplan were not correct.
2. Some "READ_ONLY" properties in the moveplan were modified.
3. Target Middleware Home was not valid.
4. Some internal operation failed.
SEVERE : Nov 20, 2016 01:00:05 - ACTION - CLONE-20365 Check the T2P logs for more details.
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: Paste config in offline mode failed.
at oracle.as.clone.cloner.component.J2EEComponentApplyCloner.doClone(J2EEComponentApplyCloner.java:264)
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 : Nov 20, 2016 01:00:05 - SEVERE - CLONE-20937 "pasteConfig" operation of J2EE domain failed. Check clone log and error files for more details.
SEVERE : Nov 20, 2016 01:00:05 - ERROR - CLONE-20237 Restoring the sourceid "J2EECOMPONENT@EBS" has failed.
SEVERE : Nov 20, 2016 01:00:05 - CAUSE - CLONE-20237 An internal operation failed.
SEVERE : Nov 20, 2016 01:00:05 - ACTION - CLONE-20237 Check the clone log for more details.
SEVERE : Nov 20, 2016 01:00:05 - ERROR - CLONE-20218 Cloning is not successful.
SEVERE : Nov 20, 2016 01:00:05 - CAUSE - CLONE-20218 An internal operation failed.
SEVERE : Nov 20, 2016 01:00:05 - ACTION - CLONE-20218 Provide the clone log and error file for investigation.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. run adcfgclone.pl

CAUSE

File moveplan.xml on the SOURCE instance contains 2 oacore managed servers.
Per below the oacore_server2 port value is not within the correct port pool range.
Also in certain cases the port may already be assigned to another tier on the source or target:

For example:
oacore_server1 : 7001
oacore_server2 : 7004

SOLUTION

As discussed in Bug 22840524 , to resolve the issue test the following steps in a development TARGET instance and then migrate accordingly:

1. Follow Note 1383621.1 - Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1) to cleanup the target instance.
2. Run adpreclone. This should recreate the cloning directory, including generating a new moveplan.
3. Rerun adcfgclone.pl by giving a correct port pool value with a higher range than SOURCE instance.


REFERENCES

Comments

Post a Comment

Popular posts from this blog

12c: emctl start agent Fails or Hangs or Timeout or Connection Refused

EM 12c: emctl start agent Fails or Hangs or Timeout or Connection Refused Due to PKCS11 'security.pkcs11.P11SecureRandom.implNextBytes' Reported in Thread Dump 'Hang detected' (Doc ID 1427773.1) APPLIES TO: Enterprise Manager Base Platform - Version 12.1.0.1.0 to 12.1.0.2.0 [Release 12.1] Oracle Solaris on SPARC (64-bit) SYMPTOMS $AGENT_INST/bin/emctl start agent fails to start or gets hung Oracle Enterprise Manager Cloud Control 12c Release 2 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. Starting agent ........................................................................................... OR $AGENT_INST/bin/emctl start agent fails with following error Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. Agent status could not be determined. Check the agent process Consult the log files in: /oracle/product/Agent_home/agent_inst/sysman/log $AGENT_INST/bin/emctl
Read more

11G ODI Temp usage

OBIA 11g ODI Temporary Table Consume Large Tablespace, How To Purge These Tables ? (Doc ID 1572972.1) To BottomTo Bottom APPLIES TO: Business Intelligence Applications Consumer - Version 11.1.1.7.0 and later Information in this document applies to any platform. GOAL There are some temporary tables consuming huge amounts of space in the DW_DATA tablespace. The table's name listed as below: C$_<Session ID number>.1GB How can we purge these data? and when to purge these data ? SOLUTION These tables are automatically purged once the interface is run successfully. If there are failed sessions, then this table is not dropped immediately. This helps in debugging the failed sessions. At the end of the load plan which  is generated using Load Plan Generator (LPG), we have a step called Finalize Batch Load , under which there is a step called Clean Work and Flow Tables. This automatically drops any such stale tables that are older than 30 days. You can reduce this default of 30 day
Read more