/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 PL04. 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 |
|---|---|
| 497173 | Executing sp_tables against a User Defined Function may report some status incorrectly. See KBA 2411224 |
| 552310 | When the maximum number of allowable user defined types are added, despite deleting some of existing user defined types, does not make room for adding new types. |
| 727207 | Updating a proxy table mapped to SAP IQ with an access rule bound to a column may fail with an SAP IQ error, "SQL Anywhere Error -1010024". The fix is enabled through traceflag 11249. |
| 727226 | A 908 error, "Unable to find any entries in sysusages for dbid ' < database_id > ', database ' < database_name > '. Run DBCC CHECKTABLE on sysusages in the master database.", may be reported on a database that was previously created entirely on the master device, after a full database dump of master is loaded into a freshly created master device. |
| 734313 | Verifications are added in the module 'plc__shiftblock' when the PLC of a session contains erroneous metadata and is about to damage another session PLC while a 3475 error is reported. Under rare circumstances the error message 140063, "ERROR in < module_name > for plc < 0x > ... " may be reported in the SAP ASE error log. |
| 756013 | New Rep Agent configuration options, 'initial log scan percent' and 'max user task slowdown', are introduced for stream and synchronous replication mode. When the Rep Agent is booted, these options allow a better control of the slowdown of concurrent user tasks activity, so that the Rep Agent can reach the end of the transaction log and switch to synchronous mode on due time. |
| 760523 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sqt_deallocate' together with a stack trace which includes the modules 'lwp_create' and 's_cache_stmt' may be reported in the SAP ASE error log after a 701 error, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", is reported when a SELECT query is executed. See KBA 2496908. |
| 765005 | A 7222 error, "Received bad token 0xff from site ' < server name > '", may be reported in the SAP ASE error log when a nested RPC is executed. |
| 765203 | On AIX in threaded kernel mode, the monEngine connections column is incorrect and dump database may fail with 'soc_nconnect: No free file descriptors available' raised in the errorlog when executed concurrently with sp_listener. See KBA 2573288 |
| 768847 | A 804 error, "Unable to find buffer < buffer_address > from cache < cache_name > holding logical page < page_number > in sdes < sdes_address > kept buffer pool for object < object_name > ", may be reported in the SAP ASE error log after the process performing an ONLINE DATABASE is killed. |
| 772020 | The XML output of cached plans may lead to XML parsing errors if it contains parameters values with XML meta-characters like '&', ' < ' or ' > '. |
| 781081 | A 8207 error, "Couldn't find an available descriptor for an object. Raise the value of the configuration parameter 'number of open objects' for more descriptors", may be reported when executing UPDATE STATISTICS WITH HASHING, leading to incorrect statistics being computed. See KBA 2555080. |
| 783675 | The thresholds metadata reported by DBCC DBTABLE may display information for segment 33 mistakenly. |
| 792149 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'th_accounting' together with a stack trace which includes the modules 'xact__postcommit_processing' and 'th_ext_unreserve', may be reported in the SAP ASE error log while executing DBCC FINDSTRANDED or DBCC DBREPAIR( < database_name > , findstranded). See KBA 2554434. |
| 793970 | A signal 11 may occur when executing some sybmon commands, such as SQLTEXT, QUEUE, MMGRPOOLS, if the dump file being analyzed does not contain the procedure cache. |
| 795557 | A 5605 message, "Prepare transaction RPC to the remote server < server_name > failed. Transaction key < key_value > . Return status -2.", may be reported because an external transaction is out of synchronisation between the local server and the remote server after a deadlock occurs on the remote server. See KBA 2276710. |
| 796120 | Under certain circumstances, the SAP ASE may hang during a DML operation when using Latch Free Btree indexes and the NV Cache is enabled. |
| 796208 | Under rare circumstances, SAP ASE on Windows platform may leak memory when using security identifiers. |
| 797041 | A 1163 error, "The space allocated to the sysgams table in database ' < dbname > ' (dbid = #) must be at least 16 pages.", together with a stack trace which includes the modules 'pggam__srchonegampage' and 'pg_allocate_syslogs' may be reported in the SAP ASE error log when using CREATE DATABASE FOR LOAD to create a database bigger than 63GB in a 2KB server, 128GB in a 4KB server, 256GB in an 8KB server or 512GB in a 16KB server, with dedicated log devices which are placed out of that range. See KBA 2269985. |
| 797068 | Message 10330 is raised when table created by users aliased as dbo, are accessed by users of dbo owned stored procedure. See KBA 2287529. |
| 798608 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc_ddlmap_release' together with a stack trace which includes the modules 'ddlmap_finish' and 'xact__commit_local', may be reported in the SAP ASE error log when the database option "ddl in tran" is enabled and a transaction that contains many INSERT commands in a single batch is executed. See KBA 2316693. |
| 798661 | The message, "Assertion (pss- > powner_uid > DBO_UID)", may be reported in the SAP ASE error log when sp_modifyuser ' < user_name > ', 'resolve as', 'dbo' was initially executed while a query which involves a user table is run and the diagserver binary is in use. |
| 799684 | The "setuser" command is not replicated. See KBA 2488137. |
| 800118 | A 16805 error, "A LOB LOCATOR was used that is no longer valid: Either the transaction that created it has ended or it has been deallocated.", may be reported during the execution of a stored procedure that has a SELECT query which assigns a text value into two LOB local variables. See KBA 2462386 |
| 800208 | The recovery of a database appears to hang. Multiple executions of DBCC SHOWRECOVERY will show the recovery processing the same "Current log record" (an AEXTENT) while "Recovery Pages: Getpage requests:" value increases greatly over time. See KBA 2340791. |
| 800440 | A new option has been added to sp_add_resource_limit, sp_modify_resource_limit and sp_drop_resource_limit to apply the limit to any user using any application. See KBA 2358540. |
| 800532 | A new config option, "decompression row threshold", is added to decompress the entire data rows instead of decompressing each columns one by one for compressed tables with large number of columns. The value of the config option represents the maximum number of columns in a table which will be uncompressed using column decompression. If the number of columns is larger than this value, SAP ASE will use row decompression instead. The default value for "decompression row threshold" is 20. |
| 801343 | Incorrect statistics may be generated when when using the "with hashing" option with update statistics. See KBA 2359108. |
| 801535 | A 16110 error, "srv_select() was called with a bad select mask (NULL) parameter." may be reported in the SAP backup server error log when a DUMP DATABASE is executed and the database is using a large number of devices. |
| 801788 | After running command "Reorg rebuild < table_name > < index_name > ", index pages are not compressed. |
| 801978 | A 140 error, "Can only use IF UPDATE within a CREATE TRIGGER", may be reported when the configuration option 'procedure deferred compilation' is enabled and a body of trigger containing the UPDATE built-in function is executed (i.e. triggered). See KBA 2366912 |
| 801996 | The unique index to be used as the primary key for replication can be set manually with the new system stored procedure sp_setreppk which has the following usage: sp_setreppk table_name [, index_name]. |
| 802335 | In some cases, intelligent index scan may cause low LIO estimate with a poor index being chosen for the plan, resulting in poor performance. |
| 803016 | Backup Server does not generate localized progress messages when DUMP or LOAD command is executed. See KBA 2382891. |
| 803144 | In rare circumstances, a 8201 error, "Keep count of descriptor (objid= < object_id > , dbid= < database_id > ) was expected to be 1. Instead 0 was found.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'des__unkeep' and 'ptngetpages' while an object is created and SAP ASE needs to reuse a descriptor in the metadata cache to instantiate this object. |
| 803225 | The PRINT statement displays BIGDATETIME values with millisecond granularity while the documentation specifies that BIGDATETIME has a display format that includes full microsecond precision. See KBA 2385764. |
| 803545 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_update_stmt_metrics' together with a stack trace which includes the modules 'curs_close' and 'mem_freepages' may be reported in the SAP ASE error log when a CURSOR is closed. See KBA 2533441. |
| 804071 | The message, "timeslice -1001, current process infected" in the module 'pausenonatomic' followed by a stack trace that includes the module 'getpage_with_validation' and 'bt__getnextscanpg', may be reported in the SAP ASE error log under heavy concurrent activities. |
| 804444 | Performance degradation may be observed in SAP ASE when executing a query with multiple predicates of which one is an IN list, because SAP ASE is not choosing an efficient index. |
| 804856 | In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of < wrong_length > . Maximum allowed length is < max_length > ", may be reported in the SAP ASE error log when page compression is used. See KBA 2595171. |
| 804886 | The message, "D00: Page Verification Error: Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; check this page (page#= < pagenum > row#=0 offset in row number table=0)", may be incorrectly reported in the Backup Server error log when executing DUMP DATABASE WITH VERIFY for a syslogs page. See KBA 2427308. |
| 804992 | A 1640 error, "Adaptive Server requires encryption of the login password on the network", and a 4002 error, "Login failed", may be reported when running preupgrade utility if the value of server config option 'net password encryption reqd' is set to 2 or 3. |
| 805133 | On Linux platform, under rare circumstances a connection to SAP ASE may hang after the client issues a cancel. |
| 805275 | SAP ASE server will disable ASE_JAVA functionality if jvm.wl is missing and the message 10762 together with the detailed reason will be reported in SAP ASE error log. This is to improve the default security should jvm.wl be accidentally removed. |
| 805701 | Executing CREATE PROCEDURE/FUNCTION DEFAULT SCHEMA with an invalid schema name will succeed in an SQLScript database if no objects are involved in the CREATE PROCEDURE/FUNCTION body. |
| 805990 | In rare circumstances on heavily loaded SAP ASE systems, CREATE TABLE into an in-memory database may hang with a stack trace which includes the modules 'getpage__noscan', 'getpage_with_validation' and 'bufsearch_cache_getlatch'. See KBA 2266313. |
| 806009 | A 1511 error, "Sort cannot be reconciled with transaction log" and a 4313 error "Recreate index failed for table < table_id > , index < index_id > . The table has been left in an inconsistent state, and the index is missing, so LOAD TRANSACTION errors may result.", may be reported when running REORG REBUILD on an allpage-locked table with a clustered index that allows duplicate rows. |
| 806172 | A 7412 error, "Space available in segment ‘ < name > ’ has fallen critically low in database ‘ < name > ’. All future modifications to this database will be suspended until the transaction log is successfully dumped and space becomes available.", may be observed during execution of complex queries which involve operator GROUP BY and aggregate function SUM. See KBA 2438017. |
| 806252 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dmpx__find_dmpxact_type' together with a stack trace which includes the modules 'dmpx_truncatemain' and 'dmpxact', may be reported in the SAP ASE error log when an encrypted database is dumped. See KBA 2571913. |
| 806256 | During upgrade, when Granular Permission is enabled, connections to SAP ASE may fail with a stack overflow message followed by a stacktrace that includes the modules ' dbc_checkmode' and 'dbt_get_with_statuscheck'. See KBA 2441829 |
| 806377 | A 632 error, "Attempt to move memory with an incorrect length of < wrong_len > . Maximum allowed length is < max_len > .", may be reported in the SAP ASE error log when executing SELECT statements with query_text() under traceflag 16939 against a spid associated with a Java program with many dynamic parameters. |
| 806477 | Query with MERGE statement may result in spurious errors about incorrect conversions. |
| 806500 | Sub-optimal performance may result when multi-database queries are executed and the "auditing" configuration option is enabled. A contention on spinlock 'rdbt_spinlock' will be seen in the modules 'dbt_keep', 'dbt_unkeep' or 'dbt_rekeep' when called by module 'usedb' while SAP ASE attempts to open the user tables of a query. |
| 806683 | A 16878 error, "The limit specified in a LIMIT clause may not be negative", will be reported against an SQLScript database if the TOP N value exceeds the maximum value of an unsigned 32-bit integer value. |
| 806871 | Executing the built-in function get_index_info against an On-Disk MVCC enabled table may return unexpected results. |
| 807179 | Incorrect data may be inserted into a table in a SQLScript database when values of incompatible datatypes are used. |
| 807307 | A 3606 message, "Arithmetic overflow occurred", may be reported when executing sp_configure " < param_name > ", 0, " < value > {K|M|G}" with a < value > greater than or equal to 2048G. |
| 807346 | A 3333 error, "Failed to get a log marker for scan to undo transaction (Rid pageid = < pagenum > ; row num : < rowid > } in database < dbname > due to error < value > .", together with a stack trace which includes the modules 'insert_unique_error' and 'abortmark' may be reported in the SAP ASE error log when Adaptive Server is rolling back a DML command and the configuration option 'user log queue size' is disabled. |
| 807606 | Workload profiler has been extended to support IMRS Cache size and Version DB size estimations for On-disk MVCC. |
| 807707 | A 632 error, "Attempt to move memory with an incorrect length of < negative_value > . Maximum allowed length is 16384.", may be reported in SAP ASE error log when creating a procedure which has complex SQL with nested subqueries involving the use of ' < table > .*' to represent all the columns in the tables. |
| 807823 | Empty PLC (Private Log Cache) blocks with only a BEGIN TRANSACTION log record present are flushed to syslogs during DUMP DATABASE when the database option 'allow incremental dumps' is enabled, or the database was created with the 'INMEMORY' option. This will prevent the transaction log truncation from taking place when a transaction is still open. |
| 807870 | The message, "Current process infected with signal 11 (SIGSEGV)" coming from the module 'oh_findendoffset_inobuf' together with a stack trace in the SAP ASE errorlog that includes the modules 'rvm__get_obfuscated_currstmt' and 'rvm__audit_getcommand_subcommand', may be reported in the SAP ASE error log when executing sp_addlogin and ALTER LOGIN in a batch with auditing enabled. See KBA 2469521. |
| 807871 | New feature that adds SSL support to the backup server. |
| 808080 | When the configuration parameters 'number of network tasks' and 'number of disk tasks' are changed their new value is not written to the SAP ASE configuration file. See KBA 2472350. |
| 808127 | A 154 error, "Limit clause is not allowed in view", may be reported by SAP ASE when creating a VIEW with a LIMIT clause. In addition, a 4501 error, "View < view_name > has more columns defined than column names given", may be reported when creating a View User Defined Functions (VUDF) with LIMIT clause. |
| 808160 | The execution of SP_SETREPTABLE by an unauthorized user should fail with a 18418 error, "Only the System Administrator (SA), the Database Owner (dbo) or a user with REPLICATION authorization may execute this stored procedure", as opposed to a 567 error, "You must have the following role(s) to execute this command/procedure: 'sa_role'. Please contact a user with the appropriate role for help.". |
| 808289 | A 12822 error, "Cannot create temporary table '## < table_name > '. Prefix name '## < table_name > ' is already in use by another temporary table ## < table_name > '.", may be reported when a SELECT query references a session temporary table while a user temporary table with the same name exists in the current session. This error will likely be seen in SAP Business Suite ASE systems. |
| 808297 | The execution of sp_dump_history @operation = 'purge', @status = 'fail' may delete all rows from the dump history file mistakenly. |
| 808353 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'ksmask_rpacket' followed by a stack trace that includes the modules 'kstcpnetctlrProcessRead' and 'iocPoll', may be reported in the SAP ASE error log. Thereafter, the SAP ASE may become unresponsive. See KBA 2336205. |
| 808470 | A new option, 'with nowait', has been added to the DROP INDEX command, to let DROP INDEX return instantly and leave the major work of dropping the index like index page deallocation done in the background, allowing concurrent DDL and DML commands execution on the original user table. |
| 808494 | When SAP ASE Rep Agent is configured in LTL mode and is started with the resync option, the configuration parameter 'batch ltl' is inadvertently changed to 'false'. |
| 808794 | Improvements have been made to audit logging. |
| 809100 | When SP_SHOWOPTSTATS is run on tables that have large number of step counts in statistics, other sessions may observe performance degradation when accessing same set of tables. See KBA 2492238. |
| 809121 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeScrollCache::LeScrCacheGetRow' followed by a stack trace that includes the modules 'LeLOBCache::copyOutParam' and 'getvalue', may be reported in the SAP ASE error log when inserting a TEXT value from a local variable after performing a substring operation. See KBA 2492093. |
| 809158 | A 17262 error, "A user with the specified login name already exists.", will be reported when creating a user in a TSQL database while a user with same name exists in a SQLScript database. |
| 809258 | Some messages like, "Cleanup for database ID < db_id > in < module_name > ..." were reported unnecessarily in the SAP ASE error log during the recovery process despite a successful cleanup of pre-allocated log pages. KBA2644346 - Clean up messages can be found while recovering database |
| 809337 | Point-in-Time recovery of IMRS-enabled databases using LOAD TRAN ... WITH UNTIL_TIME interface is restricted. |
| 809659 | Crossed and nested cursor operations are now supported in Accelerator for ASE when propagating them into HANA. |
| 809661 | HANA column table identity column is now supported when executing DDL statements on tables that have an identity column. Traceflag 17001 is required to turn on this enhancement. |
| 809700 | Queries involving large number of SUM aggregates execute slowly on SAP ASE in an Business Warehouse type of environment. |
| 809748 | The message, "SSL or Crypto Error Message: 'The SSL handshake failed. Root error: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol'", may be reported in the SAP ASE error log when an SSL connection reuses a socket that was previously used by a terminated site handler. See KBA 2533391 |
| 809940 | SAP ASE does not report an error about missing an external login during scheduled job creation using sp_sjobcreate with jproperties=run_as_owner. |
| 810033 | Under rare circumstances, a 728 error, "Allocation of size < n > bytes from the row storage cache, < imrs cache name > , failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information ....", followed by the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ridmap_update' together with a stack trace that includes the modules 'imrs__upd_ridmap' and 'imrs_rollback_imrv', may be reported during rollback of pack operation if the IMRS cache is under configured. |
| 810114 | Predefined entities less-than sign ' < ' and greater-than sign ' > ' in SOAP body elements are converted into ' < ' and ' > ' when a document/literal style web method is invoked by webservices. |
| 810202 | In rare circumstances, a 803 error, "Unable to place buffer < buffer_address > from cache < cache_name > holding logical page < page_number > in sdes for object < object_name > - either there is no room in sdes or buffer already in requested slot", following a 7901 error, "Page < page_number > , partition ID < partition_id > , is expected to be the first page of a text/image/unitext value", may be reported when DBCC REBUILD_TEXT is executed. |
| 810261 | The message, "Assertion (sdes) failed in file abortcmd.c ...", followed by the message, "Assertion (XACT_CHECK_STATE(xdes, XACT_IN_CMD)) failed in file abortcmd.c ...", may be reported in the SAP ASE error log when ALTER DATABASE < database_name > OFF is run and the database has On-Disk MVCC enabled tables while the diagserver binary is in use. |
| 810271 | On SSL enabled HADR setup, if FaultManager is configured, heartbeat client may fail to boot resulting in failure of FaultManager bootstrap. |
| 810276 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module '__milli_memcpy', followed by a stack trace that includes the modules 'tdsrecv_params', 'tdsrecv__process_batchparam' and 'tdsrecv__dynexec_batch', may be reported in the SAP ASE error log when a JAVA application executes an INSERT with a TINYINT datatype. See KBA 2554290. |
| 810286 | High contention on spinlock for global scheduler queue ('global sched') may be observed for some highly concurrent workloads. |
| 810308 | On IBM AIX platform with SSL enabled, the message, "ssl_nrpacket_iocp: vsn 7 kpid 6750260 not enough space to read header", may be reported repeatedly in the SAP ASE error log and SAP ASE may become CPU bound. |
| 810398 | In certain cases, Abstract Plan may be incorrectly stripped off when dynamic SQL uses polymorphic built-in functions. |
| 810443 | A 208 error, " < table_name > not found", will be reported when accessing a table created in a SQLScript database by using the SELECT INTO command issued from a TSQL database. |
| 810463 | In highly concurrent environments with scans on few tables, contention on buffer-level spinlock (‘bufspin < cache name > ’) for latching the buffers corresponding to scanned pages may be observed. |
| 810485 | The output of SELECT SHOW_CACHED_PLAN_IN_XML garbles the values of the bind parameters if the parameter count is more than 35. See KBA 2593765. |
| 810486 | The procedure cache may get full with multiple copies of the query plan for a single stored procedure involving DDL and index creation within a transaction. |
| 810493 | A new column, “datachange: < change_rate > ”, has been added to the output of sp_showplan with query's spid when ‘set show_object_list on’ to display the data change rate of the query involved objects since the last update statistics. |
| 810512 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'get_stored_char_size' together with a stack trace which includes the modules 'get_unicode_text' and 'sqlscript_lex' may be reported in the SAP ASE error log when creating a procedure that contains comments like '/*****/' in a SQLScript database. |
| 810533 | In rare circumstances, a 12301 error, "Internal error: the index (id = 0) and the data for row (Pageno, Rowno) in table ' < Tablename > ', database < dbid > are inconsistent; data is marked deleted but index is not. Aborting the transaction", may be reported from a process that is running a query on a DOL table with isolation level 0. See KBA 2588993. |
| 810581 | The commit of transactions in an IMRSLOG database could take longer due to the absence of group commit functionality support for IMRSLOG. |
| 810656 | A new traceflag 11011 is added to disable the behavior where multiple INSERT statements with similar numeric input values caches a single query plan instead of creating a new plan for each statement. This behavior was introduced to avoid spinlock contention in statement cache due to large number of plans being cached for INSERT statements with similar parameters. |
| 810688 | A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be reported during the execution of a query that is using a fact table hint and no legal execution plan is found. |
| 810718 | On Windows platforms, if a JDBC connection to SAP ASE with SSL enabled is not explicitly closed by the application, SAP ASE may re-run the last command and this may lead to logical corruptions. |
| 810757 | A predicate with multiple columns, such as ((c1,c2) > (x,y)), can be incorrectly qualified as a criteria for partition elimination. This may lead to incorrect results. See KBA 2345886. |
| 810799 | In rare circumstances when DDL replication is enabled, some DDL commands may not be replicated from the primary SAP ASE when the default data cache is under configured and lots of concurrent replication activity is taking place. |
| 810812 | The Migrated Version to modify a row, residing on a datapage, in an On-Disk MVCC enabled table is now no longer created. |
| 810923 | A 16877 error, "Unable to create a new user-defined type 'type-name'. Please try again when there are fewer user-defined table types in SYSTYPES.", may be reported in the error log when creating many Table Types. |
| 810933 | systypes.uid in the SYSTYPES system table may be incorrect when creating a user-defined table type as non-DBO user. |
| 810948 | Apache Jakarta Common CLI has been upgraded to version 1.4 and Apache Jakarta Common Logging has been upgraded to version 1.2. |
| 810952 | On HP and IBM systems, the message, "Stack overflow detected" in the module 'upunsetcritical' together with a stacktrace which includes the modules 'kcvDeleteCondVar' and 'ubf_is_addr_inpool', may be reported in the SAP ASE error log during a graceful shutdown of the server while the diagserver binary is in use. |
| 810968 | A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization.", may be incorrectly reported by SAP ASE under heavy concurrent activity during query execution. |
| 810976 | A 156 error, "Incorrect syntax near the keyword 'set message_text'", will be reported when updating a column with name 'message_text'. See KBA 2540286. |
| 810985 | When a table that has a UNITEXT column is marked for replication sometimes the data may not be replicated correctly. |
| 811000 | In rare circumstances, a decrease in the UsedSizeHWM, PctUtilHWM and NumRowsHWM values may be observed in the output of "sp_imrs 'show','cacheinfo'" when a large number of DMLs have been running for a significant amount of time and the sp_imrs command is executed in between the DMLS. |
| 811009 | Under certain circumstances, negative values may be reported by SAP ASE in the MemForRowVersionsOverhead and/or MemForOlderVersions columns of the monIMRSPartitionActivity and monIMRSCacheActivity MDA tables for databases that use In-memory row storage either for row caching or on-disk MVCC. |
| 811046 | The message, "timeslice -1001, current process infected" followed by a stack trace that includes the module 'mda_populate_monCachedProcedures', may be reported in the SAP ASE error log when querying the monCachedProcedures MDA table. See KBA 2541894. |
| 811089 | A 207, 233, 264, 2760, or 12810 error indicating that an invalid column name is referenced in a query, may be incorrectly reported by SAP ASE under heavy concurrent activity during query execution. Additionally a new SAP ASE trace flag 16889 is introduced which allows to enable an alternate behavior that resolves these errors. However the use of this trace flag may expose a situation, as mentioned in CR 801618, whereby a 8211 error, "A newly created ssql_id for SQL to store in statement cache is a duplicate object id of an existing table in system tempdb." may be reported or a segmentation violation in module 's_compile_stmt' may also be seen. See KBA 2543028. |
| 811094 | A 835 error, "Illegal attempt to change contents of buffer: BUF= < Buffer_Address > " may be reported in the SAP ASE error log when post commit shrink is trying to shrink a leaf page. See KBA 2549500. |
| 811110 | Statements like "UPDATE TABLE_A SET COL_1 = ? ,... WHERE COL_X = ? AND COL_Y = ?" without the values of the bind variables, may be printed out in the SAP ASE error log when a deadlock happens. The information printed out is now enhanced to include the bind variables when SAP ASE prints the information about the participating spids and the SQL statements that caused the deadlock. |
| 811125 | The message, "Current process infected with signa 11 (SIGSEGV)" in the module 'ind__get_sysindrow' together with a stack trace which includes the modules 'reindex' and 'exec_dbcc' may be reported in the SAP ASE error log when DBCC REINDEX is executed on an invalid object that is not an index. See KBA 2544150. |
| 811166 | The "sp_imrs 'clear', 'blocking_spid'" interface has been enhanced to forcefully preempt statements that may be blocking IMRS Garbage Collection. |
| 811176 | setuphadr is enhanced to support SSL connections for Backup Server. |
| 811203 | A 728 error, "Allocation of size 10944 bytes from the row storage cache, 'imrs_cache', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = 0x10", may be reported unexpectedly in the ASE SAP error log when a SELECT query is run on an IMRS-enabled table. |
| 811206 | Under some circumstances, the DSI thread may shut down with a 3959 error, "New transaction cannot be started as Adaptive Server is in 'Inactive' HADR state. The command could not be completed", reported in the standby SAP ASE when replicating a CREATE MATERIALIZED VIEW statement in a HADR setup. |
| 811265 | Incorrect run sizes for the data caches may be reported by sp_sysmon with the "cache wizard" option. See KBA 2540661. |
| 811339 | A stored procedure recreated with the option "CREATE OR REPLACE" and where 'deferred name resolution' is ON, may incorrectly keep in memory older version of the procedure. When executed, this older version may be used instead of the new one. |
| 811343 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ssql_lookup', followed by a stack trace that includes the modules 'sqt_get_from_stmtcache' and 's__xoltp_dynprepare', may be reported in the SAP ASE error log when executing a dynamic SQL with the statement cache enabled. See KBA 2535419. |
| 811382 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'p_fill_syscolumns' together with a stack trace which includes the modules ‘proccreate' and 's_crtproc', may be reported in the SAP ASE error log when creating a SQL function with table types. See KBA 2580511. |
| 811413 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'tally_fetch' together with a stack trace which includes the modules 'tally_fetch' and 'showplan', may be reported in the SAP ASE error log if the system stored procedure sp_showplan is executed at the point that the related table is to be closed during the execution of a query from the target process. This is quite similar to CR 791453, but the error happens when accessing SYSLOGS. See KBA 2550674. |
| 811480 | A 'Blocking call exception' on SAP ASE can crash the server if another exception occurs in the handler itself. |
| 811490 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'js__expirejobs' (or js__collectjobs or js__add_dup_callout) together with a stack trace which includes the modules 'jobscheduler' and 'js__chores' may be reported in the SAP ASE error log when the timeout parameter for a job is set to a non-zero value and the configuration option 'enable job scheduler' is enabled. |
| 811498 | Spurious messages "Warning: Unknown parameter" on several configuration parameters may be reported in the SAP ASE error log. See KBA 2552639. |
| 811504 | A 2702 error, "Database 'master' does not exist." and the message "Database 'master': ASE could not completely upgrade this database" might be reported during upgrading a server earlier than 16.0 SP03 to 16.0 SP03 or later. |
| 811521 | A 691 error, "Encountered invalid logical page '0' while accessing database ' < database_name > ', object 'syslogs' (8), index 'syslogs' (0), ...", may be reported in the SAP ASE error log when DUMP TRANSACTION < database_name > WITH NO_LOG is run when the database is enabled for replication and the last change threshold for this database was crossed. |
| 811524 | Under some conditions, the procedure cache in SAP ASE may contain a large number of cached plans for the same SQL user defined function. |
| 811554 | An ODBC syntax error, "Syntax error or access violation;257 sql syntax error: incorrect syntax near ')'", may occur for an INSERT-SELECT query which contains a column name that is longer than 11 characters. |
| 811555 | The 'versiondbid' column of the SYSDATABASES table may be updated with an unexpected non-zero value after upgrading a SAP ASE of version 16.0 SP02 or earlier to 16.0 SP03 or later. |
| 811564 | A 101 error, "SQL syntax error", followed by a 137 error, "Must declare variable '@segmentna'", will be reported when SP_IMRSLOG_THRESHOLDACTION is triggered in an IMRSLOG database whose database name is more than 11 characters long. |
| 811581 | Under certain circumstances, SAP ASE may hang during a DML operation when Latch Free Btree indexes are used and the Lock Less Data Cache is enabled. |
| 811583 | In rare circumstances, despite multiple threshold procedures on IMRSLOG are triggered, only the first invocation is able to successfully pack some rows. This eventually leads to IMRSLOG full situation, causing the workload of a single task performing random DMLs on several IMRS enabled tables to hang. |
| 811597 | When SSL is enabled, an attempt by SAP ASE to connect to a backup server which is down results in a hang. |
| 811606 | A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, involving updates to rows containing In-row LOB columns. |
| 811615 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log ...", may be reported during LOAD TRAN when DBCC TUNE with one of the options "ascinserts", "indextrips" or "oamtrips" was run for a table stored in a different database than the source database were the dump was taken. See KBA 2556287. |
| 811649 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrs_odmvcc_pack_row', together with a stack trace which includes the modules 'imrs_odmvcc_pack_au' and 'dropo' may be reported in the SAP ASE error log when dropping an On-Disk MVCC enabled table. See KBA 2562972. |
| 811653 | When a Replication Server DSI thread is down due to a DDL replication error, the DDL might be skipped when resuming the connection if granular permission is enabled on the SAP ASE server. |
| 811667 | In rare circumstances, if concurrent inserts are taking place into a Data Only Locked (DOL) table while REORG DEFRAG is executed, some inserted rows may not be visible after REORG DEFRAG is completed. |
| 811681 | In rare circumstances, the message ”timeslice error: spid < value > exhausted its 'time slice' of 100 milliseconds and additional 'cpu grace time' of 500 ticks (50000 milliseconds). It has been marked for termination.”, may be reported in the SAP ASE error log on a heavily used HADR setup, followed by the message "Current process infected with signal 11 (SIGSEGV)" in the module ‘ra__ci_destroy_stop_scanner’ together with a stack trace which includes the modules ‘ra__ci_destroy’ and ‘ra_ci_main_thread’ when a Rep Agent is shutdown. |
| 811690 | Wrong results may be returned when a LIMIT/OFFSET clause is used in a DISTINCT view. |
| 811697 | A 206 error, "Operand type clash: FLOAT is incompatible with MAINTENANCE TOKEN" or a 529 error, "Explicit conversion from datatype 'FLOAT' to 'UNITEXT' is not allowed.", may be reported when inserting FLOAT data with the statement cache enabled. See KBA 2558456. |
| 811698 | In rare circumstances, an 806 error, "Could not find virtual page for logical page < page_number > in database < database_name > .", together with a stack trace which includes the modules 'imrslogrec_fix_holes' and 'imrslogrec_logbounds' may be reported in the SAP ASE error log during boot time recovery. |
| 811699 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace that includes the modules 'firstcmd_workno', 'firstroot_workno' and 'sqlscript_parse', may be reported in the SAP ASE error log when the RETURN statement is used with UNION/MINUS/EXCEPT in a procedure in an SQLScript database. See KBA 2560830. |
| 811702 | DBCC IMRS('print', 'threshold', < database name > , 'null') may lead to incorrect values of min, max and default for the different threshold fields. |
| 811703 | A 3701 error, "Cannot drop the table ' < table_nname > ', because it doesn't exist in the system catalogs" will be reported when the dbo user tries to drop a table type that was created by another user. |
| 811706 | In rare circumstances, a 803 error, "Unable to place buffer < buffer_num > from cache < cache name > holding logical page < page_num > in sdes for object 'sysversions' - either there is no room in sdes or buffer already in requested slot", may be reported when executing a SELECT query against an On-Disk MVCC database. |
| 811716 | A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be raised when a query that includes a UNION VIEW with LIMIT clause and without an OFFSET clause is executed. See KBA 2556253. |
| 811719 | In an SAP ASE HADR environment, it is not possible to define the location of the database, configuration files, translog, log and backup directories during set up of Replication Server and RMA. It is now possible to provide user defined locations for the 5 directories in the resource file for configuring Replication Server and RMA through setuphadr. |
| 811766 | In rare circumstances, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database < database_name > because the target page is not a data page..." may be reported in the SAP ASE error log by IMRS recovery following a server crash, if an uncommitted transaction was logged on a new IMRSLOG page. |
| 811775 | If workload profiler is re-installed using installwlprofiler after capturing a workload, without doing a prior uninstall, then subsequent capture of workload using sp_wlprofiler 'monitor', may run into error 512, “Subquery returned more than 1 value. This is illegal when the subquery follows =, !=, < , < = , > , > =, or when the subquery is used as an expression”, followed by error 3621, “Command has been aborted”. This is due to stale statistics from the previous workload profiler installation. |
| 811787 | In an HADR environment where SAP ASE is configured for LDAP User authentication and the login mapping is set to 'create login', then internal login creation automatically initiated by SAP ASE during the login fails with error 3959 "New transaction cannot be started as Adaptive Server is in 'Inactive' HADR state. The command could not be completed." and the DSI for the master database goes down. |
| 811811 | A 594 error, "The UPDATE WHERE CURRENT OF to the cursor ' < name > ' failed because column ' < name > ' being updated was not specified in the SELECT list.", may be reported when an cursor update statement that references a temporary table is executed and the configuration option "optimize temp table resolution" is enabled. See KBA 2562119. |
| 811825 | Wrong results may be returned from a query that has complex OR clauses. See KBA 2563459 and SAP Note 2596598. |
| 811842 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'psort__dolscanpage' together with a stack trace that includes the modules 'psort__dolscanptn' and 'psort__dolscan', may be reported in the SAP ASE error log when REORG REBUILD with online option is executed on a round-robin partitioned DOL table with a global placement index. |
| 811850 | A 11060 error, "This statement has exceeded the maximum number of recompilations (10). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported when executing nested views and procedures. See KBA 2462416. |
| 811856 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'open__byname' followed by a stack trace that includes the modules ‘open_user_table', ‘cm_which_cache’ and 'q_setup_tab_cache_info', may be reported in the SAP ASE error log when selecting from a table variable with compatibility mode enabled. |
| 811864 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'rvm_validate_proc' followed by a stack trace that includes the modules 'proccreate', 's_crtproc' and 's_cache_stmt', may be reported in the SAP ASE error log when upgrading a SAP ASE 15.7-based server to a 16.0 SP03 based version. |
| 811882 | In rare circumstances, a 6189 error, "In-memory row storage RIDMAP check failed with < > error(s)." along with messages like "Number of maximum entries on RIDM_PAGE# < > is < > which is not between expected values < > and < > ." and "Check for Migrated rows in ridmap failed with errors printed above." may be reported when DBCC CHECKALLOC is run on an IMRS enabled database. |
| 811885 | In rare circumstances, a 7989 error, "The serial allocation flag was found to be improperly set in allocation unit < > , at extent ID < > , with alloc map = < > and objid = 8. This flag has been cleared by DBCC.", may be reported when DBCC TABLEALLOC is run with 'full' or 'optimized' option while concurrent DMLs take place. See KBA 2574619. |
| 811913 | The message, "Assertion (((mass_ptr)- > bpage- > anp.pptnid == SYSIMRSLOGS) || (((SDES *)((void *)0)) && ((SDES *)((void *)0))- > sobjid == SYSIMRSLOGS) || (MASS_CHANGERS_ACTIVE_COUNT(mass_ptr) == 0))", together with a stack trace which includes the modules 'bufunpredirty' and 'alterdb' may be reported in the SAP ASE error log when ALTER DATABASE is run while the diagserver binary is in use. |
| 811929 | In rare circumstances a user process may hang with a status value of "PLC sleep" as shown in system table master..sysprocesses, when running DUMP TRAN WITH TRUNCATE_ONLY on a database which has the database option "trunc log on chkpt" enabled. |
| 811935 | DBCC page() command is enhanced to print character encoding information. |
| 811943 | The message, "No memory for < bucketpool_name > bucket pool growth ( < value > bytes)", may be reported unexpectedly in the SAP ASE error log although memory is available in the memory global pool 'blockpool'. |
| 811954 | In a rare circumstance, a 603 error, "There are not enough system session descriptors available to run this query. Raise the value of the configuration parameter 'number of aux scan descriptors' or retry your query later.", followed by a 803 error, "Unable to place buffer < buffer > from cache < cache > holding logical page < page no. > in sdes for object < table name > - either there is no room in sdes or buffer already in requested slot", may be reported when a cursor declared against an On-disk MVCC table is opened. |
| 811967 | Only relevant for Business Suite extensions of SAP ASE: Unable to create view which is referencing non materialized temporary table which is prefixed by other user name. |
| 811968 | A 17260 error, "Can't run < sproc_name > from within a transaction", 226 error, " < command_name > command not allowed within multi-statement transaction" or 2762 error, "The < command_name > command is not allowed within a multi-statement transaction in the < db_name > database" may be reported when executing sp_spaceusage with 'set chained mode on'. |
| 811982 | Auto-IMRS partition tuning may get enabled for On-Disk MVCC enabled database if database is created without providing ROW STORAGE cache but is added later. |
| 811995 | The defined length of a column may be incorrect when creating an in-lined UDF with a datatype mismatch between the return table and SELECT statement. |
| 812006 | Under rare circumstances, SSL connections to an SAP ASE running in process kernel mode may hang during network I/O. |
| 812028 | In rare circumstances, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database < database_name > because the target page is not a data page..." may be reported in the SAP ASE error log by IMRS recovery following a server crash, if the size of IMRSLOG is large whereby log pages may need to be re-used during recovery. See KBA 2574681. |
| 812054 | The message, "Page Verification Error: Adaptive Server accessed a row that has an illegal length of..." followed by a crash of the backup server emulator process with the message, "Emulator interprocess communication failed with error state = 14, error code=32, system message=Broken pipe.", may be reported in the Backup Server error log when DUMP DATABASE is run if a database dump is taken using a dump configuration that includes the option WITH VERIFY=FULL. See KBA 2595456. |
| 812074 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace in the module 'ckpt_chores' or 'checkpoint', may be reported in the SAP ASE error log when DUMP TRANSACTION is executed. |
| 812086 | In rare circumstances, a 3404 error, "Could not open controlling database < value > of controlling database in multi-db transaction.", may be reported when MOUNT DATABASE is executed on a database that is in load sequence and a multi-database transaction was involved earlier. |
| 812120 | Under some circumstances, a 16805 error, "A LOB LOCATOR was used that is no longer valid: Either the transaction that created it has ended or it has been deallocated", may be reported when using LOB Locators to access the LOB Cache. |
| 812134 | A 208 error, "tempdb..tablename not found", may be reported when a temporary table, which is referenced by a stored procedure created by a user who is aliased to dbo, is recreated. |
| 812138 | In rare circumstances, the message, "CACHED ROW CHECK FAIL: Expected cached row with row id = < value > , to have the same row length as in page store but found a mismatch.", may be reported followed by a 15916 error, "Text pointer value < value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < number > , in row < number > located on page < number > , partition ID < number > for object with ID < number > and references first text page < number > ", when running DBCC CHECKTABLE on an IMRS enabled table. Additionally a 7928 error, "Index < name > is not consistent; found < number > leaf rows but < number > data rows. Drop and recreate the index.", and a 2510 error, "Key mismatch between index page < number > , partition ID < number > ; at offset < value > ; and data page < number > (row ID < number > ), partition ID < number > . Drop and re-create index ID < number > of table < name > in database < name > .", may also be reported. |
| 812142 | DBCC PAGE command has been enhanced to print decompressed data. |
| 812156 | For Java applications, if there is a stored procedure with output parameters, and if the output parameters come before input parameters, there is a possibility of incorrect values being stored for integers. See KBA 2571900 |
| 812173 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_fill_and_send_monProcessWaits' together with a stack trace which includes the modules 'conn_hdlr' and 'kisignal' may be reported in the SAP ASE error log when the monProcessWaits MDA table is queried. |
| 812204 | A 5702 error, "ASE is terminating this process" together with an access violation exception stack trace which includes the modules 'KiUserExceptionDispatcher' and 'RtlDecodePointer' may be reported in the SAP ASE error log when running installjava utility on Windows platform. |
| 812236 | In rare circumstances, the message, "STFreeAPool(0): package(0x < address > ) still in use", may be reported in the SAP ASE error log when the RepAgent scanner thread is still using a package while the native thread is attempting to release it when the stream between SAP ASE and SRS is down and the synchronous replication mode is enabled in an HADR setup. |
| 812241 | The message, "Assertion (objsdes- > sstat2 & SS2_WKTAB_SHARED_DES" together with a stack trace which includes the modules 'LePlanRelease' and 'close_shared_worktables', may be reported in the SAP ASE error log if a query execution internally requires the creation of a shareable work table while the diagserver binary is in use. |
| 812242 | An On-Disk MVCC database dump can be loaded with success into an archive database mistakenly. This will cause the metadata of the archive database to be corrupted. |
| 812249 | A dynamic prepared statement with LIMIT clause may return wrong result with limit value passed as a variable and executed multiple times for different LIMIT values. |
| 812266 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrs_odmvcc_pack_row', together with a stack trace which includes the modules 'imrs_odmvcc_pack_au' and 'imrs__packthd_work' may be reported in the SAP ASE error log when using On-Disk MVCC tables. |
| 812268 | The Workload Profiler will report information in the new columns MaxInsRowsInXact, MaxDelRowsInXact and MaxUpdRowsInXact of the MDA table master..monOpenObjectActivity respectively for the maximum number of inserts, deletes and updates that were executed on a user table under any transaction. |
| 812269 | The MDA table, monRepStreamStatistics, may report inaccurate values for buffer pool package related monitoring in columns TotalPopulatePkgTime, TotalWaitToSendTime and TotalSendTime when stream mode replication is enabled. |
| 812273 | A signal 11 error followed by a stack trace that includes the modules 'smd_sample_server' and 'sm_exec_command' may be reported when executing the sybmon "sample" command when "allocate max shared memory" is set as DEFAULT (0). |
| 812300 | The IMRS data cache high watermark stored in the header of a transaction dump is empty mistakenly. The will result in LOAD TRANSACTION not checking whether the target cache is big enough and it may eventually run out of memory when reapplying the IMRSLOG transactions. |
| 812304 | Spurious errors may occur when trying to create a Global Temporary Table. |
| 812308 | Under certain circumstances, the message, "Assertion (lk_sufficient_tablk(sdes, SH_INT)) failed" followed by a stack trace that includes the modules 'fglock_verify' and 'dol_qualrow', may be reported in the SAP ASE error log when INSERTs, UPDATEs or DELETEs are executed on an object whose metadata has previously been bound using DBCC TUNE(bind_des, < dbid > , < objname > ) while the diagserver binary is in use. |
| 812309 | A 3624 error, "Truncation error occurred", may be reported when executing INSERT involving NUMERIC datatypes and the statement cache is enabled. This is due to CR 805165 which addressed a spinlock contention performance scenario on the statement cache. The fix introduced by CR 805165 is now disabled by default. It can be enabled using a new trace flag 11013. |
| 812311 | Increasing the configuration option 'user log cache' will significantly increase the SAP ASE memory consumption unexpectedly. See KBA 2570113. |
| 812323 | The message, "SYBMULTBUF ERROR: Volume validation error: attempt to flush < file_name > ”, will be reported in the SAP Backup Server error log on Windows platform when DUMP database or DUMP transaction is executed and the ASE configuration option 'enable buffered io for load' is enabled. |
| 812328 | In rare circumstances, a 12311 error, "Internal error: address lock request on page < page number > of index id < index id > of table < table name > (id = < object id > ) in database < database name > failed with status < value > . No need to drop the index.", may be reported when running INSERT, UPDATE, or IMRS PACK operations and the transaction rollback. See KBA 2577215. |
| 812339 | A 3606 error, "Arithmetic overflow occurred.", may be reported while executing sp_helpdb on a database having a log device greater than 1TB. |
| 812347 | DDLGen fails to get the expected cache size |
| 812352 | A 18236 error, "Error updating the audit flags. This is a system error. Contact a user with System Security Officer (SSO) Role", may be reported when executing sp_audit to turn on any global audit option with the compatibility mode enabled. |
| 812354 | The execution of a DUMP or LOAD command will hang in the module 'login_response' when it is run from the threshold action procedure and the option 'net password encryption' is enabled in the SYB_BACKUP backup server. |
| 812360 | A 12034 error, "Collection of monitoring data for table ' < MDA Table > ' failed due to insufficient memory. Retry when there is less load, or fewer users, on the server. < num_row > rows were not returned because < number_byte > bytes of memory could not be allocated.", may be reported when querying some MDA tables in a heavy-loaded system. |
| 812375 | The message, "Assertion (dol__can_clear_PUNCbit(sdes, &lkreport))" together with a stack trace which includes the modules 'bt__markdeleted' and 'bt__undo_leafinsdel', may be reported in the SAP ASE error log when rolling back an INSERT and the row is marked as committed unexpectedly while the diagserver binary is in use. |
| 812381 | A 16053 error, "The command 'DISK REINIT' with property 'IMRSLOG' is currently not supported in SAP Adaptive Server Enterprise Edition.", may be reported in the SAP ASE error log when mounting an IMRSLOG enabled database. |
| 812390 | In rare circumstances, message 725, " < COMMAND > : failed to allocate 96 bytes from Adaptive Server's main memory pool.", may be reported for some statement when the Global Fragment Pool size is under configured. Commands and transactions that access IMRS tables may also fail after this error message is reported. |
| 812391 | The message, "Assertion (sdes- > sstat & SS_NODATA || !RID_ISZERO(&odmvcc_mig_rid))" together with a stack trace which includes the modules 'imrs_getrow' and 'imrs_get_snapshot_version', may be reported in the SAP ASE error log when a DML is run while the diagserver binary is in use. Alternatively, the message, "Assertion (++entered_once == 1)" together with a stack trace which includes the modules 'imrs_gcthd_work' and 'imrs__gc_row_version', may be also reported. |
| 812392 | In rare circumstances, the message, "Current process infected with signal 6" in the module 'gsignal' together with a stack trace which includes the modules 'dcl_find_interface' and 'dcl_property' may be reported in the SAP ASE error log when the SAP ASE server is gracefully shut down and a site handler is configured. |
| 812393 | An erroneous message, "Assertion (upd_ok) failed" in the module 'altdb__check_fwd_rows', may be reported in the SAP ASE error log if DBCC DBREPAIR with 'redo_shrink' option is executed to repair a partially completed shrink database and the diagserver binary is in use. It is a false assertion message from the diagserver, data is NOT corrupted. NO symptoms are reported in dataserver. |
| 812416 | A 632 error, "Attempt to move memory with an incorrect length of 51152. Maximum allowed length is 16384.", may be reported when updating the size of a large Non Volatile Cache (~100GB) using the sp_nvcacheconfig stored procedure. |
| 812418 | On Windows platforms, setuphadr may fail to create route when SSL is enabled. |
| 812420 | The message, "Assertion (ra_ci_stream)" together with a stack trace which includes the modules 'ra__ci_syslogs_scanner_destroy' and 'ra__ci_sleep_on_detached_stream' may be reported in the SAP ASE error log if the RepAgent is shutdown and streaming replication is enabled while the diagserver binary is in use. Alternatively, the message, "Assertion ((xlr- > loh.loh_op == XREC_DELETE) || (xlr- > loh.loh_op == XREC_IDELETE) || (xlr- > loh.loh_op == XREC_DOL_DELETE))" together with a stack trace which includes the modules 'ra__ci_syslogs_scanner_scan' and 'ra__save_befimg' may be also reported. |
| 812430 | When View UDFs and Table UDFs are mixed in the same batch or stored procedure, wrong results for Table UDFs may occur due to incorrect parameter handling. |
| 812460 | SAP ASE using external security services such as Kerberos can suffer from unbalanced engine load with an excess of runnable tasks waiting for engine 0. |
| 812472 | A 11060 error, "This statement has exceeded the maximum number of recompilations ( < value > ). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported when executing another user's stored procedure. |
| 812494 | When performing an unplanned failover in an HADR system with stream replication enabled, Rep Agent may shutdown with a 9219 error, "RepAgent : Internal coding error". |
| 812496 | A 8015 error, "Adaptive Server has truncated parameter number 3 passed to rpc 'as_db_dam' on server < server_name > . The remote server does not support character or binary data wider than 255 bytes." may be reported when DUMP DATABASE is executed in server passthrough mode and the database option 'allow incremental dumps' is enabled. |
| 812517 | Sometimes the SAP ASE error log may get filled up with warning messages like "WARNING: Memory protection change failed: Invalid argument, address" when trace flag 767 is enabled. |
| 812519 | The system stored procedure, sp_logiosize, is enhanced to support large buffer pool I/O usage for sysimrslogs system table in IMRS-enabled databases. |
| 812566 | In rare circumstances, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database < database_name > because the target page is not a data page..." may be reported in the SAP ASE error log by IMRS recovery following a server crash, if the first page of the IMRSLOG is not initialized and the first transaction is not flushed in the IMRSLOG. |
| 812584 | In rare circumstances on a heavily-loaded multi-engine SAP ASE system, the execution of UPDATE INDEX operator as shown by sp_showplan may hang and result in a 1105 error, "Can't allocate space for object < objname > in database < dbname > because < segname > segment is full/has no free extents", reported. |
| 812588 | In rare circumstances, the REP AGENT task cannot be stopped when stream replication is enabled. The modules 'upyield', 'ra_ci_main_thread' and 'ra__ci_destroy_stop_scanner' will be reported for the hanging task when dbcc stacktrace( < spid > ) is run. |
| 812591 | For SAP ASE running on Windows or AIX platform, under rare circumstances, the DUMP DATABASE command or 'sp_dropserver SYB_BACKUP' may hang when SSL is enabled. |
| 812620 | Under rare circumstances, the DUMP TRANSACTION command may hang for SSL enabled connections. |
| 812633 | A 102 error, "Incorrect syntax near 'passwd'" may be reported when DUMP TRANSACTION or LOAD TRANSACTION is executed with the PASSWD option. |
| 812646 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'tdsrecv_fetch' together with a stack trace which includes the modules 'conn_hdlr' and 'kisignal', may be reported in the SAP ASE error log when missing cursor and dynamic statements are replayed by Workload Capture. See KBA 2585531. |
| 812661 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'cfg__altercacheconfig' together with a stack trace which includes the modules 'cfg_main' and 's_execute', may be reported in the SAP ASE error log when the built-in, config_admin(), is executed. |
| 812678 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra_malloc_mempool' and 'ra_mempool_alloc_internal' may be reported in the SAP ASE error log when the Rep Agent STP Manager Thread terminates abnormally leading to corruption in the Rep Agent Memory Pool. |
| 812690 | sp_sysmon reports rows inserted for Fully Logged APL Heap Table from non-logged inserts such as worktables and materialized tables like sysprocesses and sysmonitors. See KBA 2586495. |
| 812721 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace which includes the modules 'ex_logprint' and 'ra_CIStreamMessageCallback', may be reported in the SAP ASE error log when synchronous mode replication is enabled. |
| 812741 | The message, "Assertion (XACT_CHECK_STATE(pack_ctx- > pctx_xprm.xdes, XACT_IN_CMD))” together with a stack trace which includes the modules 'imslog__movetruncpt_break_xact' and 'd__imrs_log_trunc' may be reported in the SAP ASE error log when the IMRSLOG is being truncated while the diagserver binary is in use. |
| 812750 | The error, "SYBMULTBUF ERROR: Error in acknowledging command '166' to the archive emulator..." will be printed in the SAP backup server error log at load time when some of the database devices is using buffered I/O. On Windows platforms, the message, "SYBMULTBUF ERROR: Volume validation error: attempt to flush..", will be printed in the SAP Backup Server error log also at dump time. |
| 812840 | A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, when compression is enabled. |
| 812892 | A 12406 error, "Failed to find the last row marker for transaction ( < page# > , < rowed > ) in sysimrslogs for database ' < dbname > ' ( < dbid > ). The sysimrslogs row is corrupted." in the module 'imrslogrec_fix_lastlog' together with a stack trace which includes the modules 'boot__recover_and_online' and 'imrslogrec_logbounds', may be reported in the SAP ASE error log during ASE startup while recovering an IMRS enabled database. |
| 812945 | In an SAP ASE HADR environment, if all the five parameters, namely the location of the database, configuration files, translog, log and backup directories, for configuring Replication Server and RMA are not provided in the resource file, the RMA will not start leading to failure during execution of setuphadr. |
| 812950 | After upgrading from a pre-16.0 SP03 server to a 16.0 SP03 based server, if SSL is configured and the SSL listener is specified in interfaces file, then the server certificate may not be decoded correctly by the server if the certificate file has the private key before the certificates. This may lead to the upgraded server failing to start up. |
| 812953 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < dbname > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), ...", together with a stack trace which includes the modules 'xsc__sysimrslogs_getnext' and 'apf_imrslog_allocunit' may be reported in the SAP ASE error log when DBCC LOG is run for an IMRS enabled database. |
| 812955 | Even after the successful application of the fact_table_hint, optimizer constructed the final plan using the subplan generated for compatibility mode. |
| 812978 | syslogshold may occasionally show a row with a transaction start date of 1 Jan 1900. See KBA 2587185. |
| 813005 | In rare circumstances on an HADR setup, a 156 error, "Incorrect syntax near the keyword ' < value > '", may be reported in the standby SAP ASE error log during the replication of CREATE VIEW, resulting in the DSI replication stream to implicitly stop. |
| 813014 | Once a scalar-valued SQL UDF is referenced in a query, or in the text of a DDL command, any attempt to drop or replace the SQL UDF will result in error 3702, stating that the SQL function cannot be dropped or replaced because it is currently in use. See KBA 2553759 |
| 813096 | In rare circumstances, DUMP and LOAD operations may not succeed when using an SSL connection between SAP ASE and backup server on Windows and AIX platforms. |
| 813108 | In case a workload involves tables created by multiple logins, workload profiler is unable to archive tables other than those created by login dbo. |
| 813109 | A network connection using SSL may hang during login and ASE may get CPU bound. |
| 813110 | A table with compressed LOB columns uses more space when populating the table via VIEWs. See KBA 2594175. |
| 813112 | In rare circumstances, a 9219 error, "RepAgent( < dbid > ): Internal coding error." or a 9254 error, "RepAgent( < dbid > ): Could not locate schema version for object id ' < objid > ' in the transaction log.", followed by a 9204 error, "RepAgent( < dbid > ): Could not locate schema for object with id = ( < objid > ), current marker ( < pageno > , < rowno > )" may be reported in SAP ASE error log when RepAgent is configured for stream replication and a replicated table schema is changed. |
| 813114 | Sybmon "status" and "engines" commands report the wrong engine status as "Not Halted" for memory dump generated by either "DBCC MEMDUMP" command or manual command "memdump" with engine halt option. See KBA 2596784. |
| 813129 | When Rep Agent is configured for stream replication and a retryable error occurs after the execution of a DDL command altering the schema of a table, Rep Agent may fail to process again the log records requiring the old schema of the table. As the wrong schema is sent to SRS, the DSI may shut down with an error from ASE such as a 207 error, "Invalid column name ' < column_name > '". |
| 813140 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memalloc' together with a stack trace which includes the modules 's_cpparamd' and 'vu_res_view', may be reported in the SAP ASE error log when executing multiple SELECTs on deeply nested VUDFs in a batch. |
| 813142 | 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).", will be reported after a cursor is opened and a SELECT query references a temporary table in the same batch. |
| 813236 | A 692 error, "Uninitialized logical page < value > was read while accessing < information > . Please contact SAP Technical Support", may be reported when executing DUMP TRAN WITH NO_LOG on a database that is marked as read-only. |
| 813238 | The message, "Attempt to push affinity to a non-existent engine", may be reported in the SAP ASE errorlog when performing a DISK UNMIRROR command to set the secondary mirror as the primary device while running in process mode. See KBA 2597350. |
| 813244 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < dbname > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), ..." may be reported in the SAP ASE error log when DUMP DATABASE is run for an IMRS enabled database on which the IMRSLOG segment was first removed and then re-inserted using ALTER DATABASE command. |
| 813248 | Executing sp_displaylogin with a wildcard may show different information of "Password expiration interval", "Minimum password length" and "Maximum failed logins" from information displayed individually after you change the attributes of one of the login accounts. See KBA 2598951. |
| 813259 | The system stored procedure, sp_helpdb, will not report IMRSLOG devices used by a database if they don't have the direct I/O option enabled. |
| 813266 | New statements are not cached after a 701 error, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", is reported resulting in a performance loss and high engine utilization. See KBA 2600140. |
| 813268 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'text_tabcheck' together with a stack trace which includes the modules 'dol__imrs_datarows_check' and 'checktable' may be reported in the SAP ASE error log when DBCC CHECKTABLE is run on a table that is DRC or IMRS MVCC enabled. |
| 813283 | SAP ASE workload capture may record incomplete pcap file names in the SAP ASE error log especially when the server is configured with multiple engines. |
| 813303 | In a HADR environment, when a Primary SAP ASE is rebooted, it may switch to Standby mode with error 208, "sysservers not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", followed by error 11221, "No external login for suserid 0, server name ' < value > '", reported in the SAP ASE error log. |
| 813348 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < dbname > ' because the requested RID has a higher number than the last RID on the page", may be reported in the SAP ASE error log during the reconciliation-redo phase of IMRSLOG recovery, if at the end of the reconciliation-redo phase, the old and new last page of the log happen to be on different fragments. |
| 813401 | Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled. |
| 813451 | sp_configure 'Non-Volatile Caches' incorrectly shows "User Defined NV Cache" and "NV Cache Threshold" as configurable options. See KBA 2604896. |
| 813470 | Executing ALTER TABLE to change the locking scheme to ALL PAGES or DATA PAGES for an IMRS enabled table will succeed if the same ALTER TABLE command also contains add/modify/drop column command. |
| 813473 | In rare circumstances on a heavily-loaded multi-engine Solaris x64 system, SAP Adaptive Server may hang in the module 'xls_flush_plcqueue' when the configuration option "user log cache queue size" is enabled while the Private Log Cache of a user task is being flushed in the transaction log. |
| 813501 | In very rare circumstances, if CREATE INDEX and at least two updates are run in a same batch, then concurrent updates, affecting the same set of rows, qualified by the second update onwards, might succeed wrongly. |
| 813514 | When a cursor at snapshot isolation is opened on On Disk MVCC enabled tables, and 20 or more such tables are involved in the cursor, any command executed from the same session post open cursor may hang forever. |
| 813520 | In rare circumstances, a 12309 error, "Expanding update on object < name > in database < name > cannot succeed on page < number > , because the contiguous_free_bytes of < value > is less than the difference of < value > between new rowlen and old rowlen. This is an internal error. ASE is terminating this process.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'dol__expand'/'dol__delete_insert' and 'dol_update' while performing an expanding UPDATE on a table that is stored in an On-Disk MVCC enabled database. |
| 813523 | The message, "timeslice < value > , current process infected at < value > " in the module 'pthread_cond_wait' together with a stack trace which includes the modules 'np_io_read' and 'ct_results', may be reported in the SAP ASE error log when the Rep Agent is shutdown while the Replication Server is not reachable and the synchronous stream replicarion is enabled in an HADR setup. |
| 813529 | Handling of default values for global temporary tables is not correct. See KBA 2608519. |
| 813535 | On heavily loaded systems, spinlock contention may be observed on statement cache when multiple INSERT statements with similar data of numeric datatype are present. Use the run time trace flag 11013 to enable the use of a single cached plan for multiple INSERT statements. |
| 813536 | A 267 error, "Object < name > cannot be found" in the module 'open_globaltt', may be reported in the SAP ASE error log when running ONLINE DATABASE after having loaded a database dump. See KBA 2607240. |
| 813551 | In rare circumstances, the message, "Assertion(!sdes || sdes- > saccerrcode == ACCERR_UPDATE_OK) failed" may be reported in the SAP ASE error log while PACK operation is in progress and the diagserver binary is in use. |
| 813573 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'pss__release' together with a stack trace which includes the modules 'quitfn_indirect' and 'pss_unkeep' may be reported in the SAP ASE error log when a task disconnects after executing some queries that involve INDEX scans on MVCC enabled tables. |
| 813574 | When upgrading from a pre-16.0 SP03 server to a 16.0 SP03 based server, the auditing process may terminate with a 716 error, "Unable to allocate memory of size < num > bytes from the 'default' pool'", reported in the SAP ASE error log when the 'auditing' option is disabled. See KBA 2609783 |
| 813662 | The message, "Current process infected with signal 8 (SIGFPE)" in the module 'imrs_get_pdes_imrs' together with a stack trace which includes the modules 'altertab' and 'alt__set_option' may be reported in the SAP ASE error log when ‘ALTER TABLE < name > SET ROW_CACHING ON’ is run in an IMRS enabled database after LOAD DATABASE was run. |
| 813684 | XPserver may fail to start with failure to load dependent libraries if the path to the SYBASE directory is longer than about 60 characters and JVM services are in use |
| 813721 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrsm__alloc_metadata' together with a stack trace which includes the modules 'imrs__recover_insert' and 'imrslogrec_redo_log', may be reported in the SAP ASE error log when boot time recovery on an IMRS enabled database is taking place. |
| 813849 | The ASE backup server process in AIX, SOLARIS and HP-UX platforms may leak some memory when dumping and loading databases, which causes it to grow until it exceeds the O/S memory limit. The backup server may then hang or crash with a core dump with the message, "Backup Server: 1.1.2.8: Memory allocation failed in bs_mkvdisktab for a sd_vector allocation. This DUMP or LOAD session must exit.", reported in the error log. See KBA 2605477. |
| 813852 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'index_compress_page_with_prefix' together with a stack trace which includes the modules 'redo_bt_rebldleafs' and 'recovery' may be reported in the SAP ASE error log during the recovery of a transaction log dump which contains index compressed operations. See KBA 2614971. |
| 813853 | A 6931 error, "The table 'sysimrslogs' with ID 59 in database < name > is corrupt. Page < value1 > is linked to page < value2 > that either is out of the database boundary or belongs to an invalid fragment.", together with a stack trace that includes the module 'imrslog_validate_nextpg' may be reported in the SAP ASE error log after loading an IMRS database dump into an IMRS database with a bigger IMRSLOG size. |
| 813870 | Cached query plans may not be recompiled even when the total rowcount on the tables involved in the cached plans changes by more than the value configured by the ‘recompile_factor’ attribute. |
| 813886 | Under rare circumstances, a connection may hang after receiving a cancel request from the client. See KBA 2633664. |
| 813895 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrs_abort_to_imrv' together with a stack trace which includes the modules 'xact_rollback' and 'le_runerr', may be reported in the SAP ASE error log when a DML on an On-Disk-MVCC enabled table is rolled back after a 728 error, "Allocation of size < value > bytes from the row storage cache, ' < name > ', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < value > ", is encountered. |
| 813896 | sp_imrs show, tables does not show any information when executed on an On-Disk MVCC enabled database. |
| 813897 | A 18118 error, "Object 'sysimrslogs' does not exist in this database" will be reported when executing sp_imrs show, "all metrics", < imrs_cache name > on an On Disk MVCC enabled database. |
| 813898 | A 2714 message, "There is already an object named '##...' in the database.", may be reported in the SAP ASE error log when an attempt is made to create an inlined table-valued UDF that references a Global Temporary Table that has yet to be materialized. |
| 813968 | In rare circumstances, the message, "Assertion (latch_free_btree && !lfb_skip_leaf) failed", may be reported in the SAP ASE error log while boot time recovery of a database is in progress and the diagserver binary is in use. |
| 813971 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'apl__startscan' together with a stack trace which includes the modules 'xsc__sysimrslogs_setscan' and 'db_high_ts_on_logpg', may be reported in the SAP ASE error log while recovering a database that is Data Row Cache enabled. |
| 813994 | In some circumstances, the message, "Rep Agent detected error 406 with message 'CI API call DropLastMetaObj() failed' at line 9670 in file ra_ci_cmd.c." and the message "RepAgent( < dbid > ): Warning: The size of the stream buffer is too small ( < value1 > bytes). Use sp_config_rep_agent ' < dbname > ', 'stream buffer size', ' < value2 > ' to increase it.", may be reported in the SAP ASE error log when streaming replication in synchronous mode is enabled. See KBA 2618490. |
| 813997 | In an HADR environment with a DR node configured, under rare circumstances unplanned failover may fail and the message "Failed to change the configuration option 'HADR mode' to 1." may be seen in the log of the to-be-made primary SAP ASE. |
| 813998 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qualpage' followed by a stack trace that includes the modules 'apl__startscan' and 'startptnscan', may be reported in the SAP ASE error log when a JDBC client executes queries with property DYNAMIC_PREPARE set to true and the parameters "abstract plan load" and "enable literal autoparam" are enabled in SAP ASE. See KBA 2617753. |
| 814032 | A 6812 error, "Failed to PACK < x > inserted and < y > migrated rows in IMRS for partition ' < name > ' with partition id < value > and indid < value > of table ' < name > '" may be reported when CREATE CLUSTER INDEX is run in an IMRS enabled database after boot/load recovery. |
| 814059 | In rare circumstances, for On Disk MVCC enabled tables, the number of UPDATE ROW locks taken by SAP ASE may be higher if value of the configuration parameter 'imrs cache utilization' is set to lower value. |
| 814168 | Enable IMRS recovery using backwards scan of sysimrslogs, for improved performance, and efficient memory usage of IMRS during recovery. |
| 814240 | The message, "Current process infected with signal 11" in the module 'CtlibRemoteAccess::getSubstValue' together with stacktrace that includes the moedules 'CtlibRemoteAccess::getColumnValues' and 'RPCRemoteAccess::getNext', may be reported in SAP ASE error log when 'granular permission' is enabled and a query, involving user created built-in functions and proxy tables, is executed. |
| 814332 | The message, "Current process infected with signal 11", followed by a stack trace that includes the module 'mda_calc_proc_hdr_mem_KB' and 'mda_populate_monCachedProcedures' may be reported in the SAP ASE error log while querying the monCachedProcedures MDA table. |
| 814341 | In rare circumstances, DML/scanner using isolation level 1 or isolation level 2 may skip committed INSERTED rows, if IMRS_PACK task is concurrently packing same set of rows. |
| 814358 | In rare circumstances, during boot time recovery of an IMRS enabled database some transactions may be ignored when the Adaptive Server is impolitely shut down and the corresponding IMRSLOG pages for these transactions are located 512 pages beyond the last fully committed transaction and a previous boot time recovery did not recover IMRSLOG. The message, "Empty oldest insert xact. No need to run imrslog recovery.", is reported in the SAP ASE error log. |
| 814433 | A 12336 error, "Definition time object 'database ' < dbname > ' ( < dbid > ), object ' < objname > ' ( < objid > )' found at run time as an attempt to drop the table had failed in a previous query. Please drop the above mentioned table using the DROP TABLE command." may be reported when trying to access a table after loading a database dump that was taken while the table was being created. |
| 814462 | If the option 'enable dump history' is enabled and the DUMP or LOAD command uses the syb_tsm library with more that one stripe, the stripe name stored in the dump history file for each of the stripes will be the result of concatenating the previous stripe name. When the length of this is greater than 255 bytes, a 11076 error, "The name '' is too long. Maximum length is 255." will be reported, although the dump itself is successful. See KBA 2629866. |
| 814479 | A 18121 message, "Unrecognized change attribute option." is reported in the SAP ASE error log when the procedure sp_chgattribute is used to change the 'optimitistic_LFB' attribute of an index. |
| 814574 | A 12832 error, "The LDAP URL string ' < LDAP server URL > ' is invalid. LDAP subsystem reported error 'Can't contact LDAP server'", may be reported when using sp_ldapadmin to create secure LDAP connections. |
| 814613 | The message, "rapidlog unable to open file ..." and "timeslice -1501, current process infected" followed by a stack trace that includes the module 'worcap_packet', may be reported in the SAP ASE error log when capturing a workload. |
| 814619 | The message, "Extending database by < value > pages ( < value > megabytes) on disk master", may be reported instead of a 5044 error, "ALTER DATABASE failed. Database < dbname > cannot be larger than the smallest database ( < dbname > ) that uses it as a template.", when ALTER DATABASE is run to extend a template database being used by a relaxed durability database whose size cannot accommodate the new size of the template database. |
| 814649 | A 325 error, " Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be reported when a query, which involves columns from an INNER JOIN being used in an ORDER BY clause, is executed against a VIEW and ROW LIMIT is applied. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on Power 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Solaris on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP03 PL04, ASE SP03 PL04, SP03 PL04, 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)