SAP Knowledge Base Article - Preview

2087945 - Targeted CR List for ASE 15.0.1 IR


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



In the output of SP_CONFIGURE command, even if the new and old values of a configuration parameter are same then it will change the value of configuration parameter and will write a new config file.


Incorrect usage of Disk Mirror command throws Error 5101 with obsolete optional parameters. The syntax displayed is DISK MIRROR NAME=" < name > ", MIRROR=" < device > " [,WRITES={noserial | serial}] [,READS={mirrored | nomirrored}], [,CONTIGUOUS]. Here, parameter < [,READS={mirrored| nomirrored}] > is obsolete.


Improve the performance of sp_setreptable when the table has text or image columns.


C++ ASE Plug-in is no longer supported.


Improvement to Historical Server command line processing.


Added two new builtins. isdatetime() determines whether an input expression is a valid datetime value. isnumeric() determines whether an expression is a valid numeric type.


New configuration property 'cis idle connection timeout' has been implemented. The value of this property represents seconds. However, the granularity of the timeout is determined by the housekeeper, which wakes up roughly every minute to perform its housekeeping chores. One of the new chores is to check for CIS connections that have been idle for a time equal to or greater than the configured timeout value. If that is the case, these connections are dropped, if no transaction is pending for the thread that owns the connection.


Under certain unusual load conditions, it is possible for 2 or more CPU bound tasks to block other tasks at the same priority for an unacceptably long time


Referential integrity may not be enforced for UPDATE or INSERT query if the query is executed with the option SET ROWCOUNT.


SQL text capture may be turned off in the ASE when the Monitor Server terminates. This will cause collection of data for the monProcessSQLText and monSysSQLText MDA tables to stop.


In "Disk I/O Management" section of sp_sysmon output, we may find wrong values on Device Semaphore Granted/Waited fields if there is a skipped vdevno and async disk I/Os are delayed.


A filelist has been added to the image at $IMAGE_ROOT/manifest.txt listing all the files that will be installed by this EBF.


After upgrade, table level statistics on system tables are wrong.


Once a database has been almost fully filled up using the BCP or the SELECT INTO command, some premature out of data space conditions may be hit by commands like INSERT, CREATE TABLE, SELECT INTO, BCP, ... whereas 'sp_helpdb' shows that free data space is available. Alternatively, for mixed log and data databases, 3475 errors may be raised under the same space usage conditions.


The alter table command silently fails when referential integrity constraint has a non-existent database name.


Enhance DBCC CHECKTABLE for empty ALLPAGES LOCKED, SLICED tables to report error if the root page of the index has extraneous entries pointing to deallocated pages even though the table is empty.


In rare circumstances, 3223 and 3208 error is returned when ASE reads the dump header for cross-platform database load, if the database has many disk fragments in Sysusages. The message "current process infected with 11" in the module 'lddb__stat_translate' together with a stack trace which includes the modules 'lddb__unscr_stat_page' may be reported in the error log, when loading a database across platform, if the database has an orphan row in Sysstatistics.


Make SQLDBGR to be JDBC3.0 compliant.


The message "current process infected with 11" in the module 'kbfalloc' may be reported in the error log when using network packet size greater than the configured value of "default network packet size".


In multi engine environment, if the engine which is running the "disk mirror" is not able to access the primary device, mirroring succeeds but later ASE fails during the subsequent operations with the errors such as : - Error 692: "Uninitialized logical page < page id > was read while accessing object < object id > in database < database id > or - Error 822: Could not start I/O for request BLKIO < ...buffer details >


sybsystemdb transaction log may fill when selecting data from the MDA tables into a permanent table if "enable xact coordination" is set to 1 or "trunc log on chkpt" is not turned on for sybsystemdb.


On MacOS X, if JAVA_HOME environment is not set, sqldbgr reports "Unknown platform!" error.


Previously when user opened Data panel for a table or view and sort the data, columns with duplicate values would not sort correctly, with Nulls replacing the duplicate values. This has been corrected.


BCP IN operation may report 2404 error when unilib conversion is enabled.


CIS: When a setuser command has been issued on the session, create proxy_table command will fail with Msg 911 and 11206.


System stored procedure sp_who may incorrectly report login name for a session executing stored procedure if the stored procedure is being recompiled and the procedure executor does not own the procedure being executed.


On Mac OS X platform, error, "Volume validation error: illegal volume change, device < device name > : volume mounted out of order, expected volume 0001, got volume 16777216.", is reported by Backup Server when running load database with a dump file that was generated on little-endian platform.


sp_estspace output is incorrect for APL tables with short rows on wide page size. There is a limit of 256 rows per page that the code does not account for.


Added new T-SQL builtin, PARTITION_OBJECT_ID() that displays the object ID given a partition ID and an optional database ID. Interface is PARTITION_OBJECT_ID( < partition ID > [, < database ID > ]). Returns NULL for non-existent or invalid input arguments.


select into encrypt is NOT failing with error 11776 when identity columns are encrypted.


A process may deadlocked with itself on an allocation page latch following a log full condition (1105 error). This connection may then block other connections needing the same latch or other locks this session holds.


Monitor Server in an SSL configuration may crash after several hours of running.


An application error in transaction nesting leads to a segmentation fault with message 3934 "Transaction manager has detected a nesting failure. Number of BEGIN TRAN commands (issued after an attach operation) do not match the number of COMMIT TRAN commands (issued before a detach operation)". A stack trace with module finish_xact() will be found in the errorlog.


The message "current process infected with 11" in the module 'lddb__stat_translate' together with a stack trace which includes the modules 'lddb__unscr_stat_page' may be reported in the error log, when loading a database across platform, if the database has an orphan row in syssatistics.


A login attempt into ASE may fail with a 1601 error after several recurring 709 errors have been raised because of procedure cache memory shortage.


Flush all data to the Sybmon log file whenver the 'log off' command is executed.


The SQL data type UNSIGNED BIGINT is currently mapped to the Java type "double". This conversion will incorrectly give an approximate value when the UNSIGNED BIGINT value is large enough.


When the sampling option is used for UPDATE STATISTICS, existing multi-attribute density values may not be reused. With this fix, range density and total density will be calculated from the sampled dataset, unless existing values were from a full scan of data.


sortkey('sjisbin') function does not work correctly with SJIS Hankaku-Katakana characters.


An interrupt during an open cursor statement involving a light weight procedure may lead to a stacktrace in the errorlog with functions curs_release(), close_range(), sortend().


If user do not has permission to table syssrvoles, will get error message "SELECT permission denied on object syssrvoles, database master, owner dbo" when selecting permissions tab under a stored procedure that login owns in Sybase Central. This behavior is corrected so user can still access this tab and read permission for users and groups (roles is blocked).


Assertion failure in Monitor Client library (SYDateTimeValue::init ())when client application uses cs_ctx_global() without CS_VERSION_110.


(OPTIMIZER) The estimated total cost of the final plan as displayed by the output of traceflag 310 may be incorrect in the case of a query with joins on more than 4 tables.


Some option settings may not be exported from login trigger to the session level.


This fix is to update logic of counting physical processors considering introduction of SMT (Simultaneous multithreading) capable Power5 processors.


This fix is to support additional license type "EV" for evaluation period license.


Provide default "Certificate password" and "Keystore password" for custom Web Service installation.


In rare circumstances the message "current process infected with 11" in the module 'senderror' may be reported in the error log together with a stack trace when executing a prepared dynamic statement.


Enables CTLIB API checking for dataserver. This is done through Traceflag 11297.


A 953 error may be unexpectedly raised while running the 'LOAD DATABASE' command for the master database, if ever one of the database living on the master device has been extended onto another disk device.


An unexpected 515 error, "Attempt to insert NULL value into column 'column', table 'table_name'; column does not allow nulls" may be raised when executing an INSERT statement inside a stored procedure and the option STRING_RTRUNCATION is ON and the value to be inserted only contains blanks.


When executing system stored procedure sp_helpdb and the option QUOTED_IDENTIFIER has been set some unexpected errors may be raised and the procedure will fail.


ASE returns conversion error 9502 when doing an implicit conversion from unichar to nchar.


Query performing view materialization using parallel strategy may return incorrect results.


CIS: "create proxy_table" which maps onto a remote server supporting DECIMAL identity might result in message 11246 "Precision or scale mismatch in remote object..."


Due to packaging error, ASE Plugin included in 12.5.3 ESD#3 and ESD#4 cause following errors. When ASE Plug-in that is coded with JRE 1.4 is run with 1.3 JVM, it gives stack trace during Create Table which results in a stack trace that says java.lang.NoSuchMethodError. When ASE Plug-in that is coded with JRE 1.3 is run with 1.4 JVM, focus error will be seen during Create Table.


The changes included in OCS 12.5.1 ESD#10 include fixes for the following issues: SCL/Kerberos memory leaks on successful connections when using MIT Kerberos, CR 385928. After many hundreds or thousands of successful Kerberos connections, memory leak resulted in memory allocation errors in the errorlog and authentication errors returned to clients. The memory allocation errors reported: "Security Control Layer's memory allocation routine returned an error." An API change occurred to OCS internal functions used by Security Control Layer (SCL) drivers called by ASE. The request ID changed to type long to handle 64bit request ID used by SCL and DCL drivers. CR 384600, the associated OCS fix, avoids a segmentation violation that can occur on 64 bit platforms when using Kerberos or Directory Services lookups.


Implement a NONTRANSACTIONAL PROCEDURE option for CREATE EXISTING TABLE to avoid blocking issues with SELECT INTO.


New sybmon command 'showrecovery' to print recovery information for a given database.


SCL error messages are not available to display on engine 1 and greater. Instead of the text message explaining the error that occured, the following message appears: 01:00000:00049:2005/10/12 15:59:25.84 kernel Failed to get the Connectivity Library (Security Control Layer) error message.


A stored procedure with the SQL query with an aggregate in the having clause may fail to execute correctly raising error 2805 "Bad pointer 0x3294d04 encountered while remapping stored procedure" or the execution may be broken and stack trace logged in the errorlog file. Module "proc__mkworkrg" should be referenced in the backtrace.


On a 64-bit platform, stored procedure "sp_helpjava" cannot display correct serialVersionUID.


There could be more reasons for Large I/O to be denied as compared to what is displayed in sp_sysmon o/p as has been indicated in cr 256785


Cross-platform load incorrectly fails to convert or initialize unallocated pages. In rare cases, the unconverted page contents may mislead recovery at some time in the future.


Sub-optimal performance for a query with a WHERE clause contianing col1 IS NULL AND col2 = < value > , with an index in col1, col2 and a high number of rows with col1 is NULL.


User datatype information is not correctly send in the TDS packet for cross database queries on tables with columns based on user defined datatypes.


Under circumstances, when ASE is running multiple engines and more than 50 connections, doing java functionality, the JVM use to throw various stacktraces when it calls GarbageCollector for recollecting memory.


SSL5 feature is supported on hpia64 platform for ASE 12.5.4


DBCC ORPHANTABLES may fail to clean up an orphaned temporary table that resides in a temporary database whose ID is different from the current session's temporary database ID.


CIS: Error message 3708, "Cannot drop < table_name > because it is a system table." and message 2601, "Attempt to insert duplicate key row in < object_name > with unique index" may be reported when executing a CREATE DATABASE ... FOR PROXY_UPDATE against MSSQL backend.


A query like: select @v = @v + id from sysobjects where @v +id < 104, which has an expression in the select-list as well as an expression in the WHERE-clause can cause a query plan to be generated that contains a RestrictOp as the parent of another RestrictOp: One RestrictOp will evaluate the expression in the select-lis while the other will evaluate the expression in the WHERE-clause. Although the query results are correct, there can be a slight performance impact of having two RestrictOps when a single RestrictOp could do the same processing.


During shutdown, the XP Server was consuming all available CPU time due to a difference between Mac OS X 10.3.x and 10.4.x. A system function (dlclose())was returning failure, as expected, in 10.3.x, but was always returning success in 10.4.


SSL5 feature is supported on RedHat Linux Opteron 64bit platform for ASE 12.5.3


CIS : When the UPDATE STATISTICS command is issued immediately upon creation of a proxy table containing clusterd index in an Allpages lock scheme, an erroneous entry in SYSTABSTATS with column id 0 (object id) will be created and the ASE internal housekeeper task may monopolize the CPU utilization to 100%. During ASE shutdown, an error message 6008, "Unable to write statistics for object < objid > in database < dbid > . Please run update statistics on this table after boot-up or prior to accessing the table next time" will be reported in the errorlog. Once ASE that contains this fix has been started/rebooted, the entry in SYSTABSTATS with id = 0 should also be manually deleted.


Client application based on DBLibrary API and executing UPDATE statements using the TSEQUAL() function may fail and the client server connection gets broken with TDS protocol errors. This is due to the extra result set sent by tsequal() builtin which may not be correctly handling by DBLibrary API.


In rare circumstances, running OPTDIAG with simulate statistics -i < input_filename > option might cause the optdiag binary to crash, if the input file is missing the title for the "default data cache".


A presence of the named CHECK constraint in the temporary table definition prohibits creation of multiple instances of the table. User will see error 2714 with the message "There is already an object named 'constraint name' in the database." when attempting to create a temporary table.


Modify MDA table definitions in the installmontables script to access monitoring data through local connections. This eliminates the need for a loopback remote server definition when using the MDA tables.


CIS: CREATE INDEX options IGNORE_DUP_KEY and IGNORE_DUP_ROW are not ignored when executing an INSERT or UPDATE query to a proxy table in a remote ASE.


For Adaptive Server Enterprise running on HP-UX systems with asynchronous I/O enabled, if /dev/async runs out of free ports, any attempt to online an engine causes ASE to shut down.


The audit sub-system unexpectedly causes empty beginxact/commitxact pairs in a database transaction log if the SELECT command is audited on a table and the transaction mode is 'chained'.


sp_helpmaplogin truncates the display of client name and login name to 20 characters


CIS: Insert text or image data into ASIQ 12.6 may cause a hang on ASE. The spid needs to be manually killed from another ISQL session.


Query selecting from a view with UNION may fail with error 104: "Order-by items must appear in the select-list if the statement contains set operators." if in the parent query ORDER BY clause is used on the view column which is not present in the parent's query SELECT list.


When a stored procedure fails then the error handling procedure tries to read the sysattributes table. But if the stored procedure itself failed because of a failure accessing sysattributes then the error handler can be triggered recursively leading to an infinite loop. The requirement to read sysattributes has now been removed from the error handler


Attempts to load shared memory dump files on Linux may fail due to erroneous reports of memory segment overlap


Msg. 103, 'The transactionname that starts with < name > is too long. Maximum length is 67.' is raised using BEGIN TRANSACTION @variable whereby the @variable contains a transactionname greather then 67 bytes. Maximum allowed for a transactionname is 30.


The error 8240 with the message : "The table 'table_name' in database 'db_name' is being created and the transaction has not been committed yet. Please retry the query later." may be raised if the parallel query is executed on a table created in the same transaction.


DDLGen generates 'null' in permissions statements. For eg. for pubs2 database, 'titles' table, some incorrect statements generated are: Grant null on dbo.titles to guest go Grant null on dbo.titles to guest go


If table data copy fails on a table with an identity column, Migration tool may issue the error: "Unable to 'SET IDENTITY_INSERT' for table ' < tablename > ' because IDENTITY_INSERT or IDENTITY_UPDATE is already ON" on subsequent tables.


Session cleanup processing can encounter an "engine affinity stack overflow" during Kerberos authentication processing if the client disconnects during a narrow processing window.


A query violating cross database referentail integrity may sometimes fail to report referential integrity error. Instead of this a client session may get killed and the message reporting TDS packet synchronization problem will be displayed.


Query performing outer join between views with union may sometimes fail to execute.


INSERT into a table with a VARCHAR column may incorrectly leave trailing spaces in the VARCHAR column if the source of the data is a table with longer VARCHAR column.


The following error may be seen in the ASE log: "Error 120510: ksmask__rpacket: Invalid tdslength value < length > ". This is usually caused when a non-TDS client connects to the port that ASE is using as its master listener, and sends data that is not in valid TDS format. An additional message will now accompany this message providing the IP address of the client in question, so that it can be tracked down. In addition, traceflag 7845 can be used to suppress these messages if they cause a nuisance.


A 631 error, "The length of < value > passed to delete row routine for the row at offset < value > is incorrect on the following page ..." may be reported on Sysdevices when during the execution of a DISK MIRROR command a buffer pool whose size is greater than 2K bytes is used by ASE.


In rare circumstances an ASE task my terminate with a timeslice error while a configurable shared memory dump (CSMD) is being generated. This problem does not apply to ASE running on the Windows platform.


Stored procedure executing INSERT statement into a temporaray table from the remote table may fail with error 208 "Object not found" referencing the temporary table if the system is configured to use multiple temporaray databases.


ASE gets segmentation violation in sec_recv_params() during Kerberos client login when an unusually large security token is given by the client to ASE during authentication.


In very rare circumstances the message "Infected with 11" together with module names "show_plan" can be encountered when using sp_showplan to look the plan of another process.


The message "timeslice < negative number > , current process infected" maybe reported in the errorlog together with a stack trace which includes the modules 'ns_handle' and 'ns_prep_stmnt' if a batch including together a CREATE TABLE statement and a SELECT executing java was being executed and an error condition happened.


In very rare circumstances, Adaptive Server may loop while allocating memory from procedure cache, and the looping SPID can not be killed.


The following messages are seen in quick succession: 'ubo_object_from_slot:Sybproc Invalid slot id 0' followed by 'kernel current process (0xb000b0) infected with 11'.


JS Schedule wizard and properties window display an error when trying to create a schedule with a 1 day interval, but restricted to selected days of the week or days of the month.


Cache binding information is not being written to unpartition restamp log record. So, during runtime rollback, the pages are being fetched into the default data cache. This is leading to the condition that a page is in two caches at the same time. So, further attempts to fetch the page throws 693 error.


When statistics are not available for the optimizer to make accurate estimates, the default selectivities could result in long compilation times before optimization timeout occurs, since the optimizer is searching for a better plan. The adjustment to cost estimates for joins when no statistics are available was to use a formula similar to pre-15.0, which based on the larger of the rows counts from either side of the join.


In rare circumstances one or more ASE engines may remain non responsive after a Configurable Shared Memory Dump (CSMD) completes, causing an inability to connect to ASE. This issue does not apply to ASE running on the Windows platform.


ASE running on the HPUX/Itanium platform does not retry i/o operations in the event that they are interrupted by signals from the operating system. This can result in an operation being reported as 'failed' when simply retrying the operation would result in success.


While executing the jobs having job command text > 1800 characters, the jobs may not get executed and even jsagent process and Job Scheduler task in ASE may terminate. As a result of Job Scheduler task terminating, messages such as "Job Scheduler Task set to stop", "Job Scheduler Task was not stopped by a Task shutdown request" etc. appear in the errorlog file.


Enable Encrypted Column feature on HP Itanium 64bit platform


JVM performance degrades after applying ESD #4 or ESD #5 on all platforms excluding sgi, hp and solaris 64-bit.


Error 2581 "Data page ... indicates that an overflow page is linked to it; however, the next page ... has not been marked as an overflow page." may be reported by DBCC CHECKTABLE on an All Pages Locks table that has a clustered index whose overflow pages deallocations needed to be redone by the recovery process either at boot time or after the LOAD TRAN command was run.


If the Korean locale is used, Open Client and Open Server application will fail due to a missing 'escape' character in the file $SYBASE/locales/message/korean/libinsck.loc [copyright] message.


Job Scheduler GUI: A Schedule's Between time option is not being saved when selected.


Disable collection of data for the monOpenObjectActivity MDA table if a process encounters a stack overflow condition.


DBCC CHECKTABLE will now report errors if these exist in the root key information area in the BTREE index root page.


Under rare circumstances it may not be possible to drop a stored procedure, unless ASE is restarted, if a session failed to execute this stored procedure because of error 216 "Attempt to automatically drop temporary table failed." that was hit due to disk space shortage in a temporary database and ASE has also aknowledged an attention event (Control-C) emitted by this session following these errors.


A 691 error, "Encountered invalid logical page '0' while accessing object '8' in database ' < dbid > '.", 623 or 806 error is reported by ONLINE DATABASE command after loading a database with a cross-platform dump and the database is in read-only mode.


Job Scheduler database, sybmgmtdb, may not be freeing space as defined by the user in the the JS Administration window.


ASE fails to start with TLI style interfaces entry


The message "current process infected with 11" in the module 'ind__get_sysindrow' together with a stack trace may be reported in the error log if a trigger containing "inserted" or "deleted" is fired on a table that has been renamed and that the old table name is used on another object (e.g. a view).


This is customer's request. For ASE15.0, no matter the client can support large identifier or not, the ASE will send the large identifier names to the client and this could cause the problem. To fix this problem, the ASE will check if the client could support large identifier or not, if the client does not support large identifier and the identifier name is longer than 30 bytes, the ASE will raise an error msg; otherwise, sending the large identifier.


A 206 error "Operand type clash: < datatype1 > is incompatible with < datatype2 > " maybe be raised when executing a stored procedure containing a SELECT CONVERT( < java datatype1 > , < java datatype2 > ) statement in a database that was loaded from a dump of a database with different dbid. If the source database is dropped errors 913, "Could not find row in sysdatabases with database id < dbid > . Run DBCC CHECKTABLE on sysdatabases." and 11060 "This statement has exceeded the maximum number of recompilations (10). This indicates an internal error. Please note the error prior to this one and contact Sybase Technical Support" are raised instead.


Add Encrpyption Column feature to ase15x on linuxamd64 platform.


The error "Could not find virtual page for logical page 9984 in database 'master'", with a stack trace which includes the modules like 'log_to_virt', 'virtmap ', 'bufgrab ', 'getpage_with_validation ' , will be reported if the requested size for master database is not multiple of size of allocation unit. The similar error will be reported in case of model database also.


If sp_configure is used to change just the server's default sort order (without changing the server's default character set at the same time), and before rebooting, a subsequent change is made to nearly any parameter, then after the reboot the new sort order appears to have taken effect (according to the errorlog and sp_helpsort) but it doesn't in fact work.


After a SELECT-INTO, where encryption is specified on the target table and where the data is generated from a UNION of SELECT statements, a subsequent SELLECT of the data in the target table will generate the error, "Msg 154133, Level 18, State 5, An internal error occurred during an encryption operation (errorcode -1). Please contact Sybase Technical Support".


During an upgrade in which statistics exist on an encrypted column, there is an inconsistency introduced into the statistics for that encrypted column. This fix will prevent the inconsistency from being introduced in the catalogs, so that queries can correctly complete when referencing the encrypted column.


On platforms other than Intel/AMD, inserting data to a fixed-length unichar column that is shorter than the actual length of the column, and where the unichar column is not aligned on a 2-byte boundary in the page may cause the process to terminate with a bus error.


Enable LDAP User Authentication feature on hpia64 platform


When using the monDeadLock MDA table and a process executing a stored procedure or trigger is involved in a deadlock, the monDeadLock table HeldProcDBID and HeldProcedureID columns do not report the DBID and Object ID of the stored procedure or trigger.


Enable Encrypted Column feature on Solaris AMD Opteron 64bit platform


In rare circumstances, an 822 error, "Could not start I/O for request BLKIO flags..." or other recovery-related error may be reported during the failover of a primary server to a secondary server in an HA environment.


A SELECT from a proxy table mapped to an RPC will abort the entire transaction if the RPC returns a status of 0.


When large quantities of memory is allocated, from procedure cache, for a single query, performance may be affected adversely due to lengthy chains.


Listing the tables in the FROM clause in a different order could result in a very different query plan, sometimes a very bad performing query plan.


Update Statistics Wizard's first page contains a list of table columns and their types. The column types are now displaying correctly.


Corrects a performance issue with IN lists If a table t1 has an index i1 on columns (a1,a2,a3) and multiple IN lists are defined e.g. select * from t1 where a1 in (1,2) and a2 in (10,11) and a3 in (100,101) the optimizer would only consider costing subsequent IN lists if the previous IN lists were reasonably selective. The change is to cost all IN lists, since strongly selective IN list can follow weak IN in lists, and then determine whether to avoid some less significant IN lists due to poor selectivity.


Backup Server error[23] "The 'read' call failed for device 'device_name' with error number 14 (Bad address). Refer to your operating system documentation for further details." or error [105] "The 'uncompress' call failed for device 'device_name' with error number 0 (Error 0)." is returned, when a database dump file that was generated with 'with compression= < compression_level > ' clause is loaded across platform.


In extremely rare situations, recovery of the current database page timestamp can result in a value a few increments lower than in specified behavior. The practical impact is virtually nil, and any theoretical problem quickly resolves after a few new runtime updates.


Previously certain ASE Plug-in icons such as Indexes appeared cut-off. This has been corrected.


Queries involving inner tables of an outer join query with predicates of =NULL returns wrong results. An example of such a query would be: select 1 from r left join s on r.a = s.a where s.a = NULL


When an ANSI outer join query has an equi-join in the ON clause and one of the equi-join columns also has "col= < ct > " in the WHERE clause, the optimizer will not consider using the MergeJoin algorithm, although it's legal under these circumstances.


On IBM Power Linux platform, stacktrace does not report all the functions on the stack.


A 625 error may be reported by sp_post_xpload if a user table is updated before index is rebuilt manually or by sp_post_xpload, and after a database dump has been loaded across platform and brought online.


A UNION query such as: select a from x where 1=2 union select b from y, which contains a predicate that is always false (in this case 1=2) in the first SELECT of the UNION may not return all of the rows of the result set if the query plan chosen by the optimizer contains a hash-based UNION operation. The presence of the hash-based UNION operation in the query plan is shown in showplan by the line: HASH UNION Operator.


Previously when user right-clicked a table, "Edit..." menu item was missing. This has beeen added so that user can edit the table using Table Editor.


Attempting "LOAD DATABASE master" from a dump where the disk map in the dump does not exactly match the disk map in the target server can cause ASE to encounter a page read error, which it reports as error: 695, state: 1. This causes the load to fail.


When importing statistics in simulate mode resulted in some selectivities to be out of bound thereby causing poorer plans.


Wrong results produced when selecting from a table that is list partitioned and the WHERE clause of the SELECT statement has a BETWEEN predicate on a column that is not the partitioning key.


CIS: When retrieving IMAGE data, ASE may encounter a SEGV in routines omni_rly_row() and memallocheap().


All partitions can be eliminated in queries against a partitioned table that is list partitioned and contains queries that has a predicate on the partitioned key that is used to eliminate partitions. The predicate must be composed of a BETWEEN clause on the partitioned key AND another predicate on the partitioned key that selects ONLY the partitions that would be selected by the BETWEEN predicate.


Update table statistics command is enhanced to enable generation of systabstats statistics for an index or an index partition.


In rare circumstances, column data may not be translated if more than 127 contiguous columns data are non-null values and all the columns require translation and all translation type is same length, when database dump file is loaded across platform.


DBCC CHECKTABLE may fail to report error 2510: "Key mismatch between index page < index pno > , partition ID < ptnid > ; at offset < indoffset > ; and data page < data pno > (row ID < rnum > ), partition ID < ptnid > . Drop and re-create index ID < indid > of table ' < tabname > ' in database ' < dbname > '." and abort silently, or return "Invalid parameter" error with 2510 error message.


Enable LDAP User Authentication feature on Solaris Opteron 64bit platform


Conversion errors, error code 257, raised during optimization when there is a constant expression in the WHERE clause of a SELECT statement. These constant expressions involved VARCHAR data types.


Increased size of sybsystemprocs database from 120MB to 132 MB.


Create unique local index on range/list/hash partitioned table should be allowed even when the index key list sequence is not the same as that of partition key, as long as the partition key list is a subset of index key list


Enable JS feature on linuxamd64 platform.


Enable LDAP User Authentication feature on Linux Opteron 64bit platform


When command-line trace flag -T450 is set, queries involving a group-by clause (and having 32 or less distinct group-by columns) will have a predicable ordering similar to that of ASE 12.5.x. Namely, in the absence of an explicit order-by clause, ordering will be that of the group-by columns.


Excessive compilation time when there are a lot of range or list partitions in the joining relation(s).


This fix is to update logic of counting physical processors considering the introduction of CMP and CMT capable processors.


This fix is to update logic of counting number of physical processors considering the introduction of intel hyperthreaded processors.


If path ends with \, dbisql.bat will gives java syntax error. Correct that by adding ; at the end of path inside dbisql.bat


Adds Replication Agent support for alter table < table_name > drop partition.


Enable MIT Kerberos feature on HPIA platform


Enable MIT Kerberos feature on Linux IBM pSeries platform


sqlupgraderes can not boot old ASE in the upgrade process.


A suboptimal plan could be chosen for a query that has a large "IN (values ...)" WHERE clause and whose SELECT list columns would make a row too large to store into a worktable.


This fix is to support new license type "NA". "NA" stands for not applicable.


The fine-grained algorithm enabling/disabling settings are currently available at the connection level, through the SET XXX ON/OFF/DEFAULT, where XXX is nl_join, merge_join, etc. There settings should be available also at the query level using AP language extensions (as currently the case for the optgoal and opttimeout settings).


The query plan for a query such as: select substring ('back yard', -1, -4) where 1 = 2, which has an expression in the select-list, but also has an expression in the WHERE-clause that disqualifies all rows will still cause the select-list expression to be evaluated. In the example, the expression is invalid, so an error will be returned, even though no rows qualify.


The sqlloc utility does not show charset gb18030 when 'Chinese' language is chosen.


When, on a table, 2 function indexes are created, and subsequently the first index is dropped, ASE stacktraces and terminates


CIS: Error msg 691 together with a stack trace which includes the modules 'txtimg_upd_table' and 'amc_finish_command' may be reported in the error log if ALTER TABLE ... MODIFY a column to null on a proxy table with any text or image column


Previously (15.0 ESD#2 ASE Plug-in) BCP menu for a view is located at the end of its context menu. This has been moved to closer to the top of context menu to be consistent with other object's context menu.


Database page might be initialized and result in 1142 error or error message 'Unable to find the sysusages row that controls the allocation page < pageno > while doing the extents accounting for OAM page < pageno > , object ID < objid > , index ID < indid > , database ID < dbid > (OAM entry nn).' printed in the errorlog during ONLINE or 692 error during sp_post_xpload, after 15.0 database dump file was loaded across platform if there is an un-upgraded allocation page in the 15.0 database dump file. This problem happens only after a pre-15.0 database was upgraded to 15.0 and was dumped again on 15.0, then loaded on 15.0 again across platform.


Incorrect percentages may be reported while dumping a database.


The server may raise error 702 while running a large union query and "statistic time" option is set to on.


When a shared memory dump is performed on the Linux platform using the CSMD facility a message saying that "at least one engine failed to halt" may be written to the errorlog. This problem has been corrected.


Use of the dataserver -k command line option incorrectly generates a usage error message and prevents ASE startup from proceeding.


Wrong scalar aggregate (such as count()) result when all partitions in the underlying table have been eliminated during compilation.


Queries that have a large number of joining tables and also contain subqueries in the SELECT and the FROM clause can result in a stack trace if the opimizer times out before getting a valid plan.


An INSERT SELECT ORDER BY query could require a Sort and run thus very slowly despite the needed ordering being cheaply available form the existing indices.


To add/edit a JINI server discovery entry, ASE Plug-in now uses a spin box (instead of a text box) for accepting the port number of the entry.


Previously Connect dialog displayed error message ID instead of the error message when server discovery through "Find..." returned no results. This has been corrected.


ASEPlugin used to wait for acquiring connection when connected to a standard port (like telnet=23), sometimes it would be around 15minutes, causing ASEP to hang. This fix adds a user settable parameter in ASEP- > Settings Tab, to control the login timeout period. By default it is 30secs.


On some platforms (like Windows), the "upgrade" utility program might terminate abnormally with a segmentation violation or access violation if the program failed to execute an upgrade step correctly.


DBCC CHECKTABLE may report error 15080, reporting an inconsistency in the root key information on BTree root pages of DOL tables. This will occur if an ALTER TABLE operation was performed on a DOL table to increase the length of a variable length column, and that column was used in some index. If this inconsistency is reported on a system catalog, use DBCC REINDEX to rebuild the specific index showing this inconsistency. For user tables exhibiting this condition, drop and recreate the affected index.


In the Syconfig.exe configure new Backupserver options screen, the character set drop down list doesn't contain all valid character sets in non-English language.


MSGCONSUME does not abort the transaction correctly for some RTMS errors, which will cause the consequent stacktrace.


When ASE's license limits the total permitted amount of disk space used for data storage, and a DISK RESIZE command attempts to add space to a device, and the resulting total space is within the permitted limit, ASE will incorrectly report that the named device does not exist.


DDLGen inserts extra white spaces (tabs) in check constraint definition if the length of the definition of a single constraint exceeds 255 characters.


102 error given for "with override" option for load database on linux 32bit.


A SELECT from a proxy table on ASE 15.0 that is mapped to a remote table on an earlier version of ASE with a name 29 or more characters long will result in an Error Msg 103.


There were some instances when interrupts and kill were not recognized and the query could not be aborted. More checks for interrupts and kill are added during execution of a query.


SP_SPACEUSED < table_name > may report an innacurate value for "rowtotal" if the given table resides in a temporary database.


The SP_CONFIGURE stored procedure trying to change both the 'default sortorder id' and 'default character set id' may not work correctly if the old and new values for first parameter in sp_configure are same.


sp_dboption fails with an error message "Cannot checkpoint database < db_name > because its status is: offline, online for standby access, read only." if the database is set to readonly and an upgrade of the database that was loaded from pre-15.0 version of ASE has not happened yet.


The error " Syntax error encountered. Sizes must be of the form int[KMGP]. For example, a size of 5 megabytes may be specified as '5M'." will be generated if in the SP_CONFIGURE command both "default character set id" and "default sortorder_id" are changed together and second argument is 0.


The value of the monProcessActivity table CPUTime column is occassionally reset to zero. As a result, this column may not report the cumulative CPU time for a process.


The store index operator used in the reformatting strategy did not have the join keys created properly, so that instead of a nested loop keyed lookup, a cart prod was performed, although the costing expected that a keyed lookup would be done. This resulted poor performance when expressions were used in a join, which used a reformatting strategy.


Error 2823 "Process x tried to remove a PROC_BUF 0xxxxxx name '*ssxxxxxxxxxxx'.." maybe produced when two sessions execute the same SQL in an ASE where "statement cache" is enabled.


Transient I/O issue could cause timestamp mismatch error (12315) during btree scan.


DB LIB function, dbdatlen(), returns a wrong result with fixed length char column in ASE15


When ASE is started with the Express Edition license, it is possible to exceed license limits on total disk space by using the "disk reinit" command.


Adaptive Server Enterprise may crash with a stack trace pointing to terminate_process


Normalization failed to remove NOT nodes for a query that projects a built-in function with a subquery as the argument.


Previously a server discovery filter for finding servers with port number less than a number didn't work. This has been corrected.


An assertion failure and stack trace could be produced when: - the query is unconnected, in that not all FROM clause tables are connected with eachother through join clauses; - a subset of the FROM clause tables form a STAR query, in that there is one table that is equi-joined with each of the other ones; - another subset of the FROM clause tables contains at least 2 tables, that join with eachother but don't join with tables in the STAR subset.


When enabled, set index_union limits the scan of a table with an or clause.Index unions (also known as an or strategy) are used for queries that contain or clauses. For example: select * from titleauthor where au_id ="409-56-7008" or title_id ="PC8888" If you have enabled index_union, this example uses an index on au_id to find the row IDs (RIDs) of all titleauthor tuples with au_id =409-56-7008", and uses an index on title_id to find the RIDs of all titleauthor tuples with title_id =PC8888". Adaptive Server then unions all RIDs (to eliminate duplicates). The resulting RIDs are joined with a RidJoin to access the data tuples If index_union is disabled, Adaptive Server does not use an index union strategy in a query to limit the table scan. Instead it uses other access paths on the table (in the example above, it would use a table scan for table titleauthor), and applies the or clause as a filter in the scan operator.


695 error maybe given when a load of a database has been aborted and another database is being dropped during cross platform dump and load.


When creating a Job Scheduler schedule from the command-line utilities, the user may receive an error stating that the startdate is later than the enddate when the schedule enddate is specified but the startdate is not specified.


The error 644 "Index row entry for data row id ... is missing from index page ... of index id 2 of table 'syscolumns' ..." may be reported when a syscolumns row is being updated in the deferred mode as shown by sp_showplan and the row being updated is the forwarded location.


In rare situations during ASE shutdown a stack trace may be seen showing a storage access violation in ntdll.dll (this only affects ASE running on Windows systems).


When the statement cache is configured for Adaptive Server, the bcp 'out' command used with the '-C' flag fails with Msg 225 when copying out encrypted data.


Stack trace associated with error 14127 "Cannot drop or modify partition descriptor ... as it is in use. Please retry your command later. Total reference count ... Task reference count ..." May be seen rarely when create placement index command is rolled back for resources reason.


Web services folder does not open when ASE Plug-in is connected to pre 15.0 servers. It gives a stack trace when an attempt is made to open this folder.


set option show_missing_stats on reports missing stats on columns with BIT datatype, which is noise, since update statistics cannot be done on BIT datatypes


An outer join query with an ON clause containing a join condition with constants would stack trace. An example of such a query would be: SELECT * FROM (SELECT 1 AS Col1) TableA LEFT JOIN (SELECT 1 AS Col2) TableB ON 1=2


Errors 950 and 5903 maybe given when dropping an encryption key if one of the databases is offline. Warning 15427 should be given instead and the key should be dropped.


When a user generates DDL for database objects, a dialog shows up to allow user to exclude certain objects for DDL generation. The objects would be incorrectly selected when Table is selected and the list is sorted by clicking the column header. This has been corrected.


A stacktrace may occur when a query is executed on the monProcessObject MDA table.


If a Lava parallel query terminates abnormally, then a SEGV could occur in terminate_process() effectively shutting down the server engines.


The message "current process infected with 11" in the module 'void CgpPop::setDataIOHints(int,int,int)' may be reported in the error log if a query uses TOP on a local index.


After creating a compiled object (view, stored procedure etc) in ASE Plug-in through the template, the next time when you try to bring up the template for creation of a new object of the same type, the template does not come up


Queries involving constant predicates under OR (e.g. 1=@v1 OR r.a=5) could result in poor performance since the selectivity of the constant predicate (1=@v1) was not accounted for resulting in possible poor join orders. Magic numbers are now used for the constant predicates.


A SELECT * from monLicense in a multi-engine configuration could result in a stack trace which includes VTABRemoteAccess::mdaStartScan.


Previously ASE Plug-in did not close connections to Unified Agents, causing the agents to potentially run out of memory. Now ASE Plug-in explicitly closes all its connections to the agents when Sybase Central exits. Note this may cause a slight delay in closing Sybase Central.


A select from a very large table with an IN list greater than 40 may fail with a stack trace that includes CgLavaUtils::CgCompVirtualCol.


Cntr-C did not interrupt a long compilation prior to this bug fix, and would only be processed once the compilation was complete


No best plan found when user specifies potential conflicting optgoal and optimization criteria. For example, use fastfirstrow optgoal and turn off nljoin at the same time could sometimes lead to the case because the only viable join operator for some query under the optgoal would be nljoin.


Wrong result (missing rows) could happen for query INSERT ... SELECT DISTINCT ... ORDER BY which also satisfies: 1. there is some expression as part of the SELECT DISTINCT items. 2. some ORDER BY items are NOT part of the SELECT DISTINCT items.


In rare occasions, error 1156 may be reported and stack trace occurs when trace 2901 is on when create placement index command fails due to resources reason.


Error 940 "Dbtable in wrong state for operation: ... keep = 0 ..." may be reported in the error log in module "dbt_unkeep" during the execution of an UPDATE command whose trigger has a cursor statement that references TEXT/IMAGE columns. The modules "xact_commit" and "xact_end_session" will also be reported in the stack trace.


When a database is bound to a named cache and that database is upgraded, the upgrade succeeds but ASE will report error 858, "Cache [name] does not exist" for that cache. The upgrade utility records this message as a failure.


Staled buffer could be used for index building, and wrong page could be used in index chain, raising wrongpage error or wrong ptnid error (12329 error).


A SQL query with a correlated subquery can cause a stack trace to happen, when run under parallel mode. If the same query is made to run in serial mode, it works fine.


In Sybase Central ASE Plug-in, when repartitioning a table with list partition strategy, you may get an 'Incorrect syntax error' if in the list partition spec dialog you enter blank values for the list partition set of values.


NullPointer seen when call Tool- > datatypes from Table Editor.


Aggregate(s) in a subquery could generate an incorrect parallel plan and caused stacktrace from LePipeRWState::LePrwsRWVtuple(LeVtuple*,pipe_client_rwmode,int) during execution.


When a query plan has several occurences of a table for a single table occurence in the query's FROM list (as for non-combinable aggregates, extended columns aggregation, GROUP BY ALL, etc.), the Abstract Plan has no way to distinguihs between them. We need to generate unique internal names in such a case to be able to apply lated such an AP.


The Job Scheduler Administration window always reports that the Job Scheduler is running, even when it is stopped.


When 'statement cache' is enabled and there are large in-lists (e.g. 15000 in-lists), timeslice error may occur.


sp_cacheconfig will display wash size as '****** Kb' if the number of digits in the wash size is greater than 6.


There was a problem in the hash distinct and hash aggregation operations when processing large datasets. This could possibly lead to duplicate rows in the distinct case and/or incorrect row interpretation in the aggregation case.


A java.lang.NullPointerException is thrown if the user selects the key checkbox on the column encryption tab (within column properties) and subsequently selects the property button.


The message content for eight resource-level insufficient-memory errors has been expanded to recommend an action. Each such message gains this sentence: "Raise the value of the configuration parameter 'procedure cache size'". The eight affected errors have these error numbers: 3001, 3103, 3161, 3162, 3228, 4201, 4979, and 5203.


When create clustered index on large partitioned tables (especially those just upgraded from 12.5), 832 error could be raised during the sampling phase.


If 'statement cache size' is configured to a non-zero value in Adaptive Server, a Replication Server session may report error 225 'Cannot run query--referenced object (NAME NOT RECOVERABLE) dropped during query optimization' when the query processes an encrypted column.


Too few rows could be returned when dynamic partition elimination occurs on DOL tables due to the ILA "Index LookAhead" optimization. This will only occur if the access pattern for rows switches on ILA at the parent level and the next access moves to a new partition. This would generally occur when the table is on the inside of a NLjoin strategy. Note, the problem does not occur with the ILA optimization is done at the leaf level. Problem can be worked around using trace commandline flag 12611.


Error:8419, Severity:20, State:3 may occur when an installation has not been upgraded and a query had been executed. All users, other than the users with sa and operator roles, are not allowed to access a database that is yet to be upgraded to prevent errors in databases that have not been upgraded.


When calling a SQLJ procedure, from jConnect, that returns multiple result sets, only the first result set is returned.


A database or transaction log dump that was taken using the WITH COMPRESSION = < compression > and the AT < remote backup server > options cannot be loaded using a local backup server (that is, without the AT < remote backup server > option). In addition, the dump that is created is not compressed despite compression having been requested.


When 'statement cache' is enabled, server may stacktrace when executing a select into query with nested union operators.


For very large tables, with more than 2,200,000,000 rows, sp_spaceused reports lead to arithmatic overflow.


The 12.5.4 Backup Server is unable to load a dump taken using the WITH COMPRESSION option, when the dump was originally taken remotely (using the AT option) but loaded remotely (without the AT option) and vice versa. Likewise, Adaptive Server is unable to load this dump into an archive database.


An outer join query, where the inner table of the outer join is range or list partitioned can result in wrong results. This is because the upper bound of the outer join or the entire partitioning conditions for the list partition on the inner table is being evaluated at the WHERE clause rather than the ON clause.


A user that is not valid in a database may gain access to objects in that database via a system stored procedure that is executed from a database different from the one where the procedure is created.


There is an incompatibility between Adaptive Server and RepServer 15.0 when replicating an alter table statement that modifies an encrypted column to change the key or the data type. The data type of the encrypted column in the replicate database is changed to varbinary.


When a loaded database needs to be upgraded but its transaction log has passed the last-chance threshold, ONLINE DATABASE will report that it could not bring the database online but will not say why. (Reason: log is almost full, so upgrade could not happen.)


The error "No virtual mapping for logical page < pageno > " followed by a core dump of the backup server will happen if the command LOAD DATABASE WITH VERIFYONLY is run and the database from where it is executed is smaller than the database being verified.


Localized versions of ASEP may display a NullPointerException when the user opens the properties window for a Job Scheduler Schedule or selects the Time tab in that window.


For an allpage locked table with a clustered index, built-in USED_PAGES() will now return the used pages for the data layer alone when queried with index ID of 0. And it continues to return the sum of used pages for the data and index layer when queried with index ID of 1.


Wrong duplicate result rows in the result for SELECT DISTINCT cname=NULL, ... query.


701 error or timeslice error happened when using "set forceplan on" for a query with a lot of joining tables.


A query of the form 'IF (@v IN (1,2,3,..,41))', where the IN list contains more than 40 values can result in error 325 (Adaptive Server finds no legal query plan for this statement.) or a stacktrace that includes the routine _popDistCheckAndLazyEnforce.


Selecting a template from the Add Job Template Browser window causes a NullPointerException.


SELECT FOR BROWSE may return incorrect table name/column name information.


In some cases, the nary-NLJ strategy could return too few rows. This could occur if and only if one of the inner scans was on a DOL table "T", the table had two or more SARGs on it where some of the SARGs were dependent on different outer scans (or a constant) and some instance of opening "T" qualified no pages/rows.


The error 678 "Invalid Buffer Cache Access: Could not open object ' < value > ' in database ' < value > '" may be raised mistakenly during the execution of DBCC CHECKALLOC with the FIX option or DBCC TEXTALLOC with the FULL and FIX options, if the object being corrected does not exist anymore in the given database. This error results in the abort of the given DBCC command.


A table with both an identity and timestamp fields will insert bogus timestamp values for all new rows.


Under some circumstances a SELECT statement containing subqueries in the target list could return incorrect values for those subqueries if the same subqueries are used within predicates in the WHERE clause.


While upgrading auditing database 'sybsecurity', ASE can report that upgrade could not install item 244. This causes upgrade of sybsecurity to fail. ASE does not report the reason for the failure.


Syntax errors of Abstract Plans will be reported if 'g_join' or 'm_g_join' clause is followed by more than two tables which is, however, supported syntax before Galaxy release


A UNION query with a select statement (other than the first one) that returns no rows will return too few rows if the optimizer selects a query plan with a hash-based UNION operation. The presence of the hash-based UNION operation in the query plan is shown in showplan by the line: HASH UNION Operator. The following query is representative of such a union query where the second select statement will return no rows: select 1 union select a from x where 1=2 union select 2


The boot time recovery of a database that has a big syslogs segment allocated to it, irrespective of it being a dedicated log sergment or not, may take more time to complete compared to a pre-15.0 ASE system. The recovery process will spend cycles in module 'pg_logdevusage' in reading each syslogs allocation page while establishing statistics information in module 'systs_fill_catalogs' as opposed to only consider the statistics information that was retrieved from the systabstats system catalog already.


Fewer rows may be deleted than specified by a delete query using a join to at least one additional table. This may occur if the chosen plan uses a merge join, and the rows are deleted in 'direct' mode (does not occur with deferred deletes). This may only happen when deleting from APL tables and requires duplicate values in the joined column.


Sometimes an outerjoin ON clause was not considered as an index sarg causing bad performing index scan when the ON clause was involving expression on one side of the join. Also false join could be added to the plan causing wrong results when there were nested outerjoins in the query.


When a cursor that joins two or more tables is declared with a FOR UPDATE clause, a subsequent UPDATE query using the the WHERE CURRENT OF cursor clause may cause a 594 error: The UPDATE WHERE CURRENT OF to the cursor ' < cursor_name > ' failed because column ' < column_name > ' being updated was not specified in the SELECT list. The error can occur if the optimizer chooses to join the tables in an order that is different from the order of the tables in the FROM clause of the DECLARE CURSOR statement.


When additional license sources are specified in the SYBASE_LICENSE_FILE environment variable then ASE fails to boot. The LM_LICENSE_FILE environment variable can be used instead, however, it is recommended that all license files (including files that point to license servers) are placed in the $SYBASE/SYSAM-2_0/licenses directory, rather than ASE relying on a specific runtime environment to obtain it's licenses.



  • SAP Adaptive Server Enterprise (ASE) 15.0.1 IR
  • 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


Fix, Patch, 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.