/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 PL06. 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 |
|---|---|
| 356151 | Feature request to enable UNMOUNT DATABASE and QUIESCE DATABASE with external dump commands when server is configured for disk mirroring. |
| 635454 | The file size generated when the set option 'tracefile' is enabled is limited to 2GB. KBA 2089573. |
| 677266 | A 6908 error, "During redo the page timestamp value is less than old timestamp from log ..." may be raised in the SAP ASE error log while loading a transaction dump having two transactions TEXTSTOR and TEXTFREE on sysattributes system table that are used by Web Services in the source database. See KBA 2294696 |
| 733723 | The message "compressed log" may be reported mistakenly when sp_helpdb is executed on a database where an alter database with the log off option was first executed. |
| 773524 | Under rare circumstances, when a transaction rollback fails, the transaction remains open erroneously and allows other concurrent transactions to progress. Eventually this failed transaction becomes the oldest open transaction and prevents the transaction log truncation thus making the database unusable when the log last chance threshold is reached. Additionally if SAP ASE is restarted, the database recovery fails and the database is marked suspect. The new database option "allow db suspect on rollback error" if enabled allows a forceful shutdown of the database and marks the database suspect if a non-recoverable error is hit during a transaction rollback. This provides the ability to the end-user to execute a last DUMP TRAN allowing to archive all the transactions up to the point the rollback failed. |
| 776004 | A 712 error, "There is insufficient heap memory to allocate 92928 bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.” may be reported together with a stack trace which includes the modules 'ptnc_replace_ptncond’ and 'alt__add_partition’ in the SAP ASE error log when adding multiple partitions into a table while using separate statements in a single batch. See KBA 2107233. |
| 777172 | sp_cacheconfig fails with an Arithmetic overflow error when the cache size exceeds 2TB. |
| 778761 | The message "Current process infected with 11" in the module ‘buf_consolidate_lfb_find_newbuf’ together with a stack trace which includes the modules ‘bt__insert_into_leaf’ and ‘ins_insert’, may be reported in the SAP ASE error log when a DML is executed into an in-memory database on a DOL table that has an index which was created with the option ‘latch_free_index’ enabled. |
| 788517 | A 3328 error, "Redo of 'CREATE INDEX' in transaction ID (0,0) for table name < > , object ID < > did not find 'syscolumns' system catalog log record. Recovery of database < > cannot continue." followed by 3329 error, "Redo of 'CREATE INDEX' for table < > , object ID < > did not build compression information. Recovery of database < > cannot continue." followed by 4314 error, "Cannot find table < > to recreate index < > ." may be reported during LOAD TRANSACTION in the SAP ASE error log while an index is logically rebuild. See KBA 2216220. |
| 789277 | The error message, "CT-LIBRARY error: ct_results(): protocol specific layer: external error: There is a TDS protocol error", is reported back to the client when SAP ASE executes a remote procedure that exists in SAP IQ and the procedure has an output parameter that is either decimal, numeric or datetime. See KBA 2213838 |
| 789474 | Usage of large buffer pool for a database which has NV cache bound to it can lead to disk corruption. |
| 789748 | A deadlock may be reported on ‘sysobjects’ system table when temporary tables are created by a concurrent execution of SELECT-INTO commands during ZDO SAP upgrade. |
| 789993 | SAP ASE running on Windows with encryption enabled, under rare situation may experience client disconnection with the following message in the SAP ASE log - "An I/O error occurred during the underlying SSL operation. Check your I/O callback handler return values and error codes.". |
| 792092 | SAP ASE on Linux hits 823 errors when the underlying storage disk is configured for 4K sector size. See KBA 2243658. |
| 793969 | Sybmon command "keptbuf < spid > " will report signal 11 error on a memory dump without including page cache. |
| 794933 | MSA Replication using SQLDML causes DSI thread down due error 11055 |
| 795395 | An unexpected message, "Usage: sp_logging_rate {'full'|'sum', '[day,]hh:mm:ss'}[, @interval='hh:mm:ss'][, @clear_option='y'|" may be reported in the 'Object_status' column of the output of sp_help command. |
| 795533 | In rare circumstances on a heavily-loaded multi-engine system, a timeslice error in the module 'ubo_slotscan_getnext' together with a stack trace which includes the modules 'mda_populate_monCachedProcedures' and 'VTABRemoteAccess::getNext' may be reported in the SAP ASE error log when the MDA table monCachedProcedures is queried. See KBA 2393400. |
| 795815 | The message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace that includes the module GttTable::getStarQueryGtIdOrder() and sequencer(), may be reported in the SAP ASE error log when a query is executed with a derived table (using UNION) joined to a Fact table using the fact_table hint. See KBA 2283395. |
| 796256 | The reporting of SAP ASE RepAgent configuration option changes in the SAP ASE error log is now enabled. |
| 797712 | In rare circumstances, the SAP ASE dataserver may hang in the function LeHashContext::HB1stOpen() as a result of a Ctrl-C on a parallel HashJoin query. |
| 798255 | Error 2762 "The 'DROP TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database." is reported when signal druing post commit shrink. |
| 800370 | On AIX, Client application in rare situation may hang after sending a new command after a cancel. |
| 800670 | In a Multiple Paths Replication environment configured for the 'filter' distribution model, a DDL command on a table having a bound filter is always sent to the path on which the filter is bound but also, by default, to the default path unless the new Rep Agent configuration parameter 'ignore implicit filter for ddl' is set to 'true'. See KBA 2341608. |
| 800880 | The message, "Current process infected with 11" in the module 'pg_clean_oam_entries’ together with a stack trace which includes the modules 'reorg__ptn_fr’ and 'reorg_main’, may be reported in the SAP ASE error log when the command REORG COMPACT is executed. See KBA 2351844. |
| 800932 | The error, "java.lang.SecurityException: Unsupported Thread method", may be reported in the SAP ASE error log with SAP JRE Version 8 or greater, during the execution of a UDF that makes use of a private network stack even when the option -Dsybase.allow.native.lib is enabled. |
| 801147 | In rare circumstances a user process may hung on PLC Sleep with recursive calls to module 'amc_alloc_firstpages' when running DUMP TRAN WITH TRUNCATE_ONLY on a database that has the option "trunc log on chkpt" enabled. |
| 801406 | default rma tds port change to 4909 |
| 801414 | The ULC Flushes counts under the 'Transaction Management' section of sp_sysmon report may be incorrect and may not add up to 100%. |
| 801598 | In rare circumstances, an 806 error, "Could not find virtual page for logical page < > in database < > ." may be reported in the SAP ASE error log after performing a LOAD DATABASE whereby the target database diskmap does not match that of the source database in the dump. Alternatively in KBA 2411446, a 4343 error, "An error occured when converting the row offset table in the page < > of object ID < > . Either the number of rows, < > , or the free offset in the page, < > , is incorrect. The conversion will be skipped. Please, contact SAP product support." may be reported when performing a cross-platform LOAD DATABASE. See KBA 2420672. |
| 801681 | In virtual host, SAP ASE might experience large number of page faults which could cause a task to timeslice. In this situation for a task which is about to timeslice, allow additional grace time. |
| 801865 | A 16382 error, "The configured maximum number of mutexes have already been created" may be reported in the SAP ASE Backup Server error log for some of the dumps prior to their failing, when there are more than 128 simultaneous dumps executed. |
| 801908 | In rare circumstances, when SAP ASE has Non-Volatile Caches some of user processes may hang after database dumps for potentially indefinite time. Stack of the hung processes shows ssd_prewrite() |
| 801912 | The message "Current process infected with 11 (SIGSEGV)" in the module 'mem__pageallocate_this_engine' together with a 718 error, "Memory allocation from process private memory is being performed by an incorrect process. Current Spid: ' < value > '. Owning Spid: ' < value > '. Memory: ' < value > '. This is an Adaptive Server internal error. Please contact SAP Tech Support." and a 707 error, "System error detected during attempt to free memory at address < value > . Please consult the ASE error log for more details." may be reported in the SAP ASE error log when a stored procedure involving temporary tables is executed. |
| 802115 | A 12726 error, "Suspect Granularity: Dump database of < dbname > failed because some of the data in this database is suspect" may be reported when DUMP DATABASE is executed and the recovery fault isolation mode was set to 'page' mode. |
| 802213 | The message, "Current process infected with 11", in the module 'ubffreef' together with a stack trace which includes the modules 'fdp_free_memory' and 'terminate_process' may be reported in the SAP Cluster Edition ASE error log when a session terminates resulting in SAP ASE shutting down implicitly. See KBA 2369414. |
| 802687 | High contention on the rdbt_spinlock spinlock may be observed. |
| 802695 | KBA 2375006 - In rare circumstances, doing multiple shrinks after one another may result error 806(Could not find virtual page for logical page < logical page number > in database < database id > ), which will lead to timeslice issue. |
| 802740 | A 873 error, “Process < spid > is requesting exclusive latch on buffer … while holding 4 latches. A process can hold only 4 latches at a time.” in the module ‘rec_undo_session’ together with a stack trace which includes the modules ‘le_runerr’ and ‘LeDeleteOp::_LeOpNext’ may be reported in the SAP ASE error log when attempting to delete rows for the system table syslogs. |
| 802768 | In rare circumstances a hang may occur in SAP ASE between two sessions whereby the first session hangs in the module ‘plc_flush’ waiting for a page to be written on disk by holding a lock on the second session Private Log Cache, while the second session is writing the same page on disk and is waiting to acquire the lock on its own Private Log Cache. |
| 802848 | The message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace that includes the modules s_mapcontrol() and s_compile(), may be reported in the SAP ASE error log when procedures involving IF statemens and ORDER BY clauses are executed with "enable metrics capture" and "enable literal autoparam" are turned on. See KBA 2379446. |
| 803288 | A 8203 error, "Expected to find the descriptor for object < value > in database < value > in DROP state." may be reported while executing 'dbcc purgesqlcache' after execution of SELECT queries which have built-in show_cached_plan_in_html in where clause. |
| 803373 | In some circumstances the message "current process infected with 11" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra__cilib_malloc_wrapper_with_ctx' and 'ra_mempool_alloc_internal' may be reported in the SAP ASE error log when the streaming replication mode is enabled and after a Replication Agent has been shut down. The Replication Agent shutdown may have damaged the ASE Replication Agent global fragment memory pool. |
| 803378 | NFR: Add DR admin user to secure store for BHADR. |
| 803413 | DBCC ORPHANTABLES may fail to drop orphaned temporary tables if the user is bound to a different tempdb than the one having DBCC ORPHANTABLES being executed. See KBA 2392219. |
| 803415 | An Arithmetic Overflow error can be seen when using sp_configure " < param_name > ", 0, " < value > {K|M|G}" instead of number of pages. |
| 803497 | A 7377 error, "SELECT INSERT cannot be specified with isolation level clause." may be reported when a select-insert command is executed because the OMNI layer may add to the query the clause "AT ISOLATION" mistakenly. |
| 803547 | The message, "Current process infected with 11", in the module ‘com__exctnume_copy’ together with a stack trace which includes the modules ‘mod_numeric’ and ‘LeRun’ may be reported in the SAP ASE error log when a query that involves modulus operations on numeric variables is re-executed. See KBA 2397851. |
| 803569 | In rare circumstances the message, "Current process infected with 11", in the module 'pg__truncateoam' together with a stack trace which includes the modules 'trunc_wktable' and 'pg_free_extents' may be reported in the SAP ASE error log if a SELECT is executed while auditing is enabled and LOAD DATABASE on a non-existing database was initially executed by the same session. |
| 803575 | DELETE from a table variable removes more rows than it should. See KBA 2408286. |
| 803584 | A 614 error, "Adaptive Server accessed a row that has an illegal length of < length > while in database ' < db name > '. Page pointer = < page address > , pageno = < page number > , status = < status > , ptnid = < partition id > , indexid = < index id > , level = < level > , pnextrno = < next rowno > . The minimum row length is < length > . The page size is < page size > ." may be reported in the SAP ASE error log during an UPDATE command execution on All Pages Lock table while a compressed non-clustered index is used to access the data. |
| 803606 | If the database is in the middle of a load sequence the space added by ALTER DATABASE is not accounted by the threshold manager and hence it is not available for new allocations in this database. |
| 803614 | The message, "Current process infected with 11", in the module 'bt__delrow’ together with a stack trace which includes the modules 'buf_consolidate_lfb_delta’ and 'alt__ind_set_latch_free’ may be reported in the SAP ASE error log when ALTER INDEX is executed to disable the option 'latch_free_index’. |
| 803627 | A 1795 error, "'ALTER TABLE' failed because the dataserver was unable to allocate space for deferred table ' < name > in database ' < name > ." may be reported when ALTER TABLE is executed on a table that was created with the option 'deferred_allocation' enabled. |
| 803634 | When replicating compressed LOB columns, Replication Server DSI may fail with ASE error 7153. |
| 803651 | Every time when granular permission is enabled or auditing is enabled and any Non-Volatile cache configuration command is executed using sp_nvcacheconfig or sp_nvbindcache then the message "current process infected with signal 11" in the module "prot_pcr_get_perms" will be reported in error log. Alternatively a message like "NV cache change failed on cache: < cachename > return code: 0." could be displayed to user |
| 803681 | The performance of INSERT statements might be slower while using Dynamic prepare for VARCHAR/TEXT type column. |
| 803716 | SAP ASE did not shutdown after issuing 'shutdown with wait' command as it continued to wait for the Job Scheduler to go down. |
| 803727 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module check__xfsexceptions() together with a stack trace which includes the modules check_xfsenabled() and dir_opentable() may be reported in the SAP ASE error log, when 'enable file access' is disabled after mapping a proxy table to an external directory and the proxy table is subsequently accessed. |
| 803730 | If next_identity() is called against a table in another database and encounters a permissions problem, error 10330 may report the wrong table and database names. |
| 803837 | Under rare circumstances SAP ASE may hang when a spid that is writing log records is kill with the force option. |
| 803858 | When using streaming replication and the acknowledgements from Replication Server are received before the associated disk I/O for the committing transaction could finish, it is possible that an SAP ASE user task will request a mode switch to asynchronous although this is not required. |
| 803870 | A 264 error, “Column name < col_name > appears more than once in the result column list.” may be reported when an INSERT command is run on a table that has a trigger on insert, after a reorg rebuild was executed and an alter table drop column with no datacopy has been issued before. |
| 803875 | Sybmon sample command showed single frame of stack and reported SymGetSymFromAddr64 error 126 on windows platform. |
| 803877 | When password expiration = 0 specified during role or login creation then SAP ASE does not check the expiration clause specified with the command. |
| 803900 | In rare situations, disconnected client can cause orphaned task in SAP ASE. |
| 803903 | In a HADR environment, connection to the standby SAP ASE is not redirected to the primary ASE when SSL is used. |
| 803924 | An assertion failure with a stack trace including the modules OptGlobal::GblAssignOptId(), TpopTabScan::TpopTabScan() and GtcChildOptBlock::_GtcExpandMatchTopPops() may be reported in the SAP ASE error log when using LIMIT clause in IN predicate whose first expression is not in the select list of the outside query. |
| 803935 | The monThread MDA table will report the same statistics metrics for all threads on the Linux platform. The thread utilization in sp_sysmon output is reported incorrectly. A typical symptom is the thread utilization for all threads are the same and might exceed 100%. |
| 803956 | In some rare circumstance, the message, "Current process infected with signal 11 (SIGSEGV)", together with stack trace that includes the modules mda_empty_opstack(), mda__freeze() and mda_config_bi() may be reported in the SAP ASE error log when a process runs sp_sysmon or sp_monitors command. |
| 804003 | The message "Current process infected with 11" in the module dcomp_getcpinfo_trigger() together with a stack trace which includes the modules decompress_column_by_colid(), LeCompressSubs() and exectrig() may be reported in the SAP ASE error log when a SELECT query on the inserted system table is executed inside a trigger. |
| 804107 | On IBM AIX platforms, an incorrect value may be returned for the role_name() built-in when the statement is executed against a SAP HANA backend server. |
| 804121 | A 9561 error, "An insert or update to table < tname > places column < cname > at offset < value1 > , ending at offset < value2 > . The maximum permitted ending offset for this column is < value3 > . This is a server internal error." may be reported during an INSERT command execution after a reorg rebuild is run on an APL table which has undergone first an alter table drop column with no datacopy followed by a clustered index creation or drop. |
| 804132 | Execution of sp_dump_history in chained mode is now allowed. |
| 804157 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log old timestamp= < > . Log record marker = ( < > , < > )." may be reported in the SAP ASE error log during boot time recovery after a non-polite SAP ASE shutdown while an REORG REBUILD command was running. Alternatively a 3478 error may be reported during recovery undo processing. See KBA 2404095. |
| 804163 | A 540 error, "Schema for database object < > has changed since compilation of this query. Please re-execute query." may be reported erroneously when a SELECT query is executed at transaction isolation level 0 whereby the schema change detection is due to a row count recompilation. |
| 804176 | The columns NumberOfMempoolAllocates and MempoolHighUsage of the MDA table monRepLogActivity always show zero. |
| 804197 | An 805 error, "Bad pointer < > encountered while remapping stored procedure < > . Must re-create procedure.", may be reported when LOAD DATABASE is run and the database dump that is loaded was taken with a pre-15.7 SP130 ASE version. See KBA 2423678. |
| 804211 | In some circumstances, the query on monCachedStatement might return empty resultset with a warning like "Command has been aborted". Some applications like DBACockpit might hit error when querying this table. See KBA 2402937. |
| 804276 | Parallel queries do not use User Thread Pools for worker threads. See KBA 2214120. |
| 804338 | In rare circumstances the message, "Current proces infected with 11" in the module la_alloc_one_page() together with a stack trace that includes the modules log__newpage() and plcblock__flush() may be reported in the SAP ASE error log following the message "ERROR: Can't get a new log page in dbid ...". |
| 804356 | When running in process mode, the server may terminate due to segmentation fault, after printing the error message, "uppwakeup: kpid = < -KPID > not within range", in the SAP ASE error log. |
| 804358 | The message "Current process infected with 10 (SIGBUS) or 11 (SIGSEGV)" in the module 'log_setopts' together with a stack trace may be reported in the SAP ASE error log when GRANT or REVOKE command is executed on a database where DDL replication is turned on. |
| 804381 | Multiple messages (1562, 1563 and etc.) are not re-directed to the trace file when tracing is enabled. See KBA 2407736. |
| 804394 | When the master database is setup for replication, Replication Agent may fail with errors 9254 and 9204 after dropping an object specific to replication such as the procedure 'rs_marker'. |
| 804408 | KBA 2452537 In rare circumstances, commands like DBCC REINDEX, DBCC DBREPAIR may acquire granular level (row/page) locks while they hold table level exclusive lock. |
| 804411 | In rare cases, queries involving a view on the inner side of an OUTERJOIN and having a subquery, may result in the optimizer timing out without a legal query plan . |
| 804573 | A 2760 error, "Column name ' < some corrupted column name > ' does not exist in target table." may be reported when creating index on a deferred table with the online parameter on ibmaix64 and sunsparc64 platforms. |
| 804606 | 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 REORG REBUILD command that was not finished at run-time. See KBA 2423084. |
| 804693 | In SAP ASE 16, MDA table monCachedProcedures does not reset counter when a new plan is generated due to temp table remap. |
| 804742 | If the set option ansinull is enabled, the execution of SP_HELPDB with @printopt = NULL returns less columns than expected. See KBA 2413731. |
| 804744 | A Page Verification Error notifying "fixed-row status improperly set" may be reported for DOL pages containing forwarded rows when DUMP/LOAD DATABASE is executed with VERIFY=FULL. See KBA 2414787. |
| 804775 | In rare circumstances CIS or RAT connections may hang or fail to connect. When a connection is hung, the execution of DBCC STACKTRACE( < spid > ) will report the function ksctsuspend() in the call stack. |
| 804824 | The 1295 error, "Unconditional lock request for table or page #, dbid # was made while holding a latch", may be reported in the SAP ASE error log when executing the command ALTER DATABASE OFF to remove a fragment of a log device. |
| 804839 | The message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the modules lock_draincache() and lock_release(), may be reported in the SAP ASE error log when termination of spids are done concurrently with lock-intensive INSERTs leading to freelock list corruption. See KBA 2414647. |
| 804930 | When upgrading SAP ASE dataserver via binary swap, NVcache are not restored back. |
| 805153 | The message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the modules yyparse(), sqlpars(), internal_sql(), curs_convert_to_exec() and curs_declare(), may be reported in the SAP ASE error log when executing prepared statements that include "ROWS OFFSET ?" via ODBC driver. |
| 805162 | In a highly loaded system where the statement and procedure caches are not sufficiently configured, the message "current process infected with 11 (SIGSEGV)" in the module 'ssql_lookup', or 'ssql__getdesc', or 'ssql__choose_victim' may be reported in the SAP ASE error log with the message 'Spinlock SSQLCACHE_SPIN' held, resulting in an implicit SAP ASE shutdown. |
| 805165 | Using numeric datatypes in a parameterized SQL with values that are similar such as 1.11 and 11.11 may lead to spinlock contention on the statement cache. |
| 805208 | If there is a stored procedure running at ISOLATION LEVEL 0 with: "INSERT ... SELECT ..." command without a FROM clause OR "SELECT ... INTO ..." command without a FROM clause and with "INSERT SELECT AT LEVEL 0" feature enabled the stored procedure may run into multiple recompilation error (11060). |
| 805246 | The message, "Current process infected with 11", in the module query_text() together with a stack trace which includes the modules exec_lava() and LePlanNext() may be reported in the SAP ASE error log when a session executes SP_SHOWPLAN. |
| 805301 | In rare cases, the 940 error message, "Dbtable in wrong state for operation", may be repeatedly reported in the SAP ASE error log when a error related to dbt_keep count going into negative values happens in a specific clean up code path. |
| 805449 | The message, "Current process infected with 11", in the module copy_sqltext() followed by a stack trace including the modules sqlpars() and internal_sql(), may be reported in the SAP ASE error log after the configuration options 'enable monitoring' and 'show deferred compilation text' are turned on. See KBA 2428396. |
| 805458 | In rare circumstances a 692, 834, 4216 or 4218 error can be reported in the SAP ASE error log when LTL mode replication is enabled. The errors are seen after DUMP TRANSACTION is executed. |
| 805471 | There could be discrepancy in NVcache's size when multiple NVcache are created with similar name. |
| 805498 | In rare circumstances on heavily-loaded systems create table in in-memory database may hang with a stack trace which includes the modules getpage__noscan(), getpage_with_validation() and bufsearch_cache_getlatch(). |
| 805646 | New columns ahave been added to monRepStreamStatistics for buffer pool package related monitoring when stream mode replication is enabled. |
| 805767 | When user running setuphadr with SAP ASE user "sa" locked, it will hit NullPointerException error but does not show what the error really is. |
| 805798 | In rare circumstances when the configuration option 'user log cache queue size' is enabled sessions may hang under a single-engine SAP ASE configuration. See KBA 2434457 |
| 805833 | In Accelerator for ASE, SAP ASE boolean operators %, &, |, ^ and ~ are translated to the equivalent functions in HANA. |
| 805984 | In certain circumstances, SAP ASE may raise error 17260, "Can't run < sproc name > from within a transaction.", if sp_monitorconfig is run in chained mode. |
| 806017 | A 8224 error, "Internal error: could not save description of lightweight procedure < > " together with a stack trace which includes the modules 'open__lwpbyname' and 'sqt_get_plan' may be reported in the SAP ASE error log while reinstalling a DES for a lightweight procedure in the metadata cache. See KBA 2452601. |
| 806106 | setuphadr may fail if granular permission is enabled. |
| 806146 | sp_configure should not accept 'User Defined NV Cache' as a valid configuration option. |
| 806272 | The temporary tables with same name will be created in JCS JDBC environment without error message. |
| 806392 | The message "Database 'master' is now online." may not be reported following the execution of LOAD DATABASE master command although the database is onlined. |
| 806446 | sp_configure 'number of early send rows', < value > and sp_configure 'early row send increment', < value > returns permission related error 10350 when granular permissions is enabled. |
| 806510 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stac ktrace that includes the module rvm__audit_roletoggle(), may be reported in the SAP ASE error log when enabling a role with a password within a stored procedure. |
| 806622 | Suboptimal performance may be seen on a heavily loaded multi-engine server, along with high value in spins for Resource- > rdbt_spin spinlock (Spins column in monSpinlockActivity). |
| 806724 | The message, "Current process infected with signal 11 (SIGSEGV)" involving the function dol_update() or decompress_column_by_coloff() or the error message 644 or the error message 2601 may be reported in the SAP ASE error log when executing ALTER DATABASE changing the options 'set compression' and 'lob_compression' together. See KBA 2447629. |
| 806726 | In rare circumstances, the message "current process infected with 11" in the module 'ssql__ubffree' together with a stack trace which includes the modules 'sqt_put_in_stmtcache' and 'ssql__rmplans' may be reported in the SAP ASE error log during the execution of a query resulting in SAP ASE shutting down implicitly while holding the spinlock SSQLCACHE_SPIN. |
| 807191 | LIMIT clause doesn't work with UNION view. The LIMIT clause doesn't make any affect and the whole result set is returned. |
| 807666 | In a replication environment using LTL, when Replication Agent ignores the truncation point received from Replication Server after determining that it is not valid as indicated by a warning message in the SAP ASE error log, data may stop being replicated or Replication Agent may terminate abnormally with an error 624. |
| 808060 | The JVM White Listing functionality may not be enabled whereby the "PCA JVM - DPRT White Listing is enabled" message will not appear during the JVM bootstrap in the SAP ASE error log. Alternatively Adaptive Server may hit a segmentation violation in JVM together with a native stacktrace in the module 'JavaThread::print_on_error' on hpia64 platform. |
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 PL06, ASE SP02 PL06, Adaptive Server Enterprise, Fix, Patch, Error, Bug, SP02 PL06 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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)