Known Issues for Adaptive Server Cluster Edition

Learn about known issues and apply workarounds for Adaptive Server Cluster Edition. Known issues are listed in descending order of Change Request (CR) numbers.

Sybase does not include system problem reports (SPRs) and closed problem reports (CPRs) with Adaptive Server Enterprise. You can search the Web site for solved cases. Click Support > Services > Solved Cases.

CR #	Description
714061	*The forwrowcnt* column in the systabstats table does not change after running online reorg rebuild** The number of forwarded rows in the forwrowcnt column of the systabstats table does not zero out after running the online reorg rebuild command. Workaround: Run update statistics on the table after running online reorg rebuild.
713855	An exception is raised when migrating from Adaptive Server versions, 12.5.4 through 15.0 to version 15.7 ESD #2 using sybmigrate An exception is raised due to inconsistencies between roles that exist in the sysusers table of the source server and the roles that exist in the sysusers table of the target server. Workaround: In the source and target server, run the query: `select u.* from sysusers u, syssrvroles r where u.name = r.name and r.srid < 31 order by u.uid` Compare the results of the above query retrieved from the source and target servers. In source server, insert rows returned from the query into master.dbo.sysusers table. These rows contain server roles that exist in target sysusers table and do not exist in the source sysusers table. Run `sybmigrate -m setup` Delete the same rows that you inserted in step 3 from source's master.dbo.sysusers. For example, when migrating from Adaptive Server 15.0 to Adaptive Server 15.7 ESD #2. Run the following query in the source and target servers: `select u.* from sysusers u, syssrvroles r where u.name = r.name and r.srid < 31 order by u.uid` Your query shows you need to insert one row (-2, 16398, 16398, 'keycustodian_role', NULL) into the source master.dbo.sysusers table. Run the following SQL in the source server: `use master` `exec sp_configure 'allow updates to system tables' 1` `insert sysusers values(-2, 16398, 16398, 'keycustodian_role', NULL)` `exec sp_configure 'allow updates to system tables', 0` Run `sybmigrate -m setup` Run the following SQL in the source server: `use master` `exec sp_configure 'allow updates to system tables' 1` `delete sysusers where name = 'keycustodian_role'` `exec sp_configure 'allow updates to system tables', 0`
713631	Create index in parallel with descending keys may fail with error 832 In some cases, when the creation of an index in parallel mode using the WITH CONSUMERS=`number` option is executed, and the configuration parameter enable functionality group is on, Adaptive Server may generate the following error: `Error 832: Unable to place buffer 0x4e498f68 holding logical page 2344 in sdes for object <table name> - there is no room in sdes aux keep pool.` The following is an example of a command that may generate the error message: `1> create index ind on tab(a desc,b, c) with consumers = 3` `2> go` Workaround: This is an internal error that does not lead to data corruption. Traceflag 549 could be used to avoid running into this error.
713464	Create index in parallel with descending keys may fail with error 1503 In some cases, when the creation of an index in parallel mode using the WITH CONSUMERS=`number` option is executed, and the configuration parameter enable functionality group is on, Adaptive Server may generate the following error: `Msg 1503, Level 20, State 2: Line 1: Sort Internal Error:` `The Root page of right/left sub-index tree is missing. Command has been aborted.` The following is an example of a command that may generate the error message: `1> create index ind on tab(a desc,b, c) with consumers = 3` `2> go` Workaround: This is an internal error that does not lead to data corruption. Traceflag 549 could be used to avoid running into this error.
713189	Using sybcluster to add an instance from an XML input file fails When configuring an auxiliary server (xpserver or backupserver) in an Adaptive Cluster, an input error is raised when using an XML input file to add an instance from the sybcluster tool. The input error is raised when attempting to validate the XML input file. Workaround: Use interactive mode to add a new instance to a cluster using sybcluster when configuring an auxiliary server for a cluster server.
712783	The same row is returned by multiple queries on MDA FDP tables in Cluster Edition When queries are executed on the Monitoring and Diagnostic FDP tables in an Adaptive Server Cluster Edition server, the same row may be returned in multiple result sets. Workaround: None.
711328	Using sybcluster to add an instance in interactive mode fails When using interactive mode, adding an instance on a new node of an existing cluster will cause an infinate loop when entered on a new tempdb device. The infinate loop is a prompt to enter a tempdb device path. Workaround: Exit the session and restart sybcluster. To add the instance, enter "Y" to reuse the Cluster Agent plugin at the sybcluster prompt.
696072	In some Cluster Edition configurations, Adaptive Server 624 and 69x errors may occur in rare circumstances during database replication of a database or replication of tables within a database. In active-active or active-passive cluster configurations, you can configure RepAgent to run on only one node of the cluster. These errors may occur 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. 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.
695625	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.
694912	The sybcluster localize utility does not function properly and exceptions are raised. If the $SYBASE/SYBASE_ASE/locales directory contains files or directories that are not server-related locales files, the sybcluster localize utility does not function properly. If unrelated files are in the locales directory, the localize command aborts and raises an exception at the beginning phase. If an unrelated directory is in the locales directory, the charset selection menu is shown incorrectly and localize may abort during further processing. Workaround: Do not place files or directories unrelated to localization in the $SYBASE/SYBASE_ASE/locales directory.
684556	\ The select for update semantics introduced in version 15.7 do not support datapages-locked tables. select for update support exists only for datarows-locked pages.
680041	The value of the server network name as defined by the srvnetname column for a loopback server must be the name of the cluster. 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.
615204	If enable DTM is set, the distributed recovery feature is disabled and all databases are recovered only on the cluster coordinator, rather than on different instances of the cluster. Workaround: None.
595923	There are two known issues with transfer table: 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.
483651	Incorrect cluster failover may occur during diagnostic shared-memory dump. 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.
478875	In the Adaptive Server plug-in, you cannot drop a connected instance; your connection is lost as soon as the instance is shut down. Workaround: Before shutting down the instance to drop, connect to another instance in the cluster.