Release Notes Fivetran HVR Version 6.2.5/7 (linux_glibc2.12-x64-64bit) 2025-06-19 COMPATIBILITY FOR PLATFORM LINUX_GLIBC2.12-X64-64BIT ---------------------------------------------------- Fivetran HVR version 6.x is not compatible with the versions 5.x and 4.x. So, ensure that the HVR version is 6.x on the Hub machine and Agent machine. - Operating System: Linux (x86 64 bit) based on GLIBC 2.12 and higher. - Operating System: Red Hat Enterprise Server version 6 and higher - Operating System: SuSE Enterprise Server version 12.0 and higher This release contains 64-bit executables which will not run on a 32-bit Linux machine. - Ingres: 64-bit (a64.lnx) version 10.0, 10.1, 10.2, 11.0, 11.1, 11.2 (with patch 15820 or later) and 12.0 Capture of X100 tables is not supported - Vector: version 4.x, 5.0, 5.1 and 6.0 as hub and target, not capture. - Vector Hadoop Edition: version 4.x as hub and target, not capture. - Oracle: version 11.1, 11.2, 12.1, 12.2, 18, 19c and 21c, Exadata - Netweaver: version 7.5 and higher - DB2 on Linux, Unix, Windows: version 10.5, 11.1 and 11.5 - DB2 for i: version 7.2, 7.3, 7.4 and 7.5 Requires ODBC driver manager UnixODBC Requires IBM i Access Client Solutions ODBC Driver 64-bit - DB2 for z/OS: version 11.1, 12.1 and 13.1 Version 11.1 requires DB2 client, DB2 server or DB2 Connect version 10.5 or higher Versions 12.1 and 13.1 requires DB2 client, DB2 server or DB2 Connect version 11.1 fixpack 1 or higher - PostgreSQL: version 9.6, 10, 11, 12, 13, 14, 15, 16 and 17 Aurora PostgreSQL: version 11, 12, 13, 14, 15, 16 and 17 Yugabyte: version 2024.1 as capure and target, but not hub - MySQL: version 5.6, 5.7 and 8 MariaDB: version 10.3, 10.4, 10.5, 10.6 and 10.11 Aurora MySQL: version 1, 2 and 3. - SQL Server: version 2017 and Azure SQL Database Requires ODBC driver manager UnixODBC Requires ODBC Driver for SQL Server 11 or higher - Snowflake: version 2.x as target, but not hub or capture Requires ODBC driver manager UnixODBC Requires Snowflake ODBC driver 2.13.20 or higher - Sybase: version 16 as target, capture but not hub Requires Open Client-Library - SingleStore: version 7.1 (7.1.8 or higher) as target, but not as hub or capture - Databricks on Azure: 10.x, 11.x, 12.x, 13.x and 14.x as target, but not as hub or capture Requires ODBC driver manager UnixODBC Requires Simba Spark ODBC Driver 64-bit version 2.6.19 or higher - Databricks on AWS: versions 10.x, 11.x, 12.x, 13.x and 14.x as target, but not as hub or capture Requires ODBC driver manager UnixODBC Requires Simba Spark ODBC Driver 64-bit version 2.6.19 or higher - Google BigQuery: version 2.3 as target, but not as hub or capture Requires ODBC driver manager UnixODBC Requires Simba ODBC Driver for Google BigQuery 64-bit version 2.3.2 or higher - HANA: version 1.0 SPS 11 and 12, and version 2.0 SPS 00 up to SPS 08 Requires ODBC driver manager UnixODBC Requires HANA ODBC driver 2.00 or higher - Teradata: version 16.x and 17.x, as target and hub, not capture Requires Teradata ODBC driver 16.10 for Teradata 16.x Requires Teradata ODBC driver 17.10 for Teradata 17.x Requires TTU 16.10 libraries for Teradata 16.x Requires TTU 17.10 libraries for Teradata 17.x - Greenplum: version 4.0, 4.2, 4.3, 5.5 and 5.10 up to 6.90 as target, not as capture or hub. Requires DataDirect Connect64 XE ODBC 7.1.3.99 - 7.1.5 driver for Greenplum provided by Pivotal. - Redshift: version 1.0.x, as target, not as capture or hub. Requires ODBC driver manager UnixODBC. Requires Amazon Redshift driver 1.2.6.1006-1 - File replication: local, FTP/FTPS and SFTP - Apache Hadoop HDFS: version 3.3.6 and above HVR needs Hadoop 3.3.6+ libraries and Java 8 on its local machine to access HDFS. 'hadoop' command must be in $PATH or Hadoop home must have been configured via one of the following environment variables: $HADOOP_COMMON_HOME, $HADOOP_HOME, $HADOOP_PREFIX. - Apache Hive: version 1.1, 2.1, 2.3, 3.0, 3.1 with UnixODBC driver manager HVR can create Hive external tables above S3/HDFS files. Hvr only uses these during compare. Refresh or integration of this data is done into the S3/HDSF file location. Capture from Hive and hub database in Hive are not supported. Requires ODBC driver manager UnixODBC. Requires HortonWorks ODBC 2.1.2 or above for Hadoop Hive Requires Cloudera ODBC 2.5.12 or above for Hadoop Hive - Apache Kafka: version 0.8 and above (including 0.11) - S3: supported - Google Cloud Storage: supported - Azure Blob FS: supported - Azure Data Lake Store: supported - Installation: Hub and Agent - Perl 5.8 or higher (only needed for hub machine). BUNDLED IN THIS INSTALLATION ------------------------------------- - Fivetran Proxy Agent 1.1.0 - Java Runtime Environment (JRE) 17.0.14 API VERSIONS SUPPORTED BY THIS HUB SERVER AND FOR REMOTE CLI ------------------------------------------------------------ /api/v0 /api/v6.0.5 /api/v6.0.5.1 /api/v6.0.5.2 /api/v6.1 /api/v6.1.0.3 /api/v6.1.0.4 /api/v6.1.0.5 /api/v6.1.0.6 /api/v6.1.0.7 /api/v6.1.0.11 /api/v6.1.0.15 /api/v6.1.0.26 /api/v6.1.0.36 /api/v6.1.5 /api/v6.1.5.2 /api/v6.2.5 /api/v6.2.5.2 /api/v6.2.6 HOSTED DATABASE SUPPORT POLICY ----------------------------- Often HVR supported source and target locations that can be installed on premises will be hosted by third parties such as cloud providers including (but not limited to) Alibaba, Amazon, Google, Microsoft and others. These hosted systems are generally supported by HVR as sources and targets insofar as they are compatible with their downloadable counterparts. The certification of compatibility is incumbent on the hosting provider, not HVR. Platforms have been separately documented where compatibility is not comparable and HVR has been able to implement interoperability code changes (for example, Amazon Aurora PostgreSQL). If a provider claims compatibility then they must offer the same SQL and API calls and responses that support the features as indicated in the HVR documentation for the corresponding location class requirements in the appropriate source and target sections. In cases where compatibility is not complete then support is not guaranteed. Any issue that may exhibit itself on the hosted platform must be reproducible on an equivalent downloadable version to be considered a bug in the HVR software. INSTALLING A FIVETRAN HVR UPGRADE ------------------------- Often all machines are upgraded at the same time. Current HVR version are fully compatible with two previous major versions; it is not necessary to upgrade all machines in a channel at once. Instead it is possible to only upgrade certain machines. E.g. only the hub machine, agent machine, capture (could be the hub or an agent), or the integrate machine (could be the hub or an agent). If this is done, it should be understood that each HVR release fixes some bugs and/or contains new features. Each bug fix or feature is only effective if the specific machine(s) indicated for it are upgraded. New features should not be used until all machines that are specified for that feature are upgraded, otherwise errors can occur. For example, if a new HVR release fixes an integrate bug, then that release must be installed on the machine(s) which do integrate. So if only the hub machine is upgraded, then there will be no benefit. To decide whether each machines needs to be upgraded, see the descriptions in the release notes below. Each description ends with a line says which machine must be upgraded for that specific bug fix or feature to be effective. LOG BASED CAPTURE SUPPORT ------------------------- - Ingres Log based capture is supported for all Ingres versions supported by HVR. No support for dual or partitioned DBMS log-files. No support for page-spanning rows. DDL replication (using action AdaptDDL) is not supported. - Oracle Log based capture is supported for all Oracle versions supported by HVR. Oracle RAC (cluster) and Oracle ASM are supported. For Oracle version 9, log-based capture is not supported for LOBs or tables without a primary key. Compressed tables are only supported for Oracle 11.2 and higher. Log based capture is supported from Data Guard standby database for Oracle 11 and higher. HVR can also capture from an database that was previously a Data Guard target. If HVR was capturing changes from one primary Oracle database and a role transition occur (so that a different Data Guard target becomes the new primary) then HVR can continue capturing from the new primary, including capturing any changes which occurred before the transition. This process is automatic, providing that the HVR location is connecting to Oracle in a way which 'follows the primary'. Log based capture from tables that are encrypted using Oracle TDE is supported for Oracle version 11 and higher. Both tables in an encrypted tablespace and tables with encrypted columns are supported. HVR supports software and hardware (HSM) wallets. If the wallet is not configured as auto-login (Oracle internal file cwallet.sso), the password for the software wallet or HSM needs to be set on the HVR Live Wallet port using the hvrlivewallet command. The software wallet can be in ASM or in a local filesystem. Capturing from Oracle TDE is not supported on HP-UX. Platforms that use OpenSSL version 3 do not support auto-login wallets for Oracle version 11. - SQL Server Log based capture is supported for SQL Server 2008, 2012, 2014, 2016, 2017, 2019 and 2022. Data Compression is supported. Capture from compressed backup transaction log files is supported. Capture from encrypted backup transaction log files is supported. Capture from memory optimized tables is not supported. Capture from tables with XML_COMPRESSION = ON is not supported. Capture of typed XML columns containing xsd:float and xsd:double values is not supported. Log based capture from databases that are encrypted using the SQL Server TDE is supported. The log based capture is supported only for the databases whose Database Encryption Key (DEK) is protected by Certificates. Log based capture is not supported from databases whose DEK is protected by Asymmetric Key. Column level encryption is not supported. Always Encrypted feature is not supported. - DB2 on Linux, Unix, Windows (LUW) Log based capture is supported for DB2 on Linux, Unix, Windows (LUW). The following table types are supported - regular tables, multidimensional clustering (MDC) tables, insert time clustering (ITC) tables, uncompressed tables, row compressed tables (both static and adaptive) and value compressed tables (both static and adaptive). - DB2 for i Log based capture is supported for DB2 for i - DB2 for z/OS Log based capture for DB2 for z/OS is supported. The following table types are supported - regular tables, compressed tables, partitioned tables, history tables and archive tables. Capture from LOAD is not supported. - PostgreSQL Log based capture is supported for all PostgreSQL versions supported by HVR. - HANA Log based capture is supported on Linux (not Windows) for HANA: version 1.0 SPS 11 and 12, and version 2.0 SPS 00 up to SPS 07 Only column-store tables are supported (no row-store tables). - MySQL and MariaDB Log based capture is supported for all MySQL and MariaDB versions supported by HVR. FIVETRAN HVR NETWORK ENCRYPTION ---------------------- An HVR connection to a remote location can be configured so that all communication over the network is encrypted. For network encryption, HVR uses OpenSSL, which is developed by the OpenSSL Project (http://www.openssl.org). HVR uses OpenSSL version "3.0.8" On UNIX, HVR's encryption will attempt to exploit the entropy (randomness) generation capability supplied by the '/dev/urandom' device. For optimal security, it is recommended that this Operating System option is installed, especially on the machine used to generate public/private key pairs CREDITS ------- - License Agreements, Copyrights, and Notices for the third-party software are listed in the hvr.3rdparty file in HVR_HOME directory NEW FEATURES IN HVR 6.2.5/7 (2025-06-19) ---------------------------------------- [T-696646] ADDED SUPPORT FOR CUSTOM ALERT HEADERS To use this feature, upgrade HVR on the hub machine(s). This new feature adds support for customizable alert headers. You can now include custom text and dynamic keywords such as [[channel]], [[hub]], and [[location]] in alert messages. [T-918755] THIS FEATURE ADDS THE OPTION TO PROCESS KEY UPDATES AS DELETE/INSERTS TO A SOFTDELETE TARGET. To use this feature, upgrade HVR on the integrate and hub machine(s). The ColumnProperties action has a new option, MarkBeforeKeyChangeRowAsDeleted which is only valid if the SoftDelete option is set. When processing a key update, if MarkBeforeKeyChangeRowAsDeleted is set the old row will be retained and marked as deleted. [T-924654] KEEP DIFFERENCE FILES OPTION IS NOW ONLY ALLOWED FOR HUBOWNER OR SYSADMIN To use this feature, upgrade HVR on the hub machine(s). Verbose compare and refresh now requires HubOwner or SysAdmin. This is the `-v` option on the CLI for hvrcompare and hvrrefresh, and the UI option 'Keep Difference Files' for the dialogs. The UI option is no longer shows to users that lack these privileges. [T-952485] OPTIONALLY ADD KEY RANGES TO THE INSERT JOIN TO LIMIT THE NUMBER OF ROWS JOINED To use this feature, upgrade HVR on the integrate machine(s). For updates that have column values missing, and where there is a surrogate key, HVR issues an insert join that inserts into the burst table a new set of rows with missing columns populated by the matching rows in the target. This feature provides an option that causes HVR to add key ranges to the clause that joins with the target table, reducing the number of rows included in the join. [T-956617] ADDED 'CMVP' TO PACKAGE NAMES FOR HVR BUILDS USING FIPS-VALIDATED OPENSSL VIA CMVP To use this feature, upgrade HVR on all machine(s). Package names now include a "cmvp" when HVR is built with OpenSSL that has been validated under the Cryptographic Module Validation Program (CMVP). [T-959196] UPDATED OPENSSL VERSION IN CMVP-CERTIFIED BUILDS TO 3.0.8 To use this feature, upgrade HVR on all machine(s). Updated the OpenSSL version used in CMVP-certified builds to 3.0.8. [T-964651] BUNDLE FIVETRAN PROXY 1.1.0 To use this feature, upgrade HVR on the agent machine(s). Upgraded bundled Fivetran Proxy to 1.1.0 [T-972940] ENHANCED RESILIENCE OF HVRLICENSE ERROR HANDLING To use this feature, upgrade HVR on the hub machine(s). This improvement enhances the resilience of hvrlicense by converting several specific errors into warnings. The following error codes are now treated as warnings: `F_JR4508`, `F_JR4509`, `F_JR450A`, `F_JR450B`, `F_JR450D`, and `F_JR450F`, all related to missing cols_key_sorted or cols_nkey_sorted fields in sample or metadata files. Additionally, when MAR with re-sync detection fails, hvrlicense now automatically falls back to MAR without re-sync detection to improve reliability. [T-900891] DATABRICKS: IMPLEMENTED VERSION RECOVERY LOCATION PROPERTY To use this feature, upgrade HVR on the integrate and hub machine(s). This new feature adds the Version Recovery Location property for Databricks to ensure proper recovery from integration job failures and prevent duplicate entries on the target. It introduces a new 'last_successful_version' column in the burst state table. The column is automatically added by altering the existing table, so no table recreation is needed. [T-928438] DATABRICKS: ADDED SUPPORT FOR DATABRICKS ODBC DRIVER VERSION 2.9.1 To use this feature, upgrade HVR on the integrate machine(s). Added support for Databricks ODBC driver version 2.9.1. [T-953583] DB2 FOR LINUX, UNIX AND WINDOWS: ENABLED DISPLAY OF ALL SCHEMA NAMES IN TABLE SELECTION UI To use this feature, upgrade HVR on the integrate and capture machine(s). This new feature enables all schema names, including those starting with reserved prefixes such as "SYS " and "Q ", to be displayed in the schema list of the table selection UI for Db2 LUW. Previously, these schemas were hidden based on IBM recommendations. You can now view and select tables from all available schemas regardless of their names. [T-918655] DB2 FOR I: ADDED SUPPORT FOR CAPTURING PROGRAM_NAME AND JOB_NAME To use this feature, upgrade HVR on all machine(s). This new feature enables capturing the PROGRAM_NAME and JOB_NAME values from transactions in Db2 for i. To enable this, set the environment variables HVR_DB2I_PROGRAM_NAME=1 and/or HVR_DB2I_JOB_NAME=1. The captured values are exposed as {hvr_cap_program} and {hvr_cap_job}, and can be used in RenameExpressions, CaptureExpressions, and IntegrateExpressions. The value "UNKNOWN" will be used for {hvr_cap_program} and {hvr_cap_job} (1) during refresh, (2) for Db2 for i source locations if HVR_DB2I_PROGRAM_NAME or HVR_DB2I_JOB_NAME is not set and (3) for all other source DBMS. [T-732012] MARIADB: ADDED SUPPORT FOR MARIADB VERSIONS 10.5, 10.6 AND 10.11 To use this feature, upgrade HVR on the integrate, capture and hub machine(s). Added support for MariaDB versions 10.5, 10.6 and 10.11. Dropped support for MariaDB versions 10.0, 10.1 and 10.2. [T-919966] MYSQL: ADDED SUPPORT FOR MYSQL 8.4 To use this feature, upgrade HVR on the integrate, capture and hub machine(s). This new feature enables replication and integration with MySQL 8.4, allowing full compatibility across capture, hub, and integration components. [T-949935] ORACLE: ADDED OPTION TO EXCLUDE REDO LOGS DATED IN THE FUTURE To use this feature, upgrade HVR on the capture and hub machine(s). This feature allows you to exclude redo log files -archived or online- if their timestamp is ahead of the current system time on the database host. Such logs can cause issues in certain environments. To enable this behavior, set the environment variable HVR_ORA_EXCLUDE_FUTURE_DATED_LOGS to 1. The default is 0. [T-797120] SNOWFLAKE: IMPROVED CREDENTIAL MASKING IN COPY INTO ERRORS To use this feature, upgrade HVR on the integrate machine(s). This improvement enhances credential masking in the integrate log when COPY INTO statements fail for Snowflake targets. Sensitive AWS credentials (such as aws_key_id, aws_secret_key, and aws_token) are now automatically obfuscated in error messages to prevent unintended exposure in log files. PROBLEMS FIXED IN HVR 6.2.5/7 (2025-06-19) ---------------------------------------- [T-865957] ADDED ENVIRONMENT VARIABLE TO DISABLE SQL SERVER MAXIMUM KEY LENGTH ERROR. To fix this bug, upgrade HVR on the integrate machine(s). By default, HVR would reject the creation of a primary key constraint in SQL Server if the combined key length exceeded 900 bytes, resulting in an error. This update adds `HVR_MSSQL_MAX_KEY_LEN_ERROR_DISABLE` environment variable to disable reporting error in such cases and continue to creation of primary key constraint. [T-890325] FIXED F_JS0610 DURING REST API REQUEST GET HUBS/{HUB}/DEFINITION To fix this bug, upgrade HVR on the hub machine(s). This fix improves the hub configuration cache policy, reducing unnecessary database access and preventing the error. [T-905188] FIXED F_JD2236 DUPLICATE KEY ERROR IN HVR_STATS To fix this bug, upgrade HVR on the hub machine(s). Fixed a rare issue that caused the F_JD2236 duplicate key error when processing HVR statistics. The process now logs duplicate rows as warnings instead of stopping execution when this condition occurs. T-868131 T-823623 [T-919530] FIXED F_JR0E14 FOR CLOUD VMS WITH TEMPORARY FINGERPRINT QUERY FAILURE To fix this bug, upgrade HVR on the hub machine(s). Fixed the F_JR0E14 error on cloud VMs caused by a temporary failure in the cloud metadata query used for fingerprint generation. This bug could cause licenses from registered HVR installations on Consumption Based Pricing to not work properly. [T-920516] FIXED F_JR0E14 ON HUBS RUNNING ON GOOGLE CLOUD INSTANCES To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where fingerprinting failed with F_JR0E14 on hubs running on Google Cloud instances. This fix updates the signature verification process to correctly use the public certificates published by Google. [T-922064] FIXED INVALID TIMESTAMP FORMAT ERROR THROWN BY HVR ALERT To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where HVR alert was throwing an invalid timestamp format error. This fix ensures that HVR alert correctly reads timestamp entries, even if the last line in the log file is incomplete. The check has been made more resilient to ignore invalid timestamps. [T-923959] FIXED INTEGRATE PERFORMANCE ISSUE WITH PRUNERANGE HIGH CPU USAGE To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue that caused the integrate job to have high CPU usage in the prune range logic. [T-924657] ADDED AN ENVIRONMENT VARIABLE TO CONTROL THE MAPPING BINARY TO UUID To fix this bug, upgrade HVR on the integrate machine(s). Added an environment variable to control byte order adjustment when replicating from binary columns to UUID columns. By default, HVR adjusts the byte order of the first three groups in a UUID on little endian machines. Set the environment variable to disable adjustment when targeting UUIDs. The variable applies to all columns in all tables for the associated integrate job. [T-945452] FIXED F_JG200A DUE TO INCOMPLETE VALIDATION OF COLUMN PROPERTIES SETUP To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue that caused a segmentation fault when multiple IntegrateExpression parameters were defined for the same column without using ExpressionScope. This fix adds validation to ensure such configurations are only allowed when ExpressionScope is present. [T-947603] FIXED HVRLICENSE FAILURE DUE TO MISSING METADATA IN MAR FILES To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where `hvrlicense` failed due to missing cols_key_sorted or cols_nkey_sorted metadata in MAR files. This occurred when the hub had previously written MAR files without the required metadata, leading to any of the following errors: - F_JR4508: Missing cols_key_sorted from Main Sample file of the following configurations - F_JR4509: Missing cols_key_sorted from .mar_meta file of the following configurations - F_JR450A: Missing cols_key_sorted from Main Sample file and .mar_meta file of the following configurations - F_JR450B: Missing cols_nkey_sorted from Main Sample file of the following configurations - F_JR450D: Missing cols_nkey_sorted from .mar_meta file of the following configurations - F_JR450F: Missing cols_nkey_sorted from Main Sample file and .mar_meta file of the following configurations This fix ensures that the hub now correctly writes complete metadata in new MAR files. T-949470 T-945873 [T-949533] FIXED MAR ISSUE FOR COLUMNS WITH BASENAMES To fix this bug, upgrade HVR on the integrate machine(s). Fixed MAR issue for columns with base names configured in the repository catalogs or through action ColumnProperties with parameter BaseName [T-950403] FIXED POSSIBLE DEADLOCKS WITH UPSERT-STYLE REFRESH JOBS To fix this bug, upgrade HVR on the hub machine(s). Fixed a possible deadlock that could occur when running an upsert-style refresh job. [T-956591] FIXED F_JR2A06 WITH ENABLED ADAPTDDL ON SAP-BASED LOCATION To fix this bug, upgrade HVR on the capture machine(s). Fixed F_JR2A06 with enabled AdaptDDL on SAP-based location. [T-957443] FIXED COMPARE REPORTING DIFFERENCES FOR DECIMAL/NUMERIC -0 VERSUS 0 To fix this bug, upgrade HVR on all machine(s). Some DBMS allow both -0 and 0 as value in decimal/numeric data type columns. In some situations HVR compare would report differences for those values. That has now been fixed. [T-961690] ENHANCED MEMORY MANAGEMENT IN HVRLICENSE FOR MAR WITH RE-SYNC DETECTION To fix this bug, upgrade HVR on the hub machine(s). Enhanced hvrlicense memory management for MAR with re-sync detection. [T-936543] DATABRICKS: FIXED F_JD2911 ERROR WITH UNITY_CATALOG FLAVOR FOR DATABRICKS. To fix this bug, upgrade HVR on the integrate machine(s). Fixed F_JD2911 error with UNITY_CATALOG flavor for Databricks that occurs when HVR hub version does not support UNITY_CATALOG flavor, while the agent version does. [T-947468] DATABRICKS: FIXED ERROR F_JD1203 WHEN COLUMN NAMES CONTAIN SPECIAL CHARACTERS To fix this bug, upgrade HVR on the integrate machine(s). Fixed error F_JD1203 when column names contain certain special characters. [T-965214] DATABRICKS: FIX ERROR F_JD1202 FOR DATABASE NAMES STARTING WITH DIGITS To fix this bug, upgrade HVR on the integrate machine(s). Fixed error F_JD1202 that occurred when using a database with a name beginning with a digit. [T-946217] DB2 FOR I: FIXED DBMS ERROR SQL0502 DURING REFRESH To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed the F_JD22D3 : DBMS error [SQL0502 - Cursor SQL_CUR0578EA90 already open or allocated] that caused Refresh to restart. [T-954964] DB2 FOR I: FIXED F_JD22D3 WHEN SWITCHING RECEIVERS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where Db2 for i capture failed with F_JD22D3: DBMS error [SQL0443 - STARTING_SEQUENCE OR ENDING_SEQUENCE NOT FOUND] when switching between journal receivers. [T-962665] DB2 FOR I: FIXED REFRESH CRASH WHEN SOME DATABASE ERRORS ARE HIT To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed call when cleaning up statements on some error handling. [T-951847] DB2 FOR Z/OS: FIXED F_JZ9240 WHEN CAPTURING WITH ADAPTDDL To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where capturing from Db2 for z/OS with AdaptDDL enabled could fail with error F_JZ9240: "SYSTABLES 'x,x,x::hvr_systables' delete log record encountered with unexpected length." This occurred when views or aliases were deleted from the Db2 for z/OS source database. [T-936692] ORACLE: FIXED QUERY BUILDER ISSUE GENERATING INVALID WHERE CLAUSE To fix this bug, upgrade HVR on the capture machine(s). This fix addresses an issue where the Oracle query builder would incorrectly include WHERE (NULL) in certain scenarios, leading to invalid SQL syntax. [T-952037] ORACLE: FIXED AN ISSUE IN THE HCC PARSER THAT TRIGGERED ERROR F_JD2E00 ON INTEGRATE SIDE To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue in the HCC parser that triggered error F_JD2E00 on Integrate side. [T-968201] POSTGRESQL: FIXED F_JG2430 WHEN ACTIVATING REPLICATION WITH SUPPLEMENTAL LOGGING To fix this bug, upgrade HVR on the hub machine(s). Fixed F_JG2430 error occured during replication activation when checking a PostgreSQL table's replica identity, specifically for tables outside the default schema. [T-971475] POSTGRESQL: FIXED MEMORY LEAK FOR POSTGRESQL CAPTURE To fix this bug, upgrade HVR on the capture machine(s). Fixed memory leak issue in PostgreSQL logical replication capture during parsing records. [T-950822] SQL SERVER: IMPROVED SPARSE COLUMNS SUPPORT To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed an issue that could cause data integrity problems when replicating sparse columns in clustered SQL Server tables. After upgrade, perform Activate Replication with table enrollment to apply the fix. For tables with sparse columns, HVR will now prompt for an index rebuild if it detects that sparse column IDs cannot be reliably mapped. This happens when either of the following has occurred since the last index rebuild: - Columns were dropped. - Columns were altered in a way that causes SQL Server to internally drop and recreate them (e.g., changing column nullability). [T-965105] SNOWFLAKE: FIXED A BUG WHERE A NEW PRIMARY KEY WAS NOT REPLICATED VIA ADAPTDDL To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where AdaptDDL did not replicate a new primary key constraint to the target when the source table initially had no primary key. [T-930191] SYBASE ASE: CORRECTED UNNECESSARY LOG PAGE READS DUE TO PERCEIVED TIMESTAMP INCONSISTENCIES To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where the capture process misidentified timestamp inconsistencies, resulting in unnecessary log page reads. This fix improves performance by optimizing how timestamp consistency is evaluated during log reading. T-924886 NEW FEATURES IN HVR 6.2.5/6 (2025-05-22) ---------------------------------------- [T-578774] RE-ENABLED MASK PARAMETER FOR REFRESH AND COMPARE To use this feature, upgrade HVR on the hub machine(s). This feature re-enables the -m (mask) parameter in the hvrrefresh and hvrcompare commands, as well as in the UI. The mask parameter is useful for scenarios where more data exists in the target than in the source, such as when deletes are ignored during capture. This change restores essential functionality for filtering target data during refresh and compare operations. [T-762641] ENABLED SPLIT ALERTS FOR INDIVIDUAL MESSAGES To use this feature, upgrade HVR on the hub machine(s). Alerts can now be split into separate messages, one for each alert. The title of each message reflects the specific alert. In split alert mode, the message limit controls the maximum number of alerts sent per alert check. [T-843080] ADDED SAML SINGLE LOGOUT (SLO) SUPPORT To use this feature, upgrade HVR on the hub machine(s). This new feature enables SAML Single Logout (SLO) support in HVR. SLO allows you to log out of all applications connected to the Identity Provider (IdP) in a single action. When you log out from the IdP, you are automatically logged out from the HVR UI in all browser sessions. However, logging out from the HVR UI in one browser only ends that session, while other browser sessions and the IdP session remain active. To enable this feature, ensure that your IdP supports SAML SLO and that the 'SingleLogoutService' endpoint is configured in the IdP. This endpoint can be found in the SP metadata file. T-843079 [T-912224] DB2 FOR LINUX, UNIX AND WINDOWS: ADDED SUPPORT FOR DB2 LUW VERSION 12.1 ON AIX To use this feature, upgrade HVR on the integrate and capture machine(s). Added support for Db2 LUW version 12.1 on AIX. [T-927916] DB2 FOR LINUX, UNIX AND WINDOWS: CREATED LOCATION PROPERTY TO ALLOW LOGGING OF BULK LOAD To use this feature, upgrade HVR on the integrate and hub machine(s). This new feature adds the location property Copy_Yes_Path to to allow bulk load operations during integrate or refresh to be logged into the recovery log. The target database must be recoverable for this feature to function. [T-936321] GOOGLE BIGQUERY: ADDED THE ABILITY TO LOAD USING EXTERNAL TABLES To use this feature, upgrade HVR on the integrate and hub machine(s). This new feature adds an optional method for loading target tables in BigQuery using external tables. BigQuery enforces a quota of 1,500 loads per table per day when using LOAD DATA. To avoid hitting this limit, this feature introduces an alternative method. It stages data in cloud storage, creates an external table, and uses INSERT SQL to load the target table. This method only affects burst loads; refresh operations continue using LOAD DATA to support parallel slicing. [T-844072] ORACLE: ALLOW FOR LONGER BANNERS IN ORACLE DB To use this feature, upgrade HVR on the capture machine(s). This new feature enables HVR to capture the full database banner in newer Oracle Database versions. Previously, longer banners could be truncated, which may have caused minor connection or validation issues. [T-886071] POSTGRESQL: ADDED SUPPORT FOR POSTGRESQL 17 To use this feature, upgrade HVR on all machine(s). Added support for PostgreSQL 17. [T-912492] POSTGRESQL: IMPROVED SUPPORT FOR LOOP DETECTION WITH REPLICATION ORIGIN To use this feature, upgrade HVR on the integrate machine(s). Added support for managing recapturing in Bulk Refresh for PostgreSQL as target. Added error check F_JD6502 for illegal duplicate session name used for Loop detection. This only applies to PostgreSQL using Logical Replication (Capture_Method=SQL) with the 'pgoutput' plugin. [T-896569] REDSHIFT: ADDED SUPPORT FOR PARQUET FOR STAGING To use this feature, upgrade HVR on the integrate machine(s). This new feature adds support for using the Parquet file format during staging to Amazon Redshift. [T-945542] SAP HANA: ADDED SUPPORT FOR HANA 2.0 SP8 To use this feature, upgrade HVR on the capture machine(s). Added support for HANA 2.0 SP8, which introduces a new log encoding format. PROBLEMS FIXED IN HVR 6.2.5/6 (2025-05-22) ---------------------------------------- [T-844018] FIXED ERROR MESSAGE FOR EMPTY TIMESTAMP ON INACTIVITY ALERT To fix this bug, upgrade HVR on the hub machine(s). Fixed error message for empty timestamp on alert. Now, it will skip the inactivity alert if it cannot retrive the time timestamp of the last activity. [T-860721] FIXED HUB SERVER CONFIGURATION PARTIALLY RESET DURING SETUP To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where the hub server configuration was partially reset during setup, which is only relevant if the user pre-configures advanced properties not available in the setup UI before running the actual setup. E.g. Hubserverconfig properties `HTTPS_PrivateKey_Password` and `Public_Key` were explicitly deleted during the setup process, when the customer clicked the Confirm Repository Connection button. This fix ensures that any hubservconfig properties are not deleted during the setup process. [T-908769] FIXED THE INTEGRATE STATISTICS GRAPHS FOR APPEND MODE To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue that prevented the integrate statistics graphs from being displayed when the Integrate method was set to APPEND. [T-910794] FIXED SIGBUS ON SPARC WHEN READING DECFLOAT VALUES To fix this bug, upgrade HVR on the integrate, capture and hub machine(s). Fixed an issue that caused a SIGBUS error on SPARC systems, and potentially other architectures with strict memory alignment requirements, when reading decfloat values. This fix ensures memory is properly aligned before invoking decNumber functions, which require aligned memory access. [T-921880] FIXED F_JD1202 ERROR CAUSED BY MULTI-DELETE OPERATIONS TO TIMEKEY TARGET To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where multi-delete operations caused an F_JD1202 error during integration into a TimeKey target. This fix ensures that multi-delete operations are now processed correctly without triggering errors. [T-922783] FIXED INTEGRATION OF DOUBLE-PRECISION FLOATING-POINT NUMBERS INTO SNOWFLAKE To fix this bug, upgrade HVR on the integrate machine(s). Fixed integration of double-precision floating-point numbers into Snowflake by increasing the precision from 15 to 17 significant digits. [T-928439] FIXED PASSING INCORRECT LIST OF PREDEFINED SUBSTITUTIONS TO USE WITH INTEGRATE /MESSAGEKEY OPTION FOR KAFKA-BASED LOCATION To fix this bug, upgrade HVR on the integrate and hub machine(s). Passed a valid set of predefined substitutions for Kafka-based location used in with Integrate /MessageKey option [T-936774] ENHANCED MEMORY TRACKING IN CERTAIN ORACLE ASM SCENARIOS To fix this bug, upgrade HVR on all machine(s). This fix enhances memory tracking to ensure all allocations are correctly monitored during capture from Oracle ASM sources. The fix extends the previous enhancements made in T-926960, addressing a case where memory usage could appear to grow continuously due to previously untracked allocations. [T-938801] FIXED F_JG4518 MAR SAMPLE BUFFER CAPACITY EXCEEDED To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue that caused the MAR sample buffer to exceed capacity during sliced loads, triggering error F_JG4518. [T-941966] FIXED F_JG0EA2 INVALID OR NOT SUPPORTED MAR SIGNATURE VERSION 4 To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue that caused error F_JG0EA2 due to an unsupported MAR signature version. This occurred when using a newer MAR with re-sync detection on older installations lacking support for version 4. The fix ensures backward compatibility with earlier versions. [T-945364] FIXED BROKEN LINKS TO DOCUMENTATION FOR LOCATION CONNECTION FOR DATABRICKS AND DATABRICKS REQUIREMENTS. To fix this bug, upgrade HVR on the hub machine(s). Fixed broken links to documentation for Location Connection for Databricks and Databricks Requirements. [T-934209] DATABRICKS: FIXED F_JD2150 ERROR FOR DEFAULT DATE VALUES ON DATABRICKS To fix this bug, upgrade HVR on the integrate machine(s). Fixed F_JD2150 error that occurred when a default value was generated for a datetime or timestamp column in Databricks. [T-872400] DB2 FOR I: FIXED WARNING W_JT044C DUE TO SKIPPED RECORDS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue in Db2 for i capture where missing begin transaction records triggered Warning W_JT044C. This issue could also cause other record types to be skipped, potentially leading to ignored changes. [T-944399] ORACLE: FIXED A BAD COLUMN DATA PARSING ON ORACLE HCC TABLE INSERT OPERATION To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue with bad column data parsing from Oracle redo-record for an insert operation into HCC table, triggering error F_JD2E00 on Integrate side. [T-947231] ORACLE: FIXED A MEMORY CORRUPTION DURING ORACLE HCC ZLIB DECOMPRESSION To fix this bug, upgrade HVR on the capture machine(s). Fixed a memory corruption during Oracle HCC Zlib decompression. [T-931862] POSTGRESQL: FIXED POSSIBLE ERROR F_JG221D OCCURRING AFTER ENROLL REVISION To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue (F_JG221D) encountered in the capture job after processing an enroll revision involving a source table schema change. For example, adding a partition that was detected by Activation. [T-936071] POSTGRESQL: FIXED PARSING COMMIT TIMESTAMP FROM BEGIN WITH PGOUTPUT To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where the commit timestamp in Begin messages was not parsed when using the pgoutput plugin. This fix ensures that the commit timestamp is now correctly read and processed. [T-933697] SAP HANA: FIXED F_JZ0A36 WHILE DECODING STRING-BASED DATATYPES FOR HANA SP8 To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where the wrong length encoding method was selected when decoding string-based datatypes for HANA SP8. The fix ensures that both the HANA release version and the column description are considered. Backward compatibility was also implemented to process archived log files from previous HANA versions. [T-887151] SQL SERVER: FIXED OPERATION ORDERING FOR SQL SERVER SETWISE OPERATIONS To fix this bug, upgrade HVR on the capture machine(s). Fixed a data integrity issue where SQL Server could emit deletes after inserts during setwise operations. This issue occurred when HVR_SETWISE_KEYUPDATE_DECOMPOSE was set to "default" or "auto". The fix ensures that deletes are always processed before inserts during setwise updates to maintain data integrity. [T-923646] SQL SERVER: FIXED F_JD0A62 FOR SQL SERVER STRIPED BACKUPS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where reading from certain SQL Server striped backups resulted in error F_JD0A62. [T-923953] SQL SERVER: FIXED F_JD21AE WHEN GENERATING STATISTICS FOR OAUTH2 SQL SERVER CONNECTIONS To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where the F_JD21AE error occurred when generating statistics for OAuth SQL Server connections. [T-946141] SYBASE ASE: FIXED ISSUE CAUSING SYBASE ASE TO THROW JUNK CHARACTERS IN CAPTURE JOB To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where Sybase ASE capture jobs were failing due to invalid characters appearing in the output stream. NEW FEATURES IN HVR 6.2.5/5 (2025-04-24) ---------------------------------------- [T-602875] ENABLED MAR WITH RE-SYNC DETECTION To use this feature, upgrade HVR on the integrate and hub machine(s). This new feature enables MAR with re-sync detection for consumption-based pricing. It ensures accurate measurement by charging only for changed data during a refresh, eliminating the need to restrict refreshes within the 5-day troubleshooting window. To use this feature, upgrade the HVR Hub and the HVR Agent (on integrate machines). If you don't upgrade prior to renewal, data used in the system (MAR without re-sync detection) will be applied to the new service consumption table: https://www.fivetran.com/legal/service-consumption-table-update. Transition to the updated pricing model is a contractual/billing task that needs to be aligned between customer and sales representative. Additional disk storage is required on the hub system in $HVR_CONFIG. This feature is not supported for HANA sources. Hubs not registered under consumption-based pricing remain unaffected. [T-696642] ADDED HVR LATENCY ONLY ALERT OPTION To use this feature, upgrade HVR on the hub machine(s). Added a new feature that enables sending latency only alerts. [T-696643] ADDED HVR LATENCY ESCALATION ALERT OPTION To use this feature, upgrade HVR on the hub machine(s). This feature adds support for latency escalation alerts, allowing to define alerts with multiple levels of escalation based on latency thresholds. You can configure alerts to notify different recipients at each escalation level, enabling more precise and timely responses to latency issues. [T-696650] HVR ALERTS FOR ALERT ACTIVITY WINDOWS AND FREQUENCIES To use this feature, upgrade HVR on the hub machine(s). We have added the activity window and frequencies feature. You can now add activity windows to control when alerts get executed and set alert frequencies for each window. This feature enables deeper control over alert execution. [T-696651] ADDED SUPPORT FOR CUSTOM ALERT FILTERING WITH REGULAR EXPRESSIONS To use this feature, upgrade HVR on the hub machine(s). This new feature enables the use of custom regular expressions for alert filtering, replacing the default pre-filtering behavior. You can now define a regex to determine which log messages are considered before applying exclusion and inclusion filters, allowing for more flexible alert customization. [T-762199] HVR ALERTS BLACKOUT WINDOW FEATURE To use this feature, upgrade HVR on the hub machine(s). Added the Alerts Blackout Window feature, which allows you to suppress alerts during predefined time periods. This feature supports scheduling blackout windows for specific durations or recurring intervals, applicable at the channel, group, or hub level. You can also end a blackout period early if needed. [T-762637] CUMULATIVE INCLUSION AND EXCLUSION FILTERS FOR HVR ALERTS To use this feature, upgrade HVR on the hub machine(s). Added cumulative inclusion filters using regular expressions to the existing ignore pattern filter for HVR alerts. This enhancement allows more granular control over which alerts are included or excluded based on specified patterns, improving alert management flexibility. [T-805646] HONORED REPEAT INTERVAL FOR LATENCY ALERTS To use this feature, upgrade HVR on the hub machine(s). Latency alerts now respect the configured Repeat Interval setting in all scenarios. This enhancement ensures that latency alerts are not repeatedly sent within the specified interval, reducing unnecessary duplicate notifications. [T-909508] ADDED SUPPORT FOR JOIN CONDITIONS IN RESTRICT REFRESH AND COMPARE To use this feature, upgrade HVR on the agent and hub machine(s). This new feature allows you to add table joins in action Restrict with parameters RefreshJoinCondition and CompareJoinCondition. It is available only for SQL Server source locations. [T-919463] BUNDLE JRE 17.0.14 To use this feature, upgrade HVR on the agent machine(s). Upgraded the bundled JRE to version 17.0.14 and updated the release notes generation to use JRE versions instead of Zulu versions. [T-878274] DATABRICKS: ADDED SUPPORT FOR KMS-ENCRYPTED S3 STAGING BUCKETS To use this feature, upgrade HVR on the hub machine(s). This feature enables support for S3 buckets with KMS encryption when configuring the Integrate Staging Directory for a Databricks location. You can now specify a customer master key ID for encryption. [T-884441] DATABRICKS: ADDED SUPPORT FOR PRIMARY KEY CONSTRAINTS FOR DATABRICKS To use this feature, upgrade HVR on the integrate and hub machine(s). Added support for primary key constraints for Databricks with Unity Catalog. [T-866318] DB2 FOR I: ADDED TRACE MESSAGES FOR DB2 FOR I To use this feature, upgrade HVR on the capture machine(s). Added more trace messages for Db2 for i capture. This shows more information when HVR_DB2I_READ_TRACE is set regarding create timestamps of journals. [T-925836] DB2 FOR Z/OS: ADDED SUPPORT FOR CAPTURING RECORDS ENCODED USING EDITPROC To use this feature, upgrade HVR on the capture machine(s) and upgrade HVR's stored procedures on the DB2 for z/OS capture machine(s). To enable this set environment variable HVR_DB2Z_ZREAD_EDITPROC=1 on the capture location. This requires Db2 version 13 function level 100 or higher. [T-861450] ORACLE: ENABLED THE ASM/BFILE CHANNEL TO SAVE REDOS USING A UNIQUE PATH To use this feature, upgrade HVR on the capture machine(s). This feature enables saving archive logs in different directories, providing more flexibility and control over data management. It is particularly beneficial for Oracle RAC ASM-BFile configurations with multichannel setups. [T-911813] ORACLE: ADDED ERROR HANDLING FOR LONG TABLE NAMES IN ORACLE SUPPLEMENTAL LOGGING To use this feature, upgrade HVR on the capture and hub machine(s). This feature adds validation for Oracle supplemental logging to throw an error if a table name exceeds the 30-character limit. HVR previously enforced this limit only for column names. With this change, table names are also checked for compliance. If you are using a GoldenGate license, this limit increases to 128 characters. [T-913609] ORACLE: ADD SUPPORT FOR ORACLE CHARACTERSET WE8ISO8859P9 To use this feature, upgrade HVR on the capture machine(s). HVR main driver already had support for ISO-8859-9 [Latin 5, Turkish]; this feature enables it for Oracle DB. The name of this encoding in Oracle is WE8ISO8859P9. [T-850408] POSTGRESQL: ADDED SUPPORT OF ALTER COLUMN TO ADAPTDDL FOR POSTGRESQL To use this feature, upgrade HVR on the capture machine(s). Added support of alter column to AdaptDDL for PostgreSQL. HVR now supports capturing ADD COLUMN, DROP COLUMN, and ALTER COLUMN operations, including changes to data type, data size (shrink and extend), and precision for character, numeric and timestamp data types. [T-868097] POSTGRESQL: ADDED SUPPORT OF KEY CHANGES TO ADAPTDDL FOR POSTGRESQL To use this feature, upgrade HVR on the capture machine(s). Added support of replication key changes to AdaptDDL for PostgreSQL. HVR replication key aligns PostgreSQL's REPLICA IDENTITY setting and keys. - When REPLICA IDENTITY = DEFAULT, primary key is used as HVR replication key. - When REPLICA IDENTITY = USING INDEX, the chosen unique index is used as HVR replication key. - When REPLICA IDENTITY = FULL, HVR prioritizes the first unique index as the replication key. If none exists, HVR uses all non-LOB columns. With AdaptDDL defined, it will take effect once capture job encounters replication key changes. [T-893563] SAP HANA: ADDED SUPPORT FOR NEW LOG TRANSACTION FORMAT IN SAP HANA SP8 To use this feature, upgrade HVR on the capture machine(s). SAP HANA SP8 introduced a new encoding format for short string lengths between 128 and 255. This feature ensures support for the updated log transaction format, maintaining compatibility with SAP HANA's latest changes. [T-831828] SYBASE ASE: LIST ALL TABLES AFFECTED BY A TRANSACTION WHEN ENCOUNTERING A CAPTURE ERROR To use this feature, upgrade HVR on the capture machine(s). This feature adds the ability to list all tables affected by a transaction when a capture error occurs. This feature is only available for direct capture. The feature is disabled by default and can be enabled by setting the environment variable `HVR_SY_ENABLE_DEFERRED_ERROR` to `1`. When enabled: 1. If a record fails to be read or parsed during capture, and the transaction ID can be identified, capture will continue reading until it encounters the commit for that transaction. 2. Once the commit is detected, error `F_JT080B` will be thrown for each error that occurred within the transaction. 3. Each error message will include: 4. The original error code and message that would have been thrown at capture time 5. The affected table name 6. The associated channel name PROBLEMS FIXED IN HVR 6.2.5/5 (2025-04-24) ---------------------------------------- [T-887772] FIXED DATE FORMATTING ISSUE IN REFRESH WITH SLICING To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue in the Refresh dialog where selecting the Slicing option with a date field and using boundary-type slicing would format the boundaries with an added time and timezone. A new option, Plain Date, has been added to the dropdown menu to format date boundaries without appending time or timezone. Previously, entering a date would format it as 2025-01-01T00:00:00+0100 or 2025-01-01T00:00:00Z based on the Local Time or UTC selection. With the new Plain Date option, the format is now 2025-01-01. [T-899132] FIXED CHANGE IN EXTENDED DATATYPE NOT BEING HANDLED IN TABLE REDEFINITION To fix this bug, upgrade HVR on the hub machine(s). Fixed issue that occurred when redefining a table from source, and a column changed from one extended datatype to another. The change was not detected, leaving the column with the original data type. [T-901035] FIXED SQL SERVER TIME COLUMN REPLICATING TO NEGATIVE INTEGER IN KAFKA To fix this bug, upgrade HVR on the integrate and hub machine(s). Fixed an issue where a SQL Server time(7) column was incorrectly replicated to a negative integer in Kafka. [T-901526] FIXED INCORRECT DATABASE LABEL IN DATETIME CONVERSION ERRORS To fix this bug, upgrade HVR on the integrate machine(s). Fixed incorrect database labels in log messages for datetime conversion errors. Previously, error messages incorrectly referenced a specific database system (e.g., "DB2") instead of reflecting the general HVR data type. Each relevant message has been updated to use a standardized format, ensuring clarity and accuracy when reporting datetime conversion issues across different database systems. Additionally, incorrect datetime constants in these messages have been corrected. [T-901920] UPDATED MARIADB CONNECTOR/C TO VERSION 3.4.0 To fix this bug, upgrade HVR on all machine(s). Updated HVR to use MariaDB Connector/C version 3.4.0 for improved compatibility and performance. [T-902011] SECURITY ENHANCEMENTS FROM UPGRADING GO To fix this bug, upgrade HVR on the hub machine(s). Go version used to compile hvrhubserver upgraded on all build systems. [T-906341] ENHANCED TRACING SYSTEM FOR CAPTURE JOB To fix this bug, upgrade HVR on the capture machine(s). This feature enables you to more easily control and observe logs produced during a capture job. It helps simplify debugging of incidents that may occur while using HVR. [T-911315] IMPROVED 'OUT-OF-RANGE' MESSAGES To fix this bug, upgrade HVR on all machine(s). Improved 'out-of-range' messages according to English rules [T-911391] FIXES UNEXPECTED CONDITION READING TMPSTORE DURING INTEGRATE To fix this bug, upgrade HVR on the integrate machine(s). Fixes an issue where integrate jobs are failing with an `F_JG21DF: Unexpected condition while reading of temp store` error during replicating a channel with a Surrogate key. This fix ensures that tempstores are internally copied when needed to avoid reading potentially corrupted tempstore. [T-921746] FIXED SLOW PERFORMANCE OF BATCH TABLE PROCESSING BY SAP DESCRIBE To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where redundant SQL requests caused slow performance during batch table processing with SAP Describe. [T-926960] ENHANCED MEMORY TRACKING IN CERTAIN ORACLE ASM SCENARIOS To fix this bug, upgrade HVR on all machine(s). Fixed an issue where certain memory allocations were not included in HVR's internal tracking. This enhancement improves visibility for debugging in rare scenarios, such as when using Oracle ASM capture. [T-932854] FIXED F_JD21AE SSL ERROR IN MEMSQL To fix this bug, upgrade HVR on all machine(s). Fixed a F_JD21AE error in MemSQL where SSL is not being disabled on servers where it is not supported. [T-844978] AZURE DATA LAKE STORAGE: FIXED INCORRECT PROCESSING 403 ERROR WITH AZURE FS PRIVATE ENDPOINTS To fix this bug, upgrade HVR on the integrate and capture machine(s). Fixed an issue where a 403 (Unauthorized) error was incorrectly processed when using private endpoints to access Azure Data Lake Storage. This fix implements a fallback mechanism to allow continued access if one of the interfaces is forbidden. [T-911883] AZURE DATA LAKE STORAGE: FIXED FLUSH FAILURE CAUSED BY MEMORY ALLOCATION ERROR To fix this bug, upgrade HVR on all machine(s). - Fixed an issue where flush operations to Azure Data Lake Storage (ADLS) could fail due to a memory allocation error. The underlying Azure SDK has been updated to resolve this problem. [T-925810] AZURE DATA LAKE STORAGE: FIXED INCORRECT PROXY FORMAT FOR GENERATING AZURE TOKEN To fix this bug, upgrade HVR on all machine(s). - Fixed an issue where token generation Azure SQL Server was failing due to incorrect proxy format. [T-891207] DB2 FOR LINUX, UNIX AND WINDOWS: FIXED DBMS ERRORS DURING CAPTURE START MOMENT ACTIVATION To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where using the Capture Start Moment (capture) option during replication activation could cause DBMS errors (SQL2657N or SQL2651N). This fix ensures that rewind start ranges are correctly determined based on valid log sequence numbers and timestamps present in the recovery logs. [T-911874] DB2 FOR I: FIXED DBMS ERROR SQL0519 DURING REFRESH To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed the F_JD22D3 : DBMS error [SQL0519 - Prepared statement STMT0002 in use] during refresh when the receiver before the current receiver has been purged. [T-919123] DB2 FOR I: FIXED F_JD22E8 ERROR MESSAGE TEXT To fix this bug, upgrade HVR on the capture machine(s). Fixed the F_JD22E8 error message text [T-898076] ORACLE: FIXED TDE WALLET PATH ESCAPING To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where TDE wallet path escaping was not handled correctly. This fix ensures automatic detection of path styles and proper handling of Windows-style paths within a Linux hub. [T-911681] ORACLE: FIXED LOB HANDLES LEAKING DURING POSITIONING STEP To fix this bug, upgrade HVR on the capture machine(s). Fixed LOB handles leaking during positioning step [T-913009] ORACLE: FIXED F_JT02CD WHILE COMPARING/REFRESHING ORACLE SOURCE USING SELECT MOMENT To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed an issue when comparing/refreshing from Oracle using a Select Moment [T-922929] ORACLE: FIXED FREEING OF UNALLOCATED MEMORY To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed an issue where the initial capture setup could fail when reading logs, leading to an attempt to free unallocated memory. This fix improves the stability of the capture process when starting replication. [T-912685] POSTGRESQL: FIXED COMPATIBILITY ISSUE WITH POSTGRESQL REPLICATION ORIGINS To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where HVR Agents running older versions could encounter the F_JD2912 error with PostgreSQL replication origin management feature. This feature, introduced in HVR version 6.2.5/2, allows HVR to automatically track and manage replication progress on PostgreSQL, enabling loop detection. This fix ensures backward compatibility with HVR Agents that do not support this capability. [T-914519] POSTGRESQL: FIXED CAPTURE HANG WHEN USING RESTART SETTING To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where the capture job could hang when the environment variable HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL was set to 1. [T-901315] SAP HANA: ADDED ENVINOMENT VARIABLE TO DETECT STATE TABLES IN ALL SCHEMAS To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where the Loopback Adapter in HANA only detected loopback if the HVR_I* state tables existed in the schema owned by the location user. Introduced the HVR_STATE_TBL_GLOB_ALL_SCHEMAS environment variable to enable scanning for state tables across all schemas. This ensures loopback detection works as expected. [T-905310] SAP HANA: FIXED HANDLING SAVEPOINT (PARTIAL ROLLBACK) IN SAP HANA To fix this bug, upgrade HVR on the capture machine(s). This change fixes the handling of SAVEPOINT (partial rollback) operations in SAP HANA log replication. [T-914434] SQL SERVER: FIXED F_JD20F2 ERROR FOR AZURE SYNAPSE SOURCES To fix this bug, upgrade HVR on the integrate, capture and hub machine(s). Fixed an issue where error F_JD20F2 occurred during channel activation for Azure Synapse locations. [T-926240] SQL SERVER: FIXED SQL SERVER MEMORY LEAK ON CONNECTION To fix this bug, upgrade HVR on all machine(s). Fixed an issue where a memory leak occurred during the SQL Server connection process. [T-895365] SNOWFLAKE: FIXED UNNEEDED ALTER TABLE STATEMENTS FOR VARIANT COLUMNS To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where a column of type VARIANT resulted in unnecessary ALTER TABLE statements. [T-903871] SNOWFLAKE: FIXED LOCALIZATION FOR SMALL FIXED-SIZE LONG DATA TYPES To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where small fixed-size long data types were not correctly localized during integration. This fix ensures accurate data handling for these types in Snowflake. [T-851063] SYBASE ASE: LOCALIZING SYBASE ASE DATATYPE DATETIME FOR CSV INTEGRATION FAILED To fix this bug, upgrade HVR on the integrate machine(s). When replicating from Sybase ASE to a CSV file, one may experience an error message like this one: `F_JD0F01: Localizing datatype 'sybase_datetime' to dbms [file..v0] for column 'dt' of table 'ff_csv_sybase_datetime' was unsuccessful` With this change the error will no longer be thrown and the replication will work as expected. [T-913680] SYBASE ASE: FIXED F_JD02A5 NUMBER OF ROWS VERY LARGE WHILE COMPARING To fix this bug, upgrade HVR on all machine(s). Fixed an issue while comparing Sybase ASE tables with a very large number of rows. Using COUNT_BIG( ) instead of COUNT( ). NEW FEATURES IN HVR 6.2.5/4 (2025-03-18) ---------------------------------------- [T-891077] ADD ENVIRONMENT VARIABLE HVR_CAP_STATE_TRACE TO ENABLE LOGGING OF CAP_STATE DATA. To use this feature, upgrade HVR on the capture machine(s). Environment variable `HVR_CAP_STATE_TRACE` has been introduced to enable logging of `cap_state` data. [T-892484] ENHANCED HVRSSLGEN FOR HTTPS CONFIGURATION ASSISTANCE To use this feature, upgrade HVR on the hub machine(s). Enhanced hvrsslgen CLI command: - Added an example for configuring the Hub Server for HTTPS. - Improved the --help output for better usability. Enhanced the hvrhubserverconfig CLI command: - Introduced -K and -k options to copy certificate files to the appropriate directory. [T-896515] ADDED SUPPORT FOR CMVP-CERTIFIED HVR RELEASES To use this feature, upgrade HVR on all machine(s). Added support for CMVP (Cryptographic Module Validation Program)-certified releases of HVR. You can now choose between standard HVR releases and CMVP-certified releases, ensuring compliance with cryptographic security standards. [T-872874] DB2 FOR LINUX, UNIX AND WINDOWS: ADD COPY YES OPTION TO BULK LOAD IN DB2 To use this feature, upgrade HVR on the integrate and hub machine(s). Add new parameter HVR_DB2_LUW_COPY_YES_PATH to set a location to save backup images for db2 LUW bulk LOAD COPY=YES option. This was added to allow bulk LOAD in refresh or integrate to log entries in the recovery log. [T-900774] DB2 FOR I: REMOVED SYSTEM TABLE FILTERING FOR TABLE DISPLAY To use this feature, upgrade HVR on all machine(s). Previously, HVR filtered out tables owned by 'SYSDTB', 'QSYS', 'QBRMS', 'QPGMR', 'QSECOFR', and 'QTMHHTTP' when displaying lists of Db2 for i tables. This change removes that filtering, ensuring all tables are now visible in table lists. [T-903122] DB2 FOR I: INTRODUCED A NEW SQL EXPRESSION SUBSTITUTION {HVR_TX_SEQUENCE_NUMBER} To use this feature, upgrade HVR on the integrate, capture and hub machine(s). Introduced a new SQL expression substitution, {hvr_tx_sequence_number}, which lets you include the Db2 for i sequence number. It can be used only if the source location database is Db2 for i. For more information, see the MessageKey parameter in the Integrate action or the IntegrateExpression parameter in the ColumnProperties action. [T-818783] SNOWFLAKE: SUPPORT USING PARQUET FILES WHEN STAGING DATA TO SNOWFLAKE To use this feature, upgrade HVR on the integrate and hub machine(s). This feature adds support for staging data using Parquet files when loading data into Snowflake. By default, HVR uses CSV files for staging data into a target database. To ensure accurate replication of DATETIME data in Snowflake, the TZ environment variable must be set to match the time zone of your Snowflake data warehouse. When using Parquet files for staging, dates prior to the year 1583 (the Julian to Gregorian calendar switch) will not be replicated correctly. PROBLEMS FIXED IN HVR 6.2.5/4 (2025-03-18) ---------------------------------------- [T-845409] FIXED INTEGRATION OF LOB COLUMN UPDATES ON DUPLICATE TABLES To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where updates to LOB columns were ignored during burst integrate on tables with duplicates. This fix ensures burst integrate treats LOB columns as part of the replication key, preventing their changes from being skipped. [T-873674] FIXED TIMEKEY COMPARE ERROR AFTER MIGRATION FROM HVR 5 To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where 'hvr_integ_seq' and 'hvr_tx_seq' integrate expressions were not resized during migration from HVR 5 to HVR 6, leading to coalesce errors in HVR compare. These expressions are shorter in HVR 5 than in HVR 6. The hvrconvert5to6 script now updates the action to ensure the correct expression size and prompts users to update their target tables. [T-886198] FIXED RECOVERY FOR APPEND INTEGRATE METHOD To fix this bug, upgrade HVR on the integrate and hub machine(s). Fixed an issue where recovery with the APPEND integrate method could result in duplicate rows in the target TimeKey table. [T-888438] FIXED UPSERT REFRESH TABLES NOT ADHERING TO ACTION DBOBJECTGENERATION WITH PARAMETER BURSTTABLESCHEMA To fix this bug, upgrade HVR on the integrate and hub machine(s). Fixed an issue where the upsert refresh tables were not created in a schema defined by Action DbObjectGeneration with parameter BurstTableSchema. [T-892206] FIXED POSSIBLE F_JG2459 ACTIVATING CHANGE FROM BURST TO APPEND To fix this bug, upgrade HVR on the hub machine(s). If the Integrate method is changed from BURST to APPEND on a busy system, activation may interrupt Integrate while Integrate is applying changes to the target. If this happens then when the Integrate job re-starts is will throw the error "F_JG2459: Get value of variable 'proc_move_phase' failed. Variable not set.". The fix is to reset the flag that indicates burst applying changes to the target is incomplete. [T-892683] FIXED ERROR MESSAGES WHEN HTTPS_PRIVATE_KEY_PASSWORD IS INCORRECT To fix this bug, upgrade HVR on the hub machine(s). Added errors for missing cases when password was missing or incorrect. [T-894732] FIXED LEGACY FLOAT NON-NUMERIC VALUE REPRESENTATION ON WINDOWS To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where non-numeric float values were represented in a legacy format on Windows (for example, NaN was represented as 1#QNAN000000000). [T-896929] FIXED F_JD20FF WHEN PROCESS SAP DATA ON SQL SERVER 2008 To fix this bug, upgrade HVR on the integrate, capture and hub machine(s). SQL Server 2008 uses deprectated IMAGE data type to store binary data, added support to process it [T-901521] FIXED UNKNOWN API VERSION ERROR WITH USER_AUTO_CREATE IN HUB SERVER To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where the API version 'v6.2.5.3' was unknown to the Hub Server when using the User_Auto_Create feature. Users do not need to perform any additional steps after the upgrade. T-885642 [T-903823] FIXED F_JC0516 ON SERVICE NAME WITH HYPHEN FOR ORACLE RAC To fix this bug, upgrade HVR on the hub machine(s). Fixed TNS redirection when connecting to Oracle RAC clusters with a dash ( `-`) in their service name. [T-342436] ORACLE: FIXED SEGMENTATION VIOLATION ON ORACLE PLUGGABLE DATABASE WITH AUTO-LOGIN TDE WALLET To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue that caused a segmentation violation (SIGSEGV) during activation on Oracle pluggable databases using an auto-login TDE wallet. [T-506235] ORACLE: FIXED ORACLE CAPTURE STUCK IN AN INDEFINITE CYCLE ON A RAC ENVIRONMENT To fix this bug, upgrade HVR on the capture machine(s). This fix addresses an issue in Archive Log Only (ALO) mode Oracle Capture for getting stuck in an indefinite cycle looking for archive log on a RAC environment with more than 7 clusters. [T-872373] ORACLE: FIXED SEGMENTATION VIOLATION ON INSERT INTO ORACLE HCC TABLE To fix this bug, upgrade HVR on the capture machine(s). This fix addresses a segmentation violation in the capture process when processing specific insert operation on Hybrid Columnar Compression (HCC) tables. This issue was caused by a specific column encoding in compressed data, which depended on the table structure and data. [T-886892] ORACLE: FIXED FAILURE IN CONNECTING TO AN ORACLE RAC DATA GUARD INSTANCE To fix this bug, upgrade HVR on the capture and agent machine(s). This fix addressed a failure when capturing from an Oracle RAC Data Guard physical standby instance, which requires a SYSDBA privilege. [T-881786] POSTGRESQL: FIXED ADVANCING THE REPLICATION SLOT IN IDLE CHANNELS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where PostgreSQL logical replication capture was failing to update the capture state and advance the replication slot when the channel was idle. This fix ensures that keepalive messages from logical replication are correctly processed. The fix only works when `HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL` is set to `0`. [T-895947] POSTGRESQL: MOVED REPLICA IDENTITY ERROR CHECK TO CHANNEL ACTIVATION To fix this bug, upgrade HVR on the capture and hub machine(s). Fixed an issue where refresh-only channels failed with the F_JR6501 error when adding tables. This happened due to the PostgreSQL table's REPLICA IDENTITY configuration. The error check is now performed during channel activation if the Supplemental Logging option is selected. [T-896858] POSTGRESQL: DO NOT ALTER REPLICA IDENTITY TO FULL WHEN CREATING TABLE WITH KEYS To fix this bug, upgrade HVR on all machine(s). When creating tables in a PostgreSQL database, HVR always set replica identity to full using ALTER TABLE. This has been fixed for tables with keys to preserve the default replica identity. [T-904989] POSTGRESQL: FIXED ADDING NEW TABLES TO PUBLICATION ON POSTGRESQL To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where newly added tables in an existing channel were not capturing changes. This occurred because new tables were not added to the publication. [T-868226] SQL SERVER: FIXED F_JD0A6A FOR SQL SERVER STRIPED BACKUPS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where reading from certain SQL Server striped backups resulted in error F_JD0A6A. [T-894808] SQL SERVER: FIXED F_JD0A6B FOR SQL SERVER STRIPED BACKUPS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where reading from certain SQL Server striped backups resulted in error F_JD0A6B. [T-905515] SQL SERVER: FIXED CAPTURE CRASH IN SQL SERVER WHEN NO BACKUPS FOUND To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where a segmentation fault occurred during capture in SQL Server if the query to determine backup locations returned no rows. [T-893129] SNOWFLAKE: FIXED ERROR MESSAGE F_JD22C1 WHEN HAVING CUSTOM SQL DATATYPES DISABLED To fix this bug, upgrade HVR on the integrate machine(s). Fixed error message F_JD22C1 when having custom SQL datatypes disabled ( `HVR_SNOWFLAKE_ODBC_USE_CUSTOM_SQL_DATA_TYPES=FALSE`). [T-888313] SYBASE ASE: FIXED SYBASE ASE MULTI-DIRECTIONAL REPLICATION To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue with multi-directional replication in Sybase ASE where the capture process was incorrectly recapturing changes made by integrate job, causing an infinite replication loop. [T-796337] TERADATA: FIXED PARAMETERS BINDING ISSUE To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue (F_JD20F0) where SQL_NEED_DATA error occurred in Teradata location when using parameters binding. [T-888220] UI: FIXED 'REPLICATION COMPONENTS NOT ACTIVATED' ERROR IN FILE-TO-FILE CHANNELS To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where file-to-file channels incorrectly displayed the error "Some replication components not activated for location", despite being correctly activated. NEW FEATURES IN HVR 6.2.5/3 (2025-02-18) ---------------------------------------- [T-814570] INTRODUCED /ONCAPTURETABLEENDCYCLE PARAMETER TO CAPTURE To use this feature, upgrade HVR on the capture and hub machine(s). Introduced /OnCaptureTableEndCycle parameter to Capture Action. When enabled, transactions involving these tables will terminate the capture cycle and force the end of the integration cycle after resolving the transaction. [T-867133] BUNDLE PRUNSRV-1.4.1-X64 To use this feature, upgrade HVR on the agent machine(s). Upgraded bundled prunsrv-1.4.1-x64.exe. T-791943 - Investigate and Fix Popup when stopping windows proxy service [T-885642] USER PROVISIONING To use this feature, upgrade HVR on the hub machine(s). This new feature enables automatic user provisioning. Non-SAML user provisioning When non-SAML user provisioning is enabled and a user tries to log in with a username unknown to HVR, HVR will try to verify the user with the configured authentication method for user provisioning. If the user can be verified, the user will be automatically created with the same authentication method. To enable this feature, set the repository property `User_Auto_Create` to value `pam`, `plugin` or `windows`. SAML user provisioning When SAML user provisioning is enabled and a user attempts to log in using SAML 2.0 authentication, and the third-party trusted Identity Provider successfully authenticates the user, the SAML user will be automatically created if the user is not yet known by HVR. To enable this feature, set the repository property `User_Auto_Create=saml` and set up SAML as the authentication method. - T-833068 - Build a feature in HVR to provision a user in case the user called during login does not exist in the repository but does exist in LDAP - T-200332 - [M] HVR Support Single Sign-On to HVR hub through SAML [T-735476] DATABRICKS: ADDED INTEGRATE APPEND METHOD FOR TIMEKEY CHANNELS To use this feature, upgrade HVR on the integrate and hub machine(s). This feature adds a new Integrate method, APPEND, for writing TimeKey changes directly to the target table when the target is Databricks. The APPEND method is only applicable to TimeKey channels with a Databricks target. When set, row changes are staged and then loaded into the target table. [T-735475] GOOGLE BIGQUERY: ADDED INTEGRATE APPEND METHOD FOR TIMEKEY CHANNELS To use this feature, upgrade HVR on the integrate and hub machine(s). This feature adds support for the APPEND Integrate method when the target is BigQuery. When the Integrate method is set to APPEND, row changes are staged and then loaded directly into the target table. [T-753751] ORACLE: ADDED SUPPORT FOR PASSWORDLESS AUTHENTICATION To use this feature, upgrade HVR on the capture and hub machine(s). Added support for TLS passwordless authentication to source database through specification of username as "passwordless" and a dummy password. [T-830951] ORACLE: ADDED SUPPORT FOR WE8DEC CHARACTER SET FOR ORACLE CAPTURE To use this feature, upgrade HVR on all machine(s). Added support for capturing data from columns using the WE8DEC character set encoding in Oracle. This character set, also known as DEC-MCS, IBM1100, CP1100, and csDECMCS, is specified by setting NLS_LANG=AMERICA_AMERICAN.DECMCS in the Oracle client environment. Previously, using this character set resulted in the F_JD5E07 unsupported character set error. [T-691654] POSTGRESQL: REMOVED HVR_PQ_SELECT_USE_CURSOR ENVIRONMENT VARIABLE To use this feature, upgrade HVR on the capture and hub machine(s). Removed the HVR_PQ_SELECT_USE_CURSOR environment variable. [T-863241] POSTGRESQL: ADDED SUPPORT OF YUGABYTEDB RELEASE 2024.2 To use this feature, upgrade HVR on all machine(s). Added support of YugabyteDB latest release 2024.2.x.x. [T-551961] REDSHIFT: SUPPORT REDSHIFT ODBC DRIVER VERSION 2.1.4+ To use this feature, upgrade HVR on the integrate machine(s). Support Redshift ODBC driver version 2.1.4+ [T-863905] SQL SERVER: ADDED SQL SERVER ENVIRONMENT VARIABLE TO SET CDC TABLE ROLE-NAME To use this feature, upgrade HVR on the capture machine(s). This new feature adds the environment variable HVR_MSSQL_CDC_ENABLE_ROLENAME, which allows you to set the database role that is passed to `sys.sp_cdc_enable_table` when enabling supplemental logging during activation. [T-735477] SNOWFLAKE: ADDED INTEGRATE APPEND METHOD FOR TIMEKEY CHANNELS To use this feature, upgrade HVR on the integrate and hub machine(s). This feature adds support for the APPEND Integrate method when the target is Snowflake. When the Integrate method is set to APPEND, row changes are staged and then loaded directly into the target table. [T-717373] TERADATA: ADDED AN ENVIRONMENT VARIABLE PROVIDING DEFAULTS FOR MISSING TIMESTAMP VALUES To use this feature, upgrade HVR on the integrate machine(s). Added the environment variable HVR_TERADATA_DEFAULT_MISSING_TIMESTAMP, which allows you to set a default value for missing values of the timestamp type in Teradata targets. PROBLEMS FIXED IN HVR 6.2.5/3 (2025-02-18) ---------------------------------------- [T-692082] IGNORING 404 ERRORS DURING DELETE IN S3 To fix this bug, upgrade HVR on the integrate machine(s). Ignoring 404 errors during delete in S3. [T-840520] FIXED ROW DUPLICATION AFTER ONLINE REFRESH FAILS ON SEQUENCE QUERY To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where a failed sequence query during an online refresh could result in duplicate rows. This fix moves the sequence query to a separate subtask in the refresh job, ensuring that only the failed query is retried without affecting the rest of the process. [T-844466] FIX HVRAGENTLISTENER STARTUP FAILURE ON AIX 7.3 To fix this bug, upgrade HVR on the capture and agent machine(s). The hvragentlistener fails to start on AIX 7.3 because of loading environment variables with floating point data types. [T-853293] FIXED BULK REFRESH FAILURE FOR ORACLE LOCATIONS WITH CASE-SENSITIVE NAMES To fix this bug, upgrade HVR on the integrate and capture machine(s). Fixed an issue where bulk refresh fails for Oracle locations when case-sensitive names are enabled. [T-867908] FIXED CRASH DUMP GENERATION ON LINUX To fix this bug, upgrade HVR on all machine(s). Fixed crash dump generation on Linux. [T-871969] AZURE DATA LAKE STORAGE: FIXED F_JG0B15 ERROR WHEN GETTING AUTHENTICATION TOKEN FOR AZURE To fix this bug, upgrade HVR on the integrate, capture and hub machine(s). We have made the following improvement to the Azure SDK for HVR: - Fixed F_JGOB15 when getting token from Azure FS when using Azure Client credentials mode [T-859707] DATABRICKS: FIXED AN ISSUE WITH DUPLICATE ROWS IN TARGET TABLE AFTER RECOVERY DURING A MERGE REFRESH To fix this bug, upgrade HVR on the integrate and hub machine(s). Fixed an issue with duplicate rows in target table after recovery during a merge refresh. [T-876036] DATABRICKS: ALLOW NAN/INF VALUES IN FLOAT COLUMNS WHEN REPLICATING TO DATABRICKS To fix this bug, upgrade HVR on the integrate machine(s). Fixed a bug where NaN and +/-Inf float values raised an error when replicating to Databricks. [T-872905] GOOGLE BIGQUERY: FIXED BURST STRING CONTROLS FOR BIGQUERY To fix this bug, upgrade HVR on the integrate machine(s). This fixes the generation of string controls for Burst Integrate for BigQuery. [T-876031] GOOGLE BIGQUERY: ALLOW NAN/INF VALUES IN FLOAT COLUMNS WHEN REPLICATING TO BIGQUERY To fix this bug, upgrade HVR on the integrate machine(s). Fixed a bug where NaN and +/-Inf float values raised an error when replicating to BigQuery. [T-873078] KAFKA: FIXED DATATYPE ERROR DURING SLICED REFRESH TO KAFKA To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where datatype errors occurred when performing a sliced refresh to Kafka with specific slice selections. T-762287 [T-828238] ORACLE: FIX LOOPBACK WHEN CASE-SENSITIVITY IS ENABLED. To fix this bug, upgrade HVR on the capture and agent machine(s). The internal loopback adapter's functionality to ignore deletions is not working correctly for Oracle source locations with enabled case-sensitive names. [T-863796] ORACLE: REVERTED TO ZLIB DUE TO ISSUES WITH ZLIB-NG To fix this bug, upgrade HVR on all machine(s). Reverted to the zlib library due to issues with zlib-ng causing segmentation faults. [T-866950] ORACLE: FIXED F_JG220F PROCEDURE 'SCANORADBENROLL' ENCOUNTERED UNEXPECTED OPTION To fix this bug, upgrade HVR on the capture machine(s). Fixed a bug wherein the scalar context of the DbOraScanEnroll FProc threw an error when it encountered the -c flag in the enroll. This bug arose after the changes made in T-578960 which added the -c flag to enrollment but did not correctly handle it during the validity check. T-578960 [T-870029] POSTGRESQL: FIXED MEMORY LEAK IN POSTGRESQL LOOP DETECTION To fix this bug, upgrade HVR on all machine(s). Fixed a memory leak that occurred during loop detection in PostgreSQL when using the pgoutput output decoding plugin. T-840569 [T-862244] SAP NETWEAVER: FIXED F_JD200A SEGMENTATION FAULT ERROR WHEN ACTIVATING ORACLE SOURCE DATABASE To fix this bug, upgrade HVR on the capture and agent machine(s). Fixed an issue where a segmentation fault (error F_JD200A) occurred when activating an Oracle source database. [T-864118] SQL SERVER: FIXED F_JD1A16 FOR SQL SERVER BACKUPS WITH TDE OPTIMIZED COMPRESSION To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where reading from some SQL Server Backups created with TDE and Optimized Compression errored out with F_JD1A16. [T-866198] SNOWFLAKE: ALLOW NAN/INF VALUES IN FLOAT COLUMNS WHEN REPLICATING TO SNOWFLAKE To fix this bug, upgrade HVR on the integrate machine(s). Fixed a bug where NaN and +/-Inf float values raised an error when replicating to Snowflake. [T-853916] SYBASE ASE: FIXED SYBASE ASE LOG READER HANDLING OF LOG PAGE ROLLOVER To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where the Sybase ASE Log Reader incorrectly flagged log corruption during transaction log rollover. This fix ensures that wrapped log pages are now handled correctly. [T-861790] SYBASE ASE: RESOLVED SEGMENTATION ISSUE WITH SYBASE ASE AS REPOSITORY DATABASE To fix this bug, upgrade HVR on the hub machine(s). Fixed a segmentation issue that could occur when Sybase ASE was used as the repository database. [T-862025] SYBASE ASE: IMPROVED ERROR HANDLING FOR BEGIN OPERATION PAGE NUMBER MISMATCH To fix this bug, upgrade HVR on the capture machine(s). In this change, the check to ensure the page number inside the `BEGIN` operation matches the page number in the header has been moved to mandatory checks. This means the number of retries for this check is now controlled by `HVR_SY_READ_CORRUPT_PAGE_MAX` (instead of `HVR_SY_READ_CORRUPT_OPERATION_MAX`). If the maximum number of retries is reached, the system throws a continuable error `F_JZ270A` instead of `W_JZ1D03`. [T-876052] SYBASE ASE: FIXED ERROR MESSAGE F_JZ0C27 FOR COMPRESSED TRANSACTION LOG RECORDS To fix this bug, upgrade HVR on the capture machine(s). Updated error message F_JZ0C27 to clearly differentiate between fully compressed dump files, which are supported, and transaction log files with compressed records, which are not supported. [T-844023] UI: FIXED UI ISSUE HIDING 'MERGE INTO TARGET' FOR BIGQUERY REFRESH To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where the 'Merge Into Target' option was unavailable in the Refresh Data dialog for BigQuery targets. NEW FEATURES IN HVR 6.2.5/2 (2025-01-14) ---------------------------------------- [T-200332] SUPPORT FOR SINGLE SIGN-ON TO HVR HUB THROUGH SAML To use this feature, upgrade HVR on the hub machine(s). Integrates Single Sign-On using SAML when authenticating HVR users in the Hub Server. This means HVR users can be configured to depend on 3rd party SSO providers for authentication. The system is designed to be flexible, and has been tested with Microsoft Entra, Google and Okta. The requires manual configuration through the CLI, please refer to the documentation on how to set this up. T-563985 T-824210 [T-718241] ADDED ADAPTDDL /ONADDCOLUMNWITHDEFAULT To use this feature, upgrade HVR on all machine(s). Added the capability to customize behavior when AdaptDDL detects new columns with default values using the new AdaptDDL parameter /OnAddColumnWithDefault. The available options are: * ADD_COLUMN_WITH_EMPTY_DEFAULT: Maintain the default behavior where no distinction is made between columns with and without default values. * REFRESH: Always refresh the table, replacing the data ensuring the source default value is in the target. * FAIL_INTEG_JOB: Send a breakpoint control to all involved Integrate jobs. Once all changes up to the DDL sequence are integrated, the control will cause the Integrate job to fail with an error. The issue must then be solved manually, and the control must be removed manually. * WARNING: Perform the same behavior as ADD_COLUMN_WITH_EMPTY_DEFAULT but issue a warning. Supported source databases include Oracle, SQL Server, Db2 for Linux, Unix, and Windows, Db2 for i, Db2 for z/OS, PostgreSQL, MySQL, and Sybase ASE. [T-791634] UPDATE OPENSSL AND RELATED LIBRARIES TO THE HVR VERSION. To use this feature, upgrade HVR on all machine(s). This change updates OpenSSL and related libraries to the HVR version. After this change, the OpenSSL version in HVR will include an `_HVR` prefix. For example, `OPENSSL_3.0.0` will become `OPENSSL_HVR_3.0.0`, preventing any conflicts with the system's OpenSSL libraries. [T-824210] ADDED HUBSERVER PROPERTY PUBLIC_HOST To use this feature, upgrade HVR on the hub machine(s). Added HubServer property Public_Host, which can be used for indicating what public hostname the HubServer is reachable from by a user. This interacts with the HTTPS certificates and e.g. SAML configurations. [T-853368] BUNDLE FIVETRAN PROXY 1.0.22 To use this feature, upgrade HVR on all machine(s). Upgrade bundle Fivetran Proxy to 1.0.22 [T-827322] AZURE DATA LAKE STORAGE: IMPROVED PERFORMANCE FOR READ/WRITE OPERATIONS FOR AZURE ADLS2 To use this feature, upgrade HVR on the hub machine(s). Improved performance by fixing a slow read/write issue for Azure SDK. [T-844978] AZURE DATA LAKE STORAGE: REDUCED PERMISSIONS NEEDED FOR USING AZURE FS To use this feature, upgrade HVR on the hub machine(s). HVR now supports handling the 403 Unauthorized exceptions, reducing the permissions required for Azure integration. You no longer need to assign the Storage Account Contributor role to enable functionality. [T-848830] DATABRICKS: ADDED SUPPORT TO RECONNECT TO DATABRICKS WHEN THE SESSION GETS INVALIDATED To use this feature, upgrade HVR on the integrate machine(s). Added support to reconnect to Databricks when the session gets invalidated. [T-821229] INGRES: ADDED SUPPORT FOR INGRES 12.0 To use this feature, upgrade HVR on all machine(s). Added support for Ingres 12.0. [T-771715] MYSQL: ADDED NATIVE SUPPORT FOR JSON DATA TYPE IN MYSQL To use this feature, upgrade HVR on the integrate, capture and hub machine(s). We have added native support for the MySQL JSON data type. Previously, we supported JSON as an extended data type. [T-851665] ORACLE: IMPLEMENT LOB PREFETCHING ON SESSION WIDE LEVEL To use this feature, upgrade HVR on the integrate and capture machine(s). This change allows you to configure the LOB prefetch size for Oracle databases at the session level. The new environment variable HVR_ORA_LOBPREFETCH_SIZE enables setting a prefetch size that applies to all LOB columns (CLOB, BLOB, NCLOB and BFILE) in replicated tables. To maintain the current behavior, avoid modifying the new environment variable, and you will see no changes in your workflow. With this setting on, you'll avoid doing a roundtrip between HVR and your Oracle DB, as long as the LOB object in this specific row is smaller or equal in size (expressed in characters, not bytes) to HVR_ORA_LOBPREFETCH_SIZE. This change is available for Oracle versions 19.0 and newer. [T-816256] POSTGRESQL: DO NOT ALLOW TEST_DECODING OUTPUT PLUGIN FOR POSTGRES 17 OR YUGABYTE To use this feature, upgrade HVR on the capture machine(s). Logical replication output plugin `test_decoding` is not allowed for PostgreSQL 17 or later or any version of YugabyteDB. Please use the default plugin: - `pgoutput` for PostgreSQL - `yboutput` for YugabyteDB [T-840569] POSTGRESQL: ADDED LOOP DETECTION SUPPORT FOR POSTGRESQL WITH PGOUTPUT PLUGIN To use this feature, upgrade HVR on all machine(s). This feature improvement enables support for loop detection and recapturing management using session names for PostgreSQL with the pgoutput output decoding plugin. This feature leverages PostgreSQL's replication progress tracking and replication origins to enable loop detection in cascade and bi-directional replication scenarios. Use of functions for replication origin is only allowed to the superuser by default, but may be allowed to other users by using the GRANT command. HVR sends a warning message when permission is not granted for pg_replication_origin_create() function at the beginning of replication progress tracking. [T-853242] POSTGRESQL: SUPPORT SETTING CUSTOM PUBLICATION NAME THROUGH LOCATION PROPERTY To use this feature, upgrade HVR on the capture and hub machine(s). Adds support for setting custom PostgreSQL PUBLICATION name through location property named `Publication_Name`. Removes support for setting custom PostgreSQL PUBLICATION name through environment variable `HVR_PUBLICATION_NAME`. [T-853355] SYBASE ASE: SUPPORT PASSWORD ENCRYPTION FOR ASE To use this feature, upgrade HVR on all machine(s). Password encryption for Sybase ASE is now supported. Two new location properties have been added to Sybase ASE locations: - `Enable Password Encryption`: When enabled, the connection property `CS_SEC_ENCRYPTION` is set to `true` during connection to the database. - `Enable Extended Password Encryption`: When enabled, the connection property `CS_SEC_EXTENDED_ENCRYPTION` is set to `true` during connection to the database. These properties are available in the HVR GUI and are only accessible when the `Authentication Method` is set to `User Name and Password`. PROBLEMS FIXED IN HVR 6.2.5/2 (2025-01-14) ---------------------------------------- [T-821848] FIX OCCURRENCE OF F_JG2305 DURING CAP_STATE CONVERSION To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where older versions of HVR5 generated a reduced cap_state file with insufficient fields for HVR6, causing the "F_JG2305: Attempt to fetch non-optional elements from a list that already is exhausted" error during cap_state conversion. This fix repairs the cap_state file by populating the missing fields with default values, ensuring compatibility with HVR6. [T-846162] FIXED F_JG2221 FOR ISOLATED TABLE REFRESH To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue for isolate table refresh `F_JG2221: Tag !pcontrol supplied to source-get-only pipe 'UnLZ4' without a source handle...` [T-852696] FIXED F_JG20CD DURING SNAPSHOT CREATION To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue affecting snapshot creation on Windows hubs with extended file paths. Previously, zipping the hub content would open excessive file handles, resulting in an F_JG20CD error. This fix resolves the issue by periodically closing and reopening the zip archive after every 100 files. - T-583853 - T-684900 [T-833817] AZURE DATA LAKE STORAGE: FIXED SIGSEGV WITH AZURE FS IN AZURE GOV CLOUD To fix this bug, upgrade HVR on the hub machine(s). A segmentation fault was happening during delete using azure us govenment cloud, now it is fixed. [T-821054] DATABRICKS: FIXED CONSISTENCY ISSUE WHEN USING HVR_STAGING_NULL_INDICATOR To fix this bug, upgrade HVR on the integrate machine(s). The environment variable HVR_STAGING_NULL_INDICATOR can be used to change the null indicator written to the CSV staging file from the default value of "\N". This is useful in cases where the "\N" string is a valid column value in the source. This fix addresses data inconsistencies introduced if the HVR_STAGING_NULL_INDICATOR environment variable is used with a BigQuery or Databricks target. [T-763638] INGRES: FIXED SEGMENTATION VIOLATION ERROR F_JT0287 (F_JG200A) FOR INGRES To fix this bug, upgrade HVR on the integrate machine(s). Resolved the F_JT0287 (F_JG200A) error that occurs when action Restrict with parameter IntegrateCondition is defined for Ingres, which also caused the Integrate job to fail. [T-851006] INGRES: FIX F_JD21B5 ON COMPARE/REFRESH WITH ABSENT COLUMN To fix this bug, upgrade HVR on the hub machine(s). Fix "F_JD21B5 DBMS error [Column ''###'' not found in any specified table]" for Ingres when running compare or refresh on table with absent column properties. [T-644743] ORACLE: FIXED LOG SCAN ERROR WHEN HVR COULD NOT FIND REDO COVERING SCN To fix this bug, upgrade HVR on the capture machine(s). Fixed log scan error when HVR could not find redo covering SCN [T-810525] ORACLE: FIXED DELAYED FILE REMOVING To fix this bug, upgrade HVR on the capture machine(s). Optionally treat file removal permission errors as a warning, allowing capture to continue and retry on subsequent capture cycles to remove archived logs. [T-833193] ORACLE: FIXED STRING FORMATTING THAT CAUSED IDENTIFIER LENGTH OVERFLOW To fix this bug, upgrade HVR on the capture machine(s). Fixed string formatting that caused identifier length overflow [T-834092] ORACLE: FIXED CONNECTION HANDLING FOR RAC WITH SCAN. To fix this bug, upgrade HVR on the capture machine(s). Fixed connection handling for RAC with SCAN. New environment variable was provided to use single connection. [T-834880] ORACLE: REDUCE NUMBER OF ROUNDTRIPS TO ORACLE DB WHILE SELECTING WITH TABLES WITH LOB COLUMNS To fix this bug, upgrade HVR on the integrate and capture machine(s). This change reduces number of roundtrips that HVR makes towards the Oracle DB while extracting LOB columns from an Oracle DB. [T-840488] ORACLE: FIXED ORACLE PARSER IN PARSING CERTAIN TYPE OF UPDATE REDO RECORD To fix this bug, upgrade HVR on the capture machine(s). This fix addresses Oracle LBC parser in parsing certain type of Update Redo Record that causes log scanning F_JZ196A error. [T-849129] SAP HANA: FIXED DUPLICATE INDEX NAME ERROR IN ADAPTDDL FOR HANA To fix this bug, upgrade HVR on the capture and agent machine(s). Fixed an issue where adding or removing a column from a HANA source table caused an AdaptDDL error F_JD0215: "cannot use duplicate index name". NEW FEATURES IN HVR 6.2.5/1 (2024-12-17) ---------------------------------------- [T-783428] UPDATED DATA TYPE HANDLING FOR TARGET DBMSES THAT DO NOT SUPPORT TIME DATA TYPE To use this feature, upgrade HVR on all machine(s). HVR now defaults to using a VARCHAR data type for target databases that do not support the TIME data type. Previously, in such cases, HVR defaulted to using a TIMESTAMP data type on a target. This updated behavior applies to newly created channels and to cases where you modify the table DDL. Existing channels will continue with their current replication behavior. For example, if an existing channel replicates the TIME data type as a TIMESTAMP on the target, it will keep doing so. However, if you recreate tables on the target using a refresh or the AdaptDDL action, the default will switch to VARCHAR. You can override this new behavior by using the ColumnProperties action with the DatatypeMatch and Datatype parameters. [T-830301] ADDED RESILIENCE TO UNKNOWN PROPERTIES AFTER DOWNGRADE To use this feature, upgrade HVR on the hub machine(s). After a downgrade of HVR, there may be properties in the repository database or in files on disk. An older version of HVR will throw validation errors on unknown properties. This fix will instead print a warning and ignore them. Since properties are validated in various places, and HVR spawns many processes, many warnings may come out. These are safe to ignore, but are important to log because just ignoring properties may or may not cause further issues. [T-708437] DATABRICKS: ADD AN OPTION TO USE PARQUET FILES FOR STAGING TO DATABRICKS To use this feature, upgrade HVR on the integrate and hub machine(s). If a target location uses staging for loading the burst table during integrate, or the target table during refresh, the rows are stagind in csv files. With this change an option has been added to the Databricks location configuration that allows the user to use parquet files for staging. The new option is in the Source and Target Properties section of the Databricks location configuration and is titled "STAGING FILE FORMAT". [T-729900] GOOGLE BIGQUERY: SUPPORT USING PARQUET FILES WHEN STAGING DATA TO BIGQUERY To use this feature, upgrade HVR on the integrate and hub machine(s). This feature adds support for staging data using Parquet files when loading data into BigQuery. By default, HVR uses CSV files for staging data into a target database. To ensure accurate replication of DATETIME data in BigQuery, the TZ environment variable must be set to match the time zone of your BigQuery data warehouse. When using Parquet files for staging, dates prior to the year 1583 (the Julian to Gregorian calendar switch) will not be replicated correctly. For all staging file formats, timestamp values with fractional seconds in years before 1698 or after 2242 may be reported as mismatches by Compare, due to a rounding error during data querying. [T-808387] KAFKA: ADDED ABILITY TO SEND KAFKA HEADERS WITHIN KAFKA MESSAGE To use this feature, upgrade HVR on the integrate and hub machine(s). This feature introduces a new behavior for Kafka message generation. Added a new "MessageHeaders" parameter in the "Integrate" action, which enables Kafka messages to include a header section. [T-662534] POSTGRESQL: ADDED SUPPORT FOR COPY STATEMENT WHEN CAPTURING DATA FROM POSTGRES To use this feature, upgrade HVR on the capture machine(s). This change adds support for using COPY statement when capturing data from PostgreSQL source. Environment variable HVR_PQ_SELECT_USE_COPY has been added and is enabled by default. Additionally, the default value of the environment variable HVR_PQ_SELECT_USE_CURSOR has been changed to 0. [T-764064] POSTGRESQL: ADDED AUTOMATIC CONVERSION TO PGOUTPUT FOR EXISTING CHANNELS To use this feature, upgrade HVR on the capture machine(s). HVR now automatically converts existing channels to `pgoutput` logical decoding output plugin without requiring reactivation or refresh. Publications and replication slots are managed seamlessly when the capture job starts. [T-785880] POSTGRESQL: ADDED SUPPORT FOR SETTING REPLICATION SLOT NAME To use this feature, upgrade HVR on the capture machine(s). This change adds the Replication_Slot_Name location property to override the replication slot name. Replication slots are used for PostgreSQL logical replication (Capture_Method=SQL). [T-805555] POSTGRESQL: DISABLED DIRECT CAPTURE METHOD FOR POSTGRESQL To use this feature, upgrade HVR on the capture and hub machine(s). HVR has discontinued support for the DIRECT capture method for PostgreSQL. [T-249606] SAP HANA: ADD SUPPORT OF SAP DATA TYPES D16/34N,TIMN,DATN,UTCL FROM SAP DICTIONARIES To use this feature, upgrade HVR on the integrate and capture machine(s). HVR introduced support of SAP HANA datatypes D16/34N,TIMN,DATN,UTCL from SAP Dictionaries. [T-202643] SNOWFLAKE: ADDED SUPPORT FOR TRANSIENT TABLES To use this feature, upgrade HVR on the integrate and hub machine(s). HVR now supports transient tables when integrating to Snowflake. When setting the `TransientTable` TableProperties action, the corresponding target tables will be created as transient tables. Note that this only affects newly created tables and tables that are re-created due to schema changes. Specifically schema changes that result in a `ALTER TABLE` statement will not change the table type. PROBLEMS FIXED IN HVR 6.2.5/1 (2024-12-17) ---------------------------------------- [T-766320] REMOVED REDUNDANT LOG MESSAGES FROM MERGE REFRESH To fix this bug, upgrade HVR on the integrate machine(s). Fixed some confusing log messages in merge refresh jobs. One redundant message was removed, and in another message a section was removed in case we don't have data to show there. [T-816245] FIXED "TIMESTAMP HAS UNEXPECTED FORMAT" IN HVRSTATS. To fix this bug, upgrade HVR on the hub machine(s). Made hvrstats more resilient against unexpected timestamp formats. Previously, the stats job threw an F_JG231B error: "Timestamp has unexpected format". The fix is to skip processing such lines, adding them to the irregular output lines. [T-817227] FIXED CRASH LIKE F_JT04C6 FOR SOFTDELETE CHANNELS To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue with Softdelete pipe injection where Softdelete pipe was injected once per table when customers used table_scope. [T-825975] FIX DUPLICATE ROW ERROR F_JD024D DURING INTEGRATION OF KEY CHANGE To fix this bug, upgrade HVR on the integrate machine(s). Fix duplicate row error F_JD024D during integration of multiple resilient key updates. [T-827122] FIXED F_JT1550 CRASH IN ORACLE ASM LOG-BASED CAPTURE To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue causing crashes in Oracle ASM log-based capture worker processes. The issue produced errors such as: `Nov 04 04:41:27: hub-cap-src[bc0]: F_JG2166: Unexpected I/O detected on link to parent job process Nov 04 04:41:27: hub-cap-src: F_JT1550: Coprocess 'bc0' terminated with signal 9.` The specific process name 'bcXXX' may vary, but will always start with 'bc', and this fix only applies to such cases. [T-838145] DATABRICKS: FIXED F_JD1202 WHEN USING REFRESH MERGE OPTION WITH DATABRICKS EXTERNAL TABLES To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue that occured when refreshing data into a Databricks table that has an external location, and where the refresh "Merge into Target" option is selected. [T-844400] DATABRICKS: FIXED F_JG2919 THROWN DUE TO A NEGATIVE STRING LENGTH To fix this bug, upgrade HVR on the integrate machine(s). Fixed 'F_JG2919: Encountered internal error while encoding string from' thrown due to a negative length. Note that this change also fixes 'F_JG2228: Unable to allocate' with a very large number of bytes reported. [T-840417] GOOGLE BIGQUERY: FIXED ISSUE WITH BIGQUERY WHEN DATASET AND BUCKET ARE IN MULTI-REGION EU To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where the error "F_JR1779 The BigQuery region 'EU' (from location property Bigquery_Region) is not the same as the discovered region 'eu-west-1' of the Google Cloud Storage" occurred when both the target dataset and the staging bucket were configured in the multi-region "EU". [T-811598] ORACLE: FIX DELETE ON ORACLE TABLE WITH EXTENDED VARCHAR2 COLUMN To fix this bug, upgrade HVR on the capture machine(s). This fix addressed a corruption on target table when Capture processed a delete operation on Oracle table with extended varchar2 column on a channel with soft-delete. The reason for the corruption is the inclusion of the LOB data header in the extended varchar2 data and the fix detects the extended varchar2 column and excludes the column data from the Delete record. [T-764064] POSTGRESQL: RESET CONNECTION INSTEAD OF STOP STREAMING REPLICATION To fix this bug, upgrade HVR on the capture machine(s). To improve handling of automatic conversion to the `pgoutput` output plugin for PostgreSQL, this change resets the connection instead of explicitly stopping streaming replication. It avoids potential error "no COPY in progress" with obsolete replication slot created for the `test_decoding` output plugin. [T-831999] SAP HANA: FIXED FALSE-POSITIVE THROWING F_JZ0A3F WHILE PARSING PARTIAL UPDATES FOR SAP HANA To fix this bug, upgrade HVR on the capture machine(s). Fixed F_JZ0A3F false-positive throwing when paritial update has more then 16 Million rows in one transaction. [T-793953] SQL SERVER: FIX CONNECTING TO AZURE SQL SERVER VIA OAUTH2 To fix this bug, upgrade HVR on the integrate and hub machine(s). Fixed an issue where HVR could fail with error F_JD21AE when attempting to connect to an Azure SQL Server using access tokens provided by OAuth2 authentication, due to incorrectly passing those credentials. Users facing either 'Login failed for user `` or `SPI Provider: No Kerberos credentials available` errors when connecting to an Azure SQL Server using OAuth2 authentication should upgrade to this version to resolve the issue. [T-826536] SYBASE ASE: FIXED READING OF PARTIALLY WRITTEN PAGES IN SYBASE BY ADDING CONSISTENCY CHECKS FOR RECORDS. To fix this bug, upgrade HVR on the capture machine(s). Fixed reading of partially written pages in Sybase by adding consistency checks for records. Added two additional checks while reading pages: 1. Page Number Consistency Check When the page number inside any record is higher than the current page number, it is considered a partially written page. The system will retry reading pages up to a maximum number defined by the environment variable `HVR_SY_READ_CORRUPT_PAGE_MAX` (default value: 10, maximum value: 255). If the number of retries reaches the maximum, an error `F_JZ1D02: The indicated page number ...` will be thrown, and the capture job will exit. 1. INSERT/DELETE/INSIND/DOL_INSIND Consistency Check Consistency of the page number and page timestamp within INSERT/DELETE/INSIND/DOL_INSIND operations is checked. If the page number or page timestamp of these operations is greater than the current page number or page timestamp, it is assumed to be a partially written page. Upon the first occurrence, a warning message, `W_JZ1D03: The indicated page number` ... or `W_JZ1D04: The page timestamp in the ...`, will be logged. The capture job will attempt to reread the page up to the maximum number of retries specified by the environment variable HVR_SY_READ_CORRUPT_OPERATION_MAX (default value: 10, maximum value: 255). If the maximum retries are reached without resolution, a warning `W_JZ1D05: Earlier, a record at address (%u, %hu) was encountered with an unexpected page number ...` will be logged, and the capture job will consider it a valid record and continue processing. [T-831523] SYBASE ASE: FIX THE OCCURENCE OF F_JZ270C - AN AFTER OPERATION IS SEEN BEFORE A BEFORE OPERATION To fix this bug, upgrade HVR on the capture machine(s). In some circumstances, UPDATEs to an "All Pages Locked" table will result in a fault similar to the following: `F_JZ270C: The [INSERT] record at (42156,10) will output a [update_after] operation, but the associated [update_before] operation has not been found.` This was due to a bug in identifying when update_before operations were output. As a result of this fix, the fault should no longer be observed. [T-833372] SYBASE ASE: FIXED THE OCCURRENCE OF F_JZ270C - DNOOP IS ALREADY MATCHED To fix this bug, upgrade HVR on the capture machine(s). In a scenario where a transaction affects multiple rows, we were encountering the error `F_JZ2709: The %s record at (%u, %hu)` in the logs. This occurred because the latest `DNOOP` was already matched with the previous `DELETE` record, but the `DNOOP` of the current `DELETE` record had not yet arrived. We mistakenly matched the `DNOOP` of the previous `DELETE` record with the current `DELETE` record. This issue has now been fixed. [T-837327] SYBASE ASE: FIXED THE OCCURRENCE OF F_JZ270A WHEN PAGE NUMBERS ARE REUSED AFTER ROLLING OVER TO OLD NUMBERS. To fix this bug, upgrade HVR on the capture machine(s). Fixed the occurrence of F_JZ270A when page numbers are reused after rolling over to old numbers. In addition, the following errors are now also continuable: `F_JZ0A91`, `F_JZ0A92`, and `F_JZ270A`. [T-833926] UI: FIXED THE REDEFINE BUTTON TO WORK ON VIEWS To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue with the Redefine button on the UI that caused it to fail when used on a database view. [T-846665] UI: FIXED SNOWFLAKE CLIENT PRIVATE KEY DIRECTORY OPENS IN STAGING DIRECTORY INSTEAD OF HUB DIRECTORY To fix this bug, upgrade HVR on the hub machine(s). Fixed a UI bug where specifying an integrate staging directory on Snowflake caused the "CLIENT PRIVATE KEY" in "Database Connection" to open the integrate staging directory instead of the hub directory. NEW FEATURES IN HVR 6.2.5/0 (2024-11-21) ---------------------------------------- [T-200579] ADDED ABILITY TO CREATE ISOLATE TABLE REFRESH To use this feature, upgrade HVR on all machine(s). Allow users to create isolate table refresh for either refresh events initiated by the users or refresh events created as part of an AdaptDDL operation. User-initiated refresh events that are created without isolation, would result in all relevant integ jobs to be suspended until the refresh completes. However, isolate table refresh, would keep integ jobs working on all tables that aren't part of the isolate table refresh. Once the isolate table refresh completes, integration of the isolated tables will continue. AdaptDDL-initiated refresh events, would result in the capture side to be waiting for the refresh to completes. However, isolate table refresh, would keep the capture side working on all tables (including the isolated tables), and make the integ side working on all tables that aren't part of the isolate table refresh. Once the isolate table refresh completes, integration of the isolated tables will continue. [T-306320] EXPOSE RESILIENT OPERATIONS IN ONLINE REFRESH. To use this feature, upgrade HVR on the integrate and hub machine(s). Currently we expose only a subset of hvr_ops in the {hvr_op} integrate expression. For tables with ColumnProperties /TimeKey, this can result in apparent duplicate rows. For example, if a row was inserted while an online refresh was executing. By returning the resilient hvr_op codes, the results in the target table can be more easily interpreted. Additionally, the compare function will work correctly with these codes, instead of throwing a 1+1 compare/coalesce error when this situation occurred. To turn on this new behavior, the HVR_EXPR_SUBST_HVR_OP_RESIL environment variable must be set to zero. The default behavior is to return the subset of hvr_ops as before, the user must opt-in to the new behavior with the environment variable. [T-732111] ADD THE ABILITY TO CUSTOMIZE {HVR_OP} VALUES To use this feature, upgrade HVR on the integrate and hub machine(s). Allow users to customize {hvr_op} values by creating a ColumnProperties action with the following parameters * /IntegrateExpression={hvr_op_str [custom mapping]} /Extra /Datatype=char /Length=2 * E.g. /IntegrateExpression={hvr_op_str 0>D;1>I;2>U} /Extra /Datatype=char /Length=2 * Or /IntegrateExpression={hvr_op_str} /Extra /Datatype=char /Length=2 * In this case, since the user doesn't define a custom mapping, we will use the default mapping which is 0>D;1>I;2>U;3>K;4>4;5>T DataType can be char or varchar. If an hvr_op value is not part of the mapping, it won't be mapped to anything but it will be used as is. Since hvr_op can be a double-digit number, the ColumnProperties parameter /Length should be no less than 2. [T-801413] UPGRADED BUNDLED FIVETRAN PROXY TO 1.0.20 To use this feature, upgrade HVR on the agent machine(s). Upgraded bundled Fivetran Proxy to 1.0.20 [T-821955] BUNDLE FIVETRAN PROXY 1.0.21 To use this feature, upgrade HVR on the agent machine(s). Upgraded bundled Fivetran Proxy to 1.0.21 [T-771320] DATABRICKS: ADDED SUPPORT TO USE GOOGLE CLOUD STORAGE AS STAGING To use this feature, upgrade HVR on the integrate and hub machine(s). Added support to use Google Cloud Storage as staging for Databricks. Make sure the Databricks cluster is properly configured to access the corresponding Google Cloud Storage bucket(s). [T-775861] DATABRICKS: ADDED SUPPORT FOR BC DATES IN DATABRICKS TIMESTAMP To use this feature, upgrade HVR on the integrate and hub machine(s). This change adds support for BC (Before Christ) dates in the Databricks TIMESTAMP data type. [T-763648] DB2 FOR I: ADDED SUPPORT FOR XML DATA TYPE To use this feature, upgrade HVR on all machine(s). HVR now supports the XML data type in Db2 for i. [T-763650] DB2 FOR I: ADDED SUPPORT FOR ROWID DATA TYPE To use this feature, upgrade HVR on all machine(s). HVR now supports the ROWID data type in Db2 for i. [T-763651] DB2 FOR I: ADDED SUPPORT FOR DATALINK DATA TYPE To use this feature, upgrade HVR on all machine(s). HVR now supports the DATALINK data type in Db2 for i. Note that only the URL is replicated. Any embedded comment is ignored. [T-805110] DB2 FOR I: ADDED SUPPORT FOR BINARY DECIMAL PHYSICAL FILE DATA TYPE To use this feature, upgrade HVR on all machine(s). HVR now supports the BINARY DECIMAL (B, BINDEC) data type in Db2 for i. [T-789914] GOOGLE BIGQUERY: ENABLE PARALLEL SLICED REFRESH FOR BIGQUERY To use this feature, upgrade HVR on the hub machine(s). This change enables running a sliced bulk load refresh in parallel when the target is BigQuery [T-766016] ORACLE: ADDED SUPPORT FOR CONFIGURABLE LOB PREFETCH SIZE To use this feature, upgrade HVR on the integrate and capture machine(s). This change allows you to configure the LOB prefetch size for Oracle databases at the session level. The new environment variable HVR_ORA_LOBPREFETCH_SIZE enables setting a prefetch size that applies to all LOB columns (such as CLOB and BLOB) in replicated tables. To maintain the current behavior, avoid modifying the new environment variable, and you will see no changes in your workflow. This change is available for Oracle versions 12.2 and newer. [T-779320] ORACLE: ENABLED CONCURRENT CHANNEL READING FROM SINGLE ORACLE DATABASE USING BFILE To use this feature, upgrade HVR on the capture machine(s). This improvement allows multiple channels to read from the same Oracle database using BFILE. Previously, each channel required a separate BFILE directory path to avoid conflicts when accessing archived sequences from ASM. This update automatically adds a unique pre/suffix to files, enabling multiple channels to safely read concurrently within a single BFILE directory path. [T-784052] ORACLE: OPTIMIZED ONE OF THE QUERY USED IN HVRADAPT FOR ORACLE To use this feature, upgrade HVR on the capture machine(s). This improvement optimizes one of the Oracle query used in hvradapt for getting the supplemental logging setting of a list of tables using the HVR_SYS_TAB that could take a considerable amount of time to complete, resulting in a huge delay in adding tables to the channel. [T-810525] ORACLE: OPTIONALLY TREAT PERMISSIONS ERROR ON FILE REMOVING AS A WARNING To use this feature, upgrade HVR on the capture machine(s). Optionally treat permissions error on file removing as a warning to allow capture to continue [T-662172] POSTGRESQL: SUPPORT YUGABYTEDB WITH LOGICAL REPLICATION CAPTURE METHOD To use this feature, upgrade HVR on all machine(s). Add support for YugabyteDB release starting 2024.1.1.0 where PostgreSQL Logical Replication Protocol Support is added. Add YugabyteDB as an option of source and target location type on UI. Add support for YugabyteDB exclusive REPLICA IDENTITY option CHANGE. Set default isolation level to REPEATABLE READ for YugabyteDB. [T-683294] POSTGRESQL: ADDED SUPPORT FOR POSTGRESQL LOGICAL REPLICATION WITH `PGOUTPUT` PLUGIN To use this feature, upgrade HVR on the capture machine(s). This new feature enables support for PostgreSQL logical replication with `pgoutput` plugin, which is the standard decoding output plugin alongside `test_decoding`, currently supported by HVR. `pgoutput` plugin has to work with publication management, allowing us only receive selected tables from PostgreSQL logical replication stream and improving overall capture performance. Please note that loopback detection with `pgoutput` is not available yet. [T-683297] POSTGRESQL: ADDED OPTION FOR MANAGING PUBLICATIONS FOR POSTGRESQL DATABASES To use this feature, upgrade HVR on the capture and hub machine(s). This update enables management of publications in PostgreSQL databases used as source locations. - Added a checkbox to the Activate Replication dialog for enabling/disabling publication management. - Introduced the option `-u` in the hvractivate command that enables the creation of a publication if it does not already exist. - Only selected tables are added to publications. - T-683297 - T-728737 - T-728743 - T-728747 - T-754211 [T-705418] POSTGRESQL: REMOVE STREAMING REPLICATION ALTERNATIVE IMPLEMENTATION To use this feature, upgrade HVR on the capture machine(s). HVR SQL capture for PostgreSQL has an alternative implementation to consume logical decoding changes using SQL level functions. This is enabled by setting HVR_PQ_USE_STREAMING_REPLICATION to 0. This implementation is inefficient and has many problems. This has been deprecated and made not necessary for any supported PostgreSQL version in HVR 6.1.5 releases. We are removing it altogether in 6.2.5. Complete list of removed settings by this change: - HVR_PQ_USE_STREAMING_REPLICATION - HVR_PQ_USE_REPLICATION_SLOT_ADVANCE - HVR_PQ_LOG_CURS_PREFETCH - HVR_PQ_LOG_READ_PAGE_GROUP [T-764063] POSTGRESQL: STOP USING TEST_DECODING AS DEFAULT PLUGIN To use this feature, upgrade HVR on the capture machine(s). Stop using test_decoding as default plugin when to create new channels, pgoutput plugin will be used. The default value of environment variable HVR_PQ_USE_TEST_DECODING is 0. [T-780218] POSTGRESQL: DISABLE HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL BY DEFAULT To use this feature, upgrade HVR on the capture machine(s). This change disables HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL by default for all versions of PostgreSQL. [T-780241] POSTGRESQL: DROP SUPPORT FOR POSTGRESQL 9.5 To use this feature, upgrade HVR on all machine(s). This change removes support for PostgreSQL 9.5. [T-800574] POSTGRESQL: ADDED SUPPORT FOR SETTING POSTGRESQL PUBLICATION NAME To use this feature, upgrade HVR on the capture machine(s). This change adds the HVR_PUBLICATION_NAME environment variable to override the publication name. [T-801374] POSTGRESQL: REMOVED FORCED TIMEOUT IN STREAMING REPLICATION To use this feature, upgrade HVR on the capture machine(s). HVR no longer forces timeouts in streaming replication for PostgreSQL versions 12 and earlier. Timeouts were needed to handle limitations that existed before the HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL setting. Now that this setting is available and disabled by default, this change simplifies the decision process and eliminates the need for special handling of older PostgreSQL versions. No additional user actions are required. [T-812232] POSTGRESQL: ADDED SUPPORT OF YBOUTPUT PLUGIN FOR YUGABYTEDB LOGICAL REPLICATION To use this feature, upgrade HVR on the capture machine(s). This new feature enables support for YugabyteDB logical replication with `yboutput` plugin, in addition to the existing support of `test_decoding` plugin. And by default it uses `yboutput` plugin. `yboutput` plugin has to work with publication management, allowing us only receive selected tables from YugabyteDB logical replication stream and improving overall capture performance. PROBLEMS FIXED IN HVR 6.2.5/0 (2024-11-21) ---------------------------------------- [T-689331] FIXED INCORRECT PROCESSING OF HANA UTCL DATATYPE, IMPROVED ERROR HANDLING To fix this bug, upgrade HVR on the capture machine(s). Replace SAP transport files with newest version. Delivers fixes to for T-689331 and T-734793: Fixed incorrect processing of SAP Hana UTCL datatype for Netweaver driver; Correctly sends error reports in case of SQL processing [T-778063] FIXED RESILIENT INTEGRATE OF NON-KEY COLUMNS WHEN A ROW WAS DELETED AND THEN INSERTED WITH THE SAME KEY To fix this bug, upgrade HVR on the integrate machine(s). Fixed resilient integrate of non-key columns when a row was deleted and then inserted with the same key. See also T-679974, which resolved this case only for key columns. [T-778090] FIX 'TRUNCATE' SUPPORT FOR POSTGRES TIMEKEY TABLES To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where error F_JD2313 was thrown on refresh after a truncate on a timekey channel for Postgres. T-597752 - Fixed a similar issue for Redshift [T-784898] FIXED F_JR4328 WHEN IMPORTING CHANNEL WITH ENCRYPTED TDE CERTIFICATES To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where channel import would fail with error F_JR4328 if the channel contained a location with a TDE certificate and was exported using encryption with a transport key. The error was caused by a premature validation of the certificate's private key and is now eliminated by skipping the certificate validation if the private key is encrypted. [T-791278] FIXED ERROR F_JG2142 WHEN REPLICATING FROM SAP HANA To fix this bug, upgrade HVR on the integrate machine(s). Fixed error F_JG2142 when performing a DELETE operation during replication from SAP HANA. [T-791280] FIXED F_JR0A0E WHEN ACCESSING ENCRYPTED SQL SERVER LOCATIONS To fix this bug, upgrade HVR on the hub machine(s). Fixed F_JR0A0E errors that occurred when accessing encrypted SQL Server locations after upgrading to OpenSSL 3. The issue was caused by missing ciphers that were moved to a legacy module in OpenSSL. This fix now packages the legacy module with HVR, eliminating the dependency on the hub machine having a separate OpenSSL installation. [T-794592] FIXED F_JR032D DURING HVRDEFINITIONIMPORT FOR CASE-INSENSITIVE ACTION NAMES To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where error F_JR032D could be triggered during hvrdefinitionimport if the action name was correct but the case did not match. This could only occur when users manually created definition JSON data or migrated manually edited HVR 5 hub database. It is recommended to use canonical ActionName capitalization when creating a definition JSON or to sanitize JSON data migrated from a manually edited HVR 5 hub. [T-795635] FIXED FALSE DIFFERENCES IN ONLINE COMPARE WITH CUSTOM TASK NAME To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue where correct behavior of online compare depended on the compare job using the default task name of "cmp". In some edge cases, compare jobs with custom task names could report incorrect results. [T-801179] FIX UNEXPECTED TIMESTAMP FORMAT WRITTEN BY CAPTURE JOB To fix this bug, upgrade HVR on the hub machine(s). Fixed capture writing timestamp in output file without timezone and in unexpected format (missing T). T-602157 [T-805282] FIXED INTEGRATEEXPRESSION PERFORMANCE OF CAST(CURRENT_TIMESTAMP() AS DATETIME) FOR BIGQUERY To fix this bug, upgrade HVR on the hub machine(s). Add `cast(current_timestamp() as datetime)` to the constsqlexpr.pat so whenever `cast(current_timestamp() as datetime)` is used in IntegrateExpression, there will be no performance overhead [T-810635] FIX INTEGRATEEXPRESSION NOT POPULATED FOR BEFORE-UPDATE RECORDS FOR SOFTDELETE FILE TARGETS To fix this bug, upgrade HVR on the hub machine(s). Fix IntegrateExpression not populated for before-update records for SoftDelete file targets [T-821576] FIXED F_JD5E12 (MISSING INPUT ENCODING FOR DATATYPE '106' DATALINK) WHILE RUNNING HVRDATATYPEMAP To fix this bug, upgrade HVR on the hub machine(s). This fixes hvrdatatypemap outputting mapping for data type datalink [T-826502] FIXED SIGSEGV CONDITION DURING CHANNEL ADAPT To fix this bug, upgrade HVR on the hub machine(s). A segmentation fault condition was present in the adapt code. This has been removed. [T-826645] FIXED SPACE IN HVR_HOME CAUSING F_JG057F WITH CONNECTION RESET BY PEER To fix this bug, upgrade HVR on the proxy and agent machine(s). Fixed space in %HVR_HOME% causing F_JG057F: TLS negotiation failed: I/O error occurred: Connection reset by peer. This fix specifically applies to a Connection reset by peer error: - When the customer has an HVR_HOME with whitespace in it - That exposes itself as F_JG057F: TLS negotiation failed, and explicitly not another F_J error code that may have the same underlying Connection reset by peer. [T-827139] ENFORCE MINIMUM SUPORTED DATABASE VERSION UPON CONNECTING To fix this bug, upgrade HVR on the integrate and capture machine(s). This bug fix forces a supported version check upon connecting to a database. If a database is not supported, the new error F_JT05DD is raised, with the suggestion to contact customer support. [T-830358] FIXED F_JG2459 IN HVRREFRESH AND HVRCOMPARE INVOCATIONS To fix this bug, upgrade HVR on the hub machine(s). Fixes F_JG2459: Get value of variable 'opt_E_is_time' failed. Variable not set. when calling hvrrefresh and hvrcompare on repository databases configured with overridden library environment (e.g. PostgreSQL_Pglib location property) [T-777038] DB2 FOR LINUX, UNIX AND WINDOWS: FIXED F_JD21B5 SQL0206N "TYPE" IS NOT VALID FOR TIME AND DATE COLUMNS WITH A DEFAULT DEFAULT To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue appearing during HVR activate with error code F_JD21B5 SQL0206N "TYPE" is not valid. This can happen for TIME and DATE columns with a default value of DEFAULT. [T-615210] DB2 FOR I: FIX F_JT0451 PIPE TXGROUP ENCOUNTERED A COMMIT WITH SEQUENCE <= EARLIER SEQUENCE ERROR WITH DST CHANGE ON DB2 FOR I SOURCE WITH DB2I_LOG_JOURNAL_SYSSEQ=TRUE To fix this bug, upgrade HVR on the capture machine(s). When capturing changes from Db2 for i with DB2i_Log_Journal_SysSeq=true, HVR used Db2 for i system sequence numbers to sort changes. Those system sequence numbers are, however, time based which causes problems when switching from summer time to winter time. HVR, therefore, will no longer use system sequence numbers to sort captured changes. Another way to sort captured changes will be used instead. That also allows handling of sequence number resets. [T-793972] DB2 FOR I: DB2 FOR I BY DEFAULT CAPTURES ALL MEMBERS BUT SETTING HVR_DB2I_MULTI_MEMBER_ALL=0 CAPTURES ONLY FIRST MEMBER To fix this bug, upgrade HVR on the capture machine(s). By default all members from DB2 for i multi-member files are captured. But setting environment variable HVR_DB2I_MULTI_MEMBER_ALL to 0 will lead to only first member being captured. Note that if HVR_DB2I_MULTI_MEMBER_ALL is set to 0 and tables which are in the channel are removed from the source database, then those tables should also be removed from the channel, otherwise the capture job will fail. [T-793790] DB2 FOR Z/OS: FIXED MEMORY LEAK DURING HVR ADAPT To fix this bug, upgrade HVR on the integrate and capture machine(s). This fix addresses a memory leak during HVR Adapt with Db2 for z/OS [T-785500] KAFKA: FIXED REGRESSION "TARGET UNKNOWN (0X80090303)" WHILE USING KERBEROS AUTHENTICATION ON WINDOWS PLATFORM To fix this bug, upgrade HVR on the integrate machine(s). Fixed "Target unknown (0x80090303)" while using Kerberos Authentication on Windows platform: - librdkafka used for communication with Kafka broker is rebuilt to correctly use UNICODE versions of SSPI WinAPI [T-761689] ORACLE: FIX FAILURE IN CONNECTING TO A NON-ACTIVE ORACLE DATA GUARD INSTANCE To fix this bug, upgrade HVR on the hub machine(s). This fix addressed a failure in capturing from a non-active Oracle Data Guard physical standby instance, which requires a sysdba privilege. The issue was introduced by T-632414 [T-790201] ORACLE: FIXED REGRESSION IN HANDLING REMOVED FILES WHEN SCANNING ARCHIVES To fix this bug, upgrade HVR on the capture machine(s). Fixed regression in handling removed files when scanning archives [T-802234] ORACLE: FIXED PREFIX FOR TEMPORARY FILES TO ALLOW CORRECT AGENTLESS USAGE To fix this bug, upgrade HVR on the capture machine(s). Fixed prefix for temporary files to allow correct agentless usage [T-822430] ORACLE: FIXED ADDITIONAL SLASH IN THE FRONT OF THE WINDOWS DIRECTORY NAME To fix this bug, upgrade HVR on the capture machine(s). Fixed additional slash in the front of the windows directory name. [T-723684] POSTGRESQL: FIXED SUPPLEMENTAL LOGGING FOR YUGABYTEDB To fix this bug, upgrade HVR on the capture machine(s). Supplemental logging will perform "ALTER TABLE ... REPLICA IDENTITY FULL" for regular PostgreSQL if REPLICA IDENTITY is set to DEFAULT. This fix ensures that the same logic applies to YugabyteDB when REPLICA IDENTITY is set to CHANGE, which is YugabyteDB's default setting. [T-795641] POSTGRESQL: FIXED ISSUE WITH RESTARTING STREAMING REPLICATION AT THE END OF WAL SERVICE To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where HVR would not correctly follow the WAL position (LSN) when the HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL setting was enabled. This defect could occur in specific rare workloads, potentially impacting replication reliability. The fix ensures that the streaming replication connection to PostgreSQL restarts correctly at the end of the WAL, as expected. [T-801613] POSTGRESQL: FIX TABLE NAMES ON PUBLICATION TO USE BASENAME To fix this bug, upgrade HVR on the capture machine(s). Fixed to use tables basename when setting tables on PUBLICATION. It was using table names on channel which could be different from basenames. T-683297 [T-805911] POSTGRESQL: ADDED SUPPORT FOR SETTING POSTGRESQL PUBLICATION NAME To fix this bug, upgrade HVR on the capture machine(s). This change stops HVR hub from trying to create PUBLICATION on unsupported agents. [T-806818] POSTGRESQL: FIXED PUBLICATION CREATION FOR TABLES WITH NON DEFAULT SCHEMA To fix this bug, upgrade HVR on the capture machine(s). This change fixes creation of PUBLICATION for tables that have non default schema. [T-812112] POSTGRESQL: FIXED F_JZ6227 TEST_DECODING MESSAGE TYPE To fix this bug, upgrade HVR on the capture machine(s). Fixed F_JZ6227 error when it failed to detect the "message" type emitted by `test_decoding` plugin of PostgreSQL logical replication. The hardcoded "message" keyword has been fixed to allow proper detection and handling. [T-814502] POSTGRESQL: ADD SINGLE PARTITIONS TO PUBLICATION FOR POSTGRES VERSION LESS THAN 13 To fix this bug, upgrade HVR on the capture machine(s). This fix adds partitions of the root table to the publication for PostgreSQL version prior to 13. [T-820616] POSTGRESQL: FIXED NON-KEY UPDATE FOR YUGABYTEDB'S YBOUTPUT PLUGIN To fix this bug, upgrade HVR on the capture machine(s). Fixed non-key update for YugabyteDB's yboutput plugin. With yboutput plugin, update before may contain old tuple with all columns unchanged, this fix resolved the error to replicate non-key update. [T-597752] REDSHIFT: FIXED TRUNCATE SUPPORT FOR TIMEKEY TABLES To fix this bug, upgrade HVR on the integrate machine(s). Redshift ODBC driver incorrectly reports not-null columns to be nullable. Then, HVR tries to insert nulls into these columns which results in error. In particular, this happens while replicating a 'truncate' statement on source table to target TimeKey table. [T-690300] SAP HANA: FIXED F_JD2288 WHILE PROCESSING OF HANA NATIVE DATATYPES DATE/TIME/TIMESTAMP To fix this bug, upgrade HVR on the integrate, capture and hub machine(s). Fixed getting trucated data from SAP Hana database like '0001-01-0'. Occured only if there are any LOB column in table definition. Correctly recognize SAP Time format 'HHMMSS' as a time. Correctly recognize SAP UTC Timstamp format 'YYYYMMDDHHMMSSsssssssss" as a timestamp [T-775324] SAP HANA: FIXED F_JZ0A4D AND F_JZ0A4E WHILE SEARCHING FOR HANA LOG BACKUPS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where the capture from HANA may fail with F_JZ0A4D or F_JZ0A4E. When searching for a HANA log backup, capture job checks backup catalog, primary location and alternate location in order. When a suitable log backup is not found but a newer than needed backup is found instead, capture job may have failed with either F_JZ0A4D or F_JZ0A4E error code prematurely before checking the other locations. [T-802201] SAP HANA: FIXED PROVIDING EMPTY CONFIGURATION PARAMETER VALUE FOR SAP HANA HDBBACKINT UTULITY To fix this bug, upgrade HVR on the capture machine(s). In case of using Microsoft backint implementataion (MSAWB) 'log_backup_parameter_file' value is not set in SAP Hana configuration. HVR ignores to use '-p' option for hdbbackint application if value is not provided neither in SAP Hana database nor in location configuration. [T-819323] SAP HANA: FIXED F_JZ0C0D DURING CAPTURE FROM SAP HANA To fix this bug, upgrade HVR on the capture machine(s). Fxied incorrect calculation expected LOB size. [T-691448] SAP NETWEAVER: FIXED DATATYPE MAPPING FOR THE HANA'S DECIMAL_FLOAT WHEN CONNECTING OVER NETWEAVER To fix this bug, upgrade HVR on the capture machine(s). When connecting to a HANA database over the NetWeaver, all HANA datatypes based on the DECIMAL_FLOAT internal datatype were incorrectly mapped to the HVR's internal datatype 19 (decimal), whereas it should be mapped to the HVR's internal datatype 8 (number). This may later lead to the capture job failing with the F_JZ0A33 error. This fix addresses this issue. [T-739543] SQL SERVER: FIXED SQL SERVER CAPTURE REWIND TO THE OLDEST TX WHEN SOME TABLES ARE NOT IN THE DEFAULT SCHEMA To fix this bug, upgrade HVR on the capture and hub machine(s). When looking for the beginning of the oldest running transaction on SQL Server, HVR only considers transactions that hold a lock on one of the tables in the channel. Due to a bug, owever, only tables in the source database's default schema were considered. This fix addresses the issue. The issue affects Activate with the "Rewind to Start of Source Databases' Oldest Transaction" option and Online Refresh with "Changes before refresh are skipped by both capture or integrate jobs" option. [T-816669] SQL SERVER: FIXED F_JD0A3D DURING CAPTURE FROM SQL SERVER To fix this bug, upgrade HVR on the capture machine(s). SQL Server log-based capture may fail with the F_JD0A3D error if one or more of the source tables contain DECIMAL SPARSE columns. This fix addresses the issue. [T-798206] SNOWFLAKE: FIXED LEAKING OF EXPIRED CREDENTIALS TO LOG FILE To fix this bug, upgrade HVR on the integrate machine(s). Fixed an issue where expired credentials are leaked into the logs. All credentials are now redacted when logging erroneous SQL queries. [T-690218] SYBASE ASE: ADDED MORE CHECKS TO HELP PREVENT READS OF PARTIALLY WRITTEN LOG PAGES WITH ASE LOG BASED CAPTURE To fix this bug, upgrade HVR on the capture machine(s). Since there is no coordination between Sybase ASE and HVR in the writing and reading of transaction log pages, HVR must perform various checks after reading a page to ensure it is self-consistent and that contents are as expected. Otherwise, HVR risks reading pages which are only partially written. This change introduces more page consistency checking while allowing a configurable number of inconsistencies when re-reading the same page before reporting a fault. This allows an opportunity for a partially written page to become completely written before a fault is reported. The number of re-reads is configurable using environment variable HVR_SY_READ_CORRUPT_PAGE_MAX. [T-710526] SYBASE ASE: FIXED F_JD0AD0 BY NOT MOVING THE TRUNCATION POINT IF THE START_ADDR IS "UNKNOWN" IN ASE To fix this bug, upgrade HVR on the capture machine(s). The truncation point is no longer moved if the start_addr is "unknown" in ASE. This avoids a F_JD0AD0 error being raised in this scenario. [T-717979] SYBASE ASE: ASE DIRECT CAPTURE - SCANNER ENCOUNTERED AFTER BEFORE BEFORE To fix this bug, upgrade HVR on the capture machine(s). NOOP/INOOP/DNOOP transaction log records were mishandled in some instances, causing the following error: `text F_JT0406: Scanner encountered 'after update' before the 'before update' change is ready` A combination of log records being mishandled is illustrated by this example of a single "deferred" UPDATE operation. ```text DNOOP 5373308, 1 (0x0051FD7C, 0x01) 01 01 0c 00 7b fd 51 00 0c 00 00 00 30 00 88 00 00 00 00 00 00 00 00 00 00 00 00 00 b6 e1 d4 5e 00 00 00 00 00 00 00 00 2b 50 39 00 07 00 00 dc NOOP 5373308, 2 (0x0051FD7C, 0x02) 01 02 0a 05 7b fd 51 00 0c 00 00 00 08 01 88 00 00 00 00 00 00 00 00 00 00 00 00 00 b6 e1 d4 5e 00 00 00 00 00 00 00 00 2f 07 4e 4e 58 36 37 30 37 37 20 23 db c3 ff 05 a2 b1 00 00 fa e4 bd 00 41 da c3 ff 05 db 00 4c 4f 41 4e 00 00 00 00 00 00 0c 40 4a 50 4d 34 32 32 30 30 37 45 53 46 53 45 43 9f a5 00 00 00 00 00 00 54 fe fb 05 b5 87 de 5e a9 99 8b 3f 82 b1 00 00 00 00 00 00 a6 b3 00 00 00 00 00 00 00 00 00 94 81 4a 98 41 4d 44 50 46 58 30 58 36 37 30 37 37 ba 49 0c 02 2b 07 10 40 45 53 46 53 45 43 6f 00 82 b1 00 00 00 00 00 00 82 b1 00 00 00 00 00 00 19 fc 08 00 78 00 7b 7c 01 00 4e 23 30 00 ce 02 a7 d2 46 00 63 f1 01 00 30 aa a6 a2 a0 9e 9d 9c 9c 9c 98 96 94 92 8a 82 82 80 7a 72 72 72 72 6c 6a 66 5e 56 56 56 56 56 56 4e 46 46 46 46 46 46 42 42 42 3a 34 2b 2b 23 1f 00 17 42 5f 2a DNOOP 5373308, 3 (0x0051FD7C, 0x03) Same content as DNOOP (5373308,5) 01 03 0c 00 7b fd 51 00 0c 00 00 00 30 00 88 00 00 00 00 00 00 00 00 00 00 00 00 00 b6 e1 d4 5e 00 00 00 00 00 00 00 00 92 ee 38 00 22 00 00 c6 INOOP 5373308, 4 (0x0051FD7C, 0x04) Same content as NOOP (5373308,6), References both DNOOP (5373308,3) and DNOOP (5373308,5) 01 04 0b 05 7b fd 51 00 0c 00 00 00 08 01 88 00 00 00 00 00 00 00 00 00 00 00 00 00 b6 e1 d4 5e 00 00 00 00 00 00 00 00 2f 22 4e 4e 58 36 34 45 30 42 20 23 c5 c1 ff 05 a2 b1 00 00 fa e4 bd 00 41 c4 c1 ff 05 db 00 4c 4f 41 4e 00 00 00 00 00 00 0c 40 4a 50 4d 34 31 33 31 39 35 45 53 46 53 45 43 dd a0 00 00 00 00 00 00 54 fe fb 05 62 23 bd 66 c1 dd b3 3f 82 b1 00 00 00 00 00 00 4e cb 00 00 00 00 00 00 00 00 00 a8 f8 f1 9d 41 4d 44 50 46 58 30 58 36 34 45 30 42 a8 c6 4b 37 89 41 10 40 45 53 46 53 45 43 5c 01 82 b1 00 00 00 00 00 00 82 b1 00 00 00 00 00 00 19 fc 03 00 68 01 63 06 08 00 4e 23 42 00 f7 02 a7 d2 46 00 6c 20 08 00 30 aa a6 a2 a0 9e 9d 9c 9c 9c 98 96 94 92 8a 82 82 80 7a 72 72 72 72 6c 6a 66 5e 56 56 56 56 56 56 4e 46 46 46 46 46 46 42 42 42 3a 34 2b 2b 23 1f 04 4f 06 10 00 DNOOP 5373308, 5 (0x0051FD7C, 0x05) Called out in error message. Same content as DNOOP (5373308,3) 01 05 0c 00 7b fd 51 00 0c 00 00 00 30 00 88 00 00 00 00 00 00 00 00 00 00 00 00 00 b6 e1 d4 5e 00 00 00 00 00 00 00 00 92 ee 38 00 22 00 00 c6 NOOP 5373308, 6 (0x0051FD7C, 0x06) Same content as INOOP (5373308,4) 01 06 0a 05 7b fd 51 00 0c 00 00 00 08 01 88 00 00 00 00 00 00 00 00 00 00 00 00 00 b6 e1 d4 5e 00 00 00 00 00 00 00 00 2f 22 4e 4e 58 36 34 45 30 42 20 23 c5 c1 ff 05 a2 b1 00 00 fa e4 bd 00 41 c4 c1 ff 05 db 00 4c 4f 41 4e 00 00 00 00 00 00 0c 40 4a 50 4d 34 31 33 31 39 35 45 53 46 53 45 43 dd a0 00 00 00 00 00 00 54 fe fb 05 62 23 bd 66 c1 dd b3 3f 82 b1 00 00 00 00 00 00 4e cb 00 00 00 00 00 00 00 00 00 a8 f8 f1 9d 41 4d 44 50 46 58 30 58 36 34 45 30 42 a8 c6 4b 37 89 41 10 40 45 53 46 53 45 43 5c 01 82 b1 00 00 00 00 00 00 82 b1 00 00 00 00 00 00 19 fc 03 00 68 01 63 06 08 00 4e 23 42 00 f7 02 a7 d2 46 00 6c 20 08 00 30 aa a6 a2 a0 9e 9d 9c 9c 9c 98 96 94 92 8a 82 82 80 7a 72 72 72 72 6c 6a 66 5e 56 56 56 56 56 56 4e 46 46 46 46 46 46 42 42 42 3a 34 2b 2b 23 1f 00 00 00 00 00 ``` DNOOPs are to be paired with INOOPs in forming the Before and After images of an UPDATE operation. Prior to this correction, the list of DNOOPs encountered was searched forwards to find a match for a given INOOP. In fact, the matching DNOOP for an INOOP seems always to be the immediately preceding operation so that this list should be searched backwards. In addition, after analysis, it seems that the NOOP records are being used to "cancel" the immediately preceding DNOOP records. Also, not illustrated, the INSIND record has been observed to be used to trigger the output of the Before and After images of a "deferred" UPDATE. Recently it has been shown that an INSERT record may be used instead of the INSIND for that same purpose. HVR now takes these insights into account in its log-scan activities. [T-717979] SYBASE ASE: FIXED FAILING UPDATE TO A PARTITIONED TABLE IN SYBASE ASE To fix this bug, upgrade HVR on the capture machine(s). Fixed failing UPDATE to a partitioned table in Sybase ASE whereby an UPDATE to a row moves it from one partition of the table to another. [T-720493] SYBASE ASE: ASE ARCHIVE LOG CAPTURE - BETTER HANDLING OF UNEXPECTED END-OF-FILE To fix this bug, upgrade HVR on the capture machine(s). When configured to read archived transaction logs, the ASE Capture job is unable to distinguish an archive that has been completely written from one that is in the process of being written. In the later case, the file may appear to be corrupted resulting in a failure message similar to the following: `F_JZ0C16: An unexpected end-of-file is encountered while trying to read 2048 bytes of data at an offset of 16384 bytes from the backup transaction log file 'my_tran_log_archive_1.trn'.` Eventually the job will restart and likely successfully read the archive upon a subsequent try. In an effort to more appropriately report the situation, with this change the capture job will now report a warning message similar to the following: `W_JZ2702: An unexpected end-of-file is encountered while trying to read 2048 bytes of data at an offset of 16384 bytes from the backup transaction log file 'my_tran_log_archive_1.trn'. Assuming a partially written file and will re-read shortly.` The capture job will report this warning for up to 5 times before reporting the failure, at which point the administrator may wish to stop the job and determine whether in fact, the archive file contains some corruption. [T-743384] SYBASE ASE: MORE THOROUGHLY CHECK FOR CONSISTENCY OF PAGES IN SYBASE TO AVOID READING PARTIALLY WRITTEN PAGES To fix this bug, upgrade HVR on the capture machine(s). In this change, Sybase transaction log pages are more thoroughly checked for consistency to avoid reading partially written pages. Two additional checks have been introduced while reading pages: 1. Page Number Consistency Check When the page number inside the `BEGIN` operation is not consistent with the page number in the header, a warning `W_JZ1D02: The indicated page number ...` will be logged. The system will retry reading pages up to a maximum number defined by the environment variable `HVR_SY_READ_CORRUPT_PAGE_MAX` (default value is 10, maximum value is 255). If the number of retries reaches the maximum, an error `F_JZ1D02: The indicated page number ...` will be thrown, and the capture job will exit. 1. Timestamp Regression Check Consistency of timestamps read from the logs is checked. If a timestamp regression is encountered (i.e., a new timestamp is older than a previously seen timestamp), it is assumed to be a partially written page. Upon the first occurrence, a warning `W_JZ1D00: Encountered a timestamp regression at address ...` will be printed. The capture job will retry reading the page up to the maximum number specified by the environment variable `HVR_SY_READ_TSTAMP_REGRESSION_MAX` (default value is 10, maximum value is 255). If the timestamp regression is resolved during the retries, a message `Earlier, a timestamp regression was encountered at address (%u,%hu), but it has been resolved ...` will be printed. If the maximum number of retries is reached without resolution, a warning `W_JZ1D01: Earlier, a timestamp regression was encountered at address (%u,%hu). It was not resolved after ...` will be logged, and the capture will assume it is a correct record and continue processing. [T-763583] SYBASE ASE: ASE DIRECT CAPTURE - DELETE RECORD FOR DNOOP RECORD IS NOT FOUND To fix this bug, upgrade HVR on the capture machine(s). INSIND records are used to "tie together" the Before and After images of some kinds of UPDATE operations. INSIND record processing makes adjustments for After images of UPDATEs but fails to account for Before images that may have been earlier produced, particularly when LOBs (and so ROWIMAGE records) are involved. With this change proper adjustments are made when processing INSIND records to account for the Before images of UPDATE operations and the user will no longer experience the error: `text F_JZ270B: The DNOOP record at (,) was expected to be matched to a DELETE record with data page and rowid (,), but that data row was not found.` [T-780679] SYBASE ASE: RESOLVED FAULT IN CAPTURING 'TRUNCATE TABLE PARTITION' OPERATIONS FOR SYBASE ASE To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where Sybase ASE Capture jobs would ignore executions of `truncate table partition` commands. Execution of these commands now correctly force a refresh of the table. It is recommended to check the consistency of any partitioned tables that may have had these commands executed against them. [T-782731] SYBASE ASE: FIXED INFINITE LOOP ON W_JZ1D00/W_JZ1D01 WARNINGS To fix this bug, upgrade HVR on the capture machine(s). Fixed infinite loop on W_JZ1D00/W_JZ1D01 warnings, which occurred during a sanity check of a page in Sybase ASE when multiple records on the page had timestamps earlier than the current timestamp. [T-799532] SYBASE ASE: FIXED CAPTURE LOG FLOODING CAUSED BY W_JZ1D00, W_JZ1D01, AND W_JZ1D02 WARNINGS To fix this bug, upgrade HVR on the capture machine(s). Fixed capture log flooding caused by W_JZ1D00, W_JZ1D01, and W_JZ1D02 warnings. [T-814303] SYBASE ASE: ASE DIRECT CAPTURE - DELETE RECORD FOR DNOOP RECORD IS NOT FOUND To fix this bug, upgrade HVR on the capture machine(s). A further correction on top of T-763583 which better supports deferred UPDATEs when LOB columns are involved. With this change proper adjustments are made when processing DNOOP records to account for the Before images of UPDATE operations when LOBs are involved and the user will no longer experience the error: `text F_JZ270B: The DNOOP record at (,) was expected to be matched to a DELETE record with data page and rowid (,), but that data row was not found.` [T-814453] SYBASE ASE: FIXED F_JT0268 IN A TRANSACTION THAT UPDATES MULTIPLE TABLES. To fix this bug, upgrade HVR on the capture machine(s). Fixed `F_JT0268` in a transaction that updates multiple tables. The issue occurred when a transaction affecting multiple tables triggered a special case: only the ROWIMAGE operation with status ZSY_RWI_XSTAT_WRITETEXT and ZSY_RWI_XSTAT_AFTER_IMAGE was logged for the first table, while the second table's operations were logged in the following order: DNOOP, INOOP, DELETE, and finally INSIND. The first ROWIMAGE caused us to emit `UPDATE_BEFORE`. Since we received DNOOP and INOOP for the second table before the DELETE operation, we did not emit anything on DELETE. Then, when INSIND occurred, we mistakenly believed `UPDATE_BEFORE` for this table had already been emitted, so we incorrectly emitted `UPDATE_AFTER`. NEW FEATURES IN HVR 6.2.0/0 (2024-09-25) ---------------------------------------- [T-763647] DB2 FOR I: ADDED SUPPORT FOR BOOLEAN DATA TYPE IN DB2 FOR I To use this feature, upgrade HVR on all machine(s). HVR now supports the BOOLEAN data type in Db2 for i. Note that some older Db2 for i ODBC drivers have limitations in describing BOOLEAN columns. As a result, HVR will coerce source data to CHAR(1) instead of BOOLEAN. Integrate will still work properly when the source data contains only valid BOOLEAN values, but it may result in: - integer values other than 0 or 1 get silently converted to 1. - a Db2 for i error "SQL0402" for non-integer values. Defining action TableProperties with CoerceErrorPolicy cannot prevent this behavior. [T-777706] POSTGRESQL: DROP SUPPORT FOR POSTGRESQL 9.4 To use this feature, upgrade HVR on all machine(s). This change removes support for PostgreSQL 9.4. PROBLEMS FIXED IN HVR 6.2.0/0 (2024-09-25) ---------------------------------------- [T-752851] FIXED CHANNEL ACTIVATION FAILING WITH F_JR0923 To fix this bug, upgrade HVR on the hub machine(s). Fixed channel activation failing with F_JR0923 even though ColumnProperties with parameter ExpressionScope has parameter Context set, since the Context should only affect refresh/compare, activation shouldn't have been impacted. This fix ensure that context is always considered during the activation checks for ExpressionScope. [T-755955] FIXED F_JX0021 IN SLACK ALERTS CAUSED BY IMPROPER ESCAPING To fix this bug, upgrade HVR on the hub machine(s). Fixed a bug in HVR Slack alerts. In a rare edge case, if the alert was truncated in such a way that left it ending with a backslash, it caused an F_JX0021 error. In addition, the system would fail in creating an event for the alert error because of bad escaping for backslashes and double quotes. This fixes both those problems. [T-761882] FIXED F_JT0D2C WHEN USING OPT-IN BEFORE IMAGE FOR SAP UNPACK To fix this bug, upgrade HVR on the integrate machine(s). Fixed `F_JT0D2C` when using opt-in before image for SAP unpack. Only applies for opt-in cases where `$HVR_SAP_UNPACK_USE_BEFORE` is set. Fixed the sorting of update pairs such that they are kept together when double sorting in some SAP unpack scenarios. [T-762287] IMPROVED DATA COMPARE WITH BOUNDARY SLICING FOR NON-NULLABLE DATATYPE To fix this bug, upgrade HVR on the hub machine(s). Fixed an issue the query of the last slice for data compare with range slicing did try to match for NULL values in its where clause for columns that where non-nullable. For some databases this lead to a full table scan. Now we do not match for NULL values for columns that are not nullable according to the channel definition. If the source database has a nullable key column, and the column is not nullable in the channel definition, the NULL key will now no longer be in any slice when using boundary slicing. [T-776910] FIXED THE DATA TYPE OF HVR_CAP_LOC COLUMN IN HISTORY TABLE To fix this bug, upgrade HVR on the hub machine(s). Fixed history table having hvr_cap_loc column as varchar(5) while it should have it as varchar(12) [T-784478] FIXED BURST TABLES IN CUSTOM SCHEMA ON ORACLE TARGET NOT DROPPING ON DEACTIVATE To fix this bug, upgrade HVR on the integrate machine(s). Fixed burst tables in custom schema on Oracle target not dropping on deactivate [T-784570] FIXED FAILING INTEGRATE ON MYSQL TARGET WITH CUSTOM BURST TABLE SCHEMA DEFINED To fix this bug, upgrade HVR on the integrate machine(s). Fixed failing integrate on MySQL target with Burst integrate and custom burst table schema defined. [T-778939] INGRES: FIXED F_JZ220A IN CASE OF UNEXPECTED TIMESTAMP To fix this bug, upgrade HVR on the capture machine(s). Implemented ZIZ_INGRES_Y2K38_USE_32BIT_TIMESTAMP to fix Ingres F_JZ220A in case of unexpected timestamp. This environment variable is used to choose either to ignore or not ignore the higher 4 bytes in the 8-byte timestamp value captured from Ingres log file. In case of ignore the date is limited by 2038 year. [T-597251] ORACLE: FIXED INVALID DATE WHILE TRYING TO CONVERT DATE TO NUMBER To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where HVR exception `F_JD20D7: Invalid date encountered while trying to convert date to number of seconds since 01.01.1970 for column` was thrown from an automated test. Issue is fixed now. Issue was introduced by: T-564881 [T-738837] ORACLE: IMPROVED ORACLE CHANGE CAPTURE FOR UNDO CHAINING To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where Oracle log parsing encountered the error - "F_JZ1122: Chained undo change vector does not have enough structures." This fix allows multiple undo segments to be collated, split blocks to be merged between segments, and ensures proper handling of straddling undo segments. Additionally, the `hvrlogdump` output is now consistent with Oracle's native dumping format. [T-767763] POSTGRESQL: ENHANCED ERROR REPORTING FOR DATABASE SUB-TRANSACTIONS To fix this bug, upgrade HVR on all machine(s). HVR could previously report an F_JD22D4 error without any accompanying details when it occurred within a database sub-transaction. This fix ensures that relevant error details are now included. [T-774367] POSTGRESQL: FIXED ENDING CYCLES IN THE BEGINNING OF CAPTURE To fix this bug, upgrade HVR on the capture machine(s). HVR PostgreSQL capture could fail to end the capture cycles when `HVR_PQ_STREAMING_REPLICATION_RESTART_AT_END_OF_WAL` is `1` which is currently the default for PostgreSQL versions below 16. This change fixes the problem. [T-779065] POSTGRESQL: FIXED ERROR F_JT0921 WHEN ADDING VIEWS TO CHANNEL To fix this bug, upgrade HVR on the hub machine(s). Fixed error F_JT0921 when adding views or materialized views to channel from PostgreSQL. This could be reproduced both on UI and CLI. [T-735358] SQL SERVER: FIXED MSSQL F_JD0A0E ERROR WHEN CAPTURING UPDATE TRANSACTIONS To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue where HVR could fail with error F_JD0A0E when capturing updates for LOB columns, even though those updates had been correctly integrated on the target during a prior capture cycle. [T-717979] SYBASE ASE: FIXED ERROR F_JT0406 WITH TRANSACTION LOG RECORD HANDLING To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue with the handling and pairing of NOOP, INOOP, and DNOOP transaction log records, which are used to form the before and after images of an UPDATE operation. Previously, mishandling these records in some instances caused the following error - "Error Code: F_JT0406 - Scanner encountered 'after update' before the 'before update' change is ready". The fix ensures that DNOOP records are correctly matched by searching backward for their corresponding INOOP records. Additionally, NOOP records are handled properly, canceling the preceding DNOOP records as expected. [T-763583] SYBASE ASE: FIXED ERROR F_JZ270B WHERE THE DELETE RECORD FOR DNOOP WAS NOT FOUND To fix this bug, upgrade HVR on the capture machine(s). Fixed an issue with INSIND record processing during Direct capture, which made adjustments only for After images of UPDATEs and failed to account for Before images that might have been produced earlier, particularly with LOBs and ROWIMAGE records. This issue caused the following error - "F_JZ270B: The DNOOP record at (,) was expected to be matched to a DELETE record with data page and rowid (,), but that data row was not found." This fix ensures that proper adjustments are now made for Before images of UPDATE operations. [T-775721] SYBASE ASE: FIXED REFRESH JOB FOR SYBASE TARGETS WITHOUT CASE-SENSITIVE NAMES. To fix this bug, upgrade HVR on the integrate machine(s). The `Refresh` job was failing for sources with Case-Sensitive Names enabled, and Sybase targets without Case-Sensitive Names. [T-757389] UI: FIXED MANAGED SECRETS OPERATION ON WINDOWS To fix this bug, upgrade HVR on the hub machine(s). Fixed Managed Secrets to use hvrmanagedpassword.bat script name on Windows. [T-775030] UI: FIXED UNEXPECTED ENVIRONMENT ACTIONS APPLIED IN TABLE SELECTION UI To fix this bug, upgrade HVR on the hub machine(s). Fixed unexpected Environment actions being applied when browsing DB schemas on table selection in UI, by passing channel name to the REST API. [T-777475] UI: FIXED REFRESH/COMPARE DIFFERENCE VIEWING PERMISSION REQUIREMENTS To fix this bug, upgrade HVR on the hub machine(s). Changed permission requirements from ReadExecRefresh to ReadExec for querying refresh/compare differences, as compare can be performed by a ReadExec user. [T-779939] UI: FIXED ALERTS NOT SAVING SMTP "SPECIFIC PORT" To fix this bug, upgrade HVR on the hub machine(s). An alert option "Specific Port" under "Advanced SMTP Configuration" section in UI could be cleared (removed, which also means resetting to the default value), if "Advanced SMTP Configuration" section is collapsed. This has been fixed.