Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange Change Data Capture Introduction
  3. Part 2: CDC Components Configuration and Management
  4. Part 3: CDC Sources Configuration and Management
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: CDC for z/OS Troubleshooting
  8. Appendix B: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for z/OS

CDC Guide for z/OS

Back Next

DB2 ECCR Usage Guidelines

DB2 ECCR Usage Guidelines

The DB2 ECCR has the following usage guidelines:
  • You must define DB2 source tables with the DATA CAPTURE CHANGES option. For more information about this option, see the IBM DB2 documentation.
  • The first time you start the DB2 ECCR, use the START COLD parameter. Thereafter, use the START WARM parameter except when a cold start or special start is required for recovery purposes.
  • You need at least one active capture registration to start the ECCR successfully. If no active registrations exist, the ECCR abends with a U3680 code, and PowerExchange issues message PWXEDM177509E to indicate that no active registrations exist.
  • The DB2 ECCR issues IFCID 306 READS requests to read DB2 log data. To issue the READS request, the ECCR requires that MONITOR TRACE 1 be started. Therefore, the user ID under which the DB2 ECCR runs must have the following authorities:
    • TRACE authority to issue the START TRACE command.
    • DISPLAY authority to issue a DISPLAY TRACE to determine if the MONITOR TRACE is already active.
    • MONITOR2 authority to issue the READS request to get the log data that includes the changes to capture.
    If the user ID for the DB2 ECCR has SYSOPR, SYSCTL, or SYSADM authority, you do not need to grant additional authority.
    If the DB2 ECCR starts the trace during initialization, it issues the following message: 
    PWXEDM177137I -START TRACE(MONITOR) PLAN(
    plan
    ) LOCATION(
    caname
    ) CLASS(1)
    If MONITOR TRACE 1 is started, the DB2 ECCR does not issue the START TRACE command. If MONITOR TRACE 1 was not started or has been stopped, the DB2 ECCR starts it.
  • The DB2 ECCR reads the SYSTABLESPACE and SYSTABLEPART tables to determine if the DB2 table spaces that contain the source tables use an outdated row format version. If the table spaces use an outdated row format version, the ECCR reads the physical data sets that underlie table spaces to get the latest reordered row format (RRF) fixed-length-row information. For the ECCR to read the physical data sets, the ECCR must run under the control of a user ID that has read access to these data sets.
  • The DB2 ECCR also performs schema verification the first time that the ECCR receives a change record for a table after a schema change on that table. To prevent the ECCR from terminating when the table schemas do not match, you must update the corresponding capture registration any time that the source schema changes.
  • At DB2 ECCR startup, the ECCR issues SQL PREPARE and DESCRIBE statements to verify that the TCAP tables are of the correct format for the DB2 version from which the ECCR is capturing change data. Ensure that the user ID under which the ECCR runs has the EXPLAIN system privilege. This privilege is required for the ECCR to issue the PREPARE and DESCRIBE statements.
0 COMMENTS
We’d like to hear from you!