/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in Adaptive Server Enterprise (ASE) 16.0 SP03 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 |
|---|---|
| 475133 | A Kerberos user is now allowed to execute ALTER LOGIN...MODIFY PASSWORD by passing caller password as null, if 'allow kerberos null password' is configured to 1. See KBA 2627321. |
| 549837 | The output of DBCC SHOWRECOVERY show some lines with incorrect information |
| 635018 | A new function, show_prepared_statements(), is provided to display the SQL text for the prepared statements. |
| 639976 | show_plan built-in has been enhanced to print procedure plan information from the procedure cache. |
| 660984 | A 7348 error, "Select expression results in more than one column having same name. Column name ' < colname > ' is specified more than once", will be reported if duplicate correlation names referencing different column names are present in the select list of a query. See KBA 2183207. |
| 751131 | The Sybmon restart command fails for a halted server with messages like "ResumeThread using ptrace failed for thread nnn, errno 3" if the server is running in threaded kernel mode and the Sybmon session is not the one that halted the server. |
| 772630 | The new fields 'dump_end_time' time when the DUMP ended and 'dump_size' expressed in pages have been added in the dump history file for better reporting. |
| 781928 | In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc__findcachedSQLplan' together with a stack trace which includes the modules 'mem_getpages' and 'freeprocs', may be reported in the SAP ASE error log when LOAD DATABASE is run, while another session is reusing the same object descriptor, whose procedure buffer is in the process of being freed by the session running the LOAD command. See KBA 2162502 & 2270963. |
| 785335 | A 2714 error, "There is already an object named < tablename > in the database", may be reported during the recompilation of a batch of prepared statements which creates a user table in tempdb followed by CREATE INDEX or any DDL on the same table. See KBA 2368989. |
| 786358 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'deletetext' followed by a stack trace that includes the modules 'omni_text_free' and 'omni_text_recover', may be reported in SAP ASE error log during recovery after failure to insert TEXT data into proxy tables. See KBA 2187723. |
| 790553 | The message, "Update of syslogins failed", can be seen in the SAP ASE error log when a login attempt was interrupted during the update of the system table syslogins. See KBA 2201383. |
| 793978 | For a multi-engine SAP ASE configured with LDAP authentication and running on the default kernel threaded mode, under rare circumstances, during a login, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'ldap_set_option' together with a stacktrace that includes the modules 'kllookupdn' and 'klbindfuncalt', may be reported in the SAP ASE log causing the SAP ASE to abruptly shut down. See KBA 2262332. |
| 798527 | setuphadr is enhanced to re-start the HADR set up from the step where it last encountered a recoverable error. If the error cannot be recovered, setuphadr will clean up the incomplete environment and re-attempt the set up. |
| 799092 | The message, "-- Unknown object type: SF", may be reported in the context when executing the sp_helptext system stored procedure against User-Defined SQL Functions with the 'ddlgen' option enabled. |
| 800520 | In rare circumstances, BCP IN may fail together with a stacktrace which includes the modules 'bt__check_insert_position' and 'bt_insert' reported in SAP ASE error log when the server sortorder is something like '*nocase*'. |
| 800868 | A 9557 error, "The server failed to create or update a row in table ' < name > ' because a varying-length column would start at offset < value > . This starting location cannot be represented accurately in the table's row format.", may be reported during DML execution if the SAP ASE page size is configured to either 8K or 16K bytes and the database option 'allow wide dol rows' is disabled. |
| 800965 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des__free_txrcoldes' together with a stack trace which includes the modules 'proc__used_as_login_script' and 'dropobject', may be reported in the SAP ASE error log when a stored procedure is executed. See KBA 2479691. |
| 802504 | A 15434 error, "Adaptive Server failed to create an encryption key for internal use. Please contact SAP Technical Support.", may be reported when the master key password is changed with ALTER ENCRYPTION KEY after a cross platform database dump is loaded in a different endianness platform compared to the one where the full database dump was taken. |
| 802535 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'showE_STMT' followed by a stack trace that includes the modules 'show_plan' and 'LeRun', may be reported in the SAP ASE error log when executing sp_showplan if the statement has changed during the execution of sp_showplan. See KBA 2373058. |
| 802812 | Streaming replication using the Component Interface now also supports object level replication. |
| 804078 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'com__exctnume_copy' together with a stack trace which includes the modules 'comnb_numtonum' and 'LeEvals::LeEvRun', may be reported in the SAP ASE error log if the configuration option, 'streamlined dynamic SQL', is enabled and a dynamic cursor query with an ISNULL expression on a numeric field is executed. See KBA 2493162. |
| 806370 | When auditing of sso_role is enabled, unexpected audit records may be generated against users without sso_role. See KBA 2441754. |
| 806853 | The output for the SET option sub-commands 'show_best_plan', 'show_final_plan', 'show_lio_costing', 'show_elimination' and 'show_parallel' does not print any information when the 'brief' option is used. See KBA 2450023. |
| 808387 | New options, 'disable_dc' and 'enable_dc', have been added to the sp_procxmode system stored procedure, to disable and enable deferred compilation for a particular user stored procedure respectively. |
| 808428 | ALTER DATABASE ROW STORAGE OFF currently needs the database to be in SINGLE USER mode. This fix lifts this restriction. |
| 809658 | Garbage collector for In-Memory Row Storage may get blocked on a utility, such as REORG REBUILD, REORG RECLAIM_SPACE, REORG FORWARDED_ROWS, REORG COMPACT, ALTER TABLE, CREATE CLUSTERED INDEX, DROP INDEX, TRUNCATE TABLE, even after the utility has exclusive lock granted on the table or does not involve the In-Memory row store content. |
| 809800 | A 7130 error, "WRITETEXT with no log is not valid at this time. Database testdb1 must first be configured for this.", may be reported when WRITETEXT is run against an in-row LOB column while replication is enabled. Additionally when WRITETEXT is run against an off-row LOB column of an MVCC or On-Disk-MVCC enabled table while replication is enabled a ROWIMAGE log record is logged twice mistakenly. |
| 810312 | A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > ." may be reported in the SAP ASE error log during LOAD TRANSACTION if the dump contains log records for index compressed pages as a result of REORG REBUILD INDEX execution. See KBA 2395755. |
| 810764 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ind__get_sysindrow' together with a stack trace which includes the modules 'par_get_info' and 's_runtime_compile', may be reported in the SAP ASE error log when a stored procedure that creates temporary tables is executed and SAP ASE references the wrong object. Use the SAP ASE command line (boot) trace flag 11014 to enable the current fix. See KBA 2438077. |
| 810847 | When the option 'set statistics io' is turned on, the output has been enhanced to display the number of logical and physical IOs for the sysversions table for On-Disk MVCC enabled tables and the number of rows read/write or migrated to IMRS for Data Row Cached and MVCC enabled tables. |
| 810912 | When the option "set statistics on" is enabled, a 16064 message, "SET STATISTICS ON: file ' < filename > ': file open failed with error < error_number > : File exists", may be reported when executing multi statements within one second. |
| 810991 | In a DRC/IMRS MVCC enabled table, rollback of a command may fail due to lack of memory. |
| 811061 | The execution of the system stored procedure sp_who may show an empty or erratic value for 'hostname' for the JOB SCHEDULER task as opposed to a NULL value. |
| 811095 | Workload Profiler is enhanced to be able to predict DRC suitability, estimated IMRS GC and IMRS PACK threads. |
| 811197 | A new stored procedure, sp_shrink, is now provided to shrink devices and databases. |
| 811296 | Incorrect HitCount and NumInserts may be reported in the monStatementCache MDA table. See KBA 2548423. |
| 811663 | Performance degradation may be observed when the SAP ASE optimizer selects a sub-optimal query plan in some cases where there are variables in the WHERE clause. |
| 811725 | Improve process of object id assignments to temporary tables to avoid raising spurious errors relevant to temporary tables like 'object not found', 'column not found'. |
| 811919 | DISK RESIZE must accept a negative value to shrink the device and truncate the device file in order to release space to the OS. |
| 811970 | In rare circumstances, a SQL query that is executed in parallel may hang in the module 'LePipeRWState::LePrwsRWVtuple' for the parent thread and the module 'LavaThreadDriverMain' for the worker threads participating in the query execution. See KBA 2567720. |
| 812014 | On Solaris 5.11 and later versions, the message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the SAP ASE error log when sybmon is attaching to the server which is not using ISM (Intimate Shared Memory). See KBA 2670742. |
| 812216 | If an SAP ASE engine hangs while a network listener is affinitied to it, the network listener will be respawned, but may not resume accepting connections as expected. |
| 812443 | If trace flag 766 is turned on, occasionally "ELC_VALIDATION_ERROR: Page < address > is not allocated in procedure cache. pelc = < address > , chunksize = < chunk size > , engine id = < engine id > , validate_flag = < 0/1/2 > " or ELC_VALIDATION_ERROR: Page not marked free. pelc = < address > , chunksize = < chunk size > engine id = < engine id > , validate_flag = < 0/1/2 > ." may be falsely reported in the SAP ASE error log during heavy workload or when SAP Adaptive Server flushes an Engine Local Cache (ELC) memory to its global memory pool. See KBA 2581174. |
| 812461 | In rare circumstances in a Distributed Transaction(DTM) environment, when the coordinating server is being rebooted after the crash, the messages, "Running spid is < SPID of current PSS > , spid from the pss in the sdes is < SPID of PSS cached in sdes > " and "Running kpid is < KPID of current PSS > , kpid from the pss in the sdes is < KPID of PSS cached in SDES > ", together with a stack trace, which includes the modules 'pss_from_sdes' and 'closetable', may be reported in the errorlog of a participant server for an On Disk MVCC enabled database, when the diagserver binary is used. |
| 812476 | The CREATE TABLE and ALTER TABLE commands have been extended to provide new options to warm the IMRS Cache. New syntax extensions now allow all rows accessed by a query to be cached or the maximum number of rows that can be cached by a query to be specified. |
| 812477 | Under rare circumstances, SAP ASE may appear to hang during an UPDATE STATISTICS or another commands that runs at a lower priority. See KBA 2581507. |
| 812551 | A 154 error, "LIMIT clause is not allowed in UNION.", will be reported when applying the LIMIT clause in a UNION query. |
| 812687 | The sp_sysmon report is completed with a new entry in the section "Transaction Management", for the "ULC Flushes to Xact Log": "by IMRSLOG Replication". It indicates when the ULC was flushed while writing a book-keeping log record in SYSLOGS for a replicated transaction in SYSIMRSLOGS. |
| 812823 | On heavily loaded systems, spinlock contention may be observed on statement cache when multiple UPDATE statements with similar data of numeric datatype are present. Use the run time trace flag 11013 to enable the use of a single cached plan for multiple UPDATE statements. See KBA 2590282. |
| 812875 | The 9239 error message, "RepAgent( < database-ID > ): Cannot allocate < number > bytes of memory and will sleep until memory becomes available. Rep Agent Thread: < value > , status: < value > / < value > . Contact a user with System Administrator (SA) role to reconfigure Adaptive Server with more memory for Replication.", is enhanced with details which can help in analyzing the reason for memory shortage of the Rep Agent Memory Pool. |
| 812974 | New interface to allow packing rows out of IMRS using the sp_imrs system stored procedure. The syntax is sp_imrs 'pack_rows', ['aus', ' < number_of_Allocation_Units_to_pack > ' | 'pct', ' < percentage_of_Allocation_Units_to_pack > ']. |
| 813037 | During a graceful shutdown of SAP ASE in threaded mode, the errorlog indicates a new configuration file is written even if there are no configuration changes done. See KBA 2594978. |
| 813102 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page. Rid pageid = < value > ; row num = < value > . Page pointer = < value > , pageno = < value > , status = < value > , ptnid = < value > , indexid = < value > , level = < value > , pnextrno = < value > ", may be reported in the SAP ASE error log when an IMRS enabled database is replicated and there is very high activity on the database. |
| 813326 | A 249 error, "Syntax error during explicit conversion of VARCHAR value '# < value > ' to a INT field", will be reported when executing sp_shmdumpconfig. See KBA 2623861. |
| 813337 | A 6601 error, "You cannot execute a query involving access from T-SQL database and SQLScript database at the same time", will be reported when sp_downgrade_esd is run against a SQLScript database. |
| 813511 | In rare circumstances, a 3401 error, "Rec_logbounds: getnext SCAN_RID of last checkpoint failed on Rid from sysdatabases. Rid pageid = < page# > ; row num = < row# > .", may be reported in the SAP ASE error log during boot time recovery resulting in the database not being recovered or Adaprive Server may not start if the error occurs for the master database. |
| 813547 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322. |
| 813672 | The message, "Sybmon encountered signal 11 at address elf_offset_to_name", together with a stack trace which includes the modules 'os_getsyms' and 'pcdescformat' may be reported when running the sample command on the Solaris x64 platform. |
| 813694 | On Windows platform, a 12055 error, "System call stati64 failed with error 3", will be reported when executing a query on the monDeviceSpaceUsage table when there is a SAP ASE device created on a Windows mounted path. See KBA 2611275. |
| 813720 | In rare circumstances, the background process IMRS_PACK may hang indefinitely for an IMRS enabled database while searching for rows to pack in the IMRS ILM queue. |
| 813810 | In rare circumstances on a heavily-loaded system, SAP ASE may omit to recover IMRS committed transactions during the crash recovery of an IMRS enabled database when the configuration option ‘recovery interval in minutes’ is set to a small value and DUMP DATABASE or DUMP TRANSACTION commands are frequently executed. |
| 813815 | Under an HADR setup when stream replication is enabled, a 9405 error, "RepAgent( < dbid > ): Internal Error. The total number of columns in raobj ( < number > ) does not match the number of elements in RA_COLS list ( < number > ).", may be reported in the SAP ASE error log. This error occurs when the metadata can't fit in the current package and Rep Agent has to flush it prior to sending the metadata. The error doesn't impact replication and can be ignored. See KBA 2630044. |
| 813847 | Multiple threshold actions may be executed unwantedly to extend a database through a threshold action if the database is blocked due to long duration of a concurrent DUMP DATABASE execution. See KBA 2614731. |
| 813917 | The shared objects libjpeg.so and liblcms.so (JPEG.DLL/JPEG.PDB and LCMS.DLL/LCMS.PDB on Windows) have been added to ${SYBASE}/shared/ase/jvm.wl (%SYBASE%\Shared\ase\jvm.wl on Windows) JVM allow-list[*] file. |
| 814051 | An UPDATE query which involves tables not consistently qualified with the 'dbo' qualifier, may give wrong results when executed by a user who is not the database owner. See KBA 2619053. |
| 814095 | Under rare circumstances, SAP ASE may hang at startup during engine online, when SAP ASE is running on kernel process mode. See KBA 2635465. |
| 814190 | A 16053 error, "The command 'LOAD TRANSACTION' with property 'WITH UNTIL_TIME' is currently not supported in SAP Adaptive Server, IMRS-database < database_name > .", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database. |
| 814192 | Improvements have been made to the configuration option "restricted decrypt permission". See KBA 2623174. |
| 814204 | In rare circumstances, the statement line number is not correctly displayed in the showplan output when an SQL statement is executed with the set showplan option enabled. |
| 814248 | A new SAP ASE configuration option, "stream rep msg channel timeout", is introduced through sp_configure for an HADR setup using synchronous replication. During a failover, this option defines the minimum time in seconds before a mode switch can take place. The default value is 60 seconds. |
| 814287 | With command line traceflag 11826 on, final query plans will print unique physical operator ids, to make their identification simpler. See KBA 2723236. |
| 814289 | The message, "Internal error: data length mismatch in ct_fetch().", may be reported in the Optdiag error log when displaying statistics using the Optdiag in a BASH shell with the LANG environment variable set to default. See KBA 1866748. |
| 814330 | For SAP BW user queries with fact_table hints, sometimes when the hint fails, SAP ASE selects a suboptimal plan because of a bad optimzation goal, resulting in poor performance. See KBA 2717708. |
| 814445 | In some rare scenarios, parallel execution of a query hangs when dynamic thread allocation feature is on and the query plan contains LeRestrictOp in the right subtree of LeMJOp. See KBA 2642040. |
| 814496 | The SAP ASE Workload Analyzer will fail to replay dynamic SQLs in a workload with errors, "Dynamic SQL error - Prepared statement 'xxxxx' does not exist.", reported in the SAP ASE Workload Analyzer Error Report Dashboard if the capture starts after the dynamic SQLs have been prepared. See KBA 2628500 |
| 814590 | DDLgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. See KBA 2632662. |
| 814596 | A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name1 > , object < obj_name1 > , index < idx_name1 > , partition < ptn_name1 > and not to database < db_name2 > , object < obj_name2 > , index < idx_name2 > , partition < ptn_name2 > ", may be reported in the SAP ASE error log after executing a CREATE CLUSTERED INDEX on a round-robin partitioned table with the dboption 'enforce dump tran sequence' enabled. |
| 814605 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeHashContext::Open' followed by a stack trace that includes the modules 'LeHashOp::_LeOpOpen', 'LeEmitXchgOp::_LeOpOpen' and 'LePlanOpen', may be reported in the SAP ASE error log when executing some SAP BW queries using a cached plan with a fact_table hint |
| 814632 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ksMuxSchedulerRemoveQ' may be reported in the SAP ASE error log when a SHUTDOWN command with the WITH NOWAIT option is executed and will cause the shutdown command to hang. |
| 814639 | Under an HADR setup when stream replication in enabled, sometimes the last command replicated is not confirmed by Adaptive Server and hence not applied on the standby database by Replication Server if there is no activity occurring in the primary database following that last command execution. |
| 814657 | In rare circumstances under an HADR setup, a 9414 error, "server RepAgent( < dbid > ): Streaming replication stream CI Library error -1 with severity 2 and message 'Producer receiver ' < db_name > ' failed to receive data, shutting down transport to 'ocs:host:port'.'. Rep Agent detected error 3 with message 'Unknown' at line 0 in file nofilename.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent hang. |
| 814658 | The message, "Sybase ENPAPI Error Message: INFORMATION: The FIPS Certified Crypto Kernel is enabled", is reported in the Job Scheduler Agent log as an information message but it also contains the term "Error", making it ambiguous. KBA 2652006 - Unclear information in ASE errorlog file about 'ENPAPI Error' |
| 814669 | DBCC CHECKCATALOG output format is misaligned and appears garbled. See KBA 2634413. |
| 814674 | In some cases, wrong results may be returned when executing a stored procedure containing views that might need to be recompiled. |
| 814700 | A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization." may be reported when enabling statement cache and using a table variable within a derived table. See KBA 2635224. |
| 814754 | A batched language command executed with DYNAMIC_PREPARE set to FALSE can result in an open object and cached statement to be consumed and unable to be reused or freed for each batch. See KBA 2613604. |
| 814755 | Occasionally the execution of a SELECT query on a Data Only Locked (DOL) table may lead to incorrect results when the query optimizer uses a composite index of this table in order to access the data whose index leading column datatype is a fixed length CHAR and it contains special ASCII characters, such as CHAR(10), CHAR(31) or CHAR(1). See KBA 2636753 |
| 814767 | A 12352 error, "A transaction in database ' < name > ' (spid= < value > ) has hit a fatal error during rollback. ASE will try to reboot and recover the database. The XREC_BEGINXACT of this failing transaction is ( < page# > , < row# > ).", will now be reported in the SAP ASE error log besides to the end-user when the database option 'allow db suspect on rollback error' is enabled and a non-recoverable error is hit during a transaction rollback. |
| 814782 | MERGE statement that does not perform any action may incorrectly return a rowcount different than zero. |
| 814788 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'func2view' followed by a stack trace that includes the modules 's_crtproc' and 'sequencer', may be reported in the SAP ASE error log when creating an in-lined Table-Valued SQL-based User Defined Function without SELECT statement. |
| 814798 | In an HADR setup when stream replication is enabled, a 2615 error, "Attempt to insert duplicate row in database ' < name > ' ( < database ID > ), object ' < name > ' ( < object ID > ), index ' < name > ' (0), partition ' < name > ' ( < partition ID > ). Could drop and recreate index with ignore duprow or allow dup", followed by the message, "Command has been aborted", may be reported when replicating an All Pages Locked table that has a clustered index defined. |
| 814806 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < name > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), partition 'sysimrslogs_59' (59). Please contact SAP Technical Support.", may be reported in the SAP ASE error log when a SELECT-INTO from sysimrslogs command is executed. |
| 814837 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mem__pageallocate_this_engine' together with a stack trace which includes the modules 'mem_pageallocate', 'mem_getpages' and 'hashbifs_md5_lerun', may be reported in the SAP ASE error log when using hashbytes() built-in with MD5 algorithm and input arguments as NUMERIC/DECIMAL/MONEY. See KBA 2636316. |
| 814870 | A 10330 error, "Access permission denied on object < objname > , database < dbname > , owner < username > ", may be reported when a stored procedure is executed by a user that does not have explicit permissions granted on the underlying referenced objects in the stored procedure, such as partitioned tables and user defined functions, while SAP ASE renormalizes the stored procedure from its text. |
| 814910 | In rare circumstances, the message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation", in the module 'get_resrow_size' together with a stack trace which includes the modules 'LopInsert::_lopCodeGen' and 's _compile_stmt' may be reported in the SAP ASE error log when a query is compiled and an object ID has been recycled by Adaptive Server causing a conflict between a definition time object ID and a Light Weight Procedure (LWP) object ID. |
| 814916 | In a HADR installation, a new $SYBASE/DM/dir.properties file is added to capture the Custom Directory Information specified during HADR configuration. |
| 814919 | In rare circumstances under an HADR setup, a 12406 error, "Failed to find the last row marker for transaction ( < pagenum > , < rownum > ) in sysimrslogs for database ' < dbname > ' ( < dbid > ). The sysimrslogs row is corrupted.", may be reported during boot-time recovery of an IMRSLOG enabled database when stream replication is enabled. |
| 814923 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra_malloc_mempool' and 'ra_mempool_alloc_internal', may be reported in the SAP ASE error log when the Rep Agent Secondary Truncation Point (STP) Manager Thread terminates abnormally leading to corruption in the Rep Agent Memory Pool. See KBA 2722607. |
| 814927 | In rare circumstances on a heavily-loaded system, DROP INDEX may hang when the SAP ASE configuration option "hcb index auto tuning" is enabled and the HCB AUTO TUNING process is now sleeping and was working on the corresponding index. |
| 814942 | The SAP ASE Workload Analyzer will fail to replay a workload with errors, "ReplayThread- > loginUser for session < session ID > is empty" and "recieveTDSPackageToASEServer no response data from server for < Thread ID > ,SessionState [conn_id= < Session ID > , replayQueryID= < Query ID > , sessionStatus=LOGIN" reported in the SAP ASE Cockpit log if there are Kerberos enabled sessions. |
| 814959 | In rare circumstances, a hang may be seen and reported by sp_lock, when a process executes a WRITETEXT command that is replicated and involves an in-row LOB column and a shared row lock request cannot be granted immediately, or when it sets the IDENTITY max burn value for a table and an exclusive table lock request cannot be granted immediately, or when the commands ALTER DATABASE and DUMP DATABASE or TRANSACTION are run concurrently and an exclusive address lock request on the database disk map cannot be granted immediately. |
| 814960 | In rare circumstances, SAP ASE sessions may hang in the module 'des_do_get' when attempting to access a table, as a result of a 2622 error, "Insufficient room on this page to insert a row of length < row length > . Page pointer = < page address > , pageno = < page number > , status = < page status > , ptnid = < partition id > , indexid = < index id > , level = < level > , pnextrno = < next row number > .", hit by another session together with a stack trace which includes the modules 'des__scavenge' and 'stat_pdes_flush_datachange' reported in the SAP ASE error log while an object descriptor is reused to host metadata for this table. See KBA 2670244. |
| 814962 | A 2512 error, "Table Corrupt: Cannot find the specified row number < value > , in index page < value > , partition ID < value > , on data page < value > .", may be reported when running DBCC CHECKTABLE and after loading a transaction dump that was taken while a concurrent committing transaction and the ckeckpoint log record written by DUMP TRAN was stored interleaved with the committing transaction log records in such a way that the fullycommitxact marker in the dump header is set to the dump instant of the IMRSLOG database. |
| 814968 | Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled. |
| 814980 | In rare circumstances on a multiple-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace which includes the modules 'strn0cpy', 'worcap_admin' and 'd_worcap_start' may be reported in the SAP ASE errorlog when the "dbcc workload_capture(start)" command is executed when the server is still being boot-strapped. |
| 814983 | In rare circumstances under an HADR setup a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the target page is not a data page.", or a 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page.", or a 625 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the entry in the offset table for that RID is less than or equal to 0.", may be reported by the Rep-Agent scanner of IMRSLOG when a re-scan occurs and stream replication is enabled on an IMRS database. |
| 815018 | A 5859 error, "The configuration number '652' is invalid.", which value corresponds to the configuration parameter "bind backupserver address" may be reported in the SAP ASE error log during startup after adding a Dump Configuration using the ASE Cockpit or by using the stored procedure sp_config_dump. See KBA 2640866. |
| 815021 | The values of local variable parameters are not printed in the output of the 'select query_text( < spid > )' query. |
| 815044 | A 101 error, "SQL syntax error", followed by a 105 error, "Unclosed quote before the character string", may be reported in the SAP ASE error log when the Job Scheduler is scheduling a new job with start time equal to the current time and under the condition that it has already scheduled maximum jobs i.e. equal to the value of config parameter 'job scheduler tasks'. |
| 815051 | In rare circumstances, a 5166 error, "DISK RESIZE encountered an error while attempting to open/resize the physical file < file_name > . Please consult the ASE error log (in the ASE boot directory) for more details", may be reported in the SAP ASE error log along with the message, "basis_dsizecheck: attempt to write page < page no > on device < path of the device > failed, system error is: Invalid argument", when DISK RESIZE is run again after a silent failure of an earlier DISK RESIZE command. See KBA 2645986 |
| 815055 | A 207 error, "Invalid column name ' < name > '.", may be reported during the execution of a SELECT query that joins a proxy table which has a LOB column while the statement cache is enabled. See KBA 2647459 |
| 815056 | A 208 error, "# < temporary_table_name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).", may be reported during the recompilation of a prepared statements batch which creates a temporary table. See KBA 2646418. |
| 815070 | SQL query text is not printed with stacktrace when SAP ASE runs into an exception during parallel execution. |
| 815081 | In rare circumstances, a 702 error, "Memory request for < num > bytes exceeds the size of single page of < 16384/8192/4096/2048 > bytes.", may be reported on a 16K/8K/4K/2K-byte SAP ASE installation, in the corresponding order, when the system stored procedure sp_post_xpload is executed after a cross platform DUMP or LOAD was run and a table in the source database has undergone a no data copy operation. |
| 815086 | The 728 error message, "Allocation of size < value > bytes from the row storage cache, ' < name > ', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < value > , object ID = < value > , partition ID = < value > , request type = < value > ( < string > ).", is enhanced to provide additional context information when we have run out-of-memory for an IMRS enabled database. |
| 815099 | A 12858 error, "Update to sysobjects row for database ' < name > ' ( < dbid > ), object ' < name > ' ( < objid > ) failed.", in the module 'obj_updrow' together with a stack trace which includes the modules 'des_idtflush' and 'des_checkpoint' may be reported in the SAP ASE error log when DUMP DATABASE is in progress and the DDL transaction that created this object is rolled back. |
| 815102 | A 251 message, "Unable to allocate ancillary table for query optimization. Maximum number of tables in a query (91) exceeded" may be be reported when more than 91 worktables are required internally by to execute a query. |
| 815110 | In rare circumstances under an HADR setup, a 9219 error, "RepAgent( < dbid > ): Internal coding error.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent implicit shut down or hang. |
| 815121 | A warning message, "The configured value < value_1 > for parameter 'kernel resource memory' is too low. It should be at least < value_2 > for the present configuration", is reported when the kernel resource memory is resized by the server. This is not an appropriate warning and is now replaced by an informational message, "ASE has autoconfigured 'kernel resource memory' to < value_3 > pages". |
| 815123 | The Backup Server may leak some memory when using non absolute paths for the interfaces file, the configuration file, the hosts.allow file or the dump stripes. |
| 815161 | A 8006 error, "ASE error detected by Backup Server. Refer to the preceding Backup Server message.", together with a stack trace that includes the modules 'dmp_send_dpm' and 'dpdb_main', may be reported in the ASE error log and the counterpart error, "3.15.2.1: The disk piece for page < number > does not belong to phase 2.", in the backup server error log when DUMP DATABASE is run while taking a database dump of an IMRS enabled database and the configuration parameter 'optimize dump for faster load' is enabled. |
| 815175 | In rare circumstances, SAP ASE may hang in the module 'xsc_sysimrslogs_valid_xactblk' together with the modules 'xsc__sysimrslogs_getnext' and 'rec__boot_recover_dbs' reported in the call stack of the hanging process while an IMRS enabled database is recovered as a result of an IMSLOG invalid page present in the committed region of the IMRSLOG. |
| 815210 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ResRelOp' followed by a stack trace that includes the modules 'ResRelOpProcess' and 'CgpPop::_CgpPePredBmToScalar', may be reported in the SAP ASE error log when a query is executed that involves an OUTER JOIN on a materialized view and a non-materialized view that return a constant column and there is a predicate on this constant column. |
| 815216 | The index attribute 'optimitistic_LFB' will not be enabled as expected on big-endian platforms such as Solaris, IBM pSeries Linux, IBM AIX and HP Itanium platforms, when executing command "sp_chgattribute ' optimitistic_LFB', 1". |
| 815217 | In rare circumstances, a storage access violation or the message, "Current process infected with signal 11 (SIGSEGV)" followed by a stack trace that includes the modules 'ubffreef', 'memfreeheap' and 'table__check', may be reported in the SAP ASE error log when running DBCC CHECKTABLE against system tables like SYSCOMMENTS where there are hidden columns. See KBA 2722616. |
| 815225 | Status bits representing a text page or an OAM page may be incorrectly set in a page pertaining to an imrslog segment. |
| 815238 | An 15413 error, "An internal error occurred during an encryption operation (error code -1)", may be reported when selecting data from views that contain encrypted columns where each view is created with the UNION ALL clause. See KBA 2651130. |
| 815342 | A SELECT query against the monSysLoad MDA table can return zero row if a search argument on EngineNumber or StatisticID is used with an engine number other than engine 0. See KBA 2651421. |
| 815367 | In rare circumstances, DUMP DATATBASE may take extra time while releasing memory pages that keep track of page updates since the dump has started, after the dump is completed if the configuration option 'optimize dump for faster load' is enabled. See KBA 2657654 |
| 815369 | A new status bit (0x20) has been added to the dump history record to mark those entries that were inserted as a result of a LOAD instead of a DUMP operation. |
| 815388 | ASE needs to be rebooted to load the new SSL certificate after the existing certificate expires. This is now fixed by allowing ASE to reload new SSL certificate dynamically using the new parameter 'refreshcert' for sp_ssladmin. |
| 815399 | In rare circumstances, DBCC CHECKTABLE may report index inconsistencies on an IMRS enabled table, after LOAD DATABASE followed by one or more of LOAD TRANSACTION commands using the backward scan recovery strategy were executed. |
| 815429 | A new system view, syslogininfo, has been added to allow ASE users having sa_role or sso_role role to find out the number of days remaining before logins will be locked due to an unchanged password. See KBA 2686769. |
| 815472 | In rare circumstances, when a workload with a large dataset is being monitored using the Workload Profiler, an arithmetic overflow error may occur. If a new monitoring session is started while the existing one is still active, a 19537 error, "Invalid syntax or illegal use of the USING clause" is incorrectly reported which is misleading. |
| 815480 | The error, "Backup Server: 3.17.2.2: Pathname parameter must specify an absolute pathname. Rejected value: (unreachable)/ASE-16_0/install", followed by a 8009 error, "Error encountered by Backup Server. Please refer to Backup Server messages for details.", will be raised when executing a DUMP or LOAD command if the SAP ASE working directory is unmounted. See KBA 2669530. |
| 815496 | Under rare circumstances, the free page count for database segment 0 (system) may become negative and not reset to 0 without a message reported in the SAP ASE error log indicating this negative free page count. See KBA 2686750. |
| 815548 | In rare circumstances, a 631 error, "The length of < value > passed to delete row routine for the row at offset < value > is incorrect on the following page of database ' < name > ': Page pointer = < value > , pageno = < value > ... The expected row length is < value > . The offset should be no greater than < value > .", may be reported in the SAP ASE error log followed by the message, "Error while undoing log row in database ' < name > '. Rid pageid = < value > ; row num = < value > .", during the roll back of a user transaction when the syslogs available space has crossed the last chance threshold and the session was explicitly killed. This may result in phantom locks left behind because of the roll back failing. See KBA 2660763. |
| 815581 | A 11060 message, "This statement has exceeded the maximum number of recompilations (20). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support", may be reported during workload replay with the "Reset server time to source workload capture time" option selected and a VIEW, that is created after the workload captured time, is accessed. See KBA 2661224. |
| 815594 | Under some circumstances, the output from executing the sp_opt_querystats procedure with the 'option_show_long' option may have malformed text with random newline breaks over some words. |
| 815608 | In rare circumstances, the message, "Current process infected with 11 (SIGSEGV)" in the module 'dol__index_decompress_row' together with a stack trace which includes the modules 'bulk_fast_idxupdate' and 'reorg_defrag', may be reported in the SAP ASE error log when REORG DEFRAG is run. See SAP Note 2665483. |
| 815610 | A 9414 error, "RepAgent( < dbid > ): Streaming replication < value > CI Library error < value > with severity < value > and message ' < failure_reason > '. Rep Agent detected error < value > with message 'Unknown' at line at line 0 in file nofilename." may be reported in the SAP ASE error log when the stream replication is enabled and an error has occurred in an HADR setup. The code is enhanced to report appropriate line number and file name values to help diagnose the code path taken when the problem was encountered. See KBA 2686789. |
| 815662 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'EquivClass::EquivClass' together with a stack trace that includes the modules 'EquivClass::eqcCheapestNonBmoSortPop', 'EquivClass::eqcEagerEnforce' and 'GttTable::GttUsefulIndex', may be reported in the SAP ASE error log when selecting from a table-valued UDF using Parallel Mode. See KBA 2663557. |
| 815677 | Non thread-safe time routines are used to construct up the stripe names when DUMP DATABASE or DUMP TRANSACTION is executed with the option "using config= < dump_configuration > ". |
| 815681 | Performing a downgrade from SAP ASE 16.0 SP02 PL05 or higher to a version prior to SAP ASE 16.0 SP02 may report a failure on 'sysobjects.sysstat5' and 'sysindexes.status4' columns for replicated tables having a unique index. See KBA 2664693. |
| 815730 | Performing a downgrade from SAP ASE 16.0 SP03 PL04 may report a failure on 'sysindexes.status4' columns for user tables having a Latch Free Btree index on big-endian platforms, such as Solaris, IBM pSeries Linux, IBM AIX and HP Itanium platforms. |
| 815731 | A 728 error, "Allocation of size < num > bytes from the row storage cache, < cachename > , failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < memory_address > , object ID = < object_ID > , partition ID = < partition_ID > , request type = < type_ID > < (type name) > .", may be reported when a DELETE or UPDATE operation is being performed on a row that reside in the in-memory row storage and there is not enough space available. |
| 815740 | The message "current process infected with 11 (SIGSEGV)" in the module 'site_login_cancel' with a stack trace followed by the message "Scheduler infected: exiting" may be reported in the SAP ASE error log. See KBA 2682423. |
| 815749 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'vu_fixupvar' followed by a stack trace that includes the modules 'vu_fixupview', 'vu_fixuproot' and 'vu_fixupsubq', may be reported in the SAP ASE error log when a query is executed on a VIEW and there are more than 128 worktables involved in the VIEW. |
| 815803 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubffreef' followed by a stack trace that includes the modules 'ufclose', 'dir_sendtext' and 'DIRRemoteAccess::sendText', may be reported in the SAP ASE error log during concurrent access of big files via a proxy table. See KBA 2672421. |
| 815811 | Executing 'REORG REBUILD < table name > < index name > ' where the index has latch_free_index enabled may result in various errors including 12314, 12323, 820, 872, 11068 at run time and a 3478 error during recovery. See KBA 2669056. |
| 815821 | When Rep Agent is configured for stream replication in an IMRS enabled database and a retriable stream error occurs, the message "current process infected with 11 (SIGSEGV)" in the module 'ubffreef' together with a stack trace which includes the modules 'ra_free_mempool' and 'ra_ci_stp_remove_all_oqid' may be reported in the SAP ASE error log resulting in Adaptive Server terminating abnormally because of RAMEM_SPIN spinlock being held. See KBA 2686301. |
| 815832 | A 11021 error, "Function < function_name > invoked with wrong number or type of argument(s).", may be reported in the SAP ASE error log when upgrading a SAP ASE 16.0 SP03 PL03 or later version and an in-lined table-valued UDF is accessed. |
| 815833 | A query, which is selecting from a view with a left outer join and a predicate in where clause, and the view definition contains a subquery in 'When exists' which is wrapped in 'case' clause and a left outer join is used, may return wrong results which don't take the predicate into account. See KBA 2690931. |
| 815835 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE. |
| 815844 | When SAP ASE encounters a secondary signal violation while dealing with a primary signal violation, it makes the process that hit these signal violations a zombie process. SAP ASE will now shut down implicitly instead and the message, "UNHANDLED EXCEPTION: signal in signal handler", will be reported in the SAP ASE error log. When required it is possible to retain the zombie process behavior by starting SAP ASE with the trace flag 2917 or enabling it at run time using DBCC TRACEON. See KBA 2682383. |
| 815851 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'odlrh__toloh' together with a stack trace which includes the modules 'onl__test_upgraded_replicated_db' and 'online_database' may be reported in the SAP ASE error log, when a replicated database dump is loaded into an upgraded Adaptive Server version. See KBA 2686290. |
| 815932 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'lt_get_proc' together with a stack trace which includes the modules 'lt_send_truncpoint' and 'exec_dbcc' may be reported in the SAP ASE error log when the command 'DBCC SETTRUNC' or 'DBCC GETTRUNC' is executed. |
| 815945 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'prot_pcr_get_perms' followed by a stack trace that includes the modules 'rvm_dispatch' and 'rvm_cfgadm_check_access', may be reported in SAP ASE error log when granular permission is enabled and any Non-Volatile cache configuration command is executed using sp_nvcacheconfig, sp_nvbindcache or with sp_sysmon. See KBA 2671978. |
| 816000 | A 15101 message, "There is insufficient memory to allocate < n > bytes. Please increase configuration parameter 'messaging memory', or try again when there is less activity on the server." may be reported when a large value has been set for the configuration parameter 'messaging memory' and real time messaging queries are executed in multiple concurrent sessions. See KBA 2674952. |
| 816003 | Update the version of Jetty used for SAP ASE Webservices to Jetty 9.4.11. |
| 816009 | In rare circumstance, a 889 error, "Internal error. Contact SAP Technical Support for help. BCM thread found MASS < buffer_address > in database < database_name > ( < database_ID > ) and cache < cache_name > ( < cache_ID > ) in an unexpected state < value > ", may be reported if latch free indexes are created and the house keeper garbage collector task (HKGC) is enabled in the database. See KBA 2686353. |
| 816024 | In rare circumstances, when the Backup Server is shut down with "shutdown SYB_BACKUP", the SITE HANDLER for the SYB_BACKUP connection never gets released in SAP ASE. Then on a successful restart of the Backup Server, the SITE HANDLER is unable to connect to the Backup Server. This causes that all subsequent DUMP commands are hanging in the SAP ASE Server. SAP ASE traceflag 8024 (along with 3623) should be enabled to collect diagnostics in the SAP ASE log. See KBA 2669570. |
| 816025 | The message, "A fatal error has been detected by the SAP Java Virtual Machine: EXCEPTION_ACCESS_VIOLATION (0xc0000005)", together with the error message, "NTPCI__exit(1); Native Thread failed to unwind while attempting to shutdown the PCI", may be reported in the SAP ASE error log when loading sunec.dll on Windows platforms. See KBA 2687973. |
| 816028 | The description of parameter "--upgrade-ok" has been updated to make clearer what it does. |
| 816034 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE and also behind the last hole fixed by the Fix-Phase of imrslog boot-time recovery. |
| 816078 | In rare circumstances under an HADR setup, the coordinator process of SAP ASE RepAgent may hang in the module 'ra__ci_coordinator_waits_for_switch_ack' preventing the replication flow to continue. |
| 816107 | The active Rep Agent trace flags will now be reported in the SAP ASE error log when a Rep Agent is started. When no Rep Agent trace flag is active the message, "RepAgent( < dbid > ) no active traceflags.", will be reported. Otherwise the message, "RepAgent( < dbid > ) active traceflags: < TF1 > , < TF2 > , ..." will be reported. |
| 816203 | updatease fails to start the SAP ASE server if the master device file size is larger than 4GB. |
| 816290 | The number of free log pages in a database could be incorrectly reported by the sp_helpdb command, if the command ALTER DATABASE [LOG] OFF is used to remove pieces from the last database fragments and the command DUMP DATABASE WITH SHRINK_LOG is executed to remove the resulting fragment holes. |
| 816352 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'yylex' together with a stack trace which includes the modules 'sqlpars' and 'internal_sql' may be reported in the SAP ASE error log when many non-visible[*] characters appear in the query text following an SQL keyword, resulting in either a zombie task being created (in ASE 15.7 SP140 or ASE 16.0 SP03 PL04) or SAP ASE unexpectedly shuts down (in ASE 16.0 SP03 PL05 where a double signal is regarded as a fatal condition, but TF 2917 can be used to revert behaviour to the zombie task creation). See KBA 2686240. |
| 816355 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that there are some cross-log transactions whose sysimrslogs records are present on a sysimrslogs page that has a higher timestamp than that of the syslogs page containing the OQID rid. |
| 816407 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'obfuscate_ldapacpwd' together with a stack trace which includes the modules 'ua__setldapacct' and 'sa_ssladmin' may be reported in the SAP ASE error log when sp_ldapadmin is run with command set_access_acct as part of LDAP configuration. |
| 816409 | A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after having dropped a user database which is marked suspect and is On-Disk MVCC enabled. |
| 816425 | Memory leak in the PSS memory pool may be observed when there are multiple executions of 'set role with password on' in every other 'set proxy' session without a corresponding 'set role off'. See KBA 2656891. |
| 816450 | A 208 error, " < Table_name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", is reported when running any query involving global temporary table on an SAP ASE that is upgraded from a version between 16.0 SP02 GA and 16.0 SP02 PL06 HF1 to a higher version, and when the global temporary table is created with deferred table allocation set on the pre-upgraded version of ASE. See KBA 2680853. |
| 816487 | A new configuration option 'secondary signal handling' is introduced for SAP ASE which determines how the server handles secondary signals. The default value (1) makes the server shutdown on secondary signal. |
| 816520 | When no size is specified in the ALTER DATABASE command, the default size is incorrectly set to 512KB instead of 1MB for an Adaptive Server installation that is using a page size of 2KB. See KBA 2722663. |
| 816538 | In rare circumstances, SAP ASE may become unresponsive and a 15403 error, "No memory for Encrypted Columns Frag bucket pool growth", may be reported in the SAP ASE log when the configuration parameter 'max parallel degree' is set to value greater than 1. See KBA 2691726. |
| 816545 | Running sp_helpdb against a database can report usage as "-- unused by any segments --" when a database usage contains a user defined segment only. See KBA 2691648. |
| 816639 | An extra line may be printed between the header and the actual content in the sp_helpdb output. |
| 816643 | The message, "Invalid data found and rebuilt in segment accounting array for segment < segment_id > in database ID < database_id > .", may be reported in the SAP ASE error log following the recovery of a database. See KBA 2672135. |
| 816677 | A 10707 error, "java.io.FileNotFoundException: < jre > /lib/ext/ < jar_file > (Permission denied)" together with java stack trace may be reported when running a java method which implicitly invoke the loading of the extension < jar_file > . |
| 816700 | The sybmon command, 'print < address > -1 DES', may enter into an infinite loop and print the message, "txc_colid=0, txc_coffset=0, txc_indid=0", repeatedly when a memory dump is loaded in virtual map mode. |
| 816710 | In rare circustances, a process may hang in the module 'fio__p_sema' when trying to DUMP or LOAD a database if another Adaptive Server process has died due to a time slice error when reading or writing the dump history file. |
| 816729 | A 1244 error, "Could not find address lock at address < address > while trying to release it", may be reported when querying the monCachedObject MDA table. |
| 816738 | The total number of database pages stored in the dump header could not match the number of pages according to the database disk map stored in the same dump header if the database had trailing log holes and the end-user executed the command DUMP DATABASE WITH SHRINK_LOG | SHRINK_DATA | SHRINK_DATABASE. |
| 816752 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'bufsearch_cache_getlatch' together with a stack trace which includes the modules 'bt__fillrkey' and 'redo_bt_pagecompress', may be reported in the SAP ASE error log when LOAD TRANSACTION fails to redo some log record operations that involve cache-discrepant compressed index pages. See KBA 2696547. |
| 817092 | When a downgrade is attempted from ASE 16.0 SP03 PL04 or higher version to a lower version using the stored procedure sp_downgrade_esd, and the higher version contains SQL UDFs that do not reference tables, the downgrade will fail. See KBA 2722683. |
| 817180 | In rare circumstances, a client connection using SSL may hang with the message, "ssl_nrpacket: vsn < value > kpid < value > bytesleft 0 iostatus 4 incomplete header", reported in the ASE error log. This message will henceforth be purely informational and will not indicate an error. |
| 817283 | A 2847 error, "The object < sp_xxx > is not a SQLJ function. If this is a SQL function, specify owner.objectname", and a 14216 error, "Function < sp_xxx > not found. If this is a SQLJ function or SQL function, use sp_help to check whether the object exists (sp_help may produce a large amount of output)", will be reported when attempting to access SQL UDFs residing in sybsystemprocs whose names begin with "sp_" from any other database. See KBA 2714003. |
| 817431 | Update the SAP ASE integrated JREs to SAP JRE 8.1.046 and SAP JRE 7.1.060. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on Power 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Solaris on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP03 PL06, ASE SP03 PL06, SP03 PL06, 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)