Known Issues for Adaptive Server Cluster Edition

The load database … with listonly=load_sql command may generate load commands which, if executed, may require manually altering 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: Manually alter the target database.

The show_condensed_text function returns a NULL value for queries in the statement cache when the enable literal autoparam configuration parameter is enabled.

Workaround: Do not use the show_condensed_text function when enable literal autoparam is enabled.

A cumulative dump cannot be used as a meta-data file for the sybdumptran utility.

Workaround: None.

load database with verify does not support automatic physical database rearrangement.

If load database with verify is executed, the automatic remapping between the source and target database to ensure that the data segment is on data devices and the log segment is on log devices is not performed. This may result in the behaviour of releases prior to 15.7 SP100, which is the data segment may be mapped to log devices and the log segment may be mapped to data devices in the target database.

Workaround: Sybase recommends that you use the dump database with verify command to verify the database.

Solaris Asynchronous I/O Performance

Applications running against Adaptive Server on the Solaris platform in threaded mode may experience poor performance. The solution requires a fix for Oracle Bug 16054425 and then setting the configuration parameter solaris async i/o mode to 1. This option is effective if Adaptive Server is running in threaded kernel mode. If solaris async i/o mode is set to 1 without a patch for Oracle Bug 16054425, Adaptive Server may report 694 or 823 errors and require restarting Adaptive Server. For more information, refer to CR 697533 - Solved Cases on the http://www.sybase.com/support web site.

getdate() sporadically returns clock time in UTC rather than the configured timezone.

On Solaris 10 updates earlier than Update 11 (Generic_147441-23), Adaptive Server running in kernel threaded mode might experience a temporary time shift from local time to GMT. For example, time value of 10:00 might change to 18:00 for a short period.

Workaround: Upgrade the Solaris 10 OS to an update level of 11 or later.

In active-active or active-passive cluster configurations, you can configure RepAgent to run on only one node of the cluster. In rare circumstances, when RepAgent reads an older image of database log pages that is on disk while the latest image is on another node, you may see Adaptive Server 624 and 69x errors.

Workaround: Sybase recommends that for:

• Active-passive configuration – run RepAgent on the active node to ensure that data and log pages are on the same node as RepAgent.
• Active-active configuration – start Adaptive Server with the 16872 trace flag to prevent log page corruption and 69x errors. However, using this flag degrades the server performance.

This message is reported by Open Client applications connecting to Adaptive Server Enterprise:

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 Kerberos message confidentiality service is turned on.

Workaround: Reconnect to the server with confidentiality service turned off.

select for update support exists only for datarows-locked pages.

For the sp_opt_querystats stored procedure to succeed, the value of the srvnetname column for a loopback remote server must be the name of a cluster in the cluster interfaces file and not the name of a cluster instance.

Workaround: Make sure that the srvnetname column for the loopback remote server is the name of the cluster.

An error is raised when renaming a read only database

Error (3906) can occur when executing sp_renamedb on a database that has 'read only' status. Also, when attempting to turn off the 'read only' status on a database that you have attempted to rename, error 3501 is raised.

Workaround: Execute sp_renamedb stored procedure from master database context as follows:

use master   
go       
sp_renamedb <dbname>, 
<new_dbname>   
go 

Workaround: None.

• When creating a unique index that is using 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.

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

cpuinfo.mechanism=NOAPICCHECK

(sh) export SYBASE_SAM_CPUINFO=CPUID (csh) setenv SYBASE_SAM_CPUINFO CPUID

If you start an instance while the rest of the cluster is performing a diagnostic shared memory dump, the instance that is starting may incorrectly perform a cluster takeover. This occurs only if automatic cluster takeover is set to 1, or if the --cluster_takeover option is passed to the data server. In environments without i/o fencing enabled, this may lead to data corruption.

Workaround: Do not start an instance during a diagnostic shared-memory dump. Configure automatic cluster takeover to 0.