/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in Adaptive Server Enterprise (ASE) 16.0 SP03 PL09. Please be sure to read the Disclaimer below.
If the EBF/SP has been released, check the CR list and coverletter at the support.sap.com.
Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.
| CR Number | Description |
|---|---|
| 203166 | A new configuration option 'default textsize' is added to make the default textsize server configurable where textsize is the maximum size of LOB data that can be sent for a SELECT query. This configuration value can be in the range of 0 to 2,147,483,647 bytes with 32,768 bytes being the default value. See KBA 2896934. |
| 403593 | In some circumstances, SAP Adaptive Server may not return any error message when setting the configuration option 'current audit table' to a non existent audit table. See KBA 2921876. |
| 493451 | The message for error 4325 has been enhanced to provide more context to the end-user when LOAD TRANSACTION WITH UNTIL_TIME is executed. It will be reported as "The transaction log start date ( < date > ) is more recent than the specified recovery until date ( < date > ), so it doesn't need to be loaded.". Additionally new error 4325 is added and will be reported as "Transaction log end date ( < date > ) is earlier than the specified recovery until date ( < date > ), so it has been loaded.". See KBA 2897980. |
| 562207 | A new column "restricted" has been added to the output of the system stored procedure sp_helprotect to implement the protection information about SET PROXY when RESTRICTED ROLE option is used in GRANT SET PROXY command. See KBA 2159486. |
| 635017 | Addition of new system stored procedure 'sp_mem' which will report the total procedure cache memory used by a session (spid), the number of prepared statements and their procedure cache memory consumption. |
| 636128 | When a database dump that was gathered with either 15.7 or pre-16.0 SP03 release, is loaded into pre-16.0 SP03 PL08 release, and after the database is upgraded by Adaptive Server, the database timestamp value may jump to an unexpectedly high value. See KBA 2572545. |
| 659119 | Two new messages are introduced to the showplan output for dynamic prepared statements. The message, "Executing a newly cached prepared statement (SSQL_ID = < value > )", will be printed for the first execution of a dynamic prepared statement. The message, "Executing a previously cached prepared statement (SSQL_ID = < value > )", will be printed when using a previously cached plan from statement cache. See KBA 2922900. |
| 718093 | The stored procedure sp_logintrigger does not warn the end-user, if the specified procedure does not exist, before successfully updating the login trigger. |
| 741286 | The system stored procedure 'sp_checkreswords' has been extended to check and report role names that are Transact_SQL reserved keywords. |
| 742869 | In rare circumstances, when the same table is created, referenced and dropped by concurrent prepared batches execution, segmentation violations errors may be reported in the SAP ASE error log together with a stack trace which includes the module 'open__byname'. See KBA 2169248. |
| 749605 | A new stored procedure "sp_optgoaldiff < optgoal_name1 > , < optgoal_name2 > " is introduced which prints the differences for active optimization criteria between two optimization goals. |
| 760591 | The MDA table master..monRepTruncationPoint may sometimes report inconsistent values for the columns LongestProcessingTime and TotalProcessingTime in an HADR setup when streaming replication is enabled. |
| 780130 | A 12850 error, "Command 'setcipher' encountered invalid cipher suite name 'Strong' in cipher, preferences are unchanged" may be reported if an attempt is made to set a ciphersuite with 'sp_ssladmin' before SSL is configured with 'sp_configure'. See KBA 2904067. |
| 787154 | In rare circumstances, Adaptive Server may be unable to switch the stream mode back to 'sync' from 'async' in an HADR setup when several user tasks have requested concurrently a mode switch to 'async' due to commit time expiration. |
| 787724 | The message, "WARNING: The transaction log for database ' < database-name > ' (dbid < database-id > ) can no longer be dumped due to user ' < user-name > ' (suid < user-id > ) executing DBCC.", may be reported in the SAP ASE server error log while running DBCC SHRINKDB_SETUP. See KBA 2897502. |
| 791716 | The message text for error 3474, "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 = < log-marker > .", error 3478, "During undo the page timestamp value is less than new timestamp from log. Page #= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log new timestamp= < log-new-timestamp > . Log record marker = < log-marker > .", and error 6902, "Page timestamp value falls between the old and new timestamps from log. Page#= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log: old timestamp=" < log-old-timestamp > ", new timestamp= < log-new-timestamp > . Log record marker = < log-marker > .", have been enhanced to also report the relevant transaction ID. For example, a 3474 error will be reported as "During redo the page timestamp value is less than old timestamp from log. Page #=641, object id =24, page timestamp=0001 00000000. Log old timestamp=0001 00001772. Log record marker = (10253, 17). Xactid = (10253, 16).". |
| 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. |
| 806011 | The error message, "Bad TDS response stream received from server. Unexpected token type received: 0", may be reported by an ODBC application when a SELECT query that contains an order by value greater than 255 is executed. |
| 811074 | The message, "Estimated remaining rollback time is < negative-value > seconds.", may be reported when KILL < spid-value > WITH STATUSONLY command is executed on a session that is in the process of rolling back a transaction. See KBA 2542597 |
| 811933 | Queries with GROUP BY involving large result sets using "group_hashing" strategy may underperform during execution. See KBA 2676005. |
| 812073 | A 326 error, "ALTER TABLE ' < table-name > ' failed. The table is 0-way partitioned, and a 1-way parallel plan was generated due to lack of parallel resources. Increase the value of 'max parallel degree' and 'number of worker processes' to at least 0, and try again.", may be reported when CREATE INDEX is executed while the set option 'quoted_identifier' is enabled, the table name contains ']' character and the configuration option 'enable compatibility mode' is on. See KBA 2898002. |
| 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. |
| 814043 | In rare circumstances, the built-in show_cached_plan_in_xml() does not return the query plan for queries in the statement cache when executing a statement in a cursor. See KBA 2697102. |
| 814338 | A new opimization criteria 'restrictive_greedy' has been added to avoid error 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.", while executing large queries during compilation phase. The same functionality is also available under TF 11838. See KBA 2901646. |
| 814901 | The message, "current process infected with 11 (SIGSEGV)", in the module 'memalloc’ together with a stack trace which includes the modules 'stu_findslot' and 'statgather’ may be reported in the SAP ASE error log during the process of statistics gathering when CREATE INDEX or a SELECT query involving sort is executed. See KBA 2641337. |
| 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. |
| 815762 | Syntax errors 102, 105, and 107 may be raised when accessing view or stored procedure referencing a table which has "." character in its name. Msg 102, Level 15, State 4: Server 'LINUX_160SP0', Line 2: Incorrect syntax near '[]'. Msg 105, Level 15, State 2: Server 'LINUX_160SP0', Line 4: Unclosed quote before the character string '" '. Msg 107, Level 15, State 1: Server 'LINUX_160SP0', Line 2: The column prefix 'mytable.Funds reservation field status var' does not match with a table name or alias name used in the query. Either the table is not specified in the FROM clause or it has a correlation name which must be used instead. Msg 107, Level 15, State 1: Server 'LINUX_160SP0', Line 3: The column prefix 'mytable.Foreign Trade: Screen ctrl of imp.data f' does not match with a table name or alias name used in the query. Either the table is not specified in the FROM clause or it has a correlation name which must be used instead. |
| 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. See KBA 2948438. |
| 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. |
| 817439 | KBA 2709213 - temp worktable not cleaned up in user temporary database (user tempdb) in ASE157 SP139 |
| 818346 | The execution of sp_dump_history may leave behind tables in the system tempdb database if the connection gets terminated abnormally, which will require an explicit manual drop of these tables by the end-user. See KBA 2753062. |
| 818593 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'OptGlobal::GblOptimize' together with a stack trace may be reported in the SAP ASE error log during the compilation phase of a stored procedure execution. See KBA 2946919. |
| 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. |
| 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. |
| 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. |
| 818713 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sqlexc_intercept_exception' together with a stack trace may be reported in the SAP ASE error log when view redefinition happens. See KBA 2771076. |
| 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. |
| 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. |
| 819222 | The reserved_pages value reported by 'sp_spaceused syslogs' keeps growing when the database option 'delayed commit' is enabled. See KBA 2747756. |
| 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. |
| 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. |
| 819340 | In rare circumstances, a 834 error with state 3, "Illegal attempt to change contents of buffer: ...", in the module ‘buffree’ together with a stack trace which includes the modules ‘buf_elcsearch’ and 'bt_delete' may be reported in the SAP ASE error log during the execution of a DML query while the buffer is being de-allocated and another session is in the process of changing it. See KBA 2869028. |
| 819416 | In rare circumstances, the message, "current process infected with 11 (SIGSEGV)", in the module 'fg_lock' or 'sendtext' together with a stack trace may be reported in the SAP ASE error log during the execution of a query which accesses LOB data. See KBA 2878406. |
| 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. |
| 819587 | In rare circumstances, a 678 error, "Invalid Buffer Cache Access: Could not open object ' < object-id > ' in database ' < database-id > '", together with a stack trace which includes the modules 'open_get_cacheid', 'Optimize' and 's_compile_stmt' may be reported in the SAP ASE error log while Adaptive Server is building the query plan of a DML query which involves an in-memory user temporary database. See KBA 2891210. |
| 819609 | In rare circumstances, some queries that are executed in parallel mode by SAP Adaptive Server may hang. DBCC stacktrace( < spid-value > ) when run on the parent and worker processes will report the modules 'pipe_read' and 'LePipeRWState::_LePrwsReadConstant' on the top of the stack. See KBA 2815487. |
| 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 |
| 819639 | The LogicalReads/PhysicalReads columns in monProcessActivity may not be updated when running an UPDATE STATISTICS command. See KBA 2812568. |
| 819692 | In rare circumstances, Adaptive Server may freeze unexpectedly when many alarms are in use. See KBA 2815362. |
| 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. |
| 819729 | In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the module 'ssql_lookup' may be reported in the SAP ASE error log when a query is executed and the statement cache is full. This will be followed by an implicit shut down of the Adaptive Server. See KBA 2835051. |
| 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. |
| 819810 | In rare circumstances, the message, "timeslice < negative-value > , current process infected" in the module 'sb__start' together with a stack trace which includes the modules 'sb_getsite' and 'dmpxact' may be reported in the SAP ASE error log when a remote DUMP TRANSACTION is executed. See KBA 2928400. |
| 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. |
| 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. |
| 819943 | A 2714 error, "There is already an object named < > in the database.", is incorrectly raised for prepared statements with a batch which has create table with one of the columns having a default value, insert into the table and select from the table. See KBA 2904035. |
| 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. |
| 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. |
| 820055 | [New Feature Request] Implemented an interface to mark a non-clustered index not to be used by any query with or without AP (AP which is not optgoal, Optlevel, timeout, optcriteria). |
| 820105 | New trace flag 14325 introduced whereby additional validations on All Page Locked tables (APL) are performed during the execution of UPDATE or DELETE commands. See KBA 2904122. |
| 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. |
| 820134 | In rare circumstances, the execution of dynamic prepared queries using correlated subqueries may fail with a syntax error when parameterized abstract plans are in use. See KBA 2904074. |
| 820144 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'OmniQuickPass::expandRangetableName' together with a stack trace which includes the modules 'internal_sql' and 'LeSQLRep' may be reported in the SAP ASE error log when SQL Replication is enabled and a DML query involving views or derived tables is run. See KBA 2850968. |
| 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. |
| 820178 | The message, "Invalid data found and rebuilt in segment accounting array for segment < segment-number > in database ID < database-ID > .", may be incorrectly reported in the SAP Adaptive Server error log for a temporary database during recovery. See KBA 2846731. |
| 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. |
| 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. |
| 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. |
| 820285 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'kbfalloc’ together with a stack trace which includes the modules 'boot__recover_and_online’ and 'db_build_dshmap‘ may be reported in the SAP ASE error log when the database dump of the master database is loaded on a newly created master device. See KBA 2901664. |
| 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. |
| 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. |
| 820346 | A 3508 error, "Attempt to set ' < database-name > ' database to single user mode failed because the usage count is < number > . Make sure that no other users are currently using this database and rerun CHECKPOINT" may be reported when the "sp_dboption ' < database-name > ', 'single user', true" command is executed to set the database into single user mode. See KBA 2948470. |
| 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. See KBA 2695973. |
| 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. |
| 820371 | When executing the command UNMOUNT DATABASE on a replicated database while Rep Agent is running, or when killing explicitly the Rep Agent Scanner or the Secondary Transaction Point Manager, in an HADR setup, one or several stack traces may be reported in the SAP ASE error log which could include the modules 'ra_ci_scanner_release_ci_interface', 'ra__cilib_thread_setup', or 'ra_ci_exception_handler'. Adaptive Server may become unresponsive or perform an implicit shutdown. See KBA 2900112. |
| 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. |
| 820386 | In rare circumstances, a 8213 error, "Failed to acquire address lock on object < object-name > " can be seen when performing inserts on a table containing an identity column and the database containing the table has an active DUMP DATABASE running. See KBA 2776030. |
| 820387 | The MDA table master..monRepSyncTaskStatistics may sometimes report inconsistent values for the columns AverageCommitToRAProcessTime and AverageRAProcessToPkgFlushTime in an HADR setup when streaming replication is enabled. See KBA 2882397. |
| 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. See KBA 2907191. |
| 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. |
| 820542 | The error message, "Backup Server: 7.4.2.1: Option 'CAPACITY': '-198967296' is an invalid value -- check the documentation for allowable values.", may be reported in the SAP Backup Server error log, when a database is dumped on a tape device with size greater than 2TB. See KBA 2864376. |
| 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. |
| 820548 | The message, "current process infected with 11 (SIGSEGV)", in the module 'LeCheckIdentInsUpdForMerge' together with a stack trace may be reported in the SAP ASE error log when a complex MERGE query is executed whose query plan involves SEQUENCER operator. See KBA 2908758. |
| 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. |
| 820609 | With predicated privileges, incorrect results may be observed for queries that use derived tables or views. See KBA 2866816. |
| 820627 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the modules 'showplan' or 'show_plan’ followed by a stack trace may be reported in the SAP ASE error log when executing sp_showplan to check another session. See KBA 2923564. |
| 820635 | The query on the monHANANonPushdown MDA table will fail with message "Command has been aborted" without reporting all required options for this table if 'enable monitoring', 'nonpushdown pipe active' or 'nonpushdown pipe max messages' is set as 0 (default). |
| 820672 | In rare circumstances, when a huge table is queried, some MDA tables like monProcessStatement, monProcessActivity and monSysStatement may suddenly jump to a huge value like 9223372034707304682 in LogicalReads column after the value reaches to 2,147,483,647 (2^31 -1). See KBA 2873194. |
| 820700 | In rare circumstances, a 834 error, "Illegal attempt to clean buffer: < allocation-page-meta-data > .", may be reported in the SAP ASE error log when LOAD DATABASE is executed and a earlier housekeeper task (HK_GC) has run out-of-log space (error 1105) in the database while deallocating a page which caused its allocation page remain unexpectedly kept. See KBA 2897499. |
| 820711 | SAP Adaptive Server may unexpectedly exit with no message reported in the error log when XML is in use. See KBA 2868544. |
| 820716 | In rare circumstances, the message "timeslice < negative-value > , current process infected" in the module 'lock_address' together with a stack trace which includes the modules 'bt__lockprevpg', 'bt__pgdealloc' and 'hkgc_garbagecollect' may be reported in the SAP ASE error log when many concurrent DML commands on DOL tables (Data Only Locked) are executed and index pages need to be shrunk. See KBA 2879991. |
| 820771 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log old timestamp= < > . Log record marker = ( < > , < > ).", or a 3478 error, "During undo the page timestamp value is less than new timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log new timestamp= < > . Log record marker = ( < > , < > ). Xactid = ( < > , < > ).", or a 12337 error, "Page ' < > ' in database ' < > ' was incorrectly found to be uninitialized when it was read. Recovery of this database cannot continue.", may be reported in the SAP ASE error log during boot time recovery after a non-polite shutdown of the Adaptive Server while REORG REBUILD command was running. See KBA 2877124. |
| 820774 | The error message, "Backup Server: 4.124.2.1: Archive API error for device='::test.dmp::000': Vendor application name= < UNINIT > ,Library version=0, API routine= < UNINIT > , Message=Unable to open API library for device '::test.dmp'. Library path is'/$SYBASE/ASE16_0/lib/lib.so'.dlopen() returned: Code=0, Message=/$SYBASE/ASE-16_0/lib/lib.so: cannot open shared object file: No such file or directory.", may be reported in the SAP Backup Server error log instead of the error message, "Backup Server: 4.131.2.1: Device: '::test.dmp'. The stream identifier '' has an incorrect length. A valid length is from 1 to 255 bytes long.", when DUMP TRANSACTION < database-name > to '::test.dmp' is executed. See KBA 2897457. |
| 820775 | In rare circumstances the message, “Current process infected with signal 11 (SIGSEGV)” in the module ‘PartNodeInfo::collocatedSite’ together with a stack trace may be reported in the SAP ASE error log during the optimization phase of a complex query. See KBA 2890244. |
| 820783 | In rare circumstances, a 4853 error, "Server has encountered badly formatted rows during bulk insert. The bulk client may be too old to format rows properly for this server version.", may be reported during bulk copy utility execution when the Adaptive Server trace flag 4899 is enabled and the total length of a row is greater than 256 bytes. See KBA 2893303. |
| 820817 | The message "current process infected with 11 (SIGSEGV)" in the module 'mda__populate_RepCoordinatorTable' together with a stack trace which includes the modules 'mda_populate_monRepCoordinator' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on MDA table master..monRepCoordinator is executed and another session concurrently has terminated the Adaptive Server Rep Agent tasks prematurely. See KBA 2895845. |
| 820841 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ridmap_lookup' together with a stack trace which includes the modules 'd__log_xlog_analyze' and 'd_imrslog_analyze' may be reported in the SAP ASE error log when DBCC IMRSLOG with the 'analyze' option is executed. |
| 820844 | The message, "Current process infected with 11 (SIGSEGV)", may be reported together with a stack trace which includes the module 'OmniQuickPass::generateSelectinto' in the SAP ASE error log when a SELECT INTO query with an aggregate function is executed on a database that has SQL Statement Replication enabled. See KBA 2879192. |
| 820857 | The partial rollback of a transaction may be unexpectedly discarded by SAP Replication Server replication, resulting in a data mismatch between the primary and replicate Adaptive Server databases when LTL replication is enabled. See KBA 2879588. |
| 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. |
| 820904 | In rare circumstances a time slice error may be reported in the SAP ASE error log together with a stack trace which includes the modules 'cudf_get_resref' and 'cudf_start_query' followed by an implicit shutdown of Adaptive Server if the C-UDF library could not be loaded because of a version compatibility conflict. See KBA 2901691. |
| 820948 | In rare circumstances, a performance degradation may be seen when executing queries and the optimization goal for ‘allrows_mix’ is in use. |
| 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. |
| 820976 | In HA setup, on ibmaix platform, sybha utility will hit an error while deleting the tmp file when sp_companion is run multiple times. See KBA 2884877. |
| 820988 | High load of cross database queries may lead to contention on sysocolumns system table. See KBA 2890197. |
| 820993 | The message, "ERROR: Cannot start due to invalid credentials", may be reported in webservice error log when runws is executed and the Adaptive Server configuration option "net password encryption reqd" is set to a non-zero value. |
| 820994 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log old timestamp= < > . Log record marker = ( < > , < > ).", or a 3478 error, "During undo the page timestamp value is less than new timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log new timestamp= < > . Log record marker = ( < > , < > ). Xactid = ( < > , < > ).", or a 12337 error, "Page ' < > ' in database ' < > ' was incorrectly found to be uninitialized when it was read. Recovery of this database cannot continue.", may be reported in the SAP ASE error log during boot time recovery after a non-polite shutdown of the Adaptive Server while REORG REBUILD command was running. See KBA 2877124. |
| 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: < > , suid: < > , hostname: < > , application name: < > ", 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. |
| 821013 | In rare circumstances, the message "ERROR in plc__discard() for plc < address > with MLDML lrs_to_discard( < non-zero-number > ) for dbid < database-id > is not between 0 and plc_count(0).", together with a stacktrace that includes the modules 'onlutl__apply_insdel_lr' and 'xls_discard_plc' may be reported in the SAP ASE error log when REORG REBUILD with ONLINE and HK WASH processes are running in parallel. See KBA 2896298. |
| 821036 | A 622 error, "Opentable was passed a varno of 250. Object '' in database 'tempdb' already has that session descriptor in use. This occurred while opening object id < negative-object-ID > in database id 2.", or the message, "current process infected with 11 (SIGSEGV)", together with a stack trace which includes the modules 'sdes_hookup' and 'GttTable::GttUsefulIndex' may be reported in the SAP ASE error log during the recompilation of a large query because of insufficient resources that would have allowed Adaptive Server to execute the query in parallel mode. See KBA 2896395. |
| 821038 | In rare circumstances on a multi-engine IBM AIX system, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'free' together with a stack trace which includes the modules 'mda_fill_and_send_monProcessSQLText.fdpr.chunk.1' or 'mda_fill_and_send_monProcessSQLText' may be reported in the error log when the monProcessSQLText MDA table is queried. See KBA 2895827. |
| 821042 | In rare circumstances, a 835 error with state 11, "Illegal attempt to change contents of buffer: ...", in the module 'smp_bufpredirty' together with a stack trace which includes the modules 'row_delete' and ‘bt__delrow’ may be reported in the SAP ASE error log during the execution of a DML query while the buffer is being de-allocated and another session is in the process of changing it. See KBA 2908677. |
| 821043 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'le_showPLL' followed by a stack trace that includes the modules 'showE_STMT' and 'showplan', may be reported in the SAP ASE error log when executing sp_showplan to display plan info of a query running on another session. See KBA 2895780. |
| 821061 | A 207 error, "Invalid column name < value > .", may be reported during the execution of a stored procedure that references temporary tables. This error is likely to be reported when nested stored procedures that create temporary tables at multiple nested levels are run. See KBA 2896397. |
| 821086 | In rare circumstances, a 834 error, "Illegal attempt to clean buffer: < sysdams-page-meta-data > ." in the module 'cm_dbclean' together with a stack trace which includes the modules 'buf_offline_database' and 'lddb_main' may be reported in the SAP ASE error log when LOAD DATABASE is executed and an earlier full database dump command execution was either interrupted or killed while the database option "allow incremental dumps" is enabled. See KBA 2893318. |
| 821098 | SAP ASE installer incorrectly displays "Please deselect any products that you do not want to configure now" during the step of 'Configure New Servers' when (by default) all options are already de-selected. |
| 821102 | When $SYBASE/WLA directory is readonly, WLACLIUtil will fail to start with exception like "log4j:WARN No appenders could be found for logger (com.sybase.workload.cli.WLACLIUtil)" even though a log file has been specified in command line with "-L" option. See KBA 2904572. |
| 821112 | The message, "The log page count in DBINFO for database < database-name > is inaccurate because dbi_freelogpages_at_ckpt ( < value-greater-than-zero) should be less than dbt_logsize (0). Run DBCC TABLEALLOC(syslogs, full, fix) on this database in single-user mode to make the counts consistent again.", may be reported in the SAP ASE error log during the recovery of a database upon Adaptive Server startup. This occurrence of the message is a false positive message and can be ignored because at this point in time dbt_logsize is not yet established. See KBA 2899024. |
| 821132 | In some circumstances, ALTER TABLE DROP PARTITION command may slowly execute especially on hyper-partitioned tables. The call stack for the session executing this command will often report the modules 'ptnc_fix_pctxt' and 's_cpytxt'. See KBA 2896288. |
| 821136 | The message "end of stack trace" is not printed in the SAP Adaptive Server error log together with the stack trace, when the I/O Controller thread hits a signal. |
| 821175 | If the value of the 'max SQL text monitored' configuration parameter is set without rebooting the ASE server, a query on the monProcessSQLText Monitoring Table may generate a 632 error. See KBA 2904567. |
| 821194 | Under rare circumstances, ALTER TABLE may be incorrectly applied to global temporary tables. |
| 821207 | Under rare circumstances, when a query against MDA tables results in a signal 10, signal 11 or time slice error, SAP Adaptive Server may shut down implicitly with a message like "Spinlock [ < spinlock-value > ] at address [ < address-value > ] owned by [ < kpid-value > ". See KBA 2901110. |
| 821245 | A new Adaptive Server configuration, 'ignore outdated plans' is added to skip the outdated plan check when populating the Active column in master..monCachedProcedures MDA table. |
| 821260 | WLACLIUtil may not report some DEBUG messages into log file even though the log level has been set as 5 (DEBUG) with the "-m" option. See KBA 2904575. |
| 821262 | Added restriction on SQL Anywhere database configuration file access in SAP ASE Cockpit for Windows. |
| 821265 | Additional checks added in DROP SERVICE command. |
| 821302 | Under rare circumstances, the Backup Server configuration file may be overwritten unexpectedly. See KBA 2921881. |
| 821331 | A 15497 error, "The password for the master key of database 'master' has not been set", may be reported when Adaptive Server tries to decrypt database sybsecurity during SAP ASE restart. See KBA 2922899. |
| 821334 | The message, "current process infected with 11 (SIGSEGV)", in the module 'LeLOBCache::LeLOBCacheInsert' together with a stack trace including the modules 'tdsrecv_dynamic' and 'tdsrecv_params' may be reported in the SAP ASE error log when inserting a parameterized value with setUnicodeStream into an image column using a dynamically prepared statement. See KBA 2909261. |
| 821339 | When executing dynamic prepared statements while SQL statement replication is enabled and the Adaptive Server configuration parameter 'streamlined dynamic sql' is set to 1, Rep Agent may terminate abnormally with a 9202 error, "RepAgent( < database-id > ): Nested replicated stored procedure detected. Transaction log may be corrupt. Please contact SAP Technical Support. (current marker = < page-number > , < row-number > )". |
| 821345 | A 871 error, "Process < process-id > is trying to release a latch on buffer < buffer-address > (dbid: < database-id > , pageno: < page-number > ) without holding a latch on the buffer.", may be reported in the SAP ASE error log when high concurrent activity is taking place in a user defined temporary database. See KBA 2916685. |
| 821350 | Sybmon command "findbuf < database-id > < page-number > 1" will report signal 11 error in the module 'd__findbuf_cachelet' when executed on a memory dump which does not include the page cache. See KBA 2924666. |
| 821351 | A Table valued UDF may return a non-null datetime value instead of null for a nullable datetime column when an explicit null valued is used for a SELECT statement. See KBA 2909254. |
| 821359 | Additional checks added in XP Server while loading the required DLL on Windows platform. |
| 821365 | In rare circumstances, the message "uaremove: alarm id 0 not within range", may be reported in the SAP Adaptive Server error log. |
| 821389 | A 12822 error, "Cannot create temporary table < table-name > . Prefix name < name > is already in use by another temporary table < table-name > .", is unexpectedly not raised when a stored procedure that creates the same temporary table is executed, causing an orphan temporary table to be left behind and requiring DBCC ORPHANTABLES to be then executed. See KBA 2910916 |
| 821437 | The message, "RepAgent( < database-id > ): Cannot allocate < value > bytes of memory. You may need to reconfigure the parameter 'replication agent memory size' with more memory.", may be reported in the SAP ASE error log after frequently executed queries on the MDA table monRepStreamStatistics. See KBA 2921916. |
| 821504 | In rare circumstances, SAP ASE Rep Agent might be shut down following the message "Streaming replication distribution CI Library error -3 with severity 2 and message 'Package(...) buffer is depleted. Total < number > , used < number > , requesting < number > .'. Rep Agent detected error 313 with message 'CI API call < function name > failed ' at line < line number > in file ra_ci_cmd.c". See KBA 2921889. |
| 821527 | The partial rollback of a transaction may be unexpectedly discarded by replication, resulting in a data mismatch between the primary and replicate databases. This applies to SAP Adaptive Server Replication Agent for setups using LTL replication only. See KBA 2879588. |
| 821535 | A 605 error, "An attempt was made to fetch logical page < page-id > from cache 'default data cache'. Page belongs to database < database-name > ( < database-id > ), object < object-name > ( < object-id > ), index < index-name > ( < index_id > ), partition < partition-name > ( < partition-id > ) and not to database < database-name > ( < database-id > ), object < object-name > ( < object-id > ), index < index-name > ( < index-id > ), partition < partition-name > ( < partition-id > ).", may be reported in the SAP error log together with a stack trace which includes the modules 'pg_latchoam' and 'ups__updstats' when UPDATE STATISTICS is executed on an All Pages Locked table while DML commands are concurrently executed on the same table. See KBA 2948437. |
| 821540 | Stored procedures which reference SQL UDF objects (User-Defined-Functions) may be compiled at each execution instead of Adaptive Server reusing already compiled and cached query plans. See KBA 2918013. |
| 821558 | Replication of statements using SQL based replication logic may fail for queries having ANSI joins. SAP Adaptive Server may incorrectly provide replication information to Replication Server and as a result the DSI thread may encounter problems while replicating data to the companion ASE. KBA 2937503 |
| 821640 | Error 614 "Adaptive Server accessed a row that has an illegal length of < length > while in data base < db_name > . < pageno > . The minimum row length is < length > . The page size is < page_size > ." may be raised in user tempdb or in system tempdb under high concurrent environment of create temp table. |
| 821649 | In an HADR setup, Rep Agent may not be notified in due time when user log caches are flushed to syslogs. See KBA 2924668. |
| 821748 | In rare circumstances, the message “Current process infected with signal 11 (SIGSEGV)” together with a stack trace which includes the module ‘cfree’ may be reported in the SAP error log in an HADR Always On setup. Alternatively the message “Current process infected with signal 6 (SIGABRT/SIGIOT)” together with a stack trace which includes the module ‘gsignal’ may be reported as well. See KBA 2883016. |
| 821753 | In rare circumstances, SAP Adaptive Server processes may be blocked while running EXECUTE ESP commands as shown by sp_who because the XP Server process hangs and will not respond back to these commands requests. When printing the execution stack trace of the XP Server process, for example with gstack < xpserver-pid > , the modules ‘srv_free�, ‘malloc� and '__lll_lock_wait_private' will be reported which is an evidence of the XP Server process hanging forever. See KBA 2937598. |
| 821779 | SAP ASE Cockpit installation writes encrypted sensitive information to the installation log file. |
| 821814 | In rare circumstances, a timeslice error in the module 'lc_findconn' together with a stack trace which includes the modules 'readremote', 'dpdb_poll_async_bs_rpc' and 'dpdb_main' may be reported in the SAP ASE error log when DUMP DATABASE is executed. See KBA 2928400. |
| 821864 | Enhancements added to the Rep Agent schema cache module allowing lesser look ups to sysobjects system table and more efficient hashing access for better performance while either searching or instantiating an object in the cache. See KBA 2946040. |
| 821959 | The installmaster file has a typo in query "select ::isolation fromm dummy". See KBA 2922993. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 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 PL09, ASE SP03 PL09, SP03 PL09, 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)