Informatica Data Replication FAQs

Transcription

1 Informatica Data Replication FAQs 2012 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation.

2 Abstract This article describes frequently asked questions about using Informatica Data Replication for transactional data replication. It includes information about Data Replication features. Supported Versions Informatica Data Replication HotFix 2 Table of Contents General Questions Recovery and Checkpoint Processing DB2 for Linux, UNIX, and Windows Sources Microsoft SQL Server Sources Oracle Sources Sybase Sources Targets General Questions What is Informatica Data Replication? Informatica Data Replication is a transactional data replication tool. It extracts DML changes (inserts, deletes, and updates) from DB2 for Linux, UNIX, and Windows, Microsoft SQL Server, Oracle, and Sybase ASE databases and replicates the changes to heterogeneous targets. It also extracts DDL changes from Oracle sources. Targets include relational databases and flat files. Data Replication can replicate large volumes of data with low latency and without degrading source system performance. You can use Data Replication for the following purposes: Update data warehouses with changes from OLTP systems in a timely manner Offload data for query processing on a less busy system Provide up-to-date data for operational reporting Update ODS systems to provide the latest data for making critical and timely business decisions Extract transactional changes in text format for migration to a non-database target such as Hadoop or Hive Use Data Replication in conjunction with Fast Clone to migrate data to different platforms with near zerodowntime Can Data Replication replicate changes from a single source to multiple targets? Yes. You can configure a replication from a single source to multiple targets in Network mode. The targets must be of the same type and use the compatible target schema that can have different names. For example, you can replicate changes from a Microsoft SQL Server source to multiple Oracle targets. Data Replication has no limit on the number of targets. 2

3 When configuring this type of replication job from the Data Replication Console, connect to the primary target on the Target Database tab using a named connection. Then, on the Routing tab, add the other targets and perform the following optional tasks: Define selection conditions to filter rows to different targets. For example, you could send rows for a specific region to one target and rows for another region to a different target. However, you must use the same columnlevel filtering criteria for all targets. For example, if you select a subset of columns, you must replicate those same columns to all targets. Exclude tables from replication for a particular target. By default, Data Replication replicates all mapped tables to all targets. Override the primary target schema name to use a different schema name for the secondary target. Override the apply mode for a particular target. Override the schema for the audit log table for a particular target. Override the primary target schema and table name for the recovery table for a particular target. Can Data Replication replicate changes from multiple sources to a single target? Yes. Data Replication can emulate replication from multiple sources to a single target. To configure this type of replication job from multiple sources to a single target, create a configuration file for one source and then deploy it locally for all of the other sources. When deploying the configuration file, use the same target connection and override the source connection. The Data Replication Console creates a configuration file with a file name that consists of the original configuration file name followed by a copy identifier. Can Data Replication replicate data continuously? Yes, Data Replication can replicate change data continuously in Network mode from all supported sources to all supported targets. When configuring a continuous replication job, select one of the following options on the Extract Range tab: For Microsoft SQL Server sources, select Read from online transaction logs. For Oracle sources, select Read from online redo logs. For Sybase ASE sources, select Read from online logs. In the Runtime Settings tab > General view, you can set continuous replication latency. The default value for continuous replication latency is 1 second, which is usually acceptable to process all changes in a microcycle You also must create a schedule that includes the Extractor, Send intermediate file, and Applier tasks. These schedule tasks must be independent from each other. When running the continuous replication, you can view replication statistics in the Data Replication Console to analyze the Extractor, Send intermediate file, and Applier task performance and replication latency. To open the Statistics window, click the Statistics toolbar button, or on the Server Manager tab > Schedules view, right-click a schedule row and click Statistics. Does Data Replication support bidirectional replication? For configurations with two active databases, Data Replication provides loopback avoidance to prevent changes from being returned to the database to which they were originally written by the Data Replication Applier. However, Data Replication does not provide full conflict resolution. Does Data Replication extract data from the columns that have user-defined data types (UDTs)? Data Replication can extract change data from UDT columns for Microsoft SQL Server and Sybase ASE sources only. Data Replication does not extract data from UDT columns for DB2 for Linux, UNIX, and Windows or Oracle sources. 3

4 What type of data compression algorithm does Data Replication use on intermediate files that are sent over the network? If you select the Compress data on the fly option on the Runtime Settings tab > General view, Data Replication uses the QuickLZ software to compress and decompress intermediate files during a data replication job. You cannot specify a compression ratio or select another compression method. However, with the default compression, data replication jobs that use QuickLZ compression are often much faster than those without compression because of the reduction in I/O that is associated with writing compressed data to a target. For more information about QuickLZ, see Can Data Replication replicate DDL changes? Data Replication can replicate only DDL changes that add or drop columns for replication configurations with Oracle sources and Oracle targets. Does the Data Replication Console use JDBC drivers to connect to source and target databases? Yes. The Data Replication Console uses JDBC drivers to connect to sources and targets. Data Replication supplies JDBC drivers in the DataReplication_installation\lib subdirectory. For Netezza, Teradata, and earlier versions of MySQL, you must download the appropriate JDBC drivers from the database-vendor Web site and put them in the DataReplication_installation\lib subdirectory. The following table describes the JDBC drivers and environment variables that the Data Replication Console requires: Database Driver Environment Variable Driver Provided by Data Replication? DB2 for Linux, UNIX, and Windows DataDirect DB2 JDBC driver, dwdb2.jar DB2_JDBC_DRIVER_LIB Yes Greenplum PostgreSQL JDBC driver, postgresql jdbc2.jar POSTGRESQL_JDBC_ DRIVER_LIB Yes Microsoft SQL Server DataDirect SQL Server JDBC driver, dwsqlserver.jar SQLSERVER_JDBC_DRIVER_ LIB Yes MySQL For MySQL Enterprise Edition 5.0.x and 5.1, use the DataDirect MySQL JDBC driver, dwmysql.jar. For other supported MySQL versions, use the MySQL JDBC driver, mysql- connector-java bin.jar. MYSQL_JDBC_DRIVER_LIB For MySQL Enterprise Edition 5.0.x and 5.1, Data Replication provides the DataDirect MySQL JDBC driver. For other supported MySQL versions, download the MySQL JDBC driver from MySQL web site using either a GPL or commercial license. Netezza Netezza JDBC driver, nzjdbc.jar NETEZZA_JDBC_DRIVER_LIB No. Download this driver from Netezza. Oracle Oracle JDBC driver, classes12.jar ORACLE_JDBC_DRIVER Yes PostgreSQL PostgreSQL JDBC driver, postgresql jdbc2.jar POSTGRESQL_JDBC_ DRIVER_LIB Yes Sybase ASE Sybase JDBC driver, dwsybase.jar SYBASE_JDBC_DRIVER Yes 4

5 Database Driver Environment Variable Driver Provided by Data Replication? Teradata All of the Teradata JDBC driver files: - terajdbc4.jar - tdgssconfig.jar - tdgssjava.jar TERADATA_JDBC_DRIVER_ LIB No. Download these driver files from Teradata. Vertica PostgreSQL JDBC driver, postgresql jdbc2.jar POSTGRESQL_JDBC_ DRIVER_LIB Yes Verify that the JDBC drivers you use have the.jar file names that are specified in the table. If not, open the idr_console.sh or idr_console.cmd in a text editor and edit the environment variable values to specify the JDBC drivers that you use. When do I need to install ODBC drivers? Data Replication uses ODBC drivers to connect to most targets to apply or synchronize change data. On Linux or UNIX, use one of the DataDirect ODBC drivers that Data Replication provides in the DataReplication_installation/dd/lib subdirectory. However, for Vertica and Netezza, download the DataDirect ODBC driver from the database vendor and put them in the DataReplication_installation/dd/lib subdirectory. The following table describes the Data Replication requirements for ODBC drivers, including whether a driver is required on the source, target, or both: Database Source Destination Comment DB2 for Linux, UNIX, and Windows Yes, for InitialSync Yes, for InitialSync For DB2 sources and targets, ensure that the DB2 Client, DB2 Runtime Client, or DB2 Connect is installed. Data Replication uses the DB2 Call Level Interface (CLI), which is provided with the clients, to access the database for transactional replication. To run an InitialSync task on Windows, also install the IBM DB2 ODBC driver. This driver is usually delivered with the DB2 Client. If necessary, you can manually download it. To run InitialSync on Linux and UNIX, use the DataDirect ODBC driver for DB2 for Linux, UNIX, and Windows that Data Replication provides. Greenplum n/a Yes On Windows, install the Greenplum ODBC driver (preferred) or the PostgreSQL ODBC driver for Greenplum targets. On Linux and UNIX, use the DataDirect ODBC driver for Greenplum that Data Replication provides. Microsoft SQL Server Yes, on Linux and UNIX Yes, on Linux and UNIX On Windows, ensure that the SQL Server Native Client is installed. On Linux and UNIX, use the DataDirect ODBC driver for Microsoft SQL Server that Data Replication provides. MySQL n/a Yes On Windows, install the MySQL ODBC driver for MySQL targets. On Linux and UNIX, use the DataDirect ODBC driver for MySQL that Data Replication provides. Netezza n/a Yes On Windows, install the Netezza ODBC driver for Netezza targets. On Linux and UNIX, install the DataDirect ODBC driver for Netezza targets. 5

6 Database Source Destination Comment Oracle No No For Oracle sources and targets, ensure that the Oracle Client is installed. PostgreSQL n/a Yes On Windows, install the PostgreSQL ODBC driver for PostgreSQL targets. On Linux and UNIX, use the DataDirect ODBC driver for PostgreSQL that Data Replication provides. Sybase ASE Yes Yes On Windows, ensure that the ODBC driver that comes with Sybase ASE is installed. On Linux and Unix, use the DataDirect ODBC driver for Sybase that Data Replication provides. Teradata n/a Yes For Teradata targets, install the TPT libraries that include the Teradata ODBC driver. Vertica n/a Yes On Windows, install the Vertica ODBC driver for Vertica targets. On Linux and UNIX, install the DataDirect ODBC driver for Vertica targets. Tip: Download the driver or client for your database version. On Linux and UNIX, you also must complete the following configuration tasks: In the Informatica Data Replication Console, verify that the global.use_data_direct parameter on the Runtime Settings tab > Advanced Settings view is set to 1. Verify that the DD_INSTALLDIR environment variable points to the DataReplication_installation/dd directory. Do I need to install an ODBC driver manager? On Linux and UNIX systems, Data Replication requires an ODBC driver manager in addition to the ODBC drivers that it uses to connect to targets and sources. The driver manager provides an ODBC API that enables Data Replication to communicate with the ODBC drivers. Data Replication provides the DataDirect driver manager libraries in the DataReplication_installation/dd/lib directory. Depending on the operating system, use one of the following environment variables to point to the directory that contains the DataDirect driver libraries: Operating System AIX HP-UX Linux Solaris Environment Variable LIBPATH SHLIB_PATH LD_LIBRARY_PATH Use the LD_LIBRARY_PATH_64 environment variable if it is already defined in the system. Otherwise, use the LD_LIBRARY_PATH environment variable. Also, set the ODBCINST environment variable to point to the DataReplication_installation/dd/odbcinst.ini file. 6

7 When do I use the SQL Apply, Merge Apply, and Audit Apply modes? Apply modes use different mechanisms to apply change data to the target: SQL Apply executes SQL statements on the target that are equivalent to the SQL change operations on the source. Use SQL Apply mode for data replication to DB2 for Linux, UNIX, and Windows, MySQL, Microsoft SQL Server, Oracle, PostgreSQL, and Sybase ASE targets Audit Apply inserts a row to the audit log table on the target for each operation that occurred on the source. An audit log table contains operation metadata and before and after values for each source column. You can use this apply mode for all supported targets to audit changes for regulatory or oversight purposes. Merge Apply is a combination of SQL Apply and Audit Apply. The Applier accumulates all changes in the audit log tables, merges the changes into fewer SQL statements, and then applies the changes to the target. The SQL merge statements are optimized for the types of SQL changes in the apply batch. You must use Merge Apply for data replication to Greenplum, Netezza, Teradata, and Vertica targets. You can also use it for data replication to Oracle. Can Data Replication run InitialSync task for a subset of mapped source tables? Yes. You can run InitialSync task in the Data Replication Console or from the command line to selectively materialize target tables. In the Data Replication Console, set -1 Sync SCN for the tables that you need to materialize, save the configuration, and then run InitialSync. From the command line, run InitialSync with the RESYNC parameter set to P to materialize only the tables for which the SCN value is set to -1 in the configuration file. From the command line, run InitialSync with the RESYNC parameter set to N and use the DEST_TABLES or EXCLUDE_DEST_TABLES parameters to specify the source tables that you need to materialize. How can I get the commit timestamp of the last replicated record? Use the Audit Apply mode for the data replication. In this mode, Data Replication stores commit timestamps in the audit log tables. What is the DBSYNC_SYNC_INFO table used for? Data Replication creates the DBSYNC_SYNC_INFO table when the InitialSync component performs an initial synchronization of an Oracle source and Oracle target using a database link (dblink). The DBSYNC_SYNC_INFO table contains information about the InitialSync operation. The table has the following structure: "CREATE TABLE %s.dbsync_sync_info " \ "(id VARCHAR2(20)," \ "sync_date DATE," \ "source_db VARCHAR2(512)," \ "source_schema VARCHAR2(512)," \ "source_table VARCHAR2(512)," \ "dest_db VARCHAR2(512)," \ "dest_schema VARCHAR2(512)," \ "dest_table VARCHAR2(512)," \ "scn_wrap NUMBER(12)," \ "scn_base NUMBER(12)," \ "rows_transfered number(18)," \ "duration number(18)," \ "primary key (id) ) initrans 10" How do I start the Informatica Data Replication Console? Are there any prerequisites? The executable for the Informatica Data Replication Console is in the top-level Data Replication installation directory. To start the console: On Windows, run idr_console.cmd. On Linux or UNIX, run idr_console.sh. 7

8 Before starting the console, verify that the following prerequisites are met: The Data Replication Console requires the Java Runtime Environment (JRE) 1.5 or later. If the JRE is not installed, you can download it for free from You must define a JRE_HOME environment variable that points to the JRE base directory. Also, include the JRE_HOME/bin directory in the PATH environment variable. On Linux and UNIX, the Data Replication Console requires an X Window environment. Configure an X Window environment if one does not exist. How do I start the Data Replication Extractor and Applier? Do I need to start the Extractor first? You can start the Extractor and Applier from the command line or the Informatica Data Replication Console. You should start the Extractor prior to starting Applier. Otherwise, the Applier does not find the files with which it needs to work. To manually start the Extractor: From the command line, run the appropriate Extractor script for the type of source database that you use. These script files are described in the Informatica Data Replication User Guide. From the Data Replication Console, click the Extract data toolbar button or click Data > Extract data on the menu bar. In Local mode, you must have previously specified the executable for the Extractor task on the Runtime Settings tab > File Locations view To manually start the Applier: From the command line, run the appropriate Applier script for the type of target database that you use. These script files are described in the Informatica Data Replication User Guide. From the Data Replication Console, click the Apply to target toolbar button or click Data > Apply to Target on the menu bar. In Local mode, you must have previously specified the executable for the Applier task on the Runtime Settings tab > File Locations view In Network mode, you can run a schedule that includes Extractor and Applier tasks at a specific date and time, periodically, or continuously. How do I start the InitialSync component to perform an initial materialization of the target based on the source schema? You can manually run the InitialSync task from the command line or the Informatica Data Replication Console: From the command line, run the appropriate InitialSync script for the type of target database that you use. These script files are described in the Informatica Data Replication User Guide. From the Data Replication Console, click the Synchronize toolbar button or click Data > Synchronize on the menu bar. In Network mode, you can run a schedule that includes InitialSync task at a specific date and time, periodically, or continuously. Recovery and Checkpoint Processing Are recovery tables required? Informatica recommends that you use the recovery table for all replication configurations to prevent the Applier from replicating previously applied data again when the Applier task restarts. Typically, you generate recovery tables from the Data Replication Console. When you save a configuration file, Data Replication displays a dialog box in which you confirm the generation of recovery tables. If an error occurs when the Data Replication Console is generating the recovery tables, you can manually execute CREATE TABLE statements to create recovery tables. For example CREATE TABLE statements, see the Informatica Data Replication User Guide. 8

9 For a replication job with multiple targets, you can override the recovery table names to specify a different name for each target on the Routing tab > Override Apply subtab. Can I use a single recovery table for multiple configurations? Yes. You can use the same recovery table for different replication configurations. Which tool can I use to view SQLite databases of the Server Manager, Extractor, and Applier? To view the SQLite database.db or.db3 files for the Server Manager, Extractor, and Applier, you can use SQLite Expert program or SQLite command line shell. You can download SQLite command line shell from How do I determine the last captured SCN? You can retrieve the last captured SCN from the Extractor SQLite database file, DataReplication_installation/ configs/<configuration_name>.db. To get the last captured SCN, run the following query: select max(last_change) from OracleRedoLogFilePoll DB2 for Linux, UNIX, and Windows Sources Does Data Replication extract change data from DB2 materialized query tables? Yes. Data Replication can extract change data from DB2 materialized query tables. Does Data Replication extract change data from DB2 partitioned tables? Yes. Data Replication can extract change data from DB2 partitioned tables. However, Data Replication does not support source tables in a partitioned database environment that was created with the DB2 Database Partitioning Feature (DPF). Which mechanism does Informatica Data Replication InitialSync use to unload data from DB2 for Linux, UNIX, and Windows? For DB2 for Linux, UNIX, and Windows sources, InitialSync unloads data by using either ODBC or the db2export API. For source tables that do not have columns larger than 32,700 bytes, InitialSync uses the faster db2export API. Otherwise, InitialSync uses the DB2 ODBC driver. Why is a DBSYNC_SYNC_LSN table required for DB2 sources? Because DB2 does not provide a way to retrieve the current LSN from the database, InitialSync inserts a record for each target table in a service table. Data Replication creates the service table with the default name of DBSYNC_SYNC_LSN in the DB2 source database. After you start change data replication, the Extractor uses these records to determine the initial LSN to pass to the Applier. The Applier only applies the changes that have an LSN greater than the passed LSN. Why do I need to run the Extractor prior to running an InitialSync task for DB2 sources? During the initial run, the Extractor writes the current LSN to the configuration file. When you run the Extractor again, after the InitialSync task, it uses the LSN in the configuration file to determine the point from which to start reading the transaction log. Microsoft SQL Server Sources Does the Data Replication Extractor for Microsoft SQL Server sources use a Microsoft API to read data? No. The Extractor reads the Microsoft SQL Server transaction logs directly. Does Data Replication extract change data from Microsoft SQL Server indexed views? Yes. Data Replication can extract change data from Microsoft SQL Server indexed views. 9

10 Does the Data Replication Extractor for Microsoft SQL Server sources use the Microsoft SQL Server CDC tables? No. The Extractor reads the transaction logs directly. However, Data Replication generates empty Microsoft SQL Server CDC tables when you enable Replicate mode. Can Data Replication extract change data from a Microsoft SQL Server database while SQL Server native transactional replication is active? Yes. Data Replication can extract change data while Microsoft SQL Server native replication is running. If you run Informatica Data Replication replication jobs and Microsoft SQL Server native replication against the same database, select the Disable Secondary Truncation Checkpoint option on the Runtime Settings > General view. This setting disables the Data Replication secondary truncation checkpoint to prevent incomplete data capture. In this case, Microsoft SQL Server manages the secondary truncation checkpoint and produces backup logs. Data Replication must be able to read both the backup logs and the online logs if it does not manage the secondary truncation checkpoint. Can a Data Replication Extractor process multiple Microsoft SQL Server databases? Yes. The Data Replication Extractor can extract data from multiple Microsoft SQL Server databases that belong to the same Microsoft SQL Server instance. Can Data Replication capture data from SQL Server online logs and backup logs? To capture data from online logs, Data Replication must run on the same Windows system as the Microsoft SQL Server database. To capture data from backup logs, Data Replication requires the backup logs to be in Microsoft SQL Server native format. You can run the Data Replication Extractor on the SQL Server source system or on a separate system that has the same operating system or a different operating system. To run the Extractor on a separate system, configure the Data Replication Server Manager on the source system in one of the following ways: Configure the Server Manager to create backup logs periodically and send the logs to the Server Manager that is installed on the system where the Extractor runs. Configure the Server Manager to create backup logs periodically in a shared directory that can be accessed over the network. The Extractor that runs on the other system can then access the shared directory to read the backup logs. Can I use a third-party tool to create backup logs for Microsoft SQL Server sources? Yes. Instead of running the Data Replication backup task for Microsoft SQL Server sources, you can use a thirdparty tool to create backup logs. However, you can only use tools that produce backup logs in native Microsoft SQL Server format. Can Data Replication capture Microsoft SQL Server change data from a Linux or UNIX system? Yes. On Linux and UNIX systems, Data Replication supports Microsoft SQL Server as a source database provided that you access the data using the Data Replication Server Manager, a mounted file system, or a copy of the SQL Server archive logs. Does Data Replication support Microsoft SQL Server tables that do not have primary keys? Yes. Data Replication supports Microsoft SQL Server tables that do not have primary keys. For the each of these tables, you must define a virtual index in the Data Replication Console. When do I need to enable Replicate mode? When Replicate mode is set to ON for a Microsoft SQL Server source, Data Replication uses SQL Server replication stored procedures to perform the following functions: Provide accurate processing of updates for BLOB records and prevent partial processing of BLOB data. Log additional columns, similar to Oracle supplemental logging, to uniquely identify rows and get consistent change records. 10

11 Force Microsoft SQL Server to log updates as a pair of delete and insert operations. This type of logging allows Data Replication to process the before image and after image of data for Audit Apply processing. Normally, the Server Manager enables the Replicate mode for Microsoft SQL Server databases when you save the configuration file. However, if necessary, you can enable Replicate mode manually. On the Server Manager tab > Servers view, select the server where Microsoft SQL Server is installed. Then right-click the server row and click MS SQL instances. You can then enable Replicate mode for all or some replicated databases or tables. Oracle Sources Does Data Replication extract change data from Oracle online redo logs? Yes. Data Replication can extract change data from both Oracle online redo logs and archived logs in a Real Application Cluster (RAC) or non-rac environment. Can Data Replication extract change data from an Oracle source in a Real Application Cluster (RAC) environment that uses Automatic Storage Management (ASM)? Yes. In a RAC, Data Replication can extract change data from both Oracle online redo logs and archived logs that are managed by ASM. How do I configure Data Replication to extract change data from an Oracle source in a RAC environment that uses ASM? On the Source Database tab of the Informatica Data Replication Console, enter the following information: In the Database Connection view, select the RAC Support box. In the ASM Settings view, enter the following information that Data Replication uses to connect to the ASM instance: - ASM instance hostname. The host name or IP address of the system with the ASM instance. - ASM instance port. The port number that is used to connect to the ASM instance. The default value is ASM sys username. The user name of the default Oracle user that was created at Oracle installation, or another user that you define. This user must have SYSDBA privileges. - ASM sys password. A clear text password for the ASM sys user. - ASM instance. A service name for the ASM instance. The default value is +ASM. If you want to use the Oracle instance name instead, select Use SID instead of SERVICE_NAME and then enter an Oracle instance name that is defined in an ORACLE_SID environment variable. Does Data Replication support Oracle compressed tables? In Oracle 9i and later releases up to Oracle 11g Release 1, Data Replication can extract only SQL inserts, with or without the append hint, from tables that have table compression or OLTP compression. In Oracle 11g Release 2 and later, Data Replication can extract all SQL change operations, including inserts, updates, and deletes. Data Replication does not support Oracle Exadata Hybrid Columnar Compression. Does Data Replication extract changes from Oracle index-organized tables (IOTs)? Yes. Data Replication can extract changes from IOTs. Does Data Replication extract changes from Oracle materialized views? Yes. Data Replication can extract changes from Oracle materialized views. Does Data Replication extract changes from an Oracle logical standby database? Yes. Data Replication can extract changes from Oracle logical standby databases. However, if you run the InitialSync component, you must use the original database as the source for the initial materialization. Note: This limitation does not apply to Oracle physical standby databases. You can run the InitialSync component with an Oracle physical standby database as the source. 11

12 Can I suppress Oracle database triggers so that they do not become active on target objects during replication? If you have Oracle or a later 10.2 patch, or if you have Oracle or later, Data Replication can suppress Oracle database triggers so that they do not become active on target objects during replication. The Data Replication Oracle user must be granted the special privileges that are provided in the following Oracle stored procedures: For Oracle or later 10.2 patches: dbms_streams_auth.grant_admin_privilege For Oracle or later: dbms_goldengate_auth.grant_admin_privilege For example: exec dbms_goldengate_auth.grant_admin_privilege('idr_user'); For Oracle 9i, Oracle 10g Release 1, and Oracle 11g Release 1, Data Replication cannot suppress Oracle database triggers. Does Data Replication support Oracle Transparent Data Encryption (TDE)? Yes. Data Replication can extract change data from the columns in Oracle source tables that are encrypted with Oracle TDE. Data Replication supports TDE with all Oracle encryption algorithms, including 3DES and AES with 128-bit, 192-bit, and 256-bit key lengths. Data Replication also supports TDE with MAC integrity checking and with SALT enhanced security. If your Oracle sources use Oracle TDE encryption of columns, you must specify the wallet with the master encryption key on the Runtime Settings > General view. Also, you must copy the following libraries from %ORACLE_HOME%/jlib subdirectory to the DataReplication_installation/lib subdirectory: oraclepki.jar osdt_cert.jar osdt_core.jar Note: Data Replication does not support TDE encryption of tablespaces. Does Data Replication extract DDL changes for Oracle sources? For Oracle-to-Oracle configuration, Data Replication can extract the ADD COLUMN and DROP COLUMN changes. To configure Data Replication to capture DDL changes, select Add and Drop options in the DDL capture box on the Map Columns tab. Data Replication does not support DDL capture for heterogeneous configurations. Does Data Replication extract change data from Oracle Express Edition sources? Yes. Data Replication can extract change data from Oracle Express Edition sources. Does Data Replication extract change data from Oracle redo logs on raw devices on Linux? Yes. Data Replication can extract change data from both Oracle online redo logs and archived logs that are on a raw device on Linux. Can Data Replication extract Oracle direct-path inserts and apply them to an Oracle target as direct-path inserts? Yes. Data Replication replicates direct-path inserts. Does the Oracle source database need to have supplemental logging enabled? Yes. Data Replication requires minimal global supplemental logging at the database level. To enable supplemental logging, use the following SQL statement: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; ALTER SYSTEM SWITCH LOGFILE; 12

13 Sybase Sources Which mechanism does Data Replication use to extract change data from Sybase ASE sources? Sybase ASE Extractor reads the transaction logs directly. Does Data Replication extract change data from Sybase ASE transaction logs on raw devices on Linux? Data Replication can extract change data from Sybase ASE transaction logs that are on a raw device on Linux. Data Replication cannot extract change data from Sybase ASE backup transaction logs that are on a raw device on Linux. Does Data Replication use the system tables to extract change data from Sybase ASE sources? Yes. Data Replication requires access to certain system tables to retrieve service information, but it does not modify or add data to the system tables. The Sybase ASE Extractor uses the master..sysusages and master..sysdevices system tables to get list of device files that contain the log segment. The Data Replication Console uses the master..syscolumns, master..systypes, master..sysusers, master..sysobjects, and master..sysindexes system tables to get metadata. Why is a DBSYNC_SYNC_LSN table required for Sybase sources? Because Sybase ASE does not provide a way to retrieve the current LSN from the database, InitialSync inserts a record for each target table in a service table. Data Replication creates the service table with the default name of DBSYNC_SYNC_LSN in the Sybase ASE source database. After you start change data replication, the Extractor uses these records to determine the initial LSN to pass to the Applier. The Applier only applies the changes that have an LSN greater than the passed LSN. Do I need to have access to transaction log to extract change data? Yes. The system user that runs the Sybase ASE Extractor must have read access to the transaction log. Why do I need to turn on replication mode for Sybase ASE sources? When you turn on replication mode for Sybase ASE sources, the transaction log contains the before and after images for all change data. Data Replication requires the before and after images to perform accurate replication of updates and proper handling of LOB data. Targets Is Data Replication Merge Apply mode supported for Microsoft SQL Server targets? No. Merge Apply is supported only for Greenplum, Netezza, Oracle, Teradata, and Vertica targets. Does Data Replication support SQL Server Express Edition as a target? Yes. Data Replication supports the Express Edition of SQL Server 2005, 2008, and 2008 R2 as a target. Also, Data Replication supports the Express Edition of SQL Server 2005, 2008, and 2008 R2 as a source. Which load utilities does InitialSync use to load data to Data Replication targets? The following table describes connectivity software that InitialSync uses to load data to different types of targets: Database DB2 for Linux, UNIX, and Windows Greenplum Connectivity Software ODBC connectivity or DB2 LOAD command LibPQ library 13

14 Database Microsoft SQL Server MySQL Netezza Oracle PostgreSQL Sybase ASE Teradata Vertica Connectivity Software Bulk Copy Program (BCP) load utility ODBC connectivity External tables using the ODBC connectivity DBlinks or Direct Load API LibPQ library ODBC connectivity TPT libraries LibPQ library Author Anna Turukina Technical Writer 14