远程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:542514
CR Number:   542514
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.0 1476 02 Sep 2008 Fixed
10.0.1 3757 02 Sep 2008 Fixed
11.0.1 1935 25 Nov 2008 Fixed
Description
In a SQL Anywhere SOAP response, binary data types greater than 250 bytes in length were not base64 encoded. This has been fixed, and applies to SQL Anywhere SOAP services that have been defined with DATATYPE ON or DATATYPE OUT.



CR:542516
CR Number:   542516
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1475 29 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
Shutting down the Relay Server Outbound Enabler could have caused the communication error message: "Communication error! Failed reading." to be logged in the Relay Server log file. This has been fixed.



CR:542519
CR Number:   542519
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)
11.0.0 1475 29 Aug 2008 Fixed
10.0.1 3756 29 Aug 2008 Fixed
9.0.2 3716 29 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
If an application made a large number of remote calls to fetch data from a JDBC based Remote Data Access server, then there was a chance the server would have crashed. For this problem to have occurred, the remote table and/or column names must have been longer than 30 characters. This problem has now been fixed.



CR:542521
CR Number:   542521
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1475 29 Aug 2008 Fixed
10.0.1 3756 29 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
On Unix systems, when an application crashed, rather that aborting or exiting, it may have gone intio a state of 100% CPU utilization. This would have occurred when the following conditions occurred in order:

1. The application loaded one of SQL Anywhere's client libraries (JDBC driver, ODBC

driver, DBLIB), which automatically install a signal handler.

2. The application installs its own signal handler function

3. An application fault happens which causes the application's signal handler to call the SA signal handler.

The SA signal handler will return without causingan abort and the application fault would have been re-triggered. The re-trigger of the signal and the return without handling the signal generated 100% CPU utilization. This has been fixed.



CR:542522
CR Number:   542522
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1475 28 Aug 2008 Fixed
9.0.2 3716 28 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
In rare cases, executing an invalid ALTER PROCEDURE statement could have caused a server crash or an incorrect error message. This has been fixed.



CR:542523
CR Number:   542523
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.0 1475 29 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
It was possible for a mirroring connection (i.e. a connection from one server to another server in a high availability configuration) to have failed with no error message being written to the console. This has been fixed.



CR:542524
CR Number:   542524
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1475 29 Aug 2008 Fixed
10.0.1 3756 29 Aug 2008 Fixed
9.0.2 3716 29 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
If an application on a Unix system used the iAnywhere JDBC driver to connect to a DB2 server using a 64-bit DB2 ODBC driver, then calling the Connection.getTransactionIsolationLevel() method may have crashed the client. This problem has been fixed.



CR:542528
CR Number:   542528
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1475 29 Aug 2008 Fixed
10.0.1 3756 29 Aug 2008 Fixed
11.0.1 1934 25 Nov 2008 Fixed
Description
An application using the iAnywhere JDBC driver may have in rare cases received a Null Pointer Exception when calling Connection.close(). This problem has now been fixed.



CR:542622
CR Number:   542622
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1476 29 Aug 2008 Fixed
11.0.1 1935 25 Nov 2008 Fixed
Description
If a database contained userids which had been assigned non-default login policies, running the Extraction utility (dbxtract) would have generated a reload script containing references to those users, even though some of them might not be defined in the extracted database. This has been fixed.



CR:542634
CR Number:   542634
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1476 02 Sep 2008 Fixed
11.0.1 1935 25 Nov 2008 Fixed
Description
In a MobiLink farm environment with Server-Initiated Sychronization, when the secondary notifier was under stress, it may have failed to have been promoted to the primary. This would have resulted in an I/O exception being thrown whenever a push or pollnow request arose. This problem has been fixed.



CR:542656
CR Number:   542656
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)
11.0.0 1476 02 Sep 2008 Fixed
11.0.1 1935 25 Nov 2008 Fixed
Description
When run on Windows Vista systems, selecting "Make Interactive SQL the default editor for .SQL files and plan files" in the "Options" dialog, did not make Interactive SQL the default editor. This has been fixed.



CR:542763
CR Number:   542763
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1480 03 Sep 2008 Fixed
11.0.1 1939 25 Nov 2008 Fixed
Description
UltraLite databases could have grown unnecessarily when blobs and clobs were updated. Pages from blobs/clobs on deleted rows were not bing properly released. This has been corrected.



CR:542768
CR Number:   542768
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1480 03 Sep 2008 Fixed
11.0.1 1939 25 Nov 2008 Fixed
Description
Incorrect parameters to the system functions LEFT(), RIGHT() and INSERTSTR() could have caused a Java exception. This has been fixed.



CR:542812
CR Number:   542812
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Sep 2008 Fixed
Description
If the Administration Tools were the only components installed, the tools would not run correctly, eg., Sybase Central would fail to load the SQL Anywhere plugin. The jodbc.jar file was not being installed. This has been corrected.



CR:542825
CR Number:   542825
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 1939 04 Mar 2009 Fixed
11.0.0 1480 04 Mar 2009 Fixed
10.0.1 3758 04 Mar 2009 Fixed
Description
SQL Anywhere attempts to create a single physical data structure when multiple indexes on the same table are created with identical properties. The dbspace id recorded in the catalog for a newly created index referred to the dbspace id for the new logical index instead of the dbspace id of the existing physical index shared by the new index. This problem has been corrected, and the server will now record the dbspace id of the existing index whenever sharing takes place.



Note, existing databases with this problem can be corrected by dropping and recreating the logical indexes sharing a physical index. Whether or not an existing database has an instance of this problem can be determined by checking the physical_index_id and the file_id fields of the system view SYS.SYSIDX. The problem cases exist in a database when two indexes on the same table have the same physical_index_id values but their file_id values differ.



CR:542840
CR Number:   542840
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)
11.0.0 1482 04 Sep 2008 Fixed
10.0.1 3759 04 Sep 2008 Fixed
9.0.2 3720 04 Sep 2008 Fixed
11.0.1 1941 25 Nov 2008 Fixed
Description
If a Disconnect event was defined and a connection was dropped using DROP CONNECTION, the value of event_parameter('DisconnectReason') would have been incorrect when evaluated inside the event handler. This has been fixed.



CR:542868
CR Number:   542868
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)
11.0.0 1482 05 Sep 2008 Fixed
10.0.1 3759 05 Sep 2008 Fixed
11.0.1 1941 25 Nov 2008 Fixed
Description
In rare circumstances the server could have hung updating a blob column. This has been fixed.



CR:542949
CR Number:   542949
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)
11.0.0 1481 03 Sep 2008 Fixed
11.0.1 1940 25 Nov 2008 Fixed
Description
Sybase Central would sometimes have failed to populate the All Connected Users tab and failed to graph statistics on the Performance Monitor tab. These problems have been fixed.



CR:542959
CR Number:   542959
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1481 03 Sep 2008 Fixed
10.0.1 3759 03 Sep 2008 Fixed
11.0.1 1940 25 Nov 2008 Fixed
Description
The Interactive SQL utility's (dbisqlc) OUTPUT statement was incorrectly using the value (NULL) for null values, instead of using a blank value. This has been fixed.



This can be worked around by using dbisql or by correcting the output_nulls Interactive SQL option using the statement:

set option output_nulls = ''



CR:542962
CR Number:   542962
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1487 08 Sep 2008 Fixed
10.0.1 3761 08 Sep 2008 Fixed
11.0.1 1946 25 Nov 2008 Fixed
Description
On a busy server, if an application made an external environment or Java call which could have resulted in a thread deadlock error, there was a small possibility that the server would have hung. This problem has now been fixed.



CR:542967
CR Number:   542967
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1488 04 Sep 2008 Fixed
11.0.1 1947 25 Nov 2008 Fixed
Description
If the Unload utility (dbunload) was used to unload an existing database with comments on text indexes or text configurations, the comments were not unloaded. This has been fixed.



CR:542977
CR Number:   542977
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)
11.0.0 1481 03 Sep 2008 Fixed
11.0.1 1940 25 Nov 2008 Fixed
Description
If a connection was using the CLR External Environment, and the CLR External Environment was left idle for ten minutes or so, then that connection would no longer have been able to make CLR calls, even though other connections were able to use the CLR External Environment without difficulty. This problem has now been fixed.



Note that a simple workaround to the problem is to execute:



STOP EXTERNAL ENVIRONMENT CLR



on the connection that is having difficulty executing CLR calls. Unfortunately, stopping the CLR External Environment will have the side effect of dropping all static variables for that particular connection.



CR:543002
CR Number:   543002
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)
11.0.0 1481 04 Sep 2008 Fixed
10.0.1 3759 04 Sep 2008 Fixed
9.0.2 3720 04 Sep 2008 Fixed
11.0.1 1940 26 Nov 2008 Fixed
Description
An HTTP server response returning an error status, such as "404 Not Found", was returned in the server's language and the Content-Type header incorrectly specifies charset=ISO-8859-1. This has been fixed so that HTTP status messages are now always returned in the English language. Therefore the Content-Type header charset=ISO-8859-1 will now be correct.



CR:543006
CR Number:   543006
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.0 1481 04 Sep 2008 Fixed
10.0.1 3759 04 Sep 2008 Fixed
11.0.1 1940 26 Nov 2008 Fixed
Description
If an application was using a JDBC based Remote Data Access server to fetch long multi-byte string data, then there was a possibility the server would have crashed. This problem has been fixed.



CR:543011
CR Number:   543011
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)
11.0.0 1483 05 Sep 2008 Fixed
11.0.1 1941 26 Nov 2008 Fixed
Description
If the Windows desktop was used to associate ".sql" files with the Interactive SQL utility (dbisql), double-clicking a ".sql" file would probably not have launched dbisql. This has been fixed so that now it does, as long as the desktop was told to open the file with "dbisql.exe" (i.e. NOT "dbisql.com"). Before this change, the only reliable way to associate .SQL files with dbisql was to use the "Make Interactive SQL the default editor..." check box in the "Options" window.



CR:543069
CR Number:   543069
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)
11.0.0 1511 02 Oct 2008 Fixed
10.0.1 3775 02 Oct 2008 Fixed
11.0.1 1970 26 Nov 2008 Fixed
Description
The server could have leaked memory, possibly leading to an 'Out of Memory' error, when using TDS connections (eg. jConnect) that fetched string data. This has now been corrected.



CR:543100
CR Number:   543100
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)
11.0.0 1482 04 Sep 2008 Fixed
11.0.1 1941 26 Nov 2008 Fixed
Description
The table editor would have allowed marking all columns in a table for deletion. If this was attempted in multiple operations; that is, by selecting some of the columns and pressing the Delete key, and then selecting the remaining columns and pressing the Delete key again. In such cases, attempting to save the table would have failed while attempting to delete the last column in the table. This has been fixed. Now it is no longer possible to mark all columns for deletion. Attempting to do so displays an error message.



CR:543127
CR Number:   543127
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)
11.0.0 1483 08 Sep 2008 Fixed
11.0.1 1941 26 Nov 2008 Fixed
Description
After executing the Unload utility (dbunload) with the -d option (data only), the resulting reload.sql file would have contained calls to the non-existent function sa_unload_display_table_status(). The same problem would have occurred when using the Sybase Central Unload wizard and chosing "Unload data only". This has been fixed.



CR:543135
CR Number:   543135
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)
11.0.0 1483 08 Sep 2008 Fixed
11.0.1 1941 26 Nov 2008 Fixed
Description
When the Interactive SQL utility (dbisql) was started with the -q "Suppress non-critical messages" command line option, it did not suppressing the following warnings:

- "Interactive SQL is currently configured to quit if a SQL statement fails to execute"

- "You are connected to an database which is not explicitly supported"

- "ODBC tracing is currently enabled"

This has been corrected and these warnings are now suppressed when "-q" is used.



CR:543210
CR Number:   543210
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1503 24 Sep 2008 Fixed
11.0.1 1955 26 Nov 2008 Fixed
Description
Queries with a large number of aggregate expressions in the select list, but without a GROUP BY clause, could have crashed the server. This has been fixed.



A workaround for this problem is to add a GROUP BY clause.



CR:543216
CR Number:   543216
Product Name:   UltraLite
Product Component:   UltraLite Schema Painter
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3751 07 Nov 2008 Fixed
Description
The Schema Painter would have failed to save schema if it contained multibyte characters. This has been fixed.



CR:543231
CR Number:   543231
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)
11.0.0 1484 08 Sep 2008 Fixed
10.0.1 3760 08 Sep 2008 Fixed
9.0.2 3721 08 Sep 2008 Fixed
11.0.1 1942 26 Nov 2008 Fixed
Description
The OK button on the "Connect" dialog could have failed to do anything if all of the following were true:

1. The "Fast launcher" option was enabled

2. The "Connect" window was opened and left open in one DBISQL window

3. A "Connect" window was opened and closed from another DBISQL window

This has been fixed. To workaround the problem, close the "Connect" window and reopen it.



CR:543245
CR Number:   543245
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)
11.0.0 1484 09 Sep 2008 Fixed
10.0.1 3760 09 Sep 2008 Fixed
11.0.1 1942 26 Nov 2008 Fixed
Description
In certain configurations, executing the REMOTE RESET statement can cause the server to crash. This has been fixed.



CR:543248
CR Number:   543248
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1484 05 Sep 2008 Fixed
10.0.1 3760 05 Sep 2008 Fixed
11.0.1 1942 26 Nov 2008 Fixed
Description
If a comment was created for a primary key, the comment would not have been unloaded by the Unload utility (dbunload). This has been fixed.



CR:543254
CR Number:   543254
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)
11.0.0 1488 10 Sep 2008 Fixed
11.0.1 1947 26 Nov 2008 Fixed
Description
The value for the "EncryptedPassword" connection parameter was visible in clear text on the "Advanced" page of the "Connect" window. This has been fixed.



CR:543261
CR Number:   543261
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)
11.0.0 1491 09 Sep 2008 Fixed
10.0.1 3764 09 Sep 2008 Fixed
11.0.1 1950 26 Nov 2008 Fixed
Description
The server could have hang while concurrently updating blob columns. This has been fixed.



CR:543272
CR Number:   543272
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)
9.0.2 3726 09 Sep 2008 Fixed
Description
Second and subsequent connections from a single application may have used TCP/SPX options specified by the first connection made by that application using the same protocol. This could potentially have resulted in a connection being made to the wrong server. This has been fixed.



CR:543367
CR Number:   543367
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)
11.0.0 1487 09 Sep 2008 Fixed
11.0.1 1945 26 Nov 2008 Fixed
Description
Clicking the "Options" button in the Query Editor window did not automatically select the "Query Editor" tab in the "Options" window as it did in previous versions of Interactive SQL. This has been corrected.



CR:543375
CR Number:   543375
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1494 09 Sep 2008 Fixed
11.0.1 1950 26 Nov 2008 Fixed
Description
Failure of a statement which was partially executed and involved either clobs or blobs, could have caused unneccessary database growth. Blobs and clobs were not being correctly discarded following statement failure. This has been corrected.



CR:543380
CR Number:   543380
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)
11.0.0 1487 09 Sep 2008 Fixed
11.0.1 1946 26 Nov 2008 Fixed
Description
Clicking the "Create a synchronization subscription" task for a MobiLink user would have caused nothing to happen. Now, the "Create Synchronization Subscription Wizard" is opened.



CR:543391
CR Number:   543391
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1487 09 Sep 2008 Fixed
11.0.1 1946 26 Nov 2008 Fixed
Description
A security flaw in the MobiLink server was fixed.



CR:543394
CR Number:   543394
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)
11.0.0 1487 09 Sep 2008 Fixed
11.0.1 1946 26 Nov 2008 Fixed
Description
An INSERT, UPDATE or DELETE statement executed on a table with an IMMEDIATE text index could have caused correctness issues for subsequent CONTAINS queries that used the text index. For the problem to have occurred, very long string values (over 32K characters) had to have been indexed by the text index and modified by the INSERT, UPDATE or DELETE statement. This has been fixed.



For existing databases with IMMEDIATE text indexes that could be affected by this issue, dropping and recreating the text index is recommended.



CR:543397
CR Number:   543397
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1488 10 Sep 2008 Fixed
10.0.1 3761 10 Sep 2008 Fixed
11.0.1 1947 26 Nov 2008 Fixed
Description
If an application was connected via jConnect and attempted to query the column metadata of a table containing a DATE or TIME column, then the server would have incorrectly returned the error -186 'Subquery cannot return more than one row'. When support for the TDS DATE and TIME datatypes was added, the metadata information in spt_jdatatype_info was not properly updated. This has now been fixed.



CR:543478
CR Number:   543478
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 3820 22 Dec 2008 Fixed
9.0.2 3770 22 Dec 2008 Fixed
Description
In very rare circumstances, an auto-shutdown of a database could have caused the server to crash, if the server was in the process of shrinking the cache at the same time. This problem has been fixed.



CR:543491
CR Number:   543491
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)
11.0.0 1504 10 Sep 2008 Fixed
11.0.1 1963 26 Nov 2008 Fixed
Description
Sybase Central could have crash while attempting to fetch the messages for a server. This has been fixed.



CR:543518
CR Number:   543518
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.0 1489 10 Sep 2008 Fixed
10.0.1 3763 10 Sep 2008 Fixed
11.0.1 1948 26 Nov 2008 Fixed
Description
The SQL Anywhere http option "AcceptCharset" generated a SQL error with "SQLCODE -939 Invalid setting for HTTP option" when a match was not found within the union of the client's Accept-Charset list and the server's AcceptCharset http option charset list. This has been fixed.



With this change a SQL error is now generated only if the http option value is malformed or none of the charsets within the value are supported by SQL Anywhere. In addition, the run-time selection of a suitable response charset has changed to provide more control over the charset selection. Primarily, given that the union of server and client charset lists are empty, a charset is now selected based on the server's AcceptCharset http option value not from the client's Accept-Charset request header. The old behaviour is supported by allowing an asterisk (*) to be specified within the AcceptCharset http option list. An asterisk has the meaning that, should the client/server charset union be empty, try to use the preferred charset specified by the client. If none are found, then select from the server's AcceptCharset http option list. A summary of the processing priority of the various cases follow:



Processing Priority cases:



1 - If a charset can be selected from the union of charsets from the AcceptCharset http option and the Accept-Charset HTTP request header, then it will be used (no change in behaviour).

2 - If the client sends an Accept-Charset HTTP request header, but none of the charsets match the AcceptCharset http option, then use the first and/or highest q-value charset specified within the AcceptCharset http option. (This is a behaviour change).

3 - If the client does not send an Accept-Charset HTTP request header, select the first and/or highest q-value charset specified within the AcceptCharset http option (no change in behaviour).



Caveats:

a. Within the AcceptCharset http option value, the placement of the '+' token (which specifies the use of database charset whenever possible regardless of the q-value assigned to it by the client) is now significant. If '+' is specified anywhere within the http option value then case 1) will be true if the client happens to specify the database charset. If '+' is specified first and/or it has the highest q-value, then cases 2) and 3) above would resolve to using the database charset.

b. Within the AcceptCharset http option value, an asterisk (*) signifies that any client charset (as specified by its Accept-Charset HTTP header) should be considered prior to defaulting to the http option charset list. The best match within the union of client/server charsets ( case 1) ) has priority. In the processing priority cases above, having failed case 1) the client's Accept-Charset is scanned for a suitable charset. If a suitable charset is not found, then a charset is selected according to case 3).

c. SQLCODE -939 error is only generated if the http option value is malformed or none of the specified charsets within its value is supported by SQL Anywhere. The database charset is selected whenever a SQLCODE -939 error is generated.



CR:543525
CR Number:   543525
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 3723 11 Sep 2008 Fixed
Description
Issuing a REMOTE RESET, or granting REMOTE to a user, when the log offset was larger than 4GB could have caused the server to crash. This has been fixed.



CR:543541
CR Number:   543541
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1488 10 Sep 2008 Fixed
10.0.1 3762 10 Sep 2008 Fixed
11.0.1 1947 26 Nov 2008 Fixed
Description
If an application was connected via the iAnywhere JDBC driver, and the application had made DatabaseMetaData calls, then calling Connection.close() would have given a NullPointerException if the server has already closed the connection. This problem has now been fixed.



CR:543548
CR Number:   543548
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1488 11 Sep 2008 Fixed
11.0.1 1947 26 Nov 2008 Fixed
Description
The version number built into the UltraLiteJ.jad file for RIM BlackBerry deployment would sometimes have been incorrecting generated. This has been fixed.



CR:543552
CR Number:   543552
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1474 11 Sep 2008 Fixed
11.0.1 1933 26 Nov 2008 Fixed
Description
In a scenario where a table had a large number of initial inserts followed by a large number of deletes, inserts or updates, where the number of deletes that had taken place were always greater than the number of inserts, the database may have become corrupted. These operations may have occur via program initiated operations, or via synchronization operations. This has been fixed. Existing databases that have not yet been corrupted will be fixed when the UltraLiteJ library is updated.



CR:543562
CR Number:   543562
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1490 11 Sep 2008 Fixed
10.0.1 3763 11 Sep 2008 Fixed
9.0.2 3723 11 Sep 2008 Fixed
11.0.1 1949 26 Nov 2008 Fixed
Description
If an application was connected using jConnect and attempted to fetch a result set containing a large number of columns (more than 3000), then the application would have failed with a TDS protocol error. This problem has now been fixed.

Note, that in order to fetch such a result set, the application must be using jConnect 6.x.



CR:543631
CR Number:   543631
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)
10.0.1 3768 22 Sep 2008 Fixed
Description
If a simple statement was executed with a particular form of ORDER BY clause, then the server could have crashed while executing the statement. This has been fixed.



CR:543647
CR Number:   543647
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)
10.0.1 3768 19 Sep 2008 Fixed
Description
The REFRESH MATERIALIZED VIEW statement is used to rebuild the contents of a materialized view. When this statement was used inside a stored procedure, execution of the procedure could have caused the server to crash under certain circumstances. This problem has been corrected, and the server now executes the stored procedure correctly. The problem can be avoided by using EXECUTE IMMEDIATE with the REFRESH statement.



CR:543652
CR Number:   543652
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)
11.0.0 1489 10 Sep 2008 Fixed
11.0.1 1948 26 Nov 2008 Fixed
Description
The stored procedure debugger would not allow breakpoints to be set within triggers. This has been fixed.



CR:543656
CR Number:   543656
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)
11.0.0 1503 23 Sep 2008 Fixed
11.0.1 1961 26 Nov 2008 Fixed
Description
A database that had gone through recovery after an abnormal shutdown could have been unreadable by the MobiLink Client dbmlsync. Dbmlsync would have reported that the transaction log was corrupt, even though the server successfully recovered. At the end of recovery, the server performs a checkpoint. This checkpoint was correctly updated in the database and written to the transaction log, but was not being flushed to the log properly. This has now been fixed.



The original crashed database will need to be recovered with the fixed server.



CR:543658
CR Number:   543658
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)
11.0.0 1489 23 Sep 2008 Fixed
11.0.1 1948 26 Nov 2008 Fixed
Description
If the property sheet for a column was opened and its comment updated when an index or text index was selected in the tree, then the updated comment would not have appeared in the right pane. This has been fixed.



CR:543689
CR Number:   543689
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)
11.0.0 1489 11 Sep 2008 Fixed
11.0.1 1948 26 Nov 2008 Fixed
Description
Sybase Central could have crashed, if when attempting to change a table's primary

key from within the Table Editor the primary key was dropped, but could not be re-created. This has been fixed.



CR:543694
CR Number:   543694
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.0 1503 25 Sep 2008 Fixed
10.0.1 3771 24 Sep 2008 Fixed
11.0.1 1961 26 Nov 2008 Fixed
Description
When using Snapshot isolation, WITH HOLD cursors would have failed to see rows modified by their own connection after the connection executed a COMMIT. This has been fixed so that when using Snapshot, Statement-Snapshot or Readonly-Statement-Snapshot isolation,

WITH HOLD cursors will see a snapshot of all rows committed at the snapshot start time, as well as all modifications done by the current connection since the start of the transaction within which the cursor was open.



Note that the contents of the cursors are unaffected by the current transaction committing.



CR:543695
CR Number:   543695
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1532 13 Nov 2008 Fixed
10.0.1 3797 13 Nov 2008 Fixed
9.0.2 3752 13 Nov 2008 Fixed
11.0.1 2018 26 Nov 2008 Fixed
Description
Output parameters for stored procedure calls that were marked as indirect (DBTYPE_BYREF) were not handled properly by the SQL Anywhere OLE DB provider. This problem has been corrected.



CR:543803
CR Number:   543803
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)
11.0.0 1490 11 Sep 2008 Fixed
11.0.1 1949 26 Nov 2008 Fixed
Description
On the "Request Logging" page of a server's property sheet, the drop-down list adjacent to the "All connections to the following database:" radio button would actually have listed connections, not databases. This has been fixed.



CR:543812
CR Number:   543812
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1498 18 Sep 2008 Fixed
10.0.1 3767 18 Sep 2008 Fixed
11.0.1 1957 26 Nov 2008 Fixed
Description
If a user caused an event to fire, e.g. by disconnecting to fire a Disconnect event, and another user immediately caused that user to be dropped, the server would have crashed. This has been fixed.
Workaround Description
 Provide an engine name for reloading the 11 database since it isn't running at the time of



CR:543814
CR Number:   543814
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)
Description
The ansi_substring option, which was removed in the 11.0.0 release, has been re-instated. The default value for the option is ON, as it was in version 10. For databases created with 11.0.0 where the option did not exist, a setting for PUBLIC.ansi_substring must be defined before attempting to set the option for another user and before executing "set temporary option ansi_substring ...".



CR:543826
CR Number:   543826
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.0 1490 12 Sep 2008 Fixed
10.0.1 3763 12 Sep 2008 Fixed
11.0.1 1949 26 Nov 2008 Fixed
Description
If an application called sp_remote_columns to determine the domain ids of an UltraLite table, and the UltraLite table contained a UniqueIdentifier column, then the domain id of the uniqueidentifer column would have been incorrectly returned as Char. This problem has now been fixed.



CR:543835
CR Number:   543835
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.0 1491 12 Sep 2008 Fixed
10.0.1 3764 12 Sep 2008 Fixed
11.0.1 1950 26 Nov 2008 Fixed
Description
The functions YEARS(), MONTHS(), WEEKS(), DAYS(), HOURS(), MINUTES(), and SECONDS() could have been described with the incorrect data type. If these functions were used with two parameters with the second parameter an untyped expression, then the expression was assigned the incorrect data type. Untyped expressions include NULL constant literals and host variable that are not yet bound to a type, for example during DESCRIBE.

For example, the following expression was incorrectly described as TIMESTAMP (it should be INT):

select months( current timestamp, NULL )

This incorrect type could have affected more complex expressions composed with one of the affected functions as an argument. This problem has been fixed.



Note, this change could alter the definition of materialized views; views containing the affected constructs should be refreshed.



CR:543888
CR Number:   543888
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1505 18 Sep 2008 Fixed
10.0.1 3771 18 Sep 2008 Fixed
9.0.2 3730 18 Sep 2008 Fixed
11.0.1 1963 26 Nov 2008 Fixed
12.0.0.1 1963 26 Nov 2008 Fixed
Description
The SQL Anywhere OLE DB provider did not support multiple parameter sets in the ICommand::Execute method. The number of parameter sets is specified in the cParamSets field of the DBPARAMS structure, for example:



HRESULT Execute (

IUnknown牋牋*pUnkOuter,

REFIID牋牋牋牋riid,

DBPARAMS牋牋*pParams,

DBROWCOUNT牋*pcRowsAffected,

IUnknown牋牋**ppRowset);



struct DBPARAMS {

void *pData;

DB_UPARAMS cParamSets;

HACCESSOR hAccessor;

};



This is now supported, so it is now possible to execute one INSERT statement and specify several sets of parameters in order to insert several rows into a table.



Note the following OLE DB specification restriction:

Sets of multiple parameters (cParamSets is greater than one) can be specified only if DBPROP_MULTIPLEPARAMSETS is VARIANT_TRUE and the command does not return any rowsets.



This means that multiple parameterized SELECT statements can not be executed that would each return a result set. For the SQL Anywhere provider, DBPROP_MULTIPLEPARAMSETS is VARIANT_TRUE (and always has been).



CR:543910
CR Number:   543910
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.0 1498 22 Sep 2008 Fixed
10.0.1 3767 22 Sep 2008 Fixed
9.0.2 3727 22 Sep 2008 Fixed
11.0.1 1957 26 Nov 2008 Fixed
Description
The version 10 and 11 servers were truncating 32-byte names to 31 bytes. So when a version 10 or 11 client attempted a shared memory connection specifying a 32-byte server name that had a common prefix of exactly 31 bytes with a running version 10 or 11 server that also has a 31-byte name, the connection attempt would have failed. As well, if a version 10 or 11 client attempted a shared memory connection specifying a server name that had a common prefix of exactly 31 bytes with a running version 9 or prior server that had a name longer than 31 bytes, the connection attempt would have failed. This problem has been fixed. Note that for version 10 and 11, the fix affects both client and server. For version 9, the fix is just to the server. However, an unmodified version 10 or 11 client will be able to establish such a connection against an unmodified version 9

server.



CR:543940
CR Number:   543940
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1499 19 Sep 2008 Fixed
10.0.1 3768 19 Sep 2008 Fixed
11.0.1 1958 26 Nov 2008 Fixed
Description
The server could have stop responding and continue to consume CPU when processing the SUBSTR() function. For this to have occurred, the SUBSTR() must appear on the right hand side of a string concatenation operation and must also be over a string that comes from a row in a table. Additionally, the string data must be greater than one database page in length. Even if all these conditions are met, it is very unlikely that this bug will be hit, as it depends on other internal server conditions as well. This has now been fixed.
Workaround Description
 Adding message statement at various points

through-out all the various functions seems

to be a way to avoid the hang.



CR:543943
CR Number:   543943
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)
11.0.0 1491 12 Sep 2008 Fixed
11.0.1 1950 26 Nov 2008 Fixed
Description
When using the Table editor to create a column or modify its data type, if the data type was set in the column's property sheet, then extraneous NO INDEX or COMPRESSED clauses could have been added to the CREATE TABLE or ALTER TABLE statement. This has been fixed.



CR:543955
CR Number:   543955
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1430 23 Sep 2008 Fixed
11.0.1 1889 26 Nov 2008 Fixed
Description
Some files for subfeatures would still have be included in the install created by the Deployment Wizard, even if their parent feature was unselected. This has been fixed.



CR:544030
CR Number:   544030
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1495 16 Sep 2008 Fixed
11.0.1 1955 26 Nov 2008 Fixed
Description
Triggers defined on global temporary tables were not fired. This has been fixed.



CR:544047
CR Number:   544047
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1513 03 Oct 2008 Fixed
10.0.1 3777 03 Oct 2008 Fixed
11.0.1 1973 26 Nov 2008 Fixed
Description
Validation of a database may have reported that some tables contained orphaned blobs. This was only true for tables that were stored in a dbspace other than the SYSTEM dbspace. This should also have only occurred on databases using snapshot isolation. Databases containing these orphaned blobs have pages which are being wasted. The only way to free these pages for reuse is to rebuild the database file. This problem has been fix so that generating orphaned blobs should no longer be possible.



CR:544069
CR Number:   544069
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 3725 16 Sep 2008 Fixed
Description
The server could have crashed if two or more connections were simultaneously scanning a table for the first time after the server was started. This has been fixed.



CR:544094
CR Number:   544094
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)
11.0.0 1494 16 Sep 2008 Fixed
11.0.1 1954 26 Nov 2008 Fixed
Description
When creating a procedure or function, if an existing procedure or function was altered and a language clause was specified with an undefined language, then the server would have failed to return an error. This problem has now been fixed and the server now correctly returns an error.



CR:544101
CR Number:   544101
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)
11.0.0 1506 16 Sep 2008 Fixed
11.0.1 1965 26 Nov 2008 Fixed
Description
The initial width of the "Plan Viewer" window could have been too narrow to display all of its contents. As a result, the "Get Plan" button could have been hidden. This has been fixed.



CR:544181
CR Number:   544181
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.0 1514 08 Oct 2008 Fixed
10.0.1 3778 08 Oct 2008 Fixed
11.0.1 1955 26 Nov 2008 Fixed
Description
Calling the system function traced_plan() for a query containing captured host variables could have failed and return a conversion error. When using Profiling Mode in the Sybase Central plugin, this caused the profiling browser to fail to display a "Best Guessed Plan" for a query whose original graphical plan was not captured. This has been fixed.



CR:544187
CR Number:   544187
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)
11.0.0 1510 29 Sep 2008 Fixed
10.0.1 3773 29 Sep 2008 Fixed
9.0.2 3732 01 Oct 2008 Fixed
11.0.1 1969 26 Nov 2008 Fixed
Description
A server could have failed to start if another server was starting at the same time. The server that failed to start would have displayed the error "Database cannot be started -- No such file or directory". The error message was also misleading since the database file did exist; the server actually had a problem opening the database's temporary file. This has been fixed.



CR:544191
CR Number:   544191
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 3730 24 Sep 2008 Fixed
Description
In some circumstances, host variable references in batches could have caused a server crash. This has been fixed so that the error "Host variables may not be used within a batch" is now returned.



CR:544199
CR Number:   544199
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)
11.0.0 1503 23 Sep 2008 Fixed
10.0.1 3769 23 Sep 2008 Fixed
11.0.1 1962 26 Nov 2008 Fixed
Description
In rare situations, the server could have crashed during graphical plan construction. For the problem to occur, one of the tables used in the query had to have a unique index and a foreign key index sharing the same columns and settings, and the index had to be considered or used for the query. This has been fixed.



CR:544213
CR Number:   544213
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)
11.0.0 1495 16 Sep 2008 Fixed
11.0.1 1955 26 Nov 2008 Fixed
Description
Comments on the following object types were not preserved by dbunload:

dbspaces

Java classes

Java jars

external environments

external environment objects

login policies

This has been fixed.



CR:544214
CR Number:   544214
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1495 18 Sep 2008 Fixed
10.0.1 3766 18 Sep 2008 Fixed
11.0.1 1955 26 Nov 2008 Fixed
Description
The changes for Engineering case 535861 caused the OLE DB schema support stored procedures to not be installed in newly created databases. This problem has now been corrected.



As a work-around, databases can be upgraded using dbupgrad.exe or by executing an ALTER DATABASE UPGRADE PROCEDURE ON statement.



CR:544318
CR Number:   544318
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)
10.0.1 3769 23 Sep 2008 Fixed
Description
Specific forms of SELECT statements could have caused a server crash when opened with particular cursor types. This problem has been fixed.



As an interim work-around, the server command line switch "-hW AllowBypassCosted" can be specified to avoid this problem.



CR:544321
CR Number:   544321
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Windows 2000
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1502 23 Sep 2008 Fixed
10.0.1 3769 15 Oct 2008 Fixed
11.0.1 1961 26 Nov 2008 Fixed
Description
An HTTPS synchronization through a proxy server that required authentication would have failed. When using HTTPS through a proxy server, the client first sends a CONNECT HTTP request to establish a channel through the proxy. Unfortunately, authentication challenges was only active for GET and POST requests. This has been corrected so that CONNECT requests are now active as well.



CR:544343
CR Number:   544343
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2043 25 Mar 2009 Fixed
Description
When the Deployment wizard was used to create an installment that included Sybase Central and the SQL Anywhere plugin, the plugin was not automatically installed in Sybase Central. This has been fixed



CR:544350
CR Number:   544350
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1496 18 Sep 2008 Fixed
11.0.1 1956 26 Nov 2008 Fixed
Description
A user could have dropped a publication whose upload was in an unknown state. For example, the synchronization failed due to a communication error before the upload acknowledgement was received from MobiLink. Dropping a publication whose upload status is unknown could result in lost upload data or duplicate uploads. This has been fixed. Attempting to drop a publication in such a state will now result in a SQLE_SYNC_STATUS_UNKNOWN error.



CR:544460
CR Number:   544460
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3775 02 Oct 2008 Fixed
Description
Particular forms of complex predicates could have caused the server to crash when executed against a string column with declared size no more than 7 bytes. This has been fixed.



CR:544486
CR Number:   544486
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1498 19 Sep 2008 Fixed
10.0.1 3767 19 Sep 2008 Fixed
9.0.2 3727 19 Sep 2008 Fixed
11.0.1 1957 26 Nov 2008 Fixed
Description
If an application connected using Open Client attempted to fetch a result set containing a large number of columns (more than 3000), then the application would have failed with a TDS protocol error. This problem has now been fixed.



Note, that in order to fetch such a result set, the application must be using Open Client 15.



CR:544496
CR Number:   544496
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)
11.0.0 1489 23 Sep 2008 Fixed
10.0.1 3769 23 Sep 2008 Fixed
9.0.2 3729 23 Sep 2008 Fixed
11.0.1 1948 26 Nov 2008 Fixed
Description
If the server was started with the "-x none" command line option, and without the -xs option, then calling an external web procedure would have caused the server to crash. This has been fixed.



CR:544525
CR Number:   544525
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1498 22 Sep 2008 Fixed
11.0.1 1958 26 Nov 2008 Fixed
Description
If a publication that had been previous used in a synchronization was dropped, the next publication created would not have been able to synchronize due to a progress offset error from MobiLink. This has been fixed.



CR:544612
CR Number:   544612
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)
11.0.0 1499 19 Sep 2008 Fixed
11.0.1 1958 26 Nov 2008 Fixed
Description
If a row was inserted into a database table using the table in the "Results" panel, and the table contained a non-nullable TIME, DATE, or TIMESTAMP column, the column was initially filled with the current time or date in a format that was not necessarily parsable by the database. This has been fixed.



CR:544613
CR Number:   544613
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1498 22 Sep 2008 Fixed
10.0.1 3767 25 Sep 2008 Fixed
9.0.2 3728 25 Sep 2008 Fixed
11.0.1 1957 26 Nov 2008 Fixed
Description
In an SIS environment, if a MobiLink client device went offline (device a), and then another client device (device B) came online with the same device address (ie. IP address/port) as A, and an SIS UDP notification for client A was sent by the notifier, then client B would have received and rejected the notification with an error similar to the following:

Error: <Notifier(QAnyNotifier_client)>: Request 1604437321 is accepted by invalid respondent 'ias_receiver_lsn'. Please check the message filters on the listener



This error would have happened whenever a UDP notification for client A was sent, resulting in wasteful SIS notifications. This has now been fixed. For 9.0.2, the fix was made only for MobiLink with messaging (QAnywhere) for ASA consolidated databases. In later versions, the fix applies to all MobiLink Notifiers in all supported consolidated databases.



CR:544614
CR Number:   544614
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)
11.0.0 1499 22 Sep 2008 Fixed
11.0.1 1958 27 Nov 2008 Fixed
Description
Pressing the F2 key while inserting or updating a row in the "Results" pane table, would have resulted in an internal error. This has been fixed by ignoring the F2 key if editing mode is already entered.



CR:544626
CR Number:   544626
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Linux
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1519 20 Oct 2008 Fixed
10.0.1 3785 20 Oct 2008 Fixed
11.0.1 1988 27 Nov 2008 Fixed
Description
The iAnywhere JDBC driver may have crashed when allocating a new statement, and the Java VM was out of memory. This has been fixed. The driver will now either fail gracefully, or assert, depending on the circumstances.
Workaround Description
 none



CR:544641
CR Number:   544641
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)
11.0.0 1499 22 Sep 2008 Fixed
11.0.1 1935 27 Nov 2008 Fixed
Description
When running on Windows systems, the server could have taken longer than necessary to shutdown, or could even have crashed during the shutdown process. This has now been fixed.



CR:544651
CR Number:   544651
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)
11.0.0 1502 22 Sep 2008 Fixed
11.0.1 1958 27 Nov 2008 Fixed
Description
Under rare circumstances, a full text search could have returned incorrect results. For this problem to occur, the database with the text index had to have been refreshed at least once and then moved between platforms with different byte orderings. This has now been fixed. No action needs to be taken for databases with text indexes that were created on little-endian machines and were never refreshed or updated on big-endian machines. Text indexes will need to be truncated and refreshed (for MANUAL and AUTO text indexes), or recreated (for IMMEDIATE indexes), after applying this fix if they were created or refreshed on a big-endian machine.



CR:544669
CR Number:   544669
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)
11.0.0 1506 29 Sep 2008 Fixed
10.0.1 3772 29 Sep 2008 Fixed
9.0.2 3730 29 Sep 2008 Fixed
11.0.1 1965 27 Nov 2008 Fixed
Description
If a column histogram incorrectly contained a selectivity estimate of 100% for the NULL values, the best plan found by the optimizer could have been very inefficient. This problem affected the computation of the selectivity estimation of predicates of the form "T.X theta expression" (theta can be =, <>, >, >=, < or <=) which would have incorrectly been computed as 0%. A change has been made to the optimizer so that it no longer trusts a NULL selectivity estimation of 100%, instead it uses the computed selectivity estimation of (100% - epsilon).





To test the estimated selectivity of the NULL values for a column T.X use: "select first estimate(X, null) from T".



A workaround is to recreate statistics on the column T.X by using: "create statistics T (X)". However, if the column T.X has often only NULL values, and then it is updated to some non-null values, it is recommended to upgrade to a server containing this fix.



CR:544670
CR Number:   544670
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.0 1502 23 Sep 2008 Fixed
10.0.1 3769 23 Sep 2008 Fixed
11.0.1 1959 27 Nov 2008 Fixed
Description
In some cases, statements containing complex expressions could have used an excessive amount of memory that could affect other connections in the server. This has been fixed so that attempts to execute large expressions that can not be handled will now generate the error:

-890 "Statement size or complexity exceeds server limits"



CR:544672
CR Number:   544672
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)
11.0.0 1502 23 Sep 2008 Fixed
11.0.1 1961 27 Nov 2008 Fixed
Description
Some fulltext queries took inordinate amounts of memory when opening the statement. These queries typically also took too long to open. These problems predominantly affected queries with long phrases or queries over NGRAM indexes with long search terms. The memory usage and open times have been improved.



CR:544689
CR Number:   544689
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1504 22 Sep 2008 Fixed
11.0.1 1963 27 Nov 2008 Fixed
Description
All database pages for a table may not have been freed when the table was dropped. This has now been fixed.



CR:544763
CR Number:   544763
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1506 23 Sep 2008 Fixed
10.0.1 3772 23 Sep 2008 Fixed
11.0.1 1965 27 Nov 2008 Fixed
Description
The -nc option, which limits the number of concurrent sockets opened by MobiLink server, wasn't feasible to use with non-persistent HTTP/HTTPS, because sockets that could have been continuations of valid synchronizations might have been rejected. The -sm option has been improved to provide similar functionality to -nc when used with non-persistent HTTP/HTTPS. Furthermore, the MobiLink server should usually have provided HTTP error 503 (Service Unavailable) to the remote when the -sm limit was reached and sessions were kicked out. If the -nc limit was reached, however, the error would instead have been a socket error -- usually with a system code about being unable to connect, but experience has shown the system code can vary.



Note, to limit the number of concurrent synchronizations for non-persistent HTTP/HTTPS, the -nc option should be set significantly higher than -sm. The greater the difference between -sm and -nc, the more likely (but never guaranteed) the 503 error will be sent to the remote instead of a socket error.



CR:544779
CR Number:   544779
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)
11.0.0 1502 23 Sep 2008 Fixed
11.0.1 1961 27 Nov 2008 Fixed
Description
Any web service in the SYSWEBSERVICE table with data in the PARAMETER column would have been disabled when the database was unloaded into a new database. This has been fixed.

Note, any SOAP services that defined a DATATYPE, GROUP or FORMAT clause, or any web service that defined a METHODS clause, were affected.





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