/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.1 SP00 PL02. 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 |
|---|---|
| 693148 | If master datbase is dumped and there are incomplete transactions during dump, when load of master database is executed, the incomplete transactions are not rolled back. |
| 749724 | object_status "contains compressed data" remains after table is truncated |
| 826610 | The message, "Page Verification Error: Page mismatch. Page < page-number-#1 > contains < page-number-#2 > in page header.", may be reported by Backup Server during DUMP DATABASE when an unallocated page is read and the page ID in the page header doesn't match the page number. See KBA 3147603. |
| 827002 | A 15960 error, "The compression information of LOB started with page < > does not match that found in system catalog.", may be reported in the SAP ASE HADR secondary site when dbcc checktable is run. See SAP KBA 3335392. |
| 827384 | A 804 error, "Unable to find buffer < > from cache 'default data cache' holding logical page < > in sdes < > kept buffer pool for object < > .", may be reported in the SAP ASE error log when REORG REBUILD is run. See KBA 3271126. |
| 828068 | In rare circumstances, a 702 error, a 724 error or the message "current process infected with 11" together with a stack trace which includes the modules 'treecpynames', 'cpynamelist' and 'vu_viewcopy' may be reported in the SAP ASE error log if a query involving views including derived tables with UNION/UNION ALL runs. See KBA 3339850. |
| 828332 | execute as (caller/owner) clause is added for trigger creation. Existing trigger creation(without any clause) and execution behaviour is same as earlier |
| 829054 | When concurrent sessions are executing INSERT and UPDATE commands on a Data row Only Locked table (DOL) while a SELECT query performs a table scan at isolation level READ COMMITTED it may sometimes fail to return qualifying rows. See KBA 3430799. |
| 829333 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'vu_getviewdefn' together with a stack trace may be reported in the SAP ASE error log when using a table user defined function in the FROM clause of a query. See KBA 3464211. |
| 829509 | In rare circumstances, a 7452 error, "Failed to find specified threshold in threshold cache on instance 1 for database < database name > ( < database id > ), segment < segment number > , free space < > . Use 'dbcc thresholds' to see the threshold cache contents.", may be reported in the SAP ASE error log. After this error, dump database may fail with a 1166 error, "You cannot execute the command 'DUMP' on database < database name > because it was created with asynchronous initialization and it has not been fully initialized. Retry the command later.". See KBA 3484901. |
| 830177 | A new column, OptimizationTime, is added into monCachedProcedures in SAP ASE to report the compilation time for a stored procedure. |
| 830194 | The message, “Current process infected with signal 11 (SIGSEGV)”, in the module ‘ubffreef’ together with a stack trace which includes the modules ‘LePlanRelease’ and ‘s_result_const_memfree’, may be reported in the SAP ASE error log during the execution of a query in parallel mode. See KBA 3550356. |
| 830375 | In rare circumstances, a 8210 error, "Duplicate of work table descriptor found in the id hash table for temporary object < a negative value > ” together with stack trace, may be reported mistakenly by SAP ASE when execution a special query. See KBA 3577504. |
| 830709 | Infected with 11 in bt__insert_into_leaf. See KBA 3603341. |
| 830775 | SELECT INTO with TOP rowcount are ignored with SQLDML - KBA 3610066 |
| 831033 | A 12308 error, "Internal error: Invalid row id (Row < row > , Page < page > ) encountered in the table ' < table > ' in database ' < database > '.", may be reported in the SAP ASE error log after a REORG REBUILD WITH ONLINE command has been executed on a large DOL table with page compression enabled, when the housekeeper garbage collection task processes a page that was deallocated by the REORG operation before post-commit processing has completed. See SAP note 3636010 |
| 831150 | In rare circumstances, 700 series errors and/or random SIGSEGVs may be reported in the SAP ASE error log during the compilation or execution phase of a stored procedure execution. See KBA 3649123. |
| 831199 | Enabling SSL without setting ssl_ca_file left the value empty, allowed the backupserver to boot, but caused dump and load to fail because the dataserver could not establish a secure connection without a valid CA file. |
| 831248 | In rare circumstances, a user task in SAP ASE may indefinitely sleep in the module 'plc__lock' while performing a BULK INSERT operation. See KBA 3658883. |
| 831279 | Stack guardword corrupted after error 1204 with GP turned on. |
| 831284 | Update sp_helpview and sp_help for all options to expose object status information in the tabular format. |
| 831296 | The stored procedure sp_spaceused may report space usage values as 0 MB for small tables and indexes, even though they occupy disk space. Additionally, the stored procedure sp_helpdb reports space usage with MB option in whole integers. |
| 831317 | Infected with Signal 11 (SIGSEGV) error is reported in function lddb__stat_translate() while performing a LOAD DATABASE. See KBA 3675200. |
| 831389 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'proc_replace' together with a stack trace which includes the modules 'proc_replace' and 's_reinstallProcTree' may be reported in the SAP ASE error log when a view is undergoing runtime upgrade. See KBA 3691212. |
| 831397 | High spinlock contention on the SSQLCACHE_SPIN[i] is observed when there is high turnover in the statement cache pool. See KBA 3677140. |
| 831415 | sp_passwordpolicy 'list', 'allow password downgrade' shows 'NULL' value out of master database other than the expected '0' value in the master database. Please see KBA 3679860. |
| 831417 | 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 a DUMP DATABASE command execution to be released. See KBA 3678625. |
| 831418 | Error 691 and stack trace in a trigger execution after adding new column in the table and trigger. (KBA 3678587) |
| 831434 | A 12213 error, "Resource Governor lock count limit ( < limit > ) exceeded. Transaction has been aborted.", may be reported when running large INSERT statements while the configuration option allow statement rollback is enabled and a Resource Governor lock limit is exceeded. |
| 831480 | ASE_ASM License is required to enable JWT feature. |
| 831557 | In rare circumstances, Rep Agent may skip a TEXTINSERT log record. When this occurs in an HADR setup, the SRS Capture thread terminates with an error #74056 for inconsistent LOB block length. See KBA 3115211. |
| 831566 | A 11060 error, "This statement has exceeded the maximum number of recompilations (20). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported by SAP ASE when a dynamic prepared statement which uses table variables in a INSERT-SELECT statement is executed. See KBA 3696213. |
| 831569 | The read_only table attribute cannot be modified using the sp_chgattribute system stored procedure when the objname parameter follows the < username > . < tablename > format. |
| 831606 | A 12308 error, "No shared memory dump condition was found for condition type %s and value 0.", may be reported even with server crash while running sp_shmdumpconfig on SAP ASE. |
| 831638 | On IBMAIX platform, an 'Error: 9829'(state maybe 14, 17 or 23, with or without stack trace) which is like 'Compressed data row xxx in objid xxx, dbid xxx, page xxx is corrupted.' may be reported in the SAP ASE error log during decompressing. (KBA 3722191) |
| 831665 | In rare circumstances, timeslice error in the module 'pchk_release_retry_resource' together with a stack trace may be reported in the SAP ASE error log. See KBA 3722199. |
| 831683 | In rare circumstances, the message, "timeslice < negative-value > , current process infected", in the module 'write' together with a stack trace which includes the module 'shm_update_errorlog' may be reported in the SAP ASE error log while collecting a shared memory dump. See KBA 3704060. |
| 831699 | Infected with Signal 11 (SIGSEGV) in locklogin() while executing DROP LOGIN. See KBA 3709058. |
| 831703 | In rare circumstances, dbcc proc_cache(free_unused) can cause a timeslice in function freeprocs that crashes server ASE due to rprocmgr_spin spinlock. See KBA 3707833. |
| 831716 | Error 702, "Memory request for xxxxx bytes exceeds the size of single page of 16384 bytes.", may be reported when "sql statement replication" is enabled. See KBA 3707926. |
| 831717 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 's_cleanframe' together with a stack trace may be reported in the SAP ASE error log during the VEH recovery from Optimize and execution phases. |
| 831733 | When a query qualifies for a simplified fast‑execution path, such as certain UNION or simple queries, it may not be correctly recognized by ASE, resulting in unexpected performance degradation. See KBA 3711527. |
| 831789 | Add new config option and new table attribute to ignore the rows during trigger execution which are ignored due to 'ignore_dup_key' index property. |
| 831837 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'checkverify' and 'collocate__impl' may be reported in the SAP ASE error log when checkverify after checkstorage. See KBA 3726138. |
| 831858 | In rare circumstances a SIGSEGV (Signal 11) in prXITEM() can happen when DBCC SHOWRECOVERY is executed during ongoing recovery processing. |
| 831866 | In an HADR setup, some transactions may erroneously not get replicated to the secondary site and 9416 error, "Rep Agent on database ' < database-name > ' switched from mode 'sync' to mode 'async' because timer on commit expired", may be reported frequently by SAP ASE Rep Agent when the primary ASE is restarted after a crash or shutdown with nowait. See SAP Note 3729021. |
| 831879 | Infected with signal 11 (SIGSEGV) at address in idxpi_memfree(). See KBA 3734475. |
| 831882 | While loading a database dump, a 631 error with state 3 is raised with the message "The length of xxx passed to delete row routine for the row at offset 0 is incorrect on the following page of database ' < database name > ': Page pointer = < address > , pageno = < page number > , status = < address > , ptnid = < partition ID > , indexid = 0, level = 0, pnextrno = 0. The expected row length is < length > . The offset should be no greater than < offset value > ." in the recovery redo phase. See KBA 3729693. |
| 831897 | Following a 1204 error, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'setuser' together with a stack trace may be reported in the SAP ASE error log. See KBA 3733477. |
| 831914 | A 247 error, " Arithmetic overflow during explicit conversion of DATE value 'Dec 17 1899' to a SMALLDATETIME field .", may be reported in the SAP ASE error log during executing a parallel SELECT query with the getdate() and convert() built-in functions. See KBA 3735305. |
| 831948 | An 10350 error, "Permission related internal error was encountered. Unable to continue execution", may be reported if using "sp_configure 'configuration file'" to update configuration file with GP enabled. |
| 831971 | The Secondary Truncation Point of all the replicated databases of an HADR system may stop moving. See KBA 3742840. |
| 832001 | The stored procedure sp_securityprofile incorrectly reports authenticate with ANY instead of JWT for JWT configurations. See KBA 3745299. |
| 832002 | The command DUMP TRANSACTION hangs when executed on the primary ASE of an HADR system. Rep Agent eventually raises an error 9416, "Rep Agent on database ' < database-name > ' switched from mode 'sync' to mode 'async' because timer on commit expired". See KBA 3762374 |
| 832024 | The upgrade or preupgrade utility will fail to connect if the length of the sa password is 30 bytes long. |
| 832027 | The hashkey value stored for sysquerymetrics does not match the hashkey generated in monCachedStatement for a cached statement when 'set plan dump' is enabled and trace flag 11032 is enabled. See KBA 3746812. |
| 832057 | In rare circumstances, timeslice error may be encountered with a stack trace which includes the modules 'lddb__unscr_phys_page' reported in the SAP ASE error log when performing a cross-platform load of a dump containing unallocated encrypted SYSLOG pages from the source database. |
| 832079 | Infected with 11 at LeHashOp::_LeOpNext with allrows_dss + merge_join |
| 832111 | Spinlock Contention on fglockspins may be high under heavy load when server configuration 'enable granular permissions' is enabled in the ASE server. See SAP note 3789757. |
| 832131 | SAP ASE Workload Analyzer Command Line Utility (WLACLIUtil) may not refresh the analysis progress for long time when a capture or replay is being analyzed. |
| 832133 | SAP ASE Workload Analyzer Command Line Utility (WLACLIUtil) may run slowly when the analysis progress is close to or at 80%. |
| 832162 | Hardening of connections across ssl and non ssl ports. |
| 832174 | Under rare circumstances, Error 10331, "Permission denied, database master, owner dbo. You need the following permission(s) to run this command: MANAGE SECURITY CONFIGURATION." is reported during master database recovery and granular permissions is enabled. See KBA 3764901. |
| 832182 | A 245 error, "Domain error during implicit conversion of DECIMAL value '' to a DECIMAL field," may be reported in the SAP ASE error log during the execution of a SELECT query when a DECIMAL parameter is required in a parameterized view. |
| 832207 | A 12001 error, "Data collection failed: Command 'netstat -ea' failed (Exit code 1): Cannot run netstat - execvpe failed (ENOENT - No such file or directory)", may be reported from SAP ASE Sybdiag utility while it is used to collect osdata with "-Tosdata" option on SuSE 15 or above versions. |
| 832211 | A 14005 error, "Executing Query Error: Error occurred while executing the SQL query statement 'select * from master..monLicense'. The message returned was 'You must have any of the following role(s) to execute this command/procedure: 'sapmon_role' . Please contact a user with the appropriate role for help.'", may be reported from SAP ASE Sybdiag utility while it is used to collect ASE server data with "-Tasecore", "-Taseadd" or "-Taseopt" options on 16.1 SP00 PL02 or above versions. |
| 832252 | SAP ASE Workload Analyzer Command Line Utility (WLACLIUtil) may run slow when analyzing a capture or replay that contains many big queries. |
| 832272 | A new option, "-Q", is added to SAP ASE Sybdiag utility to suppress the console log output. |
| 832297 | SAP ASE Sybdiag utility may not report os_iostat data correctly on Linux servers which kernel is 4.x (like SuSE 12.5, RHEL 7.x/8.x etc.) |
| 832398 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'mbkt_do_alloc' together with a stack trace which includes the modules 'form_and_send_audit_syslog' and 'rvm__audit_table_view_access' may be reported in the SAP ASE error log when a stored procedure that has parameters is executed while auditing is enabled and the audit trail type is set to 'syslog'. This may result in an implicit shutdown of SAP Adaptive Server. See SAP note 3807887 |
Read more...
Environment
- AIX 64bit
- Linux on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.1
Keywords
KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , BC-DB-SYB , Business Suite 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/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)