SAP Knowledge Base Article - Preview

3115940 - Targeted CR List for ASE 16.0 SP04 PL02

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 SP04 PL02. 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
677539 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'alloc_dirtychains' together with a stack trace that includes the modules 'CgLavaUtils::CgCompFakeTable' and 's_compile' may be reported in the SAP ASE error log when a SELECT query using a fake system table such as sysprocesses and syslocks is executed and the tempdb database is not yet available. See KBA 2636652.
799714 LTL Rep Agent enhancements to support Replication Server Kerberos principal name. This feature is enabled by LTL Rep Agent configuration option 'rs principal'.
817087 The message, "Assertion (!single_plcblock || buf_destroy) failed", together with a stack trace which includes the modules 'xls_remove_buf_from_plcblock' and 'dol_insert' may be reported in the SAP ASE error log when multi-database, a mix of high and low durability databases, transactions are involved while the diagserver binary is in use.
817607 A SELECT query accessing a remote table which has LOB columns and is located into an Oracle database will hang. See KBA 3075030.
818657 Change default value of 'replication agent memory size' from 8M to 100M
818877 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'result' together with a stacktrace which includes the modules 'pre_aggview' and 's_compile' may be reported in the SAP ASE error log while Adaptive Server is compiling the system stored procedure sp_rep_masterdbsetup. See KBA 2773865.
819982 In rare circumstances, UNMOUNT DATABASE may hang blocking other tasks. Alternatively the message, “Current process infected with signal 11 (SIGSEGV)”, in the module ‘fm_free_frame’ together with a stack trace which includes the modules ‘db__create_sysusages_map’ and ‘dbt_get’ may be reported in the SAP ASE error log. Adaptive Server trace flag 12392 when enabled will check for illicit values in the frame list and report errors. See KBA 2835590.
819992 Extensions are added in sybmon utility, to capture the call stacks for CI native threads in a shared memory dump, to ease HADR debugging. However, for each replicated database, these extensions require the allocation of additional 24M-bytes memory from the Replication Agent global memory pool. Consequently the ASE configuration option ?replication agent memory size? should be adjusted.
820500 In rare circumstances, the message, "timeslice < value > , current process infected", in the module 'des_checkpoint' together with a stack trace which includes the modules 'checkpoint' and 'dmpx_truncatemain' may be reported in the SAP ASE error log after error 8211, "Mismatch found between the name and id descriptor hash table for table < table-name > , objid = < object-id > . Descriptor hashed by name = 0x0 and hashed by id = < value > .", is reported. See KBA 2890281.
821225 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'bt__logandinsdel' together with a stacktrace which includes the modules 'onlutl_logical_sync' and 'cri_bldindex' may be reported in the SAP ASE error log when running CREATE INDEX with ONLINE on a data-only-locked table while concurrent DELETE statements are executed on the same table. See KBA 2944725.
821705 In rare circumstances, at timeslice error in the module 'parame_search_plan_by_sym' together with a stack trace may be reported in the SAP ASE error log when a SELECT query from a view that has a large IN list with all host variables is executed and the statement cache is enabled. See KBA 2926798.
821795 In rare circumstances, a 834 error, "Illegal attempt to clean buffer: BUF= < value > , MASS= < value > , ...", may be reported in the SAP ASE error log whereby the given object descriptor is left in destroy state 'DBST_DESTROY' which will cause other sessions that are accessing this object to hang. See KBA 3111328.
821967 A 567 error, "You must have the following role(s) to execute this command/procedure: < role_name > . Please contact a user with the appropriate role for help.", may be reported when sp_dbcc_deletehistory is executed by a user who is aliased as dbo to the given database. See KBA 2938063.
822035 In some circumstances the execution of selected queries in 16.0 ASE setups may perform slower than in 15.7 ASE setups. See KBA 2967838.
822656 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'dol_ncdelete' together with a stack trace which includes the modules 'attrib_delrows' and 'etc_cleanup_task' preceded by the message, "ssl_server_handshake: ... FAILED ...", may be reported in the SAP ASE error log when an SSL connection fails to login to Adaptive Server. See KBA 2964957.
822952 Queries executed on remote tables don't release BLOB locator memory on remote SAP ASE server right after execution until disconnection time. See KBA 2973829.
823238 A 15432 error, "A validation check failed when Adaptive Server decrypted an encryption key. This error may indicate an incorrect password", may be reported when ALTER TABLE command to encrypt/decrypt a column of a table with key copy is replicated. See KBA 3111510.
823929 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 's_check_target' together with a stack trace including the modules 's_execute' and 'execproc' may be reported in the SAP ASE error log during the execution of a query. See KBA 2803094.
824059 The LTL multi-thread Rep Agent can't be stopped after receiving SRS error 14040, "Replication Agent for < server-name > . < database-name > has been Suspended. Disconnecting Replication Agent.". Rep Agent appears down in SRS but it is still running in ASE, and sp_stop_rep_agent or kill have no effect.
824106 A new column, Status is added into the MDA table monProcess to show the current status of a process. See KBA 3017136.
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.
824152 A new configuration option ‘max cached stmt size’ is introduced to SAP Adaptive Server which indicates the maximum size of SQL statements that can be saved in statement cache. The default value is 16k bytes, which means that SQL statements having size greater than this are not saved in the statement cache.
824186 In rare circumstances, a 8213 error, "Failed to acquire address lock on object < object-name > " can be seen when performing inserts on a table containing an identity column and the database containing the table has an active DUMP DATABASE running and a concurrent DUMP TRAN has failed. See KBA 2157709.
824349 An incorrect result may be seen with a parallel query plan execution for a SELECT query that involves “ < column > LIKE < @variable > " predicate where the same < column > is used in an index and in a join condition and the LIKE optimization happens along with transitivity closure(TC). If required the fix can be disabled by turning on the optimization criteria "optlike_tc" so to allow such transitivity closure for like predicate optimization.
824378 The message, “Current process infected with signal 11 (SIGSEGV)”, in the module ‘iocRunController’ together with a stack trace which includes the modules ‘nthrd_backtrace’ and ‘krtctskException’ may be reported in the SAP ASE error log causing an Adaptive Server hang. See KBA 2758257.
824396 SAP ASE may consume lots of memory from the stored procedure cache when the built-in show_condensed_text(SSQLID, 'text') is executed on an Adaptive Server that has many statements cached in the statement cache.
824441 In rare circumstances, Adaptive Server sessions may hang when DISK MIRROR is taking place and extensive I/O operations are in progress. See KBA 3096706
824464 In rare circumstance, the message, "Current process infected with signal 11 (SIGSEGV)", followed by a stacktrace that includes the modules mda_fill_and_send_monProcessObject may be reported in the SAP ASE error log when the monProcessObject MDA table is queried. See KBA 3043251
824465 In some circumstances, the execution of queries involving Data Only Locked tables (DOL) in 16.0 ASE setups may perform slower than in 15.7 ASE setups. See KBA 2893425.
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.
824730 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'PopDistinct < ParallelCost, ParallelProps > ::_popConsGroupOrdering()' together with a stack trace which includes the modules 'OptGlobal::GblOptimize' and 's_compile_stmt' may be reported in the SAP ASE error log when a SELECT query using ROWS LIMIT option is executed. See KBA 3054992.
824738 The error message, "A00: SYBMULTBUF ERROR: In basis_get_membufs, failed to create shared memory segment for I/O buffers. shmget call failed with system error=No space left on device", may be reported in the SAP Backupserver error log when DUMP command is executed.
824810 A 9239 error, "Cannot allocate < size > bytes of memory and will sleep until memory becomes available. Rep Agent Thread: Scanner-syslogs, status: starting / not sleeping. Contact a user with System Administrator (SA) role to reconfigure Adaptive Server with more memory for Replication.", may be reported in the SAP ASE error log after Replication Server is restarted or log transfer is suspended or Replication Agent is restarted. The number of bytes reported in the error message will be in the magnitude of 8 MB.
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.
824853 A new column, NetworkControllerID is added into the MDA table monProcessNetIO to show the Network Controller ID handling network I/Os for a process.
824859 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ResRelOp' together with a stack trace may be reported in the SAP ASE error log when a SELECT with group by having clause is executed whereby the disjunctive predicate in the having clause is a row constructor and the group by column list is not present in the projection list. See KBA 3086932.
824875 A 14216 error, "Function ' < function-name > ' not found. If this is a SQLJ function or SQL function, use sp_help to check whether the object exists (sp_help may produce a large amount of output).", may be reported when a user defined CREATE FUNCTION that calls another user defined function is created while the session option 'deferred_name_resolution' is enabled. See KBA 3069880.
824878 In rare circumstances, a 14315 error, "Error while inserting text into syscomments for partition condition < value > in database < value > for table < value > , indid < value > .", together with a stack trace which includes the modules 'ptnc__fill_syscomments', 'ptnc__fill_syscomments' and 'crt_main' may be reported in the SAP ASE error log when there is no free space available in the database while creating a table with partitions or creating new partitions for a table.
824883 The execution of a prepared statement may return no rows unexpectedly when the statement cache is enabled and the SELECT query has a where clause for a numeric column and host variable such as ‘numeric_column = ?’. See KBA 3075839
824907 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ra_ci_init_native_thread' together with a stack trace which includes the modules 'ci_thread_create' and 'MSProducerStartXPort' may be reported in the SAP ASE error log in an HADR setup after Replication Server is restarted, log transfer is suspended, or Rep Agent is restarted. See KBA 3102581.
824958 In rare circumstances, the message, "timeslice < negative-value > , current process infected", in the module 'pausenonatomic' together with a stack trace which includes the modules 'bufgrab' and 'getpage_with_validation' may be reported in the SAP ASE error log during the execution of a query. See KBA 3111464.
824962 The message text for error 4325 and error 4354 have been enhanced to indicate that the LOAD TRAN command has failed when the option with UNTIL_TIME has been used with an invalid value.
824973 In rare circumstances, a timeslice current process infected error in the module 'crt_upd_col_nullability' together with a stack trace which includes the modules 'crt_main' and 's_execute' may be reported in the SAP ASE error log during the execution of a query. See KBA 3066887.
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.
825014 Enhancements made in DBCC DBREPAIR for option 'fixtimestamp' to patch the timestamp value of each page belonging to an allocated extent, as well use a better I/O mechanism to increase disk throughput.
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.
825022 When timestamps in a database approach the maximum limit, a 935 error, “WARNING - the timestamp in database ‘ < database-name > ’ (0x < 2-bytes > , 0x < 4-bytes > ) is approaching the maximum allowed. < percentage-value > % of the emergency reserve timestamps remain before the database is shut down automatically. Please contact SAP Technical Support.”, will be reported in the SAP ASE error log, preceded by “Error: 935, Severity: 19, State: < 1|3 > ” therefore allowing admin tools searching on high severity values in the ASE error log to alert consequently the database administrator.
825025 The message, "Invalid column length: < value > . Value must be between 0 and < value > at offset < value > for < value > row with minimum row length of < value > .", together with a stacktrace which includes the modules 'collocate', 'LeSubst__getcolval' and 'exectrig' may be reported in the SAP ASE error log during UPDATE execution when the base table has an update trigger defined and the update command is performed after the table is altered. See KBA 3079830.
825049 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'deletetext' together with a stack trace which includes the modules 'omni_text_free', 'omni_text_recover' and 'onl_online_db' may be reported in the SAP ASE error log when INSERT commands into a proxy table having LOB columns have failed and Adaptive Server is restarted. See KBA 3070215.
825062 A new attribute "read_only" has been added to be used with sp_chgattribute for a table. When enabled data manipulation cannot be done on the respective table.
825084 In rare circumstances, a 6401 error, "Cannot rollback Invalid pointer param number 2, pointer value 0x < value > - no transaction or savepoint of that name found.", may be reported when DISK RESIZE execution fails. See KBA 3096682.
825148 When the SAP ASE configuration option 'enable functionality group' is on, Adaptive Server will allow dropping of a global temporary table even if its status indicates that it is in use by another session.
825166 In rare circumstance, SAP ASE Workload Analyzer may fail to replay some statements if they have dependency on some other statements in a different session.
825204 In rare circumstances, Adaptive Server may implicitly shutdown with the message, "Spinlocks held by taskblock", being reported in the SAP ASE error log, when one of the I/O controller task or any other RTC task hits a signal and a spinlock is held by any other user task. See KBA 3083007.
825234 A 4246 error, "Warning: DUMP TRAN WITH NO_LOG is disallowed while in bypass recovery mode since data inconsistencies beyond human repair may occur in this database! Execute 'dump tran < database-name > with no_log, force_key= < value > ' to bypass the restriction at your own risk!", will be reported when the end-user attempts to truncate the log of database that was in bypass recovery mode. The action whereby the force_key option is eventually used will be logged in the SAP ASE error log.
825236 A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is 16384.", or a 9219 error with state 58, "RepAgent( < database-id > ): Internal error.", may be reported in the SAP ASE error log when replicating a large number of concurrent DML commands on replicated LOB columns that will cause the Rep Agent to terminate abnormally.
825241 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'sddostats' together with a stack trace which includes the modules 'sdfinish_normal' or 'sdfinish_mirrored' may be reported in the SAP ASE error log after an I/O error is reported "sddone: {read|write} error on virtual disk < value > block < value > " and the configuration "enable monitoring" is enabled. See KBA 3079874.
825255 In an HADR setup, when SAP ASE Rep Agent performs a mode switch to 'async' while the stream is concurrently being closed, the message, "Current process (0x0) infected with signal 11 (SIGSEGV)", may be reported in SAP Adaptive Server error log together with a stack trace which includes the modules 'STSendMsgs', 'ra_ci_send_mode_switch_message' and 'ra__ci_background_task_wait_for_srs_ack'. See KBA 3112081.
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.
825390 In rare circumstances, the execution of a stored procedure may fail silently when the stored procedure creates a temporary table and references a SQL UDF that is accessing this temporary table while the stored procedure was created with the configuration option "deferred name resolution" enabled.
825394 SELECT DISTINCT on a large number of columns hangs in COMPILING state and uses up procedure cache resulting in high cpu utilization. See KBA 3089126.
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.
825423 The message, "Current process infected with 11 (SIGSEGV)", in the module 's_mustrecompile' together with a stacktrace which includes the module 'curs_execute' may be reported in the SAP ASE error log when a dynamic prepared statement is executing with an implicit cursor on a select statement. See KBA 3092626.
825691 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'scan_resource_cleanup' together with a stack trace which includes the modules 'cri_scan' and 'cri_main' may be reported in the SAP ASE error log if CREATE INDEX raises an error.
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.
825725 A 456 error, "Failed to execute USE DATABASE, because this is a read-only connection. Read-only connections can only execute SELECT statements. Use 'set readonly off' to execute USE DATABASE.", may be reported by SAP ASE Workload Analyzer when a workload containing DML statements is replayed against 16.0 SP04 or 16.0 SP04 PL01 Adaptive Server. See KBA 3110948.
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.


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 SP04 PL02, ASE SP04 PL02, SP04 PL02 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.