/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
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 Number | Description |
|---|---|
| 665006 | The audit event for shutdown command has been enhanced to distinguish between the shutdown action of Adaptive Server and Backup Server. |
| 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. |
| 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. |
| 799714 | LTL Rep Agent enhancements to support Replication Server Kerberos principal name. This feature is enabled by LTL Rep Agent configuration option 'rs principal'. |
| 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. |
| 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. |
| 817367 | Enhancements to dbcc dbrepair() interface to accept dbid as paramter. |
| 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 |
| 818848 | DBCC HELP does not provide syntax for DBCC SHRINKDB_SETUP. See KBA 2787004. |
| 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. |
| 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. |
| 819571 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'blkioStartIO' together with a stack trace which includes the modules 'adb__doio' and 'adb__rdwr_page' may be reported in the SAP ASE error log when loading an archive database and the configuration value for option 'disk i/o structures' is not sufficiently set up. See KBA 2814538. |
| 819738 | SAP Adaptive Server and Replication Server are enhanced to support the replication of 'update statistics' and 'delete statistics' commands under an HADR setup. |
| 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. |
| 820463 | A 1295 error, "Unconditional lock request for table or page < page-number > , dbid < database-id > was made while holding a latch.", in the module 'lock__semawait' together with a stack trace which includes the module 'dmpx_truncatemain' and 'dmpld_acquire_dumpdb_lock' may be reported in the SAP ASE error log during DUMP TRANSACTION when during an earlier attempt 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.", was reported. See KBA 3157033. |
| 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. |
| 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. |
| 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. |
| 821377 | The new columns for 'BucketNo', 'ChainPosition', 'ChainLength', 'SpinlockName' and 'SpinlockSlotID' are added in the MDA table 'monLocks'. |
| 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. |
| 822069 | The message, "FATAL UNHANDLED EXCEPTION: signal 0 hit while handling a previously hit signal. The server cannot continue and will shut down.", may be reported in the SAP ASE error log while Adaptive Server was dealing with an initial signal error resulting into an implicit ASE shutdown. See KBA 2953080. |
| 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. |
| 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. |
| 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). See KBA 3140740. |
| 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. |
| 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. |
| 823298 | The default value of the SAP ASE configuration option 'dump history filename' is 'dumphist'. This filename value can be changed to 'dumphist. < ASE-server-name > ' when executing sp_configure ‘dump history filename’, 1. It can be set back to 'dumphist' when executing sp_configure ‘dump history filename’, 0. |
| 823473 | SAP Adaptive Server is enhanced to support capturing or replaying a workload on a HANA Cloud ASE instance. |
| 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 | 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. |
| 823778 | A 702 error, "Memory request for < number > bytes exceeds the size of single page of 16384 bytes.", may be reported in the SAP ASE error log during the execution of a join between two SQL-derived tables. The left one SQL-derived table is defined by 'SELECT DISTINCT' and the other one SQL-derived table is defined by 'SELECT GROUP BY'. See KBA 3086892. |
| 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. |
| 824156 | A new configuration option 'sqlfunc syntax valid' is introduced to SAP Adaptive Server which determines whether extended syntax validations will be performed for SQL functions. The default is false, which means extended syntax validations will not be performed for SQL functions. See KBA 3134291. |
| 824160 | A new configuration option ‘print stack overflow info’ is introduced to SAP Adaptive Server which provides a stacktrace when a transaction is aborted due to insufficient stack space that can provide additional diagnostics on stack usage by the query. The default value is 0, which means additional stack overflow information is not printed. KBA 2602934 |
| 824162 | The new value of 2 is added to the SAP ASE configuration option ‘enable console logging’ which disables console logging if opening the console in non-blocking mode fails. KBA 3133899 |
| 824170 | Sybdiag may not report correct "I/O Statistics" information in view/osdata/OSI_IO_content.xml when it is executed on some Linux servers which kernel version is higher than 2.x. |
| 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. See KBA 3140755. |
| 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. See KBA 3140745. |
| 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. |
| 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. |
| 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. See KBA 3143404. |
| 824680 | SAP Adaptive Server logins using LDAP authentication may become locked if the configuration option 'maximum failed logins' is enabled and the LDAP server is not available. See KBA 3051029. |
| 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. See KBA 3089993. |
| 824883 | The execution of a prepared statement may return no row 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. |
| 824951 | A 515 error, "Attempt to insert NULL value into column < column-name > , table < table-name > ; column does not allow nulls. Update fails...", may be reported during a trigger execution if the value to be inserted in the target table is the default value of a non-materialized column of the source table. See KBA 3065843. |
| 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. |
| 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 on Unix platforms 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. |
| 825021 | A 644 error, "Index row entry for data row id < page-number, row-number > is missing from index page < page-number > of index id < index-id > of table < object-id > in database < database-id > . Xactid is < page-number, row-number > . Drop and re-create the index.", may be frequently reported in the SAP ASE error log when a high number of DELETE and INSERT batches are concurrently executed. See KBA 3069024. |
| 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. See KBA 3138485. |
| 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. |
| 825052 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'res_type' together with a stacktrace which includes the modules ‘res_type’, ‘res_col’, 'crt_tabvar_cols' and 'crt_tabvar_main' may be reported in the SAP ASE error log when a local variable uses a user defined data type that has the same name of an existing rule. See KBA 3070388. |
| 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. |
| 825063 | On heavily-loaded SAP ASE systems, a high spinlock contention on spinlock SSQLCACHE_SPIN may be observed when the Adaptive Server available procedure cache memory is reduced due to a large amount of triggers having been created. See KBA 3150098. |
| 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. |
| 825150 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'encr_reencrypt_key' together with a stack trace which includes the module 's_decrypt_keys' may be reported in the SAP ASE error log when a client using Kerberos authentication accesses a table with one or more encrypted columns. See KBA 3075374. |
| 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. See KBA 3140756. |
| 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. |
| 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. See KBA 3139002. |
| 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. See KBA 3138973. |
| 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. |
| 825249 | After database reload or SAP ASE upgrade a query referencing a view that has the same name as some table referenced by this view may loop endlessly trying to resolve the object id of the table referenced by the view. See KBA 3088292. |
| 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. |
| 825261 | The "Logical Process Manager Warning" messages which are reported in the SAP ASE error log for sessions having execution bindings and encountering errors such as 1204, 1295 or holding latches at the time of an error is hit will be suppressed when ASE trace flag 1239 is in use. See KBA 3079851. |
| 825302 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'res_insert' together with a stacktrace which includes the module ‘yyparse’ may be reported in the SAP ASE error log when a language prepared statement containing many batches of statements along with thousands of parameters is executed. See KBA 3082610. |
| 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.". See KBA 3143378. |
| 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. See KBA 3121124 |
| 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. |
| 825395 | In an HADR setup, the primary server fails to be activated when it is rebooted after having executed the RMA command sap_disable_replication. |
| 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. |
| 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. |
| 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. |
| 825563 | Workload analyzer command line utility can support replay with JTW token by inputting a JWT token in replay wizard when asked to provide password for captured sessions. |
| 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. |
| 825678 | The scheduled tasks in SAP ASE Job Scheduler which are created by sybmgmtdb..sp_sjobcreate while using the @option for dates will be reported by sybmgmtdb..sp_sjobhelp with an incorrect ‘on days’ value. |
| 825684 | In rare circumstances, SAP Adaptive Server Rep Agent may not be stopped due to a stream replication native thread sleeping on exit on which the Rep Agent is dependent while the configuration option 'enable pci' is on. See KBA 3150546 . |
| 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. |
| 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. |
| 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. See KBA 3140741. |
| 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. |
| 825783 | In some circumstances, SAP Adaptive Server may not use the cipher that was established by sp_ssladmin system stored procedure and option 'setcipher'. See KBA 3114815. |
| 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. |
| 825795 | Logins with expired passwords which authenticate with SAP ASE authentication are allowed to execute commands while the configuration 'enable pam user auth' is set to 1. See KBA 3112160. |
| 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. See KBA 3143387. |
| 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. See KBA 3143377. |
| 825858 | The "compare show < replay_name > " command in SAP ASE Workload Analyzer Command Line Utility is enhanced to report the capture and replay durations. |
| 825873 | The message, "Current process infected with 11 (SIGSEGV)", in the module ‘sendtext’ together with a stack trace which includes the modules 'LeSendRow::sendRowToClient' and 'exec_lava' 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.". |
| 825934 | The SAP ASE configuration option ‘temp table statement caching’ when set to true indicates that SQL statements which reference temporary tables will be saved in the statement cache. The default value is true which means that such SQL statements are saved in the statement cache. |
| 825935 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeSendRow::_sendColsToClient' followed by a stack trace which includes the modules 'LeSendRow::sendRowToClient' and 'exec_lava' may be reported in the SAP ASE error log when a SELECT query retrieves an in-row LOB column whose value has been previously updated to NULL from a non-NULL value. See KBA 3157053. |
| 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. |
| 826025 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'TraceOut::operator' together with a stack trace which includes the module 'ShowStmtHeader' may be reported in the SAP ASE error log when executing the built-in show_cached_plan_in_xml() against a prepared statement. See KBA 3138487. |
| 826036 | The SAP ASE configuration option 'sqlfunc syntax valid' is renamed to 'disable ext syntax validation'. This option determines whether to disable extended syntax validations. The default value is false, which means that extended syntax validations will be performed for SQL functions. |
| 826183 | Log4j 1.x is removed from SAP ASE/SRS/SDK. See KBA 3129897. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)