Documentation forDatabase Performance Analyzer

Register an Amazon RDS for Oracle database instance

Complete the following steps to register an individual Amazon RDS for Oracle database instance for monitoring with DPA.

Identify the privileged user

When you register a database instance with the registration wizard, 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 self-managed Amazon RDS for Oracle database instances, the privileged user requires the following privileges:

SYS user

To register an instance without entering the SYS password into DPA, see Register an Amazon RDS Oracle database instance for DPA monitoring with reduced permissions.

Complete the registration wizard

  1. On the DPA homepage, click Register DB Instance for Monitoring.
  2. Under Amazon RDS, click Amazon RDS for Oracle.
  3. Click Next.
  4. Complete the wizard panels as described in the following table.

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.

Panel Instructions
Enter Monitored Database Instance Connection Information

Amazon Relational Database Service (RDS) for Oracle database instances have three connection options:

  • Direct Connect
  • Transparent Network Substrate (TNS) Connect Descriptor
  • Lightweight Directory Access Protocol (LDAP) or TNS Name

Direct Connect

Enter the Service Name or System Identifier (SID), host name or IP address, and port. The default port is 1521.

TNS Connect Descriptor

The Connect Descriptor value contains everything after NAME= in the tnsnames.ora file. The beginning (DESCRIPTION= is necessary. For example:


LDAP or TNS Name

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

After you configure Oracle Name Resolution, you can use the LDAP/TNS Name when registering additional monitored database instances.

RAC instances

For an Oracle RAC (Real Application Cluster), register 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.

DBA user

Enter DBA credentials for DPA to register the database instance.

Enter the Monitoring User

Create or specify the account that DPA will use to gather information. 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, click 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.

To specify an existing account:

  1. Next to Create Monitoring User, click No.
  2. Enter the user name and password.

If you create the user manually, DPA uses the default Tablespaces for that user.

Oracle Monitoring Information

If the monitored instance contains the Oracle E-Business Suite, DPA can 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.

Oracle Repository Tablespace

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

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.

Select the Alert Groups

If you have no Alert Groups set up, or if this new database instance does not match the database type of the Alert Group, the wizard skips this step.

Alert Groups simplify alert configuration and help make alerting more consistent across the monitored database instances.

Select the Alert Groups you want the new database instance to join.

Summary Review the information and click Register Database Instance.
Database Instance Registration Complete Click Finish to return to the DPA homepage.

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.