Targeted CR List for ASE 15.7 SP103
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.
|738117||The message, "Current process infected with signal 11", followed by a stack trace that includes the module ssql_release() or ssql_choose_victims() may be reported in the ASE error log when the statement cache is full in a high concurrency ASE environment.|
|742407||Add extra diagnostics for the data change fragment pool in order to help catch incorrect memory accesses of the data change fragment pool and thus also improve robustness.|
|743637||MERGE triggers on DOL tables may return the incorrect number of rows for the inserted table: too few rows for the UPDATE trigger and possibly too many rows for the INSERT trigger.|
|743922||In rare circumstances, a SELECT FOR UPDATE query may return successfully without getting the exclusive lock on the row, even if READPAST mode was not being used. This only affects the AIX platforms and has been identified as an AIX compiler optimization issue when high levels of optimization are used on a specific module.|
|744714||sqlupgrade and upgrade for unix to have dynamic timeout.|
|745873||In rare cases a 692 error, "Uninitialized logical page ' < pageno > ' was read while accessing database ..." may be reported sometime after loading a database dump that was taken of a database in both Enterprise Edition and Cluster Edition, that had been created on devices with ?direct i/o? turned on, or taken of a database in a Cluster Edition system only, that had been created on devices with ?dsync? turned on.|
|746562||A trigger defined on MERGE statement executing both INSERT and UPDATE actions may return incorrect rows for inserted table for the INSERT action. This happens if the same trigger is defined for both INSERT and UPDATE: "create trigger T on TAB for insert,update as ..."|
|746597||In some cases an error may be reported in the ASE errorlog, accompanied by a stack trace with the functions kbfalloc() and ptn__pdes_init_colupdcnt() in the stack.|