SAP Knowledge Base Article - Preview

2694360 - Targeted CR List for ASE 16.0 SP03 PL07

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
635018 A new function, show_prepared_statements(), is provided to display the SQL text for the prepared statements.
748461 The message "current process infected with 11 (SIGSEGV)" in the module 'open_byname’ together with a stack trace which includes the modules 'col_open_range' and 'vu_redefine' may be reported in the SAP ASE error log when during the execution of a stored procedure a view statement requires redefinition as it was compiled with the configuration option 'procedure deferred compilation' enabled. See KBA 2017991.
781928 In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc__findcachedSQLplan' together with a stack trace which includes the modules 'mem_getpages' and 'freeprocs', may be reported in the SAP ASE error log when LOAD DATABASE is run, while another session is reusing the same object descriptor, whose procedure buffer is in the process of being freed by the session running the LOAD command. See KBA 2162502 & 2270963.
800100 In some circumstances, a 2402 error, "Error converting characters into server's character set. Some character(s) could not be converted.", may be raised when executing a procedure but the procedure execution is not aborted leading to wrong results being returned for subsequent statements in the procedure when the server's and client's character sets are different and the same procedure has been run successfully previously and the query plan was cached. KBA: 2339369 - Procedure not exiting after Error 2402 reported
800965 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des__free_txrcoldes' together with a stack trace which includes the modules 'proc__used_as_login_script' and 'dropobject', may be reported in the SAP ASE error log when a stored procedure is executed. See KBA 2479691.
802535 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'showE_STMT' followed by a stack trace that includes the modules 'show_plan' and 'LeRun', may be reported in the SAP ASE error log when executing sp_showplan if the statement has changed during the execution of sp_showplan. See KBA 2373058.
802812 Streaming replication using the Component Interface now also supports object level replication.
806370 When auditing of sso_role is enabled, unexpected audit records may be generated against users without sso_role. See KBA 2441754
808387 New options, "disable_dc" and "enable_dc" has been added to the sp_procxmode system stored procedure, to disable and enable deferred compilation for a particular user stored procedure respectively.
809793 SAP ASE applies the 'allrows_mix' optgoal instead of the current session level optgoal at the query level if an invalid user defined goal is sent with the abstract plan.
809800 A 7130 error, "WRITETEXT with no log is not valid at this time. Database testdb1 must first be configured for this.", may be reported when WRITETEXT is run against an in-row LOB column while replication is enabled. Additionally when WRITETEXT is run against an off-row LOB column of an MVCC or On-Disk-MVCC enabled table while replication is enabled a ROWIMAGE log record is logged twice mistakenly.
810432 Allow IMRSLOGS threshold actions to restart when SAP ASE is rebooted and the free pages count is still below the defined threshold level for both single and multiple thresholds modes used for IMRSLOGS. The later mode is enabled with the SAP ASE trace flag 7439.
810467 A 1290 error, "Internal Error in lock manager routine: Attempted lock upgrade from update row to exclusive row in parallel query thread (family id < value > , spid < value > is Illegal.", together with a stack trace which includes the modules 'lock__ins_logical' and 'dol_update' may be reported in the SAP ASE error log when an UPDATE query is executed in parallel mode.
810764 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ind__get_sysindrow' together with a stack trace which includes the modules 'par_get_info' and 's_runtime_compile', may be reported in the SAP ASE error log when a stored procedure that creates temporary tables is executed and SAP ASE references the wrong object. Use the SAP ASE command line (boot) trace flag 11014 to enable the current fix. See KBA 2438077.
811700 Upgrade of Xerces from 2.1 to 3.2
811970 In rare circumstances, a SQL query that is executed in parallel may hang in the module 'LePipeRWState::LePrwsRWVtuple' for the parent thread and the module 'LavaThreadDriverMain' for the worker threads participating in the query execution. See KBA 2567720.
812443 If trace flag 766 is turned on, occasionally "ELC_VALIDATION_ERROR: Page < address > is not allocated in procedure cache. pelc = < address > , chunksize = < chunk size > , engine id = < engine id > , validate_flag = < 0/1/2 > " or ELC_VALIDATION_ERROR: Page not marked free. pelc = < address > , chunksize = < chunk size > engine id = < engine id > , validate_flag = < 0/1/2 > ." may be falsely reported in the SAP ASE error log during heavy workload or when SAP Adaptive Server flushes an Engine Local Cache (ELC) memory to its global memory pool. See KBA 2581174.
812551 A 154 error, "LIMIT clause is not allowed in UNION.", will be reported when applying the LIMIT clause in a UNION query.
813224 An incorrect value like '# < value > ' may be seen in the 'Memory Used' column of the sp_configure output when the 'max memory' parameter is set to a value greater than or equal to 2048 GB.
813326 A 249 error, "Syntax error during explicit conversion of VARCHAR value '# < value > ' to a INT field", will be reported when executing sp_shmdumpconfig. See KBA 2623861.
813547 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322.
813847 Multiple threshold actions may be executed unwantedly to extend a database through a threshold action if the database is blocked due to long duration of a concurrent DUMP DATABASE execution. See KBA 2614731.
813917 The shared objects libjpeg.so and liblcms.so (JPEG.DLL/JPEG.PDB and LCMS.DLL/LCMS.PDB on Windows) have been added to ${SYBASE}/shared/ase/jvm.wl (%SYBASE%\Shared\ase\jvm.wl on Windows) JVM white-list file.
814051 An UPDATE query which involves tables not consistently qualified with the 'dbo' qualifier, may give wrong results when executed by a user who is not the database owner. See KBA 2619053.
814190 A 16053 error, "The command 'LOAD TRANSACTION' with property 'WITH UNTIL_TIME' is currently not supported in SAP Adaptive Server, IMRS-database < database_name > .", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database.
814248 A new SAP ASE configuration option, "stream rep msg channel timeout", is introduced through sp_configure for an HADR setup using synchronous replication. During a failover, this option defines the minimum time in seconds before a mode switch can take place. The default value is 60 seconds.
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.
814496 The SAP ASE Workload Analyzer will fail to replay dynamic SQLs in a workload with errors, "Dynamic SQL error - Prepared statement 'xxxxx' does not exist.", reported in the SAP ASE Workload Analyzer Error Report Dashboard if the capture starts after the dynamic SQLs have been prepared.
814590 ddlgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. KBA - 2632662
814596 A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name1 > , object < obj_name1 > , index < idx_name1 > , partition < ptn_name1 > and not to database < db_name2 > , object < obj_name2 > , index < idx_name2 > , partition < ptn_name2 > ", may be reported in the SAP ASE error log after executing a CREATE CLUSTERED INDEX on a round-robin partitioned table with the dboption 'enforce dump tran sequence' enabled.
814651 The text of the 4305 error, "Specified file 'dump device' is out of sequence. Current time stamp is < datetime1 > while dump was from < datetime2 > .", has been improved to provide the dump file name in the message text. See KBA 2634147.
814669 dbcc checkcatalog output format is misaligned and appears garbled. See KBA 2634413.
814754 A batched language command executed with DYNAMIC_PREPARE set to FALSE can result in an open object and cached statement to be consumed and unable to be reused or freed for each batch. See KBA 2613604.
814755 Occasionally the execution of a SELECT query on a Data Only Locked (DOL) table may lead to incorrect results when the query optimizer uses a composite index of this table in order to access the data whose index leading column datatype is a fixed length CHAR and it contains special ASCII characters, such as CHAR(10), CHAR(31) or CHAR(1). See KBA 2636753
814910 In rare circumstances, the message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation", in the module 'get_resrow_size' together with a stack trace which includes the modules 'LopInsert::_lopCodeGen' and 's _compile_stmt' may be reported in the SAP ASE error log when a query is compiled and an object ID has been recycled by Adaptive Server causing a conflict between a definition time object ID and a Light Weight Procedure (LWP) object ID.
815210 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ResRelOp' followed by a stack trace that includes the modules 'ResRelOpProcess' and 'CgpPop::_CgpPePredBmToScalar', may be reported in the SAP ASE error log when a query is executed that involves an OUTER JOIN on a materialized view and a non-materialized view that return a constant column and there is a predicate on this constant column.
815581 A 11060 message, "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 during workload replay with the "Reset server time to source workload capture time" option selected and a VIEW, that is created after the workload captured time, is accessed. See KBA 2661224.
815594 Under some circumstances, the output from executing the sp_opt_querystats procedure with the 'option_show_long' option may have malformed text with random newline breaks over some words.
815693 FM failed to run as heartbeat stopped due to multiple tempdb exists - KBA 2672505
815706 On Windows platforms, the message, "Parameter 'start address' (number 1) to DBCC command 'bytes' has invalid value/type." may be reported in client console, or the printed address doesn't match the specified address in DBCC BYTES command when DBCC BYTES (address, length) is executed.
815740 The message "current process infected with 11 (SIGSEGV)" in the module 'site_login_cancel' with a stack trace followed by the message "Scheduler infected: exiting" may be reported in the SAP ASE error log. See KBA 2682423.
815760 A new backup server configuration parameter, 'retaindays', has been added to specify the number of days that a database or transaction dump will not be writable.
815803 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubffreef' followed by a stack trace that includes the modules 'ufclose', 'dir_sendtext' and 'DIRRemoteAccess::sendText', may be reported in the SAP ASE error log during concurrent access of big files via a proxy table. See KBA 2672421.
815827 sp_help ' < proc_name > ' may report an incorrect fully qualified parameter list when the procedure < proc_name > is created with TABLE type or TABLE variable parameters.
815832 A 11021 error, "Function < function_name > invoked with wrong number or type of argument(s).", may be reported in the SAP ASE error log when upgrading a SAP ASE 16.0 SP03 PL03 or later version and an in-lined table-valued UDF is accessed.
815833 A query, which is selecting from a view with a left outer join and a predicate in where clause, and the view definition contains a subquery in 'When exists' which is wrapped in 'case' clause and a left outer join is used, may return wrong results which don't take the predicate into account. See KBA 2690931.
816000 A 15101 message, "There is insufficient memory to allocate < n > bytes. Please increase configuration parameter 'messaging memory', or try again when there is less activity on the server." may be reported when a large value has been set for the configuration parameter 'messaging memory' and real time messaging queries are executed in multiple concurrent sessions. See KBA 2674952.
816003 Upgrade the version of Jetty from 7.6.5 to 9.4.11.
816009 In rare circumstance, a 889 error, "Internal error. Contact SAP Technical Support for help. BCM thread found MASS < buffer_address > in database < database_name > ( < database_ID > ) and cache < cache_name > ( < cache_ID > ) in an unexpected state < value > ", may be reported if latch free indexes are created and the house keeper garbage collector task (HKGC) is enabled in the database. See KBA 2686353.
816024 In rare circumstances, when the Backup Server is shut down with "shutdown SYB_BACKUP", the SITE HANDLER for the SYB_BACKUP connection never gets released in SAP ASE. Then on a successful restart of the Backup Server, the SITE HANDLER is unable to connect to the Backup Server. This causes that all subsequent DUMP commands are hanging in the SAP ASE Server. ASE traceflag 8024 (along with 3623) should be enabled to collect diagnostics in the SAP ASE log. See KBA 2669570.
816025 The message, "A fatal error has been detected by the SAP Java Virtual Machine: EXCEPTION_ACCESS_VIOLATION (0xc0000005)", together with the error message, "NTPCI__exit(1); Native Thread failed to unwind while attempting to shutdown the PCI", may be reported in the SAP ASE error log when loading sunec.dll on Windows platforms. See KBA 2687973.
816034 In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE and also behind the last hole fixed by the Fix-Phase of imrslog boot-time recovery.
816062 The message, "ERROR in plc__lrtopage() for plc < address1 > , dbid < database_id > , log record from plc at offset < address2 > with len_logrec < size > does not fit in log page with size < page_size > .", together with a stack trace which includes the modules 'xact__commitxact' and 'xls_flush_plcqueue' may be reported in the SAP ASE error log when a multi-database transaction is committed and one branch of the transaction involves an in-memory enabled database. See KBA 2709753
816073 The message "enp_aesEncrypt: CCLCipherCtx_all failed with error: 0xa0100014." may be found in the SAP ASE errorlog when the length of the user password which is used for the Job Scheduler is either 7 or 23. See KBA 2677850.
816078 In rare circumstances under an HADR setup, the coordinator process of SAP ASE RepAgent may hang in the module 'ra__ci_coordinator_waits_for_switch_ack' preventing the replication flow to continue.
816107 The active Rep Agent trace flags will now be reported in the SAP ASE error log when a Rep Agent is started. When no Rep Agent trace flag is active the message, "RepAgent( < dbid > ) no active traceflags.", will be reported. Otherwise the message, "RepAgent( < dbid > ) active traceflags: < TF1 > , < TF2 > , ..." will be reported.
816203 Updatease fails to start the SAP ASE server if the master device file size is larger than 4GB.
816272 The system stored procedure 'sp_activeroles' may show only the latest granted user defined predicated role, even if multiple user defined predicated roles are granted to the login, when SAP ASE configuration option 'enable predicated privileges' is enabled. See KBA 2684433.
816290 The number of free log pages in a database could be incorrectly reported by the sp_helpdb command, if the command ALTER DATABASE [LOG] OFF is used to remove pieces from the last database fragments and the command DUMP DATABASE WITH SHRINK_LOG is executed to remove the resulting fragment holes.
816352 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'yylex' together with a stack trace which includes the modules 'sqlpars' and 'internal_sql' may be reported in the SAP ASE error log when many white space characters appear in the query text following an SQL keyword, resulting in either a zombie task being created (in ASE 15.7 SP140 or ASE 16.0 SP03 PL04) or SAP ASE unexpectedly shuts down (in ASE 16.0 SP03 PL05 where a double signal is regarded as a fatal condition, but TF 2917 can be used to revert behaviour to the zombie task creation). See KBA 2686240.
816391 The dump history file contains unexpected 'dump.error' messages at a time when SAP ASE reports 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." and the log truncation is not successful. See KBA 2686302.
816407 The message, "Current process infected with signal 10 (SIGBUS)" in the module 'obfuscate_ldapacpwd' together with a stack trace which includes the modules 'ua__setldapacct' and 'sa_ssladmin' may be reported in the SAP ASE error log when sp_ldapadmin is run with command set_access_acct as part of LDAP configuration.
816409 A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after having dropped a user database which is marked suspect and is On-Disk MVCC enabled.
816425 Memory leak and contention in the PSS memory pool may be observed when there are multiple executions of 'set role with password on' in every other 'set proxy' session without a corresponding 'set role off'. See KBA 2656891.
816457 A new option 'create_table' has been added to the system stored procedure sp_dump_history that creates a proxy table in the tempdb database to access the dump history file.
816487 A new configuration option 'secondary signal handling' is introduced for SAP ASE which determines how the server handles secondary signals. The default value (1) makes the server shutdown on secondary signal.
816520 When no size is specified in the ALTER DATABASE command, the default size is incorrectly set to 512KB instead of 1MB for an Adaptive Server installation that is using a page size of 2KB.
816521 sp_showplan is enhanced to use 0 instead of -1 to display the specified statement ID.
816538 In rare circumstances, SAP ASE may become unresponsive and a 15403 error, "No memory for Encrypted Columns Frag bucket pool growth", may be reported in the SAP ASE log when the configuration parameter 'max parallel degree' is set to value greater than 1. See KBA 2691726.
816545 Running sp_helpdb against a database can report usage as "-- unused by any segments --" when a database usage contains a user defined segment only. See KBA 2691648.
816557 The message, "Assertion (pss- > pdbtkept = NULL)", together with a stack trace that includes the modules 'mda_populate_monRepLogActivity' and 'mda_exec', may be reported in SAP ASE error log when querying the MDA table monRepLogActivity while the diagserver binary is in use.
816562 The message, "Assertion (!(imrv- > imrv_status & IMRV_BULK_PURGE_VERSIONS) || ( imrslog_bkoutctx- > bulk_purge_ctxp && (imrslog_bkoutctx- > bulk_purge_ctxp - > ibpc_nloggedrows == IMRV_BULK_PURGE_NROWS(imrv)))) failed", may be reported in the SAP ASE error log for an IMRS enabled database during the execution of TRUNCATE TABLE while the diagserver binary is in use.
816639 An extra line may be printed between the header and the actual content in the sp_helpdb output.
816643 The message, "Invalid data found and rebuilt in segment accounting array for segment < segment_id > in database ID < database_id > .", may be reported in the SAP ASE error log following the recovery of a database. See KBA 2672135.
816677 A 10707 error, "java.io.FileNotFoundException: < jre > /lib/ext/ < jar_file > (Permission denied)" together with java stack trace may be reported when running a java method which implicitly invoke the loading of the extension < jar_file > .
816700 The sybmon command, 'print < address > -1 DES', may enter into an infinite loop and print the message, "txc_colid=0, txc_coffset=0, txc_indid=0", repeatedly when a memory dump is loaded in virtual map mode.
816710 In rare circustances, a process may hang in the module 'fio__p_sema' when trying to DUMP or LOAD a database if another Adaptive Server process has died due to a time slice error when reading or writing the dump history file.
816715 A memory leak in the Backup Server may be seen every time a DUMP of an in-memory database is taken.
816729 A 1244 error, "Could not find address lock at address < address > while trying to release it", may be reported when querying the monCachedObject MDA table.
816735 Dump files created using a pipe can now be loaded without using a pipe. Additionally, backup files created without using a pipe can now be loaded from a pipe.
816738 The total number of database pages stored in the dump header could not match the number of pages according to the database disk map stored in the same dump header if the database had trailing log holes and the end-user executed the command DUMP DATABASE WITH SHRINK_LOG | SHRINK_DATA | SHRINK_DATABASE.
816739 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'show_plan' followed by a stack trace which includes the modules 'LeRun' and 'LeEvals::LeEvRun', may be reported in the SAP ASE error log when using sp_showplan to query another session's query plan that involves CURSORs and the statement cache is enabled.
816752 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'bufsearch_cache_getlatch' together with a stack trace which includes the modules 'bt__fillrkey' and 'redo_bt_pagecompress', may be reported in the SAP ASE error log when LOAD TRANSACTION fails to redo some log record operations that involve cache-discrepant compressed index pages. See KBA 2696547.
816756 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'brfinish' together with a stack trace which includes the modules 'iocRunController' and 'blkioComplete', may be reported in the SAP ASE error log when SAP ASE completes a disk I/O operation.
816762 Using the sp_bindexeclass 'sv' object type to change the server-wide priority setting for the housekeeper wash task does not work.
816934 Incorrect results may be observed when a query involves temporary precomputed result set and the 'set rowcount < number > ' is used to limit the number of rows.
816941 A 9235 error, "Could not allocate memory for gettrunc. Please retry gettrunc() later when more memory is available, or re-configure the server with a larger procedure cache.", will be reported when the command DBCC GETTRUNC fails to allocate memory. The error message wrongly refers to the procedure cache and should instead indicate the need to increase the value of the parameter 'replication agent memory size'.
816992 When a DUMP or LOAD command using a backupserver API library is aborted from the client, the call to the module 'syb_close' that will close the stripes gets the mode SUCCEED_ON_CLOSE instead of ABORT_ON_CLOSE. The result is that the API library cannot know that the operation was aborted. See KBA 2705604.
817001 The message, "The compiler will use the current best plan when 10%(Optimization Timeout limit) of average execution time is exceeded.", may be reported mistakenly by SAP ASE when the set option show brief/on/normal/long is enabled and the set plan opttimeoutlimit < value > is set to a different value than the default value of 10.
817092 When a downgrade is attempted from ASE 16.0 SP03 PL04 or higher version to a lower version using the stored procedure sp_downgrade_esd, and the higher version contains SQL UDFs that do not reference tables, the downgrade will fail.
817167 A 712 error, "There is insufficient heap memory to allocate < wrong_huge_value > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.", may be reported with the wrong number of bytes that could not be allocated.

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