/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) 15.7 SP141. 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 |
|---|---|
| 477889 | When the Rep Agent configuration parameter 'trace log file' is changed while Rep Agent is running, the new value isn't dynamically taken into account. |
| 650665 | In rare circumstances the message "Current process infected with signal 11 (SIGSEGV)" in the module 'norm3_expr' together with a stack trace which includes the module 'norm3__process_case' may be reported in the error log when a query includes a derived table and has a DISTINCT clause with a SUBQ in resdom and has an OJ. See KBA 2413073. |
| 694618 | The message, “The log page count in DBINFO for database < name > is inaccurate because dbi_freelogpages_at_ckpt < value > should be less than dbt_logsize < value > . Run DBCC TABLEALLOC(syslogs, full, fix) on this database in single-user mode to make the counts consistent again.”, may be reported in the SAP ASE error log during a database CHECKPOINT to help diagnose the origin of a 3475 error, “There is no space available in SYSLOGS to log a record for which space has been reserved in database < value > (id < value > ). This process will retry at intervals of one minute.”. |
| 732697 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sscan_copy_init' together with a stack trace which includes the modules 'onlutl_getTS_for_lpage' and 'pg_oamscan_nextpage' may be reported in the SAP ASE error log when running REORG REBUILD ONLINE after executing a 'drop column with no datacopy' on a LOB column. |
| 741482 | The error message, "Page ' ' (partition ID = ' ') belongs to DOL table ' ' which does not have pages linked. Cannot process this command.", raised if the page is DOL index leaf page, now enhance dbcc pglinkage() that it can display the linkage of DOL index leaf page. See KBA 2739076. |
| 748461 | The message "current process infected with 11 (SIGSEGV)" in the module 'open_byname' together with a stack trace which includes the modules 'col_open_range' and 'vu_redefine' may be reported in the SAP ASE error log when during the execution of a stored procedure a view statement requires redefinition as it was compiled with the configuration option 'procedure deferred compilation' enabled. See KBA 2017991. |
| 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. |
| 756343 | The error message, "ORA-01036: illegal variable name/number", may be reported when executing a query against a proxy table mapped to Direct Connect for Oracle that uses SAP ASE keyword identifiers as the object names. |
| 774449 | Error 702 "Memory request for < memory size > bytes exceeds the size of single page of < page size > bytes." can be raised during querying a table which has more than 4100 partitions and MDA is turned ON. |
| 780441 | With XOLTP workset query, if "dynamic SQL plan pinning" is enabled, then after enabling or disabling "streamlined dynamic SQL", an infected with signal 11 (SIGSEGV) stacktrace in routine crp_vardec() with other routines including sqt_reparse() and tdsrecv_dynamic() may be reported in the SAP ASE error log. See KBA 2722587. |
| 780764 | The error message, "Current process infected with signal 11 (SIGSEGV)", followed by the stack trace involving the modules 'ra__coord_driver' and 'ra_schema_dealloc_cache' may be reported against the Replication Agent Coordinator Thread when Replication Agent is configured for Multiple Paths Replication and Multiple Scanners, and it is stopped by executing sp_stop_rep_agent. |
| 781187 | The error, "ct_connect(): directory service layer: internal directory control layer error: Requested server name not found", will be raised when trying to DUMP or LOAD an in-memory database using LDAP as directory service. |
| 781679 | The time stamp that is used to generate the dump file names during the execution of DUMP DATABASE / TRANSACTION USING CONFIG commands, that are typically named using the format 'database_name.dump_type.date-timestamp.stripeID', has been enhanced to ensure they are unique. See KBA 2693916. |
| 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. |
| 785795 | The message, "Current process infected with signal 11" in the module 'Gbitstr::Gbitstr' followed by a stack trace that includes the module 'LeAPScanContext::LeAPScanContext', may be reported in the error log when executing queries when the SAP ASE host machine is low of free memory or swap space. Some queries may cause memory leak against SAP ASE 16.0 SP01 and later if the configurable parameter 'enable monitoring' is set. Queries referencing partitioned tables may leak more memory than using non-partition tables for this issue. See KBA 2187216. |
| 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. |
| 787661 | When a process querying MDA tables hits an "infected with signal 11 (SIGSEGV)" error, SAP ASE server may shut down with a message like "Spinlock [spinlock] at address [address] owned by [kpid]". See KBA 2764646. |
| 790473 | The command DBCC CHECKSTORAGE() can report the error 'Compressed length ( < value > ) is too big. File probably corrupted.' in the SAP error log, if executed on an archive database that is created on a compressed dump. |
| 792295 | In rare circumstance, error 15946, "Invalid column length %d found for column, column ID %d, row ID %d, page number %u, partition ID %d. The length is greater than the expected maximum column length %d.", may be reported by dbcc checkdb() or dbcc checktable() after some columns are dropped using "alter table ... with no datacopy". |
| 792561 | Updateable cursor scans do not apply on queries with sub-selects such as 'EXISTS' and 'NOT EXISTS' sub-queries. This restriction has now been relaxed when trace flag 11015 is enabled. See KBA 2246480. |
| 793970 | An infected with signal 11 (SIGSEGV) may occur when executing some sybmon commands, such as SQLTEXT, QUEUE, MMGRPOOLS, if the dump file being analyzed does not contain the procedure cache. |
| 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. |
| 798983 | In rare circumstances, the message "timeslice -501, current process infected" in the module 'kbfalloc' together with a stack trace which includes the modules 'itl__realloc_aut_dict' and 'itl_au_update_xfer_mark' may be reported in the SAP ASE error log when BCP is executed with multiple threads. |
| 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. |
| 799128 | Under rare circumstances, a 821 error message, "Attempt to unhash buffer in cache 'tempdb_cache' at ' < address > ' with a buffer pageno of ' < x > ' and database id ' < x > ' with HASHED status set failed - buffer was not found. 'Page pointer = < address > , pageno = < x > , status = < x > , ptnid = < x > , indexid = 0, level = 0'." may be reported in the SAP ASE errorlog when a query is killed while creating a worktable for reformatting. See KBA 2430458. |
| 800348 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘ upwakeup’ together with a stack trace which includes the modules ‘ kbctMain’ and ‘ krtctskRun’ may be reported in the SAP ASE error log. See KBA 2769786. |
| 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*'. |
| 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. |
| 801343 | Incorrect statistics may be generated when using the "with hashing" option with UPDATE STATISTICS. See KBA 2359108. |
| 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. |
| 803087 | The message "current process infected with 11 (SIGSEGV)" in the module 'CgGenLava::CGConsScanOp' together with a stack trace which includes the modules 's_compile_stmt' and 'GenLava' may be reported in the SAP ASE error log when executing a query that use a non-correlated subquery which contains an IN clause. See KBA 2383992. |
| 803153 | The message, “Current process infected with signal 11 (SIGSEGV)” in the module ‘s_free’ followed by a stack trace that includes the modules ‘metrics_dump’, ‘metrics_proc_dump' and 'proc__deallocmem', may be reported in the SAP ASE error log when there is not enough space to allocate a worktable and an error occurs during cleanup while having "enable metrics capture" enabled. See KBA 2384910 |
| 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. |
| 803837 | Under rare circumstances SAP ASE may hang when a spid that is writing log records is killed with the force option. |
| 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. |
| 804695 | The message, "xpserver is using enhanced security", is repeatedly reported in the SAP ASE error log. See KBA 2412523. |
| 805133 | On Linux platform, under rare circumstances a connection to SAP ASE may hang after the client issues a cancel. |
| 805275 | SAP ASE server will disable ASE_JAVA functionality if the jvm.wl file is missing, and the message 10762 together with the detailed reason will be reported in SAP ASE error log. This is to improve the default security should the jvm.wl authorization file be accidentally removed. |
| 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. |
| 806885 | In rare circumstances, the message, "Caught an Unknown exception in handleRPC" may be reported in the Webservices log when executing "exec sp_webservices 'add'" with a duplicate service name. See KBA 2710519 |
| 807307 | A 3606 message, "Arithmetic overflow occurred", may be reported when executing sp_configure " < param_name > ", 0, " < value > {K|M|G}" with a < value > greater than or equal to 2048G. |
| 807420 | Msg 247, Level 16, State 1: "Arithmetic overflow during implicit conversion of UNSIGNED INT value " < value > " to a INT field" cat be seen when running the sp_spaceusage stored procedure to display syslogs. See KBA 2776772 |
| 808040 | KBA 2573343. In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'pci_killslot' together with a stack trace may be reported in the SAP ASE error log during a forced shutdown (shutdown with nowait). |
| 808297 | The execution of sp_dump_history @operation = 'purge', @status = 'fail' may delete all rows from the dump history file mistakenly. See KBA 2475482 |
| 808635 | A 3944 error, "Attempt to BEGIN TRANSACTION in database < dbname > failed because the database is in standby access mode", may be reported during DBCC CHECKDB or DBCC CHECKALLOC execution if the database is in standby access mode. See KBA 2458617. |
| 808897 | In rare circumstances, a 706 error, "Process < value > tried to remove PROC_HDR < value > that it does not hold in Pss." together with a stack trace which includes the modules 'rm_prochdr' and 'memfree' may be reported in the SAP ASE error log when a process is killed. See KBA 2171618. |
| 809421 | In rare circumstances, after a column datatype of a Data-Only-Locked table is changed from INTEGER to CHAR/VARCHAR where the column is a part of a clustered index key, the 3121 error, "Index < table > .PK_ind (objid= < objid > , indid=2) may be invalid. It uses CHAR or VARCHAR columns in its key and was created under a different sort order ID ( < sort-order-id > ) or charset ID ( < char-set-id > ) than the ones on this server (SortOrd= < sort-order-id1 > , CharSet= < char-set-id1 > )", may be reported when a dump of the database is taken, and then loaded and an ONLINE DATABASE command is executed. See KBA 2755798. |
| 809793 | SAP ASE applies the 'allrows_mix' optgoal instead of the current session level optgoal at the query level if an invalid user defined goal is sent with the abstract plan. |
| 810647 | A 806 error, "Could not find virtual page for logical page < n > in database ' < dbname > '", may be reported in the SAP ASE log when updating a base table column used in a materialized view with 'IMMEDIATE REFRESH' if the base table has a TEXT and/or IMAGE column(s). See KBA ##2531239 |
| 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. |
| 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. |
| 811135 | After an upgrade, a 10330 error, "INSERT permission denied on object < obj_name > , database < db_name > , owner < username > ", may be reported when procedures are executed by a user without explicit permissions on the underlying objects ( only partitioned tables) in the procedures. See KBA 2560832. |
| 811265 | Incorrect run sizes for the data caches may be reported by sp_sysmon with the "cache wizard" option. See KBA 2540661. |
| 811296 | Incorrect HitCount and NumInserts may be reported in the monStatementCache MDA table. See KBA 2548423. |
| 811490 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'js__expirejobs' (or js__collectjobs or js__add_dup_callout) together with a stack trace which includes the modules 'jobscheduler' and 'js__chores' may be reported in the SAP ASE error log when the timeout parameter for a job is set to a non-zero value and the configuration option 'enable job scheduler' is enabled. |
| 811667 | In rare circumstances, if concurrent inserts are taking place into a Data Only Locked (DOL) table while REORG DEFRAG is executed, some inserted rows may not be visible after REORG DEFRAG is completed. See SAP note 2777678 |
| 811701 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 's_handle' together with a stack trace which includes the modules 's_recompile' and 'execproc', may be reported in the SAP ASE error log when creating a Light Weight Procedure (LWP) after a 2812 error, "Stored procedure ' < 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. See KBA 2471704. |
| 811723 | In rare circumstances, the message, "JZ0R1: Result set is IDLE as you are not currently accessing a row." may be reported in the Webservices log file. See KBA 2559676 |
| 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'. See KBA 2755790. |
| 811764 | A 644 error, "Index row entry for data row id < page#, row# > ) is missing from index page < value > of index id < value > of table < name > in database < name > . Xactid is < page#, row# > ). Drop and re-create the index." together with a stack trace that includes the modules 'bt_delete' and 'row_delete' may be reported in the SAP ASE error log on a non-clustered index when DELETE commands are executed and the housekeeper task is performing aggressive garbage collection concurrently. See KBA 2523141. |
| 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. |
| 812173 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_fill_and_send_monProcessWaits' together with a stack trace which includes the modules 'conn_hdlr' and 'kisignal' may be reported in the SAP ASE error log when the monProcessWaits MDA table is queried. See KBA 2591095. |
| 812256 | In rare circumstances on a heavily-loaded multi-engine system, a 3914 error, "Illegal internal transaction status. This is an internal system error", may be reported in the SAP ASE error log when the configuration parameter 'number of open objects' is under configured whereby SAP ASE reuses a metadata descriptor whose object had statistics information to flush on disk first. See KBA 2575197. |
| 812273 | An infected with signal 11 (SIGSEGV) error followed by a stack trace that includes the modules 'smd_sample_server' and 'sm_exec_command' may be reported in the SAP ASE error log when executing the sybmon "sample" command when "allocate max shared memory" is set as DEFAULT (0). |
| 812328 | In rare circumstances, a 12311 error, "Internal error: address lock request on page < page number > of index id < index id > of table < table name > (id = < object id > ) in database < database name > failed with status < value > . No need to drop the index.", may be reported when running INSERT, UPDATE, or IMRS PACK operations and the transaction rollback. See KBA 2577215. |
| 812393 | An erroneous message, "Assertion (upd_ok) failed" in the module 'altdb__check_fwd_rows', may be reported in the SAP ASE error log if DBCC DBREPAIR with 'redo_shrink' option is executed to repair a partially completed shrink database and the diagserver binary is in use. It is a false assertion message from the diagserver, data is NOT corrupted. NO symptoms are reported in dataserver. |
| 812496 | A 8015 error, "Adaptive Server has truncated parameter number 3 passed to rpc 'as_db_dam' on server < server_name > . The remote server does not support character or binary data wider than 255 bytes.", may be reported when DUMP DATABASE is executed in server passthrough mode and the database option 'allow incremental dumps' is enabled. |
| 812517 | Sometimes the SAP ASE error log may get filled up with warning messages like "WARNING: Memory protection change failed: Invalid argument, address" when trace flag 767 is enabled. |
| 812690 | sp_sysmon reports rows inserted for Fully Logged APL Heap Table from non-logged inserts such as worktables and materialized tables like sysprocesses and sysmonitors. See KBA 2586495. |
| 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. |
| 813075 | In rare circumstances, 2601 error, "Attempt to insert duplicate key row in object < table_name > with unique index < index name > ", may be reported on the standby SAP ASE server, when running an UPDATE command on a compressed APL table that has a primary key constraint on the primary SAP ASE server. See KBA 2608496. |
| 813096 | In rare circumstances, DUMP and LOAD operations may not succeed when using an SSL connection between SAP ASE and the SAP ASE backup server on the Windows and AIX platforms. |
| 813114 | Sybmon "status" and "engines" commands report the wrong engine status as "Not Halted" for memory dump generated by either "DBCC MEMDUMP" command or manual command "memdump" with engine halt option. See KBA 2596784. |
| 813237 | A 921 error, "Database < name > has not been recovered yet - please wait and try again.", may be reported when USE < database > is executed on a Single Instance Database after SAP ASE Cluster Edition is started. See KBA 2598706. |
| 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. |
| 813401 | Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled. |
| 813501 | In very rare circumstances, if CREATE INDEX and at least two updates are run in a same batch, then concurrent updates, affecting the same set of rows, qualified by the second update onwards, might succeed wrongly. |
| 813535 | On heavily loaded systems, spinlock contention may be observed on statement cache when multiple INSERT statements with similar data of numeric datatype are present. Use the run time trace flag 11013 to enable the use of a single cached plan for multiple INSERT statements. |
| 813580 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'omni_ct_cancel' or 'uctSetIssuedCnt' or 'ct_poll' together with a stack trace which includes the module 'omni_ct_cancel' or 'omni_ct_close' may be reported in the SAP ASE error log when the SAP ASE configuration parameter 'cis idle connection timeout' is turned on. See KBA 2697042. |
| 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. |
| 813689 | In a HADR environment, under rare circumstances, a planned failover issued using RMA command sap_failover may fail and the message, "split brain check refused to allow this server to become Primary", may be reported in the SAP ASE error log. |
| 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. |
| 813718 | When a non DBA user with proper privileges runs a homogenous batch update using a Java client, the errors, "JZ0BE: BatchUpdateException: Error occurred while executing batch statement: The dynamic statement '*sh1497365668_1600677172ss*' could not be found. This may be due to insufficient metadata descriptors. Increase the serverwide 'number of open objects' parameter or the 'procedure cache size' parameter" and "JZ0BE: BatchUpdateException: Error occurred while executing batch statement: A query plan cannot be generated for DML command executed with homogeneous batch parameters. The batch was aborted", may be reported at the Java client. See KBA 2611208. |
| 813752 | Diagnostic tracing for "SSL handshake failed" errors has been added. The diagnostic tracing can be enabled through traceflag 7867. See KBA 2633020. |
| 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. |
| 813886 | Under rare circumstances, a connection may hang after receiving a cancel request from the client. See KBA 2633664. |
| 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. |
| 813983 | A 515 error, "Attempt to insert NULL value into column 'seqnum', table '#result_body'; column does not allow nulls", may be reported if sp_helpartition is executed, after executing ALTER TABLE DROP COLUMN WITH NO DATACOPY followed by ALTER TABLE MOVE PARTITION. |
| 814029 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'iocmResize' together with a stack trace which includes the modules 'cfg_notify_iotasks' and 'cfg__notifyconfig' may be reported in the SAP ASE error log when the value of config parameter "number of disk tasks" or "number of network tasks" is changed at run-time and then reverted back to the earlier value. |
| 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. |
| 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. |
| 814206 | On platforms other than Linux, when the compatibility mode is enabled, a 5846 error, "Illegal value '0' specified for configuration option ' < config name > '. The legal values are between ' < lower limit > ' and ' < upper limit > '", may be reported even when a correct value is provided. |
| 814240 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'CtlibRemoteAccess::getSubstValue' together with stacktrace that includes the moedules 'CtlibRemoteAccess::getColumnValues' and 'RPCRemoteAccess::getNext', may be reported in SAP ASE error log when 'granular permission' is enabled and a query, involving user created built-in functions and proxy tables, is executed. |
| 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. |
| 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 |
| 814598 | The output of replicate() is truncated to 1024 characters when the SAP ASE configuration option "enable literal autoparam" is enabled. See KBA 2722653. |
| 814613 | The message, "rapidlog unable to open file ..." and "timeslice -1501, current process infected" followed by a stack trace that includes the module 'worcap_packet', may be reported in the SAP ASE error log when capturing a workload. See KBA 2710120. |
| 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. |
| 814712 | On Windows 32bit (nt386) platform, SAP ASE configured with 16K pagesize and default max memory, fails to boot and the message "The value of the 'max memory' parameter (72704) defined in the configuration file is not high enough to set the other parameter values specified in the configuration file. 'max memory' should be greater than the 'total logical memory' ' < value > '." may be reported in the SAP ASE log. |
| 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. |
| 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. See KBA 2748289. |
| 814891 | The DBINFO meta-data may contain wrong information after a cross-database DUMP and LOAD from an SAP ASE 16.0 SP02 to 16.0 SP03 release. See KBA 2710240. |
| 814903 | The SAP ASE Backup Server on the Windows platform will abort after raising an internal assertion if the debug version of the SAP open server library (e.g. as found in the $SYBASE\$SYBASE_OCS\DLL\DEBUG directory) is used. |
| 814910 | In rare circumstances, the message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation" or an "infected with 11 (SIGSEGV)" 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. See KBA 2788678. |
| 814921 | An 16367 error, "EXECUTE AS OWNER procedures cannot be created by an alias or with the SETUSER command when the procedure has SQL statements that reference objects across databases. Create the procedure from a non-impersonated session.", may be reported in the SAP ASE error log when an impersonating user tries to execute a cross-database stored procedure which was created with the 'deferred name resolution' configuration enabled. See KBA 2755255. |
| 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. See KBA 2747779. |
| 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. |
| 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'. |
| 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 |
| 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". See KBA 2748316. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 815569 | The configuration file offset record in the decompressed dump is not correct and hence sybmon cannot extract the original configuration file. |
| 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. |
| 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 > ". |
| 815706 | On Windows platforms, the message, "Parameter 'start address' (number 1) to DBCC command 'bytes' has invalid value/type." may be reported in client console, or the printed address doesn't match the specified address in DBCC BYTES command when DBCC BYTES (address, length) is executed. |
| 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. |
| 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. |
| 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. |
| 815867 | A 100015 soft fault (page loop error) may be reported by sp_dbcc_faultreport after executing a DBCC CHECKSTORAGE on a database that contains about 15000 syspartitions rows. See KBA 2670254. |
| 816001 | KBA 2754612 - The message, "The stored procedure < sproc_name > has an old format and cannot be used internally by Adaptive Server until it has been upgraded. You can execute DBCC UPGRADE_OBJECT( < sproc_name > ) to avoid this.", may be reported during an upgrade of SAP ASE to a higher version due to the system stored procedures being created with 'deferred name resolution' enabled in the pre-upgrade version. |
| 816003 | Update the version of Jetty used for SAP ASE Webservices to Jetty 9.4.11. |
| 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. |
| 816102 | The message "current process infected with 11" in the module 'norm3_expr' together with a stack trace which includes the modules 'norm3__process_case' and 'crcpc_norm' may be reported in the error log when computed columns is queried in a SELECT statment. See KBA 2413073. |
| 816125 | A 11138 error, "Failed to create role < role_name_992 > , because this exceeds the maximum number roles limit of '1024'. Please delete roles you don't need and rerun your command.", may be reported when a user tries to create the 992nd role. See KBA ##2679595 |
| 816272 | The system stored procedure 'sp_activeroles' may show only the latest granted user defined predicated role, even if multiple user defined predicated roles are granted to the login, when SAP ASE configuration option 'enable predicated privileges' is enabled. See KBA 2684433. |
| 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 invisible 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. |
| 816400 | In rare circumstances, the progress status message, 'Backup Server: 4.188.1.1: Database < database_name > : < value > kilobytes ( < value > %) DUMPED.', may be truncated unexpectedly when DUMP DATABASE is executed. See KBA 2687371. |
| 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. |
| 816425 | A 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. |
| 816544 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubfreef' together with a stack trace which includes the modules 'cm_increase_cache_size' and 'cfg__updatecache', may be reported in the SAP ASE error log when increasing the size of an inmemory cache. See KBA 2691539. |
| 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. |
| 816571 | The message, "Assertion (!keylength || !statp- > st_cache.st_length || ((statp- > st_descending ? -1 : 1) * compare_value( stu_null_datatype(histp- > st_steps. st_dt.st_idatatype), statp- > st_cache.va.st_buffer, statp- > st_cache.st_length, keybufp, keylength)) > = 0)", together with a stack trace which includes the module 'ups_histogram_gather' may be reported when creating a unique index on a CHAR column on a partition table and the diagserver binary is in use. |
| 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. |
| 816715 | A memory leak in the Backup Server may be seen every time a DUMP of an in-memory database is taken. |
| 816716 | A 11030 error, "Execution of unknown type ptncond_xxx_0 failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo.ptncond_xxx_0.", can be seen after an upgrade when a roundrobin partitioned table with a clustered index has an index key with bigdatetime/bigdate/bigtime datatype. See KBA 2697077. |
| 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. |
| 816941 | A 9235 error, "Could not allocate memory for gettrunc. Please retry gettrunc() later when more memory is available, or re-configure the server with a larger procedure cache.", will be reported when the command DBCC GETTRUNC fails to allocate memory. The error message wrongly refers to the procedure cache and should instead indicate the need to increase the value of the parameter 'replication agent memory size'. |
| 816992 | When a DUMP or LOAD command using an SAP ASE backupserver API library is aborted from the client, the call to the module 'syb_close' that will close the stripes gets the mode SUCCEED_ON_CLOSE instead of ABORT_ON_CLOSE. The result is that the API library cannot know that the operation was aborted. See KBA 2705604. |
| 817072 | The jobs scheduled by the SAP ASE Job Scheduler does not expire after the timeout period even when the 'default_timeout' for the job is set to a non-zero value in the absence of 'timeout' for the scheduled job. See KBA 2748408. |
| 817220 | Under rare circumstances, a spid involving remote I/O and the back trace of that spid using 'dbcc stacktrace( < spid > )' includes the module omni_ct_connect, usctconnect and ksctsuspend, may not hit timeslice error if there is any issues in the module ksctsuspend. |
| 817243 | The 632 error, "Attempt to move memory with an incorrect length of < size > . Maximum allowed length is < max_size > .", with state 2 does not provide diagnostic info. See KBA 2776092. |
| 817400 | In rare circumstances, random failures with the message "current process infected with signal 11 (SIGSEGV)" together with a stack trace may be reported in the SAP ASE error log when SELECT queries were earlier executed with the reformat strategy applied and the reformat worktable had rows whose size was unexpectedly bigger than the current Adaptive Server configured page size. See KBA 2763915. |
| 817401 | Using KILL < spid > WITH FORCE on an idle process can result in the process remaining alive and reported by sp_who despite the connection is released. See KBA 2719233. |
| 817472 | When a database is extended using asynchronous initialization and the new pages occupy a database range that has been asynchronously initialized before and later dropped using ALTER DATABASE OFF, some of the pages in the new fragment could remain uninitialized. |
| 817535 | In rare circumstances, the message, "Invalid OAM page (OAMINVALID_1) stat 4: pageno= < value > , sdes_stat= < value > , pstat= < value > , dbid=5, etc.", together with a stack trace that includes the modules 'th_accounting', 'th_sleep_on_lct' and 'terminate_process', may be printed in the SAP ASE error log when a SELECT query that requires a work table to be created is killed. |
| 817545 | The error message, "ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect", followed by a stack trace that includes the modules 'omni_exec_immediate', ' omni_sync_roles' and 'set_role', may be reported in the SAP ASE error log when executing SET ROLE REPLICATION_ROLE ON in the context of proxy objects. See KBA 2786327. |
| 817593 | The MDA table monDeviceSpaceUsage does not return any rows for database devices that are created on block device. See KBA 2728041 |
| 817606 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'metrics_proc_dump' together with a stack trace which includes the modules 'd_flushmetrics' and 'exec_dbcc', may be reported in the SAP ASE error log when executing sp_metrics 'flush' and the procedure cache is being cleaned up in parallel. See KBA 2730139. |
| 817619 | The message, "Security Control Layer's memory allocation routine returned an error.", and the message, "SCL error in function: sec_setup. Operation: sec_memalloc().", are reported in the SAP ASE error log when the memory pool used for external authentication such as Kerberos becomes fragmented. See KBA 2732809. |
| 817620 | When LOAD TRANSACTION < database_name > WITH LISTONLY = LOAD_SQL is executed, SAP ASE may incorrectly report the option WITH PASSWD for a transaction dump that was dumped without password protection, if a subsequent transaction dump was taken with password protection. |
| 817629 | Under rare circumstances, a 1608 error, "A client process exited abnormally, or a network error was encountered" together with timeslice error followed by a stack trace which includes the module 'LopSubqAttach::GroupSimilarSubqNode' may be reported in the SAP ASE error log when a nested subquery is executed. See KBA 2727908. |
| 817682 | A 18302 error, "User < login name > is not a valid user in the < db name > database.", may be reported even when a user having sa_role executes the stored procedure sp_dbcc_faultreport. See KBA 2731983. |
| 817734 | SQL statement replication involving quoted identifiers may cause the SAP SRS DSI to shut down after receiving an SAP ASE error indicating a syntax error, or after hitting SAP SRS error 5186, "Row count mismatch for the SQL Statement Replication command executed on ' < servername > . < dbname > '.". See KBA 2721403. |
| 817868 | In rare circumstances, DUMP DATABASE or DUMP TRANSACTION will sleep indefinitely when sp_dump_history is run with the 'purge' option at the exact same time as the DUMP and the configuration parameter 'enable dump history' is enabled. See KBA 2737615. |
| 817869 | In rare circumstances, a 102 error, "Incorrect syntax near ';'.", followed by a 111 error, "CREATE PROCEDURE must be the first command in a query batch.", and a 156 error, "Incorrect syntax near the keyword 'END'.", may be reported when CREATE PROCEDURE is executed and the stored procedure text includes a large number of invisible characters. See KBA 2716155. |
| 817933 | On Windows platforms, the message, "java.io.FileNotFoundException: < pca_jvm_tmp_dir > \ < file_name > (Access is denied)", together with a Java stack trace may be reported when the IO operations are performed with Java IO API and the configured pca_jvm_tmp_dir is not accessible. |
| 817964 | A 11060 error, "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 the execution of a SELECT query that references a view with tables that were dropped, re-created, or altered. See KBA 2791952. |
| 817974 | If the configuration parameter "enable concurrent dump tran" is set to 1, SAP ASE may allow a transaction dump to be loaded on top of the wrong full database dump, if it was generated concurrently with it, and the transaction dump ends between the time the full database dump started and the dump instant time was taken. Alternatively, a 4305 error, "Specified dump file ' < filename > ' is out of sequence.", may be incorrectly reported when trying to load a transaction dump generated after the concurrent transaction dump finished. |
| 818020 | KBA 2752182 - In rare circumstances, the message, "Failed to execute the threshold procedure for database < dbid > , segment 2, free space < num > ." or the message, "Failed to find specified threshold in threshold cache on instance 1 for database mld ( < dbid > ), segment 2, free space < num > . Use 'dbcc thresholds' to see the threshold cache contents.", may be printed in the SAP ASE error log when multiple tasks hit the threshold at the same time. This mainly happens for mixed log/data databases. |
| 818168 | A 1526 error, "Sort failure. The configure size for data cache ( < name > ) is not sufficient to handle the sort buffers ( < value > ) requested. Please reconfigure the data cache or sort buffers and try the command again.", may be reported during the execution of a query with a non-unique state value which prevents us to identify the root cause of the error. See KBA 2748397. |
| 818225 | The SYBMON extract command can extract the errorlog and configuration file successfully but the file content is invalid. See KBA 2749964. |
| 818231 | In rare circumstances, using the 'setLong' method in a PreparedStatement may result in an incorrect value being assigned to a BIGINT datatype when the Java code is executed inside SAP ASE using the SAP ASE's internal sybase.asejdbc.ASEDriver driver. See KBA 2748353 |
| 818245 | A 7625 error, "Audit table number ' < value > ' is invalid." with state 3, prints a incorrect value for the audit table number. See KBA 2751731. |
| 818264 | A stored procedure which uses multiple IF, ELSE, or WHILE clauses to conditionally execute DML statements may have the stored procedure text incorrectly saved in syscomments. See KBA 2749949. |
| 818321 | The message, "FATAL UNHANDLED EXCEPTION: signal < number > hit while handling a previously hit signal. The server cannot continue and will shut down.", may be reported in the SAP ASE log when an external signal is send to ASE e.g. via OS kill command. See KBA 2682383. |
| 818324 | Under rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'kstcpnetctlrNcheckQuit' together with a stack trace which includes the modules 'ncheck_checksocket' and 'krtctskException' may be reported in the SAP ASE error log and SAP ASE may become unresponsive. See KBA 2757868 |
| 818327 | On heavily loaded systems, spinlock contention on SSQLCACHE_SPIN may be observed on statement cache when a prepared statement performing INSERT statements with numeric datatypes (or similar) are present and the option DYNAMIC_PREPARE is set to FALSE. SAP KBA 2770344 |
| 818370 | In rare circumstances the message, “segmentation fault (core dumped)”, may be reported by the SAP Backup Server on Linux platform when a DUMP DATABASE is run as the result of possible memory leaks that could occur during the dump. |
| 818373 | Under rare circumstances, a 12583 error, "Unable to log a record in database < name > (id < value > ) due to internal error -8.", may be reported when a session that is writing log records is killed with the WITH FORCE option. See KBA 2790981. |
| 818438 | sp_shmdumpconfig reports incorrect numbers for Data Caches & Server Memory fields. It adds half the combined Data Caches size to Server Memory field. See KBA 2755150. |
| 818469 | A 4325 error, "The specified recovery date ( < value > ) is not between the start ( < value2 > ) and end ( < value3 > ) date.", may be reported when LOAD TRANSACTION WITH UNTIL_TIME= < Point_In_Time_Recovery > is executed and the transaction dump when taken has a dump instant value that is later than the specified PITR value. |
| 818746 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dso_resgov_timlim' may be reported in the SAP ASE error log when a task disconnects at the same moment a limit is crossed and the limit action is enforced. SAP KBA 2767573. |
| 818885 | When running sp_sysmon using the appl or appl_and_login option, the application or application- > login section reports inaccurate Disk and Network I/Os when there are multiple sessions with the same application or application- > login pairing. See KBA 2776095. |
| 818953 | The message "ELC_VALIDATION_ERROR: Page address not aligned to memory page size.", followed by "Current process infected with signal 11 (SIGSEGV)" in the module 'subp' together with a stack trace which includes the modules 's_execsetvar' and 'subparams' may be reported in the SAP ASE error log when prepared INSERT statements are executed. See KBA 2774710. |
| 818972 | The message "current process infected with 11" in the module 'lt_run' together with a stack trace which includes the modules 'lt_send_row', 'mda_populate_monMemoryUsage', 'mdarpc_exec' and 'execrpc' may be reported in the error log when the monMemoryUsage MDA table is queried remotely as an RPC for a proxy table. See KBA 2781904. |
| 818978 | A 7124 error, "The offset and length specified in the READTEXT command is greater than the actual data length of < value > ." may be reported when running "readtext" with the "size" or "offset" parameter datatype different than integer. See KBA 2778603. |
| 819260 | A 911 error, "Attempt to locate entry in sysdatabases for database '' by name failed - no entry found under that name. Make sure that name is entered properly.", may be reported when a prepared statement issuing CHECKPOINT < database_name > is executed. See KBA 2791971. |
| 819273 | SAP Adaptive Server dataserver process leaks O/S memory when the built-in xmlextract() is executed. See KBA 2806756. |
| 819302 | The upgrade items for zeroing the columns 'imrslogptr' and 'imrsloglastptr' in table 'master.dbo.sysdatabases' and the column 'schemaid' in table 'sybsecurity.dbo.systypes' may be missed when upgrading an Adaptive Server installation from 16.0 SP02 PL07 or 16.0 SP02 PL08 to 16.0 SP03 PLxx. |
| 819600 | If the '#Configure New Servers' configuration in rs file is not specified, silent installation mode should not perform the relevant configuration operation, but the current program will judge that the configuration is required without the user specifying it, resulting in configuration error. |
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 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition
Keywords
CR, CR List, ASE 15.7 SP141, ASE SP141, Adaptive Server Enterprise, Fix, Patch, Error, Bug, SP141 , KBA , white-list , white , white space character , 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)