Known Issues for Adaptive Server Cluster Edition

• Two or more nodes survive the node failure
• Failover recovery is needed for a multi-database transaction that has completed only the first phase of the two-phase commit protocol.

If the database is replicated, the stale log pages may also result in errors during replication.

Workaround: None.

When a session executing a query using session temporary tables is terminated by another session, and statement cache is enabled in Adaptive Server, the error log reports this error: Current process infected with 11 in the module s_free, and may include a stack trace with modules clean_process and kill_proc. Under some circumstances, Adaptive Server also reports error 6103: Unable to do cleanup for the killed process.

Workaround: None.

If you create a cluster using sybcluster or Adaptive Server plug-in and enter dev/vx/rdsk/raw1g4 for the path to the master device or other database device, sybcluster and Adaptive Server plug-in correctly detect the device managed by VCS. If you create a cluster and enter /work1/raw1g4 for the path to the master device, sybcluster or Adaptive Server plug-in prints:

"This device is not managed by Veritas Cluster File System or Veritas Volume Manager.
     Do you want to continue (Y/N)? "

Workaround: Ignore this message. sybcluster cannot validate a VCS raw device that uses a link path, but can use the link path to build the cluster.

Workaround: Convert the bigtime value to bigdatetime before executing the Transact-SQL function dateadd.

• 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: Re-create the abstract plans associated with the stored procedure.

If Adaptive Server users execute Java-in-SQL statements while executing sp_engine "offline", engine_id, Adaptive Server may report stack traces in its error log if the engine is hosting a JVM.

Workaround:Do not take the engine offline until Java clients are disconnected. Instead, take the engine offline that is not hosting the JVM.

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

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

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

Workaround:Set the environment variable XKEYSYMDB:

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

When you initially execute the uafstartup.sh script, you may receive an error stating that you do not have permissions to access some files. This problem is caused by latency issues in the NFS file system layer, and occurs only when you attempt to start multiple Unified Agents simultaneously in the current $SYBASE directory.

Workaround: Wait a few seconds, then retry.

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 may have already created some configuration files and devices.

Workaround: Before you restart a wizard session:

1. Stop the srvbuildres or dataserver utilities, if either are running.
2. Stop the Unified Agents on all nodes.
3. Remove the directory with the name of the cluster you tried to create from the $SYBASE_UA/nodes/node_name/plugins directory.
4. Remove the interfaces file entries for the cluster you tried to create.
5. Restart the Unified Agents on all nodes.

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 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 may lead to data corruption.

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

Create index aborted on duplicate rows.

Workaround: Run sp_sysmon with the clear option.

Workaround: None.

When you configure the Job Scheduler Self Management feature for an Adaptive Server localized for Simplified Chinese, you may receive an error saying that a varchar datatype cannot be converted to a date. The Job Scheduler configuration process stops at this point.

Workaround: Do not configure the Self Management feature for Simplified Chinese.

When you attempt to create a Job Scheduler schedule using the Adaptive Server plug-in for an Adaptive Server that is localized for Simplified Chinese, you may receive an error indicating that the varchar datatype cannot be converted to a date.

Workaround: Localize the Adaptive Server for Simplified Chinese before configuring Job Scheduler.

When you start the Monitor Client GUI in an environment using LDAP instead of an interfaces file, the Monitor Client GUI cannot connect to any servers.

Workaround: Create an interfaces file with entries for the servers that are monitored and use this with the Monitor Client GUI.

rs_init in Replication Server version 12.6 and earlier cannot create an RSSD database in Adaptive Server Enterprise version 15.0 or later.

Workaround: If you do not use an Embedded RSSD (ERSSD), manually create the RSSD database before using rs_init to create a new Replication Server. See the Replication Server Administration Guide.