Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
 
 
 
 
 

 
 
CLICK TO EXPAND NAVIGATION
CLICK TO EXPAND NAVIGATION
 
 
 
 
Support > Technical Documents > Document Types > Technote > Targeted CR List for ASE 15.7 SP122  
RSS Feed
 
 
 

Targeted CR List for ASE 15.7 SP122

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.


Bug ID Description
684459 On the AIX platform, improve the mapping of addresses to function names in SAP ASE stack traces. This will provide a superior mapping when the address is in a shared library.
757824 When running in SAP ASE process mode under heavy load in a multiengine environment, an engine may become CPU bound when handling network cancel requests arising from attentions received either from the client or from kill commands. In the event that the network listener was on the run queue of the engine which has become CPU bound as above, it may be impossible to establish new logins to the server.
758328 A poor index may be chosen for a join, if the selectivity of previous joins is estimated to be 0 rows (likely caused by a predicate selecting an 0.0 weight range cell in the histogram). The optcriteria avoid_zero_weight_histograms or trace flag 16991 will adjust selectivity estimates so that at least one row will be selected when joining histograms. Note that ase_current will not enable this functionality, and that "set avoid_zero_weight_histograms on", a user defined optgoal which includes avoid_zero_weight_histograms or trace flag 16991 is needed.
759142 When update statistics is performed on a character column with a non-binary character set, and in addition update statistics uses the consumers phrase, then there is the possibility of many small weight frequency cells following a zero weight range cell. This may cause poor query plan selection if a predicate selects a zero weight histogram cell. optcriteria cr759142 will avoid generation of small frequency cells following a zero weight range cell, when the consumers phrase is used in update statistics to generate stats on a mostly unique non-binary character set column.
759188 When a merge join is being used and if the inner table has in-row LOB columns with NULL values, an infected with 11 (SIGSEGV) stacktrace referencing the function sendtext() may be reported in the SAP ASE errorlog.
759245 If there are equality predicates or joins which are used for index keys, then occasionally an index which has few positioning keys specified than another index will be chosen. If 2 indexes have only equality predicates or equality joins used for keys, then a heuristic is added to choose the index with more limiting keys if those keys cover all the limiting and filtering keys of another index. The optcriteria EQUALS_SCAN_SUPERSET and trace flag 16989 will apply the heuristic to index scan which are not the inner of a nested loop join. The optcriteria EQUALS_NLJOIN_SCAN_SUPERSET and trace flag 16990 will apply the heuristics to all index scans. Note that the optcriteria are not turned on by any optgoal, and a SET command, user defined optgoal, or trace flag is needed to enable the heuristic
759377 In a very rare situation, SAP ASE may panic and shutdown if sp_sysmon is being run and a connection disconnects at the same time.
759728 In situations where a lot of create tables are run in parallel and the SAP ASE configuration has 'enable inline default sharing' set, CREATE TABLE commands may not perform well.
760187 The index id is incorrectly reported as 0 in the SAP ASE error message number 12301 - "Internal error: the index (id = < ID > ) and the data for row ( < page > , < row > ) in table ' < table > ', database < db > are inconsistent; data is marked deleted but index is not. Aborting the transaction."
760248 There may be situations where parallel create index with "utility statistics hashing" is turned on, but then a worker thread may hang due to incorrect error handling.
760274 In rare circumstances when running UPDATE INDEX STATISTICS, SAP ASE may report time slice error in the SAP ASE errorlog. The stack trace will be inside the function close_table().
760661 Optimize the procedure cache allocation. This vastly speeds up start-up for SAP ASE configured with a very large procedure cache.
760673 If the data cache is configured small, SAP ASE may report a 'cache too small' 3478 error when the new sort buffer algorithm is used (CR 750937).
760684 A 707 error "System error detected during attempt to free memory at address < addr > . Please consult the ASE error log for more details." may be raised by SAP ASE when multiple SAP ASE connections are executing parallel CREATE INDEX commands.
761036 Under rare conditions, when doing an isolation level 0 scan, error 12301 - "Internal error: the index (id = < num > ) and the data for row ( < page# > , < row# > ) in table ' < table name > ', database < dbnum > are inconsistent; data is marked deleted but index is not. Aborting the transaction." may be reported.
761555 Some of the cache buffers used for sort are not claimed and unclaimed correctly. This can lead to a performance impact if cache swap occurs.
762174 An SAP ASE stack trace in function SearchEngine::_SeFindOptimal could occur after a lengthy optimization, most likely after an aggregate with a GROUP BY in which the GROUP BY columns originate from multiple tables.
762281 The version of OpenSSL used has been upgraded to OpenSSL 1.0.1g

 

Related Links

DOCUMENT ATTRIBUTES
Last Revised: May 14, 2014
Product: Adaptive Server Enterprise
Technical Topics: Error Message, Database Admin, Bug Information, Troubleshooting
  
Business or Technical: Technical
Content Id: 1099393
Infotype: Technote
 
 
 

 
© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics