Stelo Technical Documents

Collecting SQDR Information for Stelo Technical Support

Last Update: 29 December 2022
Product: StarQuest Data Replicator
Version: 3.x
Article ID: SQV00DR009

Abstract

If you experience a problem with the StarQuest Data Replicator, use the following guide to collect diagnostic data to provide to a Stelo Technical Support Engineer. Gathering information prior to contacting Stelo will enable the Technical Support Engineer to resolve the problem in the shortest amount of time possible.

Solution

Compile environment information

Please note the following to report to Stelo Technical Support:

• Windows version and service pack level (e.g., Windows 2019)
• Control database e.g. Db2 version or SQL Server version and service pack level
• SQDR version (from Help | About in the Replicator Manager)
• StarSQL and/or other ODBC driver version (from the Drivers tab of the ODBC Data Source Administrator)
• Source and destination database versions (e.g. DB2 for z/OS 10, Oracle 11g, SQL Server 2019)

Note symptoms and problematic behavior

Try to describe the symptoms of the problem by answering these questions:

• Is the problem related to installation and/or licensing of the software?
• Is there a failure that results in an error message?
• Does one or more systems involved in the replication process hang or become non-responsive?
• Is the data corrupted or not replicated as expected?
• Did the problem being to occur after an upgrade to either the database source, destination, or SQDR system?

Record all error messages from the Replicator Manager

• If the problem results in an error message while creating, modifying or saving a subscription, record the steps to create the error along with the error message.
• If the problem is specific to a replication subscription, view the replication statistics in the Replicator Manager. While in the Replicator Manager, highlight the problematic replication and double-click the replication result in the right pane to view any associated error messages. Copy the error message to send to Stelo Technical Support.

Review the Windows Event Viewer

• View the messages using the Windows Event Viewer found in the Administrative Tools from the Control Panel. Any error messages will most likely be logged as Application messages with the Source name SQDRSVC. Either copy the Event description or save the entire log to send to StarQuest Technical Support. To modify the SQDR service to record an expanded level of warnings in the Event Log, change the service properties as instructed in the SQDR Help topic Service Properties Logging Tab.

Capture an ODBC trace

• ODBC API traces are useful for isolating problems relating to the Replicator Manager and general database access. See Technical Document How to Generate an ODBC Trace with the ODBC Data Source Administrator for more information.

Capture a StarSQL DRDA trace using the DRDA Trace Recorder (for problems with StarSQL only)

• If the SQDR replication uses StarSQL as the ODBC driver for Db2, capture a DRDA Trace to assist StarQuest Technical Support in locating the problem. See Technical Document How to Generate a DRDA Trace with the StarSQL DRDA Trace Recorder.