Documentation forDatabase Performance Analyzer

Register an Amazon RDS for Oracle database instance

The following sections provide instructions for using a wizard to register an Amazon RDS for Oracle database instance to be monitored by DPA.

Alternatively, you can use mass registration to register multiple database instances, or you can register database instances using scripts that call the DPA API.

For an Oracle RAC (Real Application Cluster), SolarWinds recommends registering every physical instance in the cluster. Do not register the virtual IP that distributes load across the RAC instances.

If you choose to register the virtual IP load balancing listener, or to monitor only a subset of instances in the cluster, DPA will not have complete and consistent data. This will affect DPA's tuning and resource analysis.

For more information, see DPA registration and licensing options for clustered environments.

If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately. After the trial period, you must activate a license to monitor the database instance.

Options for creating the monitoring user

The DPA monitoring user must be created to enable DPA to monitor a database instance. If DPA is not integrated with CyberArk, the following options in the registration wizard determine how the monitoring user and utility package are created or configured.

If DPA is integrated with CyberArk, these options are not displayed. You must create the monitoring user.

Register an Amazon RDS for Oracle database instance and create the monitoring user yourself

Task 1: Create the monitoring user

  1. Copy the following script to a file: CreateMonUserAmazonOracle.sql
  2. Edit the script to update the user name and password values.
  3. Connect to the Amazon RDS for Oracle database, and run the script. To ensure that the connected user has all the privileges needed to create the monitoring user, SolarWinds recommends connecting as master user, which has the DBA role assigned to run the script.

Task 2: Complete the registration wizard

  1. In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
  2. Under Amazon RDS & Aurora, select Amazon RDS for Oracle.
  3. If the monitoring user prompt is displayed, select I will create the monitoring user manually. Then click Next.
  4. Complete the Connection information panel:

    1. Select the connection method, and then complete the fields required for the selected method:

      Connection methodRequired fields
      Direct connect
      • Enter the host name or IP address of the server that hosts the database instance.
      • Verify or update the port used for the connection. The default port is 1521.
      • Specify the SID (System Identifier) or Service name of the database instance.
      TNS connect descriptor

      In the TNS descriptor box, enter everything after NAME= in the tnsnames.ora file. The beginning (DESCRIPTION= is necessary. For example:

      (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = myserver.mycompany.com)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME = myserver)))

      TNS name

      In the TNS name box, enter the SERVICE_NAME value from the tnsnames.ora file.

      To use this option, Oracle Name Resolution must be configured. For instructions, see Connect to Oracle using name resolution.

      LDAP

      In the LDAP box, enter the LDAP distinguished name.

      To use this option, Oracle Name Resolution must be configured. For instructions, see Connect to Oracle using name resolution.

    2. Under SSL mode, specify the type of secure socket layer (SSL) connections established between the instance and the DPA server.

      SSL connections are not available if LDAP is selected as the Connection method.

      SSL modeDescription
      DisableSSL encryption is not used.
      Validate server certificateSSL is enabled. The client verifies that the server is trustworthy by checking the certificate chain up to a trusted certificate authority (CA).
      Validate server certificate and match hostnameSSL is enabled. The client verifies the certificate chain and also verifies that the server hostname matches its certificate's Subject Alternative Name or Common Name (CN).

    3. Enter the user name and password of the monitoring user created previously. Or, if DPA is configured to use CyberArk, enter the CyberArk credentials query for the monitoring user.

    4. Click Next.

      DPA validates the connection information and the privileges of the monitoring user. If the validation is successful, the Instance options pane opens.

  5. Specify the following Instance options.

    The instance name and group membership can be changed after registration.

    1. If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance.

      By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.

    2. If the monitored instance contains the Oracle E-Business Suite, specify whether you want DPA to collect additional information about the suite.

      DPA can capture Oracle E-Business data to identify the screens, modules, and users generating the database requests. This gives you increased visibility into the causes of performance problems in the Oracle E-Business Suite, Oracle Enterprise Resource Planning (ERP), and Oracle Applications environments.

    3. Enter the name that DPA will display to identify this database instance.

      The Display name field defaults to the name retrieved from the database instance.

    4. (Optional) If you have manually created instance groups, you can assign this database instance to one of the groups.

      If no manual groups exist, this option is not shown.

    5. (Optional) If you have existing alert groups, you can assign this database instance to one or more groups.

      If no alert groups exist, or the existing groups do not match this instance's database type, this option is not shown.

    6. Click Next.

  6. Review the information on the Summary page. Click Back if you need to make changes. When the information is correct, click Register.

Register an Amazon RDS for Oracle database instance and let DPA create the monitoring user

Task 1: Identify the privileged user

When you register a database instance using this option, you must provide the credentials of a privileged user. During registration, the privileged user either creates the monitoring user or grants the required privileges to an existing user that you designate as the monitoring user. DPA does not store the credentials of the privileged user. 

For Amazon RDS for Oracle database instances, the privileged user must be assigned the DBA role.

Task 2: Complete the registration wizard

  1. In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
  2. Under Amazon RDS & Aurora, select Amazon RDS for Oracle.
  3. At the monitoring user prompt, select DPA will create/configure the monitoring user. Then click Next.
  4. Enter the following connection information:

    1. Select the connection method, and then complete the fields required for the selected method:

      Connection methodRequired fields
      Direct connect
      • Enter the host name or IP address of the server that hosts the database instance.
      • Verify or update the port used for the connection. The default port is 1521.
      • Specify the SID (System Identifier) or Service name of the database instance.
      TNS connect descriptor

      In the TNS descriptor box, enter everything after NAME= in the tnsnames.ora file. The beginning (DESCRIPTION= is necessary. For example:

      (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = myserver.mycompany.com)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME = myserver)))

      LDAP or TNS name

      In the LDAP/TNS name box, enter the LDAP distinguished name or the SERVICE_NAME value from the tnsnames.ora file.

      To use this option, Oracle Name Resolution must be configured. For instructions, see Connect to Oracle using name resolution.

    2. In the DBA Username and DBA Password fields, enter the name and password of the privileged user you identified previously.

    3. Click Next.

      DPA validates the connection information and the privileges of the privileged user. If the validation is successful, the Monitoring User pane opens.

      If registration fails because your DPA server cannot connect to the instance's server, see DPA database registration failure when attempting to register a database on an external network.

  5. Create or specify the account that DPA will use to gather information (the monitoring user).

    To ensure that the account has the required permissions, SolarWinds recommends creating a new account.

    • To create a new account:

      1. Next to Create Monitoring User, select Yes.
      2. Enter the user name and password.
      3. Select a Tablespace and Temp Tablespace on the monitored database. This is primarily used for gathering Explain Plan data for monitored queries.
      4. Click Next.

    • To specify an existing account:

      1. Next to Create Monitoring User, select No.

      2. Enter the user name and password.

        DPA uses the default Tablespaces for that user.

        DPA ignores data on the monitored database instance from the monitoring user. Make sure the monitoring user will not cause load on the monitored instance.

      3. Click Next to open the Oracle Monitoring Information pane.

  6. On the Oracle Monitoring Information pane, complete the following steps:

    1. Click Yes if the monitored instance contains the Oracle E-Business Suite and you want DPA to collect additional information about the suite.

      DPA can capture Oracle E-Business data to identify the screens, modules, and users generating the database requests. This gives you increased visibility into the causes of performance problems in the Oracle E-Business Suite, Oracle Enterprise Resource Planning (ERP), and Oracle Applications environments.

      The SYS password option is not available for Amazon RDS instances.

    2. Click Next.

      If your repository database is Oracle, the Oracle Repository Tablespace panel opens. If not, continue with step 8.

  7. If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance. Then click Next.

    By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.

    If your repository database is not Oracle, the wizard skips this step.

  8. (Optional) Select the alert groups you want the new database instance to join. Then click Next.

    • If no alert groups exist, or the existing groups do not match the database type of this instance, the wizard skips this step.

    • Group membership can be changed after registration

  9. Review the information, and click Register Database Instance.

  10. When the registration is complete, click Finish to return to the DPA home page.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.