/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 SP02 PL07. 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 |
|---|---|
| 722778 | When executing DBCC CHECKSTORAGE, the worker processes created show the current database name, instead of tempdb, in the 'tempdbname' section of sp_who output. See KBA 2119852. |
| 725714 | A new feature request to avoid sysattributes look-ups for user defined role activation during login processing. |
| 745608 | CREATE INDEX allows '.' (period) in the index name with quoted identifiers. Once created, the index then can not be dropped through normal means. See KBA 2475406. |
| 745786 | In rare circumstances, an 871 error, "Process < spid > is trying to release a latch on buffer < buffer_address > (dbid: < dbid > , pageno: < pgid > ) without holding a latch on the buffer." may be reported after a resource governor error is hit. |
| 761436 | When create a DESC global clustered index on a roundrobin partitioned table, then reorg rebuild the table may fail for error 1530: "Create index with sorted_data was aborted because of row out of order". |
| 766251 | sp_helpconfig "heap memory per user" with a new value shows the size of memory in kilobytes, but it should be in bytes. |
| 767440 | The built-in ISNUMERIC() incorrectly returns 1 (indicating that conversion to int, float, money or decimal is guaranteed to be allowed) for some inputs such as '.', ',', '$', '+', '-', 'e' that can appear in numeric values but are not valid numeric values on their own. See KBA 2053654. |
| 778210 | Under rare circumstances, an 1105 error, "Can't allocate space for object 'syslogs'...", may be raised when trying to extend a database if the last chance threshold had been reached and there are many processes in log suspend state waiting for the log space to become available. |
| 779014 | In rare circumstances, inserting rows into a database that has the option 'trunc log on chkpt' enabled may hang. |
| 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. |
| 784112 | Exclusively for Business Suite users of Adaptive Server, the materialization of temporary tables were modified to take latest information from catalog. |
| 787389 | On Windows platform, if SAP ASE runs out of room in the socket table, the server will permanently stop listening for new connections even after sockets become available again. |
| 790982 | A spid may hang and be unkillable if the client is unable to receive or stops receiving network requests from SAP ASE running on AIX. See KBA 2000952. |
| 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. |
| 794379 | Exclusively for Business Suite users of Adaptive Server, the materialization of temporary tables were not exposed via ddl syntax explicitly |
| 795985 | Only relevant for Business Suite extensions of SAP ASE: Error 269 "Clustered index row entry for data page 8484 is missing in index page 1001 of table '##dept01000430016691309' in database 'tempdb'; index row contains data page 1009 instead. |
| 796164 | A 3702 error, "Cannot drop or replace the encryption key ' < encryption_key_name > ' because it is currently in use.", should be reported when DROP ENCRYPTION KEY < encryption_key_name > is run while the encryption key is still referenced, but the key was dropped mistakenly and no message was raised. |
| 796208 | Memory leak may happen in function create_standard_acl_nt() since AllocateAndInitializeSid() is used. |
| 796242 | In rare scenarios, SAP ASE diagserver (dataserver not affected) when executing a partition level utility like split partition or move partition may hit error 806 "Could not find virtual page for logical page < > in database < > ." along with a stacktrace involving module like 'rbld_rebuild_indexes()', while executing a partition level utility exercising partition level locking mechanism, which needs to rebuild indexes on a table with CLUSTERED INDEX. |
| 796418 | Remove a number of duplicate wait events to improve the accuracy of the wait event diagnostics. |
| 796566 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'Lop::lopProcessTree' together with a stack trace which includes the modules 'Lop::lopProcessTree' and 'lopGenerate' or in the module 'OptBlock::_OptInitProducerPj' together with a stack trace which includes the modules 'OptBlock::OptPhaseInitPj' and 'OptGlobal::GblAssignOptId', may be reported in the SAP ASE error log when a GROUP BY is used in a subquery and the subquery selects only a CONSTANT in its projection and the subquery does not have a HAVING clause. See KBA 2290097. |
| 796914 | Only relevant for Business Suite extensions of SAP ASE: the materialization of temporary tables fails if source table is a non-existing or a system table. |
| 797068 | Message 10330 is raised when table created by users aliased as dbo, are accessed by users of dbo owned stored procedure |
| 797077 | Occasionally, a 712 message, "There is insufficient heap memory to allocate < nn > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system", may be raised, and "XML session heap memory < aa > , size < mm > bytes is not freed" could be found in the error log for the diagserver when XML table related queries are intensively used in concurrent sessions. See KBA 2453962. |
| 797416 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qremap__obuf' followed by a stack trace that includes the modules 'qremap__tree', 'qremap__tmpobj' and 'proctree_copy', may be reported in the SAP ASE error log when declaring a table variable with a CHECK constraint. See KBA 2551743. |
| 797450 | A 2809 error, "Request for view < table_name > failed because < table_name > is a table object." may be reported during the execution of a stored procedure that has a view reference if the stored procedure was initially compiled and later the view was dropped and a table was created with the same name as the dropped view. See KBA 2297847. |
| 798060 | A 209 message, "Ambiguous column name < column_name > ", may be incorrectly reported when executing queries that involve table variables. See KBA 2308860. |
| 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. |
| 798781 | In rare circumstance, a 7105 error, "TEXT/IMAGE/UNITEXT page < page # > does not have a next page. Either there is a suspect text page chain, or transaction isolation level 'read uncommitted' has been set. Database tempdb, table < table name > , first text page < page # > ", may be reported when inserting data into a UNITEXT column. |
| 799064 | A 2514 error, "Table Corrupt: Type id 56 (type name = 56) does not match between systypes and syscolumns" maybe reported by DBCC CHECKCATALOG on a database containing table-valued functions. |
| 799127 | A 804 error, "Unable to find buffer '0x%lx' from cache '%.*s' holding logical page '%u' in sdes '0x%lx' kept buffer pool for object '%.*s'.", maybe reported when queries generate DOL worktable and truncate it. |
| 799147 | Error 1295 "Unconditional lock request for table or page 'pageid', dbid 'dbid' was made while holding a latch." may be reported when btree index splits. |
| 799194 | An 806 error, "Could not find virtual page for logical page < > in database < > " may be reported after loading a database dump that is followed by one or more transaction dumps while trying to access a page, if the database was shrunk before taking the database dump or a transaction dump followed by a database extension that was captured in a following transaction dump. |
| 799308 | A 12306 error, "No table lock on object < system_tablename > in database < proxy_dbname > ", may be reported when executing SELECT INTO from a source system table into a proxy database as a non-sa user. |
| 799428 | When the configuration parameter 'extend implicit conversion' is set and an implicit varchar to numeric conversion is performed, the precision and scale of the resulting numeric might exceed their respective maximum values. For varchar lengths greater than 77, the resulting numeric would consist of uniquely post-decimal digits (i.e. NUMERIC(77,77)), which was not the intent. Also, extended implicit conversions erroneously suppressed truncation errors for conversions between character and int/numeric types. |
| 799493 | A 29006 error, "Invalid DOL data row pointer: row < > with status 0x800 must be normal row instead of compressed row" may be reported when running SELECT-INTO while the compatibility mode is enabled and some of the tables are compressed. See KBA 2327918. |
| 800118 | Error indicating "missing text value in procedure" occurs when nested procedures uses TEXT (LOB) type local variables and assigns at least 2 LOBs in a single SELECT statement. |
| 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. |
| 800350 | KBA 2550451. Infected with signal 11 (SIGSEGV) error in open_range() while executing GRANT ALL permissions on a view that is created on a global temporary table. |
| 800915 | A 926 error, "Database 'tempdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause", followed by error 1619, "Could not open TEMPDB, unable to continue." may be reported in the SAP ASE error log when loading a database dump of the master database. |
| 801343 | KBA 2359108 - Incorrect statistics may be generated when when using the "with hashing" option with update statistics, |
| 801459 | The message, "One or more entries in the logsegment segment free space counts in database ID < dbid > was found to be negative and has been set to 0.", may be incorrectly reported in the SAP ASE error log at boot time when SAP ASE reserves few syslogs pages while recovering the database but before the unreserved pages information is read. |
| 801788 | After running command "Reorg rebuild < table_name > < index_name > ", index pages are not compressed. |
| 801789 | When "set forceplan on" is enabled, the internally generated abstract plan may lead to very inefficient plan to satisfy the forceplan for the queries which involved min/max operations. See KBA 2364881. |
| 801872 | A 1530 error, "Create index with sorted_data was aborted because of row out of order", may be reported instead of error 15451, "You cannot encrypt/decrypt column < column_name > because it belongs to a clustered/placement index on table < table_name > . Drop the index before the ALTER command, and recreate it afterwards.", when the encryption key of an encrypted column, that is part of a clustered index key, is changed while the non-clustered indexes for this table are being rebuilt. |
| 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]. |
| 802418 | The message, "java.lang.OutOfMemoryError: GC overhead limit exceeded", together with error 10762, "Cannot initialize the Java Virtual Machine because either the Java class library or PCA plugin library is missing, corrupted, or incompatible with the current server release. Contact your System Administrator for help.", may be reported when executing massive Java related functions in some long term running connections. |
| 802476 | SAP ASE may return a wrong result set if a proxy table is used in a derived table and is involved in an aggregate query. See KBA 2371951. |
| 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. |
| 803189 | 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 while transaction rollback containing an open cursor on an Allpages Locked Table (APL) with a clustered index and one or more nonclustered indexes, if DML within that transaction had a cursor pointing to a row, which is not the last row of the table. |
| 803225 | KBA 2385764. The PRINT statement displays BIGDATETIME values with millisecond granularity while the documentation specifies that BIGDATETIME has a display format that includes full microsecond precision. |
| 803241 | The option of 'ansinull' may be changed in a stored procedure when this stored procedure is triggered to recompile. |
| 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. |
| 803592 | In rare circumstances, the number of free log pages may sometimes be inaccurately reported when SP_SPACEUSED is run if allocated but stranded log pages exist in the database. |
| 803834 | The message, "current process infected with 11 (SIGSEGV)" in the module 'des_checkpoint' together with a stack trace which includes the modules 'dpdb_main' and 'checkpoint', may be reported in the SAP ASE error log when DUMP DATABASE is run resulting in SAP ASE shutting down implicitly because of the spinlock 'Dbtable- > dbt_defpipebufgpspin' being held. See KBA 2439610. |
| 803864 | A 511 error, "Attempt to update or insert row failed because resultant row of size < > bytes is larger than the maximum size ( < > bytes) allowed for this table. Command has been aborted." may be reported when running UPDATE on a compressed table. See KBA 2398449. |
| 803866 | A 7718 error, "The 'CREATE ENCRYPTION KEY' command is not allowed within a multi-statement" and the 2946 error, "Failed to create service key syb_xpskey", may be reported when executing xp_cmdshell (or any extended stored procedure) within a transaction for the first time. Subsequent executions do raise the errors. |
| 803881 | DESC option doesn't work on all platforms in subquery when the ORDER BY item isn't in SELECT list. |
| 803955 | KBA 2545318. Under rare circumstances, flushing log pages could try to flush non-log buffers causing the server to run into SIGSEGV in bufawrite()on the stack under cm_writelogdes_upto_sequence() or other errors. |
| 804030 | Following an error raised during the invocation of nested TUDFs (Table User-Defined Functions), the TUDFs involved will be marked as busy, and subsequent attempts to drop them may fail with a 3702, "Cannot drop or replace the < object_name > because it is currently in use". The message 'current process infected with 11 (SIGSEGV)' together with a stack trace containing the module 'tabvar_release' may also been seen in some cases in the SAP ASE error log. See KBA 2505576. |
| 804063 | The message, "Current process infected with signal 11" together with a stack trace that includes the modules querytuning_ins_sysoptions() and ins_sysoptions(), may be reported in the SAP ASE error log when executing a query that joins sysoptions, monProcessActivity and sysprocesses. |
| 804347 | KBA 2553567. In rare circumstances, when semantic partitioning is enabled, a stack trace in the function VbmManager::_VbmPutBm() may be observed if select query has join of list partitioned tables with equality predicate. |
| 804522 | A query that compares a CHAR with the result of DATEADD() returns different results when statement cache is active. See KBA 2409707. |
| 804888 | Only relevant for Business Suite extensions of SAP ASE: Error 279 "Object not found" while using base table is created with compression option or database is enabled with compression on. |
| 804893 | A query that is using TUDF and outer joins may sometimes return incorrect results because the outer join is incorrectly changed to a regular join. |
| 804900 | Transaction dumps created with the configuration option 'enable delta dump tran' on could result in inconsistent results if loaded onto an archive database. |
| 805018 | sp_configure raises the 5861 error, "The current 'max memory' value < max_memory_value > , is not sufficient to change the parameter 'number of user connections' to '32728'. 'max memory' should be greater than 'total logical memory' < wrong_memory_value > required for the configuration.", with an invalid value for total logical memory when configuring for 32729 or more user connections. See KBA 2417198. |
| 805133 | On Linux platform, under rare circumstances a connection to SAP ASE may hang after the client issues a cancel. |
| 805134 | Only relevant for Business Suite extensions of SAP ASE: Error 279 "Object not found" while using user created view if base table is created with compression option or database is enabled with compression on. |
| 805217 | KBA 2424530. The warning message, "Warning: The following user tables have duplicate rows in sysstatistics. Please drop and recreate statistics on these objects", may be reported in the SAP ASE error log when running preupgrade with a roundrobin partitioned table in the database. |
| 805251 | A 156 error, "Incorrect syntax near the keyword 'ORDER'", maybe reported in the SAP ASE error log when an ORDER BY clause is used with FOR XML in subquery. See KBA 2421236. |
| 805280 | For SAP ASE running in threaded kernel mode, a task (spid) may get stuck in kctCheckAsync(), i.e. DBCC STACKTRACE( < spid > ) shows function kctCheckAsync. This spid can be killed using 'kill < spid > ' if traceflag 7866 is enabled, or if the time (in minutes) indicated by the SAP ASE configuration parameter 'async poll timeout' period has elapsed, then the task automatically returns from kctCheckAsync() function, closing the remote connection. |
| 805381 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace that includes the modules PopIndScan::popGenCgp(), CgpGlobal::CgpGenerate(), s_compile() and sequencer() may be reported in the SAP ASE error log when executing statements that include DISTINCT with LOB columns. |
| 805430 | SAP ASE does not raise error 102 when invalid parameter names appear in DENY statement. |
| 805527 | The monDataCache MDA table might report incorrect values in PhysicalReads, APFReads and PhysicalWrites columns that are much less than the corresponding values from the monCachePool MDA table for a data cache with multiple partitions. |
| 805601 | The message, "PCI(T1): WARNING: FindPublicMethodFlags; is re-throwing Exception", may be reported in the SAP ASE error log when executing massive Java related functions through JDBC for several hours. See KBA 2425822. |
| 805624 | ALTER DATABASE fails silently when passed an expansion size that is smaller than the minimum for the server's page size. See KBA 2429256. |
| 805713 | sp_object_stats raises error 208 about being unable to find table syslkstats in a multiple tempdb when the user executing it is bound to a tempdb other than the system tempdb (dbid 2). |
| 805792 | A 140059 error, "The current row ID < > does not match the new row ID < > for update in logical page < > for DOL table ID < > , partition ID < > , index ID < > and update mode < > in database < > . This is an internal error" may be reported in the SAP ASE error log together with a stack trace which includes the modules 'writetext' and 'txtimg_set_txtpinfo' when running WRITETEXT while replication is enabled and concurrent DMLs are executed. |
| 805802 | SAP XP Server may generate core file when connection establishment between SAP ASE and SAP XP Server fails. |
| 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. |
| 806094 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'tdsrecv_params' together with a stack trace which includes the modules 'tdsrecv_rpc' and 'execrpc' may be reported in the SAP ASE error log when running an RPC, either when an error has caused the current command abort, or the end-user has interrupted the RPC execution, or the connection was lost. See KBA 2479094 |
| 806181 | Error 169 regarding duplicate ORDER BY clauses may be raised incorrectly when clauses are actually unique on servers configured for the UTF8 character set. See KBA 2439551. |
| 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 |
| 806327 | The message, "Current process infected with 11" in the module 's__prep_tablefunc' together with a stack trace which includes the modules 's_normquery' and 's_normalize' may be reported in the SAP ASE error log if a Table UDF is used in a nested subquery. See KBA 2546009. |
| 806377 | Isql maybe crashed or An 632 error "Attempt to move memory with an incorrect length of %d. Maximum allowed length is %d." raised during exercising query_text under traceflag 16939 against the spid associated with the java program with many dynamic parameters. |
| 806477 | Query with MERGE statement may result in spurious errors about incorrect conversions. |
| 806687 | In rare circumstances the message, "Current process infected with 11", together with a stack trace that includes the modules dol_get_delrows_indeallpg() and undo_dol_xalloc_nolink() may be reported in the SAP ASE error log when recovery is undoing a CREATE INDEX with computed columns that was not finished at run-time. |
| 806690 | A 2749 message, "Number of argument position specifiers in RAISERROR command is greater than the number of arguments passed", may be reported when executing sp_sysmon with a valid section name such as sp_sysmon "00:01:01", "housekeeper". See KBA 2447113. |
| 806700 | In rare circumstances, sp_monitorconfig may return '0' value for the 'Max_Used' column for configuration parameters which internally uses memory from object pool. See KBA 2515680. |
| 806734 | In rare circumstances, a 257 error, "Implicit conversion from datatype ' < data type > ' to ' < data type > ' is not allowed. Use the CONVERT function to run this query.", may be reported when inserting a row into a table variable with an identity column. |
| 806912 | SAP Sybmigrate reports a JDBC exception stack trace "com.sybase.jdbc4.jdbc.SybSQLException: Invalid role string '' entered" and sysloginroles may not be correctly copied from the source to target server. |
| 806917 | In Accelerator for SAP ASE, cursor pushdown does not support cursor status statement @@fetch_status. |
| 806965 | SAP ASE will intermittently fail to bring one or more engines online during boot while allocating memory for the engine. See KBA 2447283 |
| 807015 | Uniqueness bit for unique index in rootkey info may be lost after online REORG REBUILD or online partition level utilities such as split/move partition using ALTER TABLE. |
| 807059 | The REORG DEFRAG command is not honouring 'enforce dump tran sequence' when 'full logging for reorg' is disabled mistakenly, causing subsequent DUMP TRAN executions to abort with a 4207 error, "Dump transaction is not allowed because a non-logged operation was performed on the database..." unexpectedly. See KBA 2456447. |
| 807128 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'altdb__report_shrinklog_info' together with a stack trace which includes the modules 'altdb__do_shrinkdb' and 'altdb_shrink' may be reported in the SAP ASE error log when shrink database and shrink log command are run concurrently. |
| 807134 | An Arithmetic Overflow error can be seen when using "sp_dbextend 'device', devicename, 'growby', 'maxsize' " with invalid values for 'growby' and 'maxsize'. |
| 807242 | In rare cases, the number of log pages returned by the built-in LCT_ADMIN("num_logpages", < dbid > ) may be incorrect. |
| 807245 | Missing parent information of some functions/labels in stack output. |
| 807324 | When a spid executing sp_dump_history gets abnormally terminated e.g. due to a timeslice error, then it does not release the resource (semaphore) thus disallowing other spids to execute SP_DUMP_HISTORY. Only way to cleanup then is to recycle the SAP ASE. |
| 807353 | During SAP ASE configuration for failover on Veritas Cluster Server, SAP ASE gets shutdown. |
| 807383 | On Unix platforms, in the Job Scheduler Agent (jsagent) process, when multiple threads hits a fatal signal like SIGSEGV simultaneously, then the core file is not generated. |
| 807410 | In case of streaming replication when the synchronous mode is enabled, a low value for the configuration parameter 'max commit wait time' can cause a task to wait on commit forever. |
| 807433 | In some circumstances, the value of monNetworkIO.BytesSent might not increase on IBM AIX platform even though there are some network I/O activities. |
| 807451 | If a database with AT_SHUTDOWN durability has active transactions that, for some reason, cannot be terminated when the server is shutdown politely with a maximum wait time using the clause WITH WAIT="xx:xx:xx", the message "The database < > with durability 'AT_SHUTDOWN' could not be shut down properly and will not be recovered when Adaptive Server is re-started." should be printed in the errorlog, but it was not. |
| 807471 | A 12546 error, "During undo the timestamp to be assigned to a page is less than the current page timestamp." followed by a 3478 error, "During undo the page timestamp value is less than new timestamp from log." may be reported in the SAP ASE error log during the recovery of a database when alter database un-partition was executed before SAP ASE is shutdown. |
| 807676 | The replication of a DML command on a table having a function-based index fails and a 11738 error, "Name 'sybfi < value > ' is reserved for internal use by Adaptive Server." is reported in the error log of Replication Server. |
| 807724 | sp_showcontrolinfo shows incorrect value in scope column for a "AP" binding. This only happened when the previous row is a "LG" binding and current "AP" row has the scope with NULL value. See KBA 2465543. |
| 807741 | Executing ALTER TABLE FOR PROXY_UPDATE against a proxy table mapped to SAP Anywhere or SAP IQ may fail with incorrect syntax error. |
| 807765 | A 5072 error, "ALTER DATABASE cannot remove the first 256 pages of a database", may be reported when executing ALTER DATABASE < dbname > OFF < device > . |
| 807766 | When encrypted column is enabled for a table which has default value for some columns, then in sp_help 'tablename' output,'Encrypted' property for these columns show 'NULL' value instead of 0, if the data in these columns are not encrypted. |
| 807819 | When the master device is upgraded from a pre-15.0.2 version of SAP ASE, the execution of sp_passwordpolicy 'list', 'allow password downgrade' should report the message 'Password downgrade is allowed' instead of 'New master database'. |
| 807849 | SAP ASE may incur a segmentation fault in ksnetctlrAddSockEvent() when new client connections are made during shutdown with nowait. |
| 807870 | KBA 2469521. 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. |
| 807905 | DBCC NETMEMUSAGE shows a very large and incorrect value for the used memory field. |
| 807929 | A 207 error, "Invalid column name 'sysstat5'", may be reported when using the migration tool to migrate from a lower version of SAP ASE (lower than 16.0 SP02) to higher version of SAP ASE, or when creating a proxy table from a higher version of SAP ASE to a lower version. |
| 807940 | A signal 11 error may be raised when using the "Stack" command in Sybmon during unwinding of the stack trace on some platforms like ibmaix64 platform. |
| 807966 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'mda_populate_monSpinlockActivity' together with a stacktrace which includes the modules 'mda_exec' and 'VTABRemoteAccess::startScan' may be reported in the SAP ASE error log when a SELECT from monSpinlockActivity is run. See KBA 2545393. |
| 807992 | The message, "Timeslice -1501, current process infected" in the module 'rl_log_writev' together with a stack trace may be reported in the SAP ASE error log if a workload capture started after server reboot. |
| 808040 | KBA 2573343. In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'pci_killslot' together with a stack trace may be reported in the SAP ASE error log during a forced shutdown (shutdown with nowait). |
| 808080 | KBA 2472350 - Changes to parameters 'number of network tasks' and 'number of disk tasks' are not written to configuration file |
| 808195 | SELECT INTO temp table may result in the error, "inserted value too large for column", to be reported at HANA if the source table was created using traceflag 11246 that allows mapping varchar column to HANA as nvarchar. |
| 808205 | Executing a preupgrade from an SAP ASE 12.* server to any SAP ASE version above 15.0 may result in a 207 error, "Invalid column name < column_name > ", for columns 'partitiontype' and 'conditionid' that do not exist in the SAP ASE 12.* version. |
| 808225 | A 2901 error, "Exception stack limit exceeded", followed by a stack trace that includes the modules 'getuidfromname' and 'udr_crtrole', may be reported in the SAP ASE error log when executing CREATE ROLE on AIX platform with a large number of databases. See KBA 2479506. |
| 808280 | The partial rollback of a transaction may be unexpectedly discarded by replication, resulting in a data mismatch between the primary and replicate databases. |
| 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. |
| 808326 | Descending sorting doesn't work correctly in a query containing both an ORDER BY clause and a LIMIT clause. |
| 808357 | LogicalReads/PhysicalReads in the monProcessActivity, monSysStatement and monProcessStatement MDA tables will not be updated correctly when "enable compatibility mode" is set as 1. See KBA 2478206. |
| 808425 | KBA 2580447. The error, "Sybmon encountered signal 11 at address < addr > ", will be raised when "hanginfo" is executed in sybmon that is attaching to an SAP ASE server. The functions sm_os_ctrl_suspend_thread and khashtable appear in the stack. Some structure fields might also be missing from sybmon "ptype" command output. |
| 808440 | Downgrading a database to a pre-16.0 SP01 version may fail with message, "Error: Database db contains suspect defer recovery indexes that must be dropped via sp_deferred_index_recovery drop option before downgrade." |
| 808489 | A segmentation violation followed by a stack trace that includes the module 'am_count_bits_in_dmap' may be reported in the SAP ASE error log when loading a database dump on a database that is marked as suspect if the database is bigger than 64G in a 2K server, 128G in a 4K server, 256G in a 8K server and 512G in a 16K server. See KBA 2490688. |
| 808518 | On HP platform, under heavy load, a spid may hit timeslice error when returning query results to the client. |
| 808535 | A 9417 error, "RepAgent( < dbid > ): The CI-resource 'CMD Package' is exhausted, please use 'sp_config_rep_agent' to increase the configuration value of 'buffer pool size'. Waiting for a free package may result in performance degradation." may be reported in the SAP ASE error log when using streaming replication while excessive flushing of partially filled packages takes place. |
| 808553 | RC4 and 3DES are removed from the SSL default cipher suites list. |
| 808631 | The error "ERROR !!! Skipped patching dbid. Page in run < > . Page in buffer < > ." will be mistakenly printed in the SAP ASE backupserver error log for every allocation page when doing cross platform load. |
| 808634 | sp_sjobcontrol stored procedure may fail with error 553 when called to enable/disable caller's scheduled jobs, using the syntax "exec sp_sjobcontrol @name='jname= < jobname > ', @option='enable|disable'". |
| 808636 | A 716 error, "Unable to allocate memory of size < nnnnn > bytes from the 'compression info' pool", followed by a 2628 error, "In database < dbname > , page < page_num > is linked forward to page < page_num1 > , but that page is linked backward to page < page_num2 > . Please report this internal error to SAP Technical Support", may be reported in the SAP ASE error log when inserting into a table with compressed indexes. See KBA 2483958. |
| 808637 | KBA 2460661. Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'js__sequencer_load' together with a stack trace that includes the module 'js__sequencer_boot', may be reported when installjsdb is modified to include spaces instead of tab and the Job Scheduler fails to start. |
| 808666 | The monDeviceSpaceUsage table might return incorrect data when it is queried concurrently from multiple sessions. In rare cases, the Global Fragment Pool might be corrupted. Customer may see signal 11 error in kbfalloc() or kbffree(). |
| 808729 | SAP ASE does not handle numeric conversion results consistently during RPC calls when arithabort is OFF. |
| 808761 | ALLOW and DENY are not updated as SAP ASE reserved keywords leading to a 156 error, "Incorrect syntax near the keyword 'allow'." or "Incorrect syntax near the keyword 'deny'." being reported when the reserved keyword 'allow' or 'deny' is used as an identifier in any DDL statement. See KBA 2483160. |
| 808773 | SAP ASE server is further improved following the fix for CR 787670 to check each LOB first text page and clear uninitialized TIPSA information when the server trace flag 7167 is enabled to prevent error 632 from being mistakenly reported when compressed LOB data is in use. |
| 808883 | A 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database..." may be reported when there is a long running transaction that causes DUMP TRANSACTION to not truncate any log pages and DUMP TRANSACTION is run a high number of times. |
| 808888 | The fix for a long running internal 'sort_local' transaction during cursor processing causing tempdb log full scenario is turned on by default (previously TF 11821 was needed to turn this fix ON), and now TF 11820 can be used to turn the fix OFF. |
| 808936 | The message, "Incorrect column type in the offset table of row < > . This row is on page < > , partition ID < > , and belongs to object 'syscomments' (ID 6) in database ' < > ' (ID < > )." may be mistakenly reported when running DBCC CHECKTABLE(syscomments). |
| 808961 | A 952 error, "Database < dbname > cannot be opened because the system index descriptor for table ID 4 cannot be installed.", may be reported when booting a server with 4K page size downgraded from 16.0 SP03. |
| 809026 | When SQL Statement Replication is enabled the DSI connection may go down with error 5150, "Function 'rs_get_textptr' for table ' < table_name > ' returned multiple rows." while a SELECT INTO statement that involves LOB columns is replicated. |
| 809043 | A 16878 error, "The limit specified in a LIMIT clause may not be negative", may be reported during the execution of a dynamic prepared statement with LIMIT clause and table-valued user defined function. |
| 809093 | The error message "Logical page < page_num > is not in the given database map" will be printed in the SAP Backupserver error log followed by a stack trace in the SAP ASE error log including the module 'dmpld_send_dbdam_runlist' at DUMP DATABASE time if the database option 'allow incremental dumps' is enabled and SAP ASE failed to allocate the required number of pages to store the bitmap of changed pages. |
| 809098 | Cleanup is failing during abort transaction due to no space in log. |
| 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. |
| 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 . |
| 809179 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dbt_unkeep' together with a stack trace which includes the module 'close_range' may be reported in the SAP ASE error log when a query uses a worktable. See KBA 2545441. |
| 809188 | The error, "Invalid RPC sequence at RPC as_cmd. 5.7.2.7: RPC ('as_cmd') execution failed.", may be raised when executing a remote DUMP or LOAD at a server using a name or address-port that is redirected to the actual remote Backup Server address. |
| 809210 | A 11060 error, "This statement has exceeded the maximum number of recompilations (10). This indicates an internal error." may be reported when executing a SELECT query in read uncommitted mode which results in a nested execution of User Defined Functions (UDF) that can return a table variable. |
| 809244 | After the fix of CR 777172, cache size is stored in terms of 2K. Views have been changed accordingly to reflect this behavior. Cache sizes up to 2TB will show actual size in the views. |
| 809265 | After running "alter database < database_name > on/off < database_device > size = '0M'", command fails with error Msg 5015 - "CREATE or ALTER DATABASE failed. The size specified must be < n > megabyte(s) or greater". |
| 809308 | A 941 error, "Illegal database context operation", will be reported when LOAD DATABASE of master database is run. |
| 809330 | A 9502 error, "Data exception - string data right truncated Command has been aborted.", or truncated values for 'Name' column, may be reported if a configuration option name exceeds 25 characters when SP_MONITORCONFIG with the 'all' option is executed and the set option string_rtruncation is enabled. |
| 809365 | Buffer level spinlock statistics (like spins, grabs, waits) are not visible in MDA, sysmon or other monitoring tools. |
| 809371 | A dynamic prepared statement with LIMIT clause may return wrong result with limit value passed as a variable and executed multiple times for different values. |
| 809381 | In rare circumstances when REORG REBUILD is terminated using Ctrl-C, sp_help on the table undergoing REORG REBUILD returns error 17461, incorrectly indicating that object does not exist in the database. |
| 809395 | In rare circumstances, the message, "Current process infected with 11" in the module 's_execclearvar' together with a stack trace which includes the module 'tdsrecv__process_batchparam' may be reported in the SAP ASE error log during the execution of a DML on a table that has a DECIMAL column with high precision defined such as DECIMAL(38,1). See KBA 2412709. |
| 809422 | A 590 error, "Dynamic SQL error - Prepared statement < ssql_id > does not exist", followed by a 709 error, "Memory request for < value > bytes exceeds the size of single page of < pagesize > bytes" or a 724 error, "Internal Error: Function 'memalloc' was passed an illegal size value < value > ", may be reported in the SAP ASE error log when executing a prepared statement with Derived Table UDF and the statement cache is enabled. |
| 809442 | In rare circumstances, a session may hang in the module 'prepprev' after a rollback due to error 2601 "Attempt to insert duplicate key row in object ' < table_name > ' with unique index ' < index_name > ' ...". See KBA 2503863. |
| 809498 | A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ) and not to database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ) or a 692 error, "Uninitialized logical page < page_num > was read while accessing database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ). Please contact SAP Technical Support." may be reported when a user is inserting a data from a source table to target table using SELECT INTO command while another user is fetching data from target table at isolation level READ UNCOMMITTED. |
| 809524 | When an IN subquery contains a reference to a table-valued UDF and there is no correlating column, the subquery may be erroneously flattened (converted into a join) resulting in a segmentation violation session termination. |
| 809638 | Sometimes, an SAP ASE spid hangs in the module 'prepprev' after rollback due to error 2601 (duplicate key error). |
| 809672 | In an SAP ASE HADR environment, under situations when the SAP ASE server is listening on multiple ports, then an HADR aware client may fail to receive the HADR map of the configuration from the server. |
| 809681 | placeholder CR for SAP Accelerator for ASE 2.0 Revision 020 (SP02) |
| 809700 | Queries involving large number of SUM aggregates works slowly on SAP ASE in an Business Warehouse type of environment. |
| 809748 | SSL handshake fails with message "SSL or Crypto Error Message: 'The SSL handshake failed. Root error: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol'" when an SSL connection reuses a socket that was used by a terminated site handler. |
| 809751 | A 18004 message, "Audit option 'sproc' is ambiguous", may be reported when executing sp_displayaudit 'global', 'sproc' after upgrading to a SAP ASE 16.0 version from a version prior to 16.0 |
| 809773 | Occasionally, a 712 message, "There is insufficient heap memory to allocate < nn > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system", may be raised for insufficient heap memory when multiple XML sessions (such as more than 15) run XML queries at the same time. See KBA 2515782. |
| 809799 | A 515 error, "Attempt to insert NULL value into column < column_name > , table < table_name > ; column does not allow nulls. Update fails.", may be reported when executing sp_cacheconfig after an IMDB cache which is bound to a device or database is deleted. |
| 809851 | Text back link will not be maintained for tables with TEXT/IMAGE/UNITEXT columns when they have replication enabled, thus less log records will be generated by DML operations. |
| 809999 | Executing sp_configure with no parameter may result in the error, "No matching configuration options. Here is a listing of groups:" while printing out group information. |
| 810067 | Binary data may get truncated in SELECT UNION ALL queries executed against proxy tables. |
| 810115 | Enhancement in HADR to allow user to configure application interface using 'sp_hadr_admin' stored procedure. The HADR map and client redirection will be based on the application interface info (if configured). |
| 810132 | The 814 error, "Keep count of buffer ' < buffer addr > ' in cache ' < cache name > ' holding logical page ' < pageno > ' in database ' < database name' has become negative" followed by a stack trace that includes the module 'dam__destroy' may be displayed when creating a database, if the option 'allow incremental dumps' is enabled in the model database. |
| 810170 | A 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database", may be reported after the command "dbcc usedextents()" is run that corrected free space count indicated by the message "Those for data or data-and-log were corrected in memory" |
| 810188 | A 12323 error, "Internal error occured during rebuild of index id < index id > of table < object id > (id = < id > ) in database < database id > while processing page < page id > . Run dbcc checktable to see if the index is consistent." may occur when executing REORG REBUILD on a Latch Free Btree index. |
| 810229 | The prefix of previous index page is propagated to the new allocated index page unnecessarily during split under Midpoint split. This is not needed and is inefficient. |
| 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. |
| 810376 | Error 9557 may result when the "disallow simple passwords" feature is on and passwords generated by the password_random() function happen to include the name of the login the password is assigned to. An additional optional parameter is added to password_random() so it can be passed the login name to avoid including in the resulting password string. See KBA 2525248. |
| 810398 | In certain cases, Abstract plan may be incorrectly stripped off when dynamic SQL uses polymorphic built-in functions are used. |
| 810405 | With replication on, error message 632, "Attempt to move memory with an incorrect length of < wrong_val > . Maximum allowed length is 16384.", may be raised while trying to decrypt any encrypted column of table when set encryption password was set for that column and not for encryption key with which column is encrypted. |
| 810459 | When sorting is required for an ORDER BY clause, and arithmetic errors occur, transaction aborts may occur, when only statement aborts are expected under sp_configure 'allow statement rollback'. Regular TUDFs mask this erroneous behavior, while inlining them (making them to behave like views) exposes it. |
| 810462 | An invalid TDS error might be observed while running builtin index_col on global temporary table created with index compression set to on. |
| 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. |
| 810488 | The message, "Command has been aborted", may be reported when closing or deallocating an insensitive cursor. See KBA 2528002. |
| 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 DOL table with isolation level 0. |
| 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. |
| 810717 | Extending maximum cache size upto 4TB on all platforms. |
| 810743 | SAP ASE running on Windows will see a timeslice error if a task hits a divide by zero error |
| 810947 | In a single engine SAP ASE setup, two sessions may wait for each other while flushing log records from their Private Log Cache to the transaction log, when they run at a different priority. |
| 810948 | Apache Jakarta Common CLI is upgraded to 1.4 and Apache Jakarta Common Logging is upgraded to 1.2. |
| 811046 | A process querying the monCachedProcedures MDA table might crash the server with the message like "timeslice -1001, current process infected" with the module 'mda_populate_monCachedProcedures' on the stack. Please see KBA 2541894 for more details. |
| 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. See KBA 254302. 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. |
| 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. |
| 811150 | The Tivoli Storage Manager option for mountWait '-M' was incorrectly placed as part of the stripe name in the dump history file of SAP ASE. |
| 811160 | Upgrade Java API for XML-Based RPC (JAX-RPC, new version is 1.1.3), SOAP with Attachments API for Java (SAAJ, new version is 1.3), Web Services Description Language for Java (wsdl4j, new version is 1.6.3) and JavaMail (new version is 1.6.0) to the latest versions. |
| 811209 | When changing the replication status of a database having Global Temporary Tables to 'none', the execution of the command SP_REPTOSTANDBY < DBNAME > , 'NONE' fails with a 267 error, "Object '##xxx' cannot be found.", followed by a 18413 error, "Due to a system failure, the replication status for ' < dbname > ' has not been changed.". |
| 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. |
| 811348 | On Windows platform, the error, "Do you want to allow the following program from an unknown publisher to make changes to this computer?", may be reported when executing an SAP ASE binary despite the binary being appropriately signed by SAP. |
| 811438 | The message, "Current process infected with signal 6 (SIGABRT/SIGIOT)" followed by a stack trace that includes the modules 'cfree', 'pcifree' and 'OdbcRemoteAccess::CleanUp', may be reported in the SAP ASE error log when a NUMERIC column in a proxy table mapped to HANA is queried. See KBA 2553679. |
| 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. |
| 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. |
| 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. |
| 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. |
| 811774 | On IBM AIX platform with SSL enabled, ODBC Driver under rare circumstances may see connection terminated with error 30046. |
| 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. |
| 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. |
| 811958 | RMA directory changed from 15_5 to 16_0 |
| 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. |
| 812006 | Under rare circumstances, SSL connections to an SAP ASE running in process kernel mode may hang during network I/O. |
| 812227 | For ASE running on Linux, Solaris & HP, under rare circumstances an SSL connection may unexpectedly terminate with message "SSL or Crypto Error Info: psn -1, vsn -1, sockp (nil) error id 12, severity -2, provider id 2." in the ASE error log. |
| 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. |
| 812304 | Spurious errors may happen when trying to create global temporary table. |
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 SP02 PL07, ASE SP02 PL07, SP02 PL07, 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)