SAP Knowledge Base Article - Preview

3253524 - Targeted CR List for ASE 16.0 SP04 PL04

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 PL04. 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
762764 Introduce new global variable @@version_number_full. For ASE version"16.0.03.09", @@version_number_full will return integer value 1600309.
768285 A 834 error, "Illegal attempt to clean buffer: BUF= < buffer-address > ...", may be reported in the SAP ASE error log during boot recovery of an encrypted database after DISK REFIT was executed. See KBA 3256646.
774799 A 290024 error, "Invalid column length: < column-length > . Value must be between 0 and < maximum-column-length > at offset < column-offset > for ' < row-format > ' row with minimum row length of < minimum-column-length > .", may be reported by SAP Adaptive Server when a SELECT query is executed and an invalid column length is encountered. This message will now include the SQL Text that was executing when the error was encountered. See KBA 3271535.
794520 A new system stored procedure sp_evaluate_bs_cfg < database-name > [, < stripe-count > ] is introduced in SAP ASE to suggest an optimal utilization of stripes and service threads for the currently Backupserver configured shared memory. See KBA 2917434.
799405 In some circumstances, DBCC CHECKSTORAGE may seem to hang when it is executed against an archive database. See KBA 3259509.
819608 In rare circumstances, the message, "timeslice < negative-value > , current process infected", in the module 'sysxacts_materialize' together with a stack trace which includes the modules 'make_fake' and 's_setuptables', may be reported in the SAP ASE error log during the execution of a query involving systransactions. See KBA 2894955.
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.
822348 When TRUNCATE TABLE is executed in an encrypted database, SAP Adaptive Server may write some data in cleartext form on disk. See KBA 2952769.
823145 A 5055 error, "You cannot remove < number > log pages ( < number > MB) from the database < name > because the amount of free log space remaining ...", or a 5056 error, "You cannot remove < number > pages ( < number > MB) from database < name > ; only < number > unreserved pages ( < number > MB) are available.", may be reported by SAP ASE when ALTER DATABASE < name > LOG OFF < device > is executed for shrinking a log device. See KBA 3289600.
823436 A 804 error, "Unable to find buffer < address > from cache < cache-name > holding logical page < page# > in sdes < address > kept buffer pool for object < table-name > .", or a 814 error, "Keep count of buffer < address > in cache < cache-name > holding logical page < page# > in database ' < database-name > ' has become negative.", together with a stack trace which includes the modules 'dol_update', 'dol_update', and 'bufunkeep_do_decrement' may be reported in the SAP ASE error log when a DML is executed and the database transaction log is full. Bootstrap Adaptive Server with trace flag 1102 in order to gather more information in the error log when the transaction log gets full. See KBA 2994461.
823670 In rare circumstances, the message, "stack overflow last chance handler for task < kpid-value > ...", may be reported in the SAP ASE error log when a session has encountered an overflow stack situation and Adaptive Server is unable to report the session's call stack which would have helped diagnose the problem. See KBA 3018577.
824144 DBCC RESOURCE is enhanced to report the value for ‘raudflags’ which indicates the status of the audit process. Also the new built-in ‘is_audit_suspended()’ is added which indicates whether the audit process is suspended or not. Additionally the message, "Attention: Audit process is suspended", will be printed in the SAP ASE error log every 30 minutes if the audit process is suspended. See KBA 3256664.
824257 The MDA table monRepStreamStatistics is expanded to support new columns for HADR replication setups such as TotalWaitForPkgCount, TotalPackageCodingTime,LastPackageCodingTime,LongestPackageCodingTime,TotalCIE2ESmallTime,LastCIE2ESmallTime,LongestCIE2ESmallTime,TotalCIE2EMidTime,LastCIE2EMidTime,LongestCIE2EMidTime, TotalCIE2EHighTime,LastCIE2EHighTime,and LongestCIE2EHighTime. See KBA 3296470.
824691 In a very busy SAP Adaptive Server system, some procedure cache memory corruption may happen when concurrently one task is recompiling a cached statement and other tasks are competing for procedure cache memory while ASE is running short of procedure cache memory. A possible side effect is described in KBA 3051772 whereby ASE will shut down implicitly after a signal 11 (SIGSEGV) error is hit in the module 'senderror'.
824724 The stored procedure 'sp_chgattribute' is enhanced to accept a fully qualified object name as parameter. See KBA 827582.
824929 The column PagesTouched of the monitoring table monCachePool may provide an incorrect value when the pages from an encrypted database are brought into the SAP ASE data cache. See KBA 3063991.
825087 Query performance degradation may be observed along with network tasks running at 100% cpu when sessions execute SELECT queries using a large IN list and are connected to the SSL port. A new static Adaptive Server configuration option "max network events" is added to configure the maximum number of events the SAP ASE network controller can read from the O/S. The default value is 50 and the maximum is 500. See KBA 3083028.
825338 In rare circumstances, a 6913 error, "DUMP DATABASE < database-name > FULL is unable to clear the list of changed database pages. Future incremental dumps will be unnecessarily large until the next successful full DUMP DATABASE.", may be reported by SAP ASE when DUMP DATABASE is executed while the database option 'allow incremental dumps' is enabled. A diagnostics message will be printed in the Adaptive Server error log to help diagnose error 6913. See KBA 3238636.
825383 The 'Housekeeper Section' of sp_sysmon may recommend to increase "housekeeper free write percent" even though there is a low ratio of 'Dirty Buffer Cache Washes'. See KBA 3087788.
825614 In rare circumstances, a timeslice error together with a stack trace in the module 'oj_merge_ojblock' may be reported in the SAP Adaptive Server error log when a complex query that includes multiple views is executed. See KBA 3033730.
825663 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'plc__flush' together with a stack trace which includes the modules 'kill_proc' and 'rec_undo_session', may be reported in the SAP ASE error log while a session that has hit a stack overflow is terminated. See KBA 3164476.
825776 A 8009 error, “Error encountered by Backup Server. Please refer to Backup Server messages for details.”, may be reported by SAP ASE when DUMP DATABASE using the LABEL option is executed and the label name is provided without quotes. The Backupserver will first report the message, “Backup Server: 7.7.2.1: Option 'label' is not valid.”. See KBA 3290575.
825780 The message, "timeslice < negative-value > , current process infected", together with a stack trace which includes the modules 'GenCondensedText::isInTree' and 'show_condensed_text' may be reported in the SAP ASE error log when a SELECT query is using SHOW_CONDENSED_TEXT() built-in function. See KBA 3255032.
825859 SAP Adaptive Server is enhanced on Linux platform, to support booting with variable percentages of available huge page memory and remaining regular page memory. The ASE trace flag 17014 can be used to disable this behavior. See KBA 3296512.
825986 The error message, "ANS0344E (RC2107) Cannot Send data with a zero byte sizeEstimate", may be reported in the SAP Backupserver error log when DUMP command with database size greater than 4TB is executed using TSM. See KBA 3135839
826147 The message, "Current process infected with 11 (SIGSEGV)", in the module 'ssl_cipherbypss' together with a stack trace may be reported in the SAP ASE error log when a remote procedure call executes SELECT @@ssl_ciphersuite and the connection uses a site handler. The local client making the call will hang and the stacktrace will be reported in the remote SAP ASE error log. See KBA 3145809.
826193 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 during LOAD TRANSACTION when we are in a load sequence which spans across 16.0 SP02 and 16.0 SP03 versions, and the transaction dump being loaded was taken after Adaptive Server was upgraded from 16.0 SP02 or lower to 16.0 SP03 or higher, and a full database dump on 16.0 SP03 was not taken first. This error is observed when the database option 'enforce dump tran sequence' is enabled. The fix made in CR 822434 is redesigned herein to lift the obligation for taking a full database dump after Adaptive Server was upgraded to 16.0 SP03. See KBA 3289574.
826231 In rare circumstances, during the recovery phase of a database, negative values may be reported in the SAP ASE error log, for example, "Undo pass for database ' < database-name > ': 290090394 records done (100%); -7727 records left.", for the number of records to be recovered. See KBA 3158464.
826319 In rare circumstances, when a stored procedure that includes a MERGE INTO statement that is using the xmltable() query function which references a LOB parameter is executed, some memory corruption in the SAP ASE procedure cache may occur resulting in messages, "Current process infected with signal 11 (SIGSEGV)", reported in different modules. See KBA 3236455.
826338 Workload queries captured in a source capture are not shown in the Replay Analysis dashboard in Workload Analyzer of Administration and Management Console (AMC). This happens when the Use a generic password for all logins option is enabled for a replay in AMC. See KBA 3243010.
826383 In rare circumstances, SAP ASE may shut down implicitly after multiple 1204 errors, "ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.", or 1105 errors, "Can't allocate space for object 'syslogs' in database 'sybsecurity' because 'logsegment' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.", have been reported causing the termination of the audit process. See KBA 3229085.
826409 A 247 error message,"Arithmetic overflow during implicit conversion of UNSIGNED INT value ' < integer value > ' to a INT field" may be reported by stored procedure sp_ddlgen when the database is large enough to use pages in unsigned int page range. See KBA 3191721.
826412 New dbcc command, 'dbcc alarms' is added in SAP Adaptive Server Enterprise server to print alarms and their status. Additionally 'dbcc mempool("Alarms","show",1)' command is enhanced to print information about the alarm structures which are in use. See KBA 3189250.
826455 The SAP ASE procedure cache memory management is improved to free already allocated memory after encountering a 701 error, "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.", when a dynamic prepared query execution attempts to insert a huge amount of LOB data in a table. See KBA 3193727.
826550 SAP Adaptive Server has been improved to handle errors better during RPC execution. See KBA 3274344.
826558 A 692 error, "Uninitialized logical page ' < page-number > ' was read while accessing database ' < database-name > ' ( < database-id > ), object '' (99), index ' < Unknown > ' (0), partition ' < Unknown > ' (99).", may be reported in the SAP ASE error log when executing CREATE DATABASE FOR LOAD using over 6.25 terabytes of space. See KBA 3204034.
826565 A SELECT query on system table master..syscurconfigs may display negative values indicating an overflow when a data cache is configured with a greater than 2TB size. See KBA 3274290.
826623 In rare circumstances, the ASE Rep Agent may hang when the error message, "(CI-Info) Message: 76066, Severity: 5 Failed to serialize a package for Stream 'ISP'(pbuf = < package-information > , cnt = < counter-information > , cmds = < number-of-commands > , xdr = < package-information > ).", is reported in the SAP ASE error log under an HADR setup. Subsequently any attempt to either stop the Rep Agent or kill the Rep Agent will fail. See KBA 3207018
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.
826708 A 5123 error, "DISK INIT encountered an error while attempting to open/create the physical file for device ' < raw-device > '. Consult the Adaptive Server error log for more details. For the Cluster Edition, check the error log of each instance.", may be reported on AIX platform by SAP ASE when DISK INIT is run on a raw device and the sector size is of 4096 bytes. See KBA 3213002.
826718 DUMP DATABASE when used with compression levels 1 to 9 may expose a performance degradation on SunOS platform after having upgraded Adaptive Server to 16.0 SP03 PL06 release whereby the support for Zlib 1.2.12 version has been added. See KBA 3147657.
826725 In rare circumstances, the message, "BACKUPSERVER: bs_trap; process received signal 11", together with a stack trace which includes the modules 'as_report_progress' and 'srv_lockmutex' may be reported in the SAP Backup Server error log during LOAD DATABASE execution. See KBA 2896338.
826736 A 247 error, "Arithmetic overflow during explicit conversion of NUMERIC value ' < value > ' to a INT field.", may be reported by sp_sysmon_dcache_sum when running sp_sysmon for a large sample time on a very busy ASE. See KBA 2544721.
826739 A 4956 error, "Cannot alter table if REORG command or level 0 scans are active.", may be reported when simultaneous ALTER TABLE ... ADD PARTITION are run against a table while the configuration option 'enable utility lvl 0 scan wait' is enabled. See KBA 3216925.
826780 In rare circumstances, an undetected deadlock may occur between two tasks when SAP ASE is started with trace flag 859 which enables role lookup optimization and high access concurrency on sysattributes takes place. See KBA 3217673.
826819 The system stored procedure sp_altermessage is enhanced with the addition of new option ‘with_stack’. This new option allows to report in the SAP Adaptive Server error log the call stack from where in the code a given error is raised along with the error message itself. See KBA 3264966.
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.
826834 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 3238648.
826869 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules ‘dumpnames’ and ‘uni25m2__sqlhilo’ may be reported in the SAP Adaptive Server error log during DUMP DATABASE execution and TSM is in use. See KBA 3238651.
826899 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'subglobals' together with a stack trace may be reported in the SAP ASE error log during the execution of a query and a 261 error, "' < name > ' is not a recognized global variable.", was first reported. See KBA 3238692.
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.
826916 A 15946 error, "Invalid column length < column-length > found for column, column ID < column-id > , row ID < row-id > , page number < page-number > , partition ID < partition-id > . The length is greater than the expected maximum column length < maximum-column-length > .", may be reported by SAP Adaptive Server when a SELECT query is executed and an invalid column length is encountered. See KBA 3238630.
826932 A 930 error, "Database ' < database-name > ' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with 'for load' option.", may be reported during ALTER DATABASE on a database created FOR LOAD while the SAP ASE configuration option 'enable granular permissions' is enabled. See KBA 3229663.
826959 A 4022 error, "Server message: The password has expired, but you are still allowed to log in. You must change your password before you can continue. If a login trigger is set, it will not be executed.", and a 7742 error, "Server message: You must change your password using the ALTER LOGIN command before you can continue.", may be reported in the SAP JSAgent error log during startup of the jsagent when the sp_passwordpolicy 'expire login' is set to '1'. See KBA 3231364.
826969 A new configuration option 'HADR primary strict bootstrap' is added to SAP Adaptive Server, which when enabled would disallow primary ASE to boot if the standby ASE is not reachable. See KBA 3271537.
826995 A 17471 error, "The device name supplied is not a normal database device.", is reported instead of a 17470 error, "No such device exists -- run sp_helpdevice to list the ASE devices.", when either executing sp_dropdevice, sp_logdevice, or sp_deviceattr using a device that does not exist. See KBA 3234009.
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.
827068 When SAP ASE Workload Analyzer Command Line Utility (WLACLIUtil) is used to capture a workload from a windows ASE server or replay a workload against a windows ASE server and the "Do you want to automatically download PCAP files to local after capture is stopped" answer is set as "Yes", ASE will crash and WLACLIUtil will report an exception in com.sybase.workload.ASECatCaptureMgr$ASECatPCAPDownloadTask.run. See KBA 3275825.
827078 A timeslice error in the module 'prepprev' together with a stack trace which includes the modules 'onl__test_upgraded_replicated_db' and 'apl__startscan' may be reported in the SAP ASE error log during database boot recovery. See KBA 3242248.
827101 A 1265 error, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr=0x(nil), lrmagic=", may be reported in the SAP ASE error log when ALTER TABLE ... DROP PARTITION ... WITH ONLINE is run while replication is enabled in the database. See KBA 3248910.
827115 SAP ASE server will fail to boot, if the underlying platform does not support TSX (Transactional synchronization Extensions) capability, but the ASE configuration option “enable transactional memory” is set in the config file. See KBA 3245400.
827120 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 for HP platform. This will result in Adaptive Server shutting down implicitly. KBA 3287846
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. See KBA 3289609.
827155 A 10304 error, "Only the owner of object ' < object-name > ' or a user with 'sa_role' role can run this command.'", may be reported when "dbcc chgindcachedvalue( < database-name > . < object-owner > . < object-name > )" is executed in a database other than the database name indicated in the dbcc command by the object owner to whom the 'own database' privilege is granted on this database.
827181 Changes to hashing algorithm to provide better hash key distribution for SAP ASE statement cache component. Adaptive Server needs be started with trace flag 11032 to enable this change. See KBA 3269956.
827192 In rare cases, even after the timeout period has expired, the SAP ASE Jobscheduler's stored procedure "sp_sjobcontrol" with option "stop_js_timeout" does not stop the JSAGENT.
827193 In some circumstances, the query plan hint for WITH RECOMPILE is not recognized by execute cursor statements. See KBA 3281062.
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.
827202 In some circumstances, when a query that includes a nested execution of the built-in 'hashbytes' is run, SAP ASE may produce an incorrect results set. See KBA 3253011.
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.
827215 The installmaster script incorrectly does not insert supporting rows in spt_mda system table for jConnect readonly capability. See KBA 3241137.
827232 The execution of built-in show_cached_plan_in_xml( < statement-id > ,0) will not print the query plan details for execute cursors. See KBA 3269443.
827233 The message, "Current process infected with 11 (SIGSEGV)", in the module 'astc__dtxp_scavenge' together with a stacktrace may be reported in the SAP ASE error log when Adaptive Server has run out of "number of dtx participants". See KBA 2697060.
827237 The current fix expands CR 826739 fix whereby a 4956 error was reported by SAP ASE when ALTER TABLE ... ADD PARTITION commands are executed simultaneously on a table while the configuration option 'enable utility lvl 0 scan wait' is on. See KBA 3216925.
827306 In rare circumstances, an undetected deadlock may occur between a task running GRANT ROLE or REVOKE ROLE and a task performing a role lookup when SAP ASE is started with trace flag 859 which enables role lookup optimization. See KBA 3261480.
827325 A new option to skip 'removehadr' is added in 'setuphadr' utility while configuring an HADR system. See KBA 3275824.
827332 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'curs_close' together with a stack trace which includes the modules 's_recompile' and 's_readproc' may be reported in the SAP ASE error log when a stored procedure that has a server cursor is recompiled and before a 701 error, "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.", was reported. See KBA 3281068.
827333 A new optimizer criteria 'SET_OR_CURSOR' is added in SAP Adaptive Server allowing to enable OR optimization strategies for cursor queries processing. By default this optimizer criteria is disabled. See KBA 3291593.
827355 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", may be reported in SAP ASE error log together with a stack trace which includes either the module 'next_root', or 'IsExprNullable', or 'proc__setdb_tree' when a stored procedure is either executed or compiled. See KBA 3268829.
827373 The initial fix for CR 794082 and CR 825773 have been reworked in the current CR. Rolling back a transaction within nested triggers may cause unnecessary recompilations of the parent trigger. Additionally rolling back a transaction within a trigger may cause the calling procedure query plan removal from the Adaptive Server procedure cache. See KBA 3114259.
827440 SAP ASE may not check in ASE_WORKLOADANALYZER license when the execution of "sp_configure 'enable workload analyzer'" gets failed for insufficient kernel resource memory. See KBA 3290532.
827482 SAP ASE Workload Analyzer Utility or AMC may fail to analyze a workload with a message like, "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.", even though the ASE configuration option "procedure cache size" has been set to a big value. See KBA 3290479.
827537 The DTD validator has been disabled by default in SAP Adaptive Server. You can enable it by setting the environment variable XERCES_DISABLE_DTD to 0.
827540 Error Message 4997 "ALTER TABLE 'saptools..AMC_REPO_SERVER' failed. Default clause is required in order to add non-NULL column 'CREATED_BY'." is raised by instbaldr.sql script during an upgrade. See KBA 3285878.
827561 The error message, "10000 - Unanticipated Error: An unanticipated error occurred. The message returned was "For input string: "B"".", may be reported by SAP Sybdiag when it is run on HP-UX platform. See KBA 3296389 .
827653 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memalloc' together with a stack trace which includes the modules 'rvm__get_command' and 'parserr', may be reported in the SAP ASE error log when auditing is enabled and when a CREATE PROCEDURE command which includes USE < database-name > is the first command executed post-logon in the session. Alternatively, a 719 error, "The last prochdr value is not available for the prochdr '0x0'. This is an Adaptive Server internal error ...", may be seen. See KBA 3294210.
827694 enable LOB in triggers by default when "enable functionality group" on.


Read more...

Environment

  • AIX 64bit
  • HP-UX on IA64 64bit
  • Linux on x86 64 64bit
  • Solaris on Sparc 64bit
  • Windows on x64 64bit

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR, CR List, ASE 16.0 SP04 PL04, ASE SP04 PL04, SP04 PL04 Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem

About this page

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

Search for additional results

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