Limitations and considerations

The following limitations apply when using SAP HANA as a source in a replication task.

The limitations differ according to whether you are accessing SAP HANA directly or via SAP Application Server.

Limitations when accessing SAP HANA directly

General limitations

• Change Processing is not supported with SAP BW tables.
• Compatibility views are not supported and will not be available for selection.
• CA views are not supported and will not be available for selection.
• Row store data storage is not supported.
• Multitenant architecture is only supported on a single host.

• Only transparent tables (including SAP S/4HANA transparent tables) are supported.

• Latency when applying changes - The latency shown in the User Interface is the interval between Replicate capturing a change from the source (i.e. not the source commit time), and that change existing on the target.

Limitations and considerations when using the Trigger-based CDC method

• Changes to a table's Primary Key will not be replicated to the target.

• Latency when applying changes - The latency shown in the User Interface is the interval between Replicate capturing a change from the source (i.e. not the source commit time), and that change existing on the target.

• DDL operations are not supported.

The following limitations only apply when the Record mode in the endpoint settings' Advanced tab is set to Primary key only:

• Soft DELETE operations are not supported and will not be captured.

• The Apply Conflicts error handling policy must be set to the following:

  No record found for applying an UPDATE: INSERT the missing target record

• The Store Changes replication mode is not supported when working with Change Tables. It is only supported when working with an Audit table.

• The Start from timestamp method of resuming a task is not supported.

• By default, the longest supported transaction length is 60 seconds. If there are transactions in your environment that exceed 60 seconds, set the Transactional consistency value in the endpoint's Advanced tab to the required value.

• For tasks configured with the Apply Changes replication option, transformation filters are only supported with Primary Key columns.

Limitations and considerations when using the Log-based CDC method

• Replicate creates a hana__row_id column on the target as a Unique Index and changes the original Primary Key/Unique Index to a standard column.

  Information noteOn MySQL and SAP HANA targets, Replicate creates a hana__row_id column on the target as a Unique Index and keeps the original Primary Key/Unique Index.
• Capturing DELETE and UPDATE operations for filtered records is not supported.
• The AR_H_USER header column is not supported.
• Transformations that affect multiple columns are not supported.
• When storing changes in Change Tables, only the Row_id and changed columns of the after-image will be stored. All other columns will have NULL values.
• The TRUNCATE table and PARTITION DDLs are not supported. On detecting a table with such operations, Replicate will suspend the table and require it to be reloaded.
• As the SAP HANA endpoint can be configured to connect to one instance only, in the event of failover in a HA environment, the endpoint must be manually reconfigured to point to the new instance. Then reload all associated tasks.

• The following Apply Conflicts error handling policy is not supported:

  No record found for applying an UPDATE: INSERT the missing target record

• The following Change Processing Tuning option is not supported:

  Using the Apply changes using SQL MERGE option in Batch optimized apply mode

• The SAP HANA scale-out configuration is not supported.

Unsupported data types

The following data types are not supported:

• ARRAY
• ST_GEOMETRY
• ST_POINT

Limitations and considerations when accessing SAP HANA via SAP Application Server

• The data type STRING (Length=0) for NCLOBs is not supported.
• The source_lookup Data Enrichment function is not supported. For more information on this function, see Data Enrichment functions
• Replication of views is not supported.
• Only transparent table are supported
• The AR_H_USER header column is not supported
• CA views are not supported and will not be available for selection
• Row store data storage is not supported.

• Replicate creates a hana__row_id column on the target as a Unique Index and changes the original Primary Key/Unique Index to a standard column.

  Information noteOn MySQL and SAP HANA targets, Replicate creates a hana__row_id column on the target as a Unique Index and keeps the original Primary Key/Unique Index.
• Capturing DELETE and UPDATE operations for filtered records is not supported.
• Transformations that affect multiple columns are not supported.
• When storing changes in Change Tables, only the Row_id and changed columns of the after-image will be stored. All other columns will have NULL values.
• The TRUNCATE table and PARTITION DDLs are not supported. On detecting a table with such operations, Replicate will suspend the table and require it to be reloaded.
• As the SAP HANA endpoint can be configured to connect to one instance only, in the event of failover in a HA environment, the endpoint must be manually reconfigured to point to the new instance. Then reload all associated tasks.

• The following Apply Conflicts error handling policy is not supported:

  No record found for applying an UPDATE: INSERT the missing target record

• The following Change Processing Tuning option is not supported:

  Using the Apply changes using SQL MERGE option in Batch optimized apply mode

• The SAP HANA scale-out configuration is not supported.

• A filter should be defined for the Client column to capture client-specific changes during CDC.

• Backint backup is not supported.

• Only S/4HANA systems are supported. SAP ECC on HANA (Business Suite on HANA) is not supported.