SAP Adaptive Enterprise 16.0 - Release Bulletin For HP-UX

SAP Adaptive Server Enterprise
Document Version: 16.0 - 2014-09-19
Release Bulletin for HP-UX
Table of Contents
1
Release Bulletin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Product Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1
Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2
Product Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3
2.2.1
Compatibility of Fixes with Previous SAP ASE Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
2.2.2
Password Compatibility with Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Changes That Affect Existing Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3.1
FIPS Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.2
SDK for SAP ASE and PC Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.3
Behavior Change for When Triggers are Fired. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.4
Changes to Plan Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
2.3.5
Location for Utilities and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.6
Changes for SAP ASE Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.7
Backup Server and IBM Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1
Special Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1.1
Release Directory Structure Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
3.1.2
Installing Enterprise Connect Data Access (ECDA) or MainframeConnect DirectConnect for
z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2
Special Configuration Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.2.1
3.3
Manage Permissions of Remote Hosts That Access Backup Server. . . . . . . . . . . . . . . . . . . . 12
Special Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.3.1
Compare Configuration Parameters Before and After an Upgrade. . . . . . . . . . . . . . . . . . . . . 12
3.3.2
Cross-Platform Loading of an Encrypted Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3.3
Upgrade and Runtime Logging Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3.4
Avoiding Text and Image Problems with SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3.5
Loading Database Dumps into Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4
Known Installation Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Known Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Documentation Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1
Database Encryption Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2
Job Scheduler Parameter job scheduler interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3
Job Scheduler Command sp_sjobdrop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4
Security Built-in Function Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.5
Shareable Temporary Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.6
Hash-Based Update Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2014 SAP SE or an SAP affiliate company. All rights reserved.

Table of Contents
5.7
Values for lock timeout pipe active. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.8
dbcc page Parameter logical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.9
Behavior of Concurrent DDLs and reorg defrag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Obtaining Help and Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.1
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2
Downloading Product Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3
Product and Component Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.4
Accessibility Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table of Contents
Release Bulletin
SAP Adaptive Server Enterprise is a high-performance relational database management system for missioncritical, data-intensive environments. It ensures highest operational efficiency and throughput on a broad range of
platforms.

Release Bulletin
Product Summary
This release bulletin provides late-breaking information about SAP Adaptive Server Enterprise (ASE) version
16.0. A more recent version may be available on the Web.
2.1
Interoperability
Interoperability of SAP ASE against other SAP products, across different platforms, versions, and client
products.
Interoperability between big-endian and little-endian platforms has been verified. Windows, Linux x86-32, Linux
x86-64, Solaris x86-32, and Solaris x86-64 are little-endian platforms. IBM AIX, Linux on Power, Solaris SPARC,
and HP-UX on Itanium are big-endian platforms.
Table 1: Supported Client Platforms for SAP ASE
Client Name
Version
Supported Platform
SAP Open Client/SAP Open

Server
15.7, 16.0
AIX 32-bit
AIX 64-bit
HP-UX IA 32-bit
HP-UX IA 64-bit
Linux x86 32-bit
Linux x86-64 64-bit
Linux Pseries 32-bit
Solaris SPARC 32-bit
Solaris x86 32-bit
Solaris x86-64 64-bit
Windows x86 32-bit
Windows x86-64 64-bit

Product Summary
Client Name
Version
Supported Platform
15.5
AIX 32-bit
AIX 64-bit
HP-UX 32-bit
HP-UX 64-bit
15.7, 16.0
Extension Module for Python
15.7, 16.0
Extension Module for PHP
15.7, 16.0
Database Driver for PERL
SAP jConnect for JDBC
7.0.x, 16.0
HP-UX IA 32-bit
HP-UX IA 64-bit
Linux x86 32-bit
Linux x86-64 64-bit
Solaris x86 32-bit
Mac OS X Intel 32-bit
Windows x86 32-bit
AIX 64-bit
HP-UX IA 64-bit
Linux x86-64 64-bit
AIX 64-bit
HP-UX IA 64-bit
Linux x86-64 64-bit
AIX 32-bit
HP-UX IA 32-bit
Linux x86-64 64-bit
All

Product Summary
Client Name
Version
Supported Platform
SAP ASE ODBC Driver
15.7, 16.0
Linux x86 32-bit
Linux x86-64 64-bit
AIX 64-bit
HP-UX IA 64-bit
Windows x86 32-bit
Linux x86 32-bit
Linux x86-64 64-bit
Mac OS X Intel 32-bit
Windows x86 32-bit
Windows x86 32-bit
Windows x86 32-bit
IBM AIX POWER 64-bit
HP-UX IA 64-bit
Linux x86-64 64-bit
Linux on POWER 64-bit
Windows x86 32-bit
HP-UX IA 64-bit
Linux x86-64 64-bit
Windows x86 32-bit
15.5.x
SAP ASE OLE DB Provider
ADO.NET
SAP Replication Server
15.7, 15.5.x
2.x, 4.x, 16.0
15.7.1 SP100, 15.7.1 SP200
15.7, 15.7.1

Product Summary
Client Name
Version
Supported Platform
15.5, 15.6
HP-UX IA 64-bit
Linux x86 32-bit
Linux x86-64 64-bit
Windows x86 32-bit
Note
SAP ASE is supported on SAP Control Center 3.3.
2.2
Product Compatibility
Learn about SAP ASE compatibility with earlier versions of ASE, and with other SAP products.
2.2.1
Compatibility of Fixes with Previous SAP ASE Releases
SAP ASE 16.0 contains all the fixes of releases SAP ASE 15.7 SP100 to SP103, SP110, and all previous SAP ASE
15.7 releases, up to and including SAP ASE 15.7 SP60.
2.2.2
Password Compatibility with Replication Server
There are compatibility issues with replicating logins and roles between different versions of SAP ASE.
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.

Product Summary
2.3
Changes That Affect Existing Applications
Learn about changes in SAP ASE 16.0 that affect your existing applications.
2.3.1
FIPS Encryption
In Adaptive Server 15.7 SP60 and later, enabling the FIPS login password encryption parameter specifies
that the FIPS 140-2 compliant module is used for all encryption related operations.
FIPS Encryption must be turned on and the client libraries must also enable FIPS to complete FIPS configuration.
In releases prior to Adaptive Server 15.7 SP60, enabling the FIPS login password encryption parameter
specified the use of the FIPS 140-2 compliant cryptographic module for the encryption of passwords in
transmission, in memory and on disk.
2.3.2
SDK for SAP ASE and PC Client
The PC-client components are now available as part of SDK for SAP ASE. You can download this software
development kit (SDK) from the SAP Service Marketplace.
Earlier versions of SAP ASE required you to install PC-client components from a separate CD. The SAP Service
Marketplace includes client applications and utilities you can download and use to access the SAP ASE server to
execute queries or manage the server. SDK for SAP ASE also contains the Open Client/ Open Server Software
Developers Kit, which you can use to develop applications that access the server, and ODBC, OLE DB, and
ADO.NET clients.
For information about changes that affect SDK for SAP ASE, see the most recent release bulletins for these
products on the SAP Help Portal.
2.3.3
Behavior Change for When Triggers are Fired
The new ODBC connection property, CAP_CUMULATIVE_DONE optimizes the way SAP ASE processes batch
insert statements. By default, this property is on.
With CAP_CUMULATIVE_DONE on, triggers fire after all inserts in a batch are processed. That is, after the
batch insert has inserted all rows, any trigger that exists on the insert table is fired only once.
In releases earlier than SAP ASE 16.0, CAP_CUMULATIVE_DONE is not recognized, and triggers fire after
each row is inserted.
To change the default behavior, turn off CAP_CUMULATIVE_DONE in the ODBC connection string.

Product Summary
2.3.4
Changes to Plan Sharing
The enable plan sharing configuration option is no longer automatically enabled when the enable
functionality group configuration option is enabled: you must now explicitly enable plan sharing.
2.3.5
Location for Utilities and Scripts
The location of the command line version of some utilities and scripts has changed.
For UNIX, the path for these utilities and scripts has been changed to $SYBASE/ASE-16_0/bin:
auditinit
startserver
preupgrade
upgrade
For Windows, the path for these utilites and scripts has been changed to %SYBASE%\ASE-16_0\bin:
auditinit
startsrv
preupgrd
upgrade
2.3.6
Changes for SAP ASE Plug-in
The SQL Central plug-in (formally Sybase Central) is no longer included in the SAP ASE installation image. Use
SAP Control Center 3.3 to manage your SAP ASE 16.0 servers.
2.3.7
Backup Server and IBM Tivoli Storage Manager
Use a local backup server to dump and load to the IBM Tivoli Storage Manager; you cannot use a remote backup
server.
You can configure the IBM Tivoli Storage Manager on a host machine other than the local backup server.
10

Product Summary
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.
3.1
Special Installation Instructions
Learn about special installation instructions for SAP ASE.
3.1.1
Release Directory Structure Change
SAP ASE directories names have been modified for version 16.0.
Earlier than SAP ASE 16.0
SAP ASE 16.0
$SYBASE/ASE-15_0
$SYBASE/ASE-16_0
$SYBASE/OCS-15_0
$SYBASE/OCS-16_0
$SYBASE/WS-15_0
$SYBASE/WS-16_0
$SYBASE/DBISQL
$SYBASE/DBISQL-16_0
$SYBASE/jConnect-7_0
$SYBASE/jConnect-16_0
3.1.2
Installing Enterprise Connect Data Access (ECDA) or
MainframeConnect DirectConnect for z/OS
SAP strongly recommends that you install the ECDA DirectConnect option or MainframeConnect DirectConnect
for z/OS, including DirectConnect Manager, into its own directory.

11
3.2
Special Configuration Instructions
Special configuration instructions for SAP ASE.
3.2.1
Manage Permissions of Remote Hosts That Access
Backup Server
During Backup Server configuration, the option Allow Hosts is now available. This option prevents remote dumps
and loads, and execution of remote procedure calls (RPCs) from any client or server that is running on
unauthorized servers.
Enter a comma-separated lists of host names or IP addresses that are allowed to connect to the Backup Server.
The default value is NULL. When NULL, only the dataserver running on the same host as the Backup Server can
access the Backup Server.
3.3
Special Upgrade Instructions
Get last-minute instructions for upgrading and migrating SAP ASE.
3.3.1
Compare Configuration Parameters Before and After
an Upgrade
Existing configuration parameters defined using an early version of SAP ASE are reset to default values.
Some configuration parameters that were added in ASE 15.7 are reset to their default values, regardless of
the values that were set on the 15.7 server.
Configuration parameters belonging to the Application Functionality group are reset to zero even when
enable functionality group is set to 1.
The workaround for this issue is to compare the configuration parameters before and after upgrading to 16.0 and
reset the configuration parameters accordingly.
These are the configuration parameters affected:
enable backupserver HA
enable dump history
recovery prefetch size
optimize dump for faster load
enable plan sharing
kernel resource memory
12

enable async database init
cluster redundancy level
FIPS login password encryption
enable predicated privileges
enable granular permissions
enable functionality group
select for update
streamlined dynamic SQL
enable inline default sharing
enable permissive unicode
quoted identifier enhancements
suppress js max task message
enable concurrent dump tran
enable large pool for load
Note
Not all of the parameters listed are present in earlier versions of SAP ASE 15.7. You only need check for
parameters that exist in the older 15.7 version on your system.
3.3.2
Cross-Platform Loading of an Encrypted Database
Cross-platform loading of an encrypted database dump is not supported in SAP ASE 16.0.
3.3.3
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.
See the New Features Guide > Runtime Logging Enhancements for more information about the SAP ASE queuing
strategy.

13
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.
3.3.4
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>
2>
1>
2>
3>
2.
use <database_name>
go
select name from sysobjects where id in
(select id from syscolumns where type = 34 or type = 35)
go
Using the latest SAP ASE version, run the following on each database to detect garbage flags:
1> dbcc checkdb(dbname, skip_ncindex)
2> go
14

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

15
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)
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.3.5
Loading Database Dumps into Earlier Versions
You cannot dump a database from a 16.0 version of SAP ASE and load it into a database on a server running a
release earlier than 16.0.
3.4
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
757866 Installer does not display the minimum OS version or missing patches.
In the event of a failed installation due to not meeting the minimum OS version or patch requirements,
the installer does not display the reason for the failed installation.
Workaround: See the installation guide for your platform for installation requirements.
692496 Configuring tempdb device for HA
16

CR #
Description
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 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.
588793 Installing SAP ASE 15.5 and later versions that use Install Anywhere on older directories that have been
installed with InstallShield Multiplatform can lead to incompatibility issues.
These issues occur while using products installed with different installer technologies:
If you install products using Install Anywhere or InstallShield Multiplatform on top of a product
installed using the other 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 indicating messages.
Workaround: Do not install products that use Install Anywhere and products that use InstallShield
Multiplatform in the same directory.

17
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
759956 Error 15497 is produced during server boot if system tempdb is encrypted.
Problems can occur when re-creating temporary databases during a server reboot.
Workaround: Do not encrypt temporary databases.
757883 ddlgen raises the error: DG16: Could not get Console instance.
You cannot invoke the ddlgen utility from a script while supplying the pseudo password using -Pext
to hide the password, and redirect the input where the actual password is in a file or used to set an
environment variable.
Workaround: To hide the password, invoke ddlgen from the command line and do not supply a value
for the -P parameter. ddlgen prompts you for the password, and the password is hidden from any
user who issues the ps command on the host machine where ddlgen is running.
756990 Queries involving proxy tables fail when there are more than 50 table names.
Workaround: None. Queries involving proxy tables have a 50-table limit.
748320 Columns with Name sybdropcol <column_id> <object_id>
Issuing split or move partition on user tables that:
Include any columns named sybdropcol_<<column_id>>_<<object_id>>
Have undergone alter table drop column with no data copy
may fail, and issue error message 2705:

Level 16, State 1: Line 1: Column names in each
table must be unique. Column name '<colname>' in table
'#<table name>' is specified more than once.
741918
Java applications fail to start using SAP JRE7.

Java applications, such as sybdiag, which run using SAP JRE7.1 008 may encountered 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.
739773 The load database with listonly=load_sql command may generate load commands
which, if executed, may require you to manually alter the target database for the load to succeed.
This issue can occur in cases where an alter database off command was run on the source
database.
Workaround: None.
18

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 If you change the ID of any server 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.
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.
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
enabled.
580614 A single-engine SAP ASE may stop responding when, after performing a Java task, additional
engines are manually brought online.

19
CR #
Description
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.
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.
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
directory permissions in the file system. The physical directory can have any permissions mask that is
appropriate for that directory.) This setting is only for the sybpcidb configuration properties, where
you can configure 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)'
20

Documentation Updates
Read about updates, corrections, and clarifications to the documentation released with SAP ASE .
5.1
Database Encryption Restrictions
The documentation for database encryption is missing restriction information concerning REORG commands.
Document: New Features Guide 16.0 > Full Database Encryption > Encrypt an Existing Database.
Do not execute REORG commands when the encryption or decryption of database is in progress. This is because
the REORG command can rearrange the pages of the database being encrypted or decrypted, which can affect
the fragment size.
5.2
Job Scheduler Parameter job
scheduler interval
The configuration parameter job scheduler interval incorrectly describes the value of units as minutes.
Document: System Administration Guide: Volume 1 > Setting Configuration Parameters > Configuration
parameters.
The documentation provides the value of units for the configuration parameter as follows:
job scheduler interval Default value : 1 (in minutes)
Range of values : 1 600
The correct unit value is seconds.
5.3
Job Scheduler Command sp_sjobdrop
The sp_sjobdrop name parameter incorrectly states that the name of a job or a schedule can be used for the
name argument.
Document: Job Scheduler User's Guide >Command Reference.
You must use the ID of scheduled job, job, or schedule for the name argument.

21
5.4
Security Built-in Function Permissions
The documentation regarding permissions for several built-in functions is incomplete.

Document: Reference Manual: Building Blocks > Transact-SQL Functions.
Functions
asehostname
Permissions
With granular permissions enabled, you must be granted select on
asehostname or have manage server permission to execute
asehostname.
With granular permissions disabled, you must be granted select on
asehostname or be a user with sa_role to execute asehostname.
migrate_instance_id
Any user can execute migrate_instance_id.
show_cached_text
With granular permissions enabled, you must be a user with mon_role, or

have monitor qp performance permission to execute
show_cached_text.
With granular permissions disabled, you must be a user with mon_role or
sa_role to execute show_cached_text.
show_cached_text_long
With granular permissions enabled, you must be a user with mon_role, or

have monitor qp performance permission to execute
show_cached_text_long.
With granular permissions disabled, you must be a user with mon_role or
sa_role to execute show_cached_text_long.
show_plan
With granular permissions enabled, you must be a user with monitor qp

performance permission to execute show_plan.
With granular permissions disabled, you must be a user with sa_role to
execute show_plan.
user_id
Any user can execute user_id.
workload_metric
With granular permissions enabled, you must have manage cluster

permission or be a user with ha_role to execute workload_metric.
With granular permissions disabled, you must be a user with sa_role or
ha_role to execute workload_metric.
5.5
Shareable Temporary Tables
The documentation incorrectly states that a shared temporary table exists until the current session ends, or until
its owner drops it using drop table.
22

Document: Transact-SQL Users Guide > Creating Databases and Tables > Creating Tables > Using temporary
tables.
While hash temporary tables exist until the current session or scope is exited, shared temporary tables exist until
they are explicitly dropped.
5.6
Hash-Based Update Statistics
An example for the update statistics configuration parameter hashing is missing an example showing that
three parameters are required for the option
Document: New Features Guide 15.7 ESD #2 > Hash-Based Update Statistics > Enabling hash-based statistics.
This is an example of using update statistics using the hashing option:
sp_configure 'update statistics hashing', 0, 'on'
5.7
Values for lock timeout pipe active
The default value and the range of values for lock timeout pipe active are incorrect.
Document: System Administration Guide: Volume 1 > Setting Configuration Parameters > Configuration
parameters.
The correct values are:
Default value 0 (off)
Range of values 1 (on), 0 (off)
5.8
dbcc page
Parameter logical
The documentation for the dbcc page command incorrectly describes the logical parameter.
Document: Troubleshooting and Error Messages Guide > Encyclopedia of Tasks > Useful dbcc Commands > Other
dbcc Commands.
The correct description for the logical parameter is:
If cache = 1, the value of logical is considered 1 and the value passed for pageno is treated as logical page
number.
If cache = 0, the value of logical is taken as the virtual device number and the value passed for pageno is
treated as a virtual page number. You can obtain the virtual device number from the master..sysusages table.

23
5.9
Behavior of Concurrent DDLs and reorg defrag
This information supplements the documentation for Incremental Reorganization and describes how concurrent
DDLs behave when reorg defrag is in progress, and how reorg defrag behaves during concurrent DDLs.
Document: New Features Guide 15.7 SP100 > Incremental Reorganization.
When reorg defrag is in progress on a table, invocation of any schema-changing utility or datareorganization utility fails with error 11051. In rare cases of race condition between reorg defrag and the
other utility, one of them might have to wait for the other to complete.
When reorg defrag utility is in progress on a table, another invocation of reorg defrag on the same table
fails with error 8233.
When a schema-changing utility or data-reorganization utility is in progress, invocation of reorg defrag

waits for the utility to complete before proceeding to defragment the data.
24

Obtaining Help and Additional Information
Use the Product Documentation site and online help to learn more about this product release.
Product Documentation at http://sybooks.sybase.com/

online documentation that you can access using
a standard Web browser. You can browse documents online, or download them as PDFs. The Web site also
has links to other resources, such as white papers, community forums, maintenance releases, and support
content.
Online help in the product, if available.
To read or print PDF documents, you need Adobe Acrobat Reader, which is available as a free download from the
Adobe
Web site.
Note
A more recent release bulletin, with critical product or document information added after the product release,
may be available from the Product Documentation Web site.
6.1
Technical Support
Get support for SAP products.

If your organization has purchased a support contract for this product, then one or more of your colleagues is
designated as an authorized support contact. If you have any questions, or if you need assistance during the
installation process, ask a designated person to contact Technical Support as specified in your contract:
Sybase Technical Support or the Sybase subsidiary in your area
SAP Technical Support
Customers with an SAP support contract can obtain support for this product at the SAP support site, http://
service.sap.com/sybase/support
location (login may be required).
. You can also find information about Sybase support migration at this
Customers with a Sybase support contract can obtain support for this product at http://www.sybase.com/
support
(login required).

25
6.2
Downloading Product Updates
Get maintenance releases, support packages and patches, and related information.
Procedure
If you purchased the product directly from Sybase or from an authorized Sybase reseller:
a) Go to http://www.sybase.com/support
b) Select
Support
EBFs/Maintenance .
c) If prompted, enter your MySybase user name and password.

d) (Optional) Select a filter, a time frame, or both, and click Go.
e) Select a product.
Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance
releases because you are not registered as an authorized support contact. If you have not registered, but
have valid information provided by your Sybase representative or through your support contract, click My
Account to add the Technical Support Contact role to your MySybase profile.
f)
Click the Info icon to display the EBF/Maintenance report, or click the product description to download
the software.
If you ordered your product under an SAP contract:

a) Go to http://service.sap.com/swdc
and log in if prompted.
b) Select Search for Software Downloads and enter the name of your product. Click Search.
6.3
Product and Component Certifications
Certification reports verify Sybase product performance on a particular platform.

To find the latest information about certifications:
For partner product certifications, go to http://www.sybase.com/detail_list?id=9784
For platform certifications, go to http://certification.sybase.com/ucr/search.do
6.4
Accessibility Features
Accessibility ensures access to electronic information for all users, including those with disabilities.
Documentation for this product is available in an HTML version that is designed for accessibility.
26

Vision impaired users can navigate through the online document with an adaptive technology such as a screen
reader, or view it with a screen enlarger.
HTML documentation has been tested for compliance with accessibility requirements of Section 508 of the U.S
Rehabilitation Act. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines,
such as the World Wide Web Consortium (W3C) guidelines for Web sites.
Note
You may need to configure your accessibility tool for optimal use. Some screen readers pronounce text based
on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You
might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your
tool.
For information about how Sybase supports accessibility, see the Sybase Accessibility site: http://
www.sybase.com/products/accessibility
standards.
. The site includes links to information about Section 508 and W3C
You may find additional information about accessibility features in the product documentation.

27
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 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 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).
28


29
www.sap.com/contactsap
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.

SAP Adaptive Enterprise 16.0 - Release Bulletin For HP-UX

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SAP Adaptive Enterprise 16.0 - Release Bulletin For HP-UX

Diunggah oleh

Hak Cipta:

Format Tersedia

SAP Adaptive Server Enterprise

Document Version: 16.0 - 2014-09-19

Release Bulletin for HP-UX

Compatibility of Fixes with Previous SAP ASE Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Password Compatibility with Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Changes That Affect Existing Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

SDK for SAP ASE and PC Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Behavior Change for When Triggers are Fired. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Changes to Plan Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Location for Utilities and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Changes for SAP ASE Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Backup Server and IBM Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Special Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Release Directory Structure Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Special Configuration Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Manage Permissions of Remote Hosts That Access Backup Server. . . . . . . . . . . . . . . . . . . . 12

Special Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Compare Configuration Parameters Before and After an Upgrade. . . . . . . . . . . . . . . . . . . . . 12

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

Upgrade and Runtime Logging Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

Loading Database Dumps into Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Known Installation Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Known Issues for SAP ASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Database Encryption Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Job Scheduler Parameter job scheduler interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Job Scheduler Command sp_sjobdrop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Security Built-in Function Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Shareable Temporary Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Hash-Based Update Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2014 SAP SE or an SAP affiliate company. All rights reserved.

Release Bulletin for HP-UX

Values for lock timeout pipe active. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

dbcc page Parameter logical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Behavior of Concurrent DDLs and reorg defrag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Obtaining Help and Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Downloading Product Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Product and Component Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Release Bulletin for HP-UX

2014 SAP SE or an SAP affiliate company. All rights reserved.

2014 SAP SE or an SAP affiliate company. All rights reserved.

Release Bulletin for HP-UX

SAP Open Client/SAP Open

Linux x86 32-bit

Linux x86-64 64-bit

Linux Pseries 32-bit

Linux Pseries 64-bit

Solaris SPARC 32-bit

Solaris SPARC 64-bit

Solaris x86 32-bit

Solaris x86-64 64-bit

Windows x86 32-bit

Windows x86-64 64-bit

Release Bulletin for HP-UX

2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP Adaptive Server Enterprise

Extension Module for Python

SAP Adaptive Server Enterprise

Extension Module for PHP

SAP Adaptive Server Enterprise

Database Driver for PERL

SAP jConnect for JDBC