StarQuest Technical Documents

Quick Start Guide to Using SQDR Plus on Windows (split configuration)(Part 2)

Last Update: 6 February 2015
Product: SQDR Plus
Version: 4.50 or later
Article ID: SQV00PU008-WW

Abstract

This Quick Start Guide describes how to install and configure all of the software you need to perform incremental replication operations using SQDR and SQDR Plus.

This document assumes that you have already performed the steps to prepare the Tier 1 source database system and install and configure the Tier 2 SQDR Plus server. If not, refer to the Part 1 section appropriate for your environment; see Quick Start Guide to Using SQDR Plus. You will need certain information gathered in Part 1; we recommend using the SQDR Plus Configuration Worksheet.

This document assumes that you are configuring a split tier 2/3 implementation, with SQDR Plus and SQDR running on different Windows machines. If you are configuring a different implementation, return to the master index for the SQDR Plus Quick Start Guide and select the appropriate Part 2 document.

General considerations

The same individual or a combination of individuals must be capable of performing in the following three roles in order to successfully complete the evaluation.

• Tier 1 Database Administrator (Db2 Administrator) is someone with administrative authority on the Tier 1 source system.
• Tier 3 Administrator is someone with administrative authority to install SQDR on a Windows computer. This person must also have a set of Db2 user credentials that provide adequate authority to work with the libraries and tables you want to replicate.

The Windows client platform that will run SQDR must have:

• TCP/IP access to the source database host, the destination database, and the SQDR Plus server.
• In a split tier environment, use Regedit to configure TCP KeepAlive Settings.
• Access to Db2 for LUW or Microsoft SQL Server to be used for the SQDR control database. In a combined tier environment, this is typically the Db2 for LUW instance installed with SQDR Plus. In a split tier environment, using SQL Server Express is typically recommended.
• A supported web browser for managing the SQDR Plus server.

 

SQL Server considerations

• When SQL Server is a destination of an incremental group, the collation of the SQL Server database to where data will be replicated should be case-sensitive. Verify the collation for the database by viewing the database properties in the SQL Server Management Studio. A case-sensitive collation will have the characters “CS” appended to the Collation Designator. For example, the collation SQL_Latin1_General_CP1_CS_AS is a case-sensitive collation for U.S. English systems. Refer to the SQL Server Books Online for more information on collation values.

Summary of tasks

Perform the tasks in the order described, noting that some provide information used in subsequent steps. The detailed instructions for each task follow this summary.

1. Db2 Administrator: If the source system is Db2, use StarAdmin (installed with SQDR Plus) to bind SQL packages in the database. This requires knowledge of the database host and sufficient user privilege. Provide database connectivity information to the Client-Platform Administrator to be used when configuring a source.
2. Client-Platform Administrator:
   1. Install ODBC drivers for source and destination databases if necessary, and determine connection strings for the source and destination databases.
   2. License the software.
   3. Run the SQDR configuration, connecting to the Db2 for LUW instance installed with SQDR Plus.
   4. Configure an SQDR incremental replication group and replication subscription.
   5. Review the subscription status.

Step 1: (Db2 Administrator task) Download and Install StarAdmin (Db2 source only)

Estimated Time: 10 minutes

The Windows installer for SQDR Plus includes StarAdmin, which will be used in the next step to bind StarSQL host packages.

 

Step 2: (Db2 Administrator task) Bind Host Packages Using StarAdmin

Estimated Time: 15 minutes

The database connectivity information collected in this section should be provided later to the SQDR Client-Platform Administrator for use in creating ODBC connection strings or data sources.

1. Collect the Db2 host information and fill in the values for your environment in the space provided in the table below.

   Connection Parameter	Description	Your Value
   Host	The network Host Name or IP address of the Db2 server.
   Port	The port number on which Db2 listens for connection requests, as determined during the pre-installation tasks.
   Database Name	The name of the source Db2 database.
   Package Collection	Set this value to SQDR or QGPL	SQDR or QGPL
   Username/Password	A Db2 user account that has authority to create and bind packages in the SQDR collection.

2. Start the StarAdmin application from the SQDR Plus program group on the Tier 2 machine.
3. Enter the database connectivity values in the Connection Settings dialog and click OK.
4. Upon connecting successfully, StarAdmin will immediately bind one package, which will be displayed in the package list. The status bar at the bottom of the dialog will display the Database Name, Package Collection, Db2 Type, and Version. If StarAdmin fails to connect to the database, review the suggested resolutions in the Common Error Messages section of the StarQuest technical document Binding StarSQL Packages Using StarAdmin and make any necessary corrections to the values in the connection dialog.
5. Leave the default values for the Package Settings and Grant Options.
6. From the Command menu, select Bind to create and bind the remaining packages.
7. Once the bind package operation has completed, review the summary dialog. If the packages are created and bound successfully, the summary output will look similar to the following:

Package binding starting: Wed Jul 29 14:44:03 PDT 2009
UID=SUPERUSER
HostName=DB2HOST.DOMAIN.COM
Port=446
Server=DB2PROD
PkgColID=SQDR
AutoTypDefOvr=
BindRules=RUN
CustomizePrdid=No
UseJumboPackages=No
UseEncryption=Any

jdbc:StarSQL_JDBC://DB2HOST.DOMAIN.COM:446/DB2PROD;collection=SQDR

SQL package SWNC0000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWNC0000 to PUBLIC
SQL package SWRU0000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWRU0000 to PUBLIC
SQL package SWRC0000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWRC0000 to PUBLIC
SQL package SWRR0000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWRR0000 to PUBLIC
SQL package SWTS0000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWTS0000 to PUBLIC
SQL package SWNC1000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWNC1000 to PUBLIC
SQL package SWRU1000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWRU1000 to PUBLIC
SQL package SWRC1000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWRC1000 to PUBLIC
SQL package SWRR1000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWRR1000 to PUBLIC
SQL package SWTS1000 in collection SQDR has been created.
Granted execute privileges on SQDR.SWTS1000 to PUBLIC
SQL package QSYS2 in collection SQDR has been created.
Granted execute privileges on SQDR.QSYS2 to PUBLIC

Package binding completed: Wed Jul 29 14:44:55 PDT 2009

If any errors are reported, review the suggested resolutions in the Common Error Messages section of the StarQuest technical document Binding StarSQL Packages Using StarAdmin, correct the problem and execute the bind operation again. If you are unable to resolve the error condition, copy the entire Summary text and send it to StarQuest Customer Support at support@starquest.com.

8. Copy the connection information at the top of the Summary text to the clipboard, as this information will be used in step 4c.
9. Click the Finished button to return to the main dialog.
10. From the File menu, choose Close Database and then Exit.

 

Step 3: Use Db2 for LUW for the SQDR Control Database

SQDR will use the Db2 for LUW instance installed with SQDR Plus; continue to the next step.

If you have not already done so, create a SQL Server database (we recommend using the name ControlDB) and verify that you understand the credentials needed to access the database.

Step 4a: (Tier 3 Administrator task) Install the StarQuest Data Replicator Software

Estimated Time: 10 minutes

The StarQuest Data Replicator software is distributed as a compressed file that you download from the StarQuest Ventures Web site.

1. Log on as an Administrator.
2. Download SQDR using the download link provided by StarQuest Support, unblock the zip file if necessary (right-click and select Properties of the zip file), and uncompress the file into a temporary directory.
3. Run the setup.exe program from the SQDR installer image.
4. Respond to the prompts accordingly to complete the installation.

At the end of the installation, the installer prompts you to start the ODBC Administrator and/or the SQDR Configuration. Select the option to run SQDR Configuration and proceed to the next step.

Step 4b: (Tier 3 Administrator task) License the StarQuest Products

Estimated Time: 5 minutes

StarQuest products require a valid set of licenses for both evaluation and production purposes.

1. Open the StarLicense Configuration utility from Start --> Programs --> StarQuest Data Replicator --> License Configuration.
2. Under the Licenses tab, click the Add button and record the Node ID.
3. Supply the Node ID to StarQuest support, who will generate the necessary licenses.
4. Enter the supplied licenses on the Add dialog. Repeat until all of the license keys have been entered. Depending on the type of deployment, there will 2 to 4 licenses.
5. Restart any running StarQuest services (SQDR, StarPipes, StarLicense Server) or any applications using StarSQL.

Step 4c: (Tier 3 Administrator task) Install ODBC drivers for source and destination

Estimated Time: 5 minutes

You must have ODBC drivers for each source and destination type. In our example below, we will be using StarSQL to access an IBM Db2 for i source; StarSQL is already installed as part of the SQDR installation. For a SQL Server destination, use the latest version of Microsoft ODBC Driver 17 for SQL Server..

Step 4d: (Tier 3 Administrator) Configure the StarQuest Data Replicator Service

Estimated Time: 10 minutes

You must configure the Data Replicator service to create the control database tables.

1. If the SQDR Configuration Wizard is not already running, launch it from the SQDR program group: Start—>Programs—>StarQuest Data Replicator—>Data Replicator Configuration.
2. On the Control Database Logon panel, you can specify whether to use a connection string or an ODBC data source to connect to the SQDR control database. We will be using a connection string.
3. Modify the connection string, changing 127.0.0.1 to the hostname or IP address of the tier 2 system, to connect to the Db2 for LUW database "SQDRC" that was created during installation of SQDR Plus on the tier 2 system. Enter the credentials for the local Windows or Linux user sqdr that was created on the tier 2 system in Part I. Click Next to proceed.



 

4. On the next panel, select the option Create new control tables and click Next.
   
   
   
5. On the next panel, leave the Authorization ID at its default of SQDR and click Next.



 

6. Continue clicking Next, accepting defaults for the remaining panels. Select Automatic as the Service Startup Type and choose the Local System Account as the Log On As user. If you would like to change the Data Replicator service properties, we recommend doing this in Windows Services once the SQDR configuration has been completed. Click Next.
7. Review the configuration summary, choose to start the Data Replicator Service and Manager and click Finish to save the Data Replicator configuration.

 

Step 4e: (Tier 3 Administrator) Start the Data Replicator Manager and Create a Subscription

Estimated Time: 10 minutes

You use the Data Replicator Manager to set up and administer replication operations.

The example below demonstrates creating a replication from IBM Db2 for i (using the StarSQL ODBC driver) to Microsoft SQL Server (using the ODBC 17 Driver for SQL Server). To replicate between other DBMS types, make sure that you have installed an appropriate ODBC driver (the installation of SQDR includes a number of ODBC drivers). Refer to the Using Connection Strings topic of the Data Replicator Manager help file (under Working with Sources) for connection string examples for various DBMS types.

Define a Source

To define the source data that you want to replicate:

1. In the main Data Replicator Manager window, right-click the Sources folder and select the Insert Source command.
2. Create a source using connection strings:
   
   
   1. Select the ODBC Driver radio button.
   2. Select StarSQL (64-bit) from the list of ODBC drivers.
   3. The ODBC driver name will appear in the Source Name field. Be sure to modify this name to clearly identify the database; the name cannot be changed after it is saved. In our example, we are naming it DB2.
   4. Enter a valid connection string (maximum 254 characters). For StarSQL, the connection string will look like
      Server=MYRDB;HostName=myhostip;Port=446;IsolationLevel=2;PkgColID=SQDR;QryBufSz=8192000;
      Note that IsolationLevel=2 is required for a Db2 for i source.
      
   5. Enter a user ID and password that has permission to access that database.

 

3. Click on the Advanced tab.
4. On the Advanced dialog, set the default values for Database and/or Object Schema, as appropriate for your database. These values are necessary for the Copy Member operations.
5. SQDR will automatically detect any available Capture Agent schemas and enable incremental replication. If multiple Capture Agent schemas are detected on the host system, select the desired schema from the drop-down menu.
6. We recommend that you supply a Notification Address (host name or IP address) of the computer that you want to receive a UDP notification when changes are committed to this source. Configuring a notification address will reduce the time it takes for the SQDR client to detect and retrieve source table changes. The drop-down menu lists the IP addresses of all active network connections for the local machine. It is recommended that you use a static IP address rather than a DHCP address.

7. Click OK to create the source.

Define a Destination

Now define the destination that will receive the replicated data.

1. Right-click the Destinations folder and select the Insert Destination command.
2. Create a SQL Server destination using connection strings:
   
3. Select the ODBC Driver radio button.
4. Select ODBC 17 for SQL Server from the list of ODBC drivers (this driver is now recommended rather than the Native Client shown in the screen shot)
5. The ODBC driver name will appear in the Destination name field. Be sure to modify this name to clearly identify the database; the name cannot be changed after it is saved. In our example, we are naming it SQL Server.
6. Enter a valid connection string (maximum 254 characters). For SQL Server, the connection string will look like Server=MYHOST\MYINSTANCE.
   
7. Enter a user ID and password that has permission to access that database.
   

3. Click the Advanced tab.
4. On the Advanced dialog, set the default value for the Database and/or Object Schema, as appropriate for your database. These values will be used by the SQDR subscription wizard to populate configuration fields and during Copy Member operations.

5. Click OK to create the destination.

Create an Incremental Group

In this section you create a group in which to place one or more subscriptions that perform incremental replication operations between the specified source and destination.

1. Right-click the Groups folder and select Insert Incremental Group. In the Group properties dialog, enter a name for the Group and an optional description in the Comment field. The default values for the remaining options are typically suitable for first-time users. To learn more about a particular option, click the Help button in this dialog to launch the SQDR online help topic for this tab.

2. On the Advanced tab, select the Source and Destination that will be used for each incremental replication subscription in this group. Ensure that the Receive Change Data Notifications from Capture Agent option is selected (i.e., checked). Leave the Apply options and Subscription Defaults as their default values and click OK to create the group.

Create a Subscription

The Replicator Manager provides a Subscription Wizard to help you define the specific source data and how you want to replicate it.

1. Right-click the Subscriptions folder beneath the source that you added and select the Insert Subscription command. The Add Subscription Wizard appears.
2. In the Select the Source pane, select Incrementalas the Replication Type and enter a schema or object name if you want to filter the source objects list. Click the Refresh button to display the available source objects in the right pane and select the source object you want to replicate. Click Next to proceed.

3. In the Select a Destination pane, select the destination you added to the Replicator Manager. Review the Destination Options and Replication Options, and click Next to proceed.
   



4. In the Select Group pane select the incremental replication group that you created earlier. Click Next to continue.

5. The Define Criteria pane allows you to specify a SQL WHERE clause in order to horizontally partition the data to be replicated. Enter a valid WHERE clause or leave the field blank. Click the Verify Criteria button to verify access to the table and that the number of rows to be returned are in the expected range. Click Next to continue.
6. The Define Destination Columns pane allows you to review and change the data type mappings for the source and destination objects. If desired, modify the data types of the destination table by selecting one or more columns (use shift-click or control-click to select multiple columns), select Modify Column, make the desired change, and click OK. Click Next.

7. Click Next in the Create Statement pane. The CREATE TABLE statement will not appear until the subscription has been saved.
8. On the Define Processing pane, enter optional host commands to be executed before and/or after the data is replicated. Click Next to continue.
9. On the Indexes/Constraints pane, click Refresh to display any indexes or constraints defined for the source. Select any that you want to replicate to the destination and click Next.
10. Review the default subscription name provided and, if desired, modify. Click Finish to save the subscription.

The subscription is added beneath the Subscriptions folder of the defined source and to the corresponding group.

Step 4f: Review the Subscription Status

Estimated Time: less than 5 minutes

After you define an incremental replication subscription, the Data Replicator runs a baseline snapshot replication that forms the base against which incremental changes are tracked. After the baseline snapshot replication succeeds, the source table is actively monitored by SQDR Plus for changes. This step shows you how to monitor the status of a subscription and a group of incremental subscriptions.

1. Review the status of the subscription by highlighting the subscription in the left pane of the Replicator Manager.

2. Double-click the replication event, indicated by the  icon, to view the statistics of the baseline snapshot. If the data did not replicate successfully, review the error(s) and correct the subscription properties as necessary.

3. Locate the member subscription under Groups, and double-click on the Replication Event to view the status of the subscription.

After the baseline snapshot operation completes successfully the incremental subscription is automatically enabled and actively monitoring for changes at the source.

Continuing Your Software Evaluation

This Quick Start Guide was intended to help you install the StarQuest software and perform a data replication operation as quickly as possible.  Please continue to experiment with the software by adding additional subscriptions, scheduling replication operations, and performing SQL operations on data before and/or after it is replicated. As you experiment with the SQDR software, refer to the product documentation for more information.

• The SQDR Plus Control Center (SQDR Manager) provides an online help system that provides more information about configuring and managing the SQDR Plus Staging Agent.
• The Data Replicator Manager provides an online help system that provides more information about defining and running replication operations. Press F1 or click a Help button from the Data Replicator Manager to display the online help system.

If you encounter any problems while using the evaluation software, please open a support ticket at http://support.starquest.com or call +1 415.669.9619 for assistance.