SAP Knowledge Base Article - Preview

3208547 - Targeted CR List for ASE 16.0 SP03 PL13

Symptom

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 SP03 PL13 . Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the support.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 NumberDescription
644353 A new option 'except_count' is added to SAP Adaptive Server built-in pssinfo() to print the number of frames in the exception stack of a session.
666702 A deadlock may be reported by SAP ASE on master..sysdevices system table when concurrent sessions execute UNMOUNT DATABASE on different user databases. See KBA 3127525.
771406 After a database reload or an ASE upgrade, when a query referencing a view that has the same name as a table referenced by this view is executed, SAP ASE may loop endlessly trying to resolve the object id of the table referenced by the view.
808018 A 2601 error, "Attempt to insert duplicate key row in object 'temp worktable' with unique index", may be reported by SAP ASE when updating a table variable.
820176 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'row_delete' followed by a stack trace that includes the modules 'LeCacheWkTblIO::deleteRow', 'LeScrollCache::_deleteRow' and 'LeScrollCache::LeCacheDelete', may be reported in the SAP ASE error log when deleting rows from a table variable. See KBA 2854066.
820494 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ups_main' together with a stack trace may be reported in the SAP ASE error log when UPDATE STATISTICS is executed against a materialized view.
822348 When TRUNCATE TABLE is executed in an encrypted database, SAP Adaptive Server may write some data in cleartext form on disk. See KBA 2952769.
824154 A new optimizer criteria ‘rowconst_opt' is introduced to SAP Adaptive Server which enable/disable the row constructor optimization for range predicate index scan selectivity. Default setting is 'enabled'.
825021 A 644 error, "Index row entry for data row id < page-number, row-number > is missing from index page < page-number > of index id < index-id > of table < object-id > in database < database-id > . Xactid is < page-number, row-number > . Drop and re-create the index.", may be frequently reported in the SAP ASE error log when a high number of DELETE and INSERT batches are concurrently executed. See KBA 3069024.
825395 In an HADR setup, the primary server fails to be activated when it is rebooted after having executed the RMA command sap_disable_replication.
825576 In rare circumstances, UNMOUNT DATABASE may hang with the message, "Database < database-name > with dbid < database-id > is already shut down.", reported in the SAP ASE error log. See KBA 3100804.
825856 In rare circumstances, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < database-name > ' because the target page is not a data page ...", in the module 'rec_undo_session' together with a stack trace which includes the modules 'le_runerr' and 'abortcmd' may be reported in the SAP ASE error log when concurrent DML commands are executed and a DML command needs to rollback which also happens to run out of syslogs space (1105 error). The session failing to rollback will leave phantom logical locks behind it that may require an ASE reboot.
826023 When a secondary signal occurs SAP Adaptive Server has been improved to prevent a signal during session cleanup. Additionally if ASE is started with trace flag 2917 and a secondary signal occurs, ASE won’t be killed but the process will be put in zombie state with its locks released to prevent blocking other sessions. See KBA 2682383
826036 The SAP ASE configuration option 'sqlfunc syntax valid' is renamed to 'extended syntax validation'. This option determines whether extended syntax validations will be enabled. The default value is true, which means that extended syntax validations will be performed for SQL functions.
826137 A 3914 error, "Illegal internal transaction status. This is an internal system error.", may be continuously reported in the SAP ASE error log when the Housekeeper garbage collection task has first hit a 940 error, "Dbtable in wrong state for operation: DBTABLE pointer = ...". See KBA 3144763.
826149 An undetected deadlock may occur when two connections execute ALTER TABLE ... ADD PARTITION simultaneously while the SAP ASE configuration options "functionality group" and "enable utility lvl 0 scan wait" are enabled. See KBA 3146433.
826153 In rare circumstances, a session that attempts to kill another session that is holding a buffer latch on sysattributes system table, may cause the killer task to block forever on the same buffer latch. See KBA 3163527.
826332 The message, "timeslice < negative-value > , current process infected", together with a stack trace which includes the modules 'dup_elem_memfree' and 'memfreeheap' may be reported in the SAP ASE error log when a SELECT query is using an IN clause with a nested subquery that itself is using an IN clause and the ASE trace flag 132 is enabled. See KBA 3167885.
826416 SQL Text in ASE error log drops 2 characters per chunk when a fatal error is received which comes from a specific place in terminate_process.
826427 The message, "Current process infected with 11 (SIGSEGV)", in the module 'lt_notify_flush' together with a stack trace which includes the modules 'xls_flush' and ‘xact_commit’ may be reported in the SAP ASE error log when a session commits a transaction in a database setup for replication while a concurrent session is executing 'DBCC SETTRUNC'. This will result into an implicit shutdown of Adaptive Server as the task holds the spinlock for ‘Dbt- > dbt_repl_context.repl_spinlock’ when the error is encountered. See KBA 3194320.
826428 A 701 error, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", may be unexpectedly reported during the execution of a query because some procedure cache memory leak occurred earlier while executing SELECT queries on partitioned tables with more than 4096 partitions. See KBA 2537375.
826429 The message, “Backup Server: 5.16.2.2: Client-Library error: Error number 44, Layer 4, Origin 1, Severity 188978561028: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.”, may be reported in the Backupserver error log when DUMP or LOAD is run for an in-memory database and the configuration parameter 'net password encryption reqd' is enabled. See KBA 3192435.
826467 The message "Adaptive Server message 4002, state 1, severity 14: Login failed." may be reported when preupgrade or upgrade utility is executed on sunx64 platform with SAP ASE 16.0 SP03 PL12 release.
826491 The message, "Resource- > rattrib_readers: < value > ", may be repeatedly reported in the SAP Adaptive Server error log when simultaneous scans of syssrvroles system table are being performed. See KBA 3195319.
826497 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeVtuple::LeVtGetColumn' together with a stack trace which includes the modules 'LeHashEntry::ReadRow' and 'LePlanNext', may be reported in the SAP ASE error log when a SELECT query which includes Unions in a derived-table expression and contains a group-by clause referencing one or more correlated columns that are literal values from the UNION block is executed. See KBA 3195220.
826499 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memchr' together with a stack trace which includes the modules 'query_text' and 'prSensitiveSQLTEXT' may be reported in the SAP ASE error log when 'sp_showplan < spid > ' is executed on Solaris Adaptive Server.
826509 When an insensitive cursor involving LOB columns is opened, SAP ASE may unexpectedly earlier release the shared table level lock held on the base table.
826550 SAP Adaptive Server has been improved to handle errors better during RPC execution.
826564 In an HADR setup an excessive growth of the Replication Server rs_schemas system table may be seen in Embedded RSSD, when frequent DROP TABLE commands are executed in the primary SAP Adaptive Server.
826593 A 17957 error, “You cannot set the 'enforce dump tran sequence' database option because the database < database-name > is either marked as needing a database dump, an unlogged operation was performed or the transaction log was truncated. Dump the database, then retry setting the option.”, may be unnecessarily raised when sp_dboption < database-name > , 'enforce dump tran sequence', 'false' is run while the option was already disabled.
826599 In rare circumstances, when the configuration option 'enable job scheduler' is in use, an infinitely growing call stack which includes the modules 'jsj_printServerMsg' and 'jso_WriteToBuffer' may be seen in the JSAGENT O/S process when a 1105 error, "Can't allocate space for object 'js_output' in database 'sybmgmtdb' because 'default' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.", is hit by SAP Adaptive Server while writing to database 'sybmgmtdb'.
826600 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'update' together with a stacktrace which includes the modules 'LeWkTbl::updateWkTbl' and 'LeScrollCache::LeCacheUpdate' may be reported in the SAP ASE error log when executing UPDATE on table variable.
826629 This is complementary change to CR 826497 providing further improvement for execution of queries using group hashing strategy.
826642 The message text for error 9979 has been enhanced to report the cache name involved with "Too many worker processes ( < work-processes-number > ) are configured for the available < pool-size > K buffer pool in cache ' < named-cache > '.".
826668 Query using ROWS LIMIT when executed in the compatibility mode results in "tds protocol error" erroro message. See KBA 3210688.
826678 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'row_delete' followed by a stack trace that includes the modules 'LeCacheWkTblIO::deleteRow', 'LeScrollCache::_deleteRow' and 'LeScrollCache::LeCacheDelete', may be reported in the SAP ASE error log when deleting row from table variable.
826714 A 4846 error, "Bulk copy failed. Error occurred while updating the last page of the table.", may be unnecessarily reported in the SAP ASE error log when BULK INSERT is executed and the session was chosen as the deadlock victim by Adaptive Server. See KBA 3213515.


Read more...

Environment

  • 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

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR, CR List, ASE 16.0 SP03 PL13, ASE SP03, SP03, PL13, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.