SAP Knowledge Base Article - Preview

2694360 - Targeted CR List for ASE 16.0 SP03 PL07


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

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 NumberDescription
635018 A new function, show_prepared_statements(), is provided to display the SQL text for the prepared statements.
781928 In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc__findcachedSQLplan' together with a stack trace which includes the modules 'mem_getpages' and 'freeprocs', may be reported in the SAP ASE error log when LOAD DATABASE is run, while another session is reusing the same object descriptor, whose procedure buffer is in the process of being freed by the session running the LOAD command. See KBA 2162502 & 2270963.
802812 Streaming replication using the Component Interface now also supports object level replication.
806370 When auditing of sso_role is enabled, unexpected audit records may be generated against users without sso_role. See KBA 2441754
808387 New options, "disable_dc" and "enable_dc" has been added to the sp_procxmode system stored procedure, to disable and enable deferred compilation for a particular user stored procedure respectively.
810432 Allow IMRSLOGS threshold actions to restart when SAP ASE is rebooted and the free pages count is still below the defined threshold level for both single and multiple thresholds modes used for IMRSLOGS. The later mode is enabled with the SAP ASE trace flag 7439.
811700 Upgrade of Xerces from 2.1 to 3.2
813326 A 249 error, "Syntax error during explicit conversion of VARCHAR value '# < value > ' to a INT field", will be reported when executing sp_shmdumpconfig. See KBA 2623861.
813547 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322.
813847 Multiple threshold actions may be executed unwantedly to extend a database through a threshold action if the database is blocked due to long duration of a concurrent DUMP DATABASE execution. See KBA 2614731.
814051 An UPDATE query which involves tables not consistently qualified with the 'dbo' qualifier, may give wrong results when executed by a user who is not the database owner. See KBA 2619053.
814248 A new SAP ASE configuration option, "stream rep msg channel timeout", is introduced through sp_configure for an HADR setup using synchronous replication. During a failover, this option defines the minimum time in seconds before a mode switch can take place. The default value is 60 seconds.
814590 ddlgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. KBA - 2632662
814596 A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name1 > , object < obj_name1 > , index < idx_name1 > , partition < ptn_name1 > and not to database < db_name2 > , object < obj_name2 > , index < idx_name2 > , partition < ptn_name2 > ", may be reported in the SAP ASE error log after executing a CREATE CLUSTERED INDEX on a round-robin partitioned table with the dboption 'enforce dump tran sequence' enabled.
814651 The text of the 4305 error, "Specified file 'dump device' is out of sequence. Current time stamp is < datetime1 > while dump was from < datetime2 > .", has been improved to provide the dump file name in the message text. See KBA 2634147.
814754 A batched language command executed with DYNAMIC_PREPARE set to FALSE can result in an open object and cached statement to be consumed and unable to be reused or freed for each batch. See KBA 2613604.
815210 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ResRelOp' followed by a stack trace that includes the modules 'ResRelOpProcess' and 'CgpPop::_CgpPePredBmToScalar', may be reported in the SAP ASE error log when a query is executed that involves an OUTER JOIN on a materialized view and a non-materialized view that return a constant column and there is a predicate on this constant column.
815581 A 11060 message, "This statement has exceeded the maximum number of recompilations (20). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support", may be reported during workload replay with the "Reset server time to source workload capture time" option selected and a VIEW, that is created after the workload captured time, is accessed. See KBA 2661224.
815594 Under some circumstances, the output from executing the sp_opt_querystats procedure with the 'option_show_long' option may have malformed text with random newline breaks over some words.
815740 The message "current process infected with 11 (SIGSEGV)" in the module 'site_login_cancel' with a stack trace followed by the message "Scheduler infected: exiting" may be reported in the SAP ASE error log. See KBA 2682423.
815803 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubffreef' followed by a stack trace that includes the modules 'ufclose', 'dir_sendtext' and 'DIRRemoteAccess::sendText', may be reported in the SAP ASE errorlog during concurrent access of big files via a proxy table. See KBA 2672421.
815827 sp_help ' < proc_name > ' may report an incorrect fully qualified parameter list when the procedure < proc_name > is created with TABLE type or TABLE variable parameters.
815832 A 11021 error, "Function < function_name > invoked with wrong number or type of argument(s).", may be reported in the SAP ASE error log when upgrading a SAP ASE 16.0 SP03 PL03 or later version and an in-lined table-valued UDF is accessed.
815833 A query, which is selecting from a view with a left outer join and a predicate in where clause, and the view definition contains a subquery in 'When exists' which is wrapped in 'case' clause and a left outer join is used, may return wrong results which don't take the predicate into account. See KBA 2690931.
816000 A 15101 message, "There is insufficient memory to allocate < n > bytes. Please increase configuration parameter 'messaging memory', or try again when there is less activity on the server." may be reported when a large value has been set for the configuration parameter 'messaging memory' and real time messaging queries are executed in multiple concurrent sessions. See KBA 2674952.
816025 The message, "A fatal error has been detected by the SAP Java Virtual Machine: EXCEPTION_ACCESS_VIOLATION (0xc0000005)", together with the error message, "NTPCI__exit(1); Native Thread failed to unwind while attempting to shutdown the PCI", may be reported in the SAP ASE error log when loading sunec.dll on Windows platforms. See KBA 2687973.
816034 In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE and also behind the last hole fixed by the Fix-Phase of imrslog boot-time recovery.
816073 The message "enp_aesEncrypt: CCLCipherCtx_all failed with error: 0xa0100014." may be found in the SAP ASE errorlog when the length of the user password which is used for the Job Scheduler is either 7 or 23. See KBA 2677850.
816078 In rare circumstances under an HADR setup, the coordinator process of SAP ASE RepAgent may hang in the module 'ra__ci_coordinator_waits_for_switch_ack' preventing the replication flow to continue.
816107 The active Rep Agent trace flags will now be reported in the SAP ASE error log when a Rep Agent is started. When no Rep Agent trace flag is active the message, "RepAgent( < dbid > ) no active traceflags.", will be reported. Otherwise the message, "RepAgent( < dbid > ) active traceflags: < TF1 > , < TF2 > , ..." will be reported.
816203 Updatease fails to start the SAP ASE server if the master device file size is larger than 4GB.
816290 The number of free log pages in a database could be incorrectly reported by the sp_helpdb command, if the command ALTER DATABASE [LOG] OFF is used to remove pieces from the last database fragments and the command DUMP DATABASE WITH SHRINK_LOG is executed to remove the resulting fragment holes.
816352 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'yylex' together with a stack trace which includes the modules 'sqlpars' and 'internal_sql' may be reported in the SAP ASE error log when many whitespace characters appear in the query text following a SQL keyword, resulting in a zombie task or the ASE unexpectedly shuts down. See KBA 2686240.
816391 The dump history file contains unexpected 'dump.error' messages at a time when SAP ASE reports a 1204 error, " ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS." and the log truncation is not successful. See KBA 2686302.
816409 A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after having dropped a user database which is marked suspect and is On-Disk MVCC enabled.
816520 When no size is specified in the ALTER DATABASE command, the default size is incorrectly set to 512KB instead of 1MB for an Adaptive Server installation that is using a page size of 2KB.
816557 The message, "Assertion (pss- > pdbtkept = NULL)", together with a stack trace that includes the modules 'mda_populate_monRepLogActivity' and 'mda_exec', may be reported in SAP ASE error log when querying the MDA table monRepLogActivity while the diagserver binary is in use.
816643 The message, "Invalid data found and rebuilt in segment accounting array for segment < segment_id > in database ID < database_id > .", may be reported in the SAP ASE error log following the recovery of a database. See KBA 2672135.



  • 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 SP03 PL07, ASE SP03 PL07, SP03 PL07, 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 , 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.