2079889 - Targeted CR List for ASE 15.7 SP101 - SAP ASE | SAP Knowledge Base Article

SAP Knowledge Base Articles - preview

2079889 - Targeted CR List for ASE 15.7 SP101 - SAP ASE


The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in future Adaptive Server Enterprise (ASE) EBF/SP or PL releases. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the service.sap.com.

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



In circumstances whereby the select list of an INSERT SELECT with ORDER BY does not include the 'order by' columns, it is possible that the optimizer will favour a non-matching index scan using an index with the order by column(s) as opposed to a more efficient plan using a matching index scan for one or more of the filter predicates. A new optcriteria cr702725 has been introduced for this change. Use "set cr702725 1" to turn on the change and "set cr702725 0" to turn it off.


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.


In rare occasions, Adaptive Server's internal timer becomes non-operational. Such occurrence is reported to the errorlog with messages like Warning: Alarm Service for Timer non-operational. If this message generated multiple times, report to support and restart the server (alarminterval=-7001)


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.


In certain circumstances, databases, including system databases, can incorrectly get into LOG SUSPEND mode, issuing message: "Space available in the log segment has fallen critically low in database ' < dbname > '. All future modifications to this database will be suspended until the log is successfully dumped and space becomes available." This may happen even though there is much unreserved space in the database. The problem may also manifest in 3475 errors: "There is no space available in SYSLOGS to log a record for which space has been reserved in database < dbname > ."


Shrinkpage() will raise a 631 error if the parent nonleaf page has only one nonleaf row that points to the shrinking page.


A 1209 error, "Internal Error in lock manager routine: Attempted lock upgrade from shared intent to shared table in parallel query thread is illegal", may be reported in the error log during a SELECT or SELECT-INTO query on a table with parallel plan if there are concurrent DMLs or utilities operating on the table.


In rare circumstances, the task will hang when LIKE clause or patindex(builtin) operator on the columns which contain the LOB data defined as compressed.


After multiple HADR failovers, new client connections to a server in the HADR group may fail with error message "Read from the server has timed out" or "There is a tds login error".


"shutdown with nowait" may fail to shutdown the server followed by SIGSEGV stacktrace with modules ktMuxThreadGetSchedQ(), ktMuxThreadTick(), utpApplyAll(), utpmApplyAll(), kaclkintr_thread() on the stack.


If a table has small compressible off-row LOB columns that are not compressed due to size or other factors, ASE RepAgent may send an incorrect text length to Replication Server causing the Replication Server to stop replicating.


RepAgent may run out of memory and shutdown if started and stopped a large number of times.


Database device remapping is disabled when a database is loaded with VERIFY.


A Fault Type Error 100008, "Fixed format error", may be reported by DBCC CHECKSTORAGE if DBCC CHECKDB or DBCC CHECKTABLE is run on a database/table which contains variable length columns previously.


The message, "Error: sdt_getpage: Attempt to read page '0' but device < device_name > is not open. Exiting", is reported when a cumulative dump is used as a metadata file for sybdumptran.


If an ODBC or JDBC client enables one or both of HADR_MAP and HADR_NOKILL capabilities, different message text for same error codes is seen in case of HADR errors.


If any of the system databases is > 2GB, the Update Adaptive Server in the installer or $SYBASE/ASE-15_0/bin/updatease (%SYBASE%\ASE-15_0\bin\updatease.exe on Windows) utility will fail with "Arithmetic overflow occurred." error.


The show_condensed_text built-in function returns a NULL value for queries in the statement cache when the 'enable literal autoparam' configuration parameter is enabled.


ASE may report a 12062 error that the operation stack has overflowed when "execution time monitoring" is on.


The message, "Current process infected with signal 11" followed by a stack trace that includes the module ktMuxThreadGetSchedQ() may reported during shutdown and may not lead to a complete ASE shutdown.


On Windows 2008 R2 platform, ASE HA may fail to create Sybase Companion Server. "sp_companion configure" fails with message "HA Config Error: Unable to write cluster resource properties for ASE server ' < name > ' (operating system error 183)."


Queries with OUTER JOIN and a reference to syscomments.text can get wrong results when "select on syscomments.text" is set to 0.


A 12319 error, "Fatal internal error encountered during deferred dml on table < tabname > in database < dbname > . All rows that qualified during the first phase were not visited during second phase of dml" may be reported followed by a stack trace that includes the modules dol_def_update() and dodeferred() when running CREATE INDEX or REORG REBUILD with ONLINE option with concurrent DMLs on hot objects.


"sp_hadr_admin status, 'anyvalue'" fails when executed on standby HADR server when quoted_identifier is on.


In an HADR environment, the privileged connection (to the old primary) with info capabilities gets killed upon activation of the new primary server.


LOAD TRANSACTION of a transaction dump involving the log records of materialization of an indexed table with 'deferred allocation' property may fail with the 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #=x, object id = y, page timestamp=z. Log old timestamp=a. Log record marker =(p, q)."


A 9284 error, "RepAgent( < dbid > ). Cannot allocate 9024 bytes of memory. You may need to reconfigure the parameter 'replication agent memory size' with more memory." may be reported when LOB off-row data is replicated, resulting in the Rep Agent Thread for this database to be terminated abnormally.



  • 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 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition


CR, ASE 15.7 SP101, ASE 15.7, SP101, Adaptive, Server, Enterprise, Fix, Patch, Error, Bug, , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , Problem

About this page

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

Search for additional results

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