Release Bulletin Adaptive Server Enterprise 15.0.1 Cluster ...infocenter-archive.sybase.com/help/topic/com.sybase.infocenter.dc... · IBM AIX 6.1. See to the Cluster ... 9.1 Performance

Copyright 2008 by Sybase, Inc. All rights reserved. Sybase trademarks can be viewed at the Sybase trademarks page at http://www.sybase.com/detail?id=1011207. Sybase and the marks listed are trademarks of Sybase, Inc. ® indicates registration in the United States of America. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names mentioned may be trademarks of the respec-tive companies with which they are associated.

Release BulletinAdaptive Server® Enterprise 15.0.1Cluster Edition ESD #4 for IBM AIX

Document ID: DC00903-01-1501-01

Last revised: December 3, 2008

Topic Page

1. Accessing current release bulletin information 2

2. Product summary 2

2.1 Version contents 2

2.2 Additional features and support for Cluster Edition ESD #4 3

2.3 Features and utilities unsupported in this version 3

3. Special installation instructions 5

4. Special configuration instructions 5

4.1 Increasing Adaptive Server shared memory requirements 5

4.2 Number of pre-allocated extents 5

4.3 Client failover due to host failure 6

4.4 Protect IO from a non-member instance in a cluster 6

5. Special upgrade instructions 6

5.1 Upgrading from a 12.5.3 installation with cache bindings on sybsystemdb

7

5.2 Upgrading Job Scheduler 7

6. Changed functionality in this version 7

6.1 Component Integration Services support 7

6.2 Directory changes 7

6.3 Changes that affect application behavior 8

6.4 Changes that affect database administration operations 11

7. Known Problems 14

7.1 Cannot find agents with UDP server discovery 15

7.2 Starting Unified Agent could report a permissions error 15

7.3 Blank spaces in an ldap server entry 15

7.4 cis connect timeout and enable SNMP are not implemented 15

7.5 Known problems with the Adaptive Server cluster feature 16

7.6 Known problems with the Adaptive Server plug-in 17

1. Accessing current release bulletin information Adaptive Server Enterprise Cluster Edition

2 Release Bulletin for IBM AIX

1. Accessing current release bulletin informationA more recent version of this release bulletin could be available on the Web. To check for critical product or document information added after the product release, use the Sybase® Product Manuals Web site.

❖ Accessing release bulletins at the Sybase Product Manuals Web site

1 Go to Product Manuals at http://www.sybase.com/support/manuals/.

2 Select a product and language and click Go.

3 Select a product version from the Document Set list.

4 Select the Release Bulletins link.

5 From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.

2. Product summaryEnclosed is Sybase Adaptive Server® Enterprise 15.0.1 Cluster Edition for IBM AIX 6.1.

See to the Cluster Edition Installation Guide for operating system requirements, and the Sybase Certification Web Page at http://certification.sybase.com for additional operating systems supports.

2.1 Version contents• Adaptive Server 15.0.1 Cluster Edition ESD #4

8. Product Compatibility 19

9. Documentation updates and clarifications 19

9.1 Performance and Tuning Guide 19

10. Technical support 20

11. Other sources of information 20

11.1 Sybase certifications on the Web 20

11.2 Sybase EBFs and software maintenance 21

12. Accessibility features 22

Topic Page

Adaptive Server Enterprise Cluster Edition 2. Product summary

Release Bulletin for IBM AIX 3

• PC-Client 15.0.1 Cluster Edition

2.2 Additional features and support for Cluster Edition ESD #4The ESD #4 version of the Cluster Edition includes these features and system changes:

• Configuring auxiliary servers (Backup Server, XP Server, and Monitor Server) using Adaptive Server Plug-in – Online help.

• Configuring auxiliary servers (Backup Server, XP Server, and Monitor Server) using sybcluster – Chapter 3 in the Installation Guide.

• Performing server upgrades to Adaptive Server 15.0.1 Cluster Edition ESD #4 using the sybcluster utility – Chapter 6 in the Installation Guide.

• number of open databases configuration parameter raised from 5 to 6 – “Changed configuration parameters” in the Users Guide to Clusters.

• SSL support for jConnect, ODBC, OLE DB and ADO.NET – “Connection migration” in the Users Guide to Clusters.

• IO fencing – “IO fencing” in the Installation Guide.

• Interconnect networks and monCIPCLinks monitoring – The following sections in the Users Guide to Clusters:

• “Monitoring links between instances” in Chapter 1, “An Overview of the Cluster Edition.”

• Chapter 4, “Using Monitoring Tables in a Clustered Environment.”

2.3 Features and utilities unsupported in this versionThis section descriptions those features and utilities that are not supported in this version of Adaptive Server.

2.3.1 Unsupported utilities and features in the Cluster Edition

The following utility programs are not supported for the Cluster Edition:

• sqlupgrade

• sqlloc

• srvbuild

These features are not supported for the Cluster Edition:

2. Product summary Adaptive Server Enterprise Cluster Edition


• Distributed Transaction Management (DTM).

• mount, unmount, and dbshutdown commands.

• Adaptive Server disk mirroring.

• The Adaptive Server Enterprise high-availability (HA) option does not apply. In the Cluster Edition, HA is integrated into Adaptive Server.

• Java in the server.

• Because the Cluster Edition does not include the Adaptive Server Transaction Coordinator (ASTC), Component Integration Services (CIS) for the Cluster Edition does not provide a full two-phase commit. CIS handles queries that include remote servers in a “best effort” basis.

• Replication using Adaptive Server Enterprise Replicator.

Note The ASE-15_0/bin directory includes a utility called iofenceutil, which duplicates the functionality of qrmutil --fence_capable, but does not require the quorum device and also returns an exit code. This is an internal utility used by sybcluster and is not designed for regular use.

2.3.2 Maximum number of instances supported in Adaptive Server Cluster Edition

While Adaptive Server 15.0.1 Cluster Edition contains architecture for up to 32 instances in a cluster, this ESD #4 release is currently certified and supported on four instances only.

2.3.3 The Cluster Edition version 15.0.1 ESD #4 does not support IPv6

The Cluster Edition version 15.0.1 ESD #4 does not support Internet Protocol version 6 (IPv6) on IBM AIX. It does support IPv4.

Adaptive Server Enterprise Cluster Edition 3. Special installation instructions


3. Special installation instructionsSybase strongly recommends that you install the Adaptive Server Enterprise 15.0.1 Cluster Edition into its own directory. If you cannot do this, install the Cluster Edition last.

Warning! Sybase recommends that you not install an older version of a Sybase product in a $SYBASE directory that includes a newer Sybase product. For example, installing Replication Server® 15.0 on top of the Cluster Edition could make either the Cluster Edition or Replication Server inoperable, depending on the choices you select during install.

4. Special configuration instructionsThis section describes special configuration instructions for the Cluster Edition.

4.1 Increasing Adaptive Server shared memory requirementsAdaptive Server requires an additional 32MB of shared memory than in previous versions. You must increase configuration parameter 'max memory' to accommodate the additional memory requirement.

4.2 Number of pre-allocated extents In earlier versions of Adaptive Server, the maximum value allowed for the number of pre-allocated extents was 31. For the Cluster Edition the maximum values allowed for the number of pre-allocated extents is 32.

Using a value of 32 for the number of pre-allocated extents has a special significance for configuration and impacts the space allocations Adaptive Server performs internally. If you set the number of pre-allocated extents to 32, Adaptive Server attempts to reserve an entire allocation unit worth of extents for utility operations which use a large scale allocation scheme of space reservation like BCP-in and select into. This greatly improves the performance of these utilities, particularly when you run them concurrently on multiple nodes. consequently, using a value of 32 greatly increases the likelihood that each node of a cluster is able to work independently on its own allocation unit without interference from the other nodes.

5. Special upgrade instructions Adaptive Server Enterprise Cluster Edition


4.3 Client failover due to host failureWhen the node hosting an Adaptive Server instance fails, clients connected to that instance could not immediately failover. This is caused by the behavior of the TCP driver, which does not tell the client that the connection has been lost.

The TCP driver uses a mechanism known as keepalive to detect when the connection has been lost. The keepalive configuration varies by operating system, but generally defaults to a 2 hour window to detect the disconnect. It could be desirable to tune the TCP keepalive to a smaller value on the client machine to speed the failure detection (see your operating system manual).

You can avoid the delay in keepalive by coding the client applications to use timeouts. For Open Client (ct-library) applications, this includes the CS_TIMEOUT and CS_LOGIN_TIMEOUT parameters. For more information, see the Client-Library/C Reference Manual at http://infocenter.sybase.com/help/topic/com.sybase.dc32840_1500/html/ctref/title.htm.

This information is also documented in the “Troubleshooting” chapter in the Users Guide to Clusters.

4.4 Protect IO from a non-member instance in a clusterData corruption could occur when an instance leaves a cluster while there still exist in flight buffers on the departing node that are still in transition toward shared disks. To protect against writing to a shared disk, enable IO fencing.

To enable IO fencing, set the configuration parameter in the server configuration file to on. The default is off:

sp_configure “enable i/o fencing”, 1

For more information about IO fencing, see the installation guide.

5. Special upgrade instructionsThis section describes special upgrade instructions for the Cluster Edition.

Adaptive Server Enterprise Cluster Edition 6. Changed functionality in this version


5.1 Upgrading from a 12.5.3 installation with cache bindings on sybsystemdb

If you are upgrading from Adaptive Server version 12.5.3 ESD #4, or a later to the Cluster Editor ESD #4, and the sybsystemdb system database is bound to a user-defined cache, you could encounter a “current process... infected with 11" error in the module 'bufdlink' during preupgrade, with the modules 'pg_getreserved', 'pg_recacloam', 'bufpindirty' reported in the stack trace.

Workaround: Drop the cache bindings for sybsystemdb that are bound to a and re-run preupgrade.

5.2 Upgrading Job SchedulerWhen upgrading from a 12.5.x version to an Adaptive Server Cluster Edition version of Job Scheduler, you must increase the size of sybmgmtdb from 50MB to 90MB.

If jobs are created from templates, upgrade those jobs. See the instructions on upgrading Job Scheduler in the Users Guide to Clusters.

6. Changed functionality in this versionFor complete information regarding the new functionality of the Cluster Edition. See “System Changes” in the Users Guide to Clusters.

6.1 Component Integration Services supportThe Cluster Edition does not include the Adaptive Server Transaction Coordinator (ASTC) and does not provide a full two-phase commit. Instead, CIS handles queries that include remote servers on a best-effort basis.

6.2 Directory changesSybase has changed the director structures for Cluster Edition to:

• The cluster plug-ins directory is now named $SYBASE_UA/templates/plugins/com.sybase.ase.cluster/15.0.1.

• A directory named SDCADMIN-15_0 has been created to include the lib files for sybcluster.

6. Changed functionality in this version Adaptive Server Enterprise Cluster Edition


• All product components in the Cluster Edition use JRE-1_4 or JRE-1_5, which are now in the $SYBASE/shared directory.

• The Job Scheduler component (JS-12_5 in Adaptive Server version 12.5) is now in the ASE-15_0/jobscheduler directory.

6.3 Changes that affect application behaviorFor complete information about added functionality see the “System Changes” chapter of the Users Guide to Clusters.

6.3.1 Adaptive Server Enterprise does not support db2 server class

Server class db2 is not supported by Adaptive Server. To use db2, migrate your db2 server class to direct_connect class.

6.3.2 Using sp_configure in the Cluster Edition

• To configure an instance-specific value only for the instance to which you are currently connected.

• Cluster-wide configuration options are never made instance-specific.

• Reconfiguration of a cluster-wide value does not overwrite an instance-specific configuration.

6.3.3 Accessing temporary objects shareable across sessions

Applications created since Adaptive Server version 12.5.0.3 may create shareable tables in user-created temporary databases. To enable existing applications to continue to work with the Cluster Edition, user-created temporary databases that include these shareable tables need to be dropped and re-created as global temporary databases with the same names.

6.3.4 Managing assigned temporary database inside an application

The default temporary database which is assigned to a session is a local, temporary, instance specific, database. It is not the system tempdb (with a dbid of 2). After upgrading from a non-clustered environment, you could need to modify applications that previously assumed the default assigned temporary database as system tempdb (with a dbid of 2) in their actions, so that these actions are now applied to the assigned local temporary database in the Cluster Edition.



For example: in a nonclustered environment, an application truncates the log of the default temporary database by:

dump tran tempdb with truncate_only.

In the Cluster Edition, you must modify the application to truncate the log of the default assigned temporary database:

declare @tempdbname varchar(30)select @tempdbname = db_name(@@tempdbid)dump tran @tempdbname with truncate_only

6.3.5 Permissions for user-defined roles in local temporary databases

Do not grant permission to user defined roles in local temporary databases. If you do so, you could not be able to drop a role.

6.3.6 Long-identifier changes

• Adaptive Server Enterprise now supports long identifiers. There are new limits for the length of object names or identifiers: 255 bytes for regular identifiers, and 253 bytes for delimited identifiers. The new limit applies to most user-defined identifiers including table name, column name, index name and so on. Due to the expanded limits, some system tables (catalogs) and built-in functions have been expanded. For variables, “@” counts as 1 byte, and the allowed name is 254 bytes long.

• Change identifier names with corresponding application changes for binding values. Make sure your application is not binding names of identifiers with only 30 bytes, which was the previous limit. This could cause a variety of unexpected behaviors or error messages.

6.3.7 Query changes

• Some queries could now return general syntax error (message 102) instead of syntax error at line # (message 156).

• The order of result sets in the Cluster Edition could vary between queries unless there is an order by clause in the query.

• Query compilation time could increase as the query processing engine looks for more ways to optimize the query.

• See the Adaptive Server 15.0 Performance and Tuning Guide for details about query processing in the Cluster Edition.



6.3.8 Component Integration Services changes

• NULL behavior differs in Oracle, ASA, and IQ—you must override ANSI NULL behavior for it to work as in the Cluster Edition.

• The Cluster Edition no longer pads char null, varchar, binary null, and varbinary datatypes for proxy tables.

• By default, cursors are READ ONLY. Declare cursors with for update to update through them.

• You must have an index if you are using updateable cursors.

• Component Integration Services engines no longer take special measures to re-declare cursors for back ends that close cursors on end tran.

• You must declare an explicit begin tran and end tran around cursor statements for DB2 servers.

• If you attempt to create a column constraint on java, text, image, and unitext datatypes, message 11074 is raised.

• create table, create existing table, or create proxy table statements that contain a location clause are restricted by the fact that they must be the only statement in a batch. This also applies to select into statements that contain a location clause.

6.3.9 Error message changes

• Many messages have been changed to specify “ASE” in the error message.

• When creating a temporary table that already exists, Adaptive Server Enterprise raises message 12822, instead of 2714.

• The identity column overflow message is now raised with message 587 instead of 4916.

• When you create a Java function that does not exist in the catalogs, message 14216 is raised instead of syntax error message 195.

• When a non-owner executes sp_procxmode to change the transaction mode associated with a stored procedure, error message 10354 is raised.

• Arithmetic overflow errors are now raised with message 3606 with severity 16.

• Message 2579 has been replaced with message 12907 in dbcc checktable output.



6.4 Changes that affect database administration operationsFor more information about added functionality see the System Changes chapter of the Users Guide to Clusters.

6.4.1 Run time change of identity gap is not supported in the Cluster Edition

Use of the sp_chgattribute stored procedure to change the value of identity_gap at runtime is not supported.

6.4.2 Usage of system built-in functions

Built-in functions that provide space information, such as data_pgs, reserved_pgs, used_pgs, ptn_data_pgs, and rowcnt have been replaced with data_pages, reserved_pages, used_pages, and row_count, respectively. See Reference Manual: Building Blocks for detailed information.

6.4.3 DDL and DML changes

As of Adaptive Server 15.0.x, the following changes have taken place:

• alter table… unpartition is not allowed on tables with indexes (use alter table with 1 partition to remove the partitions).

• alter table on a partitioned table with max parallel degree less than the number of partitions could succeed without raising message 326.

• Creating a clustered index on an empty partitioned table returns a new informational message, 1936.

• Null column names are not allowed during view creation.

• A select statement that contains an aggregate from a proxy table that is mapped to an RPC with a parameter, fails with error message 201.

6.4.4 System stored procedure changes

As of Adaptive Server 15.0.x the following changes have taken place:

• The output of sp_help object has been changed. Specifically, Data_Located_on_segment has been removed, while Computed_Column_Object and information related to partitions have been added.

• The order of index_keys and index_description in the output of sp_helpindex has been changed.



• Major changes have been made to the output of sp_helpartition and sp_helpsegment.

• sp_who returns “NULL” instead of blank in the hostname column for all system tasks.

• sp_who results in SQL command (insert or select) in the output. In earlier versions, sp_who returned select for the tasks that executed sp_who.

• sp_objectsegment displays segment information for all partitions of the table.

• sp_lock output does not contain a column called partitionid.

• sp_monitorconfig now accepts number of open partitions. When this procedure is executed with the parameter all, additional output for configuration parameter number of open partitions is displayed.

• The Metadata Cache Management section of sp_sysmon displays additional information pertaining to open partitions.

6.4.5 Common diagnostics changes including trace flag usage

These changes are in place as of Adaptive Server 15.0.x:

• Output for dbcc listoam has changed substantially.

• The space state message printed in the old dbcc listoam output is now available as a new column spacestate in sysobjects.

• Output for dbcc tablealloc has changed.

• Output for dbcc page now displays the print partition ID instead of the object ID.

• Output for dbcc checktable on a partitioned table has been changed to provide partition-level information.

• dbcc checktable/tablealloc/indexalloc has new syntax for partition support.

• Output for the reorg reclaim_space tablename with resume command has changed.

• reorg rebuild fails with message 11051 when table is in use by other tasks.

• Output of sp_dbcc_faultreport has been enhanced to show partition ID information.



• The hostname, program_name, hostprocess, and cmd columns in sysprocesses have been changed to varchar(30) and made nullable. select from sysprocesses returns NULL for these columns instead of space for system tasks.

• The “first” column in sysindexes has been moved to the “firstpage” column in syspartitions.

• The name column in syspartitions has been changed from index_name+_+tableid to index_name+_+ptn_id for partition table with indexes.

• The basic cost of the optimizer now includes CPU cost.

• Parallel costing is performed only on base tables and indexes that are larger than 20 pages.

• For information about trace flags and diagnostics, see the Query Processor document.

6.4.6 System resource changes

These changes are in place as of Adaptive Server 15.0.x:

• The Cluster Edition uses more procedure cache because:

• The query processing engine looks for additional ways to optimize the query.

• The execution engine avoids materialization of worktables and evaluates aggregations in memory as much as possible.

• The data change counters maintained for the datachange function allocate memory from procedure cache. The partition condition tree is cached in the procedure cache. Partition boundary values are allocated in the procedure cache, resulting in a required increase in procedure cache resources.

• New configuration parameter max repartition degree controls the maximum degree to which an intermediate data stream can be repartitioned. The default value of this parameter is 1, which indicates that repartitioning is not set and is bound by the number of online engines configured for Adaptive Server Enterprise. For a query with a large number of tables, the Cluster Edition can put an increased demand on auxiliary scan descriptors.

7. Known Problems Adaptive Server Enterprise Cluster Edition


Set the value of max repartition degree to a value lower than the number of engines to decrease resource usage. You could also need to configure a larger value for the auxiliary scan descriptor pool.

• The Cluster Edition avoids worktable materialization and incurs more resources in auxiliary scan descriptors.

• During the upgrade process, max memory is increased by Adaptive Server Enterprise if the new total logical memory is greater than max memory. The new value of max memory is set to the new value of total logical memory.

• During the upgrade process, number of open partitions is set to the same value as number of open indexes, resulting in increased memory usage. An open partition requires approximately 950 bytes.

• In the Cluster Edition, all database data and metadata objects can be accessed and cached by any instance in the cluster. As a consequence, these objects are subject to distributed locking and cache coherency enforcement, as are runtime global data structures and variables. Hence, in the Cluster Edition the default value of 'number of locks' config parameter has been bumped up. This could require you to take a closer look at the 'max memory' configuration and make proper adjustments.

6.4.7 Unpartitioning of user tables during upgrade

In the Cluster Edition, each table partition must have a different partitionid. To avoid the expense of changing the partitionid for each page during the upgrade process, Adaptive Server Enterprise unpartitions any partitioned tables. Repartition these tables when the upgrade process completes.

7. Known ProblemsThis section describes known problems and workarounds for Enterprise Cluster Edition.

Note Sybase no longer includes System Problem Reports (SPR) and Closed Problem Reports (CPR) with your copy of Adaptive Server Enterprise. Known problems, which used to be in the SPR, are now described in this section of the release bulletin. Closed issues that were documented in the CPR are now searchable from Solved Cases at the Sybase Web site at http://www.sybase.com. To access the Solved Cases search form, click Support and Services | Solved Cases.

Adaptive Server Enterprise Cluster Edition 7. Known Problems


7.1 Cannot find agents with UDP server discovery[CR #551965] Neither sybcluster nor the Adaptive Server plug-in wizards can find the agents running on AIX 6.1.1 machines with UDP server discovery:

sybcluster -U uafadmin -P

Workaround: Utililities can find all the agents in the local subnet including those running on AIX 6.1.1 machines if you connect specifically to the machine’s agent:

sybcluster -U uafadmin -P -F aix1:9999

However in order to prevent this from happening altogether, install the 6100-02 Service Pack 1 from the IBM Web site at http://www-933.ibm.com/eserver/support/fixes/fixcentral/pfixpacks/61.

7.2 Starting Unified Agent could report a permissions error[CR# 487525] When you execute the uafstartup.sh script for the first time, you could receive an error stating that you do not have permissions to access some files. This occurs when starting the agents for the first time in the current $SYBASE directory only if starting multiple UAF agents at the same time. This problem is caused by latency issues in the NFS file system layer.

Workaround: Wait a few seconds, then retry a second time.

7.3 Blank spaces in an ldap server entry[CR #333307] If you have a blank space after your ldap server entry, dscp defaults to using the interfaces driver and does not connect to an ldap server.

Workaround: To use dscp to make an entry into an ldap server, enable ldap by editing the $SYBASE/OCS-15_0/config/libtcl.cfg file to add the ldap server you plan to use.

7.4 cis connect timeout and enable SNMP are not implemented[CR #341787] The cis connect timeout and enable SNMP configuration parameters are not currently implemented.

Workaround: Do not use these configuration parameters.



7.5 Known problems with the Adaptive Server cluster featureThis section describes known problems with the cluster feature of Adaptive Server.

7.5.1 Setting 'cluster heartbeat retries' to value higher than 2 not permitted[CR #486377] Configuring cluster heartbeat retries to a value greater than 2 could result in a total cluster shutdown during failover handling for clusters with more than 2 instances.

Workaround: Do not configure cluster heartbeat retries to a value higher than 2.

7.5.2 Restarting an unfinished Cluster Creation wizard session[CR# 485070] If you exit from the Cluster Creation wizard during a cluster configuration and then restart the wizard session using the same configuration parameters (cluster name, instance name, and so on), the wizard could have already created some configuration files and devices.

Workaround: Follow these steps.

❖ Before you restart a wizard session:

1 Stop the srvbuildres or dataserver utilities, if either are running.

2 Stop the UAF agents on all nodes.

3 Remove the directory with the name of the cluster you tried to create during the wizard session in the $SYBASE_UA/nodes/node_name/plugins/cluster_name directory.

4 Remove the interfaces file entries for the cluster you tried to create.

5 Restart the UAF agents on all nodes.

7.5.3 Incorrect Cluster failover can occur[CR #483651] If an instance is booting while the rest of the cluster is performing a diagnostic shared memory dump, the booting instance could incorrectly perform a cluster takeover. This only occurs if automatic cluster takeover is set to 1 or if the --cluster_takeover option is passed to the dataserver. In environments without i/o fencing enabled this could lead to data corruption.

Workaround: Avoid booting an instance while a shared memory dump is taking place. Configure automatic cluster takeover to 0.

Adaptive Server Enterprise Cluster Edition 7. Known Problems


7.6 Known problems with the Adaptive Server plug-inThis section discusses Interactive SQL and Adaptive Server Enterprise plug-in issues and their workarounds.

7.6.1 Server properties information incorrectly shows beta release type[CR #552076] When viewing Adaptive Server ESD #4 server properties information from the plug-in, the release type incorrectly appears as “Beta.” This is caused by an incorrect identifier “B” in the version string, such as “Adaptive Server Enterprise/15.0.1/EBF 16386 Cluster Edition ESD#4/B/ia64/HP-UX B.11.23/ase1501ce/2581/64-bit/FBO/Sat Nov 22 03:30:25 2008.” The fourth field separated by “/” should be a “P” to indicate Production for this release.

Workaround: None; there is no impact to the server.

7.6.2 Instance folder can display junk characters when running in Chinese or Japanese

[CR #550812] When connected to a cluster and logical cluster without sa_role, the instances folder’s Address column displays junk characters when running in a Chinese or Japanese environment.

Workaround: Reconnect to the cluster as a user with sa_role.

7.6.3 Scheduled Job Properties dialog shows NullPointerException in Chinese[CR #550738] When you are in a Simplified Chinese environment, the Adaptive Server plug-in returns a null pointer exception in the Scheduled Job Properties dialog.

Workaround: None.

7.6.4 During create cluster command sybcluster reports a permission error[CR# 487524] sybcluster could report that the user does not have write permission to the directory in which raw devices are configured during the create cluster command. This happens when the name of the device is misspelled or no device by the specified name exists.

Workaround: To correct this problem re-enter the name of an existing device.



7.6.5 sybcluster, UAF and SSL do not use LDAP[CR #480444] The Users Guide to Clusters says that you can use LDAP for the cluster, and that if interface entries are not present in the quorum device, then LDAP can be used if configured in libtcl.cfg (libtcl64.cfg). Since the UAF does not use LDAP, this means that you cannot use sybcluster and Sybase Central to manage the cluster startup/shutdown effectively. In addition, SSL will not work with UAF.

Workaround: If you are using LDAP directory services, create an interfaces file with the cluster connection information for use by the UAF components such as sybcluster and Adaptive Server plug-in. There is currently no workaround if the Adaptive Server is using SSL encryption.

7.6.6 Dropping instance in Adaptive Server plug-in functionality cannot drop connected instance

[CR#478875] In the Adaptive Server plug-in a connected instance cannot be dropped. If you drop a connected instance, your connection is lost as soon as the instance is shutdown.

Workaround: Connect to another instance in the cluster before shutting down the instance you wish to drop.

7.6.7 Reconnecting Adaptive Server plug-in does not occur automatically[CR #469418] When the Adaptive Server plug-in is connected to a cluster through an instance that goes down, it does not automatically reconnect to another running instance.

Workaround: Use host:port to reconnect to another running instance.

Adaptive Server Enterprise Cluster Edition 8. Product Compatibility


8. Product CompatibilityTable 1: Adaptive Server Enterprise Cluster Edition interoperability with other products

For information on new features in Open Client/Open Server see the New Features Open Server™ 15.0 and SDK 15.0 for Microsoft Windows, Linux and Unix at http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc20155_1500/html/newfesd/title.htm&toc=/com.sybase.help.os_15.0/toc.xml

9. Documentation updates and clarificationsThis section describes updates and clarifications to Adaptive Server documentation.

9.1 Performance and Tuning GuideThis section describes updates and clarifications to the Performance and Tuning Guide.

9.1.1 Monitoring and Analyzing

Under “Transaction Management” the section titled “Preallocating Log Pages to Reduce Contention” should be removed. The dbcc tune (log_prealloc) feature has been removed.

Platforms Op

en C

lien

t/O

pen

Ser

ver1

2.5X

Op

en C

lien

t/O

pen

15.

0X

jCo

nn

ect

5.5

jCo

nn

ect

6.0.

x

AS

E O

DB

C b

y S

ybas

e 12

.5x

AS

E O

DB

C b

y S

ybas

e 15

.0x

AS

E O

LE

DB

by

Syb

ase

12.5

x

AS

E O

LE

DB

by

Syb

ase

15.0

x

AD

ON

ET

1.1

x

Rep

licat

ion

Ser

ver

15.0

.x

IBM AIX 6.1 X X X X X X X X X X

10. Technical support Adaptive Server Enterprise Cluster Edition


10. Technical supportEach Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.

11. Other sources of informationUse the Sybase Getting Started CD, the SyBooks™ CD, and the Sybase Product Manuals Web site to learn more about your product:

• The Getting Started CD contains release bulletins and installation guides in PDF format, and could also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.

• The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format.

Some documentation could be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the PDF files, you need Adobe Acrobat Reader.

Refer to the SyBooks Installation Guide on the Getting Started CD, or the README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.

• The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.

To access the Sybase Product Manuals Web site, go to Product Manuals at http://www.sybase.com/support/manuals/.

11.1 Sybase certifications on the WebTechnical documentation at the Sybase Web site is updated frequently.

Adaptive Server Enterprise Cluster Edition 11. Other sources of information


❖ Finding the latest information on product certifications

1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/.

2 Click Certification Report.

3 In the Certification Report filter select a product, platform, and timeframe and then click Go.

4 Click a Certification Report title to display the report.

❖ Finding the latest information on component certifications

1 Point your Web browser to Availability and Certification Reports at http://certification.sybase.com/.

2 Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

3 Select Search to display the availability and certification report for the selection.

❖ Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/.

2 Click MySybase and create a MySybase profile.

11.2 Sybase EBFs and software maintenance

❖ Finding the latest information on EBFs and software maintenance

1 Point your Web browser to the Sybase Support Page at http://www.sybase.com/support.

2 Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

3 Select a product.

4 Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

12. Accessibility features Adaptive Server Enterprise Cluster Edition


Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

5 Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.

12. Accessibility featuresThis document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.

Adaptive Server Enterprise version 15.0.1 ESD #4 and the HTML documentation have been tested for compliance with U.S. government Section 508 Accessibility requirements. 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.

The online help for this product is also provided in HTML, which you can navigate using a screen reader.

Note You might 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 Sybase Accessibility at http://www.sybase.com/accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.