SAP Knowledge Base Article - Preview

2659546 - Targeted CR List for ASE 16.0 SP03 PL06

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
549837 The output of DBCC SHOWRECOVERY show some lines with incorrect information
790553 The message, "Update of syslogins failed", can be seen in the SAP ASE error log when a login attempt was interrupted during the update of the system table syslogins. See KBA 2201383.
798527 setuphadr is enhanced to re-start the HADR set up from the step where it last encountered a recoverable error. If the error cannot be recovered, setuphadr will clean up the incomplete environment and re-attempt the set up.
799092 The message, "-- Unknown object type: SF", may be reported in the context when executing the sp_helptext system stored procedure against User-Defined SQL Functions with the 'ddlgen' option enabled.
800520 In rare circumstances, BCP IN may fail together with a stacktrace which includes the modules 'bt__check_insert_position' and 'bt_insert' reported in SAP ASE error log when the server sortorder is something like '*nocase*'.
800868 A 9557 error, "The server failed to create or update a row in table ' < name > ' because a varying-length column would start at offset < value > . This starting location cannot be represented accurately in the table's row format.", may be reported during DML execution if the SAP ASE page size is configured to either 8K or 16K bytes and the database option 'allow wide dol rows' is disabled.
804078 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'com__exctnume_copy' together with a stack trace which includes the modules 'comnb_numtonum' and 'LeEvals::LeEvRun', may be reported in the SAP ASE error log if the configuration option, 'streamlined dynamic SQL', is enabled and a dynamic cursor query with an ISNULL expression on a numeric field is executed. See KBA 2493162.
805500 Upgrade Adaptive Server and Backup server ZLIB version to 1.2.11.
806853 The output for the SET option sub-commands 'show_best_plan', 'show_final_plan', 'show_lio_costing', 'show_elimination' and 'show_parallel' does not print any information when the 'brief' option is used. See KBA 2450023.
809658 Garbage collector for In-Memory Row Storage may get blocked on a utility, such as REORG REBUILD, REORG RECLAIM_SPACE, REORG FORWARDED_ROWS, REORG COMPACT, ALTER TABLE, CREATE CLUSTERED INDEX, DROP INDEX, TRUNCATE TABLE, even after the utility has exclusive lock granted on the table or does not involve the In-Memory row store content.
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
810991 In a DRC/IMRS MVCC enabled table, rollback of a command may fail due to lack of memory.
811061 The execution of the system stored procedure sp_who may show an empty or erratic value for 'hostname' for the JOB SCHEDULER task as opposed to a NULL value.
811725 Improve process of object id assignments to temporary tables to avoid raising spurious errors relevant to temporary tables like 'object not found', 'column not found'.
811919 DISK RESIZE must accept a negative value to shrink the device and truncate the device file in order to release space to the OS.
812014 On Solaris 5.11 and later versions, the message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the SAP ASE error log when sybmon is attaching to the server which is not using ISM (Intimate Shared Memory).
812216 If an SAP ASE engine hangs while a network listener is affinitied to it, the network listener will be respawned, but may not resume accepting connections as expected.
812461 In rare circumstances in a Distributed Transaction(DTM) environment, when the coordinating server is being rebooted after the crash, the messages, "Running spid is < SPID of current PSS > , spid from the pss in the sdes is < SPID of PSS cached in sdes > " and "Running kpid is < KPID of current PSS > , kpid from the pss in the sdes is < KPID of PSS cached in SDES > ", together with a stack trace, which includes the modules 'pss_from_sdes' and 'closetable', may be reported in the errorlog of a participant server for an On Disk MVCC enabled database, when the diagserver binary is used.
812477 Under rare circumstances, SAP ASE may appear to hang during an UPDATE STATISTICS or another commands that runs at a lower priority. See KBA 2581507.
812687 The sp_sysmon report is completed with a new entry in the section "Transaction Management", for the "ULC Flushes to Xact Log": "by IMRSLOG Replication". It indicates when the ULC was flushed while writing a book-keeping log record in SYSLOGS for a replicated transaction in SYSIMRSLOGS.
812974 New interface to allow packing rows out of IMRS using the sp_imrs system stored procedure. The syntax is sp_imrs 'pack_rows', ['aus', ' < number_of_Allocation_Units_to_pack > ' | 'pct', ' < percentage_of_Allocation_Units_to_pack > '].
813037 During a graceful shutdown of SAP ASE in threaded mode, the errorlog indicates a new configuration file is written even if there are no configuration changes done. See KBA 2594978.
813102 A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page. Rid pageid = < value > ; row num = < value > . Page pointer = < value > , pageno = < value > , status = < value > , ptnid = < value > , indexid = < value > , level = < value > , pnextrno = < value > ", may be reported in the SAP ASE error log when an IMRS enabled database is replicated and there is very high activity on the database.
813511 In rare circumstances, a 3401 error, "Rec_logbounds: getnext SCAN_RID of last checkpoint failed on Rid from sysdatabases. Rid pageid = < page# > ; row num = < row# > .", may be reported in the SAP ASE error log during boot time recovery resulting in the database not being recovered or Adaprive Server may not start if the error occurs for the master database.
813517 The speed of the dump and load of databases that contain large regions of empty pages is now faster. The allocation pages of empty allocation units are no longer copied to the dump archives.
813694 On Windows platform, a 12055 error, "System call stati64 failed with error 3", will be reported when executing a query on the monDeviceSpaceUsage table when there is a SAP ASE device created on a Windows mounted path. See KBA 2611275.
813720 In rare circumstances, the background process IMRS_PACK may hang indefinitely for an IMRS enabled database while searching for rows to pack in the IMRS ILM queue.
813810 In rare circumstances on a heavily-loaded system, Adaptive Server may omit to recover IMRS committed transactions during the crash recovery of an IMRS enabled database when the configuration option ‘recovery interval in minutes’ is set to a small value and DUMP DATABASE or DUMP TRANSACTION commands are frequently executed.
813815 Under an HADR setup when stream replication is enabled, a 9405 error, "RepAgent( < dbid > ): Internal Error. The total number of columns in raobj ( < number > ) does not match the number of elements in RA_COLS list ( < number > ).", may be reported in the ASE error log. This error occurs when the metadata can't fit in the current package and Rep Agent has to flush it prior to sending the metadata. The error doesn't impact replication and can be ignored. See KBA 2630044
814095 Under rare circumstances, SAP ASE may hang at startup during engine online, when config parameter 'kernel mode' = process. See KBA 2635465.
814192 The dbo and table owner can grant explicit decrypt permissions on an encrypted column when both the options 'enable granular permissions' and 'restricted decrypt permission' are enabled. See KBA 2623174.
814204 In rare circumstances, the statement line number is not correctly displayed in the showplan output when an SQL statement is executed with the set showplan option enabled.
814289 The message, "Internal error: data length mismatch in ct_fetch().", may be reported in the Optdiag error log when displaying statistics using the Optdiag in a BASH shell with the LANG environment variable set to default. See KBA 1866748.
814330 For SAP BW user queries with fact_table hints, sometimes when the hint fails, SAP ASE selects a suboptimal plan because of a bad optimzation goal, resulting in poor performance.
814445 In some rare scenarios, parallel execution of a query hangs when dynamic thread allocation feature is on and the query plan contains LeRestrictOp in the right subtree of LeMJOp. See KBA 2642040
814478 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memmove' followed by a stack trace may be reported in the SAP ASE error log when executing subqueries that make use of built-in replicate(). See KBA 2630662.
814632 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘ksMuxSchedulerRemoveQ' may be reported in the SAP ASE error log when a SHUTDOWN command with the WITH NOWAIT option is executed and will cause the shutdown command to hang.
814639 Under an HADR setup when stream replication in enabled, sometimes the last command replicated is not confirmed by Adaptive Server and hence not applied on the standby database by Replication Server if there is no activity occurring in the primary database following that last command execution.
814657 In rare circumstances under an HADR setup, a 9414 error, "server RepAgent( < dbid > ): Streaming replication stream CI Library error -1 with severity 2 and message 'Producer receiver ' < db_name > ' failed to receive data, shutting down transport to 'ocs:host:port'.'. Rep Agent detected error 3 with message 'Unknown' at line 0 in file nofilename.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent hang.
814658 The message, "Sybase ENPAPI Error Message: INFORMATION: The FIPS Certified Crypto Kernel is enabled", is reported in the Job Scheduler Agent log as an information message but it also contains the term "Error", making it ambiguous. KBA 2652006 - Unclear information in ASE errorlog file about 'ENPAPI Error'
814674 In some cases while using JDBC/ODBC driver, the functions getTablePrivileges() and getColumnPrivileges() may not return expected results.
814700 A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization." may be reported when enabling statement cache and using a table variable within a derived table. See KBA 2635224.
814767 A 12352 error, "A transaction in database ' < name > ' (spid= < value > ) has hit a fatal error during rollback. ASE will try to reboot and recover the database. The XREC_BEGINXACT of this failing transaction is ( < page# > , < row# > ).", will now be reported in the SAP ASE error log besides to the end-user when the database option 'allow db suspect on rollback error' is enabled and a non-recoverable error is hit during a transaction rollback.
814782 MERGE statement that does not perform any action may incorrectly return a rowcount different than zero.
814788 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'func2view' followed by a stack trace that includes the modules 's_crtproc' and 'sequencer', may be reported in the SAP ASE error log when creating an in-lined Table-Valued SQL-based User Defined Function without SELECT statement.
814798 In an HADR setup when stream replication is enabled, a 2615 error, "Attempt to insert duplicate row in database ' < name > ' ( < database ID > ), object ' < name > ' ( < object ID > ), index ' < name > ' (0), partition ' < name > ' ( < partition ID > ). Could drop and recreate index with ignore duprow or allow dup", followed by the message, "Command has been aborted", may be reported when replicating an All Pages Locked table that has a clustered index defined.
814806 A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < name > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), partition 'sysimrslogs_59' (59). Please contact SAP Technical Support.", may be reported in the SAP ASE error log when a SELECT-INTO from sysimrslogs command is executed.
814837 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mem__pageallocate_this_engine' together with a stack trace which includes the modules 'mem_pageallocate', 'mem_getpages' and 'hashbifs_md5_lerun', may be reported in the SAP ASE error log when using hashbytes() built-in with MD5 algorithm and input arguments as NUMERIC/DECIMAL/MONEY. See KBA 2636316.
814870 A 10330 error, "Access permission denied on object < objname > , database < dbname > , owner < username > ", may be reported when a stored procedure is executed by a user that does not have explicit permissions granted on the underlying referenced objects in the stored procedure, such as partitioned tables and user defined functions, while SAP ASE renormalizes the stored procedure from its text.
814916 In a HADR installation, a new $SYBASE/DM/dir.properties file is added to capture the Custom Directory Information specified during HADR configuration.
814919 In rare circumstances under an HADR setup, a 12406 error, "Failed to find the last row marker for transaction ( < pagenum > , < rownum > ) in sysimrslogs for database ' < dbname > ' ( < dbid > ). The sysimrslogs row is corrupted.", may be reported during boot-time recovery of an IMRSLOG enabled database when stream replication is enabled.
814923 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra_malloc_mempool' and 'ra_mempool_alloc_internal', may be reported in the SAP ASE error log when the Rep Agent Secondary Truncation Point (STP) Manager Thread terminates abnormally leading to corruption in the Rep Agent Memory Pool.
814927 In rare circumstances on a heavily-loaded system, DROP INDEX may hang when the SAP ASE configuration option "hcb index auto tuning" is enabled and the HCB AUTO TUNING process is now sleeping and was working on the corresponding index.
814959 In rare circumstances, a hang may be seen and reported by sp_lock, when a process executes a WRITETEXT command that is replicated and involves an in-row LOB column and a shared row lock request cannot be granted immediately, or when it sets the IDENTITY max burn value for a table and an exclusive table lock request cannot be granted immediately, or when the commands ALTER DATABASE and DUMP DATABASE or TRANSACTION are run concurrently and an exclusive address lock request on the database disk map cannot be granted immediately.
814962 A 2512 error, "Table Corrupt: Cannot find the specified row number < value > , in index page < value > , partition ID < value > , on data page < value > .", may be reported when running DBCC CHECKTABLE and after loading a transaction dump that was taken while a concurrent committing transaction and the ckeckpoint log record written by DUMP TRAN was stored interleaved with the committing transaction log records in such a way that the fullycommitxact marker in the dump header is set to the dump instant of the IMRSLOG database.
814968 Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled.
814983 In rare circumstances under an HADR setup a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the target page is not a data page.", or a 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page.", or a 625 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the entry in the offset table for that RID is less than or equal to 0.", may be reported by the Rep-Agent scanner of IMRSLOG when a re-scan occurs and stream replication is enabled on an IMRS database.
814991 An error, "Configuration parameter 'max memory' is above the maximum. It is < value > , but must be at most -1", may be reported when executing the preupgrade utility.
815018 A 5859 error, "The configuration number '652' is invalid.", which value corresponds to the configuration parameter "bind backupserver address" may be reported in the SAP ASE error log during startup after adding a Dump Configuration using the ASE Cockpit or by using the stored procedure sp_config_dump. See KBA 2640866.
815021 The values of local variable parameters are not printed in the output of the 'select query_text( < spid > )' query.
815044 A 101 error, "SQL syntax error", followed by a 105 error, "Unclosed quote before the character string", may be reported in the SAP ASE error log when the Job Scheduler is scheduling a new job with start time equal to the current time and under the condition that it has already scheduled maximum jobs i.e. equal to the value of config parameter 'job scheduler tasks'.
815055 A 207 error, "Invalid column name ' < name > '.", may be reported during the execution of a SELECT query that joins a proxy table which has a LOB column while the statement cache is enabled. See KBA 2647459
815056 A 208 error, "# < temporary_table_name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).”, may be reported during the recompilation of a prepared statements batch which creates a temporary table. See KBA 2646418
815070 SQL query text is not printed with stacktrace when ASE runs into an exception during parallel execution.
815081 In rare circumstances, a 702 error, "Memory request for < num > bytes exceeds the size of single page of < 16384/8192/4096/2048 > bytes.", may be reported on a 16K/8K/4K/2K-byte SAP ASE installation, in the corresponding order, when the system stored procedure sp_post_xpload is executed after a cross platform DUMP or LOAD was run and a table in the source database has undergone a no data copy operation.
815086 The error message 728, “Allocation of size < value > bytes from the row storage cache, ' < name > ', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < value > , object ID = < value > , partition ID = < value > , request type = < value > ( < string > ).”, is enhanced to provide additional context information when we have run out-of-memory for an IMRS enabled database.
815099 A 12858 error, "Update to sysobjects row for database ' < name > ' ( < dbid > ), object ' < name > ' ( < objid > ) failed.", in the module 'obj_updrow' together with a stack trace which includes the modules 'des_idtflush' and 'des_checkpoint' may be reported in the SAP ASE error log when DUMP DATABASE is in progress and the DDL transaction that created this object is rolled back.
815102 A 251 message, "Unable to allocate ancillary table for query optimization. Maximum number of tables in a query (91) exceeded" may be be reported when more than 91 worktables are required internally by to execute a query.
815110 In rare circumstances under an HADR setup, a 9219 error, “RepAgent( < dbid > ): Internal coding error.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent implicit shut down or hang.
815121 A warning message, "The configured value < value_1 > for parameter 'kernel resource memory' is too low. It should be at least < value_2 > for the present configuration", is reported when the kernel resource memory is resized by the server. This is not an appropriate warning and is now replaced by an informational message, "ASE has autoconfigured 'kernel resource memory' to < value_3 > pages".
815123 The backup server may leak some memory when using non absolute paths for the interfaces file, the configuration file, the hosts.allow file or the dump stripes.
815161 A 8006 error, "ASE error detected by Backup Server. Refer to the preceding Backup Server message.", together with a stack trace that includes the modules 'dmp_send_dpm' and 'dpdb_main', may be reported in the ASE error log and the counterpart error, "3.15.2.1: The disk piece for page < number > does not belong to phase 2.", in the backup server error log when DUMP DATABASE is run while taking a database dump of an IMRS enabled database and the configuration parameter 'optimize dump for faster load' is enabled.
815175 In rare circumstances, SAP ASE may hang in the module 'xsc_sysimrslogs_valid_xactblk' together with the modules 'xsc__sysimrslogs_getnext' and 'rec__boot_recover_dbs' reported in the call stack of the hanging process while an IMRS enabled database is recovered as a result of an IMSLOG invalid page present in the committed region of the IMRSLOG.
815216 The index attribute 'optimitistic_LFB' will not be enabled as expected on big-endian platforms such as Solaris, IBM pSeries Linux, IBM AIX and HP Itanium platforms, when executing the stored procedure "sp_chgattribute 'optimitistic_LFB', 1".
815217 In rare circumstances, a storage access violation or the message, "Current process infected with signal 11 (SIGSEGV)" followed by a stack trace that includes the modules 'ubffreef', 'memfreeheap' and 'table__check', may be reported in the SAP ASE error log when running DBCC CHECKTABLE against system tables like SYSCOMMENTS where there are hidden columns.
815225 Status bits representing a text page or an OAM page may be incorrectly set in a page pertaining to an imrslog segment.
815342 A SELECT query against the monSysLoad MDA table can return zero row if a search argument on EngineNumber or StatisticID is used with an engine number other than engine 0. See KBA 2651421.
815369 A new status bit (0x20) has been added to the dump history record to mark those entries that were inserted as a result of a LOAD instead of a DUMP operation.
815399 In rare circumstances, DBCC CHECKTABLE may report index inconsistencies on an IMRS enabled table, after LOAD DATABASE followed by one or more of LOAD TRANSACTION commands using the backward scan recovery strategy were executed.
815472 In rare circumstances, when a workload with a large dataset is being monitored using the Workload Profiler, an arithmetic overflow error may occur. If a new monitoring session is started while the existing one is still active, a 19537 error, "Invalid syntax or illegal use of the USING clause" is incorrectly reported which is misleading.
815496 Under rare circumstances the free page count for database segment 0 (system) may become negative and not reset to 0 without a message reported in the SAP ASE error log indicating this negative free page count.
815548 In rare circumstances, a 631 error, "The length of < value > passed to delete row routine for the row at offset < value > is incorrect on the following page of database ' < name > ’: Page pointer = < value > , pageno = < value > ... The expected row length is < value > . The offset should be no greater than < value > .”, may be reported in the SAP ASE error log followed by the message, "Error while undoing log row in database ‘ < name > ’. Rid pageid = < value > ; row num = < value > .”, during the roll back of a user transaction when the syslogs available space has crossed the last chance threshold and the session was explicitly killed. This may result in phantom locks left behind because of the roll back failing. See KBA 2660763.
815681 Performing a downgrade from SAP ASE 16.0 SP02 PL05 or higher to a version prior to SAP ASE 16.0 SP02 may report a failure on 'sysobjects.sysstat5' and 'sysindexes.status4' columns for replicated tables having a unique index. See KBA 2664693.
815731 A 728 error, "Allocation of size < num > bytes from the row storage cache, < cachename > , failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < memory_address > , object ID = < object_ID > , partition ID = < partition_ID > , request type = < type_ID > < (type name) > .", may be reported when a DELETE or UPDATE operation is being performed on a row that reside in the in-memory row storage and there is not enough space available.

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 PL06, ASE SP03 PL06, SP03 PL06, 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.