/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 |
|---|---|
| 55716 | If a database device does not have any segment associated with it, sp_helpdb incorrectly prints the usage of this device fragment as "data only" instead of "unused by any segments". |
| 497173 | Executing sp_tables against a User Defined Function may report some status incorrectly. See KBA 2411224 |
| 552310 | When the maximum number of allowable user defined types are added, despite deleting some of existing user defined types, does not make room for adding new types. |
| 635454 | The file size generated when the set option 'tracefile' is enabled is limited to 2GB. KBA 2089573. |
| 677266 | A 6908 error, "During redo the page timestamp value is less than old timestamp from log ..." may be raised in the SAP ASE error log while loading a transaction dump having two transactions TEXTSTOR and TEXTFREE on sysattributes system table that are used by Web Services in the source database. See KBA 2294696 |
| 680410 | The execution of the system stored procedure sp_help_rep_agent with a client application which doesn't support large identifiers fails with error 103 because the identifier 'max_number_of_replication_paths' is too long. See KBA 1945011. |
| 716957 | In rare circumstances, a 614 error, "Adaptive Server accessed a row that has an illegal length of < value > while in data base < database > " may be reported when running DBCC FIX_TEXT on a data-only-locked table. |
| 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. |
| 722778 | When executing DBCC CHECKSTORAGE, the worker processes created show the current database name, instead of tempdb, in the 'tempdbname' section of sp_who output. See KBA 2119852. |
| 725140 | In some rare cases, running queries involving SQLUDF could lead to stacktrace in cpysqludf(). |
| 725714 | A new feature request to avoid sysattributes look-ups for user defined role activation during login processing. |
| 732482 | A query against a remote table may get a signal 11 (SIGSEGV) during UPDATE STATISTICS. |
| 734313 | Verifications are added in the module 'plc__shiftblock' when the PLC of a session contains erroneous metadata and is about to damage another session PLC while a 3475 error is reported. Under rare circumstances the error message 140063, "ERROR in < module_name > for plc < 0x > ... " may be reported in the SAP ASE error log. |
| 742910 | A timeslice error with a stacktrace in the module 'copy_colinfo' may be seen for queries using a "*" in the select into list along with a join clause, where one of the columns in the projection is an encrypted column. |
| 745608 | CREATE INDEX allows '.' (period) in the index name with quoted identifiers. Once created, the index then can not be dropped through normal means. See KBA 2475406. |
| 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. |
| 747033 | There could be a deadlock between level0 scanner and alter table add/drop utility, when we have "enable utility lvl 0 scan wait" set to one, when there is L0 cursor open by the scanner. |
| 747444 | Customer may see error 644 when create a temp table and hit memory issue in the middle of update syspartitions table. |
| 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(). |
| 760523 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sqt_deallocate' together with a stack trace which includes the modules 'lwp_create' and 's_cache_stmt' may be reported in the SAP ASE error log after 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.", is reported when a SELECT query is executed. See KBA 2496908. |
| 761436 | When a DESC global clustered index is created on a roundrobin partitioned table, then reorg rebuild on the table may fail with error 1530: "Create index with sorted_data was aborted because of row out of order". See KBA 2415363 |
| 763615 | A 9502 error, "Data exception - string data right truncated", may be reported during ALTER TABLE MODIFY column to NULL with multi-bytes charset and the session property string_rtruncation is set. |
| 763637 | When Rep Agent is processing the execution of the stored procedure rs_marker with a null parameter value, the message "current process infected with 11" together with a stack trace which includes the modules 'ra__process_request' and 'ra__pack_cmd_request' may be reported in the SAP ASE error log. In rare circumstances, the message "current process infected with 11" together with a stack trace which includes the modules 'ra_free_mempool' and 'ubffreef', or 'ra_malloc_mempool' and 'ubfalloc' may be reported in the SAP ASE error log if the Rep Agent memory pool gets corrupted. |
| 765005 | A 7222 error, "Received bad token 0xff from site ' < server name > '", may be reported in the SAP ASE error log when a nested RPC is executed. |
| 765203 | On AIX in threaded kernel mode, the monEngine connections column is incorrect and dump database may fail with 'soc_nconnect: No free file descriptors available' raised in the errorlog when executed concurrently with sp_listener. See KBA 2573288. |
| 767440 | The built-in ISNUMERIC() incorrectly returns 1 (indicating that conversion to int, float, money or decimal is guaranteed to be allowed) for some inputs such as '.', ',', '$', '+', '-', 'e' that can appear in numeric values but are not valid numeric values on their own. See KBA 2053654. |
| 767540 | View definition containing 'with check option' cause was not saved in syscomments system catalog during upgrading to a newer SAP ASE version |
| 769607 | When creating a partitioned table with a large number of partitions (greater than 3000) and a large number of local indexes (greater than 10) then a 702 error may result. |
| 772020 | The XML output of cached plans may lead to XML parsing errors if it contains parameters values with XML meta-characters like '&', ' < ' or ' > '. |
| 774871 | Under rare conditions, error 14622, "The dbinfo anchor in the database '% < dbname > ' is already locked by the task", could be raised when attempting to lock the database context information structure during exception handling. |
| 775488 | Optimization for "filling free space info" after an inpolite shutdown of SAP ASE. |
| 777172 | sp_cacheconfig fails with an Arithmetic overflow error when the cache size exceeds 2TB. |
| 777610 | KBA2594291 / 2215570 After abnormal shutdown of job scheduler due to issues like inconsistency in Job Scheduler work tables, failing to execute jobs, js stop functioning due to resource issue or disconnecting with jsagent, the job scheduler does not restart automatically after "max js restart attempts". |
| 778143 | Order-by queries with 7 or more tables or that use compatibility mode may generate a 325 error (no legal query plan found). This behavior can be sporadic. Note that the 7 or more tables may consist of worktables used to materialize interim results. For example, aggregates that contain a distinct clause may require a worktable to calculate the result. These interim tables will then need to be joined back together to produce a final result. |
| 781057 | wrong result could happen when using a scalar aggregate derived table/view as an outer join inner table during INSERT or SELECT...INTO. SELECT c1= d1.d1a , c2= d2.d2a INTO selinto1 FROM (select d1a=avg(c3a) from t3) d1 LEFT JOIN (select d2a=sum(c2a) from t2) d2 ON d1.d1a != d2.d2a WHERE d1.d1a != d2.d2a |
| 781081 | A 8207 error, "Couldn't find an available descriptor for an object. Raise the value of the configuration parameter 'number of open objects' for more descriptors", may be reported when executing UPDATE STATISTICS WITH HASHING, leading to incorrect statistics being computed. See KBA 2555080. |
| 782869 | KBA 2197020: SQL query with TOP and abstract plan using user defined optimization goal may fail with stack traces reported in the error log. |
| 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. |
| 785213 | When sp_cacheconfig is executed from tempdb a message "An attempt was made to startup a multi-database update in database 'master' after starting up the master transaction in a temporary database. This could render the database 'master' unrecoverable and this update is therefore not allowed." is displayed. A better message should be displayed. |
| 785304 | When multi-path replication is enabled, suspending the connection of a Rep Agent sender to SRS while no replicated activity occurs on the primary database may result in a hang situation, instead of a Rep Agent re-scan. Furthermore, if activity on the primary database causes the hang to cease, Rep Agent will terminate instead of re-scanning. |
| 786596 | When HK Ignore option is specified then showing of Cache Status as HK ignore for log only and default cache type in sp_cacheconfig. Earlier HK Ignore was shown for mixed cache only. |
| 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. |
| 789277 | The error message, "CT-LIBRARY error: ct_results(): protocol specific layer: external error: There is a TDS protocol error", is reported back to the client when SAP ASE executes a remote procedure that exists in SAP IQ and the procedure has an output parameter that is either decimal, numeric or datetime. See KBA 2213838 |
| 789993 | SAP ASE running on Windows with encryption enabled, under rare situation may experience client disconnection with the following message in the SAP ASE log - "An I/O error occurred during the underlying SSL operation. Check your I/O callback handler return values and error codes.". |
| 790463 | Procedure cache may get full with multiple plan copies of single stored procedure involving DDL inside a transaction. |
| 790982 | A spid may hang and be unkillable if the client is unable to receive or stops receiving network requests from SAP ASE running on AIX. See KBA 2000952. |
| 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. |
| 792092 | SAP ASE on Linux hits 823 errors when the underlying storage disk is configured for 4K sector size. See KBA 2243658. |
| 792149 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'th_accounting' together with a stack trace which includes the modules 'xact__postcommit_processing' and 'th_ext_unreserve', may be reported in the SAP ASE error log while executing DBCC FINDSTRANDED or DBCC DBREPAIR( < database_name > , findstranded). See KBA 2554434. |
| 792295 | In rare circumstance, error 15946, "Invalid column length %d found for column, column ID %d, row ID %d, page number %u, partition ID %d. The length is greater than the expected maximum column length %d.", may be reported by dbcc checkdb() or dbcc checktable() after some columns are dropped using "alter table ... with no datacopy". |
| 793217 | Transferring NULL LOB data from remote source via INSERT-SELECT may result in wrong data inserted. |
| 793969 | Sybmon command "keptbuf < spid > " will report signal 11 error on a memory dump without including page cache. |
| 794933 | MSA Replication using SQLDML causes DSI thread down due error 11055 |
| 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. |
| 795557 | A 5605 message, "Prepare transaction RPC to the remote server < server_name > failed. Transaction key < key_value > . Return status -2.", may be reported because an external transaction is out of synchronisation between the local server and the remote server after a deadlock occurs on the remote server. See KBA 2276710. |
| 795863 | Multiple concurrent transaction dumps started while a full or cumulative dump is running can unnecessarily delay the latter command completion time. |
| 796164 | A 3702 error, "Cannot drop or replace the encryption key ' < encryption_key_name > ' because it is currently in use.", should be reported when DROP ENCRYPTION KEY < encryption_key_name > is run while the encryption key is still referenced, but the key was dropped mistakenly and no message was raised. |
| 796208 | Under rare circumstances, SAP ASE on Windows platform may leak memory when using security identifiers. |
| 796418 | Remove a number of duplicate wait events to improve the accuracy of the wait event diagnostics. |
| 796566 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'Lop::lopProcessTree' together with a stack trace which includes the modules 'Lop::lopProcessTree' and 'lopGenerate' or in the module 'OptBlock::_OptInitProducerPj' together with a stack trace which includes the modules 'OptBlock::OptPhaseInitPj' and 'OptGlobal::GblAssignOptId', may be reported in the SAP ASE error log when a GROUP BY is used in a subquery and the subquery selects only a CONSTANT in its projection and the subquery does not have a HAVING clause. See KBA 2290097. |
| 797041 | A 1163 error, "The space allocated to the sysgams table in database ' < dbname > ' (dbid = #) must be at least 16 pages.", together with a stack trace which includes the modules 'pggam__srchonegampage' and 'pg_allocate_syslogs' may be reported in the SAP ASE error log when using CREATE DATABASE FOR LOAD to create a database bigger than 63GB in a 2KB server, 128GB in a 4KB server, 256GB in an 8KB server or 512GB in a 16KB server, with dedicated log devices which are placed out of that range. See KBA 2269985. |
| 797450 | A 2809 error, "Request for view < table_name > failed because < table_name > is a table object." may be reported during the execution of a stored procedure that has a view reference if the stored procedure was initially compiled and later the view was dropped and a table was created with the same name as the dropped view. See KBA 2297847. |
| 798192 | sp_help does not work in chained transaction mode. |
| 798255 | Error 2762 "The 'DROP TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database." is reported when signal druing post commit shrink. |
| 798608 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc_ddlmap_release' together with a stack trace which includes the modules 'ddlmap_finish' and 'xact__commit_local', may be reported in the SAP ASE error log when the database option "ddl in tran" is enabled and a transaction that contains many INSERT commands in a single batch is executed. See KBA 2316693. |
| 798669 | The error 247, "Arithmetic overflow during implicit conversion of UNSIGNED INT NULL value < > to a INT field", may be reported when sp_spaceused is executed on very large databases (of size > 4TB). |
| 798781 | In rare circumstance, a 7105 error, "TEXT/IMAGE/UNITEXT page < page # > does not have a next page. Either there is a suspect text page chain, or transaction isolation level 'read uncommitted' has been set. Database tempdb, table < table name > , first text page < page # > ", may be reported when inserting data into a UNITEXT column. |
| 799127 | A 804 error, "Unable to find buffer '0x%lx' from cache '%.*s' holding logical page '%u' in sdes '0x%lx' kept buffer pool for object '%.*s'.", maybe reported when queries generate DOL worktable and truncate it. |
| 799147 | Error 1295 "Unconditional lock request for table or page 'pageid', dbid 'dbid' was made while holding a latch." may be reported when btree index splits. |
| 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. |
| 799308 | A 12306 error, "No table lock on object < system_tablename > in database < proxy_dbname > ", may be reported when executing SELECT INTO from a source system table into a proxy database as a non-sa user. |
| 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. |
| 799690 | KBA 2402238. The message "current process infected with 11" in the module 'memmove' together with a stack trace which includes the modules 'tdsrecv__dynexec' and 'tdsrecv_params' may be reported in the SAP ASE error log if a JDBC application has the DYNAMIC_PREPARE option enabled while a dynamic INSERT command is executed that involves parameter values of VARCHAR type. |
| 799969 | In rare circumstances, when the database option 'allow page signing' is enabled, a task may hit a time slice error reported in the SAP ASE error log. Alternatively the error 'ulpspinlock: spinlock order violation' may be reported. |
| 800118 | A 16805 error, "A LOB LOCATOR was used that is no longer valid: Either the transaction that created it has ended or it has been deallocated.", may be reported during the execution of a stored procedure that has a SELECT query which assigns a text value into two LOB local variables. See KBA 2462386 |
| 800167 | The command DUMP DATABASE CUMULATIVE could fail and the backup server could die if the table SYSDAMS became corrupted. |
| 800208 | The recovery of a database appears to hang. Multiple executions of DBCC SHOWRECOVERY will show the recovery processing the same "Current log record" (an AEXTENT) while "Recovery Pages: Getpage requests:" value increases greatly over time. See KBA 2340791. |
| 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. |
| 800440 | A new option has been added to sp_add_resource_limit, sp_modify_resource_limit and sp_drop_resource_limit to apply the limit to any user using any application. See KBA 2358540. |
| 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. |
| 800670 | In a Multiple Paths Replication environment configured for the 'filter' distribution model, a DDL command on a table having a bound filter is always sent to the path on which the filter is bound but also, by default, to the default path unless the new Rep Agent configuration parameter 'ignore implicit filter for ddl' is set to 'true'. See KBA 2341608. |
| 800721 | In case of unlogged activity happening while the DUMP command is running on a database, SAP ASE may report the message, "(0 rows affected)". See KBA 2348911. |
| 800733 | Dropping a database on a corrupt device can lead to timeslice errors and result in corruption of the master database. |
| 800813 | sp_helpdefrag can result in arithmetic overflow due to type mismatch. |
| 800822 | Job Scheduler may fail to start during setup with sapinst on AIX platform. |
| 800855 | In rare circumstances, SAP ASE may hit error 515, "Attempt to insert NULL value into column < column_name > , table < table_name > ; column does not allow nulls. Update fails", for a 16K page size dataserver after explicitly adding the identity column in a table which is already populated. |
| 800868 | A 9557 error, "The server failed to create or update a row in table ' < name > ' because a varying-length column would start at offset < value > . This starting location cannot be represented accurately in the table's row format.", may be reported during DML execution if the SAP ASE page size is configured to either 8K or 16K bytes and the database option 'allow wide dol rows' is disabled. |
| 800873 | 2 issues were resolved (1) Error 12052 may occur for table monTableCompression and SAP ASE may hit access violation in the module 'senderror' on Windows platform. (2) SAP ASE may hit access violation in the module 'mda_populate_monSpinlockActivity' on Windows platform. |
| 800932 | The error, "java.lang.SecurityException: Unsupported Thread method", may be reported in the SAP ASE error log with SAP JRE Version 8 or greater, during the execution of a UDF that makes use of a private network stack even when the option -Dsybase.allow.native.lib is enabled. |
| 800942 | The message, "Current process infected with 11" in the module 'js__callout' together with a stack trace which includes the modules 'js__chores' and 'jobscheduler', may be reported in the SAP ASE error log when there are simultaneous Job Scheduler start requests. |
| 800980 | For all Unix platforms, add means of handling a secondary failure in the spid fatal signal handler (i.e. handler for SIGSEGV, SIGBUS etc) and stack overflow checking in signal handler for SAP ASE. 2 new configuration parameters 'sigstack min size' and 'sigstack csmd min size' are introduced in order to configure the minimum amount of stack needed for handling the signal. A task which gets infected with a signal and does not dispose of the required amount of free stack will be transformed into a zombie task. It is advised to contact SAP technical support before modifying these configuration parameters. Minimum stack checking can be disabled via trace flag 2913 and secondary signal handler can be turned off using Trace Flag 2912. |
| 800995 | When the DUMP TRAN command fails, the bits DMPX_TRUNCLOG and DMPX_DUMPLOG remain set in the DBTABLE field dbt_extstat, and the bit DBTX_DUMPLOGFAILED, that should be set, is not. See KBA 2354552. |
| 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 may fail with an infected with 11 error in function sendtext(). See KBA 2467903. |
| 801198 | A 5031 error, "Database test which is currently offline has been altered from size < > logical pages ( < > physical pages) to < > logical pages ( < > physical pages).", may be reported when ALTER DATABASE is executed even though the database is actually online. The error message is harmless and should be ignored. See KBA 2385089. |
| 801219 | A 10386 message, "SELECT BUILTIN permission denied on builtin authmech, owner system security officer", will be reported when a user with SSO role and default database set to a database other than 'master', executes a query involving the built-in authmech(). See KBA 2357201. |
| 801220 | LOAD ... WITH COPYONLY does not work for compressed archive dumps. |
| 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. |
| 801616 | This is visible only to 15.7 SP138 or SP139. This issue was caused by CR717101 which is a new fix in PL05 and also port to ASE 15.7 SP140. |
| 801681 | In virtual host, SAP ASE might experience large number of page faults which could cause a task to timeslice. In this situation for a task which is about to timeslice, allow additional grace time. Also periodically report the page fault counts. |
| 801735 | A 631 error "The length of < value > passed to delete row routine for the row at offset < value > is incorrect on the following page of database ' < DBID > ': < PAGE > . The expected row length is < value > . The offset should be no greater than < value > ." may be reported when there is a redo of a DELETE log record for an APL data compressed table that has a clustered index during a LOAD TRANSACTION. |
| 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. |
| 801865 | A 16382 error, "The configured maximum number of mutexes have already been created" may be reported in the SAP ASE Backup Server error log for some of the dumps prior to their failing, when there are more than 128 simultaneous dumps executed. |
| 801872 | A 1530 error, "Create index with sorted_data was aborted because of row out of order", may be reported instead of error 15451, "You cannot encrypt/decrypt column < column_name > because it belongs to a clustered/placement index on table < table_name > . Drop the index before the ALTER command, and recreate it afterwards.", when the encryption key of an encrypted column, that is part of a clustered index key, is changed while the non-clustered indexes for this table are being rebuilt. |
| 801912 | KBA 2345992. 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. |
| 801978 | A 140 error, "Can only use IF UPDATE within a CREATE TRIGGER", may be reported when the configuration option 'procedure deferred compilation' is enabled and a body of trigger containing the UPDATE built-in function is executed (i.e. triggered). See KBA 2366912 |
| 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. |
| 802115 | A 12726 error, "Suspect Granularity: Dump database of < dbname > failed because some of the data in this database is suspect" may be reported when DUMP DATABASE is executed and the recovery fault isolation mode was set to 'page' mode. |
| 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. |
| 802418 | The message, "java.lang.OutOfMemoryError: GC overhead limit exceeded", together with error 10762, "Cannot initialize the Java Virtual Machine because either the Java class library or PCA plugin library is missing, corrupted, or incompatible with the current server release. Contact your System Administrator for help.", may be reported when executing massive Java related functions in some long term running connections. See KBA 2371346. |
| 802476 | SAP ASE may return a wrong result set if a proxy table is used in a derived table and is involved in an aggregate query. See KBA 2371951. |
| 802649 | KBA 2552219. In rare circumstances, Error 1265 'An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family < lr no, lrmagic no > .' can be raised for SIDB databases if reorg rebuild with online is run. |
| 802687 | KBA2452601 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. |
| 802695 | KBA 2375006 - In rare circumstances, doing multiple shrinks after one another may result error 806(Could not find virtual page for logical page < logical page number > in database < database id > ), which will lead to timeslice issue. |
| 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 | KBA2589035 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(). |
| 802848 | The message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace that includes the modules s_mapcontrol() and s_compile(), may be reported in the SAP ASE error log when procedures involving IF statemens and ORDER BY clauses are executed with "enable metrics capture" and "enable literal autoparam" are turned on. See KBA 2379446. |
| 802855 | The message, "Current process infected with 11", in the module 'FindClassWithLoaderID' together with a stack trace which includes the modules 'pci_tpmworker_thrd' and 'pci_tpminvoker_chores' will be reported in the SAP ASE error log if a Java UDF or ADT is run and a backup server was explicitly shut down in the same session before the Java UDF or ADT execution. |
| 803099 | In rare circumstances concurrent HKGC and create table can lead to a scenario where HKGC marks the buffer as destroy and the same page held by buffer is allocated to create table. The original proposal for this fix needed so be reworked and has not been GA'd. The issue is now being reworked via CR 805498. |
| 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. |
| 803221 | DUMP or LOAD using the compression library 'libcompress.so' may result in relocation errors in Solaris running on machines with AMD processor. See KBA 2307017. |
| 803336 | The system stored procedure sp_help_rep_agent truncates the value of the Rep Agent configuration parameter 'ddl path for unbound objects' to 5 characters. As a consequence, 'defau' is displayed instead of 'default'. |
| 803413 | DBCC ORPHANTABLES may fail to drop orphaned temporary tables if the user is bound to a different tempdb than the one having DBCC ORPHANTABLES being executed. See KBA 2392219. |
| 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. |
| 803545 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_update_stmt_metrics' together with a stack trace which includes the modules 'curs_close' and 'mem_freepages' may be reported in the SAP ASE error log when a CURSOR is closed. See KBA 2533441. |
| 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. |
| 803592 | In rare circumstances, the number of free log pages may sometimes be inaccurately reported when SP_SPACEUSED is run if allocated but stranded log pages exist in the database. |
| 803634 | When replicating compressed LOB columns, Replication Server DSI may fail with ASE error 7153. |
| 803681 | The performance of INSERT statements might be slower while using Dynamic prepare for VARCHAR/TEXT type column. |
| 803716 | SAP ASE did not shutdown after issuing 'shutdown with wait' command as it continued to wait for the Job Scheduler to go down. |
| 803730 | If next_identity() is called against a table in another database and encounters a permissions problem, error 10330 may report the wrong table and database names. |
| 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. |
| 803866 | A 7718 error, "The 'CREATE ENCRYPTION KEY' command is not allowed within a multi-statement" and the 2946 error, "Failed to create service key syb_xpskey", may be reported when executing xp_cmdshell (or any extended stored procedure) within a transaction for the first time. Subsequent executions do not raise the errors. |
| 803870 | A 264 error, "Column name < col_name > appears more than once in the result column list." may be reported when an INSERT command is run on a table that has a trigger on insert, after a reorg rebuild was executed and an alter table drop column with no datacopy has been issued before. KBA 2406065 |
| 803875 | Sybmon sample command showed single frame of stack and reported SymGetSymFromAddr64 error 126 on windows platform. |
| 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%. |
| 803956 | In some rare circumstance, the message, "Current process infected with signal 11 (SIGSEGV)", together with stack trace that includes the modules mda_empty_opstack(), mda__freeze() and mda_config_bi() may be reported in the SAP ASE error log when a process runs sp_sysmon or sp_monitors command. |
| 804071 | The message, "timeslice -1001, current process infected" in the module 'pausenonatomic' followed by a stack trace that includes the module 'getpage_with_validation' and 'bt__getnextscanpg', may be reported in the SAP ASE error log under heavy concurrent activities. |
| 804121 | A 9561 error, "An insert or update to table < tname > places column < cname > at offset < value1 > , ending at offset < value2 > . The maximum permitted ending offset for this column is < value3 > . This is a server internal error." may be reported during an INSERT command execution after a reorg rebuild is run on an APL table which has undergone first an alter table drop column with no datacopy followed by a clustered index creation or drop. |
| 804132 | Execution of sp_dump_history in chained mode is now allowed. |
| 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. |
| 804186 | For queries that are huge, identification of physical operators in the final plan becomes difficult |
| 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. |
| 804346 | The output of str() built-in is truncated to 1024 characters when the SAP ASE configuration option "enable literal autoparam" is enabled. See KBA 2407120. |
| 804347 | KBA 2553567. In rare circumstances, when semantic partitioning is enabled, a stack trace in the function VbmManager::_VbmPutBm() may be observed if select query has join of list partitioned tables with equality predicate. |
| 804356 | When running in process mode, the server may terminate due to segmentation fault, after printing the error message, "uppwakeup: kpid = < -KPID > not within range", in the SAP ASE error log. |
| 804358 | The message "Current process infected with 10 (SIGBUS) or 11 (SIGSEGV)" in the module 'log_setopts' together with a stack trace may be reported in the SAP ASE error log when GRANT or REVOKE command is executed on a database where DDL replication is turned on. |
| 804381 | Multiple messages (1562, 1563 and etc.) are not re-directed to the trace file when tracing is enabled. See KBA 2407736. |
| 804394 | When the master database is setup for replication, Replication Agent may fail with errors 9254 and 9204 after dropping an object specific to replication such as the procedure 'rs_marker'. |
| 804408 | KBA 2452537 In rare circumstances, commands like DBCC REINDEX, DBCC DBREPAIR may acquire granular level (row/page) locks while they hold table level exclusive lock. |
| 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 . |
| 804444 | Performance degradation may be observed in SAP ASE when executing a query with multiple predicates of which one is an IN list, because SAP ASE is not choosing an efficient index. |
| 804522 | A query that compares a CHAR with the result of DATEADD() returns different results when statement cache is active. See KBA 2409707. |
| 804573 | A 2760 error, "Column name ' < some corrupted column name > ' does not exist in target table." may be reported when creating index on a deferred table with the online parameter on ibmaix64 and sunsparc64 platforms. |
| 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. |
| 804744 | A Page Verification Error notifying "fixed-row status improperly set" may be reported for DOL pages containing forwarded rows when DUMP/LOAD DATABASE is executed with VERIFY=FULL. See KBA 2414787. |
| 804839 | The message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the modules lock_draincache() and lock_release(), may be reported in the SAP ASE error log when termination of spids are done concurrently with lock-intensive INSERTs leading to freelock list corruption. See KBA 2414647. |
| 804856 | In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of < wrong_length > . Maximum allowed length is < max_length > ", may be reported in the SAP ASE error log when page compression is used. See KBA 2595171. |
| 804886 | The message, "D00: Page Verification Error: Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; check this page (page#= < pagenum > row#=0 offset in row number table=0)", may be incorrectly reported in the Backup Server error log when executing DUMP DATABASE WITH VERIFY for a syslogs page. See KBA 2427308. |
| 805018 | sp_configure raises the 5861 error, "The current 'max memory' value < max_memory_value > , is not sufficient to change the parameter 'number of user connections' to '32728'. 'max memory' should be greater than 'total logical memory' < wrong_memory_value > required for the configuration.", with an invalid value for total logical memory when configuring for 32729 or more user connections. See KBA 2417198. |
| 805162 | KBA 2413420. 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. |
| 805165 | Using numeric datatypes in a parameterized SQL with values that are similar such as 1.11 and 11.11 may lead to spinlock contention on the statement cache. Note that due to some problems that this CR introduced, in some releases, this CR has been disabled by default by CR 812309. |
| 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). |
| 805275 | SAP ASE server will disable ASE_JAVA functionality if jvm.wl is missing, and the message 10762 together with the detailed reason will be reported in SAP ASE error log. This is to improve the default security should the jvm.wl authorization file be accidentally removed. |
| 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. See KBA 2435989 |
| 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. |
| 805463 | Device usage information will not be reported by sp_helpdb mistakenly when the provided database name is using square brackets to escape wildcard characters such as underscores. See KBA 2426257. |
| 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(). |
| 805527 | The monDataCache MDA table might report incorrect values in PhysicalReads, APFReads and PhysicalWrites columns that are much less than the corresponding values from the monCachePool MDA table for a data cache with multiple partitions. |
| 805601 | The message, "PCI(T1): WARNING: FindPublicMethodFlags; is re-throwing Exception", may be reported in the SAP ASE error log when executing massive Java related functions through JDBC for several hours. See KBA 2425822. |
| 805624 | ALTER DATABASE fails silently when passed an expansion size that is smaller than the minimum for the server's page size. See KBA 2429256. |
| 805713 | sp_object_stats raises error 208 about being unable to find table syslkstats in a multiple tempdb when the user executing it is bound to a tempdb other than the system tempdb (dbid 2). |
| 805802 | SAP XP Server may generate core file when connection establishment between SAP ASE and SAP XP Server fails. |
| 805984 | SAP ASE unexpectedly raises error 17260, "Can't run < sproc name > from within a transaction.", if sp_monitorconfig is run in chained mode. |
| 805990 | In rare circumstances on heavily loaded SAP ASE systems, CREATE TABLE into an in-memory database may hang with a stack trace which includes the modules 'getpage__noscan', 'getpage_with_validation' and 'bufsearch_cache_getlatch'. See KBA 2266313. |
| 806009 | A 1511 error, "Sort cannot be reconciled with transaction log" and a 4313 error "Recreate index failed for table < table_id > , index < index_id > . The table has been left in an inconsistent state, and the index is missing, so LOAD TRANSACTION errors may result.", may be reported when running REORG REBUILD on an allpage-locked table with a clustered index that allows duplicate rows. |
| 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 |
| 806181 | Error 169 regarding duplicate ORDER BY clauses may be raised incorrectly when clauses are actually unique on servers configured for the UTF8 character set. See KBA 2439551. |
| 806446 | sp_configure 'number of early send rows', < value > and sp_configure 'early row send increment', < value > returns permission related error 10350 when granular permissions is enabled. |
| 806500 | Sub-optimal performance may result when multi-database queries are executed and the "auditing" configuration option is enabled. A contention on spinlock 'rdbt_spinlock' will be seen in the modules 'dbt_keep', 'dbt_unkeep' or 'dbt_rekeep' when called by module 'usedb' while SAP ASE attempts to open the user tables of a query. |
| 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. |
| 806680 | Online utility processing, a parallel plan is generated and buffer is kept in this scenario dereferencing session descriptor may lead to SIGSEGV. |
| 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. |
| 806700 | In rare circumstances, sp_monitorconfig may return '0' value for the 'Max_Used' column for configuration parameters which internally uses memory from object pool. See KBA 2515680. |
| 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 | KBA2388707 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 |
| 807015 | Uniqueness bit for unique index in rootkey info may be lost after online REORG REBUILD or online partition level utilities such as split/move partition using ALTER TABLE. |
| 807092 | KBA 2455587 The Bucket Pool entries in the configuration file disappear after modifying a configuration parameter with sp_configure. |
| 807128 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'altdb__report_shrinklog_info' together with a stack trace which includes the modules 'altdb__do_shrinkdb' and 'altdb_shrink' may be reported in the SAP ASE error log when shrink database and shrink log command are run concurrently. |
| 807134 | An Arithmetic Overflow error can be seen when using "sp_dbextend 'device', devicename, 'growby', 'maxsize' " with invalid values for 'growby' and 'maxsize'. |
| 807245 | Missing parent information of some functions/labels in stack output. |
| 807324 | When a spid executing sp_dump_history gets abnormally terminated e.g. due to a timeslice error, then it does not release the resource (semaphore) thus disallowing other spids to execute SP_DUMP_HISTORY. Only way to cleanup then is to recycle the SAP ASE. |
| 807383 | On Unix platforms, in the Job Scheduler Agent (jsagent) process, when multiple threads hits a fatal signal like SIGSEGV simultaneously, then the core file is not generated. |
| 807433 | In some circumstances, the value of monNetworkIO.BytesSent might not increase on IBM AIX platform even though there are some network I/O activities. |
| 807451 | If a database with AT_SHUTDOWN durability has active transactions that, for some reason, cannot be terminated when the server is shutdown politely with a maximum wait time using the clause WITH WAIT="xx:xx:xx", the message "The database < > with durability 'AT_SHUTDOWN' could not be shut down properly and will not be recovered when Adaptive Server is re-started." should be printed in the errorlog, but it was not. |
| 807471 | A 12546 error, "During undo the timestamp to be assigned to a page is less than the current page timestamp." followed by a 3478 error, "During undo the page timestamp value is less than new timestamp from log." may be reported in the SAP ASE error log during the recovery of a database when alter database un-partition was executed before SAP ASE is shutdown. |
| 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 > " |
| 807724 | sp_showcontrolinfo shows incorrect value in scope column for a "AP" binding. This only happened when the previous row is a "LG" binding and current "AP" row has the scope with NULL value. See KBA 2465543. |
| 807766 | When encrypted column is enabled for a table which has default value for some columns, then in sp_help 'tablename' output,'Encrypted' property for these columns show 'NULL' value instead of 0, if the data in these columns are not encrypted. |
| 807819 | When the master device is upgraded from a pre-15.0.2 version of SAP ASE, the execution of sp_passwordpolicy 'list', 'allow password downgrade' should report the message 'Password downgrade is allowed' instead of 'New master database'. |
| 807823 | Empty PLC (Private Log Cache) blocks with only a BEGIN TRANSACTION log record present are flushed to syslogs during DUMP DATABASE when the database option 'allow incremental dumps' is enabled, or the database was created with the 'INMEMORY' option. This will prevent the transaction log truncation from taking place when a transaction is still open. |
| 807849 | SAP ASE may incur a segmentation fault in ksnetctlrAddSockEvent() when new client connections are made during shutdown with nowait. |
| 807870 | The message, "Current process infected with signal 11 (SIGSEGV)" coming from the module 'oh_findendoffset_inobuf' together with a stack trace in the SAP ASE errorlog that includes the modules 'rvm__get_obfuscated_currstmt' and 'rvm__audit_getcommand_subcommand', may be reported in the SAP ASE error log when executing sp_addlogin and ALTER LOGIN in a batch with auditing enabled. See KBA 2469521. |
| 807940 | A signal 11 error may be raised when using the "Stack" command in Sybmon during unwinding of the stack trace on some platforms like ibmaix64 platform. |
| 807966 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'mda_populate_monSpinlockActivity' together with a stacktrace which includes the modules 'mda_exec' and 'VTABRemoteAccess::startScan' may be reported in the SAP ASE error log when a SELECT from monSpinlockActivity is run. See KBA 2545393. |
| 807992 | The message, "Timeslice -1501, current process infected" in the module 'rl_log_writev' together with a stack trace may be reported in the SAP ASE error log if a workload capture started after server reboot. |
| 808012 | The execution of LOAD WITH LISTONLY=CREATE_SQL on an in-memory database generates a cache creation of half the size of the original size value mistakenly. |
| 808035 | sp_monitorconfig reports inaccurate usage values for 'additional network memory' when the 'Network Buffers' Bucketpool is enabled. See KBA 2471654. |
| 808076 | When Replication Agent is restarted after the execution and replication of a 'DUMP DATABASE' command, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < dbname > ' because the target page is not a data page. Rid pageid = 0x0; row num = 0x0." may be reported in the SAP ASE error log. See KBA 2469439. |
| 808080 | When the configuration parameters 'number of network tasks' and 'number of disk tasks' are changed their new value is not written to the SAP ASE configuration file. See KBA 2472350. |
| 808205 | Executing a preupgrade from an SAP ASE 12.* server to any SAP ASE version above 15.0 may result in a 207 error, "Invalid column name < column_name > ", for columns 'partitiontype' and 'conditionid' that do not exist in the SAP ASE 12.* version. |
| 808353 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'ksmask_rpacket' followed by a stack trace that includes the modules 'kstcpnetctlrProcessRead' and 'iocPoll', may be reported in the SAP ASE error log. Thereafter, the SAP ASE may become unresponsive. See KBA 2336205. |
| 808357 | LogicalReads/PhysicalReads in the monProcessActivity, monSysStatement and monProcessStatement MDA tables will not be updated correctly when "enable compatibility mode" is set as 1. See KBA 2478206. |
| 808425 | KBA 2580447. The error, "Sybmon encountered signal 11 at address < addr > ", will be raised when "hanginfo" is executed in sybmon that is attaching to an SAP ASE server. The functions sm_os_ctrl_suspend_thread and khashtable appear in the stack. Some structure fields might also be missing from sybmon "ptype" command output. |
| 808489 | A segmentation violation followed by a stack trace that includes the module 'am_count_bits_in_dmap' may be reported in the SAP ASE error log when loading a database dump on a database that is marked as suspect if the database is bigger than 64G in a 2K server, 128G in a 4K server, 256G in a 8K server and 512G in a 16K server. See KBA 2490688. |
| 808553 | RC4 and 3DES are removed from the SSL default cipher suites list. |
| 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. |
| 808634 | sp_sjobcontrol stored procedure may fail with error 553 when called to enable/disable caller's scheduled jobs, using the syntax "exec sp_sjobcontrol @name='jname= < jobname > ', @option='enable|disable'". |
| 808637 | KBA 2460661. Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'js__sequencer_load' together with a stack trace that includes the module 'js__sequencer_boot', may be reported when installjsdb is modified to include spaces instead of tab and the Job Scheduler fails to start. |
| 808666 | The monDeviceSpaceUsage table might return incorrect data when it is queried concurrently from multiple sessions. In rare cases, the Global Fragment Pool might be corrupted. Customer may see signal 11 error in kbfalloc() or kbffree(). |
| 808729 | SAP ASE does not handle numeric conversion results consistently during RPC calls when arithabort is OFF. |
| 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. |
| 808883 | KBA2547172 A 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database..." may be reported when there is a long running transaction that causes DUMP TRANSACTION to not truncate any log pages and DUMP TRANSACTION is run a high number of times. |
| 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. |
| 808936 | The message, "Incorrect column type in the offset table of row < > . This row is on page < > , partition ID < > , and belongs to object 'syscomments' (ID 6) in database ' < > ' (ID < > )." may be mistakenly reported when running DBCC CHECKTABLE(syscomments). |
| 808961 | A 952 error, "Database < dbname > cannot be opened because the system index descriptor for table ID 4 cannot be installed.", may be reported when booting a server with 4K page size downgraded from 16.0 SP03. |
| 809026 | When SQL Statement Replication is enabled the DSI connection may go down with error 5150, "Function 'rs_get_textptr' for table ' < table_name > ' returned multiple rows." while a SELECT INTO statement that involves LOB columns is replicated. |
| 809038 | The error, "The dbinfo anchor in the database 'database ' < dbname > '' is already locked by the task. Nested access to dbinfo anchor is not allowed.", followed by a stack trace that includes the module 'checkpoint' may be reported in the SAP ASE error log if the checkpoint task runs out of locks. |
| 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. |
| 809098 | Cleanup is failing during abort transaction due to no space in log. |
| 809100 | When SP_SHOWOPTSTATS is run on tables that have large number of step counts in statistics, other sessions may observe performance degradation when accessing same set of tables. See KBA 2492238. |
| 809121 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeScrollCache::LeScrCacheGetRow' followed by a stack trace that includes the modules 'LeLOBCache::copyOutParam' and 'getvalue', may be reported in the SAP ASE error log when inserting a TEXT value from a local variable after performing a substring operation. See KBA 2492093. |
| 809179 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dbt_unkeep' together with a stack trace which includes the module 'close_range' may be reported in the SAP ASE error log when a query uses a worktable. See KBA 2545441. |
| 809244 | After the fix of CR 777172, cache size is stored in terms of 2K. Views have been changed accordingly to reflect this behavior. Cache sizes up to 2TB will show actual size in the views. |
| 809265 | After running "alter database < database_name > on/off < database_device > size = '0M'", command fails with error Msg 5015 - "CREATE or ALTER DATABASE failed. The size specified must be < n > megabyte(s) or greater". |
| 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 when SP_MONITORCONFIG with the 'all' option is executed and the set option string_rtruncation is enabled. |
| 809381 | In rare circumstances when REORG REBUILD is terminated using Ctrl-C, sp_help on the table undergoing REORG REBUILD returns error 17461, incorrectly indicating that object does not exist in the database. |
| 809395 | In rare circumstances, the message, "Current process infected with 11" in the module 's_execclearvar' together with a stack trace which includes the module 'tdsrecv__process_batchparam' may be reported in the SAP ASE error log during the execution of a DML on a table that has a DECIMAL column with high precision defined such as DECIMAL(38,1). See KBA 2412709. |
| 809442 | In rare circumstances, a session may hang in the module 'prepprev' after a rollback due to error 2601 "Attempt to insert duplicate key row in object ' < table_name > ' with unique index ' < index_name > ' ...". See KBA 2503863. |
| 809498 | A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ) and not to database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ) or a 692 error, "Uninitialized logical page < page_num > was read while accessing database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ). Please contact SAP Technical Support." may be reported when a user is inserting a data from a source table to target table using SELECT INTO command while another user is fetching data from target table at isolation level READ UNCOMMITTED. |
| 809638 | Sometimes, an SAP ASE spid hangs in the module 'prepprev' after rollback due to error 2601 (duplicate key error). |
| 809748 | The message, "SSL or Crypto Error Message: 'The SSL handshake failed. Root error: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol'", may be reported in the SAP ASE error log when an SSL connection reuses a socket that was previously used by a terminated site handler. See KBA 2533391 |
| 809773 | Occasionally, a 712 message, "There is insufficient heap memory to allocate < nn > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system", may be raised for insufficient heap memory when multiple XML sessions (such as more than 15) run XML queries at the same time. See KBA 2515782. |
| 809799 | A 515 error, "Attempt to insert NULL value into column < column_name > , table < table_name > ; column does not allow nulls. Update fails.", may be reported when executing sp_cacheconfig after an IMDB cache which is bound to a device or database is deleted. |
| 809940 | SAP ASE does not report an error about missing an external login during scheduled job creation using sp_sjobcreate with jproperties=run_as_owner. |
| 810076 | Implement Microsoft Authenticode SHA256 signing for SAP ASE binaries on Microsoft Windows. |
| 810114 | Predefined entities less-than sign ' < ' and greater-than sign ' > ' in SOAP body elements are converted into ' < ' and ' > ' when a document/literal style web method is invoked by webservices. |
| 810126 | Files created with the compression library when DUMP DATABASE < dbname > to 'compress:: < pathname > ' is executed will get the standard umask defined by the end-user who has started the backup server instead of 640 (rw-r-----). See KBA 2514450. |
| 810132 | The 814 error, "Keep count of buffer ' < buffer addr > ' in cache ' < cache name > ' holding logical page ' < pageno > ' in database ' < database name' has become negative" followed by a stack trace that includes the module 'dam__destroy' may be displayed when creating a database, if the option 'allow incremental dumps' is enabled in the model database. |
| 810202 | In rare circumstances, a 803 error, "Unable to place buffer < buffer_address > from cache < cache_name > holding logical page < page_number > in sdes for object < object_name > - either there is no room in sdes or buffer already in requested slot", following a 7901 error, "Page < page_number > , partition ID < partition_id > , is expected to be the first page of a text/image/unitext value", may be reported when DBCC REBUILD_TEXT is executed. |
| 810222 | Executing sp_help ' < proxy_table_name > ' may report an incorrect fully qualified name for the remote object name when there are more than one proxy table defined with the same name but with different owners. See KBA 2602353. |
| 810276 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module '__milli_memcpy', followed by a stack trace that includes the modules 'tdsrecv_params', 'tdsrecv__process_batchparam' and 'tdsrecv__dynexec_batch', may be reported in the SAP ASE error log when a JAVA application executes an INSERT with a TINYINT datatype. See KBA 2554290. |
| 810376 | Error 9557 may result when the "disallow simple passwords" feature is on and passwords generated by the password_random() function happen to include the name of the login the password is assigned to. An additional optional parameter is added to password_random() so it can be passed the login name to avoid including in the resulting password string. See KBA 2525248. |
| 810405 | With replication on, error message 632, "Attempt to move memory with an incorrect length of < wrong_val > . Maximum allowed length is 16384.", may be raised while trying to decrypt any encrypted column of table when set encryption password was set for that column and not for encryption key with which column is encrypted. |
| 810488 | The message, "Command has been aborted", may be reported when closing or deallocating an insensitive cursor. See KBA 2528002. |
| 810656 | A new traceflag 11011 is added to disable the behavior where multiple INSERT statements with similar numeric input values caches a single query plan instead of creating a new plan for each statement. This behavior was introduced to avoid spinlock contention in statement cache due to large number of plans being cached for INSERT statements with similar parameters. |
| 810743 | SAP ASE running on Windows will see a timeslice error if a task hits a divide by zero error |
| 810757 | A predicate with multiple columns, such as ((c1,c2) > (x,y)), can be incorrectly qualified as a criteria for partition elimination. This may lead to incorrect results. See KBA 2345886. |
| 810799 | In rare circumstances when DDL replication is enabled, some DDL commands may not be replicated from the primary SAP ASE when the default data cache is under configured and lots of concurrent replication activity is taking place. |
| 810937 | Some wait events may be aggregated/rolled up incorrectly. |
| 810952 | On HP and IBM systems, the message, "Stack overflow detected" in the module 'upunsetcritical' together with a stacktrace which includes the modules 'kcvDeleteCondVar' and 'ubf_is_addr_inpool', may be reported in the SAP ASE error log during a graceful shutdown of the server while the diagserver binary is in use. |
| 810985 | When a table that has a UNITEXT column is marked for replication sometimes the data may not be replicated correctly. |
| 810995 | SAP ASE running on Microsoft Windows on a virtual machine can hang when encountering a resource issue on the VM. See KBA 2542797. |
| 811089 | A 207, 233, 264, 2760, or 12810 error indicating that an invalid column name is referenced in a query, may be incorrectly reported by SAP ASE under heavy concurrent activity during query execution. Additionally a new SAP ASE trace flag 16889 is introduced which allows to enable an alternate behavior that resolves these errors. However the use of this trace flag may expose a situation, as mentioned in CR 801618, whereby a 8211 error, "A newly created ssql_id for SQL to store in statement cache is a duplicate object id of an existing table in system tempdb." may be reported or a segmentation violation in module 's_compile_stmt' may also be seen. See KBA 2543028. |
| 811135 | After an upgrade, a 10330 error, "INSERT permission denied on object < obj_name > , database < db_name > , owner < username > ", may be reported when procedures are executed by a user without explicit permissions on the underlying objects ( only partitioned tables) in the procedures. See KBA 2560832. |
| 811173 | Once a spid is stuck in kctCheckAsync() loop, any changes made to 'async poll timeout' configuration parameter is not effective for that spid. |
| 811206 | Under some circumstances, the DSI thread may shut down with a 3959 error, "New transaction cannot be started as Adaptive Server is in 'Inactive' HADR state. The command could not be completed", reported in the standby SAP ASE when replicating a CREATE MATERIALIZED VIEW statement in a HADR setup. |
| 811480 | A 'Blocking call exception' on SAP ASE can crash the server if another exception occurs in the handler itself. |
| 811521 | A 691 error, "Encountered invalid logical page '0' while accessing database ' < database_name > ', object 'syslogs' (8), index 'syslogs' (0), ...", may be reported in the SAP ASE error log when DUMP TRANSACTION < database_name > WITH NO_LOG is run when the database is enabled for replication and the last change threshold for this database was crossed. |
| 811606 | A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, involving updates to rows containing In-row LOB columns. |
| 811615 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log ...", may be reported during LOAD TRAN when DBCC TUNE with one of the options "ascinserts", "indextrips" or "oamtrips" was run for a table stored in a different database than the source database were the dump was taken. See KBA 2556287. |
| 811697 | A 206 error, "Operand type clash: FLOAT is incompatible with MAINTENANCE TOKEN" or a 529 error, "Explicit conversion from datatype 'FLOAT' to 'UNITEXT' is not allowed.", may be reported when inserting FLOAT data with the statement cache enabled. See KBA 2558456. |
| 811701 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 's_handle' together with a stack trace which includes the modules 's_recompile' and 'execproc', may be reported in the SAP ASE error log when creating a Light Weight Procedure (LWP) after a 2812 error, "Stored procedure ' < name > ' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", is reported. See KBA 2471704. |
| 811811 | A 594 error, "The UPDATE WHERE CURRENT OF to the cursor ' < name > ' failed because column ' < name > ' being updated was not specified in the SELECT list.", may be reported when an cursor update statement that references a temporary table is executed and the configuration option "optimize temp table resolution" is enabled. See KBA 2562119. |
| 811825 | Wrong results may be returned from a query that has complex OR clauses. See KBA 2563459 and SAP Note 2596598. |
| 811842 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'psort__dolscanpage' together with a stack trace that includes the modules 'psort__dolscanptn' and 'psort__dolscan', may be reported in the SAP ASE error log when REORG REBUILD with online option is executed on a round-robin partitioned DOL table with a global placement index. |
| 811850 | A 11060 error, "This statement has exceeded the maximum number of recompilations (10). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported when executing nested views and procedures. See KBA 2462416. |
| 811935 | DBCC page() command is enhanced to print character encoding information. |
| 811965 | A 9209 error, "RepAgent( < dbid > ): Missing datarow in TEXT/IMAGE/UNITEXT insert log record. Transaction log may be corrupt. Please contact SYBASE Technical Support. (current marker = ( < page# > , < rowid > ))." may be reported in the SAP ASE error log when LOB data is replicated. See KBA 2567397. |
| 812006 | Under rare circumstances, SSL connections to an SAP ASE running in process kernel mode may hang during network I/O. |
| 812086 | In rare circumstances, a 3404 error, "Could not open controlling database < value > of controlling database in multi-db transaction.", may be reported when MOUNT DATABASE is executed on a database that is in load sequence and a multi-database transaction was involved earlier. See KBA 2656744. |
| 812120 | Under some circumstances, a 16805 error, "A LOB LOCATOR was used that is no longer valid: Either the transaction that created it has ended or it has been deallocated", may be reported when using LOB Locators to access the LOB Cache. |
| 812142 | DBCC PAGE command has been enhanced to print decompressed data. |
| 812156 | For Java applications, if there is a stored procedure with output parameters, and if the output parameters come before input parameters, there is a possibility of incorrect values being stored for integers. See KBA 2571900 |
| 812172 | Adaptive Server Enterprise incorrectly sets @@error with 'Resource Governor message 11056 for "tempdb space" limit, despite the action is set to "warn only". This is documented in KBA 2573341. |
| 812173 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_fill_and_send_monProcessWaits' together with a stack trace which includes the modules 'conn_hdlr' and 'kisignal' may be reported in the SAP ASE error log when the monProcessWaits MDA table is queried. |
| 812204 | A 5702 error, "ASE is terminating this process" together with an access violation exception stack trace which includes the modules 'KiUserExceptionDispatcher' and 'RtlDecodePointer' may be reported in the SAP ASE error log when running installjava utility on Windows platform. |
| 812227 | For SAP ASE running on Linux, Solaris & HP, under rare circumstances an SSL connection may unexpectedly terminate with message "SSL or Crypto Error Info: psn -1, vsn -1, sockp (nil) error id 12, severity -2, provider id 2." in the SAP ASE error log. |
| 812309 | A 3624 error, "Truncation error occurred", may be reported when executing INSERT involving NUMERIC datatypes and the statement cache is enabled. This is due to CR 805165 which addressed a spinlock contention performance scenario on the statement cache. The fix introduced by CR 805165 is now disabled by default. CR 805165 can be enabled using the run time trace flag 11013. |
| 812354 | The execution of a DUMP or LOAD command will hang in the module 'login_response' when it is run from the threshold action procedure and the option 'net password encryption' is enabled in the SYB_BACKUP backup server. |
| 812392 | In rare circumstances, the message, "Current process infected with signal 6" in the module 'gsignal' together with a stack trace which includes the modules 'dcl_find_interface' and 'dcl_property' may be reported in the SAP ASE error log when the SAP ASE server is gracefully shut down and a site handler is configured. |
| 812393 | An erroneous message, "Assertion (upd_ok) failed" in the module 'altdb__check_fwd_rows', may be reported in the SAP ASE error log if DBCC DBREPAIR with 'redo_shrink' option is executed to repair a partially completed shrink database and the diagserver binary is in use. It is a false assertion message from the diagserver, data is NOT corrupted. NO symptoms are reported in dataserver. |
| 812411 | Correct a couple of typos in the exception messages for "an unforeseen exception" and "an array bounds exceeded". |
| 812460 | SAP ASE using external security services such as Kerberos can suffer from unbalanced engine load with an excess of runnable tasks waiting for engine 0. |
| 812633 | A 102 error, "Incorrect syntax near 'passwd'" may be reported when DUMP TRANSACTION or LOAD TRANSACTION is executed with the PASSWD option. |
| 812828 | The message, "%s permission denied on object %S_OBJID, database %S_DBID, owner %.*s", might be reported in client console when doing INSERT operation on a user table created for store logs, after the server has been upgraded from 15.7 SP134 or later version to 15.7 later versions. |
| 812840 | A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, when compression is enabled. |
| 812978 | syslogshold may occasionally show a row with a transaction start date of 1 Jan 1900. See KBA 2587185. |
| 813005 | In rare circumstances on an HADR setup, a 156 error, "Incorrect syntax near the keyword ' < value > '", may be reported in the standby SAP ASE error log during the replication of CREATE VIEW, resulting in the DSI replication stream to implicitly stop. |
| 813075 | In rare circumstance, 2601 error, "Attempt to insert duplicate key row in object < table name > with unique index < index name > ", may be reported on the standby SAP ASE server, when running an UPDATE command on a compressed APL table that has a primary key constraint on the primary SAP ASE server. |
| 813110 | A table with compressed LOB columns uses more space when populating the table via VIEWs. See KBA 2594175. |
| 813114 | Sybmon "status" and "engines" commands report the wrong engine status as "Not Halted" for memory dump generated by either "DBCC MEMDUMP" command or manual command "memdump" with engine halt option. See KBA 2596784. |
| 813118 | The message, "ubo_object_from_slot: Pss Invalid slot id 0", along with the message, "Current process infected with 11 (SIGSEGV)" in the module 'lock__print_deadlockchain' together with a stack trace which includes the modules 'lock__perform_deadlock_search' and 'lock_firstpage' may be reported in the SAP ASE error log when the configuration options "print deadlock information" and "deadlock pipe active" are enabled, while SAP ASE is processing a deadlock scenario between user tasks during the execution of a query. See KBA 2599942. |
| 813238 | The message, "Attempt to push affinity to a non-existent engine", may be reported in the SAP ASE errorlog when performing a DISK UNMIRROR command to set the secondary mirror as the primary device while running in process mode. See KBA 2597350. |
| 813248 | Executing sp_displaylogin with a wildcard may show different information of "Password expiration interval", "Minimum password length" and "Maximum failed logins" from information displayed individually after you change the attributes of one of the login accounts. See KBA 2598951. |
| 813283 | SAP ASE workload capture may record incomplete pcap file names in the SAP ASE error log especially when the server is configured with multiple engines. |
| 813292 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'OmniQuickPass::locateSubquery' followed by a stack trace that includes the modules 'OmniQuickPass::locateOjRange' and 'OmniQuickPass::handleOJBlock', may be reported in the SAP ASE error log when a query that involves ANSI OUTER JOIN and subqueries is executed against a proxy table. See KBA 2600457. |
| 813303 | In an HADR environment, when a Primary SAP ASE is rebooted, it may switch to Standby mode with error 208, "sysservers not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", followed by error 11221, "No external login for suserid 0, server name ' < value > '", reported in the SAP ASE error log. |
| 813359 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'OmniQuickPass::expandRangetableName' together with a stack trace that includes the module 'generateTransSQL', may be reported in the SAP ASE error log when the set option 'show_transformed_sql' is enabled. See KBA 2600457. |
| 813473 | In rare circumstances on a heavily-loaded multi-engine Solaris x64 system, SAP Adaptive Server may hang in the module 'xls_flush_plcqueue' when the configuration option "user log cache queue size" is enabled while the Private Log Cache of a user task is being flushed in the transaction log. |
| 813849 | The SAP ASE backup server process in AIX, SOLARIS and HP-UX platforms may leak some memory when dumping and loading databases, which causes it to grow until it exceeds the O/S memory limit. The backup server may then hang or crash with a core dump with the message, "Backup Server: 1.1.2.8: Memory allocation failed in bs_mkvdisktab for a sd_vector allocation. This DUMP or LOAD session must exit.", reported in the error log. See KBA 2605477. |
| 813886 | Under rare circumstances, a connection may hang after receiving a cancel request from the client. See KBA 2633664. |
| 814198 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mem_pageallocate', may be reported in the SAP ASE error log when a query is executed and the engine local cache memory is corrupted. See KBA 2636316. |
| 814206 | On platforms other than Linux, when the compatibility mode is enabled, a 5846 error, "Illegal value '0' specified for configuration option ' < config name > '. The legal values are between ' < lower limit > ' and ' < upper limit > '", may be reported even when a correct value is provided. |
| 814332 | The message, "Current process infected with signal 11", followed by a stack trace that includes the module 'mda_calc_proc_hdr_mem_KB' and 'mda_populate_monCachedProcedures' may be reported in the SAP ASE error log while querying the monCachedProcedures MDA table. |
| 814613 | The message, "rapidlog unable to open file ..." and "timeslice -1501, current process infected" followed by a stack trace that includes the module 'worcap_packet', may be reported in the SAP ASE error log when capturing a workload. |
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
CR, CR List, ASE 15.7 SP140, ASE SP140, Adaptive Server Enterprise, Fix, Patch, Error, Bug, SP140 , 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)