/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 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 | Description |
|---|---|
| 718500 | The message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace that includes the module oj_syboj_ojdepends_maps(), may be reported in the SAP ASE error log when executing an illegal OUTER JOIN request. An appropriate error should be raised instead. |
| 732482 | A query against a remote table may get a signal 11 (SIGSEGV) during UPDATE STATISTICS. |
| 745786 | In rare circumstances, an 871 error, "Process < spid > is trying to release a latch on buffer < buffer_address > (dbid: < dbid > , pageno: < pgid > ) without holding a latch on the buffer." may be reported after a resource governor error is hit. |
| 757484 | In some heavy loaded environment, SAP ASE might report a timeslice error in the SAP ASE errorlog with a stack trace mentioning the function plgrabstats(). |
| 784729 | Allow lightweight permission checking for non-imdb queries also. This also helps to reduce unnecessary reads on sysobjects table, seen as a separate issue under CR 791956. |
| 787670 | SAP ASE server is enhanced to clear uninitialized TIPSA flags automatically under new traceflag 7167 when accessing text/image/unitext columns. If you have never previously used LOB compression feature on the database, this helps avoid 632 errors if you don't have enough time to run DBCC commands to check and fix all text pages in huge databases. Later if you plan to use LOB compression feature, turn off traceflag 7167, then check and fix if needed all text pages. Do not enable this traceflag if you have previously used LOB compression in the database. See KBA 2107660. |
| 788517 | A 3328 error, "Redo of 'CREATE INDEX' in transaction ID (0,0) for table name < > , object ID < > did not find 'syscolumns' system catalog log record. Recovery of database < > cannot continue." followed by 3329 error, "Redo of 'CREATE INDEX' for table < > , object ID < > did not build compression information. Recovery of database < > cannot continue." followed by 4314 error, "Cannot find table < > to recreate index < > ." may be reported during LOAD TRANSACTION in the SAP ASE error log while an index is logically rebuild. See KBA 2216220. |
| 791224 | Executing a procedures doesn't raise 10386 error (permission denied error) when the caller/session owner of the procedure doesn't have appropriate permissions for the statements defined in the stored procedure. |
| 794974 | KBA 2270636 - Error 8211 - A newly created ssql_id for SQL to store in statement cache is a duplicate object id of an existing table in system tempdb. |
| 795533 | In rare circumstances on a heavily-loaded multi-engine system, a timeslice error in the module 'ubo_slotscan_getnext' together with a stack trace which includes the modules 'mda_populate_monCachedProcedures' and 'VTABRemoteAccess::getNext' may be reported in the SAP ASE error log when the MDA table monCachedProcedures is queried. See KBA 2393400. |
| 799194 | An 806 error, "Could not find virtual page for logical page < > in database < > " may be reported after loading a database dump that is followed by one or more transaction dumps while trying to access a page, if the database was shrunk before taking the database dump or a transaction dump followed by a database extension that was captured in a following transaction dump. |
| 799493 | A 29006 error, "Invalid DOL data row pointer: row < > with status 0x800 must be normal row instead of compressed row" may be reported when running SELECT-INTO while the compatibility mode is enabled and some of the tables are compressed. See KBA 2327918. |
| 799568 | REORG DEFRAG with resume may cause table corruption. Error 614 (Illegal length) and 9991 (Orphan row not marked committed delete) may subsequently be reported when running DBCC CHECKTABLE. See KBA 2329226. |
| 800167 | The command DUMP DATABASE CUMULATIVE could fail and the backup server could die if the table SYSDAMS became corrupted. |
| 800300 | KBA 2385151. The message, "Current process infected with 11 (SIGSEGV)" in the module 'execproc' together with a stack trace which includes the modules 'sequencer' and 's_execute', may be reported in the SAP ASE error log when a stored procedure is executed. |
| 800370 | On AIX, in a rare situation, a client application may hang after sending a new command after a cancel had been sent to the client. |
| 800461 | SSL connections fails intermittently. |
| 800625 | A 940 error, "Dbtable in wrong state for operation: DBTABLE pointer = < value > , dbid = < value > , state = < value > , status= < value > , keep = < value > , system task keep = < value > , name = < value > " with state 11 and 52 might be seen when customized optimization goal setting is on. |
| 800733 | Dropping a database on a corrupt device can lead to timeslice errors and result in corruption of the master database. |
| 801024 | A 12316 error, "Internal error: Attempt to garbage collect a deallocated data page < > in table < > , database < > . Aborting the transaction.", may be reported by HKGC task when accessing a deallocated page while concurrent DML activity is taking place in parallel and some commands are rolled-back. |
| 801058 | The command DBCC CHECKALLOC could report a discrepancy between the actual number of free log pages and the cached number of free log pages, after ALTER DATABASE LOG OFF fails with an error 5053 due to existing log pages in the log fragment to be shrunk. See KBA 2422628. |
| 801114 | When inner table of an OUTER JOIN query has in-row LOB column which is not part of the transitive closure, the query should succeed without a stack trace. |
| 801424 | In Sun Cluster, failover is not triggered because the script which uses haisql is not able to get the correct state of the companion SAP ASE. |
| 801427 | Query with join and search clause comparing VARBINARY column and VARCHAR constant may return incorrect results. Rows which should be qualified are not returned. Showplan option will indicate that a unique index is used to scan the table with VARBINARY column. |
| 801598 | In rare circumstances, an 806 error, "Could not find virtual page for logical page < > in database < > ." may be reported in the SAP ASE error log after performing a LOAD DATABASE whereby the target database diskmap does not match that of the source database in the dump. Alternatively in KBA 2411446, a 4343 error, "An error occured when converting the row offset table in the page < > of object ID < > . Either the number of rows, < > , or the free offset in the page, < > , is incorrect. The conversion will be skipped. Please, contact SAP product support." may be reported when performing a cross-platform LOAD DATABASE. See KBA 2420672. |
| 801789 | When "set forceplan on" is enabled, the internally generated abstract plan may lead to very inefficient plan to satisfy the forceplan for the queries which involved min/max operations. See KBA 2364881. |
| 801824 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database < dbname > because the requested RID has a higher number than the last RID on the page.", or a 625 error, "Adaptive Server failed to retrieve a row via its RID in database < dbname > because the entry in the offset table for that RID is less than or equal to 0.", may be reported while a row is inserted into an APL table that has a clustered index and the insert causes a page split to happen. |
| 801912 | The message "Current process infected with 11 (SIGSEGV)" in the module 'mem__pageallocate_this_engine' together with a 718 error, "Memory allocation from process private memory is being performed by an incorrect process. Current Spid: ' < value > '. Owning Spid: ' < value > '. Memory: ' < value > '. This is an Adaptive Server internal error. Please contact SAP Tech Support." and a 707 error, "System error detected during attempt to free memory at address < value > . Please consult the ASE error log for more details." may be reported in the SAP ASE error log when a stored procedure involving temporary tables is executed. |
| 802083 | KBA 2396565-The error 705, "There is no room for process < value > to store PROC_HDR < value > in Pss.", together with a stack trace which includes the modules 'memalloc' and 'add_prochdr' may be reported in the error log when an explicit kill < spid > or attention is received by a process that is being killed contains some temporary tables. |
| 802213 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'ubffreef' together with a stack trace which includes the modules 'fdp_free_memory' and 'terminate_process' may be reported in the SAP Cluster Edition ASE error log when a session terminates resulting in SAP ASE shutting down implicitly. See KBA 2369414. |
| 802687 | High contention may be seen on the spinlock 'Resource- > rdbt_spin' in a heavily loaded multi-engine SAP ASE system resulting in performance degradation, when many concurrent Light Weight Procedures being executed while the SQL statement cache is enabled. |
| 802768 | In rare circumstances a hang may occur in SAP ASE between two sessions whereby the first session hangs in the module 'plc_flush' waiting for a page to be written on disk by holding a lock on the second session Private Log Cache, while the second session is writing the same page on disk and is waiting to acquire the lock on its own Private Log Cache. |
| 802811 | In rare circumstances on a heavily-loaded multi-engine system, a timeslice error in the module 'kboalloc' together with a stack trace which includes the modules 'ptn__pdes_grab' and 'des__fill_common' may be reported in the SAP ASE error log during execution of the built-in row_count(). |
| 803189 | A 624 error "Adaptive Server failed to retrieve a row via its RID in database < dbname > because the requested RID has a higher number than the last RID on the page.", may be reported while transaction rollback containing an open cursor on an Allpages Locked Table (APL) with a clustered index and one or more nonclustered indexes, if DML within that transaction had a cursor pointing to a row, which is not the last row of the table. |
| 803497 | A 7377 error, "SELECT INSERT cannot be specified with isolation level clause." may be reported when a select-insert command is executed because the OMNI layer may add to the query the clause "AT ISOLATION" mistakenly. |
| 803547 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'com__exctnume_copy' together with a stack trace which includes the modules 'mod_numeric' and 'LeRun' may be reported in the SAP ASE error log when a query that involves modulus operations on numeric variables is re-executed. See KBA 2397851. |
| 803864 | A 511 error, "Attempt to update or insert row failed because resultant row of size < > bytes is larger than the maximum size ( < > bytes) allowed for this table. Command has been aborted." may be reported when running UPDATE on a compressed table. See KBA 2398449. |
| 803900 | In rare situations, disconnected client can cause orphaned task in SAP ASE. |
| 803935 | The monThread MDA table will report the same statistics metrics for all threads on the Linux platform. The thread utilization in sp_sysmon output is reported incorrectly. A typical symptom is the thread utilization for all threads are the same and might exceed 100%. |
| 804157 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log old timestamp= < > . Log record marker = ( < > , < > )." may be reported in the SAP ASE error log during boot time recovery after a non-polite SAP ASE shutdown while an REORG REBUILD command was running. Alternatively a 3478 error may be reported during recovery undo processing. See KBA 2404095. |
| 804197 | An 805 error, "Bad pointer < > encountered while remapping stored procedure < > . Must re-create procedure.", may be reported when LOAD DATABASE is run and the database dump that is loaded was taken with a pre-15.7 SP130 SAP ASE version. See KBA 2423678. |
| 804276 | Parallel queries do not use User Thread Pools for worker threads. See KBA 2214120. |
| 804347 | In rare circumstances, when semantic partitioning is enabled, A stack trace might be observed if select query has join of list partitioned tables with equality predicate. |
| 804381 | Multiple messages (1562, 1563 and etc.) are not re-directed to the trace file when tracing is enabled. See KBA 2407736. |
| 804411 | In rare cases, queries involving a view on the inner side of an OUTERJOIN and having a subquery, may result in the optimizer timing out without a legal query plan . |
| 804606 | In rare circumstances the message, "Current process infected with 11", together with a stack trace that includes the modules dol_get_delrows_indeallpg() and undo_dol_xalloc_nolink() may be reported in the SAP ASE error log when recovery is undoing a REORG REBUILD command that was not finished at run-time. See KBA 2423084. |
| 805162 | In a highly loaded system where the statement and procedure caches are not sufficiently configured, the message "current process infected with 11 (SIGSEGV)" in the module 'ssql_lookup', or 'ssql__getdesc', or 'ssql__choose_victim' may be reported in the SAP ASE error log with the message 'Spinlock SSQLCACHE_SPIN' held, resulting in an implicit SAP ASE shutdown. |
| 805208 | If there is a stored procedure running at ISOLATION LEVEL 0 with: "INSERT ... SELECT ..." command without a FROM clause OR "SELECT ... INTO ..." command without a FROM clause and with "INSERT SELECT AT LEVEL 0" feature enabled the stored procedure may run into multiple recompilation error (11060). |
| 805280 | For SAP ASE running in threaded kernel mode, a task (spid) may get stuck in kctCheckAsync(), i.e. DBCC STACKTRACE( < spid > ) shows function kctCheckAsync. This spid can be killed using 'kill < spid > ' if traceflag 7866 is enabled, or if the time (in minutes) indicated by the SAP ASE configuration parameter 'async poll timeout' period has elapsed, then the task automatically returns from kctCheckAsync() function, closing the remote connection. |
| 805301 | In rare cases, the 940 error message, "Dbtable in wrong state for operation", may be repeatedly reported in the SAP ASE error log when a error related to dbt_keep count going into negative values happens in a specific clean up code path. |
| 805449 | The message, "Current process infected with 11 (SIGSEGV)", in the module copy_sqltext() followed by a stack trace including the modules sqlpars() and internal_sql(), may be reported in the SAP ASE error log after the configuration options 'enable monitoring' and 'show deferred compilation text' are turned on. See KBA 2428396. |
| 805498 | In rare circumstances on heavily-loaded systems create table in in-memory database may hang with a stack trace which includes the modules getpage__noscan(), getpage_with_validation() and bufsearch_cache_getlatch(). |
| 805984 | SAP ASE unxepectedly raises error 17260, "Can't run < sproc name > from within a transaction.", if sp_monitorconfig is run in chained mode. |
| 806017 | KBA2452601 - A 8224 error, "Internal error: could not save description of lightweight procedure < > " together with a stack trace which includes the modules 'open__lwpbyname' and 'sqt_get_plan' may be reported in the SAP ASE error log while reinstalling a DES for a lightweight procedure in the metadata cache. |
| 806094 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'tdsrecv_params' together with a stack trace which includes the modules 'tdsrecv_rpc' and 'execrpc' may be reported in the SAP ASE error log when running an RPC, either when an error has caused the current command abort, or the end-user has interrupted the RPC execution, or the connection was lost. See KBA 2479094 |
| 806622 | High contention may be seen on the spinlock 'Resource- > rdbt_spin' in a heavily loaded multi-engine SAP ASE system resulting in performance degradation, as shown in the Spins column of table monSpinlockActivity. |
| 806687 | In rare circumstances the message, "Current process infected with 11", together with a stack trace that includes the modules dol_get_delrows_indeallpg() and undo_dol_xalloc_nolink() may be reported in the SAP ASE error log when recovery is undoing a CREATE INDEX with computed columns that was not finished at run-time. |
| 806724 | The message, "Current process infected with signal 11 (SIGSEGV)" involving the function dol_update() or decompress_column_by_coloff() or the error message 644 or the error message 2601 may be reported in the SAP ASE error log when executing ALTER DATABASE changing the options 'set compression' and 'lob_compression' together. See KBA 2447629. |
| 806726 | In rare circumstances, the message "current process infected with 11" in the module 'ssql__ubffree' together with a stack trace which includes the modules 'sqt_put_in_stmtcache' and 'ssql__rmplans' may be reported in the SAP ASE error log during the execution of a query resulting in SAP ASE shutting down implicitly while holding the spinlock SSQLCACHE_SPIN. |
| 806965 | SAP ASE will intermittently fail to bring one or more engines online during boot while allocating memory for the engine. See KBA 2447283 |
| 807092 | KBA 2455587 The Bucket Pool entries in the configuration file disappear after modifying a configuration parameter with sp_configure. |
| 807666 | In a replication environment using LTL, when Replication Agent ignores the truncation point received from Replication Server after determining that it is not valid as indicated by a warning message in the SAP ASE error log, data may stop being replicated or Replication Agent may terminate abnormally with a 624 error - "Adaptive Server failed to retrieve a row via its RID in database ' < db > ' because the requested RID has a higher number than the last RID on the page. < rid > . < page > " |
| 808631 | The error "ERROR !!! Skipped patching dbid. Page in run < > . Page in buffer < > ." will be mistakenly printed in the SAP ASE backupserver error log for every allocation page when doing cross platform load. |
| 808774 | dbcc shrinkdb_setup fails with message 10350 state 45 when SAP ASE is configured to enable granular permissions. Workaround is to temporarily turn off granular permissions while running shrinkdb_setup. |
| 808888 | The fix for a long running internal 'sort_local' transaction during cursor processing causing tempdb log full scenario is turned on by default (previously TF 11821 was needed to turn this fix ON), and now TF 11820 can be used to turn the fix OFF. |
| 809093 | The error message "Logical page < page_num > is not in the given database map" will be printed in the SAP Backupserver error log followed by a stack trace in the SAP ASE error log including the module 'dmpld_send_dbdam_runlist' at DUMP DATABASE time if the database option 'allow incremental dumps' is enabled and SAP ASE failed to allocate the required number of pages to store the bitmap of changed pages. |
| 809102 | If the orphan table was created by a stored proc (so the table name starts by #toto01 #toto02 #toto03) and the stored proc us rerun by the same spid, the temporary tables is not detected as being an orphan and a "cannot create table because it already exists.." error may be reported. |
| 809308 | A 941 error, "Illegal database context operation", will be reported when LOAD DATABASE of master database is run. |
| 809330 | A 9502 error, "Data exception - string data right truncated Command has been aborted.", or truncated values for 'Name' column, may be reported if a configuration option name exceeds 25 characters while SP_MONITORCONFIG with the 'all' option is run and the set option string_rtruncation is enabled. |
| 809381 | In rare circumstances when REORG REBUILD is terminated using ^C, sp_help on the table undergoing REORG REBUILD returns error 17461, incorrectly indicating that object does not exist in the database. |
| 809638 | Sometimes, an SAP ASE spid hangs in the module 'prepprev' after rollback due to error 2601 (duplicate key error). |
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 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition
Keywords
Change Request, Fix, Patch, SP 139, , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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)