SAP Knowledge Base Article - Preview

2694360 - Targeted CR List for ASE 16.0 SP03 PL07

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 PL07. 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
362501 Reporting of 1608 error, "A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.", to the SAP ASE log can be disabled when traceflag 7869 is switched on either at boot time or at run time. See KBA 2757008.
477889 When the Rep Agent configuration parameter 'trace log file' is changed while Rep Agent is running, the new value isn't dynamically taken into account.
577300 The message, "Message too long. Length = 1266008003", as opposed to the message, " < SQL_command > : Could not acquire < lock_type > due to < error_condition > .", may be reported in the SAP ASE error log when a transaction is started in a database that was first quiesced. See KBA 2705438
635018 A new function, show_prepared_statements(), is provided to display the SQL text for the prepared statements.
640973 No audit records are produced for audit event 58 when it is configured and an audit table is truncated. See KBA 2547617.
694618 The message, “The log page count in DBINFO for database < name > is inaccurate because dbi_freelogpages_at_ckpt < value > should be less than dbt_logsize < value > . 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 a database CHECKPOINT to help diagnose the origin of a 3475 error, “There is no space available in SYSLOGS to log a record for which space has been reserved in database < value > (id < value > ). This process will retry at intervals of one minute.”.
698404 backupserver: Invalid object id found in srv_deletemutex
699826 Allow DUMP and LOAD of an in-memory database when using single-sign-on authentication mechanisms, like Kerberos. See KBA 2754515.
729284 A 1703 error, "Failed to allocate disk space for a work table in database < database_name > . You may be able to free up space by using the DUMP TRANsaction command, or you may want to extend the size of the database by using the ALTER DATABASE command.", when reported is not reflected in the global variable @@error because the severity used was informational as opposed to insufficient resources.
732697 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sscan_copy_init' together with a stack trace which includes the modules 'onlutl_getTS_for_lpage' and 'pg_oamscan_nextpage' may be reported in the SAP ASE error log when running REORG REBUILD ONLINE after executing a 'drop column with no datacopy' on a LOB column.
744954 A 10866 error, "The value of 'max concurrently recovered dbs' ('1') must be less than the value of 'syb_default_pool thread count' ('1'). Use sp_configure to lower the value of 'max concurrently recovered dbs' or raise the value of 'syb_default_pool thread count'.", may be reported when 'sp_configure "max concurrently recovered db", 1' is run followed by a 5849 error, "Verification failed for parameter 'max concurrently recovered db'".
748461 The message "current process infected with 11 (SIGSEGV)" in the module 'open_byname' together with a stack trace which includes the modules 'col_open_range' and 'vu_redefine' may be reported in the SAP ASE error log when during the execution of a stored procedure a view statement requires redefinition as it was compiled with the configuration option 'procedure deferred compilation' enabled. See KBA 2017991.
760658 A 702 error, "Memory request for 26216 bytes exceeds the size of single page of 16384 bytes.", in the module 'memalloc' together with a stack trace which includes the modules 'LeCloner::LeClMixedDTSarg' and 's_compile' may be reported in the SAP ASE error log when multiple duplicate entries are present in an IN list of a SELECT query resulting in the session being terminated.
775241 In rare circumstances when SAP ASE is started in single user mode (-m) and a database which has async log service (ALS) enabled, is being downgraded, sp_downgrade may hang.
779584 A 4338 error, "Database < name > cannot be brought online by spid < value > because it appears to be in the process of being onlined by another session already.", or a 12594 error, "The database < name > cannot be brought online because we are unable to obtain exclusive access. The command has been aborted.", is reported with an incorrect severity when ONLINE DATABASE fails, resulting in the error not being set in the global variable @@error.
780558 A new configuration option, "max number of IN elements", is added to limit the number of elements in IN clauses of a query. The default value is 0 which indicates no limit as per existing behaviour. If a value is configured, the value must be between 256 and 128,000. See KBA 2138945.
781187 The error, "ct_connect(): directory service layer: internal directory control layer error: Requested server name not found", will be raised when trying to DUMP or LOAD an in-memory database using LDAP as directory service.
781928 In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc__findcachedSQLplan' together with a stack trace which includes the modules 'mem_getpages' and 'freeprocs', may be reported in the SAP ASE error log when LOAD DATABASE is run, while another session is reusing the same object descriptor, whose procedure buffer is in the process of being freed by the session running the LOAD command. See KBA 2162502 & 2270963.
785335 A 2714 error, "There is already an object named < tablename > in the database", may be reported during the recompilation of a batch of prepared statements which creates a user table in tempdb followed by CREATE INDEX or any DDL on the same table. See KBA 2368989.
785816 Cached statements using global temporary tables are shared among different users which is incorrect. In addition, the message, “Assertion (PERM_GET_APERM(pctx- > perms.bperms[0], pctx- > objtype) || pctx- > perms.bperms[0] == PERM_MNG_AUDITING)” together with a stack trace which includes the modules ‘has_privilege’, ‘ssql_save_SQL’ and ‘sqt_put_in_stmtcache’ may be reported in the SAP ASE error log when granular permission is enabled and the diagserver is in use.
792561 Updateable cursor scans do not apply on queries with sub-selects such as 'EXISTS' and 'NOT EXISTS' sub-queries. This restriction has now been relaxed when trace flag 11015 is enabled. See KBA 2246480.
792900 The commands GRANT and REVOKE are unexpectedly replicated when the permission applies to an object in the master database and the grantee is a role or a list of roles. As a consequence, when a GRANT command is executed on a user object in the master database, the SRS DSI thread is shutdown after receiving an ASE 208 error because the user object creation isn't replicated.
794360 The new message, "The SPQ log file in Replication Server is < number > percent full.", will be reported in the ASE error log under an HADR setup when the Rep Agent is configured for stream replication and it runs out of free packages during data replication.
798983 In rare circumstances, the message "timeslice -501, current process infected" in the module 'kbfalloc' together with a stack trace which includes the modules 'itl__realloc_aut_dict' and 'itl_au_update_xfer_mark' may be reported in the SAP ASE error log when BCP is executed with multiple threads.
799128 Under rare circumstances, a 821 error message, "Attempt to unhash buffer in cache 'tempdb_cache' at ' < address > ' with a buffer pageno of ' < x > ' and database id ' < x > ' with HASHED status set failed - buffer was not found. 'Page pointer = < address > , pageno = < x > , status = < x > , ptnid = < x > , indexid = 0, level = 0'." may be reported in the SAP ASE errorlog when a query is killed while creating a worktable for reformatting. See KBA 2430458.
800100 In some circumstances, a 2402 error, "Error converting characters into server's character set. Some character(s) could not be converted.", may be raised when executing a procedure but the procedure execution is not aborted leading to wrong results being returned for subsequent statements in the procedure when the server's and client's character sets are different and the same procedure has been run successfully previously and the query plan was cached. KBA: 2339369 - Procedure not exiting after Error 2402 reported
800348 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘ upwakeup’ together with a stack trace which includes the modules ‘ kbctMain’ and ‘ krtctskRun’ may be reported in the SAP ASE error log. See KBA 2769786.
800965 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des__free_txrcoldes' together with a stack trace which includes the modules 'proc__used_as_login_script' and 'dropobject', may be reported in the SAP ASE error log when a stored procedure is executed. See KBA 2479691.
802535 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'showE_STMT' followed by a stack trace that includes the modules 'show_plan' and 'LeRun', may be reported in the SAP ASE error log when executing sp_showplan if the statement has changed during the execution of sp_showplan. See KBA 2373058.
802812 Streaming replication using the Component Interface now also supports object level replication.
803603 A 3732 error, "Cannot drop index < value > because there are one or more isolation level 0 scans, or REORG command, active on table." together with a stack trace which includes the modules 'xact__commitxact' and 'dropi' may be reported in the error log when DROP INDEX is executed.
803791 The performance of the user_name() builtin has been improved when it is used multilpe times in the same query. See KBA 2404672
804096 The 'status2' column in system table 'sysdevices' has the 17th bit (Value 65536) set, but this is not documented. See KBA 2402811.
804756 The message, "Caught IOException: com.sybase.jdbc4.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed", will be reported when executing the sqldbgr with a re-directed input file and a local variable is set in sqldbgr. A corresponding stack trace that includes the modules 'sqldbg__setvariable', 'dbgrpc_control' and 'exec__native_rpc' will be reported in the SAP ASE error log.
806370 When auditing of sso_role is enabled, unexpected audit records may be generated against users without sso_role. See KBA 2441754.
806471 The message, "IMRS Garbage Collector or Pack Task for Database < database_name > failed to start with code -7.”, may be reported in the SAP ASE error log during the recovery of an IMRS enabled database when previously ASE was shutdown using the nowait option while the database was being shutdown by dbcc dbreboot("shutdown", < database_name > ) command.
806885 In rare circumstances, the message, "Caught an Unknown exception in handleRPC" may be reported in the Webservices log when executing "exec sp_webservices 'add'" with a duplicate service name. See KBA 2710519
807044 The severity level of the 9239 error message, "RepAgent( < database-ID > ): Cannot allocate < number > bytes of memory and will sleep until memory becomes available. Rep Agent Thread: < value > , status: < value > / < value > . Contact a user with System Administrator (SA) role to reconfigure Adaptive Server with more memory for Replication.", has been changed from 10 (Status Information) to 17 (Insufficient Resources).
807779 In rare circumstances, the message, "Assertion (scan_context) failed", together with a stack trace which includes the modules 'ra__ci_notify_syslogs_scanner_for_flush', 'ra_ci_notify_flush' and 'xact_commit' may be reported in the SAP ASE error log when streaming replication is enabled, the Replication Agent memory pool is exhausted and the diagserver binary is in use.
808387 New options, 'disable_dc' and 'enable_dc', have been added to the sp_procxmode system stored procedure, to disable and enable deferred compilation for a particular user stored procedure respectively. See KBA 2755124.
809421 In rare circumstances, after a column datatype of a Data-Only-Locked table is changed from INTEGER to CHAR/VARCHAR where the column is a part of a clustered index key, the 3121 error, "Index < table > .PK_ind (objid= < objid > , indid=2) may be invalid. It uses CHAR or VARCHAR columns in its key and was created under a different sort order ID ( < sort-order-id > ) or charset ID ( < char-set-id > ) than the ones on this server (SortOrd= < sort-order-id1 > , CharSet= < char-set-id1 > )", may be reported when a dump of the database is taken, and then loaded and an ONLINE DATABASE command is executed. See KBA 2755798.
809793 SAP ASE applies the 'allrows_mix' optgoal instead of the current session level optgoal at the query level if an invalid user defined goal is sent with the abstract plan.
809800 A 7130 error, "WRITETEXT with no log is not valid at this time. Database testdb1 must first be configured for this.", may be reported when WRITETEXT is run against an in-row LOB column while replication is enabled. Additionally when WRITETEXT is run against an off-row LOB column of an MVCC or On-Disk-MVCC enabled table while replication is enabled a ROWIMAGE log record is logged twice mistakenly.
810432 Allow IMRSLOGS threshold actions to restart when SAP ASE is rebooted and the free pages count is still below the defined threshold level for both single and multiple thresholds modes used for IMRSLOGS. The later mode is enabled with the SAP ASE trace flag 7439.
810467 A 1290 error, "Internal Error in lock manager routine: Attempted lock upgrade from update row to exclusive row in parallel query thread (family id < value > , spid < value > is Illegal.", together with a stack trace which includes the modules 'lock__ins_logical' and 'dol_update' may be reported in the SAP ASE error log when an UPDATE query is executed in parallel mode.
810647 A 806 error, "Could not find virtual page for logical page < n > in database ' < dbname > '", may be reported in the SAP ASE log when updating a base table column used in a materialized view with 'IMMEDIATE REFRESH' if the base table has a TEXT and/or IMAGE column(s). See KBA ##2531239
810764 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ind__get_sysindrow' together with a stack trace which includes the modules 'par_get_info' and 's_runtime_compile', may be reported in the SAP ASE error log when a stored procedure that creates temporary tables is executed and SAP ASE references the wrong object. Use the SAP ASE command line (boot) trace flag 11014 to enable the current fix. See KBA 2438077.
810863 auditinit fails to start if no sa password is provided.
811341 A 9502 error, "Data exception - string data right truncated", is not raised as expected when string values in variables are truncated. See KBA 2534801.
811723 In rare circumstances, the message, "JZ0R1: Result set is IDLE as you are not currently accessing a row." may be reported in the Webservices log file. See KBA 2559676
811764 A 644 error, "Index row entry for data row id < page#, row# > ) is missing from index page < value > of index id < value > of table < name > in database < name > . Xactid is < page#, row# > ). Drop and re-create the index." together with a stack trace that includes the modules 'bt_delete' and 'row_delete' may be reported in the SAP ASE error log on a non-clustered index when DELETE commands are executed and the housekeeper task is performing aggressive garbage collection concurrently. See KBA 2523141.
811970 In rare circumstances, a SQL query that is executed in parallel may hang in the module 'LePipeRWState::LePrwsRWVtuple' for the parent thread and the module 'LavaThreadDriverMain' for the worker threads participating in the query execution. See KBA 2567720.
812443 If trace flag 766 is turned on, occasionally "ELC_VALIDATION_ERROR: Page < address > is not allocated in procedure cache. pelc = < address > , chunksize = < chunk size > , engine id = < engine id > , validate_flag = < 0/1/2 > " or ELC_VALIDATION_ERROR: Page not marked free. pelc = < address > , chunksize = < chunk size > engine id = < engine id > , validate_flag = < 0/1/2 > ." may be falsely reported in the SAP ASE error log during heavy workload or when SAP Adaptive Server flushes an Engine Local Cache (ELC) memory to its global memory pool. See KBA 2581174.
812551 A 154 error, "LIMIT clause is not allowed in UNION.", will be reported when applying the LIMIT clause in a UNION query.
812977 Under rare circumstances, decoded function names in the SAP ASE stack traces may not be correct on Linux platform. See KBA 2698064.
813224 An incorrect value like '# < value > ' may be seen in the 'Memory Used' column of the sp_configure output when the 'max memory' parameter is set to a value greater than or equal to 2048 GB. See KBA 2748384.
813326 A 249 error, "Syntax error during explicit conversion of VARCHAR value '# < value > ' to a INT field", will be reported when executing sp_shmdumpconfig. See KBA 2623861.
813547 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322.
813580 In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'omni_ct_cancel' or 'uctSetIssuedCnt' or 'ct_poll' together with a stack trace which includes the module 'omni_ct_cancel' or 'omni_ct_close' may be reported in the SAP ASE error log when the SAP ASE configuration parameter 'cis idle connection timeout' is turned on. See KBA 2697042.
813847 Multiple threshold actions may be executed unwantedly to extend a database through a threshold action if the database is blocked due to long duration of a concurrent DUMP DATABASE execution. See KBA 2614731.
813917 The shared objects libjpeg.so and liblcms.so (JPEG.DLL/JPEG.PDB and LCMS.DLL/LCMS.PDB on Windows) have been added to ${SYBASE}/shared/ase/jvm.wl (%SYBASE%\Shared\ase\jvm.wl on Windows) JVM white-list file.
814051 An UPDATE query which involves tables not consistently qualified with the 'dbo' qualifier, may give wrong results when executed by a user who is not the database owner. See KBA 2619053.
814070 Under some circumstances, the Abstract Plan may be incorrectly stripped off when a dynamic SQL uses polymorphic built-in functions in a cursor statement. See KBA 2749022.
814190 A 16053 error, "The command 'LOAD TRANSACTION' with property 'WITH UNTIL_TIME' is currently not supported in SAP Adaptive Server, IMRS-database < database_name > .", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database.
814248 A new SAP ASE configuration option, "stream rep msg channel timeout", is introduced through sp_configure for an HADR setup using synchronous replication. During a failover, this option defines the minimum time in seconds before a mode switch can take place. The default value is 60 seconds.
814468 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'search_root_block_from_seqnode' together with a stack trace that includes the modules 'get_root_block', 'tdsrecv__mktree' and 'tdsrecv_open', may be reported in the SAP ASE error log when a user stored procedure with an execute cursor is executed. See KBA 2628762.
814478 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memmove' followed by a stack trace may be reported in the SAP ASE error log when executing subqueries that make use of built-in replicate(). See KBA 2630662.
814496 The SAP ASE Workload Analyzer will fail to replay dynamic SQLs in a workload with errors, "Dynamic SQL error - Prepared statement 'xxxxx' does not exist.", reported in the SAP ASE Workload Analyzer Error Report Dashboard if the capture starts after the dynamic SQLs have been prepared. See KBA 2628500
814572 A new MDA table, monSSLCertInfo, has been introduced to list the details of the SSL certificates used by SAP ASE. See KBA 2755239.
814590 DDLgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. See KBA 2632662.
814596 A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name1 > , object < obj_name1 > , index < idx_name1 > , partition < ptn_name1 > and not to database < db_name2 > , object < obj_name2 > , index < idx_name2 > , partition < ptn_name2 > ", may be reported in the SAP ASE error log after executing a CREATE CLUSTERED INDEX on a round-robin partitioned table with the dboption 'enforce dump tran sequence' enabled.
814651 The text of the 4305 error, "Specified file 'dump device' is out of sequence. Current time stamp is < datetime1 > while dump was from < datetime2 > .", has been improved to provide the dump file name in the message text. See KBA 2634147.
814654 SAP ASE fails to enforce check constraints on global temporary tables. See KBA 2634213.
814669 DBCC CHECKCATALOG output format is misaligned and appears garbled. See KBA 2634413.
814705 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'alloc_dirtychains' together with a stack trace which includes the modules 'CgLavaUtils::CgCompFakeTable' and 'GenLava' may be reported in the SAP ASE error log if a SELECT query on syslogsdetail is executed while SAP ASE is booted with trace flag 3608 whereby only the master database is recovered. See KBA 2635388.
814754 A batched language command executed with DYNAMIC_PREPARE set to FALSE can result in an open object and cached statement to be consumed and unable to be reused or freed for each batch. See KBA 2613604.
814755 Occasionally the execution of a SELECT query on a Data Only Locked (DOL) table may lead to incorrect results when the query optimizer uses a composite index of this table in order to access the data whose index leading column datatype is a fixed length CHAR and it contains special ASCII characters, such as CHAR(10), CHAR(31) or CHAR(1). See KBA 2636753
814910 In rare circumstances, the message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation" or an "infected with 11 (SIGSEGV)" in the module 'get_resrow_size' together with a stack trace which includes the modules 'LopInsert::_lopCodeGen' and 's _compile_stmt' may be reported in the SAP ASE error log when a query is compiled and an object ID has been recycled by Adaptive Server causing a conflict between a definition time object ID and a Light Weight Procedure (LWP) object ID. See KBA 2788678.
814921 An 16367 error, "EXECUTE AS OWNER procedures cannot be created by an alias or with the SETUSER command when the procedure has SQL statements that reference objects across databases. Create the procedure from a non-impersonated session.", may be reported in the SAP ASE error log when an impersonating user tries to execute a cross-database stored procedure which was created with the 'deferred name resolution' configuration enabled. See KBA 2755255.
814960 In rare circumstances, SAP ASE sessions may hang in the module 'des_do_get' when attempting to access a table, as a result of a 2622 error, "Insufficient room on this page to insert a row of length < row length > . Page pointer = < page address > , pageno = < page number > , status = < page status > , ptnid = < partition id > , indexid = < index id > , level = < level > , pnextrno = < next row number > .", hit by another session together with a stack trace which includes the modules 'des__scavenge' and 'stat_pdes_flush_datachange' reported in the SAP ASE error log while an object descriptor is reused to host metadata for this table. See KBA 2670244.
815210 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ResRelOp' followed by a stack trace that includes the modules 'ResRelOpProcess' and 'CgpPop::_CgpPePredBmToScalar', may be reported in the SAP ASE error log when a query is executed that involves an OUTER JOIN on a materialized view and a non-materialized view that return a constant column and there is a predicate on this constant column.
815377 In rare circumstances on heavily loaded systems, a 539 error, "Unexpected internal access methods error 0, state 30.", or a 3914 error, "Illegal internal transaction status. This is an internal system error.", may be reported for a query involving temporary refresh pre-computed result set.
815553 A 622 error, "Opentable was passed a varno of 0. Object ' < table_name > ' in database ' < database_name > ' already has that session descriptor in use. This occurred while opening object id < object_id > in database id < database_id > .", may be reported in the SAP ASE error log after upgrading from ASE version 16.0 SP02 to version 16.0 SP03 or upgrading from ASE version 15.7 to version 16.0 SP02 when a SELECT statement references a table having computed columns which involving SQL user defined function. See KBA 2686324.
815569 The configuration file offset record in the decompressed dump is not correct and hence sybmon cannot extract the original configuration file.
815581 A 11060 message, "This statement has exceeded the maximum number of recompilations (20). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support", may be reported during workload replay with the "Reset server time to source workload capture time" option selected and a VIEW, that is created after the workload captured time, is accessed. See KBA 2661224.
815594 Under some circumstances, the output from executing the sp_opt_querystats procedure with the 'option_show_long' option may have malformed text with random newline breaks over some words.
815626 In rare circumstances, a 820 error, "Attempt to dirty non-log buffer BUF= < value > , MASS= < value > , ... Pinned xdes= < value > spid= < value > which is in I/O.", together with a stack trace which includes the modules 'bufpindirty' and 'plc__flush' may be reported in the SAP ASE error log when the syslogs system table is bound to a dedicated log cache having large buffer pool sizes configured. See KBA 2747852.
815693 In an SAP HADR system, the fault manager failed to start the heartbeat when multiple tempdb is configured in SAP ASE. See KBA 2672505.
815706 On Windows platforms, the message, "Parameter 'start address' (number 1) to DBCC command 'bytes' has invalid value/type." may be reported in client console, or the printed address doesn't match the specified address in DBCC BYTES command when DBCC BYTES (address, length) is executed.
815740 The message "current process infected with 11 (SIGSEGV)" in the module 'site_login_cancel' with a stack trace followed by the message "Scheduler infected: exiting" may be reported in the SAP ASE error log. See KBA 2682423.
815760 A new backup server configuration parameter, 'retaindays', has been added to specify the number of days that a database or transaction dump will not be writable.
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.
815803 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubffreef' followed by a stack trace that includes the modules 'ufclose', 'dir_sendtext' and 'DIRRemoteAccess::sendText', may be reported in the SAP ASE error log during concurrent access of big files via a proxy table. See KBA 2672421.
815827 sp_help ' < proc_name > ' may report an incorrect fully qualified parameter list when the procedure < proc_name > is created with TABLE type or TABLE variable parameters.
815832 A 11021 error, "Function < function_name > invoked with wrong number or type of argument(s).", may be reported in the SAP ASE error log when upgrading a SAP ASE 16.0 SP03 PL03 or later version and an in-lined table-valued UDF is accessed. See KBA 2748456 and 2738592.
815833 A query, which is selecting from a view with a left outer join and a predicate in where clause, and the view definition contains a subquery in 'When exists' which is wrapped in 'case' clause and a left outer join is used, may return wrong results which don't take the predicate into account. See KBA 2690931.
815867 A 100015 soft fault (page loop error) may be reported by sp_dbcc_faultreport after executing a DBCC CHECKSTORAGE on a database that contains about 15000 syspartitions rows. See KBA 2670254.
815981 A 208 error, "## < 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 stored procedure materializes a global temporary table under a transaction that is rolled back afterwards. See KBA 2672877.
816000 A 15101 message, "There is insufficient memory to allocate < n > bytes. Please increase configuration parameter 'messaging memory', or try again when there is less activity on the server." may be reported when a large value has been set for the configuration parameter 'messaging memory' and real time messaging queries are executed in multiple concurrent sessions. See KBA 2674952.
816001 KBA 2754612 - The message, "The stored procedure < sproc_name > has an old format and cannot be used internally by Adaptive Server until it has been upgraded. You can execute DBCC UPGRADE_OBJECT( < sproc_name > ) to avoid this.", may be reported during an upgrade of SAP ASE to a higher version due to the system stored procedures being created with 'deferred name resolution' enabled in the pre-upgrade version.
816003 Update the version of Jetty used for SAP ASE Webservices to Jetty 9.4.11.
816009 In rare circumstance, a 889 error, "Internal error. Contact SAP Technical Support for help. BCM thread found MASS < buffer_address > in database < database_name > ( < database_ID > ) and cache < cache_name > ( < cache_ID > ) in an unexpected state < value > ", may be reported if latch free indexes are created and the house keeper garbage collector task (HKGC) is enabled in the database. See KBA 2686353.
816013 In rare circumstances, a 3935 error, "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context. The transaction is currently in 'Command-attached' state.", may be reported when executing a query in STATEMENT SNAPSHOT ISOLATION mode against a Multi-Version Concurrency Control (MVCC) enabled table when the configuration option 'allow statement rollback' is enabled.
816024 In rare circumstances, when the Backup Server is shut down with "shutdown SYB_BACKUP", the SITE HANDLER for the SYB_BACKUP connection never gets released in SAP ASE. Then on a successful restart of the Backup Server, the SITE HANDLER is unable to connect to the Backup Server. This causes that all subsequent DUMP commands are hanging in the SAP ASE Server. SAP ASE traceflag 8024 (along with 3623) should be enabled to collect diagnostics in the SAP ASE log. See KBA 2669570.
816025 The message, "A fatal error has been detected by the SAP Java Virtual Machine: EXCEPTION_ACCESS_VIOLATION (0xc0000005)", together with the error message, "NTPCI__exit(1); Native Thread failed to unwind while attempting to shutdown the PCI", may be reported in the SAP ASE error log when loading sunec.dll on Windows platforms. See KBA 2687973.
816034 In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE and also behind the last hole fixed by the Fix-Phase of imrslog boot-time recovery.
816054 The message, "Current process infected with signal 11(SIGSEGV)", followed by a stack trace that includes the modules 'bt__col_cmp_noopt' and 'bt__nonlfrow_cmp' may be reported in the SAP ASE error log when a SELECT query with GROUP BY that contains expressions is executed. See KBA 2681394.
816062 The message, "ERROR in plc__lrtopage() for plc < address1 > , dbid < database_id > , log record from plc at offset < address2 > with len_logrec < size > does not fit in log page with size < page_size > .", together with a stack trace which includes the modules 'xact__commitxact' and 'xls_flush_plcqueue' may be reported in the SAP ASE error log when a multi-database transaction is committed and one branch of the transaction involves an in-memory enabled database. See KBA 2709753.
816073 The message "enp_aesEncrypt: CCLCipherCtx_all failed with error: 0xa0100014." may be found in the SAP ASE errorlog when the length of the user password which is used for the Job Scheduler is either 7 or 23. See KBA 2677850.
816078 In rare circumstances under an HADR setup, the coordinator process of SAP ASE RepAgent may hang in the module 'ra__ci_coordinator_waits_for_switch_ack' preventing the replication flow to continue.
816102 The message "current process infected with 11" in the module 'norm3_expr' together with a stack trace which includes the modules 'norm3__process_case' and 'crcpc_norm' may be reported in the error log when computed columns is queried in a SELECT statment. See KBA 2413073.
816107 The active Rep Agent trace flags will now be reported in the SAP ASE error log when a Rep Agent is started. When no Rep Agent trace flag is active the message, "RepAgent( < dbid > ) no active traceflags.", will be reported. Otherwise the message, "RepAgent( < dbid > ) active traceflags: < TF1 > , < TF2 > , ..." will be reported.
816125 A 11138 error, "Failed to create role < role_name_992 > , because this exceeds the maximum number roles limit of '1024'. Please delete roles you don't need and rerun your command.", may be reported when a user tries to create the 992nd role. See KBA ##2679595
816178 In rare circumstances, when DBCC REINDEX() or SP_FIXINDEX hit out of memory error 1105, "Can't allocate space for object ' < object-name > ' in database ' < db-name > ' because ' < segment-name > ' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment", on a DATA-ONLY Locked table with a placement index, then subsequent commands scanning the same object may fail with either of error 696, "An attempt was made to fetch logical page ' < page-number > ' from cache ' < cache-name > '. Page belongs to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > and not to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > . Restart of ASE will clear the error. Please contact your System Administrator for help.", or error 1142, "Invalid OAM Page < page-number > . Found pstat= < stats > , object= < obj-id > , database= < db-id > , indid= < ind-id > .", or error 605, "An attempt was made to fetch logical page ' < page-number > ' from cache ' < cache-name > '. Page belongs to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > and not to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > .", or error 692, "Uninitialized logical page ' < page-number > ' was read while accessing < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > . Please contact SAP Technical Support.".
816203 updatease fails to start the SAP ASE server if the master device file size is larger than 4GB.
816272 The system stored procedure 'sp_activeroles' may show only the latest granted user defined predicated role, even if multiple user defined predicated roles are granted to the login, when SAP ASE configuration option 'enable predicated privileges' is enabled. See KBA 2684433.
816290 The number of free log pages in a database could be incorrectly reported by the sp_helpdb command, if the command ALTER DATABASE [LOG] OFF is used to remove pieces from the last database fragments and the command DUMP DATABASE WITH SHRINK_LOG is executed to remove the resulting fragment holes.
816322 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 select query_text in parallel.
816352 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'yylex' together with a stack trace which includes the modules 'sqlpars' and 'internal_sql' may be reported in the SAP ASE error log when many white space characters appear in the query text following an SQL keyword, resulting in either a zombie task being created (in ASE 15.7 SP140 or ASE 16.0 SP03 PL04) or SAP ASE unexpectedly shuts down (in ASE 16.0 SP03 PL05 where a double signal is regarded as a fatal condition, but TF 2917 can be used to revert behaviour to the zombie task creation). See KBA 2686240.
816355 In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that there are some cross-log transactions whose sysimrslogs records are present on a sysimrslogs page that has a higher timestamp than that of the syslogs page containing the OQID rid.
816391 The dump history file contains unexpected 'dump.error' messages at a time when SAP ASE reports 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." and the log truncation is not successful. See KBA 2686302.
816397 A 1526 error, "Sort failure. The configure size for data cache ( < name > ) is not sufficient to handle the sort buffers ( < value > ) requested. Please reconfigure the data cache or sort buffers and try the command again.", may be reported during the execution of a query as a consequence of a memory leak caused by the extensive usage of the built-in set_appcontext() and rm_appcontext(). See KBA 2748397.
816400 In rare circumstances, the progress status message, 'Backup Server: 4.188.1.1: Database < database_name > : < value > kilobytes ( < value > %) DUMPED.', may be truncated unexpectedly when DUMP DATABASE is executed. See KBA 2687371.
816407 The message, "Current process infected with signal 10 (SIGBUS)" in the module 'obfuscate_ldapacpwd' together with a stack trace which includes the modules 'ua__setldapacct' and 'sa_ssladmin' may be reported in the SAP ASE error log when sp_ldapadmin is run with command set_access_acct as part of LDAP configuration.
816409 A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after having dropped a user database which is marked suspect and is On-Disk MVCC enabled.
816425 A memory leak in the PSS memory pool may be observed when there are multiple executions of 'SET ROLE WITH PASSWORD ON' in every other 'SET PROXY' session without a corresponding 'SET ROLE OFF'. See KBA 2656891.
816450 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)", is reported when running any query involving global temporary table on an SAP ASE that is upgraded from a version between 16.0 SP02 GA and 16.0 SP02 PL06 HF1 to a higher version, and when the global temporary table is created with deferred table allocation set on the pre-upgraded version of ASE. See KBA 2680853.
816457 A new option 'create_table' has been added to the system stored procedure sp_dump_history that creates a proxy table in the tempdb database to access the dump history file.
816487 A new configuration option 'secondary signal handling' is introduced for SAP ASE which determines how the server handles secondary signals. The default value (1) makes the server shutdown on secondary signal.
816520 When no size is specified in the ALTER DATABASE command, the default size is incorrectly set to 512KB instead of 1MB for an Adaptive Server installation that is using a page size of 2KB. See KBA 2722663.
816521 sp_showplan is enhanced to use 0 instead of -1 to display the specified statement ID.
816538 In rare circumstances, SAP ASE may become unresponsive and a 15403 error, "No memory for Encrypted Columns Frag bucket pool growth", may be reported in the SAP ASE log when the configuration parameter 'max parallel degree' is set to value greater than 1. See KBA 2691726.
816544 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubfreef' together with a stack trace which includes the modules 'cm_increase_cache_size' and 'cfg__updatecache', may be reported in the SAP ASE error log when increasing the size of an inmemory cache. See KBA 2691539.
816545 Running sp_helpdb against a database can report usage as "-- unused by any segments --" when a database usage contains a user defined segment only. See KBA 2691648.
816557 The message, "Assertion (pss- > pdbtkept = NULL)", together with a stack trace that includes the modules 'mda_populate_monRepLogActivity' and 'mda_exec', may be reported in SAP ASE error log when querying the MDA table monRepLogActivity while the diagserver binary is in use.
816562 The message, "Assertion (!(imrv- > imrv_status & IMRV_BULK_PURGE_VERSIONS) || ( imrslog_bkoutctx- > bulk_purge_ctxp && (imrslog_bkoutctx- > bulk_purge_ctxp - > ibpc_nloggedrows == IMRV_BULK_PURGE_NROWS(imrv)))) failed", may be reported in the SAP ASE error log for an IMRS enabled database during the execution of TRUNCATE TABLE while the diagserver binary is in use.
816603 Enhancement to support LATCH FREE INDEX at database level.
816605 When the value of configuration parameter "HCB index auto tuning" is set to 1, unique indexes will be qualified for Hash Caching depending on the workload.
816639 An extra line may be printed between the header and the actual content in the sp_helpdb output.
816641 When sp_thresholdaction runs in a temporary database it does not inherit the usual roles the sa account should have. See KBA 2693655
816643 The message, "Invalid data found and rebuilt in segment accounting array for segment < segment_id > in database ID < database_id > .", may be reported in the SAP ASE error log following the recovery of a database. See KBA 2672135.
816646 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module ‘GtElement::GtSecondaryInit(OptBlock*)' and the message, "timeslice error: spid < spid# > exhausted its 'time slice' of < X > milliseconds and additional 'cpu grace time' of < Y > ticks ( < Z > milliseconds). It has been marked for termination.", together with a stack trace which includes the module 'ApStoredTab::findGttTable()' may be reported in the SAP ASE log while executing a large query. See KBA 2699085.
816677 A 10707 error, "java.io.FileNotFoundException: < jre > /lib/ext/ < jar_file > (Permission denied)" together with java stack trace may be reported when running a java method which implicitly invoke the loading of the extension < jar_file > .
816694 The message "current process infected with 11 (SIGSEGV)" in the module 'pipe_read' or 'pipe_write' together with a stack trace may be reported in the SAP ASE error log during the parallel execution of a Lava query. See KBA 2694998.
816700 The sybmon command, 'print < address > -1 DES', may enter into an infinite loop and print the message, "txc_colid=0, txc_coffset=0, txc_indid=0", repeatedly when a memory dump is loaded in virtual map mode.
816703 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.
816710 In rare circustances, a process may hang in the module 'fio__p_sema' when trying to DUMP or LOAD a database if another Adaptive Server process has died due to a time slice error when reading or writing the dump history file.
816715 A memory leak in the Backup Server may be seen every time a DUMP of an in-memory database is taken.
816729 A 1244 error, "Could not find address lock at address < address > while trying to release it", may be reported when querying the monCachedObject MDA table.
816735 Dump files created using a pipe can now be loaded without using a pipe. Additionally, backup files created without using a pipe can now be loaded from a pipe. See KBA 2793815.
816738 The total number of database pages stored in the dump header could not match the number of pages according to the database disk map stored in the same dump header if the database had trailing log holes and the end-user executed the command DUMP DATABASE WITH SHRINK_LOG | SHRINK_DATA | SHRINK_DATABASE.
816739 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'show_plan' followed by a stack trace which includes the modules 'LeRun' and 'LeEvals::LeEvRun', may be reported in the SAP ASE error log when using sp_showplan to query another session's query plan that involves CURSORs and the statement cache is enabled. See KBA 2722621.
816752 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'bufsearch_cache_getlatch' together with a stack trace which includes the modules 'bt__fillrkey' and 'redo_bt_pagecompress', may be reported in the SAP ASE error log when LOAD TRANSACTION fails to redo some log record operations that involve cache-discrepant compressed index pages. See KBA 2696547.
816756 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'brfinish' together with a stack trace which includes the modules 'iocRunController' and 'blkioComplete', may be reported in the SAP ASE error log when SAP ASE completes a disk I/O operation. See KBA 2722610.
816760 Progress messages have been added for the ONLINE DATABASE command execution for better reporting.
816762 Using the SP_BINDEXECLASS 'sv' object type to change the server-wide priority setting for the housekeeper wash task does not work. See KBA 2725920.
816829 Occasionally on a heavily-loaded multi-engine system, some column values in the monState MDA table, including ULCKBWritten, LogicalReads, PhysicalReads etc. might suddenly become decreased. See KBA 2748418.
816909 KBA 2702143. A new configuration option 'HADR connect timeout' is introduced to control the timeout value for the connection to the remote ASE.
816934 Incorrect results may be observed when a query involves temporary precomputed result set and the 'set rowcount < number > ' is used to limit the number of rows.
816941 A 9235 error, "Could not allocate memory for gettrunc. Please retry gettrunc() later when more memory is available, or re-configure the server with a larger procedure cache.", will be reported when the command DBCC GETTRUNC fails to allocate memory. The error message wrongly refers to the procedure cache and should instead indicate the need to increase the value of the parameter 'replication agent memory size'.
816955 Error 11058 "Statement contains ' < > ' columns/expessions in the target list. This exceeds the maximum limit of '4096'." might be raised when using cursors with large IN() list which exceed 4096 elements. See KBA 2747807.
816992 When a DUMP or LOAD command using an SAP ASE backupserver API library is aborted from the client, the call to the module 'syb_close' that will close the stripes gets the mode SUCCEED_ON_CLOSE instead of ABORT_ON_CLOSE. The result is that the API library cannot know that the operation was aborted. See KBA 2705604.
817001 The message, "The compiler will use the current best plan when 10%(Optimization Timeout limit) of average execution time is exceeded.", may be reported mistakenly by SAP ASE when the set option show brief/on/normal/long is enabled and the set plan opttimeoutlimit < value > is set to a different value than the default value of 10.
817028 The 10330 error, "EXECUTE permission denied on object sp_extrapwdchecks, database master, owner dbo", may be reported by sp_extrapwdchecks when a non-sso user attempts to change his own password. See KBA 2710822.
817066 The configuration option, "abstract plan dynamic replace", has been extended to accept a new option value of '2'. When the configuration option is set to '2', the parameterized SQL text with its abstract plan will be saved in sysqueryplans.
817072 The jobs scheduled by the SAP ASE Job Scheduler does not expire after the timeout period even when the 'default_timeout' for the job is set to a non-zero value in the absence of 'timeout' for the scheduled job. See KBA 2748408.
817092 When a downgrade is attempted from ASE 16.0 SP03 PL04 or higher version to a lower version using the stored procedure sp_downgrade_esd, and the higher version contains SQL UDFs that do not reference tables, the downgrade will fail. See KBA 2722683.
817103 When the option 'set statistics io' is turned on, the output has been enhanced to display the number of hash cache lookups and hits for Hash Cache Btree (HCB) enabled indexes on Data Row Cached (DRC) enabled tables.
817111 Under rare circumstances, the message, "Current process infected with signal 6 (SIGABRT/SIGIOT)" in the module 'gsignal()' together with a stack trace which includes the modules 'dcl__get_sess_props' and 'iface_props' may be reported in the SAP ASE error log when stopping the SAP ASE using SHUTDOWN WITH NOWAIT and the diagserver is in use.
817125 The values of variables used with the CREATE/ALTER/DROP LOGIN commands are not captured in the audit records when global auditing is on and the audit option 'login_admin' is enabled. See KBA 2746705.
817167 A 712 error, "There is insufficient heap memory to allocate < wrong_huge_value > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.", may be reported with the wrong number of bytes that could not be allocated. See KBA 2798900.
817180 In rare circumstances, a client connection using SSL may hang with the message, "ssl_nrpacket: vsn < value > kpid < value > bytesleft 0 iostatus 4 incomplete header", reported in the ASE error log. This message will henceforth be purely informational and will not indicate an error. See KBA 2748388.
817191 A 267 error, "Object ' < name > ' cannot be found.", may be reported when using global temporary table in a query and the global temporary table name exceeds 255 characters.
817220 Under rare circumstances, a spid involving remote I/O and the back trace of that spid using 'dbcc stacktrace( < spid > )' includes the module omni_ct_connect, usctconnect and ksctsuspend, may not hit timeslice error if there is any issues in the module ksctsuspend.
817238 The error, "SYBMULTBUF ERROR: Volume validation error: attempt to flush ' < filename > ' returned 22.", may be reported in the SAP Backup Server error log file when executing a LOAD command of a database that is created on raw partitions. This is a warning message that can be ignored. See KBA 2785313.
817243 The 632 error, "Attempt to move memory with an incorrect length of < size > . Maximum allowed length is < max_size > .", with state 2 does not provide diagnostic info. See KBA 2776092.
817271 In rare circumstances, REORG REBUILD INDEX may hang due to latch self-deadlock if concurrent processes are splitting leaf pages of the same table while running REORG REBUILD INDEX on the same table. See KBA 2713796.
817283 A 2847 error, "The object < sp_xxx > is not a SQLJ function. If this is a SQL function, specify owner.objectname", and a 14216 error, "Function < sp_xxx > not found. If this is a SQLJ function or SQL function, use sp_help to check whether the object exists (sp_help may produce a large amount of output)", will be reported when attempting to access SQL UDFs residing in sybsystemprocs whose names begin with "sp_" from any other database. See KBA 2714003.
817295 Key words "Old Value:" and "New Value:" are now provided in audit tables for event 154 when audit option 'config_history' is enabled. See KBA 2746660.
817366 Trace flag 7817 is enhanced to make it possible to detect the rare occurrence when an attention acknowledgement is split across two TDS packets. Such occurrences are characterized by the message, "send_done: spid < id > vsn < no > acking attention with donestat 0x20", being followed by the message, "ussflush: spid < id > vsn < no > sending 16384 bytes with tds TDSEOM 0 under pending attention", where TDSEOM is 0 (rather than 1).
817389 A 3606 error, "Arithmetic overflow occurred.", may be reported while executing stored procedure sp_shrink 'database', < database name > , < device name > , < size > . See KBA 2767036.
817401 Using KILL < spid > WITH FORCE on an idle process can result in the process remaining alive and reported by sp_who despite the connection is released. See KBA 2719233.
817414 In rare circumstances, DUMP DATABASE may fail with the error message "Backup Server: 4.145.2.22: [80] Error for database/archive device while working on stripe device ' < stripe name > '. Internal error: In rdr_xfer, the run list is too long." reported.
817422 When using Procedure Deferred Compilation in conjunction with SQL Statement Replication, SQL statements whose compilation were deferred may be wrongly replicated, causing the DSI to go down with SQL syntax errors reported against the replicated database. See KBA 2719958.
817424 A 4623 error, "Error encountered while retrieving column information. Aborting grant/revoke command.", may be reported in the SAP ASE error log when the configuration option 'enable predicated privileges' is enabled and a SELECT from table variables is executed. See KBA 2720607.
817431 Update the SAP ASE integrated JREs to SAP JRE 8.1.046 and SAP JRE 7.1.060.
817472 When a database is extended using asynchronous initialization and the new pages occupy a database range that has been asynchronously initialized before and later dropped using ALTER DATABASE OFF, some of the pages in the new fragment could remain uninitialized.
817499 DBCC ORPHANTABLES may falsely identify actively used temporary tables that are created inside a stored procedure as orphan tables. See KBA 2714936.
817519 A 17152 error, "The dump history file version is invalid.", may be reported when sp_dump_history is executed with any operation option if previously the end-user has purged dump history records from the dump history file by using the ‘delete’ operation option.
817523 SAP ASE may become unresponsive when an error is received on a network connection using SSL. See KBA 2746721.
817525 Audit records are not generated after a rpc login failure when the audit option 'rpc' is specified as 'fail' for a particular login.
817535 In rare circumstances, the message, "Invalid OAM page (OAMINVALID_1) stat 4: pageno= < value > , sdes_stat= < value > , pstat= < value > , dbid=5, etc.", together with a stack trace that includes the modules 'th_accounting', 'th_sleep_on_lct' and 'terminate_process', may be printed in the SAP ASE error log when a SELECT query that requires a work table to be created is killed.
817544 In rare circumstances, the message, "A00: SYBMULTBUF ERROR: Failed to open database info file /tmp/SYB_BACKUP1095308512. Code=2, Message=No such file or directory" and "A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 16, error code=32, system message=Broken pipe.", may be reported in the SAP Backup server error log when a dump is taken. See KBA 2726662.
817545 The error message, "ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect", followed by a stack trace that includes the modules 'omni_exec_immediate', ' omni_sync_roles' and 'set_role', may be reported in the SAP ASE error log when executing SET ROLE REPLICATION_ROLE ON in the context of proxy objects. See KBA 2786327.
817559 In rare circumstances, the message, "Stack corrupted, server aborting.", together with a stack trace which includes the modules 'ubffreef', 'upunsetcritical' and 'upyield' may be reported in the SAP ASE error log while Adaptive Server releases memory and the diagserver binary is in use.
817593 The MDA table monDeviceSpaceUsage does not return any rows for database devices that are created on block device. See KBA 2728041
817598 sybdiag fails to connect to an SSL enabled ASE server with message like "The Specified Interfaces file < interfaces_file > has an unknown format" or "JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s)" raised. See KBA 2727796.
817606 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'metrics_proc_dump' together with a stack trace which includes the modules 'd_flushmetrics' and 'exec_dbcc', may be reported in the SAP ASE error log when executing sp_metrics 'flush' and the procedure cache is being cleaned up in parallel. See KBA 2730139.
817619 The message, "Security Control Layer's memory allocation routine returned an error.", and the message, "SCL error in function: sec_setup. Operation: sec_memalloc().", are reported in the SAP ASE error log when the memory pool used for external authentication such as Kerberos becomes fragmented. See KBA 2732809.
817620 When LOAD TRANSACTION < database_name > WITH LISTONLY = LOAD_SQL is executed, SAP ASE may incorrectly report the option WITH PASSWD for a transaction dump that was dumped without password protection, if a subsequent transaction dump was taken with password protection.
817622 A 2514 error, "Table Corrupt: Type id 0 (type name = 0) does not match between systypes and syscolumns", will be reported falsely when running DBCC CHECKCATALOG for a database that has C-User Defined Functions created. See KBA 2729470.
817629 Under rare circumstances, a 1608 error, "A client process exited abnormally, or a network error was encountered" together with timeslice error followed by a stack trace which includes the module 'LopSubqAttach::GroupSimilarSubqNode' may be reported in the SAP ASE error log when a nested subquery is executed. See KBA 2727908.
817680 A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > .", may be reported during database encryption. See KBA 2761091.
817682 A 18302 error, "User < login name > is not a valid user in the < db name > database.", may be reported even when a user having sa_role executes the stored procedure sp_dbcc_faultreport. See KBA 2731983.
817734 SQL statement replication involving quoted identifiers may cause the SAP SRS DSI to shut down after receiving an SAP ASE error indicating a syntax error, or after hitting SAP SRS error 5186, "Row count mismatch for the SQL Statement Replication command executed on ' < servername > . < dbname > '.". See KBA 2721403.
817736 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeTableFunctionOp::copyInParam' followed by a stack trace that includes the modules 'LeTableFunctionOp::_LeOpOpen', 'LeOperator::LeOpOpen' and 'LeNLJOp::_LeOpNext', may be reported in the SAP ASE error log when selecting from a table-valued UDF with column and constant parameters.
817770 The message, "Backup Server: 4.142.2.90: [0] The 'sem_open' call failed with error number 17 (File exists). Refer to your operating system documentation for further details.", may be reported in the ASE Backup Server error log when "backupserver -help" is executed multiple times.
817816 In rare circumstances, some data may not be recovered correctly after LOAD TRANSACTION WITH UNTIL_TIME in an IMRS enabled database is executed while significant IMRS activity is taking place.
817834 A 1028 error, "Failed to apply the top operator 'nl_join'", may be reported when an UPDATE query involving a remote table with a join condition on the update column is executed. See KBA 2736509.
817835 The message, "Assertion (unassigned_space == 0) failed", together with a stack trace which includes the module 'lddb__map_segments_and_holes' and 'ldx__loadlog' may be reported in the SAP ASE error log when an IMRS-enabled database, which had earlier been altered to modify data segment size while the diagserver binary is in use, is loaded back using the database and transaction dumps. See KBA 2750483.
817868 In rare circumstances, DUMP DATABASE or DUMP TRANSACTION will sleep indefinitely when sp_dump_history is run with the 'purge' option at the exact same time as the DUMP and the configuration parameter 'enable dump history' is enabled. See KBA 2737615.
817925 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mda__get_procedure_schemas' together with a stack trace which includes the modules 'mda_populate_monCachedProcedures' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on the MDA table monCachedProcedures is executed. See KBA 2755225
817933 On Windows platforms, the message, "java.io.FileNotFoundException: < pca_jvm_tmp_dir > \ < file_name > (Access is denied)", together with a Java stack trace may be reported when the IO operations are performed with Java IO API and the configured pca_jvm_tmp_dir is not accessible.
817954 A 11307 error, "The object ' < object_ID > ' in database ' < database_ID > ' is not a valid parameter for the built-in function logschema(). The object must be a user table or a stored procedure.", may be reported in the SAP ASE error log when DDL replication is enabled, and a table type is being dropped.
817964 Queries referencing view with tables that were dropped and re-created or altered may result in error 11060: "This statement has exceeded the maximum number of recompilations (20)".
817974 If the configuration parameter "enable concurrent dump tran" is set to 1, SAP ASE may allow a transaction dump to be loaded on top of the wrong full database dump, if it was generated concurrently with it, and the transaction dump ends between the time the full database dump started and the dump instant time was taken. Alternatively, a 4305 error, "Specified dump file ' < filename > ' is out of sequence.", may be incorrectly reported when trying to load a transaction dump generated after the concurrent transaction dump finished.
818006 A 12834 error, "The login name ' < login_name > ' is invalid. The LDAP subsystem reported error '(license ASE_DIRS is not enabled)'." may be reported when executing the stored procedure sp_ldapadmin 'check_login', ' < login_name > ' while the configuration option 'enable ldap user auth' is disabled and a valid ASE_DIRS license exists. See KBA 2742137.
818014 A 632 error, "Attempt to move memory with an incorrect length of < N > . Maximum allowed length is 16384.", may be reported in the SAP ASE error log when executing an remote procedure call against a HANA backend server.
818020 KBA 2752182 - In rare circumstances, the message, "Failed to execute the threshold procedure for database < dbid > , segment 2, free space < num > ." or the message, "Failed to find specified threshold in threshold cache on instance 1 for database mld ( < dbid > ), segment 2, free space < num > . Use 'dbcc thresholds' to see the threshold cache contents.", may be printed in the SAP ASE error log when multiple tasks hit the threshold at the same time. This mainly happens for mixed log/data databases.
818064 In rare circumstances, the message, "imrslogrec_fix_lastlog: getpage_noscan failed to get last page: < pagenum > for database imrsdb1 ( < dbid > )", may be reported in the SAP ASE error following a failure of ONLINE DATABASE if a transaction dump is loaded which contains only one transaction in such a way that its ENDXACT falls on a different page than the BEGINXACT and the last page is partially flushed.
818065 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'prObject_list' together with a stack trace which includes the modules 'showplan' and 'exec_lava' may be reported in the SAP ASE error log when sp_showplan is executed. See KBA 2743737.
818080 Improve the performance of recovery redo pass phase in SAP Adaptive Server when open transactions with many log records had to be redone during boot recovery.
818084 A 6701 error, “Could not open dbid < value > , object id < value > .”, may be reported followed by an implicit transaction abort, during a Business Suite zero-downtime upgrade which prevents the upgrade from succeeding.
818102 In a HADR system, under rare circumstances, when the primary host is shut down or the network on primary host is down, an unplanned failover could take a long time.
818109 Tables in the database may wrongly become row caching/ MVCC or ODMVCC enabled when the ALTER DATABASE commands "ALTER DATABASE < dbname > set ROW CACHING ON FOR ALL TABLES", "ALTER DATABASE < dbname > set SNAPSHOT ISOLATION ON FOR ALL TABLES" or "ALTER DATABASE < dbname > set SNAPSHOT ISOLATION ON USING VERSION STORAGE FOR ALL TABLES" is executed without associating IMRSLOG or VERSION STORAGE with the database. See KBA 2750515.
818137 A 4346 error, "ASE cannot load a delta transaction log onto a database that is logically smaller ( < value > physical pages, < value > logical pages) than the source database( < value > physical pages, < value > logical pages). Recreate the database < name > with at least < value > physical log pages.", may be reported incorrectly due to an invalid pointer parameter value during LOAD TRANSACTION.
818168 A 1526 error, "Sort failure. The configure size for data cache ( < name > ) is not sufficient to handle the sort buffers ( < value > ) requested. Please reconfigure the data cache or sort buffers and try the command again.", may be reported during the execution of a query with a non-unique state value which prevents us to identify the root cause of the error. See KBA 2748397.
818206 The error, "Backup Server: 9.1.2.4: Unable to open configuration file ' < ASE-directory > /defaultbs.cfg'. Operating system error 13.", will be raised and the Backup Server will not boot if the Backup Server is started without specifying a configuration file and the file defaultbs.cfg in the SAP ASE directory is not readable.
818208 In an HADR environment, the replication of a DDL command using quoted identifiers and executed in a non-replicated stored procedure may cause the SRS DSI to shutdown after receiving a syntax error from the replicate ASE.
818231 In rare circumstances, using the 'setLong' method in a PreparedStatement may result in an incorrect value being assigned to a BIGINT datatype when the Java code is executed inside SAP ASE using the SAP ASE's internal sybase.asejdbc.ASEDriver driver. See KBA 2748353
818245 A 7625 error, "Audit table number ' < value > ' is invalid." with state 3, prints a incorrect value for the audit table number. See KBA 2751731.
818246 INSERT and DELETE permission is granted to Public for table syb_auto_db_extend_control via the installdbextend script.
818264 A stored procedure which uses multiple IF, ELSE, or WHILE clauses to conditionally execute DML statements may have the stored procedure text incorrectly saved in syscomments. See KBA 2749949.
818311 Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module ‘mbkt_do_alloc’ together with a stack trace which includes the modules ‘js__queue_jobid’ and ‘js_wakeup’ may be reported in the SAP ASE error log when multiple requests to start the job scheduler are made simultaneously. See KBA 2787012.
818321 The message, "FATAL UNHANDLED EXCEPTION: signal < number > hit while handling a previously hit signal. The server cannot continue and will shut down.", may be reported in the SAP ASE log when an external signal is send to ASE e.g. via OS kill command. See KBA 2682383.
818324 Under rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'kstcpnetctlrNcheckQuit' together with a stack trace which includes the modules 'ncheck_checksocket' and 'krtctskException' may be reported in the SAP ASE error log and SAP ASE may become unresponsive. See KBA 2757868
818327 On heavily loaded systems, spinlock contention on SSQLCACHE_SPIN may be observed on statement cache when a prepared statement performing INSERT statements with numeric datatypes (or similar) are present and the option DYNAMIC_PREPARE is set to FALSE. SAP KBA 2770344
818362 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'cudf_start_query' together with a stack trace which includes the modules 'curs_fetch' and 'get_datachange' may be reported in the SAP ASE error log when a query with the built-in datachange() is executed via a JDBC connection. This error may result in the SAP ASE shutting down. See KBA 2756423
818373 Under rare circumstances, a 12583 error, "Unable to log a record in database < name > (id < value > ) due to internal error -8.", may be reported when a session that is writing log records is killed with the WITH FORCE option. See KBA 2790981.
818408 Under rare circumstances dump and load database may hang when using multiple stripes on Windows platforms.
818438 sp_shmdumpconfig reports incorrect numbers for Data Caches & Server Memory fields. It adds half the combined Data Caches size to Server Memory field. See KBA 2755150.
818469 A 4325 error, "The specified recovery date ( < value > ) is not between the start ( < value2 > ) and end ( < value3 > ) date.", may be reported when LOAD TRANSACTION WITH UNTIL_TIME= < Point_In_Time_Recovery > is executed and the transaction dump when taken has a dump instant value that is later than the specified PITR value.
818484 A new parameter, 'host_public_ip', has been introduced in the resource file of setuphadr, which can cab be set to the public IP address of the host. If this parameter is set, then RMA will use this address to connect to the host.
818523 In rare circumstances, Adaptive Server may perform wrong memory deallocations when a cursor query that involves the built-in datachange() is executed and XML monitoring is enabled. This may cause errors reporting incorrect accounting between allocated and deallocated memory pages and sometimes may result in the session terminated with a stack trace reported in the SAP ASE error log. See KBA 2756423
818524 On Windows platforms, the error, "'CreateFile' call failed for database/archive device while working on stripe device < number > (The system cannot find the file specified)", may be reported when executing a DUMP command on a shared network folder using the Universal Naming Convention (UNC). See KBA 2751605.
818611 SAP ASE may choose a non-performant query plan execution when a query with a ROWS LIMIT/OFFSET clause using a MAXINT value is executed. See SAP Note 2783751.
818642 When running in an HADR environment, ASE may incur SIGILL in function sybnet__flt_init() on standby during setuphadr on AIX platform.
818666 The message "system exception generated by a storage access violation" in the module 'omni_parse_name_using_optional_bracket' together with a stack trace which includes the modules 'tmp_dropto' and 's_normalize' may be reported in the SAP ASE error log when failing to create a stored procedure that references a global temporary table due to an error that is not related to the global temporary table. See KBA 2764590.
818684 The message "TaskReplication.runTask(): SetupReplicationTask time out." may appear during setuphadr when high number of databases are involved. A new environment variable, 'SETUP_SRS_TIMEOUT' and 'MATERIALIZE_DB_TIMEOUT', has been introduced, which can be used to set the timeout value in seconds, for setting up replication and materializing databases, respectively. KBA# 2776399 - Unable to materialize large ASE Database with sap_materialize auto
818728 Under rare circumstances in an HADR setup that has an IMRS database enabled, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, there is a small window which may cause data loss as DML commands are sent to Replication Server after their commit and will be incorrectly ignored.
818746 Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dso_resgov_timlim' may be reported in the SAP ASE error log when a task disconnects at the same moment a limit is crossed and the limit action is enforced. SAP KBA 2767573.
818784 A 7928 error, "Index < name > is not consistent; found < number > leaf rows but < number > data rows.", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database.
818812 In some circumstances, query using compressed index may not return all qualified data rows on data-only locked tables. See KBA 2803119.
818824 The message, "No resources to allocate TH_FREESPACE_DIAG for database < dbid > . Freespace accounting information cannot be shown.", may be reported in the SAP ASE error log when LOAD DATABASE, LOAD TRANSACTION or ONLINE DATABASE is executed. See KBA 2769024.
818885 When running sp_sysmon using the appl or appl_and_login option, the application or application- > login section reports inaccurate Disk and Network I/Os when there are multiple sessions with the same application or application- > login pairing. See KBA 2776095.
818957 A 2753 error may be raised on an ASE where Japanese language is installed if "enable monitoring" and "plan text pipe active" configuration parameter are 1 or showplan is enabled for a complex query. See KBA 2777310.
819016 In rare circumstances under an HADR setup the ASE Replication Agent may shut down after reporting a 9415 error, "RepAgent( < dbid > ): Warning: The size of the stream buffer is too small ( < size > bytes). Use sp_config_rep_agent ' < dbname > ', 'stream buffer size', ' < new_value > ' to increase it.". Additionally a CI Library error message indicating the failure of a CI API call is reported in the SAP ASE error log.
819070 The message, "current process infected with 11 (SIGSEGV)" in the module 'getnext' together with a stack trace which includes the modules 'upgd__add_table_anchors' and 'upgd_upgrade_db' may be reported in the SAP error log during ONLINE DATABASE while an internal upgrade is run as the database dump was taken on a previous ASE release and a different platform. See KBA 2786974.
819087 Installer may fail when user set DO_UPDATE_INSTALL_HADR_COMPONENT=DM if ASE component is upgraded first.
819185 A 3624 error "Truncation error occurred" is raised with severity 10 (warning) instead of severity 16 (error) when DYNAMIC PREPARE is set to FALSE for batch processing (language batch param) and the client tries to insert a numeric which is out of scale.
819188 In rare circumstances, Adaptive Server may incorrectly create the in-lined version of a Table Valued User Defined Function (TUDF). As a result a 207 error, “Invalid column name < name > .”, may be reported during the execution of a query which references this TUDF.
819317 A 3775 error, "Unable to drop global temporary table < name > as it is in use", may be reported during the DROP of a global temporary table due to the presence of an orphan instance of the global temporary table. See KBA 2794963.

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 PL07, ASE SP03 PL07, SP03 PL07, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , 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.