1. From the Targets menu, select Databases.
2. For View, select Search List. From the View menu, select Expand All.
3. Look for the source CDB (the CDB that the source PDB is a part of) in the list, then click the name of the PDB from which you want to create a test master PDB.
4. From the Oracle Database menu, select Cloning, then select Create Test Master.

   Alternatively, in Step 3, you can right click the name of the PDB from which you want to create a test master PDB, select Oracle Database, select Cloning, then select Create Test Master.

5. On the Create Test Master Pluggable Database: Source and Destination page, do the following:

   • Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.

   • In the Pluggable Database Definition section, specify a name, and a display name for the test master PDB. Enterprise Manager uses the display name to identify the test master PDB target.

   • In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.

   • In the Container Database section, specify the destination CDB (the CDB that the test master PDB must be a part of).

   • In the Credentials section, specify the SYSDBA credentials for the destination CDB, and the host credentials for the destination CDB. Also, if the destination CDB is using Automatic Storage Management (ASM) to manage disk storage, you must specify the ASM credentials.

     Click Next.

     
     

     

     
     
6. On the Create Test Master Pluggable Database: Configuration page, do the following:

   In the Database Files Location section, specify the storage location where the datafiles of the test master PDB must be stored. If the destination CDB is using ASM to manage disk storage, specify the disk group where the datafiles of the test master PDB must be stored.

   To ensure that only the source PDB data model definition is cloned (and the source PDB data is not cloned), select Exclude User Data.

   In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.

   In the Advanced Configuration section, specify the storage limits for the maximum size of the test master PDB, and the maximum size of a shared tablespace within the test master PDB. By default, no limits are placed on the values for these attributes. In the Miscellaneous section, select the logging option that you want to use for the tablespaces created within the test master PDB.

   Note that if the destination CDB is part of an Exadata machine, the Access Controls and Permissions section is displayed in place of the Advanced Configuration section. In this case, you must specify the owner and the group that must be granted read only permissions on the datafiles.

   Click Next.

   
   

   

   
   
7. On the Create Test Master Pluggable Database: Post Processing page, in the Data Masking section, specify the data masking definition that you want to apply after creating the test master PDB. Data masking masks sensitive data in a database.

   For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

   In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before, and after creating the test master PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after creating the test master PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

   Click Next.

   
   

   

   
   
8. Specify an instance name for the deployment procedure. Also, specify the point in time when you want the deployment procedure to begin.

   In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the deployment procedure is scheduled, and when it succeeds.

   Click Next.

   
   

   

   
   
9. Review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

   Click Clone to submit the deployment procedure to create a test master PDB from the source PDB.

   
   

   

   
   

   Note:

   The pluggable database cloning procedure contains a prerequisite step that is enabled by default. This step causes the cloning procedure to fail. To disable this step, run the following command:

   emctl set property -name oracle.sysman.db.pdb.prereq_enabled —sysman_pwd <sysman password> —value false

   To enable this step, run the following command:

   emctl set property -name oracle.sysman.db.pdb.prereq_enabled -sysman_pwd <sysman password> —value true

1. From the Targets menu, select Databases.
2. For View, select Search List. From the View menu, select Expand All.
3. Look for the source CDB (the CDB that the source PDB is a part of) in the list, then click the name of the PDB from which you want to create a test master PDB.
4. From the Oracle Database menu, select Cloning, then select Create Test Master.

   Alternatively, in Step 3, you can right click the name of the PDB from which you want to create a test master PDB, select Oracle Database, select Cloning, then select Create Test Master.

5. On the Create Test Master Pluggable Database: Source and Destination page, do the following:

   • Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.

   • In the Pluggable Database Definition section, specify a name, and a display name for the test master PDB. Enterprise Manager uses the display name to identify the test master PDB target.

   • In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.

   • In the Container Database section, specify the destination CDB (the CDB that the test master PDB must be a part of).

   • In the Credentials section, specify the SYSDBA credentials for the destination CDB, and the host credentials for the destination CDB. Also, if the destination CDB is using Automatic Storage Management (ASM) to manage disk storage, you must specify the ASM credentials.

     Click Next.

     
     

     

     
     
6. On the Create Test Master Pluggable Database: Configuration page, do the following:

   In the Database Files Location section, specify the disk group where the data files of the test master PDB will be created.

   To ensure that only the source PDB data model definition is cloned (and the source PDB data is not cloned), select Exclude User Data.

   In the Access Controls and Permissions section, specify the owner and the group that must be granted read-only permissions on the data files.

   Click Next.

   
   

   

   
   
7. On the Create Test Master Pluggable Database: Post Processing page, in the Data Masking section, specify the data masking definition that you want to apply after creating the test master PDB. Data masking masks sensitive data in a database.

   For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

   In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before, and after creating the test master PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after creating the test master PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

   Click Next.

   
   

   

   
   
8. Specify an instance name for the deployment procedure. Also, specify the point in time when you want the deployment procedure to begin.

   In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the deployment procedure is scheduled, and when it succeeds.

   Click Next.

   
   

   

   
   
9. Review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

   Click Clone to submit the deployment procedure to create a test master PDB from the source PDB.

   
   

   

   
   

1. From the Targets menu, select Databases.
2. For View, select Search List. From the View menu, select Expand All.
3. Look for the source CDB (the CDB that the source test master PDB is a part of) in the list, then click the name of the test master PDB that you want to clone.
4. From the Oracle Database menu, select Cloning, then select Create Snapshot Clone.

   Alternatively, in Step 3, you can right click the name of the test master PDB that you want to clone, select Oracle Database, select Cloning, then select Create Snapshot Clone.

5. On the Source and Destination: Create Snapshot Clone Pluggable Database, do the following:

   • Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.

   • In the Credentials section, specify the SYSDBA credentials of the CDB.

   • In the Pluggable Database Definition section, specify the name of the PDB, and a display name of the PDB snapshot clone. Enterprise Manager uses the display name to identify the PDB snapshot clone target.

   • In the PDB Administrator Credentials section, specify the credentials of the Admin user account that you want to use to administer the PDB snapshot clone.

     To clone the test master PDB to a CDB different from the source CDB, select Clone the Pluggable Database into a different Container Database, then specify the destination CDB.

   • In the Credentials section, specify the CDB host credentials. Also, specify the ASM credentials of the ASM that will be used to manage disk storage.

     
     

     

     
     
6. If you do not need to specify anymore details, click Clone. This submits the deployment procedure to clone a PDB to a CDB that is deployed in a public cloud setup.

   To specify other configuration details, mask data, as well as schedule the cloning process, click Advanced.

   Follow the rest of the steps, if you have selected the Advanced option. The option to Clone is available on each page.

7. On the Create Snapshot Clone Pluggable Database: Source and Destination page, verify the details specified, and then click Next.
   
   

   

   
   
8. On the Create Snapshot Clone Pluggable Database: Configuration page, do the following:

   • In the Database Files Location section, specify the name of the Sparse disk group where the data files of the PDB snapshot clone will be created.

   • In the Advanced Configuration section, specify the storage limits for the maximum size of the PDB snapshot clone, and the maximum size of a shared tablespace within the PDB snapshot clone. By default, no limits are placed on the values for these attributes.

   • In the Miscellaneous section, select the default logging option for the tablespaces created within the PDB snapshot clone.

   • Click Next.

     
     

     

     
     
9. On the Create Snapshot Clone Pluggable Database: Post Processing section, in the Data Masking section, specify the data masking definition that you want to apply after cloning the PDB. Data masking masks sensitive data in a database.

   For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

   In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before cloning, and after cloning the PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after cloning the PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

   Click Next.

   
   

   

   
   
10. On the Create Snapshot Clone Pluggable Database: Schedule page, specify an instance name for the cloning deployment procedure. Also, specify the point in time when you want the cloning procedure to begin.

    In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the cloning deployment procedure is scheduled, and when it succeeds.

    Click Next.

    
    

    

    
    
11. On the Create Snapshot Clone Pluggable Database: Review page, review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

    Click Clone to submit the deployment procedure to create a snapshot clone of the exadata test master PDB.

    
    

    

    
    

1. From the Targets menu, select Databases.
2. For View, select Search List. From the View menu, select Expand All.
3. Look for the source CDB (the CDB that the source PDB is a part of) in the list, then click the name of the PDB from which you want to create a test master PDB.
4. From the Oracle Database menu, select Cloning, then select Create Test Master.

   Alternatively, in Step 3, you can right click the name of the PDB from which you want to create a test master PDB, select Oracle Database, select Cloning, then select Create Test Master.

5. On the Create Test Master Pluggable Database: Source and Destination page, do the following:

   • Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.

   • In the Pluggable Database Definition section, specify a name, and a display name for the test master PDB. Enterprise Manager uses the display name to identify the test master PDB target.

   • In the PDB Administrator Credentials section, specify the credentials of the admin user account that you want to use to administer the test master PDB.

   • In the Container Database section, specify the destination CDB (the CDB that the test master PDB must be a part of).

   • In the Credentials section, specify the SYSDBA credentials for the destination CDB, and the host credentials for the destination CDB. Also, if the destination CDB is using Automatic Storage Management (ASM) to manage disk storage, you must specify the ASM credentials.

     Click Next.

     
     

     

     
     
6. On the Create Test Master Pluggable Database: Configuration page, in the Database Files Location section, specify the ACFS mount point storage location where the data files of the test master PDB will be created.

   To ensure that only the source PDB data model definition is cloned (and the source PDB data is not cloned), select Exclude User Data.

   Click Next.

   
   

   

   
   
7. On the Create Test Master Pluggable Database: Post Processing page, in the Data Masking section, specify the data masking definition that you want to apply after creating the test master PDB. Data masking masks sensitive data in a database.

   For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

   In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before, and after creating the test master PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after creating the test master PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

   Click Next.

   
   

   

   
   
8. Specify an instance name for the deployment procedure. Also, specify the point in time when you want the deployment procedure to begin.

   In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the deployment procedure is scheduled, and when it succeeds.

   Click Next.

   
   

   

   
   
9. Review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

   Click Clone to submit the deployment procedure to create a test master PDB from the source PDB.

   
   

   

   
   

1. From the Targets menu, select Databases.
2. For View, select Search List. From the View menu, select Expand All.
3. Look for the source CDB (the CDB that the source test master PDB is a part of) in the list, then click the name of the test master PDB that you want to clone.
4. From the Oracle Database menu, select Cloning, then select Create Snapshot Clone.

   Alternatively, in Step 3, you can right click the name of the test master PDB that you want to clone, select Oracle Database, select Cloning, then select Create Snapshot Clone.

5. On the Source and Destination: Create Snapshot Clone Pluggable Database, do the following:

   • Specify the SYSDBA credentials for the source CDB. You can choose to use the preferred credentials, use a saved set of named credentials, or specify a new set of credentials.

   • In the Credentials section, specify the SYSDBA credentials of the CDB.

   • In the Pluggable Database Definition section, specify the name of the PDB, and a display name of the PDB snapshot clone. Enterprise Manager uses the display name to identify the PDB snapshot clone target.

   • In the PDB Administrator Credentials section, specify the credentials of the Admin user account that you want to use to administer the PDB snapshot clone.

     To clone the test master PDB to a CDB different from the source CDB, select Clone the Pluggable Database into a different Container Database, then specify the destination CDB.

   • In the Credentials section, specify the CDB host credentials. Also, specify the ASM credentials of the ASM that will be used to manage disk storage.

     
     

     

     
     
6. If you do not need to specify anymore details, click Clone. This submits the deployment procedure to clone a PDB to a CDB that is deployed in a public cloud setup.

   To specify other configuration details, mask data, as well as schedule the cloning process, click Advanced.

   Follow the rest of the steps, if you have selected the Advanced option. The option to Clone is available on each page.

7. On the Create Snapshot Clone Pluggable Database: Source and Destination page, verify the details specified, and then click Next.
   
   

   

   
   
8. On the Create Snapshot Clone Pluggable Database: Configuration page, do the following:

   • In the Database Files Location section, specify the name of the Sparse disk group where the data files of the PDB snapshot clone will be created.

   • In the Advanced Configuration section, specify the storage limits for the maximum size of the PDB snapshot clone, and the maximum size of a shared tablespace within the PDB snapshot clone. By default, no limits are placed on the values for these attributes.

   • In the Miscellaneous section, select the default logging option for the tablespaces created within the PDB snapshot clone.

   • Click Next.

     
     

     

     
     
9. On the Create Snapshot Clone Pluggable Database: Post Processing section, in the Data Masking section, specify the data masking definition that you want to apply after cloning the PDB. Data masking masks sensitive data in a database.

   For information on how to create a data masking definition, see the Oracle Data Masking and Subsetting Guide. Note that you can apply a data masking definition only if you have the Subset-Masking license pack.

   In the Custom Scripts section, for Pre Script and Post Script, specify the Oracle Software Library components that contain the scripts that you want to run before cloning, and after cloning the PDB respectively. Also, for SQL Script, specify the SQL scripts that you want to run after cloning the PDB. For Run As User, select the user account that you want to use to run the SQL scripts.

   Click Next.

   
   

   

   
   
10. On the Create Snapshot Clone Pluggable Database: Schedule page, specify an instance name for the cloning deployment procedure. Also, specify the point in time when you want the cloning procedure to begin.

    In the Notification section, select the deployment procedure states for which you want to receive e-mail notifications. For example, if you select Scheduled and Succeeded for Status for Notification, you will receive e-mail notifications when the cloning deployment procedure is scheduled, and when it succeeds.

    Click Next.

    
    

    

    
    
11. On the Create Snapshot Clone Pluggable Database: Review page, review all the details you provided. If you want to edit certain details, click Back to navigate to the required page.

    Click Clone to submit the deployment procedure to create a snapshot clone of the exadata test master PDB.

    
    

    

    
    

1. On the Databases page, you can access the Database Snap Clone wizard by following any one method:

   • Select the database that you want to clone from the list of the databases displayed. On the Database homepage, click the Database menu, select Cloning, and then select Create Snap Clone.

   • Right click on the database target name, select Database, select Cloning, and then select Create Snap Clone.

   • Right click on the database target name, select Database, select Cloning, and then select Clone Management. On the Clone Management page, in the Snap Clone Databases box, click Create.

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

   • In the Source section, launch the credentials selector by clicking the search icons for SYSDBA Database and Database Host credentials. Click OK.

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

     If you selected Now, specify or search and select the SYSASM ASM Credentials. Now refers to Live Clone.

     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.

     
     

     

     
     

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

     You can create snap clones by selecting a storage snapshot from the carousel. 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.

     
     

     

     
     
3. In the Destination Database Definition section, do the following:

   • Specify a display name.

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

       In the Hosts section, specify the Oracle Home location. The host gets specified by default. Next, select the Database Home credentials and the SYSASM ASM credentials.

     • RAC Database

       In the Hosts section, specify or select the cluster target. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

       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.

     • RAC One Node Database

       In the Hosts section, specify or select the cluster target. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

       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.

     Click Next.

     
     

     

     
     

   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.

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

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

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

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

     Click Next.

     
     

     

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

   Click Next.

   
   

   

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

   Click Next.

   
   

   

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

   Click Next.

   
   

   

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

   Click Submit.

   
   

   

   
   

To create a Test Master database, you can use either of the following solutions:

• Creating a Test Master Database Using the Clone Wizard

• Creating a Test Master Database Using EM CLI

CLONE_TYPE=DUPLICATE
COMMON_DB_DBSNMP_PASSWORD=password
COMMON_DB_SID=clonedb
COMMON_DB_SYSTEM_PASSWORD=sunrise
COMMON_DB_SYS_PASSWORD=sunrise
DATABASE_PASSWORDS=Sumrise1
COMMON_GLOBAL_DB_NAME=clonedb.xyz.com
DB_ADMIN_PASSWORD_SAME=true
DEST_LISTENER_SELECTION=DEST_DB_HOME
HOST_NORMAL_NAMED_CRED=HOST:SYSCO
IS_TESTMASTER_DATABASE=Y
USAGE_MODE = testMaster
CLOUD_TARGET = true
LISTENER_PORT=1526
ORACLE_BASE_LOC=/scratch/app
ORACLE_HOME_LOC=/scratch/app/product/11.2.0./dbhome_1
EM_USER=sys
EM_PWD=Sunrise1
SRC_DB_CRED=DB:SYSCO
SRC_DB_TARGET_NAME=ora.xyz.com
SRC_HOST_NORMAL_NAMED_CRED=HOST:SYSCO
TARGET_HOST_LIST=bl1.xyz.com

1. From the Targets menu, select Databases.
2. On the Databases page, right click on the database target that you want to enable as a test master database. From the menu that appears, select Oracle Database, select Cloning, and then select Enable Test Master.
3. On the Enable as a Test Master Database page, specify or search and select the SYSDBA database and database host credentials.
4. Specify or search and select the parent database from which the database has been cloned. This provides better lineage tracking.
5. Specify or select a data masking definition if you want to mask data in the cloned database before enabling it as a test master.
6. In the Custom Scripts section, you can select Software Library components that contain post cloning scripts. The clone database can also be customized by executing the post cloning SQL script.
7. In the Access Controls and Permissions section, specify the owner and group that should be given read-only permissions on the datafiles.
8. Click Submit.
   
   

   

   
   

1. From the Targets menu, select Databases.
2. On the Databases page, right click on the database target that you want to disable as a test master database. From the menu that appears, select Oracle Database, select Cloning, and then select Disable Test Master.
3. On the Disable Test Master page, specify or search and select the SYSDBA database and database host credentials.
4. The Exadata Snapshot Clone Databases sections lists the database snapshot clones that will be deleted as part of the process of disabling the test master.
5. Click Submit. This action resets the datafiles to read-write mode and restarts the database in open mode. You can later make further changes to the database and then enable it as test master again, if you choose to.
   
   

   

   
   

To create a Test Master PDB, you can use either of the following solutions:

• Creating a Test Master Pluggable Database Using the Clone Wizard

• Creating a Test Master Pluggable Database Using EM CLI

SRC_PDB_TARGET=cdb_prod_PDB
SRC_HOST_CREDS=NC_HOST_SCY:SYCO
SRC_CDB_CREDS=NC_HOST_SYC:SYCO
SRC_WORK_DIR=/tmp/source
DEST_HOST_CREDS=NC_SLCO_SSH:SYS
DEST_LOCATION=/scratch/sray/app/sray/cdb_tm/HR_TM_PDB6
DEST_CDB_TARGET=cdb_tm
DEST_CDB_TYPE=oracle_database
DEST_CDB_CREDS=NC_HOST_SYC:SYCO
DEST_PDB_NAME=HR_TM_PDB6
IS_CREATE_AS_TESTMASTER=true
MASKING_DEFINITION_NAME=CRM_Masking_Defn

1. On the Databases page, you can access the CloneDB wizard by following any one method:

   • Select the database that you want to clone from the list of the databases displayed. On the Database home page, click the Database menu, select Cloning, and then select Create CloneDB.

   • Right click on the database target name, select Database, select Cloning, and then select Create CloneDB.

   • Right click on the database target name, select Database, select Cloning, and then select Clone Management. On the Clone Management page, in the CloneDB Databases box, click Create.

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

   • In the Source section, launch the credentials selector by selecting the search icons for SYSDBA Database and Database Host 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.

     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.

3. In the Destination Database Definition section, do the following:

   • Specify a display name.

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

   • The RAC Database type is selected by default.

     In the Hosts section, specify or select the cluster target. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

     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.

     
     

     

     
     

     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.

     Click Next.

4. 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. The File System option is selected by default.

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

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

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

     Click Next.

     
     

     

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

   
   

   

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

   Click Next.

   
   

   

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

   Click Next.

   
   

   

   
   
8. On the Create CloneDB Database: Review page, verify the details of the source database, the data source of the clone, and the destination database.

   Click Submit.

   
   

   

   
   

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.

1. From the Targets menu, select Databases.
2. On the Databases page, you can access the Database Snap Clone wizard by following any one method:

   • Select the test master database that you want to clone from the list of the databases displayed. On the Database homepage, click the Database menu, select Cloning, and then select Create Snapshot Clone.

   • Right click on the test master database target name, select Database, select Cloning, and then select Create Snapshot Clone.

3. On the Create Exadata Snapshot Clone Database: Source and Destination page, do the following:

   • In the Source section, launch the credentials selector by clicking the search icons for SYSDBA Database and Database Host credentials. Click OK.

   • In the Data Time Series section, Now is selected by default.

     Now refers to Live Clone.

     Specify or select the SYSASM ASM credentials.

     
     

     

     
     
4. In the Destination Database Definition section, do the following:

   • Specify a display name.

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

       In the Hosts section, specify the Oracle Home location. The host gets specified by default. Next, select the Database Home credentials and the SYSASM ASM credentials.

     • RAC Database

       In the Hosts section, the cluster field is auto selected from the parent database and disabled. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

       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.

     • RAC One Node Database

       In the Hosts section, specify or select the cluster target. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

       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.

     Click Next.

     
     

     

     
     

   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.

5. On the Create Exadata Snapshot Clone Database: Configuration page, do the following:

   • In the Database Files Location, specify the Sparse disk group and the redo log file size.

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

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

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

     Click Next.

     
     

     

     
     
6. On the Create Exadata Snapshot 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.

   Click Next.

   
   

   

   
   
7. On the Create Exadata Snapshot 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.

   Click Next.

   
   

   

   
   
8. On the Create Exadata Snapshot 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

   
   

   

   
   

   Click Next.

9. On the Create Exadata Snapshot Database: Review page, verify the details of the source database, the data source of the clone, and the destination database.

   Click Submit.

   
   

   

   
   

To register storage servers for:

• Sun ZFS Storage Server: See Registering a Sun ZFS Storage Server.

• Solaris File System (ZFS): See Registering a Solaris File System (ZFS) Storage Server.

You must create one or more resource providers which include:

• PaaS Infrastructure Zones: See Creating a PaaS Infrastructure Zone.

• Database Pool: See Creating a Database Pool for Database as a Service

1. From the Enterprise menu, select Cloud, then select Cloud Home. From the Oracle Cloud menu, select Setup, then select the Database Service family on the left panel. Click the Test Master Databases tab.
2. To create a test master from a live standby database, click Add and select a standby database that is to be designated as the test master. The newly added database appears in the Test Master Database page and can be used to create the snap clone database instances.

1. On the Storage Registration page, in the Details section, select the Databases tab, and then select the database from the table which you want to use for Snap Clone, and then click Enable Snap Clone.

   The Supported column in the table shows if the databases listed support Snap Clone or not.

   Note: If a database listed shows the Not Supported icon in the Supported column, you can view the Message column from the View menu. This column displays the reason. A possible reason is that the data files are missing on the storage server and may be located on either local disk or some other unregistered storage server. Another reason could be that the data files reside on another storage that is not synchronized.

2. Once snap clone has been successfully enabled, a confirmation message appears. Click OK.

   To view all the files located on the storage server, click Show Files. To view all the projects (aggregates), volumes, and snapshots in the storage server, select the Contents tab.

1. You can access the Database Provisioning page using any of the following ways:

   • From the Enterprise menu, select Cloud, and then select Cloud Home. On the Cloud home page, click Oracle Cloud, select Setup, and then select Data Sources. On the Database: Data Sources page, in the Data Profiles tab, click Create.

   • From the Enterprise menu, select Provisioning and Patching, and then select Database Provisioning. On the Database Provisioning page, in the Profiles section, click Create.

   • From the database target home page, click Oracle Database, select Provisioning, and then select Create Provisioning Profile.

2. On the Reference Target page, click the search icon to select a target.
3. In the Search and Select:Targets display box, select the database you want to create a profile for, and then, click Select.

   Note:

   Ensure that the database you select is enabled for Snap Clone.

4. On the Reference Target page, select the following:

   • Data Content

   • Structure and Data to include physical and structural files from the database

   • Create

   • Storage Snapshots

5. In the Credentials section, select the database. In the Credentials column, you can select Named Credentials and then select a credential name from the Credential Name column (or) select Preferred Credentials. Click Next.
6. On the Create Database Provisioning Profile: Page, in the Profile Information section, do the following:

   • Specify or select a profile location in the software library where the database profile will be created.

   • Specify a unique profile name.

     For example:
     Snap Clone Profile for HR database
     

   • Add a description for the profile.

   • Verify the profile version and the vendor.

   • Add any additional notes such as host name, database, data content, data content mode, and the like.

7. In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time. You can also choose to repeat the creation of the provisioning profile, and set a repeat time.
8. In the Purge Policy section, you have three options:

   • None. Select this option you do not want to purge any data collected.

   • Snapshots. This option enables you to specify the maximum number of snapshots that can be purged.

   • Day(s). This option enables you to specify the number of days after which the data component should be purged.

9. Specify or select a working directory. Click Next.
10. On the Review page, ensure that the selections you have made in the previous pages are correctly displayed and click Submit. Otherwise, click Back repeatedly till you reach the page where you want to make changes. Click Cancel to abort the provisioning profile creation.

    Once you have submitted the provisioning profile creation job, manually refresh the page if View Data has been set to Real Time: Manual Refresh. Else, set View Data to reload after a specific period of time, and then select an execution step from the Procedure Steps tree on the left pane to view the details.

    To view the submitted jobs, select the Procedure Activity link in the Data Profiles tab.

1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role. The EM_SSA_ADMINISTRATOR role you select must also have the EM_STORAGE_OPERATOR privileges.
2. From the Enterprise menu, select Cloud, then select Cloud Home. The Cloud Home page appears. From the Oracle Cloud menu, select Setup, then select Getting Started.
3. Click the Setup link next to the Databases option in the left panel. Select Database from the drop down menu.
4. Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.

   Figure 24-1 Create Service Template: General (Snap Clone)

   
   
   
5. Enter a name and description for the service template. The description must be unique and provide information on the type of service template being created.
6. In the Source Identification section, select the Using Profile radio button, click the Search icon and select the test master database based on the snap clone profile you created.
7. In the Profile Version field, you can select either of the following:

   • Latest: This ensures that the latest profile is always used by the self service user.

   • Selected by user at request time: If this option is selected, the self service user can select the profile to be used when creating a service request.

8. In the Database Definition region, specify the following:

   • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the number of nodes.

   • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

     • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

       The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

       For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

     • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

   • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

9. In the Zones region, click Add to select a PaaS Infrastructure Zone into which the database instance is to be provisioned. Click Assign Pool. Select a pool from the list and assign this pool to the PaaS Infrastructure Zone. The database will be provisioned into this pool.
10. After you have selected the zone and the pool, the host target is populated in the Reference Host field.
11. Click Next. The Database Cloud Self Service Portal Setup: Database page appears.

    Figure 24-2 Create Service Template: Database (Snap Clone)

    
    
    
12. In the Reference Host region, the name of the PaaS Infrastructure zone, the database pool, and the reference host you have selected in the Database Cloud Self Service Portal Setup: General page are displayed.

    The database values such as the location of the file system and the listener port you select must be available on the reference host.

13. Specify the following details:

    • Storage: You can configure the volumes that will be used by the database:

      • Mount Point Prefix: The mount point prefix can be the Same for All Volumes or Different for Each Volume.

        Specify the prefix for the new mount point for the database being provisioned. 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>. If the Mount Point Prefix is different for each volume, specify a different value for each volume,

      • Writable Space: The Writable Space can be the Same for All Volumes or Different for Each Volume.

        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.

    • Enable Archiving: If this check box is selected, the database will not be shut down during a refresh. This allows self service users to schedule backups and restore operations without shutting down the database.

    • Snapshot Policy: Snapshots are sets of historical data for specific time periods. By default, Oracle Database automatically generates snapshots of the performance data once every hour and retains the statistics in the workload repository for 8 days. Select the Allow the user to take snapshots for the new database checkbox and specify the Maximum Number of Snapshots that can be taken.

      Snapshots can be created for a specific point in time. The number of snapshots is determined by the value specified by the self service administrator in the Maximum Number of Snapshots field. Once the snapshot has been taken, the database can be restored to a specific snapshot taken a particular point in time. For example, if there are several snapshots such as snap1, snap2, and snap3, if the database is restored to snap2, snap3 will be deleted.

    • In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.

    • Administrator Credentials: Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.

    • Non Administrator Credentials: Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password.

    • Master Account Privileges: Enter the name of the Master Account. You can specify the privileges that are to be provided to the master account user by specifying them in the Privileges field.

14. Click Next. The Create Service Template: Initialization Parameters page appears.

    Figure 24-3 Create Service Template: Initialization Parameters (Snap Clone)

    
    
    
15. In this page, you can specify the following:

    • Database Sizes: Select the database sizes that are to be supported by this service template.

      Note: The database size definitions must have already been defined using the emcli create_database_size command. See Database Size EM CLI Verbs for details.

      You can select sizes such as small, medium, and large. Each database size has a specific memory, storage, CPU cores, and units. Select a size and select Include in Template to associate it with the service template. Click Default to designate it as the default database size.

    • Initialization Parameters: You can configure the values of various initialization parameters that affect the operation of the database instance. Select a parameter and click the Set icon to modify the value of the parameter.

16. Click Next. The Create Service Template: Customization page appears. Specify the custom scripts that need to be executed before and after the database is created. See Pre and Post Request Creation / Deletion Scripts for details.

    You can also specify a custom Post SQL Script and select the user who can run the script. For more details, see Selecting the Post SQL Script.

17. In the Target Properties region, you can specify global target properties such as Location, Department, Line of Business, and so on. These properties will be applied to the database clones that are created. You can do the following:

    • Mark a property as mandatory by selecting the Required check box. If a property is marked as mandatory, the self service user must specify a value for this property while requesting a database.

    • Lock a property. When a property is locked, the self service user cannot modify the value of this property while requesting a database.

18. Click Next. The Create Service Template: Roles page appears. Click Add to select the SSA user roles to which this service template will be available. All users belonging to the selected role can use this service template. Click Next.
19. The Create Service Template: Review page appears. Click Create. The newly created service template will appear in the Database Cloud Self Service Portal Setup: Service Templates page.

1. First, you must make sure that all the prerequisites are met. See Getting Started.
2. The next step is to identify the production database and the physical standby database. The production database is prod1 and the standby database as prod1stb.
3. Next, you must register the storage server. This step validates the storage and discovers prod1stb on the storage server. See Registering Storage Servers.
4. You must then create one or more PaaS Infrastructure Zones and one or more database pools. See Creating Resource Providers
5. Then, you must define the quota that you wish to allocate to the self service users. See Defining Quotas.
6. The next step is to designate the standby database, prod1stb as the test master.
7. Next, you must enable prod1stb for snap clone. This allows creation of snap clones using snapshot technology. See Enabling the Test Master for Snap Clone.
8. The next step is to create a snapshot profile from prod1stb. See Creating a Database Provisioning Profile Using Snapshots

   While creating the profile, specify the Start Date as 05/15/2015, the Repeat schedule as Every N Days and the Frequency as Every 1 day. Specify the End By date as 05/20/2015. A new version of the snapshot profile will be created every day from the Start date of 05/15/2015.

   In the Purge Policy field, specify the Number of Snapshots as 5. This will ensure that after 5 versions of the snapshot are created, the first or oldest one will be purged.

9. To make this profile available to the self service user, you must create a service catalog entry or a service template. Create a template called Snap Clone Template. See Creating Service Template Using Snap Clone Profile. Set the Profile Version field to Selected by user at request time. The self service user can choose the profile version that is to be used to create the snap clone.
10. The self service user can then use the Snap Clone Template, select a version of the profile and use it to create the snap clone. See Requesting a Database. As and when a new version of the profile is available (see Creating and Refreshing Snapshots of the Test Master), the self service user can choose to refresh the profile to the latest version. See Refresh an RMAN Database.

    Based on the Purge Policy which is set to 5 snapshots, the older versions of the snapshots will be deleted. But if the self service user has a database that is using that snapshot, the profile cannot be deleted until the self service user has refreshed the profile to the latest version.

1. From the Enterprise menu, select Cloud, then select Cloud Home. From the Oracle Cloud menu, select Setup, then select the Database Service family on the left panel. Select Data Sources and click on the Test Master Databases tab.
2. To create a new test master, click on the Create menu. Select a production database from which the test master is to be created and click Select. The Clone Database: Source and Destination page appears.
3. On the Create Test Master Database: Source and Destination page, do the following:

   • In the Source section, launch the credentials selector by selecting the search icons for SYSDBA Database and Database Host credentials. Click OK.

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

     If you selected Now, specify or search and select the SYSASM ASM Credentials. 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 a specific time between the selected backup or snapshot and the next (or latest point of source). The backups or dumps are created at specific intervals and the test master that is based on these will reflect the production database at specific points in time. To reflect the latest data in the production database, the test master needs to be periodically refreshed.

4. In the Destination Database Definition section, do the following:

   • Specify a display name.

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

       In the Hosts section, specify the Oracle Home location. The host gets specified by default. Next, select the Database Home credentials and the SYSASM ASM credentials.

     • RAC Database

       In the Hosts section, specify or select the cluster target. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

       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.

     • RAC One Node Database

       In the Hosts section, specify or select the cluster target. The Oracle Home location gets specified by default. Next, specify the Database Host credentials, and the SYSASM ASM credentials.

       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.

       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.

     Click Next.

5. On the Create Test Master Database: Configuration page, do the following.

   • Database Files Location: Specify the location in which the data files, temporary files, redo log files, and control files will be created. You must specify a mount point which must be present on a registered storage volume so that the self service administrator can enable this test master for snap clone.

     You can select:

     • File System: The Oracle Database File System creates a standard file system interface on top of files and directories that are stored in database tables. If you select this option, you must specify or select the Location of the File System. You can specify a common location for all the files or you can select the Use Oracle Optimal Flexible Architecture-compliant directory structure (OFA) checkbox and specify different locations for data files, redo log files, and so on.

     • Automatic Storage Management: The Oracle Automatic Storage Management (ASM) is a volume manager and a file system for database files that supports single-instance and RAC configurations. ASM groups the disks in your storage system into one or more disk groups. If you select ASM, select a common location for the database files.

   • Recovery Files Location: To simplify the management of backup and recovery files, a fast recovery area can be created for your database. The fast recovery area can be a ASM disk group or a file system that provides a centralized disk location for backup and recovery file.To allow self service users to schedule backups and perform restore operations, you can select the Use Fast Recovery Area checkbox and specify the location of the Fast Recovery Area and the Fast Recovery Size. The amount of disk space to allocate for the fast recovery area depends on the size and activity levels of your database.

   • Listener Configuration: Click Add to add one or more listener targets that are to be associated with the new database.

   • Database Credentials: Specify the passwords for the administrative users (SYS, SYSTEM and DBSNMP) of the new database being cloned. You can choose to use the same password for all the schemas or different passwords for each schema.

6. Click Next. Some values such as db_block_size cannot be modified.
7. Click Next. The Create Test Master Database: Post Processing page appears. Specify the following details:

   • 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. After selecting the masking definition, select the In-Place Masking option to generate a script to replace the sensitive data in-place with masked data on the cloned database. For more details on creating a masking definition, see the Enterprise Manager Database Testing Guide.

     Note:

     The masking definition can be used only when you have the Oracle Data Masking and Subsetting license pack.

   • Specify the custom scripts that need to be executed before and after the database is created. See Pre and Post Request Creation / Deletion Scripts for details.

   • Specify the path for the SQL script which allows you to run the script against the newly cloned database as a user such as SYS, SYSTEM, or any other specified user. The SQL script allows you to customize the cloned database. For more details, see Selecting the Post SQL Script.

   • Select the Create Data Profile check box if you wish to create a database provisioning profile that is based on the test master. These profiles can be refreshed automatically or at specified intervals. Different versions of the profile are saved and are available to the self service user until they are purged. This ensures that the test master is periodically updated and the latest data can be used by the self service user. You can create a database provisioning profile if:

     • This version of the test master must be available for cloning in future, even after the test master has be refreshed.

     Enter the following details for the profile:

     • Profile Type: Select RMAN Backup or RMAN Image.

     • Backup Mode: If you select the RMAN Backup profile type, you can select one of the following: Select Online Backup to make a backup while the database is up and running. Select Offline Backup to shutdown the database for the duration of backup and bring it back once the backup is complete.

     • Backup Location: Enter the directory path that already contains a backup location.

     • Backup File Tag: Backup files will be tagged with the tag specified here.

     • Location: Select the directory for the backup location.

     • Enter the name, description, version number, vendor, and additional notes.

     • Purge Policy Type: This can be None, Snapshots, or Days. If you select None, the profiles will need to be manually deleted as required. If you select Snapshots, specify the maximum number of snapshots that can be retained. If you select Day(s), specify the number of days the profile can be retained.

     • Schedule: Specify whether the profile needs to be created immediately or at a later date.

8. Click Next. Specify the schedule for the creation of the test master. It can be created immediately (if physical standby used, it is created immediately and automatically refreshed) or can be created at a later date / time and refreshed at specified intervals.
9. Click Next. Review the information entered so far and click Submit to create the test master. After the test master has been created, you can refresh the test master as required to create a new version of the profile on which the test master is based.

1. From the Enterprise menu, select Cloud, then select Cloud Home. From the Oracle Cloud menu, select Setup, then select the Database Service family on the left panel. Click the Test Master Databases tab.
2. Select the test master that is to be refreshed and click Refresh. The Refresh Database: Source and Destination page appears.
3. Select the Prior Point in Time option and select the backup to which the test master is to be refreshed. You can modify the source and destination credentials.
4. If you select the Now option, you will see the following screen.

   Figure 24-4 Test Master Refresh: Source and Destination (Now)

   
   
   

   Click Next. The Configuration page appears.

   Figure 24-5 Test Master Refresh: Configuration

   
   

   

   
   
5. Specify the Mount Point Prefix for the storage volume that will be used by the clone database and the database credentials. Click Next.
6. In the Initialization Parameters page, edit the values of various initialization parameters that affect the operation of the database instance. Click Next.
7. In the 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. After selecting the masking definition, select the In-Place Masking option to generate a script to replace the sensitive data in-place with masked data on the cloned database. For more details on creating a masking definition, see the Enterprise Manager Database Testing Guide

     Note:

     The masking definition can be used only when you have the Oracle Data Masking and Subsetting license pack.

   • Specify the custom scripts that need to be executed before and after the database is created. See Pre and Post Request Creation / Deletion Scripts for details.

   • Specify the path for the SQL script which allows you to run the script against the newly cloned database as a user such as SYS, SYSTEM, or any other specified user. The SQL script allows you to customize the cloned database. For more details, see Selecting the Post SQL Script.

8. Click Next. Specify the schedule for the creation of the test master. It can be created immediately (if physical standby used, it is created immediately and automatically refreshed) or can be created at a later date / time and refreshed at specified intervals.
9. Click Next. Review the information entered so far and click Submit to refresh the test master.

   Note:

   You can use the emcli refresh_database command to refresh the database. See Database Profile EM CLI Verbs for details.

1. From the Enterprise menu, select Cloud, then select Cloud Home. From the Oracle Cloud menu, select Setup, then select the Database Service family on the left panel. Click Data Sources.
2. In the Data Sources page, click the Data Profiles tab. The list of the profiles is displayed.

   Figure 24-6 Refresh Snap Shot Profile

   
   
   
3. Select the profile to be refreshed and click Refresh Profile. A confirmation message is displayed. Click Yes to submit the refresh profile job.

1. First, you must make sure that all the prerequisites are met. See Getting Started.
2. Next, you must register the storage server. See Registering Storage Servers.
3. You must then create one or more PaaS Infrastructure Zones and one or more database pools. See Creating Resource Providers.
4. Then, you must define the quota that you wish to allocate to the self service users. See Defining Quotas.
5. The next step is to identify the production database (prod1) and create an RMAN backup prod1_backup.
6. Create a test master (testmaster1) based on prod1_backup. See Creating a Discretely Synchronized Test Master.
7. Next, you must enable testmaster1 for snap clone. This allows creation of snap clones using snapshot technology. See Enabling the Test Master for Snap Clone.
8. Next, you must create a profile (snap_profile) that is based on testmaster1. See Creating a Database Provisioning Profile Using Snapshots
9. To make this profile available to the self service user, you must create a service catalog entry or a service template. Create a template called Snap Clone Template1. See Creating a Service Template Using Snap Clone Profile. In the Service Template, the Profile Version field is set to Latest. This will ensure that the self service user will always use the latest version of the profile to create database instances.
10. The self service user can then use the Snap Clone Template1 to create the snap clone. See Requesting a Database.
11. To get the latest production data, the self service administrator refreshes TestMaster1. See Refreshing the Test Master Database.
12. Since the test master now contains updated data, a new revision of the profile must be created. See Refreshing the Snap Shot Profile.
13. Now that a new revision of the profile (snap_profile) is available, the self service user can refresh his database instance to get the latest production data. See Refresh an RMAN Database. The storage space that was used by the older version of the test master will be reclaimed by the refreshed test master.

1. You can access the Database Provisioning page using either of the following ways:

   • From the Enterprise menu, select Cloud, and then select Cloud Home. On the Cloud home page, click Oracle Cloud, select Setup, and then select Data Sources. On the Database: Data Sources page, in the Data Profiles tab, click Create.

   • From the Enterprise menu, select Provisioning and Patching, and then select Database Provisioning. On the Database Provisioning page, in the Profiles section, click Create.

   • From the database target home page, click Oracle Database, select Provisioning, and then select Create Provisioning Profile.

2. On the Reference Target page, click the search icon to select a target.
   
   

   

   
   
3. In the Search and Select: Targets display box, select the database you want to create a profile for, and then, click Select.
   
   

   

   
   
4. On the Reference Target page, select the following:

   • Data Content

   • Structure and Data to include physical and structural files from the database or Structure Only to include only the structural files in the template.

   • Create

   • RMAN Database Image

   
   

   

   
   
5. In the Credentials section, select the database. In the Credentials column, you can select Named Credentials and then select a credential name from the Credential Name column (or) select Preferred Credentials. Click Next.
   
   

   

   
   
6. On the Content Options page, specify the backup location for the RMAN image mode. By default, the backup location selected is Offline Backup. You can choose Online Backup only if it is enabled.

   Then, select Directory for the backup location and enter the directory path, or select Fast Recovery Area, which already contains a backup location.

   
   

   

   
   

   Note:

   • Ensure that the specified location is accessible to all the nodes in the database pool.

   • Depending on the database version, the profile (image) may need to be manually staged on an NFS shared location.

   Click Next.

7. On the Create Database Provisioning Profile: Page, in the Profile Information section, do the following:

   • Specify or select a profile location in the software library where the database profile will be created.

   • Specify a unique profile name.

     For example:
     RMAN Database Image for HR database
     

   • Add a description for the profile.

   • Verify the profile version and the vendor.

   • Add any additional notes such as host name, database, data content, data content mode, and the like.

     
     

     

     
     
8. In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time. You can also choose to repeat the creation of the provisioning profile, and set a repeat time.
9. In the Purge Policy section, you have three options:

   • None. Select this option you do not want to purge any data collected.

   • Snapshots. This option enables you to specify the maximum number of snapshots that can be purged.

   • Day(s). This option enables you to specify the number of days after which the data component should be purged.

     
     

     

     
     
10. Specify or select a working directory. Click Next.
11. On the Review page, ensure that the selections you have made in the previous pages are correctly displayed and click Submit. Otherwise, click Back repeatedly till you reach the page where you want to make changes. Click Cancel to abort the provisioning profile creation.
    
    

    

    
    

    Once you have submitted the provisioning profile creation job, manually refresh the page if View Data has been set to Real Time: Manual Refresh. Else, set View Data to reload after a specific period of time, and then select an execution step from the Procedure Steps tree on the left pane to view the details.

    To view the submitted jobs, select the Procedure Activity link in the Data Profiles tab.

1. Log into Enterprise Manager as a user with the EM_SSA_ADMINISTRATOR role.
2. From the Enterprise menu, select Cloud, then select Cloud Home. The Cloud Home page appears. From the Oracle Cloud menu, select Setup, then select Getting Started.
3. Click the Setup link next to the Databases option in the left panel. Select Database from the drop down menu.
4. Click the Service Templates link. The Service Templates page appears. Click Create. The Create Service Template: General page appears.

   Figure 24-7 Create Service Template: General (CloneDB)

   
   

   

   
   
5. Enter a name and description for the service template. The description must be unique and provide information on the type of service template being created.
6. Click the Search icon next to the Profile field and select the test master database based on the RMAN Image profile.
7. In the Profile Version field, you can select either of the following:

   • Latest: This ensures that the latest profile is always used by the self service user.

   • Selected by user at request time: If this option is selected, the self service user can select the profile to be used when creating a service request.

8. In the Database Definition region, select the following:

   • Create: Select CloneDB Database option. Each file is copied as an image copy which is a bit-for-bit copy of a database file created on disk. Image copies are identical to copies created with operating system commands such as cp on Linux or COPY on Windows, but are recorded in the RMAN repository and so are usable by RMAN. This option allows you reduce the amount of storage and enables rapid creation of multiple databases.

     If you are doing an online backup, you must ensure that your Test Master database is in ARCHIVELOG mode and that all of the necessary archived redo log files are saved and accessible to the CloneDB database environment. If you are doing an offline backup, you must ensure that the backup copies are accessible to the CloneDB database environment.

   • Type: This can be Single Instance or Real Application Cluster (RAC). If you select RAC, specify the Number of Nodes.

   • Database SID: This is an optional field. You can select Specify Prefix or Specified by User at Request Time.

     • Specify Prefix: If you choose this option, enter a prefix that is to be used to generate a unique System Identifier (SID) at the time of database creation. The prefix helps to identify databases created using this service template. The prefix can be a maximum of 6 characters.

       The new database name generated will be based on the SID Prefix specified here. For example, if the prefix is specified as MYDB, the SID for the new database is generated as MYDB0000, MYDB0001, MYDB0002, and so on.

       For existing databases (running databases and in progress requests), a unique SID name is generated for single instance databases, or a unique name is generated for real application cluster databases. For example, if the existing SIDs running on a host are MYDB0000, MYDB0001, MYDB0002 And In progress are MYDB0003, MYDB0004, the new SID or database name generated for the new request is MYDB0005.

     • Specified by User at Request Time: If you choose this option, you can leave this field blank and specify the SID when you are making a database request.

   • Domain Name: This is an optional field. Enter a Domain Name to be used for the new database being created. You must ensure that the domain name does not contain a preceding "." (dot).

9. In the Pools and Zones region, click Add to select a PaaS Infrastructure Zone into which the database instance is to be provisioned. Click Assign Pool. Select a pool from the list and assign this pool to the PaaS Infrastructure Zone. The database will be provisioned into this pool.
10. After you have selected the zone and the pool, the host target is populated in the Reference Host field.
11. In the Reference Host region, the name of the PaaS Infrastructure zone, the database pool, and the reference host you have selected in the Database Cloud Self Service Portal Setup: General page are displayed.
12. In the Location field, specify the location for the database files. This must be an NFS location.
13. To simplify the management of backup and recovery files, you can optionally create a fast recovery area for your database. Select the Enable Fast Recovery Area checkbox to specify the location in which recovery related files must be stored. The fast recovery area can be a file system that provides a centralized disk location for backup and recovery file. Specify the location of the Fast Recovery Area and the Fast Recovery Size. The amount of disk space to allocate for the fast recovery area depends on the size and activity levels of your database.

    If the Enable Archiving check box is selected, the database will not be shut down during a refresh. This allows self service users to schedule backups and restore operations without shutting down the database.

14. If you have chosen to create a CloneDB database, you can optionally allow the user to take a backup copy of the database. Select the Allow the user to take backup copy for the new database checkbox. Specify the maximum number of backups allowed and the backup location.
15. In the Listener Port field, specify listener port number that is to be associated with the new database. If you have selected a 11.2 or later RAC database, you must specify the scan port number.
16. Specify the Administrator Credentials. Specify passwords for the system schemas of the new database. These schemas will not be available to the EM_SSA_USERS. You can choose to use the same password for all the schemas or different passwords for each schema. If these values are not specified, default values will be used and the EM_ADMINISTRATOR can change them.
17. Apart from the system schemas, if you want to restrict access to other schemas, you can select them in the Non-Administrator Credentials region and specify the password. These schemas will be locked and the EM_SSA_USERS cannot access them. Click Next.
18. Click Next. The Create Service Template: Initialization Parameters page appears. In this page, you can configure the values of various initialization parameters that affect the operation of the database instance. Select the parameter and click the Set icon to modify the value of the parameter.
19. Click Next. The Create Service Template: Customization page appears. Specify the custom scripts that need to be executed before and after the database is created. See Pre and Post Request Creation / Deletion Scripts for details.
20. In the Target Properties region, you can specify global target properties such as Location, Department, Line of Business, and so on. You can do the following:

    • Mark a property as mandatory by selecting the Required check box. If a property is marked as mandatory, the self service user must specify a value for this property while requesting a database.

    • Lock a property. When a property is locked, the self service user cannot modify the value of this property while requesting a database.

21. Click Next. The Create Service Template: Roles page appears. Click Add to select the SSA user roles to which this service template will be available. All users belonging to the selected role can use this service template. Click Next.
22. The Create Service Template: Review page appears. Click Create. The newly created service template will appear in the Database Cloud Self Service Portal Setup: Service Templates page.