SAP Knowledge Base Article - Preview

2985561 - Targeted CR List for ASE 16.0 SP03 PL10

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 PL10. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the support.sap.com.

Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release. 

CR NumberDescription
489340 When inserting data into a TIMESTAMP column and the source data is the result of an aggregate built-in, SAP ASE will incorrectly insert into this column the current timestamp value rather than the source data. See KBA 2408246.
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.
699909 The execution of stored procedure sp_helpartition may produce unexpected results when the configuration option 'ansinull' is enabled.
773057 In rare circumstances, the message, “Assertion (0) failed in file memory.c”, together with a stack trace which includes the modules 'css_deallocate' and ‘memfree’ may be reported in the SAP ASE error log when a cursor with a large query text whose length is greater than 16KB and less than or equal to 2MB bytes is deallocated and the diagserver binary is in use.
774152 Whenever threadpool size is reduced using ALTER THREAD POOL command, it leads to 'kernel resource memory' leak. See KBA 2750513.
786753 The message, “Current process infected with signal 11 (SIGSEGV)”, in the module ‘_lopConsWktAccess’ together with a stack trace which includes the modules ‘_lopConsJoins’ and ‘s_compile_stmt’ may be reported in the SAP ASE error log when running a select query with joins and union all. See KBA 2190172.
792860 The system stored procedure sp_opt_querystats is enhanced to support user defined optgoals and transaction isolation level when reporting information about the optimization of a query.
799240 The message, “Current process infected with signal 11 (SIGSEGV)”, together with a stack trace which includes the modules ‘altdb__divide_diskmap’ and ‘altdb_shrink’ may be reported in the SAP Adaptive Server error log when ALTER DATABASE command with the "off" option is executed to shrink a database. See KBA 2323410.
802123 In rare circumstances, when one or more data or log devices are corrupted, dropping a database using such device(s) may cause the session to be terminated and may corrupt the master database.
804443 An incorrect result set may be returned during the execution of a SELECT query which includes an ORDER BY clause on an expression and ROWS OFFSET and LIMIT options are also in use. See KBA 2408819.
809701 When the cache size is changed by actions performed during the execution of sp_cacheconfig or sp_confighistory, the old cache size value is reported in 2K-bytes and the new cache size value is reported in K-bytes which causes inconsistency and confusion.
810542 When a dynamic prepared statement with the abstract plan hint "use with_recompile" is executed, Adaptive Server will not recompile the statement unexpectedly.
813940 CHAINED MODE fails to start a transaction for commands that don't access a table. See KBA 2952649.
814281 When using the "identity burning set factor" ASE generates burning sets that are about 5 times larger than they should be for identity columns based on INTEGER and BIGINT datatypes. See KBA 2624705.
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.
815921 A new column 'clientport' is added into master..sysprocesses system table and a new column 'ClientPort' is added to master..monProcess and master..monProcessLookup MDA tables to show client port numbers of user connections.
816908 Some new columns, 'NetType', 'ListenerAddress', 'ListenerPort', 'SSLCommonName', 'SSLCipherName' and 'SSLVersionName' are added to master..monProcess and master..monProcessLookup MDA tables to report network used by incoming clients. See KBA 2578601 for more details.
818435 In rare circumstances, on IBM systems LOAD operations may fail without a clear evidence that shows where the failure starts. Additional diagnostics have been added to the Backup Server to trace the events during the LOAD command execution accessible via trace flag -D16. See KBA 2757065.
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.
818657 Change default value of 'replication agent memory size' from 8M to 100M
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.
818726 A 208 error, “ < table-name > not found. Specify owner.objectname or use sp_help to check whether the object exists sp_help may produce lots of output”, may be reported when a SELECT query is executed using an in-memory database while its associated template database is renamed using sp_renamedb. See KBA 3009019.
818916 In rare circumstances, a 2601 error, “Attempt to insert duplicate key row in object ' < table-name > ’ with unique index ‘ < index-name > ’ < additional-data > ”, may be reported when MERGE commands are concurrently executed. Adaptive Server trace flag 16844 when enabled will print diagnostics information in such cases. See KBA 2785836.
819222 The reserved_pages value reported by 'sp_spaceused syslogs' keeps growing when the database option 'delayed commit' is enabled. See KBA 2747756.
819443 In rare circumstances, SAP Adaptive Server may ignore predicates when an outer join query is executed using a merge join with a hash union scan on an empty inner table, which can result to wrong results. See KBA 2850224
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.
819733 In rare circumstances, a timeslice error together with a stack trace in the module 's_xform_to_execute' may be reported in the SAP Adaptive Server error log when a query that includes the abstract plan hint 'with_recompile' is executed while the configuration option 'statement cache size' is enabled. See KBA 2817683.
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.
819811 A 2520 error, "Database named < database-name > not found; check sysdatabases", may be reported when DROP DATABASE ? is executed thru a prepared statement. See KBA 2823552.
819834 A 9992 error, "The actual number of rows ( < row-count > ) in DOL datapage < page-id > , partition ID < partition-id > , and count of #rows - 'nextrno' - < row-count > in the page header, do not match.", a 12308 error, "Internal error : Invalid row id (Row < row-id > , Page < page-id > ) encountered in the table ' < table-name > ' in database ' < database-name > '.", a 2512 error, "Table Corrupt: Cannot find the specified row number < row-id > , in index page < page-id > , partition ID < partition-id > , on data page < page-id > .", and a 7928 error, "Index < index-name > is not consistent; found < row-count > leaf rows but < row-count > data rows. Drop and recreate the index.", may be reported by DBCC CHECKTABLE when a Data Only Locked (DOL) data page is found to be invalid. See KBA 2889757.
819992 Extensions are added in sybmon utility, to capture the call stacks for CI native threads in a shared memory dump, to ease HADR debugging. However, for each replicated database, these extensions require the allocation of additional 24M-bytes memory from the Replication Agent global memory pool. Consequently the ASE configuration option ‘replication agent memory size’ should be adjusted.
820004 ASE version string and active trace flags are missing when a new error log is opened either using sp_errorlog or by errorlog rollover feature.
820103 A 8201 error, "Keep count of descriptor (objid= < object-id > , dbid= < database-id > ) was expected to be 1. Instead 0 was found.", together with a stack trace which includes the modules 'des_unkeep' and 'ptngetpages' may be reported in the SAP ASE error log during the execution of built-in data_pages() when the Adaptive Server configuration option 'number of open objects' is under configured. See KBA 2884324.
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.
820149 A 10353 error, "You must have any of the following role(s) to execute this command/procedure: 'sa_role, sso_role'. Please contact a user with the appropriate role for help.", may be reported when sp_dump_history is executed by a user having the 'oper_role' granted. See KBA 2844541.
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.
820187 When Rep Agent is configured for Multiple Paths Replication using Multiple Scanners with at least two replication paths defined and the Rep Agent is stopped with sp_stop_rep_agent, the message "timeslice < negative-value > , current process infected" may be reported in SAP ASE error log, together with a stack trace which includes the modules 'ra_free_all_raxacts' and 'ra__coord_driver'. See KBA 2960271.
820188 When Rep Agent is configured for Multiple Paths Replication using Multiple Scanners, it ignores the abnormal termination of a Scanner thread or a Sender thread.
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.
820378 A 925 error, "Maximum number of used databases for each query has been exceeded. The maximum allowed is 8.", may be reported when UPDATE STATISTICS command fails continuously for 8 times. See KBA 2994983.
820488 The message, "current process infected with 11 (SIGSEGV)", in the module 'qry_init_stats' together with a stack trace may be reported in the SAP error log when a derived table in a SELECT query is aliased with the name of an existing temporary table, and the configuration option 'optimize temp table resolution' is enabled. See KBA 2862371.
820557 A 156 error, “Incorrect syntax near the keyword 'else'.”, may be reported when installing sp_addtype system stored procedure while executing installhasvss. See KBA 2964898.
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.
820661 In some circumstances, a performance drop may be observed with SAP ASE 16.0 release, when a large batch of DELETE commands is executed and an index scan is chosen to perform the query. This can be worked around at the session level by executing ‘set postcommit_shrink off’ before the batch execution to disable the post-commit index page shrink chores. See KBA 2870613.
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.
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.
820832 In rare circumstances, a 692 error, “Uninitialized logical page ‘ < page-number > ’ was read while accessing database ' < database-name > ’ ( < database-id > ), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8). Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘checkpoint_db’, ‘ckpt_need_new_record’ and ‘wrongpage’ may be reported in the SAP ASE error log when the database option "trunc log on chkpt" is being enabled and after ONLINE DATABASE is executed in a database that was already online. Alternatively, a 1251 error, “The dbinfo anchor in the database 'database ' < database-name > ' ( < database-id > )' is already locked by the task. Nested access to dbinfo anchor is not allowed. Lock was acquired in file 'loaddb.c' at line 2165. This is an internal error. Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘xact_commit’, ‘xls_preflush’ and ‘lock_psema’ may be also seen. See KBA 2878392.
820948 In rare circumstances, a performance degradation may be seen when executing queries and the optimization goal for ‘allrows_mix’ is in use.
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. See KBA 3009450.
821059 A new option 'html' is added to sp_showplan system stored procedure allowing to generate the plan information for a given 'spid' and redirect it into an HTML file in the target folder as previously specified by SET STATISTICS PLAN_DIRECTORY_HTML command. See KBA 2890602
821114 Statements executing the replicate() built-in using a local variable or value from an expression results in a column header of 16384 bytes instead of the actual width. See KBA 2895352.
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.
821135 A 874 error, "Process < process-id > is trying to unkeep buffer < buffer-address > (dbid: < database-id > , pageno: < page-number > ) without releasing the shared latch it holds on the buffer.", may be reported in the SAP ASE error log when executing DBCC CHECKTABLE and while the diagserver binary is in use.
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.
821137 In a HADR environment, if the ct-lib controller thread running on the standby ASE terminates, then the primary ASE may run out of user connections over the period of time.
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.
821254 In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of 18432. Maximum allowed length is 16384.", may be reported when ALTER DATABASE OFF/LOG OFF is executed on a device that has many fragments allocated. Alternatively, the message, "Current process infected with 11 (SIGSEGV)" in the module 'altdb__free_device_fragments' together with a stacktrace may be reported in the SAP Adaptive Server error log. See KBA 2903224.
821261 A 267 error, "object '## < table-name > ' cannot be found.", may be reported when attempting to access a global temporary table which was created in an IMDB temporary database. See KBA 2903472.
821288 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeScanOp::LeOpSaveIOStats' followed by a stack trace that includes the modules 'LeDMLOp::_LeOpClose', 'LeEmittOp::_LeOpClose' and 'LePlanClose', may be reported in the SAP ASE error log when updating a user table with a in-row text columns and a foreign key constraint. See KBA 2964443.
821294 In rare circumstances, the message "Stack overflow detected", together with a stacktrace which includes the modules 'ucstackcrash' and 'sy_kill_task' may be reported in the SAP Adaptive Server error log, although there is no actual stack overflow, when a process is forcibly killed while it is holding a spinlock. This will result in Adaptive Server shutting down implicitly. See KBA 2905701
821318 Under rare circumstances, the message "timeslice < negative-value > , current process infected at kbfalloc" together with a stack trace that includes the modules 'create_destconst' and 'ss_texttounitext' may be reported in the SAP ASE error log when inserting a parameterized text value into a unitext column using a dynamically prepared statement. See KBA 2900443.
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.
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 > )". See KBA 2967909.
821344 A 692 error, "Uninitialized logical page ' < page-id > ' was read while accessing < partition-information > . Please contact SAP Technical Support.", or a 4216 error, "DUMP DATABASE failed in database < database-name > : unexpected end of log encountered on page < page-id > while scanning for page < page-id > .", may be reported when DUMP DATABASE is executed on a non recovered encrypted database after Adaptive Server reboot. See KBA 2964448.
821346 The execution of sp_encryption helpkey,'%key_mst%' may return an empty result set. See KBA 2936507.
821367 The SAP ASE Rep Agent configuration option 'priority' is taken into consideration for the scanner process under an HADR setup.
821391 In rare circumstances, the message, "Internal Ct-Lib/Cs-Lib error 16843057: 'ct_send(): user api layer: external error: This routine cannot be called because another command structure has results pending.'", may be reported when creating a remote table in a nested query on a proxy table. See KBA 2995039.
821406 A 624 error, "Adaptive Server failed to retrieve a row via its RID in database < database-name > because the requested RID has a higher number than the last RID on the page.", may be reported in the SAP Adaptive Server error log when a transaction is rolled back and involves a DML command as well an open cursor defined on an Allpages Locked Table (APL) which has a clustered index and one or more non-clustered indexes. See KBA 2994956.
821511 In rare circumstances, the message "Warning: The size of the stream buffer is too small ( < old-value > bytes). Use sp_config_rep_agent ' < database-name > ', 'stream buffer size', ' < new-value > ' to increase it." when preceded by a 9414 error whose text mentions "CI API call to SendMsgs() failed" may be erroneously reported in an HADR setup and can be ignored. See KBA 2946994.
821523 In rare circumstances, a 1159 error, "Attempt to locate LSA extent partition control block failed for dbid ' < database-id > ', objid ' < object-id > ', indid ' < index-id > ' and partition id ' < partition-id > '.", together with a stack trace which includes the modules 'soextfinish', 'undo_apl_aextent' and 'pg_ea_getextp' may be reported in the SAP ASE error log while executing a SELECT INTO query which internally attempts to create and sort a work table, but the internal transaction is being undone. See KBA 2986566.
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.
821539 A 11216 error, "Internal Ct-Lib/Cs-Lib error 33816856: 'cs_convert: cslib user api layer: common library error: The conversion/operation was stopped due to a syntax error in the source field.'.", may be reported on Windows during the execution of sp_dump_history. See KBA 2918657.
821549 A 2714 error, “There is already an object named ' < object-name > ' in the database.”, may unexpectedly not be reported when CREATE VIEW with name 'dbo.sysquerymetrics' is executed although a view with name 'sysquerymetrics' exists already. See KBA 2919190
821550 The message "Truncation error occurred. Command has been aborted." may be reported when executing 'sp_chgattribute < table-name > , < attribute > , 0, < float-value > '. See KBA 2964498.
821588 A 11283 error, "External file access is not enabled or not licensed", may be reported on Windows platform when sp_dump_history is executed. See KBA 2921227.
821629 A new error 3689, "Cannot allocate shared memory as 'max memory' limit of ' < value > ' pages has been reached. Please increase configuration parameter 'max memory' to allow additional shared memory allocation. Total physical memory allocated so far ' < value > ' pages.", will be reported when appropriate to the client and will be logged in the SAP Adaptive Server error log. See KBA 2943124.
821632 A 11080 error, "The definition tree (object id: < object-id > ) of computed column ' < column-name > ' is missing.", may be reported during the execution of a stored procedure which creates a temporary table with computed column and recompilation is happening while the configuration option "deferred name resolution" is enabled. See KBA 2923497.
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. See KBA 2986600.
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.
821671 The output for LOAD DATABASE WITH listonly = create_sql is enhanced to include the options WITH latch_free_index, WITH defer_index_recovery and the database type TEMPORARY in the CREATE DATABASE statement.
821687 The message, "Current process infected with 11 (SIGSEGV)", together with a stack trace including the module 'GtgGroup::GtInitGcPerGt' may be reported in the SAP ASE error log when a query that has nested aggregate functions including distinct with both GROUP BY and HAVING clauses is executed. See KBA 2503398.
821696 The information reported in column LogRecordsProcessed for MDA tables monRepScanners, monRepLogActivity and monRepScannersTotalTime may sometimes be inaccurate. See KBA 2964364.
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.
821756 In rare circumstances, ASE errorlog may see "Error: 19206 sp_shrinkdevice: Execute immediate SQL failed. SQL statement is: DISK RESIZE NAME = ' < device > ', SIZE = ' < size > '" while running sp_shrink command when the resulting disk size is more than 2,147,483,647B~=2048MB. See KBA 2976897.
821761 A 14612 error, “Inconsistent usage anchor: Dbid '1' Lstart '51200'.”, may be reported by DBCC CHECKCATALOG after having booted the SAP Adaptive Server with options ‘-w master’ and ‘-f’. The newly introduced option ‘fix_anchor_usg’ for DBCC DBREPAIR will allow to correct this error. See KBA 2968918.
821769 A 1265 error, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr= < lock-address > , lrmagic=f).", in the module 'lock_release' together with a stack trace which includes the modules 'unmountdb' and 'dbs_shutdown' may be reported in the SAP Adaptive Server error log when UNMOUNT DATABASE is executed and at least one session was found active in the target database which had session level attributes associated with it. See KBA 2933398.
821789 A 911 error, " Attempt to locate entry in sysdatabases for database < database-name > by name failed - no entry found under that name. Make sure that name is entered properly. ", may be reported when creating a user stored procedure which contains a delete-join query and the table names in the join query have both the database name qualified and the SAP Adaptive Server option 'deferred name resolution' is enabled. See KBA 2931133.
821809 The system stored procedure sp_monitorconfig when executed with option "number of remote logins” may report inaccurate values in columns ‘Num_active’ and ‘Max_Use’ which exceed the configured value for remote logins when a 7221 error, “Login to site ‘ < ASE-name > ’ failed.”, is frequently reported. See KBA 2932504.
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.
821833 The message, "Warning: Cannot resolve LDAP function ldap_controls_free.", may be seen in the SAP Adaptive Server error log during the server bootstrap even if LDAP is not enabled. See KBA 2932575.
821848 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'xls_flush_plcqueue' together with a stack trace that includes the modules 'xls_reconfig_plcblk' and 'xact__preparexact' may be reported in the SAP Adaptive Server error log during the execution of a multi-database transaction which involves low and full durability databases. See KBA 2947965.
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.
821919 In rare circumstances, a 14108 error, “Could not find partition descriptor for objid < object-id > , indid < index-id > , ptnid < partition-id > in dbid < database-id > .”, may be reported when ALTER TABLE MERGE PARTITION is run on an empty range partitioned All Pages Locked table having a clustered index and can result in some Adaptive Server resources not being released. See KBA 2948449.
821959 The installmaster file has a typo in query "select ::isolation fromm dummy". See KBA 2922993.
821979 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'LeScanOp::_LeOpAcquire' and ‘LePlanAcquire’ may be reported in the SAP Adaptive Server error log during the execution of a query. See KBA 2767557.
822007 The execution of DBCC ORPHANTABLES may incorrectly report the existence of an orphan table when the table is not orphan. See KBA 2938960.
822016 The message, "No server log file open; Using stderr for log", may be unnecessarily reported when the SAP Backup Server is booted. See KBA 2741519.
822078 Wrong results may be observed when table variables with identical names are used in different stored procedures. See KBA 3009033.
822102 A 2 error, "Message empty.", may be reported in the SAP ASE error log when inserting column name or number of supplied values does not match table variable definition. See KBA 2946944.
822118 A 9522 error, "The parameter that specifies the number of rows in a SET ROWCOUNT statement must be an integer with a value greater than 0.", will be reported when SET ROWCOUNT command is executed and an unsigned variable is passed to it. See KBA 2995048.
822136 After executing the command 'ALTER TABLE ... DISABLE TRIGGER' on several tables in an HADR setup without further logging activity on these tables, the user session in SAP Adaptive Server may eventually hang in the module ‘ra_ci_sync_pl_schema_request’.
822150 Under rare circumstances, select query on the MDA table 'monBucketPool' may show the bucketpool used (BucketPoolUsed column) value is greater than bucketpool used max (BucketPoolUsedMax column). See KBA 3009051.
822157 DBCC CHECKSTORAGE reports fault 100029 with fault_state 44 on OAM pages that have invalid bits set in the page header status field. The recommended action of running DBCC CHECKTABLE does not fix the fault. See KBA 2949021.
822164 The message, "Rep Agent on database ' < database-name > ' switched from mode 'async' to mode 'sync' because scanner reached end of log", and the message, "Rep Agent on database ' < database-name > ' switched from mode 'sync' to mode 'async' because timer on commit expired.", may be reported almost at the same time in the SAP Adaptive Server error log under a high workload in an HADR setup. The call stack of the Rep Agent scanner spid will show the modules 'ra__ci_stream_pkg_stats_pool_almost_exhausted' or 'ra__ci_stream_pkg_stats_shrink_pool'. See KBA 2994966.
822184 In rare circumstances, a hang may be seen when a remote procedure call (RPC) is executed between two SAP Adaptive Server instances. See KBA 2974458.
822205 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des_scavenge_for' together with a stack trace including the modules 'ptn__pdes_grab' and 'ind_ides_init' may be reported in the SAP ASE error log when Adaptive Server instantiates the metadata for a table in the metadata cache while the configuration option for 'number of open indexes' is under configured. See KBA 3009020.
822256 When MERGE is run on a table with a timestamp column, the timestamp column does not change when existing rows are updated. See KBA 2947932.
822314 A 3114 error, "Database master does not have an entry in Sysdatabases.", may be reported in the SAP Adaptive Server error log when loading a full database dump of the master database which was taken on a system that has been upgraded from pre-16.0 to 16.0 SP03 PL08 release. See KBA 2974405
822324 When the Adaptive Server option 'procedure deferred compilation' is enabled and the deferred compilation is processing a derived table in a system stored procedure, SAP ASE may incorrectly decide to recompile the procedure. See KBA 2969291.
822380 A 834 error with state 4, “Illegal attempt to clean buffer: < buffer-meta-data > ”, together with a stack trace which includes the modules ‘cm_dbclean’ and ‘lddb_main’ may be reported in the SAP ASE error log when LOAD DATABASE is executed. Alternatively the CHKPOINT WRKR process may hang in the module ‘cm__waitfor_io’ despite no active I/O presence. See KBA 2820054.
822391 In rare circumstances, a 2780 error, "maxlen( < value > is less than length ( < value > )", may be reported in the SAP Adaptive Server error log when an ALTER TABLE DROP COLUMN command followed by a SELECT command is executed. See KBA 3009034.
822402 In rare circumstances, a process may indefinitely sleep in the module 'xls_flush_plcqueue' and may block other processes running in the SAP Adaptive Server when the configuration option 'user log cache queue size' is enabled. The system may appear to hang and only restarting Adaptive Server will unblock this situation. See KBA 2594508.
822432 The message, "Assertion (!"ins_insert(): SSA_STMTLOCK is not set")", may be reported in the SAP Adaptive Server error log when a deferred update is executed and the diagserver binary is in use.
822434 A 3328 error, “Redo of 'CREATE INDEX' in transaction ID (0,0) for table name '', object ID '0' did not find 'sysobjects' system catalog log record. Recovery of database 'BLA' cannot continue.”, may be reported by LOAD TRANSACTION when loading a transaction dump that was taken after ASE was upgraded from SP02 to SP03 and a full database dump on SP03 was not taken first. This error is observed when the given database has the option 'enforce dump tran sequence' enabled.
822443 The messages, " < date-hour-timestamp > : A00: E-Diag: C_QATRACE command received." and " < date-hour-timestamp > A00: E-Diag: Received the trace flags bitmap. Tracing within sybmultbuf is enabled." are automatically archived in the SAP Backup Server error log unnecessarily.
822444 In a database setup for LTL replication, when Rep Agent is suspended, then resumed by executing the SRS administration commands 'SUSPEND LOG TRANSFER' and 'RESUME LOG TRANSFER', the message "process infected with signal 11" may be reported in the error log together with a stack trace which includes the modules 'kbfalloc', 'ra_malloc_mempool' and 'rep_agent_thread'. ASE eventually terminates. KBA 2958090.
822570 After loading a database dump from a platform having a different endianness, Rep Agent may fail to start. The message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation." may be reported in SAP ASE error log, together with a stack trace showing the modules 'memmove', 'anch__log_anchor' and 'ra_put_credentials' See KBA 2969667.
822622 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'ra_ci_stpmgr_thread' may be reported in the SAP Adaptive Server error log when sap_teardown is executed and the Rep Agent is stopped in an HADR setup. See KBA 2962144.
822660 In rare circumstances, data between primary and standby might be inconsistent under an HADR setup with DRC replication enabled when two ALTER TABLE commands are executed on different tables followed by DML executed on reverse order on these two tables.
822677 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'buf__writewait', 'buf__free_side_mass' and 'iocRunController' may be reported in the SAP ASE error log when DBCC INDEXALLOC is executed on an encrypted database and the configuration option 'enable LFB index' is active. See KBA 3010146.
822682 In rare circumstances, a spid may hang with COMPILING status as shown by stored procedure sp_who, when executing a disjoint SELECT with LIKE operators. See KBA 2965623.
822688 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'LeRun' may be reported in the SAP Adaptive Server error log during the execution of a query that uses the built-in isnumeric( < string > ) with a very large value of < string > .
822699 The message, "Assertion (E_CALLER_REORG_REBUILD(pss)) failed", may be reported in the SAP Adaptive Server error log when the built-in object_id( < object-name > ) execution fails and when the diagserver binary is in use.
822716 A 834 error, "Illegal attempt to clean buffer ...", together with a stack trace which includes the module 'rec__boot_recover_dbs', 'buf_online_database' and 'cm_dbclean' may be reported in the SAP ASE error log when sp_object_stats is executed while a database is undergoing recovery. See KBA 2982529.
822719 On Windows, dbisql client does not run when executed from the Start menu. See KBA: 3004717.
822785 A 10330 error, "DROP TABLE or DROP ANY TABLE permission denied on object dir_ < value > , database tempdb, owner dbo", may be reported when sp_dump_history is executed by a user which does not have 'sa_role' granted and the configuration option 'enable granular permissions' is set.
822806 Avoid multiple evaluation of has_role() built-in in the same query even if the built-in is a part of complex expression performed on each qualifying row. See KBA 3010179.
822941 When the session level setting SET SHOWPLAN is enabled, the output generated for queries performing SELECT DISTINCT on two or more columns may report the usage of 'HASH DISTINCT Operator' even if the session level setting SET DISTINCT_HASHING was disabled. See KBA 2976938.
822998 In an HADR setup, when SAP ASE Rep Agent performs a mode switch to 'async' while the stream is concurrently being closed, the message, "Current process (0x0) infected with signal 11 (SIGSEGV)", may be reported in SAP Adaptive Server error log together with a stack trace which includes the modules 'STSendMsgs', 'ra_ci_send_mode_switch_message' and 'ra__ci_background_task_wait_for_srs_ack'. See KBA 2975520.
823009 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'rvm__audit_dbreference' may be reported in the SAP error log when ASE user modifies the owner of encryption key created by another user and auditing system has been setup to audit this event and granular permissions are enabled. See KBA 2984145.
823014 The text of a stored procedure or trigger may be incorrectly stored in syscomments system table if the SQL text contains a session level SET statement to a numeric value followed by a command. See KBA 2975923.
823035 When the Rep Agent Coordinator thread is killed with the KILL command in an HADR setup, an infinite number of 9242 errors may be reported in SAP Adaptive Server error log. See KBA 2975483.
823043 In rare circumstances, a 14316 error, "The number field in syscomments for partition condition '****' in database '*' for table '****' indid '*' has exceeded the 32767 limit", may be reported in the SAP ASE error log when "ALTER TABLE ADD PARTITION" is executed. See KBA 2975007.
823050 After dumping and loading a database that has had ALTER DATABASE SHRINK run on it, sp_helpsegment may report negative 'used_pages' values for that database. See KBA: 2995964.
823119 In rare circumstances, a 678 error, "Invalid Buffer Cache Access: Could not open object ' < object-id > ' in database ' < database-id > '", together with a stack trace which includes the modules 'open_get_cacheid', 'Optimize' and 's_compile_stmt' may be reported in the SAP ASE error log while Adaptive Server is building the query plan of a DML query which involves a system temporary database or a user defined temporary database. See KBA 2891210.
823120 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'add_decrypt_bi' may be reported in the SAP Adaptive Server error log when performing a select against a table that includes encrypted columns. See KBA 2979605.
823126 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'adjust_const_desc', and sometimes the signal 11 is followed by looping messages, "FATAL UNHANDLED EXCEPTION", may be reported in the SAP Adaptive Server error log when storing T-SQL text using SET command in a local variable that contains one or more '+' operators along with "/* . . . */" style comments and the configuration option 'enable literal autoparam' is set. See KBA 2979907.
823135 An incorrect value for column 'QuiesceTag' may be reported when a SELECT query is run on table master..monOpenDatabases although a PREPARE DATABASE < tag-value > RELEASE has been executed before. See KBA 2980484.
823146 A 10330 error, “DROP TABLE or DROP ANY TABLE permission denied on object dir_ < value > ,database tempdb, owner dbo”, followed by a 10331 error, “Permission denied, database master, owner dbo. You need the following permission(s) to run this command: MAP EXTERNAL FILE.”, may be reported when sp_dump_history is executed by a user who does not have the same level of privileges as the previous user that executed the same system store procedure.
823199 In rare circumstances, a 1603 error, "Process priority 5 invalid or no process slots available", followed by the message "Failed to spawn delete sybdsam handler task.", may be reported in the SAP ASE error log when dropping a large amount of objects simultaneously and the Adaptive Server is configured for a single engine and the "number of user connections" is less than the number of objects being dropped. See KBA 2981553.
823200 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'dbinfo_boot_set_pg24objid' together with a stack trace which includes the modules 'dmpx__setup' and 'dbinfoupd' may be reported in the SAP ASE error log when DUMP TRANSACTION is executed. See KBA 2983946.
823228 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'pg_syslogs_extent_count' together with a stack trace including the modules 'th_fill_and_report_freespaceinfo', 'dbt__fill', and ‘lddb_main’ may be reported in the SAP ASE error log when LOAD DATABASE is executed. See KBA 3014622.
823236 The SAP ASE Rep agent will not be notified for log extension after DUMP DATABASE is executed for an in-memory-database which will prevent data changes from being replicated.
823253 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'is_numeric' and 'LeRun' may be reported in the SAP Adaptive Server error log during the execution of a query that uses the built-in sap_hextobin( < string > , < string-length > ) with a very large value for < string-length > . See KBA 3001411.
823263 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'mda__collectCachedStatements' together with a stack trace including the modules 'mda_populate_monCachedStatement' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on master..monCachedStatement is executed. This results in Adaptive Server implicit shut down due to spinlock SSQLCACHE_SPIN being held. See KBA 2985036.
823265 A comma might be missed among values in Object_status attribute of sp_help < table_name > .
823277 In rare circumstances, the message, “Thread CAP Parser( ) infected with signal 11.”, together with a stack trace which includes the modules ‘exc__appDumpStack’, ‘exc_terminate’ and ‘strlcpy’ may be reported in the SAP Replication Server error log when an unexpectedly empty log record is processed under an HADR setup resulting in the replication flow to stop.
823310 Under rare circumstances, some user tasks might remain in a RUNNABLE state forever, while binding an active process (SPID) to a different thread pool using system stored procedure sp_bindexeclass. See KBA 2987082.
823325 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 's_setupvar' and 'subgoals' may be reported in the SAP ASE error log on HP-UX platform when SELECT @@ssl_protocol is executed and the configuration option 'enable ssl' is enabled.
823328 In rare circumstances, connections from SAP Adaptive Server to Open server applications may hung. This hang was observed in the situation when the ASE site handler process is sleeping while it is freeing a SITEBUF data structure, and is awaiting for an existing connection to wake it up. The environment variable SITE_RETRIES whose default value is 30 seconds and it can be adjusted prior to bootstrap Adaptive Server to set the time for which ASE will wait before attempting to forcibly kill the site handler.
823356 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'ra__ci_stpmgr_execute' may be reported in the SAP Adaptive Server error log when the Rep Agent is stopped in an HADR setup. See KBA 3009036.
823375 In rare scenarios the message, “Current process infected with signal 11 (SIGSEGV)”, together with a stack trace which includes the modules 'pss__get_free_pss','pss_alloc'.'spawn_conn_hdlr'. See KBA 2676160
823413 A 806 error, "Could not find virtual page for logical page < page-number > in database < database-name > .", may be reported in the SAP ASE error log during the execution of a SELECT query whereby a worktable is required to sort a column whose size is close to the maximum width of a data row that can fit on a data page and there are NULL values in the sorted column. Alternatively a 614 error, "Adaptive Server accessed a row that has an illegal length of 0 while in database < database-name > . Page pointer = < page-address > , pageno = 24, status = 0x1, ptnid = -1, indexid = 0, level = 0. The minimum row length is < value > ?. The page size is 2048.", may be reported. See KBA 2531140.
823464 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'bufpagedestroy_noscan' may be reported in the SAP Adaptive Server error log when a SELECT query requires a worktable creation and the session option SET SORT_RESOURCES is enabled.
823487 In rare circumstances, the message, “Current process infected with signal 11 (SIGSEGV)”, in the module 'crt_allocpages_for_dft' together with a stack trace which includes the modules 's_execute' and 'sequencer' may be reported in the SAP ASE error log when a DML is run and the Adaptive Server is allocating disk space for a deferred created table but has run out of disk space in the database.
823492 The message, "Current process infected with signal 11 (SIGSEGV)", or "Adaptive Server Enterprise system exception generated by a storage access violation", in the module '_lopConsWktAccess' together with a stack trace which includes the modules 'lopConsJoins' and 's_compile_stmt' may be reported in the SAP ASE error log during the execution of a SELECT query when the configuration option "inline table functions" is enabled. See KBA 2992794.
823547 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memtextlen' together with a stack trace which includes the modules 'prE_PARAMs_buf' and 'prSQLTEXT', may be reported in the SAP ASE error log when executing DBCC SQLTEXT and a SELECT query is being executed in parallel. See KBA 2843657.
823687 Infected with Signal 11(SIGSEGV) in null() with altdb__upd_text_ptr on the stack may be reported in the SAP Adaptive Server error log when executing an ALTER DATABASE OFF command to shrink database. See KBA 3016683.
823700 A timeslice error in the module 'exc_raise' together with a stack trace which includes the modules 'quitfn' and 'LeExecSqlFunc' may be reported in the SAP ASE error log when killing a nested user defined function execution. The killed session will unexpectedly remain orphan and invisible by sp_who while it will continue to hold logical locks as shown by sp_lock. The current fix completes that of CR 785132. See KBA 2188555.
823714 The message, "Current infected with signal 11 (SIGSEGV)", in the module 'cri_fill_sarglengths' together with a stack trace which includes the modules 's__finish_alttab' and 'cri_ncrebuild' may be reported in the SAP ASE error log when CREATE INDEX and ALTER TABLE DROP both reference the same column and are executed together in a single batch. See KBA 3009010.
823732 The error message, “Backup Server: 4.141.2.40: [12] The 'CreateFile' call failed for database/archive device while working on stripe device '\\.\pipe\mypipe' with error number 2 (The system cannot find the file specified). Refer to your operating system documentation for further details.”, will be reported when DUMP DATABASE that is using a pipe archive device is executed. See KBA 3005089.
823768 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'err_pll_primary_processing' and 'LavaThreadDriverCleanup' may be reported in the SAP Adaptive Server error log during the execution of a query.
823853 When SSL configuration is not setup as expected on Linux, then the SAP Backupserver cannot be started and no error message is reported either on the console or the Backupserver error log.
823879 When replicating a large text or image value having an uncompressed size greater than 2GB, in a database setup for LTL replication, Rep Agent may terminate abnormally. The message, "RepAgent( < database-id > ): Received the following error message from the Replication Server: Msg 2056. Line < line-number > , character < column-number > : Incorrect syntax with '-'.", is reported in SAP ASE error log. See KBA 3009024.
823887 Under some circumstances, the message, "Internal error: SIGSEGV happened, please refer this issue to SAP Technical Support.", together with a stack trace in module VEH_Optimize() may be reported in SAP ASE error log but without detailed call stack information on Linux platform. Starting Adaptive Server with trace flag 16995 disables Vectored Exception Handling mechanism and allows detailed call stack information to be reported.
823936 In a replication environment setup for DDL replication, the DDL command 'CREATE VIEW' is erroneously replicated when it is executed inside a privately created system stored procedure or inside a replicated user stored procedure. In the latter case, the SRS DSI terminates after receiving ASE error 2714, "There is already an object named ' < view-name > ' in the database.".
824019 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'do__validate_stale_page_ts' together with a stack trace which includes the modules 'do_needed' and 'ds__recoverdbs' may be reported in the SAP ASE error log instead of raising error 3478 during recovery. See KBA 3014853.
824077 A 9965 error, "The entries in dbcc_config for database 'master' are either missing or invalid. Use sp_dbcc_evaluatedb to determine appropriate values for the entries and sp_dbcc_updateconfig to set them.", may be reported when DBCC CHECKSTORAGE or CHECKVERIFY against the master database if executed for the first time on 16.0 ASE SP03 PL09 or SP04. See KBA 3017156.
824095 Spinlock contention on data cache due to scans on the sysobjects table may be observed with highly concurrent workloads executing prepared statements. See KBA 3017684.

 


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 PL10, ASE SP03 PL10, SP03 PL10, 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.