1/25/2019 Document 1625533.

1
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

OBIEE 11g Test-to-Production (T2P) / Clone Procedures Guide (Doc ID 1625533.1)

In this Document

Purpose
Scope
Details

The following sequence was followed to clone using the test-to-production movement scripts.
Steps to perform on the 'source' environment you are cloning from:
Steps to perfom on the 'target' environment you are cloning to:
References

APPLIES TO:

Business Intelligence Suite Enterprise Edition - Version 11.1.1.7.0 to 11.1.1.9.0 [Release 11g]
Business Intelligence Server Enterprise Edition - Version 11.1.1.7.0 to 11.1.1.9.0 [Release 11g]
Information in this document applies to any platform.
This does not apply to 12c. See the 12c Administrator's Guide 'Moving From Test To Production is Carried Out in a
Different Way'

PURPOSE

This document is intended to assist with the test-to-production (T2P) process for an Oracle Business Intelligence
Enterprise Edition (OBIEE) installation. The documentation has various steps that are posted in various sections of the
Fusion Middleware Administration Guide; therefore, the intent of this document is to link all the steps together in a
"cookbook" format to make the process easier to follow and help one to avoid common pitfalls or mistakes. The document
does not intend to cover every scenario or pre-requisite and co-requisite steps such as moving the RCU database.

SCOPE

This document is intended for OBIEE and Fusion Middleware Administrators who have access to the environment and are
able to run scripts providing the appropriate variables.

Note: If you are looking for Oracle Business Intelligence Applications (OBIA) specific information, then please see the link
below which is documented here as as an informational pointer. OBIA T2P steps themselves are outside the scope of this
document.

For OBIA, the recommended approach is: OBIA 11g How to Migrate Configurations and Customizations from Development
to a Test or a Production Environment (Doc ID 1984269.1)

If you do use the T2P process, the separate steps for Oracle Data Integrator (ODI) are documented here: 21.4.10 Moving
Oracle Data Integrator to a Target Environment

DETAILS

The Fusion Middleware Adminstrator Guide contains the steps for completing this process, you will want to familiarize
yourself with these chapters:

19 Cloning Oracle Fusion Middleware

Introduction to Cloning
What You Can Clone
Understanding the Cloning Process
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 1/8
1/25/2019 Document 1625533.1

20 Using the Movement Scripts

21 Moving from a Test to a Production Environment

The high-level steps are:

Task 1, "Move the Database, Middleware Home, and Perform the Initial Configuration"

Task 2, "Patch-Merge the Repository File"

Task 3, "Configure Security in the New Target Environment"

Task 4, "Move the Configuration of the Oracle BI Enterprise Edition Components"

Task 5, "Copy and Scale Out to New Cluster Hosts in the Target Environment"

Task 6, "Enable New Agents and Oracle BI Publisher Scheduled Jobs"

Task 7, "Update Links to External Systems"

Task 8, "(Optional) Move Oracle Business Intelligence Related Applications"

Within Task 1:

To move the database and Middleware home, and perform the initial configuration:

1. Move or create the database, as described in Section 21.3.3.

2. Move Identity Management components, as described in Section 21.4.1.

3. Move the Middleware home and binary files, as described in Section 21.3.4.

4. Move the configuration of the domain and Node Manager, as described in Section 21.3.5.

Note that when you move the configuration of the domain, the pasteConfig script copies the configuration of the
domain, including the Administration Server and Managed Servers.

5. Configure users and groups, as described in Section 21.3.7.

This document will focus on steps 3 - 4 using a default Weblogic embedded LDAP authenticator.

The following sequence was followed to clone using the test-to-production movement scripts.

Steps to perform on the 'source' environment you are cloning from:

1. Set the environment.

The easiest method is to source the existing bi-init.sh environment script.

. $ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup/bi-
init.sh
export MW_HOME=[your middleware home]

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 2/8
1/25/2019 Document 1625533.1

Note: The rest of the soure environment will assume you are working within the same shell and do not need to
set the environment again. If you start a new shell, be sure and set the environment again.

2. Copy the binaries, by executing the copyBinary.sh (for the Middleware Home) script.
Documented here: Section 21.3.4 - review the notes.
$MW_HOME/oracle_common/bin/copyBinary.sh -javaHome $ORACLE_HOME/jdk -archiveLoc
/tmp/mw_bincopy.jar -sourceMWHomeLoc $MW_HOME -invPtrLoc
$MW_HOME/Oracle_BI1/oraInst.loc

Move the jar file to the new host (if cloning to a new host)

3. Before copying the configuration, perform the steps in this technical note first to avoid an error.

Cloning FMW 11g Java Components Fails with Error CLONE-20408: "Detected "Unix Machine" type in machine
configuration" (Doc ID 1302904.1)

4. Copy the configuration.

Tip: You will be running the CopyConfig script a minimum of twice. Once for the domain and once for the
instance. If you have multiple instances, then you could be running the script multiples times for each instance.

Note: The content of the pwd.txt file is a single word which is the password of the Weblogic Server
administrative user (typically weblogic) typed in clear text. Example:

Admin123

The file can be located anyhwere in the disk. In this example, it is placed under $HOME directory.

Documented here:
Domain: http://docs.oracle.com/cd/E28280_01/core.1111/e10105/testprod.htm#ASADM11773
Instance: http://docs.oracle.com/cd/E28280_01/core.1111/e10105/testprod.htm#ASADM11770

Execute: copyConfig.sh (source domain location and middlewware home) script.

For example:
$MW_HOME/oracle_common/bin/copyConfig.sh -javaHome $ORACLE_HOME/jdk -archiveLoc
/tmp/fmwconfig2.jar -sourceDomainLoc $DOMAIN_HOME -sourceMWHomeLoc $MW_HOME -
domainHostName sourcehost.sourcedomain -domainPortNum 7001 -domainAdminUserName
weblogic -domainAdminPasswordFile $HOME/pwd.txt -silent true

Execute: copyConfig.sh (instance)

For example:
$MW_HOME/oracle_common/bin/copyConfig.sh -javaHome $ORACLE_HOME/jdk -archiveLoc
/tmp/inst_config.jar -sourceInstanceHomeLoc $ORACLE_INSTANCE

5. Extract the move plan:

extractmoveplan.sh (from jar files created in created in the copyConfig.sh step above -- fmwconfig2.jar )
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 3/8
1/25/2019 Document 1625533.1

Documented here: http://docs.oracle.com/cd/E28280_01/core.1111/e10105/clone.htm#CIHEHJAD

20.3 Modifying Move Plans

Notes: Do not add, comment, or remove any section of a move plan.

You must generate a move plan using the extractMovePlan script *each time* you create an archive, even if you
have made no changes to the move plan.
If you use a move plan that was created with a different archive, the archive will not be accepted and the
pasteConfig script will fail.
The pasteConfig scripts checks that the move plan and archive match. If they do not, the script returns an error.

Note: The above syntax above is from the documentation and it alludes that you should not modify the move
plan; however, you do have to edit certain portions of it. The documentation is emphasizing not to change any
portion other than what you are documented to edit.

Syntax: http://docs.oracle.com/cd/E28280_01/core.1111/e10105/clone.htm#autoId9
20.2.1.7 extractMovePlan Script

Note: -planDirLoc
This should be an absolute path to an existing and empty directory with write permissions

Edit the move plan -- changed hostnames, ports, updated password file locations
extract move plan from the domain jar file you generated (in this example, fmwconfig2.jar)

For example:
export ORACLE_COMMON=$MW_HOME/oracle_common

$ORACLE_COMMON/bin/extractMovePlan.sh -javaHome $ORACLE_HOME/jdk -archiveLoc

/tmp/fmwconfig2.jar -planDirLoc /tmp/fmwconfig_plan -logDirLoc /tmp

extract move plan from instance jar file you generated (in this example, instance_config.jar)
For example:
$ORACLE_COMMON/bin/extractMovePlan.sh -javaHome $ORACLE_HOME/jdk -archiveLoc
/tmp/inst_config.jar -planDirLoc /tmp/instanceplan -logDirLoc /tmp

6.
Documented here: 20.3 Modifying Move Plans

7. Copy all jar files and moveplans to target host.

From this example:

$MW_HOME/oracle_common/jlib/cloningclient.jar
PasteBinary (.sh /.cmd)
PasteConfig (.sh / .cmd)
fmwconfig2.jar
inst_config.jar
mw_bincopy.jar
moveplan.xml - generated for domain
moveplan.xml - generated for each instance (Tip: keep these in a separately identified directory to avoid
mixing them up, especially if named the same)

Tip: copy bi-init.sh from source to target temp directory and comment out the line .
$ORACLE_INSTANCE/bifoundation/OracleBIApplication/$ORACLE_BI_APPLICATION/setup/user.sh

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 4/8
1/25/2019 Document 1625533.1

This is only used to easily set the environment in the target. It serves no other purpose.

Also, copy the PasteBinary and PasteConfig scripts and $MW_HOME/oracle_common/jlib/cloningclient.jar

Reference: http://docs.oracle.com/cd/E28280_01/core.1111/e10105/clone.htm#autoId1

Steps to perfom on the 'target' environment you are cloning to:

Tips before you begin:

On the target, you need to ensure you have a JDK installed to run the PasteBinary script
export JAVA_HOME=/usr/java
export PATH=$JAVA_HOME/bin:$PATH

Tip: Copy from source or create (as root) the oraInst.loc file for the Oracle Inventory to avoid the following error:

ERROR - CLONE-20264 Default inventory pointer location file is invalid.

SEVERE : Oct 18, 2013 14:18:06 - CAUSE - CLONE-20264 There are two possible causes
for an invalid default invPtrLoc file "/etc/oraInst.loc":

1. The file did not exist.

2. It was a zero size file.

SEVERE : Oct 18, 2013 14:18:06 - ACTION - CLONE-20264 Ensure that the default
oraInst.loc file at "default location" is valid or provide a different, valid
Inventory Pointer file using the -invPtrLoc argument.

Reference: Bug 9470034 : T2P: "/ETC/ORAINST.LOC " NEEDS TO BE CREATED BY SUPER/ROOT USER ON A NEW
SYSTEM

1. Execute the pasteBinary.sh script (from mw_bincopy.jar file created in the copyBinary step above)

For example:
. /tmp/bi-init.sh (to set the environment)

/tmp/pasteBinary.sh -javaHome $JAVA_HOME -archiveLoc /tmp/mw_bincopy.jar -

targetMWHomeLoc /home/oracle/middleware

close the session / shell

2. Execute pasteConfig.sh to configure the domain:

+ open new shell

+ export JAVA_HOME
+ export PATH=$JAVA_HOME/bin:$PATH
+ Change bi-init.sh to reflect new directory structure at target (if different)
+ Comment call to user.sh in bi-init.sh
+ Source bi-init.sh (. /tmp/bi-init.sh)

pasteConfig.sh for domain (new moveplan and jar file from prior step)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 5/8
1/25/2019 Document 1625533.1

TIP: Ensure the move plan is updated to provide the explicit path to the password file for the stated datasource
(i.e - DataSource1)

For example:

From:
<type>DATASOURCE</type>
<configProperty id="DataSource1">
....
...
<configProperty>
<name>Password File</name>
<value/>

to:

<type>DATASOURCE</type>
<configProperty id="DataSource1">
....
...
<configProperty>
<name>Password File</name>
<value>/tmp/pwd.txt</value>

Tip: Ensure all the datasources have a password file configured; else you will incur the error below.

SEVERE : Oct 21, 2013 08:47:43 - ERROR - CLONE-20327 Invalid password file.
SEVERE : Oct 21, 2013 08:47:43 - CAUSE - CLONE-20327 The DataSource1 password file
did not exist or first line did not contain password.
SEVERE : Oct 21, 2013 08:47:43 - ACTION - CLONE-20327 Provide a valid password
file.
SEVERE : Oct 21, 2013 08:47:43 - ERROR - CLONE-20327 Invalid password file.
SEVERE : Oct 21, 2013 08:47:43 - CAUSE - CLONE-20327 The DataSource1 password file
did not exist or first line did not contain password.
SEVERE : Oct 21, 2013 08:47:43 - ACTION - CLONE-20327 Provide a valid password
file.

For example, for every <configProperty id="80ca62c5-0bd5-0000-714b-e31d00000000">

under <type>CONNECTIONPOOLS</type>

INFO : Oct 21, 2013 09:55:38 - CLONE-21203 The RPD ConnectionPool uid:password
password file: "", either does not exist or is zero size.

Update moveplan.xml

From

<configGroup>
<type>CONNECTIONPOOLS</type>
<Description>connection pools</Description>
<configProperty id="80ca62c5-0bd5-0000-714b-e31d00000000">
<name>SampleApp_Lite_Xml</name>

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 6/8
1/25/2019 Document 1625533.1
<configProperty>
<name>password</name>
<value/>
.....
......

To:

<configGroup>
<type>CONNECTIONPOOLS</type>
<Description>connection pools</Description>
<configProperty id="80ca62c5-0bd5-0000-714b-e31d00000000">
<name>SampleApp_Lite_Xml</name>
<configProperty>
<name>password</name>
<value>/tmp/connectionpoolpwd.txt</value>

Tip: Ensure you have localhost first in your /etc/host file; else, the script may not be able to communicate with the
AdminServer even if it is running

See Document 1941911.1 - T2P - ERROR - CLONE-20362 While Running PasteConfig.sh

/tmp/pasteConfig.sh -javaHome $ORACLE_HOME/jdk -archiveLoc /tmp/fmwconfig.jar -

targetDomainLoc /home/oracle/middleware/user_projects/domains/bifoundation_domain -
targetMWHomeLoc /home/oracle/middleware -movePlanLoc /tmp/moveplan.xml -
domainAdminPasswordFile /tmp/pwd.txt -logDirLoc /tmp

tmp]$ /tmp/pasteConfig.sh -javaHome $ORACLE_HOME/jdk -archiveLoc /tmp/fmwconfig.jar -

targetDomainLoc /home/oracle/middleware/user_projects/domains/bifoundation_domain -
targetMWHomeLoc /home/oracle/middleware -movePlanLoc /tmp/moveplan.xml -
domainAdminPasswordFile /tmp/pwd.txt -logDirLoc /tm
This script is not executed from bin directory of Common Oracle home as cloningclient.jar is not available under jlib
directory of Common Oracle home. Execute from bin directory.

/home/oracle/middleware/oracle_common/bin/pasteConfig.sh -javaHome $ORACLE_HOME/jdk

-archiveLoc /tmp/fmwconfig.jar -targetDomainLoc
/home/oracle/middleware/user_projects/domains/bifoundation_domain -targetMWHomeLoc
/home/oracle/middleware -movePlanLoc /tmp/moveplan.xml -domainAdminPasswordFile
/tmp/pwd.txt -logDirLoc /tmp

3. 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.

Set new environment variables (if needed, changed from source or running prior scripts in the shell)

For example:

mv $MW_HOME/instances/instance1 $MW_HOME/instances/instance_old

4. pasteConfig.sh for instance

/home/oracle/middleware/oracle_common/bin/pasteConfig.sh -javaHome $ORACLE_HOME/jdk
-archiveLoc /tmp/inst_config.jar -targetInstanceHomeLoc
/home/oracle/middleware/instances/instance1 -targetInstanceName instance1 -
targetOracleHomeLoc /home/oracle/middleware/Oracle_BI1 -domainHostName

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 7/8
1/25/2019 Document 1625533.1
sourcehost.sourcedomain -domainPortNum 7001 -domainAdminUserName weblogic -
domainAdminPasswordFile /tmp/pwd.txt -logDirLoc /tmp -movePlanLoc /tmp/moveplan.xml

If you are unable to authenticate in the cloned / target environment after the T2P process, then please check this solution:

Authenticating In OBIEE 11g Fails With ' [nQSError: 46164] HTTP Server returned 404 (Not Found) for URL' In The
nqsserver.log Document 1629981.1

REFERENCES

NOTE:1302904.1 - Cloning FMW 11g Java Components Fails with Error CLONE-20408: "Detected "Unix Machine" type in
machine configuration"
NOTE:1953881.1 - OBIEE 11g Test-to-Production (T2P): Is There A Move Plan Property To Configure The Port For Each
Individual BI System Component ?
NOTE:1941911.1 - T2P - ERROR - CLONE-20362 While Running PasteConfig.sh
NOTE:1984269.1 - OBIA 11g How to Migrate Configurations and Customizations from Development to a Test or a
Production Environment
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12xu1xi78k_427&id=1625533.1 8/8