/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in Adaptive Server Enterprise (ASE) 16.0 SP04 PL05. Please be sure to read the Disclaimer below.
If the EBF/SP has been released, check the CR list and coverletter at the support.sap.com.
Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.
| CR Number | Description |
|---|---|
| 548251 | A 3151 error, "Adaptive Server cannot load this database because the database that was dumped was not quiescent when the dump was performed. Run sp_flushstats before DUMP DATABASE and ensure that the database is not updated during the dump.", may be reported by SAP ASE when loading a cross-platform full database dump after a large amount of processing has taken place instead of the error raised earlier. See KBA 3291701. |
| 697345 | DBCC CHECKDB is enhanced to show periodic percentage progress status during its execution with messages like "23 table(s) of 56 processed. 50% completed.". See KBA 2449176. |
| 768857 | A 11035 error, "Execution of trigger < trigger-name > failed because upgrade found no entry in syscomments for this object. Please drop and recreate < trigger-name > .", may be reported by SAP ASE when trying to execute objects whose row is manually deleted from syscomments following a cross-platform migration. This is expected, but a warning message that the objects will need to be rebuilt should be issued during the migration process. See KBA 2052455. |
| 814225 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeHashTable::Prob' together with a stack trace may be reported in the SAP ASE error log when a SELECT query using MINUS or EXCEPT operators is executed and the 'hash_union_distinct' operator is enabled. See KBA 2623674. |
| 816494 | In rare circumstances, SAP ASE may return an incorrect result set when a SELECT query on a hash partitioned table that includes a point predicate WHERE clause for a ‘binary’ or ‘varbinary’ partitioning key column is executed. |
| 819875 | sp_showoptstats execution may generate incorrect xml output when histogram values contain multibyte characters. See KBA 2827889. |
| 821057 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'LeAlignedDataRow::readRow' may be reported in the SAP ASE error log when an insensitive scroll cursor using built-in functions in the cursor definition is opened. See KBA 2890758. |
| 821435 | A 12212 error, "Internal Error: The partition ID ( < partition-id-1 > ) of the lock does not match the partition ID ( < partition-id-2 > ) of the new request on this lock. dbid= < database-id > , objid= < object-id > , pageno= < page-number > , rowno= < row-number > locktype= < lock-type > ", together with a stack trace which includes the modules 'lock_do_logical', 'dol__ncinsert' and 'LeBulkOpOpen' may be reported in the SAP ASE error log when data rows are inserted in a partitioned table concurrently. See KBA 2985160. |
| 822335 | The frequency of error 9409, "Current transaction ID ( < value > , < value > ) in database < database-name > (dbid = < database-id > ): commit wait < reason > .", reported in the SAP ASE error log has been diminished. See KBA 3289685. |
| 822406 | When QUIESCE and PREPARE commands are executed with either 'hold' or 'release' options SAP Adaptive Server will report informational messages to the client also as opposed to the error log only. See KBA 3338972 |
| 822540 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'sqt_find_desc_pss' together with a stack trace which includes the module 'tdsrecv_dynamic' may be reported in the SAP ASE error log when a dynamic statement is executed. This error may be followed by the message, "FATAL UNHANDLED EXCEPTION: signal 0 hit while handling a previously hit signal. The server cannot continue and will shut down.". See KBA 2959193. |
| 822613 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'xact_check_active' together with a stack trace which includes the modules 'hadr__deactivate_begin' and 'hadr__deactivate' may be reported in the SAP ASE error log when executing sap_failover. See KBA 2962061. |
| 823117 | SAP ASE is enhanced to better identify the high water mark for "number of locks" used when the system stored procedure sp_monitorconfig is executed. |
| 823218 | A time slice error or a system exception (0xc0000094) may be reported in the SAP ASE error log together with a stack trace which includes the modules 'stu_sortrange_to_hist', 'stu_nosort_merge_hist' and 'update_statistics_col_hash' when UPDATE STATISTICS WITH HASHING is executed. See KBA 2147566. |
| 823360 | In rare circumstances, after loading a cumulative dump an invalid row may be seen in master..sysusages for the target database with segmap and location column values set to zero and a positive vdevno column value respectively. See KBA 3238664. |
| 823787 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'CgHashPart::CgGenLePartitions' together with a stack trace which includes the modules 'CgpAppendUnionAll' and 's_compile_stmt' may be reported in the SAP ASE error log when a select union query is executed. See KBA 3273610. |
| 823824 | SAP Adaptive Server is enhanced to better handle data type conversion from LOB to varchar while a query is being re-normalized. |
| 824320 | The value from column 'sval' for a role audit option in sybsecurity..sysauditoptions does not match the correct value reported in sp_displayaudit system stored procedure. See KBA 3312260. |
| 825172 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'uwpredisconnect' together with a stack trace which includes the modules ‘err_disconnect_allchildren’ and 'err_pll_secondary_processing' may be reported in the SAP ASE error log when a parallel select query encounters an error during its execution. See KBA 3075572. |
| 825173 | A 832 error, "Unable to place buffer < hexadecimal-address > holding logical page < page-number > in sdes for object 'temp worktable' - there is no room in sdes aux keep pool.", in the module 'bufkeep_sdes' together with a stack trace which includes the modules 'sort_bufreserve' and 'LeHashContext::ProcessTuple' may be reported in the SAP ASE error log when a SELECT query using either INTERSECT, MINUS, or EXCEPT operators is executed. See KBA 3090000. |
| 825361 | When a select permission privilege is revoked on a system table from the public group, this change does not persist after an SAP ASE version upgrade. See KBA 3086018. |
| 825777 | The execution of DBCC PROC_CACHE("free_unused") will no longer free pages in the statement cache and only free pages in the procedure cache, in order to diminish the likelihood of hitting a 707 error, "System error detected during attempt to free memory at address < 0xvalue > . Please consult the ASE error log for more details.", together with a stack trace in the module 'mem_freepages' while a query is concurrently executed as dynamic sql. The ASE trace flag 2836 can be used to revert to the previous behavior of this dbcc to once again free statement cache pages along with procedure cache pages. See KBA 3114442. |
| 825797 | The message text for errors 2628 and 2630 is enhanced to indicate to which object the problematic page belongs when a shrink or split index operation fails. Additionally when an orphan locked spinlock is found, Adaptive Server will report the server process id value, besides the kernel process id value. |
| 825828 | The message, "FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.", together with a stack trace which includes the modules 'terminate_process', 'mda_nap_start' and 'mda_update_stmt_metrics' may be reported in the SAP ASE error log during the handling of an initial signal 11 hit, which will result into an implicit shut down of Adaptive Server. See KBA 3123917. |
| 825833 | The Backup server is enhanced to report in the error log the Adaptive Server process ID value (spid) which initiated the DUMP or LOAD command for example '00021:', followed by the command type operation for example '00:' for TRANSACTION or '01:' for DATABASE. |
| 825884 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'LeHashTable::GetBucket' or 'LeHashTable::GetPartition' may be reported in the SAP ASE error log when a hash join select query is run in parallel while the query execution is aborted. See KBA 3126590. |
| 826055 | SAP ASE Sybdiag report appears blank on browsers other than Internet Explorer. See KBA 3140802. |
| 826382 | The 'LockRequests' and 'LockWaits' columns for MDA tables monOpenObjectActivity and monTempdbActivity may report lock statistics data which unexpectedly include lock statistics data for internally scanned system tables. |
| 826387 | The message, "Current process infected with signal 11 (SIGSEGV)", may be reported with a stack trace including ptn__setup_pdeslookupopt() in the SAP ASE error log when inserting a row into a partitioned table during alter table drop partition on the same table at the same time. See KBA 3179925. |
| 826413 | A new SAP Adaptive Server trace flag 17015 is added to print the diagnostics of an alarm if it is freed again. See KBA 3189250. |
| 826636 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LePlanRelease' together with a stack trace which includes the modules 'tdsrecv__dynexec_xoltp' and 's_execute' may be reported in the SAP Adaptive Server error log during the execution of a dynamic SELECT query. See KBA 3208573. |
| 826663 | The error message, "ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect", together with a stack trace which includes the modules 'omni_exec_immediate', 'omni_sync_roles' and 'set_role', may be reported in the SAP ASE error log when executing SET ROLE < role-name > ON. See KBA 3231085. |
| 826726 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'cm_dbclean' together with a stack trace which includes the modules 'masterrecover' and 'dsinit' may be reported in the SAP ASE error log when starting a 4KB page size Adaptive Server whose 'default data cache' size is greater than 2TB. |
| 826773 | Setuphadr supports intermediate CA to enable SSL in HADR. |
| 826783 | SAP ASE is enhanced to also report the error messages for 5082, 5087, 5088, and 5089 along with their SQL text in the error log, when ALTER DATABASE command is executed. See KBA 3217783. |
| 826790 | A 2601 error, "Attempt to insert duplicate key row in object 'sysservers' with unique index 'csysservers'", may be reported in SAP ASE error log when sp_addserver is run to add the 999th entry into sysservers table. See KBA 3218200. |
| 826854 | A 14127 error, "Cannot drop or modify partition descriptor < partition-information > as it is in use. Please retry your command later. Total reference count ' < value > '. Task reference count ' < value > '.", may be frequently reported by SAP ASE when ALTER TABLE ... DROP PARTITION is run. See KBA 2056295. |
| 826868 | A 9561 error, "An insert or update to table ' < table-name > ' places column ' < column-name > ' at offset < value > , ending at offset < negative-value > . The maximum permitted ending offset for this column is < value > . This is a server internal error.", together with the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeDataRow::writeRow' may be reported in the SAP ASE error log when an UPDATE or INSERT is executed. See KBA 3226235. |
| 826932 | A 930 error, "Database ' < database-name > ' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with 'for load' option.", may be reported during ALTER DATABASE on a database created FOR LOAD while the SAP ASE configuration option 'enable granular permissions' is enabled. See KBA 3229663. |
| 826935 | In rare circumstances, the login password plain text is not obfuscated in the audit records when the SAP ASE configuration option 'auditing' is enabled, if the login password is NULL or contains the same delimiter in which it is enclosed. |
| 826963 | When a SELECT query with a LIKE clause that is using a global variable is executed, SAP ASE may return an incorrect result. See KBA 3366290. |
| 827009 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'open__byname' together with a stack trace which includes the modules 'pre__replace_cpc' and 'pre__process_vcpc_fi' may be reported in the SAP ASE error log when a SELECT query is recompiled while the Adaptive Server configuration option 'deferred name resolution' is enabled. See KBA 3235230. |
| 827135 | Document enhancement request to add a description of the National Language prefix "N" to the documents. This prefix is similar to the "U&" prefix for Unicode, and can be used for nchar, nvarchar, ntext, etc. datatypes. |
| 827140 | Under certain circumstances, the message, "Proceeding buffer with MASS_DESTROY set", may be reported in the SAP ASE error log. See KBA 3247012. |
| 827184 | A 17915 error, "Warning: the specified account is currently active.", is unexpectedly not reported by SAP ASE when sp_droplogin ' < login-name > ' is run and the login name to delete is active. |
| 827188 | In rare circumstances, a 695 error, "An attempt was made to read logical page ' < page-number-1 > ' for database ' < database-name > ' ( < database-id > ), object '' (99), index ' < Unknown > ' (0), partition ' < Unknown > ' (99) from disk. Wrong logical page ' < page-number-2 > ' was brought into cache 'default data cache'. If pages are being signed, this may indicate a signature check failure.", together with a stack trace which includes the modules 'pg_get_alloc_page' and 'ldxact' may be reported in the SAP ASE error log when LOAD TRANSACTION is executed. See KBA 3254015. |
| 827223 | While ALTER TABLE is executed to either split or move the data of a table's partition, if the built-in defrag_status() is concurrently run, SAP ASE may delete the defragmentation information for all the partitions of the table unexpectedly. See KBA 3254095. |
| 827256 | A 702 error, "Memory request for < value > bytes exceeds the size of single page of 16384 bytes.", together with a stack trace which includes the modules 'memalloc' and 'LeCloner::LeClSargMap' may be reported in the SAP ASE error log when a SELECT query that has thousands of elements into an IN clause is executed. See KBA 3268844. |
| 827426 | The message, “ct_send_data(): user api layer: external error: The connection has been marked dead.”, followed by the message, "bcp copy in partially failed", may be reported when BCP is executed by a Kerberos login to import certain data into an SAP ASE table. See KBA 3326409. |
| 827435 | The message, "background task message: sp_dbxt_do_resize_dev: Device < device-name > of size < size > resized by < negative-value > to a total size of < size > .", may be reported in SAP ASE error log on Windows platform when DISK RESIZE fails due to insufficient free space on the file system where the device resides. See KBA 3195468. |
| 827472 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'EVP_MD_CTX_cleanup' and 'ssl_handshake' may be reported in the SAP ASE error log during an SSL connection attempt, even if fix in CR 825726 is included. See KBA 3310377. |
| 827490 | In rare circumstances, the message, "Adaptive Server Enterprise system exception generated by a storage access violation.", together with a stack trace which includes the module 'ra_ci_scanner_thread' may be reported in the SAP ASE error log on Windows during Rep Agent startup in an HADR setup with synchronous replication. |
| 827506 | A 12313 error, "Insert into page id < page-id > of index id < index-id > of table < table-name > (id = < table-id > ) in database < database-name > tried to replace undeleted RID ( < page-number > , < row-number > ) at slot < slot-number > and ridposn < rid-position-number > . Try dropping and recreating the index.", may be reported in the SAP ASE error log during a concurrent execution of WRITETEXT and INSERT commands on the same table having in-row-lob columns. See KBA 3282626. |
| 827512 | In rare circumstances, a 9859 error, "A DDL command like ALTER/TRUNCATE TABLE is active on partition ' < partition-name > ' of object ' < table-name > ' in database ' < database-name > '. Please retry your query later.", may be reported when a SELECT statement is executed while the partition is being dropped or truncated by another session. |
| 827522 | The message "CCLCryptFactory_createKeyPair failed with error" followed by the message, "Current process infected with 11 (SIGSEGV)", in the module 'ex_testhandle' together with a stacktrace which includes the modules 'attrib_getrow' and 'encr_udcall_rsa_renew' be reported in the SAP ASE error log when RSA keypair generation fails. See KBA 3288597. |
| 827537 | The DTD validator has been disabled by default in SAP Adaptive Server. You can enable it by setting the environment variable XERCES_DISABLE_DTD to 0. |
| 827561 | The error message, "10000 - Unanticipated Error: An unanticipated error occurred. The message returned was "For input string: "B"".", may be reported by SAP Sybdiag when it is run on HP-UX platform. See KBA 3296389 . |
| 827564 | SAP Adaptive Server will make use of unique state values for error 9561, "An insert or update to table < table-name > places column < column-name > at offset < offset-value > , ending at offset < offset-value > . The maximum permitted ending offset for this column is < offset-value > . This is a server internal error.", so to help uniquely identify the relevant client of module 'colOffErr' whereby this error is reported. |
| 827593 | In rare circumstances, the checkpoint process "CHECKPOINT SLEEP" may hang and block other processes. This will require a manual restart of SAP ASE to clear the issue. See KBA 3291530. |
| 827603 | When using a very large valDays as a parameter to generate a certification file, SAP Adaptive Server may use an invalid datetime in place of the correct datetime when printing the SSL certificate load success message. See KBA 3290674. |
| 827615 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'proc__deallocmem' together with a stack trace which includes the modules 'freeprocs' and 'd_proccache' may be reported in the SAP ASE error log when DBCC PROC_CACHE('free_unused') is executed. See KBA 3301324. |
| 827638 | When SAP Adaptive Server is configured for secure LDAP user authentication and the LDAP Server is configured to only accept TLS 1.2 connections, then LDAP user authentication to ASE will fail. See KBA 3292538. |
| 827643 | In rare cases, the ExecutionCount column in monCachedProcedures system table will report 0 even though the procedure has been executed recently. See KBA 3293091. |
| 827650 | In rare circumstances, a 290026 error, "Invalid DOL data row pointer: row < row-number > with status < status-value > must be normal row instead of compressed row.", together with a stack trace which includes the modules 'collocate' and 'LeMerge::mergeNext' may be reported in the SAP ASE error log when accessing a table that has pages marked for compression and the table is not marked for compression. See KBA 3293801. |
| 827653 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memalloc' together with a stack trace which includes the modules 'rvm__get_command' and 'parserr', may be reported in the SAP ASE error log when auditing is enabled and when a CREATE PROCEDURE command which includes USE < database-name > is the first command executed post-logon in the session. Alternatively, a 719 error, "The last prochdr value is not available for the prochdr '0x0'. This is an Adaptive Server internal error ...", may be seen. See KBA 3294210. |
| 827662 | SAP ASE is enhanced to improve the diagnostic output information when a wrong page is read while attempting to read an allocation page. See KBA 3281881. |
| 827668 | SAP Adaptive Server is enhanced to print diagnostics information when the message, "SIGSEGV is caught by VEH_Optimize()", is reported in the SAP ASE error log. The trace flag 16996 when enabled will additionally report in the error log the call stack of the session hitting this SIGSGEV. |
| 827673 | A 12212 error, "Internal Error: The partition ID ( < partition-id-1 > ) of the lock does not match the partition ID ( < partition-id-2 > ) of the new request on this lock. dbid= < database-id > , objid= < object-id > , pageno= < page-number > , rowno= < row-number > locktype= < lock-type > ", together with a stack trace which includes the modules 'lock_do_logical', 'updateLeRow' and 'writetext' may be reported in the SAP ASE error log when WRITETEXT is run on a partitioned table. See KBA 3298831. |
| 827694 | enable LOB in triggers by default when "enable functionality group" on. See KBA 2162544. |
| 827701 | When a query execution plan is printed with the option 'set showplan on', SAP ASE may not report the name of a table variable that is used in the SELECT query. |
| 827729 | A 2601 error, "Attempt to insert duplicate key row in object 'sysstatistics' with unique index 'csysstatistics'", may be reported by SAP ASE when ALTER TABLE DROP COLUMN with a list of hundreds of columns to drop is executed. See KBA 3303371. |
| 827730 | In rare circumstances, a 806 error, "Could not find virtual page for logical page < page-number > in database ' < database-name > '.", together with a stack trace which includes the modules 'pg_get_alloc_page' and 'mda__collect_cached_ptninfo' in the SAP ASE error log may be reported when monCachedObject MDA table is queried. |
| 827742 | A 102 error, "Incorrect syntax near '""'.", followed by a 11031 error, "Execution of unknown type < partition-condition-name > failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo. < partition-condition-name > .", may be reported after upgrading SAP ASE while reparsing round-robin condition partition text. See KBA 3305953. |
| 827768 | The message, "Backup Server: 4.18.2.1: Unsupported device type. The stat() system call returned type '2000' for 'C:\WINDOWS\system32\NUL'. Refer to your operating system documentation for more details.", may be reported on Windows platform when DUMP DATABASE using a NULL device is executed. see KBA 2809950. |
| 827771 | In very rare circumstances, with HADR setup configured, when the primary ASE goes down and sap_failover is issued, and the primary ASE is booted back immediately, the message, "HADR operation: sap_failover is failed", may be reported in the SAP ASE error log and the 'hadr mode' of both ASE instances may be found as "Primary" resulting in a split-brain situation. |
| 827789 | In rare cases, the ReadTime column in monDeviceIO system table will report less read time than the real I/O read time. See KBA 3310221. |
| 827797 | When ALTER TABLE is executed by using an invalid object such as a view object, despite a 11307 error, "The object < object-id > in database < database-id > is not a valid parameter for the built-in function logschema(). The object must be a user table or a stored procedure.", followed by a 11309 error, "The built-in function logschema() failed for object < object-id > in database < database-id > . See the other messages printed along with this message for more information.", being reported, this may result in an HADR setup into the SAP ASE Rep Agent schema cache exhaustion causing DLL commands such as ALTER TABLE or DROP TABLE to hang. See KBA 3312643. |
| 827802 | In rare circumstances, the message, "RepAgent( < database-id > Failed to change the memory protection for a CI Native thread, ...", may be reported in the SAP ASE error log when Rep Agent is started in an HADR setup, while a CI native thread allocates stack from shared memory. This is a warning message since the CI native thread will revert using the default stack. |
| 827809 | The message, "Messaging services API call failed. Operation 'um_get_ep_maxmsglen'. Error received from the messaging provider. . .", may be reported when IBM MQ msgsend() is executed after having upgraded to SAP Adaptive version 16.0 SP03 PL13 and SAP Adaptive version 16.0 SP04 PL03. See KBA 3322015. |
| 827810 | A 290025 error, "Invalid DOL data row pointer: row < row-id > with status < row-status > must be the forwarded row location instead of the home row location." or A 290026 error, "Invalid DOL data row pointer: row < row-id > with status < row-status > must be normal row instead of compressed row.", may be reported by SAP Adaptive Server when a SELECT query is executed and an invalid data row pointer is encountered. These messages will now include the SQL Text that was executing when the error was encountered along with diagnostic information. KBA 3382759 |
| 827823 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'tdslob_handle' together with a stack trace which includes the modules 'tdsrecv_dynamic' and 'memalloc' may be reported in the SAP ASE error log during the execution of a dynamic SELECT query. |
| 827826 | In rare circumstances, a 707 error, "System error detected during attempt to free memory at address 0x0. Please consult the ASE error log for more details.", in the module 'mem__shrink_this_phdr' together with a stack trace which includes the modules 'tdsrecv__xoltp_finish' and 'tdsrecv_dynamic' may be reported in the SAP ASE error log during the cleanup phase of a failed dynamically prepared query execution. KBA 3314961. |
| 827834 | The MDA tables monDeadLock, monLocks and monLockTimeout may report negative values in PageNumber column. See KBA 3321508. |
| 827839 | In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'Optimize' together with a stack trace which includes the modules 'rvm_clean_pcrtree' and 'kill_proc', followed by the message, "FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.", may be reported in the SAP ASE error log when a SELECT query is executed and Adaptive Server has captured an initial signal 11 error and was attempting to recover from it. The messages, "SIGSEGV is caught by VEH_Optimize()" and "Return VXACTION_CONTINUE from VEH_Optimize()" will be first seen in the error log. See KBA 3316645. |
| 827840 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'des__uninstall_or_swap' together with a stacktrace which includes the modules 'des__recreate' and 's_mustrecompile' may be reported in the SAP ASE error log when accessing a partitioned table while another process is running ALTER TABLE ... DROP PARTITION. See KBA 3315867. |
| 827846 | In rare circumstances, an incorrect result set may be returned when a SQL query includes some aggregate functions and group_hashing is enabled. See KBA 3316594. |
| 827852 | SAP Adaptive Server is enhanced to allow the current settings of the optimization goal 'sap_olap' to persist through ASE version upgrades. See KBA 3317118. |
| 827862 | SAP ASE is enhanced to remove from the data cache a stale page following a 694 error, "An attempt was made to read logical page < logical-page-number > , virtpage < virtual-page-number > from virtual device < device-name > for ... The page was not read successfully. You may have a device problem or an operating system problem.". See KBA 3401075. |
| 827867 | In rare circumstances, Adaptive Server processes may appear to hang due to being in runnable state while waiting for the database-disk-map lock held by an ALTER DATABASE command execution to be released. See KBA 3319334. |
| 827881 | The dynamic configuration option "max cached stmt size" was introduced in SAP ASE 16.0 SP04 PL02 and 16.0 SP03 PL12 releases with a default value of 16K bytes. Some performance degradation may be observed when the statement cache is enabled and frequently executed SQL queries with a text size bigger than 16384 bytes are not cached due to this default size value. The default value is now set to 64K bytes. See KBA 3231350. |
| 827929 | In rare circumstances, the database timestamp (@@dbts) may jump by a large amount unexpectedly when LOAD TRANSACTION is run and the archive being loaded was taken on a database with SAP ASE replication enabled. See KBA 3326882. |
| 827948 | SAP Adaptive Server option 'des_greedyalloc' which is set by DBCC TUNE execution does not result in a reduction in latch sleep during heavy INSERT activity on a large database. See KBA 3326377. |
| 827971 | The HADR Overview menu in AMC raises the message "Error in checking if Fault Manager is enabled" on an ASE that is configured with a case insensitive character set. Seek KBA 3329029. |
| 827981 | The database level replication status may become inaccurate after dropping the last replicated table or stored procedure without first disabling the replication at the object level. |
| 827995 | SAP Adaptive Server is enhanced to report useful debugging information that should help narrow down the root cause of a 2780 error, "Maxlen ( < value > ) is less than length ( < value > ) for the new constant ...". See KBA 3053562. |
| 827999 | A 1621 error, "Type ' < value > ' not allowed before login.", will not be reported in the SAP ASE error log when Adaptive Server is booted with trace flag 7860. See KBA 3332525. |
| 828008 | When DBCC PROC_CACHE with option 'free_unused' is executed and the ASE trace flag 2837 is enabled, SAP Adaptive Server will only free query tree objects from the procedure cache. |
| 828017 | A 631 error, "The length of < length > passed to delete row routine for the row at offset < offset > is incorrect on the following page of database ' < database-id > ': < page-id > . The expected row length is < length > . The offset should be no greater than < offset > .", may be reported in the SAP ASE error log during runtime rollback with PAGE_COMPRESS log records. See KBA 3420711. |
| 828030 | A 12358 error, "Cannot execute DISK RESIZE to shrink device ' < device-name > '. Please use 'sp_shrink' to shrink the device.", may be reported by SAP ASE when DISK RESIZE is not executed through the system stored procedure sp_shrink. See KBA 3343098. |
| 828071 | The message, "Kernel resource memory pool has been exhausted. Try increasing the value of 'kernel resource memory'", followed by a 9241 error, "RepAgent( < database-id > ): Failure initializing the Rep Agent Context.", may be reported in the SAP ASE error log after the server has booted and there are dozens of Rep Agents coming online. As a result of the error, the Rep Agent fails to come online. See KBA 3340730. |
| 828074 | The message, "No server log file open; Using stderr for log.", may be printed to the console when starting the Backup Server when a ' < backup-server-name > .cfg' does not exist and is created for the first time. See KBA 3340741. |
| 828091 | Signal 11 with stack including des_clean - See KBA 3342427 |
| 828165 | In rare circumstances, a COMMIT TRANSACTION may not finish if an external attention is sent to SAP ASE by the client application. |
| 828184 | A 8201 error, "Keep count of descriptor (objid= < object-id > , dbid= < database-id > ) was expected to be 1. Instead 0 was found.", in the module 'des_rekeep' together with a stack trace which includes the modules 's_compile' and 'proc_cacheplan' may be raised in the SAP ASE error log during the execution of an UPDATE following a 1205 deadlock error. See KBA 3354684. |
| 828191 | SAP ASE may continue to collect monitoring data for some historical MDA tables when the configuration option " < value > pipe active" is set as 1 but the configuration option " < value > pipe max messages" is set as default or 0 and this may bring some potential performance impact on ASE. See KBA 3353691. |
| 828195 | The descriptions reported by sp_helpconfig for multiple configurations are incorrect or incomplete. See KBA 3425488. |
| 828196 | The message, "Error: 1105, Severity: 17, State: < unique-value > ", is reported in the SAP ASE error log together with a diagnostic call stack when the Adaptive Server trace flag 1102 is enabled. The call stack is no longer needed as it makes the error log to grow a lot. The end-user can execute "sp_altermessage 1105,'with_stack','true'" to print the diagnostic call stack while restoring the original behavior of trace flag 1102. See KBA 3354576. |
| 828200 | A 924 error, "Database ' < database-name > ' is already open and can only have one user at a time.", and a 3512 error, "Cannot checkpoint database ' < database-name > ' because its status is: not usable.", may be reported when trying to disable single user mode for a database and it is in use. Additionally, sp_helpdb will no longer report the database is in single user mode even though it remains in single user mode. See KBA 3355158. |
| 828216 | Reduced locks contention when executing ALTER TABLE in a database configured for DDL replication. See KBA 3364830. |
| 828233 | SAP ASE is enhanced to not silently skip corrupted pages during a table scan and instead report an error. See KBA 3365514. |
| 828234 | A 1029 error, "CS-Library error: Error: 33816868, Severity 1 -- 'cs_convert: cslib user api layer: common library error: The result is truncated because the conversion/operation resulted in overflow.'", may be reported in the SAP SRS error log by the DSI thread when replication and SQL Statement Replication feature are enabled and the size of SQL statement where clause exceeds the system limit of 16385 bytes. See KBA 3401120. |
| 828289 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'senderror' together with a stack trace which includes the modules 'terseprint', 'ex__doprint' and 'exc_callprint', may be reported in the SAP ASE error log when an error was previously hit while the configuration option 'secondary signal handling' is enabled. See KBA 3373571. |
| 828292 | SAP Adaptive Server is enhanced to allow supporting the maximum number of file descriptors at boot time for Linux and Solaris systems. See KBA 3377529. |
| 828294 | When a configuration setting is changed using the sp_configure stored procedure the configuration file is updated with the new settings and subsequently, the order in which the syb_default_pool and syb_blocking_pool entries listed in the configuration file will reverse with each change. See KBA 3364393. |
| 828330 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'open__byname' together with a stack trace which includes the modules 'proc__used_as_login_script' and 'dropobject' may be reported in the SAP ASE error log when a light weight procedure is dropped. See KBA 3375053. |
| 828339 | A 1289 error, "Internal Error in lock manager routine: Invalid lock mode exclusive page, requested by task (family id < parent-spid > , < child-spid-1 > ) conflicts with existing family request mode exclusive page belonging to task (family id < parent-spid > , < child-spid-2 > .", may be reported when DBCC CHECKSTORAGE is run. See KBA 3356016. |
| 828348 | When using the deprecated system stored procedure sp_addlogin to create a new login using the default authentication mechanism in a replicated master database (HADR, MSA or warm standby), the master..syslogins status column shows different values on the primary and standby SAP ASE servers. See KBA 3372057. |
| 828351 | The fix made in CR 826122 has been backed out in CR 828339. In the current CR we have redesigned CR 826122 initial fix in order to avoid hitting a 4306 error, "There was activity on database since last load, unable to load. Must restart load sequence with the load database to continue.", when LOAD TRANSACTION is run after DBCC CHECKDB or DBCC CHECKCATALOG was executed, while the database was kept offline and in load sequence. See KBA 3143853. |
| 828365 | In rare circumstances, a 9210 error with state 13, "RepAgent( < database-id > ): Fatal error from CT-Lib. (CT-Lib command = usctresults, return status = 4047).", may be reported in the SAP ASE error log when replication is enabled, resulting in an implicit RepAgent shut down. See KBA 3377051. |
| 828368 | In rare circumstances, the message, "ulvspinlock: spinlock being released improperly.", in the module 'ulvspinlock' together with a stack trace which includes the modules 'des_do_get' and 'open_user_table' may be reported in the SAP ASE error log during the execution of a query. |
| 828386 | The monitor counter for "Procedure Removals" reported by sp_sysmon will be incremented each time a dynamically prepared statement is executed and the configuration "streamlined dynamic SQL" is disabled. See KBA 3390135. |
| 828389 | The Rep Agent configuration parameter 'net password encryption' has no effect when it is set to false when SAP Adaptive Server is upgraded to 16.0 SP04 PL04 release. See KBA 3377092. |
| 828439 | In a high concurrency system, 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.", the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'init_before_msg' together with a stack trace may be reported in the SAP ASE error log during the execution of a query. |
| 828443 | In a high concurrency system, 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.", the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'freeprocs' together with a stack trace may be reported in the SAP ASE error log during the execution of a query. |
| 828450 | The remote server configuration parameter 'net password encryption' has no effect when it is set to false when SAP Adaptive Server is upgraded to 16.0 SP04 PL04 release. See KBA 3379590. |
| 828463 | Optdiag enhancements to support -W functionality allowing to disable password encryption. |
| 828476 | The message, "Row count mismatch for the command executed on ' < server-name > . < database-name > '. The command impacted 0 rows but it should impact 1 rows.", may be reported in the SAP SRS error log by the DSI thread when replication and SQL Statement Replication feature are enabled and the SQL statement is a deferred delete. |
| 828477 | In an HADR setup, a timeslice error may be reported in SAP ASE error log, together with a stack trace which includes the modules 'ra_ci_scanner_get_wparm_value' and 'ra_ci_distribute_cmd', when SQL Statement replication is enabled or when replicating a stored procedure having a parameter whose size exceeds the ASE page size. |
| 828495 | Under rare circumstances, SAP Adaptive Server may implicitly shutdown with the message, "Current process infected with 11 (SIGSEGV)", in the module 'ktMuxThreadScheduleOut' or 'ss_nulltoany' may be reported in the SAP error log when running dbcc sqltext against a spid that is changing. See KBA 3385381. |
| 828554 | The fix made in CR 822348 for encrypted databases and released in 16.0 SP04 PL04 and 16.0 SP03 PL13 is backed out in the current CR 828554 because it causes issues. See KBA 3407931. |
| 828603 | SAP Adaptive Server may fail to bootstrap and produce a core dump file during startup after having upgraded SUSE operating system glibc library to version 13.2 which includes library version libstdc++.so.6.0.32. See KBA 3394455. |
| 828630 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'apply_grrev' together with a stack trace which includes the modules 'grantrev' and 's_execute' may be reported in the SAP ASE error log when GRANT or REVOKE is executed. See KBA 3411308. |
| 828710 | The fix made in CR 822733 for encrypted databases and released in 16.0 SP04 PL03 and 16.0 SP03 PL12 is backed out in the current CR 828710 because it causes issues. See KBA 3411406. |
| 828711 | In a high concurrency system, some SQL descriptor memory from the procedure cache may be reallocated to a new session, yet another session may still access this memory. This can cause SIGSEGV errors to be reported in the SAP ASE error log while a session is accessing this memory. |
| 828786 | In HADR setup, the command "sp_hadr_admin setlogin, < login > " will fail and the error "Arithmetic overflow during implicit conversion of INT value to a UNSIGNED INT field" will be reported, if login which has negative suid is being used during setlogin. See KBA 3418052. |
| 828820 | In rare circumstances the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'procrm' together with a stack trace which includes the modules 'd_proccache' and 'freeprocs' may be reported in the SAP ASE error log when DBCC PROC_CACHE is executed. This may sometimes lead to an implicit shutdown of Adaptive Server. See KBA 3301324. |
Read more...
Environment
- Linux on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP04 PL05, ASE SP04 PL05, SP04 PL05 Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)