SAP ASE Release Bulletin HP En

20
7/21/2019 SAP ASE Release Bulletin HP En http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 1/20 PUBLIC SAP Adaptive Server Enterprise 16.0 SP02 Document Version: 1.1 – 2015-09-03 Release Bulletin for HP-UX

description

SAP SYBASE ASE 16

Transcript of SAP ASE Release Bulletin HP En

Page 1: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 1/20

PUBLIC

SAP Adaptive Server Enterprise 16.0 SP02

Document Version: 1.1 – 2015-09-03

Release Bulletin for HP-UX

Page 2: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 2/20

Content

1 Product Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 SAP Adaptive Server Enterprise Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

1.3 Database Always-On (HADR) Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.4 Product Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Installing SAP ASE Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2 New SAP ASE Release Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3 Special Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Cross-Platform Loading of an Encrypted Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrade and Runtime Logging Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Avoiding Text and Image Problems with SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3 Known Installation Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

4 Known Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

5 Known Issues for SAP ASE Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6 Documentation Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6.1 Documentation for New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2

P U B L I C

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

Release Bulletin for HP-UX

Content

Page 3: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 3/20

1 Product Summary

This release bulletin provides late-breaking information about SAP Adaptive Server Enterprise (SAP ASE)

version 16.0 SP02.

1.1 Interoperability

Learn about interoperability of SAP ASE against other SAP products versions and client products.

For information about platform support for SAP ASE and other products, see SAP Product Availability Matrix

(PAM) .

The following information is published regularly on PAM:

● Release type (for example, standard release, early adoption release, or custom development project

release)

● Planned availability

● Maintenance durations

● Upgrade paths

● Platform availability, including database platforms and operating systems

Table 1: Interoperability of SAP ASE against other SAP products and client versions

Client Name Version

SAP Open Client™/SAP Open Server™ 15.7, 16.0

15.5

SAP Adaptive Server Enterprise Extension Module for Python 15.7, 16.0

SAP Adaptive Server Enterprise Extension Module for PHP 15.7, 16.0

SAP Adaptive Server Enterprise Database Driver for PERL 15.7, 16.0

SAP jConnect™ for JDBC 7.0.x, 16.0

SAP ASE ODBC Driver 15.7, 16.0

15.5.x

SAP ASE OLE DB Provider 15.7, 15.5.x

ADO.NET 2.x, 4.x, 16.0

SAP Replication Server 15.7, 15.7.1, 15.7.1 SP100,

15.7.1 SP200, 15.7.1 SP300

15.5, 15.6

Release Bulletin for HP-UX

Product Summary

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

Page 4: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 4/20

Table 2: Plug In Support

Plug In Name Version

SAP Adaptive Server Cockpit 16.0 SP02

SAP Control Center

Note

You can access previously collected and archived statistics, however features or func

tionality introduced in 16.0 SP02 are not supported.

3.3

1.2 SAP Adaptive Server Enterprise Cockpit

SAP ASE cockpit is a new graphical administration tool for on-board management and monitoring of SAP ASE.

SAP ASE cockpit provides availability monitoring, historical monitoring, and real-time monitoring in a scalable

Web application. It offers real-time alerts of availability, performance, and capacity issues, and intelligent tools

for spotting performance and usage trends. Availability, performance, and capacity alerts are configured and

enabled by default.

Unlike SAP Control Center, SAP ASE cockpit is designed as an on-board management solution, where you

install the cockpit on each SAP ASE host to manage and monitor that system.

The documentation for the SAP ASE cockpit is available only through the SAP Help Portal: SAP Adaptive

Server Enterprise Cockpit

Note

Previous plug-in versions supported a local version of the documentation which was installed along with the

software image. SAP ASE versions 16.0 SP02 and later do not support locally installed documentation.

1.3 Database Always-On (HADR) Platform Support

See Prerequisites, Restrictions, and Recommendations in the HADR Users Guide for information about

platform support.

Related Information

HADR Users Guide

4

P U B L I C

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

Release Bulletin for HP-UX

Product Summary

Page 5: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 5/20

1.4 Product Compatibility

Learn about SAP ASE compatibility with earlier versions of SAP ASE, and with other SAP products.

Compatibility of Fixes with Previous SAP ASE Releases

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

● 15.7 SP63 and older

● 15.7 SP100 to SP104

● 15.7 SP110 to SP111

● 15.7 SP121 to SP122

● 15.7 SP130 to SP135

● 16.0 to 16.0 PL05

● 16.0 SP01 to 16.0 SP01 PL02

Password Compatibility with Replication Server

You can replicate logins from SAP ASE version 15.0.2 and later to earlier server versions only during the

password downgrade period when allow password downgrade is set to 1.

You cannot replicate roles with passwords from SAP ASE 15.7 and later to earlier server versions.

Release Bulletin for HP-UX

Product Summary

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

Page 6: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 6/20

2 Installation and Configuration

Get last-minute information about installation, configuration, and upgrading and downgrading that was

omitted from your installation guide, or that needs special emphasis.

Caution

SAP recommends that you do not install an older version of an SAP product in a $SYBASE directory that

includes a newer SAP product.

2.1 Installing SAP ASE Cockpit

Special installation instructions for SAP ASE Cockpit.

SAP ASE Cockpit

SAP ASE cockpit is installed as part of an SAP ASE server installation and runs on the same host as the SAPASE server. SAP ASE cockpit provides on-board capabilities to manage and monitor SAP ASE servers which

are running on the same host.

It is possible to continue to run SCC 3.x on your system (allowing you access to previously collected and

archived statistics), but SCC does not recognize any features or functionality introduced in 16.0 SP02.

For more information about the SAP ASE cockpit, see the SAP Adaptive Server Enterprise Cockpit

documentation.

For information about installing the SAP ASE cockpit, see the Installation Guide for your platform.

6

P U B L I C

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

Release Bulletin for HP-UX

Installation and Configuration

Page 7: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 7/20

2.2 New SAP ASE Release Directory

The COCKPIT-4 release directory is new for 16.0 SP02. This directory supports the new SAP ASE cockpit

graphical administration tool for on-board management and monitoring of SAP ASE.

2.3 Special Upgrade Instructions

Get last-minute instructions for upgrading and migrating SAP ASE.

2.3.1 Cross-Platform Loading of an Encrypted Database

Cross-platform loading of an encrypted database dump is not supported in version SAP ASE 16.0 and later.

2.3.2 Upgrade and Runtime Logging Enhancements

To improve the performance of runtime logging, SAP recommends that you use the SAP ASE queuingstrategy.

If you create a new server installation that does not use an existing configuration file, SAP ASE creates a

configuration file that sets the user log cache queue size and user log cache size parameters to

DEFAULT.

As a result, in version 16.0 and later, SAP ASE enables queuing strategy for log records because it is assumed

that the default value for user log cache queue size is set to 1, and that user log cache size is set

to 4 times the server page size.

The queuing strategy for log records requires that the user log cache size configuration parameter is at

least 4 times the server page size. If you are upgrading an installation to version 16.0, the preupgrade utility willreport the following error if user log cache size is less than 4 times the server page size:

***ERROR: configuration parameter 'user log cache size' is toolow for upgrade. It is <size>, but must be at least <minimum size>.

Ensure that user log cache size has been set to at least 4 times the server page size to allow the upgrade

to continue.

Unless you have a specific reason not to, SAP recommends that you use the queuing strategy to improve the

performance of runtime logging. If you do not want to enable the queuing strategy, then after the installation

has been successfully upgraded to 16.0, change user log cache queue size to 0. The user log cache

size parameter can be set to any multiple of the server page size (it is not restricted to a minimum of 4 times

the server page size), if user log cache queue size is set to 0.

Release Bulletin for HP-UX

Installation and Configuration

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 7

Page 8: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 8/20

2.3.3 Avoiding Text and Image Problems with SAP ASE

Databases that contain text or image columns from versions of SAP ASE earlier than 12.0 are known to have

garbage flags in the text/image status area on text/image pages. These garbage flags may cause errors or

data corruption after you upgrade the database to later versions.

Determine Whether the Database Contains Text or Image Columns

Determine whether the earlier-than-12.0 database contains text or image columns. These column types are

indicated in the system table syscolumns with a value of 34 for image and 35 for text. If the database does

not contain text or image columns, no further steps are needed.

Find Errors and Possible Corruption

If the database does contain text or image columns, follow these steps to determine if there are errors and

possible corruption.

1. Execute:

1> use <database_name> 2> go1> select name from sysobjects where id in

2> (select id from syscolumns where type = 34 or type = 35)3> go 

2. Using the latest SAP ASE version, run the following on each database to detect garbage flags:

1> dbcc checkdb(dbname, skip_ncindex) 2> go

If dbcc checkdb reports 12918 errors as shown below, the database contains garbage flags and must be

fixed. If the database does not report these types of errors, no further steps are needed.

Flags (0x%x) in Text/Image/Unitext Page Status Area on text page %u(partition id %d) does not match the attribute of text pagechain starting from page %u. Run DBCC REBUILD_TEXT to fix it.

Fixing Garbage Flags on a Database Where a Cross-Platform Dump and Load

Has Not Been Performed

If the database contains garbage flags, and you have never performed a cross-platform dump and load on the

database, correct the garbage flags by executing the appropriate command.

● If error 12918 is reported for several tables, correct garbage flags for all tables in a database by executing.

dbcc rebuild_text(‘all’)

8

P U B L I C

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

Release Bulletin for HP-UX

Installation and Configuration

Page 9: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 9/20

● If error 12918 is reported for a limited number of tables, correct garbage flags on specified tables by

executing:

dbcc rebuild_text(‘table_name’)

● If error 12918 is reported for only one table, correct garbage flags on the specified columns in a table by

executing:

dbcc rebuild_text(‘table_name’, ‘column_name’)

Fixing Garbage Flags on a Database Where a Cross-Platform Dump and Load

Has Been Performed

Note

In 15.7 SP110 or later, this issue has been fixed and a cross-platform database load does not corrupt text or

image data even if there are garbage flags.

● If the database contains garbage flags and you have performed a cross-platform database load on either:

○ Version 15.0 ESD#2 or later, but before version 15.0.2, or,

○ Version 15.0.2 or later, and the source database version (the version on the source platform where the

dump file was generated) is 15.0 or later,

Then run dbcc rebuild_text with the repairtext option. The repairtext is the 5th parameter andshould be set to a value of 1. For example:

dbcc rebuild_text(‘all’ | ‘table_name’, ‘column_name’ | null, null, null, 1)

The repairtext option repairs corrupted text and image data caused during a cross-platform database

load by garbage flags. This repairtext option prints each page number in the error log for the text/

image data that is repaired.

Note

If you run the dbcc rebuild_text command with the repairtext option on a database that

contains garbage flags but on which a cross-platform database load was never performed, or if a cross-platform database load was performed on a version 15.0.2 or later from a source database version prior

to 15.0, this command will corrupt correct text and image data by byte-swap. Make sure you are aware

of the version on which a cross-platform database load was performed and the source database

version.

● If the cross-platform database load was performed on 15.0.2 or later (12.5.3, or 12.5.4) and the source

database version (the version on the source platform where the dump file was generated), is earlier than

15.0 (for example 12.5, or 12.5.3), correct the garbage flags by executing the appropriate command.

○ If error 12918 is reported for several tables, correct garbage flags for all tables in a database by

executing:

dbcc rebuild_text(‘all’)

Release Bulletin for HP-UX

Installation and Configuration

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 9

Page 10: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 10/20

○ If error 12918 is reported for a limited number of tables, correct garbage flags on specified tables by

executing:

dbcc rebuild_text(‘table_name’)

○ If error 12918 is reported for only one table, correct garbage flags on the specified columns in a table

by executing:

dbcc rebuild_text(‘table_name’, ‘column_name’)

10

P U B L I C

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

Release Bulletin for HP-UX

Installation and Configuration

Page 11: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 11/20

3 Known Installation Issues for SAP ASE

Learn about known installer issues and workarounds. Known issues are listed in descending order of Change

Request (CR) numbers.

CR # Description

788612 For an HADR installation, there is no option to specify a port number for rssd_port and

rssd_ra_port.

By default, the ports rssd_port and rssd_ra_port are an increase of one from the base SRS port.

This may lead to an install error if the ports are occupied, or they are specified for another purpose.

Workaround: When specifying the SRS ports in during an HADR installation, make sure the next two port

numbers (+1 and +2) are also available for use. The HADR setup will use those port numbers for the RSSD

and RSSD_SA ports.

692496 When installing an SAP ASE server to be used in an HA configuration, the sp_companion stored proce

dure configure command may fail due to duplicate device names for the tempdbdev logical device.

Workaround: Do not specify the "Tempdb Device" (set the value of this field to blank) when configuring the

secondary server during SAP ASE installation.

● 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 thetempdb 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.

588793 You may experience incompatibility issues when installing SAP ASE 15.5 and later versions that use

Install Anywhere on older directories that have been installed with InstallShield Multiplatform.

These issues occur when using products installed with different installer technologies:

● If you install products using Install Anywhere or InstallShield Multiplatform on top of a product instal

led using a different installer, the same files included in both installers are silently overwritten by the

later installation.

● If you run either the Install Anywhere or InstallShield Multiplatformuninstaller

, the same files in

stalled by both installers are removed without any error messages.

Workaround: Do not install products that use Install Anywhere and products that use InstallShield Multi

platform in the same directory.

Release Bulletin for HP-UX

Known Installation Issues for SAP ASE

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

Page 12: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 12/20

4 Known Issues for SAP ASE

Learn about known issues and workarounds. Known issues are listed in descending order of Change Request

(CR) numbers.

CR # Description

789356 The Workload Analyzer capture feature will not capture workload sessions if the client connections do

not define the application name connection property.

Workaround: Define an application name for all connections in the application.

788942 The following 644 error may be reported against a latch free index created for a large table which has

many duplicate keys.

Index row entry for data row id <row_id> is missing from index page<page_no>of index id <index_id> of table <table_name> in database <db_name>.Xactid is <trans_id>. Drop and re-create the index.

Workaround: Drop and re-create the index.

788898 The execution of DBCC CHECKSTORAGE on the master database may mistakenly report the faults

100009, 100029, and 100030 on the table sysanchors.

Workaround: Faults 100009, 100029, and 100030 on table sysanchors can be ignored.

788861 In an HADR cluster, if granular permission is enabled, replication may stop with a DSI reporting per

mission error such as: "ERROR #1028 DSI EXEC"

This is due to the error:

Message: 10330 'INSERT permission denied on object ... .'

Workaround: After the HADR cluster is configured, if granular permissions is to be enabled, grant the fol

lowing roles on the primary SAP ASE server (that server will be replicated to the companion SAP ASE

server):

● grant role replication_maint_role_gp to DR_maint

● grant role hadr_admin_role_gp to DR_admin

If the above roles were not granted before enabling granular permission in an HADR cluster, and replication

stops with the above error message, then login to the companion SAP ASE server as usersa and grant the

above roles, then resume DSI on the remote replication server using the command:

resume connection to <CompanionServer>.<dbname>

Where <CompanionServer> is the SAP ASE server name of the companion node and <dbname> is the

database that encountered the error.

After this, login to the primary SAP ASE as user sa and grant the above roles.

12

P U B L I C

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

Release Bulletin for HP-UX

Known Issues for SAP ASE

Page 13: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 13/20

CR # Description

788609 If the buffer size is not sufficient, performing a full database encryption returns error 2956.

Workaround: Configure the buffer pool size associated with the database with enough space to allow SAP

ASE to perform a full database encryption.

788128 For the Workload Analyzer option, the value of the default network packet size configura

tion parameter on the replay server must be greater than or equal to 1024.

This requirement is due to the fact that, during replay, there is a need to create login packets for the con

nections involved in the replay process. The size of the login packet that is created is 608 bytes. This is only

used on the replay server.

Workaround: Set the value of the default network packet size to 1024 or greater.

787897 The Workload Capture analysis might fail when you turn on dbcc workload_capture parameter full_response to capture all TDS data for a batch query.

This issue is caused by too many responses for the batch query.

Workaround: Turn off the full_response option when capturing a workload.

787759 During a planned fail over on an HADR cluster, client connections are not disconnected and therefore

remain on the old primary server.

Rather than failing over to the new primary server, the following message is returned:

Msg 2379, The primary server has been successfully deactivated.

Workaround: To resolve this issue, do one of the following:

● Shutdown or kill the previous primary server when a new primary is established.

● Kill the SPIDs on the SAP ASE server for non-privilege connections that persist after a new primary is

established.

787024 When SAP ASE RepAgent is configured for stream replication in synchronous mode, the primary data

base may run out of log space if most of the activity in this database is performed on non-replicated

objects.

Workaround: Extend the log and generate activity on replicated tables.

786637 When using job scheduler templates for scheduling jobs, you will receive a message that the job failed,

even in situations where the job was successful.

Workaround: View the job status by using sp_sjobhistory to view the history in the js_output ta

ble.

785064 When executing the sap_teardown command, the system may incorrectly indicate the tear down was

successful.

When you submit the sap_teardown command after a failed HADR replication system setup, the Repli

cation Server process may not be properly cleaned up from the system.

Workaround: Check for, and kill Replication Server processes on both primary and standby systems.

Release Bulletin for HP-UX

Known Issues for SAP ASE

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 13

Page 14: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 14/20

CR # Description

783753 In some circumstances an error is reported to the errorlog when RepAgent is configured forstream

replication.

The following error might be printed repeatedly, indicating that RepAgent is unable to continue sending

data to Replication Server.

Package buffer depleted index <value> max <value> size <value>

Workaround: Increase the RepAgent configuration parameterstream buffer size from the default

value to 1572864. For example:

1. sp_stop_repagent <dbname> <dbname>

2. use <dbname>

3. sp_config_rep_agent <dbname>, 'stream buffer size', '1572864'

4. sp_start_repagent <dbname>

783376 There is a small window of potentially lost data if an SAP ASE server crashes and the RepAgent was in

the the process of switching from synchronous to asynchronous mode in stream replication.

When the primary SAP ASE server in an HADR cluster is no longer responding, the fault manager detects

this situation and triggers a failover. However, there is a potentially for lost data if the server is not respond

ing between the time when RepAgent is switching from synchronous to asynchronous mode in stream rep

lication during an automatic failover, and the time this switch is communicated to Replication Server.

Workaround: None.

764250 Using ddl in tran in either synchronous or near-synchronous replication while changing objects in a

single transaction can cause the transaction to hang.

The following batch transaction is an example of this issue. A table is created and its schema is also

changed under the same transaction. The transaction as well as the Replication Agent task for the given

database hangs.

begin transaction gocreate table foo …goinsert foo ... values …go

alter table foo …go 

Workaround: None.

741918 Java applications fail to start using SAP JRE7.

Java applications, such as sybdiag, which run using SAP JRE may encounter the error:A fatal

exception has occurred. This error is caused by exceeding the number of possible semaphores on

the machine running the Java application.

Workaround: Use the ipcrm utility to terminate semaphores, for example, ipcrm –s <semid>, or re

start the machine.

14

P U B L I C

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

Release Bulletin for HP-UX

Known Issues for SAP ASE

Page 15: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 15/20

CR # Description

695625 Confidentiality service causes error.

This message is reported by Open Client applications connecting to SAP ASE:

ct_send(): network packet layer: internal Client Library error: State

error: trying to write when 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.

684556 The select for update semantics introduced in version 15.7 do not support datapages-locked tables.

Workaround: None. select for update support exists only for datarows-locked pages.

664550 Kerberos authentication for remote connections fail after configuring high availability.

If the ID of any server gets changed after configuring high availability (HA) with SAP ASE, you may experi

ence issues with Kerberos authentication for remote connections to those servers with IDs that have

changed.

Workaround: Restart the SAP ASE server.

595923 Known issues with transfer table.

● When creating a unique index that uses the ignore_dup_key property, importing a row with a key

that is already present in the table 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 statement, since in those cases, the row

is discarded, and the transaction continues.● When an insert trigger exists, the trigger is not fired when data is inserted throughtransfer

table...from.

Workaround: None.

589269 SAP ASE may stop responding during start-up.

If you are using the in-memory database or relaxed-durability database feature, SAP ASE may run into a

timeslice error during start-up if it cannot access the license server as it starts.

Workaround: Make sure SAP ASE can access the license server.

587828 Cannot disable RMI socket operations using pca_jvm_netio.

RMI sockets continue to function, even if you have either manually disabled them, or executed:

 sp_jreconfig "disable", "pca_jvm_netio"

Consequently, a Java RMI client continues to connect to a remote RMI server to execute functionality over

the network.

Workaround: Remove any unused RMI classes from the database. By default, pca_jvm_netio is ena

bled.

Release Bulletin for HP-UX

Known Issues for SAP ASE

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 15

Page 16: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 16/20

CR # Description

580614 A single-engine SAP ASE may stop responding when, after performing a Java task, additional engines

are manually brought online.

While running on a single engine, SAP ASE may either stop responding, or cause connected clients to block

indefinitely, generate a stack trace, or not process when the server performs a task that uses Java, as soon

as additional engines are manually brought online. This is caused be an issue with the HP-UX commercial

off-the-shelf Java Virtual Machine.

Workaround: Always have a minimum of two engines configured when starting SAP ASE; this allows the

HP-UX commercial off-the-shelf JVM to automatically target the highest engine number available.

In addition, do not set any configuration options in SAP ASE that target engine 0 for the HP-UX commercial

off-the-shelf JVM.

546787 Due to a known issue in HP-UX, creating a file using the Java in the database feature fails unless the

working directory permission mask is set to 0777 or equivalent.

Workaround: Set the mask on the working directory to 0777. (This is not the same as the physical direc

tory permissions in the file system. The physical directory can have any permissions mask that is appropri

ate for that directory.) This setting is only for the sybpcidb configuration properties, where you can con

figure a working directory with a mask that allows or prevents certain actions from within the JVM. Apply

the mask using either an add command or an update command. For example:

sp_jreconfig 'add', pca_jvm_work_dir, '/some/path(ugo=rwx)'

or:

sp_jreconfig 'update', pca_jvm_work_dir, '/old/path', '/newpath(ugo=rwx)'

16

P U B L I C

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

Release Bulletin for HP-UX

Known Issues for SAP ASE

Page 17: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 17/20

5 Known Issues for SAP ASE Cockpit

Descriptions of known issues, workarounds, and restrictions for SAP ASE cockpit. Find Issues by Change

Request (CR) numbers.

CR # Description

788772 Replay for the Workload Analyzer option in SAP ASE cockpit may fail for connections within the work

load that were already established at the time that the original workload was captured.

When this occurs, the following message will appear in the Replay Wizard Replay Status screen:

WARN: Failed to receive data from server for session XError messages reporting java.net.SocketException: Connection reset will be found in

the agent.log file for the SAP ASE cockpit server.

Workaround: Start workload capture on the SAP ASE server before any clients connect to the server.

788435 Updating table statistics fails from the SAP ASE cockpit.

Workaround: Use the isql utility to run the update statistics command for a table.

787775 After an unplanned failover, the SAP ASE cockpit HADR dashboard for the old primary server may not

be able to refresh, causing the dashboard to become blank.

Workaround: Do one of the following:

● Use the new primary’s HADR dashboard.

● In order to resolve the issue of the blank HADR dashboard on the new primary, restart the SAP ASE

cockpit server on the new primary.

787519 An error is raised after installation indicating that registering the ASE Agent Plug-in failed.

If you choose to install SAP ASE using the Japanese language platform and then choose the option Enable

Monitoring, you will see an error at the end of the installation indicating that the registration of the ASE

Agent Plug-in inside SAP ASE cockpit failed. This does not impact SAP ASE or the SAP ASE cockpit installa

tion, but it does impact the registration of ASE Agent Plug-in.

Workaround: Manually register the ASE Agent Plug-in after the installation is complete. See Registering and

 Authenticating an SAP ASE Cockpit Agent, in the SAP ASE Cockpit documentation.

Release Bulletin for HP-UX

Known Issues for SAP ASE Cockpit

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 17

Page 18: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 18/20

6 Documentation Updates

Read about updates, corrections, and clarifications to the documentation released with SAP ASE .

6.1 Documentation for New Features

New and changed features are now described in the What's New document. The New Features Guide has been

deprecated.

18

P U B L I C

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

Release Bulletin for HP-UX

Documentation Updates

Page 19: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 19/20

Important Disclaimers and Legal Information

Coding Samples

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system

environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and

completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP

intentionally or by SAP's gross negligence.

Accessibility

The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be

a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however,

does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of

SAP.

Gender-Neutral Language

As far as possible, SAP do cumentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as

"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided o r a gender-neutral noun

does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does

not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any

damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for

transparency (see: http://help.sap.com/disclaimer).

Release Bulletin for HP-UX

Important Disclaimers and Legal Information

P U B L I C

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 19

Page 20: SAP ASE Release Bulletin HP En

7/21/2019 SAP ASE Release Bulletin HP En

http://slidepdf.com/reader/full/sap-ase-release-bulletin-hp-en 20/20

www.sap.com/contactsap

© 2015 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 wellas their respective logos are trademarks or registered trademarks

of SAP SE (or an SAP affiliate c ompany) in Germany and other

countries. All other product and service names mentioned are the

trademarks of their respective companies.

Please see http://www.sap.com/corporate-en/legal/copyright/