Informatica® Data Replication 9.8.0 HotFix 1 Release Notes Informatica Data Replication Release Notes 9.8.0 HotFix 1 March 2019 © Copyright Informatica LLC 2019 Publication Date: 2019-03-26 Table of Contents Introduction..................................................................... iv Chapter 1: Installation and Upgrades......................................... 5 Chapter 2: Fixes.............................................................. 6 Chapter 3: Known Limitations................................................. 8 Chapter 4: Informatica Global Customer Support............................. 13 Table of Contents 3 Introduction This document contains important information about enhancements, fixes, and known limitations in Informatica Data Replication 9.8.0 HotFix 1. iv C h a p t e r 1 Installation and Upgrades For information about installing or upgrading Data Replication, see the Data Replication Installation and Upgrade Guide. 5 C h a p t e r 2 Fixes The following table describes fixed limitations: Bug Description IDR-4073 When the Oracle Extractor parses a chained or migrated row, it might incorrectly determine the type of a DML operation. For example, it might interpret an Update operation as a Delete. IDR-4068 For Microsoft SQL Server 2016 sources, the Extractor ends with the following error when processing an Update record: Could not convert character data from UTF16 to UTF8. This error can occur when null values are updated to non-null values. IDR-4052 If a ROLLBACK TO SAVEPOINT operation occurs on an Oracle source, the Applier might skip records that are not rolled back on the source when applying data to the target. IDR-4050 The DB2 Extractor does not capture values of primary key columns in Update records if these columns also belong to unique indexes for which DB2 DATA CAPTURE is not enabled. IDR-4044 If the endianness of the Oracle Extractor system differs from the endianness of the Oracle source system, the Extractor might skip a ROLLBACK operation. In this case, the Extractor might process the records that were rolled back, causing the Applier to end with an error. IDR-4003 For Oracle 12c sources that run in Oracle 11 compatibility mode, the Extractor ends with error message IDR-030811 when parsing a CREATE TABLE AS SELECT record. The error occurs only if replication of CREATE TABLE DDL operations is enabled in the configuration. IDR-3997 For Microsoft SQL Server 2016 sources, the Extractor prints error message IDR-020219 to the task execution log when processing a Delete record. IDR-3989 The Oracle Extractor might incorrectly process WHERE clauses for filtering source data. As a result, some records might not be excluded from Applier processing. IDR-3979 The SQL Server Extractor ends abnormally and generates a core file when processing records in backup transaction logs from tables that use row compression. IDR-3968, The Oracle Extractor might hang when it runs on UNIX and processes redo logs from an Amazon IDR-3864, Relational Database Service (RDS) for Oracle instance. IDR-3767 IDR-3966 The Microsoft SQL Server Extractor ends with a memory allocation error when processing an XML LOB column that contains a page with corrupted data. The corrupted data is caused by an allocation unit (ALU) cleaning operation that occurs after the LOB row is deleted. 6 Bug Description IDR-3955 An Applier that runs in continuous mode might not replicate a mapped table to a secondary target in an existing configuration that has multiple targets. The problem occurs if you previously excluded the table from replication. IDR-3914 The Applier ends with an error when applying DB2 TIME data to an Apache Kafka target. IDR-3897 The Oracle Extractor ends with an error when processing CREATE TABLE AS SELECT records from Oracle 18c sources. IDR-3892 The Oracle Extractor might fail to detect the 8-byte SCN format of Oracle 12c databases. As a result, the Extractor incorrectly reads the SCN values from redo log records and then cannot find records for extraction processing. IDR-3876, The Oracle Extractor might extract corrupted data from a chained row if columns in this row use Oracle IDR-3870, Transparent Data Encryption (TDE). IDR-3836 IDR-3861 A Server Manager subserver that is configured for HTTPS communication might stop responding when it receives a stop command. IDR-3856 InitialSync ends abnormally and generates a core file when loading varbinary(max) data from a Microsoft SQL Server source to Oracle BLOB columns. IDR-3851 The Server Manager might log the following error message after a successful backup of a replication configuration: The Server Manager could not open the configuration SQLite database 'database_file_name'. IDR-3849 The Server Manager does not adjust the Applier start point values for Audit Apply mappings after cleaning a replication configuration. IDR-3848 The Server Manager sets the Extractor start point to an incorrect SCN value after cleaning a replication configuration that has multiple targets. IDR-3847 The Data Replication Console does not show all of the logs for continuous schedules on the Event Viewer tab > Logs of Schedules view. IDR-3829 For replication configurations that have an Oracle source and target, the Applier ends with an error when applying CREATE TABLE records for large index-organized tables (IOTs) defined with the OVERFLOW TABLESPACE clause. IDR-3787 The SQL Server Extractor might end with the following error when processing a compressed backup log: MS SQL backup file is corrupted or backup format is not supported. IDR-3423 The Data Replication Console might display the following error message when connecting to a target database: This database type is not supported by Informatica Data Replication. 7 C h a p t e r 3 Known Limitations The following table describes known limitations: Bug Description IDR-3925 A MySQL Extractor task that runs in continuous mode and extracts data from a remote MySQL database server fails to create intermediate files that contain the extracted change data. As a result, no change data is sent to the target database. Workaround: Run the MySQL Extractor task on demand or schedule the task to run periodically. IDR-3157 For Vertica 9 targets, an Applier or InitialSync process that runs on Solaris might hang or end abnormally with a core file. Workaround: Install the DataDirect ODBC driver v.4.1.19 for Vertica targets. IDR-3056 For configurations that have an Oracle source and target, InitialSync performance becomes degraded when synchronizing tables that include LOB columns. This performance issue does not occur in Data Replication 9.7.0 HotFix 1. IDR-1843 For configurations that have a MySQL source and an Apache Kafka, Cloudera, Flat File, or Hortonworks target, the Data Replication Console allows you to map source columns that have unsupported data types, such as JSON or spatial data types. Mapped columns with unsupported data types cause the Extractor to end with an error. Workaround: In the Data Replication Console, do not map MySQL source columns with unsupported data types when you create a configuration that has an Apache Kafka, Cloudera, Flat File, or Hortonworks target. IDR-1680 For all source types, Data Replication does not support the use of non-Latin characters or special IDR-1670 characters in source object names. If these characters are used in object names, Data Replication tasks might end abnormally. (424492) IDR-1625 IDR-1611 IDR-589 IDR-1633 If you do not use InitialSync to materialize targets, either by choice or because InitialSync is not supported for the target type, Data Replication does not set the Sync Point from which the Applier starts applying change data to the targets. In this case, all of the data extracted from the current source log file that contains the Extractor Start Point is applied to the target, including data earlier than the synchronization point. For Apache Kafka, Cloudera, Flat File, and Hortonworks targets that do not use InitialSync, the Applier always applies all of the data extracted from the current source log file, unless you manually set the Sync Point for apply processing. Workaround: To avoid replicating all data from the beginning of the current source log file to targets for which the Sync Point was not generated during initial synchronization, manually set the Applier Sync Point for each mapped target table before starting the Apply task. 8 Bug Description IDR-1585 Data Replication cannot replicate change data or DDL operations for MySQL source columns with the unsigned FLOAT or DOUBLE data type to Oracle targets. You cannot map these columns in the Data Replication Console. Any DDL operation that adds or alters these columns is ignored. Workaround: For DDL changes, edit the DDL statements to omit the unsigned FLOAT or DOUBLE data types or change these data types to a supported data type. Then run the DDL statements on the target instead of using Data Replication to replicate the DDL changes. IDR-1552 For configurations that have Oracle sources and Apache Kafka, Cloudera, Flat File, Hortonworks, or Oracle targets, if a source column contains a TIMESTAMP WITH LOCAL TIMEZONE data type with a value of 0001-01-01, Data Replication might produce an invalid year value in the target column. Workaround: Substitute a virtual column for any date column that could have the value of 0001-01-01. For Apache Kafka, Cloudera, Flat File, or Hortonworks targets, use a Tcl expression to handle the condition. For Oracle targets, you can use a SQL script. For example, add 1 to the day if the column value could produce a year value of 0 in the target column after conversion to UTC, or substitute a null value or a hard-coded constant. Alternatively, filter out all source table rows that contain date values of 0001-01-01. IDR-1121 The Applier and InitialSync can run the ./support/tcl/dbs_worker_start.tcl and ./support/tcl/dbs_worker_end.tcl scripts only if the replication configuration includes one or more virtual columns with assigned Tcl scripts.