Click here to load reader

PowerExchange SQL Server Adapter Guide...1 C HAPTER 1 Overview This chapter includes the following topics: ♦ PowerExchange Batch, 1 ♦ Change Capture with PowerExchange Change and

  • View
    1

  • Download
    1

Embed Size (px)

Text of PowerExchange SQL Server Adapter Guide...1 C HAPTER 1 Overview This chapter includes the following...

  • Informatica® PowerExchange®(Version 8.6)

    SQL Server Adapter Guide

  • Informatica PowerExchange SQL Server Adapter Guide

    Version 8.6 June 2008

    Copyright (c) 1998–2008 Informatica Corporation. All rights reserved.

    This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending.

    Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

    The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

    Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

    Copyright, Byte Designs Ltd. All rights reserved.

    This product includes ICU software which is copyright (c) 1995-2003 International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://www-306.ibm.com/software/globalization/icu/license.jsp.

    The product includes the zlib library copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler.

    DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

    Part Number: PWX-MSQ-860-0001

  • Table of Contents

    Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiInformatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

    Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

    Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

    Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

    Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

    Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

    Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PowerExchange Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

    Change Capture with PowerExchange Change and PowerExchange Real-time . . . . . . . . . . . . . . 1

    Phases of Change Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

    PowerExchange Change Capture Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

    Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    Chapter 2: Bulk Movement of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Accessing Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Testing a Remote PowerExchange Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Sourcing Microsoft SQL Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Chapter 3: Personal Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Using Personal Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

    Chapter 4: Configuring SQL Server Change Data Capture . . . . . . . . . . . . . . . . . . . . . 9Configuring SQL Server for Change Data Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

    Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

    Configuring PowerExchange for Change Data Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

    Configuring the DBMOVER Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

    Configuring Real-time Extraction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

    Configuring Batch Extraction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

    Configuring Continuous Extraction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Implementing SQL Server Change Data Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Managing Capture Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    Adding a Capture Registration to an Existing Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Deleting a Registration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Deleting a Registration Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Viewing a Registration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Viewing a Capture Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Extraction Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Define the Extraction Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

    Deleting an Extraction Group or Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

    Application Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    Table of Contents iii

  • Reset to a New Start Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

    Migrating to Condense File Extraction Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

    Chapter 5: PowerExchange Condense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29PowerExchange Condense Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

    Making Capture Registrations Eligible for Condense Processing . . . . . . . . . . . . . . . . . . . 29

    Configuring the PowerExchange Condense Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

    PowerExchange Condense Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

    PowerExchange Condense Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

    Configuring PowerExchange Condense Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

    Starting and Stopping PowerExchange Condense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Starting PowerExchange Condense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Stopping PowerExchange Condense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

    Chapter 6: Managing Change Data Capture Definitions. . . . . . . . . . . . . . . . . . . . . . . 37Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

    Changing the Underlying Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

    Adding Columns to Capture Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

    Removing Columns from Capture Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

    Modifying Columns in Capture Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

    Changing Extraction Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

    Associating Capture Registrations with Extraction Maps . . . . . . . . . . . . . . . . . . . . . . . . . 41

    Adding or Removing Columns from Extraction Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

    Version Indicator in Extraction Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

    Changing Properties of Capture Registrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    Amending a Capture Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    Setting to Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    Set to History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

    Chapter 7: Accessing CDC Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Accessing Captures Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    Creating Restart Points with DTLUAPPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

    DTLUAPPL - The Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

    Running DTLUAPPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

    Adding an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

    Modifying an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

    Printing an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

    Real-time Extraction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

    Testing with the Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

    Using Real-time Extraction Mode in PowerCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    SQL Server CDC Condense File Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    Chapter 8: Stopping Change Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

    iv Table of Contents

  • Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

    Table of Contents v

  • vi Table of Contents

  • Preface

    This manual is designed to give the required information to develop a Microsoft SQL Server data capture environment and must only be used once all the required steps from the PowerExchange Installation Guide are completed successfully. It is assumed that the PowerExchange Listener is active on the target platform and that it has been tested by use of the Ping utility.

    The steps required in this manual depends on the functions of the product will be used at this installation. There are two strategies available for refreshing data in a target database:

    ♦ Bulk update using PowerCenter

    ♦ Frequent or near real-time update using data capture techniques

    PowerCenter or other third-party software can be used to move the data to the target.

    Informatica Resources

    Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

    Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected] We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments.

    Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

    vii

  • Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.

    Informatica Global Customer SupportThere are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone, email, or the WebSupport Service.

    Use the following email addresses to contact Informatica Global Customer Support:

    [email protected] for technical inquiries

    [email protected] for general customer service requests

    WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

    Use the following telephone numbers to contact Informatica Global Customer Support:

    North America / South America Europe / Middle East / Africa Asia / Australia

    Informatica Corporation Headquarters100 Cardinal WayRedwood City, California 94063United States

    Toll Free +1 877 463 2435

    Standard RateBrazil: +55 11 3523 7761 Mexico: +52 55 1168 9763 United States: +1 650 385 5800

    Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

    Toll Free 00 800 4632 4357

    Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

    Informatica Business Solutions Pvt. Ltd.Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008India

    Toll Free Australia: 1 800 151 830Singapore: 001 800 4632 4357

    Standard RateIndia: +91 80 4112 5738

    viii Preface

  • C H A P T E R 1

    Overview

    This chapter includes the following topics:

    ♦ PowerExchange Batch, 1

    ♦ Change Capture with PowerExchange Change and PowerExchange Real-time, 1

    ♦ Phases of Change Propagation, 2

    ♦ Software Requirements, 3

    PowerExchange BatchPowerExchange Batch allows you to perform bulk moves of data from data source to target. You can move data from and to UNIX or Linux, Windows, z/OS, and i5/OS.

    Change Capture with PowerExchange Change and PowerExchange Real-time

    Continually repeating the load process through PowerExchange Batch may be costly in terms of space, time, and human resources. What is required is the ability to capture additions, amendments, and deletions to the source data structures and the data itself. In addition, there is a need to ensure that if several changes have taken place, only the latest change is applied.

    A number of rules are required to ensure that the start point for the changes and the changes themselves can be clearly identified. The change management process must impact on operational systems and procedures. The process needs to be integrated within them to ensure continuous identification and capture of changes.

    The logical extension of the initial PowerExchange Batch process is PowerExchange Change that retrieves updates at a periodicity set by the user, and the near real-time version PowerExchange Real-time. A variety of components work together to propagate changed data from a source to a target. This section provides a diagram and descriptions of the data-flow and control-flow components of PowerExchange Change. PowerExchange Change and PowerExchange Real-time are both briefly covered here for clarity, however, for MS SQL Server capture, PowerExchange Real-time is the only option.

    PowerExchange Change is enabled by the CAPX access method from condensed files.

    PowerExchange Real-time is enabled by the CAPXRT access method direct against the PowerExchange Logger.

    1

  • PowerExchange Change and PowerExchange Real-time make data available to be applied to target databases but does not apply the data directly. In these instances, the apply process can be carried out with PowerCenter or a partner tool.

    The following figure shows how the CAPXRT or CAPX access methods make changes available to PowerCenter so that PowerCenter can apply the changes to the target databases:

    Phases of Change PropagationChange capture is the process of capturing changes made to the source database and creating an inventory of those changes in an internal log.

    PowerExchange Change Capture ComponentsPowerExchange Microsoft SQL Server Capture sources data from Microsoft SQL Server publication technology.

    Figure 1-1 depicts the PowerExchange Change Capture architecture for a Microsoft SQL Server Capture source that can be applied to a target database using either the PowerCenter Apply feature or a partner product:

    Figure 1-1. PowerExchange Change Capture Architecture for a Local Microsoft SQL Server Target

    PowerExchange Listener

    CONDENSEDCHANGES

    LISTENERCAPX PowerCenter

    PowerExchangeCCT

    CaptureRegistrations

    PowerExchangeChange

    UOWCLEANSER

    CONDENSERTASK

    PowerExchange Real-timeAdapters

    AdabasDatacom

    DB2 for z/OSDB2 for i5/OSDB2 for LUW

    IDMSIMS

    OracleSQL Server

    VSAM

    PowerExchange ChangeAdapters

    AdabasDatacom

    DB2 for z/OSDB2 for i5/OS

    IDMSIMS

    VSAM

    EXTRACTIONMAPS

    CAPTUREREGISTRATIONS

    PowerExchange Navigator

    PowerCenterUOW

    CLEANSER

    LISTENERCAPXRT

    TCP/IP or MQ

    Push or Pull

    PowerExchangeReal-time

    PowerExchangeApply

    Third PartyChange Data

    Consumer

    WINDOWS

    User Application

    1

    SQL ServerReplication

    4

    PowerExchange

    5

    PowerExchange REGISTRATIONDEFINITIONS

    B

    PowerExchange NAVIGATOR

    A

    SQL ServerLog

    3

    SQL ServerDatabase

    2

    Key

    CONTROL FLOWCOMPONENT

    DATA FLOWCOMPONENT

    2 Chapter 1: Overview

  • The components that control the flow of data appear as elliptical shapes with alphabetic labels. These components handle the changed data as it progresses through the propagation process. Some of these components, such as the user application and the source and target databases, are not PowerExchange Change Capture components.

    Table 1-1 describes the data flow components:

    To create a data capture environment, complete the following steps:

    1. Configure DBMOVER.cfg parameters.

    2. Configure Microsoft Replication.

    3. Register a data source.

    4. Complete Microsoft SQL Server prerequisites.

    5. Materialize tables using the Bulk Move facility.

    6. Register a restart token.

    7. Access the data.

    For more information, see the PowerExchange Reference Manual.

    Software RequirementsSoftware requirements for PowerExchange Change Capture and Microsoft SQL Server Capture are Microsoft SQL Server 2000 or greater in the following versions:

    ♦ Enterprise Edition

    ♦ Standard Edition

    ♦ Development Edition

    Change capture is not compatible with Personal Edition.

    Table 1-1. Change Propagation Components

    Component Description

    User Application Any software that updates the source database on an ongoing basis.

    SQL Database The Microsoft SQL Server database where the source data resides. PowerExchange Change Capture can capture changes from more than one source database or data file. Microsoft SQL Server data is captured by utilizing existing Microsoft Publication technology.

    SQL Server Log Microsoft SQL Server uses the logs to source the replication transactions.

    Replication PowerExchange works with Microsoft publication technology to make changes available for extract.

    PowerExchange PowerExchange can direct data returned to a number of targets. These may involve passing data to a partner tool to apply the changes to the target, or to use PowerCenter software to apply the data changes directly to the target.

    PowerExchange Navigator PowerExchange Navigator is used to specify the PowerExchange registration, locations, users, and user groups.

    PowerExchange Registration Definitions

    The central repository holds information on all the data sources and locations. The repository can be created on whatever platform is deemed preferable.

    Software Requirements 3

  • 4 Chapter 1: Overview

  • C H A P T E R 2

    Bulk Movement of Data

    This chapter includes the following topics:

    ♦ Accessing Microsoft SQL Server, 5

    ♦ Testing a Remote PowerExchange Listener, 5

    ♦ Sourcing Microsoft SQL Server Data, 5

    Accessing Microsoft SQL ServerBefore you access Microsoft SQL Server, complete the PowerExchange pre-installation checklist.

    ♦ The name of the distribution server either already in existence or created for PowerExchange capture.

    ♦ The name of the distribution database either already in existence or created for PowerExchange capture.

    ♦ The tables to be sourced and whether they are grouped under a particular owner.

    ♦ The user name and password to access these tables.

    Testing a Remote PowerExchange ListenerTo use a remote PowerExchange Listener, it must first be started. To determine if it is started and to check your connectivity, enter the following command at a command prompt:

    dtlrexe loc= prog=ping

    In this command, is the Node name in the dbmover.cfg file that points to the remote platform.

    Sourcing Microsoft SQL Server DataThis document covers the following topics, allowing you to capture data, then access that data with PowerExchange tools. The captured data is also available for use by other products, such as ETL tools.

    To source Microsoft SQL Server data:

    ♦ Obtain the valid user ID and password for the source database.

    5

  • ♦ Obtain any database specific information, such as Microsoft SQL Server database and server names.

    ♦ Ping the IP address of the source machine to check it is visible.

    ♦ Add a node name for the location in the dbmover.cfg file.

    ♦ Use the command “dtlrexe loc= prog=ping uid= pwd=” to test that the remote PowerExchange Listener is started, where is the Node name from the dbmover.cfg file.

    ♦ Create the Microsoft SQL Server replication environment if not already used.

    ♦ Use PowerExchange Navigator to create a Personal Metadata Profile for the Microsoft SQL Server source database and view some real data, having checked that the metadata is returned successfully. For more information, see the PowerExchange Navigator User Guide.

    ♦ Use PowerCenter or similar software product to execute the request to move data.

    6 Chapter 2: Bulk Movement of Data

  • C H A P T E R 3

    Personal Metadata

    This chapter includes the following topic:

    ♦ Using Personal Metadata, 7

    Using Personal MetadataYou can view Microsoft SQL Server tables and data from the PowerExchange Navigator.

    To view Personal Metadata, make sure the PowerExchange Navigator can see the data server by adding a new entry to the dbmover.cfg file. By default, the first lines of the file appears as follows:

    LISTENER=(node1,TCPIP,2480)NODE=(local,TCPIP,127.0.0.1,2480)NODE=(node1,TCPIP,127.0.0.1,2480)NODE=(default,TCPIP,x,2480)

    If Microsoft SQL Server resides on a machine remote from the PowerExchange Navigator, add a line that specifies the IP address and the PowerExchange Listener started on that machine.

    To create Personal Metadata to view Microsoft SQL Server data:

    1. In the PowerExchange Navigator Resource Explorer, right-click Personal Metadata and click Add Personal Metadata, or click the Add Personal Metadata icon. The Personal Metadata - Name dialog box appears.

    2. Enter the following information:

    Field Description

    Name Name for the Personal Metadata.

    Location Location of Microsoft SQL Server data. This location must also be specified in the dbmover.cfg configuration file.

    Type Type of data. Select MSSQL.

    UserID UserID may not be required. The security requirements are dependant upon the settings of the SECURITY dbmover parameter. For more information about the SECURITY parameter, see the PowerExchange Reference Manual.

    Password Password may not be required. The security requirements are dependant upon the settings of the SECURITY dbmover parameter. If the password is left blank but is required then a pop-up password box will appear enabling the password to be given. Leaving the password blank prevents the password being stored by PowerExchange and potentially causing password violations if the Personal Metadata is read after the password for the user has changed.The SECURITY parameter is documented in the PowerExchange Reference Manual.

    7

  • 3. Click Next.

    4. To reduce the number of tables returned, enter the Owner or Table name. Qualify the selection if required, and click Finish.

    If you leave Owner and Table blank, the Navigator returns all tables in the database.

    The number of tables returned for selection can be narrowed down. If both the Owner and Table are left blank then all tables within the database are returned. Qualify the selection if required and click Finish.

    The Navigator displays all tables meeting the filter requirements.

    5. Click the table you want to use.

    The columns and column attributes appear.

    6. Click the Row Test icon .

    7. Review the database information. By default, the row test returns 10 rows. Optionally, change the number of rows returned by the row test, and then click Go.

    The Navigator returns the specified number of rows from the table.

    DSN Data Source Name. The name of the Microsoft SQL Server.

    Database Name of the Microsoft SQL Server database. This field is required.

    Description An optional description of the metadata.

    Field Description

    8 Chapter 3: Personal Metadata

  • C H A P T E R 4

    Configuring SQL Server Change Data Capture

    This chapter includes the following topics:

    ♦ Configuring SQL Server for Change Data Capture, 9

    ♦ Configuring PowerExchange for Change Data Capture, 10

    ♦ Implementing SQL Server Change Data Capture, 16

    ♦ Managing Capture Registrations, 17

    ♦ Extraction Maps, 20

    ♦ Application Group, 24

    ♦ Migrating to Condense File Extraction Modes, 26

    Configuring SQL Server for Change Data Capture

    Microsoft SQL Server Prerequisites♦ If the PowerExchange Navigator does not reside on the same box as the Microsoft SQL Server software, then

    Microsoft SQL Server client software must be installed on the Navigator machine.

    ♦ Microsoft SQL Server must be Microsoft SQL Server 2000 or greater.

    ♦ Microsoft SQL Server Replication must be enabled using the Microsoft SQL Server Publication technology.

    Required AuthorityIn the absence of a user name and password both the PowerExchange Navigator and capture extract uses Windows authorization to connect to Microsoft SQL Server. Registering items for capture requires system administrator or db_owner authority. For data extract tasks the user must have read access to the distribution database.

    You require read access to the distribution database for data extraction tasks.

    Microsoft SQL Server PublicationsPowerExchange requires that Microsoft SQL Server distribution is enabled on the server from which data is to be captured. To enable distribution through the Microsoft SQL Server Management console, click Tools > Replication > Configure Publishing, Subscribers, and Distribution:

    9

  • Alternatively, use the following Microsoft SQL Server supplied stored procedures:

    ♦ sp_adddistributor

    ♦ sp_adddistributiondb

    ♦ sp_adddistpublisher

    For more information about Microsoft SQL Server Replication technology, see the Microsoft MSDN library on the Microsoft web site.

    To capture a large number of transaction updates, use a distributed server as the host of the distribution database. Using a dedicated distribution server can avoid competition for CPU and disk storage with a production instance.

    The default retention period for transactions at the distributor is 72 hours. Informatica recommends that this is increased to 14 days, although the need for resilience will need to be balanced against practical space issues when there is a very high frequency of change.

    RestrictionsThe following restrictions apply to SQL Server capture:

    ♦ Capture tables must have a Primary Key.

    ♦ System tables can not be captured.

    ♦ Long columns are not captured in before images.

    ♦ User ID is not captured.

    ♦ Timestamp is that of capture, and not of the original transaction.

    ♦ Tables that include column types of sql_variant cannot be registered for capture.

    Configuring PowerExchange for Change Data CapturePowerExchange uses the Microsoft SQL Server distribution database to extract captured changes and provides the following extraction options:

    ♦ Real-time extraction mode. When you use real-time extraction mode, PowerExchange reads the changes from the distribution database and continues reading change data until you stop the extraction.

    Real-time extraction provides the lowest latency for change data extraction.

    ♦ Batch extraction mode from condense files. When you use batch extraction mode from condense files, PowerExchange reads the changes from condense files created by PowerExchange Condense. PowerExchange reads only the closed condense files that existed when the extraction starts and ends the extraction when these condense files have been processed.

    Batch extraction mode from condense files provides the highest latency for change data extraction.

    ♦ Continuous extraction mode from condense files. When you use continuous extraction mode from condense files, PowerExchange reads the changes from condense files created by PowerExchange Condense. PowerExchange reads data from condense files as it is being written by the condense task, even if the condense file is not yet closed. PowerExchange continues reading changes from condense files until you stop the extraction.

    Using continuous extraction mode from condense files provides near real-time access to change data.

    For more information, see “PowerExchange Condense” on page 29.

    You can configure PowerExchange for all three extraction modes providing flexibility when choosing an extraction mode for a specific application or set of tables.

    10 Chapter 4: Configuring SQL Server Change Data Capture

  • Configuring the DBMOVER Configuration FilePowerExchange uses the specifications provided in the DBMOVER configuration file, dbmover.cfg, to configure the operation of various PowerExchange tasks as well as their communication with other PowerExchange tasks. For a complete list of all DBMOVER configuration file parameters, see the PowerExchange Reference Manual.

    PowerExchange CDC and the PowerExchange Listener use parameters specified in the dbmover.cfg configuration file to:

    ♦ Connect to Microsoft SQL Server databases and tables.

    ♦ Determine the directories in which to store capture registrations, extraction maps, capture files, and condense files.

    ♦ Get connection information in order to extract changes from SQL Server distribution databases and from condense files.

    PowerExchange Condense has an additional configuration file, dtlca.cfg. For more information, see “Configuring PowerExchange Condense Parameters” on page 32.

    To use change data capture, configure the following DBMOVER configuration parameters:

    CAPT_PATH and CAPT_XTRA StatementsBy default, PowerExchange creates all capture files, registrations, and extraction maps in the PowerExchange install directory. Use the following parameters in the PowerExchange DBMOVER configuration file to specify different directories:

    Parameter Required Description

    CAPT_PATH No PowerExchange stores registrations, capture files such as the CCT and CDCT, condense files, and Condense task checkpoint files in the specified directory. Default is the PowerExchange install directory. See “CAPT_PATH and CAPT_XTRA Statements” on page 11.

    CAPT_XRTA No PowerExchange stores capture extraction maps in the specified directory. Default is the PowerExchange install directory. See “CAPT_PATH and CAPT_XTRA Statements” on page 11.

    CAPI_SRC_DFLT Yes Specifies the default CAPI_CONNECTION PowerExchange uses when none is supplied. Using CAPI_SRC_DFLT, you can specify default CAPI_CONNECTION statements for different source types in a single configuration file.See “CAPI_SRC_DFLT Statement” on page 12.

    CAPI_CONNECTION Yes PowerExchange requires CAPI_CONNECTION statements for real-time extraction mode, continuous extraction mode from condense files, and the Condense task.See “Required CAPI_CONNECTION Statements” on page 12 and “CAPI_CONNECTION Statement for Continuous Extraction Mode” on page 13.

    Parameter Description

    CAPT_PATH PowerExchange stores registrations, capture files such as the CCT and CDCT, condense files, and Condense task checkpoint files in the specified directory. Create this directory, if it does not exist, prior to using CDC. Default is the PowerExchange install directory.

    CAPT_XTRA PowerExchange stores capture extraction maps in the specified directory. Create this directory, if it does not exist, prior to using CDC.Default is the PowerExchange install directory.

    Configuring PowerExchange for Change Data Capture 11

  • Specify these parameters with unique directories to separate CDC objects and files from the PowerExchange code. Separating these data objects and files from the PowerExchange code can ease the software migration process since data objects and files are not inter-mingled with the PowerExchange code.

    CAPI_SRC_DFLT StatementYou can code multiple CAPI connection statements in a single DBMOVER configuration file. Use the CAPI_SRC_DFLT to specify the default CAPI_CONNECTION statement for a specific source type. PowerExchange uses the CAPI_SRC_DFLT statement for a specific source type when no CAPI_CONNECTION override is supplied. The following example shows CAPI_SRC_DFLT statements for multiple source types in a single DBMOVER configuration file:

    CAPI_SRC_DFLT=(MSQL,sql_name)CAPI_SRC_DFLT=(UDB,db2_name)CAPI_SRC_DFLT=(ORA,uowc_name)

    To use continuous extraction mode for condense files, the extraction must use a CAPX CAPI_CONNECTION statement. If the CAPI_SRC_DFLT statement points to a source CAPI_CONNECTION, specify the CAPI connection override for the extraction.

    PowerExchange Condense uses source CAPI_CONNECTION statements. If the CAPI_SRC_DFLT statement points to a CAPX CAPI_CONNECTION, specify the appropriate source CAPI_CONNECTION name in the CONN_OVR parameter in the PowerExchange Condense configuration file.

    Required CAPI_CONNECTION StatementsPowerExchange uses CAPI connection statements to configure CDC processing. SQL Server CDC requires the following CAPI_CONNECTION statements:

    ♦ MSQL CAPI_CONNECTION for real-time extraction mode and for PowerExchange Condense

    Add the MSQL CAPI_CONNECTION statement to the PowerExchange DBMOVER configuration file, dbmover.cfg, on the machine running SQL Server CDC. For example:

    CAPI_CONNECTION=(NAME=sql_name,TYPE=(MSQL,DISTDB=distdb,DISTSRV=distsrv))

    Note: PowerExchange does not require CAPI_CONNECTION statements on the PowerExchange Navigator machine. You can register tables for CDC and perform database row test functions in Navigator using the remote PowerExchange Listener running on the machine capturing the changes.

    MSQL CAPI_CONNECTION ParametersUse the MSQL CAPI_CONNECTION statement to specify parameters for Microsoft SQL Server CDC.

    The MSQL statement has the following syntax:

    CAPI_CONNECTION=( NAME=name, [DLLTRACE=trace_id], [TRACE=trace], TYPE=(MSQL, DISTDB=distribution_db, DISTSRV=distrib_srv, [DWFLAGS=(flag1,flag2,flag3)], [EOF=Y|N], [MEMCACHE=cache_value], [POLWAIT=ssss], [RSTRADV=sssss] ))

    Parameter Required Default Description

    DISTDB Yes none The name of the distribution database.

    DISTSRV Yes none The network name of the distribution server.

    12 Chapter 4: Configuring SQL Server Change Data Capture

  • CAPI_CONNECTION Statement for Continuous Extraction ModeFor continuous extraction mode from condense files, configure CAPX CAPI_CONNECTION statements. For example:

    DLLTRACE No none Specifies the name of the TRACE= statement that activates internal DLL tracing for this specific CAPI. Only specify this parameter when instructed to do so by Informatica Global Customer Support.

    DWFLAGS No none A series of three positional flags with values of Y or N:Flag1 - Warn on data truncation. Y Forces processing to continue if data of an unexpected length is received. The default is N and to stop processing. Flag2 - Warn on schema change. Y Forces processing to continue if schema changes are detected. The default is N and to stop processing. Flag3 - Warn on change data lost. Y Forces processing to continue if the requested start sequence is not found in the transaction log. The default is N and to stop processing. Only use this parameter when instructed to do so by Informatica Global Customer Support.

    EOF No N Specifies whether PowerExchange ends extractions when end-of-log is reached (EOF=Y) or not (EOF=N). Since this parameter affects all users of the CAPI_CONNECTION, use one of the following methods instead:Specify Idle Time=0 on the PWXPC Real Time application connection. - Specify WAITTIME=0 in the ODBC data source.- Valid values are Y or N.

    MEMCACHE No 248K Number of Kilobytes to allocate for caching a single row update. Valid values are 1 to 519720.

    NAME Yes none Specifies a unique name for the CAPI_CONNECTION statement.Maximum is 8 characters.

    POLWAIT No 10 Number of seconds to wait between polling for new data after end of current data has been achieved. Valid values are 1 to 2147483647.

    RSTRADV No none Specifies the number of seconds PowerExchanger waits before advancing the restart tokens by returning an empty Unit of Work (UOW). Empty UOWs contain no data, only restart tokens. The RSTRADV wait period for a source starts after a UOW for that source is processed and is reset when the next UOW is received or when an empty UOW is returned because the wait period expires, whichever comes first.If RSTRADV is not specified, then PowerExchange does not return empty units of work to help advance the restart point. For example, if you set RSTRADV=5 and a source in the extraction has not had any changes for ten seconds, an empty UOW will be returned for that source after five seconds. This advances the restart point of that source. Warning: Specifying RSTRADV=0 adversely affects performance. With RSTRADV=0, PowerExchange returns empty UOWs after every UOW processed.Valid values are any number of seconds between 0 and 86400.

    TRACE No none Specifies the name of the TRACE= statement that activates the common CAPI tracing. Only specify this parameter when instructed to do so by Informatica Global Customer Support.

    TYPE Yes none Specify MSQL.

    Parameter Required Default Description

    Configuring PowerExchange for Change Data Capture 13

  • CAPI_CONNECTION=(NAME=capx_name,TYPE=(CAPX,DFLTINST=collection_id))

    Collection_id must match the instance or database name in the PowerExchange Navigator registration group containing the capture registrations.

    When using continuous extraction mode for condense files, configure the CAPI_SRC_DFLT statement to point to the MSQL CAPI_CONNECTION statement. PowerExchange Condense does not allow CAPI_CONNECTION overrides so the MSQL CAPI connection statement must be the default CAPI connection statement.

    Note: PowerExchange does not require CAPI_CONNECTION statements on the PowerExchange Navigator machine. You can register tables for CDC and perform database row test functions in Navigator using the remote PowerExchange Listener running on the machine capturing the changes.

    CAPX CAPI_CONNECTION ParametersThe CAPX CAPI_CONNECTION statement specifies the parameters used for continuous extraction from condense files. Using continuous extraction mode from condense files, extractions run near real-time using condense files as the change stream.

    You can use continuous extraction mode from condense files with DB2 for Linux, UNIX, and Windows CDC, Oracle CDC, and SQL Server CDC.

    The CAPX statement has the following syntax:

    CAPI_CONNECTION=( NAME=name, [DLLTRACE=trace_id], [TRACE=trace], TYPE=(CAPX, DFLTINST=collection_id, [FILEWAIT=nnnnn], [RSTRADV=sssss] ))

    Parameter Required Default Description

    DFLTINST Yes none Specifies the PowerExchange instance to process. For DB2 for Linux, UNIX, and Windows, specify the database from the registration group.For Oracle, specify the collection identifier from the ORACLEID statement or the instance from the registration group. For Microsoft SQL Server, specify the instance from the registration group.

    DLLTRACE No none Specifies the name of the TRACE= statement that activates internal DLL tracing for this specific CAPI. Only specify this parameter when instructed to do so by Informatica Global Customer Support.

    FILEWAIT No 1 Specifies the number of seconds to wait before checking for new condense files.Minimum is 1. Maximum is 86400.

    NAME Yes none Specifies a unique name for the CAPI_CONNECTION statement.Minimum is 1 character. Maximum is 8 characters.

    14 Chapter 4: Configuring SQL Server Change Data Capture

  • Configuring Real-time Extraction ModeComplete the following steps to configure PowerExchange real-time extraction mode:

    1. Configure SQL Server. See “Configuring SQL Server for Change Data Capture” on page 9.

    2. Configure PowerExchange for CDC. For more information about the statements that you need to define, see the following topics:

    ♦ “CAPT_PATH and CAPT_XTRA Statements” on page 11

    ♦ “CAPI_SRC_DFLT Statement” on page 12

    ♦ “Required CAPI_CONNECTION Statements” on page 12

    3. Register tables for SQL Server CDC. For more information, see “Managing Capture Registrations” on page 17.

    4. Test the configuration.

    5. Configure the PowerCenter extraction by creating mappings and workflows. For more information, see PowerExchange Interfaces for PowerCenter.

    6. Establish a starting point in the change stream for the extraction. See “Creating Restart Points with DTLUAPPL” on page 81.

    Configuring Batch Extraction ModeComplete the following steps to configure PowerExchange batch extraction mode for condense files:

    1. Configure SQL Server. See “Configuring SQL Server for Change Data Capture” on page 9.

    2. Configure PowerExchange for CDC. For more information about the statements that you need to define, see the following topics:

    ♦ “CAPT_PATH and CAPT_XTRA Statements” on page 11

    ♦ “CAPI_SRC_DFLT Statement” on page 12

    ♦ “Required CAPI_CONNECTION Statements” on page 12

    ♦ “Configuring the PowerExchange Condense Process” on page 30

    3. Register tables for SQL Server CDC selecting Part in the Condense option. Delete and recreate any existing capture registrations. For more information, see “Managing Capture Registrations” on page 17.

    RSTRADV No none Specifies the number of seconds to wait after receiving a Unit of Work (UOW) for a source in the extraction before advancing the restart tokens by returning an “empty” UOW.Use this parameter to reduce the amount of data which is reprocessed when restarting the extraction.Default is to advance the restart tokens for a source in the extraction when a UOW for that source is read.Minimum is 0. Maximum is 86400.RSTRADV=0 returns empty UOWs regardless of whether the overall restart point has changed. It advances the restart point for every UOW encountered, regardless of whether the overall restart point for the extraction is advanced. Warning: Specifying RSTRADV=0 adversely affects performance.

    TRACE No none Specifies the name of the TRACE= statement that activates the common CAPI tracing. Only specify this parameter when instructed to do so by Informatica Global Customer Support.

    TYPE Yes none Specify CAPX.

    Parameter Required Default Description

    Configuring PowerExchange for Change Data Capture 15

  • 4. Start PowerExchange Condense. For more information, see “Starting and Stopping PowerExchange Condense” on page 35

    5. Test the configuration.

    6. If migrating from real-time extraction mode, see “Migrating to Condense File Extraction Modes” on page 26.

    7. Configure the PowerCenter extraction by creating mappings and workflows. For more information, see PowerExchange Interfaces for PowerCenter.

    8. Establish a starting point in the change stream for the extraction. For more information, see “Creating Restart Points with DTLUAPPL” on page 81

    Configuring Continuous Extraction ModeComplete the following steps to configure PowerExchange continuous extraction mode:

    1. Configure SQL Server. For more information, see “Configuring SQL Server for Change Data Capture” on page 9.

    2. Configure PowerExchange for CDC. For more information about the statements that you need to define, see the following topics:

    ♦ “CAPT_PATH and CAPT_XTRA Statements” on page 11

    ♦ “CAPI_SRC_DFLT Statement” on page 12

    ♦ “Required CAPI_CONNECTION Statements” on page 12

    ♦ “CAPI_CONNECTION Statement for Continuous Extraction Mode” on page 13

    ♦ “Configuring the PowerExchange Condense Process” on page 30

    3. Register tables for SQL Server CDC selecting Part in the Condense option. Delete and recreate any existing capture registrations. For more information, see “Managing Capture Registrations” on page 17.

    4. Start PowerExchange Condense. For more information, see “Starting and Stopping PowerExchange Condense” on page 35

    5. Test the configuration.

    6. If migrating from real-time extraction mode, see “Migrating to Condense File Extraction Modes” on page 26.

    7. Configure the PowerCenter extraction by creating mappings and workflows. For more information, see PowerExchange Interfaces for PowerCenter.

    8. Establish a starting point in the change stream for the extraction. For more information, see “Creating Restart Points with DTLUAPPL” on page 81

    Implementing SQL Server Change Data Capture Use the following procedure to implement SQL Server change data capture:

    1. Amend the dbmover.cfg file on the registration machine. For more information, see “Configuring PowerExchange for Change Data Capture” on page 10.

    2. Configure Microsoft SQL Server Replication. For more information, see “Configuring SQL Server for Change Data Capture” on page 9.

    3. Make sure the Microsoft SQL Server Agent service is running.

    4. Register the source using the PowerExchange Navigator. For more information, see “Managing Capture Registrations” on page 17.

    16 Chapter 4: Configuring SQL Server Change Data Capture

  • 5. Establish a capture start point. For more information, see “Creating Restart Points with DTLUAPPL” on page 45.

    6. Set the PowerExchange capture registration to Active.

    Managing Capture RegistrationsTo enable PowerExchange to select the correct changes, you must specify the tables for which the capture collects changes. The registration process consists of a number of tasks, some using the PowerExchange Navigator and others using standard Microsoft SQL Server utilities or Stored Procedures.

    Creating a Registration GroupThe registration of the source table is performed using the PowerExchange Navigator. The capture registrations are defined under the Registration Group under Resources on the Resource Explorer panel. A Registration Group is a user-defined group of individual capture registrations.

    To add a registration group:

    1. Use the toolbar Add Registration Group icon or right-click Registration Group and choose Add Registration Group. The Add Registration Group dialog box appears.

    2. Enter the following information:

    3. Click Next.

    4. Enter the following information in the Add Capture Registration - Name and Table Filter dialog box.

    Use the Table Filter fields to reduce the number of tables returned. If you do not use a table filter, all tables available within the selected database are returned. Qualify the selection if required.

    Field Description

    Name The name of the Registration Group. A Registration Group can have multiple capture registrations.

    Location The location of the Microsoft SQL Server Distribution server. Pick a location already defined within the Navigator.

    Type Select MSSQL.

    UserID/Password The user name and password to be used when accessing the Location and the Instance. The Microsoft SQL Server user name must have access to the Microsoft SQL Server location through the Navigator. If the password is left blank the Navigator prompts for the password to be entered as required.

    Registration Server Database Server

    The name of the server in which the database from which changes will be captured resides. Select from the list.

    Registration Server Database Name

    The name of the database for which changes are captured. Select from the list.

    Field Description

    Name Name of this registration within the Registration Group. This is limited to 8 alphanumeric characters.

    Table Filter The filter criteria will minimize the actual selection list retrieved from the specified Location and Instance.

    Owner Filter on the table owner, table name or no filter. Filter where possible where the database is known to include many tables otherwise a large amount of information will be returned.

    Managing Capture Registrations 17

  • 5. Click Next. A list of source tables matching the filter conditions appears.

    6. Double-click the table you want to register for data capture.

    There can only be one capture registration for a given source.

    The columns in the selected table appear. Columns with a key icon are the index columns for that table. To be eligible for data capture, tables must have a primary key.

    7. Check Select Column for each column you want to include for capture.

    When selecting columns for capture, be sure to include all columns you might want to use. An extraction process can select a subset of the captured columns, but it cannot select data that has not been captured.

    Note: Changes to the table structure after registering the columns require updating the capture registration through versioning. For more information, see “Version Indicator in Extraction Definitions” on page 42.

    The following table describes the Tables fields that appear in this dialog box:

    The following table describes the Columns fields:

    8. Click Next. A capture registration can only contain one table.

    In the Add Capture Registration - Type dialog box, define the type and characteristics of the capture registration.

    9. Enter the following information to define the capture registration:

    10. Click Finish. In this example, the registration has been added as Inactive.

    If the registration had been created as active, data would be captured from that point onwards.

    Table The required table if known.

    Escape Character

    The escape character that can be used in table names.

    Tables Field Description

    Creator Name Table creator

    Name Table name

    Type Database object type

    Columns Field Description

    Select Columns Indicates whether a column is selected for capture.

    NameTC1 Column name

    Field Description

    Condense Specifies the type of condense processing to do for the capture registration:- None. Indicates that no condense processing is done. - Part. Indicates that condense processing is done and keeps all committed changes for

    each source row.

    Status Status of the capture registration. This can have one of two values:- Inactive. The registration is to be defined but is not to be used by the Collection Agent.

    This may be done so that a registration is prepared ready for starting capture before the target is materialised (initial data load), and ready to switch to active at the appropriate time.

    - Active. The registration is effective immediately.

    Field Description

    18 Chapter 4: Configuring SQL Server Change Data Capture

  • For a more controlled method, create the registration as inactive, perform an initial load of target tables, then change the registration to active at the appropriate time.

    Each creation of a Registration Group automatically creates a matching extraction group and Application Group with the same name.

    When defining an actual capture registration for a source the system automatically defines an extraction process for that registration. These default extract definitions can be modified by the user.

    Once a table is registered and the status of the registration is set to Active, the registration cannot be changed. This is to ensure that the data already collected is not invalidated. To change an existing registration, a new version for the table has to be created and activated. Changes required as a result of changes to the source table are handled by versioning of the registrations. For more information, see “Version Indicator in Extraction Definitions” on page 42.

    To change the capture registration status:

    1. In the Navigator, select the capture registration.

    2. In the Resource Inspector, change the Status as necessary. A small red square appears next to Status.

    3. To accept the change, click Apply. The Status changes. The red square clears and an icon next to the registration turns red.

    4. When exiting the registration, a prompt appears to save your changes. Click Yes.

    The Registration saved to the Capture Registration Repository file on the source platform.

    5. After the registration is created, you can view it in the Microsoft SQL Server Enterprise Manager.

    Adding a Capture Registration to an Existing GroupTo add a capture registration to an existing group:

    1. Right click the required Registration Group and click Open.

    2. Use the toolbar Add Capture Registration icon. The Add Capture Registration - Name and Table Filter panel appears.

    3. Follow Steps 2 to 4 in “Managing Capture Registrations” on page 17.

    Deleting a Registration GroupDeleting a Registration Group does not delete any Registration Entries. Only group information held locally on the workstation is deleted. You can delete a registration group if there are no active registrations outstanding for the group.

    To delete a registration group:

    1. Select the appropriate Registration Group.

    2. Click Delete and click Yes to confirm deletion.

    3. Click Yes.

    Deleting a Registration EntryTo delete a registration entry, select the registration entry and click Delete. If the registration is not active you will be asked to confirm the deletion, otherwise you will be prompted to make the registration history before deleting. This will delete the registration entry on the source platform. Data will no longer be picked up by the extraction process.

    Managing Capture Registrations 19

  • Viewing a Registration GroupSelect a group in the Resource Explorer. This displays group details in the Resource Inspector. A complete list of registrations displays under the Registration Group in the Resource Explorer.

    Viewing a Capture RegistrationTo view capture registration details:

    1. Double-click a Capture Definition Group from the Resource Explorer Resource tab.

    2. Select a capture registration from the group list and then double-click on the Registration Name that you want to view. The following information displays:

    Extraction MapsAn extraction process is a process of extracting changes from PowerExchange Change Capture. Captured data can be extracted directly from the log using the CAPXRT access. As part of the capture registration process, an extraction group with the same name is automatically defined. You can modify these default definitions.

    Note: A separate Application is created for each extraction. If you use multiple extractions in a single Application, run only one extraction at a time. If you need additional extraction processes, use the Add Extract Definition wizard to define them. When extracting changes for a source the user (PowerCenter or third-party software) specifies a standard SQL request in the format:

    Select * from DataMap.Name

    This is the same as any other SQL request given to the PowerExchange API. When using the default data map that is being created as part of the capture registration process the request would have the following format:

    Area Description

    Resource Explorer Displays a list of capture registration groups and the capture registrations within each group. To select and open a capture registration double click on the capture registration name. All the registration details are displayed in the Capture Registration details panels.

    Capture Registration Details

    Displays the column information of the table referenced by the capture registration. This only displays details for those columns that are selected for capture. This includes:- Name- Table Name- Column No - Type- Length- Scale- KeyTo make changes to an existing list of columns (for a given source) right-click on the registration name.

    Resource Inspector Displays the registration properties of the capture registration. For example, Type will be Synchronous and the Tag contents will be used when writing changes to the PowerExchange Logger. If you make any changes they must be confirmed by clicking on the Apply button. Once confirmed, the Registration in the Explorer changes color. This is an indication that the source requires to be saved.

    20 Chapter 4: Configuring SQL Server Change Data Capture

  • Select * from Dxcollectionid.creator_tablename

    Define the Extraction ProcessThe extractions are defined under the extraction group under Resources in the Resource Explorer. By default, when a Registration Group is defined an extraction group with the same name is automatically created. There is normally no need to define extraction groups manually.

    To add an extraction group:

    1. In the Resource Explorer, right-click Extraction Group and click Add Extraction Group. Or use the Add Extraction Group icon.

    2. Enter the following information:

    3. Click Finish.

    To add an extraction definition to an extraction group:

    1. In the Resource Explorer, right-click the new extraction group and select Open.

    2. Right-click the extraction group name and click Add Extraction Definition.

    3. Enter the following information.

    Variable Description

    D Default entry, all user-defined data maps will start with U.

    x 10 for Microsoft SQL Server.

    collectionid Collection ID specified when creating the registration group.

    Field Description

    Name The name of the extraction group.

    Location Specifies the name as defined in the dbmover.cfg file where the PowerExchange Listener is located.

    Type The type of data to be extracted.

    UserID/Password User name and password to identify the user and check their authorizations.

    Registration Server Database Server

    Select the Microsoft SQL Server database server.

    Registration Server Database Name

    Select the required Microsoft SQL Server database for capture.

    Field Description

    Schema Name Name of the schema based on the following naming convention: U__- U. User Defined.- DB_Type. Database type. Use 10 for Microsoft SQL Server.- DB_Instance. Database instance, for example, docd000.The schema name is unique within a specific PowerExchange Listener, database instance, and database type.

    Map Name A name given to that specific extraction definition. The default map name contains the registration name. You can create a map name up to 8 characters long.

    Table Name A name given to the table part of the data map name. The default name contains the actual table name. You can create a table name up to 20 characters long.

    Extraction Maps 21

  • The constructed data map name has the format: U10.. Add Extraction Definitions - Capture Registrations.

    You can add a version of a capture registration to the extraction process definition using the Add Extract Definitions - Capture Registrations dialog box.

    The Available Capture Registrations list displays the capture registrations that are available for selection. The Current Capture Registrations list displays the name of the capture registrations that have been selected for the extraction definition.

    In this dialog box, you can manage the versions of registrations associated with the extraction process. For example, you could remove a version 1 registration and then add the next version.

    Data Delivery FormatPowerExchange captures data and saves it as Before and After Images in the PowerExchange Logger.

    The way this captured data is delivered is based on the Image Type defined in:

    ♦ CAPXImageType through ODBC

    ♦ SQL Escape Sequence DTLIMTYPE

    The following table describes how captured update data can be delivered:

    Note: Inserts and deletes are delivered without before images.

    Table 4-1. Available Capture Registrations Fields

    Field Description

    Name Displays the name of the capture registrations that are available for selection.

    Version Displays the version number of the capture registration.

    Condense Displays the condense state of the capture registration.

    Status Displays the status of the capture registration. This can have one of two values:- I. Inactive. The registration is to be defined but not used by the Collection Agent.- A. Active. The registration is to be defined and used by the Collection Agent.

    Table 4-2. Current Capture Registration Fields

    Field Description

    Name The name of the capture registration that has been selected.

    Version The version number of the capture registration.

    Condense The condense state of the capture registration.

    Status The status of the capture registration.

    Image Type Description

    BA Delivers the Before Image (before the latest change) and the After Image (the latest change). The Before Image is shipped with an action character forcing the deletion of the record. The After Image (which includes the changes) is in the format of an Insert.

    AI Delivers only the After Image data for the update.

    TU Delivers the data before and after images as they occur. The Before Image is shipped to enable the application to ensure nothing has changed in that record since the request. The After Image comes through as a change (or Update) record.The update is still a full image but the application picking this up will be able to change the target record rather than Delete it and Insert the new one as when using BA.

    22 Chapter 4: Configuring SQL Server Change Data Capture

  • Specify Extraction CriteriaThere are a variety of values that can be specified when running an extraction process. When using the ODBC interface to PowerExchange, you define them as part of the ODBC definition. ODBC allows various overrides using escape sequences:

    ♦ DTLXTYPE=

    ♦ DTLAPP=

    ♦ DTLDSN=

    Note: The overrides below are fully detailed in the PowerExchange Reference Manual.

    Deleting an Extraction Group or DefinitionTo delete an extraction group:

    1. Select the appropriate extraction group.

    2. Click Delete, and click Yes to confirm the deletion.

    Deleting the extraction group does not delete any extraction definitions. It only removes the group-related information.

    To delete an extraction definition:

    Select the Extract Definition and then press the Delete button.

    This deletes the Extract Definition entry. Once the entry is deleted it is not possible to extract any more changes using that extraction definition. Care has to be taken to ensure that the back end application is changed in correspondence. This will invalidate the source definition in, for example, the ETL tools.

    Viewing an Extraction Definition

    To view the extraction definition details:

    1. On the Extraction Group tab of the Resource Explorer, double-click the extraction group that contains the extraction definition.

    2. Select an Extract Definition from the group contents and double-click the Registration Name.

    − Resource Explorer. Displays a list of extraction groups and the extraction definitions within each group. To select and open an extraction definition, double-click on the extraction name. All the extraction details are displayed in the Extract Definition details panels.

    − Extract Definition. Displays a list of extract definitions. It is possible to remove columns from the Extract Definition by clearing the associated box. By default, the automatically generated columns are not

    Parameter Value Parameters Description

    DTLAPP Name Allows the you to specify the capture extract application ID without having to define a new data source when accessing PowerExchange (CAPXRT) data through ODBC.

    DTLDSN DSN Allows the SQL override of the physical file name coded in the data map. Allows you to use ODBC to read NRDB and NRDB2 data from various files through one ODBC data source. For ODBC this is coded anywhere in the SQL as {DTLDSN=xxx}.

    DTLXTYPE/Type SL None Extract all new captured data since the last extraction.

    RS None Default DTLXTYPE. Run the last-specified extraction process. This is either the last extraction that was run or the one that is specified with the Reset Start Point Wizard in the Application dialog box. For more information about Application Groups, see “Application Group” on page 24.

    Extraction Maps 23

  • displayed. Click the mouse right button to display these columns. They can be selected as part of the extract definition. Click File > Save to save any changes.

    − Extraction Details. Displays the Name, Version and referenced Table of the extraction definition.

    − Table Details. Displays the column information of the table referenced by the extraction definition. This includes:

    ♦ Name

    ♦ Type

    ♦ Precision

    ♦ Scale

    ♦ Length

    You can right-click the Table Details area of the Extract Definition dialog box and select Show Auto Generated Columns from the menu. The following columns appear:

    In addition, null indicator hidden columns are shown adjacent to nullable columns and a length indicator when these are of variable length.

    − Resource Inspector. The Extraction Group tab displays the connection properties of the extraction definition. If you make any changes, use the Apply button to confirm your changes.

    Application GroupYou can display the information for a given extraction application and reset the status of the extraction process to allow for another run.

    Column Description Data Type Length

    DTL__CAPXRESTART1 Coded position of the extracted data in the extraction log.

    VARBIN 255

    DTL__CAPXRESTART2 Coded start point for the oldest unit-of-work. VARBIN 255

    DTL__CAPXUOW Coded position of the start of the commitment control for the unit-of-work for this update.

    VARBIN 255

    DTL__CAPXUSER Value is always null. Microsoft SQL Server does not provide this information.

    VARCHAR 255

    DTL__CAPXTIMESTAMP The time the change is captured by PowerExchange. The time displays in the following format:YYYYMMDDHHMMSSnnnnnn (where nnnnnn=microseconds)

    CHAR 20

    DTL__CAPXACTION The change capture action: I for insert, D for delete, or U for update.

    CHAR 1

    DTL__BI The Before Image of the changed field is retrieved in addition to the normal retrieval of the After Image. For more information about DTL__BI, see the PowerExchange Navigator User Guide.

    Has the data type and length of the source column.

    DTL__CI You can add a change indicator (CI) to each column in which you are interested. For Updates this indicates if the column has changed: Y for yes, N for no. Inserts and Deletes always returns a null value.For more information about DTL__CI, see the PowerExchange Navigator User Guide.

    CHAR 1

    24 Chapter 4: Configuring SQL Server Change Data Capture

  • You can view an audit trail of all the extractions that have run, their status and an indication of the captured data that has been moved.

    The Application Group is based on the same principle as the extraction and registration groups. The group level identifies the location of the PowerExchange Listener task. There is no need for a database instance type or name. The Resource Inspector displays the following:

    ♦ Name

    ♦ Location

    ♦ UserID

    ♦ Password

    The Application Name list is based on the application name on the extraction run.

    Click on an application name to display a list of all successful and unsuccessful extractions. Extractions appear in order of execution, starting with the most recent. Click on the timestamp to display details for the extraction run, including registration name, table name, and the CND files that were read.

    Right-click an application name to displays a list of possible actions for the application name. Select a timestamp for a given application and then right-click to display a list of options.

    Reset to a New Start PointThe Application tracks the extractions against a registration and stores the start point for the next run. There are occasions when one or more extractions need to be run again. You can do this by resetting the start point for the application.

    This feature is used to reset the start point of the next extraction run for the selected application. It resets the start point to the start point of the open timestamp. You can then perform one of the following processes:

    ♦ Restart the application at the start of the selected run.

    ♦ Reset the application again.

    Note: This is a powerful feature and can not be undone. If in doubt, use DTLUAPPL. Tokens can be printed for copy/paste using DTLUCDEP.

    The following examples use an application MSSQLRT, which has had three extractions run against it. Because this is for demonstration purposes only, the extract times are very close together.

    To restart to a new start point:

    1. To open the required application, double-click the Application Group, and then select an application.

    Note the order of runs shown in the right hand pane. The first and last runs show the time of the first and last runs and the Current Run is blank.

    2. Highlight the run to which the start point is to be reset. In this case the earliest of the two runs is selected.

    3. To select the Application Group name, right-click and select Reset To New Start Point. Note how the icon to the left of the application group turns red. The restart point is reset to the start point of the chosen run.

    4. Save the change. The Current Run information is replaced by the run information from the second extraction.

    XTYPE Description

    SL Extract all new captured data since the last extraction.

    RS Run the last-specified extraction process again. This is either the last extraction that was run or the one that is specified in the Application dialog box.

    Application Group 25

  • Migrating to Condense File Extraction ModesYou can migrate real-time extractions to batch or continuous extraction modes. Consider the following:

    ♦ PowerExchange Condense uses the capture registration to parse the change data it writes to the condense files. During the capture registration creation process, PowerExchange records version information in the capture registration.

    PowerExchange Condense writes the changes to the condense files in a different format if the capture registration is created using PowerExchange 8.5.x. This format change allows Condense to support multi-byte character sets. To prevent any future extraction incompatibilities, recreate any registrations enabled for Condense after installing PowerExchange 8.5.x.

    ♦ Restart tokens differ between real-time, batch, and continuous extraction mode.

    In order to maintain positioning within the change stream, PowerExchange constructs restart tokens. These restart tokens are used to re-establish connection to the change stream to the point of interruption when extractions are restarted.

    PowerExchange creates a one format of restart tokens for real-time and batch extraction mode and a different format for continuous extraction mode. These different formats of restart tokens are not compatible. Switching an extraction from one mode to another requires a migration process.

    Use the following procedures to migrate between extraction modes.

    To migrate from real-time to batch extraction mode:

    1. Configure PowerExchange Condense. For more information, see “Configuring the PowerExchange Condense Process” on page 30.

    2. Quiesce write activity to all tables switching from real-time to batch extraction mode.

    3. Extract all captured changes and then stop the extraction.

    4. Run DTLUAPPL with RSTTKN GENERATE to get restart point.

    Configure DTLUAPPL to use the MSQL CAPI_CONNECTION statement. If the PowerExchange configuration file is configured with this CAPI statement as the default, no overrides are necessary when using DTLUAPPL. Otherwise, use the CONN_OVR parameter and point to the MSQL CAPI_CONNECTION statement.

    5. Reinstate write access to all quiesced tables.

    6. Delete and recreate the capture registration specifying Condense Part.

    7. Update the RESTART_TOKEN and SEQUENCE_TOKEN statements in the PowerExchange Condense parameter file, dtlca.cfg, with restart information generated by DTLUAPPL. For more information, see “Configuring PowerExchange Condense Parameters” on page 32.

    8. Cold start PowerExchange Condense.

    9. Change the extraction from real-time to batch extraction mode.

    If using PWXPC, change the session to use a PWX CDC Change connection instead of a PWX CDC Real Time connection. For more information, see PowerExchange Interfaces for PowerCenter.

    If using ODBC, update the ODBC data source and change the DBTYPE from CAPXRT to CAPX. For more information, see the PowerExchange Reference Manual.

    10. Cold start the PowerCenter extraction session.

    To migrate from real-time to continuous extraction mode:

    1. Configure the Condense task. For more information, see “Configuring PowerExchange Condense” on page 36.

    2. Quiesce write activity to all tables switching from real-time to continuous extraction mode.

    3. Extract all captured changes and then stop the extraction.

    26 Chapter 4: Configuring SQL Server Change Data Capture

  • 4. Run DTLUAPPL with RSTTKN GENERATE to get restart points.

    Configure DTLUAPPL to use the MSQL CAPI_CONNECTION statement. If the PowerExchange configuration file is configured with this CAPI statement as the default, no overrides are necessary when using DTLUAPPL. Otherwise, use the CONN_OVR parameter and point to the MSQL CAPI_CONNECTION statement.

    5. Reinstate write access to all tables that were quiesced.

    6. Delete and recreate the capture registration specifying Condense Part.

    7. Update the RESTART_TOKEN and SEQUENCE_TOKEN statements in the Condense parameter file, dtlca.cfg, with restart information generated by DTLUAPPL for the Condense task. For more information, see “Configuring PowerExchange Condense Parameters” on page 32.

    8. Update the PowerExchange configuration file, dbmover.cfg, with the CAPX CAPI_CONNECTION. For more information, see “CAPX CAPI_CONNECTION Parameters” on page 14.

    9. Cold start PowerExchange Condense.

    10. Change the extraction from real-time to continuous extraction mode.

    If using PWXPC, update the PWX CDC Real Time connection in the session to specify the name of the CAPX CAPI_CONNECTION statement in the CAPI Connection Name Override attribute. For more information, see PowerExchange Interfaces for PowerCenter.

    If using ODBC, override the ODBC data source with the name of the CAPX CAPI_CONNECTION statement using the SQL Escape Sequence DTLCONNOVR. For more information, see the PowerExchange Reference Manual.

    11. Cold start the PowerCenter extraction session.

    To migrate from batch to continuous extraction mode:

    1. Stop the Condense task.

    2. Extract all captured changes and then stop all extractions.

    3. Run DTLUAPPL with RSTTKN GENERATE to get restart point.

    Configure DTLUAPPL to use the MSQL CAPI_CONNECTION statement. If the PowerExchange configuration file is configured with this CAPI statement as the default, no overrides are necessary when using DTLUAPPL. Otherwise, use the CONN_OVR parameter and point to the MSQL CAPI_CONNECTION statement.

    4. Update the RESTART_TOKEN and SEQUENCE_TOKEN statements in the Condense parameter file, dtlca.cfg, with restart information generated by DTLUAPPL for the Condense task. For more information, see “Configuring PowerExchange Condense Parameters” on page 32.

    5. Update the PowerExchange configuration file, dbmover.cfg, with the CAPX CAPI_CONNECTION. For more information, see “CAPX CAPI_CONNECTION Parameters” on page 14.

    6. Cold start PowerExchange Condense.

    Note: PowerExchange Condense deletes all existing condense files when cold started. Extract all condensed data for all tables before using cold start.

    7. Change the extraction from batch to continuous extraction mode.

    If using PWXPC, change the session to use a PWX CDC Real Time connection instead of a PWX CDC Change connection. Specify the name of the CAPX CAPI_CONNECTION statement in the CAPI Connection Name Override attribute. For more information, see PowerExchange Interfaces for PowerCenter.

    If using ODBC, update the ODBC data source changing the DBTYPE from CAPX to CAPXRT. Override the ODBC data source with the name of the CAPX CAPI_CONNECTION statement using the SQL Escape Sequence DTLCONNOVR. For more information, see the PowerExchange Reference Manual.

    8. Cold start the PowerCenter extraction session.

    Migrating to Condense File Extraction Modes 27

  • 28 Chapter 4: Configuring SQL Server Change Data Capture

  • C H A P T E R 5

    PowerExchange Condense

    This chapter includes the following topics:

    ♦ PowerExchange Condense Overview, 29

    ♦ Configuring the PowerExchange Condense Process, 30

    ♦ Configuring PowerExchange Condense Parameters, 32

    ♦ Starting and Stopping PowerExchange Condense, 35

    PowerExchange Condense OverviewPowerExchange Condense captures changes from transactional databases, condenses the changes, and then writes the changes to condense files. PowerExchange Condense parameters control the frequency with which the data is condensed.

    Changes are partially condensed into chronological order without eliminating any of the individual changes made to a record. This method is called partial condense.

    PowerExchange extracts changes from condense files using one of the following modes:

    ♦ Batch extraction mode for condense files using the CAPX access method

    ♦ Continuous extraction mode for condense files using the CAPXRT access method

    Making Capture Registrations Eligible for Condense ProcessingPowerExchange Condense only condenses data for capture registrations that request condense processing. Request condense processing for a capture registration by selecting Part for the condense option in the capture registration. For more information about capture registrations, see “Managing Capture Registrations” on page 17.

    PowerExchange Condense requires active capture registrations with condense specified. If no capture registrations meet these criteria, PowerExchange Condense issue a message indicating that there are no active registrations and ends. For more information about modifying existing capture registrations to take advantage of the condense option, see “Extraction Maps” on page 20.

    29

  • Configuring the PowerExchange Condense ProcessPowerExchange Condense is composed of the following subtasks:

    ♦ Controller. This subtask starts and stops the other subtasks and controls PowerExchange Condense processing.

    ♦ Condense. This subtask read changes from the change stream, condenses the change data, and writes the changes to condense files.

    ♦ Command handler. This subtask provides the command interface to the condense subtask.

    ♦ Dump. This subtask provides dump services to the condense subtask.

    The PowerExchange log contains messages indicating when the various tasks start and end and also from which task a message is being issued.

    PowerExchange Condense Operational ModesPowerExchange Condense has the following modes of operation:

    ♦ Batch

    ♦ Continuous

    Set the mode of operation using the COLL_END_LOG parameter. For more information, see “Configuring PowerExchange Condense Parameters” on page 32.

    PowerExchange Condense Batch ModeIn batch mode, a single condense cycle is run and then PowerExchange Condense shuts down. Running PowerExchange Condense in this fashion is well suited to batch extraction applications.

    Specify batch mode for PowerExchange Condense by coding COLL_END_LOG=1 in the Condense configuration file.

    PowerExchange Condense Continuous ModeIn continuous mode, PowerExchange Condense runs the condense subtask continuously for an extended period of time. The condense subtask pauses after each condense cycle. The next condense cycle is triggered by one of the following:

    ♦ The NO_DATA_WAIT period expires.

    ♦ A CONDENSE command is manually entered.

    ♦ A FILESWITCH command is manually entered.

    ♦ A SHUTCOND command is manually entered.

    In continuous mode, PowerExchange Condense does not shut down. You must shut it down using the SHUTDOWN or SHUTCOND command.

    Specify continuous mode for PowerExchange Condense by coding COLL_END_LOG=0 in the Condense configuration file.

    File Switch ProcessingRunning in continuous mode, PowerExchange Condense periodically closes condense files and then starts new ones. This process is called file switch processing. File switch processing closes the open condense files if they contains data and opens a new set of condense files for future changes. PowerExchange Condense automatically does a file switch when the criteria defined by the FILE_SWITCH_CRIT, FILE_SWITCH_VAL, and the FILE_SWITCH_MIN configuration parameters are met. File switch also occurs if you manually issue a FILESWITCH command.

    30 Chapter 5: PowerExchange Condense

  • Note: PowerExchange Condense does not file switch if no data is present in the current condense file. The file switch is skipped until the next interval. The file switch continues to be skipped until an interval expires and there is data in the condense file.

    PowerExchange Condense Output FilesPowerExchange Condense writes output files to the directory specified by the CAPT_PATH parameter in the PowerExchange dbmover.cfg configuration file. If no CAPT_PATH parameter is specified, PowerExchange Condense writes the output files to the directory from where it is invoked.

    CDCT FileThe CDCT file is updated by PowerExchange Condense. The PowerExchange Listener reads the CDCT when extracting data.

    After each file switch, PowerExchange Condense writes records to the CDCT containing information about each condense file. These keyed records contain information about the data that has been condensed such as the condense file name, the start and end times, whether before images are included, the number of records in the file, and other control information.

    For example, if a partial condensed file contains records for two registration tags, then PowerExchange Condense writes three records to the CDCT. All records show the name of the file. Two of the records show the record count for each registration tag. The other record has no registration tag and counts the number of “commit” records in the file, one for each unit of work.

    CDCT records match DCT records on the Checkpoint file. PowerExchange Condense verifies the records match during warm start processing. If they do not match, PowerExchange Condense adjusts the CDCT by either inserting or deleting records as appropriate.

    Condense FilesPowerExchange Condense creates condense files during the condense cycle if there are captured changes to write. The condense files contain the change data for the active registrations PowerExchange Condense found during its initialization. PowerExchange Condense customizes the names of the condense files using the valu