SAP Knowledge Base Article - Preview

2077434 - Targeted CR List for ASE 16.0 GA PL02 - SAP ASE


The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in Adaptive Server Enterprise (ASE) 16.0 GA PL02. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the

Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.

CR Number



On AIX platform, the mapping of addresses to function names in SAP ASE stack traces has been improved. This will provide a superior mapping when the address is in a shared library.


The unreserved page count might be off by the number of pages of the table SYSDAMS if SAP ASE uses the OAM pages to calculate the free space counts. The database fragments containing pages of the system table SYSDAMS will show the space used by this table as free.


In rare circumstances, when running TRUNCATE TABLE on a very large table, the table does not show up on monProcessObject.


MERGE into statement with columns having decrypt defaults in their ON clause may not produce expected results when the user does not have decrypt permission.


A 14108 error, "Could not find partition descriptor for objid < obj_id > , indid < indid > , ptnid < ptn_id > in dbid < db_id > " will be raised when creating a local index on a partitioned table if the database option 'allow incremental dumps' is enabled.


Stored procedures with application context functions take a very long time to execute because SAP ASE accesses system catalogs each time for protection checks.


In rare cases, if SAP ASE server crashes during a ALTER TABLE UNPARTITION or MERGE PARTITION transaction, after recovery, DBCC CHECKTABLE of the table may report a 2583 error, "Number of data pages (#) counted by DBCC differs from count in the data OAM (#) for dbid < db_id > object < obj_id > ".


The message, "Current process infected with signal 11", followed by a stack trace that includes the modules def_insert() and xls_sessionid() may be reported in the error log when an INSERT query is run in DEFERRED mode.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module mda_fill_and_send_monProcessStatement() may be reported in the error log when running a query of the form SELECT ... INTO temptable.


An assertion will occur if encrypted columns is enabled and there are external passwords that need to be recreated.


Arithmetic overflow occurred in procedure 'sp_sysmon_kernel'.


The error message 7786 has been updated to include the server user name.


In some special cases, the index size with index compression is larger than when the index is uncompressed.


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.


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.


Stored procedures using "execute as caller" with queries that create and query #temporary tables fail with error 208, "Server ' < servername > ', Line 26: < #temporary_table > not found after LOAD DATABASE".


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.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module sendtext() may be reported in the error log when a MERGE JOIN is being used and if the inner table has in-row LOB columns with NULL values.


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.


In rare cases, when a transaction rolls back, it may hit error 623 when starting the backward scan on a page. The 623 error message will indicate that the Rid pageid = 0; row num = 0.


In very rare situations, SAP ASE may panic and shutdown if sp_sysmon is being run and a connection disconnects at the same time.


On Windows platform, SAP ASE may open an arbitrary listener port during MS DTC service initialization for distributed transaction management.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module LeScanOp::_LeOpNext() may be reported in the error log when an online utility (e.g. REORG REBUILD) is in progress on a table that contains forwarded rows.


Arithmetic overflow may occur when executing procedure sp_sysmon_locks.


CREATE TABLE commands may not perform well in situations where a lot of CREATE TABLE commands are run in parallel and the SAP ASE configuration has 'enable inline default sharing' set.


DBCC CHECKTABLE may encounter a 2511 error, "Keys of index ID < id > for table < tablename > in leaf page are not in the correct order. Drop and re-create the index (index page < pageno > , partition ID < partition_id > )", if 'enable functionality group' is enabled and the base table lockscheme is DOL and changing the table's lockscheme from DOL to APL as part of AMC.


The 6918 error, "The SYSDAMS page that stores the state of page # in database ' < dbname > ' could not be found. The option 'allow incremental dumps' will be disabled because SAP ASE cannot continue recording page modifications", can be raised if the table SYSDAMS gets the very first extent of an allocation unit allocated.


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".


The error message, "Length of plain text is less than one cipher block", may be reported in the error log during encryption of a database.


Under some circumstances, a worker thread may hang due to incorrect error handling during parallel CREATE INDEX with "utility statistics hashing" turned on.


In rare circumstances, a time slice error followed by a stack trace that includes the modules ups_end_statglobalnosort() and close_table() may be reported in the error log when running UPDATE INDEX STATISTICS.


Resource limit violation message 11001 (severity level 17:EX_RESOURCE) is reported when action 5(record action) is configured.


A DUMP WITH COMPRESSION could fail with the message "SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=0, system message=Pipe I/O returned 0 bytes". If a core file is produced the stack will show the module sm__do_allocations().


Under certain circumstances, the preupgrade utility from SAP ASE 16.0 can encounter data conversion errors and overflow errors when checking for free space in a database's system segment.


Wrong result could happen when an EQUIJOIN on a single INT4 column is placing a bloom filter probe into the scan and the scan is at the inner side of another NESTED LOOP JOIN with a pushdown EQUIJOIN sarg on the same column.


SAP ASE fails to boot on Windows with the message "FATAL: shared memory region is being held at xxx bytes but yyy bytes are required" being reported in the SAP ASE errorlog.


On a server that has a large number of objects, the sp_sysmon report may take a long time to complete and error message 1508, "Create index aborted on duplicate rows. Primary key is < keyname > ", may be reported in the error log.


DBISQL 16 stopped reading interfaces entries when the file contains a large number of entries.


The procedure cache allocation is optimised. This vastly speeds up the start-up of SAP ASE configured with a very large procedure cache.


A 3478 error, "During undo the page timestamp value is less than new timestamp from log." or other fatal errors may be reported in the error log when SAP ASE is rolling back a transaction following an 863 error, "Buffer resources in cache < cache_name > are unavailable. Please re-run this query or ask the system administrator to re-configure buffer cache memory." that is accompanied with messages "Named cache < cache_name, cache_id > is configured too small for current demands".


If the data cache is configured small, SAP ASE may report a 'cache too small' error when the new sort buffer algorithm is used.


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.


A parallel query may be rejected during execution because the worker thread pool has fewer threads available than the minimum number of threads required to execute the plan. In this case, the query should be sent back to be recompiled in serial mode. However, the query will be recompiled in parallel mode and then fails during execution again if it contains a plan-clause with the following directive "(use optgoal allrows_dss)". At this point a 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization", is raised because the procedure buffer object is missing.


When there is no active transaction in a database, running select loginfo('dbname','stp_pages') will give the result of 0 even if the secondary truncation page is not the same as the last log page.


In some rare cases, some of the pdes spinlocks show contention with objects that have a large number of partitions.


A 6908 error, "During redo the page timestamp value is less than old timestamp from log. etc." followed by a stack trace that includes the module 'recovery' could be raised when loading a database dump if the configuration parameter 'optimize dump for faster load' is enabled and there is very high update activity in SAP ASE while the dump database command is running. To workaround the problem the end-user can set the trace flag 3022 (either via the command line or by using dbcc traceon or by using SET SWITCH ON ignore_trailer_ckpt) before loading the database.


Upgrade to SAP ASE 16.0 may fail with the error message "Kernel resource memory pool has been exhausted. Try increasing the value of 'kernel resource memory'".


Under rare conditions, a 12301 error, "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 during an isolation level 0 scan.


When there are several scans on the same index and some of the scans hit the same index page needed to be shrunk concurrently, the index page may be shrunk twice. The second attempt will fail and a 2630 error, "In database < db > , page < page#2 > is linked backward to page < page#1 > , but that page is linked forward to page < page#3 > . Please report this internal error to SAP Technical Support". Although a 2630 error is raised, the index is not corrupted.


The message, "Current process infected with signal 10 (SIGBUS)", followed by a stack trace that includes the modules 'loginfo_builtin' and 'exec_lava' may be reported in the error log when the builtin loginfo(' < dbname > ','oldest_active_transaction_date') is executed.


sybatch.exe failed to set the XP Server in upgrading server if Replication Server is configured.


A 7786 error, "Unable to turn role off since user is not a valid user in the current database", may be reported incorrectly when executing the SET ROLE OFF command.


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.


A 614 error may be reported when executing DBCC CHECKSTORAGE on an encrypted database.


SAP ASE server may hang during the rs_init() command on encrypted databases.


The optcriteria EQUALS_SCAN_SUPERSET and EQUALS_NLJOIN_SCAN_SUPERSET have had the comments changed so that the respective optcriteria names shows up in the sysoptions output.


Executing DBCC CHECKSTORAGE on an encrypted database gets aborted at the 'index chain' check.


The time range restriction in Resource Governor does not allow users to add time range overlap limits even with different limit types.


A 18207 error, "Illegal action 5", may be reported when executing stored procedure sp_modify_resource_limit.


DBCC CHECKTABLE may report a 605 error, "An attempt was made to fetch logical page < pageno > from cache < name > . Page belongs to < info1 > and not to < info2 > " may be reported after creating an index with online option.


syconfig/sybatch try to recreate XP Server during upgrade even it doesn't exist.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module SearchEngine::_SeFindOptimal may be reported in the error log after a lengthy optimization, most likely after an aggregate with a GROUP BY in which the GROUP BY columns originate from multiple tables.


The version of OpenSSL used has been upgraded to OpenSSL 1.0.1g


On HP-UX platform, sqlupgrade[res] cannot boot the old SAP ASE if LD_LIBRARY_PATH environment variable is set.


sp_showoptstats will have poor performance if a large number of partitions are defined and/or a large number of columns have histograms defined.


When permission on built-in function is granted to a role which is granted to a user, then executing the built-in function may result in permission error.


DBISQL16/ASE in scrollable table mode, trimmed leading/trailing white spaces from error/warning/info messages, affecting the stored procedure output formatting such as "sp_showtext", where the output consists only info messages. This behavior is removed. Also, in scrollable table mode, previously Messages panel limited the number of messages to 1000 items. This limit has been removed.


sp_monitor inherits permission of exec to public from lower version server (i.e. 15.5) after upgrade to 16.0.


The "Command" column in the query of monThresholdEvent is displayed as "AWAITING COMMAND" when using dynamic SQL.


The message, "The log for database < dbname > includes a CREATE INDEX (with deferred roll-forward) operation that is incompatible with this server version and operating environment", is not reported as expected, if a transaction log dump from an earlier 15.7 release is loaded and the dump contains a CREATE INDEX transaction that was originally done WITH DEFERRED_RECOVERY=MANUAL or DEFERRED_RECOVERY=NONE.


If an upgrade from a SAP ASE server with a version lower than 15.7 SP100 fails to create the table SYSDAMS because it ran out of space, executing ALTER DATABASE to extend the space will fail with the 12324 error, "In database < dbname > , the server failed to open required table 'SYSDAMS'".


A 9502 error, "Data exception - string data right truncated", may be reported during ALTER TABLE MODIFY column to NULL with multi-bytes charset and the session property string_rtruncation is set.


A 2956 error, "Unable to grab a buffer to encrypt logical page < page_num > in database < db_id > . Increase the size of the buffer pool in the buffer cache < cache_name > ", may be raised to report buffer shortage when large transactions are executed on an encrypted database.



  • AIX 64bit
  • HP-UX on IA64 64bit
  • Linux on Power 64bit
  • Linux on x86 64 64bit
  • Solaris on Sparc 64bit
  • Solaris on x86 64 64bit
  • Windows on x64 64bit


SAP Adaptive Server Enterprise 16.0


CR, CR List, ASE 16.0 PL02, ASE PL02, PL02, PL 02, Adaptive Server Enterprise, Fix, Patch, Error, Bug, GA PL02 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.