PUBLIC

SAP Adaptive Server Enterprise 16.0 SP04

Document Version: 1.0 – 2020-03-04

SAP ASE Release Bulletin

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

THE BEST RUN

Content

1 SAP ASE Release Bulletin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Known Issues for SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

SAP ASE Release Bulletin

2 PUBLIC Content
1 SAP ASE Release Bulletin

This release bulletin provides known issues about SAP ASE.

Product Components

For information about Open Server and SDK for ASE, see Open Server and SDK for SAP Adaptive Server
Enterprise.

Compatibility of Fixes with Previous SAP ASE Releases

SAP ASE 16.0 SP04 contains all the bug fixes of releases:

● 16.0 SP03 to 16.0 SP03 PL09

● 16.0 SP02 to SP02 PL09 (including Hot Fix releases through SAP ASE 16.0 SP02 PL09 HF2)
● 16.0 SP01 to SP01 PL03
● 16.0 to 16.0 PL05
● 15.7 SP130 to SP141 (including Hot Fix releases through SAP ASE SP141 HF2)
● 15.7 SP121 to SP122
● 15.7 SP110 to SP111
● 15.7 SP100 to SP104
● 15.7 to SP64

SAP ASE Release Bulletin

SAP ASE Release Bulletin PUBLIC 3
2 Known Issues for SAP ASE

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

Use the search fields for each column to find specific terms, platforms, and CR numbers.

SAP ASE Release Bulletin

4 PUBLIC Known Issues for SAP ASE
Table 1: SAP ASE Release Bulletin
CR # Platform Description

823548 Solaris SAP Replication Server runs into DSI down during HADR rolling up­
grade.
IBM AIX
When upgrading SAP Replication Server from versions upper than 16.0
HP-UX
SP03 to 16.0 SP04 for the HADR rolling upgrade on Solaris, IBM AIX, or
HP-UX platforms, SAP Replication Server runs into DSI down because it
can not find the function string rs_referential_integrity and
function string class rs_sqlserver_function_class.

Workaround:

After upgrading the inactive SAP Replication Server, log into the active
SAP Replication Server on the standby host, execute the following SQL
statements before go on with the failover process.

isql -Usa -P <password> -S <server_name> (SAP

Replication Server on the standby host)
connect
go
delete from rs_clsfunctions where funcid =
0x000000000400014c
go
insert rs_clsfunctions (prsid, funcname,
funcid, objid, conflicting, userdefined,
rowtype) values(0,"rs_referential_integrity",
0x000000000400014c,0x0000000000000000,0,0,1)
go
delete from rs_funcstrings where fstringid =
0x000000000800014c
go
insert rs_funcstrings (prsid, classid, funcid,
name, fstringid, attributes, parameters,
param_hash, rowtype)
values(0,0x0000000001000001,0x000000000400014c,
"rs_referential_integrity",0x000000000800014c,
24, 0,0,1)
go
delete from rs_systext where parentid =
0x000000000800014c
go
insert rs_systext values
(0,0x000000000800014c,'O',1,"")
go

delete from rs_funcstrings where fstringid =

0x000000000fffff5c
go
insert rs_funcstrings (prsid, classid, funcid,
name, fstringid, attributes, parameters,
param_hash, rowtype)
values(0,0x0000000001000003,0x000000000400014c,
"rs_referential_integrity",0x000000000fffff5c,
24,0,0,1)
go

SAP ASE Release Bulletin

Known Issues for SAP ASE PUBLIC 5
CR # Platform Description

823033 Linux Heartbeat startup fails on the primary and standby SAP ASE in the
Fault Manager configured HADR environment.
Solaris
The SAP Host Agent 721_REL PL49 which is being shipped with SAP ASE
IBM AIX
16.0 SP04 can cause Fault Manager bootstrap to fail with heartbeat er­
HP-UX rors in the log.

Windows Workaround:

You can either:

● change the permission of the /usr/sap/hostctrl/work di­

rectory to 755 on both the primary and standby SAP ASE servers.
For example:

chmod -R 755 /usr/sap/hostctrl/work

● add the SAP ASE user that is provided during the installation of Fault
Manager to the sapsys group. For example, if the user is fmuser,
run the following command to add it to the sapsys group:

$usermod -a -G sapsys fmuser

SAP ASE Release Bulletin

6 PUBLIC Known Issues for SAP ASE
CR # Platform Description

822042 Solaris RMA cannot start after upgrading JRE to version 8.

The UcryptoProvider is added to the security providers list in JRE 8

with high priority, which is used by default. But the RMA classloader
doesn't support this security provider and therefore RMA cannot start.

Workaround:

1. Comment out this security provider.

2. Assign the sun.security.pkcs11.SunPKCS11 of high prior­
ity in the java.security under $SYBASE/shared/
SAPJRE-8_1_062_64BIT/lib/security. For example:

#security.provider.
1=com.oracle.security.ucrypto.UcryptoProvid
er ${java.home}/lib/security/ucrypto-
solaris.cfg
#security.provider.
2=sun.security.pkcs11.SunPKCS11 $
{java.home}/lib/security/sunpkcs11-
solaris.cfg
#security.provider.
3=sun.security.provider.Sun
#security.provider.
4=sun.security.rsa.SunRsaSign
#security.provider.5=sun.security.ec.SunEC
#security.provider.
6=com.sun.net.ssl.internal.ssl.Provider
#security.provider.
7=com.sun.crypto.provider.SunJCE
#security.provider.
8=sun.security.jgss.SunProvider
#security.provider.
9=com.sun.security.sasl.Provider
#security.provider.
10=org.jcp.xml.dsig.internal.dom.XMLDSigRI
#security.provider.
11=sun.security.smartcardio.SunPCSC
security.provider.
1=sun.security.pkcs11.SunPKCS11 $
{java.home}/lib/security/sunpkcs11-
solaris.cfg
security.provider.
2=sun.security.provider.Sun
security.provider.
3=sun.security.rsa.SunRsaSign
security.provider.4=sun.security.ec.SunEC
security.provider.
5=com.sun.net.ssl.internal.ssl.Provider
security.provider.
6=com.sun.crypto.provider.SunJCE
security.provider.
7=sun.security.jgss.SunProvider
security.provider.
8=com.sun.security.sasl.Provider
security.provider.
9=org.jcp.xml.dsig.internal.dom.XMLDSigRI
security.provider.
10=sun.security.smartcardio.SunPCSC

SAP ASE Release Bulletin

Known Issues for SAP ASE PUBLIC 7
CR # Platform Description

820582 Linux Stable Queue Manager (SQM) is in the Sleeping for Segment
status and therefore may hang the execution of the suspend capture
Solaris
command.
IBM AIX
Workaround:
HP-UX
Expand the proportion of inbound queue:
Windows
configure replication server set
ibq_part_proportion to 'value'

The default value is 70 (%) , you can expand the value to larger than 70.

If the SQM status is still Sleeping for Segment after expanding

the proportion to 100, try to expand or add partitions for this SAP Repli­
cation Server.

808181 Windows While closing an ASEConnection thread, ADO.NET for the

Drv160SP03PL07 driver may crash with the following error:
Exception Sybase.Data.AseClient.AseException: At-
tempt to locate entry in sysdatabases for data-
base 'System.Char[]' by name failed - no entry
found under that name.
Make sure that name is entered properly.
Workaround: none.

SAP ASE Release Bulletin

8 PUBLIC Known Issues for SAP ASE
CR # Platform Description

814939 Linux You may receive error 10330 when accessing cross-database "dbo"
owned objects through "dbo" owned procedures. This happens when
Solaris
the objects and procedures are created by the user aliased to "dbo".
IBM AIX
 Note
HP-UX
There are no issues with accessing:
Windows
● Objects in the same database
● Objects created by "dbo" itself
● Non-dbo objects

Workaround:

1. As a "dbo", modify the owner of the objects to "dbo". Examples:

alter table my_tab modify owner "dbo"

go

alter proc my_proc modify owner "dbo"

go

2. Free the object, partition, and index descriptors linked to the objects
using dbcc cacheremove(). Examples:

dbcc cacheremove (db1, my_tab)

go

dbcc cacheremove (db2, my_proc)

go

SAP ASE Release Bulletin

Known Issues for SAP ASE PUBLIC 9
CR # Platform Description

810159 Linux SAP ASE cockpit may no longer function after upgrading the SAP ASE
cockpit from versions SAP ASE 16.0 SP02 PL0x to version 16.0 SP02
Solaris
PL06 and later.
IBM AIX
If this occurs, you may see errors similar to the following in the SAP ASE
HP-UX Cockpit agent.log log file (located in $COCKPIT_HOME/log):

Windows
2017-12-05 19:03:11,959 [ERROR]
[module.ProductModuleLoader]
[scc-pm-loader-1-
AgentPlugin:name=com.sybase.ua.plugins.asemap_4
.0.0_1]
- The SCC Product Module "ASE Management Agent
Plugin" XML could not be
processed.
java.lang.RuntimeException: Could not query
repository for role
…
Caused by:
org.hibernate.NonUniqueObjectException: a
different
object with the same identifier value was
already associated
with the session:
[com.sybase.scc.model.resource.ResourceTypeVers
ion#9]

Workaround: Shut down the SAP ASE cockpit and preform one of the fol­
lowing:

● Replace $COCKPIT_HOME/plugins/ASEMAP/
ProductModule.xml with the previous version. This work­
around preserves the current repository (monitoring history), but
limits access to upgraded SAP ASE cockpit features.
● Remove the files located in $COCKPIT_HOME/services/
Repository/db/repository.*, erasing the current reposi­
tory.

SAP recommends that you not perform an in-place or installer-per­

formed upgrade for the cockpit. You can bypass this action by renaming
the COCKPIT-4 file to something else (for example,
old_COCKPIT-4) before starting the upgrade process. A new cockpit
will be installed (SAP ASE cockpit is part of the default install set).

Follow instructions here to add the SAP ASE to the new cockpit once the
upgrade is complete: https://launchpad.support.sap.com/#/notes/
0002307016

SAP ASE Release Bulletin

10 PUBLIC Known Issues for SAP ASE
CR # Platform Description

808629 Linux The enable delta dump tran configuration option is not com­
patible with archive databases.
Solaris
Transaction dumps created with enable delta dump tran ena­
IBM AIX
bled can create inconsistencies when loading more than one of these
HP-UX transaction dumps into an archive database.

Windows Workaround: Disable the enable delta dump tran configuration

parameter for transaction dumps that will be loaded into an archive data­
base.

799331 Solaris There are known issues when SAP ASE is configured for Kerberos on
the sunx64 (Solaris amd64) platform, and a Kerberos connection is
attempted to an SAP ASE server.

Workaround: To work around this issue, set the environment variable

LD_PRELOAD to the path of the GSSAPI library before booting the SAP
ASE server. For example, if the GSSAPI library is located at /work/
MIT_Kerberos/sunx64/lib/libgssapi_krb5.so:

● csh: setenv LD_PRELOAD /work/MIT_Kerberos/

sunx64/lib/libgssapi_krb5.so
● bash : export LD_PRELOAD = /work/MIT_Kerberos/
sunx64/lib/libgssapi_krb5.so

792988 Linux SAP ASE Cockpit fails to start.

Solaris The SAP ASE Cockpit fails to start if you do not have write permission to
the working directory.
IBM AIX
Workaround: Change to a directory with write permission before starting
HP-UX
SAP ASE Cockpit.
Windows

791557 Linux Error during installation in console or silent mode.

Solaris When installing SAP ASE in console or silent modes, an error is raised if
the DISPLAY environment variable is set.
IBM AIX
An error similar to the following is raised:
HP-UX

Windows class
com.sybase.ia.common.LastScreenAction.install()
Unexpected Fatal Error:
java.lang.NoClassDefFoundError: java/awt/
Toolkit :
cannot initialize class because prior
initialization attempt failed

Workaround: Unset the DISPLAY environment variable when running

the installer in console or silent modes.

SAP ASE Release Bulletin

Known Issues for SAP ASE PUBLIC 11
CR # Platform Description

785492 IBM AIX An attempt to connect to the XPserver will fail when configuration op­
tion enable xact coordination and server option
negotiated logins are set to true.

The following errors are produced:

11216/13/16 ct_connect(): protocol specific

layer:
external error: The attempt to connect to the
server failed. Run the SAP11216/13/16
ct_connect(): protocol specific layer:
external error: The attempt to connect to the
server failed.
11206/1/16 Unable to connect to server
'<servername>
11206/1/16 Unable to connect to server
'<servername>''

Workaround: None.

695625 Linux Confidentiality service causes error.

Solaris This message is reported by Open Client applications connecting to SAP

ASE:
IBM AIX
ct_send(): network packet layer: internal Client
HP-UX
Library error: State error: trying to write when
Windows connection is expecting a read.

This message is reported in some cases when the Kerberos message

confidentiality service is turned on.

Workaround: Reconnect to the server with the confidentiality service

turned off.

692496 Linux When installing an SAP ASE server to be used in an HA configuration,

the sp_companion stored procedure configure command may fail due
Solaris
to duplicate device names for the tempdbdev logical device.
IBM AIX
Workaround: Do not specify the "Tempdb Device" (set the value of this
HP-UX field to blank) when configuring the secondary server during SAP ASE in­
stallation.
Windows
● If additional tempdb space is required on either server, log in to this
server after the installation is complete and use the alter
database command to increase the size of tempdb.
● If additional disk space is required to allocate the tempdb database,
use the disk init command to create a new database device for
tempdb.
● If you create a new device, the logical device name should be unique
between the two servers.

SAP ASE Release Bulletin

12 PUBLIC Known Issues for SAP ASE
CR # Platform Description

684556 Linux The select for update semantics introduced in version 15.7 do not
support datapages-locked tables.
Solaris
Workaround: None. select for update support exists only for da­
IBM AIX
tarows-locked pages.
HP-UX

Windows

624167 Windows When you install SAP ASE 15.5 ESD #1 or later in a non-English envi­
ronment, the default installation type is Custom rather than Typical.

Workaround: Use the Custom option. If you select the option Typical, the
Additional Language Modules component is not installed, and some mes­
sages may not be localized.

595923 Linux Known issues with transfer table.

Solaris ● When creating a unique index that uses the ignore_dup_key

property, importing a row with a key that is already present in the ta­
IBM AIX ble leads to an error, and the import is aborted. This differs from
when a duplicate key is inserted with bcp or with a regular insert
HP-UX
statement, since in those cases, the row is discarded, and the trans­
Windows action continues.
● When an insert trigger exists, the trigger is not fired when data is
inserted through transfer table...from.

Workaround: None.

576652 Linux SySAM2-enabled products incorrectly determine the number of cores

and chips on quad-core processors.
Solaris
This may be as a result of your SAP ASE small business edition or chip
IBM AIX
license not being activated and having gone into a grace period.
Windows
Workaround: Remove this line from your SySAM properties file, if it ex­
ists:

cpuinfo.mechanism=NOAPICCHECK

If the problem still remains, set the following environment variable, then
run the products:

(sh) export SYBASE_SAM_CPUINFO=CPUID (csh)

setenv SYBASE_SAM_CPUINFO CPUID

If the problem still remains, please contact SAP Product Support.

SAP ASE Release Bulletin

Known Issues for SAP ASE PUBLIC 13
Important Disclaimers and Legal Information

Hyperlinks
Some 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 Platforms

Some 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 Features

Experimental 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 Code
Any 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 Language
We 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.

SAP ASE Release Bulletin

14 PUBLIC Important Disclaimers and Legal Information
SAP ASE Release Bulletin
Important Disclaimers and Legal Information PUBLIC 15
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