远程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:634191
CR Number:   634191
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.0 2550 06 Jul 2010 Fixed
11.0.1 2460 06 Jul 2010 Fixed
12.0.1 2964 21 Sep 2010 Fixed
Description
If an application made an external C environment call with a NULL argument, and the external C environment routine subsequently called get_value() to retrieve the NULL argument, then the environment would have incorrectly returned a status of 0 indicating failure to the external C environment routine, rather than returning a non-zero status. This problem has now been fixed.



CR:634195
CR Number:   634195
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.0 2549 06 Jul 2010 Fixed
12.0.1 2959 21 Sep 2010 Fixed
Description
Synchronization model generated event scripts with errors or warnings could have included lines starting with #ERROR or #WARN, instead of having commented error or warning messages. This has been fixed.



CR:634196
CR Number:   634196
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.0 2550 06 Jul 2010 Fixed
12.0.1 2964 21 Sep 2010 Fixed
Description
When editing data in a scrollable table, the first keystroke pressed in a cell whose value was "(NULL)" or "(DEFAULT)" was being inadvertently ignored. This has been fixed.



CR:634198
CR Number:   634198
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.0 2550 06 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
When deploying a Synchronization Model with Java or .NET table scripts, the scripts would not have been added. Instead of having the SQL to define such scripts, the generated SQL file would have included an error message "Scripts of type 'x' not supported" where 'x' was Java or .NET. This has been fixed.



CR:634289
CR Number:   634289
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.0 2550 06 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
Attempting to upgrade a database would on rare occasions have failed with a 'database in use' error, even though there was no other connection active on the database. This problem has now been fixed.



CR:634293
CR Number:   634293
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.0 2550 06 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
The Interactive SQL utility could have crashed when sorting a large result set which returned tens of thousands of rows. This would have occurred in the following situation:

1. Click the column header to sort by that column

2. Click "Yes" when asked to fetch the remaining rows

3. Cancel fetching the rows

4. Click a different column header to sort by some other column



This has now been fixed.



CR:634294
CR Number:   634294
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.0 2458 06 Jul 2010 Fixed
11.0.1 2461 06 Jul 2010 Fixed
Description
Due to a bug in some BlackBerry OS versions, an UltraLiteJ application may have failed to create a database on some simulators and devices. Typically, the result would have been an I/O or access control error. This condition may have occurred more frequently if UltraLiteJ was uninstalled and re-installed. This has been fixed.



CR:634302
CR Number:   634302
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.0 2550 07 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
The Interactive SQL utility could have crashed when sorting a result set which returned tens of thousands of rows. This would have occurred in the following situation:

1. Click the column header to sort by that column

2. click "Yes" (or press Enter) when asked to fetch the remaining rows

3. Immediately press the F5 key.



The crash will occur once the entire result set had been read. This has now been fixed.



CR:634313
CR Number:   634313
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2550 06 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
If Ultralite for Mac OS X or IPhone attempted to synchronize through a proxy host while using HTTPS or TLS, the connection would not have been established, and the sync would have failed. This has been fixed



CR:634324
CR Number:   634324
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)
12.0.0 2562 13 Jul 2010 Fixed
12.0.1 2989 21 Sep 2010 Fixed
Description
The Timeout parameter of the system procedure xp_startsmtp() was being ignored. This has been corrected.



CR:634327
CR Number:   634327
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.0 2554 13 Jul 2010 Fixed
11.0.1 2468 13 Jul 2010 Fixed
10.0.1 4099 13 Jul 2010 Fixed
12.0.1 2975 21 Sep 2010 Fixed
Description
The server may have hung while running the Validation utility (dbvalid), or the equivalent VALIDATE DATABASE statement. This was only possible if multiple connections were open to the database, at least one of which is doing DDL (such as an ALTER TABLE statement), and a checkpoint or connection attempt was made during the validate. This has now been fixed.



Note, it is recommended that the database server not be servicing other connections while database validation is taking place.



CR:634330
CR Number:   634330
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.0 2551 12 Aug 2010 Fixed
11.0.1 2463 08 Jul 2010 Fixed
10.0.1 4096 08 Jul 2010 Fixed
12.0.1 2966 21 Sep 2010 Fixed
Description
Kerberos server principals needed to be of the form: server_name@REALM (for example myserver@SYBASE.COM). There was no way to specify a Kerberos server principal of the industry standard form: server_name/hostname@REALM (for example myserver/mymachine.sybase.com@SYBASE.COM). Now the Kerberos server principal can be specified with the server -kp option. The server principal specified by -kp must have been extracted to the Kerberos keytab file on the machine running the database server. Note that only one of -kp or -kr can be specified.



-kp dbengX/dbsrvX server option:

Specifies the Kerberos server principal and enable Kerberos authenticated connections to the database server.



Syntax:

-kp server-principal



Applies to:

all OSes except Windows Mobile



Remarks:

This option specifies the Kerberos server principal used by the database server. Normally, the principal used by the database server for Kerberos authentication is server-name@default-realm, where default-realm is the default realm configured for the Kerberos client. Use this option if you want to use a different server principal, such as the more standard format server-name/hostname@myrealm. If OpenClient or jConnect Kerberos authenticated connections are made to the server, the server principal must be specified by the application (see SERVICE_PRINCIPAL_NAME for jConnect).



The -kr option cannot be specified if the -kp option is specified.



Specifying this option enables Kerberos authentication to the database server.

See also:

<same list as -kr option documents, with the addition of the -kr option>

Example:

The following command starts a database server that accepts Kerberos logins and uses the principal myserver/mymachine.sybase.com@SYBASE.COM for authentication.



dbeng12 -kp myserver/mymachine.domain.com@MYREALM -n myserver C:\kerberos.db



CR:634340
CR Number:   634340
Product Name:   UltraLiteJ
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 26 Aug 2010 Fixed
11.0.1 2486 26 Aug 2010 Fixed
12.0.1 3018 21 Sep 2010 Fixed
Description
Synchronizations that worked fine on a BlackBerry Bold 9700 with OS 5.0.0.351, failed when the device was upgraded to 5.0.0.743. The application did not use BES or BIS communication, but tried Direct TCP, WAP 2.0 and WAP 1.x. When using BES or BIS communication, there was no issues with synchronization. This problem has been report to Research In Motion since it was discovered that calls to InputStream.read() had an additional 10 seconds overhead with OS 5.0.0.743 when using WAP 2.0 (and simillar delay with DirectTCP and WAP 1.x). UltraLiteJ has now been patch edto reduce the impact of this issue.



For the most reliable synchronization, a device should be paired with a BES (BlackBerry Enterprise Server) or the application should use BIS communication (application provider can join RIM partner program for free and then apply to use the BIS protocol).



CR:634437
CR Number:   634437
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.0 2550 08 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
Selecting a database's Locks tab would have caused Sybase Central to crash if there were any ReadPK or WriteNoPK locks. This has been fixed.



CR:634440
CR Number:   634440
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2551 07 Jul 2010 Fixed
11.0.1 2462 07 Jul 2010 Fixed
12.0.1 2966 21 Sep 2010 Fixed
Description
In the Table Editor, a primary key column could have been marked for deletion by selecting the column and pressing the Delete key, even though the Delete menu item and Delete toolbar button were disabled. In such cases, attempting to save the table could have caused Sybase Central to crash. This has been fixed so that now pressing the Delete key does nothing when one or more of the selected columns is in the primary key.



CR:634445
CR Number:   634445
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2472 07 Jul 2010 Fixed
10.0.1 4105 04 Aug 2010 Fixed
Description
As a side-effect of the changes made for Engineering case 627780, the Start Server in Background utility (dbspawn) on Windows no longer allowed the database server start line to be passed as a single quoted string. This behaviour has now been restored to its previous state on Windows only, and only for versions 10.0.1 and 11.0.1. Version 12 will retain

the new behaviour as per the documentation.



CR:634453
CR Number:   634453
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.0 2551 07 Jul 2010 Fixed
12.0.1 2966 22 Sep 2010 Fixed
Description
When attempting to export a large number of metrics (typically in the range of 50+ metrics and/or 1 million+ points), the SQL Anywhere Monitor could have reported "Error #2038", or a java.lang.OutOfMemoryError. In an effort to prevent this, the SA Monitor now limits the amount of data that can be exported at one time. As of this fix, only a maximum of 25 metrics or 1 million points may be exported at once.



CR:634489
CR Number:   634489
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 2986 28 Jul 2010 Fixed
Description
The Interactive SQL utility (dbisql) would have required the exact case for identifiers to be used when connecting to a SQL Anywhere case-sensitive database. This was incorrect for SQL Anywhere, as case-sensitivity affects string comparisons not identifiers, and has now been corrected.



This general problem affected a number of other aspects of dbisql behavior, and have also been corected:

1. The "Lookup Table Name" window, the "Lookup Procedure Name" window, and the text completer made case-sensitive searches for matching object names if connected to a case-sensitive SQL Anwyhere database.

2. The INPUT USING statement would have failed if the table name in the FROM clause did not match the exact case of an existing table in the case-sensitive database from which data was being imported.

3. In the Query Editor, the list of available columns did not show any columns unless the table name matched the case of the database table name (affects: "Columns", "GROUP BY", and "ORDER BY" tabs; "Expression Editor" window). Also, the "Table pattern" field on the "Tables" tab was applied in a case-sensitive way.



CR:634503
CR Number:   634503
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.0 2551 08 Jul 2010 Fixed
11.0.1 2463 08 Jul 2010 Fixed
10.0.1 4096 08 Jul 2010 Fixed
12.0.1 2966 22 Sep 2010 Fixed
Description
When completing the name of a column in a SELECT statement following the FROM clause, the completed text could have included the owner name for the table which contained the column, but not the table name. This was not valid SQL. Now, the owner name is not part of the inserted text.



CR:634504
CR Number:   634504
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2551 08 Jul 2010 Fixed
11.0.1 2463 08 Jul 2010 Fixed
10.0.1 4096 08 Jul 2010 Fixed
12.0.1 2966 22 Sep 2010 Fixed
Description
SQL Anywhere ODBC data sources were not listed in Visual Studio's Add Connection dialogbox on 64 bit Windows systems. This has now been fixed.



CR:634532
CR Number:   634532
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2553 13 Jul 2010 Fixed
11.0.1 2465 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
Connections to a database using a large cache on Windows Mobile devices, could have failed with the error SQLE_DYNAMIC_MEMORY_EXHAUSTED. This has been fixed.



CR:634556
CR Number:   634556
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.0 2551 08 Jul 2010 Fixed
12.0.1 2967 22 Sep 2010 Fixed
Description
For a Synchronization Model using server-initiated synchronization and a SQL Anywhere consolidated database, the generated publication_non_blocking_download_ack event script would have included a GO delimiter that caused an error when the script executed. This has been

fixed.



CR:634559
CR Number:   634559
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2551 08 Jul 2010 Fixed
12.0.1 2967 22 Sep 2010 Fixed
Description
Upgrading a version 10 Synchronization Model with server-initiated synchronization enabled would have lead to the ml_set_sis_sync_state stored procedure being called in two events, because the old end_publication script was not removed when the replacement publication_nonblocking_download_ack event script was generated. This has been fixed.



CR:634612
CR Number:   634612
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2551 12 Jul 2010 Fixed
11.0.1 2464 12 Jul 2010 Fixed
12.0.1 2967 22 Sep 2010 Fixed
Description
When F5 was pressed, or View -> Refresh Folder was selected, while creating a new table in the Table Editor and No selected when prompted to save the table, then the prompt to save dialog would have been shown again. This has been fixed.



CR:634664
CR Number:   634664
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2551 12 Jul 2010 Fixed
11.0.1 2464 12 Jul 2010 Fixed
10.0.1 4096 12 Jul 2010 Fixed
9.0.2 3974 12 Jul 2010 Fixed
12.0.1 2967 22 Sep 2010 Fixed
Description
The Microsoft SQL Server Reporting Services 2008 application uses the Linked Server mechanism to communicate via OLE DB to a SQL Anywhere server. It can send EXEC statements of the following form to the SQL Anywhere OLE DB provider:

EXEC owner.procedure_name :parm1, :parm2, ...



where :parm1, etc. are bound parameters.



The SQL Anywhere OLE DB provider has been improved to now handle this syntax.



CR:634675
CR Number:   634675
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.0 2552 12 Jul 2010 Fixed
11.0.1 2464 12 Jul 2010 Fixed
12.0.1 2967 22 Sep 2010 Fixed
Description
Sybase Central could have crashed when attempting to view the data of a table after dropping the table's primary key by some means other than Sybase Central (for example, via the Interactive SQL utility), and then refreshing the Sybase Central viewer via F5 or View -> Refresh. This has been fixed.



CR:634724
CR Number:   634724
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)
11.0.1 2467 15 Jul 2010 Fixed
Description
With the option Blocking set to 'off', any attempts to modify a row that is locked by another user will result in an error message. Occasionally, this error message would have contained the string 'another user', instead of a valid user name. This has been fixed.



CR:634728
CR Number:   634728
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.0 2568 12 Aug 2010 Fixed
11.0.1 2480 12 Aug 2010 Fixed
10.0.1 4111 12 Aug 2010 Fixed
12.0.1 3004 22 Sep 2010 Fixed
Description
If a simple statement had one of the following forms and a table hint was used in the FROM clause, it was possible for subsequent statements from the same connection with the same form, but with different hints, to use the hints from the earlier statement.

1) SELECT {table columns} FROM {table} WHERE {primary key col1 = val1, primary key col2 = val2, ... }

2) UPDATE {table} SET ... WHERE {primary key col1 = val1, primary key col2 = val2, ... }

3) DELETE FROM {table} SET ... WHERE {primary key col1 = val1, primary key col2 = val2, ... }



This has been fixed. As a work-around, the statements can be change to include "OPTIONS( FORCE OPTIMIZATION )", or the server can be started with the following command line switch: "-hW AllowSimpleUserCache".



CR:634765
CR Number:   634765
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.0 2552 12 Jul 2010 Fixed
12.0.1 2968 21 Sep 2010 Fixed
Description
When an alert widget attempted to display a large number of alerts, it was possible that the web browser would have become unresponsive. This has been fixed.



CR:634775
CR Number:   634775
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.0 2561 27 Jul 2010 Fixed
11.0.1 2473 27 Jul 2010 Fixed
12.0.1 2986 22 Sep 2010 Fixed
Description
Execution of a CREATE TEXT INDEX <name> ON <table_name>(...) statement on a proxy table could have failed silently without giving an error. The creation of text indexes on proxy tables is not allowed, and the statement now gives the appropriate error.



CR:634785
CR Number:   634785
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)
11.0.1 2483 20 Aug 2010 Fixed
Description
When applying an MSI install built using the deployment wizard, and specifying the target directory similar to the following:

msiexec /i sqlany11.msi SQLANYDIR="{path to install directory}\xxx xxxxxxxx xx"



the install could have failed. This has been fixed.



CR:634791
CR Number:   634791
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.0 2552 12 Jul 2010 Fixed
12.0.1 2968 22 Sep 2010 Fixed
Description
Sybase Central could have displayed a server twice in the tree. This could eventually have caused a crash when disconnecting from a database running on the server. This has been fixed.



CR:634883
CR Number:   634883
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.0 2567 10 Aug 2010 Fixed
11.0.1 2478 10 Aug 2010 Fixed
10.0.1 4111 10 Aug 2010 Fixed
12.0.1 3000 22 Sep 2010 Fixed
Description
Connections which had communication compression enabled could have been dropped, resulting in the "Connection was terminated" error. This was more likely to occur if the connection had both communication compression and simple encryption enabled. If the server -z log and the client LOGFILE log was used, the message "Failed to decompress a compressed packet" would have appearred in one or both of the logs when this problem occurred. This has been fixed.



CR:634894
CR Number:   634894
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.0 2553 14 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
When modifying a character column value after selecting "Edit in Window" from the "...' menu, if there was a database error with the value, the value could have been corrected with a new value, but the old value was resent by mistake. This has been fixed.



CR:634898
CR Number:   634898
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.0 2553 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
The wrong year could have been selected after clicking the "Calendar" button in a task's property sheet, or in the "Delete Agent Events" window. The problem occurred only if a date in a year other than the current one was selected. This has been fixed.



CR:634900
CR Number:   634900
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 3081 05 Oct 2010 Fixed
12.0.0 2558 05 Oct 2010 Fixed
11.0.1 2560 08 Feb 2011 Fixed
Description
The server may have become deadlocked while acquiring shared latches. This has now been corrected.



CR:634906
CR Number:   634906
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.0 2553 13 Jul 2010 Fixed
11.0.1 2465 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
Setting the "Show results from each statement" option would have resulted in incorrect behavior: Attempts to sort, select all, or copy column data would have resulted in an attempt to fetch more rows if required. That attempt should not have been made. When "Show results for each statement" is On, only the rows already fetched can be sorted. This has been corrected.



CR:634908
CR Number:   634908
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.0 2559 27 Jul 2010 Fixed
12.0.1 2986 22 Sep 2010 Fixed
Description
In the Developer Edition, the SQL Anywhere Monitor required a reboot for System Tray - > Browse Data to work. This has been fixed.



CR:634919
CR Number:   634919
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.0 2553 13 Jul 2010 Fixed
11.0.1 2465 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
The utility SetupVSPackage.exe did not modify the Global Assembly Cache (GAC) or the machine.config file if Visual Studio was not installed. This problem has been fixed.



CR:634921
CR Number:   634921
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 4101 20 Jul 2010 Fixed
Description
When a ping synchronization took place, the MobiLink server needed to check the status of the connection to the consolidated database, and would have done so by executing a query to count the number of rows in the ml_scripts_modified table, but MobiLink would not have committed or rolled back this query when the ping synchronization was complete, leaving the transaction open. If the consolidated database used snapshot isolation, this open transaction would have resulted in the MobiLink server sending an older last modified timestamp than was necessary to remote databases until this transaction was closed, which would not happen until another non-ping synchronization re-used the same connection in the connection pool. While this did not result in any data loss, it could result in the same rows being downloaded to the remote databases multiple times. The MobiLink server no longer leaves this transaction open after a ping synchronization.



CR:634933
CR Number:   634933
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.0 2553 13 Jul 2010 Fixed
11.0.1 2465 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
Deploying a Synchronization Model with the "Run this wizard initialized with last deployment settings" option would have given an empty field for the location of the UltraLite database file, instead of using the location from the last deployment. A workaround is to use the Browse button to pick the previously deployed UDB file. This has been fixed.



CR:634934
CR Number:   634934
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.0 2553 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
If a computer was configured to display numbers with a thousands separator, and a NUMERIC, REAL, FLOAT, or DECIMAL value that contained a thousands separator was edited, the editor would have started empty and the bell would ring. Now the thousands separator is stripped out, and the resulting string is used as the initial editor value.



CR:634938
CR Number:   634938
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.0 2553 13 Jul 2010 Fixed
12.0.1 2971 22 Sep 2010 Fixed
Description
The Task Wizard would have crashed if the "This task requires or creates a remote database" checkbox was checked, but no Remote Schema Names had been added to the project. The crash happened when the "Finish" button was clicked. This has been fixed.



CR:635035
CR Number:   635035
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2553 13 Jul 2010 Fixed
12.0.1 2972 22 Sep 2010 Fixed
Description
While very rare, it was possible for the Server Enumeration utility (dblocate) to hang. This has been fixed.



CR:635062
CR Number:   635062
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2552 14 Jul 2010 Fixed
11.0.1 2465 14 Jul 2010 Fixed
12.0.1 2969 22 Sep 2010 Fixed
Description
The Relay Server Outbound Enabler (RSOE) could have failed to connect to an Apache Relay Server, with the error message "HTTP chunk length too long". The same RSOE would not have reproduced this error with a Microsoft IIS webserver. This has been fixed.



CR:635066
CR Number:   635066
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.0 2553 13 Jul 2010 Fixed
11.0.1 2466 13 Jul 2010 Fixed
11.0.0 1654 13 Jul 2010 Fixed
12.0.1 2972 22 Sep 2010 Fixed
Description
When Snapshot isolation was enabled, deleted rows might not have been physically removed in some cases. This has been corrected.
Workaround Description
 None.



CR:635072
CR Number:   635072
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2553 14 Jul 2010 Fixed
11.0.1 2466 14 Jul 2010 Fixed
10.0.1 4096 14 Jul 2010 Fixed
12.0.1 2972 22 Sep 2010 Fixed
Description
Specifying a single, empty authentication parameter on the dbmlsync commandline, or using a synchronization profile, would have caused dbmlsync to report "out of memory". For example specifying the following on the commandline would have caused the error:

-ap ""



This problem has been fixed.



Note, a workaround is to specify the parameter using a single comma. For example -ap , This passes a single empty authentication parameter but does not cause the "out of memory" error.



CR:635078
CR Number:   635078
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.0 2553 14 Jul 2010 Fixed
12.0.1 2972 22 Sep 2010 Fixed
Description
If the preferred language was "Simplified Chinese", the date picker would not have displayed the month names when attempting to set a date range on the Export Metrics dialog. This has been fixed.



CR:635085
CR Number:   635085
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2553 14 Jul 2010 Fixed
12.0.1 2972 22 Sep 2010 Fixed
Description
Attempting to create or interact with a database on an attached Windows CE device using the desktop tools (i.e. Sybase Central or command line utilities), using a WCE:\... database filename, would have fail. The WCE:\... paths have now been special cased when qualifying filenames.



CR:635120
CR Number:   635120
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.0 2556 20 Jul 2010 Fixed
11.0.1 2470 20 Jul 2010 Fixed
10.0.1 4101 20 Jul 2010 Fixed
12.0.1 2980 22 Sep 2010 Fixed
Description
In exceptionally rare conditions, the server may have crashed while reading a row of a table that had a very large number of columns. This has now been fixed.



CR:635166
CR Number:   635166
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.0 2554 14 Jul 2010 Fixed
12.0.1 2973 22 Sep 2010 Fixed
Description
If a user had a Resource List Widget that was sorted based on resource status, and a resource updated its status, the widget would not have been re-sort. This has been fixed.



CR:635167
CR Number:   635167
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.0 2554 14 Jul 2010 Fixed
12.0.1 2974 22 Sep 2010 Fixed
Description
Database connections acquired from the HTTP connection pool may have incorrectly referenced Global Temporary tables. Typically, a procedure that inserted data would have failed with a (SQLCODE -207) "Wrong number of values for INSERT" on subsequent HTTP requests. This has been fixed. A work-around is to disable HTTP connection pooling with the following database option: set option Public.http_connection_pool_basesize=0.



CR:635168
CR Number:   635168
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.0 2554 14 Jul 2010 Fixed
12.0.1 2973 22 Sep 2010 Fixed
Description
If a read-only user logged in to the SQL Anywhere Monitor and attempted to close a SQL Anywhere connection using the Connection Widget, it would have failed silently. This has been fixed. Read-only users can now successfully close connections.



CR:635175
CR Number:   635175
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2553 14 Jul 2010 Fixed
11.0.1 2467 14 Jul 2010 Fixed
12.0.1 2972 22 Sep 2010 Fixed
Description
When there was a design problem in the Notifier property (e.g. user defined a request_cursor referencing an unknown column), the Notifier would have reported the SQLException on MobiLink server startup, but the error report did not contain enough context information to pinpoint the issue efficiently. The Notifier would also have produced repeated NullPointerException in the MobiLink log after it failed to start. This has been fixed to add context information in addition to the SQLException and stop the Notifier from running if it has encountered a design problem.

The following is an example output after the fix.

<Main> [-10133] java.lang.Exception: Notifier(Simple).request_cursor: Failed to prepare request cursor

<Main> [-10133] at ianywhere.ml.notifier.Notifier.connectDB(Notifier.java:390)

<Main> [-10133] at ianywhere.ml.notifier.Scheduler.connectDB(Scheduler.java:360)

<Main> [-10133] at ianywhere.ml.notifier.Scheduler.run(Scheduler.java:428)

<Main> [-10133] at java.lang.Thread.run(Thread.java:619)

<Main> [-10133] Caused by: java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Column 'bogus_content' not found

<Main> [-10133] at ianywhere.ml.jdbcodbc.IConnection.nativePrepareStatement(Native Method)

<Main> [-10133] at ianywhere.ml.jdbcodbc.IConnection.prepareStatement(IConnection.java:554)

<Main> [-10133] at ianywhere.ml.notifier.Notifier.connectDB(Notifier.java:388)

<Main> [-10133] ... 3 more

<Main> <SISI><Scheduler(0:1)>: Shutdown

<Main> <SISI><Scheduler(0:1)>: Disconnected from database



CR:635300
CR Number:   635300
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2552 15 Jul 2010 Fixed
12.0.1 2968 22 Sep 2010 Fixed
Description
The text displayed by an evaluation version of the MobiLink server was truncated. This has been fixed.



CR:635322
CR Number:   635322
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.0 2554 15 Jul 2010 Fixed
11.0.1 2468 15 Jul 2010 Fixed
11.0.0 1654 15 Jul 2010 Fixed
12.0.1 2975 22 Sep 2010 Fixed
Description
The cleaner may not have completely cleaned pages in some situations. This has now been fixed.



CR:635336
CR Number:   635336
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.0 2554 19 Jul 2010 Fixed
11.0.1 2468 19 Jul 2010 Fixed
10.0.1 4099 19 Jul 2010 Fixed
12.0.1 2975 22 Sep 2010 Fixed
Description
The MobiLink Server Log File Viewer would have shown empty user names and remote IDs in its "Synchronizations" and "Details" panels when running on a non-English Solaris, Mac OS X, or French Linux system, and Sybase Central was set up to run in that non-English language. This has been fixed.



CR:635353
CR Number:   635353
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 3326 12 Apr 2011 Fixed
12.0.0 2669 12 Apr 2011 Fixed
11.0.1 2589 12 Apr 2011 Fixed
10.0.1 4209 12 Apr 2011 Fixed
Description
The server could have hung when a connection disconnected, or was dropped. This was more likely to have occurred if the server was under heavy load. This has been fixed.



CR:635356
CR Number:   635356
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 3040 25 Aug 2010 Fixed
12.0.0 2585 22 Sep 2010 Fixed
Description
The server could have crashed under certain specific circumstances when executing the DROP STATISTICS statement. This problem has been resolved.



CR:635357
CR Number:   635357
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.0 2554 19 Jul 2010 Fixed
12.0.1 2975 22 Sep 2010 Fixed
Description
A deleted row with a blob column could have been created with an invalid format when using the MobiLink Replay utility's replay API if the code generated by mlgenreplayapi was modified so that the blob value can be passed to the Delete method of the MLReplayUploadTable_<table name> class. The result of trying to synchronize this deleted row would have been a failed synchronization. This has been fixed.



CR:635419
CR Number:   635419
Product Name:   SQL Anywhere
Product Component:   SNMP Extension Agent
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2570 19 Jul 2010 Fixed
11.0.1 2468 15 Sep 2010 Fixed
12.0.1 3009 22 Sep 2010 Fixed
Description
Attempting to retrieve the uid_has_hyphens option setting through the SNMP interface would always have returned NULL. This has been fixed.



CR:635433
CR Number:   635433
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.0 2555 19 Jul 2010 Fixed
12.0.1 2976 22 Sep 2010 Fixed
Description
Attempting to change the type of an existing command would have put the "Commands" panel in Sybase Central in a state where it was not possible to modify the command unless some other item was selected in the "Folders" pane, then the remote task again was selected again. Other symptoms included the drop-down list for the "Command type" flashing briefly before disappearing. This has now been fixed.



CR:635442
CR Number:   635442
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.0 2555 19 Jul 2010 Fixed
12.0.1 2976 22 Sep 2010 Fixed
Description
The MobiLink Agent for central administration of remotes could have failed to upload its log file if the file upload command used the variable 'agent_log' for the filename. The failure would have occurred if the full filepath of the log file was long (more than 100 bytes). This has been fixed.



CR:635443
CR Number:   635443
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)
12.0.0 2555 19 Jul 2010 Fixed
11.0.1 2468 19 Jul 2010 Fixed
10.0.1 4100 19 Jul 2010 Fixed
12.0.1 2976 22 Sep 2010 Fixed
Description
When not connected to a database in the SQL Anywhere Console utility (dbconsole), the "File/Options" menu is disabled. The "Options" context menus for the "Connections", "Properties", and "Messages" panels were not disabled. This has been corrected so that now they are disabled.



CR:635466
CR Number:   635466
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)
12.0.0 2567 21 Jul 2010 Fixed
11.0.1 2478 21 Jul 2010 Fixed
10.0.1 4111 21 Jul 2010 Fixed
12.0.1 3000 22 Sep 2010 Fixed
Description
When making a TCP connection to a remote machine that was unavailable (i.e. powered off, network cable unplugged, etc.), the time taken to time out could have been far longer than the value of the TIMEOUT parameter. This has been fixed.



CR:635468
CR Number:   635468
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.0 2555 19 Jul 2010 Fixed
11.0.1 2468 19 Jul 2010 Fixed
12.0.1 2976 22 Sep 2010 Fixed
Description
On Mac OS X systems only, the names of favorites in the Favorites sidebar would have disappeared when the mouse was moved over them. This has been fixed.



CR:635618
CR Number:   635618
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 2472 20 Jul 2010 Fixed
12.0.0 2561 28 Jul 2010 Fixed
10.0.1 4105 28 Jul 2010 Fixed
12.0.1 2987 22 Sep 2010 Fixed
Description
When converting a string to a time using the CONVERT function and an explicit format-style, SQL Anywhere 10.0 and above could have rejected conversions permitted by earlier versions.



For example, the following statement is accepted by version 9.0, but rejected by version 10.0 and above:

select convert( time, '11:45am', 14 ) tm_conv



The behavour of converting from strings to TIME changed from version 9.0 of SQL Anywhere to version 10.0 and later, with version 10.0 and later applying the same rules that conversions from string to timestamp used. The string '11:45am' does not precisely match the format style 14 (hh:nn:ss:sss) because it contains an "am" indicator that is not present in the style.



Parsing of formatted time strings has been enhanced so that the time portion of a string is accepted provided that it matches the format [hh:nn:ss.ssssssAA]. The time string must specify the hour digits, but all other time parts are optional. The AM/PM indicator is always accepted whether or not time parts are omitted. Note that this now permits up to six digits to represent microseconds after the seconds. This change affects the conversion of string to TIME and also to TIMESTAMP, so there is a consistent parsing. The following is rejected after this change, even though it was accepted in 9.0:

select convert( time, '1991-02-03 11:45', 101 )



The string does not match the style format 101 (mm/dd/yyyy).



Further, in some cases it was possible to generate invalid timestamps with string conversions. This has also been fixed.



CR:635629
CR Number:   635629
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2556 19 Jul 2010 Fixed
11.0.1 2469 19 Jul 2010 Fixed
12.0.1 2979 22 Sep 2010 Fixed
Description
If the Platform field on the Overview page had a long name, the horizontal splitbar could not be moved to view it. This has been fixed.



CR:635652
CR Number:   635652
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.0 2556 20 Jul 2010 Fixed
12.0.1 2979 22 Sep 2010 Fixed
Description
When working with the Recommendations panel within Profiling, its suggestions may sometimes have contained a very long line, which it would have shown in the text area without any line wrapping. This meant that scrolling from left to right was required to view its contains. This has been fixed.



CR:635655
CR Number:   635655
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.0 2556 21 Jul 2010 Fixed
12.0.1 2979 22 Sep 2010 Fixed
Description
If -xs was used to start the HTTP or HTTPS server on a Windows machine with IPv6 enabled, and the port number to be used was already in use by an IPv4-only application, the server would have reported a bind error ("Could not bind to address 0.0.0.0:80") but would have started anyway. This has been fixed - the server will refuse to start in this situation.



CR:635660
CR Number:   635660
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.0 2556 20 Jul 2010 Fixed
12.0.1 2979 22 Sep 2010 Fixed
Description
When choosing columns to add to a delete shadow table in the Download Delete Subset tab for a table mapping, the expression for which the columns were required was not shown when the download delete subset option was "Same" and the download subset option was "Custom". Changing to the Download Subset tab was required to see the expression. This has been fixed. Now the custom download subset table list and SQL expression are displayed as

read-only in the Download Delete Subset tab when the download delete subset option is "Same" and the download subset option is "Custom".



CR:635800
CR Number:   635800
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.0 2557 27 Jul 2010 Fixed
11.0.1 2471 27 Jul 2010 Fixed
12.0.1 2982 22 Sep 2010 Fixed
Description
The error, SQLE_TOO_MANY_CURSORS, would have been reported when there were more than 32 prepared statements for a cursor, each of which had a parameter set. The limit should have been 64 prepared statements. This was corrected.



CR:635803
CR Number:   635803
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.0 2562 28 Jul 2010 Fixed
11.0.1 2473 28 Jul 2010 Fixed
10.0.1 4106 28 Jul 2010 Fixed
12.0.1 2988 22 Sep 2010 Fixed
Description
Diagnostic tracing databases, or databases created by the automatic Application Profiling Wizard, would have failed to start if the original database had auditing enabled. This has been fixed.



A workaround is to temporarily disable auditing on the main database, create the tracing database, and then re-enable it.



CR:635809
CR Number:   635809
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)
12.0.0 2556 20 Jul 2010 Fixed
12.0.1 2980 22 Sep 2010 Fixed
Description
The server's memory usage could have been more than expected. Some memory allocations that could have been from the server's cache, came from the heap instead. This has been fixed.



CR:635815
CR Number:   635815
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.0 2557 20 Jul 2010 Fixed
11.0.1 2470 20 Jul 2010 Fixed
12.0.1 2981 22 Sep 2010 Fixed
Description
If Java or other external environment objects were installed in a database, and the database failed to shut down cleanly before the next checkpoint, then it was likely that the Java or external environment objects would have needed to be re-installed. This problem has now been fixed.



CR:635956
CR Number:   635956
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 3269 04 Aug 2010 Fixed
12.0.0 2628 04 Jan 2011 Fixed
11.0.1 2476 04 Jan 2011 Fixed
10.0.1 4166 04 Jan 2011 Fixed
Description
A query with a CUBE, ROLLUP, or GROUPING SETS clause and HAVING predicates may have returned an incorrect result set. The query must not have had any aggregate functions, and the grouping sets must have contained the grand total which should have been filtered by the HAVING predicates, but instead it was returned as a valid row.



For example:

select n_comment from nation group by cube (n_comment) HAVING n_comment like 'alw%';



The result set would have contained all the rows with n_comment for which the predicate "n_comment LIKE 'alw%' is TRUE, but also the row "(NULL)". This has now been fixed.



CR:635960
CR Number:   635960
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.0 2557 22 Jul 2010 Fixed
12.0.1 2981 23 Sep 2010 Fixed
Description
Attempting to using Integrated Login, or Kerberos, with the NodeType connection parameter could have failed. This has been fixed.



CR:635961
CR Number:   635961
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.0 2557 21 Jul 2010 Fixed
11.0.1 2470 21 Jul 2010 Fixed
12.0.1 2981 23 Sep 2010 Fixed
Description
Attempting to connect using Integrated Login to a mirror server, or copy node, would have failed with the error "Integrated login failed". This has been fixed.



CR:635977
CR Number:   635977
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2557 21 Jul 2010 Fixed
12.0.1 2981 23 Sep 2010 Fixed
Description
The MobiLink server could have hung if it was shutdown after the consolidated server was shutdown or the consolidated server had crashed. This has been fixed.



CR:635991
CR Number:   635991
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2557 22 Jul 2010 Fixed
12.0.1 2981 23 Sep 2010 Fixed
Description
Attempting to unload and reload a 12.0.0 database which was configured for mirroring or read-only scale-out, could have resulted in a syntax error during reload. The syntax error would have occurred on a SET MIRROR OPTION or ALTER MIRROR SERVER statement. This has been fixed.



As a work around, the reload.sql file can be edited to double the embedded quotes and escape other characters requiring escaping in these statements.



CR:636018
CR Number:   636018
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.0 2568 13 Aug 2010 Fixed
11.0.1 2480 13 Aug 2010 Fixed
10.0.1 4111 13 Aug 2010 Fixed
12.0.1 3004 23 Sep 2010 Fixed
Description
Queries involving indexes containing long values could have returned incorrect results. Index corruption was possible, but not likely. This problem has now been fixed.



CR:636082
CR Number:   636082
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2557 22 Jul 2010 Fixed
12.0.1 2982 23 Sep 2010 Fixed
Description
UltraLite should generate an error if a column in a primary key was dropped, but this situation was not being properly diagnosed. This has now been corrected.



CR:636289
CR Number:   636289
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.0 2558 26 Jul 2010 Fixed
12.0.1 2983 23 Sep 2010 Fixed
Description
Under rare circumstances, the server could have hung when synchronizing (or rarely, fetching) large blobs or spatial data. This has been fixed.



A partial workaround is to decrease the frequency of checkpoints; the hang is most likely to occur during a checkpoint. Of course, decreasing the checkpoint frequency will increase recovery time.



CR:636304
CR Number:   636304
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.0 2559 27 Jul 2010 Fixed
11.0.1 2458 27 Jul 2010 Fixed
12.0.1 2979 23 Sep 2010 Fixed
Description
Opening the Domain, Web Service or Spatial Reference System property dialogs could have caused the Sybase Central to crash. This has been fixed.



CR:636305
CR Number:   636305
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2559 27 Jul 2010 Fixed
11.0.1 2472 27 Jul 2010 Fixed
12.0.1 2986 23 Sep 2010 Fixed
Description
When the transaction log contained many entries, sorting of the audit table could have been very slow. This has been fixed by no longer allowing the audit table to be sortable.



CR:636307
CR Number:   636307
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.0 2561 28 Jul 2010 Fixed
11.0.1 2473 28 Jul 2010 Fixed
10.0.1 4105 28 Jul 2010 Fixed
12.0.1 2987 23 Sep 2010 Fixed
Description
A simple UPDATE statement that affected a large number of rows could have consumed memory proportional to the number of rows if the statement used one of the following features:

- results from a user-defined function with numeric Expression Caching (any data type)

- a LIKE predicate

- a CAST of a string to an approximate number (REAL, DOUBLE, or FLOAT)

- the SORTKEY or COMPARE builtin function

- the REMAINDER or MOD builtin functions with arguments of type NUMERIC or DECIMAL

- the MEDIAN aggregate function

- a spatial data type



If the memory usage exceeded what was allowed for one connection, the statement would have failed with a dynamic memory exhausted error. This has been fixed.



CR:636310
CR Number:   636310
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.0 2560 27 Jul 2010 Fixed
11.0.1 2472 27 Jul 2010 Fixed
12.0.1 2986 23 Sep 2010 Fixed
Description
In the "Connect" window, "Tools/Save as ODBC Data Source" can be clicked to save the contents of the window as a DSN. That window was not closing when the Esc key was pressed. This has been fixed so that now it does.



CR:636312
CR Number:   636312
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.0 2559 27 Jul 2010 Fixed
11.0.1 2459 27 Jul 2010 Fixed
12.0.1 2986 23 Sep 2010 Fixed
Description
Selecting 'Undo' or 'Redo' (or typing Ctrl-Z or Ctrl-Y) while viewing a spatial reference system's Definition tab, a system trigger's SQL tab, a Java class's Description tab, or an external environment object's Contents tab, would either have caused Sybase Central to crash or hang, when selecting another object in the tree. This has been fixed.



CR:636315
CR Number:   636315
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.0 2561 27 Jul 2010 Fixed
11.0.1 2472 27 Jul 2010 Fixed
12.0.1 2986 23 Sep 2010 Fixed
23 Sep 2010 EOL'd version. Not to be Fixed.
Description
A database could have been corrupted when run with Lazy Loading and a prepared query, which required a temporary table, was reused. This has been corrected



CR:636316
CR Number:   636316
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.0 2561 27 Jul 2010 Fixed
12.0.1 2986 23 Sep 2010 Fixed
Description
If an application connected to a database that had either been initialized or upgraded with version 12 software, and subsequently made several external environment calls, then in very rare cases, the application might have received an empty result from the external environment and the error:

Permission denied: you do not have permission to execute the procedure "sajvm_JavaWorker"



would have been reported in the server console. This problem has now been fixed.



CR:636421
CR Number:   636421
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   15.5 ESD #3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Nov 2010 Presently Not Targeted For Any Future Release Of This Product
Description
Tested and reproduced with Interactive SQL 11.0.1 2430 from PC Client 15.5



Interactive SQL reaches 100% CPU when larger sql files are opened and scrolled. Depending on the machine processor (Pentium IV or older Pentium D), the performance gets very bad, or, according to customer's test, DBISQL can even hang.



CR:636422
CR Number:   636422
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.0 2561 27 Jul 2010 Fixed
12.0.1 2987 23 Sep 2010 Fixed
Description
The Interactive SQL utilirt can show results as a scrolling table, or as plain text. Changing this option using the "Show Results as" items in the "Data" menu, could have resulted in the option changing unexpectedly when disconnecting and reconnecting. The problem was that the option was not being saved consistently when it was changed. This has been fixed.



CR:636438
CR Number:   636438
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.0 2576 31 Aug 2010 Fixed
11.0.1 2474 31 Aug 2010 Fixed
12.0.1 3022 23 Sep 2010 Fixed
Description
The exception "ianywhere.ultralitej.implementation.JrException: UltraLiteJ Error[-280]: Publication 'ul_no_pub' not found" may have been reported for Connection.resetLastDownloadTime(Connection.SYNC_ALL_DB_PUB_NAME). A workaround would be to call Connection.getLastDownloadTime(Connection.SYNC_ALL_DB_PUB_NAME).getTime() prior to the call to resetLastDownloadTime(). This has been fixed.



CR:636442
CR Number:   636442
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.0 2561 28 Jul 2010 Fixed
12.0.1 2987 23 Sep 2010 Fixed
Description
If a server in a read-only scale-out system redirected a connection to another server due to the NodeType connection parameter, the internal count for the number of client connections could have been incorrect. This could have caused the server to:

- incorrectly prompt that there were active connections when shutting down the server

- incorrectly determine if an unconditional dbstop or STOP SERVER was required

- incorrectly enforce the -gm connection limit



This has been fixed.



CR:636508
CR Number:   636508
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)
11.0.1 2474 29 Jul 2010 Fixed
Description
Attempting to use an unnamed multi-column unique constraint as an index hint in the FROM clause, would have caused the error "Cannot find index named". This has been fixed.



CR:636520
CR Number:   636520
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.0 2484 28 Jul 2010 Fixed
12.0.1 2988 23 Sep 2010 Fixed
Description
Indexes may have become corrupt when performing delete operations. The corruption was more likely to occur on multi-column indexes when the data in the index consisted of disjoint sets of highly clustered data, and may manifest itself by causing assertions such as 106200, 106201, 106216, 106217, or as errors from dbvalid. This has now been fixed, Rebuilding the affected indexes using a server with this fix, by executing the "ALTER INDEX REBUILD" statement, should be done when experiencing indexing related problems.



CR:636535
CR Number:   636535
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.0 2573 24 Aug 2010 Fixed
12.0.1 3015 23 Sep 2010 Fixed
Description
When building a text index using an external prefilter or term breaker, the server

could have recorded the length of the document before prefiltering as the final length. This could have caused the scores reported by the CONTAINS queries to differ (in most cases be lower) than expected. The problem did not affect the text indexes built using no external libraries.

For example: If the following two values (documents)

'<html><body>A <b>very</b> nice day...</body></html>'

'<html><body>Peace and quiet at home</body></html>'



were indexed using a tag-removing prefilter, the lengths of the actual text were not equal, but the lengths recorded by the index would have included the lengths of the tags, making the document lengths equal. This has now been fixed.



CR:636544
CR Number:   636544
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.0 2562 29 Jul 2010 Fixed
11.0.1 2474 29 Jul 2010 Fixed
12.0.1 2989 23 Sep 2010 Fixed
Description
There is a tool in the "Connect" window which creates an ODBC DSN from the contents of the window. If a DSN had been selected in the window, its contents were not included in the newly created DSN which usually made the new DSN useless. Now, the new DSN contains the parameters of the selected DSN.



CR:636549
CR Number:   636549
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.0 2562 28 Jul 2010 Fixed
12.0.1 2988 23 Sep 2010 Fixed
Description
The file in which custom source control settings were saved was incorrectly named ".sybSourceControl999". It is now called ".sybSourceControl610", and has been moved into the same directory as the other configuration files for the Interactive SQL utility. If a custom source control system has already been configured, it will have to be reconfigured after this change.



CR:636555
CR Number:   636555
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.0 2562 03 Aug 2010 Fixed
12.0.1 2989 23 Sep 2010 Fixed
Description
Editing NCHAR, NVARCHAR, or LONGNVARCHAR values would have resulted in an error message of the form "The row could not be inserted. Column ... not found". This has been fixed.



Note, this problem would also have affected the "Data" tabs in Sybase Central.





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