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 PL14 . 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.
|820087||The message, "timeslice < negative-value > , current process infected ...", in the module 'j_forcep_order' together with a stack trace which includes the modules 'join' and 's_ap_compat_gen' may be reported in the SAP ASE error log when the SET options 'forceplan' and 'compatibility_mode' are enabled. See KBA 2840783.|
|821662||The Message 701, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", may be reported when executing the built-in 'hashbytes' or 'hash' by using the ‘md5’ hash algorithm against a table which has millions of rows stored. See KBA 2925203.|
|826658||The message, "ELC_VALIDATION_ERROR: Page not marked free.", may be reported in the SAP ASE error log when CREATE INDEX fails with a 1521 error, "Sort failed because a table in tempdb used for the processing of the query had a bad data page count. Tempdb should not have been damaged.". See KBA 3210652.|
|826833||The message, "current process infected with 11 (SIGSEGV)", in either the module 'pipe_read' or 'pipe_emptypipe' together with a stack trace may be reported in the SAP ASE error log during the parallel execution of a Lava query on AIX systems only. See KBA 2694998.|
|826901||In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LOBparamCacheRelease' together with a stack trace which includes the modules 'terminate_process' and 'lava_last_chance_cleanup' may be reported in the SAP ASE error log when a session is killed while executing a select query with LOB datum.|
|827033||The SAP ASE message text for 2780 error, "maxlen ( < value > ) is less than length ( < value > )", which is raised in module 'mk_constant' is enhanced to report useful debugging information that should help the root cause analysis. See KBA 3053562.|
|827045||The message, "Current process infected with signal 10 (SIGBUS)", in the module 'LeSendRow::_sendColsToClien' or 'sendtext' together with a stack trace which includes the modules 'LeSendRow::sendRowToClient' and 'LeEmitSndOp::_LeEoRouteResults', may be reported in the SAP ASE error log on Solaris systems when a SELECT query that includes in-row LOB columns is run while Adaptive Server executes the query using a HASH operator. See KBA 3238270.|
|827132||The system stored procedure sp_sysmon_locks misses to report 'Lock Promotion' values for 'Up-Page' and 'Up-Row' cases. See KBA 3252094.|
|827133||A 529 error, “Explicit conversion from datatype 'IMAGE' to 'VARCHAR' is not allowed.”, may be reported when insert auditing is enabled and a data row is inserted into a table that has an IMAGE column defined. See KBA 3245904.|
|827148||In rare circumstances, a 692 error, "Uninitialized logical page < page-number > was read while accessing database < database-name > ( < database-id > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), partition 'sysimrslogs_59' (59). Please contact SAP Technical Support.", may be reported in the SAP ASE error log under an HADR system which includes an IMRS-enabled database.|
|827195||DBCC FIX_PAGE utility has been enhanced to support new mode 'relaxed'.|
|827197||The output of DBCC SHOWRECOVERY may sometimes report an inaccurate value for "Percentage of log scan completed". See KBA 3252031.|
|827207||The message, "Current process infected with 11 (SIGSEGV)", in the module 'mda_populate_monDeviceIO' together with a stacktrace may be reported in the SAP ASE error log when queries are being run against MDA table master..monDeviceIO while a device is simultaneously being dropped via sp_dropdevice or unmount database. See KBA 3124331.|
|827213||The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'lookup_varnode' together with a stack trace which includes the modules 'internal_sql' and 'bld_cmd_estep' may be reported in the SAP ASE error log when a @table variable is referenced in the Transact-SQL command that is dynamically run with EXECUTE. See KBA 3255603.|
|827325||A new option to skip 'removehadr' is added in 'setuphadr' utility while configuring an HADR system.
- 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
CR, CR List, ASE 16.0 SP03 PL14, ASE SP03, SP03, PL14, 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 pageThis 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.