Replication Monitoring Center for DB2

DB2 Replication Center

• shipped with and licensed with DB2 UDB Version 8
• includes various features, but its strength is replication set-up
• works with DB2 UDB Version 8 and DB2 DataPropagator Version 8 only

Replication Monitoring Center for DB2

• "as is" software, shipped and licensed serparately from DB2 UDB
• highly optimized for replication monitoring in order to access important information quickly and easily even in large environments with hundreds of databases involved in replication
• has no feature for setting up a replication scenario, but it can be used to perform various operational tasks in existing scenarios
• works with DB2 DataPropagator Versions 5, 6, 7, and 8, also in parallel.

Both software tools support DB2 DataPropagator on the different DB2 plattforms.

Another way is to install the software on a platform supported by an available installation package and transfer the files to your target system. The procedure is described in the Release.html file that is installed with the software.

If you get the message "Database driver ... could not be loaded....", try the following:

• Check how RMC has been started: It cannot be started by double-clicking on the db2rmc.jar file on windows systems because the standard CLASSPATH (and the DB2 JDBC driver package) will not be considered with this method. The same problem appears when RMC is started using "java -jar db2rmc.jar".
• Check your CLASSPATH variable: The CLASSPATH system variable must include the DB2 JDBC driver package. For DB2 UDB Versions 5, 6, 7, and 8, the standard package is <db2path>/java/db2java.zip. If you want to use the DB2 UDB Version 8 JDBC DRDA driver, add the package <db2path>/java/db2jcc.jar to your CLASSPATH.
• When you have no local DB2 UDB Client installed but are using the DB2 JDBC Net Driver (JDBC type 3): Copy to your machine the db2java.zip file of the DB2 JDBC Applet Server installation that you want to access and include it into the CLASSPATH variable.
• When you have no local DB2 UDB Client installed but are using the DB2 JDBC DRDA Driver (JDBC type 4, DB2 UDB Version 8 only): Copy a db2jcc.jar file of a DB2 UDB 8 client to your machine and include it into the CLASSPATH variable.
• Check the JDBC driver settings in the RMC settings dialog: All three types of DB2 JDBC drivers are preconfigured. When you are not sure whether the configuration is correct or not, reset all parameters to the default values (select a parameter, click on right mouse button, press Reset to Default OR stop RMC, delete the properties file, and restart).

When you want to use the Net driver or DRDA driver, you must specify a host name and a port number to which the remote DB2 Service is listening:

• DRDA Driver: Use the DB2 Server port as used for DB2 Client configuration (default port on LUW: 50000; on iSeries and zSeries: 446).
• Net Driver: Use the port of the started DB2 JDBC Applet Server (available only at DB2 UDB LUW, default port: 6789).

You get the message "The database alias name ... could not be found":

The database you want to access is not cataloged at the DB2 client or server to which your JDBC driver is connected. Ensure that the database is cataloged properly. Use DB2 UDB documentation and the DB2 UDB configuration assistants for further information.

You get the message "CLI0616E Error opening socket":

You are using a DB2 JDBC Applet server that's not started at the remote system and the specified port. Start the server at this system using the following command:
db2jstrt <port number>

In order to use this feature, you need a server providing a SMTP mailing interface. The following settings must be reviewed in the application settings:

• alert.mail.sender: e-mail address that appears in the from information of a notification mail. This address is for information only; it can not be used to reach the RMC installation by mail.
• alert.mail.host: Host name or IP address of the SMTP server. This mail server will be used by RMC to send the notification messages. It should provide a SMTP service at port 25.
• alert.mail.recipients: One or more recipient e-mail addresses. Multiple addresses must be separated by blanks. You can dedicate different e-mail formats to individual recipients (for example, when you want to send full notification information to your Lotus Notes® or Microsoft® Outlook address but only a short abstract of alert records to your pager in parallel).

It is mandatory to specify all parameters described above. There are additional settings (alert.mail.*) that can be used to customize notification, such as notification trigger, mail content, and mailing format.

• Limit the maximum of displayed Apply history records in RMC:
1. Start RMC and go to the Settings dialog box.
2. Change the setting General-> Apply-> apply.historyrows to a value greater than 0 (such as 2000).
3. Restart RMC and browse your subscriptions.
• Prune the Apply trail table content manually or using RMC operating tasks.