/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 SP03 PL11 . 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 |
|---|---|
| 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. |
| 798870 | On heavily-loaded systems, single spinlock usage to access the SQL statement cache can cause a performance bottleneck. Adaptive Server is enhanced to improve concurrent access to the SQL statement cache by using multiple spinlocks. See KBA 2319667. |
| 807655 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeRowBuffer::addRowLen' together with a stacktrace which includes the modules 'LePlanClose' and 'exec_lava' may be reported in the SAP ASE error log when MERGE INTO command is executed. See KBA 3087300. |
| 814416 | A 102 error, "Incorrect syntax near ' < value > '.", may be reported by the DSI thread on the standby ASE when SQL Statement Replication is enabled and the text of a SQL statement executed on the primary ASE is larger than 16K bytes. See KBA 2521419. |
| 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. |
| 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. |
| 819964 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LePlanOpenAndExecute' together with a stack trace which includes the modules 'LeAlignedDataRow::readRow', 'LeHashBufferReader::GetNext' and 'LeHashOFileOp::_LeOpNext', may be reported in the SAP ASE error log a SELECT query which includes a subquery that contains a group-by clause referencing one or more correlated columns from an outer query block is executed. The new set option ‘group_hashing_buffer' when enabled will avoid this problem from occurring. See KBA 2889759 |
| 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. |
| 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. |
| 821702 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module "stphd_reprioritize" together with a stack trace may be reported in the SAP ASE error log when CREATE INDEX without hash option is executed in parallel mode and the configuration option 'utility statistics hashing' is disabled. See KBA 2960219. |
| 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. |
| 822232 | The message, “Current process infected with signal 11 (SIGSEGV)”, in the module ‘row_delete’ together with a stack trace which includes the modules ‘lobj_droplogin’ and ‘lobj_droploginmain’ may be reported in the SAP ASE error log when DROP LOGIN WITH OVERRIDE is executed. See KBA 2947086. |
| 822372 | Total Priority Changes in sysmon reporting high counts in ASE 16.0 SP03 PL07 compared to ASE 16.0 SP03 PL04 - KBA 3048136 |
| 822390 | The message, "FATAL UNHANDLED EXCEPTION: signal < #signal > hit while handling a previously hit signal. The server cannot continue and will shut down.", in the module 'LeProcessExecStats' together with a stack trace which includes the modules 'LePlanRelease' and 'exec_lava', may be reported in the SAP ASE error log when executing SELECT SHOW_PLAN(). See KBA 2961133. |
| 822621 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'showplan' together with a stack trace which includes the modules 'sequencer' and 's_compile' may be reported in the SAP ASE error log when sp_showplan is run while it is retrieving the query plan of a stored procedure that is being executed by EXECUTE @procname and the variable size is bigger than 300 characters. See KBA 3031276. |
| 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. |
| 822659 | The message, "Sybmon encountered signal 11 at address", in the module 'pcstkwalk' together with a stack trace which includes the modules 'monbacktrace' and 'md_profile_server' may be reported when the "profile" command is executed in SAP ASE sybmon utility. |
| 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). |
| 822932 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", in the module 'ns__pop_brset' together with a stack trace which includes the modules 'ns_close_stmnt' and 'get_datachange' may be reported in the SAP ASE error log when running the datachange() built-in. See KBA 2973356. |
| 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. |
| 822961 | When the configuration option "enable granular permissions" is disabled, even if "sp_audit 'security', 'all', 'all', 'on'" is executed, then audit records of some system procedures may not be written in the sysaudits_01 system table. See KBA 2975656. |
| 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. |
| 823281 | A 19083 error, "Procedure sp_sjobcontrol, you do not have permission to access the specified scheduledjob, job, schedule or running job - @name.", may be reported when a login with js_admin_role attempts to disable a job from another login using 'all_users' option. See KBA 2984063. |
| 823344 | In rare circumstances, an incorrect result set may be returned when querying a table with page compression enabled. See KBA 2986752. |
| 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. |
| 823954 | A 241 error, "Scale error during implicit conversion of NUMERIC value '0. < zero-padded-value-of-38-decimal > ' to a NUMERIC field.", may be reported when an INSERT is executed whereby a local variable which is defined as a numeric is being used for the row insertion while the statement cache and the flag 11013 are enabled. See KBA 3011627. |
| 824041 | In rare circumstances under a single engine Adaptive Server system, a high priority process may hang during DML execution when allocating a new syslogs page while another, relatively low priority, process concurrently allocates a new data page and is yet to validate it, in the same mixed log and data database. The first process will be hanging in the module ‘pg__allocate_syslogs_extent’ and the second process in the module ‘getpage_with_validation’. See KBA 3015981. |
| 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. |
| 824082 | A 4218 error with state 2, "Failure during DUMP of database < database-name > : serial log page allocation rules broken...", may be reported by SAP ASE when the built-in lct_admin('num_logpages', < database-id > ) is run against a mixed-log-and-data database. See KBA 2935506. |
| 824104 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'Snap::Validate()' together with a stack trace that includes the modules 'SnapValidation' and 'dsinit', may be reported in the SAP ASE error log when booting Adaptive Server. See KBA 3018138 |
| 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. |
| 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. |
| 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. |
| 824165 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'tds_send' together with a stacktrace which includes the modules 'openremote' and 'dpdb_main' may be reported in the SAP ASE error log during the execution of DUMP DATABASE USING CONFIG= < config-name > whereby the option 'number of retries' is set and the session is killed resulting in the connection to Adaptive Server being lost. See KBA 3060285. |
| 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. |
| 824210 | A SELECT query that is mixing regular views and in-lined TUDFs may sometimes return incorrect results. See KBA 3087319. |
| 824232 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'crv_main' together with a stacktrace which includes the modules 'tmp_crv' and 's_normalize' maye be reported in the SAP ASE error log when CREATE VIEW using a large number of UNION operators is executed. See KBA 3059990. |
| 824246 | In rare circumstances, when SIGSEGV is caught in optimizer by VEH handler function VEH_Optimize(), and subsequent SIGSEGV happens in function release_compiler_scratch_space() due to memory corruption, that causes VEH handler function to encounter another kisignal over and over until we ran out of time and timesliced. See KBA 3087291. |
| 824268 | When DISK MIRROR is running on SAP Adaptive Server, it will prevent DUMP TRANSACTION and DUMP DATABASE from being executed. See KBA 3029188. |
| 824330 | The message, "Current infected with signal 11 (SIGSEGV)", in the module 'ra_end_tran' together with a stack trace which includes the modules 'ra_free_all_raxacts' and 'ra_close_context' may be reported in the SAP ASE error log when Rep Agent receives error 9284 "Cannot allocate 32768 bytes of memory. You may need to reconfigure the parameter 'replication agent memory size' with more memory.", and it is configured for Multiple Paths Replication using Multiple Scanners with at least two replication paths defined. See KBA 3033751. |
| 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. |
| 824395 | The message, "Lock log failed for db 2. error=-12", may be reported in the SAP ASE error log when a resource governor limit has been crossed in system tempdb, followed by 4215 errors with state 1, "DUMP TRANSACTION failed in database tempdb: < page-# > not first log page in serially allocated log extent or allocation page. Should be: < page-# > . Previous log record in scan: < page-# > .", whenever an attempt to truncate the transaction log of system tempdb is attempted. See KBA 3046131. |
| 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. |
| 824416 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'open__byname' together with a stacktrace which includes the modules 'omni_opt_like' and 'dso_opt_like' may be reported in the SAP ASE error log when executing a table-valued SQL UDFs that performs a LIKE search argument against a table variable column. See KBA 3040803. |
| 824436 | The message, "attempted read from memory location < memory-location > from instruction at location < memory-location > ", followed by the message, "Backup Server system exception < memory-location > generated by a storage access violation", in the module 'MapViewOfFile' together with a stack trace which includes the modules 'CreateMutex' and 'syb_vsnprintf' may be reported in the SAP Backupserver error log while booting the Backupserver on Windows. |
| 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 |
| 824459 | Implement faster EXECUTE statement compilation. This optimization is enabled with ASE trace flag 11028. |
| 824462 | The error message, "Backup Server: 4.141.2.66: [0] The 'write' call failed for database/archive device while working on stripe device < stripe-device-path > with error number 32 (Broken pipe). Refer to your operating system documentation for further details.", may be reported in the Backupserver error log when DUMP DATABASE is executed. See KBA 3061896. |
| 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. |
| 824485 | The message, "Shutting down Rep Agent for database, ' < database-name > ' (dbid = < database-id > )", followed by error 9414, "RepAgent( < database-id > ): Streaming replication stream CI Library error -1 with severity 2 and message ' < CI-error-message-text > '. Rep Agent detected error 3 with message ' < error-message-text > ' at line < line-number > in file ra_ci_scanner.c.", may be reported in the SAP ASE error log after Replication Server is restarted or log transfer is suspended immediately after SAP ASE Replication Agent is started. See KBA 3067419. |
| 824491 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'ra_malloc_mempool' together with a stacktrace which includes the modules 'ra_ci_sync_wakeup_insert' and 'syslogs_finishlog' may be reported in the SAP ASE error log when a Rep Agent is shut down while a remote procedure call is being committed by the ASTC Handler. See KBA 3043915. |
| 824545 | The error message, "Backup Server: 4.142.2.92: [0] The 'CloseHandle' call failed with error number 6 (The handle is invalid). Refer to your operating system documentation for further details.", may be reported in the Backupserver error log on Windows when "backupserver.exe -v" is executed to display the Backupserver version. See KBA 3060452. |
| 824661 | The warning message printed in the ASE log during thread creation does not print operating system stack size in use when the limit 'stacksize' is greater than two megabytes. |
| 824669 | A 6908 error, “During redo the page timestamp value is less than old timestamp from log. Page #= < page-number > , object id = 99, page timestamp= < timestamp-value > . Log old timestamp= < timestamp-value > .”, may be reported during the redo phase of LOAD DATABASE or LOAD TRANSACTION execution. See SAP Note 3050714. |
| 824670 | A 3193 error, "Database < database-name > does not have space allocated for page < page-id > from the dump. Extend the database by < size > MB and retry the command.", may be reported with incorrect number of megabytes when loading a transaction dump which has a log record that refers to a data page that resides in a data hole. See KBA 3050445. |
| 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. |
| 824710 | Enable access rule to reference multiple variables. Mapping between variables in the RULE and columns in the table is done based on the name. @col variable will reference column named 'col'. This functionality is enabled with ASE trace flag 134. |
| 824723 | A 3606 error, "Arithmetic overflow occurred", may be reported when executing sp_helpcache on a system with very large caches configured. See KBA 2402812. |
| 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. |
| 824787 | A 823 error, "I/O error detected during read for ...", may be reported during CREATE DATABASE when an encrypted database is used as a template database for another user database. |
| 824795 | A 806 error, "Could not find virtual page for logical page < page-number > in database < database-name > .", may be reported in the SAP ASE error log during the execution of a SELECT query whereby a worktable is required to sort a column whose size is close to the maximum width of a data row that can fit on a data page and there are NULL values in the sorted column. Alternatively a 614 error, "Adaptive Server accessed a row that has an illegal length of 0 while in database < database-name > . Page pointer = < page-address > , pageno = 24, status = 0x1, ptnid = -1, indexid = 0, level = 0. The minimum row length is < value > . The page size is 2048.", may be reported. See KBA 2531140. |
| 824800 | Under some circumstances, SAP ASE Workload Analyzer may fail to analyze a replay workload and the messages, "Thread < tid > failed to read RawTDS for session < sessionid > " and "No resultset found for stored procedure p_showalltds", may be reported in WLACLIUtil console window and log files. See KBA 3060283. |
| 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. |
| 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 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 |
| 824884 | Export workload/comparison might hang without reporting error while error message "The maximum length of cell contents (text) is 32767 characters" can be found in SAP ASE error log. KBA 3119619 |
| 824886 | In rare circumstances, SAP Adaptive Server error log rollover operation when the configuration option 'error-log-size' is enabled may fail and ASE may stop receiving any messages in the error log. A backup file created during rollover operation with name like errorlog_bak. < timestamp > could be seen. |
| 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. |
| 824917 | When setting the Kerberos principal name of a remote server with principal name greater than 20 characters using sp_serveroption "server principal" option, the value is truncated to 20 characters. This results in connection failure for Kerberos connections to remote server. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 825249 | After database reload or 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. |
| 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. |
| 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. |
| 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. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 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 PL11, ASE SP03, SP03, PL11, 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)