/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 PL01. 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 |
|---|---|
| 489340 | When inserting data into a TIMESTAMP column and the source data is the result of an aggregate built-in, SAP ASE will incorrectly insert into this column the current timestamp value rather than the source data. See KBA 2408246. |
| 538343 | When UPDATE STATISTICS is executed an incorrect value of extent0pgcnt column may be stored in the system table systabstats. See KBA 3079771 |
| 683438 | DBCC EXTENTDUMP is enhanced to report the OAM page number of an extent. |
| 700495 | A 7210 error, "Can't open a connection to site ' < remote-ASE-server-name > ' because 'set up channel' message could not be sent.", may be reported when execution a remote stored procedure call when the remote server has either option 'net password encryption' or 'net password encryption reqd' enabled. See KBA 3060930. |
| 702153 | The built-in user_name() may display an incorrect user name after a cross-database execute as owner stored procedure is run from within a parent stored procedure. |
| 705151 | The execution of SELECT count(*) on very large tables may return an inaccurate or negative value. See KBA 2056252. |
| 749621 | When sp_dump_history with "purge" option is executed, SAP Adaptive Server does not report the number of records that have been purged nor the dump history backup file name that has been created. |
| 773057 | In rare circumstances, the message, “Assertion (0) failed in file memory.c”, together with a stack trace which includes the modules 'css_deallocate' and ‘memfree’ may be reported in the SAP ASE error log when a cursor with a large query text whose length is greater than 16KB and less than or equal to 2MB bytes is deallocated and the diagserver binary is in use. |
| 774152 | Whenever threadpool size is reduced using ALTER THREAD POOL command, it leads to 'kernel resource memory' leak. See KBA 2750513. |
| 778898 | The stored procedure "sp_dboption" is enhanced to log changes done to database options into ASE errorlog. |
| 786753 | The message, “Current process infected with signal 11 (SIGSEGV)”, in the module ‘_lopConsWktAccess’ together with a stack trace which includes the modules ‘_lopConsJoins’ and ‘s_compile_stmt’ may be reported in the SAP ASE error log when running a select query with joins and union all. See KBA 2190172. |
| 792860 | The system stored procedure sp_opt_querystats is enhanced to support user defined optgoals and transaction isolation level when reporting information about the optimization of a query. |
| 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. |
| 799240 | The message, “Current process infected with signal 11 (SIGSEGV)”, together with a stack trace which includes the modules ‘altdb__divide_diskmap’ and ‘altdb_shrink’ may be reported in the SAP Adaptive Server error log when ALTER DATABASE command with the "off" option is executed to shrink a database. See KBA 2323410. |
| 799714 | LTL Rep Agent enhancements to support Replication Server Kerberos principal name. This feature is enabled by LTL Rep Agent configuration option 'rs principal'. |
| 802123 | In rare circumstances, when one or more data or log devices are corrupted, dropping a database using such device(s) may cause the session to be terminated and may corrupt the master database. |
| 804443 | An incorrect result set may be returned during the execution of a SELECT query which includes an ORDER BY clause on an expression and ROWS OFFSET and LIMIT options are also in use. See KBA 2408819. |
| 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. |
| 816960 | In rare circumstances, the message, "pcstkwalk: No more space in buffer to hold stack frames", may be seen in the SAP ASE error log while Adaptive Server is reporting a stacktrace. See KBA 2990589. |
| 818435 | In rare circumstances, on IBM systems LOAD operations may fail without a clear evidence that shows where the failure starts. Additional diagnostics have been added to the Backup Server to trace the events during the LOAD command execution accessible via trace flag -D16. See KBA 2757065. |
| 818726 | A 208 error, “ < table-name > not found. Specify owner.objectname or use sp_help to check whether the object exists sp_help may produce lots of output”, may be reported when a SELECT query is executed using an in-memory database while its associated template database is renamed using sp_renamedb. See KBA 3009019. |
| 818916 | In rare circumstances, a 2601 error, “Attempt to insert duplicate key row in object ' < table-name > ’ with unique index ‘ < index-name > ’ < additional-data > ”, may be reported when MERGE commands are concurrently executed. Adaptive Server trace flag 16844 when enabled will print diagnostics information in such cases. See KBA 2785836. |
| 819811 | A 2520 error, "Database named < database-name > not found; check sysdatabases", may be reported when DROP DATABASE ? is executed thru a prepared statement. See KBA 2823552. |
| 819834 | A 9992 error, "The actual number of rows ( < row-count > ) in DOL datapage < page-id > , partition ID < partition-id > , and count of #rows - 'nextrno' - < row-count > in the page header, do not match.", a 12308 error, "Internal error : Invalid row id (Row < row-id > , Page < page-id > ) encountered in the table ' < table-name > ' in database ' < database-name > '.", a 2512 error, "Table Corrupt: Cannot find the specified row number < row-id > , in index page < page-id > , partition ID < partition-id > , on data page < page-id > .", and a 7928 error, "Index < index-name > is not consistent; found < row-count > leaf rows but < row-count > data rows. Drop and recreate the index.", may be reported by DBCC CHECKTABLE when a Data Only Locked (DOL) data page is found to be invalid. See KBA 2889757. |
| 819937 | In rare circumstances, SSL connections to SAP Adaptive Server may not complete their login phase and hung. The execution of sp_who will show the corresponding server processes in 'MAINTENANCE TOKEN' command mode. See KBA 2832542. |
| 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 |
| 820103 | A 8201 error, "Keep count of descriptor (objid= < object-id > , dbid= < database-id > ) was expected to be 1. Instead 0 was found.", together with a stack trace which includes the modules 'des_unkeep' and 'ptngetpages' may be reported in the SAP ASE error log during the execution of built-in data_pages() when the Adaptive Server configuration option 'number of open objects' is under configured. See KBA 2884324. |
| 820149 | A 10353 error, "You must have any of the following role(s) to execute this command/procedure: 'sa_role, sso_role'. Please contact a user with the appropriate role for help.", may be reported when sp_dump_history is executed by a user having the 'oper_role' granted. See KBA 2844541. |
| 820188 | When Rep Agent is configured for Multiple Paths Replication using Multiple Scanners, it ignores the abnormal termination of a Scanner thread or a Sender thread. |
| 820488 | The message, "current process infected with 11 (SIGSEGV)", in the module 'qry_init_stats' together with a stack trace may be reported in the SAP error log when a derived table in a SELECT query is aliased with the name of an existing temporary table, and the configuration option 'optimize temp table resolution' is enabled. See KBA 2862371. |
| 820661 | In some circumstances, a performance drop may be observed with SAP ASE 16.0 release, when a large batch of DELETE commands is executed and an index scan is chosen to perform the query. This can be worked around at the session level by executing ‘set postcommit_shrink off’ before the batch execution to disable the post-commit index page shrink chores. See KBA 2870613. |
| 820832 | In rare circumstances, a 692 error, “Uninitialized logical page ‘ < page-number > ’ was read while accessing database ' < database-name > ’ ( < database-id > ), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8). Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘checkpoint_db’, ‘ckpt_need_new_record’ and ‘wrongpage’ may be reported in the SAP ASE error log when the database option "trunc log on chkpt" is being enabled and after ONLINE DATABASE is executed in a database that was already online. Alternatively, a 1251 error, “The dbinfo anchor in the database 'database ' < database-name > ' ( < database-id > )' is already locked by the task. Nested access to dbinfo anchor is not allowed. Lock was acquired in file 'loaddb.c' at line 2165. This is an internal error. Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘xact_commit’, ‘xls_preflush’ and ‘lock_psema’ may be also seen. See KBA 2878392. |
| 820930 | The message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'StColstat::StAdjustDensity' together with a stack trace including the modules 's_compile_stmt' and 'optimize' may be reported in the SAP ASE error log when a SELECT query is run while Adaptive Server evaluates an execution plan for the query. See KBA 2885841. |
| 821007 | In rare circumstances, the message, "Stack guardword corrupted", may be reported in the SAP ASE error log together with a stacktrace which includes the modules 'ucstackcrash' and 'exc_raise' when a stack overflow is detected and the trace flag 3601 is enabled. This may cause an implicit shutdown of Adaptive Server. |
| 821135 | A 874 error, "Process < process-id > is trying to unkeep buffer < buffer-address > (dbid: < database-id > , pageno: < page-number > ) without releasing the shared latch it holds on the buffer.", may be reported in the SAP ASE error log when executing DBCC CHECKTABLE and while the diagserver binary is in use. |
| 821261 | A 267 error, "object '## < table-name > ' cannot be found.", may be reported when attempting to access a global temporary table which was created in an IMDB temporary database. See KBA 2903472. |
| 821294 | In rare circumstances, the message "Stack overflow detected", together with a stacktrace which includes the modules 'ucstackcrash' and 'sy_kill_task' may be reported in the SAP Adaptive Server error log, although there is no actual stack overflow, when a process is forcibly killed while it is holding a spinlock. This will result in Adaptive Server shutting down implicitly. See KBA 2905701 |
| 821318 | Under rare circumstances, the message "timeslice < negative-value > , current process infected at kbfalloc" together with a stack trace that includes the modules 'create_destconst' and 'ss_texttounitext' may be reported in the SAP ASE error log when inserting a parameterized text value into a unitext column using a dynamically prepared statement. See KBA 2900443. |
| 821367 | The SAP ASE Rep Agent configuration option 'priority' is taken into consideration for the scanner process under an HADR setup. |
| 821523 | In rare circumstances, a 1159 error, "Attempt to locate LSA extent partition control block failed for dbid ' < database-id > ', objid ' < object-id > ', indid ' < index-id > ' and partition id ' < partition-id > '.", together with a stack trace which includes the modules 'soextfinish', 'undo_apl_aextent' and 'pg_ea_getextp' may be reported in the SAP ASE error log while executing a SELECT INTO query which internally attempts to create and sort a work table, but the internal transaction is being undone. See KBA 2986566. |
| 821588 | A 11283 error, "External file access is not enabled or not licensed", may be reported on Windows platform when sp_dump_history is executed. See KBA 2921227. |
| 821607 | In rare circumstances, SAP Adaptive Server may report in master..monCachedObject MDA table inaccurate values in CachedKB column when at least one large I/O pool is configured in data cache. See KBA 2923998. |
| 821632 | A 11080 error, "The definition tree (object id: < object-id > ) of computed column ' < column-name > ' is missing.", may be reported during the execution of a stored procedure which creates a temporary table with computed column and recompilation is happening while the configuration option "deferred name resolution" is enabled. See KBA 2923497. |
| 821696 | The information reported in column LogRecordsProcessed for MDA tables monRepScanners, monRepLogActivity and monRepScannersTotalTime may sometimes be inaccurate. See KBA 2964364. |
| 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. |
| 821756 | In rare circumstances, a 19206 error, "sp_shrinkdevice: Execute immediate SQL failed. SQL statement is: DISK RESIZE NAME = ' < device-name > ', SIZE = ' < size-value > '", may be reported in the SAP SAP error log while running sp_shrink system stored procedure and the resulting disk size is more than 2,147,483,647 bytes (2048 Mbytes). See KBA 2976897. |
| 821804 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'pci_tpminvoke_function' together with a stacktrace may be reported in the SAP ASE error log when a java program inserting into a java type column with PreparedStatement is executed. See KBA 2930886. |
| 821809 | The system stored procedure sp_monitorconfig when executed with option "number of remote logins” may report inaccurate values in columns ‘Num_active’ and ‘Max_Use’ which exceed the configured value for remote logins when a 7221 error, “Login to site ‘ < ASE-name > ’ failed.”, is frequently reported. See KBA 2932504. |
| 821833 | The message, "Warning: Cannot resolve LDAP function ldap_controls_free.", may be seen in the SAP Adaptive Server error log during the server bootstrap even if LDAP is not enabled. See KBA 2932575. |
| 821904 | A 13979 error, "Invalid pointer param number 2, pointer value 0x does not own any objects with type 'encryption key' in the current database, or no change is needed.", may be reported when executing "ALTER ENCRYPTION KEY userA.* MODIFY OWNER userB" and userA doesn't own any objects. See KBA 3067415. |
| 822016 | The message, "No server log file open; Using stderr for log", may be unnecessarily reported when the SAP Backup Server is booted. See KBA 2741519. |
| 822037 | A 4060 error, "Login name not found for suid < value > . Check and make sure an entry exists in Syslogins.", followed by a 10386 error, "SELECT BUILTIN permission denied on builtin set_appcontext, owner system administrator", may be reported when executing a procedure that contains a built-in function like set_appcontext() after changing ownership of the procedure to 'dbo' and the original creator of the procedure no longer exists. See KBA 2941381. |
| 822065 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'proc_release' together with a stack trace which includes the modules 'tdsrecv__dyndealloc' and 'tdsrecv__dyndealloc' may be reported in the SAP ASE error log when running a dynamic SQL statement. See KBA 2941048. |
| 822078 | Wrong results may be observed when table variables with identical names are used in different stored procedures. See KBA 3009033. |
| 822150 | Under rare circumstances, select query on the MDA table 'monBucketPool' may show the bucketpool used (BucketPoolUsed column) value is greater than bucketpool used max (BucketPoolUsedMax column). See KBA 3009051. |
| 822157 | DBCC CHECKSTORAGE reports fault 100029 with fault_state 44 on OAM pages that have invalid bits set in the page header status field. The recommended action of running DBCC CHECKTABLE does not fix the fault. See KBA 2949021. |
| 822205 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des_scavenge_for' together with a stack trace including the modules 'ptn__pdes_grab' and 'ind_ides_init' may be reported in the SAP ASE error log when Adaptive Server instantiates the metadata for a table in the metadata cache while the configuration option for 'number of open indexes' is under configured. See KBA 3009020. |
| 822230 | The message, “timeslice < negative-value > , current process infected”, in the module ‘exc__raise’ together with a stacktrace which includes the modules ‘lddb_main’ and ‘adb_read_all_stripes’ may be reported in the SAP Adaptive Server error log during the execution of LOAD DATABASE of an archive database dump. |
| 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. |
| 822256 | When MERGE is run on a table with a timestamp column, the timestamp column does not change when existing rows are updated. See KBA 2947932. |
| 822318 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'sdes_hookup' together with a stacktrace that includes the modules 'show_condensed_text' and 'col_open_range' may be reported in the SAP ASE error log when running built-in show_condensed_text(). See KBA 2950527. |
| 822324 | When the Adaptive Server option 'procedure deferred compilation' is enabled and the deferred compilation is processing a derived table in a system stored procedure, SAP ASE may incorrectly decide to recompile the procedure. See KBA 2969291. |
| 822373 | A new mechanism to recompile cached or prepared queries using outer joins is introduced in SAP Adaptive Server to allow optimal query plans creation based on the provided runtime parameters values. This mechanism is not enabled by default and can be enabled with trace flag 11025. See KBA 3037884. |
| 822380 | A 834 error with state 4, “Illegal attempt to clean buffer: < buffer-meta-data > ”, together with a stack trace which includes the modules ‘cm_dbclean’ and ‘lddb_main’ may be reported in the SAP ASE error log when LOAD DATABASE is executed. Alternatively the CHKPOINT WRKR process may hang in the module ‘cm__waitfor_io’ despite no active I/O presence. See KBA 2820054. |
| 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. |
| 822391 | In rare circumstances, a 2780 error, "maxlen( < value > is less than length ( < value > )", may be reported in the SAP Adaptive Server error log when an ALTER TABLE DROP COLUMN command followed by a SELECT command is executed. See KBA 3009034. |
| 822434 | A 3328 error, “Redo of 'CREATE INDEX' in transaction ID (0,0) for table name '', object ID '0' did not find 'sysobjects' system catalog log record. Recovery of database 'BLA' cannot continue.”, may be reported by LOAD TRANSACTION when loading a transaction dump that was taken after ASE was upgraded from SP02 to SP03 and a full database dump on SP03 was not taken first. This error is observed when the given database has the option 'enforce dump tran sequence' enabled. |
| 822444 | In a database setup for LTL replication, when Rep Agent is suspended, then resumed by executing the SRS administration commands 'SUSPEND LOG TRANSFER' and 'RESUME LOG TRANSFER', the message "process infected with signal 11" may be reported in the error log together with a stack trace which includes the modules 'kbfalloc', 'ra_malloc_mempool' and 'rep_agent_thread'. ASE eventually terminates. KBA 2958090. |
| 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. |
| 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. |
| 822660 | In rare circumstances, data between primary and standby might be inconsistent under an HADR setup with DRC replication enabled when two ALTER TABLE commands are executed on different tables followed by DML executed on reverse order on these two tables. |
| 822682 | In rare circumstances, a spid may hang with COMPILING status as shown by stored procedure sp_who, when executing a disjoint SELECT with LIKE operators. See KBA 2965623. |
| 822688 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'LeRun' may be reported in the SAP Adaptive Server error log during the execution of a query that uses the built-in isnumeric( < string > ) with a very large value of < string > . |
| 822700 | A 706 error with state 3, "Process < spid > tried to remove PROC_HDR < address > that it does not hold in Pss.", may be reported in the SAP ASE error log during the cleanup phase of a query execution. See KBA 3015737. |
| 822716 | A 834 error, "Illegal attempt to clean buffer ...", together with a stack trace which includes the module 'rec__boot_recover_dbs', 'buf_online_database' and 'cm_dbclean' may be reported in the SAP ASE error log when sp_object_stats is executed while a database is undergoing recovery. See KBA 2982529. |
| 822719 | On Windows, dbisql client does not run when executed from the Start menu. See KBA: 3004717. |
| 822760 | In rare circumstances, timeslice error in the module 'pchk_bt_leaf_page' may be reported in the error log when executing CHECKSTORAGE on a database having tables with index compression enabled. See KBA 2967913. |
| 822872 | Under rare circumstances, Adaptive Server may hang with a message, "Initiating shared memory dump for ..." in the SAP ASE error log when the shared memory is being dumped for a configured operating system signal. See KBA 3009872. |
| 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. |
| 822941 | When the session level setting SET SHOWPLAN is enabled, the output generated for queries performing SELECT DISTINCT on two or more columns may report the usage of 'HASH DISTINCT Operator' even if the session level setting SET DISTINCT_HASHING was disabled. See KBA 2976938. |
| 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. |
| 823014 | The text of a stored procedure or trigger may be incorrectly stored in syscomments system table if the SQL text contains a session level SET statement to a numeric value followed by a command. See KBA 2975923. |
| 823035 | When the Rep Agent Coordinator thread is killed with the KILL command in an HADR setup, an infinite number of 9242 errors may be reported in SAP Adaptive Server error log. See KBA 2975483. |
| 823039 | A 9510 error, "The builtin function 'syb_sendmsg' failed to send the message < text > to destination < IP-Address > at port number < value > because the Internet address is incorrectly formed or is non-existent. Please enter the Internet address in its correct form and retry.", may be reported when the IP Address value has leading or trailing blank characters included. |
| 823043 | In rare circumstances, a 14316 error, "The number field in syscomments for partition condition '****' in database '*' for table '****' indid '*' has exceeded the 32767 limit", may be reported in the SAP ASE error log when "ALTER TABLE ADD PARTITION" is executed. See KBA 2975007. |
| 823050 | After dumping and loading a database that has had ALTER DATABASE SHRINK run on it, sp_helpsegment may report negative 'used_pages' values for that database. See KBA: 2995964. |
| 823078 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ubofree' together with a stack trace which includes the modules 'ups_disable_hashstats_parallelism' and 'cri_ptn_index' may be reported in the SAP ASE error log when CREATE INDEX is executed. See KBA 2978619. |
| 823119 | In rare circumstances, a 678 error, "Invalid Buffer Cache Access: Could not open object ' < object-id > ' in database ' < database-id > '", together with a stack trace which includes the modules 'open_get_cacheid', 'Optimize' and 's_compile_stmt' may be reported in the SAP ASE error log while Adaptive Server is building the query plan of a DML query which involves a system temporary database or a user defined temporary database. See KBA 2891210. |
| 823120 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'add_decrypt_bi' may be reported in the SAP Adaptive Server error log when performing a select against a table that includes encrypted columns. See KBA 2979605. |
| 823126 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'adjust_const_desc', and sometimes the signal 11 is followed by looping messages, "FATAL UNHANDLED EXCEPTION", may be reported in the SAP Adaptive Server error log when storing T-SQL text using SET command in a local variable that contains one or more '+' operators along with "/* . . . */" style comments and the configuration option 'enable literal autoparam' is set. See KBA 2979907. |
| 823135 | An incorrect value for column 'QuiesceTag' may be reported when a SELECT query is run on table master..monOpenDatabases although a PREPARE DATABASE < tag-value > RELEASE has been executed before. See KBA 2980484. |
| 823142 | When starting a capture with "dbcc workload_capture(start)" command, SAP ASE may report an error like "Workload capture failed to start for insufficient kernel resource memory. Please increase the value of 'kernel resource memory' and try again." See KBA 3086885. |
| 823146 | A 10330 error, “DROP TABLE or DROP ANY TABLE permission denied on object dir_ < value > ,database tempdb, owner dbo”, followed by a 10331 error, “Permission denied, database master, owner dbo. You need the following permission(s) to run this command: MAP EXTERNAL FILE.”, may be reported when sp_dump_history is executed by a user who does not have the same level of privileges as the previous user that executed the same system store procedure. See KBA 3059084. |
| 823199 | In rare circumstances, a 1603 error, "Process priority 5 invalid or no process slots available", followed by the message "Failed to spawn delete sybdsam handler task.", may be reported in the SAP ASE error log when dropping a large amount of objects simultaneously and the Adaptive Server is configured for a single engine and the "number of user connections" is less than the number of objects being dropped. See KBA 2981553. |
| 823200 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'dbinfo_boot_set_pg24objid' together with a stack trace which includes the modules 'dmpx__setup' and 'dbinfoupd' may be reported in the SAP ASE error log when DUMP TRANSACTION is executed. See KBA 2983946. |
| 823228 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'pg_syslogs_extent_count' together with a stack trace including the modules 'th_fill_and_report_freespaceinfo', 'dbt__fill', and ‘lddb_main’ may be reported in the SAP ASE error log when LOAD DATABASE is executed. See KBA 3014622. |
| 823235 | When executing 'sp_hadr_admin failover_timeestimate' in an HADR setup, a list of the oldest active transaction for each HADR database is displayed. |
| 823236 | The SAP ASE Rep agent will not be notified for log extension after DUMP DATABASE is executed for an in-memory-database which will prevent data changes from being replicated. |
| 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. |
| 823253 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'is_numeric' and 'LeRun' may be reported in the SAP Adaptive Server error log during the execution of a query that uses the built-in sap_hextobin( < string > , < string-length > ) with a very large value for < string-length > . See KBA 3001411. |
| 823263 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'mda__collectCachedStatements' together with a stack trace including the modules 'mda_populate_monCachedStatement' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on master..monCachedStatement is executed. This results in Adaptive Server implicit shut down due to spinlock SSQLCACHE_SPIN being held. See KBA 2985036. |
| 823265 | A comma might be missed among values in Object_status attribute of sp_help < table_name > . |
| 823277 | In rare circumstances, the message, “Thread CAP Parser( ) infected with signal 11.”, together with a stack trace which includes the modules ‘exc__appDumpStack’, ‘exc_terminate’ and ‘strlcpy’ may be reported in the SAP Replication Server error log when an unexpectedly empty log record is processed under an HADR setup resulting in the replication flow to stop. |
| 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. |
| 823290 | In rare circumstances, replay might hang and never complete when BCP which is used to import a large amount of data into SAP Adaptive Server is captured and the table does not exist on the replay server. See KBA 2985083. |
| 823310 | Under rare circumstances, some user tasks might remain in a RUNNABLE state forever, while binding an active process (SPID) to a different thread pool using system stored procedure sp_bindexeclass. See KBA 2987082. |
| 823313 | The message, "sqlsrvr.exe has stopped working", may be reported when upgrading from SAP Adaptive Server 15.7 to 16.0 SP03 on Windows 2012 platform. See KBA 2986134. |
| 823325 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 's_setupvar' and 'subgoals' may be reported in the SAP ASE error log on HP-UX platform when SELECT @@ssl_protocol is executed and the configuration option 'enable ssl' is enabled. See KBA 3060007. |
| 823328 | In rare circumstances, connections from SAP Adaptive Server to Open server applications may hung. This hang was observed in the situation when the ASE site handler process is sleeping while it is freeing a SITEBUF data structure, and is awaiting for an existing connection to wake it up. The environment variable SITE_RETRIES whose default value is 30 seconds and it can be adjusted prior to bootstrap Adaptive Server to set the time for which ASE will wait before attempting to forcibly kill the site handler. See KBA 3079763. |
| 823344 | In rare circumstances, an incorrect result set may be returned when querying a table with page compression enabled. See KBA 2986752. |
| 823356 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'ra__ci_stpmgr_execute' may be reported in the SAP Adaptive Server error log when the Rep Agent is stopped in an HADR setup. See KBA 3009036. |
| 823375 | In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'pss__get_free_pss' together with a stack trace which includes the modules 'pss_alloc' and 'spawn_conn_hdlr' may be reported in the SAP ASE error log. See KBA 2676160. |
| 823392 | The "replay show" command in SAP ASE Workload Analyzer Command Line Utility is enhanced to list all replays of a given capture. |
| 823412 | SAP ASE won't report the resource limit violation event in MDA table master..monThresholdEvent table if the resource limit action is configured as 2 (aborts the query batch), 3 (aborts the transaction) or 4 (kills the session). See KBA 2989840. |
| 823464 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'bufpagedestroy_noscan' may be reported in the SAP Adaptive Server error log when a SELECT query requires a worktable creation and the session option SET SORT_RESOURCES is enabled. See KBA 3060360. |
| 823466 | In rare circumstances, a 4702 error, "XML parser fatal error", may be reported when the built-in xmlextract() is executed and charset 'SJIS' is in use. |
| 823487 | In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'crt_allocpages_for_dft' together with a stack trace which includes the modules 's_execute' and 'sequencer' may be reported in the SAP ASE error log when a DML is run and the Adaptive Server is allocating disk space for a deferred created table but has run out of disk space in the database. See KBA 3059123. |
| 823492 | The message, "Current process infected with signal 11 (SIGSEGV)", or "Adaptive Server Enterprise system exception generated by a storage access violation", in the module '_lopConsWktAccess' together with a stack trace which includes the modules 'lopConsJoins' and 's_compile_stmt' may be reported in the SAP ASE error log during the execution of a SELECT query when the configuration option "inline table functions" is enabled. See KBA 2992794. |
| 823522 | In some circumstances, SAP Adaptive Server may report in master..monOpenObjectActivity MDA table incorrect values in LastUsedDate column. See KBA 2996719 |
| 823547 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memtextlen' together with a stack trace which includes the modules 'prE_PARAMs_buf' and 'prSQLTEXT', may be reported in the SAP ASE error log when executing DBCC SQLTEXT and a SELECT query is being executed in parallel. See KBA 2843657. |
| 823555 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules ‘dmpx_truncatemain’ and ‘dmpxact’ may be reported in the SAP Adaptive Server error log during DUMP TRANSACTION using a dump configuration file with the @retry parameter set and while the command execution is retried following an initial failure. See KBA 3059942. |
| 823562 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'mem__validate_assign', may be reported in the SAP ASE error log when a query is executed and the engine local cache memory is corrupted. See KBA 2998317. |
| 823639 | Export comparison may hang with status reporting "Exporting Progress: [5.00%]." when using the workload analyzer command line utility. |
| 823672 | Two new columns, BackupEndTime (date the last backup finished for the database) and LastTranLogEndDumpTime (date the last dump transaction finished for the database) are introduced in MDA table master.dbo.monOpenDatabases. Column LastTranLogEndDumpTime is not updated when dump transaction is executed with either no_log or truncate_only option. |
| 823687 | Infected with Signal 11(SIGSEGV) in null() with altdb__upd_text_ptr on the stack may be reported in the SAP Adaptive Server error log when executing an ALTER DATABASE OFF command to shrink database. See KBA 3016683. |
| 823700 | A timeslice error in the module 'exc_raise' together with a stack trace which includes the modules 'quitfn' and 'LeExecSqlFunc' may be reported in the SAP ASE error log when killing a nested user defined function execution. The killed session will unexpectedly remain orphan and invisible by sp_who while it will continue to hold logical locks as shown by sp_lock. The current fix completes that of CR 785132. See KBA 2188555. |
| 823714 | The message, "Current infected with signal 11 (SIGSEGV)", in the module 'cri_fill_sarglengths' together with a stack trace which includes the modules 's__finish_alttab' and 'cri_ncrebuild' may be reported in the SAP ASE error log when CREATE INDEX and ALTER TABLE DROP both reference the same column and are executed together in a single batch. See KBA 3009010. |
| 823732 | The error message, “Backup Server: 4.141.2.40: [12] The 'CreateFile' call failed for database/archive device while working on stripe device '\\.\pipe\mypipe' with error number 2 (The system cannot find the file specified). Refer to your operating system documentation for further details.”, will be reported when DUMP DATABASE that is using a pipe archive device is executed. See KBA 3005089. |
| 823768 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'err_pll_primary_processing' and 'LavaThreadDriverCleanup' may be reported in the SAP Adaptive Server error log during the execution of a query. See KBA 3059158. |
| 823816 | A 341 error, “Internal error: SIGSEGV happened, please refer this issue to SAP Technical Support.", in the module ‘VEH_Optimize' together with a stack trace way be reported in the SAP ASE error log when the statistics of a proxy table became inaccurate following an upgrade to 16.0 SP03 PL09 release. See KBA 3012203. |
| 823853 | When SSL configuration is not setup as expected on Linux, then the SAP Backupserver cannot be started and no error message is reported either on the console or the Backupserver error log. See KBA 3079789. |
| 823879 | When replicating a large text or image value having an uncompressed size greater than 2GB, in a database setup for LTL replication, Rep Agent may terminate abnormally. The message, "RepAgent( < database-id > ): Received the following error message from the Replication Server: Msg 2056. Line < line-number > , character < column-number > : Incorrect syntax with '-'.", is reported in SAP ASE error log. See KBA 3009024. |
| 823887 | Under some circumstances, the message, "Internal error: SIGSEGV happened, please refer this issue to SAP Technical Support.", together with a stack trace in module VEH_Optimize() may be reported in SAP ASE error log but without detailed call stack information on Linux platform. Starting Adaptive Server with trace flag 16995 disables Vectored Exception Handling mechanism and allows detailed call stack information to be reported. KBA 3033771. |
| 823936 | In a replication environment setup for DDL replication, the DDL command 'CREATE VIEW' is erroneously replicated when it is executed inside a privately created system stored procedure or inside a replicated user stored procedure. In the latter case, the SRS DSI terminates after receiving ASE error 2714, "There is already an object named ' < view-name > ' in the database.". See KBA 3059922. |
| 823940 | In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of < negative-value > . Maximum allowed length is 16384.“, followed by the message, "Current process infecte:d with signal 11 (SIGSEGV)", in the module 'iocRunController' together with a stack trace which includes the modules 'brfinish', 'ea_bufdecrypt' and 'memmove_error' may be reported in the SAP ASE error log. This will result in the iocRunController task to die which will require an ASE restart. See KBA 3011046. |
| 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. |
| 824019 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'do__validate_stale_page_ts' together with a stack trace which includes the modules 'do_needed' and 'ds__recoverdbs' may be reported in the SAP ASE error log instead of raising error 3478 during recovery. See KBA 3014853. |
| 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. |
| 824077 | A 9965 error, "The entries in dbcc_config for database 'master' are either missing or invalid. Use sp_dbcc_evaluatedb to determine appropriate values for the entries and sp_dbcc_updateconfig to set them.", may be reported when DBCC CHECKSTORAGE or CHECKVERIFY against the master database if executed for the first time on 16.0 ASE SP03 PL09 or SP04. See KBA 3017156. |
| 824078 | A 10331 error, "Permission denied, database master, owner dbo. You need the following permission(s) to run this command: CREATE DATABASE.", may be reported when the option 'enable granular permissions' is set and a user with 'create database' privilege executes CREATE ARCHIVE DATABASE. See KBA 3059944. |
| 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. |
| 824095 | Spinlock contention on data cache due to scans on the sysobjects table may be observed with highly concurrent workloads executing prepared statements. See KBA 3017684. |
| 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 |
| 824153 | A new configuration option ‘temp table statement caching’ is introduced to SAP Adaptive Server which indicates if SQL statements that reference temporary tables are saved in the statement cache. The default value is true, which means that such SQL statements are not saved in the statement cache. |
| 824157 | A new configuration option 'bulk insert validation' is introduced to SAP Adaptive Server which indicates if row format validations are done for bulk inserts. The default value is true, which means that validations will be done for bulk inserts. |
| 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. |
| 824221 | Adaptive Server is enhanced to avoid multiple evaluations of the built-in has_role() for each qualifying row in a query. This optimization applies to either cursor and non-cursor queries. See KBA 3010179. |
| 824229 | A timeslice error in the module 'pausenonatomic' together with a stack trace which includes the module 'des_checkpoint' may be reported in the SAP ASE error log when DUMP DATABASE is running. See KBA 3027150. |
| 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. |
| 824297 | In rare circumstances, the message, "timeslice -2001, current process infected", in the module 'pausenonatomic' together with a stack trace which includes the modules 'sort' and 'sortclean' may be reported in the SAP ASE error log during the execution phase of a stored procedure when a signal 11 (SIGSEGV) is caught in the sort manager of the Adaptive Server. See KBA 3033771. |
| 824310 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'n3__bi_func_signature' together with a stacktrace which includes the modules 'crcpc_norm' and 'add__computedcol' may be reported in the SAP ASE error log when a dynamic prepared INSERT statement is executed. See KBA 3032737. |
| 824316 | The Adaptive Server bootstrap trace flag 754 that allows to disable the shared ELC access functionality is made fully operational. See KBA 3087302. |
| 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. |
| 824369 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'STAdjustPkgPoolSize' together with a stacktrace which includes the modules 'ra_ci_allocate_cmd_package' and 'ra_process_lr' may be reported in the SAP ASE error log under an HADR setup after the message "Message: 76007, Severity: 5 Partial packages allocated for Stream ' < database-name > '" is reported. See KBA 3041962 |
| 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. |
| 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. |
| 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. |
| 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. |
| 824496 | A new column RoleName is added to MDA table master..monThresholdEvent. This column will report the role name while reporting resource limit violation event if the resource limit is set based on a user defined role. For other cases the RoleName value reported will be NULL. |
| 824522 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules ‘dpdb_main’ may be reported in the SAP Adaptive Server error log during DUMP DATABASE using a dump configuration file with the @retry parameter set and while the command execution is retried following an initial failure. See KBA 3061899. |
| 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. |
| 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. |
| 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. |
| 824860 | SAP ASE Workload Analyzer Command Line Utility may wrongly report PCAP files are not accessible when a workload in "Loaded" or "Analyzing" status is re-analyzed. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 |
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 PL01, ASE SP04 PL01, SP04 PL01, 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)