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

E27046-20
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

4 Overview of Database Provisioning

This chapter provides an overview of the database provisioning feature in Oracle Enterprise Manager Cloud Control (Cloud Control), supported targets and deployment procedures offered by Cloud Control, and the infrastructure you need to set up to get started with database provisioning. In particular, this chapter covers the following:

4.1 Overview of Database Provisioning Feature

The Provisioning solution is an important part of Lifecycle Management solution offered by Cloud Control. As part of the database provisioning solution, Cloud Control enables you to provision Oracle Databases (also known as single-instance databases) and Oracle Real Application Clusters databases, extend or delete Oracle Real Application Clusters nodes, provision Oracle Real Application Clusters One node databases, provision pluggable databases, and also upgrade Oracle single-instance databases in a scalable and automated manner. Figure 4-1 shows the database provisioning solution in Cloud Control.

Figure 4-1 Database Provisioning Solution in Cloud Control

Surrounding text describes Figure 4-1 .

For this release, database provisioning features are as follows:

Designer and Operator Roles

Cloud Control offers clearly defined administrator roles such as Designers and Operators. With a Designer role, you can lock down one or more fields in the deployment procedures, thus allowing the operators to run the procedure only with standard, preset configurations.

Locking Down Feature in Designer Role

The locking down feature in Database Provisioning enables Designers to lock down the set of variables, such as host targets, credentials, Oracle homes to be provisioned, and others, in the deployment procedure wizard. This enforces standard deployments and minimizes errors in configurations during mass deployment. The operator can then deploy the procedure that the designer configures and saves in the Procedure Library. For more information about locking down deployment procedures, see Section 36.4.2.1.

Provisioning Profiles and Database Templates

You can create Provisioning Profiles to be used in database provisioning to ensure standardization in deployments and to minimize errors. You can also create database templates from the Cloud Control Console to be used in your provisioning activities.

Creating Databases Using Cloud Control

Cloud Control now enables you to create databases from the Cloud Control console. This ensures that you can use a single interface for provisioning and creating databases. For more information about creating databases, see Chapter 15.

Easy to Navigate Database Provisioning Wizards

Designers and Operators can easily use and navigate through the enhanced Database Provisioning wizards in Cloud Control.

Self Update

Using the Self Update feature, you can automatically download and install updates to your provisioning entities. For more information on using the Self Update feature to update your provisioning entities, see Section 2.6.

Database Provisioning Console for all Database Provisioning Activities

The Database Provisioning console is a starting point for your database provisioning activities. The console displays information about provisioning setup, profiles, deployment procedures, and information about getting started with provisioning.

Figure 4-2 shows how you can access the Database Provisioning screen from within Cloud Control console.

Figure 4-2 Accessing Database Provisioning Screen

Surrounding text describes Figure 4-2 .

4.2 Supported Targets and Deployment Procedures for Database Provisioning

Cloud Control enables you to perform database provisioning using deployment procedures. A deployment procedure is a set of predefined steps that complete the task of provisioning. For information about deployment procedures in general, see Chapter 36.

Table 4-1 lists the database deployment procedures offered by Cloud Control and the various targets that can be provisioned.

Table 4-1 Database Deployment Procedures and Targets Provisioned

Deployment Procedure Targets Provisioned

Provision Oracle Database

  • Oracle Database (single instance) 10g Release 1 to 12c

  • Oracle Grid Infrastructure 12c

  • Oracle Automatic Storage Management (Oracle ASM) 12c

Provision Oracle Real Application Clusters

  • Oracle Real Application Clusters (Oracle RAC) 12c

  • Oracle RAC One Node 12c

  • Oracle Grid Infrastructure 12c

  • Oracle Automatic Storage Management (Oracle ASM) 12c

Create Oracle Database

  • Oracle Database (single-instance database) 12c

  • Oracle Real Application Clusters (Oracle RAC) 12c

  • Oracle RAC One Node 12c

Provision Pluggable Database

Note: You cannot manually invoke this deployment procedure from the Database Provisioning page. This deployment procedure is invoked internally when you use the Provision Pluggable Database console or EM CLI to provision pluggable databases.

Pluggable Databases (available only as a part of Oracle Database 12c Release 1 or higher)

Provision Oracle Clusterware / Oracle RAC for UNIX and RDBMS versions 10g/11g (applicable for UNIX platform)

  • Oracle Real Application Clusters (Oracle RAC) 10g Release 1 to 11g Release 1

  • Oracle Clusterware 10g Release 1 to 11g Release 1

  • Oracle Clusterware Automatic Storage Management (Oracle ASM) 10g Release 1 to 11g Release 1

Provision Oracle Clusterware / Oracle RAC for Windows and RDBMS versions 10g/11g (applicable for Windows platform)

  • Oracle Real Application Clusters (Oracle RAC) 10g Release 1 to 11g Release 1

  • Oracle Clusterware 10g Release 1 to 11g Release 1

  • Oracle Clusterware Automatic Storage Management (Oracle ASM) 10g Release 1 to 11g Release 1

Extend/Scale Up Oracle Real Application Clusters

Oracle Real Application Clusters (Oracle RAC) 10g Release 1 to 11g Release 2

Delete/Scale Down Oracle Real Application Clusters

Oracle Real Application Clusters (Oracle RAC) 10g Release 1 to 11g Release 2

Provision Oracle Database Client

Oracle Database Client 10g Release 2 to 11g Release 2


Table 4-2 lists various use cases for database provisioning deployment procedures.

Table 4-2 use cases for Database Deployment Procedures

Deployment Procedure use case Link

Provision Oracle Database

  • Provisioning and Creating Single-Instance Databases

  • Provisioning Single-Instance Database with Oracle Automatic Storage Management

  • Provisioning Single-Instance Database Software Only

  • Provisioning Oracle Grid Infrastructure with Single-Instance Database and Configuring Database with Oracle Automatic Storage Management

  • Provisioning Oracle Grid Infrastructure and Single-Instance Database Software Only

Provision Oracle Real Application Clusters

  • Provisioning Grid Infrastructure with Oracle Real Application Clusters Database and Configuring Database with Oracle Automatic Storage Management

  • Provisioning Oracle Real Application Clusters Database with File System on an Existing Cluster

  • Provisioning Oracle Real Application Clusters Database with File System on a New Cluster

Create Oracle Database

  • Creating Single-Instance Database

  • Create Oracle Real Application Clusters Database

  • Creating Oracle Real Application Clusters One database

Provision Pluggable Database

  • Creating a New Pluggable Database

  • Plugging In an Unplugged Pluggable Database

  • Cloning a Pluggable Database

  • Migrating a Non-Container Database as a Pluggable Database

  • Unplugging and Dropping a Pluggable Database

Provision Oracle Clusterware / Oracle RAC for Windows and RDBMS versions 10g/11g

Provision Oracle Clusterware / Oracle RAC for UNIX and RDBMS versions 10g/11g

  • Cloning a Running Oracle Real Application Clusters

  • Provisioning Oracle Real Application Clusters Using Gold Image

  • Provisioning Oracle Real Application Clusters Using Archived Software Binaries

Extend/Scale Up Oracle Real Application Clusters

Extending Oracle Real Application Clusters

Section 10.2

Delete/Scale Down Oracle Real Application Clusters

Deleting Oracle Real Application Clusters

Section 11.3

Section 11.4

Provision Oracle Database Client

  • Cloning a Running Oracle Database Replay Client

  • Provisioning Oracle Database Replay Client Using Gold Image

  • Provisioning Oracle Database Replay Client Using Installation Binaries


4.3 Setting Up Database Provisioning

You can provision Oracle Databases, Oracle Real Application Clusters Databases, and Oracle RAC One Node Databases using database templates, installation media, or database entities, or you can use provisioning profiles to standardize deployments.

This section explains the following:

Note:

If you have upgraded from an older version of Cloud Control to version 12c, you will need to ensure that CSH shell is present as /bin/csh before you can run the database provisioning deployment procedures.

4.3.1 Meeting Basic Infrastructure and Host Requirements

To satisfy these requirements, you must do the following:

  • Meet the basic infrastructure requirements as described in Chapter 2.

  • Ensure that the host is set up for database provisioning entities. For more information about host readiness, see Appendix B.

4.3.2 Understanding Administrator Privileges for Provisioning Database

Table 4-3 describes the roles and the minimum privileges required for using database deployment procedures. These roles are default roles available in Cloud Control. You need not create them, but you must explicitly create administrators based on these roles. For instructions, see Section 2.4.

Table 4-3 Privileges for Using Deployment Procedures

Role Target Privileges Resource Privileges Implementation Recommendation

EM_PROVISIONING_DESIGNER

Operator any target

  • Resource Type:

    Deployment Procedure

    Privilege:

    Create, Manage Launch Access

  • Resource Type:

    Software Library Entity

    Privilege:

    Manage Any Software Library Entity

Required when you want to grant and restrict access to deployment procedures.

EM_PROVISIONING_OPERATOR

  • Operator any target

  • Launch DP Permission

  • Resource Type:

    Deployment Procedure

    Privilege:

    Create, Manage Launch Access

  • Resource Type:

    Software Library Entity

    Privilege:

    Manage Any Software Library Entity

Required when you want to launch deployment procedures.


4.3.3 Prerequisites for Designers

Following are the prerequisites for designers to start database provisioning:

  • Ensure that you meet the mandatory infrastructure requirements described in Chapter 2.

  • Discover and monitor the destination hosts in Cloud Control. For this purpose, you need the latest version of Oracle Management Agent (Management Agent) on the destination hosts. For more information refer to the Oracle Cloud Control Installation and Basic Configuration Guide. Ensure that the agents are installed in the same location on all hosts.

  • Set up the Oracle Software Library (Software Library). Ensure that the installation media, database templates, or provisioning entities are available in the Software Library. For information about creating them, see Section 4.3. Alternatively, use a provisioning profile to store the database template. For information about creating a database provisioning profile, see Section 4.3.5.

  • Store the operating system credentials of the destination hosts as preferred credentials in Oracle Management Repository (Management Repository) or use Named Credentials.

    If you are using SUDO, PowerBroker, see Section 2.3.3 for information on setting up these authentication utilities.

  • Ensure that the operating system groups corresponding to the following roles already exist on the hosts you select for provisioning. If these groups do not exist, then the Deployment Procedure automatically creates them. However, if these have to be created on NIS, then you must create them manually before running the Deployment Procedure. For information about creating these operating system groups, refer to the Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2).

    The Oracle Database user (typically oracle) must be a member of the following groups:

    • Inventory Group (OINSTALL) as the primary group

    • Database Administrator (OSDBA)

    • Database Operator (OSOPER)

    The Grid Infrastructure user (typically grid) must be a member of the following groups:

    • Inventory Group (OINSTALL) as the primary group

    • ASM Database Administrator (ASMDBA)

    • ASM Instance Operator (ASMOPER)

    • ASM Instance Administrator (OSASM)

  • Ensure that you use an operating system user that has write permission on the following locations:

    • Oracle base directory for Grid Infrastructure where diagnostic data files related to Grid Infrastructure can be stored.

    • Oracle base directory for database where diagnostic data files related to database can be stored.

    • Grid Infrastructure software directory where Grid Infrastructure software can be provisioned.

    • Database software location where database software can be provisioned Working directory where cloning-related files can be staged.

  • Ensure that you have Operator-Any Target privileges in Cloud Control.

  • For provisioning Oracle Real Application Clusters Databases (Oracle RAC), the following are additional prerequisites:

    • Meet the hardware, software, and network requirements for Oracle Grid Infrastructure and Oracle RAC installation on the target hosts. For information about the hardware, software, and network requirements for Oracle Grid Infrastructure and Oracle RAC installation, refer to the Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2).

    • The Oracle RAC Database user must be a member of the group ASM Database Administrator (ASMDBA).

4.3.4 Prerequisites for Operators

Operators who run the deployment procedures must meet the following prerequisites:

  • Ensure that as an operator, you have permissions to view credentials (set and locked by the designer), view targets, submit jobs, and launch deployment procedures.

  • Ensure that the operating system groups corresponding to the following roles already exist on the hosts you select for provisioning. The operating system users of these groups automatically get the respective privileges.

    • Inventory Group (OINSTALL)

    • ASM Database Administrator (ASMDBA)

    • ASM Instance Operator (ASMOPER)

    • Database Administrator (OSDBA)

    • Database Operator (OSOPER)

    • ASM Instance Administrator (OSASM)

  • Ensure that you have Operator-Any Target privileges in Cloud Control.

4.3.5 Creating Provisioning Profiles

Provisioning Profile is an entity that contains software bits and configuration. When a provisioning profile is created from an existing installation, it provides the flexibility to clone either Grid Infrastructure (with software or configuration) and Oracle Database (with software or configuration). You can create database templates using provisioning profiles. A designer or administrator can create a database provisioning profile as a one-time activity that can be used by operators for mass deployment. Using provisioning profile enables standardization in deployments and reduces the need for rescheduling deployments by avoiding errors while configuring deployment procedures.

To create database provisioning profile, follow these steps:

  1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning.

  2. In the Database Procedures page, in the Profiles section, click Create. The Create Database Provisioning Profile wizard is launched.

    Database Provisioning Profile Creation
  3. On the Reference Target page, click the search icon.

  4. On the Search and Select: Targets window, select the reference target from which you want to create the provisioning profile, and then click Select.

  5. In the Reference target page, the Include Operation allows you to select the components you want to include in the provisioning profile. Depending on the reference host configuration, you can select to include Database Oracle Home, Grid Infrastructure Oracle Home, and their related configuration as part of the provisioning profile as below:

    • Database Oracle Home to include Oracle database gold image in the profile

    • Grid Infrastructure Oracle Home and its Configuration Properties to include Grid infrastructure gold image and its configuration in the profile

    • Data Content to include Oracle database template (or Data) in the profile where you can Select Structure and Data to include physical and structural files from the database or Structure only to include only the structural files in the template.

      Database Provisioning Profile Reference Target Section
  6. In the Credentials section, select Preferred Credentials or Named Credentials. If using Named Credentials, select the credentials or click + to specify new Named Credentials.

    In the Add Credentials window, specify the User Name and Password. Select Set as Preferred Credentials if you want to set these as the Preferred Credentials. Click Add.

    Click Next.

    Database Profile Reference Targets Credentials
  7. On the Profile page, do the following:

    • In the Profile Information section, enter a unique profile name of your choice.

      For example:
      Cluster Profile [time when created]
      

      Retain or edit the default details such as Profile Location where you want to store the provisioning profile in the Software Library, Name, Description, Version, Vendor, Notes, and the Name of Components included in the profile.

    • In the Schedule section, you can choose to start the profile creation immediately, or you can schedule it for a later time.

    • In the Working Directory section, specify the temporary working directory to be used during database provisioning profile creation.

    • In the Software Library Storage section, select the Software Library Location Type and Software Library Location Name.

    • Click Next.

    Database Profile
  8. In 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. The Deployment Instance Name is generated with the profile name and user name.

  9. Once you have submitted the provisioning profile creation job, ensure that the provisioning profile appears in the Database Provisioning page.

4.3.6 Creating Installation Media

To create installation media that can be used for database provisioning, follow these steps:

  1. Create a temporary location mkdir /tmp/installmedia.

  2. Navigate to the following URL:

    http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

  3. Click the See All link for the operating system on which you want to provision the database.

  4. Select Accept License Agreement.

  5. Download zip files 1 and 2 for Database and Grid Infrastructure software to the temporary directory created earlier.

  6. Navigate to the temporary directory and extract the contents of the zip files.

    For example, to extract the contents of the database software zip files, run these commands:

    Unzip linux_11gR2_database_1of2.zip
    Unzip linux_11gR2_database_2of2.zip
    
  7. Create a single zip file with the contents of both the downloaded zip files.

    For example, to create a zip for the two database software zip files you downloaded, first extract the contents of each of the zip files as described in the previous step, and then run the following command to create one complete zip file:

    zip -r linux_11gR2_database.zip database/ 
    
  8. In Cloud Control, from the Enterprise menu, select Provisioning and Patching and then select Software Library.

  9. In Software Library, select the directory where you want to create the installation media component for the database.

  10. From the Actions menu, select Create Entity, then select Component.

  11. In the Create Entity: Component dialog, select Subtype as Installation Media and click Continue.

  12. In the Create Installation Media: Describe page, enter the Name and Description for the component, and click Next.

  13. In the Create Installation Media: Configure page, select Product Version, Platform, and Product from the list.

    For Product, select Oracle Database for Oracle Database, Oracle Client for Oracle Database Replay Client, and Oracle Grid Infrastructure for Grid Infrastructure software.

    Click Next.

  14. In the Create Installation Media: Select Files page, select Upload Files.

    1. In the Specify destination section, choose a Software Library storage location as the Upload Location for the database software.

    2. In the Specify Source section, select File Source as Agent Machine and select the host from which you want to upload the files.

    3. Click Add.

    4. In the Remote File Browser, click Login As.

    5. Select the Host Credentials and click OK.

    6. Navigate to the temporary directory and select the zipped database file created earlier.

    7. Click Add and then click OK.

    Click Next.

  15. In the Create Installation Media: Review page, review the details you have provided and click Save and Upload to save and upload the installation media files to Software Library.

4.3.7 Creating Database Templates

Cloud Control allows you to create database templates that you can use for cloning or creating additional databases. To create database templates, follow these steps:

  1. From the Targets menu, select Databases.

  2. In the Databases page, click on the database from which you want to create a template.

  3. In the Database home page, from the Oracle Database menu, select Provisioning, then select Create Database Template.

  4. In Template Type page, select:

    • Structure as well as data to include physical data files and structural information in the template. User-defined schemas and data will be included in the template. Databases created from this type of template will be identical to the source database.

    • Structure to include structural information about the source database including tablespace options, initialization parameters, and data files. User-defined schemas and data will not be included in the template.

    Select host credentials. You can select Preferred Credentials, Named Credentials, or Enter Credentials.

    Click Next.

  5. In the Template Options page, specify the Template Name and Description. Specify the template location:

    • Select Store Template in Software Library to specify the Storage Type and Location on the OMS Agent File System or Shared File System.

    • Select Store Template on the Managed Host to store template at ORACLE_HOME/assistants/dbca/templates in the target Oracle home.

    Specify the database file locations. Select:

    • Use Oracle Flexible Architecture to convert the location of files in the template to OFA.

    • Maintain File Location if you want the location of the files in the template to be identical to the source database.

    Click Next.

  6. In the Schedule page, specify the job name and schedule. If you want to run the job immediately, then retain the default selection, that is, One Time (Immediately). If you want to run the job later, then select One Time (Later) and provide time zone, start date, and start time details. You can also select to blackout the database during the template creation process. Click Next.

  7. In the Review page, review the details you have provided for the job and if you are satisfied with the details, then click Submit Job to run the job according to the schedule set. If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.

  8. In the Jobs page, verify that the job has successfully completed and the template has been created as specified.

Note:

You can also use Database Configuration Assistant (DBCA) for creating database templates.

You can edit and customize the database template you create and then upload the customized template to the Software Library. For information about uploading database templates to Software Library manually, see Section 4.3.8.

4.3.8 Uploading Database Templates to Software Library

You can edit and customize your database templates and then upload them to Software Library as follows:

  1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

  2. On the Software Library Home page, select the folder where you want to upload the database template.

  3. From the Actions menu, select Create Entity, then select Component. Alternately, right click the custom folder, and from the menu, select Create Entity, then select Component.

  4. From the Create Entity: Component dialog box, select Database Template and click Continue.

    Cloud Control displays the Create DatabaseTemplate page.

  5. On the Describe page, enter the Name, Description, and Other Attributes that describe the entity.

    Note: The component name must be unique to the parent folder that it resides in. Sometime even when you enter a unique name, it may report a conflict, this is because there could be an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it.

    Click +Add to attach the database template. Select the template as the Source file in the format templatename.dbt or templatename.dbc. Retain the File Name as displayed. Ensure that the file size is less than 2 MB.

    In the Notes field, include information related to the entity like changes being made to the entity or modification history that you want to track.

  6. On the Select Files page, add all the database template related files.

    Select Upload Files to upload all the database template files as follows:

    1. In the Specify Destination section, choose the Software Library location where you want to upload the files.

    2. In the Specify Source section, select the location where you have stored the template files. The location can be your local machine or the agent machine.

    3. Click +Add to upload the database template files.

      For Structure template, again add the templatename.dbt file. In case of Structure And Data template, upload the templatename.dbc, datafiledump.dfb and the controlfile.ctl files. Mark the templatename.dbc file as the Main File.

    Select Refer Files to refer files from an existing referenced file storage location. Select the Referenced File Location and add the source file.

  7. On the Review page, review the details and then click Save and Upload to create the component and upload the binary to Software Library.

4.3.9 Creating Database Provisioning Entities

You can create and store provisioning entities in the Software Library to be used for provisioning Oracle databases. Cloud Control allows you to create the following types of database provisioning entities:

  • Oracle Database Clone

  • Oracle Clusterware Clone

The following subsections explain how to create these provisioning entities:

4.3.9.1 Creating an Oracle Database Clone from a Reference Home

To create an Oracle Database Clone from a reference home, perform the following steps:

  1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

  2. On the Software Library Home page, select any custom folder and create the database clone component.

  3. From the Actions menu, select Create Entity, then select Component. Alternately, right click the custom folder, and from the menu, select Create Entity, then select Component.

  4. From the Create Entity: Component dialog box, select Oracle Database Software Clone and click Continue.

    Cloud Control displays the Create Oracle Database Software Clone page.

  5. On the Describe page, enter the Name, Description, and Other Attributes that describe the entity.

    Note: The component name must be unique to the parent folder that it resides in. Sometime even when you enter a unique name, it may report a conflict, this is because there could be an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it.

    Click +Add to attach files that describe the entity better like readme, collateral, licensing, and so on. Ensure that the file size is less than 2 MB.

    In the Notes field, include information related to the entity like changes being made to the entity or modification history that you want to track.

  6. On the Configure page, from the Create Component from menu, select Reference Oracle Home and do the following:

    1. In the Reference Oracle Home section, click the magnifier icon to select the desired database Oracle home from the list of databases running on the host machine.

      The Oracle Home Location and Host Name fields are populated with the selected values.

    2. In the Oracle Home Credentials section, select the credential type you want to use for accessing the targets you manage. For information about setting credentials, see Section 2.3

    3. In the Working Directory and Files to Exclude section, enter a Working Directory on the host on which you have write permissions, so that the cloned zip file can be created and placed there temporarily.

      The Files to exclude field is pre-populated with certain types of files or patterns that will be excluded from the cloned zip file. However, you can customize this list based on your requirement.

    4. In the Software Library Upload Location section, select a configured storage location from the list where you want to place the database clone software.

      For more information on creating a Software Library Storage Location, see Section 2.2.

  7. On the Review page, review the details and then click Save and Upload to create the component and upload the binary to Software Library.

4.3.9.2 Creating an Oracle Database Clone from an External Storage

To create an Oracle Database Clone from an external storage, perform the following steps:

  1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

  2. On the Software Library Home page, select any custom folder and create the database clone component.

  3. From the Actions menu, select Create Entity, then select Component. Alternately, right click the custom folder, and from the menu, select Create Entity, then select Component.

  4. From the Create Entity: Component dialog box, select Oracle Database Software Clone and click Continue.

    Cloud Control displays the Create Oracle Database Software Clone page.

  5. On the Describe page, enter the Name, Description, and Other Attributes that describe the entity.

    Note: The component name must be unique to the parent folder that it resides in. Sometime even when you enter a unique name, it may report a conflict, this is because there could be an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it.

    Click +Add to attach files that describe the entity better like readme, collateral, licensing, and so on. Ensure that the file size is less than 2 MB.

    In the Notes field, include information related to the entity like changes being made to the entity or modification history that you want to track.

  6. On the Configure page, from the Create Component from menu, select Existing Oracle Home Archive and do the following:

    1. In the Oracle Home Archive section, select a external storage location from where you can refer to the database clone software. From the External Storage Location Name menu, select the location name.

      For more information on configuring external storage locations, see Section 2.2.

      In Oracle Home Archive Location, enter the exact path, which is basically the relative path from the configured location, of the archive file residing on the external storage location. Ensure that the archive file is a valid zip file.

      Note:

      To create the zip file of an Oracle Home, use the following syntax:
      <ZIP  PATH>/zip -r -S -9 -1 <archiveName.zip> <directory or list  of files to be archived> -x <patterns to exclude files>
      
    2. In the Oracle Home Properties section, select the Product, Version, Platform, and RAC Home values, as these configuration properties are particularly useful to search or track an entity.

  7. On the Review page, review the details and then click Save and Upload to create the component and upload the binary to Software Library.

4.3.9.3 Creating an Oracle Clusterware Clone from a Reference Home

To create an Oracle Clusterware Clone from a reference home, perform the following steps:

  1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

  2. On the Software Library Home page, select any custom folder and create the database clone component.

  3. From the Actions menu, select Create Entity, then select Component. Alternately, right click the custom folder, and from the menu, select Create Entity, then select Component.

  4. From the Create Entity: Component dialog box, select Oracle Clusterware Clone and click Continue.

    Cloud Control displays the Create Oracle Clusterware Clone: Describe page.

  5. On the Describe page, enter the Name, Description, and Other Attributes that describe the entity.

    Note: The component name must be unique to the parent folder that it resides in. Sometime even when you enter a unique name, it may report a conflict, this is because there could be an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it.

    Click +Add to attach files that describe the entity better like readme, collateral, licensing, and so on. Ensure that the file size is less than 2 MB.

    In the Notes field, include information related to the entity like changes being made to the entity or modification history that you want to track.

  6. On the Configure page, from the Create Component from menu, select Reference Home and do the following:

    1. In the Reference Oracle Home section, click the magnifier icon to select the desired Oracle Clusterware Oracle home from the list of Clusterware homes running on the host machine.

      The Oracle Home Location and Host fields are populated with the selected values.

    2. In the Oracle Home Credentials section, select the credential type you want to use for accessing the targets you manage. For information about setting credentials, see Section 2.3.

    3. In the Working Directory and Files to Exclude section, enter a Working Directory on the host on which you have write permissions, so that the cloned zip file can be created and placed there temporarily.

      The Files to exclude field is pre-populated with certain types of files or patterns that will be excluded from the cloned zip file. However, you can customize this list based on your requirement.

    4. In the Software Library Upload Location section, select a configured storage location from the list where you want to place the Oracle Clusterware clone software.

      For more information on creating a Software Library Storage Location, see Section 2.2.

  7. On the Review page, review the details and then click Save and Upload to create the component and upload the binary to the Software Library.

4.3.9.4 Creating an Oracle Clusterware Clone from an External Storage

To create an Oracle Clusterware Clone from a external storage location, perform the following steps:

  1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

  2. On the Software Library Home page, select any custom folder and create the database clone component.

  3. From the Actions menu, select Create Entity, then select Component. Alternately, right click the custom folder, and from the menu, select Create Entity, then select Component.

  4. From the Create Entity: Component dialog box, select Oracle Clusterware Clone and click Continue.

    Cloud Control displays the Create Oracle Clusterware Clone: Describe page.

  5. On the Describe page, enter the Name, Description, and Other Attributes that describe the entity.

    Note: The component name must be unique to the parent folder that it resides in. Sometime even when you enter a unique name, it may report a conflict, this is because there could be an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it.

    Click +Add to attach files that describe the entity better like readme, collateral, licensing, and so on. Ensure that the file size is less than 2 MB.

    In the Notes field, include information related to the entity like changes being made to the entity or modification history that you want to track.

  6. On the Configure page, from the Create Component from menu, select Existing Oracle Home Archive and do the following:

    1. In the Oracle Home Archive section, select a external storage location from where you can refer to the Oracle Clusterware clone software. From the External Storage Location Name menu, select the location name.

      For more information on configuring external storage locations, see Section 2.2.

      In Oracle Home Archive Location, enter the exact path, which is basically the relative path from the configured location, to the archive file residing on the external storage location. Ensure that the archive file is a valid zip file.

      Note:

      To create the zip file of an Oracle Home, use the following syntax:
      <ZIP  PATH>/zip -r -S -9 -1 <archiveName.zip> <directory or list  of files to be archived> -x <patterns to exclude files>
      
    2. In the Oracle Home Properties section, select the Product, Version, and Platform values, as these configuration properties are particularly useful to search or track an entity.

  7. On the Review page, review the details and then click Save and Upload to create the component and upload the binary to Software Library.

4.3.10 Downloading Cluster Verification Utility

Cluster Verification Utility (CVU) performs system checks in preparation for installation, patch updates, or other system changes. You can synchronize cluster verification utility (CVU) binaries with Software Library.

Enterprise Manager, by default, provides a routine job that is scheduled daily to download binaries from My Oracle Support if corresponding binaries in the Software Library need to be updated. If your Enterprise Manager deployment is behind a firewall or a DMZ such that the HTTP connection to My Oracle Support is disabled, the routine job will skip its execution. In this case, you can manually download the CVU binaries corresponding to your platform from OTN or My Oracle Support using patch 16766985 as source. You can then synchronize these manually downloaded Cluster Verification Utility (CVU) binaries to Software Library as follows:

  1. From the Enterprise menu, select Provisioning and Patching, then select Database Provisioning.

  2. In the Database Provisioning page, click CVU Setup.

  3. In the Download Cluster Verification Utility page, select one of the following:

    1. Local Machine to select the CVU binaries from your local computer.

    2. Agent Machine to select the CVU binaries from the agent machine.

  4. Click OK. This will update the Software Library with the latest cluster verification utility binaries.