远程Sybase数据库技术支持,联系手机:13811580958,QQ:289965371!

 

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!

如有问题,请联系我!

QQ :289965371 点击这里给我发消息
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:735923
CR Number:   735923
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1492 28 Mar 2013 Fixed
12.0.1 3876 28 Mar 2013 Fixed
Description
Calling SAConnection.Open would have thrown an exception when attempting to open the 'utility_db'.



CR:735992
CR Number:   735992
Product Name:   SQL Anywhere
Product Component:   OData Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1493 01 Apr 2013 Fixed
Description
When computing the Multiplicity of an Association, the OData Producer was not taking unique indexes into account. For example, the tables T8 and T8b are functionally identical but generate different multiplicity:



CREATE TABLE T8 (

pk1 INTEGER NOT NULL,

c1 INTEGER,

PRIMARY KEY (pk1),

FOREIGN KEY F_KEY_T8 (c1) REFERENCES T7 MATCH UNIQUE SIMPLE );



CREATE TABLE T8b (

pk1 INTEGER NOT NULL,

c1 INTEGER NULL,

PRIMARY KEY (pk1));



CREATE UNIQUE INDEX T8bIndex on T8b(c1);



ALTER TABLE T8b ADD CONSTRAINT

F_KEY_T8b FOREIGN KEY (c1)

REFERENCES T7 (pk1)



Results in



<Association Name="F_KEY_T8">

<End Role="T8_Dependent" Type="SAPSybaseOData.T8" Multiplicity="0..1"/>

<End Role="T7_Principal" Type="SAPSybaseOData.T7" Multiplicity="0..1"/>

</Association>



<Association Name="F_KEY_T8b">

<End Role="T8b_Dependent" Type="SAPSybaseOData.T8b" Multiplicity="*"/>

<End Role="T7_Principal" Type="SAPSybaseOData.T7" Multiplicity="0..1"/>

</Association>



This has been fixed. Table T8b above now returns associations identical to those of table T8.



CR:735993
CR Number:   735993
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1493 01 Apr 2013 Fixed
Description
The test window of the MobiLink Plug-in was not modal. This has been corrected.



CR:735998
CR Number:   735998
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1493 28 Mar 2013 Fixed
12.0.1 3877 28 Mar 2013 Fixed
Description
The Relay Server Outbound Enabler may have restarted unnecessarily in rare situation, resulting in repeated RSE3003 error for a duration as long as the OE-RS liveness timeout period. One example situation would have been when a Relay Server was removed from the farm and then being added back after. This has been fixed.



CR:736004
CR Number:   736004
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1585 05 Jul 2013 Fixed
12.0.1 3931 05 Jul 2013 Fixed
Description
Some window functions, including MIN and MAX, could have given incorrect results if called over a column with data type TIMESTAMP WITH TIME ZONE. This has been fixed.



CR:736024
CR Number:   736024
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3877 01 Apr 2013 Fixed
Description
The renew_overlapped_cookie property was introduced for the Relay Server to work with clients without cookie isolation support. The default value of renew_overlapped_cookie in version 16.0.0 was set to 'yes' for maximum compatibility. The same feature was added to version 12.0.1, however the default value was 'no'. The 12.0.1 decision has been revised and this feature is now on by default in 12.0.1 as well.



CR:736044
CR Number:   736044
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1498 01 Apr 2013 Fixed
12.0.1 3879 01 Apr 2013 Fixed
Description
The MobiLink server may have crashed when the MobiLink client connects via HTTPS via a proxy. Although the likelihood of the crash was extremely low, it has been corrected.



CR:736239
CR Number:   736239
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1529 02 May 2013 Fixed
12.0.1 3895 02 May 2013 Fixed
Description
When the MobiLink client held on to old affinity information across Outbound Enabler restarts, and used it on new requests, the Outbound Enabler would have failed the relay (reported as OEE1051 error on version 16). The Outbound Enabler has been fixed to allow the traffic to go through instead.



CR:736249
CR Number:   736249
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1497 01 Apr 2013 Fixed
Description
Numeric and Decimal columns and parameters are transferred to and from the client in packed-decimal format when the column or parameter is bound as SQL_NUMERIC (SQL_C_NUMERIC). APIs like ODBC, OLE DB, and JDBC must convert between the packed-decimal number and a 128-bit binary number for these cases. Improvements have been made to the conversion routines for Windows 64-bit platforms.

Conversions from packed-decimal to 128-bit binary for numbers in the range 10^20 to 10^38 are now approximately 67 times faster.

Conversions from 128-bit binary to packed-decimal for numbers in the range 10^20 to 10^38 are now approximately 2.7 times faster.



CR:736255
CR Number:   736255
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3895 01 May 2013 Fixed
Description
A SQLE_COLUMN_NOT_STREAMABLE error would be erroneously reported when importing in the Interactive SQL utlity. This has been fixed.



CR:736264
CR Number:   736264
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1490 02 Apr 2013 Fixed
Description
A number of improvements and bug fixes have been made to the SQL Anywhere OLE DB provider.

1 - When a column cannot be fetched in its entirety, the status is now set to DBSTATUS_S_TRUNCATED instead of DBSTATUS_S_OK, and length to actual length, not amount fetched.

2 - IRowsetUpdate methods InsertRow/Update now inserts rows in manual commit mode (i.e., commit in batches), rather than autocommit each row.

3 - Improved support for DBTYPE_DBTIME2/DBTYPE_DBTIMESTAMPOFFSET data types.

4 - In order to identify columns that are DEFAULT AUTOINCREMENT, IColumnsInfo::GetColumnInfo now sets the DBCOLUMNFLAGS_ISROWVER bit for those columns. Microsoft defines a column with this attribute as a non-writable versioning column (such as the SQL Server TIMESTAMP) which suits SQL Server. Note, however, that SQL Anywhere supports versioning columns that are writable.

5 - Corrected failure to describe money/smallmoney as DBTYPE_CY (currency type). Also corrected OLE DB schema queries DBSCHEMA_COLUMNS, DBSCHEMA_PROCEDURE_COLUMNS, and DBSCHEMA_PROCEDURE_PARAMETERS results for DBTYPE_CY.

6 - Corrections were made to the schema rowset information (DBSCHEMA_COLUMNS, DBSCHEMA_PROCEDURE_COLUMNS, and DBSCHEMA_PROCEDURE_PARAMETERS) for datetime/time precision and scale.

7 - Corrections were made to 搑un-time information for datetime/time precision and scale.

8 - Added "DATETIME" to the list of DBPARAMBINDINFO.pwszDataSourceType types for SetParameterInfo (SQL Server uses this undocumented type name). Type names are usually of the form 揇BTYPE_xxx (for example, 揇BTYPE_I4, 揇BTYPE_STR, 揇BTYPE_DBTIMESTAMP).

9 - Adjusted GetConversionSize values for TIME, DATETIME, DATETIMEOFFSET data types (only 6 fractional digits are supported by SQL Anywhere).

10 - A memory leak caused by failure to free rows whose refcount is 0 in Update() was fixed.

11- A possible memory corruption in calls to IRowsetChange::SetData, IRowsetChange::InsertRow, ISequentialStream::Write, and IRowChange::SetColumns was fixed.

12 - A performance problem when DataConvert was used when no conversion is required was fixed.

13 - A performance issue with SQL_NUMERIC columns, with values comprised of 19 to 37 decimal digits, was fixed.



CR:736356
CR Number:   736356
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1498 03 Apr 2013 Fixed
12.0.1 3879 03 Apr 2013 Fixed
Description
Sybase Central could have crashed after changing the definition of a view or materialized view. This has been fixed.



CR:736526
CR Number:   736526
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1501 25 Apr 2013 Fixed
Description
Under very rare conditions, reading indexes containing compressed data could have lead to a server crash with an 慽nvalid memory read error. This has been fixed.



CR:736527
CR Number:   736527
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 04 Apr 2013 Fixed
Description
The OLE DB provider accepts two cbBookmark values, one which is the 搒hort DBBMK_FIRST/LAST value, and another with the value "4" or "8" depending on the bitness of the provider. The 64-bit provider was flagging "4" was an illegal value for cbBookmark, and the 32-bit provider flagged "8" was an illegal value for cbBookmark. The OLE DB provider should have accepted both values as the length of a bookmark value and fetched the appropriate 32-bit/64-bit bookmark value from memory. This problem affected IRowsetLocate::GetRowsAt, IRowsetLocate::Compare, IRowsetLocate::GetRowsByBookmark, IRowsetLocate::Hash, and IRowsetScroll::GetApproximatePosition, and IRowsetExactScroll::GetExactPosition. It has now been fixed so that both 32-bit and 64-bit providers now support 4-byte and 8-byte bookmark values, in addition to 1-byte values.



CR:736544
CR Number:   736544
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
When creating or altering a table, CHECK constraints were allowed that were not valid. These failed when evaluating the CHECK at execution time.

- in TABLE checks, unknown column/variable names were permitted if they started with '@'

- aggregate and window functions were permitted

- ROWID() and NUMBER() were permitted

- host variable references were permitted

This has been fixed. These now give appropriate errors when the CHECK is created.



CR:736546
CR Number:   736546
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
The LIKE predicate allows an optional ESCAPE argument which must be a single character. In some cases where the string and pattern could be optimized, an error was not returned for ESCAPE arguments that did not consist of a single character.



For example:

select if 'abc' like 'abc' escape '99' then 1 else 0 endif



should have failed with an error, but did not. This has been fixed.



CR:736547
CR Number:   736547
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1504 09 Apr 2013 Fixed
12.0.1 3882 09 Apr 2013 Fixed
11.0.1 2969 09 Apr 2013 Fixed
Description
Under rare circumstances, evaluation of a query with complex expressions could have caused a server crash. This has been fixed.



CR:736562
CR Number:   736562
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
When combining values, where one was an array and the other was a NULL literal value, it was possible for the result to fail with an unexpected error.



For example:

create or replace variable var_strarray array(3) of long varchar;

select cardinality( coalesce( var_strarray, null ) );



would have failed with the error:

Could not execute statement.

Expression is not an array

SQLCODE=-1666,



This has been fixed.



CR:736570
CR Number:   736570
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1505 05 Apr 2013 Fixed
Description
Statements that included invalid Transact-SQL outer join predicates, did not give appropriate errors.



For example, the following gave an 搃nvalid expression error:

select count(*) c

having c *= 0



This has been fixed.



CR:736571
CR Number:   736571
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
Certain SQL constructs containing selectivity estimates could have caused the server to crash. This has been fixed.



CR:736572
CR Number:   736572
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
When converting a value of Row type with a field of Array type, an inappropriate error may have been given.



For example:

create or replace variable var_row row(col_intarray array(3) of int);

set var_row = var_row;

set var_row = var_row;



The second SET statement would have returned the error:

Expression is not an array

SQLCODE=-1666, ODBC 3 State="HY000"



This has been fixed.



CR:736573
CR Number:   736573
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
When executing statements that included invalid uses of the NUMBER function, the statement could have failed with a non-fatal assertion failure.



For example:

select COUNT( DISTINCT NUMBER(*) )

from sys.dummy



would have failed with the following error:

*** ERROR *** Assertion failed: 106103 (16.0.0.1320)[asatest] NUMBER(*) is not associated



This has been fixed so that an appropriate error is now returned.



CR:736574
CR Number:   736574
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
When using a statement that contained a ROWID() expression in a search condition, it was possible for the statement to fail with a nonfatal assertion failure.



For example:

select first 1

from T_Exprs

where col_str >= CAST( ROWID(T_Exprs) AS LONG VARCHAR )

order by 'a'



would have failed with the following errort:

Could not execute statement.

Run time SQL error -- *** ERROR *** Assertion failed: 106105

Unexpected expression type dfe_FieldRID while compiling



This has been fixed.



CR:736575
CR Number:   736575
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 05 Apr 2013 Fixed
Description
In some cases, a statement that contained a dotted reference was misinterpreted with the dotted reference interpreted as a row access.



For example:

select (dt.ci).nosuchcolumn

from (

select cast(row(25 as val1,27) as row(val1 int, ci int)) ci

) dt



would have incorrectly returned DT.ci.ci instead of an error. This has now been fixed.



CR:736680
CR Number:   736680
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1508 12 Apr 2013 Fixed
12.0.1 3884 12 Apr 2013 Fixed
Description
It was possible for a mirror server to have hung for a few seconds or indefinitely, have had connection timeouts, failed, or have had poor performance. It was more likely to see these problems when running multiple mirrored databases on a single server that had automatic multiprogramming level enabled (the default) and there were nearly as many mirrored databases as cores.



This has been fixed by ensuring some long running background tasks do not affect the number of tasks controlled by the multiprogramming level. A workaround is to ensure that the minimum multiprogramming level is at least three times the number of mirrored databases.



Two new server properties were added by this change:

1) property( 'CurrentMirrorBackgroundWorkers' ): The number of workers currently being used for database mirroring background tasks. These workers are separate from those controlled by the multiprogramming level.

2) property( 'MaxMirrorBackgroundWorkers' ): The highest number of workers used for database mirroring background tasks since the server started. These workers are separate from those controlled by the multiprogramming level.



CR:736683
CR Number:   736683
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1501 08 Apr 2013 Fixed
12.0.1 3881 08 Apr 2013 Fixed
Description
An UltraLite database could have unnecessarily grown by a small amount during each synchronization, or as a result of executing publication DDL. This has now been corrected.



CR:736687
CR Number:   736687
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1530 02 May 2013 Fixed
12.0.1 3896 02 May 2013 Fixed
11.0.1 2979 02 May 2013 Fixed
Description
Queries with predicates of the form '( T.X = <constant expression> OR T.X = <constant expression> OR ...)' may have had unoptimal plans if the <constant expression> was a variable, host variable, or aliased constant. This has been fixed.



CR:736716
CR Number:   736716
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1503 08 Apr 2013 Fixed
12.0.1 3882 08 Apr 2013 Fixed
Description
By design, the Relay Server Outbound Enabler treats client disconnect as an immediate cancel of the request if it is happening at the middle of the HTTP request/response cycle. Therefore, uploads could have been truncated by the immediate cancelling, if the client disconnect arrived while the upload was queued up. This has now been changed so to make sure all request bytes that came before the disconnect are not cancelled by the client disconnect. Also, the RSOE no longer views this situation as an abnormal behavior of an HTTP client.



CR:736717
CR Number:   736717
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1503 08 Apr 2013 Fixed
12.0.1 3882 08 Apr 2013 Fixed
Description
The Relay Server may have reported that the shared memory manager was in an unhealthy state when under heavy load. This has been fixed.



CR:736786
CR Number:   736786
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1506 10 Apr 2013 Fixed
Description
Two ALTER TABLE ... DROP DEFAULT statements, executed consecutively on the columns that where created in an online fashion, would have cause the server fail assertion 200610 (Attempting to normalize a non-continued row ). This has now been fixed.



CR:736791
CR Number:   736791
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1500 08 Apr 2013 Fixed
Description
In the case where users turn on HTTP backend status detection in the Relay Server Outbound Enabler (by providing a url_status parameter in the -cs optiobn), it was possible for the RSOE to fail to identify if the backend was available or not. This has now been fixed by making the RSOE more tolerant to space characters when parsing the HTTP response provided by the backend server.



CR:736806
CR Number:   736806
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1509 12 Apr 2013 Fixed
12.0.1 3884 12 Apr 2013 Fixed
11.0.1 2970 12 Apr 2013 Fixed
Description
Under rare circumstances, evaluation of very complex expressions could have caused the server to crash. This has been fixed.



CR:736823
CR Number:   736823
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1501 09 Apr 2013 Fixed
12.0.1 3881 09 Apr 2013 Fixed
Description
If a database was created with the -a or -af dbinit command line options set, or with the "ACCENT RESPECT" or "ACCENT FRENCH" clause on a CREATE DATABASE STATEMENT, and if the database CHAR charset was not a UCA collation, then catalog lookups for tables, procedures, etc, could have been slow because the server would not have taken advantage of the available indexes on the catalog tables. This problem has been fixed.



As a side effect of the fix, dbunload now generates dbinit command lines or CREATE DATABASE statements that use fully explicit collation specifications such as "1252LATIN1(CaseSensitivity=Respect)" and it no longer puts -a, -af, ACCENT RESPECT, and ACCENT FRENCH on dbinit command lines or CREATE DATABASE statements. By using fully explicit collation specifications, dbunload also no longer puts "-c" or "CASE RESPECT/IGNORE" on dbinit command lines or CREATE DATABASE statements.



CR:737027
CR Number:   737027
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1955 25 Jun 2014 Fixed
12.0.1 4129 25 Jun 2014 Fixed
Description
If in a query block, two equal correlation names referred to exactly the same view or base table, then the server could have merged them and performed a query rewrite. The server incorrectly rewrote a query if one of the two table expressions aliased with the same correlation name was a derived table, a procedure name, an openstring expression, a contains expression, or a DML derived table. As a result, the server may have returned an incorrect result set. This has been fixed.



CR:737036
CR Number:   737036
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 29 Apr 2013 Fixed
12.0.1 3892 29 Apr 2013 Fixed
Description
Executing a REORGANIZE TABLE statement could have worked sub-optimally and may have left some pages with single rows on them. This has been fixed



CR:737159
CR Number:   737159
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1508 12 Apr 2013 Fixed
12.0.1 3884 12 Apr 2013 Fixed
11.0.1 2970 12 Apr 2013 Fixed
Description
If two separate connections had set the PRIORITY connection option, and the database shut down unexpectedly so as to required automatic recovery, it was possible for the database to fail the automatic recovery with assertion 100904:



Failed to redo a database operation (id=#, page_no=0x#, offset=0x###)

Error: Permission denied: you do not have permission to set the option 'PRIORITY'



This has been fixed. An upgraded database server will now be able to recover the database successfully.



CR:737184
CR Number:   737184
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2970 12 Apr 2013 Fixed
Description
It was possible for a mirror server running multiple mirrored databases to have hung, have had connection timeouts, failed, or have had poor performance. These problems were more likely as the number of mirrored databases running on the server increased. This has been fixed. As a workaround, the -gn value could be increased.



CR:737186
CR Number:   737186
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1509 12 Apr 2013 Fixed
12.0.1 3885 12 Apr 2013 Fixed
11.0.1 2970 12 Apr 2013 Fixed
Description
In rare, timing dependent cases, executing the "ALTER DATABASE SET PARTNER FAILOVER" statement could have hung. If this occurred, the server itself was not hung, but the server on which the statement was executed would not accept connections to the database being failed over. This has been fixed. As a workaround, the server that was running as the primary could be stopped, or the database that was running as the primary could be stopped by connecting to the utility database and executing the STOP DATABASE statement.



CR:737191
CR Number:   737191
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1508 12 Apr 2013 Fixed
12.0.1 3884 12 Apr 2013 Fixed
Description
The MSSqlToSA.xml mapping file is used by the SQL Server Import and Export Data wizard (DTSWizard). This mapping file has now been improved in the following ways:



- other SQL Server clients (SQLOLEDB;SQLNCLI;SQLNCLI10) are now included in the list of possible data sources, in addition to the existing SQL Server .NET provider.

- "datetimeoffset" is now mapped to "timestamp with time zone" instead of "datetimeoffset", because the Microsoft DTSWizard would append "(0)" to "datetimeoffset" and that would cause a syntax error when the CREATE TABLE statement was executed against a SQL Anywhere / Sybase IQ server. For example, "CREATE TABLE Temp (dtocol datetimeoffset(0) )" is invalid syntax.

- 揻loat is now mapped to 揹ouble, instead of float. This causes the Microsoft DTSWizard to use "real" for small precision float types, and "double" for large precision float types. When 揻loat was used, Microsoft did not add the precision specification (for example, float_col float(53)).



These improvements apply to the use of the SQL Anywhere .NET or the SQL Anywhere OLE DB providers, in combination with a number SQL Server providers, in the migration of tables from SQL Server to SQL Anywhere/Sybase IQ.



CR:737271
CR Number:   737271
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 29 Apr 2013 Not a Bug
Description
If two separate connections had set the PRIORITY connection option, and the database shut down unexpectedly and so required automatic recovery when restarted, it was possible for the database to fail the automatic recovery with assertion 100904:



Failed to redo a database operation (id=#, page_no=0x#, offset=0x###)

Error: Permission denied: you do not have permission to set the option 'PRIORITY'



This has been fixed. An upgraded database server will now be able to recover the database successfully.



CR:737416
CR Number:   737416
Product Name:   SQL Anywhere
Product Component:   OData Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1515 16 Apr 2013 Fixed
Description
When the OData Producer tried to create an entity against a SQL Anywhere proxy table, the server would have shutdown and the Producer would have failed. This has been fixed. However, the OData Producer for SQL Anywhere will not allow the use of default values in the proxy tables primary key. Clients must specify all primary key properties explicitly when creating new entities.



CR:737497
CR Number:   737497
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1537 01 May 2013 Fixed
12.0.1 3899 01 May 2013 Fixed
Description
Previously, the CREATE INDEX statement for local temporary tables on read-only nodes had been disallowed. This has been changed, and now local temporary tables are the only tables where index creation is allowed on the read-only databases.



CR:737533
CR Number:   737533
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1513 18 Apr 2013 Fixed
Description
When a secured feature exception occurred, and Sybase Central prompted for a secure feature key, it asked for an authorization key only. This has been corrected so that it now prompts for both the key name and its authorization key.



CR:737598
CR Number:   737598
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.0 4590 09 May 2013 Fixed
Description
The "Run New Task" wizard (and some others) display a list of task parameters with a component for each parameter. For those parameters which had a default value, the wizard provided an editable combobox for the value. The dropdown contained one item: "(Default)". There were a number of usability issues with the combobox which made it difficult to enter values when the box was open. This has been corrected so that now, the combobox has been replaced by a text field. When the text field is empty, the word "(Default)" appears in the field.



CR:737612
CR Number:   737612
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1514 17 Apr 2013 Fixed
12.0.1 3887 17 Apr 2013 Fixed
Description
If an application closed the connection to the database used to synchronize before the synchronization completed, the database could have become corrupt. One possible symptom of this corruption was the runtime sending two different progress values for the same publication during synchronization. This has been fixed. Now the runtime will report SQLE_SYNCHRONIZATION_IN_PROGRESS in the close connection call and immediate abort the application. When the database is restarted, recovery will be done to rollback any uncommitted operations that occurred during synchronization.



CR:737614
CR Number:   737614
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1514 18 Apr 2013 Fixed
12.0.1 3887 18 Apr 2013 Fixed
Description
If a native thread in the Java VM launched by the MobiLink Server printed to stdout, it was redirected to the MobiLink log file. If the MobiLink Server was ready to accept synchronizations when the Java VM attempted to print to stdout, it was possible that the Java VM could have crashed after printing the string, which would also have crashed the MobiLink Server. A work around for this issue is to start the Java VM with the -XtraceFile option, which will redirect the Java VM stdout to a file instead of the MobiLink log file. The issue has now been fixed, and the way the Java VM stdout strings are written to the MobiLink Log has changed. Instead of being posted as errors to the log with error number -10133, the output is now informational and has "(JVM): " at the start of the string to identify the source of the string.



CR:737801
CR Number:   737801
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1516 19 Apr 2013 Fixed
12.0.1 3889 19 Apr 2013 Fixed
Description
If a single user on a computer ran a number of copies of the Interactive SQL utility (dbisql), it was possible for its options to have been reset to their defaults. For this to have occurred, one dbisql process would have to have be starting, when another dbisql process was shutting down. This has now been fixed.



CR:737813
CR Number:   737813
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1516 29 Apr 2013 Fixed
Description
In the Options window, if the "Editor" category and the "Tabs" tab were selected, then the Options window was resized, the controls in the tab could have easily resized themselves in a way that made it very difficult to see the values. This has been fixed.



CR:737917
CR Number:   737917
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1528 30 Apr 2013 Fixed
12.0.1 4148 05 Aug 2014 Fixed
Description
Some queries that contained an invalid GROUP BY or HAVING clause could have failed to give an error. Specific constructs that were not correctly validated include the following:

- x IS OF TYPE()

- x IS [NOT] DISTINCT FROM y

- TSEQUAL( x, y )

- array_expression[[ index_expression ]]

- (row_type_expression).field_name

- Subqueries predicates or subselects that contained joins with outer references in the ON condition



In certain cases, these invalid queries failed with a non-fatal assertion failure. In specific circumstances, it was also possible for the server to crash. This problem has now been fixed.



CR:737992
CR Number:   737992
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1520 25 Apr 2013 Fixed
Description
The error message that was displayed when help could not be opened for the Console or Interactive SQL utilities was always in English. Now the message can be localized. Also, the title for the message window was incorrectly empty, this has been fixed.



CR:738030
CR Number:   738030
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1527 25 Apr 2013 Fixed
Description
The Event Trace Data File Management utility (dbmanageetd) did not display the full contents of an ETD file if logging to the file was interrupted (e.g. because of a process crash) and then resumed on a new process. This has been fixed.



CR:738031
CR Number:   738031
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1521 25 Apr 2013 Fixed
12.0.1 3891 25 Apr 2013 Fixed
Description
Using dbstop -c "...;NODETYPE=..." could have failed. Note that it is not recommended that NODETYPE is used with dbstop since it may not be clear which server will be stopped. This has been fixed.



CR:738036
CR Number:   738036
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1522 25 Apr 2013 Fixed
Description
Support for callbacks has been added to version 3 of the SQL Anywhere C API. The following function is now available when _SACAPI_VERSION is defined as 3.

void sqlany_register_callback( a_sqlany_connection * sqlany_conn, a_sqlany_callback_type index, SQLANY_CALLBACK_PARM callback );

This function can be used to register callback functions.



Parameters

sqlany_conn A connection object with a connection established using sqlany_connect().

index Any of the following:

CALLBACK_START

CALLBACK_WAIT

CALLBACK_FINISH

CALLBACK_MESSAGE

CALLBACK_CONN_DROPPED

CALLBACK_DEBUG_MESSAGE

CALLBACK_VALIDATE_FILE_TRANSFER

callback Address of the callback routine.



The index parameter values correspond to the index parameter values of the Embedded SQL/DBLIB db_register_a_callback function (http://dcx.sybase.com/goto?page=sa160/en/dbprogramming/db-register-a-callback-esql.html).

typedef enum a_sqlany_callback_type {

CALLBACK_START = 0,

CALLBACK_WAIT,

CALLBACK_FINISH,

CALLBACK_MESSAGE = 7,

CALLBACK_CONN_DROPPED,

CALLBACK_DEBUG_MESSAGE,

CALLBACK_VALIDATE_FILE_TRANSFER

} a_sqlany_callback_type;



Callback routines are typed "SQLANY_CALLBACK". This corresponds to the Embedded SQL/DBLIB SQL_CALLBACK type.

The a_sqlany_message_type enum is used with message callbacks (index=CALLBACK_MESSAGE).



typedef enum a_sqlany_message_type {

MESSAGE_TYPE_INFO = 0,

MESSAGE_TYPE_WARNING,

MESSAGE_TYPE_ACTION,

MESSAGE_TYPE_STATUS,

MESSAGE_TYPE_PROGRESS

} a_sqlany_message_type;



Here is an example from SDK\dbcapi\examples\callback.cpp.

api.sqlany_register_callback( sqlany_conn, CALLBACK_MESSAGE, (SQLANY_CALLBACK_PARM)messages );



void SQLANY_CALLBACK messages( void *sqlca, a_sqlany_message_type msg_type, int sqlcode, unsigned short length, char *msg )

{

size_t mlen;

char mbuffer[80];

switch( msg_type )

{

case MESSAGE_TYPE_INFO:

printf( "The message type was INFO.\n" );

break;

case MESSAGE_TYPE_WARNING:

printf( "The message type was WARNING.\n" );

break;

case MESSAGE_TYPE_ACTION:

printf( "The message type was ACTION.\n" );

break;

case MESSAGE_TYPE_STATUS:

printf( "The message type was STATUS.\n" );

break;

case MESSAGE_TYPE_PROGRESS:

printf( "The message type was PROGRESS.\n" );

break;

}

mlen = __min( length, sizeof(mbuffer) );

strncpy( mbuffer, msg, mlen );

mbuffer[mlen] = '\0';

printf( "Message was \"%s\" SQLCODE(%d)\n", mbuffer, sqlcode );

}



A complete callback example with two callback routines can be found in SDK\dbcapi\examples\callback.cpp.



CR:738143
CR Number:   738143
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 29 Apr 2013 Fixed
12.0.1 3892 29 Apr 2013 Fixed
Description
In rare circumstances, the ADO.NET Provider could have thrown an AccessViolationException when reading a DataSet. This has now been fixed.



CR:738144
CR Number:   738144
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1524 30 Apr 2013 Fixed
12.0.1 3893 30 Apr 2013 Fixed
11.0.1 2976 30 Apr 2013 Fixed
Description
In rare circumstances, calling SAConnection could have throw a NullReferenceException when the ConnectionString property was accessed. This has now been fixed.



CR:738147
CR Number:   738147
Product Name:   SQL Anywhere
Product Component:   OData Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1522 25 Apr 2013 Fixed
Description
When creating entities in an entity set representing a proxy table in a SQL Anywhere database, without fully specifying key properties, the OData Producer would have given an inaccurate error message (30125 - "One or more properties could not be reset to a default value."). This has been fixed. Now, if any of the missing key properties does not have a default value, a 30124 error ("Cannot set a non-nullable property to null.")will now be returned. Otherwise if the missing key properties have default values, a 30154 error ("Key properties with default values must be explicitly set in this entity set.") will now be returned.



CR:738148
CR Number:   738148
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.0 4573 25 Apr 2013 Fixed
Description
A number of issues with the 揅hange Server Version" wizard have been fixed:



1. On the "Restart Servers" page, if "Create a task..." was selected, options for methods selected in the "Run" box should have been shown, but were not. For example, if "Run" was set to "On a certain date", the date should have been selectable.



2. If the version of system servers was changed, and the cloud had high availability turned on, a message that the cloud needed to be restarted was displayed three times.



CR:738201
CR Number:   738201
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1554 24 May 2013 Fixed
12.0.1 3907 24 May 2013 Fixed
Description
When attempting a download resumption through the Relay Server to a MobiLink server farm, the client could have connected to the wrong MobiLink server, resulting in the download resumption attempt failing. The client weren抰 persisting the HTTP cookies that the Relay Server requires to match it back up with the correct MobiLink server. The cookies are now stored with the rest of the restart state.



CR:738246
CR Number:   738246
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 25 Apr 2013 Fixed
Description
The system trace events, SYS_RLL_StartProcedure, SYS_RLL_StopProcedure, SYS_RLL_StartTrigger, and SYS_RLL_StopTrigger, only logged one letter in the procedure_name field of the trace event. This has been fixed.



CR:738247
CR Number:   738247
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 25 Apr 2013 Fixed
Description
Trace event session names and trace event names were being treated as case sensitive. This has been fixed.



CR:738260
CR Number:   738260
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 29 Apr 2013 Fixed
12.0.1 3892 29 Apr 2013 Fixed
Description
A read-only scale-out system, or an asynchronous mirror, could have done more disk writes and more communication with children than necessary, which could have resulted in somewhat slower performance. The unnecessary writes and communication were most likely when many small transactions per second were being committed on the primary or root server. This has been fixed so that the unnecessary writes and communication have been eliminated.



CR:738276
CR Number:   738276
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 30 Apr 2013 Fixed
12.0.1 3893 30 Apr 2013 Fixed
11.0.1 2976 30 Apr 2013 Fixed
Description
For specific types of views and procedures using a WINDOW specification, it was possible for the server to crash when processing a query referencing the view or procedure. This has now been fixed.



CR:738279
CR Number:   738279
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Infrastructure
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.0 3881 29 Apr 2013 Fixed
Description
A SQL Anywhere OnDemand Edition cloud can be upgraded to an SAP Sybase SQL Anywhere, on-demand edition cloud provided:



1) the cloud infrastructure has been upgraded to 1.0.0.3881 (see note 1 below),

2) all the servers in the cloud are running 12.0.1.3873 (see note 2 below), and

3) the cloud secure feature key is at least 6 characters in length (see note 3 below).



If the SQL Anywhere OnDemand Edition cloud meets the above criteria, then the cloud can be upgraded by performing the following steps:



1) using the cloud console, choose 揈vents & Tasks->Run new task and run the PrepareForUpgrade task (see note 4 below).

2) once the PrepareForUpgrade task completes successfully, use the 揢pgrade cloud infrastructure button to download and upgrade to the new SAP Sybase SQL Anywhere, on-demand edition cloud.



Note 1:

If the SQL Anywhere OnDemand Edition cloud infrastructure is below version 1.0.0.3881, then use the 揢pgrade cloud infrastructure button to upgrade the cloud to version 1.0.0.3881.



Note 2:

If all the servers in the cloud are not running version 12.0.1.3783, then they can be upgraded to run the latest server version by:



1) Using the 揅loud Software->Change server version wizard, change the server version of all servers that are not running the latest server version to 12.0.1.3873. Make sure you select 揇o not restart any servers. Note that if you have both Windows and Linux hosts in your cloud, then you will need to perform this step twice, once for each platform.

2) Stop the cloud.

3) Restart the 1.0.0.3881 cloud agent on each of the cloud HA hosts. This will also start your cloud HA servers.

4) Start all of the other servers in your cloud.

5) Verify that all of the servers in the cloud are now running 12.0.1.3783.



Note 3:

If the cloud secure feature key is less than 6 characters in length, then use 揈vents & Tasks->Run new task to run the AlterCloud task. The AlterCloud task will allow you to change the cloud secure feature key.



Note 4:

The PrepareForUpgrade task takes two parameters: license_key and patch_file. The license_key parameter is not the license key that was provided with your SQL Anywhere OnDemand Edition software. Instead a new license key will be provided by SAP for the new SAP Sybase SQL Anywhere, on-demand edition cloud. The patch file will also be provided by SAP and you will be required to put this patch file locally on the host where the cloud primary server is running. The patch_file parameter is the full path to the patch file on the primary host.



When the PrepareForUpgrade task runs, it will verify that the license key is correct, the secure feature key is at least 6 characters in length and all of the servers in the cloud are running 12.0.1.3873. If any of these criteria is not met, then the PrepareForUpgrade task will exit with an appropriate message. It should be noted that these messages will be returned in English only.



Once all of the above criteria are met, the PrepareForUpgrade task will run and will modify the cloud as follows:



1) All software earlier than version 1.0.0.3881-12.0.1.3873 will be removed from all hosts in the cloud. This includes both installed software and hosted software.

2) A unique public key/private key pair will be generated and stored on each host in the cloud.

3) The patch file provided by SAP will be applied to allow the cloud to download the new SAP Sybase SQL Anywhere, on-demand edition software.



Please note that the PrepareForUpgrade task can take a significant amount of time to run depending on the number of hosts in the cloud. Once the PrepareForUpgrade task completes, the cloud is ready to be upgraded to the new SAP Sybase SQL Anywhere, on-demand edition software. The cloud at this point is perfectly usable and databases can continue to be added, dropped, backed up etc. You should not, however, attempt to add new hosts after performing the PrepareForUpgrade task and before completing the 揢pgrade cloud infrastructure process. If you do add hosts between the time that you run PrepareForUpgrade and before you complete the 揢pgrade cloud infrastructure, then you will be required to run PrepareForUpgrade a second time.



CR:738302
CR Number:   738302
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 29 Apr 2013 Fixed
Description
When comparing databases, Sybase Central could have run out of memory if the source for a procedure, function, view, materialized view or trigger contained a large comment within the 揅REATE <object-type> <object-owner>.<object-name> prefix. This has been fixed.



CR:738312
CR Number:   738312
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1523 29 Apr 2013 Fixed
Description
When comparing databases, an error could have occurred if either database contained any of the following:

1. A table column with a default value containing nested parentheses

2. A table column with a computed value spanning multiple lines and/or containing nested parentheses

3. A table or column check constraint definition spanning multiple lines and/or containing nested parentheses



These issues have been fixed.



CR:738381
CR Number:   738381
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1528 30 Apr 2013 Fixed
12.0.1 3895 30 Apr 2013 Fixed
Description
Changes have been made to improve performance for connection pooling.



CR:738400
CR Number:   738400
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1524 30 Apr 2013 Fixed
Description
In the 12.0.1 installer for Mac OS X, there is an information panel at the end of the install that tells users that they must build the UltraLite library from the source files included in the install prior to developing on iPhone or building the samples. This panel was erroneously excluded in the 16.0 GA installer, though it still applies, and has now been added.



CR:738415
CR Number:   738415
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1540 15 May 2013 Fixed
12.0.1 3901 15 May 2013 Fixed
Description
Use of connection pooling could have caused web applications to hang. This has been corrected.



CR:738510
CR Number:   738510
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1527 30 Apr 2013 Fixed
Description
The xp_getenv() built-in function returns long binary. In nearly all cases, since environment variables are typically used to store strings, users would need to cast the long binary value to a char or nchar type, depending on their needs. Optionally, csconvert() would need to be used in order to ensure the strings are in the correct character set, but this is not particularly easy to use. This has been corrected. In databases created after this fix, xp_getenv() will return a long nvarchar. This allows strings to be used easily, while minimizing string mangling due to character set conversion. The environment variable value is obtained in UTF-16 from Windows. On Unix platforms, both the variable name and the variable value are assumed to be in the OS charset, and are then converted to the NCHAR charset for the database. If this is not the case, some variable name lookups may fail or values may be mangled.



CR:738517
CR Number:   738517
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1527 30 Apr 2013 Fixed
12.0.1 3893 30 Apr 2013 Fixed
Description
On Unix platforms, using any of the email functions, while running a version 12.0 database on a version 16.0 server, would have failed with an error: 揇ynamic library 憀ibdbextf.so could not be loaded. This has now been fixed.



There are two workarounds:

- ensure that libdbtasks12_r.so.1 is in the library load path (e.g. copy it into the SA 16.0 installation next to libdbextf.so.1)

- upgrade the database to version 16.0



CR:738617
CR Number:   738617
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1531 03 May 2013 Fixed
12.0.1 3897 03 May 2013 Fixed
11.0.1 2979 03 May 2013 Fixed
Description
In exceptional rare circumstances, the server may have crashed while trying to use the string value of a column DEFAULT or COMPUTE definition. This may have occurred after resetting the column's DEFAULT or COMPUTE definition using ALTER TABLE. Restarting

the database after executing the ALTER TABLE prevents the problem. This has been fixed.



CR:738659
CR Number:   738659
Product Name:   MobiLink
Product Component:   MobiLink Profiler
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1529 01 May 2013 Fixed
Description
In some cases, a profiling session opened from the profiling database may have had some changed information, compared to when the profiling session was collected. Some data may not have been saved correctly in the database, especially if the same MobiLink Profiler instance was used for multiple sessions and non-initial sessions were ended while synchronizations were active, or while recent data was still being saved in the profiling database. Even if the data in the profiling database was correct, the "in progress" and "active" sync properties would always have been false when a saved session was opened. These problems have now been fixed.



To mitigate these problems, restart the Profiler between sessions, start sessions when no synchronizations are in progress, and end sessions after all synchronizations have completed.



CR:738679
CR Number:   738679
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1529 01 May 2013 Fixed
Description
If a database created with a version 12 server was run on a version 16 server (without being upgraded), inserting data into a compressed column would have succeed and the data could be correctly retrieved, but if the same database was later moved back to a version 12 server, the data may not have been retrieved correctly. This problem would also have been seen if views, procedures, events, triggers, comments on objects, text configuration objects, or java JAR files were added or altered in the version 12 database while running on the version 16 server (since those system tables contain compressed columns). This has been fixed.



CR:738691
CR Number:   738691
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1529 02 May 2013 Fixed
Description
Using the dbmanageetd.exe command line option 杅regex prevented any results from being filtered. This has been fixed.



CR:738707
CR Number:   738707
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1530 02 May 2013 Fixed
12.0.1 3896 02 May 2013 Fixed
11.0.1 2979 02 May 2013 Fixed
Description
When a mirror or copy node was transitioning between pulling log pages and having the primary or parent pushing log pages, it was possible for the mirror or copy node to have failed assertions 112011 or 100927. This has been fixed.



CR:738756
CR Number:   738756
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1538 09 May 2013 Fixed
12.0.1 3899 09 May 2013 Fixed
11.0.1 2982 09 May 2013 Fixed
Description
If an operation on the database had executed trigger actions that included UPDATE PUBLICATION commands, and that operation was also implicitly rolled back because of an error in the trigger (such as a referential integrity violation), then it was possible for SQL Remote (dbremote) to have sent operations that would have been rolled back in the database. The Log Translation utility (dbtran) may have also shown operations as committed in the translated transaction log that were rolled back. This issue has now been fixed



CR:738779
CR Number:   738779
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1530 02 May 2013 Fixed
Description
The UltraLite Runtime could have crashed when setting a blob parameter on a prepared statement if the statement was a query and there were more parameters than columns in the result set. This has been fixed.



CR:738782
CR Number:   738782
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1527 03 May 2013 Fixed
12.0.1 3896 03 May 2013 Fixed
Description
The integrated Relay Server Outbound Enabler (RSOE) library could have crashed the Mobilink server in the following cases:

1- In an error case, such as a failure to send data to the backend

2- In a timing sensitive situation, while the RSOE was sending data to the backend and receiving a notification from the RelayServer to disconnect a socket (due to client dropping the connection or aborting for any reason before completing a clean send/receive HTTP cycle).



This has been fixed.



CR:738786
CR Number:   738786
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   16.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1530 03 May 2013 Fixed
Description
The integrated Relay Server Outbound Enabler (RSOE)could have missed processing a socket close event, leading to leaked memory. This problem was rare and random and only occurred in a time-sensitive scenario where the integrated RSOE was sending data to the backend server and received a notification from the Relay Server to close that particular socket connection. This has been fixed.



CR:738912
CR Number:   738912
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1533 06 May 2013 Fixed
12.0.1 3898 06 May 2013 Fixed
Description
In extremely rare cases, a copy node could have been partially connected to its parent indefinitely, and not write or apply log operations. In order for this to have occurred, a connection to its parent would need have been dropped shortly after it was established. The sa_mirror_server_status() system procedure would have reported the copy node as connected. This has been fixed.



As workaround, restarting the copynode in this state would cause it to get and apply log operations from its parent.



CR:738955
CR Number:   738955
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1535 06 May 2013 Fixed
12.0.1 3898 06 May 2013 Fixed
11.0.1 2981 06 May 2013 Fixed
Description
In rare timing dependent cases, when the primary server was shutdown, the mirror could have failed to take over as primary. In versions 11 and 12, both the primary and mirror could have both appeared to have hung for two minutes while the primary was shutting down. This has been fixed.



CR:738974
CR Number:   738974
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 May 2013 Fixed
Description
The SQL Anywhere Python Database support (sqlanydb) does not work with python 3.3. This has been fixed.



CR:738994
CR Number:   738994
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1538 08 May 2013 Fixed
12.0.1 3899 08 May 2013 Fixed
11.0.1 2982 08 May 2013 Fixed
Description
If the mirror tried to take over as primary and failed, in rare cases it was possible for the database on the mirror to have become corrupted. The most likely case of this occurring involved the connection between the two partners being dropped for some reason, and then the mirror server or database being shut down while the mirror was in the middle of attempting to take over as primary. This has been fixed.



CR:739081
CR Number:   739081
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1537 08 May 2013 Fixed
Description
Inherited object privileges can now be viewed for any table, view, procedure, function, sequence generator, or dbspace via the 揚rivileges tabs.



Also, inherited object privileges can now be viewed for any user or role via the 揟able Privileges, 揤iew Privileges, 揚rocedure Privileges, 揝equence Privileges, and 揇bspace Privileges tabs.



In both cases, a new 揝how Inherited check box has been added to the tabs. With the check box checked, the tabs show privileges that are inherited through role inheritance, in addition to privileges that are granted explicitly.



CR:739154
CR Number:   739154
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1538 08 May 2013 Fixed
12.0.1 3899 08 May 2013 Fixed
Description
In rare timing dependent cases, the primary could have restarted unnecessarily if the connection between the primary and mirror server was dropped about the same time that the mirror became synchronized. When the primary restarted, the database was stopped and restarted, causing all connections to have been dropped. This has been fixed so that the primary does not restart in this case.



CR:739171
CR Number:   739171
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1538 08 May 2013 Fixed
Description
Sybase Central could have become unresponsive for a few moments when a stored procedure was saved, if the text completer was open. The problem occurred if the start of the ALTER PROCEDURE statement was modified (perhaps by removing the quotation marks from the owner or procedure name), then clicking the "Save" toolbar button. This has been fixed.



CR:739173
CR Number:   739173
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1538 09 May 2013 Fixed
12.0.1 3899 09 May 2013 Fixed
Description
In the MobiLink Server Log File Viewer, on the "Synchronizations" panel, a single synchronization could have appeared a number of times in the "Synchronizations" table. This happened when the messages from the sync were interspersed with messages from "<Main>". This has been fixed.



CR:739187
CR Number:   739187
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1544 14 May 2013 Fixed
12.0.1 3902 14 May 2013 Fixed
11.0.1 2984 14 May 2013 Fixed
Description
If an application executed the STOP JAVA or STOP EXTERNAL ENVIRONMENT statement for a database scoped external environment (i.e java or clr), then the server and external environment resources associated with the connection would be correctly cleaned up, but the external environment executable would not have been shut down. This problem has been corrected and the executable will now shut down when the STOP JAVA or STOP EXTERNAL ENVIRONMENT CLR statement is explicitly executed and there are no other connections using the database scoped external environment.



CR:739247
CR Number:   739247
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1607 18 Jul 2013 Fixed
12.0.1 3939 18 Jul 2013 Fixed
Description
When a new SAConnectionStringBuilder object was created and used by each SAConnection object in a loop, performance was slow. Performance has now been improved.



CR:739248
CR Number:   739248
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1539 10 May 2013 Fixed
Description
CREATE TABLE allows the default for a column to reference a non-existing variable. The server does not validate the DEFAULT clause at creation time. Trying to do the same thing in ALTER TABLE, causes a server crash. This has been fixed, and the server now returns an appropriate error message.



CR:739269
CR Number:   739269
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1543 14 May 2013 Fixed
12.0.1 3902 13 May 2013 Fixed
Description
A procedural statement of the form "IF [NOT] EXISTS( simple-subselect ) ..." may have failed with a warning or an error. The warning "The result returned is non-deterministic" was returned if the subselect did not contain an ORDER BY clause. The error "Cursor has not been declared" was returned if the THEN clause, but not the ELSE clause, contained a SELECT statement that returned a result set, and the IF condition evaluated to 'false'. This has been fixed.



CR:739349
CR Number:   739349
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1544 14 May 2013 Fixed
12.0.1 3902 14 May 2013 Fixed
Description
If an application executed a SQL SECURITY INVOKER JAVA stored procedure with an effective user id that required quoting or that was owned by a user id that required quoting, then the server would have failed the Java procedure execution with a syntax error. This problem has now been fixed.



Note, a user id that requires quoting would be one that was either a keyword, or contained a dot (.) or some other unusual character. No other external environment is affected by this problem.



CR:739361
CR Number:   739361
Product Name:   MobiLink
Product Component:   MobiLink Profiler
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1540 10 May 2013 Fixed
Description
An error could have occurred if the View > By Remote ID option was selected when a profiling session was started. This has been fixed.



A workaround is to use View > Compact View instead.



CR:739688
CR Number:   739688
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3783 15 May 2013 Fixed
Description
If the SQL Anywhere OnDemand Edition cloud infrastructure is below version 1.0.0.3881, then use the 揢pgrade cloud infrastructure button to upgrade the cloud to version 1.0.0.3881. Once the cloud infrastructure has been upgraded to 1.0.0.3881, then the cloud servers can be upgraded to 12.0.1.3783.



To upgrade the cloud servers to 12.0.1.3783, follow the steps outlined below instead of following the original documented procedure:



1) Using the 揅loud Software->Change server version wizard, change the server version of all servers that are not running the latest server version to 12.0.1.3873. Make sure to select 揇o not restart any servers. Note that if there are both Windows and Linux hosts in your cloud, then this step will need to performed twice, once for each platform.

2) Stop the cloud.

3) Restart the 1.0.0.3881 cloud agent on each of the cloud HA hosts. This will also start the cloud HA servers.

4) Start all of the other servers in the cloud.

5) Verify that all of the servers in the cloud are now running 12.0.1.3783.



CR:739706
CR Number:   739706
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1547 16 May 2013 Fixed
Description
If a server was started with a database that contained an invalid path to the transaction log file, the startup message and console log could have contained garbage characters. This has been fixed.



CR:739802
CR Number:   739802
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1547 16 May 2013 Fixed
Description
When connected to an IQ database, or if your the Interactive SQL utility is configured to use only IQ, the following "Help" menu items have been disabled:



Interactive SQL Help

SQL Syntax

Keyboard Shortcuts



Also, on the "Connect" window, the "Help" button has been disabled if the type selected is "SAP Sybase IQ".



CR:739810
CR Number:   739810
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1547 17 May 2013 Fixed
12.0.1 3903 17 May 2013 Fixed
Description
During quick setup, users are prompted by the following question:

Expect Afaria clients (y/N)?

If the answer is yes, the expectation is that the quick setup script will configure IIS to turn off request buffering, due to the incompatibility between IIS and Afaria client regarding how the size of the entity body of the HTTP request was specified. The IIS7 version of the quick setup script was failing to turn off the buffering. This problem has been fixed.



CR:739834
CR Number:   739834
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1535 17 May 2013 Fixed
Description
If a recipient list for an email sent using xp_sendmail contained leading, trailing, or duplicate semi-colons, the server could have crashed when sending the message. This has been fixed.



CR:739835
CR Number:   739835
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1535 17 May 2013 Fixed
Description
The body of email messages sent using xp_sendmail would have been truncated at 255 characters. This has been fixed.



CR:739928
CR Number:   739928
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1548 22 May 2013 Fixed
Description
When the 64-bit version of the Information utility (dbinfo) was run on Mac OS X systems with the -u option, the values for the 揑ndex Pages, %used (index pages) and 揚ercent of File columns could have been very large positive or negative numbers. This has been fixed.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具:ReadASADB。
此工具支持ASA v5.0,v6.0,v7.0,v8.0,v9.0,v10.0,v11.0,v12.0等版本。
恢复Sybase SQL Anywhere的工具在国内应该算首创。

ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具

  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集  包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

本工具的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------