14 Cloning Oracle Databases

Enterprise Manager Cloud Control enables you to clone databases using the Full Clone, Snap Clone, or CloneDB methods. You can then promote the database clone as a Test Master database.

This section outlines the following procedures which you can use to create a database clone:

14.1 Creating a Full Clone Database

To create a full clone database, follow these steps:

  1. On the Database target home page, click Oracle Database, select Provisioning, and then click Clone and Refresh.

    Clone and Refresh page navigation
  2. On the Clone and Refresh page, in the Full Clone Databases section, click Create.

    Create button for full clone

    The Clone and Refresh table displays the names of clones created, the status of the clone, the database version, the type of the clone, and also consists of columns that display if the clone database is a Test Master database, if it has masked data, and if it is cloud target.

    Note:

    A Test Master is sanitized version of the production database. It can be created using live data and is continuously synchronized with the primary database. It can also be created from a database backup taken at a prior point in time and refreshed at discrete intervals. The Test Master column shows a green tick if the clone database is a Test Master database.

    The Data Masked column shows a green tick if the data in the database clone has been masked, during the Post Processing step while creating the clone.

    The Cloud Target column shows if the clone database is a cloud target.

  3. On the Create Full Clone Database: Source Destination page, do the following:

    • In the Source Credentials section, launch the credentials selector by selecting the search icons for Database and Oracle Home. Select the Named credentials or specify New credentials. Click OK.

    • In the Source Data Time Series, select Now or Prior Point in Time.

      Note:

      Now refers to Live Clone.
      Full Clone source section

      If you selected Prior Point in Time, a carousel of RMAN Backup images appear. Select the appropriate RMAN backup by clicking Select on the image.

      Cloning Database Source Date Time Series

      You can create full clones by selecting a backup and optionally modify the time and SCN to do a point in time restore.The Select Time option has the minimum limit set to the current backups time and maximum time limit set to the next backup time. You can modify this in case you have to create a new clone between these two time periods. Similarly, you can do the same for SCN by selecting the Select SCN option.

      Select date and SCN
  4. In the Destination Database Definition section, do the following:

    • Specify a Global Database Name and SID.

      A database is uniquely identified by a Global Database Name. The typical form of a name is name.domain. A database is referenced by at least one Oracle instance which is uniquely identified by SID.

    • Select one of the following types of databases:

      • Single Instance Database.

        Specify the Oracle Home that you want to use as the destination host. The host gets specified by default. Next, select the Database Home credentials and the Root credentials.

      • RAC Database

        Specify or select the cluster target, the Oracle Home, and the configuration.

        In the Nodes section, select the cluster and Oracle Home to display one or more hosts on which the administrator managed Oracle RAC database will be created,

        Select the Database Home credentials.

      • RAC One Node Database

        Specify or select the cluster target, the Oracle Home, and the configuration.

        In the Nodes section, select the cluster and Oracle Home to display one or more hosts on which the administrator managed Oracle RAC database will be created,

        Select the Database Home credentials.

      Click Next.

      Creating Full clone destination section
  5. In the Destination section, specify or search and select the destination Oracle Home. The host gets added automatically.

    Note:

    Oracle supports inline patching as part of clones. When the destination home selected has patches applied such as the latest CPU or PSU, then the cloned database is automatically brought up with that level.
  6. In the Destination Credentials section, specify the Oracle Home credentials.

    Click Next.

  7. On the Create Full Clone Database: Configuration page, do the following:

    • In the Database Files Location, specify the location where you want the data files, temp files, redo log files, and control files to be created. You can select File System or Automatic Storage Management (ASM), and then specify the common location for the database files.

      The Use Oracle Optimal Flexible Architecture-compliant directory structure (OFA) option enables you to configure different locations for:

      • Archive and Redo logs

      • Data files

      • Control file

      • Temporary file

      Database files location for creating full clone database
    • In the Recovery Files location, specify the location where you want the recovery files, such as archived redo logs, RMAN backups, and other related files to be created. You can choose to use the fast area recovery by selecting Use Fast Recovery Area. If you do, specify the fast recovery area size. The fast recovery area size is defaulted to that of source.

      Recovery Files Location section in creating full clone database wizard
    • In the Listener Configuration section, select the listener targets running under the new Oracle Home, to register the clone database.

      Listener Configuration section
    • In the Database Credentials section, specify passwords for the SYS, SYSTEM, and DBSNMP administrative users in the clone database. You can choose to have the same password for all the three users or a different password for each.

      Database credentials section

      Click Next.

  8. On the Create Full Clone Database: Initialization Parameters page, you can configure the values of various initialization parameters that affect the operation of the database instance. Select the parameter and click Edit to modify the value of the parameter.

    Initialization Parameters page

    Click Next.

  9. On the Create Full Clone Database: Post Processing page, specify the following:

    • Masking Definition: Data masking is the process of masking sensitive data in test or non-production databases. The masking definition defines the columns to be masked in the format of the masked data. Specify the masking definition to be applied after the database is cloned.

      Note:

      The masking definition can be used only when you have a Subset-Masking license pack.
    • Custom Scripts: Specify the custom scripts that need to be executed before and after the database is created.

    • Create Data Profile: This option enables you to automatically take a backup of the new cloned instance once it is created. When the clone or the Test Master is refreshed, this section displays the existing profiles created for the database. You can select the profile that has to be refreshed along with the database.

    • Create as Test Master: This option if you want to create the cloned database as a Test Master database.

    Post Processing page

    Click Next.

  10. On the Create Full Clone Database: Schedule page, specify a unique deployment procedure instance name. You can choose to start the deployment procedure immediately or at a later time,

    In the Notification Details section, you can choose to set the following notifications:

    • Scheduled

    • Running

    • Action Required

    • Suspended

    • Succeeded

    • Problems

    Schedule page

    Click Next.

  11. On the Clone Database: Review page, verify the details of the source database, the data source of the clone, and the destination database.

    Review page

    Click Submit.

14.2 Creating a Snap Clone Database

To create a Snap Clone database, follow these steps:

  1. On the Database target home page, click Oracle Database, select Provisioning, and then click Clone and Refresh.

    Clone and Refresh page navigation
  2. On the Clone and Refresh page, in the Full Clone Databases section, click Create.

    Create button for creating Snap Clone database

    The Clone and Refresh table displays the names of clones created, the status of the clone, the database version, the type of the clone, and also consists of columns that display if the clone database is a Test Master database, if it has masked data, and if it is cloud target.

    Note:

    A Test Master is sanitized version of the production database. It can be created using live data and is continuously synchronized with the primary database. It can also be created from a database backup taken at a prior point in time and refreshed at discrete intervals. The Test Master column shows a green tick if the clone database is a Test Master database.

    The Data Masked column shows a green tick if the data in the database clone has been masked, during the Post Processing step while creating the clone.

    The Cloud Target column shows if the clone database is a cloud target.

  3. On the Create Snap Clone Database: Source Destination page, do the following:

    • In the Source Credentials section, launch the credentials selector by selecting the search icons for Database and Oracle Home. Select the Named credentials or specify New credentials. Click OK.

    • In the Source Data Time Series, select Now or Prior Point in Time.

      Note:

      Now refers to Live Clone.

      If you selected Prior Point in Time, a carousel of RMAN Backup images appear. Select the appropriate RMAN backup by clicking Select on the image.

      Select prior point in time

      You can create full clones by selecting a backup and optionally modify the time and SCN to do a point in time restore.The Select Time option has the minimum limit set to the current backups time and maximum time limit set to the next backup time. You can modify this in case you have to create a new clone between these two time periods. Similarly, you can do the same for SCN by selecting the Select SCN option.

      Select date and SCN
    • In the Database Snapshot section specify the location, name, description, version, and vendor of the snapshot profile which will be created as part of the clone database job.You can add additional notes, such as host name, database, data content, and data content mode.

      Source section for creating snap clone database
  4. In the Destination Database Definition section, do the following:

    • Specify a Global Database Name and SID.

      A database is uniquely identified by a Global Database Name. The typical form of a name is name.domain. A database is referenced by at least one Oracle instance which is uniquely identified by SID.

    • Select one of the following types of databases:

      • Single Instance Database.

        Specify the Oracle Home that you want to use as the destination host. The host gets specified by default. Next, select the Database Home credentials and the Root credentials.

      • RAC Database

        Specify or select the cluster target, the Oracle Home, and the configuration.

        In the Nodes section, select the cluster and Oracle Home to display one or more hosts on which the administrator managed Oracle RAC database will be created,

        Select the Database Home credentials.

      • RAC One Node Database

        Specify or select the cluster target, the Oracle Home, and the configuration.

        In the Nodes section, select the cluster and Oracle Home to display one or more hosts on which the administrator managed Oracle RAC database will be created,

        Select the Database Home credentials.

      Click Next.

      Creating Full clone destination section
  5. In the Destination section, specify or search and select the destination Oracle Home. The host gets added automatically.

    Note:

    Oracle supports inline patching as part of clones. When the destination home selected has patches applied such as the latest CPU or PSU, then the cloned database is automatically brought up with that level.
  6. In the Destination Credentials section, specify the Oracle Home and Root credentials.

    Click Next.

  7. On the Create Snap Clone Database: Configuration page, do the following:

    • In the Configure Volumes, configure the volumes that will be used by the clone database, by specifying the following:

      • Mount Point Prefix: Specify a new mount point for the database being cloned. This value would be prefixed to an auto-generated mount point where a clone of this volume will be mounted. The volume will be mounted on /<mount-prefix> <unique-suffix-generated-by-EM> /<source-path>. The mount point prefix can be the Same for All Volumes or Different for Each Volume.

        Note:

        the volumes must be pre-created.
      • Writable Space: Specify the amount of space required for block changes. The value specified here cannot exceed the Storage Ceiling specified for the server. For example, for minimal data changes, you specify the value as 1% of the original volume size. The writable space can be the Same for All Volumes or Different for Each Volume.

      Configure Volumes section
    • The storage details of the selected database are displayed in the Volume Content Information section. Click Show Files to view the layout of the database files in the volumes.

      Volume Content Information
    • In the Listener Configuration section, select the listener targets running under the new Oracle Home, to register the clone database, You can add new listeners by clicking Add, and specifying the listener name and port.

      Listener Configuration section
    • In the Database Credentials section, specify passwords for the SYS, SYSTEM, and DBSNMP administrative users in the clone database. You can choose to have the same password for all the three users or a different password for each.

      Database Credentials section

      Click Next.

  8. On the Create Snap Clone Database: Initialization Parameters page, you can configure the values of various initialization parameters that affect the operation of the database instance. Select the parameter and click Edit to modify the value of the parameter.

    Initialization Parameters page
    Click Next.

  9. On the Create Snap Clone Database: Post Processing page, specify the following:

    • Masking Definition: Data masking is the process of masking sensitive data in test or non-production databases. The masking definition defines the columns to be masked in the format of the masked data. Specify the masking definition to be applied after the database is cloned.

      Note:

      The masking definition can be used only when you have a Subset-Masking license pack.
    • Custom Scripts: Specify the custom scripts that need to be executed before and after the database is created.

    Post Processing page

    Click Next.

  10. On the Create Snap Clone Database: Schedule page, specify a unique deployment procedure instance name. You can choose to start the deployment procedure immediately or at a later time,

    In the Notification Details section, you can choose to set the following notifications:

    • Scheduled

    • Running

    • Action Required

    • Suspended

    • Succeeded

    • Problems

    Schedule page
    Click Next.

  11. On the Create Snap Clone Database: Review page, verify the details of the source database, the data source of the clone, and the destination database.

    Review page
    Click Submit.

14.3 Creating a CloneDB Database

You can create CloneDB databases only when you have RMAN Image backups.

To create a CloneDB database, follow these steps:

  1. On the Database target home page, click Oracle Database, select Provisioning, and then click Clone and Refresh.

    Clone and Refresh page navigation
  2. On the Clone and Refresh page, in the CloneDB Databases section, click Create.

    Create button for creating a CloneDB database

    The Clone and Refresh table displays the names of clones created, the status of the clone, the database version, the type of the clone, and also consists of columns that display if the clone database is a Test Master database, if it has masked data, and if it is cloud target.

    Note:

    A Test Master is sanitized version of the production database. It can be created using live data and is continuously synchronized with the primary database. It can also be created from a database backup taken at a prior point in time and refreshed at discrete intervals. The Test Master column shows a green tick if the clone database is a Test Master database.

    The Data Masked column shows a green tick if the data in the database clone has been masked, during the Post Processing step while creating the clone.

    The Cloud Target column shows if the clone database is a cloud target.

  3. On the Create CloneDB Database: Source Destination page, do the following:

    • In the Source Credentials section, specify or search and select the database and Oracle Home credentials. Click OK.

    • In the Source Data Time Series, Prior Point in Time is selected automatically.

      Select the appropriate RMAN Image backup by clicking Select on the image.

      Cloning Database Source Date Time Series

      You can create full clones by selecting a backup and optionally modify the time and SCN to do a point in time restore.The Select Time option has the minimum limit set to the current backups time and maximum time limit set to the next backup time. You can modify this in case you have to create a new clone between these two time periods. Similarly, you can do the same for SCN by selecting the Select SCN option.

      Modify SCN and time
  4. In the Destination Database Definition section, do the following:

    • Specify a global database name and SID.

    • Select the version of the database.

    • Select one of the following types of databases:

      • Single Instance Database.

        Specify the Oracle Home that you want to use as the destination host. The host gets specified by default. Next, select the Database Home credentials and the Root credentials.

      • RAC Database

        Specify or select the cluster target, the Oracle Home, and the configuration.

        In the Nodes section, select the cluster and Oracle Home to display one or more hosts on which the administrator managed Oracle RAC database will be created,

        Select the Database Home credentials.

      • RAC One Node Database

        Specify or select the cluster target, the Oracle Home, and the configuration.

        In the Nodes section, select the cluster and Oracle Home to display one or more hosts on which the administrator managed Oracle RAC database will be created,

        Select the Database Home credentials.

      Creating Full clone destination section
  5. In the Destination section, specify or search and select the destination Oracle Home. The host gets added automatically.

    Note:

    Oracle supports inline patching as part of clones. When the destination home selected has patches applied such as the latest CPU or PSU, then the cloned database is automatically brought up with that level.
  6. In the Destination Credentials section, specify the Oracle Home credentials.

    Click Next.

  7. On the Create CloneDB Database: Configuration page, do the following:

    • In the Database Files Location, specify the location where you want the data files, temp files, redo log files, and control files to be created. You can select File System or Automatic Storage Management (ASM), and then specify the common location for the database files.

      The Use Oracle Optimal Flexible Architecture-compliant directory structure (OFA) option enables you to configure different locations for:

      • Archive and Redo logs

      • Data files

      • Control file

      • Temporary file

        Database files location for creating full clone database
    • In the Recovery Files location, specify the location where you want the recovery files, such as archived redo logs, RMAN backups, and other related files to be created. You can choose to use the fast area recovery by selecting Use Fast Recovery Area. If you do, specify the fast recovery area size. The fast recovery area size is defaulted to that of source.

      Recovery Files Location section in creating full clone database wizard
    • In the Database Mode section, you can enable Read Only.

    • In the Listener Configuration section, select the listener targets running under the new Oracle Home, to register the clone database.

      Listener Configuration section
    • In the Database Credentials section, specify passwords for the SYS, SYSTEM, and DBSNMP administrative users in the clone database. You can choose to have the same password for all the three users or a different password for each.

      Database credentials section

      Click Next.

  8. On the Create CloneDB Database: Initialization Parameters page, you can configure the values of various initialization parameters that affect the operation of the database instance. Select the parameter and click Edit to modify the value of the parameter.

    Click Next.

  9. On the Create CloneDB Database: Post Processing page, specify the following:

    • Masking Definition: Data masking is the process of masking sensitive data in test or non-production databases. The masking definition defines the columns to be masked in the format of the masked data. Specify the masking definition to be applied after the database is cloned.

      Note:

      The masking definition can be used only when you have a Subset-Masking license pack.
    • Custom Scripts: Specify the custom scripts that need to be executed before and after the database is created.

    • Create Data Profile: This option enables you to automatically take a backup of the new cloned instance once it is created. When the clone or the Test Master is refreshed, this section displays the existing profiles created for the database. You can select the profile that has to be refreshed along with the database.

    • Create as Test Master: This option if you want to create the cloned database as a Test Master database.

    Post Processing page

    Click Next.

  10. On the Create CloneDB Database: Schedule page, specify a unique deployment procedure instance name. You can choose to start the deployment procedure immediately or at a later time.

    In the Notification Details section, you can choose to set the following notifications:

    • Scheduled

    • Running

    • Action Required

    • Suspended

    • Succeeded

    • Problems

    Schedule page

    Click Next.

  11. On the Clone Database: Review page, verify the details of the source database, the data source of the clone, and the destination database,

    Click Submit.

14.4 Managing Clone Databases

The Clone and Refresh page enables you to manage clone databases by adding clone databases, removing clone database, and promoting the clone databases as Test Master.

To access the Clone and Refresh page, navigate to an Oracle database target home page. On the home page, click Oracle Database, select Provisioning, and then select Clone and Refresh.

Adding Clone Databases

The Add button can be used to add the clones of the current databases which have already been created.To add a database clone instance, click on Add. In the Select Targets dialog box that opens, select a database target, and click Select. The database instance gets added to the Clones section in the Database Cloning page.

Removing Clone Databases

Only the databases that are added using the Add button can be removed using the Remove button.T

o remove a database clone instance, select the database clone instance that you want to remove, from the Clones section. Click Remove.

Promoting Clone Databases as Test Master

To promote a database clone database instance as Test Master, select the clone instance that you want to recreate from the Clone section. Click Promote as Test Master.

You can also remove the clone database instance from Test Masters, by selecting the clone database instance from the Clones section, and clicking Remove from Test Masters.

Refresh Clone Databases

To refresh a clone database, select the clone database instance from the Clone section, and then click Refresh.

Managing clone databases

Creating Data Profiles

The Data Profiles tab on the Clone and Refresh page displays the data profiles that you have created from the clone database. On the Data Profiles page, you can view the contents of existing data profiles. You can also Edit and Refresh these data profiles.

Data Profiles page

You can also create a new data profile by clicking Create. This takes you to the Create Provisioning Profile wizard. Refer to Enterprise Manager Cloud Control Administrator's Guide for information on how to create a provisioning profile using this wizard.

14.5 Refreshing Clone Databases

To refresh a clone database, navigate to the Refresh and Clone page by following these steps:

  1. From the Targets menu, select Databases.

  2. On the databases home page, select the database clone instance that you want to refresh from the list of databases.

  3. On the database target home page, click Oracle Database, select Provisioning, and then select Clone and Refresh.

  4. On the Clone and Refresh page, select the Refresh tab.

The Refresh page displays the following sections:

  • Drift from Source Database

    This section displays the name of the source database from which this database has been cloned. It shows the number of days since the clone database has been refreshed. Click Refresh to refresh the clone database.

  • Database Volume Details

    This section displays the storage details for the selected databases. Click Show files to view the layout of the database files in the volumes. A display box appears that shows the storage layout and file layout of the selected database.

  • History

    This section displays the past refreshes of the database. It shows the date and time of the refresh, where it has been refreshed from, the owner of the database, and the status of the refresh action.

  • Storage Utilization

    This section displays the storage volume of the database, the storage contents, the mount point, the amount of writable storage used, and the synchronization date.

Refresh page

14.6 Cloning Databases Using the Classic Cloning Wizard

You can clone databases using the older cloning wizard. This section consists of the following:

14.6.1 Overview of Classic 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.6.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 and Refresh Database.

  4. On the Clone and Refresh page, click the Switch to Classic Clone link.

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

    The Clone Database wizard opens.

  6. 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.
  7. 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.
  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.example.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.6.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 Clone and Refresh page, click the Switch to Classic Clone link.

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

    The Clone Database wizard opens.

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

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

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

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

  12. 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.example.com

    • Specify a unique instance name.

      For example: clone1

    • Select File System as the database storage.

    • Click Next.

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

    Click Next.

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

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

  16. 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.6.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 Clone and Refresh page, click the Switch to Classic Clone link.

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

    The Clone Database wizard opens.

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

    Click Continue.

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

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

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

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

  12. 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.example.com

    • Specify a unique instance name.

      For example: clone1

    • Select File System as the database storage.

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

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

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

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

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

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