/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.1 SP00 PL01. Please be sure to read the Disclaimer below.
If the EBF/SP has been released, check the CR list and coverletter at the support.sap.com.
Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.
| CR Number | Description |
|---|---|
| 551014 | The built-in hashbytes() now supports the SHA-256 algorithm. See KBA 3108409. |
| 718367 | The SAP Backup Server error log and the dump header of an archive have been enhanced to include the login-name, suid, and spid values of the ASE process executing a DUMP DATABASE/TRANSACTION or LOAD DATABASE/TRANSACTION commands, allowing user identification without configuring auditing necessarily. |
| 749724 | object_status "contains compressed data" remains after table is truncated |
| 795707 | SAP Adaptive Server will perform memory movement sanity checks when started with trace flag 713 to help diagnose procedure cache memory corruption issues. |
| 800272 | The new database option “online free space acctg” allows SAP ASE to provide quicker end-users access to the database after an unpolite shutdown or crash of Adaptive Server, while the data segment free space counts are being recalculated. |
| 803692 | SAP ASE may report error 1972 without tableID and databaseID information when an index is created. |
| 819997 | A query from proxy table with long fixed binary column mapped to remote IQ table of binary column data type raises SIGSEGV sometimes. See KBA 2836702. |
| 820797 | Signal 11 on OdbcRemoteAccess::prepareResultSet(). See KBA 3586459. |
| 821081 | High contention on the database spinlock (rdbt_spin) may be seen during the execution when there are large number of databases( > 128) in ASE. |
| 821446 | In some circumstances, SAP ASE sp_sysmon may not report correct "Total Parallel Queries" information (count is 0) in the "Parallel Query Management" section even though parallel execution is actually used. |
| 821551 | Sybmigrate doesn't report object status if using objtype_create_list_from_sql=QUERY in resource file. See KBA 3007251. |
| 822898 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 's_estmt_pssinit' together with a stack trace may be reported in the SAP ASE error log, sometimes following a 701 error, "There is not enough procedure cache to run this procedure ...". See KBA 2358848. |
| 823355 | CIS operation may fail with a syntax error near '-' if the ASE has not been rebooted in a long time. See KBA 2987109 |
| 823436 | A 804 error, "Unable to find buffer < address > from cache < cache-name > holding logical page < page# > in sdes < address > kept buffer pool for object < table-name > .", or a 814 error, "Keep count of buffer < address > in cache < cache-name > holding logical page < page# > in database ' < database-name > ' has become negative.", together with a stack trace which includes the modules 'dol_update', 'dol_update', and 'bufunkeep_do_decrement' may be reported in the SAP ASE error log when a DML is executed and the database transaction log is full. Bootstrap Adaptive Server with trace flag 1102 in order to gather more information in the error log when the transaction log gets full. See KBA 2994461. |
| 823869 | SAP ASE may report incorrect value in "size" column from a proxy table created with "external directory" if the corresponding file size is larger than 2 gigabytes. |
| 824239 | In rare circumstances, a session that is executing 'sp_spaceused < table-name > ' may be put to sleep while an online utility on the same table is in progress. The call stack of the hanging session may report the modules 'des_do_get', 'des__in_use_error' and 'pg_getpagecounts'. See KBA 3112838. |
| 824449 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'pci_tpminvoke_longfunction' together with a stack trace which includes the modules 'objVerifySerializability' and 'BRIDGEapi_DeleteGlobalRef' may be reported in the SAP ASE error log when inserting rows with Java object to a table with Java ADT column types. |
| 824865 | A 8009 error, "Error encountered by Backup Server. Please refer to Backup Server messages for details.", may be reported when 'LOAD DATABASE < database-name > with listonly=create_sql' is executed and previously a database dump was taken using a dump configuration file. |
| 825178 | SAP ASE installjava may report an error like 'Server Message: asename - Msg 10795, Level 16, State 1: The file ' < classname > ' contained in the jar does not represent a valid Java class file.'. See KBA 3075958. |
| 825654 | A new configuration parameter 'lob cache percent' is introduced into SAP ASE allowing to limit the amount of memory used from the procedure cache by LOB objects. |
| 826302 | Load database from a remote backupserver with blocksize greater than 229376 (4K*56) failed with error,"The database page size of 4096 bytes obtained from ASE is different from the database page size of -1024 bytes read from the dump header. The LOAD session must exit.". See KBA 3192324. |
| 826480 | The global variable @@triggerstatus is introduced in SAP Adaptive Server. It returns the value for the action that has caused a trigger to be executed that is either 1 when the trigger was executed by an INSERT statement, 2 by an UPDATE statement, 3 by a DELETE statement, or 0 otherwise. |
| 826612 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'ptn__get_field' together with a stacktrace which includes the module 'mda_populate_monOpenObjectActivity' may be reported in the SAP ASE error log when querying the MDA table monOpenObjectActivity after running DROP INDEX WITH NOWAIT. See KBA 3205143. |
| 826720 | Improve error message 9829 "Compressed data row 0xxxxxxxxx in objid 1111111111, dbid 4 is corrupted." by including the page number the row is on. |
| 826737 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memtextlen' together with a stacktrace which includes the modules 'inserttext' and 'insert_all' may be reported in the SAP ASE error log when multiple DMLs on a table that has LOB columns are executed. |
| 826826 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeSendRow::sendRowToClient' together with a stack trace which includes the modules 'LeEmitSndOp' and 'exec_lava' may be reported in the SAP ASE error log during the execution of a SELECT query. To enable the diagnostic information for errors reported while sending LOB data to the client, Adaptive Server can be started with trace flag 7121. To disable the fix which handles NULL values for in-row LOB columns, Adaptive Server can be started with trace flag 7123. See KBA 2869968. |
| 827149 | A 3621 error with state 2, "You cannot load this dump because it contains functionality (feature ID < invalid-value > ) that is available only on the server on which it was dumped.", may sometimes be reported when downgrading SAP ASE to a version that does not support some feature. See KBA 3252070. |
| 827444 | A 1265 error, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr= < lock-address > , lrmagic=f).", in the module 'lock_release' together with a stack trace which includes the modules 'unmountdb' and 'dbs_shutdown' may be reported in the SAP Adaptive Server error log when UNMOUNT DATABASE is executed and at least one session was found active in the target database or doing cross database transaction involving target database which had session level attributes associated with it. See KBA 2933398. |
| 827511 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'prSQLTEXT' together with a stack trace which includes the module 'exec_dbcc' may be reported in the SAP ASE error log when DBCC SQLTEXT( < spid-value > ) is run against an active session. See KBA 3282789. |
| 827679 | Enhanced diagnostics for the message: "usrfill: vsn xx kpid xxxx read not posted due to external attention" by including client information, socket flags and buffer status. This message is logged in the SAP ASE error log when a client abruptly disconnects. |
| 827822 | Provide new functionality to existing built-in pageinfo() to read the requested page from disk |
| 827994 | SAP ASE may report an error message, "ASE is terminating this process" with the connection terminated when running commands "dbcc addextendedproc/dropextendedproc/findstranded" without input parameters. See KBA 3652196. |
| 828148 | DDLGEN is terminated after reported a user table has syntax error. Apostrophe (') in a column name is causing the problem. Please see KBA 3348879. |
| 828220 | In some circumstances, the message, "The free space count for fragment with lstart < logical-page-number > in database < database-name > was found to be negative and has been set to 0. Execute 'DBCC USEDEXTENTS( < database-name > ,0,1)' in single user mode to correct this count.", may be reported in the SAP ASE error log unexpectedly. |
| 828246 | Setting a BigDecimal type in prepared insert statement causes the scale part lost when executing the java code through JDBC dispatched in ASE server PCI/JVM. However directly executing the same code in standard JDBC client code can insert the value correctly. |
| 828331 | When server configuration 'enable granular permissions' is set to 1, the message "Permission related internal error was encountered. Unable to continue execution." is reported while executing command DBCC PRINTOLOG. |
| 828414 | The NV Cache section in sp_sysmon will print empty information even when an nvcache is not configured. See KBA 3377053. |
| 828469 | The message, "Current process infected with 11 (SIGSEGV)", in the module 'memalloc_zero' together with a stack trace which includes the module 'lavalfa_err_init' may be reported in the SAP ASE error log when running a SELECT query. See KBA 3382808. |
| 828504 | Error 707 "System error detected during attempt to free memory at address 0x2ac03e164a20" |
| 828690 | A 249 error, "Syntax error during implicit conversion of CHAR value < > to a INT field.", may be reported by SAP ASE when a SELECT query is run using a nested parameterized view. |
| 828817 | Provide a stored procedure to report the progress of a database shrink and additionally provide estimated completion time. See KBA 3254621. |
| 828834 | The message, "Only the owner of object < > or a user with 'sa_role' role can run this command." may not be reported by the SAP ASE server when a user tries to execute ALTER INDEX on another user's table and configuration 'enable granular permissions' is set to 1. |
| 829057 | Enhancement request to suppress "Cannot read, host process disconnected" and "Cannot send, host process disconnected" messages to the SAP ASE Errorlog under Traceflag 1675. See KBA 3428798. |
| 829062 | SAP ASE diagserver may report an assertion failure, "Assertion ((rgadmlobp- > admlob_oldcolscopied + rgadmlobp- > admlob_oldcolsdropped) == rgadmlobp- > admlob_numoldcols) failed in < path > /generic/source/sequencer/pre_alttab.c" when a LOB column is changed from "materialized" to "not materialized" |
| 829173 | The message "Sybmon encountered signal 11 at address os_get_prev_stk_desc + < offset > " may be reported when "profile" is run in sybmon on ibmaix64 platform. |
| 829340 | In rare circumstances, successive calls to getdate() built-in in SAP Adaptive Server may return a datetime value which is older than the previously returned datetime value. See KBA 3468430. |
| 829343 | Provide monDeviceIO performance information to sp_sysmon Disk I/O Management section. |
| 829351 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'bt__formsplitlogrec' together with a stack trace may be reported in the SAP ASE error log when SELECT INTO is executed. See KBA 3464190. |
| 829378 | The message, "Segmentation fault (core dumped)", will be reported when attempting to start the SAP ASE Backup Server without first having set the SYBASE environment variable. See KBA 3471199. |
| 829470 | In SAP ASE HADR environment, if 'cis packet size' is set to a value greater than 'max network packet size' the RMA reports error 'The packet size ( < value > ) specified at login time is illegal. Legal values are between < value > and < value > ' and execution of setuphadr fails. |
| 829481 | The message "ssl_nrpacket: vsn xxx kpid xxxxxx read returning -4 state 1" is reported in the SAP ASE error log when ASE performs a network receive on an SSL client that has disconnected abruptly. See KBA 3478645. |
| 829514 | The message, "Current process infected with signal 8 (SIGFPE)", or "timeslice < value > , current process infected at < address > ", in the module 's__collectdiagparam' may be reported in the SAP ASE error log when Adaptive Server has not restarted for long time. See KBA 2998380. |
| 829538 | A 456 error, “Failed to execute DROP PROCEDURE, because this is a read-only connection. Read-only connections can only execute SELECT statements. Use 'set readonly off' to execute DROP PROCEDURE.”, may be reported by SAP ASE when a JDBC connection is attempted and the options 'readonly' and 'dynamic_prepare' are enabled. |
| 829540 | When a MERGE command that has an UPDATE action which also assigns local variables is executed, SAP ASE will assign a NULL value to the second and subsequent local variables in the UPDATE action. See KBA 3531173. |
| 829574 | A 2742 message, "SET DATEFIRST < > is out of range." and 'Error: 2805, state: 20', may be reported by SAP ASE when a stored procedure is executed with recompile and the configuration options 'enable metrics capture' and 'enable literal autoparam' are enabled. See KBA 3492504. |
| 829608 | When TRUNCATE TABLE < table-name > PARTITION < partition-name > is executed, SAP ASE will rebuild the global indexes of the given table, even if the partition being truncated is empty. Additionally, the execution of DUMP TRANSACTION may be blocked for the duration of the global indexes rebuild. See KBA 3498667. |
| 829628 | The message, "Current process infected with 11 (SIGSEGV)", in the module ‘sqt_releases_ssql’ together with a stack trace which includes the modules ‘tdsrecv__dyndealloc’ and ‘tdsrecv_dynamic’ may be reported in the SAP ASE error log when the statement cache is full. See KBA 3464047. |
| 829656 | The message, "Current process infected with signal 11 (SIGSEGV)", either in the module 'memfree' or 'sequencer' may be reported in the SAP ASE error log when running sp_showplan against a running spid. See KBA 3426914. |
| 829660 | Under rare circumstances, the message "timeslice < negative-value > , current process infected at free__linkedcst" together with a stack trace when inserting a parameterized text value into a unitext column using a dynamically prepared statement. See KBA 3531166. |
| 829664 | In a high concurrency system, when SAP ASE is started with trace flag 11036 a new mechanism is used to improve performance and correctness when dealing with light weight procedures which is internally used for caching an ad-hoc query in the statement cache or a dynamic SQL prepare statement processing. Additionally, trace flag 8235 that is based on trace flag 11036 can further reduce memory usage. |
| 829766 | The stored procedures "sp_helpdb" and "sp_spaceused" are modified to report sizes of objects and databases in megabytes (MB) instead of kilobytes (KB). |
| 829799 | Two SAP Adaptive Servers can boot up on same port in windows system. See KBA 3519054 |
| 829803 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'plc__flush' together with a stack trace which includes the modules 'xls_pre_alloc_numclrs', 'xact_begin' and 'crt_main' may be reported in the SAP ASE error log when a stored procedure is run. |
| 829856 | SAP ASE sybmigrate might run into hang with repeatedly printing "still waiting at sync point < num > / < totalnum > " in the log file during the migration phase. |
| 829859 | In some circumstances, with granular permission enabled some performance impact may be observed when has_privilege() is involved. |
| 829887 | The system stored procedures sp_querysmobj and sp_deletesmobj have been enhanced to support hyperscaler cloud backups for IBM, AWS, GCP, and Azure with following changes. a) Updated 'server_name' parameter: Wildcard '*' is no longer allowed. A valid server name must be provided. If using '*' an error will be reported. b) New optional parameter 'config_name': If provided, the command will be run directly without needing a prior execution of SYB_BACKUP...sp_extlibcreds. If not, SYB_BACKUP...sp_extlibcreds must be first run once per Backup Server restart. |
| 829918 | In rare circumstances, an Adaptive Server hang may be observed after a session hits a 1249 error followed by errors 1251 and 6103 together with a stack trace which includes the modules 'lock__semawait', 'log__lock', 'xls__get_lastlogbp', and 'plc__flush' on AIX systems. See KBA 3536134. Start SAP ASE with trace flag 1240 to collect diagnostics information to help narrow down the root cause. |
| 829983 | The MDA table monSQLRepMisses may indicate Configuration instead of QueryLimitation as the cause for some queries which are not eligible for SQL statement replication. |
| 829999 | A 4402 error, “Infinite loop in view definition. Cannot resolve the view definitions in the query to the underlying tables.”, may be reported by SAP ASE when querying a view that references a SQL Function that is using a TUDF (Table User Defined Function) and before the query execution the SQL Function has been recreated. |
| 830005 | Limit 'create database' and 'drop database' to only saptu when 'cloudservice' is enabled. |
| 830014 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeRun' together with a stack trace may be reported in the SAP ASE error log when querying a view that includes table-valued UDFs and performs a hash union distinct join. See KBA 3542784. |
| 830015 | In rare circumstances, SAP Backup Server may run out of server connections when a client fails to connect to it and the two messages, "Backup Server: 1.28.2. < state-value > : Open Server routine srv_senddone failed. See Backup Server error log for additional information.", with state values 49 and 51 are reported in the Backup Server error log. See KBA 3542841. |
| 830030 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'xls_pre_alloc_numclrs' together with a stack trace which includes the modules 'lrd_log_run_dealloc', 'dmpx_truncatemain' and 'ckptproc' may be reported in the SAP ASE error log when the checkpoint task does checkpoint a database. See KBA 3535124. |
| 830034 | Enable sequence when "functionality group" is ON |
| 830039 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 's_recrtproc' together with a stack trace which includes the modules 's_recompile' and 's_renormalize' may be reported in the SAP ASE error log when a stored procedure is executed WITH RENORMALIZE option. See KBA 3577953. |
| 830040 | In rare circumstances, a COMMIT TRANSACTION may not finish if an external attention is sent to SAP ASE by the client application on version which includes fixes for CRs 829240 and 828165. See KBA 3422036. |
| 830079 | When replicating from SAP ASE to SAP HANA, ASE Rep Agent may terminate abnormally with an error 9210 state 30, "RepAgent( < dbid > ): Fatal error from CT-Lib. (CT-Lib command = usctresults, return status = 4047).". See KBA 3540554. |
| 830117 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'xact_rollback' together with a stack trace which includes the module 'set_repdb_off' may be reported in the SAP ASE error log when the command SP_REPTOSTANDBY < database-name > , 'NONE' is executed on an active system and is victim of a deadlock. See KBA 3545082. |
| 830141 | sp_help ' < object_name > ' may report an incorrect read_only value after ASE is upgraded or the database is loaded from an older version than ASE 16.0 SP02. See KBA 3392168. |
| 830155 | SAP Adaptive Server trace flag 17015 is extended at two more places to print the diagnostics of an alarm if it is freed again. See KBA 3189250. |
| 830178 | NFR: User can set bsrv.bs_config_file in response file to specify the configuration file path. |
| 830185 | In rare circumstances, a 1265 error with state 1, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr= < lock-address > , lrmagic=f).", may be reported in the SAP ASE error log during the execution of COMMIT TRANSACTION. See KBA 3549578. |
| 830195 | In rare circumstances, a 12858 error, "Update to sysobjects row for database ' < database-name > ' ( < database-id > ), object 'rs_ticket_history' ( < object-id > ) failed.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'dpdb_main', 'checkpoint’, des_idtflush' and 'obj_updrow' when DUMP DATABASE is run on an HADR system and concurrently table 'rs_ticket_history' is being dropped. See KBA 3564105. |
| 830206 | Msg 208 " < object name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)." maybe raised involving vu_redefine() when query from views after load database. |
| 830209 | The default value for optimize temp table resolution depends on the value to which enable functionality group is set. If you set enable functionality group to: 0 – the default value for optimize temp table resolution is 0. 1 – the default value for optimize temp table resolution is 1. However, if you set optimize temp table resolution to 1, it uses a value of 1 regardless of what you set enable functionality group to. |
| 830212 | The SAP ASE 'charset' and 'langinstall' utilities have been enhanced to support the option '-S < host-name > : < port-number > ' and an 'ssl' enabled connection. |
| 830218 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module ‘FILERemoteAccess::startScan’ together with a stack trace which includes the modules 'exec_lava’ and ‘LePlanNext’ may be reported in the SAP ASE error log when a SELECT query references a proxy table whose file name does not exist. |
| 830223 | show_cached_plan_in_xml() doesn't print the compile and exec parameters when using server side cursors. |
| 830243 | When joining proxy tables and local tables with WHERE conditions that include IN and OR clauses on the same column of one of the proxy tables, the query may return fewer rows than expected. See KBA 3555615. |
| 830253 | In some circumstances, incorrect data may be inserted in a local table when SELECT INTO EXISTING is executed and the data being inserted is not matching the datatype of the target local table column. See KBA 3269984. |
| 830254 | An error 10364, "Permission denied.", is reported when a user other than the dbo and without sa_role or replication_role, executes the system stored procedure SP_SETREPTABLE or SP_SETREPPROC without any parameter in order to list the replicated objects in the current database. See KBA 3556852. |
| 830258 | A 8233 error, “ < command-type > operation is in progress on the object < table-name > in database ' < database=name > '. Retry your query later.”, followed by a 941 error, “Illegal database context operation.”, together with a stack trace which includes the modules ‘s_runtime_compile’ and ‘closedb’, may be reported in the SAP ASE error log during the execution of a query. This may cause Adaptive Server to be unresponsive following error 6103, “Unable to do cleanup for the killed process; received Msg 941”. See KBA 3559053. |
| 830292 | The message, "Cannot allocate resources for listener with protocol < > , host < > , port < > .", may be reported in the SAP ASE error log during startup while upgrading to ASE 16.1 SP00 PL00 release with SSL enabled preventing Adaptive Server from booting. |
| 830310 | NFR: Setuphadr allows user to disable rma_admin password expiration. |
| 830351 | SAP ASE DDLGen may run into hang without any error message when -CNUMBER option is greater than 1. |
| 830400 | DBCC CHECKSTORAGE can take longer to prepare for checking when the number of objects is in the 10's of thousands. |
| 830416 | Memory leak when run dbcc checkstorage with_index option. |
| 830436 | SAP ASE may not clear the page compression bit (0x2000) from sysobjects.sysstat3 when a table is configured from "page compression" to "pagev2 compression". |
| 830455 | Stored procedures such as sp_help, sp_options, and sp_helpcache are not executed in read-only mode because the 'COND' operation is not allowed in read-only mode. See KBA 3652157. |
| 830507 | The configuration option "open index hash spinlock ratio" does not impact the number of spinlocks used for Index Hash Spinlock Contention. See KBA 3617221. |
| 830511 | In a database setup for LTL replication, a 9241 error, "RepAgent( < database-id > ): Failure initializing the Rep Agent Context.", together with a stack trace in the module 'ra_alarm_handler' may be reported in the SAP ASE error log when the RepAgent is killed and restarted immediately. Eventually, the message "Scheduler infected: exiting" is reported in the SAP ASE error log and ASE terminates. See KBA 3587182. |
| 830529 | The error message, "Backup Server: 1.28.2.235: Open Server routine at_lockmutex: mutex:262 spid: 0 failed. See Backup Server error log for additional information.", may be reported in the SAP Backup server error log when "sp_querysmobj ' < external-api > ', ' < output-file > ', '*', '*', '*', '*'" is executed. |
| 830531 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'Optimize' together with the message, "SIGSEGV is caught by VEH_Optimize()", may be reported in the SAP ASE error log during the execution of a SELECT query. See KBA 3618167. |
| 830572 | The execution of sp_helpconstraint will fail if the executor does not have the sa_role granted and a table has columns with default values, even when the executor is aliased to dbo. See KBA 3590836. |
| 830605 | SAP ASE may consume huge heap memory when a MDA table having huge rows is queried. See SAP Note 3595727 |
| 830628 | Apache Commons CLI and POI library in Workload Analyzer Command Line Utility is upgraded to commons-io-1.9.0 and poi-5.4.1. |
| 830630 | Apache Commons CLI is upgraded to version 1.9.0. |
| 830633 | Provide a sql interface to retrieve environment variable values. |
| 830634 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'xact__rollbackxact' together with a stack trace which includes the module 'omni_add_objectdef' may be reported in the SAP ASE error log when CREATE EXISTING TABLE is run that refers to an external server which does not exist in sysservers system table. |
| 830677 | Further adjustment/enhancement for new feature request under CR 828658. |
| 830696 | In rare circumstances, SAP ASE may report incorrect times metrics in 'monCachedStatement' table whereby 'MaxElapsedTime' may be less than 'TotalElapsedTime' while a long running query is being executed by another process. See SAP note 3602036 |
| 830735 | In a HADR environment, when a user logs in to the AMC UI of the Standby ASE server, the HADR Overview screen does not display any data and displays an error message “Unable to load data”. |
| 830777 | Feature Cockpit, SAP ASE Cockpit, Remote Command and Control Agent for SAP ASE are removed. |
| 830782 | In rare circumstances, a 605 error, “An attempt was made to fetch logical page < ... > ”, together with a stack trace which includes the modules ‘lava_psort_consumer’, ‘lava_startsort’ and ‘lava__nextpage’ may be reported in the SAP ASE error log when one session is creating an index and another concurrent session is inserting data with bulk copy while the 'compression info pool size' is under configured. |
| 830801 | In some circumstances, an undetected deadlock may be observed between processes trying to acquire a PLC_LOCK (Private-Log-Cache Lock) together with a stack trace which includes the modules 'buf_get_latch', 'xls_bufunpin', and 'plc__lock', sometimes followed by an 1105 error, "Can't allocate space for object ' < object-name > ' in database ' < database-name > ' because ' < segment-name > ' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.". See KBA 3618683. |
| 830815 | Adds a new message 1881: "Database '%.*s' has been created with success.", this will be printed to console & in ASE error log on successfully creating a database. |
| 830827 | A 10354 error, "Permission denied. You must be either the system administrator (SA), the database administrator (dbo), or the owner of this object to perform this operation.", may be reported by SAP ASE when sp_dboption is executed within the master database for another database. See KBA 3658780. |
| 830872 | SAP ASE may consume huge heap memory when a MDA table like monProcess or monOpenObjectActivity having huge rows is queried. See SAP Note 3595727. |
| 830907 | A 2601 error, "Attempt to insert duplicate key row in object ' < table-name > ' with unique index ' < index-name > '", may be reported during HADR replication which will bring down the DSI thread connection to SAP ASE. The connection cannot be restarted, and re-materialization is necessary. See KBA 3630732. |
| 830991 | When SAP ASE is started with trace flag 11036 the message, "Current process infected with 11 (SIGSEGV)", in the module 'proc_release' together with a stack trace which includes the modules 's_dealloccss' and 'css_deallocate' may be reported in the SAP ASE error log when DEALLOCATE CURSOR is run while the statement cache is enabled. |
| 831004 | When upgrade ASE server with the GUI tool sqlupgrade, a segmentation fault might happen. |
| 831070 | When shutting down SAP ASE, invalid text may be shown for "shutdown info" in the SAP ASE error log even though no shutdown info message was provided to the shutdown command. |
| 831079 | When SAP ASE is started with trace flag 11036 the message, "Current process infected with 11 (SIGSEGV)", in the module 'kbfalloc' together with a stack trace which includes the modules 'ssql_save_SQL' and 'lwp_create' may be reported in the SAP ASE error log when a query is run while the statement cache is enabled. |
Read more...
Environment
- AIX 64bit
- Linux on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.1
Keywords
CR, CR List, ASE 16.1,SP00 PL01, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)