Targeted CR List for ASE 15.5 ESD#5.1
The purpose of this document is to help Sybase customers obtain a general idea of potential bug fixes in future Adaptive Server Enterprise (ASE) EBF releases. Please be sure to read the Disclaimer and General Notes below.
If the EBF has been released, check the CR list and coverletter at the sybase.com EBF/Maintenance site: http://downloads.sybase.com/swd/base.do
Disclaimer: This document lists the targeted (not committed) fixed CR list for the release listed above. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. Sybase does not commit to releasing EBFs on the specified dates or to including the CR fixes in the said EBF. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that Sybase may decide not to release an EBF that was previously scheduled for release.
||In ASE Cluster Edition, dropping a database and recreating a new local temporary database reusing the same database ID may result in issues during runtime.
||When the ASE ESD number is not an integer (e.g. 1.1, 4.1 or 5.1 etc), then anything using the sp_versioncrack stored procedure (e.g. sp_spaceusage) may encounter a 249 error (conversion error).
||The 420 message, "The TEXT, IMAGE and UNITEXT datatypes cannot be used in an ORDER BY clause or in the select list of a query in a UNION statement.", may be reported when selecting a TEXT column from a proxy table in a UNION ALL query.
||In ASE Cluster Edition, changing a database from a non mixed-log-and-data to mixed-log-and-data may invalidate an internal assumption and server may exhibit unknown issues.
||In rare circumstances, the message "current process infected with 11" together with a stack trace which includes the module "jvmh_utl_printn" may be reported in the error log when ASE attempts to bootstrap the COTS JVM. This will result in Java operations being impossible to execute.
||Under certain circumstances, in ASE Cluster Edition, CREATE DATABASE immediately following a DROP DATABASE may hang with messages in the error log indicating failure to reclaim active locks.
||The message, "The Begin Timestamp= < ts1 > of the completing transaction in database < dbid > is lower than the Database Commit Timestamp= < ts2 > ", may be printed in the error log together with a stack trace that contains the modules dbts_commits_remxdes() and xact_end_session() when chained transactions are used, and ASE is started with the diagserver binary.
||When an installation is created by ASE version 15.0.3 or before, then upgraded to 15.5, and then further upgraded to 15.7 or later, then if the upgraded server is downgraded back to 15.5, the booting of the 15.5 server may encounter a segmentation fault. This fault prevents recovery from completing.