Targeted CR List for ASE 15.7 SP102
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.
||The command DBCC SETTRUNC ('ltm', 'end') extends the transaction log with one page before setting the Secondary Truncation Point to the new end of the log so as to avoid unwanted data replication.
||ASE on Windows crashes due to system exception (0xc0000005) generated by a storage access violation with error message "attempted write to memory location 0000000000000000 from instruction at location 0x0000000000000000".
||In rare circumstances, the RepAgent thread may fail to terminate and hang in the module 'upsleepgeneric'. The execution for DBCC STACKTRACE( < RepAgent_spid > ) would indicate the RepAgent sleeping in the modules 'usctcancel' and 'ksctsuspend'.
||Under some rare circumstances, a shrink-database operation can encounter errors that kill the processing thread but do not clean up the memory it was using.
||Under some rare circumstances, a shrink-database operation can encounter errors of index not consistent on DOL table.
||When RepAgent terminates abnormally with an error while connecting to Replication Server, the connection is not closed and the associated session is still held on Replication Server mistakenly.
||If a database is configured to 'allow incremental dumps' updates to pages that happen when bringing the database online could be missing from the next incremental dump.
||The message, "Current process infected with signal 11", together with a stack trace that includes the module scan_getrow() may be reported in the error log when executing DBCC CHECKTABLE if a shrink- database operation is not completed and the dataserver is rebooted.
||Under some rare circumstances, a shrink-database operation can encounter errors of index not consistent on DOL tables and little endian platform.
||In some cases, runtime rollback of a transaction that is done in parallel (parallel CREATE INDEX, SELECT INTO, REORG REBUILD or ALTER TALBLE (with data copy)) will be incomplete leaving the database in an inconsistent state.
||Under rare circumstances the Rep Agent may report a 9219 error with state number 61, "RepAgent( < dbid > ): Internal coding error", when processing LOB data resulting in the Rep Agent termination.
||A 4306 error, "There was activity on database since last load, unable to load", may be reported when loading a database or transaction log dump of a database whose size is smaller than the target database into which it is being loaded, thereby breaking the load sequence.
||A 691: "Encountered invalid logical page ' < page > ' while accessing < partition > . This is an internal system error. Please contact Sybase Technical Support." error followed by a stack trace that contains the modules getpage_with_validation() and wrongpage() may be reported in the error log under the following conditions: (1) The configuration option "streamlined dynamic SQL" is enabled, either directly or by enabling functionality group and (2) A dynamic prepared INSERT or UPDATE statement is executed on a table that has been created with deferred_allocation and (3) The prepared statement has been executed successfully at least once and (4) The target table that is inserted/updated is dropped and re-created as a defered_allocation table and (5) The dynamic INSERT/UPDATE query is re-executed from the same ASE connection.
||When DDL replication is ON, the execution of a DDL command as a prepared statement aborts with error 11314. Trace flag 9152 can be used to allow the DDL command to proceed without being replicated.
||An undetected deadlock might occur between a process that ran out of syslogs space and has crossed the last chance syslogs threshold and another process that is attempting to expand the syslogs size by executing an ALTER DATABASE command. The output of dbcc stacktrace( < spid > ) command for one of these two processes will show the modules 'th_sleep_on_lct' and 'upsleepgeneric' whereas for the other process the modules 'writeLock' and 'upyield'. An ASE restart is needed to unblock this situation.
||The message, "Current process infected with signal 11", in the module 'dam_prepare_dump_end' together with a stack trace which includes the modules 'dpdb_main' and 's_execute' may be reported in the error log when a DUMP DATABASE command is executed and the database option 'allow incremental dumps' is enabled and the system table SYSDAMS contains an extent that is the first extent of an allocation unit causing this table to have a number of pages that is not a multiple of 8.
||During BCP for a table which has undergone an ALTER TABLE DROP column with no datacopy operation, ASE may send wrong default values for columns to the client.