SAP Knowledge Base Article - Preview

2090975 - Targeted CR List for ASE 16.0 GA PL05


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

If the EBF/SP has been released, check the CR list and coverletter at the

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
643556 Cross platform transaction load is not supported, but it is allowed and it may result in Msg 695, Level 21 "An attempt was made to read logical page ' < pageid > ' for database ' < db_name > ' ... Wrong logical page '2433379939' was broughtinto cache"; Cross platform load in an archive database is also not supported but it is allowed and may result in Msg 15760 - "Invalid dump header when loading the database with ID ' < n > '.".
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.
744560 In rare circumstances, when the CREATE INDEX and REORG REBUILD commands are running in parallel, WORKER processes may hang/sleep infinitely.
749795 The loginfo() built-in has been optimized to avoid blocking while database dump or dump transaction is executed concurrently. Similar optimization was made to lct_admin() built-in when used with "num_logpages" option.
751184 The Secondary Truncation Point may not be moving as expected by the SAP ASE RepAgent process in a Multiple Paths Replication environment.
756609 The wrong suid may be reported in sysprocesses when executing a stored procedure with execute as owner from another database context.
757323 The MDA table monRepSyncTaskStatistics that provides statistics on (near) synchronous replication, will report information erroneously when the current replication mode is asynchronous.
757643 Child sort thread during index rebuild leads to assertion failure as it does not recognize concurrent partition level utility execution.
760269 A 9254 error 'RepAgent( < dbid > ): Could not locate schema version for object id ' < value > ' in the transaction log." followed by a 9204 error 'RepAgent( < dbid > ): Could not locate schema for object with id = ( < value > ), current marker ( < page# > , < row# > ).' may be reported in the SAP ASE error log when SQL Statement Replication is active and a transaction involving SQL statement Replication is rolled back. This will result in the Rep Agent Thread terminating abnormally.
761333 In some workloads with lot of dynamic prepare statements executing on the system, we would see buffer cache of system table 'sysusers' and 'sysdatabases' to be hot.
762057 In rare circumstances if DBCC PSS fails it may leave the pss in a kept state and cause subsequent commands to get fail with error 8601 "Process < n > tried to keep the PSS for process < m > when it already had the PSS for process < p > kept."
762072 The messages 'ERROR: JNI_CreateJavaVM; failed attaching to the JVM for AttachCurrentThread() with -1', 'WARNING: FindClassWithLoaderID; is re-throwing Exception' or 'WARNING: FindPublicMethodFlags; is re-throwing Exception' may be reported in the SAP ASE error log, when the PCI memory pool is running out of memory.
765074 A 2546 error: "Table Corrupt: Extent id < extid > on allocation pg# < pgnum > has objid < objid > , indid < indid > , and used bit on, but reference bit off." may sometimes be reported by DBCC CHECKALLOC following the rollback of a transaction that contains a CREATE INDEX command as well as DMLs to the table within the same transaction, in a database with DDL_IN_TRAN option turned on.
765273 Select-into was not allowed in multi-statement transaction. This is now possible and is enabled by the new configuration option 'enable select into in tran'.
766247 In rare circumstances a DUMP or LOAD command could fail on a Windows platform with the error message in the SAP ASE backup server errorlog 'Error in acknowledging command '152' to the archive emulator'.
766498 A non sa_role user cannot generate DDL for a database if that user does not have sa_role.
767021 In rare circumstances, a 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < pg > , page timestamp= < ts > . Log old timestamp= < ts2 > ." may be reported during recovery when an online utility like ONLINE REORG REBUILD / ONLINE CREATE CLUSTERED INDEX / ONLINE SPLIT PARTITION command was running at the time SAP ASE was shutdown with nowait or was abnormally stopped.
767605 UPDATE STATISTICS when run concurrently with REORG DEFRAG or TRUNCATE TABLE might end up in a state where no progress is made.
767665 When the sybdumptran utility is run with the option "-p header" it will display date time fields such as 'DATABASE dump ... date Thu Jul', 'Crdate:Thu Jul' or 'Dumptrdate:Tue Jul' with a truncated value where only the first 7 characters e.g. 'Tue Jul' will be displayed.
768097 The loginfo() built-in when executed with option 'can_free_using_dump_tran' may occasionally return values other than between 0 and 100 %.
768198 In rare circumstances, when the number of OAM pages for a table exceeds the value of 32767, SAP ASE may hit a stack overflow error with a stack trace which includes the modules 'pg_allocoam' and 'pg__cond_insertoam' reported in the error log.
768463 DDLGen gets EC2 SybSQLException error when -TEC -N% on a huge number of db server
768475 If a table created in an user database with cross database encryption and decrypt default on the column is dropped from master, the following error message "The decrypt_default for column id 2 was not found in the system catalogs." is raised to the end-user.
768497 The message "current process infected with 11 (SIGSEGV)" in the module 'ejrCacheClean' together with a stack trace which includes the modules 'tdsrecv__process_batchparam' and 'sequencer' may be reported in the SAP ASE error log if a Jconnect application inserts values into a numeric column as a language batch in non-BCP mode.
768584 In SAP DBISQL if a user sets "showplan on", and the result display is in scrollable table mode and is editable, the plans for internal queries would be displayed along with the plan for the actual executed query.
768780 REORG DEFRAG leaves the number of deleted rows in systabstats unmodified.
768853 The execution of sp_addthreshold immediately after having dropped a segment with sp_dropsegment, will result in the server shutting down if the debug version of SAP ASE is used together with a stack trace which includes the modules 'th__modify_thresh_idx' and 'dbrepair' reported in the error log.
768880 In rare circumstances a deadlock may be seen between DUMP DATABASE and DUMP TRANSACTION when these commands are executed on the same database concurrently and the configuration option "enable concurrent dump tran" is set.
768903 SAP ASE running on the Windows platform can suffer an access violation exception at location 0 with a corrupted stack.
768925 The upgrade of a database created on a version prior to SAP ASE 15.7 SP100 to a higher version can take a long time to create the system table SYSDAMS if the database is big and it's almost fully allocated.
768980 GRANT DBCC MONITOR TO < user > fails with error 165 in SAP ASE 15.7 ESD2 and later versions with the error message 16 - 'Privilege DBCC monitor may not be GRANTed or REVOKEd.'
769243 When the loginfo() built-in is executed with any of the following options, “oldest_active_transaction_pct”, “stp_span_pct” or “can_free_using_dump_tran”, it may return an incorrect value of 0.
769260 In SAP ASE Cluster Edition, if a node crashes when a process on this node is in the middle of load database, node failover recovery may hang and not be able to complete.
769653 Sybmigrate supports the ASE 15.7 SP130 new features: HADR and 'Resolve as owner' on Stand By server.
769727 Error 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 for the following scenarios 1) Predicated Privileges are not being automatically re-normalized after being loaded from a dump. 2) When a predicated privilege fails to re-compile, the exception handling incorrectly cleans up leading to 706 errors.
769868 SAP ASE might report an infected with 11 (SIGSEGV) stacktrace in the function mda_flush_iostats() when the SAP ASE configuration option "enable monitoring" is set to 1.
770041 OpenSSL FIPS is not certified.
770092 A 3606 error "Arithmetic overflow occurred." may be reported during the execution of sp_helpdb on a database after loading a transaction dump into a database that has a trailing log hole.
770254 For an HADR enabled SAP ASE on the IBM AIX platform, if "sp_hadr_admin activate" command is executed, extraneous characters such as ": !" are displayed.
770255 In rare circumstances, a 605 error "An attempt was made to fetch logical page ' < pageno > ' from cache 'log cache'. Page belongs to database ' < dbname > ', object ' < Unknown > ' (0), index ' < Unknown > ' (0), partition ' < Unknown > ' (-1) and not to database ' < dbname > ' ( < dbid > ), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8)" together with a stack trace which includes the modules 'getpage_with_validation', 'num_logpages' and 'loginfo3_xactspanbyspid' may be reported in the error log when the loginfo() built-in is executed with the 'xactspanbyspid' option.
770403 Dump database with verify=read_after_write and verify=crc but with no compression specified may produce an unexpected verification message such as "Backup Server: Database repro_db: Verification reported x errors.".
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.
770468 A 12531 error "The table SYSDAMS could not be opened in database ..." will be unnecessarily reported when loading a database dump taken from a pre-15.7 version into an SAP ASE version equal or greater than 15.7, although this error will not cause the load of the database dump to fail.
770514 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.
770563 DDLGEN does not generate the correct webservice DDL.
770848 DSParser failed to detect the interfaces format when the first entry's server name is not followed immediately by the query/master service definitions.
770992 In rare circumstances, the error 692, " Uninitialized logical page ' < pageno > ' was read while accessing database ..." could be raised when creating a database with FOR LOAD option.
771039 In rare circumstances when the option 'enable incremental dump' is enabled in the database, the message 'closetable: table already closed for sdes ...' followed by a stack trace that includes the modules 'xact_end_session' and 'closetable' may be reported in the SAP ASE error log.
771055 On the IBM AIX platform, while generating stack trace, SIGSEGV (Signal 11) or timeslice error is observed in search_tbt() or strncpy().
771141 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.".
771158 In rare cases, the table may be corrupted if exception occurs when executing ALTER TABLE command to change compressed table's lock schema.
771198 The message "current process infected with 11 (SIGSEGV)" in the module 'dam_prepare_dump_end' together with a stack trace which includes the module 'dpdb_main' may be reported in the SAP ASE error log when a DUMP DATABASE is executed and while a concurrent DUMP TRANSACTION is aborted. This would require the configuration option 'enable concurrent dump' and the database option 'allow incremental dumps' being both enabled.
771230 A REORG DEFRAG process, if killed, then in rare cases could leave the state of object specifying that an utility is active.
771286 The SAP ASE optimizer can make an unexpected selectivity estimate of 0.001 when a selectivity of 0.0 is detected and optcriteria avoid_zero_weight_histograms is enabled. The cr771286 optcriteria corrects the mis-estimate.
771301 The error "Volume validation error: attempt to open ' < file name > ' returned Too many open files" can be raised by the SAP ASE backup server when trying to dump or load on the SOLARIS, HP and IBM AIX platforms after running for some time because a socket is being left opened every time a connection is established.
771433 Repeated reduction/increasing the number of running engines in threaded kernel mode (using alter thread pool) may eventually lead to a situation where a server login is not possible.
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.
771677 The SAP DBISQL window title fails to refresh after a "use < db_name > " statement is executed.
771870 When processing replicated data for a table having several BIT datatype columns, RepAgent may stacktrace in the module 'ra__substitute_vals'.
772045 SAP Application context built-in functions may report an unexpected permissions error
772101 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.
772405 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 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.
772668 SAP ASE in threaded kernel mode configured with synchronous IO may hang when there is an IO failure returned from the OS e.g. EIO.
772670 When turning on the "utility statistics hashing" configuration parameter (or explicitly using the with statistics hashing phrase) and using parallel CREATE INDEX command then a 697 error "An attempt was made to fetch logical page ' < page > ' for < ptninfo > _PTNINFO from cache ' < cache > '. Wrong logical page ' < page > ' was found in cache." can occur. This will not affect UPDATE STATISTICS or the serial CREATE INDEX command.
773094 DBISQL 16.0 allows results to be editable from the results window.
773128 Make visible. This is a placeholder CR for routing purposes, not a real fix.
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 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.
774172 SAP DBISQL 16 may use a lot of memory and scrolling the result set is slow in text mode.
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.
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.
775034 A 691 error, "Encountered invalid logical page '0' while accessing database < dbname > , object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8)." may sometimes be reported while running the loginfo() built-in with "stp_pages" option.



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


SAP Adaptive Server Enterprise 16.0


CR, CR List, ASE 16.0 PL05, ASE PL05, PL05, PL 05, Adaptive Server Enterprise, Fix, Patch, Error, Bug, GA PL05 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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.