Symptom
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 |
---|---|
551014 | The built-in hashbytes() now supports the SHA-256 algorithm. See KBA 3108409. |
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. |
795707 | SAP Adaptive Server will perform memory movement sanity checks when started with trace flag 713 to help diagnose procedure cache memory corruption issues. |
800272 | The new database option “online free space acctg” allows SAP ASE to provide quicker end-users access to the database after an unpolite shutdown or crash of Adaptive Server, while the data segment free space counts are being recalculated. |
812699 | set show_object_list on does not provide object information for cache statements. |
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. |
821081 | High contention on the database spinlock (rdbt_spin) may be seen during the execution when there are large number of databases( > 128) in ASE. |
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. |
822898 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 's_estmt_pssinit' together with a stack trace may be reported in the SAP ASE error log, sometimes following a 701 error, "There is not enough procedure cache to run this procedure ...". See KBA 2358848. |
823355 | CIS operation may fail with a syntax error near '-' if the ASE has not been rebooted in a long time. See KBA 2987109 |
824239 | In rare circumstances, a session that is executing 'sp_spaceused < table-name > ' may be put to sleep while an online utility on the same table is in progress. The call stack of the hanging session may report the modules 'des_do_get', 'des__in_use_error' and 'pg_getpagecounts'. See KBA 3112838. |
824449 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'pci_tpminvoke_longfunction' together with a stack trace which includes the modules 'objVerifySerializability' and 'BRIDGEapi_DeleteGlobalRef' may be reported in the SAP ASE error log when inserting rows with Java object to a table with Java ADT column types. |
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. |
826480 | The global variable @@triggerstatus is introduced in SAP Adaptive Server. It returns the value for the action that has caused a trigger to be executed that is either 1 when the trigger was executed by an INSERT statement, 2 by an UPDATE statement, 3 by a DELETE statement, or 0 otherwise. |
826612 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'ptn__get_field' together with a stacktrace which includes the module 'mda_populate_monOpenObjectActivity' may be reported in the SAP ASE error log when querying the MDA table monOpenObjectActivity after running DROP INDEX WITH NOWAIT. See KBA 3205143. |
826720 | Improve error message 9829 "Compressed data row 0xxxxxxxxx in objid 1111111111, dbid 4 is corrupted." by including the page number the row is on. |
826737 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memtextlen' together with a stacktrace which includes the modules 'inserttext' and 'insert_all' may be reported in the SAP ASE error log when multiple DMLs on a table that has LOB columns are executed. |
826815 | Feature enhancement to provide ability to read out data from table with corruption. See KBA 3358688. |
826826 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeSendRow::sendRowToClient' together with a stack trace which includes the modules 'LeEmitSndOp' and 'exec_lava' may be reported in the SAP ASE error log during the execution of a SELECT query. To enable the diagnostic information for errors reported while sending LOB data to the client, Adaptive Server can be started with trace flag 7121. To disable the fix which handles NULL values for in-row LOB columns, Adaptive Server can be started with trace flag 7123. See KBA 2869968. |
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 |
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. |
827511 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'prSQLTEXT' together with a stack trace which includes the module 'exec_dbcc' may be reported in the SAP ASE error log when DBCC SQLTEXT( < spid-value > ) is run against an active session. See KBA 3282789. |
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. |
827679 | Enhanced diagnostics for the message: "usrfill: vsn xx kpid xxxx read not posted due to external attention" by including client information, socket flags and buffer status. This message is logged in the SAP ASE error log when a client abruptly disconnects. |
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. |
827916 | Enhance the 'shutdown' command to supply a user defined message to the SAP ASE log during shutdown. See KBA 3323967. |
828109 | Feature enhancement to have the 1621 error message specify the ip address and port that sent the incorrect packet. See KBA 1973518. |
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. |
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. |
828246 | Setting a BigDecimal type in prepared insert statement causes the scale part lost when executing the java code through JDBC dispatched in ASE server PCI/JVM. However directly executing the same code in standard JDBC client code can insert the value correctly. |
828331 | When server configuration 'enable granular permissions' is set to 1, the message "Permission related internal error was encountered. Unable to continue execution." is reported while executing command DBCC PRINTOLOG. |
828414 | The NV Cache section in sp_sysmon will print empty information even when an nvcache is not configured. See KBA 3377053. |
828504 | Error 707 "System error detected during attempt to free memory at address 0x2ac03e164a20" |
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. |
828690 | A 249 error, "Syntax error during implicit conversion of CHAR value < > to a INT field.", may be reported by SAP ASE when a SELECT query is run using a nested parameterized view. |
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. |
829057 | Enhancement request to suppress "Cannot read, host process disconnected" and "Cannot send, host process disconnected" messages to the SAP ASE Errorlog under Traceflag 1675. See KBA 3428798. |
829062 | SAP ASE diagserver may report an assertion failure, "Assertion ((rgadmlobp- > admlob_oldcolscopied + rgadmlobp- > admlob_oldcolsdropped) == rgadmlobp- > admlob_numoldcols) failed in < path > /generic/source/sequencer/pre_alttab.c" when a LOB column is changed from "materialized" to "not materialized" |
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. |
829138 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'a_remapqblockvar' followed by a stack trace that includes the modules 'tree_traverse_roots', 'tree_traverse_roots' and 'ApPlan::ApInit', may be reported in the SAP ASE error log when a complex join query that involves at least 6 tables and outer joins is run. See KBA 3476885. |
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. |
829173 | The message "Sybmon encountered signal 11 at address os_get_prev_stk_desc + < offset > " may be reported when "profile" is run in sybmon on ibmaix64 platform. |
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 | Introduce new stored procedure "sp_helpaltermessage" in SAP ASE to report the list of messages that are altered using sp_altermessage "WITH_LOG" or "WITH_STACK" option. 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 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. |
829340 | In rare circumstances, successive calls to getdate() built-in in SAP Adaptive Server may return a datetime value which is older than the previously returned datetime value. See KBA 3468430. |
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. |
829343 | Provide monDeviceIO performance information to sp_sysmon Disk I/O Management section. |
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. |
829351 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'bt__formsplitlogrec' together with a stack trace may be reported in the SAP ASE error log when SELECT INTO is executed. See KBA 3464190. |
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. |
829476 | Audit event 39 may continue to be inserted into the sysaudits table for each trigger execution after turning off auditing for a specific login. See KBA 3547769. |
829481 | The message "ssl_nrpacket: vsn xxx kpid xxxxxx read returning -4 state 1" is reported in the SAP ASE error log when ASE performs a network receive on an SSL client that has disconnected abruptly. See KBA 3478645. |
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. See KBA 3531173. |
829543 | The 'setuphadr' utility has been improved to utilize only the user-installed version of OpenSSL. |
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 See 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. See KBA 3542775. |
829608 | When TRUNCATE TABLE < table-name > PARTITION < partition-name > is executed, SAP ASE will rebuild the global indexes of the given table, even if the partition being truncated is empty. Additionally, the execution of DUMP TRANSACTION may be blocked for the duration of the global indexes rebuild. See KBA 3498667. |
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. |
829628 | The message, "Current process infected with 11 (SIGSEGV)", in the module ‘sqt_releases_ssql’ together with a stack trace which includes the modules ‘tdsrecv__dyndealloc’ and ‘tdsrecv_dynamic’ may be reported in the SAP ASE error log when the statement cache is full. See KBA 3464047. |
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. |
829656 | The message, "Current process infected with signal 11 (SIGSEGV)", either in the module 'memfree' or 'sequencer' may be reported in the SAP ASE error log when running sp_showplan against a running spid. See KBA 3426914. |
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. See KBA 3531166. |
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. See KBA 3542798. |
829799 | Two SAP Adaptive Servers can boot up on same port in windows system. See KBA 3519054 |
829803 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'plc__flush' together with a stack trace which includes the modules 'xls_pre_alloc_numclrs', 'xact_begin' and 'crt_main' may be reported in the SAP ASE error log when a stored procedure is run. |
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. |
829856 | SAP ASE sybmigrate might run into hang with repeatedly printing "still waiting at sync point < num > / < totalnum > " in the log file during the migration phase. |
829983 | The MDA table monSQLRepMisses may indicate Configuration instead of QueryLimitation as the cause for some queries which are not eligible for SQL statement replication. |
829999 | A 4402 error, “Infinite loop in view definition. Cannot resolve the view definitions in the query to the underlying tables.”, may be reported by SAP ASE when querying a view that references a SQL Function that is using a TUDF (Table User Defined Function) and before the query execution the SQL Function has been recreated. |
830005 | Limit 'create database' and 'drop database' to only saptu when 'cloudservice' is enabled. |
830014 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeRun' together with a stack trace may be reported in the SAP ASE error log when querying a view that includes table-valued UDFs and performs a hash union distinct join. See KBA 3542784. |
830015 | In rare circumstances, SAP Backup Server may run out of server connections when a client fails to connect to it and the two messages, "Backup Server: 1.28.2. < state-value > : Open Server routine srv_senddone failed. See Backup Server error log for additional information.", with state values 49 and 51 are reported in the Backup Server error log. See KBA 3542841. |
830030 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'xls_pre_alloc_numclrs' together with a stack trace which includes the modules 'lrd_log_run_dealloc', 'dmpx_truncatemain' and 'ckptproc' may be reported in the SAP ASE error log when the checkpoint task does checkpoint a database. See KBA 3535124. |
830034 | Enable sequence when "functionality group" is ON |
830039 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 's_recrtproc' together with a stack trace which includes the modules 's_recompile' and 's_renormalize' may be reported in the SAP ASE error log when a stored procedure is executed WITH RENORMALIZE option. See KBA 3577953. |
830079 | When replicating from SAP ASE to SAP HANA, ASE Rep Agent may terminate abnormally with an error 9210 state 30, "RepAgent( < dbid > ): Fatal error from CT-Lib. (CT-Lib command = usctresults, return status = 4047).". See KBA 3540554. |
830117 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'xact_rollback' together with a stack trace which includes the module 'set_repdb_off' may be reported in the SAP ASE error log when the command SP_REPTOSTANDBY < database-name > , 'NONE' is executed on an active system and is victim of a deadlock. See KBA 3545082. |
830141 | sp_help ' < object_name > ' may report an incorrect read_only value after ASE is upgraded or the database is loaded from an older version than ASE 16.0 SP02. See KBA 3392168. |
830155 | SAP Adaptive Server trace flag 17015 is extended at two more places to print the diagnostics of an alarm if it is freed again. See KBA 3189250. |
830185 | In rare circumstances, a 1265 error with state 1, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr= < lock-address > , lrmagic=f).", may be reported in the SAP ASE error log during the execution of COMMIT TRANSACTION. See KBA 3549578. |
830195 | In rare circumstances, a 12858 error, "Update to sysobjects row for database ' < database-name > ' ( < database-id > ), object 'rs_ticket_history' ( < object-id > ) failed.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'dpdb_main', 'checkpoint’, des_idtflush' and 'obj_updrow' when DUMP DATABASE is run on an HADR system and concurrently table 'rs_ticket_history' is being dropped. See KBA 3564105. |
830209 | The default value for optimize temp table resolution depends on the value to which enable functionality group is set. If you set enable functionality group to: 0 – the default value for optimize temp table resolution is 0. 1 – the default value for optimize temp table resolution is 1. However, if you set optimize temp table resolution to 1, it uses a value of 1 regardless of what you set enable functionality group to. |
830223 | show_cached_plan_in_xml() doesn't print the compile and exec parameters when using server side cursors. |
830243 | When joining proxy tables and local tables with WHERE conditions that include IN and OR clauses on the same column of one of the proxy tables, the query may return fewer rows than expected. See KBA 3555615. |
830253 | In some circumstances, incorrect data may be inserted in a local table when SELECT INTO EXISTING is executed and the data being inserted is not matching the datatype of the target local table column. See KBA 3269984. |
830254 | An error 10364, "Permission denied.", is reported when a user other than the dbo and without sa_role or replication_role, executes the system stored procedure SP_SETREPTABLE or SP_SETREPPROC without any parameter in order to list the replicated objects in the current database. See KBA 3556852. |
830258 | Infected with SIG 11 at pss_init() that was preceded by Error 941 State 1 and Error 6103 State 1, after Error 8233 state 1 was seen and PSS was reused and making ASE unresponsive. See KBA 3559053. |
830310 | NFR: Setuphadr allows user to disable rma_admin password expiration. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Windows on x64 64bit
Product
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.