Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 214 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Error during 'pasteConfig.sh' (instance) - OBIEE T2P Cloning
Hi -
I am following OBIEE 11g Test-to-Production (T2P) / Clone Procedures Guide (Doc ID 1625533.1). I am nearly finished with the steps, but have hit an error on the target. Here is the step, taken from the MOS note:
Here is the output from the command line:
INFO : Jul 19, 2017 11:26:46 - CLONE-21276
---------------------------------------------------
T2P Summary Begin
---------------------------------------------------
Error Message :1
Jul 19, 2017 11:26:46 - ERROR - CLONE-20312 Oracle instance name is invalid.
Jul 19, 2017 11:26:46 - CAUSE - CLONE-20312 The instance name is already registered with domain.
Jul 19, 2017 11:26:46 - ACTION - CLONE-20312 Provide an instance name which is not registered with domain.
Error Message :2
Jul 19, 2017 11:26:46 - ERROR - CLONE-20222 Parameters validation has failed.
Jul 19, 2017 11:26:46 - CAUSE - CLONE-20222 Primary parameters validation for "pasteConfig" failed.
Jul 19, 2017 11:26:46 - ACTION - CLONE-20222 Check the clone log and error file and provide correct value.
Error Message 
Jul 19, 2017 11:26:46 - ERROR - CLONE-20237 Restoring the sourceid "asinstance@obiprd" has failed.
Jul 19, 2017 11:26:46 - CAUSE - CLONE-20237 An internal operation failed.
Jul 19, 2017 11:26:46 - ACTION - CLONE-20237 Check the clone log for more details.
---------------------------------------------------
T2P Summary End
---------------------------------------------------
SEVERE : Jul 19, 2017 11:26:46 - ERROR - CLONE-20218 Cloning is not successful.
SEVERE : Jul 19, 2017 11:26:46 - CAUSE - CLONE-20218 An internal operation failed.
SEVERE : Jul 19, 2017 11:26:46 - ACTION - CLONE-20218 Provide the clone log and error file for investigation.
Here is the actual command I ran (full path is substitued with '{path}'):
./pasteConfig.sh -javaHome {path}/jdk/jre -archiveLoc {path}/inst_config.jar -targetInstanceHomeLoc {path}/obiprd -targetInstanceName obiprd
-targetOracleHomeLoc {path}/Oracle_BI1 -domainHostName {source_hotsname_domain} -domainPortNum 7001 -domainAdminUserName weblogic
-domainAdminPasswordFile {path}/clone_obiadmin.txt -logDirLoc {path}/clonetemp -movePlanLoc {path}/moveplan.xml
My understanding, based on the product documentation, is that the instance name should be the same for target and source.
https://docs.oracle.com/middleware/11119/core/ASADM/testprod.htm#BABGJGCF
Any ideas why this is happening?
OBIEE 11.1.1.9.x
Regards,
Charles
Answers
-
The same Doc you mention has a step under
"Steps to perfom on the 'target' environment you are cloning to:"
which says
"Move / rename the instances directory to old_instance. The prior scrips created the instance directory, but it is nothing other than a placeholder / shell. If you do not rename it, then next script will fail if it detects the directory is there."
have you done it?
0 -
Hi -
Thank for the update. I did perform that step - I renamed that directory to 'instance_old'.
ls -l
total 8
drwxr-x--T 6 applmgr applmgr 4096 May 31 11:31 instance_old
Regards,
Charles
0 -
I think I may have figured this out. In my original post, it shows this:
The above snippet was taken directly from the MOS note. But, I believe that the 'domainHostName' parameter should not contain the source host information. After changing this to the target host information, the instance pasteconfig completed successfully.
I looked through the product documentation on this, and found that it does not call out the source host like the MOS note:
https://docs.oracle.com/middleware/11119/core/ASADM/testprod.htm#BABGJGCF
https://docs.oracle.com/cd/E28280_01/core.1111/e10105/testprod.htm#ASADM339
Regards,
Charles
0