2632245 - Targeted CR List for ASE 16.0 SP02 PL07 HF1

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 SP02 PL07 HF1. 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
760523	The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sqt_deallocate' together with a stack trace which includes the modules 'lwp_create' and 's_cache_stmt' may be reported in the SAP ASE error log 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.", is reported when a SELECT query is executed. See KBA 2496908.
802335	In some cases, intelligent index scan may cause low LIO estimate with a poor index being chosen for the plan, resulting in poor performance.
804856	In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of < wrong_length > . Maximum allowed length is < max_length > ", may be reported in the SAP ASE error log when page compression is used. See KBA 2595171.
805275	SAP ASE server will disable ASE_JAVA functionality if the jvm.wl file is missing, and the message 10762 together with the detailed reason will be reported in SAP ASE error log. This is to improve the default security should the jvm.wl authorization file be accidentally removed.
808794	Improvements have been made to audit logging.
810312	A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > ." may be reported in the SAP ASE error log during LOAD TRANSACTION if the dump contains log records for index compressed pages as a result of REORG REBUILD INDEX execution. See KBA 2395755
810485	The output of SELECT SHOW_CACHED_PLAN_IN_XML garbles the values of the bind parameters if the parameter count is more than 35. See KBA 2593765.
810688	A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be reported during the execution of a query that is using a fact table hint and no legal execution plan is found.
810757	A predicate with multiple columns, such as ((c1,c2) > (x,y)), can be incorrectly qualified as a criteria for partition elimination. This may lead to incorrect results. See KBA 2345886.
810799	In rare circumstances when DDL replication is enabled, some DDL commands may not be replicated from the primary SAP ASE when the default data cache is under configured and lots of concurrent replication activity is taking place.
811606	A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, involving updates to rows containing In-row LOB columns.
811716	A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be raised when a query that includes a UNION VIEW with LIMIT clause and without an OFFSET clause is executed. See KBA 2556253.
811825	Wrong results may be returned from a query that has complex OR clauses. See KBA 2563459 and SAP Note 2596598.
812054	The message, "Page Verification Error: Adaptive Server accessed a row that has an illegal length of..." followed by a crash of the backup server emulator process with the message, "Emulator interprocess communication failed with error state = 14, error code=32, system message=Broken pipe.", may be reported in the Backup Server error log when DUMP DATABASE is run if a database dump is taken using a dump configuration that includes the option WITH VERIFY=FULL. See KBA 2595456.
812309	A 3624 error, "Truncation error occurred", may be reported when executing INSERT involving NUMERIC datatypes and the statement cache is enabled. This is due to CR 805165 which addressed a spinlock contention performance scenario on the statement cache. The fix introduced by CR 805165 is now disabled by default. CR 805165 can be enabled using the run time trace flag 11013.
812311	Increasing the configuration option 'user log cache' will significantly increase the SAP ASE memory consumption unexpectedly. See KBA 2570113.
812360	A 12034 error, "Collection of monitoring data for table ' < MDA Table > ' failed due to insufficient memory. Retry when there is less load, or fewer users, on the server. < num_row > rows were not returned because < number_byte > bytes of memory could not be allocated.", may be reported when querying some MDA tables in a heavy-loaded system.
812840	A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, when compression is enabled.
812955	Even after the successful application of the fact_table_hint, optimizer constructed the final plan using the subplan generated for compatibility mode.
813529	Handling of default values for global temporary tables is not correct. See KBA 2608519.
813536	A 267 error, "Object < name > cannot be found" in the module 'open_globaltt', may be reported in the SAP ASE error log when running ONLINE DATABASE after having loaded a database dump. See KBA 2607240.
813852	The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'index_compress_page_with_prefix' together with a stack trace which includes the modules 'redo_bt_rebldleafs' and 'recovery' may be reported in the SAP ASE error log during the recovery of a transaction log dump which contains index compressed operations. See KBA 2614971.
813886	Under rare circumstances, a connection may hang after receiving a cancel request from the client. See KBA 2633664.
813998	The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qualpage' followed by a stack trace that includes the modules 'apl__startscan' and 'startptnscan', may be reported in the SAP ASE error log when a JDBC client executes queries with property DYNAMIC_PREPARE set to true and the parameters "abstract plan load" and "enable literal autoparam" are enabled in SAP ASE. See KBA 2617753.
814357	A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > ", may be reported when executing a query against the monMemoryUsage MDA table.
814462	If the option 'enable dump history' is enabled and the DUMP or LOAD command uses the syb_tsm library with more that one stripe, the stripe name stored in the dump history file for each of the stripes will be the result of concatenating the previous stripe name. When the length of this is greater than 255 bytes, a 11076 error, "The name '' is too long. Maximum length is 255." will be reported, although the dump itself is successful. See KBA 2629866.
814501	When Rep Agent is configured for stream replication in sync or near-sync mode and a stream mode switch to or from async takes place while a DDL command is altering the schema of a table, Rep Agent may use an inconsistent schema of the table, causing the SRS DSI to shut down with an error from SAP ASE such as a 207 error, "Invalid column name ' < column_name > '".
815608	In rare circumstances, the message, "Current process infected with 11 (SIGSEGV)" in the module 'dol__index_decompress_row' together with a stack trace which includes the modules 'bulk_fast_idxupdate' and 'reorg_defrag', may be reported in the SAP ASE error log when REORG DEFRAG is run. See SAP Note 2665483.
815844	When SAP ASE encounters a secondary signal violation while dealing with a primary signal violation, it makes the process that hit these signal violations zombie. SAP ASE will now shut down implicitly instead and the message, "UNHANDLED EXCEPTION: signal in signal handler", will be reported in the SAP ASE error log. When required it is possible to retain the zombie process behavior by starting SAP ASE with the trace flag 2917 or enabling it at run time using DBCC TRACEON.

Environment

AIX 64bit
HP-UX on IA64 64bit
Linux on Power 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 SP02 PL07 HF1, ASE SP02 PL07 HF1, SP02 PL07 HF1, Adaptive Server Enterprise, Fix, Patch, Error, Bug, HF01 , 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.