StarQuest Technical Documents

Collecting SQDR Information for StarQuest Technical Support

Last Update: 07 February 2005
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 StarQuest Technical Support Engineer. Gathering information prior to contacting StarQuest 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 StarQuest Technical Support:

  • Windows version and service pack level (e.g., Windows 2008R2 SP1)
  • 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 2014)

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 StarQuest 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

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

Copy the control database and tables using the WRITEDB.CMD

  • The StarQuest Data Replicator software includes a WRITEDB.CMD utility that uses the SQL Server Bulk Copy Program (BCP) to copy the contents of the Data Replicator control database tables and views to text files. If you encounter a problem while using the Data Replicator, StarQuest Technical Support may ask that you run WRITEDB.CMD to help troubleshoot the problem. See Technical Document SQV00DR003, Transferring SQDR Control Database Information to Text Files for more information.

DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. 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 instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.