If Informatica Data Replication is not currently installed, complete a first-time installation. Otherwise, complete the upgrade procedure.

Transcription

1 Informatica Corporation Data Replication Version Release Notes August 2013 Copyright (c) 2013 Informatica Corporation. All rights reserved. Contents Introduction... 1 Installation and Upgrading... 1 Installing Data Replication for the First Time Upgrading Data Replication Closed Enhancement Requests... 3 New Features... 3 Fixes... 4 Known Limitations Informatica Global Customer Support Introduction This document contains important information about enhancements, fixes, and known limitations in Informatica Data Replication It also describes how to upgrade to Data Replication from an earlier release. Installation and Upgrading If Informatica Data Replication is not currently installed, complete a first-time installation. Otherwise, complete the upgrade procedure. Data Replication is supported on AIX, HP-UX, Linux, Solaris, and Windows operating systems. Installing Data Replication for the First Time Complete the standard installation procedure that is described in the Informatica Data Replication User Guide. IDR-RN

2 Upgrading Data Replication To upgrade to Informatica Data Replication from an earlier release back to 3.0, Informatica recommends that you extract or decompress the Data Replication installation file into the existing Data Replication installation directory. Retain the license key from the earlier Data Replication installation. Note: To upgrade to Informatica Data Replication from a release earlier than 3.0, contact Informatica Global Customer Support. If you run Data Replication on multiple systems, upgrade Data Replication on all of the systems. Do not run Data Replication on one system and run an earlier Data Replication release on another system in the same topology. 1. Transfer the platform-specific Data Replication installation file that you received from Informatica to a directory other than the existing installation directory on your system. Tip: Retain the installation file to upgrade other Data Replication instances or to redo an upgrade. 2. Stop all replication tasks and schedules. 3. Stop all Server Manager servers that are running under the earlier Data Replication version. If you are running the Server Manager as a service or a daemon, use the following commands to stop and remove the service or daemon: On Windows: cd %DBSYNC_HOME% server_manager.exe RUN_AS_SERVICE -k server_manager.exe RUN_AS_SERVICE -r On Linux and UNIX: cd $DBSYNC_HOME./server_manager.sh stop Then verify that the Server Manager daemon is not running. For example, you can use the following command: ps -eaf grep server_manager 4. Back up the existing Data Replication installation, including the intermediate files and replication configurations. 5. If you are upgrading from Data Replication 9.5.0, delete the following.jar files from the lib directory in the existing Data Replication installation: hadoop-core jar hadoop-core jar Note: Data Replication and contain conflicting versions of the Hadoop jar files. If you do not delete the earlier jar files, when you start the Data Replication Console, the console reports that it found multiple versions of the Hadoop library. 6. Copy the license key file, DbSync.key, to a temporary directory on the system. 7. Extract or decompress the installation file into the existing Data Replication installation directory: On Linux, decompress the DataReplication_9_5_1.linux.x86_64.tar.gz file. On Windows, extract the DataReplication_9_5_1.windows.32bit.zip file. Confirm that the files for the previous version in the Data Replication installation directory were overridden. 2 IDR-RN

3 8. Copy the license key from the temporary directory to the directory with the Data Replication installation. 9. If you installed a JDBC driver to a location other than the DataReplication_installation/lib earlier, edit the idr_console.cmd script (for Windows) or idr_console.sh script (for Linux and UNIX) to correctly specify the JDBC driver environment variables. Set the JDBC driver environment variables to point to the location of the JDBC drivers. Use the environment variables for your source and target database types that are described in the Informatica Data Replication User Guide. 10. Verify that the DBSYNC_HOME environment variable still points to the Data Replication installation. 11. Restart all of the Server Manager servers. If you are running a Server Manager instance as a service or a daemon, use the following commands to restart the Server Manager service or daemon. On Windows: cd %DBSYNC_HOME% server_manager.exe RUN_AS_SERVICE -i server_manager.exe RUN_AS_SERVICE -s On Linux and UNIX: cd $DBSYNC_HOME./server_manager.sh 12. Restart all of the replication tasks and schedules in Data Replication Closed Enhancement Requests The following table describes closed enhancement requests: The Data Replication Console includes an enhanced editor for creating SQL expressions. In the Insert an SQL Expression dialog box, you can use the data access operators in the Columns list box and the SQL comparison operator buttons in lower right corner to quickly define a SQL expression On the Map Tables tab of the Data Replication Console, you can now use wildcard expressions to map source tables and columns to target tables and columns. The wildcard expressions can include one or more asterisk (*) wildcard characters, each representing zero or more characters anywhere in the table or column names You can now specify a Start SCN value in a configuration to override the default point in the transaction logs from which the Extractor starts reading changes when you run the Extractor task for the first time From the Data Replication Console, you can now set a specific Sync SCN value for multiple target tables at one time to quickly configure Applier processing. New Features In addition to the closed enhancement requests, Data Replication provides some new features. For descriptions of these new features, see the Informatica Data Replication Release Guide. IDR-RN

4 Fixes The following table describes fixed limitations: The Extractor might not extract all of the change data of interest from the Microsoft SQL Server active transaction log if the log is composed of multiple physical LDF files An Extractor that runs in continuous mode might end with a unique constraint violation error when using a configuration that has a Microsoft SQL Server source and an Oracle target For configurations with an Oracle source and a Teradata target, the Applier might fail to apply Inserts to a target table if it receives Updates of primary key columns to process in the same apply cycle. This failure occurs if the target table has column names that match reserved Teradata keywords When processing Microsoft SQL Server sources, the Extractor might end with an error but report a status of Success An InitialSync task that runs on multiple threads might end abnormally with Exit Code For Oracle sources, the Extractor task might process redo logs for chained rows incorrectly. The Extractor might record null values for columns that were not updated on the source , , For Oracle sources, the Extractor might end with a processqmirow error when processing Quick Multi Insert (QMI) records When processing Oracle ASM sources, the Extractor might end abnormally with the following Oracle error: ORA : converting column overflows integer datatype The Data Replication Console fails to deploy configuration changes for targets other than Microsoft SQL Server, Oracle, Sybase ASE, and DB2 for Linux, UNIX, and Windows , For Teradata targets, Data Replication does not replicate DDL operations that alter a column length The Data Replication Console cannot open a configuration with a Microsoft SQL Server source and an EXTERNALFEED target that you previously created. The Console reports the following error: Failed to load the configuration because of the error: Internal error. The target schema 'dbo' not found. Contact Informatica Global Customer Support For Oracle targets, the Applier ends with the following error when applying empty and null values to character and binary columns: Msg: Incompatible data types in stream operation For Microsoft SQL Server sources, the Data Replication Console might get incorrect metadata for source columns. As a result, the Extractor might extract the wrong change data For Microsoft SQL Server sources, the Server Manager might fail to connect to the source database when you save a configuration or enable Replicate mode from the Data Replication Console. This error occurs because the Server Manager tries to connect to IP address when the source database has disabled this interface. Now the Server Manager connects to the first active interface. 4 IDR-RN

5 In Merge Apply mode, an Applier task that uses a configuration that specifies different SQL expressions for Insert, Update, and Delete operations might incorrectly use the SQL expressions for Insert operations to process Updates and Deletes The InitialSync and Applier tasks might end abnormally with a Severe 139 error and generate a core file because of memory corruption. This error occurs when you use configurations that include a large number of virtual columns For Microsoft SQL Server sources, the Extractor might end abnormally with the following error when processing valid backup logs: MS SQL backup file is corrupted. This problem occurs because the Extractor uses the incorrect procedure to determine the size of the backup logs For Greenplum, PostgreSQL, and Vertica targets, InitialSync might end abnormally during target synchronization if you use a replication configuration that includes rules for handling timestamp datatype incompatibilities For Oracle RAC sources, the Extractor task might end with error This error occurs because the Extractor tries to execute SQL statements without establishing a connection to the source database For Microsoft SQL Server sources, the Extractor might not process change data for a source column correctly after an operation that changes the leaf_offset value of this column occurs. Data Replication uses the leaf_offset value to get change data for the column from transaction logs. The leaf_offset value might change after a DBCC DBREINDEX operation. Also, the Applier might end abnormally or apply data incorrectly when processing intermediate files that contain change data from source columns with changed leaf_offset values InitialSync performance is degraded when InitialSync is processing Tcl scripts For Microsoft SQL Server sources, Data Replication might choose the standard ODBC driver instead of the Native Client. With the ODBC driver, Data Replication fails to enable Replicate mode or query the Replicate mode status The Server Manager might generate a core file when sending an SMTP alert to multiple subscribers For Microsoft SQL Server sources, the Data Replication Console might display the following error when opening a configuration or refreshing metadata on the Map Tables tab: Cannot Retrieve LSN, please contact global support The Server Manager might stop sending notifications if its connection to the SMTP server is interrupted For Microsoft SQL Server sources and targets, the Data Replication Console fails to generate a target schema for tables that contain a SYSNAME column The Applier might end abnormally when processing Updates from Oracle sources that write null values to columns. This problems occurs if Oracle does not write the redo values for these Updates to the log For configurations that specify SQL expressions, InitialSync might end with the ORA error when using DBLinks to synchronize Oracle sources and targets. IDR-RN

6 If the size of an updated replication configuration exceeds the buffer size that the Data Replication Console uses to send data to a Server Manager instance, Data Replication fails to update the replication configuration and reports Error For configurations with Oracle sources and Teradata targets, InitialSync might end abnormally when loading data to date and timestamp columns with the TPT Load Operator The Data Replication Console cannot open a configuration or refresh configuration metadata if you defined many WHERE clauses for a mapped source column After opening a configuration with MySQL targets, the Data Replication Console might get an empty list of target schemas and drop the table mappings for these schemas For configurations with Oracle sources and Teradata targets, Data Replication does not replicate ALTER TABLE statements that change the length of source VARCHAR2 columns The Applier generates a core file when using multiple threads to process change data from source tables that have virtual columns to which Tcl scripts are assigned In the Customize Settings for the Selected Tables dialog box, if you set the Distribute by field for a table to Tables, the dialog box still displays the default value of Rows On AIX, the Extractor might end with an error when reading online redo logs that are on a raw device. The problem occurs because the Extractor incorrectly determines the raw offset for the raw device The Applier task might end abnormally with Error code 139 and generate a core file If Data Replication fails to restart the Microsoft SQL Server source to enable Replicate mode, the Data Replication Console prints an error message to the log but does not display this message The Data Replication Console might fail to open a configuration that maps Oracle partitioned tables to target tables. When this failure occurs, the Data Replication Console reports the following Oracle error: ORA-01427: single-row subquery returns more than one row For Microsoft SQL Server sources, the Extractor might not parse the online log to which the database server is writing data. In this situation, the Extractor issues the following error message or a similar message: Parser error while parsing [online] block with VLF ID 0x10301 Block ID 0x100b Slot count The Server Manager does not send SMTP notifications about a task restart if the task is configured to run on a Server Manager subserver The Applier might end with an error or apply null values when processing Tcl expressions If the Server Manager is configured to frequently send SMTP notifications, it might end abnormally because of a handle leak The Server Manager ends abnormally with the following error because the class that the Server Manager uses to work with SQLite databases is not thread-safe: SQLITE_MISUSE[21]: Error binding int param 6 IDR-RN

7 For configurations with Oracle sources, the Data Replication Console incorrectly retrieves metadata for unique source indexes that include one or more columns with the DESC keyword. As a result, the Applier cannot use these indexes to uniquely identify rows when applying Updates and Deletes The Applier task might end abnormally with return code -1 but not issue an error message. This problem occurs because an internal Server Manager mechanism is not thread-safe For Greenplum 4.2 targets, the Applier might end with the following error message or a similar message: Msg: [Informatica][ODBC Greenplum Wire Protocol driver][greenplum] ERROR: syntax error at or near ")"(Position 180;File scan.l;line 979;Routine base_yyerror;) This error occurs because the PostgreSQL decode function has a new syntax in Greenplum For Oracle sources, the Extractor task might use the incorrect network order to process a redo record. In this situation, the Extractor ends with the following error: Unable to parse a redo record For configurations with a Microsoft SQL Server source and a Microsoft SQL Server target, the target columns that the Data Replication Console generates based on source TIMESTAMP columns have an incorrect datatype. When you use a configuration that contains incorrect target column datatypes to run a replication, the InitialSync and Extractor tasks might fail On AIX, the Applier for Teradata ends abnormally when executing the strcpy () function from the $DBSYNC_HOME/support/libtcl8.5.so library For Microsoft SQL Server sources, InitialSync ends abnormally when synchronizing a target table that is mapped to a source table for which you previously dropped the first column. This problem occurs because the Data Replication Console writes incorrect column positions for the source table to the configuration The InitialSync task ignores the initial.max_long_size parameter and ends with an error when processing Microsoft SQL Server IMAGE columns that are mapped to Oracle BLOB columns For Teradata 14.0 targets, Data Replication does not support mappings to target NUMBER columns In the Data Replication Console, the MS SQL Server Instances dialog box, from which you set the Replicate mode for Microsoft SQL Server sources, does not display SQL Server instances, databases, and tables in the alphabetical order The Applier might end abnormally when logging messages of the LM_DEBUG severity level If the before- and after-image suffixes for audit table columns contain a single character, the Map Columns tab of the Data Replication Console might display a pair of before- and after-image columns instead of a single audit table column For Teradata targets, an InitialSync task that runs on AIX ends abnormally when processing a Tcl script for a TIMESTAMP column that has a precision greater than For Teradata targets, the Data Replication Console might not save a replication configuration if it maps a source table to a target view that is generated based on a target table with long column names On AIX, low compiler optimization levels degrade Extractor and Applier performance Data Replication does not replicate Oracle direct-path Inserts to Oracle target tables that are defined with the PARALLEL option. IDR-RN

8 In Audit Apply mode, the Applier task might end abnormally with the following message: Msg: Row must be full for flushing output stream For Oracle and Netezza targets, the Applier might end abnormally when applying changes in Merge Apply mode to target tables that include primary key or virtual index columns with the NOT NULL constraint For Oracle and Microsoft SQL Server sources, if you open and save the configuration in the Data Replication Console after InitialSync completes target materialization, the Extractor might skip some transactions. The Extractor skips transactions that occur after you created the configuration file and before you started the Extractor For configurations with an Oracle source, the Applier ends with an error when replicating EATE TABLE... AS SELECT operations that create a table based on another table that contains LOB columns The Applier task might end abnormally with the following message when processing DDL changes: ConfigRepDB.cpp:11303: void History::buildChanges(int, History::op_vector_t&, int): Assertion 'false' failed InitialSync might end with an error when loading large tables to Teradata targets for which you defined SQL expressions that use TIMESTAMP values For configurations with a Microsoft SQL Server source and a Microsoft SQL Server target, Data Replication incorrectly replicates ALTER TABLE operations that add a non-clustered primary key to a table. The Applier adds a clustered primary key to the corresponding target table For Teradata targets, InitialSync cannot process Tcl scripts that are associated with virtual columns that have the TIMESTAMP datatype If you map a virtual column to which a Tcl script is assigned to the primary key column on the target, the Tcl Script Engine incorrectly sets values for the target column After the Applier executes the dbs::skip command from a Tcl script, it also skips a subsequent record For Oracle sources, the Extractor task might end abnormally when it parses records that are related to clustered tables If a target table includes one or more columns that are mapped to virtual source columns to which an empty SQL expression is assigned, the Applier ends abnormally when applying Updates to this table For Microsoft SQL Server sources, the Applier task ends with an error after it tries to process a DDL statement that changes the size of a source column that is mapped to a BLOB or CLOB column The Data Replication Console cannot open a replication configuration that was created in the console supplied with Data Replication version 2.5 or earlier For Oracle RAC sources, the Extractor task might parse Oracle logs incorrectly, thereby causing change data inconsistencies The SQL Script Engine cannot process SQL expressions that access the before and after values of unmapped source columns when you run InitialSync with a native load utility or run the Applier in Merge Apply mode. 8 IDR-RN

9 For Oracle sources, the Extractor task logs the following message for each row if a column is added to a source table when ADD COLUMN replication is disabled: ChangeRecordFilter::PushRedoCTLV got column column_name for table table_name which is not in the table's definitions This message is now issued when the extract.verbose_level runtime parameter is set to The Applier cannot retrieve metadata values for SQL expressions that are defined for a virtual source column with the DATE datatype For Oracle sources, the Extractor incorrectly applies filters that use a WHERE clause to Quick Multi Insert (QMI) records The Server Manager might get incorrect exit codes from tasks. In this situation, the Server Manager might send an incorrect task status of Success to the Data Replication Console even though the task generated a core file For Microsoft SQL Server sources, the Extractor cannot process SELECT * FROM table1 INTO table2 statements if the table from which you select data is empty Data Replication does not replicate TRUNCATE TABLE operations to Teradata targets For a reverse-replication configuration that you generate for a DB2 source and DB2 target, the Data Replication Console provides an incorrect value for the db2.initial_lsn runtime parameter. Consequently, when you run the Extractor with the configuration, the Extractor ends abnormally If you run the Server Manager as a service on a Windows system with an expired Data Replication license key, the Server Manager service does not stop when you issue the following command: server_manager.exe RUN_AS_SERVICE -k For configurations with a Microsoft SQL Server source and an Oracle target, Data Replication might not process DDL statements that resize columns or change the nullable constraint correctly For Sybase ASE sources, Data Replication cannot use the same configuration to run an InitialSync task and an Extractor task in Continuous mode when these tasks simultaneously process different sets of source tables For Netezza targets, the Applier might end abnormally when applying Updates in Merge Apply mode to target distribution columns. Review the Release Notes of previous releases for information about previous fixed limitations. IDR-RN

10 Known Limitations The following table describes known limitations: If you add one or more LDF files to the transaction log after performing a full database backup, the MS SQL Server Backup task cannot back up the extended transaction log. Workaround: Instead of the MS SQL Server Backup task, use a third-party tool that creates backup logs in native format If you add one or more LDF files to the transaction log while the Extractor task is running, the Extractor might not extract all of the change data of replication interest from the extended transaction log. Workaround: Before you add the LDF files to the transaction log, stop the Extractor task For configurations with a Microsoft SQL Server source and an Oracle target, Data Replication increases the length of source CHAR and VARCHAR values that include national characters when replicating these values to a target. The Applier cannot apply these longer values to the corresponding target CHAR and VARCHAR columns that were generated based on DataReplication_installation/uiconf/DataTypes.xml file. Workaround: If source CHAR and VARCHAR columns include national characters, increase the length of the corresponding target columns. Map the source CHAR(n) and VARCHAR(n) columns to the CHAR(n+2) and VARCHAR(n+2) columns on the target , On HP-UX, InitialSync ends abnormally when using a configuration that has a DB2 source or DB2 target If a configuration includes table mappings that use different apply modes, Data Replication might use the wrong apply mode when replicating DROP TABLE operations. For example, if a configuration includes Merge Apply and Audit Apply mappings and a DROP TABLE occurs on a source table mapped in Audit Apply mode, the Applier incorrectly tries to use Merge Apply mode to process the DROP TABLE operation. The Applier ends abnormally because it cannot find the audit log table to drop. Conversely, if a DROP TABLE operation occurs on a source table mapped in Merge Apply mode, the Applier incorrectly tries to use Audit Apply mode to process the DROP TABLE operation. In this case, the Applier drops the target table and preserves the audit log table For TEXTDRIVER and Hadoop targets, the Applier ends abnormally when replicating TRUNCATE TABLE statements. Ensure that the replication of TRUNCATE TABLE operations is disabled for these target types The Applier might end abnormally when processing Updates if it uses a configuration that includes virtual columns and mapped source columns with a LOB datatype On Linux and UNIX systems, Data Replication might end abnormally and generate a core file if the ODBCINST environment variable points to an existing directory instead of to the odbcinst.ini file For Microsoft SQL Server sources and targets, InitialSync incorrectly handles non-latin object names. If a Microsoft SQL Server source or target uses non-latin object names, InitialSync does not materialize target tables from the source tables The Applier ends abnormally when processing Updates and Deletes for tables with fixed-length columns that are part of a logical primary key if the source and target column lengths differ. This error occurs because of trailing spaces in these columns. 10 IDR-RN

11 If you define WHERE clauses for multiple source columns and use one or more OR operators to join these WHERE clauses, the Extractor ignores all of these WHERE clauses when filtering data. However, InitialSync supports WHERE clauses with the OR operator and uses the operator precedence rules of the source database For Oracle sources, Data Replication cannot map columns that have the NUMBER(x, -1) datatype. Consequently, Data Replication incorrectly generates target schemas based on source tables that include NUMBER(x, -1) columns. Also, Data Replication incorrectly replicates source DDL statements that create NUMBER(x, -1) columns For Greenplum targets, the Applier cannot process SQL expressions that include the datatype cast operator (::) For Microsoft SQL Server sources, Data Replication replicates Updates of primary key columns as a pair of Delete and Insert operations, even if the extract.mssql.process_updates_as_updates parameter is set to 1. Consequently, Data Replication incorrectly resolves Update conflicts based on the conflict resolution rules that you define in the configuration For configurations with a single source and multiple targets, the Applier recovery cycle might end abnormally if more than one target in the configuration use the same recovery table For Microsoft SQL Server targets, if you configured InitialSync to synchronize data in multiple transactions and InitialSync fails after the first few commits, InitialSync incorrectly handles this failure. The next time InitialSync runs, instead of synchronizing all data, it synchronizes only the data that was not committed during the previous failed run. Consequently, InitialSync does not report a constraint violation error during the subsequent run For Oracle sources, the Extractor processes the archive log or online redo log that includes the Start SCN value from the beginning of the log. If the Start SCN value that the Data Replication Console calculated or that you manually set in the configuration is located in the middle of an Oracle log, the Extractor processing starts from the beginning of the log that includes the Start SCN value For Oracle targets, Data Replication does not support replication of rows that include BLOB, CLOB, LONG, LONG RAW, or NCLOB columns if the total amount of data in these columns exceeds 4000 bytes Data Replication does not support Internet Protocol version 6 (IPv6) For DB2 sources, the SQL Script Engine cannot calculate mathematical expressions that include REAL or DOUBLE constants greater than 10. Also, the SQL Script Engine rounds the results of mathematical expressions that include integer constants to an integer value. Workaround: In the SQL script, use the E notation representation of REAL or DOUBLE constants greater than 10. To get a REAL or DOUBLE value as a result of a mathematical operation, use the E notation representations for all of the integer operands For configurations with Oracle sources and Sybase ASE targets, the Applier cannot apply DROP CONSTRAINT operations that drop a primary key defined for an initially nullable column For DB2 and Sybase ASE sources, the Extractor skips all DDL changes that occur on a source between the time you open or refresh the configuration in the Data Replication Console and the time you save the configuration. To prevent skipped DDL changes, do not execute the DDL statements on the source during this period The Applier cannot replicate DDL operations that drop the last mapped table or column. IDR-RN

12 For Sybase ASE targets, Data Replication cannot replicate data to Sybase BIT columns in Audit Apply mode. This problem occurs because the Applier cannot insert null values into the before image and after image of BIT columns When replicating data from Microsoft SQL Server sources to DB2 targets, Data Replication does not process UNIQUEIDENTIFIER columns. The Data Replication Console maps UNIQUEIDENTIFIER columns to CHARACTER FOR BIT DATA columns. However, Data Replication does not support CHARACTER FOR BIT DATA columns for DB2 targets For Netezza targets, Data Replication does not replicate DDL operations for source tables and columns that have lowercase names. The Applier ends abnormally when replicating subsequent DML changes for these tables and columns For Microsoft SQL Server sources, if you add a clustered index to a mapped source table that the Extractor task previously processed, Data Replication does not update partition-related information in the configuration. Consequently, when you run the Extractor later, it cannot extract DML changes that occurred after you added the index. Workaround: To correctly extract change data after you add a clustered index to a SQL Server source table, open the configuration in the Data Replication Console and save it. This action updates partitionrelated information When you replicate data from Sybase ASE source columns with the DOUBLE, FLOAT, or REAL datatype to a TEXTDRIVER target, Data Replication truncates the scale to six digits , The Applier does not lock a target row to apply a conflict resolution rule. You might get unexpected data on the target if changes for the row in conflict occur during the interval between Applier detection of the conflict and application of the conflict resolution rule Data Replication cannot filter source data for a replication job by using a WHERE clause that includes column names with spaces or special characters. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at 12 IDR-RN

13 Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Brazil Mexico North America Toll Free France Germany Italy Netherlands Portugal Spain Switzerland United Kingdom Standard Rate Belgium France Germany Netherlands United Kingdom Toll Free Australia Asia Pacific China IDR-RN