/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 SP03 PL15 . 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. |
| 812699 | set show_object_list on does not provide object information for cache statements. |
| 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. |
| 818545 | Under rare circumstances, a timeslice error in the module 'atomic_try' followed by a stack trace which includes the modules 'kieng_allocproccache' and 'uballoc' may be reported in the SAP ASE error log when increasing the size of a thread pool with alter thread pool and the procedure cache is starved of free pages and/or have very high contention. See KBA 2760444. |
| 819875 | sp_showoptstats execution may generate incorrect xml output when histogram values contain multibyte characters. See KBA 2827889. |
| 820309 | The message, “Current process (0x5f0554d0) infected with signal 11 (SIGSEGV)”, in the module ‘ubfgrow’ together with a stack trace which includes the module ‘memallocheap’ may be reported in the SAP ASE error log due to heap memory corruption. When Adaptive Server is bootstrapped with trace flag 797 instrumentation logic will be enabled allowing to capture the process causing this issue. See KBA 2858959. |
| 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. |
| 822514 | The output of DBCC HOTBUFS may report a database id of 0 (dbid) for buffers that have been freed to the LRU end chain of the buffer cache. See KBA 2957818. |
| 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. |
| 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. |
| 823906 | A 1157 error, "Insert free space value < negative-value > in page header of DOL datapage < page-number > belonging to object id < object-id > in database ' < database-id > ' is incorrect. It has been recomputed and is now < negative-value > .", may incorrectly be reported by SAP ASE when the table attribute "exp_row_size" has been changed via sp_chgattribute for a table with existing data. See KBA 3010154. |
| 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. |
| 825242 | The message "The sybsystemdb device must be the same size or larger than the sybsystemdb database." may be reported by srvbuildres when the resource file has USE_DEFAULT for the sybsystemdb database size and has specified a specific device size for sybsystemdb. See KBA 3081251. |
| 825520 | The error message, "Backup Server: 5.16.2.2: Client-Library error: Error number 44, Layer 4, Origin 1, Severity 188978561028: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed..", may be reported by SAP Backup Server when DUMP DATABASE is executed and Kerberos authentication is enabled in Adaptive Server. See KBA 3422498. |
| 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. |
| 826348 | The message, "stack_tracer: stack overflow last chance handler. Task < kpid-value > has completely exhausted stack at line ...", may be reported in the SAP ASE error log when a stored procedure that is calling a user defined function which is using a temporary table is interrupted. See KBA 3168911. |
| 826360 | In rare circumstances, the frequent message with transaction commit wait expired will be reported in primary ASE error log when the primary ASE is restarted from crash situation or shutdown with wait nowait_hadr. |
| 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. |
| 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. |
| 826815 | Feature enhancement to provide ability to read out data from table with corruption. See KBA 3358688. |
| 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. |
| 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. |
| 827140 | Under certain circumstances, the message, "Proceeding buffer with MASS_DESTROY set", may be reported in the SAP ASE error log. See KBA 3247012. |
| 827181 | Changes to hashing algorithm to provide better hash key distribution for SAP Adaptive Server statement cache component. ASE needs to be started with trace flag 11032 to enable this change. See KBA 3269956. |
| 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. |
| 827492 | In SAP ASE sample extended stored procedure program xp_echo.c fails to compile with error "xp_echo.c:20:18: fatal error: port.h: No such file or directory". See KBA 3281995. |
| 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. |
| 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. |
| 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 3303293. |
| 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. |
| 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. |
| 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. |
| 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. See KBA 3422515. |
| 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 |
| 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. |
| 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. |
| 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. |
| 827848 | The message, "Assertion (xdes- > xcomplogbytesleft_diag > = 0) ", may be reported in the SAP ASE error log during the ROLLBACK of a CREATE INDEX with ONLINE command and the diagserver binary is in use. |
| 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. |
| 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. |
| 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. See KBA 3422517. |
| 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 |
| 828109 | Feature enhancement to have the 1621 error message specify the ip address and port that sent the incorrect packet. See KBA 1973518. |
| 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. |
| 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. |
| 828201 | The global variable @@heapmemsize may return a large negative value if the size of the SAP ASE configuration option 'heap memory per user' exceeds 2GB. See KBA 3355209. |
| 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. |
| 828237 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'Optimize' together with a stack trace which includes the module 'open_range' followed by a second signal 11 occurrence in the module 'tabvar_release' may be reported in the SAP ASE error log when INSERT TABVAR SELECT statement is run. See KBA 3357731. |
| 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. |
| 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. |
| 828344 | The stored procedure sp_passwordpolicy silently ignores the fourth parameter when using the 'set' option for any setting other than 'keypair regeneration period'. See KBA 3372056. |
| 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. See KBA 3374985. |
| 828369 | A 15497 error, "The password for the master key of database 'master' has not been set", may be reported when Adaptive Server tries to decrypt database sybsystemdb/sybsystemprocs during SAP ASE restart. See KBA 3373725. |
| 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. |
| 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. See KBA 3422482. |
| 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. See KBA 3422038. |
| 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. See KBA 3422009. |
| 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. |
| 828550 | SAP ASE may report inconsistent I/O activity data for temp tables in the monIOQueue MDA table. See KBA 3390201. |
| 828553 | Upgrade SAP CCL library to version 8.5.52. |
| 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 3352609. |
| 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. |
| 828605 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ct__api_state_trans' together with a stack trace may be reported in the SAP ASE error log when a Component Integration Service (CIS) query is executed. See KBA 3394426. |
| 828637 | A 605 error, "An attempt was made to fetch logical page ' < page-number > from cache 'default data cache'...", together with a stack trace while includes the modules 'extent_reconfigure' and 'pg_zapoam' may be reported in the SAP ASE error log when DBCC REBUILDEXTENTS is run on an All Pages Locked (APL) table. |
| 828691 | A 14218 error, “Cannot create or execute a SQLJ UDF, because Java services are not enabled.”, may be reported by SAP ASE when executing a stored procedure which includes a function that has not been yet created because the configuration option “deferred name resolution” is enabled. See KBA 3422986. |
| 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. See KBA 3464047. |
| 828738 | In rare circumstance the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'get_range_sdes' together with a stack trace which includes the modules 'StoredTab::open()' and 's_compile_stmt' may be reported in the SAP ASE error log when a query is being compiled. See KBA 3408394. |
| 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. |
| 828797 | Print a diagnostic message to the SAP ASE error log when a manual shared memory dump is taken with the Sybmon utility. |
| 828803 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'bufunkeep_do_decrement()' may be reported in the SAP ASE error log when DBCC CHECKSTORAGE is executed for encrypted database. |
| 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. |
| 828883 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace may be reported in the SAP ASE error log during the execution of a query plan in systems using index compression feature. The stack trace for the killed connection may report different information depending on the victim’s code path and the procedure cache memory corruption caused by concurrent index decompression operations being executed. See KBA 3464195. |
| 828900 | A 712 error, "There is insufficient heap memory to allocate < number > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.", may be reported when DBCC LISTOAM is run against a very large table. See KBA 2139552. |
| 828901 | In rare circumstances an undetected deadlock may occur in SAP ASE between three sessions, when one session executes reserved_pages() built-in on syslogs, another session executes an INSERT which requires additional space allocation for logging needs, and another session attempts to expand the database log via ALTER DATABASE. See KBA 3464199. |
| 828913 | In rare circumstances the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memalloc' together with a stack trace which includes the modules 'rvm__audit_getcommand_subcommand' and 'ex_audit' may be reported in the SAP ASE error log when auditing is enabled and an error for a client cursor is being processed. See KBA 3425476. |
| 828917 | In rare cases, the PhysicalReads column in monProcessActivity system table may report negative value when insensitive cursor is executed. |
| 828933 | A site handler process will appear to hang after receiving an invalid packet. See KBA 3417710. |
| 828937 | In rare circumstances, SELECT INTO may hang on heavily loaded SAP ASE systems when executed into an in-memory database with a call stack which includes the modules 'pg__allocate_in_oamcreate', 'getpage__noscan', 'getpage_with_validation' and 'bufsearch_cache_getlatch'. See KBA 3418026. |
| 828953 | The TCP/IP incoming connections backlog queue for SAP ASE on Linux is restricted to 128, potentially causing certain clients to fail to connect during a surge of incoming connection requests. Similarly, this issue can arise on the Solaris platform, where the backlog queue is limited to 256. See KBA 3419671. |
| 828966 | The message, "The page number for page < page-number > in the buffer < buffer-address > found zero (ppageno = 0, pptnid = 0, pindid = 0, ppstat = 0x0, pts_hi = 0000, pts_lo = 00000000). This may indicate uninitialized page.", may be reported in the SAP ASE error log when trace flag 829 or 830 is enabled although there is no reason per se. |
| 828984 | A 3052 error, "DUMP TRANSACTION requires a dump configuration name because the configuration option 'enforce dump configuration' is enabled.", may be reported by SAP ASE when DUMP TRANSACTION is run while the configuration option 'enforce dump configuration' is set, but the dump succeeds instead of failing. See KBA 3429418. |
| 829006 | The message text for error 12944 has been enhanced with, "The insert free space value ( < value > ) in the page header of DOL datapage < value > , partition ID < value > is not equal to the sum of cfs and ncfs ( < value > ) in the page, recomputation of insfs will be attempted.", and when the recompute gives the same values the new informational message, "The Insert free space value ( < value > ) in the page header of DOL datapage < value > , partition ID < value > has not changed. Plan to run REORG REBUILD for table ' < value > '.", will be reported by DBCC CHECKTABLE. |
| 829008 | SAP Adaptive Server fail to bootstrap and report the message, "ASE_PCI: failed to bridge Pluggable Component Interfaces with code -77", on SLES 15 SP6. See KBA 3425215. |
| 829100 | If reserve_identity() built-in function is called against a table in another database, error 10330 may be reported with a message "INSERT permission denied" on the wrong table and database names although the user has the INSERT permission on the given table. See KBA 3434663. |
| 829140 | In rare circumstances, a shared memory dump taken with SAP ASE may run into hang on SuSE 15.6 or later versions. |
| 829247 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'os_schedcoma' may be reported in the SAP ASE error log when starting the server using process mode on AIX. See KBA 3448238. |
| 829267 | SAP ASE may implicitly shutdown when CREATE, ALTER, or DROP ENCRYPTION KEY command is executed for HSM key after ASE was restarted, due to a SIGTRAP signal. The message, "fatal: morestack on g0", will be reported in the SAP ASE error log. |
| 829335 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ra__ci_destroy_stop_scanner' together with a stack trace may be reported in the SAP ASE error log while Rep Agent is being shutdown. See KBA 3468141. |
| 829336 | A 605 error, "An attempt was made to fetch logical page < > from cache < > . Page belongs to database < > , object < > , index < > , partition < > and not to database < > , object < > , index < > , partition < > . Restart of ASE will clear the error. Please contact your System Administrator for help.", with state 9, or a 696 error, "An attempt was made to fetch logical page < > from cache < > . Page belongs to database < > , object < > , index < > , partition < > and not to database < > , object < > , index < > , partition < > . Restart of ASE will clear the error. Please contact your System Administrator for help.", with state 9, may be reported in the SAP ASE error log while scanning a DOL table or during an ASE version upgrade to 16.0 SPO4 PL05 or PL06. |
| 829342 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'get_range_sdes' together with a stack trace which includes the modules 's_mustrecompile' and 's_opentables' may be reported in the SAP ASE error log during the compilation phase of a query. See KBA 3476350. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Solaris on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP03 PL15, ASE SP03 PL15, SP03 PL15 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)