Skip Headers
Oracle® Enterprise Manager Cloud Administration Guide
12c Release 3 (12.1.0.3)

E28814-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

11 Setting Up a DBaaS Cloud

This chapter covers the initial configuration required to enable a Database as a Service Cloud. It contains the following sections:

11.1 Setting Up the DBaaS Cloud

You can set up the DBaaS Cloud in two ways:

11.2 Getting Started

This section helps you get started by providing an overview of the steps involved in setting up a Private Database Cloud. Before you set up the database cloud, you must download and deploy the required plug-ins. For more details, see Section 3.3, "Deploying the Required Plug-ins".

Table 11-1 Getting Started with DBaaS

Step Task Role

1

Define roles for administrators and self service users. See Section 3.4, "Defining Roles and Assigning Users".

Super Administrator

2

Install the Management Agent on unmanaged hosts so that they can be monitored by Enterprise Manager. Section 9.2, "Adding Hosts".

Super Administrator

3

Configure Privilege Delegation Settings on your managed hosts. Section 3.6, "Configuring Privilege Delegation Settings".

Super Administrator

4

Configure the storage location for the Software Library. See Section 3.1, "Setting Up the Software Library"

Cloud Administrator

6

Set up provisioning credentials. See Section 11.3, "Setting Up Credentials for Provisioning".

Self Service Administrator

7

If you are:

Self Service Administrator

8

Configure the Listener. See Section 11.7, "Configuring the Oracle Listener".

Self Service Administrator

9

Register the storage servers. See Section 11.8, "Registering and Managing Storage Servers".

Self Service Administrator


Figure 11-1 shows the sequence of steps involved in enabling Database or Schema as a Service.

Figure 11-1 Enabling Database / Schema as a Service

Enabling Database / Schema as a Service

11.3 Setting Up Credentials for Provisioning

Before you perform any operations on the Managed Servers or databases, you must define the credentials that will be used by Enterprise Manager to connect to the targets.

You need to set up the following types of credentials:

  • Normal credentials are the host operating system credentials used to provision the database software and create databases. For example, oracle/<login password>. These credentials are saved when the Database Pool is created and are used when the EM_SSA_USER requests a database or a schema.

  • Privileged credentials are the host operating system credentials used to perform privileged actions like executing root scripts. These credentials are used deploying software (for running root.sh during deployment), for mounting and unmounting storage volumes (for databases created with snapshots) and so on. These credentials are saved along with the Database Pool if the pool is used for creating databases using snapshots.

  • Database SYSDBA credentials are used and saved for schema as a service database pool. These credentials are required only for schema as a service.

Note:

It is recommended that the same OS user who owns the Oracle Home on the host, creates the database.

To create named credentials, follow these steps:

  1. Log in to Enterprise Manager as an administrator with the EM_SSA_ADMINISTRATOR role.

  2. From the Setup menu, select Security, then select Named Credentials.

  3. Click Create in the Named Credentials page.

  4. Enter the Credential Name and Credential Description. Set the Authenticating Target Type field to Host and Scope field to Global. Enter the user name and password in the Credential Properties section. If you need to set privileged credentials, select Sudo or PowerBroker in the Run Privilege field and enter values in the Run As and Profile fields.

  5. Click Test and Save.

  6. Verify these credentials against a host target and click OK.

11.4 Provisioning Database Software

Before you can enable database as a service, the database software must already be provisioned on all hosts. Database software can be provisioned by an administrator with the EM_SSA_ADMINISTRATOR role in the following ways:

  • Provisioning Profile

    • Capture a gold image of an existing database using a Provisioning Profile. See the Enterprise Manager Lifecycle Management Administrator's Guide for details.

    • Use the Provisioning Profile to provision the Clusterware/ASM or Grid Infrastructure (for Real Application Cluster databases), and Database Oracle Home. This method ensures that the necessary database plug-in (monitoring part of the database plug-in) is deployed onto the Management Agent as part of the database provisioning Oracle Home installation.

      To create a provisioning profile, from the Enterprise menu, select Provisioning and Patching, then select Database Provisioning and select the database provisioning deployment procedure to be used. You can select either Provision Oracle Database or Provisioning Oracle RAC Database deployment procedure.

      Note: Do not create a new database as part of this deployment procedure.

  • Using the Database Installer

    • From the Setup menu, select Extensibility, then select Plug-ins. and deploy the complete database plug-in on all the Management Agents in a PaaS Infrastructure Zone.

    • Run the Clusterware/ASM or Grid Infrastructure installer to set up the cluster and ASM (for RAC databases).

    • Run the Database Installer and ensure you select the create database option on all hosts.

    • Discover the database. From the Setup menu, select Add Target, then Add Targets Manually, and then select Add Non-Host Targets Using Guided Process (Also Adds Related Targets).

    • From the Enterprise menu, you can also select Job, then select Library and submit the Discover Promote Oracle Home Target job to add the Oracle Home.

For more details on provisioning the database software, see the Enterprise Manager Lifecycle Management Administrator's Guide.

11.5 Deploying the Database

For schema as a service, you must deploy a single instance or RAC database. To deploy a database, you must use the Provision Oracle Database deployment procedure. See the Enterprise Manager Lifecycle Management Administrator's Guide for details.

11.6 Creating a Container Database

An Oracle Database can contain a portable collection of schemas, schema objects, and nonschema objects, that appear to an Oracle Net client as a separate database. This self-contained collection is called a pluggable database (PDB). A multi-tenant container database (CDB) is a database that includes one or more PDBs.

You can create a CDB either by using the Database Configuration Assistant (DBCA) or the CREATE_DATABASE SQL statement. See the Oracle Database Administrator's Guide for details. After the CDB is created, it consists of the root and the seed. The root contains minimal user data or no user data, and the seed contains no user data.

PDBs contain user data. After the CDB has been created, you can add PDBs to the CDB by using either of the following options:

  • Create a new CDB. See the Lifecycle Management Administrator's Guide for details.

  • Plug in an unplugged PDB into a CDB. See the Lifecycle Management Administrator's Guide for details.

11.7 Configuring the Oracle Listener

You need to configure an Oracle Home and the Oracle Listener before you can add them as Enterprise Manager targets.

To set up the Oracle Listener (Listener) for the database hosts, follow these steps:

  1. Log in as a user with the EM_SSA_ADMINISTRATOR role and perform mass deployment of database homes on the newly added hosts as described in Section 9.2, "Adding Hosts".

  2. To configure a Listener running from the same Oracle Home on which the database instance is to be created, launch a Bash shell and enter the following commands:

    1. <AGENT_BASE>/agent_inst/bin/emctl stop agent

    2. export TNS_ADMIN=<DB_HOME_LOCATION>/network/admin

    3. <AGENT_BASE>/agent_inst/bin/emctl start agent

    4. export ORACLE_HOME=<DB_HOME_LOCATION>

    5. Run $ORACLE_HOME/bin/netca and create the listener. Make sure you have the same Listener name and Listener port on all the hosts.

  3. To configure a Listener running from the Single Instance High Availability (SIHA) Oracle Home, launch a Bash shell and enter the following commands:

    1. export ORACLE_HOME=<SIHA_HOME_LOCATION>

    2. Run $ORACLE_HOME/bin/netca and create the listener. Make sure you have the same listener name and listener port on all the hosts

  4. Log in as the user with the DBAAS_ADMIN_ROLE and discover the newly added Listener target on all the hosts. From the Setup menu, select Add Target, then select Add Target Manually.

  5. Select the Add Non-Host Targets Using Guided Process option and select Target Type as Oracle Database, Listener, and Automatic Storage Management and click Add Guided Discovery and follow the steps in the wizard. Before you add the new Listener target, ensure the ORACLE_HOME for the Listener is pointing to the correct ORACLE_HOME location. This process adds the Oracle Home target which is used when a database pool is created.

11.8 Registering and Managing Storage Servers

This chapter contains the following sections:

11.8.1 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 and 7420 models.

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

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

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

11.8.2 Overview of Registering Storage Servers

Registering a storage server, such as NetApp storage server or Sun ZFS 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.

11.8.3 Prerequisites for Registering Storage Servers

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

11.8.3.1 Configuring Storage Servers

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

Note:

Only NetApp and Sun ZFS storage servers are supported in Enterprise Manager Cloud Control 12c.
11.8.3.1.1 Obtaining NetApp Hardware Privileges and Licenses

NetApp Hardware Privileges

Privileges is a generic term. The term varies for different storage server vendors. For example, NetApp refers to privileges as Capabilities.

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

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

Setup for NetApp Storage Server

Note:

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

To set up the NetApp storage server, follow these steps:

  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.

NetApp Hardware Licenses

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

  • flex_clone

  • nfs

  • snaprestore

11.8.3.1.2 Obtaining Sun ZFS Hardware Privileges and Licenses

Privileges is a generic term. The term varies for different storage server vendors. 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 hardware user:

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

Setup for Sun ZFS Storage Server

To setup the Sun ZFS storage server, 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.

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.

11.8.3.1.3 Obtaining Solaris ZFS Hardware Privileges and Licenses

Solaris ZFS Hardware Privileges

Privileges is a generic term. The term varies for different storage server vendors. For example, Solaris ZFS refers to privileges as Permissions.

For Solaris ZFS storage server, to use Snap Clone, grant the following privileges on the the pool for the Solaris ZFS hardware user:

  • clone

  • create

  • destroy

  • mount

  • rename

  • rollback

  • share

  • snapshot

  • quota

  • reservation

  • sharenfs

  • canmount

  • recordsize

Solaris ZFS Hardware Licenses

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

11.8.3.2 Customizing Storage Agent Proxy

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

Note:

Storage Proxy Agent is supported only on Linux Intel x64 platform.
11.8.3.2.1 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)

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

11.8.3.2.3 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,
11.8.3.2.4 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.

11.8.3.3 Granting Roles and Privileges

To perform various storage server activities, you need to grant the following roles and privileges:

11.8.3.3.1 Accessing Security Class

Table 11-2 displays the security class you need for accessing privileges for storage management.

Table 11-2 Security Class

Security Class Description Base Table Base Table Column

STORAGE

Defines access privileges for storage management

SMF_STORAGE_HARDWARE

STORAGE_HARDWARE_GUID

STORAGE_HARDWARE_NAME

CREATED_BY


11.8.3.3.2 Granting General Privileges

Table 11-3 displays the general privileges you need to set before you register a storage server.

Table 11-3 General Privileges for Storage Server Registration and Management

Privilege Description Scope Notion Included Privilege

VIEW_ANY_STORAGE

Ability to view any storage.

class

VIEW

nil

REGISTER_STORAGE

Ability to register storage.

class

CREATE

nil

VIEW_STORAGE

Ability to view storage details.

object

VIEW

nil

MANAGE_STORAGE

Ability to synchronize storage.

object

EDIT

VIEW_STORAGE

CREATE_JOB

MANAGE_ANY_STORAGE

Ability to manage any of the registered storage servers.

object

EDIT

VIEW_ANY_STORAGE

CREATE_JOB

FULL_STORAGE

Ability to modify or remove storage.

object

FULL

MANAGE_STORAGE


11.8.3.3.3 Granting Target Privileges

Table 11-4 displays the target privilege you need to set, for enabling or disabling Snap Clone for a target.

Table 11-4 Target Privilege for Enabling or Disabling Snap Clone

Target Privilege Scope Notion Include In Privilege Included Privilege Applicable Target Type

SNAP_CLONE_TARGET

object

Manage

FULL_TARGET

VIEW_TARGET

oracle_database

rac_database


11.8.3.3.4 Granting Roles

Table 11-5 displays the roles you need to grant to be able to register a storage server and perform various activities on the registered storage server.

Table 11-5 Roles for Registering and Managing the Storage Server

Role Description Security Class Privilege Granted To Role

EM_STORAGE_ADMINISTRATOR

Role has privileges to register storage hardware for Snap Clone.

STORAGE

STORAGE

TARGET

TARGET

NAMED_CREDENTIALS

JOB

SWLIB_ENTITY_MGMT

MANAGE_ANY_STORAGE

REGISTER_STORAGE

VIEW_ANY_TARGET

PERFORM_OPERATION_ANYWHERE

CREATE_CREDENTIAL

CREATE_JOB

SWLIB_CREATE_ANY_ENTITY

SWLIB_VIEW_ANY_ENTITY

EM_ALL_ADMINISTRATOR

EM_STORAGE_OPERATOR

Role has privileges to manage storage hardware for Snap Clone.

STORAGE

TARGET

TARGET

JOB

SWLIB_VIEW_ANY_ENTITY

MANAGE_ANY_STORAGE

VIEW_ANY_TARGET

PERFORM_OPERATION_ANYWHERE

CREATE_JOB

SWLIB_VIEW_ANY_ENTITY

EM_ALL_OPERATOR


11.8.3.3.5 Granting Privileges for Provisioning

You need the following privileges to be able to use the storage server for provisioning:

  • VIEW_STORAGE on the storage server

  • GET_CREDENTIAL on the storage server

  • GET_CREDENTIAL on all the Management Agent credentials of the storage server

  • PERFORM_OPERATION on the storage server Management Agent

Note:

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.

11.8.4 Registering Storage Servers

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 or Sun ZFS Storage, 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:

    Enterprise Manager Cloud Control 12c supports only NetApp and Sun ZFS storage servers.

    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.

      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.

  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.

      Submit registration job

11.8.5 Administering the Storage Server

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

11.8.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. Synchronize button

    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.

  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.

    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.

11.8.5.2 Enabling or Disabling Snap Clone

To enable or disable Snap Clone, do the following:

Note:

You need SNAP_CLONE_TARGET or FULL_TARGET privilege on the database to enable or disable Snap Clone.
  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 or Disable 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 enable 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 enabled or disabled successfully for the database, a confirmation display box appears. Click OK.

    Note:

    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.

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

    Deregistration confirmation

    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.

11.8.6 Managing Storage Servers

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

11.8.6.1 Managing Storage Allocation

You can manage storage allocation by performing the following tasks:

  • Editing the Storage Ceiling

  • Creating Storage Volume

  • Resizing Volumes of a Database

11.8.6.1.1 Editing the Storage Ceiling

Storage Ceiling is the maximum amount of storage from a project or aggregate 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.

11.8.6.1.2 Creating Storage Volume

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

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

  4. Select a storage and specify the volume information.

  5. In the Host Details section, select the host credentials for which the permissions to access the volume would be granted.

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

  7. Click Submit.

11.8.6.1.3 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:

Resizing of volumes of a Test Master database cannot be done using Enterprise Manager.

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

  4. On the Resize page, specify the new size for the volume or volumes that you want to resize. If you do not want to resize a volume, you can leave the New Size field blank.

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

  6. Click Submit.

    Note:

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

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

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

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

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