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.1 SP01 PL00. 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 |
|---|---|
| 767164 | If SQL statement replication is enabled on the primary database and rows on a table are updated by using rand()/rand2()/newid()/password_random() builtin functions, replicated data may appear out of sync. |
| 821213 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'com__subexctnumetochar' together with a stack trace may be reported in the SAP ASE error log when an out-of-range numeric or decimal value is set as a parameter of a dynamic prepared statement in a Java program. See KBA 2900703. |
| 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 KBA 3335392. |
| 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. |
| 830950 | SAP Adaptive Server Enterprise 16.1 installer fails to configure Historical Monitoring Data Repository with a 701 error with the message "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." during enabling BALDR. |
| 831124 | The row_count built-in function will return incorrect values for compressed and uncompressed page counts after running reorg defrag. |
| 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. |
| 831321 | A stack overflow and subsequent crash due to stack corruption are observed when executing a dynamic prepared statement with numeric input parameters containing out-of-range values. |
| 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. |
| 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. |
| 831665 | In rare circumstances, timeslice error in the module 'check storage' together with a stack trace may be reported in the SAP ASE error log. See KBA 1336992. |
| 831685 | The runtime JRE of SAP ASE Sybdiag is migrated from SAPJRE8 to SapMachine 21. |
| 831691 | The runtime JRE of SAP ASE Sybmigrate is migrated from SAPJRE8 to SapMachine 21. |
| 831692 | The runtime JRE of SAP ASE DDLGen is migrated from SAPJRE8 to SapMachine 21. |
| 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. |
Read more...
Environment
- AIX 64bit
- Linux on x86 64 64bit
- Windows on x64 64bit
Product
Keywords
CR, CR List, ASE 16.1,SP01 PL00, Adaptive Server Enterprise, Fix, Patch, Error, Bug , 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.
SAP Knowledge Base Article - Preview