/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
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 SP04 . 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 Number | Description |
|---|---|
| 55716 | If a database device does not have any segment associated with it, sp_helpdb incorrectly prints the usage of this device fragment as "data only" instead of "unused by any segments". |
| 203166 | A new configuration option 'default textsize' is added to make the default textsize server configurable where textsize is the maximum size of LOB data that can be sent for a SELECT query. This configuration value can be in the range of 0 to 2,147,483,647 bytes with 32,768 bytes being the default value. See KBA 2896934. |
| 291321 | A 4305 error, "Specified file 'dump device' is out of sequence. Current time stamp is < date_value_1 > while dump was from < date_value_2 > .", will be reported during LOAD TRANSACTION when loading a transaction dump after having loaded a transaction dump that was taken with the NO_TRUNCATE option. |
| 337600 | Extended resource governor functionality to set resource limits based on user defined roles. |
| 362501 | Reporting of 1608 error, "A client process exited abnormally, or a network error was encountered. Unless other errors occurred, continue processing normally.", to the SAP ASE log can be disabled when traceflag 7869 is switched on either at boot time or at run time. See KBA 2757008. |
| 397943 | The message text for error 3409, “Roll forward transaction < xact-name > .”, and error 3410, “Roll back transaction < xact-name > -- was aborted.”, have been enhanced to also report the transaction ID value. For example, a 3410 error will now be reported as ‘Roll back transaction '$write_stats' -- was aborted (xactid: Rid pageid = 10253; row num = 16).’, and a 3409 error as 'Roll forward transaction '$write_stats' (xactid: Rid pageid = 1111; row num = 8).". |
| 403593 | In some circumstances, SAP Adaptive Server may not return any error message when setting the configuration option 'current audit table' to a non existent audit table. See KBA 2921876. |
| 475133 | A Kerberos user is now allowed to execute ALTER LOGIN...MODIFY PASSWORD by passing caller password as null, if 'allow kerberos null password' is configured to 1. See KBA 2627321. |
| 477889 | When the Rep Agent configuration parameter 'trace log file' is changed while Rep Agent is running, the new value isn't dynamically taken into account. |
| 493451 | The message for error 4325 has been enhanced to provide more context to the end-user when LOAD TRANSACTION WITH UNTIL_TIME is executed. It will be reported as "The transaction log start date ( < date > ) is more recent than the specified recovery until date ( < date > ), so it doesn't need to be loaded.". Additionally new error 4325 is added and will be reported as "Transaction log end date ( < date > ) is earlier than the specified recovery until date ( < date > ), so it has been loaded.". See KBA 2897980. |
| 497173 | Executing sp_tables against a User Defined Function may report some status incorrectly. See KBA 2411224 |
| 549837 | The output of DBCC SHOWRECOVERY show some lines with incorrect information |
| 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. |
| 555826 | When the master database is recovered from a database dump that was taken on another Adaptive Server, it may inherit a Secondary Truncation Point if the source database was marked for replication. When this happens, the message, "Warning: The Secondary Truncation Point is active in the database 'master'.", will be reported in the SAP ASE error log allowing the SA user to take an action. |
| 562207 | A new column "restricted" has been added to the output of the system stored procedure sp_helprotect to implement the protection information about SET PROXY when RESTRICTED ROLE option is used in GRANT SET PROXY command. See KBA 2159486. |
| 577300 | The message, "Message too long. Length = 1266008003", as opposed to the message, " < SQL_command > : Could not acquire < lock_type > due to < error_condition > .", may be reported in the SAP ASE error log when a transaction is started in a database that was first quiesced. See KBA 2705438 |
| 624829 | A new resource limit 'optimizer_memory_limit' has been added to be monitored by resource governor, to restrict the memory used in query optimization and reduce query optimization time. |
| 635017 | Addition of new system stored procedure 'sp_mem' which will report the total procedure cache memory used by a session (spid), the number of prepared statements and their procedure cache memory consumption. |
| 635018 | A new function, show_prepared_statements(), is provided to display the SQL text for the prepared statements. |
| 636128 | When a database dump that was gathered with either 15.7 or pre-16.0 SP03 release, is loaded into pre-16.0 SP03 PL08 release, and after the database is upgraded by Adaptive Server, the database timestamp value may jump to an unexpectedly high value. See KBA 2572545. |
| 636236 | A 14108 error, "Could not find partition descriptor for objid < value > , indid < value > , ptnid < value > in dbid < value > .", may be reported during SELECT INTO a LOB column from a source table with a non-LOB column. See KBA 2624460. |
| 637833 | Under rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'usctcondrop' together with a stack trace which includes the modules ‘rdes_free' may be reported in the SAP ASE error log when a killed kernel process tries to run on ASE engine. See KBA 2843659. |
| 639976 | show_plan built-in has been enhanced to print procedure plan information from the procedure cache. |
| 640973 | No audit records are produced for audit event 58 when it is configured and an audit table is truncated. See KBA 2547617. |
| 650665 | In rare circumstances the message "Current process infected with signal 11 (SIGSEGV)" in the module 'norm3_expr' together with a stack trace which includes the module 'norm3__process_case' may be reported in the error log when a query includes a derived table and has a DISTINCT clause with a SUBQ in resdom and has an OJ. See KBA 2413073. |
| 652932 | For showplan output having an EXECUTE step, the name of the stored procedure will also be output. |
| 659119 | Two new messages are introduced to the showplan output for dynamic prepared statements. The message, "Executing a newly cached prepared statement (SSQL_ID = < value > )", will be printed for the first execution of a dynamic prepared statement. The message, "Executing a previously cached prepared statement (SSQL_ID = < value > )", will be printed when using a previously cached plan from statement cache. See KBA 2922900. |
| 660433 | DBCC LOG will report field names when printing log records in a more consistent way across different log type of records. For example 'objectid' will be reported as 'objid', 'partition ID' as 'ptnid', 'extent ID' as 'extid', 'index ID' as 'indid' and 'cache ID' as 'cid'. |
| 660984 | A 7348 error, "Select expression results in more than one column having same name. Column name ' < colname > ' is specified more than once", will be reported if duplicate correlation names referencing different column names are present in the select list of a query. See KBA 2183207. |
| 683542 | Feature request to include database name or dbid in addition to the table name currently printed in REORG related messages in the ASE errorlor |
| 691603 | In rare circumstances, the message, "Assertion (!ctx- > cmdopt.is_tempdb) failed" may be reported in the SAP ASE error log when a temporary database with proxy_update option is in the process of being created and the diagserver binary is in use. |
| 694618 | The message, “The log page count in DBINFO for database < name > is inaccurate because dbi_freelogpages_at_ckpt < value > should be less than dbt_logsize < value > . Run DBCC TABLEALLOC(syslogs, full, fix) on this database in single-user mode to make the counts consistent again.”, may be reported in the SAP ASE error log during a database CHECKPOINT to help diagnose the origin of a 3475 error, “There is no space available in SYSLOGS to log a record for which space has been reserved in database < value > (id < value > ). This process will retry at intervals of one minute.”. |
| 697805 | When the Adaptive Server configuration parameter "quoted identifier enhancements" is not enabled and the session option "quoted_identifiers" is set, the execution of CREATE TABLE with a bracketed table name but with a quoted column name will unexpectedly result in the column being created with quotes included as part of its name. |
| 698404 | backupserver: Invalid object id found in srv_deletemutex |
| 699826 | Allow DUMP and LOAD of an in-memory database when using single-sign-on authentication mechanisms, like Kerberos. See KBA 2754515. |
| 699909 | The execution of stored procedure sp_helpartition may produce unexpected results when the configuration option 'ansinull' is enabled. |
| 700234 | A 536 error, "Invalid length parameter with value of -1 passed to the substring function.", may be reported by sp_dropserver when the target database has been created with a file based default location. |
| 701262 | A 17301 error, “’ < object-name > ’ is not a valid type name.”, may be reported by sp_addtype a bracketed identifier is given as the name of the type to be added. Additionally a 203 error, “The name ‘object-name > ’ is not a valid identifier.”, may be raised by SELECT-INTO when quoted _identifier param is not set an a bracketed identifier is in the select list. |
| 704451 | Remove orphaned transaction dump records from the dump history file when purging preceding transaction dump records. |
| 717519 | The execution of "sp_setrepproc integer_p, 'table'" on primary ASE is replicated as "exec sp_setrepproc @replicate_name='integer_p', @setflag='table', @logflag='log_sproc'" which will lead to error 18108 because the parameters combination is incorrect. |
| 718093 | The stored procedure sp_logintrigger does not warn the end-user, if the specified procedure does not exist, before successfully updating the login trigger. |
| 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. |
| 725677 | A 3250 error, "The devices < device name > and < device name > specified in the command should be different" may be reported during the execution of DUMP DATABASE to a NULL device when it is referenced more than once. See KBA 2809910. |
| 727207 | Updating a proxy table mapped to SAP IQ with an access rule bound to a column may fail with an SAP IQ error, "SQL Anywhere Error -1010024". The fix is enabled through traceflag 11249. |
| 727226 | A 908 error, "Unable to find any entries in sysusages for dbid ' < database_id > ', database ' < database_name > '. Run DBCC CHECKTABLE on sysusages in the master database.", may be reported on a database that was previously created entirely on the master device, after a full database dump of master is loaded into a freshly created master device. |
| 729284 | A 1703 error, "Failed to allocate disk space for a work table in database < database_name > . You may be able to free up space by using the DUMP TRANsaction command, or you may want to extend the size of the database by using the ALTER DATABASE command.", when reported is not reflected in the global variable @@error because the severity used was informational as opposed to insufficient resources. |
| 732697 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sscan_copy_init' together with a stack trace which includes the modules 'onlutl_getTS_for_lpage' and 'pg_oamscan_nextpage' may be reported in the SAP ASE error log when running REORG REBUILD ONLINE after executing a 'drop column with no datacopy' on a LOB column. |
| 734313 | Verifications are added in the module 'plc__shiftblock' when the PLC of a session contains erroneous metadata and is about to damage another session PLC while a 3475 error is reported. Under rare circumstances the error message 140063, "ERROR in < module_name > for plc < 0x > ... " may be reported in the SAP ASE error log. |
| 735328 | Addition of new MDA table master..monProcELC to provide statistics on Engine Local Cache (ELC) related counters. |
| 741286 | The system stored procedure 'sp_checkreswords' has been extended to check and report role names that are Transact_SQL reserved keywords. |
| 741444 | Sybdumptran utility does not print an error when an invalid meta data file is used. |
| 742869 | In rare circumstances, when the same table is created, referenced and dropped by concurrent prepared batches execution, segmentation violations errors may be reported in the SAP ASE error log together with a stack trace which includes the module 'open__byname'. See KBA 2169248. |
| 744954 | A 10866 error, "The value of 'max concurrently recovered dbs' ('1') must be less than the value of 'syb_default_pool thread count' ('1'). Use sp_configure to lower the value of 'max concurrently recovered dbs' or raise the value of 'syb_default_pool thread count'.", may be reported when 'sp_configure "max concurrently recovered db", 1' is run followed by a 5849 error, "Verification failed for parameter 'max concurrently recovered db'". |
| 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. |
| 748461 | The message "current process infected with 11 (SIGSEGV)" in the module 'open_byname' together with a stack trace which includes the modules 'col_open_range' and 'vu_redefine' may be reported in the SAP ASE error log when during the execution of a stored procedure a view statement requires redefinition as it was compiled with the configuration option 'procedure deferred compilation' enabled. See KBA 2017991. |
| 749605 | A new stored procedure "sp_optgoaldiff < optgoal_name1 > , < optgoal_name2 > " is introduced which prints the differences for active optimization criteria between two optimization goals. |
| 751131 | The Sybmon restart command fails for a halted server with messages like "ResumeThread using ptrace failed for thread nnn, errno 3" if the server is running in threaded kernel mode and the Sybmon session is not the one that halted the server. |
| 752096 | The NULL dump device is supported on Windows platform for DUMP DATABASE command which is useful for performance testing. See KBA 2809950. |
| 752204 | When the Adaptive Server configuration option ‘enable granular permissions’ is enabled, ALTER DATABASE execution would have required the OWN DATABASE privilege(on the database) instead of the MANAGE DATABASE privilege(on the database) like CREATE DATABASE requires. See KBA 1949781. |
| 752453 | The support of Java columns, installation of a jar file with installjava utility and removal of a jar file with REMOVE JAVA command is made available when using synchronous replication in an HADR setup. |
| 756013 | New Rep Agent configuration options, 'initial log scan percent' and 'max user task slowdown', are introduced for stream and synchronous replication mode. When the Rep Agent is booted, these options allow a better control of the slowdown of concurrent user tasks activity, so that the Rep Agent can reach the end of the transaction log and switch to synchronous mode on due time. |
| 756343 | The error message, "ORA-01036: illegal variable name/number", may be reported when executing a query against a proxy table mapped to Direct Connect for Oracle that uses SAP ASE keyword identifiers as the object names. KBA 2836586 |
| 760523 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sqt_deallocate' together with a stack trace which includes the modules 'lwp_create' and 's_cache_stmt' may be reported in the SAP ASE error log after a 701 error, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", is reported when a SELECT query is executed. See KBA 2496908. |
| 760591 | The MDA table master..monRepTruncationPoint may sometimes report inconsistent values for the columns LongestProcessingTime and TotalProcessingTime in an HADR setup when streaming replication is enabled. See KBA 2964874. |
| 760658 | A 702 error, "Memory request for 26216 bytes exceeds the size of single page of 16384 bytes.", in the module 'memalloc' together with a stack trace which includes the modules 'LeCloner::LeClMixedDTSarg' and 's_compile' may be reported in the SAP ASE error log when multiple duplicate entries are present in an IN list of a SELECT query resulting in the session being terminated. |
| 765005 | A 7222 error, "Received bad token 0xff from site ' < server name > '", may be reported in the SAP ASE error log when a nested RPC is executed. |
| 765203 | On AIX in threaded kernel mode, the monEngine connections column is incorrect and dump database may fail with 'soc_nconnect: No free file descriptors available' raised in the errorlog when executed concurrently with sp_listener. See KBA 2573288. |
| 765245 | Allow access to TEXT/IMAGE fields in inserted/deleted tables from triggers when 'functionality group' is enabled. |
| 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. |
| 768847 | A 804 error, "Unable to find buffer < buffer_address > from cache < cache_name > holding logical page < page_number > in sdes < sdes_address > kept buffer pool for object < object_name > ", may be reported in the SAP ASE error log after the process performing an ONLINE DATABASE is killed. |
| 769166 | The output of sp_help < table-name > will now report 'plldegree' for the table and for each index entry present in the table. The output of sp_helpindex < table-name > will now report 'plldegree' for each index entry for table. See KBA 2054738. |
| 769213 | Change made with sp_dumpoptimize to have an effect even when the Backup Server is restarted. See KBA 2064844. |
| 772020 | The XML output of cached plans may lead to XML parsing errors if it contains parameters values with XML meta-characters like '&', ' < ' or ' > '. |
| 772630 | The new fields 'dump_end_time' time when the DUMP ended and 'dump_size' expressed in pages have been added in the dump history file for better reporting. |
| 773417 | Additional information will be reported in the SAP ASE error log following a 4086 error, "Could not execute login script for user < name > ", allowing to help diagnose the cause of the error. |
| 774104 | A 15476 error, "Failed to find login password information for user < username > for key xxx", may be reported when 'login_passwd' option used in ALTER ENCRYPTION... MODIFY ENCRYPTION ... command on a connection authenticated using Kerberos. |
| 774751 | The value of IOTime, ReadTime and WriteTime queried from MDA monDeviceIO table may frequently overflow when ASE under heavy IO activity workloads. See KBA 2097726. |
| 775241 | In rare circumstances when SAP ASE is started in single user mode (-m) and a database which has async log service (ALS) enabled, is being downgraded, sp_downgrade may hang. |
| 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. See KBA 2589112. |
| 778507 | Compact output is now provided for REORG DEFRAG and REORG COMPACT utilities. |
| 778763 | dbcc memusage command might report inconsistent values under "Cache Memory" when caches are dynamically created/deleted. |
| 779014 | In rare circumstances, inserting rows into a database that has the option 'trunc log on chkpt' enabled may hang. |
| 779584 | A 4338 error, "Database < name > cannot be brought online by spid < value > because it appears to be in the process of being onlined by another session already.", or a 12594 error, "The database < name > cannot be brought online because we are unable to obtain exclusive access. The command has been aborted.", is reported with an incorrect severity when ONLINE DATABASE fails, resulting in the error not being set in the global variable @@error. |
| 780130 | A 12850 error, "Command 'setcipher' encountered invalid cipher suite name 'Strong' in cipher, preferences are unchanged" may be reported if an attempt is made to set a ciphersuite with 'sp_ssladmin' before SSL is configured with 'sp_configure'. See KBA 2904067. |
| 780558 | A new configuration option, "max number of IN elements", is added to limit the number of elements in IN clauses of a query. The default value is 0 which indicates no limit as per existing behaviour. If a value is configured, the value must be between 256 and 128,000. See KBA 2138945. |
| 780627 | The execution of DBCC TUNE with option ‘des_greedyalloc’ does not report an error message when it is repeatedly executed on the same user table. See KBA 2845839. |
| 781081 | A 8207 error, "Couldn't find an available descriptor for an object. Raise the value of the configuration parameter 'number of open objects' for more descriptors", may be reported when executing UPDATE STATISTICS WITH HASHING, leading to incorrect statistics being computed. See KBA 2555080. |
| 781187 | The error, "ct_connect(): directory service layer: internal directory control layer error: Requested server name not found", will be raised when trying to DUMP or LOAD an in-memory database using LDAP as directory service. |
| 781928 | In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc__findcachedSQLplan' together with a stack trace which includes the modules 'mem_getpages' and 'freeprocs', may be reported in the SAP ASE error log when LOAD DATABASE is run, while another session is reusing the same object descriptor, whose procedure buffer is in the process of being freed by the session running the LOAD command. See KBA 2162502 & 2270963. |
| 783406 | A 10331 error, “Permission denied, database master, owner dbo. You need the following permission(s) to run this command: UPDATE ANY SECURITY CATALOG.”, may be reported when UPDATE STATISTICS on a system table is executed by an end-user who has the privileges for managing any statistics granted, and the ASE configuration option “enable granular permissions” is on. See KBA 2163512. |
| 783675 | The thresholds metadata reported by DBCC DBTABLE may display information for segment 33 mistakenly. |
| 785335 | A 2714 error, "There is already an object named < tablename > in the database", may be reported during the recompilation of a batch of prepared statements which creates a user table in tempdb followed by CREATE INDEX or any DDL on the same table. See KBA 2368989. |
| 785816 | Cached statements using global temporary tables are shared among different users which is incorrect. In addition, the message, “Assertion (PERM_GET_APERM(pctx- > perms.bperms[0], pctx- > objtype) || pctx- > perms.bperms[0] == PERM_MNG_AUDITING)” together with a stack trace which includes the modules ‘has_privilege’, ‘ssql_save_SQL’ and ‘sqt_put_in_stmtcache’ may be reported in the SAP ASE error log when granular permission is enabled and the diagserver is in use. |
| 786358 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'deletetext' followed by a stack trace that includes the modules 'omni_text_free' and 'omni_text_recover', may be reported in SAP ASE error log during recovery after failure to insert TEXT data into proxy tables. See KBA 2187723. |
| 787154 | In rare circumstances, Adaptive Server may be unable to switch the stream mode back to 'sync' from 'async' in an HADR setup when several user tasks have requested concurrently a mode switch to 'async' due to commit time expiration. |
| 787389 | On Windows platform, if SAP ASE runs out of room in the socket table, the server will permanently stop listening for new connections even after sockets become available again. |
| 787724 | The message, "WARNING: The transaction log for database ' < database-name > ' (dbid < database-id > ) can no longer be dumped due to user ' < user-name > ' (suid < user-id > ) executing DBCC.", may be reported in the SAP ASE server error log while running DBCC SHRINKDB_SETUP. See KBA 2897502. |
| 788834 | KBA 2386865. Timeslice error with functions mda_exec and klicense_report in stacktrace when querying the monLicense table. |
| 789192 | Under rare cisrcumstances, after an upgrade of SAP ASE, a 11031 error, "Procedure ' < procedure-name > ': Execution of SQL function < function-name > failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo. < procedure-name > .", or a 11798 error, "Illegal CREATE FUNCTION statement within a scalar SQL function.", may be reported when executing a stored procedure or a function. See KBA 2217001. |
| 790553 | The message, "Update of syslogins failed", can be seen in the SAP ASE error log when a login attempt was interrupted during the update of the system table syslogins. See KBA 2201383. |
| 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. |
| 791716 | The message text for error 3474, "During redo the page timestamp value is less than old timestamp from log. Page #= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log old timestamp= < log-old-timestamp > . Log record marker = < log-marker > .", error 3478, "During undo the page timestamp value is less than new timestamp from log. Page #= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log new timestamp= < log-new-timestamp > . Log record marker = < log-marker > .", and error 6902, "Page timestamp value falls between the old and new timestamps from log. Page#= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log: old timestamp=" < log-old-timestamp > ", new timestamp= < log-new-timestamp > . Log record marker = < log-marker > .", have been enhanced to also report the relevant transaction ID. For example, a 3474 error will be reported as "During redo the page timestamp value is less than old timestamp from log. Page #=641, object id =24, page timestamp=0001 00000000. Log old timestamp=0001 00001772. Log record marker = (10253, 17). Xactid = (10253, 16).". |
| 791720 | The tran_dumpable_status() function returns status 1 for offline databases marked suspect due to rollback even though the transaction log for such databases can still be dumped. See KBA 2237035. |
| 792149 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'th_accounting' together with a stack trace which includes the modules 'xact__postcommit_processing' and 'th_ext_unreserve', may be reported in the SAP ASE error log while executing DBCC FINDSTRANDED or DBCC DBREPAIR( < database_name > , findstranded). See KBA 2554434. |
| 792255 | Trace flag 3945 is used to enable validation checks during updates in order to ensure that logging is made in the correct database. If validation checks fail, a 3945 error, "An illegal attempt was made to update < object-name > in database < database-name > using a transaction that was started in database < database-name > (mode: < update-mode-value > , type: < query-type-value > .)", is reported. This validation is now the default ASE behavior and new trace flag 3996 can be used to disable it if required. The trace flag 3945 is not active any more. |
| 792561 | Updateable cursor scans do not apply on queries with sub-selects such as 'EXISTS' and 'NOT EXISTS' sub-queries. This restriction has now been relaxed when trace flag 11015 is enabled. See KBA 2246480. |
| 792900 | The commands GRANT and REVOKE are unexpectedly replicated when the permission applies to an object in the master database and the grantee is a role or a list of roles. As a consequence, when a GRANT command is executed on a user object in the master database, the SRS DSI thread is shutdown after receiving an ASE 208 error because the user object creation isn't replicated. |
| 793970 | An infected with signal 11 (SIGSEGV) may occur when executing some sybmon commands, such as SQLTEXT, QUEUE, MMGRPOOLS, if the dump file being analyzed does not contain the procedure cache. |
| 793978 | For a multi-engine SAP ASE configured with LDAP authentication and running on the default kernel threaded mode, under rare circumstances, during a login, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'ldap_set_option' together with a stacktrace that includes the modules 'kllookupdn' and 'klbindfuncalt', may be reported in the SAP ASE log causing the SAP ASE to abruptly shut down. See KBA 2262332. |
| 794360 | The new message, "The SPQ log file in Replication Server is < number > percent full.", will be reported in the ASE error log under an HADR setup when the Rep Agent is configured for stream replication and it runs out of free packages during data replication. |
| 795557 | A 5605 message, "Prepare transaction RPC to the remote server < server_name > failed. Transaction key < key_value > . Return status -2.", may be reported because an external transaction is out of synchronisation between the local server and the remote server after a deadlock occurs on the remote server. See KBA 2276710. |
| 795930 | The stored procedure sp_errorlog is extended with new option "change bslog" which allows to recycle the Backupserver error log. See KBA 2282318. |
| 796120 | Under certain circumstances, the SAP ASE may hang during a DML operation when using Latch Free Btree indexes and the NV Cache is enabled. |
| 796164 | A 3702 error, "Cannot drop or replace the encryption key ' < encryption_key_name > ' because it is currently in use.", should be reported when DROP ENCRYPTION KEY < encryption_key_name > is run while the encryption key is still referenced, but the key was dropped mistakenly and no message was raised. |
| 796208 | Under rare circumstances, SAP ASE on Windows platform may leak memory when using security identifiers. |
| 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. |
| 797041 | A 1163 error, "The space allocated to the sysgams table in database ' < dbname > ' (dbid = #) must be at least 16 pages.", together with a stack trace which includes the modules 'pggam__srchonegampage' and 'pg_allocate_syslogs' may be reported in the SAP ASE error log when using CREATE DATABASE FOR LOAD to create a database bigger than 63GB in a 2KB server, 128GB in a 4KB server, 256GB in an 8KB server or 512GB in a 16KB server, with dedicated log devices which are placed out of that range. See KBA 2269985. |
| 797068 | Message 10330 is raised when table created by users aliased as dbo, are accessed by users of dbo owned stored procedure. See KBA 2287529. |
| 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. |
| 797999 | The message text for error 11919 has been changed to, "You cannot run REORG REBUILD in this database because either the database option 'full logging for reorg rebuild' or 'full logging for all' or 'select into/bulkcopy' is not enabled.". See KBA 2308016. |
| 798060 | A 209 message, "Ambiguous column name < column_name > ", may be incorrectly reported when executing queries that involve table variables. See KBA 2308860. |
| 798527 | setuphadr is enhanced to re-start the HADR set up from the step where it last encountered a recoverable error. If the error cannot be recovered, setuphadr will clean up the incomplete environment and re-attempt the set up. |
| 798608 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'proc_ddlmap_release' together with a stack trace which includes the modules 'ddlmap_finish' and 'xact__commit_local', may be reported in the SAP ASE error log when the database option "ddl in tran" is enabled and a transaction that contains many INSERT commands in a single batch is executed. See KBA 2316693. |
| 798661 | The message, "Assertion (pss- > powner_uid > DBO_UID)", may be reported in the SAP ASE error log when sp_modifyuser ' < user_name > ', 'resolve as', 'dbo' was initially executed while a query which involves a user table is run and the diagserver binary is in use. |
| 798781 | In rare circumstance, a 7105 error, "TEXT/IMAGE/UNITEXT page < page # > does not have a next page. Either there is a suspect text page chain, or transaction isolation level 'read uncommitted' has been set. Database tempdb, table < table name > , first text page < page # > ", may be reported when inserting data into a UNITEXT column. |
| 798983 | In rare circumstances, the message "timeslice -501, current process infected" in the module 'kbfalloc' together with a stack trace which includes the modules 'itl__realloc_aut_dict' and 'itl_au_update_xfer_mark' may be reported in the SAP ASE error log when BCP is executed with multiple threads. See KBA 3002623. |
| 799064 | A 2514 error, "Table Corrupt: Type id 56 (type name = 56) does not match between systypes and syscolumns" maybe reported by DBCC CHECKCATALOG on a database containing table-valued functions. |
| 799092 | The message, "-- Unknown object type: SF", may be reported in the context when executing the sp_helptext system stored procedure against User-Defined SQL Functions with the 'ddlgen' option enabled. |
| 799127 | A 804 error, "Unable to find buffer '0x%lx' from cache '%.*s' holding logical page '%u' in sdes '0x%lx' kept buffer pool for object '%.*s'.", maybe reported when queries generate DOL worktable and truncate it. |
| 799128 | In rare circumstances, a 821 error, "Attempt to unhash buffer in cache 'tempdb_cache' at ' < address > ' with a buffer pageno of ' < page-number > ' and database id ' < database-id > ' with HASHED status set failed - buffer was not found. 'Page pointer = < address > , pageno = < page-number > , status = < status-value > , ptnid = < partition-id > , indexid = 0, level = 0'.", may be reported in the SAP ASE error log when a query is killed while creating a worktable for reformatting. See KBA 2430458. |
| 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. |
| 799428 | When the configuration parameter 'extend implicit conversion' is set and an implicit varchar to numeric conversion is performed, the precision and scale of the resulting numeric might exceed their respective maximum values. For varchar lengths greater than 77, the resulting numeric would consist of uniquely post-decimal digits (i.e. NUMERIC(77,77)), which was not the intent. Also, extended implicit conversions erroneously suppressed truncation errors for conversions between character and int/numeric types. |
| 799684 | The "setuser" command is not replicated. See KBA 2488137. |
| 800100 | In some circumstances, a 2402 error, "Error converting characters into server's character set. Some character(s) could not be converted.", may be raised when executing a procedure but the procedure execution is not aborted leading to wrong results being returned for subsequent statements in the procedure when the server's and client's character sets are different and the same procedure has been run successfully previously and the query plan was cached. KBA: 2339369 - Procedure not exiting after Error 2402 reported |
| 800118 | 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 be reported during the execution of a stored procedure that has a SELECT query which assigns a text value into two LOB local variables. See KBA 2462386 |
| 800208 | The recovery of a database appears to hang. Multiple executions of DBCC SHOWRECOVERY will show the recovery processing the same "Current log record" (an AEXTENT) while "Recovery Pages: Getpage requests:" value increases greatly over time. See KBA 2340791. |
| 800348 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘ upwakeup’ together with a stack trace which includes the modules ‘ kbctMain’ and ‘ krtctskRun’ may be reported in the SAP ASE error log. See KBA 2769786. |
| 800440 | A new option has been added to sp_add_resource_limit, sp_modify_resource_limit and sp_drop_resource_limit to apply the limit to any user using any application. See KBA 2358540. |
| 800520 | In rare circumstances, BCP IN may fail together with a stacktrace which includes the modules 'bt__check_insert_position' and 'bt_insert' reported in SAP ASE error log when the server sortorder is something like '*nocase*'. |
| 800532 | A new config option, "decompression row threshold", is added to decompress the entire data rows instead of decompressing each columns one by one for compressed tables with large number of columns. The value of the config option represents the maximum number of columns in a table which will be uncompressed using column decompression. If the number of columns is larger than this value, SAP ASE will use row decompression instead. The default value for "decompression row threshold" is 20. |
| 800868 | A 9557 error, "The server failed to create or update a row in table ' < name > ' because a varying-length column would start at offset < value > . This starting location cannot be represented accurately in the table's row format.", may be reported during DML execution if the SAP ASE page size is configured to either 8K or 16K bytes and the database option 'allow wide dol rows' is disabled. |
| 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. |
| 800965 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des__free_txrcoldes' together with a stack trace which includes the modules 'proc__used_as_login_script' and 'dropobject', may be reported in the SAP ASE error log when a stored procedure is executed. See KBA 2479691. |
| 801212 | Performance degradation may be observed when there is procedure cache contention due to most of the engine level cache being full or empty. |
| 801219 | A 10386 message, "SELECT BUILTIN permission denied on builtin authmech, owner system security officer", will be reported when a user with SSO role and default database set to a database other than 'master', executes a query involving the built-in authmech(). See KBA 2357201. |
| 801266 | A 16386 error, "Error: SQLScript syntax 'locate' is not supported", will be reported when executing the built-in function locate() from an SQLScript database. |
| 801343 | Incorrect statistics may be generated when using the "with hashing" option with UPDATE STATISTICS. See KBA 2359108. |
| 801535 | A 16110 error, "srv_select() was called with a bad select mask (NULL) parameter." may be reported in the SAP backup server error log when a DUMP DATABASE is executed and the database is using a large number of devices. See KBA 3001387. |
| 801788 | After running command "Reorg rebuild < table_name > < index_name > ", index pages are not compressed. |
| 801872 | A 1530 error, "Create index with sorted_data was aborted because of row out of order", may be reported instead of error 15451, "You cannot encrypt/decrypt column < column_name > because it belongs to a clustered/placement index on table < table_name > . Drop the index before the ALTER command, and recreate it afterwards.", when the encryption key of an encrypted column, that is part of a clustered index key, is changed while the non-clustered indexes for this table are being rebuilt. |
| 801911 | The new configuration option 'audit trail type' when enabled allows to redirect the SAP Adaptive Server audit records to the O/S syslog file instead of storing them in sybsecurity.dbo.sysaudits_ < xx > tables. |
| 801978 | A 140 error, "Can only use IF UPDATE within a CREATE TRIGGER", may be reported when the configuration option 'procedure deferred compilation' is enabled and a body of trigger containing the UPDATE built-in function is executed (i.e. triggered). See KBA 2366912 |
| 801996 | The unique index to be used as the primary key for replication can be set manually with the new system stored procedure sp_setreppk which has the following usage: sp_setreppk table_name[, index_name]. |
| 802335 | In some cases, intelligent index scan may cause a low LIO estimate with a poor index then being chosen for the plan, resulting in poor performance. New optcriteria intelligent_index_scan (enabled by default) can be used to disable intelligent index scan at a session level. |
| 802476 | SAP ASE may return a wrong result set if a proxy table is used in a derived table and is involved in an aggregate query. See KBA 2371951. |
| 802504 | A 15434 error, "Adaptive Server failed to create an encryption key for internal use. Please contact SAP Technical Support.", may be reported when the master key password is changed with ALTER ENCRYPTION KEY after a cross platform database dump is loaded in a different endianness platform compared to the one where the full database dump was taken. |
| 802535 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'showE_STMT' followed by a stack trace that includes the modules 'show_plan' and 'LeRun', may be reported in the SAP ASE error log when executing sp_showplan if the statement has changed during the execution of sp_showplan. See KBA 2373058. |
| 802812 | Streaming replication using the Component Interface now also supports object level replication. |
| 802852 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 's_unsave_kept_stmts' together with a stack trace which includes the modules 's_normalize' and 's_xform_to_execute' may be reported in the SAP ASE error log when a query in a batch is executed and the statement cache is enabled. See KBA 2453655. |
| 803016 | Backup Server does not generate localized progress messages when DUMP or LOAD command is executed. See KBA 2382891. |
| 803087 | The message "current process infected with 11 (SIGSEGV)" in the module 'CgGenLava::CGConsScanOp' together with a stack trace which includes the modules 's_compile_stmt' and 'GenLava' may be reported in the SAP ASE error log when executing a query that use a non-correlated subquery which contains an IN clause. See KBA 2383992. |
| 803144 | In rare circumstances, a 8201 error, "Keep count of descriptor (objid= < object_id > , dbid= < database_id > ) was expected to be 1. Instead 0 was found.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'des__unkeep' and 'ptngetpages' while an object is created and SAP ASE needs to reuse a descriptor in the metadata cache to instantiate this object. |
| 803225 | The PRINT statement displays BIGDATETIME values with millisecond granularity while the documentation specifies that BIGDATETIME has a display format that includes full microsecond precision. See KBA 2385764. |
| 803241 | The option of 'ansinull' may be changed in a stored procedure when this stored procedure is triggered to recompile. |
| 803545 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_update_stmt_metrics' together with a stack trace which includes the modules 'curs_close' and 'mem_freepages' may be reported in the SAP ASE error log when a CURSOR is closed. See KBA 2533441. |
| 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. |
| 803603 | A 3732 error, "Cannot drop index < value > because there are one or more isolation level 0 scans, or REORG command, active on table.", together with a stack trace which includes the modules 'xact__commitxact' and 'dropi' may be reported in the SAP ASE error log when DROP INDEX is executed. |
| 803791 | The performance of the user_name() builtin has been improved when it is used multilpe times in the same query. See KBA 2404672 |
| 803834 | The message, "current process infected with 11 (SIGSEGV)" in the module 'des_checkpoint' together with a stack trace which includes the modules 'dpdb_main' and 'checkpoint', may be reported in the SAP ASE error log when DUMP DATABASE is run resulting in SAP ASE shutting down implicitly because of the spinlock 'Dbtable- > dbt_defpipebufgpspin' being held. See KBA 2439610. |
| 803866 | A 7718 error, "The 'CREATE ENCRYPTION KEY' command is not allowed within a multi-statement" and the 2946 error, "Failed to create service key syb_xpskey", may be reported when executing xp_cmdshell (or any extended stored procedure) within a transaction for the first time. Subsequent executions do not raise the errors. See KBA 2398458. |
| 804071 | The message, "timeslice -1001, current process infected" in the module 'pausenonatomic' followed by a stack trace that includes the module 'getpage_with_validation' and 'bt__getnextscanpg', may be reported in the SAP ASE error log under heavy concurrent activities. |
| 804078 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'com__exctnume_copy' together with a stack trace which includes the modules 'comnb_numtonum' and 'LeEvals::LeEvRun', may be reported in the SAP ASE error log if the configuration option, 'streamlined dynamic SQL', is enabled and a dynamic cursor query with an ISNULL expression on a numeric field is executed. See KBA 2493162. |
| 804096 | The 'status2' column in system table 'sysdevices' has the 17th bit (Value 65536) set, but this is not documented. See KBA 2402811. |
| 804346 | The output of str() built-in is truncated to 1024 characters when the SAP ASE configuration option "enable literal autoparam" is enabled. See KBA 2407120. |
| 804347 | KBA 2553567. In rare circumstances, when semantic partitioning is enabled, a stack trace in the function VbmManager::_VbmPutBm() may be observed if select query has join of list partitioned tables with equality predicate. |
| 804444 | Performance degradation may be observed in SAP ASE when executing a query with multiple predicates of which one is an IN list, because SAP ASE is not choosing an efficient index. |
| 804522 | A query that compares a CHAR with the result of DATEADD() returns different results when statement cache is active. See KBA 2409707. |
| 804695 | The message, "xpserver is using enhanced security", is repeatedly reported in the SAP ASE error log. See KBA 2412523. |
| 804756 | The message, "Caught IOException: com.sybase.jdbc4.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed", will be reported when executing the sqldbgr with a re-directed input file and a local variable is set in sqldbgr. A corresponding stack trace that includes the modules 'sqldbg__setvariable', 'dbgrpc_control' and 'exec__native_rpc' will be reported in the SAP ASE error log. |
| 804836 | A 718 error, "Memory allocation from process private memory is being performed by an incorrect process, ... This is an Adaptive Server internal error. Please contact SAP Tech Support", together with stack strace in the module 'LeHashOp::_LeOpOpen' may be reported in the SAP ASE error log during the parallel execution of a query. See KBA 2564532. |
| 804856 | In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of < wrong_length > . Maximum allowed length is < max_length > ", may be reported in the SAP ASE error log when page compression is used. See KBA 2595171. |
| 804886 | The message, "D00: Page Verification Error: Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; check this page (page#= < pagenum > row#=0 offset in row number table=0)", may be incorrectly reported in the Backup Server error log when executing DUMP DATABASE WITH VERIFY for a syslogs page. See KBA 2427308. |
| 804893 | A query that is using TUDF and outer joins may sometimes return incorrect results because the outer join is incorrectly changed to a regular join. |
| 804992 | A 1640 error, "Adaptive Server requires encryption of the login password on the network", and a 4002 error, "Login failed", may be reported when running preupgrade utility if the value of server config option 'net password encryption reqd' is set to 2 or 3. |
| 805018 | sp_configure raises the 5861 error, "The current 'max memory' value < max_memory_value > , is not sufficient to change the parameter 'number of user connections' to '32728'. 'max memory' should be greater than 'total logical memory' < wrong_memory_value > required for the configuration.", with an invalid value for total logical memory when configuring for 32729 or more user connections. See KBA 2417198. |
| 805133 | On Linux platform, under rare circumstances a connection to SAP ASE may hang after the client issues a cancel. |
| 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. |
| 805275 | SAP ASE server will disable ASE_JAVA functionality if the jvm.wl file is missing, and the message 10762 together with the detailed reason will be reported in SAP ASE error log. This is to improve the default security should the jvm.wl authorization file be accidentally removed. See KBA 2950988. |
| 805280 | For SAP ASE running in threaded kernel mode, a task (spid) may get stuck in kctCheckAsync(), i.e. DBCC STACKTRACE( < spid > ) shows function kctCheckAsync. This spid can be killed using 'kill < spid > ' if traceflag 7866 is enabled, or if the time (in minutes) indicated by the SAP ASE configuration parameter 'async poll timeout' period has elapsed, then the task automatically returns from kctCheckAsync() function, closing the remote connection. See KBA 2435989. |
| 805463 | Device usage information will not be reported by sp_helpdb mistakenly when the provided database name is using square brackets to escape wildcard characters such as underscores. See KBA 2426257. |
| 805527 | The monDataCache MDA table might report incorrect values in PhysicalReads, APFReads and PhysicalWrites columns that are much less than the corresponding values from the monCachePool MDA table for a data cache with multiple partitions. |
| 805701 | Executing CREATE PROCEDURE/FUNCTION DEFAULT SCHEMA with an invalid schema name will succeed in an SQLScript database if no objects are involved in the CREATE PROCEDURE/FUNCTION body. |
| 805990 | In rare circumstances on heavily loaded SAP ASE systems, CREATE TABLE into an in-memory database may hang with a stack trace which includes the modules 'getpage__noscan', 'getpage_with_validation' and 'bufsearch_cache_getlatch'. See KBA 2266313. |
| 806009 | A 1511 error, "Sort cannot be reconciled with transaction log" and a 4313 error "Recreate index failed for table < table_id > , index < index_id > . The table has been left in an inconsistent state, and the index is missing, so LOAD TRANSACTION errors may result.", may be reported when running REORG REBUILD on an allpage-locked table with a clustered index that allows duplicate rows. |
| 806011 | The error message, "Bad TDS response stream received from server. Unexpected token type received: 0", may be reported by an ODBC application when a SELECT query that contains an order by value greater than 255 is executed. See KBA 2918544. |
| 806088 | A 701 error, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", is thrown during compilation phase while executing large query with alternative_greedy_search enabled. The current fix can be enabled through the run time trace flag 11838. See KBA 2593791. |
| 806172 | A 7412 error, "Space available in segment ' < name > ' has fallen critically low in database ' < name > '. All future modifications to this database will be suspended until the transaction log is successfully dumped and space becomes available.", may be observed during execution of complex queries which involve operator GROUP BY and aggregate function SUM. See KBA 2438017. |
| 806180 | Messages on the progress of IMRS redo recovery phase for a database are now reported either to the client or in the SAP ASE error log, respectively for LOAD and boot recovery cases. Additionally when LOAD DATABASE or LOAD TRANSACTION is run, IMRS recovery messages are now reported to the client instead of the error log. |
| 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. |
| 806256 | During upgrade, when Granular Permission is enabled, connections to SAP ASE may fail with a stack overflow message followed by a stacktrace that includes the modules ' dbc_checkmode' and 'dbt_get_with_statuscheck'. See KBA 2441829. |
| 806327 | The message, "Current process infected with 11" in the module 's__prep_tablefunc' together with a stack trace which includes the modules 's_normquery' and 's_normalize' may be reported in the SAP ASE error log if a Table UDF is used in a nested subquery. See KBA 2546009. |
| 806370 | When auditing of sso_role is enabled, unexpected audit records may be generated against users without sso_role. See KBA 2441754. |
| 806377 | A 632 error, "Attempt to move memory with an incorrect length of < wrong_len > . Maximum allowed length is < max_len > .", may be reported in the SAP ASE error log when executing SELECT statements with query_text() under traceflag 16939 against a spid associated with a Java program with many dynamic parameters. |
| 806471 | The message, "IMRS Garbage Collector or Pack Task for Database < database_name > failed to start with code -7.”, may be reported in the SAP ASE error log during the recovery of an IMRS enabled database when previously ASE was shutdown using the nowait option while the database was being shutdown by dbcc dbreboot("shutdown", < database_name > ) command. |
| 806477 | Query with MERGE statement may result in spurious errors about incorrect conversions. |
| 806500 | Sub-optimal performance may result when multi-database queries are executed and the "auditing" configuration option is enabled. A contention on spinlock 'rdbt_spinlock' will be seen in the modules 'dbt_keep', 'dbt_unkeep' or 'dbt_rekeep' when called by module 'usedb' while SAP ASE attempts to open the user tables of a query. |
| 806683 | A 16878 error, "The limit specified in a LIMIT clause may not be negative", will be reported against an SQLScript database if the TOP N value exceeds the maximum value of an unsigned 32-bit integer value. |
| 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. |
| 806700 | In rare circumstances, sp_monitorconfig may return '0' value for the 'Max_Used' column for configuration parameters which internally uses memory from object pool. See KBA 2515680. |
| 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. |
| 806849 | In rare circumstances, the IMRSLOG may not be truncated following a successful execution of DBCC IMRS with option 'move truncation point' if there are long running statements or transactions active. |
| 806853 | The output for the SET option sub-commands 'show_best_plan', 'show_final_plan', 'show_lio_costing', 'show_elimination' and 'show_parallel' does not print any information when the 'brief' option is used. See KBA 2450023. |
| 806871 | Executing the built-in function get_index_info against an On-Disk MVCC enabled table may return unexpected results. |
| 806885 | In rare circumstances, the message, "Caught an Unknown exception in handleRPC" may be reported in the Webservices log when executing "exec sp_webservices 'add'" with a duplicate service name. See KBA 2710519 |
| 806917 | In Accelerator for SAP ASE, cursor pushdown does not support cursor status statement @@fetch_status. |
| 807044 | The severity level of the 9239 error message, "RepAgent( < database-ID > ): Cannot allocate < number > bytes of memory and will sleep until memory becomes available. Rep Agent Thread: < value > , status: < value > / < value > . Contact a user with System Administrator (SA) role to reconfigure Adaptive Server with more memory for Replication.", has been changed from 10 (Status Information) to 17 (Insufficient Resources). See KBA 2872312. |
| 807059 | The REORG DEFRAG command is not honouring 'enforce dump tran sequence' when 'full logging for reorg' is disabled mistakenly, causing subsequent DUMP TRAN executions to abort with a 4207 error, "Dump transaction is not allowed because a non-logged operation was performed on the database..." unexpectedly. See KBA 2456447. |
| 807128 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'altdb__report_shrinklog_info' together with a stack trace which includes the modules 'altdb__do_shrinkdb' and 'altdb_shrink' may be reported in the SAP ASE error log when shrink database and shrink log command are run concurrently. See KBA 2574170. |
| 807179 | Incorrect data may be inserted into a table in a SQLScript database when values of incompatible datatypes are used. |
| 807242 | In rare cases, the number of log pages returned by the built-in LCT_ADMIN("num_logpages", < dbid > ) may be incorrect. |
| 807270 | In custom HADR environment, if the Fault Manager is used, and if the SAP ASE is configured with the All-Pages lock scheme, then the Fault Manager shows incorrect ASE status as DB_INDOUBT even if SAP ASE is in healthy state. |
| 807307 | A 3606 message, "Arithmetic overflow occurred", may be reported when executing sp_configure " < param_name > ", 0, " < value > {K|M|G}" with a < value > greater than or equal to 2048G. |
| 807346 | A 3333 error, "Failed to get a log marker for scan to undo transaction (Rid pageid = < pagenum > ; row num : < rowid > } in database < dbname > due to error < value > .", together with a stack trace which includes the modules 'insert_unique_error' and 'abortmark' may be reported in the SAP ASE error log when Adaptive Server is rolling back a DML command and the configuration option 'user log queue size' is disabled. See KBA 2654420. |
| 807383 | On Unix platforms, in the Job Scheduler Agent (jsagent) process, when multiple threads hits a fatal signal like SIGSEGV simultaneously, then the core file is not generated. |
| 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. |
| 807532 | In rare circumstances, a timeslice error in the module 's_xform_to_execute' together with a stack trace which includes the modules 'bin__ncmp' and 'memhilo' may be reported in the error log when executing a query that includes a long IN list and the statement cache is enabled and the configuration option 'enable literal autoparam' is on. See KBA 2462063 |
| 807606 | Workload profiler has been extended to support IMRS Cache size and Version DB size estimations for On-disk MVCC. |
| 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. See KBA 2679264. |
| 807707 | A 632 error, "Attempt to move memory with an incorrect length of < negative_value > . Maximum allowed length is 16384.", may be reported in SAP ASE error log when creating a procedure which has complex SQL with nested subqueries involving the use of ' < table > .*' to represent all the columns in the tables. See KBA 2936918. |
| 807724 | sp_showcontrolinfo shows incorrect value in scope column for a "AP" binding. This only happened when the previous row is a "LG" binding and current "AP" row has the scope with NULL value. See KBA 2465543. |
| 807741 | Executing ALTER TABLE FOR PROXY_UPDATE against a proxy table mapped to SAP Anywhere or SAP IQ may fail with incorrect syntax error. |
| 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 > . See KBA 2359499. |
| 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. |
| 807779 | In rare circumstances, the message, "Assertion (scan_context) failed", together with a stack trace which includes the modules 'ra__ci_notify_syslogs_scanner_for_flush', 'ra_ci_notify_flush' and 'xact_commit' may be reported in the SAP ASE error log when streaming replication is enabled, the Replication Agent memory pool is exhausted and the diagserver binary is in use. |
| 807808 | A 987 error, "IMRS Garbage Collector or Pack Task for Database < dbname > failed to start with code -7", may be reported when "ALTER DATABASE < dbname > ROW STORAGE ON < cachename > " is run on a database that is currently offline. |
| 807819 | When the master device is upgraded from a pre-15.0.2 version of SAP ASE, the execution of sp_passwordpolicy 'list', 'allow password downgrade' should report the message 'Password downgrade is allowed' instead of 'New master database'. |
| 807823 | Empty PLC (Private Log Cache) blocks with only a BEGIN TRANSACTION log record present are flushed to syslogs during DUMP DATABASE when the database option 'allow incremental dumps' is enabled, or the database was created with the 'INMEMORY' option. This will prevent the transaction log truncation from taking place when a transaction is still open. |
| 807870 | The message, "Current process infected with signal 11 (SIGSEGV)" coming from the module 'oh_findendoffset_inobuf' together with a stack trace in the SAP ASE errorlog that includes the modules 'rvm__get_obfuscated_currstmt' and 'rvm__audit_getcommand_subcommand', may be reported in the SAP ASE error log when executing sp_addlogin and ALTER LOGIN in a batch with auditing enabled. See KBA 2469521. |
| 807871 | New feature that adds SSL support to the backup server. |
| 807929 | A 207 error, "Invalid column name 'sysstat5'", may be reported when using the migration tool to migrate from a lower version of SAP ASE (lower than 16.0 SP02) to higher version of SAP ASE, or when creating a proxy table from a higher version of SAP ASE to a lower version. |
| 807966 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'mda_populate_monSpinlockActivity' together with a stacktrace which includes the modules 'mda_exec' and 'VTABRemoteAccess::startScan' may be reported in the SAP ASE error log when a SELECT from monSpinlockActivity is run. See KBA 2545393. |
| 808040 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'pci_killslot' together with a stack trace may be reported in the SAP ASE error log during a forced shutdown (shutdown with nowait). See KBA 2573343. |
| 808080 | When the configuration parameters 'number of network tasks' and 'number of disk tasks' are changed their new value is not written to the SAP ASE configuration file. See KBA 2472350. |
| 808127 | A 154 error, "Limit clause is not allowed in view", may be reported by SAP ASE when creating a VIEW with a LIMIT clause. In addition, a 4501 error, "View < view_name > has more columns defined than column names given", may be reported when creating a View User Defined Functions (VUDF) with LIMIT clause. |
| 808160 | The execution of SP_SETREPTABLE by an unauthorized user should fail with a 18418 error, "Only the System Administrator (SA), the Database Owner (dbo) or a user with REPLICATION authorization may execute this stored procedure", as opposed to a 567 error, "You must have the following role(s) to execute this command/procedure: 'sa_role'. Please contact a user with the appropriate role for help.". |
| 808195 | SELECT INTO temp table may result in the error, "inserted value too large for column", to be reported at HANA if the source table was created using traceflag 11246 that allows mapping varchar column to HANA as nvarchar. |
| 808205 | Executing a preupgrade from an SAP ASE 12.* server to any SAP ASE version above 15.0 may result in a 207 error, "Invalid column name < column_name > ", for columns 'partitiontype' and 'conditionid' that do not exist in the SAP ASE 12.* version. |
| 808225 | A 2901 error, "Exception stack limit exceeded", followed by a stack trace that includes the modules 'getuidfromname' and 'udr_crtrole', may be reported in the SAP ASE error log when executing CREATE ROLE on AIX platform with a large number of databases. See KBA 2479506. |
| 808232 | MDA Wait events to identify IMRS GC/PACK, IMRS LOB GC, Hash Cached B-tree GC sleeps and corresponding context switch reasons are missing in the sysmon report. |
| 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. |
| 808282 | A 313 error, "The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table 'master..spt_values'", can occur if running stored procedure sp_spaceusage/sp_dboption under isolation level 0. |
| 808289 | A 12822 error, "Cannot create temporary table '## < table_name > '. Prefix name '## < table_name > ' is already in use by another temporary table ## < table_name > '.", may be reported when a SELECT query references a session temporary table while a user temporary table with the same name exists in the current session. This error will likely be seen in SAP Business Suite ASE systems. |
| 808297 | The execution of sp_dump_history @operation = 'purge', @status = 'fail' may delete all rows from the dump history file mistakenly. See KBA 2475482. |
| 808309 | In rare circumstances, the message, "DROP DATABASE could not clean < amount_of_unreleased_memory > bytes from the row storage cache, ' < imrs_cache_name > '. Please drop and recreate the cache before reusing it.", may be reported by DROP DATABASE if Garbage Collect system tasks (IMRS GC) terminate before Pack system tasks (IMRS_PACK) whereby some memory is wasted in the given IMRS cache. |
| 808353 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'ksmask_rpacket' followed by a stack trace that includes the modules 'kstcpnetctlrProcessRead' and 'iocPoll', may be reported in the SAP ASE error log. Thereafter, the SAP ASE may become unresponsive. See KBA 2336205. |
| 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. |
| 808387 | New options, 'disable_dc' and 'enable_dc', have been added to the sp_procxmode system stored procedure, to disable and enable deferred compilation for a particular user stored procedure respectively. See KBA 2755124. |
| 808428 | ALTER DATABASE ROW STORAGE OFF currently needs the database to be in SINGLE USER mode. This fix lifts this restriction. |
| 808441 | Inserts to a data row caching enabled round robin partitioned table might be disproportionately distributed. |
| 808443 | Lock promotion to table lock should be avoided when executing the command DBCC IMRS(maintain, imrslog, < dbname > , 'move truncation point'). |
| 808470 | A new option, 'with nowait', has been added to the DROP INDEX command, to let DROP INDEX return instantly and leave the major work of dropping the index like index page deallocation done in the background, allowing concurrent DDL and DML commands execution on the original user table. |
| 808494 | When SAP ASE Rep Agent is configured in LTL mode and is started with the resync option, the configuration parameter 'batch ltl' is inadvertently changed to 'false'. |
| 808518 | On HP platform, under heavy load, a spid may hit timeslice error when returning query results to the client. See KBA 2858482 |
| 808523 | A 313 error, "The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table < table_name > ", may be reported when an All-Pages Lock MDA table or proxy table is queried at isolation level 0. |
| 808535 | A 9417 error, "RepAgent( < dbid > ): The CI-resource 'CMD Package' is exhausted, please use 'sp_config_rep_agent' to increase the configuration value of 'buffer pool size'. Waiting for a free package may result in performance degradation." may be reported in the SAP ASE error log when using streaming replication while excessive flushing of partially filled packages takes place. |
| 808634 | sp_sjobcontrol stored procedure may fail with error 553 when called to enable/disable caller's scheduled jobs, using the syntax "exec sp_sjobcontrol @name='jname= < jobname > ', @option='enable|disable'". |
| 808635 | A 3944 error, "Attempt to BEGIN TRANSACTION in database < dbname > failed because the database is in standby access mode", may be reported during DBCC CHECKDB or DBCC CHECKALLOC execution if the database is in standby access mode. See KBA 2458617. |
| 808637 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'js__sequencer_load' together with a stack trace that includes the module 'js__sequencer_boot', may be reported when installjsdb is modified to include spaces instead of tab and the Job Scheduler fails to start. See KBA 2460661. |
| 808641 | In rare circumstances, if "sp_dboption < dbname > , 'single user', true" fails for an in-memory row storage (IMRS) enabled database, IMRS background threads for garbage collection and / or pack (of this database) may not be re-spawned. |
| 808652 | In rare circumstances, when ALTER DATABASE < dbname > off < device_name > command is executed concurrently with INSERT / UPDATE or DELETE commands on an on-disk MVCC enabled database, Adaptive Server may report Error 806 "Could not find virtual page for logical page < pageno > in database ' < dbname > '" along with a stack-trace involving module like 'altdb__upd_text_ptr'. Alternatively, a subsequent DBCC CHECKSTORAGE followed by DBCC CHECKVERIFY command may report hard faults. |
| 808707 | sp_helpconfig is enhanced to estimate Hash Cached B-tree (HCB) index memory pool size. |
| 808742 | For ASE running on Linux, Solaris & HP, an SSL connection may hang if the client cancels the current command while query results are being sent to client by ASE OR ASE may get cpu bound if the client of an SSL connection disconnects while ASE is writing to the connection. See KBA 2547765. |
| 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. |
| 808773 | SAP ASE server is further improved following the fix for CR 787670 to check each LOB first text page and clear uninitialized TIPSA information when the server trace flag 7167 is enabled to prevent error 632 from being mistakenly reported when compressed LOB data is in use. |
| 808784 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", followed by a stacktrace that includes the modules 'LeWkTbl::rewindWkTbl' and 'LeCache::LeCacheNext' may be reported in the SAP ASE error log when a SELECT FOR UPDATE query encounters write conflicts while executing on an On-Disk MVCC or MVCC enabled table. See KBA 2546130. |
| 808794 | Improvements have been made to audit logging. |
| 808871 | The message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace that includes the modules 'querytuning_ins_sysoptions' and 'ins_sysoptions', may be reported in the SAP ASE error log when executing a query that joins sysoptions, monProcessActivity and sysprocesses. See KBA 2545407. |
| 808888 | The fix for a long running internal 'sort_local' transaction during cursor processing causing tempdb log full scenario is turned on by default (previously TF 11821 was needed to turn this fix ON), and now TF 11820 can be used to turn the fix OFF. |
| 808897 | In rare circumstances, a 706 error, "Process < value > tried to remove PROC_HDR < value > that it does not hold in Pss.", together with a stack trace which includes the modules 'rm_prochdr' and 'memfree' may be reported in the SAP ASE error log when a process is killed. See KBA 2171618. |
| 808936 | The message, "Incorrect column type in the offset table of row < > . This row is on page < > , partition ID < > , and belongs to object 'syscomments' (ID 6) in database ' < > ' (ID < > )." may be mistakenly reported when running DBCC CHECKTABLE(syscomments). |
| 808954 | The stored procedure, sp_imrs, is enhanced to support the execution of sp_imrs 'pack', 'deleted rows' which will pack deleted rows from all tables. Additionally sp_imrs 'show' is extended to report the 'delrowcounts' entity which will display metrics of deleted rows waiting to be packed. |
| 809020 | The message, "Current process infected with signal 4 (SIGILL)" in the module 'NormalizeScalar' followed by a stack trace that includes the modules 'PesState::PesInit', 'OptBlock::OptPhaseTcLists' and 'OptGlobal::_GblSearchEngine', may be reported in the SAP ASE error log when inserting into a table with a check constraint using UNION. See KBA 2490559. |
| 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. |
| 809038 | The error, "The dbinfo anchor in the database 'database ' < dbname > '' is already locked by the task. Nested access to dbinfo anchor is not allowed.", followed by a stack trace that includes the module 'checkpoint' may be reported in the SAP ASE error log if the checkpoint task runs out of locks. See KBA 2951413. |
| 809065 | A 2705 error, “Column names in each table must be unique. Column name < column_name > in table < table_name > is specified more than once” and a 207 error, “Invalid column name < column_name > ”, may be reported against an SQLScript database when an ORDER BY clause is used in a CURSOR statement. |
| 809098 | Cleanup is failing during abort transaction due to no space in log. |
| 809100 | When SP_SHOWOPTSTATS is run on tables that have large number of step counts in statistics, other sessions may observe performance degradation when accessing same set of tables. See KBA 2492238. |
| 809121 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'LeScrollCache::LeScrCacheGetRow' followed by a stack trace that includes the modules 'LeLOBCache::copyOutParam' and 'getvalue', may be reported in the SAP ASE error log when inserting a TEXT value from a local variable after performing a substring operation. See KBA 2492093. |
| 809124 | A 16386 error, ""SQL syntax error: not enough values", will be reported when executing a SELECT INTO query in a SQLScript database. |
| 809158 | A 17262 error, "A user with the specified login name already exists.", will be reported when creating a user in a TSQL database while a user with same name exists in a SQLScript database. |
| 809160 | sp_helpdb does not indicate if a database is created as a SQLScript or TSQL database. |
| 809164 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules ‘memmove’, ‘mkvarchar’ and ‘sqlscript_parse’ may be reported in the SAP ASE error log when creating a user with an invalid password in a SQLScript database. See KBA 2546008. |
| 809179 | 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. See KBA 2545441. |
| 809188 | The error, "Invalid RPC sequence at RPC as_cmd. 5.7.2.7: RPC ('as_cmd') execution failed.", may be raised when executing a remote DUMP or LOAD at a server using a name or address-port that is redirected to the actual remote Backup Server address. See KBA 2934075. |
| 809219 | Under rare circumstances, if a SELECT FOR UPDATE query having LOB columns is executed under a transaction with statement snapshot or transaction snapshot isolation on an On-disk MVCC enabled table and before the transaction could complete, an UPDATE or DELETE query is executed on the same set of rows, UPDATE or DELETE query may go through and modify the rows instead of waiting for the transaction, having SELECT FOR UPDATE query, to be committed or rolled back. |
| 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. |
| 809244 | After the fix of CR 777172, cache size is stored in terms of 2K. Views have been changed accordingly to reflect this behavior. Cache sizes up to 2TB will show actual size in the views. |
| 809251 | The message, "Adaptive Server Enterprise system exception generated by a storage access violation" in the module 'search_root_block_from_seqnode' together with a stack trace which includes the modules 'get_root_block' and 'tdsrecv__mktree' may be reported in the SAP ASE error log when the builtin datachange() is used in a procedure. See KBA 2554157. |
| 809258 | Some messages like, "Cleanup for database ID < db_id > in < module_name > ..." were reported unnecessarily in the SAP ASE error log during the recovery process despite a successful cleanup of pre-allocated log pages. See KBA 2644346. |
| 809324 | No warning message is reported when a portion of IMRS cache memory could not be freed after executing ALTER DATABASE ROW STORAGE OFF. |
| 809330 | A 9502 error, "Data exception - string data right truncated Command has been aborted.", or truncated values for 'Name' column, may be reported if a configuration option name exceeds 25 characters when SP_MONITORCONFIG with the 'all' option is executed and the set option string_rtruncation is enabled. |
| 809337 | Point-in-Time recovery of IMRS-enabled databases using LOAD TRAN ... WITH UNTIL_TIME interface is restricted. |
| 809348 | The value of an updated column may have an incorrect column length after executing an UPSERT query on a table with a very long column name in an SQLScript database. |
| 809356 | In rare circumstances, cached rows in an IMRS enabled table which are later deleted may not be packed through background pack until the table is dropped or table reorg utility such as offline REORG REBUILD is run on the table. |
| 809365 | Buffer level spinlock statistics (like spins, grabs, waits) are not visible in MDA, sysmon or other monitoring tools. |
| 809373 | A 102 error, "Incorrect syntax near '@'", will be raised in a SQLScript database when executing a batch statement containing a DECLARE statement in a DO...BEGIN...END construct and the statement cache is enabled. |
| 809381 | In rare circumstances when REORG REBUILD is terminated using Ctrl-C, sp_help on the table undergoing REORG REBUILD returns error 17461, incorrectly indicating that object does not exist in the database. |
| 809395 | In rare circumstances, the message, "Current process infected with 11" in the module 's_execclearvar' together with a stack trace which includes the module 'tdsrecv__process_batchparam' may be reported in the SAP ASE error log during the execution of a DML on a table that has a DECIMAL column with high precision defined such as DECIMAL(38,1). See KBA 2412709. |
| 809412 | A new option 'delete' has been added to the system stored procedure sp_dump_history to delete records that contain the stripe name and/or dump_date specified. A backup of the previous dump history file is generated. |
| 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. |
| 809418 | Adaptive Sever may report SIGNAL 11 (SEGV) along with a stack involving modules like 'imrs_oldest_stmt_ts', if ALTER DATABASE < dbname > ROW STORAGE OFF is followed by DBCC DBTABLE < dbname > on a IMRS enabled database. See KBA 2546117. |
| 809421 | In rare circumstances, after a column datatype of a Data-Only-Locked table is changed from INTEGER to CHAR/VARCHAR where the column is a part of a clustered index key, the 3121 error, "Index < table > .PK_ind (objid= < objid > , indid=2) may be invalid. It uses CHAR or VARCHAR columns in its key and was created under a different sort order ID ( < sort-order-id > ) or charset ID ( < char-set-id > ) than the ones on this server (SortOrd= < sort-order-id1 > , CharSet= < char-set-id1 > )", may be reported when a dump of the database is taken, and then loaded and an ONLINE DATABASE command is executed. See KBA 2755798. |
| 809422 | A 590 error, "Dynamic SQL error - Prepared statement < ssql_id > does not exist", followed by a 709 error, "Memory request for < value > bytes exceeds the size of single page of < pagesize > bytes" or a 724 error, "Internal Error: Function 'memalloc' was passed an illegal size value < value > ", may be reported in the SAP ASE error log when executing a prepared statement with Derived Table UDF and the statement cache is enabled. See KBA 2944060. |
| 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. |
| 809449 | Creating a SQLScript database succeeds unexpectedly on Windows platform. SQLScript database is not officially supported yet on Windows platform. |
| 809476 | A SELECT FOR UPDATE query, executing on an In-memory MVCC table and selecting a column which is part of an index of the table, may get unexpected output. |
| 809498 | A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ) and not to database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ) or a 692 error, "Uninitialized logical page < page_num > was read while accessing database < db_name > ( < db_id > ), object < object_name > ( < object_id > ), index < index_name > ( < index_id > ), partition < partition_name > ( < partition_id > ). Please contact SAP Technical Support." may be reported when a user is inserting a data from a source table to target table using SELECT INTO command while another user is fetching data from target table at isolation level READ UNCOMMITTED. See KBA 2502516. |
| 809524 | When an IN subquery contains a reference to a table-valued UDF and there is no correlating column, the subquery may be erroneously flattened (converted into a join) resulting in a segmentation violation session termination. |
| 809611 | The 728 error, "Allocation of size %d bytes from the row storage cache, '%.*s', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = 0x%x.", may be reported for row storage if the transaction is idle for a long duration. |
| 809613 | A 247 error, "Arithmetic overflow during implicit conversion of BIGINT value '2147485186' to a INT field.", may be reported when the PAGEINFO built-in is run with the options 'page number', 'next page' or 'previous page'. |
| 809658 | Garbage collector for In-Memory Row Storage may get blocked on a utility, such as REORG REBUILD, REORG RECLAIM_SPACE, REORG FORWARDED_ROWS, REORG COMPACT, ALTER TABLE, CREATE CLUSTERED INDEX, DROP INDEX, TRUNCATE TABLE, even after the utility has exclusive lock granted on the table or does not involve the In-Memory row store content. |
| 809659 | Crossed and nested cursor operations are now supported in Accelerator for ASE when propagating them into HANA. |
| 809661 | HANA column table identity column is now supported when executing DDL statements on tables that have an identity column. Traceflag 17001 is required to turn on this enhancement. |
| 809663 | On IBM AIX platforms, the sp_add_resource_limit...idle_time parameter does not work with the resource governor. |
| 809669 | In rare circumstances, the message, "Invalid column length: < value > . Value must be between 0 and < offset > at offset < offset_value > for 'data-only' row with minimum row length of < min_value > ", followed by a stack trace that includes the modules 'hkgc__processindexpg' and 'imrs_mvcc_is_ridstale' may be reported in the SAP ASE error log when the housekeeper process runs Garbage Collection on an MVCC enabled table. |
| 809672 | In an SAP ASE HADR environment, under situations when the SAP ASE server is listening on multiple ports, then an HADR aware client may fail to receive the HADR map of the configuration from the server. |
| 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. |
| 809700 | Queries involving large number of SUM aggregates execute slowly on SAP ASE in an Business Warehouse type of environment. See KBA 2885872. |
| 809701 | When the cache size is changed by actions performed during the execution of sp_cacheconfig or sp_confighistory, the old cache size value is reported in 2K-bytes and the new cache size value is reported in K-bytes which causes inconsistency and confusion. |
| 809718 | When "set forceplan on" is enabled, the internally generated abstract plan may lead to very inefficient plan to satisfy the forceplan for the queries which involved min/max operations. See KBA 2364881 |
| 809748 | The message, "SSL or Crypto Error Message: 'The SSL handshake failed. Root error: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol'", may be reported in the SAP ASE error log when an SSL connection reuses a socket that was previously used by a terminated site handler. See KBA 2533391. |
| 809751 | A 18004 message, "Audit option 'sproc' is ambiguous", may be reported when executing sp_displayaudit 'global', 'sproc' after upgrading to a SAP ASE 16.0 version from a version prior to 16.0 |
| 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. |
| 809777 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < dbname > ' because the requested RID has a higher number than the last RID on the page ...", may be reported when DBCC LOG( < dbid > , -1, < partition_first_page > , 0, < number_of_log_records > , -3) is run and the database has an empty IMRSLOGS. See KBA 2936503. |
| 809793 | SAP ASE applies the 'allrows_mix' optgoal instead of the current session level optgoal at the query level if an invalid user defined goal is sent with the abstract plan. |
| 809794 | A 6807 error, "Initialization of the cache, ' < cache name > ', failed due to insufficient memory available to allocate < cache size > bytes. Increase the value of 'max memory' configuration parameter and retry." can occur during reboot if the system is downgraded from SP03 PL01 or SP03 PL02 to SP03 GA. |
| 809799 | A 515 error, "Attempt to insert NULL value into column < column_name > , table < table_name > ; column does not allow nulls. Update fails.", may be reported when executing sp_cacheconfig after an IMDB cache which is bound to a device or database is deleted. |
| 809800 | A 7130 error, "WRITETEXT with no log is not valid at this time. Database testdb1 must first be configured for this.", may be reported when WRITETEXT is run against an in-row LOB column while replication is enabled. Additionally when WRITETEXT is run against an off-row LOB column of an MVCC or On-Disk-MVCC enabled table while replication is enabled a ROWIMAGE log record is logged twice mistakenly. |
| 809804 | On rare occasions when the first transaction in SYSIMRSLOG, that spans across multiple pages, is not flushed, recovery may erroneously consider SYSIMRSLOGS to be empty and not recover any transactions. |
| 809831 | In an HADR environment, the message, "Current process infected with 11 (SIGSEGV)" in the module 'ra__health_check' followed by a stack trace that includes the modules 'rep_drain_log', 'hadr__drain' and 'hadr__deactivate' may be reported in the SAP ASE error log when one of the Rep Agent Threads terminates during the deactivation of the primary ASE. See KBA 2546075. |
| 809880 | Using streaming replication in synchronous mode together with multi-database transactions, it is possible that data is no longer replicated and the task executing the transaction sleeps until another task executes a single-database transaction in the same database. |
| 809940 | SAP ASE does not report an error about missing an external login during scheduled job creation using sp_sjobcreate with jproperties=run_as_owner. |
| 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. |
| 809966 | JDBC application may encounter connection dead exception, login failed or hang while connecting to an SSL enabled server. |
| 809999 | KBA2544712 Executing sp_configure with no parameter may result in the error, "No matching configuration options. Here is a listing of groups:" while printing out group information. |
| 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. |
| 810033 | Under rare circumstances, a 728 error, "Allocation of size < n > bytes from the row storage cache, < imrs cache name > , failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information ....", followed by the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ridmap_update' together with a stack trace that includes the modules 'imrs__upd_ridmap' and 'imrs_rollback_imrv', may be reported during rollback of pack operation if the IMRS cache is under configured. |
| 810067 | Binary data may get truncated in SELECT UNION ALL queries executed against proxy tables. |
| 810076 | Implement Microsoft Authenticode SHA256 signing for SAP ASE binaries on Microsoft Windows. |
| 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. |
| 810098 | Attempt to delete a row storage cache bound to a database may inadvertently change the cache replacement policy of the cache while failing with error 16763, "sp_cacheconfig failed since the cache ' < cache_name > ' is in use as ROW STORAGE cache by database ' < dbname > '." |
| 810114 | Predefined entities less-than sign ' < ' and greater-than sign ' > ' in SOAP body elements are converted into ' < ' and ' > ' when a document/literal style web method is invoked by webservices. |
| 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). |
| 810126 | Files created with the compression library when DUMP DATABASE/TRANSACTION < dbname > to 'compress:: < pathname > ' is executed will get the standard umask defined by the end-user who has started the backup server instead of 640 (rw-r-----). See KBA 2514450. |
| 810132 | The 814 error, "Keep count of buffer ' < buffer addr > ' in cache ' < cache name > ' holding logical page ' < pageno > ' in database ' < database name' has become negative" followed by a stack trace that includes the module 'dam__destroy' may be displayed when creating a database, if the option 'allow incremental dumps' is enabled in the model database. |
| 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. See KBAs 2722712 and 2722713. |
| 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() |
| 810161 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module ‘imrs_odmvcc_pack_au’ together with a stack trace which includes the modules ‘pg__objdeall_process_alloc’ and ‘pg_ptndeall’ may be reported in the SAP ASE error log instead of a 4341 error, "Cannot load the database 'db_name' because the row storage cache doesn't exist. Please, create a row storage cache with at least 'row_storage_size' and retry the command", when an ODMVCC database dump is loaded on to a NON-ODMVCC database. See KBA 2533988. |
| 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". See KBA 2519484. |
| 810179 | In rare circumstances on a heavily-loaded multi-engine system, a 1265 error, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family the message.", followed by the message "current process infected with 11" together with a stack trace which includes the modules 'dbinfoget_exst' and 'dmpx__finishdump' may be reported in the SAP ASE error log when DUMP TRANSACTION command execution gets into a deadlock. See KBA 2953716. |
| 810188 | A 12323 error, "Internal error occured during rebuild of index id < index id > of table < object id > (id = < id > ) in database < database id > while processing page < page id > . Run dbcc checktable to see if the index is consistent." may occur when executing REORG REBUILD on a Latch Free Btree index. |
| 810202 | In rare circumstances, a 803 error, "Unable to place buffer < buffer_address > from cache < cache_name > holding logical page < page_number > in sdes for object < object_name > - either there is no room in sdes or buffer already in requested slot", following a 7901 error, "Page < page_number > , partition ID < partition_id > , is expected to be the first page of a text/image/unitext value", may be reported when DBCC REBUILD_TEXT is executed. |
| 810222 | Executing sp_help ' < proxy_table_name > ' may report an incorrect fully qualified name for the remote object name when there are more than one proxy table defined with the same name but with different owners. See KBA 2602353. |
| 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. |
| 810248 | An uncommitted transaction on sysconfigures will cause 'shutdown with nowait' to hang. The shutdown can be completed if the transaction is committed or aborted. |
| 810261 | The message, "Assertion (sdes) failed in file abortcmd.c ...", followed by the message, "Assertion (XACT_CHECK_STATE(xdes, XACT_IN_CMD)) failed in file abortcmd.c ...", may be reported in the SAP ASE error log when ALTER DATABASE < database_name > OFF is run and the database has On-Disk MVCC enabled tables while the diagserver binary is in use. |
| 810271 | On SSL enabled HADR setup, if FaultManager is configured, heartbeat client may fail to boot resulting in failure of FaultManager bootstrap. |
| 810276 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module '__milli_memcpy', followed by a stack trace that includes the modules 'tdsrecv_params', 'tdsrecv__process_batchparam' and 'tdsrecv__dynexec_batch', may be reported in the SAP ASE error log when a JAVA application executes an INSERT with a TINYINT datatype. See KBA 2554290. |
| 810279 | When Rep Agent is configured for stream replication and the connection to Replication Server is lost, immediately after reconnecting, it may terminate with a stack trace which includes the modules 'ra_ci_scanner_thread' and 'ra__ci_flush_CI_stream' reported in the SAP ASE error log. See KBA 2553761. |
| 810282 | In rare circumstances, Rep Agent may fail to start with the message, "Current process infected with 11" together with a stack trace which includes the modules 'ra__init_qa_hooks' and 'actx_set' reported in the SAP ASE error log. See KBA 2329207. |
| 810286 | High contention on spinlock for global scheduler queue ('global sched') may be observed for some highly concurrent workloads. |
| 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. |
| 810312 | A 632 error, "Attempt to move memory with an incorrect length of < > . Maximum allowed length is < > .", may be reported in the SAP ASE error log during LOAD TRANSACTION if the dump contains log records for index compressed pages as a result of REORG REBUILD INDEX execution. See KBA 2395755. |
| 810357 | The 6924 error, "The chain of database fragments used by the Sysimrslogs table seems corrupted. A scan of the table would result in an infinite loop. The command will be aborted. Please contact SAP Technical Support." may be reported in the SAP ASE error log at the beginning of a database recovery. The recovery progress will show a negative number of pages to be processed. This doesn't affect recovery. See KBA 2947082. |
| 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. |
| 810384 | JDBC based applications may fail with the exception, "com.sybase.jdbc3.jdbc.SybSQLException: Stored procedure 'sp_drv_getchainedtransaction' not found". See KBA 2525896. |
| 810398 | In certain cases, Abstract Plan may be incorrectly stripped off when dynamic SQL uses polymorphic built-in functions. See KBA 2748978. |
| 810405 | With replication on, error message 632, "Attempt to move memory with an incorrect length of < wrong_val > . Maximum allowed length is 16384.", may be raised while trying to decrypt any encrypted column of table when set encryption password was set for that column and not for encryption key with which column is encrypted. See KBA 2951882. |
| 810432 | Allow IMRSLOGS threshold actions to restart when SAP ASE is rebooted and the free pages count is still below the defined threshold level for both single and multiple thresholds modes used for IMRSLOGS. The later mode is enabled with the SAP ASE trace flag 7439. |
| 810440 | Within a SQL UDF (scalar or Table-Valued), nested SQL operations that open database objects may fail with error number 622, erroneously claiming that there is a conflict with objects open in the enclosing SQL UDF. |
| 810443 | A 208 error, " < table_name > not found", will be reported when accessing a table created in a SQLScript database by using the SELECT INTO command issued from a TSQL database. |
| 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. |
| 810462 | An invalid TDS error might be observed while running builtin index_col on global temporary table created with index compression set to on. |
| 810463 | In highly concurrent environments with scans on few tables, contention on buffer-level spinlock (‘bufspin < cache name > ’) for latching the buffers corresponding to scanned pages may be observed. |
| 810467 | A 1290 error, "Internal Error in lock manager routine: Attempted lock upgrade from update row to exclusive row in parallel query thread (family id < value > , spid < value > is Illegal.", together with a stack trace which includes the modules 'lock__ins_logical' and 'dol_update' may be reported in the SAP ASE error log when an UPDATE query is executed in parallel mode. See KBA 2952307. |
| 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. |
| 810485 | The output of SELECT SHOW_CACHED_PLAN_IN_XML garbles the values of the bind parameters if the parameter count is more than 35. See KBA 2593765. |
| 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. |
| 810493 | The datachange column is in the sp_showplan output only when @display_lvl short, full or long is used. To see the datachange column, you don't need to enable show_object_list, and outside of sp_showplan, show_object_list doesn't show datchange column. View the datachange column when you want to immediately identify if tables involved in a query may have outdated statistics. |
| 810512 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'get_stored_char_size' together with a stack trace which includes the modules 'get_unicode_text' and 'sqlscript_lex' may be reported in the SAP ASE error log when creating a procedure that contains comments like '/*****/' in a SQLScript database. See KBA 2933987. |
| 810525 | Row storage cache memory used for RIDMAP table was 256MB for ODMVCC enabled database. The cache memory has now been reduced to 128MB. |
| 810533 | In rare circumstances, a 12301 error, "Internal error: the index (id = 0) and the data for row (Pageno, Rowno) in table ' < Tablename > ', database < dbid > are inconsistent; data is marked deleted but index is not. Aborting the transaction", may be reported from a process that is running a query on a DOL table with isolation level 0. See KBA 2588993. |
| 810542 | When a dynamic prepared statement with the abstract plan hint "use with_recompile" is executed, Adaptive Server will not recompile the statement unexpectedly. |
| 810581 | The commit of transactions in an IMRSLOG database could take longer due to the absence of group commit functionality support for IMRSLOG. |
| 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. |
| 810647 | A 806 error, "Could not find virtual page for logical page < n > in database ' < dbname > '", may be reported in the SAP ASE log when updating a base table column used in a materialized view with 'IMMEDIATE REFRESH' if the base table has a TEXT and/or IMAGE column(s). See KBA 2531239. |
| 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. |
| 810688 | A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be reported during the execution of a query that is using a fact table hint and no legal execution plan is found. |
| 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 |
| 810757 | A predicate with multiple columns, such as ((c1,c2) > (x,y)), can be incorrectly qualified as a criteria for partition elimination. This may lead to incorrect results. See KBA 2345886. |
| 810764 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ind__get_sysindrow' together with a stack trace which includes the modules 'par_get_info' and 's_runtime_compile', may be reported in the SAP ASE error log when a stored procedure that creates temporary tables is executed and SAP ASE references the wrong object. Use the SAP ASE command line (boot) trace flag 11014 to enable the current fix. See KBA 2438077. |
| 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: 3.29.2.1: No virtual mapping for logical page ..." if the database in the dump had got some fragments removed using ALTER DATABASE OFF. See KBA 2543492. |
| 810799 | In rare circumstances when DDL replication is enabled, some DDL commands may not be replicated from the primary SAP ASE when the default data cache is under configured and lots of concurrent replication activity is taking place. |
| 810812 | The Migrated Version to modify a row, residing on a datapage, in an On-Disk MVCC enabled table is now no longer created. |
| 810847 | When the option 'set statistics io' is enabled, the output has been enhanced to display the number of logical and physical IOs for the sysversions table for On-Disk MVCC enabled tables and the number of rows read/write or migrated to IMRS for Data Row Cached and MVCC enabled tables. |
| 810863 | auditinit fails to start if no sa password is provided. |
| 810912 | When the option "set statistics on" is enabled, a 16064 message, "SET STATISTICS ON: file ' < filename > ': file open failed with error < error_number > : File exists", may be reported when executing multi statements within one second. |
| 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. |
| 810933 | systypes.uid in the SYSTYPES system table may be incorrect when creating a user-defined table type as non-DBO user. |
| 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. |
| 810948 | Apache Jakarta Common CLI has been upgraded to version 1.4 and Apache Jakarta Common Logging has been upgraded to version 1.2. |
| 810952 | On HP and IBM systems, the message, "Stack overflow detected" in the module 'upunsetcritical' together with a stacktrace which includes the modules 'kcvDeleteCondVar' and 'ubf_is_addr_inpool', may be reported in the SAP ASE error log during a graceful shutdown of the server while the diagserver binary is in use. |
| 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. |
| 810976 | A 156 error, "Incorrect syntax near the keyword 'set message_text'", will be reported when updating a column with name 'message_text'. See KBA 2540286. |
| 810985 | When a table that has a UNITEXT column is marked for replication sometimes the data may not be replicated correctly. |
| 810991 | In a DRC/IMRS MVCC enabled table, rollback of a command may fail due to lack of memory. |
| 810995 | SAP ASE running on Microsoft Windows on a virtual machine (VM) can hang when encountering a resource issue on the VM. See KBA 2542797. |
| 811000 | In rare circumstances, a decrease in the UsedSizeHWM, PctUtilHWM and NumRowsHWM values may be observed in the output of "sp_imrs 'show','cacheinfo'" when a large number of DMLs have been running for a significant amount of time and the sp_imrs command is executed in between the DMLS. |
| 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. |
| 811009 | Under certain circumstances, negative values may be reported by SAP ASE in the MemForRowVersionsOverhead and/or MemForOlderVersions columns of the monIMRSPartitionActivity and monIMRSCacheActivity MDA tables for databases that use In-memory row storage either for row caching or on-disk MVCC. |
| 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. See KBA 2721986. |
| 811034 | The message "current process infected with signal 8 (SIGFPE)" or "timeslice < value > , current process infected at < address > " in the module "s__collectdiagparam" may be reported in the errorlog when ASE has not restarted for long time. See KBA 2542965. |
| 811046 | The message, "timeslice -1001, current process infected" followed by a stack trace that includes the module 'mda_populate_monCachedProcedures', may be reported in the SAP ASE error log when querying the monCachedProcedures MDA table. See KBA 2541894. |
| 811061 | The execution of the system stored procedure sp_who may show an empty or erratic value for 'hostname' for the JOB SCHEDULER task as opposed to a NULL value. |
| 811074 | The message, "Estimated remaining rollback time is < negative-value > seconds.", may be reported when KILL < spid-value > WITH STATUSONLY command is executed on a session that is in the process of rolling back a transaction. See KBA 2542597 |
| 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. 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. See KBA 2543028. |
| 811094 | In rare circumstances, a 835 error with state 3, "Illegal attempt to change contents of buffer: ...", in the module ‘smp_bufpredirty’ together with a stack trace which includes the modules ‘bt__pgdealloc’ and ‘bt_shrink_post’ may be reported in the SAP ASE error log during the execution of a DML query while the buffer is being de-allocated and another session is in the process of changing it. See KBA 2549500. |
| 811095 | Workload Profiler is enhanced to be able to predict DRC suitability, estimated IMRS GC and IMRS PACK threads. |
| 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. |
| 811125 | The message, "Current process infected with signa 11 (SIGSEGV)" in the module 'ind__get_sysindrow' together with a stack trace which includes the modules 'reindex' and 'exec_dbcc' may be reported in the SAP ASE error log when DBCC REINDEX is executed on an invalid object that is not an index. See KBA 2544150. |
| 811135 | After an upgrade, a 10330 error, "INSERT permission denied on object < obj_name > , database < db_name > , owner < username > ", may be reported when procedures are executed by a user without explicit permissions on the underlying objects ( only partitioned tables) in the procedures. See KBA 2560832. |
| 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 when using the SYB_TSM library. |
| 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. |
| 811166 | The "sp_imrs 'clear', 'blocking_spid'" interface has been enhanced to forcefully preempt statements that may be blocking IMRS Garbage Collection. |
| 811173 | Once a spid is stuck in kctCheckAsync() loop, any changes made to 'async poll timeout' configuration parameter is not effective for that spid. |
| 811176 | setuphadr is enhanced to support SSL connections for Backup Server. |
| 811197 | A new stored procedure, sp_shrink, is now provided to shrink devices and databases.. See KBA 2770197. |
| 811203 | A 728 error, "Allocation of size 10944 bytes from the row storage cache, 'imrs_cache', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = 0x10", may be reported unexpectedly in the ASE SAP error log when a SELECT query is run on an IMRS-enabled table. |
| 811206 | Under some circumstances, the DSI thread may shut down with a 3959 error, "New transaction cannot be started as Adaptive Server is in 'Inactive' HADR state. The command could not be completed", reported in the standby SAP ASE when replicating a CREATE MATERIALIZED VIEW statement in a HADR setup. |
| 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. See KBA 2952325. |
| 811265 | Incorrect run sizes for the data caches may be reported by sp_sysmon with the "cache wizard" option. See KBA 2540661. |
| 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. |
| 811296 | Incorrect HitCount and NumInserts may be reported in the monStatementCache MDA table. See KBA 2548423. |
| 811339 | A stored procedure recreated with the option "CREATE OR REPLACE" and where 'deferred name resolution' is ON, may incorrectly keep in memory older version of the procedure. When executed, this older version may be used instead of the new one. |
| 811341 | A 9502 error, "Data exception - string data right truncated", is not raised as expected when string values in variables are truncated. See KBA 2534801. |
| 811343 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ssql_lookup', followed by a stack trace that includes the modules 'sqt_get_from_stmtcache' and 's__xoltp_dynprepare', may be reported in the SAP ASE error log when executing a dynamic SQL with the statement cache enabled. See KBA 2535419. |
| 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. |
| 811382 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'p_fill_syscolumns' together with a stack trace which includes the modules ‘proccreate' and 's_crtproc', may be reported in the SAP ASE error log when creating a SQL function with table types. See KBA 2580511. |
| 811395 | The error, "Page Verification Error: Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table ...", can be incorrectly reported in the SAP backup server error log if the command DUMP DATABASE WITH VERIFY=HEADER is executed on an encrypted database. Additionally the command LOAD DATABASE WITH VERIFY will fail to load a database that is encrypted instead of just ignoring the VERIFY option. See KBA 2550069. |
| 811413 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'tally_fetch' together with a stack trace which includes the modules 'tally_fetch' and 'showplan', may be reported in the SAP ASE error log if the 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. This is quite similar to CR 791453, but the error happens when accessing SYSLOGS. See KBA 2550674. |
| 811438 | The message, "Current process infected with signal 6 (SIGABRT/SIGIOT)" followed by a stack trace that includes the modules 'cfree', 'pci_free' 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. |
| 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. |
| 811480 | A 'Blocking call exception' on SAP ASE can crash the server if another exception occurs in the handler itself. |
| 811490 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'js__expirejobs' (or js__collectjobs or js__add_dup_callout) together with a stack trace which includes the modules 'jobscheduler' and 'js__chores' may be reported in the SAP ASE error log when the timeout parameter for a job is set to a non-zero value and the configuration option 'enable job scheduler' is enabled. See KBA 2837701. |
| 811498 | Spurious messages "Warning: Unknown parameter" on several configuration parameters may be reported in the SAP ASE error log. See KBA 2552639. |
| 811504 | A 2702 error, "Database 'master' does not exist." and the message "Database 'master': ASE could not completely upgrade this database" might be reported during upgrading a server earlier than 16.0 SP03 to 16.0 SP03 or later. See KBA 2552823. |
| 811515 | Wrong value inserted with stored procedure passing decimal or numeric |
| 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. See KBA 2948001. |
| 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. See KBA 2687228. |
| 811554 | An ODBC syntax error, "Syntax error or access violation;257 sql syntax error: incorrect syntax near ')'", may occur for an INSERT-SELECT query which contains a column name that is longer than 11 characters. |
| 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. |
| 811564 | A 101 error, "SQL syntax error", followed by a 137 error, "Must declare variable '@segmentna'", will be reported when SP_IMRSLOG_THRESHOLDACTION is triggered in an IMRSLOG database whose database name is more than 11 characters long. |
| 811581 | Under certain circumstances, SAP ASE may hang during a DML operation when Latch Free Btree indexes are used and the Lock Less Data Cache is enabled. |
| 811583 | In rare circumstances, despite multiple threshold procedures on IMRSLOG are triggered, only the first invocation is able to successfully pack some rows. This eventually leads to IMRSLOG full situation, causing the workload of a single task performing random DMLs on several IMRS enabled tables to hang. |
| 811597 | When SSL is enabled, an attempt by SAP ASE to connect to a backup server which is down results in a hang. |
| 811606 | A 15916 error, "Text pointer value < text-pointer-value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column-id > in row < row-id > located on page < page-number > partition ID < partition-id > for object with ID < object-id > and references first text page < first-text-page-number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, involving updates to rows containing in-row LOB columns. |
| 811615 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log ...", may be reported during LOAD TRAN when DBCC TUNE with one of the options "ascinserts", "indextrips" or "oamtrips" was run for a table stored in a different database than the source database where the dump was taken. See KBA 2556287. |
| 811649 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrs_odmvcc_pack_row', together with a stack trace which includes the modules 'imrs_odmvcc_pack_au' and 'dropo' may be reported in the SAP ASE error log when dropping an On-Disk MVCC enabled table. See KBA 2562972. |
| 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. |
| 811663 | Performance degradation may be observed when the SAP ASE optimizer selects a sub-optimal query plan in some cases where there are variables in the WHERE clause. See Note 2781778. |
| 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. See SAP note 2777678 |
| 811681 | In rare circumstances, the message ”timeslice error: spid < value > exhausted its 'time slice' of 100 milliseconds and additional 'cpu grace time' of 500 ticks (50000 milliseconds). It has been marked for termination.”, may be reported in the SAP ASE error log on a heavily used HADR setup, followed by the message "Current process infected with signal 11 (SIGSEGV)" in the module ‘ra__ci_destroy_stop_scanner’ together with a stack trace which includes the modules ‘ra__ci_destroy’ and ‘ra_ci_main_thread’ when a Rep Agent is shutdown. See KBA 2572498. |
| 811690 | Wrong results may be returned when a LIMIT/OFFSET clause is used in a DISTINCT view. |
| 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. |
| 811699 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace that includes the modules 'firstcmd_workno', 'firstroot_workno' and 'sqlscript_parse', may be reported in the SAP ASE error log when the RETURN statement is used with UNION/MINUS/EXCEPT in a procedure in an SQLScript database. See KBA 2560830. |
| 811701 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 's_handle' together with a stack trace which includes the modules 's_recompile' and 'execproc', may be reported in the SAP ASE error log when creating a Light Weight Procedure (LWP) after a 2812 error, "Stored procedure ' < name > ' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", is reported. See KBA 2471704. |
| 811702 | DBCC IMRS('print', 'threshold', < database name > , 'null') may lead to incorrect values of min, max and default for the different threshold fields. |
| 811703 | A 3701 error, "Cannot drop the table ' < table_nname > ', because it doesn't exist in the system catalogs" will be reported when the dbo user tries to drop a table type that was created by another user. |
| 811706 | In rare circumstances, a 803 error, "Unable to place buffer < buffer_num > from cache < cache name > holding logical page < page_num > in sdes for object 'sysversions' - either there is no room in sdes or buffer already in requested slot", may be reported when executing a SELECT query against an On-Disk MVCC database. |
| 811716 | A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be raised when a query that includes a UNION VIEW with LIMIT clause and without an OFFSET clause is executed. See KBA 2556253. |
| 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. |
| 811723 | In rare circumstances, the message, "JZ0R1: Result set is IDLE as you are not currently accessing a row." may be reported in the Webservices log file. See KBA 2559676 |
| 811725 | Improve process of object id assignments to temporary tables to avoid raising spurious errors relevant to temporary tables like 'object not found', 'column not found'. See KBA 2755790. |
| 811764 | A 644 error, "Index row entry for data row id < page#, row# > ) is missing from index page < value > of index id < value > of table < name > in database < name > . Xactid is < page#, row# > ). Drop and re-create the index." together with a stack trace that includes the modules 'bt_delete' and 'row_delete' may be reported in the SAP ASE error log on a non-clustered index when DELETE commands are executed and the housekeeper task is performing aggressive garbage collection concurrently. See KBA 2523141. |
| 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. |
| 811775 | If workload profiler is re-installed using installwlprofiler after capturing a workload, without doing a prior uninstall, then subsequent capture of workload using sp_wlprofiler 'monitor', may run into error 512, “Subquery returned more than 1 value. This is illegal when the subquery follows =, !=, < , < = , > , > =, or when the subquery is used as an expression”, followed by error 3621, “Command has been aborted”. This is due to stale statistics from the previous workload profiler installation. |
| 811784 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeCacheDMLOp::_LeOpAcquire' together with a stack trace that includes the modules 'LeEmittOp::_LeOpAcquire' and 'LePlanAcquire', will be reported in the SAP ASE error log if the user attempts to use a table UDF as a scalar UDF in a SELECT statement. See KBA 2938978. |
| 811787 | In an HADR environment where SAP ASE is configured for LDAP User authentication and the login mapping is set to 'create login', then internal login creation automatically initiated by SAP ASE during the login fails with error 3959 "New transaction cannot be started as Adaptive Server is in 'Inactive' HADR state. The command could not be completed." and the DSI for the master database goes down. |
| 811811 | 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 cursor update statement that references a temporary table is executed and the configuration option "optimize temp table resolution" is enabled. See KBA 2562119. |
| 811825 | Wrong results may be returned from a query that has complex OR clauses. See KBA 2563459 and SAP Note 2596598. |
| 811842 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'psort__dolscanpage' together with a stack trace that includes the modules 'psort__dolscanptn' and 'psort__dolscan', may be reported in the SAP ASE error log when REORG REBUILD with online option is executed on a round-robin partitioned DOL table with a global placement index. See KBA 2669610. |
| 811850 | A 11060 error, "This statement has exceeded the maximum number of recompilations (10). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported when executing nested views and procedures. See KBA 2462416. |
| 811856 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'open__byname' followed by a stack trace that includes the modules 'open_user_table', 'cm_which_cache' and 'q_setup_tab_cache_info', may be reported in the SAP ASE error log when selecting from a table variable with compatibility mode enabled. See KBA 2947012. |
| 811864 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'rvm_validate_proc' followed by a stack trace that includes the modules 'proccreate', 's_crtproc' and 's_cache_stmt', may be reported in the SAP ASE error log when upgrading a SAP ASE 15.7-based server to a 16.0 SP03 based version. See KBA 2649965. |
| 811882 | In rare circumstances, a 6189 error, "In-memory row storage RIDMAP check failed with < > error(s)." along with messages like "Number of maximum entries on RIDM_PAGE# < > is < > which is not between expected values < > and < > ." and "Check for Migrated rows in ridmap failed with errors printed above." may be reported when DBCC CHECKALLOC is run on an IMRS enabled database. |
| 811884 | A 2812 error, "Stored procedure can not be found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", and a 267 error, "Object not found", may be reported when creating a Global Temporary Table with a name of length 255. |
| 811885 | In rare circumstances, a 7989 error, "The serial allocation flag was found to be improperly set in allocation unit < > , at extent ID < > , with alloc map = < > and objid = 8. This flag has been cleared by DBCC.", may be reported when DBCC TABLEALLOC is run with 'full' or 'optimized' option while concurrent DMLs take place. See KBA 2574619. |
| 811913 | The message, "Assertion (((mass_ptr)- > bpage- > anp.pptnid == SYSIMRSLOGS) || (((SDES *)((void *)0)) && ((SDES *)((void *)0))- > sobjid == SYSIMRSLOGS) || (MASS_CHANGERS_ACTIVE_COUNT(mass_ptr) == 0))", together with a stack trace which includes the modules 'bufunpredirty' and 'alterdb' may be reported in the SAP ASE error log when ALTER DATABASE is run while the diagserver binary is in use. |
| 811919 | DISK RESIZE must accept a negative value to shrink the device and truncate the device file in order to release space to the OS. |
| 811929 | In rare circumstances a user process may hang with a status value of "PLC sleep" as shown in system table master..sysprocesses, when running DUMP TRAN WITH TRUNCATE_ONLY on a database which has the database option "trunc log on chkpt" enabled. |
| 811933 | Queries with GROUP BY involving large result sets using "group_hashing" strategy may underperform during execution. Trace flag 16800 when enabled will use a newly introduced hash algorithm for "group_hashing" strategy in order to alleviate the performance problem. See KBA 2676005. |
| 811935 | DBCC page() command is enhanced to print character encoding information. |
| 811943 | The message, "No memory for < bucketpool_name > bucket pool growth ( < value > bytes)", may be reported unexpectedly in the SAP ASE error log although memory is available in the memory global pool 'blockpool'. |
| 811954 | In a rare circumstance, a 603 error, "There are not enough system session descriptors available to run this query. Raise the value of the configuration parameter 'number of aux scan descriptors' or retry your query later.", followed by a 803 error, "Unable to place buffer < buffer > from cache < cache > holding logical page < page no. > in sdes for object < table name > - either there is no room in sdes or buffer already in requested slot", may be reported when a cursor declared against an On-disk MVCC table is opened. |
| 811965 | A 9209 error, "RepAgent( < dbid > ): Missing datarow in TEXT/IMAGE/UNITEXT insert log record. Transaction log may be corrupt. Please contact SAP Technical Support. (current marker = ( < page# > , < rowid > ))." may be reported in the SAP ASE error log when LOB data is replicated. See KBA 2567397. |
| 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'. |
| 811970 | In rare circumstances, a SQL query that is executed in parallel may hang in the module 'LePipeRWState::LePrwsRWVtuple' for the parent thread and the module 'LavaThreadDriverMain' for the worker threads participating in the query execution. See KBA 2567720. |
| 811982 | Auto-IMRS partition tuning may get enabled for On-Disk MVCC enabled database if database is created without providing ROW STORAGE cache but is added later. |
| 811995 | The defined length of a column may be incorrect when creating an in-lined UDF with a datatype mismatch between the return table and SELECT statement. |
| 812006 | Under rare circumstances, SSL connections to an SAP ASE running in process kernel mode may hang during network I/O. KBA 250956 |
| 812014 | On Solaris 5.11 and later versions, the message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the SAP ASE error log when sybmon is attaching to the server which is not using ISM (Intimate Shared Memory). See KBA 2670742. |
| 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. |
| 812054 | The message, "Page Verification Error: Adaptive Server accessed a row that has an illegal length of..." followed by a crash of the backup server emulator process with the message, "Emulator interprocess communication failed with error state = 14, error code=32, system message=Broken pipe.", may be reported in the Backup Server error log when DUMP DATABASE is run if a database dump is taken using a dump configuration that includes the option WITH VERIFY=FULL. See KBA 2595456. |
| 812073 | A 326 error, "ALTER TABLE ' < table-name > ' failed. The table is 0-way partitioned, and a 1-way parallel plan was generated due to lack of parallel resources. Increase the value of 'max parallel degree' and 'number of worker processes' to at least 0, and try again.", may be reported when CREATE INDEX is executed while the set option 'quoted_identifier' is enabled, the table name contains ']' character and the configuration option 'enable compatibility mode' is on. See KBA 2898002. |
| 812074 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace in the module 'ckpt_chores' or 'checkpoint', may be reported in the SAP ASE error log when DUMP TRANSACTION is executed. See KBA 2947042. |
| 812077 | For the column of type unitext, if the value is NULL, SELECT on this column or implicitly converting this column to text may return unexpected data. See KBA 2564601. |
| 812086 | In rare circumstances, a 3404 error, "Could not open controlling database < value > of controlling database in multi-db transaction.", may be reported when MOUNT DATABASE is executed on a database that is in load sequence and a multi-database transaction was involved earlier. See KBA 2656744. |
| 812120 | Under some circumstances, 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 be reported when using LOB Locators to access the LOB Cache. |
| 812138 | In rare circumstances, the message, "CACHED ROW CHECK FAIL: Expected cached row with row id = < value > , to have the same row length as in page store but found a mismatch.", may be reported followed by a 15916 error, "Text pointer value < value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < number > , in row < number > located on page < number > , partition ID < number > for object with ID < number > and references first text page < number > ", when running DBCC CHECKTABLE on an IMRS enabled table. Additionally a 7928 error, "Index < name > is not consistent; found < number > leaf rows but < number > data rows. Drop and recreate the index.", and a 2510 error, "Key mismatch between index page < number > , partition ID < number > ; at offset < value > ; and data page < number > (row ID < number > ), partition ID < number > . Drop and re-create index ID < number > of table < name > in database < name > .", may also be reported. |
| 812142 | DBCC PAGE command has been enhanced to print decompressed data. |
| 812156 | For Java applications, if there is a stored procedure with output parameters, and if the output parameters come before input parameters, there is a possibility of incorrect values being stored for integers. See KBA 2571900 |
| 812173 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mda_fill_and_send_monProcessWaits' together with a stack trace which includes the modules 'conn_hdlr' and 'kisignal' may be reported in the SAP ASE error log when the monProcessWaits MDA table is queried. See KBA 2591095. |
| 812204 | A 5702 error, "ASE is terminating this process" together with an access violation exception stack trace which includes the modules 'KiUserExceptionDispatcher' and 'RtlDecodePointer' may be reported in the SAP ASE error log when running installjava utility on Windows platform. |
| 812216 | If an SAP ASE engine hangs while a network listener is affinitied to it, the network listener will be respawned, but may not resume accepting connections as expected. |
| 812236 | In rare circumstances, the message, "STFreeAPool(0): package(0x < address > ) still in use", may be reported in the SAP ASE error log when the RepAgent scanner thread is still using a package while the native thread is attempting to release it when the stream between SAP ASE and SRS is down and the synchronous replication mode is enabled in an HADR setup. See KBA 2951829. |
| 812241 | The message, "Assertion (objsdes- > sstat2 & SS2_WKTAB_SHARED_DES" together with a stack trace which includes the modules 'LePlanRelease' and 'close_shared_worktables', may be reported in the SAP ASE error log if a query execution internally requires the creation of a shareable work table while the diagserver binary is in use. |
| 812242 | An On-Disk MVCC database dump can be loaded with success into an archive database mistakenly. This will cause the metadata of the archive database to be corrupted. |
| 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. |
| 812256 | In rare circumstances on a heavily-loaded multi-engine system, a 3914 error, "Illegal internal transaction status. This is an internal system error", may be reported in the SAP ASE error log when the configuration parameter 'number of open objects' is under configured whereby SAP ASE reuses a metadata descriptor whose object had statistics information to flush on disk first. See KBA 2575197. |
| 812266 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrs_odmvcc_pack_row', together with a stack trace which includes the modules 'imrs_odmvcc_pack_au' and 'imrs__packthd_work' may be reported in the SAP ASE error log when using On-Disk MVCC tables. |
| 812268 | The Workload Profiler will report information in the new columns MaxInsRowsInXact, MaxDelRowsInXact and MaxUpdRowsInXact of the MDA table master..monOpenObjectActivity respectively for the maximum number of inserts, deletes and updates that were executed on a user table under any transaction. |
| 812269 | The MDA table, monRepStreamStatistics, may report inaccurate values for buffer pool package related monitoring in columns TotalPopulatePkgTime, TotalWaitToSendTime and TotalSendTime when stream mode replication is enabled. |
| 812273 | An infected with signal 11 (SIGSEGV) error followed by a stack trace that includes the modules 'smd_sample_server' and 'sm_exec_command' may be reported in the SAP ASE error log when executing the sybmon "sample" command when "allocate max shared memory" is set as DEFAULT (0). |
| 812300 | The IMRS data cache high watermark stored in the header of a transaction dump is empty mistakenly. The will result in LOAD TRANSACTION not checking whether the target cache is big enough and it may eventually run out of memory when reapplying the IMRSLOG transactions. |
| 812304 | Spurious errors may occur when trying to create a Global Temporary Table. |
| 812308 | Under certain circumstances, the message, "Assertion (lk_sufficient_tablk(sdes, SH_INT)) failed" followed by a stack trace that includes the modules 'fglock_verify' and 'dol_qualrow', may be reported in the SAP ASE error log when INSERTs, UPDATEs or DELETEs are executed on an object whose metadata has previously been bound using DBCC TUNE(bind_des, < dbid > , < objname > ) while the diagserver binary is in use. |
| 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. CR 805165 can be enabled using the run time trace flag 11013. See KBA 2593724. |
| 812311 | Increasing the configuration option 'user log cache' will significantly increase the SAP ASE memory consumption unexpectedly. See KBA 2570113. |
| 812323 | The message, "SYBMULTBUF ERROR: Volume validation error: attempt to flush < file_name > ”, will be reported in the SAP Backup Server error log on Windows platform when DUMP database or DUMP transaction is executed and the ASE configuration option 'enable buffered io for load' is enabled. See KBA 2947051. |
| 812328 | In rare circumstances, a 12311 error, "Internal error: address lock request on page < page number > of index id < index id > of table < table name > (id = < object id > ) in database < database name > failed with status < value > . No need to drop the index.", may be reported when running INSERT, UPDATE, or IMRS PACK operations and the transaction rollback. See KBA 2577215. |
| 812339 | A 3606 error, "Arithmetic overflow occurred.", may be reported while executing sp_helpdb on a database having a log device greater than 1TB. |
| 812347 | DDLGen fails to get the expected cache size |
| 812352 | A 18236 error, "Error updating the audit flags. This is a system error. Contact a user with System Security Officer (SSO) Role", may be reported when executing sp_audit to turn on any global audit option with the compatibility mode enabled. |
| 812354 | The execution of a DUMP or LOAD command will hang in the module 'login_response' when it is run from the threshold action procedure and the option 'net password encryption' is enabled in the SYB_BACKUP backup server. |
| 812355 | The sybmon sqltext and planprint commands are enhanced to print the query text in the specified OHEADER address and to print only the Lava plan for the specified E_STMT address. See KBA 2890263. |
| 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. KBA 2892312 |
| 812375 | The message, "Assertion (dol__can_clear_PUNCbit(sdes, &lkreport))" together with a stack trace which includes the modules 'bt__markdeleted' and 'bt__undo_leafinsdel', may be reported in the SAP ASE error log when rolling back an INSERT and the row is marked as committed unexpectedly while the diagserver binary is in use. |
| 812381 | A 16053 error, "The command 'DISK REINIT' with property 'IMRSLOG' is currently not supported in SAP Adaptive Server Enterprise Edition.", may be reported in the SAP ASE error log when mounting an IMRSLOG enabled database. |
| 812390 | In rare circumstances, message 725, " < COMMAND > : failed to allocate 96 bytes from Adaptive Server's main memory pool.", may be reported for some statement when the Global Fragment Pool size is under configured. Commands and transactions that access IMRS tables may also fail after this error message is reported. |
| 812391 | The message, "Assertion (sdes- > sstat & SS_NODATA || !RID_ISZERO(&odmvcc_mig_rid))" together with a stack trace which includes the modules 'imrs_getrow' and 'imrs_get_snapshot_version', may be reported in the SAP ASE error log when a DML is run while the diagserver binary is in use. Alternatively, the message, "Assertion (++entered_once == 1)" together with a stack trace which includes the modules 'imrs_gcthd_work' and 'imrs__gc_row_version', may be also reported. |
| 812392 | In rare circumstances, the message, "Current process infected with signal 6" in the module 'gsignal' together with a stack trace which includes the modules 'dcl_find_interface' and 'dcl_property' may be reported in the SAP ASE error log when the SAP ASE server is gracefully shut down and a site handler is configured. See KBA 2935019. |
| 812393 | An erroneous message, "Assertion (upd_ok) failed" in the module 'altdb__check_fwd_rows', may be reported in the SAP ASE error log if DBCC DBREPAIR with 'redo_shrink' option is executed to repair a partially completed shrink database and the diagserver binary is in use. It is a false assertion message from the diagserver, data is NOT corrupted. NO symptoms are reported in dataserver. |
| 812411 | A couple of typos have been corrected in the exception messages for "an unforeseen exception" and "an array bounds exceeded". |
| 812416 | A 632 error, "Attempt to move memory with an incorrect length of 51152. Maximum allowed length is 16384.", may be reported when updating the size of a large Non Volatile Cache (~100GB) using the sp_nvcacheconfig stored procedure. See KBA 2935133. |
| 812418 | On Windows platforms, setuphadr may fail to create route when SSL is enabled. |
| 812420 | The message, "Assertion (ra_ci_stream)" together with a stack trace which includes the modules 'ra__ci_syslogs_scanner_destroy' and 'ra__ci_sleep_on_detached_stream' may be reported in the SAP ASE error log if the RepAgent is shutdown and streaming replication is enabled while the diagserver binary is in use. Alternatively, the message, "Assertion ((xlr- > loh.loh_op == XREC_DELETE) || (xlr- > loh.loh_op == XREC_IDELETE) || (xlr- > loh.loh_op == XREC_DOL_DELETE))" together with a stack trace which includes the modules 'ra__ci_syslogs_scanner_scan' and 'ra__save_befimg' may be also reported. |
| 812430 | When View UDFs and Table UDFs are mixed in the same batch or stored procedure, wrong results for Table UDFs may occur due to incorrect parameter handling. |
| 812443 | If trace flag 766 is turned on, occasionally "ELC_VALIDATION_ERROR: Page < address > is not allocated in procedure cache. pelc = < address > , chunksize = < chunk size > , engine id = < engine id > , validate_flag = < 0/1/2 > " or ELC_VALIDATION_ERROR: Page not marked free. pelc = < address > , chunksize = < chunk size > engine id = < engine id > , validate_flag = < 0/1/2 > ." may be falsely reported in the SAP ASE error log during heavy workload or when SAP Adaptive Server flushes an Engine Local Cache (ELC) memory to its global memory pool. See KBA 2581174. |
| 812460 | SAP ASE using external security services such as Kerberos can suffer from unbalanced engine load with an excess of runnable tasks waiting for engine 0. See KBA 2700728. |
| 812461 | In rare circumstances in a Distributed Transaction(DTM) environment, when the coordinating server is being rebooted after the crash, the messages, "Running spid is < SPID of current PSS > , spid from the pss in the sdes is < SPID of PSS cached in sdes > " and "Running kpid is < KPID of current PSS > , kpid from the pss in the sdes is < KPID of PSS cached in SDES > ", together with a stack trace, which includes the modules 'pss_from_sdes' and 'closetable', may be reported in the errorlog of a participant server for an On Disk MVCC enabled database, when the diagserver binary is used. |
| 812472 | A 11060 error, "This statement has exceeded the maximum number of recompilations ( < value > ). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported when executing another user's stored procedure. |
| 812476 | The CREATE TABLE and ALTER TABLE commands have been extended to provide new options to warm the IMRS Cache. New syntax extensions now allow all rows accessed by a query to be cached or the maximum number of rows that can be cached by a query to be specified. |
| 812477 | Under rare circumstances, SAP ASE may appear to hang during an UPDATE STATISTICS or another commands that runs at a lower priority. See KBA 2581507. |
| 812494 | When performing an unplanned failover in an HADR system with stream replication enabled, Rep Agent may shutdown with a 9219 error, "RepAgent : Internal coding error". See KBA 2935625. |
| 812496 | A 8015 error, "Adaptive Server has truncated parameter number 3 passed to rpc 'as_db_dam' on server < server_name > . The remote server does not support character or binary data wider than 255 bytes.", may be reported when DUMP DATABASE is executed in server passthrough mode and the database option 'allow incremental dumps' is enabled. |
| 812497 | In rare circumstances, a 12324 error, "In database ' < name > ', the server failed to open required table ' < id > '. Please contact SAP Technical Support.", may be reported in the SAP ASE error log when the system stored procedure sp_reptostandby with the option 'NONE' is executed while a concurrent session is dropping the table reported in the error message. Instead, a 11305 error, "Failed to open the object ' < id > ' in database ' < name > ' while executing the built-in function setdbrepstat(). Check if the object exists and retry the operation.", will be reported. See KBA 2935651. |
| 812517 | Sometimes the SAP ASE error log may get filled up with warning messages like "WARNING: Memory protection change failed: Invalid argument, address" when trace flag 767 is enabled. See KBA 2935642. |
| 812519 | The system stored procedure, sp_logiosize, is enhanced to support large buffer pool I/O usage for sysimrslogs system table in IMRS-enabled databases. |
| 812532 | In rare circumstances, a 11060 error, "This statement has exceeded the maximum number of recompilations (10).", may be reported when Dynamic SQL queries are executed from Java or Python clients. See KBA 2845818. |
| 812551 | A 154 error, "LIMIT clause is not allowed in UNION.", will be reported when applying the LIMIT clause in a UNION query. |
| 812566 | 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 first page of the IMRSLOG is not initialized and the first transaction is not flushed in the IMRSLOG. See KBA 2951873. |
| 812584 | In rare circumstances on a heavily-loaded multi-engine SAP ASE system, the execution of UPDATE INDEX operator as shown by sp_showplan may hang and result in a 1105 error, "Can't allocate space for object < objname > in database < dbname > because < segname > segment is full/has no free extents", reported. |
| 812588 | In rare circumstances, the REP AGENT task cannot be stopped when stream replication is enabled. The modules 'upyield', 'ra_ci_main_thread' and 'ra__ci_destroy_stop_scanner' will be reported for the hanging task when dbcc stacktrace( < spid > ) is run. |
| 812591 | In rare circumstances, the execution of DUMP DATABASE or 'sp_dropserver SYB_BACKUP' may hang when SSL is enabled on Windows or AIX platform, respectively in the modules 'sb_getsite' or 'sb_disconnect’. See KBA 2758199. |
| 812620 | Under rare circumstances, the DUMP TRANSACTION command may hang for SSL enabled connections. See KBA 2758273. |
| 812633 | A 102 error, "Incorrect syntax near 'passwd'" may be reported when DUMP TRANSACTION or LOAD TRANSACTION is executed with the PASSWD option. |
| 812646 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'tdsrecv_fetch' together with a stack trace which includes the modules 'conn_hdlr' and 'kisignal', may be reported in the SAP ASE error log when missing cursor and dynamic statements are replayed by Workload Capture. See KBA 2585531. |
| 812661 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'cfg__altercacheconfig' together with a stack trace which includes the modules 'cfg_main' and 's_execute', may be reported in the SAP ASE error log when the built-in, config_admin(), is executed. See KBA 2750586. |
| 812678 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra_malloc_mempool' and 'ra_mempool_alloc_internal' may be reported in the SAP ASE error log when the Rep Agent STP Manager Thread terminates abnormally leading to corruption in the Rep Agent Memory Pool. See KBA 2722607. |
| 812687 | The sp_sysmon report is completed with a new entry in the section "Transaction Management", for the "ULC Flushes to Xact Log": "by IMRSLOG Replication". It indicates when the ULC was flushed while writing a book-keeping log record in SYSLOGS for a replicated transaction in SYSIMRSLOGS. |
| 812690 | sp_sysmon reports rows inserted for Fully Logged APL Heap Table from non-logged inserts such as worktables and materialized tables like sysprocesses and sysmonitors. See KBA 2586495. |
| 812704 | A new optimizer criteria 'numeric_alt' has been added to improve the performance of queries having large number of SUM aggregates run on SAP ASE in a Business Warehouse environment. See KBA 2885872. |
| 812721 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace which includes the modules 'ex_logprint' and 'ra_CIStreamMessageCallback', may be reported in the SAP ASE error log when synchronous mode replication is enabled. |
| 812734 | A 156 error, "Incorrect syntax near the keyword 'sql_error_code'", will be reported when 'sql_error_code' is used as an identifier. See KBA 2695927. |
| 812741 | The message, "Assertion (XACT_CHECK_STATE(pack_ctx- > pctx_xprm.xdes, XACT_IN_CMD))” together with a stack trace which includes the modules 'imslog__movetruncpt_break_xact' and 'd__imrs_log_trunc' may be reported in the SAP ASE error log when the IMRSLOG is being truncated while the diagserver binary is in use. |
| 812750 | The error, "SYBMULTBUF ERROR: Error in acknowledging command '166' to the archive emulator, System error=etc." may be reported in the SAP Backup Server error log at LOAD time when some of the database devices is using buffered I/O. On Windows platforms, the error, "SYBMULTBUF ERROR: Volume validation error: attempt to flush ' < filename > ' returned 5.", may be reported in the SAP Backup Server error log at DUMP time. These are warning messages that can be ignored. See KBA 2595504. |
| 812823 | On heavily loaded systems, spinlock contention may be observed on statement cache when multiple UPDATE statements with similar data of numeric datatype are present. Use the run time trace flag 11013 to enable the use of a single cached plan for multiple UPDATE statements. See KBA 2590282. |
| 812840 | A 15916 error, "Text pointer value < text pointer value > references a data page with an invalid timestamp. This value is for TEXT/IMAGE column < column id > in row < row id > located on page < page number > partition ID < partition id > for object with ID < object id > and references first text page < first text page number > ", may be reported when executing DBCC CHECKTABLE after REORG REBUILD ONLINE is run with concurrent DMLs, when compression is enabled. |
| 812852 | The value of parameters for some datatypes such as BINARY and VARBINARY in dynamic SQL may not be printed out in the output of "sp_showplan 'long'", "select query_text( < spid > )" or the deadlock SQL text. |
| 812875 | The 9239 error message, "RepAgent( < database-ID > ): Cannot allocate < number > bytes of memory and will sleep until memory becomes available. Rep Agent Thread: < value > , status: < value > / < value > . Contact a user with System Administrator (SA) role to reconfigure Adaptive Server with more memory for Replication.", is enhanced with details which can help in analyzing the reason for memory shortage of the Rep Agent Memory Pool. See KBA 2872312. |
| 812892 | A 12406 error, "Failed to find the last row marker for transaction ( < page# > , < rowed > ) in sysimrslogs for database ' < dbname > ' ( < dbid > ). The sysimrslogs row is corrupted." in the module 'imrslogrec_fix_lastlog' together with a stack trace which includes the modules 'boot__recover_and_online' and 'imrslogrec_logbounds', may be reported in the SAP ASE error log during ASE startup while recovering an IMRS enabled database. See KBA 2695955. |
| 812945 | In an SAP ASE HADR environment, if all the five parameters, namely the location of the database, configuration files, translog, log and backup directories, for configuring Replication Server and RMA are not provided in the resource file, the RMA will not start leading to failure during execution of setuphadr. |
| 812950 | After upgrading from a pre-16.0 SP03 server to a 16.0 SP03 based server, if SSL is configured and the SSL listener is specified in interfaces file, then the server certificate may not be decoded correctly by the server if the certificate file has the private key before the certificates. This may lead to the upgraded server failing to start up. |
| 812953 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < dbname > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), ...", together with a stack trace which includes the modules 'xsc__sysimrslogs_getnext' and 'apf_imrslog_allocunit' may be reported in the SAP ASE error log when DBCC LOG is run for an IMRS enabled database. See KBA 2877198. |
| 812955 | Even after the successful application of the fact_table hint, optimizer constructed the final plan using the subplan generated for compatibility mode. See KBA 2748346. |
| 812974 | New interface to allow packing rows out of IMRS using the sp_imrs system stored procedure. The syntax is sp_imrs 'pack_rows', ['aus', ' < number_of_Allocation_Units_to_pack > ' | 'pct', ' < percentage_of_Allocation_Units_to_pack > ']. |
| 812977 | Under rare circumstances, decoded function names in the SAP ASE stack traces may not be correct on Linux platform. See KBA 2698064. |
| 812978 | syslogshold may occasionally show a row with a transaction start date of 1 Jan 1900. See KBA 2587185. |
| 813005 | In rare circumstances on an HADR setup, a 156 error, "Incorrect syntax near the keyword ' < value > '", may be reported in the standby SAP ASE error log during the replication of CREATE VIEW, resulting in the DSI replication stream to implicitly stop. See KBA 2732864. |
| 813014 | Once a scalar-valued SQL UDF is referenced in a query, or in the text of a DDL command, any attempt to drop or replace the SQL UDF will result in error 3702, stating that the SQL function cannot be dropped or replaced because it is currently in use. See KBA 2553759 |
| 813037 | During a graceful shutdown of SAP ASE in threaded mode, the errorlog indicates a new configuration file is written even if there are no configuration changes done. See KBA 2594978. |
| 813075 | In rare circumstances, 2601 error, "Attempt to insert duplicate key row in object < table_name > with unique index < index name > ", may be reported on the standby SAP ASE server, when running an UPDATE command on a compressed APL table that has a primary key constraint on the primary SAP ASE server. See KBA 2608496. |
| 813096 | In rare circumstances, DUMP and LOAD operations may not succeed when using an SSL connection between SAP ASE and the SAP ASE backup server on the Windows and AIX platforms. |
| 813102 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page. Rid pageid = < value > ; row num = < value > . Page pointer = < value > , pageno = < value > , status = < value > , ptnid = < value > , indexid = < value > , level = < value > , pnextrno = < value > ", may be reported in the SAP ASE error log when an IMRS enabled database is replicated and there is very high activity on the database. See KBA 2871752. |
| 813108 | In case a workload involves tables created by multiple logins, workload profiler is unable to archive tables other than those created by login dbo. |
| 813109 | A network connection using SSL may hang during login and ASE may get CPU bound. |
| 813110 | A table with compressed LOB columns uses more space when populating the table via VIEWs. See KBA 2594175. |
| 813112 | In rare circumstances, a 9219 error, "RepAgent( < dbid > ): Internal coding error." or a 9254 error, "RepAgent( < dbid > ): Could not locate schema version for object id ' < objid > ' in the transaction log.", followed by a 9204 error, "RepAgent( < dbid > ): Could not locate schema for object with id = ( < objid > ), current marker ( < pageno > , < rowno > )" may be reported in SAP ASE error log when RepAgent is configured for stream replication and a replicated table schema is changed. See KBA 2845172. |
| 813114 | Sybmon "status" and "engines" commands report the wrong engine status as "Not Halted" for memory dump generated by either "DBCC MEMDUMP" command or manual command "memdump" with engine halt option. See KBA 2596784. |
| 813118 | The message, "ubo_object_from_slot: Pss Invalid slot id 0", along with the message, "Current process infected with 11 (SIGSEGV)" in the module 'lock__print_deadlockchain' together with a stack trace which includes the modules 'lock__perform_deadlock_search' and 'lock_firstpage' may be reported in the SAP ASE error log when the configuration options "print deadlock information" and "deadlock pipe active" are enabled, while SAP ASE is processing a deadlock scenario between user tasks during the execution of a query. See KBA 2599942. |
| 813129 | When Rep Agent is configured for stream replication and a retryable error occurs after the execution of a DDL command altering the schema of a table, Rep Agent may fail to process again the log records requiring the old schema of the table. As the wrong schema is sent to SRS, the DSI may shut down with an error from SAP ASE such as a 207 error, "Invalid column name ' < column_name > '". |
| 813140 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memalloc' together with a stack trace which includes the modules 's_cpparamd' and 'vu_res_view', may be reported in the SAP ASE error log when executing multiple SELECTs on deeply nested VUDFs in a batch. See KBA 2847722. |
| 813142 | A 208 error, "# < table_name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).", will be reported after a cursor is opened and a SELECT query references a temporary table in the same batch. |
| 813224 | An incorrect value like '# < value > ' may be seen in the 'Memory Used' column of the < sp_configure ‘max memory’ > output when the 'max memory' parameter is set to a value greater than or equal to 2048 GB. See KBA 2748384. |
| 813236 | A 692 error, "Uninitialized logical page < value > was read while accessing < information > . Please contact SAP Technical Support", may be reported when executing DUMP TRAN WITH NO_LOG on a database that is marked as read-only. |
| 813238 | The message, "Attempt to push affinity to a non-existent engine", may be reported in the SAP ASE errorlog when performing a DISK UNMIRROR command to set the secondary mirror as the primary device while running in process mode. See KBA 2597350. |
| 813244 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < dbname > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), ..." may be reported in the SAP ASE error log when DUMP DATABASE is run for an IMRS enabled database on which the IMRSLOG segment was first removed and then re-inserted using ALTER DATABASE command. |
| 813248 | Executing sp_displaylogin with a wildcard may show different information of "Password expiration interval", "Minimum password length" and "Maximum failed logins" from information displayed individually after you change the attributes of one of the login accounts. See KBA 2598951. |
| 813259 | The system stored procedure, sp_helpdb, will not report IMRSLOG devices used by a database if they don't have the direct I/O option enabled. |
| 813266 | New statements are not cached after a 701 error, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", is reported resulting in a performance loss and high engine utilization. See KBA 2600140. |
| 813268 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'text_tabcheck' together with a stack trace which includes the modules 'dol__imrs_datarows_check' and 'checktable' may be reported in the SAP ASE error log when DBCC CHECKTABLE is run on a table that is DRC or IMRS MVCC enabled. See KBA 2858441. |
| 813283 | SAP ASE workload capture may record incomplete pcap file names in the SAP ASE error log especially when the server is configured with multiple engines. |
| 813292 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'OmniQuickPass::locateSubquery' followed by a stack trace that includes the modules 'OmniQuickPass::locateOjRange' and 'OmniQuickPass::handleOJBlock', may be reported in the SAP ASE error log when a query that involves ANSI OUTER JOIN and subqueries is executed against a proxy table. See KBA 2600457. |
| 813303 | In an HADR environment, when a Primary SAP ASE is rebooted, it may switch to Standby mode with error 208, "sysservers not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", followed by error 11221, "No external login for suserid 0, server name ' < value > '", reported in the SAP ASE error log. See KBA 2871744. |
| 813315 | When dropping a SQLScript database, a 3906 error, "Attempt to BEGIN TRANSACTION in database < dbname > failed because database is READ ONLY", may be reported against another database < dbname > that is not the SQLScript database being dropped. |
| 813326 | A 249 error, "Syntax error during explicit conversion of VARCHAR value '# < value > ' to a INT field", will be reported when executing sp_shmdumpconfig. See KBA 2623861. |
| 813337 | A 6601 error, "You cannot execute a query involving access from T-SQL database and SQLScript database at the same time", will be reported when sp_downgrade_esd is run against a SQLScript database. |
| 813348 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < dbname > ' because the requested RID has a higher number than the last RID on the page", may be reported in the SAP ASE error log during the reconciliation-redo phase of IMRSLOG recovery, if at the end of the reconciliation-redo phase, the old and new last page of the log happen to be on different fragments. See KBA 2871707. |
| 813359 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'OmniQuickPass::expandRangetableName' together with a stack trace that includes the module 'generateTransSQL', may be reported in the SAP ASE error log when the set option 'show_transformed_sql' is enabled. See KBA 2600457. |
| 813401 | Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled. |
| 813451 | sp_configure 'Non-Volatile Caches' incorrectly shows "User Defined NV Cache" and "NV Cache Threshold" as configurable options. See KBA 2604896. |
| 813470 | Executing ALTER TABLE to change the locking scheme to ALL PAGES or DATA PAGES for an IMRS enabled table will succeed if the same ALTER TABLE command also contains add/modify/drop column command. |
| 813473 | In rare circumstances on a heavily-loaded multi-engine Solaris x64 system, SAP Adaptive Server may hang in the module 'xls_flush_plcqueue' when the configuration option "user log cache queue size" is enabled while the Private Log Cache of a user task is being flushed in the transaction log. See KBA 2594508. |
| 813501 | In very rare circumstances, if CREATE INDEX and at least two updates are run in a same batch, then concurrent updates, affecting the same set of rows, qualified by the second update onwards, might succeed wrongly. |
| 813510 | Sybdumptran utility allows a database or transaction dump that was taken with the Backup Server archive API to be used as metadata file. |
| 813511 | In rare circumstances, a 3401 error, "Rec_logbounds: getnext SCAN_RID of last checkpoint failed on Rid from sysdatabases. Rid pageid = < page# > ; row num = < row# > .", may be reported in the SAP ASE error log during boot time recovery resulting in the database not being recovered or Adaprive Server may not start if the error occurs for the master database. See KBA 2845080. |
| 813514 | When a cursor at snapshot isolation is opened on On Disk MVCC enabled tables, and 20 or more such tables are involved in the cursor, any command executed from the same session post open cursor may hang forever. |
| 813520 | In rare circumstances, a 12309 error, "Expanding update on object < name > in database < name > cannot succeed on page < number > , because the contiguous_free_bytes of < value > is less than the difference of < value > between new rowlen and old rowlen. This is an internal error. ASE is terminating this process.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'dol__expand'/'dol__delete_insert' and 'dol_update' while performing an expanding UPDATE on a table that is stored in an On-Disk MVCC enabled database. See KBA 2856720. |
| 813523 | The message, "timeslice < value > , current process infected at < value > " in the module 'pthread_cond_wait' together with a stack trace which includes the modules 'np_io_read' and 'ct_results', may be reported in the SAP ASE error log when the Rep Agent is shutdown while the Replication Server is not reachable and the synchronous stream replication is enabled in an HADR setup. See KBA 2807757 |
| 813529 | Handling of default values for global temporary tables is not correct. See KBA 2608519. |
| 813535 | On heavily loaded systems, spinlock contention may be observed on statement cache when multiple INSERT statements with similar data of numeric datatype are present. Use the run time trace flag 11013 to enable the use of a single cached plan for multiple INSERT statements. |
| 813536 | A 267 error, "Object < name > cannot be found" in the module 'open_globaltt', may be reported in the SAP ASE error log when running ONLINE DATABASE after having loaded a database dump. See KBA 2607240. |
| 813547 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322. |
| 813551 | In rare circumstances, the message, "Assertion(!sdes || sdes- > saccerrcode == ACCERR_UPDATE_OK) failed" may be reported in the SAP ASE error log while PACK operation is in progress and the diagserver binary is in use. |
| 813573 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'pss__release' together with a stack trace which includes the modules 'quitfn_indirect' and 'pss_unkeep' may be reported in the SAP ASE error log when a task disconnects after executing some queries that involve INDEX scans on MVCC enabled tables. See KBA 2787481. |
| 813574 | When upgrading from a pre-16.0 SP03 server to a 16.0 SP03 based server, the auditing process may terminate with a 716 error, "Unable to allocate memory of size < num > bytes from the 'default' pool'", reported in the SAP ASE error log when the 'auditing' option is disabled. See KBA 2609783 |
| 813580 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'omni_ct_cancel' or 'uctSetIssuedCnt' or 'ct_poll' together with a stack trace which includes the module 'omni_ct_cancel' or 'omni_ct_close' may be reported in the SAP ASE error log when the SAP ASE configuration parameter 'cis idle connection timeout' is turned on. See KBA 2697042. |
| 813639 | During the execution of a SAP BW SQL query with a fact table hint, in some cases the SAP ASE optimizer may chose a non-performant join order when the fact table hint fails and the alternative greedy search option is enabled, despite an appropriate join order being present in the query. Use the runtime trace flag 11836 or the optimization criteria forceplan_alternative_greedy to enable the current fix. See KBA 2755228. |
| 813662 | The message, "Current process infected with signal 8 (SIGFPE)" in the module 'imrs_get_pdes_imrs' together with a stack trace which includes the modules 'altertab' and 'alt__set_option' may be reported in the SAP ASE error log when 'ALTER TABLE < name > SET ROW_CACHING ON' is run in an IMRS enabled database after LOAD DATABASE was run. See KBA 2835052. |
| 813672 | The message, "Sybmon encountered signal 11 at address elf_offset_to_name", together with a stack trace which includes the modules 'os_getsyms' and 'pcdescformat' may be reported when running the sample command on the Solaris x64 platform. |
| 813684 | XPserver may fail to start with failure to load dependent libraries if the path to the SYBASE directory is longer than about 60 characters and JVM services are in use |
| 813689 | In a HADR environment, under rare circumstances, a planned failover issued using RMA command sap_failover may fail and the message, "split brain check refused to allow this server to become Primary", may be reported in the SAP ASE error log. See KBA 2879537. |
| 813691 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'rep_cfg_valid_context' may be reported in the SAP ASE error log when executing the system stored procedure sp_config_rep_agent and the version of installmaster is more recent than the one of the dataserver binary. See KBA 2879574. |
| 813694 | On Windows platform, a 12055 error, "System call stati64 failed with error 3", will be reported when executing a query on the monDeviceSpaceUsage table when there is a SAP ASE device created on a Windows mounted path. See KBA 2611275. |
| 813718 | When a non DBA user with proper privileges runs a homogenous batch update using a Java client, the errors, "JZ0BE: BatchUpdateException: Error occurred while executing batch statement: The dynamic statement '*sh1497365668_1600677172ss*' could not be found. This may be due to insufficient metadata descriptors. Increase the serverwide 'number of open objects' parameter or the 'procedure cache size' parameter" and "JZ0BE: BatchUpdateException: Error occurred while executing batch statement: A query plan cannot be generated for DML command executed with homogeneous batch parameters. The batch was aborted", may be reported at the Java client. See KBA 2611208. |
| 813720 | In rare circumstances, the background process IMRS_PACK may hang indefinitely for an IMRS enabled database while searching for rows to pack in the IMRS ILM queue. |
| 813721 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrsm__alloc_metadata' together with a stack trace which includes the modules 'imrs__recover_insert' and 'imrslogrec_redo_log', may be reported in the SAP ASE error log when boot time recovery on an IMRS enabled database is taking place. See KBA 2787473. |
| 813752 | Diagnostic tracing for "SSL handshake failed" errors has been added. The diagnostic tracing can be enabled through traceflag 7867. See KBA 2633020. |
| 813810 | In rare circumstances on a heavily-loaded system, SAP ASE may omit to recover IMRS committed transactions during the crash recovery of an IMRS enabled database when the configuration option ‘recovery interval in minutes’ is set to a small value and DUMP DATABASE or DUMP TRANSACTION commands are frequently executed. |
| 813815 | Under an HADR setup when stream replication is enabled, a 9405 error, "RepAgent( < dbid > ): Internal Error. The total number of columns in raobj ( < number > ) does not match the number of elements in RA_COLS list ( < number > ).", may be reported in the SAP ASE error log. This error occurs when the metadata can't fit in the current package and Rep Agent has to flush it prior to sending the metadata. The error doesn't impact replication and can be ignored. See KBA 2630044. |
| 813847 | Multiple threshold actions may be executed unwantedly to extend a database through a threshold action if the database is blocked due to long duration of a concurrent DUMP DATABASE execution. See KBA 2614731. |
| 813849 | The SAP ASE backup server process in AIX, SOLARIS and HP-UX platforms may leak some memory when dumping and loading databases, which causes it to grow until it exceeds the O/S memory limit. The backup server may then hang or crash with a core dump with the message, "Backup Server: 1.1.2.8: Memory allocation failed in bs_mkvdisktab for a sd_vector allocation. This DUMP or LOAD session must exit.", reported in the error log. See KBA 2605477. |
| 813852 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'index_compress_page_with_prefix' together with a stack trace which includes the modules 'redo_bt_rebldleafs' and 'recovery' may be reported in the SAP ASE error log during the recovery of a transaction log dump which contains index compressed operations. See KBA 2614971. |
| 813853 | A 6931 error, "The table 'sysimrslogs' with ID 59 in database < name > is corrupt. Page < value1 > is linked to page < value2 > that either is out of the database boundary or belongs to an invalid fragment.", together with a stack trace that includes the module 'imrslog_validate_nextpg' may be reported in the SAP ASE error log after loading an IMRS database dump into an IMRS database with a bigger IMRSLOG size. See KBA 2857309. |
| 813870 | Cached query plans may not be recompiled even when the total rowcount on the tables involved in the cached plans changes by more than the value configured by the ‘recompile_factor’ attribute. |
| 813886 | Under rare circumstances, a connection may hang after receiving a cancel request from the client. See KBA 2633664. |
| 813895 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'imrs_abort_to_imrv' together with a stack trace which includes the modules 'xact_rollback' and 'le_runerr', may be reported in the SAP ASE error log when a DML on an On-Disk-MVCC enabled table is rolled back after a 728 error, "Allocation of size < value > bytes from the row storage cache, ' < name > ', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < value > ", is encountered. See KBA 2857906. |
| 813896 | sp_imrs show, tables does not show any information when executed on an On-Disk MVCC enabled database. |
| 813897 | A 18118 error, "Object 'sysimrslogs' does not exist in this database" will be reported when executing sp_imrs show, "all metrics", < imrs_cache name > on an On Disk MVCC enabled database. |
| 813898 | A 2714 message, "There is already an object named '##...' in the database.", may be reported in the SAP ASE error log when an attempt is made to create an inlined table-valued UDF that references a Global Temporary Table that has yet to be materialized. See KBA 2657804. |
| 813917 | The shared objects libjpeg.so and liblcms.so (JPEG.DLL/JPEG.PDB and LCMS.DLL/LCMS.PDB on Windows) have been added to ${SYBASE}/shared/ase/jvm.wl (%SYBASE%\Shared\ase\jvm.wl on Windows) JVM allow-list[*] file. |
| 813940 | CHAINED MODE fails to start a transaction for commands that don't access a table. See KBA 2952649. |
| 813968 | In rare circumstances, the message, "Assertion (latch_free_btree && !lfb_skip_leaf) failed", may be reported in the SAP ASE error log while boot time recovery of a database is in progress and the diagserver binary is in use. |
| 813971 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'apl__startscan' together with a stack trace which includes the modules 'xsc__sysimrslogs_setscan' and 'db_high_ts_on_logpg', may be reported in the SAP ASE error log while recovering a database that is Data Row Cache enabled. See KBA 2872228. |
| 813983 | A 515 error, "Attempt to insert NULL value into column 'seqnum', table '#result_body'; column does not allow nulls", may be reported if sp_helpartition is executed, after executing ALTER TABLE DROP COLUMN WITH NO DATACOPY followed by ALTER TABLE MOVE PARTITION. |
| 813994 | In some circumstances, the message, "Rep Agent detected error 406 with message 'CI API call DropLastMetaObj() failed' at line 9670 in file ra_ci_cmd.c." and the message "RepAgent( < dbid > ): Warning: The size of the stream buffer is too small ( < value1 > bytes). Use sp_config_rep_agent ' < dbname > ', 'stream buffer size', ' < value2 > ' to increase it.", may be reported in the SAP ASE error log when streaming replication in synchronous mode is enabled. See KBA 2618490. |
| 813997 | In an HADR environment with a DR node configured, under rare circumstances unplanned failover may fail and the message "Failed to change the configuration option 'HADR mode' to 1." may be seen in the log of the to-be-made primary SAP ASE. See KBA 2887256. |
| 813998 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qualpage' followed by a stack trace that includes the modules 'apl__startscan' and 'startptnscan', may be reported in the SAP ASE error log when a JDBC client executes queries with property DYNAMIC_PREPARE set to true and the parameters "abstract plan load" and "enable literal autoparam" are enabled in SAP ASE. See KBA 2617753. |
| 814003 | A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after dropping an user database which is marked suspect and is On-Disk MVCC enabled. |
| 814029 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'iocmResize' together with a stack trace which includes the modules 'cfg_notify_iotasks' and 'cfg__notifyconfig' may be reported in the SAP ASE error log when the value of config parameter "number of disk tasks" or "number of network tasks" is changed at run-time and then reverted back to the earlier value. See KBA 2887284. |
| 814032 | A 6812 error, "Failed to PACK < x > inserted and < y > migrated rows in IMRS for partition ' < name > ' with partition id < value > and indid < value > of table ' < name > '" may be reported when CREATE CLUSTER INDEX is run in an IMRS enabled database after boot/load recovery. |
| 814043 | In rare circumstances, the built-in show_cached_plan_in_xml() does not return the query plan for queries in the statement cache when executing a statement in a cursor. See KBA 2697102. |
| 814051 | An UPDATE query which involves tables not consistently qualified with the 'dbo' qualifier, may give wrong results when executed by a user who is not the database owner. See KBA 2619053. |
| 814059 | In rare circumstances, for On Disk MVCC enabled tables, the number of UPDATE ROW locks taken by SAP ASE may be higher if value of the configuration parameter 'imrs cache utilization' is set to lower value. |
| 814070 | Under some circumstances, the Abstract Plan may be incorrectly stripped off when a dynamic SQL uses polymorphic built-in functions in a cursor statement. See KBA 2749022. |
| 814095 | Under rare circumstances, SAP ASE may hang at startup during engine online, when SAP ASE is running on kernel process mode. See KBA 2635465. |
| 814121 | In rare circumstances, Rep Agent may terminate with 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.". See KBA 2872301. |
| 814168 | Enable IMRS recovery using backwards scan of sysimrslogs, for improved performance, and efficient memory usage of IMRS during recovery. |
| 814190 | A 16053 error, "The command 'LOAD TRANSACTION' with property 'WITH UNTIL_TIME' is currently not supported in SAP Adaptive Server, IMRS-database < database_name > .", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database. |
| 814192 | Improvements have been made to the configuration option "restricted decrypt permission". |
| 814198 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mem_pageallocate', may be reported in the SAP ASE error log when a query is executed and the engine local cache memory is corrupted. See KBA 2614662. |
| 814204 | In rare circumstances, the statement line number is not correctly displayed in the showplan output when an SQL statement is executed with the set showplan option enabled. |
| 814217 | IMRS Cache size estimation done by Workload Profiler has been improved by accounting kernel overhead memory accurately. |
| 814240 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'CtlibRemoteAccess::getSubstValue' together with stacktrace that includes the moedules 'CtlibRemoteAccess::getColumnValues' and 'RPCRemoteAccess::getNext', may be reported in SAP ASE error log when 'granular permission' is enabled and a query, involving user created built-in functions and proxy tables, is executed. See KBA 2834468. |
| 814248 | A new SAP ASE configuration option, "stream rep msg channel timeout", is introduced through sp_configure for an HADR setup using synchronous replication. During a failover, this option defines the minimum time in seconds before a mode switch can take place. The default value is 60 seconds. |
| 814287 | With command line traceflag 11826 on, final query plans will print unique physical operator ids, to make their identification simpler. See KBA 2723236. |
| 814289 | The message, "Internal error: data length mismatch in ct_fetch().", may be reported in the Optdiag error log when displaying statistics using the Optdiag in a BASH shell with the LANG environment variable set to default. See KBA 1866748. |
| 814301 | In rare circumstances, the message, "DROP DATABASE could not clean < amount_of_unreleased_memory > bytes from the row storage cache, ' < imrs_cache_name > '. Please drop and recreate the cache before reusing it.", might be reported by DROP DATABASE, in case DMLs or imrslog_thresholdaction was running concurrently with DROP DATABASE command on the same database. |
| 814304 | In rare circumstances, SAP ASE may not find an abstract plan on disk during the re-compilation of a cached query which may result in a sub-optimal performance when the query is executed. See KBA 2748977. |
| 814317 | The message, "Assertion (!imrv- > imrv_xprev_verp || imrv_drc_prev) failed", may be reported in the SAP ASE error log, when a savepoint is added within an active transaction after executing DMLs against on-disk MVCC enabled tables and diagserver binary is in use. |
| 814325 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ridmap_update' together with a stack trace which includes the modules 'imrs_insert' and 'dol_insert', may be reported in the SAP ASE error log when inserting data into a Data Only Locked table in an IMRS database. |
| 814327 | The set command in the backupserver does not accept parameters values including blanks. The command has been changed to accept parameters to be enclosed in either single or double quotes, or between square brackets. |
| 814330 | For SAP BW user queries with fact_table hints, sometimes when the hint fails, SAP ASE selects a suboptimal plan because of a bad optimzation goal, resulting in poor performance. See KBA 2717708. |
| 814332 | The message, "Current process infected with signal 11", followed by a stack trace that includes the module 'mda_calc_proc_hdr_mem_KB' and 'mda_populate_monCachedProcedures' may be reported in the SAP ASE error log while querying the monCachedProcedures MDA table. See KBA 2835046. |
| 814338 | A new opimization criteria 'restrictive_greedy' has been added to avoid error 701, "There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.", while executing large queries during compilation phase. The same functionality is also available under TF 11838. See KBA 2901646. |
| 814341 | In rare circumstances, DML/scanner using isolation level 1 or isolation level 2 may skip committed INSERTED rows, if IMRS_PACK task is concurrently packing same set of rows. |
| 814358 | In rare circumstances, during boot time recovery of an IMRS enabled database some transactions may be ignored when the Adaptive Server is impolitely shut down and the corresponding IMRSLOG pages for these transactions are located 512 pages beyond the last fully committed transaction and a previous boot time recovery did not recover IMRSLOG. The message, "Empty oldest insert xact. No need to run imrslog recovery.", is reported in the SAP ASE error log. |
| 814397 | sp_sysmon_repagent system stored procedure raises "insufficient result space" error for replicated database IDs larger than 3 digits (999). See KBA 2628080. |
| 814433 | A 12336 error, "Definition time object 'database ' < dbname > ' ( < dbid > ), object ' < objname > ' ( < objid > )' found at run time as an attempt to drop the table had failed in a previous query. Please drop the above mentioned table using the DROP TABLE command." may be reported when trying to access a table after loading a database dump that was taken while the table was being created. |
| 814445 | In some rare scenarios, parallel execution of a query hangs when dynamic thread allocation feature is on and the query plan contains LeRestrictOp in the right subtree of LeMJOp. See KBA 2642040. |
| 814462 | If the option 'enable dump history' is enabled and the DUMP or LOAD command uses the SYB_TSM library with more than one stripe, the stripe name stored in the dump history file for each of the stripes will be the result of concatenating the previous stripe name. When the length of this is greater than 255 bytes, a 11076 error, "The name '' is too long. Maximum length is 255." will be reported, although the dump itself is successful. See KBA 2629866. |
| 814468 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'search_root_block_from_seqnode' together with a stack trace that includes the modules 'get_root_block', 'tdsrecv__mktree' and 'tdsrecv_open', may be reported in the SAP ASE error log when a user stored procedure with an execute cursor is executed. See KBA 2628762. |
| 814471 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ncdelete' together with a stack trace which includes the modules 'transfer_table' and 'row_delete', may be reported in the SAP ASE error log when TRANSFER TABLE < objname > FROM < filename > is executed on an All Pages Locked table (APL) and the table has an clustered and at least one non-clustered index defined and the same set of imported rows were present already in the table while diagserver is in use. |
| 814478 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memmove' followed by a stack trace may be reported in the SAP ASE error log when executing subqueries that make use of built-in replicate(). See KBA 2630662. |
| 814479 | A 18121 message, "Unrecognized change attribute option." is reported in the SAP ASE error log when the procedure sp_chgattribute is used to change the 'optimitistic_LFB' attribute of an index. |
| 814496 | The SAP ASE Workload Analyzer will fail to replay dynamic SQLs in a workload with errors, "Dynamic SQL error - Prepared statement 'xxxxx' does not exist.", reported in the SAP ASE Workload Analyzer Error Report Dashboard if the capture starts after the dynamic SQLs have been prepared. See KBA 2628500 |
| 814501 | When Rep Agent is configured for stream replication in sync or near-sync mode and a stream mode switch to or from async takes place while a DDL command is altering the schema of a table, Rep Agent may use an inconsistent schema of the table, causing the SRS DSI to shut down with an error from SAP ASE such as a 207 error, "Invalid column name ' < column_name > '". |
| 814518 | The error, "1 NvCache device found, please remove Nvcache device before proceeding to downgrade", will be reported when executing sp_downgrade_esd master to downgrade a server from SAP ASE 16.0 SP03 PL04 to a pre 16.0 SP03 PL04 version. |
| 814572 | A new MDA table, monSSLCertInfo, has been introduced to list the details of the SSL certificates used by SAP ASE. See KBA 2755239. |
| 814574 | A 12832 error, "The LDAP URL string ' < LDAP server URL > ' is invalid. LDAP subsystem reported error 'Can't contact LDAP server'", may be reported when using sp_ldapadmin to create secure LDAP connections. |
| 814583 | Under rare circumstances, the message "One or more entries in the data segment free space counts in database ID < value > was found to be negative and has been set to 0." may be reported many times in the SAP ASE error log. The message is enhanced to include fragment information and a corrective action and is printed only once for the same fragment. The new message text is, "The free space count for fragment with lstart < value > in database ' < dbname > ' was found to be negative and has been set to 0. Execute 'DBCC USEDEXTENTS( < dbname > ,0,1)' in single user mode to correct this count.". See KBA 2877207. |
| 814590 | DDLgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. See KBA 2632662. |
| 814596 | A 605 error, "An attempt was made to fetch logical page < page_num > from cache < cache_name > . Page belongs to database < db_name1 > , object < obj_name1 > , index < idx_name1 > , partition < ptn_name1 > and not to database < db_name2 > , object < obj_name2 > , index < idx_name2 > , partition < ptn_name2 > ", may be reported in the SAP ASE error log after executing a CREATE CLUSTERED INDEX on a round-robin partitioned table with the dboption 'enforce dump tran sequence' enabled. See KBA 2877205. |
| 814605 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeHashContext::Open' followed by a stack trace that includes the modules 'LeHashOp::_LeOpOpen', 'LeEmitXchgOp::_LeOpOpen' and 'LePlanOpen', may be reported in the SAP ASE error log when executing some SAP BW queries using a cached plan with a fact_table hint. See KBA 2877200. |
| 814613 | The message, "rapidlog unable to open file ..." and "timeslice -1501, current process infected" followed by a stack trace that includes the module 'worcap_packet', may be reported in the SAP ASE error log when capturing a workload. See KBA 2710120. |
| 814619 | The message, "Extending database by < value > pages ( < value > megabytes) on disk master", may be reported instead of a 5044 error, "ALTER DATABASE failed. Database < dbname > cannot be larger than the smallest database ( < dbname > ) that uses it as a template.", when ALTER DATABASE is run to extend a template database being used by a relaxed durability database whose size cannot accommodate the new size of the template database. |
| 814632 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ksMuxSchedulerRemoveQ' may be reported in the SAP ASE error log when a SHUTDOWN command with the WITH NOWAIT option is executed and will cause the shutdown command to hang. See KBA 2877223. |
| 814639 | Under an HADR setup when stream replication in enabled, sometimes the last command replicated is not confirmed by Adaptive Server and hence not applied on the standby database by Replication Server if there is no activity occurring in the primary database following that last command execution. |
| 814649 | A 325 error, " Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be reported when a query, which involves columns from an INNER JOIN being used in an ORDER BY clause, is executed against a VIEW and ROW LIMIT is applied. |
| 814651 | The text of the 4305 error, "Specified file 'dump device' is out of sequence. Current time stamp is < datetime1 > while dump was from < datetime2 > .", has been improved to provide the dump file name in the message text. See KBA 2634147. |
| 814654 | SAP ASE fails to enforce check constraints on global temporary tables. See KBA 2634213. |
| 814657 | In rare circumstances under an HADR setup, a 9414 error, "RepAgent( < dbid > ): Streaming replication stream CI Library error -1 with severity 2 and message 'Producer receiver ' < dbname > ' failed to receive data, shutting down transport to 'ocs:host:port'.'. Rep Agent detected error 3 with message 'Unknown' at line 0 in file nofilename.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent hang. See KBA 2692056. |
| 814658 | The message, "Sybase ENPAPI Error Message: INFORMATION: The FIPS Certified Crypto Kernel is enabled", is reported in the Job Scheduler Agent log as an information message but it also contains the term "Error", making it ambiguous. See KBA 2652006. |
| 814669 | DBCC CHECKCATALOG output format is misaligned and appears garbled. See KBA 2634413. |
| 814674 | In some cases, wrong results may be returned when executing a stored procedure containing views that might need to be recompiled. |
| 814700 | A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization." may be reported when enabling statement cache and using a table variable within a derived table. See KBA 2635224. |
| 814705 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'alloc_dirtychains' together with a stack trace which includes the modules 'CgLavaUtils::CgCompFakeTable' and 'GenLava' may be reported in the SAP ASE error log if a SELECT query on syslogsdetail is executed while SAP ASE is booted with trace flag 3608 whereby only the master database is recovered. See KBA 2635388. |
| 814714 | A 3702 error, "Cannot drop or replace the database ' < db name > ' because it is currently in use.", may be reported when dropping the versioned temporary database after switching off the version storage using "ALTER DATABASE < db name > VERSION STORAGE OFF" on user database. |
| 814743 | In rare circumstances, after taking a database dump of an IMRS enabled database, if operations on imrs_inserted rows stop for some time such that none of the log records between the oldest_inserted_xact and lastxact contain VRIDs, and there is a REBOOT followed by new inserts and a transaction dump taken, then loading the dumps may cause data corruption. |
| 814745 | The message, "kernel ssl_nrpacket_iocp: vsn 18 kpid 20250779 sossltdsremaining 0 bytestoread 29 iostatus ZERO", may be reported in the SAP ASE error log when SSL is enabled. See KBA 2885790. |
| 814754 | A batched language command executed with DYNAMIC_PREPARE set to FALSE can result in an open object and cached statement to be consumed and unable to be reused or freed for each batch. See KBA 2613604. |
| 814755 | Occasionally the execution of a SELECT query on a Data Only Locked (DOL) table may lead to incorrect results when the query optimizer uses a composite index of this table in order to access the data whose index leading column datatype is a fixed length CHAR and it contains special ASCII characters, such as CHAR(10), CHAR(31) or CHAR(1). See KBA 2636753 |
| 814762 | In rare circumstances, in an HADR setup when an IMRS database is replicated and the stream replication mode is enabled, the Rep Agent may sometimes send to Replication Server inconsistent Origin Queue ID (OQID) values that will prevent the Replication Server from draining its Simple Persistent Queue (SPQ) correctly. |
| 814767 | A 12352 error, "A transaction in database ' < name > ' (spid= < value > ) has hit a fatal error during rollback. ASE will try to reboot and recover the database. The XREC_BEGINXACT of this failing transaction is ( < page# > , < row# > ).", will now be reported in the SAP ASE error log besides to the end-user when the database option 'allow db suspect on rollback error' is enabled and a non-recoverable error is hit during a transaction rollback. |
| 814771 | For charsets involving multi-byte characters, example EUCJIS, sp_autoformat might incorrectly truncate data in the column, which can affect outputs of sp_helpdb, sp_helpdevice and other sprocs using sp_autoformat. See KBA 2637280. |
| 814782 | MERGE statement that does not perform any action may incorrectly return a rowcount different than zero. |
| 814788 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'func2view' followed by a stack trace that includes the modules 's_crtproc' and 'sequencer', may be reported in the SAP ASE error log when creating an in-lined Table-Valued SQL-based User Defined Function without SELECT statement. See KBA 2872236. |
| 814798 | In an HADR setup when stream replication is enabled, a 2615 error, "Attempt to insert duplicate row in database ' < name > ' ( < database ID > ), object ' < name > ' ( < object ID > ), index ' < name > ' (0), partition ' < name > ' ( < partition ID > ). Could drop and recreate index with ignore duprow or allow dup", followed by the message, "Command has been aborted", may be reported when replicating an All Pages Locked table that has a clustered index defined. See KBA 2872881. |
| 814806 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < name > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), partition 'sysimrslogs_59' (59). Please contact SAP Technical Support.", may be reported in the SAP ASE error log when a SELECT-INTO from sysimrslogs command is executed. See KBA 2872253. |
| 814828 | The role status shown in syssrvroles system table may not be correct after upgrading a 15.0.3 or 15.5 server to 16.0 SP03 or later version. |
| 814837 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mem__pageallocate_this_engine' together with a stack trace which includes the modules 'mem_pageallocate', 'mem_getpages' and 'hashbifs_md5_lerun', may be reported in the SAP ASE error log when using hashbytes() built-in with MD5 algorithm and input arguments as NUMERIC/DECIMAL/MONEY. See KBA 2636316. |
| 814870 | A 10330 error, "Access permission denied on object < objname > , database < dbname > , owner < username > ", may be reported when a stored procedure is executed by a user that does not have explicit permissions granted on the underlying referenced objects in the stored procedure, such as partitioned tables and user defined functions, while SAP ASE renormalizes the stored procedure from its text. See KBA 2748289. |
| 814891 | The DBINFO meta-data may contain wrong information after a cross-database DUMP and LOAD from an SAP ASE 16.0 SP02 to 16.0 SP03 release. See KBA 2710240. |
| 814895 | The message, "Assertion (rowstate != UNCOM_DEL)" together with a stacktrace which includes the modules 'bt__lock' and 'bt__savekeynblk', may be reported in SAP ASE error log when isolation level 3 scans are executed against IMRS enabled tables while the diagserver binary is in use. |
| 814901 | The message, "current process infected with 11 (SIGSEGV)", in the module 'memalloc’ together with a stack trace which includes the modules 'stu_findslot' and 'statgather’ may be reported in the SAP ASE error log during the process of statistics gathering when CREATE INDEX or a SELECT query involving sort is executed. See KBA 2641337. |
| 814903 | The SAP ASE Backup Server on the Windows platform will abort after raising an internal assertion if the debug version of the SAP open server library (e.g. as found in the $SYBASE\$SYBASE_OCS\DLL\DEBUG directory) is used. |
| 814910 | In rare circumstances, the message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation" or an "infected with 11 (SIGSEGV)" in the module 'get_resrow_size' together with a stack trace which includes the modules 'LopInsert::_lopCodeGen' and 's _compile_stmt' may be reported in the SAP ASE error log when a query is compiled and an object ID has been recycled by Adaptive Server causing a conflict between a definition time object ID and a Light Weight Procedure (LWP) object ID. See KBA 2788678. |
| 814916 | In a HADR installation, a new $SYBASE/DM/dir.properties file is added to capture the Custom Directory Information specified during HADR configuration. |
| 814919 | In rare circumstances under an HADR setup, a 12406 error, "Failed to find the last row marker for transaction ( < pagenum > , < rownum > ) in sysimrslogs for database ' < dbname > ' ( < dbid > ). The sysimrslogs row is corrupted.", may be reported during boot-time recovery of an IMRSLOG enabled database when stream replication is enabled. See KBA 2857871. |
| 814921 | An 16367 error, "EXECUTE AS OWNER procedures cannot be created by an alias or with the SETUSER command when the procedure has SQL statements that reference objects across databases. Create the procedure from a non-impersonated session.", may be reported in the SAP ASE error log when an impersonating user tries to execute a cross-database stored procedure which was created with the 'deferred name resolution' configuration enabled. See KBA 2755255. |
| 814923 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra_malloc_mempool' and 'ra_mempool_alloc_internal', may be reported in the SAP ASE error log when the Rep Agent Secondary Truncation Point (STP) Manager Thread terminates abnormally leading to corruption in the Rep Agent Memory Pool. See KBA 2722607. |
| 814927 | In rare circumstances on a heavily-loaded system, DROP INDEX may hang when the SAP ASE configuration option "hcb index auto tuning" is enabled and the HCB AUTO TUNING process is now sleeping and was working on the corresponding index. |
| 814942 | The SAP ASE Workload Analyzer will fail to replay a workload with errors, "ReplayThread- > loginUser for session < session ID > is empty" and "recieveTDSPackageToASEServer no response data from server for < Thread ID > ,SessionState [conn_id= < Session ID > , replayQueryID= < Query ID > , sessionStatus=LOGIN" reported in the SAP ASE Cockpit log if there are Kerberos enabled sessions. See KBA 2747779. |
| 814959 | In rare circumstances, a hang may be seen and reported by sp_lock, when a process executes a WRITETEXT command that is replicated and involves an in-row LOB column and a shared row lock request cannot be granted immediately, or when it sets the IDENTITY max burn value for a table and an exclusive table lock request cannot be granted immediately, or when the commands ALTER DATABASE and DUMP DATABASE or TRANSACTION are run concurrently and an exclusive address lock request on the database disk map cannot be granted immediately. |
| 814960 | In rare circumstances, SAP ASE sessions may hang in the module 'des_do_get' when attempting to access a table, as a result of a 2622 error, "Insufficient room on this page to insert a row of length < row length > . Page pointer = < page address > , pageno = < page number > , status = < page status > , ptnid = < partition id > , indexid = < index id > , level = < level > , pnextrno = < next row number > .", hit by another session together with a stack trace which includes the modules 'des__scavenge' and 'stat_pdes_flush_datachange' reported in the SAP ASE error log while an object descriptor is reused to host metadata for this table. See KBA 2670244. |
| 814962 | A 2512 error, "Table Corrupt: Cannot find the specified row number < value > , in index page < value > , partition ID < value > , on data page < value > .", may be reported when running DBCC CHECKTABLE and after loading a transaction dump that was taken while a concurrent committing transaction and the ckeckpoint log record written by DUMP TRAN was stored interleaved with the committing transaction log records in such a way that the fullycommitxact marker in the dump header is set to the dump instant of the IMRSLOG database. |
| 814968 | Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled. |
| 814980 | In rare circumstances on a multiple-engine system, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace which includes the modules 'strn0cpy', 'worcap_admin' and 'd_worcap_start' may be reported in the SAP ASE errorlog when the "dbcc workload_capture(start)" command is executed when the server is still being boot-strapped. See KBA 2877231. |
| 814983 | In rare circumstances under an HADR setup a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the target page is not a data page.", or a 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page.", or a 625 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the entry in the offset table for that RID is less than or equal to 0.", may be reported by the Rep-Agent scanner of IMRSLOG when a re-scan occurs and stream replication is enabled on an IMRS database. |
| 815018 | A 5859 error, "The configuration number '652' is invalid.", which value corresponds to the configuration parameter "bind backupserver address" may be reported in the SAP ASE error log during startup after adding a Dump Configuration using the ASE Cockpit or by using the stored procedure sp_config_dump. See KBA 2640866. |
| 815021 | The values of local variable parameters are not printed in the output of the 'SELECT QUERY_TEXT( < spid > )' query. |
| 815044 | A 101 error, "SQL syntax error", followed by a 105 error, "Unclosed quote before the character string", may be reported in the SAP ASE error log when the Job Scheduler is scheduling a new job with start time equal to the current time and under the condition that it has already scheduled maximum jobs i.e. equal to the value of config parameter 'job scheduler tasks'. |
| 815051 | In rare circumstances, a 5166 error, "DISK RESIZE encountered an error while attempting to open/resize the physical file < file_name > . Please consult the ASE error log (in the ASE boot directory) for more details", may be reported in the SAP ASE error log along with the message, "basis_dsizecheck: attempt to write page < page no > on device < path of the device > failed, system error is: Invalid argument", when DISK RESIZE is run again after a silent failure of an earlier DISK RESIZE command. See KBA 2645986 |
| 815055 | A 207 error, "Invalid column name ' < name > '.", may be reported during the execution of a SELECT query that joins a proxy table which has a LOB column while the statement cache is enabled. See KBA 2647459 |
| 815056 | A 208 error, "# < temporary_table_name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).", may be reported during the recompilation of a prepared statements batch which creates a temporary table. See KBA 2646418. |
| 815070 | SQL query text is not printed with stacktrace when SAP ASE runs into an exception during parallel execution. |
| 815081 | In rare circumstances, a 702 error, "Memory request for < num > bytes exceeds the size of single page of < 16384/8192/4096/2048 > bytes.", may be reported on a 16K/8K/4K/2K-byte SAP ASE installation, in the corresponding order, when the system stored procedure sp_post_xpload is executed after a cross platform DUMP or LOAD was run and a table in the source database has undergone a no data copy operation. See KBA 2646348. |
| 815086 | The 728 error message, "Allocation of size < value > bytes from the row storage cache, ' < name > ', failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < value > , object ID = < value > , partition ID = < value > , request type = < value > ( < string > ).", is enhanced to provide additional context information when we have run out-of-memory for an IMRS enabled database. See KBA 2885869. |
| 815099 | A 12858 error, "Update to sysobjects row for database ' < name > ' ( < dbid > ), object ' < name > ' ( < objid > ) failed.", in the module 'obj_updrow' together with a stack trace which includes the modules 'des_idtflush' and 'des_checkpoint' may be reported in the SAP ASE error log when DUMP DATABASE is in progress and the DDL transaction that created this object is rolled back. See KBA 2879979. |
| 815102 | A 251 message, "Unable to allocate ancillary table for query optimization. Maximum number of tables in a query (91) exceeded" may be be reported when more than 91 worktables are required internally by to execute a query. |
| 815110 | In rare circumstances under an HADR setup, a 9219 error, "RepAgent( < dbid > ): Internal coding error.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent implicit shut down or hang. See KBA 2885911. |
| 815121 | A warning message, "The configured value < value_1 > for parameter 'kernel resource memory' is too low. It should be at least < value_2 > for the present configuration", is reported when the kernel resource memory is resized by the server. This is not an appropriate warning and is now replaced by an informational message, "ASE has autoconfigured 'kernel resource memory' to < value_3 > pages". See KBA 2748316. |
| 815123 | The Backup Server may leak some memory when using non absolute paths for the interfaces file, the configuration file, the hosts.allow file or the dump stripes. |
| 815161 | A 8006 error, "ASE error detected by Backup Server. Refer to the preceding Backup Server message.", together with a stack trace that includes the modules 'dmp_send_dpm' and 'dpdb_main', may be reported in the ASE error log and the counterpart error, "3.15.2.1: The disk piece for page < number > does not belong to phase 2.", in the backup server error log when DUMP DATABASE is run while taking a database dump of an IMRS enabled database and the configuration parameter 'optimize dump for faster load' is enabled. |
| 815175 | In rare circumstances, SAP ASE may hang in the module 'xsc_sysimrslogs_valid_xactblk' together with the modules 'xsc__sysimrslogs_getnext' and 'rec__boot_recover_dbs' reported in the call stack of the hanging process while an IMRS enabled database is recovered as a result of an IMSLOG invalid page present in the committed region of the IMRSLOG. |
| 815204 | The message "current process infected with 11 (SIGSEGV)" in the module 'np_conn_props' together with a stack trace which includes the modules 'omni_ct_cancel' and 'hk_cis_idle_timeout' may be reported in the SAP ASE error log when many CIS connections exist and the configuration option "cis idle connection timeout" is enabled. Alternatively the SIGSEGV can be hit in the modules ‘comn_loc_copy’, ‘ct_poll’, ‘ct_gp_version’, ‘ct_gp_version’ or ‘ct__tds_sendcmds’. See KBA 2651690. |
| 815210 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ResRelOp' followed by a stack trace that includes the modules 'ResRelOpProcess' and 'CgpPop::_CgpPePredBmToScalar', may be reported in the SAP ASE error log when a query is executed that involves an OUTER JOIN on a materialized view and a non-materialized view that return a constant column and there is a predicate on this constant column. See KBA 2843635. |
| 815216 | The index attribute 'optimitistic_LFB' will not be enabled as expected on big-endian platforms such as Solaris, IBM pSeries Linux, IBM AIX and HP Itanium platforms, when executing command "sp_chgattribute ' optimitistic_LFB', 1". |
| 815217 | In rare circumstances, a storage access violation or the message, "Current process infected with signal 11 (SIGSEGV)" followed by a stack trace that includes the modules 'ubffreef', 'memfreeheap' and 'table__check', may be reported in the SAP ASE error log when running DBCC CHECKTABLE against system tables like SYSCOMMENTS where there are hidden columns. See KBA 2722616. |
| 815225 | Status bits representing a text page or an OAM page may be incorrectly set in a page pertaining to an imrslog segment. |
| 815238 | An 15413 error, "An internal error occurred during an encryption operation (error code -1)", may be reported when selecting data from views that contain encrypted columns where each view is created with the UNION ALL clause. See KBA 2651130. |
| 815342 | A SELECT query against the monSysLoad MDA table can return zero row if a search argument on EngineNumber or StatisticID is used with an engine number other than engine 0. See KBA 2651421. |
| 815367 | In rare circumstances, DUMP DATABASE may take extra time while releasing memory pages that keep track of page updates since the dump has started, after the dump is completed if the configuration option 'optimize dump for faster load' is enabled. See KBA 2657654. |
| 815369 | A new status bit (0x20) has been added to the dump history record to mark those entries that were inserted as a result of a LOAD instead of a DUMP operation. |
| 815377 | In rare circumstances on heavily loaded systems, a 539 error, "Unexpected internal access methods error 0, state 30.", or a 3914 error, "Illegal internal transaction status. This is an internal system error.", may be reported for a query involving temporary refresh pre-computed result set. See KBA 2825565. |
| 815388 | ASE needs to be rebooted to load the new SSL certificate after the existing certificate expires. This is now fixed by allowing ASE to reload new SSL certificate dynamically using the new parameter 'refreshcert' for sp_ssladmin. See KBA 2749006. |
| 815399 | In rare circumstances, DBCC CHECKTABLE may report index inconsistencies on an IMRS enabled table, after LOAD DATABASE followed by one or more of LOAD TRANSACTION commands using the backward scan recovery strategy were executed. |
| 815429 | A new system view, syslogininfo, has been added to allow ASE users having sa_role or sso_role role to find out the number of days remaining before logins will be locked due to an unchanged password. See KBA 2686769. |
| 815472 | In rare circumstances, when a workload with a large dataset is being monitored using the Workload Profiler, an arithmetic overflow error may occur. If a new monitoring session is started while the existing one is still active, a 19537 error, "Invalid syntax or illegal use of the USING clause" is incorrectly reported which is misleading. |
| 815480 | The error, "Backup Server: 3.17.2.2: Pathname parameter must specify an absolute pathname. Rejected value: (unreachable)/ASE-16_0/install", followed by a 8009 error, "Error encountered by Backup Server. Please refer to Backup Server messages for details.", will be raised when executing a DUMP or LOAD command if the SAP ASE working directory is unmounted. See KBA 2669530. |
| 815496 | Under rare circumstances, the free page count for database segment 0 (system) may become negative and not reset to 0 without a message reported in the SAP ASE error log indicating this negative free page count. See KBA 2686750. |
| 815548 | In rare circumstances, a 631 error, "The length of < value > passed to delete row routine for the row at offset < value > is incorrect on the following page of database ' < name > ': Page pointer = < value > , pageno = < value > ... The expected row length is < value > . The offset should be no greater than < value > .", may be reported in the SAP ASE error log followed by the message, "Error while undoing log row in database ' < name > '. Rid pageid = < value > ; row num = < value > .", during the roll back of a user transaction when the syslogs available space has crossed the last chance threshold and the session was explicitly killed. This may result in phantom locks left behind because of the roll back failing. See KBA 2660763. |
| 815553 | A 622 error, "Opentable was passed a varno of 0. Object ' < table_name > ' in database ' < database_name > ' already has that session descriptor in use. This occurred while opening object id < object_id > in database id < database_id > .", may be reported in the SAP ASE error log after upgrading from ASE version 16.0 SP02 to version 16.0 SP03 or upgrading from ASE version 15.7 to version 16.0 SP02 when a SELECT statement references a table having computed columns which involving SQL user defined function. See KBA 2686324. |
| 815559 | Occasionally the monProcessActivity MDA table may report negative value in LocksHeld column after the sp_sysmon or sp_monitor stored procedures are executed. See KBA 2755793. |
| 815569 | The configuration file offset record in the decompressed dump is not correct and hence sybmon cannot extract the original configuration file. |
| 815581 | A 11060 message, "This statement has exceeded the maximum number of recompilations (20). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support", may be reported during workload replay with the "Reset server time to source workload capture time" option selected and a VIEW, that is created after the workload captured time, is accessed. See KBA 2661224. |
| 815594 | Under some circumstances, the output from executing the sp_opt_querystats procedure with the 'option_show_long' option may have malformed text with random newline breaks over some words. |
| 815608 | In rare circumstances, the message, "Current process infected with 11 (SIGSEGV)" in the module 'dol__index_decompress_row' together with a stack trace which includes the modules 'bulk_fast_idxupdate' and 'reorg_defrag', may be reported in the SAP ASE error log when REORG DEFRAG is run. See SAP Note 2665483. |
| 815610 | A 9414 error, "RepAgent( < dbid > ): Streaming replication < value > CI Library error < value > with severity < value > and message ' < failure_reason > '. Rep Agent detected error < value > with message 'Unknown' at line at line 0 in file nofilename." may be reported in the SAP ASE error log when the stream replication is enabled and an error has occurred in an HADR setup. The code is enhanced to report appropriate line number and file name values to help diagnose the code path taken when the problem was encountered. See KBA 2686789. |
| 815626 | In rare circumstances, a 820 error, "Attempt to dirty non-log buffer BUF= < value > , MASS= < value > , ... Pinned xdes= < value > spid= < value > which is in I/O.", together with a stack trace which includes the modules 'bufpindirty' and 'plc__flush' may be reported in the SAP ASE error log when the syslogs system table is bound to a dedicated log cache having large buffer pool sizes configured. See KBA 2747852. |
| 815641 | A table with hash partitions, the column histogram steps does not match to the partition histogram after update statistics with different setting of "histogram tuning factor". See KBA 2662968 |
| 815662 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'EquivClass::EquivClass' together with a stack trace that includes the modules 'EquivClass::eqcCheapestNonBmoSortPop', 'EquivClass::eqcEagerEnforce' and 'GttTable::GttUsefulIndex', may be reported in the SAP ASE error log when selecting from a table-valued UDF using Parallel Mode. See KBA 2663557. |
| 815677 | Non thread-safe time routines are used to construct up the stripe names when DUMP DATABASE or DUMP TRANSACTION is executed with the option "using config= < dump_configuration > ". |
| 815681 | Performing a downgrade from SAP ASE 16.0 SP02 PL05 or higher to a version prior to SAP ASE 16.0 SP02 may report a failure on 'sysobjects.sysstat5' and 'sysindexes.status4' columns for replicated tables having a unique index. See KBA 2664693. |
| 815693 | In an SAP HADR system, the fault manager failed to start the heartbeat when multiple tempdb is configured in SAP ASE. See KBA 2672505. |
| 815706 | On Windows platforms, the message, "Parameter 'start address' (number 1) to DBCC command 'bytes' has invalid value/type." may be reported in client console, or the printed address doesn't match the specified address in DBCC BYTES command when DBCC BYTES (address, length) is executed. |
| 815730 | Performing a downgrade from SAP ASE 16.0 SP03 PL04 may report a failure on 'sysindexes.status4' columns for user tables having a Latch Free Btree index on big-endian platforms, such as Solaris, IBM pSeries Linux, IBM AIX and HP Itanium platforms. |
| 815731 | A 728 error, "Allocation of size < num > bytes from the row storage cache, < cachename > , failed as there is not enough memory available in the cache. Please increase the cache size. Memory allocator information = < memory_address > , object ID = < object_ID > , partition ID = < partition_ID > , request type = < type_ID > < (type name) > .", may be reported when a DELETE or UPDATE operation is being performed on a row that reside in the in-memory row storage and there is not enough space available. |
| 815740 | The message "current process infected with 11 (SIGSEGV)" in the module 'site_login_cancel' with a stack trace followed by the message "Scheduler infected: exiting" may be reported in the SAP ASE error log. See KBA 2682423. |
| 815749 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'vu_fixupvar' followed by a stack trace that includes the modules 'vu_fixupview', 'vu_fixuproot' and 'vu_fixupsubq', may be reported in the SAP ASE error log when a query is executed on a VIEW and there are more than 128 worktables involved in the VIEW. See KBA 2845585. |
| 815760 | A new backup server configuration parameter, 'retaindays', has been added to specify the number of days that a database or transaction dump will not be writable. |
| 815762 | Syntax errors 102, 105, and 107 may be raised when accessing view or stored procedure referencing a table which has "." character in its name. Msg 102, Level 15, State 4: Server 'LINUX_160SP0', Line 2: Incorrect syntax near '[]'. Msg 105, Level 15, State 2: Server 'LINUX_160SP0', Line 4: Unclosed quote before the character string '" '. Msg 107, Level 15, State 1: Server 'LINUX_160SP0', Line 2: The column prefix 'mytable.Funds reservation field status var' does not match with a table name or alias name used in the query. Either the table is not specified in the FROM clause or it has a correlation name which must be used instead. Msg 107, Level 15, State 1: Server 'LINUX_160SP0', Line 3: The column prefix 'mytable.Foreign Trade: Screen ctrl of imp.data f' does not match with a table name or alias name used in the query. Either the table is not specified in the FROM clause or it has a correlation name which must be used instead. |
| 815772 | A 2714 error, "There is already an object named '## < table_name > ' in the database.", followed by a 4413 error, "View resolution could not succeed because the previously mentioned objects, upon which the view ' < view_name > ' directly or indirectly relies, do not currently exist. These objects need to be recreated for the view to be usable.", may be reported incorrectly during the execution of a SELECT query which references a VIEW that is making use of global temporary tables. See KBA 2948438. |
| 815803 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubffreef' followed by a stack trace that includes the modules 'ufclose', 'dir_sendtext' and 'DIRRemoteAccess::sendText', may be reported in the SAP ASE error log during concurrent access of big files via a proxy table. See KBA 2672421. |
| 815811 | Executing 'REORG REBUILD < table_name > < index name > ' where the index has latch_free_index enabled may result in various errors including 12314, 12323, 820, 872, 11068 at run time and a 3478 error during recovery. See KBA 2669056. |
| 815821 | When Rep Agent is configured for stream replication in an IMRS enabled database and a retriable stream error occurs, the message "current process infected with 11 (SIGSEGV)" in the module 'ubffreef' together with a stack trace which includes the modules 'ra_free_mempool' and 'ra_ci_stp_remove_all_oqid' may be reported in the SAP ASE error log resulting in Adaptive Server terminating abnormally because of RAMEM_SPIN spinlock being held. See KBA 2686301. |
| 815824 | The Spins, Waits and Grants columns in monSpinlockActivity MDA table will get wrapped at 2147483648 (2^31) even though the columns are defined as BIGINT. See KBA 2686281. |
| 815827 | sp_help ' < proc_name > ' may report an incorrect fully qualified parameter list when the procedure < proc_name > is created with TABLE type or TABLE variable parameters. |
| 815832 | A 11021 error, "Function < function_name > invoked with wrong number or type of argument(s).", may be reported in the SAP ASE error log when upgrading a SAP ASE 16.0 SP03 PL03 or later version and an in-lined table-valued UDF is accessed. See KBA 2748456 and KBA 2738592. |
| 815833 | A query, which is selecting from a view with a left outer join and a predicate in where clause, and the view definition contains a subquery in 'When exists' which is wrapped in 'case' clause and a left outer join is used, may return wrong results which don't take the predicate into account. See KBA 2690931. |
| 815835 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE. See KBA 2879605. |
| 815844 | When SAP ASE encounters a secondary signal violation while dealing with a primary signal violation, it makes the process that hit these signal violations a zombie process. SAP ASE will now shut down implicitly instead and the message, "UNHANDLED EXCEPTION: signal in signal handler", will be reported in the SAP ASE error log. When required it is possible to retain the zombie process behavior by starting SAP ASE with the trace flag 2917 or enabling it at run time using DBCC TRACEON. See KBA 2682383. |
| 815851 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'odlrh__toloh' together with a stack trace which includes the modules 'onl__test_upgraded_replicated_db' and 'online_database' may be reported in the SAP ASE error log, when a replicated database dump is loaded into an upgraded Adaptive Server version. See KBA 2686290. |
| 815867 | A 100015 soft fault (page loop error) may be reported by sp_dbcc_faultreport after executing a DBCC CHECKSTORAGE on a database that contains about 15000 syspartitions rows. See KBA 2670254. |
| 815921 | A new column 'clientport' is added into master..sysprocesses system table and a new column 'ClientPort' is added to master..monProcess and master..monProcessLookup MDA tables to show client port numbers of user connections. |
| 815932 | The message, "Current process infected with 11 (SIGSEGV)" in the module 'lt_get_proc' together with a stack trace which includes the modules 'lt_send_truncpoint' and 'exec_dbcc' may be reported in the SAP ASE error log when the command 'DBCC SETTRUNC' or 'DBCC GETTRUNC' is executed. See KBA 2878359. |
| 815945 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'prot_pcr_get_perms' followed by a stack trace that includes the modules 'rvm_dispatch' and 'rvm_cfgadm_check_access', may be reported in SAP ASE error log when granular permission is enabled and any Non-Volatile cache configuration command is executed using sp_nvcacheconfig, sp_nvbindcache or with sp_sysmon. See KBA 2671978. |
| 815981 | A 208 error, "## < name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).", may be reported when a stored procedure materializes a global temporary table under a transaction that is rolled back afterwards. See KBA 2672877. |
| 816000 | A 15101 message, "There is insufficient memory to allocate < n > bytes. Please increase configuration parameter 'messaging memory', or try again when there is less activity on the server." may be reported when a large value has been set for the configuration parameter 'messaging memory' and real time messaging queries are executed in multiple concurrent sessions. See KBA 2674952. |
| 816001 | KBA 2754612 - The message, "The stored procedure < sproc_name > has an old format and cannot be used internally by Adaptive Server until it has been upgraded. You can execute DBCC UPGRADE_OBJECT( < sproc_name > ) to avoid this.", may be reported during an upgrade of SAP ASE to a higher version due to the system stored procedures being created with 'deferred name resolution' enabled in the pre-upgrade version. |
| 816003 | Update the version of Jetty used for SAP ASE Webservices to Jetty 9.4.11. |
| 816009 | In rare circumstance, a 889 error, "Internal error. Contact SAP Technical Support for help. BCM thread found MASS < buffer_address > in database < database_name > ( < database_ID > ) and cache < cache_name > ( < cache_ID > ) in an unexpected state < value > ", may be reported if latch free indexes are created and the house keeper garbage collector task (HKGC) is enabled in the database. See KBA 2686353. |
| 816013 | In rare circumstances, a 3935 error, "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context. The transaction is currently in 'Command-attached' state.", may be reported when executing a query in STATEMENT SNAPSHOT ISOLATION mode against a Multi-Version Concurrency Control (MVCC) enabled table when the configuration option 'allow statement rollback' is enabled. See KBA 2878396. |
| 816024 | In rare circumstances, when the Backup Server is shut down with "shutdown SYB_BACKUP", the SITE HANDLER for the SYB_BACKUP connection never gets released in SAP ASE. Then on a successful restart of the Backup Server, the SITE HANDLER is unable to connect to the Backup Server. This causes that all subsequent DUMP commands are hanging in the SAP ASE Server. SAP ASE traceflag 8024 (along with 3623) should be enabled to collect diagnostics in the SAP ASE log. See KBA 2669570. |
| 816025 | The message, "A fatal error has been detected by the SAP Java Virtual Machine: EXCEPTION_ACCESS_VIOLATION (0xc0000005)", together with the error message, "NTPCI__exit(1); Native Thread failed to unwind while attempting to shutdown the PCI", may be reported in the SAP ASE error log when loading sunec.dll on Windows platforms. See KBA 2687973. |
| 816028 | The description of parameter "--upgrade-ok" has been updated to make clearer what it does. |
| 816034 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE and also behind the last hole fixed by the Fix-Phase of imrslog boot-time recovery. See KBA 2832004. |
| 816054 | The message, "Current process infected with signal 11(SIGSEGV)", followed by a stack trace that includes the modules 'bt__col_cmp_noopt' and 'bt__nonlfrow_cmp' may be reported in the SAP ASE error log when a SELECT query with GROUP BY that contains expressions is executed. See KBA 2681394. |
| 816062 | The message, "ERROR in plc__lrtopage() for plc < address1 > , dbid < database_id > , log record from plc at offset < address2 > with len_logrec < size > does not fit in log page with size < page_size > .", together with a stack trace which includes the modules 'xact__commitxact' and 'xls_flush_plcqueue' may be reported in the SAP ASE error log when a multi-database transaction is committed and one branch of the transaction involves an in-memory enabled database. See KBA 2709753. |
| 816073 | The message "enp_aesEncrypt: CCLCipherCtx_all failed with error: 0xa0100014." may be found in the SAP ASE errorlog when the length of the user password which is used for the Job Scheduler is either 7 or 23. See KBA 2677850. |
| 816078 | In rare circumstances under an HADR setup, the coordinator process of SAP ASE RepAgent may hang in the module 'ra__ci_coordinator_waits_for_switch_ack' preventing the replication flow to continue. |
| 816102 | The message, "current process infected with 11 (SIGSEGV)", in the module 'norm3_expr' together with a stack trace which includes the modules 'norm3__process_case' and 'crcpc_norm' may be reported in the SAP ASE error log when a SELECT query with computed columns is executed. See KBA 2844942. |
| 816107 | The active Rep Agent trace flags will now be reported in the SAP ASE error log when a Rep Agent is started. When no Rep Agent trace flag is active the message, "RepAgent( < dbid > ) no active traceflags.", will be reported. Otherwise the message, "RepAgent( < dbid > ) active traceflags: < TF1 > , < TF2 > , ..." will be reported. |
| 816125 | A 11138 error, "Failed to create role < role_name_992 > , because this exceeds the maximum number roles limit of '1024'. Please delete roles you don't need and rerun your command.", may be reported when a user tries to create the 992nd role. See KBA ##2679595 |
| 816133 | Stored Notify settings in Cockpit are no longer shown after disabling a monitoring Alert. See KBA 2682425. |
| 816139 | SAP ASE Resource Governor does not terminate a session that was waiting on a lock acquisition when the configuration option ‘allow resource limits' is enabled and the resources limit action is to terminate the session when it exceeds the configured elapsed time value. See KBA 2679863. |
| 816178 | In rare circumstances, when DBCC REINDEX() or SP_FIXINDEX hit out of memory error 1105, "Can't allocate space for object ' < object-name > ' in database ' < db-name > ' because ' < segment-name > ' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment", on a DATA-ONLY Locked table with a placement index, then subsequent commands scanning the same object may fail with either of error 696, "An attempt was made to fetch logical page ' < page-number > ' from cache ' < cache-name > '. Page belongs to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > and not to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > . Restart of ASE will clear the error. Please contact your System Administrator for help.", or error 1142, "Invalid OAM Page < page-number > . Found pstat= < stats > , object= < obj-id > , database= < db-id > , indid= < ind-id > .", or error 605, "An attempt was made to fetch logical page ' < page-number > ' from cache ' < cache-name > '. Page belongs to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > and not to < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > .", or error 692, "Uninitialized logical page ' < page-number > ' was read while accessing < db-name(db-id),obj-name(obj-id),index-name(ind-id),partition-name(part-id) > . Please contact SAP Technical Support.". |
| 816203 | updatease fails to start the SAP ASE server if the master device file size is larger than 4GB. |
| 816248 | INSERT to varchar column may incorrectly left trailing spaces if the source of the INSERT command is local variable and the query to insert the data is using UNION. See KBA 2683043. |
| 816272 | The system stored procedure 'sp_activeroles' may show only the latest granted user defined predicated role, even if multiple user defined predicated roles are granted to the login, when SAP ASE configuration option 'enable predicated privileges' is enabled. See KBA 2684433. |
| 816290 | The number of free log pages in a database could be incorrectly reported by the sp_helpdb command, if the command ALTER DATABASE [LOG] OFF is used to remove pieces from the last database fragments and the command DUMP DATABASE WITH SHRINK_LOG is executed to remove the resulting fragment holes. |
| 816322 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'memtextlen' together with a stack trace which includes the modules 'prE_PARAMs_buf' and 'prSQLTEXT', may be reported in the SAP ASE error log when executing DBCC SQLTEXT and select query_text in parallel. See KBA 2843657. |
| 816352 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'yylex' together with a stack trace which includes the modules 'sqlpars' and 'internal_sql' may be reported in the SAP ASE error log when many invisible[*] characters appear in the query text following an SQL keyword, resulting in either a zombie task being created (in ASE 15.7 SP140 or ASE 16.0 SP03 PL04) or SAP ASE unexpectedly shuts down (in ASE 16.0 SP03 PL05 where a double signal is regarded as a fatal condition, but TF 2917 can be used to revert behaviour to the zombie task creation). See KBA 2686240. |
| 816355 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that there are some cross-log transactions whose sysimrslogs records are present on a sysimrslogs page that has a higher timestamp than that of the syslogs page containing the OQID rid. |
| 816391 | The dump history file contains unexpected 'dump.error' messages at a time when SAP ASE reports a 1204 error, " ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS." and the log truncation is not successful. See KBA 2686302. |
| 816397 | A 1526 error, "Sort failure. The configure size for data cache ( < name > ) is not sufficient to handle the sort buffers ( < value > ) requested. Please reconfigure the data cache or sort buffers and try the command again.", may be reported during the execution of a query as a consequence of a memory leak caused by the extensive usage of the built-in set_appcontext() and rm_appcontext(). See KBA 2748397. |
| 816400 | In rare circumstances, the progress status message, 'Backup Server: 4.188.1.1: Database < database_name > : < value > kilobytes ( < value > %) DUMPED.', may be truncated unexpectedly when DUMP DATABASE is executed. See KBA 2687371. |
| 816407 | The message, "Current process infected with signal 10 (SIGBUS)" in the module 'obfuscate_ldapacpwd' together with a stack trace which includes the modules 'ua__setldapacct' and 'sa_ssladmin' may be reported in the SAP ASE error log when sp_ldapadmin is run with command set_access_acct as part of LDAP configuration. See KBA 2843616. |
| 816409 | A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after having dropped a user database which is marked suspect and is On-Disk MVCC enabled. |
| 816425 | A memory leak in the PSS memory pool may be observed when there are multiple executions of 'SET ROLE WITH PASSWORD ON' in every other 'SET PROXY' session without a corresponding 'SET ROLE OFF'. See KBA 2656891. |
| 816450 | A 208 error, " < Table_name > not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", is reported when running any query involving global temporary table on an SAP ASE that is upgraded from a version between 16.0 SP02 GA and 16.0 SP02 PL06 HF1 to a higher version, and when the global temporary table is created with deferred table allocation set on the pre-upgraded version of ASE. See KBA 2680853. |
| 816457 | A new option 'create_table' has been added to the system stored procedure sp_dump_history that creates a proxy table in the tempdb database to access the dump history file. |
| 816487 | A new configuration option 'secondary signal handling' is introduced for SAP ASE which determines how the server handles secondary signals. The default value (1) makes the server shutdown on secondary signal. See KBA 2822070. |
| 816520 | When no size is specified in the ALTER DATABASE command, the default size is incorrectly set to 512KB instead of 1MB for an Adaptive Server installation that is using a page size of 2KB. See KBA 2722663. |
| 816521 | sp_showplan is enhanced to use 0 instead of -1 to display the specified statement ID. |
| 816538 | In rare circumstances, SAP ASE may become unresponsive and a 15403 error, "No memory for Encrypted Columns Frag bucket pool growth", may be reported in the SAP ASE log when the configuration parameter 'max parallel degree' is set to value greater than 1. See KBA 2691726. |
| 816544 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ubfreef' together with a stack trace which includes the modules 'cm_increase_cache_size' and 'cfg__updatecache', may be reported in the SAP ASE error log when increasing the size of an inmemory cache. See KBA 2691539. |
| 816545 | Running sp_helpdb against a database can report usage as "-- unused by any segments --" when a database usage contains a user defined segment only. See KBA 2691648. |
| 816557 | The message, "Assertion (pss- > pdbtkept = NULL)", together with a stack trace that includes the modules 'mda_populate_monRepLogActivity' and 'mda_exec', may be reported in SAP ASE error log when querying the MDA table monRepLogActivity while the diagserver binary is in use. |
| 816562 | The message, "Assertion (!(imrv- > imrv_status & IMRV_BULK_PURGE_VERSIONS) || ( imrslog_bkoutctx- > bulk_purge_ctxp && (imrslog_bkoutctx- > bulk_purge_ctxp - > ibpc_nloggedrows == IMRV_BULK_PURGE_NROWS(imrv)))) failed", may be reported in the SAP ASE error log for an IMRS enabled database during the execution of TRUNCATE TABLE while the diagserver binary is in use. |
| 816571 | The message, "Assertion (!keylength || !statp- > st_cache.st_length || ((statp- > st_descending ? -1 : 1) * compare_value( stu_null_datatype(histp- > st_steps. st_dt.st_idatatype), statp- > st_cache.va.st_buffer, statp- > st_cache.st_length, keybufp, keylength)) > = 0)", together with a stack trace which includes the module 'ups_histogram_gather' may be reported when creating a unique index on a CHAR column on a partition table and the diagserver binary is in use. |
| 816603 | Enhancement to support LATCH FREE INDEX at database level. |
| 816605 | When the value of configuration parameter "HCB index auto tuning" is set to 1, unique indexes will be qualified for Hash Caching depending on the workload. |
| 816639 | An extra line may be printed between the header and the actual content in the sp_helpdb output. |
| 816641 | When sp_thresholdaction runs in a temporary database it does not inherit the usual roles the sa account should have. See KBA 2693655 |
| 816643 | The message, "Invalid data found and rebuilt in segment accounting array for segment < segment_id > in database ID < database_id > .", may be reported in the SAP ASE error log following the recovery of a database. See KBA 2672135. |
| 816646 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module ‘GtElement::GtSecondaryInit(OptBlock*)' and the message, "timeslice error: spid < spid# > exhausted its 'time slice' of < X > milliseconds and additional 'cpu grace time' of < Y > ticks ( < Z > milliseconds). It has been marked for termination.", together with a stack trace which includes the module 'ApStoredTab::findGttTable()' may be reported in the SAP ASE log while executing a large query. See KBA 2699085. |
| 816677 | A 10707 error, "java.io.FileNotFoundException: < jre > /lib/ext/ < jar_file > (Permission denied)" together with java stack trace may be reported when running a java method which implicitly invoke the loading of the extension < jar_file > . |
| 816694 | The message "current process infected with 11 (SIGSEGV)" in the module 'pipe_read' or 'pipe_write' together with a stack trace may be reported in the SAP ASE error log during the parallel execution of a Lava query. See KBA 2694998. |
| 816700 | The sybmon command, 'print < address > -1 DES', may enter into an infinite loop and print the message, "txc_colid=0, txc_coffset=0, txc_indid=0", repeatedly when a memory dump is loaded in virtual map mode. |
| 816703 | The message, "RepAgent( < database_id > ): Autoscaling: Warning: The 'buffer pool' cannot grow any further and the scanner will sleep on packages becoming available.", may be excessively reported and logged in the SAP ASE error log when the 'stream replication' option is enabled. See KBA 2695973. |
| 816710 | In rare circustances, a process may hang in the module 'fio__p_sema' when trying to DUMP or LOAD a database if another Adaptive Server process has died due to a time slice error when reading or writing the dump history file. |
| 816715 | A memory leak in the Backup Server may be seen every time a DUMP of an in-memory database is taken. |
| 816716 | A 11030 error, "Execution of unknown type ptncond_xxx_0 failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo.ptncond_xxx_0.", can be seen after an upgrade when a roundrobin partitioned table with a clustered index has an index key with bigdatetime/bigdate/bigtime datatype. See KBA 2697077. |
| 816729 | A 1244 error, "Could not find address lock at address < address > while trying to release it", may be reported when querying the monCachedObject MDA table. See KBA 2835508. |
| 816735 | Dump files created using a pipe can now be loaded without using a pipe. Additionally, backup files created without using a pipe can now be loaded from a pipe. See KBA 2793815. |
| 816738 | The total number of database pages stored in the dump header could not match the number of pages according to the database disk map stored in the same dump header if the database had trailing log holes and the end-user executed the command DUMP DATABASE WITH SHRINK_LOG | SHRINK_DATA | SHRINK_DATABASE. |
| 816739 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'show_plan' followed by a stack trace which includes the modules 'LeRun' and 'LeEvals::LeEvRun', may be reported in the SAP ASE error log when using sp_showplan to query another session's query plan that involves CURSORs and the statement cache is enabled. See KBA 2722621. |
| 816752 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'bufsearch_cache_getlatch' together with a stack trace which includes the modules 'bt__fillrkey' and 'redo_bt_pagecompress', may be reported in the SAP ASE error log when LOAD TRANSACTION fails to redo some log record operations that involve cache-discrepant compressed index pages. See KBA 2696547. |
| 816756 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'brfinish' together with a stack trace which includes the modules 'iocRunController' and 'blkioComplete', may be reported in the SAP ASE error log when SAP ASE completes a disk I/O operation. See KBA 2722610. |
| 816760 | Progress messages have been added for the ONLINE DATABASE command execution for better reporting. |
| 816762 | Using the SP_BINDEXECLASS 'sv' object type to change the server-wide priority setting for the housekeeper wash task does not work. See KBA 2725920. |
| 816829 | Occasionally on a heavily-loaded multi-engine system, some column values in the monState MDA table, including ULCKBWritten, LogicalReads, PhysicalReads etc. might suddenly become decreased. See KBA 2748418. |
| 816835 | The configuration parameter "LFB memory size" is unexpectedly stored as "LFB pool size" in the configuration file. See KBA 2699329. |
| 816908 | Some new columns, 'NetType', 'ListenerAddress', 'ListenerPort', 'SSLCommonName', 'SSLCipherName' and 'SSLVersionName' are added to master..monProcess and master..monProcessLookup MDA tables to report network used by incoming clients. See KBA 2578601 for more details. |
| 816909 | KBA 2702143. A new configuration option 'HADR connect timeout' is introduced to control the timeout value for the connection to the remote ASE. |
| 816934 | Incorrect results may be observed when a query involves temporary precomputed result set and the 'set rowcount < number > ' is used to limit the number of rows. |
| 816941 | A 9235 error, "Could not allocate memory for gettrunc. Please retry gettrunc() later when more memory is available, or re-configure the server with a larger procedure cache.", will be reported when the command DBCC GETTRUNC fails to allocate memory. The error message wrongly refers to the procedure cache and should instead indicate the need to increase the value of the parameter 'replication agent memory size'. |
| 816955 | Error 11058 "Statement contains ' < > ' columns/expessions in the target list. This exceeds the maximum limit of '4096'." might be raised when using cursors with large IN() list which exceed 4096 elements. See KBA 2747807. |
| 816992 | When a DUMP or LOAD command using an SAP ASE backupserver API library is aborted from the client, the call to the module 'syb_close' that will close the stripes gets the mode SUCCEED_ON_CLOSE instead of ABORT_ON_CLOSE. The result is that the API library cannot know that the operation was aborted. See KBA 2705604. |
| 817001 | The message, "The compiler will use the current best plan when 10%(Optimization Timeout limit) of average execution time is exceeded.", may be reported mistakenly by SAP ASE when the set option show brief/on/normal/long is enabled and the set plan opttimeoutlimit < value > is set to a different value than the default value of 10. |
| 817028 | The 10330 error, "EXECUTE permission denied on object sp_extrapwdchecks, database master, owner dbo", may be reported by sp_extrapwdchecks when a non-sso user attempts to change his own password. See KBA 2710822. |
| 817066 | The configuration option, "abstract plan dynamic replace", has been extended to accept a new option value of '2'. When the configuration option is set to '2', the parameterized SQL text with its abstract plan will be saved in sysqueryplans. |
| 817069 | A 5861 error, "The current 'max memory' value ' < value > ', is not sufficient to change the parameter 'allow updates to system tables' to '1'. 'max memory' should be greater than 'total logical memory' ' < value > ' required for the configuration.", might be reported when running sp_configure with options like "allow updates" that do not require more memory when static config parameters such as "global cache partitions" is set to a non-default value and the amount of free memory remaining is relatively small. See KBA 2817648. |
| 817072 | The jobs scheduled by the SAP ASE Job Scheduler does not expire after the timeout period even when the 'default_timeout' for the job is set to a non-zero value in the absence of 'timeout' for the scheduled job. See KBA 2748408. |
| 817092 | When a downgrade is attempted from ASE 16.0 SP03 PL04 or higher version to a lower version using the stored procedure sp_downgrade_esd, and the higher version contains SQL UDFs that do not reference tables, the downgrade will fail. See KBA 2722683. |
| 817097 | A 325 error, "Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact Sybase Technical Support.", may be reported when a SELECT query with two tables join and a GROUP BY clause on each side of the join is executed while the optimization goal allrows_mix is enabled but hash_join is not. See KBA 2708697. |
| 817103 | When the option 'set statistics io' is turned on, the output has been enhanced to display the number of hash cache lookups and hits for Hash Cache Btree (HCB) enabled indexes on Data Row Cached (DRC) enabled tables. |
| 817111 | Under rare circumstances, the message, "Current process infected with signal 6 (SIGABRT/SIGIOT)" in the module 'gsignal()' together with a stack trace which includes the modules 'dcl__get_sess_props' and 'iface_props' may be reported in the SAP ASE error log when stopping the SAP ASE using SHUTDOWN WITH NOWAIT and the diagserver is in use. |
| 817125 | The values of variables used with the CREATE/ALTER/DROP LOGIN commands are not captured in the audit records when global auditing is on and the audit option 'login_admin' is enabled. See KBA 2746705. |
| 817167 | A 712 error, "There is insufficient heap memory to allocate < wrong_huge_value > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.", may be reported with the wrong number of bytes that could not be allocated. See KBA 2798900. |
| 817173 | In rare circumstances, a 16821 error, "Command UPDATE has been aborted because it cannot make unlogged changes to table ' < table-name > ' in database ' < database-name > ' while ONLINE REORG/CREATE INDEX is active on the table. ASE is terminating this process.", together with a stack trace which includes the modules 's_finish_cmd', 'xact_endupdate' and 'dodeferred' may be reported in the SAP ASE error log when an UPDATE command is run on an All Pages Locked table (APL) with clustered index and an ONLINE utility is running in parallel. |
| 817180 | In rare circumstances, a client connection using SSL may hang with the message, "ssl_nrpacket: vsn < value > kpid < value > bytesleft 0 iostatus 4 incomplete header", reported in the ASE error log. This message will henceforth be purely informational and will not indicate an error. See KBA 2748388. |
| 817191 | A 267 error, "Object ' < name > ' cannot be found.", may be reported when using global temporary table in a query and the global temporary table name exceeds 255 characters. |
| 817220 | Under rare circumstances, a spid involving remote I/O and the back trace of that spid using 'dbcc stacktrace( < spid > )' includes the module omni_ct_connect, usctconnect and ksctsuspend, may not hit timeslice error if there is any issues in the module ksctsuspend. |
| 817238 | The error, "SYBMULTBUF ERROR: Volume validation error: attempt to flush ' < filename > ' returned 22.", may be reported in the SAP Backup Server error log file when executing a LOAD command of a database that is created on raw partitions. This is a warning message that can be ignored. See KBA 2785313. |
| 817243 | The 632 error, "Attempt to move memory with an incorrect length of < size > . Maximum allowed length is < max_size > .", with state 2 does not provide diagnostic info. See KBA 2776092. |
| 817270 | When printing the "end of stack trace" message, incorrect suid was printed as a negative number when the suid is greater than 32K. The user's suid is 37029. "end of stack trace, spid 18125, kpid 1085497422, suid -28507". |
| 817271 | In rare circumstances, REORG REBUILD INDEX may hang due to latch self-deadlock if concurrent processes are splitting leaf pages of the same table while running REORG REBUILD INDEX on the same table. See KBA 2713796. |
| 817283 | A 2847 error, "The object < sp_xxx > is not a SQLJ function. If this is a SQL function, specify owner.objectname", and a 14216 error, "Function < sp_xxx > not found. If this is a SQLJ function or SQL function, use sp_help to check whether the object exists (sp_help may produce a large amount of output)", will be reported when attempting to access SQL UDFs residing in sybsystemprocs whose names begin with "sp_" from any other database. See KBA 2714003. |
| 817284 | In some circumstances, trailing spaces in a string may not be removed when inserting the string into a VARCHAR column via an Instead Of Trigger. |
| 817295 | Key words "Old Value:" and "New Value:" are now provided in audit tables for event 154 when audit option 'config_history' is enabled. See KBA 2746660. |
| 817366 | Trace flag 7817 is enhanced to make it possible to detect the rare occurrence when an attention acknowledgement is split across two TDS packets. Such occurrences are characterized by the message, "send_done: spid < id > vsn < no > acking attention with donestat 0x20", being followed by the message, "ussflush: spid < id > vsn < no > sending 16384 bytes with tds TDSEOM 0 under pending attention", where TDSEOM is 0 (rather than 1). |
| 817389 | A 3606 error, "Arithmetic overflow occurred.", may be reported while executing stored procedure sp_shrink 'database', < database name > , < device name > , < size > . See KBA 2767036. |
| 817400 | In rare circumstances, random failures with the message "current process infected with signal 11 (SIGSEGV)" together with a stack trace may be reported in the SAP ASE error log when SELECT queries were earlier executed with the reformat strategy applied and the reformat worktable had rows whose size was unexpectedly bigger than the current Adaptive Server configured page size. See KBA 2763915. |
| 817401 | Using KILL < spid > WITH FORCE on an idle process can result in the process remaining alive and reported by sp_who despite the connection is released. See KBA 2719233. |
| 817414 | In rare circumstances, DUMP DATABASE may fail with the error message "Backup Server: 4.145.2.22: [80] Error for database/archive device while working on stripe device ' < stripe name > '. Internal error: In rdr_xfer, the run list is too long." reported. See KBA 2929176. |
| 817422 | When using Procedure Deferred Compilation in conjunction with SQL Statement Replication, SQL statements whose compilation were deferred may be wrongly replicated, causing the DSI to go down with SQL syntax errors reported against the replicated database. See KBA 2719958. |
| 817424 | A 4623 error, "Error encountered while retrieving column information. Aborting grant/revoke command.", may be reported in the SAP ASE error log when the configuration option 'enable predicated privileges' is enabled and a SELECT from table variables is executed. See KBA 2720607. |
| 817431 | Update the SAP ASE integrated JREs to SAP JRE 8.1.046 and SAP JRE 7.1.060. |
| 817439 | KBA 2709213 - temp worktable not cleaned up in user temporary database (user tempdb) in ASE157 SP139 |
| 817472 | When a database is extended using asynchronous initialization and the new pages occupy a database range that has been asynchronously initialized before and later dropped using ALTER DATABASE OFF, some of the pages in the new fragment could remain uninitialized. |
| 817499 | DBCC ORPHANTABLES may falsely identify actively used temporary tables that are created inside a stored procedure as orphan tables. See KBA 2714936. |
| 817519 | A 17152 error, "The dump history file version is invalid.", may be reported when sp_dump_history is executed with any operation option if previously the end-user has purged dump history records from the dump history file by using the ‘delete’ operation option. |
| 817523 | SAP ASE may become unresponsive when an error is received on a network connection using SSL. See KBA 2746721. |
| 817525 | Audit records are not generated after a rpc login failure when the audit option 'rpc' is specified as 'fail' for a particular login. |
| 817535 | In rare circumstances, the message, "Invalid OAM page (OAMINVALID_1) stat 4: pageno= < value > , sdes_stat= < value > , pstat= < value > , dbid=5, etc.", together with a stack trace that includes the modules 'th_accounting', 'th_sleep_on_lct' and 'terminate_process', may be printed in the SAP ASE error log when a SELECT query that requires a work table to be created is killed. See KBA 2871745. |
| 817544 | In rare circumstances, the message, "A00: SYBMULTBUF ERROR: Failed to open database info file /tmp/SYB_BACKUP1095308512. Code=2, Message=No such file or directory" and "A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 16, error code=32, system message=Broken pipe.", may be reported in the SAP Backup server error log when a dump is taken. See KBA 2726662. |
| 817545 | The error message, "ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect", followed by a stack trace that includes the modules 'omni_exec_immediate', 'omni_sync_roles' and 'set_role', may be reported in the SAP ASE error log when executing SET ROLE REPLICATION_ROLE ON in the context of proxy objects. See KBA 2786327. |
| 817559 | In rare circumstances, the message, "Stack corrupted, server aborting.", together with a stack trace which includes the modules 'ubffreef', 'upunsetcritical' and 'upyield' may be reported in the SAP ASE error log while Adaptive Server releases memory and the diagserver binary is in use. |
| 817593 | The MDA table monDeviceSpaceUsage does not return any rows for database devices that are created on block device. See KBA 2728041 |
| 817594 | New backup server option 'enable_fips' added to support FIPS login password encryption. |
| 817598 | sybdiag fails to connect to an SSL enabled ASE server with message like "The Specified Interfaces file < interfaces_file > has an unknown format" or "JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s)" raised. See KBA 2727796. |
| 817606 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'metrics_proc_dump' together with a stack trace which includes the modules 'd_flushmetrics' and 'exec_dbcc', may be reported in the SAP ASE error log when executing sp_metrics 'flush' and the procedure cache is being cleaned up in parallel. See KBA 2730139. |
| 817619 | The message, "Security Control Layer's memory allocation routine returned an error.", and the message, "SCL error in function: sec_setup. Operation: sec_memalloc().", may be reported in the SAP ASE error log when the memory pool used for external authentication such as Kerberos becomes fragmented. See KBA 2732809. |
| 817620 | When LOAD TRANSACTION < database_name > WITH LISTONLY = LOAD_SQL is executed, SAP ASE may incorrectly report the option WITH PASSWD for a transaction dump that was dumped without password protection, if a subsequent transaction dump was taken with password protection. |
| 817622 | A 2514 error, "Table Corrupt: Type id 0 (type name = 0) does not match between systypes and syscolumns", will be reported falsely when running DBCC CHECKCATALOG for a database that has C-User Defined Functions created. See KBA 2729470. |
| 817629 | Under rare circumstances, a 1608 error, "A client process exited abnormally, or a network error was encountered" together with timeslice error followed by a stack trace which includes the module 'LopSubqAttach::GroupSimilarSubqNode' may be reported in the SAP ASE error log when a nested subquery is executed. See KBA 2727908. |
| 817680 | A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > .", may be reported during database encryption. See KBA 2761091. |
| 817682 | A 18302 error, "User < login name > is not a valid user in the < db name > database.", may be reported even when a user having sa_role executes the stored procedure sp_dbcc_faultreport. See KBA 2731983. |
| 817697 | In rare circumstances, it may be impossible to KILL a blocked process when the system tempdb log is full and tempdb is a mixed data and log database. See KBA 2734951. |
| 817734 | SQL statement replication involving quoted identifiers may cause the SAP SRS DSI to shut down after receiving an SAP ASE error indicating a syntax error, or after hitting SAP SRS error 5186, "Row count mismatch for the SQL Statement Replication command executed on ' < servername > . < dbname > '.". See KBA 2721403. |
| 817736 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeTableFunctionOp::copyInParam' followed by a stack trace that includes the modules 'LeTableFunctionOp::_LeOpOpen', 'LeOperator::LeOpOpen' and 'LeNLJOp::_LeOpNext', may be reported in the SAP ASE error log when selecting from a table-valued UDF with column and constant parameters. See KBA 2843589. |
| 817750 | In rare circumstances, the message, "The bit for alloc page < value > in database < number > is clear. It should be set.", may be reported when DBCC GAM is executed. See KBA 2733631. |
| 817752 | Under rare circumstances in an HADR setup, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, this may prevent some data from being replicated which will be replicated upon Rep Agent restart. The message, "(CI-Info) Message: 1001, Severity: 0 ( < dbname > )MSProdReceiver: notify client consumer is down strm < address > ...", will be reported in the ASE error log, but will not be followed by an expected 9414 error, "RepAgent( < dbid > ): Streaming replication stream CI Library error error -1 with severity 2 and message 'Producer receiver ' < dbname > ’' failed to receive data, shutting down transport to ‘ocs:host:port'.'. Rep Agent detected error 3 with message 'Unknown' at line 0 in file nofilename.". See KBA 2879595. |
| 817770 | The message, "Backup Server: 4.142.2.90: [0] The 'sem_open' call failed with error number 17 (File exists). Refer to your operating system documentation for further details.", may be reported in the ASE Backup Server error log when "backupserver -help" is executed multiple times. See KBA 2837680. |
| 817816 | In rare circumstances, some data may not be recovered correctly after LOAD TRANSACTION WITH UNTIL_TIME in an IMRS enabled database is executed while significant IMRS activity is taking place. |
| 817834 | A 1028 error, "Failed to apply the top operator 'nl_join'", may be reported when an UPDATE query involving a remote table with a join condition on the update column is executed. See KBA 2736509. |
| 817835 | The message, "Assertion (unassigned_space == 0) failed", together with a stack trace which includes the module 'lddb__map_segments_and_holes' and 'ldx__loadlog' may be reported in the SAP ASE error log when an IMRS-enabled database, which had earlier been altered to modify data segment size while the diagserver binary is in use, is loaded back using the database and transaction dumps. See KBA 2750483. |
| 817868 | In rare circumstances, DUMP DATABASE or DUMP TRANSACTION will sleep indefinitely when sp_dump_history is run with the 'purge' option at the exact same time as the DUMP and the configuration parameter 'enable dump history' is enabled. See KBA 2737615. |
| 817869 | In rare circumstances, a 102 error, "Incorrect syntax near ';'.", followed by a 111 error, "CREATE PROCEDURE must be the first command in a query batch.", and a 156 error, "Incorrect syntax near the keyword 'END'.", may be reported when CREATE PROCEDURE is executed and the stored procedure text includes a large number of invisible[*] characters. See KBA 2716155. |
| 817925 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mda__get_procedure_schemas' together with a stack trace which includes the modules 'mda_populate_monCachedProcedures' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on the MDA table monCachedProcedures is executed. See KBA 2755225 |
| 817933 | On Windows platforms, the message, "java.io.FileNotFoundException: < pca_jvm_tmp_dir > \ < file_name > (Access is denied)", together with a Java stack trace may be reported when the IO operations are performed with Java IO API and the configured pca_jvm_tmp_dir is not accessible. |
| 817954 | A 11307 error, "The object ' < object_ID > ' in database ' < database_ID > ' is not a valid parameter for the built-in function logschema(). The object must be a user table or a stored procedure.", may be reported in the SAP ASE error log when DDL replication is enabled, and a table type is being dropped. See KBA 2786860. |
| 817964 | A 11060 error, "This statement has exceeded the maximum number of recompilations (20). This indicates an internal error. Please note the error prior to this one and contact SAP Technical Support.", may be reported during the execution of a SELECT query that references a view with tables that were dropped, re-created, or altered. See KBA 2791952. |
| 817974 | If the configuration parameter "enable concurrent dump tran" is set to 1, SAP ASE may allow a transaction dump to be loaded on top of the wrong full database dump, if it was generated concurrently with it, and the transaction dump ends between the time the full database dump started and the dump instant time was taken. Alternatively, a 4305 error, "Specified dump file ' < filename > ' is out of sequence.", may be incorrectly reported when trying to load a transaction dump generated after the concurrent transaction dump finished. (KBA 2991124) |
| 818006 | A 12834 error, "The login name ' < login_name > ' is invalid. The LDAP subsystem reported error '(license ASE_DIRS is not enabled)'." may be reported when executing the stored procedure sp_ldapadmin 'check_login', ' < login_name > ' while the configuration option 'enable ldap user auth' is disabled and a valid ASE_DIRS license exists. See KBA 2742137. |
| 818014 | A 632 error, "Attempt to move memory with an incorrect length of < N > . Maximum allowed length is 16384.", may be reported in the SAP ASE error log when executing an remote procedure call against a HANA backend server. |
| 818020 | KBA 2752182 - In rare circumstances, the message, "Failed to execute the threshold procedure for database < dbid > , segment 2, free space < num > ." or the message, "Failed to find specified threshold in threshold cache on instance 1 for database mld ( < dbid > ), segment 2, free space < num > . Use 'dbcc thresholds' to see the threshold cache contents.", may be printed in the SAP ASE error log when multiple tasks hit the threshold at the same time. This mainly happens for mixed log/data databases. |
| 818064 | In rare circumstances, the message, "imrslogrec_fix_lastlog: getpage_noscan failed to get last page: < pagenum > for database imrsdb1 ( < dbid > )", may be reported in the SAP ASE error following a failure of ONLINE DATABASE if a transaction dump is loaded which contains only one transaction in such a way that its ENDXACT falls on a different page than the BEGINXACT and the last page is partially flushed. |
| 818065 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'prObject_list' together with a stack trace which includes the modules 'showplan' and 'exec_lava' may be reported in the SAP ASE error log when sp_showplan is executed. See KBA 2743737. |
| 818080 | Improve the performance of recovery redo pass phase in SAP Adaptive Server when open transactions with many log records had to be redone during boot recovery. See KBA 2817693. |
| 818084 | A 6701 error, “Could not open dbid < value > , object id < value > .”, may be reported followed by an implicit transaction abort, during a Business Suite zero-downtime upgrade which prevents the upgrade from succeeding. |
| 818102 | In a HADR system, under rare circumstances, when the primary host is shut down or the network on primary host is down, an unplanned failover could take a long time. |
| 818109 | Tables in the database may wrongly become row caching/ MVCC or ODMVCC enabled when the ALTER DATABASE commands "ALTER DATABASE < dbname > set ROW CACHING ON FOR ALL TABLES", "ALTER DATABASE < dbname > set SNAPSHOT ISOLATION ON FOR ALL TABLES" or "ALTER DATABASE < dbname > set SNAPSHOT ISOLATION ON USING VERSION STORAGE FOR ALL TABLES" is executed without associating IMRSLOG or VERSION STORAGE with the database. See KBA 2750515. |
| 818137 | A 4346 error, "ASE cannot load a delta transaction log onto a database that is logically smaller ( < value > physical pages, < value > logical pages) than the source database( < value > physical pages, < value > logical pages). Recreate the database < name > with at least < value > physical log pages.", may be reported incorrectly due to an invalid pointer parameter value during LOAD TRANSACTION. See KBA 2882962. |
| 818168 | A 1526 error, "Sort failure. The configure size for data cache ( < name > ) is not sufficient to handle the sort buffers ( < value > ) requested. Please reconfigure the data cache or sort buffers and try the command again.", may be reported during the execution of a query with a non-unique state value which prevents us to identify the root cause of the error. See KBA 2748397. |
| 818206 | The error, "Backup Server: 9.1.2.4: Unable to open configuration file ' < ASE-directory > /defaultbs.cfg'. Operating system error 13.", will be raised and the Backup Server will not boot if the Backup Server is started without specifying a configuration file and the file defaultbs.cfg in the SAP ASE directory is not readable. See KBA 2900667. |
| 818208 | In an HADR environment, the replication of a DDL command using quoted identifiers and executed in a non-replicated stored procedure may cause the SRS DSI to shutdown after receiving a syntax error from the replicate ASE. |
| 818231 | In rare circumstances, using the 'setLong' method in a PreparedStatement may result in an incorrect value being assigned to a BIGINT datatype when the Java code is executed inside SAP ASE using the SAP ASE's internal sybase.asejdbc.ASEDriver driver. See KBA 2748353 |
| 818245 | A 7625 error, "Audit table number ' < value > ' is invalid." with state 3, prints a incorrect value for the audit table number. See KBA 2751731. |
| 818246 | INSERT and DELETE permission is granted to Public for table syb_auto_db_extend_control via the installdbextend script. |
| 818253 | Feature enhancement to allow ASE to LOAD backup archives that were DUMPed using the Backup Server API without needing to use the Backup Server API for the LOAD operation. See KBA 2786342. |
| 818264 | A stored procedure which uses multiple IF, ELSE, or WHILE clauses to conditionally execute DML statements may have the stored procedure text incorrectly saved in syscomments. See KBA 2749949. |
| 818266 | The message "Engine ( < number > ) not online, Not going to Push affinity in [function] at line xxxx" may be reported in the SAP ASE error log when the configuration option "kernel mode" is set to threaded mode. These messages can be ignored. See KBA 2751782. |
| 818291 | Error message reporting into the SAP ASE error log when SSL connections are being established has been improved. |
| 818299 | A 10353 error, "You must have any of the following role(s) to execute this command/procedure: 'sybase_ts_role'. Please contact a user with the appropriate role for help.", will be reported when sp_config_rep_agent is executed which results in the failure to log the RepAgent configuration change to the SAP ASE error log. This error will cause the SRS DSI connection to shut down as this error is mapped to STOP_REPLICATION action. |
| 818302 | In rare circumstances on a heavily-loaded multi-engine system, high contention on the database spinlock (rdbt_spin) may be seen during the execution of a large number of cross-database queries. See KBA 2776093. |
| 818311 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module ‘mbkt_do_alloc’ together with a stack trace which includes the modules ‘js__queue_jobid’ and ‘js_wakeup’ may be reported in the SAP ASE error log when multiple requests to start the job scheduler are made simultaneously. See KBA 2787012. |
| 818321 | The message, "FATAL UNHANDLED EXCEPTION: signal < number > hit while handling a previously hit signal. The server cannot continue and will shut down.", may be reported in the SAP ASE log when an external signal is send to ASE e.g. via O/S kill command. See KBA 2682383. |
| 818324 | Under rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'kstcpnetctlrNcheckQuit' together with a stack trace which includes the modules 'ncheck_checksocket' and 'krtctskException' may be reported in the SAP ASE error log and SAP ASE may become unresponsive. See KBA 2757868 |
| 818327 | On heavily loaded systems, spinlock contention on SSQLCACHE_SPIN may be observed on statement cache when a prepared statement performing INSERT statements with numeric datatypes (or similar) are present and the option DYNAMIC_PREPARE is set to FALSE. SAP KBA 2770344 |
| 818344 | Add "Warning:" before the text for error message 10828. The new message is "Warning: Consider increasing the value of configuration parameter 'max memory' or decreasing the value of configuration parameters causing significant memory consumption, such as 'number of user connections'." |
| 818346 | The execution of sp_dump_history may leave behind tables in the system tempdb database if the connection gets terminated abnormally, which will require an explicit manual drop of these tables by the end-user. See KBA 2753062. |
| 818362 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'cudf_start_query' together with a stack trace which includes the modules 'curs_fetch' and 'get_datachange' may be reported in the SAP ASE error log when a query with the built-in datachange() is executed via a JDBC connection. This error may result in the SAP ASE shutting down. See KBA 2756423 |
| 818373 | Under rare circumstances, a 12583 error, "Unable to log a record in database < name > (id < value > ) due to internal error -8.", may be reported when a session that is writing log records is killed with the WITH FORCE option. See KBA 2790981. |
| 818394 | The message, "Assertion (!(USER_TABLE_OBJ(SDES_DES(sdes))) || !(sdes- > sread_sdes) || SDES_DEF_OP_LOCK_HELD(sdes- > sread_sdes))", together with a stack trace which includes the modules 'xact_endupdate’ and 'dodeferred’ may be reported in the SAP ASE error log when an UPDATE on a compressed table is executed and the diagserver binary is in use. |
| 818408 | Under rare circumstances dump and load database may hang when using multiple stripes on Windows platforms. |
| 818438 | sp_shmdumpconfig reports incorrect numbers for Data Caches & Server Memory fields. It adds half the combined Data Caches size to Server Memory field. See KBA 2755150. |
| 818469 | A 4325 error, "The specified recovery date ( < value > ) is not between the start ( < value2 > ) and end ( < value3 > ) date.", may be reported when LOAD TRANSACTION WITH UNTIL_TIME= < Point_In_Time_Recovery > is executed and the transaction dump when taken has a dump instant value that is later than the specified PITR value. |
| 818484 | A new parameter, 'host_public_ip', has been introduced in the resource file of setuphadr, which can cab be set to the public IP address of the host. If this parameter is set, then RMA will use this address to connect to the host. |
| 818504 | In rare circumstances, Adaptive Server processes may wait for a long time for DUMP DATABASE to complete, when the database size is big and there are many concurrent commands running that either perform non logged updates, like SELECT INTO, or logical log records updates, like CREATE INDEX. See KBA 2776030. |
| 818523 | In rare circumstances, Adaptive Server may perform wrong memory deallocations when a cursor query that involves the built-in datachange() is executed and XML monitoring is enabled. This may cause errors reporting incorrect accounting between allocated and deallocated memory pages and sometimes may result in the session terminated with a stack trace reported in the SAP ASE error log. See KBA 2756423. |
| 818524 | On Windows platforms, the error, "'CreateFile' call failed for database/archive device while working on stripe device < number > (The system cannot find the file specified)", may be reported when executing a DUMP command on a shared network folder using the Universal Naming Convention (UNC). See KBA 2751605. |
| 818538 | In rare circumstances, a process may run into a self-deadlock with the message, "Killing spid: < value > will not be immediate because it is waiting for a latch held by spid: < value > .", reported in the SAP ASE error log upon a KILL. This process was attempting to create a temporary table but was waiting for an allocation page lock which was held by another process. See KBA 2789764. |
| 818566 | The index to be used as the primary key for replication can be forced manually to a non-unique index with the new 'force' option of the system stored procedure sp_setreppk which has the following usage: sp_setreppk table_name[, index_name[, 'force']]. |
| 818593 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'OptGlobal::GblOptimize' together with a stack trace may be reported in the SAP ASE error log during the compilation phase of a stored procedure execution. See KBA 2946919. |
| 818594 | In rare circumstances, the message, "current process infected with 11 (SIGSEGV)", either in the module 'sort' or 'solm' together with a stack trace may be reported in the SAP ASE error log during the execution of a query that requires a sort operation. |
| 818603 | In rare circumstances, a memory leak of 41 bytes may happen when the Backup Server fails to open an archive device for write, either because it is not writable or because the volume has an expiration date, if the end-user responds using the sp_volchanged stored procedure with the 'RETRY' option. |
| 818611 | SAP ASE may choose a non-performant query plan execution when a query with a ROWS LIMIT/OFFSET clause using a MAXINT value is executed. See SAP Note 2783751. |
| 818627 | In rare circumstances, following a 1204 error, "ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.", queries or built-ins execution on SYSLOGINS may hang. See KBA 2763234. |
| 818632 | The message "current process infected with signal 11 (SIGSEGV)" in the module 'LeRun' followed by a stack trace that includes the modules 'LeEvals::LeEvRun', 'LeRestrictOp::_LeOpOpen' and 'LeScalarAggOp::_LeOpOpen', may be reported in the SAP ASE error log when a prepared statement has parameter markers as an operand in CASE search condition. SAP KBA 2762616 |
| 818642 | When running in an HADR environment, ASE may incur SIGILL in function sybnet__flt_init() on standby during setuphadr on AIX platform. See KBA 2876868. |
| 818665 | In some circumstances, a 3703 error, "Cannot drop the trigger with object-id < objid > in database < dbid > , because it doesn't exist in the system catalogs.", may be raised when dropping a view if CREATE OR REPLACE TRIGGER with INSTEAD OF option was previously executed on the view. See KBA 2764599 |
| 818666 | The message "system exception generated by a storage access violation" in the module 'omni_parse_name_using_optional_bracket' together with a stack trace which includes the modules 'tmp_dropto' and 's_normalize' may be reported in the SAP ASE error log when failing to create a stored procedure that references a global temporary table due to an error that is not related to the global temporary table. See KBA 2764590. |
| 818671 | In rare circumstance, a significant increase of CPU time is seen for table scans on tables which have data compression enabled when the number of concurrent scan tasks increases. |
| 818684 | The message "TaskReplication.runTask(): SetupReplicationTask time out." may appear during setuphadr when high number of databases are involved. A new environment variable, 'SETUP_SRS_TIMEOUT' and 'MATERIALIZE_DB_TIMEOUT', has been introduced, which can be used to set the timeout value in seconds, for setting up replication and materializing databases, respectively. See KBA 2776399 "Unable to materialize large ASE Database with sap_materialize auto". |
| 818693 | In rare circumstances, a 2714 error, "There is already an object named '# < temp_table_name > ' in the database.", may be reported by Adaptive Server when CREATE TABLE is run in order to create a temporary table which is already dropped. See KBA 2816676. |
| 818707 | In rare circumstances, a 3606 error, "Arithmetic overflow occurred.", may be reported when sp_helpdb is run after database shrink operations took place and one of the de-activated devices had a size that is larger than 4294967295. See KBA 2766504. |
| 818713 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'sqlexc_intercept_exception' together with a stack trace may be reported in the SAP ASE error log when view redefinition happens. See KBA 2771076. |
| 818714 | The message, "The used count in IMOAM Page < page# > is -1 and it does not match to the expected number 0.", may be reported when DBCC TABLEALLOC is run on an IMRS enabled table. |
| 818724 | A 3606 error, "Arithmetic overflow occurred.", may be reported while executing stored procedure sp_shrink 'device', < device name > , < size > . See KBA 2767036. |
| 818728 | Under rare circumstances in an HADR setup that has an IMRS database enabled, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, there is a small window which may cause data loss as DML commands are sent to Replication Server after their commit and will be incorrectly ignored. |
| 818730 | On certain platforms like HPIA, Adaptive Server may report a 8522 error, "Warning: Invalid location < location-number > found in database ' < database-name > ' for the fragment starting at logical page < page-number > . Execute DBCC CHECKCATALOG( < database-name > , fix) to fix it.", even after having executed DBCC CHECKCATALOG( < database-name > , fix) command. |
| 818734 | On Big-Endian platforms, setting a Backup Server configuration option to the same value it already has, will create a new configuration file identical to the previous one instead of displaying a message indicating that the value has not changed. |
| 818746 | Under rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'dso_resgov_timlim' may be reported in the SAP ASE error log when a task disconnects at the same moment a limit is crossed and the limit action is enforced. SAP KBA 2767573. |
| 818778 | In rare circumstances, a 9502 error "string data right truncated" may be raised when applications using parameterized prepared statement with dynamic SQL that uses a LIKE clause in its query over a univarchar column and statement cache is ON. See KBA 2779052. |
| 818784 | A 7928 error, "Index < name > is not consistent; found < number > leaf rows but < number > data rows.", may be reported when LOAD TRANSACTION WITH UNTIL_TIME is executed on an IMRS enabled database. |
| 818803 | In rare circumstances, the execution of a SELECT query that is using MINUS or INTERSECT operators and involves views or derived tables may return incorrect results. See KBA 2769807. |
| 818805 | In rare circumstances, the message, "The value of the 'max memory' parameter ( < value > ) defined in the configuration file is not high enough to set the other parameter values specified in the configuration file. 'max memory' should be greater than the 'total logical memory' ' < value > '.", may be unexpectedly reported in the SAP ASE error log during Adaptive Server startup. See KBA 2769883. |
| 818812 | In some circumstances, query using compressed index may not return all qualified data rows on data-only locked tables. See KBA 2803119. |
| 818818 | In rare circumstances, ASE may report high values for QueryOptimizationTime on monProcessActivity MDA table that may be higher than the elapsed time since the server gets started. See KBA 2770233. |
| 818824 | The message, "No resources to allocate TH_FREESPACE_DIAG for database < dbid > . Freespace accounting information cannot be shown.", may be reported in the SAP ASE error log when LOAD DATABASE, LOAD TRANSACTION or ONLINE DATABASE is executed. See KBA 2769024. |
| 818828 | A 3602 error, “Transaction has been rolled back.”, may be reported when performing DML commands on a table that once had trigger with multiple actions created for the table and the same trigger have been dropped. See KBA 2771427. |
| 818852 | A 10795 error, "The file ' < xx > .class' contained in the jar does not represent a valid Java class file" may be reported while install the jar file in ASE database. See KBA 2790939. |
| 818856 | A 9219 error, "RepAgent( < database-id > ): Internal error.", followed by a 9416 error, "Rep Agent on database ' < database-name > ' switched from mode ‘sync’ to mode 'async' because < reason-for-switching > ”, may be reported in SAP ASE error log under an HADR setup when RepAgent is being stopped or has run into error with message, "Current transaction ID ( < page# > , < row# > ) in database ‘ < database-name > ' (dbid = < database-id > ): commit wait expired.'”. See KBA 2850255. |
| 818875 | Using the --show-master-version switch with dataserver or sqlsrvr.exe results in a segmentation fault. See KBA 2773633. |
| 818885 | When running sp_sysmon using the appl or appl_and_login option, the application or application- > login section reports inaccurate Disk and Network I/Os when there are multiple sessions with the same application or application- > login pairing. See KBA 2776095. |
| 818891 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'oh_copy' and 'oh_dup', may be reported in the SAP ASE error log when When creating login within IF-ELSE with auditing enabled. See KBA 2843548. |
| 818953 | The message "ELC_VALIDATION_ERROR: Page address not aligned to memory page size.", followed by "Current process infected with signal 11 (SIGSEGV)" in the module 'subp' together with a stack trace which includes the modules 's_execsetvar' and 'subparams' may be reported in the SAP ASE error log when prepared INSERT statements are executed. See KBA 2774710. |
| 818957 | A 2753 error may be raised on an ASE where Japanese language is installed if "enable monitoring" and "plan text pipe active" configuration parameter are 1 or showplan is enabled for a complex query. See KBA 2777310. |
| 818971 | The message "Current process infected with 11 (SIGSEGV)" in the module 'proc_setdb' together with a stacktrace which includes the modules 's_getTreeOrPlan' and 'kw_exec' may be reported in the SAP ASE error log when DBCC CHECKSTORAGE is run on a database with many partitioned tables and the values for the configuration options 'number of open objects', 'number of open indexes' and 'number of open partitions' are not enough established. See KBA 2785031. |
| 818972 | The message "current process infected with 11" in the module 'lt_run' together with a stack trace which includes the modules 'lt_send_row', 'mda_populate_monMemoryUsage', 'mdarpc_exec' and 'execrpc' may be reported in the error log when the monMemoryUsage MDA table is queried remotely as an RPC for a proxy table. See KBA 2781904. |
| 818978 | A 7124 error, "The offset and length specified in the READTEXT command is greater than the actual data length of < value > ." may be reported when running "readtext" with the "size" or "offset" parameter datatype different than integer. See KBA 2778603. |
| 819011 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'prSQLTEXT' may be reported in the SAP ASE error log when running DBCC SQLTEXT on a spid executing a cursor which has been marked as a zombie. See KBA 2780164. |
| 819016 | In rare circumstances under an HADR setup the ASE Replication Agent may shut down after reporting a 9415 error, "RepAgent( < dbid > ): Warning: The size of the stream buffer is too small ( < size > bytes). Use sp_config_rep_agent ' < dbname > ', 'stream buffer size', ' < new_value > ' to increase it.". Additionally a CI Library error message indicating the failure of a CI API call is reported in the SAP ASE error log. See KBA 2890740. |
| 819070 | The message, "current process infected with 11 (SIGSEGV)" in the module 'getnext' together with a stack trace which includes the modules 'upgd__add_table_anchors' and 'upgd_upgrade_db' may be reported in the SAP error log during ONLINE DATABASE while an internal upgrade is run as the database dump was taken on a previous ASE release and a different platform. See KBA 2786974. |
| 819132 | The message "timeslice -501, current process infected" in the module 'exc_raise' together with a stack trace which includes the modules 'loginfo_get' and 'loginfo_builtin' may be reported in the SAP ASE error log when the built-in loginfo( < dbid > , 'inactive_pages') is executed on a mixed-log-and-data database. See KBA 2747600. |
| 819178 | Under rare circumstances, in a HADR setup, when the primary Adaptive Server is rebooted, it may start as standby and the message, "WARNING: split brain check refused to allow this server to become Primary", along with the message, "remote HADR server < server-name > is STANDBY, but configured for PRIMARY", may be reported in the SAP ASE error log. See KBA 2890707. |
| 819179 | A 3375 error, "Unable to drop global temporary table < name > as it is in use", may be reported when a global temporary table is dropped and is used concurrently by another session. See KBA 2787484. |
| 819185 | A 3624 error, "Truncation error occurred", is raised with severity 10 (warning) instead of severity 16 (error) when DYNAMIC PREPARE is set to FALSE for batch processing (language batch param) and the client tries to INSERT a numeric which is out of scale. |
| 819187 | In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module ‘kstcpnetctlrCancelRequests’ together with a stack trace may be reported in the SAP ASE error log. If shared memory dump is configured for signal 11, then ASE may hang. See KBA 2786903. |
| 819188 | In rare circumstances, Adaptive Server may incorrectly create the in-lined version of a Table Valued User Defined Function (TUDF). As a result a 207 error, “Invalid column name < name > .”, may be reported during the execution of a query which references this TUDF. |
| 819212 | A 632 error, "Attempt to move memory with an incorrect length of -xxx. Maximum allowed length is 16384", may be reported when executing CREATE LOGIN command followed by the execution of a stored procedure which contains SELECT query while auditing is enabled. See KBA 2788657. |
| 819216 | Workload Analyzer fails to identify requests that are cancelled by either TDS_BUT_ATTN token or OOB data. All these requests will have "Finished" state instead of "Cancelled" state in dashboard. See KBA 2803118. |
| 819222 | The reserved_pages value reported by 'sp_spaceused syslogs' keeps growing when the database option 'delayed commit' is enabled. See KBA 2747756. |
| 819224 | The message "current process infected with signal 8 (SIGFPE)" in the module 'proc_setdb' together with a stack trace which includes the modules 's_getTreeOrPlan', 'attachrule' and 's_compile' may be reported in the error log. See KBA 2593370. |
| 819230 | In rare circumstance, 9952 error, "Workspace < string > is too small to permit the CHECKSTORAGE operation to proceed. Use sp_dbcc_alterws and sp_dbcc_updateconfig to correct the problem", may be reported when running DBCC CHECKSTORAGE() on a very large database with a large scan workspace (whose size is greater than 80G) configured. See KBA 2025063. |
| 819231 | Under rare circumstances, the message "Volume validation error: attempt to open < ASE_devicename > returned No such file or directory", may be reported on a Solaris platform during the execution of a DUMP command when the Backup Server received a SIGPOLL signal while attempting to open an ASE device. See KBA 2774930. |
| 819237 | In rare circumstance, an outer join query may return a wrong result when a SQL UDF is used in the WHERE clause and the SQL UDF's parameter is passed in as a column name but not a variable. See KBA 2791388 |
| 819242 | The message, "current process infected with 10 (SIGBUS)", in the module 'LeOperator::LeOpSaveIOStats' together with a stack trace which includes the modules 'LeRetnCode LeDMLOp::_LeOpClose' and 'exec_lava' may be reported in the SAP ASE error log during the execution of a query when the statement cache is incoherent which can lead to Adaptive Server shutting down implicitly. See KBA 2405522. |
| 819246 | Attempt to execute the command "alter encryption key dual master [..] modify encryption with external key" incorrectly raising error 2941 instead of error 2947 which indicates the dual master can only be encrypted by user password. See KBA 2790961. |
| 819247 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memmove' together with a stack trace which includes the module 'bt__getrestartkey' may be reported in the SAP ASE error log when UPDATE STATISTICS is being run while DML commands are concurrently executed on the same table. See KBA 2792088. |
| 819260 | A 911 error, "Attempt to locate entry in sysdatabases for database '' by name failed - no entry found under that name. Make sure that name is entered properly.", may be reported when a prepared statement issuing CHECKPOINT < database_name > is executed. See KBA 2791971. |
| 819273 | SAP Adaptive Server dataserver process leaks O/S memory when the built-in xmlextract() is executed. See KBA 2806756. |
| 819285 | When the environment variable MALLOC_CHECK_ is set to 2 the Backupserver will receive a SIGABRT signal during the cleanup phase of any connection established with Adaptive Server. This will result in the Backupserver process dyeing and a manual restart is required. This behavior is the result from the fix made in CR 699826 for 16.0 SP03 PL07, "Allow DUMP and LOAD of an in-memory database when using single-sign-on authentication mechanisms, like Kerberos. See KBA 2754515.", which fix we are backing out until the root cause is identified and fixed. |
| 819302 | The upgrade items for zeroing the columns 'imrslogptr' and 'imrsloglastptr' in table 'master.dbo.sysdatabases' and the column 'schemaid' in table 'sybsecurity.dbo.systypes' may be missed when upgrading an Adaptive Server installation from 16.0 SP02 PL07 or 16.0 SP02 PL08 to 16.0 SP03 PLxx. |
| 819308 | In rare circumstances, a 2620 error, “The offset of the row number at offset < value > does not match the entry in the offset table of the following page: Page pointer = < value > , pageno = < value > , etc.”, together with a stack trace which includes the modules ‘update’ and ‘putdrow’ may be reported in the SAP ASE error log during a DML execution on an All Pages Locked (APL) table when one or more previous UPDATE command(s) were executed in deferred mode. See KBA 2838778. |
| 819317 | A 3775 error, "Unable to drop global temporary table < name > as it is in use", may be reported during the DROP of a global temporary table due to the presence of an orphan instance of the global temporary table. See KBA 2794963. |
| 819323 | In a HADR setup, if the 'setuphadr' script is run multiple times on the third (DR) node and the RMA is running, then the HADR setup is teared down. |
| 819329 | In rare circumstances the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'd_orphantables' together with a stack trace which includes the modules 'exec_dbcc' and 's_execute' may be reported in the SAP ASE error log when running DBCC ORPHANTABLES with the option 'drop' to delete an orphan temporary table. See KBA 2795213. |
| 819340 | In rare circumstances, a 834 error with state 3, "Illegal attempt to change contents of buffer: ...", in the module ‘buffree’ together with a stack trace which includes the modules ‘buf_elcsearch’ and 'bt_delete' may be reported in the SAP ASE error log during the execution of a DML query while the buffer is being de-allocated and another session is in the process of changing it. See KBA 2869028. |
| 819347 | In rare circumstances the message, "Adaptive Server Enterprise system exception < value > generated by a storage access violation.", in the module 'omni_parse_name_using_optional_bracket' together with a stack trace which includes the modules 'tmp_drop_globaltt' and 's_free' may be reported in the SAP ASE error log when a user session disconnects and an attempt to drop active global temporary tables fails. See KBA 2902143. |
| 819388 | In rare circumstances, SAP Adaptive Server may not shutdown when the SHUTDOWN command is executed or when shutdown from the Windows Service. The module 'shutdownjobscheduler’ will be reported by DBCC STACKTRACE on the session executing the SHUTDOWN command or the SHUTDOWN HANDLER task. See KBA 2797851. |
| 819401 | The 'histogram_tuning_factor' parameter of UPDATE STATISTICS command doesn't take effect for partitioned tables when it is different from the Adaptive Server configuration option 'histogram tuning factor' value. See KBA 2662968 |
| 819412 | In rare circumstances, a 3328 error, "Redo of 'CREATE INDEX' in transaction ID ( < page# > , < row# > ) for table name < objname > , object ID < objid > did not find 'syscolumns' system catalog log record. Recovery of database < dbname > cannot continue.", may be raised during LOAD TRANSACTION recovery when before the index creation the table had a non-materialized column with a constant default value and some other column of the table was dropped with 'no datacopy' option. |
| 819416 | In rare circumstances, the message, "current process infected with 11 (SIGSEGV)", in the module 'fg_lock' or 'sendtext' together with a stack trace may be reported in the SAP ASE error log during the execution of a query which accesses LOB data. See KBA 2878406. |
| 819437 | A 12324 error, "In database < name > , the server failed to open required table 'SYSPARTITIONS'. Please contact SAP Technical Support.", may be reported when a full database dump is loaded on a database that is marked as suspect due to a previously hit 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < value > , object id = < value > , page timestamp= < value > . Log old timestamp= < value > . Log record marker = ( < value > ). Transaction ID = ( < value > ).". See KBA 2808901. |
| 819439 | Under rare circumstances in an HADR setup with DRC enabled, if the connection between SAP ASE Rep Agent and SAP Replication Server is down and up again, this may prevent some data from being replicated which will be replicated upon Rep Agent restart. The message, "RepAgent( < db_id > ):Streaming replication stream CI Library error -1 with severity 2 and message 'Producer of Stream 'ERP_2' failed to send a message with < message length > -bytes.'. Rep Agent detected error 213 with message 'CI API call to SendMsgs() failed ' at line < line number > in file ra_ci_interf.c." will be reported in the ASE error log, but will not be followed by the other similar message "RepAgent( < db_id > ): Streaming replication stream CI Library error ...". See KBA 2808878. |
| 819443 | In rare circumstances, SAP Adaptive Server may ignore predicates when an outer join query is executed using a merge join with a hash union scan on an empty inner table, which can result to wrong results. See KBA 2850224 |
| 819452 | A 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < page-number > , object id = < object-id > , page timestamp= < page-timestamp > . Log old timestamp= < log-old-timestamp > . Log record marker = ( < page-number, row-number > ). Transaction ID = ( < page-number, row-number > ).", may be reported in the SAP ASE error log during LOAD TRANSACTION when either trace flag 1773 or 1774 is enabled to defer the recovery of indices at online time respectively in automatic or manual mode. |
| 819468 | When the configuration option 'enable granular permissions' is set, a user that is aliased to dbo in the master database is aliased to dbo in all databases. See KBA 2795960. |
| 819479 | The message "current process infected with 11 (SIGSEGV)" in the module 'LePipeRWState::_LePrwsWriteConstant' together with a stack trace which includes the modules 'LeExecuteWorkUnits' and 'LavaThreadDriver' may be reported in the SAP ASE error log when a SELECT query is executed in parallel. See KBA 2694998. |
| 819493 | A 247 error, "Arithmetic overflow during explicit conversion of FLOAT value ' < value > ' to a NUMERIC field" may be reported when executing sp_helpcache or manually querying the syscacheinfo or syscachepoolinfo view on the system that configures very large caches. See KBA 2402812 |
| 819500 | Under rare circumstances, on a heavily-loaded multi-engine SAP ASE, the 'Operations' column in monOpenObjectActivity MDA table might get wrapped in a short time. |
| 819522 | In some scenarios, using SQL-batch in chained mode which includes the queries "select into #temp" and "drop table #temp" may leave behind an orphan #temp table. See KBA 2805819. |
| 819523 | A 2901 error, "Exception stack limit exceeded", followed by a rolled back transaction, may be reported in the SAP ASE error log when executing "dbcc upgrade_object(dbname, 'procedure', 'check')" on AIX platform. See KBA 2805876. |
| 819536 | In rare circumstances, the message, "Assertion (mutex- > lockcount == 0) failed" may be reported in the SAP Backupserver error log when a DUMP command is executed and the diagserver binary is in use. See KBA 2871713. |
| 819538 | jConnect applications may fail with the message, ‘java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).’, reported when SAP ASE is configured with MIT Kerberos and charset conversion is not available between Adaptive Server and jConnect charsets in use. See KBA 2807020. |
| 819540 | The message "current process infected with 11 (SIGSEGV)" in the module 'dbt_kept_by_pss' together with a stack trace which includes the modules 'dbs_shutdown' and 'dbs_dbreboot' may be reported in the SAP ASE error log when DBCC DBREBOOT with option 'shutdown_load' is executed. See KBA 2807357. |
| 819553 | A 12308 error, "Internal error : Invalid row id (Row < row-number > , Page < page-number > ) encountered in the table 'syscolumns' in database ' < database-name > '.", may be reported in the SAP ASE error log when high concurrent activity is taking place in a user defined temporary database. See KBA 2808782. |
| 819559 | The message, "timeslice < value > , current process infected at < value > ", in the module 'pthread_cond_timedwait' together with a stack trace which includes the modules 'MSOCSSendMsg' and 'ct_results', may be reported in the SAP ASE error log when the connection between SAP ASE Rep Agent and SAP Replication Server is down and synchronous stream replication is enabled in an HADR setup. See KBA 2807757. |
| 819560 | In rare circumstances, SAP ASE Rep Agent hangs on startup in an HADR setup due to a previous abnormal termination following a time slice error encountered. The call stack of the Rep Agent task will report the module 'upyield' followed by the modules 'ra_ci_main_thread', 'ra__ci_setup' and 'ra_ci_init_CI_lib'. See KBA 2807757. |
| 819570 | Under rare circumstances, a 3935 error, "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context. The transaction is currently in 'NULL XDES' state.", may be reported in the SAP ASE error log when before many 1105 errors were encountered. See KBA 2816667. |
| 819587 | In rare circumstances, a 678 error, "Invalid Buffer Cache Access: Could not open object ' < object-id > ' in database ' < database-id > '", together with a stack trace which includes the modules 'open_get_cacheid', 'Optimize' and 's_compile_stmt' may be reported in the SAP ASE error log while Adaptive Server is building the query plan of a DML query which involves an in-memory user temporary database. See KBA 2891210. |
| 819607 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'OptBlock::_OptInitBlobTcIdBm' followed by a stack trace that includes the modules 'OptBlock::OptPhase2aInit', 'OptGlobal::GblAssignOptId' and ‘OptGlobal::_GblSearchEngine', may be reported in the SAP ASE error log when a SELECT query is executed on a user table that has a column whose datatype is TABLE. See KBA 2818520. |
| 819609 | In rare circumstances, some queries that are executed in parallel mode by SAP Adaptive Server may hang. DBCC stacktrace( < spid-value > ) when run on the parent and worker processes will report the modules 'pipe_read' and 'LePipeRWState::_LePrwsReadConstant' on the top of the stack. See KBA 2815487. |
| 819618 | When SAP ASE is configured with a server page size larger than 2K bytes, the replication of a jar image installed with the utility installjava, may fail due to badly formed LTL commands sent to SRS by Replication Agent. |
| 819626 | Workload capture takes longer time to stop especially when ASE configured with multiple online engines. The more engines configured, the more time it takes to stop the workload capture. Typically, it may takes over 1 minute when ASE configured with 32 engines. |
| 819633 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'qremap__obuf' followed by a stack trace that includes the modules 'fglk__send_prom_attn', 'fglk__promote' and 'fglk__check_and_promote', may be reported in the SAP ASE error log when a query involving SQL UDF was being executed in parallel and it attempted to promote the locks to a lock of a higher level. See KBA 2812380 |
| 819639 | The LogicalReads/PhysicalReads columns in monProcessActivity may not be updated when running an UPDATE STATISTICS command. See KBA 2812568. |
| 819682 | The message, "Adaptive Server Enterprise system exception ( < address > ) generated by a storage access violation.", in the module 'ise_mapsqlaccess' together with a stack trace which includes the modules 'revokeacct' and 'd_iseadmin' may be reported in the SAP ASE error log when sp_grantlogin is executed on Windows platform if either the Integrated Security mode or the Mixed mode is in use. See KBA 2815124. |
| 819692 | In rare circumstances, Adaptive Server may freeze unexpectedly when many alarms are in use. See KBA 2815362. |
| 819711 | Sub-optimal performance may result during highly concurrent user login activity while accessing system tables SSYSSVROLES and SYSATTRIBUTES. An optimization is introduced that can be enabled by boot strapping Adaptive Server with trace flag 859. See KBA 2889793. |
| 819729 | In rare circumstances on a heavily-loaded multi-engine system, the message, "Current process infected with signal 11 (SIGSEGV)", followed by a stack trace that includes the module 'ssql_lookup' may be reported in the SAP ASE error log when a query is executed and the statement cache is full. This will be followed by an implicit shut down of the Adaptive Server. See KBA 2835051. |
| 819733 | In rare circumstances, a timeslice error together with a stack trace in the module 's_xform_to_execute' may be reported in the SAP Adaptive Server error log when a query that includes the abstract plan hint 'with_recompile' is executed while the configuration option 'statement cache size' is enabled. See KBA 2817683. |
| 819746 | The message 156 "Incorrect syntax near the keyword 'else'." can be seen when running the sp_dropdevice command after an upgrade. See KBA 2818609. |
| 819751 | Diagnostic enhancement to include spid, hostname, application name and SQL text for the message "stack_tracer: stack overflow last chance handler". See KBA 2886307. |
| 819756 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'com__exctnume_copy' together with stack trace which includes the module 's__convert_nume' may be reported in the SAP ASE error log when a prepared statement performs UPDATE on numeric columns to NULL and the option DYNAMIC_PREPARE is set to FALSE and trace flag 11013 is enabled. See KBA 2819614. |
| 819759 | Increase the largest single shared memory segment creation size to 4 terabytes. See KBA 2819670. |
| 819760 | In rare circumstances, a 6103 error, "Unable to do cleanup for the killed process; received Msg 835.", may be incorrectly raised, or the previously raised critical error may get erroneously re-raised by the same spid (and different kpid), or the spid for network listener may hit a SIGSEGV error together with the stack trace showing 'pss_free_seqhdrs' reported in the SAP ASE error log. You can enable trace flag 8601 either during ASE start-up or at run time using DBCC TRACEON to avoid these errors. See KBA 2838149. |
| 819773 | Additional status flags information for the stream buffer will be reported for investigation purposes when a process (spid) issues a cancel operation. See KBA 2810952. |
| 819777 | Enable Secure User Store Support for optdiag with command line options -k and -H. See KBA 2825630. |
| 819782 | A 840 error, "Device ' < device-name > ' (with physical name ' < physical-name > ', and virtual device number < value > ) has not been correctly activated at startup time. Please contact a user with System Administrator (SA) role.", may be reported in SAP ASE error log when Adaptice Server is configured for HADR. |
| 819795 | The message "Current process infected with signal 11 (SIGSEGV)" together with a stack trace in module 'mbkt_free' may be reported in the SAP ASE error log when multiple "alter database .. encrypt" or "alter database .. decrypt" commands are run simultaneously and there are not enough "number of worker processes" available to service the encryption or decryption tasks. See KBA 2822653. |
| 819803 | When the environment variable MALLOC_CHECK_ is set to 2, the Backupserver receives a SIGABRT signal during the cleanup phase of any connection established with Adaptive Server 16.0 SP03 PL07. The Backupserver process dies and a manual restart is required. The current fix implements fully the requirement for CR 699826. See KBA 2754515. |
| 819807 | A 454 error, "Number of elements in the largest IN list of 20732 exceeds the configured maximum value of 2000. Either use sp_configure 'max number of IN elements' to increase the value, or break the query into smaller pieces.", will be reported when a SELECT query is executed with a large IN list containing over 32767 elements, and the value of config option "max number of IN elements" is set to 2000. The 454 error is raised correctly, but the counted number of 20732 is incorrect. |
| 819810 | In rare circumstances, the message, "timeslice < negative-value > , current process infected" in the module 'sb__start' together with a stack trace which includes the modules 'sb_getsite' and 'dmpxact' may be reported in the SAP ASE error log when a remote DUMP TRANSACTION is executed. See KBA 2928400. |
| 819816 | A 9204 error, "RepAgent( < database-id > ): Could not locate schema for object with id = ( < object-id > ), current marker ( < page-number > , < row-number > ).", may be reported when 'REORG REBUILD < table-name > WITH ONLINE' is executed in a database using synchronous replication under an HADR setup. See KBA 2823970. |
| 819829 | A 639 error, "Attempt to fetch logical page < > dbid < > failed - page is not currently allocated.", or a 692 error, "Uninitialized logical page < > was read while accessing < > . Please contact SAP Technical Support.", or a 694 error, "An attempt was made to read logical page < > , virtpage < > from virtual device < > for < > . The page was not read successfully. You may have a device problem or an operating system problem.", may be reported in the SAP ASE error log when a large empty database is loaded from a compressed dump on winx64 platform. |
| 819831 | In rare circumstances, in a replication setup the truncation of the SAP ASE transaction log may be prevented because REORG REBUILD command was unnecessarily marked for replication. KBA 2969411 |
| 819845 | In very rare circumstances, the message "current process infected with 11 (SIGSGEV)" in the module 'pg_get_alloc_page' together with a stack trace which includes the modules 'pg_oamscan_nextpage' and 'dol_oamscan_getnext' may be reported in the SAP ASE error log during the execution of a query. See KBA 2835036. |
| 819846 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'rvm_has_decrypt_permission' together with a stack trace which includes the modules 'LeRun' and 'exec_lava' may be reported in the SAP ASE error log when a SELECT query against an encrypted column is executed. See KBA 2827203. |
| 819870 | READONLY connection should be able to execute only SELECT queries. See KBA 2810386 |
| 819874 | The message, "current process infected with 11 (SIGSEGV)" in the module 'ldap_value_free' together with a stack trace which includes the modules 'login__ldapauth' and 'login_handshake' may be reported in the SAP ASE error log due to a memory leak when openLDAP authentication is switching Composed DN to Searched DN while connecting to Adaptive Server. |
| 819901 | In rare circumstances a 692, 834, 4216 or 4218 error can be reported in the SAP ASE error log when LTL mode replication is enabled and the Rep Agent configuration parameter 'multithread rep agent' is set to 'true'. The errors are seen after DUMP TRANSACTION is executed or when Rep Agent is started. See KBA 2885891. |
| 819904 | In rare circumstances, the message "timeslice - < integer value > , current process infected at < hexadecimal value > " or the message "current process infected with 11 (SIGSEGV)" together with a stack trace which includes the module 'ra_sender_thread' may be reported in the SAP ASE error log when shutting down Rep Agent in a database setup for LTL mode replication and the Rep Agent configuration parameters 'multithread rep agent' and 'multiple scanners' are set to 'true'. See KBA 2843602. |
| 819943 | A 2714 error, "There is already an object named < > in the database.", is incorrectly raised for prepared statements with a batch which has create table with one of the columns having a default value, insert into the table and select from the table. See KBA 2904035. |
| 819970 | A 3705 error, "Cannot use DROP TYPE with ' < type-name > ' because ' < type-name > ' is a table. Use DROP TABLE.", may be reported in the SAP ASE error log when dropping a table type in a database that was loaded from a database dump having a different database ID value from the current database. See KBA 2835023. |
| 819977 | A 712 error, "There is insufficient heap memory to allocate < number > bytes. Please increase configuration parameter 'heap memory per user' or try again when there is less activity on the system.”, may be reported during the execution of a query when frequent MERGE statements were run and their target table had an update trigger executed. Alternatively, the message, "Could not obtain required number < number-of-bytes > of resource of type 'Pss Heap Memory'. Since the process absolutely requires this resource, it is going to wait indefinitely till the resource becomes available. Please increase the configuration parameter 'heap memory per user'.”, may be reported in the SAP ASE error log. See KBA 2835522. |
| 819996 | In rare circumstances, under an HADR setup when synchronous replication is enabled, the message, "A message from Replication Agent ' < database-name > ' is coming: 'buffer_pool_size for < database-name > is adjusted from < larger-size > to < smaller-size > .", followed by the message, "A message from Replication Agent ' < database-name > ' is coming: 'buffer_pool_size for < database-name > is adjusted from < smaller-size > to < larger-size > .", may be reported in the SAP Replication Server error log. |
| 820000 | When the configuration parameter 'enable functionality group' is on, Adaptive Server will use a default textsize value of 2G bytes that cannot be changed anymore to another value with the SET TEXTSIZE command. See KBA 2857264. |
| 820004 | ASE version string and active trace flags are missing when a new error log is opened either using sp_errorlog or by errorlog rollover feature. |
| 820042 | The message, "current process infected with 11 (SIGSEGV)", in the module 'hcb_tab_has_hcbidx' together with a stack trace which includes the modules 'alterdb' and 'altdb__row_storage_off_for_imrsdb' may be reported in the SAP ASE error log if turning off version storage of an IMRS-enabled database containing views that reference global temporary tables. See KBA 2853467. |
| 820049 | In rare circumstances, a 1204 error, "ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.", together with a stack trace which includes the modules 's _get_usr_goal' and 'pss_init' may be reported in the SAP ASE error log when Adaptive Server runs out-of-locks. Alternatively a time slice error may be seen in the module 'listener'. See KBA 2838550. |
| 820050 | The message, "current process infected with 11 (SIGSEGV)", in the module 'sb__diag_print_sitebuf' together with a stack trace which includes the modules 'prSITE_INFO' and 'exec_dbcc' may be reported in the SAP ASE error log when DBCC SITE is executed. See KBA 2853512. |
| 820055 | [New Feature Request] Implemented an interface to mark a non-clustered index not to be used by any query with or without AP (AP which is not optgoal, Optlevel, timeout, optcriteria). |
| 820057 | The database timestamp '@@dbts' jumps by a large amount unexpectedly during LOAD DATABASE when a database dump is loaded from a pre-16.0 SP03 Adaptive Server version into 16.0 SP03 or greater. See KBA 2839301. |
| 820105 | New trace flag 14325 introduced whereby additional validations on All Page Locked tables (APL) are performed during the execution of UPDATE or DELETE commands. See KBA 2904122. |
| 820121 | The message "current process infected with 11 (SIGSEGV)" in the module 'ea__add_imrslog_dmap' together with a stack trace which includes the module 'ea_encrypt_decrypt_db_main' may be reported in the SAP ASE error log when encryption feature is enabled, an IMRS log device exists and IMRS feature is not enabled. See KBA 2840114. |
| 820134 | In rare circumstances, the execution of dynamic prepared queries using correlated subqueries may fail with a syntax error when parameterized abstract plans are in use. See KBA 2904074. |
| 820140 | The message, "current process infected with 11 (SIGSEGV)", in the module 'syb_get_sess_pwd' together with a stack trace which includes the modules 'ra_open_context' and 'ra_sync_credentials' may be reported in the SAP ASE error log when Rep Agent receives a retry-able error such as a disconnection from SRS, in a database setup for LTL mode replication and the Rep Agent configuration parameters 'multithread rep agent' and 'multiple scanners' are enabled. See KBA 2847131 |
| 820144 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'OmniQuickPass::expandRangetableName' together with a stack trace which includes the modules 'internal_sql' and 'LeSQLRep' may be reported in the SAP ASE error log when SQL Replication is enabled and a DML query involving views or derived tables is run. See KBA 2850968. |
| 820151 | The execution of CREATE LOGIN < login-name > WITH PASSWORD < password > DEFAULT DATABASE < database-name > may fail at the client-application side with a java.lang.NullPointerException error after upgrading t Adaptive Server from 15.7 to 16.0 because a NULL value for status5 column of master..sysdatabases may unexpectedly be seen. |
| 820163 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)", in the module 'crdb__phys' together with a stack trace which includes the modules 'crdb_tempdb' and 'recover_tempdb' may be reported in the SAP ASE error log during the creation of a user temporary database while booting Adaptive Server. See KBA 2845915. |
| 820167 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'imrs_get_pdes_imrs' together with a stack trace which includes the modules 'usedb' and 'boot__recover_and_online' may be reported in the SAP ASE error log, when a database dump is loaded from a pre-16.0 SP03 Adaptive Server version into an IMRS-enabled database and ASE is subsequently rebooted. See KBA 2861875. |
| 820170 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'logcommand' together with a stack trace which includes the modules 'cri_main' and 'execproc', may be reported in the SAP ASE error log when DDL replication is enabled and a stored procedure that creates an index conditionally is executed. See KBA 2607322. |
| 820178 | The message, "Invalid data found and rebuilt in segment accounting array for segment < segment-number > in database ID < database-ID > .", may be incorrectly reported in the SAP Adaptive Server error log for a temporary database during recovery. See KBA 2846731. |
| 820187 | When Rep Agent is configured for Multiple Paths Replication using Multiple Scanners with at least two replication paths defined and the Rep Agent is stopped with sp_stop_rep_agent, the message "timeslice < negative-value > , current process infected" may be reported in SAP ASE error log, together with a stack trace which includes the modules 'ra_free_all_raxacts' and 'ra__coord_driver'. See KBA 2960271. |
| 820193 | In rare circumstances, the message "current process infected with signal 11 (SIGSEGV)" in the module 'undo_blockingcall_nowait' together with a stacktrace which includes the module 'shm__write_memsegment' may be reported in the SAP ASE error log causing Adaptive Server to hang when a Configurable Shared Memory Dump is setup with more than one dump threads enabled. See KBA 2854079. |
| 820202 | SAP ASE Rep Agent may terminate abnormally with a 9209 error, "RepAgent( < database-id > ): Missing datarow in TEXT/IMAGE/UNITEXT insert log record....", or a 9204 error, "RepAgent( < database-id > ): Could not locate schema for object with id = ( < object-id > ), current marker ( < page-number > , < row-number > ).", when REORG REBUILD is executed on a replicated table on which ALTER TABLE...WITH NO DATACOPY had previously been executed. See KBA 2890246. |
| 820207 | The message, "current process infected with 11 (SIGSEGV)" in the module 'pchk_fault' together with a stack trace which includes the module 'pchk_chk_txt_chain' may be reported in the SAP error log during CHECKSTORAGE when configured for multiple worker processes and one or more tables have LOB columns. See KBA 2845515. |
| 820213 | The message, "The Replication Agent thread for database ' < database-name > ' is not currently running.", may be reported when sp_stop_rep_agent < database-name > is executed, while the message, "A Rep Agent Thread for database ' < database-name > ' (dbid= < database-id > ) is already running.", is reported when sp_start_rep_agent < database-name > is run. |
| 820220 | New trace flag 11021 introduced whereby the built-in ISNUMERIC() behavior is reverted to pre-CR 767440 fix. See KBA 2053654. |
| 820242 | A new functionality is added in SAP ASE Workload Analyzer Command Line Utility which allows user to export capture, replay or comparison dashboard to an Excel file for analysis. See KBA 2850143. |
| 820268 | Under some circumstances, a remapping Error: 2805, may be seen in the error log on execution of sql statement containing constants in both the predicate and in a group by clause. |
| 820270 | In rare circumstances, when the monProcessActivity and monProcessStatement MDA tables are queried twice in short time, the values of the second query may be less than the values of the first query in LogicalReads or PhysicalReads column. |
| 820285 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'kbfalloc’ together with a stack trace which includes the modules 'boot__recover_and_online’ and 'db_build_dshmap‘ may be reported in the SAP ASE error log when the database dump of the master database is loaded on a newly created master device. See KBA 2901664. |
| 820290 | The message, "current process infected with 11 (SIGSEGV)", in the module 'pipe_write' together with a stack trace may be reported in the SAP ASE error log during the parallel execution of a Lava query. See KBA 2694998. |
| 820300 | Lack of diagnostics prevents root cause analysis when an error 834, state 3 is raised which leads to transaction log getting full with below error message: Space available in segment < segment_name > has fallen critically low in database < dbname > . All future modifications to this database will be aborted until the transaction log is successfully dumped and space becomes available. Diagnostic reporting to error log has been introduced which are disabled by default and can be enabled under trace flag 891. Trace flag 894 can be enabled to raise exception 835, state 11 instead of reporting diagnostics. Previously introduced trace flag 893 is obsolete. |
| 820315 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'do_needed' together with a stack trace which includes the modules 'redo_bt_rebldleafs' and 'ldxact' may be reported in the SAP ASE error log, when a database dump that was taken after a reorg rebuild command was run, is loaded with either trace flag 3303 or 3300 enabled. See KBA 2885784. |
| 820329 | The message, "timeslice < value > , current process infected at < value > ", in the module 's__setup_hostvars' together with a stack trace which includes the modules 's_xform_to_execute' and 's_normalize', may be reported in the SAP ASE error log when executing a user query having very large IN list with host variables if Statement Cache is on. See KBA 2857869. |
| 820346 | A 3508 error, "Attempt to set ' < database-name > ' database to single user mode failed because the usage count is < number > . Make sure that no other users are currently using this database and rerun CHECKPOINT" may be reported when the "sp_dboption ' < database-name > ', 'single user', true" command is executed to set the database into single user mode. See KBA 2948470. |
| 820349 | The message, "RepAgent( < database-id > ): Autoscaling: Warning: The 'buffer pool' cannot grow any further and the scanner will sleep on packages becoming available.", may be excessively reported and logged in the SAP ASE error log when the 'stream replication' option is enabled. See KBA 2695973. |
| 820350 | The show_condensed_text(SSQLID, 'text') function may generate incorrect "column_name AS column_name" in select-list when a query is a subquery in the where clause. An example is that "select c1 from t1 where c2 in (select c3 from t2)" will be condensed to "SELECT c1 FROM t1 WHERE c2 IN (SELECT c3 AS c3 FROM t2)". |
| 820354 | The message, "A00: SYBMULTBUF ERROR: Internal error: unable to create errorlog buffer semaphore", may be reported in the SAP ASE Backup Server error log on a Sun Solaris system when DUMP DATABASE is executed after the '/tmp' file system was cleaned up by the end-user. See KBA 2855663. |
| 820371 | When executing the command UNMOUNT DATABASE on a replicated database while Rep Agent is running, or when killing explicitly the Rep Agent Scanner or the Secondary Transaction Point Manager, in an HADR setup, one or several stack traces may be reported in the SAP ASE error log which could include the modules 'ra_ci_scanner_release_ci_interface', 'ra__cilib_thread_setup', or 'ra_ci_exception_handler'. Adaptive Server may become unresponsive or perform an implicit shutdown. See KBA 2900112. |
| 820378 | A 925 error, "Maximum number of used databases for each query has been exceeded. The maximum allowed is 8.", may be reported when UPDATE STATISTICS command fails continuously for 8 times. See KBA 2994983. |
| 820381 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeLOBCache::LeLOBCacheInsert' followed by a stack trace that includes the modules 'LeRun', 'LeEvals::LeEvRun' and 'LeScalarOp::_LeOpNext', may be reported in the SAP ASE error log when executing sp_showplan to check another session. See KBA 2856735. |
| 820386 | In rare circumstances, a 8213 error, "Failed to acquire address lock on object < object-name > " can be seen when performing inserts on a table containing an identity column and the database containing the table has an active DUMP DATABASE running. See KBA 2776030. |
| 820387 | The MDA table master..monRepSyncTaskStatistics may sometimes report inconsistent values for the columns AverageCommitToRAProcessTime and AverageRAProcessToPkgFlushTime in an HADR setup when streaming replication is enabled. See KBA 2882397. |
| 820449 | The error message, "Backup Server: 9.5.2.1: Error in verification function for config option < configuration-option > .", followed by the message, "Backup Server: 9.4.2.1: There was an error when setting the configuration option < configuration-option > = < configuration-value > .", may be reported in the SAP Backup Server error log while booting the Backup Server and any of the configuration options "warn_level", "server_connections", "packet_size", "allocation_threshold" and "reserved_threshold" has had its non-default value changed. See KBA 2907191. |
| 820483 | A 605 error, “An attempt was made to fetch logical page < page-number > ' from cache < datacache-name > . Page belongs to database 'sybsystemprocs' (31514), object 'sysprocedures' (5), index 'sysprocedures' (0), partition 'sysprocedures_5' (5) and not to database 'sybsystemprocs' (31514), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8).”, in the module ‘xxs__loglast’ together with a stack trace which includes the modules ‘hadr_getremote_status’ and ‘hadr_init’ may be reported in the SAP ASE error log occasionally in an HADR setup during the boot time of the Adaptive Server. |
| 820516 | In rare circumstances, Adaptive Server may return unexpected results if multiple cursors exist for a session and a FETCH < cursor-name > command is run after a DELETE command is executed which resulted in emptying few data pages from an All Pages Locked table and the cursor's query execution plan was using an index scan. |
| 820521 | When trace flag 4899 is enabled, Adaptive Server will perform additional row format validations when the rows being inserted into a table are formatted by the client application such as JDBC using bulk copy option. |
| 820542 | The error message, "Backup Server: 7.4.2.1: Option 'CAPACITY': '-198967296' is an invalid value -- check the documentation for allowable values.", may be reported in the SAP Backup Server error log, when a database is dumped on a tape device with size greater than 2TB. See KBA 2864376. |
| 820545 | A 9219 error, "Internal error.", followed by a 9204 error, "RepAgent( < database-id > ): Could not locate schema for object with id = ( < object-id > ), current marker (0, 0)." may be reported in SAP ASE error log when a very large number of DDL commands are executed concurrently in a database using synchronous replication under an HADR setup. |
| 820548 | The message, "current process infected with 11 (SIGSEGV)", in the module 'LeCheckIdentInsUpdForMerge' together with a stack trace may be reported in the SAP ASE error log when a complex MERGE query is executed whose query plan involves SEQUENCER operator. See KBA 2908758. |
| 820557 | A 156 error, “Incorrect syntax near the keyword 'else'.”, may be reported when installing sp_addtype system stored procedure while executing installhasvss. See KBA 2964898. |
| 820579 | The message, "Backup Server: 4.23.2.1: baio_read: read /dev/ < raw-disk-path > : Not enough space.", followed by the message, "Backup Server: 4.141.2.16: [63] The 'write' call failed for database/archive device while working on stripe device '/dev/ < raw-disk-path > ' with error number 12 (Not enough space).", may be reported to the SAP Backup Server error log when DUMP DATABASE is executed on a database that resides on a raw partition device on the HP Itanium platform and the Adaptive Server configuration option "allow sql server async i/o" is enabled, while the configuration option "enable hp posix async i/o" is disabled. See KBA 2866900. |
| 820609 | With predicated privileges, incorrect results may be observed for queries that use derived tables or views. See KBA 2866816. |
| 820627 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the modules 'showplan' or 'show_plan’ followed by a stack trace may be reported in the SAP ASE error log when executing sp_showplan to check another session. See KBA 2923564. |
| 820635 | The query on the monHANANonPushdown MDA table will fail with message "Command has been aborted" without reporting all required options for this table if 'enable monitoring', 'nonpushdown pipe active' or 'nonpushdown pipe max messages' is set as 0 (default). |
| 820672 | In rare circumstances, when a huge table is queried, some MDA tables like monProcessStatement, monProcessActivity and monSysStatement may suddenly jump to a huge value like 9223372034707304682 in LogicalReads column after the value reaches to 2,147,483,647 (2^31 -1). See KBA 2873194. |
| 820700 | In rare circumstances, a 834 error, "Illegal attempt to clean buffer: < allocation-page-meta-data > .", may be reported in the SAP ASE error log when LOAD DATABASE is executed and a earlier housekeeper task (HK_GC) has run out-of-log space (error 1105) in the database while deallocating a page which caused its allocation page remain unexpectedly kept. See KBA 2897499. |
| 820711 | SAP Adaptive Server may unexpectedly exit with no message reported in the error log when XML is in use. See KBA 2868544. |
| 820716 | In rare circumstances, the message "timeslice < negative-value > , current process infected" in the module 'lock_address' together with a stack trace which includes the modules 'bt__lockprevpg', 'bt__pgdealloc' and 'hkgc_garbagecollect' may be reported in the SAP ASE error log when many concurrent DML commands on DOL tables (Data Only Locked) are executed and index pages need to be shrunk. See KBA 2879991. |
| 820771 | 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 = ( < > , < > ).", or a 3478 error, "During undo the page timestamp value is less than new timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log new timestamp= < > . Log record marker = ( < > , < > ). Xactid = ( < > , < > ).", or a 12337 error, "Page ' < > ' in database ' < > ' was incorrectly found to be uninitialized when it was read. Recovery of this database cannot continue.", may be reported in the SAP ASE error log during boot time recovery after a non-polite shutdown of the Adaptive Server while REORG REBUILD command was running. See KBA 2877124. |
| 820774 | The error message, "Backup Server: 4.124.2.1: Archive API error for device='::test.dmp::000': Vendor application name= < UNINIT > ,Library version=0, API routine= < UNINIT > , Message=Unable to open API library for device '::test.dmp'. Library path is'/$SYBASE/ASE16_0/lib/lib.so'.dlopen() returned: Code=0, Message=/$SYBASE/ASE-16_0/lib/lib.so: cannot open shared object file: No such file or directory.", may be reported in the SAP Backup Server error log instead of the error message, "Backup Server: 4.131.2.1: Device: '::test.dmp'. The stream identifier '' has an incorrect length. A valid length is from 1 to 255 bytes long.", when DUMP TRANSACTION < database-name > to '::test.dmp' is executed. See KBA 2897457. |
| 820775 | In rare circumstances the message, “Current process infected with signal 11 (SIGSEGV)” in the module ‘PartNodeInfo::collocatedSite’ together with a stack trace may be reported in the SAP ASE error log during the optimization phase of a complex query. See KBA 2890244. |
| 820783 | In rare circumstances, a 4853 error, "Server has encountered badly formatted rows during bulk insert. The bulk client may be too old to format rows properly for this server version.", may be reported during bulk copy utility execution when the Adaptive Server trace flag 4899 is enabled and the total length of a row is greater than 256 bytes. See KBA 2893303. |
| 820815 | Insensitive cursors may hold shared intent 'sh_intent' locks on the base table when the cursor would return less than 1000 rows. See KBA 2883034. |
| 820817 | The message "current process infected with 11 (SIGSEGV)" in the module 'mda__populate_RepCoordinatorTable' together with a stack trace which includes the modules 'mda_populate_monRepCoordinator' and 'mda_exec' may be reported in the SAP ASE error log when a SELECT query on MDA table master..monRepCoordinator is executed and another session concurrently has terminated the Adaptive Server Rep Agent tasks prematurely. See KBA 2895845. |
| 820832 | In rare circumstances, a 692 error, “Uninitialized logical page ‘ < page-number > ’ was read while accessing database ' < database-name > ’ ( < database-id > ), object 'syslogs' (8), index 'syslogs' (0), partition 'syslogs_8' (8). Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘checkpoint_db’, ‘ckpt_need_new_record’ and ‘wrongpage’ may be reported in the SAP ASE error log when the database option "trunc log on chkpt" is being enabled and after ONLINE DATABASE is executed in a database that was already online. Alternatively, a 1251 error, “The dbinfo anchor in the database 'database ' < database-name > ' ( < database-id > )' is already locked by the task. Nested access to dbinfo anchor is not allowed. Lock was acquired in file 'loaddb.c' at line 2165. This is an internal error. Please contact SAP Technical Support.”, with a stack trace which includes the modules ‘xact_commit’, ‘xls_preflush’ and ‘lock_psema’ may be also seen. See KBA 2878392. |
| 820841 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'ridmap_lookup' together with a stack trace which includes the modules 'd__log_xlog_analyze' and 'd_imrslog_analyze' may be reported in the SAP ASE error log when DBCC IMRSLOG with the 'analyze' option is executed. See KBA 2960273. |
| 820844 | The message, "Current process infected with 11 (SIGSEGV)", may be reported together with a stack trace which includes the module 'OmniQuickPass::generateSelectinto' in the SAP ASE error log when a SELECT INTO query with an aggregate function is executed on a database that has SQL Statement Replication enabled. See KBA 2879192. |
| 820857 | The partial rollback of a transaction may be unexpectedly discarded by SAP Replication Server replication, resulting in a data mismatch between the primary and replicate Adaptive Server databases when LTL replication is enabled. See KBA 2879588. |
| 820871 | The built-in get_appcontext() may return an incorrect value if it is executed in the same query with another built-in. See KBA 2881971. |
| 820904 | In rare circumstances a time slice error may be reported in the SAP ASE error log together with a stack trace which includes the modules 'cudf_get_resref' and 'cudf_start_query' followed by an implicit shutdown of Adaptive Server if the C-UDF library could not be loaded because of a version compatibility conflict. See KBA 2901691. |
| 820948 | In rare circumstances, a performance degradation may be seen when executing queries and the optimization goal for ‘allrows_mix’ is in use. |
| 820974 | A 16382 error, "The configured maximum number of mutexes have already been created", may be reported in the SAP ASE Backup Server error log when many simultaneous dumps are executed. Sometimes the message, "BACKUPSERVER: bs_trap; process received signal 11", may also be seen resulting in the Backup Server implicitly shutting down. See KBA 2896338. |
| 820976 | In HA setup, on ibmaix platform, sybha utility will hit an error while deleting the tmp file when sp_companion is run multiple times. See KBA 2884877. |
| 820983 | In rare circumstances either a 632 error, or a time slice error, or a signal 11 error, may be hit during the recovery of a transaction dump that was taken with Adaptive Server version 16.0 SP02 PL07 (or lower) and 16.0 SP03 PL04 HF1 (or lower) while REORG REBUILD command on a table with compressed indexes was running. Enabling trace flag 12669 before loading the failing transaction dump can be used to overcome these errors. See KBA 2889466. |
| 820988 | High load of cross database queries may lead to contention on sysocolumns system table. See KBA 2890197. |
| 820993 | The message, "ERROR: Cannot start due to invalid credentials", may be reported in webservice error log when runws is executed and the Adaptive Server configuration option "net password encryption reqd" is set to a non-zero value. |
| 820994 | 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 = ( < > , < > ).", or a 3478 error, "During undo the page timestamp value is less than new timestamp from log. Page #= < > , object id = < > , page timestamp= < > . Log new timestamp= < > . Log record marker = ( < > , < > ). Xactid = ( < > , < > ).", or a 12337 error, "Page ' < > ' in database ' < > ' was incorrectly found to be uninitialized when it was read. Recovery of this database cannot continue.", may be reported in the SAP ASE error log during boot time recovery after a non-polite shutdown of the Adaptive Server while REORG REBUILD command was running. See KBA 2877124. |
| 821002 | A 3626 error, "The transaction was aborted because it used too much stack space. Either use sp_configure to increase the stack size, or break the query into smaller pieces. spid: < > , suid: < > , hostname: < > , application name: < > ", may be reported when executing a large number of DML commands in a single batch and the trace flag 11013 is enabled. See KBA 2886254. |
| 821005 | The ASE configuration parameter 'HADR remote query timeout' cannot be set to 0 i.e. disabled. This restriction is now relaxed and the default value is changed to 0 i.e. disabled. See KBA 2900121. |
| 821013 | In rare circumstances, the message "ERROR in plc__discard() for plc < address > with MLDML lrs_to_discard( < non-zero-number > ) for dbid < database-id > is not between 0 and plc_count(0).", together with a stacktrace that includes the modules 'onlutl__apply_insdel_lr' and 'xls_discard_plc' may be reported in the SAP ASE error log when REORG REBUILD with ONLINE and HK WASH processes are running in parallel. See KBA 2896298. |
| 821036 | A 622 error, "Opentable was passed a varno of 250. Object '' in database 'tempdb' already has that session descriptor in use. This occurred while opening object id < negative-object-ID > in database id 2.", or the message, "current process infected with 11 (SIGSEGV)", together with a stack trace which includes the modules 'sdes_hookup' and 'GttTable::GttUsefulIndex' may be reported in the SAP ASE error log during the recompilation of a large query because of insufficient resources that would have allowed Adaptive Server to execute the query in parallel mode. See KBA 2896395. |
| 821038 | In rare circumstances on a multi-engine IBM AIX system, the message "Current process infected with signal 11 (SIGSEGV)" in the module 'free' together with a stack trace which includes the modules 'mda_fill_and_send_monProcessSQLText.fdpr.chunk.1' or 'mda_fill_and_send_monProcessSQLText' may be reported in the error log when the monProcessSQLText MDA table is queried. See KBA 2895827. |
| 821042 | In rare circumstances, a 835 error with state 11, "Illegal attempt to change contents of buffer: ...", in the module 'smp_bufpredirty' together with a stack trace which includes the modules 'row_delete' and ‘bt__delrow’ may be reported in the SAP ASE error log during the execution of a DML query while the buffer is being de-allocated and another session is in the process of changing it. See KBA 2908677. |
| 821043 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'le_showPLL' followed by a stack trace that includes the modules 'showE_STMT' and 'showplan', may be reported in the SAP ASE error log when executing sp_showplan to display plan info of a query running on another session. See KBA 2895780. |
| 821059 | A new option 'html' is added to sp_showplan system stored procedure allowing to generate the plan information for a given 'spid' and redirect it into an HTML file in the target folder as previously specified by SET STATISTICS PLAN_DIRECTORY_HTML command. See KBA 2890602 |
| 821061 | A 207 error, "Invalid column name < value > .", may be reported during the execution of a stored procedure that references temporary tables. This error is likely to be reported when nested stored procedures that create temporary tables at multiple nested levels are run. See KBA 2896397. |
| 821086 | In rare circumstances, a 834 error, "Illegal attempt to clean buffer: < sysdams-page-meta-data > ." in the module 'cm_dbclean' together with a stack trace which includes the modules 'buf_offline_database' and 'lddb_main' may be reported in the SAP ASE error log when LOAD DATABASE is executed and an earlier full database dump command execution was either interrupted or killed while the database option "allow incremental dumps" is enabled. See KBA 2893318. |
| 821102 | When $SYBASE/WLA directory is readonly, WLACLIUtil will fail to start with exception like "log4j:WARN No appenders could be found for logger (com.sybase.workload.cli.WLACLIUtil)" even though a log file has been specified in command line with "-L" option. See KBA 2904572. |
| 821112 | The message, "The log page count in DBINFO for database < database-name > is inaccurate because dbi_freelogpages_at_ckpt ( < value-greater-than-zero) should be less than dbt_logsize (0). Run DBCC TABLEALLOC(syslogs, full, fix) on this database in single-user mode to make the counts consistent again.", may be reported in the SAP ASE error log during the recovery of a database upon Adaptive Server startup. This occurrence of the message is a false positive message and can be ignored because at this point in time dbt_logsize is not yet established. See KBA 2899024. |
| 821132 | In some circumstances, ALTER TABLE DROP PARTITION command may slowly execute especially on hyper-partitioned tables. The call stack for the session executing this command will often report the modules 'ptnc_fix_pctxt' and 's_cpytxt'. See KBA 2896288. |
| 821136 | The message "end of stack trace" is not printed in the SAP Adaptive Server error log together with the stack trace, when the I/O Controller thread hits a signal. |
| 821137 | In a HADR environment, if the ct-lib controller thread running on the standby ASE terminates, then the primary ASE may run out of user connections over the period of time. |
| 821175 | If the value of the 'max SQL text monitored' configuration parameter is set without rebooting the ASE server, a query on the monProcessSQLText Monitoring Table may generate a 632 error. See KBA 2904567. |
| 821194 | Under rare circumstances, ALTER TABLE may be incorrectly applied to global temporary tables. |
| 821207 | Under rare circumstances, when a query against MDA tables results in a signal 10, signal 11 or time slice error, SAP Adaptive Server may shut down implicitly with a message like "Spinlock [ < spinlock-value > ] at address [ < address-value > ] owned by [ < kpid-value > ". See KBA 2901110. |
| 821245 | A new Adaptive Server configuration, 'ignore outdated plans' is added to skip the outdated plan check when populating the Active column in master..monCachedProcedures MDA table. |
| 821254 | In rare circumstances, a 632 error, "Attempt to move memory with an incorrect length of 18432. Maximum allowed length is 16384.", may be reported when ALTER DATABASE OFF/LOG OFF is executed on a device that has many fragments allocated. Alternatively, the message, "Current process infected with 11 (SIGSEGV)" in the module 'altdb__free_device_fragments' together with a stacktrace may be reported in the SAP Adaptive Server error log. See KBA 2903224. |
| 821260 | WLACLIUtil may not report some DEBUG messages into log file even though the log level has been set as 5 (DEBUG) with the "-m" option. See KBA 2904575. |
| 821262 | Added restriction on SQL Anywhere database configuration file access in SAP ASE Cockpit for Windows. |
| 821265 | Additional checks added in DROP SERVICE command. |
| 821288 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeScanOp::LeOpSaveIOStats' followed by a stack trace that includes the modules 'LeDMLOp::_LeOpClose', 'LeEmittOp::_LeOpClose' and 'LePlanClose', may be reported in the SAP ASE error log when updating a user table with a in-row text columns and a foreign key constraint. See KBA 2964443. |
| 821302 | Under rare circumstances, the Backup Server configuration file may be overwritten unexpectedly. See KBA 2921881. |
| 821331 | A 15497 error, "The password for the master key of database 'master' has not been set", may be reported when Adaptive Server tries to decrypt database sybsecurity during SAP ASE restart. See KBA 2922899. |
| 821334 | The message, "current process infected with 11 (SIGSEGV)", in the module 'LeLOBCache::LeLOBCacheInsert' together with a stack trace including the modules 'tdsrecv_dynamic' and 'tdsrecv_params' may be reported in the SAP ASE error log when inserting a parameterized value with setUnicodeStream into an image column using a dynamically prepared statement. See KBA 2909261. |
| 821339 | When executing dynamic prepared statements while SQL statement replication is enabled and the Adaptive Server configuration parameter 'streamlined dynamic sql' is set to 1, Rep Agent may terminate abnormally with a 9202 error, "RepAgent( < database-id > ): Nested replicated stored procedure detected. Transaction log may be corrupt. Please contact SAP Technical Support. (current marker = < page-number > , < row-number > )". See KBA 2967909. |
| 821344 | A 692 error, "Uninitialized logical page ' < page-id > ' was read while accessing < partition-information > . Please contact SAP Technical Support.", or a 4216 error, "DUMP DATABASE failed in database < database-name > : unexpected end of log encountered on page < page-id > while scanning for page < page-id > .", may be reported when DUMP DATABASE is executed on a non recovered encrypted database after Adaptive Server reboot. See KBA 2964448. |
| 821345 | A 871 error, "Process < process-id > is trying to release a latch on buffer < buffer-address > (dbid: < database-id > , pageno: < page-number > ) without holding a latch on the buffer.", may be reported in the SAP ASE error log when high concurrent activity is taking place in a user defined temporary database. See KBA 2916685. |
| 821346 | The execution of sp_encryption helpkey,'%key_mst%' may return an empty result set. See KBA 2936507. |
| 821350 | Sybmon command "findbuf < database-id > < page-number > 1" will report signal 11 error in the module 'd__findbuf_cachelet' when executed on a memory dump which does not include the page cache. See KBA 2924666. |
| 821351 | A Table valued UDF may return a non-null datetime value instead of null for a nullable datetime column when an explicit null valued is used for a SELECT statement. See KBA 2909254. |
| 821359 | Additional checks added in XP Server while loading the required DLL on Windows platform. |
| 821365 | In rare circumstances, the message "uaremove: alarm id 0 not within range", may be reported in the SAP Adaptive Server error log. See KBA 2985166. |
| 821389 | A 12822 error, "Cannot create temporary table < table-name > . Prefix name < name > is already in use by another temporary table < table-name > .", is unexpectedly not raised when a stored procedure that creates the same temporary table is executed, causing an orphan temporary table to be left behind and requiring DBCC ORPHANTABLES to be then executed. See KBA 2910916 |
| 821391 | In rare circumstances, the message, "Internal Ct-Lib/Cs-Lib error 16843057: 'ct_send(): user api layer: external error: This routine cannot be called because another command structure has results pending.'", may be reported when creating a remote table in a nested query on a proxy table. See KBA 2995039. |
| 821406 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database < database-name > because the requested RID has a higher number than the last RID on the page.", may be reported in the SAP Adaptive Server error log when a transaction is rolled back and involves a DML command as well an open cursor defined on an Allpages Locked Table (APL) which has a clustered index and one or more non-clustered indexes. See KBA 2994956. |
| 821437 | The message, "RepAgent( < database-id > ): Cannot allocate < value > bytes of memory. You may need to reconfigure the parameter 'replication agent memory size' with more memory.", may be reported in the SAP ASE error log after frequently executed queries on the MDA table monRepStreamStatistics. See KBA 2921916. |
| 821504 | In rare circumstances, SAP ASE Rep Agent might be shut down following the message "Streaming replication distribution CI Library error -3 with severity 2 and message 'Package(...) buffer is depleted. Total < number > , used < number > , requesting < number > .'. Rep Agent detected error 313 with message 'CI API call < function name > failed ' at line < line number > in file ra_ci_cmd.c". See KBA 2921889. |
| 821511 | In rare circumstances, the message "Warning: The size of the stream buffer is too small ( < old-value > bytes). Use sp_config_rep_agent ' < database-name > ', 'stream buffer size', ' < new-value > ' to increase it." when preceded by a 9414 error whose text mentions "CI API call to SendMsgs() failed" may be erroneously reported in an HADR setup and can be ignored. See KBA 2946994. |
| 821527 | The partial rollback of a transaction may be unexpectedly discarded by replication, resulting in a data mismatch between the primary and replicate databases. This applies to SAP Adaptive Server Replication Agent for setups using LTL replication only. See KBA 2879588. |
| 821535 | A 605 error, "An attempt was made to fetch logical page < page-id > from cache 'default data cache'. Page belongs to database < database-name > ( < database-id > ), object < object-name > ( < object-id > ), index < index-name > ( < index_id > ), partition < partition-name > ( < partition-id > ) and not to database < database-name > ( < database-id > ), object < object-name > ( < object-id > ), index < index-name > ( < index-id > ), partition < partition-name > ( < partition-id > ).", may be reported in the SAP error log together with a stack trace which includes the modules 'pg_latchoam' and 'ups__updstats' when UPDATE STATISTICS is executed on an All Pages Locked table while DML commands are concurrently executed on the same table. See KBA 2948437. |
| 821539 | A 11216 error, "Internal Ct-Lib/Cs-Lib error 33816856: 'cs_convert: cslib user api layer: common library error: The conversion/operation was stopped due to a syntax error in the source field.'.", may be reported on Windows during the execution of sp_dump_history. See KBA 2918657. |
| 821540 | Stored procedures which reference SQL UDF objects (User-Defined-Functions) may be compiled at each execution instead of Adaptive Server reusing already compiled and cached query plans. See KBA 2918013. |
| 821549 | A 2714 error, “There is already an object named ' < object-name > ' in the database.”, may unexpectedly not be reported when CREATE VIEW with name 'dbo.sysquerymetrics' is executed although a view with name 'sysquerymetrics' exists already. See KBA 2919190 |
| 821550 | The message "Truncation error occurred. Command has been aborted." may be reported when executing 'sp_chgattribute < table-name > , < attribute > , 0, < float-value > '. See KBA 2964498. |
| 821558 | Replication of statements using SQL based replication logic may fail for queries having ANSI joins. SAP Adaptive Server may incorrectly provide replication information to Replication Server and as a result the DSI thread may encounter problems while replicating data to the companion ASE. See KBA 2937503. |
| 821629 | A new error 3689, "Cannot allocate shared memory as 'max memory' limit of ' < value > ' pages has been reached. Please increase configuration parameter 'max memory' to allow additional shared memory allocation. Total physical memory allocated so far ' < value > ' pages.", will be reported when appropriate to the client and will be logged in the SAP Adaptive Server error log. See KBA 2943124. |
| 821640 | Error 614 "Adaptive Server accessed a row that has an illegal length of < length > while in data base < db_name > . < pageno > . The minimum row length is < length > . The page size is < page_size > ." may be raised in user tempdb or in system tempdb under high concurrent environment of create temp table. See KBA 2986600. |
| 821649 | In an HADR setup, Rep Agent may not be notified in due time when user log caches are flushed to syslogs. See KBA 2924668. |
| 821671 | The output for LOAD DATABASE WITH listonly = create_sql is enhanced to include the options WITH latch_free_index, WITH defer_index_recovery and the database type TEMPORARY in the CREATE DATABASE statement. |
| 821687 | The message, "Current process infected with 11 (SIGSEGV)", together with a stack trace including the module 'GtgGroup::GtInitGcPerGt' may be reported in the SAP ASE error log when a query that has nested aggregate functions including distinct with both GROUP BY and HAVING clauses is executed. See KBA 2503398. |
| 821736 | The "dbcc workload_capture(preference, [logins|nonlogins], < logins > )" command will truncate the long < logins > list silently if the < logins > list is longer than 512 bytes. As a result, the logins filter set for a capture may not work as expected in Workload Analyzer Command Line Utility. |
| 821748 | In rare circumstances, the message “Current process infected with signal 11 (SIGSEGV)” together with a stack trace which includes the module ‘cfree’ may be reported in the SAP error log in an HADR Always On setup. Alternatively the message “Current process infected with signal 6 (SIGABRT/SIGIOT)” together with a stack trace which includes the module ‘gsignal’ may be reported as well. See KBA 2883016. |
| 821753 | In rare circumstances, SAP Adaptive Server processes may be blocked while running EXECUTE ESP commands as shown by sp_who because the XP Server process hangs and will not respond back to these commands requests. When printing the execution stack trace of the XP Server process, for example with gstack < xpserver-pid > , the modules ‘srv_free', ‘malloc' and '__lll_lock_wait_private' will be reported which is an evidence of the XP Server process hanging forever. See KBA 2937598. |
| 821761 | A 14612 error, “Inconsistent usage anchor: Dbid '1' Lstart '51200'.”, may be reported by DBCC CHECKCATALOG after having booted the SAP Adaptive Server with options ‘-w master’ and ‘-f’. The newly introduced option ‘fix_anchor_usg’ for DBCC DBREPAIR will allow to correct this error. See KBA 2968918. |
| 821769 | A 1265 error, "An illegal attempt was made to release an invalid lock or a lock that is not owned by the process family (lr= < lock-address > , lrmagic=f).", in the module 'lock_release' together with a stack trace which includes the modules 'unmountdb' and 'dbs_shutdown' may be reported in the SAP Adaptive Server error log when UNMOUNT DATABASE is executed and at least one session was found active in the target database which had session level attributes associated with it. See KBA 2933398. |
| 821779 | SAP ASE Cockpit installation writes encrypted sensitive information to the installation log file. |
| 821789 | A 911 error, " Attempt to locate entry in sysdatabases for database < database-name > by name failed - no entry found under that name. Make sure that name is entered properly. ", may be reported when creating a user stored procedure which contains a delete-join query and the table names in the join query have both the database name qualified and the SAP Adaptive Server option 'deferred name resolution' is enabled. See KBA 2931133. |
| 821814 | In rare circumstances, a timeslice error in the module 'lc_findconn' together with a stack trace which includes the modules 'readremote', 'dpdb_poll_async_bs_rpc' and 'dpdb_main' may be reported in the SAP ASE error log when DUMP DATABASE is executed. See KBA 2928400. |
| 821848 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'xls_flush_plcqueue' together with a stack trace that includes the modules 'xls_reconfig_plcblk' and 'xact__preparexact' may be reported in the SAP Adaptive Server error log during the execution of a multi-database transaction which involves low and full durability databases. See KBA 2947965. |
| 821864 | Enhancements added to the Rep Agent schema cache module allowing lesser look ups to sysobjects system table and more efficient hashing access for better performance while either searching or instantiating an object in the cache. See KBA 2946040. |
| 821919 | In rare circumstances, a 14108 error, “Could not find partition descriptor for objid < object-id > , indid < index-id > , ptnid < partition-id > in dbid < database-id > .”, may be reported when ALTER TABLE MERGE PARTITION is run on an empty range partitioned All Pages Locked table having a clustered index and can result in some Adaptive Server resources not being released. See KBA 2948449. |
| 821959 | The installmaster file has a typo in query "select ::isolation fromm dummy". See KBA 2922993. |
| 822007 | The execution of DBCC ORPHANTABLES may incorrectly report the existence of an orphan table when the table is not orphan. See KBA 2938960. |
| 822102 | A 2 error, "Message empty.", may be reported in the SAP ASE error log when inserting column name or number of supplied values does not match table variable definition. See KBA 2946944. |
| 822118 | A 9522 error, "The parameter that specifies the number of rows in a SET ROWCOUNT statement must be an integer with a value greater than 0.", will be reported when SET ROWCOUNT command is executed and an unsigned variable is passed to it. See KBA 2995048. |
| 822136 | After executing the command 'ALTER TABLE ... DISABLE TRIGGER' on several tables in an HADR setup without further logging activity on these tables, the user session in SAP Adaptive Server may eventually hang in the module ‘ra_ci_sync_pl_schema_request’. |
| 822164 | The message, "Rep Agent on database ' < database-name > ' switched from mode 'async' to mode 'sync' because scanner reached end of log", and the message, "Rep Agent on database ' < database-name > ' switched from mode 'sync' to mode 'async' because timer on commit expired.", may be reported almost at the same time in the SAP Adaptive Server error log under a high workload in an HADR setup. The call stack of the Rep Agent scanner spid will show the modules 'ra__ci_stream_pkg_stats_pool_almost_exhausted' or 'ra__ci_stream_pkg_stats_shrink_pool'. See KBA 2994966. |
| 822184 | In rare circumstances, a hang may be seen when a remote procedure call (RPC) is executed between two SAP Adaptive Server instances. See KBA 2974458. |
| 822230 | The message, “timeslice < negative-value > , current process infected”, in the module ‘exc__raise’ together with a stacktrace which includes the modules ‘lddb_main’ and ‘adb_read_all_stripes’ may be reported in the SAP Adaptive Server error log during the execution of LOAD DATABASE of an archive database dump. |
| 822233 | The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'memfreeheap' together with a stack trace that include the module 'rbld_rebuild_indexes' may be reported in the SAP Adaptive Server error log after a 1530 error, "Create index with sorted_data was aborted because of row out of order. Primary key of first out of order row is < row data > ", is reported. |
| 822247 | When a workload is captured from an ASE server that has an active Backup Server, SAP ASE Workload Analyzer may fail to compare a replay and its original workload with an error like "Replay comparison failed. Attempt to insert NULL value into column 'tpcq_querytext', table 'sybcatdb.dbo.t_topperfchgqrys_cap'". See KBA 2947687. |
| 822266 | NFR: setuphadr enable XA replication for new setup. |
| 822314 | A 3114 error, "Database master does not have an entry in Sysdatabases.", may be reported in the SAP Adaptive Server error log when loading a full database dump of the master database which was taken on a system that has been upgraded from pre-16.0 to 16.0 SP03 PL08 release. See KBA 2974405 |
| 822402 | In rare circumstances, a process may indefinitely sleep in the module 'xls_flush_plcqueue' and may block other processes running in the SAP Adaptive Server when the configuration option 'user log cache queue size' is enabled. The system may appear to hang and only restarting Adaptive Server will unblock this situation. See KBA 2594508. |
| 822432 | The message, "Assertion (!"ins_insert(): SSA_STMTLOCK is not set")", may be reported in the SAP Adaptive Server error log when a deferred update is executed and the diagserver binary is in use. |
| 822443 | The messages, " < date-hour-timestamp > : A00: E-Diag: C_QATRACE command received." and " < date-hour-timestamp > A00: E-Diag: Received the trace flags bitmap. Tracing within sybmultbuf is enabled." are automatically archived in the SAP Backup Server error log unnecessarily. |
| 822570 | After loading a database dump from a platform having a different endianness, Rep Agent may fail to start. The message "Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation." may be reported in SAP ASE error log, together with a stack trace showing the modules 'memmove', 'anch__log_anchor' and 'ra_put_credentials' See KBA 2969667. |
| 822622 | In rare circumstances, the message "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'ra_ci_stpmgr_thread' may be reported in the SAP Adaptive Server error log when sap_teardown is executed and the Rep Agent is stopped in an HADR setup. See KBA 2962144. |
| 822677 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 'buf__writewait', 'buf__free_side_mass' and 'iocRunController' may be reported in the SAP ASE error log when DBCC INDEXALLOC is executed on an encrypted database and the configuration option 'enable LFB index' is active. |
| 822678 | In rare circumstances, the message “timeslice < negative-value > , current process infected” in the module ‘ex_subhandle’ together with a stacktrace which includes the modules ‘dpdb_main’ and ‘des_checkpoint_flush_sysstats’ may be reported in the SAP Adaptive Server error log during the execution of DUMP DATABASE on a heavily loaded setup. |
| 822683 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'des_getval' together with a stack trace that includes the modules 'mem__free_this_phdr' and 'mem_procmem_lastchance_cleanup' may be reported in the SAP Adaptive Server error log during cleanup of 706 error, "Process < spid > tried to remove PROC_HDR < address > that it does not hold in Pss.". See KBA 2965455. |
| 822699 | The message, "Assertion (E_CALLER_REORG_REBUILD(pss)) failed", may be reported in the SAP Adaptive Server error log when the built-in object_id( < object-name > ) execution fails and when the diagserver binary is in use. |
| 822842 | In rare circumstances, SAP Adaptive Server Workload Analyzer may report more sessions than actual when a capture/replay is re-analyzed after its previous analysis has failed. |
| 822957 | The maximum allowed capture or replay name in SAP ASE Workload Analyzer Command Line Utility is extended from 30 characters to 50 characters. See KBA 2978666. |
| 822971 | The message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace in either the module 'mda_fill_and_send_monProcess' or 'mda_fill_and_send_monProcessLookup' may be reported in the SAP Adaptive Server error log when either the monProcess or monProcessLookup MDA table is queried while a Backup Server is running. |
| 822998 | In an HADR setup, when SAP ASE Rep Agent performs a mode switch to 'async' while the stream is concurrently being closed, the message, "Current process (0x0) infected with signal 11 (SIGSEGV)", may be reported in SAP Adaptive Server error log together with a stack trace which includes the modules 'STSendMsgs', 'ra_ci_send_mode_switch_message' and 'ra__ci_background_task_wait_for_srs_ack'. See KBA 2975520. |
| 823009 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the module 'rvm__audit_dbreference' may be reported in the SAP error log when ASE user modifies the owner of encryption key created by another user and auditing system has been setup to audit this event and granular permissions are enabled. See KBA 2984145. |
| 823107 | The message ERROR_INVALID_FUNCTION may be reported in the ASE_Suite.log file on a new installation. See KBA 2979449. |
| 823277 | In rare circumstances, the message, “Thread CAP Parser( ) infected with signal 11.”, together with a stack trace which includes the modules ‘exc__appDumpStack’, ‘exc_terminate’ and ‘strlcpy’ may be reported in the SAP Replication Server error log when an unexpectedly empty log record is processed under an HADR setup resulting in the replication flow to stop. |
| 823325 | The message, "Current process infected with signal 11 (SIGSEGV)", together with a stack trace which includes the modules 's_setupvar' and 'subgoals' may be reported in the SAP ASE error log on HP-UX platform when SELECT @@ssl_protocol is executed and the configuration option 'enable ssl' is enabled. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP04, ASE SP04, SP04, Adaptive Server Enterprise, Fix, Patch, Error, Bug , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)