/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 future Adaptive Server Enterprise (ASE) EBF/SP or PL releases. Please be sure to read the Disclaimer below.
If the EBF/SP has been released, check the CR list and coverletter at the service.sap.com.
Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.
| CR 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". |
| 497173 | Executing sp_tables against a User Defined Function may report some status incorrectly. See KBA 2411224 |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 772020 | The XML output of cached plans may lead to XML parsing errors if it contains parameters values with XML meta-characters like '&', ' < ' or ' > '. |
| 778507 | Compact output is now provided for REORG DEFRAG and REORG COMPACT utilities. |
| 781679 | The time stamp that is used to generate the dump file names during the execution of DUMP DATABASE / TRANSACTION USING CONFIG commands, that are typically named using the format 'database_name.dump_type.date-timestamp.stripeID', has been enhanced to ensure they are unique. See KBA 2693916. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 795426 | The built-in function REPLICATE (char_expr | uchar_expr, integer_expr) may return an incorrect result when turning TF 244 off and integer_expr is a constant expression. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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*'. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 804186 | For complex queries, identification of physical operators in the final plan becomes difficult. This enhancement adds an ID to each POP operator in showplan output when 'show long', 'show normal' or 'XML output' is switched on and traceflag 11826 is active. See KBA 2723236. |
| 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. |
| 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. |
| 804695 | The message, "xpserver is using enhanced security", is repeatedly reported in the SAP ASE error log. See KBA 2412523. |
| 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. |
| 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. |
| 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. |
| 805571 | Only relevant for Business Suite extensions of SAP ASE: An invalid error 102 "Incorrect syntax" might be observed while running select on table with space in the table name if quoted identifier is set to true. |
| 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. |
| 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 fix can be enabled by runtime trace flag 11838. |
| 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. |
| 806370 | When auditing of sso_role is enabled, unexpected audit records may be generated against users without sso_role. See KBA 2441754. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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.". |
| 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. |
| 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'. |
| 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. |
| 808794 | Improvements have been made to audit logging. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 810312 | A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > ." 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 810985 | When a table that has a UNITEXT column is marked for replication sometimes the data may not be replicated correctly. |
| 810995 | SAP ASE running on Microsoft Windows on a virtual machine can hang when encountering a resource issue on the VM. See KBA 2542797. |
| 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. |
| 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. |
| 811176 | setuphadr is enhanced to support SSL connections for Backup Server. |
| 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. |
| 811265 | Incorrect run sizes for the data caches may be reported by sp_sysmon with the "cache wizard" option. See KBA 2540661. |
| 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. |
| 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. |
| 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. |
| 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 were the dump was taken. See KBA 2556287. |
| 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. |
| 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. |
| 811714 | On Windows platform, the error message, "Could not start 'openssl pkcs12 -export -in < input_file > -out < output_file > -name < server_name > ....', The system cannot find the file specified", may be reported during HADR setup. |
| 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. |
| 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'. |
| 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. |
| 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. |
| 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. |
| 811935 | DBCC page() command is enhanced to print character encoding information. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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). |
| 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. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 812522 | In rare circumstances, the message, "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.", maybe raised when printing sql text and following with the stack trace in the module 'prE_PARAMs_buf' in SAP Adaptive Server error log. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 812955 | Even after the successful application of the fact_table_hint, optimizer constructed the final plan using the subplan generated for compatibility mode. |
| 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. |
| 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 |
| 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. |
| 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. |
| 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 > '". |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 813752 | Diagnostic tracing for "SSL handshake failed" errors has been added. The diagnostic tracing can be enabled through traceflag 7867. See KBA 2633020. |
| 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. |
| 813886 | Under rare circumstances, a connection may hang after receiving a cancel request from the client. See KBA 2633664. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 814192 | Improvements have been made to the configuration option "restricted decrypt permission". See KBA 2623174. |
| 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 2636316. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 814357 | A 632 error, "Attempt to move memory with an incorrect length of < value > . Maximum allowed length is < value > ", may be reported when executing a query against the monMemoryUsage MDA table. |
| 814397 | sp_sysmon_repagent system stored procedure raises "insufficient result space" error for replicated database IDs larger than 3 digits (999). See KBA 2628080. |
| 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. |
| 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. |
| 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. |
| 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.". |
| 814590 | DDLgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. See KBA 2632662. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| 814916 | In a HADR installation, a new $SYBASE/DM/dir.properties file is added to capture the Custom Directory Information specified during HADR configuration. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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". |
| 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. |
| 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. |
| 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. |
| 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 DATATBASE 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 815944 | In rare circumstances on an HADR setup, the message, "Current process infected with signal 11 (SIGSEGV)" together with a stack trace which includes the modules 'ra_free_mempool' and 'ra_dealloc_ra_xact', may be reported in the SAP ASE error log when synchronous replication is enabled. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| 816425 | 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. |
| 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. |
| 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. |
| 816639 | An extra line may be printed between the header and the actual content in the sp_helpdb output. |
| 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 > . |
| 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. |
| 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. |
| 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. |
| 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. |
| 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'. |
| 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. |
| 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. |
| 817431 | Update the SAP ASE integrated JREs to SAP JRE 8.1.046 and SAP JRE 7.1.060. |
Read more...
Environment
- AIX 64bit
- HP-UX on IA64 64bit
- Linux on x86 64 64bit
- Solaris on Sparc 64bit
- Solaris on x86 64 64bit
- Windows on x64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR, CR List, ASE 16.0 SP02 PL08, ASE SP02 PL08, SP02 PL08, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , white-list , white , white space character , 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)