Known issues and workarounds for replicating to SAP HANA database.
CR# | Bugzilla# | Description |
---|---|---|
737642 | 30506 |
Cannot replicate DECFLOAT values between -2.2207e-307 to 2.2207e-308 into an SAP HANA database. Workaround: None. |
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. |
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:
|
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. |