This section provides information about problems or enhancements that are made available as "point releases" and major releases of the Stelo Data Replicator Plus software.
| Version Number | Release Date | Description |
|---|---|---|
| v6.51.0424 | Apr 2025 |
Bug Fixes 2098 - DB2/LUW T2 Lagtime shows as 0 during daylight savings time 1937 - Databricks stdout output size causes notebook to crash |
| v6.50.0414 | Apr 2025 |
New Features/ Enhancements 1846 - Docker container: SQDR Plus uses the same time zone as the host 1875 - Set user agent string for BigQuery 1555 - Enforce CPU core count license on SQDR Plus 1717 - Support source server switching for PostgresSQL Bug Fixes 1910 - Baseline of XML columns from DB2/UDB to BigQuery works but incremental rows cause exception in agent log 1935 - Offline table inadvertently added to XStream filter if published. 1994 - Staging error with Informix BYTE columns 2027 - Databricks: the worker thread remains active even thought the notebook was cancelled |
| v6.45.0211 | Feb 2025 |
New Features/ Enhancements Repackaged with SQDR 6.45 |
| v6.43.0122 | Jan 2025 |
New Features/ Enhancements 1532 - Support source server switching for MariaDB Bug Fixes 1641 - Publishing with import file does not work after jetty upgrade |
| v6.41.1211 | Dec 2024 |
New Features/ Enhancements Repackaged with SQDR 6.41 |
| v6.40.1129 | Nov 2024 |
New Features/ Enhancements 1291 - Update Jetty from 10.0.12 to 12.0.13, Derby 10.16.1.1 to 10.17.1.0, and JRE 17 to 21 1353 - Support MySQL JDBC 8.4 1463 - [BigQuery] New parameter checkNullability to apply data when the nullability of destinations columns in the tier 3 control database does not match the actual BigQuery destination table Bug Fixes 1507 - Stored procedure PUSHCHANGES returned error java.sql.SQLException: Temp table was not created after altering from NULL to not null and insert data to BQ destination 1508 - ALTER with the online keyword does not replicate the DDL over to the destination 1510 - Databricks: Harmless info message in agent log when a FLOAT source columns is baselined 1345 - "Could not initialize class com.starquest.sqdr.mgr.deserialization.BeanDeserializerWithValidation" when using "Set-Agent" commandlet |
| v6.39.0819 | Aug 2024 |
New Features/ Enhancements 740 - RTRIM support for BigQuery 870 - Upgrade JRE to 17.0.11 881 - Allow archive subscriptions from MySQL to be created for source table without primary key/unique index 925 - AS400: Make sure we sleep "pollSleepTime" ms if the userSpace was not completely filled. 893 - Upgrade JRE to 17.0.11 (Linux) Bug Fixes 952 - MySQL: MySQL/Azure does not allow upper case table names that are being used by SQDRPlus 920 - MySQL/MariaDB agent fails "silently" when processing complex DDL statement. 854 - "com.ibm.db2.jcc.am.SqlSyntaxErrorException" shows up after making baseline from DB2 FOR LUW to Databricks 979 - "JSONObject does not have a boolean" when mapping bit data type from MySQL to BQ 1037 - MySQL mediumtext to BigQuery does not honor our maxClobLength setting 1072 - Null-valued LOB data in baseline to Databricks causes exception |
| v6.38.0424 | Apr 2024 |
Bug Fixes / Enhancements 660 - Improve error messages from SQDRUDBLog64 Shared library 591 - Support mechanism to delay acknowledgment to XStream Outbound server 603 - HADR: Provide feedback about Standby UDB/DB state in GUI, history, and logs/diagnostics 717 - Allow BigQuery Baselines to run for more than 5 hours 718 - java.io.IOException: Cannot run program "db2pd": error=2, No such file or directory 742 - MariaDB/MySQL: Source timestamps are staged/replicated in the timezone of the Tier 2 Staging database. 724 - BigQuery: Error applying incremental changes to destination table where the highest ordinal is a derived non-nullable column 733 - Error when running baseline with the first column is a derived column 734 - wrong icon for parent agent 791 - MySQL/MariaDB, Slow record processing due to unintentially being dependent on pollSleepTime 775 - Temp table was not merged for bds.mbr_event_actions {UPDATE/MERGE must match at most one source row for each target row} resulting in possible duplicates |
| v6.37.0307 | Mar 2024 |
Bug Fixes / Enhancements 650 - Scala code: ability to specify additional properties on JDBC URL 667 - MySQL: char/varchar columns encoded as utf8mb3 translated to empty string 668: Certify DB2 11.5.9 Special Build 39210 (2024-02-08) to be used by Stelo as control database |
| v6.36.0229 | Mar 2024 |
Bug Fixes / Enhancements 634 - MySQL/MariaDB: Server/Connection Failures should not be ignored 635 - DB2 UDB LUW: Don't require the staging database to use the same codepage as source database |
| v6.34.0206 | Feb 2024 |
Bug Fixes / Enhancements 609 - XStream: Remove excessive INFO level messages. 612 - Databricks: pruning of request table can cause exception 618 - Db2 LUW 11.5.9 certified to be used as Stelo's control database 627 - Improve cancel behavior for streaming destinations (Databricks, BigQuery, etc.) |
| v6.33.0112 | Jan 2024 |
Bug Fixes / Enhancements 589 - iSeries: K record (key value change) needs to have fixed character columns trimmed (like I,U,D records) 590 - Databricks snapshot may fail due to stale cached metadata |
| v6.32.0108 | Jan 2024 |
New Features 459 - Persist changes to drmgr server connections immediately Bug Fixes / Enhancements 505 - Removing Maximum retry options 506 - Not showing warning "Pruner.run: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=SQDR.SQ_JRNMAP, DRIVER=4.25.1301" 507 - Agent statistics show 0 T2 lagtime when Tier 02 is in a different time zone 508 - Rollback/Undo can cause overflow in row count column 509 - Show number of Cores assigned to the Agent JVM on startup. 514 - [PostGreSQL] FK should be created as " DEFERRABLE " 517 - [BigQuery] Failure applying incremental data for subscription with RRN if there is a primary key defined for it on the destination table. 519 - [BigQuery] Bad row length estimate can cause Replication Manager to show negative byte count and throughput |
| v6.30.1207 | Dec 2023 |
New Features 169 - Support Google BigQuery as destination 397 - [Databricks] Automatically clean up SQDR.SQ_APPLYWORK 217 - [Databricks] Implement compression in t4 instead of in t2 218 - [Databricks] Improve the status feedback from the notebook to t3 380 - [Databricks] Improve feedback from Tier 4 to Tier 3, sufficient to ascertain if hung 381 - [Databricks] Optionally throw exceptions to the Scala code 491 - Change default for staging ""delete before image data for iSeries source using *AFTER journaling. 460 - Before image for iSeries Delete records even with journaling option *AFTER 211 - DB2 11.5.8 is certified to use for Stelo's control databases 431 - Default to cursorFetch for JDBC Connections to MS SQL Server 382 - Provide DB2 backup and restore scripts in [sqdrplus installation]/tools folder 317 - XStream usability improvements: 1) Remove case sensitivity when specifying source db by SID and using lower case. 2) Skip/ignore any older log records returned by XStream when using non-standard (e.g. Warm) startup/recovery option. Bug Fixes / Enhancements 202 - [Databricks] baseline with LONGTEXT from MySQL fails 303 - [Databricks] Possible data loss on tier 3 retry 339 - [Databricks] Provide better error messages when writing to local staging table during baseline 490 - [Databricks] Scala code fails to return error 420 - Drop existing ""merge indexes"" 201 - Excessive Diagnostics messages from MariaDB agent 406 - Missing alter from MariaDB 316 - Modify default for MySQL JDBC URL to limit memory usage |
| 6.22.1011 | Oct 2023 |
Bug Fixes / Enhancements 217 - Databricks - Implement compression in tier 4 instead of in tier 2 which improves performance when processing large numbers of incremental changes 218 - Databricks - Improve the status feedback from the notebook to tier 3. Added additional output in the Scala notebook. Makes it easier to see when a baseline starts and ends. 303 - Databricks - Possible data loss on tier 3 retry. Tier 3 detects if PushChanges is called when there already is an outstanding (not cancelled) PushChanges call for the group. The old call will be cancelled before processing starts of the new PushChanges call. |
| 6.21.0921 | Sep 2023 |
Bug Fixes / Enhancements 246 - Update log4j to 2.3.2 to address log4j vulnerability with a certain jar file |
| 6.20.0818 | Aug 2023 | New Features 17000 - Update Oracle Instant Client version to 19.19 15993 - Support PostGreSQL as incremental source 15905 - Support Confluent as a destination Bug Fixes / Enhancements 16143 - Databricks: (Pull) Long running transaction on the sq_applywork control table can cause a deadlock. 16127 - Databricks: Scala Apply code does not exit if there are errors applying changes 16028 - Error generating JDBC URL for DB2/LUW agent 15996 - The money data type cannot replicate negative number |
| 6.15.0531 | May 2023 |
New Features Bug Fixes / Enhancements 16011 - Databricks: Pull staged baseline fails for NCLOB data type 16020 - XStream: "-~" (Negative infinity) in NUMBER column, cause exception in NUMBER.toString() |
| 6.13.0131 | Jan 2023 | 13749 - Installer: update bundled version of jetty 13750 - Installer: update bundled version of derby 14778 - Installer: changes for JRE 17 14982 - JRE17: email & ftp 15523 - Launch agent: run db2updv115 after DB2 RESTORE DB 15556 - Installer: create kafkasq installer 15557 - Installer: changes for SQDR Plus 6x 15575 - Installer: update to IS2021 15579 - Installer: sign our Windows binaries 15595 - Installer: update prq.bat (script for choosing location of subinstallers) 15609 - Oracle XStreams: Acknowledge read position more often. 15617 - JTOpen 11.0 15672 - Control Center: Update to GWT 2.10 15678 - XStream: Restarting agent while processing single row transactions may leave uncommitted transactions. 15679 - XStream: Acknowledge low watermark position more frequently. 15684 - XStream: Implement workaround for Oracle Outbound Server running out of memory and hanging 15693 - Installer: include Oracle & iSeries scripts 15696 - Oracle Logminer RAC: Avoid or diagnose periodic hang 15707 - Xstream sourceDbName and case sensitivity 15717 - Oracle: T2 Lagtime always zero 15744 - Installer: update JRE to 17.0.5 15764 - Installer: update mysql-binlog-connector to 0.27.5 15756 - Installer: clean up old JRE, Jetty & Derby files 15801 - Installer: VS redistributables 14.34.31931.0 15806 - Control Center: use newer version of db2jcc4 JDBC driver 15807 - Installer: update to Oracle Instant Client 19.17 15808 - Control Center: update Oracle JDBC to 19.16 15809 - Installer: update hsqldb.jar to to 2.7.1 |
If you need to contact technical support, please provide the following information to help the support engineers address your issue. You can contact Stelo via phone, email, or facsimile as indicated at the bottom of this page.
| Company Information | Address Phone |
|---|---|
| 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, SSL/TLS) |
| Client Type | Client Type and Operating System (i.e., Windows Server 2019, Oracle Linux 8.6) |
| Stelo Product, Version, and Source | Which Stelo product and what version is installed (i.e., StarSQL for Windows v6.41.0719) Where you obtained the software (i.e., direct from Stelo, name of specific reseller) |
| Problem Information | Provide as much detail as possible, including information about any application that is using the Stelo product when the problem occurs and the exact error message that appears. |
Stelo, a StarQuest company
548 Market St, #22938
San Francisco, CA 94104-5401
Telephone: +1 415.669.9619
Sales information: https://www.stelodata.com/contact-stelo
URL: https://www.stelodata.com
Support: https://support.stelodata.com
Info Center: https://docs.stelodata.com