SAP Knowledge Base Article - Preview

2091031 - Targeted CR List for ASE 15.7 SP132

Symptom

The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in future Adaptive Server Enterprise (ASE) EBF/SP or PL releases. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the service.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
724843 Signal 11 in OmniQuickPass::targetlist()could occur for SQL statement with subquery when show_transformed_sql is on.
732503 The message "current process infected with 11 (SIGSEGV)" in the module 'des__clean' together with a stack trace which includes the modules 'des_refreshall' and 'online_database' may be reported in the SAP ASE error log when multiple sessions are executing the ONLINE DATABASE command simultaneously for the same database. This will result in SAP ASE shutting down implicitly.
733331 Error message 1509 may be raised when CREATE INDEX or UPDATE STATISTIC is executed in parallel on huge table where there are very few distinct COLUMNS values.
749462 KBA 2115602. When statement cache is on and if fewer of parameters are sent to SAP ASE than the query expects, then an infected with 11 (SIGSEGV) stacktrace in the s__make_param() function may be reported in the SAP ASE errorlog.
752858 Replicating "datetime" data type from primary DB when primary client application apply data having different localization than RepServer, cause DSI to goes down with error #249 when Statement-Replication is activated and threshold is reach: E. 2013/12/02 08:55:31. ERROR #1028 DSI EXEC(106(1) db_srv2.ads_main) - dsiqmint.c(4358) Message from server: Message: 249, State 1, Severity 16 -- 'Syntax error during implicit conversion of VARCHAR value 'Dez 1 2013 11:00:23:020PM' to a DATETIME field.'. (here, “Dez” word (in datetime value “Dez 1 2013 11:00:23:020PM”) is the short name for December month in German) This may also impact other "date" data type.
754736 When starting an SAP ASE server up with hundreds of engines, the CPU utilization is high and the server seems to hang.
767002 KBA 2118380. UNION operators that contain fewer than four SELECT statements could consume a large portion and possibly all of the procedure cache if one or more of the select statements has a significant number of joins in it. This is unlikely to occur if the optgoal is allrows_oltp as fewer join pops are generated.
767792 A new dbcc command DELETE_EXTENTS has been added to delete orphaned extents. It must be used under the guidance of SAP support only.
768903 SAP ASE running on the Windows platform can suffer an access violation exception (0xc0000005) at location 0x0 with a corrupted stack.
769247 Sometimes concurrent DMLs will fail when using online CREATE INDEX.
769653 Sybmigrate supports the ASE 15.7 SP130 new features: HADR and 'Resolve as owner' on Stand By server.
769966 KBA 2115571. Index creation always running in serial mode when the first selected column contains large percentage of NULL values.
770016 When execute some statements through JDBC such as table create statement, sometimes, it could hang.
770415 When using hash based statistics gathering on partitioned tables, there could be statistics missing on some local partitions and hence the final global histogram is inaccurate. The inaccurate histogram could result in sub-optimal query plans. This also would result in the DATACHANGE() counters for that column on that partition not being reset, resulting in frequent update statistics maintenance on the partitioned table when depending on the DATACHANGE() function.
770514 KBA 2117327. A 691 error, "Encountered invalid logical page '0' while accessing database ' < dbname > ' ( < dbid > ), object 'sysgams' (14), index 'sysgams' (0), partition 'sysgams_14' (14). This is an internal system error..." together with a stack trace which includes the modules 'am_op' and 'pg_ptndeall' may be reported in the SAP ASE error log, during the execution of a DML command, when the database size has been extended such that it would have required the Global Allocation Map (GAM) to be extended. The GAM would need to be extended for every 64 G-bytes in a 2 K-bytes page size server, 128 G-bytes in a 4 K-bytes page size server, etc. Alternatively a 690 or 692 error may be reported.
771053 SAP ASE may encounter a signal 11 (SIGSEGV) in the function usgetipaddr() on the IBM AIX platform
771141 KBA 2115565. A query with select into a temporary table with union having predicated privileges for tables in the from clause may produce a 225 error - "Cannot run query--referenced object (name < name > ) dropped during query optimization.".
771143 Memory allocation errors similar to "ks_falloc: Cannot allocate using ubfalloc(rnetmempool, 4096). Encryption provider initialization failed on engine 19." may be noticed in the ASE error log file when engines are made offline and online in threaded mode kernel.
771228 SAP ASE may report the message "Assertion (this- > tMagic == 0x4B545255) failed in file ..." when using sp_sysmon
771344 sybdiag does not report the configuration option "prevent automatic upgrade".
771451 SAP ASE may log an infected with 11 (SIGSEGV) referencing the function kboflushcache in the SAP ASE errorlog.
771550 A session using a java function may raise error 712 "There is insufficient heap memory to allocate < n > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system." after a while.
771676 When a select from a table with predicated privileges is done after running update index statistics on the table, errors 706 - "Process < n > tried to remove PROC_HDR < addr > that it does not hold in Pss." and 913 - "Could not find row in sysdatabases with database id < n > ." may be reported.
771770 In rare circumstances, an undetected deadlock may occur following 1249 error, "Process became runnable before lock it was waiting for was released", is reported.
771897 KBA 2108039. The loginfo builtin with the 'xactspanbyspid' option can sometimes result in a stacktrace being reported in the SAP ASE errorlog with a message like "ubo_object_from_slot:Pss Invalid slot id 0".
771901 An 834 error, “Illegal attempt to clean buffer…” in the module ‘cm_dbclean’ together with a stack trace which includes the modules ‘onl_online_db’ and ‘buf_online_database’ may be reported in the error log when DUMP TRANSACTION or DUMP DATABASE and ONLINE DATABASE are executed simultaneously for the same database.
771949 KBA 2115498. SAP ASE is returning a longer string/resultset for str_replace.
772000 The message "timeslice -501, current process infected" in the module 'plc__discard' together with a stack trace which includes the modules 'xact__rollbackxact' and 'finishlog' may be reported in the error log when a multi-database transaction is executed in chained mode whereby the option dml_logging=minimal is enabled and while a DML command is rolled back following an error encountered.
772045 SAP ASE Application context built-in functions may report an unexpected permissions error.
772101 KBA 2099190. There may be a signal 11 (SIGSEGV) reported in the SAP ASE errorlog when in a query a union or union all with 4 or more sides of the union exist. This is rare and would usually be accompanied by missing stats resulting in large overestimates in the optimizer, and/or an underconfigured tempdb.
772356 KBA 2094262. Execution of sp_downgrade may take a very long time to complete.
772405 KBA 2117914. A 9004 error, "I/O error detected on disk buffer 0x... for page request < value > , dbid < value > ." followed by a stack trace that contains the module 'crdb_init_first_au' may be reported in the SAP ASE error log when trying to execute an ALTER DATABASE FOR LOAD command for an in-memory database.
772435 KBA 2116143. If user's machine is too slow, sqlupgrade[res] and syconfig.exe/sybatch.exe may failed to upgrade SAP ASE because it can't reconnect to the SAP ASE booted in single user mode.
772605 The error "d_log(): xls_startscan() failed - XLS error -3: Invalid condition" may be reported when executing DBCC LOG to get the log records for a particular SAP ASE process id when passing - < process ID > as the second parameter value of this command.
772749 KBA 2090182. Under some rare conditions, execute dynamic sql sttaements could lead to the SIG 11 and stacktrace includes crp_vardec(), crp_var(), and sqt_reparse().
772903 If a dump is created with the database option 'allow page signing' enabled and loaded 'WITH LISTONLY = CREATE_SQL', the sp_dboption command is not generated by 'CREATE_SQL' for setting the option 'allow page signing'.
773010 When a query causes timeout error, it incorrectly reads bytes from the TDS stream, reports an unexpected error like "Type '64' not implemented" and generates two RESPONSE messages to the client.
773273 KBA 2116202. When a database has enabled page signing, under rare circumstances a transaction log page may be written with invalid page linking pointers. This can manifest as 806 errors during recovery or rollback.
773554 The execution of loginfo( < dbid > , ‘xactspanbyspid’, < spid > ) built-in could take long time to complete while a DUMP TRANSACTION is concurrently run or when the amount of transaction log that is held up by it is very big.
773638 In large, highly concurrent environments, SAP ASE may, under specific circumstances, cease to elect large ( > 1 page) IO and instead revert to regular (1 page) IO for asynchronous pre-fetch (APF) for a cache. The specific circumstances include that a single table is very frequently accessed, that the table does not fit into its named cache, causing cache misses and that the workload is such that the plans include large IO and APF.
773879 KBA 2116754. SAP ASE running in threaded kernel mode on the IBM AIX platform may hit a stack overflow error while starting the Job Scheduler and this may lead to a shutdown of SAP ASE.
773950 A 1295 error, "Unconditional lock request for table or page < > , dbid < > was made while holding a latch." followed by the message "current process infected with 11" in the module 'xls_sessionid' together with a stack trace which includes the modules ' chk_and_send_audit' and 'send_audit' may be reported in the error log when REORG REBUILD INDEX is executed concurrently with DUMP DATABASE.
773957 Wrong result could be inserted into the under table when updating a view with float literal if the view has a instead of trigger and literal autoparam and statement cache are enabled.
773966 An infected with 11 (SIGSEGV) in the function in StgStatPkg::StgVarLengthColEstimates may be reported in the SAP ASE errorlog.
773978 When parallel CREATE INDEX with hash based statistics gathering is used, there is a possibility of a worker thread being placed in a sleep state and not be woken up, which will cause the session to hang.
774079 Eliminate a spinlock window while updating MASS Status during hk_bufawrite.
774082 When running parallel CREATE INDEX with hash based statistics gathering there may be a timeslice error.
774203 If the database option "enforce dump tran sequence" is enabled, do not disallow CREATE INDEX with ONLINE option to run if the index is also being created with the DEFERRED_RECOVERY option.
774211 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 a DML query is executed which includes an expression that references the reserve_identity() built-in.
774323 A 644 error: "Index row entry for data row id ( < pageid > , < rownum > ) is missing from index page < index_pageid > of index id < indid > of table ' < tabname > ' in database ' < dbname > ' may sometimes be reported during recovery while undoing log records pertaining to an index on a Datarows Only Locked table.
774338 In rare circumstances an 11051 error, “CREATE INDEX on the object ‘ < table > ’ failed. Table is currently being used by one or more other tasks. Retry your query later.” may be reported while transaction isolation level 0 scans are active on the same table. Starting SAP ASE with trace flag 8225 will reduce the likelihood of this error.
774411 In rare circumstances a 706 error, "Process tried to remove PROC_HDR that it does not hold in Pss", in the module onlutl_release_resources() together with a stack trace which includes the modules 'memfree' and 'rm_prochdr' may be reported in the SAP ASE error log when running CREATE INDEX or REORG REBUILD with the online option.
774416 Occasionally a error 644,"Index row entry for data row id (%u, %d) is missing from index page %u of index id %d of table ' < name > ' in database ' < n > '. Xactid is (%u,%d). Drop and re-create the index." will be reported, when online parallel create index on unpartitioned DOL table with concurrent DMLs.
774650 A SPID is holding a latch on a buffer and sleeping and some other SPID's are waiting on the same buffer leading to a hang.
774683 The SAP ASE server kills database connections when deadlocks occur when a language batch command is followed by an RPC call. A stacktrace with an access violation/infected with 11 (SIGSEGV) is reported in SAP ASE errorlog.
774699 Under rare circumstances during upgrade or initial installation, after SAP ASE reports that it is beginning upgrade step ID 1650 it may produce a stack trace saying that a stack overrun was detected and that the stack guardword is corrupt.
774786 A 820 error, "Attempt to dirty non-log buffer ... which is in I/O" in the module 'bufpindirty' together with a stack trace which includes the modules 'undo_bt_split' and 'rec__undo_abort_incomplete_ntas' may be reported in the error log during the undo phase of boot recovery if there are incomplete transactions that split index pages of Data Only Locked tables.
774906 A 605 error, "An attempt was made to fetch logical page ' < > ' from cache ' < > '. Page belongs to database ' < > ' ...", in the module ‘bt__getchildlatched’ together with a stack trace which includes the modules ‘rec_undo_session_apf’ and ‘xact__rollback_local’ may be reported in the error log while a session is rolling back a transaction containing a CREATE INDEX that is followed by DMLs in a database with the option 'ddl in tran' enabled.
775030 KBA 2117888. Sometimes, if temp tables change in between two batch insert calls via jdbc, then we might have a situation where we point to memory that has been freed, leading to either of following errors : 705, 706, 707, 715 or Error 719 or similar error related to memory free, having stacktrace of batch_loopend - > s_copytmps - > memfree.
775036 When an online utility rolls back, a concurrent update on the same table could hit the error 12319 "Fatal internal error encountered during deferred dml on table < > in database < > . All rows that qualified during the first phase were not visited during second phase of dml."
775297 When the Job Scheduler initialization fails or terminates, the subsequent Job scheduler boot may fail with an error "Attempt to insert duplicate key row in object ' < js_table_name > ' with unique index ' < js_row_index > '"
775355 A 1108 error, "Cannot deallocate extent < extentid > , database < dbid > . Object id < objid > , index id < indid > , status 1 in extent does not match object id < objid2 > , index id < indid2 > , status 0 in object being deallocated. Run DBCC CHECKALLOC." may be reported in the module 'pg__dropbuf' together with a stack trace in the error log which includes the modules 'xact_rollback' and 'undo_apl_aextent', when an index page split occurs during the logical synchronization phase of ONLINE CREATE INDEX for a Data Only Locked table and the command is rolled back in the end.
775422 During rollback of online create index, level0 scanners might not be able to use the DES.
775446 KBA 2105799. The SAP ASE server might not boot with the error "defined cache configuration consumes more memory than is available for buffer caches".
775501 SAP ASE could hit error 705 ("There is no room for process xxx to store PROC_HDR 0xxxx in Pss") when a lot of recompilations happen due to schema count changes.
775559 A 102 error, Incorrect syntax near '~'. One or more indexes are corrupt. They will be rebuilt ...", may be reported during ONLINE DATABASE if the database contains an index whose name is a quoted_identifier and the index was created with defer_recovery = NONE option and while the recovery of this index has been deferred by LOAD TRANSACTION.
775561 A 'hang' situation due to an infinite loop may be encountered by a LOAD TRANSACTION command if the transaction log being loaded has more than 631 CREATE INDEX transactions with DEFER_RECOVERY option set.
775599 In rare circumstances, a 1295 error, "Unconditional lock request for table or page < page number > , dbid < dbid > was made while holding a latch.", may be reported by the system housekeeper chores task.
775654 In rare circumstances, the message "current process infected with 11" in the module 's_setreturns' or 'LeEmitNoSndOp::_LeOpNext' together with a stack trace maybe be reported in the error log when Job Scheduler is started using the stored procedure SP_SJOBCONTROL and a 1204 error, "ASE has run out of LOCKS. Re-run your command ..." is triggered.
775721 The assertion failure: "Assertion (xdes- > xcomplogbytesleft_diag > = 0) failed in file /calm/svr/sql/generic/source/access/do.c line < line_num > " may be seen with a diagserver during the ROLLBACK of a CREATE INDEX with ONLINE command.
775735 A 605 error, "An attempt was made to fetch logical page ' < pgid > ' from cache ' < cachename > '. Page belongs to < obj_name1 > and not to < obj_name2 > ", may be sometimes reported when a transaction containing multiple CREATE and DROP INDEX commands is rolled back in a database that has the 'ddl in tran' option enabled.
775820 A 2628 error, "In database < > , page < > is linked forward to page < > , but that page is linked backward to page < > . Please report this internal error to Sybase Technical Support.", followed by a 644 error, "Index row entry for data row id < > is missing from index page < > of index id < > of table < > in database < > . Xactid is < > . Drop and re-create the index." may be reported when a DROP INDEX command is run concurrently with ONLINE CREATE INDEX command.
775875 Parallel queries may close their child threads before the child is completely drained. This can happen when non-correlated subqueries are flattened internally into existence joins. Unfortunately, the child thread will continue to drain it's plan fragment even when the pipe it is writing to is closed leading to bad performance.
775943 In rare circumstances, an aborted ONLINE CREATE INDEX or ONLINE REORG REBUILD may cause a subsequent UPDATE or DELETE command to hit a 644 error, "Index row entry for data row id < > is missing from index page < > of index id < > of table < > in database < > . Xactid is < > . Drop and re-create the index.".
776090 KBA 2114230. In rare circumstances, the message "timeslice, current process infected" in the module 'qualpage' together with a stack trace which includes the modules 'dol_def_update' and 'xls_getnext' may be reported in the SAP ASE error log when an UPDATE statement is run in deferred mode. At boot recovery or load transaction time a 3301 error, "Invalid log record found in syslogs (logop < value > )", may be reported. Alternatively during data consistency checks a 7928 error, "Index < name > is not consistent; found < n-1 > leaf rows but < n > data rows. Drop and recreate the index." may be reported.
776152 KBA 2105598. The message "current process infected with 11 (SIGSEGV)" in the module ‘dbts_ptscmp’ together with a stack trace which includes the modules ‘th_lct_admin’ and ‘num_logpages’ may be reported in the SAP ASE error log when the lct_admin() built-in is used to get total number of log pages for databases with mixed log and data segments.
776176 A 1142 error, "Invalid OAM Page < oampgid > . Found pstat= < page_status > , object= < objid > , database= < dbid > , indid= < indid > .", may be reported when CREATE INDEX and DROP INDEX commands are executed in a user transaction and while the database option 'ddl in tran' is enabled.
776222 KBA 2111076. A 644 error, "Index row entry for data row id ( < page# > , < row# > ) is missing from index page < page# > of index id < value > of table ' < name > ' in database 'name'. Xactid is ( < page# > , < row# > ) ). Drop and re-create the index.", may be reported on little-endian platforms when a clustered index on a Data Only Locked table permits duplicate keys and the index refers to pages of which the hex value of lowest two bytes is 0xffff.
776348 After installing HADR or Warm Standby Replication, materialization may fail or permission errors may occur on the standby server for privileged logins.
776409 KBA 2117329. In rare circumstances a task may not be able to abort its current active transactions and hang when sp_hadr_admin deactivate was issued by another task. The task will appear to hang in the module 'stack_abort' followed by the modules 'getpage_with_validation' and 'hadr_endxacts'.
776433 The SAP ASE Agent Plugin shows incorrect version string
776549 KBA 2115587. The message "Assertion(!"xfep- > xfe_up_skip_in_clr_ctr < 0") failed' in the module 'rec_undo_log' together with a stack trace which includes the modules 'online_database' and 'rec_onlinetime' may be reported in the SAP ASE error log if the diagserver binary is used, duting ONLINE DATABASE recovery after loading a database dump that contained CREATE INDEX rolled back operations and the database had the option "ddl in tran" enabled.
776684 Error message 692 may be raised when table OAM scan is used in a long transaction if database option "ddl in tran" is enabled and a clustered index is created before the table OAM scan under the same long transaction. The message says "Uninitialized logical page ' < page_id > ' was read while accessing database ' < database_name > ' ( < db_id > ), object ' < table_name > '( < object_id > ), index ' < index_name > ' ( < index_id > ), partition ' < partition_name > ' ( < partition_id > ). Please contact SAP Technical Support."
776692 suser_name() may display incorrect user name after a cross database execute as owner stored procedure is executed from a parent stored procedure.
776748 In rare circumstances, Adaptive Server may hang as a result of an undetected self-deadlock for a process that is doing DUMP DATABASE if the database option ‘allow incremental dumps’ is enabled.
777210 A 631 error, "The length of < > passed to delete row routine for the row at offset < > is incorrect on the following page of database ' < > ' ... The offset should be no greater than < > .", in the module 'rec_undo_session' together with a stack trace which includes the modules 'LeBulkOpOpen' and 'xact_rollback' may be reported in the error log when a table is encrypted and eligible for incremental transfer and BCP utility is used to load data into it.
777382 CREATE ONLINE INDEX WITH HASH STATS was not working as documented.

Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 SP132
  • 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 15.7 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition

Keywords

Fix, Patch, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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.