2077421 - Targeted CR List for ASE 16.0 GA PL01 - SAP ASE | SAP Knowledge Base Article

SAP Knowledge Base Articles - preview

2077421 - Targeted CR List for ASE 16.0 GA PL01 - 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 a jConnect application with DYNAMIC_PREPARE set to true, auditing of DML statements doesn't print the correct parameter values when the same cursor is closed and opened again.


A 702 error, "Memory request for NN bytes exceeds the size of single page of 16384 bytes. ASE is terminating this process", may be reported when using queries with tables that have more than 4192 partitions.


Sometimes a long running transaction can be seen in tempdb for $sort_local which results in tempdb filling up if a large data set needs to be sorted.


A 331 error, "Query is too complex and has exhausted the name space for Ordering IDs, please breakup query into simpler components.", may be reported during a complex query with multi-tables especially using aggregates and allrows_dss optgoal.


If the DML contains a builtin function with two or more parameters, the audit trail may print the parameters in reverse order.


A 213 error, "Insert error: column name or number of supplied values does not match table definition." may be reported in a stored procedure, when deferred compilation is active, if a column is added to a table and there is a dependency on "select * " behavior to ignore the extra column. Trace flag 7798 will ignore this error if deferred compilation is turned on and allow normal compilation to process the statement. If normal compilation still sees an inconsistency, or some other activity causes re-resolution of the stored procedure, then errors may be still be reported.


When procedure deferred compilation is turned off, DML auditing of stored procedures may not print variables in audit trail.


Sometimes, error 7705 could be raised unexpectedly for LIKE predicate with ESCAPE clause if there is a same letter in LIKE and ESCAPE clause, but one is an upper case letter and the other is a lower case letter.


When shared memory size exceeds 1TB, sp_shmdumpconfig might report error 265, "Insufficient result space for explicit conversion of INT value '1382954' to a CHAR field.".


A timeslice error followed by a stacktrace that includes the modules stphd_release_last_mvcc_histogram(), stphd_release_unreferenced_mvcc_histograms() and stu_nosort_range() may be reported in the error log in a heavily loaded system during the CREATE INDEX operation when using hashing.


LIKE optimization does not happen for a ? + ? pattern that is used in a prepared statement.


In rare circumstances, a 1105 message "Can't allocate space for object 'syslogs' in database 'tempdb' because 'logsegment' segment is full" may incorrectly be printed for tempdb when the first pages of tempdb are not mapped in sysusages.


A timeslice error, followed by a stacktrace that includes the module memshrink(), may be reported in the SAP ASE errorlog during a sort operation on a very large data set.


Under certain circumstances, a 2956 error, "Unable to grab a buffer to encrypt logical page < pagenum > in database < dbid > . Increase the size of the 16K buffer pool in the buffer cache 'default data cache'", may be reported when using an encrypted database.


A 4720 error, "Cannot truncate table < tablename > because there are one or more isolation level 0 scans, or REORG command, active on the table", may be reported during a TRUNCATE TABLE command while level 0 scans are active. This new feature is enabled when the new configuration option 'enable utility lvl 0 scan wait' is set.


When running on a table with thousands of partitions, create local nonclustered index or placement index command may fail due to stack overflow with no error message printed.


In rare circumstances, checkstorage or sp_dbcc_alterws might not expand the scan/text workspace to the size suggested by sp_plan_dbccdb or specified value.


When a user invokes DDLGen from a script and wishes to hide the password by supplying the pseudo password (-Pext) and including the actual password in a file or setting in an environment variable, the error "DG16: Could not get Console instance" is reported.


Under rare circumstances, some qualified data rows may not be returned for a query which uses RID list scan on a partitioned DOL table.


The error message, "SSL or Crypto Error Message: 'csi_cipher_crypto'" may be reported when encrypting an existing database.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module LeExecuteWorkUnits(), may be reported in the error log during execution of query plans that use both the 'dynamic thread assignment' and 'parallel index update'.


1) If SAP ASE is installed as an overlay, sybatch will reset the XP Server port to default during upgrade. 2) sybatch requires user to specify sqlsrv.master_device_physical_name, sqlsrv.master_device_size, sqlsrv.master_db_size and sqlsrv.application_type which are not really needed in upgrade. 3) sybatch recreates the XP Server Windows service even if it doesn't exist for the old server.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module s_recompile() may be reported in the error log when a table schema change happens after processing the first row, and before finishing the second row of an dynamic batch INSERT.


When upgrading to SAP ASE 16.0, the upgrade utility will report error 4243, "DUMP TRANSACTION WITH NO_LOG or DUMP TRANSACTION WITH TRUNCATE_ONLY is not allowed in database ' < dbname > ' while the 'enforce dump tran sequence' database option is enabled." if a database has option "enforce dump tran sequence" set.


Creation of temporary tables in a large number of concurrent user sessions leads to a high number of accesses to syslogins.


DDL commands within prepared statements can now be replicated.


When using data encryption functionality on Windows platforms, encryption operations can make an engine stall for short periods of time.


Database encryption fails with error 16839, "Database < dbname > cannot be encrypted when encryption is in progress.", after an abnormal shutdown.


Executing DBCC CHECKSTORAGE on an encrypted archive database may raise suspect conditions.


The Job Scheduler may fail to start after setting the minimum password length using sp_passwordpolicy to a value greater than the value of the minimum password length set by sp_configure.


Under a heavily used replication environment and in rare circumstances the Rep Agent schema cache and the Rep Agent memory pool can run out of memory because of a memory leak issue.


When a process that is executing a DUMP DATABASE command is killed either using the KILL command or using CTRL-C or the SQL session goes away, the Backup Server will not release its associated resources until it finishes copying the whole database. One of the consequences is that the archive devices can remain locked for a long time because the sybmultbuf processes stay alive.


A 614 error - "Adaptive Server accessed a row that has an illegal length of < n > while in data base ' < dbname > '. < page info > . The minimum row length is < n > . The page size is < n > ." may be reported when executing DBCC CHECKDB on an unencrypted database that is encrypted first and then decrypted.


A poor query plan might be selected when parallel UPDATE STATISTICS (for instance using the consumers phrase) is used to gather statistics. After installing SAP ASE with the fix for this issue, update statistics will need to be run on affected tables.


If replication is currently disabled and a table having non-materialized columns is dropped or one of its non-materialized defaults changes, then when replication is enabled again, it can encounter errors when trying to replicate that table's rows.


REORG command has been changed such that it cannot be executed while encryption or decryption of database is in progress.


When SAP ASE is upgraded to 16.0 from 15.7 or later and the 16.0 server writes a new configuration file before being shut down after upgrade is complete, then that configuration file may contain entries that were unexpectedly changed from what the older version server originally configured.


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.


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



  • 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 PL01, ASE PL01, PL01, PL 01, Adaptive Server Enterprise, Fix, Patch, Error, Bug, GA PL01 , 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.