Register a DB2 database

DPA requires the DB2 instance-wide parameter {DFT_MON_STMT} to be turned on to collect monitoring data. Follow the on-screen instructions to check and set the parameter.

If {DFT_MON_STMT} is set to OFF, you can use DPA to register the database instance. Later, you can set it to ON and restart the database instance during an approved maintenance window. In the meantime, the database shows a status of Idle.

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.

• DPA 9.0 and later monitors all DB2 databases in the specified instance.
• Do you want to monitor a single database in an earlier version of DPA? See Switch to DB2 instance-wide monitoring.
• To monitor a single database, each database must be registered separately through this wizard, even if multiple databases are contained on a single DB2 server instance.
• For instance-wide monitoring, one database must be registered for the DPA connection.

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.

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. Select the Authentication method, and enter the user name and password.

To specify an existing account:

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

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 specified monitoring user. Make sure the monitoring user will not cause load on the monitored instance.

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.

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.