远程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:649138
CR Number:   649138
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3104 22 Nov 2010 Fixed
12.0.0 2613 22 Nov 2010 Fixed
Description
Editing a LONG VARCHAR value on the Data tab in Sybase Central, or in the Results panel of the Interactive SQL utility, would have caused a crash if the value was entered directly, as opposed to loading the value from a file. This has been fixed.



CR:649298
CR Number:   649298
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3104 22 Nov 2010 Fixed
12.0.0 2614 22 Nov 2010 Fixed
Description
If the "backend security" option for a backend server farm was set to HTTP or HTTPS in the relay server plugin, the setting was not written to the relay server configuration file and so was lost when the file was saved. This has now been corrected.



CR:649315
CR Number:   649315
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3104 22 Nov 2010 Fixed
12.0.0 2614 22 Nov 2010 Fixed
Description
When viewing a graph widget in either Japanese or Simplified Chinese, the time axis would have used an incorrect localization. This has been fixed. The Monitor now uses the numeric MM/DD format in these cases. Note that English, German and French locales are not affected by this fix.



CR:649437
CR Number:   649437
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)
12.0.1 3097 23 Nov 2010 Fixed
12.0.0 2618 23 Nov 2010 Fixed
11.0.1 2526 02 Dec 2010 Fixed
Description
Version 9.0.x has an optimization for a very large number of WHERE predicates that are in Disjunctive Normal Form (DNF), which was not implemented starting with version 10.0.0.

For example:

WHERE

(T.A1 = c11 and T.A2 = c12 and ... and T.Ak =c1k) OR

.....

(T.A1 = cN1 and T.A2 = cN2 and .... and T.Ak =cNk)

AND

(other predicates)



The values for c11, c12, ..., cNk are constants, and N is large. The following sargable IN predicates were generated from the original predicates:

T.A1 IN {c11,c21, ..., cN1} AND

...

T.Ak IN { c1k, ..., cNk}



If there existed an index on table T with a prefix on any combination of the columns T.A1, ..., T.Ak, then a partial index scan using the sargable IN predicates could have been chosen in the best access plan. For example, if an index 'idx1' existed on T < A2, Ak > then the partial index scan [ {c12, ..., cN2} JNL {c1k, ..., cNk} JNL T <idx1>] may have been used in the best access plan. The original predicate would still have been applied after the index scan as a postfilter.



This optimization was not implemented starting with SA 10.0.0, as multiindex scans introduced in SA 11.0.0 and enhanced in SA 11.0.1 provided more general access methods using any combination of UNION and INTERSECTION of indexes. Multiindex scans performed better than the above optimization for small to medium size DNF predicates. However, multiindex scans can be inefficient when the number of predicates is large, for example, DNF predicates having 1,000 or more terms. This new feature addresses, in a very general way, these extreme cases and other cases when multiindex index scans use the same index. A multicolumn inmemory table is built with the exact combinations used in a DNF term, and this table is joined with the index scan. In the example above, if an index 'idx2' on T<A1, A2,..., Ak> exists, the access method

[{(c11,c12,...,c1k), (c21,c22,...,c2k),..., (cN1, cN2, ..., cNk)} JNL T<idx2>]

will be built.

Prior to this change the following multiindex scan was considered:

T<idx2: (c11,c12,...,c1k)> UNION T<idx2: (c21,c22,...,c2k)> UNION ... UNION T<idx2: (cN1,cN2,...,cNk)>

This multiindex scan could have been inefficient if N was greater than 1,000.



CR:649468
CR Number:   649468
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3105 23 Nov 2010 Fixed
12.0.0 2614 23 Nov 2010 Fixed
11.0.1 2527 23 Nov 2010 Fixed
10.0.1 4151 23 Nov 2010 Fixed
Description
When a SQL error occurred that was not in the last SQL statement entered, an error dialog was displayed that had a 'Continue' and a 'Stop' button. Hitting the escape key had no effect. Thisn has been corrected so that hitting the escape key on this dialog now selects the 'Stop' action.



For example, open the Interactve SQL utility (dbisql), connect to database and enter the following:



select * from foo;

select 'hello'



Since there is no table foo, the first statement generates an error dialog with a 'Stop' and 'Continue' button. Hitting escape here is now the same as pressing the 'Stop' button.



CR:649475
CR Number:   649475
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)
12.0.1 3105 24 Nov 2010 Fixed
12.0.0 2615 24 Nov 2010 Fixed
11.0.1 2528 24 Nov 2010 Fixed
10.0.1 4145 24 Nov 2010 Fixed
Description
If a JDBC application connected via jConnect called the method DatabaseMetaData.getSchemas(), then the server would have failed the request with the error "the 'FileVersion' property is no longer supported". This problem has now been fixed and the proper list of userids is now returned to the application.



CR:649492
CR Number:   649492
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3105 24 Nov 2010 Fixed
12.0.0 2614 24 Nov 2010 Fixed
11.0.1 2528 24 Nov 2010 Fixed
Description
The Ping utility (dbping) can be used to specify an ODBC driver or driver manager library (-l option). If the Unix driver manager included with SQL Anywhere (libdbodmX.so) was used as the argument for the dbping -l option, dbping would have returned the error 'Failed爐o爈oad燨DBC燿river'. This has been fixed so that dbping can be used with libdbodmX.so.



CR:649528
CR Number:   649528
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3110 25 Nov 2010 Fixed
12.0.0 2615 25 Nov 2010 Fixed
11.0.1 2529 25 Nov 2010 Fixed
Description
Execution of DROP TABLE and DROP INDEX statements would not have failed when the affected table was being referenced by another prepared statement. This has been corrected.



CR:649614
CR Number:   649614
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)
12.0.1 3110 29 Nov 2010 Fixed
12.0.0 2616 29 Nov 2010 Fixed
Description
Column constraints using the TREAT() function or IS OF predicate could have incorrectly allowed references to columns other than the column the constraint was created on. This has been fixed.



CR:649620
CR Number:   649620
Product Name:   UltraLiteJ
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3105 24 Nov 2010 Fixed
12.0.0 2615 24 Nov 2010 Fixed
Description
When attempting to transfer a database from a BlackBerry device via USB, the on-device utility would have reported an error transferring the database, but the log would have shown the last chunk was sent. This issue did not reproduce on simulators. In most cases, an examination of the database that was received on the desktop would have shown that the database was completely transferred. This has been fixed.



CR:649644
CR Number:   649644
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3109 24 Nov 2010 Fixed
12.0.0 2615 24 Nov 2010 Fixed
11.0.1 2528 24 Nov 2010 Fixed
Description
The ODBC driver could not properly handle the following SQL statement because it thought it was improperly formed:

create table [ab'cd] (i int )



This has now been fixed so that the driver now supports table names with embedded quotes enclosed in brackets.



CR:649651
CR Number:   649651
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)
12.0.1 3110 25 Nov 2010 Fixed
12.0.0 2615 25 Nov 2010 Fixed
Description
If a query was executed that contained a function in the SELECT list, and the function was defined in the following very specific way:

CREATE FUNCTION ...

RETURNS ...

BEGIN

DECLARE variable ...

SELECT ... INTO variable FROM ...

RETURN variable

END



and the SELECT statement within the function referenced proxy tables, then there was a chance the server would have crashed. This problem has now been fixed.



CR:649655
CR Number:   649655
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3111 26 Nov 2010 Fixed
12.0.0 2616 26 Nov 2010 Fixed
11.0.1 2529 26 Nov 2010 Fixed
Description
The result set returned by a query could have had an incorrect ordering when different indexes could have been used to implement WHERE conjuncts and ORDER BY clause This was corrected.



An example would be

SELECT * FROM table WHERE c1 = 10 ORDER BY c2

where c1 and c2 each were the first column in different indexes.



CR:649763
CR Number:   649763
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3111 26 Nov 2010 Fixed
12.0.0 2616 26 Nov 2010 Fixed
11.0.1 2529 26 Nov 2010 Fixed
Description
If an application connected with autostop=yes, and subsequently made a CLR external environment call, then the CLR external environment could have crashed when the application disconnected. This problem has now been fixed.



CR:649795
CR Number:   649795
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)
12.0.1 3105 25 Nov 2010 Fixed
12.0.0 2614 25 Nov 2010 Fixed
11.0.1 2527 25 Nov 2010 Fixed
10.0.1 4151 25 Nov 2010 Fixed
Description
Queries over indexes could have returned incorrect results if long index entries (greater than ~240 bytes) appeared in the index, with index corruption a possibility. This has been fixed.



CR:649797
CR Number:   649797
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)
12.0.1 3110 25 Nov 2010 Fixed
12.0.0 2615 25 Nov 2010 Fixed
11.0.1 2529 25 Nov 2010 Fixed
10.0.1 4156 25 Nov 2010 Fixed
Description
An index containing long values could have become corrupted if the table was subsequently altered to add columns, remove columns that did not appear in the index, or change the nullability of a column not appearing in the index. Also, for this to have happened, entries must have been deleted from the index. This has been fixed.



CR:649868
CR Number:   649868
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)
12.0.1 3112 29 Nov 2010 Fixed
12.0.0 2616 29 Nov 2010 Fixed
11.0.1 2530 29 Nov 2010 Fixed
Description
A brief network outage in a mirroring environment could have resulted in one of the servers reporting "Alternate server name in use"; or the former mirror server restarting, but not becoming the primary server. This has been fixed.



CR:649928
CR Number:   649928
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)
12.0.1 3115 29 Nov 2010 Fixed
11.0.1 2530 29 Nov 2010 Fixed
10.0.1 4154 29 Nov 2010 Fixed
Description
Sending large attachment files via SMTP using the system Procedure xp_sendmail() may have crashed the server. This problem was introduced by the changes made for Engineering case 643590, and have now been fixed.



CR:649978
CR Number:   649978
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)
12.0.1 3116 01 Dec 2010 Fixed
12.0.0 2617 01 Dec 2010 Fixed
11.0.1 2531 01 Dec 2010 Fixed
Description
Under rare circumstances, some statements involving proxy tables could have missed expression checking. This has been corrected.



CR:650006
CR Number:   650006
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3115 29 Nov 2010 Fixed
12.0.0 2617 29 Nov 2010 Fixed
Description
On the "Create Backend Server Farm" dialog, the Apply button was not enabled when the selection in the "Client security" or "Backend security" comboboxes was changed. This has been fixed.



CR:650010
CR Number:   650010
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3116 01 Dec 2010 Fixed
12.0.0 2617 01 Dec 2010 Fixed
11.0.1 2531 01 Dec 2010 Fixed
Description
Some large integers were being improperly scanned. This has been corrected.



CR:650116
CR Number:   650116
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)
9.0.2 3995 30 Nov 2010 Fixed
Description
The server may have crashed when a stored procedure that had a SQL statement with window functions was executed. The crash did not occur immediately when the procedure was executed, but some time later. This has been fixed.



The workaround is to rewrite the SQL statement to not use window functions.



CR:650177
CR Number:   650177
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)
12.0.1 3120 06 Dec 2010 Fixed
12.0.0 2618 06 Dec 2010 Fixed
11.0.1 2532 06 Dec 2010 Fixed
Description
Both the Interactive SQL utility and Sybase Central use the same syntax highlighting editor to display SQL. On Mac OSX systems only, hitting the tab key in the editor would have caused all the text in the editor to be selected and indented 1 tab stop. This has been fixed. Now, when the tab key is pressed, if any text in the editor is selected then that text is indented 1 tab, otherwise a tab character is inserted at the current insertion point.



CR:650337
CR Number:   650337
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)
12.0.1 3262 01 Dec 2010 Fixed
12.0.0 2621 10 Dec 2010 Fixed
11.0.1 2531 10 Dec 2010 Fixed
Description
Queries with an outer join having the same base table as the preserved and null-supplying sides could have returned incorrect result sets. Conditions where this could happen:

1. the outer join is of the form : T as T1 LEFT OUTER JOIN T as T2 ON(p)

2. the ON predicate p has only equijoins, and at least two equijoins

3. p is of the form : T1.c1 = T2.c1 and T1.c3 = T2.c2

4. there exists an unique index on T < c1,c2>



This has been fixed.



CR:650345
CR Number:   650345
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3119 02 Dec 2010 Fixed
12.0.0 2618 02 Dec 2010 Fixed
Description
The "Connect" window allows for starting and connecting to a database on a different machine. When that action was selected, a dialog is presented with a number of fields to fill in (Host, Port, Database File Name, etc.) A checkbox to turn off Autostart was missing. It has been added.



This affected all programs that use the "Connect" window to connect to a SQL Anywhere database -- the Interactive SQL utility, Sybase Central, and the Console utility. A workaround is to add "astop=no" to the "(other)" field on the "Advanced Options" tab.



CR:650352
CR Number:   650352
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)
12.0.1 3119 02 Dec 2010 Fixed
12.0.0 2618 02 Dec 2010 Fixed
11.0.1 2531 02 Dec 2010 Fixed
Description
Procedure profiling showed statements that executed in under 1 millisecond as using zero time, even when those statements were executed many times. This has been fixed.



CR:650489
CR Number:   650489
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)
12.0.1 3126 03 Dec 2010 Fixed
12.0.0 2621 03 Dec 2010 Fixed
11.0.1 2534 03 Dec 2010 Fixed
10.0.1 4158 03 Dec 2010 Fixed
Description
If an application made a remote procedure call that made changes to a remote database and then subsequently called ROLLBACK, the changes would not have been rolled back on the remote database that the remote procedure call affected, but would have been rolled back locally and on the other remote databases that the local connection modified. This problem has now been fixed.



CR:650502
CR Number:   650502
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3120 03 Dec 2010 Fixed
12.0.0 2518 03 Dec 2010 Fixed
Description
When an ODBC application called SQLDriverConnect to connect, and specified the SQL_DRIVER_PROMPT option so that the connection dialog was displayed, the connection string returned did not contain the DSN parameter. All other parameters were correctly returned, but DSN was stripped out. This has been fixed.



CR:650626
CR Number:   650626
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2627 04 Jan 2011 Fixed
Description
The "Check for updates" menu items (start menu and application menus) would have always reported that a new version of the Documentation was available, even when the latest version was installed. This has been fixed.



CR:650650
CR Number:   650650
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3121 03 Dec 2010 Fixed
12.0.0 2619 03 Dec 2010 Fixed
Description
When the action setting on the Logon page of the ODBC administrator was "Start and connect to another computer", the Autostop checkbox was missing. This has been fixed.



Note, Engineering case 650345 is a similar issue in the Administration tools connection dialog.



CR:650663
CR Number:   650663
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3125 07 Dec 2010 Fixed
12.0.0 2620 07 Dec 2010 Fixed
Description
Executing a query that involved the use of the Java external environment, and that required the server to repeatedly call the same Java method over and over again, may have resulted in the performance of the query might being very slow. The server performance in this specific case has now been improved considerably. Note that this performance improvement may not help queries where multiple Java methods are called at the same time.



For example, the query:

SELECT SUM( java_p(...) ) FROM ...



involves repeatedly calling java_p and the performance of such queries will be improved with this fix. In addition, the query:

SELECT SUM( java_p(...) ), AVG( java_p(...) ) FROM ...



also involves repeatedly calling java_p, and again the performance of such queries will be improved with this fix. But, the query:

SELECT SUM(java_p(...)), AVG(java_p2(...)) FROM ...



which involves repeatedly calling both java_p and java_p2 will not benefit from this performance improvement.



CR:650690
CR Number:   650690
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3261 07 Dec 2010 Fixed
12.0.0 2620 07 Dec 2010 Fixed
Description
The server would have returned assertion failed 100905 "Articles on the table use do not match those on the table definition", if a table had publications and a simple INSERT with multiple row value constructors was executed. For example: insert into tab1 values (1,'a'),(2,'b'). This has been fixed.



CR:650719
CR Number:   650719
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Windows 2000
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3275 14 Jan 2011 Fixed
12.0.0 2632 14 Jan 2011 Fixed
11.0.1 2546 14 Jan 2011 Fixed
10.0.1 4170 14 Jan 2011 Fixed
Description
After a failed download, an attempt to restart the download may have failed and reported a "Protocol Error" or a read failure. This has been fixed.



CR:650740
CR Number:   650740
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)
12.0.1 3261 10 Dec 2010 Fixed
12.0.0 2621 10 Dec 2010 Fixed
11.0.1 2535 10 Dec 2010 Fixed
10.0.1 4159 10 Dec 2010 Fixed
Description
Execution of a DROP DATABASE statement would have failed if the automatically generated database alias name was an invalid identifier. This has been fixed.



CR:650829
CR Number:   650829
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2533 06 Dec 2010 Fixed
10.0.1 4157 06 Dec 2010 Fixed
Description
The Validate utility, or the VALIDATE utility, could have reported spurious orphaned blobs if there were indexes containing long values. This has been fixed.



CR:650856
CR Number:   650856
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2621 10 Dec 2010 Fixed
11.0.1 2535 10 Dec 2010 Fixed
12.0.1 3298 04 Mar 2011 Fixed
10.0.1 4281 05 Oct 2011 Fixed
Description
Synchronizations using HTTP-based communication protocols (including HTTP, HTTPS and other encrypted HTTP protocols) could have failed intermittently. When synchronizations failed, they would do so after the download had been applied and committed, and would have reported an error message like: "Data read failed. Requested 2 bytes but got 0 bytes." When this occurred the MobiLink server would have reported the error: "Connection was dropped due to lack of network activity". These failures were only likely to occur when applying the download to the remote database took longer than the stream timeout interval, which is 4 minutes by default. This problem has now been resolved



CR:650870
CR Number:   650870
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3124 07 Dec 2010 Fixed
12.0.0 2620 07 Dec 2010 Fixed
Description
The MobiLink Replay utility (mlreplay) could have crashed when using a replay DLL/shared object if the recorded protocol being replayed was not the same as the recorded protocol used to generate the code for the replay DLL/shared object. This has been fixed so that code can be generated once and then replayed with many different recorded protocol files so long as the schema is the same.



CR:651015
CR Number:   651015
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)
12.0.1 3125 07 Dec 2010 Fixed
12.0.0 2520 07 Dec 2010 Fixed
Description
When executing an "INSTALL JAVA [NEW | UPDATE] JAR" statement with a compressed jar file, there was a very small chance that some of the classes or resources within the jar would have been installed incorrectly. This problem has now been fixed.



CR:651029
CR Number:   651029
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3125 07 Dec 2010 Fixed
12.0.0 2620 07 Dec 2010 Fixed
11.0.1 2534 07 Dec 2010 Fixed
10.0.1 4158 07 Dec 2010 Fixed
Description
On Linux builds where the kernel was compiled to support something other than 1024 processors, the database server could have failed to detect the correct processor geometry and could have crashed. This problem has been fixed. Note that recent Linux kernels have been built with support for up to 4096 processors.



CR:651040
CR Number:   651040
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)
12.0.1 3126 07 Dec 2010 Fixed
12.0.0 2621 10 Dec 2010 Fixed
Description
When executing VALIDATE TABLE and VALIDATE INDEX statements, thay may not have used as much CPU parallelism as they could have. This problem has been fixed.



CR:651047
CR Number:   651047
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)
12.0.1 3125 08 Dec 2010 Fixed
12.0.0 2620 08 Dec 2010 Fixed
Description
In some cases, execution of parallel plans on machines with large number of cores

could be poor when dynamic adjustment of the multiprogramming level is enabled. This has been fixed.



CR:651104
CR Number:   651104
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3132 21 Dec 2010 Fixed
12.0.0 2623 21 Dec 2010 Fixed
11.0.1 2644 21 Jul 2011 Fixed
Description
When a table contained NOT NULL columns, particularly with interspersed primary key and LONG (clob/blob) columns, rows may have become corrupted. This may have resulted in rows not being uploaded properly, values read as the wrong column, or ArrayIndexOutOfBounds error, when reading LONG values. This has been fixed.



CR:651169
CR Number:   651169
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)
12.0.1 3262 13 Dec 2010 Fixed
12.0.0 2622 13 Dec 2010 Fixed
11.0.1 2535 13 Dec 2010 Fixed
Description
If a database containing a table with a uniqueidentifier column was unloaded using the Unload utility (dbunload) with one of the external unload options (-xi or -xx), and the resulting reload.sql script was executed using the Interactive SQL utility, a conversion error would have been reported. This has been fixed. A workaround is to avoid using -xx or -xi when rebuilding the database.



CR:651294
CR Number:   651294
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3267 22 Dec 2010 Fixed
12.0.0 2626 22 Dec 2010 Fixed
Description
When starting a 32-bit server with a large initial number of request tasks (-gn option), the server could have failed to start by reporting an error, crashing or quietly exiting. This problem has been fixed by reducing the maximum cache size to accommodate the address space needed for the stacks of the request tasks.



CR:651323
CR Number:   651323
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)
12.0.1 3262 10 Dec 2010 Fixed
12.0.0 2621 10 Dec 2010 Fixed
Description
When the distance between two ST_Points exceeded the spatial reference system's tolerance by at least a factor of 1, but less than a factor of sqrt(2), the spatial relations ST_Equals and ST_Intersects could have incorrectly returned TRUE. This has been fixed.



CR:651344
CR Number:   651344
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)
12.0.1 3127 10 Dec 2010 Fixed
12.0.0 2621 10 Dec 2010 Fixed
Description
When running the server in 'in-memory' / 'no-writes' mode (-im nw), the CREATE DBSPACE statement would have created a file in the filesystem, rather than just emulating one inside the database server. Other than the creation of the physical file, all writes to it were emulated in memory. This has been corrected so that the server no longer creates the dbspace file on disk.



CR:651363
CR Number:   651363
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3127 10 Dec 2010 Fixed
Description
When a client interface could not load the language resource DLL on Windows, a message box was displayed showing the error message. This behaviour has been changed so that the message box is no longer displayed, since it could interfere with unattended systems. Instead, each client library will relay the information to its caller via appropriate methods, and dblib will set the error in the SQLCA to SQLSTATE_FAILED_TO_CREATE_STREAMS_ENV.



CR:651373
CR Number:   651373
Product Name:   UltraLiteJ
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3127 10 Dec 2010 Fixed
12.0.0 2621 10 Dec 2010 Fixed
Description
Using the UltraLiteJ Database Transfer Utility to transfer a database from the simulator or a device to the desktop through HTTP, would have failed. Also, the device application would not have properly canceled a transfer. This has been fixed.



Note, both desktop and device side applications must be updated simultaneously.



CR:651375
CR Number:   651375
Product Name:   MobiLink
Product Component:   MobiLink Agent
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3133 15 Dec 2010 Fixed
12.0.0 2623 15 Dec 2010 Fixed
Description
With a Microsoft SQL Server consolidated, MobiLink client synchronizations may have failed after making schema changes. The MobiLink synchronization log would have shown SQL Server error #16954. When using SQL Server tracing, an additional error #156 (syntax error) could have been seen. The cause appears to be a bug in SQL Server 2005, but has not been seen on SQL Server 2008. This has now been fixed.



To patch an existing MobiLink system setup:

1. Shut down the MobiLink servers

2. execute the SQL in %SQLANY12%\MobiLink\Setup\syncmss_ebf.sql



The patch only updates stored procedures, no data will be disturbed by this script. MobiLink systems setup after installing this fix do not need the patch to be applied.



CR:651383
CR Number:   651383
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3266 04 Jan 2011 Fixed
12.0.0 2626 04 Jan 2011 Fixed
11.0.1 2539 04 Jan 2011 Fixed
10.0.1 4163 04 Jan 2011 Fixed
9.0.2 3998 04 Jan 2011 Fixed
Description
As of the changes for Engineering case 633120, a SQL query producing multiple result sets was not handled correctly by the SQL Anywhere OLE DB provider. This problem has now been corrected. The cursor is no longer closed after the first result set is processed.



CR:651491
CR Number:   651491
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3128 13 Dec 2010 Fixed
12.0.0 2622 13 Dec 2010 Fixed
11.0.1 2535 13 Dec 2010 Fixed
10.0.1 4159 13 Dec 2010 Fixed
Description
Typing Ctrl-Z in an unmodified editor would have marked it as modified. This has been fixed.



CR:651508
CR Number:   651508
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3128 10 Dec 2010 Fixed
12.0.0 2622 10 Dec 2010 Fixed
Description
If an invalid combination of TCP protocol options was specified (eg. DoBroadcast=DIRECT but no HOST=) in a connection string, the client application could have crashed. This would only have happened on Unix systems. This has been fixed.



CR:651510
CR Number:   651510
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3128 10 Dec 2010 Fixed
12.0.0 2622 10 Dec 2010 Fixed
11.0.1 2535 10 Dec 2010 Fixed
Description
Execution of the utility SetupVSPackage, would have shown an error: "Object reference not set to an instance of an object." if machine.config file did not have the entry <DbProviderFactories>. This problem has been fixed.



CR:651520
CR Number:   651520
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   6.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3264 15 Dec 2010 Fixed
12.0.0 2623 15 Dec 2010 Fixed
11.0.1 2537 15 Dec 2010 Fixed
10.0.1 4161 15 Dec 2010 Fixed
Description
Displaying the results of an Index Consultant run of a large workload could have required an excessive amount of memory, causing Sybase Central to crash if there was not enough physical memory available. This has been fixed.



CR:651656
CR Number:   651656
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)
12.0.1 3132 13 Dec 2010 Fixed
12.0.0 2623 13 Dec 2010 Failed
Description
In some cases, setting a SQL Remote option could cause a server crash. This has been fixed.



CR:651658
CR Number:   651658
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)
12.0.1 3263 14 Dec 2010 Fixed
12.0.0 2623 14 Dec 2010 Fixed
11.0.1 2536 14 Dec 2010 Fixed
Description
On Windows systems, SQL Anywhere provides a version 1 (registry) performance provider. Windows should generate WMI classes automatically after the counter dll is registered, but these classes were generated only after instances of these objects (i.e. server, database and connection) existed in a process running in session 0 (i.e. as a service in Vista and up). This has been fixed.



CR:651692
CR Number:   651692
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3263 13 Dec 2010 Fixed
12.0.0 2623 13 Dec 2010 Fixed
Description
When a plug-in failed to load on startup, other plug-ins may then not work correctly. This has been fixed.



CR:651694
CR Number:   651694
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)
12.0.1 3265 20 Dec 2010 Fixed
12.0.0 2625 20 Dec 2010 Fixed
11.0.1 2538 20 Dec 2010 Fixed
10.0.1 4162 20 Dec 2010 Fixed
Description
If the connections between servers in a mirroring system used encryption, the primary server could have hung when performing an operation which required exclusive access to the database (e.g. a checkpoint) if other update activity was also occurring. This has been fixed.



CR:651707
CR Number:   651707
Product Name:   SQL Anywhere
Product Component:   SNMP Extension Agent
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3133 14 Dec 2010 Fixed
12.0.0 2623 14 Dec 2010 Fixed
11.0.1 2537 14 Dec 2010 Fixed
10.0.2 4161 14 Dec 2010 Fixed
Description
The iAnywhere.mib file that shipped with the SNMP agent was not SMI compliant. This has been fixed.

Note that this change did not affect the software itself.



CR:651723
CR Number:   651723
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3262 15 Dec 2010 Fixed
12.0.0 2623 15 Dec 2010 Fixed
Description
Opening a column's Property sheet would have caused the error: "Support for spatial is not available for this CPU", when the server was run on a system with on a Pentium III processor. The same error would also have occurred in the Function and Domain wizards, and the Spatial Reference Systems folder if it was selected in the tree. These issues have been fixed.



CR:651729
CR Number:   651729
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)
12.0.1 3127 14 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
11.0.1 2536 14 Dec 2010 Fixed
10.0.1 4160 14 Dec 2010 Fixed
Description
In some rare cases, the server may have hung if diagnostic tracing had been enabled. This has been fixed.



CR:651846
CR Number:   651846
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)
12.0.1 3264 14 Dec 2010 Fixed
12.0.0 2623 14 Dec 2010 Fixed
11.0.1 2537 14 Dec 2010 Fixed
Description
On Windows systems, the performance monitor might not have displayed counter values provided by the server. Typically this would have happened when a shared memory client that was attached to the server terminated abnormally. Counter values should not display for subsequent servers until all processes holding handles to the dead server (e.g. shared memory clients) are terminated. This has been fixed.



CR:651880
CR Number:   651880
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3133 15 Dec 2010 Fixed
12.0.0 2623 15 Dec 2010 Fixed
11.0.1 2537 15 Dec 2010 Fixed
Description
The reply-to address for messages originating from a Weblogic 10.3 JMS server were formatted in such a way that they could not have been resolved by the JMS connector. This has been fixed.



CR:652034
CR Number:   652034
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3135 16 Dec 2010 Fixed
12.0.0 2624 16 Dec 2010 Fixed
Description
When analyzing an Application Profiling or Diagnostic trace, the Application Profiling wizard may have recommended changing the -gn setting, even though this no longer applies to version 12 servers. This has been fixed.



CR:652037
CR Number:   652037
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
11.0.1 2538 17 Dec 2010 Fixed
Description
The Unload utility (dbunload) could have crashed when attempting to unload a database into an existing database. A crash would have occurred when a data-only unload (-d) was being done, and a user or table in the source database did not exist in the destination database. If the unload was done through the Sybase Central Unload wizard, the wizard would have crashed. This has been fixed.



CR:652075
CR Number:   652075
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3135 16 Dec 2010 Fixed
12.0.0 2624 16 Dec 2010 Fixed
11.0.1 2537 16 Dec 2010 Fixed
Description
The changes made for Engineering case 644855, to correct a crashing problem when the Windows desktop appearance was changed, caused fonts to not render properly in the result set table. Some characters could have been displayed as boxes in the column headers for result sets. This has been fixed.



CR:652107
CR Number:   652107
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)
12.0.1 3264 16 Dec 2010 Fixed
12.0.0 2624 16 Dec 2010 Fixed
11.0.1 2537 16 Dec 2010 Fixed
10.0.1 4162 16 Dec 2010 Fixed
Description
If a foreign key had both ON UPDATE and ON DELETE actions, renaming a column referenced by the foreign key could have caused one of the system triggers to be deleted and the other to be left unchanged. A trigger for an ON UPDATE action could have been converted to an ON DELETE action. This has been fixed.



CR:652131
CR Number:   652131
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
Description
Sybase Central could have failed to find the results of a search when editing an object in the right pane, if "Cancel" was clicked when asked to save changes before showing the search result. This has been fixed.



CR:652188
CR Number:   652188
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3265 16 Dec 2010 Fixed
12.0.0 2624 16 Dec 2010 Fixed
11.0.1 2538 16 Dec 2010 Fixed
10.0.1 4162 16 Dec 2010 Fixed
Description
When a table was selected in the tree and the Indexes tab was shown in the right pane, there was no File -> New -> Index... menu item. As such, it was only possible to start the Index wizard from the toolbar button. This has been fixed.



CR:652201
CR Number:   652201
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
Description
The HOST connection parameter is usually of the form host:port, but can also contain a comma separated list of host and port pairs. The ODBC driver usually splits the HOST connection parameter and displays it in the Administrator as two text fields labeled host and port. When it was a list of values, it was incorrectly splitting it at the first colon. This has been fixed.



CR:652202
CR Number:   652202
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
Description
When editing an "Execute SQL" command in a remote task, the caret could have been displayed in the wrong position if the text contained tab characters. This has been fixed.



CR:652211
CR Number:   652211
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 16 Dec 2010 Fixed
12.0.0 2624 16 Dec 2010 Fixed
Description
In dialogs, components are often labelled with text that has a mnemonic, shown with an underlined letter. It is permissible for two components to have the same mnemonic. In that case, pressing ALT and the mnemonic should move the focus to the next component which has the given mnemonic. This moving of the focus was broken if the component which currently had the focus was an editable combobox. This problem was surfacing in the Connect dialog used by the admin tools when starting a database on another computer. The "i" mnemonic is shared by the "Database file" field and the "Find" button. When the "Database file" field had focus, pressing ALT+I did not move focus to the "Find" button. This has been fixed so that now it does.



CR:652220
CR Number:   652220
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)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
Description
The server could have hung in some very rare circumstances when there was considerable temporary file growth. This has been fixed.



A workaround is to pre-grow the temporary file using the ALTER DBSPACE statement, or by creating a DiskSpace event to periodically grow the temporary file.



The same issue was fixed for earlier version by Engineering case 580773.



CR:652221
CR Number:   652221
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)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
11.0.1 2538 17 Dec 2010 Fixed
Description
In some cases, calling a web services stored procedure may have crashed the server. This has been fixed.



CR:652243
CR Number:   652243
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)
12.0.1 3137 17 Dec 2010 Fixed
12.0.0 2625 17 Dec 2010 Fixed
11.0.1 2538 17 Dec 2010 Fixed
Description
MobiLink clients using persistent HTTP 1.0 connections may fail occasionally when using the Relay Server. The failure was isolated to synchronizations that ran into a rare timing problem. This has been corrected.



CR:652244
CR Number:   652244
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)
12.0.1 3295 21 Jan 2011 Fixed
Description
An internal unload/reload (i.e. dbunload -ii) that encountered a SQL error could have hung or caused a subsequent unload/reload on the same server to hang. This problem has been fixed.



CR:652247
CR Number:   652247
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
Description
The title line of the usage screen for the MobiLink Agent stop utility (mlastop) may have contained an untranslated character. This has been fixed.



CR:652248
CR Number:   652248
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)
12.0.1 3141 17 Dec 2010 Fixed
12.0.0 2626 17 Dec 2010 Fixed
11.0.1 2540 17 Dec 2010 Fixed
Description
Clicking 'Apply' on the Auditing tab filter pane, could have thrown an exception causing Sybase Central to crash. This has been fixed.



CR:652249
CR Number:   652249
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3136 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
11.0.1 2538 17 Dec 2010 Fixed
Description
The title line of the usage screen for the QAnywhere Stop utility (qastop) may have contained an untranslated character. This has been fixed.



CR:652253
CR Number:   652253
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 2538 17 Dec 2010 Fixed
10.0.1 4162 17 Dec 2010 Fixed
Description
In some rare cases, when run on HP, AIX, and Solaris systems the server may have crashed on shutdown. This has been fixed.



CR:652263
CR Number:   652263
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3265 17 Dec 2010 Fixed
12.0.0 2624 17 Dec 2010 Fixed
11.0.1 2538 17 Dec 2010 Fixed
Description
The usage text for the Relay Server Outbound Enabler didn't describe what were the valid options for the -cr option. This has been corrected so that the values are now listed for the tcp options, server certificate options, and client certificate options.



In addition, http authentication options, proxy options, and proxy authentication options, have been added in version 12.0.1.



CR:652382
CR Number:   652382
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)
12.0.1 3267 20 Dec 2010 Fixed
12.0.0 2627 20 Dec 2010 Fixed
11.0.1 2540 20 Dec 2010 Fixed
Description
The Relay Server did not work with a Relay Server Outbound Enabler (RSOE) that was behind an HTTP 1.0 proxy. The Relay Server has now been fixed to adapt to HTTP version downgrades done by an HTTP 1.0 proxy, and is needed when working with a 12.0.1 RSOE in conjunction with a HTTP 1.0 proxy.



CR:652411
CR Number:   652411
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3137 20 Dec 2010 Fixed
12.0.0 2625 20 Dec 2010 Fixed
11.0.1 2538 20 Dec 2010 Fixed
10.0.1 4162 20 Dec 2010 Fixed
Description
If an error occurred accessing the tape drive when beginning a tape backup, the BACKUP statement may have hung. This has been fixed.



CR:652543
CR Number:   652543
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)
12.0.1 3266 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
11.0.1 2539 21 Dec 2010 Fixed
10.0.1 4163 21 Dec 2010 Fixed
11.0.0 1654 21 Dec 2010 Fixed
Description
The server may have crashed during inserts into a view, if the view column was not a base table column. This has been fixed. Now the correct error SQLSTATE_NON_UPDATEABLE_VIEW is returned.



CR:652547
CR Number:   652547
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3266 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
11.0.1 2539 21 Dec 2010 Fixed
10.0.1 4163 21 Dec 2010 Fixed
Description
Altering the schedule for an event to remove a days-of-month specification did not set SYSSCHEDULE.days_of_month to null. This has been fixed.



CR:652577
CR Number:   652577
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)
12.0.1 3266 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
11.0.1 2539 21 Dec 2010 Fixed
10.0.1 4163 21 Dec 2010 Fixed
Description
Sybase Central could have crashed while the property sheet for a client message store was open, if adding a new property was started, but then the action was cancelled. This has been fixed.



CR:652587
CR Number:   652587
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)
12.0.1 3266 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
Description
When running a database without a transaction log, performance could have been significantly slower than in previous versions. This problem has been corrected. See Engineering case 608904 for a similar issue..



CR:652592
CR Number:   652592
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)
12.0.1 3268 04 Jan 2011 Fixed
12.0.0 2626 04 Jan 2011 Fixed
Description
Attempting to connect to a read-only scale-out database with a non-ASCII database name using the NODETYPE connection parameter could have incorrectly failed with a "Specified database not found" error. The database name was being sent back in either OS-charset or DB-charset, but the client needed it to be in client-charset. This has now been fixed.



CR:652609
CR Number:   652609
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3141 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
11.0.1 2539 21 Dec 2010 Fixed
10.0.1 4164 21 Dec 2010 Fixed
Description
When using Oracle as a back-end database, synchronizations may have failed with the error ORA-08207. This has been fixed.



CR:652735
CR Number:   652735
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)
12.0.1 3141 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
11.0.1 2540 21 Dec 2010 Fixed
Description
When a Relay Server shuts down, it notifies connected Relay Server Outbound Enablers (RSOE) to perform an internal shutdown before the RSOE enters recovery mode. The RSOE also notifies the Relay Server via the down channel when the the RSOE shutdown is completed. The HTTP subsystem used on IIS7.5 prevented a Relay Server from receiving the shutdown notification reliably and in turn caused an unnecessary hard shutdown of the Relay Server after a 100 sec delay. This has been fixed so that the Relay Server now handles this case properly as a graceful soft shutdown without a delay.



CR:652739
CR Number:   652739
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3141 22 Dec 2010 Fixed
12.0.0 2626 22 Dec 2010 Fixed
11.0.1 2540 22 Dec 2010 Fixed
10.0.1 4164 22 Dec 2010 Fixed
Description
If an application prepared a batch insert using the SQL Anywhere JDBC driver, and the last row in the batch involved a call to setNull() and the datatype passed to setNull() was different than the previous set of setX calls for that column, then there was a chance the JDBC driver would have inserted incorrect data. This problem has now been fixed.



For example, the following set of calls would have inserted incorrect data into the table test:



PreparedStatement pstmt = con.prepareStatement( "insert into test values(?,?)" );

pstmt.setInt(1, 1001);

pstmt.setString(2, "this is row #1" );

pstmt.addBatch();

pstmt.setInt(1, 2001);

pstmt.setString(2, "this is row #2" );

pstmt.addBatch();

pstmt.setInt(1, 3001);

pstmt.setString(2, "this is row #3" );

pstmt.addBatch();

// note the fact that we are switching datatypes below

pstmt.setNull(1, java.sql.Types.SMALLINT);

pstmt.setString(2, "this is row #4" );

pstmt.addBatch();

pstmt.executeBatch();



Again, note that this problem would not have occurred if instead of using java.sql.Types.SMALLINT, the application instead used java.sql.Types.INTEGER. In addition, if the call to setNull() was not in the last row of the batch, then again this problem would not have occurred, even if the application switched datatypes for the setNull() call.



CR:652752
CR Number:   652752
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3267 22 Dec 2010 Fixed
12.0.0 2626 22 Dec 2010 Fixed
Description
When starting dbisqlc, or an ODBC application with a connection string containing LINKS=TCPIP, if there is an error connecting the connection dialog is displayed. It was incorrectly defaulting to "connect to a running database on another computer", losing the LINKS=TCPIP setting. If TCP parameters were specified, such as LINKS=TCPIP(PORT=2638), then it worked correctly. This has now been fixed.



CR:652756
CR Number:   652756
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)
12.0.1 3267 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
Description
When validating a table that contained spatial data on 32-bit x86 systems where the processor did not support the SSE2 instruction set (the minimum required for SA spatial features), the database server would have reported a non-fatal assertion error

113300 or 113302 "failed to build cursor to validate". This problem has been fixed and the underlying error is now reported: SQL error (-1515) -- Support for spatial is not available for this CPU.



CR:652759
CR Number:   652759
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)
12.0.1 3267 21 Dec 2010 Fixed
12.0.0 2626 21 Dec 2010 Fixed
Description
If a table was included in a MobiLink publication and one or more options were defined for that publication, but there were no synchronization subscriptions defined, the table could not be ALTERed to, for example, add a new column. This has been fixed.



CR:652791
CR Number:   652791
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)
12.0.1 3267 22 Dec 2010 Fixed
12.0.0 2627 22 Dec 2010 Fixed
11.0.1 2540 22 Dec 2010 Fixed
10.0.1 4164 22 Dec 2010 Fixed
Description
If a statement for a directory access table failed with the error SQLSTATE_OMNI_REMOTE_ERROR, and this statement was the last statement of the transaction then all subsequent remote server statements of this connection would have failed with the same error. This has been fixed.



CR:652911
CR Number:   652911
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3270 05 Jan 2011 Fixed
12.0.0 2629 05 Jan 2011 Fixed
11.0.1 2542 05 Jan 2011 Fixed
10.0.1 4166 05 Jan 2011 Fixed
Description
If an INSTALL JAVA UPDATE statement was executed to update an existing java class, the server would have incorrectly added a new system object id rather than reuse the already assigned object id. This problem has now been fixed.



CR:652920
CR Number:   652920
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3143 23 Dec 2010 Fixed
12.0.0 2627 23 Dec 2010 Fixed
11.0.1 2541 23 Dec 2010 Fixed
Description
A NullPointException was possible when executing an UPDATE statement when nothing was updated. This was corrected.



CR:652949
CR Number:   652949
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)
12.0.1 3295 25 Feb 2011 Fixed
12.0.0 2651 25 Feb 2011 Fixed
11.0.1 2567 25 Feb 2011 Fixed
Description
The trigger operation condition 'UPDATE( {column-name} )' did not return TRUE if the column value had been changed by a previously running BEFORE UPDATE row-level trigger only. This has been fixed.



CR:652975
CR Number:   652975
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2555 31 Jan 2011 Fixed
Description
A NullPointerException was possible with large temporary tables and row limitation. This was corrected.



CR:653052
CR Number:   653052
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3144 04 Jan 2011 Fixed
12.0.0 2628 04 Jan 2011 Fixed
11.0.1 2541 04 Jan 2011 Fixed
10.0.1 4165 04 Jan 2011 Fixed
Description
Using the system procedure xp_sendmail with an attachment larger than about 55 kB may have resulted in the attachment being corrupted. This has been fixed.
Workaround Description
 Summary: work-around would be to send a multipart/mixed email and attach an base64 encoded file





Environment:

Windows XP SP3

Lotus Notes 8.5

SQL Anywhere 10.0.1.4157







5.) Test: attach base64 encoded file to a multipart/mixed email

- create new database, using command: dbinit qqq

- start new database, using command: dbsrv10 qqq

- create new file "prepare5.sql" (see below)

- run script in database, using command: dbisql -c dba,sql prepare5.sql

- create pdf file that should be send, using command: COPY "%SQLANY10%\ThirdPartyLegal\SQLAnywhere10ThirdPartyLegal.pdf" sample.pdf

- send email, using command: dbisql -c dba,sql CALL email_pdf ( '<STMP server>', '<senders email address>', '<recipient email address>' )

NOTE: I had been using our standard email server to send myself the test email, using command: dbisql -c dba,sql CALL email_pdf ( 'euromail4.sybase.com', 'dlauter@sybase.com', 'dlauter@sybase.com' )

- check Inbox

=> new email with the subject "sample.pdf attached to email (work-around)" received, having file "sample.pdf" attached to it

- compare the original sample.pdf with the received one

=> identical







=== prepare5.sql ===

CREATE PROCEDURE email_pdf ( IN email_server CHAR(256), IN email_sender CHAR(256), IN email_recipient CHAR(256) )

BEGIN

DECLARE content LONG VARCHAR;

call xp_startsmtp( email_sender, email_server );

set content = 'Content-Type: multipart/mixed; boundary="xxxxx";\n';

set content = content || 'This part of the email should not be shown. If this is shown then the email client is not MIME compatible\n\n';

set content = content || '--xxxxx\n';

set content = content || 'Content-Type: text/html;\n';

set content = content || 'Content-Disposition: inline;\n\n';

set content = content || 'Test\n\n';

set content = content || '--xxxxx\n';

set content = content || 'Content-Type: application/pdf; name="sample.pdf"\n';

set content = content || 'Content-Transfer-Encoding: base64\n';

set content = content || 'Content-Disposition: attachment; filename="sample.pdf"\n\n';

set content = content || base64_encode( xp_read_file( 'sample.pdf' ) ) || '\n\n';

set content = content || '--xxxxx--\n';

call xp_sendmail( recipient=email_recipient,

subject='sample.pdf attached to email (work-around)',

"message"=content,

content_type = 'ASIS' );

call xp_stopsmtp();

END





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------