Learn about known issues and apply workarounds for Adaptive Server. 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
.CR # | Description |
---|---|
684918 |
If High Availability (HA) is configured, sp_companion fails with this error: HA Config Error: Did not find any useful output from the Operating System command 'odmget HACMPresource'.
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. |
670302 |
The standard Adaptive Server 15.7 binary on AIX-64 may cause illegal instruction errors and core dumps when using a served license or an unserved sub-capacity license.
Workaround: The dataserver in the Adaptive Server 15.7 release fixes this issue, but is not optimized for performance. Following the 15.7 release, Sybase will provide a standard server binary, in a "one-off" release, that will fix this issue and also provide performance improvement. |
623788 |
Adaptive Server cannot start Job Scheduler on IPv6-enabled AIX servers for IPv4 addresses.
When you install Job Scheduler on an IPv6-enabled AIX system using an IPv4 address that starts with the first set of numbers smaller than 128, the installation may fail, and you may see a message similar to:
Job Scheduler Task failed to spawn an Agent. When this occurs, the Job Scheduler log shows:
Socket bind failed. Errno:22 Workaround: Disable IPv6 on the system. |
595923 |
There are two known issues with transfer table:
Workaround: None. |
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:
Workaround: Re-create the abstract plans associated with the stored procedure. |
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. |