Cloning an Oracle Database 9.2.0.6.0 Standard Edition Software only install

You can clone an Oracle Database 9.2.0.6.0 Standard Edition instance between two machines or on the same machine.

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.

• You have a Central Agent (10.1 or above, provided its unzip version is greater than 5.41) monitoring all the destination hosts.

Cloning an Oracle Database 9.2.0.6.0 Standard Edition between two machines

To clone an Oracle Database 9.2.0.6.0 Standard Edition instance between two machines:

1. Download and install the clone support files from OracleMetaLink, by following these steps:

   • Navigate to the Advanced Search option under Patches and Updates.

   • Enter "Clone Support Files" in the query term field.

   • Select Enterprise Manager Grid Control product from the drop-down list and select the appropriate platform.

   • Click Search

2. Patch the Oracle Management Service using the clone files.

3. Select an Oracle Database 9.2.0.6.0 home from the list of clonable homes and click Next.

4. At the Source Settings page, enter the working directory location, host credentials and the files to be excluded from the Oracle home archive. Click Next.

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

6. 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 scripts with sudo privileges, 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.

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

8. Review your selection and click Finish.

Enterprise Manager Information Roadmap

Copyright © 1996, 2007, Oracle. All rights reserved.