提供7*24专业Sybase数据库远程及现场技术支持,Sybase ASE及Sybase SQL Anywhere数据库修复服务,
请联系电话: (微信),QQ: 289965371!
We supply technical support for Sybase ASE and Sybase SQL Anywhere, also have many years of experience in recovering data from damanged Sybase devices.
Please contact us:
Phone:
Wechat: 13811580958
QQ: 289965371 联系我们获取数据库技术支持!
Email: 289965371@qq.com
扫描下方微信,联系我们:
扫描雨翰数据恢复官方微信获取专业数据库恢复服务

 

随着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:540227
CR Number:   540227
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3705 07 Aug 2008 Fixed
Description
On Linux x86 and Solaris SPARC systems, the encryption libraries have been updated to use Certicom 5.



CR:540263
CR Number:   540263
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 1454 07 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
An UltraLiteJ database may have expanded needlessly, especially in the presence of updates, either via SQL statements or synchronizations. The routine to search free space on an existing page was not always recognizing when there was room to contain a row. This has been corrected.



CR:540275
CR Number:   540275
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 1454 07 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
Incorrect results would have been obtained when evaluating expressions with hexadecimal constants that were larger than integer values. This has been fixed.



CR:540349
CR Number:   540349
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.1
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 24 Nov 2008 Fixed
Description
The UltraLite Initialize Database utility (ulinit) would have reported a syntax error if the reference database contained a foreign key on a table with the keyword 'name'. Ulinit was failing to quote the table name in the foreign key statement generator. This has been fixed.



CR:540354
CR Number:   540354
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.1 2031 02 Dec 2008 Fixed
11.0.0 1544 02 Dec 2008 Fixed
Description
UltraLiteJ could have thrown an ArrayIndexOutOfBounds exception during sync if a column in the consolidated could have stored more characters than the remote column. For this fix to be effective mlodbc11.dll must be 11.0.0.1541 or later.



CR:540369
CR Number:   540369
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 1454 07 Aug 2008 Fixed
10.0.1 3741 07 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
If request level logging of procedures was enabled, and a FORWARD TO statement was executed on a remote server from an Open Client or jConnect application, then there was a chance the server would have crashed. This problem did not occur if a non-TDS based client was used, or if request level logging of procedures was not enabled. This has been fixed.



CR:540371
CR Number:   540371
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1454 07 Aug 2008 Fixed
10.0.1 3741 07 Aug 2008 Fixed
9.0.2 3708 07 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
In rare circumstances, the server could have crashed while disconnecting, if the connection had created temporary procedures. This has been fixed.



CR:540380
CR Number:   540380
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 1266 07 Aug 2008 Fixed
10.0.1 3741 07 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
On AIX 5.3 systems, the ApproximateCPUTime connection property could have returned a value that was impossibly large. This has been fixed.



CR:540387
CR Number:   540387
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 1466 21 Aug 2008 Fixed
10.0.1 3751 21 Aug 2008 Fixed
11.0.1 1926 24 Nov 2008 Fixed
Description
When an application made an external environment procedure call, and then issued a commit followed by another external environment call, there was a chance the server would have crashed. This problem should not show up if either the original or external connection was accessing a temporary table. It has now been fixed



CR:540388
CR Number:   540388
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 1454 08 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
UltraLite databases restrict the ORDER BY clause, when used with UNION, to referencing select list items by ordinal value rather than by name. Violations of this restriction was not diagnosed correctly in some situations. UltraLiteJ has been corrected to now issue the exception SQLE_INVALID_ORDER, to be consistent with other versions of UltraLite.



CR:540390
CR Number:   540390
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1455 11 Aug 2008 Fixed
10.0.1 3742 24 Sep 2008 Fixed
11.0.1 1915 24 Nov 2008 Fixed
Description
A comparison between an integer and a BINARY value (in a SQL statement) would have caused a conversion error, 'Cannot convert numeric to a binary'. This has been corrected.



CR:540392
CR Number:   540392
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 1454 08 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
Using the Ping utility (dbping) with the -m command line option (use ODBC driver manager)

to attempt to connect to the Web Edition server would have resulted in the error "This server is not licensed to support 'ODBC' connections". This has been corrected.



CR:540393
CR Number:   540393
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 1454 08 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
If a DSN pointed to a Web Edition server, the ODBC Administrator would have given the error "This server is not licensed to support 'ODBC' connections" when the "Test Connection" button was used. This has been fixed.



CR:540407
CR Number:   540407
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1453 08 Aug 2008 Fixed
10.0.1 3741 08 Aug 2008 Fixed
11.0.1 1913 24 Nov 2008 Fixed
Description
In the dbmlsync log file it was possible for a message to occasionally be omitted, or for two messages to be mixed together. For example, a line like the following might occur in the log:

E. 2008-08-06 16:24:34. Timed out trying to readTimed out trying to read 7 bytes.

This has been fixed.



CR:540530
CR Number:   540530
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 1455 11 Aug 2008 Fixed
11.0.1 1915 24 Nov 2008 Fixed
Description
Depending on the language and character set of the operating system, the usage message could have been truncated. Running under an English language locale did not expose this problem. A buffer used for character set translation was under-sized. This has been corrected.



CR:540536
CR Number:   540536
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 1455 11 Aug 2008 Fixed
11.0.1 1915 24 Nov 2008 Fixed
Description
Certain complex regular expression patterns could have caused the server to hang for a few seconds or more. Patterns which could have caused this problem were unlikely to be used in practice, as they needed to be over 100 characters long and have certain unlikely characteristics. This has been fixed so that regular expression patterns that could have caused the server to hang will now generate the error "Statement size or complexity exceeds server limits" (-890).



CR:540557
CR Number:   540557
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 1455 11 Aug 2008 Fixed
11.0.1 1915 24 Nov 2008 Fixed
Description
If the operating system's character set did not match the database's character set, non-ASCII server messages obtained using the system procedure sa_server_messages(), would have been mangled. The server was not converting from the database's character set to the operating system's character set before returning the text. This has been fixed.



CR:540569
CR Number:   540569
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 1465 19 Aug 2008 Fixed
10.0.1 3747 19 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
Statements using EXISTS() subqueries with INTERSECT and EXCEPT may have returned incorrect results. This would have occurred when at least one of the select lists inside the EXISTS() subquery used "*". This has now been fixed.



For example:

select filename, file_id from t1 where

(

exists (select * from t1 except select * from t2)

OR

exists (select * from t2 except select * from t1)

)



CR:540575
CR Number:   540575
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 1460 19 Aug 2008 Fixed
10.0.1 3746 19 Aug 2008 Fixed
11.0.1 1920 24 Nov 2008 Fixed
Description
When in Profiling Mode in Sybase Central, clicking the Index Consultant, or DBISQL, icon for a statement on the Details tab, could have resulted in a syntax error. The problem was caused by syntax errors in SQL statements used by Sybase Central, which have now been fixed.



CR:540579
CR Number:   540579
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 1455 11 Aug 2008 Fixed
11.0.1 1915 24 Nov 2008 Fixed
Description
Attempting to connect to a partially constructed RIM BlackBerry database could have caused a NULL POINTER exception. It was assumed that an existing RIM BlackBerry database would contain a page[0]. This situation now causes an UltraLiteJ exception to be thrown.



CR:540681
CR Number:   540681
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1458 11 Aug 2008 Fixed
10.0.1 3743 11 Aug 2008 Fixed
9.0.2 3710 11 Aug 2008 Fixed
11.0.1 1918 24 Nov 2008 Fixed
Description
Running out of non-cache memory may have caused the server to hang. This has been fixed.



CR:540690
CR Number:   540690
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1453 12 Aug 2008 Fixed
11.0.1 1913 24 Nov 2008 Fixed
Description
The "Check for Updates" entry on the Windows Start menu was missing. This has been fixed.



CR:540698
CR Number:   540698
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1459 12 Aug 2008 Fixed
10.0.1 3744 12 Aug 2008 Fixed
9.0.2 3710 12 Aug 2008 Fixed
11.0.1 1919 24 Nov 2008 Fixed
Description
Calling the OleDbDataReader GetString() method may have failed if the source string had a length of 0, or it may have returned a string that was missing the trailing null termination character when the source string length was greater than or equal to 1 (i.e., "abcde" comes back as "abcd"). This problem has been fixed.



CR:540703
CR Number:   540703
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 1458 12 Aug 2008 Fixed
10.0.1 3744 12 Aug 2008 Fixed
11.0.1 1918 24 Nov 2008 Fixed
Description
When attempting to execute a query that references a proxy table mapped to a DB2 table, and one of the columns in the DB2 table was of type "varchar for bit data", there was a possiblility that fetching data from the proxy column would have resulted in data truncation. This problem does not exist for BLOB, "char for bit data" and "long varchar for bit data" DB2 columns. The has now been fixed.



CR:540708
CR Number:   540708
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 1458 12 Aug 2008 Fixed
11.0.1 1918 24 Nov 2008 Fixed
Description
If a failover occurred in a mirroring system, automatic checkpoints would not have occurred on the new primary server. Stopping and restarting both servers would have corrected the problem. This has been fixed.



CR:540725
CR Number:   540725
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1458 12 Aug 2008 Fixed
10.0.1 3744 12 Aug 2008 Fixed
11.0.1 1918 24 Nov 2008 Fixed
Description
The Migrate Database wizard could have failed to display messages in the messages dialog if it was connected to two or more databases running on the same server. The wizard was listening for asynchronous messages on the wrong connection. This has been fixed.



CR:540729
CR Number:   540729
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 1458 12 Aug 2008 Fixed
11.0.1 1918 24 Nov 2008 Fixed
Description
Attempting to cancel the Migrate Database wizard would have caused Sybase Central to crash. This has been fixed.



CR:540789
CR Number:   540789
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 1462 12 Aug 2008 Fixed
11.0.1 1922 24 Nov 2008 Fixed
Description
If several connections attempted to concurrently execute CREATE, DROP or ALTER statements for a global temporary table, or its indexes, the server could have crashed. This has been fixed so that a global temporary table and its indexes can no longer be altered or dropped if other connections have previously referenced the table until those connections have disconnected.



CR:540797
CR Number:   540797
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 1459 13 Aug 2008 Fixed
11.0.1 1919 24 Nov 2008 Fixed
Description
Printing results in landscape orientation did not use the full page area. The print attribute which specified the page margins did not reverse the printing area width and height when printing in landscape. This has been corrected.



CR:540800
CR Number:   540800
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1459 12 Aug 2008 Fixed
10.0.1 3744 12 Aug 2008 Fixed
11.0.1 1919 24 Nov 2008 Fixed
Description
The Interactive SQL utility (dbisqlc) could have incorrectly reported a syntax error when executing an INPUT statement if the user or table name required quoting to be a valid identifier. This has been fixed.



CR:540823
CR Number:   540823
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1459 12 Aug 2008 Fixed
10.0.1 3744 12 Aug 2008 Fixed
11.0.1 1919 24 Nov 2008 Fixed
Description
If a case-sensitive database was created prior to version 10 and was initialized with collation 857TRK, the Unload utility (dbunload) would have failed to unload it correctly. This has been fixed.



CR:540826
CR Number:   540826
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 1459 13 Aug 2008 Fixed
11.0.1 1926 24 Nov 2008 Fixed
Description
The window which showed long binary column values would have shown incomplete (truncated) data and a corrupt image if the column held a graphic and the result set did not contain the table's primary key. Now, instead of showing partial data, an error message is displayed which advises users on how to remedy the problem.



A similar problem affected the display of long text values, and it has also been fixed.



CR:540921
CR Number:   540921
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 1460 13 Aug 2008 Fixed
10.0.1 3745 13 Aug 2008 Fixed
11.0.1 1920 24 Nov 2008 Fixed
Description
Attempting to access a remote server defined using one of the JDBC classes, could have caused the server to crash if Java failed to start. This problem has now been fixed.



CR:540927
CR Number:   540927
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1460 19 Aug 2008 Fixed
11.0.1 1920 24 Nov 2008 Fixed
Description
Attempting to execute a query that referenced a proxy table mapped to a table in an ADS database with a WHERE clause that contained a timestamp column, could have failed with a conversion error. When generating the remote query, the server was using the wrong format specification for converting the timestamp value to a string value. This problem has now been fixed.



CR:540933
CR Number:   540933
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1267 19 Aug 2008 Fixed
Description
The passthrough feature is enabled automatically when scripts are found in the ml_passthough_script table. In order to process these scripts Java is used. On Mac OSX, the Java VM is not available for 32-bit applications, causing the MobiLink server to give an error and shut down. On Mac OSX, the MobiLink server no longer checks for these scripts.



CR:540965
CR Number:   540965
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 3713 21 Aug 2008 Fixed
Description
If a LOAD TABLE statement was executed on a table with an autoincrement column and caused the range of values for the autoincrement column to be exhausted, the server would have crashed. This has been fixed, and a "Column '<column-name>' in table '<table-name>' cannot be null" error is now given.



CR:540984
CR Number:   540984
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 1461 19 Aug 2008 Fixed
11.0.1 1920 24 Nov 2008 Fixed
Description
The Connection page of the property sheets for publications, MobiLink users and synchronization subscriptions, would have ignored an object's CommunicationType setting and would always have selected the TCP/IP radio button. This has been fixed.



CR:541053
CR Number:   541053
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1488 09 Sep 2008 Fixed
10.0.1 3761 09 Sep 2008 Fixed
11.0.1 1947 24 Nov 2008 Fixed
Description
A query containing an EXITS() predicate and returning distinct rows may have generated an incorrect result set. For this to have occurred the EXISTS predicate must have been able to be flattened into the main query block, and a KEYSET root must have been used for the query. The incorrect result set may contain duplicate rows. This problem has now been fixed.



CR:541055
CR Number:   541055
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 1461 19 Aug 2008 Fixed
11.0.1 1921 24 Nov 2008 Fixed
Description
Some CONTAINS queries may have intermittently taken much longer than they should (e.g. minutes rather than seconds with a query of several frequently occuring words and 1-2Gb of indexed text). This has been fixed fixed.



CR:541056
CR Number:   541056
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)
1461 19 Aug 2008 Fixed
Description
Using the INSTALL JAVA ... FROM expr statement, or performing an unload and reload of a database that contained Java objects, could have resulted in recovery issues later on. This problem has now been fixed.



CR:541059
CR Number:   541059
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1266 19 Aug 2008 Fixed
11.0.1 1922 24 Nov 2008 Fixed
Description
The php driver source code was missing php_sqlany_ver.h on Unix platforms. This has been corrected.



CR:541060
CR Number:   541060
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 1470 26 Aug 2008 Fixed
10.0.1 3753 26 Aug 2008 Fixed
11.0.1 1930 24 Nov 2008 Fixed
Description
The server, in rare circumstances, could have hung updating string columns. This has been fixed.



CR:541062
CR Number:   541062
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 1461 14 Aug 2008 Fixed
11.0.1 1921 24 Nov 2008 Fixed
Description
If an UltraLiteJ synchronization had failed, the next synchronization could have sent the wrong set of last download times. This has been fixed.



CR:541072
CR Number:   541072
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 3751 21 Aug 2008 Fixed
Description
Under rare circumstances, a query plan using the Merge Join algorithm with an GroupBy ordered on the right hand side of the join, could have returned incorrect results. This has been fixed.



CR:541073
CR Number:   541073
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1266 19 Aug 2008 Fixed
10.0.1 3746 19 Aug 2008 Fixed
11.0.1 1912 24 Nov 2008 Fixed
Description
On AIX 6, 64-bit software would not have found the LDAP support libraries, even if they were in the LIBPATH. The location of the LDAP system libraries was changed in AIX 6. The 64-bit library is in:

/opt/IBM/ldap/V6.1/lib64/libibmldap.a

and the 32-bit library is in:

/opt/IBM/ldap/V6.1/lib/libibmldap.a

This has been fixed.



Note that you still need to ensure that the directory with the LDAP libraries are in the LIBPATH. For example, for 64-bit libraries:

export LIBPATH=/opt/IBM/ldap/V6.1/lib64:$LIBPATH

and for 32-bit libraries:

export LIBPATH=/opt/IBM/ldap/V6.1/lib:$LIBPATH



As a work around to use SQL Anywhere LDAP support with AIX 6, create links in /usr/lib as follows (must be root):

cd /usr/lib

ln -s /opt/IBM/ldap/V6.1/lib64/libibmldap.a libibmldap64.a

ln -s /opt/IBM/ldap/V6.1/lib/libibmldap.a



CR:541075
CR Number:   541075
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)
10.0.1 3746 14 Aug 2008 Fixed
11.0.0 1461 14 Aug 2008 Fixed
11.0.1 1921 24 Nov 2008 Fixed
Description
If the MobiLink Server was processing an invalid upload stream, it was possible for the MobiLink Server to have crashed. The MobiLink Server will now fail the synchronization.



CR:541173
CR Number:   541173
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 1462 20 Aug 2008 Fixed
11.0.1 1922 24 Nov 2008 Fixed
Description
The following problems with GIF files have been fixed in the window used to display binary column values:

1. When inserting a GIF file into a binary column, a thumbnail is now displayed. Previously, the thumbnail remained empty.

2. The image format and dimensions were not displayed when viewing a binary column value which contained a GIF image.



CR:541175
CR Number:   541175
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 1462 19 Aug 2008 Fixed
10.0.1 3748 19 Aug 2008 Fixed
11.0.1 1922 24 Nov 2008 Fixed
Description
It was possible, although likely rare, for the server to crash on shutdown. This has been fixed.



CR:541188
CR Number:   541188
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 1467 20 Aug 2008 Fixed
11.0.1 1927 24 Nov 2008 Fixed
Description
When run on Unix systems, the Interactive SQL utility (dbisqlc) would have crashed opening the Options->Configure menu. This has been fixed.



CR:541200
CR Number:   541200
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1462 19 Aug 2008 Fixed
10.0.1 3747 19 Aug 2008 Fixed
11.0.1 1922 24 Nov 2008 Fixed
Description
Some missing items to the graphical and long plans have been added as follows:

1 - HAVING predicate was not dumped in the long plan for any GroupBy physical operator. 2 - HAVING predicate was not dumped for GroupBySortedSets physical operators in the graphical plan.

3 - The number of extension pages was missing in "Table Reference" section of the graphical plan.

4 - The 'Estimated Cache Pages' was missing in the long plan.



CR:541201
CR Number:   541201
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1465 20 Aug 2008 Fixed
10.0.1 3747 20 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
When running Application Profiling, the start_time and finish_time columns of the sa_diagnostic_request table were incorrectly set. The column start_time was set to the correct start time plus the value from the duration_ms column, while the column finish_time was set to the correct start time plus twice the value from the duration_ms column. This has now been corrected.



CR:541202
CR Number:   541202
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1454 19 Aug 2008 Fixed
10.0.1 1454 19 Aug 2008 Fixed
11.0.1 1914 24 Nov 2008 Fixed
Description
Statements using derived tables on the null supplying side of a left outer joins may have returned syntax errors. For this to have occurred, the derived table must have been unflattenable (i.e. it contained GROUP BY, ORDER BY, etc.) and have been used in the null-supplying side of the outer join. There must also have existed a predicate in the ON condition, which was local to the derived table (e.g., "ON .... DT.C = 10 .... "), and referenced the derived table column with a complex expression. This has now been fixed.



CR:541297
CR Number:   541297
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 1465 20 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
If a GRANT or REVOKE of EXECUTE permission for a procedure did not include the procedure's owner, the entry in the transaction log would also not have included the procedure's owner. This has been fixed.



CR:541310
CR Number:   541310
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Solaris
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1515 15 Oct 2008 Fixed
10.0.1 3779 15 Oct 2008 Fixed
11.0.1 1988 01 Dec 2008 Fixed
Description
If dbunload was used to attempt reloading a version 9 or earlier database that needed recovery, the dbunload support engine would have failed an assert and shut down. The assert failure has been fixed, but pre-version 10 databases needing recovery still cannot be reloaded with dbunload. If such a reload is attempted, dbunload will now display the error message "Failed to autostart server". The database will need to be started using using a pre-10 server, and if it then recovers successfully, it can be reloaded after the pre-10 server is shut down.



CR:541313
CR Number:   541313
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 1465 20 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
The 'blocking' option was not included in the result set of the sa_conn_properties() stored procedure. This has been corrected.



CR:541322
CR Number:   541322
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 1465 19 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
Use of the NEAR operator in a CONTAINS query may have returned incorrect results. This would have occurred when using a MANUAL or AUTO refresh index that had been refreshed several times. This has now been fixed.



CR:541333
CR Number:   541333
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)
10.0.1 3750 20 Aug 2008 Fixed
Description
Under concurrent access, a connection may have blocked on row locks waiting for other connections that had long released their row locks. This would only have happened

if the connection had no changes to commit. This has been fixed.



CR:541335
CR Number:   541335
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 1465 20 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
Windows that display long text result values did not consistently warn that only a portion of the value was being displayed. Specifically, if the value was longer than 65536 characters, but the maximum trunction length was set even higher, no warning was displayed. This has been fixed.



CR:541420
CR Number:   541420
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 1465 20 Aug 2008 Fixed
10.0.1 3750 20 Aug 2008 Fixed
11.0.1 1925 24 Nov 2008 Fixed
Description
In very rare circumstances, likely under heavy concurrency, the iAnywhere JDBC driver could have crashed. This has been fixed.



CR:541439
CR Number:   541439
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 16 Sep 2008 Fixed
11.0.1 1954 24 Nov 2008 Fixed
Description
Certain SQL statements would have returned null after being prepared. This has been corrected.



CR:541470
CR Number:   541470
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 1461 19 Aug 2008 Fixed
11.0.1 1921 24 Nov 2008 Fixed
Description
If a procedure or view was created containing an expression that included subtraction of a negative constant, the procedure or view would not have been stored correctly. This has been fixed.



CR:541478
CR Number:   541478
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3755 25 Aug 2008 Fixed
Description
The table name was not reported for SQLE_PRIMARY_KEY_NOT_UNIQUE when this error was encountered during a synchronization. This has been fixed.



CR:541575
CR Number:   541575
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1266 21 Aug 2008 Fixed
10.0.1 13752 21 Aug 2008 Fixed
11.0.1 19276 24 Nov 2008 Fixed
Description
When RSA encryption was in use by the server or client on Mac OS X systems, a crash was likely under very low memory conditions. This has been fixed.



CR:541576
CR Number:   541576
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1266 21 Aug 2008 Fixed
10.0.1 3752 21 Aug 2008 Fixed
11.0.1 1927 25 Nov 2008 Fixed
Description
When RSA encryption was in use by the server or client on Mac OS X systems, memory could have been leaked. This has been corrected.



CR:541586
CR Number:   541586
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 1467 21 Aug 2008 Fixed
11.0.1 1927 25 Nov 2008 Fixed
Description
If a CREATE EVENT statement was executed without including the owner name for the event, the statement recorded in the transaction log did not include the current user's name as the owner. This has been fixed.



CR:541591
CR Number:   541591
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Linux
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 1929 25 Aug 2008 Fixed
Description
After installing the SQL Anywhere software on a non-1252 code page Windows operating system (such as Chinese, Japanese or Korean), the demonstration database (demo.db) has a 2K page size. On 1252 code page systems, the demonstration database has a 4K page size which is expected. Some examples in the documentation may not work on non-1252 systems as a result. In particular, if a database is started on a server that has a 2K page size, databases that have larger page sizes can not be started on the same server.



To work around this issue, the demo.db database can be recreated using the dbinit, dbisql and the Scripts\mkdemo.sql script. Alternatively, the dbunload tool with the -ap option can be used to rebuild the database.



CR:541594
CR Number:   541594
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Linux
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1475 29 Aug 2008 Fixed
Description
The default for the Relay Server Outbound Enabler (RSOE) command line option -cr url_suffix was the Windows path, even on Unix. Now the RSOE default url_suffix on UNIX is /srv/iarelayserver as documented.



CR:541615
CR Number:   541615
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 1467 21 Aug 2008 Fixed
10.0.1 3752 21 Aug 2008 Fixed
9.0.2 3713 21 Aug 2008 Fixed
11.0.1 1927 25 Nov 2008 Fixed
Description
If an application made a remote procedure call to a procedure that returned a result set with unsigned data types, there was a possibility that the call would have failed with a conversion error. This problem has now been fixed.



CR:541622
CR Number:   541622
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1467 21 Aug 2008 Fixed
10.0.1 3752 21 Aug 2008 Fixed
11.0.1 1927 25 Nov 2008 Fixed
Description
If a Transact-SQL CREATE PROCEDURE statement appeared within a BEGIN ... END block, the syntax error given would have been "Syntax error near 'end' on line nnn", where nnn was the line corresponding to the end of the block. Now the error points to the first point at which the server detected a dialect conflict.



CR:541630
CR Number:   541630
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 1473 21 Aug 2008 Fixed
11.0.1 1932 25 Nov 2008 Fixed
Description
Queries using the CONTAINS search conditionwith phrases longer than three words, or adjacent NEAR operators with more than three words, could have returned false matches. This happened if all of the pairwise conditions match, but in different places in the string. For example, for the phrase "a b c" the pairwise conditions are the existence of "a b", "b c" and "a * c" where * means any word. Therefore, the string 'a b x b c x a x c' will match this phrase even though it should not. The problem is now fixed.



CR:541734
CR Number:   541734
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 1466 21 Aug 2008 Fixed
11.0.1 1926 25 Nov 2008 Fixed
Description
The Service utility (dbsvc) now supports creating services for the Relay Server (rshost) and the Outbound Enabler (rsoe) using "-t rshost" and "-t rsoe" respectively.



CR:541736
CR Number:   541736
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 1468 21 Aug 2008 Fixed
11.0.1 1928 25 Nov 2008 Fixed
Description
Under some rare, timing-dependent circumstances, the Interactive SQL utility (dbisql) could have crashed after closing one of the windows used to view long result values. This has been fixed.



CR:541739
CR Number:   541739
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2032 25 Aug 2008 Fixed
Description
When deploying a synchronization model for an UltraLite remote database to a SQL file, then using Interactive SQL to run the SQL file, errors could have occurred for DROP statements if the object did not exist, or CREATE statements if the object already existed. A user would have had to choose to ignore these errors. This has been fixed. Now, the generated SQL file uses Interactive SQL options to suppress errors that can be ignored.



CR:541742
CR Number:   541742
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 1468 21 Aug 2008 Fixed
10.0.1 3762 10 Sep 2008 Fixed
11.0.1 1927 25 Nov 2008 Fixed
Description
Virtual tables were considered non-updatable, which was incorrect. The server may have crashed if an UPDATE statement targeted a virtual table. This has been fixed.



CR:541744
CR Number:   541744
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 1468 21 Aug 2008 Fixed
10.0.1 3752 21 Aug 2008 Fixed
11.0.1 1928 25 Nov 2008 Fixed
Description
If a CREATE EXISTING TABLE command was used to create a proxy table to a remote server using one of the JDBC remote server classes, then the server would have leaked memory. This problem has now been fixed.



CR:541747
CR Number:   541747
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1468 21 Aug 2008 Fixed
11.0.1 1928 25 Nov 2008 Fixed
Description
The sample stoplists, the list of terms to ignore when building a text index, were corrupted for some languages. This has been fixed.



CR:541756
CR Number:   541756
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 1468 21 Aug 2008 Fixed
11.0.1 1928 25 Nov 2008 Fixed
Description
When an application used one of the C External Environments to return a result set back to the server, returning a NULL value would have either resulted in a conversion error or a crash of the external environment. This problem has now been fixed.



CR:541767
CR Number:   541767
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)
21 Aug 2008 Fixed
Description
The system function next_connection() could have returned temporary connections (eg. those with connection IDs greater than 1000000000). This has been fixed so that the only temporary connections that will now be displayed are event connections.



CR:541770
CR Number:   541770
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 1468 21 Aug 2008 Fixed
10.0.1 3752 21 Aug 2008 Fixed
11.0.1 1928 25 Nov 2008 Fixed
Description
If an application connected to a database with a multi-byte character set made a remote procedure call using one of the JDBC remote server classes, then there is a chance the server could have either hung or crash. For this to have occurred, the remote procedure must return a result set containing long character columns, and the proxy procedure must not have initially been defined with a proper result clause, This problem has now been fixed.



CR:541772
CR Number:   541772
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1468 22 Aug 2008 Fixed
10.0.1 3752 22 Aug 2008 Fixed
11.0.1 1928 25 Nov 2008 Fixed
Description
Calling the system function property('FunctionMaxParms',0) would have returned NULL, instead of the correct value 0. This has been fixed. This corresponds to the maximum number of arguments for the abs function.



CR:541783
CR Number:   541783
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1468 22 Aug 2008 Fixed
11.0.1 1861 25 Nov 2008 Fixed
Description
Calls to the sqlany_get_column() function in the C API library used by the data access modues for the various scripting languages (for example, PHP, PERL, Python, etc.) would have returned an incorrect value for the length field when fetching A_BINARY or A_STRING column information. This problem only affected 64-bit platforms. The length field is a size_t pointer and was being set to a 32-bit value, but on 64-bit platforms, size_t is a 64-bit value. This was fixed so that the length field points to the correct 64-bit or 32-bit value.



CR:541857
CR Number:   541857
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 1482 27 Aug 2008 Fixed
10.0.1 3759 27 Aug 2008 Fixed
11.0.1 1941 25 Nov 2008 Fixed
Description
Transactions blocked on a row lock placed by an INSERT, UPDATE, or an isolation level 2 or 3 FETCH, may have waited on the wrong connection, or may have waited indefinitely (until the transaction was forcibly aborted). For this to have occurred, the connection holding the lock must have been in the process of disconnecting when the transaction blocked. While correctness was not affected, application performance could have suffered. This has now been fixed.



CR:541861
CR Number:   541861
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)
10.0.1 3748 22 Aug 2008 Fixed
Description
The server when run on Solaris systems, had poor performance compared to previous versions. Specifically, the TCP/IP communication was slower. Serveral changes have been made to correct this.



CR:541870
CR Number:   541870
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 1469 25 Aug 2008 Fixed
11.0.1 1929 25 Nov 2008 Fixed
Description
Some versions of Windows Vista are misidentified as Windows Server 2008. Among other places, this would have shown up in the server console window, and with the 'platform' property. The GetVersion system call is unable to distinguish between Server 2008 and Windows Vista. This was corrected by changing the Getversion function to GetVersionEx.



CR:541908
CR Number:   541908
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 2252 28 May 2009 Fixed
11.0.0 1622 28 May 2009 Fixed
10.0.1 3898 28 May 2009 Fixed
Description
For some forms of simple DELETE statements on tables with computed columns, the server may have returned the following error:



*** ERROR *** Assertion failed: 106104 (...) Field unexpected during compilation (SQLCODE: -300; SQLSTATE: 40000)



This has been fixed.



CR:542016
CR Number:   542016
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 1524 21 Oct 2008 Fixed
10.0.1 3789 21 Oct 2008 Fixed
11.0.1 1988 25 Nov 2008 Fixed
Description
When rebuilding a pre-10.0 database using the Unload utility (dbunload) with the -an or -ar command line options, dbunload could have hung under very rare conditions on certain Windows systems. This problem has only ever been observed on a few machines configured as Domain Name Servers (DNS), but the hang could have occurred under other conditions as well. This has been fixed.



CR:542139
CR Number:   542139
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 1474 28 Aug 2008 Fixed
10.0.1 3756 28 Aug 2008 Fixed
11.0.1 1933 25 Nov 2008 Fixed
Description
Sybase Central would have reported errors when attempting to browse a database that had the quoted_identifier option set to Off. SQL statements sent to the database had reserved words that were used as system table columns quoted (for example, SYS.SYSTAB."encrypted"). This did not work if the quoted_identifier option was Off, so the plug-in now temporarily sets it to On.



CR:542175
CR Number:   542175
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1473 26 Aug 2008 Fixed
11.0.1 1932 25 Nov 2008 Fixed
Description
The names of objects in the transaction log were not being qualified with owner name for some statements. Now, object names in the transaction log will be qualified with the owners names when the latter are not specified for the following :

- the REFERENCES clauses of CREATE and ALTER TABLE statement

- the TABLE, [MATERIALIZED] VIEW, PRIMARY KEY, COLUMN and INDEX clauses of the COMMENT ON statement

- DROP and ALTER INDEX statements



CR:542185
CR Number:   542185
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3714 26 Aug 2008 Fixed
10.0.0 2928 26 Aug 2008 Fixed
10.0.1 3755 26 Aug 2008 Fixed
Description
When the properties of the visual or non-visual version of the Dbmlsync ActiveX Component were examined from a development environment, it would incorrectly have been described as "iAnywhere Solutions Dbmlsync ActiveX Component 9.0.1". The string has now been changed to properly reflect the true version of the component.



CR:542186
CR Number:   542186
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1497 22 Sep 2008 Fixed
10.0.1 3768 22 Sep 2008 Fixed
11.0.1 1957 25 Nov 2008 Fixed
Description
Under rare circumstances, diagnostic tracing could have failed to record some cursor information for statements within procedures, for example, information about cursor close time and the graphical plan. This has been fixed.



CR:542199
CR Number:   542199
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 1473 27 Aug 2008 Fixed
11.0.1 1933 25 Nov 2008 Fixed
Description
Attepting to start the Interactive SQL utility (dbisql), or any of the other Java administration tools, may have failed with a error that it could not load MSVCR71.DLL. This occurred if the machine does not already have MSVCR7.DLL in the path. This has been fixed.



CR:542208
CR Number:   542208
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 1474 27 Aug 2008 Fixed
11.0.1 1933 25 Nov 2008 Fixed
Description
A query using a CONTAINS search condition over a MANUAL or AUTO refresh index that searched multiple columns, would never have returned rows where the first search column was NULL, even if the others were not NULL and had matches. This is fixed.



CR:542213
CR Number:   542213
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
Executing queries with temporary tables may have caused the database to grow unbounded. Row pages and schema pages were not bing properly released for temoporary tables. This has been corrected.



CR:542239
CR Number:   542239
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)
11.0.0 1474 27 Aug 2008 Fixed
10.0.1 3756 27 Aug 2008 Fixed
11.0.1 1932 25 Nov 2008 Fixed
Description
If the Admin Mode Connection Script wizard was used to create event scripts for handle_UploadData and handle_DownloadData events, they would get an "unknown event" error when syncing. The problem was that the event scripts were created with the names "handle_uploaddata" and "handle_downloaddata" (note the differences in case). This has been fixed.



CR:542342
CR Number:   542342
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3714 27 Aug 2008 Fixed
Description
If a conversion error occurred while constructing the string to be executed by EXECUTE IMMEDIATE within a procedure, the error might not have been reported, possibly leading to a server crash. This has been fixed.



CR:542344
CR Number:   542344
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 1474 28 Aug 2008 Fixed
10.0.1 3756 28 Aug 2008 Fixed
11.0.1 1933 25 Nov 2008 Fixed
Description
In a SQL Anywhere SOAP response, Column "string" data greater than 250 bytes in length may have contained garbled characters if the data was character set converted. This has been fixed.



Example:

SA running iso-8859-2 database receiving a SOAP request with an Accept-Charset: UTF-8 HTTP request header will character set convert its response from ISO-2 to UTF-8.



CR:542349
CR Number:   542349
Product Name:   SQL Anywhere
Product Component:   Other
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
11.0.1 1934 25 Nov 2008 Fixed
Description
Executing an SQL query batch using the Perl, PHP or Python drivers, that contained a SELECT statement in addition to other SQL queries that did not return a result set, could have returned the error: -180 'Cursor not open' error. This has now been fixed.



For example:

IF EXISTS( ... ) then

DROP ...

ENDIF;

CREATE PROCEDURE ( ... )

BEGIN

SELECT ...

END;



CR:542356
CR Number:   542356
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.1 1986 12 Feb 2009 Fixed
11.0.0 1560 12 Feb 2009 Fixed
10.0.1 3845 12 Feb 2009 Fixed
Description
A query with a GROUP BY clause that referenced the same alias at least twice, would have incorrectly returned a syntax error.



For example:

SELECT item = 'abc'

FROM product p LEFT OUTER JOIN sales_order_items

GROUP BY

item,

item



This has been now been corrected.



CR:542397
CR Number:   542397
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 1475 28 Aug 2008 Fixed
10.0.1 3756 28 Aug 2008 Fixed
9.0.2 3716 28 Aug 2008 Fixed
11.0.1 1933 25 Nov 2008 Fixed
Description
The DISH service does not set the HTTP Content-Type response header, which has occasionally caused Internet Explorer 7 to fail to render the WSDL. This has been fixed so that the response headers now include Content-Type: text/xml; charset="utf-8".

Note, the charset qualifier is not included in 9.0.2 since its output is in database character set. This change is in accordance with the WSDL 1.1 specification, see http://www.w3.org/TR/wsdl#_Toc492291097.



CR:542482
CR Number:   542482
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 1941 28 Aug 2008 Fixed
11.0.0 1266 26 Nov 2008 Fixed
10.0.1 3756 26 Nov 2008 Fixed
Description
On Mac OS X systems, if the path specified in the "Database" field of the "New Server" dialog in DBLauncher contained spaces, the server would have failed to start the database. This has been fixed.





--------------------------------------华丽的分割线-------------------------------------------------------------------------

Sybase SQL Anywhere数据库恢复工具ReadASADB:

之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。
此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。
恢复Sybase SQL Anywhere的工具在国内处于领先水平。

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,16.x,17.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使用介绍

Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景

各种误操作:

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

Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景:

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
7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page
8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back.
9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back


-------------------------------------------------------------------------------------------

Sybase ASE数据库恢复工具READSYBDEVICE:

一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具!
能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。

Sybase ASE数据库恢复工具READSYBDEVICE的主要功能:

  1. 被勒索病毒加密数据文件及备份文件情况下的恢复;
  2. 系统崩溃只剩下数据文件的情况下的恢复,甚至数据库文件不存在而只有损坏的备份文件情况下的恢复;
  3. 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复;
  4. delete数据恢复、误update数据恢复、误删除表(drop)恢复、误truncate表恢复 等;
  5. 各种Sybase内部系统表损坏、索引错误的修复;
  6. master数据库损坏而无法正常运行情况下的恢复;
  7. Sybase数据库被标记为可疑,不可用等情况的恢复;
  8. Sybase数据库中数据文件内部出现坏块情况下的恢复;
  9. Sybase数据库无数据文件但有日志文件的情况下的恢复;
  10. Sybase数据库只有数据文件无任何日志文件的情况下的恢复;
  11. Sybase数据文件被误删除情况下的碎片提取恢复;
  12. 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复;
  13. 数据库sysobjects等系统表损坏无法正常应用情况下的恢复;
  14. Sybase数据库还原数据库出现失败情况下的恢复;
  15. Sybase数据库只剩下损坏的备份文件情况下的恢复。

Sybase ASE数据库恢复工具READSYBDEVICE支持的版本:

Sybase ASE 11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x


-------------------------------------------------------------------------------------------

SQL Server数据库恢复工具SQLRescue:

一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具!
能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。

SQL Server数据库恢复工具SQLRescue的主要功能:

  1. 系统崩溃只剩下数据文件的情况下的恢复,即无日志文件或者日志文件损坏情况下的恢复;
  2. 断电导致数据库文件损坏情况下的恢复;
  3. 硬盘坏道造成数据库损坏情况下的恢复;
  4. 数据文件内部存在坏页情况下的恢复;
  5. 企业管理器误删除数据表记录,管理软件误删除数据表记录的恢复;
  6. 并闩锁错误、格式化、误删除后导致软件不能使用的情况;
  7. 无法读取并闩锁页sysindexes失败情况下的修复;
  8. 数据文件被误删除情况下的碎片提取恢复;
  9. 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回;
  10. master数据库损坏而无法正常运行情况下的恢复;
  11. 数据文件无法附加情况下的数据恢复;
  12. 数据库被标记为可疑,质疑,不可用等情况的恢复;
  13. 数据库sysobjects等系统表损坏情况下的恢复;
  14. 数据被误(drop、delete、truncate)删除表数据的恢复,误update后的数据恢复等;
  15. 还原时报一致性错误,错误823等情况下的数据恢复,各种错误提示的数据库文件修复;
  16. 数据库被误格式化等情况下的数据库恢复;
  17. 日志收缩造成数据库损坏情况下的恢复;
  18. 仅剩损坏的备份文件情况下的恢复。

SQL Server数据库恢复工具SQLRescue技术特点:

只要SQL Server数据库的数据文件存在,我们就有办法帮您从数据文件中找回重要数据。
  1. 从数据文件中直接恢复数据
  2. 不能附加时直接恢复数据并生成新的数据库
  3. 系统表损坏的数据库修复
  4. 快速修复SQL 823错误、连接中断错误

SQL Server数据库恢复工具SQLRescue支持的版本:

Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------