Known Issues for SAP Replication Server

Known issues and workarounds for SAP Replication Server.

SAP Replication Server Issues
CR# Description
757999 You cannot create a subscription and use the multiple select threads option on a DB2 primary database older than version 9.7, if the num_selects option is greater than 1.

Workaround: Create the subscription without using the num_selects option, which means the number of select threads is forced to 1.
757913 If you create a subscription with a where clause for the DDL on an Oracle or a DB2 primary database, the command may fail with an error message. 
Msg 57, Level 12, State 0: 
Server '<repserver name>', Line 0: 
Type 0 is not a legal type.

Workaround: You cannot use DDL to create a subscription with a where clause on these primary databases.

757763 When the DSI suspends, the SAP Replication Server log displays message 5024 "the database with siteid '0 ' does not exist" .

Workaround: You can safely ignore this message.

757536 You cannot successfully complete an upgrade for a standalone SAP Replication Server if you are using an SAP ASE Replication Server System Database (RSSD) that does not have a RepAgent.

Workaround: Use a text editor to set these statements as comments in the rsproc_ase.sql script before upgrading its RSSD. 
sp_setrepproc rs_cmd_marker,'function'
 go 
sp_setrepproc rs_section_marker,'function'
 go
752396 The Replication Server distributor thread shuts down if you attempt to insert data into a table in SAP ASE 15.7 SP120 configured with Multi-Path Replication™.

See also CR #751192.

Workaround: Do not use Multi-Path Replication.
750140 In some cases, when SAP Replication Server version 15.7.1 SP120 or later connects via an SSL connection to a replicate SAP ASE version 15.7 SP120 and later, the connection may fail.

Workaround: Increase the maximum size of the network packet and the default network packet size to 4096 or larger.

740507 Under some specific circumstances with some types of databases, unexpected rows may be materialized to the replicate server.

This issue does not occur during continuous replication; it occurs only during materialization when all the following conditions are met:

  • The subscription where clause includes a varchar datatype column, and the column includes trailing blanks.
  • The primary data server does not allow trailing blanks in a where clause, for example, 'abc' = 'abc  '.
  • The primary data server allows trailing blanks in the varchar datatype column. For instance, SAP ASE trims trailing blanks, but other database types do not.
Workaround:
  • Do not use a varchar datatype column with trailing blanks in a subscription where clause, if the primary data server (for example, UDB) does not allow trailing blanks.
  • If the varchar datatype column must be added to the subscription where clause, and the primary data server does not allow trailing blanks. Before materialization, trim the trailing blanks for the varchar datatype columns in the where clause.
  • If either option works and if the DSI is down in normal replication due to duplicate insert error, enable auto-correction and resume DSI. After the failed row is replicated, disable autocorrection.
739186 SAP Replication Server does not support SQM cache size greater than 2GB.

Workaround: Reconfigure the block_size, sqm_page_size, sqm_cache_size parameters to reduce the cache size to less than 2GB.

See configure replication server in the Reference Manual.
724706 SAP Replication Server does not start if the LANG environment variable is set to any value except a valid SAP® Open Client™/SAP® Open Server™ language.

Workaround: Set the LANG environment variable to a supported Open Client/Server or SAP Replication Server language, or to "".

718889 If the maintenance user does not have adequate permission on the rs_dbversion table, then admin version, “connection” may return incorrect status.

Workaround: When issuing admin version, “connection”, grant select permission on the rs_dbversion table to maintenance user before the maintenance user executes admin version, “connection”.
708716 Upgrading versions of SAP Replication Server earlier than 15.5 to version 15.5 and later may fail if the preupgrade SAP Replication Server is not an ID Server.

Workaround: Either:

  • Use sysadmin system_version to obtain the new version from the ID Server; or,
  • Restart the preupgrade SAP Replication Server.
704615 SAP Replication Server may incorrectly interpret LTL commands sent by RepAgent if you enable both the asynchronous parser and Executor command cache features simultaneously.

Workaround: Do not use both features simultaneously
694983 rs_init does not connect to an Embedded Replication Server System Database (ERSSD) using SAP® SQL Anywhere® when upgrading or downgrading with versions earlier than 15.5.

Workaround: Issue this trace option in rs_init:

rs_init -r resource_file_name -T T_SEND_CLEARTEXT_PASSWORD
694628 In SAP ASE to SAP ASE replication, SAP Replication Server always uses batch mode to send class-level function strings—such as rs_usedb and rs_set_ciphertext—that set connection attributes, even if you set batch off for the connection.

Workaround: None.
690422 Incorrect value for text and image columns.

In a warm standby environment, if you set text and image columns of a table to do_not_replicate on the active database, and you create a table replication definition for this table without send standby replication definition columns, the replication definition does not include the text and image columns. As a result, the standby database gets incorrect value for the text and image columns.

Workaround:
  1. Create the table replication definition with send standby replication definition columns clause.
  2. Drop the table replication definition if it is not necessary.
678521 Cannot find a matching function string for the function-string class rs_sqlserver_function_class.

If you create multiple replication definitions for a specified primary table and you subsequently alter a column without an LOB datatype to be an LOB column in one of the replication definitions, the LOB-related function strings are not created automatically for one of the replication definitions at the replicate Replication Server. The replicate Replication Server log shows:

Cannot find a matching function string for function 'alltypes.rs_writetext' and function string class 
'rs_sqlserver_function_class'.
Workaround:
  1. Clear the failed Data Server Interface (DSI) connection queue by executing resume/skip tran until the DSI connection resumes.
  2. Drop the subscription to the problem replication definition at the replicate Replication Server, then drop the replication definition at the primary Replication Server, then re-create both.
678488 Cannot replicate BLOB data into non-nullable blob column in UDB and DB2 target databases.

Workaround: Define the blob column as nullable:

  • In the database, and,
  • If you have a table-level replication environment, the replication definition created for the blob table replication.
642091 RepAgent fails when an SAP Replication Server is configured to use Secure Sockets Layer (SSL) with an ERSSD.

Workaround: Either:

  • Disable SSL using configure replication server with the use_ssl option, or,

  • Do not use ERSSD if the SAP Replication Server is configured to use SSL.
618624 Insufficient number of threads in SAP Replication Server.

If you increase the number of client connections and did not increase the number of SAP Open Server threads that the SAP Replication Server can use, SAP Replication Server may shut down.

Workaround:
  1. Log in to RSSD.
  2. Increase the value of num_threads.
  3. Restart SAP Replication Server.
558253 Creating replication definition fails when using gb18030 character set and the ERSSD.
When you are creating the replication definition table using create replication definition, the gb18030 character set does not work correctly if you are:
  • Using the ERSSD, and
  • Using multibyte characters in the replication definition name or the table name.
Workaround: Set the environment variable SACHARSET to GBK before starting the SAP Replication Server.
452806 An application deadlock involving SAP Replication Server and SAP ASE may occur when the SAP Replication Server is configured to use parallel DSI while applying transactions to a table containing text and image columns.

Workaround: Suspend and resume the DSI connection. If the DSI thread does not suspend, restart the SAP Replication Server.
Parent topic: Known Issues