Known Issues for Replicating to SAP HANA Database

Known issues and workarounds for replicating to SAP HANA database.

SAP HANA ODBC Drivers Version 1.00.71.00 Build 0388428-1510 Issues
CR# Bugzilla# Description
755778 47344  

(Solaris) When using either version 70 or 71 of the ODBCdriver, the SAP Replication Server fails while creating the initial connection to the SAP HANA database. After restarting the server, the connection may drop and re-create.

Workaround: None.

SAP HANA ODBC Drivers Version 1.00.55 Build 0376513-1510 Issues
CR# Bugzilla# Description
737784 25968  

You cannot create a connection to a replicate SAP HANA database if you do not have write privileges to the $HOME directory before you start SAP Replication Server.

Without these privileges, when creating the connection to the SAP HANA database, the connection fails and the SAP Replication Server generates and displays the errors.

Workaround: Make sure you have write privileges to the $HOME directory when starting an SAP Replication Server.

737642 30506

Cannot replicate DECFLOAT values between -2.2207e-307 to 2.2207e-308 into an SAP HANA database.

Workaround: None.
SAP HANA Database Issues
CR# Description
735171

When replicating GB 18030 character set to SAP HANA database for text and ntext columns, the replicate value differs between the primary Replication Server and replicate Replication Server.

Workaround: Do not use text or ntext columns when you are using the GB 18030 character set.
Replicating from SAP Business Suite to SAP HANA Database Issues
CR# Description
755511

Replication Agent for Microsoft SQL Server does not truncate tables that are marked for replication.

Workaround: Execute the sp_SybTruncateTable stored procedure to truncate tables that are marked for replication.

sp_SybTruncateTable temporarily turns off the replication flag for the marked tables, issues the truncate table command, then turns on the replication flag. See Replication Agent for Microsoft SQL Server in the Replication Agent Primary Database Guide.

If you are replicating SAP Business Suite applications, download the latest patch of the SAP kernel that uses the sp_SybTruncateTable stored procedure. See SAP Note 1972365 – Retry on error 4711.
753984

If pdb_automark_tables is true when you create a new table, Replication Agent for UDB cannot replicate the transactions into the table.

Workaround:
  • For non-SAP Business Suite applications – when creating tables in Replication Agent for UDB, add the DATA CAPTURE attribute to the create table statement, or include the alter table DATA CAPTURE statement in the same transaction as the create table statement.
  • For SAP Business Suite applications – see SAP Note 1991666 - DB6: Using Sybase Replication Server Software for the patch and configuration instructions that add the DATA CAPTURE attribute to create table statements issued by the SAP ABAP stack. However, this patch does not include create table statements issued by the SAP Business Suite Java stack.
Replicating from Oracle to SAP HANA Database Issues
CR# Description
757705

If you deploy a new model and there are existing interfaces entries with same name and port number, the model does not deploy and generates an error.

Workaround: Manually edit the interfaces file to delete the existing entries.
756231 An error is generated when you replicate the TIMESTAMP WITH TIME ZONE Oracle datatype into an SAP HANA database.

Workaround: Explicitly create a table replication definition that includes the map to char clause.
Parent topic: Known Issues