SAP Knowledge Base Article - Preview

2661920 - Targeted CR List for ASE 16.0 SP02 PL08

Symptom

The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in future Adaptive Server Enterprise (ASE) EBF/SP or PL releases. Please be sure to read the Disclaimer below.

If the EBF/SP has been released, check the CR list and coverletter at the service.sap.com.

Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.

CR NumberDescription
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
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.
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.
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 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.
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.
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.
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.
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 low LIO estimate with a poor index being chosen for the plan, resulting in poor performance.
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 jvm.wl 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 TF 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.
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'.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 SYBASE Technical Support. (current marker = ( < page# > , < rowid > ))." may be reported in the SAP ASE error log when LOB data is replicated. See KBA 2567397.
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).
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.
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.
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.
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 Correct a couple of typos 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.
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.
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.
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.
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.
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
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 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.
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.
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.
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.
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 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
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.
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.
814095 Under rare circumstances, SAP ASE may hang at startup during engine online, when config parameter 'kernel mode' = process. See KBA 2635465.
814192 The dbo and table owner can grant explicit decrypt permissions on an encrypted column when both the options 'enable granular permissions' and 'restricted decrypt permission' are enabled. 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.
814240 The message, "Current process infected with signal 11" 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.
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.
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.
814462 If the option 'enable dump history' is enabled and the DUMP or LOAD command uses the syb_tsm library with more that 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.
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.
814590 ddlgen may generate wrong syntax for sp_tempdb when a login is bound with a tempdb group. 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 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.
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.
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.
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.
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.
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.
814968 Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled.
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'.
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 ASE runs into an exception during parallel execution.
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.
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 the stored procedure "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.
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.
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.
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.

Read more...

Environment

  • AIX 64bit
  • HP-UX on IA64 64bit
  • Linux on Power 64bit
  • Linux on x86 64 64bit
  • Solaris on Sparc 64bit
  • Solaris on x86 64 64bit
  • Windows on x64 64bit

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR, CR List, ASE 16.0 SP02 PL08, ASE SP02 PL08, SP02 PL08, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , Problem

About this page

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

Search for additional results

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