SAP Knowledge Base Article - Preview

3139782 - Targeted CR List for ASE 16.0 SP03 PL12

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 SP03 PL12 . 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 NumberDescription
665006 The audit event for shutdown command has been enhanced to distinguish between the shutdown action of Adaptive Server and Backup Server.
683438 DBCC EXTENTDUMP is enhanced to report the OAM page number of an extent.
704203 In rare circumstances, the message, "Log contains all committed transactions until 1900/01/01 00:00:00.00 for database < database-name > .", may be reported in the SAP ASE error log by ONLINE database command. This message is not useful during ONLINE database and should not be reported. See KBA 2509711
728520 On big endian systems such as AIX, the execution for DBCC TUNE('wcpu', < value > ) may unexpectedly succeed for a value that is not within the allowed range of values of 1 and 65534.
784791 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'kbfalloc' together with a stack trace which includes the modules 's_normalize' and 'memallocheap' may be reported in the SAP ASE error log when creating a function-based index with a fully qualified (db.owner.name) object name. See KBA 2175592.
804555 In rare circumstances, SAP Adaptive Server may return incorrect result when a query involving outer join and predicates of the form "col < > @var", is run. A fix is enabled under trace flag 11029. See KBA 2438877.
811442 A 7921 error, "Found < value > bad entries in sysindexes.", may be reported by DBCC CHECKALLOC on a database that is not having a segregated log device. See KBA 2552226.
817367 Enhancements to dbcc dbrepair() interface to accept dbid as paramter.
818848 DBCC HELP does not provide syntax for DBCC SHRINKDB_SETUP. See KBA 2787004.
819281 In rare circumstances, successive calls to getdate() built-in in SAP Adaptive Server may return a timestamp value which is older than the previously returned timestamp value. See KBA 2792603.
821193 SAP Adaptive Server auditing feature is enhanced to add full command text into audit record for 'errors' event. SQL commands failures including dump failures can be checked via 'errors' event. See KBA 2903526.
822498 The SAP Adaptive Server column names resolution mechanism during query execution has been enhanced to decrease the contention while accessing the system catalog 'syscolumns'. See KBA 2956898.
822844 Following an upgrade, Web Services reports that an unknown exception occurred: java.lang.UnsupportedOperationException: X509ExtendedKeyManager only supported on Server (See stack trace at bottom of this message).
822947 When auditing the execution of a stored procedure through sp_audit and option "exec_procedure", the database ID ‘dbid’ and name ‘dbname’ information from where the stored procedure is executed will now be reported in the sysaudits.extrainfo column. See KBA 2975564.
823671 Parallel query execution may hang if the query is killed in the middle of the execution of parallel hash join. See KBA 3001441.
823684 In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of 36616. Maximum allowed length is 16384.", may be reported in the SAP Adaptive Server error log when a SELECT query retrieves LOB data under isolation level 0. Alternatively, the message, "Current process infected with 11 (SIGSEGV)", in the module 'kbfalloc' together with a stack trace may be reported in the SAP Adaptive Server error log. See KBA 3013683.
824128 The message, "current process infected with 11 (SIGSEGV)", in the module 'des__clean' together with a stack trace which includes the modules 'des_refreshall' and 'online_database' may be reported in the SAP ASE error log when multiple sessions are executing ONLINE DATABASE simultaneously for the same database. See KBA 3111484.
824358 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ssql_release' together with a stack trace that includes the modules 's_unkeep_cached_stmts' and 'sequencer' may be reported in the SAP ASE error log when a query is executed and the statement cache is full. This will result in an implicit Adaptive Server shut down. See KBA 3035656.
824408 SAP Adaptive Server is enhanced allowing the support of QUIESCE and PREPARE DATABASE commands for system databases sybsecurity and sybmgmtdb with segregated data and log devices. See KBA 3078617.
824574 In a replicated database setup for Multiple Paths Replication, the Secondary Truncation Point of the SAP Adaptive Server replicated database may not move when any one of the replication paths is idle.
824629 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'Lop::lopProcessTree()' together with a stack trace which includes the modules 'lopGenerate' and 's_compile_stmt' may be reported in the SAP ASE error log when executing a SELECT query that has a very large number of UNION statements.
824845 In rare circumstances, the message "timeslice -10001, current process infected" in the module 'write' together with a stack trace which includes the modules 'ssltraceprint' and 'ssl_nrpacket' may be reported in the SAP ASE error log when SSL is enabled during a login after SSL handshake. See KBA 3059882.
824974 In rare circumstances, when a SIGTRAP signal is raised from a thread other than the ASE main thread, Adaptive Server may produce a core dump file without any trace shown in the SAP ASE error log and it will implicitly shut down itself. Alternatively the signal may get ignored or lead to a timeslice error. See SAP KBA 3075877.
824983 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'PtlXmlQuery::XmlXQueryNext' together with a stack trace may be reported in the SAP Adaptive Server error log when complex XML queries are executed. See KBA 3086874.
825020 In rare circumstances the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memfreeheap' together with a stack trace may be seen in the SAP ASE error log on HP platform when Statement Replication feature is enabled. Alternatively on Windows platform a 3602 error, "Transaction has been rolled back.", may be reported together with a stack trace in the module 'ex__doprint'. See KBA 3112119.
825079 A query is not killable when using a very large IN CLAUSE while traceflag 132 is enabled to remove duplicates from the IN list. See KBA 3083815.
825167 An Adaptive Server login whose password has expired is unable to change the password using ALTER LOGIN if the login has a default database other than the master database. See KBA 3075109.
825343 In rare circumstances, a 1295 error, "Unconditional lock request for table or page < page-number > , dbid < database-id > was made while holding a latch.", may be reported after REORG REBUILD fails due to a 1204 error, "ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.".
825369 Incorrect ‘in row’ column information may be reported by sp_help when a table that has an in-row LOB column datatype is altered to varchar datatype. See KBA 3111371.
825404 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'senddone' together with a stacktrace which includes the modules 'curs_fetch' and 's_cleanframe' may be reported in the SAP ASE error log when CURSOR FETCH execution has hit a deadlock error. See KBA 3089377.
825414 A 1622 error, "Type < value > not implemented.", may be reported during an incorrect TDS exchange between a client and SAP Adaptive Server. This error will be handled gracefully. See KBA 3100503.
825422 A 935 error with state 4, "WARNING - the timestamp in database ' < database-name > ' (0xff##, 0x########) is approaching the maximum allowed. < ##.# > % of the emergency reserve timestamps remain before the database is shut down automatically. Please contact SAP Technical Support.", will be reported every 12 hours in the SAP ASE error log if the database timestamp gets bigger than '0xff00 00000000'. See KBA 3130538.
825458 The message, "The 'single user' option is not valid for the 'sybsecurity' database.", may be reported when shrinking the sybsecurity database with system stored procedure sp_shrink while SAP Adaptive Server was started in single user mode. See KBA 3094124.
825516 In most circumstances, SAP Adaptive Server may report an incorrect value for column 'PacketsReceived' in the MDA table 'monProcessNetIO' when SSL is enabled. See KBA 3124582.
825604 A 632 error, "Attempt to move memory with an incorrect length of < negative-value > . Maximum allowed length is 16384.", together with a stack trace which includes either the module 'LeAlignedDataRow::copyOneCol' or 'LeAlignedDataRow::copyOneCol' may be reported in the SAP ASE error log during the execution of a SELECT query that includes in-row LOB columns and uses a HASH JOIN operator in the query plan being run. See KBA 3101476 and KBA 3094537.
825658 The new configuration option "number of dump load retries" is introduced in "Backup/Recovery" section of the SAP ASE configuration file which indicates the number of times a DUMP or LOAD command will internally be re-executed upon failure.
825708 A 4306 error, "There was activity on database since last load, unable to load. Must restart load sequence with the load database to continue.", may be reported during LOAD TRANSACTION after having taken a full database dump while the database is in load sequence and the SAP ASE configuration option "enable dump history" is set. See KBA 3108717.
825715 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'sybgetptr' together with a stack trace which includes the modules 'repparams_analyze' and 'log_sysproc_exec' may be reported in the SAP ASE error log when executing the system stored procedure sp_hidetext in a replicated database. See KBA 3111032.
825727 The error message, "Backup Server: 10.3.2.1: Fail to decrypt SSL password.", followed by the message, "Backup Server: 1.28.2.88: Open Server routine srv_props failed. See Backup Server error log for additional information.", may be reported in the SAP Backup server error log while booting the Backup server with SSL and without providing the SSL password.
825753 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeCacheDMLOp::_LeOpAcquire' together with a stack trace may be reported in the SAP ASE error log when Adaptive Server recompiles a stored procedure that is using table variables. See KBA 2539328
825773 When rolling back a transaction from within a trigger Adaptive Server may remove unexpectedly the calling procedure query plan from the SAP ASE procedure cache. See KBA 3114259.
825779 In some circumstances, SAP Adaptive Server may return an incorrect result when executing in parallel mode a SELECT JOIN query that has a search argument which involves a local variable while the configuration option 'statement cache size' is enabled. Similarly when a constant value is used instead of the local variable while the configuration option 'enable literal autoparam' is set. This may happen when the same query is run multiple times with different variable or constant values. See KBA 3114942.
825784 A 632 error, "Attempt to move memory with an incorrect length of -1. Maximum allowed length is 16384.', may be reported in the SAP ASE error log during the execution of a dynamic SQL query with streamlined LOB parameter that has been interrupted by the end-user. See KBA 3132077.
825790 In rare circumstances, a global temporary table may be erroneously instantiated by SAP Adaptive Server during the execution of a query. See KBA 3116987
825793 In rare circumstances, a 614 error, "Adaptive Server accessed a row that has an illegal length of < row-length > while in database < database-name > '. Page pointer = < page-address > , pageno = < page-number > , status = < page-status > , ptnid = < partition-id > , indexid = < index-id > , level = < index-level > , pnextrno = < page-next-row-number > . The minimum row length is < min-row-length > . The page size is < page-size > .", or a 9829 error, "Compressed data row < row-address > in objid < object-id > , dbid < database-id > is corrupted.", or a 806 error, "Could not find virtual page for logical page < page-number > in database ' < database-name > '.", may be reported when an UPDATE is executed after turning compression off on an APL table without having first rebuild its clustered index. See KBA 3115727.
825796 A 941 error, "Illegal database context operation.", in the module 'closedb' together with a stack trace which includes the modules 'lddb_main' and 'lddb_cleanup' may be reported in the SAP ASE error log when LOAD DATABASE of master database is executed.
825835 In rare circumstances, SAP Adaptive Server may allow a duplicate key row to be inserted in a round robin partitioned APL table that has a unique clustered index, after a column has been dropped using ALTER TABLE while this column is not part of the unique clustered index.
825873 In some circumstances, the message, "Current process infected with 11 (SIGSEGV)", in the module ‘sendtext’ together with a stack trace may be reported in the SAP Adaptive Server error log, when a SELECT query retrieves LOB data while the query is executed using hash join mechanism. See KBA 3130547 .
825897 The message, "Current process infected with signal 11 (SIGSEGV)", in the module ‘ssql_getdesc’ together with a stack trace may be reported in the SAP Adaptive Server error log when ‘sp_options show’ is executed and statement cache monitoring is enabled while the diagserver binary is in use. See KBA 3131268.
825923 The message text for error 1903 and 9863 has been enhanced to report the table name involved in the error with respectively " < size-value > is the maximum allowable size of an index. Composite index size specified on table ' < table-name > ' is < size-value > bytes." and " < operation-value > operations cannot be specified on table ' < table-name > ' with < locking-scheme > lock scheme.".
825938 In rare circumstances, Adaptive Server may run into a hang situation that was seen on IBM platform with the messages, "Initiating shared memory dump for signal 11” and "Dumping shared memory to dump file: < dump-filename > ", reported in the SAP ASE error log while a shared memory dump is gathered following a signal 11 error that was triggered from module ‘_global_lock_common’. The current simplest solution will allow to gather a shared memory dump without however using parallel dump and compression capabilities. See KBA 3135121
825974 The message “sddone: < write-or-read > error on virtual disk < virtual-disk-number > block < block-number > ” followed by “sddone: Operation would block” may be reported in the SAP ASE error log on HP-UX platform after an unsuccessful I/O operation during the execution of a query. See KBA 3135187.


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 PL12, ASE SP03, SP03, PL12, 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 ONE Support launchpad (Login required).

Search for additional results

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