/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 PL07. 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 |
|---|---|
| 769843 | In some circumstances, SAP ASE may return an incorrect result set for a SELECT query, when the configuration option "disable varbinary truncation" is enabled and a unique index exists on a varbinary column of a DOL table, and the index is used by the query execution. See KBA 3380593. |
| 782482 | SAP ASE Sybdiag utility is enhanced to include jsagent log file and some other diagnostic information. |
| 816038 | The message, "SYBMULTBUF ERROR: Internal error: In get_init_command, expected C_INIT command. Instead, received command = 0.", may be reported in the Backup Server error log during a backup execution when there is a mismatch between 'backupserver' and 'sybmultbuf' binaries versions. See KBA 2675940. |
| 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. |
| 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. |
| 825583 | The new LOAD_STATUS option for the LOAD DATABASE ... WITH LISTONLY command allows SAP ASE to check if the LOAD DATABASE execution would have failed with either error 3105, “Data on dump will not fit into current database. Need < > Mbyte database.”, or error 3185, “The < > segment in the target database < > is too small ( < > MB) to accommodate the < > segment from the dumped database ( < > MB).”. |
| 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. |
| 826815 | Feature enhancement to provide ability to read out data from table with corruption. See KBA 3358688. |
| 827219 | In rare circumstances, misleading information may be reported in the SAP ASE error log during the recovery of a database. For example, the message, "Redo pass for database ' < database-name > ': 1220408100 records done (99%); 13 records left.", is unexpectedly followed a couple of hours later by the message, "Redo pass of recovery has processed < number-of-records > committed and < number-of-records > aborted transactions.", although the expectation is that Adaptive Server would have needed few minutes only to recover the reported 13 log records and complete the Redo pass phase. |
| 827243 | The online partition utilities are made compatible with DDL replication. |
| 827358 | A 7452 error, “Failed to find specified threshold in threshold cache on instance 1 for database < database-name > ... Use 'dbcc thresholds' to see the threshold cache contents.”, may be reported by SAP ASE when sp_dbextend is run against a mixed log and data database. Additionally the status for the segment ‘logsegment’ will be changed to “disabled by LCT”. See KBA 3268402. |
| 827431 | The stored procedure sp_displayaudit will report NULL for Subject Name if auditing for a login is enabled and that login has been dropped. See KBA 3277237. |
| 827437 | A 5899 error, "The value of the 'max memory' parameter ( < value > ) defined in the configuration file is not high enough to set the other parameter values specified in the configuration file.", may be reported when trying to set the value for "number of open databases" to a very high value (over 5300) even though there is sufficient memory available. See KBA 3452741 |
| 827541 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'vu_materialize' together with a stack trace including the modules 's_recompile' and 's_recompile' may be reported in the SAP ASE error log when a database is quiesced or when the transaction log gets full while querying a view. See KBA 03470774. |
| 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. |
| 828109 | Feature enhancement to have the 1621 error message specify the ip address and port that sent the incorrect packet. See KBA 1973518. |
| 828220 | In some circumstances, the message, "The free space count for fragment with lstart < logical-page-number > in database < database-name > was found to be negative and has been set to 0. Execute 'DBCC USEDEXTENTS( < database-name > ,0,1)' in single user mode to correct this count.", may be reported in the SAP ASE error log unexpectedly. |
| 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. |
| 828571 | In rare circumstances, CREATE INDEX 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 3392316. |
| 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. |
| 828736 | ASE Webservices is responding to HTTP TRACE and TRACK request during ASE Webservices is running. See KBA 3422047. |
| 828827 | In rare circumstances, random messages, "Current process infected with 11 (SIGSEGV)", or other errors like a 8201 error, "Keep count of descriptor (objid= < > , dbid= < > ) was expected to be < > . Instead < > was found.", together with a stack trace, may be reported in the SAP ASE error log when Adaptive Server runs out of "open objects", "open partitions", or "open indexes". |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 829097 | SAP Adaptive Server is enhanced to suppress SSL messages for module 'ssl_server_handshake' from being reported in the ASE error log. The ASE trace flag 7871 enables this behavior. See KBA 3442564. |
| 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. |
| 829123 | The error message, " < archive-name > is not a valid file path.", may be reported with SAP ASE 16.0 SP04 PL05 release when DUMP DATABASE is executed and the < archive-name > includes a double dot ".." character. See KBA 3442246. |
| 829140 | In rare circumstances, a shared memory dump taken with SAP ASE may run into hang on SuSE 15.6 or later versions. |
| 829144 | A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization." may be reported by SAP ASE when a query is executed against a table using simulated statistics and the data page count is 2147483648 or greater. See KBA 3440771. |
| 829152 | In rare circumstances a 2622 error, "Insufficient room on this page to insert a row of length < > . Page pointer = < > , pageno = < > , status = < > , ptnid = < > , indexid = 0, level = 0, pnextrno = < > .", together with a stack trace which includes the module 'dol_putdrow' may be reported in the SAP error log when a row for a DOL table is either inserted or updated. See KBA 3514582. |
| 829167 | The optimizer may have incorrect costing resulting in a poor performing plan when the page count of a table in the query exceeds 2147483647 pages. See KBA 3441930. |
| 829170 | A 3512 error, "Cannot checkpoint database < database-name > because its status is: not usable.", may be reported when sp_dboption is executed on an Archive Database to enable the 'single user' option. |
| 829220 | In rare circumstances the message, "Remapping failure for the query: < query-text > ", may be reported in the SAP ASE error log when executing a query which involves parameterized views. |
| 829234 | When sp_serverinfo is executed by a high number of sessions this results in high accumulated logical I/O on the syscurconfigs system table which causes performance degradation. See KBA 3445837. |
| 829240 | In rare circumstances, an interrupt request send by the application to Adaptive Server may be acknowledged while a user local transaction was in process, resulting in this transaction being rolled backed implicitly but unexpectedly. Thereafter a 12104 error, "A LOCK TABLE command is not allowed outside the scope of a transaction on table ' < table-name > ' in the database ' < database-name > '." may be reported by SAP ASE, or the message, "Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRAN is missing. Previous count = 1, Current count = 0.", may be seen in the SAP ASE error log. See KBA 3446837. |
| 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. |
| 829254 | In rare circumstances, a user task in SAP ASE may indefinitely sleep in the module 'xls_flush_plcqueue' while detaching an external transaction which action triggers the User Log Cache of the task to be flushed in the syslogs system table. See KBA 3448476. |
| 829259 | A 11105 error, "No such user/role ' < name > ' exists.", followed by a 7729 error, "Invalid role string ' < name > ' entered.", may be reported by SAP ASE when SET PROXY < user-name > is executed while Adaptive Server was started with trace flag 859 and < user-name > has a role name that is exactly 30 bytes long. See KBA 3451391. |
| 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. |
| 829292 | Adaptive server enterprise new stored procedure "sp_helpaltermessage" will report message altered for "WITH_LOG" or "WITH_STACK". See KBA 3452284. |
| 829297 | A 530 error, "Attempt to insert NULL value into column < column-identifier > in work table (table id < table-identifier > ); column does not allow NULLS. UPDATE fails.", may be reported in the SAP ASE error log during the execution of a SELECT query that includes Table-valued User Defined Functions (TUDF), Aggregate Functions and “Hash Vector Aggregate Operators” is shown in the query plan through “set showplan on”. See KBA 3515494. |
| 829302 | SAP ASE Workload Analyzer Command Line Utility would fail to connect to an SSL enabled repository server or would fail to start a capture or replay on an SSL enabled ASE server if a keystore protected by non-default password ("changeit") is specified. |
| 829318 | A 11216 error, "Internal Ct-Lib/Cs-Lib error 33816856: 'cs_convert: cslib user api layer: common library error: The conversion/operation was stopped due to a syntax error in the source field.'.", may be reported when sp_dump_history is run and an entry in the dump history file is broken into multiple lines instead of a single line. See KBA 3455971. |
| 829324 | A 17260 error, "Can't run sp_dump_history from within a transaction.", may be reported when executing sp_dump_history and the option "set chained on" is enabled. See KBA 3520065. |
| 829327 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'tmp_get_tmpobj_by_name' together with a stack trace which includes the modules 's_mustrecompile' and 'seq_schema_check' may be reported in the SAP ASE error log during the compilation phase of a query. See KBA 3463010. |
| 829328 | A 622 message, "Opentable was passed a varno of 0. Object ' < object-name > ' in database ' < database-name > ' already has that session descriptor in use. This occurred while opening object id < object-id > in database id < database-id > .", may be reported in the SAP ASE error log when executing a procedure that references a SQL User Defined Function after upgrading to 16.0 from 15.7 release. See KBA 3464200. |
| 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. See SAP KBA 3502182. |
| 829337 | A deadlock scenario may occur when a new site handler for a backup server is spawned and at the same time the current site handler is closing. See KBA 3470720. |
| 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. |
| 829348 | Enhance the output of deadlock information printed in the SAP ASE error log to include the isolation level when the configuration "print deadlock information" is enabled. |
| 829357 | A 834 error, "Illegal attempt to clean buffer ...", may be reported in the SAP ASE error log when running ONLINE DATABASE against a database that is currently in boot time recovery. See KBA 3467486. |
| 829421 | In rare circumstances, the CHECKPOINT process may be put to sleep when checkpointing a database, with a 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database ' < database-name > ' (id < database-id > ). This process will retry at intervals of one minute.", reported in the SAP ASE error log. This may lead into an undetected deadlock situation when the user attempts to increase the database log space. See KBA 3474684. |
| 829432 | A 403 error, "Invalid operator for datatype op: BUILTIN FUNCTION type: < datatype > .", may be reported when a stored procedure that includes a MERGE command having an UPDATE action which also assigns a local variable is run and the SAP ASE configuration option "enable HugePages" is not enabled. See KBA 3471006. |
| 829484 | A 3606 error, "Arithmetic overflow occurred.", may be reported by SAP ASE when sp_sysmon_spinlock is run while sp_sysmon is executed. See KBA 3479652. |
| 829512 | The message, "BACKUPSERVER: bs_trap; process received signal 11", together with a stack trace which includes the module 'bs__check_auth' may be reported in the Backup Server error log when an ODBC client issues a command to the Backup Server and the client's hostname is not included in the Backup Server's "hosts.allow" file. See KBA 3483225. |
| 829514 | The message, "Current process infected with signal 8 (SIGFPE)", or "timeslice < value > , current process infected at < address > ", in the module 's__collectdiagparam' may be reported in the SAP ASE error log when Adaptive Server has not restarted for long time. See KBA 2998380. |
| 829540 | When a MERGE command that has an UPDATE action which also assigns local variables is executed, SAP ASE will assign a NULL value to the second and subsequent local variables in the UPDATE action. |
| 829553 | In rare circumstances, the message, "bufunkeep_do_decrement(): Clearing the stale link between buffer < buffer-address > and its side mass (nil)", may be reported in the SAP ASE error log when a full database dump is taken with the EMC networker backup solution (KBA 3504582). |
| 829574 | A 2742 message, "SET DATEFIRST < > is out of range." and 'Error: 2805, state: 20', may be reported by SAP ASE when a stored procedure is executed with recompile and the configuration options 'enable metrics capture' and 'enable literal autoparam' are enabled. See KBA 3492504. |
| 829583 | In some cases, SAP ASE may perform an extra OAM scan when page allocation for new data is taking place on an allocation unit where the table did not have data residing onto it previously. This may contribute to additional latch contention on the table's first OAM page as well on the target allocation page. |
| 829615 | A 820 error, "Attempt to dirty non-log buffer ...", together with a stack stack trace which includes the modules 'bufpindirty', 'xls_bufpindirty_single' and 'bufdirty' may be reported in the SAP ASE error log when sessions execute concurrent transactions in a low durability database, like system tempdb, along with a dump database operation being in progress. See KBA 3496547. |
| 829624 | Apache Commons CLI is upgraded to version 1.8.0. |
| 829629 | Apache Commons CLI and POI library in Workload Analyzer Command Line Utility is upgraded to commons-io-1.8.0 and poi-5.3.0. |
| 829660 | Under rare circumstances, the message "timeslice < negative-value > , current process infected at free__linkedcst" together with a stack trace when inserting a parameterized text value into a unitext column using a dynamically prepared statement. |
| 829757 | Sybdiag may report incorrect "Kernel Interface Table" information on SuSE 15.x or RHEL 9.x. |
| 829762 | In rare circumstances, a 3478 error, "During undo the page timestamp value is less than new timestamp from log ...", followed upon the given database reboot with the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'dol_deldrow' together with a stack trace which includes the modules 'undo_dol_insert' and 'boot__recover_and_online' may be reported in the SAP ASE error log. |
| 829830 | A 2560 error, "The parameter 'Page_Num' as invalid value/type", may be reported when running DBCC FIX_PAGE on a page that is in unsigned integer range. See KBA 3516805. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP04 PL07, ASE SP04 PL07, SP04 PL07 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)