Cloning a Business Intelligence and Forms Install Connected to an Infrastructure

Enterprise Manager allows you to deploy one or more Business Intelligence Services and Forms Install Application Server instances similar in configuration to a source instance.

Prerequisites for Cloning

Ensure that the following prerequisites are met before cloning:

You have setup the Grid Control properly to manage the source and target hosts.
You have a valid source Oracle home with read / write privileges. Ensure that $ORACLE_HOME/config/ias.properties file has read privileges.
If the cloned instance is required to connect to a cluster, ensure that such a cluster already exists in the farm in which that instance is expected to join.
You have a Central Agent (10.2 or above) monitoring all the destination hosts.

Cloning to Another Business Intelligence and Forms Install in the Same Farm

To clone a Business Intelligence and Forms Install connected to an infrastructure to another Business Intelligence Service and Forms Install setup connected to the same farm as the source:

Select a Business Intelligence Service and Forms Install setup 10.1.2 home from the list of clonable homes and click Next.
At the Source Settings page, enter the working directory location, host credentials and the files to be excluded from the Oracle home archive and click Next.
The credentials provided are verified and the ias.properties file is read to check the configuration. The Product Settings page is rendered accordingly, asking for the new instance name, the old and new ias_admin passwords, and the OID admin password. You may also need to specify the cluster to which the new instance should join and click Next.
Provide the destination Oracle home information along with the destination host credentials. Ensure that these credentials are correct as these are not verified here and the job may fail later if these are wrong. Click Next.
Specify the pre/post/root scripts or commands to be executed before/after the cloning operation. The same script will be executed parallely on each destination. You may choose to execute pre/post/root scripts with sudo privileges for UNIX, but the host credentials previously specified should have sudo privileges on the destination host for this to succeed. Failure of this step will not affect the overall status of the job. Click Next.

Note: If root.sh is not run through the job, you must run it manually for the cloning operation to complete.
Schedule the job immediately or at an appropriate time. You can also change the name of the job, from the default one that uses the time stamp. Click Next.
Review your selection and and click Finish.

Note : The cloned instance will automatically join back to the same farm as the source after the clone operation.

Related Topics

Enterprise Manager Information Roadmap