OBIEE Cloning

Cloning the OBIEE 11g database migration to

a new host

Ashok Thiyagarajan
ADVANS | MARLBOROUGH, MA AND CHENNAI, INDIA | WWW.ADVANSIT.COM

Table of Contents
COMPONENTS:.......................................................................................................................................... 3
TNSNAME: ................................................................................................................................................. 4
NODE MANAGER LISTEN ADDRESS: .......................................................................................................... 6
MACHINE NAME: ...................................................................................................................................... 7
VERIFIY MACHINE AND SERVERS: ............................................................................................................. 9
FILE CHANGES: ........................................................................................................................................ 10
nodemanager.properties ........................................................................................................................ 10
biee-domain.xml: .................................................................................................................................... 10
topology.xml: .......................................................................................................................................... 11
startManagedWebLogic.sh ..................................................................................................................... 11
stopManagedWebLogic.sh...................................................................................................................... 12
Config.xml: .............................................................................................................................................. 12
SCHEDULER CONNECTION SETTINGS IN ENTERPRISE MANAGER:.......................................................... 13
STARTING BI_SERVER1: ........................................................................................................................... 14
Systems MBean Browser: ....................................................................................................................... 15
Data Sources: .......................................................................................................................................... 17
STOP OBIEE SERVICES: ............................................................................................................................ 18
1. Shutdown OPMN Components ........................................................................................................... 18
2. Shutdown Managed Server ................................................................................................................ 18
3. Shutdown Node Manager ................................................................................................................... 19
4. Shutdown Admin Server ..................................................................................................................... 19
START OBIEE SERVICES:........................................................................................................................... 19
1. Start Admin Server .............................................................................................................................. 19
2. StartNode Manager ............................................................................................................................ 19
3. Start Managed Server ......................................................................................................................... 20
4. Startup OPMN Components ............................................................................................................... 20
RESTORING CATALAOG: .......................................................................................................................... 21
ARCHIVE: ................................................................................................................................................. 22

2
UNARCHIVE: ............................................................................................................................................ 23
UNARCHIVE OPTIONS: ............................................................................................................................ 24
Inherit pasted item: ................................................................................................................................ 24
Preserve pasted item: ............................................................................................................................. 24
Create pasted item: ................................................................................................................................ 24
None:....................................................................................................................................................... 24
Old: .......................................................................................................................................................... 24
All: ........................................................................................................................................................... 24
CONNECTION POOL: ............................................................................................................................... 24
SIGNING IN ERROR: ................................................................................................................................. 25

Obie.old.com to Obie.new.com
This document provides the information about the Migration of hostname, Service name and
port.
SYSTEM 1

SYSTEM 2

OBIEE
Application
Installed System

DATABASE
SCHEMAS
(dev_biplatform
& mds_own)

SYSTEM 3

OBIEE Application
Configuration without
Installation obie.new.com
from system 1 and
restoring Database
Schemas from system 2

COMPONENTS:
Listed below are the components at a high level in 11g, which require changes whenever the
host name changes.
1. Admin Server
2. Managed Server
3. Node Manager
4. RCU Schemas Connections
5. System Components

6. Hardcoded Host name entries in Repository, JDBC Connections etc

7. RCU Database Listener
Machine named obie.old.com which is where BI EE 11g is installed and currently running. To
demonstrate the host name change, i am going to rename the server to obie.new.com as
shown below.
In linux, you will have to update the hosts file to reflect the host name change. After the change
restart the machine so that OS picks up the change. The next step is to ensure that, if you have
the RCU database on the same machine, the listener is properly listening on the correct host
name. So make the following changes to listener.ora and tnsnames.ora.

TNSNAME:
In the below path the following tnsnames.ora file should be changed to our Hostname, port
number and service name.
/u01/app/Middleware/Oracle_BI1/network/admin
OBIEEDEV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.1.1)(PORT = 1520))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = obie.new.com)
)
)
After the above changes, restart the listener and ensure that you are able to connect to the
database through the tnsnames entry (This post assumes a single instance Oracle database.
Also this post will not cover the changes to get the database control working).
After getting the database connectivity to work, the next step is to start up the Admin Server.
Unlike Managed Server, Admin Server will run even with a wrong host name.
So, start up the Admin Server by running startWeblogic.sh script in
Middleware_Home}\user_projects\domains\bifoundation_domain folder.
Once the Admin Server is started, navigate to the Weblogic Console. Under
the bifoundation_domain > Environment link click on the Machines.

After Locking & Editing the Admin Console, add a new machine with the new host
name obie.new.com as shown below.

So, you should see both the old host name and the new host name under the machines list.

Activate the Changes.

NODE MANAGER LISTEN ADDRESS:

Now, in the same Machines page, click on the obie.old.com host name. Navigate to the Node
Manager tab. In the Listen Address, enter the new host name obie.new.com

Save & Activate the changes.

MACHINE NAME:
Now, under bifoundation_domain > Environments link, click on the Servers link.

Click on the bi_server1 managed server and change the machine name to obie.new.com from
the older host name (This will get activated only after you Lock & Edit the Admin Console) in
the Configuration > General tab.

Save & Activate the Changes. Now you can notice that the Managed Server will be pointing to
the new Host name as shown below

VERIFIY MACHINE AND SERVERS:

Now go the Machine>obie.new.com>servers
Click on the server tab and ensure that both the Admin server and bi_server are associated with
the newly created obie.new.com Machine name if not add both the servers.

We will still not be able to start the Managed Server as the Node Manager will be pointing to
the older host name. To overcome this, we need to first remove the existing Node Manager
Service by running the following script by which is available at
/u01/app/Middleware/wlserver_10.3/server/bin.
./setWLSEnv.sh
After running this script you will receive a message the your environment is set.
Before doing any changes take a backup of all the files which you are editing.
The following files must be changed in order to take effect of new changes.

10

FILE CHANGES:
nodemanager.properties
This file is present in folder /u01/app/Middleware/wlserver_10.3/common/nodemanager

This will install the Node Manager Service with the updated host name. Start the Node
Manager Service manually now.

biee-domain.xml:
For System Components to use the new host name, we need to basically update the bieedomain.xml file under
/u01/app/Middleware/user_projects/domains/bifoundation_domain/config/fmwconfig.
There will be 2 entries using the older host name. Update both of them to the new host
name obie.new.com

11

topology.xml:
Also, the communication (only in Enterprise Manager for listing the status of components)
between opmnctl and the java components happen through a file called Topology.xml.
This file will be present under
/u01/app/Middleware/user_projects/domains/bifoundation_domain/opmn.
Update the older host name in this file to the new host name obie.new.com

Go to below mentioned folder

/u01/app/Middleware/user_projects/domains/bifoundation_domain/bin
startManagedWebLogic.sh, stopManagedWebLogic.sh and ensure whether the ADMIN URL
and echo parameters has the new machine name obie.new.com:7001 else change accordingly.

startManagedWebLogic.sh

12

stopManagedWebLogic.sh

Config.xml:
Ensure the machine name and host name has been changed in the below config.xml file
/u01/app/Middleware/user_projects/domains/bifoundation_domain/config

13

SCHEDULER CONNECTION SETTINGS IN ENTERPRISE MANAGER:

1. Go to > EM> Business Application> Core application > Deployment > Scheduler >Lock &
Edit Configuration
2. Change the Connection setting as mentioned below.
OBIEEDEV =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.1.1.1)(PORT = 1520))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = obie.new.com)
)
)
3. Select > Activate Changes

14

STARTING BI_SERVER1:
After starting the service, navigate back to the Admin Console and click
on bifoundation_domain. From the Control tab, start thebi_server1 managed server.

Ensure that the Managed Server goes into RUNNING state before continuing on to the next
step.

15

Systems MBean Browser:

Now we have the Managed Server completely running on the new host name. But we still have
the Admin Server running on the older host name we should change that as well. We cannot
change it directly from the console (makes sense as the console itself is accessible only after we
started the script which is tied to the hostname). To update the host name of the Admin Server,
lets login to the Oracle BI Enterprise Manager (http://localhost:7001/em)
Expand the Weblogic Domain > bifoundation_domain and right click on Admin Server to
navigate to the Systems MBean browser.

16

In this update the Machine Name attribute to the new host name

Apply the changes.

17

Data Sources:
Now, we have the Admin Server pointing to the new host name (we have to restart for changes
to be applicable we can do that in the end). We still have the connections to RCU schemas
from BI EE pointing to the older host name. To update this, login to Admin Console.
Expand Services > JDBC and click on the Data Sources link.

Click on each data source(bip_datasource, mds-owsm & rtd_datasource) and update the
database connection URL (Connection Pool tab) to point to the new host name obie.new.com

18

We still have 2 more changes pending, System Components & other static files using the older
host name like RPD, start scripts etc.

After all these changes, restart your system, all the components will start normally but with the
new host name.

STOP OBIEE SERVICES:

1. Shutdown OPMN Components
Oracle Process Manager should be used to shutdown all system components.
Go to> /u01/app/Middleware/instances/instance1/bin
cd /u01/app/Middleware/instances/instance1/bin
./opmnctl stopall

2. Shutdown Managed Server

Go to > /u01/app/Middleware/user_projects/domains/bifoundation_domain/bin
cd /u01/app/Middleware/user_projects/domains/bifoundation_domain/bin
./stopManagedWebLogic.sh bi_server1 t3://obie.new.com:7001 weblogic weblogic

19

Verify that the Managed Server has shut down completely with ps -ef | grep bi_server1.

3. Shutdown Node Manager

There should be a single Node Manager for the machine. Shut it down with the command
below.
ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15
kill -9 ####

4. Shutdown Admin Server

There should be a single Node Manager for the machine. Shut it down with the command
below.
Go to> /u01/app/Middleware/user_projects/domains/bifoundation_domain/bin
./stopWebLogic.sh weblogic weblogic t3://obie.new.com:7001
Verify that the Managed Server has shut down completely with ps -ef | grep AdminServer.

START OBIEE SERVICES:

1. Start Admin Server
cd /u01pt/app/Middleware/user_projects/domains/bifoundation_domain/bin
weblogic ./startWebLogic.sh -Dweblogic.management.username= weblogic
Dweblogic.management.password=weblogic
tail -f weblogic.out
Weblogic.out is log file which logs the running status
After issuing the start command we tail the log until we see the message below, indicating that
the server has started successfully.
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

2. StartNode Manager
cd /u01/app/Middleware/wlserver_10.3/server/bin
nodemanager ./startNodeManager.sh > nodemanager.out &
tail -f nodemanager.out
nodemanager.out is log file which logs the running status

20

After issuing the start command we tail the log until we see the message below, indicating that
the server has started successfully.
<Info> <Secure socket listener started on port ####>

3. Start Managed Server

By default there should be one managed server, bi_server1 that we will start up. At this point
you should start any other Managed Servers in this WebLogic domain.
cd /u01/app/Middleware/wlserver_10.3/common/bin
./commEnv.sh
cd / u01/app/Middleware /user_projects/domains/bifoundation_domain/bin
./setDomainEnv.sh
weblogic ./startManagedWebLogic.sh bi_server1 t3://machine:7001 > bis1_startup.log &
tail weblogic.out
Weblogic.out is log file which logs the running status
After issuing the start command we tail the log until we see the message below, indicating that
the server has started successfully. Server started in RUNNING mode

4. Startup OPMN Components

Oracle Process Manager should be used to shutdown all system components.
cd /u01/app/Middleware/instances/instance1/bin
./opmnctl startall
./opmnctl status
Now you can login to console and verify the status of the running servers.

21

Now you can login to analytics and login with your username and password and verify the host
name.

RESTORING CATALAOG:
Catalog restore can be done in two ways
1. Using Catalog Manager
2. Using Catalog Tasks in Presentation Services.
Archive a Presentation Catalog (that is, the catalog root folder) or an individual catalog folder,
all objects in the folder and the folder's subfolders are saved in single compressed file.
Unarchive a Presentation Catalog or an individual catalog folder, the archive file is
uncompressed and all objects in the folder and the folder's subfolders are then stored in the
current offline catalog. Existing folders that have the same names as folders being unarchived
are overwritten.
Timestamps that are assigned to the item and folder that you are archiving, select the Keep
Timestamp checkbox.
If you do not select this option, the archiving process will not include timestamp information.
Upon unarchiving, the system will apply a timestamp indicating the time at which the item or
folder is unarchived.
Permissions that are assigned to each item or folder, select the Keep Permissions checkbox.
If you do not select this option, the archiving process will not include any permissions. Upon
unarchiving, the system will assign the parent folder's permissions to all of the items and
folders.

22

CATALOG MIGRATION:
ARCHIVE:
Go to> obie.old.com:9704/analytics and login with your USERNAME and PASSWORD

1. Go to > Catalog > Select your Catalog Folder as marked above and select Archive

2. After selecting Archive a prompt box will appear as above. If you want to keep
Permissions and Keep Timestamps enable it otherwise disable it.

3. Select OK and your catalog file will be automatically downloaded like below.

23

UNARCHIVE:
4. Go to > obie.new.advansit.com:9704/analytics and login with your USERNAME and
PASSWORD
5. Go to > Catalog > and select under which folder your Catalog folder should be deployed.
6. Select the folder on which you want un archive.

7. After select un archive it will prompt for Browse position to upload the catalog.

8. Select the Browse and upload the required catalog.

24

UNARCHIVE OPTIONS:
Inherit pasted item: Inherits its permissions (ACL) from its new parent folder.
Preserve pasted item: Preserves its permissions (ACL) as it was in the original, mapping
accounts as necessary.

Create pasted item: Preserves its permissions (ACL) as it was in the original, creating and
mapping accounts as necessary.
None: Pastes all files, but does not paste any existing files.
Old: Pastes all files, but does not paste any existing files unless they are older than the source.
All: Paste all files, whether they exist or not. The default is 'all', which was the default behavior
in Release 10.1.3.2.

CONNECTION POOL:
1.

2.
3.
4.
5.

Goto>Startup menu>Oracle Business Intelligence Enterprise Edition>Administration.

Goto>File>Open>Offline>Browse for RPD.
Enter repository password to open.
Double click the database icon present in Physical layer.
Delete the old Database name (TESTDB) and Enter new Database name (PRDDB).

25

6.

7.
8.
9.

Select Connection Pool and select edit button.

Change old datasource name to new datasource name.
After changing the Datasource name save the changes and check for Global Consistency.
Once Global Consistency check is completed select ok.

SIGNING IN ERROR:
After doing all the changes while uploading the catalog I uploaded my production catalog
and I was unable to sign in.

26

For this I followed the below steps:

1. Go to> Enterprise Manager > Weblogic Domain > Security > Credentials

27

2. Select oracle.bi.system> edit

3. Type the required password and select Ok.

4. Launch admin tool and open rpd in OFFLINE Mode

5. Click Manage > Identity > Users tab to verify if you see this user present
Note: Normally you will only see list of users when you open rpd in ONLINE mode.
Unless the users were created manually in rpd, no users should be visible in OFFLINE mode

28

6. If the user is present, delete this user entry from rpd Eg: weblogic

7. save rpd and deploy this changed rpd using EM

8. restart OBI Server component
9. relogin as the problematic user to see if you still see Unable to Sign In error

Now its all set! You can log in to your obie.new.com:9704/analytics and
check the reports that have un archived.