2560200 - Targeted CR List for ASE 16.0 SP03 PL03 | SAP Knowledge Base Article

SAP Knowledge Base Articles - preview

2560200 - Targeted CR List for ASE 16.0 SP03 PL03


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
552310 When the maximum number of allowable user defined types are added, despite deleting some of existing user defined types, does not make room for adding new types.
722778 When executing DBCC CHECKSTORAGE, the worker processes created show the current database name, instead of tempdb, in the 'tempdbname' section of sp_who output. See KBA 2119852.
745608 CREATE INDEX allows '.' (period) in the index name with quoted identifiers. Once created, the index then can not be dropped through normal means. See KBA 2475406.
766251 sp_helpconfig "heap memory per user" with a new value shows the size of memory in kilobytes, but it should be in bytes.
767440 The built-in ISNUMERIC() incorrectly returns 1 (indicating that conversion to int, float, money or decimal is guaranteed to be allowed) for some inputs such as '.', ',', '$', '+', '-', 'e' that can appear in numeric values but are not valid numeric values on their own. See KBA 2053654.
778210 Under rare circumstances, an 1105 error, "Can't allocate space for object 'syslogs'...", may be raised when trying to extend a database if the last chance threshold had been reached and there are many processes in log suspend state waiting for the log space to become available.
779014 In rare circumstances, inserting rows into a database that has the option 'trunc log on chkpt' enabled may hang.
790982 A spid may hang and be unkillable if the client is unable to receive or stops receiving network requests from SAP ASE running on AIX. See KBA 2000952.
796566 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'Lop::lopProcessTree' together with a stack trace which includes the modules 'Lop::lopProcessTree' and 'lopGenerate' or in the module 'OptBlock::_OptInitProducerPj' together with a stack trace which includes the modules 'OptBlock::OptPhaseInitPj' and 'OptGlobal::GblAssignOptId', may be reported in the SAP ASE error log when a GROUP BY is used in a subquery and the subquery selects only a CONSTANT in its projection and the subquery does not have a HAVING clause. See KBA 2290097.
797077 Occasionally, a 712 message, "There is insufficient heap memory to allocate < nn > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system", may be raised, and "XML session heap memory < aa > , size < mm > bytes is not freed" could be found in the error log for the diagserver when XML table related queries are intensively used in concurrent sessions. See KBA 2453962.
797416 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qremap__obuf' followed by a stack trace that includes the modules 'qremap__tree', 'qremap__tmpobj' and 'proctree_copy', may be reported in the SAP ASE error log when declaring a table variable with a CHECK constraint. See KBA 2551743.
797450 A 2809 error, "Request for view < table_name > failed because < table_name > is a table object." may be reported during the execution of a stored procedure that has a view reference if the stored procedure was initially compiled and later the view was dropped and a table was created with the same name as the dropped view. See KBA 2297847.
798060 A 209 message, "Ambiguous column name < column_name > ", may be incorrectly reported when executing queries that involve table variables. See KBA 2308860.
799308 A 12306 error, "No table lock on object < system_tablename > in database < proxy_dbname > ", may be reported when executing SELECT INTO from a source system table into a proxy database as a non-sa user.
800915 A 926 error, "Database 'tempdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause", followed by error 1619, "Could not open TEMPDB, unable to continue." may be reported in the SAP ASE error log when loading a database dump of the master database.
803241 The option of 'ansinull' may be changed in a stored procedure when this stored procedure is triggered to recompile.
803592 In rare circumstances, the number of free log pages may sometimes be inaccurately reported when SP_SPACEUSED is run if allocated but stranded log pages exist in the database.
804522 A query that compares a CHAR with the result of DATEADD() returns different results when statement cache is active. See KBA 2409707.
805251 A 156 error, "Incorrect syntax near the keyword 'ORDER'", maybe reported in the SAP ASE error log when an ORDER BY clause is used with FOR XML in subquery. See KBA 2421236.
806252 The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dmpx__find_dmpxact_type' together with a stack trace which includes the modules 'dmpx_truncatemain' and 'dmpxact', may be reported in the SAP ASE error log when an encrypted database is dumped. See KBA 2571913.
806477 Query with MERGE statement may result in spurious errors about incorrect conversions.
806690 A 2749 message, "Number of argument position specifiers in RAISERROR command is greater than the number of arguments passed", may be reported when executing sp_sysmon with a valid section name such as sp_sysmon "00:01:01", "housekeeper". See KBA 2447113.
806734 In rare circumstances, a 257 error, "Implicit conversion from datatype ' < data type > ' to ' < data type > ' is not allowed. Use the CONVERT function to run this query.", may be reported when inserting a row into a table variable with an identity column.
807242 In rare cases, the number of log pages returned by the built-in LCT_ADMIN("num_logpages", < dbid > ) may be incorrect.
807433 In some circumstances, the value of monNetworkIO.BytesSent might not increase on IBM AIX platform even though there are some network I/O activities.
807676 The replication of a DML command on a table having a function-based index fails and a 11738 error, "Name 'sybfi < value > ' is reserved for internal use by Adaptive Server." is reported in the error log of Replication Server.
807765 A 5072 error, "ALTER DATABASE cannot remove the first 256 pages of a database", may be reported when executing ALTER DATABASE < dbname > OFF < device > .
807766 When encrypted column is enabled for a table which has default value for some columns, then in sp_help 'tablename' output,'Encrypted' property for these columns show 'NULL' value instead of 0, if the data in these columns are not encrypted.
808240 In rare circumstances, when the database option 'ddl-in-tran' is enabled and a DDL for an IMRS object is rolled back within a user transaction, then no further rows for that object will get packed to the page store mistakenly.
808280 The partial rollback of a transaction may be unexpectedly discarded by replication, resulting in a data mismatch between the primary and replicate databases.
808357 LogicalReads/PhysicalReads in the monProcessActivity, monSysStatement and monProcessStatement MDA tables will not be updated correctly when "enable compatibility mode" is set as 1. See KBA 2478206.
808761 ALLOW and DENY are not updated as SAP ASE reserved keywords leading to a 156 error, "Incorrect syntax near the keyword 'allow'." or "Incorrect syntax near the keyword 'deny'." being reported when the reserved keyword 'allow' or 'deny' is used as an identifier in any DDL statement. See KBA 2483160.
809026 When SQL Statement Replication is enabled the DSI connection may go down with error 5150, "Function 'rs_get_textptr' for table ' < table_name > ' returned multiple rows." while a SELECT INTO statement that involves LOB columns is replicated.
809243 An error, "Undeclared variable", will be raised in a SQLScript database when executing a CREATE PROCEDURE statement containing a DECLARE statement before the BEGIN...END construct.
809414 Memory requirements for the row_storage cache of On-Disk MVCC enabled databases have been reduced by keeping less metadata per row version in the cache.
809442 In rare circumstances, a session may hang in the module 'prepprev' after a rollback due to error 2601 "Attempt to insert duplicate key row in object ' < table_name > ' with unique index ' < index_name > ' ...". See KBA 2503863.
809678 DBCC HELP has no help information for the DBCC DAM command. See KBA 2548214.
809680 The output of LOAD DATABASE WITH LISTONLY=CREATE_SQL does not include the "for sqlscript" clause for the CREATE DATABASE command when executed on a database dump taken from a SQLSCRIPT database. See KBA 2547581.
809773 Occasionally, a 712 message, "There is insufficient heap memory to allocate < nn > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system", may be raised for insufficient heap memory when multiple XML sessions (such as more than 15) run XML queries at the same time. See KBA 2515782.
809944 One new row HINTS ESTIMATED_ACTUAL_ROW_MISMATCH in red will be added at the end of operator table in HTML output when the ratio of the actual row count to the estimated row count determined during a query optimization for this operator exceeds a defined threshold.
810016 A 728 error, "Allocation of size < value > bytes from the row storage cache, < cache_name > , failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < 0xaddress > " may be reported, if row storage is enabled and the current transaction is idle for a long duration.
810031 In rare circumstances, if an out-of-memory cache error is encountered during the execution of a SAVEPOINT command in an IMRS database, a subsequent attempt to rollback to the savepoint may end up rolling back the whole transaction.
810087 A new message, "(VA = < value > ) HINTS ESTIMATED_ACTUAL_ROW_MISMATCH: exec_cnt < actual > ; est_cnt: < estimate > ", will be reported when the ratio of the actual row count to the estimated row count determined during a query optimization exceeds a defined threshold. The message is reported only when 'set statistics ioplan' and traceflag 16939 are both enabled.
810115 Enhancement in HADR to allow user to configure application interface using 'sp_hadr_admin' stored procedure. The HADR map and client redirection will be based on the application interface info (if configured).
810151 In rare circumstances, an incorrect fragment size may be reported in SAP ASE configured for 2K page size, when LOAD DATABASE with 'listonly=create_sql' option is run and the fragment size is not a multiple of Mbytes.
810157 A 2405 error, "Internal error occurred while converting characters", will be raised if a string longer than 255 characters needs to be sent back to client for built-in function greatest()/least()
810170 A 3475 error, "There is no space available in SYSLOGS to log a record for which space has been reserved in database", may be reported after the command "dbcc usedextents()" is run that corrected free space count indicated by the message "Those for data or data-and-log were corrected in memory"
810229 The prefix of previous index page is propagated to the new allocated index page unnecessarily during split under Midpoint split. This is not needed and is inefficient.
810271 On SSL enabled HADR setup, if FaultManager is configured, heartbeat client may fail to boot resulting in failure of FaultManager bootstrap.
810308 On IBM AIX platform with SSL enabled, the message, "ssl_nrpacket_iocp: vsn 7 kpid 6750260 not enough space to read header", may be reported repeatedly in the SAP ASE error log and SAP ASE may become CPU bound.
810376 Error 9557 may result when the "disallow simple passwords" feature is on and passwords generated by the password_random() function happen to include the name of the login the password is assigned to. An additional optional parameter is added to password_random() so it can be passed the login name to avoid including in the resulting password string. See KBA 2525248.
810459 When sorting is required for an ORDER BY clause, and arithmetic errors occur, transaction aborts may occur, when only statement aborts are expected under sp_configure 'allow statement rollback'. Regular TUDFs mask this erroneous behavior, while inlining them (making them to behave like views) exposes it.
810474 Wrong result with truncated value will be returned for the CAST built-in function when casting to string data type in an SQLScript database.
810486 The procedure cache may get full with multiple copies of the query plan for a single stored procedure involving DDL and index creation within a transaction.
810488 The message, "Command has been aborted", may be reported when closing or deallocating an insensitive cursor. See KBA 2528002.
810525 Row storage cache memory used for RIDMAP table was 256MB for ODMVCC enabled database. The cache memory has now been reduced to 128MB.
810598 In rare circumstances, valid transactions may be marked incorrectly as invalid and their redo work skipped by IMRSLOG recovery mistakenly while the valid transactions are interspaced by a stale and invalid transaction following multiple consecutive crashes of SAP ASE. This may cause some data inconsistency in the row store.
810615 Under rare circumstances, connections to SAP ASE configured with SSL may hang during login handshake, eventually resulting in timeout.
810656 A new traceflag 11011 is added to disable the behavior where multiple INSERT statements with similar numeric input values caches a single query plan instead of creating a new plan for each statement. This behavior was introduced to avoid spinlock contention in statement cache due to large number of plans being cached for INSERT statements with similar parameters.
810687 Memory requirements for the row_storage cache of IMRS enabled databases have been reduced by re-using some of the memory in bucketpool fragment metadata.
810718 On Windows platforms, if a JDBC connection to SAP ASE with SSL enabled is not explicitly closed by the application, SAP ASE may re-run the last command and this may lead to logical corruptions.
810743 SAP ASE running on Windows will see a timeslice error if a task hits a divide by zero error
810769 Index hash caching is now enhanced to support OR operator and IN operator.
810776 In rare circumstances, a 12345 error, "Internal Error: Process < spid > attempted to get an exclusive database disk map lock while holding an incompatible disk map lock. This request has been ignored to avoid this process blocking itself.", may be reported while LOAD DATABASE is executed.
810785 In rare circumstances, loading a database may fail with the error "Backup Server: No virtual mapping for logical page ..." if the database in the dump had got some fragments removed using ALTER DATABASE OFF.
810923 A 16877 error, "Unable to create a new user-defined type 'type-name'. Please try again when there are fewer user-defined table types in SYSTYPES.", may be reported in the error log when creating many Table Types.
810947 In a single engine SAP ASE setup, two sessions may wait for each other while flushing log records from their Private Log Cache to the transaction log, when they run at a different priority.
810968 A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization.", may be incorrectly reported by SAP ASE under heavy concurrent activity during query execution.
810995 SAP ASE running on Windows NT on a virtual machine can hang when encountering a resource issue on the VM
811001 The MDA table monIMRSCacheActivity may show inaccurate values for NumRows column after a database dump is loaded in an On-Disk MVCC enabled database mistakenly.
811015 The message, "A call to strtok() failed while attempting to read dump history file < filename > " followed by a 3188 error, "No records found for database < dbname > ." will be reported when executing the command LOAD DATABASE < dbname > with listonly=create_sql without specifying a dump stripe.
811089 A 207, 233, 264, 2760, or 12810 error indicating that an invalid column name is referenced in a query, may be incorrectly reported by SAP ASE under heavy concurrent activity during query execution. See KBA 254302. Additionally a new SAP ASE trace flag 16889 is introduced which allows to enable an alternate behavior that resolves these errors. However the use of this trace flag may expose a situation, as mentioned in CR 801618, whereby a 8211 error, "A newly created ssql_id for SQL to store in statement cache is a duplicate object id of an existing table in system tempdb." may be reported or a segmentation violation in module 's_compile_stmt' may also be seen.
811110 Statements like "UPDATE TABLE_A SET COL_1 = ? ,... WHERE COL_X = ? AND COL_Y = ?" without the values of the bind variables, may be printed out in the SAP ASE error log when a deadlock happens. The information printed out is now enhanced to include the bind variables when SAP ASE prints the information about the participating spids and the SQL statements that caused the deadlock.
811150 The Tivoli Storage Manager option for mountWait '-M' was incorrectly placed as part of the stripe name in the dump history file of SAP ASE.
811154 In rare circumstances, the message "Assertion (((-1) > 0) || (int64) (PIMRS_ROW_STAT(pimrs)- > imstat_num_migrated) > = (-1 * ((int64) ((-1)))))" together with a stack trace which includes the modules 'imrs_odmvcc_pack_row' and 'trunctab' may be reported in the SAP ASE error log when an On-Disk-MVCC enabled table is truncated while concurrent activity takes place on the table and the diagserver binary is in use.
811160 Upgrade Java API for XML-Based RPC (JAX-RPC, new version is 1.1.3), SOAP with Attachments API for Java (SAAJ, new version is 1.3), Web Services Description Language for Java (wsdl4j, new version is 1.6.3) and JavaMail (new version is 1.6.0) to the latest versions.
811173 Once a spid is stuck in kctCheckAsync() loop, any changes made to 'async poll timeout' configuration parameter is not effective for that spid.
811209 When changing the replication status of a database having Global Temporary Tables to 'none', the execution of the command SP_REPTOSTANDBY < DBNAME > , 'NONE' fails with a 267 error, "Object '##xxx' cannot be found.", followed by a 18413 error, "Due to a system failure, the replication status for ' < dbname > ' has not been changed.".
811222 In rare circumstances, the message 'Current transaction ID ( < pageid > , < rowid > ) in database 'master' (dbid = 1): commit wait expired.' followed by a 9416 error, "Rep Agent on database 'master' switched from mode 'sync' to mode 'async' because timer on commit expired." may be reported in the SAP ASE error log when stream replication is enabled and an attempt to connect to SRS is made by the Rep Agent while a connection was already established.
811273 On IBM AIX platform, the message, "Current process infected with signal 4 (SIGILL)" followed by a stack trace that includes the modules 'aix_ssl_rpacket' and 'ksaixnetctlrPostRead', may be reported in the SAP ASE error log while connecting to the dataserver using SSL. See KBA 2555156.
811294 The message, "Assertion (ra_ci_context && ci_error)" together with a stack trace which includes the modules 'ra__ci_print_additional_exception_info' and 'ra_ci_exception' may be reported in the SAP ASE error log when streaming replication is enabled and the RepAgent encounters an exception while the diagserver binary is in use.
811348 On Windows platform, the error, "Do you want to allow the following program from an unknown publisher to make changes to this computer?", may be reported when executing an SAP ASE binary despite the binary being appropriately signed by SAP.
811438 The message, "Current process infected with signal 6 (SIGABRT/SIGIOT)" followed by a stack trace that includes the modules 'cfree', 'pcifree' and 'OdbcRemoteAccess::CleanUp', may be reported in the SAP ASE error log when a NUMERIC column in a proxy table mapped to HANA is queried. See KBA 2553679.
811451 In rare circumstances, the message, "pss_init(): Failed to allocate memory for IMRS_STMTDES.", may be reported in the SAP ASE error log for each new connection when the Global Fragment Pool is running low due to its size being under configured.
811471 A 3702 error, "Cannot drop or replace the database < dbname > because it is currently in use.", will be reported while trying to drop a SQLScript database if it has been accessed before from another SQLScript database. See KBA 2555871.
811521 A 691 error, "Encountered invalid logical page '0' while accessing database ' < database_name > ', object 'syslogs' (8), index 'syslogs' (0), ...", may be reported in the SAP ASE error log when DUMP TRANSACTION < database_name > WITH NO_LOG is run when the database is enabled for replication and the last change threshold for this database was crossed.
811524 Under some conditions, the procedure cache in SAP ASE may contain a large number of cached plans for the same SQL user defined function.
811555 The 'versiondbid' column of the SYSDATABASES table may be updated with an unexpected non-zero value after upgrading a SAP ASE of version 16.0 SP02 or earlier to 16.0 SP03 or later.
811653 When a Replication Server DSI thread is down due to a DDL replication error, the DDL might be skipped when resuming the connection if granular permission is enabled on the SAP ASE server.
811667 In rare circumstances, if concurrent inserts are taking place into a Data Only Locked (DOL) table while REORG DEFRAG is executed, some inserted rows may not be visible after REORG DEFRAG is completed.
811697 A 206 error, "Operand type clash: FLOAT is incompatible with MAINTENANCE TOKEN" or a 529 error, "Explicit conversion from datatype 'FLOAT' to 'UNITEXT' is not allowed.", may be reported when inserting FLOAT data with the statement cache enabled. See KBA 2558456.
811698 In rare circumstances, an 806 error, "Could not find virtual page for logical page < page_number > in database < database_name > .", together with a stack trace which includes the modules 'imrslogrec_fix_holes' and 'imrslogrec_logbounds' may be reported in the SAP ASE error log during boot time recovery.
811714 On Windows platform, the error message, "Could not start 'openssl pkcs12 -export -in < input_file > -out < output_file > -name < server_name > ....', The system cannot find the file specified", may be reported during HADR setup.
811719 In an SAP ASE HADR environment, it is not possible to define the location of the database, configuration files, translog, log and backup directories during set up of Replication Server and RMA. It is now possible to provide user defined locations for the 5 directories in the resource file for configuring Replication Server and RMA through setuphadr.
811766 In rare circumstances, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database < database_name > because the target page is not a data page..." may be reported in the SAP ASE error log by IMRS recovery following a server crash, if an uncommitted transaction was logged on a new IMRSLOG page.
811967 Only relevant for Business Suite extensions of SAP ASE: Unable to create view which is referencing non materialized temporary table which is prefixed by other user name.
811968 A 17260 error, "Can't run < sproc_name > from within a transaction", 226 error, " < command_name > command not allowed within multi-statement transaction" or 2762 error, "The < command_name > command is not allowed within a multi-statement transaction in the < db_name > database" may be reported when executing sp_spaceusage with 'set chained mode on'.
812006 Under rare circumstances, SSL connections to an SAP ASE running in process kernel mode may hang during network I/O.
812028 In rare circumstances, a 623 error, "Adaptive Server failed to retrieve a row via its RID in database < database_name > because the target page is not a data page..." may be reported in the SAP ASE error log by IMRS recovery following a server crash, if the size of IMRSLOG is large whereby log pages may need to be re-used during recovery. See KBA 2574681.
812249 A dynamic prepared statement with LIMIT clause may return wrong result with limit value passed as a variable and executed multiple times for different LIMIT values.
812304 Spurious errors may happen when trying to create global temporary table.
812309 A 3624 error, "Truncation error occurred", may be reported when executing INSERT involving NUMERIC datatypes and the statement cache is enabled. This is due to CR 805165 which addressed a spinlock contention performance scenario on the statement cache. The fix introduced by CR 805165 is now disabled by default. It can be enabled using a new trace flag 11013.
812360 A 12034 error, "Collection of monitoring data for table ' < MDA Table > ' failed due to insufficient memory. Retry when there is less load, or fewer users, on the server. < num_row > rows were not returned because < number_byte > bytes of memory could not be allocated.", may be reported when querying some MDA tables in a heavy-loaded system.
812418 On Windows platforms, setuphadr might be failed to create route if SSL enabled.




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