2077481 - Targeted CR List for ASE 15.7 SP130 -SAP ASE | SAP Knowledge Base Article

SAP Knowledge Base Articles - preview

2077481 - Targeted CR List for ASE 15.7 SP130 -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 service.sap.com.

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

CR number



Adds the PREPARE DATABASE command. This command is very similar to the QUIESCE DATABASE command, with the exception that it does not block write activity during the HOLD phase. The HOLD/RELEASE options can be used to execute a mirror split or snapshot on the database using a certified agent, to create a copy of a database on which transaction logs can be loaded.


UPDATE STATISTICS on a proxy table with a specified column may return error 12814 - "Failed to write information in SYSTABSTATS."


In rare circumstances, after configuring a big data cache or a large stack size, SAP ASE might implicitly shut down following a JavaVM crash while executing a Java query. The message EXCEPTION_ACCESS_VIOLATION or 'ExceptionCode: c0000005' will be reported in the SAP ASE error log.


In rare circumstances, the message "current process infected with 11 (SIGSEGV)" in the module 'ind__get_sysindrow()' together with a stack trace which includes the modules 'getindexname()' and 'CgGenLava::CGConsScanOp()' may be reported in the SAP ASE error log. This may happen when a statement, using temporary user tables or tables created in the same batch or stored procedure and with indexes defined, is being compiled before execution.


In some long running ASE servers, an 8203 error - "Expected to find the descriptor for object < objid > in database < db_num > in < state > state." might be raised with crt_main in the stack trace while creating a temporary table. There will be an information message "INFO: Total Object Ids in temporary database generated: < total id count > , LWPs generated: < LWP id count > " printed for every 100 million object ids generated


On AIX platform, the mapping of addresses to function names in SAP ASE stack traces has been improved. This will provide a superior mapping when the address is in a shared library.


Setting the configuration parameter 'send doneinproc tokens' to zero, can cause the global variable @@rowcount to report an incorrect value inside a stored procedure or trigger.


Supporting Lock Remastering for SAP ASE Cluster Edition. When the master assignment is set to affinity mode, the masters will gradually get re-allocated to the instances that initiates the lock convert requests, if “enable lock remastering” is set to 1(ON) in the configuration file. By default, “enable lock remastering” is set to 0 (OFF). It is not recommended to set “enable lock remastering” to 1 (ON) for badly partitioned cases.


sp_dump_history returns error 17152, version missing or invalid, when dump history file does not exist.


The timing and IO metrics in monCachedStatement for running queries were unchanged until the query completed. Four new columns have been added to provide intermediate updates. The new columns are called TotalLIO, TotalPIO, TotalCPUTime and TotalElapsedTime.


Use of online utilities like 'reorg rebuild with online' might lead to incorrect used/unused counts in the OAM for the table. This is reflected by a later 'dbcc checkalloc' on the table reporting error messages 7949 and 7940.


Update statistics options are 'sticky', meaning previous values which are explicitly set will continue to be used for future update statistics and create index commands on the same table if these options are not specified. These sticky options are: step count (using step values); histogram_tuning_factor; sampling; hashing, partial_hashing, no_hashing. This CR implements a configuration parameter "enable sticky statistics" to control statistics stickiness server wide. The default for "enable sticky statistics" is 1, which matches existing sticky statistics behavior. To turn off sticky statistics, use: sp_configure “enable sticky statistics” , 0


Support a 'WITH RECOMPILE' clause at the statement level.


Improve "ddlgen" performance for generating ddl for schema objects


Print extra information for home location of DOL forwarded rows in DBCC PAGE output.


When REORG REBUILD WITH ONLINE is running in parallel with DMLs, DMLs may fail with a 540 error - "Schema for database object ' < name > ' has changed since compilation of this query. Please re-execute query.".


12308 error with delete or update against table in a query with distinctness e.g. joining to a distinct view or distinct derived table, and exists subquery, a union view or union in a derived table. changes associated with optcriteria cr669847 are enabled by default, but previous behavior (i.e. turn on fix only if optcriteria cr669847 is on) can be obtained by using trace flag 16987


Isolation level 0 queries occasionally fail with errors when REORG REBUILD WITH ONLINE is in progress concurrently on the same table.


DBCC UPGRADE_OBJECT with the "check" option may raise bogus 11031 (Execution of < type > < name > failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate < name > ) errors on every object checked after it encounters an object with an actual error.


The Job Scheduler fails to start if quoted_identifier property is set for the connection (which is used to start the Job Scheduler). The following error is logged in the SAP ASE errorlog: "Job Scheduler: IS_ISQL_EXT failed [set nocount on use sybmgmtdb print ":s: %1!", "sybmgmtdb"]"


The unreserved page count might be off by the number of pages of the table SYSDAMS if SAP ASE uses the OAM pages to calculate the free space counts. The database fragments containing pages of the system table SYSDAMS will show the space used by this table as free.


The function row_count() when used on system tables returns zero after upgrade from SAP ASE 12.5.4


When running optimization goal allrows_dss it is possible that an incorrect aggregate result may be returned in rare circumstances involving a derived table or view containing a union all with the aggregate operating on a constant in the select list on at least one side of the union all.


When running REORG REBUILD against a table whose name or any column name might form part of a reserved double or triple keyword phrase it is possible for an error 156 error to be reported along with error 11934 and for the REORG REBUILD command to abort.


Log the full sql text of the string passed to execute immediate in the monSysSQLText table. This is only available when traceflag 8391 is enabled.


In rare circumstances, when running TRUNCATE TABLE on a very large table, the table does not show up on monProcessObject.


There are missing VA information in some Lava plan operators when using show_cached_plan_in_xml().


Buffer pool wash size increments unexpectedly for user defined caches when remote node is booted


Shutting down an instance may cause a stack trace if I/O fencing is enabled.


Performing decryption of encrypted column data can be much slower for standard users when decrypt default is used.


Error 14613 (The ' < name > ' field in usage anchor has ' < n > ' which does not match with ' < n > from sysusages. Dbid ' < id > '. Lstart ' < n > '.) formats the last 4 parameters incorrectly so the output appears garbled. The field name is correct.


Assertion (ISUSERTABID(objid)) fails in the function xact__getdlm_fromxdes() during upgrade when running diagserver.


LPAD function will left-pad the input string with a specified pad to a supplied number of characters. RPAD function will right-pad the input string with a specified pad to a supplied number of characters.


When using sp_downgrade to downgrade an SAP ASE from version 15.7 or higher to an SAP ASE that is version 15.5 based, the keycnt in sysindexes for index sysattributes.ncsysattributes will become incorrect.


A 702 error, "Memory request for NN bytes exceeds the size of single page of 16384 bytes. ASE is terminating this process", may be reported when using queries with tables that have more than 4192 partitions.


MERGE into statement with columns having decrypt defaults in their ON clause may not produce expected results when the user does not have decrypt permission.


There may be inconsistencies in the values reported between the monProcedureCacheModuleUsage and monProcedureCacheMemoryUsage tables.


When the EQUALS_SCAN_SUPERSET optcriteria hueristic is enabled, it would not apply in the case that the index with no positioning equi-sargs exist (i.e. a full index scan). The heuristics should apply in this case if the more expensive index covers all the equi-sargs of the former index, and includes positioning equi-sargs as well. optcriteria cr748569 will support the enhanced functionality to heuristic optcriteria EQUALS_SCAN_SUPERSET. Related to this enhancement to the EQUALS_SCAN_SUPERSET is optcriteria cr763859


Add support for single instance user databases for the SAP ASE Cluster Edition.


'Invalid pointer value' error messages may occur when a non-database owner accesses the SAP ASE database.


INSERT SELECT does not support LEVEL0 scan. This is a new functionality request, to allow INSERT SELECT to support LEVEL0 scan.


In rare circumstances on a heavily-loaded Server, the message "current process infected with 11" together with a stack trace which includes the module 'mda__tc_scan_mempool' may be reported in the error log when table monTableCompression is accessed.


When using date_diff with smalldatetime and varchar arguments, a bigint may be returned.


If update statistics is used on a table with a large number of partitions (e.g. 1000), then the performance declines significantly, and an inordinate number of log records are created.


DBCC TABLEALLOC needs to scan allocation pages of the database several times, when used like 'DBCC TABLEALLOC(name, full, fix)', it may partially cause the command run a long time. DBCC CHECKALLOC has same performance issue.


If dump history file is manually edited and the first line becomes blank, the file is assumed to be empty and then is initialized.


FR: db shrink warning if not enough space available. Adding this as a part of the checking done by "alter database ... with check_only"




Stored procedures with application context functions take a very long time to execute because SAP ASE accesses system catalogs each time for protection checks.


auto_temptable_stats will automatically generate in-memory statistics on a #temptable column on the first optimizable statement that needs statistics on that column. However, the statistics are not regenerated after a subsequent INSERT/DELETE/UPDATE or TRUNCATE table command. The optcriteria or traceflag 12801 will delete all in-memory statistics on the respective table so that up-to-date statistics will be generated on the next optimizable query referencing the respective #temptable. Note that the ase_current optimization level will not enable this functionality. In order to enable this functionality, explicitly execute "set cr750883 on", or define a user defined optgoal that includes this optcriteria, or enable trace flag 12801 on server startup.


Sometimes a long running transaction can be seen in tempdb for $sort_local which results in tempdb filling up if a large data set needs to be sorted.


DELETE not using row limit optimizations The optimization is enabled by optcriteria.


A 9022 error, “Cannot deliver a command from < connection > . < database > since no transaction is open.” may be reported in the SAP RS error log, when the SAP ASE RepAgent is configured to use the ‘Multi-Path Replication’ feature and while a DML command is rolled back in ASE resulting in the replication stream to fail.


If any online utility is running and HK_GC fails to get DES, it gives rise to an 8233 error (" < name > operation is in progress on the object ' < obj > ' in database ' < dbname > '. Retry your query later."). If traceflag 2792 is ON HK_GC will wait there, which may then cause an undetected deadlock.


A 225 error, "Cannot run query--referenced object (name NAME NOT RECOVERABLE) dropped during query optimization" may be reported when SET ANSINULL statement is used inside a batch containing other statements.


When HADR is enabled, a graceful shutdown of the primary server requires that its state be inactive and the transaction logs be drained unless the new shutdown option 'nowait_hadr' be used.


When the SAP ASE kernel mode is configured as process and an SSL session/connection is abruptly killed/aborted, a SIGSEGV (infected with 11) with a stacktrace may be reported in the SAP ASE errorlog. The functions drop_connection() and ssl_nclose() are likely to be seen as part of the stacktrace.


The ASE COTS JavaVM version is updated to version JRE 7 update 55 for each supported platform in the sybpcidb database.


Error message 3128 "The dump image specified does not contain information for any of the database devices" will be printed when a transaction dump generated by sybdumptran is use with the command LOAD DATABASE ... WITH LISTONLY = CREATE_SQL"


In some rare cases, in SAP ASE Cluster Edition, when one of the nodes goes down and FAILOVER recovery starts on the other node, a deallocated page can be wrongly brought into the cache. An INSERT which is fired after recovery has completed can pick up this deallocated page and insert into it. This may result in 7928 or other index corruption errors reported from DBCC CHECKTABLE.


Forcing an index on one table, where the query has more than 6 table joins and the configuration parameter 'enable deferred parallel' set to ON, can cause an infected with 11 (SIGSEGV) to be reported in the SAP ASE errorlog with a stacktrace involving ResVector::getScalarSum or GtgGroup::GtSecondaryInit


When merge partitions for table with local indexes, if index rebuild on parallel, error message 14108 will be raised.


There is an incorrect assertion that hits with diagserver during rebooting the server if server crashed during online reorg rebuild.


The message "current process infected with 11" in the module 'plc__discard' together with a stack trace which includes the modules 'xact_endupdate' and 'reorg_main' may be reported in the error log during 'REORG REBUILD < table > WITH ONLINE' while this command is executed on a system where high concurrent DML activity is happening on the same table. Alternatively this error can occur during a high concurrent DML activity in a low durability database.


The database level replication status may become inaccurate after changing the replication status of tables or stored procedures while the secondary truncation point is not set.


SAP ASE running on Unix/Linux platforms only prints the top 25 stack frames in a stack overflow stacktrace report which could mask the root cause and also provide insufficient diagnostics when a stack overflow is caused by a recursive function. If the stack overflow backout code uses too much stack, the backout process can cause stack guard word corruption resulting in server shutdown. This CR removes the limitation on number of frames in the stacktrace and if the stack overflow backout code use of the stack reaches within 4K bytes of the stack boundary, it then initiates forcible termination of the task to prevent stack guardword corruption. The default value of 'stack guard size' is increased by 4K bytes to retain earlier level of stack availability. Traceflag 3687 provides a stacktrace when a transaction is aborted due to insufficient stack space that can provide additional diagnostics on stack usage by the query. Traceflag 3686 disables this change. This change is not applicable to the Microsoft Windows platform.


ASE with SSL configured and using CIS may hit SEGV in np__validate_servername() which would bring down the server.


If a stored procedure is compiled in deferred compilation mode and when a compilation error is raised, it could cause stacktrace with SIG 11 and other unexpected error message.


If quoted_identifier is ON and sp_hadr_admin primary is executed, next time HADR primary server reboots as standby, instead of primary.


When an insert trigger exists on the target table of the MERGE statement, the wrong result may happen.


A 331 error, "Query is too complex and has exhausted the name space for Ordering IDs, please breakup query into simpler components.", may be reported during a complex query with multi-tables especially using aggregates and allrows_dss optgoal.


Client connections to SAP ASE may hang when SSL is enabled and the network memory pool is exhausted.


Backup Server on HPUX may die with error messages: A00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 1, error code=0, system message=Pipe I/O returned 0 bytes. D00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=0, system message=Pipe I/O returned 0 bytes while trying to print out a legitimate API error.


The message, "Current process infected with signal 11", followed by a stack trace that includes the modules def_insert() and xls_sessionid() may be reported in the error log when an INSERT query is run in DEFERRED mode.


Under some rare condition, an infected with 11 (SIGSEGV) error in the function querytuning_ins_sysoptions() may be reported in the SAP ASE errorlog.


Performance of concurrent insert is slow.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module mda_fill_and_send_monProcessStatement() may be reported in the error log when running a query of the form SELECT ... INTO temptable.


SAP ASE may enter a CPU intensive loop after a SIGSEGV (infected with 11) at ktMuxThreadTick+0x24d with the following seen in the errorlog: "Returning from kmultimap_iterator_cleanup with lock held" and "Attempting to return from utpApplyAll while holding a multimap read lock (0x < address > ). The lock will be released"


When we try to alter temporary table for the database which has proxy database mapped on secondary companion, we hit error 177: CREATE PROXY_TABLE cannot create a temporary object (with '#' as the first character name.


Partial Index support


For tables with several indexes and TEXT/IMAGE/UNITEXT columns, a 605 error, "An attempt was made to fetch logical page < page id > from cache < cache > . Page belongs to database < db > , object < object > , index < index > , partition < partition > and not to database < db > , object < object > , index < index > , partition < partition > .", may be reported when running 'SELECT...INTO...FROM ... WHERE condition1 or condition2 or ...' command on it with concurrent DELETE/UPDATE/TRUNCATE TABLE commands.


An assertion will occur if encrypted columns is enabled and there are external passwords that need to be recreated.


When using LDAP, an assertion message and a SIGABRT/SIGIOT (infected with 6) stacktrace may be reported in the SAP ASE errorlog. The assertion will say "result == SYBCSI_RESULT_OK, file core/source/csimemory.c". The stacktrace will include the function login__ldapauth().


When RepAgent is configured for Multiple Paths Replication and verbose LTL traces are active through Repagent traces 9201, 9227 and 9228, a SIGSEGV may occur together with a stack trace showing the module ra__sender_ltl_cmds.


When migrate from ase155, Sybmigrate fails at report session and shows error: There are still external logins for the server 'mtrs$999'.


Dynamic SQL with LOB parameter which results in a character set conversion for a single, very, very large text field can raise a 712 error (out of heap memory). Avoidance of the 712 error involves using a workaround that avoids the large text field character set conversion altogether. When the error is invoked by a Java program, instead of by batch mode processing there can be a large memory leak of the heap memory for the connection. That memory leak is addressed by this CR.


The DUMP DATABASE command may hang when run concurrently with a many other tasks if the option 'optimize dump for faster load' is set to a non zero value.


A signal 11 may occur in LeScanOp::LeGetScanInd (called from LeOrScanContext::getNextVtup)when 'streamlined dynamic SQL' is turned on and the query contains ORed joins and one of the outer table's join columns contains a NULL value.


The message "timeslice -501, current process infected" in the module 'ra_ms_get_object_filters_for_path' together with a stack trace which includes the modules 'ra__ms_apply_repfilters' and 'ra_ms_get_object_filters_for_path' may be reported in the error log by the SAP Replication Agent scanner thread for the default path when the filter distribution model is used.


Ocassionally, a heap memory spinlock violation and followed by various stacktraces may happen for session running multiple XML queries with errors.


An ALTER TABLE SPLIT PARTITION command may report a SIGSEGV (infected with 11) in the SAP ASE errorlog if the destination partition name is not specified.


SAP ASE Replication Agent under a multiple path replication setup will not replicate the execution of rs_ticket stored procedure to all paths.


Under extreme OLTP activity in a mixed-log and data database (like tempdb), a task doing CREATE INDEX may report "Stack overflow detected: limit: 0x0x*, guardpage: 0x0x*, sp: 0x0x*" and "*** Stack guardword corrupted" together with a stack trace that includes the modules 'pg__updateoam', 'pg_oamspace', and 'pg_allocoam'.


The error 1120, "Adaptive Server failed to access page < pageno > in database ' < database name > ' because it is not an allocation page." can be raised if the commands DBCC CHECKALLOC or or DBCC TABLEALLOC(syslogs) are executed on an archive database.


HADR deactivation operation with 'force' option kills transactions on non-HADR databases.


When text is bound to a different cache than data for a given table, back-linking text partitions via dbcc shrinkdb_setup() can produce bad links.


When reporting on the dump header of a dump that was taken with a higher SAP ASE version that has used new metadata in the dump, an error 3264, "The dump header contains device information with invalid token length ...", possibly followed by errors such as 3208 “Unexpected end of file while reading beginning of dump...” will be reported. An unknown element warning message will now be reported instead.


The message "Invalid column length: < num > . Value must be between 0 and 255 at offset 0 for 'data-only' row with minimum row length of 70." together with a stack trace including the modules 'collocate' and 'ra__new_schema' may be reported if a row for a replicated table with a name of the maximum length (255 char) created by a user with a name of the maximum length (30 char) is encountered by Replication Agent.


A statement that inserts into a table with an identity column and references a view or derived table that contains a union-all that terminates a union statement may generate a 264 error (duplicate column id) if the identity value is implicitly generated (i.e. - not explicitly provided in the insert's value list).


Error 11203 - "The command ' < cmd > ' is not legal for objects of this type. External definition: < name > " may be incorrectly raised when a proxy table mapped to a file system is part of an update/delete statement.


Wrong suid in sysprocesses when executing stored procedure with execute as owner from another database context.


Duplicate identity values may be generated after loading a transaction log dump containing transactions that inserted identity values reserved using multiple calls to RESERVE_IDENTITY().


Selecting a remote column from DB2 may hit illegal symbol error if the schema name contains special characters.


A 644 error, "Index row entry for data row id ( < pageid > , < rnum > ) is missing from index page < index_pagenum > of index id < indid > of table ' < tablename > ' in database ' < dbname > '. Xactid is ( < xactid > ). Drop and re-create the index." may sometimes be reported in heavily concurrent systems using DATAROWS LOCKED or DATAPAGES LOCKED tables.


A 213 error, "Insert error: column name or number of supplied values does not match table definition." may be reported in a stored procedure, when deferred compilation is active, if a column is added to a table and there is a dependency on "select * " behavior to ignore the extra column. Trace flag 7798 will ignore this error if deferred compilation is turned on and allow normal compilation to process the statement. If normal compilation still sees an inconsistency, or some other activity causes re-resolution of the stored procedure, then errors may be still be reported.


Arithmetic overflow occurred in procedure 'sp_sysmon_kernel'.


When executing a DUMP command with more than one VERIFY option, the backup server will ignore all but the last one. Also, on Windows platform, if the archive is bigger than 4GB and we are executing WITH VERIFY=READ_AFTER_WRITE or VERIFY=CRC and the verification fails when reading a block that is at an offset greater than 4GB, the error message will report an offset value that is only the two lower bytes of the actual offset, for example "There was a failure decompressing < # > bytes at offset 804831240 when processing stripe ' < the stripe name > '" instead of the offset value for 5099798536.


The error message 7786 has been updated to include the server user name.


Reduce dynamic SQL procedure cache footprint when 'streamlined dynamic SQL' is configured by saving SQL text in the statement cache only.


Raise the restriction limit on proxy table queries from 50 tables to 250 tables.


Sometimes, error 7705 could be raised unexpectedly for LIKE predicate with ESCAPE clause if there is a same letter in LIKE and ESCAPE clause, but one is an upper case letter and the other is a lower case letter.


When shared memory size exceeds 1TB, sp_shmdumpconfig might report error 265, "Insufficient result space for explicit conversion of INT value '1382954' to a CHAR field.".


A timeslice error followed by a stacktrace that includes the modules stphd_release_last_mvcc_histogram(), stphd_release_unreferenced_mvcc_histograms() and stu_nosort_range() may be reported in the error log in a heavily loaded system during the CREATE INDEX operation when using hashing.


LIKE optimization does not happen for a ? + ? pattern that is used in a prepared statement.


In rare circumstances, a 1105 message "Can't allocate space for object 'syslogs' in database 'tempdb' because 'logsegment' segment is full" may incorrectly be printed for tempdb when the first pages of tempdb are not mapped in sysusages.


Add 'Proc Cache Header' diagnostic enhancements for the block pool to capture the time spent in bitmap scanning and collect memory allocation/free patterns. These diagnostics are disabled by default.


When displaying configuration values for Replication Agent using the sp_help_rep_agent procedure the 'rs_servername' displays only the first 30 characters.


When a 331 error occurs or there are long query optimization times or large procedure cache usage occurs in the optimization phase, then this may be due to the optimizer not pruning subplans in the search space as early as possible. Improve pruning can be turned on with optcriteria cr757301, or by using ase_current with optimization level of at least ase157sp130. Trace flag 16992 will turn off the optimization even if the optcriteria is enabled.


Cannot use syconfig to do backup server upgrade on Windows 64bit


In some rare scenarios, a utility command modifying a table and waiting for a level 0 scanner on the table to exit, might not respond to a client killing the session where a utility command is executed.


A timeslice error, followed by a stacktrace that includes the module memshrink(), may be reported in the SAP ASE errorlog during a sort operation on a very large data set.


Improve the clarity of error message 16346, "The LOAD_SQL LISTONLY option is valid only if a stripe device is not specified.". This error message will now be reported as, "You cannot use the FROM clause with the LISTONLY=LOAD_SQL option.”


RepAgent may fail with error 9275 "RepAgent ( < dbid > ): Could not locate the before image for the INSERT log record at ( < page# > , < rowid# > )." while processing the log records for a MERGE command leading to inserts and updates.


Deferred Recovery of Create Index Feature.


A 4720 error, "Cannot truncate table < tablename > because there are one or more isolation level 0 scans, or REORG command, active on the table", may be reported during a TRUNCATE TABLE command while level 0 scans are active. This new feature is enabled when the new configuration option 'enable utility lvl 0 scan wait' is set.


When running in SAP ASE process mode under heavy load in a multiengine environment, an engine may become CPU bound when handling network cancel requests arising from attentions received either from the client or from kill commands. In the event that the network listener was on the run queue of the engine which has become CPU bound as above, it may be impossible to establish new logins to the server.


Incorrect hash partition elimination may lead to incorrect results when there is an OR predicate on the partition column(s)


When running on a table with thousands of partitions, create local nonclustered index or placement index command may fail due to stack overflow with no error message printed.


When a user invokes DDLGen from a script and wishes to hide the password by supplying the pseudo password (-Pext) and including the actual password in a file or setting in an environment variable, the error "DG16: Could not get Console instance" is reported.


Support Quoted Identifiers on session temporary tables. This requires that the configuration parameter "quoted identifier enhancements" is set and the session level option "quoted_identifiers" is on.


Error message 806 (Could not find virtual page for logical page ... in database ...) may be reported for an update query with multiple outer joins when the update mode chosen for the query is not deferred update mode.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module s_recompile() may be reported in the error log when a table schema change happens after processing the first row, and before finishing the second row of an dynamic batch INSERT.


Skip blank lines in the dump history file when searching for the version record. If an invalid version record is found, initialize the history file after copying the file to a back up.


A poor index may be chosen for a join, if the selectivity of previous joins is estimated to be 0 rows (likely caused by a predicate selecting an 0.0 weight range cell in the histogram). The optcriteria avoid_zero_weight_histograms or trace flag 16991 will adjust selectivity estimates so that at least one row will be selected when joining histograms. Note that ase_current will not enable this functionality, and that "set avoid_zero_weight_histograms on", a user defined optgoal which includes avoid_zero_weight_histograms or trace flag 16991 is needed.


Creation of temporary tables in a large number of concurrent user sessions leads to a high number of accesses to syslogins.


DDL commands within prepared statements can now be replicated.


When using data encryption functionality on Windows platforms, encryption operations can make an engine stall for short periods of time.


Stored procedures using "execute as caller" with queries that create and query #temporary tables fail with error 208, "Server ' < servername > ', Line 26: < #temporary_table > not found after LOAD DATABASE".


An incorrect decision by optimizer to do the update in direct mode might result in consecutively repeated update of the same row and resulting in page corruption, manifesting in the errors 806, 614, 120024, etc.


When a process that is executing a DUMP DATABASE command is killed either using the KILL command or using CTRL-C or the SQL session goes away, the Backup Server will not release its associated resources until it finishes copying the whole database. One of the consequences is that the archive devices can remain locked for a long time because the sybmultbuf processes stay alive.


In rare circumstances, when the MDA table monProcessProcedures is being used, an infected with 11 (SIGSEGV) error along with a stacktrace may be logged in the SAP ASE errorlog . This is a similar situation as addressed by CR 754648 (which covered monProcessStatement).


A SIGSEGV (infected with 11) can be logged in the SAP ASE errorlog on the Windows platform if the loginfo() built-in is called with three parameters and for whatever reason the built-in returns an error.


Support online parallel create index.


When UPDATE STATISTICS is performed on a character column with a non-binary character set, and in addition UPDATE STATISTICS uses the consumers phrase, then there is the possibility of many small weight frequency cells following a zero weight range cell. This may cause poor query plan selection if a predicate selects a zero weight histogram cell. Optcriteria cr759142 will avoid generation of small frequency cells following a zero weight range cell, when the consumers phrase is used in UPDATE STATISTICS to generate stats on a mostly unique non-binary character set column.


A poor query plan might be selected when parallel UPDATE STATISTICS (for instance using the consumers phrase) is used to gather statistics. After installing SAP ASE with the fix for this issue, update statistics will need to be run on affected tables.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module sendtext() may be reported in the error log when a MERGE JOIN is being used and if the inner table has in-row LOB columns with NULL values.


If there are equality predicates or joins which are used for index keys, then occasionally an index which has few positioning keys specified than another index will be chosen. If 2 indexes have only equality predicates or equality joins used for keys, then a heuristic is added to choose the index with more limiting keys if those keys cover all the limiting and filtering keys of another index. The optcriteria EQUALS_SCAN_SUPERSET and trace flag 16989 will apply the heuristic to index scan which are not the inner of a nested loop join. The optcriteria EQUALS_NLJOIN_SCAN_SUPERSET and trace flag 16990 will apply the heuristics to all index scans. Note that the optcriteria are not turned on by any optgoal, and a SET command, user defined optgoal, or trace flag is needed to enable the heuristic.


In very rare situations, SAP ASE may panic and shutdown if sp_sysmon is being run and a connection disconnects at the same time.


On Windows platform, SAP ASE may open an arbitrary listener port during MS DTC service initialization for distributed transaction management.


Allow the command LOAD WITH VERIFYONLY to be executed using less stripes than the number used at DUMP time.


Support creation of a global index in parallel for a partitioned table that has one or more empty partitions. Previously, when creating a global index on partition table, if there were any empty partitions, then the index would be created in serial.


On ASE Cluster Edition insert jobs may unexpectedly continue to run with no new rows inserted into the target table. There are NO lost inserts but, dbcc checkalloc or tablealloc may report Msg 2546 or we may encounter deadlocks which can be seen in the error log.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module LeScanOp::_LeOpNext() may be reported in the error log when an online utility (e.g. REORG REBUILD) is in progress on a table that contains forwarded rows.


Arithmetic overflow may occur when executing procedure sp_sysmon_locks.


When 'net password encryption reqd' set to 1, charset/langinstall will run into 1640 (Adaptive Server requires encryption of the login password on the network) and 4002 (Login failed) errors.


CREATE TABLE commands may not perform well in situations where a lot of CREATE TABLE commands are run in parallel and the SAP ASE configuration has 'enable inline default sharing' set.


Traceflag 3605 gets left on after error 707 state 11 is hit, resulting in a wide variety of diagnostic information being written to the errorlog, in turn causing the errorlog to grow rapidly.


If a trigger for a DML query has certain commands that execute immediate are not allowed, such as begin tran, rollback trans, etc, error 11736 and 11031 could be raised for the first post-upgrade using execute immediate for the DML query.


When LOAD DATABASE ... WITH LISTONLY = 'CREATE_SQL' is used with the new functionality to create DDL for a differently named target database, the target database name is not reflected in the sp_dboption statements.


DBCC CHECKTABLE may encounter a 2511 error, "Keys of index ID < id > for table < tablename > in leaf page are not in the correct order. Drop and re-create the index (index page < pageno > , partition ID < partition_id > )", if 'enable functionality group' is enabled and the base table lockscheme is DOL and changing the table's lockscheme from DOL to APL as part of AMC.


On ASE Cluster Edition insert jobs may unexpectedly continue to run with no new rows inserted to the target table. Dbcc checkalloc or tablealloc may report Msg 2546.


The 6918 error, "The SYSDAMS page that stores the state of page # in database ' < dbname > ' could not be found. The option 'allow incremental dumps' will be disabled because SAP ASE cannot continue recording page modifications", can be raised if the table SYSDAMS gets the very first extent of an allocation unit allocated.


Optcriteria equals_scan_superset and avoid_zero_weight_histograms are associated with the ase157sp130 optimization level. Previously, a user defined optgoal needed to be defined to enable these optcriteria (or trace flags 16989 and 16991 respectively).


The index ID is incorrectly reported as 0 in the SAP ASE error message number 12301, "Internal error: the index (id = < ID > ) and the data for row ( < page > , < row > ) in table ' < table > ', database < db > are inconsistent; data is marked deleted but index is not. Aborting the transaction".


Under some circumstances, a worker thread may hang due to incorrect error handling during parallel CREATE INDEX with "utility statistics hashing" turned on.


In rare circumstances, a time slice error followed by a stack trace that includes the modules ups_end_statglobalnosort() and close_table() may be reported in the error log when running UPDATE INDEX STATISTICS.


Isolation level 0 queries fail with errors when CREATE CLUSTERED INDEX WITH ONLINE is in progress concurrently on the same table.


A DUMP WITH COMPRESSION could fail with the message "SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 9, error code=0, system message=Pipe I/O returned 0 bytes". If a core file is produced the stack will show the module sm__do_allocations().


Wrong result could happen when an EQUIJOIN on a single INT4 column is placing a bloom filter probe into the scan and the scan is at the inner side of another NESTED LOOP JOIN with a pushdown EQUIJOIN sarg on the same column.


SAP ASE fails to boot on Windows with the message "FATAL: shared memory region is being held at xxx bytes but yyy bytes are required" being reported in the SAP ASE errorlog.


On a server that has a large number of objects, the sp_sysmon report may take a long time to complete and error message 1508, "Create index aborted on duplicate rows. Primary key is < keyname > ", may be reported in the error log.


The procedure cache allocation is optimised. This vastly speeds up the start-up of SAP ASE configured with a very large procedure cache.


A 3478 error, "During undo the page timestamp value is less than new timestamp from log." or other fatal errors may be reported in the error log when SAP ASE is rolling back a transaction following an 863 error, "Buffer resources in cache < cache_name > are unavailable. Please re-run this query or ask the system administrator to re-configure buffer cache memory." that is accompanied with messages "Named cache < cache_name, cache_id > is configured too small for current demands".


If the data cache is configured small, SAP ASE may report a 'cache too small' error when the new sort buffer algorithm is used.


A 707 error, "System error detected during attempt to free memory at address < addr > . Please consult the ASE error log for more details", may be raised by SAP ASE when multiple SAP ASE connections are executing parallel CREATE INDEX commands.


In rare circumstances, after using the configuration option 'global cache partition number', the dataserver may hang. If the diagserver was being used then an Assertion (! "locks not cleaned") will be reported in the SAP ASE errorlog.


sp_sysmon and monEngine do not report DiskIOChecks in process mode.


Deprecate plan sharing feature.


A 6908 error, "During redo the page timestamp value is less than old timestamp from log. etc." followed by a stack trace that includes the module 'recovery' could be raised when loading a database dump if the configuration parameter 'optimize dump for faster load' is enabled and there is very high update activity in SAP ASE while the dump database command is running. To workaround the problem the end-user can set the trace flag 3022 (either via the command line or by using dbcc traceon or by using SET SWITCH ON ignore_trailer_ckpt) before loading the database.


Under rare conditions, a 12301 error, "Internal error: the index (id = < num > ) and the data for row ( < page# > , < row# > ) in table < table_name > , database < dbnum > are inconsistent; data is marked deleted but index is not. Aborting the transaction", may be reported during an isolation level 0 scan.


When using sql replication and nested builtins with a column reference, an incorrect sql statement may be generated instead of defaulting to row replication.


DML on tables with Encrypted Columns are significantly slower than SP50.


For SAP ASE Cluster Edition, when table creation is in progress, the checkpoint process may hit an infected with 11 (SIGSEGV) in the module 'ocm_hold()' and report a stacktrace in the SAP ASE errorlog that includes the modules 'des_has_onlutl_active()' and 'cm_writedes()'.


When there are several scans on the same index and some of the scans hit the same index page needed to be shrunk concurrently, the index page may be shrunk twice. The second attempt will fail and a 2630 error, "In database < db > , page < page#2 > is linked backward to page < page#1 > , but that page is linked forward to page < page#3 > . Please report this internal error to SAP Technical Support". Although a 2630 error is raised, the index is not corrupted.


When execute command ALTER TABLE ... SPLIT PARTITION ..., use of parallel sort and table's partition number > 1, it will encounter an Error 675: "Invalid Buffer Cache Access: Attempt to locate page < page > , database < dbid > in cache failed because no object id was specified. scan_context={objid < objid > , indid < indid > , cid < cid > }. Contact Technical Support for Assistance."


The message, "Current process infected with signal 10 (SIGBUS)", followed by a stack trace that includes the modules 'loginfo_builtin' and 'exec_lava' may be reported in the error log when the builtin loginfo(' < dbname > ','oldest_active_transaction_date') is executed.


UPDATE STATISTICS WITH SAMPLING may report error 614: "Adaptive Server accessed a row that has an illegal length of < n > while in data base ' < db > ." or error 806: "Could not find virtual page for logical page < n > in database ' < db > ', while concurrent DML is going on the same object.


A 7786 error, "Unable to turn role off since user is not a valid user in the current database", may be reported incorrectly when executing the SET ROLE OFF command.


Some of the cache buffers used for sort are not claimed and unclaimed correctly. This can lead to a performance impact if cache swap occurs.


LOAD DATABASE WITH LISTONLY=LOAD_SQL with UNTIL_TIME after a tran dump and before a database dump generates incorrect load SQL.


The optcriteria EQUALS_SCAN_SUPERSET and EQUALS_NLJOIN_SCAN_SUPERSET have had the comments changed so that the respective optcriteria names shows up in the sysoptions output.


Bulk insert to proxy tables mapped to DirectConnect for Oracle was disabled in ASE 15.0.


[Feature request] Provide a means for ASE to detect and report whether a database has been put in PREPARE state. This request is addressed by a new builtin is_prepared( < dbid > ).


New Feature: Bucket Pool memory manager to enable ASE scale over large CPU core configuration.


BCP in to a table with encrypted columns is much slower with the change from the use of the Certicom libraries.


DBCC CHECKTABLE may report a 605 error, "An attempt was made to fetch logical page < pageno > from cache < name > . Page belongs to < info1 > and not to < info2 > " may be reported after creating an index with online option.


The message, "Current process infected with signal 11", followed by a stack trace that includes the module SearchEngine::_SeFindOptimal may be reported in the error log after a lengthy optimization, most likely after an aggregate with a GROUP BY in which the GROUP BY columns originate from multiple tables.


When ansinull is off, incorrect NULL value row could be returned when an equi-join under OR predicate are on two columns with NULL values and the final plan is using a special OR strategy plan for the OR predicate. An example of such OR predicate is "t1.col1 IN (1,2,t2.col2)".


When granular permissions is enabled and the user who has "own database" permission has executed setuser " < another_user > ", the user is not able to select from < another_user > .table.


When a dynamic batch insert is executed, an "infected with 11" (SIGSEGV) stacktrace may be reported in the SAP ASE errorlog. The stack trace will reference the functions tdsrecv__process_batchparam() and tdsrecv_dynamic().


Under a rare condition, the fix for CR 750937 could cause a performance regression. The fix for 750937 is now only enabled under traceflag 219.


The version of OpenSSL used has been upgraded to OpenSSL 1.0.1g


The expression -(minimum integer value) does not raise an error.


When a non-language batch query (e.g. 'if @@transtate = 3 select 3 else select 0') is followed a language batch query which triggers an error (e.g. a query causing parsing error), an "infected with 11" (SIGSEGV) stacktrace to be reported in the SAP ASE errorlog. The stack trace will reference the functions batchparam_save_SQL() and memalloc().


When INSERT INTO SELECT at LEVEL 0 is enabled, SELECT INTO does not wait for locked rows so may return wrong results.


sp_showoptstats will have poor performance if a large number of partitions are defined and/or a large number of columns have histograms defined.


DDLGen terminates when the config option 'quoted identifier enhancements' is off.


When permission on built-in function is granted to a role which is granted to a user, then executing the built-in function may result in permission error.


Create login command does not pass the login name to sp_extrapwdchecks.


For tables with LOB columns and attribute "dealloc_first_txtpg" set to 1, error 7133 "NULL textptr passed to %s function." will be reported when WRITETEXT command is running with the new text pointer after the LOB column is updated to NULL.


Sybmigrate space estimation report fails with error 291 state 1 "Access to sysdams is disallowed".


Using a NOT LIKE clause to compare with a local variable assigned to a constant string could return different results than comparing to the constant string directly if the column has NULL values in it.


For the diagserver on Solaris platforms, if SAP ASE is running in threaded kernel mode, setting the congiguration option "number of disk tasks" to any value greater than 1, will result in an assertion failure being reported in the SAP ASE errorlog.


In rare circumstances, error message "WARNING - Fatal Error 614 occurred at ... Adaptive Server accessed a row that has an illegal length ..." may be raised if there is "ORDER BY" clause in a query that uses an in-memory temp database.


A 6908 error, "During redo the page timestamp value is less than old timestamp from log. Page .. object id = 99, page timestamp=0000 00000000. Log old timestamp=0000 00000001." may be reported during load tran in a database that has been altered with the "async_init" option.


If many queries that use an "ORDER BY" clause are executed concurrently and the "default data cache" is configured to use a large value for the "local cache partition number" parameter, then SAP ASE may run very slowly or even appear to hang.


A 2510 error, "Key mismatch between index page < value > , partition ID < value > ;... Drop and re-create index ID < value > of table ' < value > ' in database ' < value > '." followed by the message "current process infected with 11" in the module 'byte_eq' together with a stack trace which includes the modules 'compress_page' and 's_xoltp_dml' may be reported in the error log when an INSERT is executed and while the configuration option "streamlined dynamic SQL" is active. Additionally a 631 error will be reported while SAP ASE is rolling back the current transaction.


If an upgrade from a SAP ASE server with a version lower than 15.7 SP100 fails to create the table SYSDAMS because it ran out of space, executing ALTER DATABASE to extend the space will fail with the 12324 error, "In database < dbname > , the server failed to open required table 'SYSDAMS'".


Update statistics on proxy table mapped to Oracle using DCO may stacktrace at stat_sargden_accumulate if the proxy table contains NULLs.


Conversion to a text or image column containing nulls in a stored procedure may cause seemingly random stacktraces (infected with 11/SIGSEGV) to be reported in the SAP ASE errorlog.


When a RID is used to scan a table and the table has defaults that are not materialized, wrong results may be returned.


The EQUALS_SCAN_SUPERSET optcriteria hueristic rule is applied to prefer an index with more limiting equi-sarg keys specified over another index with fewer limiting keys, given that the index limiting equi-sargs keys is a superset of the latter index, and that it is also a superset all the limiting sargs and filtering sargs the latter index. However, if an enforcer such as a SORT or XCHG is applied, the index with fewer limiting equi-sarg keys may still be chosen. Optcriteria cr763859 will use the rule hueristic, but it will only apply if optcriteria EQUALS_SCAN_SUPERSET is also enabled.


The "Alter thread pool" command may cause an infected with 11 (SIGSEGV) along with a stacktrace that references the function rvm_dispatch() to be reported in the SAP ASE errorlog.


In rare circumstances, the message "current process infected with 11" (SIGSEGV) in the module 'dpdb__dflpurge' together with a stack trace may be reported in the error log followed by the message "Spinlocks held by kpid ... Resource- > rdbt_ext_spin" resulting in SAP ASE shutting down implicitly during the execution of a DUMP DATABASE command and while the configuration option "optimize dump for faster load" is set to 1.


Under some rare condition, error msg 605 could occur when try to delete a row from a table which has IN ROW LOB if compatibility mode is on.


A 692 error, "Uninitialized logical page ' < value > ' was read while accessing database 'value', object '' (99), index ' < Unknown > ' (0), partition ' < Unknown > ' (99)." may be reported during the execution of either ALTER or CREATE DATABASE command when the "FOR LOAD" option is used and while the database is larger than 64 GB. This may be followed by the message "current process infected with 11" in the module 'buf_cleanup_write_queue' together with a stack trace in the SAP ASE error log which includes the modules 'terminate_process' and 'quitfn'.


Backup Server may log false page verification errors with a message "Incorrect column type in the offset table of row x in page xxx of object ID xxxxxxxx." when executing dump database command with verify = full on a database with 'allow wide dol rows' turned on.


When performing a dictionary decompress for varchar column with character encoding, SAP ASE may report a 9829 error - " Compressed data row < rowid > in objid < objid > , dbid < dbid > is corrupted."


Under an HADR environment the current task may hang forever in the log drain phase of the deactivation process if the SAP ASE Replication Agent is unable to connect to the SAP Replication Server during the execution of 'sp_hadr_admin deactivate'.


When the advanced_aggregation optcriteria is used (typically this occurs when the optimization goal is allrows_dss), then there is a possibility of a wrong answer when a SUM, or AVG aggregate is used on an exact numeric datatype column.


The message text for error 3543 is enhanced to include the database id value such as "One or more entries in the data segment free space counts in database ID %d was found to be negative and has been set to 0."


The errors 'Object id wrong' or 'Page mismatch' can be mistakenly reported by DUMP WITH VERIFY if the system is very busy while the database dump is in progress.


Error message 15746 is modified and made generic as "Unable to run this command on the archive database '%S_DBID' because it is not supported."


sp_hadr_admin failover_timeestimate reports high value for estimated failover time.


Select negative number from tinyint column does not return 'Arithmetic overflow" error.


If auditing is enabled & stack overflow is detected, server gets SIGNAL 11 (SIGSEGV) in chk_usr_role_audit(). As a consequence, normal shutdown hangs, but 'shutdown with nowait' works.


In rare circumstances, a 3474 error, "During redo the page timestamp value is less than old timestamp from log. Page #= < pg > , page timestamp= < ts > . Log old timestamp= < ts2 > ." may be reported during recovery when an ALTER TABLE or REORG REBUILD command was running at the time SAP Adaptive Server was shutdown with nowait or was abnormally stopped.


When BULK-INSERT optimization is used for INSERT INTO ... SELECT ... statement, and when there is an exception occurs (in this case, a landing partition for a row is not found causing exception), the table will be closed by the exception handler and hence the corresponding internal table descriptor structure is also closed before the CLOSE phase. Hence, further dereferencing the internal table descriptor structure causing SEGV. This was handled before by appropriately freeing all the memory and bail-out in the CLOSE phase however, there are few bits that needed to be cleared were not cleared properly. Not clearing these bits was causing the issue described in CR# 763514.


A 3223 error, "Attempt to read a dump trailer failed; returned error code is 2.", will be reported when trying to load a database dump into a pre-15.7 SP121 SAP ASE release, if the dump was taken either with 15.7 SP121 or 15.7 SP122 SAP ASE releases and the option 'optimize dump for faster load' was enabled when the dump was taken.


In SAP ASE Cluster Edition, duplicate identity values may be generated in column that was created with the IDENTITY() built in function.


The message "Current process infected with signal 11" together with a stack trace containing the module 'ups_stat_memalloc' may be reported in the error log while running update index statistics with hashing.


Under a heavily loaded Java application environment, the messages 'PCI(M1): ERROR: JNI_CreateJavaVM; failed attaching to the JVM for AttachCurrentThread() with -1' and 'PCI(M1): ERROR: JNI_CreateJavaVM; PCA/VM FAILED; general failure' may be reported in the SAP Adaptive Server error log. These messages usually indicate that the JavaVM heap space is exhausted. In order to solve this problem the SAP Adaptive Server needs be restarted.


In rare circumstances a DUMP or LOAD command could fail on a Windows platform with the error message in the backup server errorlog 'Error in acknowledging command '152' to the archive emulator'.


Under an HADR environment on the AIX platform, a user connection (not having 'allow hadr login' privilege) to the ASE in standby mode is not redirected to the primary ASE, and the user login fails.


The indexes created internally for the replication of text/image columns are system objects and they cannot be renamed by executing the system stored procedure sp_rename.


An attempt to connect to the Backup Server could fail with the error 'The host ' < IP address > ' is not authorized to connect to this Backup Server.' reported in the SAP backup server error log if the SAP backup server is booted using a virtual address and the 'hosts.allow' file doesn't contain an entry for the actual real address.


Using the statement cache, literal auto parameterization, views and instead triggers all together may result in the wrong length for text columns after the column is updated with an instead of trigger being executed.


On Solaris platforms, a 940 error "Dbtable in wrong state for operation: DBTABLE pointer = < address > , dbid = < value > ..." together with a stack trace may be reported in the error log if 'list_dump_fs' or 'get_dump_fs' attribute is queried using function db_attr() or sp_downgrade_esd is executed.


On the Solaris platform, when a user has created a user message and the login account of this user is dropped, then an infected with 10/SIGBUS stacktrace may be logged in the SAP errorlog.


Under a heavily loaded Java application environment, the messages 'PCI(M1): ERROR: JNI_CreateJavaVM; failed attaching to the JVM for AttachCurrentThread() with -1' and 'PCI(M1): ERROR: JNI_CreateJavaVM; PCA/VM FAILED; general failure' may be reported in the SAP Adaptive Server error log. These messages usually indicate that the JavaVM heap space is exhausted. In order to solve this problem the SAP Adaptive Server needs be restarted.


When a MERGE statement is run on a table that has an insert and an update trigger defined, the implicit execution of the triggers may cause wrong results on the target table of the insert trigger.


In rare circumstances, the message "current process infected with 11" in the module 'th_accounting' together with a stack trace which includes the modules 'pg_th_reserve' and 'pg_allocate_syslogs' may be reported in the error log, if an ALTER DATABASE command is executed to extend the database size and a high level of concurrent activity is taking place in the database. This may result in the SAP Adaptive Server shutting down implicitly.


Resolve issues revealed by Coverity for RAT code.


Update sqlloc to support new sort order 'binaryalt'



  • 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 ; SAP Adaptive Server Enterprise 15.7 Cluster Edition


CR, ASE 15.7 SP130, ASE 15.7, SP130, Adaptive, Server, Enterprise, Fix, Patch, Error, Bug, , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , Problem

About this page

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

Search for additional results

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