Register an Oracle database instance
Complete the following tasks to register an individual Oracle database instance for monitoring with DPA.
- If you are monitoring an Oracle Real Application Cluster (RAC), see Registration and licensing options for clustered environments.
- You can use mass registration to registrations to register multiple database instances, or you can register database instances using scripts that call the DPA API.
Identify the privileged user
When you register a database instance, 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 Oracle database instances, the privileged user requires the following privileges:
Complete the registration wizard
- On the DPA homepage, click Register DB Instance for Monitoring.
- Under Self-Managed, click Oracle.
- Click Next.
- Complete the wizard panels as described in the following table.
|Enter Monitored Database Instance Connection Information||
DPA monitors all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.
Oracle database instances have three connection options:
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
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.
DPA uses the Oracle network configuration
If connection information other than the name has changed, update the
If the name has changed, update the
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.
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:
To specify an existing account:
If you create the user manually, DPA uses the default Tablespaces for that user.
If you are registering multiple Oracle Real Application Clusters (RAC) nodes, you may receive an error that the user already exists. You can create a different monitoring user or clear the Create a New Monitoring User check box and continue.
|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 is requested only if remote login as SYS is enabled on the monitored Oracle instance. This option is not available for Amazon RDS instances.
If you do not have remote SYS access to the computer, click the link to open the Manual Steps for Monitored Database Instance Registration.
You can run a script to run on the monitored instance to install a utility package for DPA that grants Execute permissions for that package to the monitoring user.
To register the monitored database instance manually:
|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.