SAP Knowledge Base Article - Preview

2087861 - Targeted CR List for ASE 15.0.3 ESD#3


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

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



New Feature: User-defined default execution attributes.


When User create record session without enable "sybase_script", Recording into ASE database not working.


Dump / Load command having archive device name with newline character does not get parsed appropriately and causes segmentation fault in sybmultbuf.


Occasionally on a multi-engine system, sp_monitorconfig "Active procedure cache" values might be higher than configuration value


change the description for the IndexID column in monCachedObjects table.


DDLGen: DDLGen incorrectly generates foreign key contraints for tables that do not have any if the tables have a object_ids that match referencing tables in other databases.


To remove the message of 'per object statistics active' configuration parameter required for monProcessActivity table.


allow concurrent access to the table while doing Reorg Rebuild or creating clustered index


ALTER DATABASE might take an uneccessarily long time to complete the extension of a large database when the database has been extended over a boundary that is a multiple of 63 GB.


Newly added audit options are not removed when downgrading from 15.0.2 to 15.0.1.


The message, "Current process infected with signal 11 (SIGSEGV)", may be reported in the errorlog together with a stacktrace which involves the modules '_StTcCharacterSample' and 'StTcMrgBnds' when executing a SELECT query with an IN list on encrypted columns.


In rare circumstances, Adaptive Server may give a time slice error with a stack trace which contains modules 'cm__check_page_range' or 'cm_choose_buffer_pool'.


During instance startup, a set of three messages is logged, if a secondary interconnect is not defined for the cluster. Messages are: "The cluster interconnect protocol has not been defined in the cluster input file", "Cannot resolve host name '' for the local interface of the link to monitor", and "Cannot resolve host name '' for the remote interface of the link to monitor".


Under rare circumstances, dbcc checkalloc might report a 2525 error: "Table Corrupt: Object id wrong" with "objid in ext=0" following an ONLINE DATABASE after loading two or more transaction logs.


In rare circumstances, datatype field in c6 column in sysstatistics FMT_COLUMN formatid row might be corrupted during upgrade during online database after the database is loaded across platform where byte-order is different, if the table has more than 255 columns.


Add option to remove server entry after disconnecting from ASE.


sp_configure may encounter error message 10840 with error message, "Internal error, FDP API, fdp_get_memory(): Failed to allocate 2097061 bytes.", in the errorlog.


Query performance may be affected on queries involving private temp tables for which optimizations are based on some magic numbers when statistics are not explicitly updated on the tables. An option is provided to implicitly generate statistics for private temp tables. The statistics are kept in memory until the temp table is dropped. Traceflag 2716 is used to turn on this option. Note that external tools such as optdiag and sp_modifystats will not affect the in-memory statistics. The feature does not support regular, partitioned and proxy tables, as well as optdiag output, compatibility mode and DDLs in stored procedures when deferred compilation is turned off.


In rare circumstances, a 834 error, "Illegal attempt to clean buffer" together with a stack trace which includes modules 'dbt_unreserve()' and 'cm_dbclean()' may be reported in the error log when dropping a suspect database.


diagserver could run into assertion fail when 'enable stmt cache monitoring' enabled.


Occasionally, when ASE write the logfile to dumpfile,"Error: I/O error, errno: 5 "may be reported in the errlog.


A new builtin function is_singleusermode is created to determine if server is in single-user mode. sp_downgrade will force the server to be in single-user mode before downgrade is performed.


When you run dump database command on ASE of sjis and Backup Server of eucjis, Backup Server outputs some Open Client/Server errors below and dump database command does not respond. Open Server Error: 16368.10.0.0 srv_senddone(): A message was initialized, but not completed


If the PCI subsystem fails to startup then stack traces may be seen preventing ASE from booting.


Attempting to retrieve data inserted using a deferred INSERT command for a table created with the "ignore_dup_key" clause and having TEXT columns may fail with a fatal 7114 error reading "Page < Page Number > is not a valid text page." together with a stack trace showing modules "sendtext" and "get_txtpage".


Monitor Historical Server process memory usage keeps growing while recording a session.


ASE does not check if the type of the supplied default value matches the type of the column at user table creation time.


A new column "Transactions" has been added to the monState table


dbcc stackused reports the wrong maximum amount of stack memory used on Itanium platforms.


If built-in function like data_pages(), which accesses OAM pages is called on a table in temporary database while the table is being dropped error 677 may be raised.


Incorrect information is displayed under "data cache managementt" section of sysmon report.


The index checking of DBCC CHECKTABLE doesn't check the first row of every non-leaf page, so it can't check out the corrupt index if someone of first keys is bad.


A 10334 error, "Permission related internal error was encountered. Unable to continue execution." may be reported in errorlog while running the DBCC CACHEDATAREMOVE command.


Replicating data into an encrypted column that is bound to a domain rule fails with error 225. The same failure can occur when inserting data through bcp using the -C flag.


Executing a query involving views and coalesce() may get error 4409 incorrectly.


When using builtin function object_owner_id(), if the object name is longer than 30 bytes, the builtin could return wrong owner id for the object.


PC Client 1503 ESD#1 Installer log.txt file show error message


Feature request for a dbcc command to fix 100004 checkstorage faults (timestamp value in page header larger than database timestamp).


A 8242 error "The table < table_name > in database < dbname > is bound to metadata cache ..." maybe raised when doing delete operation on a DOL table that is bound as hot object using DBCC TUNE 'des_bind' command.


CREATE EXISTING TABLE command against MSSQL backend results in Msg 11213 if the remote column is defined with a DEFAULT clause. In the same situation, CREATE PROXY_TABLE fails silently and does not return any error.


The builtin function valid_name() could cause stacktrace if NULL is passed as the second parameter.


Sometimes, ASE terminates connection to the client after error 603, "not enough system session descriptors available" occurs.


Incorrect referential interity (RI) check could happen for update/delete when there is mixed datatype equijoin between the RI column and another column. The similar mixed datatype equijoin under a view could also lead to wrong result when the view is joined to itself and has to be materialized into a worktable first.


When upgrading the server which is booted with single user mode, upgrade utility was not able to perform. It required 4 connections to finish the upgrade work. And it can finish the work with only one connection.


sp_dbcc_summaryreport is expanded to support the exclusion of faults registered in the dbcc_exclusions table like sp_dbcc_faultreport does.


When a cursor is implicitly updatable, i.e. does not have a FOR UPDATE clause or a FOR READONLY clause, and at least one index is available, then a table scan will not be considered. This change will allow a table scan to be considered if there are no unique indices available. The change was placed under optcriteria cr562947 and will be on by default for 15.0.3 ESD #2.


preupgrade utility should identify stored procedures that use depreciated function calls such as reserved_pgs().


The message reported in the ASE server log when the sybpcidb database does not exist has been improved and now contains more information. The new message suggests that the sybpcidb database may be missing, or it may need to be initialized with the installpcidb script.


signal 11 could happen in ResRelOp() during codegen when a constant expression from a view or derived table is SELECTed from an outer join view inner side and the constant expression is further participating in a simple WHERE clause (comparison involving other constant only) when the outerjoin view is queried.


Under compatibility mode, traceflag 302 diagnostics might output "unnamed-col" for predicate printing instead of the real column name.


Using a large value for 'max memory' and setting 'allocate max shared memory'=1 may cause the shared memory dump size to be much bigger than expected against SYBMON.


Add ability to kill process querying syslocks table.


Message 14623 doesn't provide enough info for users to perform corresponding operations to continue downgrade. It should provide more infomation like which objid and indid the row has.


Modifying a segment's auto expansion attributes (grow-by or max-size) results a syntax error.


Signal 11 in GtuUnion::GtSecondaryInit() may be seen in the error log and the spid terminated when selecting from a view containing a union all and the select includes > 1 variable assigment from the same column.


sp_object_stats "00:01:00" does not produce output in version 15.0.x even if you have contention.


Due to an issue with underlying dbcc checktable, sp_post_xpload can not detect all kind of index corruption, such as first key of one non-leaf page is bad. The new 'force' option of sp_post_xpload will force rebuild all the index except APL clustered index.


ddlgen generates a redundant "go" between the two ENDs for dropping the primarykey and foreignkey


If statement cache is turned on and exception is occur in compiling a statement with temporary tables in it, it could raise 8203 error sometimes.


Monitor server hung on ibmplinux redhat 5.1 platform.


RepAgent may send an incomplete multi-byte character in text data to Replication Server when the text data is longer than 4KB and starts with an XML declaration element and contains multi-byte characters.


When statement cache and literal autoparam are enabled, a batch that contains \r\n (CR NL) sequence in the middle of two statements, the statement that right after \r\n sequence may not get correctly parameterized, offset may be shifted 2 bytes on the left.


Fully qualified ASE table name in query causes exception in using DBISQL's Query Editor.


Under rare conditions a query on the monOpenObjectActivity MDA table may result in a timeslice error.


Under some circumstances, a signal 4 may be raised while calling ex_raise and ex_print.


"ct_fetch(): protocol specific layer: external error: There is a tds protocol error. An illegal token was received" may result when accessing data containing null bytes on an ASE server when character set conversion using Unilib is employed.


A stack trace in the function, setGlobalIdentity, may be generated when an INSERT query is run and this query inserts into a proxy table that is created on a remote view and the remote view is created on a table that contains an identity column and the datatype of the identity column is not NUMERIC (i.e. it could be integer or smallint) and the remote view has an instead-of trigger for insert and the instead-of trigger contains a query that selects the identity column from the inserted pseudo table.


If the interfaces file does not exist or contains no server entries, opening 'Job Scheduler Server' page of Server Properties results an NullPointerException.


AFter changing the name of the table with sp_rename triggers defined on the table may no longer working.


Allow UPDATE STATISTICS to be performed in a multi-statement transaction. Update statistics changes will become part of the transaction, and and all the work done by update statistics will be removed by any rollback. If a multi-statement transaction does not exist, then update statistics will continue to use internal transactions to commit multiple minimal atomic parts of the update statistics command which will remain even if the command is aborted. Trace flag 2720 can be used to continue with the pre-fix behaviour, in which case an attempt to run this command in a multi-statement transaction is disallowed with an error message.


Update ASE startup reporting to recognise Windows Vista and Server 2008


Logins folder's Full Name column was mistakenly removed.


Logging SQL when an instance is shut down gets a NullPointerException.


In rare circumstances, Job Scheduler might fail to run with the error "Incorrect syntax near '`'".


Truncate table is not consistent when switching tables under 'suspend audit when device full=0'


SELECT INTO using ISNULL builtin in the SELECT list could lead to target table column non-nullable while the early behavior of ASE would make the target table column nullable even when the ISNULL result can't be null for the query.


Update DBISQL from version 11.0.0 to 11.0.1.


Deleting a table with LOB columns (text, image, unitext) and non-datarows locking scheme under direct mode may hit SIGSEGV together with stack trace in the module of LeDeleteOp::_LeOpNext() if the query plan has merge joins.


Restore the old behavior in ASE125 to use parallel sort while creating index on more than one output devices.


Deferred compilation may cause unexpected parse errors when setting quoted_identifier on\off within a procedure defintion. (Error 102, 257 etc)


Sybmon planprint could cause stacktrace.


Stacktrace could happen during GroupInsert operator execution under compatibility mode for GroupBy query with a lot of aggregates.


Execution of a stored procedure which creates a table with non-materialized computed column may sometimes result in a message "current process infected with 11" and the stack trace reported in the errlrog file if the procedure performs SELECT query on this table. This is likely to happen if a procedure query tree is renormalized. Stack trace may reference modules pre__replace_cpc and s_getTreeOrPlan.


ASE 15.0.3, esd#1 HKGC, Error 12316 occurs repeatedly


The message "storage access violation" in various XML related modules together with a stack trace which includes XML related built-in modules may be reported in the error log after an error 712 raised from a previous XML query involving a large XML document.


On rare occasions a 605 error may be reported when BCP and UPDATE INDEX STATISTICS with sampling are concurrently executed on the same Data Only Locked table that has at least one non-clustered index present.


GUI: while selecting a license key file, the default directory is empty if user specify an installation destination that does not exist.


On HPPA64 and HPIA64 platforms, if Java in Database feature is enabled in High Availability system, during failback operation, "sp_companion resume" operation on the primary causes the secondary companion either to hang or die due to an internal error if PCI/JVM is active on the secondary companion. In the event of a hang, the system 'ps' command will show an extra server process running. That is, in a two engine system 'ps' would show three server processes rather than the expected two. If the error results in dead engine on the secondary companion, the error log will contain messages indicating the engine hosting the JVM has exited with a signal 11.


Create Table or Alter Table with Case statement that uses an IN list or NOT column NOT IN list or the equivalent of those expressions in a computed column will cause stacktrace.


SQL which concatenates at least two contiguous NULLs with strings may cause error 257. For example, select NULL + NULL + 'abc'.


The message "current process infected with 11" in the module 's_free' with a stack trace which includes the modules 'kill_proc', 'metrics_dump' and 's_recompile' may be reported in the error log after killing a session that was executing a stored procedure which had to be recompiled and it was hang because transaction log was almost full and the configuration option "enable metrics capture" was set to 1.


On linux platforms with jmp_buffer mangling, engine dies abruptly with the message "Engine exited with signal 11".


Executing a query with compute clause may hit SIGSEGV together with stack trace in the modules of subparserr() and parserr2().


Under some rare circumstance when ASE is unable to allocate memory for query execution the usual message for error 701 " There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache." is accompanied by the stack trace in the errorlog file. The stack trace will indicate modules LePlanRelease and LeParentOp::LeOpProcessIOStats. The issue will happen if options to display statistics were activated.


Request new Backup Server verbosity level to disable "Connection from Server" messages.


Drop in sp_addlogin and sp_role grant/revoke performance after an upgrade from ASE 12.5.3 to 15.0.3 ESD#1 on a ASE HA cluster.


When the Properties button on Threshold page of Segment Properties dialog is clicked, an internal error occurs.


Sp_addexternlogin does not work when the target server password has special characters e.g. "=". This can cause the sybmigrate process fail with an error like "Incorrect syntax near '


Compiler Optimizations that rearrange code blocks will lead to (-)ve Keep count in the Partition descriptor.


Run sybmon command "set" without arguments caused SIGSEGV.


Index counters may not be updated in monOpenObjectActivity for a table


On AIX when Sybase Central 6.0.0 encounters an internal error, an internal error message about missing libjysblib600_r.a is shown instead of the regular error dialog.


The message "current process infected with 11" in the module 'memcpy' together with a stack trace which includes the modules 'LeRun' and 'LeJoinContext::computeVirtualCols' may be reported in the error log if a SELECT UNION ALL query is executed involving an outer join, a TEXT column from the inner table is selected and some NULL values are returned.


WaitEventID(which is larger than 251) in monProcess is incorrect.


Deletes over CIS to IQ may fail with error 11298. The 'DELETE' command contains syntax that requires it to use a cursor but ASE has disabled the support of updateable cursors against IQ.


If the master database has a secondary truncation point set during an upgrade from 12.5.x to 15.0.x, then an error 950 (Database 'master' is currently offline. Please wait and try your command again later) may be raised. To avoid this issue, preupgrade or upgrade will report an error if there is a secondary truncation point set.


In rare circumstances, the message "Current process (...) infected with signal 11(SIGSEGV)" together with modules like (bool PopEmit < SerialCost,SerialProps > ::emitMatchProperties, PopBase*OptGlobal::_GblAddTopLevel maybe be encountered for queries involving statement cache, literal autoparameterization, compatibility mode and OR terms.


Permission denied error is being given on SET_APPCONTEXT when executing a proc.


Sometimes users will see error message "JZ0R1: Result set is IDLE as you are not currently accessing a row." when accessing a ASE 12.5.x database


Duplicate rows could be incorrectly returned when an EXISTS subquery is SELECTing from a DISTINCT view and not all of the view's SELECT columns are participating in the subquery's correlated equijoin predicates.


A query having concatenated columns in GROUP BY clause may return the incorrect result if all the set of GROUP BY columns are unique to the result set.


Procedural queries with optimizable LIKE clause may underperform executing more logical IOs than expected.


DDLGen doesn't hide password when a space is supplied before the password.


If there is a mismatch between the datatypes of the constants in the IN/OR list and the respective column, special OR strategy might not be used. ASE now provides a optcriteria 'use_mixed_dt_sarg_under_specialor' which when enabled, will allow special OR strategy to be considered in case of mixed datatype SARGs in the IN/OR list. Additionally, traceflag 434 has been provided to turn OFF this feature. The traceflag setting overrides the optcriteria setting.


An infected with 11 error is raised with function LeUpdateOp::_LeOpNext on the stack when the tsequal function is passed a datatype other than timestamp.


Wrong result may happen for a query if the SELECT list has an extended column which is not included in the GROUP BY clause and one of the group by columns has a constant sarg (col= < cnst > ) on it. Similar wrong result could also happen for an equijoin between a GROUP BY view/derived table and other table when there is a constant sarg in the view for the joining column.


ASE stacktraces with signal 11 when the number of columns returned from a remote procedure is less than expected from the select list to a proxy table mapped to this remote procedure.


Msg 7305: after execute select ... for update in a stored proc


ASE assumes DC supports BIGINT datatype and incorrectly sends signed/unsigned NULL integer parameters as BIGINT datatype.


Insert queries involving proxy tables which are either part of a trigger or will fire a remote trigger may crash at signal 11.


Server always selects Slow Bulk mode for bulk copying rows into table with non-clustered unique index.


The database option "no ckpt on recovery" is incorrectly turned on after load database command on master database successfully completes.


Connect Dialog would not allow modified server entry if it's previously connected to the server before modification.


There is possibility of segmentation fault during XPDL conversion of a page whose page header is incorrect with PG_DATA and PG_OFFSET bits set simultaneously.


If a parallel plan is chosen for an AMC repartition operation, sometimes the data could be inserted into the wrong partitions.


Database Wizard's (Add) Device Size Dialog does not sort device sizes correctly.


If error 249 occurs during and it does not appear to be due to constant in the query and the query has not started execution i.e. compilation is still proceeding, then this error may occur due to expression histogram processing. This can be verified by looking at the optdiag output for the columns in the query, and determining if there is a possible conversion error that could occur with one of the histogram step values. The change in behavior will be to suppress the error and use magic numbers for the selectivity of that column when used in expression histogramming.


Inserting a NULL value into a TEXT column of a proxy table with an INSTEAD OF TRIGGER may result in an assertion failure involving the module eval_locator_bi().


INSERT into a VIEW which triggers an INSERT into the proxy table may cause error 3651 when the remote table also triggers a change in one of the column values being inserted.


It's possible of deadlock on sysconfigures table if running two sp_configure at the same time.


On NT platform, Monitor server didn't shut itself down when ASE is down


When ddlgen is used to extract the DDL for an object, that contains a user defined datatype which has a default bound to the type, the DDL generated contains an extra sp_binddefault command that fails because the default already exists.


ins_syn_sql incorrectly calculates free space on the default disk


If two indexes on different tables have the same name and if output from DDLGen is generated just for indexes, then an attempt to run this generated output fails if the indexes have been deleted in the server after the DDlGen was first run for the indexes.


Unable to connect to ASE using the reserved administrative connection when network password encryption (-X) is enabled.


Sometimes, the message "current process infected with 11" in the module 's_handle' is reported in the error log along with errors 2601 and 546 while trying to insert into a table with foreign key constraints.


Some stored procedures using temporary tables and trace 299 (forced open by name resolution) may result in stack trace. This happens if a procedure is frequently renormalized. Stack trace shows module lastleft.


The message "current process infected with 11" may be reported in the error log together with a stack trace which includes the modules 'Optimize' and 's_compile' when executing an UPDATE statement involving a join between two or more tables and the table being updated has defined a functional index involving columns which are being updated with values from columns from the other table(s) participating in the join.


If forceplan is used to force the use of a vhash index to scan the table in a join, a SIGSEGV or incorrect result can occur.


when outer joins have inner tables which are derived tables with UNION operators then there is a possibility of a stack trace.


Under rare circumstances ASE fails to compile statements in the deferred compilation mode.


After ASE detects a 605 error on a DOL index, ASE does not report the 605 error again on the same wrong page until ASE restarts.


There is a possibility that during bcp operation, some rows get corrupted as received from the network. But they safely make it into the database and corrupt the data pages and eventually corrupt the database.


Segmentation violation occurs under stress conditions in artificial environment not seen with normal replication environment.


ASE Plug-in and DBISQL's Connect Dialog encounters a syntax error setting a new password when the old password contains special characters.


An error 209 with the message "Ambiguous column name" may appear if a stored procedure which performs the UPDATE or DELETE with the selfjoin is executed by the non owner of a procedure and the execution is performed using the deferred compilation mechanism.


Under some rare circumstance related to the runtime recompilation of the parallel queries using expression involving LIKE and variables or parameters ASE may fail to generate parallel plan and report stack traces in the errorlog file. A trace will show modules copy__eval and copy__eoptlike.


Query on monSysStatement table causes timeslice error with large statement pipe.


Full index scans may be selected over limiting index scans in scenarios where there is a single or no rows in the table and the costings are the same for both indices. An index scan is "limiting" when the key's major attribute has a sarg on it. The full-index scan may be selected if it has a minor optimizable attribute and it's ID is less than that of the limiting index. IDs increase in the order of index creation. Full-index scan strategies were never considerend in pre-15.0. Setting the configuration parameter "mnc_full_index_filter" to 3 or enabling the optcriteria full_index_filter will eliminate full-index-scan strategies.


sp_dbcc_configreport will report arithmetic overflow error for databases larger than 2.5TB.


Select data from monOpenObjectActivity could cause timeslice when heavy load.


XML- > sqlj functionality can regress if sequence of COTS JavaVM is out of order wrt conversion results.


Under very exceptional circumstances a timeslice followed by ungraceful shutdown of the server due to the LDAP_SPIN spinlock being held may be seen involving the housekeeper whilst checking ldap configuration.


Queries from complex views may return no results at all. Running with the diagserver executable shows an assertion failure in res_view.c: "unprocessed view found"


Histserver memory usage keeps growing.


Null clause is unnecessarily appended to the ALTER TABLE MODIFY command when it is not explicitly specified in the command statement, resulting in an Oracle ORA-01442 error. This issue is specific only for Oracle and a traceflag 11237 is used to enable this fix.


Recompilation of stored procedures reporting TABMISSING\TEMPMISSING may be seen on case-insensitive servers under traceflag 299 if column names are not consistently specified as upper or lower case in the temp table definition between executions and table re-creation.


During worktable creation, if we fail to access the tempdb, it may lead to sig-11


After a dumped ase1254 database was loaded into an ase1503 server, if the database includes tables with encrypted columns which reference keys in other databases, onlining the database will cause a stack trace. The data is brought online and can be used.


If literal autoparam is turn on, in some rare cases, isnull() builtin function could return different result comparing when literal autoparam is turned off if the parameters in the isnull() is either CHAR or VARCHAR datatype.


In some cases, dbcc checkstorage may incorrectly report the soft error "100041 (Log free space discrepancy error): Current syslogs free space does not match what dbcc counted.".


Reorg rebuild / create index on a table with a CI resets systabstats.datarowsize to initial default of average row length.


In some queries involving distinct and temp tables, if we have "capture missing statistics" config turned on we might get a stack trace with error "closetable: called with null SDES".


Selecting "Tools"- > "Adaptive Server Enterprise"- > "Preferences" results a NullPointerException when ASE Plug-in is running on a system with Spanish locale.


Timeslice and stack trace contaning LeOperator*CgpNlJoin::cgpCodeGenTryNaryNLJ amongst others may be seen under rare circumstances when executing a query involving group by and aggregation.


ASE errorlog contains "TPM FATAL 'unknown TPM error-level raised' for Task xxx in ThreadID yyy"


Create Proxy Table Wizard sometimes gets ArrayIndexOutOfBoundsException after clicking Finish.


If the either of the optcriterias mnc_full_index_filter or full_index_filter is enabled, then explicitly updateable cursors (declare statement contains and update-clause) and dirty reads on APL tables could lead to a 311 error: open mycursor Msg 311, Level 16, State 2: Line 2: The optimizer could not find a unique index which it could use to scan table 'mytab' for cursor 'mycursor'.


The dump command does not raise error message for "No space left on device" on Linux when the device is closed.


Simultaneous load operation with same archive device name fails with 'Device already in use' error.


Statements that use the application context builtins such as set_appcontext() while the statement cache is enabled may result in Error 4060.


sp_displayaudit with "login" option fails with 18004 error on 15.0.x


BY default, dbcc checkalloc( < dbname > ) turns on traceflag 3605 with SERVERWIDE scope. This can cause other processes in the ASE to unexpectedly write messages to the errorlog while the checkalloc is running.


ASE may crash with Signal 11 at CtlibRemoteCaps::generateConstant when it runs out of memory.


During execution, if "run script" options is selected for Fix Statistics or QPTune Wizard, a stack trace occurs preventing the execution to finish.


If an insert parameterized language request with certain Numeric values is sent to the dataserver and statement caching is enabled then a segv occurs. A regular statement is fine with the same values.


For srvbuild, the default available physical memory value of OOB task is shown as 80% of RAM even if this value is larger than the "max shared memory" set on the operating system.


If a query involves an extended column (a GROUP BY column which does not appear in the select list) and if the select list includes an encrypted column, the execution of the query will hit a stack trace reporting a null encryption key. An exemplary query is: table t2 (a2 int, b2 int encrypt with key1) select t2.* from t1, t2 where t1.a1 = t2.a2 group by t1.a1


When an instead-of trigger contains a query that accesses the inserted or deleted log tables and the schema counts of the view upon which the instead-of trigger is created and the log (syslogs) do not match, a 11060 error may be raised, resulting from too many (10) attempts to recompile the query plan without succeeding.


Performance issue might be hit for a query with up to 5 joining tables involving cartesian products and/or theta-only joins.


Unnecessary recompilations may happen if 'open by name' trace flag 299 is activated and a temporary table has at least one BIT column.


Despite traceflag 11906 being on, reorg rebuild messages are reported to the errorlog.


When a user with sa_role executes SETUSER to a non-sa_role user, creates a table and a procedure referring to that table, then execution of that procedure following a schema change such as dropping and recreating the table will result in an "object not found" error (Msg 208).


Feed back optimization opened exception code shortcomings under the PCI Bridge (COTS JavaVM Integration) under AMD64 platform architectures. These code shortcomings are very severe and easily lead towards memory corruption when JDBC or Java Stream operations are invoked from ASE Tasks.


Set switch command does not work with traceflag 7714 ad 7715.


Automatic workspace expansion in checkstorage does not expand the text workspace automatically even though the text workspace is smaller than the recommended size, which is 25% the size of the scan workspace.


The error msg 414 could be raised if the plan chose reformatting strategy and it has many join predicates.


For queries containing IN/OR list s.t. one or more elements in the IN/OR list is a function then unexpected results might be returned.


When running on a Unix system, BCP Wizard cannot BCP in/out multiple tables.


Dump / Load operation failing to open the device may not report the Operating System error.


The dump command may not raise an error message reporting "No space left on device" on Linux when the device is closed using Backup API compress.


When using parallel sort on worktable, several issues were encountered while executing sort operator.


Sometimes, database upgrade fails with error 1204, "out of lock error" while upgrading a system table with huge number of rows.


When the optimizer chooses a query plan that includes and Nary-Nested-Loop Join Operator (as seen in showplan output) and at least one of the Scan Operators under the Join is doing dynamic partition elimination (also shown in showplan), the query may return too few rows. This problem ocurrs in queries with at least three tables and which contain join predicates involving columns of the partitioned table that are not part of the partition condition of that table.


Some of the qualifying rows could be missed by an UPDATE statement using at least 2 tables other than the updated table (either directly in the UPDATE statement's FROM clause or within EXISTS/IN subqueries) and the join of these 2 tables involves an expression which contains one of these tables' columns which is also in the UPDATE's SET clause to compute the new values.


TEXTPTR() builtin function may sometimes return truncated result. Pending zeros are removed.


When parallelism is involved, some queries having more than 6 tables may timeout earlier during plan enumeration resulting in merge joins plan that uses excessive tempdb space.


With SQL Replication enabled queries with CASE constant expression that is expression which is not referencing table columns may fail with error 401 "Invalid operator for datatype op: = type: MAINTENANCE TOKEN" or error 551 "An unknown EVAL was sent to the execution module."


Sending a Java object using Java/JDBC on the client-side can result in a corrupted object stream being stored in a database table.


The JVM dies with error 143 when the user logs off from Windows OS running ASE.


When the view is redefined during the deferred compilation the ASE may fail during the redefinition process. Stack trace will be logged in the errorlog referencing modules like vu_redefine, col_open_range.


A transaction dump that has a DROP and CREATE index commands logged for a clustered index with sorted_data, max_rows_per_page and fillfactor options used, may result after load in a corrupted table where errors 692, 605, 2509, and 2525 could be reported.


The ASE server could potentially dump core in final stages of a server shutdown under the condition of stale PCI Bridge arranged JavaVM activities. This error is not a dangerous or worrisome event but the core files as left are ugly and consume lots of file system space.


The message "timeslice - < number > , current process infected" together with a stack trace which includes the modules "dbts_insert", 'dbts_commits_addxdes', 'xls_test_set_lrdata' and 'ha_session_dealloc' may be reported in the error log when CHAINED transactions are used in and HA environment.


Introduce configurable control for allowing or disallowing loading native libraries from within the PCA/JVM using the load and loadLibrary methods in the java.lang.System and java.lang.Runtime classes.


When compatibility mode is enabled and a stored procedure is executed, ASE may stacktrace in the function ind__itagsetup(). This happens if a query in a stored procedure refers to a table that is created and dropped inside the stored procedure and that stored procedure happens to recompile after the table has been dropped.


ASE may report 3474 and 3478 fatal errors if bulk-insert ctlib application making use of multi databases transaction needs to rollback.


After CR 531964 changes, sysprocesses.physical_io maps to piotot which is only incremented at the end of each statement because of which monProcessActivity had to be used for tracking i/o activity for running query. The physical_io should report pbufread\pbufwrite which are incremented as each i/o completes.


Unexpected errors may happen as a side effect of the compilation of SELECT INTO #TABLE statament. Errorlog will report module s_normalize. Also under some very rare circumstances on a heavy load systems a risk of random memory corruptions exists.


In rare circumstances when using 'SET ROWCOUNT' option or 'TOP' directive with 'SELECT INTO' executed in the parallel mode the rows may fail to be inserted.


When dboption "dbo use only" is set, the database owner executing sp_adduser may result in an access error (Msg 923).


Duplicate rows may be inserted into a table that has a non-unique clustered index and that has one or more BIT columns even though the option, allow_dup_row is not set. For duplicate rows to be inserted, the total number of BIT columns in a row must not be an exact multiple of the number of BITs that can be stored in a BYTE (8) - this is a necesary, but not sufficient condition.


If $SYBASE starts with /net, srvbuild[res], sqlloc[res], and sqlupgrade[res] report error: unable to load localization file < path > .


After the command 'set proxy' is executed, RepAgent still sends the original login for replicated transactions instead of the new impersonated login. As a consequence, when replicating DDL commands, objects might be created with a different owner at the replicate site.


In some rare situation, if a plan has groupinsert operator, it could raise 613 error.


Like pattern matching may return fewer rows when the following conditions are met: 1. server's default sortorder is non-binary single-byte sortorder 2. like pattern is a constant literal 3. like pattern string length is the same as column data length 4. column is either varchar or char



  • SAP Adaptive Server Enterprise (ASE) 15.0.3 ESD #3
  • 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


Sybase Adaptive Server Enterprise 15.0 ; Sybase Adaptive Server Enterprise Cluster Edition 15.0


CR, ASE 15.0.3 ESD#3, ASE 15.0.3, ESD#3, ESD 3, 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 , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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.