远程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:440231
CR Number:   440231
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2932 24 Aug 2006 Fixed
10.0.0 2452 24 Aug 2006 Fixed
9.0.2 3364 24 Aug 2006 Fixed
Description
When executing a FOR statement, where the CURSOR USING clause referenced a variable, the server would have crashed with a SIGBUS on platforms that enforce alignment, such as Solaris/SPARC. This problem has been fixed.



CR:440234
CR Number:   440234
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2938 28 Aug 2006 Fixed
10.0.0 2697 28 Aug 2006 Fixed
9.0.2 3369 28 Aug 2006 Fixed
Description
UltraLite Dynamic SQL could have generated incorrect results, and could have possibly raised an exception, when there were host variables in the select list for a query and temporary tables were required. This has been fixed.



CR:440245
CR Number:   440245
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2932 23 Aug 2006 Fixed
10.0.0 2697 23 Aug 2006 Fixed
9.0.2 3364 23 Aug 2006 Fixed
Description
In the "Export" dialog, when the "Browse" button was clicked and an existing file selected, the user was asked if they wanted to overwrite the file. This prompt has been removed, as the user is asked this anyway when they click the "Export" dialog's OK button.



CR:440246
CR Number:   440246
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3426 20 Dec 2006 Fixed
Description
ASA uses files for client-server shared memory communication. On Solaris systems, when free disk space was exhausted, attempts to allocate more shared memory was not being detected and raised as an error. Then, when either the client or the server accessed the memory, a BUS error would have occurred. This has been fixed, by added code to check free disk space whenever new shared memory is created on Solaris.



CR:440344
CR Number:   440344
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)
10.0.1 2933 24 Aug 2006 Fixed
10.0.0 2453 24 Aug 2006 Fixed
9.0.2 3364 24 Aug 2006 Fixed
Description
The performance of the ADO .Net 2.0 provider has been improved.



CR:440462
CR Number:   440462
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)
10.0.1 2934 24 Aug 2006 Fixed
10.0.0 2697 24 Aug 2006 Fixed
9.0.2 3366 24 Aug 2006 Fixed
Description
When executing a query that involved a remote table, and an aggregate whose argument was a concatenation with a user-defined function, the server would have failed with the error "syntax error near unknown", rather than successfully running the query. This has been fixed.



For example, the following would have generated the syntax error:

select min( cast( 'fred'||dba.NewID() as varchar(25) ) )

from remote_t

where remote_t is a proxy table and NewID() is a user-defined function.



CR:440465
CR Number:   440465
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3366 24 Aug 2006 Fixed
Description
Attempting to upgrade a database created with software that is newer than version 6.0.2, and older than version 8.0.0, where the public setting for the Date_order option had been changed, would have failed with a conversion error. This problem has now been fixed.



CR:440689
CR Number:   440689
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)
10.0.1 2938 29 Aug 2006 Fixed
10.0.0 2697 29 Aug 2006 Fixed
9.0.2 3367 29 Aug 2006 Fixed
Description
Executing a remote query that contains a derived table which is a UNION, would very likely have crashed the server. When analyzing the query and attempting to determine the server id of the derived table, the server was assuming that the derived table was always a simple select. The server now properly handles the case where the derived table is a UNION, INTERSECT or EXCEPT.



CR:440702
CR Number:   440702
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2938 29 Aug 2006 Fixed
10.0.0 2697 29 Aug 2006 Fixed
Description
Changing the refresh rates of the various viewers in DBConsole had no affect on how often the viewers actually refresh. This has been corrected



CR:440704
CR Number:   440704
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2938 29 Aug 2006 Fixed
10.0.0 2457 29 Aug 2006 Fixed
9.0.2 3367 29 Aug 2006 Fixed
Description
If the ODBC function SQLBindParameter was called for a SQL_WCHAR with an odd BufferLength and a NULL StrLen_or_IndPtr value, the driver would have returned an errror with SQL state "HY090". The problem has been corrected.



CR:440709
CR Number:   440709
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2940 31 Aug 2006 Fixed
10.0.0 2460 31 Aug 2006 Fixed
9.0.2 3369 31 Aug 2006 Fixed
8.0.3 5435 31 Aug 2006 Fixed
Description
When using the OLEDB provider to read values from a varchar( n ) column, using the .NET DataReader, the last character was truncated if the column contained exactly n characters. This problem has been fixed.



CR:440783
CR Number:   440783
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2939 29 Aug 2006 Fixed
10.0.0 2697 29 Aug 2006 Fixed
9.0.2 3368 29 Aug 2006 Fixed
Description
It was possible for connections with communication compression enabled to get communication errors. The problem was timing dependent, thus would have been rare, and could have occurred if the data being transferred had poor compression rates. This has been now been fixed.



CR:440811
CR Number:   440811
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)
10.0.1 2939 29 Aug 2006 Fixed
10.0.0 2697 29 Aug 2006 Fixed
Description
The properties 'disable new connections' and 'remember last statement' were not being restored correctly in the Console utility's options pane. This has been fixed.



CR:440903
CR Number:   440903
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3266 03 Oct 2006 Fixed
10.0.0 2716 03 Oct 2006 Fixed
9.0.2 3383 03 Oct 2006 Fixed
Description
If a table was defined with a trigger that fired for more than one type of event (e.g. INSERT and UPDATE) ,while unlikely, a server crash could have occurred if operations were being performed on the table while another connection was performing a DDL statement. This has been fixed.



CR:440930
CR Number:   440930
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3278 31 Oct 2006 Fixed
10.0.0 2744 31 Oct 2006 Fixed
9.0.2 3396 31 Oct 2006 Fixed
Description
The database server could have crashed with a "memory exhausted" error. One of the symptoms leading up to thecrash would have been increased disk read activity by the server, although this is not always the case. This was due to cache pages becoming unavailable for use. This could occur on machines with 2 or more processors, but was more likely to happen on machines with 4 or more processors. This issue has been fixed.



CR:441010
CR Number:   441010
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 3369 31 Aug 2006 Fixed
Description
Executing a query that referenced a window function with a constant string argument could have caused the server to crash. This has been fixed.



CR:441110
CR Number:   441110
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2942 06 Sep 2006 Fixed
10.0.0 2697 06 Sep 2006 Fixed
9.0.2 3369 06 Sep 2006 Fixed
9.0.1 2195 10 Jan 2007 Fixed
Description
Interactive SQL could have reported:



"There was an error reading the results of the SQL statement.

The displayed results may be incorrect or incomplete."



when attempting to display a result set which contained numeric data that was undisplayable. This error message has been replaced with the the textual representation of the value which is returned by the server. For example, the following statements now display a result set with one value ("?"), whereas previously, the result set column header and the error message above were displayed, with no values at all.



set temporary option precision='1';

set temporary option scale='0';

create variable v1 decimal;

create variable v2 decimal;

set v1=9;

set v2=9;

select v1*v2;



CR:441111
CR Number:   441111
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2942 08 Sep 2006 Fixed
10.0.0 2697 05 Sep 2006 Fixed
Description
Attempting to open the Connected User property sheet, while connected only to the utility_db, would have caused a "permission denied" error. The plug-in was calling dbo.sa_conn_properties() function, which is not supported for utility_db connections. This has been fixed, now the Extended Information page will display "You cannot view the Extended Information for this connection because you are only connected to the utility database."



CR:441243
CR Number:   441243
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2944 06 Sep 2006 Fixed
10.0.0 2462 06 Sep 2006 Fixed
9.0.2 3370 06 Sep 2006 Fixed
Description
Some carriers are injecting control characters in their SMS message. When this is done at the end of the message, the MobiLink Listener that received the message may have reported protocol mismatch errors, and discarded the message. This has been fixed by removing all control characters in SMS messages.



CR:441248
CR Number:   441248
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2946 05 Sep 2006 Fixed
10.0.0 2946 05 Sep 2006 Fixed
Description
When using the UltraLite Engine runtime (ULDatabaseManager.RuntimeType = ULRuntimeType.UL_ENGINE_CLIENT), the ULFileTransfer.DownloadFile() methods may have failed with a MissingMethodException. Under the 2.0 Compact Framework, the exception would have been: "Can't find PInvoke DLL 'ulnet10.dll'." This has been fixed.



A work around is to create an instance of a ULConnection class before invoking DownloadFile().



For example:

// C#

ULConnection xxx = new ULConnection();

// If the compiler complains that xxx is never used, add the do nothing code below

if( xxx.State = ConnectionState.Open ) {

// will never happen

throw new OutOfMemoryException();

}



CR:441260
CR Number:   441260
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3381 03 Oct 2006 Fixed
Description
If an INSERT ... FROM SELECT ... statement was used with the ON EXISTING SKIP/ERROR clause, and the table being inserted into contained default columns, then the server would have computed default values even for rows that already existed. As a consequence, default values, such as autoincrement, were calculated even for skipped rows resulting in skipped values in the autoincrement sequences. The server now does not compute default values for rows being skipped.



The behaviour is not going to be changed in 10.x and newer versions, as it is more consistent with what happens when the insert fails for a row that already exists, and the ON EXISTING clause was not specified. As an example, the following code will also cause autoincrement values to be skipped:



create table t1( c1 int primary key, c2 int default autoincrement );

insert into t1(c1) values(1);

insert into t1(c1) values(1);

insert into t1(c1) values(2);



The values inserted for the example above are:



1,1

1,3



CR:441267
CR Number:   441267
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3371 06 Sep 2006 Fixed
Description
There was no iAnywhere.QAnywhere.Client assembly for .NET Framework 2.0 in SQL Anywhere 9.0.2. One has now been added.



CR:441275
CR Number:   441275
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2946 06 Sep 2006 Fixed
10.0.0 2697 06 Sep 2006 Fixed
9.0.2 3371 06 Sep 2006 Fixed
8.0.3 5437 06 Sep 2006 Fixed
Description
Attempting to make a connection to the database server at midnight, could have resulted in the error "Connection error: Found server but communication error occurred". The client software did not handle a date roll-over if a timeout was specified. This has been fixed.



CR:441329
CR Number:   441329
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)
10.0.1 2947 07 Sep 2006 Fixed
10.0.0 2697 07 Sep 2006 Fixed
Description
The server did not allow a conversion between the datetime and smallint data types. However, there were certain date values for which a conversion to smallint could succeed, for example, the statement:



select cast( cast( 'Jan 1 0001 12:00:00:000AM' as datetime ) as smallint )



should return the value 10101, but was failing with the error "cannot convert timestamp to a smallint". This issue has been fixed.





In a related issue, certain operations that should result in conversion errors were incorrectly succeeding. Consider the following script:



create table t1 (c1 char(1), c2 smallint)

go

create table t2 (c2 datetime)

go

insert into t1 values ('Y', 21)

go

insert into t2 values ('Jan 1 1995 12:00:00:000AM')

go

select c1 from t1 where c2 in (select c2 from t2)

go



It should fail with the error "ASA Error -157: Cannot convert 21 to a date", but was not. This has been fixed so that the appropriate error is generated.



CR:441350
CR Number:   441350
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)
10.0.1 2947 08 Sep 2006 Fixed
10.0.0 2697 08 Sep 2006 Fixed
Description
If a table was selected from the tree and a cell value was changed in the Table Editor on the Columns tab, and then another cell in the Table Editor was clicked on, then the Undo

menu item and toolbar button would not have been enabled until F2 was pressed, or the area outside the table editor was clicked. This has been fixed.



CR:441456
CR Number:   441456
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)
10.0.1 2947 07 Sep 2006 Fixed
10.0.0 2698 07 Sep 2006 Fixed
Description
If a synchronization model in the tree was selected, and then the model's file was deleted, pressing F5, or choosing View -> Refresh Folder, would have caused Sybase Central to show the same error dialog eight times and then crash. This has been fixed so that the error dialog is now displayed once.



CR:441458
CR Number:   441458
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)
10.0.1 2947 08 Sep 2006 Fixed
10.0.0 2698 08 Sep 2006 Fixed
Description
Selecting a synchronization model in the right-pane, and then choosing File -> Remove From List, would have caused Sybase Central to crash. This has been fixed.



Note that selecting the model in the tree would avoid this problem.



CR:441472
CR Number:   441472
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)
10.0.1 2947 07 Sep 2006 Fixed
10.0.0 2698 07 Sep 2006 Fixed
Description
Clicking a cell in the Table or Column Mapping Editor would sometimes have failed to open the corresponding drop-down list for the cell. Also, in some cases items in the drop-down list would have been clipped. Both of these issues have now been fixed.



CR:441489
CR Number:   441489
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)
10.0.1 2947 08 Sep 2006 Fixed
10.0.0 2698 08 Sep 2006 Fixed
Description
When using the New Table Mapping wizard to create new mappings for a synchronization model, it was possible for the model to contain two or more table mappings that referenced the same remote table. This has been fixed.



CR:441502
CR Number:   441502
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2948 08 Sep 2006 Fixed
10.0.0 2465 08 Sep 2006 Fixed
Description
If the ALTER TABLE statement was used to modify the domain of a column to an incompatible domain, the server could have crashed. For example, an attempt to convert the type of a column from time to bigint (a conversion that is not supported) would have causes a crash. The server will now, as expected, generate a conversion error.



CR:441560
CR Number:   441560
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Windows CE 2.11
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2955 15 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
9.0.2 3375 19 Sep 2006 Fixed
Description
An application compiled to the DBTools API, which includes most the ASA database tools including dbremote, dbmlsync and dbltm, could have reported an "Out of memory" error, even though there appeared to be free memory on the system where the error was reported. This has now been fixed.



CR:441562
CR Number:   441562
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2948 08 Sep 2006 Fixed
10.0.0 2699 08 Sep 2006 Fixed
9.0.2 3371 08 Sep 2006 Fixed
Description
It may have appeared that a lot of data was being sent from the server and the client, even when the client was not receiving messages. The problem occurred when using a consolidated database where the last_download and last_upload time granularity was large, typically in the one second range. Because the QAnywhere MobiLink server against an Oracle server only supports a one second granularity, it would typically have happened only with an Oracle consolidated database. The problem was that message synchronizations between the client and the server, that took less than the timestamp granularity, would have been interpreted as a failed sync by the next synchronization, resulting in data being re-downloaded to the client. This has been fixed by correcting for the timestamp granularity, so that re-downloading data to the client will no longer occur.



CR:441568
CR Number:   441568
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)
10.0.1 2948 08 Sep 2006 Fixed
10.0.0 2699 08 Sep 2006 Fixed
Description
Attempting to set the following options using the SET OPTION statement would have failed when connected to a database:



isql_show_multiple_result_sets

isql_print_result_set



This has been fixed.



CR:441583
CR Number:   441583
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)
10.0.1 2948 08 Sep 2006 Fixed
10.0.0 2699 08 Sep 2006 Fixed
Description
If a synchronization model was created that used a shadow table for storing last modification times and used logical deletes, then deployment would not have populated the shadow table with existing rows, which would have caused no rows to be returned for the first download. This has been fixed.



A workaround is to deploy to a file only for the consolidated, and in the resulting SQL file change the WHERE clause in the INSERT INTO statement that follows the CREATE TABLE statement for the shadow table, so that it excludes deleted rows. If the defaults are used, this would involve changing 'Y' to 'N'.



CR:441585
CR Number:   441585
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)
10.0.1 2947 08 Sep 2006 Fixed
10.0.0 2697 08 Sep 2006 Fixed
Description
If a synchronization model was selected in the tree and a cell value was changed in the Table Mapping Editor or Column Mapping Editor on the Mappings tab, then the Undo

menu item and toolbar button would not have been enabled until F2 was pressed, or the area outside the Mapping Editor was clicked. This has been fixed.



CR:441606
CR Number:   441606
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)
10.0.1 2948 11 Sep 2006 Fixed
Description
On the Download Subset Details tab for a table mapping, it was possible to specify the "Table to join:" to be the same table as the table mapping's consolidated table, which would have caused a script generation error. This has been fixed so that now an error message is displayed and the problem must be corrected before proceeding.



CR:441618
CR Number:   441618
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)
10.0.1 2948 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
Description
When attempting to revert all changes to a synchronization model, if there was invalid input (that is, something that would cause a validation error when attempting to save the model) on the Mappings, Events, Authentication or Notification tab, reverting the model would have failed and the validation error would have been displayed. This has been

fixed.



CR:441663
CR Number:   441663
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)
10.0.0 2699 11 Sep 2006 Fixed
10.0.1 2951 11 Sep 2006 Fixed
Description
The Interactive SQL utility could have reported an internal exception, if it was run in a language other than English, when attempting to open or import a file which it could not interpret. This error would most likely have occured when attempting to open a binary file, or a text file which was encoded using a codepage not supported by the computer. This has been fixed.



CR:441669
CR Number:   441669
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)
10.0.0 2699 11 Sep 2006 Fixed
10.0.1 2951 11 Sep 2006 Fixed
Description
If a procedure with a NO RESULT SET clause returned a result set, an error may not have been generated. This has been fixed so that an error is now generated in this case.



CR:441675
CR Number:   441675
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3264 29 Sep 2006 Fixed
10.0.0 2712 29 Sep 2006 Fixed
9.0.2 3382 29 Sep 2006 Fixed
Description
Runing an NUnit test case repeatedly when connection pooling was enabled, could have caused a System.AccessViolationException unhandled exception. This problem has been fixed.



CR:441677
CR Number:   441677
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)
10.0.1 2951 18 Sep 2006 Fixed
10.0.0 2465 18 Sep 2006 Fixed
9.0.2 3373 18 Sep 2006 Fixed
Description
If a fatal error was encountered when starting a network listener thread, and the server may have crashed as it was shutting down. This problem has been fixed.



Note, this would only have occurred with servers running on Unix platforms.



CR:441680
CR Number:   441680
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)
10.0.1 2951 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
Description
Attempting to open a .QAA or .QAR file, which could not be read (because the file was deleted outside of Sybase Central after it had been started, for example), would not have removed the file from the "Agent Files" container. As well, attempting to open a .QAR file which could not be read, would not have given an error message, and may have opened a window containing the file's contents. These two problems have now been fixed.



CR:441754
CR Number:   441754
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2952 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
9.0.2 3374 18 Sep 2006 Fixed
9.0.1 2180 18 Sep 2006 Fixed
8.0.3 5440 18 Sep 2006 Fixed
Description
The keyword "REAL" was not supported in the Data Type column of the table editor. The workaround was to use the keyword "FLOAT" instead. This has been fixed.



CR:441772
CR Number:   441772
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 10 Oct 2006 Fixed
10.0.0 2735 10 Oct 2006 Fixed
Description
When rebuilding databases from previous versions to version 10 on Unix systems, the variables SATMP and ASTMP must both have been set to the same directory, or not have been set at all, otherwise the Unload utility would have displayed an error that it could not connect to the database. This restriction has now been removed



CR:441784
CR Number:   441784
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)
10.0.1 2952 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
9.0.2 3374 19 Sep 2006 Fixed
Description
It was possible to call the system procedure sa_server_option with the option 'quitting_time' and set an invalid datetime parameter. This has been fixed.



CR:441791
CR Number:   441791
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2952 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
Description
If an application called setNull() with the type id set to NCHAR, NVARCHAR or NLONGVARCHAR, then the iAnywhere JDBC Driver would returned a "type id unknown" error. This problem has been fixed.



CR:441798
CR Number:   441798
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)
10.0.1 2952 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
Description
If the server was shut down while a connection had a cursor open on a java stored procedure that returned a result set, it was very likely that the server would have hung or crashed. This problem has been fixed.



CR:441804
CR Number:   441804
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)
10.0.1 2959 21 Sep 2006 Fixed
10.0.0 2704 21 Sep 2006 Fixed
Description
A problem where the server could have become deadlocked and appear to be hung has been fixed. This was more likely to occur if persistent tables or indexes were being dropped or truncated.



CR:441815
CR Number:   441815
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)
10.0.1 2959 21 Sep 2006 Fixed
Description
The server tracks dependencies between views and other database objects. A view is said to be dependent upon another object if the view makes a reference to the object. When the REVOKE CONNECT statement is executed to drop a user, all objects owned by the user are dropped along with the user. The REVOKE CONECT statement counld have failed erroneously if the database contained an active view that was dependent upon an object owned by the user being dropped. The intention was to disallow the REVOKE CONNECT if the dependent view was owned by a user different from the one being dropped. The user should be dropped without error in cases where the dependent view is also owned by the user being dropped. This has been fixed so that dependent views owned the user being dropped are now ignored when executing REVOKE CONNECT.



A work around is to first drop or disable views that depend on tables and views owned by the user being dropped. This process can be easily implemented in SQL by making use of the 'ALTER TABLE .. DISABLE VIEW DEPENDENCIES' and 'ALTER VIEW ... DISABLE' statements.



CR:441856
CR Number:   441856
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)
10.0.1 2953 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
Description
The Interactive SQL utility would have ignored the EXIT statement when running in non-windowed mode if not connected to a database. This has been fixed.



CR:441864
CR Number:   441864
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 2180 19 Sep 2006 Fixed
Description
Runaway QAnywhere client synchronizations could have caused massive logging on the MobiLink server. This has been fixed.



CR:441865
CR Number:   441865
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)
10.0.1 2953 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
Description
When opening the Users folder in for an UltraLite database, Sybase Central may have crashed, or displayed non-existent or duplicate users. This has been fixed.



CR:441874
CR Number:   441874
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2953 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
Description
The Log Translation utility, and the Translate Log File wizard in Sybase Central, could have failed if the temporary directory name was more than about 10 characters. This has been fixed.



CR:441946
CR Number:   441946
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)
10.0.1 2954 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
Description
Attempting to update a row in a table that another connection had locked by editing a result set, cound have made the Interactive SQL utility to become unresponsive. This has been fixed.



Note, this same problem also affected the "Data" tab in the SQL Anywhere plug-in for Sybase Central, and has been fixed as well.



CR:441970
CR Number:   441970
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2955 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
9.0.2 3375 18 Sep 2006 Fixed
Description
Attempting to perform an INSERT ... SELECT, where the select involved a derived table that referenced both local and proxy tables, and the table being inserted into was a local table, could have caused the server to crash. This problem has been fixed.



CR:441971
CR Number:   441971
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)
10.0.1 2958 18 Sep 2006 Fixed
10.0.0 2702 18 Sep 2006 Fixed
Description
It was not possible to create multi-byte character userids and passwords with trailing bytes x7B or x7D, or with {, }, (, ) or spaces. Attempts to do so, would have failed with an invalid identifier error. As well, it was possible to create a userid or password using Sybase Central, or any of the programming APIs, which could not have been used in an UltraLite connection string. Both of these issues have now been fixed. All userids and passwords which correspond to a valid connection string value can now be specified, and values specified through Sybase Central or GrantConnectTo() which can not be used in a connection string are rejected.



Note, userids and passwords must still be valid connection string values and must not contain leading or trailing spaces, leading single or double quotes, or any semi-colons.



CR:441978
CR Number:   441978
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)
10.0.1 2954 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
9.0.2 3375 18 Sep 2006 Fixed
Description
The changes for Engineering Case 440786 introduced a problem such that running a large query that referenced proxy tables that were executed in FULL PASSTHRU mode, could have failed with a memory allocation error. This problem has been fixed.



CR:441995
CR Number:   441995
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2954 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
Description
It was possible, although extremely rare, for the MobiLink server to have crashed when using compressed network communications. The only workaround was to disable network communication compression. This problem has been fixed.



CR:442034
CR Number:   442034
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2955 19 Sep 2006 Fixed
10.0.0 2699 19 Sep 2006 Fixed
Description
It was possible for the MobiLink server to have crashed during HTTP synchronizations. This has been fixed.



CR:442144
CR Number:   442144
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)
10.0.1 2953 18 Sep 2006 Fixed
10.0.0 2699 18 Sep 2006 Fixed
Description
If a materialized view was selected in the tree, and then its Indexes tab was selected, the New View and New Materialized View menu items and toolbar buttons could not be used to create a view or materialized view. This has been fixed.



CR:442145
CR Number:   442145
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)
10.0.1 2955 18 Sep 2006 Fixed
10.0.0 2700 18 Sep 2006 Fixed
Description
After right-clicking a column in the table editor and choosing the Delete menu item, then right-clicking the same column again, the Delete menu item would have been left enabled. This has been fixed so that the Delete menu item is only enabled if the column has not already been marked for deletion.



CR:442146
CR Number:   442146
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)
10.0.1 2955 20 Sep 2006 Fixed
10.0.0 2700 20 Sep 2006 Fixed
Description
If a column in the table editor was right-clicked and the Delete menu item chosen, then the column could still have been modified by opening its property sheet. This has been fixed by opening the column's property sheet in read-only mode.



CR:442148
CR Number:   442148
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)
10.0.1 2955 20 Sep 2006 Fixed
10.0.0 2700 20 Sep 2006 Fixed
Description
If a table mapping was marked for deletion in the Table Mapping Editor, then the table mapping could still have been modified by using other menu items in the File or pop-up menus. This has been fixed by having the context and pop-up menus take into account whether the table mapping was marked for deletion.



CR:442149
CR Number:   442149
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)
10.0.1 2956 20 Sep 2006 Fixed
10.0.0 2700 20 Sep 2006 Fixed
Description
It was not possible to use the Edit menu's Cut, Copy, Paste, and Delete menu items with text fields on the Mappings tab's Download Type, Download Deletes, and Download Subset tabs, or with text fields on the Authentication and Notification tabs. This has been fixed. Note that the corresponding toolbar buttons were functional in this case.



CR:442152
CR Number:   442152
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)
10.0.1 2956 20 Sep 2006 Fixed
10.0.0 2700 20 Sep 2006 Fixed
Description
If a table mapping was marked for deletion, it was still possible to modify it by making changes on the Download Type, Download Deletes, Download Subset, and Conflict Resolution tabs. Also, if the Column Mappings tab was selected, it was possible to right-click a column mapping and change the Synchronize setting via the menu item. Both of these problems have been fixed. Now all components on these tabs, and all menus, are disabled when the corresponding table mapping is marked for deletion.



CR:442155
CR Number:   442155
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)
10.0.1 2961 25 Sep 2006 Fixed
10.0.0 2705 25 Sep 2006 Fixed
Description
If a database was involved in mirroring, and the database was shut down but the server hosting the database remained running, the mirror server was not notified of the shutdown and did not take ownership of the database. This has been fixed.



CR:442158
CR Number:   442158
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)
10.0.1 3266 03 Oct 2006 Fixed
10.0.0 2713 03 Oct 2006 Fixed
Description
If temporary table containing a compressed column was used in the result set of a stored procedure or batch, the server may have crashed. This would only have happened if the size of the *compressed* data was less than one page. This has been fixed.



CR:442176
CR Number:   442176
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)
10.0.1 2958 21 Sep 2006 Fixed
10.0.0 2702 21 Sep 2006 Fixed
Description
A SOAP request to a SQL Anywhere SOAP service having been declared with a datatype IN, or an ON clause with a call to a stored procedure that takes no parameters, would have caused the server to crash. This has been fixed.



CR:442268
CR Number:   442268
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3377 20 Sep 2006 Fixed
Description
A query containing an outer join, where the null-supplying side was a derived table, may have failed with the error "The optimizer was unable to construct a valid access plan". This occurred when the outer join was used in a correlated subquery of an EXISTS, NOT EXISTS, ANY or ALL predicate, and the derived table must have been uncorrelated, and not flattened (ie., it is a GROUPED query, a UNION query, etc.) This has been fixed



For example:

select * from product p1

where EXISTS(select *

FROM product p2

left outer join (select p3.id, count(*) from product p3 group by p3.id ) as P(ID, c) ON P.id = p2.id

WHERE p2.id = p1.id )



CR:442269
CR Number:   442269
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)
10.0.1 2956 21 Sep 2006 Fixed
10.0.0 2700 21 Sep 2006 Fixed
9.0.2 3433 21 Sep 2006 Fixed
Description
Calling the method DataReader.GetSchemaTable() would have thrown an exception if the table name contained single quotes. This has been fixed by doubling single quotes in the table name.



CR:442279
CR Number:   442279
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2959 20 Sep 2006 Fixed
10.0.0 2703 20 Sep 2006 Fixed
Description
Restarting a MobiLink server listening for HTTP requests, while a listener was already running, would have caused the MobiLink server to report protocol errors, and this listener would have failed to reconnect. This has been fixed.



CR:442283
CR Number:   442283
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2959 20 Sep 2006 Fixed
10.0.0 2703 20 Sep 2006 Fixed
Description
The Listener would have leaked memory if it failed to connect to the MobiLink server. This has been fixed.



CR:442284
CR Number:   442284
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2952 21 Sep 2006 Fixed
10.0.0 2699 21 Sep 2006 Fixed
Description
The MobiLink redirector may have crashed if a client tried to access an empty server-group and there were other non-empty server groups within the redirector configuration. This is fixed.



CR:442293
CR Number:   442293
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2952 21 Sep 2006 Fixed
10.0.0 2699 21 Sep 2006 Fixed
Description
The MobiLink redirector may have occassionally failed to redirect a large upload. An error calculating the content-length has been corrected.



CR:442297
CR Number:   442297
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2893 21 Sep 2006 Fixed
10.0.0 2697 21 Sep 2006 Fixed
Description
Running a MobiLink synchronization through the redirector for SunONE6.1 with persistent HTTP would have failed. The webserver may turn on HTTP chunking when downloading to the client, but HTTP chunking was not supported. This has been fixed by adding HTTP chunking support.



CR:442299
CR Number:   442299
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2891 21 Sep 2006 Fixed
10.0.0 2390 21 Sep 2006 Fixed
Description
MobiLink synchronizations through the MobiLink redirector for IIS with persistent HTTP would have failed. Persistent HTTP was not supported by the IIS redirector, it has now been added.



CR:442301
CR Number:   442301
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2898 22 Sep 2006 Fixed
10.0.0 2401 22 Sep 2006 Fixed
Description
Since persistent HTTP was not supported by the MobiLink redirector for iPlanet 6.0, synchronization would have failed or hung. This has been fixed by changing the redirector to turn persistent HTTP off, even when clients specify it.



CR:442303
CR Number:   442303
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)
10.0.1 2959 21 Sep 2006 Fixed
10.0.0 2703 21 Sep 2006 Fixed
Description
Calling the system prodecure xp_read_file() would have caused the server to fail with assertion 100913, if the file read was longer than the server's maximum supported string size (~2GB). This has been fixed.



CR:442305
CR Number:   442305
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2951 20 Sep 2006 Fixed
10.0.0 2699 20 Sep 2006 Fixed
Description
When the listener was using an AirCard modem to receive SMS messages, and the AirCard modem was also used by another process, or the listener itself, to dial up to an IP network, the modem may have deadlocked with a constant green light on the card. This has now been corrected.



CR:442307
CR Number:   442307
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)
10.0.1 2956 21 Sep 2006 Fixed
10.0.0 2700 21 Sep 2006 Fixed
9.0.2 3376 21 Sep 2006 Fixed
Description
Calling a stored procedure that returned empty date, datetime, smalldatetime or timestamp values, would have caused an ArgumentOutOfRangeException. This problem has been fixed.



CR:442310
CR Number:   442310
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)
10.0.1 2959 21 Sep 2006 Fixed
10.0.0 2703 21 Sep 2006 Fixed
Description
If a remote server was defined using either the SAJDBC or ASEJDBC class and a remote stored procedure was created that had string arguments, then calling the remote stored procedure would have failed with a "system exception occurred" error. This problem has been fixed.



Note, the problem does not exist if the remote server is created using one of the ODBC classes.



CR:442318
CR Number:   442318
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3377 21 Sep 2006 Fixed
Description
On Unix systems, an ODBC trace of the MobiLink server would have shown many calls to SQLSetEnvAttr, as it was being called to set the ODBC version on every connect. This problem could have caused a hang within the MobiLink server when connected to a non-ASA consolidated. The hang could have eventually tied up most, if not all, the server's worker threads, after which the MobiLink server would have been completely unresponsive. This has been fixed so that now SQLSetEnvAttr is only called when the environment is allocated.



CR:442373
CR Number:   442373
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Windows CE 2.11
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 18 Oct 2006 Fixed
10.0.0 2734 18 Oct 2006 Fixed
Description
When installing to Windows CE using the signed CAB file, the Japanese language resource library (dblgja10.dll) was not being copied, and the language key was set incorrectly in the registry. This has been corrected, now all five of the language DLLs are included in the signed .CAB files, and the language registry entry is left blank. This will allow the signed .CAB files to run by default in the same language as the device.



CR:442386
CR Number:   442386
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
Fetching an nchar column from a proxy table that contained both nchar columns and long varchar, long binary or long nvarchar columns, could have returned mangled data for the nchar column, when the nchar column appeared after the first long column in the proxy table definition. Data for nchar columns which appeared before the first long column would have been fetched correctly. This problem has been fixed so that nchar data is fetched correctly regardless of the columns position in the table definition.



CR:442387
CR Number:   442387
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
While using Sybase Central extensively, users may experienced connection failures reporting too many connections, or too many open databases, when there were only a few or only one database open. The connection count displayed in Sybase Central for a particular database would have been unreasonably high. The odbc driver was leaving connections open. If users were switching databases (while keeping one open), or repeatedly trying to connect to already connected database, connection limits could have been exceeded. This has been fixed.



CR:442398
CR Number:   442398
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
A long owner name could have obscured the names of tables in the New Remote Database Schema and Existing Remote Database pages of the Create Synchronization Model and Update Schema wizards of the MobiLink plug-in. This has been fixed



CR:442417
CR Number:   442417
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2960 25 Sep 2006 Fixed
10.0.0 2704 25 Sep 2006 Fixed
Description
The UltraLite Create Database utility (ULCREATE), did not create case sensitive databases when the option -o case=respect was set. This has been corrected.



CR:442440
CR Number:   442440
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
If a remote data access server was createded using either the SAJDBC or ASEJDBC classes, and a proxy table referencing that server was defined with a long string column, then fetching the data for that column could have lead to data corruption if the remote database was using a multi-byte character set. This problem has been fixed.



CR:442443
CR Number:   442443
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
Attempting to retrieve data from an nchar column, when connected using either jConnect or Open Client, may have caused the connection to have been dropped. This problem has been fixed.



CR:442452
CR Number:   442452
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
The LIKE operator did not respect case in case-sensitive databases. This has been fixed.



CR:442453
CR Number:   442453
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)
10.0.1 2960 22 Sep 2006 Fixed
10.0.0 2704 22 Sep 2006 Fixed
Description
Changing a table schema, or data in the data tab for a table, then switching modes, would have caused the change to be lost. This has been fixed by prompting the user to save or cancel changes when switching modes.



CR:442459
CR Number:   442459
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)
10.0.1 2960 25 Sep 2006 Fixed
10.0.0 2704 25 Sep 2006 Fixed
Description
If an externlogin was created for a remote data access server with a remote login id that was 128 bytes long, then remote connections would have failed. This problem has been fixed.



CR:442460
CR Number:   442460
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)
10.0.1 2960 25 Sep 2006 Fixed
10.0.0 2704 25 Sep 2006 Fixed
Description
When attempting to create a proxy table to a remote table, if the remote table name was 128 bytes in length or the user id of the remote table's owner was 128 bytes in length, then the server would have crashed. This problem has been fixed.



CR:442543
CR Number:   442543
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3385 06 Oct 2006 Fixed
Description
The UltraLIte Interactive SQL utility and the UltraLite schema painter were not handling systems with multiple monitors correctly. If a window was closed while on a secondary monitor and then the application was restarted when only one monitor was connected, the window would have been positioned off the visible desktop. This is now fixed.



A workaround for this situation is to do the following:

1. Right click on the application in the task bar.

2. Select Move

3. Use the keyboard cursor keys to bring the window back to the visible desktop and hit Enter when it抯 properly positioned.



CR:442554
CR Number:   442554
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)
10.0.1 2961 25 Sep 2006 Fixed
10.0.0 2705 25 Sep 2006 Fixed
Description
If a server, with an alternate server name that was not all lower-case, was shut down, other servers in the network could not have started using that server name (or alternate server name); startup would have failed with the error "Server name is already in use". This has been fixed.



CR:442567
CR Number:   442567
Product Name:   UltraLite
Product Component:   UltraLite for AppForge MobileVB
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 2962 26 Sep 2006 Fixed
10.0.0 2706 26 Sep 2006 Fixed
Description
An UltraLite for AppForge application could have crashed after calling the ULConnection.GetDatabaseProperty() method. This would have occurred if the application was written in a Crossfire language (VB.Net or C#), and run on an actual device (i.e. not in hosted mode on the desktop). This is now fixed.



CR:442574
CR Number:   442574
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3266 03 Oct 2006 Fixed
10.0.0 2716 03 Oct 2006 Fixed
9.0.2 3382 03 Oct 2006 Fixed
8.0.3 5447 03 Oct 2006 Fixed
Description
Applications which did not use ODBC (for example, dbisql and other utilities) would not find a file DSN file if the file was in the default ODBC File DSN directory. The FILEDSN connection parameter can be used to specify a file DSN. The default ODBC File DSN directory is the directory where File DSNs are created by default by the Microsoft ODBC Data Source Administrator. This has been fixed.



CR:442575
CR Number:   442575
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3378 22 Sep 2006 Fixed
Description
If a database had two or more tables with the same name and columns owned by a different users, and one of those table owners had queried their table with the Interactive SQL utility, opening the QueryEditor would have caused an exception to be thrown. This problem has been fixed.



CR:442589
CR Number:   442589
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3271 11 Oct 2006 Fixed
10.0.0 2727 11 Oct 2006 Fixed
Description
Using the ODBC Administrator to create a File DSN with a space in a parameter, would have caused the value in the file to be incorrectly quoted. This has been fixed so that File DSN values are now created without quotes.



CR:442590
CR Number:   442590
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)
10.0.1 2961 21 Sep 2006 Fixed
10.0.0 2705 21 Sep 2006 Fixed
Description
Attempting to copy and paste a Directory Access Server's proxy table within the plug-in would have failed. The remote location string was not being set correctly. 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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------