SAP Knowledge Base Article - Preview

3041421 - Targeted CR List for ASE 16.0 SP04 PL01

Symptom

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 SP04 . 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 NumberDescription
489340 When inserting data into a TIMESTAMP column and the source data is the result of an aggregate built-in, SAP ASE will incorrectly insert into this column the current timestamp value rather than the source data. See KBA 2408246.
538343 When UPDATE STATISTICS is executed an incorrect value of extent0pgcnt column may be stored in the system table systabstats.
683438 DBCC EXTENTDUMP is enhanced to report the OAM page number of an extent.
705151 The execution of SELECT count(*) on very large tables may return an inaccurate or negative value. See KBA 2056252.
774152 Whenever threadpool size is reduced using ALTER THREAD POOL command, it leads to 'kernel resource memory' leak. See KBA 2750513.
792860 The system stored procedure sp_opt_querystats is enhanced to support user defined optgoals and transaction isolation level when reporting information about the optimization of a query.
799240 The message, “Current process infected with signal 11 (SIGSEGV)”, together with a stack trace which includes the modules ‘altdb__divide_diskmap’ and ‘altdb_shrink’ may be reported in the SAP Adaptive Server error log when ALTER DATABASE command with the "off" option is executed to shrink a database. See KBA 2323410.
802123 In rare circumstances, when one or more data or log devices are corrupted, dropping a database using such device(s) may cause the session to be terminated and may corrupt the master database.
804443 An incorrect result set may be returned during the execution of a SELECT query which includes an ORDER BY clause on an expression and ROWS OFFSET and LIMIT options are also in use. See KBA 2408819.
818435 In rare circumstances, on IBM systems LOAD operations may fail without a clear evidence that shows where the failure starts. Additional diagnostics have been added to the Backup Server to trace the events during the LOAD command execution accessible via trace flag -D16. See KBA 2757065.
818726 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”, may be reported when a SELECT query is executed using an in-memory database while its associated template database is renamed using sp_renamedb. See KBA 3009019.
819834 A 9992 error, "The actual number of rows ( < row-count > ) in DOL datapage < page-id > , partition ID < partition-id > , and count of #rows - 'nextrno' - < row-count > in the page header, do not match.", a 12308 error, "Internal error : Invalid row id (Row < row-id > , Page < page-id > ) encountered in the table ' < table-name > ' in database ' < database-name > '.", a 2512 error, "Table Corrupt: Cannot find the specified row number < row-id > , in index page < page-id > , partition ID < partition-id > , on data page < page-id > .", and a 7928 error, "Index < index-name > is not consistent; found < row-count > leaf rows but < row-count > data rows. Drop and recreate the index.", may be reported by DBCC CHECKTABLE when a Data Only Locked (DOL) data page is found to be invalid. See KBA 2889757.
820149 A 10353 error, "You must have any of the following role(s) to execute this command/procedure: 'sa_role, sso_role'. Please contact a user with the appropriate role for help.", may be reported when sp_dump_history is executed by a user having the 'oper_role' granted. See KBA 2844541.
820188 When Rep Agent is configured for Multiple Paths Replication using Multiple Scanners, it ignores the abnormal termination of a Scanner thread or a Sender thread.
820488 The message, "current process infected with 11 (SIGSEGV)", in the module 'qry_init_stats' together with a stack trace may be reported in the SAP error log when a derived table in a SELECT query is aliased with the name of an existing temporary table, and the configuration option 'optimize temp table resolution' is enabled. See KBA 2862371.
820661 In some circumstances, a performance drop may be observed with SAP ASE 16.0 release, when a large batch of DELETE commands is executed and an index scan is chosen to perform the query. This can be worked around at the session level by executing ‘set postcommit_shrink off’ before the batch execution to disable the post-commit index page shrink chores. See KBA 2870613.
820832 In rare circumstances, a 692 error, “Uninitialized logical page ‘ < page-number > ’ was read while accessing database ' < database-name > ’ ( < database-id > ), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8). Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘checkpoint_db’, ‘ckpt_need_new_record’ and ‘wrongpage’ may be reported in the SAP ASE error log when the database option "trunc log on chkpt" is being enabled and after ONLINE DATABASE is executed in a database that was already online. Alternatively, a 1251 error, “The dbinfo anchor in the database 'database ' < database-name > ' ( < database-id > )' is already locked by the task. Nested access to dbinfo anchor is not allowed. Lock was acquired in file 'loaddb.c' at line 2165. This is an internal error. Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘xact_commit’, ‘xls_preflush’ and ‘lock_psema’ may be also seen. See KBA 2878392.
820930 The message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'StColstat::StAdjustDensity' together with a stack trace including the modules 's_compile_stmt' and 'optimize' may be reported in the SAP ASE error log when a SELECT query is run while Adaptive Server evaluates an execution plan for the query. See KBA 2885841.
821135 A 874 error, "Process < process-id > is trying to unkeep buffer < buffer-address > (dbid: < database-id > , pageno: < page-number > ) without releasing the shared latch it holds on the buffer.", may be reported in the SAP ASE error log when executing DBCC CHECKTABLE and while the diagserver binary is in use.
821261 A 267 error, "object '## < table-name > ' cannot be found.", may be reported when attempting to access a global temporary table which was created in an IMDB temporary database. See KBA 2903472.
821294 In rare circumstances, the message "Stack overflow detected", together with a stacktrace which includes the modules 'ucstackcrash' and 'sy_kill_task' may be reported in the SAP Adaptive Server error log, although there is no actual stack overflow, when a process is forcibly killed while it is holding a spinlock. This will result in Adaptive Server shutting down implicitly. See KBA 2905701
821347 A new Remote Procedure Call (RPC) sp_errlog is introduced in the SAP Backup Server that allows retrieving the most recent messages printed in the Backup Server error log. Additionally, a new system stored procedure sp_monbackupservererrorlog can be executed in Adaptive Server to create the proxy table master..monBackupserverErrorlog which is populated with the result set of the sp_errlog RPC execution.
821367 The SAP ASE Rep Agent configuration option 'priority' is taken into consideration for the scanner process under an HADR setup.
821523 In rare circumstances, a 1159 error, "Attempt to locate LSA extent partition control block failed for dbid ' < database-id > ', objid ' < object-id > ', indid ' < index-id > ' and partition id ' < partition-id > '.", together with a stack trace which includes the modules 'soextfinish', 'undo_apl_aextent' and 'pg_ea_getextp' may be reported in the SAP ASE error log while executing a SELECT INTO query which internally attempts to create and sort a work table, but the internal transaction is being undone. See KBA 2986566.
821588 A 11283 error, "External file access is not enabled or not licensed", may be reported on Windows platform when sp_dump_history is executed. See KBA 2921227.
821607 In rare circumstances, SAP Adaptive Server may report in master..monCachedObject MDA table inaccurate values in CachedKB column when at least one large I/O pool is configured in data cache. See KBA 2923998.
821632 A 11080 error, "The definition tree (object id: < object-id > ) of computed column ' < column-name > ' is missing.", may be reported during the execution of a stored procedure which creates a temporary table with computed column and recompilation is happening while the configuration option "deferred name resolution" is enabled. See KBA 2923497.
821696 The information reported in column LogRecordsProcessed for MDA tables monRepScanners, monRepLogActivity and monRepScannersTotalTime may sometimes be inaccurate. See KBA 2964364.
821756 In rare circumstances, a 19206 error, "sp_shrinkdevice: Execute immediate SQL failed. SQL statement is: DISK RESIZE NAME = ' < device-name > ', SIZE = ' < size-value > '", may be reported in the SAP SAP error log while running sp_shrink system stored procedure and the resulting disk size is more than 2,147,483,647 bytes (2048 Mbytes). See KBA 2976897.
821809 The system stored procedure sp_monitorconfig when executed with option "number of remote logins” may report inaccurate values in columns ‘Num_active’ and ‘Max_Use’ which exceed the configured value for remote logins when a 7221 error, “Login to site ‘ < ASE-name > ’ failed.”, is frequently reported. See KBA 2932504.
822016 The message, "No server log file open; Using stderr for log", may be unnecessarily reported when the SAP Backup Server is booted. See KBA 2741519.
822078 Wrong results may be observed when table variables with identical names are used in different stored procedures. See KBA 3009033.
822150 Under rare circumstances, select query on the MDA table 'monBucketPool' may show the bucketpool used (BucketPoolUsed column) value is greater than bucketpool used max (BucketPoolUsedMax column). See KBA 3009051.
822157 DBCC CHECKSTORAGE reports fault 100029 with fault_state 44 on OAM pages that have invalid bits set in the page header status field. The recommended action of running DBCC CHECKTABLE does not fix the fault. See KBA 2949021.
822205 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des_scavenge_for' together with a stack trace including the modules 'ptn__pdes_grab' and 'ind_ides_init' may be reported in the SAP ASE error log when Adaptive Server instantiates the metadata for a table in the metadata cache while the configuration option for 'number of open indexes' is under configured. See KBA 3009020.
822230 The message, “timeslice < negative-value > , current process infected”, in the module ‘exc__raise’ together with a stacktrace which includes the modules ‘lddb_main’ and ‘adb_read_all_stripes’ may be reported in the SAP Adaptive Server error log during the execution of LOAD DATABASE of an archive database dump.
822256 When MERGE is run on a table with a timestamp column, the timestamp column does not change when existing rows are updated. See KBA 2947932.
822318 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'sdes_hookup' together with a stacktrace that includes the modules 'show_condensed_text' and 'col_open_range' may be reported in the SAP ASE error log when running built-in show_condensed_text(). See KBA 2950527.
822391 In rare circumstances, a 2780 error, "maxlen( < value > is less than length ( < value > )", may be reported in the SAP Adaptive Server error log when an ALTER TABLE DROP COLUMN command followed by a SELECT command is executed. See KBA 3009034.
822434 A 3328 error, “Redo of 'CREATE INDEX' in transaction ID (0,0) for table name '', object ID '0' did not find 'sysobjects' system catalog log record. Recovery of database 'BLA' cannot continue.”, may be reported by LOAD TRANSACTION when loading a transaction dump that was taken after ASE was upgraded from SP02 to SP03 and a full database dump on SP03 was not taken first. This error is observed when the given database has the option 'enforce dump tran sequence' enabled.
822444 In a database setup for LTL replication, when Rep Agent is suspended, then resumed by executing the SRS administration commands 'SUSPEND LOG TRANSFER' and 'RESUME LOG TRANSFER', the message "process infected with signal 11" may be reported in the error log together with a stack trace which includes the modules 'kbfalloc', 'ra_malloc_mempool' and 'rep_agent_thread'. ASE eventually terminates. KBA 2958090.
822621 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'showplan' together with a stack trace which includes the modules 'sequencer' and 's_compile' may be reported in the SAP ASE error log when sp_showplan is run while it is retrieving the query plan of a stored procedure that is being executed by EXECUTE @procname and the variable size is bigger than 300 characters. See KBA 3031276.
822660 In rare circumstances, data between primary and standby might be inconsistent under an HADR setup with DRC replication enabled when two ALTER TABLE commands are executed on different tables followed by DML executed on reverse order on these two tables.
822682 In rare circumstances, a spid may hang with COMPILING status as shown by stored procedure sp_who, when executing a disjoint SELECT with LIKE operators. See KBA 2965623.
822688 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'LeRun' may be reported in the SAP Adaptive Server error log during the execution of a query that uses the built-in isnumeric( < string > ) with a very large value of < string > .
822716 A 834 error, "Illegal attempt to clean buffer ...", together with a stack trace which includes the module 'rec__boot_recover_dbs', 'buf_online_database' and 'cm_dbclean' may be reported in the SAP ASE error log when sp_object_stats is executed while a database is undergoing recovery. See KBA 2982529.
822719 On Windows, dbisql client does not run when executed from the Start menu. See KBA: 3004717.
822872 Under rare circumstances, Adaptive Server may hang with a message, "Initiating shared memory dump for ..." in the SAP ASE error log when the shared memory is being dumped for a configured operating system signal. See KBA 3009872.
823014 The text of a stored procedure or trigger may be incorrectly stored in syscomments system table if the SQL text contains a session level SET statement to a numeric value followed by a command. See KBA 2975923.
823035 When the Rep Agent Coordinator thread is killed with the KILL command in an HADR setup, an infinite number of 9242 errors may be reported in SAP Adaptive Server error log. See KBA 2975483.
823043 In rare circumstances, a 14316 error, "The number field in syscomments for partition condition '****' in database '*' for table '****' indid '*' has exceeded the 32767 limit", may be reported in the SAP ASE error log when "ALTER TABLE ADD PARTITION" is executed. See KBA 2975007.
823050 After dumping and loading a database that has had ALTER DATABASE SHRINK run on it, sp_helpsegment may report negative 'used_pages' values for that database. See KBA: 2995964.
823078 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ubofree' together with a stack trace which includes the modules 'ups_disable_hashstats_parallelism' and 'cri_ptn_index' may be reported in the SAP ASE error log when CREATE INDEX is executed. See KBA 2978619.
823119 In rare circumstances, a 678 error, "Invalid Buffer Cache Access: Could not open object ' < object-id > ' in database ' < database-id > '", together with a stack trace which includes the modules 'open_get_cacheid', 'Optimize' and 's_compile_stmt' may be reported in the SAP ASE error log while Adaptive Server is building the query plan of a DML query which involves a system temporary database or a user defined temporary database. See KBA 2891210.
823126 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'adjust_const_desc', and sometimes the signal 11 is followed by looping messages, "FATAL UNHANDLED EXCEPTION", may be reported in the SAP Adaptive Server error log when storing T-SQL text using SET command in a local variable that contains one or more '+' operators along with "/* . . . */" style comments and the configuration option 'enable literal autoparam' is set. See KBA 2979907.
823135 An incorrect value for column 'QuiesceTag' may be reported when a SELECT query is run on table master..monOpenDatabases although a PREPARE DATABASE < tag-value > RELEASE has been executed before. See KBA 2980484.
823142 When starting a capture with "dbcc workload_capture(start)" command, SAP ASE may report an error like "Workload capture failed to start for insufficient kernel resource memory. Please increase the value of 'kernel resource memory' and try again.".
823146 A 10330 error, “DROP TABLE or DROP ANY TABLE permission denied on object dir_ < value > ,database tempdb, owner dbo”, followed by a 10331 error, “Permission denied, database master, owner dbo. You need the following permission(s) to run this command: MAP EXTERNAL FILE.”, may be reported when sp_dump_history is executed by a user who does not have the same level of privileges as the previous user that executed the same system store procedure.
823199 In rare circumstances, a 1603 error, "Process priority 5 invalid or no process slots available", followed by the message "Failed to spawn delete sybdsam handler task.", may be reported in the SAP ASE error log when dropping a large amount of objects simultaneously and the Adaptive Server is configured for a single engine and the "number of user connections" is less than the number of objects being dropped. See KBA 2981553.
823200 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'dbinfo_boot_set_pg24objid' together with a stack trace which includes the modules 'dmpx__setup' and 'dbinfoupd' may be reported in the SAP ASE error log when DUMP TRANSACTION is executed. See KBA 2983946.
823228 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'pg_syslogs_extent_count' together with a stack trace including the modules 'th_fill_and_report_freespaceinfo', 'dbt__fill', and ‘lddb_main’ may be reported in the SAP ASE error log when LOAD DATABASE is executed. See KBA 3014622.
823235 When executing 'sp_hadr_admin failover_timeestimate' in an HADR setup, a list of the oldest active transaction for each HADR database is displayed.
823236 The SAP ASE Rep agent will not be notified for log extension after DUMP DATABASE is executed for an in-memory-database which will prevent data changes from being replicated.
823253 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'is_numeric' and 'LeRun' may be reported in the SAP Adaptive Server error log during the execution of a query that uses the built-in sap_hextobin( < string > , < string-length > ) with a very large value for < string-length > . See KBA 3001411.
823263 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'mda__collectCachedStatements' together with a stack trace including the modules 'mda_populate_monCachedStatement' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on master..monCachedStatement is executed. This results in Adaptive Server implicit shut down due to spinlock SSQLCACHE_SPIN being held. See KBA 2985036.
823265 A comma might be missed among values in Object_status attribute of sp_help < table_name > .
823277 In rare circumstances, the message, “Thread CAP Parser( ) infected with signal 11.”, together with a stack trace which includes the modules ‘exc__appDumpStack’, ‘exc_terminate’ and ‘strlcpy’ may be reported in the SAP Replication Server error log when an unexpectedly empty log record is processed under an HADR setup resulting in the replication flow to stop.
823290 In rare circumstances, replay might hang and never complete when BCP which is used to import a large amount of data into SAP Adaptive Server is captured and the table does not exist on the replay server. See KBA 2985083.
823310 Under rare circumstances, some user tasks might remain in a RUNNABLE state forever, while binding an active process (SPID) to a different thread pool using system stored procedure sp_bindexeclass. See KBA 2987082.
823328 In rare circumstances, connections from SAP Adaptive Server to Open server applications may hung. This hang was observed in the situation when the ASE site handler process is sleeping while it is freeing a SITEBUF data structure, and is awaiting for an existing connection to wake it up. The environment variable SITE_RETRIES whose default value is 30 seconds and it can be adjusted prior to bootstrap Adaptive Server to set the time for which ASE will wait before attempting to forcibly kill the site handler.
823356 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'ra__ci_stpmgr_execute' may be reported in the SAP Adaptive Server error log when the Rep Agent is stopped in an HADR setup. See KBA 3009036.
823375 In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'pss__get_free_pss' together with a stack trace which includes the modules 'pss_alloc' and 'spawn_conn_hdlr' may be reported in the SAP ASE error log. See KBA 2676160.
823392 The "replay show" command in SAP ASE Workload Analyzer Command Line Utility is enhanced to list all replays of a given capture.
823412 SAP ASE won't report the resource limit violation event in MDA table master..monThresholdEvent table if the resource limit action is configured as 2 (aborts the query batch), 3 (aborts the transaction) or 4 (kills the session). See KBA 2989840.
823413 A 806 error, "Could not find virtual page for logical page < page-number > in database < database-name > .", may be reported in the SAP ASE error log during the execution of a SELECT query whereby a worktable is required to sort a column whose size is close to the maximum width of a data row that can fit on a data page and there are NULL values in the sorted column. Alternatively a 614 error, "Adaptive Server accessed a row that has an illegal length of 0 while in database < database-name > . Page pointer = < page-address > , pageno = 24, status = 0x1, ptnid = -1, indexid = 0, level = 0. The minimum row length is < value > ?. The page size is 2048.", may be reported. See KBA 2531140.
823464 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'bufpagedestroy_noscan' may be reported in the SAP Adaptive Server error log when a SELECT query requires a worktable creation and the session option SET SORT_RESOURCES is enabled.
823466 In rare circumstances, a 4702 error, "XML parser fatal error", may be reported when the built-in xmlextract() is executed and charset 'SJIS' is in use.
823487 In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'crt_allocpages_for_dft' together with a stack trace which includes the modules 's_execute' and 'sequencer' may be reported in the SAP ASE error log when a DML is run and the Adaptive Server is allocating disk space for a deferred created table but has run out of disk space in the database.
823492 The message, "Current process infected with signal 11 (SIGSEGV)", or "Adaptive Server Enterprise system exception generated by a storage access violation", in the module '_lopConsWktAccess' together with a stack trace which includes the modules 'lopConsJoins' and 's_compile_stmt' may be reported in the SAP ASE error log during the execution of a SELECT query when the configuration option "inline table functions" is enabled. See KBA 2992794.
823522 In some circumstances, SAP Adaptive Server may report in master..monOpenObjectActivity MDA table incorrect values in LastUsedDate column. See KBA 2996719
823639 Export comparison may hang with status reporting "Exporting Progress: [5.00%]." when using the workload analyzer command line utility.
823687 Infected with Signal 11(SIGSEGV) in null() with altdb__upd_text_ptr on the stack may be reported in the SAP Adaptive Server error log when executing an ALTER DATABASE OFF command to shrink database. See KBA 3016683.
823700 A timeslice error in the module 'exc_raise' together with a stack trace which includes the modules 'quitfn' and 'LeExecSqlFunc' may be reported in the SAP ASE error log when killing a nested user defined function execution. The killed session will unexpectedly remain orphan and invisible by sp_who while it will continue to hold logical locks as shown by sp_lock. The current fix completes that of CR 785132. See KBA 2188555.
823714 The message, "Current infected with signal 11 (SIGSEGV)", in the module 'cri_fill_sarglengths' together with a stack trace which includes the modules 's__finish_alttab' and 'cri_ncrebuild' may be reported in the SAP ASE error log when CREATE INDEX and ALTER TABLE DROP both reference the same column and are executed together in a single batch. See KBA 3009010.
823732 The error message, “Backup Server: 4.141.2.40: [12] The 'CreateFile' call failed for database/archive device while working on stripe device '\\.\pipe\mypipe' with error number 2 (The system cannot find the file specified). Refer to your operating system documentation for further details.”, will be reported when DUMP DATABASE that is using a pipe archive device is executed. See KBA 3005089.
823768 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'err_pll_primary_processing' and 'LavaThreadDriverCleanup' may be reported in the SAP Adaptive Server error log during the execution of a query.
823853 When SSL configuration is not setup as expected on Linux, then the SAP Backupserver cannot be started and no error message is reported either on the console or the Backupserver error log.
823879 When replicating a large text or image value having an uncompressed size greater than 2GB, in a database setup for LTL replication, Rep Agent may terminate abnormally. The message, "RepAgent( < database-id > ): Received the following error message from the Replication Server: Msg 2056. Line < line-number > , character < column-number > : Incorrect syntax with '-'.", is reported in SAP ASE error log. See KBA 3009024.
823887 Under some circumstances, the message, "Internal error: SIGSEGV happened, please refer this issue to SAP Technical Support.", together with a stack trace in module VEH_Optimize() may be reported in SAP ASE error log but without detailed call stack information on Linux platform. Starting Adaptive Server with trace flag 16995 disables Vectored Exception Handling mechanism and allows detailed call stack information to be reported. KBA 3033771.
823936 In a replication environment setup for DDL replication, the DDL command 'CREATE VIEW' is erroneously replicated when it is executed inside a privately created system stored procedure or inside a replicated user stored procedure. In the latter case, the SRS DSI terminates after receiving ASE error 2714, "There is already an object named ' < view-name > ' in the database.".
824019 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'do__validate_stale_page_ts' together with a stack trace which includes the modules 'do_needed' and 'ds__recoverdbs' may be reported in the SAP ASE error log instead of raising error 3478 during recovery. See KBA 3014853.
824095 Spinlock contention on data cache due to scans on the sysobjects table may be observed with highly concurrent workloads executing prepared statements. See KBA 3017684.
824221 Adaptive Server is enhanced to avoid multiple evaluations of the built-in has_role() for each qualifying row in a query. This optimization applies to either cursor and non-cursor queries. See KBA 3010179.
824229 A timeslice error in the module 'pausenonatomic' together with a stack trace which includes the module 'des_checkpoint' may be reported in the SAP ASE error log when DUMP DATABASE is running. See KBA 3027150.
824232 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'crv_main' together with a stacktrace which includes the modules 'tmp_crv' and 's_normalize' maye be reported in the SAP ASE error log when CREATE VIEW using a large number of UNION operators is executed.
824297 In rare circumstances, the message, "timeslice -2001, current process infected", in the module 'pausenonatomic' together with a stack trace which includes the modules 'sort' and 'sortclean' may be reported in the SAP ASE error log during the execution phase of a stored procedure when a signal 11 (SIGSEGV) is caught in the sort manager of the Adaptive Server. See KBA 3033771.


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 SP04 PL01, ASE SP04 PL01, SP04 PL01, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.