SAP Knowledge Base Article - Preview

2084259 - Targeted CR List for ASE 15.5 ESD#1 - SAP ASE


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



DBISQL connects to wrong host in interfaces file when using standby addressing


Improve the clarity of the description for the IndexID column in monCachedObjects table.


In rare circumstance, ASE might report invalid StartTime, EndTime and CpuTime in monSysStatement.


Do not incorrectly report the message that 'per object statistics active' configuration parameter is required for the monProcessActivity table.


Use Trace Flag 2792 for allowing concurrent access to the table while doing a Reorg Rebuild.


logon audit success/failure config option prints the connectivity version along with other useful information about a login connection.


ASE running on windows reports blocks four "Cannot get value ..." [from registry] error messages every time it starts


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.


Add an option to remove the server entry after disconnecting from ASE.


The error 3935, "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context. The transaction is currently in 'Abort tran-attached' state." will be raised if the command DROP DATABASE fails while trying to release the internally created devices of an archive database.


Backup Server does not use directio or dsync i/o as configured for database devices.


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.


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


When you set tracefile and then try to write a query plan into the trace file, Application Tracing doesn't write a carriage return ("\n") with japanese messages. That's hard to read the query plan in the trace file.


If the ASE PCI subsystem fails to start up then stack traces may be seen in the ASE errorlog and ASE may not boot.


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".


The Historical Server Monitor 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.


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.


dump database with EMC Networker failed with Archive API error indicating failure in loading the API library on HP-UX platform.


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.


When executing a query involving views and coalesce(), an error 4409 may be reported 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 shows an error message like "Setup.product.install, com.sybase.ismp.ase.wizardbean.SetupLogWizardAction, sis, ERROR: product bean suite does not exist"


Add a dbcc command to enable fixing 100004 checkstorage faults (timestamp value in page header larger than database timestamp).


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 built-in function VALID_NAME() could cause a SIGSEGV (infected with 11) 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 in 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 an incorrect "go" between the two ENDs for dropping the primary key and the foreign key.


When statement cache is turned on, if an exception occurs while compiling a statement which has temporary tables in it, an error msg 8203 could be raised.


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 names in a query cause an exception when using DBISQL's Query Editor.


Feature request to support using sybmigrate from ASE 12.5.x using non-utf8 charset to ASE using utf8 charset.


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


"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 a table with sp_rename, triggers defined on the table may no longer work.


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 changed to recognise Windows Vista and Windows Server 2008, avoiding the message "ASE booted on unrecognised or unsupported operating system".


Logins folder's Full Name column was mistakenly removed.


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.


CREATE DATABASE command should print a warning message to the user if the number of databases on the server exceeds the value of the 'number of open databases' configuration parameter.


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.


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.


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


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.


Executing a query with a compute clause may hit a SIGSEGV (infected with 11) together with stack trace referring to the modules 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 a 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.


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.


Run sybmon command "set" without arguments caused SIGSEGV.


Index counters may not be updated in monOpenObjectActivity for a table


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.


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.


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 a GROUP BY clause may return an 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.


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.


A SIGSEGV (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.


During modifcation of a default value on a column using Sybase Central 6.0 the 'select into/bulkcopy' option for the database is unnecessarily changed.


ASE stacktraces with SIGSEGV (infected with 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.


Procedural statement with FOR UPDATE clause may incorrectly raise error Msg 7305, Level 15, State 1: FOR UPDATE can not be used in a SELECT which is not part of the declaration of a cursor or which is not inside a stored procedure.


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 encounter a SIGSEGV (infected with 11). "xact_sync_trigger" will usually be referenced in the stacktrace.


The performance of concurrent DMLs in a low durability database has been slightly improved through an optimization to post-commit processing of deallocated pages.


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


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.


datachange() function always returns 0 if the table has no indexes and we do update statistics on table only


ins_syn_sql incorrectly calculates free space on the default disk


Sometimes, the message "current process infected with 11" in the module 's_handle' is reported in the errorlog along with errors 2601 and 546, while trying to insert into a table that has 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. The stack trace shows the 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.


ASE Rep Agent support for the database re-synchronization feature from Replication Server 15.5.


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.


A SIGSEGV (infected with 11) referencing "lt_notify_flush" can occur under a high stress scenerio in a replication environment.


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.


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.


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"


A 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 and 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.


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 the "capture missing statistics" configuration option is turned on, a stack trace with error "closetable: called with null SDES" can be reported in the errorlog.


If a store procedure use an unpartitioned table and the compatibility mode is turned on, it could return wrong result if later this table is changed to a partitioned table when executing this procedure.


A timeslice and stack trace usually containing LeOperator*CgpNlJoin::cgpCodeGenTryNaryNLJ 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"


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'.


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


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


If an insert parameterized language request with certain Numeric values is sent to the dataserver and statement caching is enabled, then a SIGSEGV (infected with 11) 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.


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.


A 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.


The SET SWITCH command does not work with traceflags 7714 and 7715.


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 where one or more elements in the IN/OR list is a built-in function, unexpected results might be returned.


DBISQL does not support password encryption directly.


When using parallel sort on worktable, errors and/or stack traces can be encountered while executing the sort operator.


When the ASE Replication Agent connects to the Replication Server version 15.5 or above, it will issue the Replication Command Language command 'resetqueue' by default when starting up against a database with a durability value of 'no_recovery', instead of incrementing the primary database generation ID, so to prevent the likelihood of hitting a limit while updating the generation ID value. The current ASE fix will be effective when the Replication Server CR 615322 is also released in some later Replication Server 15.5 ESD version.


Executing installhasvss script raises a 2615 error.


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


When the optimizer chooses a query plan that includes a 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.


The user_name() function incorrectly returns NULL for negative user ids starting in 15.0 GA.


TEXTPTR() builtin function may sometimes return truncated results with trailing zeros removed. This occurs when a "hash distinct" operator is involved.


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


The authentication mechanism is not displayed in the audit record when doing dbcc table_xfer_check.


With SQL Replication enabled, queries using "CASE constant expression" (i.e. an 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."


Error 6901 is always reported as occurring in dbid 0 rather than the actual database containing the high timestamp value. Check @@dbts in each database to find the database(s) that actually contain high timestamp values.


If there are tables with names wider than 30 characters and SET STRING_RTRUNCATION is set ON, sp_fkeys fails with errors 9502 and 17461


When a view is redefined during deferred compilation an error can be reported along with a stack trace in the errorlog referencing modules like "vu_redefine", "col_open_range".


The result of derived_stat builtin is incorrect when the partitionid parameter is not supplied.


Executing a query involving encrypted column may hit a stack trace, if the encrypted column has decrypt_default and column statistics.


Implement CIS support for new datatypes, bigdatetime and bigtime.


On Windows systems when Adaptive Server is running with configuration option "enable literal autoparam" active in some circumstances the execution of a query containing a big literal binary value may be aborted and the message "SQL Server system exception (0xc0000005) generated by a storage access violation" together with a stack trace which includes the modules 'memcpy' and 'mkconst_desc' may be reported in the error log.


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.


Unexpected errors may happen as a side effect of the compilation of a SELECT INTO #TABLE statement. The ASE errorlog will report a stacktrace involving module s_normalize. Also under some very rare circumstances on a heavily loaded system, there a risk of random memory corruptions.


In rare circumstances error 941 "Illegal database context operation" may be reported into the errorlog while terminating ASE process.


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


The quantity of licenses required for the DH license type should match the number of processor chips. Currently it is being treated as a Server license type and only 1 license is checked out.


Need DDLGen support password encryption


The durability of a database after MOUNT DATABASE is set to UNDEFINED instead of FULL.


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.


A 3151 error, "Adaptive Server cannot load this database because the database that was dumped was not quiescent when the dump was performed ..." is reported when loading the dump of a database that has a durability of either NO_RECOVERY or AT_SHUTDOWN on a platform that has a different byte order to the platform on which the dump was taken. This is despite there being no activity in the database at the time the database dump was taken.


ASE Cluster Edition may rarely hang during failover recovery.


Job Scheduler in ASE is not able to run more than 4 jobs simultaneously.


ASE may hit 692 error during 'disk resize' of filesystem devices when server is using sync IO('allow sql server async i/o' set to 0).


Job Scheduler (jsagent) heap memory usage grows after job runs resulting in memory leaks.


Under some circumstances when a parameterized statement is being compiled and Adaptive Server is running out of memory for procedure cache the message "Stack overflow detected" may be reported in the error log together with a stack trace which includes the modules 'pars_release_resources' and 'recvhost' and may result in Adaptive Server being shutdown automatically.


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.


MonCIPCLinks table not showing the details of all the configured links


In rare circumstances, message "current process infected with 11" in the module 'des_wkinstall' may be reported in the error log while executing a query that needs to use worktables.


When ASE is booted with Java enabled and running under a multi-engine environment the module responsible for physical I/O protection may not be correctly installed.


Sybase Central BCP in "specify field terminator" requires a "\t" for tab delimited files, while command line -c needs no -t \t arg.


New traceflag to control the synchronization of file/device between writers.


In some cases, DBCC CHECKALLOC may report error 12909, "Table with object id= < id > (name = < name > ) inconsistent after Large Scale Allocation. < no > pages in extent < extid > were found reserved.", some time after either LOAD DATABASE or boottime recovery had processed log records relating to large scale allocation.


A user is not allowed to execute a procedure which makes a cross-database access based on a chain of ownership after the owner's alias is removed from both databases and his login dropped.


If a database which is template database for an IMDB is renamed using sp_renamedb, the Imdb will not be accessible on subsequent restart.


In some cases, when a database that is used as a template for creating a database with a durability of NO_RECOVERY is being recovered, a 973 error "The database ' < template_dbname > ' is currently unavailable. It is being used to create a new database." may be reported in the error log.


In some rare situations, if a plan has a "group insert" operator, it could encounter a 613 error.


Sometimes, during recovery redo pass, error 3474 may be seen indicating that a page being recovered has a timestamp older than what we expect at that point.


Querying or Accessing monTableTransfer when tables with "transfer table set on" are present would cause 14120 errors or timeslice in the server.


Some databases, e.g, sybpcidb, do not show up in ASEPlugin's database list.


ASE server on 64 bit platforms fails to start the Job Scheduler when LDAP Directory services is enabled.


The replication status 'never' set on a table may be ignored mistakenly on ASE CE by nodes other than the node where the status was originally set. Alternatively on ASE SMP, this status may be ignored mistakenly after an ASE restart.


The error 3906, "Attempt to BEGIN TRANSACTION in database 'archivedb' failed because database is READ ONLY. " may be raised when trying to access a partitioned table in an archive database.


During shutdown, if the transfer table command tries to create a transaction or insert data into the spt_TableTransfer history table and it might dump stacktrace with itl_record_transfer function in the callstack along with the 16024 error.


When a user with sso_role loads a 15.0.2 database into a 15.0.3 server with esd version #2 or lower, error 2736 occurs if the user is not a named user in the loaded database and the database has a guest account.


sqlupgraderes can not do upgrade because it can not set $OLDSYBASE.


Enhance ASE WebService to embed Jetty6 and fix SSL MITM vulnerability: CVE-2009-3555.


In some cases, the error 15717, "The archive database ' < dbname > ' is already being updated by the process with spid ' < spid > '", might be raised when trying to access an archive database that has been recovered by ASE using parallel recovery.


xp_cmdshell creates defunct processes when using "no_wait".


ASE may disable the LDAP URL for a locked or disabled login, if the LDAP server returns error code 53-'Server is unwilling to perform'. ASE treats error code 53 as fatal error and the URL is marked as FAILED. ASE should handle error code 53 without disabling the LDAP URL.


In ASE SDC, the message "current process infected with 11" in the module may be displayed in the 'cm_check_if_noobject_bound_cache' cache deletion module. This may happen when the cache creation succeeds in one of the nodes and fails in others.


The error 822, "Could not start I/O for request" could be sporadically be raised when ASE incorrectly tries to flush index pages to disk in an archive database, without having remapped them to the modified pages section.


Adaptive Server Enterprise PLugin for Sybase Central fails to correctly display that a logins password has expired.


Performance for Batch insert is slow for SDC when using large pools for logs.


Stacktrace with the invalid Column length msg when store_index is used in AP


In some special case of scanning a dol table, the interested page/buffer brought into another cache could cause 871 error.


ONLINE DATABASE command and Faiover Recovery are not synchronized in some cases. They may progress in parallel on a database; may result in corruption.


Config value like 'SQL batch capture' which is set in config file might be reset to 'DEFAULT' after reboot.


When references are left in sysattributes for a login and replication attempts to add the same login and suid again, the attempt fails with error: "Fatal protocol error. xact_beginupdate() API was invoked in the wrong context..."


Sybase Central prior to version does not support Windows 7.


Integrated login mixed mode fails for local system account even if valid username/password is specified.


Sometimes a task that hits error 892 can go into a loop, continuously raising the same error. This can result in server shutting down.


The sybcluster do not check the instance names entered by the user and verify that they are valid values.


The sybcluster utility does not check the traceflag value entered by the user and verify that they are valid values.


Currently, using a pre-15.5 client to call current_bigdatetime() directly results in errors 247\3606:- Arithmetic overflow during implicit conversion of BIGDATETIME value ' Invalid pointer param number 3, pointer value 0x9cf500d408f1 This CR is to change the return value to be either current_date() or raise an error stating 'not supported' when a pre-15.5 client is detected.


The first time syconfig is used to create an ASE, the specification for tempdb size and device is ignored and tempdb is created only on the master device with the minimum size.


When 'disk init' is executed simultaneously from multiple connection may lead to creation of devices with same vdev number.


If the size of an in-memory device is not an integer multiple of the size of an allocation unit, creation of in-memory database on such a device may hang.


system procedure 'sp_volchanged' failing, if dump operation happens to be on remote backup server.


When runing PCClient autorun.exe on FDCC Vista and select "Install PC Client Components", the installer can not be started and show error "Windows error 216 occured while load JVM".


optdiag simulate is broken in 15.5 GA releaase for SMP installations. The following error is generated: optdiag simulate statistics qts_db -Usa -P -T1 OptDiag/15.5/EBF XXXXX SMP/B/x86_64/Enterprise Linux/asearies/2431/64-bit/OPT/Mon Jan 11 00:38:22 2010 ... Server Message: - Msg 207, Level 16, State 4: Invalid column name 'instanceid'. Internal error: ct_results() returned result type CS_CMD_FAIL. Optdiag failed. Check for error messages above.


Duplicate key values could be generated for identity column during checkpoint or a node shutdown and rejoining the cluster. For tables with unique indexes on identity column, it would give error 2601 'Attempt to insert duplicate key row in object < obj_name > with unique index < index_name > '


Executing of sp_encryption to add a system encryption password or using the built-in password_random will cause a SIGSEGV resulting in a stack trace in ASE 15.5 if the /dev/random, /dev/urandom, and /dev/srandom do not exist.


Sybase CE in VCS-mode fail to change sortorder.


During bootup or when using sp_configure, ASE may indicate that verification of a configuration failed because The sum, (number of user connections) + (number of devices * max online engines) + (number of remote sites) + (max number network listeners) + (max cis remote connections) + (number of java sockets), must be no greater than... giving an very large number. The correct value is the lower 32 bits of the value.


ddlgen generate syntax error on create table command.


When changing the default character set id or changing the default sortorder id, after doing sort order chnages when restart the server, it may hit SIGSEGV.


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


Various issues might show up during cache/pool configuration.


DUMP WITH COMPRESSION = 101 may fail with messages Pipe I/O returned 0 bytes followed by Multibuffering subprocesses died


xp_echo.mak make file is incorrectly pointing to libsrv.lib instead of libsybsrv.lib


Sybase Central is unable to recognize and use the OCS interfaces file syntax for commonName handling for SSL of the form: query tcp < host > < port > ssl="CN= < commonName > ".


Error 8203 may be wrongly raised when doing select into or alter table. The message seen is as follows: Expected to find the descriptor for object %d in database %d in CLONED state.


When user make use of srvbuild to create monitor server and input invalid value which exceeds the allowed maximum number 20, there is no warning message but task will fail due to can't boot server in the end.


Password should be quoted if it has special characters.


The store procedure sp_shmdumpconfig might report incorrect values for estimated dump file size for ASE Cluster Edition.


DiagQ enhancements under TF 15578. Also, fixes a problem inside OCM where A task is sleeping inside ocm_lock waiting for lock-downgrade(BAST) request to be serviced but BAST is not serviced even though no task is holding ocm_lock;this makes other tasks to block/sleep which in turn cause system hang.


With the configuration option 'net password encryption reqd' set to 1 or 2, the JSagent fails with "ct_connect() failed", "jsd_MakeConnection() failed", "jsj_AddConxs() failed", "jsj_AddConxs() failed" and "Initialization failed initializing connection pool" messages in jsagent log file.


BCP IN will fail with error 2624 when the target table has one or more encrypted columns and all variable length data in a row is NULL.


The message "current process infected with 11" in the module 's_free' together with a stack trace which includes the modules 'clean_process' and 'kill_proc' may be reported in the error log when a session executing a query involving session temporary tables was killed by another session and statement cache is enabled in Adaptive Server. Under some circumstamces a 6103 error, "Unable to do cleanup for the killed process; ..." may also be reported after that.


The diagnostic information that is reported for the 707 error has been enhanced. Following a 707 error, a message of the form: ( < module name > ) Diagnostics for error 707 state 10: < diagnostic info > is reported in the error log together with a stack trace. An additional single line of diagnostics is reported prior to the message and stack trace above, when the 723 trace flag is turned on.


A connection/isql session may get terminated printing out a stacktrace involving the functions :s_compile(), s_compile_stmt(), PssInit(), getdbsize_in_mb() in that order when the task receives attention when waiting/sleeping after a lock request.


ddlgen 155 fail with source ASE 12.5.x.


On a multi-engine server, the number of Ct-lib connections per engine may not be evenly distributed among all the engines. The load imbalance is observed using the sybmon command 'engines -1 ectcount'.


The message "Starting diagnostics for read failure" together with a stack trace which includes the modules 'db_diskremap', 'db__diskremap_sysusages' and 'pg_fill_supergam' may be reported in the error log when a database dump from a different platform and with a different diskmap is loaded in a ASE cluster server.


The automatic start of Backup Server results in defunct sybmultbuf process after the backup is complete.


When an instance is initializing shared memory which could take a very long time, it is not sending cluster heartbeats to the other cluster members.


DDLGen for a table does not generate ddl for indexes which have been created with sorted_data option


In rare circumstances error 834 (Illegal attempt to clean buffer) may be reported in the errorlog while starting alter table utility on multinode cluster.


shortcut keys for tempdb and pci attributes are missed in srvbuild screens


Under certain circumstance, an error 632 may happen to an instance of a multiple instance cluster, it may lead to subsequent error 1601 and error 8601on the same instance, and bunch of user tasks can't proceed on one or multiple instances of the cluster when the situation occurs.


Transfer table import command in hppa platform would throw sig11 if the file provided to the command is corrupt or empty.


sqlupgrade help button on the upgrade status screen fails to show the message.


In a Multi-Node cluster, a node crash and re-join could end up generating duplicate identity values for objects with identity column.


DB2 DATE and TIME datatype cannot be mapped to an ASE DATE and TIME datatype against MFC 15. They are mapped to ASE DATETIME datatype instead. A workaround fix is provided to enable the mapping and traceflag 11238 is used to turn on the fix.


In rare circumnstances, database processes are waiting for a semaphore from the kernel memory pool and can not be killed.


Fix the error 871/20/2 when running reorg compact in ASE 15.5


1) LAST CHANCE EXCEPTION HANDLER on OS thread id caused by attempted read from invalid memory address during LDAP user authentication on Windows 64bit Adaptive Server. 2) LAST CHANCE EXCEPTION HANDLER on OS thread id caused by attempted read from invalid memory address when setting URLs on Windows 64bit Adaptive Server with switch 3635 turned on.


Under certain circumstances, a stored procedure that references a view can raise error 11060 if the objects are created on a 15.0.3 ESD#2 server and that server is subsequently upgraded to 15.0.3 ESD #3


Some messages in dataserver logs related to failover need clarification or changes to make the actions of the server clearer.


INSERT, DELETE or UPDATE commands executed with minimal logging together with the chained transaction mode may fail with a timeslice error being reported in the errorlog showing the module xls_test_set_lrdata and dbts_commits_addxdes.


In rare circumstances, a 707 error with state 10 "System error detected during attempt to free memory at address 0x < address > . Please consult the ASE error log for more details." may be reported for an ASE that uses a procedure cache whose size combined with the size of the statement cache exceed the value of 4G-bytes.


ASEPlugin attempts to access local tempdb for another node than the one the user logs into.


In rare cases, the recovery of a prepared multi-database transaction that started in the master database and that had a transaction branch on a remote Adaptive Server, might result in an inconsistent completion state between the branches of the transaction.


The execution of a stored procedure that in turn calls a cross database udf may result in permission error 10351 if the caller of the stored procedure is not the owner of the udf.


Wrong outerjoin result may happen for a query with an outerjoin between a GROUP BY view/derived table and other table when there is a constant sarg in the view for the equality joining column. Null-supplied rows from the outerjoin may be incorrectly eliminated.


In rare situation, "dbcc lockgc" might run into errors related to spinlock


Under certain circumstance, long lock hash chain(s) might contribute to 100% CPU or performance slowdown


Integrates with new Certicom and OpenSSL security libraries that tackle SSL renegotiation vulnerability described in RFC5746.


In rare circumstances, a 692 error "Uninitialized logical page ' < value > ' was read while accessing ... object 'syslogs' (8) ..." together with a stack trace which includes the modules 'rep_agent_thread' and 'xsc__syslogs_getnext' and 'wrongpage' may be reported in the error log by the Adaptive Server Replication Agent task.


Comparing bigdatetime values under a parallel plan may cause error 9566, "worker process plan copy error" to be raised.


Concurrent DML for APL table on different node may cause server hang. ASE may absort the suspect transaction.


ASE doesn't passes directio or dsync i/o as configured for database devices on HP platform


Do not acquire cluster-wide distributed locks for objects which belong to node-specific databases like local user tempdbs.


A 6909 error, "The timestamp ( < timestamp > ) of the transaction that started at date ( < date > ) in database ' < dbname > ' (database id ' < dbid > ') is earlier than the timestamp ( < timestamp > ) of the most recently started transaction." may sometimes be reported when a chained_mode transaction's pss is flushed by another task.


Under very rare circumstances, for caches using the clock replacement policy, the instance level physical lock on a page may be released without ensuring all local users of the page have finished working on it. Subsequently, the Adaptive Server Cluster Edition will report the following 892 error: "Process < spid > is holding a latch on buffer < buffer-address > (dbid: < dbid > , pageno: < pageno > ) without holding a physical lock on the buffer".


The dump and load operation initiated by specific ASE version and involving database devices with directio or dsync property may fail with error "Option 'iomode' is not valid" when Backup Server does not support 'iomode' option.


run srvbuildres with resource file that contains "sqlsrv.avail_cpu_num: PUT_THE_AVAILABLE_NUMBER_CPU_FOR_ASE_IN_OPTIMIZATION" causes srvbuildres crash.


When a 32-bit release is installed on a 64-bit Unix system, Sybase Central launch script doesn't launch Sybase Central. The workaround is to re-define SYBASE_JRE6 to point to SYBASE_JRE6_32.


ASE 15.5 Cluster Edition may raise error 820 in rare conditions, when multiple tasks are actively inserting and modifying data.


When sybase NULL semantics are enabled i.e. set ansinull off (which is the default) then there is a possibility of a wrong answer when a DISTINCT, ORDER BY, or GROUP BY is used in the query with = NULL .... or an equi-sarg like = @v1. The behavior is as if ansinull is on, which would eliminate NULLs.


Bigdatetime/Bigtime types are not disabled under compatibility mode under some circumstances.


ASE on hppa64 platform can hit SIGBUS in poll_using_memory function when we do disk init on raw devices.


In SDC, server may hang after seeing error 8243 when doing "table table unpartition" on table created for load.


Change the default value of the configuration parameter 'job scheduler tasks' to 4.


The WITH DBID = < N > option to the CREATE DATABASE command does not work in ASE 15.5.


Job Scheduler may be aborted after getting spurious state from the JS Agent when number of jobs running simultaneously is equal to value of 'job scheduler tasks'.


update statistics on partitioned tables may be slower in 15.0.3 ESD #3 than previous ESDs.


ASE running on windows may fail to start if Performance registry subkey is not present



  • 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


SAP Adaptive Server Enterprise 15.7 ; Sybase Adaptive Server Enterprise 15.5


CR, ASE 15.5 ESD#1, ASE 15.5, ESD#1, ESD 1, 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.