Preface
Overview of the Server Manager Command Line Interface
Usage Scenario: Using Server Manager CLI Commands to Run Replications
- Prerequisite Tasks for Running Replication Jobs from the Server Manager CLI
- Using the Server Manager CLI to Run Replications
  - Running a Scheduled Replication Job in Interactive Mode
  - Running a Scheduled Replication Job in Non-interactive Mode with Scripts
Command Reference

Command Line Interface for the Server Manager

9.7.0 HotFix 2

Back Next

Managing Database Supplemental Logging

Use the Server Manager CLI to manage database supplemental logging for DB2 for Linux, UNIX, and Windows, Microsoft SQL Server, and Oracle sources.

In Data Replication, database supplemental logging
is the logging of additional information in database log files by a relational source DBMS whenever an SQL change occurs on a source table. Data Replication requires this information to replicate some DDL operations, get the before images and after images for processing Updates, and resolve conflicts. The method of enabling supplemental logging depends on the source type:

For DB2 for Linux, UNIX, and Windows sources, supplemental logging is enabled by setting DATA CAPTURE CHANGES for each source table.

For Microsoft SQL Server sources, supplemental logging is enabled by setting Change Data Capture for each source table.

For Oracle sources, supplemental logging is enabled by adding columns to supplemental log groups for source tables.

You can manage database supplemental logging from the Data Replication Console and the Server Manager CLI. With Server Manager CLI commands, you can perform the following tasks:

Open the replication configuration that contains the source tables for which you want to issue commands for managing supplemental logging.

Enable database supplemental logging for source tables or columns in the following ways:

For DB2 source databases, set DATA CAPTURE CHANGES for additional tables.

For Microsoft SQL Server databases, enable Change Data Capture for additional tables.

For Oracle source tables, add columns to a supplemental log group.

Disable database supplemental logging for source tables or columns in the following ways:

For DB2 source tables, set DATA CAPTURE NONE.

For Microsoft SQL Server tables, disable Change Data Capture.

For Oracle source tables, remove columns from a supplemental log group.

Show the DB2 or SQL Server source tables or Oracle columns for which database supplemental logging is enabled.

Refresh the source database tables to reflect any changes that users made to the database options that enable or disable database supplemental logging.

Cancel the supplog add and supplog remove commands before you run the generated DDL statements that enable or disable database supplemental logging.

Run or save the generated DDL statements for enabling or disabling database supplemental logging.

By default, the Server Manager CLI commands perform these tasks for the mapped source tables. Some of the supplog commands also use optional parameters to perform these tasks for unmapped source tables.

Before you use the supplog commands, configure the following parameters in the DataReplication_installation/uiconf/default.cfg file on the computer where you use the Server Manager CLI:

Specify the following parameter to automatically use default values and cause the Server Manager CLI to stay in noninteractive mode:

use_default_values_during_saving=true

The Server Manager CLI needs to run in noninteractive mode to process the commands for managing database supplemental logging.

For DB2 and Oracle sources, if the target tables that you mapped in the configuration do not have primary keys, Data Replication creates a virtual index for these tables, by default, to properly process Updates and Deletes. The index contains all of the table columns. Alternatively, in the

DataReplication_installation/uiconf/default.cfg

file, you can specify the following parameter to disable the replication of Update and Delete operations:

pk_warning_option parameter=2

With this parameter set to 2, Data Replication replicates only Insert operations. Informatica recommends this setting to process the commands for managing database supplemental logging. The default value is 3.

The DataReplication_installation/uiconf/default.cfg file is also used by the Replication Configuration CLI.

Download Guide

Watch