7 System requirements for InfoSphere CDC for Informix 10 11 12

InfoSphere CDC for Informix (Version 10.2) 4About InfoSphere CDC and InfoSphere CDC Management Console 7System requirements for InfoSphere CDC for Informix 10Hardware and software requirements 11Running in a virtualization environment 12Disk space requirements 13RAM requirements 15Port requirements 16Understanding how InfoSphere CDC interacts with your database 17Before you install InfoSphere CDC for Informix 19User account requirements 20Configuring Informix Dynamic Server to use the Informix Change Data Capture API 21To configure Informix Dynamic Server to use the InfoSphere CDC API 22Calculating database connections required by InfoSphere CDC for Informix 23Assessing disk space and memory requirements 25Understanding the importance of an appropriately configured disk subsystem 27Understanding the InfoSphere CDC memory footprint 28Database partition changes 29Creating queues in JMS providers 30Understanding change management 31Understanding DDL awareness 32Preparing for a planned DDL change 34To resume mirroring after a DDL change using the command line 35To resume mirroring after a DDL change using Management Console 38Understanding the Informix Error Code 83793 'table has pending in-place alter' 42Installation checklist 43Installing or upgrading InfoSphere CDC for Informix 44Installing InfoSphere CDC for Informix using an interactive installation 45To install InfoSphere CDC for Informix (Windows) 46To install InfoSphere CDC for Informix (UNIX and Linux) 47To override the locale for the installation (UNIX and Linux) 48Installing InfoSphere CDC for Informix using a silent installation 49To perform a silent installation of InfoSphere CDC (UNIX and Linux) 50Upgrading InfoSphere CDC for Informix 51To upgrade InfoSphere CDC for Informix (Windows) 53To upgrade InfoSphere CDC for Informix (UNIX and Linux) 54Configuring Informix for InfoSphere CDC replication 56To configure Informix for InfoSphere CDC replication 57Configuring InfoSphere CDC for Informix (Windows) 58Configuring InfoSphere CDC for Informix instances (Windows) 59To add a new instance of InfoSphere CDC for Informix (Windows) 60To edit an instance of InfoSphere CDC for Informix (Windows) 65To delete an instance of InfoSphere CDC for Informix (Windows) 66Configuring InfoSphere CDC for Informix (UNIX and Linux) 67Configuring InfoSphere CDC instances (UNIX and Linux) 68To add a new instance of InfoSphere CDC for Informix (UNIX and Linux) 69To edit an instance of InfoSphere CDC for Informix (UNIX and Linux) 72

To delete an instance of InfoSphere CDC for Informix (UNIX and Linux) 73Configuring InfoSphere CDC for Informix for OS (operating system) clustering (UNIX and Linux)74Performing a forced or manual failover of InfoSphere CDC for Informix 75Preparing for a failover of InfoSphere CDC for Informix 76After you install and configure InfoSphere CDC for Informix 77Starting InfoSphere CDC for Informix 78To start InfoSphere CDC for Informix (Windows) 79To start InfoSphere CDC for Informix (UNIX and Linux) 80Stopping InfoSphere CDC for Informix 81To stop InfoSphere CDC for Informix (Windows) 82To stop InfoSphere CDC for Informix (UNIX and Linux) 83Performing an external refresh 84To perform an external refresh 87Creating the syscdcv1 database 88To create the syscdcv1 database 89Maintaining active TCP connections in a network environment 90To maintain active TCP connections 91Enabling SQL statements in Management Console 92To enable SQL statements in Management Console 93InfoSphere CDC for Informix metadata tables 94Data types supported by InfoSphere CDC for Informix 95System parameters for InfoSphere CDC for Informix 96Commands for InfoSphere CDC for Informix 97Using the InfoSphere CDC for Informix commands 98Setting the TSINSTANCE environment variable 99Controlling replication commands 100dmendreplication - End replication 101dmrefresh - Refresh subscription 105dmstartmirror - Start mirroring 107Database transaction log commands 110dmdecodebookmark - Display verbose information bookmark 111dmsetbookmark - Set bookmark 112dmshowbookmark - Display bookmark information 114dmshowlogdependency - Show Log Dependency 116Exporting and importing configuration commands 118dmexportconfiguration - Export InfoSphere CDC Configuration 119dmimportconfiguration - Import InfoSphere CDC Configuration 120Managing tables for replication commands 121dmdescribe - Describe source tables 122dmflagforrefresh - Flag for Refresh 123dmmarktablecapturepoint - Mark a table capture point on a source table 124dmpark - Park table 126dmreaddtable - Update source table definition 128dmreassigntable - Update target table definition 129dmsetreplicationmethod - Set replication method 130Monitoring replication commands 132dmclearevents - Clear events 133

dmgetsubscriptionstatus - Get subscription status 134dmshowevents - Display InfoSphere CDC events 135Other commands 137dmbackupmd - Back up metadata 138dmconfigurets - Configure InfoSphere CDC 139dmmarkexternalunloadstart - Start table data unload 140dmmarkexternalunloadend - End table data unload 141dmmdcommander 142dmmdconsole 143dmset - Set InfoSphere CDC system parameter 144dmshowversion - Show InfoSphere CDC version 145dmshutdown - Shut down InfoSphere CDC 146dmsupportinfo - Collect IBM Support information 149dmterminate - Terminate InfoSphere CDC processes 151dmts32 - Start InfoSphere CDC 152dmts64 - Start InfoSphere CDC 153User exits for InfoSphere CDC for Informix 154Sample Java class user exits for InfoSphere CDC for Informix 155To compile the sample Java class user exits (Windows) 156To compile the sample Java class user exits (UNIX and Linux) 157InfoSphere CDC API reference - Javadocs 158Conflict resolution audit table 159Structure of the conflict resolution audit table 160Row image format 163Truncated images 164Unaudited data types 165Uninstalling InfoSphere CDC for Informix 166To uninstall InfoSphere CDC for Informix (Windows) 167To uninstall InfoSphere CDC for Informix (UNIX and Linux) 168Troubleshooting 169Using the IBM Support Assistant (ISA DC) 170To use ISA DC to collect data for a product problem (command line) 171To use ISA DC to collect data for a product problem (GUI) 174To use ISA DC to collect data for a question or an enhancement request (command line) 176To use ISA DC to collect data for a question or an enhancement request (GUI) 178Locating log files 179Troubleshooting and contacting IBM Support 180

-

-

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 About InfoSphere CDC and InfoSphere CDCManagement Console 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.

In this section, you will learn:

5

Related information: Supported sources and targets

6

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.sysreq.doc/concepts/supportedsourceandtargets.html

-

-

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 About InfoSphere CDC and InfoSphere CDCManagement Console 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.

In this section, you will learn:

8

Related information: Supported sources and targets

9

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.sysreq.doc/concepts/supportedsourceandtargets.html

-----

IBM InfoSphere Change Data Capture, Version 10.2 System requirements for InfoSphere CDC forInformix® 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 Running in a virtualization environment Disk space requirements RAM requirements Port requirements

10

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/hardwareandsoftwarerequirements.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/runninginavirtualizationenvironment.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/diskspacerequirements.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/ramrequirements.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/portrequirements.html

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

11

https://ibm.biz/BdxyzE

https://ibm.biz/Bdxyd5

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

12

http://www-01.ibm.com/software/support/virtualization_policy.html

http://www-01.ibm.com/software/support/virtualization_policy.html

--

---

IBM InfoSphere Change Data Capture, Version 10.2 Disk space requirements

InfoSphere CDC may require additional disk space in the following situations:

You are running large batch transactions in the database on your source system.You are configuring multiple subscriptions and one of your subscriptions is latent.In this type of scenario, InfoSphere CDC on your source system may persisttransaction queues to disk if RAM is not available.You are replicating large LOB data types.You are replicating "wide" tables that have hundreds of columns.You are performing regular back ups of your metadata with the dmbackupmdcommand-line utility.

Related concepts: Hardware and software requirements RAM requirements Port requirements Configuring InfoSphere CDC for Informix (Windows) Configuring InfoSphere CDC for Informix (UNIX and Linux)

Disk spaceInfoSphere® CDC source system:5 GB—For installation files, dataqueues, and log files.Global disk quota—Disk space is requiredon your source system for this quota which is used to store in-scope change data that has not been committed in your database.The amount of disk space required is determined by yourreplication environment and the workload of your source database.Use the mirror_global_disk_quota_gb system parameter toconfigure the amount of disk space used by this quota.InfoSphere CDC target system:1 GB—The minimum amount ofdisk space allowed for the disk quota for each instance ofInfoSphere CDC. The minimum value for this quota is sufficient forall instances created on your target system. Use the InfoSphereCDC configuration tool to configure the disk space for this quota.5GB—For installation files, data queues, and log 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.

13




https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/configuringcdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/configuringcdc_unixandlinux.html

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. InfoSphere CDC source deployments may require additional RAM in the followingscenarios:

You are replicating large LOB data types with your InfoSphere CDC sourcedeployment. These data types are sent to target while being retrieved from thesource database. The target waits until all LOBs (for each record) are receivedbefore applying a row. LOBs are stored in memory as long as there is adequateRAM, otherwise they are written to disk on the target.You are replicating "wide" tables with hundreds of columns.You are performing large batch transactions in your source database rather thanonline transaction processing (OLTP).

Related concepts: Hardware and software requirements Disk space requirements Port requirements Configuring InfoSphere CDC for Informix (Windows) Configuring InfoSphere CDC for Informix (UNIX and Linux)

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.Note:InfoSphere CDC is predominantly a Java-based application.However, some portions of it are written in C. These portions ofInfoSphere CDC are not subject to the memory limits specified forthe JVM

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: Hardware and software requirements Disk space requirements RAM requirements Maintaining active TCP connections in a network environment Configuring InfoSphere CDC for Informix (Windows) Configuring InfoSphere CDC for Informix (UNIX and Linux)

Protocol Default port PurposeTCP 10201 Accepts connections

from:ManagementConsoleOtherinstallations ofInfoSphere CDC as asource ofreplicationCommandline utilities

16




https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/maintainactivetcpconnnections.html



---

IBM InfoSphere Change Data Capture, Version 10.2 Understanding how InfoSphere CDC interacts withyour database When InfoSphere® CDC interacts with your database, by reading its logs orapplying data to its tables, it creates a dependency on your database. Thisdependency manifests itself in several ways:

Log managementResource utilization and availabilityChange management

Log management Log management requires that you keep the logs from which InfoSphere CDC readsuntil such time as InfoSphere CDC has replicated data from them. Thedmshowlogdependency command, available for most InfoSphere CDC engines,informs you of those database logs on which InfoSphere CDC continues to depend.Database logs should not be removed until such time as they no longer appear inthe list of logs displayed when the command is issued. The consequences of not adhering to this policy are that InfoSphere CDC will eitherend with an error or appear to hang as it waits for the log files to become availableto read, depending on the database. If the log files have been deleted and arepermanently unavailable then you will have no option but to refresh the data.InfoSphere CDC cannot skip logs while maintaining data integrity as it will neverknow what data would be missed in the log files so skipped. For InfoSphere CDC for Informix®, the Informix Log API requires access to onlinelogs, not archived logs. Resource utilization and availability InfoSphere CDC is frequently installed on the same server as the database fromwhich it is replicating or to which it is replicating. For this reason, it is important toensure that the memory allocated for use by InfoSphere CDC is actually physicallyavailable on the machine. By default, some databases can be configured to use allavailable memory on the machine. Such a configuration will not work for InfoSphereCDC, as it will have no memory with which to run. At least the amount of memoryallocated to InfoSphere CDC will need to be set aside from the database to ensurethat InfoSphere CDC will be able to run. Symptoms of resource starvation include many variations on InfoSphere CDC failingdue to out of memory conditions, communications failures, very high latency,timeout errors, and others. Change management Sometimes referred to as schema evolution, change management refers to thenecessity of planning changes to the structure of database tables that InfoSphereCDC is replicating and coordinating those changes with the operation of InfoSphereCDC to ensure that the changes do not disrupt replication. The database and InfoSphere CDC must share the same understanding of thestructure of the tables being replicated. Without a shared understanding,InfoSphere CDC will interpret the table data incorrectly, and thereby replicate thatdata incorrectly. InfoSphere CDC endeavours to protect users from potential dataloss or corruption resulting from uncoordinated table structure changes, but it is not

17

always able to do. In order to minimize recovery efforts resulting from uncoordinatedtable structure changes, it is a best practice to follow the change managementprocedures appropriate to your database. Coordinating change managementbetween the database and InfoSphere CDC will ensure smooth continuity ofreplication with minimal effort. Please note that change management practices applyto the tables in both source and target databases. Recognizing that some table structure changes are inadvertently performed, technotes are also available to assist you in recovering from uncoordinated tablestructure changes.

18

--------

IBM InfoSphere Change Data Capture, Version 10.2 Before you install InfoSphere CDC for Informix® 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:

User account requirements Configuring Informix Dynamic Server to use the Informix Change Data Capture API Calculating database connections required by InfoSphere CDC for Informix Assessing disk space and memory requirements Understanding the importance of an appropriately configured disk subsystem Understanding the InfoSphere CDC memory footprint Database partition changes Creating queues in JMS providers

19

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/requireduseraccounts.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/configuringinformixtoiusecdc.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/calculatingdatabaseconnections.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/assessingdiskspaceandmemoryrequirements.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/understandingtheimportanceofanappropriatelyconfigureddisksubsystem.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/understandingtheinfospherecdcmemoryfootprint.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/databasepartitionchanges.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/creatingqueuesforjmsproviders.html

-

-

IBM InfoSphere Change Data Capture, Version 10.2 User account requirements Setting up a Windows user account If you are installing InfoSphere® CDC on a Windows system, you must set up anew, or decide on an existing Windows account that you will use to install, configure,or upgrade InfoSphere CDC. Setting up a UNIX user account When you are installing InfoSphere CDC on a UNIX machine, you must set up anew, or decide on an existing UNIX account that you will use to install, configure, orupgrade InfoSphere CDC. You can install InfoSphere CDC in the directory of yourchoice, however, it must be owned by the UNIX account. Informix database user account The database user account must be a part of the informix group and must begranted DBA privileges on the database. Understanding the Informix database requirements To meet the database requirements for using Informix® Change Data Capture toreplicate data, you must have the following:

An Informix database with which you want to replicate data on your system. Seethe IBMInformix Getting Started Guide if you have not installed the product andhave not set up an Informix database.Both the sysmaster and sysadmin databases in your Informix instance in order tosuccessfully replicate data using InfoSphere CDC. For information on thesedatabases, see the IBM®Informix support documentation.

20

-

IBM InfoSphere Change Data Capture, Version 10.2 Configuring Informix Dynamic Server to use theInformix Change Data Capture API You must prepare the Informix® database and database server to use the InformixChange Data Capture API before installing and configuring InfoSphere® CDC. See also:

To configure Informix Dynamic Server to use the InfoSphere CDC API

21

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/configuringidstocdcapi.html

1.

2.

3.

4.

IBM InfoSphere Change Data Capture, Version 10.2 To configure Informix® Dynamic Server to use theInfoSphere® CDC API

Turn on logging for all databases from which you intend to capture data changes.For information about logging, see the IBM®Informix Guide to SQL: Syntax. Run the following script as user informix from the $INFORMIXDIR/etc directory:syscdcv1.sqlVerify that the syscdcv1 database exists by creating a connection to it, as userinformix. For example, you could use DB-Access to connect to the syscdcv1database. Set the DB_LOCALE environment variable to be the same as the locale of thedatabase from which you want to capture data.

22

-

----

-----

-

--

--

IBM InfoSphere Change Data Capture, Version 10.2 Calculating database connections required byInfoSphere CDC for Informix® 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. Calculating connections required by InfoSphere CDC on asource database (22 + G)*I + 4*S + L + CWhere: Note: Enter 0 for any value that does not apply to your deployment of InfoSphereCDC.

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.L = number of subscriptions that contain LOB columns. C = number of InfoSphere CDC command line utilities that you plan to use.

Example: How to calculate required connections for asource database You want to set up InfoSphere CDC in the source environment as follows:

1 instance of Management Console.2InfoSphere CDC instances.3 subscriptions.1 subscription that uses LOB columns.You do not plan to use any InfoSphere CDC command line utilities.

The number of connections required on the source database will be: (22+1)*2 + 4*3 + 1 = 59 You should plan for a maximum of 59 database connections before installingInfoSphere CDC on a source database. 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.

23

- 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 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 source or target database. In most cases the defaultvalues are appropriate for 32-bit and 64-bit instances. However, if your database isprocessing an extremely heavy workload, you may have to adjust the default values.The RAM allocated must be physically available on your system. Disk space requirements for the global disk quota The global disk quota on your source and target systems is used for all capturecomponents including temporary files, transaction queues, and LOBs which arestaged on the target before being applied. InfoSphere CDC will manage disk spaceutilization across all components as required. Most databases have a mechanism that allows you to roll back or undo changes toyour database by storing uncommitted changes. Similarly, InfoSphere CDC usesthis disk quota to store in-scope change data that has not been committed in yourdatabase. Once the database transaction is committed, the disk space used by thetransaction is released. Long running open transactions will contribute to the amountof disk space used. 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. Related concepts: Hardware and software requirements Configuring InfoSphere CDC for Informix (Windows) Configuring InfoSphere CDC for Informix (UNIX and Linux) Disk space requirements RAM requirements

25






26

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.

27

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.

28

IBM InfoSphere Change Data Capture, Version 10.2 Database partition changes InfoSphere® CDC does not support database partition changes such as adding,removing, or moving except as documented for specific environments.

29

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.

30

---

IBM InfoSphere Change Data Capture, Version 10.2 Understanding change management InfoSphere® CDC maintains and depends on metadata describing source andtarget tables and columns being replicated. When Data Definition Language (DDL)changes occur that result in changes to the source or target table structures,InfoSphere CDC will no longer have the correct information with which to readsource database log records to capture change data during mirroring. For that reason, following a DDL change that results in table structural changes,InfoSphere CDC requires some action to update its metadata before replication canbe performed or resumed. As long as there is no Data Manipulation Language (DML) activity following a DDLstatement that affects replication, it is possible to resume mirroring once somespecific actions have been taken. If there is DML for the affected table following aDDL operation, a full refresh may be required for the table which has been changed. In a best case scenario, a DDL change that will affect replication should be knownand planned in advance. In this section, you will learn:

Understanding DDL awareness Preparing for a planned DDL change Understanding the Informix Error Code 83793 'table has pending in-place alter'

31

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/understandingddlawareness.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/preparingforaplannedddlchange.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/understandingtheinformixerrorcode83793tablehaspendingin-placealter.html

----

1.

2.

3.

4.

IBM InfoSphere Change Data Capture, Version 10.2 Understanding DDL awareness In the event that DDL operations occur in an unplanned manner, InfoSphere® CDCversion 6.3 and later has a feature called DDL awareness which identifies DDLchanges in database log entries that affects replication. The following list includes examples of DDL statements that affect replication:

Adding new columns.Dropping in-scope columnsDropping out of scope columnsModifying column formats (for example, data type, length, precision, and so on)

DDL statements that do not affect replication include analyzing table statistics andother maintenance procedures which do not change the "image" or "log recordformat" of the log entries for the table. Some DDL operations will cause the format tochange. Therefore, the log reader must be informed how to proceed when thisformat changes. When a DDL statement is detected, InfoSphere CDC does not send the DDLstatements to the target. Instead, InfoSphere CDC ends mirroring at that point in thelog using a controlled shutdown. For example, dropping a replicated column on thesource will not drop the corresponding column on the target. Behavior of InfoSphere CDC when a DDL statement isencountered

InfoSphere CDC detects that a DDL statement that changes the structure of anin-scope table has occurred.InfoSphere CDC initiates a normal (controlled) shutdown for a subscription whichincludes the table. A normal (controlled) shutdown means that mirroring for theaffected subscription will shut down once the target has applied all transactionsup until the point of the DDL change.When the subscription has stopped mirroring, the InfoSphere CDC event log willshow an error indicating that a DDL change has been detected and shutdowninitiated.Whether planned or not, following a DDL change, the InfoSphere CDC metadatamust be modified to accommodate the new "log record format", otherwise this willcause the log reader to fail to properly decode any log records after the point ofthe DDL.

Understanding the DDL awareness timeline There may be non-obvious cases where a DDL which happened previously, beforeadding a table to replication, can affect replication in the present, and causeInfoSphere CDC to fail with a runtime exception or possibly corrupt the data in a rowof the table on the target. In order to understand the problem posed by this, it is important to understand thatthe database log may contain a before image (the data row that was in the databasebefore a change occurred), and an after image (the data row that is in the databaseafter a change occurred). An insert log record will contain only an after image, a delete operation will containonly a before image, and an update operation will contain a before image and anafter image. On a DDL operation that changes a table structure, some database products may

32

only change metadata, but leave the old physical row structure in place for existingpages for the table. On some later update of one of these older rows, the resultinglog entry's image may not correspond to what is expected by InfoSphere CDCbased on the current structure of the table. The database itself will have anawareness of this and be able to deal with it, but InfoSphere CDC is only able to relyon the currently described structure of the table and may thus encounter an errorsituation.

33

--

IBM InfoSphere Change Data Capture, Version 10.2 Preparing for a planned DDL change In a best case scenario, a DDL change that will affect replication of tables that arebeing replicated should be known and planned in advance. In this case you shouldensure that the procedure to resume mirroring is executed during a quiescentmaintenance period for both source and target systems where no DML changesoccur to the InfoSphere® CDC in-scope tables (including tables that will not haveDDL changes). DDL changes have to be controlled so that the "log record format" changes do nothappen interleaved with DML statements. Meaning that the pattern of operationscannot be a quick succession of DDL DML DDL DML. All DDL statements must be executed at once with no DML in-between for theduration of the controlled shutdown, the metadata reconfiguration and restartingreplication. When DML occurs in-between DDL statements, a refresh must be performed to gettables back in-sync as there is no other path to recovery. An example would be when a DDL change was performed, InfoSphere CDCdetected the DDL and ended replication. While replication was down, additional DDLand DML operations were performed on the table (for example, insert a row, add acolumn, insert a row, drop a column). The table definition is now updated withinInfoSphere CDC. The table definition would have been updated to the lateststructure of the table, and will not account for the additional DML and DDLoperations. You would need to perform a refresh to resolve this inconsistency. Note: The order of the steps for the procedure is important to the success of theexecution. See also:

To resume mirroring after a DDL change using the command line To resume mirroring after a DDL change using Management Console

34

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/resumemirroringafteraddlchange_commandline.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/resumemirroringafteraddlchange_GUI.html

1.

2.

3.

--

-

--

4.

5.6.

--

-

IBM InfoSphere Change Data Capture, Version 10.2 To resume mirroring after a DDL change using thecommand line

End all DML activity on all of the tables in your database that are used forreplication.This would mean stopping any applications that are writing to thetables. DML activity must be stopped prior to making the DDL changes to thedatabase. Ensure that there are no open transactions involving a table that will be affectedby a DDL change.One way to see if there are any open transactions is to checkif there are any locks on the table. If there are any open translations, you should consult with your DBA to have theopen transactions appropriately dealt with before continuing. End replication for all running subscriptions in the InfoSphere® CDC instance byissuing the following command:dmendreplication -I <instance> -c -s <sub1><sub2><subn> Where:

<instance>—Specifies the instance name.<sub1><sub2><subn>—Specifies the names of the subscriptions wherereplication is to be ended. Multiple subscriptions names must be separated bya space.

You need to do the following: Stop all subscriptions at head of log using a controlled shutdown. Thecontrolled shutdown must complete normally - do not shutdown immediate orshutdown abort or otherwise stop the product during the controlled shutdownsequence. If the controlled shutdown does not complete normally, then aRefresh must be performed to bring the table contents back in sync.Ensure that InfoSphere CDC has reached head of log or has no latency. Wait for all subscriptions to end replicating, including the ones that are onlyperforming Refresh.

Change the replication method for the table mapping to Refresh.This disablesadditional logging for the Informix source tables and allows the DDL to beexecuted. Apply the DDL changes to all affected source tables in your database.Update the source table definitions and describe the source tables by issuing thefollowing commands:./dmreaddtable -I <instance> -t <table> -a./dmdescribe –I <instance> -s <subscription> Where:

<instance>—The name of the InfoSphere CDC instance.<table>—Specifies the name of a source table in the subscription for whichInfoSphere CDC updates the definition. You must specify the table name in theformat <schema>.<table>. To specify multiple tables, list the tables separatedby a space.<subscription>—Specifies that InfoSphere CDC sends source metadatachanges for the indicated subscriptions over to the target. To specify multiplesubscriptions, list the subscriptions separated by a space.

The table status will be reset to Mirror/Active.

35

7.

8.

--

-

9.

10.

--

11.

A.

The tables may now be in a state where they are considered to have pending in-place alters which will need to be dealt with prior to putting the tables back into amirroring state.If DDL changes have occurred on the target instance, update the target tabledefinitions by issuing the following command:./dmreassigntable -I <instance> -s<subscription> -t <table> Where:

<instance>—Specifies the name of the InfoSphere CDC instance.<subscription>—Specifies the subscription that contains the source table thatis mapped to the target table which was updated in your database. To specifymultiple subscriptions, list the subscriptions separated by a space.<table>—Specifies the name of a source table in the subscription that ismapped to the target table for which InfoSphere CDC updates the tabledefinition in the metadata. You must specify the table name in the format<schema>.<table>. To specify multiple tables, list the tables separated by aspace.

Check the table mapping for correctness.When DDL changes modify sourcecolumns, you must make sure that the target table can accommodate the newdata format (for example, going from CHAR(1) to CHAR(10) etc.). This can bedetermined in the Details area of the Table Mappings view in ManagementConsole. If necessary, manually remap the changed columns and verify the newmappings. InfoSphere CDC’s auto-mapping feature will map identical columnnames. However, since InfoSphere CDC’s auto-map is a best effort algorithm,verify and adjust your mappings to suit your business needs. If there is a requirement to perform a Refresh of the table or if refreshing thetable is the preferred means of recovering, you can flag the table for refresh andinitiate the Refresh operation../dmflagforrefresh -I <instance> -t <table> ./dmrefresh -I <instance> -f Where:

<instance>—The name of the InfoSphere CDC instance.<table>—Specifies the name of a source table in the subscription thatInfoSphere CDC flags for refresh. You must specify the table name in theformat <schema>.<table>. To specify multiple tables, list the tables separatedby a space.

Once the refresh has successfully completed, mirroring can be restarted for thesubscription and the following steps may be skipped as not required. If you choose to restart mirroring without refreshing the tables, you will need toreset the bookmark.In order to resume mirroring from the point where it washalted after the DDL operation was detected, it is necessary to reset theInfoSphere CDC bookmark to the point of the last applied operation on the targetusing the InfoSphere CDC command line interface, as follows

Get the bookmark position from the target of the last applied transaction usingthe command line utility:./dmshowbookmark -I <instance> -s <source> Where:

36

--

B.

--

-

12.

---

<instance>—Specifies the name of the InfoSphere CDC instance.<source>—Specifies the source ID of the subscription for which you want toobtain the replication position.

The bookmark value is returned as a hex value, for example:00060100000000055C973C4E7D13C8000000010000000000000000055C973C Set the bookmark on the source instance using the command line utility./dmsetbookmark -I <instance> -s <subscription> -a -b <hex> Where:

<instance>—Specifies the name of the InfoSphere CDC instance.<subscription>—Specifies the name of the subscription for whichInfoSphere CDC sets a replication position (bookmark).<hex>—Specifies the replication position (bookmark) which determines thepoint in the database log where you want InfoSphere CDC to resumemirroring. When mirroring resumes, InfoSphere CDC will start capturingchange data at the indicated replication position. The replication position is ahexadecimal-encoded string that was obtained from the target instanceusing the dmshowbookmark command.

Start mirroring for the subscriptions that were halted due to the DDL change.Issue one of the following commands:For continuous mirroring:dmstartmirror -I<instance> -c -s <subscription> For mirroring with a scheduled end: dmstartmirror -I <instance> –n –p <position><subscription> Where:

<instance>—Specifies the name of the InfoSphere CDC instance.<position>—Specifies the log position in the source database.<subscription>—Specifies the name of the subscription for which InfoSphereCDC will begin mirroring.

Related concepts: Understanding the Informix Error Code 83793 'table has pending in-place alter'

37


1.

2.

3.-

--

A.B.

C.

-

-

-

IBM InfoSphere Change Data Capture, Version 10.2 To resume mirroring after a DDL change usingManagement Console

End all DML activity on all of the tables in your database that are used forreplication.This would mean stopping any applications that are writing to thetables. DML activity must be stopped prior to making the DDL changes to thedatabase. Ensure that there are no open transactions involving a table that will be affectedby a DDL change.One way to see if there are any open transactions is to checkif there are any locks on the table. If there are any open translations, you should consult with your DBA to have theopen transactions appropriately dealt with before continuing. End replication for all running subscriptions in the InfoSphere® CDC instance

Stop all subscriptions at head of log using a controlled shutdown. Thecontrolled shutdown must complete normally - do not shutdown immediate orshutdown abort or otherwise stop the product during the controlled shutdownsequence. If the controlled shutdown does not complete normally, then aRefresh must be performed to bring the table contents back in sync.Ensure that InfoSphere CDC has reached head of log or has no latency. Wait for all subscriptions to end replicating, including the ones that are onlyperforming Refresh.

Click Monitoring > Subscriptions.If the subscriptions are available for editing, right-click one or moresubscriptions and select End Replication.Depending on your version of InfoSphere CDC, choose from the followingoptions.InfoSphere CDC version 6.5 or later:

Normal—InfoSphere CDC completes in progress work and then endsreplication. If a refresh is in progress, Normal will complete the refresh forthe current table before replication ends.Normal is the most appropriateoption for most business requirements and is the preferred method forending replication in most situations. Immediate—InfoSphere CDC stops all in progress work and then endsreplication. Starting replication after using this option can be slower thanusing the Normal. If a refresh is in progress, the refresh for the current tablewill be interrupted and then replication will end.You should ensure that alldependent source database logs are available before ending replicationusing the Immediate option. InfoSphere CDC may need to reprocess all thedependent source logs when you restart the subscription. If InfoSphere CDCis currently processing a long running transaction when you end replicationwith Immediate, InfoSphere CDC may have to resume replication from theearliest open transaction in the database logs. Use thedmshowlogdependency command to determine which logs are required. Attention: Use this option if business reasons require replication to endfaster than Normal at the expense of a slower start when you resumereplication on the subscription. Abort—InfoSphere CDC stops all in progress work and then ends replicationrapidly. Starting replication after using this option can be much slower than

38

-

-

-

-

-

-

D.4.

5.6.

A.B.C.D.

7.

the Normal. A refresh in progress will be interrupted and the target will stopprocessing any data that has not been committed before replication ends.You should ensure that all dependent source database logs are availablebefore ending replication using the Abort option. InfoSphere CDC may needto reprocess all the dependent source logs when you restart thesubscription. If InfoSphere CDC is currently processing a long runningtransaction when you end replication with Abort, InfoSphere CDC may haveto resume replication from the earliest open transaction in the databaselogs. Use the dmshowlogdependency command to determine which logs arerequired. Attention: Use this option if your business reasons require a rapid end toreplication and you are willing to tolerate a much slower start when youresume replication on the subscription. A sudden business requirement foran unplanned shutdown of your source system may require this option forending replication. Scheduled End—This option will process all committed database changes inthe source database and then end replication at the indicated point with theNormal option. This option is not available if all the tables in a subscriptionare currently refreshing.

Now—End replication at the current source system time in your sourcedatabase log. The source system time when replication will end is setwhen you click OK.Specific Date/Time—End replication with the Normal option at thespecified date and time. InfoSphere CDC displays the UTC offset (inminutes) of the source database.Specific Log Position—End replication with the Normal option at thespecified log position. InfoSphere CDC displays the format of the logposition for the source datastore. This option is only available forsupported source datastores.

InfoSphere CDC version 6.3: Controlled—InfoSphere CDC completes all in-progress operations andapplies pending changes to the target table.Immediate—InfoSphere CDC interrupts any in-progress operations anddoes not apply pending changes to the target table.

Click OK.Change the replication method for the table mapping to Refresh.This disablesadditional logging for the Informix source tables and allows the DDL to beexecuted. Apply the DDL changes to all affected source tables in your database.Update the source table definitions

Click Configuration > Subscriptions.Select the subscription.Select the mapped source and target tables in the Table Mappings view.Right-click the table and choose Update Table Definition > Source Table.

This will update the source table definition, as well as remap the new columns ifthe names match. The table status will be reset to Mirror/Parked. The tables may now be in a state where they are considered to have pending in-place alters which will need to be dealt with prior to putting the tables back into a

39

8.

A.B.C.D.

9.

10.

A.B.C.D.E.F.

11.

A.

--

B.

mirroring state.If DDL changes have occurred on the target instance, update the target tabledefinitions.

Click Configuration > Subscriptions.Select the subscription.Select the mapped source and target tables in the Table Mappings view.Right-click the table and choose Update Table Definition > Target Table.

This will update the target table definition, as well as remap the new columns ifthe names match. The table status will be reset to Mirror/Parked. Check the table mapping for correctness.When DDL modifies source columns,make sure the target table can accommodate the new data format (for example,going from CHAR(1) to CHAR(10) etc.). This can be done in the Table MappingsDetails area. If necessary, manually remap the changed columns and verify the newmappings. The InfoSphere CDC auto-mapping feature will map identical columnnames. However, since the auto-map is a best effort algorithm, verify and adjustyour mappings to suit your business needs. If there is a requirement to perform a Refresh of the table or if refreshing thetable is the preferred means of recovering, you can flag the table for refresh andinitiate the Refresh operation.

Click Configuration > Subscriptions.Select the subscription.Select the mapped source and target tables in the Table Mappings view.Right-click the table and choose Flag for Refresh.Select Standard Refresh.Click OK.

Once the refresh has successfully completed, mirroring can be restarted for thesubscription and the following steps may be skipped as not required. If you choose to restart mirroring without refreshing the tables, you will need toreset the bookmark.In order to resume mirroring from the point where it washalted after the DDL operation was detected, it is necessary to reset theInfoSphere CDC bookmark to the point of the last applied operation on the targetusing the InfoSphere CDC command line interface, as follows

Get the bookmark position from the target of the last applied transaction usingthe command line utility:./dmshowbookmark -I <instance> -s <source> Where:

<instance>—Specifies the name of the InfoSphere CDC instance.<source>—Specifies the source ID of the subscription for which you want toobtain the replication position.

The bookmark value is returned as a hex value, for example:00060100000000055C973C4E7D13C8000000010000000000000000055C973C Set the bookmark on the source instance using the command line utility./dmsetbookmark -I <instance> -s <subscription> -a -b <hex> Where:

40

--

-

12.A.B.

C.D.

<instance>—Specifies the name of the InfoSphere CDC instance.<subscription>—Specifies the name of the subscription for whichInfoSphere CDC sets a replication position (bookmark).<hex>—Specifies the replication position (bookmark) which determines thepoint in the database log where you want InfoSphere CDC to resumemirroring. When mirroring resumes, InfoSphere CDC will start capturingchange data at the indicated replication position. The replication position is ahexadecimal-encoded string that was obtained from the target instanceusing the dmshowbookmark command.

Start mirroring for the subscriptions that were halted due to the DDL change.Click Monitoring > Subscriptions.If the subscription is available for editing, right-click one or more subscriptionsand select Start Mirroring.Refresh Details is displayed if you have one ormore tables flagged for refresh and allows you to view the refreshconfiguration of these tables. Continuous mirroring will not start until therefresh of these tables is complete. Select either the Continuous or Scheduled End option.Click OK to start mirroring.Mirroring will continue until you end replication.

Related concepts: Understanding the Informix Error Code 83793 'table has pending in-place alter'

41


-

IBM InfoSphere Change Data Capture, Version 10.2 Understanding the Informix Error Code 83793 'tablehas pending in-place alter' If you try to add a table to InfoSphere® CDC replication that has been altered atsome point in the past, you may receive an InfoSphere CDC error that indicates thetable has pending in-place alters. (Informix® Error Code 83793 ('table has pendingin-place alter'). When the database engine determines that it is possible to manage existing storeddata using the new presentation caused by an ALTER statement, it will allow thechange without modifying any existing physical data row structures for existingpages on disk. This is referred to as an in-place alter. While the database engine can manage thissituation without problem it poses a problem for replication. In order to understand the problem posed by this, it is important to understand thatthe database log may contain a before image - the data row that was in thedatabase before a change happened, and an after image - the data row that is in thedatabase after a change happened. An insert log record will contain only an after image, a delete operation will containonly an after image, and an update operation will contain a before image and anafter image. If the physical structure of a row was an older format and was read from the log thatway it would differ from the current structure expected by the InfoSphere CDCreplication engine and a problem would result. For that reason, when an attempt is made to add an Informix table to an InfoSphereCDC subscription and set its mode to Mirroring, the fact that it has a pending in-place alter is detected and an error condition results. To resolve this, it is necessary to force the physical changes to be made to thetable's data pages. This is done by means of what is sometimes called a dummy UPDATE: UPDATE <table> SET column = column; Where:

<table>—Specifies the table name.Note that for some types of ALTERs where the system cannot guarantee thatexisting data can be managed in the new representation, the database engine willperform a slow ALTER. So not every ALTER will result in this error when changing atable mapping's replication method back to Mirroring following a DDL change.

42

-

--

-

--

IBM InfoSphere Change Data Capture, Version 10.2 Installation checklist The following software components must be installed before you can configure andbegin using InfoSphere® CDC for Informix®:

Informix Dynamic Server—See the installation documentation or IBM®InformixGetting Started Guide in the Informix Dynamic Server Information Center:http://publib.boulder.ibm.com/infocenter/idshelp/v115/index.jspImportant: TheInformix database server and target database must be set up to use theInfoSphere CDC API before you install and configure InfoSphere CDC. Forinformation on how to do this, see To configure Informix Dynamic Server to use theInfoSphere CDC API. Source database—Refer to your database product documentation for details.InfoSphere CDC for Informix—See the documentation relevant to your operatingsystem in Installing or upgrading InfoSphere CDC for Informix.InfoSphere CDC for the source database—See the InfoSphere CDCEnd-UserDocumentation that is applicable to your source database. This documentation islocated in the docs directory under the InfoSphere CDC installation directory.InfoSphere CDCAccess Server—See Installing Access ServerInfoSphere CDCManagement Console—See Installing Management Console

For information about using Management Console and Access Server, seeManagement Console Administration

43

http://publib.boulder.ibm.com/infocenter/idshelp/v115/index.jsp



https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/installingorupgradinginfospherecdc.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.installingasandmc.doc/concepts/installingaccessserver.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.installingasandmc.doc/concepts/installingmanagementconsole.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/overview_of_cdc.html

---

IBM InfoSphere Change Data Capture, Version 10.2 Installing or upgrading InfoSphere CDC forInformix® 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 Informix using an interactive installation Installing InfoSphere CDC for Informix using a silent installation Upgrading InfoSphere CDC for Informix 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 Informix

44

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/installingusinganinteractiveinstallation.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/installingusingasilentinstallation.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/upgradinginfospherecdc.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/before_install.html

--

-

---

IBM InfoSphere Change Data Capture, Version 10.2 Installing InfoSphere CDC for Informix® 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 Informix (Windows) To install InfoSphere CDC for Informix (UNIX and Linux) To override the locale for the installation (UNIX and Linux)

45

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/installingcdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/installingcdc_unixandlinux.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/overridethelocale_unixandlinux.html

1.

2.3.

4.5.

6.7.8.

9.

IBM InfoSphere Change Data Capture, Version 10.2 To install InfoSphere CDC for Informix® (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 Informix (Windows)

46


1.2.

3.4.

5.

6.7.

8.9.

10.

IBM InfoSphere Change Data Capture, Version 10.2 To install InfoSphere CDC for Informix® (UNIX andLinux)

Log on to the account you set up for InfoSphere® CDC.Copy the InfoSphere CDC installation file for your UNIXor Linux platform fromthe InfoSphere 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 Informix (UNIX and Linux) Related tasks: To perform a silent installation of InfoSphere CDC (UNIX and Linux)

47


https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/performasilentinstallation_unixandlinux.html

1.2.

----

-

IBM InfoSphere Change Data Capture, Version 10.2 To override the locale for the installation (UNIX andLinux) Use the following procedure to override the locale for the installer. English,Japanese and Simplified Chinese are supported.

Navigate to the directory that contains the InfoSphere® CDC installation file.Start the installer with the following flags to override the locale of the installation:

English—<installation_file_name>.bin -l enJapanese—<installation_file_name>.bin -l jaKorean—<installation_file_name>.bin -l koSimplified Chinese—<installation_file_name>.bin -l zh_CN

where: <installation_file_name> is the name of the installation file.

After the installation is complete, you have the option of launching the InfoSphereCDC configuration tool. The configuration tool will use the locale settings for yoursystem.

48

-

IBM InfoSphere Change Data Capture, Version 10.2 Installing InfoSphere CDC for Informix® 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 (UNIX and Linux)

49

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/performasilentinstallation_unixandlinux.html

1.2.

3.4.

-5.

-

IBM InfoSphere Change Data Capture, Version 10.2 To perform a silent installation of InfoSphere CDC(UNIX and Linux)

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.

Related tasks: To install InfoSphere CDC for Informix (UNIX and Linux)

50

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/installingcdc_unixandlinux.html

-

-

-

-

-

--

--

IBM InfoSphere Change Data Capture, Version 10.2 Upgrading InfoSphere CDC for Informix 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 Informix® instances associated with theinstallation to be upgraded must be stopped.All InfoSphere CDC for Informix 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 Informix.It is a best practice to backup the installation directory of the current InfoSphereCDC for Informix 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 theInformix 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 Informix (Windows) To upgrade InfoSphere CDC for Informix (UNIX and Linux)

51

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/upgradeinfospherecdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/upgradeinfospherecdc_unix.html

52

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 Informix®(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.

53

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 Informix® (UNIXand Linux)

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.

54

55

----

-

IBM InfoSphere Change Data Capture, Version 10.2 Configuring Informix for InfoSphere CDC replication Set up a replication subscription between your source databases and Informix®target databases. Before setting up a replication subscription:

Verify that your source and Informix databases are running.Ensure that you have sufficient access privileges to the databases.Verify that Informix database is set up to use the InfoSphere® CDC API.Define the replication principles in accordance with your business rules.

See also:

To configure Informix for InfoSphere CDC replication

56

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/configuringcdc.html

1.

2.3.

4.A.B.

5.

A.

B.C.

1.2.

6.

7.A.B.

8.

9.

10.

11.

12.

IBM InfoSphere Change Data Capture, Version 10.2 To configure Informix for InfoSphere CDCreplication

Create a new instance of InfoSphere® CDC for Informix®.See ConfiguringInfoSphere CDC for Informix (UNIX and Linux) or Configuring InfoSphere CDCfor Informix (Windows) for details. Create a new instance of InfoSphere CDC for your source database.Log in to Management Console.See Logging in to Management Console byconnecting to Access Server for details. Tip: To be able to work in the Access Manager perspective of the ManagementConsole, you must be a system administrator with the privilege to managedatastores and user accounts. The system administrator account was createdduring the installation of Management Console. Set up datastores for Informix and your source database.

Add a new datastore.See To add a datastore for details. Set connection parameters.See To set connection parameters on a datastorefor details.

Assign datastores to users. You need to assign both the Informix datastore andyour source datastore to one or more users.

If necessary, add new users. To be able to add new users, you must be asystem administrator who has the privilege to manage user accounts. SeeManaging user accounts for details.Assign datastores to users. See Assigning users to datastores for details.Disconnect from and then reconnect to the Access Server:

Select File > Access Server > Disconnect.Select File > Access Server > Connect.

Set the datastore connection preferences by accepting the default settings or byspecifying different settings.See Setting connection preferences for details. Set up datastores for replication:

Connect to the Informix datastore.Connect to the source database.

See Setting up datastores for replication for details. Define replication tables in both the Informix and source datastores.SeeManaging tables available for replication for details. Set up the replication subscription that you need for your implementation.SeeSetting up subscriptions for details. Map tables for replication in both subscriptions, selecting Mirror (Change DataCapture) or Net Change as the replication method.See Mapping tables fordetails. For each table mapping, set Conflict Detection and Resolution in accordancewith your business rules.See Setting conflict detection and resolution for details. Start replication on both subscriptions.See Starting and ending replication fordetails.

57





https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/loggingMC.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/loggingMC.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/tasks/addnewdatastore.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/tasks/setconnectionparms.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/Managinguseraccounts.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/assigningusersanddatastores.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/settingconnectionpreferences.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/settingupdatastoresforreplication.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/SelectingSourceTablesForReplication.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/settingupsubscriptions.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/mappingtables.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/ConflictDetectionResolution.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/StartingReplication.html

-

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Informix®(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 Informix instances (Windows) Related concepts: Hardware and software requirements Disk space requirements RAM requirements

58

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/configuringinstances_windows.html




---

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Informix®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 Informix (Windows) To edit an instance of InfoSphere CDC for Informix (Windows) To delete an instance of InfoSphere CDC for Informix (Windows)

59

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/addanewinstance_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/editaninstance_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/deleteaninstance_windows.html

1.

2.

3.4.

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

If you are configuring the first instance of InfoSphere® CDC for Informix® 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 the AccessManager 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.

60

#addanewinstanceoftransformationserverwindows__welcome



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.

61

6. In the Database area, you can configure access to the database that contains thetables for replication. To complete this step, you will require system administratorprivileges. You can then add a datastore in the Access Manager perspective inManagement Console and provide users access to this database. For moreinformation, see your Management Console documentation.

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 the specifieddomain. If your computer is notpart of a domain, you canspecify <computername>\<user name>.In the Password and ConfirmPassword boxes, enter thepassword currently associatedwith the selected Windows useraccount. 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 DescriptionInformix Server Enter the name of the Informix

database server. You mustspecify the DBSERVERNAMEvalue here, not the name of anInformix server alias.Use the Advanced button if youwant to specify Informixdatabase server settings, suchas DB_LOCALE.

Host Enter the name of the computeron which the Informix databaseserver is installed.

Name Enter the name of the databasethat you want to replicate datato or from and contains all ofthe tables for replication. This isthe database that youconfigured as part of thepreinstallation tasks.

62

7.

A.

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

H.

I.J.

K.

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 used whencharacteristics 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) isa programming interface from Oracle for connecting Java programs to namingand directory services.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-

Port Enter the number for theInformix listen port.

Username Enter the user name for thespecified database.

Password Enter the password for thespecified database.

Metadata Schema 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:InfoSphere CDCmetadata tables containimportant configurationinformation and should bebacked up as part of yourdatabase backup strategy.

63

L.

M.N.

O.8.9.

-

-

-

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: Assessing disk space and memory requirements Creating queues in JMS providers Related tasks: To start InfoSphere CDC for Informix (Windows) Related reference: dmbackupmd - Back up metadata

64



https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/startingcdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmbackupmd.html

1.

2.

3.

4.

5.

IBM InfoSphere Change Data Capture, Version 10.2 To edit an instance of InfoSphere CDC for Informix®(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.

65

1.

2.

3.4.

IBM InfoSphere Change Data Capture, Version 10.2 To delete an instance of InfoSphere® CDC forInformix® (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.

66

-

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Informix® (UNIXand Linux) 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 instances (UNIX and Linux) Related concepts: Hardware and software requirements Disk space requirements RAM requirements

67

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/configuringinstances_unixandlinux.html




---

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC instances (UNIX andLinux) 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 Informix (UNIX and Linux) To edit an instance of InfoSphere CDC for Informix (UNIX and Linux) To delete an instance of InfoSphere CDC for Informix (UNIX and Linux)

68

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/addanewinstance_unix.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/editaninstance_unixandlinux.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/deleteaninstance_unixandlinux.html

1.

2.

3.4.5.

6.

7.8.

9.10.

A.

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

H.

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

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 2 and press Enter to add a new instance of InfoSphere CDC.Enter a name for your InfoSphere CDC instance and press Enter. The instancename must be unique.Enter the port number which InfoSphere CDC uses for communication with clientworkstations running Management Console and other servers. InfoSphere CDCdisplays a default port of 10201. 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 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 yourJMS provider.Enter the user name and press Enter.

69

#addanewinstanceoftransformationserverunix__welcome

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

R.

11.

12.

13.

14.

15.16.17.

18.

19.

A.

B.-

--

C.20.

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.

Specify the name of the Informix® database server. You must specify theDBSERVERNAME value here, not the name of an Informix server alias. PressEnter.Specify the name of the Informix host computer and press EnterNote: Do notconfigure the advanced parameters unless directed by an IBM® representative. Specify the name of the database that contains all the tables for replication andpress Enter.Specify the number of the Informix listen port and press Enter. Tip: You can findthe port number in the connectivity information of your Informixsqlhosts file. Enter n and press Enter.Enter the user name for the specified database and press Enter.Enter the password for the specified database and press Enter. Theconfiguration tool will now search the database for schemas. Specify the number that corresponds to the database schema used byInfoSphere CDC for metadata tables and press Enter. You can specify anyschema except those in use by other installed instances of InfoSphere CDC forthe given database.Note:InfoSphere CDC metadata tables contain importantconfiguration information and should be backed up as part of your databasebackup strategy. 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.

70

Related concepts: Assessing disk space and memory requirements Creating queues in JMS providers Port requirements Related tasks: To start InfoSphere CDC for Informix (UNIX and Linux) Related reference: dmbackupmd - Back up metadata

71




https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/startingcdc_unixandlinux.html


1.

2.

3.

4.5.

6.

IBM InfoSphere Change Data Capture, Version 10.2 To edit an instance of InfoSphere CDC for Informix®(UNIX and Linux)

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.

72

1.2.

3.

4.5.

IBM InfoSphere Change Data Capture, Version 10.2 To delete an instance of InfoSphere CDC forInformix® (UNIX and Linux)

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.

73

---

-

-

-

--

IBM InfoSphere Change Data Capture, Version 10.2 Configuring InfoSphere CDC for Informix® for OS(operating system) clustering (UNIX and Linux) InfoSphere® CDC supports Active/Passive two-node clusters on the UNIX andLinux platforms. Clustering provides continuous access to resources in the event ofa hardware failure, software failure, or some other interruption. To implement InfoSphere CDC clustering support in your environment, you mustcomplete all of the following prerequisite tasks. Note: Prerequisites that only apply to InfoSphere CDC as a clustered source or aclustered target are specified.

Install InfoSphere CDC on the shared drive of the cluster.Add a new instance of InfoSphere CDC.Ensure that the server port you specify during configuration of the instance isavailable and persistent on both nodes of the cluster. InfoSphere CDC listens onthis port.Ensure that all of the database logs required for replication are available. Thisprerequisite only applies to InfoSphere CDC as a clustered source.Ensure that every InfoSphere CDC source that connects to the target sees thetarget in the same way. The target must have a clustered IP address or use thesame host name for both nodes of the cluster. This prerequisite only applies toInfoSphere CDC as a clustered target.Optionally, schedule a regular backup of your InfoSphere CDC metadata andevent log messages. Note that metadata will only change when you add or modifysubscriptions. You can find more information about this prerequisite in the failoverprocedure for InfoSphere CDC in this section.

Note: You can run the dmshowlogdependency command with the –i flag to list thedatabase logs required for replication. In this section, you will learn:

Performing a forced or manual failover of InfoSphere CDC for Informix Preparing for a failover of InfoSphere CDC for Informix

74

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/forcedfailoverclustering.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/failoverclustering.html

1.

2.

3.

4.

IBM InfoSphere Change Data Capture, Version 10.2 Performing a forced or manual failover ofInfoSphere CDC for Informix® A forced or manual failover is often necessary in a clustered environment forsoftware upgrades, maintenance, or other reasons. The tasks in the following stepsmust be included in your manual failover script.

Stop all instances of InfoSphere® CDC on the current active node with thefollowing command:dmshutdown -I <instance_name> Manually failover your clustered environment with the scripts or procedures thatare specific to your environment.Restart all instances on the new active node with the following commands for 32-bit and 64-bit operating systems:dmts32 - I <instance_name> or dmts64- I <instance_name> Start all subscriptions on the new active node with the dmstartmirror command.

75

1.

2.

3.

4.

5.

IBM InfoSphere Change Data Capture, Version 10.2 Preparing for a failover of InfoSphere CDC forInformix® To prepare for a failover such as a hardware or software failure, your clusteringenvironment will require a script that performs InfoSphere® CDC tasks on the newactive node. The tasks in the following steps must be included in your failover script.

Clean the transaction queues for each instance by removing all files that beginwith txqueue* in the <InfoSphere CDC installation directory>/instance/<instancename>/txnstore directory.Back up your metadata for each instance by archiving all files that begin with md*in the <InfoSphere CDC installation directory>/instance/<instance name>/confdirectory. If the metadata database does not recover after a failover, restore thesefiles to the same directory on the new active node. This task is optional.Back up your Event Log messages for each instance by archiving all files in the<InfoSphere CDC installation directory>/instance/<instance name>/eventsdirectory. If the events database does not recover after a failover, restore thesefiles to the same directory on the new active node. This task is optional.Start each instance on the new active node with the following commands for 32-bit and 64-bit operating systems:dmts32 - I <instance_name> or dmts64- I <instance_name> Start all subscriptions on the new active node with the dmstartmirror command.

76

------

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

Starting InfoSphere CDC for Informix Stopping InfoSphere CDC for Informix Performing an external refresh Creating the syscdcv1 database Maintaining active TCP connections in a network environment Enabling SQL statements in Management Console

77

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/startingcdc.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/stoppingcdc.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/performinganexternalrefresh.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/creatingthesyscdcv1.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/maintainactivetcpconnnections.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/enablingsqlstatementsinmanagementconsole.html

--

IBM InfoSphere Change Data Capture, Version 10.2 Starting InfoSphere CDC for Informix® When you install InfoSphere® CDC on a supported Windows server, you can start itmanually after the initial configuration. Starting InfoSphere CDC starts the servicesin Windows. The services will automatically start after a reboot. When you install InfoSphere CDC on a supported UNIX server, you can issue acommand to start it. After installing InfoSphere CDC, start it so that you can create adatastore for this instance in Management Console. See also:

To start InfoSphere CDC for Informix (Windows) To start InfoSphere CDC for Informix (UNIX and Linux)

78

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/startingcdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/startingcdc_unixandlinux.html

1.

2.

IBM InfoSphere Change Data Capture, Version 10.2 To start InfoSphere CDC for Informix® (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.

79

--

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

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

80

--

IBM InfoSphere Change Data Capture, Version 10.2 Stopping InfoSphere CDC for Informix® 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 Informix (Windows) To stop InfoSphere CDC for Informix (UNIX and Linux)

81

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/stoppingcdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/stoppingcdc_unixandlinux.html

1.

2.

3.

IBM InfoSphere Change Data Capture, Version 10.2 To stop InfoSphere CDC for Informix® (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.

82

1.

2.

IBM InfoSphere Change Data Capture, Version 10.2 To stop InfoSphere CDC for Informix® (UNIX andLinux)

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 or Linuxserver, and you want to shutthem all down, run thiscommand from the installationdirectory for each InfoSphereCDC instance.

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

83

---

IBM InfoSphere Change Data Capture, Version 10.2 Performing an external refresh You can perform a refresh of one or more tables in a subscription using a third-partytool, and still integrate this activity into the refresh while active capability ofInfoSphere® CDC. Such third-party tools might be a table unload at source andload at target, an application program that regenerates the content of a table beingrun against both the source and target tables, recovery of a table's content to a priorpoint in time at both the source and target, or even a refresh of the table using asubscription other than the one that will be mirroring the data. A refresh orreconstruction of a table by such a means is referred to as an external refresh. Note: An external refresh can only be performed when the target is database, not amessage queue or an ETL solution. Performing an external refresh using thedmmarkexternalunloadstart and dmmarkexternalunloadend commands is notsupported for the following replication engines:

InfoSphere CDC for InfoSphere DataStage® (either Direct Connect or Flat File)InfoSphere CDC Event ServerInfoSphere Classic CDC for z/OS®

In order to integrate the activity of the external refresh into the mirroring activity ofthe subscription, new command capabilities have been added to the products. Tounderstand what these commands do, how to provide usable data to them, andwhat to avoid so that they won't be misused, it is necessary to understand themechanism of refresh while active processing. Understanding refresh while active When a table within a subscription is set to Method:Mirror and Status:Refresh, it isreadied for a refresh while active. When the subscription is started, as viewedexternally, the table is refreshed and then mirroring of the tables in the subscriptionstarts. When the subscription starts, it must necessarily start scraping from the log ata place prior to the place when the refresh was performed. For the table that wasrefreshed at the start of mirroring, changes scraped from the log are discarded untilscraping reaches the place where the refresh had started. From that point forward,changes scraped for that table are forwarded to the target for application to thetarget table. Between the place in the log where the refresh started and the placewhere the refresh ended, a change scraped from the log could either have beenapplied to the table or not yet have been applied to the table by the time that portionof the table was refreshed. Thus the change may or may not have been forwardedto the target and been applied to the target table during the refresh. For this reason,changes scraped from the log between the places where the refresh ran are appliedat the target with an error mitigation filter that suppresses operational errors(INSERT of a preexisting row, UPDATE or DELETE of a nonexisting row). Thesechanges are said to be sent with the "indefinitely refreshed" indicator set. Oncescraping proceeds past the place in the log where the refresh ended, the indefinitelyrefreshed indicator is no longer set, and operational errors are treated as harshly asany other.It is possible that changes that have been logged before the place in thelog when the refresh started were not yet committed when the refresh started. Suchchanges would appear in the table after the COMMIT was issued, but would bediscarded when they were scraped from the log because they were logged prior tothe refresh starting place in the log. The capture of the table's content during the

84

1.

2.

3.

refresh could miss these changes, depending on how much time passes before theCOMMIT is issued. This would cause the source and target tables to beunsynchronized. To avoid this, InfoSphere CDC uses methods based on the DBMSin use to establish a point of consistency for the table at the time that the refresh fora refresh while active is starting. For example, on the z/OS platform, before therefresh starts, a shared lock with a table scope is obtained on the table beingrefreshed. The current log write position is determined, then the lock is released.This forces any units of recovery that contain changes for the table being locked tocomplete (that is, a COMMIT). When the shared lock is released the refresh starts,and the log write position sampled while the lock was held will be used as the placefor the start of the refresh. The shared lock is held for milliseconds at most, andshould not be disruptive to normal application processing for the table. Considerations for an external refresh When an external refresh occurs, it involves the capturing of the source table'scontent and the writing of that content to the target table. The period when thesource table's content is being captured is equivalent to the period during a refreshwhile active when the source table is being read. Depending on how the source andtarget tables are being re-synchronized outside of the subscription, this period couldbe significantly long (for example, using unload and load) or effectivelyinstantaneous (for example, point-in-time recovery at both source and target). ForInfoSphere CDC for z/OS, this period needs to be converted to a starting place andan ending place in the log, expressed in terms of log positions in the DBMS's log.The two (possibly identical) log positions are then provided to InfoSphere CDC usingthe command interface, and InfoSphere CDC updates the metadata with them asthough they had originated from the execution of the refresh of a refresh while active. When the subscription starts to mirror, these two log positions describe the scrapepoint when discarding of the table's data stops and marking changes as 'indefinitelyrefreshed starts, and when marking changes as indefinitely refreshed stops. For all other supported engines, the refresh while active period is determined by thecurrent position of the log when the dmmarkexternalunloadstart anddmmarkexternalunloadend commands are issued. In order for this update to the metadata to be effective and productive, the followinghave to be true:

The subscription must not be active, as is always the case when a subscription'sattributes are being modified.The first (earlier) of the two log positions must not be earlier than the log positionwhere the subscription will start scraping. If this rule is not followed, the resultsare not predictable.Neither of the two log positions should be for a place that has not yet been writtento the log. If this rule is not followed, the results are not predictable.

In addition to these considerations, there is also the issue of establishing a point ofconsistency at the start of capturing the source table for the external refresh. Whenperforming a refresh while active, as explained above, a point of consistency for thetable being refreshed is established by acquiring a shared lock with table scope.This method is unavailable when doing an external refresh, so other means ofestablishing a point of consistency should be employed. Sometimes, this will not be

85

-

possible, such as for a point-in-time recovery at both the source and target. If it ispossible, such as when performing an unload and reload, then it is stronglyrecommended that a point of consistency be established. This can be done byquiescing activity against the table, or simply by stopping all updating applicationprograms. Sometimes it may not be necessary, such as when a program is used toregenerate the entire table content at both the source and target (assuming such aprogram would, by its action, implicitly lock the entire table). Failure to take the stepsto establish a point of consistency could produce operational errors later, under thescenario described above.

To perform an external refresh Related reference: dmmarkexternalunloadend - End table data unload dmmarkexternalunloadstart - Start table data unload

86

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/performanexternalrefresh.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmmarkexternalunloadend.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmmarkexternalunloadstart.html

1.2.3.

4.5.6.7.

IBM InfoSphere Change Data Capture, Version 10.2 To perform an external refresh

Stop the subscription, if it is currently running.Run the dmmarkexternalunloadstart command.Use an external tool to unload the table data.You should determine if there areany limitations on transaction isolation levels by your external tool. Wait for the unload to complete.Run the dmmarkexternalunloadend command.Use your external tool to load the table data on the target.Start the subscription.InfoSphere® CDC will reconcile the differencescorresponding to the changes made to the source table during thesynchronization phase. InfoSphere CDC runs in the manner of Adaptive Applyduring the range marked by the start and end commands.

Related reference: dmmarkexternalunloadend - End table data unload dmmarkexternalunloadstart - Start table data unload

87



-

IBM InfoSphere Change Data Capture, Version 10.2 Creating the syscdcv1 database InfoSphere® CDC requires the InfoSphere CDC for Informix® API to capturetransaction data. Before you set up replication with InfoSphere CDC, create adatabase called syscdcv1.

To create the syscdcv1 database

88

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/createsyscdcv1db.html

1.

2.

IBM InfoSphere Change Data Capture, Version 10.2 To create the syscdcv1 database

Navigate to the etc directory under your Informix® installation directory and runthe following script:syscdcv1.sql You must use the informix user account when running this script. Verify that the syscdcv1 database exists.

89

-

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

90

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/maintainactivetcpconnections.html

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 or Linux: <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.

91

-

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

92

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/enablesqlstatementsinmanagementconsole.html

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.

93

-

--

IBM InfoSphere Change Data Capture, Version 10.2 InfoSphere CDC for Informix® metadata tables InfoSphere® CDC maintains a set of metadata tables that represent data about yourcurrent replication configuration. These tables are created in the schema anddatabase that you specify in the configuration tool and should be part of the backupstrategy for your database. InfoSphere CDC will not replicate these tables. Do notmodify the contents 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 Informix (Windows) Configuring InfoSphere CDC for Informix (UNIX and Linux)

94



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

95

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/supporteddatatypes.html

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

96

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.mcadminguide.doc/concepts/systemParametersInformix.html

--------

IBM InfoSphere Change Data Capture, Version 10.2 Commands for InfoSphere CDC for Informix® 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 Informix commands Setting the TSINSTANCE environment variable Controlling replication commands Database transaction log commands Exporting and importing configuration commands Managing tables for replication commands Monitoring replication commands Other commands

97

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/usingthecommands.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/settingthetsinstanceenvironmentvariable.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/controllingreplicationcommands.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/databasetransactionlogcommands.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/exportingandimportingconfigurationcommands.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/managingtablesforreplicationcommands.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/monitoringreplicationcommands.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/othercommands.html

--

-

-

--

-

--

IBM InfoSphere Change Data Capture, Version 10.2 Using the InfoSphere CDC for Informix® 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 Linuxor Windows.

98

-

-

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. UNIX or Linux 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.

99

---

IBM InfoSphere Change Data Capture, Version 10.2 Controlling replication commands This section contains commands that control replication in InfoSphere® CDC. See also:

dmendreplication - End replication dmrefresh - Refresh subscription dmstartmirror - Start mirroring

100

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmendreplication.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmrefresh.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmstartmirror.html

-----

-

-

-

--

IBM InfoSphere Change Data Capture, Version 10.2 dmendreplication - End replication Use this command to end refresh or mirroring on the specified subscriptions. Ending replication allows you to prepare for transitional activities in your businessenvironment and allows you to move to the next step in your business processes.Here are some examples of transitional activities in your business environment thatmay require an end to replication:

Initiating a database backup.Performing a regularly scheduled reboot of your source database server.Quiescing your database in preparation for an upgrade.Weekly batch processing has just completed.Preparing for off-line maintenance activities.

If you are replicating data continuously with Continuous mirroring and businessreasons arise that require an end to replication, InfoSphere® CDC provides multipleoptions that suit most business needs. If your business requirements dictate thatreplication must end at a particular point in your source database log because thetarget database must be in a known state when replication ends, you can choosefrom the following Scheduled End to replication options:

-se parameter—When specified without –t or –p, this parameter ends replication atthe current time in the source database log.-t parameter—When specified with –se, this parameter ends replication at a user-specified date and time.-p parameter—When specified with –se, this parameter ends replication at a user-specified log position.

An example of a scenario that might require these options is that you are populatinga reporting instance and you need stable (non-changing) data in your reportinginstance during the day. At the end of the day when you shut down your application,you can choose one of the Scheduled End (Net Change) options to update thereporting instance with data from the current day as well. If business requirements do not require a specific end point but do require a timeframe for ending replication, InfoSphere CDC provides escalating options (Normal,Immediate, and Abort) that end replication more rapidly at the expense of a slowerstart when resuming replication. For example, a routine end to replication with noparticular urgency may require the Normal option, whereas a sudden business needto end replication rapidly may require the Abort option. A routine reboot of a SANmight be appropriate for the Normal option, whereas a sudden and unexpectedhardware or application failure may require the Abort option. If you initiate an end to replication and business reasons warrant a change in thetime frame, you can reschedule the end of replication by specifying a new date andtime, a new position in the database log, or choose another option for endingreplication. Ending replication is also necessary if you want to update and make changes toyour subscription by:

Adding a table mapping to the subscription.Deleting a table mapping from the subscription.

101

--

-

--

--

--

Temporarily removing a table mapping from the subscription (parking a table).Modifying mapping details such as source and target column mappings, derivedcolumns, data translations, row and column selections, user exits, and so on.Updating the properties of a subscription when the structure of your source ortarget tables change.

This command also includes an asynchronous option for scripting (-nw parameter)that can be used with -se to allow your script to continue executing without waitingfor the Scheduled End to replication. You can also start and end replication in Management Console. For moreinformation, see Starting and ending replication. To stop an instance after ending replication on all subscriptions, use thedmshutdown command. Syntax dmendreplication [-I <INSTANCE_NAME>] [-c|-i|-a|-se [-t <date and time>|-p

<log position>] [-w|-nw]] <-A|-s <SUBSCRIPTION NAME ...>> [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the InfoSphere CDC instance for which you want to end replication.Alternatively, you can specify the TSINSTANCE environment variable in placeof this value.

-cSpecifies that InfoSphere CDC ends replication on the specified subscriptionswith the Normal option. InfoSphere CDC will use this option by default if you donot specify –se, -i, or –a.This option completes in progress work and then endsreplication. If a refresh is in progress, Normal will complete the refresh for thecurrent table before replication ends. Normal is the most appropriate option for most business requirements and isthe preferred method for ending replication in most situations.

-iSpecifies that InfoSphere CDC ends replication on the specified subscriptionswith the Immediate option.This option stops all in progress work and then endsreplication. Starting replication after using this option can be slower than using -c. If a refresh is in progress, the refresh for the current table will be interruptedand then replication will end. You should ensure that all dependent source database logs are availablebefore ending replication using the Immediate option. InfoSphere CDC mayneed to reprocess all the dependent source logs when you restart thesubscription. If InfoSphere CDC is currently processing a long runningtransaction when you end replication with Immediate, InfoSphere CDC mayhave to resume replication from the earliest open transaction in the databaselogs. Use the dmshowlogdependency command to determine which logs arerequired. Attention: Use this option if business reasons require replication to end fasterthan -c at the expense of a slower start when you resume replication on thespecified subscriptions.

102


--

--

--

--

--

--

-

-aSpecifies that InfoSphere CDC ends replication on the specified subscriptionswith the Abort option.This option stops all in progress work and then endsreplication rapidly. Starting replication after using this option can be muchslower than using -c. A refresh in progress will be interrupted and the target willstop processing any data that has not been committed before replication ends. You should ensure that all dependent source database logs are availablebefore ending replication using the Abort option. InfoSphere CDC may need toreprocess all the dependent source logs when you restart the subscription. IfInfoSphere CDC is currently processing a long running transaction when youend replication with Abort, InfoSphere CDC may have to resume replicationfrom the earliest open transaction in the database logs. Use thedmshowlogdependency command to determine which logs are required. 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.

-seSpecifies that InfoSphere CDC will end replication normally at the currentsource system time in the source database log with the Scheduled End option.The source system time when replication will end is set when you issue thiscommand.If you specify the following parameters with -se, replication will end ata specific date and time or log position:

–t—End replication at a specific date and time in your source database log.–p—End replication at a specific log position in your source database log.

Note: As latency between the source and target increases, the amount of timerequired to end replication will also increase.

-t <date and time>Indicates the date and time in the source database log when replication will endwhen using –se. When specifying a value for this parameter, use the followingformat:“yyyy-MM-dd HH:mm” This parameter is optional when you specify –se.

-p <log position>Indicates that InfoSphere CDC will end replication at the specified Informix®LSN in your source database log when using -se. The following is an exampleof an LSN format for Informix Dynamic Server:33500745064472 This parameter is optional when you specify –se.

-wIndicates that this command will wait for replication to end when you use –se. –w is the default setting for a Scheduled End to replication.If you are scriptingthe command with this parameter, your script must wait for -se processing tocomplete before it continues to execute. Note: This parameter does not apply if you specify –c, -i, or –a. InfoSphereCDC will always wait if you specify –c, -i, or –a when ending replication.

-nw

103

-

--

--

--

Indicates that this command will not wait for replication to end if you specify -se. If you are scripting this command, this parameter allows your script tocontinue executing (asynchronous) if -se processing is not complete.

-AIndicates that InfoSphere CDC ends replication on all subscriptions.Use –s toend replication on one or more subscriptions.

-s <SUBSCRIPTION NAME>Indicates the subscriptions where InfoSphere CDC will end replication.Tospecify multiple subscriptions, list the subscriptions separated by a space. Forexample: Subscription1 Subscription2 Subscription3 You must specify a value for this parameter or use –A for all subscriptions.

-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 dmendreplication -I MYINSTANCE -c -s FINANCEInfoSphere CDC ends replicationwith the Normal option for the FINANCE subscription in the specified instance. dmendreplication -I MYINSTANCE –se –t “2010-02-05-00-00” FINANCE -nwInfoSphere CDC ends replication with the Scheduled End option for the FINANCEsubscription at the specified time in the source database log. The command exitsbefore Scheduled End processing is complete. dmendreplication -I MYINSTANCE –a –s SUBSCRIPTION1 SUBSCRIPTION2InfoSphere CDC ends replication with the Abort option for SUBSCRIPTION1 andSUBSCRIPTION2 in the specified instance. Related reference: dmpark - Park table

104

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmpark.html

--

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmrefresh - Refresh subscription Use this command to refresh the specified subscriptions. When you refresh asubscription, InfoSphere® CDC ensures that the target tables are synchronized withthe source tables. Typically, you would refresh target tables when you have set thereplication method to Refresh on your tables. However, you can also refresh target tables that have a replication method set toMirror and a status of Active or Refresh. When you refresh a table configured formirroring, InfoSphere CDC refreshes the target table so that it is synchronized withthe source table and then marks a table capture point as the starting point formirroring. This command exits after it has successfully refreshed the specified subscriptions. Ifyou terminate this program while it is still running, InfoSphere CDC ends replicationimmediately for the specified subscriptions. Syntax dmrefresh [-I <INSTANCE_NAME>] [-a|-f] <-A|-s <SUBSCRIPTION_NAME ...> [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the InfoSphere CDC instance for which you want to refresh one ormore subscriptions. Alternatively, you can specify the TSINSTANCEenvironment variable in place of this value.

-aSpecifies that InfoSphere CDC refreshes all target tables in the subscription.

-fSpecifies that InfoSphere CDC refreshes only target tables that are flagged forrefresh. If you omit both the -a and -f options, InfoSphere CDC assumes -f bydefault.

-ASpecifies that InfoSphere CDC refreshes all subscriptions.

-s <SUBSCRIPTION_NAME>Specifies that InfoSphere CDC refreshes the indicated subscription. To specifymultiple 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 dmrefresh -I NEWINSTANCE -a -s FINANCEInfoSphere CDC refreshes all targettables in the Finance subscription.

105

106

-

-

-

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmstartmirror - Start mirroring Issue this command from your InfoSphere® CDC source to start mirroring on thespecified subscriptions. This command starts mirroring for any table with areplication method of Mirror and a status of Refresh or Active. Tables with areplication method of Mirror and a status of Refresh are refreshed before mirroringbegins. InfoSphere CDC provides two types of mirroring for source tables that are mappedto target tables: Continuous (-c parameter) and Scheduled End (Net Change) (-nparameter). The type of mirroring you select depends on your business needs. As its name implies, Continuous mirroring replicates changes to the target on acontinuous basis. Use this type of mirroring when business requirements dictate thatyou need replication to be running continuously and you do not have a clearlydefined reason to end replication at the present time. Scheduled End (Net Change) mirroring replicates changes (to the target) up to auser-specified point in the source database log and then ends replication. Use thistype of mirroring when business requirements dictate that you only replicate yourdata periodically and you have a clearly defined end point for the state of your targetdatabase when replication ends. Scheduled End (Net Change) mirroring allows youto end replication at the following points in your source database log:

-n parameter—When specified without –tor –p, this parameter ends replication atthe current time in the source database log.-t parameter—When specified with –n, this parameter ends replication at a user-specified date and time.-p parameter—When specified with –n, this parameter ends replication at a user-specified log position.

These user specified end points ensure that your target database is in a known statewhen replication ends. You can also start and end replication in Management Console. For moreinformation, see Starting and ending replication. Syntax dmstartmirror [-I <INSTANCE_NAME>] [-c|-n [-t <date and time>|-p

<log position>] [-w|-nw]] <-A|-s <SUBSCRIPTION NAME ...> [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the InfoSphere CDC instance for which you want to start mirroring.Alternatively, you can specify the TSINSTANCE environment variable in placeof this value.

-cSpecifies that InfoSphere CDC will start Continuous mirroring on the specifiedsubscriptions.If you do not specify –c or -n, InfoSphere CDC will startContinuous mirroring by default on the specified subscriptions.

-nSpecifies that InfoSphere CDC mirrors all committed database changes in thesource database and then ends replication normally at the current source

107


--

--

--

--

--

--

--

--

system time in the database log with the Scheduled End option. The sourcesystem time when replication will end is set when you issue this command.Ifyou specify the following parameters with –n, replication will end at a specificdate and time or log position:

–t—End replication at a specific date and time in your source database log.–p—End replication at a specific log position in your source database log.


-t <date and time>Indicates the date and time in the source database log when replication will endwhen using –n. When specifying a value for this parameter, use the followingformat:“yyyy-MM-dd HH:mm” This parameter is optional when you specify –n.

-p <log position>Indicates that InfoSphere CDC will end replication at the specified Informix®LSN in your source database log when using -se. Here is an example of anLSN format for Informix Dynamic Server:33500745064472 This parameter is optional when you specify –n.

-wIndicates that this command will wait for replication to end when you use –n. –wis the default setting for a Scheduled End to replication.If you are scripting thecommand with this parameter, your script must wait for -n processing tocomplete before it continues to execute. This parameter does not apply if you specify –c for Continuous mirroring.

-nwIndicates that this command will not wait for replication to end if you specify -n.If you are scripting this command, this parameter allows your script to continueexecuting (asynchronous) if -n processing is not complete.This parameter doesnot apply if you specify –c for Continuous mirroring.

-AIndicates that InfoSphere CDC starts mirroring for all subscriptions.Use –s tostart mirroring for one or more subscriptions.

-s <SUBSCRIPTION_NAME>Indicates the subscriptions where InfoSphere CDC will start mirroring. Tospecify multiple subscriptions, list the subscriptions separated by a space. Forexample:Subscription1 Subscription2 Subscription3 You must specify a value for this parameter or use –A for all subscriptions.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmstartmirror -I MYINSTANCE -c -s FINANCEInfoSphere CDC starts continuous

108

mirroring for the FINANCE subscription. dmstartmirror -I MYINSTANCE –n –p “000000FB:000001A4:0001” –nw –AInfoSphere CDC starts mirroring with the Scheduled End option for all subscriptionsin the specified instance. Replication will end at the specified Microsoft SQL ServerLSN in the source database log. The command will not wait for Scheduled Endprocessing to complete. dmstartmirror -I MYINSTANCE –n –t “2010-02-05-00-00” FINANCE -nwInfoSphereCDC starts mirroring with the Scheduled End option for the FINANCE subscription inthe MYINSTANCE instance. Replication will end at the specified time in the sourcedatabase log. The command will exit before Scheduled End processing is complete.

109

----

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:

dmdecodebookmark - Display verbose information bookmark dmsetbookmark - Set bookmark dmshowbookmark - Display bookmark information dmshowlogdependency - Show Log Dependency

110

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmdecodebookmark.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmsetbookmark.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmshowbookmark.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmshowlogdependency.html

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmdecodebookmark - Display verbose informationbookmark Use this command to display verbose information about a bookmark. Syntax dmdecodebookmark [-I <INSTANCE_NAME>] (-b <bookmark> | -f <bookmark_file>)

[-d <database_version>] [-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.

-b <bookmark>The bookmark as a hexadecimal-encoded string.

-f <bookmark_file>The bookmark file as a binary file.

-d<database_version>The database and version that generated the bookmark specified, if thebookmark was generated by InfoSphere CDC version 6.2 or earlier.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmdecodebookmark -f bookmark.txtInfoSphere CDC displays information about thebookmark stored in the bookmark.txt file.

111

--

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmsetbookmark - Set bookmark CAUTION: Improper use of this command can result in data loss or data duplication. Youshould only execute this command when directed by IBM Technical Support. Use this command on your InfoSphere® CDC source system to set the replicationposition (bookmark) in the stream of change data for a subscription. You can obtainthe replication position for a subscription with the dmshowbookmark command,which is executed on your InfoSphere CDC target system. Syntax dmsetbookmark [-I <INSTANCE_NAME>] -s <SUBSCRIPTION_NAME ...> (-b <bookmark> | -f

<bookmark_file_name>) [-a] [-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 <SUBSCRIPTION_NAME>The name of the subscription for which InfoSphere CDC sets a replicationposition (bookmark).

-b <bookmark>Indicates the replication position (bookmark) which determines the point in thedatabase log where you want InfoSphere CDC to resume mirroring. Whenmirroring resumes, InfoSphere CDC will start capturing change data at theindicated replication position. The replication position is a hexadecimal-encodedstring that is obtained from the dmshowbookmark command.

-f <bookmark_file_name>Indicates the name of the binary or XML file that contains all replication position(bookmark) information which determines the point in the database log whereyou want InfoSphere CDC to resume mirroring. When mirroring resumes,InfoSphere CDC will start capturing change data at the replication positionindicated in the file.You can specify an absolute path for the location of the file.If you do not specify an absolute path, you must place the file in the InfoSphereCDC installation directory. InfoSphere CDC will auto-detect the binary or XMLformat of the file.Note: If your source database is DB2® for LUW and isconfigured for DPF, you can generate the XML file used by this parameter byusing the dmshowbookmark command on your InfoSphere CDC target with the-x parameter.

-aSets all tables in the subscriptions (except for parked tables) as active as of thenew replication position (bookmark). If you do not specify this value,InfoSphere CDC will use -a by default.


112

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails Examples dmsetbookmark -I MYINSTANCE -b 6578616d706c65 -s FINANCEInfoSphere CDCsets a replication position (bookmark) for the Finance subscription for the specifiedinstance. This command specifies that mirroring will resume at the indicatedreplication position in the database log. dmsetbookmark -I MYINSTANCE -f bookmark -s FINANCEInfoSphere CDC sets areplication position (bookmark) for the Finance subscription for the specifiedinstance. This command specifies that mirroring will resume at the replicationposition (bookmark) contained in the bookmark file. InfoSphere CDC will auto-detectthe XML or binary format of the file. The file is located in InfoSphere CDC installationdirectory since no absolute path is specified.

113

--

--

--

--

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


-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.

114

--

--

-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.


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.

115

---

-

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmshowlogdependency - Show Log Dependency Use this command to display information about source database logs in order toimplement a log retention policy. For a specified instance of InfoSphere® CDC, youcan display:

A list of all the logs that are required for the specified instance.The earliest open transaction in the log for the specified instance.The logs which contain the position confirmed by the target database for thespecified instance.The logs which contain the position the specified instance is reading from.

You must issue this command on your InfoSphere CDC source system. Syntax dmshowlogdependency [-I <INSTANCE_NAME>] ( -i | -t | -l)[-c]

(-s <SUBSCRIPTION_NAME> | -A | -a) [-v] [-L <locale>] Parameters


-cConsiders the current position instead of the restart position.

-iDisplays the complete list of required source database logs for the specifiedinstance. These logs are required to start replication and contain data that hasnot been applied to the target. If you specify -A, the command considers allsubscriptions and displays a list of logs required to start replication on allsubscriptions. If you specify -s, the command displays a list of logs required tostart replication on the specified subscription. If you decide to use -a, then thecommand displays a list of logs required to start replication for each individualsubscription. Each list contains logs required for the correspondingsubscription.

-tDisplays the source database log which contains the position confirmed by thetarget database. If you specify -A, the command considers all subscriptions anddisplays the oldest log. If you specify -s, the command displays the log for thespecified subscription. If you decide to use -a, then the command displays onelog for each subscription. Each log contains the position confirmed by the targetdatabase for the corresponding subscription.

-lDisplays the source database log which contains the position InfoSphere CDCis reading from. If you specify -A, the command considers all subscriptions anddisplays the oldest log. If you specify -s, the command displays the log for thespecified subscription. If you decide to use-a, then the command displays onelog for each subscription. Each log contains the position for the correspondingsubscription.

116

-

--

--

--

--

--

Accurate information about where in the log InfoSphere CDC is reading will onlybe provided if there is a steady stream of in scope data being applied andcommitted on the source database

-s <SUBSCRIPTION_NAME>Displays a source database log or a list of logs for the specified subscription.

-ADisplays a source database log or a list of logs for all subscriptions.

-aDisplays a source database log or a list of logs for each individual subscription.

-vSpecifies verbose output (otherwise, the output is formatted for scripting).


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. The command can also print as NULL if there are notables defined in the subscription. Examples dmshowlogdependency -I MYINSTANCE -i -s MYSUBSCRIPTIONNAMEDisplaysthe complete list of required source database logs for the specified instance andsubscription. dmshowlogdependency -I MYINSTANCE -ADisplays the complete list of requiredsource database logs for all subscriptions in the specified instance.

117

--

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

118

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmexportconfiguration.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmimportconfiguration.html

--

--

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.


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

119

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmimportconfiguration.html

--

--

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. Note: You can script this command and use an InfoSphere CDC silent installation todeploy InfoSphere CDC on multiple systems. 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.


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

120

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmexportconfiguration.html

-------

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:

dmdescribe - Describe source tables dmflagforrefresh - Flag for Refresh dmmarktablecapturepoint - Mark a table capture point on a source table dmpark - Park table dmreaddtable - Update source table definition dmreassigntable - Update target table definition dmsetreplicationmethod - Set replication method

121

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmdescribe.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmflagforrefresh.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmmarktablecapturepoint.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmpark.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmreaddtable.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmreassigntable.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmsetreplicationmethod.html

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmdescribe - Describe source tables Use this command to send source table metadata changes over to the target. This command exits after it has successfully described the specified subscriptions. Syntax dmdescribe [-I <INSTANCE_NAME>] <-A|-s <SUBSCRIPTION_NAME ...> [-L <locale>] Parameters

-I <INSTANCE_NAME>Specifies the InfoSphere® CDC instance for which you want to send sourcemetadata changes over to the target. Alternatively, you can specify theTSINSTANCE environment variable in place of this value.

-ASpecifies that InfoSphere CDC will send source metadata changes made to allsubscriptions over to the target.

-s <SUBSCRIPTION_NAME>Specifies that InfoSphere CDC sends source metadata changes for theindicated subscriptions over to the target. To specify multiple subscriptions, listthe subscriptions separated by a space.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmdescribe -I NEWINSTANCE -s FINANCEInfoSphere CDC sends sourcemetadata changes in the Finance subscription over to the target for the specifiedinstance.

122

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmflagforrefresh - Flag for Refresh Use this command to flag a source table for refresh. When you flag a table forrefresh, you are selecting the tables that you want to refresh at a future point in time. Syntax dmflagforrefresh [-I <INSTANCE_NAME>] -s <SUBSCRIPTION_NAME ...>

<-A|-t <schema>.<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 name of the subscription. To specify multiple subscriptions, list thesubscriptions separated by a space.

-ASpecifies that InfoSphere CDC flags all source tables for refresh in thesubscription.

-t <schema>.<table>Specifies the name of a source table in the subscription that InfoSphere CDCflags for refresh. You must specify the table name in the format schema.table.To specify multiple tables, list the tables separated by a space.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmflagforrefresh -I MYINSTANCE -s FINANCE -AInfoSphere CDC flags for refreshall source tables in the Finance subscription for the specified instance.

123

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmmarktablecapturepoint - Mark a table capturepoint on a source table Use this command to mark a table capture point on a source table and change thestatus of the table to Active. If you changed the table before executing thiscommand, those changes will not be replicated. Mark a table capture point on a source table when you want to override an existingposition in the stream of changed data. This is possible when you have alreadysynchronized (refreshed) your source and target tables using an application otherthan InfoSphere® CDC (for example, using the import or export capabilities of yourdatabase platform) and you know the point in time your source and target aresynchronized with each other. InfoSphere CDC mirrors changes to the target tablefrom the current position in the stream of changed data. This position is set byInfoSphere CDC when you select Mirror (Change Data Capture) after mapping yourtables in the Map Tables wizard. If you want to override the position set byInfoSphere CDC, then you can manually mark a table capture point in ManagementConsole. When you decide to start mirroring on the subscription, InfoSphere CDCidentifies the position you have set as the point in time from which to capture andreplicate database changes to the target. Syntax dmmarktablecapturepoint [-I <INSTANCE_NAME>] -s <SUBSCRIPTION_NAME ...>

-A|-t <<schema>.<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 name. To specify multiple subscriptions, list thesubscriptions separated by a space.

-ASpecifies that InfoSphere CDC overrides an existing position in the stream ofchanged data on all source tables in the subscription.

-t <schema>.<table>Specifies the name of a source table in the subscription on which InfoSphereCDC marks a table capture point. You must specify the table name in theformat schema.table. To specify multiple tables, list the tables separated by aspace.


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

124

dmmarktablecapturepoint -I MYINSTANCE -s FINANCE -AInfoSphere CDC sets thestatus of all tables in the Finance subscription to Active. dmmarktablecapturepoint -I MYINSTANCE -s ACCOUNTING -t myschema.mytableInfoSphere CDC sets the status of the specified table in the Accounting subscriptionto Active.

125

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmpark - Park table Use this command to park a source table. By parking a source table, you tellInfoSphere® CDC that you do not want to capture changes for that particular tablein a subscription. When you park a table, InfoSphere CDC does not replicate anysubsequent changes you make on the source table, which may result in inconsistentsource and target tables. Note: Before you can park a source table, if you are mirroring the table to the target,then you need to end replication on the subscription. For more information, see thedmendreplication command. Syntax dmpark [-I <INSTANCE_NAME>] -s <SUBSCRIPTION_NAME ...> <-A|-t <schema>.<table> ...>

[-L <locale>] Parameters


-s <SUBSCRIPTION_NAME>Specifies the subscription name. To specify multiple subscriptions, list thesubscriptions separated by a space.

-ASpecifies that InfoSphere CDC parks all source tables in the subscription.

-t <schema>.<table>Specifies the name of a source table in the subscription that InfoSphere CDCparks. You must specify the table name in the format schema.table. To specifymultiple tables, list the tables separated by a space.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmpark -I MYINSTANCE -s FINANCE -AInfoSphere CDC parks all source tables inthe Finance subscription. Related reference: dmendreplication - End replication

126

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmendreplication.html

127

-

-

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmreaddtable - Update source table definition Use this command to update the definition of one or more source tables in theInfoSphere® CDC metadata. Run this command after you have changed thedefinition of a source table using your relational database. Notes:

This command will set the table status to Parked after updating the source tabledefinition in the InfoSphere CDC metadata. This command is not the equivalent of the Management Console Update SourceTable Definition dialog, which you access by selecting Configuration >Subscriptions > <subscription_name>, then right-clicking the table mapping nameunder Table Mappings, and then selecting Update Table Definition > Source Table.

Note: Syntax dmreaddtable [-I <INSTANCE_NAME>] <-A|-t <schema>.<table> ...> [-L <locale>] Parameters


-ASpecifies that InfoSphere CDC updates definitions for all source tables that areavailable for replication.

-t <schema>.<table>Specifies the name of a source table in the subscription for which InfoSphereCDC updates the definition. You must specify the table name in the formatschema.table. To specify multiple tables, list the tables separated by a space.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmreaddtable -I NEWINSTANCE -AInfoSphere CDC updates definitions for allsource tables that are available for replication. The status for all tables will be set toParked.

128

--

--

--

--

--

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 ...>



-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 <schema>.<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 schema.table. Tospecify multiple tables, list the tables separated by a space.


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. dmreassigntable -I CDCINSTANCE -s FINANCE -t SCHEMA1.SRCTBL1InfoSphere CDC updates the definition for the target table that is mapped to theSCHEMA1.SRCTBL1 source table in the Finance subscription.

129

--

--

--

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmsetreplicationmethod - Set replication method Use this command to change the replication method for tables in a subscription.When running this command, InfoSphere® CDC changes the status of any Activetables to Refresh. Note: Before you run this command, you must end replication on the subscription. Syntax dmsetreplicationmethod [-I <INSTANCE_NAME>] <-r|-m> -s <SUBSCRIPTION_NAME ...>



-mSpecifies that tables will use Mirror (Change Data Capture) as the replicationmethod.

-rSpecifies that tables will use Refresh (Snapshot) as the replication method.

-s <SUBSCRIPTION_NAME>Specifies the name of the subscriptions. To specify multiple subscriptions, listthe subscriptions separated by a space.

-ASpecifies that all tables in the subscription will use the indicated replicationmethod.

-t <schema>.<table>Specifies the name of a source table in the subscription that will use theindicated replication method. You must specify the table name in the formatschema.table. To specify multiple tables, list the tables separated by a space.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmsetreplicationmethod -I MYINSTANCE -r -s FINANCE -AAll tables in the Financesubscription will use Refresh as the replication method in the specified InfoSphereCDC instance. dmsetreplicationmethod -I NEWINSTANCE -m -s FINANCE -t acct.taxcodesThesource table acct.taxcodes in the Finance subscription will use Mirror as thereplication method in the specified InfoSphere CDC instance.

130

131

---

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 dmgetsubscriptionstatus - Get subscription status dmshowevents - Display InfoSphere CDC events

132

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmclearevents.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmgetsubscriptionstatus.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmshowevents.html

--

--

--

--

--

--

--

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 ...>


-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.


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.

133

--

--

--

--

--

----

IBM InfoSphere Change Data Capture, Version 10.2 dmgetsubscriptionstatus - Get subscription status Issue this command on the InfoSphere® CDC source engine to retrieve statusinformation for one or more subscriptions and send the results to standard output. Please note that this command can be issued on Linux, UNIX and Windows sourcereplication engines only, not on target replication engines. Syntax dmgetsubscriptionstatus [-I <INSTANCE_NAME>] [-p] <-A|-s <SUBSCRIPTION_NAME ...>



-pSpecifies that InfoSphere CDC sends status information to standard output.

-ASpecifies that InfoSphere CDC retrieves status information for all subscriptions.

-s <SUBSCRIPTION_NAME>Specifies the name of the subscription for which status information is retrieved.To specify multiple subscriptions, list the subscriptions separated by a space.


Result This command returns one of the following statuses for each subscription:

Recovering—The subscription is in an undetermined state.Idle—The subscription is not running.Starting—The subscription is in start up mode and is not currently replicating data.Running—The subscription is running and replicating data.

Examples dmgetsubscriptionstatus -I MYINSTANCE -p -AInfoSphere CDC retrieves statusinformation for all subscriptions and sends the results to standard output for thespecified instance.

134

--

--

--

--

--

--

--

--

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


-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


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

135

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.


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

normally.


publication.c|Describe conversation with ATLANTA completed successfully.


publication.c|Describe conversation started by ATLANTA.


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.

136

-------------

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 dmmarkexternalunloadstart - Start table data unload dmmarkexternalunloadend - End table data unload dmmdcommander dmmdconsole dmset - Set InfoSphere CDC system parameter dmshowversion - Show InfoSphere CDC version dmshutdown - Shut down InfoSphere CDC dmsupportinfo - Collect IBM Support information dmterminate - Terminate InfoSphere CDC processes dmts32 - Start InfoSphere CDC dmts64 - Start InfoSphere CDC

137


https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmconfigurets.html



https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmmdcommander.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmmdconsole.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmset.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmshowversion.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmshutdown.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmsupportinfo.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmterminate.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmts32.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmts64.html

--

--

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 for UNIX and Linux and in<Installation_directory>\instance\<instance_name>\conf\backup for Windows. Thefiles in the backup directory should be stored on separate media for possiblerecovery. Syntax dmbackupmd [-I <INSTANCE_NAME>] [-L <locale>] Parameters



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

138

--

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


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

139

--

--

--

--

-

dmmarkexternalunloadstart - Start table data unload Use this command when you want to perform a refresh outside of InfoSphere® CDCwhile the tables are still active. dmmarkexternalunloadstart will mark the starting point of the data unload for theexternal tool that will be used to load the data to the target replication engine. Syntax dmmarkexternalunloadstart [-I <INSTANCE_NAME>] [-L <locale>]

-s <SUBSCRIPTION_NAME ...> [-t <table>] 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.

-s <SUBSCRIPTION_NAME>Specifies that InfoSphere CDC sends source metadata changes for theindicated subscription to the target. To specify multiple subscriptions, list thesubscriptions separated by a space.

[-t <table>]Specifies the name of a source table in the subscription on which InfoSphereCDC marks a table capture point. The table must be named in the format<schema>.<table>. To specify multiple tables, list the tables separated by aspace.To mark the table capture point on all the source tables in the specifiedsubscription, omit this parameter.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmmarkexternalunloadstart -I MYINSTANCE -t SCHEMA1.MYTABLEInfoSphereCDC marks the unload start point in the table named MYTABLE in the specifiedschema for the specified instance. Related concepts: Performing an external refresh

140


--

--

--

--

-

dmmarkexternalunloadend - End table data unload Use this command when you want to perform a refresh outside of InfoSphere® CDCwhile the tables are still active. dmmarkexternalunloadend will mark the ending point of the data unload for theexternal tool that will be used to load the data to the target replication engine. Syntax dmmarkexternalunloadend [-I <INSTANCE_NAME>] [-L <locale>]

-s <SUBSCRIPTION_NAME ...> [-t <table>] 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.

-s <SUBSCRIPTION_NAME>Specifies that InfoSphere CDC sends source metadata changes for theindicated subscriptions over to the target. To specify multiple subscriptions, listthe subscriptions separated by a space.

[-t <table>]Specifies the name of a source table in the subscription on which InfoSphereCDC marks a table capture point. The tables must be named in the format<schema>.<table>. To specify multiple tables, list the tables separated by aspace.To mark the table capture point on all the source tables in the specifiedsubscription, omit this parameter.

Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Examples dmmarkexternalunloadend -I MYINSTANCE -t SCHEMA1.MYTABLEInfoSphereCDC marks the unload end point in the table named MYTABLE in the specifiedschema for the specified instance. Related concepts: Performing an external refresh

141


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

142

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

143

--

--

--

--

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


<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.


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.

144

--

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


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

145

--

--

--

--

IBM InfoSphere Change Data Capture, Version 10.2 dmshutdown - Shut down InfoSphere CDC Use this command to stop an instance of InfoSphere® CDC and end replication onall subscriptions that use the instance as a source. This command is often usedprior to taking a server or database offline for maintenance purposes or upgradingInfoSphere 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 specified instance as a source and as a target. Thiscommand will not complete successfully if target subscriptions are still running. To end replication on subscriptions that use the specified instance as a target, youcan use the –a parameter which will generate an error when forcefully endingreplication on subscriptions that use the specified instance as the target. If this command does not end InfoSphere CDC processes and stop the specifiedinstance, use the dmterminate command on the UNIX and Linux platforms to force acomplete shut down and on Windows, to stop the service. Syntax dmshutdown [-I <INSTANCE_NAME>] [-c|-i|-a|-se [-t <date and time>|-p <log position>]



-cSpecifies that InfoSphere CDC stops the specified instance and endsreplication on all subscriptions that use the instance as a source with theNormal option. InfoSphere CDC will use this option by default if you do notspecify –se, -i, or –a.This option completes in progress work and then endsreplication. If a refresh is in progress, Normal will complete the refresh for thecurrent table before replication ends. Normal is the most appropriate option for most business requirements and isthe preferred method for ending replication in most situations.

-iSpecifies that InfoSphere CDC stops the specified instance and endsreplication on all subscriptions that use the instance as a source with theImmediate option.This option stops all in progress work and then endsreplication. Starting replication after using this option can be slower than using -c. If a refresh is in progress, the refresh for the current table will be interruptedand then replication will end. Attention: Use this option if business reasons require replication to end fasterthan -c at the expense of a slower start when you resume replication on thespecified subscriptions.

-aSpecifies that InfoSphere CDC stops the specified instance and endsreplication on all subscriptions that use the instance as a source or target withthe Abort option. Subscriptions that use the specified instance as a target will

146

--

-

-

--

--

--

end replication with an error.This option stops all in progress work and thenends replication rapidly. Starting replication after using this option can be muchslower than using -c. A refresh in progress will be interrupted and the target willstop processing 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 as a sourceor target.

-seSpecifies that InfoSphere CDC will stop the specified instance and endreplication normally at the current source system time in the source databaselog with the Scheduled End option. Replication will end on subscriptions thatuse the specified instance as a source. The source system time whenreplication will end is set when you issue this command.You can use thefollowing parameters with this option to end replication at a specific date andtime or log position:

–t—Stop the instance and end replication at a specific date and time in yoursource database log.–p—Stop the instance and end replication at a specific log position in yoursource database log.


-t <date and time>Indicates the date and time in the source database log when replication will endwhen using –se. When specifying a value for this parameter, use the followingformat:“yyyy-MM-dd HH:mm” This parameter is optional when you specify –se.

-p <log position>Indicates that InfoSphere CDC will end replication at the specified Informix®LSN in your source database log when using -se. Here is an example of anLSN format for Informix Dynamic Server:33500745064472 This parameter is optional when you specify –se.


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Related reference: dmterminate - Terminate InfoSphere CDC processes

147

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmterminate.html

148

--

--

--

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.


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

149

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/contactingibmsupport.html

150

--

IBM InfoSphere Change Data Capture, Version 10.2 dmterminate - Terminate InfoSphere CDC processes Note: This command is only supported on the UNIX and Linux platforms. Use this command to terminate all InfoSphere® CDC processes for all instancesrunning on a UNIX or Linux server that you cannot completely shut down with thedmshutdown command. InfoSphere CDC terminates only processes that are startedby the UNIX account used to run this command. You can use this command prior to taking a server or database offline formaintenance purposes or upgrading InfoSphere CDC to the latest version. Use the dmshutdown command to gracefully shut down InfoSphere CDC. Ifdmshutdown is unable to completely shut down InfoSphere CDC, then usedmterminate to terminate any active InfoSphere CDC processes that still remainafter issuing dmshutdown. Syntax dmterminate [-L <locale>] Parameters


Result This command returns a value of 0 if the command was successful and a non-zerovalue if the command fails. Related reference: dmshutdown - Shut down InfoSphere CDC

151

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmshutdown.html

--

--

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.


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.

152

--

--

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.


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.

153

-

--

IBM InfoSphere Change Data Capture, Version 10.2 User exits for InfoSphere CDC for Informix® 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 the following type of user exit:

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:

Sample Java class user exits for InfoSphere CDC for Informix InfoSphere CDC API reference – Javadocs

154

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/sampleuserexits.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/apireferencejavadocs.html

-

-

-

-

-

-

-

-

-

--

IBM InfoSphere Change Data Capture, Version 10.2 Sample Java class user exits for InfoSphere CDCfor Informix® 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) To compile the sample Java class user exits (UNIX and Linux)

155

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/compilethesampleuserexits_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/compilethesampleuserexits_unix.html

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.

156

1.2.

3.4.

5.

6.7.

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

Stop InfoSphere® CDC.Unzip the samples.jar file into the lib directory in your InfoSphere CDC installationdirectory. Make sure you maintain the directory structure when unzipping the jarfile.After unzipping the jar file, you will have a directory structure like the following:<installation_directory>/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 directory 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.

157

--

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 and Linux—<InfoSphere CDC installation directory>/docs/api

158

----

IBM InfoSphere Change Data Capture, Version 10.2 Conflict resolution audit table When InfoSphere® CDC resolves a conflict between the source and target tables, itrecords information about the resolution in the TS_CONFAUD table. InfoSphereCDC creates this table in the target metadata location that is specified during theconfiguration of InfoSphere CDC. Note:InfoSphere CDC will add data continuously to the audit table as conflicts occur,but will never purge data from the table. Depending on the number of conflicts, theaudit table will to grow in size over time. It is the user's responsibility to schedulemaintenance (such as using a DELETE FROM statement) on the conflict resolutionaudit table regularly. A good practice would be to remove the applicable informationfrom the audit table after you have resolved each conflict. In this section, you will learn:

Structure of the conflict resolution audit table Row image format Truncated images Unaudited data types

159

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/structureoftheconflictresolutionaudittable.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/rowimageformat.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/truncatedimages.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/unauditeddatatypes.html

IBM InfoSphere Change Data Capture, Version 10.2 Structure of the conflict resolution audit table You can use the TS_CONFAUD table to track how conflict resolution affects yourtarget table. For example, you can query the AFTERIMG column to see when achange was made to the target table. Then you can review the contents of theBEFOREIMG and AFTERIMG columns to see the change on the source table thatresulted in the data on the target table. This can help in identifying issues in yourconflict resolution strategy. Conflict detection and resolution is configured in Management Console. The structure of the TS_CONFAUD table is as follows:

Column DescriptionCNFTIME The date and time on the target when the

conflict was detected.SRCTIME The time the conflicting data was applied

to the source table.SRCSYSID The source ID of the subscription.SRCSCHEMA The schema or library name for the

source table.SRCNAME The name of the source table.SRCMEMBER This field is blank.TGTSCHEMA The schema or library for the target table.TGTNAME The name of the target table.TGTMEMBER This column is only used for the IBM® i

platform.OPTYPE The row-level operation on the source

that caused the conflict. The value is oneof: 1—Inserted into the sourcetable.2—Updated on the sourcetable.3—Deleted from the source table.

CNFTYPE The type of conflict that was detected.The value is one of: 1—Inserted into thesource table. The key for that rowalready exists in the targettable.2—Updated or deleted on thesource table. The key for that row doesnot exist in the target table.3—Updatedor deleted on the source table. Theimages of the source and target tablesdo not match.4—Unexpected conflictwas detected.

160

RESMTD The conflict resolution method that wasused. The value is one of: 1—Sourcewins2—Target wins3—Largest valuewins4—Smallest value wins5—UserexitIf the resolution method was None,then a row will not be entered into thistable. See your InfoSphere® CDCdocumentation for more information onthese methods.

CNFRES Indicates if the conflict was resolved. Thevalue is one of: Y—Conflict wasresolved.N—Conflict was not resolved.

BEFORETRNC Indicates if the before image stored inBEFOREIMG was truncated. The valueis one of:Y—Value was truncated.N—Value wasnot truncated.

BEFOREIMG A representation of the row in the sourcetable after it was changed. See RowImage Format for more information onthe format of this column.

AFTERTRNC Indicates if the after image stored inAFTERIMG was truncated. The value isone of:Y—Value was truncated.N—Value wasnot truncated.

AFTERIMG A representation of the row in the sourcetable after it was changed. See RowImage Format for more information onthe format of this column.

TGTIMG A representation of the row in the targettable before replication occurred. SeeRow Image Format for more informationon the format of this column.

TGTTRNC Indicates if the after image stored inTGTIMG was truncated. The value is oneof: Y—Value was truncated.N—Valuewas not truncated.

WINIMG A representation of the final row in thetarget table after conflict resolution hasoccurred. See Row Image Format formore information on the format of thiscolumn.

WINTRNC Indicates if the image stored in WINIMGwas truncated. The value is one of:Y—Value was truncated.N—Value wasnot truncated.

161

Related concepts: Row image format

162

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/rowimageformat.html

IBM InfoSphere Change Data Capture, Version 10.2 Row image format The BEFOREIMG, AFTERIMG, TGTIMG, and WINIMG columns in the audit tableshow representations of a row in either the source or target table. The images in these columns are limited by the maximum length of VARCHAR dataon your target metadata database. The images contain all of the values in the row,except for data in raw, binary, or LOB columns. The data from each column ispresented in the following format:(length:value) In the format above, value is the data in the column and length is the number ofcharacters used to represent the data. The images display numeric data ascharacter strings and NULL values as (null). The row images match the column order in the source table and the conflictresolution audit table. These images may be truncated if the image is longer thanthe maximum length of VARCHAR data in the target metadata database. If a table'skey column is not the first column in the table, then it may be truncated.

163

IBM InfoSphere Change Data Capture, Version 10.2 Truncated images If a row image is longer than the maximum length of a VARCHAR column, then theywill be truncated. There is a column in the audit table that indicates if each imagecolumn has been truncated. For example, if WINTRNC is Y, then the value ofWINIMG was truncated. The format of the truncated column is:(-length:value) In the format above, value is the truncated value and length is the number ofcharacters in the truncated string.

164

---

IBM InfoSphere Change Data Capture, Version 10.2 Unaudited data types The audit table does not include columns of the following data types in its images:

IMAGENTEXTTEXT

If the source or target table contains rows with these data types, then the imagesimply overlooks them. Binary data will appear in the images as hex-encodedcharacters. The image does not store any information from unsupported columns.

165

--

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

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

166

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/uninstallingcdc_windows.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/uninstallingcdc_unixandlinux.html

1.2.3.

4.

IBM InfoSphere Change Data Capture, Version 10.2 To uninstall InfoSphere CDC for Informix®(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.

167

1.2.

3.

4.5.6.

7.

IBM InfoSphere Change Data Capture, Version 10.2 To uninstall InfoSphere CDC for Informix® (UNIXand Linux)

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.

168

---

--

-

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

169

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/usingibmsupportassistantisa.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/logmessages.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/concepts/contactingibmsupport.html

-

-

--

---

-

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)

170

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/useisa_productproblem_cmdline.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/useisa_productproblem_GUI.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/useisa_enhancement_cmdline.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/useisa_enhancement_cmdline.html

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/tasks/useisa_enhancement_GUI.html

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

171

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.

172

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.

173

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

174

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.

175

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

176

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.

177

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.

178

-

-

-

-

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.

179

-

-

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

180

http://www.ibm.com/software/data/infosphere/support/change-data-capture/

http://www.ibm.com/planetwide/

https://www.ibm.com/support/knowledgecenter/SSTRGZ_10.2.1/com.ibm.cdcdoc.cdcforinformix.doc/refs/dmsupportinfo.html

Documents

7 System requirements for InfoSphere CDC for Informix 10 11 12