SAP Knowledge Base Article - Preview

2816551 - Targeted CR List for ASE 16.0 SP03 PL08

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 SP03 PL08. 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
291321 A 4305 error, "Specified file 'dump device' is out of sequence. Current time stamp is < date_value_1 > while dump was from < date_value_2 > .", will be reported during LOAD TRANSACTION when loading a transaction dump after having loaded a transaction dump that was taken with the NO_TRUNCATE option.
397943 The message text for error 3409, “Roll forward transaction < xact-name > .”, and error 3410, “Roll back transaction < xact-name > -- was aborted.”, have been enhanced to also report the transaction ID value. For example, a 3410 error will now be reported as ‘Roll back transaction '$write_stats' -- was aborted (xactid: Rid pageid = 10253; row num = 16).’, and a 3409 error as 'Roll forward transaction '$write_stats' (xactid: Rid pageid = 1111; row num = 8).".
555826 When the master database is recovered from a database dump that was taken on another Adaptive Server, it may inherit a Secondary Truncation Point if the source database was marked for replication. When this happens, the message, "Warning: The Secondary Truncation Point is active in the database 'master'.", will be reported in the SAP ASE error log allowing the SA user to take an action.
637833 Under rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'usctcondrop' together with a stack trace which includes the modules ‘rdes_free' may be reported in the SAP ASE error log when a killed kernel process tries to run on ASE engine. See KBA 2843659.
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.
660433 DBCC LOG will report field names when printing log records in a more consistent way across different log type of records. For example 'objectid' will be reported as 'objid', 'partition ID' as 'ptnid', 'extent ID' as 'extid', 'index ID' as 'indid' and 'cache ID' as 'cid'.
683542 Feature request to include database name or dbid in addition to the table name currently printed in REORG related messages in the ASE errorlor
691603 In rare circumstances, the message, "Assertion (!ctx- > cmdopt.is_tempdb) failed" may be reported in the SAP ASE error log when a temporary database with proxy_update option is in the process of being created and the diagserver binary is in use.
697805 When the Adaptive Server configuration parameter "quoted identifier enhancements" is not enabled and the session option "quoted_identifiers" is set, the execution of CREATE TABLE with a bracketed table name but with a quoted column name will unexpectedly result in the column being created with quotes included as part of its name.
698404 backupserver: Invalid object id found in srv_deletemutex
700234 A 536 error, "Invalid length parameter with value of -1 passed to the substring function.", may be reported by sp_dropserver when the target database has been created with a file based default location.
701262 A 17301 error, “’ < object-name > ’ is not a valid type name.”, may be reported by sp_addtype a bracketed identifier is given as the name of the type to be added. Additionally a 203 error, “The name ‘object-name > ’ is not a valid identifier.”, may be raised by SELECT-INTO when quoted _identifier param is not set an a bracketed identifier is in the select list.
704451 Remove orphaned transaction dump records from the dump history file when purging preceding transaction dump records.
717519 The execution of "sp_setrepproc integer_p, 'table'" on primary ASE is replicated as "exec sp_setrepproc @replicate_name='integer_p', @setflag='table', @logflag='log_sproc'" which will lead to error 18108 because the parameters combination is incorrect.
725677 A 3250 error, "The devices < device name > and < device name > specified in the command should be different" may be reported during the execution of DUMP DATABASE to a NULL device when it is referenced more than once. See KBA 2809910.
735328 Addition of new MDA table master..monProcELC to provide statistics on Engine Local Cache (ELC) related counters.
741444 Sybdumptran utility does not print an error when an invalid meta data file is used.
752096 The NULL dump device is supported on Windows platform for DUMP DATABASE command which is useful for performance testing. See KBA 2809950.
752453 The support of Java columns, installation of a jar file with installjava utility and removal of a jar file with REMOVE JAVA command is made available when using synchronous replication in an HADR setup.
769166 The output of sp_help < table-name > will now report 'plldegree' for the table and for each index entry present in the table. The output of sp_helpindex < table-name > will now report 'plldegree' for each index entry for table. See KBA 2054738.
773417 Additional information will be reported in the SAP ASE error log following a 4086 error, "Could not execute login script for user < name > ", allowing to help diagnose the cause of the error.
774104 A 15476 error, "Failed to find login password information for user < username > for key xxx", may be reported when 'login_passwd' option used in ALTER ENCRYPTION... MODIFY ENCRYPTION ... command on a connection authenticated using Kerberos.
774751 The value of IOTime, ReadTime and WriteTime queried from MDA monDeviceIO table may frequently overflow when ASE under heavy IO activity workloads. See KBA 2097726.
778763 dbcc memusage command might report inconsistent values under "Cache Memory" when caches are dynamically created/deleted.
780627 The execution of DBCC TUNE with option ‘des_greedyalloc’ does not report an error message when it is repeatedly executed on the same user table. See KBA 2845839.
783406 A 10331 error, “Permission denied, database master, owner dbo. You need the following permission(s) to run this command: UPDATE ANY SECURITY CATALOG.”, may be reported when UPDATE STATISTICS on a system table is executed by an end-user who has the privileges for managing any statistics granted, and the ASE configuration option “enable granular permissions” is on. See KBA 2163512.
789192 Under rare cisrcumstances, after an upgrade of SAP ASE, a 11031 error, "Procedure ' < procedure-name > ': Execution of SQL function < function-name > failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo. < procedure-name > .", or a 11798 error, "Illegal CREATE FUNCTION statement within a scalar SQL function.", may be reported when executing a stored procedure or a function. See KBA 2217001.
791720 The tran_dumpable_status() function returns status 1 for offline databases marked suspect due to rollback even though the transaction log for such databases can still be dumped. See KBA 2237035.
792255 Trace flag 3945 is used to enable validation checks during updates in order to ensure that logging is made in the correct database. If validation checks fail, a 3945 error, "An illegal attempt was made to update < object-name > in database < database-name > using a transaction that was started in database < database-name > (mode: < update-mode-value > , type: < query-type-value > .)", is reported. This validation is now the default ASE behavior and new trace flag 3996 can be used to disable it if required. The trace flag 3945 is not active any more.
797999 The message text for error 11919 has been changed to, "You cannot run REORG REBUILD in this database because either the database option 'full logging for reorg rebuild' or 'full logging for all' or 'select into/bulkcopy' is not enabled.". See KBA 2308016.
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.
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.
802852 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 's_unsave_kept_stmts' together with a stack trace which includes the modules 's_normalize' and 's_xform_to_execute' may be reported in the SAP ASE error log when a query in a batch is executed and the statement cache is enabled. See KBA 2453655.
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.
804836 A 718 error, "Memory allocation from process private memory is being performed by an incorrect process, ... This is an Adaptive Server internal error. Please contact SAP Tech Support", together with stack strace in the module 'LeHashOp::_LeOpOpen' may be reported in the SAP ASE error log during the parallel execution of a query. See KBA 2564532.
807532 In rare circumstances, a timeslice error in the module 's_xform_to_execute' together with a stack trace which includes the modules 'bin__ncmp' and 'memhilo' may be reported in the error log when executing a query that includes a long IN list and the statement cache is enabled and the configuration option 'enable literal autoparam' is on. See KBA 2462063
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.
811034 The message "current process indectred with signal 8 (SIGFPE)" or "timeslice < value > , current process infected at < address > " in the module "s__collectdiagparam" may be reported in the errorlog when ASE has not restarted for long time. See KBA 2542965.
812077 For the column of type unitext, if the value is NULL, SELECT on this column or implicitly converting this column to text may return unexpected data. See KBA 2564601.
812355 The sybmon sqltext and planprint commands are enhanced to print the query text in the specified OHEADER address and to print only the Lava plan for the specified E_STMT address. See KBA 2890263.
812532 In rare circumstances, a 11060 error, "This statement has exceeded the maximum number of recompilations (10).", may be reported when Dynamic SQL queries are executed from Java or Python clients. See KBA 2845818.
812704 A new optimizer criteria 'numeric_alt' has been added to improve the performance of queries having large number of SUM aggregates run on SAP ASE in a Business Warehouse environment. See KBA 2885872.
813510 Sybdumptran utility allows a database or transaction dump that was taken with the Backup Server archive API to be used as metadata file.
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.
813752 Diagnostic tracing for "SSL handshake failed" errors has been added. The diagnostic tracing can be enabled through traceflag 7867. See KBA 2633020.
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.
815204 The message "current process infected with 11 (SIGSEGV)" in the module 'np_conn_props' together with a stack trace which includes the modules 'omni_ct_cancel' and 'hk_cis_idle_timeout' may be reported in the SAP ASE error log when many CIS connections exist and the configuration option "cis idle connection timeout" is enabled. Alternatively the SIGSEGV can be hit in the modules ‘comn_loc_copy’, ‘ct_poll’, ‘ct_gp_version’, ‘ct_gp_version’ or ‘ct__tds_sendcmds’. See KBA 2651690.
815377 In rare circumstances on heavily loaded systems, a 539 error, "Unexpected internal access methods error 0, state 30.", or a 3914 error, "Illegal internal transaction status. This is an internal system error.", may be reported for a query involving temporary refresh pre-computed result set. See KBA 2825565.
815559 Occasionally the monProcessActivity MDA table may report negative value in LocksHeld column after the sp_sysmon or sp_monitor stored procedures are executed. See KBA 2755793.
815626 In rare circumstances, a 820 error, "Attempt to dirty non-log buffer BUF= < value > , MASS= < value > , ... Pinned xdes= < value > spid= < value > which is in I/O.", together with a stack trace which includes the modules 'bufpindirty' and 'plc__flush' may be reported in the SAP ASE error log when the syslogs system table is bound to a dedicated log cache having large buffer pool sizes configured. See KBA 2747852.
815641 A table with hash partitions, the column histogram steps does not match to the partition histogram after update statistics with different setting of "histogram tuning factor". See KBA 2662968
815772 A 2714 error, "There is already an object named '## < table_name > ' in the database.", followed by a 4413 error, "View resolution could not succeed because the previously mentioned objects, upon which the view ' < view_name > ' directly or indirectly relies, do not currently exist. These objects need to be recreated for the view to be usable.", may be reported incorrectly during the execution of a SELECT query which references a VIEW that is making use of global temporary tables.
815824 The Spins, Waits and Grants columns in monSpinlockActivity MDA table will get wrapped at 2147483648 (2^31) even though the columns are defined as BIGINT. See KBA 2686281.
816054 The message, "Current process infected with signal 11(SIGSEGV)", followed by a stack trace that includes the modules 'bt__col_cmp_noopt' and 'bt__nonlfrow_cmp' may be reported in the SAP ASE error log when a SELECT query with GROUP BY that contains expressions is executed. See KBA 2681394.
816102 The message, "current process infected with 11 (SIGSEGV)", 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 SAP ASE error log when a SELECT query with computed columns is executed. See KBA 2844942.
816133 Stored Notify settings in Cockpit are no longer shown after disabling a monitoring Alert. See KBA 2682425.
816139 SAP ASE Resource Governor does not terminate a session that was waiting on a lock acquisition when the configuration option ‘allow resource limits' is enabled and the resources limit action is to terminate the session when it exceeds the configured elapsed time value. See KBA 2679863.
816248 INSERT to varchar column may incorrectly left trailing spaces if the source of the INSERT command is local variable and the query to insert the data is using UNION. See KBA 2683043.
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.
816646 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module ‘GtElement::GtSecondaryInit(OptBlock*)' and the message, "timeslice error: spid < spid# > exhausted its 'time slice' of < X > milliseconds and additional 'cpu grace time' of < Y > ticks ( < Z > milliseconds). It has been marked for termination.", together with a stack trace which includes the module 'ApStoredTab::findGttTable()' may be reported in the SAP ASE log while executing a large query. See KBA 2699085.
816694 The message "current process infected with 11 (SIGSEGV)" in the module 'pipe_read' or 'pipe_write' together with a stack trace may be reported in the SAP ASE error log during the parallel execution of a Lava query. See KBA 2694998.
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.
816829 Occasionally on a heavily-loaded multi-engine system, some column values in the monState MDA table, including ULCKBWritten, LogicalReads, PhysicalReads etc. might suddenly become decreased. See KBA 2748418.
816835 The configuration parameter "LFB memory size" is unexpectedly stored as "LFB pool size" in the configuration file. See KBA 2699329.
816955 Error 11058 "Statement contains ' < > ' columns/expessions in the target list. This exceeds the maximum limit of '4096'." might be raised when using cursors with large IN() list which exceed 4096 elements. See KBA 2747807.
817069 A 5861 error, "The current 'max memory' value ' < value > ', is not sufficient to change the parameter 'allow updates to system tables' to '1'. 'max memory' should be greater than 'total logical memory' ' < value > ' required for the configuration.", might be reported when running sp_configure with options like "allow updates" that do not require more memory when static config parameters such as "global cache partitions" is set to a non-default value and the amount of free memory remaining is relatively small. See KBA 2817648.
817097 A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact Sybase Technical Support.", may be reported when a SELECT query with two tables join and a GROUP BY clause on each side of the join is executed while the optimization goal allrows_mix is enabled but hash_join is not. See KBA 2708697.
817173 In rare circumstances, a 16821 error, "Command UPDATE has been aborted because it cannot make unlogged changes to table ' < table-name > ' in database ' < database-name > ' while ONLINE REORG/CREATE INDEX is active on the table. ASE is terminating this process.", together with a stack trace which includes the modules 's_finish_cmd', 'xact_endupdate' and 'dodeferred' may be reported in the SAP ASE error log when an UPDATE command is run on an All Pages Locked table (APL) with clustered index and an ONLINE utility is running in parallel.
817270 When printing the "end of stack trace" message, incorrect suid was printed as a negative number when the suid is greater than 32K. The user's suid is 37029. "end of stack trace, spid 18125, kpid 1085497422, suid -28507".
817284 In some circumstances, trailing spaces in a string may not be removed when inserting the string into a VARCHAR column via an Instead Of Trigger.
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.
817439 KBA 2709213 - temp worktable not cleaned up in user temporary database (user tempdb) in ASE157 SP139
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.
817594 New backup server option 'enable_fips' added to support FIPS login password encryption.
817680 A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > .", may be reported during database encryption. See KBA 2761091.
817697 In rare circumstances, it may be impossible to KILL a blocked process when the system tempdb log is full and tempdb is a mixed data and log database. See KBA 2734951.
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.
817750 In rare circumstances, the message, "The bit for alloc page < value > in database < number > is clear. It should be set.", may be repotred when DBCC GAM is executed. See KBA 2733631.
817752 Under rare circumstances in an HADR setup, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, this may prevent some data from being replicated which will be replicated upon Rep Agent restart. The message, "(CI-Info) Message: 1001, Severity: 0 ( < dbname > )MSProdReceiver: notify client consumer is down strm < address > ...", will be reported in the ASE error log, but will not be followed by an expected 9414 error, "RepAgent( < dbid > ): Streaming replication stream CI Library error error -1 with severity 2 and message 'Producer receiver ' < dbname > ’' failed to receive data, shutting down transport to ‘ocs:host:port'.'. Rep Agent detected error 3 with message 'Unknown' at line 0 in file nofilename.". See KBA 2879595.
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 white space characters. See KBA 2716155.
817954 A 11307 error, "The object ' < object_ID > ' in database ' < database_ID > ' is not a valid parameter for the built-in function logschema(). The object must be a user table or a stored procedure.", may be reported in the SAP ASE error log when DDL replication is enabled, and a table type is being dropped. See KBA 2786860.
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.
818065 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'prObject_list' together with a stack trace which includes the modules 'showplan' and 'exec_lava' may be reported in the SAP ASE error log when sp_showplan is executed. See KBA 2743737.
818084 A 6701 error, “Could not open dbid < value > , object id < value > .”, may be reported followed by an implicit transaction abort, during a Business Suite zero-downtime upgrade which prevents the upgrade from succeeding.
818253 Feature enhancement to allow ASE to LOAD backup archives that were DUMPed using the Backup Server API without needing to use the Backup Server API for the LOAD operation. See KBA 2786342.
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.
818266 The message "Engine ( < number > ) not online, Not going to Push affinity in [function] at line xxxx" may be reported in the SAP ASE error log when the configuration option "kernel mode" is set to threaded mode. These messages can be ignored. See KBA 2751782.
818291 Error message reporting into the SAP ASE error log when SSL connections are being established has been improved.
818299 A 10353 error, "You must have any of the following role(s) to execute this command/procedure: 'sybase_ts_role'. Please contact a user with the appropriate role for help.", will be reported when sp_config_rep_agent is executed which results in the failure to log the RepAgent configuration change to the SAP ASE error log. This error will cause the SRS DSI connection to shut down as this error is mapped to STOP_REPLICATION action.
818302 In rare circumstances on a heavily-loaded multi-engine system, high contention on the database spinlock (rdbt_spin) may be seen during the execution of a large number of cross-database queries. See KBA 2776093.
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
818344 Add "Warning:" before the text for error message 10828. The new message is "Warning: Consider increasing the value of configuration parameter 'max memory' or decreasing the value of configuration parameters causing significant memory consumption, such as 'number of user connections'."
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.
818394 The message, "Assertion (!(USER_TABLE_OBJ(SDES_DES(sdes))) || !(sdes- > sread_sdes) || SDES_DEF_OP_LOCK_HELD(sdes- > sread_sdes))", together with a stack trace which includes the modules 'xact_endupdate’ and 'dodeferred’ may be reported in the SAP ASE error log when an UPDATE on a compressed table is executed and the diagserver binary is in use.
818408 Under rare circumstances dump and load database may hang when using multiple stripes on Windows platforms.
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.
818484 A new parameter, 'host_public_ip', has been introduced in the resource file of setuphadr, which can cab be set to the public IP address of the host. If this parameter is set, then RMA will use this address to connect to the host.
818504 In rare circumstances, Adaptive Server processes may wait for a long time for DUMP DATABASE to complete, when the database size is big and there are many concurrent commands running that either perform non logged updates, like SELECT INTO, or logical log records updates, like CREATE INDEX. See KBA 2776030.
818523 In rare circumstances, Adaptive Server may perform wrong memory deallocations when a cursor query that involves the built-in datachange() is executed and XML monitoring is enabled. This may cause errors reporting incorrect accounting between allocated and deallocated memory pages and sometimes may result in the session terminated with a stack trace reported in the SAP ASE error log. See KBA 2756423.
818524 On Windows platforms, the error, "'CreateFile' call failed for database/archive device while working on stripe device < number > (The system cannot find the file specified)", may be reported when executing a DUMP command on a shared network folder using the Universal Naming Convention (UNC). See KBA 2751605.
818538 In rare circumstances, a process may run into a self-deadlock with the message, "Killing spid: < value > will not be immediate because it is waiting for a latch held by spid: < value > .", reported in the SAP ASE error log upon a KILL. This process was attempting to create a temporary table but was waiting for an allocation page lock which was held by another process. See KBA 2789764.
818566 The index to be used as the primary key for replication can be forced manually to a non-unique index with the new 'force' option of the system stored procedure sp_setreppk which has the following usage: sp_setreppk table_name[, index_name[, 'force']].
818594 In rare circumstances, the message, "current process infected with 11 (SIGSEGV)", either in the module 'sort' or 'solm' together with a stack trace may be reported in the SAP ASE error log during the execution of a query that requires a sort operation.
818603 In rare circumstances, a memory leak of 41 bytes may happen when the Backup Server fails to open an archive device for write, either because it is not writable or because the volume has an expiration date, if the end-user responds using the sp_volchanged stored procedure with the 'RETRY' option.
818611 SAP ASE may choose a non-performant query plan execution when a query with a ROWS LIMIT/OFFSET clause using a MAXINT value is executed. See SAP Note 2783751.
818627 In rare circumstances, following a 1204 error, "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.", queries or built-ins execution on SYSLOGINS may hang. See KBA 2763234.
818632 The message "current process infected with signal 11 (SIGSEGV)" in the module 'LeRun' followed by a stack trace that includes the modules 'LeEvals::LeEvRun', 'LeRestrictOp::_LeOpOpen' and 'LeScalarAggOp::_LeOpOpen', may be reported in the SAP ASE error log when a prepared statement has parameter markers as an operand in CASE search condition. SAP KBA 2762616
818642 When running in an HADR environment, ASE may incur SIGILL in function sybnet__flt_init() on standby during setuphadr on AIX platform.
818665 In some circumstances, a 3703 error, "Cannot drop the trigger with object-id < objid > in database < dbid > , because it doesn't exist in the system catalogs.", may be raised when dropping a view if CREATE OR REPLACE TRIGGER with INSTEAD OF option was previously executed on the view. See KBA 2764599
818666 The message "system exception generated by a storage access violation" in the module 'omni_parse_name_using_optional_bracket' together with a stack trace which includes the modules 'tmp_dropto' and 's_normalize' may be reported in the SAP ASE error log when failing to create a stored procedure that references a global temporary table due to an error that is not related to the global temporary table. See KBA 2764590.
818671 In rare circumstance, a significant increase of CPU time is seen for table scans on tables which have data compression enabled when the number of concurrent scan tasks increases.
818684 The message "TaskReplication.runTask(): SetupReplicationTask time out." may appear during setuphadr when high number of databases are involved. A new environment variable, 'SETUP_SRS_TIMEOUT' and 'MATERIALIZE_DB_TIMEOUT', has been introduced, which can be used to set the timeout value in seconds, for setting up replication and materializing databases, respectively. See KBA 2776399 "Unable to materialize large ASE Database with sap_materialize auto".
818693 In rare circumstances, a 2714 error, "There is already an object named '# < temp_table_name > ' in the database.", may be reported by Adaptive Server when CREATE TABLE is run in order to create a temporary table which is already dropped. See KBA 2816676.
818707 In rare circumstances, a 3606 error, "Arithmetic overflow occurred.", may be reported when sp_helpdb is run after database shrink operations took place and one of the de-activated devices had a size that is larger than 4294967295. See KBA 2766504.
818714 The message, "The used count in IMOAM Page < page# > is -1 and it does not match to the expected number 0.", may be reported when DBCC TABLEALLOC is run on an IMRS enabled table.
818724 A 3606 error, "Arithmetic overflow occurred.", may be reported while executing stored procedure sp_shrink 'device', < device name > , < size > . See KBA 2767036.
818728 Under rare circumstances in an HADR setup that has an IMRS database enabled, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, there is a small window which may cause data loss as DML commands are sent to Replication Server after their commit and will be incorrectly ignored.
818730 On certain platforms like HPIA, Adaptive Server may report a 8522 error, "Warning: Invalid location < location-number > found in database ' < database-name > ' for the fragment starting at logical page < page-number > . Execute DBCC CHECKCATALOG( < database-name > , fix) to fix it.", even after having executed DBCC CHECKCATALOG( < database-name > , fix) command.
818734 On Big-Endian platforms, setting a Backup Server configuration option to the same value it already has, will create a new configuration file identical to the previous one instead of displaying a message indicating that the value has not changed.
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.
818778 In rare circumstances, a 9502 error "string data right truncated" may be raised when applications using parameterized prepared statement with dynamic SQL that uses a LIKE clause in its query over a univarchar column and statement cache is ON. See KBA 2779052.
818784 A 7928 error, "Index < name > is not consistent; found < number > leaf rows but < number > data rows.", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database.
818803 In rare circumstances, the execution of a SELECT query that is using MINUS or INTERSECT operators and involves views or derived tables may return incorrect results. See KBA 2769807.
818805 In rare circumstances, the message, "The value of the 'max memory' parameter ( < value > ) 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 unexpectedly reported in the SAP ASE error log during Adaptive Server startup. See KBA 2769883.
818812 In some circumstances, query using compressed index may not return all qualified data rows on data-only locked tables. See KBA 2803119.
818818 In rare circumstances, ASE may report high values for QueryOptimizationTime on monProcessActivity MDA table that may be higher than the elapsed time since the server gets started. See KBA 2770233.
818824 The message, "No resources to allocate TH_FREESPACE_DIAG for database < dbid > . Freespace accounting information cannot be shown.", may be reported in the SAP ASE error log when LOAD DATABASE, LOAD TRANSACTION or ONLINE DATABASE is executed. See KBA 2769024.
818828 A 3602 error, “Transaction has been rolled back.”, may be reported when performing DML commands on a table that once had trigger with multiple actions created for the table and the same trigger have been dropped. See KBA 2771427.
818852 A 10795 error, "The file ' < xx > .class' contained in the jar does not represent a valid Java class file" may be reported while install the jar file in ASE database. See KBA 2790939.
818856 A 9219 error, "RepAgent( < database-id > ): Internal error.", followed by a 9416 error, "Rep Agent on database ' < database-name > ' switched from mode ‘sync’ to mode 'async' because < reason-for-switching > ”, may be reported in SAP ASE error log under an HADR setup when RepAgent is being stopped or has run into error with message, "Current transaction ID ( < page# > , < row# > ) in database ‘ < database-name > ' (dbid = < database-id > ): commit wait expired.'”. See KBA 2850255.
818875 Using the --show-master-version switch with dataserver or sqlsrvr.exe results in a segmentation fault. See KBA 2773633.
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.
818891 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'oh_copy' and 'oh_dup', may be reported in the SAP ASE error log when When creating login within IF-ELSE with auditing enabled. See KBA 2843548.
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.
818957 A 2753 error may be raised on an ASE where Japanese language is installed if "enable monitoring" and "plan text pipe active" configuration parameter are 1 or showplan is enabled for a complex query. See KBA 2777310.
818971 The message "Current process infected with 11 (SIGSEGV)" in the module 'proc_setdb' together with a stacktrace which includes the modules 's_getTreeOrPlan' and 'kw_exec' may be reported in the SAP ASE error log when DBCC CHECKSTORAGE is run on a database with many partitioned tables and the values for the configuration options 'number of open objects', 'number of open indexes' and 'number of open partitions' are not enough established. See KBA 2785031.
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.
819011 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'prSQLTEXT' may be reported in the SAP ASE error log when running DBCC SQLTEXT on a spid executing a cursor which has been marked as a zombie. See KBA 2780164.
819016 In rare circumstances under an HADR setup the ASE Replication Agent may shut down after reporting a 9415 error, "RepAgent( < dbid > ): Warning: The size of the stream buffer is too small ( < size > bytes). Use sp_config_rep_agent ' < dbname > ', 'stream buffer size', ' < new_value > ' to increase it.". Additionally a CI Library error message indicating the failure of a CI API call is reported in the SAP ASE error log. See KBA 2890740.
819070 The message, "current process infected with 11 (SIGSEGV)" in the module 'getnext' together with a stack trace which includes the modules 'upgd__add_table_anchors' and 'upgd_upgrade_db' may be reported in the SAP error log during ONLINE DATABASE while an internal upgrade is run as the database dump was taken on a previous ASE release and a different platform. See KBA 2786974.
819132 The message "timeslice -501, current process infected" in the module 'exc_raise' together with a stack trace which includes the modules 'loginfo_get' and 'loginfo_builtin' may be reported in the SAP ASE error log when the built-in loginfo( < dbid > , 'inactive_pages') is executed on a mixed-log-and-data database. See KBA 2747600.
819178 Under rare circumstances, in a HADR setup, when the primary Adaptive Server is rebooted, it may start as standby and the message, "WARNING: split brain check refused to allow this server to become Primary", along with the message, "remote HADR server < server-name > is STANDBY, but configured for PRIMARY", may be reported in the SAP ASE error log. See KBA 2890707.
819179 A 3375 error, "Unable to drop global temporary table < name > as it is in use", may be reported when a global temporary table is dropped and is used concurrently by another session. See KBA 2787484.
819185 A 3624 error, "Truncation error occurred", is raised with severity 10 (warning) instead of severity 16 (error) when DYNAMIC PREPARE is set to FALSE for batch processing (language batch param) and the client tries to INSERT a numeric which is out of scale.
819187 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘kstcpnetctlrCancelRequests’ together with a stack trace may be reported in the SAP ASE error log. If shared memory dump is configured for signal 11, then ASE may hang. See KBA 2786903.
819188 In rare circumstances, Adaptive Server may incorrectly create the in-lined version of a Table Valued User Defined Function (TUDF). As a result a 207 error, “Invalid column name < name > .”, may be reported during the execution of a query which references this TUDF.
819212 A 632 error, "Attempt to move memory with an incorrect length of -xxx. Maximum allowed length is 16384", may be reported when executing CREATE LOGIN command followed by the execution of a stored procedure which contains SELECT query while auditing is enabled. See KBA 2788657.
819216 Workload Analyzer fails to identify requests that are cancelled by either TDS_BUT_ATTN token or OOB data. All these requests will have "Finished" state instead of "Cancelled" state in dashboard. See KBA 2803118.
819224 The message "current process infected with signal 8 (SIGFPE)" in the module 'proc_setdb' together with a stack trace which includes the modules 's_getTreeOrPlan', 'attachrule' and 's_compile' may be reported in the error log. See KBA 2593370.
819230 In rare circumstance, 9952 error, "Workspace < string > is too small to permit the CHECKSTORAGE operation to proceed. Use sp_dbcc_alterws and sp_dbcc_updateconfig to correct the problem", may be reported when running DBCC CHECKSTORAGE() on a very large database with a large scan workspace (whose size is greater than 80G) configured. See KBA 2025063.
819231 Under rare circumstances, the message "Volume validation error: attempt to open < ASE_devicename > returned No such file or directory", may be reported on a Solaris platform during the execution of a DUMP command when the Backup Server received a SIGPOLL signal while attempting to open an ASE device. See KBA 2774930.
819237 In rare circumstance, an outer join query may return a wrong result when a SQL UDF is used in the WHERE clause and the SQL UDF's parameter is passed in as a column name but not a variable. See KBA 2791388
819242 The message, "current process infected with 10 (SIGBUS)", in the module 'LeOperator::LeOpSaveIOStats' together with a stack trace which includes the modules 'LeRetnCode LeDMLOp::_LeOpClose' and 'exec_lava' may be reported in the SAP ASE error log during the execution of a query when the statement cache is incoherent which can lead to Adaptive Server shutting down implicitly. See KBA 2405522.
819246 Attempt to execute the command "alter encryption key dual master [..] modify encryption with external key" incorrectly raising error 2941 instead of error 2947 which indicates the dual master can only be encrypted by user password. See KBA 2790961.
819247 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memmove' together with a stack trace which includes the module 'bt__getrestartkey' may be reported in the SAP ASE error log when UPDATE STATISTICS is being run while DML commands are concurrently executed on the same table. See KBA 2792088.
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.
819285 When the environment variable MALLOC_CHECK_ is set to 2 the Backupserver will receive a SIGABRT signal during the cleanup phase of any connection established with Adaptive Server. This will result in the Backupserver process dyeing and a manual restart is required. This behavior is the result from the fix made in CR 699826 for 16.0 SP03 PL07, "Allow DUMP and LOAD of an in-memory database when using single-sign-on authentication mechanisms, like Kerberos. See KBA 2754515.", which fix we are backing out until the root cause is identified and fixed.
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.
819308 In rare circumstances, a 2620 error, “The offset of the row number at offset < value > does not match the entry in the offset table of the following page: Page pointer = < value > , pageno = < value > , etc.”, together with a stack trace which includes the modules ‘update’ and ‘putdrow’ may be reported in the SAP ASE error log during a DML execution on an All Pages Locked (APL) table when one or more previous UPDATE command(s) were executed in deferred mode. See KBA 2838778.
819317 A 3775 error, "Unable to drop global temporary table < name > as it is in use", may be reported during the DROP of a global temporary table due to the presence of an orphan instance of the global temporary table. See KBA 2794963.
819323 In a HADR setup, if the 'setuphadr' script is run multiple times on the third (DR) node and the RMA is running, then the HADR setup is teared down.
819329 In rare circumstances the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'd_orphantables' together with a stack trace which includes the modules 'exec_dbcc' and 's_execute' may be reported in the SAP ASE error log when running DBCC ORPHANTABLES with the option 'drop' to delete an orphan temporary table. See KBA 2795213.
819340 In rare scenario ASE may issue error 834 with state 3 leading to checkpoint worker being blocked. The transaction log may subsequently fill. See KBA 2869028.
819347 In rare circumstances the message, "Adaptive Server Enterprise system exception < value > generated by a storage access violation.", in the module 'omni_parse_name_using_optional_bracket' together with a stack trace which includes the modules 'tmp_drop_globaltt' and 's_free' may be reported in the SAP ASE error log when a user session disconnects and an attempt to drop active global temporary tables fails.
819388 In rare circumstances, SAP Adaptive Server may not shutdown when the SHUTDOWN command is executed or when shutdown from the Windows Service. The module 'shutdownjobscheduler’ will be reported by DBCC STACKTRACE on the session executing the SHUTDOWN command or the SHUTDOWN HANDLER task. See KBA 2797851.
819401 The 'histogram_tuning_factor' parameter of UPDATE STATISTICS command doesn't take effect for partitioned tables when it is different from the Adaptive Server configuration option 'histogram tuning factor' value. See KBA 2662968
819412 In rare circumstances, a 3328 error, "Redo of 'CREATE INDEX' in transaction ID ( < page# > , < row# > ) for table name < objname > , object ID < objid > did not find 'syscolumns' system catalog log record. Recovery of database < dbname > cannot continue.", may be raised during LOAD TRANSACTION recovery when before the index creation the table had a non-materialized column with a constant default value and some other column of the table was dropped with 'no datacopy' option.
819437 A 12324 error, "In database < name > , the server failed to open required table 'SYSPARTITIONS'. Please contact SAP Technical Support.", may be reported when a full database dump is loaded on a database that is marked as suspect due to a previously hit 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < value > , object id = < value > , page timestamp= < value > . Log old timestamp= < value > . Log record marker = ( < value > ). Transaction ID = ( < value > ).". See KBA 2808901.
819439 Under rare circumstances in an HADR setup with DRC enabled, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, this may prevent some data from being replicated which will be replicated upon Rep Agent restart. The message, "RepAgent( < db_id > ):Streaming replication stream CI Library error -1 with severity 2 and message 'Producer of Stream 'ERP_2' failed to send a message with < message length > -bytes.'. Rep Agent detected error 213 with message 'CI API call to SendMsgs() failed ' at line < line number > in file ra_ci_interf.c." will be reported in the ASE error log, but will not be followed by the other similar message "RepAgent( < db_id > ): Streaming replication stream CI Library error ...". See KBA 2808878.
819452 A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log old timestamp= < log-old-timestamp > . Log record marker = ( < page-number, row-number > ). Transaction ID = ( < page-number, row-number > ).", may be reported in the SAP ASE error log during LOAD TRANSACTION when either trace flag 1773 or 1774 is enabled to defer the recovery of indices at online time respectively in automatic or manual mode.
819468 When the configuration option 'enable granular permissions' is set, a user that is aliased to dbo in the master database is aliased to dbo in all databases. See KBA 2795960.
819479 The message "current process infected with 11 (SIGSEGV)" in the module 'LePipeRWState::_LePrwsWriteConstant' together with a stack trace which includes the modules 'LeExecuteWorkUnits' and 'LavaThreadDriver' may be reported in the SAP ASE error log when a SELECT query is executed in parallel. See KBA 2694998.
819493 A 247 error, "Arithmetic overflow during explicit conversion of FLOAT value ' < value > ' to a NUMERIC field" may be reported when executing sp_helpcache or manually querying the syscacheinfo or syscachepoolinfo view on the system that configures very large caches. See KBA 2402812
819500 Under rare circumstances, on a heavily-loaded multi-engine SAP ASE, the 'Operations' column in monOpenObjectActivity MDA table might get wrapped in a short time.
819522 In some scenarios, using SQL-batch in chained mode which includes the queries "select into #temp" and "drop table #temp" may leave behind an orphan #temp table. See KBA 2805819.
819523 A 2901 error, "Exception stack limit exceeded", followed by a rolled back transaction, may be reported in the SAP ASE error log when executing "dbcc upgrade_object(dbname, 'procedure', 'check')" on AIX platform. See KBA 2805876.
819536 In rare circumstances, the message, "Assertion (mutex- > lockcount == 0) failed" may be reported in the SAP Backupserver error log when a DUMP command is executed and the diagserver binary is in use. See KBA 2871713.
819538 jConnect applications may fail with the message, ‘java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).’, reported when SAP ASE is configured with MIT Kerberos and charset conversion is not available between Adaptive Server and jConnect charsets in use. See KBA 2807020.
819540 The message "current process infected with 11 (SIGSEGV)" in the module 'dbt_kept_by_pss' together with a stack trace which includes the modules 'dbs_shutdown' and 'dbs_dbreboot' may be reported in the SAP ASE error log when DBCC DBREBOOT with option 'shutdown_load' is executed. See KBA 2807357.
819553 A 12308 error, "Internal error : Invalid row id (Row < row-number > , Page < page-number > ) encountered in the table 'syscolumns' in database ' < database-name > '.", may be reported in the SAP ASE error log when high concurrent activity is taking place in a user defined temporary database. See KBA 2808782.
819559 The message, "timeslice < value > , current process infected at < value > ", in the module 'pthread_cond_timedwait' together with a stack trace which includes the modules 'MSOCSSendMsg' and 'ct_results', may be reported in the SAP ASE error log when the connection between SAP ASE Rep Agent and SAP Replication Server is down and synchronous stream replication is enabled in an HADR setup. See KBA 2807757.
819560 In rare circumstances, SAP ASE Rep Agent hangs on startup in an HADR setup due to a previous abnormal termination following a time slice error encountered. The call stack of the Rep Agent task will report the module 'upyield' followed by the modules 'ra_ci_main_thread', 'ra__ci_setup' and 'ra_ci_init_CI_lib'. See KBA 2807757.
819570 Under rare circumstances, a 3935 error, "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context. The transaction is currently in 'NULL XDES' state.", may be reported in the SAP ASE error log when before many 1105 errors were encountered. See KBA 2816667.
819607 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'OptBlock::_OptInitBlobTcIdBm' followed by a stack trace that includes the modules 'OptBlock::OptPhase2aInit', 'OptGlobal::GblAssignOptId' and ‘OptGlobal::_GblSearchEngine', may be reported in the SAP ASE error log when a SELECT query is executed on a user table that has a column whose datatype is TABLE. See KBA 2818520.
819618 When SAP ASE is configured with a server page size larger than 2K bytes, the replication of a jar image installed with the utility installjava, may fail due to badly formed LTL commands sent to SRS by Replication Agent.
819626 Workload capture takes longer time to stop especially when ASE configured with multiple online engines. The more engines configured, the more time it takes to stop the workload capture. Typically, it may takes over 1 minute when ASE configured with 32 engines.
819633 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qremap__obuf' followed by a stack trace that includes the modules 'fglk__send_prom_attn', 'fglk__promote' and 'fglk__check_and_promote', may be reported in the SAP ASE error log when a query involving SQL UDF was being executed in parallel and it attempted to promote the locks to a lock of a higher level. See KBA 2812380
819682 The message, "Adaptive Server Enterprise system exception ( < address > ) generated by a storage access violation.", in the module 'ise_mapsqlaccess' together with a stack trace which includes the modules 'revokeacct' and 'd_iseadmin' may be reported in the SAP ASE error log when sp_grantlogin is executed on Windows platform if either the Integrated Security mode or the Mixed mode is in use. See KBA 2815124.
819711 Sub-optimal performance may result during highly concurrent user login activity while accessing system tables SSYSSVROLES and SYSATTRIBUTES. An optimization is introduced that can be enabled by boot strapping Adaptive Server with trace flag 859. See KBA 2889793.
819746 The message 156 "Incorrect syntax near the keyword 'else'." can be seen when running the sp_dropdevice command after an upgrade. See KBA 2818609.
819751 Diagnostic enhancement to include spid, hostname, application name and SQL text for the message "stack_tracer: stack overflow last chance handler". See KBA 2886307.
819756 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'com__exctnume_copy' together with stack trace which includes the module 's__convert_nume' may be reported in the SAP ASE error log when a prepared statement performs UPDATE on numeric columns to NULL and the option DYNAMIC_PREPARE is set to FALSE and trace flag 11013 is enabled. See KBA 2819614.
819760 In rare circumstances, a 6103 error, "Unable to do cleanup for the killed process; received Msg 835.", may be incorrectly raised, or the previously raised critical error may get erroneously re-raised by the same spid (and different kpid), or the spid for network listener may hit a SIGSEGV error together with the stack trace showing 'pss_free_seqhdrs' reported in the SAP ASE error log. You can enable trace flag 8601 either during ASE start-up or at run time using DBCC TRACEON to avoid these errors. See KBA 2838149.
819773 Additional status flags information for the stream buffer will be reported for investigation purposes when a process (spid) issues a cancel operation. See KBA 2810952.
819777 Enable Secure User Store Support for optdiag with command line options -k and -H. See KBA 2825630.
819782 A 840 error, "Device ' < device-name > ' (with physical name ' < physical-name > ', and virtual device number < value > ) has not been correctly activated at startup time. Please contact a user with System Administrator (SA) role.", may be reported in SAP ASE error log when Adaptice Server is configured for HADR.
819795 The message "Current process infected with signal 11 (SIGSEGV)" can be seen in the ASE error log when multiple "alter database .. encrypt" or "alter database .. decrypt" commands are run simultaneously and there are not enough "number of worker processes" available to service the encryption or decryption tasks. See KBA 2822653.
819803 When the environment variable MALLOC_CHECK_ is set to 2, the Backupserver receives a SIGABRT signal during the cleanup phase of any connection established with Adaptive Server 16.0 SP03 PL07. The Backupserver process dies and a manual restart is required. The current fix implements fully the requirement for CR 699826. See KBA 2754515.
819807 A 454 error, "Number of elements in the largest IN list of 20732 exceeds the configured maximum value of 2000. Either use sp_configure 'max number of IN elements' to increase the value, or break the query into smaller pieces.", will be reported when a SELECT query is executed with a large IN list containing over 32767 elements, and the value of config option "max number of IN elements" is set to 2000. The 454 error is raised correctly, but the counted number of 20732 is incorrect.
819816 A 9204 error, "RepAgent( < database-id > ): Could not locate schema for object with id = ( < object-id > ), current marker ( < page-number > , < row-number > ).", may be reported when 'REORG REBUILD < table-name > WITH ONLINE' is executed in a database using synchronous replication under an HADR setup. See KBA 2823970.
819829 A 639 error, "Attempt to fetch logical page < > dbid < > failed - page is not currently allocated.", or a 692 error, "Uninitialized logical page < > was read while accessing < > . Please contact SAP Technical Support.", or a 694 error, "An attempt was made to read logical page < > , virtpage < > from virtual device < > for < > . The page was not read successfully. You may have a device problem or an operating system problem.", may be reported in the SAP ASE error log when a large empty database is loaded from a compressed dump on winx64 platform.
819831 In rare circumstances, in a replication setup the truncation of the SAP ASE transaction log may be prevented because REORG REBUILD command was unnecessarily marked for replication.
819845 In very rare circumstances, the message "current process infected with 11 (SIGSGEV)" in the module 'pg_get_alloc_page' together with a stack trace which includes the modules 'pg_oamscan_nextpage' and 'dol_oamscan_getnext' may be reported in the SAP ASE error log during the execution of a query. See KBA 2835036.
819846 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'rvm_has_decrypt_permission' together with a stack trace which includes the modules 'LeRun' and 'exec_lava' may be reported in the SAP ASE error log when a SELECT query against an encrypted column is executed. See KBA 2827203.
819874 The message, "current process infected with 11 (SIGSEGV)" in the module 'ldap_value_free' together with a stack trace which includes the modules 'login__ldapauth' and 'login_handshake' may be reported in the SAP ASE error log due to a memory leak when openLDAP authentication is switching Composed DN to Searched DN while connecting to Adaptive Server.
819901 In rare circumstances a 692, 834, 4216 or 4218 error can be reported in the SAP ASE error log when LTL mode replication is enabled and the Rep Agent configuration parameter 'multithread rep agent' is set to 'true'. The errors are seen after DUMP TRANSACTION is executed or when Rep Agent is started. See KBA 2885891.
819904 In rare circumstances, the message "timeslice - < integer value > , current process infected at < hexadecimal value > " or the message "current process infected with 11 (SIGSEGV)" together with a stack trace which includes the module 'ra_sender_thread' may be reported in the SAP ASE error log when shutting down Rep Agent in a database setup for LTL mode replication and the Rep Agent configuration parameters 'multithread rep agent' and 'multiple scanners' are set to 'true'. See KBA 2843602.
819970 A 3705 error, "Cannot use DROP TYPE with ' < type-name > ' because ' < type-name > ' is a table. Use DROP TABLE.", may be reported in the SAP ASE error log when dropping a table type in a database that was loaded from a database dump having a different database ID value from the current database. See KBA 2835023.
819977 A 712 error, "There is insufficient heap memory to allocate < number > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.”, may be reported during the execution of a query when frequent MERGE statements were run and their target table had an update trigger executed. Alternatively, the message, "Could not obtain required number < number-of-bytes > of resource of type 'Pss Heap Memory'. Since the process absolutely requires this resource, it is going to wait indefinitely till the resource becomes available. Please increase the configuration parameter 'heap memory per user'.”, may be reported in the SAP ASE error log. See KBA 2835522.
819996 In rare circumstances, under an HADR setup when synchronous replication is enabled, the message, "A message from Replication Agent ' < database-name > ' is coming: 'buffer_pool_size for < database-name > is adjusted from < larger-size > to < smaller-size > .", followed by the message, "A message from Replication Agent ' < database-name > ' is coming: 'buffer_pool_size for < database-name > is adjusted from < smaller-size > to < larger-size > .", may be reported in the SAP Replication Server error log.
820000 When the configuration parameter 'enable functionality group' is on, Adaptive Server will use a default textsize value of 2G bytes that cannot be changed anymore to another value with the SET TEXTSIZE command. See KBA 2857264.
820042 The message, "current process infected with 11 (SIGSEGV)", in the module 'hcb_tab_has_hcbidx' together with a stack trace which includes the modules 'alterdb' and 'altdb__row_storage_off_for_imrsdb' may be reported in the SAP ASE error log if turning off version storage of an IMRS-enabled database containing views that reference global temporary tables. See KBA 2853467.
820049 In rare circumstances, a 1204 error, "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.", together with a stack trace which includes the modules 's _get_usr_goal' and 'pss_init' may be reported in the SAP ASE error log when Adaptive Server runs out-of-locks. Alternatively a time slice error may be seen in the module 'listener'. See KBA 2838550.
820050 The message, "current process infected with 11 (SIGSEGV)", in the module 'sb__diag_print_sitebuf' together with a stack trace which includes the modules 'prSITE_INFO' and 'exec_dbcc' may be reported in the SAP ASE error log when DBCC SITE is executed. See KBA 2853512.
820057 The database timestamp '@@dbts' jumps by a large amount unexpectedly during LOAD DATABASE when a database dump is loaded from a pre-16.0 SP03 Adaptive Server version into 16.0 SP03 or greater. See KBA 2839301.
820121 The message "current process infected with 11 (SIGSEGV)" in the module 'ea__add_imrslog_dmap' together with a stack trace which includes the module 'ea_encrypt_decrypt_db_main' may be reported in the SAP ASE error log when encryption feature is enabled, an IMRS log device exists and IMRS feature is not enabled. See KBA 2840114.
820140 The message, "current process infected with 11 (SIGSEGV)", in the module 'syb_get_sess_pwd' together with a stack trace which includes the modules 'ra_open_context' and 'ra_sync_credentials' may be reported in the SAP ASE error log when Rep Agent receives a retry-able error such as a disconnection from SRS, in a database setup for LTL mode replication and the Rep Agent configuration parameters 'multithread rep agent' and 'multiple scanners' are enabled. See KBA 2847131
820151 The execution of CREATE LOGIN < login-name > WITH PASSWORD < password > DEFAULT DATABASE < database-name > may fail at the client-application side with a java.lang.NullPointerException error after upgrading t Adaptive Server from 15.7 to 16.0 because a NULL value for status5 column of master..sysdatabases may unexpectedly be seen.
820163 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'crdb__phys' together with a stack trace which includes the modules 'crdb_tempdb' and 'recover_tempdb' may be reported in the SAP ASE error log during the creation of a user temporary database while booting Adaptive Server. See KBA 2845915.
820167 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'imrs_get_pdes_imrs' together with a stack trace which includes the modules 'usedb' and 'boot__recover_and_online' may be reported in the SAP ASE error log, when a database dump is loaded from a pre-16.0 SP03 Adaptive Server version into an IMRS-enabled database and ASE is subsequently rebooted. See KBA 2861875.
820170 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322.
820193 In rare circumstances, the message "current process infected with signal 11 (SIGSEGV)" in the module 'undo_blockingcall_nowait' together with a stacktrace which includes the module 'shm__write_memsegment' may be reported in the SAP ASE error log causing Adaptive Server to hang when a Configurable Shared Memory Dump is setup with more than one dump threads enabled. See KBA 2854079.
820202 SAP ASE Rep Agent may terminate abnormally with a 9209 error, "RepAgent( < database-id > ): Missing datarow in TEXT/IMAGE/UNITEXT insert log record....", or a 9204 error, "RepAgent( < database-id > ): Could not locate schema for object with id = ( < object-id > ), current marker ( < page-number > , < row-number > ).", when REORG REBUILD is executed on a replicated table on which ALTER TABLE...WITH NO DATACOPY had previously been executed. See KBA 2890246.
820207 The message, "current process infected with 11 (SIGSEGV)" in the module 'pchk_fault' together with a stack trace which includes the module 'pchk_chk_txt_chain' may be reported in the SAP error log during CHECKSTORAGE when configured for multiple worker processes and one or more tables have LOB columns. See KBA 2845515.
820213 The message, "The Replication Agent thread for database ' < database-name > ' is not currently running.", may be reported when sp_stop_rep_agent < database-name > is executed, while the message, "A Rep Agent Thread for database ' < database-name > ' (dbid= < database-id > ) is already running.", is reported when sp_start_rep_agent < database-name > is run.
820220 New trace flag 11021 introduced whereby the built-in ISNUMERIC() behavior is reverted to pre-CR 767440 fix. See KBA 2053654.
820268 Under some circumstances, a remapping Error: 2805, may be seen in the error log on execution of sql statement containing constants in both the predicate and in a group by clause.
820270 In rare circumstances, when the monProcessActivity and monProcessStatement MDA tables are queried twice in short time, the values of the second query may be less than the values of the first query in LogicalReads or PhysicalReads column.
820290 The message, "current process infected with 11 (SIGSEGV)", in the module 'pipe_write' together with a stack trace may be reported in the SAP ASE error log during the parallel execution of a Lava query. See KBA 2694998.
820300 Lack of diagnostics prevents root cause analysis when an error 834, state 3 is raised which leads to transaction log getting full with below error message: Space available in segment < segment_name > has fallen critically low in database < dbname > . All future modifications to this database will be aborted until the transaction log is successfully dumped and space becomes available. Diagnostic reporting to error log has been introduced which are disabled by default and can be enabled under trace flag 891. Trace flag 894 can be enabled to raise exception 835, state 11 instead of reporting diagnostics. Previously introduced trace flag 893 is obsolete.
820315 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'do_needed' together with a stack trace which includes the modules 'redo_bt_rebldleafs' and 'ldxact' may be reported in the SAP ASE error log, when a database dump that was taken after a reorg rebuild command was run, is loaded with either trace flag 3303 or 3300 enabled. See KBA 2885784.
820329 The message, "timeslice < value > , current process infected at < value > ", in the module 's__setup_hostvars' together with a stack trace which includes the modules 's_xform_to_execute' and 's_normalize', may be reported in the SAP ASE error log when executing a user query having very large IN list with host variables if Statement Cache is on. See KBA 2857869.
820349 The message, "RepAgent( < database-id > ): Autoscaling: Warning: The 'buffer pool' cannot grow any further and the scanner will sleep on packages becoming available.", may be excessively reported and logged in the SAP ASE error log when the 'stream replication' option is enabled.
820350 The show_condensed_text(SSQLID, 'text') function may generate incorrect "column_name AS column_name" in select-list when a query is a subquery in the where clause. An example is that "select c1 from t1 where c2 in (select c3 from t2)" will be condensed to "SELECT c1 FROM t1 WHERE c2 IN (SELECT c3 AS c3 FROM t2)".
820354 The message, "A00: SYBMULTBUF ERROR: Internal error: unable to create errorlog buffer semaphore", may be reported in the SAP ASE Backup Server error log on a Sun Solaris system when DUMP DATABASE is executed after the '/tmp' file system was cleaned up by the end-user. See KBA 2855663
820381 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeLOBCache::LeLOBCacheInsert' followed by a stack trace that includes the modules 'LeRun', 'LeEvals::LeEvRun' and 'LeScalarOp::_LeOpNext', may be reported in the SAP ASE error log when executing sp_showplan to check another session. See KBA 2856735.
820449 The error message, "Backup Server: 9.5.2.1: Error in verification function for config option < configuration-option > .", followed by the message, "Backup Server: 9.4.2.1: There was an error when setting the configuration option < configuration-option > = < configuration-value > .", may be reported in the SAP Backup Server error log while booting the Backup Server and any of the configuration options "warn_level", "server_connections", "packet_size", "allocation_threshold" and "reserved_threshold" has had its non-default value changed.
820483 A 605 error, “An attempt was made to fetch logical page < page-number > ' from cache < datacache-name > . Page belongs to database 'sybsystemprocs' (31514), object 'sysprocedures' (5), index 'sysprocedures' (0), partition 'sysprocedures_5' (5) and not to database 'sybsystemprocs' (31514), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8).”, in the module ‘xxs__loglast’ together with a stack trace which includes the modules ‘hadr_getremote_status’ and ‘hadr_init’ may be reported in the SAP ASE error log occasionally in an HADR setup during the boot time of the Adaptive Server.
820516 In rare circumstances, Adaptive Server may return unexpected results if multiple cursors exist for a session and a FETCH < cursor-name > command is run after a DELETE command is executed which resulted in emptying few data pages from an All Pages Locked table and the cursor's query execution plan was using an index scan.
820521 When trace flag 4899 is enabled, Adaptive Server will perform additional row format validations when the rows being inserted into a table are formatted by the client application such as JDBC using bulk copy option.
820545 A 9219 error, "Internal error.", followed by a 9204 error, "RepAgent( < database-id > ): Could not locate schema for object with id = ( < object-id > ), current marker (0, 0)." may be reported in SAP ASE error log when a very large number of DDL commands are executed concurrently in a database using synchronous replication under an HADR setup.
820579 The message, "Backup Server: 4.23.2.1: baio_read: read /dev/ < raw-disk-path > : Not enough space.", followed by the message, "Backup Server: 4.141.2.16: [63] The 'write' call failed for database/archive device while working on stripe device '/dev/ < raw-disk-path > ' with error number 12 (Not enough space).", may be reported to the SAP Backup Server error log when DUMP DATABASE is executed on a database that resides on a raw partition device on the HP Itanium platform and the Adaptive Server configuration option "allow sql server async i/o" is enabled, while the configuration option "enable hp posix async i/o" is disabled. See KBA 2866900.
820871 The built-in get_appcontext() may return an incorrect value if it is executed in the same query with another built-in. See KBA 2881971.
820974 A 16382 error, "The configured maximum number of mutexes have already been created", may be reported in the SAP ASE Backup Server error log when many simultaneous dumps are executed. Sometimes the message, "BACKUPSERVER: bs_trap; process received signal 11", may also be seen resulting in the Backup Server implicitly shutting down. See KBA 2896338.
821002 A 3626 error, "The transaction was aborted because it used too much stack space. Either use sp_configure to increase the stack size, or break the query into smaller pieces. spid: %d, suid: %d, hostname: %.*s, application name: %.*s", may be reported when executing a large number of DML commands in a single batch and the trace flag 11013 is enabled. See KBA 2886254.
821005 The ASE configuration parameter 'HADR remote query timeout' cannot be set to 0 i.e. disabled. This restriction is now relaxed and the default value is changed to 0 i.e. disabled. See KBA 2900121. 


Read more...

Environment

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

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR, CR List, ASE 16.0 SP03 PL08, ASE SP03 PL08, SP03 PL08, 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.