SAP Knowledge Base Article - Preview

2245004 - Targeted CR List for ASE 16.0 SP02 PL02

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 SP02 PL02. 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
684701 The "for xml" clause is being stripped off from the text which is saved in syscomments. This causes the procedure output to change unexpectedly (output is no longer in XML format) following upgrade.
693491 A transient 605 error may be raised by a query against a table(lock scheme datarows) having des_bind and REORG REBUILD has just been done. Please use dbcc tune(des_unbind,dbid, objname) to unbind the object before REORG REBUILD to avoid the error.
732131 A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log old timestamp= < > . Log record marker = ( < > ).", may be reported during LOAD TRANSACTION if either the built-in reserve_identity() or the dbcc set_identity_burn_max() command have been executed when the transaction dump was taken.
735498 It can take a long time to detect that there has been a KILL of a REORG REBUILD and thus to start a rollback when a huge table is involved.
746085 High CPU utlizaton and spinlock contention on a db_cache spinlock may be observed for the sysattributes table.
761855 The message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'pchk_io_done' when executing DBCC CHECKSTORAGE because the dbccdb is incorrectly encrypted.
767494 There may be index space bloat on tables with high deleted row count.
768278 LFB consolidation of GC vs flush causes some buffers to be dirtied but not in any dirty chain.
768441 Error message, "EXECUTE permission denied on object sp_showoptstats, database sybsystemprocs, owner dbo", may be reported when sp_showoptstats is executed by users other than system administrator.
769985 A 923 error, "User not allowed in database - only the owner of this database can access it", is raised when a nested stored procedure prefixed with the database name is executed in a database configured for DBO USE ONLY.
770244 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'prRA_CONTEXT' together with a stack trace which includes the modules 'd_repl_context' and 'prREPL_CONTEXT' may be reported in the error log when the Rep Agent is terminated during the execution of the DBCC REPL_CONTEXT command.
773191 Incorrect values can be reported by the SAP ASE optdiag utility for "Large I/O efficiency" when large I/O pools have been configured in SAP ASE.
774289 A 1105 error, "Can't allocate space for object ' < name > ' in database ' < db > ' because ' < segname > ' 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", may be reported when ONLINE PARALLEL CREATE INDEX is executed with a large number of consumers and the default configuration is used.
774879 Setting the Rep Agent configuration parameter 'scan timeout' to a value of '0' can cause Rep Agent scanner threads not to respond to a kill or to a stop command. Disallow setting this parameter to a value of '0'.
775572 KBA 2258141 - The 12334 error, "Attempts to read logical page `%ld`, virtpage `%ld` from virtual device `%d` for %S_PTNINFO failed due to read failure in prefetch. Please contact Sybase Technical Support", may be observed during prefetch while running selects on the tables APL table table with clustered or local index and on DOL tables with local index.
777296 A 940 error, "Dbtable in wrong state for operation: < name > ", is reported against tempdb when repeating a query which uses work table for more than 32k times.
777566 An additional shared memory segment is created when the local cache partitions for the default data cache is set to "default" and the number of online engines is greater than 2, resulting in auto-tuning recommending additional cachelets. It is also possible that this may cause the server to fail to boot.
777640 A 16805 error, "A LOB LOCATOR was used that is no longer valid: Either the transaction that created it has ended or it has been deallocated", may occur when a LOB variable is used with the substring function.
777948 Add support for "with recompile" to DML statements within stored procedure.
778071 In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the modules s__merge_finish() or CgpStoreInd::_CgpStoreIndPePredBmToScalar() may be reported in the error log when running a query with MERGE UNION and INSERT.
778237 A 17870 error, "Table '#sphelpuser2ro' does not exist in database 'tempdb2'", may be observed while executing sp_helpuser.
778347 The message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the module 'QpClearGc' may be reported in the SAP ASE error log when using a CURSOR with SELECT FOR UPDATE.
778531 Add additional diagnostics for Global Allocation MAP (GAM) status issues.
778536 A 1205 error, "Your server command (family id #%d, process id #%d) encountered a deadlock situation. Please re-run your command", may be reported in Cluster Edition for some concurrent DMLs even in one node.
778911 There may be a nan or NaN (not a number) reported in optimizer tracing that could result in poorly performing query plans. Optcriteria CR778911 will check that the range summary stats (such as range density and range unique) are non zero if there is at least one non-zero range cell in the histogram.
779616 The stored procedure, sp_modifythreshold, can create a duplicate threshold entry if two identical thresholds exist on two different segments, and one of them is changed to monitor the other segment.
779813 New feature to support automatic rollover of ASE error log file exceeding threshold size specified using "sp_configure 'errorlog size', < size in MB > ".
779826 When using stored procedures, showplan message wrongly indicates that a table in tempdb resides in an in-memory database.
779858 If the command sp_dumpoptimize is executed to change the allocation_threshold using either a suffix of this keyword or via 'archive=min|max|default', the value will be set in the Backup Server but it will be overwritten at dump time with a default value of 40% or with any previous value that has been configured using the full allocation_threshold keyword.
779895 With XML option being enabled for optimizer trace output, correct XML elements should be used to print the deferred parallel processing information of optimizer.
779922 Error 11060 reported for maximum number of recompilations(10) for the isolation level 0 transaction
779957 Two wait states were using wait event ID 727 (Encrypted Columns module waiting for csi factory creation). This change introduced wait event ID 831 to ensure all wait events have unique IDs.
780611 Under rare conditions, the message, "Current process infected with signal 11 (SIGSEGV)" or a timeslice error in the function metrics_GetForMDATable(), may be reported in the error log when the monCachedStatement table is queried in a heavy-loaded environment.
780614 cis idle connection timeout does not work as expected.
781774 In rare circumstances, CREATE INDEX may fail with a 1289 error, "Internal Error in lock manager routine: Invalid lock mode exclusive page, requested by task (family id < > , spid < > ) conflicts with existing family request mode exclusive page belonging to task (family id < > , spid < > )"
782319 sp_helpcache reports the "In memory cache size" as negative for cache sizes > = 2GB.
782345 Incorrect progress report (progress > 100%) may be reported when running dbcc tablealloc() on syslogs table.
782355 ALTER LOGIN must check the caller password when Granular Permissions (GP) is on and the caller has sso_role.
782445 A query with decimal conversion in an IN clause may not correctly return rows which should qualify when the statement cache is enabled.
782648 The message, "Backup Server: 1.67.2.16: Backup Server Internal Error in function 'fatoi'", will be raised by the Backup Server when trying to execute a remote dump or load on a Backup Server with a version less than 15.7SP60, or a version between 15.7SP101 and 15.7SP121.
782907 In rare circumstances an undetected deadlock may be seen among DUMP DATABASE, DUMP TRANSACTION and CREATE INDEX when these commands are executed on the same database concurrently. A 8213 error, "Failed to acquire address lock on object DDLOG", may result from the deadlock.
782972 Partition statistics is not retained when UPDATE STATISTICS is executed on a semantic partitioned table with ONLY 1 partition.
783192 When textptr() and ORDER BY are both used in the same SELECT statement, textptr() may return bad text pointers if the target TEXT/IMAGE/UNITEXT column has NULL values.
783358 Parallel Optimizer generated some parallel query plans with negative cost values. This fix is enabled under opt criteria CR782580.
783601 Killing a thread executing UPDATE STATISTICS on a column with highly-duplicate values causes the thread to crash.
783649 Print fact table hint diagnostic information to showplan output.
783753 While using streaming replication the message, "CI-ERR [Thu May 7 16:32:02 2015]: [(I3T)Package buffer depleted index 261720 max 262144 size 9088]" can be printed into the ASE error log.
783860 The qrmutil tool may return an exit status of 0 even when when the command fails.
784560 New feature request to let the external SAP backup server API file name use more than 30 characters as well as to accept other characters that are not just letters, numbers or '_' in the name.
784716 With CR 689004, different values of @@rowcount may be obtained when the configuration parameter “send doneinproc tokens” is set to 0 when compared with earlier releases. The old (incorrect) behaviour may be required by some applications. To restore the old behaviour, enable trace flag 11002
785196 On a Solution Manager system, spid's executing UPDATE INDEX STATISTICS may appear hang in the module ptn__datachange_reset().
785554 Under UTF8 sort order 99, if a composite index contains a leading NULL VARCHAR field, REORG REINDEX may not be able to rebuild the index.
785591 A 2956 error, "Unable to grab a buffer to encrypt logical page < page_id > in database < db_id > " followed by a stack trace involving the modules 'cm__wash_mass_lru' and 'bufawrite' may be reported in the error log when accessing an encrypted database.
785672 SAP ASE spids might hang indefinitely waiting on the MASS_DESTROY bit to be reset when tempdb is being used.
785701 In rare circumstances, a 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < > , object id = < > ..." is reported by SAP ASE during a LOAD TRAN of a transaction dump that includes a transaction of online REORG REBUILD or non-online CREATE INDEX if the earlier portion of load sequence contains a transaction of online CREATE INDEX with deferred recovery.
786104 Using ALTER TABLE ADD column_name IDENTITY sets the wrong attributes in syscolumns.
786149 When using streaming replication, the execution of sp_stop_rep_agent < db > may sometimes prevent the Replication Agent from shutting down, when for example the SQP on the Replication Server is full. In order to successfully shutdown the Replication Agent the same command along with the ‘nowait’ option needs be executed again.
786283 In rare cases, if a transaction performing INSERT on table with LOB columns gets rolled back due to HADR force de-activation with message 3958, command rollback happens instead of transaction rollback.
786412 The message, "Current process infected with signal 11 (SIGSEGV)", in the module fix_multiref() followed by a stack trace that includes the modules 'remove_illegal_const' may be reported in the error log when 'abstract plan load' and 'enable literal autoparam' are enabled and runtime recompilation has happened.
786420 KBA 2201449: A 15413 error, "An internal error occurred during an encryption operation (error code < n > ). Please contact SAP Technical Support", may be reported when selecting data from encrypted columns.
786478 The 9502 error may be reported incorrectly when using a UNIVARCHAR column with a NULL value with statement cache enabled. For example, when inserting a NULL value into the column through a JDBC prepared statement.
786540 When auditing is enabled, the spurious message, "kernel ksnetctlrSanity: vsn 6622 psn 165 kpid 1503595925 flags 0xc0000020, events 0x8", may be reported in the SAP ASE error log on the Solaris platform.
786588 An 8201 error, "Mismatch found between the name and id descriptor hash table for table...", accompanied by a stack trace that includes the modules 'des__clean' and 'des__scavenge' may be reported in the error log in some high concurrency scenarios.
786594 It can take a long time to return all rows from MDA tables if the result set is very large.
786637 CT-Lib ct_results() returned CS_CMD_FAIL for errors previously ignored, causing compatibility issues in JSTemplate due to SAP OCS CR 770865.
786672 A 594 error, "The UPDATE WHERE CURRENT OF to the cursor ' < name > ' failed because column ' < name > ' being updated was not specified in the SELECT list", may be reported when an updatable cursor has an internal query.
786780 In rare circumstances, the message "current process infected with signal 11" in the module OptGlobal::_GblAddTopLevel() together with a stack trace which includes the module emitMatchProperties() may be reported when running a complex query.
786786 setuphadr utility needs to validate RMA administrator and ASE HADR maintenance passwords on primary and companion ASE.
786808 The message, "SYBMULTBUF ERROR: Fatal Error: Database emulator failed while executing command 161", will be printed in the Backup Server error log and a DUMP command will abort if the database being dumped is created on ZFS file system and the backup server is started with trace flag -D512.
787016 KBA 2224574 - If SAP ASE configured to use native threads encounters a segmentation fault (infected with 11 (SIGSEGV)) whilst dumping shared memory (a the dump configured with multiple dump threads) then SAP ASE may crash.
787019 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'qualpage' together with a stack trace which includes the modules 'rep_agent_config' and 'attrib_getrow' may be reported in the SAP ASE error log when executing the built-in rep_agent_config() on an offline database after having loaded a 12.5.4 database dump into it.
787024 When SAP ASE RepAgent is configured for stream replication in synchronous mode, the primary database may run out of log space if most of the activity in this database is performed on non-replicated objects.
787084 When Adaptive Server is running the query processor in compatibility mode, queries with tables having predicated privileges will not work.
787093 In rare circumstances, the message "Current process infected with signal 11" in the module SeHyPsStarQueryRule::_RuleCompositeIdxMatch together with a stack trace may be reported in the error log when using the fact_table optimizer hint in the input Abstract Plan.
787699 In rare circumstances, when online CREATE INDEX is issued on an empty table and concurrent DMLs insert new rows in the table that cause addition of new index level, syspartition may report wrong ptnfirst value and subsequent CHECKALLOC may fail.
787759 In HADR cluster, during planned failover, client connections do not get killed and therefore they linger on old Primary server and receive Msg 2379, "The primary server has been successfully deactivated" rather than failing over to the new primary server.
787765 In the context of synchronous replication SAP Replication Server may report 'NCWait' status in ReadState column in the output from 'admin who' even if the transaction was written on disk by SAP ASE.
787900 An incorrect path provided for the SSL Certificate file does not lead to an error being reported.
787904 sp_showplan is enhanced as follows: (1) Print "Total rows" from sp_showplan with 'FULL' or 'LONG' option by default. (2) Print sql text and object list from sp_showplan with 'SHORT' option. (3) Add number of rows in the object list output.
787966 The message, "Current process infected with signal 11 (SIGSEGV)", followed by a stacktrace that includes the module mda_fill_and_send_monProcessObject() may be reported in the error log when running the query, "insert #monProcessObject select from master..monProcessObject"
788087 In some circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the error log together with a stack trace which includes the modules 'tmp_get_tmpobj_by_name' and 'open_range' when multiple Table UDFs are involved in a query.
788128 The replay of existing connections will fail if the server is configured with 'default network packet size' of 512.
788143 The TDS_DONE token might not be completely captured under some circumstatnces and it will cause some unexpected parse error during workload analysis.
788148 The shut down of Job Scheduler may hang if jsagent user connection hits timeout error.
788212 A timeslice error in the module 'optlookup' may occur if a stored procedure which contains a DUMP TRANSACTION command on encrypted database is executed several times.
788226 The 325 error, "Adaptive Server finds no legal query plan for this statement", may be reported when fact_table abstract plan hint is used with DELETE statements.
788228 When SAP ASE RepAgent is configured for stream replication in synchronous mode, the time reported by sp_hadr_admin 'failover_timeestimate' may be inaccurate when SAP RepAgent is not running.
788311 DDLGen reports the error, "UDM9: Critical internal application error occurred", when DDL is generated for a database and that database contains user defined messages.
788353 KBA 2208560: XPServer behaviour change for running shell scripts from SP135 onwards
788369 The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'blkioFlagIsSet' together with a stack trace which includes the modules 'utpmApplyAll' and 'kaclkintr_thread' may be reported in the SAP ASE error log resulting in ASE being unable to shut down itself gracefully that will require SAP ASE to be killed at OS level.
788474 KBA 2211717: Under some rare condition, if columns in a table have more than one constraints (not necessary in the same column), it can cause invalid rows to be inserted.
788552 In rare circumstances, when CREATE INDEX with ONLINE is executed on an APL table and there are several concurrent DMLs active, SAP ASE may hit an infected with 11 (SIGSEGV).
788562 Parallel queries may terminate early without returning all the required rows.
788609 Full DB encryption could run into error 2956 if the buffer size is not configured to be sufficient.
788639 The default behavior for workload capture full response preference has been changed. It will not capture response packets other than final DONE packets by default.
788702 The 3475 message, "There is no space available in SYSLOGS to log a record for which space has been reserved in database 'tempdb'", may be reported in the SAP ASE error log for database tempdb, when a log fragment was previously dropped from tempdb using sp_dropsegment.
788772 The replay of workload may fail for connections that had already been established at the time that the original capture was initiated.
788791 A 2628 error, "In database < dbname > , page < pageno_1 > is linked forward to page < pageno_2 > , but that page is linked backward to page < pageno_3 > . Please report this internal error to SAP Technical Support", may be encountered when using a Latch Free index in a high concurrency environment.
788808 Improper text may be generated while running sp_helptext in a procedure which has SET < some option > ON followed by the COMMIT statement.
788861 In an HADR cluster, if Granular Permission is enabled, replication may stop with DSI reporting a permission error, such as "ERROR #1028 DSI EXEC" due to SRS encountering ASE error "Message: 10330 'INSERT permission denied on object ....'".
788898 The execution of DBCC CHECKSTORAGE on the master database may erroneously report faults 100009, 100029, and 100030 on the sysanchors table.
788921 langinstall fails to install language on AIX Platform using LDAP directory services.
788942 A 644 error, "Index row entry for data row id < row_id > is missing from index page < page_no > of index id < index_id > of table < table_name > in database < db_name > . Xactid is < trans_id > . Drop and re-create the index.", may be reported against a Latch Free index created for a large table which has a lot of duplicate keys.
788947 An 941 error, "Illegal database context operation." may be observed while executing a SELECT on a table with name having the '#' prefix.
788952 In rare circumstance, dbcc shrinkdb_setup() may not be able to correct text back link for text/image/unitext columns of tables that are set to be replicated.
789086 UPDATE does not fire the trigger for UPDATE of the table through cursor.
789109 The error 'uncompress(): Input data corrupted' could be raised when loading a compressed dump created either using the Backup Server API "compress::" or the command option WITH COMPRESSION [= 1..9].
789128 In some situations, Adaptive Server Enterprise may reject the fact_table hint when large IN-list materialization takes place.
789141 SAP ASE unnecessarily requires that the command "load database master with listonly=load_sql" be run in single user mode and it also prints the message, “WARNING: In order to LOAD the master database, the ASE must run in single-user mode”.
789251 KBA 2218075 - In rare circumstances unexpected results could be returned when a query involving a LIKE clause is executed inside a stored procedure run WITH UPGRADE option (or which required to be upgraded internally from source text) and the LIKE clause references input parameters defined in the stored procedure.
789255 While using streaming replication the message, "CI-ERR [Thu May 7 16:32:02 2015]: [(I3T)Package buffer depleted index 261720 max 262144 size 9088]", may be printed into the ASE error log.
789263 When SAP ASE RepAgent is configured for stream replication in synchronous mode, additional validations are added whenever a table schema is send to SAP Replication Server. When SAP RepAgent trace flag 9208 is enabled related diagnostic messages will be reported.
789323 The message, "The log for database < dbname > includes a CREATE INDEX (with deferred roll-forward) operation that is incompatible with this server version and operating environment." may be reported during LOAD TRAN if the transaction dump contains an index that will be recovered as deferred item during the LOAD TRAN recovery.
789356 Workload by client connections with an empty application name will not be captured when using the Workload Capture feature.
789426 When IMDB is used with multiple cachelets and the database size is altered, then SAP ASE may report error 899, "The page < page > requested for in-memory < objinfo > was not found in in-memory storage cache ' < name > ' (id < n > ). Please contact SAP Technical Support."
789580 A NullPointerException may be encountered during JSTemplate installation when the ASE server is not running.
789618 setuphadr utility cannot reboot ASE if alias host name is used. It reports error, 'Cannot boot/reboot SAP ASE "{0}" because "{1}" does not exist'
789675 The p_drv_bcpmetadata stored procedure is enhanced in order to improve the performance of jConnect ENABLE_BULK_LOAD.
789944 Under some rare situations, updating a table through a IOT (instead of trigger) could result in error 16863.
789960 Under rare circumstances, an 1105 error "Can't allocate space for object 'syslogs' in database ' < dbname > ' because ' < segmentname > ' 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." may be reported in the SAP ASE error log mistakenly when executing DDL/DML commands although there is enough space available in the given segment.
789967 In rare circumstances, a 12308 error, "Invalid row id (Row < > , Page < > ) encountered in the table 'T' in database 'D'" or a 614 error "Adaptive Server accessed a row that has an illegal length of < n > while in data base 'X' ..." may be reported by a REORG REBUILD index or a DML following REORG DEFRAG on a table.
790223 The str_replace() function returns a much wider result when the pattern string is a function or variable rather than a quoted string literal.
790265 The message, "Current process infected with 11 (SIGSEGV)", in the module 'ds_destroy_table' together with a stack trace which includes the modules 'exec_dbcc' and 'checkalloc' may be reported in the SAP ASE error log when DBCC CHECKALLOC is interrupted by a Control-C.
790375 When querying the MDA table monRepScannersTotalTime, the counter column TotalTime may be less than the counter column ProcessTime.
790394 In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'dbt_unkeep' together with a stack trace which includes the module 'close_range' may be reported in the SAP ASE error log when a query uses a worktable.
790406 A 14108 error, "Could not find partition descriptor for objid < > , indid 255, ptnid < > in dbid < > .", together with a stack trace which includes the modules ‘get_txtpage’ and 'inserttext’ may be reported in the SAP ASE error log during the execution of an UPDATE command while attempting to move a LOB datum from in-row to off-row.
790436 Under some rare conditions, the message, "Current process infected with signal 11 (SIGSEGV)" in the module memset(), followed by a stack trace that includes the modules comnb_i4tonum() and set_cast_truncate() may be reported in the error log when converting from int to numeric.
790442 A 9242 error, "Underflow or overflow of state stack occurred.", may be reported when an attempt to shutdown SAP ASE RepAgent is made after its memory pool is exhausted, and the RepAgent is configured for stream replication in synchronous mode.
790455 ASE Agent Plug-in uses 'iso_1' to re-connect when a mismatched character set error occurs during connection and it may fail sometimes. It should use 'utf8' instead.
790456 Under rare circumstances, an 871 error "Process < n > is trying to release a latch on buffer < 0x > (dbid: < n > , pageno: < n > ) without holding a latch on the buffer" may be reported in the SAP ASE error log by reorg defrag when used with 'skip_compact_extents' option and a lock promotion to table level has occurred while reorg was executed.
790473 The command DBCC CHECKSTORAGE() can report the error 'Compressed length ( < value > ) is too big. File probably corrupted.' in the SAP error log, if executed on an archive database that is created on a compressed dump.
790582 The 4325 error, "The specified recovery date is not between the start and end date.", may be reported when executing the LOAD TRAN WITH UNTIL_TIME generated by LOAD DATABASE WITH LISTONLY,UNTIL_TIME, if the selected time is between the time of the last transaction in the dump and the moment the dump transaction is executed.
790618 When table-valued UDFs invoke other table-valued UDFs with output table variables of the same name (as is the case for implicitly-declared output variables), incorrect results may be returned. Also, table-valued UDFS were implicitly deterministic, meaning they would only be executed once within a query plan if the parameters remained unchanged.
790654 The %SYBASE_ASE%\bin\optase.vbs script reports an invalid 'exit' statement if the specified memory is lower than the required size.
790741 DDLGen generates output with wrong @@error check
790749 When configuring a new Backup Server with sybatch.exe using sample resources file, the error, "The attribute 'allow_hosts_list' for product 'bsrv' was specified more than once in resource file 'JT1_BS.res'" may be reported.
790983 A 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database ' < name > ' ( < id > )", may be reported when the difference between the last change threshold and a user defined threshold for the log segment is less than 128 pages.
791192 setuphadr reports the error message,'Error: "{0}" database on primary and companion SAP ASE does not have the same size' if the database does not exist on secondary site.
791207 A 702 error, "Memory request for < > bytes exceeds the size of single page of < > bytes.", together with a stack trace which includes the modules 'writetext’ and 'memalloc’ may be reported in the SAP ASE error log if an in-row LOB column is updated using SAP OCS APIs.
791247 ASE configured with Always-On (HADR) logs too many messages in the error log during deactivation. The messages are "privileged spid XXX starting new transaction 'YYY' from non-replicated database ' < db > ' during deactivation."
791390 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'xpd_swap_msb_i2' together with a stack trace which includes the modules 'lddb__unscr_phys_page' and 'lddb_unscramble' may be reported in the SAP ASE error log during the execution of a cross-platform DATABASE LOAD command.
791453 The message "current process infected with 11" in the module 'tally_fetch' together with a stack trace which includes the modules 'tally_fetch' and 'showplan' might be reported in the error log if system stored procedure sp_showplan is executed at the point that the related table is to be closed during the execution of a query from the target process.
791618 updatase hangs when upgrading the primary HADR ASE. This is because master database run of free space.
791647 The error, "Backup Server: 4.15.2.5: Label validation error: seek to trailer labels failed", might be reported by the Backup Server as the result of executing LOAD WITH LISTONLY=TRAILER (or WITH TRAILERONLY) on a compressed dump of a database with a page size > 2KB.
791654 A 2620 error, "The offset of the row number at offset < > does not match the entry in the offset table of the following page: Page pointer = < > , pageno = < > , status = < > , ptnid = < > , indexid = < > , level = < > , pnextrno = < > .", may be reported when loading a transaction dump either from SAP ASE 15.7 SP60, or 15.7 SP110 version, into SAP ASE 16.0 GA version.
791767 A 2620 error, "The offset of the row number at offset < > does not match the entry in the offset table of the following page: Page pointer = < > , pageno = < > , status = < > , ptnid = < > , indexid = < > , level = < > , pnextrno = < > .", may be reported when loading a transaction dump from either SAP ASE 15.7 SP60, or 15.7 SP110 version, into SAP ASE 16.0 GA version.
791791 setuphadr does not report error when "*.site_role" properties have the same value.
791793 syconfig.exe and sybatch.exe write incorrect "ase.home" property value to %SYBASE%\COCKPIT-4\plugins\ < ASE_server_name > \agent-plugin.xml when enable ASE Cockpit monitoring.
791847 The message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the error log after starting XPserver with traceflag 8022 (turn off enhanced security) enabled.
791979 Under rare conditions, downgrading ASE 16.0 SP02 or higher to a lower SP/PL and then upgrading it again can result in an upgrade failure. When this happens, the master database will report a failure to install a required upgrade item.
792164 Post commit shrink and Housekeeper gabbage collection are blocked by each other
792195 During an UPGRADE or a DUMP and LOAD from different versions of the SAP ASE server, execution of extended system stored procedures raises an incorrect 2851 error.
792247 The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'xact_free_ps_block' may be reported in the error log during the post commit phase of an ALTER TABLE command.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0 SP02 PL02
  • 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

"Change Request", Fix, Patch, Error, Bug, EBF, SP , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.