Known Issues for Replication Server

Known issues and workarounds for Replication Server.

Replication Server Issues
CR# Description
739573

Cannot create direct load subscription when there is no route from the replicate Replication Server to the primary Replication Server.

Workaround: Either:
  • Create a route from the replicate Replication Server to the primary Replication Server, or,
  • From the RSSD of the replicate Replication Server, get the rs_databases row for the replicate database and insert this row to the RSSD of the primary Replication Server, then restart the primary Replication Server.
739186 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 Replication Server Reference Manual.
739068 Replication Server fails to set unichar value when the table has 256 or more columns.
When there are more than 255 columns in a table, and if there are primary and replication definition column of unichar or univarchar, create subscription ... direct load may fail with this error message in the Replication Server log file:
E. 2013/05/08 14:17:29. ERROR #1027 MatApply( ) - /dsiutil.c(420) Open Client
    Client-Library error: Error: 34, Severity 5 -- '[ ExpressConnect for ODBC  Data Source|statement
    ] /calm/bldr/rsconx/odbc/generic/src/odbccolumn.cpp:1241  odbcCol::SetValue failed, value too
    long. Setting Parameter 15 to it's bind  location failed. '.

Workaround: Set the length of the corresponding replicate column twice as long as the one in the primary column.
738978 After using rs_init user database "upgrade" function and it finishes successfully, the admin version, “connection” command in Replication Server displays an incorrect Database information not found message.

Workaround: None.
738928 Replication Server does not include the hds_oracle_new_setup_for_replicate.sql script for the Oracle-to-Oracle database resynchronization.

Workaround: Use the Oracle-to-Oracle Database Resynchronization Script .
738917
For an Adaptive Server or a non-Adaptive Server primary database, a materialization error occurs in Replication Server if the table replication definition includes:
  • An LOB column
  • A column with a map to clause
  • No replicate_if_changed LOB column_name [, column_name]... clause

Workaround: Add a replicate_if_changed LOB column_name [, column_name] clause into the replication definition. For an Oracle primary database, you must define replicate_if_change.
738172 When the parallel DSI is enabled, and dsi_bulk_copy or dynamic_sql is set to on, Replication Server may fail if the transaction size is greater than dsi_large_xact_size.

Workaround: Either set:

  • The parallel DSI to off, or,
  • The dsi_bulk_copy and dynamic_sql to off.
737550 You cannot use dynamic_sql with an Adaptive Server replicate data server if tables have more 255 columns.

Workaround: Configure the replication definition and/or connection to use either Language or Bulk (dsi_bulk_copy) interface.
736202 When you set autocorrection to on for the replication definition table, Replication Server does not always update text columns correctly.

Workaround: Set autocorrection to off.
730159 Replication Server does not use the default value for a target value where none is supplied in the source value in a user-defined datatypes (UDDs) translation.

Workaround: None.
728541 Replication of LOB columns fails when data compression is enabled and you see these error messages in the Replication Server log: 
E. 2013/04/27 18:07:11. ERROR #5163 DSI EXEC(108(1) repl0_16504.tdb4) - /dsiexec.c(9510)
Text data is being converted from one character set to 
another. The length of the converted text data is longer 
than the length of the original text data times the 
config option 'dsi_text_convert_multiplier'. The value 
for the database 'repl0_16504.tdb4' is '0.000000'. Please 
increase this value for the database and resume the DSI thread.

See also Adaptive Server CR #738552.

Workaround: None.
724706 Replication Server does not start if the LANG environment variable is set to any value except a valid Open Client/Server language.

Workaround: Set the LANG environment variable to a supported Open Client/Server or 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”.
718342 Reference implementation fails because rs_init requires a non-NULL password for Replication Server.

Workaround: Provide a non-NULL password for the "sa" user in the configuration file.

708716 Upgrading versions of Replication Server earlier than 15.5 to version 15.5 and later may fail if the preupgrade 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 Replication Server.
704615 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
703894 When you set “Initialize standby using dump and load” to yes either in a resource file or in an interactive rs_init, rs_init does not add the maintenance user ID, and the Replication Server objects, such as tables and stored procedures, to the standby database.

Workaround: Use sp_addlogin to add the maintenance user to the standby database.
696035 Replication Server does not support upgrade Oracle database connections using ECO.
For connections with DCO, when you upgrade Replication Server to 15.7.1 GA and later, you see the DSI shutdown error:
" "CONN_ID": invalid identifier"
Workaround: Exclude your Oracle user databases from the seamless upgrade command, issue:
repserver -upgr...  -nodb oracle_user_db_id

and manually load the Oracle upgrade scripts.

See Upgrading Non-ASE User Databases and User Databases Not Supported by sysadmin upgrade in the Replication Server Configuration Guide.
694983 rs_init does not connect to an Embedded Replication Server System Database (ERSSD) using Adaptive Server® 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 Adaptive Server to Adaptive Server replication, 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 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 Replication Server is configured to use SSL.
618624 Insufficient number of threads in Replication Server.

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

Workaround:
  1. Log in to RSSD.
  2. Increase the value of num_threads.
  3. Restart Replication Server.
558253 Creating replication definition fails when using gb18030 character set and the ERSSD.
On Windows, 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 Replication Server.
452806 An application deadlock involving Replication Server and Adaptive Server may occur when 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 Replication Server.

Parent topic: Known Issues
Related concepts
Oracle-to-Oracle Database Resynchronization Script