/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
The purpose of this KBA is to help SAP customers obtain a general idea of potential fixed situations in Adaptive Server Enterprise (ASE) 16.0 SP03 PL05. Please be sure to read the Disclaimer below.
If the EBF/SP has been released, check the CR list and coverletter at the support.sap.com.
Disclaimer: This document lists the targeted (not committed) release dates and the targeted fixed CR list for each release. Please be aware that the purpose of this posting is solely to provide you, our customers with estimated release dates and targeted CR lists. SAP does not commit to releasing on the specified dates or to including the CR fixes in the said release. While every effort will be made to meet the said targets, changes can occur at any time. It is also possible (although unlikely) that SAP may decide not to release an EBF/SP that was previously scheduled for release.
| CR Number | Description |
|---|---|
| 55716 | If a database device does not have any segment associated with it, sp_helpdb incorrectly prints the usage of this device fragment as "data only" instead of "unused by any segments". |
| 636236 | A 14108 error, "Could not find partition descriptor for objid < value > , indid < value > , ptnid < value > in dbid < value > .", may be reported during SELECT INTO a LOB column from a source table with a non-LOB column. See KBA 2624460. |
| 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. |
| 778507 | Compact output is now provided for REORG DEFRAG and REORG COMPACT utilities. |
| 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. |
| 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. |
| 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. |
| 804695 | The message, "xpserver is using enhanced security", is repeatedly reported in the SAP ASE error log. See KBA 2412523. |
| 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. |
| 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. |
| 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. |
| 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. |
| 809412 | A new option 'delete' has been added to the system stored procedure sp_dump_history to delete records that contain the stripe name and/or dump_date specified. A backup of the previous dump history file is generated. |
| 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. |
| 811135 | After an upgrade, a 10330 error, "INSERT permission denied on object < obj_name > , database < db_name > , owner < username > ", may be reported when procedures are executed by a user without explicit permissions on the underlying objects ( only partitioned tables) in the procedures. See KBA 2560832. |
| 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. |
| 811581 | Under certain circumstances, SAP ASE may hang during a DML operation when Latch Free Btree indexes are used and the Lock Less Data Cache is enabled. |
| 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. |
| 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'. |
| 811784 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'LeCacheDMLOp::_LeOpAcquire' together with a stack trace that includes the modules 'LeEmittOp::_LeOpAcquire' and 'LePlanAcquire', will be reported in the SAP ASE error log if the user attempts to use a table UDF as a scalar UDF in a SELECT statement. |
| 811884 | On Solaris platform, a 2812 error, "Stored procedure can not be found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)", and a 267 error, "Object not found", will be reported when creating a Global Temporary Table with a name of length 255. |
| 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. |
| 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. |
| 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. |
| 812411 | A couple of typos have been corrected in the exception messages for "an unforeseen exception" and "an array bounds exceeded". |
| 812497 | In rare circumstances, a 11324 error, "In database ' < name > ', the server failed to open required table ' < id > '. Please contact SAP Technical Support.", may be reported in the SAP ASE error log when the system stored procedure sp_reptostandby with the option 'NONE' is executed while a concurrent session is dropping the table reported in the error message. Instead, a 11305 error, "Failed to open the object ' < id > ' in database ' < name > ' while executing the built-in function setdbrepstat(). Check if the object exists and retry the operation.", will be reported. |
| 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. |
| 812852 | The value of parameters for some datatypes such as BINARY and VARBINARY in dynamic SQL may not be printed out in the output of "sp_showplan 'long'", "select query_text( < spid > )" or the deadlock SQL text. |
| 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. |
| 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. |
| 813102 | A 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page. Rid pageid = < value > ; row num = < value > . Page pointer = < value > , pageno = < value > , status = < value > , ptnid = < value > , indexid = < value > , level = < value > , pnextrno = < value > ", may be reported in the SAP ASE error log when an IMRS enabled database is replicated and there is very high activity on the database. |
| 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. |
| 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. |
| 813315 | When dropping a SQLScript database, a 3906 error, "Attempt to BEGIN TRANSACTION in database < dbname > failed because database is READ ONLY", may be reported against another database < dbname > that is not the SQLScript database being dropped. |
| 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. |
| 813520 | In rare circumstances, a 12309 error, "Expanding update on object < name > in database < name > cannot succeed on page < number > , because the contiguous_free_bytes of < value > is less than the difference of < value > between new rowlen and old rowlen. This is an internal error. ASE is terminating this process.", may be reported in the SAP ASE error log together with a stack trace which includes the modules 'dol__expand'/'dol__delete_insert' and 'dol_update' while performing an expanding UPDATE on a table that is stored in an On-Disk MVCC enabled database. |
| 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. |
| 813573 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'pss__release' together with a stack trace which includes the modules 'quitfn_indirect' and 'pss_unkeep' may be reported in the SAP ASE error log when a task disconnects after executing some queries that involve INDEX scans on MVCC enabled tables. |
| 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. |
| 813662 | The message, "Current process infected with signal 8 (SIGFPE)" in the module 'imrs_get_pdes_imrs' together with a stack trace which includes the modules 'altertab' and 'alt__set_option' may be reported in the SAP ASE error log when 'ALTER TABLE < name > SET ROW_CACHING ON' is run in an IMRS enabled database after LOAD DATABASE was run. |
| 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. |
| 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. |
| 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. |
| 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. |
| 814003 | A 913 error, "Could not find row in sysdatabases with database id < dbid > ", may be reported when dropping a versioned temporary database after dropping an user database which is marked suspect and is On-Disk MVCC enabled. |
| 814029 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'iocmResize' together with a stack trace which includes the modules 'cfg_notify_iotasks' and 'cfg__notifyconfig' may be reported in the SAP ASE error log when the value of config parameter "number of disk tasks" or "number of network tasks" is changed at run-time and then reverted back to the earlier value. |
| 814032 | A 6812 error, "Failed to PACK < x > inserted and < y > migrated rows in IMRS for partition ' < name > ' with partition id < value > and indid < value > of table ' < name > '" may be reported when CREATE CLUSTER INDEX is run in an IMRS enabled database after boot/load recovery. |
| 814121 | In rare circumstances, Rep Agent may terminate with a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < database name > ' because the target page is not a data page.". |
| 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. |
| 814217 | IMRS Cache size estimation done by Workload Profiler has been improved by accounting kernel overhead memory accurately. |
| 814240 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'CtlibRemoteAccess::getSubstValue' together with stacktrace that includes the moedules 'CtlibRemoteAccess::getColumnValues' and 'RPCRemoteAccess::getNext', may be reported in SAP ASE error log when 'granular permission' is enabled and a query, involving user created built-in functions and proxy tables, is executed. |
| 814301 | In rare circumstances, the message, "DROP DATABASE could not clean < amount_of_unreleased_memory > bytes from the row storage cache, ' < imrs_cache_name > '. Please drop and recreate the cache before reusing it.", might be reported by DROP DATABASE, in case DMLs or imrslog_thresholdaction was running concurrently with DROP DATABASE command on the same database. |
| 814304 | In rare circumstances, SAP ASE may not find an abstract plan on disk during the re-compilation of a cached query which may result in a sub-optimal performance when the query is executed. |
| 814317 | The message, "Assertion (!imrv- > imrv_xprev_verp || imrv_drc_prev) failed", may be reported in the SAP ASE error log, when a savepoint is added within an active transaction after executing DMLs against on-disk MVCC enabled tables and diagserver binary is in use. |
| 814325 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'ridmap_update' together with a stack trace which includes the modules 'imrs_insert' and 'dol_insert', may be reported in the SAP ASE error log when inserting data into a Data Only Locked table in an IMRS database. |
| 814327 | The set command in the backupserver does not accept parameters values including blanks. The command has been changed to accept parameters to be enclosed in either single or double quotes, or between square brackets. |
| 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. |
| 814341 | In rare circumstances, DML/scanner using isolation level 1 or isolation level 2 may skip committed INSERTED rows, if IMRS_PACK task is concurrently packing same set of rows. |
| 814358 | In rare circumstances, during boot time recovery of an IMRS enabled database some transactions may be ignored when the Adaptive Server is impolitely shut down and the corresponding IMRSLOG pages for these transactions are located 512 pages beyond the last fully committed transaction and a previous boot time recovery did not recover IMRSLOG. The message, "Empty oldest insert xact. No need to run imrslog recovery.", is reported in the SAP ASE error log. |
| 814397 | sp_sysmon_repagent system stored procedure raises "insufficient result space" error for replicated database IDs larger than 3 digits (999). See KBA 2628080. |
| 814433 | A 12336 error, "Definition time object 'database ' < dbname > ' ( < dbid > ), object ' < objname > ' ( < objid > )' found at run time as an attempt to drop the table had failed in a previous query. Please drop the above mentioned table using the DROP TABLE command." may be reported when trying to access a table after loading a database dump that was taken while the table was being created. |
| 814445 | In some rare scenarios, parallel execution of a query hangs when dynamic thread allocation feature is on and the query plan contains LeRestrictOp in the right subtree of LeMJOp. See KBA 2642040. |
| 814462 | If the option 'enable dump history' is enabled and the DUMP or LOAD command uses the SYB_TSM library with more than one stripe, the stripe name stored in the dump history file for each of the stripes will be the result of concatenating the previous stripe name. When the length of this is greater than 255 bytes, a 11076 error, "The name '' is too long. Maximum length is 255." will be reported, although the dump itself is successful. See KBA 2629866. |
| 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. |
| 814479 | A 18121 message, "Unrecognized change attribute option." is reported in the SAP ASE error log when the procedure sp_chgattribute is used to change the 'optimitistic_LFB' attribute of an index. |
| 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. |
| 814574 | A 12832 error, "The LDAP URL string ' < LDAP server URL > ' is invalid. LDAP subsystem reported error 'Can't contact LDAP server'", may be reported when using sp_ldapadmin to create secure LDAP connections. |
| 814583 | Under rare circumstances, the message "One or more entries in the data segment free space counts in database ID < value > was found to be negative and has been set to 0." may be reported many times in the SAP ASE error log. The message is enhanced to include fragment information and a corrective action and is printed only once for the same fragment. The new message text is, "The free space count for fragment with lstart < value > in database ' < dbname > ' was found to be negative and has been set to 0. Execute 'DBCC USEDEXTENTS( < dbname > ,0,1)' in single user mode to correct this count.". |
| 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. |
| 814619 | The message, "Extending database by < value > pages ( < value > megabytes) on disk master", may be reported instead of a 5044 error, "ALTER DATABASE failed. Database < dbname > cannot be larger than the smallest database ( < dbname > ) that uses it as a template.", when ALTER DATABASE is run to extend a template database being used by a relaxed durability database whose size cannot accommodate the new size of the template database. |
| 814639 | Under an HADR setup when stream replication in enabled, sometimes the last command replicated is not confirmed by Adaptive Server and hence not applied on the standby database by Replication Server if there is no activity occurring in the primary database following that last command execution. |
| 814649 | A 325 error, " Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact SAP Technical Support.", may be reported when a query, which involves columns from an INNER JOIN being used in an ORDER BY clause, is executed against a VIEW and ROW LIMIT is applied. |
| 814657 | In rare circumstances under an HADR setup, a 9414 error, "server RepAgent( < dbid > ): Streaming replication stream CI Library error -1 with severity 2 and message 'Producer receiver ' < db_name > ' failed to receive data, shutting down transport to 'ocs:host:port'.'. Rep Agent detected error 3 with message 'Unknown' at line 0 in file nofilename.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent hang. |
| 814674 | In some cases, wrong results may be returned when executing a stored procedure containing views that might need to be recompiled. |
| 814714 | A 3702 error, "Cannot drop or replace the database ' < db name > ' because it is currently in use.", may be reported when dropping the versioned temporary database after switching off the version storage using "ALTER DATABASE < db name > VERSION STORAGE OFF" on user database. |
| 814743 | In rare circumstances, after taking a database dump of an IMRS enabled database, if operations on imrs_inserted rows stop for some time such that none of the log records between the oldest_inserted_xact and lastxact contain VRIDs, and there is a REBOOT followed by new inserts and a transaction dump taken, then loading the dumps may cause data corruption. |
| 814745 | The message, "kernel ssl_nrpacket_iocp: vsn 18 kpid 20250779 sossltdsremaining 0 bytestoread 29 iostatus ZERO", may be reported in the SAP ASE error log when SSL is enabled. |
| 814762 | In rare circumstances, in an HADR setup when an IMRS database is replicated and the stream replication mode is enabled, the Rep Agent may sometimes send to Replication Server inconsistent Origin Queue ID (OQID) values that will prevent the Replication Server from draining its Simple Persistent Queue (SPQ) correctly. |
| 814771 | For charsets involving multi-byte characters, example EUCJIS, sp_autoformat might incorrectly truncate data in the column, which can affect outputs of sp_helpdb, sp_helpdevice and other sprocs using sp_autoformat. See KBA 2637280. |
| 814782 | MERGE statement that does not perform any action may incorrectly return a rowcount different than zero. |
| 814788 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'func2view' followed by a stack trace that includes the modules 's_crtproc' and 'sequencer', may be reported in the SAP ASE error log when creating an in-lined Table-Valued SQL-based User Defined Function without SELECT statement. |
| 814806 | A 692 error, "Uninitialized logical page ' < number > ' was read while accessing database ' < name > ' ( < dbid > ), object 'sysimrslogs' (59), index 'sysimrslogs' (0), partition 'sysimrslogs_59' (59). Please contact SAP Technical Support.", may be reported in the SAP ASE error log when a SELECT-INTO from sysimrslogs command is executed. |
| 814828 | The role status shown in syssrvroles system table may not be correct after upgrading a 15.0.3 or 15.5 server to 16.0 SP03 or later version. |
| 814837 | The message, "Current process infected with signal 11 (SIGSEGV)" in the module 'mem__pageallocate_this_engine' together with a stack trace which includes the modules 'mem_pageallocate', 'mem_getpages' and 'hashbifs_md5_lerun', may be reported in the SAP ASE error log when using hashbytes() built-in with MD5 algorithm and input arguments as NUMERIC/DECIMAL/MONEY. See KBA 2636316. |
| 814870 | A 10330 error, "Access permission denied on object < objname > , database < dbname > , owner < username > ", may be reported when a stored procedure is executed by a user that does not have explicit permissions granted on the underlying referenced objects in the stored procedure, such as partitioned tables and user defined functions, while SAP ASE renormalizes the stored procedure from its text. |
| 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. |
| 814895 | The message, "Assertion (rowstate != UNCOM_DEL)" together with a stacktrace which includes the modules 'bt__lock' and 'bt__savekeynblk', may be reported in SAP ASE error log when isolation level 3 scans are executed against IMRS enabled tables while the diagserver binary is in use. |
| 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. |
| 814919 | In rare circumstances under an HADR setup, a 12406 error, "Failed to find the last row marker for transaction ( < pagenum > , < rownum > ) in sysimrslogs for database ' < dbname > ' ( < dbid > ). The sysimrslogs row is corrupted.", may be reported during boot-time recovery of an IMRSLOG enabled database when stream replication is enabled. |
| 814923 | In rare circumstances, the message, "Current process infected with signal 11 (SIGSEGV)" in the module 'kbfalloc' together with a stack trace which includes the modules 'ra_malloc_mempool' and 'ra_mempool_alloc_internal', may be reported in the SAP ASE error log when the Rep Agent Secondary Truncation Point (STP) Manager Thread terminates abnormally leading to corruption in the Rep Agent Memory Pool. |
| 814927 | In rare circumstances on a heavily-loaded system, DROP INDEX may hang when the SAP ASE configuration option "hcb index auto tuning" is enabled and the HCB AUTO TUNING process is now sleeping and was working on the corresponding index. |
| 814962 | A 2512 error, "Table Corrupt: Cannot find the specified row number < value > , in index page < value > , partition ID < value > , on data page < value > .", may be reported when running DBCC CHECKTABLE and after loading a transaction dump that was taken while a concurrent committing transaction and the ckeckpoint log record written by DUMP TRAN was stored interleaved with the committing transaction log records in such a way that the fullycommitxact marker in the dump header is set to the dump instant of the IMRSLOG database. |
| 814968 | Performance degradation in SAP ASE may be observed when 'enable granular permissions' is enabled. |
| 814983 | In rare circumstances under an HADR setup a 623 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the target page is not a data page.", or a 624 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the requested RID has a higher number than the last RID on the page.", or a 625 error, "Adaptive Server failed to retrieve a row via its RID in database ' < name > ' because the entry in the offset table for that RID is less than or equal to 0.", may be reported by the Rep-Agent scanner of IMRSLOG when a re-scan occurs and stream replication is enabled on an IMRS database. |
| 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'. |
| 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. |
| 815110 | In rare circumstances under an HADR setup, a 9219 error, "RepAgent( < dbid > ): Internal coding error.", may be reported in the SAP ASE error log when stream replication is enabled on an IMRS database that may result in Rep Agent implicit shut down or hang. |
| 815161 | A 8006 error, "ASE error detected by Backup Server. Refer to the preceding Backup Server message.", together with a stack trace that includes the modules 'dmp_send_dpm' and 'dpdb_main', may be reported in the ASE error log and the counterpart error, "3.15.2.1: The disk piece for page < number > does not belong to phase 2.", in the backup server error log when DUMP DATABASE is run while taking a database dump of an IMRS enabled database and the configuration parameter 'optimize dump for faster load' is enabled. |
| 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. |
| 815399 | In rare circumstances, DBCC CHECKTABLE may report index inconsistencies on an IMRS enabled table, after LOAD DATABASE followed by one or more of LOAD TRANSACTION commands using the backward scan recovery strategy were executed. |
| 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. |
| 815730 | Performing a downgrade from SAP ASE 16.0 SP03 PL04 may report a failure on 'sysindexes.status4' columns for user tables having a Latch Free Btree index on big-endian platforms, such as Solaris, IBM pSeries Linux, IBM AIX and HP Itanium platforms. |
| 815821 | When Rep Agent is configured for stream replication in an IMRS enabled database and a retriable stream error occurs, the message "current process infected with 11 (SIGSEGV)" in the module 'ubffreef' together with a stack trace which includes the modules 'ra_free_mempool' and 'ra_ci_stp_remove_all_oqid' may be reported in the SAP ASE error log resulting in Adaptive Server terminating abnormally because of RAMEM_SPIN spinlock being held. |
| 815835 | In rare circumstances under an HADR setup during failover, a 644 error, "Index row entry for data row id ( < pagenum > , < rownum > ) is missing from index page < pagenum > of index id < value > of table < name > in database < name > . Xactid is ( < pagenum > , < rownum > ). Drop and re-create the index.", may be reported in the SAP ASE error log during SAP ASE boot time when synchronous replication is enabled and special recovery finds that the transaction up to which all the transactions are persisted on the standby ASE is behind the fully committed transaction marker in the primary SAP ASE. |
| 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. |
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 SP03 PL05, ASE SP03 PL05, SP03 PL05, Adaptive Server Enterprise, Fix, Patch, Error, Bug , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)