Targeted CR List for ASE 15.7 ESD#3.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.
||Memory allocation failures appear in the ASE errorlog when the network memory pool is exhausted or when fragmentation of memory occurs due to memory that is not freed.
||The ASE Backup Server process has a memory leak when dumping and loading databases, which causes it to grow until it exceeds the memory limit.
||A 9254 error, "Could not locate schema version for object id '0' in the transaction log." followed by a 9204 error, "Could not locate schema for object with id = (0), current marker (0, 0)." may be reported in the error log when inserting or updating an in-row LOB datum and the ?multipath distribution model? is enabled. This will result in the Rep Agent Thread shutting down itself.
||ASE 15.7 fails to start during upgrade from ASE 12.5 due to the lack of enough ASE kernel resource memory being reserved.
||In the cases of extreme heavy loading, it is possible that CREATE CLUSTERED INDEX in parallel on a big table causes a small volume of data to be lost.
||The command ALTER DATABASE LOG OFF can result in the error 5057 ("The free space counts for the log are incorrect ...") being raised if the database has been loaded from a database dump where the command ALTER DATABASE LOG ON was run initially to extend the log.
||In rare cases of extreme heavy loading, it is possible that BCP/SELECT INTO a big table might lose allocation page entries from the OAM.
||The message "current process infected with 11" in the module 'ksct_startio' together with a stack trace which includes the modules 'ra_init_rs' and 'ra__connect_server' may be reported in the error log when the Rep Agent Thread attempts to open a new connection to the Replication Server and a previous connection attempt has failed.
||A 9284 error, "RepAgent( < dbid > ). Cannot allocate < value > bytes of memory. You may need to reconfigure the parameter 'replication agent memory size' with more memory.", followed by a 9219 error, "RepAgent( < dbid > ): Internal coding error. Rep Agent Thread for database ' < name > ' (dbid = < value > ) terminated abnormally with error. (major 92, minor 19)" maybe be reported in the error log if the Rep Agent Thread is recycled many times and compressed data is replicated.
||The message "current process infected with 11" in the module 'th_curunreservedpgs' may be reported when a session executes a SELECT statement that uses the T-SQL function "curunreservedpgs" while another session is in the process of extending the size of the current database with ALTER DATABASE command.
||If the user is granted system roles indirectly through a user defined role, execution of sp_addthreshold fails with error message 10353 "You must have any of the following role(s) to execute this command/procedure: ' < names > ' . Please contact a user with the appropriate role for help."
||Generate new release packages for ASE 15.7 ESD#3 and later.