22 Creating Snap Clones

This chapter describes how to create snap clones. It contains the following sections:

22.1 About Data Lifecycle Management

The Enterprise Manager Data Lifecycle Management solution provides a complete end to end automated flow to move data from the production environment to the test environment.

In a production environment, the database administrator will first take a backup of this production database, create a test master database from the backup, then mask the sensitive data, and finally create clones from the test master. The clones then need to be refreshed as required to ensure that the data is in sync with the production data. With the Data Lifecycle Management solution, this process is completely automated and can be performed either from the Cloning Dashboard or through the Self Service Portal.

22.2 About Snap Clones

Snap Clone provides a storage agnostic approach to creating rapid and space efficient clones of large databases. Clones of the production database are often required for test and development purposes, and it is difficult and time consuming to create these clones, especially if the databases are huge.

Enterprise Manager offers Snap Clone as a way to address this issue, so that thin clones can be created from production databases by using the copy on write technology available in some storage systems. This means that these clones take up little space initially (about 2 GB of writable space required for a thin clone of a multi-terabyte database), and will grow as inserts, updates and deletes are performed. Enterprise Manager offers two solutions with snap clone:

  • Hardware Solution: Vendor specific hardware solution which supports NetApps, Oracle Sun ZFS storage appliance, EMC VMAX, and VNX.

  • Software Solution: Storage agnostic software solution that supports all NAS and SAN storage devices. This is supported through use of the ZFS file system, and the CloneDB feature.

The main features of snap clone are:

  • Self Service Driven Approach: Empowers the self service user to clone databases as required on an ad-hoc basis.

  • Rapid Cloning: Databases can be cloned in minutes and not in days or weeks.

  • Space Efficient: This features allows users to significantly reduce the storage footprint.

22.3 Registering and Managing Storage Servers

Note:

If you are creating thin clones from a snap clone based profile, you must register and manage the storage servers such as NetApp, Sun ZFS, or EMC. See Creating Snap Clones for details.

This section describes the following:

22.3.1 Overview of Registering Storage Servers

Registering a storage server, such as NetApp storage server, Sun ZFS storage server, or EMC storage server in Enterprise Manager enables you to provision databases using the snapshot and cloning features provided by the storage.

The registration process validates the storage, and discovers the Enterprise Manager managed database targets on this storage. Once the databases are discovered, you can enable them for Snap Clone. Snap Clone is the process of creating database clones using the Storage Snapshot technology.

Note:

Databases on Windows operating systems are not supported.

22.3.2 Before You Begin

Before you begin, note the following:

  • Windows databases are not discovered as part of storage discovery. This is because the Windows storage NFS collection does not happen at all. NFS collection is also not supported on certain OS releases, and thus databases on those OS releases cannot be Snap Cloned. For further details please refer to the My Oracle Support note 465472.1. Also, NAS volumes cannot be used on Windows for supporting Oracle databases.

  • Snap Clone is supported on Sun ZFS Storage 7120, 7320, 7410, 7420 and ZS3 models, NetApp 8 hardware in 7-mode and c-mode, EMC VMAX 10K and VNX 5300, and Solaris ZFS Filesystem.

  • Snap Clone supports Sun ZFS storage on HP-UX hosts only if the OS version is B.11.31 or higher. If the OS version is lower than that, the Sun Storage may not function properly thereby Snap Clone gives unexpected results.

  • By default, the maximum number of NFS file systems that Enterprise Manager discovers on a target host is 100. However, this threshold is configurable. You can also choose a list of file systems to be monitored if you do not want all the extra file systems to be monitored.

    The configuration file $agent_inst/sysman/emd/emagent_storage.config for each host agent contains various storage monitoring related parameters.

    To configure the threshold for the NFS file systems, you need to edit the following parameters:

    Collection Size:START
    Disks=1000
    FileSystems=1000
    Volumes=1000
    Collection Size:END 
    

    If you choose to provide a list of file systems to be monitored, it can be provided between the following lines:

    FileSystems:START

    FileSystems:END

    
    

    Restart the Management Agent and refresh the host configuration for the changes to this configuration file to be effective.

  • If the OMS Repository is running on RDBMS with 11.1.0.7.0 and AL32UTF8 character set, you need to apply patch 11893621.

22.3.3 Prerequisites for Registering Storage Servers

Before you register a storage server, follow the prerequisites outlined in the following sections:

22.3.3.1 Configuring Storage Servers

Before you register a storage server, you require the following privileges and licenses to successfully use Snap Clone:

Note:

Enterprise Manager Cloud Control 13c supports NetApp, Sun ZFS, Solaris File System (ZFS) and EMC storage servers.

Configuring NetApp Hardware

This section consists of the following:

Obtaining NetApp Hardware Privileges

Privileges is a generic term. NetApp refers to privileges as Capabilities.

For NetApp storage server, to use Snap Clone, assign the following privileges or capabilities to the NetApp storage credentials:

Note:

You can assign these capabilities individually or by using wildcard notations. For example:

'api-volume-*', 'api-*', 'cli-*' 
  • api-aggr-list-info

  • api-aggr-options-list-info

  • api-file-delete-file

  • api-file-get-file-info

  • api-file-read-file

  • api-license-list-info

  • api-nfs-exportfs-append-rules

  • api-nfs-exportfs-delete-rules

  • api-nfs-exportfs-list-rules

  • api-nfs-exportfs-modify-rule

  • api-snapshot-create

  • api-snapshot-delete

  • api-snapshot-list-info

  • api-snapshot-reclaimable-info

  • api-snapshot-restore-volume

  • api-snapshot-set-reserve

  • api-system-api-get-elements

  • api-system-api-list

  • api-snapshot-set-schedule

  • api-system-cli

  • api-system-get-info

  • api-system-get-ontapi-version

  • api-system-get-version

  • api-useradmin-group-list

  • api-useradmin-user-list

  • api-volume-clone-create

  • api-volume-clone-split-estimate

  • api-volume-create

  • api-volume-destroy

  • api-volume-get-root-name

  • api-volume-list-info

  • api-volume-list-info-iter-end

  • api-volume-list-info-iter-next

  • api-volume-list-info-iter-start

  • api-volume-offline

  • api-volume-online

  • api-volume-restrict

  • api-volume-set-option

  • api-volume-size

  • cli-filestats

  • login-http-admin

Obtaining NetApp Hardware Licenses

Snap Clone on a NetApp storage server requires a valid license for the following services:

  • flex_clone

  • nfs

  • snaprestore

Creating NetApp Storage Credentials

To create the NetApp storage credentials, follow these steps:

Note:

Snap Clone is supported only on NetApp Data ONTAP® 7.2.1.1P1D18 or higher, and ONTAP@ 8.x (7-mode, c-mode, and v-server mode).

  1. Create ROLE em_smf_admin_role' with all the recommended capabilities, such as api-aggr-list-info,api-file-delete-file, and the like.

  2. Create GROUP em_smf_admin_group with the ROLE em_smf_admin_role.

  3. Create USER em_smf_admin with GROUP em_smf_admin_group and a secure password.

Note:

The user em_smf_admin must be a dedicated user to be used by Oracle Enterprise Manager. Oracle does not recommend sharing this account for any other purposes.

Configuring NetApp 8 Cluster Mode Hardware

This topic discusses how to setup NetApp 8 cluster mode (c-mode) hardware for supporting Snap Clone in Enterprise Manager Cloud Control 13c.

NetApp 8 hardware in 7-mode is already supported for Snap Clone.

To configure NetApp 8 c-mode hardware, refer to the following sections:

NetApp 8 Configuration Supported with Cluster Mode

The configuration supported with c-mode is as follows:

  • Snap Clone features are supported only with SVM (Vserver).

  • Registration of a physical cluster node is not supported.

  • Multiple SVMs can be registered with Enterprise Manager Cloud Control 13c. All the registered SVMs are managed independently.

Preparing the NetApp 8 Storage and SVM

To prepare the NetApp 8 storage and SVM, ensure that the following requirements are done:

  • The NetApp 8 c-mode hardware should have an SVM created. If not, you should create an SVM which will be registered with the Enterprise Manager.

  • The SVM should have a network interface (LIF) with both Management and Data access. The domain name and IP address of this interface should be provided on the Storage Registration page in the Enterprise Manager.

  • There should be at least one aggregate (volume) assigned to the SVM. The aggregates should not be shared between the SVMs.

  • The SVM should have a user account that has the vsadmin-volume role assigned for ontapi access.

    The user credentials should be supplied on the Storage Registration page in the Enterprise Manager.

  • The root volume of SVM should have an export policy with a rule that allows Read Only access to all hosts. If you are using NFS v4, then the Superuser access needs to be granted from the Modify Export Rule dialog box.

    Note:

    • A directory named em_volumes is created with permissions 0444 inside the root volume of SVM. This directory will be used as an Enterprise Manager name space for the junction point.

    • All the storage volumes created will use the junction point /em_volumes in the name space.

    Note:

    When you register an SVM in Enterprise Manager Cloud Control, the details of all the aggregates assigned to it are fetched. The total size of an aggregate is required to set the quota, perform space computation, and for reporting.

    Presently, NetApp does not provide any Data ONTAP API to fetch the aggregate total size from an SVM. As a workaround, the available size of an aggregate is considered as the total size and is set as the Storage Ceiling during first Synchronize run. Storage Ceiling is the maximum amount of space that Enterprise Manager can use in an aggregate.

    If the total space of an aggregate is increased on the storage, you can increase the Storage Ceiling till you consume the available space in that aggregate.

Configuring Sun ZFS and ZS3 Hardware

This section consists of the following:

Obtaining Sun ZFS Hardware Privileges

Privileges is a generic term. For example, Sun ZFS refers to privileges as Permissions.

For Sun ZFS storage server, to use Snap Clone, assign the following privileges or permissions to the Sun ZFS storage credentials:

Note:

All the permissions listed must be set to true. The scope must be 'nas' and there must not be any further filters.

  • changeProtocolProps

  • changeSpaceProps

  • clone and createShare

  • destroy

  • rollback

  • takeSnap

Obtaining Sun ZFS Hardware Licenses

Snap Clone on Sun ZFS Storage Appliance requires a license for the Clones feature. A restricted-use license for the same is included with the Enterprise Manager Snap Clone.

Creating Sun ZFS Storage Credentials

To create the Sun ZFS storage credentials, follow these steps:

  1. Create ROLE em_smf_admin_role.

  2. Create AUTHORIZATIONS for the ROLE em_smf_admin_role.

  3. Set SCOPE as nas.

  4. Set the recommended permissions, such as, allow_changeProtocolProps, allow_changeSpaceProps, and the like to true.

  5. Create USER em_smf_admin and set its ROLE property as em_smf_admin_role.

    Note:

    The user em_smf_admin must be a dedicated user to be used by Oracle Enterprise Manager. Oracle does not recommend sharing this account for any other purposes.

Configuring Solaris File System (ZFS) Storage Servers

This section consists of the following:

Obtaining Solaris File System (ZFS) Privileges

Solaris File System (ZFS) refers to privileges as Permissions. For Solaris File System (ZFS) storage server, to use Snap Clone, grant the following permissions on the pool for the Solaris File System (ZFS) user:

  • clone

  • create

  • destroy

  • mount

  • rename

  • rollback

  • share

  • snapshot

  • quota

  • reservation

  • sharenfs

  • canmount

  • recordsize

Obtaining Solaris File System (ZFS) Licenses

Solaris File System (ZFS) does not require any special hardware license. Only Oracle Solaris OS version 11.1 is supported.

Setting Up Solaris File System (ZFS) Storage Servers

Solaris File System (ZFS) storage servers can work with any storage hardware. You do not need to buy any additional storage hardware. Instead, you can attach your in-house storage hardware and to acquire the Oracle Snap Clone functionality. For example, you can attach LUNs from an EMC VMAX, VNX systems, a Hitachi VSP, or an Oracle Pillar Axiom FC array.

The following storage topology figure explains how this works:

Note:

This figure assumes that you have a SAN storage device with 4 x 1TB logical unit devices exposed to the Solaris File System (ZFS) storage server.


Storage Topology

This section contains the following:

Prerequisites for Setting Up Solaris File System (ZFS) Storage Servers

Before you configure a Solaris File System (ZFS) storage server, ensure that you meet requirements:

  • Ensure that zfs_arc_max is not set in /etc/system. If it needs to be set ensure that it is set to a high value such as 80% of RAM.

  • Ensure that the storage server is configured with multiple LUNs. Each LUN should be a maximum of 1TB. A minimum 2 LUNs of 1TB each is recommended for a Snap Clone. Each LUN should have a mirror LUN which is mounted on the host over a different controller to isolate failover. A LUN can be attached to the Solaris host over Fibre Channel for better performance.

    Note:

    If Fibre Channel is not available, any direct attached storage or iSCSI based LUNs are sufficient.

  • All LUNs used in a pool should be equal in size. It is preferable to use less than 12 LUNs in a pool.

  • Apart from LUNs, the storage needs cache and log devices to improve zpool performance. Both these devices should ideally be individual flash/SSD devices. In case it's difficult to procure individual devices, one can use slices cut from a single device. Log device needs to be about 32GB in size and also have redundancy and battery backup to prevent data loss. Cache device can be about 128GB in size and need not have redundancy.

Requirements for Storage Area Network Storage

The requirements for Storage Area Network (SAN) storage are as follows:

  • It is recommended to create large LUNs and lesser number of LUNs. The maximum recommended size for a LUN is 3TB.

  • LUNs should come from different SAN storage pools or an entirely different SAN storage device.

    These LUNs are needed for mirroring, to maintain the pool level redundancy. If your SAN storage maintains a hardware level redundancy, then you can skip this requirement.

  • The LUNs should be exposed over Fiber Channel.

Recommendations for Solaris File System (ZFS) Pools

The recommendations for Solaris File system (ZFS) pools are as follows:

  • Create the Storage pool with multiple LUNs of the same size. You can add more disks to the storage pool to increase the size based on your usage.

  • The storage pool created on the Solaris File System (ZFS) storage server should use the LUNs coming from a different SAN storage pool or an entirely different SAN storage device. You can skip this if your SAN storage maintains hardware level redundancy.

  • To repair data inconsistencies, use ZFS redundancy such as mirror, RAIDZ, RAIDZ-2 or RAIDZ-3 to repair data inconsistencies, regardless of whether RAIDZ is implemented at the underlying storage device.

  • For better throughput and performance, use cache and log devices. Both these devices should ideally be on individual flash/SSD devices. In case of difficulty in procuring individual devices, you can use slices cut from a single device.

    It is recommended to have the Log device at about 50% of RAM and also have redundancy and battery backup to prevent data loss. Cache device size could be based on the size of the workload and the pool.

    Cache device do not support redundancy. This is optional.

  • While creating the pool, it has to be sized to accommodate the test master database along with the cloned databases. A clone will co-exist with the parent database in the same storage pool. Therefore, you should plan for test master and clone capacity well ahead.

    For example, The size of the test master is 1TB and you expect to create 10 clones with each of them expected to differ from the test master by 100G. Then, the storage pool should be minimum 2.5TB in size.

  • Maintain the storage pool with at least 20% free space. If the free space falls below this level, then the performance of the pool degrades.

Configuring Solaris File System (ZFS) Users and Pools

You need to create a user which will be able to administer the storage from Enterprise Manager. To do this, run the following commands as root user:

# /sbin/useradd -d /home/emzfsadm -s /bin/bash emzfsadm
# passwd emzfsadm

Note:

The username should be less than or equal to 8 characters.

You need to configure the ZFS pool that is used to host volumes, and grant privileges on this pool to the user created. The emzfsadm user should have the privileges on all the zpools and its mount points in the system.

To configure the ZFS pool, refer to the following table and run the following commands:

Note:

The table displays a reference implementation, and you can choose to change this as required.

Pool Name lunpool

Disks (SAN exposed LUNs over FC/iSCI)

lun1=c9t5006016E3DE0340Ed0,

lun2=c9t5006016E3DE0340Ed1

Disks Mirror (SAN exposed LUNs over FC/iSCI)

mir1=c10t5006016E3DE0340Ed2,

mir2=c10t5006016E3DE0340Ed3

Flash/ SSD disk (log)

ssd1=c4t0d0s0

Flash/SSD disk (cache)

ssd2=c4t0d1s0

# zpool create lunpool mirror lun1=c9t5006016E3DE0340Ed0 mir1=c10t5006016E3DE0340Ed2 mirror lun2=c9t5006016E3DE0340Ed1 mir2=c10t5006016E3DE0340Ed3 log ssd1=c4t0d0s0 cache ssd2=c4t0d1s0
 

Example format output is as follows:

bash-4.1# /usr/sbin/format
Searching for disks...done
 
AVAILABLE DISK SELECTIONS:
       0. c9t5006016E3DE0340Ed0 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,0
       1. c9t5006016E3DE0340Ed1 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,1
       2. c10t5006016E3DE0340Ed2 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,2
       3. c10t5006016E3DE0340Ed3 <DGC-VRAID-0532-1.00TB>
          /pci@78,0/pci8086,3c08@3/pci10df,f100@0/fp@0,0/disk@w5006016e3de0340e,3


[ We need to find the size of pool that was created ]
# df -k /lunpool
Filesystem           1024-blocks        Used   Available Capacity  Mounted on
lunpool              1434746880          31  1434746784     1%    /lunpool
 
[ We use the Available size shown here to set quota as shown below ]
 
# zfs set quota=1434746784 lunpool
 
# zfs allow emzfsadm clone,create,destroy,mount,rename,rollback,share,snapshot,quota,reservation,sharenfs,canmount,recordsize,logbias lunpool
 
# chmod A+user:emzfsadm:add_subdirectory:fd:allow /lunpool
 
# chmod A+user:emzfsadm:delete_child:fd:allow /lunpool

Note:

this content did not make it through the conversion

Configuring EMC Storage Servers

Before you use an EMC Symmetrix VMAX Family or an EMC VNX storage server, you need to first setup the EMC storage hardware for supporting Snap Clone in Oracle Enterprise Manager 13c. Ensure that all the requirements are met in the following sections:

Supported Configuration for EMC Storage Servers

Before you configure the EMC Symmetrix VMAX family or the EMC VNX storage server, check the following list. The list displays components that are supported and are not supported for EMC VMAX and EMC VNX storage.

  • EMC VMAX 10K and VNX 5300 are certified to use. Higher models in the same series are expected to work.

  • Only Linux and Solaris operating systems are supported. Other operating systems are not yet supported.

  • Multi-pathing is mandatory.

  • Only EMC PowerPath, and Solaris MPxIO are supported.

  • Switched fabric is supported. Arbitrated loop is not supported.

  • Emulex (LPe12002-E) host bus adapters are certified to use. Other adapters are expected to work.

  • SCSI over Fibre Channel is supported. iSCSI, NAS are not yet supported.

  • Oracle Grid Infrastructure 11.2 is supported.

  • Oracle Grid Infrastructure 12.1 with Local ASM Storage option is supported. Flex ASM is not supported.

  • ASM Filter Driver is not supported.

  • ASM support is only for raw devices. File System is not supported.

  • Support for Thin Volumes (TDEV) on VMAX.

  • Support for only LUNs on VNX. NAS is not yet supported.

Requirements for EMC Symmetrix VMAX Family and Database Servers

The requirement for the operating system version of EMC Symmetrix VMAX Family is:

  • EMC VMAX Enginuity Version: 5876.251.161 and above

  • SMI-S Provider Version: V4.6.1.6 and above

  • Solutions Enabler Version: V7.6-1755 and above

Note:

The EMC VMAX Enginuity version is the Operating System version of the storage.

The SMI-Provider and Solutions Enabler are installed on a host in a SAN.

The requirements for database server are as follows:

Oracle Database Requirements

  • Oracle Database 10.2.0.5 and higher

Operating System Requirements

  • Oracle Linux 5 update 8 (compatible with RHEL 5 update 8) and above

  • Oracle Linux 6 (compatible with RHEL 6) and above

  • Oracle Solaris 10 and 11

Multipathing Requirements

  • EMC PowerPath Version 5.6 or above as available for Linux Operating System release and kernel version

  • EMC PowerPath Version 5.5 or above as available for Oracle Solaris 11.1 release

  • EMC PowerPath Version 6 is not supported.

  • Solaris MPxIO as available in latest update

Oracle Grid Infrastructure Requirements

  • Oracle Grid Infrastructure 11.2

  • Oracle Grid Infrastructure 12.1. Flex ASM is not supported.

Preparing the Storage Area Network

To prepare the storage area network, follow the configuration steps outlined in each section.

SAN Fabric Configuration

Configure your SAN fabric with multipathing by ensuring the following:

  • You must have redundancy at storage, switch and server level.

  • Perform the zoning such that multiple paths are configured from the storage to the server.

  • Configure the paths such that a failure at a target port, or a switch or a host bus adapter will not cause unavailability of storage LUNs.

  • Configure gatekeepers on the host where EMC SMI-S provider is installed. To configure gatekeepers, refer to the documentation available on the EMC website:

SMI-S Provider

You should install the SMI-S provider and Solutions Enabler on one of the servers in the fabric where the storage is configured. To install and configure the SMI-S provider, refer to the documentation available on the EMC website:

The SMI-S provider URL and login credentials are needed to interact with the storage. An example of an SMI-S Service Provider URL is https://rstx4100smis:5989.

These details are needed when you register a storage server. You are required to do the following:

  • Ensure that the VMAX or VNX storage is discovered by the SMI-S provider.

  • Add the VNX storages to the SMI-S provider.

  • Create a user account with administrator privileges in the SMI-S provider to access the VMAX or VNX storage.

  • Set a sync interval of 1 hour.


Setting up a Storage Area Network environment

Understanding VMAX Terminology

The following table outlines VMAX terms that are used in this section. Refer to these terms to gain a better conceptual understanding, before you prepare the EMC VMAX storage.

Table 22-1 VMAX terminologies

Term Definition

Logical Unit

An I/O device is referred to as a Logical Unit.

Logical Unit Number

A unique address associated with a Logical Unit.

Initiator

Any Logical Unit that starts a service request to another Logical Unit is referred to as an Initiator

Initiator Group

An initiator group is a logical grouping of up to 32 Fibre Channel initiators (HBA ports), eight iSCSI names, or a combination of both. An initiator group may also contain the name of another initiator group to allow the groups to be cascaded to a depth of one.

Port Group

A port group is a logical grouping of Fibre Channel and/or iSCSI front-end director ports. The only limit on the number of ports in a port group is the number of ports in the Symmetrix system. It is also likely that a port group can contain a subset of the available ports in order to isolate workloads to specific ports.

Note: As a pre-requisite, OEM expects a port group created with the name ORACLE_EM_PORT_GROUP and it should contain the required target ports.

Storage Group

A storage group is a logical grouping of up to 4,096 Symmetrix devices.

Target

Any Logical Unit to which a service request is targeted is referred to as a Target

Masking View

A masking view defines an association between one initiator group, one port group, and one storage group. When a masking view is created, the devices in the storage group are mapped to the ports in the port group and masked to the initiators in the initiator group.

SCSI Command

A service request is referred to as a SCSI command

Host Bus Adapter (HBA)

The term host bus adapter (HBA) is most often used to refer to a Fibre Channel interface card. Each HBA has a unique World Wide Name (WWN), which is similar to an Ethernet MAC address in that it uses an OUI assigned by the IEEE. However, WWNs are longer (8 bytes). There are two types of WWNs on a HBA: a node WWN (WWNN), which is shared by all ports on a host bus adapter, and a port WWN (WWPN), which is unique to each port. There are HBA models of different speeds: 1Gbit/s, 2Gbit/s, 4Gbit/s, 8Gbit/s, 10Gbit/s, 16Gbit/s and 20Gbit/s.

For more information on VMAX storage and terminologies, refer to the document EMC Symmetrix VMAX Family with Enginuity available in the EMC website.

Preparing the EMC VMAX Storage

Configure your EMC VMAX appliance such that it is zoned with all the required nodes where you need to provision databases. To prepare the EMC VMAX storage, do the following on the storage server:

  • Ensure that all the Host Initiator ports are available from the storage side.

  • It is recommended to create one initiator group per host with corresponding initiators to increase security. The 'Consistent LUNs' property of the immediate parent Initiator Group of the initiators should to set to 'No'

  • Create a Port Group called ORACLE_EM_PORT_GROUP to be used by Oracle Enterprise Manager for creating Masking Views. This port group should contain all the target ports that will be viewed collectively by all the hosts registered in the Enterprise Manager Cloud Control system.

    For example, host1 views storage ports P1 and P2, and host2 views storage ports P3 and P4. Then, the ORACLE_EM_PORT_GROUP should include all ports P1, P2, P3 and P4. Include only the necessary target ports as needed by the development infrastructure.

  • Create a separate Virtual Provisioning Pool also known as Thin Pool, and dedicate it for Oracle Enterprise Manager.

  • Ensure that the TimeFinder license is enabled to perform VP Snap

Preparing the EMC VNX Storage

Configure your EMC VNX appliance such that it is zoned with all the required nodes where you need to provision databases. To prepare the EMC VNX storage, do the following on the storage server:

Note:

EMC VNX Storage supports only LUN creation, cloning, and deletion. It does not support NAS.

  • Ensure that all host initiator ports are available from the storage side.

  • Ensure that the initiators belonging to one host are grouped and named after the Host on the EMC VNX storage.

  • Create one storage group with one host for each of the hosts registered in Enterprise Manager.

    For example, if initiators i1 and i2 belong to host1, register the initiators under the name Host1. Create a new storage group SG1 and connect Host1 to it. Similarly, create one storage group for each of the hosts that are to be added to Enterprise Manager.

Preparing Database Servers

To prepare your server for Enterprise Manager Snap Clone, ensure the following:

  • Servers should be physical and equipped with Host Bus Adapters. NPIV and VMs not supported.

  • Configure your servers with recommended and supported multipath software. If you use EMC PowerPath, then enable the PowerPath license.To enable the PowerPath license, use the following command:

    emcpreg -install
    
  • If you need the servers to support Oracle Real Application Clusters, then install Oracle Clusterware.

    Note:

    ASM and Clusterware have to be installed and those components have to be discovered in Enterprise Manager as a target. Once ASM and Clusterware are installed, additional ASM disk groups can be created from Enterprise Manager.

  • Enable Privileged Host Monitoring credentials for all the servers. If the server is part of a cluster, then you should enable privileged host monitoring credential for that cluster.

    For more details on enabling privileged host monitoring credentials, refer to Oracle Enterprise Manager Framework, Host, and Services Metric Reference Manual.

  • If you are using Linux, you should configure Oracle ASMLib, and set the asm_diskstring parameter to a valid ASM path. For example:

    /dev/oracleasm/disks/

    Update the boot sequence such that the ASMLib service is run first, and then the multipath service.

    To install Oracle ASMLib, refer to the following website:

    http://www.oracle.com/technetwork/server-storage/linux/install-082632.html

    To configure Oracle ASMLib on multipath disks, refer to the following website:

    http://www.oracle.com/technetwork/server-storage/linux/multipath-097959.html

Setting Privileged Host Monitoring Credentials

You should set the privilege delegation settings before setting Host monitoring credentials. Do the following:

Note:

This is required only on hosts that are used for snap cloning databases on EMC storage.

  1. From the Setup menu, click on Security and then select Monitoring Credentials.

  2. On the Monitoring Credentials page, select Cluster or Host according to your requirement and then. click Manage Monitoring Credentials.


    monitoring credentials page

  3. On the Cluster Monitoring Credentials page, select Privileged Host Monitoring Credentials set for the cluster or host and click Set Credentials.


    Cluster Monitoring Credentials page

  4. In the dialogue box that appears, specify the credentials, and click Save.

  5. After the host monitoring credentials are set for the cluster, refresh the cluster metrics. Verify if the Storage Area Network metrics get collected for the hosts.


    SAN host metric

22.3.3.2 Customizing Storage Proxy Agents

A Proxy Agent is required when you register a NetApp, Sun ZFSSA or Solaris File System (ZFS) File System.

Before you register a NetApp storage server, meet the following prerequisites:

Note:

Storage Proxy Agent is supported only on Linux Intel x64 platform.

Acquiring Third Party Licenses

The Storage Management Framework is shipped by default for Linux x86-64 bit platform, and is dependent on the following third party modules:

  • Source CPAN - CPAN licensing apply

    • IO::Tty (version 1.10)

    • XML::Simple (version 2.20)

    • Net::SSLeay (version 1.52)

  • Open Source - Owner licensing apply

    • OpenSSL(version 1.0.1e)

Uploading Storage Vendor SDK

Before you register a NetApp storage server, do the following:

  1. Download the NetApp Manageability SDK version 5.0R1 for all the platforms from the following NetApp support site: http://support.netapp.com/NOW/cgi-bin/software

  2. Unzip the 5.1 SDK and package the Perl NetApp Data OnTap Client SDK as a tar file. Generally, you will find the SDK in the lib/perl/NetApp folder. The tar file when extracted should look as follows:

    NetApp.tar
    - netapp
      - Na  Element.pm
      - NaServer.pm
      - NaErrno.pm
    

    For example, the Software Library entity Storage Management Framework Third Party/Storage/NetApp/default should have a single file entry that contains NetApp.tar with the above tar structure.

    Note:

    Ensure that there is no extra space in any file path name or software library name.

  3. Once the tar file is ready, create the following folder hierarchy in software library: Storage Management Framework Third Party/Storage/NetApp

  4. Upload the tar file as a Generic Component named default.

    Note:

    YTo upload the tar file, you must use the OMS shared filesystem for the software library.

    The tar file should be uploaded to this default software library entity as a Main File.

Overriding the Default SDK

The default SDK is used for all the NetApp storage servers. However, the storage server may work with only a certain SDK. In such a case, you can override the SDK per storage server, by uploading an SDK and using it only for this particular storage server.

To override the existing SDK for a storage server, upload the tar file to the Software Library entity. The tar file should have the structure as mentioned in Step 3 of the previous section.

The Software Library entity name should be the same as the storage server name.

For example, if the storage server name is mynetapp.example.com, then the Software Library entity must be as follows:

Storage Management Framework Third Party/Storage/NetApp/mynetapp.example.com

Note:

A storage specific SDK is given a higher preference than the default SDK,

Overriding Third Party Server Components

By default, all the required third party components are shipped for Linux Intel 64 bit platform. If you need to override it by any chance, package the tar file as follows:

Note:

The tar file should contain a thirdparty folder whose structure should be as mentioned below:

thirdparty
|-- lib
| |-- engines
| | |-- lib4758cca.so
| | |-- libaep.so
| | |-- libatalla.so
| | |-- libcapi.so
| | |-- libchil.so
| | |-- libcswift.so
| | |-- libgmp.so
| | |-- libgost.so
| | |-- libnuron.so
| | |-- libpadlock.so
| | |-- libsureware.so
| | `-- libubsec.so
| |-- libcrypto.a
| |-- libcrypto.so
| |-- libcrypto.so.1.0.0
| |-- libssl.a
| |-- libssl.so
| `-- libssl.so.1.0.0
`-- pm
|-- CPAN
| |-- IO
| | |-- Pty.pm
| | |-- Tty
| | | `-- Constant.pm
| | `-- Tty.pm
| |-- Net
| | |-- SSLeay
| | | `-- Handle.pm
| | `-- SSLeay.pm
| |-- XML
| | `-- Simple.pm
| `-- auto
| |-- IO
| | `-- Tty
| | |-- Tty.bs
| | `-- Tty.so
| `-- Net
| `-- SSLeay
| |-- SSLeay.bs
| |-- SSLeay.so

Ensure that the tar file is uploaded to the Software Library entity which is named after the platform name, x86_64. The Software Library entity must be under the following:

Storage Management Framework Third Party/Server

The x86_64 entity, when uploaded is copied to all the storage proxy hosts irrespective of which storage server it would be processing. To use this entity on a specific storage proxy agent, name the entity after the host name.

For example, Storage Management Framework/Third Party/Server/x86_64 will be copied to any storage proxy host which is on an x86_64 platform. Similarly, Storage Management Framework Third Party/Server/myhost.example.com is copied only to myhost.example.com, if it is used as a storage proxy host.

The host name is given a higher preference than the platform preference.

22.3.4 Registering Storage Servers

To register a particular storage server, follow the procedure outlined in the respective section:

22.3.4.1 Registering a NetApp or a Sun ZFS Storage Server

To register the storage server, follow these steps:

  1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
  2. On the Storage Registration page, in the Storage section, click on Register, and then select either NetApp Storage Appliance or Sun ZFS Storage Appliance, based on which storage server you want to register.

    Note:

    If you see a No named credentials available message, it means that no credentials are registered or the credentials are owned by another user.


    Storage Registration page

    Note:

    You need the EM_STORAGE_ADMINISTRATOR role to complete the storage registration.

  3. On the NetApp or Sun ZFS Storage Registration page, in the Storage section, do the following:

    NetApp Storage Registration

    • Enter the storage server name in the Name field. Ensure that the name is the valid host name and contains no spaces and invalid characters.

    • Select the protocol.

      Note:

      For NetApp storage, the connection is over http or https. For Sun ZFS storage, the connection is over ssh.

    • Select the Storage Credentials, or click on the green plus sign to add.

      Note:

      These credentials will be used by the Management Agent to execute storage (NetApp or Sun ZFS) APIs.

      Only credentials owned by the user are displayed here.

      In the display box that appears, enter the storage server name and password. Confirm the password and click OK.

    • Enter storage name aliases (optional).

      The storage name alias should be in lowercase.

      Note:

      A storage name alias is any name that may have been used when mounting a volume from the storage.

      For example: IP address, FQDN, DNS alias, and the like.

      A storage alias is necessary to identify the database targets on the storage. The database targets are identified by mapping the mount points to the files used by the database. For example, if the storage mystorage.com has an alias mystorage.net, and a database uses a data file mounted as mystorage.net:/u01, then mystorage.net must be added as an alias for the discovery to work.

      When you register the storage, use the admin interface as the storage name. List the data interfaces in the storage alias section. The registered storage name will be used to perform registration operations and while mounting the volumes on target host, it will give preference to interfaces listed as storage aliases.

  4. In the Agent to Manage Storage section, do the following:
    • Click Add to add a Management Agent host. A Storage Agent display box appears. Select a Management Agent from the Target Name column of the table. Then, click Select.

      Note:

      The Management Agent list displays only Linux X64 Management Agents.


      Agent to Manage Storage


      Storage Agent

      The Management Agent selected is used for performing operations on the storage server.

    • Once a Management Agent is selected, the Management Agent credentials are found and a named credential for the host is displayed.

      Note:

      The Management Agent credentials are used to connect to the Management Agent from Oracle Management Service.

      Multiple Management Agents can be configured to monitor the storage device. Click Add to choose a second Management Agent if required.

      Note:

      Configuring multiple Management Agents to monitor the storage device provides you with a backup in the event that an host is down or the Management Agent is under blackout.

    • Click Submit to register the storage server.

22.3.4.2 Registering a Solaris File System (ZFS) Storage Server

To register the storage server, follow these steps:

  1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
  2. On the Storage Registration page, in the Storage section, click on Register, and then select Solaris File System (ZFS)

    Note:

    If you see a No named credentials available message, it means that no credentials are registered or the credentials are owned by another user.


    Registering a Solaris ZFS file system

    Note:

    You need the EM_STORAGE_ADMINISTRATOR role to complete the storage registration.

  3. On the Register File System (ZFS) page, in the Storage section, do the following:
    • Enter the Solaris system name in the Name field. Ensure that the name is the valid host name or IP address and contains no spaces and invalid characters.

    • Select the protocol.

    • Select the Storage Credentials, or click on the green plus sign to add.

      Note:

      These credentials will be used by the Management Agent to execute Solaris file system APIs.

      Only credentials owned by the user are displayed here.

      In the display box that appears, enter the storage server name and password. Confirm the password and click OK.

    • Enter storage name aliases (optional).

      The storage name alias should be in lowercase.

      Note:

      A storage name alias is any name that may have been used when mounting a volume from the storage.

      For example: IP address, FQDN, DNS alias, and the like.

      Storage alias is necessary to identify the database targets on the storage. The database targets are identified by mapping the mount points to the files used by the database. For example, if the storage mystorage.com has an alias mystorage.net, and a database uses a data file mounted as mystorage.net:/u01, then mystorage.net must be added as an alias for the discovery to work.

      When you register the storage, use the admin interface as the storage name. List the data interfaces in the storage alias section. The registered storage name will be used to perform registration operations and while mounting the volumes on target host, it will give preference to interfaces listed as storage aliases.


      Storage Registration page for Solaris ZFS file system

  4. In the Synchronize Schedule section, specify the frequency to synchronize the storage details with the hardware.

    Ensure that the zpools setup is completed before clicking Submit. To setup the zpools, refer to Configuring Solaris File System (ZFS) Users and Pools.

22.3.4.3 Registering an EMC Storage Server

To register the storage server, follow these steps:

Note:

Before you register an EMC storage server, the storage server should be prepared. To prepare the storage server refer to Configuring EMC Storage Servers.

  1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
  2. On the Storage Registration page, in the Storage section, click on Register, and then select EMC Storage Array.

    EMC Storage Registration page

    Note:

    If you see a No named credentials available message, it means that no credentials are registered or the credentials are owned by another user.

    Note:

    You need the EM_STORAGE_ADMINISTRATOR role to complete the storage registration.

  3. On the Register EMC Storage Appliance page, in the Storage section, do the following:
    • Specify the storage server name in the Name field. Ensure that the name is the valid storage name and contains no spaces and invalid characters.

    • For EMC storage, the connection is over SMI-S protocol. Specify the SMI-S Provider URL.

    • Specify the SMI-S User Credentials, or click on the green plus sign to add.

      Note:

      These credentials are used by the Enterprise Manager to interact with the EMC storage appliance.

      The credentials should be of the Administrator in the SMI-S provider and not that of the storage.

      Only credentials owned by the user are displayed here.

      In the display box that appears, enter the SMI-S User name and password. Confirm the password and click OK.

  4. In the Synchronize Schedule section, specify the frequency to synchronize the storage details with the hardware.

    Register EMC Storage Appliance page

    Click Submit.

22.3.5 Administering the Storage Server

To administer the storage server, refer to the following sections:

22.3.5.1 Synchronizing Storage Servers

When you register a storage server for the first time, a synchronize job is run automatically. However, to discover new changes or creations, you should schedule a synchronize job to run at a scheduled time, preferably during a quiet period when Snap Clone actions are not in progress. To do this, follow these steps:

  1. On the Storage Registration page, in the Storage section, click Synchronize.

    Note:

    When you click on Synchronize, a deployment procedure is submitted which discovers all databases monitored by Enterprise Manager Cloud Control which can be used for Snap Clone.

    Windows databases are not discovered as part of storage discovery. This is because the Windows storage NFS collection does not happen at all. For further details please refer to the MOS note 465472.1

    You need EM_STORAGE_OPERATOR role along with GET_CREDENTIAL privilege on the Storage Server and Storage Management Agent credentials to be able to synchronize the storage.

  2. A confirmation box appears. Click OK.

    Synchronization confirmation box

    This action now submits a one-time synchronization job.

    Note:

    The synchronization job fetches latest storage information, and recomputes the mapping between storage volumes and databases.

  3. On the Storage Registration page, in the Storage section, to view the procedure details of the Management Agent host, click on the value (for example, Scheduled) in the Status column.

    Synchronization Confirmation

  4. On the Provisioning page, in the Procedure Steps section, click View, and then select Expand All. Keep clicking the Refresh button on the page to view the procedure activity as it progresses.

    Expand All on Provisioning page

    The synchronization status of the Management Agent on the Storage Registration page, changes to Succeeded once the synchronization process is complete.

  5. To update a synchronize schedule of a registered storage server, select a storage server on the Storage Registration page and then click on Edit. On the Edit Storage page, in the Synchronize Storage section, edit the repetition time and frequency of the synchronize job.

    Synchronize Schedule

    Note:

    The frequency of a synchronization job is set at 3 hours by default.

    Click Submit.

Note:

The Associating Storage Volumes With Targets step relies on both database target metrics and host metrics. The database target (oracle_database/rac_database) should have up-to-date metrics for the Controlfiles, Datafiles and Redologs. The File Systems metric should be up to date for the hosts on which the database is running.

22.3.5.2 Deregistering Storage Servers

To deregister a registered storage server, follow these steps:

Note:

To deregister a storage server, you need FULL_STORAGE privilege on the storage along with FULL_JOB privilege on the Synchronization GUID of the storage server.

  1. From the Setup menu, click on Provisioning and Patching, and then select Storage Registration.
  2. On the Storage Registration page, in the Storage section, select a storage server from the list of registered storage servers.
  3. Select Remove.

    On the Remove Storage page, select the storage server that you want to deregister, and then click Submit.

    The storage server is now deregistered.

Note:

Once a storage is deregistered, the Snap Clone profiles and Service Templates on the storage will no longer be functional, and the relationship between these Profiles, Service Templates and Snap Cloned targets will be lost.

Note:

It is recommended to delete the volumes created using Enterprise Manager before deregistering a storage. As a self service user, you should submit deletion requests for the cloned databases.

To submit these deletion requests, click Remove from the Hierarchy tab on the Storage Registrations page for deleting the volumes that were created by Enterprise Manager for hosting test master databases.

22.3.6 Managing Storage Servers

To manage the storage server, refer to the following sections:

22.3.6.1 Managing Storage Allocation

You can manage storage allocation by performing the following tasks:

Editing the Storage Ceiling

Storage Ceiling is the maximum amount of storage from a project, aggregate, or thin pool that Enterprise Manager is allowed to use. This ensures that Enterprise Manager creates clones in that project only till this limit is reached. When a storage project is discovered for the first time, the entire capacity of the project is set as the ceiling. In case of Sun ZFS, the quota set on the project is used.

Note:

You must explicitly set quota property for the Sun ZFS storage project on the storage end. Also, the project should have a non zero quota set on the storage end. Else, Enterprise Manager will not be able to clone on it.

To edit the storage ceiling, do the following:

  1. On the Storage Registration page, from the Storage section, select the storage server for which you want to edit the storage ceiling.

  2. Select the Contents tab, select the aggregate, and then click Edit Storage Ceiling.

    Note:

    Edit Storage Ceiling option enables you modify the maximum amount of storage that Enterprise Manager can use. You can create clones or resize volumes only till this limit is reached.

  3. In the Edit Storage Ceiling dialog box, enter the storage ceiling, and then, click OK.


    Edit Storage Ceiling Dialog Box

Creating Storage Volumes

To create storage volume, do the following:

  1. On the Storage Registration page, from the Storage section, select the storage server for which you want to create storage volume.

  2. Select the Contents tab, select the aggregate, and then select Create Storage Volumes.


    Create Storage Volumes button

  3. On the Create Storage Volumes page, in the Storage Volume Details section, click Add.


    Add storage volume

  4. Select a storage and specify the size in GB (size cannot exceed the storage size). The specified size should be able to accommodate the test master database size, without consuming the entire storage size.

    Next, specify a mount point starting with /.

    For example,
    If the storage is "lunpool", select the "lunpool".
    The specified size under the size column should not exceed the storage space. If the size of the "lunpool" is 100GB and the test master database is 10 GB, then specify size as 10GB. 
    The mount point should be a meaningful mount point starting with "/".
    For example: /oracle/oradata
    

    Storage Volume details

  5. In the Host Details section, specify the following:

    • Host Credentials: Specify the target host credentials of the Oracle software.

    • Storage Purpose: For using Snap Clone, the most important options are as follows:

      • Oracle Datafiles for RAC

      • Oracle Datafiles for Single Instance

      Note:

      You can also store the OCR and Voting disks and Oracle binaries in the storage volume,

    • Platform: Select the supported target platform. The volume will be mounted on the supported target platform.

    • Mount Options: Mount options field is automatically filled based on the values specified for the storage purpose and the platform. Do not edit the mount options.

    • Select NFS v3 or NFS v4.

  6. Select one or more hosts to perform the mount operations by clicking Add.

    If you select Oracle Datafiles for RAC, you would normally specify more than one host. The volume is then mounted on the specified hosts automatically after the completion of the procedure activity.


    Storage Volume host details

  7. Click Submit.

    When you click Submit, a procedure activity is executed. On completion of the procedure activity, the volumes get mounted on the target system. You can now proceed to create a test master database on the mounted volumes on the target system.

Resizing Volumes of a Database

When a database runs out of space in any of its volumes, you can resize the volume according to your requirement. To resize volume(s) of a clone, follow these steps:

Note:

This is not available for EMC storage servers.

Note:

Resizing of volumes of a Test Master database cannot be done using Enterprise Manager, unless the volumes for the Test Master were created using the Create Volumes UI.

Note:

You need the FULL_STORAGE privilege to resize volumes of a database or a clone. Also, ensure that the underlying storage supports quota management of volumes.

  1. On the Storage Registration page, from the Storage section select the required storage server.

  2. In the Details section, select the Hierarchy tab, and then select the target.

    The Storage Volume Details table displays the details of the volumes of the target. This enables you to identify which of the volume of the target is running out of space.

  3. In the Volume Details table, select Resize.


    Resize button for resizing volumes

  4. On the Resize Storage Volumes page, specify the New Writable Space for the volume or volumes that you want to resize. If you do not want to resize a volume, you can leave the New Writable Space field blank.


    Resizing Volume of database page

  5. You can schedule the resize to take place immediately or at a later time.


    Schedule for resizing storage volume of a database

  6. Click Submit.

    Note:

    You can monitor the re-size procedure from the Procedure Activity tab.

Creating Thin Volumes

This section is only for EMC Symmetrix VMAX Family and EMC VNX Storage.

An EMC Symmetrix VMAX Family or an EMC VNX storage enables you to create thin volumes and ASM disks from the created thin volumes. To create thin volumes on an EMC Symmetrix VMAX Family or EMC VNX storage, follow these steps:

Note:

Enterprise Manager enables you to create a thin volume from a thin pool after clusterware and ASM components are installed.

After you install the clusterware and ASM components, the asm_diskstring parameter may be set to Null. This could cause failure during creation of the thin pool.

To prevent this from happening, set the asm_diskstring parameter to a valid disk path and restart the ASM instance.

For example, set the asm_diskstring parameter as:

/dev/oracleasm/disks/*

  1. On the Storage Registration page, in the Storage section, select the EMC Symmetrix VMAX Family or EMX VNX storage on which you want to create thin volumes.
  2. In the Details section, select the Contents tab, and then click Create Thin Volume.

    Create Thin Volume button

  3. In the Storage Details section, the ASM Disk Group is set to Create with External Redundancy, by default. ASM Disk Group creation is optional. If you want to create an ASM Disk Group with redundancy you can skip this step for now by selecting Do not create. I will create later. You can then later create it using the Oracle Enterprise Manager ASM target home page or the ASM Configuration Assistant.
  4. Click Add to create multiple LUNs of same size and create an ASM disk group with those volumes. You can create one or more disk groups at a time.
  5. Select the thin pool/storage pool, and then specify the number of thin volumes, and the size for the thin volume.

    Note:

    It is recommended to create larger LUNs and lesser number of LUNs.

    For example, if you want a disk group of size 200 GB, create 1 LUN of size 200 GB and make a disk group out of it. Do not create 10 x 20 GB LUNs for it.

    Note:

    A thin volume of size more than 240GB is not permitted by default on a VMAX storage. To create thin volumes of size more than 240GB, request the storage administrator to enable auto meta on the VMAX. The storage administrator can remove this restriction or in the alternative, create multiple thin volumes of size less than 240GB.

    To create LUNs of size more than 240GB, contact the storage administrator to enable auto meta.

    Do not create LUNs of size more than 2TB.

  6. In the Host Details section, specify a host or a cluster, or select one by clicking the Search icon. The disks will be created on the ASM instance present on this host or cluster. A single disk partition is created on all the presented disks.

    Note:

    Only Linux and Solaris hosts are supported.

  7. Specify the root and grid infrastructure credentials. Only the credentials that you own are listed.

    Thin Volume Details

    Click Submit.

    Note:

    Once a Create Target request succeeds and a diskgroup has been created, you must manually set the attributes of the diskgroup in compatible.asm and compatible.rdbms depending on the version of the database that will be installed on the diskgroup.

Example 22-1 Understanding Space Utilization on EMC Storage Servers

Writable space implementation on EMC Storage Server is different from NetApp, Sun ZFS SA, and Sun ZFS storage servers. In NetApp, Sun ZFS SA, and Sun ZFS storage servers, writable space defined in a service template will be allocated from the storage pool to the clone database even if data is not written to the volume. In EMC storage servers (VMAX and VNX) space is only reserved on the storage pool. The space is consumed only when data is written to the volume or LUN.

For example, if you define 10GB writable space in a service template, in NetApp, Sun ZFS SA, and Sun ZFS, space of 10GB will be allocated to the clone database from storage pool even if data is not written to the volume. In an EMC storage, space is consumed only when data is written to the volume or LUN.

In Enterprise Manager, to create thin volumes (ASM Disk groups/LUNS) up to the maximum size defined for the storage pool, select the Contents tab on the Storage Registration page, and then select Create Thin Volume.The test master database can then be created on ASM Disk groups or LUNs.

The following graphic shows the Test Master database and the created clone database:


Test master and clone database

The following graphic shows the storage volume of the Test Master database:


Storage volume of the Test Master database

The following graphic shows storage volume of the clone database:


Storage volume of the clone database

Note:

ASM disk groups, as discussed, can be created using the Create Thin Volumes option. However, they can also be created using other methods. The following example illustrates the space usage on EMC VMAX and VNX storage servers:

Let us assume the Storage Pool is of size 1 TB and Storage ceiling is set to 1 TB.

Scenario 1:

If an Enterprise Manager Storage Administrator creates 2 ASM disk groups, as an example, DATA and REDO of sizes 125GB and 75GB respectively through the Create Thin Volume method and the Test Master database is created on those disk groups, used space on DATA and REDO disk groups are 100GB and 50GB respectively (remaining free space on DATA and REDO disk groups are 25GB), then each clone database created by a self service user will be allocated 25GB of writable space on the DATA and REDO disk groups.

New data written to the cloned database is the actual used space and can grow up to 25GB on each disk group. The DATA and REDO disk groups in this scenario.

The Enterprise Manager Storage Administrator will be able to create 600GB LUNs through the Create Thin volume method, assuming a clone database is created from a 200GB Test Master database. The size of the clone database will also be deducted from available space. The Self Service User will be able to create multiple clones. The number of clone databases that can be created cannot be estimated as it depends on the amount of new data written to the initial clone database in that storage pool.

Scenario 2:

If an Enterprise Manager Storage Administrator creates 2 ASM disk groups, as an example, DATA and REDO of sizes 850GB and 150GB respectively through the Create Thin Volume method, and the Test Master database is created on those ASM disk groups, used space on the DATA and REDO disk groups are 750GB and 50GB respectively (remaining free space on DATA and REDO is 100GB), then each clone database created by a self service user will be allocated 100GB of writable space on DATA and REDO disk groups.

New data written to the cloned database is the actual used space and can grow up to 100GB on each disk group. The DATA and REDO disk groups in this scenario.

Similar to Scenario 1, the Self Service User will be able to create multiple clones, but number of clone databases cannot be estimated. The Enterprise Manager Storage Administrator will not be able to create additional disk groups in scenario 2. This is the major difference when compared to Scenario 1.

In both scenarios, only the actual used space of the clones will be subtracted from the Storage Ceiling.The general formula for writable disk space is the difference between the LUN size and the actual space occupied by data.

22.3.6.2 Managing Storage Access Privileges

To manage storage access privileges for a registered storage server, follow these steps:

  1. On the Storage Registration page, in the Storage section, select a storage server from the list of registered storage servers.

    Note:

    The Storage Registration page displays only the databases which you have VIEW_STORAGE privilege on.

  2. Click Manage Access.

    Manage Access button

  3. On the Manage Access page, do the following:
    • Click Change, if you need to change the Owner of the registered storage server.

      Note:

      The Owner of a registered storage server can perform all actions on the storage server, and grant privileges and roles to other Administrators.


      Manage Access Change button

    • Click Add Grant to grant privileges to an Administrator, Role or both.

    • On the Add Grant page, enter an Administrator name or select the type, and then click Go.

    • Select an Administrator from the list of Administrators or Roles, and then click Select.

  4. On the Manage Access page, you can change privileges of an Administrator or Role by selecting the Administrator or Role from the Grantee column, and then clicking Change Privilege.
  5. In the Change Privilege display box, you can select one of the three following privileges:
    • View Storage (ability to view the storage)

    • Manage Storage (ability to edit the storage)

    • Full Storage (ability to edit or remove the storage)

    Click OK.

  6. You can also revoke a grant to an Administrator by selecting the Administrator from the Grantee column, and then clicking Revoke Grant.
  7. When you are done with granting, revoking, or changing privileges to Administrators or Roles, click Submit.

Note:

To be able to use the storage server, you also need to specifically grant privileges to the storage server and storage Management Agent credentials to the user.

22.3.6.3 Viewing Storage Registration Overview and Hierarchy

To view the storage registration overview, on the Storage Registration page, in the Details section, select the Overview tab. The Overview section provides a summary of storage usage information. It also displays a Snap Clone Storage Savings graph that shows the total space savings by creating the databases as a Snap Clone versus without Snap Clone.

Note:

If you have NetApp volumes with no space guarantee, you may see negative allocated space in the Overview tab. Set guarantee to 'volume' to prevent this.


Storage registration page Overview tab

To view the storage registration hierarchy, on the Storage Registration page, in the Details sections, select the Hierarchy tab. This displays the storage relationships between the following:

  • Test Master Database

  • Database Profile

  • Snap Clone Database

  • Snap Clone Database Snapshots

You can select a row to display the corresponding Volume or Snapshot Details.


Storage Registration page Hierarchy tab

If a database profile or Snap Clone database creation was not successful, and it is not possible to delete the entity from its respective user interface, click on the Remove button to access the Manage Storage page. From this page, you can submit a procedure to dismount volumes and delete the snapshots or volumes created from an incomplete database profile or snap clone database.

Note:

The Manage Storage page only handles cleanup of storage entities and does not remove any database profile or target information from the repository.

The Remove button is enabled only if you have the FULL_STORAGE privilege.

You can also select the Procedure Activity tab on the right panel, to see any storage related procedures run against that storage entity.

To view the NFS Exports, select the Volume Details tab. Select View, Columns, and then select NFS Exports.

The Volume Details tab, under the Hierarchy tab also has a Synchronize button.This enables you to submit a synchronize target deployment procedure. The deployment procedure collects metrics for a given target and its host, determines which volumes are used by the target, collects the latest information, and updates the storage registration data model. It can be used when a target has been recently changed, data files added in different locations, and the like.

22.3.6.4 Editing Storage Servers

To edit a storage server, on the Storage Registration page, select the storage server and then, click Edit. On the Storage Edit page, you can do the following:

  • Add or remove aliases.

  • Add, remove, or select an Agent that can be used to perform operations on the storage server.

  • Specify a frequency to synchronize storage details with the hardware.

Note:

If the credentials for editing a storage server are not owned by you, an Override Credentials checkbox will be present in the Storage and Agent to Manage Storage sections. You can choose to use the same credentials or you can override the credentials by selecting the checkbox.

22.4 Creating Test Master Databases

This section contains the following topics:

22.4.1 Creating a Discretely Synchronized Test Master

A test master database is a sanitized version of the production database. Production data can be optionally masked before the test master is created. A test master can be created from a snapshot or an RMAN Backup profile taken at a prior point in time and refreshed at specific intervals. This option is useful if the source data has to be masked to hide sensitive data.

To create a test master, follow these steps:

  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.

Note:

You can also use the emcli create_clone command to create the test master. See Creating a Database Clone Using EM CLI Verbs for more details.

22.4.2 Using a Physical Standby Database as a Test Master

A test master database is a sanitized version of the production database. A test master can be created from a live standby database by using the Oracle Data Guard feature. Profiles or snapshots can be created from the test master (see Creating a Database Provisioning Profile Using Snapshots) and these profiles can be used to create snap clones (see Requesting a Database). Since the test master is a physical standby database with live data, you must schedule and create profiles and snapshots on a periodic basis to ensure that the latest data is captured in the profile (see Creating and Refreshing Snapshots of the Test Master). Self service users can create multiple snap clones from each profile and refresh their snap clones (see Refreshing a Database) when a new profile or snapshot become available.

To create a test master, follow these steps:

  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.

22.4.2.1 Enabling the Test Master for Snap Clone

After the test master database has been created, you must enable snap clone on the database.

Note:

You need SNAP_CLONE_TARGET or FULL_TARGET privilege on the database to enable snap clone.

To enable snap clone, follow these steps:

  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.

22.4.3 Creating a Storage Test Master

To create a storage test master, follow these steps:

  1. From the Targets menu, select Databases.
  2. On the Databases page, click the name of the database target that you want to create a storage test master for.
  3. On the database home page, click Oracle Database, select Cloning, and then select Create Snapshot Test Master.
  4. On the Create Storage Test Master page, in the Reference Database section, do the following:
    • Specify the database home credentials.

    • Specify the root credentials of the database.

    • Specify the database credentials.

  5. In the Test Master field, specify a unique name for the storage test master that you want to create.

    For example, PROD_TM_Storage_TestMaster.

  6. In the Storage Details section, do the following:
    • Select the storage server that you want to use to create a storage test master on.

    • Select the project, size, and mount point for RMAN image backup of data and control files. For example, select emsdemo01 (2000.00 GB) as the project, select 3.0 GB as the size, and specify /PROD_TM_data as the mount point.

    • Select the project, size, and mount point for archive log backup. For example, select emsdemo01 (2000.00 GB) as the project, select 4.0 GB as the size, and specify /PROD_TM_arch as the mount point.

  7. In the Schedule section, you can choose to create the storage test master immediately, or you can select Later, and specify a time of your choice. You can also set a specific time or date to repeat the process.
  8. In the Purge Policy section, select either of the following:
    • None - If you do not want to purge any data.

    • Snapshots - If you want to purge the data after a certain number of snapshots has been created. Select the number of maximum snapshots.

    • Day(s) - If you want to purge the data after a certain number of days. Select the number of days.

  9. Click Create.

    Create storage test master page

22.5 Creating Snap Clone Databases

This section contains the following topics:

22.5.1 Creating Snap Clones from the Cloning Dashboard

You can create a snap clone from the Administration Dashboard and promote the snap clone as the Test Master Database. This section outlines the following procedures which you can use to create and manage snap clone databases:

22.5.1.1 Creating a Snap Clone Database

To create a Database Snap Clone, follow these steps:

  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.


      Create Snap Clone Source page

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


      Create Snap Clone database prior point in time section

  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.


      Create snap clone destination section

    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.


      Create Snap Clone Database Configuration page

  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.


    Create Snap Clone Initialization Parameters page

  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.


    Create Snap Clone Post Processing page

  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.


    Create Snap Clone Database Schedule page

  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.


    Create Snap Clone Database Review page

22.5.1.2 Creating a Test Master Database

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

22.5.1.2.1 Creating a Test Master Database Using the Clone Wizard

A test master database is a sanitized version of the production database. Production data can be optionally masked before the test master is created. A test master can be created from a snapshot or an RMAN Backup profile taken at a prior point in time and refreshed at specific intervals. This option is useful if the source data has to be masked to hide sensitive data.

To create a test master, follow these steps:

  1. On the Databases page, you can access the Full Clone database 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 Test Master.

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

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

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

  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.

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

    • Click Next.

  5. On the Create Test Master 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. Some values such as db_block_size cannot be modified.

    Click Next.

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

  7. On the Create Test Master Database: Schedule page, 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.

    Click Next.

  8. On the Create Test Master Database: Review page, review and verify the information specified 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.
22.5.1.2.2 Creating a Test Master Database Using EM CLI

To create a Test Master database execute the verb emcli create_clone -inputFile=/tmp/create_test_master.props, where create_test_master.props is the properties file with the parameters and values required to create the Test Master.

Sample properties file (create_test_master.props):

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

To verify the status of the Test Master database creation execute the EM CLI verb emcli get_instance_status -instance={instance GUI}.

22.5.1.3 Enabling a Test Master Database

To convert a database to a test master database, follow these steps:

  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.

    Enabling a Test Master Database

22.5.1.4 Disabling a Test Master Database

To disable a test master database, follow these steps:

  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.

    Disabling a Test Master database

22.5.1.5 Creating a Test Master Pluggable Database

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

22.5.1.5.1 Creating a Test Master Pluggable Database Using the Clone Wizard

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

  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.


      Create Test Master Pluggable Database: Source and Destination page

  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.


    Create Test Master PDB: Config page

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

    Test Master PDB Post Processing page

  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.


    Create Test Master PDB: Schedule page

  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.

    Create Test Master: Review Page
22.5.1.5.2 Creating a Test Master Pluggable Database Using EM CLI

To create a Test Master pluggable database, execute the command emcli pdb_clone_management -input_file=data:/xyz/sdf/pdb_test_master.props, where the sample contents of the pdb_test_master.props file is given below.

Sample properties file to create a Test master PDB:

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

Note:

You will need to add two more parameters (ACL_DF_OWNER=oracle and ACL_DF_GROUP=oinstall) in case you need to create the Test Master on Exadata ASM.

22.5.1.6 Creating a Storage Test Master

To create a storage test master, follow these steps:

  1. From the Targets menu, select Databases.
  2. On the Databases page, click the name of the database target that you want to create a storage test master for.
  3. On the database home page, click Oracle Database, select Cloning, and then select Create Snapshot Test Master.
  4. On the Create Storage Test Master page, in the Reference Database section, do the following:
    • Specify the database home credentials.

    • Specify the root credentials of the database.

    • Specify the database credentials.

  5. In the Test Master field, specify a unique name for the storage test master that you want to create.

    For example, PROD_TM_Storage_TestMaster.

  6. In the Storage Details section, do the following:
    • Select the storage server that you want to use to create a storage test master on.

    • Select the project, size, and mount point for RMAN image backup of data and control files. For example, select emsdemo01 (2000.00 GB) as the project, select 3.0 GB as the size, and specify /PROD_TM_data as the mount point.

    • Select the project, size, and mount point for archive log backup. For example, select emsdemo01 (2000.00 GB) as the project, select 4.0 GB as the size, and specify /PROD_TM_arch as the mount point.

  7. In the Schedule section, you can choose to create the storage test master immediately, or you can select Later, and specify a time of your choice. You can also set a specific time or date to repeat the process.
  8. In the Purge Policy section, select either of the following:
    • None - If you do not want to purge any data.

    • Snapshots - If you want to purge the data after a certain number of snapshots has been created. Select the number of maximum snapshots.

    • Day(s) - If you want to purge the data after a certain number of days. Select the number of days.

  9. Click Create.

    Create storage test master page

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


      Create CloneDB Source and Destination page

      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.


      Create CloneDB configuration page

  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.


    Create CloneDB initialization parameters page

  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.


    Create CloneDB Post Processing page

  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.


    Create CloneDB Schedule page

  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.


    Create CloneDB review page

22.5.1.8 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. See Refreshing Clone Databases.


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.

22.5.1.9 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

22.5.1.10 Creating a Snapshot Clone of an Exadata Test Master Database

To create a snapshot clone of an Exadata Test Master database, follow these steps:

  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.


      Exadata snapshot clone source page

  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.


      Exadata snapshot clone destination section

    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.


      Exadata snapshot clone configuration page

  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.


    Exadata snapshot clone initialization parameters page

  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.


    Exadata snapshot clone post processing page

  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


    Exadata snapshot clone schedule page

    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.


    Exadata snapshot clone review page

22.5.2 Creating Snap Clones from a Discretely Synchronized Test Master

You can create snap clones from a discretely synchronized test master if the test master is present on a NAS storage device. This table lists the steps involved in creating a snap clone using a snapshot profile.

Table 22-2 Creating Snap Clone - Discrete Flow

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Getting Started

2

Register storage servers.

See Registering Storage Servers

3

Create one or more resource providers.

See Creating Resource Providers.

4

Configure the request settings.

See Configuring Request Settings.

4

Define quotas for each self service user.

See Defining Quotas

5

Create a test master database from an RMAN Backup.

See Creating a Discretely Synchronized Test Master.

6

Enable the test master for snap clone

See Enabling the Test Master for Snap Clone

6

Create a snap clone profile from the test master.

See Creating a Database Provisioning Profile Using Snapshots

9

Create a service template based on the profile you have created.

See Creating a Service Template Using Snap Clone Profile.

10

Configure the Chargeback Service. (this step is optional)

See Configuring Chargeback.

11

Select the service template you have created and request a database.

See Requesting a Database

12

Refresh the test master and the database instance:

  • Refresh the test master.

  • Refresh the snap shot profile.

  • Refresh the snap clone database instance.

See:

22.5.2.1 Getting Started

22.5.2.2 Registering Storage Servers

22.5.2.3 Creating Resource Providers

22.5.2.4 Configuring Request Settings

22.5.2.5 Defining Quotas

22.5.2.6 Creating a Service Template Using Snap Clone Profile

22.5.2.7 Configuring Chargeback

Optionally, you can configure the chargeback service. See Chargeback Administration.

22.5.2.8 Requesting a Database

The self service user can now select the service template based on the database template profile and create a database. See Requesting a Database.

22.5.2.9 Example: Creating Snap Clones from Discretely Synchronized Test Master

The following example shows how you can create snap clones from a test master database that is refreshed at discrete intervals.

  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 Refreshing a Database. The storage space that was used by the older version of the test master will be reclaimed by the refreshed test master.

22.5.3 Creating Snap Clones from an In-Sync Test Master

You can create snap clones using a standby database that is designated as the test master database. The test master database is always current and in sync with the production database. To create snap clones using this approach, follow these steps:

Table 22-3 Creating Snap Clone (Continuous Flow)

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Getting Started.

2

Register storage servers.

See Registering Storage Servers.

3

Create one or more resource providers.

See Creating Resource Providers.

4

Configure the request settings.

See Configuring Request Settings.

5

Define quotas for each self service user.

See Defining Quotas

7

Add a standby database and designate it as the test master.

See Using a Physical Standby Database as a Test Master

Note: This standby database must be present on a registered storage server (such as NetApp, Sun ZFS, or EMC) that allows creation of snap clones.

6

Enable the test master for snap clone.

See Enabling the Test Master for Snap Clone.

7

Create snapshot profiles from the test master.

Creating a Database Provisioning Profile Using Snapshots.

8

Create a service template.

See Creating Service Template Using Snap Clone Profile

9

Configure the Chargeback Service. (this step is optional)

See Configuring Chargeback.

10

While deploying a database, select the service template you have created.

See Requesting a Database

22.5.3.1 Getting Started

22.5.3.2 Registering Storage Servers

To register storage servers for:

22.5.3.3 Creating Resource Providers

You must create one or more resource providers which include:

22.5.3.3.1 Creating a Database Pool for Database as a Service

To create a database pool for database as a service, follow these steps:

  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. From the Oracle Cloud menu, select Setup, then select Getting Started. Click the Setup link next to the Database service family, click the Database Pool link and click Create.

    Figure 22-1 Create Database Pool


    Create Database Pool

  3. In the Credentials region, specify the following credentials:
    • Host: Required for creating and starting the database.

    • Root: Users with these credentials can perform privileged actions like executing root scripts. For snap clone databases, the snapshots must be mounted by a root user. To facilitate this, privileged credentials must be set up to perform typical root user actions with SUDO privileges.

    • Grid Infrastructure: This is an optional field and is required only for creating snap clones on EMC storage to create ASM disks.

    • Automatic Storage Management: This is an optional field. It is required if you plan to use this database pool for live cloning on any database running on ASM.

  4. Enter a name and description for the database pool.
  5. Specify the following details:
    • PaaS Infrastructure Zone: Select the PaaS Infrastructure Zone into which the database instance is to be provisioned.

    • Database Configuration: Specify the configuration of the database being provisioned. This can either be Single Instance or Cluster Database (RAC) but cannot be a combination of both.

    • Platform and Version: Specify the platform and version of the database being deployed.

  6. Click Add and select one or more Oracle Homes to be added to the database pool.
  7. In the Maximum Number of Database Instances (per host), enter the maximum number of database instances that can be running on each host in the pool.

    Note:

    For RAC databases. the value specified in this field is used to ensure that the nodes on which the database is be created meets this criteria.

  8. Click Submit to create a database pool. The newly created pool will appear in the Database Cloud Self Service Portal Setup: Database Pools page. The database pool can now be added to the Service Template.

22.5.3.4 Configuring Request Settings

You can configure the request settings by specifying when a request can be made, its duration, and so on. See Configuring Request Settings for details.

22.5.3.5 Defining Quotas

After configuring the request settings, you must define quotas for each self service user. See Setting Up Quotas for details.

22.5.3.6 Configuring Chargeback

Optionally, you can configure the chargeback service. See Chargeback Administration.

22.5.3.7 Requesting a Database

The self service user can now select the service template based on the database template profile and create a database. See Requesting a Database.

22.5.3.8 Example: Creating Snap Clones from an In-Sync Test Master

The following example shows how you can create a snap clones from a physical standby database.

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

22.5.4 Creating Snap Clones from a Storage Test Master

You can use storage snapshots of the test master to create snap clones. This table lists the steps involved in creating a snap clone using a storage test master.

Table 22-4 Creating Snap Clone - Discrete Flow

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Getting Started

2

Register storage servers.

See Registering Storage Servers

3

Create one or more resource providers.

See Creating Resource Providers.

4

Configure the request settings.

See Configuring Request Settings.

4

Define quotas for each self service user.

See Defining Quotas

5

Create a storage test master.

See Creating a Storage Test Master

9

Create a service template based on the storage test master.

See Creating a Service Template from a Storage Test Master.

10

Configure the Chargeback Service. (this step is optional)

See Configuring Chargeback.

11

Select the service template you have created and request a database.

See Requesting a Database

12

Refresh the storage test master and the database instance:

  • Refresh the storage test master.

  • Refresh the snap clone database instance.

See:

22.5.4.1 Getting Started

22.5.4.2 Registering Storage Servers

22.5.4.3 Creating Resource Providers

22.5.4.4 Configuring Request Settings

22.5.4.5 Defining Quotas

22.5.4.6 Configuring Chargeback

Optionally, you can configure the chargeback service. See Chargeback Administration.

22.5.4.7 Requesting a Database

The self service user can now select the service template based on the database template profile and create a database. See Requesting a Database.

22.5.5 Creating a CloneDB Database

The CloneDB feature allows you to clone a database multiple times without copying the data into different locations. Instead Oracle Database creates the files in the Clone DB database using copy-on-write technology, so that only the blocks that are modified in the Clone DB database require additional storage on disk. Clone DB reduces the amount of storage required for testing purposes and enables rapid creation of multiple database clones. Clone DB is supported for database 11.2.0.3 or later versions.

You can create CloneDB databases by using a discretely synchronized test master by following these steps:

Table 22-5 Creating Snap Clone - Discrete Flow

Step Task Role

1

Follow the steps in the Getting Started section to enable DBaaS.

See Getting Started

3

Create one or more resource providers.

See Creating Resource Providers.

4

Configure the request settings.

See Configuring Request Settings.

5

Define quotas for each self service user.

See Defining Quotas

6

Create a database provisioning profile using snapshots from an RMAN Image Backup.

See Creating a Database Provisioning Profile Using RMAN Database Image

9

Create a service template based on the profile you have created.

See Creating a Service Template Using RMAN Image Profile.

10

Configure the Chargeback Service. (this step is optional)

See Configuring Chargeback.

11

Select the service template you have created and request a database.

See Requesting a Database

22.6 Creating a Database Provisioning Profile for Snap Clone

This section covers the following:

22.6.1 Creating a Database Provisioning Profile Using Snapshots

Prerequisites for Creating a Database Provisioning Profile Using Snapshots

Before you create a database provisioning profile, follow these prerequisites:

  • Ensure that the storage server you want to register for storage is available on the network.To register a storage server, refer to Registering and Managing Storage Servers.

    Note:

    NetApp ,Sun ZFS, Solaris ZFS, and EMC storage servers are supported in Enterprise Manager Cloud Control 12c.

  • Ensure that the storage server is connected to a Management Agent installed and monitored in Enterprise Manager Cloud Control for communication.

  • Ensure that the storage server is registered, and at least one database should be present which is enabled for Snap Clone.

  • To create the profile, you must have the EM_STORAGE_OPERATOR or EM_STORAGE_ADMINISTRATOR privileges.

Creating a Database Provisioning Profile Using Snapshots

To create a database provisioning profile, follow these steps:

Note:

When a snapshot is used by a database, it cannot be deleted. When you remove a snapshot, it becomes obsolete.

This means that you cannot request any new databases using the obsolete snapshot. This is indicated by the red pushpin against the database, which means that the snapshot is pinned and cannot be used.

When the database using that snapshot is deleted, it gets automatically purged in the next run.

  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. For information refer to Enabling or Disabling 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.

22.6.2 Creating a Database Provisioning Profile Using RMAN Database Image

To create a database provisioning profile, follow these steps:

  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.

    Reference Target page

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

    Search and Select Targets display box

  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


    Create provisioning profile using 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.

    Credentials

  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.


    Content Options page

    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.


      RMAN database image profile information page

  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.


      Database snapshot purge policy

  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.

    Review page

    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.

22.7 Creating Service Templates for Snap Clone

This section contains the following topics:

22.7.1 Creating Service Template Using Snap Clone Profile

To create a snap clone based service template, follow these steps:

  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 22-2 Create Service Template: General (Snap Clone)


    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 22-3 Create Service Template: Database (Snap Clone)


    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 22-4 Create Service Template: Initialization Parameters (Snap Clone)


    Create Service Template: Initialization Parameters
  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.

22.7.2 Creating a Service Template from a Storage Test Master

To create a storage test master based service template, follow these steps:

  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 22-5 Create Service Template: General (Storage Test Master)


    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 Storage Test Master radio button, click the Search icon and select the storage test master 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. 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.

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

  13. Click Next. The Create Service Template: Initialization Parameters page appears.
  14. 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.

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

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

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

22.7.3 Creating a Service Template Using RMAN Image Profile

To create a service template using RMAN Image Profile, follow these steps:

  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 22-6 Create Service Template: General (CloneDB)


    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.

22.7.4 Creating a Service Template for EMC Snap Clone

Note:

This option can be used only for snapshots created on EMC storage.

Prerequisites

Before you can create snap clones on EMC storage, you must ensure that the prerequisites described in Configuring EMC Storage Servers are met.

To create a service template using an existing database, follow these steps:

  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 22-7 Create Service Template: General: EMC Snap Clone


    Create Service Template: General: EMC 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 Existing Database radio button, click the Search icon and select the test master database that you had created earlier. See Using a Physical Standby Database as a Test Master for more details.
  7. Specify the host and database credentials.
  8. In the Database Definition region, the Create Snap Clone Database option is selected. Enter the following details:
    • 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. 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. Click Next. The Create Service Template: Database page appears.
  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 a Automatic Storage Management (ASM) disk group, location of the file system, and listener port you select must be available on the reference host.

  13. Specify the following:
    • Storage Type: Select Automatic Storage Management (ASM). 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 the Disk Group here.

    • Fast Recovery (Optional): To simplify the management of backup and recovery files, you can 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 ASM disk group or 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. 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.
  15. 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.
  16. 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.
  17. Click Next. The Create Service Template: Initialization Parameters page appears. 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.

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

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

22.8 Snap Clone Data Creation

This section contains the following topics:

22.8.1 Requesting a Database

To request a new database, follow these steps:

  1. Click the Request New Service link on the Database Cloud Self Service Portal. The service offerings window is displayed.
  2. In the Service Type drop down, select All to view all the service offerings available for the Database Service Family. You can select Database, Pluggable Database, or Schema to view service offerings only for the selected service type.
  3. Select a service template from the list and click Select. The service template you select can be based on RMAN backup profile, physical standby database, or snapshot based profile. Select the appropriate template according to your requirement.
  4. The New Database Service Request page appears.

    Figure 22-8 Create Database


    Create Database

    Enter the following details:

    • Request Name: Enter the name of the request.

    • Zone: Select a PaaS Zone on which the database is to be deployed.

    • Database SID: This field is displayed if the service template you have selected allows you to specify the database SID at request time. Enter a unique Database SID.

    • Database Service Name: Enter a unique database service name. The name you specify must be unique across all database, pluggable database, and schema service requests.

      You cannot use the same database service name that has been used for future scheduled requests. If a Delete operation failed, you cannot use the name specified in the failed request.

      Note:

      • You can create a standby database only if the service template you select contains a database pool with standby databases.

      • If the service template supports standby databases, depending on the preferences set up the self service administrator, you can choose to create a standby database if required. You can also select from one or more standbys (a subset of what is defined in the service template). If you do not wish to create a standby database and you select only a subset of the topology supported by the service template, you can request one or more of the remaining standbys at a later point in time after the current request has been completed.

    • Deployment Input: Specify the user name and password for the database. If you have selected an RMAN or snap clone based service template, and you are allowed to choose from the active data points, you can select an RMAN backup or snap shot here.

    • Schedule Request: Specify the schedule for the request.

    • Service Instance Properties: Any mandatory and optional target properties are displayed here. If a property is marked mandatory, you must enter a value for that property.

  5. If the service template you selected is based on a RMAN Backup, Snapshot or RMAN Image profile, the list of available backups, snapshots, or images are listed in the Snapshot region. These snapshots reflect the state of the test master database at any point in time.

    Figure 22-9 Create Database (Snapshots)


    Create Database (Snapshots)

    Select a snapshot from the list and click Submit to deploy the database to the selected zone. The new database that is created will be based on the selected snapshot.

22.8.1.1 Requesting a Schema

You can create a database service with one or more schemas and populate the schema with the required data.

Requesting an Export Profile Based Schema

You can create a schema based on a service template with a schema export profile or an empty service template. To create a schema based on a schema export profile, follow these steps:

  1. Log in to Enterprise Manager as a user with EM_SSA_USER role or any role that includes EM_SSA_USER role.

  2. The Database Cloud Self Service Portal page appears. Select Databases from the Manage drop down list to navigate to the Database Cloud Self Service Portal.

  3. Click Request New Service in the Services region.

  4. Choose a Schema Service Template with an schema export profile from the list and click Select. The Create Schema page appears. The name and description of the service template you have selected is displayed. Enter the following details:

    • Request Name: Enter a name for the schema service request.

    • Zone: Select the zone in which the schema is to be created.

    • Database Service Name: Enter a unique name for the database service.

    • Workload Size: Specify the workload size for the service request.

    • Schema Prefix: Enter a prefix for the schema. For clustered databases, the service is registered with Grid Infrastructure credentials.

  5. Click Rename Schema to enter a new name for the schema. If you wish to retain the source schema name, ensure that the Schema Prefix field is blank.

  6. Specify the password for the schema. Select the Same Password for all Schemas checkbox to use the same password for all the schemas.

  7. The Master Account for the schema is displayed. The schema with Master Account privileges will have access to all other schemas created as part of the service request.

  8. In the Tablespace Details region, the names of all the tablespaces in the schema are displayed. You can modify the tablespace name and specify a new name in the New Tablespace Name box.

  9. Specify the schedule for the request and click Submit to create the schema.

Requesting an Empty Schema

To create a schema with an empty schema template, follow these steps:

  1. Follow steps 1 to 3 listed above and in the Select Service Template window, select an empty schema template from the list.
  2. Specify the details of the schema as listed in steps 4 to 7.
  3. In the Tablespace Details region, you can specify a separate tablespace for each schema or use the same tablepsace for all the schemas.
  4. Specify the schedule for the schema request and click Submit to create the schema.

22.8.1.2 Requesting a Pluggable Database

You can request a pluggable database based on a selected service template. To request a pluggable database, follow these steps:

  1. Login to Enterprise Manager as a user with EM_SSA_USER role or any role that includes EM_SSA_USER role.
  2. The Infrastructure Cloud Self Service Portal page appears. Select Databases from the Manage drop down list.
  3. Click Request New Service in the Services region. In the Request New Service window that appears, select Pluggable Database from the Service Type drop down.
  4. Choose a service template from the list and click Select. The Create Pluggable Database page appears.

    Figure 22-10 New Pluggable Database Service Request


    New Pluggable Database Service Request
  5. Specify the following details:
    • Request Name: Enter the name of the request.

    • Zone: Select a PaaS Infrastructure Zone with the container databases into which the pluggable database is to be deployed.

    • PDB Name: Enter a unique pluggable database name.

      Note:

      • The database service name you specify must be unique across all database, pluggable database, and schema service requests.

      • You cannot use the same database service name that has been used for future scheduled request.

      • If a Delete operation failed, you cannot use the name specified in the failed request.

    • Database Service Name: Enter a unique database service name.

    • Workload Size: Workload represents the total CPU, memory, and storage requirements for each service. Select the Workload Size from the drop down list.

    • Deployment Input: Specify the pluggable database administrator user name and password.

    • Schedule Request: Specify the schedule for the request.

    • Service Instance Properties: Any mandatory and optional target properties are displayed here. If a property is marked mandatory, you must enter a value for that property.

  6. Click Submit to deploy the database to the selected zone.

22.8.2 Refreshing the Test Master Database

The test master database is created from an RMAN Backup profile of the production database taken at a particular point in time. Since the production database is constantly updated, to ensure that the latest production data is available in the test master, it has to be refreshed at periodic intervals.

To refresh the test master database, follow these steps:

  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 22-11 Test Master Refresh: Source and Destination (Now)


    Test Master Refresh: Source and Destination (Now)

    Click Next. The Configuration page appears.

    Figure 22-12 Test Master Refresh: Configuration


    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.

When the test master is refreshed, you can create a new profile based on the updated test master. The self service user can choose to refresh the database instances to the latest profile. The storage space that was used by the older version of the test master will be reclaimed by the updated (refreshed) test master.

22.8.3 Refreshing the Test Master Snapshots

You can create a new revision of the storage test master by following these steps:

  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 Test Master Snapshots tab. The list of the snapshots is displayed.

    Figure 22-13 Refresh Storage Snapshot


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

22.8.4 Snapshot Data Profile Refresh

This section covers the following topics:

22.8.4.1 Refreshing the Snap Shot Profile

After the test master has been refreshed, you must create a new revision of the snap shot profile. To do so, you must refresh the snap shot profile by following these steps:

  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 22-14 Refresh Snap Shot Profile


    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.

22.8.4.2 Creating and Refreshing Snapshots of the Test Master

After the snapshot profile has been created, you can refresh the profile at scheduled intervals and create new versions of the profile.

To create a snapshot profile of the test master (or the physical standby database), follow the steps listed in Creating a Database Provisioning Profile Using Snapshots. To refresh a snapshot profile, follow these steps:

  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 Data Profiles tab.
  2. Select the snapshot profile that is to be refreshed.

    Click Refresh. You will see a message indicating that a new snapshot (version) of the profile will be created. Click Yes to submit the refresh profile job and create a new snapshot.

22.8.4.2.1 Snapshot Purge Policy

Snapshots can be refreshed at regular intervals to ensure that the latest production data is available to the users. Every time a snapshot is refreshed, a new version of the snapshot is created. When the self service user refreshes his database to a newer version of the snapshot, the older versions can be deleted. You can delete them manually or define a purge policy while creating the snapshot.

22.8.5 Refreshing a Database

After you have created a database, you can keep the data current and consistent with the production database by refreshing it on a regular basis. To refresh a database, follow these steps:

  1. In the Database Self Service Portal Home page, click on the Name link in the Services region to drill down to the Database Home page.

    Figure 22-15 Refresh Database


    Refresh Database

  2. Click Refresh. The list of available snapshots or RMAN backups are displayed.

    Figure 22-16 Snapshots


    Snapshots

    Select a snapshot profile from the list and click Refresh. You will see a message that the database will be refreshed to the selected snapshot version and older snapshots will be deleted. Click Yes to submit the Refresh Database Request job. On successful completion of the request, the database is refreshed and will be consistent with the selected snapshot profile.

22.9 Creating Test Master Pluggable Databases and Snapshot Clones

This section provides the following different solutions of creating test master pluggable database and snapshot clones of test master pluggable databases:

22.9.1 Creating a Test Master Pluggable Database

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

  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.


      Create Test Master Pluggable Database: Source and Destination page

  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.


    Create Test Master PDB: Config page

  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.

    Create Test Master PDB Post Processing page

  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.


    Create Test Master PDB: Schedule page

  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.


    Create Test Master PDB: Review page

    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

22.9.2 Creating an Exadata Test Master Pluggable Database

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

  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.


      Create Test Master Pluggable Database: Source and Destination page

  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.


    PDB Exadata test master configuration page

  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.

    Test Master PDB Post Processing page

  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.


    Create Test Master PDB: Schedule page

  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.


    PDB exadata test master review page

22.9.3 Creating a Snapshot Clone of an Exadata Test Master PDB

Note:

You can create snapshot clones of only those test master PDBs that are of version 12.1.0.2.0 or higher.

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a snapshot clone of a test master PDB using the new Clone PDB Wizard.

To create a snapshot clone of an exadata test master PDB, follow these steps:

  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.


      PDB exadata snapshot clone source page

  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.

    PDB exadata snapshot clone source and destination page

  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.


      PDB exadata snapshot clone config page

  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.


    PDB exadata snapshot clone post processing page

  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.


    PDB exadata snapshot clone schedule page

  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.


    PDB exadata snapshot clone review page

22.9.4 Creating an ACFS Test Master Pluggable Database

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a test master PDB from a source PDB, using the new Clone PDB Wizard.

To create a test master PDB from a source PDB, follow these steps:

  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.


      Create Test Master Pluggable Database: Source and Destination page

  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.


    Test master pdb acfs config page

  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.

    Test Master PDB Post Processing page

  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.


    Create Test Master PDB: Schedule page

  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.


    PDB acfs test master review page

22.9.5 Creating a Snapshot Clone of an ACFS Test Master PDB

Note:

You can create snapshot clones of only those test master PDBs that are of version 12.1.0.2.0 or higher.

If you have the 12.1.0.8 Enterprise Manager for Oracle Database plug-in deployed in your system, you can create a snapshot clone of a test master PDB using the new Clone PDB Wizard.

To create a snapshot clone of an exadata test master PDB, follow these steps:

  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.


      PDB exadata snapshot clone source page

  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.

    PDB exadata snapshot clone source and destination page

  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.


      PDB ACFS snapshot clone config page

  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.


    PDB exadata snapshot clone post processing page

  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.


    PDB exadata snapshot clone schedule page

  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.


    PDB ACFS snapshot clone review page

22.9.6 Enabling a Test Master Pluggable Database

To convert a pluggable database into a test master, follow these steps:

  1. Right click on the pluggable database target name that you want to enable as a test master, select Oracle Database, select Cloning, and then select Enable as a Test Master.
  2. On the Enable as a Test Master page, in the Credentials section, specify the credentials for the container database of the pluggable database, and the credentials of the Oracle Home.
  3. In the Source section, specify or search for the parent database from which the database has been created. This provides better lineage tracking.
  4. In the Data Masking section, you can choose to desensitize the data by applying masking templates or by running additional scripts of your choice.
  5. In the Custom Scripts section, you can select the Software Library components which contain post cloning scripts. The clone database can also be customized by executing the post cloning SQL script.
  6. Click Submit.

    Enabling a test master PDB

22.9.7 Disabling a Test Master Pluggable Database

Disabling a test master pluggable database, resets the data files to read-write mode and restarts the pluggable database in open mode. You can make further changes to the database and then enable it as a test master again.

To disable a test master pluggable database, follow these steps:

  1. Right click on the test master pluggable database, select Oracle Database, select Cloning, and then select Disable as a Test Master.
  2. On the Disable Test Master page, specify the credentials of the container database of the test master pluggable database. Also, specify the credentials of the Oracle Home.
  3. Click Submit.

    Disabling a test master pdb page