Known Issues for Adaptive Server

Learn about known issues and apply workarounds for Adaptive Server. 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
684753	On HP-UX Itanium machines, database queries using the Java datatype may disconnect with a connection error and stack trace. Workaround: None.
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. Workaround: None.
662413	In some cases, alter database...log on or alter database...log off generates an error: "You must have the database `dbname` in single-user mode to perform an operation that either partially fills a hole or removes a partial disk fragment from the database." Workaround: Set single-user mode using: `sp_dboption single user`, then re-run the command.
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.
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.
595859	A single-engine Adaptive Server may stop responding when, after performing a Java task, additional engines are manually brought online. While running on a single engine, Adaptive Server may either stop responding, or cause connected clients to block indefinitely, generate a stack trace, or not process when the server performs a task that uses Java, as soon as additional engines are manually brought online. This problem occurs due to an issue with the HP-UX commercial off-the-shelf Java Virtual Machine. Workaround: Always have a minimum of two engines configured when starting Adaptive Server; this allows the HP-UX commercial off-the-shelf JVM to automatically target the highest engine number available. In addition, do not set any configuration options in Adaptive Server that targets engine 0 for the HP-UX commercial off-the-shelf JVM.
589269	Adaptive Server may stop responding during start-up. If you are using the in-memory database or relaxed-durability database feature, Adaptive Server may run into a timeslice error during start-up if it cannot access the license server as it starts. Workaround: Make sure Adaptive Server can access the license server.
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.
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)'
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.