Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.0 Administrator Guide > Register a database instance for monitoring > Register an Amazon RDS for Oracle database

Register an Amazon RDS for Oracle database

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Sep 15, 2016

Views: 29 Votes: 0 Revisions: 4

To register an Amazon RDS for Oracle database for DPA to monitor:

  1. On the DPA home page, click Register DB Instance for Monitoring.
  2. Under Amazon RDS, click Amazon RDS for Oracle.
  3. Click Next.

Enter 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

Connection options

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

If this is an Oracle Real Application Clusters (RAC) instance, there may be listener configuration changes needed if you are not listening on the physical IP address. SolarWinds recommends:

  • If you are registering pluggable databases (PDBs) on a RAC instance, consider registering with the physical IP address of the host.
  • If you are registering a non-PDB RAC instance, consider registering with the SID.
  • If you are using the Service Name, consider using the physical IP address of the host. Do not use the virtual IP address (VIP) or the Oracle Single Client Access Name (SCAN) IP address.

DBA user

Enter DBA credentials for SolarWinds DPA to register the database instance.

Enter the monitoring user

SolarWinds DPA gathers information through this user from the monitored instance.

You can create a monitoring user through SolarWinds DPA, or use an existing user.

Allow DPA to create the user

SolarWinds recommends this method because SolarWinds DPA requires special permissions that existing users may not have.

  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.

Create the user manually

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

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

Oracle monitoring information

Is the Oracle E-Business Suite enabled?

If the monitored instance contains the Oracle E-Business Suite, SolarWinds DPA can collect additional information about the suite.

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


  1. Confirm the registration information, and click Register Database Instance.
  2. Click Finish to go to the DPA home page, or click Register Another Database Instance to continue registering.
Last modified
14:06, 15 Sep 2016