Tuesday, August 18, 2009

Oracle Discoverer 10g rehost a.k.a moving Discoverer 10g from one server to another

Long time no blog! The reason being that I was busy performing this Discoverer 10g rehost. Without wasting much of your time, let me get into the details.

Background

Recently, we rehosted (i.e., moved) our production instance to a new set of production servers. Discoverer 10g is also a part of our prodcution implementation. Discoverer resided on the old production servers.

Requirement

Move Discoverer 10g from the old production servers to the new ones (a.k.a rehost!).

Methodology

After scrutinizing all the available Metalink docs, I found out that no Metalink doc existed for my requirement! I had to chart my own course here (not that no one had done this before but lack of documentation - both on the web and Metalink, was a bit of an impediment).

After burrowing through all the available documentation, I surmised that I had two methods to achieve my goal:

1. Reinstallation of Discoverer 10g (including OID)

2. Cloning of Discoverer 10g ORACLE_HOME.


Steps involved in both the methods is given below:


Reinstallation of Discoverer 10g

1. Install OracleAS Identity Management Infrastructure 10g (10.1.4.0.1) [infra tier].


2. Upgrade OracleAS Identity Management Infrastructure 10g to Oracle Identity Management 10g Release 3 Patch Set 1 (10.1.4.2).


3. Install Oracle Application Server 10g Release 2 (10.1.2.0.2) type Business Intelligence and Forms (mid tier).


4. Copy Database Connection file from $FND_TOP/secure/cpepdb1_cpep.dbc on the admin node to DISCOVERER $ORACLE_HOME/discoverer/secure on the new Discoverer server.


Notes:
a. One can also copy the dbc file from the old Discoverer ORALCE_HOME
on the old server to the new Discoverer ORACLE_HOME on the new
server.


b. Create the directory
$ORACLE_HOME/discoverer/secure if it does not exist.


5. Update tnsnames.ora file - Copy the file DISCOVERER
$ORACLE_HOME/network/admin/tnsnames.ora on the old server to Discoverer
$ORACLE_HOME/network/admin/tnsnames.ora on the new server.


6. Specify Java Virtual Machine for Discoverer Plus - Check what is selected as the default (should be Sun Java 1.4) in Enterprise Manager on the Oracle Business Intelligence 10g Release 2 ORACLE_HOME using ias_admin login.


7. Modify below Applications profile options related to Discoverer in Oracle Applications


ICX_DISCOVERER_LAUNCHER & ICX_DISCOVERER_VIEWER_LAUNCHER




Cloning of Discoverer 10g ORACLE_HOME

1. Install OracleAS Identity Management Infrastructure 10g (10.1.4.0.1) [infra tier] on suomp02l.


2. Upgrade OracleAS Identity Management Infrastructure 10g to Oracle Identity Management 10g Release 3 Patch Set 1 (10.1.4.2) on suomp02l.


3. Prepare the source middle tier (Discoverer 10gAS on suomp971) for cloning.


a. For cloning, Perl 5.6.1 or higher must be installed on your system.


$ export
PERL5LIB=$ORACLE_HOME/perl/lib/5.6.1:$ORACLE_HOME/perl/lib/site_perl/5.6.1:$PERL5LIB



b. Run the script prepare_clone.pl. This script prepares the source to be cloned.


$ cd $ORACLE_HOME/clone/bin
$ perl prepare_clone.pl ORACLE_HOME=$ORACLE_HOME -oid_password <OIDPassword>


4. Archive and compress the source Oracle home, using your preferred tool for archiving (using tar and gzip).


5. Copy the compressed Oracle home from the source machine to the destination machine.


6. Extract the compressed Oracle home into a directory, which will become the new Oracle home at the destination location.


7. Run the clone.pl script. You must have write permission to the directory containing the Oracle inventory file.


$ cd $ORACLE_HOME/clone/bin
$ perl clone.pl ORACLE_HOME=<NEW_ORACLE_HOME_LOCATION> ORACLE_HOME_NAME=OH_1012_BI -instance <new_instance_name> -ias_admin_old_pwd <old_ias_admin_password> -ias_admin_new_pwd <new_ias_admin_password> -oid_password <oid_password>



8. Modify below Applications profile options related to Discoverer in Oracle Applications

ICX_DISCOVERER_LAUNCHER & ICX_DISCOVERER_VIEWER_LAUNCHER


The method that I followed was reinstallation primarily because cloning a 10g AS ORACLE_HOME is renowned to be riddled with errors and pitfalls! The reinstallation method worked like a charm and I was able to move the Discoverer 10g without any hitches and significantly, without any downtime too (!) thus avoiding weekend work!!!


References

2. Metalink Note ID: 313418.1 - Using Discoverer 10.1.2 with Oracle E-Business Suite 11i

No comments: