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

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

12 Provisioning Oracle Database Replay Client

This chapter explains how you can provision Oracle Database Replay Client using Oracle Enterprise Manager Cloud Control (Cloud Control). In particular, this chapter covers the following:

12.1 Getting Started

This section helps you get started with this chapter by providing an overview of the steps involved in provisioning Oracle Database Replay Client. Consider this section to be a documentation map to understand the sequence of actions you must perform to successfully provision Oracle Database Replay Client. Click the reference links provided against the steps to reach the relevant sections that provide more information.

Table 12-1 Getting Started with Provisioning Oracle Database Replay Client

Step Description Reference Links

Step 1

Selecting the Use Case

This chapter covers a few use cases for provisioning Oracle Database Replay Client. Select the use case that best matches your requirements.

  • To learn about cloning an existing Oracle Database Replay Client, see Section 12.2.

  • To learn about provisioning Oracle Database Replay Client using a gold image, see Section 12.3.

  • To learn about provisioning a standalone Oracle Database Replay Client, see Section 12.4.

Step 2

Meeting the Prerequisites

Before you run any Deployment Procedure, you must meet the prerequisites, such as setting up of the provisioning environment, applying mandatory patches, and setting up of Oracle Software Library.

  • To learn about the prerequisites for cloning an existing Oracle Database Replay Client, see Section 12.2.1.

  • To learn about the prerequisites for provisioning Oracle Database Replay Client using a gold image, see Section 12.3.1.

  • To learn about the prerequisites for provisioning a standalone Oracle Database Replay Client, see Section 12.4.1.

Step 3

Running the Deployment Procedure

Run the Deployment Procedure to successfully provision Oracle Database Replay Client.

  • To clone an existing Oracle Database Replay Client, follow the steps explained in Section 12.2.2.

  • To provision Oracle Database Replay Client using a gold image, follow the steps explained in Section 12.3.2.

  • To provision a standalone Oracle Database Replay Client, follow the steps explained in Section 12.4.2.


12.2 Cloning a Running Oracle Database Replay Client

This section describes how you can clone an existing Oracle Database Replay Client that is running on a host monitored by Cloud Control.

This option is best suited when you have a running instance of Oracle Database Replay Client that is stable and has all the latest patches applied, and you want to make identical copies of it on multiple hosts. However, the risk involved in using an existing instance is that the instance may be deleted or deinstalled anytime without prior notice, and as a result, the Deployment Procedure may fail. Therefore, use this option when you know that the running instance is available for cloning.

In particular, this section covers the following:

12.2.1 Prerequisites

Before running the Deployment Procedure, meet the following prerequisites:

Prerequisites for Designers

  • Ensure that you meet the prerequisites described in Chapter 2.

  • Compare the configuration of the source and target hosts and ensure that they have the same configuration. If the configurations are different, then contact your system administrator and fix the inconsistencies before running the Deployment Procedure.

    To compare the configuration of the hosts, in Cloud Control, click Targets and then Hosts. On the Hosts page, click the name of the source host to access its Home page, and then from the Host menu, click Configuration and then click Compare.

Prerequisites for Operators

  • If you have PAM/LDAP enabled in your environment, then ensure that the target agents are configured with PAM/LDAP. For more information, see My Oracle Support note 422073.1.

  • Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.

    If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges.

    For example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.

    For information about customization, see Chapter 42.

  • Ensure that the umask value on the target host is 022. To verify this, run the following command:

    $ umask

    Depending on the shell you are using, you can also verify this value in /etc/profile, /etc/bashrc, or /etc/csh.cshrc.

12.2.2 Cloning Procedure

To clone an existing instance of Oracle Database Replay Client, follow these steps:

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

  2. In the Database Procedures page, select the Provision Oracle Database Client Deployment Procedure and click Launch. The Oracle Database Client provisioning wizard is launched.

  3. On the Select Source and Destination page, do the following:

    1. In the Select Source section, select Existing Database Replay Client Installation. Then click the torch icon for Source Host and select the host on which the existing Oracle Database Replay Client is running.

      In the Source Host Details section, by default, Oracle Home, Working Directory, and Files to exclude are prefilled. Oracle Home shows where the existing instance is installed, but this is a non-editable field. For Working Directory, specify the full path to a directory on source host where the files related to cloning can be staged temporarily. For Files to exclude, specify file names that must not be cloned to the source host. Use a comma to separate the file name, and use the wildcard (*) to indicate all files with the same extension. For example, *.trc. Note that any file or folder corresponding to the regular expressions provided here will be excluded.

      In the Source Host Credentials section, select Use Preferred Credentials to use the credentials stored in the Management Repository. Select Override Preferred Credentials to specify other credentials.

    2. In the Specify Destination Host Settings section, click Add and select the target hosts on which you want to clone the existing instance of Oracle Database Replay Client.

      Note:

      On clicking Add, a window appears with a list of suitable hosts. If you do not see your desired host, then select Show All Hosts and click Go to view all other hosts.

      By default, Oracle Base, Oracle Home, and Working Directory are prefilled with sample values. Edit them and specify values that match with your environment and standards. If the directories you specify do not exist on the target hosts, then they will be created by the Deployment Procedure.

      From the Credentials list, retain the default selection, that is, Preferred, so that the preferred credentials stored in the Management Repository can be used. Credentials here refer to operating system credentials.

      Note:

      You can optionally override these preferred credentials. For example, if you have added two destination hosts where the users are A and B, then you can choose to override the preferred credentials with different credentials for each of the hosts. Similarly, if the destinations hosts have the same credentials, which may be different from the preferred credentials, then you can override the preferred credentials with the same credentials for all hosts.

      The credentials you specify here are used by the Deployment Procedure to run the provisioning operation. If this environment is secure and has locked accounts, then make sure that:

      • The credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation.

      • The Deployment Procedures has been customized to support locked environments.

      For more information, see Chapter 42.

      If you have selected multiple hosts, then from the Path list, select Same for all hosts if you want to use the same path across hosts, or select Different for each host if you want to use different paths for each host.

      Note:

      If you select Same for all hosts, then ensure that the Oracle home and the user are present on all the hosts.

      If you want to customize the host settings, then click Customize Host Settings. For example, you can specify the Management Agent home credentials, a name for your installation, or an alternate host name instead of the first host name found on the system.

    3. (Optional) In the Advanced Installation Parameters section, specify any additional parameters you want to run while installing the Oracle Database Replay Client. For example, -force (to override any warnings), -debug (to view more debug information), and -invPtrLoc <Location> (for UNIX only). Ensure that the parameters are separated by white space.

      While installing software binaries from an existing Oracle Database Replay Client location, if you want to also stage them to a shared location, then select Stage to Shared Location and specify a location that is shared across all destination hosts. This staged location can also act as a source for future deployments.

    4. In the Schedule section, schedule the Deployment Procedure to run either immediately or later.

    5. Click Continue.

  4. On the Review page, review the details you have provided for provisioning an Oracle Database Replay Client, and click Submit.

Note:

if the Deployment Procedure fails, then review log files described in Section E.7.

12.3 Provisioning Oracle Database Replay Client Using Gold Image

This section describes how you can provision a gold image of Oracle Database Replay Client from the Software Library.

This option is best suited when you have a copy of a stable, well-tested, and patched Oracle Database Replay Client stored in the Software Library. This option scores over a fresh installation because you save time in patching and testing a fresh instance.

In particular, this section covers the following:

12.3.1 Prerequisites

Before running the Deployment Procedure, meet the following prerequisites:

Prerequisites for Designers

  • Ensure that you meet the prerequisites described in Chapter 2.

  • Ensure that the gold image is available either in the Software Library or in a shared, staging location.

Prerequisites for Operators

  • If you have PAM/LDAP enabled in your environment, then ensure that the target agents are configured with PAM/LDAP. For more information, see My Oracle Support note 422073.1.

  • Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.

    If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges.

    For example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.

    For information about customization, see Chapter 42.

  • Ensure that you use an operating system user that has write permission on the staging areas used for placing software binaries of Oracle Database Replay Client.

    Deployment Procedures allow you to use staging locations for quick file-transfer of binaries and prevent high traffic over the network. While providing a staging location, ensure that the operating system user you use has write permission on those staging locations.

  • Ensure that the umask value on the target host is 022. To verify this, run the following command:

    $ umask

    Depending on the shell you are using, you can also verify this value in /etc/profile, /etc/bashrc, or /etc/csh.cshrc.

12.3.2 Provisioning Procedure

To provision a gold image of Oracle Database Replay Client from the software library, follow these steps:

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

  2. In the Database Procedures page, select the Provision Oracle Database Client Deployment Procedure and click Launch. The Oracle Database Client provisioning wizard is launched.

  3. On the Deployment Procedure Manager page, in the Procedures subtab, from the table, select Oracle Database Replay Client Provisioning. Then click Schedule Deployment.

    Cloud Control displays the Select Source and Destination page of the Deployment Procedure.

  4. On the Select Source and Destination page, do the following:

    1. In the Select Source section, do one of the following:

      If the gold image is stored as a component in the Software Library, then select Software Library. Then, click the torch icon for Component and select the component that has the gold image. Ensure that you select only components that are in "Ready" status.

      Note:

      If you do not see the required component in the Software Library, then follow the workaround described in Appendix E.

      If the gold image was stored as an image in a staging location while provisioning a database in the past, then select External Staging Server and then Gold Image. Click the torch icon for Select Host and select the host where the gold image is stored. Then click the torch icon for Stage Location and select the location on the host where the gold image is available. For Product version, specify the version of the product you are provisioning.

    2. In the Specify Destination Host Settings section, click Add and select the target hosts on which you want to install the gold image of Oracle Database Replay Client.

      Note:

      On clicking Add, a window appears with a list of suitable hosts. If you do not see your desired host, then select Show All Hosts and click Go to view all other hosts.

      By default, Oracle Base, Oracle Home, and Working Directory are prefilled with sample values. Edit them and specify values that match with your environment and standards. If the directories you specify do not exist on the target hosts, then they will be created by the Deployment Procedure.

      From the Credentials list, retain the default selection, that is, Preferred, so that the preferred credentials stored in the Management Repository can be used. Credentials here refer to operating system credentials.

      Note:

      You can optionally override these preferred credentials. For example, if you have added two destination hosts where the users are A and B, then you can choose to override the preferred credentials with different credentials for each of the hosts. Similarly, if the destinations hosts have the same credentials, which may be different from the preferred credentials, then you can override the preferred credentials with the same credentials for all hosts.

      The credentials you specify here are used by the Deployment Procedure to run the provisioning operation. If this environment is secure and has locked accounts, then make sure that:

      • The credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation.

      • The Deployment Procedures has been customized to support locked environments.

      For more information, see Chapter 42.

      If you have selected multiple hosts, then from the Path list, select Same for all hosts if you want to use the same path across hosts, or select Different for each host if you want to use different paths for each host.

      Note:

      If you select Same for all hosts, then ensure that the Oracle home and the user are present on all the hosts.

      If you want to customize the host settings, then click Customize Host Settings. For example, you can specify the Management Agent home credentials, a name for your installation, or an alternate host name instead of the first host name found on the system.

    3. (Optional) In the Advanced Installation Parameters section, specify any additional parameters you want to run while installing the Oracle Database Replay Client. For example, -force (to override any warnings), -debug (to view more debug information), and -invPtrLoc <Location> (for UNIX only). Ensure that the parameters are separated by white space.

      While installing the Oracle Database Replay Client location, if you want to also stage them to a shared location, then select Stage to Shared Location and specify a location that is shared across all destination hosts. This staged location can also act as a source for future deployments.

    4. In the Schedule section, schedule the Deployment Procedure to run either immediately or later.

    5. Click Continue.

  5. On the Review page, review the details you have provided for provisioning an Oracle Database Replay Client, and click Submit.

Note:

if the Deployment Procedure fails, then review log files described in Section E.7.

12.4 Provisioning Oracle Database Replay Client Using Installation Binaries

This section describes how you can provision Oracle Database Replay Client that is identical to the one available on the installation medium.

This option is best suited when you want a completely new installation to be provisioned across multiple hosts. Of course, understandably, this is a fresh installation and you will have to update it with all the latest patches that have been released so far.

Note:

The Oracle Database Replay Client version to be used for replaying workload must be the same version as the version of the test database on which the workload has to be replayed. Oracle Database Replay Client is supported in Oracle Database 10g Release 4 (10.2.0.4) and higher. While you can use archived software binaries for installing Oracle Database Client 11g Release 1 (11.1.0.6) and Oracle Database Client 11g Release 2, for test database versions 10.2.0.4, 10.2.0.5, and 11.1.0.7, you must create a gold image of the respective versions of Oracle Database Replay Client homes and use the same.

In particular, this section covers the following:

12.4.1 Prerequisites

Before running the Deployment Procedure, meet the following prerequisites:

Prerequisites for Designers

  • Ensure that you meet the prerequisites described in Chapter 2.

    Note:

    If you want to create a component for the software binaries of Oracle Database Replay Client, then before you access the Software Library, see My Oracle Support note 815567.1. This note explains the different requirements for each OS platform prior to using the media with Cloud Control Deployment Procedure.

    Note:

    If you want to create a component for the software binaries of Oracle Database Replay Client, do not save the shiphome or component to the Components folder in Software Library. Create a new folder in Software Library and then save the component.
  • Ensure that the installation binaries are downloaded, and archived and uploaded as a component in the Software Library.

  • Compare the configuration of the source and target hosts and ensure that they have the same configuration. If the configurations are different, then contact your system administrator and fix the inconsistencies before running the Deployment Procedure.

    To compare the configuration of the hosts, in Cloud Control, click Targets and then Hosts. On the Hosts page, click the name of the source host to access its Home page, and then from the Host menu, click Configuration and then click Compare.

Prerequisites for Operators

  • If you have PAM/LDAP enabled in your environment, then ensure that the target agents are configured with PAM/LDAP. For more information, see My Oracle Support note 422073.1.

  • Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.

    If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges.

    For example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.

    For information about customization, see Chapter 42.

  • Ensure that the umask value on the target host is 022. To verify this, run the following command:

    $ umask

    Depending on the shell you are using, you can also verify this value in /etc/profile, /etc/bashrc, or /etc/csh.cshrc.

12.4.2 Provisioning Procedure

To provision a fresh Oracle Database Replay Client, follow these steps:

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

  2. In the Database Procedures page, select the Provision Oracle Database Client Deployment Procedure and click Launch. The Oracle Database Replay Client provisioning wizard is launched.

    Cloud Control displays the Select Source and Destination page of the Deployment Procedure.

  3. On the Select Source and Destination page, do the following:

    1. In the Select Source section, do one of the following:

      If the software binaries are stored as a component in the Software Library, then select Software Library. Then, click the torch icon for Component and select the component that has the archived software binaries. Ensure that you select only components that are in "Ready" status. When you select a component from the Software Library, Cloud Control automatically populates the component location.

      Note:

      If you do not see the required component in the Software Library, then follow the workaround described in Appendix E.

      If the software binaries are stored as an archived file in a staging location, then select External Staging Server and then Shiphome. Click the torch icon for Select Host and select the host where the archived file is stored. Then click the torch icon for Stage Location and select the location on the host where the archived file is available. For Product version, specify the version of the product you are provisioning.

    2. In the Specify Destination Host Settings section, click Add and select the target hosts on which you want to install the Oracle Database Replay Client.

      Note:

      On clicking Add, a window appears with a list of suitable hosts. If you do not see your desired host, then select Show All Hosts and click Go to view all other hosts.

      By default, Oracle Base, Oracle Home, and Working Directory are prefilled with sample values. Edit them and specify values that match with your environment and standards. If the directories you specify do not exist on the target hosts, then they will be created by the Deployment Procedure.

      From the Credentials list, retain the default selection, that is, Preferred, so that the preferred credentials stored in the Management Repository can be used. Credentials here refer to operating system credentials.

      Note:

      You can optionally override these preferred credentials. For example, if you have added two destination hosts where the users are A and B, then you can choose to override the preferred credentials with different credentials for each of the hosts. Similarly, if the destinations hosts have the same credentials, which may be different from the preferred credentials, then you can override the preferred credentials with the same credentials for all hosts.

      The credentials you specify here are used by the Deployment Procedure to run the provisioning operation. If this environment is secure and has locked accounts, then make sure that:

      • The credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation.

      • The Deployment Procedures has been customized to support locked environments.

      For more information, see Chapter 42.

      If you have selected multiple hosts, then from the Path list, select Same for all hosts if you want to use the same path across hosts, or select Different for each host if you want to use different paths for each host.

      Note:

      If you select Same for all hosts, then ensure that the Oracle home and the user are present on all the hosts.

      If you want to customize the host settings, then click Customize Host Settings. For example, you can specify the Management Agent home credentials, a name for your installation, or an alternate host name instead of the first host name found on the system.

    3. (Optional) In the Advanced Installation Parameters section, specify any additional parameters you want to run while installing the Oracle Database Replay Client. For example, -force (to override any warnings), -debug (to view more debug information), and -invPtrLoc <Location> (for UNIX only). Ensure that the parameters are separated by white space.

      While installing software binaries from the Software Library, if you want to also stage them to a shared location, then select Stage to Shared Location and specify a location that is shared across all destination hosts. This staged location can also act as a source for future deployments.

    4. In the Schedule section, schedule the Deployment Procedure to run either immediately or later.

    5. Click Continue.

  4. On the Review page, review the details you have provided for provisioning an Oracle Database Replay Client, and click Submit.

Note:

if the Deployment Procedure fails, then review log files described in Section E.7.