Review the following information about Data Replication support for Netezza targets:
Because Netezza does not use binary datatypes, Data Replication does not support replication of these datatypes to Netezza targets. Before starting replication tasks for Netezza targets, ensure that the configuration does not map source columns that have binary datatypes to Netezza target columns.
Netezza does not support Updates of distribution columns. Data Replication can process Updates to distribution columns if these columns are part of a logical primary key or if you used the DISTRIBUTE ON RANDOM clause when you created the Netezza target table. If you replicate Updates to Netezza distribution columns that are part of a logical primary key, the Applier processes all Updates in the current apply cycle as a pair of Delete and Insert operations.
If you do not specify the RANDOM option or the column names in the DISTRIBUTE ON clause for a Netezza target table, Netezza distributes data by the first column in the CREATE TABLE statement, by default. If you do not have a preferred distribution column, Informatica recommends that you distribute tables on primary key columns to support Updates of the distribution columns and to provide better performance in Merge Apply mode.
When replicating a CREATE TABLE operation from a source to a Netezza target, Data Replication creates a table on the target and distributes data on the columns that are mapped to the primary key columns on the source. If the source table does not have a primary key definition, Data Replication uses the DISTRIBUTE ON RANDOM clause.
When replicating LOB data to Netezza targets, the Applier and InitialSync truncate the LOB data to the size that is specified in the
global.lob_truncation_size
runtime parameter.
On a Netezza target, the maximum number of tables that the Applier can load concurrently equals the number of Applier threads by default. You can specify the number of tables that the Applier can load concurrently in the
apply.load_sessions_per_load_pass
runtime parameter. To change this parameter value, Informatica recommends that you clear the
Create output as pipes instead of files
option on the
Runtime Settings
tab >
General
view. If this option is selected, each Applier thread can load only a single audit log table at a time.
Netezza supports a maximum of 31 concurrent Insert processes. To ensure that other applications can also load data to Netezza during data replication, the Applier limits the number of Netezza tables for concurrent load processing to a maximum of 20 tables.
By default, when InitialSync uses the native load utility to load source data to the target, the utility loads null values and empty strings as null values. Set the
global.nz_pg_empty_strings_as_null
runtime parameter to 0 to differentiate between empty strings and null values.