/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
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 SP04 PL03. 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 |
|---|---|
| 474850 | A new configuration option 'enable backupserver HA' is introduced and enabled by default whereby when a DUMP or LOAD command is executed if the Backup Server is not running, Adaptive Server will start the Backup Server automatically instead of failing the command. |
| 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. |
| 721549 | When sp_monitorconfig 'max online engines' is run, only one active engine will be reported even if multiple active engines exist, while SAP Adaptive Server is started with the configuration option 'kernel mode' set to 'threaded' mode. See KBA 3217250. |
| 767882 | If a global login trigger is created in a database other than the master database, the trigger will be disabled if any user logs in before the database containing the trigger is recovered during a reboot of SAP ASE. See KBA 2052531 |
| 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. |
| 778633 | The stored procedure sp_help for object type ‘table’ may incorrectly report ‘table is VOLATILE’, after SAP Adaptive Server is upgraded to 16.x version. See KBA 2125940. |
| 794585 | sp_helptext incorrectly raises error 567 when "select on syscomments.text" disabled and user is the database or procedure owner. See KBA 2266857. |
| 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. |
| 811837 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 's_clean_encrkeys' together with a stacktrace which includes the modules 's_execute' and 'execproc' may be reported in the SAP ASE error log during CREATE INDEX execution inside a stored procedure. See KBA 2575438. |
| 816757 | SAP ASE is improved to isolate problematic index pages while redoing index log records during bootstrap recovery. Adaptive Server will mark the problematic index pages suspect instead of marking the database suspect which prevented database accessibility. The suspect index pages can be listed by executing the existing system stored procedure sp_listsuspect_page. See KBA 3213496. |
| 819533 | When LOAD TRAN < database-name > is executed with the option UNTIL_TIME=' < datetime > ' a message will be reported in the SAP ASE error log indicating that the option was used to perform point-in-time recovery. See KBA 2904072. |
| 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. |
| 820566 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module '_IO_vfprintf' together with a stacktrace which includes the module 'vsnprintf' may be reported in the SAP ASE error log when DBCC PSS(0, < spid-value > ) is run against an active session. See KBA 2882391. |
| 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. |
| 821168 | The command DBCC SQLTEXT( < session-id > ) is unable to print the SQL statement that was most recently executed by the given session/spid. See KBA 2897963. |
| 821937 | A 820 error, ”Attempt to dirty non-log buffer BUF= < value > … which is in I/O.”, in the module ‘xls_bufpindirty_single’ together with a stack trace which includes the modules ‘pg_allocextent’ and ‘bulk_main’ may be reported in the SAP ASE error log when other sessions are concurrently dropping tables in system tempdb or a low durability database while a full database dump is being taken. See KBA 3140775. |
| 822048 | In rare circumstances, the message, "timeslice < negative-value > , current process infected", in the module 'dseg_proc_alloc' together with a stack trace which includes the modules 'execproc' and 's_execute', may be reported in the SAP ASE error log during the execution of a query. See KBA 2993737. |
| 822069 | The message, "FATAL UNHANDLED EXCEPTION: signal 0 hit while handling a previously hit signal. The server cannot continue and will shut down.", may be reported in the SAP ASE error log while Adaptive Server was dealing with an initial signal error resulting into an implicit ASE shutdown. See KBA 2953080. |
| 822733 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'bufunkeep_do_decrement()' may be reported in the SAP ASE error log when DBCC CHECKSTORAGE is executed for encrypted database. See KBA 2996176. |
| 822844 | Following an upgrade, Web Services reports that an unknown exception occurred: java.lang.UnsupportedOperationException: X509ExtendedKeyManager only supported on Server (See stack trace at bottom of this message). See KBA 3140740. |
| 822962 | A 913 error, "Could not find row in sysdatabases with database id < unknown-database-id > ", is unexpectedly not raised when the built-in LCT_ADMIN('abort', < spid > , < unknown-database-id > ) is executed and the SAP Adaptive Server auditing is enabled. See KBA 3216735. |
| 823359 | A 3105 error, "Data on dump will not fit into current database. Need < size > Mbyte database.", should be raised by Adaptive Server when a cumulative dump is loaded in a database whose size is not sufficient to hold the dump. See KBA 3216754. |
| 823938 | A new field 'dump_stripe_size' expressed in pages is added in the SAP Adaptive Server dump history file to reflect the stripe file size on disk after compression. |
| 824087 | The error message, "In order to perform this operation, you must have role 'sa_role'.", followed by a 19027 error, "Aborted dsam_check_access_auth operation due to error '20002'.", may be reported when a user with sa_role tries to execute the Data Store Access Management stored procedure dsam_set_collection while the SAP ASE configuration option 'enable granular permissions' is on. See KBA 3216694. |
| 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'. |
| 824355 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ord_getrowbounds' together with a stack trace which includes the modules 'ord_rowformat' and 'optimize_cmd' may be reported in the SAP ASE error log when a complex query which references more than 5 tables is compiled. See KBA 3035352. |
| 824358 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ssql_release' together with a stack trace that includes the modules 's_unkeep_cached_stmts' and 'sequencer' may be reported in the SAP ASE error log when a query is executed and the statement cache is full. This will result in an implicit Adaptive Server shut down. See KBA 3035656. |
| 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'. |
| 824935 | In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'pss_unkeep' together with a stack trace may be reported in the SAP ASE error log during the execution of a JDBC statement on Linux platform with FBO Adaptive Server binary. See KBA 3216170. |
| 825063 | On heavily-loaded SAP ASE systems, a high spinlock contention on spinlock SSQLCACHE_SPIN may be observed when the Adaptive Server available procedure cache memory is reduced due to a large amount of triggers having been created. See KBA 3150098. |
| 825079 | A query is not killable when using a very large IN CLAUSE while traceflag 132 is enabled to remove duplicates from the IN list. See KBA 3083815. |
| 825413 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'kbfusage' and 'kbmempooldiag' may be reported in the SAP ASE error log when DBCC MEMPOOL(" < fragment-pool > ", "usage") is executed. See KBA 3116304. |
| 825443 | A 9696 error, "Recovery failed to get the last oqid for database ' < database-name > ' from SAP Replication Server because it was either unable to connect or it received an error.", will be reported in the SAP ASE error log for HADR setups when Adaptive Server is started as new standby and the Replication Server is unreachable. Adaptive Server is enhanced to report troubleshooting steps in the error log. See KBA 3218730. |
| 825552 | A 945 error, "Unable to locate page < page-id > for database id < database-id > in the in-memory copy of Sysusages < session-id > . This is an internal error. Please contact SAP Technical Support.", may be reported in the SAP ASE error log, when missing master..sysusages rows are found during a database RECOVERY and when ALTER DATABASE or DBCC CHECKCATALOG is executed. Enable ASE trace flag 12506 and execute DBCC CHECKCATALOG to correct these discrepancies. See KBA 3218744. |
| 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. |
| 825603 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'GetSnapCounter' together with a stack trace which includes the module 'mda_fill_and_send_monProcessStatement' may be reported in the SAP ASE error log when querying the MDA table monProcessStatement. See KBA 3101978. |
| 825726 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" together with a stack trace which includes the modules 'EVP_MD_CTX_cleanup', 'EVP_DigestVerifyFinal' and 'ssl_handshake' may be reported in the SAP ASE error log during an SSL connection attempt. Alternatively the stack trace may report the modules 'ASN1_item_ex_d2i' and 'ssl_nopen'. See KBA 3127496. |
| 825781 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'mbkt__coalesce_set' together with a stack trace that includes the modules 'mbkt__coalesce_pool' and 'mbkt__consolidator', may be reported in the SAP ASE error log when the Adaptive Server 'bucket manager consolidator' task administrates memory fragments. See KBA 3114532. |
| 825784 | A 632 error, "Attempt to move memory with an incorrect length of -1. Maximum allowed length is 16384.', may be reported in the SAP ASE error log during the execution of a dynamic SQL query with streamlined LOB parameter that has been interrupted by the end-user. See KBA 3132077. |
| 825823 | In rare circumstances, SAP ASE may unnecessarily recompile a stored procedure that is using temporary tables. Adaptive Server should be started with trace flag 17012 in order to enable the fix. See KBA 3118874. |
| 825837 | A 10350 error, "Permission related internal error was encountered. Unable to continue execution.", may be reported when SELECT-INTO is executed by user1 and the target table is owned by user2 while the SAP ASE configuration option 'granular permissions' is enabled. See KBA 3216159. |
| 825854 | When an Adaptive Server engine thread is brought offline while SAP ASE configuration option 'kernel mode' is set to threaded mode, the 'StopTime' column from the MDA table 'monEngine' does not get updated. See KBA 3122853. |
| 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. |
| 825868 | In rare circumstances, the message "Current process infected with signal 10 (SIGBUS)" in the module 'ssl_nrpacket' together with a stack trace which includes the modules 'iocPoll' and 'iocRunController' may be reported in the SAP ASE error log, for SSL connection during login phase. See KBA 3149096. |
| 825881 | The built-in suser_name() may return an incorrect value when it is executed from a DBO owned stored procedure with execute as owner. See KBA 3216746. |
| 825882 | When the configuration option 'enable literal autoparam' is set to 2, SAP Adaptive Server will disable literal auto parameterization for stored procedures. See KBA 3150586. |
| 825915 | When a 8419 error, "Could not find index descriptor for objid < object-id > , indid < index-id > in dbid < database-id > .", is occasionally reported in the SAP ASE error log, additional information will now be reported by Adaptive Server for the command being executed at the time the error was hit. See KBA 3129040. |
| 825935 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeSendRow::_sendColsToClient' followed by a stack trace which includes the modules 'LeSendRow::sendRowToClient' and 'exec_lava' may be reported in the SAP ASE error log when a SELECT query retrieves an in-row LOB column whose value has been previously updated to NULL from a non-NULL value. See KBA 3157053. |
| 825965 | In rare circumstances an unplanned failover may be triggered by the SAP Fault Manager under an HADR setup when the Adaptive Server Replication Agent switches to synchronous mode while the Replication Server is still running in asynchronous mode. See KBA 3217287. |
| 825970 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ubffreef' together with a stacktrace which includes the modules 'prCONST_val' and 'lock__print_deadlockchain' may be reported in the SAP ASE error log while Adaptive Server reports deadlock information. See KBA 3134686. |
| 825977 | In rare circumstances, a timeslice error together with a stack trace which includes the modules 'ssl_nclose' and 'drop_connection' may be reported in the SAP ASE error log when SSL is in use. Adaptive Server needs be started with trace flags 7871 and 3623 to allow gather diagnostics. See KBA 3149491. |
| 825999 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'rvm__ipcr_comp' together with a stack trace which includes the modules 'rvm_migrate_pcrtree' and 'execproc' may be reported in the SAP ASE error log when a stored procedure that has a server CURSOR declared with multiple UNION ALL statements is executed. See KBA 3149527. |
| 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 |
| 826025 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'TraceOut::operator' together with a stack trace which includes the module 'ShowStmtHeader' may be reported in the SAP ASE error log when executing the built-in show_cached_plan_in_xml() against a prepared statement. See KBA 3138487. |
| 826029 | The message, "Session < value > found unrecognized Query type -1 (processQuery()", may be reported by the SAP ASE Workload Analyzer Command Line Utility while analyzing a capture. See KBA 3138974. |
| 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. |
| 826037 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'prSQLTEXT' together with a stack trace which includes the modules 'exec_dbcc' and 's_execute' may be reported in the SAP ASE error log when DBCC SQLTEXT is executed against a live session (spid). See KBA 3148608. |
| 826095 | SAP Adaptive Server may intermittently shutdown on Windows O/S with no message reported in the error log when XML is in use. See KBA 3142790. |
| 826122 | A 4306 error, "There was activity on database since last load, unable to load. Must restart load sequence with the load database to continue.", may be reported during LOAD TRANSACTION after DBCC CHECKDB or DBCC CHECKCATALOG are executed while the database is kept offline in load sequence. See KBA 3143853. |
| 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. |
| 826143 | SAP ASE Workload Analyzer Command Line Utility reports "Start Time" as UTC time in "capture show < capture-name > " or "replay show < replay-name > " commands. |
| 826146 | A 13986 error, "Ownership change of object ' < object-name > ' failed. See previous messages for more information", may be reported when ALTER TABLE .. MODIFY OWNER is executed and the table has a trigger that has two or more actions (for insert, update, delete). See KBA 3145743. |
| 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. |
| 826160 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeScanOp::_LeOpShowOp' together with a stack trace which includes the modules 'le_showPlanOp' and 'showplan' may be reported in the SAP ASE error log when running sp_showplan against a session whose queried object may have been dropped by another session in the meanwhile. See KBA 3147969. |
| 826183 | Log4j 1.x is removed from SAP ASE/SRS/SDK. See KBA 3129897. |
| 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. |
| 826214 | A 2824 error, "Process < session-id > cannot hold PROC_BUF < address > named ' < object-name > ' because it holds another PROC_BUF < address > named ' < object-name > '. A process can only hold one view, rule, or default at a time.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'proc__linktopss' and 's_getTreeOrPlan' when a java user defined function is executed while the configuration option 'enable java' is disabled. See KBA 3158443. |
| 826224 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'fglk__free_promoted' together with a stack trace which includes the modules 'fg_lock' and 'apl_getnext' may be reported in the SAP ASE error log when Adaptive Server attempts to promote to table level locking while executing a query. This will result into an implicit ASE shutdown because the spinlock 'rlockpromotion_spin' was held while the error was hit. This issue may happen if the query is using SQL User Defined Function executed in parallel. See KBA 2812380. |
| 826313 | The execution of UPDATE STATISTICS or DELETE STATISTICS is not impacted anymore by the failure to write the log records for replication of the command in an HADR setup. Such a failure is now reported with a warning message 11314, "Failed to write the replication log record for the ' < command-name > ' command in database ' < database-name > '. The ' < command-name > ' command will not be replicated.", in the SAP ASE error log. See KBA 3218756. |
| 826322 | SAP ASE Workload Analyzer Command Line Utility may report incorrect "Total Count" and "Ratio" under "Errors" tab in exported Excel format capture or replay dashboard. See KBA 3167303. |
| 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. |
| 826377 | The stored procedure sp_quotepartitiontext may incorrectly report or update a partition key for a round robin partition table that contains one or more bigdatetime or bigtime columns and the partition key is not bigdatetime or bigtime. See KBA 3170733. |
| 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. |
| 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. |
| 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. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 826869 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules ‘dumpnames’ and ‘uni25m2__sqlhilo’ may be reported in the SAP Adaptive Server error log during DUMP DATABASE execution and TSM is in use. See KBA 3238651. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP04 PL03, ASE SP04 PL03, SP04 PL03 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)