Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange CDC Introduction
  3. Part 2: PowerExchange CDC Components
  4. Part 3: PowerExchange CDC Data Sources
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

SAP HANA CDC Considerations

SAP HANA CDC Considerations

Review the following considerations for PowerExchange CDC for SAP HANA:
  • SAP HANA CDC uses both the ODBC driver and JDBC driver for SAP HANA. You must install and configure these drivers separately from the PowerExchange installation. For more information, see Preparing the SAP HANA Server for PowerExchange CDC.
  • SAP HANA CDC requires the PowerExchange Logger for Linux, UNIX, and Windows.
  • You must create a separate capture registration for each SAP HANA source table.
  • PowerExchange supports SAP HANA table names up to 127 characters. Tables with names longer than 127 characters cannot be registered for change data capture.
  • PowerExchange supports primary keys with up to 16 columns in a registered source table.
  • If a source table does not have a primary key, all columns are selected by default. Also, the
    Full Audit
    check box is selected by default and cannot be deselected.
  • When the
    Full Audit
    check box is not selected, PowerExchange switches non-nullable fields to nullable, except for fields in the primary key. Capture processing requires nullable fields because table registrations that do not use Full Audit mode do not have a before image, and any deletes in the capture process will be null.
  • If you switch a registered table from Full Audit mode to PKLOG capture mode, or from PKLOG mode to Full Audit mode, you must manually drop the existing triggers for the table. Also, delete the capture registration or change its status to History. After you re-register the source table, you can re-create the triggers 1) by using the Trigger option to generate the trigger script again, 2) by running a row test in PowerExchange Navigator, or 3) by letting the PowerExchange Logger create the triggers automatically.
  • The CDC shadow tables and sequence are required for capturing change data if you use the
    Full Audit
    option. If you no longer need a CDC table for a source table, you can drop it or retain it if you might need to use it again.

0 COMMENTS

We’d like to hear from you!