Targeted CR List for ASE 12.5.4 ESD #11.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.
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.
|722777||ASE does not respond and appears to hang when certain invalid packets are sent to it.|
|729766||A new configuration value of '2' is added to configuration option 'enable xml' for external entity reference in XML documents, ie, set "sp_configure 'enable xml', 2" for external entity reference in XML documents.|
|729919||In very rare situations where incorrect port number is specified for sp_listener, subsequent calls to sp_listener might fail.|
|730183||Extended stored procedures added using sp_addextendedproc are malformed leading to failure of the extended stored procedure. sp_helpextendedproc shows an extraneous '[' character in the DLL name.|
|736550||Under rare circumstances a 696 error: "An attempt was made to read logical page ' < page# > ' for database ' < dbname > ' ( < dbid > ), object ' < tablename > ' ... from disk. Wrong logical page ' < page# > ' was brought into cache 'default data cache'." may be reported in the error log for allocation pages after the execution of CREATE, ALTER or LOAD DATABASE commands in an ASE installation using a page size that is greater than 2K-bytes and when during their execution the message "No large buffers were available, so pages are being cleared by writing each page separately. Please be patient" is reported. Alternatively a 2529 error, "Table Corrupt: Attempted to get page < page# > , partition ID 99; got page < page# > , partition ID 99." may be reported by DBCC CHECKALLOC.|
|737762||Under rare circumstances backup server may produce unpredictable text attached to the dump trailer.|
|738322||Backup Server introduces a remote access control feature that prevents remote dumps and loads and execution of remote procedure calls (RPC) from any client or server running on unauthorized servers. Local dumps are not affected by this feature. Authorization to dump or load, to or from Backup Server is achieved by including the authorized hosts in the host.allow access control file. The default location of hosts.allow file is $SYBASE. The location and name can be changed using the Backup Server parameter -h.|