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.

Each SAP HANA source table must contain a primary key before it can be registered for CDC. PowerExchange supports primary keys with up to 16 columns in each registered source table.

If you change a registration to or from Full Audit, you must drop the triggers for the registered table. You can manually create the triggers by using the trigger function and exporting the script, by running a row test in PowerExchange Navigator, or by letting the PowerExchange Logger create the triggers automatically.

If you change a registration from Full Audit to PKLOG only, you can drop the CDC shadow table or retain it for history purposes. The shadow table is required for capturing with Full Audit.

If you do not use Full Audit, PowerExchange requires all fields that are not primary keys must nullable, and PowerExchange switches non-nullable fields to nullable except for primary keys. Capture processing requires nullable fields because table registrations that do not use Full Audit do not have a before image, and any deletes in the capture process will be null.

You must create a separate capture registration for each SAP HANA source table.

SAP HANA CDC requires the PowerExchange Logger for Linux, UNIX, and Windows.

PowerExchange supports SAP HANA table names up to 120 characters. Tables with names longer than 120 characters cannot be registered for change data capture.