PUBLICSAP Replication Server 16.0 SP04Document Version: 1.0 – 2020-12-10

SAP Replication Server Release Bulletin

© 2

020

SAP

SE o

r an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Supported Operating Systems and Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 Known Issues for SAP Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Known Issues for Replication Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3 Known Issues for Replicating to SAP IQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.4 Known Issues for Replicating to SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.5 Known Installation Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

2 PUBLICSAP Replication Server Release Bulletin

Content

1 Supported Operating Systems and Databases

This topic directs you to the slides that describe the supported platforms and databases for SAP Replication Server.

For information on the supported platforms for SAP Replication Server, as well as the supported source and target databases, see the Essential Information section on the General Information tab of the SAP Replication Server 16.0 page on the Product Availability Matrix (PAM).

SAP Replication Server Release BulletinSupported Operating Systems and Databases PUBLIC 3

2 Known Issues

Review known issues and workarounds, listed by Change Request (CR) number.

NoteYou can search for knowledge base articles and solved cases in the SAP Support Portal at https://support.sap.com/home.html . Log into the portal, select Knowledge Base & Incidents to start searching.

Key to issue types:

RTC SAP Release to Customer tracking number.

CSN SAP Customer Services Network tracking number.

CR Sybase Change Request number.

AG Agentry tracking number.

N/A No tracking number.

Related Information

Known Issues for SAP Replication Server [page 5]Known Issues for Replication Agent [page 8]Known Issues for Replicating to SAP IQ [page 9]Known Issues for Replicating to SAP HANA [page 9]Known Installation Issues [page 10]

4 PUBLICSAP Replication Server Release Bulletin

Known Issues

2.1 Known Issues for SAP Replication Server

Table 1: SAP Replication Server Issues

CR # Platform Description

823665 UNIX

Windows

ERSSD Replication Agent fails to start up after upgrading to 16.0 SP04.

If an SAP Replication Server server uses the ERSSD with a route connection, after upgrad­ing to 16.0 SP04 with the out-place upgrading, it might run into the issue that the ERSSD Replication Agent fails to start up. The out-place upgrading is to install the new version of SAP Replication Server in a new folder while the old folder which contains the old SAP Rep­lication Server remains no change. When the ERSSD Replication Agent tries to start, the dbltm thread invokes files (32-bit) in the old installation folder, but the new installation for 16.0 SP04 uses 64-bit files, so the startup fails.

Error message might look like this:

$SYBASE/REP-16_0/ASA17/bin/dbltm: error while loading shared libraries: libdblib17_r.so: wrong ELF class: ELFCLASS64

Workaround:

Manually remove the following two entries from the configuration file:

erssd_release_dir_generated erssd_start_cmd_generated

795648 UNIX

Windows

Replication Server may crash when starting.

If the ERSSD process runs out of memory and fails before Replication Server has time to initialize all of its modules, the Replication Server initialization phase could experience some inconsistencies when it automatically restarts the ERSSD process. This can cause Replication Server to crash.

Workaround:

End the ERSSD process manually and restart Replication Server.

Try the following method to prevent this issue from happening again:

● Use the erssd_cache_size parameter to limit the ERSSD process's memory con­sumption. For example:

configure replication server set erssd_cache_size to “70”

This example configures the ERSSD process to use no more than 70% of the server's virtual memory.

If of the workarounds solves the problem, contact SAP technical support for further assis­tance.

SAP Replication Server Release BulletinKnown Issues PUBLIC 5

CR # Platform Description

740507 UNIX

Windows

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, but only during materialization when all the following conditions are met:

● The subscription where clause includes a varchar datatype column, and the col­umn 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 in­sert error, enable auto-correction and resume DSI. After the failed row is replicated, disable autocorrection.

704615 UNIX

Windows

SAP Replication Server may incorrectly interpret LTL commands sent by RepAgent if you enable both the asynchronous parser and Executor command cache features si­multaneously.

Workaround: Do not use both features simultaneously

702699 UNIX (Linux) You cannot create an ExpressConnect for Oracle (ECO) connection if you have selected the sample Replication Server during installation.

Workaround: Manually start the sample Replication Server after installation.

678521 UNIX

Windows

Cannot find a matching function string for the function-string class rs_sqlserver_func­tion_class.

If you create multiple replication definitions for a specified primary table and you subse­quently alter a column without an LOB datatype to be an LOB column in one of the replica­tion 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 'all-types.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.

6 PUBLICSAP Replication Server Release Bulletin

Known Issues

CR # Platform Description

618624 UNIX

Windows

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 Windows 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.

SAP Replication Server Release BulletinKnown Issues PUBLIC 7

2.2 Known Issues for Replication Agent

Table 2: Replication Agent Issues

CR # Platform Description

689941 UNIX

Windows

RepAgent for SAP ASE handles some of the normalization errors from SAP Replication Server as warnings, which may result in data loss.

Workaround: Upgrade to SAP Replication Server 15.7 and later.

● If you are using a version of SAP ASE earlier than 15.7, the RepAgent log may show in­correct normalization errors. For example:

Column unknown.unknown status 'always_replicate' in replication definition does not match database status 'replicate_if_changed'. Use 'alter replication definition' to set 'replicate_if_changed' status, at least until existing transactions have been processed. (Refer to Troubleshooting Guide for recovery procedures.)

See the accurate error information in the SAP Replication Server log. For example:

E2011/11/16 09:17:11. ERROR #32057 REP AGENT(ost_replnxb9_32.pdb1) - /nrm/nrm.c(4175) The value given for 'blurbs.copy' cannot be translated from datatype 'text_status' to the required datatype 'varchar'.

● If you are using a version of SAP ASE later than 15.7, the RepAgent log shows the cor­rect error information. For example, the RepAgent log shows:

00:0002:00000:00018:2011/11/16 09:17:11.71 server RepAgent(4): Received the following error message from the Replication Server: Msg 32057. The value given for 'blurbs.copy' cannot be translated from datatype 'text_status' to the required datatype 'varchar'.

8 PUBLICSAP Replication Server Release Bulletin

Known Issues

2.3 Known Issues for Replicating to SAP IQ

Known issues concerning replication to SAP IQ from SAP ASE using real-time loading (RTL) in SAP Replication Server.

Table 3: Issues for Replicating to SAP IQ

CR # Platform Description

722797 UNIX

Windows

The default SAP IQ NUMERIC and DECIMAL datatypes precision and scale do not match and are incompatible with the isql and the SAP ASE defaults.

When using the default precision and scale in the replicate SAP IQ table definition for NUMERIC andDECIMAL datatypes, the SAP Replication Server DSI thread shows:

ct_results(): protocol specific layer: external error: There is a tds protocol error. An invalid numeric precision was received.Workaround: Define the target SAP IQ NUMERIC and DECIMAL datatypes with precision less than or equal to 77. See Numeric Data Types in the SAP IQ Reference: Building Blocks, Tables, and Procedures.

695949 UNIX

Windows

Connection to SAP IQ 15.4 fails when create connection using profile with UTF-8 char­acter set.

Workaround: Use SAP IQ 15.4 ESD #1.

2.4 Known Issues for Replicating to SAP HANA

Table 4: Issues for Replicating to SAP HANA

CR# Bugzilla# Platform Description

757705 N/A UNIX

Windows

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.

SAP Replication Server Release BulletinKnown Issues PUBLIC 9

2.5 Known Installation Issues

Table 5: Installation Issues

CR # Platform Description

706443 UNIX

Windows

Cannot validate passwords if you start sample Replication Server after installation.

Workaround: Manually edit these attributes in the SAMPLE_RS.res file:

● rs.rs_idserver_pass● rs.rs_rssd_prim_pass● rs.rs_rssd_maint_pass● rs.rs_ltm_rs_pass● rs.rs_rs_sa_pass● rs.rs_rs_pass

See Syntax and Parameters for a Resource File in the Configuration Guide.

701924 UNIX

Windows

The installer does not remove environment variables entries from earlier versions of $SYBASE/SYBASE.sh and $SYBASE/SYBASE.csh for UNIX, and %SYBASE%\SYB­ASE.bat for Windows

Workaround: For UNIX, manually edit the $SYBASE/SYBASE.sh and $SYBASE/SYBASE.csh to remove environment variables that are pointing to versions you do not want to include. For Windows, manually edit the %SYBASE%\SYBASE.bat to remove en­vironment variables that are pointing to versions you do not want to include.

620755 UNIX Installation fails on Solaris SPARC.

When the file descriptor limit is set to “unlimited,” the installer fails with this message:

awk: insufficient memory for string storage Context is:>>> <<<Workaround: Set the hard file descriptor limit to a number.

619793 UNIX

Windows

You cannot use the Tab and arrow keys to navigate the Choose Product Features win­dow of the installation or uninstallation program.

Workaround:

● Uninstaller – use the mouse to click the Choose Product Features window. This sets the focus on the window and allows you to use your keyboard.

● Installer – use the mouse to select the features in the Choose Product Features win­dow.

619784 UNIX Cannot run installer with default tar tool.

You see this error when the installer uses the GNU tar tool to extract files from the SAP Replication Server suite archive:

The included VM could not be unarchived (TAR). Pleasetry to download the installer again and make sure thatyou download using 'binary' mode. Please do not attemptto install this currently downloaded copy.Workaround: Define /usr/bin/tar in $PATH.

10 PUBLICSAP Replication Server Release Bulletin

Known Issues

CR # Platform Description

619779 UNIX The installer fails to launch if you specify a path to setup.bin that contains “..”.

Workaround: Ensure that the path to setup.bin does not contain “..”.

618722 UNIX

Windows

Interactive installation using response file does not work.

When installing the software in an interactive mode using a response file, the installer does not use the values stored in the file. In silent mode, the response file works as expected.

Workaround: None.

SAP Replication Server Release BulletinKnown Issues PUBLIC 11

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

12 PUBLICSAP Replication Server Release Bulletin

Important Disclaimers and Legal Information

SAP Replication Server Release BulletinImportant Disclaimers and Legal Information PUBLIC 13

www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN