2502605 - Targeted CR List for ASE 16.0 SP03 PL01 | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2502605 - Targeted CR List for ASE 16.0 SP03 PL01

Symptom

The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in future Adaptive Server Enterprise (ASE) EBF/SP or PL releases. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the service.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 NumberDescription
799194 An 806 error, "Could not find virtual page for logical page < > in database < > " may be reported after loading a database dump that is followed by one or more transaction dumps while trying to access a page, if the database was shrunk before taking the database dump or a transaction dump followed by a database extension that was captured in a following transaction dump.
807849 SAP ASE may incur a segmentation fault in ksnetctlrAddSockEvent() when new client connections are made during shutdown with nowait.
808026 In rare circumstances a 623 error, "Attempt to move memory with an incorrect length of < negative_value > . Maximum allowed length is < value > ." may be reported in the SAP ASE error log while accessing the system table sysimrslogs.
808283 An attempt to establish an SSL connection using the JDBC driver (jConnect) with JRE 1.6.0_29 or later hangs or fails.
808326 Descending sorting doesn't work correctly in a query containing both an ORDER BY clause and a LIMIT clause.
808489 A segmentation violation followed by a stack trace that includes the module 'am_count_bits_in_dmap' may be reported in the SAP ASE error log when loading a database dump on a database that is marked as suspect if the database is bigger than 64G in a 2K server, 128G in a 4K server, 256G in a 8K server and 512G in a 16K server. See KBA 2490688.
808553 RC4 and 3DES are removed from the SSL default cipher suites list.
808636 KBA2483958 A 716 error, "Unable to allocate memory of size < nnnnn > bytes from the 'compression info' pool", followed by a 2628 error, "In database < dbname > , page < page_num > is linked forward to page < page_num1 > , but that page is linked backward to page < page_num2 > . Please report this internal error to SAP Technical Support", may be reported in the SAP ASE error log when inserting into a table with compressed indexes. .
808666 The monDeviceSpaceUsage table might return incorrect data when it is queried concurrently from multiple sessions. In rare cases, the Global Fragment Pool might be corrupted. Customer may see signal 11 error in kbfalloc() or kbffree().
808683 When RepAgent is configured for stream replication, it may terminate abnormally with error 9254 while a DDL command is executed during SUM upgrade.
808720 Under rare circumstances, a 12343 error, "Cannot serialize the transaction for the scan on table < table_name > in database < db_name > , as a phantom row has been inserted in the result set, or some changes have occurred to the rows in the result set since the start of the transaction", may be reported when a SELECT FOR UDPATE query that contains ORDER BY or JOIN clauses, is executed with transaction snapshot isolation on an MVCC or On-disk MVCC enabled table.
808729 Numeric conversion results from RPC call may be incorrect.
808785 On Linux, Solaris and HP platforms, in rare circumstances, ASE may unexpectedly terminate a SSL connection.
808812 The error, "Command has been aborted", may be reported during an INSERT query after a clustered index with DESC option is first created on an empty round-robin partitioned table.
808883 A 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database..." may be reported when there is a long running transaction that causes DUMP TRANSACTION to not truncate any log pages and DUMP TRANSACTION is run a high number of times.
808940 SSL certificate load fails with error 'decryption of password failed' during server boot when service key syb_extpasswdkey exists
808941 In rare circumstances, the message, "Invalid column name 'sysstat5'", may be reported during downgrade of a database from 16.0 SP03 or after.
808961 A 952 error, "Database < dbname > cannot be opened because the system index descriptor for table ID 4 cannot be installed.", may be reported when booting a server with 4K page size downgraded from 16.0 SP03.
809006 A 12356 error, "MOUNT DATABASE failed as required temporary database '' or row storage cache '' is not present or is already in use by some other database." may be raised when executing MOUNT DATABASE command for a database having IMRS CACHE and VERSION STORAGE enabled.
809043 A 16878 error, "The limit specified in a LIMIT clause may not be negative", may be reported during the execution of a dynamic prepared statement with LIMIT clause and table-valued user defined function.
809050 On Unix platforms, CTRL+C of ASE server results in segmentation fault and may need 'kill -9 < pid > ' to be issued at the OS prompt to shutdown the ASE.
809062 Performance degradation may be observed due to an increase in SSQL_CACHESPIN spinlocks.
809093 The error message "Logical page < page_num > is not in the given database map" will be printed in the SAP Backupserver error log followed by a stack trace in the SAP ASE error log including the module 'dmpld_send_dbdam_runlist' at DUMP DATABASE time if the database option 'allow incremental dumps' is enabled and SAP ASE failed to allocate the required number of pages to store the bitmap of changed pages.
809173 A 14601 error, "Invalid length '256' found for anchor type '0'. Sysanchors page '24', offset '712'." will be reported when doing a crossed platform database load from a 16.0 SP02 database dump into a 16.0 SP03 ASE installation.
809180 The installSQLScriptProc script is missing and not included in the SAP ASE installation package.
809210 A 11060 error, "This statement has exceeded the maximum number of recompilations (10). This indicates an internal error." may be reported when executing a SELECT query in read uncommitted mode which results in a nested execution of User Defined Functions (UDF) that can return a table variable.
809306 In rare circumstances, the RepAgent may fail to shut down gracefully when the synchronous replication mode is enabled and the Replication Server is already stopped.
809308 A 941 error, "Illegal database context operation", will be reported when LOAD DATABASE of master database is run.
809353 An Arithmetic Overflow error can be seen when using sp_configure " < param_name > ", 0, " < value > {K|M|G}" instead of number of pages.
809358 The oldest inserted transaction in a database may not be moved even if all the rows of the transaction are deleted, after a SELECT column_list FROM SYSIMRSLOGSHOLD that affects more than one database.
809371 A dynamic prepared statement with LIMIT clause may return wrong result with limit value passed as a variable and executed multiple times for different values.
809392 The message, "Current process infected with 11" in the module 'apl__startscan' together with a stack trace which includes the modules 'imrslogrec_redo_log' and 'lddb_main', may be reported in the SAP ASE error log when LOAD DATABASE is run for a database dump that contains IMRS data.
809456 A 806 error, "Could not find virtual page for logical page < page# > in database < dbid > ", may be reported in the SAP ASE error log when running DBCC CHECKTABLE on a Data Only Locked table following an impolite SAP ASE shutdown while rows were packed in an IMRS database.
809624 The message, "Current process infected with 11" in the module 'apl__startscan' together with a stack trace which includes the modules 'imrslogrec_redo_log' and 'lddb_main', may be reported in the SAP ASE error log when LOAD DATABASE is run for a database dump that contains IMRS data and stream replication is enabled.
809638 Sometimes, an SAP ASE spid hangs in the module 'prepprev' after rollback due to error 2601 (duplicate key error).
809840 The message, "Current process infected with 11" in the module 'ra__health_check' together with a stack trace which includes the modules 'rep_drain_log' and 'hadr_admin', may be reported in the SAP error log if streaming replication is enabled when SP_STOP_REP_AGENT is executed while user tasks access RepAgent metadata in parallel.

 


Read more...

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 SP03 PL01, ASE SP03 PL01, SP03 PL01, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.