Register a Db2 database instance
Complete the following tasks to register an individual Db2 database instance for monitoring with DPA.
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 Db2 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 DB2 UDB.
- Click Next.
- Complete the wizard panels as described in the following table.
|Db2 Configuration Settings||
DPA requires the Db2 instance-wide parameter
|Enter Monitored Database Instance Connection Information||
Enter the host name or IP address and port of the Db2 server.
Enter the Db2 database for DPA to monitor in the Database field. DPA collects information from all Db2 instances in a cluster configuration for the specified database.
If the connection information changes for the Db2 server, all databases on that instance must be updated separately through the Update Database Instance Connection Wizard.
DPA can monitor all databases in the specified instance, or an individual database.
Enter SYSADM credentials for DPA to monitor the database instance.
Do you want more information on the Db2 permissions needed by DPA for the monitoring user? See Required Db2 permissions needed by DPA for monitoring.
|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:
DPA requires the monitoring user to have SA_ROLE and MON_ROLE privileges for data collection.
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.
|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.