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 |
---|---|
739773 | The load database … with listonly=load_sql command may generate load commands which, if executed, may require manually altering the target database for the load to succeed. This issue can occur in cases where an alter database off command was run on the source database. Workaround: Manually alter the target database. |
739080 | The show_condensed_text function returns a NULL value for queries in the statement cache when the enable literal autoparam configuration parameter is enabled. Workaround: Do not use the show_condensed_text function when enable literal autoparam is enabled. |
738744 | A cumulative dump cannot be used as a meta-data file for the sybdumptran utility. Workaround: None. |
738675 | load database with verify does not support automatic physical database rearrangement. If load database with verify is executed, the automatic remapping between the source and target database to ensure that the data segment is on data devices and the log segment is on log devices is not performed. This may result in the behaviour of releases prior to 15.7 SP100, which is the data segment may be mapped to log devices and the log segment may be mapped to data devices in the target database. Workaround: Sybase recommends that you use the dump database with verify command to verify the database. |
719212 | Solaris Asynchronous I/O Performance Applications running against Adaptive Server on the Solaris platform in threaded mode may experience poor performance. The solution requires a fix for Oracle Bug 16054425 and then setting the configuration parameter solaris async i/o mode to 1. This option is effective if Adaptive Server is running in threaded kernel mode. If solaris async i/o mode is set to 1 without a patch for Oracle Bug 16054425, Adaptive Server may report 694 or 823 errors and require restarting Adaptive Server. For more information, refer to CR 697533 - Solved Cases on the http://www.sybase.com/support web site. The fix for this issue is to install the Oracle patch for your platform:
|
717871 | getdate() sporadically returns clock time in UTC rather than the configured timezone. On Solaris 10 updates earlier than Update 11 (Generic_147441-23), Adaptive Server running in kernel threaded mode might experience a temporary time shift from local time to GMT. For example, time value of 10:00 might change to 18:00 for a short period. Workaround: Upgrade the Solaris 10 OS to an update level of 11 or later. |
696072 | In some Cluster Edition
configurations, Adaptive Server 624 and 69x errors may occur 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. 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, you may see Adaptive Server 624 and 69x errors. Workaround: Sybase recommends that for:
|
695625 | Confidentiality
service causes error. 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. |
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. |
639813 | An error is raised when renaming a read only database Error (3906) can occur when executing sp_renamedb on a database that has 'read only' status. Also, when attempting to turn off the 'read only' status on a database that you have attempted to rename, error 3501 is raised. Workaround: Execute sp_renamedb stored procedure from master database context as follows: use master go sp_renamedb <dbname>, <new_dbname> go |
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. |
576652 | SySAM2
enabled products incorrectly determine the number of cores and chips on
quad-core processors. This may be as a result of your Adaptive Server small business edition or chip license not being activated and having gone into a grace period. Workaround: Remove this line from your
SySAM properties file, if it
exists:
cpuinfo.mechanism=NOAPICCHECKIf the problem still remains, set the following environment variable, then run the products: (sh) export SYBASE_SAM_CPUINFO=CPUID (csh) setenv SYBASE_SAM_CPUINFO CPUIDIf the problem still remains, please contact Sybase Technical Support. |