StarQuest Technical Documents

Installing SQDR Plus for UDB for Multiple Databases

Last Update: 2 October 2008
Product: SQDR Plus for UDB
Version: 3.0 or later
Article ID: SQV00PU004

Abstract

SQDR Plus for UDB provides an easy-to-use solution for replicating data from a DB2 UDB for Linux, UNIX, and Windows database. The SQDR Plus installer is designed for ease-of-use and simplicity when replicating from one DB2 UDB database. This document describes how to install multiple independent copies of SQDR Plus for UDB to monitor the incremental replication of data for multiple DB2 UDB databases that reside on the same host system.

Solution

When you install multiple copies of SQDR Plus for UDB on one host computer, you must specify a different target directory and different port number for each of the databases. Follow the steps below to install multiple copies of SQDR Plus on a Linux, UNIX, or Windows host computer.

  1. Install the first copy of SQDR Plus as documented in the SQDR Plus for UDB User's Guide.
  2. Rename the InstallShield VPD (Vital Product Directory) so that a subsequent installation will appear like a new installation rather than an update. Include the database name in the new name to assist in identifying the installation.

On a Windows host, change the VPD name as shown below:

C:\Program Files\Common Files\InstallShield\Universal\SQDR

to

C:\Program Files\Common Files\InstallShield\Universal\SQDR_database1

On a UNIX host, change the VPD name as shown below:

# cd /root
# mv InstallShield InstallShield_database1

  1. If you are running DB2 UDB on a Windows host, rename the Program Group directory as illustrated below, replacing database1 with the name of the database that this copy of SQDR Plus will monitor:

C:\Documents and Settings\All Users\Start Menu\Programs\SQDR Plus for DB2 UDB

to

C:\Documents and Settings\All Users\Start Menu\Programs\SQDR Plus for DB2 UDB database1

There is no need to stop the service of the first installation, since the new installation will create a new service.

  1. Run the SQDR Plus for UDB installer again. It should start as for a new installation, displaying a dialog "This appears to be a new install." If the dialog reports "Version x.x.x of SQDR Plus for DB2 UDB is already installed on this system," review step 2 to ensure that the VPD was properly renamed.
  2. On the DB2 parameters screen, specify the appropriate database and logon credentials. Use a different DB2 user ID to create a unique copy of the SQDR Plus stored procedures ((SQLLIB\FUNCTION\JAR\user\CAPTURE_PROCS_JAR.jar). (If you do not use different DB2 user IDs for each copy of SQDR Plus, uninstalling one copy will remove the stored procedures used by other copies.)
  3. There is no need to change the directory for database-related configuration because it is uniquely identified with the unique database name (e.g. C:\Documents and Settings\All Users\Application Data\StarQuest\sqdrplus\database). Press Next to continue.
  4. On the SQDR parameters screen, specify a unique port number, such as 50006, for the Capture Agent to use for communicating with this database.
  5. Select whether you want SQDR Plus to manage the log files. Note that if you configure the database for "Allow SQDR to manage logs," the installer updates a single copy of the exit program (db2uext2). This should not affect the existing SQDR Plus instance unless there are significant changes to the exit program in the future.
  6. The service name in the Service Parameters dialog also is based on the unique database name, so there is no need to change it. Press Next to continue.
  7. In the next dialog it is important to change the "Target directory for Java Programs" to another directory, such as

C:\Program Files\StarQuest\sqdrplus_database2

After you install the second copy of SQDR Plus, there should be two services available: SQDRPlus(database1) and SQDRPlus(database2). These services operate independently of each other, and you can start, stop, and pause them as necessary for managing the corresponding database.

If you are running SQDR Plus on a Windows host computer you also will see two program groups. The shortcuts in each program group allow you to work with each copy of SQDR Plus independently. The program group is named SQDR Plus for DB2 UDB unless you modify the name to include the database as suggested in step 3 above.

Operational Considerations

This section addresses additional considerations for upgrading or uninstalling SQDR Plus when you have multiple copies running on a single host computer. These procedures also can be used to work with multiple DB2 instances, setting DB2INSTANCE to the instance you want to affect before running the installer, and with multiple copies of DB2 UDB v9 or later. For easier identification of multiple instances and copies, use database names that are unique throughout the system. If you do use the same database name in different instances or copies, change the name of the directory for the database-related configuration and the Windows service name so they are unique.

Uninstalling SQDR Plus

When you have multiple copies of SQDR Plus for UDB installed on a single host you must separately uninstall each instance of the SQDR Plus Capture Agent. Refer to the SQDR Plus User's Guide for details about uninstalling the software from a UNIX- or Windows-based computer.

Begin by uninstalling the last copy of SQDR Plus that you installed, because that is the installation that the InstallShield VPD is currently set to use. After uninstalling that copy, rename the VPD and uninstall the next copy.

On Windows:

  1. Rename the program group for the most recently-installed copy of SQDR Plus back to the original name, SQDR Plus for DB2 UDB.
  2. Open the Add/Remove Programs control panel. You will see multiple entries for SQDR Plus. Select any of them, and run the uninstall.

To uninstall another copy of SQDR Plus on the same host computer, perform the steps below for each additional instance.

  1. Rename the program group for the next copy of SQDR Plus that you want to uninstall back to the original name of SQDR Plus for DB2 UDB.
  2. Rename the corresponding InstallShield VPD from SQDR_databaseN to SQDR (see step 2 in the "Solution" section).
  3. Run the uninstallation program from the Add/Remove Programs control panel.

On UNIX:

  1. Uninstall the the most recently-installed copy of SQDR Plus by running the uninstall script in its program directory.
  2. For the next copy of SQDR Plus, rename the corresponding InstallShield VPD from SQDR_databaseN to SQDR (see step 2 in the "Solution" section).
  3. Run the uninstall script in the program directory of that copy.

Upgrading SQDR Plus

Follow the steps below to upgrade multiple copies of SQDR Plus for UDB that are installed on the same host computer.

Begin by upgrading the last copy of SQDR Plus that you installed, because that is the installation that the InstallShield VPD is currently set to use.

  1. Rename the program group for the copy of SQDR Plus that you want to upgrade back to the original name, SQDR Plus for DB2 UDB.
  2. Run the installation program to upgrade that copy of SQDR Plus.
  3. Rename the program group with a unique name to make it clear which database that copy of SQDR Plus is monitoring (see step 3 in the "Solution" section).
  4. Rename the InstallShield VPD with a unique name to correspond to this installation (see step 2 in the "Solution" section).

To upgrade another copy SQDR Plus on the same host computer, perform the steps below for each additional instance.

  1. Rename the program group for the copy of SQDR Plus that you want to upgrade back to the original name of SQDR Plus for DB2 UDB.
  2. Rename the corresponding InstallShield VPD from SQDR+databaseN to SQDR.
  3. Run the installation program to upgrade that copy of SQDR Plus.
  4. After the upgrade completes, rename the program group with a unique name that includes the database name to identify which SQDR Plus Capture Agent the commands in that group affect (see step 3 in the "Solutions" section).

DISCLAIMER

The information in technical documents comes without any warranty. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The information in technical documents may be gathered from various sources, including IBM, Microsoft, and other organizations.