SAP ASE Release Bulletin Linux En

PUBLIC

SAP Adaptive Server Enterprise 16.0 SP02Document Version: 1.1 – 2015-09-03

Release Bulletin for Linux

Content

1 Product Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 SAP Adaptive Server Enterprise Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.3 Database Always-On (HADR) Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Product Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Installing SAP ASE Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 New SAP ASE Release Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 Special Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Cross-Platform Loading of an Encrypted Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Upgrade and Runtime Logging Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Avoiding Text and Image Problems with SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

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

4 Known Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

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

6 Documentation Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246.1 Documentation for New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

2P U B L I C© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Release Bulletin for LinuxContent

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 LinuxProduct Summary

P U B L I C© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

http://help.sap.com/disclaimer?site=https://apps.support.sap.com/sap/support/pam

http://help.sap.com/disclaimer?site=https://apps.support.sap.com/sap/support/pam

Table 2: Plug In Support

Plug In Name Version

SAP Adaptive Server Cockpit 16.0 SP02

SAP Control Center

NoteYou can access previously collected and archived statistics, however features or functionality 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

NotePrevious 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



http://help.sap.com/Download/Multimedia/zip-ase1602/SAP_ASE_Cockpit_en.pdf


http://help.sap.com/Download/Multimedia/zip-ase1602/SAP_ASE_Database_Always_On_Users_Guide_en.pdf

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.



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.

CautionSAP 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 SAP ASE 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.


Release Bulletin for LinuxInstallation and Configuration


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 queuing strategy.

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 will report 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 too low 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.



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 in2> (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 page chain 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’)



● 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

NoteIn 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 and should 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.

NoteIf 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’)



○ 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’)



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

671351 Installing SAP ASE 16.0 on top of SAP Replication Agent 15.2 causes SySAM errors.

Workaround: Before installing SAP ASE 16.0, modify the SySAM file permissions to include write permissions.

625837 You cannot share a machine-level license from different Linux PowerPC operating systems on IBM logical partitions.

The machine ID for Linux PowerPCs on IBM logical partitions is the virtual machine's MAC address, which means that SySAM cannot identify a unique machine ID for Linux on IBM logical partitions.

Workaround: None. You cannot share a machine license between different operating systems.

Release Bulletin for LinuxKnown Installation Issues for SAP ASE


CR # Description

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 installed 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 Multiplatform uninstaller, the same files installed by both installers are removed without any error messages.

Workaround: Do not install products that use Install Anywhere and products that use InstallShield Multiplatform in the same directory.


Release Bulletin for LinuxKnown Installation Issues for SAP ASE

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 permission 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 following 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 user sa 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.

Release Bulletin for LinuxKnown Issues for SAP ASE


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 configuration 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 connections 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 database 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.



CR # Description

786984 Attaching SAP ASE to a large piece of shared memory may fail.

You may experience problems when attempting to start SAP ASE on RHEL with a large data cache (less than total available memory on the machine). Doing so creates a large shared memory segment which can fail to attach, producing the following error in the errorlog: Cannot attach shared memory : error = 22 (Invalid argument) os_create_region: shmat(251461637): Invalid argument .

NoteThe server will start without any issues if the amount of data cache is reduced.

This issue is due to a utility called prelink, which is shipped with RHEL. The prelink utility prelinks shared libraries and binaries for quicker startup. Without prelink, glibc and all the system libraries get loaded in the higher address range(~ 0x7f0000000000), which is out of the range of the SAP ASE end-of-heap, allowing of room for its shared memory area. However, with prelink, the system's libraries are prelinked to load in the lower address range(~ 0x3000000000), which is in the range of the SAP ASE shared memory area. To see if prelink is installed, enter:

rpm -qa | grep prelink

Workaround: Follow these steps to workaround the issue:

1. Determine the SAP ASE process ID.

ps -afe | grep dataserver

or

pidof dataserver

2. View the memory map for the SAP ASE process.

cat /proc/<pid>/maps For example: … 3241800000-324198a000 r-xp 00000000 08:03 2753009 /lib64/libc-2.12.so …

3. Shutdown the SAP ASE server.

4. Edit the prelink configuration file as root user.

sudo vim /etc/sysconfig/prelink

5. Change the following in the file: PRELINKING=yes to PRELINKING=no .

6. Run prelink as root user.

sudo prelink –ua



CR # Description

NoteAlternatively, you can manually run /etc/cron.daily/prelink as root user.

7. Restart SAP ASE.

8. Verify that the memory map for SAP ASE shows the system libraries such as libc are loaded high in the address space.

cat /proc/<pid>/maps For example: … 7ffff7a4a000-7ffff7bd4000 r-xp 00000000 08:03 2752928 /lib64/libc-2.12.so …

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

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

783753 In some circumstances an error is reported to the errorlog when RepAgent is configured for stream 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 parameter stream 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>



CR # Description

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 responding between the time when RepAgent is switching from synchronous to asynchronous mode in stream replication during an automatic failover, and the time this switch is communicated to Replication Server.

Workaround: None.



CR # Description

771972 SuSE Enterprise 11.0 (and Patchlevels) only - Under some network setup, SAP ASE may crash when it tries to boot strap the PCA/JVM and while needing to retrieve ‘userid’ and ‘password’ information from the Name Service Switch layer (NSS).

If the userid and password information is serviced by the Network Information Service layer (NIS) under NSS then the SAP ASE crash may occur. This problem is due to a known run-time problem in Suse SLES 11 and is tracked under Suse BugID 607530 (duplicate of Suse BugID 477061). The root cause of this problem is a rogue call to free(3) for a non-existent memory pointer. An SAP ASE crash will typically report the below information.

======= Backtrace: ========= /lib64/libc.so.6(+0x75358)[0x7ffff68fd358]/lib64/libc.so.6(cfree+0x6c)[0x7ffff69022fc]/lib64/libnss_nis.so.2(_nss_nis_getpwuid_r+0xf1)[0x7ffff0f4a001]/lib64/libnss_compat.so.2(+0x2ab8)[0x7ffff1152ab8]/lib64/libnss_compat.so.2(+0x2ca6)[0x7ffff1152ca6]/lib64/libnss_compat.so.2(_nss_compat_getpwuid_r+0x100)[0x7ffff1153020]/lib64/libc.so.6(getpwuid_r+0xec)[0x7ffff692cc1c]

Workaround: To avoid this problem, follow the suggestions below:

● Use Suse SLES 12 or OpenSuse 11 where the Suse BugID 607530 is fixed.● Use RedHat RHEL 6 or RHEL 7 where this problem is not exposed.● Use Suse SLES 11 but fully disable the run-time component of NSS that causes the problem to mani

fest, namely NIS. Refer to your system administration reference guide for disabling NIS.

To diminish the likelihood of this problem by limiting NIS lookups and while using Suse SLES 11, follow the suggestions below:

● Add the userid and groupid values, under which SAP ASE is started, in the /etc/passwd, /etc/shadow and /etc/group files. You can find these values using the below ypmatch commands.

% ypmatch `whoami` passwd % ypmatch `groups` group

● Add all the hostnames and hostaddresses where SAP ASE may need to connect in the /etc/hosts file. You can find their values using the below ypcat command.

% ypcat hosts

● Disable the NIS lookups for the passwd:, group:, and hosts: directives in the /etc/nsswitch.conf file (remove nis from the following lines):

passwd: files nis vas4 group: files nis vas4 hosts: files dns nis



CR # Description

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 …goalter 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 restart the machine.

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 experience issues with Kerberos authentication for remote connections to those servers with IDs that have changed.

Workaround: Restart the SAP ASE server.



CR # Description

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 through transfer 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.



CR # Description

578921 (SuSE Enterprise 11.0 (and Patchlevels) only) Under some network setups, SAP ASE may crash when it tries to boot strap the PCA/JVM and while needing to retrieve userid and password information from the Name Service Switch layer (NSS).

If the information is serviced by the Network Information Service layer (NIS) under NSS, then the SAP ASE crash may occur. This problem is due to a known run-time problem in Suse SLES 11 and is tracked under Suse BugID 607530 (duplicate of Suse BugID 477061). The root cause of this problem is a rogue call to free(3) for a non-existent memory pointer. An SAP ASE crash will typically report the below information:

======= Backtrace: ========= /lib64/libc.so.6(+0x75358)[0x7ffff68fd358]/lib64/libc.so.6(cfree+0x6c)[0x7ffff69022fc]/lib64/libnss_nis.so.2(_nss_nis_getpwuid_r+0xf1)[0x7ffff0f4a001]/lib64/libnss_compat.so.2(+0x2ab8)[0x7ffff1152ab8]/lib64/libnss_compat.so.2(+0x2ca6)[0x7ffff1152ca6]/lib64/libnss_compat.so.2(_nss_compat_getpwuid_r+0x100)[0x7ffff1153020]/lib64/libc.so.6(getpwuid_r+0xec)[0x7ffff692cc1c]

Workaround: To avoid this problem, follow these suggestions:

● Use Suse SLES 12 or OpenSuse 11 where the Suse BugID 607530 is fixed.● Use RedHat RHEL 6 or RHEL 7 where this problem is not exposed.● Use Suse SLES 11 but fully disable the run-time component of NSS that causes the problem to mani

fest, namely NIS. Please refer to your system administration reference guide for disabling NIS.

To diminish the likelihood of encountering this problem by limiting NIS lookups and while using Suse SLES 11, follow these suggestions:

● Add the userid and groupid values under which SAP ASE is started in the /etc/passwd, /etc/shadow and /etc/group files.You can find these values using the ypmatch commands:

○ % ypmatch whoami passwd○ % ypmatch groups group

● Add all the hostname and hostaddresses where SAP ASE may need to connect in the /etc/hosts file. You can find these values using the ypcat command:

○ % ypcat hosts● Disable the NIS lookups for the passwd:, group:, and hosts: directives in the /etc/

nsswitch.conf file by removing nis from the these lines:

○ passwd: files nis vas4 ○ group: files nis vas4 ○ hosts: files dns nis



CR # Description

576652 SySAM2-enabled products incorrectly determine the number of cores and chips on quad-core processors.

This may be as a result of your SAP ASE small business edition or chip license not being activated and having gone into a grace period.

Workaround: Remove this line from your SySAM properties file, if it exists:

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.

558020 dsedit fails with translation table syntax errors.

When you try to enter a new server entry or a port number, the dsedit utility fails and displays parsing errors similar to:

Warning: translation table syntax error: Unknown keysym name: osfActivate. Warning: ... found while parsing ':<Key>osfActivate: ManagerParentActivate()'. Warning: String to TranslationTable conversion encountered errors. Warning: translation table syntax error: Unknown keysym name: osfBeginLine. Warning: ... found while parsing ':<Key>osfBeginLine: ManagerGadgetTraverseHome()'

These errors indicate that the X-server program that renders graphics is not cached or set up as the default for the environment.

Workaround: Set the environment variable XKEYSYMDB:

% setenv XKEYSYMDB “/usr/share/X11/XKeysymDB”



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 workload 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 installation, 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 LinuxKnown Issues for SAP ASE Cockpit


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.


Release Bulletin for LinuxDocumentation Updates

Important Disclaimers and Legal Information

Coding SamplesAny 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.

AccessibilityThe 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 LanguageAs far as possible, SAP documentation 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 or 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 HyperlinksThe 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 LinuxImportant Disclaimers and Legal Information


http://help.sap.com/disclaimer/

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 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 http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

SAP ASE Release Bulletin Linux En

Documents

Transcript of SAP ASE Release Bulletin Linux En