Skip Headers
Oracle® Enterprise Manager Lifecycle Management Administrator's Guide
12c Release 4 (12.1.0.4)

E27046-25
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

14 Cloning Oracle Databases

This chapter contains the following sections:

14.1 Overview of Cloning Methods

You can use the Enterprise Manager Clone Database wizard to clone an Oracle database instance to an existing Oracle home. After you have an Oracle database instance in a known state (for example, you've configured it, tuned it, and tested it), you may want to clone that database to another existing Oracle home.

The following table lists the cloning methods and their cloning process:

Table 14-1 Oracle Database Cloning Methods

Cloning Method Cloning Process

Cloning an Oracle Database Using Recovery Manager (RMAN) Backup

  • Connects source and destination Oracle instances

  • Copies database files using RMAN duplicate feature

  • Recovers and opens the cloned database

Cloning an Oracle Database Using Staging Areas

  • Backs up each database file and stores it in a staging area

  • Transfers each backup file from source to destination

  • Restores each backup file to the specified locations

  • Recovers and opens the cloned database

Cloning an Oracle Database Using an Existing Backup

  • Creates cloned database as of specified point-in-time or SCN

  • Validates backups prior to the clone operation

  • Transfers required archived redo log files to destination host

  • Recovers and opens the cloned database


14.2 Cloning an Oracle Database Using Recovery Manager (RMAN) Backup

To clone an Oracle database using RMAN backup, follow these steps:

  1. From the Targets menu, select Databases.

  2. On the Databases page, select a database that you want to clone.

  3. On the Database target page, from the Oracle Database menu, select Provisioning, and then click Clone Database.

  4. On the Database Login page, enter your credentials. Click Login.

    The Clone Database wizard opens.

  5. On the Clone Database page: Source Type page, select Online Backup and Use Recovery Manager (RMAN) to copy database files.

    Click Continue.

    Note:

    When you use RMAN backup to clone a database, the source database will be duplicated directly to the specified destination Oracle Home. No staging areas are required.
  6. On the Clone Database: Source Options page, in the Degree of Parallels box, enter the number of parallel channels used by RMAN to copy the database files. The default number is 2.

    Note:

    Increased parallelism may speed the process if sufficient network bandwidth is available.
  7. In the Source Host Credentials section, enter the credentials of the user who owns the source database Oracle server installation. You can either select Named credential or New credential.

    If you select New credential, enter the Username and Password. You can select the Set as Preferred Credentials checkbox, if you want to use these set of credentials again. Click Test to check if your credentials are valid.

    Click Next.

  8. On the Clone Database: Select Destinations page, in the Destination Oracle Home section, click the Search icon.

    Note:

    The Oracle Home should exist on the specified host and should match the version of the source database.

    On the Destination Oracle Home page that appears, search and select the destination Oracle Home. Click Next.

  9. In the Destination Host Credentials section, enter the credentials of the user who owns the Oracle Home specified in the Destination Oracle Home section.

  10. In the Destination Database section, do the following: specify the global database name, the instance name, and for select file system as the database storage. Click Next.

    • Specify the global database name.

      For example: clone1.us.oracle.com

    • Specify a unique instance name.

      For example: clone1

    • Select File System as the database storage.

    • Click Next.

  11. On the Clone Database: Destination Options page, select Use Database Area and Fast Recovery Area.

    Click Next.

  12. On the Clone Database: Database Configuration page, in the Listener Configuration section, specify the name and port of the listener that will be used for the cloned database. If a new name and port are specified that are not in use by an exiting listener, a new listener using the specified port will be created.

    In the Database Registration section, select Register the cloned database as an Enterprise Manager target monitored by using DBSNMP. Enter the target database name.

    Click Next.

  13. On the Clone Database: Schedule page, specify a name description for the clone job. You can choose to run the clone job immediately or you can specify a later time and date for the job to run.

    Click Next.

  14. On the Clone Database: Review page, review the details and configuration of the source database, the destination database, and the database storage. You can view the database storage files by clicking on View Source Database Files.

    Click Submit Job. T

    he clone database job is now submitted. When the job completes, a Clone Database: Confirmation page appears. To view the status of the job, click View Status. To exit the page click OK.

14.3 Cloning an Oracle Database Using Staging Areas

To clone an Oracle database by copying database files via staging areas, follow these steps:

  1. From the Targets menu, select Databases.

  2. On the Databases page, select a database that you want to clone.

  3. On the Database target page, from the Oracle Database menu, select Provisioning, and then click Clone Database.

  4. On the Database Login page, enter your credentials. Click Login.

    The Clone Database wizard opens.

  5. On the Clone Database page: Source Type page, select Online Backup and Copy database files via staging areas.

    Click Continue.

    Note:

    This method requires staging areas on both the source and the destination hosts.
  6. On the Clone Database: Source Options page, in the Staging Area section, enter the Staging Area Location.

    Note:

    A staging area on the source host is required in order to clone a running database. A backup is performed on the database and the backup files are stored in the staging area.
  7. Select if you want to delete or retain the staging area after the cloning operation.

    By retaining the staging area after a cloning operation, you avoid doing another backup later. However, this option requires a minimum disk space of 2230 MB.

  8. In the Source Host Credentials section, enter the credentials of the user who owns the source database Oracle server installation. You can either select Named credential or New credential.

    If you select New credential, enter the Username and Password. You can select the Set as Preferred Credentials checkbox, if you want to use these set of credentials again. Click Test to check if your credentials are valid.

    Click Next.

  9. On the Clone Database: Select Destinations page, in the Destination Oracle Home section, click the Search icon.

    Note:

    The Oracle Home should exist on the specified host and should match the version of the source database.

    On the Destination Oracle Home page that appears, search and select the destination Oracle Home. Click Next.

  10. In the Destination Host Credentials section, enter the credentials of the user who owns the Oracle Home specified in the Destination Oracle Home section.

  11. In the Destination Database section, do the following: specify the global database name, the instance name, and for select file system as the database storage. Click Next.

    • Specify the global database name.

      For example: clone1.us.oracle.com

    • Specify a unique instance name.

      For example: clone1

    • Select File System as the database storage.

    • Click Next.

  12. On the Clone Database: Destination Options page, select Use Database Area and Fast Recovery Area.

    Click Next.

  13. On the Clone Database: Database Configuration page, in the Listener Configuration section, specify the name and port of the listener that will be used for the cloned database. If a new name and port are specified that are not in use by an exiting listener, a new listener using the specified port will be created.

    In the Database Registration section, select Register the cloned database as an Enterprise Manager target monitored by using DBSNMP. Enter the target database name.

    Click Next.

  14. On the Clone Database: Schedule page, specify a name description for the clone job. You can choose to run the clone job immediately or you can specify a later time and date for the job to run.

    Click Next.

  15. On the Clone Database: Review page, review the details and configuration of the source database, the destination database, and the database storage. You can view the database storage files by clicking on View Source Database Files.

    Click Submit Job. T

    he clone database job is now submitted. When the job completes, a Clone Database: Confirmation page appears. To view the status of the job, click View Status. To exit the page click OK.

14.4 Cloning an Oracle Database Using an Existing Backup

To clone an Oracle database using an existing backup, follow these steps:

  1. From the Targets menu, select Databases.

  2. On the Databases page, select a database that you want to clone.

  3. On the Database target page, from the Oracle Database menu, select Provisioning, and then click Clone Database.

  4. On the Database Login page, enter your credentials. Click Login.

    The Clone Database wizard opens.

  5. On the Clone Database page: Source Type page, select Existing BackUp.

    Click Continue.

  6. On the Clone Database: Source Host Credentials page, select the backup that you want to use.

  7. In the Source Host Credentials section, enter the credentials of the user who owns the source database Oracle server installation. You can either select Preferred, Named or New credential.

    If you select New credential, enter the Username and Password. You can select the Set as Preferred Credentials checkbox, if you want to use these set of credentials again. Click Test to check if your credentials are valid.

    Click Next.

  8. On the Clone Database: Backup Details page, in the Point In Time section, specify a time or System Change Number (SCN). This will help identify backups necessary to create the clone database.

    Note:

    If the existing backup does not have all necessary archive logs, Enterprise Manager will transfer them from the source host to the destination host as part of the clone operation.
  9. Oracle database backups are can be encrypted using a database wallet, password, or both. If the backups are encrypted, specify the encryption mode and password as needed, in the Encryption section. By default, the encryption mode is set as None.

    Click Next.

  10. In the Destination Host Credentials section, enter the credentials of the user who owns the Oracle Home specified in the Destination Oracle Home section.

  11. In the Destination Database section, do the following: specify the global database name, the instance name, and for select file system as the database storage. Click Next.

    • Specify the global database name.

      For example: clone1.us.oracle.com

    • Specify a unique instance name.

      For example: clone1

    • Select File System as the database storage.

  12. In the Parallelism section, in the Degree of Parallels box, enter the number of parallel channels used by RMAN to copy the database files. The default number is 2.

    Note:

    Increased parallelism may speed the process if sufficient network bandwidth is available.

    Click Next.

  13. On the Clone Database: Destination Database Settings page, in the Memory Parameters section, select Configure Memory Management and then from the drop-down list select Automatic Shared Memory Management.

    The database automatically sets the optimal distribution of memory across the System Global Area (SGA) components. The distribution of memory will change from time to time to accommodate changes in the workload. Also, specify the aggregate Program Global Area (PGA) size.

  14. In the Listener Configuration section, specify the name and port of the listener to be configured for the database. If the listener specified does not exist at the destination Oracle Home, it will be created.

    Note:

    If you are going to convert the cloned database RAC at a later point, it is recommended that you specify storage location shared across all hosts in the cluster.
  15. In the Recovery Files section, specify the location where recovery-related files such as, archived redo log files, RMAN backups, and the like are to be created.

    Click Next.

  16. On the Clone Database: Storage Locations page, in Database Files Location section, specify the location where datafiles, tempfiles, redo log files, and control files are to be created.

    In the Database Registration section, select Register the cloned database as an Enterprise Manager target monitored by using DBSNMP. Enter the target database name.

    Click Next.

  17. On the Clone Database: Schedule page, specify a name description for the clone job. You can choose to run the clone job immediately or you can specify a later time and date for the job to run.

    Click Next.

  18. On the Clone Database: Review page, review the details and configuration of the source database, the destination database, and the database storage. You can view the database storage files by clicking on View Source Database Files.

    Click Submit Job. T

    The clone database job is now submitted. When the job completes, a Clone Database: Confirmation page appears. To view the status of the job, click View Status. To exit the page click OK.