StarQuest Data Replicator Release Notes

StarQuest Data Replicator v5.24 Release Notes

August 2021

Introduction

StarQuest Data Replicator (SQDR) is a replication software product that allows you to copy data between IBM Db2, Oracle, Microsoft SQL Server, MySQL and Informix database environments. You can replicate any table, portion of a table, or view. You can schedule replications to take place at specified intervals or on demand. Replicating data from one database management system to another allows you to:

  • Make the same data available to users of different database systems
  • Make the same data available to multiple sites
  • Balance network and database server loads by making the data available from two or more database servers
  • Create backup copies of data

StarQuest Data Replicator provides:

  • Incremental replication from host databases supported by SQDR Plus.
  • Full refresh replication, which copies all the source data that you specify for replication, regardless of when that data was last replicated. This provides a "snapshot" of the specified source data at the time of replication.

If you will be using SQDR for snapshot replication, refer to the Quick Start Guide for the StarQuest Data Replicator for detailed information about installing StarQuest Data Replicator for the first time. If you will be using SQDR with its companion product SQDR Plus for incremental replication, refer to the SQDR Plus Quick Start Guide.

After you install the software, refer to the online help for information about configuring and using the Data Replicator. Press F1 or click the Help button in a dialog or on the toolbar to display the online help when using the Data Replicator Manager application.

The following topics are addressed in these Release Notes.

  • What's New in this Release
  • Upgrade Considerations
  • System Requirements
  • Installing and Using the StarQuest Data Replicator Software
  • Known Issues
  • Documentation Errata
  • Release History
  • Contacting StarQuest

What's New in this Release

This release of the StarQuest Data Replicator introduces the following new features and improvements:

  • Improved support for automatic handling of source schema changes (e.g. ALTER TABLE ALTER COLUMN of tables on the source). For details, see the ALTER Processing topic (under Creating a Group of Subscriptions) in the SQDR Help file (drmgr.chm).
  • Bug fixes

Upgrade Considerations

VERY IMPORTANT: After upgrading from a version of SQDR Plus prior to 5.10, a harmless "Table Altered" condition will occur for all subscriptions. To resolve this condition, use Data Replicator Manager to either

  • Run the incremental group OR
  • Set the DDL Replication property to AUTOMATIC. This can be done at the group level or at the service level.

Carefully consider the values for the DDL Replication settings before resuming replications after the update. Customers using "archive" subscriptions may want to change the group advanced property to specify "ignore" for dropping columns, as appropriate, to retain historical information. Customers who typically replicate only some subset of columns, and do not want to automatically add new columns may want to specify "ignore" for adding columns. However, most customers will want to use Automatic/Add-Perform/Drop-Perform in order to take advantage of the automatic handling of source schema changes (for source DBMS systems that are supported by SQDR Plus for automatic handling - see the ALTER Processing topic (under Creating a Group of Subscriptions) in the SQDR Help file (drmgr.chm).

Important:Data Replicator Manager v5.10 or later must be used when connecting to an SQDR service running 5.10 or later.

The use of the latest ODBC driver for SQL Server (currently 17.6.1, released July 2020) is required when using SQL Server as a control database, and recommended when using SQL Server as a source or a destination.

Important: CONTROL DATABASE SCHEMA VERSION

SQDR 5.10 introduces Control Database Schema version 5.10; previous versions are 4.90v2, 4.90, 4.50, 4.02. Contact StarQuest Support for assistance/advice if you are updating from SQDR prior to v5.07. We recommend creating a backup of your control database before performing the upgrade.

  • If you are updating from SQDR 5.07 through 5.08, run the Data Replicator Configuration to update your existing control database to the 5.10 format. Select the checkbox to run the Configuration on the final screen of the installation wizard, or select Data Replicator Configuration from the Program Group, and choose "Use an existing control database and tables".
  • If you are updating from SQDR 4.50 through 5.06, upgrade to SQDR 5.08 and run the Data Replicator Configuration to update the control database to 4.90v2 format, and then upgrade to SQDR 5.10 or later and update it to the 5.10 format.
  • If you are updating from SQDR 4.0x or 4.1x, you must first upgrade the control database to 4.50 format, then 4.90v2 format, before updating to the 5.10 format.
  • If you are updating from SQDR 3x,, you must first upgrade the control database to 4.02 format, then 4.50 format, then 4.90v2 format, before updating to the 5.10 format.

Important: If you are upgrading from any version of StarQuest Data Replicator earlier than 4.90, you must run the Data Replicator Configuration to migrate your settings from the registry to the Control database.

Important:After updating from a version prior to 4.90, the service will attempt to connect to every configured Source on startup, and will continue to do so on each service startup until it finally makes contact with that Source. If your SQDR configuration contains Sources that are either temporarily or permanently inaccessible, there will be a noticeable delay at startup. You can reduce this delay by changing the Login Timeout value on the Connection Pools panel of Service Properties from the default of 30 seconds to a lower value. However, it is preferable to ensure that all sources are accessible at least once during SQDR service startup, or remove unused Sources.

Db2 LUW 11.5.5 is now recommended for staging databases. If you are currently using SQDR with an earlier version of Db2 (10.5, 11.1, 11.5.0, or 11.5.4), you can continue to use the earlier version of Db2, but we recommend updating to Db2 11.5.5 at your earliest convenience.

System Requirements

You can install and run the StarQuest Data Replicator on:

  • Windows Server Server 2012R2, Server 2016, Server 2019
  • Windows 8.1 or 10 64-bit (not recommended for production usage)

If you are currently running a 32-bit version of SQDR on a 64-bit operating system, we recommend upgrading to a 64-bit version of SQDR. See Upgrading to 64-bit SQDR for upgrade instructions or contact StarQuest Support.

We recommend installing the latest Windows updates. For Windows Server 2012R2 and windows 8.1, the  April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) is required.

A minimum screen resolution of 1024 x 768 is recommended when using Data Replicator Manager.

SQDR requires Visual C++ 2017/2019 runtimes. The SQDR installer will install the Microsoft-supplied Microsoft Visual C++ 2017/2019 Redistributable package if it is not already present on the system. The Microsoft Redistributable package will remain on the system if SQDR is upgraded or uninstalled.

SQDR requires the Universal C Runtime (KB2999226), which is a Windows operating system component typically installed by Windows Update on systems earlier than Windows 10; it can also be downloaded from Update for Universal C Runtime in Windows. If not already present, this component is installed by the SQDR installer as part of the Visual Studio 2017 redistributables. The error api-ms-win-crt-convert-I1-1-0.dll is missing will result if KB2999226 has not been installed.

The following command will display whether KB2999226 has been installed:

C> wmic qfe list brief /format:texttablewsys | findstr KB2999226

The SQDR Service Properties utility requires .NET Framework 4.6 or later.

The Data Replicator requires a control database in which to store definitions for sources, destinations, and subscriptions. If you are using SQDR Plus to support incremental replication, we recommend using the instance of Db2 LUW installed with SQDR Plus. Otherwise, you can use any of the following versions of IBM Db2 for Linux, Unix Windows (LUW) or Microsoft SQL Server for the SQDR control database. You can obtain DB2 Community Edition free of charge from IBM. Similarly, you can obtain the Microsoft SQL Server Express free of charge from http://www.microsoft.com/downloads to use as a control database for the Data Replicator.

  • IBM Db2 for LUW 11.5.5 (existing deployments using older versions of Db2 will continue to function)
  • SQL Server 2008/2008R2/2012/2014/2016/2017/2019, including Express Edition (2008R2sp1 or later recommended)

The control database can be either local or remote. For a remote database, install the appropriate ODBC driver:

  • For Db2 for LUW control database: StarQuest StarSQL (included in the SQDR installer)
  • For SQL Server control database: Microsoft ODBC Driver 17

You can replicate data to and from any of the following database systems:

  • Db2 for i (formerly known as DB2/400, DB2 UDB for iSeries, and DB2 for i5/OS) running OS/400 V5R4 and later
  • Db2 for Linux, UNIX, and Windows (DB2 LUW) v9.7 and later
  • Db2 for z/OS v8.1 and later
  • SQL Server 2019, 2017, 2016, 2014, 2012, 2008R2, 2008, 2005
  • Oracle 10g or later
  • Kognitio WX2 7.1 or later
  • MySQL 4.1 or later
  • MariaDB
  • Amazon Aurora
  • Apache Derby (JavaDB) 10.3 or later
  • TmaxSoft Tibero 6 or later
  • PostgreSQL
  • EDB Postgres Advanced Server
  • Actian (Pervasive) PSQL
  • Amazon Redshift
  • Salesforce
  • Snowflake
  • Exasol
  • CSV/text files, using the SQDR Text Driver
  • Informix: any version of Informix supported by v4.10FC6X2, FC7, or later of the IBM Informix ODBC driver:

For incremental replication, SQDR Plus must be configured for the host database system.

Access to Db2 databases requires the StarSQL ODBC/DRDA driver (v6.2 or later recommended and included as part of the SQDR installation), the IBM Db2 Connect driver, or the IBM i Access Client Solutions or i Access for Windows driver (for access to data sources on Db2 for i).

If you use IBM i Access for Windows for accessing a Db2 for i database, install iAccess 7.1 (5770-XE1) with the SI64724 (June 2017) or later service pack. If you use IBM i Access Client Solutions (5733XJ1), the Windows Application Package must be at the June 2017 level or later.

For access to SQL Server, use the ODBC Driver 17.x for SQL Server. We recommend using the latest ODBC Driver 17.x (currently 17.7.2).

Access to Apache Derby (JavaDB) requires StarSQL 6.20 or later.

PostgreSQL considerations:

When using the psqlODBC driver for PostgreSQL as a destination, we recommend configuring the Advanced panel as follows. See the Help file for a sample DSN-less connection string. We recommend using v10.1 or later of the psqlODBC driver; do not use v9.06.0500.

  • Max Varchar Size: 32767
  • Max Long Varchar Size: 214748364 (2GB)

When using the SQDR bundled ODBC driver for PostgreSQL as a destination, we recommend configuring the Advanced panel as follows. See the Help file for a sample DSN-less connection string.

  • Enable the checkbox for Fetch TSWTZ as Timestamp (the default is to treat this type as CHAR(27))
  • Max char Size: 255
  • Max Varchar Size: 32767
  • Max Long Varchar Size: 214748364 (2GB)
  • Extended Options: enter BatchMechanism=2

Oracle considerations:

  • Access to Oracle databases requires one of the following ODBC drivers:
    • SQDR bundled ODBC driver for Oracle (recommended)
    • Oracle Instant Client ( 12.1.0.2 or later)
    • Full Oracle Client
    • Progress DataDirect Connect or Connect64 for ODBC (Oracle Database Wire Protocol Driver)
  • When using an ODBC data source for the SQDR bundled ODBC driver for Oracle, supply the string ColumnSizeAsCharacter=1; ColumnsAsChar=1 in the Extended Options field on the Advanced panel.
  • When using Oracle as a source or destination, we recommend setting the system environment variable NLS_LANG in the system control panel to ensure proper character translation of character data to the local ANSI page of the SQDR system. For example, if you are using a US English Windows system, set NLS_LANG to AMERICAN_AMERICA.WE8MSWIN1252. This is especially important if you disable the Bind Character types as Wide (Unicode) option in the SQDR service properties dialog.

For more information about the NLS_LANG environment variable, see:
Oracle 11g Appendix C Configuring Oracle Database Globalization Support
Oracle 12c Appendix C Configuring Oracle Database Globalization Support

MySQL considerations:

  • We recommend using Connector/ODBC 5.1.8 or later; do not use Connector/ODBC 5.1.6. You can also use the MariaDB ODBC driver. You can use the SQDR bundled ODBC driver or DataDirect Connect for ODBC if you are using MySQL Enterprise.
  • We recommend using the Unicode (w) version rather than the ANSI (a) version of the MySQL ODBC driver when SQDR is configured for Bind Character Types as Wide (Unicode), which is the default.
  • If MySQL is the destination for an incremental subscription, specify the option Return matched rows instead of affected rows in the Cursors/Results panel of the MySQL ODBC configuration or specify FOUND_ROWS=1 in a connection string. This is particularly important if the MySQL database is configured as case-insensitive and the source database is not.
  • Enable Prepare statements on the client in the Details/Misc panel of the MySQL ODBC configuration or specify NO_SSPS=1 in a connection string to avoid an error condition in which the server exhausts its prepared statement limit.

  Informix considerations:

  • You can use the the SQDR bundled ODBC driver, IBM Informix ODBC driver (CSDK) v4.10FC7 or later, the IBM Db2 ODBC driver, or the DataDirect Connect for ODBC driver to connect to Informix. Some drivers may have limitations; for example, the IBM Db2 ODBC driver cannot handle variable UDT (CLOB) fields.

Salesforce considerations:

  • Set Transaction Mode=1-Ignore on the Advanced Panel.

Snowflake considerations

  • Issue the following command for the user being used by SQDR for the Snowflake source or destination:

alter user myuser set TIMESTAMP_TYPE_MAPPING = 'TIMESTAMP_LTZ'

  • Snowflake does not support INDEX create/drop, but does support primary key/unique index constraints.

In addition, you can use the Data Replicator with other databases if they can be accessed through an ODBC driver that complies with Level 2 of the ODBC 3.51 specification.

Installing and Using the StarQuest Data Replicator Software

  • If you will be using SQDR with its companion product SQDR Plus for incremental replication, refer to the appropriate SQDR Plus Quick Start Guide at https://docs.starquest.com/Supportdocs/browseQuickStarts.shtml. The SQDR Plus guides include instructions for installing both SQDR and SQDR Plus.
  • If you will be using SQDR for snapshot replication, refer to the Quick Start Guide for the StarQuest Data Replicator for detailed information about installing StarQuest Data Replicator for the first time.
  • After you install the software, refer to the online help for information about configuring and using Data Replicator. Press F1 or click the Help button in a dialog or on the toolbar to display the online help when using the Data Replicator Manager application.
  • Browse the StarQuest Data Replicator technical documents at https://docs.starquest.com/Supportdocs/techSQDR/browseSQDR.shtml for specialized information, such as using the StarQuest Data Replicator in a particular environment or to accomplish a special task.
  • Refer to the technical document Troubleshooting SQDR Installation and Setup Issues for resolving problems that may be occur when installing SQDR or performing initial setup tasks..

Known Issues

MySQL Considerations

Indexes and primary keys on a MySQL source table may appear incorrectly in the subscription wizard; verify that only valid indexes are selected for replication purposes.

Precision Limitation for Oracle CHAR and RAW Column Types

The Oracle ODBC driver driver has a limitation that affects replicating from SQL Server or Db2 columns to an Oracle column of data type CHAR or RAW. Although the Oracle CHAR and RAW data types allow larger values, you must set the precision for the destination column that uses these types to 255 or less. If the source column precision is greater than 255, you can avoid data truncation by changing the destination column to a data type that allows a larger precision value. For character data, change the Oracle destination column data type to VARCHAR or LONG. For binary data, change the data type to LONG RAW.

Oracle Destination (Oracle driver) and Use Unicode Intermediates disables Mutirow Row Fetch and Insert:

If the destination is an Oracle database (using the Oracle ODBC driver) and the SQDR service is configured with Use Unicode Intermediates, the setting for Multirow Fetch and Insert is ignored, and the message "useUnicodeIntermediates disables MultiRow option for replication to Oracle destination" will appear in the replication statistics. Solution: use the SQDR bundled driver or DataDirect driver for Oracle.

Oracle destination limited to only one unsizable LONG mapping

If the destination is an Oracle database, you can replicate only one column that contains an unsizable LONG mapping; this is an Oracle limitation. If your source table contains more than one such column (e.g.multiple columns that map to BLOB or CLOB datatypes), you will need to choose which column to replicate and remove the other columns from the subscription.

Oracle Object Types are not supported
Oracle Object Types (also known as Abstract Data Types (ADT) or user-defined types) are complex compound structures that are not supported using ODBC and thus cannot be replicated by SQDR. You can replicate other data contained in tables with Object Type columns by deleting those columns in the Subscription Wizard.

Incremental Replication of Oracle LOB columns
There is a known issue when performing incremental replication of LOB columns from an Oracle source. When updating the contents of length of a LOB column that is greater than 4000 bytes, you must also update another column of the same row.

BCP error when replicating to SQL Server

Replication to SQL Server may fail in certain situations, such as when there is at least one LOB column n the source table and more than one ''image" column in the target table. You can work around this problem by specifying "Insert using ODBC" rather than BCP in the destination options of the subscription.

Replicating XML columns to and from Db2 for i (iSeries) and Db2 for LUW

When replicating tables containing XML columns to Db2 for i and Db2 for LUW destinations, the following limitations apply:

  • XML support was introduced to the iSeries in IBM i 7.1. When replicating XML data to IBM i 6.1 or earlier, XML columns will be mapped to CLOB.
  • If you are using IBM iAccess driver to access Db2 for i, use the May 2014 fixpak (SI53584) or later. In addition, if you are retrieving XML data from Db2 for i with iAccess, use the ODBC.INI
    keyword XMLDeclarationFormat or the connection string keyword XMLDECLARATION and specify a value of 0 or 2.
  • If you are using StarSQL 6.19 or later as the destination driver to Db2 for i, and inserting NULL-valued XML data, install PTF SI52427(i 7.1) or SI52430 (i 6.1). This PTF is included in the June 2014 DB2 group PTF.

Replicating NULL-valued XML columns to Db2 for LUW with StarSQL

If you are using StarSQL 6.19 or later to connect to a Db2 for LUW destination and inserting NULL-valued XML data, you will need the fix for one of the following APARS, included in the listed fixpak:

  • DB2 9.7: APAR IC99936 FP10
  • DB2 10.1: APAR IT00342 FP5
  • DB2 10.5: APAR IT00343 FP4

Memory usage of Service increases when communicating with Manager

Leaving the Data Replicator Manager running for extended periods of time could cause a memory management problem in the Replicator Service. To avoid this, we recommend running the Replicator Manager only when you need to configure the service or subscriptions or monitor the replication operations. In addition, the Replication Manager will automatically exit after running for twelve hours.

Saving Subscriptions to AS/400 Member Files

If you encounter a subscription validation error while saving a new subscription that will replicate to a member of a physical file on an AS/400, you may need to cancel the subscription wizard and completely redefine the subscription in order to specify a member for the destination file.

Columns with a DEFAULT value

If the source table has columns that are defined with a DEFAULT value, that information is not preserved when the destination table is created using SQDR.

Solutions:

  • Execute an "ALTER TABLE" SQL statement after creating the table (e.g. as a Post-processing step):
  • e.g. ALTER TABLE MYTABLE ALTER COLUMN LOG_DATE SET WITH DEFAULT 'CURRENT TIMESTAMP'

or

  • Copy the CREATE TABLE DDL statement as defined on the source system, execute it in an ad-hoc fasion on the destination system, and configure the SQDR destination as "Use Existing Table"

Config: Control database naming

Do not use a hyphen when naming a SQL Server control database; an ODBC syntax error: "Incorrect syntax near 'Control-DB'" will result when sqdrconf attempts to create the control database.

SQDR Service fails to start

If the SQDR Service fails to start with the error "The service did not respond to the start or control request in a timely fashion.", be sure that the user specified to run the service is authorized to use DCOM. On Windows Server 2008, this can be accomplished by adding the user to the group Distributed COM Users.

MySQL: table not found error

If the name of a MySQL source table contains a period, the table will appear in the list of available source tables, but selecting it for replication will result in a "table not found" error. Either rename the table or create a view over the table and choose the view for replication.

Kognitio WX2 Issues

  • The maximum length for a VARCHAR column should be 7899 rather than 7900. Also, if you have large VARCHAR columns in your source table, edit the column mapping for each subscription individually to make sure that it is set correctly.
  • SQDR reports the creation of an index as sucessful when, in fact, no index is created.
  • You may receive a misleading "table exists" message when creating a table.
  • Certain character data may result in the error "SQLSTATE S1000, native error 1195573780, [Kognitio][WX2 Driver][wx2] CG0214: Invalid string representation"
  • When WX2 is used as a source, views are not supported.

Documentation Errata

Release History

This section provides information about problems or enhancements that are made available as "point releases" and major releases of the StarQuest Data Replicator software.

Version Number Release Date Significant Changes
v5.24.0826 Aug 2021 15089 - Text driver: Improve performance of Delete All Rows
15389 - SQDR_ODBC: 8.0.1.44
15391 - Error constructiong verify statement if Oracle or SQL Server has column with "SELECT" in the name.
15392 - force use of ANSI quotes if using MariaDB ODBC Driver
15394 - Incorporate SQL statement into ir_keylog
15395 - Sequenced Apply & GetChanges
15406 - Update VS2019 redist to 14.29.30040.0
15408 - Insure sequence comparison is transitive
15431 - Avoid locked group after abnormal member condition (error; warn, etc.) or stop
15448 - Padding of SQL_VARCHAR controlled by new service property padVarchar
15450 - Handle long (>8k) Create Statement when converting a subscription
v5.23.0710 Jul 2021 15310 - Issues with configuring MySQL ODBC driver
15352 - Implement Apply sequenced DML
15333 - SQDR_ODBC 8.0.1.43
15347 - SQDR_ODBC: update SQDR MySQL ODBC to 8.0.2
15356 - SQDR_ODBC: rpcurl28.dll
15357 - Apply runtime_error
15358 - Log error in eventlog if source notification enabled and invalid interface specified
15385 - revise handling of Halt on Flagged condition
v5.22.0413 Apr 2021 15120 - Replicator should insure max number of rows <= 32k
15146 - Assertion Failed: RC.second File: sqdatareplicator.cpp line: 5808
15156 - Return FALSE if source_id not found
15160 - protect against misreported source length of derived column when inflating char->varchar
15163 - enhance column scripts to allow for staging derived column expression
15169 - allocate wide character as even number of bytes
15170 - Eliminate compiler warnings
15171 - Help: modernize terminology
15176 - Installer: VS2019 redistrib 14.28.29325.2
15178 - Require/Provide before image data if soft-delete and "use upsert" specified
15182 - Certify EnterpriseDB DBMS support
15190 - SQDR_ODBC 8.0.1.38
15196 - switch to "closed window" state *after* sucessful create of the primary key/unique index
15216 - MySQL destination - Native Loader failure
15228 - Catch and notify unhandled exceptions in Apply
15230 - Avoiding warning in replication about truncation of unused ROWID column
15239 - padding should not be attempted with CLOB
15240 - Update VC2019 redistributables to 4.28.29913.0
15250 - [SQDR Manager] Group stopped with error '[Microsoft][ODBC Driver Manager] Invalid string or buffer length' after subscription is synchronizing the baseline
15253 - SQDR_ODBC: installer - replace HTML help with PDF files
15256 - SQDR_ODBC 8.0.1.40
15259 - [SQDR Manager/ Import mapping script] txt file is not shown under the Text Files (*.txt) file dialog
15271 - SQDR_ODBC installer: adjust product code in PRQ
15278 - Insure MySQL accepts ANSI_QUOTE character
v5.21.1203 Dec 2020 15046 - Provide finer detail on failure to load dll error message
15056 - Refactor minidump support
15059 - Improve binding of numeric imprecise types (float, real, double)
15066 - Conditional apply of before image if using "archive" subscription
15070 - Column truncated message missing column name
15087 - Provide option to "pause" group if DML results in flagged row
15099 - Incremental group logging "Keys-always" issue
15103 - when mapping numeric/decimal to varchar, use column display size, not precision
15111 - cdcAuditUseTarget should be boolean
15129 - SQDR_ODBC 8.0.1.35
v5.20.0921 Sep 2020 14956 - Exasol: ODBC TIMESTAMP should report as (23,3)
14957 - Column mapping exact matching logic too stringent when source is "identity..."
14810 - React to new gen staging table for ALTER COLUMN size
14963 - Installer: VS2019 redistrib 14.27.29016.0
14976 - Incorporate Alter Column logic into DDL processing
14987 - Tighten apply column change processing - provide improved feedback on DDL processing
14996 - SQDR_ODBC 8.0.1.30
15010 - Multi Member checkbox deselected after enabled
15017 - Use QSYS2.QCMDEXC rather than QSYS.QCMDEXC
15029 - Enable "fast save" - bypass validation on destination
15030 - Derived column expression should not be excluded for "B" image data
15031 - Column name mapping for use existing should be case insensitive
15033 - provide system property to minimize subscription validation
v5.19.0727 Jul 2020 14924 - [SQDR Help/Subscription Column Properties] document 'Create target unique index using source table RRN' option
14935 - Deprecate replicate DDL only option
14939 - Enable connection pooling for StarSQL
14940 - Improve performance of SetSubscription when dealing with large source tables
14942 - Partition Key "nullabiliity" check too restrictive
14948 - SQDR_ODBC 8.0.1.27
14950 - [SQDR Manager] The app displayed 'Failed to launch help' when trying to open help in Source Object Filter screen
StarSQL 6.41.0707
v5.18.0621 Jun 2020 13625 - RS Error - Deleting Destination - time out trying to acquire exclusive lock
13457 - Provide option to disable automatic identifier case folding
14761 - Upgrade from pre-V5.08 overwrites service properties with defaults
14844 - Add Group property to enable/disable index
14845 - Add Group Property to control use of checkpoint restart for both types of groups (IR &SS)
14852 - SQDRInfo: crash on cancel of initial popup; add Exit button
14858 - Kafka Producer needs to handle complex connection strings
14867 - Replicate FK group option not properly initialized when creating a new group
14875 - Flush (delete) staging connections when pausing source or target
14876 - Provide more granular detail when encountering "ODBC message: SQLSTATE 22001"
14890 - Automatically shift to "mixed case" if source DBMS does not use UPPERCASE default
14806 - SQDR_ODBC 8.0.1.25: add rptls28; put rptrc28 in system32; fix PRQ
14871 - Initialization of Incremental Support Failed - Manager will not start
14921 - Extra digits when replicating "large" precision values from Oracle NUMBER type
v5.17.0417 Apr 2020 14835 - Permit long wait for multithreaded fetch
14836 - Permit specification of minimum number of buffers to allocation
14840 - Add Exasol as certified DBMS
14842 - Use "Delete" when partition key is in effect instead of "Truncate"
v5.16.0401 Apr 2020 14691 - Add support for Text ODBC Drivers
14795 - SQDR Installer: update from 5.08 does not update drmgr and related
14368 - Change "use existing" to offer to create destination if doesn't exist at sub save
14808 - Archive subscription should not create any IR index, since only inserts are performed
14817 - Expand logging of scheduled events
StarSQL 6.41.0331
SQDR_ODBC 8.0.1.22
v5.15.0309 Mar 2020 14786 - Installer: update vs2017/2019 runtime to 14.24.28127
14789 - build with VS2019
StarSQL 6.40.0309
SQDR_ODBC 8.0.1.21
v5.14.0220 Feb 2020 14341 - email notification: SMTP authentication issues with Office365
14721 - SQDR_ODBC: remove v7 drivers for Oracle, SQL Server, Hive
14776 - MSSQL ControlDB 5.10 upgrade issue
14782 - drmgr installer: "error reading setup initialization file" in rare cases
SQDR_ODBC 8.0.1.20
v5.12.1209 Dec 2019 14584 - Group properties/Advanced tab - left justify the top paragraph of text to match up with boxes below
14598 - Redshift: enable truncate option
14673 - Certify Snowflake as valid Destination DB
14712 - Remote drmgr fails on win10 1903 & 1909
14713 - Align all controls on Group Advanced page
14717 - SQDRInfo: build with ChilkatDotNet46.dll
14722 - Use a Multi-value insert for Redshift if "bulk load" is specified
14723 - SQDR_ODBC 8.0.1.18
14736 - Do not flag as mismatched key if subscription uses RRN and alter is processed
v5.11.1115 Nov 2019 14639 - Include Before Image in AfterImage (updated)
14657 - Support MariaDB ODBC driver
14675 - Log DDL of subscription
14692 - Add service property for ODBC Connection Attribute "Packet Size"
14696 - SQDR_ODBC 8.0.1.17
14697 - Implement MySQL Bulk Loader based upon multiple value INSERT
14698 - Avoid deadlock if modifying an active I/R Group's properties
14699 - Add BatchMechanism=2 for SQDR_POSTGRESQL destinations
14703 - Installer: update vs2017 runtime to latest 14.23.27820.0
v5.10.1007 Oct 2019 14510 - Oracle Source - @null and @SEQ derived column macros
14561 - Support source table alter without requiring new baseline
14574 - Remove change data notification enabled from Group Advance Page
14575 - Upgrade controlDB version to 5.10
14577 - Installer: changes for SQDR 5.10 (registry, new files)
14591 - Improved handling of thread wait
14609 - Informix: @TX macro results in invalid syntax while validating subscription
14611 - Enhance Ddl Replication Options
14620 - Enlarge replication statistic dialog
14621 - Expand size of Column Properties Dialog
14622 - Handle DBMS Specific requirements for ALTER processing
14639 - Include Before Image in AfterImage
14658 - ALTER processing/ DROP: IGNORE - The replication is failed when dropping a column in Source table (SQ-43)
14659 - MySQL Destination/Alter processing/Drop:Ignore] The system attempts wrong SQL syntax to alter the column to permit null values (SQ-48)
14664 - SqdrConf: "Use integrated security" is checked even if not configured to use
14665 - Make system default DDL manual(ignore,ignore)
14680 - SQDR_ODBC: 8.0.1.16
v5.07.0327 Mar 2019 14539 - Refactor Key Processing in Apply
14545 - datetime->varchar2(23) results in string truncation error
14547 - Handle inflation of timestamp to large destination
14549 - Issue processing insert into iSer to Oracle sub (CLOB to LONG)
14550 - Detect LOB truncation in Apply
14551 - Oracle destination: Drop associated index if constructing drop primary key SQL
14555 - Editing existing SQL Server source may result in bogus error message
14556 - Use reference to object, not copy, when analyzing imported data types for derived columns
14558 - SQL Server CT Agent with "use existing "must force "relaxed apply"
v5.06.0302 Mar 2019 14519 - Expose foreign keys as group/subscription replication choice for IR Groups/Subscriptions
14535 - Expand displayed length of SQL_DOUBLE to 23 with precision 17
14537 - Mutable keys may result in extra rows after touchup of baseline
v5.05.0214 Feb 2019 14523 - Enhance Insert processing to incorporate new "M" vector
14527 - Oracle: Sub flagged when update statement is missing columns
14528 - Handle subscription that specifies Upsert that includes a clob
SQDR_ODBC 8.0.1.10
v5.04.0128 Jan 2019 14488 - Enhance Derived Columns to specify staging DBMS derivation rules
14490 - New builtin macro @null for derived column definitions
14501 - New @skip macro
14505 - Expose fetch error if present and using multithreaded baseline
14509 - Don't use Upsert if compression in effect
v5.03.1307 Jan 2019 14419 - Informix & IBM Informix driver - detect I/R schema - case-sensitivity
14428 - Implement support for SQ47114711M control column in CV
14436 - column import scripting for "DROP"
14437 - If use existing automatically drop non-existing destination columns
14440 - Expand "MAP" directive to provide means of defining derived column for a source column
14442 - Handle mapping of TIMESTAMP(93) to DATE(91)
14444 - If "use existing" is specified do not preserve unused source columns in the subscription
14458 - Informix LOB length macros
14480 - DB2 Connect fails to connect via StarPipes with non-zero Login Timeout
14481 - Increase new source/dest connection maximum default to 100
14482 - Informix (through DB2 gateway): subcription creation issue
14483 - JSON encoding of single quote
14493 - "P_KEY" column values in sqlogger "key" columns
14497 - changes for MySQL Connector/ODBC 8.0.13
SQDR_ODBC 8.0.1.9
v5.02.1016 Oct 2018 13552 - Disallow changing SQL Server source database during Add Subscription
14337 - win2019/win10 fall 2018: ADO/VARCHAR issue
14412 - SQLStatistics/SQLFetch fails with "numeric value out of range"
14413 - Don't lookup IR Schemas when running subscription wizard
14423 - SQDR_ODBC installer: add SQL Server 8
14424 - SQL Server: Qualify lookup for IR Schemas to default database if specified
14427 - Enforce soft-delete restricted update even if change vector not implemented
SQDR_ODBC 8.0.1.7
v5.01.0905 Sept 2018 14355 - SQDR: build with vs2017
14356 - SQDR Installer: updates for VS2017 build
14357 - SQDR & SQDR_ODBC Installer: update to InstallShield 2018
14365 - Allow derived column to be defined as part of destination where clause for CDC processing
14366 - Provide means to create/maintain a "partition key"
14367 - When import/inserting multiple subscriptions do not generate unique dest name if "use existing"
14371 - SQDR_ODBC: add Salesforce & Redshift
14390 - Modify open window protocol for Oracle
14397 - soft Delete option should also consider @TYPE, not just JED('enttyp')
14398 - Tighten use of "relaxedApply"
14402 - Installer: update to vs2017 14.15.26706 redistrib
14405 - Create of Group with Schedule in subscription wizard should not create schedule for subscriptions
SQDR_ODBC 8.0.1.5
v5.00.0722 Jul 2018 14207 - Redesigned checkpoint restart - expanded support for keyed tables
14273 - Subscription Wizard: Provide option to associate destination schema with source schema
14291 - Expose wait time for service shutdown in drmgr
14300 - Check to disable existing indexes for baseline should occur in separate UOW
14301 - Avoid failing to run baseline because checkpoint is invalid
14303 - Import Group Members with three-part names
14304 - Support Amazon Redshift as destination and snapshot source
14313 - Preseve service property customizations when using Manager
14314 - Serialized XML & JSON should match TIME & TIMESTAMP source scale
14325 - Revise connection management to support drivers/dbms without support for transactions
14338 - Add support for SalesForce & Redshift
14344 - Improve handling of re-prepare required in baseline
14345 - improvements for BT14207
14346 - Cannot create additional indexes on SQL Server ControlDB if CS is specified
14347 - Truncate results in SQL Error Invalid SQL <EOF>
14348 - Cache DBMS support for SQLCancel
StarSQL 6.37.0719
SQDR_ODBC 8.0.1.4
v4.99.0502 May 2018 14279 - option to ignore baseline source commit error
14280 - option to compress nonunique index (SQL Server)
14287 - Make sc stop sqdrsvc "fast"
14236 - SQDRConf: support ODBC Driver 17 for SQL Server & IBM DB2 ODBC driver
v4.98.0428 Apr 2018 11834 - If Use Existing and Destination allows, Disable/Rebuild non-unique indexes
14249 - Add macro @tz
14258 - SQL Server: Support I/R subs from database with hyphen or other nonstandard chars
14272 - Settings for various maximum Apply retry intervals
14279 - option to ignore baseline source commit error
14280 - option to compress nonunique index (SQL Server)
14287 - Make sc stop sqdrsvc "fast"
SQDR_ODBC 8.0.1.3
v4.97.0226 Feb 2018 14216 - Improve text in destination panel and I/R Group advanced panel
14219 - Use 3 part name if optioned on in RRN scalar function
14227 - provide mechanism to avoid matching non-supported ODBC types in subscription wizard
v4.96.1322 Jan 2018 9746 - Improve support for destination object naming conventions
13899 - Support Pervasive PSQL as a destination (SS & IR) and snapshot source
14050 - SDQR_ODBC: add SQDR Oracle 8.0.x & Hive 8.0.
14054 - SQDR Oracle 8.0.x driver - mapping for VARCHAR(10) and other data types
14117 - Expose "scale" for SQL_TIMESTAMP data types in subscription wizard
14126 - Drmgr: Decouple use of Qualifier and Schema from certified DBMS types
14127 - Expand use of GetValue to allow mix of C_Types and SQL Types
14128 - Replication should automatically disable MultiRow if not supported
14168 - Clarify error message when Apply flags an incremental subscription for baseline
14157 - Postgresql/Azure/MySQL/Pervasive target - rerun existing IR sub, does not attempt to drop index first - results in error
14180 - Cache GetTypeInfo Catalog call
14186 - Display preprocessing messages in subscription replication statistics during group run
14191 - Insert Member into Snapshot Group Fails
14194 - MySQL - datetime(0) -> datetime2(0) mappings resulting in RPC errors
14199 - Expose a useful default database value if the source/dest driver uses qualifier
SQDR_ODBC 8.0.1.2
StarSQL 6.34
v4.95.1114 Nov 2017 14080 - drmgr: display version # of servers
14121 - TargetChecker reports negative value (-1) in Source column when criteria specified
v4.94.1107 Nov 2017 13817 - Support schema & table name wildcard for COLUMN and DROP scripts
14058 - MySQL - IR w/LOB Column & decorator against source db/table
14105 - SQDR_Oracle Timestamp processing should display "TIMESTAMP(scale)" mapping option
14108 - Issues with change processing for null syncrhonized tables using unique constraints
14112 - Replicate char to varchar destination maintaining blank fill if RTRIM not enabled
14115 - Only truncate timestamps if source scale > target scale
v4.93.1024 Oct 2017 11613 - Permit Manager to connect to SQDRSVC on remote hosts
14060 - drmgr: Connections folder will not sort on "Name" column when clicked. Incorrect sort on "Dwell"
14064 - Subscription Wizard Apply option "Archive" broken for multiple subscriptions
14065 - Installer: create & document a Manager-only installer
14077 - drmgr: reduce elevation requirement
v4.92.1002 Oct 2017 14063 - Provide performance defaults for SQDR_Oracle driver connection strings
v4.91.0920 Sep 2017 14061 - Oracle to SQLServer - Manual Synchronization option - commit at source fails
v4.90.0912 Sep 2017 13903 - Recognize MySQL as Incremental Replication Source
13681 - Migrate SQDRSVC registry values to control database table
13924 - Fix verify criteria check (IR)
13941 - Add CSAC & CAC for Oracle Apply and Source connection strings
13942 - AddSubscriber should always use quoted names for construction of select column and where clause
13951 - Utilize persisted database capabilities in srcdestcache
13958 - Improve performance of group properties modifications
13970 - Use three part names for SQL Server & Azure Drop Index Statement
13971 - When using MINENDDTA do not UPSERT
13974 - iSeries MINENTDTA handling during open window processing
13976 - Move operation must relink TargetYoke
13983 - Avoid writing empty string into Oracle Character data type columns
13984 - Change service defaults for various parameters
14003 - suppress AutoUnique datatypes for destination mapping
14004 - Improvements to Cancel for subscription run and to connection handling for baselines
14009 - suppress "timestamp" as option for SQL Server destination column mapping
14015 -bind iSeries "ROWID" as binary data for purposes of Apply
14053 - Throw std::runtime_error instead of issuing "abort" when SQDR_ASSERT raised
StarSQL 6.33
SQDR_ODBC 7.1.6.6

Contacting StarQuest

If you need to contact technical support, please provide the following information to help the support engineers address your issue. You can contact StarQuest via phone, email, or facsimile as indicated at the bottom of this page.

Company Information Address
Phone
Fax
Contact Information First and Last Name of individual contact
Email Address
Host Type Hardware and Operating System (i.e., IBM i 7.3)
Network Protocol/Gateways Protocol and/or Gateways used (i.e., TCP/IP, HIS 2000)
Client Type Client Type and Operating System (i.e., Windows 2016)
StarQuest Product,
Version, and Source
Which StarQuest product and what version is installed (i.e., StarSQL for Windows v6.37.0719)
Where you obtained the software (i.e., direct from StarQuest, name of specific reseller)
Problem Information Provide as much detail as possible, including information about any application that is using the StarQuest product when the problem occurs and the exact error message that appears.

© 2021 StarQuest Ventures, Inc. All rights reserved.

StarQuest Ventures logoStarQuest Ventures, Inc.
548 Market St, #22938
San Francisco, CA 94104-5401
Telephone: +1 415.669.9619
FAX: +1 415.669.9639
Sales information: https://www.starquest.com/contact
URL: https://www.starquest.com
Support: https://support.starquest.com
Info Center: https://www.starquest.com/docs