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 Number | Description |
---|---|
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. |
702240 | A housekeeper check for database timestamp values increasing at an abnormally rapid rate has been added in the housekeeper task of Adaptive Server. In case the condition triggers the message, "WARNING - The timestamp of database ' < database-name > ' had an unexpected jump from ( < hexadecimal-value > , < hexadecimal-value > ) to ( < hexadecimal-value > , < hexadecimal-value > ). Please contact SAP Technical Support.", will be reported in the SAP ASE error log. See KBA 3230458. |
768285 | A 834 error, "Illegal attempt to clean buffer: BUF= < buffer-address > ...", may be reported in the SAP ASE error log during boot recovery of an encrypted database after DISK REFIT was executed. See KBA 3256646. |
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. |
774799 | A 290024 error, "Invalid column length: < column-length > . Value must be between 0 and < maximum-column-length > at offset < column-offset > for ' < row-format > ' row with minimum row length of < minimum-column-length > .", may be reported by SAP Adaptive Server when a SELECT query is executed and an invalid column length is encountered. |
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. See KBA 3216180. |
819608 | In rare circumstances, the message, "timeslice < negative-value > , current process infected", in the module 'sysxacts_materialize' together with a stack trace which includes the modules 'make_fake' and 's_setuptables', may be reported in the SAP ASE error log during the execution of a query involving systransactions. See KBA 2894955. |
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. See KBA 3228631. |
820599 | The message, "Adaptive Server Enterprise system exception generated by a storage access violation.", in the module 'xls_pre_alloc_numclrs' together with a stack trace which includes the modules 'grantrev' and 'logcommand' may be reported in the standby SAP ASE error log in an HADR setup. See KBA 3215756. |
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. |
823436 | A 804 error, "Unable to find buffer < address > from cache < cache-name > holding logical page < page# > in sdes < address > kept buffer pool for object < table-name > .", or a 814 error, "Keep count of buffer < address > in cache < cache-name > holding logical page < page# > in database ' < database-name > ' has become negative.", together with a stack trace which includes the modules 'dol_update', 'dol_update', and 'bufunkeep_do_decrement' may be reported in the SAP ASE error log when a DML is executed and the database transaction log is full. Bootstrap Adaptive Server with trace flag 1102 in order to gather more information in the error log when the transaction log gets full. See KBA 2994461. |
824144 | DBCC RESOURCE is enhanced to report the value for ‘raudflags’ which indicates the status of the audit process. Also the new built-in ‘is_audit_suspended()’ is added which indicates whether the audit process is suspended or not. Additionally the message, "Attention: Audit process is suspended", will be printed in the SAP ASE error log every 30 minutes if the audit process is suspended. See KBA 3256664. |
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'. |
824691 | In a very busy SAP Adaptive Server system, some procedure cache memory corruption may happen when concurrently one task is recompiling a cached statement and other tasks are competing for procedure cache memory while ASE is running short of procedure cache memory. A possible side effect is described in KBA 3051772 whereby ASE will shut down implicitly after a signal 11 (SIGSEGV) error is hit in the module 'senderror'. |
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. |
825087 | Query performance degradation may be observed along with network tasks running at 100% cpu when sessions execute SELECT queries using a large IN list and are connected to the SSL port. A new static Adaptive Server configuration option "max network events" is added to configure the maximum number of events the SAP ASE network controller can read from the O/S. The default value is 50 and the maximum is 500. See KBA 3083028. |
825338 | In rare circumstances, a 6913 error, "DUMP DATABASE < database-name > FULL is unable to clear the list of changed database pages. Future incremental dumps will be unnecessarily large until the next successful full DUMP DATABASE.", may be reported by SAP ASE when DUMP DATABASE is executed while the database option 'allow incremental dumps' is enabled. A diagnostics message will be printed in the Adaptive Server error log to help diagnose error 6913. See KBA 3238636. |
825383 | The 'Housekeeper Section' of sp_sysmon may recommend to increase "housekeeper free write percent" even though there is a low ratio of 'Dirty Buffer Cache Washes'. See KBA 3087788. |
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. When ASE is started with trace flag 6916, Adaptive Server will check and fix incorrect database usages at an interval of five minutes and may report the message, “Found incorrect database usage count in database ‘ < database-name > ’ with ID < database-id > : dbt = < hexadecimal-address > , dbt_keep = < count-value > , dbt_systask_keep = < count-value > . Resetting database usage count to 1”, in its error log. See KBA 3100804. |
825614 | In rare circumstances, a timeslice error together with a stack trace in the module 'oj_merge_ojblock' may be reported in the SAP Adaptive Server error log when a complex query that includes multiple views is executed. See KBA 3033730. |
825684 | In rare circumstances, SAP Adaptive Server Rep Agent may not be stopped due to a stream replication native thread sleeping on exit on which the Rep Agent is dependent while the configuration option 'enable pci' is on. See KBA 3150546. |
825780 | The message, "timeslice < negative-value > , current process infected", together with a stack trace which includes the modules 'GenCondensedText::isInTree' and 'show_condensed_text' may be reported in the SAP ASE error log when a SELECT query is using SHOW_CONDENSED_TEXT() built-in function. See KBA 3255032. |
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. See KBA 3230055. |
825986 | The error message, "ANS0344E (RC2107) Cannot Send data with a zero byte sizeEstimate", may be reported in the SAP Backupserver error log when DUMP command with database size greater than 4TB is executed using TSM. See KBA 3135839 |
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. See KBA 3218777. |
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. |
826147 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'ssl_cipherbypss' together with a stack trace may be reported in the SAP ASE error log when a remote procedure call executes SELECT @@ssl_ciphersuite and the connection uses a site handler. The local client making the call will hang and the stacktrace will be reported in the remote SAP ASE error log. See KBA 3145809. |
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. |
826197 | SAP ASE may report CacheSize, Overhead and CAS counters for a single cache partition instead all cache paritions in MDA table monDataCache when there are more than one partition configured for a cache. See KBA 3151578. |
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. |
826383 | In rare circumstances, SAP ASE may shut down implicitly after multiple 1204 errors, "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.", or 1105 errors, "Can't allocate space for object 'syslogs' in database 'sybsecurity' because 'logsegment' 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.", have been reported causing the termination of the audit process. See KBA 3229085. |
826409 | A 247 error message,"Arithmetic overflow during implicit conversion of UNSIGNED INT value ' < integer value > ' to a INT field" may be reported by stored procedure sp_ddlgen when the database is large enough to use pages in unsigned int page range. See KBA 3191721. |
826412 | New dbcc command, 'dbcc alarms' is added in SAP Adaptive Server Enterprise server to print alarms and their status. Additionally 'dbcc mempool("Alarms","show",1)' command is enhanced to print information about the alarm structures which are in use. See KBA 3189250. |
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. See KBA 3230067. |
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. |
826455 | The SAP ASE procedure cache memory management is improved to free already allocated memory after encountering 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.", when a dynamic prepared query execution attempts to insert a huge amount of LOB data in a table. See KBA 3193727. |
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. See KBA 3216088. |
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. See KBA 3274344. |
826558 | A 692 error, "Uninitialized logical page ' < page-number > ' was read while accessing database ' < database-name > ' ( < database-id > ), object '' (99), index ' < Unknown > ' (0), partition ' < Unknown > ' (99).", may be reported in the SAP ASE error log when executing CREATE DATABASE FOR LOAD using over 6.25 terabytes of space. See KBA 3204034. |
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. See KBA 3229049 |
826565 | A SELECT query on system table master..syscurconfigs may display negative values indicating an overflow when a data cache is configured with a greater than 2TB size. See KBA 3274290. |
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. See KBA 3228593. |
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'. See KBA 3216227. |
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. See KBA 3228579. |
826623 | In rare circumstances, the ASE Rep Agent may hang when the error message, "(CI-Info) Message: 76066, Severity: 5 Failed to serialize a package for Stream 'ISP'(pbuf = < package-information > , cnt = < counter-information > , cmds = < number-of-commands > , xdr = < package-information > ).", is reported in the SAP ASE error log under an HADR setup. Subsequently any attempt to either stop the Rep Agent or kill the Rep Agent will fail. See KBA 3207018 |
826629 | This fix complements that of CR 826497 by providing further improvements in SAP Adaptive Server for the execution of queries that are using the group hashing strategy. See KBA 3195220. |
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 > '.". See KBA 3230016. |
826658 | The message, "ELC_VALIDATION_ERROR: Page not marked free.", may be reported in the SAP ASE error log when CREATE INDEX fails with a 1521 error, "Sort failed because a table in tempdb used for the processing of the query had a bad data page count. Tempdb should not have been damaged.". See KBA 3210652. |
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. See KBA 3213889. |
826708 | A 5123 error, "DISK INIT encountered an error while attempting to open/create the physical file for device ' < raw-device > '. Consult the Adaptive Server error log for more details. For the Cluster Edition, check the error log of each instance.", may be reported on AIX platform by SAP ASE when DISK INIT is run on a raw device and the sector size is of 4096 bytes. See KBA 3213002. |
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. |
826718 | DUMP DATABASE when used with compression levels 1 to 9 may expose a performance degradation on SunOS platform after having upgraded Adaptive Server to 16.0 SP03 PL06 release whereby the support for Zlib 1.2.12 version has been added. See KBA 3147657. |
826725 | In rare circumstances, the message, "BACKUPSERVER: bs_trap; process received signal 11", together with a stack trace which includes the modules 'as_report_progress' and 'srv_lockmutex' may be reported in the SAP Backup Server error log during LOAD DATABASE execution. See KBA 2896338. |
826736 | A 247 error, "Arithmetic overflow during explicit conversion of NUMERIC value ' < value > ' to a INT field.", may be reported by sp_sysmon_dcache_sum when running sp_sysmon for a large sample time on a very busy ASE. See KBA 2544721. |
826739 | A 4956 error, "Cannot alter table if REORG command or level 0 scans are active.", may be reported when simultaneous ALTER TABLE ... ADD PARTITION are run against a table while the configuration option 'enable utility lvl 0 scan wait' is enabled. See KBA 3216925. |
826780 | In rare circumstances, an undetected deadlock may occur between two tasks when SAP ASE is started with trace flag 859 which enables role lookup optimization and high access concurrency on sysattributes takes place. See KBA 3217673. |
826819 | The system stored procedure sp_altermessage is enhanced with the addition of new option ‘with_stack’. This new option allows to report in the SAP Adaptive Server error log the call stack from where in the code a given error is raised along with the error message itself. See KBA 3264966. |
826834 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'ra__ci_stpmgr_execute' may be reported in the SAP Adaptive Server error log when the Rep Agent is stopped in an HADR setup. See KBA 3238648. |
826899 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'subglobals' together with a stack trace may be reported in the SAP ASE error log during the execution of a query and a 261 error, "' < name > ' is not a recognized global variable.", was first reported. See KBA 3238692. |
826916 | A 15946 error, "Invalid column length < column-length > found for column, column ID < column-id > , row ID < row-id > , page number < page-number > , partition ID < partition-id > . The length is greater than the expected maximum column length < maximum-column-length > .", may be reported by SAP Adaptive Server when a SELECT query is executed and an invalid column length is encountered. See KBA 3238630. |
826969 | A new configuration option 'HADR primary strict bootstrap' is added to SAP Adaptive Server, which when enabled would disallow primary ASE to boot if the standby ASE is not reachable. See KBA 3271537. |
826995 | A 17471 error, "The device name supplied is not a normal database device.", is reported instead of a 17470 error, "No such device exists -- run sp_helpdevice to list the ASE devices.", when either executing sp_dropdevice, sp_logdevice, or sp_deviceattr using a device that does not exist. See KBA 3234009. |
827078 | A timeslice error in the module 'prepprev' together with a stack trace which includes the modules 'onl__test_upgraded_replicated_db' and 'apl__startscan' may be reported in the SAP ASE error log during database boot recovery. See KBA 3242248. |
827101 | A 1265 error, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr=0x(nil), lrmagic=", may be reported in the SAP ASE error log when ALTER TABLE ... DROP PARTITION ... WITH ONLINE is run while replication is enabled in the database. See KBA 3248910. |
827120 | In rare circumstances, the message "Stack overflow detected", together with a stacktrace which includes the modules 'ucstackcrash' and 'sy_kill_task' may be reported in the SAP Adaptive Server error log, although there is no actual stack overflow for HP platform. This will result in Adaptive Server shutting down implicitly. KBA 3287846 |
827237 | The current fix expands CR 826739 fix whereby a 4956 error was reported by SAP ASE when ALTER TABLE ... ADD PARTITION commands are executed simultaneously on a table while the configuration option 'enable utility lvl 0 scan wait' is on. See KBA 3216925. |
827325 | A new option to skip 'removehadr' is added in 'setuphadr' utility while configuring an HADR system. See KBA 3275824. |
827355 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", may be reported in SAP ASE error log together with a stack trace which includes either the module 'next_root', or 'IsExprNullable', or 'proc__setdb_tree' when a stored procedure is either executed or compiled. See KBA 3268829. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Solaris on x86 64 64bit
- Windows on x64 64bit
Product
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.