Known Issues for Adaptive Server Cluster Edition

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

Note:

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 and Workaround
630077	In rare cases, out-of-date log pages persist in cache after a node failure in cluster configurations if both these conditions occur: 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.
618851	Terminating a session that is executing a query using session temporary tables results in errors. 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: Use one of these: Turn off the statement cache. Use traceflag 467 in the command line. If there is a successfully compiled plan in the cache, use traceflag 299 in the command line.
615890	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.
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.
612683	sybcluster and Adaptive Server Plug-in can validate Veritas Cluster Server (VCS) raw device and file systems with the actual path name, but cannot validate them for link paths. For example, Name of a VCS raw device is raw1g4. The actual path to the device is dev/vx/rdsk/cfsdg/raw1g4 . The link path to the device is /work1/raw1g4. The link to the device is obtained by executing `ln -s /dev/vx/rdsk/cfsdg/raw1g4`. 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.
612447	When you add any value into a bigtime field, and execute select dateadd using that field as a parameter, you see an overflow error. Workaround: Convert the bigtime value to bigdatetime before executing the Transact-SQL function dateadd.
612286	You cannot load database and transaction log dumps from Adaptive Server 15.5 Cluster Edition into a database on Adaptive Server 15.0.x or 15.5 (nonclustered) versions. Workaround: Use one of these methods to load the database or transaction dump from Adaptive Server 15.5 Cluster Edition: Load the database or transaction dumps into a database on Adaptive Server 15.5 Cluster Edition. Use Replication Server to replicate the database or transaction dump. Use sybmigrate, the Sybase migration tool. See the Utility Guide.
607464	Recovering a template displays an error. In some cases, when a database that is used as a template for creating a database with a durability of no_recovery is being recovered, a 937 error may be reported to the error log: The database '<template_dbname>' is currently unavailable. It is being used to create a new database. Workaround: This error does not impact the correct recovery of any databases. Following the completion of recovery, however, the default data cache may have a memory pool configuration that differs from the configured values. Execute sp_poolconfig and reconfigure the default data cache to required values.
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.
595859	Differing byte orders may generate an error during database dump. When you load a dump of a database that has a durability of no_recovery or at_shutdown, you may see: Adaptive Server cannot load this database because the database that was dumped was not quiescent when the dump was performed. This occurs when you load a dump of a database from one platform to another platform with a different byte order. Workaround: None.
582815	Under certain conditions, you may need to re-create abstract plans associated with stored procedures that include the built-in function isnull. These are the conditions: One of the parameters to isnull is a char datatype and another is a literal. enable literal parameterization is set to on. Workaround: Re-create the abstract plans associated with the stored procedure.
572710	Taking an engine offline while Java clients are connected may cause an error. 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.
551972	Using Java in the database to create a file fails on HP-UX. Due to 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)'
487525	Starting Unified Agent may report a permissions error. 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.
485070	Restarting an unfinished Cluster Creation wizard session 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: Stop the srvbuildres or dataserver utilities, if either are running. Stop the Unified Agents on all nodes. Remove the directory with the name of the cluster you tried to create from the $SYBASE_UA/nodes/node_name/plugins directory. Remove the interfaces file entries for the cluster you tried to create. Restart the Unified Agents on all nodes.
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 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.
466370	If Adaptive Server is configured for a large number of spinlocks, you may see a performance issue with sp_sysmon. This is because index creation on the worktable used by sp_sysmon fails due to duplicate key values. sp_sysmon reports error 1508: Create index aborted on duplicate rows. The large number of spinlocks on Adaptive Server account for a large number of rows in the table, and result in duplicate key values. sp_sysmon performance is slower due to the lack of an index on the worktable. Workaround: Run sp_sysmon with the clear option. Note: The clear option will reset the monitor counter values on your server.
462184	Monitor Server and Historical Server do not work with an Adaptive Server that has set its net password encryption reqd options set to 1 or 2. Workaround: None.
439406	Configuring Job Scheduler Self Management for Simplified Chinese 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.
439404	Creating Job Scheduler schedules for Adaptive Server with 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.
400784	Starting Monitor Client GUI fails when the Lightweight Directory Access Protocol (LDAP) server is used. 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.
382874	Creating RSSD database fails with earlier versions of Replication Server. 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.