Known Issues for Replication Server

Changes to the LOB data are not always replicated when replicating columns of LOB types to Oracle using ExpressConnect for Oracle (ECO) in bulk copy mode.

Workaround: Configure the connection using ECO with dsi_bulk_copy set to off.

Message from server: Message: 2601, State 6, Severity 14 -- 'Attempt to insert duplicate key row in object 'rs_translation' with unique index 'rs_key_translation'

The rs_translation system table has unique index on (classid, source_dtid). The two translation (ASE binary to rs_oracle_binary and ASE timestamp to rs_oracle_binary) generates the duplicate key insert error.

Workaround: For Replication Server versions 15.5, 15.5 ESD #1, and 15.6, you have to manually remove the translations when you encounter this error. Open the SQL scripts and search for timestamp to find the related SQL statements.

delete from rs_profdetail where profid = 0x000000000e000000 and pdetailid = 0x000000000e00003f
delete from rs_systext where parentid = 0x000000000e00003f and sequence = 1
delete from rs_profdetail where profid = 0x000000000e000000 and pdetailid = 0x000000000e000040
delete from rs_systext where parentid = 0x000000000e000040 and sequence = 1

delete from rs_profdetail where profid = 0x000000000e010000 and pdetailid = 0x000000000e010042
delete from rs_systext where parentid = 0x000000000e010042 and sequence = 1
delete from rs_profdetail where profid = 0x000000000e010000 and pdetailid = 0x000000000e010043
delete from rs_systext where parentid = 0x000000000e010043 and sequence = 1

delete from rs_profdetail where profid = 0x000000000e020000 and pdetailid = 0x000000000e02003f
delete from rs_systext where parentid = 0x000000000e02003f and sequence = 1
delete from rs_profdetail where profid = 0x000000000e020000 and pdetailid = 0x000000000e020040
delete from rs_systext where parentid = 0x000000000e020040 and sequence = 1

delete from rs_profdetail where profid = 0x000000000e00000c and pdetailid = 0x000000000e000c27
delete from rs_systext where parentid = 0x000000000e000c27 and sequence = 1
delete from rs_profdetail where profid = 0x000000000e00000c and pdetailid = 0x000000000e000c28
delete from rs_systext where parentid = 0x000000000e000c28 and sequence = 1

delete from rs_profdetail where profid = 0x000000000e000012 and pdetailid = 0x000000000e001231
delete from rs_systext where parentid = 0x000000000e001231 and sequence = 1
delete from rs_profdetail where profid = 0x000000000e000012 and pdetailid = 0x000000000e001232
delete from rs_systext where parentid = 0x000000000e001232 and sequence = 1

timestamp columns are sent to the replicate database even if High Volume Adaptive Replication (HVAR) is set to on, send_timestamp_to_standby is set to off, and there is no replication definition defined.

If you use isql and SYBASE.csh to connect to Replication Server through Secure Sockets Layer (SSL), the connection fails. isql does not initialize the network filter.

source SYBASE.csh
setenv LIBPATH $SYBASE/$SYBASE_OCS/lib3p:$LIBPATH

source SYBASE.sh
export LIBPATH=$SYBASE/SYBASE_OCS/lib3p:$LIBPATH

When you use a served partition-level license generated from the Sybase Product Download Center to start a SySAM server, you see a message that you are using an invalid license key, similar to:

(SYBASE) Invalid license key (inconsistent authentication code)
(SYBASE) License server system started on hpiabou
(SYBASE) No features to serve, exiting
(SYBASE) EXITING DUE TO SIGNAL 49 Exit reason 4
(lmgrd) SYBASE exited with status 49 (No features to serve)
(lmgrd) SYBASE daemon found no features.  Please correct
(lmgrd) license file and re-start daemons.
(lmgrd)
(lmgrd) This may be due to the fact that you are using
(lmgrd) a different license file from the one you expect.
(lmgrd) Check to make sure that:
(lmgrd) /remote/cat_fc/nli/iq152.hpia/SYSAM-2_0/licenses/18965_hpiabou_
(lmgrd) is the license file you want to use.

Workaround: Use the old host IDs for the license running on the license server.

If the libsybdldap.so and libsybdldap64.so are not specified in the Directory section in libtcl.cfg, Replication Server cannot connect to the LDAP.

For example:

[DIRECTORY]
ldap32=libsybdldap.so ldap://sylvester:3389
/dc=Sybase,dc=com??one??bindname=cn=Manager,dc=Sybase,dc=com??secret  
ldap64=libsybdldap64.so ldap://sylvester:3389
/dc=Sybase,dc=com??one??bindname=cn=Manager,dc=Sybase,dc=com??secret

The entry name has changed from ldap to ldap32. To start the LDAP session with dscp utility:

open ldap32

When configuring Replication Server 15.5 or later using the rs_init with an existing RSSD, an error occurs in rs_init.

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.

1. Log in to RSSD.
2. Increase the value of num_threads.
3. Restart Replication Server.

If the sort order is not set correctly in the [collate] section of $SYBASE/config/objectid.dat, a stack trace error occurs during Replication Server start-up.

1. Make sure that the character set and set order have been set correctly in Rep_Server_name.cfg file. For example:
   • RS_charset=cp850
   • RS_sortorder=scannocp
2. Go to $SYBASE/charsets/character set; for example, $SYBASE/charsets/cp850.
3. Locate and open corresponding sort order file; for example, scannocp.srt.
4. Check the line that has an “id” and find the sort order ID, for example,

   id = 0x30; Unique ID # (48) for the sort order

   The sort order ID is 48.

5. In $SYBASE/config/objectid.dat, check that there is a line for that sort order under the [collate] section:

   1.3.6.1.4.1.897.4.9.3.48 = scannocp

   The last number is the sort order ID (48), all other numbers are identical for all lines. If you have a custom sort order, add this line for it.

6. Restart Replication Server.

If Replication Server uses the utf8 character set and the target Adaptive Server uses the gb18030 character set, an error occurs if a table has text and image column with dsi_bulk_copy or dsi_compile_enable parameter set to on. The DSI shuts down.

This may impact your replication performance.

Workaround:

• Use single quote (‘) or double quote(“) around the long repdef_name.
• Use a truncated repdef_name. Truncate the repdef_name to the first 29 characters when issuing the rs_helprep request. The rs_helprep then appends the % wildcard at the end when it queries the RSSD tables.
• Upgrade RSSD data server to Adaptive Server 15.x.

Workaround: Create the subscription without a quoted constant or create the subscription without materialization.

Workaround: Suspend and resume the DSI connection. If the DSI thread does not suspend, restart the Replication Server.