IBM InfoSphere Change Data Capture

Version 6.3

IBM InfoSphere Change Data Capture Management Console, Version 6.3 Administration Guide

IBM InfoSphere Change Data Capture
Version 6.3

IBM InfoSphere Change Data Capture Management Console, Version 6.3 Administration Guide

Note Before using this information and the product it supports, read the information in “Notices” on page 609.

First edition This edition applies to version 6, release 3 of IBM InfoSphere CDC (product number 5724-U70) and version 6, release 2 of IBM InfoSphere CDC for z/OS (product number 5755-U96), and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2008. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
InfoSphere CDC architectural overview 1 Introducing the InfoSphere CDC Management Console interface . . . . . 3
About InfoSphere CDC Management Console . . Terminology changes . . . . . . . . . . Command changes . . . . . . . . . . . Functionality changes . . . . . . . . . . Connecting to datastores and working with subscriptions . . . . . . . . . . . . . Datastores view . . . . . . . . . . . Source Tables area . . . . . . . . . . Subscriptions view . . . . . . . . . . Mapping source and target tables . . . . . . Map Tables wizard . . . . . . . . . . Table Mappings view . . . . . . . . . Setting mapping details on a subscription . . . Edit Mapping Details view . . . . . . . Column Mappings tab . . . . . . . . . Filtering tab . . . . . . . . . . . . Translation tab . . . . . . . . . . . . Conflicts tab . . . . . . . . . . . . Operation tab . . . . . . . . . . . . User Exits tab . . . . . . . . . . . . Promoting subscriptions . . . . . . . . . Monitoring the performance of a subscription . . Subscriptions view (Monitoring perspective) . Table Mappings view (Monitoring perspective) Statistics view . . . . . . . . . . . Event Log view . . . . . . . . . . . Replication Diagram view . . . . . . . . . . . 3 3 4 4 Table Mappings view . . . . . . . . Mapping Details view . . . . . . . . Subscriptions view (Monitoring perspective) Replication Diagram view . . . . . . Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . 18 19 19 20 20

Before you start InfoSphere CDC Management Console . . . . . . . . 21
Logging in to Management Console (Connecting Access Server) . . . . . . . . . . . To log in to Management Console . . . . To change your login password. . . . . to . . 21 . . 21 . . 22

. 4 . 4 . 5 . 5 . 5 . 6 . 6 . 6 . 7 . 7 . 7 . 7 . 8 . 8 . 8 . 9 . 10 . 10 10 . 11 . 11 . 11

Setting up datastores and user accounts in Access Manager . . . . . 23
Managing datastores . . . . . . . . . . To add a new datastore . . . . . . . . To edit a datastore . . . . . . . . . . To delete a datastore . . . . . . . . . To copy a datastore . . . . . . . . . . To view the history of a datastore . . . . . To set connection parameters on a datastore . Managing user accounts . . . . . . . . . To add a new user . . . . . . . . . . To edit a user . . . . . . . . . . . . To delete a user . . . . . . . . . . . To copy a user . . . . . . . . . . . To change the existing role on a user account . To enable a System Administrator user account and datastore administration privileges . . . To view the history of a user account . . . . Assigning users to datastores . . . . . . . To assign a datastore to users . . . . . . To assign users to a datastore . . . . . . Managing datastore connections . . . . . . To delete a connection . . . . . . . . . To override default connection parameters on a datastore . . . . . . . . . . . . . Managing security on user accounts . . . . . To disable a user account . . . . . . . . To enable a user to change password at next login . . . . . . . . . . . . . . To override password expiration policy set in Management Console . . . . . . . . . To unlock a user account . . . . . . . . Setting password and account security policies on user accounts . . . . . . . . . . . . . To set complex passwords on user accounts . To enforce password history . . . . . . . To enforce password expiry . . . . . . . To enforce password locking on failed login attempts . . . . . . . . . . . . . To enforce new account expiry . . . . . . To display previous failed login attempts . . To display the last successful login . . . . . . . . . . . . . . . . . . . . . . . . 23 24 24 25 25 25 25 26 27 27 28 29 29 30 30 30 30 31 32 33

Introducing InfoSphere CDC Management Console with InfoSphere CDC Event Server . . . . . . . . . . 13
About InfoSphere CDC Event Server . . . . . . InfoSphere CDC Event Server as a target-only datastore . . . . . . . . . . . . . . . Mapping source tables on a subscription that targets a JMS message destination . . . . . . . . . Setting mapping details on a subscription that targets a JMS Message destination . . . . . . . XML Message tab . . . . . . . . . . . XML Settings tab . . . . . . . . . . . Column Mapping tab . . . . . . . . . . Filtering tab . . . . . . . . . . . . . Translation tab . . . . . . . . . . . . Operation tab . . . . . . . . . . . . . User Exits tab . . . . . . . . . . . . 13 13 14 14 15 15 15 16 16 16 16

. 33 . 34 . 34 . 34 . 34 . 35 . . . . . . . . 35 36 36 36 36 36 37 37

Using the InfoSphere CDC Management Console user interface . . 17
Datastores view . . . . . . . . . . . Subscriptions view (Configuration perspective)
© Copyright IBM Corp. 2008

. .

. 17 . 18

iii

Auditing user accounts, datastores, security policies, and general events . . . . . . . . . . . . To enable auditing . . . . . . . . . . . To generate an audit trail log . . . . . . . To generate a security log report . . . . . . To clear the log . . . . . . . . . . . . Creating list reports . . . . . . . . . . . To create a user list report . . . . . . . . To create a datastore list report . . . . . . . Commands for Access Server . . . . . . . . dmaddconnection—Adding a datastore connection to a user . . . . . . . . . . dmchangeconnection—Changing the connection parameters to a datastore . . . . . . . . . dmchangepassword—Changing the password on a user account . . . . . . . . . . . . dmcreatedatastore—Adding a datastore . . . . dmcreateuser—Adding a user . . . . . . . dmdeleteconnection—Deleting a datastore connection . . . . . . . . . . . . . . dmdeletedatastore—Deleting a datastore . . . dmdeleteuser—Deleting a user . . . . . . . dmdisableuser—Disabling a user account . . . dmenableuser—Enabling a user . . . . . . dmlistdatastoreusers—Generating a report list of users assigned to a datastore . . . . . . . dmlistuserdatastores—Generating a report list of datastores assigned to a user . . . . . . . dmlistusers—Listing user accounts . . . . . dmresetuser—Resetting a user account . . . . dmunlockuser—Unlocking a user account . . .

37 38 39 39 39 39 40 40 40 41 42 43 43 44 45 45 46 46 46 47 47 48 49 49

To delete a character encoding . To import the CSV template . . To export the CSV template . .

. . .

. . .

. . .

. . .

. . .

. 57 . 57 . 57

Setting up datastores for replication . . 59
Connecting to a datastore . . . . . . . . . To connect to a datastore . . . . . . . . Shutting down a datastore (InfoSphere CDC for Oracle) . . . . . . . . . . . . . . . To shut down a datastore . . . . . . . . Updating access parameters for a subscription . . To update access parameters for a subscription Setting system parameters on source and target datastores . . . . . . . . . . . . . . To add a system parameter . . . . . . . To modify a system parameter . . . . . . To delete a system parameter . . . . . . Creating aliases for a target datastore on a private network connection . . . . . . . . . . . To add an alias . . . . . . . . . . . To modify an alias . . . . . . . . . . To delete an alias . . . . . . . . . . . 59 . 59 . 60 . 60 . 60 60 . . . . . . . . 60 61 61 61 61 62 62 62

Upgrading subscriptions . . . . . . . 63
Upgrading Transformation Server subscriptions from version 5.3.4 to 6.2 . . . . . . . . To upgrade a subscription to Transformation Server for Microsoft SQL Server version 6.2 To transfer a bookmark to a new subscription To clear the log position for a subscription . . . . . . 63 . 63 . 64 . 64

Setting preferences in Management Console . . . . . . . . . . . . . . 51
Setting connection preferences . . . . . . . To specify a default port number . . . . . To specify outbound ports . . . . . . . To connect to databases automatically . . . Setting advanced preferences . . . . . . . To set timeout values . . . . . . . . . To allocate memory for Management Console . To verify that an automatic prompt for filtering tables is enabled . . . . . . . . . . . To disable an automatic prompt for filtering tables . . . . . . . . . . . . . . Setting prompt preferences . . . . . . . . To set prompt preferences . . . . . . . Setting statistics preferences . . . . . . . . To set the length of time for data retention . . To set the sample rate for data collection . . Setting the behavior of progress windows . . . To automatically close progress windows . . Showing usability hints . . . . . . . . . To show usability hints . . . . . . . . Setting view preferences . . . . . . . . . To set how subscriptions are grouped . . . To save project layouts automatically . . . . To set the number of events . . . . . . . Setting character encodings . . . . . . . . To add a character encoding . . . . . . . To modify a character encoding . . . . . . . . . . . . 51 51 52 52 52 52 53

Managing tables available for replication . . . . . . . . . . . . . 67
Updating, removing, and viewing tables for replication . . . . . . . . . . . . . To update the definition of a table . . . . To remove a table from Management Console To view the properties of a table . . . . . . . . . . . . 67 67 67 68

Setting notifications . . . . . . . . . 69
Selecting a notification handler . . . . . . . . Choosing a notification category and a message type Setting notifications for a datastore . . . . . . To set an email (MAPI) notification . . . . . To set an email (SMTP) notification . . . . . To set an email notification . . . . . . . . To set an email notification . . . . . . . . To set a notification for the TSDPRINT spool file To set a notification for an operator system log To set a notification for a UNIX system log . . . To set a notification using a user exit program . . To set a notification using a user exit program . . To set a notification using a user exit program . . To set a notification for a message queue . . . To filter a notification message . . . . . . . To copy notification settings . . . . . . . . Setting notifications for a subscription . . . . . To set notifications for a subscription . . . . . To view the datastore default notifications for a subscription . . . . . . . . . . . . . 70 71 72 72 73 73 74 74 74 75 75 75 76 76 77 77 77 77 78

. 53 . . . . . . . . . . . . . . . . . 53 53 54 54 54 54 55 55 55 55 55 55 56 56 56 56 57

iv

InfoSphere Change Data Capture Management Console: Administration Guide

Copying notifications for a subscription . . To copy notification settings . . . . . Setting latency thresholds and notifications . To set a latency threshold and notification

. . . .

. . . .

. . . .

78 78 78 79

Setting up and managing subscriptions 81
Using projects to organize your subscriptions . . . To add a new project . . . . . . . . . . To rename a project . . . . . . . . . . . To delete a project . . . . . . . . . . . Exporting and importing projects . . . . . . . To export projects . . . . . . . . . . . To import projects . . . . . . . . . . . Setting up subscriptions . . . . . . . . . . To add a subscription . . . . . . . . . . To modify a subscription . . . . . . . . . To delete a subscription . . . . . . . . . Specifying advanced settings for a subscription . . To specify a TCP host for a subscription . . . . To specify a firewall port for a subscription . . . To set propagation control on a subscription . . Searching for tables used in replication . . . . . To search for subscriptions that use a table in replication . . . . . . . . . . . . . . Setting up subscriptions for datastores outside of your organization . . . . . . . . . . . . To add a subscription for an external target datastore . . . . . . . . . . . . . . To modify a subscription for an external target datastore . . . . . . . . . . . . . . Copying subscriptions . . . . . . . . . . . To a copy subscription . . . . . . . . . . To copy a subscription for an external target datastore . . . . . . . . . . . . . . Setting properties for a subscription that targets IBM WebSphere DataStage . . . . . . . . . . . To specify batch size thresholds for a WebSphere DataStage subscription . . . . . . . . . To specify large object truncation size for a WebSphere DataStage subscription . . . . . Generating a WebSphere DataStage definition file for a subscription . . . . . . . . . . . . To generate a WebSphere DataStage definition file . . . . . . . . . . . . . . . . 81 82 82 82 82 82 83 83 83 84 84 84 85 85 85 86 86 86 87 87 88 88 88 89 89 90 90 90

To map a multi-member table using LiveAudit for AS/400 . . . . . . . . . . . . . To map multiple source tables to existing tables using LiveAudit . . . . . . . . . . . To map multiple source tables to new tables using LiveAudit . . . . . . . . . . . Mapping using WebSphere DataStage . . . . . To map a single source table to WebSphere DataStage using flat files . . . . . . . . To map a single source table to WebSphere DataStage using Direct Connect . . . . . . To map multiple source tables to WebSphere DataStage using flat files . . . . . . . . To map multiple source tables to WebSphere DataStage using Direct Connect . . . . . . Mapping using Adaptive Apply . . . . . . . To map a source table using Adaptive Apply To map multi-member source tables using Adaptive Apply on AS/400 . . . . . . . . Mapping to summarize data . . . . . . . . To map a source table to summarize data . . . To map multi-member source tables using Summarization on AS/400 . . . . . . . . Mapping to consolidate data (one-to-one) . . . . To map a source table to consolidate data (one-to-one) . . . . . . . . . . . . . To map multi-member source tables using Consolidation One-to-One on AS/400 . . . . Mapping to consolidate data (one-to-many) . . . To map a source table to consolidate data (one-to-many) . . . . . . . . . . . . To map multi-member source tables using Consolidation one-to-many on AS/400 . . . . Mapping to a datastore outside of your organization . . . . . . . . . . . . . . To map tables for a subscription on an external datastore . . . . . . . . . . . . . . Mapping to a JMS message destination using InfoSphere CDC Event Server . . . . . . . . To map multiple source tables to a JMS message destination . . . . . . . . . . . . . To map a single source table to a JMS message destination . . . . . . . . . . . . . To stage a source table . . . . . . . . .

102 104 105 106 106 107 108 109 110 110 112 113 114 115 117 117 119 121 122 124 126 126 127 127 129 131

Mapping tables . . . . . . . . . . . 91
Mapping using standard replication . . . . . . 91 To map similar source tables to similar target tables (One-to-One) . . . . . . . . . . . 92 To map a custom source table to a custom target table (standard) . . . . . . . . . . . . 93 To map multi-member source tables on AS/400 (standard) . . . . . . . . . . . . . . 95 To map multi-member source tables to existing target tables on AS/400 (one-to-one) . . . . . 97 To map multi-member source tables to new tables on AS/400 (one-to-one) . . . . . . . 99 Mapping using LiveAudit . . . . . . . . . 100 To map a single source table using LiveAudit 101

Managing table mappings . . . . . . 133
Remapping a source table . . . . . . . . . To remap a source table . . . . . . . . . To remap a source table (InfoSphere CDC Event Server) . . . . . . . . . . . . . . Changing the message destination . . . . . . To change the message destination of a table mapping . . . . . . . . . . . . . . Flagging a source table for a refresh . . . . . . To flag a source table for a refresh before mirroring . . . . . . . . . . . . . . Marking a table capture point on a source table To mark a table capture point on a source table before mirroring . . . . . . . . . . . Parking a table mapping from replication . . . . To park a table mapping from replication . . .
Contents

133 133 133 134 134 135 135 135 136 136 136

v

Changing the refresh order on a table mapping . . To change the refresh order on a table mapping Changing the replication method of a table mapping . . . . . . . . . . . . . . . To change the replication method of a table mapping . . . . . . . . . . . . . . Selecting a new journal table . . . . . . . . To select a new journal table . . . . . . . Setting members for replication . . . . . . . To select a member for replication . . . . . Deleting table mappings . . . . . . . . . . To delete a table mapping . . . . . . . . To delete a table mapping (InfoSphere CDC Event Server) . . . . . . . . . . . . Updating the definition of mapped source and target table in a subscription . . . . . . . . To update the definition of a source table . . . To update the definition of a target table . . .

137 137 137 138 139 139 140 140 140 140 141 141 142 142

To accumulate or deduct numeric data on a target column . . . . . . . . . . . Mapping source and target columns automatically To map columns automatically . . . . . Mapping initial values to target columns . . . To define an initial value for a target column Adding and mapping derived columns to target columns . . . . . . . . . . . . . . To add a derived column . . . . . . . To map a derived column to a target column To modify a derived column . . . . . . To delete a derived column . . . . . . .

. 159 160 . 160 . 161 161 . 162 . 163 164 . 164 . 165

Filtering rows and columns . . . . . 167
Filtering rows . . . . . . . . . To filter rows . . . . . . . . Selecting critical columns to filter rows . To select critical columns . . . . Filtering columns . . . . . . . . To filter columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 167 168 168 168 169

Customizing JMS message destination mappings . . . . . . . . 143
Creating an XML message . . . . . . . . To create an XML message . . . . . . . Importing and exporting XML files, schemas, and mapping projects . . . . . . . . . . . To import an XML, schema, or mapping definition file . . . . . . . . . . . To export an XML schema or mapping definition file . . . . . . . . . . . Building an XPath expression . . . . . . . To build an XPath expression . . . . . . Querying columns from other tables . . . . . To query columns from other tables . . . . . 143 . 143 . 144 . 145 . . . . . 145 146 146 147 147

Setting data translations on column mappings . . . . . . . . . . . . . 171
Setting data translations . . . . . . . To add a data translation . . . . . To modify a data translation . . . . To delete a data translation . . . . . Importing and exporting data translations . To import a data translation . . . . To export a data translation . . . . . . . . . . . . . . . . . . . . . . . . . 171 172 172 173 173 173 174

Setting multibyte and Unicode character set conversions . . . . . . 175
Setting multibyte conversions—common scenarios Converting multibyte character sets . . . . . . To convert multibyte character sets . . . . . Handling Unicode character encodings . . . . . To set handling for Unicode character encodings 175 175 176 176 177

Setting JMS message header properties . . . . . . . . . . . . . 151
Defining the JMS message header . . . . . . To add a JMS message header property . . . To add a custom JMS message header property To delete a custom JMS message header property . . . . . . . . . . . . . . Setting general runtime options . . . . . . . To enable InfoSphere CDC Event Server to trim text . . . . . . . . . . . . . . . . To disable InfoSphere CDC Event Server from differentiating between an empty string from a NULL value . . . . . . . . . . . . . To disable streamed transformation mode . . . Selecting a character encoding . . . . . . . . To select a character encoding . . . . . . . 151 151 152 152 153 153

Controlling row operations . . . . . 179
Suppressing the apply of row operations . . . . To suppress an insert, update, or delete . . . Preventing the audit of row operations . . . . . To prevent row operations from being audited To audit only the after image . . . . . . . Detecting conflicts on row operations . . . . . To detect conflicts on row operations . . . . Enabling the apply of soft deletes (InfoSphere CDC for Oracle) . . . . . . . . . . . . . . To enable InfoSphere CDC for Oracle to apply a soft delete . . . . . . . . . . . . . 179 179 180 180 180 181 181 182 182

154 154 154 155

Mapping columns . . . . . . . . . 157
Mapping source columns to target columns . . To map a source column to a target column . Mapping journal control fields to target columns To map a journal control field to a target column . . . . . . . . . . . . . Mapping expressions to target columns . . . To map an expression to a target column . . . 157 . 157 158 . 158 . 158 . 159

Controlling table operations . . . . . 183
Controlling the apply of refresh operations To keep all rows on a refresh . . . . To delete all rows on a refresh . . . . To audit rows on a refresh . . . . . Specifying SQL to control refresh operations To specify additional SQL after a refresh . . . . . . . . . . . . . . . . . . 183 183 184 184 184 185

vi

InfoSphere Change Data Capture Management Console: Administration Guide

To delete selected rows on a refresh .

.

.

.

. 186

Setting member identifiers . . . . . . 187
Setting member identifiers for multi-member source tables . . . . . . . . . . . To add a member identifier . . . . . . To modify a member identifier . . . . To delete a member identifier . . . . . . . . . . . . . 187 187 188 188

Setting conflict detection and resolution . . . . . . . . . . . . . 189
Resolving conflicts for source or target wins . To resolve conflicts for source row wins . To resolve conflicts for target row wins . . Resolving conflicts for largest or smallest value wins . . . . . . . . . . . . . . To resolve conflicts for largest value wins . To resolve conflicts for smallest value wins Resolving conflicts with user exits . . . . To resolve conflicts with user exit programs . . . . . . . . . 189 . 190 . 191 . . . . . 191 193 193 194 195

To configure a user exit for a Java class . . . . Configuring user exits for InfoSphere CDC for Oracle or InfoSphere CDC for Sybase . . . . . To configure a C shared library . . . . . . To configure a stored procedure (Oracle and Sybase) . . . . . . . . . . . . . . To configure a derived column or an expression that calls %STPROC (Oracle and Sybase) . . . Configuring user exits for InfoSphere CDC for AS/400 (version 6.2 and below) or InfoSphere CDC for z/OS . . . . . . . . . . . . . . . To configure a standard function . . . . . . Creating a custom data format for IBM WebSphere DataStage . . . . . . . . . . . . . . To create a custom data format for WebSphere DataStage . . . . . . . . . . . . .

214 216 216 217 218

219 219 220 220

Configuring user exits for InfoSphere CDC Event Server . . . . . . . . . 221
Overriding JMS message header properties . . To override JMS message header properties . Sending the XML message to a different JMS message destination . . . . . . . . . . To send the XML message to another JMS message destination . . . . . . . . . Creating XML output and applying XSLT to an XML message . . . . . . . . . . . . To create an XML message and apply XSLT . Sending XML messages to multiple JMS message destinations . . . . . . . . . . . . . To send an XML message to a different JMS message destination . . . . . . . . . Querying a Web service to access content . . . To query a Web service to access content . . Content based routing . . . . . . . . . To route the content of an XML message to another JMS message destination . . . . . . 221 . 222 . 223 . 223 . 224 . 225 . 226 . . . . 226 227 227 228

Starting and ending replication on subscriptions . . . . . . . . . . . 197
Starting mirroring on a subscription . . . . To start continuous mirroring . . . . . To start net-change mirroring . . . . . Starting a refresh on a subscription . . . . To start a refresh . . . . . . . . . Ending replication on a subscription. . . . To end replication . . . . . . . . . Sending XML messages to a JMS message destination . . . . . . . . . . . . To send an XML message to a JMS message destination or a staging target database. . . . . . . . . . . . . . . . . . 197 197 197 198 198 198 199

. 199 . 199

Promoting changes to subscriptions
Before you promote a subscription . . . . . Promoting subscriptions . . . . . . . . . To promote a subscription to a new environment . . . . . . . . . . . . To promote changes to an existing subscription Exporting and importing subscriptions . . . . To import a subscription from an XML file . To export a subscription into an XML file . .

201
. 201 . 202 . 202 204 . 205 . 205 . 205

. 229

Monitoring your subscriptions . . . . 231
About the state and status of your subscriptions Subscription state . . . . . . . . . . . Subscription status . . . . . . . . . . Displaying event messages during replication . . To show the event log for a subscription . . . To view event details . . . . . . . . . . To copy events . . . . . . . . . . . . To clear events . . . . . . . . . . . . To export events . . . . . . . . . . . Profiling the latency and throughput performance of your subscription . . . . . . . . . . . To start profiling the performance of a subscription . . . . . . . . . . . . . To stop profiling the performance of a subscription . . . . . . . . . . . . . To view and save plotted performance statistics of a subscription . . . . . . . . . . . Displaying a graphical view of your subscription 231 232 232 232 233 233 234 234 235 235 236 237 237 238

Configuring user exits . . . . . . . 207
Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB . . . . . . . . . . . . . . . . To configure for IDispatch COM DLL . . . . To configure for C or C++ . . . . . . . . To configure a stored procedure (Microsoft SQL Server version 5.3) . . . . . . . . . . . To configure a stored procedure (Microsoft SQL Server (version 6.0 and higher) and DB2 UDB (version 6.1 and higher)) . . . . . . . . To configure a derived column or an expression that calls %STPROC (Microsoft SQL Server 6.0 and above and DB2 UBD 6.1 and above) . . . 207 209 210 211

213

214

Using InfoSphere CDC with IBM WebSphere DataStage . . . . . . . 241
Contents

vii

Before configuring InfoSphere CDC for WebSphere DataStage . . . . . . . . . . . . . . Configuring InfoSphere CDC to send data to WebSphere DataStage . . . . . . . . . . Adding a subscription for WebSphere DataStage Mapping tables to WebSphere DataStage . . . Customizing your WebSphere DataStage table mappings . . . . . . . . . . . . . Generating a WebSphere DataStage Definition File . . . . . . . . . . . . . . . . Creating a custom data format for WebSphere DataStage . . . . . . . . . . . . . Starting replication in Management Console . . .

241 241 241 242 242 242 242 243

Using journal control fields for auditing replication activities . . . . 245
About journal control fields . . . . . . Commit Cycle ID (&CCID) . . . . . . Source RRN (&CNTRRN) . . . . . . Entry Type Code (&CODE) . . . . . . Entry Type (&ENTTYP) . . . . . . . Source Job Name (&JOB) . . . . . . Source Job Number (&JOBNO) . . . . Source Job User (&JOBUSER) . . . . . Journal Name (&JOURNAL) . . . . . Source Table Library (&LIBRARY) . . . Source Table Member Name (&MEMBER) . Source Table Name (&OBJECT) . . . . Source Program Name (&PROGRAM) . . Journal Sequence Number (&SEQNO) . . Source Server Name (&SYSTEM) . . . . Record Modification Time (&TIMESTAMP) Record Modification User (&USER) . . . About journal codes . . . . . . . . . Table Clear . . . . . . . . . . . Delete . . . . . . . . . . . . . Insert . . . . . . . . . . . . . Update Before . . . . . . . . . . Update After . . . . . . . . . . Translating journal codes into meaningful information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 246 246 247 247 248 249 250 250 251 252 252 253 254 254 255 256 257 257 258 258 258 259

. 259

Column functions . . . . . . . . . 261
Conventions in using column functions String functions . . . . . . . . Concatenation—%CONCAT . . . Lowercase—%LOWER . . . . . Left trim—%LTRIM . . . . . . Capitalization—%PROPER . . . . Character substitution—%REPLACE . Right trim—%RTRIM . . . . . . Substring—%SUBSTRING . . . . Uppercase—%UPPER . . . . . Date and time functions . . . . . . Century—%CENTURY . . . . . Current date—%CURDATE. . . . Current time—%CURTIME . . . . Current timestamp—%CURTMSTP . Conversion functions . . . . . . . Character conversion—%TOCHAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 262 262 263 263 264 265 266 267 268 269 269 270 271 273 274 274

Date conversion—%TODATE . . . . . . . Date and time conversion—%TODATETIME Number conversion—%TONUMBER . . . . Time conversion—%TOTIME . . . . . . . Conditional and variable functions . . . . . . Conditional–%IF . . . . . . . . . . . Variable—%VAR . . . . . . . . . . . Data functions . . . . . . . . . . . . . Before value—%BEFORE . . . . . . . . Current value—%CURR . . . . . . . . . Retrieve column—%GETCOL (DB2 UDB for iSeries) . . . . . . . . . . . . . . Retrieve column—%GETCOL (Dynamic SQL) Retrieve column—%SELECT . . . . . . . User exit functions . . . . . . . . . . . Stored procedure—%STPROC . . . . . . . User exit—%USER . . . . . . . . . . User exit—%USER (InfoSphere CDC for Microsoft SQL 5.x) . . . . . . . . . . . User Exit—%USERFUNC . . . . . . . . %GETCOL column function scenarios (DB2 UDB for iSeries) . . . . . . . . . . . . . . Retrieving a column from another table using the %GETCOL function (DB2 UDB for iSeries) . Performing an outer join using the %GETCOL function (DB2 UDB for iSeries) . . . . . . Nesting columns to join data using the %GETCOL function (DB2 UDB for iSeries) . . Combining columns using the %GETCOL function (DB2 UDB for iSeries) . . . . . . %GETCOL column function scenarios (Dynamic SQL) . . . . . . . . . . . . . . . . Retrieving a column using the %GETCOL function (Dynamic SQL) . . . . . . . . . Retrieving a column using the %GETCOL function without reading the same row from the table . . . . . . . . . . . . . . . Retrieving a column using nested %GETCOL functions (Dynamic SQL) . . . . . . . . Filtering rows using the %GETCOL function (Dynamic SQL) . . . . . . . . . . . . Publishing multiple derived columns using the %GETCOL function (Dynamic SQL) . . . . . .

275 277 279 280 282 282 283 284 284 284 285 288 293 297 297 298 302 303 305 305 306 306 306 307 307

308 308 309 309

System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below) . . . . . . . 313
General product system parameters AuthCode . . . . . . . DBMS . . . . . . . . . dbUser . . . . . . . . dllname . . . . . . . . DSN . . . . . . . . . NetServiceName . . . . . pwdencrypt . . . . . . . Startup Timeout . . . . . TSSrcCP . . . . . . . . TSTgtCP . . . . . . . . TCP_KEEPALIVE_SECS . . . WindowsAuthentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 314 314 314 314 314 315 315 315 315 316 316 316

viii

InfoSphere Change Data Capture Management Console: Administration Guide

Replication system parameters . . . . AutoRestart . . . . . . . . . . convertNotNullableColumns . . . . MirrorError . . . . . . . . . . RefreshError . . . . . . . . . . RefreshMode . . . . . . . . . Database translation log system parameters Cleanup Interval . . . . . . . . Cleanup Log Events . . . . . . . Cleanup Record Count . . . . . . LogCleanupMethod . . . . . . . Report Position Interval . . . . . . Synchronization Interval . . . . . . Commitment control system parameters . CommitmentControl . . . . . . . Commitment Group Size . . . . . RefreshBlock . . . . . . . . . SeparateCommits . . . . . . . . Event log system parameters . . . . . AllowEventLogClear . . . . . . . Multibyte character set system parameters. Unicode Handling . . . . . . . . Latency system parameters . . . . . . Deadband Percentage . . . . . . Monitor Sample Interval . . . . . . Notification system parameters . . . . convertNotNullableMsg . . . . . . DM_STATUS_INTERVAL . . . . . Heartbeat Timeout. . . . . . . . InvalidNumericMsg . . . . . . . Tracing system parameters . . . . . . CommTrace . . . . . . . . . . ProgramTrace . . . . . . . . . traceActive . . . . . . . . . . TraceLevel . . . . . . . . . . trcCleanup . . . . . . . . . . trcCOMM . . . . . . . . . . trcFiles . . . . . . . . . . . trcFncCalls . . . . . . . . . . trcJrlSync . . . . . . . . . . . trcReplStatus . . . . . . . . . trcScan . . . . . . . . . . . trcSQL. . . . . . . . . . . . trcThread . . . . . . . . . . . Data type system parameters . . . . . TrimVarchar . . . . . . . . . . Lock detection system parameters . . . DeadlockRetrys . . . . . . . . . DM_LOCK_DETECTION . . . . . DM_LOCK_TIMEOUT . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

317 317 317 318 318 319 319 319 320 320 321 322 322 323 323 324 324 325 325 325 325 325 326 326 329 329 329 330 331 331 332 332 332 333 333 333 333 334 334 334 334 334 334 335 335 335 335 335 335 336

mirror_commit_after_max_operations . . . . 339 mirror_commit_on_transaction_boundary . . . 340 refresh_commit_after_max_operations . . . . 340 Encoding system parameters . . . . . . . . 341 global_unicode_as_char . . . . . . . . . 341 Supplemental logging system parameters . . . . 342 mirror_logging_by_empty_triggers . . . . . 342 Disk resource system parameters . . . . . . . 343 mirror_memory_txqueue_total_mb . . . . . 343 mirror_memory_txqueue_each_mb . . . . . 343 global_memory_lob_cache_mb. . . . . . . 343 mirror_queue_for_buffers_between_cdc_threads_operations 344 Apply process system parameters . . . . . . 344 mirror_end_on_error . . . . . . . . . . 344 refresh_end_on_error . . . . . . . . . . 344 Authentication system parameters . . . . . . 345 global_ts_user_authentication_method . . . . 345

System parameters for InfoSphere CDC for Oracle (version 6.2 and below) . . . . . . . . . . . . . . 347
General product system parameters . . . . . . 347 CODE_PAGE . . . . . . . . . . . . 348 DEFAULT_ORACLE_HOME . . . . . . . 348 DEFAULT_ORACLE_SID . . . . . . . . 348 DEFAULT_ORACLE_USER . . . . . . . . 349 DM_COMMS_HOME . . . . . . . . . 349 D_MIRROR_HOME . . . . . . . . . . 349 D_MIRROR_LOG . . . . . . . . . . . 349 DM_DYNAMIC_PARAMETER_CHECK_INT 350 DM_MAX_MONITOR_ENTRIES . . . . . . 350 DM_TS_MAX_POOL_SIZE_MB . . . . . . 350 DM_TS_POOL_BLOCK_SIZE_MB . . . . . 351 <subscription>_MAX_POOL_SIZE_MB . . . . 351 <subscription>_POOL_BLOCK_SIZE_MB . . . 352 LD_LIBRARY_PATH . . . . . . . . . . 353 LIBPATH . . . . . . . . . . . . . . 353 ORACLE_HOME . . . . . . . . . . . 353 ORACLE_SID . . . . . . . . . . . . 353 PASSWORD . . . . . . . . . . . . . 354 PUBLISH_METADATA . . . . . . . . . 354 RLD_SYSTEM_TXQSIZE . . . . . . . . 354 <subscription>_TXQSIZE . . . . . . . . 355 SHLIB_PATH . . . . . . . . . . . . 355 STARTUP_TIMEOUT . . . . . . . . . . 355 TCP_KEEPALIVE_SECS . . . . . . . . . 356 USER . . . . . . . . . . . . . . . 356 Apply process system parameters . . . . . . 357 convertNotNullableColumns . . . . . . . 357 D_MIRROR_MIRROR_ERROR_LIST. . . . . 358 D_MIRROR_MIRROR_ERROR_STOP . . . . 358 D_MIRROR_REFRESH_ERROR_LIST . . . . 359 D_MIRROR_REFRESH_ERROR_STOP . . . . 359 DM_ADAPTIVE_APPLY_SOFT_DELETES . . . 359 DM_ADAPTIVE_APPLY_<SCHEMA>.<TABLENAME> 360 DM_ADAPTIVE_APPLY_MIMIC_SOURCE_OPERATION 360 DM_ARRAY_BIND_MAX . . . . . . . . 361 FILTER_NOCHANGE_UPDATES_FOR_AUDIT 361 NLS_LANG . . . . . . . . . . . . . 362 NLS_NCHAR . . . . . . . . . . . . 362
Contents

System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6.0 and above) . . . . . . . 337
Notification system parameters . . . . . . . 337 global_shutdown_after_no_heartbeat_response_minutes 337 global_conversion_not_possible_warning . . . 338 Maximize throughput system parameters . . . . 338 mirror_commit_after_max_transactions . . . . 339 mirror_commit_after_max_seconds . . . . . 339

ix

NOT_NULL_DATE_DEFAULT . . . . . . 362 TRIM_CHAR_TO_VARCHAR . . . . . . . 362 TRIM_VARCHAR_TO_VARCHAR . . . . . 363 TRIM_TO_NULL . . . . . . . . . . . 363 UNICODE_HANDLING. . . . . . . . . 364 Cascading replication system parameters . . . . 365 CASCADE_OMIT_TARGETS . . . . . . . 365 PREVENT_RECURSION. . . . . . . . . 365 Database journal (trigger) system parameters . . . 366 REPORT_POSITION_INTERVAL . . . . . . 366 MONITOR_PURGE_INTERVAL . . . . . . 367 MONITOR_REFRESH_PERIOD . . . . . . 367 Maximize throughput system parameters . . . . 367 COMMIT_GROUP_SIZE. . . . . . . . . 368 COMMIT_LEVEL . . . . . . . . . . . 368 COMMIT_INTERVAL . . . . . . . . . 369 MAINTAIN_TRANSACTION_CONSISTENCY 370 SYNCHRONIZATION_COMMIT_ GROUP_SIZE . . . . . . . . . . . . 370 SYNCHRONIZATION_INTERVAL . . . . . 371 TRANSACTION_GROUP_SIZE . . . . . . 371 TRANSACTION_INTERVAL . . . . . . . 372 TRANSACTION_RECORDS_THRESHOLD . . 372 Tracing system parameters . . . . . . . . . 372 D_MIRROR_SP_TRACE . . . . . . . . . 373 D_MIRROR_TRACE . . . . . . . . . . 373 D_MIRROR_TRACE_FILE_SIZE . . . . . . 373 D_MIRROR_TRACE_ON_ERROR . . . . . 374 DM_PRINT_DIAGNOSTICS . . . . . . . 374 D_MIRROR_ALARM_TRACE . . . . . . . 375 Refresh loader system parameters . . . . . . 375 DIRPATH_BUF_ROWS . . . . . . . . . 375 DIRPATH_BUF_SIZE . . . . . . . . . . 376 DIRPATH_CACHE_DATE_SIZE . . . . . . 377 DIRPATH_LOAD . . . . . . . . . . . 377 DIRPATH_LOGGING . . . . . . . . . 378 DIRPATH_DO_RECOVERY. . . . . . . . 378 User exit system parameters . . . . . . . . 379 D_MIRROR_SP_CONNECTION . . . . . . 379 DM_FROM_CODEPAGE_V4USEREXIT. . . . 379 DM_TO_CODEPAGE_V4USEREXIT . . . . . 380 Table mapping system parameters . . . . . . 380 TS_DELETE_ASSIGNED_OBJECTS_DURING_DESCRIBE 380 Notification system parameters . . . . . . . 381 convertNotNullableMsg . . . . . . . . . 381 DEADBAND_PERCENTAGE . . . . . . . 381 DM_STATUS_INTERVAL . . . . . . . . 384 HEARTBEAT_TIMEOUT . . . . . . . . 384 LOG_EMAIL_USERNAME . . . . . . . . 385 MONITOR_SAMPLE_INTERVAL . . . . . . 385 STATISTICS_INTERVAL . . . . . . . . . 386 Disk resource system parameters . . . . . . . 386 LOG_MAX_SIZE . . . . . . . . . . . 386

Notification system parameters . . . . . . . 388 events_max_retain . . . . . . . . . . . 388 global_shutdown_after_no_heartbeat_response_minutes 388 global_conversion_not_possible_warning . . . 389 Maximize throughput system parameters . . . . 389 mirror_commit_on_transaction_boundary . . . 389 mirror_sess_hist_age_threshold . . . . . . 390 mirror_src_ora_version . . . . . . . . . 390 refresh_commit_after_max_operations . . . . 390 userexit_max_lob_size_queue . . . . . . . 391 Database journal (trigger) system parameters . . . 391 mirror_journal_schema . . . . . . . . . 391 Encoding system parameters . . . . . . . . 391 global_unicode_as_char . . . . . . . . . 392 Disk resource system parameters . . . . . . . 392 mirror_queue_for_buffers_between_cdc_threads_operations 392 mirror_global_disk_quota_mb . . . . . . . 393 Apply process system parameters . . . . . . 393 convert_not_nullable_column . . . . . . . 393 global_max_batch_size . . . . . . . . . 394 mirror_end_on_error . . . . . . . . . . 394 refresh_end_on_error . . . . . . . . . . 394 refresh_allow_fast_loader . . . . . . . . 395 refresh_allow_jdbc_batch . . . . . . . . 395 mirror_expected_errors_list . . . . . . . . 395 refresh_in_unicode . . . . . . . . . . 396 trim_char_to_varchar . . . . . . . . . . 396 trim_varchar_to_varchar . . . . . . . . . 396 User exit system parameters . . . . . . . . 397 userexit_max_lob_size_kb . . . . . . . . 397

System parameters for InfoSphere CDC for Sybase (version 6.0 and below) . . . . . . . . . . . . . . 399
General product system parameters . . . . . CODE_PAGE . . . . . . . . . . . D_MIRROR_HOME . . . . . . . . . D_MIRROR_LOG . . . . . . . . . . DM_DYNAMIC_PARAMETER_CHECK_INT DM_MAX_MONITOR_ENTRIES . . . . . DSQUERY . . . . . . . . . . . . LD_LIBRARY_PATH . . . . . . . . . LIBPATH . . . . . . . . . . . . . PUBLISH_METADATA . . . . . . . . SYBASE . . . . . . . . . . . . . SYBASE_OCS . . . . . . . . . . . SHLIB_PATH . . . . . . . . . . . STARTUP_TIMEOUT . . . . . . . . . USER . . . . . . . . . . . . . . Apply process system parameters . . . . . convertNotNullableColumns . . . . . . D_MIRROR_MIRROR_ERROR_STOP . . . D_MIRROR_REFRESH_ERROR_STOP . . . FILTER_NOCHANGE_UPDATES_FOR_AUDIT NLS_LANG . . . . . . . . . . . . TRANSACTION_GROUP_SIZE . . . . . TRANSACTION_INTERVAL . . . . . . TRANSACTION_RECORDS_THRESHOLD . TRIM_CHAR_TO_VARCHAR . . . . . . TRIM_VARCHAR_TO_VARCHAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 400 400 400 400 401 401 401 402 402 402 402 403 403 403 404 404 405 405 405 406 406 407 407 407 408

System parameters for InfoSphere CDC for Oracle (version 6.3 and above) . . . . . . . . . . . . . . 387
General product system parameters . . . mirror_set_table_data_capture_timeout . mirror_asm_oracle_path . . . . . . . . . . . . . 387 . 387 . 388

x

InfoSphere Change Data Capture Management Console: Administration Guide

. . . . . 422 Commitment Control . . . . . . . . . . PointBase. . . . . . . 456 Contents . . 444 System parameters for InfoSphere Unicode Handling . . . . . . . . . . 421 Relational Database Directory Entry . 449 mirror_commit_on_transaction_boundary . . .3 and Latency system parameters . . . . . . 433 General product system parameters . . . . . . . . . 448 global_conversion_not_possible_warning . . . . . . . . . . D_MIRROR_BCP . . . . D_MIRROR_TRACE . . . . 455 trim_varchar_to_varchar . SYNCHRONIZATION_COMMIT_ GROUP_SIZE . . . . . 408 409 409 410 410 410 411 412 Supplemental logging system parameters . . . . . 450 refresh_commit_after_max_operations . . . . . . . . . 431 userexit_max_lob_size_kb . . . . . . . . . . COMMIT_INTERVAL . 419 Default Journal Library . . . . . . . . . . . . 413 Startup Timeout . . . . . . . . 431 Lock Timeout Value . . . . . . . . . . . . . . . . . . . . . 431 Notify Message Threshold . . . . MONITOR_SAMPLE_INTERVAL . . . . . . . . 414 TCP_KEEPALIVE_SECS . . . 429 Audit Filtered Transactions . . auto_configure_supplemental_logging . . 441 . . . . . . . LOG_EMAIL_USERNAME . . . convertNotNullableMsg . . . . SYNCHRONIZATION_INTERVAL . . . 436 . . DEADBAND_PERCENTAGE . . . . . 418 Cascading replication system parameters . . . . . . . . . . . . . . 435 Authorization Code . . . 443 . . D_HOME_BCP . . . . . . . . . . . . 443 . . . mirror_logging_by_empty_triggers . . . . . . 429 Row and column filtering system parameters . . . . . . . . . . . . . . 453 convert_not_nullable_column . 433 audit_auth_ code . . . . . . . . . 432 CDC for DB2 UDB. 412 Enable *MAXOPT3 Option . . 455 trim_char_to_varchar . . . . . 438 . . . Database journal (trigger) system parameters . . . . . . . 415 End on Error During Refresh . . 414 Allow Refresh While Active . . . . . . . . . . 442 . . 422 Commitment control system parameters . . . . . . . . . . . . . 450 Disk resource system parameters . . . 437 . . . 415 End on Error During Mirroring . . . . . . 435 xi . . . . 425 Monitor Sample Interval . . . . . 421 Data Origin Port . . 436 . . . . . 438 . . . 428 Default Date On Error . . 450 Encoding system parameters . . . . . 425 Deadband Percentage . . 433 . . . 428 Date and time column function system parameters 450 global_unicode_as_char . . . . . . . 420 Default Journal Name . . . . . . . . . . . . . . . . . . 419 Database journal (trigger) system parameters . . . COMMIT_GROUP_SIZE . . . . . . Refresh loader system parameters . . . . . . . . 436 . . . . DM_BCP_PACKET_SIZE . . . . . . . . . . . 451 mirror_global_disk_quota_mb . . . 452 mirror_queue_for_buffers_between_cdc_threads_operations Notify Message Queue Library . 430 Notify Message Queue . . . . . . . . . .2 and below) . 431 Lock detection system parameters . . . . . D_MIRROR_TRACE_ON_ERROR . . . . . . . 436 . . HEARTBEAT_TIMEOUT . . . . . . . . .TRIM_TO_NULL . . 453 mirror_end_on_error . . . . . . . 426 Messages on Invalid Numerics . . . . . . . . 421 Data Origin TCP/IP Name . . . . . . . . . . . . . . . . 418 Enable Cascading Replicates . . . . . . . . . 439 . . . . . . . 416 Refresh After Restore . 428 Numeric Column Validation . . . Cascading replication system parameters . . . . . . 429 Critical Column Filtering . 432 System parameters for InfoSphere mirror_expected_errors_list . . D_MIRROR_BCP_ROWS . . . 448 Maximize throughput system parameters . . . . . . . . . . . . . . . . . . . . . . 453 430 Apply process system parameters . . . . . . . . . 451 global_memory_lob_cache_mb. . 432 Teradata (version 6. . 443 Multibyte character set system parameters. . 442 . . . . . . . . . . . . . STATISTICS_INTERVAL . . . . 426 Messages on Column Not Null Capable . . . . . . . . . . . . DM_STATUS_INTERVAL . . . . . . 453 refresh_end_on_error . . . . . Maximize throughput system parameters . . 449 global_max_batch_size . . . . . . . . . . . . . . . . . . . . . . . 452 mirror_memory_txqueue_each_mb . . . PREVENT_RECURSION. . . . . . . 440 . LOG_MAX_SIZE . . . . . . . . . . . . . . . 445 above) . . . 434 System parameters for InfoSphere CDC for AS/400 (version 6. . . . . 447 events_max_retain . . . 414 Replication system parameters . . . . . . . . 442 . . . . . . . . . . . . . . . General product system parameters . . . 439 . . 421 Remote journal system parameters . . D_MIRROR_TRACE_FILE_SIZE . . 440 . . . . 420 Synchronization Interval . . . . . . 439 . . . . . . . Tracing system parameters . . . . . . . . 413 Record Format Check . .0 and below) . . . . . . . . 452 mirror_memory_txqueue_total_mb . 430 Event log system parameters . Disk resource system parameters . . . Notification system parameters . . . . . . . . 420 Report Position Interval . . . . . . . . . . and refresh_expected_errors_list . 425 Notification system parameters . . . . . REPORT_POSITION_INTERVAL . . . . . . . . D_MIRROR_FASTBCP . . . . . . . . . 437 . . . . . 441 . 444 CDC for Sybase (version 6. . . . . 445 Notification system parameters . . . . 427 Data type system parameters . . . . . . . . . . . . . . . . . 433 . . . . . 438 . . . . . . . . . . . . . . . 447 global_shutdown_after_no_heartbeat_response_minutes 426 Heartbeat Timeout. . . . . . . . 440 . . . . . . 427 Progress Status Interval . . .

. . . . . Lock detection system parameters . . use_uni_listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . make_fastload_log_file . . . . . . . 488 Teradata TPump system parameters . . . . . target_debug . . . . . . . . . . . . . . . . . . . . . . log_file_quota . . . . . . . fastload_in_whole . . . . . . . . . . . . . . . . . . . 484 mirror_memory_txqueue_each_mb . . . . . . tpump_logging . . . . . . . . . . . . . . . . . . . . . . . . . . fastload_backup_path . accessserver_udp_ listenport . agent_src_engine_socket_tmout . . . . . . . . dm_status_interval . . . . . . . . . tpump_script_params_file . . . 487 global_shutdown_after_no_heartbeat_response_minutes 487 global_conversion_not_possible_warning . . . . . . 490 mirror_tpump_script_val_file_name . . . . . . message_trace_level . . . . . . . . . . . . . . . . . . trace_on . . . . agent_src_engine_address . . . . . 482 Encoding system parameters . . . startup_timeout . . . agent_trace_in_message . . . . . . . . . . . . . . . . agent_udp_ listenport . . . . tpump_files_root_folder . . . . . target_initial_codepage . . . . . . . . . . refresh_commit_ block_size . . . . . message_handler_trace_level . Teradata TPump system parameters . . . . . . . . . tpump_arc_data_files . . fastload_path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fastload system parameters . . . . . . . . . . . . . . agent_max_connections_num . . . . . . . . . . . . . . . 485 mirror_end_on_error . . 483 global_unicode_as_char . . . . . . . . . . . dm_lock_detection. . . . . . . . . . . . . . Access Server system parameters . . . . . . . . . Commitment control system parameters . 484 mirror_queue_for_buffers_between_cdc_threads_operations 485 Apply process system parameters . . . . . . . . . . . . . . . . . . . agent_msg_resources_file . . log_total_quota . . . . . . . . . . . . Cascading replication system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . scrape_timeout . . . . . . .auth_ code . . . 487 Notification system parameters . . . . . . . . Latency system parameters . . . . . del_fastload_file . . . . monitor_sample_interval . . . . . . 456 456 456 457 457 457 457 457 457 457 457 458 458 458 458 458 458 458 459 459 459 459 459 459 459 460 460 460 460 460 460 460 460 460 461 461 461 461 462 463 463 464 464 464 465 465 466 466 467 467 467 468 468 468 469 469 469 470 470 471 471 heartbeat_timeout . . . . . . . . . . . 484 global_memory_lob_cache_mb. . . . . . . . . . . . . . . . . . . . . . . . . agent_message_version . db_password . 479 global_shutdown_after_no_heartbeat_response_minutes 479 global_conversion_not_possible_warning . . . . . . . . . . . . . . . . . . . 480 mirror_commit_after_max_transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 mirror_tpump_files_root_folder_path . . . . . . . . . . . . agent_jdbcpb_driver_net. . . . . . . . . agent_debug. . . . . . . . . . source_default_replication_type . . . . . . . agent_jdbcdb2_driver_net . . . . . . . . . . agent_trace_out_message . . . . . . . . . . . . source_default_active_refresh . . . . . . . . . . . . . . . . . . . . . . . Notification system parameters . . . . . . . . . . . . . . . . . . . . agent_jdbcdb2_driver . . . . . . . . . . . 490 xii InfoSphere Change Data Capture Management Console: Administration Guide . engine_ port . . dofastload . . . . Database translation log system parameters report_position_interval . . . cascade_replication . . debug . . . . . . . . . . . . . . . . . . . . . md_db_url . . . . . 484 mirror_memory_txqueue_total_mb . . . . . . tpump_max_file_size . . . . 481 mirror_commit_on_transaction_boundary . . . md_schema . . . . . . . . . . . . . . . . . . . . agent_assert . . . . . . db_user . . . 472 472 472 473 473 473 473 474 474 474 474 474 474 474 474 475 475 475 476 477 477 477 478 System parameters for InfoSphere CDC for DB2 UDB (version 6. . .2 and above) . ts_password . . . . . . trace_level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ts_product . . . . . . . Multibyte character set system parameters. . . . . . . . . . . . . . target_default_commit_level . . . . . . . . . . . . . . . 488 mirror_end_on_error . unicode_handling . . . . . . . . . 481 mirror_commit_after_max_seconds . . . commit_ interval . 489 mirror_tpump_max_file_size_mb . . . . 488 refresh_end_on_error . . tpump_ timeout . . . . . target_trace_physical_messages . . agent_jdbcpb_driver . . . . . . . dobatch . target_trace_logical_messages . . . . . target_refresh_number_of_errors_before_abort Tracing system parameters . . . . . target_assert . . . tpump_script_val_file. . agent_src_engine_port . . 485 refresh_end_on_error . . . scraper_trans_ num_limit . 482 refresh_commit_after_max_operations . . . . . . . . . . . . . . . . . . . 483 Disk resource system parameters . . . . . . . dm_lock_timeout . . . . . . . . target_mirror_number_of_errors_before_abort target_print_refresh_details . . . 481 mirror_commit_after_max_operations . . . . . 488 Apply process system parameters . . . . . . max_fastload_ file_size . . . . . . . commit_group_size . . . . . . . . . Replication system parameters . . . . . 485 System parameters for InfoSphere CDC for Teradata (version 6. . . . . . . 479 Notification system parameters . . . .1 and above) . . . . . . . 480 Maximize throughput system parameters .

. . . . . . . . . . sxt:padLeft . . . . 501 501 502 502 502 502 503 503 503 503 504 504 504 504 505 505 505 505 506 506 506 506 507 507 508 508 509 509 509 510 510 510 510 511 511 sxt:multiply . . . position . . . . . . . . . . . . . . . . . * Operator . . . round . . < Operator . . . . . . . . Change Role dialog box . . . . . sxtdb:lookup . . . . <= Operator . . . . . . . . . . . . / Operator . sxt:proper . . . . . . . . . . . . . . . . Connection Parameters dialog box Access Server Options . . . . . sxt:toUpperCase . . . . . . . . . . . . . . . . . 492 . sxt:getSequentialNum sxt:getSubField . . . . sxt:trim . 511 511 512 512 512 513 513 513 513 514 514 514 514 515 515 516 516 516 516 517 517 517 517 517 517 517 518 518 518 518 518 518 518 519 519 519 519 Dialog boxes . . . . . . . Select User dialog box . . . . . . . . . 498 refresh_end_on_error . . . Datastore tab . . . . . . . . . . . () parentheses Operator . . . . . . . . . . . . . transformations . . . . . . . . . . . . . . . . . . . . . . . . User List Report dialog box . . . . . sxt:getSysTime . . . . . . . . 497 Notification system parameters . 493 Notification system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . User tab . . . . . . . . div Operator . . . . number . . . . . + Operator . . . . . . . . . . . . stringLength . . . . . . . . . . . . . . . . . . . . . . . . . . Fastload system parameters . . . . . . . . . . . . Select Datastore dialog box . . . . . . . . . . . . . . . . . . . 498 mirror_end_on_error . . . . . . . . . . . . . . . . . . sxt:setDefault . . . . . . . . . . . true . . . . . . . . . . . . . . . . . . sxt:padRight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . History tab . . . . . . . . 501 XPath functions . New User dialog box . sxt:db-lookup . . . . . . . . . . . . formatNumber . . . . . 491 . . . . . . . sxt:toLowerCase . . . . . . . . . . . substringBefore . . . . . . sxt:filter . . . . . . contains . . Access Server Options dialog box Contents xiii . . . . . . . . . . . . . . . . . . > Operator . . . . . . . . . . . . . sxtdb:getPKSeq . . . . . . . . . sum . 499 Functions . . . . . . . . . . . . . . . . . . . Connection Parameters dialog box Copy Datastore dialog box . . . . . . . . . . . . . . startsWith . . . . . . sxt:divide . . . . . XPath expression operators . . . . . . . . . . . . . . . . . . . . . sxt:ifExist . . . . . . . . . . = Operator . . . . . . . . . 499 userexit_max_lob_size_kb . . . . . . . . . . . . . . . . . . . . . . . . . sxt:isEqual . . concat . . . . . . . . . . . . . . . . . mod Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . refresh_end_on_error . . . . . ceiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . normalizeSpace . XML objects (type III) . . . . . . . . . and Operator . . . User Properties dialog box . . . . . . . . . . data I) . . . . . . . sxt:getSysDate . . . . . . . . . . . . . . . . . . >= Operator . . . . . . [ ] Operator . . . . . . . . . string . . substringAfter . . . . . . . . . . . mirror_end_on_error . . sxt:groupConcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sxt:nodeConcat . . . . . . . . . . . global_conversion_not_possible_warning Apply process system parameters . . . . . . . . . . . . . 497 global_shutdown_after_no_heartbeat_response_minutes 497 global_conversion_not_possible_warning . substring . . . sxt:add . . . . . . . . . . . . . . . . . . . . . . . . . . . != Operator . . . . New Datastore dialog box . . . . . . . Transform extensions . . . . . . @ Operator . . . . sxt:ifReturn . . . . . . . 498 Apply process system parameters . . . 493 493 494 494 494 494 System parameters for InfoSphere CDC for WebSphere DataStage . . . . . . . . .Operator . . . . floor . . . . . . . . . . . . . . . . . . . . . . sxt:subtract . . . . History tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database functions . . . Using external Java objects in Simple string objects (type SQL data types (type II) . . 492 System parameters for InfoSphere CDC Event Server . . . . . . . . . refresh_max_fastload_file_size_mb . . . . . . . . . . . . . . . . . . . . . . 521 521 522 523 523 523 524 524 525 525 526 527 527 527 528 529 529 530 530 531 531 531 Datastore Management . . . . . . . . . . sxtdb:procCall . translate . . . . . . . . . . . . Copy User dialog box . . . . . . . . . . . . . . . . . Connection Management . . . . . . . . sxt:formatDate . . . . . . . . . . . . false . . . . . . . . . . . . userexit_max_lob_size_kb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 . . . . . .mirror_tpump_timeout_seconds . . . . . . . . . . Datastore List Report dialog box . . . . . 498 WebSphere DataStage system parameters . . . . . . . . . // Operator . User Management . . . . . . . . . . . . . . . . . . . . . . . Edit Datastore dialog box . . . . . or Operator . . . . . . . not . . . . . .

. . . . . . Transfer Bookmark dialog box . . . . . . . . Specify New Target page (Promote Subscription wizard) . . . . . . . Change Message Destination dialog box . . . . . . . . . . Promoting changes . . Specify External Target Datastore dialog box Notification dialog box . . . . . . . Datastore Properties dialog box . . . . . . Review New Table page . . . . . . . . . . Select Column dialog box . . . . . . . . . Set Member Replication dialog box . . . . Message Destinations dialog box . . . Review Settings page (Copy Subscription wizard) . . . Latency Threshold dialog box . . . . Modify Member Identifier dialog box . . . . Advanced Subscription Settings dialog box . . . . . . . . . . . . Specify External Target page (Import Subscription wizard) . . . . Specify External Target page (Promote Subscription wizard) . . Modify Encoding dialog box . . . . . . . . . . . . . . . . . . . . . . . . . Promote to a New or Existing Subscription page Specify New Source page (Promote Subscription wizard) . . . . XML message mappings . . . . . . 558 558 558 558 559 559 560 560 560 560 561 561 561 561 562 562 562 563 563 563 563 564 564 565 Wizards . . . . . . . . . . . . . . . . . . . . . . . . . Select Target Table dialog box . 567 Create Table wizard . . . . . . . Define New Subscription page . . . . . . . . . Monitoring . . . . . . . . . . . . . Mark Table Capture Point for Mirroring dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Member Identifier Dialog Box . . . . Copy Subscription wizard . . . Structure tab . . Advanced Target Settings dialog box . . Summarize Column dialog box . . . . . . . Save Changes dialog box . . . . . . . . . . . . . . . . . . . . . . . . . Notification dialog box . Delete Table Mappings dialog box . . . Specify New Target page (Copy Subscription wizard) . . . . . . . Map Columns Automatically dialog box . . . . . . . . . . . . . . . . . . . . . Upgrade Subscriptions dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unique Indexes dialog box . . Data translation . . . Change Example Table dialog box . . . Flag for Refresh dialog box . . . Table operations . . Source tables . . . . . . . . . . . . . . . Subscriptions . . . . . . . . . . . . . . . . Clear Log Position dialog box . . . . Delete Selected WHERE Clause dialog box . . . . . . . . . . . . . . . . . . . . Column Encodings dialog box . . . . . . . . . . . . . . . . . . Import Subscription wizard . . . . . . . . . . . . . . . Table mappings . . . . . . . . . . . Park (Do not replicate) dialog box . Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional SQL dialog box . . . . . . . . . . . . . . . . . . . Start Refresh dialog box . . . . Column mappings . . Specify Owner and Name page . . . . . . . . . . . . . . . Review New Table page . . . . . . . Add Encoding dialog box . . . . . . . New Subscription dialog box . . . . . . Change Refresh Order dialog box . . . . . . . . . . . . . Table Properties dialog box . Replication Tables dialog box . . . . . . Define Primary Key Name and Order page . . . . . . Filter Messages dialog box . . Review Promotion Settings page . 567 567 567 568 568 568 568 569 569 570 570 570 571 571 571 572 572 572 572 573 573 573 574 xiv InfoSphere Change Data Capture Management Console: Administration Guide . . . . . . . . . Copy Column Properties dialog box . . . . . . . . Define Columns page . . . . . . . . Define Derived Column dialog box . Naming Options dialog box . Message Destination dialog box . . . . . . . . . . Add Column dialog box . . . . . . . . . . . . . . . . . . Subscription Properties dialog box . . . . . . . . . . .Preferences . . . Review Settings page (Import Subscription wizard) . . Modify Column dialog box . . . . . . . . . . Aliases tab . . . . Specify New Target page (Import Subscription wizard) . . . . . . . Define Translation dialog box . Replication Method dialog box . . Specify Key dialog box . . Subscriptions tab . Specify New Source page (Copy Subscription wizard) . . . . . . . Update Access Parameters dialog box . . . . Update Target Table Definition dialog box . . . . . . . Retry Datastore Connection dialog box . . . . . . . . . . . . . Update Source Table Definition dialog box . . Import to a New or Existing Subscription page Specify New Source page (Import Subscription wizard) . . . . . Specify Owner and Name page . Compare XML dialog box . . . . . . Copy Notification Settings dialog box . . . . . . . . . . Filter Columns dialog box . . . . . . . . . . . . Expression Builder dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . Datastores . . . . . . Specify External Target Page (Copy Subscription wizard) . . . . . . . Add or Modify System Parameter dialog box General tab . . . . . . . . . . . . . . . Replace Expressions Variables dialog box . . . . . . . . . . . . WebSphere DataStage Properties dialog box . . . . . . . . . . . . . . . . System Parameters tab . . . . . . Target tables . . 534 534 535 535 536 536 537 537 537 537 538 538 539 539 539 539 540 540 541 541 542 542 543 543 543 544 544 544 545 545 546 546 546 546 547 547 548 548 549 549 550 550 550 551 551 551 551 552 552 553 553 553 554 554 555 555 555 556 557 557 557 Define Expression dialog box . . . . . . . . . . . . . . . . . . Add or Modify Audit Column dialog box . . Set Initial Value dialog box . . Select Target Owner or Library dialog box . . Promote Subscription wizard . . . . . . . . . . . . . . . . Define Columns page . . . Filter Tables dialog box . Import Options dialog box . . . . . . . . .

. . . . . . . Summarization mapping type . . . . . . . . . . . . . WebSphere DataStage Flat File page (WebSphere DataStage Automatic) . Define Audit Columns page (LiveAudit Automatic) . . . . Set Replication Method page (Adaptive Apply) Review Mappings page (Adaptive Apply) . . . . . . . . . . . . . . . Select Mapping Type page (WebSphere DataStage Automatic) . . . . . . . . . . . . Review Mappings page (Standard) . . . . . . . . . Select Source Table page (Standard) . . . . . . . . . . . . Select Mapping Type page (LiveAudit Automatic) . . . Review Mappings page (WebSphere DataStage Automatic) . Select Target Table page (Standard) . . . . . . Review Mappings page (WebSphere DataStage Custom) . . . . . . Consolidation one-to-many mapping type . . . . . . . Select Existing or Create New Target Tables page (One-to-One) . . . . Select Target Table page (Consolidation one-to-one) . . . . . . . . . . . . Select Target Table page (Consolidation one-to-many) . . . . . . . . . . . . . . . . . . . Select Source Tables page (Consolidation one-to-many) . . . . . . . . . . . . . . . Standard mapping type . Select Source Tables page (Mapping to an external target datastore) . . . . . . . Review Mappings page (Consolidation one-to-many) .Map Tables wizard . . . Select Mapping Type page (Consolidation one-to-one) . . . . . . . . LiveAudit mapping type (Automatic) . . . . . . . . . . . . . Map Source Tables to Existing Target Tables page (One-to-One) . . . . . . . . . Select Source Tables page (One-to-One) . . . One-to-One mapping type . . Select Source Tables page (WebSphere DataStage Automatic) . Select Mapping Type page (Mapping to an external target datastore) . . . . . . . . . . . . Select Mapping Type page (Standard) . . . . . . Mapping to an external target datastore mapping type . . Set Replication Method page (Summarization) Review Mappings page (Summarization) . . . . . . . . Select Source Tables page (Summarization) . . . . . Select WebSphere DataStage Connection Method page (WebSphere DataStage Automatic) . . Consolidation one-to-one mapping type . . Select Source Tables page . . . Select Mapping Type page (Adaptive Apply) Select Source Tables page (Adaptive Apply) . . . . . . Select Owner for New Target Tables page (LiveAudit Automatic) . . . . 574 576 576 577 577 577 577 578 578 579 579 579 579 579 580 580 580 581 581 581 581 582 582 582 582 582 582 583 583 584 584 584 585 585 585 586 586 587 587 587 587 Select Source Tables page (LiveAudit Custom) Select Target Table page (LiveAudit Custom) Review Mappings page (LiveAudit Custom) . . . . . . . . . . Contents 588 588 588 589 589 589 589 589 590 591 591 591 591 591 592 592 592 593 593 593 594 594 594 594 595 596 596 596 596 596 597 598 598 598 598 598 599 599 600 600 600 600 600 601 xv . . . . Select Source Tables page (WebSphere DataStage Custom) . . Select Target Table page (Summarization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Source Tables page (Consolidation one-to-one) . . Specify Key page (Adaptive Apply) . . . . . . . . . . . . LiveAudit mapping type (Custom) . . . . . . . . . . . . . . . . . . Message Destination mapping type (Automatic) Select Mapping Type page (Message Destination) . . Select WebSphere DataStage Connection Method page (WebSphere DataStage Custom) . WebSphere DataStage Direct Connect page (WebSphere DataStage Automatic) . . . . . . Review Mappings page (One-to-One) . Select Owner for New Target Tables page (One-to-One) . . . . . . Name Target Tables page (LiveAudit Automatic) Review Mappings page (LiveAudit Automatic) Complete Mappings page (LiveAudit Automatic) . . . . . . . . . . . . . Specify Key page (Consolidation one-to-many) Set Replication Method page (Consolidation one-to-many) . . . Specify Key page (Consolidation one-to-one) Set Replication Method page (Consolidation one-to-one) . . . . . . . . . WebSphere DataStage mapping type (Automatic) . . . Select Mapping Type page (Summarization) . . WebSphere DataStage mapping type (Custom) Select Mapping Type page (WebSphere DataStage Custom) . . . . . . . Specify Key page (Standard) . . . . . . . . . . . . . . . . . . . . Select Mapping Type page (LiveAudit Custom) Define Audit Columns page (LiveAudit Custom) . . . . . Map Source Tables to Existing Target Tables page (LiveAudit Automatic) . . WebSphere DataStage Direct Connect page (WebSphere DataStage Custom) . . . . . . . . . . . . WebSphere DataStage Flat File page (WebSphere DataStage Custom) . . . . . Set Replication Method page (Standard) . . . . . . . . . . . . . . Adaptive Apply mapping type . . Review Mappings page (Consolidation one-to-one) . . . . . Specify Key page (Summarization) . . . . . . . . Complete Mappings page (One-to-One) . Set Replication Method page (One-to-One) . . . . . . . . . . . . . . . . . Select Target Table page (Adaptive Apply) . . . . . . . . . . . . . . . Message Destination page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Source Tables page (LiveAudit Automatic) Select Existing or Create New Target Tables page (LiveAudit Automatic) . Name Target Tables page (One-to-One) . . . . . . . . . . . . . . . . . . . . . Select Mapping Type page (One-to-One) . . . . . . . . Message Content page . . . . . Select Summarization type page . . . . . . . . . . . . . . . . Select Mapping Type page (Consolidation one-to-many) . . . . . . .

. . . . . . . . . . . . Message Content page . . . . . . . . . 602 602 . . . GROUP BY Clause page . . Other Tables wizard . . . . . . . . . . . . . . . ORDER BY Clause page . . . 609 Trademarks . . . . . . . . 602 602 602 603 604 604 604 Select Table page . . . . . . . . . . 605 605 605 606 606 Notices . . . . . . . . .Review Mappings page . . . . . . . . . . . . . . . . . . . SELECT Clause page . . . . Select Source Tables page . . . . . . . . . . . Define Table Location page . . . . . . . . Message Destination page . . . . . . . . . . . . . . . . . . WHERE Clause page . . 611 xvi InfoSphere Change Data Capture Management Console: Administration Guide . . . . . . . Message Destination mapping type (Custom) Select Mapping Type page (Message Destination) . . . . . . . . Review Mappings page . . . . .

InfoSphere CDC Management Console User—the name specified in an InfoSphere CDC Management Console log in process on a client workstation (for example. These processes are also defined in Access Manager perspective so that you can connect to the same datastores in InfoSphere CDC Management Console. As a InfoSphere CDC administrator. gsmith). you can define InfoSphere CDC users in Access Manager and assign one of four roles to each InfoSphere CDC user.InfoSphere CDC architectural overview The following diagram illustrates the key components of IBM® InfoSphere™ Change Data Capture. InfoSphere CDC. Access Server—a client workstation where a set of background processes direct requests received from InfoSphere CDC Management Console on other client © Copyright IBM Corp. 2008 1 . Each role determines the InfoSphere CDC Management Console operations that can be applied by a InfoSphere CDC user to a replication configuration. DBMS —the source or target database. Datastore—an InfoSphere CDC process on a source or target server that accepts requests from an instance of Access Server and communicates with the datastore replication engine to initiate and manage replication activity. You can work only with those databases that InfoSphere CDC supports as a source or target of replicated data. Datastore replication engine processes on source and target servers are created when you install InfoSphere CDC. The key components of the InfoSphere CDC architecture are described below: Datastore Replication Engine—an InfoSphere CDC process that sends or receives replicated data. or more simply. Datastore processes on source and target servers are created when you install InfoSphere CDC.

Processes running on Access Server accept requests only from known InfoSphere CDC users. The processes running on Access Server are created during InfoSphere CDC Management Console installation. Auto-discovery provides a way for Access Manager to recognize. InfoSphere CDC Management Console—an interactive application that you can use to configure and monitor replication. Management Console also includes an event log and a monitor. all available datastores on the local subnetwork. You can have multiple instances of Access Server in your working environment. It allows you to manage replication on various servers. After you have setup replication. and initiate refresh and mirroring operations from a client workstation. Use Management Console after creating datastores in the Access Manager perspective . upon startup. The monitor provides the necessary support to continuously monitor replication operations and latency. To establish a connection. You can create datastores and other InfoSphere CDC users in the Access Manager perspective in Management Console and these are associated with Access Server.workstations to the appropriate datastores. 2 InfoSphere Change Data Capture Management Console: Administration Guide . These processes also return information back to the applications. The event log allows you to examine generated InfoSphere CDC event messages. specify replication parameters. you must know the name of the workstations where Access Server processes are running and provide appropriate security information. you may be able to connect to one of several Access Servers from InfoSphere CDC Management Console. Management Console can be closed on the client workstation without affecting active data replication activities between source and target servers. The monitor in Management Console is intended for time-critical working environments that require continuous analysis of data movement. In this case. and communicate only with known datastores. Diagrams depicting components of your replication configuration are constructed through direct manipulation of graphical objects.

© Copyright IBM Corp. and monitor replication processes. you will learn: “About InfoSphere CDC Management Console” “Terminology changes” “Command changes” on page 4 “Functionality changes” on page 4 “Connecting to datastores and working with subscriptions” on page 4 “Mapping source and target tables” on page 5 “Setting mapping details on a subscription” on page 6 “Promoting subscriptions” on page 9 “Monitoring the performance of a subscription” on page 10 About InfoSphere CDC Management Console InfoSphere CDC Management Console is an intuitive graphical user interface (GUI) that lets you create subscriptions and manage your replication environment. Management Console includes the same features as Enterprise Administrator. In this section. but provides an integrated view of your source and target data sources. You can specify tables for replication. include custom business logic. set up data transformations. Terminology changes InfoSphere CDC now uses the term v datastore in place of replication agent v source and target in place of publisher and subscriber v notifications in place of alerts and alarms v source tables and target tables in place of publication tables and subscription tables v table mappings in place of table assignments v mapping types in place of assignment types v row filtering expression in place of row selection expression v expression in place of derived expression v translation in place of value translation However. 2008 3 . you may still encounter the old terms in some InfoSphere CDC products and documentation. Monitoring and replication configuration are consolidated in a single GUI.Introducing the InfoSphere CDC Management Console interface This section is intended for users of Enterprise Administrator that want to upgrade to InfoSphere CDC Management Console.

Management Console connects to your datastores automatically. manually add tables to a subscription. Management Console automatically. you had to add tables to a catalog. v adds tables to a subscription when you map tables v performs a describe from the source datastore to the target datastore when you have mapped source and target tables. after connecting to a datastore and making your source tables available for replication. For example. Management Console provides a unified view of the datastores you have access to. you can create a new subscription and (instead of manually adding tables to a subscription and then performing a describe) associate a source datastore and a target datastore to the subscription.Command changes Management Console uses the command v Add or Remove Tables in place of Manage Publications v Update Source Table Definition in place of the Re-Add Table. and Re-assign process for updating metadata of source tables v Update Target Table Definition in place of Re-assign to update the metadata of target tables v Map Tables in place of Assign Functionality changes To eliminate the publisher-subscriber model in the user interface and align the product to a subscription-centric experience. create a new subscription. 4 InfoSphere Change Data Capture Management Console: Administration Guide . About connection to datastores By default. You can also connect to a datastore manually by disabling the Connect to Datastores Automatically check box. Therefore. update the definition of a source table. and then perform a describe to send this information to the subscriber-side. or change the properties of a subscription Connecting to datastores and working with subscriptions In Enterprise Administrator. See also: “Datastores view” “Source Tables area” on page 5 “Subscriptions view” on page 5 Datastores view Use the Datastores view to identify the datastores you can connect to and make source tables available for replication. after connecting to a replication agent. you had to configure publisher-side properties and subscriber-side properties. Describe. This option is available on the Connection page of the Edit → Preferences menu. on the publisher-side.

Access parameters for datastores are set in Access Manager. Management Console also displays Unknown target datastores when you do not have permissions to them in Access Manager. Related concepts “Connecting to a datastore” on page 59 “Setting connection preferences” on page 51 “Updating. You can add or remove source tables from replication. the processing of mapping source tables to target tables was referred to as an Assign. or because the target datastore resides outside of your organization or department.Source Tables area Depending on the datastore selected. Unknown datastores Management Console displays Unknown source datastores when you do not have permissions to them or you are disconnected from it. and viewing tables for replication” on page 67 Subscriptions view Use the Subscriptions view to create new subscriptions or view existing subscriptions. See also: “Map Tables wizard” on page 6 “Table Mappings view” on page 6 Introducing the InfoSphere CDC Management Console interface 5 . update the definition of a source table (after changing the structure of a source table). map tables between them. Related concepts “Using projects to organize your subscriptions” on page 81 “Setting up subscriptions” on page 83 “Setting up subscriptions for datastores outside of your organization” on page 86 Mapping source and target tables In Enterprise Administrator. Management Console provides a Map Tables wizard that automates the mapping process. Organize subscriptions into projects You can organize subscriptions into different projects. Management Console refers to this command as Map. You must be connected to the datastore to view the tables. and edit mapping details. You must be connected to both a source and target datastore to view existing table mappings in a subscription. Management Console also displays any disconnected target datastores. Management Console displays the hostname and IP address of unknown target datastores. and view table properties in this area. the Source Tables area lists the source tables you have made available for replication. removing.

replication method. You can also view the mapping type. To view incomplete table mappings. These properties are now consolidated in the Edit Mapping Details view of Management Console. Setting mapping details on a subscription In Enterprise Administrator. See also: “Edit Mapping Details view” on page 7 “Column Mappings tab” on page 7 “Filtering tab” on page 7 6 InfoSphere Change Data Capture Management Console: Administration Guide . in the Table Mappings view. If you did not assign a source table to a target table in Enterprise Administrator. you can map a source table to a target table that does not share the same structure or similar table names as the source table. and columns with the same or compatible data types. – One-to-One—lets you map multiple source tables to multiple target tables (available in Enterprise Administrator as Standard Replication) – LiveAudit—lets you map multiple source tables to multiple target tables when you want to track source table operations v Custom—lets you map a source table to a target table that is customized in some way. Related concepts “Mapping using standard replication” on page 91 “Mapping using LiveAudit” on page 100 Table Mappings view Use the Table Mappings view to see a list of mapped source and target tables within a subscription. when you choose Standard mapping type. In Enterprise Administrator. You can also access this view from the Monitoring perspective. See “Monitoring the performance of a subscription” on page 10. Management Console lists this as an incomplete table mapping. right-click and select the Show Incomplete Mappings option. or properties for a subscribed publication table on the Publishers tab. Show Incomplete Table Mappings By default. The wizard organizes mapping types into two areas v Automatic—lets you perform a bulk assignment of multiple source tables to multiple target tables that have the same table structure. you were able to set properties for an assigned subscription table on the Subscribers tab. similar table names. you did this after adding a table to the subscription on the publisher-side.Map Tables wizard Use the Map Tables wizard to map multiple source tables to multiple target tables or map tables one at a time using a custom mapping type. Management Console displays only assigned table mappings. For example. and status of each table mapping. Set Replication Method You must now choose a replication method before you finish mapping source and target tables.

or both. a target table. Column Mappings tab Use the Column Mappings tab to v map source columns to target columns v create a derived column on the source table v v v v build custom expressions and map to target columns map accumulation and deduction expressions for summarization mapping types map journal control fields map source and target columns automatically Related concepts “Mapping source columns to target columns” on page 157 “Mapping journal control fields to target columns” on page 158 “Mapping expressions to target columns” on page 158 “Mapping source and target columns automatically” on page 160 “Mapping initial values to target columns” on page 161 “Adding and mapping derived columns to target columns” on page 162 Filtering tab Use the Filtering tab to v define a row-filtering expression to include or exclude rows from replication (row selection expression in Enterprise Administrator) v filter columns v enable critical column selection Related concepts “Filtering rows” on page 167 “Selecting critical columns to filter rows” on page 168 “Filtering columns” on page 168 Translation tab Use the Translation tab to v set translations (value translations in Enterprise Administrator) v set encoding conversions (character handling in Enterprise Administrator) v set multibyte character encoding conversions (this is a new feature and only available in specific platforms and versions of InfoSphere CDC) Related concepts “Setting data translations” on page 171 “Converting multibyte character sets” on page 175 “Handling Unicode character encodings” on page 176 Introducing the InfoSphere CDC Management Console interface 7 .“Translation tab” “Conflicts tab” on page 8 “Operation tab” on page 8 “User Exits tab” on page 8 Edit Mapping Details view Use the Edit Mapping Details view to configure details for a mapped source table.

Related concepts “Resolving conflicts for source or target wins” on page 189 “Resolving conflicts for largest or smallest value wins” on page 191 “Resolving conflicts with user exits” on page 194 Operation tab Use the Operation tab to specify the row-level or table-level operations you want InfoSphere CDC to apply on a target table when there is a corresponding row-level or table-level operation on the source table. then you can select None.Conflicts tab Use the Conflicts tab when you want InfoSphere CDC to detect conflicts on target columns and resolve them. In Enterprise Administrator. you had to specify row-level or table-level options on separate tabs of the Subscription Table Properties dialog box—the Table tab and the Row tab. If you do not want InfoSphere CDC to detect conflicts on target columns. Related concepts “Suppressing the apply of row operations” on page 179 “Preventing the audit of row operations” on page 180 “Detecting conflicts on row operations” on page 181 “Controlling the apply of refresh operations” on page 183 “Specifying SQL to control refresh operations” on page 184 User Exits tab Use the User Exit when you want InfoSphere CDC to detect conflicts on target columns and resolve them for v identify the name and type of user exit you want InfoSphere CDC to call v specify at which event or action you want InfoSphere CDC to call the user exit (either before or after a row-level or table-level operation) In Enterprise Administrator. then you had to specify the name of the user exit (User Exit Before or User Exit After) in either the Table tab or Row tab of the Subscription Table Properties dialog box. Related concepts 8 InfoSphere Change Data Capture Management Console: Administration Guide . if you wanted InfoSphere CDC to call the user exit before or after a specific event (either before or after a row-level or table-level operation). These options are now consolidated in the Operation tab of Management Console. then you can select None. v source row wins v target row wins v largest value wins v smallest value wins v user exits If you do not want InfoSphere CDC to detect conflicts on target columns. These options are now consolidated in the Event and Actions area in the User Exits tab of Management Console.

Use the Promote Subscription wizard to v promote to a new subscription—the wizard creates a copy of the subscription with changed configuration details. Also. If you need to send the XML to another department or organization. v promote changes to an existing subscription—the wizard creates a copy of the subscription with the same configuration details as a previously promoted subscription. the wizard lets you either import the changes into a new subscription or overwrite an existing one. In Enterprise Administrator. Both the commands Export Subscription and Import Subscription are available on the Subscription menu. About comparing XML You can compare the XML of the new subscription with the original. You can promote a subscription using the Promote Subscriptions command available in the Subscription menu. if you have configured items on your source tables or target tables then you can promote these to datastores in the new environment.2 and below) or InfoSphere CDC for z/OS” on page 219 Promoting subscriptions The manual subscription promotion process available in Enterprise Administrator has been replaced with a Promote Subscription wizard in Management Console. The promotion wizard can also create copies and backups of InfoSphere CDC replication configurations. As an alternative to promoting subscriptions. You can also export the subscription directly to an XML file from the Promote Subscription wizard Related concepts “Promoting subscriptions” on page 202 Introducing the InfoSphere CDC Management Console interface 9 . This wizard provides an integrated view of your subscription and automates the process of promoting subscription changes from development to test to production. you can export the XML to your local computer. Use the Import Subscription wizard when you have exported the subscription as an XML file on your local computer and made changes to this file. You can also make copies of a subscription to a new subscription using Copy Subscription wizard. you had to promote the publisher-side and subscriber-side of the subscription. Promote Subscription wizard The Promote Subscription wizard lets you promote subscription changes from development to test to production. you can also use export and import subscriptions. The wizard saves your changes and you can reapply these when you need to promote to an existing subscription. When you are ready to import the XML file into Management Console.“Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 “Configuring user exits for InfoSphere CDC for Oracle or InfoSphere CDC for Sybase” on page 216 “Configuring user exits for InfoSphere CDC for AS/400 (version 6.

and source and target datastores for each subscription. latency. Use the table mappings view in the Monitoring perspective to reset a log position (update the bookmark) flag tables for a refresh park tables from replication change the refresh order change the replication method update table definitions delete table mappings view the properties of source and target tables v reset a log position (update the bookmark) v flag tables for a refresh v park tables from replication v change the refresh order v change the replication method v update table definitions v delete table mappings v view the properties of source and target tables Related concepts 10 InfoSphere Change Data Capture Management Console: Administration Guide . See also: “Subscriptions view (Monitoring perspective)” “Table Mappings view (Monitoring perspective)” “Statistics view” on page 11 “Event Log view” on page 11 “Replication Diagram view” on page 11 Subscriptions view (Monitoring perspective) The Monitoring perspective lists the replication state and status. You can view the performance of a subscription in the Monitoring perspective. Use the Subscriptions view in the Monitoring perspective to v start continuous or net-change mirroring on a subscription v start a refresh of the target table v end replication v show the Table Mappings view to control replication v show the Event Log view to monitor the state and status of a subscription v show the Statistics view to monitor the latency and throughput of a subscription Related concepts “Starting mirroring on a subscription” on page 197 “Starting a refresh on a subscription” on page 198 “Ending replication on a subscription” on page 198 Table Mappings view (Monitoring perspective) You can open the table mappings view in the Monitoring perspective so you can manage and control the replication of table mappings.“Exporting and importing subscriptions” on page 205 Monitoring the performance of a subscription In Enterprise Administrator. The functionality of this application is integrated into the Management Console interface. you were able to monitor the performance of a subscription using the Enterprise Administrator Monitor.

you were able to monitor events using the Enterprise Administrator Event Log Viewer. Use the Event Log view to monitor source and target replication and activities on your source and target datastores. The functionality of this application is integrated into the Management Console interface. Related concepts “Displaying event messages during replication” on page 232 Replication Diagram view In Enterprise Administrator. You can also double-click on each event to read details about each event in a separate window. v throughput. The functionality of this application is integrated into the Management Console interface. Related concepts “Displaying a graphical view of your subscription” on page 238 Introducing the InfoSphere CDC Management Console interface 11 . Management Console automatically creates a replication diagram for each project in your replication configuration. the number of operations applied to the target table (measured in bytes and number of operations) Related concepts “Profiling the latency and throughput performance of your subscription” on page 235 Event Log view In Enterprise Administrator. you were able to create a diagram using the Enterprise Administrator Monitor. You can monitor the following statistics v latency. the amount of a time a subscription takes to replicate data to the target table.“Flagging a source table for a refresh” on page 135 “Marking a table capture point on a source table” on page 135 “Parking a table mapping from replication” on page 136 “Changing the refresh order on a table mapping” on page 137 “Changing the replication method of a table mapping” on page 137 “Setting members for replication” on page 140 “Deleting table mappings” on page 140 Statistics view The Statistics view monitor latency and throughput on a subscription. Use the Replication Diagram view to see a topological view of your replication configuration.

12 InfoSphere Change Data Capture Management Console: Administration Guide .

Introducing InfoSphere CDC Management Console with InfoSphere CDC Event Server This section is intended for users of Management Console that want to transform data to XML and send data to a JMS message destination with InfoSphere CDC Event Server In this section. Before you can use InfoSphere CDC Event Server to transform table data in XML. When InfoSphere CDC Event Server detects a row-level operation (insert. it sends the XML message to the JMS message destination. You can then continue to add a subscription that uses InfoSphere CDC Event Server as the target datastore. you will learn: “About InfoSphere CDC Event Server” “InfoSphere CDC Event Server as a target-only datastore” “Mapping source tables on a subscription that targets a JMS message destination” on page 14 “Setting mapping details on a subscription that targets a JMS Message destination” on page 14 About InfoSphere CDC Event Server InfoSphere CDC Event Server receives replicated row-level operations (inserts. updates. v Inventory levels are running low on a particular product—Detect a low inventory and generate an XML message which some other application could interpret and automatically place a new order. you must install and setup a InfoSphere CDC source product that can scrape row-level operations (inserts. deletes) from your source database and transforms these rows into XML. The following are some examples of the kinds of business events that you can define: v A new customer sale has been entered into the source database—You may want InfoSphere CDC Event Server to send an XML message to a JMS application which will generate an event to different departments. v Credit card balance changes significantly in a short period of time—You may want to track this and notify the fraud department with real time information about the credit card changes. you can map source columns to XML elements and attributes. This means that InfoSphere CDC Event Server can only receive row-level and table-level operations already replicated from another supported InfoSphere CDC product that you have installed. InfoSphere CDC Event Server as a target-only datastore InfoSphere CDC Event Server is a target-only product. You must install another InfoSphere CDC product and connect to this datastore so that you can select the source tables you want to make available for replication. and deletes) from your source database. update. © Copyright IBM Corp. When you start mirroring and if there is a row-level operation on your source table. or a delete). Using InfoSphere CDC Management Console. InfoSphere CDC Event Server receives and applies the row-level operation to the XML document which is sent to a JMS message destination (queue or topic). updates. 2008 13 .

the Translation tab. removing. You may want to map your source table to a target staging table in order to customize the source table outside of your production database in some way before InfoSphere CDC Event Server converts the replicated rows into XML. by mapping the source table to a staging database. When you map a source table to a message destination. InfoSphere CDC Event Server depends on the staging database (instead of your production database) to receive and transform replicated rows into XML. the Filtering tab. This XML message is sent to a JMS application supported by InfoSphere CDC Event Server. See also: 14 InfoSphere Change Data Capture Management Console: Administration Guide . In addition to the existing mapping details that you can configure with other InfoSphere CDC products you install. Also. The Message Destination Mappings mapping type option is available in the Map Tables wizard. you can reduce performance overhead on your production database. and the User Exits tab are available for configuration with InfoSphere CDC Event Server.Related concepts “Connecting to a datastore” on page 59 “Updating. Management Console provides additional configuration details available only with subscriptions created with InfoSphere CDC Event Server: v XML message tab v XML settings tab As with other InfoSphere CDC products. Note: The Column mappings tab and the Operations tab are only available if you have mapped your source table to a target staging table. When you enable the One table mapping of any type option in the Map Tables wizard and choose Standard. the wizard lets you map your source table to a target table available in an embedded staging database provided with InfoSphere CDC Event Server. Management Console provides another mapping type that is only available when you create a subscription that targets a JMS message destination using InfoSphere CDC Event Server. Related tasks “To map multiple source tables to a JMS message destination” on page 127 “To stage a source table” on page 131 Setting mapping details on a subscription that targets a JMS Message destination Management Console lets you create an XML message for subscriptions that target JMS message destinations. and viewing tables for replication” on page 67 “Setting up subscriptions” on page 83 Mapping source tables on a subscription that targets a JMS message destination In addition to the existing mapping types available with other InfoSphere CDC products you install. InfoSphere CDC Event Server provides an embedded staging database as a temporary repository for your source table before it is transformed to XML. InfoSphere CDC Event Server receives the row-level operation and transforms this row into XML. You can also map your source table to a target staging table.

you can decide on the source columns you want to map (or unmap) from columns in the target staging table. you can map your source table to a target staging table in order to send a copy of the source table to the staging database. Related concepts “Creating an XML message” on page 143 Introducing InfoSphere CDC Management Console with InfoSphere CDC Event Server 15 . v You want to reduce performance overhead on your production database. a copy of your source table is sent to the staging database. build XPath expressions. Before mapping your source table to a JMS message destination. import and export mapping projects. Related concepts “Defining the JMS message header” on page 151 “Setting general runtime options” on page 153 Column Mapping tab Use this tab to map source columns to columns in a target staging table. import and export XML schemas. Because you have mapped your source table to a target staging table. and mapping projects” on page 144 “Building an XPath expression” on page 146 “Querying columns from other tables” on page 147 XML Settings tab Use this tab to set JMS message header properties and set general runtime options. Related concepts “Creating an XML message” on page 143 “Importing and exporting XML files. This lets you control which columns you want to include or exclude for replication and therefore the kind of data you want to include or exclude for InfoSphere CDC Event Server to XML. InfoSphere CDC Event Server receives replicated rows from the staging database (instead of your production database) and transforms these rows into XML. and query columns from other tables if required. when you start replication. schemas. This setup reduces performance overhead on your production environment. In this scenario.“XML Message tab” “XML Settings tab” “Column Mapping tab” “Filtering tab” on page 16 “Translation tab” on page 16 “Operation tab” on page 16 “User Exits tab” on page 16 XML Message tab Use this tab to create your XML message. You may want to map your source table to a target staging table when: v You want to customize the source table outside of your production database. InfoSphere CDC Event Server provides an embedded staging database as a temporary repository for your source table before it is converted into XML. This tab is only available if you have you have mapped your source table to a target staging table using the Standard mapping type in the Map Tables wizard. Using the Column Mappings tab.

update. and deletes) and table-level operations (truncate/clear) to the target staging table. Related concepts “Creating an XML message” on page 143 “Controlling row operations” on page 179 “Controlling table operations” on page 183 User Exits tab Use this tab configure a user exit for InfoSphere CDC Event Server. This tab is only available if you have you have mapped your source table to a target staging table using the Standard mapping type in the Map Tables wizard. update. and/or run the user exit before or after applying a row-level operation to the JMS message destination. When you add a data translation and start replication. User exits define a set of actions that you want InfoSphere CDC Event Server to run either before or after applying a row-level operation. the supported InfoSphere CDC source product translates values from the source column into the new value you specified for the mapped target column. If you have only mapped your source table to a JMS message destination. you can use this tab to add a data translation between your source and target staging columns and/or set encoding conversions. InfoSphere CDC Event Server then inserts the translated value into an XML document. InfoSphere CDC Event Server can run the user exit before or after applying a row-level operation to the target staging table. You can only set a data translation on a subscription for source columns that are mapped to target staging columns.“Mapping columns” on page 157 Related tasks “To stage a source table” on page 131 Filtering tab Use this tab to include or exclude rows or columns for replication. Row-level operations include an insert. or a delete. Related concepts “Filtering rows and columns” on page 167 Translation tab Depending on how you have mapped your source table. Related concepts “Setting data translations on column mappings” on page 171 “Setting multibyte and Unicode character set conversions” on page 175 Operation tab Use this tab to control how InfoSphere CDC Event Server applies row-level operations (insert. then you can only set encoding conversions for any multibyte character sets in your source table. Depending on how you have mapped your source table. Related concepts “Configuring user exits” on page 207 16 InfoSphere Change Data Capture Management Console: Administration Guide .

log in toInfoSphere CDC Management Console and click Configuration > Datastores. v Configure notifications on your source or target datastores. Preferences allow you to control the behavior of InfoSphere CDC Management Console. and transforming your data. For example. Related concepts “Logging in to Management Console (Connecting to Access Server)” on page 21 “Setting up datastores for replication” on page 59 © Copyright IBM Corp. After logging in to Management Console you will see two perspectives. In the Configuration perspective. Tables made available for replication are contained in a datastore.Using the InfoSphere CDC Management Console user interface InfoSphere CDC Management Console is composed of a number of windows or tabs that are referred to as perspectives and views. from which you can access a number of different views. mapping your tables. 2008 17 . you can use the different views to configure your replication environment by connecting to your datastores. Configuration and Monitoring. Each datastore represents the database to which you want to connect and acts as a container for your tables. In the Monitoring perspective. v Configure properties on your datastores such as system parameters. In this view. you can choose whether you want to connect to datastores automatically after logging in to InfoSphere CDC Management Console. In this section. creating subscriptions. you can do the following: v Connect to datastores. different views allow you to initiate replication and monitor your replication activity. To access this view. you will learn: “Datastores view” “Subscriptions view (Configuration perspective)” on page 18 “Table Mappings view” on page 18 “Mapping Details view” on page 19 “Subscriptions view (Monitoring perspective)” on page 19 “Replication Diagram view” on page 20 “Setting Preferences” on page 20 Datastores view Datastores are logical entities that represent the data files and processes required to accomplish data replication.

Use the Table Mappings view to see a list of mapped source and target tables within a subscription. you can do the following: v Add and configure subscriptions v Create. To access this view. and status of each table mapping v v v v v Flag a source table for refresh before mirroring Set a log position on a source table Park a table mapping from replication Change the refresh order on a table mapping Change the replication method of a table mapping Related concepts “Setting up and managing subscriptions” on page 81 “Mapping tables” on page 91 “Managing table mappings” on page 133 18 InfoSphere Change Data Capture Management Console: Administration Guide . After defining a subscription in InfoSphere CDC Management Console. Subscriptions use datastores as the source or target of replicated data. select the subscription with the table mappings to display this view. The table mappings that you create with the wizard are displayed in this view. and status of each table mapping. replication method. export. you can use the Map Tables wizard to map source and target tables. It contains details of the data that is being replicated and how the source data is applied to the target. Subscriptions can contain as many table mappings as necessary. After you have done this.Subscriptions view (Configuration perspective) A subscription is a connection that is required to replicate data between a source datastore and a target datastore. In this view. replication method. In this view. and import projects for your subscriptions v Promote subscriptions Related concepts “Logging in to Management Console (Connecting to Access Server)” on page 21 “Setting up and managing subscriptions” on page 81 “Promoting changes to subscriptions” on page 201 Table Mappings view You cannot display the Table Mappings view until you create a subscription and map your tables. You can also access this view from the Monitoring perspective. and the number of table mappings you create depends on how many source tables you want InfoSphere CDC to replicate to the target system. You can also view the mapping type. you can do the following: v View a list of mapped source and target tables within a subscription v View the mapping type. log in toInfoSphere CDC Management Console and click Configuration > Subscriptions.

and delete a data translation. this view contains operational features for subscriptions that allow you to connect to datastores. In this view. v Configure user exits. log in toInfoSphere CDC Management Console and click Monitoring > Subscriptions. you can do the following: v Monitor the state and status of your subscription v Display the event messages in the Event Log view v Profile the latency and throughtput performance of your subscription in the Statistics view v Start or end replication on a subscription Using the InfoSphere CDC Management Console user interface 19 . In addition. start or end replication. you can do the following: v Customize the kind of information you want to map to target columns in a subscription. display subscription properties. v Set member identifiers for multi-member source tables. v Control the truncation of the target table in response to a table-level clear or refresh operation so that all or some of the rows are preserved. In this view. v Set how a target table responds to changes made on the source table. v Include or exclude rows or columns for replication. To access this view. modify. and display table mappings for subscriptions. Related concepts “Setting up and managing subscriptions” on page 81 “Mapping tables” on page 91 “Mapping columns” on page 157 “Filtering rows and columns” on page 167 “Setting data translations on column mappings” on page 171 “Setting multibyte and Unicode character set conversions” on page 175 “Controlling row operations” on page 179 “Controlling table operations” on page 183 “Setting member identifiers” on page 187 “Setting conflict detection and resolution” on page 189 “Configuring user exits” on page 207 Subscriptions view (Monitoring perspective) This view alllows you to monitor and analyze replication activities for each subscription so that you can diagnose potential problems. After you have done this. v Add. v Specify how InfoSphere CDC converts character sets on source columns during replication. right-click a subscription and select Edit Mapping Details to display this view. v Configure conflict detection and resolution.Mapping Details view You cannot display the Mapping Details view until you create a subscription and map your tables.

The graphical nature of this view is what differentiates it from the Subscriptions view in the Monitoring perspective which uses a table format to display information about your replication environment. Preferences. v Control how statistics are collected for your replication environment. The operational tasks that you can perform in this view are identical to the Subscriptions view (Monitoring perspective). v Set timeout values. and set prompts for filtering large numbers of tables. Related concepts “Setting preferences in Management Console” on page 51 20 InfoSphere Change Data Capture Management Console: Administration Guide . click Edit. v Control the behavior or views. Preferences allow you to do the following: v Specify port preferences for Access Server and connection preferences for datastores.v v v v Refresh a Subscription Connect to a datastore Show table mappings for a subscription Display subscription properties Related concepts “Monitoring your subscriptions” on page 231 “Starting and ending replication on subscriptions” on page 197 “Connecting to a datastore” on page 59 Replication Diagram view This view uses schematic diagrams to visually represent the relationship between subscriptions and datastores in your replication configuration. log in toInfoSphere CDC Management Console and click Monitoring > Replication Diagram. allocate memory. v Control the behavior of progress windows. Setting Preferences Preferences allow you to control certain aspects of the behavior ofInfoSphere CDC Management Console. To access Preferences. v Set prompt preferences. To access this view.

For more information. type or select the host name (system name) or full IP address of the workstation running Access Server. For more information. you can add users and datastores. Your system administrator can set your user name and password in the Access Manager perspective. 5. Navigate to the programs menu and start Management Console. See also: “To log in to Management Console” “To change your login password” on page 22 To log in to Management Console 1. Using the Access Manager perspective in Management Console. After creating a datastore. see or contact your InfoSphere CDC system administrator. In this section. 3. make sure that you have installed Access Server. 2. © Copyright IBM Corp. In the Access Manager perspective in Management Console. Management Console users can connect to it.Before you start InfoSphere CDC Management Console Before you can start and log in to Management Console. Note: If you want to log in using the default port number. Type the TCP/IP port number in the Port Number box. The level of permissions depends on the role you want to assign to a user. you need to do the following: Add datastores—datastores are required to access the tables in your database. Add users—as an InfoSphere CDC system administrator. 2008 21 . you are connecting to Access Server. but you can only connect to one server at a time. Access Server is the server application that controls access to your replication environment. The default port number was specified in the Edit → Preferences menu. Ensure that your InfoSphere CDC system administrator has added you as a user to an existing datastore in Management Console. you need to add users and provide them with permissions for your datastores. In the Server Name list. click Default. The password is case-sensitive. see your Access Server and Management Console Installation Guide. Type your user name in the User Name box. You can have multiple instances of Access Server in your working environment. Type your password in the Password box. see Access Server and Management Console Installation Guide. 4. For more information on installing Access Server. 6. you will learn: “Logging in to Management Console (Connecting to Access Server)” Related concepts “Setting up datastores and user accounts in Access Manager” on page 23 Logging in to Management Console (Connecting to Access Server) When you log in to Management Console.

Type the current password in the Current® password box. Type and confirm the new password in the New password and Confirm password boxes.Related tasks “To add a new user” on page 27 To change your login password 1. 3. 22 InfoSphere Change Data Capture Management Console: Administration Guide . 2. Click File > Access Server> Change Password.

Users can be assigned to different roles that are distinguished by different levels of access into Management Console. security policies. In this section. copy. and delete datastores—adding a datastore in Management Console means that you are in the process of making an installation of InfoSphere CDC and the database you want users to replicate to or from available for connection by other users. Only users you have assigned to a datastore can connect to the datastore. you can add. You must be a System Administrator that can manage datastores and user accounts to create datastores and users in the Access Manager perspective. you must be a System Administrator that has the privilege to manage datastores and user accounts. As a System Administrator. you must specify information about the database and provide database connection parameters so that users can connect to the datastore. you will learn: “Managing datastores” “Managing user accounts” on page 26 “Assigning users to datastores” on page 30 “Managing datastore connections” on page 32 “Managing security on user accounts” on page 34 “Setting password and account security policies on user accounts” on page 35 “Auditing user accounts. 2008 23 . modify.Setting up datastores and user accounts in Access Manager InfoSphere CDC Access Manager is an integrated component of Management Console that provides a central point of administration for system administrators to manage datastores and user accounts. When adding a new datastore. Note: To be able to work in the Access Manager perspective. and delete datastores in the Access Manager perspective of Management Console. The Access Manager perspective also provides security options that you can set on user accounts. © Copyright IBM Corp. You can then assign these users to datastores and set database connection parameters in order to provide users with access to an installation of InfoSphere CDC and the database available for replication. Use the Datastore Management view to: v Add. and general events” on page 37 “Creating list reports” on page 39 “Commands for Access Server” on page 40 Managing datastores A datastore represents the InfoSphere CDC installation and the database made available for replication. modify. v Assign users to a datastore—assigning users to a datastore gives them access to an installation of InfoSphere CDC and the ability to connect to the database that you have made available for replication on the server. datastores.

Click File > Access Server > Properties. 5. 7. this returns the datastore properties including the type of server where you have installed InfoSphere CDC and the version number of the product. 3. the date of creation. Ping the server. 2. Type the host name or the full IP address of the server where you have installed InfoSphere CDC in the Server box. type it in the Name box. and the last time it was modified. 4. If the name of the server or IP address where InfoSphere CDC is installed has changed. 3. See also: “To add a new datastore” “To edit a datastore” “To delete a datastore” on page 25 “To copy a datastore” on page 25 “To view the history of a datastore” on page 25 “To set connection parameters on a datastore” on page 25 Related concepts “Setting up datastores for replication” on page 59 Related tasks “To assign users to a datastore” on page 31 To add a new datastore 1. Click Access Manager > Datastore Management. you must be a System Administrator that has the privilege to manage datastores and user accounts. Select an existing datastore. 5. 6. type it in the Server box. Click File > Access Server > New Datastore.v Propagate connection parameters—propagating new connection parameters for users that use the existing connection parameters eases system administration in that you only have to specify connection parameters once. If successful. Type the name of the datastore in the Name box. Click Access Manager > Datastore Management. 2. 24 InfoSphere Change Data Capture Management Console: Administration Guide . 6. Type the port number of the server in the Port box. If you want to change the Name of the datastore. If you want to change the description. 4. Note: You can only add a datastore if you are a System Administrator and have the privilege to manage datastores and user accounts. Type a description in the Description box. v Generate reports on the activities related to a set of datastores—generating a report on a specific datastore can help you keep track of which users you have assigned datastore access to and what databases users can access. Note: To be able to work in the Access Manager perspective. Related concepts “Setting up datastores for replication” on page 59 To edit a datastore 1. type it in the Description box.

Type the database user name in the DB Login box. 4. Click Access Manager > Datastore Management. 6. 4. 3. Click Connection Parameters. 2. Click Access Manager > Datastore Management. 3. type it in the Port box. If the port number of the server has changed. 2. Click Access Manager > Datastore Management. Click File > Access Server > Delete. 3. Type the name of the new datastore in the New Name box.7. Related concepts “Setting up datastores for replication” on page 59 To set connection parameters on a datastore 1. Note: You can only copy a datastore if you are a System Administrator and have the privilege to manage datastores and user accounts. Select an existing datastore. Type and confirm the password to connect to this database in the Password and Confirm boxes. Related concepts “Setting up datastores for replication” on page 59 To copy a datastore 1. Note: You can only delete a datastore if you are a System Administrator and have the privilege to manage datastores and user accounts. Related concepts “Setting up datastores for replication” on page 59 To delete a datastore 1. 2. 2. Click History. then you must specify the user you created when installing InfoSphere CDC. 4. Click Access Manager > Datastore Management. 5. 3. Select an existing datastore. Type the name of the database or the Universal Resource Locator (URL) of the database server in the Database/URL box. Related concepts “Setting up datastores for replication” on page 59 To view the history of a datastore 1. 7. Select an existing datastore. Setting up datastores and user accounts in Access Manager 25 . Click File > Access Server > Copy. Click File > Access Server > Properties. Note: You can only edit a datastore if you are a System Administrator and have the privilege to manage datastores and user accounts. Select an existing datastore or hold CTRL and select multiple datastores. Click File > Access Server > Properties. If you want users to connect to a database for replication with WebSphere® DataStage™.

you must specify a unique user name. Monitor account. Note: To be able to work in the Access Manager perspective. the date of user account creation. delete. modify. the role of the user. Related concepts “Setting up datastores for replication” on page 59 Managing user accounts You can create user accounts and assign these users to a datastore in the Access Manager perspective of Management Console. and the last time it was modified. Note: You can only set connection parameters on a datastore if you are a System Administrator that can manage datastores and user accounts. v Add. See also: “To add a new user” on page 27 “To edit a user” on page 27 “To delete a user” on page 28 “To copy a user” on page 29 “To change the existing role on a user account” on page 29 “To enable a System Administrator user account and datastore administration privileges” on page 30 “To view the history of a user account” on page 30 Related tasks “To assign a datastore to users” on page 30 26 InfoSphere Change Data Capture Management Console: Administration Guide . v Generate a report on selected user accounts—generating a report on a specific user account can help you keep track of which datastores the user has access to.8. You can also track account status settings such as if the account is locked. or copy user accounts—adding a user account is necessary to provide users with the ability to connect to Access Server and log into Management Console. if the user is required to change their password at next login. Users can work in either a System Administrator account. If you want users assigned to this datastore that use the existing connection parameters to connect to the datastore using the new connection parameters you have set for this datastore. v Assign a datastore to a user—assigning a datastore provides the user access to an installation of InfoSphere CDC and the ability to connect to the database that you have made available for replication on the server. v Change the security role of a user—changing the security role on a user account determines the level of access a user has in Management Console. it must meet any complex password requirements you may have set in Management Console. When adding a user account. Administrator account. disabled. or an Operator account. you must be a System Administrator that has the privilege to manage datastores and user accounts. then enable the Propagate changes to users checkbox. When setting a password for the user. or if the account has a password expiry policy set on it.

view statistics. 4. Enable user account and datastore administration—enables a user assigned the System Administrator role access to the Access Manager perspective. stop. type and confirm it in the Password and Confirm boxes. However. Click Access Manager > User Management. Note: You can only add a new user if you are a System Administrator and have the privilege to manage datastores and user accounts. then they can create new users. and define Access Server password settings. and can view notifications sent by subscriptions or datastores. type their full name and a description in the Full Name and Description boxes. If you want the user to specify a password. or view notifications sent by subscriptions and datastores. To edit a user 1. Notes: v Users assigned to the Operator role can start. They can also view the tables selected for refresh and start a refresh on a subscription. This is the name the user will need to supply when connecting to Access Server and logging into Management Console. However. 2. Monitors also have access to the Replication Diagram view. Click Access Manager > User Management. configure replication. choose one of the following: Role v System Administrator—specifies that users assigned to this role can perform all available operations in Management Console. v Administrator—specifies that users assigned to this role can perform all available operations in Management Console. System administrators can also modify system parameters to calibrate their replication environment. refresh tables. Only users that require full operational access to the Monitoring and Configuration perspectives should be assigned to this role. v Users assigned to the Monitor role can view the event log. v Monitor—specifies that users assigned to this role only have access to the Monitoring perspective in Management Console. Users can view the replication state and status of a subscription and can view latency threshold information. and monitor replication activities. If you want to keep a profile of the user for system administrator purposes. but cannot modify system parameters.To add a new user 1. 6. Setting up datastores and user accounts in Access Manager 27 . 5. users assigned to this role cannot start or stop replication. Click File > Access Server > New User. If you want to assign the user to a role. If you enable this option for a user. new datastores. If you have enabled complex passwords. Select an existing user. Type the name of the user in the Name box. Users assigned to this role can access both the Monitoring and Configuration perspectives. 2. then you must specify a password that meets the requirements. 3. and view table mappings. v Operator—specifies that users assigned to this role only have access to the Monitoring perspective in Management Console. Operators also have access to the Replication Diagram view. users assigned to this role cannot configure replication and select or remove tables from a refresh.

v Monitor—specifies that users assigned to this role only have access to the Monitoring perspective in Management Console. Note: You can only edit a user if you are a System Administrator and have the privilege to manage datastores and user accounts. Click File > Access Server > Properties. Users assigned to this role can access both the Monitoring and Configuration perspectives. then you must specify a password that meets the requirements. refresh tables. type and confirm it in the Password and Confirm boxes. 3. and view table mappings. Users can view the replication state and status of a subscription and can view latency threshold information. System administrators can also modify system parameters to calibrate their replication environment. Note: You can only delete a user if you are a System Administrator that can manage datastores and user accounts. users assigned to this role cannot configure replication and select or remove tables from a refresh.3. choose one of the following: Role v System Administrator—specifies that users assigned to this role can perform all available operations in Management Console. If you enable this option for a user. 5. stop. type this information in the Full Name and Description boxes. To delete a user 1. 28 InfoSphere Change Data Capture Management Console: Administration Guide . but cannot modify system parameters. v Administrator—specifies that users assigned to this role can perform all available operations in Management Console. then they can create new users. and can view notifications sent by subscriptions or datastores. new datastores. and monitor replication activities. if you have enabled complex passwords. However. configure replication. Click File > Access Server > Delete. Select an existing user or hold the CTRL key to select multiple users. Only users that require full operational access to the Monitoring and Configuration perspectives should be assigned to this role. users assigned to this role cannot start or stop replication. Operators also have access to the Replication Diagram view. Enable user account and datastore administration—enables a user assigned the System Administrator role access to the Access Manager perspective. v Operator—specifies that users assigned to this role only have access to the Monitoring perspective in Management Console. and define Access Server password settings. Monitors also have access to the Replication Diagram view. or view notifications sent by subscriptions and datastores. If you want to change the role assigned to the user. If you want to change the full name or description of the user. However. As the system administrator. They can also view the tables selected for refresh and start a refresh on a subscription. view statistics. 6. Click Access Manager > User Management. If you want the user to specify a new password. 4. 2. Notes: v Users assigned to the Operator role can start. v Users assigned to the Monitor role can view the event log.

configure replication. users assigned to this role cannot start or stop replication. To change the existing role on a user account 1. but cannot modify system parameters. Click File > Access Server > Change Role. Note: You can only copy a user if you are a System Administrator that can manage datastores and user accounts. 3. Notes: v Users assigned to the Operator role can start. or view notifications sent by subscriptions and datastores. Note: You can only change the role of users if you are a System Administrator and have the privilege to manage datastores and user accounts. Click Access Manager > User Management. If you enable this option for a user. Enable user account and datastore administration—enables a user assigned the System Administrator role access to the Access Manager perspective.To copy a user 1. Operators also have access to the Replication Diagram view. v Administrator—specifies that users assigned to this role can perform all available operations in Management Console. 4. refresh tables. Users can view the replication state and status of a subscription and can view latency threshold information. view statistics. stop. Click File > Access Server > Copy. Select an existing user or hold the CTRL key to select multiple users. then they can create new users. Select an existing user. Type the name of the user in the Enter the name of the user box. System administrators can also modify system parameters to calibrate their replication environment. v Users assigned to the Monitor role can view the event log. and define Access Server password settings. However. Choose from one of the following: Role v System Administrator—specifies that users assigned to this role can perform all available operations in Management Console. 2. Only users that require full operational access to the Monitoring and Configuration perspectives should be assigned to this role. Users assigned to this role can access both the Monitoring and Configuration perspectives. v Operator—specifies that users assigned to this role only have access to the Monitoring perspective in Management Console. 2. and view table mappings. and monitor replication activities. 3. users assigned to this role cannot configure replication and select or remove tables from a refresh. Monitors also have access to the Replication Diagram view. They can also view the tables selected for refresh and start a refresh on a subscription. Setting up datastores and user accounts in Access Manager 29 . However. v Monitor—specifies that users assigned to this role only have access to the Monitoring perspective in Management Console. and can view notifications sent by subscriptions or datastores. 4. Click Access Manager > User Management. new datastores.

If you choose to override the defaults. 4. Click Access Manager > User Management. You can click OK to accept the default connection parameters on the datastore or you can choose to override the default parameters for the selected user. Note: You can only view the history of an account if you are a System Administrator that can manage datastores and user accounts. 2. 6. Users need this relationship so that they can connect to a datastore. you must be a System Administrator that has the privilege to manage datastores and user accounts. 30 InfoSphere Change Data Capture Management Console: Administration Guide . Click Access Manager > User Management. Click Access Manager > User Management. 7. 4. 5. Select an existing user. 4. Click History. specify the following: 1. 2. A datastore represents the InfoSphere CDC installation and the database made available for replication. 3. 5. 3. Both methods create the required relationship between a datastore and a user. Assigning users to datastores You can either assign a datastore to a user or assign a user to a datastore in the Access Manager perspective of Management Console. Ensure the user is assigned to the System Administrator role. 3. Note: You can only enable a System Administrator to manage datastores and user accounts if you are a System Administrator that can manage datastores and user accounts. Review the connection parameters.To enable a System Administrator user account and datastore administration privileges 1. Click File > Access Server > Assign > Datastore. See also: “To assign a datastore to users” “To assign users to a datastore” on page 31 To assign a datastore to users Ensure you have added a user. 2. Select an existing user. Click File > Access Server > Properties. Select a datastore. Select an existing user or hold the CTRL key to select multiple users. Note: To be able to work in the Access Manager perspective. Click File > Access Server > Properties. Enable the Enable user account and datastore administration checkbox. To view the history of a user account 1.

Review the connection parameters. 3. 5. 7. 8.v Database/URL—specifies the name of the database or the Universal Resource Locator (URL) of the database server you want to connect to. v Allow connection parameters saving—enables the user to save the connection parameters when connecting to a datastore. If you want to set specific options on how these connection parameters are displayed to the user when connecting to the datastore in the Connect to datastore dialog box. 2. Click Access Manager > Datastore Management. v DB Password—specifies the password to connect to the database. Setting up datastores and user accounts in Access Manager 31 . then enable one or more of the following options: v Always show connection dialog—enables the user to specify the password each time they want to connect to the datastore. specify the following: v Database/URL—specifies the name of the database or the Universal Resource Locator (URL) of the database server you want to connect to. v DB Login—specifies the database user name to connect to the database. v Confirm Password—specifies the confirmed password. Ensure you have added a datastore. Select a user or hold the CTRL key to select multiple users. To assign users to a datastore 1. 4. then you must specify the user you created when installingInfoSphere CDC. v DB Password—specifies the password to connect to the database. Note: You can only assign a datastore to users if you are a System Administrator and have the privilege to manage datastores and user accounts. then you must specify the user you created when installingInfoSphere CDC. If you choose to override the defaults. Select an existing datastore. v Show parameter valuess (except password)—displays the connection parameters to the user (except password) each time the user tries to connect to the datastore. v Write-protect parameters (except password)—displays the connection parameters to the user (except password) in read-only format each time the user tries to connect to the datastore. 6. v Confirm Password—specifies the confirmed password. If you want to set specific options on how these connection parameters are displayed to the user when connecting to the datastore in the Connect to datastore dialog box. If you want users to connect to the database for replication with WebSphere DataStage. then enable one or more of the following options: v Always show connection dialog—enables the user to specify the password each time they want to connect to the datastore. 8. Click File > Access Server > Assign > User. If you want users to connect to the database for replication with WebSphere DataStage. v DB Login—specifies the database user name to connect to the database. You can click OK to accept the default connection parameters on the datastore or you can choose to override the default parameters for the selected user(s).

See also: “To delete a connection” on page 33 “To override default connection parameters on a datastore” on page 33 32 InfoSphere Change Data Capture Management Console: Administration Guide . Users will need to be made aware of the new parameters so that they can connect. Use the Connection Management view to: v Assign a user to a datastore—assigning a user to a datastore creates a datastore centric relationship between a datastore and a user. This means when you select a user in the User Management view. v Set connection parameters—setting connection parameters on a datastore provides users with the ability to connect to the datastore.v Show parameter valuess (except password)—displays the connection parameters to the user (except password) each time the user tries to connect to the datastore. When assigning a datastore. you must specify the correct connection parameters. As a System Administrator. Managing datastore connections A datastore represents the InfoSphere CDC installation and the database made available for replication. you must specify the correct connection parameters. you should be able to see all the datastores you have assigned to that specific user in the Connection Management view. Note: You can only assign users to a datastore if you are a System Administrator and have the privilege to manage datastores and user accounts. This means when you select a datastore in the Datastores Management view. you must be a System Administrator that has the privilege to manage datastores and user accounts. v Assign a datastore to a user—assigning a datastore to a user creates a user centric relationship between a user and a datastore. v Modify and delete connection parameters—deleting an existing connection may be necessary when a user no longer requires access to a specific datastore. then these parameters will display when you assign a user to a datastore. The user will require these parameters in order to connect to the datastore. you can manage datastore connections. v Write-protect parameters (except password)—displays the connection parameters to the user (except password) in read-only format each time the user tries to connect to the datastore. You can assign the same datastore to more than one user. You can choose to apply these same connection parameters. You can also modify connection parameters. v Allow connection parameters saving—enables the user to save the connection parameters when connecting to a datastore. When assigning a user. You can assign the same user to more than one datastore. you should be able to see all the users you have assigned to that specific datastore in the Connection Management view. or choose to override these and specify another set of connection parameters. Note: To be able to work in the Access Manager perspective. If you have already specified connection parameters for a datastore when you had added it to Management Console. The user will require these parameters in order to connect to the datastore.

3. 6. 4. v Allow connection parameters saving—enables the user to save the connection parameters when connecting to a datastore. Note: You can only override connection parameters on a datastore if you are a System Administrator and have the privilege to manage datastores and user accounts. v Click User Management and select an existing user that has a datastore assigned to it. Select the user assigned to this datastore in the Connection Management view. Type the name of the database or the Universal Resource Locator (URL) of the database server in the Database/URL box.Related tasks “To assign users to a datastore” on page 31 To delete a connection 1. Click Access Manager > Datastore Management. Note: You can only delete a datastore if you are a System Administrator that can manage datastores and user accounts. Type the database user name in the DB Login box. then you must specify the user you created when installing InfoSphere CDC. Ensure you have assigned a datastore and a user. 2. Click Connection Management and right-click on the datastore assigned to the user. Click File > Access Server > Properties. If you want users to connect to a database for replication with WebSphere DataStage. Click Access Manager. Select the datastore. 7. 2. 9. If you want to set specific options on how these connection parameters are displayed to the user when connecting to the datastore in the Connect to datastore dialog box. then enable one or more of the following options: v Always show connection dialog—enables the user to specify the password each time they want to connect to the datastore. 8. 3. Click Delete Connection. Setting up datastores and user accounts in Access Manager 33 . Ensure you have assigned a user to the datastore. Click Connection Management and right-click on the user assigned to the datastore. v Write-protect parameters (except password)—displays the connection parameters to the user (except password) in read-only format each time the user tries to connect to the datastore. Click Delete Connection. Delete an existing connection using one of the following methods: v Click Datastores Management and select an existing datastore that has a user assigned to it. v Show parameter valuess (except password)—displays the connection parameters to the user (except password) each time the user tries to connect to the datastore. To override default connection parameters on a datastore 1. 5. Type and confirm the password to connect to this database in the DB Password and Confirm boxes.

Enable the Password never expires checkbox. 4. Note: To be able to work in the Access Manager perspective. v enable users to change their passwords at next login. See also: “To disable a user account” “To enable a user to change password at next login” “To override password expiration policy set in Management Console” “To unlock a user account” on page 35 To disable a user account 1. 3. v override any password expiration policy you may have set in Management Console. 2. Click File > Access Server > Properties. Select an existing user. Select an existing user. Note: You can only override an existing password expiration policy if you are a System Administrator that can manage datastores and user accounts. Click File > Access Server > Properties. To override password expiration policy set in Management Console 1. To enable a user to change password at next login 1. Click Access Manager > User Management. Select an existing user. v unlock locked user accounts. Note: You can only enable a user to change the password at next login if you are a System Administrator that can manage datastores and user accounts. 34 InfoSphere Change Data Capture Management Console: Administration Guide . Click Access Manager > User Management. 4. 2. 4.Managing security on user accounts You can set specific security options on an existing user account in the Access Manager perspective of Management Console. 2. 3. Click Access Manager > User Management. 3. Click File > Access Server > Properties. Use the User Properties dialog box to: v disable a user account. Enable the User must change password at next login checkbox. Enable the Account is disabled checkbox. you must be a System Administrator that has the privilege to manage datastores and user accounts.

v Display the number of failed login attempts—enables users to track the number of failed login attempts before they get locked out of the account. See also: “To set complex passwords on user accounts” on page 36 “To enforce password history” on page 36 “To enforce password expiry” on page 36 “To enforce password locking on failed login attempts” on page 36 “To enforce new account expiry” on page 36 “To display previous failed login attempts” on page 37 “To display the last successful login” on page 37 Setting up datastores and user accounts in Access Manager 35 . Setting password and account security policies on user accounts You can enhance password and account security on all user accounts in the Access Manager perspective of Management Console. v Enforce a password expiry policy—enables system administrators to enhance security by ensuring that new passwords are created and associated with user accounts. Click Access Manager > User Management. The policy creates a condition where a user will be locked out of their account after a number of attempts. v Enforce password history—enables system administrators to enhance security by ensuring that old passwords are not continually reused. For this policy to be effective. Click File > Access Server > Properties. Note: You can only unlock an account if you are a System Administrator that can manage datastores and user accounts. This checkbox is enabled automatically after the number of failed login attempts exceeds the locking policy you may have set in the Access Server Options dialog box in Management Console. Note: To be able to work in the Access Manager perspective. 2. Disable the Account is locked checkbox. v Display the last successful login—enables users to track their last successful login.To unlock a user account 1. Select an existing user. By default. You can control this by setting the minimum age of the password. Use the Access Server Options dialog box to: v Set a complex password requirement—enhances password security by enabling users to specify a complex password when logging into Management Console. v Enforce an account expiry after new account creation—enhances account security by forcing users to change their passwords when a new account is created for them. you must be a System Administrator that has the privilege to manage datastores and user accounts. v Lock accounts after a number of failed login attempts—enables a three strikes login policy which is used to prevent computer password attacks. 3. 4. this setting is set to 3 login attempts. do not let users change their password immediately after setting a new one.

Ensure the Enforce password expiry checkbox is enabled. 2. Type the minimum number of non-alphabetic characters in the Minimum non-alphabetic characters box. Enable the Require complex password checkbox. Note: You can only enforce password expiry if you are a System Administrator and have the privilege to manage datastores and user accounts. Type the maximum number of days before a password expires in the Maximum password (age) box. Click File > Access Server > Access Server Options. 3. Click File > Access Server > Access Server Options. 4. Click Passwords. 4. The number must be between 1 and 12. 2. The default number is 3. 36 InfoSphere Change Data Capture Management Console: Administration Guide . 6. Type the number of passwords remembered in the Passwords remembered box. 3. The number must be between 0 and 30. To enforce password expiry 1. 2. Note: You can only set complex passwords on user accounts if you are a System Administrator that can manage datastores and user accounts. 4. To enforce password history 1. Click Accounts. Note: You can only enforce new password locking if you are a System Administrator and have the privilege to manage datastores and user accounts. 2. Type the minimum password length in the Minimum password length box. The default number is 3. The number must be between 0 and 30. Type the minimum number of alphabetic characters in the Minimum alphabetic characters box. Click File > Access Server > Access Server Options. Click File > Access Server > Access Server Options. 3. The default number is 5. Note: You can only enforce password history if you are a System Administrator and have the privilege to manage datastores and user accounts. 3. 5. Type the maximum number of attempts before an accounts is locked in the Consecutive failures before lock box. 2. The number must be between 1 and 100. 1. To enforce new account expiry 1. The number must be between 1 and 999. To enforce password locking on failed login attempts 1. Ensure the Lock accounts on failed login attempts checkbox is enabled. Click Passwords.To set complex passwords on user accounts Click File > Access Server > Access Server Options. Ensure the Enforce Password history checkbox is enabled. Click Accounts. 4. Click Passwords. The number must be between 0 and 30.

To display previous failed login attempts 1. modified. Click Accounts. and display or print them through a web browser. security policies set on user accounts. Note: You can only display previous failed login attempts if you are a System Administrator and have the privilege to manage datastores and user accounts. Auditing user accounts. verifying system integrity. you can systematically examine user activities and identify any attempts to breach the security of your replication configuration. Click File > Access Server > Access Server Options. You can generate audit trail reports after enabling audit logging. Collecting data generated by user activities is very important for analyzing the security of information. Ensure the Display last successful login checkbox is enabled. You can save audit trail reports as HTML files. By generating reports that contain this type of information. security policies. Note: You can only enforce new account expiry if you are a System Administrator and have the privilege to manage datastores and user accounts. To display the last successful login 1. or deleted user accounts v Added. 2. Click Accounts. and other general events. Ensure the Display previous failed login attempts checkbox is enabled. datastores. The default number is 15. datastores. Use the Audit Trail Report dialog box to generate an audit trail report. or renamed datastores v New or lost user and datastore assignments v Enabled. When audit logging is enabled. Two types of reports can be generated from an audit log: audit trail and security log. The number must be between 1 and 999. 4. Click File > Access Server > Access Server Options. and general events You can audit user accounts. deleted. You can archive audit log files and generate audit trail reports for a specified period of time from the current audit log. 3. Use the Audit tab in the Access Server Options dialog box to: v Enable audit logging—enabling audit logging lets you audit the activity of user accounts. Note: You can only display the last successful login if you are a System Administrator and have the privilege to manage datastores and user accounts. or modified ability to generate an audit log Setting up datastores and user accounts in Access Manager 37 . Ensure the Enforce new account expiry checkbox is enabled. and general events in the Access Manager perspective of Management Console. security policies. datastores. 3. 2. The following activities are recorded in the report: v Added. modified. or from an archived log file. Access Server keeps track of significant activities and records them into an audit log file.3. Type the maximum number of days before a new account expires in the Maximum new account age (days) box. disabled. and detecting signs of suspicious behavior.

v Audit datastore management—enable if you want to audit datastore management activities such as the creation. The following activities are recorded the report: v v v v v v v Modified user passwords Disabled or enabled user accounts Locked or unlocked user accounts Successful or failed log in attempts by a user Which users are logged or logged out of Management Console Which datastores users are connected to or disconnected from Started or stopped Access Servers v Generated report lists Each of the activities contained in either an audit trail or security log report has the following categories and items of information: v Event—specifies the description of the activity being audited. you must be a System Administrator that has the privilege to manage datastores and user accounts. and deletion of users. v Audit general events—enable if you want to audit general events generated by Access Server. Click File > Access Server > Access Server Options. Enable the Audit log checkbox. 2. and deletion of datastores. datastore name. modification. v Comment—provides more information if applicable. 4. 38 InfoSphere Change Data Capture Management Console: Administration Guide . v Timestamp—the date and time of activity. v Identification—depending on the activities being audited. and the process responsible for generating the activity. Enable one or more of the following: v Audit account management—enable if you want to audit user account management activities such as the creation. See also: “To “To “To “To enable auditing” generate an audit trail log” on page 39 generate a security log report” on page 39 clear the log” on page 39 To enable auditing 1.v Modified security settings on user accounts Use the Security Log dialog box to generate a security log report. 3. modification. Note: To be able to work in the Access Manager perspective. the report will specify the name on the user account. You can generate security log reports after enabling audit logging. Click Audit. v Audit security policy management—enable if you want to audit security policy settings related to passwords and user accounts.

Creating list reports You can generate a list report in the Access Manager perspective of Management Console. To clear the log 1. 4. 3. Click File > Access Server > Audit log > Security Log. Note: You can only generate a security log report if you are a System Administrator and have the privilege to manage datastores and user accounts. Note: You can only clear the log if you are a System Administrator and have the privilege to manage datastores and user accounts. Note: If you have cleared your log. Click File > Access Server > Audit log > Clear Log.Note: You can only enable auditing if you are a System Administrator and have the privilege to manage datastores and user accounts. Select the start date of the events you want to audit in the From box. This ensures that there is nothing important in the report that you want to save first before clearing the log. then the report will be empty until new events are generated. Ensure you have enabled audit logging. 2. then the report will be empty until new events are generated. Select the end date of the events you want to audit in the To box. Ensure you have enabled audit logging. Note: If you have cleared your log. 2. Note: To be able to work in the Access Manager perspective. 3. To generate an audit trail log 1. See also: “To create a user list report” on page 40 “To create a datastore list report” on page 40 Setting up datastores and user accounts in Access Manager 39 . 3. Ensure you have enabled audit logging and generated a report. you must be a System Administrator that has the privilege to manage datastores and user accounts. Select the end date of the events you want to audit in the To box. Note: You can only generate an audit trail log if you are a System Administrator and have the privilege to manage datastores and user accounts. Click Yes to clear the log. Select the start date of the events you want to audit in the From box. Click File > Access Server > Audit log > Audit Trail. 2. To generate a security log report 1. 4.

Click OK and Save. Select an existing datastore or hold the CTRL key to select multiple datastores. Select an existing user or hold the CTRL key to select multiple users. v Datastore Platform—includes the type of database platform on which this datastore resides. Click File > Access Server > Reports>Datastore Report. Note: You can only create a list report if you are a System Administrator and have the privilege to manage datastores and user accounts. 2. Enable one or more of the following: v Full Name—includes the full name you specified when you created the user. v Date Last Modified—includes the date the datastore was last modified. 3. Click Access Manager > User Management. v Role—includes the role you had assigned to the user. 1. 3. v Description—includes the description you specified when you created the user. v Date Created—includes the date you had created the datastore. Enable one or more of the following: v Description—includes a description you specified when you added the datastore. 4. or Linux® command prompt. UNIX®. To create a datastore list report Click Access Manager > Datastore Management. v User Access—includes the users you have assigned to this datastore. v Datastores Access—includes the datastores you have assigned to the user. v Account Status—includes information about the account such as password expiry or if the account has been disabled or locked. Note: You can only create a list report if you are a System Administrator and have the privilege to manage datastores and user accounts. v Date Created—includes the date you had created the user account. 4.To create a user list report 1. v Date Last Modified—includes the date the user was last modified. you will learn: “dmaddconnection—Adding a datastore connection to a user” on page 41 “dmchangeconnection—Changing the connection parameters to a datastore” on page 42 “dmchangepassword—Changing the password on a user account” on page 43 “dmcreatedatastore—Adding a datastore” on page 43 “dmcreateuser—Adding a user” on page 44 “dmdeleteconnection—Deleting a datastore connection” on page 45 40 InfoSphere Change Data Capture Management Console: Administration Guide . Click File > Access Server > Reports>User Report. In this section. 2. 5. Commands for Access Server Access Server provides a set of commands that let you manage datastores and user accounts from a Windows®.

To set connection parameters on a user account. When the user establishes a connection to the datastore.“dmdeletedatastore—Deleting a datastore” on page 45 “dmdeleteuser—Deleting a user” on page 46 “dmdisableuser—Disabling a user account” on page 46 “dmenableuser—Enabling a user” on page 46 “dmlistdatastoreusers—Generating a report list of users assigned to a datastore” on page 47 “dmlistuserdatastores—Generating a report list of datastores assigned to a user” on page 47 “dmlistusers—Listing user accounts” on page 48 “dmresetuser—Resetting a user account” on page 49 “dmunlockuser—Unlocking a user account” on page 49 dmaddconnection—Adding a datastore connection to a user Use this command to set connection parameters to a datastore for a user. Syntax Parameters userName Specifies the name of the user for which you want to create a connection. showParams Specifies that you want all the connection parameters displayed to the user (except for the password) each time the user tries to connect to the datastore. DMADDCONNECTION userName datastoreName database databaseOwner databasePassword alwaysPrompt showPa Setting up datastores and user accounts in Access Manager 41 . If you want the user to be prompted for a connection. Not all datastore connections are to a database. specify a value of FALSE. Otherwise. you must identify the name and password of the database you want users to use for replication. Use ″″ if not required. you must be a System Administrator and have the privilege to manage datastores and user accounts. Otherwise. then specify a value of TRUE. database Specifies the name of the database that you want users to replicate to or from. Not all datastore connections are to a database. Use ″″ if not required. Not all datastore connections are to a database. When adding a connection for a user. datastoreName Specifies the name of the datastore you want the user to connect to. then specify a value of TRUE. specify a value of FALSE. alwaysPrompt Specifies that you want the user to always be prompted for a connection each time the user tries to connect to the datastore. Use ″″ if not required. they are in fact connecting to this database. databaseOwner Specifies the user name of the database. If you want the parameters displayed. databasePassword Specifies the password to log into the database. This database resides on the same server as your InfoSphere CDC installation.

When the user establishes a connection to the datastore. Specifies that you want to connect to a remote installation of Access Server. datastoreName Specifies the name of the datastore you want the user to connect to. Use ″″ if not required. Not all datastore connections are to a database.writeProtected Specifies that you want all the connection parameters displayed to the user in read-only format each time the user tries to connect to the datastore. If you want the parameters displayed in read-only format. you must identify the name and password of the database you want users to use for replication. saveParams Specifies that you want the user to be able to save connection parameters when connecting to the datastore. Not all datastore connections are to a database. This database resides on the same server as your InfoSphere CDC installation. To change connection parameters on a user account. then these parameters are not required. Use ″″ if not required. Not all datastore connections are to a database. If you have installed Access Server on the same machine as Management Console. you must be a System Administrator and have the privilege to manage datastores and user accounts. databaseOwner Specifies the user name of the database. DMCHANGECONNECTION userName datastoreName database databaseOwner databasePassword [-accessserver host 42 InfoSphere Change Data Capture Management Console: Administration Guide . Use ″″ if not required. database Specifies the name of the database that you want users to replicate to or from. accessserver hostname port adminuser adminpassword These parameters are optional. then these parameters are not required. If you have installed Access Server on the same machine as Management Console. they are in fact connecting to this database. Otherwise. specify a value of FALSE. Syntax Parameters userName Specifies the name of the user for which you want to create a connection. specify a value of TRUE. When changing a connection for a user. then specify a value of TRUE. specify a value of FALSE. If you want to enable parameter saving. Otherwise. accessserver hostname port adminuser adminpassword These parameters are optional. Specifies that you want to connect to a remote installation of Access Server. dmchangeconnection—Changing the connection parameters to a datastore Use this command to change connection parameters to a datastore for a user account. databasePassword Specifies the password to log into the database.

Syntax Parameters datastoreName Specifies the name of the datastore you want to add. If you have enabled complex passwords. To change passwords. When adding a datastore. If you have installed Access Server on the same machine as Management Console. then these parameters are not required. hostname Specifies the hostname of the server where you have installed InfoSphere CDC. accessserver hostname port adminuser adminpassword These parameters are optional. Setting up datastores and user accounts in Access Manager DMCREATEDATASTORE datastoreName description hostname port [-accessserver hostname port adminuser a 43 . you must be a System Administrator and have the privilege to manage datastores and user accounts. To add a datastore. description Specifies a brief description about this datastore.dmchangepassword—Changing the password on a user account Use this command to change the password on a user account that you had created. password Specifies the password you want the user to supply when logging into Management Console. Specifies that you want to connect to a remote installation of Access Server. If you have installed Access Server on the same machine as Management Console. Syntax DMCHANGEPASSWORD username password [-accessserver hostname port adminuser adminpassword] Parameters userName Specifies the name of the user that you are changing the password for. Adding a datastore in Management Console means that you are in the process of making an installation of InfoSphere CDC and the database you want users to replicate to or from available for connection by other users. This user will require the password in order to log into Management Console. port Specifies the port number of the server where you have installed InfoSphere CDC. you must specify information about where your installation of InfoSphere CDC resides. dmcreatedatastore—Adding a datastore Use this command to add a new datastore. accessserver hostname port adminuser adminpassword These parameters are optional. then you must specify a password that meets the requirements. then these parameters are not required. you must be a System Administrator and have the privilege to manage datastores and user accounts. Specifies that you want to connect to a remote installation of Access Server.

dmcreateuser—Adding a user Use this command to add a new user. manager Specifies that a user assigned the role of SYSADMIN also has privileges to manage datastores and user accounts in the Access Manager perspective of Management Console. v MONITOR—specifies that a user assigned to this role is a Monitor and only has access to the Monitoring perspective in Management Console. Only users that require full operational access to the Monitoring and Configuration perspectives should be assigned to this role. Otherwise. then you must specify a password that meets the requirements. then specify a value of TRUE. if you want the user to login using the same password you have assigned to them. System administrators can also modify system parameters to calibrate their replication environment. password Specifies the password you want the user to supply when logging into Management Console. specify a value of TRUE. v OPERATOR—specifies a that user assigned to this role is an Operator and only has access to the Monitoring perspective in Management Console. Adding a user account is necessary to provide users with the ability to log into Management Console. then specify a value of FALSE. Enable one of the following values: v SYSADMIN—specifies that a user assigned to this role is a System Administrator and can perform all available operations in Management Console. Otherwise. If you have enabled complex passwords. changePassword Specifies you want the user to change their password when logging into Management Console for the first time. specify a value FALSE. description Specifies a description about the user. you must be a System Administrator and have the privilege to manage datastores and user accounts. If you want the user to change the password. fullname Specifies the full name of the user. v ADMIN—specifies that a user assigned to this role is an Administrator and can perform all available operations in Management Console. If you want to enable this privilege for a System Administrator. role Specifies the role you want to assign to the user. DMCREATEUSER username fullname description password role manager changePassword passwordExpires [-acc 44 InfoSphere Change Data Capture Management Console: Administration Guide . Syntax Parameters username Specifies the unique name for the user you want to create an account for. Users assigned to this role can access both the Monitoring and Configuration perspectives. but cannot modify system parameters. To add a user.

Operators also have access to the Replication Diagram view. dmdeletedatastore—Deleting a datastore Use this command to delete a datastore. If you have installed Access Server on the same machine as Management Console. and monitor replication activities. Otherwise. refresh tables. However. Syntax DMDELETEDATASTORE datastoreName [-accessserver hostname port adminuser adminpassword] Setting up datastores and user accounts in Access Manager 45 . v Users assigned to the Monitor role can view the event log. To delete a datastore. then these parameters are not required. or view notifications sent by subscriptions and datastores. Users can view the replication state and status of a subscription and can view latency threshold information. If you want to override an existing password expiry policy. Specifies that you want to connect to a remote installation of Access Server. Syntax DMDELETECONNECTION userName datastoreName [-accessserver hostname port adminuser adminpassword] Parameters username Specifies the unique name of the user you want to delete the connection for.passwordExpires Specifies that you want to override any existing password expiry policies set in Management Console so that the password never expires. configure replication. datastoreName Specifies the name of the datastore you want to delete the connection for. accessserver hostname port adminuser adminpassword These parameters are optional. Notes: v Users assigned to the Operator role can start. They can also view the tables selected for refresh and start a refresh on a subscription. specify a value of TRUE. then specify a value of FALSE. Specifies that you want to connect to a remote installation of Access Server. stop. To delete a connection. If you have installed Access Server on the same machine as Management Console. dmdeleteconnection—Deleting a datastore connection Use this command to delete an existing connection between a datastore and a user. and view table mappings. you must be a System Administrator and have the privilege to manage datastores and user accounts. if you want the password to expire. However. then these parameters are not required. view statistics. accessserver hostname port adminuser adminpassword These parameters are optional. and can view notifications sent by subscriptions or datastores. users assigned to this role cannot configure replication and select or remove tables from a refresh. you must be a System Administrator and have the privilege to manage datastores and user accounts. users assigned to this role cannot start or stop replication. Monitors also have access to the Replication Diagram view.

then these parameters are not required. you must be a System Administrator and have the privilege to manage datastores and user accounts.Parameters datastoreName Specifies the name of the datastore you want to delete. If you have installed Access Server on the same machine as Management Console. you must be a System Administrator and have the privilege to manage datastores and user accounts. accessserver hostname port adminuser adminpassword These parameters are optional. dmenableuser—Enabling a user Use this command to enable a user account. dmdeleteuser—Deleting a user Use this command to delete a user. then these parameters are not required. If you have installed Access Server on the same machine as Management Console. Specifies that you want to connect to a remote installation of Access Server. accessserver hostname port adminuser adminpassword These parameters are optional. Syntax DMENABLEUSER username [-accessserver hostname port adminuser adminpassword] 46 InfoSphere Change Data Capture Management Console: Administration Guide . To enable a user. then these parameters are not required. you must be a System Administrator and have the privilege to manage datastores and user accounts. Specifies that you want to connect to a remote installation of Access Server. This lets the user log into Management Console. To disable a user. dmdisableuser—Disabling a user account Use this command to disable a user account. Syntax DMDELETEUSER username [-accessserver hostname port adminuser adminpassword] Parameters username Specifies the name of the user you want to delete. Specifies that you want to connect to a remote installation of Access Server. Syntax DMDISABLEUSER username [-accessserver hostname port adminuser adminpassword] Parameters username Specifies the name of the user you want to disable. accessserver hostname port adminuser adminpassword These parameters are optional. This prevents the user from logging into Management Console. If you have installed Access Server on the same machine as Management Console. To delete a user.

accessserver hostname port adminuser adminpassword These parameters are optional. Setting up datastores and user accounts in Access Manager 47 . This list specifies the names of the users assigned to this datastore. you must be a System Administrator and have the privilege to manage datastores and user accounts. dmlistdatastoreusers—Generating a report list of users assigned to a datastore Use this command to generate a list of users assigned to a specific datastore. then these parameters are not required. Specifies that you want to connect to a remote installation of Access Server. To generate a report list. To generate a report list. accessserver hostname port adminuser adminpassword These parameters are optional.Parameters username Specifies the name of the user you want to enable. Specifies that you want to connect to a remote installation of Access Server. If you have installed Access Server on the same machine as Management Console. you must be a System Administrator and have the privilege to manage datastores and user accounts. then these parameters are not required. dmlistuserdatastores—Generating a report list of datastores assigned to a user Use this command to generate a list of datastores assigned to a specific user. Syntax DMLISTDATASTOREUSERS adminUser adminPassword datastoreName Parameters adminUser Specifies the name of the System Administrator. If you have installed Access Server on the same machine as Management Console. datastoreName Specifies the name of the datastore you want to generate a list for. adminPassword Specifies the password of the System Administrator. Syntax DMLISTUSERDATASTORES username [-accessserver hostname port adminuser adminpassword] Parameters username Specifies the name of the user you want to generate a list for. This list specifies the datastores assigned to this user.

v OPERATOR—specifies a that user assigned to this role is working in an Operator account and only has access to the Monitoring perspective in Management Console. FALSE indicates that the System Administrator has not been given these privileges. Locked Specifies if the account has been locked. then these parameters are not required. PwdChange Specifies if the user is required to change their password the next time the user 48 InfoSphere Change Data Capture Management Console: Administration Guide . Output User Specifies the name of the user. TRUE indicates that the account is disabled. Specifies that you want to connect to a remote installation of Access Server. Role Specifies the role assigned to the user. TRUE indicates that the System Administrator has been given these privileges. Disabled Specifies if the account has been disabled. To list users. but cannot modify system parameters. If you have installed Access Server on the same machine as Management Console. Syntax DMLISTUSERS [-accessserver hostname port adminuser adminpassword] Parameters accessserver hostname port adminuser adminpassword These parameters are optional. Only users that require full operational access to the Monitoring and Configuration perspectives should be assigned to this role. Manager Specifies if the user assigned to the role of System Administrator has also been assigned privileges to manage datastores and user accounts.dmlistusers—Listing user accounts Use this command to generate a list of users and properties on the account. This is automatically set to TRUE if the number of failed login attempts exceeds the locking policy you may have set. System administrators can also modify system parameters to calibrate their replication environment. v ADMIN—specifies that a user assigned to this role is working in an Administrator account and can perform all available operations in Management Console. v SYSADMIN—specifies that a user assigned to this role is working in a System Administrator account and can perform all available operations in Management Console. Users assigned to this role can access both the Monitoring and Configuration perspectives. v MONITOR—specifies that a user assigned to this role is working in a Monitoring account and only has access to the Monitoring perspective in Management Console. you must be a System Administrator and have the privilege to manage datastores and user accounts. FALSE indicates the account is enabled.

Users can view the replication state and status of a subscription and can view latency threshold information. configure replication. and monitor replication activities. and can view notifications sent by subscriptions or datastores. refresh tables. accessserver hostname port adminuser adminpassword These parameters are optional. FALSE indicates the password does expire based on an expiry policy. or view notifications sent by subscriptions and datastores. FALSE indicates the user can use the same password assigned to them. TRUE indicates the user is required to change the password. v Users assigned to the Monitor role can view the event log.logs into Management Console. view statistics. However. Operators also have access to the Replication Diagram view. you must be a System Administrator and have the privilege to manage datastores and user accounts. TRUE indicates the password supplied will not expire and overrides any expiry policy. Specifies that you want to connect to a remote installation of Access Server. stop. When you reset a user account. To reset a user account. Monitors also have access to the Replication Diagram view. Notes: v Users assigned to the Operator role can start. Expires Specifies if the user account overrides any existing password expiry policy set in Management Console. users assigned to this role cannot configure replication and select or remove tables from a refresh. the following properties are returned to their defaults: v the password is set to an empty string v the account is enabled v the account is unlocked v the user must change their password at next login v the password is set to follow the password expiry policy Syntax DMRESETUSER username [-accessserver hostname port adminuser adminpassword] Parameters username Specifies the name of the user account that needs to be reset. They can also view the tables selected for refresh and start a refresh on a subscription. then these parameters are not required. and view table mappings. If you have installed Access Server on the same machine as Management Console. A user account is automatically locked after the number of failed login attempts exceeds the locking policy you may have Setting up datastores and user accounts in Access Manager 49 . However. users assigned to this role cannot start or stop replication. dmresetuser—Resetting a user account Use this command to reset a user account. dmunlockuser—Unlocking a user account Use this command to unlock a user account.

then these parameters are not required. 50 InfoSphere Change Data Capture Management Console: Administration Guide . accessserver hostname port adminuser adminpassword These parameters are optional. you must be a System Administrator and have the privilege to manage datastores and user accounts.set in the Access Server Options dialog box in Management Console. Specifies that you want to connect to a remote installation of Access Server. Syntax DMUNLOCKUSER username [-accessserver hostname port adminuser adminpassword] Parameters username Specifies the name of the user you want to unlock. To unlock a user. If you have installed Access Server on the same machine as Management Console.

you are required to manually connect to each datastore after logging in. and one for each datastore that connects to Access Server. Connect to Datastores Automatically—when checked. When unchecked. specify outbound ports for Access Server. and choose whether you want to connect to datastores automatically after logging in to Management Console. In this section. 4. Click Edit → Preferences. The following ports are required: one for connection to Access Server. you will learn: “Setting connection preferences” “Setting advanced preferences” on page 52 “Setting prompt preferences” on page 53 “Setting statistics preferences” on page 54 “Setting the behavior of progress windows” on page 55 “Showing usability hints” on page 55 “Setting view preferences” on page 55 “Setting character encodings” on page 56 Setting connection preferences You can set the default port. Click Connection. Click Apply. Default Port—the default port is a unique TCP/IP number that is used to connect to Access Server. 2008 51 . You specify this port number when you install Access Manager and when you log in to Management Console. Related concepts “Setting connection preferences” © Copyright IBM Corp. 2. 3. Type the unique TCP/IP port number in the Default Port text box. automatically connects to datastores after logging into Management Console.Setting preferences in Management Console Preferences allow you to control certain aspects of the behavior of Management Console. See also: “To specify a default port number” “To specify outbound ports” on page 52 “To connect to databases automatically” on page 52 To specify a default port number 1. Specify Outbound Ports—sets the starting port number and number of ports you require to go through a firewall to Access Server. Note: You can click Restore Defaults at any time to use the default preferences.

Click Edit → Preferences. If you do not require an automatic prompt when mapping tables. 3. Click Apply. The describe and general timeout values indicate how long Management Console waits for a response from the datastore. 2. You can increase the timeout interval if necessary and adjust the amount of memory available for Management Console. In the Integration Server Timeouts area. 4. 4. v Allocate memory for Management Console. 52 InfoSphere Change Data Capture Management Console: Administration Guide . Click Apply. Click Connection. Enable the Connect to Datastores check box. Click Edit → Preferences. Related concepts “Setting connection preferences” on page 51 Setting advanced preferences You can set the following advanced preferences: v Set timeout values. Enable the Specify Outbound Ports check box. Type the starting port in the Starting Port box. 3. See also: “To set timeout values” “To allocate memory for Management Console” on page 53 “To verify that an automatic prompt for filtering tables is enabled” on page 53 “To disable an automatic prompt for filtering tables” on page 53 To set timeout values 1. v By default. Type the number of ports in the Number of Ports box. you can disable this option. Click Edit → Preferences. Management Console automatically prompts you to set a filter when retrieving a large number of tables from your database. Click Apply. Note: You can click Restore Defaults at any time to use the default preferences. 2. Click Connection. 5. 2. Related concepts “Setting connection preferences” on page 51 To connect to databases automatically 1. Note: You can click Restore Defaults at any time to use the default preferences.To specify outbound ports 1. type values in the following boxes: v Describe Timeout (in minutes) v General Timeout (in minutes) 4. 3. Click Advanced. 6.

Type the maximum amount of memory (in megabytes) you want to allocate for Management Console in the Maximum Memory box. Setting prompt preferences The preferences for prompts allow you to control when Management Console prompts you for confirmation before performing certain tasks. 2. 4. etc.To allocate memory for Management Console 1. Ensure that there is a value greater than 0 in the Minimum number of tables box. Click Edit → Preferences. Click Apply. 3. table mappings. 4. Setting preferences in Management Console 53 . subscriptions. To verify that an automatic prompt for filtering tables is enabled 1. Click Edit → Preferences. such as users. Clear the Automatically prompt for filter when expanding nodes check box. You can enable the following prompt preferences: Requesting Configuration Details from Monitoring—enables Management Console to prompt you before switching from the Monitoring perspective to the Configuration perspective when you want to edit a table mapping. Click Apply. Click Apply. Deleting Objects–enables Management Console to prompt you for confirmation before deleting objects. To disable an automatic prompt for filtering tables 1. 3. 4. 3. Starting or Ending Replication—enables Management Console to prompt you for confirmation before starting or ending replication. 2. Updating Access Parameters—enables Management Console to prompt you with a confirmation message before opening the Update Access Parameters dialog box. Click Advanced. Switching to Monitoring with Outstanding Changes—enables Management Console to prompt you if there are outstanding changes in the Mapping Details view. Click Advanced. 2. The message warns you that setting a capture point will update the bookmark for the table. Marking a Table Capture Point—enables Management Console to prompt you with a confirmation message before setting a capture point for a table. Click Advanced. Click Edit → Preferences. 5. Ensure the Automatically prompt for filter when expanding nodes check box is enabled.

3. 3. Specify the prompt options you want by enabling the appropriate check boxes. Note: You can click Restore Defaults at any time to use the default preferences. 3. You can set the following preferences: Statistics History Retained (minutes)—the length of time that Management Console retains data for the statistics view. Click Apply. Click Prompts. 54 InfoSphere Change Data Capture Management Console: Administration Guide . Statistics Sample Rate (seconds)—the frequency at which Management Console collects data for the statistics view. Setting statistics preferences The preferences for statistics let you control how Management Console collects statistics for your replication environment. Click Edit → Preferences. Type the number of minutes in the Statistics Sample Rate (seconds) box. 4. 4.Shutting Down Datastore—enables Management Console to prompt you with a confirmation message before shutting down a InfoSphere CDC for Oracle datastore. To set the sample rate for data collection 1. Click Edit → Preferences. See also: “To set prompt preferences” To set prompt preferences 1. Click Statistics. Click Apply. See also: “To set the length of time for data retention” “To set the sample rate for data collection” To set the length of time for data retention 1. 4. A lower number will increase the frequency of data collection. 2. 2. Click Statistics. Note: You can click Restore Defaults at any time to use the default preferences. Click Edit → Preferences. 2. Click Apply. Type the number of minutes in the Statistics History Retained (minutes) box.

Click Prompts. 2. 2. Click Edit → Preferences. Enable the Close Progress Windows Automatically check box. See also: “To set how subscriptions are grouped” “To save project layouts automatically” on page 56 “To set the number of events” on page 56 To set how subscriptions are grouped 1. Showing usability hints You can choose to have Management Console display a usability hint for source objects below the source columns on the Column Mappings tab in the Mapping Details view. Click Prompts. See also: “To show usability hints” To show usability hints 1. 3. Click Edit → Preferences. Setting view preferences Set preferences for view to control: v How Management Console groups subscriptions in the Subscriptions view. Enable the Show Hint for Mapping to Target Columns box. 4. 3. 2.Setting the behavior of progress windows You can choose to have Management Console automatically close progress windows after applying changes. 3. v The number of events Management Console displays in the Event Log view. 4. Enable one of the following options: v Project v Source Datastore v Target Datastore Setting preferences in Management Console 55 . Click Apply. v If Management Console saves changes to the project layout in the Replication Diagram view. Click Edit → Preferences. See also: “To automatically close progress windows” To automatically close progress windows 1. Click Apply. Click Views.

Choose one of the following from the Character Length box. Setting character encodings Management Console provides standard character sets and default encodings. 4. Click Apply. This is dependent on database platform. Click Apply. 2. 7. Click Add. In the Character Set box. 2. To save project layouts automatically 1. 3. See also: “To add a character encoding” “To modify a character encoding” on page 57 “To delete a character encoding” on page 57 “To import the CSV template” on page 57 “To export the CSV template” on page 57 To add a character encoding 1. Click Edit → Preferences. Click Apply. 4. v Single-byte 56 InfoSphere Change Data Capture Management Console: Administration Guide . Specify the number of events you want Management Console to fetch in the Number of Events to fetch box. Refer to the Java™ Supported Encodings Document for a list of supported ISO/IANA encoding names. Enable the Save Project Layouts Automatically check box. 4. 2. 5. Type the supported encoding name in the ISO/IANA Name box. Type the encoding name in the Encoding Name box. A Coded Character Set Identifier (CCSID) is a unique 16-bit number identifying a set of encoding scheme identifiers. 5. character set identifiers. Type the supported encoding name in the IBM CCSID box. Specify the number of events you want Management Console to display on a page in the Number of Events on a page box. To set the number of events 1. 6. code page identifiers. 3. Click Edit → Encodings. These become available for encoding conversion on the Translations tab in Management Consoles. and additional coding-related required information. You can add character sets and encodings to Management Console that are different from the default encodings. Click Views. Click Views. You can also import and export character sets and encodings if you need share these settings.4. 3. type a name for the character set or select an existing set. Click Edit → Preferences.

Select the character set. Click Delete. A Coded Character Set Identifier (CCSID) is a unique 16-bit number identifying a set of encoding scheme identifiers. 6. code page identifiers. Related concepts “Setting character encodings” on page 56 To import the CSV template 1. 2.v Double-byte v Multi-byte Related concepts “Setting character encodings” on page 56 To modify a character encoding 1. In the Character Set box. v Single-byte v Double-byte v Multi-byte Related concepts “Setting character encodings” on page 56 To delete a character encoding 1. Type a name for the template in the File Name box. Type the supported encoding name in the ISO/IANA Name box. type a name for the character set or select an existing set. Click Edit → Encodings. Refer to the Java Supported Encodings Document for a list of supported ISO/IANA encoding names. Click Import. 2. 3. This is dependent on database platform. Type the encoding name in the Encoding Name box. Related concepts “Setting character encodings” on page 56 To export the CSV template 1. Type a name for the template in the File Name box. 7. Type the supported encoding name in the IBM CCSID box. Click Import. 3. 2. Related concepts “Setting character encodings” on page 56 Setting preferences in Management Console 57 . Click Modify. 3. and additional coding-related required information. Click Edit → Encodings. 4. character set identifiers. 2. 5. Click Edit → Encodings. Choose one of the following from the Character Length box.

58 InfoSphere Change Data Capture Management Console: Administration Guide .

DB2® UDB for iSeries®. Notes: v Before you can connect to a datastore in Management Console. you can connect to datastores on several different platforms. including Microsoft® SQL Server. 2. See also: “To connect to a datastore” To connect to a datastore 1. Click Connect. you must have user access to a datastore. Depending on the database platform on which you have installed InfoSphere CDC. © Copyright IBM Corp. then this datastore is listed with the following icon: . You can set preferences to connect to a datastore automatically. In this section. Each datastore represents the database to which you want to connect and acts as a container for your tables. 3. select the datastore and right-click Properties. For more information. v If Management Console cannot establish a connection with a particular datastore. Oracle. make sure you are in the Datastores view. each time you log into Access Server. Tables made available for replication are contained in a datastore. see “Assigning users to datastores” on page 30. 2008 59 . request your system administrator to set access parameters for you in the Access Manager perspective in Management Console. To view general information. your system administrator must have given you user access to that datastore. and JDBC. You can view general information about the datastore and possible reasons as to why a connection could not be established in the Datastore Properties dialog box. you will learn: “Connecting to a datastore” “Shutting down a datastore (InfoSphere CDC for Oracle)” on page 60 “Updating access parameters for a subscription” on page 60 “Setting system parameters on source and target datastores” on page 60 “Creating aliases for a target datastore on a private network connection” on page 61 Connecting to a datastore Before you can connect to a datastore.Setting up datastores for replication Datastores are logical entities that represent the data files and processes required to accomplish data replication. Click File → Connect to Datastores. Select the datastore. If you do not see a datastore listed.

System parameters let you customize the behavior of InfoSphere CDC in your replication environment. modify. 60 InfoSphere Change Data Capture Management Console: Administration Guide . you must specify the access parameters that InfoSphere CDC uses to connect to the database. then you need to update each subscription that uses this datastore as a target in Management Console. Click General. and password. Setting system parameters on source and target datastores You can add. you must shut down the associated datastore in Management Console. Click Update. Click Update Related Subscriptions. Select Disconnect. or delete system parameters for datastores. Right-click on a datastore and select Shut down datastore . you must restart Management Console. You can specify system parameters in Management Console or modify system parameters on the replication servers by performing server-dependent operations. 5. 4. Right-click on a datastore and select Properties. 2. If there are any active subscriptions. Click File → Access Server. 1. 6. Note: After changing the access parameters for a datastore in Access Manager. 2. When you change the value of a system parameter for a particular source or target datastore. Click Configuration → Datastores.Shutting down a datastore (InfoSphere CDC for Oracle) When you want to end all InfoSphere CDC Access Manager replication processes to perform database or operating system maintenance activities. See also: “To update access parameters for a subscription” To update access parameters for a subscription Click Configuration → Datastores. Updating access parameters for a subscription When configuring a datastore in Access Manager. Access parameters include information such as a user ID. 3. click End Replication on each active subscription. all users that have access to that datastore can see the change as well. This ends replication on all active subscriptions. See also: “To shut down a datastore” To shut down a datastore 1. database name. If at some point you decide to change access parameters for a datastore. 4. 3.

On the Source Parameter tab. you will learn: Related concepts “Setting system parameters on source and target datastores” on page 60 To modify a system parameter 1. Type the name of the parameter in the Parameter Name box. However. 2. 5. Type the value in the Value box. etc. 4. 3. 3. Click Configuration → Datastores. In this section. click Add. Data Source Name (DSN). Setting up datastores for replication 61 . Click Delete. 4. Right-click on a datastore and select Properties. this could be a hostname. you can modify the a system parameter to specify a behavior for InfoSphere CDC that is different than the default. The Access Manager perspective uses the alias to connect to the target datastore.The default values for most system parameters should be adequate. then you need to identify the name your source datastore uses to recognize that target datastore. Click Configuration → Datastores. You can identify this name by creating an alias in Management Console. Related concepts “Setting system parameters on source and target datastores” on page 60 To delete a system parameter 1. 5. depending on your requirements. Right-click on a datastore and select Properties. If you want to create a subscription that replicates data to a target datastore on a private network connection. Type a value in the Value box. Select either Source Parameter or Target Parameter. 2. 2. On the System Parameters tab. Related concepts “Setting system parameters on source and target datastores” on page 60 Creating aliases for a target datastore on a private network connection The Access Manager perspective uses the hostname or the IP address you specified to connect to your target datastore. IP address. Right-click on a datastore and select Properties. See also: “To add a system parameter” “To modify a system parameter” “To delete a system parameter” To add a system parameter 1. select a system parameter. see “To set connection parameters on a datastore” on page 25. Click Modify. Click Configuration → Datastores. On the System Parameters tab. For more information on how to set up connection parameters to connect to a datastore. Depending on your environment. 6. select a system parameter. 4. 3.

Type a name in the Alias box. On the Alias tab. select an alias. 2. On the Alias tab. 4. 2. Right-click on a datastore and select Properties. 3. Related concepts “Creating aliases for a target datastore on a private network connection” on page 61 To delete an alias 1. 3. Click Delete. Related concepts “Creating aliases for a target datastore on a private network connection” on page 61 To modify an alias 1. Right-click on a datastore and select Properties. 4. Click Configuration → Datastores. 4. Click Configuration → Datastores. Right-click on a datastore and select Properties. click Add.See also: “To add an alias” “To modify an alias” “To delete an alias” To add an alias 1. Click Modify. 2. select an alias. 3. On the Alias tab. Related concepts “Creating aliases for a target datastore on a private network connection” on page 61 62 InfoSphere Change Data Capture Management Console: Administration Guide . Type a name in the Alias box. Click Configuration → Datastores. 5.

3.2 and created a datastore.source_table -> database2.4.target_table. Log into Management Console. you must complete the following tasks: v Upgrade subscriptions by selecting new names. and source and target datastores.4 to 6. The upgrade process may not be automatic if your subscriptions depend on notifications or output from expressions.2” Upgrading Transformation Server subscriptions from version 5.2 by following the upgrade process outlined in this section. The Transformation Server instances and datastores should be associated with the database containing the tables being replicated by Transformation Server for Microsoft SQL Server version 5. Note: Contact IBM support before you begin the upgrade process.2 To upgrade subscriptions. In this section.2” “To transfer a bookmark to a new subscription” on page 64 “To clear the log position for a subscription” on page 64 To upgrade a subscription to Transformation Server for Microsoft SQL Server version 6.3.user. you must refresh the tables in the subscription.2 1.4 subscription after clearing the log position.4 to 6.4 to version 6. 2. you will learn: “Upgrading Transformation Server subscriptions from version 5. Ensure that you have installed Transformation Server for Microsoft SQL Server version 6. If you want to resume mirroring with the version 5.Upgrading subscriptions InfoSphere CDC allows you to upgrade your subscriptions from InfoSphere CDC for Microsoft SQL Server version 5.2 on database1 and database2 to upgrade the subscription. v Clear the log position for old subscriptions. © Copyright IBM Corp.3. If you are upgrading a subscription that uses two databases.user. you will have to install Transformation Server for Microsoft SQL Server version 6. Note: Transformation Server® for Microsoft SQL Server version 5.4 supports multiple databases whereas Transformation Server for Microsoft SQL Server version 6. v Transfer the bookmark from your old subscriptions to the new upgraded subscriptions. such as database1. See also: “To upgrade a subscription to Transformation Server for Microsoft SQL Server version 6. After transferring the bookmark.3.3. 2008 63 . you can also move the bookmark back to the original subscription. new source IDs. Your datastore must support bookmark transfer. This task is optional and will prevent you from resuming replication with these subscriptions.2 supports a single database.3.

2. Select a new target datastore for each subscription in the Target Datastore box.4 as a source or target datastore and click Subscription → Upgrade → Upgrade Subscription. To install Transformation Server for Microsoft SQL Server version 6. 4. Click Continue if you want to upgrade your subscriptions without assistance from Product Support. Related tasks “To upgrade a subscription to Transformation Server for Microsoft SQL Server version 6.2 datastore. 11. Connect to the Transformation Server for Microsoft SQL version 5. Click Subscription → Upgrade → Transfer Bookmark. Enable the Transfer to New Subscription check box for subscriptions for which you want to transfer the bookmark.Management Console displays all subscriptions for which you can clear the log position.2 documentation. Click Transfer Bookmark to transfer the bookmark to the specified subscriptions. 4. Related tasks “To log in to Management Console” on page 21 “To connect to a datastore” on page 59 To transfer a bookmark to a new subscription 1.2 of Transformation Server. 5. Management Console displays a report that outlines any issues encountered during the bookmark transfer process. Connect to the Transformation Server for Microsoft SQL Server version 6. To view the upgrade report for the subscription.. 5. check box if you want to start mirroring after transferring the bookmark. 10. Type a new source ID for each subscription in the New Source ID box. 2. . 9.. Click Subscriptions → Upgrade → Clear Log Position. 64 InfoSphere Change Data Capture Management Console: Administration Guide . 7. Click Configuration → Subscriptions. After upgrading your subscription. Enable the After transferring bookmark. Management Console displays an upgrade report that outlines any issues encountered during the upgrade process to version 6. Select one or more subscriptions that use Transformation Server for Microsoft SQL version 5. Click OK to upgrade your subscription. Click Configuration → Subscriptions.3. Select a new source datastore for each subscription in the Source Datastore box.3. Click Configuration → Subscriptions.Management Console displays all subscriptions for which you can transfer the bookmark.3. see the Transformation Server for Microsoft SQL Server version 6. 3. 12..2. click View Upgrade Report. 6. 6.4 datastore. You can resume mirroring with these subscriptions.2” on page 63 “To clear the log position for a subscription” To clear the log position for a subscription 1. Type a new name for each subscription in the New Name box. After transferring the bookmark.. 8.

2” on page 63 “To transfer a bookmark to a new subscription” on page 64 Upgrading subscriptions 65 . 4.3. Enable the Clear Log check box for subscriptions for which you want to clear the log position. Related tasks “To upgrade a subscription to Transformation Server for Microsoft SQL Server version 6. Click Clear Log Position to set the replication method for the specified subscriptions to Refresh. You will not be able to resume replication with this subscription.

66 InfoSphere Change Data Capture Management Console: Administration Guide .

4. update the definition of the table if you have changed the structure in your database. See also: “To update the definition of a table” “To remove a table from Management Console” “To view the properties of a table” on page 68 To update the definition of a table 1. Right-click Replication Tables. 2008 67 . Related concepts “Updating. Select a datastore. 3. and viewing tables for replication” To remove a table from Management Console Ensure there are no subscriptions using the tables in replication. and to remove tables no longer in use by subscriptions for replication. to view the properties of tables. Select the table and click Remove. and viewing tables for replication Use the Replication Tables dialog box to update the definition of a table that has changed in your database. 6. 3. Tables are only available if you have created a table mapping in the Map Tables wizard. Select a datastore. Select the table that has changed in your relational database management system and click Update. Click Configuration → Datastores. Tables are only available if you have created a table mapping in the Map Tables wizard. and remove any tables from Management Console. 2. 2. and viewing tables for replication” Updating. Expand the database user or schema until you display its tables. 4. removing. Click Configuration → Datastores. In this section. Note: If you have deleted tables from your RDBMS (relational database management system). You make tables available fro replication by selecting tables for a table mapping in the Map Tables wizard. you will learn: “Updating. then you also need to remove the table from the Replication Tables dialog box. 5. removing. © Copyright IBM Corp. 5. Expand the database user or schema until you display its tables. Right-click Replication Tables.Managing tables available for replication You can view the tables that are available for replication. 1. removing.

Expand the database user or schema until you display its tables. 5. you must first search for tables used in the replication by subscriptions. removing. 4.Notes: v Before removing the table. 3. Right-click Replication Tables. 68 InfoSphere Change Data Capture Management Console: Administration Guide . Related concepts “Updating. Tables are only available if you have created a table mapping in the Map Tables wizard. 2. Select the table and click Properties. v Remove a table only if you have first deleted it from your relational database management system and it is still available for replication in Management Console. and then delete the table mapping if necessary. Select a datastore. and viewing tables for replication” on page 67 Related tasks “To delete a table mapping” on page 140 To view the properties of a table Click Configuration → Datastores. Related concepts “Searching for tables used in replication” on page 86 “Updating. removing. and viewing tables for replication” on page 67 1.

This means that each subscription that uses the datastore for replication inherits the notification settings by default. Copying notifications You can copy notification settings to notification categories in the same datastore or subscription. 2008 69 . you may have already set an email notification that gets sent to jane@datamirror. Using the event ID. Email notification settings include information such as the name of the person to which you send a notification or the subject line of an email. When an event occurs in your replication environment. For example. Instead of having to manually specify that jane@datamirror. if you want to be notified when mirroring fails on a subscription. you can copy this setting to other notification categories. Before you setup an email notification for MAPI. you can specify the event ID for that message in the Filter Messages dialog box. but want all those notifications sent to the same account. For example.com when the datastore DM0001@50000 on the source-side detects a fatal communications error on the network. Each message is identified with an event ID. the InfoSphere CDC loads these as default notification settings across all subscriptions that use that datastore. you can specify the messages for which you want to be notified or those which should be suppressed. © Copyright IBM Corp. Notifications are most useful when performing diagnostic analysis of replication activities in the Management Console and you want to detect events that are happening in your source and target datastores and/or subscriptions.Setting notifications You can use notifications when you want to be alerted of any problems in your replication environment. or set notifications so that they are sent from a subscription. Set notifications from the datastore before setting notifications from each subscription. InfoSphere CDC generates messages in the Event Log view. You can copy this information to other notification categories in the same datastore. This is to help you during diagnose and track the location of your notifications. Setting notifications for datastores and subscriptions You can set notifications so that they are sent from either a source or target datastore. then you can set the notification at the subscription level. if you have a subscription that uses the same datastore in some special way. Setting notifications at the datastore level is useful when you want to set the same notifications for all your datastores regardless of which subscriptions use them. However. You may have set other notifications that get sent in different events.com receive all notifications detected from DM0001@50000 in each notification. When you set a notification on the datastore. Filtering notifications You can filter notifications. you should read the considerations outlined for these protocols in your InfoSphere CDC for Microsoft SQL Server documentation.

70 InfoSphere Change Data Capture Management Console: Administration Guide . you can select certain notification handlers in the Notifications dialog box: v Message Queue—You can indicate that you want to relay a message to a specified message queue when a certain type of message is generated. Unless explicitly stated. Notification handlers specify how you want a certain notification to be handled. To specify a message queue. you may want to send messages to an email address. Note that you are responsible for creating the user exit program and ensuring that it works properly. For example. each setting described below applies to both SMTP and MAPI. Depending on the type of datastore. v User Exit/User Handler—You can indicate that you want to launch a user exit program when a certain type of message is generated. For more information about creating user exit programs for alerts and alarms. you need to specify both the name of the message queue and the library where it resides. You can set a notification so that it is handled through email. SMTP (Simple Mail Transfer Protocol) and MAPI (Messaging Application Program Interface) can be used for sending email messages. You must specify a threshold before you can set up a notification. see the appropriate InfoSphere CDC End-User Documentation. You have the option of relaying that message to up to ten different message queues. Depending on the InfoSphere CDC product you have installed. you will learn: “Selecting a notification handler” “Choosing a notification category and a message type” on page 71 “Setting notifications for a datastore” on page 72 “Setting notifications for a subscription” on page 77 “Copying notifications for a subscription” on page 78 “Setting latency thresholds and notifications” on page 78 Selecting a notification handler Before setting up a notification. In this section. or user exits.Setting latency thresholds and notifications You can also set latency notifications that alert you when InfoSphere CDC has passed your warning or problem thresholds. or you may prefer to set up a user exit that triggers certain operations upon specific InfoSphere CDC events. relay a message to a message queue. v TSDPRINT—You can indicate that you want to send the generated message to the TSDPRINT spool file provided with InfoSphere CDC for z/OS®. v Event Log—You can indicate that you want to send the generated message to the Windows application log. v SNMP (Simple Network Management Protocol)—You can indicate that you want to send a trap containing the generated message to an SNMP management system. message queues. v Email—You can indicate that you want to send the generated message to an email address. you need to decide on the kind of notification handler you want to use to receive notifications.

v Communications Events—categorizes notifications that are generated for communication events that can occur between source and the target datastores. InfoSphere CDC sends a notification when it encounters an error. For example. Notification categories Notification categories represent the events that InfoSphere CDC detects in your source and/or target datastores. Notification message type v Fatal Messages—enables you to setup a notification for fatal messages. For example. you must select a notification category and a notification message type. For more information about the operator system log. InfoSphere CDC sends a notification when it encounters an event that you need to know about. v Journal/Log Maintenance Events—categorizes notifications that are generated when InfoSphere CDC reads the journal or during log maintenance. see the InfoSphere CDC for z/OS End-User Documentation. InfoSphere CDC can generate an error message in the Event Log view when it inserts a row and creates a duplicate key. v Apply Events (Target)—InfoSphere CDC generates notifications related to events that occur during the target apply process. v Scrape/Refresh Events (Source)—categorizes notifications that are generated for events that occur when InfoSphere CDC scrapes or refreshes data from your source datastore. or when it encounters instances that require code page conversions. For example. or when it encounters a runtime verification error on a derived expression. InfoSphere CDC can generate a message when there is failure to apply on the target table. For example. InfoSphere CDC v Error Messages—enables you to setup a notification for error messages. v Oracle (on UNIX servers only)—You can indicate that you want to send a generated message to the UNIX syslogd program that logs messages from external applications like InfoSphere CDC Related concepts “Setting notifications for a datastore” on page 72 “Setting notifications for a subscription” on page 77 Choosing a notification category and a message type When setting up a notification. For example. or when permissions have not been set. Setting notifications 71 . InfoSphere CDC can generate a message when it cannot connect to a database. InfoSphere CDC can generate informational messages in the Event Log view when it is ready to mirror tables. For example.SYSLOG v DB2 UDB for z/OS–You can indicate that you want to send the generated message to the operator system log maintained on zSeries® servers. v Informational Messages—enables you to setup a notification for informational messages. InfoSphere CDC can generate a message when there is a failure to create TCP/IP socket. v Environment Events—categorizes notifications that are generated when requirements for a basic replication environment are not met.

InfoSphere CDC sends a notification when it has completed an operation during replication. 2. InfoSphere CDC can generate messages for events that occur on either your source or target datastore. v Operational Messages—enables you to setup a notification for operational messages. Click Configuration → Datastores. Type the email address in the Alert Account box.3. 6. Related concepts “Setting notifications for a datastore” “Setting notifications for a subscription” on page 77 Setting notifications for a datastore Use the Source tab or the Target tab in the Notifications dialog box to set up a notification. For example. Use a semi-colon to separate multiple email addresses or specify a distribution list from your email application.v Status Messages—enables you to setup a notification for status messages. 4. 3. 5. For example. Select a category from Notification Categories. Type the subject in theSubject box. Select Email (MAPI). InfoSphere CDC sends a notification when it encounters a specific event during replication. 72 InfoSphere Change Data Capture Management Console: Administration Guide . or when it has completed a refresh on a table. See also: “To set “To set “To set “To set “To “To “To “To “To “To “To “To an an an an email email email email (MAPI) notification” (SMTP) notification” on page 73 notification” on page 73 notification” on page 74 set a notification for the TSDPRINT spool file” on page 74 set a notification for an operator system log” on page 74 set a notification for a UNIX system log” on page 75 set a notification using a user exit program” on page 75 set a notification using a user exit program” on page 75 set a notification using a user exit program” on page 76 set a notification for a message queue” on page 76 filter a notification message” on page 77 “To copy notification settings” on page 77 To set an email (MAPI) notification Note: This information is applicable to InfoSphere CDC for Microsoft SQL Server version 5. 1. when it cannot journal changes on a table. or when it has parked a table for replication. InfoSphere CDC can generate status messages in the Event Log view when it is going to refresh a table. 7. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. InfoSphere CDC can generate operational messages in the Event Log view after applying an operation to the target table. click the Source tab or the Target tab. Right-click on a datastore and select Notification.

1.3. Right-click on a datastore and select Notification. Type the email address that will receive the email in the Alert Account box. Select a category from Notification Categories. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set an email (SMTP) notification Note: This information is applicable to InfoSphere CDC for Microsoft SQL Server version 5. 5. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. Use a semi-colon to separate multiple email addresses or specify a distribution list from your email application. 4. 4. Select the Email box. Type the subject in the Subject box. 3. click the Source tab or the Target tab. Type the email address in the Address box. click the Source tab or the Target tab. Type the email address that will send the generated messaged in the Sender Account box.8. Use a semi-colon to separate multiple email addresses or specify a distribution list from your email application. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 Setting notifications 73 . 5. The subject and profile name cannot exceed 254 characters. Select Email (SMTP). Select a category from Notification Categories. 7. 3. 7. 2. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set an email notification Note: This information is applicable to InfoSphere CDC for Oracle. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 6. The subject cannot exceed 254 characters. 8. 6. Type the name of the mail profile you created to identify the mailbox of the specific domain user in theProfile box. Type the host name of your outgoing mail server in the SMTP Mail Host box. Right-click on a datastore and select Notification. 2. Click Configuration → Datastores. 1. Click Configuration → Datastores.

5. 1. 1. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. Right-click on a datastore and select Notification. Select the Internet Mail box. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 2. Type the email address in the Alert Account box. click the Source tab or the Target tab. and InfoSphere CDC for Teradata. Click Configuration → Datastores. 4. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set a notification for the TSDPRINT spool file Note: This information is applicable to InfoSphere CDC for z/OS. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set a notification for an operator system log Note: This information is applicable to InfoSphere CDC for z/OS. 5. Select the TSDPRINT box. InfoSphere CDC for PointBase. click the Source tab or the Target tab. 6. Select a category from Notification Categories. InfoSphere CDC for Microsoft SQL Server version 6. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 74 InfoSphere Change Data Capture Management Console: Administration Guide .To set an email notification Note: This information is applicable to InfoSphere CDC for DB2 UDB.0. 3. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 1. Click Configuration → Datastores. Right-click on a datastore and select Notification. 4. Select a category from Notification Categories. Type the host name of your outgoing mail server in the SMTP Mail Host box. 2. Click Configuration → Datastores. 7. Select a category from Notification Categories. 2. 3. Right-click on a datastore and select Notification. 5. click the Source tab or the Target tab. Use a semi-colon to separate multiple email addresses or specify a distribution list from your email application. 4. Select the SYSLOG box. 3.

Note: This program supports up to eight log channels and identifies different locations where you can place messages. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 2. Select a category from Notification Categories. click the Source tab or the Target tab. 2. Right-click on a datastore and select Notification. Routes messages to the location specified in the configuration file (/etc/syslog.conf). You can configure log channels using a predefined configuration file (/etc/syslog.To set a notification for a UNIX system log Note: This information is applicable to InfoSphere CDC for Oracle. 3. 1. Setting notifications 75 . 1. 3. 4. 2. Type the number of the log channel in the Facilities box. You can attach an identifier for each message. 7. 5. 4.conf). click the Source tab or the Target tab. You should contact your UNIX system administrator to find out how many log channels are configured in your environment. 6. The number must be between 0 and 7 and it corresponds to the number specified in the configuration file. Select a category from Notification Categories. Right-click on a datastore and select Notification. 5. Select the User Exit box. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set a notification using a user exit program Note: This information is applicable to InfoSphere CDC for z/OS. 1. Right-click on a datastore and select Notification. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. Appends to all messages routed through the log channel. Type a string in the ID box. Click Configuration → Datastores. 6. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set a notification using a user exit program Note: This information is applicable to InfoSphere CDC for AS/400®. Click Configuration → Datastores. Type the name of the module in the box. Select the Syslog box. Click Configuration → Datastores.

Type the name of the library in the Library box. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 6. 4. Type the name of the library in the Library box. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 3. 4. 5. click the Source tab or the Target tab. Type the name of the message queue in the Queue box. Select the User Exit box. Select the Message Queue box. 7.0. click the Source tab or the Target tab. Select a category from Notification Categories. Click Configuration → Datastores. Type the name of the user exit program in the Program box. 6. Note: You can relay the same message up to 10 message queues. 5. Type the fully qualified Java class name of the user exit program in the Java Class Name box. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 76 InfoSphere Change Data Capture Management Console: Administration Guide . Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set a notification for a message queue Note: This information is applicable to InfoSphere CDC for AS/400. InfoSphere CDC for PointBase. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To set a notification using a user exit program Note: This information is applicable to InfoSphere CDC for DB2 UDB. Click Configuration → Datastores. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 7. and InfoSphere CDC for Teradata. 1.3. Select a category from Notification Categories. 5. 6. 1. 2. Right-click on a datastore and select Notification. 2. InfoSphere CDC for Microsoft SQL Server version 6. Select the User Handler box. 3. 4. Right-click on a datastore and select Notification. click the Source tab or the Target tab. Select a category from Notification Categories.

5.To filter a notification message 1. Before setting a notification for a subscription. 4. 2. and then decide on a severity level. Right-click on a datastore and select Notification. Type the event ID in the box. Click Filter Messages. 6. 2. Click Configuration → Datastores. ClickSource or Target. Clear the boxes for the notifications that you do not want to copy. 5. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 To copy notification settings 1. Right-click on a datastore and select Notification. Select one of the following: v Do not send these messages—Does not send the specified messages. you should do the following: v View any default notifications that were set at the datastore level for the subscription. 2. 4. then you can set notifications at the subscription level. 3. ClickCopy Settings. v Decide what kind of events you want to be notified about in your replication environment. When setting notifications you must first identify the category of the message you want to set. Right-click on a datastore and select Notification. click OK. 3. Click Configuration → Subscriptions. 6. Specify how you want to send this notification in the Notification Settings area. 5. Select the notification setting. Click Configuration → Datastores. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 Setting notifications for a subscription If you want to send a notification only when a datastore is used by a subscription. If you want to copy all notification settings. Click the Source tab or the Target tab. v Send these messages only—Sends the specified messages. Clear any default notifications settings to enable the Notification Settings area. See also: “To set notifications for a subscription” “To view the datastore default notifications for a subscription” on page 78 To set notifications for a subscription 1. Select a category from Notification Categories. 4. Setting notifications 77 . 3.

2. 5. you can send this notification through email message queues. You must set latency thresholds before you can set a notification. For example. If you want to copy all notification settings. ClickDatastore Defaults. 6. click the Source tab or the Target tab.Depending on the InfoSphere CDC product you have installed. Select the notification setting. Related concepts “Setting notifications for a subscription” on page 77 To view the datastore default notifications for a subscription 1.InfoSphere CDC sends you a notification after the following events: v Normal—latency for the journal or log is below the warning threshold. email notification settings include information such as the name of the person to which you send a notification. See also: “To copy notification settings” on page 77 To copy notification settings 1. 3. This means that latency is acceptable and within your normal range. ClickSource or Target. Latency is normal according to the latency thresholds you have set for the subscription. Right-click on a datastore and select Notification. 3. Depending on whether you want InfoSphere CDC to detect events on the source datastore or on the target datastore. 4. Click Configuration → Subscriptions. Related concepts “Setting notifications for a subscription” on page 77 Copying notifications for a subscription You can copy notification settings from one category to another in the same subscription. 78 InfoSphere Change Data Capture Management Console: Administration Guide . or a user exit program. Click Configuration → Datastores. Clear the boxes for the notifications that you do not want to copy. 4. This notification specifies how long it takesInfoSphere CDC to apply data to the target datastore. Related concepts “Setting notifications” on page 69 “Selecting a notification handler” on page 70 Setting latency thresholds and notifications You can set a notification that specifies the latency (in minutes) of a subscription. Right-click on a datastore and select Notification. The Notifications dialog box opens and displays the default notifications that were set for the datastore. click OK. or you can copy the subject line of an email between different notification categories on a subscription. When you set a notification. 2. ClickCopy Settings.

8. Specify a warning threshold (in minutes). ensure that Target → Apply → Informational is enabled.v Warning—latency for the journal or log is above the warning threshold but below the problem threshold. you will learn: Related concepts “Setting latency thresholds and notifications” on page 78 “Profiling the latency and throughput performance of your subscription” on page 235 Setting notifications 79 . 4. Depending on the InfoSphere CDC product you have installed. 2. The problem threshold must be greater than the warning threshold. Enable the Notify when latency crosses these thresholds check box. 6. Specify a problem threshold (in minutes). ClickSet Notification. Latency is now a problem according to the latency thresholds you have set for the subscription. Specify how you want to send this notification in the Notification Settings area. These changes will take effect the next time you start replication on this subscription. You must configure at least one notification setting in the Informational category so that you can receive notification messages and this must be set on the Target tab. In this section. As a best practice. Latency is starting to become a problem according to the latency thresholds you have set for the subscription. Click Configuration → Subscriptions. v Problem—latency for the journal or log is above the problem threshold. 3. Right-click on a subscription and select Latency Thresholds. or a user exit program. 5. you can send this notification through email message queues. See also: “To set a latency threshold and notification” To set a latency threshold and notification 1. 7.

80 InfoSphere Change Data Capture Management Console: Administration Guide .

In many working environments. For example. As you finish development or testing of a subscription. Subscriptions use datastores as the source or target of replicated data. you may want to group your subscriptions in projects according to their current development state. For example. Development. 2008 81 . organizations prefer to test a InfoSphere CDC replication configuration before promoting the configuration to a production environment. In this section. and some that have been promoted to production. you can use Test. finance. or sales. you may want to organize your subscriptions into projects that reflect these particular operations or departments.Setting up and managing subscriptions A subscription is a connection that is required to replicate data between a source datastore and a target datastore. you will learn: “Using projects to organize your subscriptions” “Exporting and importing projects” on page 82 “Setting up subscriptions” on page 83 “Specifying advanced settings for a subscription” on page 84 “Searching for tables used in replication” on page 86 “Setting up subscriptions for datastores outside of your organization” on page 86 “Copying subscriptions” on page 88 “Setting properties for a subscription that targets IBM WebSphere DataStage” on page 89 “Generating a WebSphere DataStage definition file for a subscription” on page 90 Using projects to organize your subscriptions Projects let you group your subscriptions into categories to reflect your organizational or operational needs. In this case. you can then move the subscription to the appropriate project. you may have subscriptions that relate to human resources. Operational Approach for Projects—The operational approach is useful if you are creating subscriptions that relate to particular departments or operations within your organization. See also: “To add a new project” on page 82 “To rename a project” on page 82 © Copyright IBM Corp. You can view the datastores that your subscriptions are using in the Source and Target columns of the Subscriptions view. If you have subscriptions that are still in development. It contains details of the data that is being replicated and how the source data is applied to the target. others that are being tested. and Production for project names. Organizational Approach for Projects—The organizational approach is useful if you want to group your subscriptions according to their current state of development.

Enter a unique name for your project. Right-click on a project and select Project → Rename Project. Click Configuration → Subscriptions.“To delete a project” To add a new project 1. 82 InfoSphere Change Data Capture Management Console: Administration Guide . 2. Related concepts “Using projects to organize your subscriptions” on page 81 Related tasks “To add a new project” “To delete a project” To delete a project 1. Right-click on a project and select Project → Export Projects. 2. 3. you can export your projects to a CSV template on your local computer. Right-click in the Subscriptions view and select Project → Add New Project. Related concepts “Using projects to organize your subscriptions” on page 81 Related tasks “To rename a project” “To add a new project” Exporting and importing projects Every user of Management Console will have a different approach to organizing their projects and subscriptions. To share your project organization with other users. Related concepts “Using projects to organize your subscriptions” on page 81 Related tasks “To rename a project” “To delete a project” To rename a project 1. 2. Click Configuration → Subscriptions. 2. 3. Other users can then import the CSV template into Management Console. Click Configuration → Subscriptions. See also: “To export projects” “To import projects” on page 83 To export projects 1. Enter a new name for your project. Management Console will delete the project and move all subscriptions to your Default project. Click Configuration → Subscriptions. Right-click on a project and select Project → Delete Project.

Select the CSV template that you want to import into Management Console and click Open. 6. 3. Existing projects will be deleted during project import. 4. How you decide to set up the datastores in your subscriptions depends on your replication requirements. Click Save. Type the name of the subscription in the Name box. then click Details and select the alias you created for the host name. Right-click on a project and select New Subscription. select an existing project or click New Project to create a new project. Type a name for the template in the File Name box. select the datastores you want to use as the source and target of data during replication activities. Click Configuration → Subscriptions. Select the source datastore from the Source list. 4. you need to add a subscription.3. From the Project list. and specify optional communication settings. 2. Right-click on a project and select Project → Import Projects. you can organize your subscription into a project. When adding a new subscription. Related concepts “Exporting and importing projects” on page 82 Related tasks “To export projects” on page 82 Setting up subscriptions Before you can start replicating data. 3. Setting up and managing subscriptions 83 . Click Configuration → Subscriptions. See also: “To add a subscription” “To modify a subscription” on page 84 “To delete a subscription” on page 84 To add a subscription 1. You will have to restart Management Console or reconnect to Access Server to see the changes. then select External and click Details to configure an external target datastore. 5. Notes: v If you want to replicate data to a target datastore using a host name that differs from the one used in Management Console. 7. Type the description of the subscription in the Description box. Related concepts “Exporting and importing projects” on page 82 Related tasks “To import projects” To import projects 1. 2. v If you want this subscription to send data to an external target. Select the target datastore from the Target list.

v You are using InfoSphere CDC Version 5. Related tasks “To end replication” on page 199 “To delete a table mapping” on page 140 “To connect to a datastore” on page 59 Specifying advanced settings for a subscription You can set communication settings for your subscription. then click Details and select the alias you created for the host name. If the subscription is sending data to an external target.2 and have a subscription with an external target datastore. Click Configuration → Subscriptions. Note: If you want to replicate data to a target datastore using a host name that differs from the one used in Management Console. You must connect to the target datastore before you can delete the subscription. You cannot delete a subscription when: v Your subscription is active. Click Configuration → Subscriptions. Click Advanced Settings.v By default. You can modify the following: v Description—Type the description of the subscription. Right-click on a subscription and select Properties. Before deleting a subscription. each new subscription you create is assigned a unique source ID in Management Console. 3. 2. you must end replication. Right-click on a subscription and select Delete subscription. Related concepts “Setting up subscriptions” on page 83 “Setting up subscriptions for datastores outside of your organization” on page 86 “Creating aliases for a target datastore on a private network connection” on page 61 To delete a subscription 1. you can specify a source ID that makes the subscription identifiable for the receiving organization. 2. Related concepts “Setting up subscriptions” on page 83 “Setting up subscriptions for datastores outside of your organization” on page 86 “Creating aliases for a target datastore on a private network connection” on page 61 To modify a subscription 1. You must remove the table mappings for the subscription before you can delete the subscription. v Your subscription is not connected to the target datastore. 84 InfoSphere Change Data Capture Management Console: Administration Guide . v Project—Select a project or click New Project to create a new project.

This is useful if you want to specify a host that you specified in the Access Manager perspective. Setting up and managing subscriptions 85 . v Propagation Control—you can use propagation control to prevent the replication of data from a particular source. then ports 2000. This is useful if you are using a hub-and-spoke replication configuration and prevents subscriptions from unnecessarily repeating operations like inserting data. 3. This is useful if you want to specify a host that is different from the host that you specified in InfoSphere CDC Access Manager. Click Configuration → Subscriptions. Click Advanced Settings. 2. and 2003 must all be accessible through the firewall. Type a port number in the Firewall Port box. Right-click on a subscription and select Properties. 2001. Related concepts “Specifying advanced settings for a subscription” on page 84 To set propagation control on a subscription 1. Click Advanced Settings. For example. you may need to specify a firewall port for your subscription. v TCP Host—specifies the TCP host that your source datastore will use to recognize the target datastore when the computer where InfoSphere CDC is installed has multiple network cards. 2. Type the TCP host name for the subscription in the TCP Host box. Your source datastore will use this name to recognize the target database when the computer where InfoSphere CDC is installed has multiple network cards. if you enter port 2000 in this field.v Firewall Port—if the source and target datastores have a limited number of ports for communication through a firewall. Right-click on a subscription and select Properties. Click Configuration → Subscriptions. Right-click on a subscription and select Properties. See also: “To specify a TCP host for a subscription” “To specify a firewall port for a subscription” “To set propagation control on a subscription” To specify a TCP host for a subscription 1. The host that you specified in the Access Manager perspective also appears by default as well as any aliases that you configured in the Datastore Properties dialog box. 2002. Related concepts “Specifying advanced settings for a subscription” on page 84 “Creating aliases for a target datastore on a private network connection” on page 61 To specify a firewall port for a subscription 1. The default option is Auto-select which will automatically select the network card that can communicate with the target datastore. InfoSphere CDC requires that the source datastore can connect to the target datastore using the firewall port and the next three ports. 2. 4. 3. 4. Click Configuration → Subscriptions.

Identify the subscription from the following: v Subscription—The name of the subscription that uses the selected table. 4. Select a datastore. Expand the source tables tree until you display the tables in the Source Tables area. If you have received authorization from the company or organization to which you are replicating data. 86 InfoSphere Change Data Capture Management Console: Administration Guide . Setting up subscriptions for datastores outside of your organization You can add subscriptions that send data to a target datastore that is external to your organization. owner. or parked. and password. Right-click on a table and select Table Properties. Click Configuration → Datastores. you must create a subscription and associate a source and target datastore. mirrored. the receiving organization must have installed InfoSphere CDC Management Console and you need to find out the necessary authentication and database details to connect to their target datastore. You may have more than one subscription using the same table in replication. Select the Do not replicate data received from any subscriptions box if you want to prevent data from being replicated to the target for all subscriptions. These datastores contain the tables you want to use in replication. v Table Status—Identifies if the selected table has been refreshed. v Replication Method—The replication method for the selected table. System and database information about external target datastores is provided by the organization or department that owns that datastore. See also: “To search for subscriptions that use a table in replication” To search for subscriptions that use a table in replication 1. it becomes important to search for the table and identify which subscriptions are using it replication activities. From the Propagation Control area. Click Advanced Settings. 2.3. v Used As—Identifies whether the table is used as source or target. 6. In order to set up a subscription that sends data to an external target datastore. 5. Related concepts “Specifying advanced settings for a subscription” on page 84 Searching for tables used in replication In order to make tables available for replication. then you can modify the properties of an external target datastore. 4. click Add to select the source ID of the subscription from which you want to prevent data from being replicated to the target. 3. or your system administrator has not given you the permission to access it. Click Search on the Subscriptions tab. When you want to make the table unavailable from replication. including the port number. 5. External target datastores are not available in your Access Manager because they reside outside of your organization or department.

Type the port number for the external target in the Target Port box. therefore. This is a time-saving mechanism. 5. 3. See also: “To add a subscription for an external target datastore” “To modify a subscription for an external target datastore” To add a subscription for an external target datastore 1. Click Configuration → Subscriptions. 7. Click Configuration → Subscriptions. see the appropriate InfoSphere CDC End-User Documentation. Note: This information is provided by the organization or department that owns the external target datastore. Type the password for the database user in the Password box. 8. then you should seeUnknown source datastores in your subscription list. Type the host name or IP address of the external target in the Host Name box. This is because you are receiving replicated data from a source datastore that is outside of your security policy (and. Type the name of the database user that owns the external target metadata in the Owner box. 2. to which you do not have access to) and the name of the source datastore is not known to you. Note: This information is provided by the organization or department that owns the external target datastore. Click Details and make the necessary changes. For more information. Right-click on a subscription and select New Subscription. Select the operating system from the Platform list. 9. 6. Right-click on a subscription with an external target datastore and selectProperties. If your organization is at the receiving end of replication activities co-ordinated with another organization that is outside of your database security policy. 3. InfoSphere CDC creates the metadata tables when you install InfoSphere CDC.You can also copy subscriptions that send data to an external target. 4. Type the name of the metadata database in the Database Name box. Select the type of database for your external target that holds the InfoSphere CDC metadata from the Database Type list. Related concepts “Setting up subscriptions for datastores outside of your organization” on page 86 Related tasks “To modify a subscription for an external target datastore” To modify a subscription for an external target datastore 1. 10. Select <External> from the Target list and click Details. Related concepts “Setting up subscriptions for datastores outside of your organization” on page 86 Setting up and managing subscriptions 87 . 2.

Select an existing project for the subscription from the Project list or click New Project to organize the subscription into a new project. If the existing subscription contains user exits. you may have to change these expressions manually. 8. click Advanced Settings.Related tasks “To add a subscription for an external target datastore” on page 87 Copying subscriptions Copying a subscription is a time-saving mechanism. Related concepts “Copying subscriptions” Related reference “Retrieve column—%SELECT” on page 293 To copy a subscription for an external target datastore 1. If you have a subscription that contains table mappings that you do not want to recreate. 11. If you built a derived column. or a row-filtering expression that uses the %SELECT column function. 12. 14. Select the databases and owners for the new target datastore underNew Name and click Next. 7. Select the databases and/or owners for the new source datastore under New Name and click Next. Right-click on a subscription and select Copy Subscription. an expression. Select the target datastore for the new subscription from theNew Target Datastore list. then specify their location for the new subscription under New Location and click Next. 10. then you can copy the subscription under a new name. Click Configuration → Subscriptions. 6. 13. 5. See also: “To a copy subscription” “To copy a subscription for an external target datastore” To a copy subscription Click Configuration → Subscriptions. Right-click on a subscription and select Copy Subscription. 2. Type a name for the subscription in the Name box. 9. Type the name of the new subscription in the Name box. 4. If you want to specify advanced settings. 3. 1. Select the source datastore for the new subscription from the New Source Datastore list. 3. Click Next. 2. After copying the subscription. then confirm the list of displayed expressions and click Next. Review the list of changes and click Finish. 88 InfoSphere Change Data Capture Management Console: Administration Guide . Type a description for the subscription in the Description box. You can also recreate an existing subscription with the same table mappings if you want to setup a replication scenario within in another environment.

8. In the Time (seconds) box. Related concepts “Copying subscriptions” on page 88 Setting properties for a subscription that targets IBM WebSphere DataStage After creating a subscription that uses InfoSphere CDC for WebSphere DataStage as a target datastore. 12. then make the necessary changes and click Next. The values that you specify are used by InfoSphere CDC to determine when a flat file is complete and is made available to WebSphere DataStage for processing. click Advanced Settings. Click Next. 6. The default value is 600. 7. Review the list of changes and click Finish. See also: “To specify batch size thresholds for a WebSphere DataStage subscription” “To specify large object truncation size for a WebSphere DataStage subscription” on page 90 Related concepts “WebSphere DataStage system parameters” on page 499 “Using InfoSphere CDC with IBM WebSphere DataStage” on page 241 To specify batch size thresholds for a WebSphere DataStage subscription 1. 5. Click OK.4. type the number of rows that can be changed before subscription data is sent to WebSphere DataStage. Click Next. If you want to change the properties of the external target datastore. Setting up and managing subscriptions 89 . 11. Select the new source datastore for the subscription from the New Source Datastore list. 2. If you want to specify advanced settings. In the Number of rows box. Type the description of the new subscription in the Description box. 10. v Large object truncation size for character and binary data. The default value is 100000. 4. 9. Click Configuration → Subscriptions. Right-click on a subscription and select WebSphere DataStage Properties. Select the databases and owners for your new source datastore under New Name. you can modify the following subscription properties: v Batch size thresholds that control how often subscription data is sent to WebSphere DataStage. Select a project for the new subscription from the Project list or click New Project to create a new project. type the amount of time that will elapse before subscription data is sent to WebSphere DataStage. 3. Note: This information is provided by the organization or department that owns the external target datastore. 5.

Right-click on a subscription and select Generate WebSphere DataStage Definition . In the Binary data (# bytes) box. Click Configuration → Subscriptions. Right-click on a subscription and select WebSphere DataStage Properties. see your IBM WebSphere DataStage documentation. 2. 3. you can generate a definition file (*. 90 InfoSphere Change Data Capture Management Console: Administration Guide . You can import this file into IBM WebSphere DataStage Designer and then customize it to meet your business requirements. The default value is 8000. type the truncation point for large binary data. 2. For more information on how to do this.dsx) that creates a job sequence and two utility routines in WebSphere DataStage. type the truncation point for large character data. 5.dsx) and click Save. 4. See also: “To generate a WebSphere DataStage definition file” Related concepts “Using InfoSphere CDC with IBM WebSphere DataStage” on page 241 “Setting properties for a subscription that targets IBM WebSphere DataStage” on page 89 To generate a WebSphere DataStage definition file 1. In the Character data (# characters) box. After generating the DSX file you can import it into WebSphere DataStage Designer.To specify large object truncation size for a WebSphere DataStage subscription 1. Select the location for your DSX file (*. 3. Generating a WebSphere DataStage definition file for a subscription After mapping your tables to WebSphere DataStage. The default value is 8000. Click OK. Click Configuration → Subscriptions.

Under standard replication. v Standard—map tables using standard replication when you want to map only one source table to one target table at a time. A row insert operation on the source table determines a row insert operation on the target table. use the Map Tables wizard to map source and target tables.Mapping tables After defining a subscription in Management Console. InfoSphere CDC applies the same operation that occurred on the source table to the target table. The Map Tables wizard automatically maps tables based on an example mapping you set up. and so on. Subscriptions can contain as many table mappings as necessary. You can map tables one at a time using standard replication. then map your source and target tables using standard replication. See also: “To map similar source tables to similar target tables (One-to-One)” on page 92 “To map a custom source table to a custom target table (standard)” on page 93 “To map multi-member source tables on AS/400 (standard)” on page 95 “To map multi-member source tables to existing target tables on AS/400 (one-to-one)” on page 97 “To map multi-member source tables to new tables on AS/400 (one-to-one)” on page 99 © Copyright IBM Corp. In this section. The number of table mappings you create depends on how many source tables you want InfoSphere CDC to replicate to the target system. v One-to-one—map tables using one-to-one replication when you want to map multiple source tables to multiple target tables at a time and these tables share the same table structure and similar table names. Your source and target tables can be of different types and you can transform the data that you replicate between the source and the target. 2008 91 . Management Console provides two mechanisms for mapping using standard replication. you will learn: “Mapping using standard replication” “Mapping using LiveAudit” on page 100 “Mapping using WebSphere DataStage” on page 106 “Mapping using Adaptive Apply” on page 110 “Mapping to summarize data” on page 113 “Mapping to consolidate data (one-to-one)” on page 117 “Mapping to consolidate data (one-to-many)” on page 121 “Mapping to a datastore outside of your organization” on page 126 “Mapping to a JMS message destination using InfoSphere CDC Event Server” on page 127 Mapping using standard replication If you want your target table to keep an updated image of the data contained in the source table. These are tables that do not share the same table structure or similar table names.

2. 8. select a database user or schema and click Specify Filter. Select a subscription. Specify your filter and click OK. Management Console retrieves the tables from your database that are available for mapping. 1. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Clear the check box for the column you want to hide and click OK. This option is only available if you have selected more than one source table. You can also import any existing filters or choose to export your filter to a text file for future use. select the database user or schema and click Refresh. 92 InfoSphere Change Data Capture Management Console: Administration Guide . The wizard uses the relationship between this target table and the selected source table to map the remaining source and target tables. select a database use or schema and click Specify Filter. Click Next. If you want to modify this filter. Click Next. 7. If you want to map to a new target table. 3. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. select the database user or schema and click Refresh. select a source table and click Filter Columns. If you do not see your table listed. Select one or more tables from the Source Tables list. 4. Management Console retrieves the tables from your database that are available for mapping. 15. 13. then the Filter Tables dialog box automatically displays when you expand a database user or schema.To map similar source tables to similar target tables (One-to-One) Click Configuration → Subscriptions. If you have decided to specify a filter. Enable Map to existing target tables and click Next. select a database user or schema and click Specify Filter. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. 11. 6. Specify your filter and click OK. If this preference is not enabled and you want to manually define a filter. Expand the database user or schema from the Target Tables list. You can click Change Example Table if you want the Map Tables wizard to base the mapping on a different source table. right-click and select Map Tables. v Show filtered tables—displays only the tables that meet the filter criteria you specified. click Create new target tables. 14. 10. 9. Enable One-to-One mapping and click Next. then the Filter Tables dialog box automatically displays when you expand a database user or schema. 12. If you do not see your table listed. 5. If this preference is not enabled and you want to manually define a filter. If you want to hide columns so that the target is not aware of them. Expand the database user or schema from the Source Tables list. Select a table from the Target Tables list.

16. 17. Review the mapping summary and click Finish. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. 19. – Name—lists the name of the journal table. Enable One table mapping of any type. enable the Prevent Recursion check box. 2. If you are using InfoSphere CDC for Microsoft SQL Server 5. This prevents InfoSphere CDC Event Server from replicating changes back to the source database when you have configured a subscription for bidirectional replication. When you select the database owner and provide a name for the journal table.DMCJRN. Mapping tables 93 . v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. Click Next. Select a subscription.3. v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. You must map these manually. right-click and select Map Tables. Contact IBM technical support to implement bidirectional replication in your environment. Verify the mappings in the Complete Mappings page. This is only available in InfoSphere CDC for Microsoft SQL Server 5. 21. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. then enable one of the following: v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>.3 to replicate source database changes and have configured bidirectional replication. If your configuration requires you to prevent recursive updates when mirroring. 18. 20. InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. Click Next. The Map Tables wizard may leave some source tables unmapped if it did not find a target table that shared the same table structure or similar column names. If you are replicating source database changes using InfoSphere CDC for Oracle Trigger-based edition and want to use a journal table to mirror database operations from the source to the target table. then enable the Prevent Recursion check box. Related tasks “To map a custom source table to a custom target table (standard)” “To map multi-member source tables on AS/400 (standard)” on page 95 “To map multi-member source tables to existing target tables on AS/400 (one-to-one)” on page 97 “To map multi-member source tables to new tables on AS/400 (one-to-one)” on page 99 To map a custom source table to a custom target table (standard) 1. 3. – Owner—lists the database owner of the journal table. Click Configuration → Subscriptions. 22.

If you do not see your table listed. Select a table from the Target Tables list. select a database user or schema and click Specify Filter. then the Filter Tables dialog box automatically displays when you expand a database user or schema. 8. Click Next. You can also import any existing filters or choose to export your filter to a text file for future use. select a database use or schema and click Specify Filter. 5. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. If this preference is not enabled and you want to manually define a filter. select the database user or schema and click Refresh. 10. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and 94 InfoSphere Change Data Capture Management Console: Administration Guide . 16. If you want to modify this filter. Choose one of the following and click Next: v Use an Index—select the index name from the Index box. 7. Select one or more tables from the Source Tables list. 13. 11. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. If you want to map to a new target table. Clear the check box for the column you want to hide and click OK. 12. v Use all searchable columns—searches all target columns to identify which columns are suitable to uniquely identify rows. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. select a database user or schema and click Specify Filter. Use if your target table has an index that uniquely identifies a row. 9. If you do not see your table listed. Specify your filter and click OK. If you want to hide columns so that the target is not aware of them. Availability of the above options is dependent on the platform and version of InfoSphere CDC Event Server that you have installed. click Create Table. v Specify the key—select the target columns from the Key Columns list. If this preference is not enabled and you want to manually define a filter. If you have decided to specify a filter. The results of the search are used to build a WHERE clause which uniquely identifies the row on the target column to apply data. Management Console retrieves the tables from your database that are available for mapping. Use if one or more target columns uniquely identifies a row. then the Filter Tables dialog box automatically displays when you expand a database user or schema.4. Expand the database user or schema from the Target Tables list. select the database user or schema and click Refresh. Select Standard from the Mapping type list and clickNext. Management Console retrieves the tables from your database that are available for mapping. 15. select a source table and click Filter Columns. 6. 14. Specify your filter and click OK. Expand the database user or schema from the Source Tables list.

17. select a database use or schema and click Specify Filter. When you select the database owner and provide a name for the journal table. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. Select a subscription. 2. This is only available in InfoSphere CDC for Microsoft SQL Server 5. 6. Contact IBM technical support to implement bidirectional replication in your environment. then enable the Prevent Recursion check box. 19. right-click and select Map Tables. Click Next. Enable One table mapping of any type. This prevents InfoSphere CDC from replicating changes back to the source database when you have configured a subscription for bidirectional replication. 20. 5.3. Management Console retrieves the tables from your database that are available for mapping. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. – Owner—lists the database owner of the journal table. 4. 21.replicate at a later time. 1. then the Filter Tables dialog box automatically displays when you expand a database user or schema. If your configuration requires you to prevent recursive updates when mirroring. Related concepts “Mapping using standard replication” on page 91 “Setting member identifiers for multi-member source tables” on page 187 To map multi-member source tables on AS/400 (standard) Click Configuration → Subscriptions. then enable one of the following: v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>. If this preference is not enabled and you want to manually define a filter. If you are using InfoSphere CDC for Microsoft SQL Server 5. Select Standard from the Mapping type list and clickNext. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. enable the Prevent Recursion check box. Review the mapping summary. 18. – Name—lists the name of the journal table.3 to replicate source database changes and have configured bidirectional replication. If you are replicating source database changes using InfoSphere CDC for Oracle Trigger-based edition and want to use a journal table to mirror database operations from the source to the target table.DMCJRN. InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. Expand the database user or schema from the Source Tables list. v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. 3. Mapping tables 95 .

v Use Source member Structure on Target—maintains the same multi-member structure on the target table as the one on the source table. If this preference is not enabled and you want to manually define a filter. Availability of the above options is dependent on the platform and version of InfoSphere CDC Event Server that you have installed. Expand the database user or schema from the Target Tables list. If you want to hide columns so that the target is not aware of them. 8. 10. 13. select the database user or schema and click Refresh. select a database user or schema and click Specify Filter. Each source member is mapped to the corresponding target member. Specify your filter and click OK. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. select a database user or schema and click Specify Filter. v Merge Source Members into One Target Member—merges all members from the source table to a single member in a multi-member. v Specify the key—select the target columns from the Key Columns list. Specify your filter and click OK. 12. Use if your target table has an index that uniquely identifies a row. select a source table and click Filter Columns. 15. 16. v Show filtered tables—displays only the tables that meet the filter criteria you specified. If you have decided to specify a filter. 9. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring. Select one or more tables from the Source Tables list. Click Next. select the database user or schema and click Refresh. 96 InfoSphere Change Data Capture Management Console: Administration Guide . If you do not see your table listed. Clear the check box for the column you want to hide and click OK. 11. If you want to modify this filter. You can also import any existing filters or choose to export your filter to a text file for future use.7. Use if one or more target columns uniquely identifies a row. Management Console retrieves the tables from your database that are available for mapping. The results of the search are used to build a WHERE clause which uniquely identifies the row on the target column to apply data. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. If you do not see your table listed. 14. v Use all searchable columns—searches all target columns to identify which columns are suitable to uniquely identify rows. Choose one of the following options and click Next: v Source and Target Files are Single Member—merges all members from the source table to a single-member target table. then the Filter Tables dialog box automatically displays when you expand a database user or schema. Choose one of the following and click Next: v Use an Index—select the index name from the Index box. Select a table from the Target Tables list. enable the Prevent Recursion check box.

– If no Relative Record Number is available on the target table (for example. 17. 1. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. Select a subscription. When this option is checked. InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. Mapping tables 97 . Enable One-to-one Mappings and click Next. 6. Expand the database user or schema from the Source Tables list. if the source table is reorganized. – This option is only available when using a InfoSphere CDC for AS/400 source. Related concepts “Mapping using standard replication” on page 91 “Setting member identifiers for multi-member source tables” on page 187 To map multi-member source tables to existing target tables on AS/400 (one-to-one) Click Configuration → Subscriptions. see “Source RRN (&CNTRRN)” on page 246. Review the mapping summary. Notes: – When this option is checked.v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. Click Next. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. 19. If you have decided to specify a filter. 5. Management Console retrieves the tables from your database that are available for mapping. 18. If you do not check this box. then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. 3. 4. 2. For more information. If this preference is not enabled and you want to manually define a filter. you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. if the table resides on a non-AS/400 system). select a database use or schema and click Specify Filter. Attention: AS/400 must be installed on both source and target. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). then the Filter Tables dialog box automatically displays when you expand a database user or schema. right-click and select Map Tables. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. InfoSphere CDC will automatically start a refresh for that table. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view.

then the Filter Tables dialog box automatically displays when you expand a database user or schema. 8. you can click the assigned target table and pick another target table from the displayed list. you can still make 98 InfoSphere Change Data Capture Management Console: Administration Guide . 15. 14. 9. select a database user or schema and click Specify Filter. Expand the database user or schema from the Target Tables list. When this option is checked. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). InfoSphere CDC will automatically start a refresh for that table. This option is only available if you have selected more than one source table. If you want to hide columns so that the target is not aware of them. select the database user or schema and click Refresh. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. Enable Map to existing target tables and clickNext. Clear the check box for the column you want to hide and click OK. v Show filtered tables—displays only the tables that meet the filter criteria you specified. The wizard uses the relationship between this target table and the selected source table to map the remaining source and target tables. If this preference is not enabled and you want to manually define a filter. 13. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. 10. If any of the mappings are incorrect. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. if the source table is reorganized. if the table resides on a non-AS/400 system). – If no Relative Record Number is available on the target table (for example. enable the Prevent Recursion check box. Specify your filter and click OK. select a database user or schema and click Specify Filter.7. If you want to modify this filter. If you do not see your table listed. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. If you do not check this box. then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. Notes: – When this option is checked. 12. Select the target table from the Target Table list and clickNext. select a source table and click Filter Columns. InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. Click Next. Select one or more tables from the Source Tables list. If you have not chosen similar tables. You can also import any existing filters or choose to export your filter to a text file for future use. If your configuration requires you to prevent recursive updates when mirroring. You can click Change Example Table if you want the Map Tables wizard to base the mapping on a different source table. 11. you can select target tables individually by clicking on the target list beside the source table you want to map. Specify your filter and click OK. Management Console retrieves the tables from your database that are available for mapping.

If you have decided to specify a filter. Select one or more tables from the Source Tables list. 2. You can also import any existing filters or choose to export your filter to a text file for future use. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Expand the database user or schema from the Source Tables list. Specify your filter and click OK. 7. Click Click to select a target owner under Target Library and select a target owner. Clear the check box for the column you want to hide and click OK. 4. v Show filtered tables—displays only the tables that meet the filter criteria you specified. select a database use or schema and click Specify Filter. Choose from the following options and click Next: v Identical to the source table names—Names the new target tables the same name as the source tables. Review the mapping summary. 9. 8. select the database user or schema and click Refresh. Review the mapping summary and click Finish. Mapping tables 99 . 12. right-click and select Map Tables. then the Filter Tables dialog box automatically displays when you expand a database user or schema. Enable Create New Target Tables and click Next. For more information. 16. If you want to modify this filter. – This option is only available when using a InfoSphere CDC for AS/400 source. select a database user or schema and click Specify Filter. 17. Enable One-to-one Mappings and click Next. If you want to hide columns so that the target is not aware of them. 10. 11. 3. Click Next. Select a subscription. If you do not see your table listed. 13. If this preference is not enabled and you want to manually define a filter. 18. Related concepts “Mapping using standard replication” on page 91 “Setting member identifiers for multi-member source tables” on page 187 To map multi-member source tables to new tables on AS/400 (one-to-one) 1. 6. Click Next. select a source table and click Filter Columns.use of this option by mapping the Relative Record Number on the source table to a column in the target table to. see “Source RRN (&CNTRRN)” on page 246. 5. Click Configuration → Subscriptions. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping.

v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. The following table summarizes how row-level operations are replicated to the target datastore when you map your tables for LiveAudit. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). For more information. Related concepts “Mapping using standard replication” on page 91 “Setting member identifiers for multi-member source tables” on page 187 Mapping using LiveAudit If you want your target table to keep an audit trail of operations applied to the source table. and clear (truncate) operations applied to the mapped source table.v Source table names with prefixes and/or suffixes—Adds the suffix and/or prefix to the source table name. you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. LiveAudit is most useful if your environment must satisfy data auditing and change-tracking requirements. update. 14. InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. To replicate data using LiveAudit. InfoSphere CDC will automatically start a refresh for that table. then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. – This option is only available when using a InfoSphere CDC for AS/400 source. With LiveAudit. you can audit changes to sensitive information. If your configuration requires you to prevent recursive updates when mirroring. If you do not check this box. 100 InfoSphere Change Data Capture Management Console: Administration Guide . your target tables contain rows that track insert. 15. then use the Map Tables wizard to map your source and target tables using LiveAudit. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. – If no Relative Record Number is available on the target table (for example. Review the mapping summary and click Finish. Notes: – When this option is checked. When this option is checked. if the table resides on a non-AS/400 system). if the source table is reorganized. Enable the Use Prefix/Suffix for index name to use the prefix/suffix as the index name. you must have a LiveAudit-enabled authorization code. see “Source RRN (&CNTRRN)” on page 246. Source operations INSERT Target Operations INSERTs the new row that was added. When you replicate data using LiveAudit. delete. and you can monitor and report on risk in a timely manner. enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table.

UPDATE (Key changed) Either: v INSERT the row that contains the after image. then the Filter Tables dialog box automatically displays when you expand a database user or schema. and INSERT another row containing after image values. See also: “To map “To map “To map “To map a single source table using LiveAudit” a multi-member table using LiveAudit for AS/400” on page 102 multiple source tables to existing tables using LiveAudit” on page 104 multiple source tables to new tables using LiveAudit” on page 105 To map a single source table using LiveAudit 1. You can choose to add. or delete audit columns to the target table. If you have decided to specify a filter. Review the following audit columns.Source operations UPDATE (Key not changed) Target Operations Either: v INSERT the row that contains the after image. v Show filtered tables—displays only the tables that meet the filter criteria you specified. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. select a database use or schema and click Specify Filter. right-click and select Map Tables. 4. v INSERT row containing before image values. Expand the database user or schema from the Source Tables list. DELETE INSERTs the row that was deleted. 2. v AudUser—stores the &USER journal control field which indicates the ID of the user who made the change to the source. If this preference is not enabled and you want to manually define a filter. 5. v AudType—stores the &ENTTYP journal control field which indicates the type of change made to the source. Select a subscription. 3. Click Next: v AudTime—stores the &TIMSTAMP journal control field which indicates date and time changes are made to the source. modify. v INSERT row containing before image values. Click Next. Click Configuration → Subscriptions. Mapping tables 101 . 7. 6. and INSERT another row containing after image values. Enable One table mapping of any type and select LiveAudit from the Mapping Type list box. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences.

17. v AudUser—stores the &USER journal control field which indicates the ID of the user who made the change to the source. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Related concepts “Mapping using LiveAudit” on page 100 To map a multi-member table using LiveAudit for AS/400 1. 12. If you want to modify this filter. 6. Management Console retrieves the tables from your database that are available for mapping. modify. If this preference is not enabled and you want to manually define a filter. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Select LiveAudit from the Mapping Type list box and clickNext. Expand the database user or schema from the Source Tables list. 15. v AudType—stores the &ENTTYP journal control field which indicates the type of change made to the source. 5. right-click and select Map Tables. 2. Select a table from the Target Tables list. Review the following audit columns. Select one or more tables from the Source Tables list. If you do not see your table listed. 9. select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK. You can also import any existing filters or choose to export your filter to a text file for future use. 10. 14. 13. Review the mapping summary. If you want to hide columns so that the target is not aware of them. Click Next: v AudTime—stores the &TIMSTAMP journal control field which indicates date and time changes are made to the source. Management Console retrieves the tables from your database that are available for mapping. Expand the database user or schema from the Target Tables list. Click Configuration → Subscriptions. then the Filter Tables dialog box automatically displays when you expand a database user or schema. If you do not see your table listed. then the Filter Tables dialog box automatically 102 InfoSphere Change Data Capture Management Console: Administration Guide . select the database user or schema and click Refresh. 4. 7. select a database user or schema and click Specify Filter. 16. 3. You can choose to add. Click Next. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. select a database user or schema and click Specify Filter.8. Select a subscription. or delete audit columns to the target table. 11. Click Next. Specify your filter and click OK. select the database user or schema and click Refresh. Specify your filter and click OK. Enable One table mapping of any type.

You can also import any existing filters or choose to export your filter to a text file for future use. select a source table and click Filter Columns. 10. 15. 16. 13. Specify your filter and click OK. Select a target table from the Target Tables list and choose one of the following options. select a database user or schema and click Specify Filter. v Use Source member Structure on Target—Maintains the same multi-member structure on the target table as the one on the source table. If this preference is not enabled and you want to manually define a filter. then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter. Click Next. v Source and Target Files are Single Member—Merges all members from the source table to a single-member target table. v Merge Source Members into One Target Member—Merges all members from the source table to a single member in a multi-member. 11. Related concepts “Mapping using standard replication” on page 91 “Setting member identifiers for multi-member source tables” on page 187 Mapping tables 103 . Clear the check box for the column you want to hide and click OK. Specify your filter and click OK. select the database user or schema and click Refresh. 17. 14. Each source member is mapped to the corresponding target member. Expand the database user or schema from the Target Tables list. If you want to hide columns so that the target is not aware of them. v Show filtered tables—displays only the tables that meet the filter criteria you specified. select a database use or schema and click Specify Filter. Select one or more tables from the Source Tables list. displays when you expand a database user or schema. 9. 12. If you have decided to specify a filter. select a database user or schema and click Specify Filter. Attention: AS/400 must be installed on both source and target.8. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. If you do not see your table listed. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Review the mapping settings. Management Console retrieves the tables from your database that are available for mapping. If you want to modify this filter. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences.

You can choose to add. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. right-click and select Map Tables. Verify that the correct target table is mapped to the source tables and click Next. select a source table and click Filter Columns. Enable Map to existing target tables and click Next. 13. Select one or more tables from the Source Tables list. Enable LiveAudit Mappings and clickNext. 5. Click Next. Clear the check box for the column you want to hide and click OK. 2. select a database user or schema and click Specify Filter. 3. select the database user or schema and click Refresh. modify. Specify your filter and click OK. Review the following audit columns. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. select a database user or schema and click Specify Filter. 104 InfoSphere Change Data Capture Management Console: Administration Guide . 11. If you want to hide columns so that the target is not aware of them. 8. If this preference is not enabled and you want to manually define a filter. v AudType—stores the &ENTTYP journal control field which indicates the type of change made to the source. Click Configuration → Subscriptions. 16. Select a subscription. 6. or delete audit columns to the target table. 14. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Click Next: v AudTime—stores the &TIMSTAMP journal control field which indicates date and time changes are made to the source. then the Filter Tables dialog box automatically displays when you expand a database user or schema. If you have decided to specify a filter. If you do not see your table listed. select a database use or schema and click Specify Filter. Expand the database user or schema from the Source Tables list. If you do not see your table listed. 10. Specify your filter and click OK. 15. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Management Console retrieves the tables from your database that are available for mapping. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. 9. 4. then the Filter Tables dialog box automatically displays when you expand a database user or schema. select the database user or schema and click Refresh.To map multiple source tables to existing tables using LiveAudit 1. 7. v AudUser—stores the &USER journal control field which indicates the ID of the user who made the change to the source. Select a table from the Target Tables list and click Next. 12. If this preference is not enabled and you want to manually define a filter. If you want to modify this filter.

v AudUser—stores the &USER journal control field which indicates the ID of the user who made the change to the source. Click Configuration → Subscriptions. or delete) applied to a row in the source table. The target table can become extremely large. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Mapping tables 105 . 8. If you want to hide columns so that the target is not aware of them. 10. select the database user or schema and click Refresh. select a source table and click Filter Columns. Select one or more tables from the Source Tables list. Review the mapping summary and click Finish. Management Console retrieves the tables from your database that are available for mapping. Enable Create New Target Tables and click Next. You can also import any existing filters or choose to export your filter to a text file for future use. Click Next: v AudTime—stores the &TIMSTAMP journal control field which indicates date and time changes are made to the source. Ensure that you allow sufficient disk space and perform regular maintenance for target tables that audit data. Click Next. Clear the check box for the column you want to hide and click OK. 5. Specify your filter and click OK. then the Filter Tables dialog box automatically displays when you expand a database user or schema. 6. modify. 12. 2. Expand the database user or schema from the Source Tables list. If you do not see your table listed. Select LiveAudit and clickNext. You can choose to add. Related concepts “Mapping using LiveAudit” on page 100 To map multiple source tables to new tables using LiveAudit 1. Review the following audit columns. 9. v Show filtered tables—displays only the tables that meet the filter criteria you specified. 17. you can click the assigned target table and pick another target table from the displayed list. InfoSphere CDC inserts a row into the target table for every row-level operation (insert. you can select target tables individually by clicking on the target list beside the source table you want to map. select a database use or schema and click Specify Filter. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping.If any of the mappings are incorrect. If you have decided to specify a filter. If you have not chosen similar tables. 11. right-click and select Map Tables. or delete audit columns to the target table. 4. If this preference is not enabled and you want to manually define a filter. 3. 7. select a database user or schema and click Specify Filter. update. v AudType—stores the &ENTTYP journal control field which indicates the type of change made to the source. If you want to modify this filter. Select a subscription.

Expand the database user or schema from the Source Tables list. right-click and select Map Tables. 5.13. select a database use or schema and click Specify Filter. 2. 14. v Source table names with prefixes and/or suffixes—Adds the suffix and/or prefix to the source table name. Choose from the following options and click Next: v Identical to the source table names—Names the new target tables the same name as the source tables. You can create as many table mappings as you feel necessary. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Select a subscription. Enable Flat File and click Next. 106 InfoSphere Change Data Capture Management Console: Administration Guide . If you have decided to specify a filter. IBM WebSphere DataStage. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. See also: “To map a single source table to WebSphere DataStage using flat files” “To map a single source table to WebSphere DataStage using Direct Connect” on page 107 “To map multiple source tables to WebSphere DataStage using flat files” on page 108 “To map multiple source tables to WebSphere DataStage using Direct Connect” on page 109 To map a single source table to WebSphere DataStage using flat files 1. Related concepts “Mapping using LiveAudit” on page 100 Mapping using WebSphere DataStage After adding a subscription that uses InfoSphere CDC for WebSphere DataStage as a target datastore. and this may depend on the number of tables that you want to replicate to the target system. 7. Click Configuration → Subscriptions. 4. Management Console retrieves the tables from your database that are available for mapping. 15. then the Filter Tables dialog box automatically displays when you expand a database user or schema. Click Click to select a target owner under Target Library and select a target owner. Review the mapping summary and click Finish. you must map one or more source tables to the target system. Enable One table mapping and select WebSphere DataStage from the Mapping Type box. 6. Enable the Use Prefix/Suffix for index name to use the prefix/suffix as the index name. Click Next. If this preference is not enabled and you want to manually define a filter. 3. v Show filtered tables—displays only the tables that meet the filter criteria you specified.

select a database user or schema and click Specify Filter. Expand the database user or schema from the Source Tables list. 3. You can also import any existing filters or choose to export your filter to a text file for future use. Enable one of the following options for the record format of the flat files and click Next: v Single Record—an update operation is sent as a single row. type the output directory for the WebSphere DataStage flat files that are generated by InfoSphere CDC and utilized by WebSphere DataStage. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Specify your filter and click OK. Enable Direct Connect and click Next. If you want to hide columns so that the target is not aware of them. 8. select a source table and click Filter Columns. Enable One table mapping and select WebSphere DataStage from the Mapping Type box. If this preference is not enabled and you want to manually define a filter.8. 13. Management Console retrieves the tables from your database that are available for mapping. To map a single source table to WebSphere DataStage using Direct Connect 1. select a database use or schema and click Specify Filter. v Show filtered tables—displays only the tables that meet the filter criteria you specified. 10. If you have decided to specify a filter. 15. Click Next. 6. 7. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. select the database user or schema and click Refresh. 9. 11. Specify your filter and click OK. If you want to modify this filter. 2. Mapping tables 107 . 14. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. right-click and select Map Tables. Select one or more tables from the Source Tables list. In the Directory box. You can also import any existing filters or choose to export your filter to a text file for future use. then the Filter Tables dialog box automatically displays when you expand a database user or schema. v Multiple Record—an update operation is sent as two rows. Clear the check box for the column you want to hide and click OK. Select a subscription. Click Next. If you want to modify this filter. If you do not see your table listed. Click Configuration → Subscriptions. select a database user or schema and click Specify Filter. 5. 4. 12. Review the mapping settings.

Click Next. 6. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Select one or more tables from the Source Tables list.9. 12. type port number for the WebSphere DataStage host. 10. 14. To map multiple source tables to WebSphere DataStage using flat files 1. 8. v Multiple Record—an update operation is sent as two rows. select the database user or schema and click Refresh. You can also import any existing filters or choose to export your filter to a text file for future use. 10. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Expand the database user or schema from the Source Tables list. Review the mapping settings. If this preference is not enabled and you want to manually define a filter. In the Port box. Enable one of the following options for the output records used by WebSphere DataStage and click Next: v Single Record—an update operation is sent as a single row. Select a subscription. Click Next. 2. 11. 9. 11. 15. Enable Flat File and click Next. Under Automatic. enable WebSphere DataStage. 5. Click Next. If you have decided to specify a filter. select the database user or schema and click Refresh. select a source table and click Filter Columns. If you want to hide columns so that the target is not aware of them. If you do not see your table listed. select a database user or schema and click Specify Filter. right-click and select Map Tables. select a database use or schema and click Specify Filter. Click Configuration → Subscriptions. Clear the check box for the column you want to hide and click OK. select a source table and click Filter Columns. If you want to hide columns so that the target is not aware of them. 7. Select one or more tables from the Source Tables list. 108 InfoSphere Change Data Capture Management Console: Administration Guide . v Show filtered tables—displays only the tables that meet the filter criteria you specified. Clear the check box for the column you want to hide and click OK. 13. In the Host box. type the host name of your WebSphere DataStage installation. 4. If you want to modify this filter. 16. If you do not see your table listed. Specify your filter and click OK. then the Filter Tables dialog box automatically displays when you expand a database user or schema. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. 3.

If you have decided to specify a filter. Review the mapping settings and click Finish. 7. In thePort box. specify the starting port if you have selected more than one source table. 14. Management Console retrieves the tables from your database that are available for mapping. To map multiple source tables to WebSphere DataStage using Direct Connect 1. select the database user or schema and click Refresh. 14. 13. If you do not see your table listed. right-click and select Map Tables. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Clear the check box for the column you want to hide and click OK. Review the mapping settings and click Finish. 12. If you want to hide columns so that the target is not aware of them. 10. In theHost box. Click Next. Select one or more tables from the Source Tables list. 8. select a database user or schema and click Specify Filter. 6. EnableDirect Connect and click Next. Mapping tables 109 . type the host name of your WebSphere DataStage installation. type the output directory for the WebSphere DataStage flat files that are generated by InfoSphere CDC Event Server and utilized by WebSphere DataStage. In the Directory box. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Enable one of the following options for the flat file output records and click Next: v Single Record—an update operation is sent as a single row. 11. then the Filter Tables dialog box automatically displays when you expand a database user or schema. Specify your filter and click OK. If you want to modify this filter. Click Next. EnableOne table mapping and select WebSphere DataStage from theMapping Type box. v Multiple Record—an update operation is sent as two rows. Expand the database user or schema from the Source Tables list. 5. select a database use or schema and click Specify Filter. Select a subscription. Click Configuration → Subscriptions.12. 3. 4. select a source table and click Filter Columns. Enable one of the following options for the output records used by WebSphere DataStage and click Next: v Single Record—an update operation is sent as a single row. 9. You can also import any existing filters or choose to export your filter to a text file for future use. v Show filtered tables—displays only the tables that meet the filter criteria you specified. If this preference is not enabled and you want to manually define a filter. 13. v Multiple Record—an update operation is sent as two rows. 15. 2.

and then use adaptive apply to populate an empty target table with the latest data. Expand the database user or schema from the Source Tables list. You can also use adaptive apply to restore the contents of a target table from recorded journal or log entries. Enable One table mapping of any type. 110 InfoSphere Change Data Capture Management Console: Administration Guide . you set the journal or log position to a specific entry or point in time. Select a subscription. You can also import any existing filters or choose to export your filter to a text file for future use. and this row does not exist on your target table. but that row already exists in your target table. select a database use or schema and click Specify Filter. InfoSphere CDC switches the insert to an update operation. select a source table and click Filter Columns. 6.Mapping using Adaptive Apply If you know that your source and target tables are not synchronized. if there is an insert on the source table. 4. If you want to hide columns so that the target is not aware of them. 7. Management Console retrieves the tables from your database that are available for mapping. If this preference is not enabled and you want to manually define a filter. 8. 10. Specify your filter and click OK. 2. select the database user or schema and click Refresh. v Show filtered tables—displays only the tables that meet the filter criteria you specified. For example. Click Next. 11. Click Configuration → Subscriptions. 9. Select one or more tables from the Source Tables list. If you want to modify this filter. To do this. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Adaptive Apply ensures that replicated rows in the source and target tables are the same. right-click and select Map Tables. See also: “To map a source table using Adaptive Apply” “To map multi-member source tables using Adaptive Apply on AS/400” on page 112 To map a source table using Adaptive Apply 1. 5. if there is an update on your source table. If you do not see your table listed. Also. Select Adaptive Apply from the Mapping type list and click Next. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Clear the check box for the column you want to hide and click OK. then InfoSphere CDC switches the update into an insert. select a database user or schema and click Specify Filter. then map your source table to your target table using the Adaptive Apply mapping type. If you have decided to specify a filter. 3. then the Filter Tables dialog box automatically displays when you expand a database user or schema. but you want to replicate data from the source to the target without error.

12. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. 13. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database user or schema and click Specify Filter. Specify your filter and click OK. 14. Select a table from the Target Tables list and click Next. If you do not see your table listed, select the database user or schema and click Refresh. Click Next. If you want to create a new table to map to, click Create Table. 15. Choose one of the following and click Next: v Use an Index—select the index name from the Index box. Use if your target table has an index that uniquely identifies a row. Specify the key—select the target columns from the Key Columns list. Use if one or more target columns uniquely identifies a row. v Use all searchable columns—searches all target columns to identify which columns are suitable to uniquely identify rows. The results of the search are used to build a WHERE clause which uniquely identifies the row on the target column to apply data. v Availability of the above options is dependent on the platform and version of InfoSphere CDC Event Server that you have installed. 16. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. 17. If you are replicating source database changes using InfoSphere CDC for Oracle Trigger-based edition and want to use a journal table to mirror database operations from the source to the target table, then enable one of the following: v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>.DMCJRN. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. When you select the database owner and provide a name for the journal table, InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. – Owner—lists the database owner of the journal table. – Name—lists the name of the journal table. 18. If you are using InfoSphere CDC for Microsoft SQL Server 5.3 to replicate source database changes and have configured bidirectional replication, then enable the Prevent Recursion check box. This prevents InfoSphere CDC from replicating changes back to the source database when you have configured a subscription for bidirectional replication. This is only available in InfoSphere CDC for Microsoft SQL Server 5.3. Contact IBM Technical Support to implement bidirectional replication in your environment.
Mapping tables

111

19. Click Next. 20. Review the mapping summary. 21. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Related concepts “Mapping using Adaptive Apply” on page 110

To map multi-member source tables using Adaptive Apply on AS/400
1. Click Configuration → Subscriptions. 2. Select a subscription, right-click and select Map Tables. 3. Select Adaptive Apply from the Mapping type list and click Next. 4. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database use or schema and click Specify Filter. 5. If you have decided to specify a filter, choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. Specify your filter and click OK. 6. If you want to modify this filter, select a database user or schema and click Specify Filter. 7. Select one or more tables from the Source Tables list. If you do not see your table listed, select the database user or schema and click Refresh. 8. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK. 9. Click Next. 10. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. 11. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database user or schema and click Specify Filter. Specify your filter and click OK. 12. Select a table from the Target Tables list and click Next. If you do not see your table listed, select the database user or schema and click Refresh. Click Next. If you want to create a new table to map to, click Create Table. 13. Choose one of the following and click Next: v Use an Index—select the index name from the Index box. Use if your target table has an index that uniquely identifies a row.

112

InfoSphere Change Data Capture Management Console: Administration Guide

Specify the key—select the target columns from the Key Columns list. Use if one or more target columns uniquely identifies a row. v Use all searchable columns—searches all target columns to identify which columns are suitable to uniquely identify rows. The results of the search are used to build a WHERE clause which uniquely identifies the row on the target column to apply data. Availability of the above options is dependent on the platform and version of InfoSphere CDC Event Server that you have installed. v 14. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. When this option is checked, InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). If you do not check this box, then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. Notes: – When this option is checked, if the source table is reorganized, InfoSphere CDC will automatically start a refresh for that table. – If no Relative Record Number is available on the target table (for example, if the table resides on a non-AS/400 system), you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. For more information, see “Source RRN (&CNTRRN)” on page 246. – This option is only available when using a InfoSphere CDC for AS/400 source. 15. Review the mapping settings. 16. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Related concepts “Mapping using Adaptive Apply” on page 110

Mapping to summarize data
If you want to accumulate or deduct numerical values on the target, then map your source and target tables using the Summarization mapping type. There are two types of summarization: Accumulation and Deduction. Accumulation ensures that numeric changes applied to the target column are directly proportional to changes applied to the corresponding source columns. Deduction ensures that numeric changes applied to the target columns are inversely proportional to changes applied to mapped source columns.

Mapping tables

113

See also: “To map a source table to summarize data” “To map multi-member source tables using Summarization on AS/400” on page 115

To map a source table to summarize data
1. 2. 3. 4. Click Configuration → Subscriptions. Select a subscription, right-click and select Map Tables. Select Summarization from the Mapping type list. Expand the database user or schema from the Source Tables list. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database use or schema and click Specify Filter. If you have decided to specify a filter, choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. Specify your filter and click OK. If you want to modify this filter, select a database user or schema and click Specify Filter. Select one or more tables from the Source Tables list. If you do not see your table listed, select the database user or schema and click Refresh. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK. Click Next.

5.

6.

7. 8. 9.

10.

11. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. 12. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database user or schema and click Specify Filter. Specify your filter and click OK. 13. Select a table from the Target Tables list and click Next. If you do not see your table listed, select the database user or schema and click Refresh. Click Next. If you want to create a new table to map to, click Create Table. 14. Select the target columns from the Key Columns list and click Next. 15. Choose one of the following from the Summarization Type list: v Accumulation—Numeric changes applied to target columns are directly proportional to changes applied to source columns. v Deduction—Numeric changes applied to target columns are inversely proportional to changes applied to source columns.

114

InfoSphere Change Data Capture Management Console: Administration Guide

16. Select the source column from the Summarized Column list and click Next. 17. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. 18. If you are replicating source database changes using InfoSphere CDC for Oracle Trigger-based edition and want to use a journal table to mirror database operations from the source to the target table, then enable one of the following: v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>.DMCJRN. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. When you select the database owner and provide a name for the journal table, InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. – Owner—lists the database owner of the journal table. – Name—lists the name of the journal table. 19. If you are using InfoSphere CDC for Microsoft SQL Server 5.3 to replicate source database changes and have configured bidirectional replication, then enable the Prevent Recursion check box. This prevents InfoSphere CDC from replicating changes back to the source database when you have configured a subscription for bidirectional replication. This is only available in InfoSphere CDC for Microsoft SQL Server 5.3. Contact IBM Technical Support to implement bidirectional replication in your environment. 20. Click Next. 21. Review the mapping settings. 22. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Related concepts “Mapping to summarize data” on page 113

To map multi-member source tables using Summarization on AS/400
1. Click Configuration → Subscriptions. 2. Select a subscription, right-click and select Map Tables. 3. Select Summarization from the Mapping type list. 4. Expand the database user or schema from the Source Tables list. Management Console retrieves the tables from your database that are available for mapping. 5. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically
Mapping tables

115

6.

7. 8. 9.

10. 11.

12.

13.

14.

15.

16. 17.

displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database use or schema and click Specify Filter. If you have decided to specify a filter, choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. Specify your filter and click OK. If you want to modify this filter, select a database user or schema and click Specify Filter. Select one or more tables from the Source Tables list. If you do not see your table listed, select the database user or schema and click Refresh. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK. Click Next. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database user or schema and click Specify Filter. Specify your filter and click OK. Select a table from the Target Tables list and click Next. If you do not see your table listed, select the database user or schema and click Refresh. Click Next. If you want to create a new table to map to, click Create Table. Select the target columns from the Key Columns list and click Next. InfoSphere CDC for AS/400 requires that the selected key columns match an existing index. Choose one of the following from the Summarization Type list: v Accumulation—Numeric changes applied to target columns are directly proportional to changes applied to source columns. v Deduction—Numeric changes applied to target columns are inversely proportional to changes applied to source columns. Select the source column from the Summarized Column list and click Next. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. When this option is checked, InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on

116

InfoSphere Change Data Capture Management Console: Administration Guide

the target side. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). If you do not check this box, then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. Notes: – When this option is checked, if the source table is reorganized, InfoSphere CDC will automatically start a refresh for that table. – If no Relative Record Number is available on the target table (for example, if the table resides on a non-AS/400 system), you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. For more information, see “Source RRN (&CNTRRN)” on page 246. – This option is only available when using a InfoSphere CDC for AS/400 source. 18. Review the mapping settings. 19. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Related concepts “Mapping to summarize data” on page 113

Mapping to consolidate data (one-to-one)
If your business environment contains information that is scattered across different source tables, you may want to consolidate it to facilitate report generation, data management, or data security. To merge different information about a common entity into a single row, such as a person, a customer, or a product part, map your source table to your target table using the Consolidation one-to-one mapping type. See also: “To map a source table to consolidate data (one-to-one)” “To map multi-member source tables using Consolidation One-to-One on AS/400” on page 119 Related concepts “Mapping using standard replication” on page 91 “Adding and mapping derived columns to target columns” on page 162 Related tasks “To map a source table to consolidate data (one-to-many)” on page 122 “To map multi-member source tables using Consolidation one-to-many on AS/400” on page 124 Related reference “Retrieve column—%GETCOL (Dynamic SQL)” on page 288

To map a source table to consolidate data (one-to-one)
1. Click Configuration → Subscriptions. 2. Select a subscription, right-click and select Map Tables. 3. Select Consolidation One-to-one from the Mapping type list.

Mapping tables

117

4. Expand the database user or schema from the Source Tables list. Management Console retrieves the tables from your database that are available for mapping. 5. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database use or schema and click Specify Filter. 6. If you have decided to specify a filter, choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. Specify your filter and click OK. 7. If you want to modify this filter, select a database user or schema and click Specify Filter. 8. Select one or more tables from the Source Tables list. If you do not see your table listed, select the database user or schema and click Refresh. 9. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK. 10. Click Next. 11. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. 12. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database user or schema and click Specify Filter. Specify your filter and click OK. 13. Select a table from the Target Tables list and click Next. If you do not see your table listed, select the database user or schema and click Refresh. Click Next. If you want to create a new table to map to, click Create Table. 14. Check the key for the target columns and click Next. 15. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. 16. If you are replicating source database changes using InfoSphere CDC for Oracle Trigger-based edition and want to use a journal table to mirror database operations from the source to the target table, then enable one of the following: v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>.DMCJRN. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target.

118

InfoSphere Change Data Capture Management Console: Administration Guide

v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. When you select the database owner and provide a name for the journal table, InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. – Owner—lists the database owner of the journal table. – Name—lists the name of the journal table. 17. If you are using InfoSphere CDC for Microsoft SQL Server 5.3 to replicate source database changes and have configured bidirectional replication, then enable the Prevent Recursion check box. This prevents InfoSphere CDC from replicating changes back to the source database when you have configured a subscription for bidirectional replication. This is only available in InfoSphere CDC for Microsoft SQL Server 5.3. Contact IBM Technical Support to implement bidirectional replication in your environment. 18. Click Next. 19. Review the mapping settings. 20. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Related concepts “Mapping to consolidate data (one-to-one)” on page 117

To map multi-member source tables using Consolidation One-to-One on AS/400
1. Click Configuration → Subscriptions. 2. Select a subscription, right-click and select Map Tables. 3. Select Consolidation One-to-one from the Mapping type list. 4. Expand the database user or schema from the Source Tables list. Management Console retrieves the tables from your database that are available for mapping. 5. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database use or schema and click Specify Filter. 6. If you have decided to specify a filter, choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. Specify your filter and click OK. 7. If you want to modify this filter, select a database user or schema and click Specify Filter. 8. Select one or more tables from the Source Tables list. If you do not see your table listed, select the database user or schema and click Refresh.

Mapping tables

119

9. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK. 10. Click Next. 11. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. 12. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database user or schema and click Specify Filter. Specify your filter and click OK. 13. Select a table from the Target Tables list and click Next. If you do not see your table listed, select the database user or schema and click Refresh. Click Next. If you want to create a new table to map to, click Create Table. 14. Check the key for the target columns and click Next. 15. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. When this option is checked, InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). If you do not check this box, then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. Notes: – When this option is checked, if the source table is reorganized, InfoSphere CDC will automatically start a refresh for that table. – If no Relative Record Number is available on the target table (for example, if the table resides on a non-AS/400 system), you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. For more information, see “Source RRN (&CNTRRN)” on page 246. – This option is only available when using a InfoSphere CDC for AS/400 source. 16. Review the mapping settings. 17. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Related concepts “Mapping to consolidate data (one-to-one)” on page 117

120

InfoSphere Change Data Capture Management Console: Administration Guide

Mapping to consolidate data (one-to-many)
If you are using a lookup table to make updates to a target table, then you can map your lookup table using one-to-many row consolidation. When you map a lookup table using one-to-many consolidation, InfoSphere CDC only applies updates to the rows in the target table. v If you insert a row into your lookup table, InfoSphere CDC: – Does not apply an operation to the target table (leaves the target table unchanged); or – Updates the row that has the same consolidation key value. v If you delete a row from your lookup table, InfoSphere CDC does not apply an operation to target table. v If you update a row in your lookup table, InfoSphere CDC updates all rows that have the same consolidation key value. The following example illustrates how InfoSphere CDC can update regional tax code information in a target table that was mapped to a source table using One to Many Consolidation. When there are updates made to the lookup table TAXCODES, InfoSphere CDC updates these columns in the target table.

Before you map your lookup table for one-to-many consolidation, make sure you have completed the following tasks:
v Created a lookup table For InfoSphere CDC to accomplish one-to-many row consolidation, you need to create a lookup table that contains the columns you want InfoSphere CDC to update in your target table. For example, if you want InfoSphere CDC to update tax codes for a specific state, then make sure these columns exist in your lookup table and that you set a primary key. For example, the primary key in the TAXCODES table would be STATE. You can then map your lookup table to the target table using one-to-many consolidation. v Mapped your source table to the target table using Standard mapping type InfoSphere CDC requires that at least one source table is mapped to the target table using a mapping type other than one-to-many consolidation, such as Standard. When you map a source table using one-to-many mapping, InfoSphere
Mapping tables

121

CDC only updates the target table and does not insert or delete rows in the target table. Therefore, another mapping type such as Standard ensures that InfoSphere CDC populates the target table with source data. You need to identify the primary key on the source table. For example, to populate the target table STOREDATA with data from the source table STORELOC, you would map the source columns STORE, CITY, STATE, and TAX to the target columns STORE_CON, CITY_CON, STATE_CON, and TAX_CON. You can map these columns using Standard mapping type. v Created a derived column on the source table using %GETCOL to retrieve data from your lookup table After mapping your source table to the target table using Standard mapping type, InfoSphere CDC requires you create a derived column on the source table to retrieve data from the lookup table when replicating data from the source to the target table. For example, if you want your source table to retrieve tax codes and state information from the TAXCODES table, your %GETCOL expression would be: %GETCOL(TAX, TAXCODES, <default value>, STATE, STATE). The default value of the tax you want InfoSphere CDC to retrieve is up to you. In this example, a typical default value would be 0. See also: “To map a source table to consolidate data (one-to-many)” “To map multi-member source tables using Consolidation one-to-many on AS/400” on page 124

To map a source table to consolidate data (one-to-many)
1. 2. 3. 4. Click Configuration → Subscriptions. Select a subscription, right-click and select Map Tables. Select Consolidation One-to-one from the Mapping type list. Expand the database user or schema from the Source Tables list. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences, then the Filter Tables dialog box automatically displays when you expand a database user or schema. If this preference is not enabled and you want to manually define a filter, select a database use or schema and click Specify Filter. If you have decided to specify a filter, choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. v Show filtered tables—displays only the tables that meet the filter criteria you specified. You can also import any existing filters or choose to export your filter to a text file for future use. Specify your filter and click OK. If you want to modify this filter, select a database user or schema and click Specify Filter. Select one or more tables from the Source Tables list. If you do not see your table listed, select the database user or schema and click Refresh. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK.

5.

6.

7. 8. 9.

122

InfoSphere Change Data Capture Management Console: Administration Guide

then the Filter Tables dialog box automatically displays when you expand a database user or schema. – Name—lists the name of the journal table. Check the consolidation key for the target columns and click Next. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. then enable one of the following: v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>. Click Next. InfoSphere CDC uses the consolidation key to determine the rows that will be updated in the target table in response to an update in the look-up table. If you do not see your table listed. Contact IBM Technical Support to implement bidirectional replication in your environment. 17.3 to replicate source database changes and have configured bidirectional replication.DMCJRN. then enable the Prevent Recursion check box. Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping Mapping tables 123 . InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. 14. Click Next. select a database user or schema and click Specify Filter. 15. Select a table from the Target Tables list and click Next. This prevents InfoSphere CDC from replicating changes back to the source database when you have configured a subscription for bidirectional replication. – Owner—lists the database owner of the journal table. 20. If this preference is not enabled and you want to manually define a filter. This is only available in InfoSphere CDC for Microsoft SQL Server 5. If you are using InfoSphere CDC for Microsoft SQL Server 5. select the database user or schema and click Refresh. If you are replicating source database changes using InfoSphere CDC for Oracle Trigger-based edition and want to use a journal table to mirror database operations from the source to the target table. 11. Expand the database user or schema from the Target Tables list. 12. Management Console retrieves the tables from your database that are available for mapping.3. The consolidation key must identify the same column you identified as the primary key in the lookup table. 18. 19. Click Next. 13. If your configuration requires you to prevent recursive updates when mirroring. When you select the database owner and provide a name for the journal table. enable the Prevent Recursion check box. click Create Table. 16.10. Specify your filter and click OK. If you want to create a new table to map to. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Review the mapping settings.

2. then the Filter Tables dialog box automatically displays when you expand a database user or schema. If you want to hide columns so that the target is not aware of them. select the table mapping you just created and right-click Edit Mapping Details. 8. After you map your lookup table for one-to-many consolidation. select the database user or schema and click Refresh. Click Next. If you have decided to specify a filter. 3. 10. 4. 12. select a database user or schema and click Specify Filter. Specify your filter and click OK. You can also import any existing filters or choose to export your filter to a text file for future use. 4. Click Apply. Expand the database user or schema from the Target Tables list. Management Console retrieves the tables from your database that are available for mapping. selectUpdate all if exists from theOn Insert list. If you want to modify this filter. select a database use or schema and click Specify Filter. On the Operations tab. then the Filter Tables dialog box automatically displays when you expand a database user or schema.v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. Management Console retrieves the tables from your database that are available for mapping. 9. 1. Clear the check box for the column you want to hide and click OK. To map multi-member source tables using Consolidation one-to-many on AS/400 Click Configuration → Subscriptions. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. 5. 11. Make sure that the appropriate columns from the lookup table are mapped to the target table. 7. verify your column mappings to the target table. If this preference is not 124 InfoSphere Change Data Capture Management Console: Administration Guide . choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. On the Column Mappings tab. This ensures that InfoSphere CDC updates all rows where the consolidation key is the same when there is an insert on the lookup table. Select Consolidation One-to-one from the Mapping type list. If this preference is not enabled and you want to manually define a filter. right-click and select Map Tables. select a source table and click Filter Columns. In the Table Mappings view. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Select a subscription. 3. make sure you have set the following on the table mapping: 1. 2. Select one or more tables from the Source Tables list. v Show filtered tables—displays only the tables that meet the filter criteria you specified. If you do not see your table listed. 6. Expand the database user or schema from the Source Tables list.

see “Source RRN (&CNTRRN)” on page 246. When this option is checked. If you want to create a new table to map to. 16. click Create Table. 18. Mapping tables 125 .13. Review the mapping settings. – This option is only available when using a InfoSphere CDC for AS/400 source. v Merge Source Members into One Target Member—merges all members from the source table to a single member in a multi-member. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. Select a table from the Target Tables list. Check the key for the target columns and click Next. Notes: – When this option is checked. After you map your lookup table for one-to-many consolidation. then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. If you do not check this box. For more information. – If no Relative Record Number is available on the target table (for example. Each source member is mapped to the corresponding target member. In the Table Mappings view. InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. 14. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. enabled and you want to manually define a filter. if the table resides on a non-AS/400 system). This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. InfoSphere CDC will automatically start a refresh for that table. make sure you have set the following on the table mapping: 1. Specify your filter and click OK. If you do not see your table listed. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. Choose one of the following options and click Next: v Source and Target Files are Single Member—merges all members from the source table to a single-member target table. 15. select the database user or schema and click Refresh. if the source table is reorganized. select a database user or schema and click Specify Filter. you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. If your configuration requires you to prevent recursive updates when mirroring. v Use Source member Structure on Target—maintains the same multi-member structure on the target table as the one on the source table. enable the Prevent Recursion check box. select the table mapping you just created and right-click Edit Mapping Details. 17.

Review the mapping settings and click Finish. 4. Click Configuration → Subscriptions. If you want to hide columns so that the target is not aware of them. verify your column mappings to the target table. Click Apply. 2. 3. Clear the check box for the column you want to hide and click OK. If you do not see your table listed. 8. selectUpdate all if exists from theOn Insert list. 4. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. You can also import any existing filters or choose to export your filter to a text file for future use. Management Console retrieves the tables from your database that are available for mapping. select a database user or schema and click Specify Filter. If you have decided to specify a filter. Specify your filter and click OK. 9. See also: “To map tables for a subscription on an external datastore” To map tables for a subscription on an external datastore 1. 6. the organization that owns the external target datastore must first add tables to the subscription before you can map the tables. 7. then the Filter Tables dialog box automatically displays when you expand a database user or schema. you can map tables using one of the available mapping types. On the Operations tab. Expand the database user or schema from the Source Tables list. select a source table and click Filter Columns. Select a subscription. Make sure that the appropriate columns from the lookup table are mapped to the target table. On the Column Mappings tab. 5. This ensures that InfoSphere CDC updates all rows where the consolidation key is the same when there is an insert on the lookup table. Click Next. select a database use or schema and click Specify Filter. If this preference is not enabled and you want to manually define a filter. v Show filtered tables—displays only the tables that meet the filter criteria you specified. Mapping to a datastore outside of your organization If you are mapping tables for a subscription with an external target datastore. select the database user or schema and click Refresh. If you want to modify this filter. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Related concepts “Mapping to a datastore outside of your organization” 126 InfoSphere Change Data Capture Management Console: Administration Guide . 10. 3.2. right-click and select Map Tables. After adding tables to the subscription. Select one or more tables from the Source Tables list.

The standard mapping type creates an exact copy of your source table in the staging database. If you have decided to specify a filter. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. Select a subscription. If you have mapped the source table to a staging table and to a JMS message destination. Click Configuration → Datastores. 8. you must map your source table to a table in the staging database using the Standard mapping type. Also. Mapping tables 127 . Click Next. InfoSphere CDC Event Server receives the row-level operation (insert. Management Console retrieves the tables from your database that are available for mapping. right-click and select Map Tables. 5. select a database use or schema and click Specify Filter. Click Configuration → Subscriptions. If you want to setup this type of replication. This may be necessary when you want InfoSphere CDC Event Server to receive replicated rows from the staging database instead of your source database so that you can reduce overhead on your production environment. update. Expand the database user or schema from the Source Tables list. Ensure you have ended replication on the subscription. Enable Message DestinationMappings. then you can map a source table to a JMS message destination.Mapping to a JMS message destination using InfoSphere CDC Event Server If you have created a subscription that uses InfoSphere CDC Event Server as a target datastore. InfoSphere CDC Event Server receives the row-level operation from the staging database and transforms it into XML. 7. If this preference is not enabled and you want to manually define a filter. 2. See also: “To map multiple source tables to a JMS message destination” “To map a single source table to a JMS message destination” on page 129 “To stage a source table” on page 131 To map multiple source tables to a JMS message destination 1. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. then the Filter Tables dialog box automatically displays when you expand a database user or schema. Ensure you are connected to an Event Server datastore. or delete) and transforms it into a row that is inserted into an XML message. you can stage your source table in an embedded staging database provided with InfoSphere CDC Event Server. Ensure you have created a subscription that uses the Event Server datastore as the target database. 3. 6. using the standard mapping type. 4. v Show filtered tables—displays only the tables that meet the filter criteria you specified.

or journal control fields in your XML document. Enable one of the following options: v Use the source table structure for the XML message: – Include before-image values—enable this option when you want the XML message to include the before image of a row-level operation. 13. the after image.9. Select one or more tables from the Source Tables list. 19. or journal control fields in your XML message as XML elements. – Use elements for data values—formats data values of the before image. Enable one of the following options: v Use persistent delivery—enable to ensure the message is not lost in transit due to a JMS provider failure. – Include after-image values—enable this option when you want the XML message to include the after image of a row-level operation. Click Next. You can choose from one of the following: – Use attributes for data values—formats data values of the before image. If you want to modify this filter. the source database. 15. 11. For example. the after image. The after-image represents the data in the source column after an insert. – Include journal control values—enable this option when you want the XML message to include journal control fields. update. Clear the check box for the column you want to hide and click OK. 12. Type a brief description about the queue or topic in the Description box. the _ENNTYPE journal control field indicates the type of row-level operation (insert. update. 128 InfoSphere Change Data Capture Management Console: Administration Guide . or journal control fields in your XML message as XML attributes. select a database user or schema and click Specify Filter. 14. Specify your filter and click OK. 18. 17. 16. update. 10. or delete) that took place on the source table. v Value Format—choose how you want to format source column data in the XML message. or the row-level operations taking place in the database log or journal of the source database. v Do not specify the message format at this time—enable this option when you want to manually decide whether you want to include the before or after image values for source columns. or delete operation on the row. select a source table and click Filter Columns. Click Next. Type the JNDI name of the JMS queue or topic to which you want to send the XML message in the Request Destination box. select the database user or schema and click Refresh. Select the JMS connection you had configured in the InfoSphere CDC Event Server Configuration Tool and click Add Destination to add a queue or a topic. Type the name of queue or topic in theName box. If you do not see your table listed. If you want to hide columns so that the target is not aware of them. These provide information about the source table. or delete operation on the row. You can also import any existing filters or choose to export your filter to a text file for future use. The before-image represents the data in the source column before an insert.

Click Configuration → Datastores. right-click and select Map Tables. 7. 4. The Mapping tables 129 . Enable one of the following options: v Use the source table structure for the XML message: – Include before-image values—enable this option when you want the XML message to include the before image of a row-level operation. 3. Related concepts “Mapping to a JMS message destination using InfoSphere CDC Event Server” on page 127 Related tasks “To map a single source table to a JMS message destination” “To stage a source table” on page 131 To map a single source table to a JMS message destination 1. select a source table and click Filter Columns. 2. If you have decided to specify a filter. v Show filtered tables—displays only the tables that meet the filter criteria you specified. Select a subscription. select a database user or schema and click Specify Filter. Management Console retrieves the tables from your database that are available for mapping. 21. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. Specify your filter and click OK. Click Next and Finish. Enable Message DestinationMappings. If you do not see your table listed. select a database use or schema and click Specify Filter. Ensure you have ended replication on the subscription. 9. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping. 10. then the Filter Tables dialog box automatically displays when you expand a database user or schema. 11. If you want to hide columns so that the target is not aware of them. 13. 8. Click Configuration → Subscriptions. Click Next. Select one or more tables from the Source Tables list. Expand the database user or schema from the Source Tables list. Clear the check box for the column you want to hide and click OK. 6. Click Test and OK. 20. Click Next. 5. If this preference is not enabled and you want to manually define a filter. You can also import any existing filters or choose to export your filter to a text file for future use. Ensure you are connected to an Event Server datastore.v Use transacted sessions—enables InfoSphere CDC Event Server to open a transacted session and commit every message to the JMS queue or topic. 12. select the database user or schema and click Refresh. If you want to modify this filter. Ensure you have created a subscription that uses the Event Server datastore as the target database.

or journal control fields in your XML document. Type the JNDI name of the JMS queue or topic to which you want to send the XML message in the Request Destination box. v Use transacted sessions—enables InfoSphere CDC Event Server to open a transacted session and commit every message to the JMS queue or topic. update. Type the name of queue or topic in the Name box. the source database. or XML file. 20. – Include journal control values—enable this option when you want the XML message to include journal control fields. – Include after-image values—enable this option when you want the XML message to include the after image of a row-level operation. or delete operation on the row. If you have decided to format the XML message based on an imported schema. 22. 19. Click Test and OK. 21. 17. – Use elements for data values—formats data values of the before image. or journal control fields in your XML message as XML attributes. update. 18. Enable one of the following options: v Use persistent delivery—enable to ensure the message is not lost in transit due to a JMS provider failure. Select the JMS connection you had configured in the InfoSphere CDC Event Server Configuration Tool and click Add Destination to add a queue or a topic. Enable this option to import the attribute values. or delete operation on the row.before-image represents the data in the source column before an insert. Enable this option to import all repeated elements. the _ENNTYPE journal control field indicates the type of row-level operation (insert. or the row-level operations taking place in the database log or journal of the source database. 15. mapping project. v Do not specify the message format at this time—enable this option when you want to manually decide whether you want to include the before or after image values for source columns. the after image. You can choose from one of the following: – Use attributes for data values—formats data values of the before image. or journal control fields in your XML message as XML elements. Related concepts 130 InfoSphere Change Data Capture Management Console: Administration Guide . InfoSphere CDC Event Server imports only one repeated element in a group node with the same parent. For example. InfoSphere CDC Event Server imports only the structure of your XML. 16. update. v Import attribute values—by default. Click Next. Type a brief description about the queue or topic in the Description box. This may be necessary if attribute values represent the structure of your XML document. These provide information about the source table. or delete) that took place on the source table. v Value Format—choose how you want to format source column data in the XML message. The after-image represents the data in the source column after an insert. the after image. 14. then browse for the file and enable one or both of the following options: v Import repeated elements with the same parent—by default. Click Next and Finish.

v Show filtered tables—displays only the tables that meet the filter criteria you specified. Specify your filter and click OK. Ensure you have ended replication on the subscription. 3. 9. Expand the database user or schema from the Target Tables list. Ensure you have created a subscription that uses the Event Server datastore as the target database. Select one or more tables from the Source Tables list. 11. Click Configuration → Subscriptions. If this preference is not enabled and you want to manually define a filter. You can also import any existing filters or choose to export your filter to a text file for future use. Click Next. then the Filter Tables dialog box automatically displays when you expand a database user or schema. 15. right-click and select Map Tables. select a database user or schema and click Specify Filter. 13. Enable One mapping of any type. Mapping tables 131 . then the Filter Tables dialog box automatically displays when you expand a database user or schema. Expand the database user or schema from the Source Tables list. Management Console retrieves the tables from your database that are available for mapping. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. 4. select a database use or schema and click Specify Filter. Click Configuration → Datastores. 10. Ensure you are connected to an Event Server datastore. 14. If the Automatically prompt for filter when expanding nodes check box is enabled in your preferences. choose a filtering method from the following options: v Show all tables—displays all the tables in your database that are available for mapping.“Mapping to a JMS message destination using InfoSphere CDC Event Server” on page 127 Related tasks “To map multiple source tables to a JMS message destination” on page 127 “To stage a source table” To stage a source table 1. Select a subscription. select a source table and click Filter Columns. Select Standard as the mapping type. Specify your filter and click OK. If you have decided to specify a filter. Management Console retrieves the tables from your database that are available for mapping. If you do not see your table listed. select the database user or schema and click Refresh. If you want to hide columns so that the target is not aware of them. 8. Clear the check box for the column you want to hide and click OK. 5. 12. 7. 6. If this preference is not enabled and you want to manually define a filter. Click Next. 2. select a database user or schema and click Specify Filter. If you want to modify this filter.

enable the Prevent Recursion check box. v Specify the key—select the target columns from the Key Columns list. If your configuration requires you to prevent recursive updates when mirroring.16. 17. Review the mapping summary. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. The results of the search are used to build a WHERE clause which uniquely identifies the row on the target column to apply data. Related concepts “Mapping to a JMS message destination using InfoSphere CDC Event Server” on page 127 132 InfoSphere Change Data Capture Management Console: Administration Guide . Choose a replication method from the following and click Next: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. Availability of the above options is dependent on the platform and version of InfoSphere CDC Event Server that you have installed. Use if one or more target columns uniquely identifies a row. Choose one of the following options and click Finish: v Define column mappings—continues with the column mapping v Create a new table mapping—allows you to start a new table mapping v Return to current view—returns you to the current view. 18. 19. Use if your target table has an index that uniquely identifies a row. Choose one of the following and click Next: v Use an Index—select the index name from the Index box. v Use all searchable columns—searches all target columns to identify which columns are suitable to uniquely identify rows.

Related concepts “Remapping a source table” To remap a source table (InfoSphere CDC Event Server) 1. then you can do the following: v Remap a source table already mapped to a JMS message destination to a staging target table. You set this when mapping tables in the Map Tables wizard. v Remap a source table already mapped to a staging target table to a JMS message destination. Select the mapped source and target tables in the Table Mappings view. 3.Managing table mappings You can manage table mappings. If you want to remap a source table on a subscription that uses InfoSphere CDC Event Server as the target datastore. Click Configuration → Datastores. © Copyright IBM Corp. 5. Right-click and click Remap Source Table . Ensure the subscription has at least one table mapping. you will learn: “Remapping a source table” “Changing the message destination” on page 134 “Flagging a source table for a refresh” on page 135 “Marking a table capture point on a source table” on page 135 “Parking a table mapping from replication” on page 136 “Changing the refresh order on a table mapping” on page 137 “Changing the replication method of a table mapping” on page 137 “Selecting a new journal table” on page 139 “Setting members for replication” on page 140 “Deleting table mappings” on page 140 “Updating the definition of mapped source and target table in a subscription” on page 141 Remapping a source table You can remap an existing source table so that it is mapped to the correct target table. 2008 133 . 4. Select the subscription that contains the mapped source and target tables. See also: “To remap a source table” “To remap a source table (InfoSphere CDC Event Server)” To remap a source table 1. Ensure you are connected to an Event Server datastore. 2. Ensure you have ended any active replication on the subscription. 6. Click Configuration → Subscriptions. In this section.

Ensure you have ended replication on the subscription. 6. 7. Related concepts “Remapping a source table” on page 133 Related tasks “To map multiple source tables to a JMS message destination” on page 127 “To stage a source table” on page 131 Changing the message destination This option is only available for subscriptions that use InfoSphere CDC Event Server as the target datastore. Select the table mapping in the Table Mappings view. See also: “To change the message destination of a table mapping” To change the message destination of a table mapping 1. 5. Click Next and map the source table to a message destination or to a staging target table. Enable one of the following: v Message Destination Mappings—enable this option if you want to map this source table to a message destination. You can change the JMS message destination of a table mapping. Related concepts “Changing the message destination” 134 InfoSphere Change Data Capture Management Console: Administration Guide . Ensure you have created a subscription that uses the Event Server datastore as the target database. Select a subscription that contains the table mapping to a message destination. 4. Click Configuration → Subscriptions. This option is only available if you have already mapped your source table to a message destination or to a staging target table. Ensure you have created a subscription that uses the Event Server datastore as the target database. Right-click Change Message Destination. Click Configuration → Datastores. Select the subscription that contains the mapped source and target tables. 4. 2. Select the table mapping in the Table Mappings view. Right-click Remap Source Table. Ensure you are connected to an Event Server datastore.2. 5. 6. Select Standard as the mapping type. Select the new message destination and click OK. 3. Click Configuration → Subscriptions. v One mapping of any type—enable this option if you want to map this source table to a staging target table. 3.

This may cause the target table to become inconsistent with the source table. Synchronizing your source and target table can become necessary when you have parked a subscription from replication for some time to make changes (such as updating the definition of a source table) and the journal no longer logs changes that are taking place on the source. 5. When you are ready to start mirroring. then you can flag the source table for a refresh before you start mirroring. Select the subscription that contains the mapped source and target tables. then you can Managing table mappings 135 .Flagging a source table for a refresh If you have a subscription that contains a target table that is not synchronized with the source table. See also: “To flag a source table for a refresh before mirroring” To flag a source table for a refresh before mirroring 1. Right-click and click Flag for Refresh. If you want to override the position set by InfoSphere CDC. Click Configuration → Subscriptions. Select the mapped source and target tables in the Table Mappings view. This is possible when you have already synchronized (refreshed) your source and target tables using an application other than InfoSphere CDC Management Console (for example. InfoSphere CDC will then mirror subsequent changes to the target. InfoSphere CDC will synchronize this source table with your target table when you start mirroring. using the import or export capabilities of your database platform) and you know the point in time your source and target are synchronized with each other. when you start refresh on a table. 3. You set this when mapping tables in the Map Tables wizard. When you flag a source table for a refresh. You can control this behavior so that InfoSphere CDC only deletes certain rows (using SQL statements) or deletes no rows in response to a refresh operation. Related concepts “Starting and ending replication on subscriptions” on page 197 “Mapping tables” on page 91 “Flagging a source table for a refresh” “Controlling the apply of refresh operations” on page 183 “Ending replication on a subscription” on page 198 Marking a table capture point on a source table Attention: Only use this procedure when you want to override an existing position in the stream of changed data. 4. InfoSphere CDC mirrors changes to the target table from the current position in the stream of changed data. InfoSphere CDC deletes all the rows in your target table. InfoSphere CDC will send all changes from the source table to the target table so that both tables are synchronized. 6. Ensure you have ended any active replication on the subscription. This position is set by InfoSphere CDC when you select Mirror (Change Data Capture) after mapping your tables in the Map Tables wizard. Ensure the subscription has at least one table mapping with replication method set to Mirror. 2. By default.

manually mark a table capture point in Management Console. See also: “To mark a table capture point on a source table before mirroring” To mark a table capture point on a source table before mirroring 1. 5. Right-click and click Park (Do not replicate). 6. Related concepts “Marking a table capture point on a source table” on page 135 “Ending replication on a subscription” on page 198 Parking a table mapping from replication If your subscription contains more than one table mapping. Ensure you have ended any active replication on the subscription. When you park a table mapping from replication. 2. Related concepts “Parking a table mapping from replication” “Ending replication on a subscription” on page 198 136 InfoSphere Change Data Capture Management Console: Administration Guide . Right-click and click Mark Table Capture Point For Mirroring. Select the mapped source table in the Table Mappings view. See also: “To park a table mapping from replication” To park a table mapping from replication 1. 3. Ensure your database platform is in idle mode to avoid losing synchronization between your source and target tables. 2. Click Configuration → Subscriptions. Tip: You can mark a table capture point on more than one mapped source table at a time. Click Configuration → Subscriptions. 5. then you can park one or more before starting mirroring or a refresh on your subscription. When you decide to start mirroring on the subscription. Tip: You can park more than one table-mapping at a time. Select the mapped source and target table in the Table Mappings view. Ensure you have ended any active replication on the subscription that contains the source table. 4. InfoSphere CDC identifies the position you have set as the point in time from which to capture and replicate database changes to the target. 4. Select the subscription that contains the mapped source and target tables. 3. Select the subscription that contains the mapped source and target tables. InfoSphere CDC does not replicate changes to the target.

Changing the refresh order on a table mapping If you have set referential integrity constraints on your tables. Each table you decide to move into a group is assigned a sequence number that InfoSphere CDC uses to refresh each table mapping in numerical order. You can change the replication method of one or more of your table mappings within a subscription. based on the fact that each employee belongs to a specific department. Click Add New Group to add the first group-Group 1. Ensure you have ended any active replication on the subscription. See also: “To change the replication method of a table mapping” on page 138 Related concepts “Table Mappings view (Monitoring perspective)” on page 10 “Starting mirroring on a subscription” on page 197 “Ending replication on a subscription” on page 198 Managing table mappings 137 . 5. 6. See also: “To change the refresh order on a table mapping” To change the refresh order on a table mapping 1. Select the subscription that contains the mapped source and target tables. ensure that the target tables are empty before starting replication. if you are mirroring the source table to the target. 2. then you need to end replication on the subscription. For example. Click Configuration → Subscriptions. You can change the order in which InfoSphere CDC refreshes your table mappings by moving tables into groups. Select the table mapping you want InfoSphere CDC to refresh first in the Table Mappings view. Right-click and click Change Refresh Order. Repeat this step for as many groups you want to add. For example. if you want InfoSphere CDC to refresh your DEPARTMENT table before refreshing the EMPLOYEE table. Note: Any remaining table mappings that you did not add to a group are refreshed by InfoSphere CDC last. 4. 3. then you can set a refresh order to preserve these constraints during a refresh. Before you can change the replication method. Related concepts “Changing the refresh order on a table mapping” “Selecting a new journal table” on page 139 “Ending replication on a subscription” on page 198 Changing the replication method of a table mapping Your subscription can contain table mappings that have a combination of replication methods: Mirror or Refresh. you may want InfoSphere CDC to refresh your DEPARTMENT tables before refreshing your EMPLOYEE tables. 7. When setting up tables that have referential integrity constraints. then you can add a group for each of these table mappings and move the DEPARTMENT table in group 1 and the EMPLOYEE table in group 2.

To change the replication method of a table mapping 1. Right-click and click Change Replication Method. enable the Prevent Recursion check box. 138 InfoSphere Change Data Capture Management Console: Administration Guide . then InfoSphere CDC for AS/400 uses a unique key to replicate to the target. if the table resides on a non-AS/400 system). Enable one of the following: v Mirror (Change Data Capture)—immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time.3. This was the journal table you had selected in the Map Tables wizard. Ensure you have ended any active replication on the subscription. If your configuration requires you to prevent recursive updates when mirroring. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). if the source table is reorganized. For more information. Select the table mapping in the Table Mappings view. If you do not check this box. When this option is checked. After InfoSphere CDC completes the refresh operation on the subscription. – This option is only available when using a InfoSphere CDC for AS/400 source. 3. Note: If you are replicating your source table using InfoSphere CDC for Oracle Trigger-based edition and decide to change the replication method from Mirror to Refresh. InfoSphere CDC Event Server will automatically start a refresh for that table. 2. This is only available in InfoSphere CDC for Microsoft SQL Server 5. then you must change the replication method back to Mirror and select the same journal table you were using before. 4. Select the subscription that contains the mapped source and target tables. 5. v Use Relative Record Number—enables InfoSphere CDC to replicate updates to the target using a relative record number. Click Configuration → Subscriptions. v Prevent Recursion—prevents InfoSphere CDC from replicating changes back to the source database when you have configured a subscription for bidirectional replication. v Refresh (Snapshot)—replicates a snapshot of the source table to the target table. Contact IBM Technical Support to implement bidirectional replication in your environment. you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. then InfoSphere CDC disassociates the journal table from the source table. if you want InfoSphere CDC to continue mirroring changes from this source table using the same journal table. Notes: – When this option is checked. see “Source RRN (&CNTRRN)” on page 246. InfoSphere CDC sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. – If no Relative Record Number is available on the target table (for example. 6.

Enable Refresh. See also: “To select a new journal table” To select a new journal table 1. This lets you select a new journal table. This disassociates the journal table from the source table. click Change Replication Method. Each time there is a new row-level operation on your source table. If you want to change the journal table you had selected in the Map Tables wizard. You can then change the replication method back to Mirror and select a new journal table that you want InfoSphere CDC to use. 5. Select the same table mapping and click Change Replication Method. a trigger executes in response to the database operation and InfoSphere CDC reads the journal table to identify the database operation that occurred. Click Monitoring → Subscriptions. The table mapping should have a replication method and status of Refresh/Refresh. InfoSphere CDC Event Server creates this new journal table and uses it to detect and replicate database changes from the source to the target. 4.DMCJRN. If you are using this same source table in other subscriptions. then you must change the replication method to Refresh so that InfoSphere CDC can disassociate the journal from the source table. If you have mapped your source and target tables and have enabled Mirror (Change Data Capture) in the Map Tables wizard. 6. InfoSphere CDC disassociates the journal table from the source table in each subscription. When you select the database owner and provide a name for the journal table. Ensure you have ended replication on the subscription. 2. v Use Default Journal—enable when you want InfoSphere CDC for Oracle to use the default journal table provided with InfoSphere CDC for Oracle: <TS SCHEMA>. Select a table mapping. 11. InfoSphere CDC then scrapes the database operation from the journal table and replicates it to the target. Click OK. 7. 10. then you have already selected a journal table. Select the subscription that contains the mapped source and target tables. Choose one of the following options and click OK. 8. v Use Selected Journal—enable when you want InfoSphere CDC for Oracle to use another journal table other than the default journal table provided with InfoSphere CDC for Oracle. InfoSphere CDC uses this journal table to detect and replicate database changes from the source to the target. Enable Mirror. 9. Right-click. – Owner—lists the database owner of the journal table. Managing table mappings 139 . 3. click Show Table Mappings. InfoSphere CDC creates this table and uses it to track the database operations that occur on your source system. then you must set the replication method to Refresh for these subscriptions as well. Right-click.Selecting a new journal table InfoSphere CDC for Oracle Trigger based edition uses journal tables to detect and replicate database changes to the target table.

You can choose from one of the following: v All current and future members—Enables InfoSphere CDC to replicate all members. See also: “To select a member for replication” To select a member for replication 1. then you can select the members you want InfoSphere CDC to replicate. Ensure you have ended replication on the subscription. 2. Select the subscription that contains the mapped source and target tables. including members you may add a future point in time. 6. Related concepts “Ending replication on a subscription” on page 198 “Selecting a new journal table” on page 139 “Mapping tables” on page 91 Setting members for replication iSeries environments supports a table concept known as multi-member files. in which one table can possess several different members. Right-click. Right-click. Before deleting a table mapping. Related concepts “Setting members for replication” Deleting table mappings You can delete table mappings that belong to a particular subscription. If you have installed InfoSphere CDC for AS/400 and have multi-member source tables. Select the subscription that contains the mapped source and target tables. 140 InfoSphere Change Data Capture Management Console: Administration Guide . Each member is part of the same table and shares the same schema. 3. Ensure you have ended replication on the subscription. See also: “To delete a table mapping” “To delete a table mapping (InfoSphere CDC Event Server)” on page 141 To delete a table mapping 1. 5.– Name—lists the name of the journal table. 2. 7. then you are provided with the option to delete either mapping. click Show Table Mappings. 4. Click Configuration → Subscriptions. you need to end replication on the subscription that contains the table mapping you want to delete. If the subscription uses InfoSphere CDC Event Server as the target datastore and you have mapped your source table to both a JMS message destination and a staging target table. click Set Member Replication. Select a table mapping. v Selected members only—Enables InfoSphere CDC to only replicate the members you selected. Click Configuration → Subscriptions. but the members are uniquely named and have unique data. 3.

you will be presented with the following options: v Delete message destination mapping—enable this option if you want to unmap your source table from a JMS message destination. Related concepts “Ending replication on a subscription” on page 198 Updating the definition of mapped source and target table in a subscription Once you change the structure of a source or mapped target table. then you may want to map this new column to a target column. Right-click and click Delete Table Mappings. set column constraints. or both. v Updating the definition of a source table—if you change the definition of a source table (add a new column. if you have added a new column on the source table. Related concepts “Ending replication on a subscription” on page 198 To delete a table mapping (InfoSphere CDC Event Server) 1. or new foreign key dependencies). you must update the definition of the table so that subscriptions are aware of the new structure. For example. Select a subscription that contains the table mapping to a message destination. Select the table mapping in the Table Mappings view. v Delete staging target mapping—enable this option if you want to unmap your source table from a staging target table. then you need to update the definition of the target table in Management Console. Click Configuration → Subscriptions. See also: “To update the definition of a source table” on page 142 “To update the definition of a target table” on page 142 Managing table mappings 141 . If you have mapped your source table to both a message destination and a target staging table. to a staging target table. Ensure you have ended replication on the subscription. 5. Right-click and click Delete Table Mappings. Management Console requires you to update the source table so that the new structure is available for configuration when editing your table mapping details. 2. 3. 4. then click Yes to the confirmation message. 6. or new foreign key dependencies). Select the table mapping in the Table Mappings view. set column constraints. v Updating the definition of a target table—if you change the definition of a target table (add a new column. if you have added a new column on the target table. Management Console requires you to update the target table so that the new structure is available for configuration when editing your table mapping details.4. 5. then you have to update the definition of the table in Management Console. If you have mapped your source table to either one of a message destination or a staging target table. For example. then you may want to map a source column to the target column.

3. select and right-click on the table mapping. 3. Related concepts “Flagging a source table for a refresh” on page 135 “Updating the definition of mapped source and target table in a subscription” on page 141 “Mapping source columns to target columns” on page 157 To update the definition of a target table 1. Related concepts “Mapping source columns to target columns” on page 157 “Updating the definition of mapped source and target table in a subscription” on page 141 142 InfoSphere Change Data Capture Management Console: Administration Guide .To update the definition of a source table 1. then you need to map a source column to the new target column. Click Update. then you need to map that column to the target. 4. 2. Select Update Table Definition → Source Table. Click End Replication on each active subscription. Select a subscription. Select the subscription that contains the mapped source and target tables. 7. Click End Replication on each active subscription. you need to synchronize your source and target tables so that InfoSphere CDC can set a log position. In the Table Mappings area. Click Configuration → Subscriptions. you should verify your mapping details. In the Table Mappings area. 2. you should verify your table mapping details. 5. If you have added a new column to your target table and you want InfoSphere CDC to replicate data to the column. Click Configuration → Subscriptions. 5. Note: As a best practice. Select Update Table Definition → Target Table. Note: As a best practice. 4. If you have added a new column and you want InfoSphere CDC to replicate data from this column. 6. Click Update. If you want to restart mirroring on the subscription. 6. select and right-click on the table mapping.

Expand the Source tree and build the structure of the XML message in one of the following ways: v If you want the XML message to have the same structure as your source table. v You can manually build the XML structure using the options provided in the XML Document Structure area: – Add an XML element © Copyright IBM Corp. import/export XML schemas. Ensure you have created a subscription that uses the Event Server datastore as the target database. Ensure you are connected to an Event Server datastore. import and export mapping projects. 5. In this section. Click the Table Mappings view and select the table mapping. 7. See also: “To create an XML message” To create an XML message 1. 2008 143 . Click the XML Message tab. v If you have an existing XML structure. 2. and mapping projects” on page 144 “Building an XPath expression” on page 146 “Querying columns from other tables” on page 147 Creating an XML message You can create an XML message by mapping source columns to XML elements and attributes. This tab is only available for subscriptions targeting a JMS message destination. schemas. you will learn: “Creating an XML message” “Importing and exporting XML files. then you can import the structure into the XML Document Structure area. and query columns from other tables if required. Click Configuration → Datastores. then you can drag and drop the entire source table to the root (/) node of the XML Document Structure area. you can use the XML Message tab to customize which columns you want to map to XML elements and attributes.Customizing JMS message destination mappings After mapping your tables using the Map Tables wizard. This method retains mappings between source columns and XML elements and attributes. 4. Right-click Edit Mapping Details. 6. 3. Select the subscription that contains the table mapping to a message destination. Ensure you have ended any active replication on the subscription. You can build your XML message and XPath expressions. Click Configuration → Subscriptions.

and mapping projects” Related tasks “To build an XPath expression” on page 146 “To end replication” on page 199 Importing and exporting XML files. schemas. you can edit the expression using the Expression editor. You can also export the schema. Related concepts “Importing and exporting XML files. This occurs when you have mapped an XML element or attribute to a source column that is blank. the structure of the XML document is displayed the XML Document Structure area in Management Console. then InfoSphere CDC Event Server includes the XML element or attribute in the XML message. verify the following options from the Output area: v Always—indicates that if the value of an XML element or attribute is empty. When importing the schema. 144 InfoSphere Change Data Capture Management Console: Administration Guide .– Add an XML attribute – Rename an element or attribute – Move an XML element or attribute up and down the result tree – Change the node type to either XML element or attribute 8. Click Apply. For each XML element or attribute you have mapped to a source column. You can also import and export XSD files and XTRANS files created in Management Console. and mapping projects You can import XML files into Management Console. However. v Importing XML files—you may have already created an XML file using an editor outside of Management Console. When importing XML files. v Optional when NULL—indicates that if the value of an XML element or attribute is mapped to a source column that is NULL. if the XML element or attribute is mapped to a source column that contains an empty string. then the XML element or attribute is not included in the XML message. 9. The XPath expression identifies the XML element or attribute that contains the value of a source column. 10. This may be necessary when another department or organization requires the schema. This value is represented as an XPath expression in the Value area. then InfoSphere CDC Event Server includes the XML element or attribute in the XML message and sets the value to an empty string. or when you have mapped the XML element or attribute to a source column that contains a derived expression that results to an empty string. v Importing and exporting XSD files—you may want to import the schema of an XML message into Management Console when it is necessary to generate an XML document using a specific structure. then the XML element or attribute is not included in the XML message. you can choose to import repeated elements and/or choose to import attribute values into . you are mapping the value of the source column to an XML element or attribute. When you map a source column to an XML element or attribute. You can then continue to map source columns to XML elements or attributes to create values and build XPath expressions if required. You can import this XML file and continue mapping source columns to elements and attributes in Management Console. If necessary. schemas. v Output when empty or NULL—indicates that if the value of an XML element or attribute is mapped to a source column that is empty or NULL. Verify the XPath expression for each mapping in the Value area.

Click Configuration → Datastores. 8. 7. Click Apply. Select the subscription that contains the table mapping to a message destination. schema. Ensure you have created a subscription that uses the Event Server datastore as the target database. Right-click Edit Mapping Details. Click the Table Mappings view and select the table mapping. Ensure you are connected to an Event Server datastore. select one of the following: v Schema file—imports the structure of the XML document. Ensure you are connected to an Event Server datastore. 4. The values in the mapping definition replace any preexisting mappings of your XML document in Management Console. Click Configuration → Subscriptions. Enable this option to import the attribute values. or mapping definition file” “To export an XML schema or mapping definition file” To import an XML. schema. 5. Click and from the Files of Type list. v XML file—imports an XML document. then the XML Import Options dialog box opens and you can enable one or both of the following options: – Import repeated elements with the same parent—By default. 2. See also: “To import an XML. You can later reuse the mapping definition for other XML documents by importing it back into Management Console.v Importing and exporting XTRANS files—you can export the mapping definition of your XML document with values to your local computer. Ensure you have created a subscription that uses the Event Server datastore as the target database. It is important to note that any preexisting mappings between source columns to XML elements and attributes in Management Console are replaced with the imported mapping definition. Management Console imports only the structure of your XML. v Mapping definition—imports an XML document with mapped source column to XML element and attribute values. and mapping projects” on page 144 To export an XML schema or mapping definition file 1. Customizing JMS message destination mappings 145 . or mapping definition file 1. Click Configuration → Subscriptions. Enable this option to import all repeated elements. 2. Click the XML Message tab. Management Console imports only one repeated element in a group node with the same parent. If you are importing an XML file. Related concepts “Importing and exporting XML files. – Import attribute values—By default. This may be necessary if attribute values represent the structure of your XML document. schemas. Click Configuration → Datastores. 6. 3.

Select the subscription that contains the table mapping to a message destination. Click the XML Message tab. 5. a function. attribute. schemas. Right-click Edit Mapping Details. 3. 5. 8. or a combination of these. Click the Table Mappings view and select the table mapping. 7. select one of the following: v Schema file (XSD)—exports only the structure of the XML document. 4. For more information about a specific function or operator. and mapping projects” on page 144 Building an XPath expression When you launch the Expression Builder. Ensure you have an existing XML structure you can build an expression for in the XML Document Structure area. Any pre-existing mapping definitions are not exported. You can build an expression using a combination of one or more of the following items: Functions—You can specify functions and a location path for your XPath expression. Click the XML Message tab. Right-click Edit Mapping Details. and the tree structure. you can build an XPath expression to reference a source column (the before or after image). See also: “To build an XPath expression” To build an XPath expression 1. 6. Click the Table Mappings view and select the table mapping. a journal control field. For more information about XPath expressions. v Operators—You can use operators to build your expression.org/TR/xpath. Related concepts “Importing and exporting XML files. 6. Ensure you are connected to an Event Server datastore. Click Configuration → Subscriptions. Click and from the Save as Type list. v Mapping definition (XTRANS)—exports the structure of the XML document and the mapping definition you created in Management Console. Ensure you have created the structure of an XML message that you can export. This includes the name of the element. 4. 2. a literal value in single quotes. 7. see http://www. Click Configuration → Datastores. Select an XML element or attribute for which you want to build an XPath expression and double-click the Value area to open the Expression Builder. Ensure you have created a subscription that uses the Event Server datastore as the target database.3. 8. v 146 InfoSphere Change Data Capture Management Console: Administration Guide . Select the subscription that contains the table mapping to a message destination.w3. Click Save. press F1.

double-click it to add to the Expression box. Ensure you have created a subscription that uses the Event Server datastore as the target database. This can be from a database you have configured a JDBC connection for or from the InfoSphere CDC Event Server staging database. Right-click Edit Mapping Details. You can query these columns from other databases for which you have configured a JDBC connection or from tables in the InfoSphere CDC Event Server staging database. 9. Select the table you want to add. Related concepts “Building an XPath expression” on page 146 Querying columns from other tables The XML message want to send may depend on columns from other tables. 12. Click Configuration → Subscriptions. Your XPath expression can reference these. 9. Click Next. Click Validate to verify the expression and click OK. v Target XML Document—Represents the XML document that you want to send to the JMS queue or topic. 2. 4. v Saved expressions—Lists any saved expressions you have built. See also: “To query columns from other tables” To query columns from other tables 1. Expand the Other Tables tree. 6. v Add table as a child of another table—enable when you want the table to reside as the child of another table. Choose one of the following: v Add table as top level node—enable when you want the other table to reside at the node level. 10. Choose one of the following: Customizing JMS message destination mappings 147 . a literal or a combination of each of these. Click Add Tables. Select the subscription that contains the table mapping to a message destination. Click Configuration → Datastores. Click the XML Message tab. You can repeat this process for all the nodes you want to add to the expression. Click the Table Mappings view and select the table mapping. 5.Database—Represents the source database and lists all the nodes (such as source columns and journal control fields) in your source table. You must add a parent table before you can add a child table. v The XPath expression should now reference the before or after image of the column. 7. 3. 8. Select the node you want to search for. Ensure you are connected to an Event Server datastore. a function. 11.

13. click Add to enable the fields required to build your WHERE clause statement. If you specify an alias for the column name. select Value from the Type list and specify the value in the Value box. you must map this expression to an XML element or attribute in your XML document. then because there is no after image of a delete operation. 17. if you map the before image of a column to an XML element or attribute and the operation on the source database was an insert. click Add. If you had enabled the Click Finish to add the table and open the SQL editor option. Click Next. With SQL. the SELECT statement will retrieve the column and return the result with the alias name you specified. v The before image or the after image of a row—to build your WHERE clause so that it returns the before image or the after image of the column. you can choose to add filters to restrict which rows are returned by the query. The where clause is optional.v Click Next to continue with the wizard—enable when you want the wizard to create the SQL statement for you based on the columns in the other table. If you want to create a WHERE clause. Omitting the WHERE clause from your SQL statement specifies that all rows are returned by the query. InfoSphere CDC Event Server will retrieve data values from the table based on your query. If you want to add more columns. then because there is no before image of that column. 15. if you want InfoSphere CDC Event Server to detect any missing before images or after images. The SQL Expression Editor opens and you are required to build a valid SQL expression. v The column of a parent table—to build your WHERE clause so that it returns the column of the parent table. On the WHERE Clause page. InfoSphere CDC Event Server inserts the after image of the column instead when you enable this check box. 14. InfoSphere CDC Event Server inserts the before image of that column instead. Your WHERE clause can return one of the following values: v Static values—to build your WHERE clause so that it returns a static value. review the columns in your select statement. select Parent Table Column from the Type list and then select the column name from the Value list. Click OK and click Next. then use other image check box. aliases can be used for column names and table names. On the Select Clause page. Specify a name for the column and the column or expression you want InfoSphere CDC Event Server to retrieve. select Trigger from the Type list and then select either the before image or the after image of the column from the Value list. click Next to continue build your SQL statement with the help of the wizard. Otherwise. This option is only available if the table is added a child of a parent table. if you map the after image of a column to XML element or attribute and the operation on the source database was a delete. When you have completed building the SQL statement. Note: You can modify the name to an alias name. For example. When you start replication. Also. 148 InfoSphere Change Data Capture Management Console: Administration Guide . 16. v Click Finish to add the table and open the SQL editor—enable when you want to create your own SQL statement in the SQL Expression editor. You can modify the SQL statement in the SQL Expression editor. click Finish. Also. then enable the If before/after image does not exist.

19. On the ORDERED BY clause page. it can be used in a SELECT statement to collect data across multiple rows. The GROUP BY clause is optional. group the results by one or more columns. Click Next. You can order the result set in either ascending or descending order. On the GROUP BY clause page. Click Finish. When specified. 21. Related concepts “Querying columns from other tables” on page 147 Customizing JMS message destination mappings 149 . sort the records in your result set. 20.18. The ORDER BY clause is optional.

150 InfoSphere Change Data Capture Management Console: Administration Guide .

6. 7. This is normally used for a request or response scenario.Setting JMS message header properties Only available for subscriptions targeting a JMS message destination. In addition to the JMS header properties provided with InfoSphere CDC Event Server. You can also add or delete custom properties that you create. 3. you may also need to associate extra information in the header of an XML message. or a provider-native byte value. InfoSphere CDC Event Server assigns a priority of © Copyright IBM Corp. an application-specific string. you will learn: “Defining the JMS message header” “Setting general runtime options” on page 153 “Selecting a character encoding” on page 154 Defining the JMS message header You can add and delete JMS message header properties. By default. Ensure you are connected to an Event Server datastore. Select the subscription that contains the table mapping to a message destination. 5. Click the Table Mappings view and select the table mapping. InfoSphere CDC Event Server lets you specify custom JMS header properties in an XML message. v JMS Priority—indicates the priority at which the JMS server will handle the message. Click Configuration → Datastores. Select one of the following in the Standard Settings area. 2. You can edit these values using the expression editor at any time. Ensure you have created a subscription that uses the Event Server datastore as the target database. See also: “To add a JMS message header property” “To add a custom JMS message header property” on page 152 “To delete a custom JMS message header property” on page 152 To add a JMS message header property 1. 2008 151 . you can use the XML Settings tab to set JMS message header properties for the XML message. Click Configuration → Subscriptions. Click the XML Settings tab. v JMS Correlation ID—provides a way to correlate related messages. You can use this information in a JMS selector to filter messages. This can either be a vendor-specific ID. These properties are saved on the source table to XML mapping and are valid each time you send the XML message to a queue or topic. Right-click Edit Mapping Details. In this section. 4.

9. 152 InfoSphere Change Data Capture Management Console: Administration Guide . Ensure you are connected to an Event Server datastore. Click Add. Your JMS provider can use a message repository that contains the definition of messages sent by third party applications. Click Configuration → Datastores. 7. which indicates that the XML message will never be deleted automatically from the queue or topic. Click Apply. Click the Table Mappings view and select the table mapping. Ensure you are connected to an Event Server datastore. v JMS Reply To—contains a destination supplied by a client when a message is sent. Click OK. Click to open the expression editor and set a value for the JMS property. 10. Type the name of the JMS property and click OK. 4. Ensure you have created a subscription that uses the Event Server datastore as the target database. 8. Click the XML Settings tab. Select the subscription that contains the table mapping to a message destination. This value is used by your JMS provider to delete XML messages automatically once the amount of time specified in the box expires. 9. 5. Click Configuration → Subscriptions. v JMS Type—specifies the type of message you are sending. Related concepts “Setting JMS message header properties” on page 151 To add a custom JMS message header property 1. Click Configuration → Datastores. v JMS Time to Live—specifies the number of milliseconds that you want the XML message to remain in the queue or topic. 6. Right-click Edit Mapping Details. You should enter a symbolic value that can be configured to the values defined in the current providers’ message repository. If you want to receive a response from the JMS queue or topic when either of these destinations receive a message. 8. Click to set a value in the Expression editor. 10. 2. JMS uses a priority scale from 0 to 9. 3. Click OK and Apply. 2. Click Configuration → Subscriptions. 11. where 0 indicates the lowest priority and 9 indicates the highest priority.4. then specify the destination. Specify a value (enclose the value in quotation marks) or an expression for the JMS property and click Verify . Related concepts “Setting JMS message header properties” on page 151 To delete a custom JMS message header property 1. This could be the name of the queue or topic. The default value is 0.

Click Configuration → Datastores. Right-click Edit Mapping Details. 2. This results in no distinction between an empty string and a null value. 5. Click the Table Mappings view and select the table mapping. v Streamed transformation mode—by default. Most XML parsers return an empty string if a referenced node does not exist in the source table. 3. Select the subscription that contains the table mapping to a message destination. InfoSphere CDC Event Server does not trim white spaces before and after character strings. Select the JMS property you want to delete in the Custom Settings area. 9. Related concepts “Setting JMS message header properties” on page 151 Setting general runtime options You can set the following runtime options: v Trim text—by default. v Nullable XPath expression—by default. Click Apply. Click Delete. InfoSphere CDC Event Server can differentiate a real empty string (the node does exist. The XST technology will dynamically switch parsing mode between (Simple API for XML) SAX and DOM depending on your transformation requirements. See also: “To enable InfoSphere CDC Event Server to trim text” “To disable InfoSphere CDC Event Server from differentiating between an empty string from a NULL value” on page 154 “To disable streamed transformation mode” on page 154 To enable InfoSphere CDC Event Server to trim text 1. Ensure you have created a subscription that uses the Event Server datastore as the target database. Disable this check box if you want InfoSphere CDC Event Server to use the Document Object Model (DOM) instead. 7. Select the subscription that contains the table mapping to a message destination. but contains an empty value) from a null value (the referenced node does not exist at all). Click the Table Mappings view and select the table mapping. You can enable this so that InfoSphere CDC Event Server trims the text. 6. 4. This may affect the performance but may be necessary in some cases. Setting JMS message header properties 153 . 8. 4. Ensure you have created a subscription that uses the Event Server datastore as the target database. InfoSphere CDC Event Server differentiates between empty strings and a null value. Ensure you are connected to an Event Server datastore. InfoSphere CDC Event Server uses IBM’s Streamed XML Transformation (XST). However. Click the XML Settings tab. Disable this option if you do not want InfoSphere CDC Event Server to distinguish between empty strings and a null value.3. Click Configuration → Subscriptions.

See also: 154 InfoSphere Change Data Capture Management Console: Administration Guide . 7. Right-click Edit Mapping Details. Click the Table Mappings view and select the table mapping. Click the XML Settings tab. You can select encodings based on character set requirements. 2. 8. Disable the Enable streamed transformation mode check box. Disable the Nullable XPath expression check box. Click the XML Settings tab. 3. Click Configuration → Datastores. Click the XML Settings tab. 2. Click Configuration → Subscriptions. Ensure you have created a subscription that uses the Event Server datastore as the target database. 4. Click Configuration → Subscriptions. 7. Ensure you are connected to an Event Server datastore. Right-click Edit Mapping Details. 6. Select the subscription that contains the table mapping to a message destination. Related concepts “Setting general runtime options” on page 153 Selecting a character encoding Select the encoding scheme you want InfoSphere CDC Event Server to use when saving a mapping. Ensure you have created a subscription that uses the Event Server datastore as the target database.5. Enable the Trim Text check box. You can also add your own character set to the list. Click the Table Mappings view and select the table mapping. Click Apply. InfoSphere CDC Event Server uses 8-bit UCS/Unicode Transformation Format (UTF-8). 6. 3. 6. Right-click Edit Mapping Details. 5. Related concepts “Setting general runtime options” on page 153 To disable InfoSphere CDC Event Server from differentiating between an empty string from a NULL value 1. Select the subscription that contains the table mapping to a message destination. 8. Click Apply. Related concepts “Setting general runtime options” on page 153 To disable streamed transformation mode 1. By default. Click Apply. 4. Click Configuration → Datastores. Ensure you are connected to an Event Server datastore. 5. 7. 8.

Click Apply. Ensure you have created a subscription that uses the Event Server datastore as the target database. Choose a character encoding from the Project File Encoding list. 6. Click the Table Mappings view and select the table mapping. Ensure you are connected to an Event Server datastore. 7. Click the XML Settings tab. Click Configuration → Subscriptions. 4. Select the subscription that contains the table mapping to a message destination. Click Configuration → Datastores. 8. type the name of the encoding in the box Related concepts “Selecting a character encoding” on page 154 Setting JMS message header properties 155 . 3. Right-click Edit Mapping Details.“To select a character encoding” To select a character encoding 1. 5. If you want to add your own character encoding. 2.

156 InfoSphere Change Data Capture Management Console: Administration Guide .

See also: “To map a source column to a target column” To map a source column to a target column 1. or if the data types between columns are not compatible. the Map Tables wizard may have left certain target columns unmapped if the column names between the source and target tables did not match. enable the Show Column Data Types check box. These target columns are mapped with an initial default value such as BLANK. NULL. 8. To view the data types of each column in a table. 5. In this section. Click Configuration → Subscriptions. Click the Column Mappings tab. 2. Drag and drop the source column to the Source area to map it to a target column. you can customize the kind of information you want to map to a target column and populate it with. Note: You can map source columns to target columns only if the data types between both are compatible. 4. InfoSphere CDC populates the target column with data from the source column. Click Apply. Click the Table Mappings view and select the table mapping. 6. Expand the Source Columns list and select a source column. You may see target columns that are not mapped to any source columns. you will learn: “Mapping source columns to target columns” “Mapping journal control fields to target columns” on page 158 “Mapping expressions to target columns” on page 158 “Mapping source and target columns automatically” on page 160 “Mapping initial values to target columns” on page 161 “Adding and mapping derived columns to target columns” on page 162 Mapping source columns to target columns Manually map any remaining target columns left by the Map Table wizard so that they are populated with data during replication activities. then most or all of your target columns are already mapped to source columns that have identical names and attributes.Mapping columns After mapping your tables using the Map Tables wizard. you can use the Column Mappings tab to customize what items you want to map to target columns in a subscription. and so on. However. © Copyright IBM Corp. 2008 157 . When you start replication on the subscription. 3. Right-click and select Edit Mapping Details. CURRENT DATE. For example. 7. using the Columns Mappings tab. If you have mapped your tables using any mapping type. Select the subscription.

These are available to you when you select LiveAudit as your mapping type. updates. When you start replication on the subscription. Click Apply. 8. Click the Table Mappings view and select the table mapping. 7. InfoSphere CDC translates the journal control field into system information and populates this information into the mapped target column during replication. Click the Column Mappings tab. then each time there is a change in your source table. If you decide to map a journal control field to a target column.Related concepts “Mapping source columns to target columns” on page 157 “Starting and ending replication on subscriptions” on page 197 Mapping journal control fields to target columns Journal control fields let you populate a target column with system information about the inserts. 6. or deletes taking place on your source tables. To capture this information in a target column. See also: “To map a journal control field to a target column” Related concepts “About journal control fields” on page 245 “Mapping using LiveAudit” on page 100 To map a journal control field to a target column 1. An expression such as %TOCHAR(OrderID. Journal control fields are especially useful when you want to audit the changes that are taking place in your source environment. 5. 4. InfoSphere CDC populates the target column with system information. For example. v Calls a stored procedure that you have configured in a user exit program. 6) would convert integer data to a string of six characters in the source column OrderID so that it is compatible with the target column that you want to populate. you can create an expression that: v Converts integer data on the source column to character data using the column function %TOCHAR. Right-click and select Edit Mapping Details. map the &USER journal control field to the appropriate target column. Mapping expressions to target columns Mapping expressions to a target column—Expressions are stored and evaluated on target columns. Click Configuration → Subscriptions. Select the subscription. Drag and drop the journal control field to Source area to map it to a target column. Expand the Journal Control Fields list and select a journal control field that is compatible with the data type of the target column. Related concepts “Mapping journal control fields to target columns” 3. For example. 2. You can specify an expression that contains a valid call to the %STPROC column 158 InfoSphere Change Data Capture Management Console: Administration Guide . you may want to audit the name of the user that inserts a row in a source table.

For example. 2. If you are calling a stored procedure that is not owned by the InfoSphere CDC user. Select the subscription. Right-click and select Edit Mapping Details. 8. Select the subscription. then you can map accumulation or deduction expressions to a target column. When you map tables for summarization. Click Configuration → Subscriptions. Expand the Expressions list and drag and dropNew Expression to the target column you want to map. Click Save to save the expression. 4. Drag and drop the source column from the list beside the target column to which you want to map. Related concepts “Mapping expressions to target columns” on page 158 To accumulate or deduct numeric data on a target column 1. Mapping accumulation and deduction expressions to a target column—If you have mapped your tables using Summarization in the Map Tables wizard. Build an expression. InfoSphere CDC evaluates the expression on the target column. Click the Table Mappings view and select the table mapping. 5. See also: “To map an expression to a target column” “To accumulate or deduct numeric data on a target column” Related concepts “Mapping to summarize data” on page 113 Related tasks “To configure a derived column or an expression that calls %STPROC (Oracle and Sybase)” on page 218 To map an expression to a target column 1. Mapping columns 159 . Click the Table Mappings view and select the table mapping. 2. if you have a target column such as REVENUE and you want the value in this column to increment each time a product gets sold in the SALESAMOUNT source column. 3. Click Apply. 3. Click the Column Mappings tab. 5.<stored procedure name>. 4. 6. This should be mapped for Summarization. Click the Column Mappings tab.manipulation function. When you start replication. You should see the expression mapped to the target column on the Column Mappings tab. 9. Click Configuration → Subscriptions. then you can map SALESAMOUNT to REVENUE. the target table is largely a repository of numerical data increments or decrements in response to source row-level operations transferred by refresh or mirroring activity. 7. Right-click and select Edit Mapping Details. you must provide the name in the form <schema>.

Click Configuration → Subscriptions. 3. map your source columns to target columns. Related concepts “Mapping expressions to target columns” on page 158 Mapping source and target columns automatically Use the Map Columns Automatically dialog box to customize how you want to map source and target columns. the source column in the list updates with a plus or minus sign. Depending on which source columns you want to summarize data. Depending on how you want to summarize data. If the number of columns in the target table is greater than the number of the columns in the source table.6. The Map Tables wizard cannot map a source column such as LOC to the target column LOCATION. 5. 9. Click Apply. then initial values are used for trailing columns in the target table. but because the column names did not match. the Map Tables wizard did not map them as you wanted. Click Auto Map. v Ordinal position—maps columns based on the order of columns in the source and target tables. Select the subscription. the second column in the target table is mapped to the second column in the source table. you may have wanted to map a particular target column to a source column. Expand the Summarization list and drag and drop eitherAccumulation or Deduction expressions on the source and target column mapping. When you start replication on the subscription. then trailing columns in the source table remain unmapped. Instead. Right-click and select Edit Mapping Details. Select the source column and clickOK. 7. Click the Table Mappings view and select the table mapping. 6. Enable one of the following mapping modes: v Original position—maps columns based on changes made on the Column Mapping tab before you opened the Map Columns Automatically dialog box. Click the Column Mappings tab. For example. You can also build an expression that summarizes data. 2. 160 InfoSphere Change Data Capture Management Console: Administration Guide . 4. If the number of columns in the source table is greater than the number of columns in the target table. See also: “To map columns automatically” Related concepts “Column Mappings tab” on page 7 To map columns automatically 1. InfoSphere CDC accumulates or deducts the summarized data in response to row-level operations occurring on the source table. 8. 7. You can only map by ordinal position provided the data types are compatible. you can map columns using a different mapping mode based on criteria such as ordinal position. The first column in the target table is mapped to the first column in the source table. and so on.

if a column in the source table is called EMPNAME. or if there is a greater number of target columns than source columns. 1. After you have mapped your tables using the Map Tables wizard. 8. there may be target columns that remain unmapped. This is useful when you are working on an iSeries database platform and you need to map the source table names to target columns. and click the Initial Value column. 7.v Name to name—maps columns based on matching column names. InfoSphere CDC populates the target columns using the mapping mode you set. Mapping columns 161 . v Name to description—maps columns based on matching target column names in source column descriptions. Click OK. See also: “To define an initial value for a target column” To define an initial value for a target column Click Configuration → Subscriptions. Enable one of the following: v Constant—Populates the target column with a constant. to open the Set Initial Value dialog box. If you select this option. Select the subscription. When you start replication on the subscription. 6. Click 8. then this column is automatically mapped to the column in the target table called EMPNAME. For these target columns. Place your cursor beside the target column that you want to populate with an initial value. Right-click and select Edit Mapping Details. The data type of the target column must be character or a binary data type. 2. For example. you can define an initial value such as a constant to populate the target column. The data type of the target column must be nullable. 5. Related concepts “Mapping source and target columns automatically” on page 160 Mapping initial values to target columns Use the Column Mappings tab to map initial values to unmapped target columns. Target columns can remain unmapped if the source and target column names do not match. Click Apply. The constant is limited to 25 characters. v Blank—Populates the target column with a blank character. 4. you need to type a constant in the Constant box. Click the Table Mappings view and select the table mapping. 3. or use the default value of the target column as specified in your RDBMS. 9. Click the Column Mappings tab. You should see your target columns mapped in the mode you selected on the Column Mappings tab. v Null—Populates the target column with a null value. You should see an unmapped target columns.

You can then map the source table using one-to-many consolidation. v Call a stored procedure that you have configured in a user exit program. v Database Default—Populates the target column with the default specified in your RDBMS. When you start replication on the subscription. and then store the result in a derived column. You can also create a derived column to: v Extract characters from string data by using functions such as %SUBSTRING. InfoSphere CDC evaluates the expression on the source system and sends the results to the target column. You can specify an expression that contains a valid call to the %STPROC column manipulation function. you must provide the name in the form <schema>.v Zero—Populates the target column with a value of zero. Related concepts “Mapping initial values to target columns” on page 161 Adding and mapping derived columns to target columns Derived columns let you move the processing of an expression from the target system to the source system.1. then both the before image and the after image of an update operation are populated with the same current date. v Retrieve information from a lookup table using %GETCOL. 9. However. it may become necessary in your environment to move the processing of this expression to the source system. you can extract a person’s initial from a column named FIRSTNAME. v Current Date—Populates the target column with the current date. When you start replication. The data type of the target column must be numeric. You can then map the derived column named FULLNAME to the target column named FULLNAME. InfoSphere CDC evaluates the expression on the target system and stores the results in the FULLNAME target column. Click OK. InfoSphere CDC populates this target column with the initial value you specified. If your subscription uses InfoSphere CDC for z/OS as a target datastore. FIRSTNAME and LASTNAME.1). 162 InfoSphere Change Data Capture Management Console: Administration Guide . by using the expression SUBSTRING(FIRSTNAME. The data type of the target column must be datetime. When you start replication. the value that populates this column is determined from the column defaults defined in your RDBMS. Click Apply. Whenever a row gets inserted into the target table. and mapped this expression to a target column named called FULLNAME. For example. you may have already defined an expression that concatenates the values of two source columns. you can build a derived column on the source table named FULLNAME and define an expression that concatenates the values of the two source columns FIRSTNAME and LASTNAME. 10.<stored procedure name>. You can create a derived column on the source table using %GETCOL so that you can retrieve data from a lookup table. If you are calling a stored procedure that is not owned by the InfoSphere CDC user. For example. Using this same example. and you have mapped your tables using the LiveAudit mapping type.

Select this option when you want InfoSphere CDC to evaluate the expression in the derived column for both the before and after images of the source table. Click Configuration → Subscriptions. This maintains database integrity. For performance reasons. Option After Image Only Before and After Images 12. Click OK to return to the Define Derived Column dialog box. Select the subscription. 16. 4. 8. 15. Click Editor to build the expression for the derived column. 2. Type a name for the derived column in the Name box. Expand the Source Columns list. You can map this derived column to a target column so that InfoSphere CDC can populate the results of the derived column in the target column.In each of these scenarios. Select a data type of the result from the Data Type list. or when you are auditing so that you can audit the full before image. Type the maximum length for the returned value in the Length box. 10. 7. 5. Click OK. evaluate the After Image Only value. 14. you can then map the derived column to the appropriate target column. Type a brief description of the derived column in the Description box. Right-click and select Edit Mapping Details. Click the Table Mappings view and select the table mapping. which requires the before image to recognize conflicts. 3. Mapping columns 163 . 6. InfoSphere CDC will evaluate the expression on the source table and send the results to the target column. You also need to select this evaluation frequency if the target column to which you mapped the derived column is a primary key column. Click Verify to verify the syntax of the expression. Select an evaluation frequency: Description Select this option when you want InfoSphere CDC to evaluate the expression in the derived column for the after image of the source table. double-click New Derived Column. 11. Click Apply. 9. 13. An evaluation frequency of Before and After Images (*BTH) is only necessary when you are performing conflict detection and resolution. This name must be unique. You should see the new derived column listed in the Source Columns list of the Column Mappings tab. Click the Column Mappings tab. See also: “To add a derived column” “To map a derived column to a target column” on page 164 “To modify a derived column” on page 164 “To delete a derived column” on page 165 To add a derived column 1.

select and right-click on an existing derived column and click Modify Derived Column. 3. Click Configuration → Subscriptions. 5. 9. 6. Click Verify to ensure the expression is valid. Right-click and select Edit Mapping Details. 7. Select the subscription. v Since the derived expression is evaluated each time a change is replicated to the target table. Click Apply to save your mapping. v Derived columns and the expressions you build for them are evaluated on source tables. Related concepts “Adding and mapping derived columns to target columns” on page 162 Related tasks “To add a derived column” on page 163 “To modify a derived column” “To delete a derived column” on page 165 To modify a derived column 1. 4. 2. the complexity of the expression can affect overall performance. Click the Column Mappings tab. 4. Expand the Source Columns list. Click Configuration → Subscriptions. InfoSphere CDC populates the target column with the results stored in the derived column. When you start replication on the subscription.Notes: v If you already have a source column in your RDBMS on which you want to base the properties of your derived column. 6. Expand the Source Columns list. To map a derived column to a target column 1. click Copy Column and select the column from the list of tables. InfoSphere CDC populates the target column with the results stored in the derived column. Right-click and select Edit Mapping Details. 3. Click Apply. length. Select the subscription. When you start replication on the subscription. Click the Table Mappings view and select the table mapping. 7. and any precision) are used as the properties of your derived column. Related concepts “Adding and mapping derived columns to target columns” on page 162 Related tasks “To add a derived column” on page 163 “To delete a derived column” on page 165 164 InfoSphere Change Data Capture Management Console: Administration Guide . The properties of this column (the data type. 2. Click the Column Mappings tab. Make the necessary changes and click OK. 5. Click the Table Mappings view and select the table mapping. and drag and drop the derived column and map it to the appropriate target column. 8.

6. 7. Select the subscription. Click the Column Mappings tab. 4. 5. 3. select and right-click on an existing derived column and click Delete Derived Column. Related concepts “Adding and mapping derived columns to target columns” on page 162 Related tasks 1.To delete a derived column Click Configuration → Subscriptions. Expand the Source Columns list. Right-click and select Edit Mapping Details. Click Apply. “To end replication” on page 199 “To add a derived column” on page 163 “To modify a derived column” on page 164 Mapping columns 165 . 2. Click the Table Mappings view and select the table mapping.

166 InfoSphere Change Data Capture Management Console: Administration Guide .

6. you need to build a row-filtering expression. The expression must return a boolean result. 4. 7. 1. 8. basic numeric operators.000. Click the Table Mappings view and select the table mapping. you would need to define a row-filtering expression (SALARY > 48000). You may only want to replicate those rows to the target table for those employees that have a salary greater than $48.2) > 50 v PRODUCTPRICE * (1 + TAX) > 20000 See also: “To filter rows” To filter rows Click Configuration → Subscriptions. Click Verify to check the syntax of the expression and click OK to return to the Filtering tab. 3. In this section. The following are examples of valid row-filtering expressions: v (SALES < 10000) OR (SALES > 90000) v ((AIRPORT = ’JFK’) OR (AIRPORT = ’LAX’)) v %IF(COUNTRY = ’US’. © Copyright IBM Corp. 2. You can use column manipulation functions. v Omit rows that match the expression—Select this option if you want InfoSphere CDC to select for replication all rows except those that satisfy your row-filtering expression.Filtering rows and columns Use theFiltering tab to include or exclude rows or columns for replication. you may have a source column such as SALARY that maintains the salary for each employee in your organization. and SQL SELECT WHERE clauses in your row-filtering expressions. PRODUCTPRICE. For example. PRODUCTPRICE *1. Select the subscription. In this scenario. All row-filtering expressions that you define must return a boolean result. Click Editor and build a row-filtering expression. Click the Filtering tab. 5. Choose one of the following options in the Row-filtering area: v Select rows that match the expression—Select this option if you want InfoSphere CDC to replicate the source rows that satisfy your row-filtering expression. Right-click and select Edit Mapping Details. you will learn: “Filtering rows” “Selecting critical columns to filter rows” on page 168 “Filtering columns” on page 168 Filtering rows In order to include or exclude particular rows for replication. 2008 167 .

When you select a column as critical. you can control the updates that InfoSphere CDC replicates using the select critical column feature. InfoSphere CDC replicates inserts. Select the subscription. Right-click and select Edit Mapping Details. 4. Related reference “Critical Column Filtering” on page 452 Filtering columns By default. InfoSphere CDC replicates all mapped source columns to the target table.9. If you are using InfoSphere CDC for AS/400 on the source. See also: “To select critical columns” To select critical columns 1. In this scenario. If there is a source column you want to exclude for replication. InfoSphere CDC excludes this column for replication. Click the Filtering tab. and deletes to the target table during replication. 6. Related concepts “Filtering rows” on page 167 Selecting critical columns to filter rows When you start replication on the subscription. InfoSphere CDC replicates the row based on the criteria you specified in your row-filtering expression. However. Instead of receiving every update made to the source table. InfoSphere CDC will only replicate this row when there are updates made to the Customer_Account_Balance column. 2. you may only want to receive the row when the customer account balance is updated. See also: “To filter columns” on page 169 168 InfoSphere Change Data Capture Management Console: Administration Guide . 3. 5. then you need to enable the Critical Column Filtering system parameter to *YES. you would select the column (Customer_Account_Balance) as a critical column. Click Configuration → Subscriptions. Click Apply. By default. When you start replication on the subscription. Click the Table Mappings view and select the table mapping. Excluding source columns for replication may become necessary if the column contains confidential information that you do not want the target to receive. For example. Select the columns you want to set as critical in theCritical check box. updates. you may have a source table that maintains customer account information. then you can clear it on the Filtering tab. InfoSphere CDC only replicates update operations when any critical column has changed value.

2. Click Apply. 4. If you do not want InfoSphere CDC to replicate data from a source columns. 5. When you start replication on the subscription. You need to unmap the source column on the Column Mappings tab. Right-click and select Edit Mapping Details. Click the Table Mappings view and select the table mapping. Note: You cannot clear a source columns from replication if you have already mapped them to target columns. InfoSphere CDC excludes this column for replication. Select the subscription. 6. Click the Filtering tab. 3. Source columns that you can clear for replication are selected with a green check mark in the Replicate column.To filter columns Click Configuration → Subscriptions. 1. 7. Related concepts “Filtering columns” on page 168 Filtering rows and columns 169 . then clear the green checkmark for that column.

170 InfoSphere Change Data Capture Management Console: Administration Guide .

it is best to use an appropriate column function or write a user exit program to convert this kind of information. then you can only add a data translation for source columns that are mapped to target staging columns. You can add a data translation only if the target column is already mapped to a source column. If you use fractional data to represent whole numbers (for example. and delete a data translation. 2008 171 . You cannot add data-to-data translations for target columns with large object (LOB) data types. such as translating product codes to their descriptions. If you need to convert numerical or date information (where the number of possible data types are limitless). Toronto.01. However. You can also import and export data translations.0). and LON and want these codes translated to a target column in their full names (New York. When you add a data translation and start replication. In this section. InfoSphere CDC supports translations to and/or from 1 and 100.Setting data translations on column mappings Use the Translation tab to add. and London). TO. InfoSphere CDC does not support translations that convert to and/or from fractional data. you will learn: “Setting data translations” “Importing and exporting data translations” on page 173 Setting data translations Management Console lets you translate specific data in your source columns to new data to mapped target columns. You cannot set a data translation for source columns that are mapped to XML elements and attributes. 1. but does not support translations to and/or from 1.01 and 100. Before adding a data translation. By specifying data translations. then InfoSphere CDC translates these whole numbers if you have defined corresponding integer translations (for 1 and 100 respectively). you may have a source column called CITY that has data such as NY. you can convert specific data values during data replication. If you have created a subscription that targets a InfoSphere CDC Event Server datastore. consider the following: v You can add a data translation for columns that contain integer data. v v v v See also: “To add a data translation” on page 172 “To modify a data translation” on page 172 “To delete a data translation” on page 173 © Copyright IBM Corp. modify. For example.0 and 100. InfoSphere CDC converts data from the source columns into the new data you set for a mapped target column. For example. You can define data translations for different data types and should only be used when there is a limited number of translations.

8. 5. and populates the mapped target column with the converted value. 10. ClickAdd. Click OK to add the translation to your list of data translations. Click the Translation tab. 6. Select the subscription. 3. Select an existing translation that you have added and clickModify. 4. Right-click and select Edit Mapping Details. 9. 6. Click the Table Mappings view and select the table mapping. 4. and populates the mapped target column with the converted value. Click Configuration → Subscriptions. 2. 7. Type the data you want to translate in the From box. 11. ClickAdd.Related tasks “To add a data translation” “To modify a data translation” “To delete a data translation” on page 173 “To import a data translation” on page 173 “To export a data translation” on page 174 To add a data translation 1. Right-click and select Edit Mapping Details. Related concepts “Mapping tables” on page 91 “Starting and ending replication on subscriptions” on page 197 To modify a data translation 1. Select the subscription. 7. InfoSphere CDC converts the value in the source column to the value you specified. 12. Type the value to which you want to translate. Click Configuration → Subscriptions. When you start replication on the subscription. Select a mapped source and target column. InfoSphere CDC converts the value in the source column to the value you specified. If you want to translate to a NULL value. When you start replication on the subscription. Click the Translation tab. then check the Translate from NULL box. If you want to translate a NULL data type. 13. in the To Value box. check the Translate to NULL box. Click the Table Mappings view and select the table mapping. If you want to add another translation. Make the necessary changes and clickOK. 5. Related concepts “Mapping tables” on page 91 “Starting and ending replication on subscriptions” on page 197 172 InfoSphere Change Data Capture Management Console: Administration Guide . 2. 3.

Right-click and select Edit Mapping Details. 2. Click the Table Mappings view and select the table mapping. any existing translations are replaced with the imported translations. 9. Select the subscription. When you import a data translation into Management Console. any existing translations are replaced with the imported translations. 5. 2. Locate the CSV file and clickOK. 6. 8. Click the Table Mappings view and select the table mapping. select the translation and clickApply. you can import the data translation and apply it for each column mapping. Click Configuration → Subscriptions. Notes: v If you want to apply the data translation to the column mapping. See also: “To import a data translation” “To export a data translation” on page 174 To import a data translation 1. 6. Select an existing data translation and ClickDelete. Select a mapped source and target column. Related concepts “Mapping tables” on page 91 “Starting and ending replication on subscriptions” on page 197 Importing and exporting data translations You can import and export data translations for mapped source and target columns. ClickImport. Select the subscription. Related concepts “Importing and exporting data translations” Related tasks “To export a data translation” on page 174 Setting data translations on column mappings 173 . 7. 5. v When you import a data translation into Management Console. Ensure you have exported a data translation for this mapping. Right-click and select Edit Mapping Details. 3. Click the Translation tab. Instead of manually specifying the translation for each column mapping. 4. It may be necessary to export a data translation when you know of multiple column mappings that require the same translation. Click Configuration → Subscriptions. Click the Translation tab. 4.To delete a data translation 1. 3.

Save the data translation as a CSV file and clickOK. Select the subscription. 6. Click Export. 3.To export a data translation 1. 9. Right-click and select Edit Mapping Details. Click the Table Mappings view and select the table mapping. Click Configuration → Subscriptions. Ensure you have added a data translation for this mapping. 7. 4. 5. Related concepts “Importing and exporting data translations” on page 173 Related tasks “To import a data translation” on page 173 174 InfoSphere Change Data Capture Management Console: Administration Guide . Click the Translation tab. 2. Select a mapped source and target column. 8.

2008 175 . InfoSphere CDC converts the character set. Related concepts “Converting multibyte character sets” “Handling Unicode character encodings” on page 176 “Resolving conflicts for source or target wins” on page 189 “Mapping using Adaptive Apply” on page 110 Converting multibyte character sets Use the Translation tab to set conversion on multibyte character sets. it is important to note that not all characters will convert with equivalent characters. you can specify how InfoSphere CDC handles Unicode character encodings during replication. During replication. If you are replicating data for an international market. For other InfoSphere CDC products. Scenario 1: Converting character sets between iSeries and DB2 UDB In this scenario. you may have a configuration in which data needs to be converted from a national language character set to Unicode. the character set on the source is in a character set such as Chinese. Multibyte character sets (MBCSs) are an alternative to Unicode for supporting character sets. you will learn: “Setting multibyte conversions—common scenarios” “Converting multibyte character sets” “Handling Unicode character encodings” on page 176 Setting multibyte conversions—common scenarios Use the following scenarios as guidelines when you want to perform encoding conversions. Scenario 2: Converting from national language character set to Unicode In this scenario. consider using Unicode or MBCS. In this section. and the target that contains the other character set is a Windows system. Note: Because of the encoding differences between platforms. For example. and the character set on the target to which you want to convert is Unicode. double. then you can specify how InfoSphere CDC converts character sets on source columns during replication. InfoSphere CDC supports single. © Copyright IBM Corp. and Unicode. multibyte national language character sets.Setting multibyte and Unicode character set conversions If you have installed InfoSphere CDC Version 6. but the source that contains the character set is an iSeries system. you may have a configuration with consistent character sets.0 or higher. you may want to convert from Simplified Chinese on your source to Simplified Chinese on the target. such as Japanese and Chinese. For example. that cannot be represented in a single byte.

Click Apply. double-byte. For example. you may be replicating your data to an organization that stores their data in the Unicode version of Chinese characters. you need to set the Unicode Handling system parameter to one of the following: v CHAR—InfoSphere CDC treats all data in Unicode columns as single-byte characters. If you want to add more character sets and encodings. Click the Table Mappings view and select the table mapping. Click the Translation tab. 1. 5. Select the character encoding to which you want to convert from the Target list. then you need to add it to the CSV (comma separated variable) template. 6. 8. Use this setting when Unicode columns contain single-byte character data. When you start replication on the subscription. See also: “To convert multibyte character sets” To convert multibyte character sets Click Configuration → Subscriptions. If you want to add more character sets and encodings. Management Console provides standard character sets and encodings. if your data is stored in Chinese characters. For example. Right-click and select Edit Mapping Details. then you can select from either Traditional or Simplified encodings. If your source column contains character data stored in multibyte. 7. Conversion of multibyte character sets is supported on InfoSphere CDC Version 6. v NOCHANGE—InfoSphere CDC treats all data in Unicode columns as a continuous bit stream. InfoSphere CDC converts the character encoding in the source column to the encoding you specified and populates the mapped target column with data in the new encoding.Management Console provides standard character sets and encodings. Select the source column that supports a multibyte character set encoding. This enables the Encoding Conversion area. 4. Before you can set how InfoSphere CDC handles data. 3. or Unicode character set.0 or higher. Related concepts “Converting multibyte character sets” on page 175 Handling Unicode character encodings Use the Translation tab to set how InfoSphere CDC handles data from the source column. 2. Select the character encoding of the data stored in your source column from the Source list. 9. Use this encoding when Unicode columns contain 176 InfoSphere Change Data Capture Management Console: Administration Guide . then you need to add it to the CSV template. then you can indicate how InfoSphere CDC handles data from this source column when replicating to a target column. Select the subscription.

Select Character Handling from the Source list.non-single-byte character data. InfoSphere CDC treats all data in Unicode columns as a continuous bit stream. See also: “To set handling for Unicode character encodings” To set handling for Unicode character encodings 1. Click the Table Mappings view and select the table mapping. Use this encoding when Unicode columns contain single-byte character data. 3. NOCHANGE ensures that InfoSphere CDC handles non-single-byte character data in the same way as previous InfoSphere CDC releases. Select the source column that supports character handling from the Source Columns list. 2. see “Unicode Handling” on page 444. Select the subscription. This enables the Encoding Conversion area. Click Configuration → Subscriptions. Depending on the platform on which you have installed InfoSphere CDC. 7. 11. 6. set one of the following system parameters: v For InfoSphere CDC for AS/400. v NOCHANGE—Select this if you have set the system parameter Unicode Handling to NO CHANGE. Click Apply. 9. Use this encoding when Unicode columns contain non-single-byte character data. 4. InfoSphere CDC treats all data in Unicode columns as single-byte characters. see “Unicode Handling” on page 325. see “UNICODE_HANDLING” on page 364. Related concepts “Handling Unicode character encodings” on page 176 Related reference “Unicode Handling” on page 444 Setting multibyte and Unicode character set conversions 177 . 5. Right-click and select Edit Mapping Details. If you have set the system parameter Unicode Handling to use the system default method to handle the character set. select from one of the following: v CHAR—Select this if you have set the system parameter Unicode Handling to CHAR. Click the Translation tab. NOCHANGE ensures that InfoSphere CDC handles non-single-byte character data in the same way as previous InfoSphere CDC releases. v For InfoSphere CDC for Oracle. 8. 10. If you want to use an encoding for the character set. select System Default. v For InfoSphere CDC for Microsoft SQL Server.

178 InfoSphere Change Data Capture Management Console: Administration Guide .

You may decide to suppress row-level operations from replicating to a target table if you have a target-side application on which you do not want any updates or deletes to occur. or a delete from replicating to the target table. Click Apply. 7. update. Click the Operation tab. 2. v Do not update—prevents InfoSphere CDC from applying an update to a mapped target table. This table mapping should be configured for Standard or Adaptive Apply replication. when you start replication. Click the Table Mappings view and select the table mapping. or delete” Related concepts “Mapping using standard replication” on page 91 “Mapping using Adaptive Apply” on page 110 To suppress an insert. 5. 4. Right-click and select Edit Mapping Details. Choose one or more of the following: v Do not insert—prevents InfoSphere CDC from applying an insert to a mapped target table. For example. You can suppress operations if you mapped tables using either Standard or Adaptive Apply replication. or delete 1. update. © Copyright IBM Corp. if your target-side application is a data warehouse. Click Configuration → Subscriptions. 2008 179 . Depending on your selections. v Do not delete—prevents InfoSphere CDC from applying a delete to a mapped target table. update. See also: “To suppress an insert. 3.Controlling row operations Management Console lets you set how a target table responds to changes made on the source table. InfoSphere CDC does not apply the row operation. Select the subscription. you will learn: “Suppressing the apply of row operations” “Preventing the audit of row operations” on page 180 “Detecting conflicts on row operations” on page 181 “Enabling the apply of soft deletes (InfoSphere CDC for Oracle)” on page 182 Suppressing the apply of row operations Use the Operations tab to suppress an insert. In this section. you may only want inserts to occur on your data warehouse tables or other third party applications. 6.

Click the Operation tab. Click the Table Mappings view and select the table mapping. This is especially useful if you want to reduce the size of your audit trails for recovery purposes. when you start replication. 2. 4. Click Configuration → Subscriptions. Depending on your selections. 6. v Do not update—prevents InfoSphere CDC from auditing an update to a mapped target table. If you have mapped your tables using LiveAudit. Click Configuration → Subscriptions. InfoSphere CDC does not audit the row operation. Select the subscription. 3. This table mapping should be configured for Standard or LiveAudit replication. Click the Table Mappings view and select the table mapping. 3. Related concepts “Preventing the audit of row operations” To audit only the after image 1. 5. 4. 2. Select Audit After Image from the On Update list. 6. See also: “To prevent row operations from being audited” “To audit only the after image” Related concepts “Mapping using LiveAudit” on page 100 To prevent row operations from being audited 1. 180 InfoSphere Change Data Capture Management Console: Administration Guide .Related concepts “Suppressing the apply of row operations” on page 179 Preventing the audit of row operations Use the Operations tab to prevent InfoSphere CDC from the auditing of row operations. Click the Operation tab. Click Apply. Choose one or more of the following: v Do not insert—prevents InfoSphere CDC from auditing an insert to a mapped target table. then InfoSphere CDC audits row level operations taking place on the source. 7. Right-click and select Edit Mapping Details. Click Apply. v Do not delete—prevents InfoSphere CDC from auditing a delete to a mapped target table. This table mapping should be configured for Standard or LiveAudit replication. You can also restrict auditing so that your target table only audits the after image when there is a change to a row in the source table. 7. Select the subscription. 5. Right-click and select Edit Mapping Details.

or delete and it is not the same as the row level operation applied to a target table. InfoSphere CDC generates a message. but there is no responding row-level operation to apply to the target. Related concepts “Preventing the audit of row operations” on page 180 Detecting conflicts on row operations Use the Operations tab to set conflict detection between row operations on the source and target. Click Apply. update or a delete operation. Right-click and select Edit Mapping Details. Choose one or more of the following: v On Insert—generates a message when there is an insert on the source. 5. else insert and check the Log changed database action box. Click the Table Mappings view and select the table mapping. v On Update—generates a message when there is an update on the source. but the resulting row-level operation on the target table is an update because that row already exists in the target table. 3. else insert and check the Log changed database action box. If you have mapped your tables using Adaptive Apply . Select the subscription. See also: “To detect conflicts on row operations” Related concepts “Resolving conflicts for source or target wins” on page 189 “Mapping using Adaptive Apply” on page 110 To detect conflicts on row operations 1. Related concepts “Resolving conflicts for source or target wins” on page 189 “Detecting conflicts on row operations” Controlling row operations 181 . 4.When you start replication. You can view these messages in the Event Log view. but the responding row-level operation on the target is an insert. Click the Operation tab. 7. v On Delete—generates a messages when there is a delete on the source. This table mapping should be configured for Standard or Adaptive Apply replication. For example. then InfoSphere CDC forces the target table into consistency with row-level operations taking place on the source table. Select Update Row if Exists. you can set detection on row-level conflicts. when InfoSphere CDC applies an insert. Click Configuration → Subscriptions. the target table only audits the source table when there is a change made to the after image. then this creates a conflict. To ensure that the target table is always consistent with the source table. Select Update Row if Exists. but the responding row-level operation on the target is an update. However. 2. 6. When there is a conflict against an insert. Select Delete Row if Exists and check the Log changed database action box. you may have inserted a row in the source table. update.

Click Configuration → Subscriptions. This table mapping should be configured for Standard or Adaptive Apply replication. Choose Delete Row. v DM_ADAPTIVE_APPLY_<SCHEMA>. See also: “To enable InfoSphere CDC for Oracle to apply a soft delete” To enable InfoSphere CDC for Oracle to apply a soft delete 1. then you can enable InfoSphere CDC for Oracle to apply a soft delete on the target table. 8. Depending on whether you want InfoSphere CDC for Oracle to apply the soft delete to all mapped target tables or to apply the soft delete on a specific target table in the subscription. 5. 6. 7. InfoSphere CDC either: v updates a row on the target table if the row exists. Click the Table Mappings view and select the table mapping. Related reference “DM_ADAPTIVE_APPLY_SOFT_DELETES” on page 359 “DM_ADAPTIVE_APPLY_<SCHEMA>. or v inserts a row on the target table if it does not exist. Click Apply. 2. the target table will contain: v the before image of the row that was deleted and v the journal entry type Delete. When InfoSphere CDC applies the soft delete.<TABLENAME>—InfoSphere CDC for Oracle applies a soft delete on a specific target table mapped using Adaptive Apply in a subscription. Select the subscription. Right-click and select Edit Mapping Details. Ensure you have set either the DM_ADAPTIVE_APPLY_SOFT_DELETES system parameter or the DM_ADAPTIVE_APPLY_<SCHEMA>. 4. 3. If you have mapped your target tables using Adaptive Apply.Enabling the apply of soft deletes (InfoSphere CDC for Oracle) You can introduce a flag that audits the current state of an existing target table which indicates that a row has been deleted (this is called a soft delete) instead of actually deleting the row (a hard delete). Click the Operation tab. you must enable one of the following system parameters: v DM_ADAPTIVE_APPLY_SOFT_DELETES—InfoSphere CDC for Oracle applies a soft delete on all target tables mapped using Adaptive Apply in a subscription.<TABLENAME>” on page 360 182 InfoSphere Change Data Capture Management Console: Administration Guide . This means that when there is a delete on the source table.<TABLENAME> system parameter to ON. if exists from the On Delete list.

InfoSphere CDC does not delete the rows in the target table. or Consolidation. 5. In this section. select Do Not Delete. 2008 183 . See also: “To keep all rows on a refresh” “To delete all rows on a refresh” on page 184 “To audit rows on a refresh” on page 184 To keep all rows on a refresh 1.Controlling table operations By default. Click Configuration → Subscriptions. Also. 4. Adaptive Apply. You can do this if you have mapped your tables using one of Standard. Click the Operation tab. Summarization. Click Apply. From the On Clear/Truncate list. 3. When you start a refresh on a table mapping. 2. Right-click and select Edit Mapping Details. 7. Click the Table Mappings view and select the table mapping. You can control this so that InfoSphere CDC preserves all or some of the rows. Select the subscription. 6. if you have mapped your tables using LiveAudit. you will learn: “Controlling the apply of refresh operations” “Specifying SQL to control refresh operations” on page 184 Controlling the apply of refresh operations Use the Operations tab to control how InfoSphere CDC applies table-level clear or refresh operations to a target table. or Summarization. InfoSphere CDC truncates the target table in response to a table-level clear or refresh operation. Adaptive Apply. Related concepts “Mapping using standard replication” on page 91 “Mapping using LiveAudit” on page 100 “Mapping using Adaptive Apply” on page 110 “Mapping to summarize data” on page 113 “Starting a refresh on a subscription” on page 198 “Controlling the apply of refresh operations” © Copyright IBM Corp. then you can specify that InfoSphere CDC provide an audit trail each time there is an table-level clear or refresh operation applied to the target table. This should be mapped for Standard.

3. 2. Click Apply. Select the subscription. 184 InfoSphere Change Data Capture Management Console: Administration Guide . Right-click and select Edit Mapping Details. 5. From the On Clear/Truncate list. 3. This should be mapped for LiveAudit. 7. InfoSphere CDC deletes all the rows in the table in response to a table clear or refresh operation. Click Apply. Select the subscription. Click the Table Mappings view and select the table mapping. select Delete All. 7. Adaptive Apply. From the On Clear/Truncate list. 6. 4. Click the Table Mappings view and select the table mapping. Use the Operation tab to specify a SQL WHERE clause that restricts the rows you want InfoSphere CDC to delete in response to a table clear or refresh operation. 5. you may want to use the WHERE clause to delete rows from the supplier table. InfoSphere CDC only deletes or truncates the rows for which the condition is true. Click Configuration → Subscriptions. 6. 4. Note: When you start a refresh on the table mapping. Related concepts “Mapping using standard replication” on page 91 “Mapping using LiveAudit” on page 100 “Mapping using Adaptive Apply” on page 110 “Mapping to summarize data” on page 113 “Starting a refresh on a subscription” on page 198 Specifying SQL to control refresh operations By default. or Summarization. Click the Operation tab. InfoSphere CDC deletes all rows in the target table in response to a table-level clear or refresh operation. InfoSphere CDC audits the table-level clear or refresh operations applied to the target table. select Audit. The SQL statement SupplierName= ’IBM’ would delete all rows from the supplier table where the SupplierName is IBM. This should be mapped for Standard.To delete all rows on a refresh 1. Click Configuration → Subscriptions. Right-click and select Edit Mapping Details. 2. For example. Click the Operation tab. Note: When you start a refresh on the table mapping. Related concepts “Mapping using standard replication” on page 91 “Mapping using Adaptive Apply” on page 110 “Mapping to summarize data” on page 113 “Starting a refresh on a subscription” on page 198 To audit rows on a refresh 1.

v You cannot reference LOB columns in delete WHERE clauses. v If your delete WHERE clause references a character column.You can also specify additional SQL statements that execute after InfoSphere CDC applies a table refresh or truncate/clear operation to the target table. Click the Table Mappings view and select the table mapping. 3. Controlling table operations 185 . Click Configuration → Subscriptions. If you have installed InfoSphere CDC for DB2 UDB. v SQL statements must be 4. v No support for logical branching and iteration. you need to run the DMSQL command to enable the Additional SQL feature in Management Console. then you need to set the keyword ALLOWSQL to YES to enable theAdditional SQL feature in Management Console.) in the string. For example. the specified value must be enclosed in single quotes. 2. see Section 4. If a character string in a SQL statement contains a semi-colon. see InfoSphere CDC for DB2 UDB End-User Documentation. or column name that contains spaces. to reference the table name ″EMP NY″. then you must enclose the name in square brackets.3 Modifying DBMS LOAD Configuration Control Statements in the InfoSphere CDC for z/OS End-User Documentation. 5. Click the Operation tab. table. Select the subscription. See also: “To specify additional SQL after a refresh” “To delete selected rows on a refresh” on page 186 To specify additional SQL after a refresh 1. then you need to create a metadata table to enable the Additional SQL feature in Management Console. MGR = ’Anna Kim’. For all InfoSphere CDC products (except for InfoSphere CDC for z/OS and InfoSphere CDC for DB2 UDB). Before issuing SQL statements in Management Console. Right-click and select Edit Mapping Details. For more information. UPDATE. and DELETE statements. For example. consider the following: v If you are referencing a database. For more information. do not press the Enter key to break the statements over more than one line. The text will feed automatically to the next line. see the commands section of the appropriate InfoSphere CDC End-User Documentation for your InfoSphere CDC product. v Management Console does not verify SQL statements for syntactical correctness. For more information about this keyword. If you specify SQL statements that do not fit on one line. you must enter it as [EMP NY]. v Separate multiple SQL statements by semi-colons (. v Specify only SQL INSERT.. 4. If you have installed InfoSphere CDC for z/OS.000 bytes or less in length. The target DBMS verifies statements during replication. You can add this keyword to the TSDDBMxx Configuration Control data set member. v The database running on the target server must recognize the syntax of the SQL statements. specify two semi-colons consecutively (.).

Click the Table Mappings view and select the table mapping. InfoSphere CDC either continues or ends data replication in response to the error. Click OK to save your changes. 7. Click the Operation tab. depending on the system parameters you have set. select Delete Selected Rows. Related concepts “Specifying SQL to control refresh operations” on page 184 “Starting a refresh on a subscription” on page 198 186 InfoSphere Change Data Capture Management Console: Administration Guide . 8. Also. Click Additional SQL. Note: If InfoSphere CDC encounters an error during execution of a SQL statement. 3. then type SQL statement in the SQL Immediately After Truncate box. Right-click and select Edit Mapping Details. 10. Click Apply to apply the SQL WHERE clause to your subscription. From the On Clear/Truncate list. 4. Click Editor to specify a SQL WHERE clause for the selected rows. 9. 11. select Delete Selected Rows. Click Configuration → Subscriptions. If you want InfoSphere CDC to execute SQL after a refresh operation. Select the subscription. 2.6. 7. Note: When you start a refresh on the table mapping. 6. it ignores all remaining statements. Click Verify to make sure the SQL WHERE clause is valid and click OK. InfoSphere CDC deletes only those rows for which you have specified a SQL statement. 8. 5. From the On Clear/Truncate list. 9. 10. then type SQL in the SQL Immediately After Refresh box. Click Apply. If you want InfoSphere CDC to execute SQL after a truncate operation. Related concepts “Specifying SQL to control refresh operations” on page 184 Related tasks “To delete selected rows on a refresh” To delete selected rows on a refresh 1. Expand the Target Columns list and select the target columns on which you want to restrict deletions.

4. If you have installed InfoSphere CDC for AS/400 on your source system and want to replicate a multi-member source table to a single-member target table. Member Identifiers is only enabled if you have mapped an iSeries multi-member source table to a single-member target table on any platform. but the members are uniquely named and have unique data. Type the name of the member for which you want to add an identifier in the Member Name box. the member data on the target is overwritten by data from another member. © Copyright IBM Corp. 6. 3. InfoSphere CDC requires an identifier so that it does not truncate rows when it applies a refresh to a single-member target table. Click Member Identifiers. you need to create a column on the target table that can maintain the identifiers for the members in your source table. Click Verify to make sure the expression is valid and click OK. In this section. Before adding a member identifier. Click Configuration → Subscriptions. If you do not specify an identifier for your multi-member source table. 7. After creating the target column. 10. then each time InfoSphere CDC applies a refresh to the single-member target. you will learn: “Setting member identifiers for multi-member source tables” Setting member identifiers for multi-member source tables You can add. or delete member identifiers when you have installed InfoSphere CDC for AS/400 on your source system and you are replicating a multi-member source table to a single-member target table on any platform. Expand the Target Columns tree and double-click to select the target column you want to include in the member identifier WHERE clause. 5. map the journal control field &MEMBER to this column. Click the Table Mappings view and select the table mapping. then you need to identify each member in the source table. in which one table can possess several different members. 8.Setting member identifiers iSeries environments supports a table concept known as multi-member files. Click Add. Right-click and select Edit Mapping Details. Click the Operation tab. modify. See also: “To add a member identifier” “To modify a member identifier” on page 188 “To delete a member identifier” on page 188 To add a member identifier 1. Select the subscription. Each member is part of the same table and shares the same schema. 9. 2. 2008 187 .

You can continue adding identifiers for each member in your source table. 11. Click OK. 12. Click Apply. Related concepts “Setting member identifiers for multi-member source tables” on page 187

To modify a member identifier
1. 2. 3. 4. 5. Click Configuration → Subscriptions. Select the subscription. Click the Table Mappings view and select the table mapping. Right-click and select Edit Mapping Details. Click the Operation tab.

6. Click Member Identifiers. 7. Click Modify. 8. Make the necessary changes and clickOK. You can continue making changes to other member identifiers or click OK to save your changes. 9. Click Apply. Related concepts “Setting member identifiers for multi-member source tables” on page 187

To delete a member identifier
1. Click Configuration → Subscriptions. 2. Select the subscription. 3. Click the Table Mappings view and select the table mapping. 4. 5. 6. 7. 8. 9. Right-click and select Edit Mapping Details. Click the Operation tab. Click Member Identifiers. Select the member identifier that you want to delete and click Delete. Click OK to save your changes. Click Apply. Related concepts “Setting member identifiers for multi-member source tables” on page 187

188

InfoSphere Change Data Capture Management Console: Administration Guide

Setting conflict detection and resolution
Conflict detection and resolution lets you detect, log, and act on inconsistent data on the target. This ensures your replication environment handles data conflicts automatically and in accordance with your business rules. Set conflict detection so that InfoSphere CDC can detect and resolve conflicts as they occur. As conflicts are detected and resolved, InfoSphere CDC logs them in a conflict resolution audit table. During replication, InfoSphere CDC detects conflicts when you: v Insert a row and the row’s key already exists in the target table. This violates the unique key constraint. v Update a row and the row’s key does not exist in the target table. v Update a row and the contents of the rows in the source table and target table, before the update, do not match. v Delete a row and the row’s key does not exist in the target table. v Delete a row and the contents of the rows in the source table and target table, before the delete, do not match. InfoSphere CDC does not detect conflicts in target columns that are: v Populated with expressions using the %BEFORE, %CURR, %GETCOL, %STPROC, and %USER column functions. v Populated with journal control fields. v Not populated by a value. Notes: v InfoSphere CDC does not detect conflicts in columns that have Large Object (LOB) data types. v Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC Version 5.3 and higher. In this section, you will learn: “Resolving conflicts for source or target wins” “Resolving conflicts for largest or smallest value wins” on page 191 “Resolving conflicts with user exits” on page 194

Resolving conflicts for source or target wins
Resolving conflicts for source wins
Use the Conflicts tab to set conflict detection and resolution so that the source wins. When InfoSphere CDC resolves conflicts so that the source column wins, it applies the row from the source table to the target table. This ensures the target table row matches the data in your source table upon replication. For example, a remote location ships 100 books and updates their INVENTORY table to the latest quantity of the books. When InfoSphere CDC attempts to replicate the update to the target table, it detects a conflict because there is no row to update. In this scenario, InfoSphere CDC resolves the conflict by inserting the row from the source
© Copyright IBM Corp. 2008

189

to the target.

Resolving conflicts for target wins
Use the Conflicts tab to set conflict detection and resolution so that the target wins. When InfoSphere CDC resolves conflicts for target wins, it does not apply any source changes to the target table. This preserves the row in the target table as InfoSphere CDC does not apply data from the source in the event of a conflict. For example, a remote location ships 25 pens and reduces the quantity of their pens to 175. Before starting replication with InfoSphere CDC, a clerk accidently changes the quantity of the pens to 300 on the target table. If InfoSphere CDC is configured to resolve conflicts for target wins, then no change is made to the target table and it is the same both before and after replication.

Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. See also: “To resolve conflicts for source row wins” “To resolve conflicts for target row wins” on page 191 Related concepts “Resolving conflicts for source or target wins” on page 189 “Mapping using standard replication” on page 91

To resolve conflicts for source row wins
1. Click Configuration → Subscriptions. 2. Select the subscription. 3. Click the Table Mappings view and select the table mapping. This should be mapped for Standard replication. 4. Right-click and select Edit Mapping Details. 5. Click the Conflicts tab.

190

InfoSphere Change Data Capture Management Console: Administration Guide

The Target Column displays all of the columns in the target table. 6. Select the columns on which you want to detect conflicts. 7. Select Source Wins from the Conflict Resolution Method list. 8. Click Apply. When you start replication on the subscription, if InfoSphere CDC detects a conflict in the target column, the source data is replicated to the target. Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. Related concepts “Resolving conflicts for source or target wins” on page 189 “Mapping using standard replication” on page 91

To resolve conflicts for target row wins
1. Click Configuration → Subscriptions. 2. Select the subscription. 3. Click the Table Mappings view and select the table mapping. This should be mapped for Standard replication. 4. Right-click and select Edit Mapping Details. 5. Click the Conflicts tab. The Target Column displays all of the columns in the target table. 6. Select the columns on which you want to detect conflicts. 7. Select Target Wins from the Conflict Resolution Method list. 8. Click Apply. When you start replication on the subscription, if InfoSphere CDC detects a conflict in the target column, the source data is replicated to the target. Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. Related concepts “Resolving conflicts for source or target wins” on page 189 “Mapping using standard replication” on page 91

Resolving conflicts for largest or smallest value wins
Use the Conflicts tab to set conflict detection and resolution so that the largest value wins or the smallest value wins.

Resolving conflicts for largest value wins
When InfoSphere CDC resolves conflicts for largest value wins, it applies the change to the target if the source row has a larger value than the corresponding row on the target table. For example, if the comparison column contains revision times, then the target row matches the row that was most recently updated (largest time value). When resolving conflicts for largest value wins, InfoSphere CDC treats NULL values as the smallest possible value. If the row does not exist on the target table,
Setting conflict detection and resolution

191

then InfoSphere CDC uses NULL as the comparison value. If InfoSphere CDC detects the conflict while deleting a row, then it uses the before image of the source table and compares it to the target value. If both the source and target values are the same, then InfoSphere CDC resolves the conflict using the Target Wins method (no change is applied to the target).

Resolving conflicts for smallest value wins
When InfoSphere CDC resolves conflicts for smallest value wins, it only applies the change to the target if the value in the source row is smaller than the corresponding row on the target table. For example, if the comparison column contains quantities, then InfoSphere CDC matches the target row with the row that has the smaller quantity.

When resolving conflicts for smallest value wins, InfoSphere CDC treats NULL values as the smallest possible value. If the row does not exist on the target table, then InfoSphere CDC uses NULL as the comparison value. If InfoSphere CDC detects the conflict while deleting a row, then it uses the before image of the source table and compares it to the target value. If both the source and target values are the same, then InfoSphere CDC resolves the conflict using the Target Wins method (no change is applied to the target). If both the source and target values are the same, then InfoSphere CDC resolves it using the Target Wins method (no change is applied to the target). Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. See also: “To resolve conflicts for largest value wins” on page 193 “To resolve conflicts for smallest value wins” on page 193 Related concepts “Mapping using standard replication” on page 91

192

InfoSphere Change Data Capture Management Console: Administration Guide

To resolve conflicts for largest value wins
1. Click Configuration → Subscriptions. 2. Select the subscription. 3. Click the Table Mappings view and select the table mapping. This should be mapped for Standard replication. 4. Right-click and select Edit Mapping Details. 5. Click the Conflicts tab. The Target Column displays all of the columns in the target table. 6. Select the target columns on which you want to detect conflicts in the Detect Conflicts area. 7. Select Largest Value Wins from the Conflict Resolution Method list. 8. Select the column on the target table that you want to compare to the row on the source table from the Value Comparison Column . 9. Click Apply. When you start replication on the subscription, if InfoSphere CDC detects a conflict in the target column, the source data is replicated to the target. Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. Related concepts “Resolving conflicts for source or target wins” on page 189 “Mapping using standard replication” on page 91

To resolve conflicts for smallest value wins
1. Click Configuration → Subscriptions. 2. Select the subscription. 3. Click the Table Mappings view and select the table mapping. This should be mapped for Standard replication. 4. Right-click and select Edit Mapping Details. 5. Click the Conflicts tab. The Target Column displays all of the columns in the target table. 6. Select the columns on which you want to detect conflicts. 7. Select Smallest Value Wins from the Conflict Resolution Method list. 8. Select the column on the target table that you want to compare to the row on the source table from the Value Comparison Column. 9. Click Apply. When you start replication on the subscription, if InfoSphere CDC detects a conflict in the target column, the source data is replicated to the target. Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. For more information on the requirements to configure a user exit program for conflict detection and resolution, see the ″User Exits″ section in the InfoSphere CDC documentation for your platform. Related concepts
Setting conflict detection and resolution

193

“Resolving conflicts for source or target wins” on page 189 “Mapping using standard replication” on page 91

Resolving conflicts with user exits
Use the Conflicts tab to resolve conflicts with user exit programs.

Resolving conflicts with user exit programs
When InfoSphere CDC resolves conflicts with a user exit program, it applies the image returned by the user exit program to the target table. Configuring a user exit program lets you specify the row you want InfoSphere CDC to use to resolve the conflict on the target table. When your user exit program returns a row, InfoSphere CDC applies that row to the target table to resolve the conflict. For example, a remote location receives a new shipment of erasers with a quantity of 400® and updates their INVENTORY table by inserting a new row. When InfoSphere CDC attempts to replicate the new insert, it detects a conflict because the row already exists in the target table. Since the database administrator has configured a user exit program that: v Receives data from the Eraser row from both the source and target table. v Concatenates values of both tables. InfoSphere CDC resolves the conflict according to the specifications in the user exit program.

Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. See also: “To resolve conflicts with user exit programs” on page 195 Related concepts “Mapping using standard replication” on page 91

194

InfoSphere Change Data Capture Management Console: Administration Guide

To resolve conflicts with user exit programs
1. Click Configuration → Subscriptions. 2. Select the subscription. 3. Click the Table Mappings view and select the table mapping. This should be mapped for Standard replication. 4. Right-click and select Edit Mapping Details. 5. Click the Conflicts tab. The Target Column displays all of the columns in the target table. 6. Select the columns on which you want to detect conflicts. 7. Select User Exit from the Conflict Resolution Method list. 8. Type the full path and file name of the user exit program you want to call when InfoSphere CDC detects a conflict in the User Exit (with path) box. 9. Click Apply. When you start replication on the subscription, if InfoSphere CDC detects a conflict in the target column, the source data is replicated to the target. For more information on conflict resolution user exit programs, see the ″User Exits″ section in the InfoSphere CDC documentation for your platform. Note: Conflict detection and resolution is only available when you map your tables using Standard replication. Conflict detection and resolution is supported for InfoSphere CDC version 5.3 and higher. Related concepts “Resolving conflicts for source or target wins” on page 189 “Mapping using standard replication” on page 91

Setting conflict detection and resolution

195

196

InfoSphere Change Data Capture Management Console: Administration Guide

Starting and ending replication on subscriptions
InfoSphere CDC lets you mirror data from all source tables (using change data capture technology) to mapped target tables. InfoSphere CDC provides two types of mirroring: continuous and net-change mirroring. You can also refresh tables in a subscription. You can manage mirroring on subscriptions from the Monitoring perspective in Management Console. In this section, you will learn: “Starting mirroring on a subscription” “Starting a refresh on a subscription” on page 198 “Ending replication on a subscription” on page 198 “Sending XML messages to a JMS message destination” on page 199

Starting mirroring on a subscription
v Continuous Mirroring—InfoSphere CDC applies changes to a target table as they occur (in real-time) on the source table. Continuous mirroring is appropriate when you need the latest information at all times and if your environment experiences frequent changes to large volumes of data. Instead capturing these changes using a batch transfer, you can replicate changes to the target on a continuous basis. v Net-change Mirroring—InfoSphere CDC accumulates changes that are occurring on the source table at a specific point in time and replicates these changes to the target table. When InfoSphere CDC completes sending the accumulated changes to the target table, net-change mirroring stops. You should use net-change mirroring when it is not necessary to have source and target tables synchronized at all times, and when you want to perform replication during off-peak periods or from a specific point in time. See also: “To start continuous mirroring” “To start net-change mirroring”

To start continuous mirroring
1. Ensure the subscription has at least one table mapping with replication method set to Mirror. You set this when mapping tables in the Map Tables wizard. 2. Click Monitoring → Subscriptions. 3. Select the subscription. 4. Right-click and select Start Mirroring (Continuous). Related concepts “Starting mirroring on a subscription” “Mapping tables” on page 91

To start net-change mirroring
1. Ensure the subscription has at least one table mapping with replication method set to Mirror. You set this when mapping tables in the Map Tables> wizard. 2. Click Monitoring → Subscriptions.
© Copyright IBM Corp. 2008

197

3. Select the subscription. 4. Right-click and select Start Mirroring (Net-change) . Related concepts “Starting mirroring on a subscription” on page 197

Starting a refresh on a subscription
When you start a refresh on a subscription, InfoSphere CDC sends a complete copy of the data in a source table to the target table. This operation overwrites any existing rows in the target table. The following list provides some possible scenarios for why you would want to use refresh instead of mirroring: v To create a periodic updated copy of your production environment for testing and development purposes. This is useful when you have promoted a set of subscriptions from a test to a production environment. v To gain performance in your environment. If you have a source table with a very small number of rows that gets a very large number of updates, this may consume a lot of bandwidth. Performing a refresh on these source tables on a weekly, daily, or hourly basis may be the best solution. See also: “To start a refresh” Related concepts “Promoting changes to subscriptions” on page 201

To start a refresh
1. Specify the rows on which you want InfoSphere CDC to apply a refresh. You can do this by specifying SQL statements in the Operation tab of Management Console. If you do not specify rows, then InfoSphere CDC refreshes all rows in the target table. 2. Click Monitoring → Subscriptions. 3. Select the subscription. 4. Right-click and select Start Refresh. 5. Select the tables you want to refresh. Note: If you have installed InfoSphere CDC for AS/400 or InfoSphere CDC for Microsoft SQL Server, then you need to make sure that there are no changes taking place on the source table while InfoSphere CDC refreshes the target table. Related concepts “Controlling the apply of refresh operations” on page 183

Ending replication on a subscription
You can end replication on your subscriptions when you want to prepare for any off-line maintenance activities. For example, you may want to start a full backup on a database or perform a regularly scheduled reboot of your server. Ending replication becomes necessary if you want to update and make changes to your subscription by: v Adding a table mapping to the subscription. v Deleting a table mapping from the subscription. v Temporarily removing a table mapping from the subscription (parking a table).

198

InfoSphere Change Data Capture Management Console: Administration Guide

v Modifying mapping details such as source and target column mappings, derived columns, data translations, row and column selections, user exits, and so on. v Updating the properties of a subscription when the structure of your source and/or target tables change. v Synchronizing source and target tables before restarting mirroring. See also: “To end replication”

To end replication
1. Click Monitoring → Subscriptions. 2. Select the subscription. 3. Right-click and select End Replication. 4. Choose one of the following options:
Option Controlled Description Lets InfoSphere CDC complete all in-progress operations and apply pending changes to the target table. Interrupts any current operations. InfoSphere CDC does not apply pending changes to the target table.

Immediate

Sending XML messages to a JMS message destination
For InfoSphere CDC Event Server to send the XML message to a JMS message destination, you must start mirroring on the subscription that contains the table mapping. When you start mirroring on the subscription, InfoSphere CDC Event Server sends a complete copy of all the rows in your source table to the JMS message destination, to the staging target table, or both. The subscription stays active and waits for additional events to occur on the source table. See also: “To send an XML message to a JMS message destination or a staging target database”

To send an XML message to a JMS message destination or a staging target database
1. Click Configuration → Datastores. Ensure you are connected to an Event Server datastore. 2. Click Configuration → Subscriptions. Ensure you have created a subscription that uses the Event Server datastore as the target database. 3. Select the subscription that contains the table mapping to a message destination, a staging target table, or both. 4. Click the Table Mappings view and select the table mapping. Ensure you have set the replication method for this table mapping to Mirror (Change Data Capture).
Starting and ending replication on subscriptions

199

Related concepts “Sending XML messages to multiple JMS message destinations” on page 226 Related tasks “To create an XML message” on page 143 200 InfoSphere Change Data Capture Management Console: Administration Guide .5. it switches to Mirror Continuous. staging target table. or both. InfoSphere CDC Event Server sends a copy of all the rows to your message destination. 6. Click Monitoring → Subscriptions. right-click Start Mirroring. Select the subscription that contains the table mapping. If this is the first time you are starting replication. After this is complete.

The purpose of promoting subscriptions is to relocate your subscription from one environment to another. If so. If you have built an expression on the source such as %GETCOL. and retire subscriptions. any notifications you set for the subscription. modify. you will learn: “Before you promote a subscription” “Promoting subscriptions” on page 202 “Exporting and importing subscriptions” on page 205 Before you promote a subscription You should consider the following points before promoting a subscription: v End replication—ensure you have ended replication on the subscription. you may have built a derived column on the source that references values from another table located in another database: %GETCOL(JobTitle. 2008 201 . the replication method.CustomerData". Placing subscriptions into projects are a useful organizational tool to distinguish between an existing and newly promoted subscription. v Identify the full path name or program name of user exits called by an expression—if you have an expression that calls a stored procedure on the source using the %USER column function. including the source database.dbo. source and target column mappings. the table called CustomerData might exist in another database. source tables. InfoSphere CDCManagement Console promotes the properties of your subscription. The Promote Subscription wizard promotes the configuration details you set for your table mapping in the Mapping Details area of the Management Console to the new environment. then this kind of expression will reference the names of columns from other tables. other than Northwind. For example. you should know the name and owner of the new source database that contain the table referenced in the expression. These mapping details are promoted to the new environment. the subscription is relocated into the new environment and uses new source and target datastores. v Review mapping details for the subscription—ensure that you have reviewed mapping details you set for the subscription. then you need to specify the name of the new source database that contains this table in the Promote Subscription wizard. you need to make sure that stored © Copyright IBM Corp. v Identify database name and owner—identify the database name and owner of the new source database. v Organize subscriptions into projects—organize the subscription that you want to promote into a project. When you are finished promoting your changes. In this section. Before you promote these expressions to the new environment. "Northwind. "Sales Manager") When promoting expressions to a new environment. table mappings. and any expressions into the new environment. If your organization has implemented a succession of development stages. then you may want to test your subscriptions before making them available in your production environment. data translations.Promoting changes to subscriptions Change management is the process by which you can develop.

2. For example. if you have an expression that calls a stored procedure on the target using the %STPROC function. see “Flagging a source table for a refresh” on page 135. the subscription may already exist in a project that you have reserved for testing subscriptions. Select Promote to a new subscription. you are promoting a subscription to a new environment. but you may have made some minor changes on the subscription. InfoSphere CDC maintains synchronization between your source and target tables and you do not need to set the log position in the new environment. For example. Note: When promoting changes to an existing subscription. You can promote subscriptions into one of these environments. However. you need to promote your changes to the into the testing environment. Using the Promotion Wizard. 3. you have made changes to a subscription that has already been promoted to another environment. you may have projects that are exclusive for development or testing purposes. then InfoSphere CDC does not maintain the log position and you will have to resynchronize your source and target tables in the original and in the new environment. You should also know the location (full path) for the stored procedure. Click Configuration → Subscriptions. you can: v Promote a Subscription to a New Environment—in this scenario. Type the name of the new subscription in the Name box. you can promote your subscription from a development environment and into a production environment when you are ready to use that subscription in replication activities.procedure exists in the new source database and specify the location of the stored procedure (for example. To make sure the subscription in the test environment includes the changes that you made. 4. if you are making changes that causes you to lose synchronization between your source and target tables (such as updating the definition of a source table). For more information on how to synchronize source and target tables in a table mapping. you need to make sure that stored procedure exists in the new target database. For example. See also: “To promote a subscription to a new environment” “To promote changes to an existing subscription” on page 204 To promote a subscription to a new environment 1. Also. Related concepts “Promoting changes to subscriptions” on page 201 Related tasks “To end replication” on page 199 Promoting subscriptions Use the Promote Subscription wizard to promote your subscription to a new environment. 202 InfoSphere Change Data Capture Management Console: Administration Guide . Right-click on a subscription and select Promote Subscription. the DLL path) in the Promote Subscription wizard. v Promote Changes to an Existing Subscription—in this scenario.

5. or the name of the user exit program referenced in the expression. Select the name of the new target datastore from the New Target Datastore list. Type a port number for the new subscription. 10. make sure that the table referenced in the derived column exists in the new source database. specify the name of the database and owner that contains the table that is referenced in the %GETCOL function. If you have configured expressions with column functions that call user exit programs. Also. then click Next. If you have built a derived column on the source that references another table in another database using the %GETCOL column function. 6. Make sure that the stored procedure or user exit program already exists in the new source database. Option Source ID Firewall Port TCP Host Description Type the source ID for the new subscription. Select the name of the new source datastore from the New Source Datastore list. Promoting changes to subscriptions 203 . Select the name of the database and owner from the New Name list and click Next. 12. This is useful if you want to specify a host that is different from the host that you specified in the Access Manager perspective. 7. 11. The default option is Auto-selectwhich will automatically select the network card that can communicate with the target datastore. 9. then click Advanced Settings and choose a valid alias and click OK. Do not replicate data received from any subscriptions 8. click Advanced Settings. then click Next. Specifies the TCP host that your source datastore will use to recognize the target datastore when the computer where InfoSphere CDC is installed has multiple network cards. 13. such as %USER or %STPROC. Propagation Control Click Addand select the source ID for any subscription for which you want to prevent data from being replicated to the target. The host that you specified in theAccess Manager perspective also appears by default as well as any alias’ that you configured in the Datastore Propertiesdialog box. Select a project for the new subscription from the Project list or click New Project to create a new project. then specify the full path that contains the stored procedure. If you want to specify advanced settings for the subscription. Select the name of the database and owner from the New Name list and click Next. Modify the following properties and click OK. Specifies that you want to prevent replication from all subscriptions. Type the description of the new subscription in the Descriptionbox. If you have added an alias for the target datastore that the source system can recognize.

Note: If you do not select a project. Click View XML to confirm the location and attributes of the promoted subscription. then click Next. Select the subscription to which you want to promote changes from the Promote To list. an expression. Click View XML to confirm the location and attributes of the promoted subscription. specify the full path that contains the stored procedure. 9. Related concepts “Before you promote a subscription” on page 201 “Promoting subscriptions” on page 202 To promote changes to an existing subscription 1. 16.14. make sure that the table or column referenced in the %SELECT expression exists in the new database. 15. After the promotion. or a row-filtering expression that uses the %SELECT column function. confirm the list of displayed expressions and click Next. If you have built a derived column. Management Console places the new subscription into the Default Project. Confirm the source datastore and the name of the database and owner from which you want to promote the changes. Review the list of changes and click Finish. Review the list of changes and click Finish. specify the name of the database and owner that contains the table that is referenced in the %GETCOL function. Select Promote to an existing subscription. and click Next. Also. After promotion. then click Next. 4. 8. If you have configured expressions with column functions that call user exit programs. 3. make sure that the table or column referenced in the %SELECT expression exists in the new database. 10. 5. 6. or a row-filtering expression that uses the %SELECT column function. Right-click on a subscription and select Promote Subscription. or the name of the user exit program referenced in the expression. 2. If you have built a derived column. make sure that the table referenced in the derived column exists in the new source database. such as %USER or %STPROC. then confirm the list of displayed expressions and click Next. Click Configuration → Subscriptions. Related concepts “Before you promote a subscription” on page 201 “Promoting subscriptions” on page 202 204 InfoSphere Change Data Capture Management Console: Administration Guide . then click Next. Make sure that the stored procedure or user exit program already exists in the new source database. 7. Confirm the target datastore and the name of the database and owner to which you want to promote the changes. an expression. If you have built a derived column on the source that references another table in another database using the %GETCOL column function.

select one of the following options: Description Copies the settings in the XML file into a new subscription. Right-click on a subscription and select Import Subscription. 3. Click Configuration → Subscriptions. Select an XML file and click Open. 3. 2. Related concepts “Exporting and importing subscriptions” Related tasks “To promote a subscription to a new environment” on page 202 “To promote changes to an existing subscription” on page 204 Promoting changes to subscriptions 205 .Exporting and importing subscriptions Using InfoSphere CDC export and import capabilities. Option Import to a new subscription Import changes to an existing subscription Note: The steps to importing a new or existing subscription are the same as promoting a new or existing subscription. Click Configuration → Subscriptions. Type the name for the XML file and click Save. Depending on how you want to import the settings of your subscription. Copies the settings in the XML file into an existing subscription. 4. See also: “To import a subscription from an XML file” “To export a subscription into an XML file” To import a subscription from an XML file 1. Right-click on a subscription and select Export Subscription. and you can save these files on your local computer or elsewhere. you can prepare XML files that include details you have set on your subscription. Related concepts “Exporting and importing subscriptions” Related tasks “To promote a subscription to a new environment” on page 202 “To promote changes to an existing subscription” on page 204 To export a subscription into an XML file 1. 2.

206 InfoSphere Change Data Capture Management Console: Administration Guide .

For example. Table-level operations include a refresh or a truncate operation. such as the original invoice date. Row-level operations include an insert. update. For example.Management Console lets you enable or disable user exits developed for IDispatch. InfoSphere CDC can run the user exit and apply the row-level operation (insert. you can configure a row-level user exit program that sends an alert after InfoSphere CDC replicates a delete operation on a particular target table. update. in response to a table-level truncate operation. you can develop logic for insert.Configuring user exits A user exit lets you define a set of actions that InfoSphere CDC can run before or after a database event occurs on a specified table. November 2006. you can develop a user exit that lets you do a soft delete rather than a hard delete on the target table. you need to do the following in Microsoft SQL Server: v Create the user-defined function. The following list identifies common scenarios for developing a user exit program before or after row or table-level operations: Customize when InfoSphere CDC replicates a row-level operation to the target table. When using InfoSphere CDC. and replace them by invoking a user exit program that performs custom operations. v Disable the default row-level or table-level operations. User exits can be grouped as either a Before User Exit or an After User Exit: v Before User Exit—runs before InfoSphere CDC replicates any row-level or table-level operations to the target table. For example. you will learn: “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” “Configuring user exits for InfoSphere CDC for Oracle or InfoSphere CDC for Sybase” on page 216 “Configuring user exits for InfoSphere CDC for AS/400 (version 6. or a delete. 2008 207 . or delete operations so that these occur based on some specified criteria. update. v After User Exit—runs after InfoSphere CDC replicates any row-level or table-level operations to the target table. a database event is defined as either a row-level operation or as a table-level operation.2 and below) or InfoSphere CDC for z/OS” on page 219 “Creating a custom data format for IBM WebSphere DataStage” on page 220 Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB You can configure the following types of user exits with InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB: IDispatch COM DLL (InfoSphere CDC for Microsoft SQL Server)—You can invoke at run-time a function you defined using IDispatch. January 2004. v In this section. Before you can use Management Console to configure a user exit. and so on. When configuring an IDispatch COM DLL user exit. such as. © Copyright IBM Corp. February 2004. or delete) to the appropriate target table based on the original invoice date.

As a result.0).0 and above and DB2 UBD 6. see your user exits documentation for InfoSphere CDC for Microsoft SQL Server. You need to configure a user exit in java that implements the UserExitIF interface class provided by InfoSphere CDC for DB2 UDB and InfoSphere CDC for Microsoft SQL Server (version 6.1 and above)” on page 214 “To configure a user exit for a Java class” on page 214 Related concepts “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 208 InfoSphere Change Data Capture Management Console: Administration Guide .3. you can only select (not name) the functions that you want to call at the various processing points. Depending on how you have configured the stored procedure. See also: “To configure for IDispatch COM DLL” on page 209 “To configure for C or C++” on page 210 “To configure a stored procedure (Microsoft SQL Server version 5.1))—you can configure a stored procedure user exit for InfoSphere CDC for Microsoft SQL Server Version 6. method names are pre-defined.3)—you can configure a user exit as a stored procedure for InfoSphere CDC for Microsoft SQL Server Version 5. The interface contains four pre-defined user exit program stubs that you should not modify. For more information.1).0 and higher) and DB2 UDB (version 6. Your stored procedure user exit can then retrieve the image of the row from these tables and use them as required. This means that you can only enable and disable user exit programs.1 and higher))” on page 213 “To configure a derived column or an expression that calls %STPROC (Microsoft SQL Server 6. C:\Program Files\Microsoft SQL Server\MSSQL\Binn (or wherever appropriate). InfoSphere CDC provides a pre-defined interface (IDTS_UserExit) so that InfoSphere CDC can interact with the server object you define. You need to identify the schema that contains the stored procedure and identify the InfoSphere CDC operations on which you want to run the user exit.1 and higher. v v C or C++ (InfoSphere CDC for Microsoft SQL Server)—you can specify a DLL library that contains the compiled user exit program. Java Class (InfoSphere CDC for Microsoft SQL Server (version 6.3)” on page 211 “To configure a stored procedure (Microsoft SQL Server (version 6. Stored Procedure (InfoSphere CDC for Microsoft SQL Server (version 5. InfoSphere CDC for DB2 UDB)—for Java class user exits. see the InfoSphere CDC End-User Documentation for each of these platforms. For more information about this class. Extract or build the DLL file and place it in a location.Create the user exit. you must reference the library dts_usrext. For example. you need to identify temporary or permanent tables so that InfoSphere CDC can populate these tables with the images of the row-level operations applied to the target table. Stored Procedure (InfoSphere CDC for Microsoft SQL Server (version 6. v If you are using Visual Basic.tlb after starting Visual Basic.

zero. then enable Update All Columns. and they are not affected by InfoSphere CDC. InfoSphere CDC runs the exist after replicating a truncate operation. Click the User Exits tab. it is important that you clear this box if you do not need to pass the user-defined constant values. Click Apply. Due to performance reasons. 5. Click Configuration → Subscriptions. InfoSphere CDC runs the user exit before replicating a delete operation. 9. InfoSphere CDC runs the user exit after replicating a delete operation. If you do not enable Update All Columns. 3.To configure for IDispatch COM DLL Note: This information is applicable to InfoSphere CDC for Microsof SQL Server. InfoSphere CDC runs the user exit before replicating a truncate operation. 6. 7. Select the table mapping. Type the name of the class module and project that contains the user exit program that you want run in the DLL Name box. InfoSphere CDC runs the user exit before replicating an update operation. Related concepts Configuring user exits 209 . InfoSphere CDC runs the user exit after replicating an update operation. then InfoSphere CDC passes the default column value (for example. Select the subscription. blank. 10. 2. Right-click and select Edit Mapping Details. Other applications usually maintain these constant values. InfoSphere CDC runs the user exit after replicating a refresh operation. InfoSphere CDC runs the user exit before replicating a refresh operation. or NULL) to the user exit program. In some environments. Select IDispatch COM DLL from the User Exit Type list. the target table may contain one or more columns that store user-defined constants. If you want InfoSphere CDC to retrieve the current constant value from the target and pass it to a user exit program that runs before or after InfoSphere CDC replicates an update operation to the target table. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating an insert operation. 1. InfoSphere CDC runs the user exit after replicating an insert operation. 4. 8.

2. Type the name of the user exit programs you want to call in the Function Name list. InfoSphere CDC runs the user exit before replicating an update operation. Select C/C++ DLL from the User Exit Type list. InfoSphere CDC runs the exist after replicating a truncate operation. Click Configuration → Subscriptions. and they are not affected by InfoSphere CDC. If you want InfoSphere CDC to retrieve the current constant value from the target and pass it to a user exit program that runs before or after InfoSphere CDC replicates an update operation to the target table. InfoSphere CDC runs the user exit before replicating a refresh operation. InfoSphere CDC runs the user exit before replicating a truncate operation. InfoSphere CDC runs the user exit before replicating a delete operation. If you do not enable Update All Columns. the target table may contain one or more columns that store user-defined constants. Other applications usually maintain these constant values. then InfoSphere CDC passes the default column 210 InfoSphere Change Data Capture Management Console: Administration Guide . Type the full path name of a DLL library that contains the compiled user exit program in the DLL Name box. 7. 4. In some environments. 9. 10. 1. 5. Click the User Exits tab. Select the subscription 3. then enable Update All Column. InfoSphere CDC runs the user exit after replicating an insert operation. InfoSphere CDC runs the user exit after replicating an update operation. InfoSphere CDC runs the user exit after replicating a delete operation. Click the Table Mappings view and select the table mapping. 11. Click Apply.“Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 To configure for C or C++ Note: This information is applicable to InfoSphere CDC for Microsoft SQL Server. 8. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating an insert operation. 6. Right-click and select Edit Mapping Details. InfoSphere CDC runs the user exit after replicating a refresh operation.

Click the User Exits tab. in the Database Owner box. If you have a stored procedure that requires access to journal information for each updated row. Select the subscription. then provide the name of the temporary or permanent table in the Update Table Image box. see “Using journal control fields for auditing replication activities” on page 245. 10. then provide the name of the temporary or permanent table in the Key Table Image box. or NULL) to the user exit program. Select Stored Procedure from the User Exit Type list. Note that InfoSphere CDC does not verify whether an image table name Configuring user exits 211 . 3. Type the database owner of the stored procedure. InfoSphere CDC populates this table with the before image of the rows in the source table. 4. During replication. Journal header information includes journal control fields and journal codes that indicate what kind of update was made on the row. Related concepts “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 To configure a stored procedure (Microsoft SQL Server version 5. 8. InfoSphere CDC populates this table with either the after or before images of the key column data. it is important that you clear this box if you do not need to pass the user-defined constant values. 11. Depending on the kind of row-level operation applied to the target table. Your stored procedure user exit then retrieves the after or before image of the key column data from this table. Click the Table Mappings view and select the table mapping. If you have a stored procedure that runs after InfoSphere CDC replicates an update operation to the target table. 5. Notes: v InfoSphere CDC supports fully qualified image table names to a maximum of 100 characters in length. 2. During replication. 6. Your stored procedure user exit then retrieves the before image of the row from this table. 1. then provide the name of the temporary or permanent table in the Journal Table Image box. Due to performance reasons. 7. Your stored procedure user exit then retrieves the after image of the row from this table. blank. Right-click and select Edit Mapping Details. but database naming restrictions still apply. then provide the name of the temporary or permanent table in the Before Table Image box. For more information about journal control fields.value (for example. If you have a stored procedure that requires access to a specific row. If you have configured a stored procedure that runs before a row-level operation is replicated to the target table. InfoSphere CDC populates this table with the after image of the update operation that was applied to the target. Click Configuration → Subscriptions. InfoSphere CDC populates this table with the journal header information.3. 9. zero.3) Note: This information is applicable to InfoSphere CDC for Microsoft SQL Server version 5.

InfoSphere CDC runs the user exit after replicating a delete operation. the target table may contain one or more columns that store user-defined constants. In some environments. InfoSphere CDC runs the user exit after replicating an insert operation.conforms to a database naming convention. If you do not enable Update All Columns. and they are not affected by InfoSphere CDC. If you are referencing a database or table that contains spaces. then you must enclose the name in square brackets. then check the Update All Columns box. InfoSphere CDC runs the user exit after replicating a refresh operation. it is important that you clear this box if you do not need to pass the user-defined constant values.1 and higher))” on page 213 212 InfoSphere Change Data Capture Management Console: Administration Guide . InfoSphere CDC runs the user exit before replicating a delete operation. then InfoSphere CDC passes the default column value (for example. blank. If you want to retrieve the current constant value (also known as the before or after image of the source row) and pass it to a user exit program that runs before or after a row-level operation is replicated to the target table. Related concepts “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 Related tasks “To configure a stored procedure (Microsoft SQL Server (version 6. If you want to create permanent tables using Management Console. Other applications usually maintain these constant values. then click Create Tables. 12. 13. InfoSphere CDC runs the user exit after replicating an update operation. to reference the table name ″EMP NY″. Click Apply. InfoSphere CDC runs the user exit before replicating an update operation. For example. InfoSphere CDC runs the exist after replicating a truncate operation. InfoSphere CDC runs the user exit before replicating a truncate operation. or NULL) to the user exit program. InfoSphere CDC runs the user exit before replicating a refresh operation.0 and higher) and DB2 UDB (version 6. v The image tables and the target tables should reside in different databases to prevent any possibility of locking the database. Due to performance reasons. 14. zero. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating an insert operation. 15. you must enter it as [EMP NY].

To configure a stored procedure (Microsoft SQL Server (version 6. InfoSphere CDC runs the user exit before replicating a refresh operation. InfoSphere CDC runs the user exit before replicating a delete operation. InfoSphere CDC runs the user exit after replicating a delete operation.1 and higher). Select Stored Procedure from the User Exit Type list. Click the User Exits tab. Type the name of the schema that contains the stored procedure in the Schema box.1 and higher)) Note: This information is applicable to InfoSphere CDC for Microsoft SQL Server (version 6.Deprecated option to maintain user exits that were created using InfoSphere CDC for Microsoft SQL Server (version 5.0 and higher) and DB2 UDB (version 6.0 and higher) and InfoSphere CDC for DB2 UDB (version 6. 4. 9. InfoSphere CDC runs the user exit after replicating an insert operation. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating an insert operation. Use the Stored Procedure option for all new user exits. Select the subscription. InfoSphere CDC runs the exist after replicating a truncate operation. InfoSphere CDC runs the user exit before replicating a truncate operation. Click Configuration → Subscriptions. 2. InfoSphere CDC runs the user exit after replicating an update operation. Right-click and select Edit Mapping Details. Note: Use the Stored Procedure . 7. Select the table mapping in the Table Mappings view. InfoSphere CDC runs the user exit before replicating an update operation. 3. 5. InfoSphere CDC runs the user exit after replicating a refresh operation. 1. 8.3). Related concepts “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 Related tasks Configuring user exits 213 . 6. Click Apply.

1 and above) Note: This information is applicable to InfoSphere CDC for Microsoft SLQ Server (version 6. For example. 3. 2. Type the name of the Java class user exit that implements the UserExitIF interface in the Class Name box. you may have imported the UserExitIF interface. 1.0 and above) and InfoSphere CDC for DB2 UBD (version 6. and do one of the following: v If you want InfoSphere CDC to evaluate an expression on the source table. then build an expression. you must provide the name in the form <schema>. Click the Table Mappings view and select the table mapping. Related concepts “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 Related tasks “To configure a stored procedure (Microsoft SQL Server version 5. then add a derived column. Select the subscription.“To configure a stored procedure (Microsoft SQL Server version 5. 2.0 or higher) and InfoSphere CDC for DB2 UDB. Click Configuration → Subscriptions. and configure a stored procedure.<stored procedure name>. Map the derived column or the expression to the target column. v If you want InfoSphere CDC to evaluate an expression on the target table. 4. 6. 1. 7.0 and higher) and DB2 UDB (version 6. If you are calling a stored procedure that is not owned by the InfoSphere CDC user. Click the User Exits tab. Make sure the expression you define contains a valid call to the %STPROC column function. 3.1 and higher))” on page 213 “To add a derived column” on page 163 “To map a derived column to a target column” on page 164 “To map an expression to a target column” on page 159 To configure a user exit for a Java class Note: This information is applicable to InfoSphere CDC for Microsoft SQL Server (version 6.3)” on page 211 To configure a derived column or an expression that calls %STPROC (Microsoft SQL Server 6. Right-click and select Edit Mapping Details. 5. Select Java Class from the User Exit Type list. Click the Column Mappings tab. and the user exit program class that implements this interface in your function has the following definition: public class UE1 implements UserExitIF 214 InfoSphere Change Data Capture Management Console: Administration Guide .0 and above and DB2 UBD 6. Click the User Exits tab.3)” on page 211 “To configure a stored procedure (Microsoft SQL Server (version 6.1 and above).

You can access the parameters in the user exit program class by invoking the getParameter( ) method during the initialization process.In the Class Name box.datamirror. There are no conventions for specifying the parameters. InfoSphere CDC runs the user exit after replicating an insert operation. Click Apply. InfoSphere CDC runs the user exit after replicating an update operation. 9.UE1 Description If it is a stand-alone class If the class is included in a Java package (for example. InfoSphere CDC runs the exist after replicating a truncate operation. com. InfoSphere CDC runs the user exit after replicating a refresh operation. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating an insert operation. InfoSphere CDC runs the user exit before replicating an update operation. InfoSphere CDC runs the user exit before replicating a truncate operation. InfoSphere CDC runs the user exit after replicating a delete operation. Type the parameters that you want to make available to the user exit program in the Parameter box.interface. 10. InfoSphere CDC runs the user exit before replicating a delete operation. The values you type in this box are free-form. InfoSphere CDC runs the user exit before replicating a refresh operation. Related concepts “Configuring user exits for InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for DB2 UDB” on page 207 Configuring user exits 215 . 8.UE1) The files you generate from compiling the user exit program must be located in a library or folder that is referenced by the CLASSPATH environment variable. The string of parameter values cannot exceed 255 characters in length. you need to type: Option UE1 <Java package>.

5. 2. InfoSphere CDC runs the user exit before replicating an update operation. You can configure the InfoSphere CDC to run the user exit program before or after an insert. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Description InfoSphere CDC runs the user exit before replicating an insert operation. update. Select C Shared Library from the User Exit Type list.Configuring user exits for InfoSphere CDC for Oracle or InfoSphere CDC for Sybase C Shared Library—you can configure a C user exit program for InfoSphere CDC. 1. InfoSphere CDC can call your stored procedure from either the source or target when you use the %STPROC column function in an expression. then check the Retrieve Current Values box. InfoSphere CDC runs the user exit after replicating an insert operation. 8. If you want InfoSphere CDC to retrieve the current constant value from the target and pass it to a user exit program that runs before or after InfoSphere CDC replicates an update operation to the target table. Select the table mapping. Click Configuration → Subscriptions. Stored Procedure—you can configure a stored procedure user exit for InfoSphere CDC. Right-click and select Edit Mapping Details. If you want InfoSphere CDC to evaluate and call your stored procedure on the target. then you need to build an expression. then you need to add a derived column. 3. Select the subscription. or truncate operation. 9. InfoSphere CDC runs the user exit after replicating an update operation. delete. See also: “To configure a C shared library” “To configure a stored procedure (Oracle and Sybase)” on page 217 “To configure a derived column or an expression that calls %STPROC (Oracle and Sybase)” on page 218 To configure a C shared library Note: This information is applicable to InfoSphere CDC for Oracle andInfoSphere CDC for Sybase). If you want InfoSphere CDC to evaluate and call your stored procedure on the source. Type the full path name of the file containing the shared library in the File (path) box. 216 InfoSphere Change Data Capture Management Console: Administration Guide . 7. 4. Click the User Exits tab. You need to identify the schema that contains the stored procedure and identify the InfoSphere CDC operations on which you want to run the user exit. 6.

1. 5. InfoSphere CDC runs the user exit after replicating a refresh operation. Click the User Exits tab. then InfoSphere CDC passes the default column value (for example. 4. 8. Specify the parameters that you want InfoSphere CDC to pass to the user exit program. Click Configuration → Subscriptions. 11. or NULL) to the user exit program. then check the Retrieve Current Values box. Click Apply. If you do not enable Retrieve Current Value. and they are not affected by InfoSphere CDC. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert Description InfoSphere CDC runs the user exit before replicating an insert operation. Configuring user exits 217 . 2. 3. InfoSphere CDC runs the user exit after replicating a delete operation. Select the subscription. Due to performance reasons. 7. If you want InfoSphere CDC to retrieve the current constant value from the target and pass it to a user exit program that runs before or after InfoSphere CDC replicates an update operation to the target table. Right-click and select Edit Mapping Details. blank. 9. InfoSphere CDC runs the user exit before replicating a refresh operation. zero. Other applications usually maintain these constant values. In some environments. Select Stored Procedure from the User Exit Type list. 6. InfoSphere CDC runs the exist after replicating a truncate operation. it is important that you clear this box if you do not need to pass the user-defined constant values. Related concepts “Configuring user exits for InfoSphere CDC for Oracle or InfoSphere CDC for Sybase” on page 216 To configure a stored procedure (Oracle and Sybase) Note: This information is applicable to InfoSphere CDC for Oracle and InfoSphere CDC for Sybase. Click the Table Mappings view and select the table mapping. Type the name of the schema that contains the stored procedure in the Schema box. the target table may contain one or more columns that store user-defined constants.Option Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating a delete operation. 10. InfoSphere CDC runs the user exit before replicating a truncate operation.

Click the Column Mappings tab. In some environments. Other applications usually maintain these constant values. the target table may contain one or more columns that store user-defined constants. InfoSphere CDC runs the user exit after replicating a delete operation. InfoSphere CDC runs the user exit before replicating a truncate operation. InfoSphere CDC runs the user exit after replicating an update operation. Related concepts “Configuring user exits for InfoSphere CDC for Oracle or InfoSphere CDC for Sybase” on page 216 To configure a derived column or an expression that calls %STPROC (Oracle and Sybase) Note: This information is applicable to InfoSphere CDC for Oracle and InfoSphere CDC for Sybase. you must provide the name in the form <schema>. InfoSphere CDC runs the user exit before replicating an update operation. then add a derived column. Click the User Exits tab. blank. 10. v If you want InfoSphere CDC to evaluate an expression on the target table. 3. it is important that you clear this box if you do not need to pass the user-defined constant values. Click Apply. If you do not enable Retrieve Current Value. 1. then build an expression. InfoSphere CDC runs the user exit before replicating a delete operation. and they are not affected by InfoSphere CDC. and do one of the following: v If you want InfoSphere CDC to evaluate an expression on the source table. Make sure the expression you define contains a valid call to the %STPROC column function.<stored procedure name>. InfoSphere CDC runs the exist after replicating a truncate operation. InfoSphere CDC runs the user exit before replicating a refresh operation. and configure a stored procedure.Option After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit after replicating an insert operation. Related tasks “To configure a stored procedure (Oracle and Sybase)” on page 217 218 InfoSphere Change Data Capture Management Console: Administration Guide . then InfoSphere CDC passes the default column value (for example. Map the derived column or the expression to the target column. If you are calling a stored procedure that is not owned by the InfoSphere CDC user. or NULL) to the user exit program. 2. zero. Due to performance reasons. InfoSphere CDC runs the user exit after replicating a refresh operation.

COBOL. 2. 7. Select Standard Function from the User Exit Type list. InfoSphere CDC runs the user exit before replicating an update operation. See also: “To configure a standard function” To configure a standard function Note: This information is applicable to InfoSphere CDC for AS/400 and InfoSphere CDC for z/OS. 4. InfoSphere CDC runs the user exit after replicating a refresh operation. 1. Click Configuration → Subscriptions. Right-click and select Edit Mapping Details. Click the Table Mappings view and select the table mapping. InfoSphere CDC runs the user exit after replicating an insert operation. 6. InfoSphere CDC runs the exist after replicating a truncate operation. 8. InfoSphere CDC runs the user exit after replicating a delete operation. Click Apply. InfoSphere CDC runs the user exit before replicating a truncate operation. and C/C++. 5. Select the subscription. Click the User Exits tab.2 and below) or InfoSphere CDC for z/OS You can write standard function user exits in RPG. Related concepts Configuring user exits 219 . 3. InfoSphere CDC runs the user exit before replicating a delete operation.“To add a derived column” on page 163 “To map a derived column to a target column” on page 164 “To map an expression to a target column” on page 159 Configuring user exits for InfoSphere CDC for AS/400 (version 6. InfoSphere CDC runs the user exit after replicating an update operation. InfoSphere CDC runs the user exit before replicating a refresh operation. Type the name of the user exit programs you want InfoSphere CDC to call beside one or more of the following operations: Option Before Insert After Insert Before Update After Update Before Delete After Delete Before Refresh After Refresh Before Truncate After Truncate Description InfoSphere CDC runs the user exit before replicating an insert operation.

Right-click and select Edit Mapping Details. it may be easier for you to specify a Java class to customize the data format rather than modifying your existing WebSphere DataStage job. and the class that implements this interface in your function has the following definition: public class CustomFormat1 implements DataStageDataFormatIF In the Class Name box in the Custom Data Format area. com.datamirror. 5. you may have imported the DataStageDataFormatIF interface. Click Apply. 220 InfoSphere Change Data Capture Management Console: Administration Guide . If the class is included in a Java package (for example. the DSX file that is generated by Management Console and imported into WebSphere DataStage may no longer be relevant. For example.“Configuring user exits for InfoSphere CDC for AS/400 (version 6. you may have an existing WebSphere DataStage file-based job that will not read the default data format generated by Management Console. Select the subscription. Click the Flat File or Direct Connect tab depending on your mapping type. By customizing the data. Type the name of the Java class that implements the DataStageDataFormatIF interface in the Class Name box.CustomFormat1 ). Click the Table Mappings view and select the table mapping. For example.interface.2 and below) or InfoSphere CDC for z/OS” on page 219 Creating a custom data format for IBM WebSphere DataStage By specifying a Java class. 7. 2. For more information on the DataStageDataFormatIF interface. see the Javadocs that are installed with your InfoSphere CDC for WebSphere DataStage installation. 3. 6. Click Configuration → Subscriptions. You are responsible for ensuring that the DSX file is still relevant in WebSphere DataStage.CustomFormat1 Description If it is a stand-alone class. A Java class that creates a custom data format must implement the DataStageDataFormatIF interface. 4. See also: “To create a custom data format for WebSphere DataStage” Related concepts “Creating a custom data format for WebSphere DataStage” on page 242 To create a custom data format for WebSphere DataStage 1. In this case. The files you generate from compiling the class must be located in a library or folder that is referenced by the CLASSPATH environment variable. you need to type: Option CustomFormat1 <Java package>. you can customize the data that is being sent to WebSphere DataStage.

After User Exit—runs after InfoSphere CDC Event Server applies a row-level operation to either a table you have staged in a staging database or after applying the operation to a JMS message destination. In this section. or a delete. See also: “To override JMS message header properties” on page 222 © Copyright IBM Corp.2. you will learn: “Overriding JMS message header properties” “Sending the XML message to a different JMS message destination” on page 223 “Creating XML output and applying XSLT to an XML message” on page 224 “Sending XML messages to multiple JMS message destinations” on page 226 “Querying a Web service to access content” on page 227 “Content based routing” on page 228 Overriding JMS message header properties You can override the default JMS message header properties you had set for a source table to XML mapping in the XML Settings tab.Configuring user exits for InfoSphere CDC Event Server You can configure a user exit to define a set of actions that InfoSphere CDC Event Server can run either before or after applying a row-level operation to a staged target table or to a JMS message destination. Standard Edition.4. version 1. update. Before User Exit—runs before InfoSphere CDC Event Server applies a row-level operation to either a table you have staged in a staging database and/or before applying the operation to a JMS message destination. Depending on the JMS message property you want to override. You can develop the user exit using Java.java located in the samples folder or directory of your InfoSphere CDC Event Server installation. Row-level operations include an insert. InfoSphere CDC Event Server lets you specify parameters for the following methods in the EventServerIF interface: v setJmsCorrelationID() v setJmsCustomProperty() v setJmsDeliveryMode() v setJmsPriority() v setJmsReplyTo() v setJmsTimeToLive() v setJmsType() For an example of a user exit that overrides the JMS properties of an existing source table to XML mapping. see SampleUserExit1. Note: All Java user exits must be compiled with Java 2 Platform. 2008 221 .

In the Class Name box. 9. In the Class Name box. type the Java class name of the user exit that implements the UserExitIF interface if you have developed the user exit in Java. There are no conventions for specifying the parameters. Click Configuration → Subscriptions. and the Java class user exit that implements this interface in your function has the following definition: public class UE1 implements UserExitIF. You can access the parameters in the Java class by invoking the getParameter() method during the initialization process. type: 8. Type the parameters that you want to make available to the user exit program in the Parameter box. 4. Ensure you have created a subscription that uses the Event Server datastore as the target database. Select the table mapping and right-click Edit Mapping Details. you may have imported the EventServerIF interface. 7. The string of parameter values cannot exceed 255 characters in length. Update Delete Related concepts “Sending XML messages to multiple JMS message destinations” on page 226 “Defining the JMS message header” on page 151 “Overriding JMS message header properties” on page 221 “Configuring user exits for InfoSphere CDC Event Server” on page 221 222 InfoSphere Change Data Capture Management Console: Administration Guide . Click the User Exits tab.To override JMS message header properties 1. InfoSphere CDC Event Server runs the user exit before applying a delete operation to a table you have staged and/or before applying a delete operation to a JMS message destination. 2. Enable the Before check box for one or more of the following operations: Option Insert Description InfoSphere CDC Event Server runs the user exit before applying an insert operation to a table you have staged and/or before applying an insert operation to a JMS message destination. The values you type in this box are free-form. For example. Ensure you are connected to an Event Server datastore. 6. InfoSphere CDC Event Server runs the user exit before applying an update operation to a table you have staged and/or before applying an update operation to a JMS message destination. Ensure you have created at least one source table to XML message destination mapping within this subscription. 3. 5. Click Configuration → Datastores. Choose Java Class from the User Exit Type box.

The values you type in this box are free-form. For an example of a user exit that sends an XML message to a different JMS message destination. Type the parameters that you want to make available to the user exit program in the Parameter box. Ensure you have created a subscription that uses the Event Server datastore as the target database. See also: “To send the XML message to another JMS message destination” To send the XML message to another JMS message destination 1. Ensure you are connected to an Event Server datastore. Choose Java Class from the User Exit Type box. 2. Click Configuration → Datastores. There are no conventions for specifying the parameters.Sending the XML message to a different JMS message destination You can develop a user exit that lets you send an XML message to a different JMS message destination than the one you added using the InfoSphere CDC Configuration tool. The string of parameter values cannot exceed 255 characters in length. For example. Using the setDestination() method in a user exit with the EventServerIF interface. 6. type: 8. Click Configuration → Subscriptions. Select the table mapping and right-click Edit Mapping Details. Enable the Before check box for one or more of the following operations: Option Insert Description InfoSphere CDC Event Server runs the user exit before applying an insert operation to a table you have staged and/or before applying an insert operation to a JMS message destination. In the Class Name box. Click the User Exits tab. you may have imported the EventServerIF interface. 3. you can send an XML message to a different JMS message destination. 9. 5. see SampleUserExit2.java located in the samples folder or directory of your InfoSphere CDC Event Server installation. type the Java class name of the user exit that implements the UserExitIF interface if you have developed the user exit in Java. Configuring user exits for InfoSphere CDC Event Server 223 . Ensure you have created at least one source table to XML message destination mapping within this subscription. You can access the parameters in the Java class by invoking the getParameter() method during the initialization process. and the Java class user exit that implements this interface in your function has the following definition: public class UE1 implements UserExitIF. In the Class Name box. 7. 4.

// Apply XSLT transform 224 InfoSphere Change Data Capture Management Console: Administration Guide . Delete 10.BEFORE_INSERT_EVENT) { EventServerIF eventServer = p_Event.applyXslt("xslt/dbxml. InfoSphere CDC Event Server runs the user exit before applying a delete operation to a table you have staged and/or before applying a delete operation to a JMS message destination. You can start mirroring on the subscription that contains the source table assigned to a JMS message destination. //Set the xml message that TS/ES is going to send eventServer. Click Apply. int eventType = p_Event. // Apply XSLT transform to the xml message String xsltOutput = eventServer. InfoSphere CDC Event Server lets you specify parameters for the following methods in the EventServerIF interface: v createXmlOutput() v apply Xslt() For example.setOutputTextMessage(xsltOutput). if (eventType == ReplicationEventTypes.Option Update Description InfoSphere CDC Event Server runs the user exit before applying an update operation to a table you have staged and/or before applying an update operation to a JMS message destination. xml). Related concepts “Sending XML messages to a JMS message destination” on page 199 “Sending the XML message to a different JMS message destination” on page 223 “Configuring user exits for InfoSphere CDC Event Server” on page 221 Creating XML output and applying XSLT to an XML message You can develop a user exit which lets you create an XML message and then format the XML message using XSL Transformations (XSLT). } public boolean processReplicationEvent(ReplicationEventIF p_Event) throws UserExitException { boolean retValue = true.getEventType().xsl". ReplicationEventIF p_Event) throws UserExitException { //Get TS/ES XML Engine to create the xml file String xml = eventServer. The user exit program will set the new destination before InfoSphere CDC Event Server applies the operation to a JMS message destination. the following user exit applies XSLT on an existing XML message: } /** * Apply XSLT transform to the output message * @throws UserExitException */ private void applyXslt(EventServerIF eventServer.getEventServer().createXmlOutput(p_Event).

} See also: “To create an XML message and apply XSLT” To create an XML message and apply XSLT 1. The string of parameter values cannot exceed 255 characters in length. Ensure you have created at least one source table to XML message destination mapping within this subscription. For example. InfoSphere CDC Event Server runs the user exit before applying a delete operation to a table you have staged and/or before applying a delete operation to a JMS message destination. The values you type in this box are free-form. Choose Java Class from the User Exit Type box. Configuring user exits for InfoSphere CDC Event Server 225 . Enable the Before check box for one or more of the following operations: Option Insert Description InfoSphere CDC Event Server runs the user exit before applying an insert operation to a table you have staged and/or before applying an insert operation to a JMS message destination. 2. InfoSphere CDC Event Server runs the user exit before applying an update operation to a table you have staged and/or before applying an update operation to a JMS message destination. 6. type: 8. In the Class Name box. Click the User Exits tab. Click Apply. you may have imported the EventServerIF interface. You can access the parameters in the Java class by invoking the getParameter() method during the initialization process. 4. 7. Update Delete 10. Click Configuration → Datastores. 9. type the Java class name of the user exit that implements the UserExitIF interface if you have developed the user exit in Java. p_Event). Select the table mapping and right-click Edit Mapping Details. Ensure you have created a subscription that uses the Event Server datastore as the target database. There are no conventions for specifying the parameters. Click Configuration → Subscriptions. } return retValue.applyXslt(eventServer. and the Java class user exit that implements this interface in your function has the following definition: public class UE1 implements UserExitIF. 5. Type the parameters that you want to make available to the user exit program in the Parameter box. Ensure you are connected to an Event Server datastore. In the Class Name box. 3.

see http://java. Ensure you have created a subscription that uses the Event Server datastore as the target database. 2.You can start mirroring on the subscription that contains the source table assigned to a JMS message destination. Choose Java Class from the User Exit Type box. type: 8. For example. The values you type in this box are free-form. For an example of a user exit that sends to a different JMS message destination.html.com/ products/jms/javadoc-102a/index. The user exit program will set the new destination before InfoSphere CDC Event Server applies the operation to a JMS message destination. Ensure you are connected to an Event Server datastore. Related concepts “Sending XML messages to a JMS message destination” on page 199 “Creating XML output and applying XSLT to an XML message” on page 224 “Configuring user exits for InfoSphere CDC Event Server” on page 221 Sending XML messages to multiple JMS message destinations You can send an XML message to a different JMS queue or topic than the one you configured in InfoSphere CDC Event Server using standard Java methods. See also: “To send an XML message to a different JMS message destination” To send an XML message to a different JMS message destination 1. Type the parameters that you want to make available to the user exit program in the Parameter box. 6. For more information. see SampleUserExit2. In the Class Name box. 4. you may have imported the EventServerIF interface. Click the User Exits tab. Click Configuration → Subscriptions. 5. You can access the parameters in the Java class by invoking the getParameter() method during the initialization process. 226 InfoSphere Change Data Capture Management Console: Administration Guide . and the Java class user exit that implements this interface in your function has the following definition: public class UE1 implements UserExitIF. 7.sun.java located in the samples folder or directory of your InfoSphere CDC Event Server installation. In the Class Name box. There are no conventions for specifying the parameters. This lets you override the JMS message destination you selected when configuring InfoSphere CDC. Ensure you have created at least one source table to XML message destination mapping within this subscription. Click Configuration → Datastores. 3. You need to create the JMS destination you want to send the XML message to using Java JMS methods. type the Java class name of the user exit that implements the UserExitIF interface if you have developed the user exit in Java. The string of parameter values cannot exceed 255 characters in length. Select the table mapping and right-click Edit Mapping Details.

you can call a web service with InfoSphere CDC Event Server. The user exit program will set the new destination before InfoSphere CDC Event Server applies the operation to a JMS message destination. By developing a user exit. Update Delete 10. For an example of a user exit that queries a Web service. Configuring user exits for InfoSphere CDC Event Server 227 . You can access content from the Web service application to include it in an XML message you configured with InfoSphere CDC Event Server.java located in the samples folder or directory of your InfoSphere CDC Event Server installation. InfoSphere CDC Event Server runs the user exit before applying a delete operation to a table you have staged and/or before applying a delete operation to a JMS message destination. Ensure you have created a subscription that uses the Event Server datastore as the target database. see SampleUserExit3. Ensure you are connected to an Event Server datastore. You can start mirroring on the subscription that contains the source table assigned to a JMS message destination. Enable the Before check box for one or more of the following operations: Option Insert Description InfoSphere CDC Event Server runs the user exit before applying an insert operation to a table you have staged and/or before applying an insert operation to a JMS message destination. For example. 2. Click Configuration → Datastores. Click Configuration → Subscriptions. See also: “To query a Web service to access content” To query a Web service to access content 1.9. Related concepts “Sending XML messages to a JMS message destination” on page 199 “Sending XML messages to multiple JMS message destinations” on page 226 “Configuring user exits for InfoSphere CDC Event Server” on page 221 Querying a Web service to access content You can query a Web service using standard Java methods. you may be using a web service application to keep track of new customers that have just registered online. Click Apply. InfoSphere CDC Event Server runs the user exit before applying an update operation to a table you have staged and/or before applying an update operation to a JMS message destination.

Enable the Before check box for one or more of the following operations: Option Insert Description InfoSphere CDC Event Server runs the user exit before applying an insert operation to a table you have staged and/or before applying an insert operation to a JMS message destination. InfoSphere CDC Event Server runs the user exit before applying a delete operation to a table you have staged and/or before applying a delete operation to a JMS message destination. you may have imported the EventServerIF interface. 228 InfoSphere Change Data Capture Management Console: Administration Guide . type: 8. Ensure you have created at least one source table to XML message destination mapping within this subscription. 5. and the Java class user exit that implements this interface in your function has the following definition: public class UE1 implements UserExitIF. For example. The user exit program will set the new destination before InfoSphere CDC Event Server applies the operation to a JMS message destination. 7. 6. Type the parameters that you want to make available to the user exit program in the Parameter box. You can access the parameters in the Java class by invoking the getParameter() method during the initialization process. Related concepts “Sending XML messages to a JMS message destination” on page 199 “Querying a Web service to access content” on page 227 “Configuring user exits for InfoSphere CDC Event Server” on page 221 Content based routing You can develop a user exit that lets you send an XML message to a specific JMS message destination based on the content of the message. Click the User Exits tab. There are no conventions for specifying the parameters.3. In the Class Name box. Select the table mapping and right-click Edit Mapping Details. Click Apply. InfoSphere CDC Event Server runs the user exit before applying an update operation to a table you have staged and/or before applying an update operation to a JMS message destination. Choose Java Class from the User Exit Type box. The values you type in this box are free-form. The string of parameter values cannot exceed 255 characters in length. You can start mirroring on the subscription that contains the source table assigned to a JMS message destination. 9. In the Class Name box. type the Java class name of the user exit that implements the UserExitIF interface if you have developed the user exit in Java. Update Delete 10. 4.

Type the parameters that you want to make available to the user exit program in the Parameter box. In the Class Name box. type the Java class name of the user exit that implements the UserExitIF interface if you have developed the user exit in Java. 9.Employee table and create an source table to XML mapping using all columns from this table. In the Class Name box. InfoSphere CDC Event Server runs the user exit before applying an update operation to a table you have staged and/or before applying an update operation to a JMS message destination. Choose Java Class from the User Exit Type box. 2. 4. Click Configuration → Subscriptions. See also: “To route the content of an XML message to another JMS message destination” To route the content of an XML message to another JMS message destination 1. Update Configuring user exits for InfoSphere CDC Event Server 229 . you may want to create a simple XML message whenever a new employee is created. 5. Ensure you are connected to an Event Server datastore. For example. Ensure you have created a subscription that uses the Event Server datastore as the target database.For example. Ensure you have created at least one source table to XML message destination mapping within this subscription. The values you type in this box are free-form. Select the table mapping and right-click Edit Mapping Details. you may have imported the EventServerIF interface. 3. 7. Click Configuration → Datastores. You can then send the XML message to a JMS queue called ″HR1″ and also send this XML message to another queue called ″IT1″ each time a new employee is added to the IT department. and the Java class user exit that implements this interface in your function has the following definition: public class UE1 implements UserExitIF. There are no conventions for specifying the parameters. Click the User Exits tab. Enable the Before check box for one or more of the following operations: Option Insert Description InfoSphere CDC Event Server runs the user exit before applying an insert operation to a table you have staged and/or before applying an insert operation to a JMS message destination. The string of parameter values cannot exceed 255 characters in length. type: 8. 6. You can detect new employees by monitoring inserts into the dbo. You can access the parameters in the Java class by invoking the getParameter() method during the initialization process.

Click Apply. 10. The user exit program will set the new destination before InfoSphere CDC Event Server applies the operation to a JMS message destination. Related concepts “Sending XML messages to multiple JMS message destinations” on page 226 “Content based routing” on page 228 “Configuring user exits for InfoSphere CDC Event Server” on page 221 230 InfoSphere Change Data Capture Management Console: Administration Guide . You can start mirroring on the subscription that contains the source table assigned to a JMS message destination.Option Delete Description InfoSphere CDC Event Server runs the user exit before applying a delete operation to a table you have staged and/or before applying a delete operation to a JMS message destination.

you will learn: “About the state and status of your subscriptions” “Displaying event messages during replication” on page 232 “Profiling the latency and throughput performance of your subscription” on page 235 “Displaying a graphical view of your subscription” on page 238 Related concepts “Setting notifications” on page 69 “Disk resource system parameters” on page 386 About the state and status of your subscriptions State and status information help you determine if a subscription is behaving the way you expect. In this section. You can view messages for each subscription and datastore in your replication configuration. State information will tell you if your subscription is inactive or if it is replicating. v Examine the amount of latency for a subscription. Status information will tell you if replication is behaving normally or if there is an error. The Monitoring perspective lets you diagnose potential problems by allowing you to: v View the replication state and status for your subscriptions.Monitoring your subscriptions After configuring your replication environment and starting replication for your subscriptions. you can look at the subscription’s status to see if it is Normal or if Management Console is reporting an error. 2008 231 . See also: “Subscription state” on page 232 “Subscription status” on page 232 Related concepts “Displaying event messages during replication” on page 232 © Copyright IBM Corp. You can set latency thresholds and notifications for your subscriptions to help you determine when latency is becoming a problem. you can monitor and analyze replication activities for each subscription in the Monitoring perspective. v Depending on the platform on which you have InfoSphere CDC. If the status of the subscription is Error. v Check system messages and events that relate to a subscription or a datastore in the Event Log view. if you start mirroring for a subscription and the state of the subscription remains Inactive. you can inspect the Event Log view for the subscription to see if there is a problem. you can to set a DEADBAND PERCENTAGE system parameter to greater than zero on your target datastore if you want InfoSphere CDC to apply padding around your latency threshold. state and status work together to provide you with information you need to monitor replication activity. For example. In this way.

Subscription state Subscriptions configured in Management Console can be in one of the following states: v Starting—Indicates that InfoSphere CDC is starting replication for the subscription. v Unknown—Indicates that InfoSphere CDC cannot determine the state of the subscription. This may be a result of a lack of communication between the monitoring process and the datastores. v Unknown—Indicates that InfoSphere CDC cannot determine the status of the subscription. v Refresh—Indicates that InfoSphere CDC is refreshing data from the source to the target. You can use the Event Log view to monitor and diagnose any errors that occur during replication. Mirror Net Change—Indicates that InfoSphere CDC is mirroring changes that were made to the source since replication last ended. This may be a result of a lack of communication between the monitoring process and the datastores. v Ending—Indicates that InfoSphere CDC is close to completing replication activity on the subscription and is in the process of shutting down. Related concepts “Starting mirroring on a subscription” on page 197 “Setting up subscriptions for datastores outside of your organization” on page 86 v Subscription status Subscriptions configured in Management Console can have one of the following statuses: v Normal—Indicates that the subscription is normal and there are no known problems. v Mirror Continuous—Indicates that InfoSphere CDC is mirroring data between the source and target. This occurs when you have started continuous mirroring on the subscription. After completing the refresh. you can do the following: v View events generated by specific subscriptions or datastores. InfoSphere CDC ends replication after the changes are mirrored to the target. or your subscription is using an external source datastore. It allows you to monitor and/or identify problems with the replication activity of your subscriptions. depending on the replication method that you have selected for the subscription. or your subscription is using an external source datastore. v Error—Indicates that a problem is preventing InfoSphere CDC from replicating data on the subscription. InfoSphere CDC starts mirroring the subscription or returns to a state of Inactive. v Filter events based on severity. Related concepts “Displaying event messages during replication” Displaying event messages during replication The Event Log view lets you view events and messages generated by InfoSphere CDC during replication activities. With the Event Log view. 232 InfoSphere Change Data Capture Management Console: Administration Guide . v Inactive—Indicates that InfoSphere CDC is not replicating data on the subscription.

Click Monitoring → Subscriptions. For example. Displays events generated by the subscription on the source datastore. These events do not indicate that an error has occurred. Displays events generated by the target datastore. Related concepts “Displaying event messages during replication” on page 232 To view event details 1. Click Monitoring → Subscriptions. Select a subscription and right-click Show Event Log. v Clear the Event Log view of messages that you no longer need to investigate. 3. See also: “To show the event log for a subscription” “To view event details” “To copy events” on page 234 “To clear events” on page 234 “To export events” on page 235 To show the event log for a subscription 1. Monitoring your subscriptions 233 . 2. you may want to copy an event into an email for technical support reasons. Select a subscription and right-click Show Event Log. Select one of the following options from the Log list: Option Source General Source Replication Target General Target Replication Description Displays events generated by the source datastore. v Error or Escape—these events describe an error that InfoSphere CDC has detected. which alerts you about a potential error.Copy events. or explain conditions that led to InfoSphere CDC shutting down. v The Event Log view displays the following four categories of events which are listed by increasing severity: v Information—these events provide feedback about InfoSphere CDC operations. v Warning or Notice—these events describe situations that InfoSphere CDC has detected. v Diagnostic—these events contain information that helps you diagnose or solve a problem that may occur as a result of a certain action or operation. You can then paste the event into another application. 2. v Export events to your local computer. Displays events generated by the subscription on the target datastore.

4. 3. 234 InfoSphere Change Data Capture Management Console: Administration Guide . Displays events generated by the target datastore. Displays events generated by the target datastore. Displays events generated by the subscription on the source datastore. Click Monitoring → Subscriptions. Select a subscription and right-click Show Event Log. Select a subscription and right-click Show Event Log. 3.3. 4. Displays events generated by the target datastore. 2. Select one of the following options from the Log list: Option Source General Source Replication Target General Target Replication Description Displays events generated by the source datastore. Click Monitoring → Subscriptions. Displays events generated by the subscription on the target datastore. Related concepts “Displaying event messages during replication” on page 232 To clear events 1. Displays events generated by the subscription on the source datastore. Select one of the following options from the Log list: Option Source General Source Replication Target General Target Replication Description Displays events generated by the source datastore. Select one of the following options from the Log list: Option Source General Source Replication Target General Target Replication Description Displays events generated by the source datastore. Right-click in the list of events and select Copy Events. Related concepts “Displaying event messages during replication” on page 232 To copy events 1. Displays events generated by the subscription on the target datastore. Displays events generated by the subscription on the source datastore. Right-click in the list of events and select Event Details. 2. Displays events generated by the subscription on the target datastore.

Note: If you have installed InfoSphere CDC for Microsoft SQL Server. develop a performance baseline to determine how replication behaves with a workload that is typical for your applications and topology. To resolve this problem.4. After you have established baseline numbers for latency. It is up to you to decide how much latency you are willing to tolerate in your environment. Use the Statistics View to determine typical numbers for latency and throughput. You are prompted to save the list of events in a formatted text file to your local computer. 5. contact your network administrator. Displays events generated by the target datastore. if an application inserts a row into the source table at 10:00 and InfoSphere CDC applies that row to the target table at 10:15. Monitoring your subscriptions 235 . Right-click in the list of events and select Clear Events. Click Monitoring → Subscriptions. 2. Select one of the following options from the Log list: Option Source General Source Replication Target General Target Replication Description Displays events generated by the source datastore. 4. Select a subscription and right-click Show Event Log. you must set the registry entry (AllowEventLogClear in HKEY_LOCAL_MACHINE\ Software\DataMirror\InfoSphere CDC\SQL Server###BOT_TEXT###lt;TS_instance_name>\Agent) to 1. Related concepts “Displaying event messages during replication” on page 232 To export events 1. then the latency for the subscription is 15 minutes. Replication performance can be measured along the following two dimensions: Latency InfoSphere CDC measures latency as the amount of time that passes between when data changes on a source table and when it changes on the target table. Displays events generated by the subscription on the source datastore. set latency notifications and thresholds. A subscription can experience latency in the following situations: v Insufficient network bandwidth for the volume of transactions that you are processing. Displays events generated by the subscription on the target datastore. Related concepts “Displaying event messages during replication” on page 232 Profiling the latency and throughput performance of your subscription After you configure mapping details on a subscription. This increases the amount of time between changes on the source table and the same change on the target table. Right-click in the list of events and select Export Events. 3. For example.

To receive accurate latency statistics on a subscription. Ensure that you have set a latency threshold on the subscription. Collect Statistics. This will likely result in increased latency for a subscription until these processes are complete. 4. See also: “To start profiling the performance of a subscription” “To stop profiling the performance of a subscription” on page 237 “To view and save plotted performance statistics of a subscription” on page 237 Related concepts “Setting latency thresholds and notifications” on page 78 Related tasks “To set a latency threshold and notification” on page 79 To start profiling the performance of a subscription 1. v Database lock contention on the target database. then click Show Statistics and click Save Data.v A large refresh is occurring. v Resource intensive batch jobs or background tasks on the source or target. The plotted graph is saved in . Throughput The amount of replication activity (measured in the number of operations or size of data) a system can sustain over time.csv format to your local computer. forcing InfoSphere CDC to wait for the locks to be released. Related concepts “Starting mirroring on a subscription” on page 197 “Profiling the latency and throughput performance of your subscription” on page 235 Related tasks “To set a latency threshold and notification” on page 79 “To view and save plotted performance statistics of a subscription” on page 237 “To start profiling the performance of a subscription” 236 InfoSphere Change Data Capture Management Console: Administration Guide . An application such as a reporting system on the target database may unexpectedly lock data in the database. InfoSphere CDC calculates latency based on your system time and the offset from Coordinated Universal Time (UTC). If you want to save the collected statistics as a plotted graph. you will see a timestamp that indicates when you started profiling the performance of the subscription. Click Monitoring → Subscriptions. Note: For each machine where you have installed InfoSphere CDC. make sure that your system time is synchronized and that the time zone matches the time zone of your region. Note: If you click Show Statistics to view the plotted graph. v InfoSphere CDC is replicating tables with Large Objects (LOB). The large size of the table rows may increase latency for a subscription. 3. Ensure that you have started mirroring on the subscription you want to profile. 2. make sure these settings are correct. 5. Right-click on a subscription and select Statistics.

You will only lose performance statistics if you stop and restart collecting statistics on the same subscription. Monitoring your subscriptions 237 . Indicates the average amount of time a subscription has experienced latency since you opened the Statistics View. 3. InfoSphere CDC maintains the performance statistics that were collected prior to ending mirroring. Right-click on a subscription and select Statistics. then click Show Statistics and click Save Data. Depending on the version of InfoSphere CDC you have installed and which database platform you are using. you can also view throughput information for the subscription. The plotted graph is saved in . Notes: v If you click Show Statistics to view the plotted graph. Right-click on a subscription and select Show Statistics. you will see a timestamp that indicates when you stopped profiling the performance of the subscription. Indicates the least amount of time a subscription has experienced latency since you opened the Statistics View. Click Monitoring → Subscriptions. Click Monitoring → Subscriptions. 2. Related concepts “Profiling the latency and throughput performance of your subscription” on page 235 Related tasks “To view and save plotted performance statistics of a subscription” “To start profiling the performance of a subscription” on page 236 To view and save plotted performance statistics of a subscription 1. v If you decide to stop collecting statistics and end mirroring on the subscription. Indicates the highest amount of time a subscription has experienced latency since you opened the Statistics View.To stop profiling the performance of a subscription 1. High Low Average Throughput Depending on the InfoSphere CDC product you have installed. you can view the following performance statistics: Latency Option Current Description Indicates the amount of time the subscription is latent in replicating data to the target. Do Not Collect Statistics. 2. If you want to save the collected statistics as a plotted graph.csv format to your local computer. 3.

If you want to save and export the graph in . select one of the following from the list: Option Latency Throughput Operation/second Description Displays a graph that illustrates the latency of your subscription. Throughput Bytes/second 5. You should see a graph that plots performance for the subscription. Indicates the average rate of throughput for the subscription since you opened the Statistics view. Throughput is the amount of data (in bytes) or the number of operations that InfoSphere CDC applies on the target database process per second. Displays a graph that illustrates the amount of data (in bytes) that InfoSphere CDC applies to the target database per second.Option Current Description Indicates the current rate of throughput for the subscription since you opened the Statistics view. you may find that the Replication Diagram view is a useful visual alternative to the Subscriptions view which displays the same information in a grid format. Throughput is the amount of data (in bytes) or the number of operations that InfoSphere CDC applies on the target database process per second. 6. Indicates the highest rate of throughput for the subscription since you opened the Statistics view. Throughput is the amount of data (in bytes) or the number of operations that InfoSphere CDC applies on the target database process per second. Displays a graph that illustrates the number of operations that InfoSphere CDC applies to the target database per second.csv format. Throughput is the amount of data (in bytes) or the number of operations that InfoSphere CDC applies on the target database process per second. In the Graph area. then click Save Data. High Low Average 4. Related concepts “Setting latency thresholds and notifications” on page 78 “Displaying event messages during replication” on page 232 Displaying a graphical view of your subscription The Replication Diagram view in the Monitoring perspective uses a schematic diagram to visually represent the relationship between subscriptions and datastores in your replication configuration. When monitoring your subscriptions. Indicates the lowest rate of throughput for the subscription since you opened the Statistics view. 238 InfoSphere Change Data Capture Management Console: Administration Guide .

v Determine the source and target datastore for a subscription by examining the arrows that point to the target datastore. start a refresh. Monitoring your subscriptions 239 .In the Replication Diagramview. and view properties. v Right-click a subscription to start or stop replication. and show related subscriptions. you can do the following: v Monitor the activity of subscriptions in a specific project by using the project list in the toolbar. show table mappings. v View state. view properties. and latency information for each subscription. status. v Right-click a datastore to connect to a datastore. set a subscription notification. set a datastore notification.

240 InfoSphere Change Data Capture Management Console: Administration Guide .

You can also modify WebSphere DataStage properties for the subscription that control the number of changed rows and the amount of time elapsed before subscription data is sent to WebSphere DataStage. 2008 241 . See also: “Adding a subscription for WebSphere DataStage” “Mapping tables to WebSphere DataStage” on page 242 “Customizing your WebSphere DataStage table mappings” on page 242 “Generating a WebSphere DataStage Definition File” on page 242 “Creating a custom data format for WebSphere DataStage” on page 242 Adding a subscription for WebSphere DataStage You must add a subscription that uses InfoSphere CDC for WebSphere DataStage as a target datastore. Management Console lets you manage the source tables you want to replicate and provides you with mapping options to map your source tables according to your replication requirements. For more information on how to do this. you must do the following: 1. see “Setting up subscriptions” on page 83. You can also customize the data based on your business requirements.Using InfoSphere CDC with IBM WebSphere DataStage With InfoSphere CDC for WebSphere DataStage you can replicate data to IBM WebSphere DataStage based on table mapping details configured in InfoSphere CDC Management Console. Related concepts “Setting up subscriptions” on page 83 © Copyright IBM Corp. you will learn: “Before configuring InfoSphere CDC for WebSphere DataStage” “Configuring InfoSphere CDC to send data to WebSphere DataStage” “Starting replication in Management Console” on page 243 Before configuring InfoSphere CDC for WebSphere DataStage Before configuring InfoSphere CDC for WebSphere DataStage in Management Console. Install and configure InfoSphere CDC for WebSphere DataStage. Related tasks “To add a new datastore” on page 24 Configuring InfoSphere CDC to send data to WebSphere DataStage There are several configuration tasks that are required in InfoSphere CDC Management Console before you can send data to WebSphere DataStage. see your InfoSphere CDC for WebSphere DataStage End-User Documentation. In this section. 2. Create a datastore in Management Console. For more information on how to add a subscription in Management Console.

you can generate a WebSphere DataStage definition file (*. you can customize the data that is being sent to WebSphere DataStage. The results of the expression are sent to the target system.“Setting properties for a subscription that targets IBM WebSphere DataStage” on page 89 Mapping tables to WebSphere DataStage After adding a subscription. v Filtering Rows and Columns—You can include or exclude rows or columns for replication. Related concepts “Mapping using WebSphere DataStage” on page 106 Customizing your WebSphere DataStage table mappings After mapping your tables to WebSphere DataStage. Functionality that is not available for WebSphere DataStage table mappings is not displayed or disabled. IBM WebSphere DataStage.dsx) that creates a job sequence and two utility routines in WebSphere DataStage. You can import this file into IBM WebSphere DataStage Designer and then customize it to meet your business requirements. Note: When customizing your WebSphere DataStage table mappings in Management Console. For more information about running a WebSphere DataStage job. the the DSX file that is generated by Management Console and imported into WebSphere DataStage may no longer 242 InfoSphere Change Data Capture Management Console: Administration Guide . and specifying how InfoSphere CDC converts character sets on source columns during replication: v Derived Columns—With a derived column you can create an expression that is evaluated by InfoSphere CDC on a source column. By customizing the data. see your WebSphere DataStage documentation. you have the option of customizing your table mappings by creating derived columns. You can create as many table mappings as you feel necessary. Related concepts “Setting multibyte and Unicode character set conversions” on page 175 “Filtering rows and columns” on page 167 Related tasks “To add a derived column” on page 163 Generating a WebSphere DataStage Definition File After mapping one or more source tables. v Multibyte and Unicode Character Set Conversions—You can specify how InfoSphere CDC converts character sets on source columns during replication. Related concepts “Generating a WebSphere DataStage definition file for a subscription” on page 90 Creating a custom data format for WebSphere DataStage By specifying a Java class. you must map one or more source tables to the target system. you will have access to a sub-set of functionality that is normally available for database targets. WebSphere DataStage. and this may depend on the number of tables that you want to replicate to the target system. filtering rows and columns.

you are responsible for ensuring that the DSX file is still relevant in WebSphere DataStage. If you customize the data that is sent to WebSphere DataStage. For the appropriate way to start and stop subscriptions and WebSphere DataStage jobs. Related concepts “Starting and ending replication on subscriptions” on page 197 Using InfoSphere CDC with IBM WebSphere DataStage 243 . see your InfoSphere CDC for WebSphere DataStage documentation.be relevant. Related concepts “Creating a custom data format for IBM WebSphere DataStage” on page 220 Starting replication in Management Console You can start replication for a subscription that uses InfoSphere CDC for WebSphere DataStage like any other subscription in Management Console.

244 InfoSphere Change Data Capture Management Console: Administration Guide .

who made the change. To capture this information for each row in a table on the target system. the database records the change in a log entry that contains the changed data plus extra information about what type of change was made. v If you have installed InfoSphere CDC for z/OS and you want to build an expression with &MEMBER. InfoSphere CDC makes the extra log entry information available through journal control fields. you can add a column to the table and map that column to the appropriate journal control field. v InfoSphere CDC does not support the mapping of journal control fields to LOB columns in a target table. and when the change was made. For more information. See also: “Commit Cycle ID (&CCID)” on page 246 “Source RRN (&CNTRRN)” on page 246 “Entry Type Code (&CODE)” on page 247 “Entry Type (&ENTTYP)” on page 247 “Source Job Name (&JOB)” on page 248 © Copyright IBM Corp. InfoSphere CDC replicates the log information from the source system and applies this information to the mapped columns on your target system. Depending on the source and target database vendors. you should consider the following: v If you have installed InfoSphere CDC Version 5. see the appropriate User Exits section for your platform.2 or higher.Using journal control fields for auditing replication activities In this section. some journal control fields may or may not be supported. You can also include journal control fields in row selection and derived expressions. You can map journal control fields to columns on the target system. InfoSphere CDC replicates the changed data along with the extra log entry information to the target system. some journal control fields contain non-character data. InfoSphere CDC provides many journal control fields that contain log entries from your source systems. When a change is made on the source system. For example. you may want to maintain when the last replicated change was applied to each row in a table on the source system. InfoSphere CDC converts these values to character data before they are passed to a user exit program. then you need to enclose this journal control field in single quotes. v Depending on the type of platform you have installed InfoSphere CDC and the replication method (mirror or refresh). you will learn: “About journal control fields” “About journal codes” on page 257 “Translating journal codes into meaningful information” on page 259 About journal control fields Journal control fields provide information about the log entry on the source system. When a relevant log entry triggers a replication event to the target system. Before using a journal control field. 2008 245 .

x) InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. Data Type—Integer (InfoSphere CDC 5. If you decide to use this journal control field when refreshing data.“Source Job Number (&JOBNO)” on page 249 “Source Job User (&JOBUSER)” on page 250 “Journal Name (&JOURNAL)” on page 250 “Source Table Library (&LIBRARY)” on page 251 “Source Table Member Name (&MEMBER)” on page 252 “Source Table Name (&OBJECT)” on page 252 “Source Program Name (&PROGRAM)” on page 253 “Journal Sequence Number (&SEQNO)” on page 254 “Source Server Name (&SYSTEM)” on page 254 “Record Modification Time (&TIMESTAMP)” on page 255 “Record Modification User (&USER)” on page 256 Commit Cycle ID (&CCID) An identifier for the transaction with the update. InfoSphere CDC sets this journal control field to a default value of 0. 246 InfoSphere Change Data Capture Management Console: Administration Guide . journal control fields may or may not be supported when mirroring or refreshing data. journal control fields may or may not be supported when mirroring or refreshing data. When refreshing data. InfoSphere CDC sets this journal control field to a default value of 0. and is not available when mirroring data. If you decide to use this journal control field when mirroring data. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC refreshes data. Source RRN (&CNTRRN) The relative record number of the source table that recorded the journal entry. Data Type—Integer (InfoSphere CDC 5. InfoSphere CDC sets this journal control field to a default value of 1. If you decide to use this journal control field when refreshing data. and is not available when refreshing data. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. v InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is not available. and is not available when refreshing data. and is not available when mirroring data. InfoSphere CDC sets this journal control field to a default value of 0. v InfoSphere CDC for z/OS—Support for this journal control field is available only when InfoSphere CDC mirrors data. v InfoSphere CDC for DB2 UDB—Support for this journal control field is available only when refreshing data.x) InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products.

v InfoSphere CDC for AS/400—Support for this journal control field is available only when mirroring data. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. and is not available when refreshing data. For more information. InfoSphere CDC sets this journal control field to a default value of 0. and is not available when mirroring data. Entry Type (&ENTTYP) Indicates the type of update. v InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is available only when InfoSphere CDC refreshes data. If you decide to use this journal control field when mirroring data. If you decide to use this journal control field when mirroring data. v InfoSphere CDC for z/OS—Support for this journal control field is not available. For each journal entry code there are one or more possible journal entry types that provide more detailed information about the entry. v InfoSphere CDC for z/OS—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. If you decide to use this journal control field when mirroring data. and is not available when mirroring data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC refreshes data. Entry Type Code (&CODE) The code that identifies the type of journal entry. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. v InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. journal control fields may or may not be supported when mirroring or refreshing data. If you decide to use this journal control field when refreshing data. InfoSphere CDC sets this journal control field to a default value of 0. you can use a journal entry type to label each audit Using journal control fields for auditing replication activities 247 .v InfoSphere CDC for AS/400—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. see “Using journal control fields for auditing replication activities” on page 245. and is not available when mirroring data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. InfoSphere CDC sets this journal control field to a default value of U on the subscriber. When refreshing data. InfoSphere CDC sets this journal control field to a default value of R. InfoSphere CDC sets this journal control field to NULL. For example. v InfoSphere CDC for DB2 UDB—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. You can use journal entry types for auditing events that occur between your source and target tables. v InfoSphere CDC for DB2 UDB —Support for this journal control field is available only when InfoSphere CDC refreshes data. ″U″ for refresh and ″R″ for mirror.

v InfoSphere CDC for Microsoft SQL Server (V5. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. and is not available when refreshing data. If you decide to use this journal control field when 248 InfoSphere Change Data Capture Management Console: Administration Guide . InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. This is represented by a distinct two-letter code. journal control fields may or may not be supported when mirroring or refreshing data. journal control fields may or may not be supported when mirroring or refreshing data. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. If you decide to use this journal control field when refreshing data. InfoSphere CDC sets this journal control field to NULL. If you decide to use this journal control field when refreshing data.3)—Support for this journal control field is not available. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. this journal control field contains data that is not consistent with the defined contents of the journal control field. v InfoSphere CDC for DB2 UDB—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. this journal control field contains the program that performed the operation on the source table. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. If you decide to use this journal control field when refreshing data. InfoSphere CDC leaves this journal control field empty. v Source Job Name (&JOB) The name of the job that made the update on the source system.record with the event that occurred on your source table that caused the audit record to be written to the target table. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data. If you decide to use this journal control field when mirroring data. InfoSphere CDC sets this journal control field to UNKNOWN on the subscriber. When mirroring data. and is not available when refreshing data. v InfoSphere CDC for z/OS—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. and is not available when refreshing data. InfoSphere CDC sets this journal control field to a default value of RR on the subscriber. v InfoSphere CDC for Microsoft SQL Server (V6. v InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data.0)—Support for this journal control field is not available. If you decide to use this journal control field when refreshing data.

If you decide to use this journal control when refreshing data. InfoSphere CDC leaves this journal control field empty. If you decide to use this journal control field when mirroring data. and is not available when refreshing data. InfoSphere CDC leaves this journal control field empty. If you decide to use this journal control field when mirroring data. v InfoSphere CDC for DB2 UDB—Support for this journal control field is not available. If you decide to use this journal control field when refreshing data. and is not available when refreshing data. Using journal control fields for auditing replication activities 249 . InfoSphere CDC sets this journal control field to 000000. v InfoSphere CDC for z/OS—Support for this journal control field is not available. InfoSphere CDC sets this journal control field to NULL. When mirroring data. Source Job Number (&JOBNO) The operating system user ID of the update process. If you decide to use this journal control field when refreshing data. this journal control field contains the process ID (UNIX) and the process name (Windows) that performed the operation on the source table. InfoSphere CDC sets this journal control field to a default value of 0 on the subscriber. InfoSphere CDC sets this journal control field to a default value of 0. v InfoSphere CDC for z/OS—Support for this journal control field is available only when InfoSphere CDC mirrors data. If you decide to use this journal control field when refreshing data. InfoSphere CDC sets this journal control field to 000000. If you decide to use this journal control field when refreshing data. When mirroring data. InfoSphere CDC leaves it empty. InfoSphere CDC sets this journal control field to InfoSphere CDC. v InfoSphere CDC for Microsoft SQL Server (V5. If you decide to use this journal control field when refreshing data. and is not available when refreshing data. If you decide to use this journal control field when refreshing data. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products.mirroring data.0)—Support for this journal control field is not available. It is usually the name of the job that created the Logical Unit of Work. If you decide to use this journal control field when mirroring data. When mirroring data. v InfoSphere CDC for DB2 UDB—Support for this journal control field is not available. The Correlation ID is an internal DB2 identifier. InfoSphere CDC leaves it empty. InfoSphere CDC sets this journal control field to InfoSphere CDC. this journal control field contains the Logical Unit of Work’s Correlation ID. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. InfoSphere CDC sets this journal control field to 000000. If you decide to use this journal control field when refreshing data.3)—Support for this journal control is not available. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data. journal control fields may or may not be supported when mirroring or refreshing data. v InfoSphere CDC for Microsoft SQL Server (V6. If you decide to use this journal control field when mirroring data. the journal control field contains an empty string. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. InfoSphere CDC leaves this journal control field empty.

InfoSphere CDC sets this journal control field to UNKNOWN on the subscriber. v InfoSphere CDC for z/OS—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. this journal control field contains the User ID of the InfoSphere CDC address space. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. InfoSphere CDC sets this journal control field to TS. the high byte of this journal control field identifies the name of the journal. this journal control field contains the Authorization ID that the job used to connect to DB2. If you decide to use this journal control field when mirroring or refreshing data.3)—Support for this journal control field is not available. When mirroring data. When mirroring data. and is not available when refreshing data. If you decide to use this journal control field when refreshing data. InfoSphere CDC sets this journal control field to NULL. Journal Name (&JOURNAL) The name of the journal.Source Job User (&JOBUSER) The operating system user at the time of the update. and the low byte of this field identifies the library where it resides. journal control fields may or may not be supported when mirroring or refreshing data. If you decide to use this journal control field when mirroring data. v InfoSphere CDC for Microsoft SQL Server (V5. The name is set to the database user that owns the InfoSphere CDC metadata tables. and is not available when refreshing data. this journal control field contains the name of the user that performed the operation on the source table. When refreshing data. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. InfoSphere CDC sets this journal control field to TS. v InfoSphere CDC for Microsoft SQL Server (V6. InfoSphere CDC leaves this journal control field empty. If you decide to use this journal control field when refreshing data. InfoSphere CDC sets this journal control field to the database user name on the subscriber. If you decide to use this journal control field when refreshing data. v InfoSphere CDC for DB2 UDB—Support for this journal control field is not available.0+)—Support for this journal control field is not available. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. Data Type—Character 250 InfoSphere Change Data Capture Management Console: Administration Guide . This is usually the User ID of the job. If you decide to use this journal control field when mirroring data. If you decide to use this journal control field when refreshing data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data. Depending on the version of InfoSphere CDC you install. InfoSphere CDC sets this journal control field to the database user name on the subscriber. The name is set to the database user that owns the InfoSphere CDC metadata tables. JRN1 LIB1. For example.

When mirroring data. InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is available only when InfoSphere CDC mirrors data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data.InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. If you decide to use this journal control field when refreshing data. If you decide to use this journal control field when refreshing data. v InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. If both the name and library are included in this journal control field. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. v InfoSphere CDC for AS/400—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. Using journal control fields for auditing replication activities 251 . v InfoSphere CDC for z/OS—Support for this journal control field is only available when InfoSphere CDC mirrors data. and is not available when refreshing data. InfoSphere CDC leaves this journal control field empty. If you decide to use this journal control field when refreshing data. InfoSphere CDC sets this journal control field to UNKNOWN on the subscriber. v InfoSphere CDC for DB2 UDB—Support for this journal control field is available only when InfoSphere CDC mirrors data. journal control fields may or may not be supported when mirroring or refreshing data. this journal control field contains the journal name in the format <schema>. journal control fields may or may not be supported when mirroring or refreshing data. and is not available when refreshing data. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. If you decide to use this journal control field when refreshing data. then &JRNLIB journal control field is not supported by InfoSphere CDC. v Source Table Library (&LIBRARY) The name of the source table schema or its alias. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data.<journal>. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. If you decide to use this journal control field when refreshing data. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. and is not available when refreshing data. and is not available when refreshing data. When mirroring data. it contains the journal name and journal library.<journal>. InfoSphere CDC leaves this journal control field empty. InfoSphere CDC sets this journal control field to NULL. and is not available when refreshing data. InfoSphere CDC sets this journal control field to a default value of N. and is not available when refreshing data. this journal control field contains the name of the DB2 subsystem or data sharing group to which InfoSphere CDC is connected. When mirroring data. this journal control field contains the journal name in the format <schema>. When mirroring data.

If you decide to use this journal control field when mirroring or refreshing data. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. v InfoSphere CDC for AS/400—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. the journal control field contains the database name in which the table was created and owner ID of the table in the format <dbname.v InfoSphere CDC for DB2 UDB—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. Source Table Name (&OBJECT) The name of the source table or its alias. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. When mirroring or refreshing data. When mirroring data. v InfoSphere CDC for Microsoft SQL Server (V5. InfoSphere CDC leaves this journal control field empty. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data. When mirroring or refreshing data.0)—Support for this journal control field is not available. When mirroring or refreshing data. this journal control field contains the name of the source table. v InfoSphere CDC for z/OS—Support for this journal control field is not available.3)—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. Source Table Member Name (&MEMBER) The name of the source table or its alias. v InfoSphere CDC for Microsoft SQL Server (V6. journal control fields may or may not be supported when mirroring or refreshing data. v InfoSphere CDC for AS/400—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. this journal control field contains the name of the source table. If you decide to use this journal control field when mirroring or refreshing data. 252 InfoSphere Change Data Capture Management Console: Administration Guide . and is not available when refreshing data. journal control fields may or may not be supported when mirroring or refreshing data. this journal control field contains the name of the source table. v InfoSphere CDC for DB2 UDB—Support for this journal control field is not available.owner>. InfoSphere CDC leaves this journal control field empty. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. v InfoSphere CDC for z/OS—Support for this journal control field is only available when InfoSphere CDC mirrors data.

InfoSphere CDC sets this journal control field to UNKNOWN.0)—Support for this journal control field is not available. InfoSphere CDC leaves this journal control field empty. this journal control field contains the DB2 plan name to which the user is connected. Using journal control fields for auditing replication activities 253 . v InfoSphere CDC for z/OS—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. If you decide to use this journal control field when mirroring data. When mirroring or refreshing data. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. and is not available when refreshing data. If you decide to use this journal control field when refreshing data. If you decide to use this journal control field when mirroring data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data. v InfoSphere CDC for z/OS—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. InfoSphere CDC sets this journal control field to UNKNOWN. v Source Program Name (&PROGRAM) The name of the program on the source system that made the update. If you decide to use this journal control field when refreshing data. When mirroring or refreshing data. InfoSphere CDC sets this journal control field to UNKNOWN on the subscriber. InfoSphere CDC leaves this journal control field empty. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. If you decide to use this journal control field when refreshing data. InfoSphere CDC leaves this journal control field empty. v InfoSphere CDC for Microsoft SQL Server (V6. this journal control field contains the program that performed the operation on the source table. and is not available when refreshing data. and is not available when refreshing data. When mirroring data. journal control fields may or may not be supported when mirroring or refreshing data.3)—Support for this journal control field is not available. InfoSphere CDC sets this journal control field to NULL v InfoSphere CDC for Microsoft SQL Server (V5. v InfoSphere CDC for DB2 UDB—Support for this journal control field is not available. A plan describes the SQL that accesses the tables. indices used and so on. this journal control field contains the name of the source table.InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data v InfoSphere CDC for DB2 UDB—Support for this journal control field is available only when InfoSphere CDC mirrors data. If you decide to use this journal control field when mirroring or refreshing data. paths. If you decide to use this journal control field when refreshing data.

this journal control field contains the sequence number. Source Server Name (&SYSTEM) The host name of the source system. 254 InfoSphere Change Data Capture Management Console: Administration Guide . Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. When mirroring data. If you decide to use this journal control field when refreshing data. If you decide to use this journal control field when refreshing data. If you decide to use this journal control field when mirroring or refreshing data. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. journal control fields may or may not be supported when mirroring or refreshing data. this journal control field contains the name of the source system. DB2 uses RBAs and LRSNs to keep track of log positions. v InfoSphere CDC for DB2 UDB—Support for this journal control field is not available. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available only when InfoSphere CDC mirrors data. this journal control field contains the RBA or LRSN integer. and is not available when refreshing data. v InfoSphere CDC for Oracle and Sybase—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. and is not available when refreshing data. If you decide to use this journal control field when mirroring or refreshing data. v InfoSphere CDC for z/OS—Support for this journal control field is only available when InfoSphere CDC mirrors data. v InfoSphere CDC for Microsoft SQL Server—Support for this journal control field is not available. InfoSphere CDC sets this journal control field to a default value of 0. When mirroring or refreshing data. InfoSphere CDC sets this journal control field to a default value of 0.x) InfoSphere CDC Support—depending on the InfoSphere CDC product that you install.Journal Sequence Number (&SEQNO) The sequence number of this update in the journal. When mirroring data. Data Type—Integer (InfoSphere CDC 5. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. and is not available when refreshing data. InfoSphere CDC sets this journal control field to relative record number on the target. v InfoSphere CDC for AS/400—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. InfoSphere CDC sets this journal control field to a default value of 0. If you decide to use this journal control field when refreshing data. v InfoSphere CDC for AS/400—Support for this journal control field is available only when InfoSphere CDC mirrors data. journal control fields may or may not be supported when mirroring or refreshing data. InfoSphere CDC sets this journal control field to NULL.

v InfoSphere CDC for AS/400—support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. Data Type—Timestamp (InfoSphere CDC 5. this journal control field contains the data and time of when InfoSphere CDC applied the operation to the source table. If you decide to use this journal control field when mirroring or refreshing data. this journal control field contains the system name on which InfoSphere CDC is running. the date and time format of this journal control field is YYYY-MM-DD-HH:MM:SS. or delete) to the source table. When refreshing data. Using journal control fields for auditing replication activities 255 . or delete) to the source table. When refreshing data. this journal control field contains the date and time of when InfoSphere CDC applied the row-level operation (insert. this journal control field contains the date and time of when InfoSphere CDC replicated the row in the source table. InfoSphere CDC leaves this journal control field empty.3)—support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. this journal control field contains the current date and time. this journal control field contains the date and time of when InfoSphere CDC applied the row-level operation (insert. v InfoSphere CDC for Microsoft SQL Server (V6. In environments that support microsecond precision. v InfoSphere CDC for Microsoft SQL Server (V6. this journal control field contains the date and time of when InfoSphere CDC refreshed the first row.UUUUUU. v InfoSphere CDC for Oracle and Sybase—support for this journal control field is available when InfoSphere CDC mirrors or refreshes data.0)—support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. When mirroring data. When mirroring data. v Record Modification Time (&TIMESTAMP) The date and time of when the update or refresh was made on the source. InfoSphere CDC leaves this journal control field empty. When refreshing data.InfoSphere CDC for Microsoft SQL Server (V5. Otherwise. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. v InfoSphere CDC for Microsoft SQL Server (V5.x) InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. The system name is extracted from the root control block (CVT) of the z/OS operating system. journal control fields may or may not be supported when mirroring or refreshing data.x)—Support for this journal control field is not available. this journal control field contains the date and time of when InfoSphere CDC applied the row-level operation (insert. update. this journal control field contains the current date and time. v InfoSphere CDC for DB2 UDB—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data v InfoSphere CDC for z/OS—Support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. When mirroring or refreshing data. When refreshing data. When mirroring data. When mirroring data. update. If you decide to use this journal control field when mirroring or refreshing data. v InfoSphere CDC for DB2 UDB—support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. When mirroring data. update. or delete) to the source table. InfoSphere CDC sets the microsecond component UUUUUU to zeroes or does not include it at all.x)—Support for this journal control field is not available.

v InfoSphere CDC for AS/400—support for this journal control field is available only when InfoSphere CDC mirrors data. InfoSphere CDC sets this journal control field to UNKNOWN on the subscriber. v InfoSphere CDC for DB2 UDB—support for this journal control field is available only when InfoSphere CDC mirrors data. Data Type—Character InfoSphere CDC Support—depending on the InfoSphere CDC product that you install. and is not available when refreshing data. update.3)—support for this journal control field is only available when InfoSphere CDC mirrors data.this journal control field contains the date and time of when InfoSphere CDC applied the row-level operation (insert. If you decide to use this journal control field when refreshing data. v InfoSphere CDC for Microsoft SQL Server (V5. this journal control field contains the date and time of when InfoSphere CDC refreshed the first row. and is not available when refreshing data. and is not available when refreshing data. update. v InfoSphere CDC for Microsoft SQL Server (V6. and is not available when refreshing data. v InfoSphere CDC for z/OS—support for this journal control field is available when InfoSphere CDC mirrors or refreshes data. When mirroring data. InfoSphere CDC sets this journal control field to NOT SET. or delete) to the source table. it contains the name of the dbo. or delete) to the source table. When mirroring data. When refreshing data. If you decide to use this journal control field when refreshing data. this journal control field contains the time when InfoSphere CDC applied the row-level operation (insert. this journal control field contains the current date and time. v InfoSphere CDC for z/OS—support for this journal control field is available only when InfoSphere CDC mirrors data. When refreshing data. If you decide to use this journal control field when refreshing data.0)—support for this journal control field is available only when InfoSphere CDC mirrors data. this journal control field contains the Authorization ID that the job used to connect to DB2. Record Modification User (&USER) The user ID that made the update on the source. this journal control field contains the name of the user or if the user that made the change is the system administrator. v InfoSphere CDC for Oracle and Sybase—support for this journal control field is available only when InfoSphere CDC mirrors data. When mirroring data. and is not available when refreshing data. and is not available when refreshing data. Unsupported journal control fields contain default values that vary between the InfoSphere CDC products. If you decide to use this journal control field when refreshing data. 256 InfoSphere Change Data Capture Management Console: Administration Guide . When mirroring data. This is usually the User ID of the job. this journal control field contains the name of the database user that performed the operation on the source table. InfoSphere CDC sets this journal control field to NULL. InfoSphere CDC sets this journal control field to NOT SET. journal control fields may or may not be supported when mirroring or refreshing data.

v AZ—Journal Change Apply End. table. table. In the target database. Depending on the type of Table Clear event that has taken place on the source system. InfoSphere CDC appends this entry to the audit table on the target system. InfoSphere CDC supports an iSeries journal code. v RS—indicates that prior to a refresh. RZ is a journal code generated by InfoSphere CDC. which indicates the starting point for a set of journal entries and reverses previous applies that were made to a file. v MD—indicates that a file. see “Translating journal codes into meaningful information” on page 259.About journal codes The &ENTTYP journal control field generates journal codes that provide you with the information you need to identify the exact table operations on the source system that generated the audit record in the table on the target system. v RZJjournal Change Remove End. For more information. or member on the source system. table. or member on the source system. or member has been deleted on the source system. InfoSphere CDC generates multiple journal codes. InfoSphere CDC appends this entry to the audit table on the target system. Using journal control fields for auditing replication activities 257 . a file. InfoSphere CDC appends this entry to the audit table on the target system. or member has been cleared on the source system. which indicates the ending point for a set of journal entries applied to a file. or member has been cleared on the source system. v AYJjournal Change Apply Start. the refresh is a result of an implied table restore. which indicates the starting point for a set of journal entries applied to a file. v RC—Journal Change Remove Start. This uses journal control fields for auditing replication activities. which indicates the ending point for a set of journal entries and reverses previous applies that were made to a file. table. the &ENTTYPjournal control field contains the two-character journal code that identifies the specific event that happened at the source table level and which generated the audit record on the target system. table. you can determine the events that generated each audit record. table. or member on the source system. iSeries journal codes v CR—indicates that a file. You can customize the journal codes generated by InfoSphere CDC. By mapping the &ENTTYP journal control field to the added audit column in the table on the target system. It is not an iSeries journal code. You can customize the journal codes by building an expression with the %IF column function. In this case. InfoSphere CDC appends this entry to the audit table on the target system. table. See also: “Table Clear” “Delete” on page 258 “Insert” on page 258 “Update Before” on page 258 “Update After” on page 259 Table Clear The Table Clear events clear data in a table on the source system. Journal codes represent events that take place in your source database. or member on the source system.

MZ is a journal code generated by InfoSphere CDC. v MN—Before Rename. v CH—indicates that a file on the source system has been changed. InfoSphere CDC supports an iSeries journal code. v DR—Indicates that a record from a table on the source system has been deleted because of a rollback operation of an inserted record. which indicates that a new name has been given to a file or member on the source system. which indicates when the file has been moved on the source system. v MM—Before Publication File Move. InfoSphere CDC appends this entry to the audit table on the target system. v UR—Indicates that a record in a table on the source system has been inserted through a rollback of a deleted record.v JM—indicates that journaling on the file or table has been started on the source system. 258 InfoSphere Change Data Capture Management Console: Administration Guide . or member has been reorganized on the source system. v PX—Indicates that a record in a table on the source system has been inserted by re-establishing a deleted record. iSeries journal codes v PT—Indicates that a record in a table on the source system has been inserted. Update Before The Update Before events provide you with the before image of records updated in a table on the source system. v RR—Indicates that a record in a table on the source system has been refreshed. v MZ—After Publication File Move. It is not an iSeries journal code. which indicates a new location for a file that has been moved on the source system. InfoSphere CDC supports an iSeries journal code. which indicates when the file or member has been renamed on the source system. Depending on the type of Delete event that has taken place on the source system. Depending on the type of Update Before event that has taken place on the source system. Delete The Delete events delete records in a table on the source system. iSeries journal codes v DL—Indicates that a record from a table on the source system has been deleted. When a non-schema change is applied to the audit table on the source system. v EJ—indicates that journaling on the file or table ended on the source system. InfoSphere CDC appends this entry to the audit table on the target system. Depending on the type of Insert event that has taken place on the source system. v NZ—After Rename. Insert The Insert events insert rows in a table on the source system. InfoSphere CDC appends this entry to the audit table on the target system. InfoSphere CDC appends this entry to the audit table on the target system. table. v MR—indicates that a file on the source system has been restored. v RG—indicates that a file. InfoSphere CDC generates a journal code. InfoSphere CDC appends this entry to the audit table on the target system.

see the appropriate InfoSphere CDC documentation for your platform. You can audit both images using an InfoSphere CDC system parameter. v BR—Indicates the before image of a record updated for rollback in a table on the source system. It is not an iSeries journal code. FD is a journal code generated by InfoSphere CDC. v FI—Indicates the after image of a record updated in a table on the source system that satisfies a row selection expression. It is not an iSeries journal code. InfoSphere CDC only includes a single record (FD) in the audit table. Otherwise. v v FB—Indicates the before image of a record updated in a table on the source system that does not satisfy a row selection expression. v FP—Indicates the after image of a record updated in a table on the source system that does not satisfy a row selection expression. v FD—Indicates the before image of a record updated in a table on the source system that satisfies a row selection expression. Translating journal codes into meaningful information When you map your tables using LiveAudit. InfoSphere CDC appends this entry to the audit table on the target system as a Filtered Record Insert. InfoSphere CDC appends this entry to the audit table on the target system as a Filtered Record Insert. InfoSphere CDC generates a distinct two-letter journal code on your audit table to help you identify the event that occurred on the source. This record is only placed in the audit table when the corresponding after image satisfies the row selection expression (FI) and you want to include both images in the audit table. For more information. It is not an iSeries journal code. Depending on the type of Update After event that has taken place on the source system. v UR—Indicates the after image of a record updated for rollback in a table on the source system. if you map a journal control field to a target column. Otherwise. You can audit both images using a InfoSphere CDC system parameter. FD is a journal code generated by InfoSphere CDC. For example. FP is a journal code generated by InfoSphere CDC. you can map your audit columns to the &ENTTYP journal control field to let you know what kind of change has been made on your source table. InfoSphere CDC generates a journal code. see the appropriate InfoSphere CDC User Manual for your platform. iSeries journal codes v UP—Indicates the after image of a record updated in a table on the source system. Because there are many changes that can take place. This record is only placed in the audit table when the corresponding before image satisfies the row selection expression (FD) and you want to include both images in the audit table. For more information. InfoSphere CDC appends this entry to the audit table on the target system as a Filtered Record Delete. Update After The Update After events provide you with the after image of records updated in a table on the source system. if there has been a row inserted in your Using journal control fields for auditing replication activities 259 . InfoSphere CDC only includes a single record (FI) in the audit table. InfoSphere CDC appends this entry to the audit table on the target system as a Filtered Record Delete. It is not an iSeries journal code.iSeries journal codes v UB—Indicates the before image of a record updated in a table on the source system. FB is a journal code generated by InfoSphere CDC.

instead of having the journal code ″PT″ to indicate that there has been a new row inserted in your source table. v If the before image on the source table has been updated. %IF(&ENTTYP= "UB". 260 InfoSphere Change Data Capture Management Console: Administration Guide . For example. v If a row on the source table has been deleted. InfoSphere CDC inserts a row into the target table with the journal code ’PT’. The example below illustrates how you can use the %IF column function to convert journal codes into custom letters %IF(&ENTTYP=“PT” OR &ENTTYP="RR". You may want to customize journal codes so that they are more meaningful in your organization. "A". otherwise it generates ″R″ on the audit table. then InfoSphere CDC generates ″D″ on the audit table. "B". %IF(&ENTTYP= "UP". then in response to this update. The %IF column function evaluates conditional expressions and returns different values if the expression is true or false. then InfoSphere CDC generates ″I″ on the audit table. %IF(&ENTTYP="DL"."I". then InfoSphere CDC generates ″B″ on the audit table.source table. you may want to use a one-letter code such as ″I″ to identify the insert. The journal codes your system generates depend on the database platform that you are using."R")))) This expression does the following: v If a row has been inserted or refreshed on the source table. v If the after image has been updated on the source table then InfoSphere CDC generates ″A″ in the audit table."D".

v Names of column functions are case sensitive. you cannot specify a Large OBject (LOB) column as a function parameter. v Specifying character values as decimal integers: – The values you specify within brackets are decimal integers that represent either American Standard Code for Information Interchange (ASCII) or Extended Binary Coded Decimal Interchange Code (EBCDIC) characters. For all other InfoSphere CDC products installed on the target system. v You can specify character literals in their internal numeric representation. In this section. you will learn: “Conventions in using column functions” “String functions” on page 262 “Date and time functions” on page 269 “Conversion functions” on page 274 “Conditional and variable functions” on page 282 “Data functions” on page 284 “User exit functions” on page 297 “%GETCOL column function scenarios (DB2 UDB for iSeries)” on page 305 “%GETCOL column function scenarios (Dynamic SQL)” on page 307 “Publishing multiple derived columns using the %GETCOL function (Dynamic SQL)” on page 309 Conventions in using column functions Before using column functions in expressions. This topic describes each of the column functions. v For some column functions. 2008 261 . To do this. InfoSphere CDC only supports uppercase characters. you can specify integers in ASCII format. For more information about LOB data type support. <<32>> represents a blank character in ASCII. v InfoSphere CDC for z/OS does not support the double-angled bracket notation. and also provides examples that illustrate how to use them. – If you have installed InfoSphere CDC for z/OS or InfoSphere CDC for AS/400 as a target system. © Copyright IBM Corp. as parameters for column functions. For ASCII characters. For EBCDIC. For example. some column functions may not be supported. these values must be in the range of 0 to 255. their syntax and parameters. see the appropriateInfoSphere CDC documentation. use the double-angled bracket notation (<< >>).Column functions InfoSphere CDC provides a number of column functions that you can use in expressions when mapping target columns. and the column function manipulates a value from a target column. then specify integers in EBCDIC format. This notation lets you work with character literals that contain both printable and non-printable characters. Do not prefix these values with zeroes. you should consider the following: v Depending on the InfoSphere CDC you have installed. these values must be in the range of 0 to 127.

" ". Examples %CONCAT(FNAME. and returns the result based on this sequence.v You can specify multiple characters in the same character literal. LNAME) 262 InfoSphere Change Data Capture Management Console: Administration Guide . Instead. Under a different character set. change the case of the characters in a string. You can concatenate up to 20 character fields and literals up to a total length of 2. or column functions that return character strings. See also: “Concatenation—%CONCAT” “Lowercase—%LOWER” on page 263 “Left trim—%LTRIM” on page 263 “Capitalization—%PROPER” on page 264 “Character substitution—%REPLACE” on page 265 “Right trim—%RTRIM” on page 266 “Substring—%SUBSTRING” on page 267 “Uppercase—%UPPER” on page 268 Concatenation—%CONCAT Use this function when you want InfoSphere CDC to concatenate multiple character fields and literals to form a single string. if you are using the ASCII character set.048 characters. remove blank characters from a string. these examples do not produce the same results as described. <parm2>. . replace characters of a string with other characters. Result data type Character-based. Note: Some examples in this section use the double-angled bracket notation (<< >>) and are based on the American Standard Code for Information Interchange (ASCII) character set. the notation <<65>><<78>><<78>><<65>> and <<65>>NN<<65>> represent the string ″ANNA″. v To specify NULL as a parameter in a column function. and >). literals. String functions Use these functions when you want InfoSphere CDC to manipulate strings. enter NULL without any delimiter.<parm20>) Parameters parm1 to parm20—Specify character columns. such as <45>>. v If you do not follow the double-angled bracket notation. >. During replication. Syntax %CONCAT(<parm1>. you can have InfoSphere CDC concatenate multiple strings... For example. InfoSphere CDC treats it as a sequence of characters (<. 5. or extract a substring from a string. then InfoSphere CDC does not generate an error. 4.

%LOWER("BrUcE JoNeS") Returns the string ″bruce jones″. Lowercase—%LOWER Use this function when you want InfoSphere CDC to trim all leading blank characters from a character string during replication. see “String functions” on page 262. if FNAME = ″Ray″ and LNAME = ″Kennedy″. For example. "CDC". Examples %LOWER(DEPARTMENT) Returns the strings in the DEPARTMENT column in lowercase. Related concepts “String functions” on page 262 Related reference “Substring—%SUBSTRING” on page 267 Left trim—%LTRIM Use this function when you want InfoSphere CDC to convert all uppercase characters in a string to lowercase during replication.Concatenates the values from the FNAME and LNAME columns with a blank character inserted between them. %CONCAT("Anna". or column function that returns a character string. "Management". this function returns ″Ray Kennedy″. ″marketing″.2)) Returns the string ″uc″. and so on. "Console") Returns the string ″InfoSphere CDC Management Console″. Syntax %LOWER(<parm>) Parameters parm—Specifies a character column. ″accounting″. For example. "Kim<<0>>") Returns the NUL-terminated ASCII string ″Anna Kim″.3. %LOWER(%SUBSTRING("BrUcE JoNeS". WITH P %CONCAT("InfoSphere". For information about the double-angled bracket notation. %LOWER("<<65>><<78>><<78>><<65>><<32>><<75>><<73>><<77>>") Returns the ASCII string ″anna kim″. Column functions 263 . "<<32>>". Returns NULL if parm is NULL. " ". Result data type Character-based. literal.

with no leading blank characters.3. Result data type Character-based. or column manipulation function that returns a character string. Returns NULL if parm is NULL. and the remaining letters to lowercase during replication. Related concepts “String functions” on page 262 Capitalization—%PROPER Use this function when you want InfoSphere CDC to convert the first letter of each word to uppercase. For example. %PROPER("TiNa MaNcInI") Returns the string ″Tina Mancini″. Returns NULL if parm is NULL. A word is a consecutive sequence of non-blank characters encapsulated by blank characters and string boundaries.Syntax %LTRIM(<parm>) Parameters parm—Specifies a character column. Result data type Character-based. with no leading blank characters. literal.6)) 264 InfoSphere Change Data Capture Management Console: Administration Guide . %LTRIM("Andrea Moss ") Returns the string ″Andrea Moss ″. Syntax %PROPER(<parm>) Parameters parm—Specifies a character column. The %LTRIM function does not trim trailing and embedded blank characters. Examples %PROPER(NAME) Returns the value in the NAME column with the first letter of each word capitalized. Examples %LTRIM(" George Smith") Returns the string ″George Smith″. %PROPER(%SUBSTRING("tInA mAnCiNi". ″Steve Malone″. %LTRIM("<<32>><<32>><<32>>Anna Kim") Returns the ASCII string ″Anna Kim″. literal. or column function that returns a character string.

literal. v str1—Specifies the set of characters to be replaced. It provides a character-by-character replacement. v type—Specifies the substitution type. "<type>". "0") Replaces all leading blank characters in the CUSTNO column with zeros. the extraneous characters in str1 are deleted in the result. If the number of characters in str1 is less than that in strthe extraneous characters in str2 are ignored. you can remove instances of a character from str1. %PROPER("mary-lou fernandez") Returns the string ″Mary-lou Fernandez″. "ABC". Note that ″lou″ is not converted to ″Lou″. If you specify str2 as two consecutive double quotes (″″) . – *LEAD—Replaces all leading occurrences of the specified character. Syntax %REPLACE(<parm>. Examples %REPLACE(CUSTNO. Evaluation begins with the first character and continues until a character other than ″A″. If the number of characters in str1 is greater than that in str2 . You can use this function to replace leading blank characters with zeros. Related concepts “String functions” on page 262 Related reference “Substring—%SUBSTRING” on page 267 Character substitution—%REPLACE Use this function when you want InfoSphere CDC to replace leading. – *TRAIL—Replaces all trailing occurrences of the specified character. "*LEAD". %PROPER("<<97><<110>><<110>><<97>><<32>><<107>><<105>><<109>>") Returns the ASCII string ″Anna Kim″. – *ALL—Replaces all occurrences of the specified character. "<str2>") Parameters v parm—Specifies a character column. "*LEAD".Returns the string ″Na Man″. %REPLACE(CUSTNO. "<str1>". or column function that returns a character string. or all occurrences of a specified character with another character during replication. "123") Replaces all leading occurrences of ″A″ with ″1″. Result data type Character. You must enclose values of this parameter in double quotes. v str2—Specifies the set of characters to replace those specified in str1 . ″B″ or ″C″ Column functions 265 . trailing. " ". and ″C″ with ″3″ in the CUSTNO column. ″B″ with ″2″.

For example. Replaces all occurrences of ″2″ with ″4″. %REPLACE(PRODDESC. ″C″ or ″Y″ is found. "ACY". This example illustrates how the %REPLACE function can be used to remove a character from a string instead of replacing it with another character. Related concepts “String functions” on page 262 Related reference “Left trim—%LTRIM” on page 263 “Right trim—%RTRIM” Right trim—%RTRIM Use this function when you want InfoSphere CDC to trim all trailing blank characters from a character string during replication. "45") Returns ″459899″. " ".is found. For example. "") Removes all leading blank characters in the PHONENO column. "*LEAD". To remove leading blank characters. "*ALL". this example returns ″2361acy″. and removes all occurrences of ″9″. %REPLACE("259899". If a column value is ″2361ADY″. "2". "acy") Replaces all trailing occurrences of ″A″ with ″a″. "") Removes all blank characters in the PHONENO column. This value must be greater than or equal to 1. "29". %REPLACE(PHONENO. %REPLACE(PHONENO. you can also use the %LTRIM function. Evaluation begins with the last character and continues until a character other than ″A″. this example returns ″1DC7777″. If a column value is ″ADC7777″. "4") Returns ″458″. and ″Y″ with ″y″ in the PARTNO column. literal. this example returns ″137777″. Syntax %RTRIM(<parm>) Parameters v parm—Specifies a character column. 266 InfoSphere Change Data Capture Management Console: Administration Guide . "*ALL". this example returns ″2361ADy″. "*ALL". Replaces all occurrences of ″2″ with ″4″. %REPLACE(PARTNO. if a column value is ″AC7777″. or column function that returns a character string. if a column value is ″2361ACY″. To remove trailing blank characters. This example is similar to the previous example. " ". this functions replaces all occurrences of NUL and carriage return in the PRODDESC column with blank characters. "*TRAIL". v pos—Specifies the starting position. use the %RTRIM function. "<<32>><<32>>") On platform that use the ASCII character set. "*ALL". "<<0>><<13>>". Does not remove occurrences of ″5″. ″C″ with ″c″. except that only leading blank characters are removed. %REPLACE("259899".

Syntax %SUBSTRING(<parm>. All years including and following the century line year will be designated as being in the 20th century. Returns NULL if parm is NULL. For jjj values less than 100. For example. literal or column function that returns a date value accepted by the function. InfoSphere CDC assumes a default value of 40. Result data type Character-based. – *MY—The input format is mmyy. If centuryline is set to 20 and the two-digit year specified by parm is 33. If centuryline is greater than 99. Returns NULL if parm is NULL. this function returns 2019. Examples Related concepts “String functions” on page 262 Substring—%SUBSTRING Use this function when you want InfoSphere CDC to create a character string that is a subset of an existing string that begins at a specified starting position and continues for a specified length. All years that precede the century line year will be designated as being in the 21st century. <pos>. – *MDY—The input format is mmddyy. – *DMY—The input format is ddmmyy. – *YMD—The input format is yymmdd. For example. then the function returns a string of blank characters. the Julian date for February 4th is 035. and 366. all years are designated as being in the 21st century. If you omit this parameter. which represents the 35th day of the year. this function retrrns 1933. v type—Specifies the format of the input date. This value must be greater than or equal to 1. Result data type Character-based. you must specify the leading zero or zeros. if centuryline is set to 30 and the two-digit year specified by parm is 19. with a length of len. v centuryline—Specifies the year in the century used to determine which century is added to the date. which represents December 31st in a leap year. If pos is less than the length of parm. If pos is greater than the length of parm . <len>) Parameters v parm—Specifies a character column. – *JUL—The input format is yyjjj. which represents January 1st. but pos + len Column functions 267 . – *YM—The input format is yymm. This parameter is optional. where jjj represent the sequence number of a day in the calendar year.v len—Specifies the length of the substring. You must enclose values of this parameter in double quotes. jjj must be between 1.

″MARKETING″. %UPPER("AnDrEa MoSs") Returns the string ″ANDREA MOSS″.3. 1. or column function that returns a character string.0.3. %UPPER("<<97>><<110>><<110>><<97>><<32>><<75>><<73>><<77>>") Returns the ASCII string ″ANNA KIM″. %SUBSTRING("Anna<<32>>Kim<<0>>". For information about the %SUBSTRING function. Examples %UPPER(DEPARTMENT) Returns the strings in the DEPARTMENT column in uppercase. Syntax %UPPER(<parm>) Parameters parm—specifies a character column. Examples %SUBSTRING(DIVISION. Related concepts “String functions” on page 262 Uppercase—%UPPER Use this function when you want InfoSphere CDC to convert all lowercase characters in a string to uppercase during replication. %UPPER(%SUBSTRING("AnDrEa MoSs". Result data type Character-based. For example. see . 8) Returns the ASCII string ″Anna Kim″ with no NUL-termination.2) Generates a runtime error because the starting position cannot be less than 1.2)) Returns the string ″DR″. ″ACCOUNTING″.2) Returns two characters from the DIVISION column beginning from the third position. Returns NULL if parm is NULL. and so on. %SUBSTRING("Tony Jackson". right-padded with blank characters.is greater then the length of parm . literal. then the function returns a string of length len that has the portion of parm that starts at pos and ends at the end of parm. Related concepts 268 InfoSphere Change Data Capture Management Console: Administration Guide . %UPPER("[emp ny]") Returns the string ″[EMP NY]″.

Column functions 269 . v centuryline—Specifies the year in the century used to determine which century is added to the date. This function accepts a character date value specified in one of six different formats. – *YM—The input format is yymm. – *DMY—The input format is ddmmyy. For example. if centuryline is set to 30 and the two-digit year specified by parm is 19. literal or column function that returns a date value accepted by the function. you must specify the leading zero or zeros. and 366. – *YMD—The input format is yymmdd. – *MY—The input format is mmyy. All years including and following the century line year will be designated as being in the 20th century. or retrieve the current date and time. [centuryline]) Parameters v parm—Specifies a character column.“String functions” on page 262 Related reference “Substring—%SUBSTRING” on page 267 “Uppercase—%UPPER” on page 268 Date and time functions Use these functions when you want InfoSphere CDC to manipulate date and time values during replication. – *JUL—The input format is yyjjj. – *MDY—The input format is mmddyy. If centuryline is set to 20 and the two-digit year specified by parm is 33. You must enclose values of this parameter in double quotes. where jjj represent the sequence number of a day in the calendar year. this function returns 1933. which represents January 1st. For example. jjj must be between 1. You can add a two-digit century specification to a date. all years are designated as being in the 21st century. v type—Specifies the format of the input date. All years that precede the century line year will be designated as being in the 21st century. this function returns 2019. Syntax %CENTURY(<parm>. For jjj values less than 100. "<type>". See also: “Century—%CENTURY” “Current date—%CURDATE” on page 270 “Current time—%CURTIME” on page 271 “Current timestamp—%CURTMSTP” on page 273 Century—%CENTURY Use this function when you want InfoSphere CDC to add a two-digit century specification to a date that identifies the year without the century during replication. which represents December 31st in a leap year. the Julian date for February 4th is 035. If centuryline is greater than 99. which represents the 35th day of the year.

However. Otherwise. 1999) Mapping a target column to an expression that uses the %CURDATE function is not the same as defining the current date as the initial value for the target column. InfoSphere CDC assumes a default value of 40. you may want to track when InfoSphere CDC inserts a record or when it performs updates on source and target columns.This parameter is optional. 1997) 03201980 (March 20. when you define the initial value as the current date. If you omit this parameter. Result data type Character if parm is character. Table 1 Input Date (parm) Input Format (type) Input century line Result 101001 ″*YMD″ 20101001 (October 1. For example. 1980) 041993 (April 1993) 202001 (January 2002) 1999365 (December 31. Examples Input Date (parm) 101001 211197 032080 0493 2001 99365 Input Format (type) ″*YMD″ ″*DMY″ ″*MDY″ ″*MY″ ″*YM″ ″*JUL″ 92 0 60 80 Input century line (centuryline) Result 20101001 (October 1. 1999) Related concepts “Date and time functions” on page 269 Current date—%CURDATE Use this function when you want InfoSphere CDC to return the current date during data replication (refresh or mirroring) activities on the source or target. 2010) 21111997 (November 21. InfoSphere CDC populates the target column with the current date when a record is inserted or updated in the target table. Note: InfoSphere CDC for AS/400 and InfoSphere CDC for Microsoft SQL Server do not support this function. This function uses the system clock you have set on the source or target. 1980) 0493 ″*MY″ 80 041993 (April 1993) 2001 ″*YM″ 202001 (January 2020) 99365 ″*JUL″ 92 1999365 (December 31. 1997) 032080 ″*MDY″ 60 03201980 (March 20. When you map a target column to an expression. Syntax %CURDATE("<timezone>") 270 InfoSphere Change Data Capture Management Console: Administration Guide . 2010) 211197 ″*DMY″ 0 21111997 (November 21. InfoSphere CDC populates the target column with the current date only when it inserts a record into the target table. it returns a numeric value.

10). this function returns 2004-03-11. at 1:21 AM. or column function that returns a character string. This is the same as *UTC. at 1:21 AM. v *GMT—Returns the date in Greenwich Mean Time (GMT). if the local date is January 29. literal.parm—Specifies a character column. For example. You must enclose values of this parameter in double or single quotes. this function returns 2007. v *LOC—Returns the date local to the source or target. 2004. This function uses the system clock on the source or target. 2007.Parameters timezone—Specifies the time zone of the result. Examples %CURDATE("*LOC") If the local time is March 11. Result data type Character. The %TOCHAR function extracts the month. %SUBSTRING(%TOCHAR(%CURDATE("*LOC").08-27. %CURDATE("*UTC") For a server located in the Japan Standard Time (JST) zone. and day. Related concepts “Date and time functions” on page 269 “Mapping initial values to target columns” on page 161 Related reference “Character conversion—%TOCHAR” on page 274 “Substring—%SUBSTRING” on page 267 Current time—%CURTIME Use this function when you want InfoSphere CDC to return the time when it inserts or updates a row on source and target columns. separator character. the expression returns ″01-29″. on August 28. in the format CCYY-MM-DD. 2007. v *UTC—Returns the date in Coordinated Universal Time (UTC). Syntax %CURTIME("<timezone>") Column functions 271 . %CURDATE("*GMT") For a server located in the Japan Standard Time (JST) zone. JST is 9 hours ahead of UTC (UTC+9). This example is equivalent to %CURDATE (″*UTC″). 2007. Note: InfoSphere CDC for AS/400 and InfoSphere CDC for Microsoft SQL Server do not support this function. on August 28. You can use this example if you require the month and day only.08-27. 6. JST is 9 hours ahead of UTC (UTC+9). this function returns 2007. 5) Returns the month and day of the %CURDATE function invocation local to the source or target.

MM. It returns a character result after performing time calculations.14. v *LOC—Returns the time local to the source or target.33. 2)) – %TONUMBER(%TOCHAR(%CURTIME("*UTC"). %VAR(DIFF) – 24.22.SS. v *GMT—Returns the time in Greenwich Mean Time (GMT). To modify the above expression to select a different time zone ahead or behind the local time zone. %TOCHAR(%IF(%VAR(EST. The result represents the same time in the Eastern Standard Time (EST) zone. which is 3 hours ahead of PST (PST+3). v *UTC—Returns the time in Coordinated Universal Time (UTC). In the event that the returned Pacific time is in the interval from 9:00:00 PM to 12:00:00 AM. This example is equivalent to %CURTIME (″*UTC″). %VAR(EST) – 240000). change + 30000 to a different sign and value. changing +30000 to +20000 returns the equivalent time in the Central Standard Time (CST) zone. in the format HH. "")) + 30000) < 240000. 272 InfoSphere Change Data Capture Management Console: Administration Guide . %CURTIME("*UTC") For a server located in the Hawaiian Standard Time (HST) zone. if this expression is evaluated on a server located in the Pacific Standard Time (PST) zone at 3:22:48 PM. This example illustrates that an expression can be defined to convert local time to the equivalent time in any other time zone (not necessarily UTC). %VAR(EST). Examples %CURTIME("*LOC") If the local time is 11:25:22 PM (local). &VAR(DIFF))) Returns the time difference between UTC and the time zone of the source or target where the %CURTIME functions are invoked.14. 2))) > 12. For example. This is the same as *UTC. %IF(%VAR(DIFF.25. %VAR(DIFF) + 24. ". %TONUMBER(%TOCHAR(%CURTIME("*LOC"). "*ALL". the expression returns ″182248″. %CURTIME(″*GMT″) For a server located in the Hawaiian Standard Time (HST) zone. For example.33. %TONUMBER(%REPLACE(%TOCHAR(%CURTIME("*LOC"). 6) Returns the time of the %CURTIME function invocation three time zones ahead relative to the local time zone on the source or target. HST is 10 hours behind UTC (UTC-10).". this function returns 07.Parameters timezone—Specifies the time zone of the result. HST is 10 hours behind UTC (UTC-10). You must enclose values of this parameter in double or single quotes. at 9:14:33 PM. %IF(%VAR(DIFF) < – 12. the %IF function ensures that the expression returns the equivalent Eastern time on the following day. at 9:14:33 PM. Result data type Character. this function returns 07. this function returns 23. 8).

zeroes will be used to right-pad the result to a six-digit length. the results do not show microseconds. v *LOC—Returns the time local to the source or target. For example. local time. If the server is located in the Mountain Standard Time (MST) zone and the functions are invoked at 1:22:13 AM. Note: This example compares equivalent times after obtaining two separate time samples.11.For example. In the examples for this function. v *GMT—Returns the time in Greenwich Mean Time (GMT). This example is equivalent to %CURTMSTP(″*UTC″). where UUUUUU represents the number of microseconds. this function returns 2011-09-21-19. Note: InfoSphere CDC for AS/400 and InfoSphere CDC for Microsoft SQL Server do not support this function.849217. which may not always produce the correct results.01. if this expression is evaluated on a server located in the Central Europe Time (CET) zone at 6:43:07 PM. at 4:31:01 AM on September 22. 2008-12-09-03. Column functions 273 . v *UTC—Returns the time in Coordinated Universal Time (UTC). this function returns 2011-09-21-19.31. JST is 9 hours ahead of UTC (UTC+9). 2011. the expression returns -7.34. You must enclose values of this parameter in double or single quotes. 2005. in the format CCYY-MM-DD-HH. %CURTMSTP("*UTC") For a server located in the Japan Standard Time (JST) zone. local time. %CURTMSTP("*GMT") For a server located in the Japan Standard Time (JST) zone. Current timestamp—%CURTMSTP Use this function to when you want InfoSphere CDC to track the date and time when it inserts or updates a row in source and target columns.SS. 2011. This function uses the system clock on the source or target. Syntax %CURTMSTP("<timezone>") Parameters timezone—Specifies the time zone of the result.31. Examples %CURTMSTP("*LOC") If the local time is 2:05:54 AM on June 18.54.UUUUUU. and %CURTIME ("*UTC") is invoked one second later at 8:00:00 AM. This is the same as *UTC. JST is 9 hours ahead of UTC (UTC+9).05. this function returns 2005-06-18-02. the expression returns 1. Result data type Character. at 4:31:01 AM on September 22.01.MM. For environments that do not support microsecond precision. The expression will not produce the correct result if %CURTIME ("*LOC") is invoked at 7:59:59 AM.

WST is 8 hours ahead of UTC (UTC+8). Syntax %TOCHAR(<parm>. or from a numeric or character value to a datetime-type value. 2013 at 4:05:22 AM.” Conversion functions Use these functions when you want InfoSphere CDC to convert values from one data type to another during replication.23 1234. The following table provides several examples with integers that have a defined number of decimal places and an example of how InfoSphere CDC for z/OS converts real floating decimals. This parameter is optional and is only available with InfoSphere CDC for z/OS. v len—Specifies the number of characters to be returned. You can use this example if you do not require the number of seconds and microseconds. 16) Returns the date and time (hours and minutes only) of the %CURTMSTP function invocation in UTC. For information about the %TOCHAR function. “Character conversion—%TOCHAR.5 Length 6 7 Decimal 2 2 Result 001. The %TOCHAR function converts the date to character data and returns the first 16 characters of the timestamp returned by the %CURTMSTP function.05″. if the %CURTMSTP function is invoked on a server located in the Western Standard Time (WST) zone on April 24.50 274 InfoSphere Change Data Capture Management Console: Administration Guide . For example. Input value 1. This feature is only available with InfoSphere CDC for z/OS. <length>.2345 1234. the expression returns ″2013-04-23-20.%TOCHAR(%CURTMSTP("*UTC"). A decimal place counts as a returned value. if you specify that you want to return three characters. v decimal—An integer value that specifies the number of decimal places in the returned value. See also: “Character conversion—%TOCHAR” “Date conversion—%TODATE” on page 275 “Date and time conversion—%TODATETIME” on page 277 “Number conversion—%TONUMBER” on page 279 “Time conversion—%TOTIME” on page 280 Character conversion—%TOCHAR Use this function to convert any value to a character string. For example. [decimal]) Parameters v parm—Specifies a column name or literal. You can convert from any value to a character string or a numeric value. Note: Specify a negative value for this parameter if you would like %TOCHAR to treat the incoming value as unsigned. this function returns the three leftmost or high order digits of parm.

″13878964169332555778″.020000″ The decimal part is right-padded with zeros to return a string of seven characters.1″ ″001234″ The integer value is left-padded with zeros to return a string of six characters. to datetime or character-type values with century. 45699 9 2 ″000456. Note: The ability to specify negative lengths is only supported by InfoSphere CDC for z/OS. Column functions 275 .Input value 1. or from character formats without century. By specifying a negative length. $SEQNO -20 Not specified.123 1234 Input length (len) 3 5 3 6 Decimal places (decimal) Not specified. Not specified.02 7 Not specified.4″ ″0.02000 Result data type If len specifies a value greater than the length of parm.45 0.99″ The integer value is left-padded with zeros and two decimal places to return a string of nine characters. You can convert dates from packed-numeric. the result is left-padded or right-padded with blank characters. Note: The decimal parameter is only supported by InfoSphere CDC for z/OS. Result ″123″ ″123. 1. Not specified. Not specified.02 1. ″1. %TOCHAR treats the &SEQNO journal control field as unsigned. Examples Input value (parm) 12345 123.02 1.02 (Real floating decimal) Length 7 7 Decimal 2 2 Result 0001. zoned-numeric. Date conversion—%TODATE Use this function when you want InfoSphere CDC to convert a numeric or character data type value to a datetime-data type during replication.

which represents January 1st. For example. – *YMD—the input format is yymmdd. Any other value represents the 21st century. and 366. 2039. the %TODATE function returns the corresponding year in the 20th century. Result data type Character. type value *YMD (yymmdd) *MDY (mmddyy) *DMY (ddmmyy) *YYMD (ccyymmdd) *CYMD (cyymmdd) *JUL (yyjjj) *CJUL (cyyjjj) *YJUL (ccyyjjj) Length of date 6 digits 6 digits 6 digits 8 digits 7 digits 6 digits 6 digits 7 digits v type—specifies the format of the input date. If you specify a value for yy between 0 and 39. if you specify a value for yy between 40 and 99. or day. – *DMY—the input format is ddmmyy. A value of 0 for c represents the 20th century. the %TODATE function returns the default value 1901-01-01. When you set type to *JUL. 1940. 276 InfoSphere Change Data Capture Management Console: Administration Guide . "<type>") Parameters v date—specifies the input date. For example. – *JUL—the input format is yyjjj. where cc represents the century. the length of that string must match the length for the format specified by type. where c represents the century. the Julian date for February 4th is 035. where jjj represent the sequence number of a day in the calendar year. – *YJUL—the input format is ccyyjjj. where c represents the century. If date is the name of a column containing a character string. – *YYMD—the input format is ccyymmdd. You must enclose values of this parameter in double quotes. in standard ISO (International Organization for Standardization) format. which represents December 31st in a leap year. jjj must be between 1. – *CYMD—the input format is cyymmdd. which represents the 35th day of the year. InfoSphere CDC generates an error if the length is any other value. you must specify the leading zero or zeros.Syntax %TODATE(<date>. that is CCYY-MM-DD. the %TODATE function returns the corresponding year in the 21st century. where cc represents the century. For example. as indicated below. month. If the input date contains an invalid value for the year. – *CJUL—the input format is cyyjjj. For jjj values less than 100. A value of 0 for c represents the 20th century. – MDY—the input format is mmddyy. Any other value represents the 21st century.

<time>) Parameters v date—specifies the input date. 1901) 1968-07-01 (July 1. You can convert dates from packed-numeric. 1991) Date and time conversion—%TODATETIME Use this function when you want InfoSphere CDC to convert a numeric or character data type to a datetime data type during replication. If date is the name of a column containing a character string. You can also convert time data types from packed-numeric. Note: InfoSphere CDC for AS/400 does not support this function. type value *YMD (yymmdd) *MDY (mmddyy) *DMY (ddmmyy) *YYMD (ccyymmdd) *CYMD (cyymmdd) *JUL (yyjjj) *CJUL (cyyjjj) *YJUL (ccyyjjj) Length of date 6 digits 6 digits 6 digits 8 digits 7 digits 6 digits 6 digits 7 digits Column functions 277 . "<type>".Examples These examples show the hyphen (-) as the separator character in the returned ISO dates. 1976) 1995-10-01 (October 10. to datetime or character-type values with century. InfoSphere CDC generates an error if the length is any other value. the month. zoned-numeric. Depending on your environment. 2010) 1995-01-04 (January 4. 1995) 1901-01-01 (January 1. zoned-numeric. 1968) 1956-02-05 (February 5. a different character may separate the year. 1956) 2010-02-16 (February 16. or from character formats without century. 1995) 2002-02-01 (February 2. and the day in the output date. Syntax %TODATE(<date>. as indicated below. Input date (date) 760704 100195 000000 010768 19560205 1100216 95004 102032 1991359 Input format (type) *YMD *MDY *MDY *DMY *YYMD *CYMD *JUL *CJUL *YJUL Result 1976-07-04 (July 4. the length of that string must match the length for the format specified by type. 2002) 1991-12-25 (December 25. or character formats into datetime or character-type values with century.

v type—specifies the format of the input date. 278 InfoSphere Change Data Capture Management Console: Administration Guide . – *YJUL—the input format is ccyyjjj. For example. if you specify a value for yy between 40 and 99. The table below indicates the length and format for this parameter. HHMMSS. For jjj values less than 100. Depending on your environment. depending on the data type of the input time. – *CYMD—the input format is cyymmdd. 2039. where c represents the century. and the day in the output date. the minutes. you must specify the leading zero or zeros. – *YYMD—the input format is ccyymmdd. a different character may separate the year. For example. “HH:MM:SS”. the %TODATE function returns the corresponding year in the 21st century. the month. and 366. where cc represents the century. – MDY—the input format is mmddyy. For example. the Julian date for February 4th is 035. and the seconds in the output time. – *CJUL—the input format is cyyjjj. – *YMD—the input format is yymmdd. When you set type to *JUL. Examples The table below provides examples for this function. in standard ISO (International Organization for Standardization) format. You must enclose values of this parameter in double quotes. month. 223000 represents 10:30 PM. a different character may separate the hours. where cc represents the century. and the colon (:) as the separator in the returned ISO time values. 71500 represents 7:15 AM. Result data type Character. jjj must be between 1. A value of 0 for c represents the 20th century. – *DMY—the input format is ddmmyy. v time—Specifies the input time. For example. For example. These examples show the hyphen (-) as the separator character in the returned ISO dates. Any other value represents the 21st century. If you specify a value for yy between 0 and 39. Also. where c represents the century. – *JUL—the input format is yyjjj. the %TODATETIME function returns the default value 1901-01-01 for the date. where jjj represent the sequence number of a day in the calendar year. which represents January 1st. 1940. For example. If the input date contains an invalid value for the year. A value of 0 for c represents the 20th century. Any other value represents the 21st century. the %TODATE function returns the corresponding year in the 20th century. which represents the 35th day of the year. ″10:30:00″ represents 10:30 AM. Data type Numeric Length 5 digits 6 digits Character 8 digits Format HMMSS. or day. You must enclose values of this parameter in double quotes. which represents December 31st in a leap year.

literal or column function that returns a character string. Syntax %TONUMBER(<parm>) Parameters v parm—Specifies a character column.<digits>] [{e | E} [<sign>] <digits>] In the specification above. the %TONUMBER function returns a floating point number. Column functions 279 .Input date (date) 891102 Input format (type) *YMD Input time (time) 112500 Result 1989-11-02 11:25:00 (November 2. 2002 at 5:15 PM) 030496 *MDY ″13:42:00″ 000000 *MDY ″10:55:00″ 210570 *DMY ″09:05:00″ 20100902 *YYMD 023000 1060723 *CYMD 193300 91060 *JUL 220100 097106 *CJUL 043500 2002092 *YJUL ″17:15:00″ Number conversion—%TONUMBER Use this function when you want InfoSphere CDC to convert a character field or literal to a numeric value during replication. 1989 at 11:25 AM) 1996-03-04 13:42:00 (March 4. 2010 at 2:30 AM) 2006-07-23 19:33:00 (July 23. the white space can consist of one or more blank or tab characters. The decimal digits may be followed by an exponent that consists of the letter E (in upper or lower case) and an optionally signed decimal integer. 1996 at 1:42 PM) 1901-01-01 10:55:00 (January 1. the %TONUMBER function returns zero. – If you convert a correctly formed character field or literal that contains an exponent. The signs must be plus (+) or minus (-). It must be in the following format: [<whitepsace>] [<sign>] [<digits>] [. 2006 at 7:33 PM) 1991-03-01 22:01:00 (March 1. 1991 at 10:01 PM) 1997-04-16 04:35:00 (April 16. and you can specify only decimal digits. 1970 at 9:05 AM) 2010-09-02 02:30:00 (February 9. Note the following when using the %TONUMBER function: – If parm does not follow the format above. At least one digit must appear after the decimal point. 1901 at 10:55 AM) 1970-05-21 09:05:00 (May 21. 1997 at 4:35 AM) 2002-04-02 17:15:00 (April 2.

but it cannot be converted to a numeric value. Returns an integer value of 0. Returns an integer value of 3. Returns an integer value of 0. because the %TONUMBER function cannot convert character strings that do not conform to the data format described for parm. or time data type to a time data type during replication. Returns an integer value of 0. Returns an integer value of 0. Returns an integer value of 0. then it truncates the decimal part is truncated and returns 12. Returns an integer of -920824. it returns an integer value of 0. 280 InfoSphere Change Data Capture Management Console: Administration Guide .– Floating point values expressed in character form are converted to 8-byte floating-point data types.1e0″ ″44 90″ ″ 66.1. Returns a floating point value of -0. If this function is mapped to an integer column. Returns a floating point value of 66. but precision may be lost.10″ ″911HELLO″ ″+2. Returns a floating point value of 4500. this function returns NULL. InfoSphere CDC generates a message in Event Log.89″ ″. If the column from which this function is called is nullable. Returns an integer value of 0. Examples Input value (parm) ″12. – Precision may be lost when you convert numerical values expressed in character form that exceed a certain number of digits.5E3″ ″$1000″ ″-.45.67″ Time conversion—%TOTIME Use this function when you want InfoSphere CDC to convert a character. Leading zeros are removed. Returns a floating point value of 220.2e+2″ ″ 4. numeric. Returns a floating point value of -12. Result data type Numeric.4″ ″-0920824″ NULL ″ABC″ ″″ ″12345678901234567. Otherwise.45″ Result Returns a floating point value of 12.4. You can convert from different formats based on the type of the input value.67 ″3″ ″-12. – Integer values expressed in character form are converted to 4-byte integer data types. Returns a non-zero result. The input value is valid as a character string.

am. %TOTIME (12:05. Any number of blank characters can precede or follow the six digits. and seconds. For example. You cannot specify seconds in this format. Any number of blank characters can precede the first digit or follow the last digit. You can omit leading zeros in the number of hours and minutes. %TOTIME ("3 5 P") returns 15:05:00. Any number of blank characters can precede the first digit or follow the AM/PM specification. %TOTIME ( 012537 ) returns 01:25:37. You can specify AM and PM in a number of different ways. [whitespace] digit [digit] separator digit [digit] [separator digit [digit]] [whitespace] This format lets you specify a time value that contains valid separator characters (colon. 71500 represents 7:15 AM and 223000 represents 10:30 PM. in the format HMMSS or HHMMSS. For example. in one of the following formats: [whitespace] digit digit digit digit digit digit [whitespace] This format lets you specify a time value that contains six consecutive digits. This value must be positive. For example. or PM. For example. [whitespace] digit [digit] separator digit [digit] [whitespace] {A | a | P | p} [{M | m}] [whitespace] This format lets you specify a time value that indicates AM or PM. v Character.Note: InfoSphere CDC for Microsoft SQL Server does not support this function. You cannot specify more than one separator character in the time value. minutes. This function uses the system clock on the source or target. %TOTIME ("04: 20 PM") is not valid. aM. Note: InfoSphere CDC for AS/400 and InfoSphere CDC for Microsoft SQL Server do not support this function.20) is not valid. in which case the %TOTIME function assumes zero seconds. minutes. P. Result data type These examples show the colon (:) as the separator character in the returned ISO (International Organization for Standardization) time values. You can omit the number of seconds. %TOTIME ("12:05") returns 12:05:00. You cannot specify more than one separator character in the time value. period or one or more spaces) between hours. For example. For example. comma. and if it contains a fractional part. the %TOTIME function assumes zero seconds. If you do so. such as A. v Numeric. AM. For example. You can omit leading zeros in the number of hours. Syntax %TOTIME(<time>) Parameters time—Specifies a column or literal that can have one of the following types: v Time. and seconds. Am. a. the fraction must be zero. Depending on your Column functions 281 . Use this function to when you want InfoSphere CDC to track the date and time when it inserts or updates a row in source and target columns. %TOTIME ("12 5 20") returns 12:05:20.

minutes.environment. Use the %VAR function when you want InfoSphere CDC to declare a new variable. and seconds in the output time. Result data type The type of data returned by the true (expression_if_true) and false (expression_if_false) expressions. a different character may separate the hours. 282 InfoSphere Change Data Capture Management Console: Administration Guide . Examples Input value (parm) ″ 012537 ″ ″22:4:12″ ″4:05P″ ″2 5 Am″ 204521 91035. <expression_if_true>. Syntax %IF(<conditional>.0000 250521 ″10: 10:35″ Result 01:25:37 22:04:12 16:05:00 02:05:00 20:45:21 09:10:35 00:00:00 00:00:00 Conditional and variable functions Use the %IF column function when you want InfoSphere CDC to evaluate an expression and return different results. The values returned by expression_if_true and expression_if_false must both be of the same data type. v expression_if_false—specifies an expression that is evaluated if the condition is false. v expression_if_true—specifies an expression that is evaluated if the condition is true. assign a value to it. <expression_if_false>) Parameters v conditional—specifies a conditional expression that evaluates to true or false. or retrieve the value of an existing variable. The conditional expression must compare identical data types. See also: “Conditional–%IF” “Variable—%VAR” on page 283 Conditional–%IF Use this function when you want InfoSphere CDC to evaluate a conditional expression and return different results during replication.

[expression]) Parameters v variable_name—Specifies the name of the defined or retrieved variable. "*YMD"))) If a value in the DATSTR column is ″010101″. in ascending column sequence. from column to column. this example returns 71-07-23. v expression—Specifies a literal or a complex expression. If QTY is less than 100. %VAR(QTY) * PRICE. This parameter is optional. "*YYMD"). the result of the expression is QTY * PRICE * (1 . "ID is not 1") If the value in the ID column is equal to 1. PRICE*QTY) If the value in the PRICE column is 10 and the value in the QTY column is 5. Otherwise. see “Date conversion—%TODATE” on page 275. "ID is 1". %TODATE(DATSTR. for a value of ″710723″ in the DATSTR column. you cannot pass a variable between rows. NULL. If you specify it. In all other cases. then the result of the expression is QTY * PRICE. the function assigns the new value to it. provided that the variable is defined (using the %VAR function) in a preceding column or previously in the current expression. For information about the %IF Column functions 283 . You can pass a variable in the same row. the function creates a new variable. this function returns 1901-01-01. and returns the value 50. For information about the %TODATE function. Result data type The type of data assigned to the variable (variable_name).DISCOUNT)) Sets the QTY variable to QTYORD plus QTYBACKORD. %IF(DATSTR="999999". then this function assigns the value 50 to the SBTTL variable. Examples %VAR(SBTTL. If you omit this parameter. assigns the given value to it. this function returns the current value of the SBTTL variable. %IF(%VAR(QTY. %IF(DATSTR="010101". this function returns the string ″ID is 1″.Examples %IF(ID=1. If a value in DATSTR is ″999999″.DISCOUNT). Related reference “Date conversion—%TODATE” on page 275 Variable—%VAR Use this function when you want InfoSphere CDC to evaluate a conditional expression and return different results during replication. it returns equivalent dates to values in DATSTR. Syntax %VAR(<variable_name>. Otherwise. and returns the value of the variable. However. If the variable already exists. the function retrieves the value of the variable. QTYORD + QTYBACKORD) <100. For example. %TODATE(19010101. %VAR(QTY) * PRICE * (1. it returns the string ″ID is not 1″. it returns NULL. %VAR(SBTTL) If SBTTL is defined either in an expression for a preceding column or earlier in the current expression.

Current value—%CURR Use this function when you want InfoSphere CDC to retrieve the value of a target column before applying an update on a source column. before it was updated on the source by the change being replicated. Examples %VAR(CRLIMIT) Returns the previous value in the CRLIMIT column. See also: “Before value—%BEFORE” “Current value—%CURR” “Retrieve column—%GETCOL (DB2 UDB for iSeries)” on page 285 “Retrieve column—%GETCOL (Dynamic SQL)” on page 288 “Retrieve column—%SELECT” on page 293 Before value—%BEFORE Use this function when you want InfoSphere CDC to retrieve the value of a source column before applying an update. this function returns the appropriate default value for the data type of the target column. the value of a target column before applying an update. Note: InfoSphere CDC for z/OS does not support this function. see “Conditional–%IF” on page 282. Syntax %VAR(<parm>) 284 InfoSphere Change Data Capture Management Console: Administration Guide .function. Result data type The data type of the source column (parm). an expression. Syntax %VAR(<parm>) Parameters parm—Specifies the name of a source column. this function returns NULL. including all rows that are inserted during a refresh. When you use these functions. InfoSphere CDC can return the value of a source column before applying an update. and the value of a column for a specific row in a table. Otherwise. When a row is inserted into the target table. You cannot specify a journal control field. Related reference “Conditional–%IF” on page 282 Data functions Use these functions when you want InfoSphere CDC to retrieve column values during replication. or a column function as the input parameter.

The result of the expression is assigned to the derived column.%BEFORE(SRCCNT)) + %CURR(TGTTOT) You can use this example to maintain the total of two or more numeric column values that are contained in the same table on different datastores. This difference is added to the current sum stored in the derived column TGTTOL. even if the source column contains multi-byte data. an expression. When a value in a SRCCNT column is updated. Result data type The data type of the target column (parm). Examples %CURR(BALANCE) Returns the current value of the target column BALANCE. %TONUMBER) as its parameter. the SRCCNT column is mapped to the corresponding target column with the same name. The %CURR function returns the value of the target column as single-byte characters. including all rows that are inserted during a refresh. (SRCCNT . because %CURR does not accept another column function (in this example. the difference between the new value and the previous value is calculated using the %BEFORE function.%BEFORE(BALANCE) Calculates the difference between the values in the source and target columns before an update is made.Parameters parm—Specifies the name of a source column. the current balance would be placed in the derived column before the update to BALANCE is applied to the target table. Related reference “Before value—%BEFORE” on page 284 Retrieve column—%GETCOL (DB2 UDB for iSeries) Use this function when you want InfoSphere CDC to retrieve the value of a column for a specific row in a table. or a column function as the input parameter. In each source table. You can use this example only for numeric fields. this function returns the appropriate default value for the data type of the target column. so that InfoSphere CDC returns additional columns when it has previously invoked a %GETCOL function. If the result is not equal to zero. You cannot specify a journal control field. %CURR(BALANCE) . In an expression. with a subset of parameters. %CURR(%TONUMBER(EMPNO)) InfoSphere CDC generates an error when verifying the expression. The expression in this example is assigned to the derived column TGTTOL on the target. You can also use this function. the column values were not the same before the update was applied on the source and on the target. Column functions 285 . When a row is inserted into the target table.

[default_value]) %GETCOL(<column_name>. [default_value]). <table_name>) %GETCOL(<column_name>. If the read is unsuccessful. v Condition the table reads that are performed. v table_name—Specifies the name of a table. If more than one row satisfy the key requirements specified. <table_name>. The previous %GETCOL function invocation must be for the same journal entry during continuous mirroring or the same row during refresh. <key_valuen>]) This function reads a table and returns the value of the column specified. based on the key column values that are identified. then this function returns the first row only.. to allow InfoSphere CDCto perform the necessary secondary reads.[<key_count>]. then this function returns the default value specified and sends a message to the appropriate message queue. You can specify the table name using one of the following formats: 286 InfoSphere Change Data Capture Management Console: Administration Guide . v Read tables external to InfoSphere CDC to perform dynamic translations on the target. The primary table refers to the source table being replicated. <key_value1>. The secondary tables refer to tables referenced in the %GETCOL function. v Specify the order that table reads are performed. without reading the table again. v Use columns from secondary tables that were retrieved previously to populate keys for subsequent reads (the population of key column values is not restricted to primary columns only). [default_value].. [record_format]. Note: This topic contains information about the %GETCOL function supported by InfoSphere CDC for AS/400. The specified column in the table must exist when specifying the expression. The short syntax lets you retrieve more than one column from a table (that was read previously using the %GETCOL function).You can use the %GETCOL function in expressions to perform the following operations: v Obtain columns from one or more keyed secondary tables and join them with an existing primary table before sending data to the target. v Specify how keys of the secondary tables are populated. . <table_name>. This table must be keyed. <key_value2>. Parameters v column_name—Specifies the name of a column. The table_name and record_format parameters specified in the short format of the %GETCOL function invocation must match the table_name and record_format parameters specified in the long format of the %GETCOL function invocation. Long syntax format—reads from database %GETCOL(<column_name>. Short syntax format—reads from existing &GETCOL result %GETCOL(<column_name>. You cannot specify an expression for this parameter. <table_name>.. [record_format]) This function returns the value of the specified column from a row retrieved by a previous %GETCOL function invocation. You cannot specify an expression for this parameter.

You cannot specify an expression for this parameter. ″FILE″. If you omit this parameter.– The library. For example. It should be the number of key columns of the record format selected.. InfoSphere CDC assumes a default value of *LIBL for the library name. ″NO SALESREP″ or ″1995-05-10″. You cannot specify an expression for this parameter. InfoSphere CDC assumes a default value of *FIRST for the member name. time. If you omit this parameter. Specify this parameter if more than one record format exist. – The file is specified. then this function returns a default value according to the data type of the column specified. 1940-01-01 (Date Zero). Time Integer (4 bytes) Small integer (2 bytes) Timestamp 00:00:00 (Time Zero) Zero Zero 0001-01-01 00:00:00 (Timestamp Zero) v record_format—Specifies the record format for the record to read. . If you omit this parameter. For example. – The file and member names are specified. You cannot specify an expression for this parameter. ″LIBRARY/FILE″. If you omit this parameter. This value must be a literal or constant. If you omit this parameter. then InfoSphere CDC assumes a default value of 1. date. These key values must match the key columns of the table to read. This applies to the *JUL (Julian) date format. This applies to all date formats except *JUL (Julian). If you specify NULL as the default value. file. For example. depending on the data type of the specified column. For example. ″LIBRARY/FILE(MEMBER)″. then InfoSphere CDC reads the first record format.. then the column must be nullable. ″FILE(MEMBER)″. For character. InfoSphere CDC assumes a default value of *LIBL for the library name and a default value of *FIRST for the member name. For example. Field type Character Decimal (packed) Numeric (zoned) Real (4–byte floating point) Float (8–byte floating point) Date Default value Blank character Zero Zero Zero Zero 0001-01-01 (Date Zero). and member names are specified. Column functions 287 . It must be an integer greater than 0. Character data passed as key parameters is padded with blank characters. then you must enter a comma instead of the parameter value to indicate its position in the parameter list. and timestamp data types. v key_value1. or truncated if the length does not match the length of the key column.key_valuen—Specify the key values to use when performing the read. key_value2. v default_value—Specifies a default value to return if the read fails. then you must enter a comma instead of the parameter value to indicate its position in the parameter list. – The library and file are specified. v key_count—Indicates the number of key values specified as parameters. you must enclose values of this parameter in double quotes.

member *FIRST. %GETCOL (CUSTNAME. member *FIRST. "PRODLIB/CUSTMAST") Retrieves the CUSTNAME column from a previous read of the CUSTMAST table in library PRODLIB. You can also use this function when entering an expression for a target column. and record format ″FMT2″. – An expression performed on a column that was previously read using the %GETCOL function.The key value can be either a primary table column (direct column mapping) or an expression. "PRODLIB/CUSTMAST". then this function returns blank characters. not found) and assuming that the data type for the CUSTNAME column is CHARACTER. To use this function before replication. Result data type The data type of the column retrieved (column_name). Examples The following examples are of scenarios where the %GETCOL function is used: %GETCOL (CUSTNAME. You must specify these parameters if the key_count parameter is specified. then this function returns ″NO CUSTMAST″. "FMT2") Retrieves the CUSTNAME column from a previous read of the CUSTMAST table in library PRODLIB. even if the source column contains multi-byte data. The previous read must have ″FMT2″ specified for the record format. not found). . The %GETCOL function returns the value of the column as single-byte characters. If the read is unsuccessful (for example. then this function returns blanks characters. Related reference “Retrieve column—%GETCOL (Dynamic SQL)” “Retrieve column—%SELECT” on page 293 Retrieve column—%GETCOL (Dynamic SQL) Use this function to perform a secondary table column lookup based on the specified key columns in the primary and secondary tables. member *FIRST. – A column from a previous read using the %GETCOL function. you must add a derived column to the primary table and enter an expression for that column that uses the %GETCOL function. If the read is unsuccessful (for example. "NO CUSTMAST") Retrieves the CUSTNAME column from a previous read of the CUSTMAST table in library PRODLIB. Some examples include: – An expression performed on a primary table column that matches the definition of the key column in the table to read. 288 InfoSphere Change Data Capture Management Console: Administration Guide . and record format *FIRST. "PRODLIB/CUSTMAST". not found) and assuming that the data type for the CUSTNAME column is CHARACTER. %GETCOL (CUSTNAME. If the read is unsuccessful (for example. The %GETCOL function retrieves secondary table columns before replicating them along with primary table columns to the target. and record format *FIRST.

<key_name>. <key_value1>.<. Note the following when specifying this parameter: – If you installed InfoSphere CDC for Oracle. the primary and secondary tables must have one or more key columns. . If the read is unsuccessful or a previous %GETCOL function invocation was not performed. The table_name parameter specified in the short format of the %GETCOL function invocation must match the table_name parameter specified in the long format of the %GETCOL function invocation. based on the data type of the derived column. you can specify the table name in the format ’<OWNER_NAME>. then you must convert them to the appropriate data types using conversion column functions.. If you specify a table or column name that contains spaces. Long syntax format—reads from database %GETCOL(<column_name>..″. such as %TOCHAR.<TABLE_NAME>’. <table_name>. based on the key column names and values that are identified. The key columns in the primary and secondary tables are used to retrieve a different column in the secondary table. If you are using InfoSphere CDC for z/OS. if the key column data types are different. enter [EMP NY] to reference a table named ″EMP NY″. then InfoSphere CDC generates an error message when verifying the expression that contains the %GETCOL function. where the owner and table are in uppercase. then see %GETCOL and %SELECT Function Calls and Processing Efficiency in your InfoSphere CDC for z/OS documentation for information about performance considerations when using the %GETCOL or %SELECT column functions.. The key columns that are used to retrieve data can have different names and data types. then you must enclose that name in square brackets. <default_value>) This function returns the value of a the specified column from a row retrieved by a previous %GETCOL function invocation. then InfoSphere CDC generates an error message and sets the values of the derived column in which the %GETCOL function is used to default values. If the specified column does not exist in the secondary table.. then InfoSphere CDC assumes that the owner is the user that installed InfoSphere CDC. <key_name>. Column functions 289 . If ownership of the table cannot be determined.If you installed InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for Sybase. <key_valuen>) This function reads a table and returns the value of the column specified. <key_value2>. Parameters v column_name—Specifies the name of a column. The short syntax lets you retrieve more than one column from a table (that was read previously using the %GETCOL function). you must specify the table name in the format ″. Note: This topic contains information about the %GETCOL function supported by any InfoSphere CDC product except for InfoSphere CDC for AS/400.To use this function. However. Short syntax format—reads from existing &GETCOL result %GETCOL(<column_name>.default_value>. then InfoSphere CDC assumes the default value of PUBLIC for the owner name. You cannot specify an expression for this parameter. For example. <table_name>. If you omit the owner name. without reading the table again. v table_name—Specifies the name of a table.

<table_name>″ or ’<owner_name>. If you specify NULL as the default value. v key_value—Specifies. Note: For InfoSphere CDC for z/OS.<table_name>″ or ’[owner_name]. The key value can be any expression. use the %IF function. v key_name—Identifies the key column name in the secondary table used to retrieve the secondary column specified by column_name. To ensure that the %GETCOL function is invoked only for records with non-NULL key values. you must specify the table name in the format ″[owner_name]. the %GETCOL function returns a default value according to the data type of the column specified. Examples The following examples use the relationship between primary and secondary tables. Result data type The data type of the column retrieved (column_name). for each key column. v default_value—Specifies a default value to return when no row can be found in the secondary table using the key value that matches the value of the referring (foreign) key column in the primary table row. but is not specified in a %GETCOL function invocation. even if the source column contains multi-byte data. If the corresponding row cannot be found in the secondary table. 290 InfoSphere Change Data Capture Management Console: Administration Guide . an associated key value. The %GETCOL function returns the value of the column as singlebyte characters.– If you installed InfoSphere CDC for z/OS. Note: The DB2 UDB for z/OS API requires that the column specified in key_name is not nullable. If you omit this parameter. In this case. then the column must be nullable. If you specify a primary column name. InfoSphere CDC generates an error if a default value is required. For certain InfoSphere CDC products.<table_name>’. InfoSphere CDC for z/OS generates an error message if it encounters a NULL key value when processing the %GETCOL function. – If you installed InfoSphere CDC for DB2 UDB or InfoSphere CDC for PointBase. you must specify the table name in the format ″<owner_name>. You can specify multiple key name and value pairs. then InfoSphere CDC uses the after image value of that column as the key_value for the key column in the secondary table to locate the corresponding row in the secondary table. then the default value populates the derived column for the row sent to the target. this is a required parameter. you can specify up to nine key_name/key_value pairs.<table_name>’. then you must enter two consecutive commas (for the long syntax) or a comma (for the short syntax) prior to the right parenthesis to indicate its position in the parameter list.

EMPBRANCH) Assuming the primary and secondary tables shown above. EMPQ3. Column functions 291 . this example returns their country from the COUNTRY secondary table record. If COUNTRY does not contain a record that satisfies the condition in the WHERE clause. For an employee in the EMPLOYEE primary table. and fourth quarter sales figures. third. For example. this example returns their first quarter sales figure from the SALES secondary table record. then this function returns the default value for the data type of the COUNTRY column.GSMITH.%SELECT("SELECT COUNTRY FROM DB1. to maintain the second. You can retrieve these values using the %VAR function and map them to the EMPQ2. you map the %SELECT function to the EMPQ1 column in the EMPLOYEE table. you map the %SELECT function to the EMPCOUNTRY column in the EMPLOYEE table. respectively. 0. 0. Since this example returns more than one column value. 0. named Q2. who works at Branch 4. %SELECT("SELECT Q1. Q2. and EMPQ4 columns in EMPLOYEE.COUNTRY WHERE BRANCH = ?". 0) Assuming the primary and secondary tables shown above. blank characters if the data type is character. Q3. EMPBRANCH.SALES WHERE EMP = ? AND ? = 4". Q3. Q4 FROM DB1. InfoSphere CDC defines three variables. and Q4.GSMITH. For an employee in the EMPLOYEE primary table. EMPID.

EMPID. v The CODE variable is set to ″Z″. InfoSphere CDC sets the three variables Q2. this example returns their income from the SALARY secondary table record. 292 InfoSphere Change Data Capture Management Console: Administration Guide . EMPBRANCH. reference LASTADJDATE before CODE in the SQL SELECT statement. For an employee in the EMPLOYEE primary table located in United States. this example returns the amount of vacation used from the VACATION secondary table record. For an employee in the EMPLOYEE primary table. If SALARY does not contain a record that satisfies the condition in the WHERE clause. SYSDUMMY1 is an existing DB2 dummy system table referenced in the SQL SELECT statement to satisfy syntax requirements. Q3.SALARY WHERE EMP = ? AND BRANCH = ?". NEXTADJDATE FROM DB1. Since this column is listed third in the SQL SELECT statement. ’JAPAN’. you must specify a default value for LASTADJDATE only. or France. you map the %SELECT function to the EMPVACUSED column in the EMPLOYEE table. Since this example returns more than one column value.SYSDUMMY1". and NEXTADJDATE. then the function returns 0. ’UK’. To eliminate the need to specify a default value for CODE. LASTADJDATE. NEXTADJDATE FROM DB1. you must also specify default values for the INCOME and CODE columns. This example uses the %SELECT function to retrieve the next value for a sequence in DB2 UDB for z/OS V8 or higher. and Q4 to 0. you map the %SELECT function to the EMPINCOME column in the EMPLOYEE table. In addition.GSMITH. CODE. 1970-01-01) Assuming the primary and secondary tables shown in the table diagram previously. LASTADJDATE. "Z". then the %SELECT function returns 0.VACATION WHERE EMP = ? AND EMPCOUNTRY IN (’USA’. EMPID. If VACATION does not contain a record that satisfies the condition in the WHERE clause. CODE. 0) Assuming the primary and secondary tables shown in the previous image.SALARY WHERE EMP = ? AND BRANCH = ?". InfoSphere CDC defines three variables. v The LASTADJDATE variable is set to 1970-01-01. EMPBRANCH. 1) This example returns the next value for sequence SEQ1. 1970-01-01). In this example. named CODE.GSMITH. EMPID. %SELECT("SELECT INCOME. the data type of the result is the same as the data type of the sequence object. then: v The %SELECT function returns 0. ’FRANCE’)". v The NEXTADJDATE variable is set to 1901–01–01 (the z/OS default date value). 0. 0.GSMITH. LASTADJDATE. In this case. You can retrieve these values using the %VAR function and map them to columns that you must add to the primary table. to maintain the other items of salary information. %SELECT("SELECT USED FROM DB1. %SELECT("SELECT NEXT VALUE FOR SEQ1 FROM SYSIBM. Japan. United Kingdom.If SALES does not contain a record that satisfies the condition in the WHERE clause. as follows: %SELECT("SELECT INCOME.

24) This example returns the previous value for sequence SEQ2. Syntax %SELECT(<sql_select_stmt>. in order to call the function. . you should exercise caution when using the %SELECT function to issue SQL SELECT statements. For example. see your DB2 UDB for z/OS documentation. <parm>. see your DB2 UDB for z/OS documentation. . SYSDUMMY1 is an existing DB2 dummy system table referenced in the SQL SELECT statement to satisfy syntax requirements. %SELECT("SELECT PREVIOUS VALUE FOR SEQ2 FROM SYSIBM.. Related reference “Character conversion—%TOCHAR” on page 274 “Retrieve column—%GETCOL (DB2 UDB for iSeries)” on page 285 “Conditional–%IF” on page 282 Retrieve column—%SELECT Use this function to specify a valid SQL SELECT statement that retrieves one or more column values from a secondary table so that they can be logically joined to a primary table record. Note: This function is only supported by InfoSphere CDC for z/OS. the data type of the result is the same as the data type of the sequence object. <parm2>. Therefore. 24.. You must Column functions 293 . The statement must be valid according to DB2 UDB for z/OS usage rules. see the ″%GETCOL and %SELECT Function Calls and Processing Efficiency″ section in your InfoSphere CDC for z/OS documentation. [default_value2]. You must enter any integer value for the second parameter. <parm>. For information about performance considerations when using the %GETCOL or %SELECT column functions. For usage rules.. For information about sequences and the types of values that you can generate from sequences. This example uses the %SELECT function to retrieve the previous value for a sequence in DB2 UDB for z/OS V8 or higher.. For example. For information about sequences and the types of values that you can generate from sequences. [default_value]..SYSDUMMY1".You must enter any integer value for the second parameter.[default_value]) Parameters v sql_select_stmt—Specifies a character string containing a valid SQL SELECT statement. in order to call the function. the z/OS user identifier that is used to start the InfoSphere CDC address space must have sufficient DB2 UDB for z/OS privileges to perform SQL SELECT statements. Certain clauses and functions may have side effects that result in the changing of DB2 table data and/or the generation of data outside of the control of DB2. In this case. see your DB2 UDB for z/OS documentation.. CAUTION: The use of SQL SELECT statements may constitute a security concern in your environment. To use this function. 1. You can specify only one SQL SELECT statement in each %SELECT function.

In the WHERE clause. default_value2. Using a single %SELECT function to retrieve all secondary table column values and then using the %VAR function to map to subsequent columns is more efficient than invoking the %SELECT function multiple times to retrieve each column value individually. you can retrieve the values assigned to variables and map them to subsequent columns in the primary table.. then these values are assigned to variables.. of the corresponding column in the SQL SELECT statement. expression variables. For information about other operators that you can use.. Result data type The data type of the first secondary table column listed in the SQL SELECT statement. If two or more column values are retrieved by the SQL SELECT statement. . If these variable names cannot be defined. starting at 1. the variable names are the same as the corresponding column names. then the previously defined variables will be overwritten. The result of the %SELECT function is a value from the first column specified in the SQL SELECT statement. default_value1. column functions. you can use any operators that are supported by DB2 UDB for z/OS. zero for numeric-based columns. zero-length strings for characterbased columns. Note: If you have defined variables that have the same names as those created by InfoSphere CDC automatically. expressions.. By default. then you must also specify another parameter for the function. and so on.use parameter placeholders to refer to values that are not available until the expression is being executed. 294 InfoSphere Change Data Capture Management Console: Administration Guide . Using the %VAR function in expressions. and so on. the value specified for parm1 replaces the first question mark. To identify parameter placeholders in the SQL SELECT WHERE clause. parmn—Specify literals. see your DB2 UDB for z/OS documentation. based on the data type of the column. To specify a default value for a column that is not listed first in the SQL SELECT statement. make sure existing variable names that you have defined do not conflict with variable names created by InfoSphere CDC. then this function returns an appropriate value. or primary table columns. such as IN. Therefore. the value specified for parm2 replaces the second question mark in the WHERE clause. you must specify default values for all preceding columns. If you only want to specify the SQL SELECT statement parameter. v parm1. where n is the numeric position. use question marks (?). then the names are set to COLn. Note the following when specifying parameters for this function: – The number of parameters cannot exceed 21. If you do not specify a default value for a column and the secondary table record does not exist. – You must specify a minimum of two parameters. v default_valuem—Specify default values that the function returns for each column when the record specified by the WHERE clause does not exist in the secondary table. See examples below for situations where you must specify an unused parameter.. For example. You cannot specify NULL for any parameter placeholder. . parm2. In the SQL WHERE clause..

Q3. Since this example returns more than one column value. For example. blank characters if the data type is character. you map the %SELECT function to the EMPQ1 column in the EMPLOYEE table. For an employee in the EMPLOYEE primary table. and Q4.GSMITH. 0. this example returns their country from the COUNTRY secondary table record. %SELECT("SELECT Q1. Q3.Examples The following examples use the relationship between primary and secondary tables: %SELECT("SELECT COUNTRY FROM DB1. 0.COUNTRY WHERE BRANCH = ?". EMPBRANCH) Assuming the primary and secondary tables shown above. to maintain the second. InfoSphere CDC defines three variables. named Q2. and fourth Column functions 295 . Q4 FROM DB1. 0. Q2. this example returns their first quarter sales figure from the SALES secondary table record. who works at Branch 4. third. then this function returns the default value for the data type of the COUNTRY column.SALES WHERE EMP = ? AND ? = 4". you map the %SELECT function to the EMPCOUNTRY column in the EMPLOYEE table. 0) Assuming the primary and secondary tables shown above.GSMITH. EMPID. EMPBRANCH. For an employee in the EMPLOYEE primary table. If COUNTRY does not contain a record that satisfies the condition in the WHERE clause.

1) This example returns the next value for sequence SEQ1. named CODE. Since this example returns more than one column value. Q3. Japan. For an employee in the EMPLOYEE primary table located in United States. NEXTADJDATE FROM DB1. %SELECT("SELECT INCOME. %SELECT("SELECT NEXT VALUE FOR SEQ1 FROM SYSIBM. then the %SELECT function returns 0. this example returns the amount of vacation used from the VACATION secondary table record.GSMITH.VACATION WHERE EMP = ? AND EMPCOUNTRY IN (’USA’. If SALES does not contain a record that satisfies the condition in the WHERE clause.GSMITH. v The LASTADJDATE variable is set to 1970-01-01. "Z".SALARY WHERE EMP = ? AND BRANCH = ?". InfoSphere CDC sets the three variables Q2.SYSDUMMY1". To eliminate the need to specify a default value for CODE. then: v The %SELECT function returns 0. NEXTADJDATE FROM DB1. This example uses the %SELECT function to retrieve the next value for a sequence in DB2 UDB for z/OS V8 or higher. LASTADJDATE. EMPID. 0. 0) Assuming the primary and secondary tables shown in the previous image. You can retrieve these values using the %VAR function and map them to columns that you must add to the primary table.SALARY WHERE EMP = ? AND BRANCH = ?". For an employee in the EMPLOYEE primary table. you must specify a default value for LASTADJDATE only. and Q4 to 0. EMPBRANCH. LASTADJDATE. EMPID. EMPID. reference LASTADJDATE before CODE in the SQL SELECT statement. If SALARY does not contain a record that satisfies the condition in the WHERE clause. United Kingdom. ’FRANCE’)". you must also specify default values for the INCOME and CODE columns. EMPBRANCH. ’UK’. as follows: %SELECT("SELECT INCOME. the data type of the result is the same as the data type of the sequence object. ’JAPAN’. You can retrieve these values using the %VAR function and map them to the EMPQ2. 1970-01-01) %SELECT("SELECT USED FROM DB1. respectively. 1970-01-01) Assuming the primary and secondary tables shown in the previous image.quarter sales figures. LASTADJDATE. you map the %SELECT function to the EMPVACUSED column in the EMPLOYEE table. SYSDUMMY1 is an existing DB2 dummy system table referenced in the SQL SELECT statement to satisfy syntax requirements.Since this column is listed third in the SQL SELECT statement. In this case. If VACATION does not contain a record that satisfies the condition in the WHERE clause. In addition. CODE. 0. In this example. you map the %SELECT function to the EMPINCOME column in the EMPLOYEE table.GSMITH. and EMPQ4 columns in EMPLOYEE. or France. v The NEXTADJDATE variable is set to 1901-01-01 (the z/OS default date value). to maintain the other items of salary information. 296 InfoSphere Change Data Capture Management Console: Administration Guide . CODE. and NEXTADJDATE. v The CODE variable is set to ″Z″. this example returns their income from the SALARY secondary table record. then the function returns 0. EMPQ3. InfoSphere CDC defines three variables.

See also: “Stored procedure—%STPROC” “User exit—%USER” on page 298 “User exit—%USER (InfoSphere CDC for Microsoft SQL 5. the data type of the result is the same as the data type of the sequence object. For example. see your DB2 UDB for z/OS documentation. you must specify the name of the stored procedure in the format <databae_name>. For information about sequences and the types of values that you can generate from sequences. see your DB2 UDB for z/OS documentation.<stored_procedure_name>.. Depending on the InfoSphere CDC platform you have installed. <parm20>) Parameters v stored_procedure_name—Specifies the name of the stored procedure in the default database.x)” on page 302 “User Exit—%USERFUNC” on page 303 Stored procedure—%STPROC Use this function to call a stored procedure. If you installed InfoSphere CDC for Microsoft SQL Server. Note: InfoSphere CDC for z/OS and InfoSphere CDC for DB2 UDB do not support this function. On the z/OS platform. You must enter any integer value for the second parameter. you can call a stored procedure or another type of user exit program using a column function. This example uses the %SELECT function to retrieve the previous value for a sequence in DB2 UDB for z/OS V8 or higher. .. You must enclose values of this parameter in single quotes. in order to call the function. 1. in order to call the function. 24. The database and owner name are not required if the stored procedure is defined in the default database. You can call a stored procedure from a derived column on the source or create an expression on the target..<owner_name>. <parm2>. %SELECT("SELECT PREVIOUS VALUE FOR SEQ2 FROM SYSIBM. For example. Syntax %STPROC(’stored_procedure_name’. 24) This example returns the previous value for sequence SEQ2. use the %USER function to call a user exit program that issues SQL statements. SYSDUMMY1 is an existing DB2 dummy system table referenced in the SQL SELECT statement to satisfy syntax requirements. <parm1>.SYSDUMMY1". For information about sequences and the types of values that you can generate from sequences. User exit functions Use these functions to call user exit programs from expressions.You must enter any integer value for the second parameter. Column functions 297 . In this case.

if you specify values for the first two parameters only. parm20—Specify columns or literals that are passed as parameters to the stored procedure (maximum 20). For example. begin select name1 into nameFound from customer where custno = custid.. Related tasks “To add a derived column” on page 163 “To map an expression to a target column” on page 159 Related reference “User exit—%USER” User exit—%USER Use this function to call a user exit program from an expression.. ... . InfoSphere CDC assigns default values to the last three parameters. If you installed InfoSphere CDC for Sybase. 2. CUSTOMER_ID) This call returns the customer name that corresponds to the customer identification number CUSTOMER_ID. @CUSTID int as select @CUSTNAME=name from customer where custno=@CUSTID v If you installed InfoSphere CDC for Oracle: create or replace function custname (custid integer) return varchar2 as nameFound varchar2(30). 298 InfoSphere Change Data Capture Management Console: Administration Guide . as presented below. Define a stored procedure. parm2. Do not specify this parameter in the list of parameters for the %STPROC function (parm1. This function provides flexibility when complex logic that cannot be expressed using the provided column functions is required.v parm1. The type and order of the parameters specified in the %STPROC function invocation must match the type and order of the parameters defined in the stored procedure. You can omit any number of trailing parameters.. for a stored procedure with five parameters. InfoSphere CDC assumes the default value if a parameter is not specified. the first parameter defined in the stored procedure specifies the value returned by the function. parm2. parm20). Examples The following example returns the customer name that corresponds to a specified customer identification number. Perform the following steps: 1. in the default database: v If you installed InfoSphere CDC for Microsoft SQL Server or InfoSphere CDC for Sybase: create procedure CUSTNAME @CUSTNAME varchar(30) OUT. return nameFound. 2 Use the following column function: %STPROC(‘CUSTNAME’.. end custname. Result data type The data type of the result returned by the stored procedure. You can use this function to call a user exit program with input parameters.

<parmn> Parameters v program_name—Specifies the name of the user exit program. In the user exit program that you write. Syntax %USER(’<program_name>’. v 1—Result or input parameter is NULL. see the appropriate InfoSphere CDC user exits guide.. You can write the user exit program in any high-level language.For more information about user exit programs. parmn—Specify columns or literals that are passed as parameters to the user exit program (maximum 20). . Specifies the number of decimal places in the result or input parameter. You must enclose values of this parameter in single quotes.. parmn). parm2. If you are using a InfoSphere CDC product other than InfoSphere CDC for z/OS. v parm1.. Note: InfoSphere CDC for Microsoft SQL Server does not support this function. You must place an executable object for the user exit program in the InfoSphere CDC installation directory prior to starting refresh or mirroring. <parm22>. DIGITS Two-byte binary DECPLC Two-byte binary NULLIND Two-byte binary Column functions 299 .. Field DATATYPE Length and data type Two-byte binary Description Specifies the data type of the result or input parameter: v 1—Character v 2—Date v 3—Float v 4—Integer v 5—Packed numeric v 6—Time v 7—Zoned numeric LENGTH Two-byte integer Specifies the length of the result or input parameter in bytes. you cannot use this function to call a stored procedure. parm2. <parm1>. you must declare a data structure that defines specific fields for the result and each input parameter (parm1. Specifies whether or not the result or input parameter is NULL: v 0—Result or input parameter is not NULL..... .. Specifies the number of digits in the result or input parameter. .

v *MDY—The date format is mmddyy. v *DMY—The date format is ddmmyy. For example. DATAMIRROR CORP. AUTHOR. v *EUR—European date format. the field that contains the result returned by the user exit program. see the COBOL user exit program below. passing the BRANCH column as a parameter. USERSEL1. Result data type The data type of the result returned by the user exit program. USERSEL1 checks whether or not BRANCH is set to ’11’. Note: This user exit program is provided for illustration purposes only. IDENTIFICATION DIVISION. then the user exit program returns a one-byte character value of Y.Field DTMFMT Length and data type Four-byte character Description Specifies the date format in the result or input parameter: v *USA—United States date format. PROGRAM-ID. The name of this field in the user exit program is user-defined. the field that contains the input parameter value passed to the user exit program. v *ISO—ISO (International Organization for Standardization) date format. Examples %USER(‘USERSEL1’. BRANCH) This function calls the COBOL program USERSEL1. v For the user exit program result. v *YMD—The date format is yymmdd. it returns a character value of N. <VALUE> Specifies one of the following: v For each input parameter. If it is. v *JIS—Japanese Industrial Standard. IBM recommends that you test this program before invoking it in your environment. Otherwise. 300 InfoSphere Change Data Capture Management Console: Administration Guide .

03 TYP-FLOAT PIC S9(4) VALUE 3. ****************************************************************** * P R O C E D U R E D I V I S I O N ****************************************************************** PROCEDURE DIVISION USING RETURN-VALUE PARM-1. 03 TYP-DATE PIC S9(4) VALUE 2. 03 RV-DTMFMT PIC X(4). MOVE ZERO TO RV-DIGITS. * 01 DATATYPES COMP-4. 03 RV-LENGTH PIC S9(4) COMP-4. 03 P1-DATATYPE PIC S9(4) COMP-4. 01 RETURN-VALUE. OBJECT-COMPUTER. SOURCE-COMPUTER. else returns ‘N’. 03 P1-LENGTH PIC S9(4) COMP-4.INSTALLATION.0 * ---------------* Description: SAMPLE COBOL USER ENTRY POINT PROGRAM * ---------------* ****************************************************************** ENVIRONMENT DIVISION. 03 TYP-CHAR PIC S9(4) VALUE 1. 03 P1-DIGITS PIC S9(4) COMP-4. ******************************************************************* * Program : USERSEL1. 03 P1-BRANCH PIC X(2). 03 P1-DTMFMT PIC X(4). CONFIGURATION SECTION. 03 TYP-INTEGER PIC S9(4) VALUE 4. DATE-COMPILED. MOVE 1 TO RV-LENGTH. 03 RV-DECPLC PIC S9(4) COMP-4. ****************************************************************** * L I N K A G E S E C T I O N ****************************************************************** LINKAGE SECTION. 01 PARM-1. 03 RV-SELECT PIC X(1). Column functions 301 . ****************************************************************** * D A T A D I V I S I O N ****************************************************************** DATA DIVISION. * returns ‘Y’. 03 P1-NULLIND PIC S9(4) COMP-4. 03 RV-NULLIND PIC S9(4) COMP-4. 03 TYP-PACKED PIC S9(4) VALUE 5. ML-0010. 03 TYP-ZONED PIC S9(4) VALUE 7. 03 RV-DATATYPE PIC S9(4) COMP-4. 03 P1-DECPLC PIC S9(4) COMP-4. DATAMIRROR CORP. * ---------------* Version: 1. IBM-AS400. * MOVE TYP-CHAR TO RV-DATATYPE. IBM-AS400. * * Define the Returned Value as a 1-byte character field. ****************************************************************** * W O R K I N G S T O R A G E S E C T I O N ****************************************************************** WORKING-STORAGE SECTION. 03 TYP-TIME PIC S9(4) VALUE 6. 03 RV-DIGITS PIC S9(4) COMP-4. * * This example program checks parm 1 for a value of ‘11’ and if found.

For example.. . MOVE SPACES TO RV-DTMFMT. To call stored procedures in expressions defined on the target. For information about creating Microsoft SQL Server stored procedures.x) If you have installed InfoSphere CDC for Microsoft SQL Server. for a stored procedure with five parameters.. parm20). parm2. Related reference “Stored procedure—%STPROC” on page 297 “User exit—%USER (InfoSphere CDC for Microsoft SQL 5. dbo. This function allows you to specify Microsoft stored procedures as input parameters. The number of parameters specified in the stored procedure must match the number of parameters specified in Management Console. see InfoSphere CDC for Microsoft SQL Server User Exits Guide. * IF P1-BRANCH IS EQUAL TO ‘11’ MOVE ‘Y’ TO RV-SELECT ELSE MOVE ‘N’ TO RV-SELECT.. Do not specify this parameter in the %USER parameter list (parm1.<owner_name>. EXIT PROGRAM. The first parameter defined in the stored procedure must be the OUTPUT parameter followed by the input parameters. For example. use this function to call a stored procedure on the source. You can omit any number of trailing parameters.<stored_procedure_name>.x)” “User Exit—%USERFUNC” on page 303 User exit—%USER (InfoSphere CDC for Microsoft SQL 5. <parm2>. Note: This function is only supported by InfoSphere CDC for Microsoft SQL Server on the source. if you specify values for the first two parameters only. . v parm1. The type and order of the parameters specified in the %USER call must match the type and order of the parameters defined in the stored procedure. InfoSphere CDC assigns default values to the last three parameters. use the %STPROC function. . v owner_name—specifies the owner of the stored procedure.. v stored_procedure_name—specifies the name of the stored procedure. MOVE ZERO TO RV-NULLIND.. <parm20> Parameters v database_name—specifies the name of the database where the stored procedure resides.. 302 InfoSphere Change Data Capture Management Console: Administration Guide .. parm2.. Syntax %USER(<database_name>. parm20—specify columns or literals that are passed as parameters to the stored procedure (maximum 20). * * Test for a value of ‘11’ in the first parameter..MOVE ZERO TO RV-DECPLC. <parm1>. InfoSphere CDC assumes the default value if a parameter is not specified.

@in_date datetime AS select @out_int = DATEDIFF(day.sp_join".item_list. not column names. You can use this function to call a user exit program with input parameters. These examples assume that a stored procedure. program_name. Syntax %USERFUNC(function_type.dbo.item_number = @in_item_number) GO Related reference “Stored procedure—%STPROC” on page 297 “User exit—%USER” on page 298 “User Exit—%USERFUNC” User Exit—%USERFUNC Use this function to call a Java class user exit program or a stored procedure from an expression. <parm2>.description ON inventory_db. . is defined in the database... The example stored procedure calculates the difference in days between the current date and a date specified as parameter: CREATE PROCEDURE dbo. while the second call example specifies a value as input parameter (″12-jan-2000″). is defined in the database.col_item_number) %USER("datamirror. while the second call example specifies a value as input parameter (12).dbo.dbo.description.description.. see your InfoSphere CDC user exits documentation.item_desc FROM inventory_db. similar to the following.dbo. These examples assume that a stored procedure. Specify “JAVA” to call a Java class user exit program or “STOREDPROC” to call a stored procedure user exit program.dbo. For more information about user exit programs. getdate()) GO %USER("datamirror. You must enclose these values in double quotes to indicate they are strings.item_number WHERE (inventory_db."12-jan-2000") The first call example specifies a source column name as input parameter (COL_DATE). [<parm1>.sp_date_diff @out_int int output.dbo. @in_date.dbo.item_number = inventory_db. The example stored procedure performs a join to a description table to get the description of an item given its item number: CREATE PROCEDURE dbo.description. This function provides flexibility when complex logic that cannot be expressed using the provided column functions is required.sp_join".sp_date_diff".COL_DATE) %USER("datamirror. Column functions 303 . This function also supports MBCS data.dbo.12) The first call example specifies a source column name as input parameter (col_item_number).dbo.sp_date_diff".sp_join @out_item_description varchar(10) output @in_item_number int AS SELECT @out_item_description = inventory_db.Result data type The data type of the result returned by the stored procedure.dbo. <parmn>] Parameters v function_type—Indicate the type of user exit. similar to the following. Examples %USER("datamirror.item_list INNER JOIN inventory_db.

.item_desc FROM inventory_db. is defined in the database. If your Java class has a package name then you must create the appropriate directories under the lib directory. The example stored procedure performs a join to a description table to get the description of an item given its item number. These examples assume that a stored procedure.dbo. These examples assume that a stored procedure. The stored procedure must exist in your database and you must specify the stored procedure name and database owner or schema.sp_date_diff @out_int int output. while the second call example specifies a value as input parameter (″12-jan-2000″).The Java class should be placed in your lib directory."dbo. The example stored procedure calculates the difference in days between the current date and a date specified as parameter.item_list INNER JOIN inventory_db. @in_date."12-jan-2000") The first call example specifies a source column name as input parameter (COL_DATE).COL_DATE) %USERFUNC("STOREDPROC". @in_date datetime AS select @out_int = DATEDIFF(day.description."dbo.sp_date_diff".sp_join".sp_date_diff".col_item_number) %USERFUNC("STOREDPROC".description ON 304 InfoSphere Change Data Capture Management Console: Administration Guide ."dbo. BRANCH) This function calls the Java user exit program of USERSEL1 and passes the BRANCH column as a parameter. CREATE PROCEDURE dbo. The stored procedure must exist in your database and you must specify the database owner or schema. Stored procedures must exist in your database you must specify the database owner or schema as well as the name of the stored procedure. getdate()) GO %USERFUNC("STOREDPROC". The stored procedure must exist in your database and you must specify the stored procedure name and database owner or schema: CREATE PROCEDURE dbo. Otherwise. parm2. while the second call example specifies a value as input parameter (12). "USERSEL1".dbo. is defined in the database. v program_name—The name of your Java class or stored procedure. v parm1. ..dbo. Result data type The data type of the result returned by the stored procedure. %USERFUNC("STOREDPROC".sp_join". If it is. similar to the following. USERSEL1 checks whether or not BRANCH is set to ’11’.12) The first call example specifies a source column name as input parameter (col_item_number). then the user exit program returns a one-byte character value of Y.. parmn—Specify columns or literals that are passed as parameters to the Java class user exit or stored procedure user exit.sp_join @out_item_description varchar(10) output @in_item_number int AS SELECT @out_item_description = inventory_db. similar to the following. it returns a character value of N. Examples %USERFUNC("JAVA"."dbo.

dbo. ″PRODLIB/STATE″.x)” on page 302 %GETCOL column function scenarios (DB2 UDB for iSeries) The %GETCOL column function scenarios in this section are specific to InfoSphere CDCInfoSphere CDC for AS/400.item_list. To use this example.description. STNAME.item_number = inventory_db. In this example. STATE. based on the NAME column. STATE) Column functions 305 .dbo. 1. Add a derived column.inventory_db. 2. .item_number = @in_item_number) GO Related concepts “Setting multibyte and Unicode character set conversions” on page 175 Related reference “Stored procedure—%STPROC” on page 297 “User exit—%USER” on page 298 “User exit—%USER (InfoSphere CDC for Microsoft SQL 5. you will retrieve the column NAME from the STATE table using the STATE column from the EMPLOYEE table. and COUNTRY) tables. perform the following steps: 1. Enter the following expression for the STNAME derived column: %GETCOL(NAME. to the STATE table. See also: “Retrieving a column from another table using the %GETCOL function (DB2 UDB for iSeries)” “Performing an outer join using the %GETCOL function (DB2 UDB for iSeries)” on page 306 “Nesting columns to join data using the %GETCOL function (DB2 UDB for iSeries)” on page 306 “Combining columns using the %GETCOL function (DB2 UDB for iSeries)” on page 306 Retrieving a column from another table using the %GETCOL function (DB2 UDB for iSeries) This example uses the relationship between a primary (EMPLOYEE) and secondary (BRANCE. “%GETCOL column function scenarios (Dynamic SQL)” on page 307.item_number WHERE (inventory_db.description.dbo. If you are using a different InfoSphere CDC product. .

Add a derived column. In this example. 1. CTNAME. 1. ″PRODLIB/STATE″. based on the NAME column. to the COUNTRY table. CTNAME. 1. This column was retrieved in a previous %GETCOL invocation. In this example. ″-″. perform the following steps: 1. . you will combine the STATE and COUNTRY columns from the STATE table using the %CONCAT function. used to read the COUNTRY table. To use this example. Enter the following expression for the REGION column: %CONCAT(%GETCOL(STATE. ″PRODLIB/STATE″. the default_value and record_format parameters are not specified. STATE)) This function retrieves the NAME column from the COUNTRY table using the STATE column from the EMPLOYEE table and the COUNTRY column from the STATE table. perform the following steps: 1. Add a derived column. %GETCOL(COUNTRY. . Add a derived column. Nesting columns to join data using the %GETCOL function (DB2 UDB for iSeries) This example uses the relationship between primary and secondary tables. In the first %GETCOL function. To use this example. In this example. . you will retrieve the column NAME from the COUNTRY table using the COUNTRY column from the STATE table. to the COUNTRY table. Related reference 306 InfoSphere Change Data Capture Management Console: Administration Guide . ″PRODLIB/COUNTRY″. as they are specified in the long version of the %GETCOL function that performed the read. based on the STATE and COUNTRY columns in the STATE table. 2. Combining columns using the %GETCOL function (DB2 UDB for iSeries) This example uses the relationship between primary and secondary tables. 2. Enter the following expression for the CTNAME column: %GETCOL(NAME. is not from the primary table. you will consolidate data from secondary tables without replicating the secondary tables. ″PRODLIB/STATE″)) The second %GETCOL function retrieves the COUNTRY column from the STATE table. To use this example. %GETCOL(COUNTRY. 2. .Performing an outer join using the %GETCOL function (DB2 UDB for iSeries) This example uses the relationship between primary and secondary tables. The COUNTRY column. REGION. %GETCOL(COUNTRY. based on the NAME column. . perform the following steps: 1. . ″PRODLIB/STATE″. 1. ″PRODLIB/COUNTRY″. This column was retrieved in a previous %GETCOL function invocation. . STATE). ″FAILED″. Enter the following expression for the CTNAME column: %GETCOL(NAME. ″FAILED″)) The second %GETCOL function retrieves the COUNTRY column from the STATE table.

you can also refer to “Retrieve column—%SELECT” on page 293. depending on your database. using the value in the BRANCH column in the primary table and the key column BRANCHB in the secondary table. STATE.BRANCH secondary table. ″MASTER.BRANCH″. %GETCOL(NAMEB.DBO. Column functions 307 .BRANCH table. To use the example. The table names referenced in the examples follow the format for InfoSphere CDC for Microsoft SQL Server and InfoSphere CDC for Sybase.DBO. For InfoSphere CDC for z/OS.DBO. BRANCHB. and COUNTRY) table relationship. ″<NO NAME>″. then this function returns ″″ for that record in the retrieved column. see the table_name parameter for information about specifying table names for this function.“Concatenation—%CONCAT” on page 262 %GETCOL column function scenarios (Dynamic SQL) The %GETCOL column function scenarios in this section apply to any InfoSphere CDC product except InfoSphere CDC for AS/400. you must add a derived column to the MASTER.EMPLOYEE primary table and enter the specified %GETCOL function in that column. If you installed another InfoSphere CDC product. BRANCH) This example retrieves the NAMEB column from the MASTER.DBO. See also: “Retrieving a “Retrieving a row from the “Retrieving a page 308 column using the %GETCOL function (Dynamic SQL)” column using the %GETCOL function without reading the same table” on page 308 column using nested %GETCOL functions (Dynamic SQL)” on “Filtering rows using the %GETCOL function (Dynamic SQL)” on page 309 Retrieving a column using the %GETCOL function (Dynamic SQL) This example refers to the primary (EMPLOYEE) and secondary (BRANCH. If a record in the primary table has a branch number that does not exist in the MASTER.

″MASTER.COUNTRY″.STATE″. The table names referenced in the examples follow the format for InfoSphere CDC for Microsoft SQL Server and InfoSphere CDC for Sybase. blank characters if the data type is character. ″″)) 308 InfoSphere Change Data Capture Management Console: Administration Guide . %GETCOL(COUNTRYS. %GETCOL(NAMEC.STATE secondary table. ″MASTER. without reading again the same row from the table.EMPLOYEE primary table and enter the specified %GETCOL function in that column. depending on your database. see the table_name parameter for information about specifying table names for this function. For example.STATE.DBO. To use the example. STATES. If a record in the primary table has a state that does not exist in MASTER. then this function returns the default value for the data type of the NAMES column. depending on your database.DBO. ″MASTER. ″MASTER. STATE) This function call retrieves the NAMES column from the MASTER. ″MASTER. . this function call retrieves the COUNTRYS column from the MASTER.STATE″. If you installed another InfoSphere CDC product.DBO. Retrieving a column using nested %GETCOL functions (Dynamic SQL) This example refers to the primary and secondary table relationship.Retrieving a column using the %GETCOL function without reading the same row from the table This example refers to the primary and secondary tables. . If you installed another InfoSphere CDC product. For example.DBO.DBO. using the key column STATE in the primary table and the key column STATES in the secondary table.STATE″. If a record in the primary table has a state that does not exist in MASTER. STATES. The table names referenced in the examples follow the format for InfoSphere CDC for Microsoft SQL Server and InfoSphere CDC for Sybase.STATE″. %GETCOL(NAMES.EMPLOYEE primary table and enter the specified %GETCOL function in that column.DBO. then this function returns the default value for the data type of the NAMES column. To use the example. blank characters if the data type is character. blank characters if the data type is character. %GETCOL(NAMES. using the key column STATE in the primary table and the key column STATES in the secondary table. If a record in the primary table has a state that does not exist in MASTER.DBO. you must add a derived column to the MASTER.STATE secondary table. .STATE. STATE) This function call retrieves the NAMES column from the MASTER.DBO.STATE secondary table. For example. see the table_name parameter for information about specifying table names for this function. ″″) Used after the previous %GETCOL function. you must add a derived column to the MASTER.DBO. then this function returns the default value for the data type of the COUNTRYS column.DBO.DBO. %GETCOL(COUNTRYS.DBO. COUNTRYC.STATE.DBO.

with a COUNTRYS value set to USA.STATE table and compares them with ’USA’.DBO. ″MASTER. Then. you must add a derived column to the MASTER. In this example you do not retrieve the NAMEC column in the MASTER.DBO.DBO. are either selected or omitted for replication.COUNTRY table using the key column COUNTRYS in MASTER. If you installed another InfoSphere CDC product. the second %GETCOL function in this example is called first to retrieve the COUNTRYS column from the MASTER.DBO.COUNTRY table directly. . see the table_name parameter for information about specifying table names for this function. The table names referenced in the examples follow the format for InfoSphere CDC for Microsoft SQL Server and InfoSphere CDC for Sybase. the first %GETCOL function is called to retrieve the NAMEC column from the MASTER. To use the example. using the COUNTRYC key column. The function retrieves values of the COUNTRYS column from the MASTER. %GETCOL(COUNTRYS. The table names referenced in the examples follow the format for InfoSphere CDC for Microsoft SQL Server and InfoSphere CDC for Sybase.STATE″.EMPLOYEE primary table and enter the specified %GETCOL function in that column.DBO.STATE table.DBO.COUNTRY. Filtering rows using the %GETCOL function (Dynamic SQL) This example refers to the primary and secondary table relationship.EMPLOYEE primary table. If you installed another InfoSphere CDC product.DBO. Publishing multiple derived columns using the %GETCOL function (Dynamic SQL) This example refers to the primary and secondary table relationship. depending on your database.DBO. Depending on your rowfiltering settings on the Filtering tab. see the table_name parameter for information about specifying table names for this function. Instead.DBO. because the primary table does not contain a key column to retrieve NAMEC.DBO. depending on your database. STATES.COUNTRY. rows in the MASTER.DBO. Column functions 309 . you retrieve the NAMEC column indirectly using the COUNTRYS key column in MASTER.STATE and the key column COUNTRYC in MASTER.Used after the previous %GETCOL function. STATE) = ’USA’ This example uses the %GETCOL function in a row-filtering expression.STATE and the COUNTRYC key column in MASTER.

By calling the %GETCOL function twice.This example combines the CUSTID and CUSTADDR tables into a single CUSTOMER table with all five columns. ″Not Found″.CUSTADDR″. to the CUSTID source table and enter the following expression for the column: %GETCOL(ADDRESS1. Instead. Add a derived column.DBO. ADDR1. to the CUSTID source table and enter the following expression for the column: %GETCOL(ADDRESS2.CUSTADDR″. To use this example. The expression for ADDR2 uses the results returned by the previous %GETCOL function invocation without reading the CUSTADDR table. ″MASTER. CUSTNO) 2. it uses matching rows from the ADDR2 definition to know when to return the value from the ADDRESS2 column. Add a derived column. If either %GETCOL function cannot find a matching row. CUSTNO. 310 InfoSphere Change Data Capture Management Console: Administration Guide . ″Not Found″) The expression for ADDR1 queries the CUSTADDR table and returns the value in the ADDRESS1 column where the two CUSTNO values match. perform the following steps: 1. ADDR2. you retrieve values of two columns from the same row in the secondary table. without reading the same table twice. The first call reads the entire row into memory and the second call retrieves data from the same row in memory. ″MASTER.DBO. then it returns a value of ″Not Found″.

Related concepts “Filtering rows and columns” on page 167 Column functions 311 .

312 InfoSphere Change Data Capture Management Console: Administration Guide .

Maintain these default settings until you become familiar with the configuration of InfoSphere CDC. 2008 313 . The default system parameter settings are appropriate for most installations. v When upgrading to a higher version of InfoSphere CDC. See also: “AuthCode” on page 314 “DBMS” on page 314 “dbUser” on page 314 “dllname” on page 314 “DSN” on page 314 “NetServiceName” on page 315 “pwdencrypt” on page 315 “Startup Timeout” on page 315 “TSSrcCP” on page 315 © Copyright IBM Corp. Notes: v If you make changes to a system parameter during active replication. you must stop and restart replication for the changes to take effect. then you can use system parameters to modify the behavior of default operations in InfoSphere CDC.3 and below) System parameters let you control the behavior of InfoSphere CDC. any pre-existing settings for system parameters are maintained. If your replication environment requires a particular configuration. InfoSphere CDC provides system parameters that control the behavior of your source and/or target datastores.System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. In this section. you will learn: “General product system parameters” “Replication system parameters” on page 317 “Database translation log system parameters” on page 319 “Commitment control system parameters” on page 323 “Event log system parameters” on page 325 “Multibyte character set system parameters” on page 325 “Latency system parameters” on page 326 “Notification system parameters” on page 329 “Tracing system parameters” on page 332 “Data type system parameters” on page 335 “Lock detection system parameters” on page 335 General product system parameters General product system parameters let you control basic features of InfoSphere CDC and information you may have specified during installation.

see your IBM representative. see your IBM representative. Applies To—Source and Target dllname For information about setting this system parameter.“TSTgtCP” on page 316 “TCP_KEEPALIVE_SECS” on page 316 “WindowsAuthentication” on page 316 AuthCode Use this system parameter to adjust the authorization code issued by IBM.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 DBMS For information about setting this system parameter.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 314 InfoSphere Change Data Capture Management Console: Administration Guide . You may need to modify your authorization code when: v Moving from a temporary license to a permanent license v Machine classes have changed v Upgrading to a new version of InfoSphere CDC Applies To—Source and Target Note: You can also modify the authorization using the Authorization Code Setup utility Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Applies To—Target dbUser For information about setting this system parameter. see your IBM representative. Applies To—Source and Target Note: This parameter was specified during InfoSphere CDC installation. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Applies To—Target DSN Use this system parameter to identify ODBC data source name used by InfoSphere CDC to define the metadata database on either the source or target system.

Default Setting—1 Guidelines Encryption or decryption does not affect existing user identifiers and passwords in InfoSphere CDC metadata tables. v 1—Encrypt user identifiers and passwords in metadata tables. Applies To—Source The pwdencrypt system parameters is set to either 0 or 1: v 0—Do not encrypt user identifiers and passwords in metadata tables.NetServiceName For information about setting this system parameter. Applies To—Source and Target Related concepts “System parameters for InfoSphere CDC for AS/400 (version 6.2 and below)” on page 435 TSSrcCP Use this system parameter to identify the code page InfoSphere CDC uses for each instance of a target database. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Applies To—Target pwdencrypt Use this system parameter to encrypt or decrypt user identifiers and passwords stored in InfoSphere CDC metadata tables. Applies To—Target Default Setting—The system code page when InfoSphere CDC was installed.3 and below)” on page 313 System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. see your IBM representative. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “Deadband Percentage” on page 326 Startup Timeout For information about setting this system parameter. Any changes you make to this system parameter apply only to user identifiers and passwords added after setting the system parameter.3 and below) 315 . see your IBM representative.

v To set TCP_KEEPALIVE_SECS: 1. 3. During idle periods. Create a string value called TCP_KEEPALIVE_SECS under the registry key created above. see your IBM representative. set this parameter to a value lower than the configured firewall timeout. Applies To—Source and Target Default Setting—300 seconds (5 min) Minimum Setting—0 Guidelines v To prevent the firewall from closing during active data replication. Note: It is important you set this system parameter when you have a firewall connection that has been configured to timeout. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.“Setting system parameters on source and target datastores” on page 60 TSTgtCP Use this system parameter to identify the source system code page of InfoSphere CDC. Set TCP_KEEPALIVE_SECS to the value that you want. InfoSphere CDC sends a keep alive notification to keep the connection open. Create a registry key called HKEY_LOCAL_MACHINE\SOFTWARE\ DataMirror\InfoSphere CDC\Comms 2. Applies To—Source and Target 316 InfoSphere Change Data Capture Management Console: Administration Guide . Applies To—Source Default Setting—The system code page when InfoSphere CDC was installed. This prevents the firewall from closing the connection.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 TCP_KEEPALIVE_SECS Use this system parameter to determine the time (in seconds) InfoSphere CDC waits before sending a keep alive notification over the network.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 WindowsAuthentication For information about setting this parameter.

No error message is generated in Event Log and replication continues.Replication system parameters Replication system parameters let you control how InfoSphere CDC behaves after detecting errors during replication. v 1—Enables automatic restart of replication operations. v ON—InfoSphere CDC will automatically insert an appropriate default value in the target column. Applies To—Target Set this parameter to one of the following: v OFF—An error message will be generated in Event Log. a warning message may be generated in Event Log. Replication will continue or not based on whether the MirrorError or RefreshError system parameters are set to END or ON. You can also control how often InfoSphere CDC communicates the status of replication activities. Default Setting—0 Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below) 317 .3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “convertNotNullableColumns” convertNotNullableColumns Use this system parameter to indicate whether or not NULL values will be converted to default values when replicating data that contains NULL values to non-nullable target columns. and how InfoSphere CDC should apply a refresh operation. Applies To—Source The AutoRestart system parameters is set to either 0 or 1: v 0—Disables automatic restart of replication operations. System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. See also: “AutoRestart” “convertNotNullableColumns” “MirrorError” on page 318 “RefreshError” on page 318 “RefreshMode” on page 319 AutoRestart Use this system parameter to enable or disable InfoSphere CDC to automatically restart replication after detecting a failover in a clustered environment. Depending on the convertNotNullableMsg system parameter setting.

Default Setting—END Related concepts 318 InfoSphere Change Data Capture Management Console: Administration Guide . Applies To—Target The RefreshError system parameter can be set to either END or GO: v END—InfoSphere CDC ends a refresh operation after it encounters one or more errors. 1901-01-01 for date data types. and so on. v GO—Continues mirroring after InfoSphere CDC encounters an error. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. v GO—InfoSphere CDC continues a refresh operation after it encountering one or more errors.0 and below)” on page 399 Related reference “MirrorError” “RefreshError” “convertNotNullableMsg” on page 329 “D_MIRROR_MIRROR_ERROR_STOP” on page 405 “D_MIRROR_REFRESH_ERROR_STOP” on page 359 MirrorError Use this system parameter to start or stop InfoSphere CDC from continuing mirroring when it encounters one or more errors. Default Setting—END Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. blank character for character data types.The default value depends on the data type of the subscription column. Applies To—Target The MirrorEnd system parameter can be set to either END or GO: v END—Stops mirroring after InfoSphere CDC encounters an error. For example. zero for numeric data types.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 RefreshError Use this system parameter to start or stop InfoSphere CDC from continuing mirroring when it encounters one or more errors.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for Sybase (version 6.

InfoSphere CDC can use BCP (bulk copy refresh) in which a block of rows are sent as a single unit during a refresh operation. Perform a standard refresh. This method is faster than the standard method of refreshing tables used by InfoSphere CDC.“System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.s The RefreshMode system parameter can be set to either BCP or SQL: BCP SQL Perform a bulk copy refresh. You can also control often InfoSphere CDC reports its log position to the target and performs log synchronization between the source and the target.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “RefreshBlock” on page 324 Database translation log system parameters Database transaction log system parameters let you control how InfoSphere CDC cleans the logs of the distribution database. Default Setting BCP Note: Use the RefreshBlock system parameter to set the number of records in a block.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 RefreshMode Applies To Target Use this system parameter to set how InfoSphere CDC applies rows to the target during a refresh operation.3 and below) 319 . System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. See also: “Cleanup Interval” “Cleanup Log Events” on page 320 “Cleanup Record Count” on page 320 “LogCleanupMethod” on page 321 “Report Position Interval” on page 322 “Synchronization Interval” on page 322 Cleanup Interval Use this system parameter to set the time (in seconds) for InfoSphere CDC to clean up the distribution database on the source system.

Depending on the number of log entries you set for deletion and the amount of data being mirrored in your environment. v NO—Does not generate notifications indicating the duration of the cleanup cycle and how many processed log entries have been deleted from the distribution database. InfoSphere CDC can generate regular notifications to indicate how many processed log entries it deleted from the distribution database during a cleanup cycle. v The time between consecutive cleanup cycles is determined by the Cleanup Interval system parameter. Applies To—Source The Cleanup Log Events system parameter is set to either YES or NO: v YES—Generates notifications indicating the duration of the cleanup cycle and how many processed log entries have been deleted from the distribution database. v If you modify the value after setting the system parameter. Default Setting—NO Notes: v InfoSphere CDC places notifications in the Event Log. multiple operations may be required to delete all processed log entries during a cleanup cycle. InfoSphere CDC uses the modified value after completing the next cleanup cycle. If the cleanup cycle completes in a short period of time.Applies To—Source Default Setting—120 seconds Minimum Settings—1 second Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. then InfoSphere CDC only generates notifications that mark the start and end of each cleanup cycle.3 and below)” on page 313 “Displaying event messages during replication” on page 232 “Setting system parameters on source and target datastores” on page 60 Cleanup Record Count Use this system parameter to increase or decrease the number of log entries InfoSphere CDC can delete from the distribution database during a cleanup cycle. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Cleanup Log Events Use this system parameter to enable or disable InfoSphere CDC from generating a notification during a cleanup cycle. Applies To—Source 320 InfoSphere Change Data Capture Management Console: Administration Guide .

3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “Cleanup Log Events” on page 320 LogCleanupMethod Use this system parameter to enable or disable InfoSphere CDC from using IBM stored procedures to clean up transactions in the distribution database. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.Default Setting—8000 log entries Minimum Settings—100 log entries Maximum Settings—100000 log entries Guidelines v You may want to reduce the number of operations applied to the distribution database and set this parameter to a higher number so that InfoSphere CDC can delete a greater number of log entries. To avoid conflicts with other processes that access the distribution database. then InfoSphere CDC uses the defaults. set this parameter to a smaller number of log entries that InfoSphere CDC can delete during a clean up cycle. set this parameter to the approximate number of log entries that InfoSphere CDC can delete in your environment in 1 second. InfoSphere CDC uses the modified value after completing the next cleanup cycle. v The time between consecutive cleanup cycles is determined by the Cleanup Interval system parameter. v 1—Use IBM stored procedures. v If you modify the value after setting the system parameter. Applies To—Source The LogCleanupMethod system parameter is set to either 0 or 1: v 0—Use Microsoft stored procedures.3 and below) 321 . Although this improves the performance of the cleanup cycle. Notes: v If you set a value outside the acceptable range. the Microsoft log reader process and the InfoSphere CDC log scraper process). This can also conflict with other processes that use the distribution database (for example. Default Setting—0 Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. v To ensure a short cleanup cycle.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. a higher number of log entries can increase the amount of time it takes for InfoSphere CDC to complete the cleanup cycle.

Applies To—Source Default Setting—5000 milliseconds (5 seconds) Minimum Settings—1000 milliseconds (1 second) Maximum Settings—300000 milliseconds (5 minutes) Guidelines v If the number of milliseconds is set low. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.Report Position Interval Use this system parameter to set how often (in milliseconds) InfoSphere CDC informs the target system about its log position. then InfoSphere CDC uses the defaults. The target system uses this information to advance its bookmarks. Applies To—Source Default Setting—60 seconds Minimum Settings—1 second Maximum Settings—3000 seconds (50 minutes) Guidelines If you are replicating large volumes of data.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for AS/400 (version 6. v If the number of milliseconds is set high. Notes: v If you set a value outside the acceptable range. the source system informs the target system of its current log position. Synchronization is achieved when the source reports to the target the position of the last committed change. v This system parameter can also prevent InfoSphere CDC from rereading log entries that do not apply to the table currently being replicated. it may affect the accuracy of the information displayed in progress and bookmark notifications. set this system parameter to a lower number of seconds to remove obsolete logs more frequently. 322 InfoSphere Change Data Capture Management Console: Administration Guide . then the target system can provide accurate progress notifications that indicate how far replication has progressed. When the source system is in idle mode and there are no log entries for the subscription.2 and below)” on page 435 Synchronization Interval Use this system parameter to set how often (in seconds) InfoSphere CDC performs log synchronization between the source and the target.

Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. InfoSphere CDC does not maintain transaction consistency during replication.2 and below)” on page 435 Commitment control system parameters Commitment control system parameters let you control how InfoSphere CDC issues commits to the target system. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. v 2—Enables InfoSphere CDC to use commitment control against the target system after applying all rows.Note: If a value outside the acceptable range is specified. If there is a communications or server failure and you have enabled this system parameter. This setting provides true transaction consistency by ensuring that entire transactions are committed to the target database even in the event of a communications or server failure Default Setting—0 Note: You can set the maximum number of rows that InfoSphere CDC can contain a committed transaction using the RefreshBlock system parameter. then InfoSphere CDC rolls back the partially applied transaction to the last commit.3 and below) 323 .3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “RefreshBlock” on page 324 System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for AS/400 (version 6. Applies To—Source The CommitmentControl system parameter is set to either 0 or 2: v 0—Disables commitment control for transaction processing. See also: “CommitmentControl” “Commitment Group Size” on page 324 “RefreshBlock” on page 324 “SeparateCommits” on page 325 CommitmentControl Use this system parameter to enable or disable InfoSphere CDC from using commitment control. Enabling commitment control maintains transaction consistency during replication and ensures that all transactions are applied to the target system. the default setting is used.

if you set this system parameter to apply 10 rows. This reduces the number of commits to the target system. Applies To—Target Default Setting—10000 records Guidelines v If the table you are replicating is relatively large. Depending on how you are refreshing data to the target. Applies To—Target Set the Commitment Group Size system parameter to the number rows you want InfoSphere CDC to apply before issuing a commit. then InfoSphere CDC issues a commit to the target system after applying 10 rows. v This system parameter affects the commit size only if you set the CommitmentControl system parameter to 0 Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. InfoSphere CDC can contain rows for bulk copy refresh or a commit group operations.Commitment Group Size Use this system parameter to set the number of rows InfoSphere CDC applies to the target system before issuing a commit.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “CommitmentControl” on page 323 “SeparateCommits” on page 325 324 InfoSphere Change Data Capture Management Console: Administration Guide . IBM recommends increasing the number of records (refresh block or commit group) to improve performance. v If you are encounter errors during replication. reduce the number of records. Although performance is affected. For example.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “CommitmentControl” on page 323 RefreshBlock Use this system parameter to set the number of rows InfoSphere CDC can contain in a refresh block or a commit group. Default Setting—0 (InfoSphere CDC will not use commit groups) Notes: v This system parameter improves the performance of the InfoSphere CDC apply process because commits to the target system are issued on an interval basis rather than on an transactional basis. lowering the number of records may eliminate these errors during replication. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.

See also: “AllowEventLogClear” AllowEventLogClear For information about setting this system parameter. then this may result in the bookmark not being synchronized with the target system.SeparateCommits Use this system parameter to control how InfoSphere CDC commits bookmarks. For each InfoSphere CDC installation on a server.3 and below) 325 . Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. If you set this parameter to On and InfoSphere CDC encounters an error during the apply process and ends the apply process abnormally. See also: “Unicode Handling” Unicode Handling Use this system parameter to indicate the default method of treating data in defined Unicode columns. Default Setting—Off Guidelines IBM recommends that you set this parameter to On only for performance reasons. v Off—InfoSphere CDC commits the bookmark together with the user data. InfoSphere CDC can commit bookmarks together or separate from the user data. Applies To—Target The SeparateCommits system parameter can set to On or Off: v On—InfoSphere CDC commits the bookmark separate from user data. Applies To—Source Multibyte character set system parameters Multibyte character set system parameters let you control how InfoSphere CDC treats character sets during replication.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Event log system parameters Event log system parameters let you control how InfoSphere CDC interacts with notify message queues. see Transformation Server for Microsoft SQL Server Commands Reference. For more information about bookmarks and how to retrieve bookmark values on the target. see your IBM representative. this system parameter defines the system default method of treating data in Unicode System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.

Applies To—Source Data types Use this system parameter: v nchar v nvarchar This system parameter is set to either CHAR or NOCHANGE: v CHAR—InfoSphere CDC treats all data in Unicode columns as single-byte characters. as defined by this system parameter. Default Setting—NOCHANGE Note: NOCHANGE does not ensure that replicated non-single-byte character data in Unicode columns are represented properly on the target. For more information about user exit programs. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. is used. See also: “Deadband Percentage” “Monitor Sample Interval” on page 329 Deadband Percentage Applies To—Target Identifies the size of the range around each latency threshold setting. see the InfoSphere CDC for Microsoft SQL Server User Exits Guide.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related tasks “To set handling for Unicode character encodings” on page 177 Latency system parameters Latency system parameters let you control how often InfoSphere CDC generates a latency notification and updates latency statistics in the Event Log. Latency is calculated at regular intervals. For replicated non-single-byte character data. the current system default method. Use this setting when Unicode columns contain non-single-byte character data. where 326 InfoSphere Change Data Capture Management Console: Administration Guide . a latency message is generated when latency has risen above or fallen below a threshold. If a Unicode column is set to the system default. NOCHANGE ensures InfoSphere CDC will handle non-single-byte character data in the same way as previous InfoSphere CDC releases. Use this setting when Unicode columns contain single-byte character data. Based on latency thresholds defined. you may need to apply user exit programs or other customization to properly represent the data in Unicode columns.columns. v NOCHANGE—InfoSphere CDC treats all data in Unicode columns as a continuous bit stream.

which is expressed as a percentage. This graph illustrates latency message generation with the DEADBAND_PERCENTAGE value set to 3%: System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. three latency messages are generated. assume that a latency threshold is 5 minutes and this system parameter is set to 10. Therefore.3 and below) 327 . You can set notifications in response to a generated latency message. This system parameter. By adjusting this system parameter. the size of the range around the threshold can be increased or decreased. For example. a latency message is generated each time latency crosses over the latency threshold of 5 minutes. five latency messages are generated when this system parameter is set to 3. This graph illustrates latency message generation with the DEADBAND_PERCENTAGE value set to 10%: If this DEADBAND_PERCENTAGE is set to 3 (the default setting) for the same example. The following calculations are performed to determine the lower and upper limits (in minutes) of the range around the threshold: v Padding = 10% of 5 minutes = 0. a latency message will be generated only when latency rises above 6 minutes or falls below 4 minutes.5 minutes (rounded up to 1 minute) v Padding is rounded up or down to the nearest whole minute: – Upper limit of range = 5 minutes + 1 minute (padding) = 6 minutes – Lower limit of range = 5 minutes . Given sample latency over a ten minute period where latency is calculated every minute. By changing the value assigned to this system parameter. A latency message is generated only when latency has risen above the upper limit of the range or fallen below the lower limit of the range. you can control the number of latency messages placed in Event Log.1 minute (padding) = 4 minutes As a result. A 10% range is applied around the 5 minute threshold. and the threshold itself can be made thicker or thinner. Based on the same sample latency in the previous graph where latency is calculated every minute. no padding is applied to the latency threshold. allows you to pad a threshold equally on both sides to create a range around the threshold.the interval is the current setting for the MONITOR_SAMPLE_INTERVAL system parameter.

Default Setting—3% Minimum Setting—3% Maximum Setting—10% Note: If you set a value outside the acceptable range. then InfoSphere CDC uses the defaults.3 and below)” on page 313 “Setting latency thresholds and notifications” on page 78 “Setting system parameters on source and target datastores” on page 60 Related reference “pwdencrypt” on page 315 328 InfoSphere Change Data Capture Management Console: Administration Guide . If a value outside the acceptable range is specified. an additional 288 latency messages would be generated each day if this system parameter is not changed from its default setting to 10%. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. each range is attached to its threshold. and the two ranges can overlap with no change in behavior. two separate ranges are defined when padding is at least one minute. Since there are two latency thresholds that you can set (a warning threshold and a problem threshold). In this case. the default setting is used.If the number of latency messages generated over the ten minute period for the 10% (3 latency messages) and 3% (5 latency messages) settings are averages.

2 and below)” on page 435 Notification system parameters Notification system parameters let you control if you should generate InfoSphere CDC messages in the Event Log for specific events. v If you set a value outside the acceptable range. then InfoSphere CDC uses the defaults.3 and below) 329 . Set this parameter to one of the following: v OFF—No warning message is generated in Event Log. Maximum Setting—3600 seconds (one hour) Notes: v InfoSphere CDC generates latency notifications when latency rises above or falls below the thresholds and places these in the Event Log. InfoSphere CDC samples the target system to determine if latency has risen above or fallen below the specified threshold settings.Monitor Sample Interval Use this system parameter to set how often (in seconds) InfoSphere CDC updates replication latency metrics. Replication latency metrics are not updated. Otherwise.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for AS/400 (version 6. Related concepts “Setting latency thresholds and notifications” on page 78 “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Applies To—Source and Target Default Setting—5 seconds Minimum Setting—0 seconds. See also: “convertNotNullableMsg” “DM_STATUS_INTERVAL” on page 330 “Heartbeat Timeout” on page 331 “InvalidNumericMsg” on page 331 convertNotNullableMsg Use this system parameter to indicate whether or not a warning message will be generated in Event Log each time data that contains NULL values is converted to default values for non-nullable target columns. this parameter has no effect. Applies To—Target This system parameter applies only when convertNotNullableColumns=ON. System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.

Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. No progress notifications will be issued.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for Sybase (version 6. On the source. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. the default setting is used.v ON—A warning message is generated in Event Log each time a NULL value is converted to a default value. progress notifications identify: v The bookmark sent by the source v The corresponding log name v The subscription name to which the bookmark was sent On the target.0 and below)” on page 399 Related reference “convertNotNullableColumns” on page 317 “DM_STATUS_INTERVAL” “Heartbeat Timeout” on page 331 “InvalidNumericMsg” on page 331 DM_STATUS_INTERVAL Use this system parameter to set how often (in seconds) InfoSphere CDC issues progress notifications about the status of replication activities.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 330 InfoSphere Change Data Capture Management Console: Administration Guide . No progress notifications will be issued. progress notifications identify: v The bookmark received by the target v The corresponding log name v The source ID from which the bookmark was received Applies To—Source and Target Default Setting—0 seconds. Maximum Setting—7200 seconds Notes: v InfoSphere CDC places progress notifications in the Event Log. Minimum Setting—0 seconds. v If a value outside the acceptable range is specified.

Applies To—Source Default Setting—15 minutes Minimum Setting—3 minutes Maximum Setting—999 minutes Notes: v InfoSphere CDC places notifications (message identifiers 3165 and 11010) in the Event Log when a heartbeat timeout occurs. then InfoSphere CDC determines that a problem has occurred and attempts to stop all its source and target processes for each active subscription. v YES—Generate a notification for each invalid numeric field detected by InfoSphere CDC. or NB. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Default Setting—YES Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. notifications are generated for each invalid numeric fields except those that are not initialized. InfoSphere CDC sends internal heartbeat notifications between the source and target systems to verify communications and the status of replication processes for each active subscription. If the source or target do not receive a reply to a notification within the specified timeout interval. v NO—Do not generate a notification for each invalid numeric field detected by InfoSphere CDC.Heartbeat Timeout Use this system parameter to increase or decrease the communication timeout interval (in minutes) before InfoSphere CDC detects a communication problem and attempts to stop active replication processes.3 and below)” on page 313 “Displaying event messages during replication” on page 232 “Setting system parameters on source and target datastores” on page 60 InvalidNumericMsg Use this system parameter to enable or disable InfoSphere CDC from generating a notification each time it detects an invalid numeric field. v If you set a value outside the acceptable range. Applies To—Target The InvalidNumericMsg system parameter can be set to YES. NO.3 and below)” on page 313 System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. then InfoSphere CDC uses the defaults. v NB—Generate a notification for certain types of invalid numeric fields detected by InfoSphere CDC.3 and below) 331 .

Applies To—Target The CommTrace system parameter can be set to either ON or OFF: v ON—Activates a communications module trace. v Activating a trace adversely affects performance. Applies To—Target The ProgramTrace system parameter can be set to either ON or OFF: v ON—Activate an update module trace. 332 InfoSphere Change Data Capture Management Console: Administration Guide . v OFF—Do not activate a communications module trace.“Setting system parameters on source and target datastores” on page 60 Tracing system parameters Tracing system parameters let you perform diagnostic activities with InfoSphere CDC. Default Setting—OFF Notes: v The trace should only be produced if requested by IBM technical support. See also: “CommTrace” “ProgramTrace” “traceActive” on page 333 “TraceLevel” on page 333 “trcCleanup” on page 333 “trcCOMM” on page 333 “trcFiles” on page 334 “trcFncCalls” on page 334 “trcJrlSync” on page 334 “trcReplStatus” on page 334 “trcScan” on page 334 “trcSQL” on page 334 “trcThread” on page 335 CommTrace Use this system parameter to turn tracing of the communications module on or off. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 ProgramTrace Use this system parameter to activate or deactivate InfoSphere CDC from tracing the update module.

2. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. Applies To—Source TraceLevel Use this system parameter to set the level of detail produced by a program trace.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 traceActive For information about setting this system parameter. see your IBM representative. or 3: v 1—Produces a trace with the highest level of detail. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. v 2—Produces a trace with a medium level of detail. see your IBM representative. Default Setting—OFF Notes: v The trace is encrypted and should only be produced if requested by IBM technical support. v 3—Produces a trace with the lowest level of detail. Applies To—Target The TraceLevel system parameter can be set to either 1.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 trcCleanup For information about setting this system parameter. Applies To—Source System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. v Activating a trace adversely affects performance. Default Setting—3 Note: Contact IBM technical support for the suggested level of detail. Applies To—Source trcCOMM For information about setting this system parameter. see your IBM representative.v OFF—Do not activate an update module trace.3 and below) 333 .

Applies To—Source trcScan For information about setting this system parameter. Applies To—Source trcJrlSync For information about setting this system parameter. see your IBM representative. Applies To—Source trcReplStatus For information about setting this system parameter. Applies To—Source and Target Default Setting—InfoSphere CDC installation folder. see your IBM representative. Applies To—Source 334 InfoSphere Change Data Capture Management Console: Administration Guide . Guidelines You must specify the full path of the folder where you want to place the trace file. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.trcFiles Use this system parameter to identify the location of the file that contains information produced by an update or communications module trace. Applies To—Source trcSQL For information about setting this system parameter.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “CommTrace” on page 332 “ProgramTrace” on page 332 trcFncCalls For information about setting this system parameter. see your IBM representative. Note: You can enable tracing using the ProgramTrace and CommTrace system parameters. see your IBM representative. see your IBM representative.

Applies To—Target Default Setting—3 attempts Related concepts “Displaying event messages during replication” on page 232 “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 DM_LOCK_DETECTION Use this system parameter to turn lock detection on or off. update. see your IBM representative. or delete) to the target table after detecting a deadlock. See also: “TrimVarchar” TrimVarchar For information about setting this system parameter. Applies To—Source Data type system parameters Data type system parameters let you control how InfoSphere CDC handles certain data types. See also: “DeadlockRetrys” “DM_LOCK_DETECTION” “DM_LOCK_TIMEOUT” on page 336 DeadlockRetrys Use this system parameter to identify the number of attempts InfoSphere CDC applies a table or row-level operation (clear table.3 and below) 335 . InfoSphere CDC cancels the operation and generates an error notification in Event Log. If the operation cannot be applied after the specified number of attempts has been made. If InfoSphere CDC attempts to modify a table or row that has been locked by another process. Applies To—Target Lock detection system parameters Lock detection system parameters let you control how InfoSphere CDC applies data when it detects a locked table or row. see your IBM representative. insert. then System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.trcThread For information about setting this system parameter.

Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 Related reference “DM_LOCK_TIMEOUT” DM_LOCK_TIMEOUT Use this system parameter to set the amount of time (in seconds) that InfoSphere CDC waits before attempting to modify a locked user or metadata table. These notifications identify the specific table and row that InfoSphere CDC could not modify.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 336 InfoSphere Change Data Capture Management Console: Administration Guide . When InfoSphere CDC attempts to modify a locked table. InfoSphere CDC waits until the locked row becomes available. v Table locking notification is supported for tables containing user data and replication metadata tables.turning lock detection ON enables InfoSphere CDC to wait for a specific amount of time before attempting to apply the data again. Default Setting—ON Note: You can specify the time to wait using the DM_LOCK_TIMEOUT system parameter. Applies To—Source and Target The DM_LOCK_DETECTION system can be set to either ON or OFF: v ON—Enables table and row lock detection. Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. it places a notification in the Event Log. Applies To—Target Default Setting—30 seconds Minimum Setting—1 second Maximum Setting—60 seconds Notes: v If you set a value outside the acceptable range. v OFF—Disables table and row lock detection. then InfoSphere CDC uses the defaults.

in minutes. of communication inactivity before active InfoSphere CDC processes for a subscription are stopped. you will learn: “Notification system parameters” “Maximize throughput system parameters” on page 338 “Encoding system parameters” on page 341 “Supplemental logging system parameters” on page 342 “Disk resource system parameters” on page 343 “Apply process system parameters” on page 344 “Authentication system parameters” on page 345 Notification system parameters Notification system parameters let you control if you should generate InfoSphere CDC messages in the Event Log for specific events. any pre-existing settings for system parameters are maintained. InfoSphere CDC provides system parameters that control the behavior of your source and/or target datastores.System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. Applies To—Source Default Setting—15 minutes Minimum Setting—3 minutes © Copyright IBM Corp. the default setting is used. If your replication environment requires a particular configuration. 2008 337 . then you can use system parameters to modify the behavior of default operations in InfoSphere CDC. Notes: v If you make changes to a system parameter during active replication. Maintain these default settings until you become familiar with the configuration of InfoSphere CDC. In this section. you must stop and restart InfoSphere CDC for the changes to take effect. If a value outside the acceptable range is specified. See also: “global_shutdown_after_no_heartbeat_response_minutes” “global_conversion_not_possible_warning” on page 338 global_shutdown_after_no_heartbeat_response_minutes Use this system parameter to specify the duration.0 and above) System parameters let you control the behavior of InfoSphere CDC. The default system parameter settings are appropriate for most installations. v When upgrading to a higher version of InfoSphere CDC.

Set this parameter to one of the following: true—generates a warning in the Event Log if data conversion is not possible for a specific data value or converted data types are encountered that are out of range. Applies To—Target Default Setting—False Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. Every commit on the target database will correspond with a commit on the target. However. See also: “mirror_commit_after_max_transactions” on page 339 “mirror_commit_after_max_seconds” on page 339 “mirror_commit_after_max_operations” on page 339 “mirror_commit_on_transaction_boundary” on page 340 “refresh_commit_after_max_operations” on page 340 338 InfoSphere Change Data Capture Management Console: Administration Guide . but if your target system has limited resources and an increase in latency is acceptable. The InfoSphere CDC apply process groups transactions on the target to reduce the workload. if the source does three small transactions containing one operation each. it may not perform every commit that was done on the source.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 Maximize throughput system parameters InfoSphere CDC system parameters allow you to significantly reduce the workload of the target database during mirroring. The default settings are appropriate for most databases. v Converted data types are encountered that are out of range. You can use this grouping of system parameters to significantly reduce the resources required by the target database. you can adjust the settings appropriately.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 global_conversion_not_possible_warning Use this system parameter to control whether or not InfoSphere CDC generates a warning in the Management Console Event Log in the following situations: v Data conversion is not possible for a specific data value.Maximum Setting—999 minutes Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. false—does not generate a warning in the Event Log if data conversion is not possible for a specific data value or converted data types are encountered that are out of range. the target may commit all three operations as part of a single transaction. For example.

but not all source commits will be issued on the target. When data volume is higher. When data volume is higher.0 and above) 339 . has elapsed since the last target commit it issued. Commits are issued to the target database in response to commits issued by applications running on the source. The frequency at which source commits are issued to the target database will vary depending on the volume of changes. then there will be a target commit issued for this source commit. then it will issue a target commit either immediately (if it isn’t currently in the middle of a source transaction) or as soon as it receives the next source commit. This system parameter is used to place a limit on how infrequent these target commits can become. in seconds. If the specified amount of time.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 mirror_commit_after_max_operations This system parameter specifies a threshold used to determine when to issue a commit to the target database.mirror_commit_after_max_transactions This system parameter specifies a threshold used to determine when to issue a commit to the target database. less frequent commits on the target will allow for the higher data throughput required to maintain low latency. Applies To—Target Default Setting—1 second Minimum Setting—1 Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. Commits are issued to the target database in response to commits issued by applications running on the source. The frequency at which source commits are issued to the target database will vary depending on the volume of changes. Commits are issued to the target database in System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. less frequent commits on the target will allow for the higher data throughput required to maintain low latency. Applies To—Target Default Setting—10 Minimum Setting—1 Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. This system parameter is used to place a limit on how infrequent these target commits can become. but not all source commits will be issued on the target. If the source commit being processed has reached this threshold of source commits received since the last target commit was issued.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 mirror_commit_after_max_seconds This system parameter specifies a threshold used to determine when to issue a commit to the target database.

If you choose to ignore the commitment control of the source database. No attempt to maintain transaction consistency is performed during mirroring. The frequency at which source commits are issued to the target database will vary depending on the volume of changes. Applies To—Target Default Setting—1000 Minimum Setting—1 Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. This setting provides true transaction consistency by ensuring that only committed transactions are sent to the target. InfoSphere CDC allows you to see the partial results of large transactions. Applies To—Target 340 InfoSphere Change Data Capture Management Console: Administration Guide . less frequent commits on the target will allow for the higher data throughput required to maintain low latency.response to commits issued by applications running on the source. InfoSphere CDC periodically commits the changes to the target database rather than performing the refresh as a single large transaction. Applies To—Target Default Setting—true Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. To reduce the workload on the target database during refresh.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 refresh_commit_after_max_operations This system parameter identifies the number of rows comprising each transaction during refresh. but not all source commits will be issued on the target. This system parameter is used to place a limit on how infrequent these target commits can become. This value disables commitment control for transaction processing. then it will issue a target commit at the next source commit it receives from the source. Only records in a committed transaction are mirrored to the target. v false—Ignores the commitment control of the source database. If the target has applied this number of operations since the last target commit was issued.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 mirror_commit_on_transaction_boundary This system parameter indicates whether or not the commits that InfoSphere CDC does on the target database will always correspond with a commit that occurred on the source database. When data volume is higher. Set this parameter to one of the following: v true—Does not ignore the commitment control of the source database.

see the InfoSphere CDC End-User Documentation for your platform. Setting this system parameter to false ensures that InfoSphere CDC handles non-single-byte character data in the same way as previous InfoSphere CDC releases. Applies To—Source Default Setting—false Note: The following SQL Server data types are considered to be Unicode columns and are therefore affected by the value assigned to this system parameter: v nchar v nvarchar Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. is used. you can set the default method for treating data in defined Unicode columns.0 and above) 341 . v false—InfoSphere CDC treats all data in Unicode columns as a continuous bit stream. you may have to apply user exit programs or other customization to properly represent data in Unicode columns. Use this setting when Unicode columns contain non-single-byte character data.Default Setting—1000 Minimum Setting—1 Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. See also: “global_unicode_as_char” global_unicode_as_char This system parameter indicates the default method of treating data in defined Unicode columns. For replicated non-single-byte character data. and you can set the default character encoding for your database. Set this parameter to one of the following: v true—InfoSphere CDC treats all data in Unicode columns as single-byte characters.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 Encoding system parameters For some system parameters. Use this setting when Unicode columns contain single-byte character data. this system parameter defines the system default method of treating data in Unicode columns. For more information about user exit programs. For each InfoSphere CDC installation on a server. as defined by this system parameter.0 and above)” on page 337 System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. Note: Setting this parameter to false does not ensure that replicated non-single-byte character data in Unicode columns are represented properly on the target. the current system default method. If a Unicode column is set to the system default.

If you choose false and are using Microsoft SQL Server 2000.3 and above)” on page 425 Supplemental logging system parameters Some system parameter control the database logging mechanism used by InfoSphere CDC.“Setting system parameters on source and target datastores” on page 60 “Setting multibyte conversions—common scenarios” on page 175 “System parameters for InfoSphere CDC for Sybase (version 6. @optname = ’publish’. Note that you can use the following query to check if your database is enabled for Microsoft Replication: exec sp_helpreplicationdboption Applies To—Source Default Setting—true Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. v false—The Distribution Database is used as your supplemental logging method. 2. Set up Microsoft Replication and verify that the Distribution database exists. Set this parameter to one of the following: v true—Empty triggers are used as your supplemental logging method for Microsoft SQL Server 2000. @value = ’true’ Where your_db_name is your database name. Add the database to Microsoft Replication using the following query: EXEC sp_replicationdboption @dbname = ’your_db_name’.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 342 InfoSphere Change Data Capture Management Console: Administration Guide . you must add your database to replication/publication with the following steps: 1. See also: “mirror_logging_by_empty_triggers” “auto_configure_supplemental_logging” on page 433 “mirror_logging_by_empty_triggers” on page 434 mirror_logging_by_empty_triggers This system parameter allows you to choose empty triggers as your supplemental logging method for Microsoft SQL Server 2000. This method of supplemental logging is available for Microsoft SQL Server 2000 and Microsoft SQL Server 2005.

this system parameter should be large enough to hold the data for the largest transactions that occur on the source.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 global_memory_lob_cache_mb This system parameter controls the amount of memory that will be used to stage LOB values on the target.0 and above) 343 . For optimal performance. if you are able to allocate more than the default value of 512 MB for the InfoSphere CDC Java Virtual Machine. For optimal performance. For optimal performance. then you can adjust the disk resource system parameters to use the increased memory. Default Setting—2 Megabytes Applies To—Target Related concepts System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 mirror_memory_txqueue_each_mb This system parameter controls the amount of memory used to stage data on the source. Applies To—Source Default Setting—15 Megabytes Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. Applies To—Source Default Setting—3 Megabytes Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. this system parameter should be large enough to hold the largest amount of uncommited data that will ever exist in the source database.Disk resource system parameters Some system parameters control memory usage in InfoSphere CDC. See also: “mirror_memory_txqueue_total_mb” “mirror_memory_txqueue_each_mb” “global_memory_lob_cache_mb” “mirror_queue_for_buffers_between_cdc_threads_operations” on page 344 mirror_memory_txqueue_total_mb This system parameter controls the amount of memory used to stage data on the source. For improved performance. this value should be large enough to hold the entire data for the largest LOB values that will be replicated.

See also: “mirror_end_on_error” “refresh_end_on_error” mirror_end_on_error Use this system parameter to indicate if you want to end mirroring after an apply error occurs on the target database.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 Apply process system parameters Some system parameters adjust the way InfoSphere CDC applies rows. Set this parameter to one of the following: 344 InfoSphere Change Data Capture Management Console: Administration Guide .0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 mirror_queue_for_buffers_between_cdc_threads_operations This system parameter controls the ability of InfoSphere CDC’s log scraping to take advantage of multiple processors.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 refresh_end_on_error Use this system parameter to indicate if you want to end a refresh after an apply error occurs.“System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. Set this parameter to one of the following: v true—End mirroring after an apply error on the target database. column data. The default setting is acceptable for most situations. Applies To—Source Default Setting—100 entries Minimum Setting—100 entries Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. You can increase this value for highly scalable environments. and error handling. Applies To—Target Default Setting—true Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. v false—Do not end mirroring after an apply error on the target database.

see your InfoSphere CDC for Microsoft SQL Server documentation.0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 Authentication system parameters Some system parameters control authentication in InfoSphere CDC. The password is not verified.v v true—End a refresh after an apply error occurs. Set this parameter to one of the following: Note: IBM recommends that you set these values with the dmset command. v windows_authentication—Indicates that InfoSphere CDC uses Windows authentication. With this type of authentication. see “To add a new datastore” on page 24. Default Setting—None System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. With this type of authentication. you must specify a SQL Server user/password combination when you create a datastore in the Access Manager perspective in Management Console. Applies To—Target Default Setting—true Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6. For more information on configuring InfoSphere CDC. v db_authentication—Indicates that InfoSphere CDC uses SQL Server authentication. The Windows user must have a SELECT permission on the TS_AUTH metadata table. With this type of authentication.0 and above) 345 . See also: “global_ts_user_authentication_method” global_ts_user_authentication_method This system parameter allows you to specify the authentication method that InfoSphere CDC will use to authenticate the user/password combination specified in in the Access Manager perspective in Management Console. false—Do not end a refresh after an apply error occurs. you must specify a SQL Server user when you create a datastore in the Access Manager perspective in Management Console . By default. see your InfoSphere CDC for Microsoft SQL Server documentation. For more information on how to create a datastore in the Access Manager perspective. v validation—Indicates that InfoSphere CDC verifies that a SQL Server user exists. you must specify a Windows user/password combination that has access to your SQL Server database when you create a datastore in the Access Manager perspective in Management Console. The Windows user must have a ″SELECT″ permission on TS_AUTH metadata table. this system parameter is set to the authentication method that you specify when configuring InfoSphere CDC. For more information.

0 and above)” on page 337 “Setting system parameters on source and target datastores” on page 60 Related tasks “To add a new datastore” on page 24 346 InfoSphere Change Data Capture Management Console: Administration Guide .Related concepts “System Parameters for InfoSphere CDC for Microsoft SQL Server (version 6.

Note: If you make changes to a system parameter during active replication. then you can use system parameters to modify the behavior of default operations in InfoSphere CDC. 2008 347 . The default system parameter settings are appropriate for most installations.2 and below) System parameters let you control the behavior of InfoSphere CDC. you must stop and restart replication for the changes to take effect. InfoSphere CDC provides system parameters that control the behavior of your source and/or target datastores. you will learn: “General product system parameters” “Apply process system parameters” on page 357 “Cascading replication system parameters” on page 365 “Database journal (trigger) system parameters” on page 366 “Maximize throughput system parameters” on page 367 “Tracing system parameters” on page 372 “Refresh loader system parameters” on page 375 “User exit system parameters” on page 379 “Table mapping system parameters” on page 380 “Notification system parameters” on page 381 “Disk resource system parameters” on page 386 General product system parameters General product system parameters let you control basic features of InfoSphere CDC and information you may have specified during installation. If your replication environment requires a particular configuration. Maintain these default settings until you become familiar with the configuration of InfoSphere CDC.System parameters for InfoSphere CDC for Oracle (version 6. See also: “CODE_PAGE” on page 348 “DEFAULT_ORACLE_HOME” on page 348 “DEFAULT_ORACLE_SID” on page 348 “DEFAULT_ORACLE_USER” on page 349 “DM_COMMS_HOME” on page 349 “D_MIRROR_HOME” on page 349 “D_MIRROR_LOG” on page 349 “DM_DYNAMIC_PARAMETER_CHECK_INT” on page 350 “DM_MAX_MONITOR_ENTRIES” on page 350 “DM_TS_MAX_POOL_SIZE_MB” on page 350 “DM_TS_POOL_BLOCK_SIZE_MB” on page 351 “<subscription>_MAX_POOL_SIZE_MB” on page 351 © Copyright IBM Corp. In this section.

Applies To—Source Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Source and Target Default Setting—The system code page when InfoSphere CDC was installed.2 and below)” on page 347 DEFAULT_ORACLE_SID Use this system parameter to specify the Oracle SID for the Oracle database instance that is started by default. Applies To—Source Default Setting—The Oracle SID specified when InfoSphere CDC was installed. Related concepts 348 InfoSphere Change Data Capture Management Console: Administration Guide . Modify this parameter only if you installed InfoSphere CDC in multiple database instances. This value is set during installation and should not be modified except under the guidance of a IBM technical support. Modify this parameter only if you installed InfoSphere CDC in multiple database instances.“<subscription>_POOL_BLOCK_SIZE_MB” on page 352 “LD_LIBRARY_PATH” on page 353 “LIBPATH” on page 353 “ORACLE_HOME” on page 353 “ORACLE_SID” on page 353 “PASSWORD” on page 354 “PUBLISH_METADATA” on page 354 “RLD_SYSTEM_TXQSIZE” on page 354 “<subscription>_TXQSIZE” on page 355 “SHLIB_PATH” on page 355 “STARTUP_TIMEOUT” on page 355 “TCP_KEEPALIVE_SECS” on page 356 “USER” on page 356 CODE_PAGE Use this system parameter to specify the code page associated with NLS_LANG. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “NLS_LANG” on page 362 DEFAULT_ORACLE_HOME Use this parameter to specify the installation directory for the Oracle database instance that is started by default.

2 and below)” on page 347 D_MIRROR_LOG Use this system parameter to specify the directory (full path) where InfoSphere CDC log files are located. Applies To—Source Default Setting—The Oracle user specified when InfoSphere CDC was installed.2 and below)” on page 347 DM_COMMS_HOME For information about setting this system parameter. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. see your IBM representative. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Source and Target Default Setting—The log subdirectory in the installation directory specified when InfoSphere CDC was installed.2 and below)” on page 347 DEFAULT_ORACLE_USER Use this system parameter to specify the name of the user for the Oracle database instance that is started by default. This little command copies things.“System parameters for InfoSphere CDC for Oracle (version 6. D_MIRROR_HOME Use this system parameter to specify the directory (full path) where InfoSphere CDC is installed on the server. Applies To—Source and Target Default Setting—The installation directory specified when InfoSphere CDC was installed.2 and below) 349 . Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Modify this parameter only if you installed InfoSphere CDC in multiple database instances.

in seconds.2 and below)” on page 347 DM_MAX_MONITOR_ENTRIES Use this system parameter to increase or decrease the number of subscriptions that InfoSphere CDC can support in the Monitor in Management Console.483. you should specify the number of blocks you want InfoSphere CDC to create using the DM_TS_POOL_BLOCK_SIZE_MB system parameter.648 (maximum integer) Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. By default. InfoSphere CDC can handle 20 subscriptions. InfoSphere CDC allocates an entry for each source and target datastore within a subscription. Applies To—Source Default Setting—20 entries.DM_DYNAMIC_PARAMETER_CHECK_INT Use this system parameter to specify how often. After specifying the size of the staging store. Minimum Setting—1 entry Maximum Setting—1000 entries DM_TS_MAX_POOL_SIZE_MB Use this system parameter when you need to resize the staging store component of InfoSphere CDC. InfoSphere CDC does not check for changes to dynamic system parameters. For example. InfoSphere CDC checks for changes to the values of dynamic system parameters during active replication to a subscription. Applies To—Source and Target The following system parameters are dynamic: v “D_MIRROR_TRACE” on page 414 v “D_MIRROR_TRACE_ON_ERROR” on page 414 (on the target only) v “DM_PRINT_DIAGNOSTICS” on page 374 v “STATISTICS_INTERVAL” on page 420 v “SYNCHRONIZATION_COMMIT_ GROUP_SIZE” on page 412 v “SYNCHRONIZATION_INTERVAL” on page 413 Default Setting—300 seconds (5 minutes) Minimum Setting—0. 350 InfoSphere Change Data Capture Management Console: Administration Guide .147. InfoSphere CDC will allocate 30 entries for this datastore. For example. set this parameter to 216. You can specify a value in megabytes (MB). Maximum Setting—2. if you have a datastore that is being used as a source datastore within 20 subscriptions and as a target datastore within 10 subscriptions. to check once a day. then you must set this system parameter to at least 30.000.

For example. In this scenario. If you do not specify a block size for this system parameter. see the ″setjrnpos—set Jjournal position in the commands″ section of the InfoSphere CDC for Oracle End-User Documentation. If the size of the active staging store is not large enough to accommodate all data. you must set the journal position to the last applied position by running the setjrnpos command. Default Setting—25% of the default setting for the RLD_SYSTEM_TXQSIZE system parameter which is 128 MB.Applies To—Source This setting must be large enough to store data for the largest predicted transaction that occurs in the Oracle database. Note: After changing the value of this parameter. After specifying the size System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC issues an error message (Message ID 307) in the event log and shuts down. Related reference “DM_TS_MAX_POOL_SIZE_MB” on page 350 <subscription>_MAX_POOL_SIZE_MB Use this system parameter when you want to resize the staging store for a specific subscription. then InfoSphere CDC will create a maximum of 4 blocks (no larger than 20 MB each) of space for the staging store. InfoSphere CDC will create a maximum 5 blocks of 20 MB each. To set the journal position. Applies To—Source Default Setting—None. The size you had specified with the DM_TS_MAX_POOL_SIZE_MB system parameter is adjusted based on the block size you specify. see ″Running the Bookmark Viewer Command and Setting the Journal Position on the Source″ in the ″Installing InfoSphere CDC″ section of the InfoSphere CDC for Oracle End-User Documentation.2 and below) 351 . For more information about the setjrnpos command. You can specify a value in megabytes (MB). Related reference “DM_TS_POOL_BLOCK_SIZE_MB” “RLD_SYSTEM_TXQSIZE” on page 354 DM_TS_POOL_BLOCK_SIZE_MB Use this system parameter when you are in the process of resizing the staging store component of InfoSphere CDC and need to specify a block size you want InfoSphere CDC to create for the staging store. The staging store size should be at least 150% of the largest predicted transaction. The value you specify for DM_TS_POOL_BLOCK_SIZE_MB indicates the block size you want InfoSphere CDC to create for the staging store. You must have already specified the size of the staging store (in MB) using the DM_TS_MAX_POOL_SIZE_MB system parameter. you may have specified 100 MB for the staging store using the DM_TS_MAX_POOL_SIZE_MB system parameter.

InfoSphere CDC issues an error message (Message ID 307) in the event log and shuts down. InfoSphere CDC will create a maximum 5 blocks of 20 MB each. then InfoSphere CDC will create a maximum of 4 blocks (no larger than 20 MB each) of space for the staging store. The value you specify for <subscription>_TS_POOL_BLOCK_SIZE_MB indicates the block size you want InfoSphere CDC to create for the staging store. If you do not specify a block size for this system parameter. see ″Running the Bookmark Viewer Command and Setting the Journal Position on the Source″ in the ″Installing InfoSphere CDC″ section of the InfoSphere CDC for Oracle End-User Documentation. you may have specified 100 MB for the staging store using the <subscription>_TS_MAX_POOL_SIZE_MB system parameter. If the size of the active staging store is not large enough to accommodate all data. The size you had specified with the <subscription>_TS_MAX_POOL_SIZE_MB system parameter is adjusted based on the block size you specify. For example. To set the journal position. For more information about the setjrnpos command.of the staging store. Applies To—Source Default Setting—None. Applies To--Source Default Setting--25% of the default setting for the RLD_SYSTEM_TXQSIZE system parameter which is 128 MB. you must set the journal position to the last applied position by running the setjrnpos command. This setting must be large enough to store data for the largest predicted transaction that occurs in the Oracle database. In this scenario. Related reference “<subscription>_MAX_POOL_SIZE_MB” on page 351 352 InfoSphere Change Data Capture Management Console: Administration Guide . Related reference “RLD_SYSTEM_TXQSIZE” on page 354 “<subscription>_POOL_BLOCK_SIZE_MB” <subscription>_POOL_BLOCK_SIZE_MB Use this system parameter when you are in the process of resizing the staging store component for a specific subscription and need to specify a block size you want InfoSphere CDC to create for the staging store. You must have already specified the size of the staging store (in MB) using the <subscription>_TS_MAX_POOL_SIZE_MB system parameter. The staging store size should be at least 150% of the largest predicted transaction. Note: After changing the value of this parameter. see the ″setjrnpos—set Jjournal position in the commands″ section of the InfoSphere CDC for Oracle End-User Documentation. you should specify the block size you want InfoSphere CDC to create using the <subscription>_POOL_BLOCK_SIZE_MB system parameter.

2 and below)” on page 347 System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Source Default Setting—The Oracle SID specified when InfoSphere CDC was installed. This value is set during installation and should not be modified.2 and below) 353 . Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Source and Target Default Setting—The path to the InfoSphere CDC libraries and the database libraries when InfoSphere CDC was installed.2 and below)” on page 347 ORACLE_HOME Use this system parameter to specify the Oracle home directory. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 LIBPATH Use this system parameter to specify the path to the InfoSphere CDC libraries and the database libraries (for AIX® operating systems). Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.LD_LIBRARY_PATH Use this system parameter to specify the path to the InfoSphere CDC libraries and the database libraries for Solaris and Linux operating systems. This value is set during installation and should not be modified. Applies To—Source Default Setting—The Oracle home directory specified when InfoSphere CDC was installed.2 and below)” on page 347 ORACLE_SID Use this system parameter to specify the Oracle SID. Applies To—Source and Target Default Setting—The path to the InfoSphere CDC libraries and the Oracle libraries when InfoSphere CDC was installed Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.

InfoSphere CDC issues an error message and shuts down.2 and below)” on page 347 354 InfoSphere Change Data Capture Management Console: Administration Guide . For information about dmsetpass. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 RLD_SYSTEM_TXQSIZE Use this system parameter to specify the size.2 and below)” on page 347 PUBLISH_METADATA Use this system parameter to enable or disable the display of InfoSphere CDC metadata tables in Management Console. The active transaction queue store contains data for concurrent transactions that have been extracted from the Oracle redo log. Applies To—Source This setting must be large enough to store data for all concurrent transactions that occur in the Oracle database. If the size of the active transaction queue store is not large enough to accommodate all data. for the active transaction queue store maintained by InfoSphere CDC. making them available to be selected for replication. Applies To—Source This parameter was set during installation and should not be modified. in megabytes (MB). which can be set using the dmsetpass command. Default Setting—128 MB Minimum Setting—5 MB Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. v ON—InfoSphere CDC metadata tables are displayed in the Add/Remove Tables dialog box.PASSWORD Use this system parameter to identify the encrypted database password. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Source Set this parameter to one of the following: v OFF—InfoSphere CDC metadata tables are not displayed in Management Console. see dmsetpass—Set Password in the Commands section of the InfoSphere CDC for Oracle documentation.

Applies To—Source and Target Default Setting—The path to the InfoSphere CDC libraries and the database libraries when InfoSphere CDC was installed. in seconds.2 and below) 355 . v The name of the system parameter is not case-sensitive. System parameters for InfoSphere CDC for Oracle (version 6. then use the RLD_SYSTEM_TXQSIZE to allocate queue storage size. Applies To—Source Default Setting—There is no default value for this system parameter.<subscription>_TXQSIZE Use this system parameter to specify the size. If you have added two subscriptions in Management Console named SUB1 and sub1.2 and below)” on page 347 Related reference “RLD_SYSTEM_TXQSIZE” on page 354 SHLIB_PATH Use this system parameter to specify the path to the InfoSphere CDC libraries and the database libraries for HP-UX operating systems. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Notes: v The subscription name precedes the name of the system parameter (TXQSIZE). in megabytes (MB). extracted from the Oracle redo log.2 and below)” on page 347 STARTUP_TIMEOUT Use this system parameter to specify the maximum waiting period. you want to allocate per subscription for the active transaction queue store. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. v This system parameter applies only to the Redo Log edition of InfoSphere CDC for Oracle. This value is set during installation and should not be modified. sub1TXQSIZE. If you want all other subscriptions to use the same storage size. for process handling to complete during InfoSphere CDC startup. For example. then both subscriptions will use the same value specified for the system parameter. It indicates how long the communication program waits for the database setup program to start before timing out. This area represents the amount of space required to store data for a single transaction. This system parameter is useful when you want to allocate a specific amount of queue storage for a specific subscription you have added in InfoSphere CDC Management Console. If you decide not to specify a value in megabytes for this system parameter. then InfoSphere CDC will use the value you specified for the RLD_SYSTEM_TXQSIZE system parameter.

Insert the following line in the file: TCP_KEEPALIVE_SECS = <value>. see the ″dmsetpass—Set Password in the Commands″ section of the InfoSphere CDC for Oracle documentation. InfoSphere CDC sends a keep alive message to keep the connection open. Create a file named dmcommparms. where value is the setting for this system parameter. 356 InfoSphere Change Data Capture Management Console: Administration Guide . You can also set this user using the dmsetpass command.cfg in the <InfoSphere CDC install dir>/lib directory.2 and below)” on page 347 USER Use this system parameter to specify the Oracle user name that was specified during installation. Default Setting—300 seconds (5 min) Minimum Setting—0 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. 2. To set this system parameter. Set this parameter to a value lower than the firewall timeout. so that the firewall does not close the connection during data replication. to wait before sending a keep alive message over the network. enter: TCP_KEEPALIVE_SECS = 60.2 and below)” on page 347 TCP_KEEPALIVE_SECS Use this parameter to specify the time interval. For example.Applies To—Source and Target Default Setting—120 Minimum Setting—60 Maximum Setting—3600 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. For information about dmsetpass. to set to 1 minute. do the following: 1. Applies To—Source Default Setting—The InfoSphere CDC user specified when InfoSphere CDC was installed. to prevent them from closing the connection. If a connection is idle for the specified time interval. Applies To—Source and Target Setting this system parameter is needed in environments that have firewalls with timeout connection values. during idle periods.

Apply process system parameters In this section, you will learn about system parameters that adjust how InfoSphere CDC applies rows, column data, and errors to the target. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

Apply process system parameters
Some system parameters adjust the way InfoSphere CDC applies rows, column data, and error handling. See also: “convertNotNullableColumns” “D_MIRROR_MIRROR_ERROR_LIST” on page 358 “D_MIRROR_MIRROR_ERROR_STOP” on page 358 “D_MIRROR_REFRESH_ERROR_LIST” on page 359 “D_MIRROR_REFRESH_ERROR_STOP” on page 359 “DM_ADAPTIVE_APPLY_SOFT_DELETES” on page 359 “DM_ADAPTIVE_APPLY_<SCHEMA>.<TABLENAME>” on page 360 “DM_ADAPTIVE_APPLY_MIMIC_SOURCE_OPERATION” on page 360 “DM_ARRAY_BIND_MAX” on page 361 “FILTER_NOCHANGE_UPDATES_FOR_AUDIT” on page 361 “NLS_LANG” on page 362 “NLS_NCHAR” on page 362 “NOT_NULL_DATE_DEFAULT” on page 362 “TRIM_CHAR_TO_VARCHAR” on page 362 “TRIM_VARCHAR_TO_VARCHAR” on page 363 “TRIM_TO_NULL” on page 363 “UNICODE_HANDLING” on page 364

convertNotNullableColumns
Use this system parameter to indicate whether or not NULL values will be converted to default values when replicating data that contains NULL values to non-nullable target columns. Applies To—Target Set this parameter to one of the following: v OFF—An error message will be generated in Event Log. Replication will continue or not based on whether the MirrorError or RefreshError system parameters are set to END or ON. v ON—InfoSphere CDC will automatically insert an appropriate default value in the target column. No error message is generated in Event Log and replication continues. Depending on the convertNotNullableMsg system parameter setting, a warning message may be generated in Event Log.

System parameters for InfoSphere CDC for Oracle (version 6.2 and below)

357

The default value depends on the data type of the subscription column. For example, zero for numeric data types, blank character for character data types, 1901-01-01 for date data types, and so on. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “D_MIRROR_MIRROR_ERROR_STOP” “D_MIRROR_REFRESH_ERROR_STOP” on page 359 “convertNotNullableMsg” on page 381

D_MIRROR_MIRROR_ERROR_LIST
Use this system parameter to allow certain errors to be ignored during mirroring. Applies To—Target If the “D_MIRROR_MIRROR_ERROR_STOP” on page 405 system parameter is set to ON, use this parameter to allow certain errors to be ignored during mirroring. The value assigned to this parameter is a comma-delimited list of Oracle or Sybase database error numbers. For example, to ignore primary key violations, but to stop mirroring on any other update errors, set D_MIRROR_MIRROR_ERROR_LIST=1. This value corresponds to the Oracle error ″ORA-00001: unique constraint violated (<schema>.<constraint>)″. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “D_MIRROR_MIRROR_ERROR_STOP”

D_MIRROR_MIRROR_ERROR_STOP
Use this parameter to indicate whether or not mirroring continues after an error has occurred during a row insert, delete, or update operation. Applies To—Target Set this parameter to one of the following: v ON—Mirroring stops after an error has occurred. v OFF—Mirroring continues after an error has occurred. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “D_MIRROR_MIRROR_ERROR_LIST”

358

InfoSphere Change Data Capture Management Console: Administration Guide

D_MIRROR_REFRESH_ERROR_LIST
Use this system parameter to allow certain errors to be ignored during data refresh. Applies To—Target If the “D_MIRROR_REFRESH_ERROR_STOP” system parameter is set to ON, use this parameter to allow certain errors to be ignored during data refresh. The value assigned to this parameter is a comma-delimited list of Oracle or Sybase database error numbers. For example, to ignore primary key violations, but to stop refresh on any other update errors, set D_MIRROR_REFRESH_ERROR_LIST=1. This value corresponds to the Oracle error ″ORA-00001: unique constraint violated (<schema>.<constraint>)″. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “D_MIRROR_MIRROR_ERROR_STOP” on page 358

D_MIRROR_REFRESH_ERROR_STOP
Use this system parameter to indicate whether or not InfoSphere CDC should continue to perform a refresh after encountering an error during a row insert operation. Applies To—Target Set this parameter to one of the following: v ON—Data refresh stops after an error has occurred. v OFF—Data refresh continues after an error has occurred. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 “System parameters for InfoSphere CDC for Sybase (version 6.0 and below)” on page 399 Related reference “D_MIRROR_REFRESH_ERROR_LIST” “D_MIRROR_MIRROR_ERROR_STOP” on page 405

DM_ADAPTIVE_APPLY_SOFT_DELETES
Use this system parameter to enable InfoSphere CDC to apply a soft delete on all target tables mapped using Adaptive Apply in a subscription. Applies To—Target Set this parameter to one of the following:
System parameters for InfoSphere CDC for Oracle (version 6.2 and below)

359

v ON—When there is a delete on the source table, InfoSphere CDC either: – updates the rows on all target tables if the rows exist, or – inserts the rows on all target tables if the rows do not exist. v OFF—When there is a delete on the source table, InfoSphere CDC either: – deletes the rows on all target tables if the rows exist, or – does nothing and issues an informational message in the Event log if the rows do not exist. See ″Enabling Apply of Soft Deletes″ in the InfoSphere CDC Management Console Administration Guide. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 “Enabling the apply of soft deletes (InfoSphere CDC for Oracle)” on page 182

DM_ADAPTIVE_APPLY_<SCHEMA>.<TABLENAME>
Use this system parameter to enable InfoSphere CDC to apply a soft delete on a specific target table mapped using Adaptive Apply in a subscription. Applies To—Target Set this parameter to one of the following: v ON—When there is a delete on the source table, InfoSphere CDC either: – updates the row on the target table if the row exists, or – inserts the row on the target table if it does not exist. v OFF—When there is a delete on the source table, InfoSphere CDC either: – deletes the row on the target table if the row exists, or – does nothing and issues an informational message in the Event log if the row does not exist. See ″Enabling Apply of Soft Deletes″ in InfoSphere CDC Management Console Administration Guide. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 “Enabling the apply of soft deletes (InfoSphere CDC for Oracle)” on page 182

DM_ADAPTIVE_APPLY_MIMIC_SOURCE_OPERATION
Use this system parameter to modify the how InfoSphere CDC applies data to the target when you have mapped your source and target tables using Adaptive Apply. If you enable this system parameter, InfoSphere CDC avoids performing a SELECT query on the target table and you may benefit with performance improvement. For information about setting this system parameter, see your IBM representative. Applies To—Target Set this parameter to one of the following:

360

InfoSphere Change Data Capture Management Console: Administration Guide

v ON—InfoSphere CDC avoids performing a SELECT query on the target table. v OFF—InfoSphere CDC performs a SELECT query on the target table. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

DM_ARRAY_BIND_MAX
Use this system parameter to specify the maximum number of rows that InfoSphere CDC can place in an array and apply to the target database. InfoSphere CDC collects rows and places them in an array (in memory) while receiving table-level operations from the source system. InfoSphere CDC applies the rows from the array when there is a change to a different table, when there is a new table-level operation, or when the maximum number of rows in an array has been reached. Applies To—Target Default Setting—25 Minimum Setting—1 Maximum Setting—Maximum number of rows (integer) Guidelines Before InfoSphere CDC places rows into an array, it allocates memory for the maximum number of rows you specify and multiplies this integer by the maximum length of a row. If the maximum number of rows is too large, then InfoSphere CDC cannot allocate enough memory and will shut down. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

FILTER_NOCHANGE_UPDATES_FOR_AUDIT
Use this system parameter to indicate whether or not updates that have identical before and after column images (that is, the row has been updated to the same value), are replicated to the target table for any tables configured for LiveAudit replication. Applies To—Source Set this parameter to one of the following: v OFF—If a row in a source table is updated to the same value, InfoSphere CDC replicates the value to the target table. v ON—If a row in a source table is updated to the same value, InfoSphere CDC does not replicate the value to the target table. This parameter only affects tables that are configured for LiveAudit replication. For non-audit tables, only updates that change the column data are replicated to the target tables.
System parameters for InfoSphere CDC for Oracle (version 6.2 and below)

361

Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

NLS_LANG
Use this system parameter to specify the database character set preceded with a period. For more information about setting this system parameter, see your IBM representative. Applies To—Source and Target Default Setting—The database character set, preceded with a period, corresponding to the language selected when the database was installed. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

NLS_NCHAR
Use this system parameter to set the database national character set. For information about setting this system parameter, see your IBM representative.

NOT_NULL_DATE_DEFAULT
Applies To—Target Specifies the default value that InfoSphere CDC assigns to a NULL date being replicated to a non-nullable date column on the target database. If this parameter is not specified, InfoSphere CDC uses the Default Setting. Default Setting—1901-01-01 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “TRIM_TO_NULL” on page 363

TRIM_CHAR_TO_VARCHAR
Use this system parameter to specify whether or not trailing blank characters are trimmed from source columns of CHAR data type when replicating data to target columns of VARCHAR data type. Applies To—Target Set this parameter to one of the following: v OFF—Trailing blanks are not trimmed.

362

InfoSphere Change Data Capture Management Console: Administration Guide

v ON—Trailing blanks are trimmed. If TRIM_TO_NULL =OFF, InfoSphere CDC inserts a single blank character in the target column. If TRIM_TO_NULL =ON and the target column is nullable, InfoSphere CDC inserts NULL in the column. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “TRIM_TO_NULL”

TRIM_VARCHAR_TO_VARCHAR
Use this system parameter to specify whether or not trailing blank characters are trimmed from source columns of VARCHAR data type when replicating data to target columns of VARCHAR data type. Applies To—Target Set this parameter to one of the following: v OFF—Trailing blanks are not trimmed. v ON—Trailing blanks are trimmed. If TRIM_TO_NULL =OFF, InfoSphere CDC inserts a single blank character in the target column. If TRIM_TO_NULL =ON and the target column is nullable, InfoSphere CDC inserts NULL in the column. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “TRIM_TO_NULL”

TRIM_TO_NULL
Use this system parameter to specify how source columns that contain blank characters only are handled during data replication. Applies To—Target Set this parameter to one of the following: v OFF—For data mapped to VARCHAR columns, trailing blanks are trimmed or not to a single blank depending on the TRIM_CHAR_TO_VARCHAR and TRIM_VARCHAR_TO_VARCHAR system parameters. For data mapped to CHAR columns, setting this parameter to OFF has no effect. v ON—For data mapped to CHAR columns, if the target column is nullable, InfoSphere CDC inserts NULL in the column. For CHAR data mapped to VARCHAR columns, if TRIM_CHAR_TO_VARCHAR =ON and the target column is nullable, InfoSphere CDC inserts NULL in the column. For VARCHAR data mapped to VARCHAR columns, if TRIM_VARCHAR_TO_VARCHAR =ON and the target column is nullable, InfoSphere CDC inserts NULL in the column.

System parameters for InfoSphere CDC for Oracle (version 6.2 and below)

363

If the target column is non-nullable, source columns that contain blank characters only are handled according to the convertNotNullableColumns system parameter. The table below explains how the TRIM_ system parameters affect the data replicated to the target for source columns that contain blank characters only.
TRIM_ parameter settings TRIM_CHAR_ TO_ VARCHAR ON ON OFF OFF ON ON OFF OFF TRIM_ VARCHAR_ TO_ VARCHAR ON OFF ON OFF ON OFF ON OFF TRIM_ TO_ NULL ON ON ON ON OFF OFF OFF OFF Target data CHAR to VARCHAR NULL NULL Source data Source data VARCHAR to VARCHAR NULL Source data NULL Source data Any data type to CHAR NULL NULL NULL NULL Blanks Blanks Blanks Blanks

Single blank Single blank Single blank Source data Source data Source data Single blank Source data

Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “TRIM_VARCHAR_TO_VARCHAR” on page 363 “TRIM_CHAR_TO_VARCHAR” on page 362

UNICODE_HANDLING
Use this system parameter to indicate the default method of treating data in defined Unicode columns. For each InfoSphere CDC installation on a server, this system parameter defines the system default method of treating data in Unicode columns. If a Unicode column is set to the system default, the current system default method, as defined by this system parameter, is used. Applies To—Source The following Oracle data types are considered to be Unicode columns, and are therefore affected by the value assigned to this system parameter: v NCHAR v NVARCHAR2 v NCLOB This system parameter is set to either CHAR or NOCHANGE: v CHAR—InfoSphere CDC treats all data in Unicode columns as single-byte characters. Use this setting when Unicode columns contain single-byte character data. v NOCHANGE—InfoSphere CDC treats all data in Unicode columns as a continuous bit stream. Use this setting when Unicode columns contain

364

InfoSphere Change Data Capture Management Console: Administration Guide

non-single-byte character data. NOCHANGE ensures InfoSphere CDC will handle non-single-byte character data in the same way as previous InfoSphere CDC releases. Note: If replicating data to a non-Oracle subscriber, NOCHANGE does not ensure that replicated non-single-byte character data in Unicode columns are represented properly on the target. For replicated non single-byte character data, you may need to apply user exit programs or other customization to properly represent data in Unicode columns. For more information about user exit programs, see C user exits for table/row level operations in the ″User Exits″ section of the InfoSphere CDC for Oracle documentation. Default Setting—NOCHANGE Note: NOCHANGE does not ensure that replicated non-single-byte character data in Unicode columns are represented properly on the target. For replicated non-single-byte character data, you may need to apply user exit programs or other customization to properly represent the data in Unicode columns. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 “Setting multibyte and Unicode character set conversions” on page 175

Cascading replication system parameters
Cascading replication system parameters control InfoSphere CDC cascading replication. See also: “CASCADE_OMIT_TARGETS” “PREVENT_RECURSION”

CASCADE_OMIT_TARGETS
Use this system parameter to indicate whether or not cascading replication will be disabled for specific subscriptions. Applies To—Source The value assigned to this parameter is a comma-separated list of subscription names. Changes applied by InfoSphere CDC are not replicated to these subscriptions, even if you set the system parameter PREVENT_RECURSION to OFF. The list of subscriptions cannot exceed 1023 bytes in length. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “PREVENT_RECURSION”

PREVENT_RECURSION
Use this parameter to indicate whether or not to prevent cascading replication for bi-directional configurations.
System parameters for InfoSphere CDC for Oracle (version 6.2 and below)

365

Applies To—Source Set this parameter to one of the following: v ON—Changes applied by InfoSphere CDC are not be replicated back to the source database from where it came from. v OFF—Changes made by InfoSphere CDC are replicated, except when filtered out by the CASCADE_OMIT_TARGETS system parameter. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “CASCADE_OMIT_TARGETS” on page 365

Database journal (trigger) system parameters
Database journal or trigger system parameters let you manage the InfoSphere CDC journal table. See also: “REPORT_POSITION_INTERVAL” “MONITOR_PURGE_INTERVAL” on page 367 “MONITOR_REFRESH_PERIOD” on page 367 “mirror_journal_schema” on page 391

REPORT_POSITION_INTERVAL
Use this system parameter to specify how often (in seconds) the source informs the target about its position in the current journal during times of no activity. During times of no activity, when there are no journal entries to be processed pertaining to the current subscription, the source informs the target of its current position so that the target can advance its bookmarks accordingly. By specifying a low setting for this parameter, the target can reflect more accurately how far replication has progressed. Applies To—Source After a shutdown and restart, you can use this system parameter to prevent InfoSphere CDC from rereading entries that do not apply to the current replication configuration. The value of this parameter affects the information that is displayed in progress and bookmark messages. A high value for this parameter may result in information that is not up-to-date being displayed. Default Setting—5 Minimum Setting—1 Maximum Setting—300 Related concepts

366

InfoSphere Change Data Capture Management Console: Administration Guide

“System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

MONITOR_PURGE_INTERVAL
Use this system parameter to specify the time interval between journal purges. When this time interval has elapsed, InfoSphere CDC removes from its journals all records that have been committed on all targets to which they are replicated. Applies To—Source Specify this parameter in the format #h#m#s, where # is the number of hours, minutes, and seconds, respectively. For example, 1h30m represents 1 hour and 30 minutes. If a time specification value is 0, you can omit it. Default Setting—1h Minimum Setting—1m Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

MONITOR_REFRESH_PERIOD
Use this parameter to specify the time interval between journal polls. InfoSphere CDC performs journal polls to check for new changes on the source. Applies To—Source Note: If you replicate large volumes of data, set this parameter to its minimum value so that InfoSphere CDC checks for changes more frequently. Specify this parameter in the format #h#m#s, where # is the number of hours, minutes, and seconds, respectively. For example, 1h30m represents 1 hour and 30 minutes. If a time specification value is 0, you can omit it. Default Setting—5s Minimum Setting—1s Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347

Maximize throughput system parameters
InfoSphere CDC system parameters allow you to significantly reduce the workload of the target database during mirroring. The InfoSphere CDC apply process groups transactions on the target to reduce the workload. Every commit on the target database will correspond with a commit on the target. However, it may not perform every commit that was done on the source. For example, if the source does three small transactions containing one operation each, the target may commit all three operations as part of a single transaction. You can use this grouping of system parameters to significantly reduce the resources required by the target

System parameters for InfoSphere CDC for Oracle (version 6.2 and below)

367

database. The default settings are appropriate for most databases, but if your target system has limited resources and an increase in latency is acceptable, you can adjust the settings appropriately. See also: “COMMIT_GROUP_SIZE” “COMMIT_LEVEL” “COMMIT_INTERVAL” on page 369 “MAINTAIN_TRANSACTION_CONSISTENCY” on page 370 “SYNCHRONIZATION_COMMIT_ GROUP_SIZE” on page 370 “SYNCHRONIZATION_INTERVAL” on page 371 “TRANSACTION_GROUP_SIZE” on page 371 “TRANSACTION_INTERVAL” on page 372 “TRANSACTION_RECORDS_THRESHOLD” on page 372

COMMIT_GROUP_SIZE
Use this system parameter to specify the minimum number of rows InfoSphere CDC should apply to the database before a commit is issued. InfoSphere CDC issues a commit on the target when the transaction that contains the rows completes. Use the COMMIT_GROUP_SIZE and COMMIT_INTERVAL system parameters together. InfoSphere CDC issues a commit when either when the number of rows specified by COMMIT_GROUP_SIZE has been applied to the target, or when the time interval specified by COMMIT_INTERVAL has elapsed. Setting only one of these system parameters without the other can result in uncommitted data on the target. Applies To—Target Default Setting—5000 Minimum Setting—0. InfoSphere CDC does not use commit groups to apply data to the target. Guidelines Set this parameter to 0 if D_MIRROR_MIRROR_ERROR_STOP=OFF. If a rollback occurs, InfoSphere CDC rolls back all outstanding rows in the commit group. Since InfoSphere CDC is set to continue on error, you may lose data. Note: Use this parameter only if InfoSphere CDC is not running under commitment control (COMMIT_LEVEL =0).

COMMIT_LEVEL
Use this system parameter to indicate the level of commitment control for InfoSphere CDC to process transactions. Applies To—Target Set this parameter to one of the following:

368

InfoSphere Change Data Capture Management Console: Administration Guide

in seconds.2 and below)” on page 347 Related reference “COMMIT_LEVEL” on page 368 “COMMIT_GROUP_SIZE” on page 411 “D_MIRROR_MIRROR_ERROR_STOP” on page 358 System parameters for InfoSphere CDC for Oracle (version 6. When the COMMIT_INTERVAL time expires. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 COMMIT_INTERVAL Use this system parameter to specify the time interval between commits. Setting only one of these system parameters without the other can result in uncommitted data on the target. Guidelines Set this parameter to 0 if D_MIRROR_MIRROR_ERROR_STOP=OFF. InfoSphere CDC issues a commit on a target database for each completed transaction. Use the COMMIT_GROUP_SIZE and COMMIT_INTERVAL system parameters together. Note: Use this parameter only if InfoSphere CDC is not running under commitment control (COMMIT_LEVEL =0). InfoSphere CDC rolls back all outstanding rows in the commit group. v 2—When replication is interrupted. and ensures that a transaction will not be partially applied on the target database. InfoSphere CDC issues a commit when either when the number of rows specified by COMMIT_GROUP_SIZE has been applied to the target. or when the time interval specified by COMMIT_INTERVAL has elapsed. to limit the number of commits InfoSphere CDC issues on the target database. Since InfoSphere CDC is set to continue on error.v 0—Disables commitment control for transaction processing. Replication resumes after the last transaction that was successfully committed. you may lose data. InfoSphere CDC issues a commit on the target database for transactions that completed within that time interval.2 and below) 369 . Applies To—Target Default Setting—60 Minimum Setting—0. This level of commitment control provides true transaction consistency. updates in a transaction that is partially applied on the source and target databases will be rolled back to the last transaction that was successfully committed. No attempt to maintain transaction consistency is performed in the event that replication is interrupted. If a rollback occurs. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.

MAINTAIN_TRANSACTION_CONSISTENCY Use this system parameter to Indicate whether or not to maintain commitment control. Applies To—Source The SYNCRONIZATION_COMMIT_GROUP_SIZE and SYNCHRONIZATION_INTERVAL system parameters are intended to be used together.2 and below)” on page 347 Related reference “COMMIT_LEVEL” on page 368 SYNCHRONIZATION_COMMIT_ GROUP_SIZE Use this system parameter to specify the number of transactions applied to the database before InfoSphere CDC performs synchronization between the source and target. you must set MAINTAIN_TRANSACTION_CONSISTENCY=ON and COMMIT_LEVEL=2 before configuring any tables for mirroring. Synchronization occurs either when the number of transactions (specified by SYNCRONIZATION_COMMIT_GROUP_SIZE) have been applied or when the time interval (specified by SYNCHRONIZATION_INTERVAL) has elapsed. the COMMIT_LEVEL system parameter is treated as 0. Note: To enable commitment control. Default Setting—128 Minimum Setting—0. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC does not use commit groups to perform synchronization. In this case.483. v ON—Commitment control is enabled.648 (maximum integer) Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. In this case. whichever comes first. the COMMIT_LEVEL system parameter must be 0 or 2. Maximum Setting—2.147. Applies To—Source Set this parameter to one of the following: v OFF—Commitment control is disabled.2 and below)” on page 347 Related reference “SYNCHRONIZATION_INTERVAL” on page 371 370 InfoSphere Change Data Capture Management Console: Administration Guide .

Synchronization occurs either when the number of transactions (specified by SYNCHRONIZATION_COMMIT_ GROUP_SIZE ) have been applied or when the time interval (specified by SYNCRONIZATION_INTERVAL) has elapsed.2 and below)” on page 347 Related reference “SYNCHRONIZATION_COMMIT_ GROUP_SIZE” on page 370 TRANSACTION_GROUP_SIZE Use this system parameter to specify the number of complete transactions applied to the database before InfoSphere CDC issues a commit. Applies To—Target Default Setting—500 Minimum Setting—0 Guidelines To increase the throughput. whichever comes first. Use the TRANSACTION_GROUP_SIZE. The COMMIT_LEVEL system parameter should be set to2 on the target System parameters for InfoSphere CDC for Oracle (version 6. TRANSACTION_INTERVAL.SYNCHRONIZATION_INTERVAL Use this system parameter to specify the interval. Note: Use this parameter only if InfoSphere CDC is running under commitment control. set to a number of transactions that would be received when busy during the TRANSACTION_INTERVAL. Synchronization is achieved when the target reports to the source the position of the last committed change. in seconds.2 and below) 371 . and TRANSACTION_RECORDS_THRESHOLDS system parameters together. Applies To—Source The SYNCRONIZATION_INTERVAL and SYNCHRONIZATION_COMMIT_ GROUP_SIZE system parameters are intended to be used together. Default Setting—1 Minimum Setting—1 Maximum Setting—300 Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC issues a commit after applying the number of transactions specified by the TRANSACTION_GROUP_SIZE. or when the time interval specified by TRANSACTION_INTERVAL has elapsed. Setting only one of these system parameters without the other can result in uncommitted transactions on the target. at which synchronization is performed between the source and target.

TRANSACTION_RECORDS_THRESHOLD Use this system parameter to specify the maximum number of operations within a transaction or group of transactions before InfoSphere CDC issues a commit Applies To—Target Default Setting—3000 Minimum Setting—0 Tracing system parameters Tracing system parameters let you perform diagnostic activities with InfoSphere CDC. that can elapse between transactions before InfoSphere CDC issues a commit. then InfoSphere CDC issues a commit immediately. Setting only one of these system parameters without the other can result in uncommitted transactions on the target. in seconds. InfoSphere CDC issues a commit after applying the number of transactions specified by the TRANSACTION_GROUP_SIZE system parameter. Use this system parameter with the TRANSACTION_GROUP_SIZE system parameter. or exceeded the time interval. If there are no transactions received by the target system. or when the time interval specified by TRANSACTION_INTERVAL system parameter has elapsed. TRANSACTION_INTERVAL Use this system parameter to specify the time interval.database. Applies To—Target Default Setting—1 Minimum Setting—0 Guidelines InfoSphere CDC issues a commit only when a commit is received by the target system and you have reached the transaction group size. or exceeded the records threshold. and the MAINTAIN_TRANSACTION_CONSISTENCY system parameter should be set to ON on the source database. See also: “D_MIRROR_SP_TRACE” on page 373 “D_MIRROR_TRACE” on page 373 “D_MIRROR_TRACE_FILE_SIZE” on page 373 “D_MIRROR_TRACE_ON_ERROR” on page 374 “DM_PRINT_DIAGNOSTICS” on page 374 “D_MIRROR_ALARM_TRACE” on page 375 372 InfoSphere Change Data Capture Management Console: Administration Guide .

When enabling this setting. InfoSphere CDC creates two trace files. Default Setting—OFF Dynamic—No D_MIRROR_TRACE Use this system parameter to indicate whether or not tracing is enabled. System parameters for InfoSphere CDC for Oracle (version 6. When the second trace file reaches its maximum size. also set the size of the trace file to an appropriate value using the D_MIRROR_TRACE_FILE_SIZE system parameter. These trace files are not encrypted. It is a plain ASCII text file and can be read directly for troubleshooting purposes. Applies To—Target Set this parameter to one of the following: v OFF—Tracing is disabled.D_MIRROR_SP_TRACE Use this system parameter to enable tracing for your stored procedure user exit.2 and below) 373 . and are meant to be sent to IBM technical support for troubleshooting purposes. set the size of the trace file to a value that is not too high.2 and below)” on page 347 Related reference “D_MIRROR_TRACE_FILE_SIZE” “D_MIRROR_LOG” on page 349 “DIRPATH_LOGGING” on page 378 “D_MIRROR_ALARM_TRACE” on page 375 D_MIRROR_TRACE_FILE_SIZE Use this system parameter to specify the maximum size of a trace file in bytes. When the first trace file reaches its maximum size. These trace files are encrypted. InfoSphere CDC creates a second file. This setting has no effect when D_MIRROR_TRACE_ON_ERROR=ON. Default Setting—OFF Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC starts overwriting the first file. Applies To—Source and Target Set this parameter to one of the following: v OFF—Tracing is disabled. To avoid disk space problems. v ON—Tracing is enabled and InfoSphere CDC creates the appropriate trace files in the log directory. v ON—Tracing is enabled and InfoSphere CDC creates the appropriate trace files in the log directory.

which can consume a large amount of disk space and affect performance. These trace files are encrypted. When enabling this setting.2 and below)” on page 347 D_MIRROR_TRACE_ON_ERROR Use this system parameter to specify whether or not InfoSphere CDC enables tracing automatically when an error occurs. Applies To—Source Set this parameter to one of the following: v OFF—Diagnostic messages will not be generated.000.2 and below)” on page 347 Related reference “D_MIRROR_TRACE_FILE_SIZE” on page 373 DM_PRINT_DIAGNOSTICS Use this system parameter to Indicate whether or not to generate diagnostic messages in the InfoSphere CDC log files. it may cause large trace files to be created.000 bytes Minimum Setting—1. use this parameter only if advised by IBM technical support.000 bytes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. v ON—Diagnostic messages will be generated. To avoid running into disk space shortage problems.000. To avoid disk space problems. Default Setting—OFF Dynamic—Yes (on the target only) Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. and are meant to be sent to IBM technical support for troubleshooting purposes. Default Setting—OFF 374 InfoSphere Change Data Capture Management Console: Administration Guide .Applies To—Source and Target Default Setting—10. also set the size of the trace file to an appropriate value using the D_MIRROR_TRACE_FILE_SIZE system parameter. set the size of the trace file to a value that is not too high. Applies To—Source and Target Set this parameter to one of the following: v OFF—InfoSphere CDC does not enable tracing when an error occurs. v ON—InfoSphere CDC enables tracing when an error occurs. InfoSphere CDC creates the appropriate trace files in the InfoSphere CDC log directory. Note: If you enable tracing.

Tracing for notification is enabled when D_MIRROR_TRACE system parameter is also set to ON. Applies To—Source and Target Set this parameter to one of the following: v OFF—Tracing for notification is disabled. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. you can improve direct path loading performance. By setting this parameter to a value greater than 0. Applies To—Target The table below explains how the DIRPATH_BUF_ROWS and DIRPATH_BUF_SIZE system parameters affect the size of the internal buffer that InfoSphere CDC uses for direct path loading.Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 D_MIRROR_ALARM_TRACE Use this system parameter to Indicate whether or not tracing for notification is enabled. See also: “DIRPATH_BUF_ROWS” “DIRPATH_BUF_SIZE” on page 376 “DIRPATH_CACHE_DATE_SIZE” on page 377 “DIRPATH_LOAD” on page 377 “DIRPATH_LOGGING” on page 378 “DIRPATH_DO_RECOVERY” on page 378 DIRPATH_BUF_ROWS Use this system parameter to specify the number of rows allocated in the internal buffer used for direct path loading.2 and below) 375 . The trace files are encrypted and are meant to be sent to IBM for troubleshooting purposes.2 and below)” on page 347 Related reference “D_MIRROR_TRACE” on page 373 Refresh loader system parameters Some system parameters affect how InfoSphere CDC applies refresh operations. v ON—Tracing for notification is enabled. System parameters for InfoSphere CDC for Oracle (version 6. The notification tracing will be located in the same trace file used for regular tracing located in the directory specified by the D_MIRROR_LOG system parameter.

As specified by DIRPATH_BUF_SIZE. As specified by DIRPATH_BUF_SIZE. As specified by DIRPATH_BUF_ROWS.2 and below)” on page 347 Related reference “DIRPATH_BUF_SIZE” DIRPATH_BUF_SIZE Use this system parameter to specify the size. By setting this parameter to a value greater than 0. As specified by DIRPATH_BUF_SIZE. As specified by DIRPATH_BUF_ROWS.DIRPATH_BUF_ SIZE 0 DIRPATH_BUF_ ROWS 0 Internal buffer size Determined dynamically. 0 Greater than 0 Greater than 0 0 376 InfoSphere Change Data Capture Management Console: Administration Guide . InfoSphere CDC allocates an internal buffer that is large enough to store the number of rows specified by DIRPATH_BUF_ROWS. Applies To—Target The table below explains how the DIRPATH_BUF_SIZE and DIRPATH_BUF_ROWS system parameters affect the size of the internal buffer that InfoSphere CDC uses for direct path loading. based on the size of the table being loaded. for the internal buffer used for direct path loading. InfoSphere CDC allocates an internal buffer that is large enough to store the number of rows specified by DIRPATH_BUF_ROWS. you can improve direct path loading performance. based on the size of the table being loaded. DIRPATH_BUF_ SIZE 0 DIRPATH_BUF_ ROWS 0 Internal buffer size Determined dynamically. 0 Greater than 0 Greater than 0 Greater than 0 0 Greater than 0 Default Setting—0 Minimum Setting—0 Maximum Setting—231 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. in bytes.

Applies To—Target Set this parameter to one of the following: v ON—Direct path loading is enabled. InfoSphere CDC can load multiple rows by loading a direct path stream that contains data for multiple rows. If the table being refreshed does not contain any DATE data type columns. Minimum Setting—0 Maximum Setting—2^32 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “DIRPATH_BUF_ROWS” on page 375 DIRPATH_CACHE_DATE_SIZE Use this system parameter to specify the number of DATE (date and timestamp) values to be cached per table being refreshed. you can improve direct path loading performance by setting this parameter to a value higher than the default setting.2 and below) 377 . If the table being refreshed contains DATE data type columns. System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC uses Oracle Call Interface (OCI) functions to perform data refresh.2 and below)” on page 347 DIRPATH_LOAD Use this system parameter to enable or disable direct path loading. Default Setting—0 Minimum Setting—0 Maximum Setting—231 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. DATE values are not cached. v OFF—Direct path loading is disabled. during direct path loading. Applies To—Target Default Setting—0. Note: If you want to enable direct path loading. By using OCI functions. this parameter has no effect.DIRPATH_BUF_ SIZE Greater than 0 DIRPATH_BUF_ ROWS Greater than 0 Internal buffer size As specified by DIRPATH_BUF_SIZE. then you need perform a refresh on each subscription to send data to the target datastore.

In Direct Path Load.2 and below)” on page 347 DIRPATH_DO_RECOVERY Use this system parameter to modify how InfoSphere CDC handles rows that have conflicting unique index values. Oracle inserts data with full image redo logging. ON—All rows with conflicting unique index values will be removed and the index will be enabled. records that were inserted are marked as logically corrupted and cannot be recovered. However. This system parameter corresponds to the Oracle NOLOGGING keyword. thus providing improved performance. Set this parameter to one of the following: v OFF—Full image redo logging is not performed. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC places an index in direct load state when it detects one or more conflicts after performing a refresh of all rows. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 378 InfoSphere Change Data Capture Management Console: Administration Guide .Note: This setting is required in cascading replication configurations. Applies To—Target OFF—No rows are removed and the index remains in direct load state and ROWID of duplicate rows are stored in the exception table as indicated in the event log. in case of instance failure. Oracle generates a minimum number of redo log entries. For more information about image redo logging.2 and below)” on page 347 DIRPATH_LOGGING Applies To—Target Indicates whether or not full image redo logging is performed. to make sure that data changes are correctly replicated to the target tables. v ON—Full image redo logging is performed. which ensures that the necessary information is available in case of instance failure. see your Oracle documentation.

x. second connection. The stored procedure user exit program and InfoSphere CDC will use the same. you must set this parameter to ON. the before and after images in C user exit programs were received in the code page of the source.x.1 and greater.2 and below) 379 . they are received in the code page of the target. Applies To—Target Set this parameter to one of the following: v OFF—A second connection to the database is not established. data must be translated back from the code page of the target to the code page of the source. To use the user exit program as defined in Version 4.2 and below)” on page 347 DM_FROM_CODEPAGE_V4USEREXIT Applies To—Target Set this parameter only if using before or after images in C user exit programs defined in InfoSphere CDC Version 4. to the Oracle database. In InfoSphere CDC Version 4. They will always use the same connection to the database as InfoSphere CDC. or stored procedure user exit programs invoked within an expression.User exit system parameters Some system parameters control user exits. Attention: If any stored procedure user exit program is issuing a commit or rollback. In Version 5. See also: “D_MIRROR_SP_CONNECTION” “DM_FROM_CODEPAGE_V4USEREXIT” “DM_TO_CODEPAGE_V4USEREXIT” on page 380 “userexit_max_lob_size_kb” on page 397 D_MIRROR_SP_CONNECTION Use this system parameter to indicate whether or not a second connection to the Oracle database is established for a stored procedure user exit program to run. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. shared connection to the Oracle database. v ON—A second connection to the database is established. or errors may be generated when applying data to the target database.x. This setting ensures that changes to tables made by InfoSphere CDC are visible to the stored procedure user exit program. The stored procedure user exit program will use this separate. Setting this parameter to ON does not affect stored procedure user exit programs for conflict resolution. otherwise data may be lost. System parameters for InfoSphere CDC for Oracle (version 6. using the %STPROC column function.

you will learn about system parameters that control table mappings. 380 InfoSphere Change Data Capture Management Console: Administration Guide .Therefore. Applies To—Target Set this parameter to one of the following: v OFF—InfoSphere CDC does not remove references to target tables when the assigned source table no longer exists. In Version 5. specify for this parameter the code page to translate from (the code page of the target). Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.x.2 and below)” on page 347 DM_TO_CODEPAGE_V4USEREXIT Applies To—Target Set this parameter only if using before or after images in C user exit programs defined in InfoSphere CDC Version 4. To use the user exit program as defined in Version 4.x. If this parameter is not set. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. data must be translated back from the code page of the target to the code page of the source. they are received in the code page of the target. See also: “TS_DELETE_ASSIGNED_OBJECTS_DURING_DESCRIBE” TS_DELETE_ASSIGNED_OBJECTS_DURING_DESCRIBE Use this system parameter (when describing source tables to subscriptions) to specify whether or not to remove references to target tables when the mapped source table no longer exists.x. In InfoSphere CDC Version 4. Table mapping system parameters In this section.1 and higher. no translation will be performed from the code page of the target to the code page of the source. Therefore. the before and after images in C user exit programs were received in the code page of the source.2 and below)” on page 347 Table mapping system parameters Some system parameters control table mappings. If this parameter is not set. specify for this parameter the code page to translate to (the code page of the source). no translation will be performed from the code page of the source to the code page of the target.

The default value depends on the data type of the subscription column. Depending on the convertNotNullableMsg system parameter setting. No error message is generated in Event Log and replication continues. blank character for character data types. v ON—InfoSphere CDC will automatically insert an appropriate default value in the target column.2 and below)” on page 347 DEADBAND_PERCENTAGE Applies To—Target System parameters for InfoSphere CDC for Oracle (version 6. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. 1901-01-01 for date data types. and so on. a warning message may be generated in Event Log. Applies To—Target Set this parameter to one of the following: v OFF—An error message will be generated in Event Log. For example. Replication will continue or not based on whether the MirrorError or RefreshError system parameters are set to END or ON.2 and below)” on page 347 Notification system parameters Notification system parameters let you control if you should generate InfoSphere CDC messages in the Event Log for specific events. zero for numeric data types.2 and below) 381 . Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.v ON—InfoSphere CDC removes references to target tables when the assigned source table no longer exists. See also: “convertNotNullableMsg” “DEADBAND_PERCENTAGE” “DM_STATUS_INTERVAL” on page 384 “HEARTBEAT_TIMEOUT” on page 384 “LOG_EMAIL_USERNAME” on page 385 “MONITOR_SAMPLE_INTERVAL” on page 385 “STATISTICS_INTERVAL” on page 386 convertNotNullableMsg Use this system parameter to indicate whether or not NULL values will be converted to default values when replicating data that contains NULL values to non-nullable target columns.

By changing the value assigned to this system parameter. Based on the same sample latency in the previous graph where latency is 382 InfoSphere Change Data Capture Management Console: Administration Guide . A latency message is generated only when latency has risen above the upper limit of the range or fallen below the lower limit of the range. and the threshold itself can be made thicker or thinner. The following calculations are performed to determine the lower and upper limits (in minutes) of the range around the threshold: v Padding = 10% of 5 minutes = 0.5 minutes (rounded up to 1 minute) v Padding is rounded up or down to the nearest whole minute: – Upper limit of range = 5 minutes + 1 minute (padding) = 6 minutes – Lower limit of range = 5 minutes . Latency is calculated at regular intervals. no padding is applied to the latency threshold. A 10% range is applied around the 5 minute threshold. three latency messages are generated. You can set notifications in response to a generated latency message. a latency message is generated when latency has risen above or fallen below a threshold.1 minute (padding) = 4 minutes As a result. a latency message will be generated only when latency rises above 6 minutes or falls below 4 minutes. a latency message is generated each time latency crosses over the latency threshold of 5 minutes. This system parameter. which is expressed as a percentage. Therefore. assume that a latency threshold is 5 minutes and this system parameter is set to 10. you can control the number of latency messages placed in Event Log. the size of the range around the threshold can be increased or decreased. where the interval is the current setting for the MONITOR_SAMPLE_INTERVAL system parameter. By adjusting this system parameter. This graph illustrates latency message generation with the DEADBAND_PERCENTAGE value set to 10%: If this DEADBAND_PERCENTAGE is set to 3 (the default setting) for the same example. Given sample latency over a ten minute period where latency is calculated every minute.Identifies the size of the range around each latency threshold setting. Based on latency thresholds defined. allows you to pad a threshold equally on both sides to create a range around the threshold. For example.

five latency messages are generated when this system parameter is set to 3. This graph illustrates latency message generation with the DEADBAND_PERCENTAGE value set to 3%: If the number of latency messages generated over the ten minute period for the 10% (3 latency messages) and 3% (5 latency messages) settings are averages. If a value outside the acceptable range is specified.2 and below) 383 . Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. In this case. Default Setting—3% Minimum Setting—3% Maximum Setting—10% Note: If you set a value outside the acceptable range.calculated every minute. Since there are two latency thresholds that you can set (a warning threshold and a problem threshold).2 and below)” on page 347 “Disk resource system parameters” on page 386 “Setting latency thresholds and notifications” on page 78 System parameters for InfoSphere CDC for Oracle (version 6. the default setting is used. an additional 288 latency messages would be generated each day if this system parameter is not changed from its default setting to 10%. and the two ranges can overlap with no change in behavior. each range is attached to its threshold. then InfoSphere CDC uses the defaults. two separate ranges are defined when padding is at least one minute.

In addition. clear Event Log on a regular basis. These messages are displayed in Event Log to indicate how replication is advancing and to provide detailed information about InfoSphere CDC replication activities. Applies To—Source and Target Note: Low values of this parameter may result in many messages displayed in Event Log. For each active subscription. messages (message identifiers 2612 and 3165) are placed in Event Log when heartbeat timeouts occur. No progress notifications will be issued. Default Setting—0 seconds. Minimum Setting—0 seconds.2 and below)” on page 347 “Displaying event messages during replication” on page 232 384 InfoSphere Change Data Capture Management Console: Administration Guide . Applies To—Source Default Setting—15 minutes Minimum Setting—3 minutes Maximum Setting—999 minutes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. In this situation. and attempts to stop all its source and target processes for the subscription. Heartbeat is a feature that manages InfoSphere CDC processes when a problem with communications or a process has been detected through the absence of communications over a specified period of time. Maximum Setting—7200 seconds Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.DM_STATUS_INTERVAL Use this system parameter to specify how often progress messages should be issued in seconds. No progress notifications will be issued. If a reply to a message is not received by the source or target within the specified timeout interval. internal heartbeat messages are sent regularly between the source and the target to determine communications and process status.2 and below)” on page 347 HEARTBEAT_TIMEOUT Use this parameter to specify the number of minutes of communication inactivity to wait before active InfoSphere CDC processes for a subscription are stopped. then InfoSphere CDC determines that a problem has occurred.

Default Setting—5 seconds Minimum Setting—0 seconds.2 and below) 385 . Applies To—Source and Target In UNIX environments. in seconds. set this parameter to NOMAIL. this setting also represents how often the storage area is sampled to determine if latency has risen above or fallen below specified threshold settings. If a value smaller than the minimum setting is specified. the value assigned to this parameter is a comma-separated list of user names. the maximum setting is used. between consecutive updates to a storage area that is used to maintain replication latency metrics. To suppress all email messages. Applies To—Source and Target On the target.2 and below)” on page 347 “Setting latency thresholds and notifications” on page 78 System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Related reference “STATISTICS_INTERVAL” on page 386 MONITOR_SAMPLE_INTERVAL Use this system parameter to identify the period of time. The value of this parameter cannot exceed 30 bytes in length. Replication latency metrics are not updated. InfoSphere CDC generates latency messages when latency rises above or falls below the thresholds. Maximum Setting—3600 seconds Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. you can set latency notifications. the minimum setting is used.LOG_EMAIL_USERNAME Use this system parameter to specify the user name that receives email messages in response to invoking the dmreadlog command or the warning message that is generated when Event Log exceeds the threshold value set by the LOG_MAX_SIZE system parameter. If a value larger than the maximum setting is specified. Management Console references this area to present replication latency information. Default Setting—The InfoSphere CDC account (UNIX user) specified when InfoSphere CDC was installed Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. In response to a generated message.

in seconds.2 and below)” on page 347 386 InfoSphere Change Data Capture Management Console: Administration Guide . set this parameter to NOMAX. For improved performance. InfoSphere CDC issues messages that contain statistics information.STATISTICS_INTERVAL Use this system parameter to specify how often. The messages in Event Log are deleted automatically when the size of Event Log is ten times the value specified by this parameter. InfoSphere CDC does not provide statistics information. Minimum Setting—0. A warning message is generated in Event Log when its size exceeds specified threshold. Default Setting—0. Applies To—Source and Target Note: Use this parameter only if advised by IBM technical support. if you are able to allocate more than the default value of 512 MB for the InfoSphere CDC Java Virtual Machine. then you can adjust the disk resource system parameters to use the increased memory. Default Setting—5000 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.2 and below)” on page 347 Disk resource system parameters Some system parameters control memory usage in InfoSphere CDC.647 (maximum integer) Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.147.483. See also: “LOG_MAX_SIZE” LOG_MAX_SIZE Use this system parameter to specify the threshold size of Event Log in KB. Maximum Setting—2. Applies To—Source and Target If you do not want to specify a threshold size. InfoSphere CDC does not provide statistics information. These messages are displayed in Event Log.

See also: “mirror_set_table_data_capture_timeout” “mirror_asm_oracle_path” on page 388 mirror_set_table_data_capture_timeout Use this system parameter to indicate how long (in minutes) InfoSphere CDC waits before declaring a failure when preparing a table for mirroring. you will learn: “General product system parameters” “Notification system parameters” on page 388 “Maximize throughput system parameters” on page 389 “Database journal (trigger) system parameters” on page 366 “Encoding system parameters” on page 391 “Disk resource system parameters” on page 392 “Apply process system parameters” on page 393 “User exit system parameters” on page 379 General product system parameters General product system parameters let you control basic features of InfoSphere CDC and information you may have specified during installation. Maintain these default settings until you become familiar with the configuration of InfoSphere CDC. The default system parameter settings are appropriate for most installations.3 and above) System parameters let you control the behavior of InfoSphere CDC. Note: If you make changes to a system parameter during active replication.System parameters for InfoSphere CDC for Oracle (version 6. If your replication environment requires a particular configuration. then you can use system parameters to modify the behavior of default operations in InfoSphere CDC. 2008 387 . InfoSphere CDC provides system parameters that control the behavior of your source and/or target datastores. Applies To—Source Default—30 minutes Minimum—0 minutes Maximum—90 minutes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. you must stop and restart replication for the changes to take effect. In this section.3 and above)” © Copyright IBM Corp.

Applies To—Source Default Setting—15 minutes Minimum Setting—3 minutes Maximum Setting—999 minutes Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. If a value outside the acceptable range is specified.3 and above)” on page 387 global_shutdown_after_no_heartbeat_response_minutes Use this system parameter to specify the duration. See also: “events_max_retain” “global_shutdown_after_no_heartbeat_response_minutes” “global_conversion_not_possible_warning” on page 389 events_max_retain Use this system parameter when you want InfoSphere CDC to refresh a target table that contains multibyte object names. Applies To—Target Default Setting—false Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Replace the ORCL label that references the common directory of the ASM-managed devices with the actual directory path. v false—InfoSphere CDC will refresh a target table that contains multibyte object names.3 and above)” on page 387 388 InfoSphere Change Data Capture Management Console: Administration Guide . of communication inactivity before active InfoSphere CDC processes for a subscription are stopped. Set this parameter to one of the following: v true—InfoSphere CDC will not refresh the target table that contains multibyte object names. Notification system parameters Notification system parameters let you control if you should generate InfoSphere CDC messages in the Event Log for specific events. in minutes. the default setting is used.mirror_asm_oracle_path Use this system parameter if the Oracle database uses ASM to manage its datafile or redo logs on a Linux box.

Every commit on the target database will correspond with a commit on the target. For example. See also: “mirror_commit_on_transaction_boundary” “mirror_sess_hist_age_threshold” on page 390 “mirror_src_ora_version” on page 390 “refresh_commit_after_max_operations” on page 390 “userexit_max_lob_size_queue” on page 391 mirror_commit_on_transaction_boundary This system parameter indicates whether or not the commits that InfoSphere CDC does on the target database will always correspond with a commit that occurred on the source database. You can use this grouping of system parameters to significantly reduce the resources required by the target database. v Converted data types are encountered that are out of range. The default settings are appropriate for most databases.3 and above) 389 . if the source does three small transactions containing one operation each. Applies To—Target Default Setting—False Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. the target may commit all three operations as part of a single transaction. but if your target system has limited resources and an increase in latency is acceptable. Set this parameter to one of the following: System parameters for InfoSphere CDC for Oracle (version 6. false—does not generate a warning in the Event Log if data conversion is not possible for a specific data value or converted data types are encountered that are out of range. If you choose to ignore the commitment control of the source database.3 and above)” on page 387 Maximize throughput system parameters InfoSphere CDC system parameters allow you to significantly reduce the workload of the target database during mirroring. Set this parameter to one of the following: true—generates a warning in the Event Log if data conversion is not possible for a specific data value or converted data types are encountered that are out of range. However. The InfoSphere CDC apply process groups transactions on the target to reduce the workload. InfoSphere CDC allows you to see the partial results of large transactions. it may not perform every commit that was done on the source. you can adjust the settings appropriately.global_conversion_not_possible_warning Use this system parameter to control whether or not InfoSphere CDC generates a warning in the Management Console Event Log in the following situations: v Data conversion is not possible for a specific data value.

If the primary database is version 10g or higher. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. No attempt to maintain transaction consistency is performed during mirroring. A negative number results in the retention of all log information.3 and above)” on page 387 mirror_src_ora_version This system parameter identifies the database version of the primary database. For example. If the value is set to a positive number.2. This value disables commitment control for transaction processing. then you must set this parameter on both the primary and backup systems.0. InfoSphere CDC periodically commits the changes to the target database rather than performing the refresh as a single large transaction. the session history will be purged accordingly. Applies To—Target Default Setting—1000 Minimum Setting—1 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. v Applies To—Target Default Setting—true Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Set this parameter to the full database version number.1.3 and above)” on page 387 390 InfoSphere Change Data Capture Management Console: Administration Guide .true—Does not ignore the commitment control of the source database.3 and above)” on page 387 refresh_commit_after_max_operations This system parameter identifies the number of rows comprising each transaction during refresh. v false—Ignores the commitment control of the source database.0. To reduce the workload on the target database during refresh. 10. This setting provides true transaction consistency by ensuring that only committed transactions are sent to the target. Default Setting—1 Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Only records in a committed transaction are mirrored to the target.3 and above)” on page 387 mirror_sess_hist_age_threshold Use this system parameter to identify the number of days of session history to maintain.

The value of this system parameter must refer to the name of an existing journal table. and you can set the default character encoding for your database. See also: “REPORT_POSITION_INTERVAL” on page 366 “MONITOR_PURGE_INTERVAL” on page 367 “MONITOR_REFRESH_PERIOD” on page 367 “mirror_journal_schema” mirror_journal_schema Use this system parameter to enable multiple instances of InfoSphere CDC to share the same trigger and journal table. Applies To–Source Default Setting–N/A Encoding system parameters For some system parameters. and created another instance INSTANCE2 that specifies the journal SCHEMA2. then you would set the system parameter mirror_journal_schema on INSTANCE2 so that it points to the journal SCHEMA1.userexit_max_lob_size_queue Use this system parameter to set the maximum size of LOB data (in kb) that InfoSphere CDC can pass to a user exit. you can set the default method for treating data in defined Unicode columns.3 and above)” on page 387 Database journal (trigger) system parameters Database journal or trigger system parameters let you manage the InfoSphere CDC journal table. To enable this system parameter. if you have created an instance INSTANCE1 that specifies the journal SCHEMA1. You can only set a value for this system parameter before mapping your tables and setting the subscription for mirroring. you must specify the name of the journal that you want shared with another instance of InfoSphere CDC. See also: “global_unicode_as_char” on page 392 System parameters for InfoSphere CDC for Oracle (version 6.3 and above) 391 . For example. This enables both instances to share the same trigger and journal table. Applies To—Target Default Setting—128 kb Maximum—None Minimum—None Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.

Default Setting—false Applies To—Source Note: Setting this parameter to false does not ensure that replicated non-single-byte character data in Unicode columns are represented properly on the target. and delete operations. this system parameter defines the system default method of treating data in Unicode columns. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.3 and above)” on page 387 Disk resource system parameters Some system parameters control memory usage in InfoSphere CDC. Use this setting when Unicode columns contain single-byte character data. For each InfoSphere CDC installation on a server. For information about how data in each Unicode source column is treated and setting multibyte and Unicode character set conversions. Using Management Console. Use this setting when Unicode columns contain non-single-byte character data. see “Setting multibyte and Unicode character set conversions” on page 175. For improved performance. if you are able to allocate more than the default value of 512 MB for the InfoSphere CDC Java Virtual Machine. Applies To—Source Default Setting—7 database operations 392 InfoSphere Change Data Capture Management Console: Administration Guide . The capacity is measured by the number of operations you want the queue to be able to store.global_unicode_as_char Use this system parameter to indicate the default method of treating data in defined Unicode columns. This includes insert. See also: “mirror_queue_for_buffers_between_cdc_threads_operations” “mirror_global_disk_quota_mb” on page 393 mirror_queue_for_buffers_between_cdc_threads_operations Use this system parameter to set the capacity of InfoSphere CDC queues to store captured changes. Set this parameter to one of the following: True—InfoSphere CDC treats all data in Unicode columns as single-byte characters. update. then you can adjust the disk resource system parameters to use the increased memory. you can specify how InfoSphere CDC converts multibyte character sets on source columns during replication. as defined by this system parameter. the current system default method. False—InfoSphere CDC treats all data in Unicode columns as a continuous bit stream. If a Unicode column is set to the system default. is used. Setting this parameter to false ensures that InfoSphere CDC handles non-single-byte character data in the same way as previous InfoSphere CDC releases.

staging stores. See also: “convert_not_nullable_column” “global_max_batch_size” on page 394 “mirror_end_on_error” on page 394 “refresh_end_on_error” on page 394 “refresh_allow_fast_loader” on page 395 “refresh_allow_jdbc_batch” on page 395 “mirror_expected_errors_list” on page 395 “refresh_in_unicode” on page 396 “trim_char_to_varchar” on page 396 “trim_varchar_to_varchar” on page 396 convert_not_nullable_column Use this system parameter to specify whether or not InfoSphere CDC should strip or leave trailing blanks on string data of the column in the target table.Maximum—2 63-1 =9223372036854775807 operations Minimum—1 database operation Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.3 and above)” on page 387 mirror_global_disk_quota_mb Use this system parameter to globally set a disk quota (in MB) for all capture components (including temporary files. Set this parameter to one of the following: v true—InfoSphere CDC strips the data of trailing blanks. and error handling. and operation queues).3 and above) 393 . System parameters for InfoSphere CDC for Oracle (version 6. transaction queues. Applies To—Source and Target Default Setting—0 Maximum—None Minimum—None Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. v false—InfoSphere CDC does not strip the string data of trailing blanks.3 and above)” on page 387 Apply process system parameters Some system parameters adjust the way InfoSphere CDC applies rows. column data. InfoSphere CDC will manage disk space utilization across all components as required.

3 and above)” on page 387 refresh_end_on_error Use this system parameter to indicate if you want to end a refresh after an apply error occurs. v false—Do not end mirroring after an apply error on the target database. when there is a new table-level operation. Management Console references this area to present replication latency information. Set this parameter to one of the following: v true—End a refresh after an apply error occurs. Use only during a refresh if refresh_end_on_error is true and refresh_expected_errors_list is empty. You can use this parameter during mirroring only if mirror_end_on_error is true and mirror_expected_errors_list is empty. Applies To—Target Default Setting—true Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Target InfoSphere CDC for Sybase Default Setting—25 rows Minimum Setting—1 row mirror_end_on_error Use this system parameter to indicate if you want to end mirroring after an apply error occurs on the target database. Before InfoSphere CDC places rows into an array. then InfoSphere CDC cannot allocate enough memory and will shut down. 394 InfoSphere Change Data Capture Management Console: Administration Guide . or when the maximum number of rows in an array has been reached. InfoSphere CDC collects rows and places them in an array (in memory) while receiving table-level operations from the source system.Applies To—Target Default Setting—false Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. InfoSphere CDC applies the rows from the array when there is a change to a different table. Set this parameter to one of the following: v true—End mirroring after an apply error on the target database. If the maximum number of rows is too large.3 and above)” on page 387 global_max_batch_size Use this system parameter to specify the maximum number of rows that InfoSphere CDC can place in an array and apply to the target database during refresh or mirroring. it allocates memory for the maximum number of rows you specify and multiplies this integer by the maximum length of a row.

This parameter can be used to allow or prevent JDBC batch from being considered. Set this parameter to one of the following: true—allows JDBC batch to be considered as an apply mode.3 and above)” on page 387 refresh_allow_fast_loader This parameter can be used to allow or prevent Oracle direct path (fast load) from being considered as a refresh method. Applies To—Target Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.3 and above)” on page 387 System parameters for InfoSphere CDC for Oracle (version 6. Applies To—Target Default Setting—true Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.3 and above)” on page 387 refresh_allow_jdbc_batch There are three apply modes for refresh: fastload.v false—Do not end a refresh after an apply error occurs.3 and above) 395 . JDBC batch and JDBC. then JDBC batch if possible and chooses JDBC if necessary. You must specify the errors in a comma separated list. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. false—prevents JDCBC batch from being considered as an apply mode. Set this parameter to one of the following: true—Allows fast load when appropriate. InfoSphere CDC chooses fastload if possible. Applies To—Target Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. false—Does not allow fast load.3 and above)” on page 387 mirror_expected_errors_list Use this system parameter when you want InfoSphere CDC to ignore specific database errors when applying data changes to the target during mirroring.

v false—InfoSphere CDC will not refresh a target table that contains multibyte object names. Applies To—Target Default Setting—false Related concepts “System parameters for InfoSphere CDC for Oracle (version 6.3 and above)” on page 387 trim_varchar_to_varchar Use this system parameter to specify whether or not InfoSphere CDC should strip or leave trailing blanks on string data of the column in the target table. Set this parameter to one of the following: v v true—InfoSphere CDC does not pad the string data with trailing blanks. false—InfoSphere CDC pads the string data with trailing blanks. Applies To—Target Default Setting—false Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Set this parameter to one of the following: v true—InfoSphere CDC strips the data of trailing blanks.refresh_in_unicode Use this system parameter when you want InfoSphere CDC to refresh a target table that contains multibyte object names.3 and above)” on page 387 396 InfoSphere Change Data Capture Management Console: Administration Guide .3 and above)” on page 387 trim_char_to_varchar Use this system parameter to specify whether or not InfoSphere CDC should pad string data with trailing blanks to the length of the column in the target table. v false—InfoSphere CDC does not strip the string data of trailing blanks. Applies To—Target Default Setting—false Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. Set this parameter to one of the following: v true—InfoSphere CDC will refresh the target table that contains multibyte object names.

3 and above) 397 . See also: “D_MIRROR_SP_CONNECTION” on page 379 “DM_FROM_CODEPAGE_V4USEREXIT” on page 379 “DM_TO_CODEPAGE_V4USEREXIT” on page 380 “userexit_max_lob_size_kb” userexit_max_lob_size_kb Use this system parameter to set the maximum size of LOB data (in kb) that InfoSphere CDC can pass to a user exit. Applies To—Target Default Setting—128 kb Maximum—None Minimum—None Related concepts “System parameters for InfoSphere CDC Event Server” on page 493 “Setting system parameters on source and target datastores” on page 60 System parameters for InfoSphere CDC for Oracle (version 6.User exit system parameters Some system parameters control user exits.

398 InfoSphere Change Data Capture Management Console: Administration Guide .

In this section. If your replication environment requires a particular configuration. The default system parameter settings are appropriate for most installations. you will learn: “General product system parameters” “Apply process system parameters” on page 404 “Cascading replication system parameters” on page 409 “Database journal (trigger) system parameters” on page 410 “Maximize throughput system parameters” on page 410 “Tracing system parameters” on page 413 “Notification system parameters” on page 415 “Disk resource system parameters” on page 420 “Refresh loader system parameters” on page 421 General product system parameters General product system parameters let you control basic features of InfoSphere CDC and information you may have specified during installation. See also: “CODE_PAGE” on page 400 “D_MIRROR_HOME” on page 400 “D_MIRROR_LOG” on page 400 “DM_DYNAMIC_PARAMETER_CHECK_INT” on page 400 “DM_MAX_MONITOR_ENTRIES” on page 401 “DSQUERY” on page 401 “LD_LIBRARY_PATH” on page 401 “LIBPATH” on page 402 “PUBLISH_METADATA” on page 402 “SYBASE” on page 402 “SYBASE_OCS” on page 402 “SHLIB_PATH” on page 403 “STARTUP_TIMEOUT” on page 403 “USER” on page 403 © Copyright IBM Corp. InfoSphere CDC provides system parameters that control the behavior of your source and/or target datastores. you must stop and restart replication for the changes to take effect. 2008 399 . then you can use system parameters to modify the behavior of default operations in InfoSphere CDC.0 and below) System parameters let you control the behavior of InfoSphere CDC.System parameters for InfoSphere CDC for Sybase (version 6. Note: If you make changes to a system parameter during active replication.

CODE_PAGE Use this system parameter to specify the code page associated with NLS_LANG. in seconds. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.000. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. For example. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.0 and below)” on page 399 D_MIRROR_LOG Use this system parameter to specify the directory (full path) where InfoSphere CDC log files are located. Applies To—Source and Target Default Setting—The log subdirectory in the installation directory specified when InfoSphere CDC was installed. Applies To—Source and Target Default Setting—The installation directory specified when InfoSphere CDC was installed. Applies To—Source and Target The following system parameters are dynamic: v “D_MIRROR_TRACE” on page 414 400 InfoSphere Change Data Capture Management Console: Administration Guide . Applies To—Source and Target Default Setting—The system code page when InfoSphere CDC was installed. set this parameter to 216.0 and below)” on page 399 DM_DYNAMIC_PARAMETER_CHECK_INT Use this system parameter to specify how often. to check once a day. This value is set during installation and should not be modified except under the guidance of a IBM technical support.0 and below)” on page 399 Related reference “NLS_LANG” on page 406 D_MIRROR_HOME Use this system parameter to specify the directory (full path) where InfoSphere CDC is installed on the server. InfoSphere CDC checks for changes to the values of dynamic system parameters during active replication to a subscription.

Applies To—Source and Target Default Setting—The path to the InfoSphere CDC libraries and the Sybase libraries when InfoSphere CDC was installed Related concepts System parameters for InfoSphere CDC for Sybase (version 6. InfoSphere CDC will allocate 30 entries for this datastore. then you must set this system parameter to at least 30. Maximum Setting—2. Applies To—Source and Target LD_LIBRARY_PATH Use this system parameter to specify the path to the InfoSphere CDC libraries and the database libraries for Solaris and Linux operating systems.483. Applies To—Source Default Setting—20 entries.147.0 and below) 401 . InfoSphere CDC can handle 20 subscriptions. if you have a datastore that is being used as a source datastore within 20 subscriptions and as a target datastore within 10 subscriptions. This value is set during installation and should not be modified.v v v v v “D_MIRROR_TRACE_ON_ERROR” on page 414 (on the target only) “DM_PRINT_DIAGNOSTICS” on page 374 “STATISTICS_INTERVAL” on page 420 “SYNCHRONIZATION_COMMIT_ GROUP_SIZE” on page 412 “SYNCHRONIZATION_INTERVAL” on page 413 Default Setting—300 seconds (5 minutes) Minimum Setting—0. By default. InfoSphere CDC allocates an entry for each source and target datastore within a subscription. Minimum Setting—1 entry Maximum Setting—1000 entries DSQUERY Use this system parameter to specify the name of the Sybase server.648 (maximum integer) Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. InfoSphere CDC does not check for changes to dynamic system parameters. For example.0 and below)” on page 399 DM_MAX_MONITOR_ENTRIES Use this system parameter to increase or decrease the number of subscriptions that InfoSphere CDC can support in the Monitor in Management Console.

Applies To—Source and Target Default Setting—The path to the InfoSphere CDC libraries and the database libraries when InfoSphere CDC was installed. This value is set during the installation and should not be modified.0 and below)” on page 399 PUBLISH_METADATA Use this system parameter to enable or disable the display of InfoSphere CDC metadata tables in Management Console. v ON—InfoSphere CDC metadata tables are displayed in the Add/Remove Tables dialog box. This value is set during the installation and should not be modified. making them available to be selected for replication.“System parameters for InfoSphere CDC for Sybase (version 6. Applies To—Source and Target Related concepts 402 InfoSphere Change Data Capture Management Console: Administration Guide .0 and below)” on page 399 LIBPATH Use this system parameter to specify the path to the InfoSphere CDC libraries and the database libraries (for AIX operating systems).0 and below)” on page 399 SYBASE_OCS Use this system parameter to specify the Sybase Open Client directory. Applies To—Source and Target Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. This value is set during installation and should not be modified. Applies To—Source Set this parameter to one of the following: v OFF—InfoSphere CDC metadata tables are not displayed in Management Console.0 and below)” on page 399 SYBASE Use this system parameter to specify the Sybase home directory. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.

in seconds. It indicates how long the communication program waits for the database setup program to start before timing out.0 and below)” on page 399 SHLIB_PATH Use this system parameter to specify the path to the InfoSphere CDC libraries and the database libraries for HP-UX operating systems.0 and below)” on page 399 USER Use this system parameter to specify the database user name that was specified during installation. Applies To—Source and Target Default Setting—120 Minimum Setting—60 Maximum Setting—3600 Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. and errors to the target. column data.0 and below)” on page 399 System parameters for InfoSphere CDC for Sybase (version 6. You can also set this user using the dmsetpass command. for process handling to complete during InfoSphere CDC startup. Applies To—Source Default Setting—The InfoSphere CDC user specified when InfoSphere CDC was installed. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.0 and below)” on page 399 STARTUP_TIMEOUT Use this system parameter to specify the maximum waiting period. Apply process system parameters In this section. Applies To—Source and Target Default Setting—The path to the InfoSphere CDC libraries and the database libraries when InfoSphere CDC was installed. you will learn about system parameters that adjust how InfoSphere CDC applies rows. This value is set during installation and should not be modified.“System parameters for InfoSphere CDC for Sybase (version 6.0 and below) 403 .

zero for numeric data types. a warning message may be generated in Event Log. Depending on the convertNotNullableMsg system parameter setting. No error message is generated in Event Log and replication continues. v ON—InfoSphere CDC will automatically insert an appropriate default value in the target column. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. column data. blank character for character data types.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for Sybase (version 6. Replication will continue or not based on whether the MirrorError or RefreshError system parameters are set to END or ON. See also: “convertNotNullableColumns” on page 317 “D_MIRROR_MIRROR_ERROR_STOP” on page 405 “D_MIRROR_REFRESH_ERROR_STOP” on page 359 “FILTER_NOCHANGE_UPDATES_FOR_AUDIT” on page 405 “NLS_LANG” on page 406 “TRANSACTION_GROUP_SIZE” on page 406 “TRANSACTION_INTERVAL” on page 407 “TRANSACTION_RECORDS_THRESHOLD” on page 407 “TRIM_CHAR_TO_VARCHAR” on page 407 “TRIM_VARCHAR_TO_VARCHAR” on page 408 “TRIM_TO_NULL” on page 408 convertNotNullableColumns Use this system parameter to indicate whether or not NULL values will be converted to default values when replicating data that contains NULL values to non-nullable target columns. The default value depends on the data type of the subscription column.Apply process system parameters Some system parameters adjust the way InfoSphere CDC applies rows. 1901-01-01 for date data types. and error handling. and so on. Applies To—Target Set this parameter to one of the following: v OFF—An error message will be generated in Event Log. For example.0 and below)” on page 399 Related reference “MirrorError” on page 318 “RefreshError” on page 318 “convertNotNullableMsg” on page 329 404 InfoSphere Change Data Capture Management Console: Administration Guide .

the row has been updated to the same value).2 and below)” on page 347 “System parameters for InfoSphere CDC for Sybase (version 6. Applies To—Source System parameters for InfoSphere CDC for Sybase (version 6. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. v OFF—Data refresh continues after an error has occurred. Applies To—Target Set this parameter to one of the following: v ON—Mirroring stops after an error has occurred.0 and below)” on page 399 Related reference “D_MIRROR_REFRESH_ERROR_STOP” on page 359 D_MIRROR_REFRESH_ERROR_STOP Use this system parameter to indicate whether or not InfoSphere CDC should continue to perform a refresh after encountering an error during a row insert operation. Applies To—Target Set this parameter to one of the following: v ON—Data refresh stops after an error has occurred. are replicated to the target table for any tables configured for LiveAudit replication.“D_MIRROR_MIRROR_ERROR_STOP” “D_MIRROR_REFRESH_ERROR_STOP” on page 359 D_MIRROR_MIRROR_ERROR_STOP Use this parameter to indicate whether or not mirroring continues after an error has occurred during a row insert. or update operation.0 and below)” on page 399 Related reference “D_MIRROR_REFRESH_ERROR_LIST” on page 359 “D_MIRROR_MIRROR_ERROR_STOP” FILTER_NOCHANGE_UPDATES_FOR_AUDIT Use this system parameter to indicate whether or not updates that have identical before and after column images (that is. delete. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. v OFF—Mirroring continues after an error has occurred.0 and below) 405 .

Set this parameter to one of the following: v OFF—If a row in a source table is updated to the same value. Applies To—Target Default Setting—500 Minimum Setting—0 Guidelines To increase the throughput. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. The COMMIT_LEVEL system parameter should be set to2 on the target 406 InfoSphere Change Data Capture Management Console: Administration Guide . Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. and TRANSACTION_RECORDS_THRESHOLDS system parameters together. preceded with a period. Note: Use this parameter only if InfoSphere CDC is running under commitment control.0 and below)” on page 399 NLS_LANG Use this system parameter to specify the database character set preceded with a period. v ON—If a row in a source table is updated to the same value. Use the TRANSACTION_GROUP_SIZE. For more information about setting this system parameter. Setting only one of these system parameters without the other can result in uncommitted transactions on the target. set to a number of transactions that would be received when busy during the TRANSACTION_INTERVAL. InfoSphere CDC replicates the value to the target table.0 and below)” on page 399 TRANSACTION_GROUP_SIZE Use this system parameter to specify the number of complete transactions applied to the database before InfoSphere CDC issues a commit. Applies To—Source and Target Default Setting—The database character set. only updates that change the column data are replicated to the target tables. For non-audit tables. InfoSphere CDC issues a commit after applying the number of transactions specified by the TRANSACTION_GROUP_SIZE. TRANSACTION_INTERVAL. see your IBM representative. corresponding to the language selected when the database was installed. This parameter only affects tables that are configured for LiveAudit replication. InfoSphere CDC does not replicate the value to the target table. or when the time interval specified by TRANSACTION_INTERVAL has elapsed.

database. If there are no transactions received by the target system.0 and below)” on page 399 TRANSACTION_RECORDS_THRESHOLD Use this system parameter to specify the maximum number of operations within a transaction or group of transactions before InfoSphere CDC issues a commit Applies To—Target Default Setting—3000 Minimum Setting—0 Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.0 and below)” on page 399 TRANSACTION_INTERVAL Use this system parameter to specify the time interval.0 and below)” on page 399 TRIM_CHAR_TO_VARCHAR Use this system parameter to specify whether or not trailing blank characters are trimmed from source columns of CHAR data type when replicating data to target columns of VARCHAR data type.0 and below) 407 . Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. or exceeded the time interval. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. or when the time interval specified by TRANSACTION_INTERVAL system parameter has elapsed. Setting only one of these system parameters without the other can result in uncommitted transactions on the target. Use this system parameter with the TRANSACTION_GROUP_SIZE system parameter. that can elapse between transactions before InfoSphere CDC issues a commit. InfoSphere CDC issues a commit after applying the number of transactions specified by the TRANSACTION_GROUP_SIZE system parameter. then InfoSphere CDC issues a commit immediately. and the MAINTAIN_TRANSACTION_CONSISTENCY system parameter should be set to ON on the source database. System parameters for InfoSphere CDC for Sybase (version 6. in seconds. Applies To—Target Default Setting—1 Minimum Setting—0 Guidelines InfoSphere CDC issues a commit only when a commit is received by the target system and you have reached the transaction group size. or exceeded the records threshold.

v ON—Trailing blanks are trimmed. If TRIM_TO_NULL =ON and the target column is nullable. For CHAR data mapped to VARCHAR columns. Applies To—Target Set this parameter to one of the following: v OFF—For data mapped to VARCHAR columns. v ON--Trailing blanks are trimmed. If TRIM_TO_NULL =ON and the target column is nullable. If TRIM_TO_NULL =OFF. Applies To—Target Set this parameter to one of the following: v OFF--Trailing blanks are not trimmed.0 and below)” on page 399 Related reference “TRIM_TO_NULL” TRIM_TO_NULL Use this system parameter to specify how source columns that contain blank characters only are handled during data replication. InfoSphere CDC inserts NULL in the column. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.Applies To—Target Set this parameter to one of the following: v OFF—Trailing blanks are not trimmed. For data mapped to CHAR columns.0 and below)” on page 399 Related reference “TRIM_TO_NULL” TRIM_VARCHAR_TO_VARCHAR Use this system parameter to specify whether or not trailing blank characters are trimmed from source columns of VARCHAR data type when replicating data to target columns of VARCHAR data type. InfoSphere CDC inserts NULL in the column. trailing blanks are trimmed or not to a single blank depending on the TRIM_CHAR_TO_VARCHAR and TRIM_VARCHAR_TO_VARCHAR system parameters. v ON—For data mapped to CHAR columns. if TRIM_CHAR_TO_VARCHAR =ON and the target column is nullable. InfoSphere CDC inserts NULL in the column. if the target column is nullable. setting this parameter to OFF has no effect. Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. InfoSphere CDC inserts a single blank character in the target column. InfoSphere CDC inserts a single blank character in the target column. For VARCHAR 408 InfoSphere Change Data Capture Management Console: Administration Guide . If TRIM_TO_NULL =OFF. InfoSphere CDC inserts NULL in the column.

See also: “PREVENT_RECURSION” PREVENT_RECURSION Use this parameter to indicate whether or not to prevent cascading replication for bi-directional configurations.0 and below)” on page 399 Related reference “TRIM_CHAR_TO_VARCHAR” on page 407 “TRIM_VARCHAR_TO_VARCHAR” on page 408 Cascading replication system parameters Cascading replication system parameters control InfoSphere CDC cascading replication. Applies To—Source Set this parameter to one of the following: v ON—Changes applied by InfoSphere CDC are not be replicated back to the source database from where it came from. if TRIM_VARCHAR_TO_VARCHAR =ON and the target column is nullable. If the target column is non-nullable. TRIM_ parameter settings TRIM_CHAR_ TO_ VARCHAR ON ON OFF OFF ON ON OFF OFF TRIM_ VARCHAR_ TO_ VARCHAR ON OFF ON OFF ON OFF ON OFF TRIM_ TO_ NULL ON ON ON ON OFF OFF OFF OFF Target data CHAR to VARCHAR NULL NULL Source data Source data VARCHAR to VARCHAR NULL Source data NULL Source data Any data type to CHAR NULL NULL NULL NULL Blanks Blanks Blanks Blanks Single blank Single blank Single blank Source data Source data Source data Single blank Source data Default Setting—OFF Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. The table below explains how the TRIM_ system parameters affect the data replicated to the target for source columns that contain blank characters only.0 and below) 409 .data mapped to VARCHAR columns. System parameters for InfoSphere CDC for Sybase (version 6. source columns that contain blank characters only are handled according to the convertNotNullableColumns system parameter. InfoSphere CDC inserts NULL in the column.

the target may commit all three operations as part of a single transaction. The InfoSphere CDC apply process groups transactions on the target to reduce the workload. when there are no journal entries to be processed pertaining to the current subscription.v OFF—Changes made by InfoSphere CDC are replicated. the target can reflect more accurately how far replication has progressed.0 and below)” on page 399 Maximize throughput system parameters InfoSphere CDC system parameters allow you to significantly reduce the workload of the target database during mirroring. The value of this parameter affects the information that is displayed in progress and bookmark messages.0 and below)” on page 399 Database journal (trigger) system parameters Database journal or trigger system parameters let you manage the InfoSphere CDC journal table. Default Setting—5 Minimum Setting—1 Maximum Setting—300 Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. except when filtered out by the CASCADE_OMIT_TARGETS system parameter. See also: “REPORT_POSITION_INTERVAL” REPORT_POSITION_INTERVAL Use this system parameter to specify how often (in seconds) the source informs the target about its position in the current journal during times of no activity. However. the source informs the target of its current position so that the target can advance its bookmarks accordingly. it may not perform every commit that was done on the source. During times of no activity. By specifying a low setting for this parameter. Default Setting—ON Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. you can use this system parameter to prevent InfoSphere CDC from rereading entries that do not apply to the current replication configuration. Every commit on the target database will correspond with a commit on the target. You can use this grouping of 410 InfoSphere Change Data Capture Management Console: Administration Guide . For example. if the source does three small transactions containing one operation each. Applies To—Source After a shutdown and restart. A high value for this parameter may result in information that is not up-to-date being displayed.

InfoSphere CDC issues a commit on the target when the transaction that contains the rows completes. If a rollback occurs. InfoSphere CDC rolls back all outstanding rows in the commit group. Use the COMMIT_GROUP_SIZE and COMMIT_INTERVAL system parameters together. See also: “COMMIT_GROUP_SIZE” “COMMIT_INTERVAL” on page 412 “SYNCHRONIZATION_COMMIT_ GROUP_SIZE” on page 412 “SYNCHRONIZATION_INTERVAL” on page 413 COMMIT_GROUP_SIZE Use this system parameter to specify the minimum number of rows InfoSphere CDC should apply to the database before a commit is issued.system parameters to significantly reduce the resources required by the target database.2 and below)” on page 347 “System parameters for InfoSphere CDC for Sybase (version 6. Since InfoSphere CDC is set to continue on error. Related concepts “System parameters for InfoSphere CDC for Oracle (version 6. you can adjust the settings appropriately.0 and below)” on page 399 Related reference “COMMIT_INTERVAL” on page 369 “COMMIT_LEVEL” on page 368 “D_MIRROR_MIRROR_ERROR_STOP” on page 358 “COMMIT_INTERVAL” on page 412 “D_MIRROR_MIRROR_ERROR_STOP” on page 405 System parameters for InfoSphere CDC for Sybase (version 6.0 and below) 411 . Guidelines Set this parameter to 0 if “D_MIRROR_MIRROR_ERROR_STOP” on page 405=OFF. InfoSphere CDC does not use commit groups to apply data to the target. but if your target system has limited resources and an increase in latency is acceptable. you may lose data. or when the time interval specified by COMMIT_INTERVAL has elapsed. The default settings are appropriate for most databases. Applies To—Target Default Setting—5000 Minimum Setting—0. InfoSphere CDC issues a commit when either when the number of rows specified by COMMIT_GROUP_SIZE has been applied to the target. Note: Use this parameter only if InfoSphere CDC is not running under commitment control (COMMIT_LEVEL =0). Setting only one of these system parameters without the other can result in uncommitted data on the target.

Applies To—Target Default Setting—60 Minimum Setting—0. InfoSphere CDC issues a commit on the target database for transactions that completed within that time interval. Setting only one of these system parameters without the other can result in uncommitted data on the target. or when the time interval specified by COMMIT_INTERVAL has elapsed. Note: Use this parameter only if InfoSphere CDC is not running under commitment control (COMMIT_LEVEL =0). Guidelines Set this parameter to 0 if “D_MIRROR_MIRROR_ERROR_STOP” on page 405=OFF. InfoSphere CDC issues a commit on a target database for each completed transaction. whichever comes first. When the COMMIT_INTERVAL time expires. InfoSphere CDC issues a commit when either when the number of rows specified by COMMIT_GROUP_SIZE has been applied to the target. you may lose data. in seconds. Synchronization occurs either when the number of transactions (specified by SYNCRONIZATION_COMMIT_GROUP_SIZE) have been applied or when the time interval (specified by SYNCHRONIZATION_INTERVAL) has elapsed. If a rollback occurs. Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. Default Setting—128 412 InfoSphere Change Data Capture Management Console: Administration Guide . to limit the number of commits InfoSphere CDC issues on the target database.0 and below)” on page 399 Related reference “COMMIT_GROUP_SIZE” on page 411 “D_MIRROR_MIRROR_ERROR_STOP” on page 405 SYNCHRONIZATION_COMMIT_ GROUP_SIZE Use this system parameter to specify the number of transactions applied to the database before InfoSphere CDC performs synchronization between the source and target. InfoSphere CDC rolls back all outstanding rows in the commit group. Use the COMMIT_GROUP_SIZE and COMMIT_INTERVAL system parameters together. Applies To—Source The SYNCRONIZATION_COMMIT_GROUP_SIZE and SYNCHRONIZATION_INTERVAL system parameters are intended to be used together.COMMIT_INTERVAL Use this system parameter to specify the time interval between commits. Since InfoSphere CDC is set to continue on error.

Applies To—Source The SYNCRONIZATION_INTERVAL and SYNCHRONIZATION_COMMIT_ GROUP_SIZE system parameters are intended to be used together.0 and below)” on page 399 Related reference “SYNCHRONIZATION_COMMIT_ GROUP_SIZE” on page 412 Tracing system parameters Tracing system parameters let you perform diagnostic activities with InfoSphere CDC.648 (maximum integer) Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. Synchronization is achieved when the target reports to the source the position of the last committed change. Maximum Setting—2.0 and below) 413 .483. whichever comes first.0 and below)” on page 399 Related reference “SYNCHRONIZATION_INTERVAL” SYNCHRONIZATION_INTERVAL Use this system parameter to specify the interval. Default Setting—1 Minimum Setting—1 Maximum Setting—300 Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.147. Synchronization occurs either when the number of transactions (specified by SYNCHRONIZATION_COMMIT_ GROUP_SIZE ) have been applied or when the time interval (specified by SYNCRONIZATION_INTERVAL) has elapsed.Minimum Setting—0. at which synchronization is performed between the source and target. See also: “D_MIRROR_TRACE” on page 414 “D_MIRROR_TRACE_FILE_SIZE” on page 414 “D_MIRROR_TRACE_ON_ERROR” on page 414 System parameters for InfoSphere CDC for Sybase (version 6. InfoSphere CDC does not use commit groups to perform synchronization. in seconds.

InfoSphere CDC starts overwriting the first file.D_MIRROR_TRACE Use this system parameter to indicate whether or not tracing is enabled. These trace files are encrypted. also set the size of the trace file to an appropriate value using the D_MIRROR_TRACE_FILE_SIZE system parameter. Applies To—Source and Target Set this parameter to one of the following: v OFF—Tracing is disabled.0 and below)” on page 399 Related reference “D_MIRROR_TRACE_FILE_SIZE” D_MIRROR_TRACE_FILE_SIZE Use this system parameter to specify the maximum size of a trace file in bytes. InfoSphere CDC creates a second file. IBM recommends setting the size of the trace file to a value that is not too high. When the second trace file reaches its maximum size.000. When the first trace file reaches its maximum size. Default Setting—OFF Dynamic—Yes Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. When enabling this setting. 414 InfoSphere Change Data Capture Management Console: Administration Guide .000 bytes Minimum Setting—1. InfoSphere CDC creates two trace files.000 bytes Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.000. v ON—Tracing is enabled and InfoSphere CDC creates the appropriate trace files in the log directory. and are meant to be sent to IBM technical support for troubleshooting purposes. This setting has no effect when D_MIRROR_TRACE_ON_ERROR=ON.0 and below)” on page 399 D_MIRROR_TRACE_ON_ERROR Use this system parameter to specify whether or not InfoSphere CDC enables tracing automatically when an error occurs. Applies To—Source and Target Default Setting—10. To avoid disk space problems. Applies To—Source and Target Set this parameter to one of the following: v OFF—InfoSphere CDC does not enable tracing when an error occurs.

To avoid disk space problems. Default Setting—OFF Related concepts System parameters for InfoSphere CDC for Sybase (version 6. Default Setting—OFF Dynamic—Yes (on the target only) Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. InfoSphere CDC creates the appropriate trace files in the InfoSphere CDC log directory. Set this parameter to one of the following: v OFF—No warning message is generated in Event Log. These trace files are encrypted. v ON—A warning message is generated in Event Log each time a NULL value is converted to a default value. Applies To—Target This system parameter applies only when convertNotNullableColumns=ON. IBM recommends setting the size of the trace file to a value that is not too high.v ON—InfoSphere CDC enables tracing when an error occurs. and are meant to be sent to IBM technical support for troubleshooting purposes. When enabling this setting. also set the size of the trace file to an appropriate value using the D_MIRROR_TRACE_FILE_SIZE system parameter.0 and below)” on page 399 Related reference “D_MIRROR_TRACE_FILE_SIZE” on page 414 Notification system parameters Notification system parameters let you control if you should generate InfoSphere CDC messages in the Event Log for specific events. Otherwise. this parameter has no effect. See also: “convertNotNullableMsg” on page 329 “DEADBAND_PERCENTAGE” on page 416 “DM_STATUS_INTERVAL” on page 418 “HEARTBEAT_TIMEOUT” on page 418 “LOG_EMAIL_USERNAME” on page 419 “MONITOR_SAMPLE_INTERVAL” on page 419 “STATISTICS_INTERVAL” on page 420 convertNotNullableMsg Use this system parameter to indicate whether or not a warning message will be generated in Event Log each time data that contains NULL values is converted to default values for non-nullable target columns.0 and below) 415 .

Given sample latency over a ten minute period where latency is calculated every minute. Based on latency thresholds defined. three latency messages are generated. A latency message is generated only when latency has risen above the upper limit of the range or fallen below the lower limit of the range. which is expressed as a percentage.5 minutes (rounded up to 1 minute) v Padding is rounded up or down to the nearest whole minute: – Upper limit of range = 5 minutes + 1 minute (padding) = 6 minutes – Lower limit of range = 5 minutes . The following calculations are performed to determine the lower and upper limits (in minutes) of the range around the threshold: v Padding = 10% of 5 minutes = 0. a latency message will be generated only when latency rises above 6 minutes or falls below 4 minutes. allows you to pad a threshold equally on both sides to create a range around the threshold. you can control the number of latency messages placed in Event Log. This system parameter. By changing the value assigned to this system parameter. and the threshold itself can be made thicker or thinner. By adjusting this system parameter.“System parameters for InfoSphere CDC for Microsoft SQL Server (version 5. a latency message is generated when latency has risen above or fallen below a threshold. A 10% range is applied around the 5 minute threshold. This graph illustrates latency message generation with the DEADBAND_PERCENTAGE value set to 10%: 416 InfoSphere Change Data Capture Management Console: Administration Guide .0 and below)” on page 399 Related reference “convertNotNullableColumns” on page 317 “DM_STATUS_INTERVAL” on page 330 “Heartbeat Timeout” on page 331 “InvalidNumericMsg” on page 331 DEADBAND_PERCENTAGE Applies To—Target Identifies the size of the range around each latency threshold setting. where the interval is the current setting for the MONITOR_SAMPLE_INTERVAL system parameter.1 minute (padding) = 4 minutes As a result. You can set notifications in response to a generated latency message. For example. Latency is calculated at regular intervals. the size of the range around the threshold can be increased or decreased.3 and below)” on page 313 “Setting system parameters on source and target datastores” on page 60 “System parameters for InfoSphere CDC for Sybase (version 6. assume that a latency threshold is 5 minutes and this system parameter is set to 10.

Therefore. five latency messages are generated when this system parameter is set to 3.If this DEADBAND_PERCENTAGE is set to 3 (the default setting) for the same example. Based on the same sample latency in the previous graph where latency is calculated every minute. This graph illustrates latency message generation with the DEADBAND_PERCENTAGE value set to 3%: If the number of latency messages generated over the ten minute period for the 10% (3 latency messages) and 3% (5 latency messages) settings are averages.0 and below) 417 . a latency message is generated each time latency crosses over the latency threshold of 5 minutes. an additional 288 latency messages would be generated each day if this system parameter is not changed from its default setting to 10%. System parameters for InfoSphere CDC for Sybase (version 6. no padding is applied to the latency threshold.

Since there are two latency thresholds that you can set (a warning threshold and a problem threshold). and the two ranges can overlap with no change in behavior. No progress notifications will be issued.0 and below)” on page 399 “Setting latency thresholds and notifications” on page 78 “Disk resource system parameters” on page 420 DM_STATUS_INTERVAL Use this system parameter to specify how often progress messages should be issued in seconds. internal heartbeat messages are sent regularly between the source and the target to determine communications and process status. Minimum Setting—0 seconds. Heartbeat is a feature that manages InfoSphere CDC processes when a problem with communications or a process has been detected through the absence of communications over a specified period of time. Applies To—Source and Target Note: Low values of this parameter may result in many messages displayed in Event Log. If a reply to a message is not received by the source or target within the specified timeout interval. messages (message identifiers 2612 and 3165) are placed in Event Log when heartbeat timeouts occur. Default Setting—0 seconds. the default setting is used. each range is attached to its threshold. In addition. Maximum Setting—7200 seconds Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. 418 InfoSphere Change Data Capture Management Console: Administration Guide . Default Setting—3% Minimum Setting—3% Maximum Setting—10% Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. No progress notifications will be issued. These messages are displayed in Event Log to indicate how replication is advancing and to provide detailed information about InfoSphere CDC replication activities. For each active subscription.0 and below)” on page 399 HEARTBEAT_TIMEOUT Use this parameter to specify the number of minutes of communication inactivity to wait before active InfoSphere CDC processes for a subscription are stopped. In this case. In this situation. and attempts to stop all its source and target processes for the subscription. two separate ranges are defined when padding is at least one minute. then InfoSphere CDC determines that a problem has occurred. clear Event Log on a regular basis. If a value outside the acceptable range is specified.

this setting also represents how often the storage area is sampled to determine whether or not latency has risen above or fallen below specified threshold settings. Management Console references this area to present replication latency information. in seconds.0 and below) 419 . If a value larger than the maximum setting is specified.0 and below)” on page 399 “Displaying event messages during replication” on page 232 LOG_EMAIL_USERNAME Use this system parameter to specify the user name that receives email messages in response to invoking the dmreadlog command or the warning message that is generated when Event Log exceeds the threshold value set by the LOG_MAX_SIZE system parameter. the minimum setting is used. Default Setting—The InfoSphere CDC account (UNIX user) specified when InfoSphere CDC was installed Related concepts “System parameters for InfoSphere CDC for Sybase (version 6. the value assigned to this parameter is a comma-separated list of user names. The value of this parameter cannot exceed 30 bytes in length. the maximum setting is used.Applies To—Source Default Setting—15 minutes Minimum Setting—3 minutes Maximum Setting—999 minutes Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.0 and below)” on page 399 Related reference “STATISTICS_INTERVAL” on page 420 MONITOR_SAMPLE_INTERVAL Use this system parameter to identify the period of time. you can set latency notifications. InfoSphere CDC generates latency messages when latency rises above or falls below the thresholds. Applies To—Source and Target On the target. Default Setting—5 seconds System parameters for InfoSphere CDC for Sybase (version 6. set this parameter to NOMAIL. between consecutive updates to a storage area that is used to maintain replication latency metrics. In response to a generated message. If a value smaller than the minimum setting is specified. Applies To—Source and Target In UNIX environments. To suppress all email messages.

Maximum Setting—2. set this parameter to NOMAX. InfoSphere CDC does not provide statistics information. Default Setting—0. Replication latency metrics are not updated. Applies To—Source and Target Note: Use this parameter only if advised by IBM technical support. Maximum Setting—3600 seconds Related concepts “System parameters for InfoSphere CDC for Sybase (version 6.Minimum Setting—0 seconds. if you are ab