InfoSphere CDC for Teradata (Version 10.2) 4About InfoSphere CDC 7System requirements for InfoSphere CDC for Teradata 10Hardware and software requirements 11Supported Teradata JDBC drivers and utilities 12Running in a virtualization environment 13Disk space requirements 14RAM requirements 15Port requirements 16Before you install InfoSphere CDC for Teradata 17Required database, user accounts, and directories 18Hardware requirements 19Apply mode methods 20Assessing disk space and memory requirements 21Understanding the importance of an appropriately configured disk subsystem 22Understanding the InfoSphere CDC memory footprint 23Calculating database connections required by InfoSphere CDC for Teradata 24Conflict detection and resolution 25Creating queues in JMS providers 26Installing or upgrading InfoSphere CDC for Teradata 27Installing InfoSphere CDC for Teradata using an interactive installation 28To install InfoSphere CDC for Teradata (Windows) 29To install InfoSphere CDC for Teradata (UNIX) 30Installing InfoSphere CDC for Teradata using a silent installation 31To perform a silent installation of InfoSphere CDC for Teradata (UNIX) 32Upgrading InfoSphere CDC for Teradata 33To upgrade InfoSphere CDC for Teradata (Windows) 35To upgrade InfoSphere CDC for Teradata (UNIX and Linux) 36Configuring InfoSphere CDC for Teradata (Windows) 38Configuring InfoSphere CDC for Teradata instances (Windows) 39To add a new instance of InfoSphere CDC for Teradata (Windows) 40To edit an instance of InfoSphere CDC for Teradata (Windows) 45To delete an instance of InfoSphere CDC for Teradata (Windows) 46Configuring InfoSphere CDC for Teradata (UNIX) 47Configuring InfoSphere CDC for Teradata instances (UNIX and Linux) 48To add a new instance of InfoSphere CDC for Teradata (UNIX) 49To edit an instance of InfoSphere CDC for Teradata (UNIX) 51To delete an instance of InfoSphere CDC for Teradata (UNIX) 52After you install and configure InfoSphere CDC for Teradata 53Starting InfoSphere CDC for Teradata 54To start InfoSphere CDC for Teradata (Windows) 55To start InfoSphere CDC for Teradata (UNIX) 56Stopping InfoSphere CDC for Teradata 57To stop InfoSphere CDC for Teradata (Windows) 58To stop InfoSphere CDC for Teradata (UNIX) 59Maintaining active TCP connections in a network environment 60To maintain active TCP connections 61

Enabling SQL statements in Management Console 62To enable SQL statements in Management Console 63Configuring the Teradata TPump utility 64Teradata TPump restrictions and limitations 65Concurrent load tasks in Teradata 67Teradata TPump error handling and recovery 68To configure error handling in TPump 69Customizing the Teradata TPump script file 70To customize the TPump script file 71Table-level customization 73Journaling before and after images 74InfoSphere CDC for Teradata metadata tables 75Data types supported by InfoSphere CDC for Teradata 76System parameters for InfoSphere CDC for Teradata 77Commands for InfoSphere CDC for Teradata 78Using the InfoSphere CDC for Teradata commands 79Setting the TSINSTANCE environment variable 80Database transaction log commands 81dmshowbookmark - Display bookmark information 82Exporting and importing configuration commands 84dmexportconfiguration - Export InfoSphere CDC Configuration 85dmimportconfiguration - Import InfoSphere CDC Configuration 86Managing tables for replication commands 87dmreassigntable - Update target table definition 88Monitoring replication commands 89dmclearevents - Clear events 90dmshowevents - Display InfoSphere CDC events 91Other commands 93dmbackupmd - Back up metadata 94dmconfigurets - Configure InfoSphere CDC 95dmset - Set InfoSphere CDC system parameter 96dmshowversion - Show InfoSphere CDC version 97dmshutdown - Shut down InfoSphere CDC 98dmsupportinfo - Collect IBM Support information 100dmts32 - Start InfoSphere CDC 102dmts64 - Start InfoSphere CDC 103dmmdcommander 104dmmdconsole 105User exits for InfoSphere CDC for Teradata 106Stored procedure user exits for table and row level operations 107Defining a stored procedure user exit 108Stored procedure user exit database connections 109Retrieving data with a stored procedure user exit 110Retrieving system values using the s$ prefix 111Retrieving journal control fields using the j$ prefix 114Retrieving data values using b$, a$, k$, and d$ prefixes 117Example of a stored procedure user exit 120

Sample Java class user exits for InfoSphere CDC for Teradata 122To compile the sample Java class user exits (Windows) 123InfoSphere CDC API reference - Javadocs 124Uninstalling InfoSphere CDC for Teradata 125To uninstall InfoSphere CDC for Teradata (Windows) 126To uninstall InfoSphere CDC for Teradata (UNIX and Linux) 127Troubleshooting 128Using the IBM Support Assistant (ISA DC) 129To use ISA DC to collect data for a product problem (command line) 130To use ISA DC to collect data for a product problem (GUI) 133To use ISA DC to collect data for a question or an enhancement request (command line) 135To use ISA DC to collect data for a question or an enhancement request (GUI) 137Locating log files 138Troubleshooting and contacting IBM Support 139

-

-

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 About InfoSphere CDC IBM®InfoSphere® Change Data Capture (InfoSphere CDC) is a replication solutionthat captures database changes as they happen and delivers them to targetdatabases, message queues, or an ETL solution such as InfoSphere DataStage®based on table mappings configured in the InfoSphere CDCManagement ConsoleGUI application. InfoSphere CDC provides low impact capture and fast delivery of data changes forkey information management initiatives including dynamic data warehousing, masterdata management, application consolidations or migrations, operational BI, andenabling SOA projects. InfoSphere CDC also helps reduce processing overheadsand network traffic by only sending the data that has changed. Replication can becarried out continuously or periodically. When data is transferred from a sourceserver, it can be remapped or transformed in the target environment. The following diagram illustrates the key components of InfoSphere CDC.

The key components of the InfoSphere CDC architecture are described below:

Access Server—Controls all of the non-command line access to the replicationenvironment. When you log in to Management Console, you are connecting toAccess Server. Access Server can be closed on the client workstation withoutaffecting active data replication activities between source and target servers.Admin API—Operates as an optional Java™-based programming interface thatyou can use to script operational configurations or interactions.Apply agent—Acts as the agent on the target that processes changes as sent bythe source.Command line interface—Allows you to administer datastores and useraccounts, as well as to perform administration scripting, independent ofManagement Console.Communication Layer (TCP/IP)—Acts as the dedicated network connectionbetween the Source and the Target.

4

-

-

-

-

-

-

-

-

-

-

-

-

Source and Target Datastore—Represents the data files and InfoSphere CDCinstances required for data replication. Each datastore represents a database towhich you want to connect and acts as a container for your tables. Tables madeavailable for replication are contained in a datastore. Management Console—Allows you to configure, monitor and manage replicationon various servers, specify replication parameters, and initiate refresh andmirroring operations from a client workstation. Management Console also allowsyou to monitor replication operations, latency, event messages, and other statisticssupported by the source or target datastore. The monitor in Management Consoleis intended for time-critical working environments that require continuous analysisof data movement. After you have set up replication, Management Console can beclosed on the client workstation without affecting active data replication activitiesbetween source and target servers.Metadata—Represents the information about the relevant tables, mappings,subscriptions, notifications, events, and other particulars of a data replicationinstance that you set up.Mirror—Performs the replication of changes to the target table or accumulation ofsource table changes used to replicate changes to the target table at a later time. Ifyou have implemented bidirectional replication in your environment, mirroring canoccur to and from both the source and target tables.Refresh—Performs the initial synchronization of the tables from the sourcedatabase to the target. This is read by the Refresh reader.Replication Engine—Serves to send and receive data. The process that sendsreplicated data is the Source Capture Engine and the process that receivesreplicated data is the Target Engine. An InfoSphere CDC instance can operate asa source capture engine and a target engine simultaneously.Single Scrape—Acts as a source-only log reader and a log parser component. Itchecks and analyzes the source database logs for all of the subscriptions on theselected datastore. Not all InfoSphere CDC engines use Single Scrape. ForInfoSphere CDC for DB2® for i, there is a Scraper job (that acts as a log reader)and a Mirror job that performs the function of mirroring (see Mirror above). Source transformation engine—Processes row filtering, critical columns, columnfiltering, encoding conversions, and other data to propagate to the target datastoreengine.Source database logs—Maintained by the source database for its own recoverypurposes. The InfoSphere CDC log reader inspects these in the mirroring process,but filters out the tables that are not in scope for replication. Target transformation engine—Processes data and value translations, encodingconversions, user exits, conflict detections, and other data on the target datastoreengine.

There are two types of target-only destinations for replication that are notdatabases:

JMS Messages—Acts as a JMS message destination (queue or topic) for row-level operations that are created as XML documents.InfoSphere DataStage—Processes changes delivered from InfoSphere CDC thatcan be used by InfoSphere DataStage jobs.

5

Related information: Supported sources and targets

6

-

-

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 About InfoSphere CDC IBM®InfoSphere® Change Data Capture (InfoSphere CDC) is a replication solutionthat captures database changes as they happen and delivers them to targetdatabases, message queues, or an ETL solution such as InfoSphere DataStage®based on table mappings configured in the InfoSphere CDCManagement ConsoleGUI application. InfoSphere CDC provides low impact capture and fast delivery of data changes forkey information management initiatives including dynamic data warehousing, masterdata management, application consolidations or migrations, operational BI, andenabling SOA projects. InfoSphere CDC also helps reduce processing overheadsand network traffic by only sending the data that has changed. Replication can becarried out continuously or periodically. When data is transferred from a sourceserver, it can be remapped or transformed in the target environment. The following diagram illustrates the key components of InfoSphere CDC.

The key components of the InfoSphere CDC architecture are described below:

Access Server—Controls all of the non-command line access to the replicationenvironment. When you log in to Management Console, you are connecting toAccess Server. Access Server can be closed on the client workstation withoutaffecting active data replication activities between source and target servers.Admin API—Operates as an optional Java™-based programming interface thatyou can use to script operational configurations or interactions.Apply agent—Acts as the agent on the target that processes changes as sent bythe source.Command line interface—Allows you to administer datastores and useraccounts, as well as to perform administration scripting, independent ofManagement Console.Communication Layer (TCP/IP)—Acts as the dedicated network connectionbetween the Source and the Target.

7

-

-

-

-

-

-

-

-

-

-

-

-

Source and Target Datastore—Represents the data files and InfoSphere CDCinstances required for data replication. Each datastore represents a database towhich you want to connect and acts as a container for your tables. Tables madeavailable for replication are contained in a datastore. Management Console—Allows you to configure, monitor and manage replicationon various servers, specify replication parameters, and initiate refresh andmirroring operations from a client workstation. Management Console also allowsyou to monitor replication operations, latency, event messages, and other statisticssupported by the source or target datastore. The monitor in Management Consoleis intended for time-critical working environments that require continuous analysisof data movement. After you have set up replication, Management Console can beclosed on the client workstation without affecting active data replication activitiesbetween source and target servers.Metadata—Represents the information about the relevant tables, mappings,subscriptions, notifications, events, and other particulars of a data replicationinstance that you set up.Mirror—Performs the replication of changes to the target table or accumulation ofsource table changes used to replicate changes to the target table at a later time. Ifyou have implemented bidirectional replication in your environment, mirroring canoccur to and from both the source and target tables.Refresh—Performs the initial synchronization of the tables from the sourcedatabase to the target. This is read by the Refresh reader.Replication Engine—Serves to send and receive data. The process that sendsreplicated data is the Source Capture Engine and the process that receivesreplicated data is the Target Engine. An InfoSphere CDC instance can operate asa source capture engine and a target engine simultaneously.Single Scrape—Acts as a source-only log reader and a log parser component. Itchecks and analyzes the source database logs for all of the subscriptions on theselected datastore. Not all InfoSphere CDC engines use Single Scrape. ForInfoSphere CDC for DB2® for i, there is a Scraper job (that acts as a log reader)and a Mirror job that performs the function of mirroring (see Mirror above). Source transformation engine—Processes row filtering, critical columns, columnfiltering, encoding conversions, and other data to propagate to the target datastoreengine.Source database logs—Maintained by the source database for its own recoverypurposes. The InfoSphere CDC log reader inspects these in the mirroring process,but filters out the tables that are not in scope for replication. Target transformation engine—Processes data and value translations, encodingconversions, user exits, conflict detections, and other data on the target datastoreengine.

There are two types of target-only destinations for replication that are notdatabases:

JMS Messages—Acts as a JMS message destination (queue or topic) for row-level operations that are created as XML documents.InfoSphere DataStage—Processes changes delivered from InfoSphere CDC thatcan be used by InfoSphere DataStage jobs.

8

Related information: Supported sources and targets

9

------

IBM InfoSphere Change Data Capture, Version 10.2 System requirements for InfoSphere CDC forTeradata Before you install InfoSphere® CDC, ensure that the system you choose meets thenecessary operating system, hardware, software, communications, disk, andmemory requirements. In this section, you will learn:

Hardware and software requirements Supported Teradata JDBC drivers and utilities Running in a virtualization environment Disk space requirements RAM requirements Port requirements

10

IBM InfoSphere Change Data Capture, Version 10.2 Hardware and software requirements Click the following links to view hardware and software requirements forInfoSphere® CDC, Management Console, and Access Server: Linux, UNIX, Windows and System i® replication engines: https://ibm.biz/BdxyzE Mainframe replication engine: https://ibm.biz/Bdxyd5 Related concepts: Disk space requirements RAM requirements Port requirements

11

IBM InfoSphere Change Data Capture, Version 10.2 Supported Teradata JDBC drivers and utilities

Teradata JDBC driver Teradata utilityTeradata JDBC driver, version13.00.00.06

Both of the following:Teradata TPump,version 13.10.00.001Teradata FastLoad,version 13.10.00.001

Teradata JDBC driver, version14.00.00.01

Both of the following:Teradata TPump,version 14.00.00.001Teradata FastLoad,version 14.00.00.001

12

IBM InfoSphere Change Data Capture, Version 10.2 Running in a virtualization environment The InfoSphere® CDC products adhere to the Virtualization Policy for IBM®Software and can be run in any virtualization environment for only the supportedoperating systems and versions listed specifically within IBMInfoSphere DataReplication System Requirements. For more information on the policy, see http://www-01.ibm.com/software/support/virtualization_policy.html

13

IBM InfoSphere Change Data Capture, Version 10.2 Disk space requirements

Disk spaceInfoSphere® CDC target system:50 GB—For installation files, dataqueues, log files, and Teradata TPump utility files.Global diskquota—Disk space is required on your target system for this quotawhich is used to store LOB data received from your InfoSphereCDC source system. The amount of disk space required isdetermined by your replication environment and the amount ofLOB data you are replicating. To improve performance, InfoSphereCDC will only persist LOB data to disk if RAM is not available onyour target system. Use the mirror_global_disk_quota_gb systemparameter to configure the amount of disk space used by thisquota.

14

IBM InfoSphere Change Data Capture, Version 10.2 RAM requirements

Although InfoSphere CDC memory requirements will fluctuate, you must work withyour system administrator to ensure the allocated memory for each instance of theproduct is available at all times. This may involve deployment planning since otherapplications with memory requirements may be installed on the same server withInfoSphere CDC. Using values other than the defaults or allocating more RAM thanis physically available on your server should only be undertaken after consideringthe impacts on product performance. Related concepts: Configuring InfoSphere CDC for Teradata (Windows) Configuring InfoSphere CDC for Teradata (UNIX)

RAMEach instance of InfoSphere® CDC requires memory for theJava™ Virtual Machine (JVM). The following default values formemory are assigned:1024 MB of RAM —Default value for each 64-bit instance ofInfoSphere CDC. 512 MB of RAM—Default value for each 32-bitinstance of InfoSphere CDC.Use the InfoSphere CDCconfiguration tool to configure the memory for each instance ofInfoSphere CDC.

15

IBM InfoSphere Change Data Capture, Version 10.2 Port requirements InfoSphere® CDC requires that you allocate a port for communication with clientworkstations running Management Console and other servers. The port must beaccessible through a firewall, although you do not require access to the Internet.

Related concepts: Maintaining active TCP connections in a network environment

Protocol Default port PurposeTCP 10701 Accepts connections

from:ManagementConsoleOtherinstallations ofInfoSphere CDC as asource ofreplicationCommandline utilities

16

---------

IBM InfoSphere Change Data Capture, Version 10.2 Before you install InfoSphere CDC for Teradata This section contains information on the tasks that you must complete beforeinstalling InfoSphere® CDC. This section assumes that you have met all of thehardware, software, database, and port requirements. You must complete all of thetasks below before installing InfoSphere CDC. In this section, you will learn:

Required database, user accounts, and directories Hardware requirements Apply mode methods Assessing disk space and memory requirements Understanding the importance of an appropriately configured disk subsystem Understanding the InfoSphere CDC memory footprint Calculating database connections required by InfoSphere CDC for Teradata Conflict detection and resolution Creating queues in JMS providers

17

IBM InfoSphere Change Data Capture, Version 10.2 Required database, user accounts, and directories Configuring a Teradata database When you configure InfoSphere® CDC, you are prompted for the name of theTeradata database you want InfoSphere CDC to connect to and replicate data.Before installing InfoSphere CDC, ensure that this Teradata database exists andthat you have created and set up a database user that has access to it. Setting up a Teradata user account For InfoSphere CDC to connect to your Teradata database, you need to create aTeradata user account. When you configure InfoSphere CDC, you are prompted forthe name of the Teradata database you want InfoSphere CDC to connect to and theuser name and password of the Teradata user that has access to this database. TheTeradata user account should have select access to DBC. Creating directories for Teradata FastLoad files Create or decide on the directory you want to use for the FastLoad utility inTeradata. Both your InfoSphere CDC user and your database must have read andwrite permissions for this directory. Use a different directory for each instance ofInfoSphere CDC.

18

IBM InfoSphere Change Data Capture, Version 10.2 Hardware requirements You need to allocate a machine on which you can install InfoSphere® CDC forTeradata. You cannot install InfoSphere CDC on the Teradata applicance. The following diagram illustrates a typical topology for the InfoSphere CDC forTeradata product:

19

-

-

IBM InfoSphere Change Data Capture, Version 10.2 Apply mode methods InfoSphere® CDC for Teradata will support fast apply modes when JDBC apply isused. However, InfoSphere CDC for Teradata will not support fast apply modeswhen TPUMP apply is used. Encoding considerations for native apply utilities When using either the TPUMP utility or FastLoad utility for refresh or mirroring, youneed to ensure that target tables do not have mixed encodings. The encodings mustbe identical between the source and target tables. You must also ensure that thefollowing system parameters are set according to the target table default encoding:

If the target table encoding is Latin, ensure that the mbcs_support_is_on systemparameter is set to false.If the target table encoding is Unicode, ensure that the mbcs_support_is_onsystem parameter is set to true.

Related information: mbcs_support_is_on

20

IBM InfoSphere Change Data Capture, Version 10.2 Assessing disk space and memory requirements InfoSphere® CDC requires disk space and memory when it processes change datafrom your source database. In order to process change data efficiently and replicatethese changes to your target system, it is very important that InfoSphere CDC hasadequate disk space and memory for each of the components described in thissection. Memory requirements for the JVM (Java Virtual Machine) As a Java-based product, InfoSphere CDC requires you to allocate the maximumamount of memory (RAM) to be used by the Java™ Virtual Machine (JVM). Thisprevents InfoSphere CDC from using all of the available memory on the systemwhere it is installed. The Maximum Memory Allowed value is set on a per-instance basis for eachinstance you create for your target database. In most cases the default values areappropriate for 32-bit and 64-bit instances. However, if your database is processingan extremely heavy workload, you may have to adjust the default values. The RAMallocated must be physically available on your system. Disk space requirements for the global disk quota Disk space is required on your target system for this quota which is used to store in-scope change data that has not been committed in your database. The amount ofdisk space required is determined by your replication environment and the workloadof your source database. You can configure the amount disk space that is allocated to this quota with themirror_global_disk_quota_gb system parameter. The default setting of this systemparameter is such that InfoSphere CDC will only stop replicating after this disk quotaexhausts all available disk space on your system. If you would prefer InfoSphereCDC to stop replicating after it uses a specific amount of disk space, you can specifythe value with this system parameter in Management Console.

21

IBM InfoSphere Change Data Capture, Version 10.2 Understanding the importance of an appropriatelyconfigured disk subsystem There are many types of disk subsystems in use to meet either business orperformance needs. Not all of these disk subsystems are suitable for use bydatabases or InfoSphere® Data Replication out of the box. Some may need to betuned to ensure that appropriate input/output semantics are in place for reliablecontinuous operation. Symptoms of an unreliable disk subsystem Without appropriate disk subsystem configuration, both the database itself orInfoSphere Data Replication may exhibit any of a wide variety of input/output relatederrors, usually random in nature. Any one of them can stop replication. If thedatabase transaction logs themselves become corrupted due to this kind ofmisconfiguration, then the database itself may become unrecoverable, putting theentire business at risk. Having an appropriately configured disk subsystem istherefore essential to the operation of both database and InfoSphere DataReplication. What makes a disk subsystem unreliable? Typically, disk mounting options that interfere with or modify the read visibility ofwrite operations are the ones which will cause data to be read inaccurately, therebycausing applications such as databases and InfoSphere Data Replication to reporterrors and fail. The expectations of these semantics between the database andInfoSphere Data Replication must be compatible with those provided by the optionsused to mount the disk subsystem in order to avoid corruption issues. Somedatabases exhibit specific behaviors only with certain disk subsystem types, soproper care and attention is needed to properly configure the disk subsystem. Special notes regarding specific configurations Direct I/O on Linux—Due to the nature of the implementation of direct I/O (directio)on Linux, applications that read from files being written using direct I/O must employexactly the same direct I/O options as the writing application. If this is not done, thereading application may not ever see the data written by the writing application andthe reading application can therefore exhibit a stall. Linux versions of InfoSphereCDC prior to version 6.5.1 Interim Fix 17 for Oracle, version 6.5.2 Interim Fix 20 forOracle, and InfoSphere Data Replication versions prior to 10.2 for Oracle andSybase can exhibit this behaviour under certain conditions. The best resolution is toupgrade to the latest Interim Fix level for InfoSphere CDC or to version 10.2 or laterfor InfoSphere Data Replication.

22

IBM InfoSphere Change Data Capture, Version 10.2 Understanding the InfoSphere CDC memoryfootprint Current® versions of InfoSphere® CDC on Linux, UNIX, and Windows platforms arewritten in the Java™ programming language. The memory specified in theInfoSphere CDC configuration tool refers to the amount of memory that the JavaVirtual Machine (JVM) will allocate to InfoSphere CDC to run. This memory is strictlyenforced by the JVM itself and the JVM will ensure that it is not exceeded. The JVM itself also consumes some memory. The amount of this other memoryvaries considerably by Java version, bit length, and operating system. A simple Javaprogram consumes 13212 KB of overhead when run in a 32-bit Java 1.5 JVM onAIX®, but 173509 KB of overhead when run in a 32-bit Java 1.5 JVM on Linux. Inother words, the overhead on Linux is 13 times larger than the overhead on AIX,when controlling for the other variables. The amount of memory overhead consumed by the JVM itself can also change overtime. This is especially true for Linux and UNIX systems. For those systems, oncethe operating system allocates memory to a process, it is not reclaimed until theprocess ends. Thus, the total amount of memory for any given process never goesdown. Given these factors, you should expect that more memory is used by InfoSphereCDC than is allocated in the configuration tool. InfoSphere CDC has no control overthis memory usage and cannot track or otherwise manage it.

23

-

--

---

IBM InfoSphere Change Data Capture, Version 10.2 Calculating database connections required byInfoSphere CDC for Teradata As an administrator, you may find it necessary to calculate how many databaseconnections are needed before installing InfoSphere® CDC on either a source or atarget database. Calculating the upper bound (both permanent and temporary)database connections will help you plan your environment so that it canaccommodate InfoSphere CDC. If you are installing InfoSphere CDC Event Server, InfoSphere CDC for InfoSphereDataStage®, InfoSphere CDC for Teradata, or InfoSphere CDC for Netezza®Technology, then you only need to calculate database connections for the targetdatabase as these products only replicate to target-only destinations. Calculating connections required by InfoSphere CDC on atarget database (4+G)*I + 3*SWhere:

G = number of Management Console GUI and CHCCLP scripting applications thatare connected to your instances of InfoSphere CDC.I = number of InfoSphere CDC instances.S = number of subscriptions in all of your InfoSphere CDC instances.

Example: How to calculate required connections for a targetdatabase You want to set up InfoSphere CDC in the target environment as follows:

1 installed Management Console GUI application.2InfoSphere CDC instances.3 subscriptions.

The number of connections required on the target database will be: (4 + 1)*2 + 3*3 = 19 You should plan for a maximum of 19 database connectionsbefore installing InfoSphere CDC on the target database.

24

IBM InfoSphere Change Data Capture, Version 10.2 Conflict detection and resolution Conflict detection and resolution is available for InfoSphere® CDC for Teradatawhen JDBC apply mode is employed, but not for TPUMP apply mode. Related concepts: Configuring the Teradata TPump utility Supported Teradata JDBC drivers and utilities

25

IBM InfoSphere Change Data Capture, Version 10.2 Creating queues in JMS providers If you choose to use a JMS provider as the communications protocol forInfoSphere® CDC, you will need to define the queues to be used by InfoSphereCDC before you attempt to configure an instance. The queues will need to be named in the format CDC_<port>, where <port> is thefive digit TCP listening port number of the instance. You can left pad the numberwith zeroes if necessary to ensure five digits (example, CDC_00123). Each InfoSphere CDC instance will require its own queue. Instances cannot share aqueue. When you create the queue, you must ensure that they are defined to holdmessages of the type BytesMessage.

26

---

IBM InfoSphere Change Data Capture, Version 10.2 Installing or upgrading InfoSphere CDC for Teradata Before attempting to install or upgrade InfoSphere® CDC, consult the database,operating system and hardware requirements for the specific version of the softwarethat you want to install, to ensure that it is compatible with your system. If you are upgrading to a later version or installing a fix pack, an installation ofInfoSphere CDC must already be present in order to successfully complete theprocess. In this section, you will learn:

Installing InfoSphere CDC for Teradata using an interactive installation Installing InfoSphere CDC for Teradata using a silent installation Upgrading InfoSphere CDC for Teradata You can upgrade InfoSphere CDC by installing a later version of the software overtop of an existing installation.

Related concepts: Before you install InfoSphere CDC for Teradata

27

--

-

--

IBM InfoSphere Change Data Capture, Version 10.2 Installing InfoSphere CDC for Teradata using aninteractive installation Note the following before you install or upgrade InfoSphere® CDC on Linux or UNIX:

Do not install or upgrade InfoSphere CDC as a root user.The installation directory requires file system permissions of 700 if you plan to usethe same user account to install the product, create and configure instances, orupgrade the product.The installation directory requires file system permissions of 770 if you plan to usedifferent user accounts to install the product, create and configure instances, orupgrade the product.

Note: Ensure that the installed version of the Management Console and AccessServer applications are either the same version as the InfoSphere CDC replicationengine or a later version. See also:

To install InfoSphere CDC for Teradata (Windows) To install InfoSphere CDC for Teradata (UNIX)

28

1.

2.3.

4.5.

6.7.8.

9.

IBM InfoSphere Change Data Capture, Version 10.2 To install InfoSphere CDC for Teradata (Windows)

Double-click on the installation executable. The IBM®InfoSphere® CDCinstallation wizard opens. Click Next.If you agree to the license terms, select I accept the terms in the licenseagreement and then click Next.Select the folder where you want to install InfoSphere CDC and click Next.If you already have an installation of InfoSphere CDC, the installation program willprompt you to upgrade the installation. Click OK to upgrade the installation.Select the location for the product icons and click Next.Review the installation summary and click Install.Select Launch Configuration Tool to launch the configuration tool after theinstallation. The configuration tool allows you to add an instance of InfoSphereCDC.Click Done to exit the installation.

Related concepts: Configuring InfoSphere CDC for Teradata (Windows)

29

1.2.

3.4.

5.

6.7.

8.9.

10.

IBM InfoSphere Change Data Capture, Version 10.2 To install InfoSphere CDC for Teradata (UNIX)

Log on to the account you set up for InfoSphere® CDC.Copy the InfoSphere CDC installation file for your UNIX platform from theInfoSphere CDC DVD or the download file.Make the installation binary file executable.Run the installation program by typing the following command:./<installation_binary_name>.bin If you already have InfoSphere CDC installed, the installation program willprompt you to upgrade. Press Enter on the Introduction screen to display the license agreement. Followthe instructions on the screen to navigate through the license agreement.To accept the license agreement, type 1.Enter the absolute path to your installation directory or press Enter to accept thedefault.Note: The directory that you specify must be owned by the account youare using for the installation. If the installation program cannot create thedirectory, you are prompted to specify a different directory. Review the installation summary. Press Enter to start the installation.After completing the installation, InfoSphere CDC gives you the option oflaunching the configuration tool for InfoSphere CDC.Type 1 to launch the configuration tool.

Note: If you have X-Windows installed, the installation program will launch theconfiguration tool in a graphical environment. Related concepts: Configuring InfoSphere CDC for Teradata (UNIX)

30

-

IBM InfoSphere Change Data Capture, Version 10.2 Installing InfoSphere CDC for Teradata using asilent installation A silent installation allows you to automatically install InfoSphere® CDC byspecifying a command with various parameters. You can use this type of installationmethod for large-scale deployments of InfoSphere CDC by embedding the silentinstallation command in a script. See also:

To perform a silent installation of InfoSphere CDC for Teradata (UNIX)

31

1.2.

3.4.

-5.

-

IBM InfoSphere Change Data Capture, Version 10.2 To perform a silent installation of InfoSphere CDCfor Teradata (UNIX)

Log on to the account you set up for InfoSphere® CDC.Copy the InfoSphere CDC installation binary from the InfoSphere CDC CD-ROMor download it from the InfoSphere CDC web site.Make the installation binary executable.Install InfoSphere CDC and generate a response file with the following command:<installation_binary_name> -r <response-file> where: <response-file> is the full path to the installation response file.

On another system, perform the silent installation by running the followingcommand:<installation_binary_name> -i silent -f <response-file> where: <response-file> is the full path to the installation response file.

32

-

-

-

-

-

--

--

IBM InfoSphere Change Data Capture, Version 10.2 Upgrading InfoSphere CDC for Teradata You can upgrade InfoSphere® CDC by installing a later version of the software overtop of an existing installation. Interim fixes cannot be used to upgrade InfoSphere CDC to later versions. You mustfirst install the general availability (GA) release of the software for the later versionand accept the software license agreement, before applying any interim fixes. Afterthe interim fix has been installed, you can start the InfoSphere CDC instances andcomplete the upgrade. Before attempting to upgrade the software, you should be aware of the followingprerequisites:

All subscriptions in all InfoSphere CDC for Teradata instances associated with theinstallation to be upgraded must be stopped.All InfoSphere CDC for Teradata instances associated with the installation must bestopped.When logging in, you must use the same account that was used during the originalinstallation of InfoSphere CDC for Teradata.It is a best practice to backup the installation directory of the current InfoSphereCDC for Teradata installation.It is a best practice to backup the InfoSphere CDC metadata tables (TS_AUTH,TS_BOOKMARK, TS_CONFAUD, and TS_DDLAUD) that are stored in theTeradata database instance that you are replicating to and from. In the event of afailure during the upgrade, having a backup of the metadata will allow you to revertto the point in time before the upgrade. In addition to the InfoSphere CDCmetadata tables stored in your database, InfoSphere CDC maintains some othermetadata in an internal database. It is a best practice to backup the InfoSphereCDC internal metadata at the same time as the InfoSphere CDC metadata tablesin your database are backed up. The dmbackup command can be used to backupthe internal InfoSphere CDC metadata tables.Do not upgrade InfoSphere CDC as a root user.The installation directory requires file system permissions of 700 to install theproduct, create and configure instances, or upgrade the product.

When upgrading an InfoSphere CDC replication engine, you must also upgradeManagement Console and Access Server to the same version or later to access thefull range of functionality that was introduced in the later version of the engine.Management Console and Access Server are backward-compatible and will supportthe functionality available in earlier versions of the engines. CAUTION: You cannot export and import subscriptions across different versions of InfoSphereCDC. Do not attempt to import a subscription file from a previous version into anupgraded version. Once the upgrade is complete, you should create a new exportedsubscriptions xml file. See also:

To upgrade InfoSphere CDC for Teradata (Windows) To upgrade InfoSphere CDC for Teradata (UNIX and Linux)

33

34

1.2.3.

4.

5.

6.7.

8.

9.

10.11.12.

IBM InfoSphere Change Data Capture, Version 10.2 To upgrade InfoSphere CDC for Teradata (Windows)

Ensure that all subscriptions in all InfoSphere® CDC instances are stopped.Ensure that all InfoSphere CDC instances are stopped.Ensure that you have a backup of the TS_AUTH, TS_BOOKMARK,TS_CONFAUD, and TS_DDLAUD metadata tables that are stored in thedatabase instance that you are replicating to and from. In the event of a failureduring the upgrade, having a backup of the metadata will allow you to revert tothe point in time before the upgrade. In addition to the InfoSphere CDCmetadata tables stored in your database, InfoSphere CDC maintains some othermetadata in an internal database. It is a best practice to backup the InfoSphereCDC internal metadata at the same time as the InfoSphere CDC metadatatables in your database are backed up. The dmbackup command can be used tobackup the internal InfoSphere CDC metadata tables.Ensure that you have backed up your InfoSphere CDC installation directory.Important: The backup of the installation directory and the metadata tablesshould be from the same timeframe, so that they contain an identical snapshotof data. Double-click on the installation executable. The IBM®InfoSphere CDCinstallation wizard opens. Click Next.If you agree to the license terms, select I accept the terms in the licenseagreement and then click Next.Select the folder for the existing installation of InfoSphere CDC to be upgradedand click Next.If you already have an installation of InfoSphere CDC, the installation programwill prompt you to upgrade the installation. Click OK to upgrade the installation.Select the location for the product icons and click Next.Review the pre-upgrade summary and click Install.After upgrading the software, you must start all the configured instances in orderto complete the upgrade process. Depending on the number of tables andsubscriptions configured, as well as the complexity of the mappings, the upgradeprocess can take anywhere from several minutes to hours. Once the upgradeprocess is complete, InfoSphere CDC will be ready for replication and willrestart.

35

1.2.3.

4.

5.6.

7.8.

9.

10.11.

12.13.

14.15.

IBM InfoSphere Change Data Capture, Version 10.2 To upgrade InfoSphere CDC for Teradata (UNIX andLinux)

Ensure that all subscriptions in all InfoSphere® CDC instances are stopped.Ensure that all InfoSphere CDC instances are stopped.Ensure that you have a backup of the TS_AUTH, TS_BOOKMARK,TS_CONFAUD, and TS_DDLAUD metadata tables that are stored in thedatabase instance that you are replicating to and from. In the event of a failureduring the upgrade, having a backup of the metadata will allow you to revert tothe point in time before the upgrade. In addition to the InfoSphere CDCmetadata tables stored in your database, InfoSphere CDC maintains some othermetadata in an internal database. It is a best practice to backup the InfoSphereCDC internal metadata at the same time as the InfoSphere CDC metadatatables in your database are backed up. The dmbackup command can be used tobackup the internal InfoSphere CDC metadata tables.Ensure that you have backed up your InfoSphere CDC installation directory.Important: The backup of the installation directory and the metadata tablesshould be from the same timeframe, so that they contain an identical snapshotof data. Log on to the account you set up for InfoSphere CDC.Copy the InfoSphere CDC installation file for the version to which you want toupgrade. This file is available on the InfoSphere CDC DVD or you can downloadthe desired version from the IBM® web site. Ensure that you have copied theinstallation file for the applicable operating system.Make the installation binary file executable.Run the installation program by typing the following command:./<installation_binary_name>.bin If you already have InfoSphere CDC installed, the installation program willprompt you to upgrade. Press Enter on the Introduction screen to display the license agreement. Followthe instructions on the screen to navigate through the license agreement.To accept the license agreement, type 1.Enter the absolute path to your installation directory or press Enter to accept thedefault.Note: The directory that you specify must be owned by the account youare using for the installation. If the installation program cannot create thedirectory, you are prompted to specify a different directory. Confirm the absolute path. If it is correct, type Y and press Enter. Type 1 to confirm that you want to upgrade the existing installation and pressEnter.Review the pre-upgrade summary. Press Enter to start the upgrade.After upgrading the software, you must start all the configured instances in orderto complete the upgrade process. Depending on the number of tables andsubscriptions configured, as well as the complexity of the mappings, the upgradeprocess can take anywhere from several minutes to hours. Once the upgradeprocess is complete, InfoSphere CDC will be ready for replication and willrestart.

36

37

-

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Teradata(Windows) After installing InfoSphere® CDC, the installation program launches a configurationtool. The configuration tool allows you to configure one or more InfoSphere CDCinstances for your environment. You must configure InfoSphere CDC before you canstart replication. In this section, you will learn:

Configuring InfoSphere CDC for Teradata instances (Windows)

38

---

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Teradata instances(Windows) You can add, edit, or delete an instance of InfoSphere® CDC. Use the InfoSphereCDC configuration tool to work with instances. You do not have to start and stopinstances. Before you add, edit, or delete an instance, ensure logging is turned on for eachdatabase from which you intend to capture data changes. After you complete the configuration, you can start InfoSphere CDC. Note: You can back up the metadata for your instance using the dmbackupmdcommand. See also:

To add a new instance of InfoSphere CDC for Teradata (Windows) To edit an instance of InfoSphere CDC for Teradata (Windows) To delete an instance of InfoSphere CDC for Teradata (Windows)

39

1.

2.

3.4.

IBM InfoSphere Change Data Capture, Version 10.2 To add a new instance of InfoSphere CDC forTeradata (Windows)

If you are configuring the first instance of InfoSphere® CDC for Teradata afterinstallation, you can proceed to Step 3 of this procedure.At the command prompt, launch the configuration tool by issuing the followingcommand in the specified directory:\<InfoSphere CDC Installation Directory>\bin\dmconfigurets.exe At the welcome message, click OK to continue.On the IBM®InfoSphere CDC New Instance dialog box, you can configure thefollowing options in the Instance area:

Option DescriptionName Enter a name for your

InfoSphere CDC instance. Thisname must be unique.

Server Port Enter the port number whichInfoSphere CDC uses forcommunication with clientworkstations runningManagement Console andother servers.Note: This portnumber cannot be used byother applications installed onthe same server. You will usethis port number whenspecifying access parametersfor your datastore in theAccess Manager perspective inManagement Console.InfoSphere CDC displays adefault TCP/IP port of 10901.For more information, see yourManagement Consoledocumentation.Note: For more information onthe port requirements forInfoSphere CDC, see Portrequirements.

Auto-Discovery Port Bypass auto-discovery. Thisfeature is disabled by default.Do not select the box or enter aport number.

40

5. In the Windows Service area, you can specify the account that will be used tostart InfoSphere CDC services. Select one of the following options:

Maximum Memory Allowed(MB)

Enter the amount of physicallyavailable RAM that you want toallocate for this instance ofInfoSphere CDC. By default,the configuration tool allocates512 MB of RAM for each 32-bitinstance and 1024 MB of RAMfor each 64-bit instance.Note:Using values other than thedefaults or allocating moreRAM than is physicallyavailable on your server shouldonly be undertaken afterconsidering the impacts onproduct performance.

Bit Version Select the bit-version of yourdatabase by selecting one ofthe following options:32 bit64bitThese options are notenabled if you are installingInfoSphere CDC on a 32-bitserver.

Option DescriptionLocal System account Start InfoSphere CDC services

through the local systemadministrator account.

41

6. In the Teradata InstanceDatabase area, you can configure access to thedatabase that contains the tables for replication. To complete this step, you willrequire system administrator privileges. You can then add a datastore in theAccess Manager perspective in Management Console and provide users accessto this database. For more information, see your Management Consoledocumentation.

This account Start InfoSphere CDC servicesthrough the specified useraccount. The account must bespecified in the format<domain>\<user name>, where<domain> is the name of adomain in your environment,and <user name> is a validlogin user name in thespecified domain. If yourcomputer is not part of adomain, you can specify<computer name>\<username>.In the Password and ConfirmPassword boxes, enter thepassword currently associatedwith the selected Windowsuser account. If you change thepassword for the Windows useraccount after installingInfoSphere CDC, you will haveto use the Windows Servicesdialog to change the passwordcurrently set for eachInfoSphere CDC service.

Option DescriptionName Enter the name of the

database that you want toreplicate data to or from andcontains all of the tables forreplication. This is thedatabase that you configuredas part of the preinstallationtasks.Note: You cannot selecta system database.Note: Do not click theAdvanced button and entervalues unless directed by anIBM representative.

User name Enter the user name for thespecified database.

Password Enter the password for thespecified database.

42

7.

--

8.

9.

A.

B.C.D.E.F.G.

H.

I.J.

In the Refresh Loader Path area, click Browse to specify the directory for bulkinserts into the database. Both your Teradata database and InfoSphere CDCmust have read and write permissions for this directory.Notes:

You should use a different directory for each instance of InfoSphere CDC.This directory may contain database tables for replication. You should take thisinto consideration when determining user access to this directory.

In the Teradata Driver area, click Add to specify the Teradata drivers. Ensurethat you have also added the .jar files necessary for the drivers.If you want to use a JMS provider as the method of communication betweendatastores, perform the following steps. Otherwise TCP/IP will be usedexclusively as the communications protocol.A JMS provider should be usedwhen characteristics of your network prevent the existence of a long term, stableTCP/IP connection.

Ensure that a queue has been created by your system administrator and isnamed correctly. Each InfoSphere CDC instance that is to use a JMSmessage provider must have a queue named in the format CDC_<port>,where <port> is the five digit TCP listening port number of the instance (youcan left pad the number with zeroes if necessary, to ensure five digits). Click the Communications Protocol tab.Select JMS or TCP/IP.Click Add.Select the required JMS Provider .jar files. Click Add Connection.Enter a remote factory name. A connection factory encapsulates a set ofconnection configuration parameters that has been defined by anadministrator. Enter a user name and password for JMS server authentication.This username is defined by your JMS provider. Contact your system administrator formore information. Click the JNDI Server tab.Enter the constant that holds the local or remote connection factory name inthe JNDI Initial Context box. Java™ Naming and Directory Interface (JNDI)is a programming interface from Oracle for connecting Java programs tonaming and directory services.

Database/User Select the database schemaused by InfoSphere CDC formetadata tables. You canspecify any schema exceptthose in use by other installedinstances of InfoSphere CDCfor the givendatabase.Note:InfoSphereCDC metadata tables containimportant configurationinformation and should bebacked up as part of yourdatabase backup strategy.

43

K.

L.

M.N.

O.10.11.

-

-

-

Enter the URL that is relative to the JNDI initial context in the JNDI URL box.In JNDI, all naming and directory operations are performed relative to acontext. Therefore the JNDI defines an initial context that serves as a startingpoint for naming and directory operations. This value should be the fully-qualified class name of the factory class that will create the initial context.If the JNDI server to which you want to connect requires authentication, thenyou need to provide the user name and password to connect to that system.Contact your system administrator for information about the user name thatyou should specify. Click OK to save the connection.Click Test if you want to verify the connection.If the JMS Provider is notconfigured correctly, InfoSphere CDC will use TCP/IP as the communicationprotocol between datastores. Click OK.

Click OK to save your configuration settings for the InfoSphere CDC instance.If InfoSphere CDC has detected an unsupported encoding, a dialog will openasking you to select an alternate encoding from a list.You can filter the list ofalternate encodings by clicking one of the following buttons:

Closest match—Displays the alternated encodings that are the closest matchto the data.Comparable encodings byte length—Displays the alternate encodings inorder of byte length.All–Displays all alternate encodings.

Select an encoding from the list and click OK. If you click Cancel, an error message will be displayed and the instance will notbe created.

Related concepts: Creating queues in JMS providers Related tasks: To start InfoSphere CDC for Teradata (Windows) Related reference: dmbackupmd - Back up metadata

44

1.

2.

3.

4.

5.

IBM InfoSphere Change Data Capture, Version 10.2 To edit an instance of InfoSphere CDC for Teradata(Windows)

In the Instances area, select the instance that you want to modify and click Stop ifthe instance is started.In the Instances area, select an instance and click Edit.The InfoSphere® CDCEdit Instance dialog opens. You can modify any of the values on this dialog box that you specified whenadding an instance.Click OK to save your changes and then click Close.The configuration tool willmodify the instance. In the Instances area, select the instance that you modified and click Start to startthe instance.

45

1.

2.

3.4.

IBM InfoSphere Change Data Capture, Version 10.2 To delete an instance of InfoSphere® CDC forTeradata (Windows)

At the command prompt, launch the configuration tool by issuing the followingcommand in the specified directory:\<InfoSphere CDC Installation Directory>\bin\dmconfigurets.exe In the Instances area, select the instance that you want to delete and click Stop ifthe instance is started.In the Instances area, select an instance and click Delete.Click Yes to permanently delete the instance.

46

-

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Teradata (UNIX) After installing InfoSphere® CDC, the installation program launches a configurationtool. The configuration tool allows you to configure one or more InfoSphere CDCinstances for your environment. You must configure InfoSphere CDC before you canstart replication. In this section, you will learn:

Configuring InfoSphere CDC for Teradata instances (UNIX and Linux)

47

---

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Teradata instances(UNIX and Linux) You can add, edit, or delete an instance of InfoSphere® CDC. Use the InfoSphereCDC configuration tool to work with instances. You do not have to start and stopinstances. Before you add, edit, or delete an instance, ensure logging is turned on for eachdatabase from which you intend to capture data changes. See also:

To add a new instance of InfoSphere CDC for Teradata (UNIX) To edit an instance of InfoSphere CDC for Teradata (UNIX) To delete an instance of InfoSphere CDC for Teradata (UNIX)

48

1.

2.

3.4.5.

6.7.

8.9.

10.11.

A.

B.C.D.E.F.G.

IBM InfoSphere Change Data Capture, Version 10.2 To add a new instance of InfoSphere CDC forTeradata (UNIX)

If you are configuring the first instance of InfoSphere® CDC after installation,you can proceed to Step 3 of this procedure.At the command prompt, launch the configuration tool by issuing the followingcommand in the specified directory:\<InfoSphere CDC Installation Directory>\bin\dmconfigurets At the welcome message, press Enter to continue.Enter the name of the instance you want to add and press Enter.Enter the port number which InfoSphere CDC uses for communication with clientworkstations running Management Console and other servers. InfoSphere CDCdisplays a default port of 10701. Press Enter.This port number cannot be usedby other applications installed on the same server. You will use this port numberwhen specifying access parameters for your datastore in the Access Managerperspective in Management Console. Press Enter to bypass auto-discovery. This feature is disabled by default.Enter the amount of physically available RAM that you want to allocate for thisinstance of InfoSphere CDC and press Enter. By default, the configuration toolallocates 512 MB of RAM for each 32-bit instance and 1024 MB of RAM for each64-bit instance.Using values other than the defaults or allocating more RAM thanis physically available on your server should only be undertaken afterconsidering the impacts on product performance. Depending on the bit version of your server, enter 32 or 64 and press Enter.If you need to add new Teradata drivers, press 2.Enter the path of the newTeradata driver and press Enter. Repeat this process until all necessary drivershave been added. Ensure that you have also added the .jar files necessary forthe drivers When all drivers have been added, press 4 to continue with the configuration.If you want to use TCP/IP as the exclusive method of communication betweendatastores, enter n and press Enter. If you want to have the option to use eithera JMS provider or TCP/IP as the communications protocol, perform the followingsteps:A JMS provider should be used when characteristics of your networkprevent the existence of a long term, stable TCP/IP connection.

Ensure that a queue has been created by your system administrator and isnamed correctly. Each InfoSphere CDC instance that is to use a JMSmessage provider must have a queue named in the format CDC_<port>,where <port> is the five digit TCP listening port number of the instance. Youcan left pad the number with zeroes if necessary to ensure five digits(example, CDC_00123).Enter y and press Enter.Enter 2 to add a JMS provider. Enter the fully qualified path to your JMS provider .jar file and press Enter.Enter 4 and press Enter to complete the configuration of the JMS providers.Enter 1 to add a JMS connection.Enter a JMS remote connection factory name and press Enter. For example,jms/ConnectionFactory. A connection factory encapsulates a set ofconnection configuration parameters that has been defined by anadministrator. InfoSphere CDC uses this to create a connection with your

49

H.I.J.K.L.M.N.O.P.Q.

R.

12.

13.14.

15.

16.17.

A.

B.-

--

C.18.

JMS provider.Enter the user name and press Enter.Enter the password to authenticate to the JMS server and press Enter.Enter the password a second time to confirm and press Enter.Enter the JNDI initial context and press Enter.Enter the URL that is relative to the JNDI Initial Context and press Enter.Enter the user name for the JNDI Principal and press Enter.Enter the JNDI credentials password and press Enter.Enter the password a second time to confirm and press Enter.Press Enter again to return to the Engine Communication Connection menu.Press 5 if you want to verify the connection and then press Enter to return tothe Engine Communication Connection menu.If the JMS Provider is notconfigured correctly, InfoSphere CDC will use TCP/IP as the communicationprotocol between datastores. Enter 7 to complete the configuration of the engine communicationconnection.

Enter the name of the database that contains all of the tables for replication andpress Enter.Enter the user name for the specified database and press Enter.Enter the password for the specified database and press Enter.The configurationtool will now search the database for schemas. Enter the number that corresponds to the database schema used by InfoSphereCDC for metadata tables and press Enter. You can specify any schema exceptthose in use by other installed instances of InfoSphere CDC for the givendatabase.Note:InfoSphere CDC metadata tables contain important configurationinformation and should be backed up as part of your database backup strategy. Enter the absolute path for the refresh loader and press Enter.If InfoSphere CDC detects an unsupported encoding, an error message will bedisplayed and you will be asked to choose an alternate encoding.

Enter y to proceed. If you enter n and press Enter to cancel, the instance willnot be created. Enter a value to choose how the alternate encodings will be displayed:

1—Displays the available alternate encodings that are the closest match tothe database.2—Displays the available alternate encodings in order of byte length.3—Displays all available alternate encodings.

Enter the number for the encoding to be used and press Enter.The configuration tool creates the InfoSphere CDC instance and prompts you tostart the instance. Enter y to start the instance.The configuration tool will promptyou if your configuration is about to overwrite the metadata for an existinginstance.

50

1.

2.

3.

4.5.

6.

IBM InfoSphere Change Data Capture, Version 10.2 To edit an instance of InfoSphere CDC for Teradata(UNIX)

Stop InfoSphere® CDC by using the dmshutdown command. You cannot edit aninstance that is running.At the command prompt, launch the configuration tool by issuing the followingcommand from the <InfoSphere CDC Installation Directory>/bin directory:./dmconfigurets Enter 1 and press Enter to list the installed instances of InfoSphere CDC. Recordthe name of the instance you want to modify.Enter 3 and press Enter to modify an instance of InfoSphere CDC. Enter the number of the instance that you want to modify and press Enter.Theconfiguration tool allows you to edit a number of values that you specified whenadding an instance. After making your changes, enter 5 and press Enter to apply your changes andreturn to the main menu. Enter 6 and press Enter to discard your changes.

51

1.2.

3.

4.5.

IBM InfoSphere Change Data Capture, Version 10.2 To delete an instance of InfoSphere CDC forTeradata (UNIX)

Stop InfoSphere® CDC by using the dmshutdown command.At the command prompt, launch the configuration tool by issuing the followingcommand from the <InfoSphere CDC installation directory>/bin directory:./dmconfigurets Enter 1 and press Enter to list the installed instances of InfoSphere CDC. Recordthe name of the instance you want to delete.Enter 4 and press Enter to delete an instance of InfoSphere CDC.Enter the instance name that you want to delete and press Enter.

52

----

IBM InfoSphere Change Data Capture, Version 10.2 After you install and configure InfoSphere CDC forTeradata Once you have installed and configured InfoSphere® CDC, you can start usingInfoSphere CDC. In this section, you will learn:

Starting InfoSphere CDC for Teradata Stopping InfoSphere CDC for Teradata Maintaining active TCP connections in a network environment Enabling SQL statements in Management Console

53

--

IBM InfoSphere Change Data Capture, Version 10.2 Starting InfoSphere CDC for Teradata When you install InfoSphere® CDC for Teradata on a supported Windows server,you can start it manually after the initial configuration. Starting InfoSphere CDC forTeradata starts the services in Windows. The services will automatically start after areboot. See also:

To start InfoSphere CDC for Teradata (Windows) To start InfoSphere CDC for Teradata (UNIX)

54

1.

2.

IBM InfoSphere Change Data Capture, Version 10.2 To start InfoSphere CDC for Teradata (Windows)

At the command prompt, launch the configuration tool by issuing the followingcommand in the specified directory:\<InfoSphere CDC Installation Directory>\bin\dmconfigurets.exe In the Instances area, select the instance that you want to start and click Start.The configuration tool starts the instance of InfoSphere® CDC.

You can also use the Windows Services dialog to start and stop InfoSphere CDCservices.

55

--

IBM InfoSphere Change Data Capture, Version 10.2 To start InfoSphere® CDC for Teradata (UNIX) Depending on the operating system you are running, issue one of the following startcommands:

dmts32 - I <instance_name>dmts64 - I <instance_name>

56

--

IBM InfoSphere Change Data Capture, Version 10.2 Stopping InfoSphere CDC for Teradata It may be necessary to stop InfoSphere® CDC when you want to change theconfiguration settings, take a server or database offline for maintenance purposes,or if you want to upgrade InfoSphere CDC. You can use the configuration tool orcommands to stop InfoSphere CDC. See also:

To stop InfoSphere CDC for Teradata (Windows) To stop InfoSphere CDC for Teradata (UNIX)

57

1.

2.

3.

IBM InfoSphere Change Data Capture, Version 10.2 To stop InfoSphere CDC for Teradata (Windows)

End replication on all subscriptions in Management Console. For moreinformation on how to end replication on subscriptions, see your ManagementConsole documentation.Launch the configuration tool by issuing the following command in the specifieddirectory:\<InfoSphere CDC Installation Directory>\bin\dmconfigurets In the Instances area, select the instance that you want to stop and click Stop.The configuration tool stops the InfoSphere® CDC instance and services. Theservices will automatically start again after a reboot.

You can also use the Windows Services dialog to start and stop InfoSphere CDCservices.

58

1.

2.

IBM InfoSphere Change Data Capture, Version 10.2 To stop InfoSphere CDC for Teradata (UNIX)

End replication on all subscriptions in Management Console. For moreinformation on how to end replication on subscriptions, see your ManagementConsole documentation.Depending on how you want to stop InfoSphere® CDC, issue one of the followingstop commands in the bin directory in your InfoSphere CDC installation directory:

Option Descriptiondmshutdown [-I<instance_name>]

Use this command to gracefullyshut down InfoSphere CDC. Ifyou have multiple activeInfoSphere CDC installationson the same UNIX server, andyou want to shut them all down,run this command from theinstallation directory for eachInfoSphere CDC instance.

dmterminate [-L <locale>] Use this command to terminateall processes for all instancesrunning on a UNIX server. Use this command when youcannot completely shut downInfoSphere CDC using thedmshutdown command.

59

-

IBM InfoSphere Change Data Capture, Version 10.2 Maintaining active TCP connections in a networkenvironment If your deployment of InfoSphere® CDC is in a network environment that uses afirewall, VPN gateway, or local system tools to detect idle TCP connections, it maybe necessary to configure the product to prevent these connections from beingclosed during periods of application inactivity between the source and target. By default, InfoSphere CDC sends a message over TCP connections every 20seconds to ensure these connections remain active during periods of inactivity. Ifyour network policies close TCP connections for idle periods of less than 20seconds, you must change the configuration of each instance of InfoSphere CDC toensure the TCP connections remain open. See also:

To maintain active TCP connections

60

1.

2.3.

4.5.

IBM InfoSphere Change Data Capture, Version 10.2 To maintain active TCP connections

For each instance of InfoSphere® CDC, navigate to one of the followingdirectories depending on your operating system:UNIX : <CDC_installation_directory>/instance/<instance_name>/conf Windows:<CDC_installation_directory>\instance\<instance_name>\conf Open the comms.ini file in a text editor.Change the KEEP_ALIVE_TIMEOUT parameter to a value that is lower than thetime used to detect idle connections in your network. For example, if yournetwork disables idle TCP connections after 15 seconds, you can change theKEEP_ALIVE_TIMEOUT parameter to a value of 10 seconds:KEEP_ALIVE_TIMEOUT=10 Save the comms.ini file.For the changes to take effect, use the configuration tool to restart all instances ofInfoSphere CDC.

InfoSphere CDC will now send messages over the TCP connection every 10seconds.

61

-

IBM InfoSphere Change Data Capture, Version 10.2 Enabling SQL statements in Management Console InfoSphere® CDC lets you execute SQL statements after it applies a table-levelclear or refresh operation to a target table. You can specify SQL statements in theAdditional SQL dialog box in Management Console. By default, this feature isdisabled in InfoSphere CDC for security reasons. You can enable this feature bycreating a table called TS_SQL_EXECAUTH in the database where you installedInfoSphere CDC. The structure of the table is unimportant, and you must create thetable using the same schema as the metadata tables during the configuration ofInfoSphere CDC. For more information about specifying SQL statements inManagement Console, see Specifying SQL to control refresh operations in yourManagement Console documentation. See also:

To enable SQL statements in Management Console

62

1.

2.

IBM InfoSphere Change Data Capture, Version 10.2 To enable SQL statements in Management Console

Locate the database on the target server that you created for InfoSphere® CDC.Depending on how you are using InfoSphere CDC, this is the database you wantInfoSphere CDC to replicate to or from.Note: During installation, InfoSphere CDCplaces metadata tables in the database necessary for InfoSphere CDCprocesses. If you want to enable the specification of SQL statements, create a table namedTS_SQL_EXECAUTH in the database.Note: The table can have any structureand must be created in the schema you specified when you configuredInfoSphere CDC.

63

------

IBM InfoSphere Change Data Capture, Version 10.2 Configuring the Teradata TPump utility This section identifies specific operational characteristics of Teradata and theTeradata TPump utility that can impact InfoSphere® CDC. In this section, you will learn:

Teradata TPump restrictions and limitations Concurrent load tasks in Teradata Teradata TPump error handling and recovery Customizing the Teradata TPump script file Table-level customization Journaling before and after images

64

----

IBM InfoSphere Change Data Capture, Version 10.2 Teradata TPump restrictions and limitations The Teradata TPump utility has a number of restrictions and limitations that impactsInfoSphere® CDC for Teradata. Unsupported features InfoSphere CDC for Teradata with TPump does not support the use of the followingfeatures:

Updating of primary keys Refresh (including parallel refresh and differential refresh)Commitment controlFast apply

Maximum data file size The maximum data file size that is supported by the Teradata TPump utility is 2gigabytes. When the Teradata TPump data file reaches the maximum file size, theutility loads the data into a Teradata database. You can change the maximum datafile size by modifying the mirror_tpump_max_file_size_mb system parameter.Modifying the file size can lead to better performance in your working environment. Maximum row length The maximum row length for a Teradata TPump load operation (data, plusindicators) is approximately 64,000 bytes. In InfoSphere CDC, the maximum rowlength determines where the Teradata TPump utility can be applied. TPump canonly be used to load data for subscriptions where the cumulative row length for allselected publication tables is less than 64,000 bytes. This imposed limitation isillustrated in the following diagram:

In the diagram, three publication tables (T1, T2, and T3) are selected for replicationunder the same subscription in InfoSphere CDC. C1, C2, and C3 identify thecolumns in the tables. In the first scenario (A), Teradata TPump cannot be used toload data for this subscription as the cumulative row length of the three tables isgreater than 64,000 bytes. In the second scenario (B), Teradata TPump can beused as the cumulative row length of the three tables is less than 64,000 bytes.

65

-

-

Encoding considerations for native apply utilities When using either the TPUMP utility or FastLoad utility for refresh or mirroring, youneed to ensure that target tables do not have mixed encodings. The encodings mustbe identical between the source and target tables. You must also ensure that thefollowing system parameters are set according to the target table default encoding:

If the target table encoding is Latin, ensure that the mbcs_support_is_on systemparameter is set to false.If the target table encoding is Unicode, ensure that the mbcs_support_is_onsystem parameter is set to true.

Related concepts: Apply mode methods Related information: mbcs_support_is_on

66

IBM InfoSphere Change Data Capture, Version 10.2 Concurrent load tasks in Teradata Teradata limits the number of concurrent load tasks used by the Teradata loadutilities (Teradata TPump, Teradata FastLoad, Teradata MultiLoad, and so on). InTeradata, the default maximum number of concurrent load tasks is 5. For eachsubscription in Management Console where Teradata TPump is used to loadreplicated data, one of the available load tasks is consumed. Therefore, a maximumof 5 subscriptions can be concurrently used to load replicated data into a Teradatadatabase. In Teradata, your database administrator can change the maximumnumber of concurrent load tasks. You may want to increase the setting if the defaultmaximum number of concurrent load tasks is insufficient in your workingenvironment. For more information, consult your database administrator or see yourTeradata documentation.

67

-

IBM InfoSphere Change Data Capture, Version 10.2 Teradata TPump error handling and recovery This section provides basic error recovery directions in the event that youexperience problems with the Teradata TPump utility when using InfoSphere® CDCfor Teradata. See also:

To configure error handling in TPump

68

1.

2.

3.

IBM InfoSphere Change Data Capture, Version 10.2 To configure error handling in TPump

If a problem occurs, examine the contents of the Teradata TPump log file.This filecontains Teradata error codes and error table names that will assist you in errorrecovery activities. For information about specific Teradata error codes and errortable names that are found in the job log file, see your Teradata documentation. The location of the Teradata TPump log file is specified by themirror_tpump_files_root_folder_path system parameter. After examining Teradata error codes and error tables and then making anynecessary corrections, re-run the Teradata TPump utility using your existing data(.dat) and script (.script) files. For more information on how to run the TeradataTPump utility, see your Teradata documentation. The location of the Teradata TPump data and script files is also specified by themirror_tpump_files_root_folder_path system parameter. If the Teradata TPump utility successfully loads data, you can delete the data andscript files or move these files to the Teradata TPump archive folder.The locationof the Teradata TPump archive folder is also specified by themirror_tpump_files_root_folder_path system parameter. If the Teradata TPump utility does not work properly, repeat the first two steps inthis procedure or see your Teradata documentation.

69

-

IBM InfoSphere Change Data Capture, Version 10.2 Customizing the Teradata TPump script file During active replication, InfoSphere® CDC generates data (.dat) and script (.script)files that are used by the Teradata TPump utility to load replicated data intoTeradata databases. Data files contain the data that is loaded into Teradata, andscript files specify what is contained in the data files and how data is loaded. Scriptfiles contain Teradata TPump command parameter settings. When replicating datato Teradata databases, the script files that InfoSphere CDC generates contain a setof default values for these parameters. However, in your working environment, youmay want to use different settings for the parameters. InfoSphere CDC can generatescript files containing Teradata TPump command parameter settings that arecustomized for your working environment. This section describes how the generatedscript files can be customized to reference your parameter settings. Note: Generally,the default values for the command parameters are suitable for most workingenvironments. If you want to specify different settings, you must be familiar withXML and Teradata TPump. For more information about the Teradata TPumpcommands and command parameters, see your Teradata documentation. See also:

To customize the TPump script file

70

1.

2.

3.

IBM InfoSphere Change Data Capture, Version 10.2 To customize the TPump script file

If necessary, stop all active data replication to Teradata databases.UseManagement Console to stop all replication to Teradata databases. For moreinformation about stopping replication, see your Management Consoledocumentation. Navigate to the directory on the Windows server where InfoSphere® CDC forTeradata has been installed. Using a text editor, open the tpumpscripttsdefaults.xml file or the file currentlyassigned to the tpump_script_val_file system parameter.By default, thetpumpscripttsdefaults.xml file is created during InfoSphere CDC installation andcontains the Teradata TPump command parameter settings that are referencedwhen InfoSphere CDC generates script files during data replication. The following information references the tpumpscripttsdefaults.xml file.Depending on the value assigned to the mirror_tpump_script_val_file_namesystem parameter in your working environment, the name of the XML file that youmust modify may be different. The unmodified contents of the tpumpscripttsdefaults.xml file are shown in thefollowing figure:

The command parameter settings apply to all publisher identifiers that are defined

71

A.

B.

C.

4.

5.

6.

in a InfoSphere CDC for Teradata installation (see <sub name="*ALL"> in theunmodified tpumpscripttsdefaults.xml file). If you can install multiple instances ofInfoSphere CDC on the same server, you can modify eachtpumpscripttsdefaults.xml file to define different command parameter settings foreach installation. For a particular InfoSphere CDC installation, you can define different commandparameter settings for each publisher identifier. In the tpumpscripttsdefaults.xmlfile:

Copy the tags from <sub name="*ALL"> to </sub> and paste the copiedmaterial immediately after the <tpumpscript> tag or immediately before the</tpumpscript> tag.Replace *ALL in <sub name="*ALL"> with the name of the publisher identifierfor which you want to define command parameter settings.Repeat the previous steps for other publisher identifiers for which you want todefine command parameter settings.

The tpumpscripttsdefaults.xml file does not contain all Teradata TPumpcommands and command parameters. However, you can add commands andcommand parameters to the file. For example, you can insert the following tags inthe BEGIN LOAD command in tpumpscripttsdefaults.xml to include the setting forthe SLEEP parameter:<param name="SLEEP"><value name="sleepperiod">10</value>

</param> If you need to add <value...> tags for a command parameter, you must includethe name attribute. However, it can be set to any string. In the example,sleepperiod is used to satisfy this requirement. If you require assistance to addcommands and command parameters, contact your IBM® sales representative. Add or modify data within the <value...> and </value> tags for the TeradataTPump parameter settings that you want to customize for your workingenvironment. You can transfer settings from Teradata TPump script files you havesuccessfully used for other purposes to the tpumpscripttsdefaults.xml file. Do not delete or change any of the <tsgenerated...> and </tsgenerated> tags inthe file. If you delete or change any of these tags, the script files generated byInfoSphere CDC are invalid. Save the changes you have made to the tpumpscripttsdefaults.xml file and thenclose the file. Start or restart data replication to Teradata databases. After starting or restartingdata replication, the script files generated by InfoSphere CDC for Teradatareference the updated Teradata TPump command parameter settings applied tothe tpumpscripttsdefaults.xml file.

72

IBM InfoSphere Change Data Capture, Version 10.2 Table-level customization You can use the tpumpscripttsdefaults.xml file to define Teradata TPump commandparameter settings for each publisher identifier. You can extend this file so that thegenerated script files also contain table-level customization. Thetpumpscripttsdefaults.xml file installed with InfoSphere® CDC does not provide atemplate to define table-level customization. Therefore, contact your IBM® salesrepresentative for further assistance in this area.

73

IBM InfoSphere Change Data Capture, Version 10.2 Journaling before and after images InfoSphere® CDC does not require that the journaling of before and after images beenabled for the owner of the InfoSphere CDC metadata tables in Teradata. Toreduce disk space usage in your working environment, disable the journaling ofbefore and after images before replicating data to Teradata databases.

74

-

--

IBM InfoSphere Change Data Capture, Version 10.2 InfoSphere CDC for Teradata metadata tables InfoSphere® CDC maintains a set of metadata tables that represent data about yourcurrent replication configuration. These tables are created in the database that youspecify in the configuration tool and should be part of the backup strategy for yourdatabase. InfoSphere CDC will not replicate these tables. Do not modify thecontents of these tables unless requested to do so by your IBM® representative. The names of the metadata tables created by InfoSphere CDC are as follows:

TS_AUTHNote: For all users you added in the Access Manager perspective inManagement Console, make sure you give GRANT SELECT privileges to theTS_AUTH metadata table. TS_BOOKMARKTS_CONFAUD—The conflict resolution audit table records information aboutconflicts that were resolved using conflict detection and resolution.

Related concepts: Configuring InfoSphere CDC for Teradata (Windows) Configuring InfoSphere CDC for Teradata (UNIX)

75

IBM InfoSphere Change Data Capture, Version 10.2 Data types supported by InfoSphere CDC forTeradata For information about data types supported by InfoSphere® CDC for Teradata, seeSupported data types.

76

IBM InfoSphere Change Data Capture, Version 10.2 System parameters for InfoSphere CDC for Teradata For information about system parameters for InfoSphere® CDC for Teradata, seeSystem parameters for InfoSphere CDC for Teradata.

77

-------

IBM InfoSphere Change Data Capture, Version 10.2 Commands for InfoSphere CDC for Teradata This section discusses the commands available with InfoSphere® CDC. Using thesecommands you can control replication, manage your tables for replication, monitorreplication, and perform various other tasks. In this section, you will learn:

Using the InfoSphere CDC for Teradata commands Setting the TSINSTANCE environment variable Database transaction log commands Exporting and importing configuration commands Managing tables for replication commands Monitoring replication commands Other commands

78

--

-

-

--

-

--

IBM InfoSphere Change Data Capture, Version 10.2 Using the InfoSphere CDC for Teradata commands You can issue InfoSphere® CDC commands at a command line prompt or as part ofa batch file or shell script. Commands are case-sensitive in UNIX environments andare located in the bin directory of your InfoSphere CDC installation directory. Youmust run the commands from this directory. Note: Use the -? flag to list the available parameters for a command and a shortdescription of each parameter. For example, dmstartmirror -?. Command formats For each command, the following items of information are provided:

Syntax—Identifies the name of the command and lists the command parameters.Parameters—Describes each parameter in the command and identifies the valuesthat can be specified.Result—Indicates the values that are returned by the command if it is successful.These values can be useful for scripting. This section also specifies the informationthat is displayed on the screen, if any, as a result of executing the command.Examples—Provides one or more examples of invoking the command.

Parameter formats Note the following conventions in the definition of the command parameters:

Angle brackets ( < > ) indicate a mandatory parameter.Square brackets ( [ ] ) indicate an optional parameter. If you omit the parameter,InfoSphere CDC uses a default value.A vertical bar ( | ) separating one or more parameters indicate that only one of theparameters in the list can be used. When one or more vertical bars appear in a listof parameters that is enclosed by square brackets [ ], the choices are limited to theparameters in the list, but you have the option to not specify any of the parameters.Ellipsis ( ... ) means that a parameter or option can be repeated more than once.You can issue the commands in UNIX or Windows.

79

-

-

IBM InfoSphere Change Data Capture, Version 10.2 Setting the TSINSTANCE environment variable Before using InfoSphere® CDC commands, you can set the TSINSTANCEenvironment variable to the name of your InfoSphere CDC instance. After you set the TSINSTANCE environment variable, you no longer have to specifythe instance name when issuing commands. Windows Issue the following command at the command prompt: SET TSINSTANCE=<instance_name> where:

<instance_name> is the name of your InfoSphere CDC instance. The following command is for kshell. You can run similar commands in other shells: export TSINSTANCE=<instance_name> where:

<instance_name> is the name of your InfoSphere CDC instance.

80

-

IBM InfoSphere Change Data Capture, Version 10.2 Database transaction log commands This section contains commands that help you manage your database transactionlog or bookmarks. See also:

dmshowbookmark - Display bookmark information

81

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmshowbookmark - Display bookmark information CAUTION: Improper use of this command in conjunction with the dmsetbookmark commandcan result in data loss or data duplication. You should only execute thedmsetbookmark command when directed by IBM Technical Support. Use this command on your InfoSphere® CDC target system to obtain the replicationposition (bookmark) in the stream of change data for a subscription. After generatingthe replication position information with this command, you can use thedmsetbookmark command on the source system to set the replication position for asubscription. Syntax dmshowbookmark [-I <INSTANCE_NAME>] -s <SOURCE_ID>

[-f <bookmark_file_name>] [-x <bookmark_file_name>] [-v] [-L <locale>] Parameters

-I <INSTANCE_NAME>The name of the InfoSphere CDC instance. You can set the TSINSTANCEenvironment variable to the name of your InfoSphere CDC instance. After this iscomplete, you no longer have to specify the instance when issuing commands.

-s <SOURCE_ID>Specifies the source ID of the subscription for which you want to obtain thereplication position (bookmark).Source IDs are automatically generated basedon truncating the subscription name to 8 characters during subscriptioncreation. Source IDs must be unique.

-f <bookmark_file_name>Specifies the name of the binary file that will be generated by this command.The generated file contains information about the replication position(bookmark) for the specified subscription. You can specify an absolute path for the location where you want to create thefile. If you do not specify an absolute path, the file is created in the InfoSphereCDC installation directory. Use the -f parameter in the dmsetbookmark command to read the binary filegenerated by this parameter. Note: Use the -x parameter if you are issuing this command from the target of aDB2® for LUW DPF source environment.

-x <bookmark_file_name>Specifies the name of the XML file that will be generated by this command. Thegenerated file contains information about the replication position (bookmark) forthe specified subscription. Use this parameter if you are replicating from a DB2for LUW DPF source environment. The XML file contains replication positions(bookmarks) for all partitions.You can specify an absolute path for the locationwhere you want to create the file. If you do not specify an absolute path, the fileis created in the InfoSphere CDC installation directory. Use the -f parameter in the dmsetbookmark command to read the XML filegenerated by this parameter.

82

--

--

-vDisplays verbose information about the replication position (bookmark),including a hexadecimal-encoded string. The amount of information displayeddepends on the type and version of the source engine. The hexadecimal-encoded string is always displayed. This parameter displays a subset of whatthe dmdecodebookmark command displays. If not specified, only ahexadecimal-encoded string is displayed.Note: Use the -x parameter if you areissuing this command from the target of a DB2 LUW DPF source environment.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmshowbookmark -I MYINSTANCE -s MASTER -f bookmarkInfoSphere CDCobtains the replication position (bookmark) information for the specified instance andthe MASTER source ID. Replication position (bookmark) information is contained inthe bookmark binary file which will be placed in the InfoSphere CDC installationdirectory since no absolute path has been specified. dmshowbookmark -I MYINSTANCE -s FINANCE -x mybookmarksInfoSphere CDCobtains the replication position (bookmark) information for the specified instance andthe FINANCE source ID. Replication position (bookmark) information is contained inthe mybookmarks XML file which will be placed in the InfoSphere CDC installationdirectory since no absolute path has been specified.

83

--

IBM InfoSphere Change Data Capture, Version 10.2 Exporting and importing configuration commands This section contains commands that allow you to export and/or import yourInfoSphere® CDC global configuration. See also:

dmexportconfiguration - Export InfoSphere CDC Configuration dmimportconfiguration - Import InfoSphere CDC Configuration

84

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmexportconfiguration - Export InfoSphere CDCConfiguration Use this command to export the configuration details of an installed instance ofInfoSphere® CDC. Configuration details are sent to an XML configuration file. Youcan use the dmimportconfiguration command to import the XML file that you createwith this command into another instance of InfoSphere CDC. Note: This command does not export subscription-specific settings that areconfigured in Management Console. Subscription-specific settings can be exportedto an XML file in Management Console. Note: This command is interactive and will prompt you for your password. Youcannot script this command. Syntax dmexportconfiguration <absolute_path_to_configuration_file> [-L <locale>] Parameters

<absolute_path_to_configuration_file>The absolute path to the XML configuration file that you want to export.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmexportconfiguration c:\configuration.xmlInfoSphere CDC exports the XML file tothe specified absolute path. Related reference: dmimportconfiguration - Import InfoSphere CDC Configuration

85

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmimportconfiguration - Import InfoSphere CDCConfiguration Use this command to import the InfoSphere® CDC configuration settings from anXML file which you created with the dmexportconfiguration command. Syntax dmimportconfiguration <absolute_path_to_configuration_file> [-L <locale>] Parameters

<absolute_path_to_configuration_file>The absolute path to the XML configuration file that you are importing.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmimportconfiguration c:\configuration.xml InfoSphere CDC imports the XML configuration file from the specified absolute path. Related reference: dmexportconfiguration - Export InfoSphere CDC Configuration

86

-

IBM InfoSphere Change Data Capture, Version 10.2 Managing tables for replication commands This section contains commands that help you manage the tables that you want toreplicate with InfoSphere® CDC. See also:

dmreassigntable - Update target table definition

87

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmreassigntable - Update target table definition Use this command to update the definition of a target table in InfoSphere® CDCmetadata after you change the definition of the target table in your database. Syntax dmreassigntable [-I <INSTANCE_NAME>] -s <SUBSCRIPTION_NAME ...>

<-A|-t <database>.<table> ...> [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.

-s <SUBSCRIPTION_NAME>Specifies the subscription that contains the source table that is mapped to thetarget table which was updated in your database. To specify multiplesubscriptions, list the subscriptions separated by a space.

-ASpecifies that InfoSphere CDC updates definitions for all target tables in thesubscription.

-t <database>.<table>Specifies the name of a source table in the subscription that is mapped to thetarget table for which InfoSphere CDC updates the table definition in themetadata. You must specify the table name in the format database.table. Tospecify multiple tables, list the tables separated by a space.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the operation was successful. If it fails, thiscommand returns a non-zero value. Example dmreassigntable -I NEWINSTANCE -s FINANCE -AInfoSphere CDC updatesdefinitions for all target tables in the Finance subscription.

88

--

IBM InfoSphere Change Data Capture, Version 10.2 Monitoring replication commands This section contains commands that help you monitor replication in InfoSphere®CDC. See also:

dmclearevents - Clear events dmshowevents - Display InfoSphere CDC events

89

--

--

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmclearevents - Clear events Use this command to delete events from the Event Log view in ManagementConsole. Syntax dmclearevents [-I <INSTANCE_NAME>] [-S|-T-|-B] <-A|-s <SUBSCRIPTION_NAME ...>

[-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere® CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.

-SSpecifies that InfoSphere CDC clears events from the source.

-TSpecifies that InfoSphere CDC clears events from the target.

-BSpecifies that InfoSphere CDC clears events from both the source and target. Ifnone of the S, T, and B options are specified, InfoSphere CDC assumes B bydefault.

-ASpecifies that InfoSphere CDC clears events for all subscriptions.

-s <SUBSCRIPTION_NAME>Specifies that InfoSphere CDC clears events for the indicated subscription. Tospecify multiple subscriptions, list the subscriptions separated by a space.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmclearevents -I MYINSTANCE -S -AInfoSphere CDC clears events from thesource for all subscriptions for the specified instance. dmclearevents -I MYINSTANCE -B -s FINANCE MARKETINGInfoSphere CDCclears events from both the source and target for the Finance and Marketingsubscriptions for the specified instance.

90

--

--

--

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmshowevents - Display InfoSphere CDC events Use this command to display InfoSphere® CDC events to standard output. You canuse this command as an alternative to showing InfoSphere CDC events in theEvent Log view in Management Console. The output of this command shows events in chronological order with the mostrecent event shown first in the list. Syntax dmshowevents [-I <INSTANCE_NAME>] <-a|-s <SUBSCRIPTION_NAME> ...

|-t <SOURCE_ID> ...|-s <SUBSCRIPTION_NAME> ... -t <SOURCE_ID> ...> [-h] [-c max_msg]

[-L <locale>] or dmshowevents -I <INSTANCE_NAME> <-a|-s <SUBSCRIPTION_NAME>|-t

<SOURCE_ID>> ...> [-h] [-c <max_msg>] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.

-aSpecifies that InfoSphere CDC shows events for all subscriptions.

-s <SUBSCRIPTION_NAME>Specifies the name of the subscription for which InfoSphere CDC displayssource events. To specify multiple subscriptions, list the subscriptionsseparated by a space.

-t <SOURCE_ID>Specifies the source ID of the subscription for which InfoSphere CDC displaystarget events. List the source IDs if you specify more than one.Source IDs areautomatically generated based on truncating the subscription name to 8characters during subscription creation. Source IDs must be unique.

-hSpecifies that InfoSphere CDC displays a header before the list of events. Thisoption helps you identify each item of information that is displayed for eachevent.

-c <max_msg>Specifies the maximum number of events that InfoSphere CDC displays. If youomit this parameter or you specify a value greater than the total number ofevents, InfoSphere CDC displays all events for the specified subscriptions andsource IDs.

Minimum Setting—0. No events are shown.Maximum Setting—2147483647

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the operation was successful. If it fails, this

91

command returns a non-zero value. Examples dmshowevents -I NEWINSTANCE -s FINANCEInfoSphere CDC displays all eventsfor the Finance subscription for the specified instance. dmshowevents -I MYINSTANCE –a –hInfoSphere CDC displays all events for allsubscriptions. A header is displayed before the list of events for the specifiedinstance. dmshowevents -I NEWINSTANCE –s FINANCE MARKETING –t ATLANTA –h –c20InfoSphere CDC displays the most recent 20 events for the Finance andMarketing subscriptions and for the Atlanta source ID. A header is displayed beforethe list of events for the specified instance. Sample output TIME|AGENTTYPE|SUBSCRIPTION|EVENTID|SEVERITY|EVENTPROGRAM|EVENTTEXT

2006-04-21 17:23:08.817|T|ATLANTA|95|Information|class com.datamirror.ts.target.

publication.c|IBM InfoSphere Change Data Capture Communications ending.

2006-04-21 17:23:08.614|T|ATLANTA|1538|Information|class com.datamirror.ts.target.

publication.c|---IBM InfoSphere Change Data Capture for ATLANTA terminating

normally.

2006-04-21 17:23:08.333|T|ATLANTA|1537|Information|class com.datamirror.ts.target.

publication.c|Describe conversation with ATLANTA completed successfully.

2006-04-21 17:23:07.911|T|ATLANTA|1536|Information|class com.datamirror.ts.target.

publication.c|Describe conversation started by ATLANTA.

2006-04-21 17:23:07.333|T|ATLANTA|1531|Information|class com.datamirror.ts.target.

publication.c|Communication with ATLANTA successfully started on Data channel.

2006-04-21 17:23:06.973|T|ATLANTA|1534|Information|class com.datamirror.ts.engine.a

|Code page conversation from the source database's code page 1252 to the target

database's code page Cp1252 for ATLANTA will be performed by the Remote system Fields in each record are separated by vertical bars ( | ). These fields are identifiedin the first line of the output. In the AGENTTYPE field, S indicates source and Tindicates target.

92

----------

IBM InfoSphere Change Data Capture, Version 10.2 Other commands This section contains miscellaneous commands that allow you to determine theversion of InfoSphere® CDC, verify communications, stop InfoSphere CDC, setsystem parameters, and back up your metadata. See also:

dmbackupmd - Back up metadata dmconfigurets - Configure InfoSphere CDC dmset - Set InfoSphere CDC system parameter dmshowversion - Show InfoSphere CDC version dmshutdown - Shut down InfoSphere CDC dmsupportinfo - Collect IBM Support information dmts32 - Start InfoSphere CDC dmts64 - Start InfoSphere CDC dmmdcommander dmmdconsole

93

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmbackupmd - Back up metadata Use this command to create a backup of the InfoSphere® CDC metadata databasewhich contains information about your current replication configuration. You shouldalways back up your metadata when there are changes to your subscriptionconfiguration and table status. You can only back up your metadata whileInfoSphere CDC is running. The backup of the metadata database is created in <Installation_directory>\instance\<instance_name>\conf\backup. The files in the backup directory should bestored on separate media for possible recovery. Syntax dmbackupmd [-I <INSTANCE_NAME>] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails.

94

--

IBM InfoSphere Change Data Capture, Version 10.2 dmconfigurets - Configure InfoSphere CDC Use this command to launch the InfoSphere® CDC configuration tool. You can usethis tool to create instances and configure your installation of InfoSphere CDC. If the DISPLAY environment variable has been set, the configuration tool willattempt to launch the graphical user interface (GUI) version of the configuration toolwhen this command is issued. If you do not have the graphical libraries installed toview the GUI, you will need to ensure that the DISPLAY environment variable hasbeen cleared in order to launch the command line version. Syntax dmconfigurets [-L <locale>] Parameters

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails.

95

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmset - Set InfoSphere CDC system parameter Use this command to view or change InfoSphere® CDC system parameters. Youcan also change system parameters in Management Console. Note: You can set any system parameter using this command. However, it will onlydisplay system parameters that are set to non-default values. Syntax dmset [-I <INSTANCE_NAME>] [<parameter_name>[=[<parameter_value>]]] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.

<parameter_name>Specifies the name of the InfoSphere CDC system parameter.

<parameter_value>Specifies the value that you want to assign to the system parameter.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmset -I MYINSTANCEDisplays all of the system parameters that are set to non-default values. dmset -I MYINSTANCE events_max_retain=20000Sets the events_max_retainsystem parameter to 20000. dmset -I MYINSTANCE events_max_retainDisplays the current value of thespecified parameter. dmset -I MYINSTANCE stop_replication=Deletes the stop_replication systemparameter.

96

--

IBM InfoSphere Change Data Capture, Version 10.2 dmshowversion - Show InfoSphere CDC version Use this command to display the InfoSphere® CDC version and build number. Runthis command before you contact your IBM® representative. Syntax dmshowversion [-L <locale>] Parameters

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the operation was successful. If it fails, thiscommand returns a non-zero value.

97

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmshutdown - Shut down InfoSphere CDC Use this command to stop an instance of InfoSphere® CDC. This command is oftenused prior to taking a server or database offline for maintenance purposes orupgrading InfoSphere CDC. Note: As a best practice before you run this command and to ensure that itcompletes successfully, use the dmendreplication command to end replication on allsubscriptions that use the instance specified in this command. To end replication on subscriptions that use the specified instance, you can use the–a parameter which will generate an error when forcefully ending replication onsubscriptions that use the instance as a target. If this command does not end InfoSphere CDC processes and stop the specifiedinstance, use the dmterminate command on the UNIX platform to force a completeshut down. Syntax dmshutdown [-I <INSTANCE_NAME>] [-c|-i|-a] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.

-cSpecifies that InfoSphere CDC stops the specified instance with the Normaloption. InfoSphere CDC will use this option by default if you do not specify -i or–a. The instance will only stop if no subscriptions are currently running.Normalis the most appropriate option for most business requirements and is thepreferred method for stopping an instance in most situations.

-iSpecifies that InfoSphere CDC stops the specified instance with the Immediateoption. The instance will only stop if no subscriptions are currently running.Starting the target instance after using this option can be slower than -c.

-aSpecifies that InfoSphere CDC stops the specified instance and endsreplication on all subscriptions that use the instance with the Abort option.Subscriptions that use the specified instance will end replication with an error.This option stops all in progress work and then ends replication rapidly. Startingreplication on subscriptions after using this option can be much slower thanusing -c. A refresh in progress will be interrupted and the target will stopprocessing any data that has not been committed before replication ends. Attention: Use this option if your business reasons require a rapid end toreplication and you are willing to tolerate a much slower start when you resumereplication on the specified subscriptions. A sudden business requirement for an unplanned shutdown of your sourcesystem may require this option for ending replication. Note: As a best practice, use the dmendreplication command to end replicationon all subscriptions that use the instance specified in this command.

98

--

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isthe locale of the machine where InfoSphere CDC is installed.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmshutdown -I MYINSTANCE -cInfoSphere CDC stops the specified instance withthe Normal option. The instance will only stop if no subscriptions are currentlyrunning. dmshutdown -I MYINSTANCE –aInfoSphere CDC stops the specified instance andends replication with the Abort option for all subscriptions that use the instance.Subscriptions that use the specified instance will end replication with an error.

99

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmsupportinfo - Collect IBM Support information Note: You should only run this command when the Management ConsoleSupportAssistant cannot connect to your InfoSphere® CDC datastore because it is notrunning or it will not run. Use this command (when requested by IBM® Technical Support) to collectInfoSphere CDC environment information in a generated .zip file that is used todiagnose and troubleshoot your support issue. Once the command has completed collecting information and generating the .zipfile, the output will display the full path and name of the .zip file. If you run thiscommand multiple times, the generated .zip files are numbered randomly. Note thatyou are responsible for deleting the generated .zip files when they are no longerrequired. Syntax dmsupportinfo [-I <INSTANCE_NAME>] [-t <"yyyy-MM-dd hh:mm:ss to yyyy-MM-dd hh:mm:ss">] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the name of the InfoSphere CDC instance. Alternatively, you canspecify the TSINSTANCE environment variable in place of this value.If you donot specify an instance (possibly because you could not create an instance),this command will only collect non-instance specific information.

-t <"yyyy-MM-dd hh:mm:ss to yyyy-MM-dd hh:mm:ss">Specifies the date and time range (relative to the time zone of the operatingsystem where you issue this command) used by InfoSphere CDC to retrieveenvironment information.Note: As a best practice, specify a date and time rangethat only captures the time period when you experienced problems. This allowsfor easier problem diagnosis and reduces the size of the files retrieved.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Example dmsupportinfo -I PRODUCTION -t "2009-12-03 08:00:00 to 2009-12-03 12:00:00"Retrieves support information for the Production instance from 8:00 AM to 12:00 PMon December 3, 2009. This is the time range when you experienced support issueswith this instance of InfoSphere CDC. Related concepts: Troubleshooting and contacting IBM Support

100

101

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmts32 - Start InfoSphere CDC Use this command to start a 32-bit instance of InfoSphere® CDC. Syntax dmts32 [-I <INSTANCE_NAME>] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the InfoSphere CDC instance for which you want to start.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmts32 -I -MYINSTANCEInfoSphere CDC starts for the specified instance.

102

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmts64 - Start InfoSphere CDC Use this command to start a 64-bit instance of InfoSphere® CDC. Syntax dmts64 [-I <INSTANCE_NAME>] [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the InfoSphere CDC instance for which you want to start.

-L <locale>The name of the locale used for the InfoSphere CDC instance. The default isyour machine's locale.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmts64 -I MYINSTANCEInfoSphere CDC starts for the specified instance.

103

IBM InfoSphere Change Data Capture, Version 10.2 dmmdcommander This command is for internal use only.

104

IBM InfoSphere Change Data Capture, Version 10.2 dmmdconsole This command is for internal use only.

105

-

-

---

IBM InfoSphere Change Data Capture, Version 10.2 User exits for InfoSphere CDC for Teradata A user exit lets you define a set of actions that InfoSphere® CDC can run before orafter a database event occurs on a specified table. User exits allow you tocustomize your environment to meet your business requirements. After compilingthe user exit, you can specify the user exit in Management Console. InfoSphere CDC provides two types of user exits:

Stored procedure—This type of user exit is run directly by the database engine andis generally faster at processing database requests.Java class—This type of user exit utilizes the InfoSphere CDC API. For moreinformation, see the API reference Javadocs.

Sample Java™ class user exits are also provided with InfoSphere CDC. You canextend or modify these samples to suit your environment. In this section, you will learn:

Stored procedure user exits for table and row level operations Sample Java class user exits for InfoSphere CDC for Teradata InfoSphere CDC API reference – Javadocs

106

----

IBM InfoSphere Change Data Capture, Version 10.2 Stored procedure user exits for table and row leveloperations A stored procedure is a program (or procedure) which is physically stored within adatabase. The advantage of a stored procedure is that when it is run, in response toa user request, it is run directly by the database engine, which usually runs on aseparate database server and is generally faster at processing database requests. After writing and compiling user exit programs, you can specify at which user exitpoint you want to invoke the user exit (either before or after a row-level or before orafter a table-level operation) on the User Exits tab of InfoSphere® CDC. See also:

Defining a stored procedure user exit Stored procedure user exit database connections Retrieving data with a stored procedure user exit Example of a stored procedure user exit

107

--

-

-

IBM InfoSphere Change Data Capture, Version 10.2 Defining a stored procedure user exit When defining a stored procedure user exit in InfoSphere® CDC, consider thefollowing:

Overloaded stored procedures are not supported.Stored procedure user exits must have at least two parameters, which must be thefirst two defined in the following order:

result—An integer output parameter that returns '0' if the stored procedure userexit is successful or a non-zero value if the stored procedure user exit is notsuccessful.returnMsg—A character output parameter that returns error messages to theEvent Log if the stored procedure user exit is not successful.

Related reference: Example of a stored procedure user exit

108

IBM InfoSphere Change Data Capture, Version 10.2 Stored procedure user exit database connections The stored procedure user exit program and InfoSphere® CDC use the sameshared connection as the default method to connect to the database. This settingensures that, by default, changes to tables made by InfoSphere CDC are visible tothe stored procedure user exit program.

109

-

-

-

-

---

IBM InfoSphere Change Data Capture, Version 10.2 Retrieving data with a stored procedure user exit You can retrieve data from your source table by passing system parameters to yourstored procedure. You can retrieve the following type of data:

Retrieve system values (s$)—when passed to a stored procedure, the s$ prefixmakes system values available from the source database to your storedprocedure. For example, s$entry identifies the entry point at which InfoSphere®CDC had run the user exit. Retrieve journal control fields (j$)—when passed to a stored procedure, the j$prefix makes journal control fields available from the source database to yourstored procedure. For example, j$USER identifies the operating system user nameof the person that made the update on the source table. This is useful if you areusing the stored procedure to audit table or row-level operations that haveoccurred on the source table.Retrieve data values—depending on the prefix you pass to the stored procedure,you can retrieve data from the source database and make it available to yourstored procedure. For example, you can use b$ to retrieve the before image of thesource column, or you can use k$ to access the target table to find the rows thatneed to be modified.

Each of these values can be used as input parameters for the stored procedure userexit that you write. The format used to retrieve data is slightly different depending onthe product that you are using:

For InfoSphere CDC, the format is <x>$<value>where <x> represents the prefix and <value> represents the name of the value to beretrieved. See also:

Retrieving system values using the s$ prefix Retrieving journal control fields using the j$ prefix Retrieving data values using b$, a$, k$, and d$ prefixes

110

IBM InfoSphere Change Data Capture, Version 10.2 Retrieving system values using the s$ prefix This prefix is used to retrieve system values. The table below presents and brieflydescribes these values.

Prefix and Value Data Type Description

111

s$entry NUMBER Represents the entrypoint from where thestored procedure wasinvoked. You caninvoke a storedprocedure from thefollowing entry points:1—indicates thatInfoSphere® CDChas invoked thestored procedurebefore a table clear(truncate)operation2—indicatesthat InfoSphere CDChas invoked thestored procedureafter a table clear(truncate)operation3—indicatesthat InfoSphere CDChas invoked thestored procedurebefore a row insertoperation4—indicatesthat InfoSphere CDChas invoked thestored procedureafter a row insertoperation5—indicatesthat InfoSphere CDChas invoked thestored procedurebefore a row updateoperation6—indicatesthat InfoSphere CDChas invoked thestored procedureafter a row updateoperation7—indicatesthat InfoSphere CDChas invoked thestored procedurebefore a row deleteoperation8—indicatesthat InfoSphere CDChas invoked thestored procedureafter a row deleteoperation9—indicatesthat InfoSphere CDChas invoked thestored procedurebefore a table refresh

112

operation10—indicates that InfoSphereCDC has invoked thestored procedureafter a table refreshoperation

s$srcSysId VARCHAR Identifies uniquely thelocation of the sourcedata.

s$srcTabId VARCHAR Represents the nameof the source table inthe source databasethat sends replicateddata to the target.

s$tgtTabId VARCHAR Represents the nameof the target table inthe target databasethat receivesreplicated data fromthe source.

113

IBM InfoSphere Change Data Capture, Version 10.2 Retrieving journal control fields using the j$ prefix This prefix is used to retrieve information about the operation that occurred on thesource system. You can use jb$ with InfoSphere® CDC to retrieve the sameinformation. Note: If you are replicating data using InfoSphere Change Data Capture for DB2®for i on the source system, then the value for j$ and jb$ with ENTT and SEQNjournal control fields will be different. jb$ENTT generates 'UB' to indicate that thebefore image of a row has been updated on the source table, and generates 'UP' toindicate that the after image of a row has been updated on the source table. Also, ifyou are using InfoSphere Change Data Capture for DB2 for i on the source system,then jb$SEQN generates an internal ID for the row within a transaction. The available values are listed:

Prefix and Value Data Type Descriptionj$CCID VARCHAR Identifies the

transaction with theinsert, update, ordelete operation.

j$CODE VARCHAR Identifies the type ofjournal or log entry,either “U” for arefresh operation or“R” for mirroring. TheIBM® i platform willsend “F” for file ortable-level entries.

j$CTRR orj$CNTRRN

VARCHAR Identifies the relativerecord number of thesource table thatrecorded thejournal/logentry.Note: CTRR orCNTRRN containsmeaningfulinformation when youinvoke your storedprocedure on theinsert entries thatmake up the refresh.The IBM i platformwill also fill this in onany insert, update, ordelete operation.

j$ENTT or j$ENTTYP VARCHAR Generates journal orlog codes that identifythe operation type onthe source system.

114

j$JRN or j$JOURNAL VARCHAR The name of thejournal/log whereInfoSphere CDC isreading insert,update, or deleteoperations from.

j$JOB VARCHAR Identifies the name ofthe job that made theinsert, update, ordelete on the sourcesystem.

j$MBR or j$MEMBER VARCHAR Identifies the name ofthe source table or itsalias.

j$NBR or j$JOBNO VARCHAR Identifies the processID of the program onthe source table thatis making the insert,update, or deleteoperation.

j$PGM orj$PROGRAM

VARCHAR Identifies the name ofthe program on thesource system thatmade the insert,update or deleteoperation.

j$SEQN or j$SEQNO VARCHAR Identifies thesequence number ofthe insert, update, ordelete operation inthe journal or log.

j$SYNM orj$SYSTEM

VARCHAR Identifies the hostname of the sourcesystem.

j$USER VARCHAR Identifies theoperating systemuser name that madethe insert, update, ordelete operation onthe source.

j$USPF VARCHAR Identifies thedatabase user namethat made the insert,update, or deleteoperation on thesource.

115

j$TSTP orj$TIMSTAMP

VARCHAR Identifies the dateand time of when theinsert, update, ordelete operation orrefresh was made onthe source. Inenvironments thatsupport microsecondprecision, the dateand time format ofthis journal controlfield is YYYY-MM-DD-HH:MM:SS.UUUUUU. Otherwise,InfoSphere CDC setsthe microsecondcomponent UUUUUUto zeroes or does notinclude it at all.

116

IBM InfoSphere Change Data Capture, Version 10.2 Retrieving data values using b$, a$, k$, and d$prefixes Four prefixes are used to retrieve data:

Prefix Mode Descriptionb$<source columnname>

Input Used to retrieve thebefore image of thedata in a sourcecolumn. The beforeimage is the originalimage from thesource table columnbefore anytransformation isapplied to it.For example, youmay have made thefollowing UPDATE toyour source table:UPDATE source_tableset MYCOLUMN = 2where MYCOLUMN = 1;

This will set 2 on allrows whereMYCOLUMN was 1before the executionof this SQLstatement.When you define astored procedure anddecide that you wantthe stored procedureto retrieve the beforeimage ofMYCOLUMN, youwould specify thefollowing:b$MYCOLUMN;

This returns a valueof 1.

117

a$<source columnname>

Input Used to retrieve theafter image of thedata in a sourcecolumn. The afterimage is thetranslated data fromthe source tablecolumn. For example,the data that wastranslated by aderived expression.For example, youmay have made thefollowing UPDATE toyour source table:UPDATE source_tableset MYCOLUMN = 2where MYCOLUMN = 1;

This will set 2 on allrows whereMYCOLUMN was 1before the executionof this SQLstatement.When you define astored procedure anddecide that you wantthe stored procedureto retrieve the afterimage ofMYCOLUMN, youwould specify thefollowing:a$MYCOLUMN;

This returns a valueof 2.

k$<target key columnname>

Input Used to access thetarget table to find therows that need to bemodified.Note: Keycolumns are notavailable for auditing.

d$<target columnname>

Input/Output Used to retrieve datavalues aftertransformation, whichwill be used to updatethe table in the targetdatabase. Only thesevalues may bemodified by thestored procedure.

118

119

IBM InfoSphere Change Data Capture, Version 10.2 Example of a stored procedure user exit The following code snippet is an example of a stored procedure user exit.

Code Commentscreate or replace procedurePROD.AUDIT_STPROC ( result OUT INT, returnMsg OUT CHAR, s$entry IN NUMBER, s$srcSysId IN CHAR, s$srcTabId IN CHAR, s$tgtTabId IN CHAR, j$ENTT IN CHAR, a$IDNO IN NUMBER, a$PRICE IN NUMBER, a$DESC IN CHAR, a$LONGDESC IN CHAR, a$TRANSDATE IN DATE, d$IDNO IN NUMBER, d$PRICE IN NUMBER, d$DESC IN CHAR, d$LONGDESC IN CHAR, d$TRANSDATE IN DATE )

The parameters you declare and want topass to your stored procedure must bevalid data types.The following parameters are mandatoryand must be declared in your storedprocedure:result—Returns a value of '0' if thestored procedure user exit is successful.If the stored procedure user exit is notsuccessful it will return a non-zero valueand a message will be sent to the EventLog.returnMsg—Returns an errormessage to the Event Log if the storedprocedure is not successful.The followingparameters have been declared in thisstored procedure:s$entry—Retrieves the entry point atwhich the stored procedure was called.In this example, InfoSphere® CDC callsthe user exit at every entrypoint.s$srcSysId—Retrieves the locationof source data.s$srcTabId—Retrievesthe name of the sourcetable.s$tgtTabId—Retrieves the name ofthe target table.j$ENTT—Retrieves thejournal code that indicates the type ofoperation on the sourcetable.a$—Retrieves the after image ofthe IDNO, PRICE, DESC, LONGDESC,and TRANSDATE sourcecolumns.d$—Retrieves the transformeddata of the IDNO, PRICE, DESC,LONGDESC, and TRANSDATA targetcolumns.

IS ENTRYPOINT VARCHAR(50); BEGIN CASE s$entryWHEN 16 THEN ENTRYPOINT :='User Exit program called Before Insert';WHEN 1048576 THEN ENTRYPOINT :='User Exit program called After Insert';WHEN 64 THEN ENTRYPOINT :='User Exit program called Before Update';WHEN 4194304 THEN ENTRYPOINT :='User Exit program called After Update';END CASE;

This stored procedure user exit can beinvoked from these entry points.

insert into PROD.AUDIT_TABLE1values (s$entry, s$srcSysId,s$srcTabId, s$tgtTabId,j$ENTT, a$IDNO, a$PRICE, a$DESC,a$LONGDESC, a$TRANSDATE, d$IDNO,d$PRICE, d$DESC, d$LONGDESC, d$TRANSDATE,ENTRYPOINT);

This stored procedure user exit willINSERT these values intoPROD.AUDIT_TABLE1.

120

result := 0; returnMsg := 'OK';END AUDIT_STPROC;

This stored procedure user exit issuccessful and returns a '0' value.Note: If your stored procedure returns anon-zero value because the storedprocedure is not successful, then anerror message is sent to the Event Log.

121

-

-

-

-

-

-

-

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 Sample Java class user exits for InfoSphere CDCfor Teradata InfoSphere® CDC provides sample user exits that you can extend or modify to suityour environment. The samples are found in samples.jar, which is located in thesamples directory in your InfoSphere CDC installation directory. The Java™ filecontains the following samples:

CRUserExitSample.java—A conflict resolution user exit that can be used withtables having a primary key column of any data type or a numeric column with anydata type. This sample is located incom.datamirror.ts.target.publication.userexit.cdr.DEUserExitSample.java—Used in expressions using the %USERFUNC columnfunction. It calculates the sum of the user-supplied parameters (in the expression)and returns the sum incremented by 1. This sample is located incom.datamirror.ts.derivedexpressionmanager.SPUserExitSample.java—Calls a stored procedure with the image coming fromthe source. This sample is located incom.datamirror.ts.target.publication.userexit.sample.UserExitSample.java—Subscribes to replication events to retrieve the details ofthe events which took place. This sample is located incom.datamirror.ts.target.publication.userexit.sample.UserExitSample1.java—Records new rows inserted into a table on the target andstores them in a text file. The user specifies the name of the text file as aparameter. This sample is located incom.datamirror.ts.target.publication.userexit.sample.

Note the following: To run the sample user exits without modifying them, you must specify the fullyqualified path to the compiled user exit in Management Console. For example,com.datamirror.ts.target.publication.userexit.sample.UserExitSample.Compiled sample user exits are located in the ts.jar file which is found in the libdirectory in your InfoSphere CDC installation directory. Note that the compiled userexits in the ts.jar file have a *.class extension.If you want to modify the sample user exits, you must compile the user exit afteryou make changes to the source code.The user exit class must also be in the InfoSphere CDC runtime classpath.

For more information on how to specify Java class or Stored Procedure user exits inManagement Console, see your Management Console documentation. See also:

To compile the sample Java class user exits (Windows)

122

1.2.

3.4.

5.

6.7.

IBM InfoSphere Change Data Capture, Version 10.2 To compile the sample Java class user exits(Windows)

Stop InfoSphere® CDC.Unzip the samples.jar file into the lib folder in your InfoSphere CDC installationfolder. Make sure you maintain the folder structure when unzipping the jar file.After unzipping the jar file, you will have a folder structure like the following:<installation_folder>\lib\com\datamirror\ts\target\publication\userexit\sample Make your changes to the sample user exit.Compile the modified user exit. For example, if you want to compileUserExitSample.java, open a command window, navigate to the lib folder andissue the following command:javac -classpath ts.jar;.com\datamirror\ts\target\publication\userexit\sample

\UserExitSample.java If this command runs successfully, there will be no output on your screen. Note: Your system must have the Java™ JDK to run this command. After running the command successfully, navigate to the following directory andconfirm that you have created a UserExitSample.class file:<installation_directory>\lib\com\datamirror\ts\target

\publication\userexit\sample Start InfoSphere CDC.The final step to configure the user exit is to specify the fully qualified path toUserExitSample in Management Console. For example:com.datamirror.ts.target.publication.userexit.sample.UserExitSample Note: Do not specify the .class extension.

For more information on how to specify Java class user exits in ManagementConsole, see your Management Console documentation. Note: If you plan to use the sample user exits in production environments, you willhave to test the samples before they are deployed. IBM® does not assumeresponsibility for adverse results caused by modified or customized user exitclasses.

123

--

IBM InfoSphere Change Data Capture, Version 10.2 InfoSphere CDC API reference – Javadocs The API reference is available in Javadoc format in your InfoSphere® CDCinstallation directory. To view the API reference, navigate to the api directory belowand click the index.html file to open the Javadoc documentation in your browser:

Windows—<InfoSphere CDC installation directory>\docs\apiUNIX—<InfoSphere CDC installation directory>/docs/api

124

--

IBM InfoSphere Change Data Capture, Version 10.2 Uninstalling InfoSphere CDC for Teradata This section provides step-by-step instructions on how to uninstall InfoSphere®CDC. In this section, you will learn:

To uninstall InfoSphere CDC for Teradata (Windows) To uninstall InfoSphere CDC for Teradata (UNIX and Linux)

125

1.2.3.

4.

IBM InfoSphere Change Data Capture, Version 10.2 To uninstall InfoSphere CDC for Teradata(Windows)

Go to Windows Control Panel > Add or Remove Programs.Locate IBM®InfoSphere® Change Data Capture and click Change/Remove.Click Uninstall on the uninstall wizard. This deletes your all your InfoSphere CDCinstances under this installation.Click Done after the uninstallation has completed.

126

1.2.

3.

4.5.6.

7.

IBM InfoSphere Change Data Capture, Version 10.2 To uninstall InfoSphere CDC for Teradata (UNIX andLinux)

Stop InfoSphere® CDC by using the dmshutdown command.At the command prompt, launch the configuration tool by issuing the followingcommand from the <InfoSphere CDC installation directory>/bin directory:./dmconfigurets Enter 1 and press Enter to list the installed instances of InfoSphere CDC. Recordthe names of all these instances. Uninstalling InfoSphere CDC is simply deletingthe InfoSphere CDC instances.Enter 4 and press Enter to delete the first instance of InfoSphere CDC.Enter the instance name that you want to delete and press Enter.Repeat the above steps to delete all the InfoSphere CDC instances you recordedpreviously.Delete the InfoSphere CDC installation directory.

127

---

--

-

IBM InfoSphere Change Data Capture, Version 10.2 Troubleshooting If you encounter issues while running InfoSphere® CDC, you have a number ofoptions for tracking and troubleshooting issues to help with problem resolution. There are three methods that you can use in InfoSphere CDC for tracking andtroubleshooting issues:

Data Collection with the IBM® Support Assistant (ISA DC)Management Console Support AssistantThe dmsupportinfo command, which is executed on the replication engine

If you are trying to troubleshoot issues with InfoSphere CDC version 10.2 or later onLinux, UNIX and Windows operating systems, you should use the ISA DC toolunless otherwise instructed by IBM Technical Support. In this section, you will learn:

Using the IBM Support Assistant (ISA DC) Locating log files In addition to the Management Console event log, InfoSphere CDC producesother logs to help troubleshoot installation and replication errors.Troubleshooting and contacting IBM Support

128

-

-

--

---

-

IBM InfoSphere Change Data Capture, Version 10.2 Using the IBM Support Assistant (ISA DC) You can use the IBM® Support Assistant Data Collection tool (ISA DC) to collectInfoSphere® CDC data to provide to IBM Technical Support to assist you introubleshooting issues with InfoSphere CDC, to request a product enhancement orto ask a question about InfoSphere CDC. ISA DC can be used with InfoSphere CDC replication engines that are version 10.2or later, except InfoSphere CDC for z/OS®. The ISA DC tool is included in the InfoSphere CDC installation process, and doesnot require configuration. The executable files are located in the isa folder in theInfoSphere CDC directory. Simply run the isadc.bat, isadc.sh or index.html file, asappropriate, to launch the tool. Prerequisites and considerations for using ISA DC Prerequisites: The following prerequisite must be satisfied on the machine on which ISA DC will berun, in order to successfully use the tool:

IBM JRE/JDK version 1.6 or laterConsiderations: The following issues should be taken into consideration before you attempt to useISA DC:

ISA DC cannot be run remotely. It must be run on the machine where the instanceis configured.ISA DC cannot be used to collect data from InfoSphere CDC for z/OS.If InfoSphere CDC is installed but you have not configured an instance or areunable to configure an instance, ISA DC can still be used to collect minimal data toassist IBM Technical Support in resolving the issue.

See also:

To use ISA DC to collect data for a product problem (command line) To use ISA DC to collect data for a product problem (GUI) To use ISA DC to collect data for a question or an enhancement request(command line) To use ISA DC to collect data for a question or an enhancement request (GUI)

129

1.

2.

3.

4.5.

6.7.8.

9.

10.

11.

12.

13.

A.

IBM InfoSphere Change Data Capture, Version 10.2 To use ISA DC to collect data for a product problem(command line)

Launch the IBM® Support Assistant.Run the isadc.bat or isadc.sh file, located inthe isa\isadc folder in the root directory of the InfoSphere® CDC instance. Enter 1 to accept the license agreement and press Enter.After the licenseagreement has been accepted, it will not be shown again. Provide a file name and press Enter.The name provided will be given to the .zipfile containing the data collection results. If you do not want to assign a name to the data collection results, press Enterand a default name will be used. Enter 1 to confirm your chosen file name and press Enter to continue.Enter 1 to run the InfoSphere Change Data CaptureSupport Assistant DataCollector and press Enter.The Welcome page is displayed. Read the Welcome page information and enter 1 to proceed. Press Enter.Enter 1 to collect data for a product problem and press Enter.Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 andpress Enter. Select the name of the InfoSphere CDC instance for which data will be collected.If you have multiple instances of InfoSphere CDC configured, you will be askedto select which instance for which you want to collect. Enter the correspondingnumber for the instance name and press Enter. If you have a single InfoSphere CDC instance configured, it will be selectedautomatically and this step will be skipped. Even if you do not have an instance configured, ISA DC will still collect whatdata is available. If no instance is configured, you can skip to Step 14. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 andpress Enter. If your selected instance is not running, you will be alerted by ISA DC. As onlyminimal data is available if the instance is stopped, it is preferable that theinstance be running during data collection.Try to start your instance. When theinstance is running, enter 1 and press Enter. If you cannot start your instance and want to continue the data collectionprocess, enter 2 and press Enter. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 andpress Enter. If the instance is running, you will be asked for information regarding when theproblem occurred.

Enter the date and time when you think the problem began and press Enter.This information must be entered in the following format: yyyy-mm-ddhh:mm:ss

130

B.

C.

D.

14.

-

-

-

-

15.

16.

17.A.

B.

C.

D.

Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter. Determine the period of time for which the data will be collected and pressEnter.The amount specified will be applied as a before value and an aftervalue to the date and time specified previously. For example, if you select 1Day as the time period, data will be collect for 24 hours before the specifieddate and time and for the 24 hours after the specified date and time. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

Select the method to transfer the data collection archive file and press Enter.Choose one of the following options:

Send using secure transfer to IBM Support (HTTPS)—Sends the .zip file toIBM Support using a secure protocol.Send using FTP to IBM Support (unencrypted)—Sends the .zip file to IBMSupport using an unencrypted protocol.Send using FTP to another location (unencrypted)—Sends the .zip file to arecipient of your choice, using an unencrypted protocol.End the collection without sending—Ends the data collection and createsthe .zip file, but does not transfer it.

Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 andpress Enter. If you chose to end the collection without sending the output, ISA DC will notifyyour when the .zip file has been successfully created. Enter 1 and press Enter toexit the application.If you chose to transfer the file using HTTPS, follow these steps:

If you want to receive a confirmation email when the upload was successful,enter an email address and press Enter. If you do not want to receiveconfirmation, press Enter to continue. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter. Enter the PMR number that was given to you by IBM Technical Support andpress Enter. Ensure that the PMR number follows the required namingconvention of PMRNumber.BranchNumber.CountryCode. If an unknownPMR number is entered, you will be asked to correct the PMR number andre-send the data. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

131

18.

A.

B.

19.A.B.C.D.E.

20.

If you chose to transfer the file to IBM Technical Support using unencryptedFTP, follow these steps:

Enter the PMR number that was given to you by IBM Technical Support andpress Enter. Ensure that the PMR number follows the required namingconvention of PMRNumber.BranchNumber.CountryCode. If an unknown PMRnumber is entered, you will be asked to correct the PMR number and re-sendthe data. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

If you chose to transfer the file using unencrypted FTP, follow these steps:Enter the FTP host name and press Enter.Enter the user name and press Enter.Enter the password for the user name and press Enter.Enter the path for the directory on the FTP server and press Enter.Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

When you receive notice that the operation has completed successfully, enter 1and press Enter to exit the application.

132

1.

2.

3.4.5.6.7.

8.

9.

10.

-----

11.

12.

A.B.

IBM InfoSphere Change Data Capture, Version 10.2 To use ISA DC to collect data for a product problem(GUI)

Launch the IBM® Support Assistant.Run the index.html file, located in theisa\isadc folder in the root directory of the InfoSphere® CDC instance. Read the license agreement and click OK to accept it.After the licenseagreement has been accepted, it will not be shown again. Click Start.The Welcome screen opens. Click OK.Select A product problem from the drop down box.Click OK.Select the name of an InfoSphere CDC instance from the drop down list andclick OK.If you have multiple instances of InfoSphere CDC configured, you willbe asked to select which instance for which you want to collect. If you have a single InfoSphere CDC instance configured, it will be selectedautomatically and this step will be skipped. If your selected instance is not running, you will be alerted by ISA DC. As onlyminimal data is available if the instance is stopped, it is preferable that theinstance be running during data collection.Try to start your instance. When theinstance is running, select Yes, I have started the instance from the drop downbox and click OK. If you cannot start your instance and want to continue the data collectionprocess, select No, continue with minimal data collection from the drop downbox and click OK. If the instance is running, you will be asked for information regarding when theproblem occurred. Enter the date and time when you think the problem beganand click OK.This information must be entered in the following format: yyyy-mm-dd hh:mm:ss. Determine the period of time for which the data will be collected and click OK.Choose one of the following values:

6 hours12 hours1 Day2 Days7 Days

The amount specified will be applied as a before value and an after value to thedate and time specified previously. For example, if you select 1 Day as the timeperiod, data will be collect for 24 hours before the specified date and time andfor the 24 hours after the specified date and time. If you chose to end the collection without sending the output, select Do nottransfer data to IBM. ISA DC will notify you when the .zip file has beensuccessfully created.If you want to transfer the data to IBM using a secure transfer (HTTPS), selectthe Transfer to IBM option.

Choose the HTTPS transfer type option.Enter the PMR number that was given to you by IBM Technical Support.Ensure that the PMR number follows the required naming convention ofPMRNumber.BranchNumber.CountryCode. If an unknown PMR number is

133

C.D.

13.

A.B.

C.14.

A.

B.C.D.E.

15.

entered, you will be asked to correct the PMR number and re-send the data. Enter your email address.Click Transfer.

If you want to transfer the data to IBM using unencrypted FTP, select theTransfer to IBM option.

Choose the FTP transfer type option.Enter the PMR number that was given to you by IBM Technical Support.Ensure that the PMR number follows the required naming convention ofPMRNumber.BranchNumber.CountryCode. If an unknown PMR number isentered, you will be asked to correct the PMR number and re-send the data. Click Transfer.

If you choose to send the data to a location other than IBM using unencryptedFTP, click Transfer to another server via FTP

Enter the email address or IP address of the recipient in the Hotmail/IPAddress field.Enter the user name.Enter the password.Enter the path for the directory on the FTP server.Click Transfer.

When you receive notice that the operation has completed successfully, clickBrowse directory if you want to see the file you created or click Start NewCollection to collect more data.To exit the application, close your browser tab orwindow.

134

1.

2.

3.

4.5.

6.7.

8.

9.

-

-

-

-

10.

11.

12.A.

B.

C.

IBM InfoSphere Change Data Capture, Version 10.2 To use ISA DC to collect data for a question or anenhancement request (command line)

Launch the IBM® Support Assistant.Run the isadc.bat or isadc.sh file, located inthe isa\isadc folder in the root directory of the InfoSphere® CDC instance. Enter 1 to accept the license agreement and press Enter.After the licenseagreement has been accepted, it will not be shown again. Provide a file name and press Enter.The name provided will be given to the .zipfile containing the data collection results. If you do not want to assign a name to the data collection results, press Enterand a default name will be used. Enter 1 to confirm your chosen file name and press Enter to continue.Enter 1 to run the InfoSphere Change Data CaptureSupport Assistant DataCollector and press Enter.The Welcome page is displayed. Read the Welcome page information and enter 1 to proceed. Press Enter.Enter 2 to collect data for a question or an enhancement request and pressEnter.Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 andpress Enter. Select the method to transfer the data collection archive file and press Enter.Choose one of the following options:

Send using secure transfer to IBM Support (HTTPS)—Sends the .zip file toIBM Support using a secure protocol.Send using FTP to IBM Support (unencrypted)—Sends the .zip file to IBMSupport using an unencrypted protocol.Send using FTP to another location (unencrypted)—Sends the .zip file to arecipient of your choice, using an unencrypted protocol.End the collection without sending—Ends the data collection and createsthe .zip file, but does not transfer it.

Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3 andpress Enter. If you chose to end the collection without sending the output, ISA DC will notifyyour when the .zip file has been successfully created. Enter 1 and press Enter toexit the application.If you chose to transfer the file using HTTPS, follow these steps:

If you want to receive a confirmation email when the upload was successful,enter an email address and press Enter. If you do not want to receiveconfirmation, press Enter to continue. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter. Enter the PMR number that was given to you by IBM Technical Support andpress Enter. Ensure that the PMR number follows the required naming

135

D.

13.

A.

B.

14.A.B.C.D.E.

15.

convention of PMRNumber.BranchNumber.CountryCode. If an unknownPMR number is entered, you will be asked to correct the PMR number andre-send the data. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

If you chose to transfer the file to IBM Technical Support using unencryptedFTP, follow these steps:

Enter the PMR number that was given to you by IBM Technical Support andpress Enter. Ensure that the PMR number follows the required namingconvention of PMRNumber.BranchNumber.CountryCode. If an unknown PMRnumber is entered, you will be asked to correct the PMR number and re-sendthe data. Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

If you chose to transfer the file using unencrypted FTP, follow these steps:Enter the FTP host name and press Enter.Enter the user name and press Enter.Enter the password for the user name and press Enter.Enter the path for the directory on the FTP server and press Enter.Enter 1 to process your input and continue collecting data. Press Enter.If youwant to cancel the collection, enter 2 and press Enter. If you want to go back and change your input for the previous step, enter 3and press Enter.

When you receive notice that the operation has completed successfully, enter 1and press Enter to exit the application.

136

1.

2.

3.4.5.6.7.

8.

A.B.

C.D.

9.

A.B.

C.10.

A.

B.C.D.E.

11.

IBM InfoSphere Change Data Capture, Version 10.2 To use ISA DC to collect data for a question or anenhancement request (GUI)

Launch the IBM® Support Assistant.Run the index.html file, located in theisa\isadc folder in the root directory of the InfoSphere® CDC instance. Read the license agreement and click OK to accept it.After the licenseagreement has been accepted, it will not be shown again. Click Start.The Welcome screen opens. Click OK.Select A question or enhancement request from the drop down box.Click OK.If you chose to end the collection without sending the output, select Do nottransfer data to IBM. ISA DC will notify you when the .zip file has beensuccessfully created.If you want to transfer the data to IBM using a secure transfer (HTTPS), selectthe Transfer to IBM option.

Choose the HTTPS transfer type option.Enter the PMR number that was given to you by IBM Technical Support.Ensure that the PMR number follows the required naming convention ofPMRNumber.BranchNumber.CountryCode. If an unknown PMR number isentered, you will be asked to correct the PMR number and re-send the data. Enter your email address.Click Transfer.

If you want to transfer the data to IBM using unencrypted FTP, select theTransfer to IBM option.

Choose the FTP transfer type option.Enter the PMR number that was given to you by IBM Technical Support.Ensure that the PMR number follows the required naming convention ofPMRNumber.BranchNumber.CountryCode. If an unknown PMR number isentered, you will be asked to correct the PMR number and re-send the data. Click Transfer.

If you choose to send the data to a location other than IBM using unencryptedFTP, click Transfer to another server via FTP

Enter the email address or IP address of the recipient in the Hotmail/IPAddress field.Enter the user name.Enter the password.Enter the path for the directory on the FTP server.Click Transfer.

When you receive notice that the operation has completed successfully, clickBrowse directory if you want to see the file you created or click Start NewCollection to collect more data.To exit the application, close your browser tab orwindow.

137

-

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 Locating log files In addition to the Management Console event log, InfoSphere® CDC producesother logs to help troubleshoot installation and replication errors. Review the log files in the <CDC_installation directory>\Uninstall\Logs directoryif you encounter any errors during the installation of InfoSphere CDC. If you encounter replication errors or replication stops, review any of these tracelogs:

<CDC_installation_directory>/log—This directory contains information for anInfoSphere CDC problem. Refer to this directory if the problem is related toconfiguring an InfoSphere CDC instance. However, it is always useful to refer thisdirectory as well as the <CDC_installation_directory>/instance/<instance_name>/log directory to troubleshoot any problem.<CDC_installation_directory>/instance/<instance_name>/log—This directorystores trace files for a specific InfoSphere CDC instance. It is also useful to refer tothe <CDC_installation_directory>/instance/<instance_name>/log directory totroubleshoot your problem. When tracing has been enabled, the trace files will beenabled under <CDC_installation_directory>/instance/<instance_name>/log/on.<CDC_installation_directory>/instance/<instance_name>/tmp—This directorytemporarily stores data such as incomplete large transactions and large LOB datavalues.<CDC_installation_directory>/instance/<instance_name>/stagingstore—Thisdirectory stores sincle scrape staging store data that does not fit in memory. Whenan InfoSphere CDC instance is stopped normally, the contents of this staging storeare written to files that are stored in this directory.

138

-

-

IBM InfoSphere Change Data Capture, Version 10.2 Troubleshooting and contacting IBM Support The following support page contains the latest troubleshooting information anddetails on how to open a service request with IBM® Support:

http://www.ibm.com/software/data/infosphere/support/change-data-capture/ For contact information in your region:

http://www.ibm.com/planetwide/ Related reference: dmsupportinfo - Collect IBM Support information

139