远程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:448836
CR Number:   448836
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3299 24 Nov 2006 Fixed
Description
The Foreign Key wizard was allowing attempts to create a foreign key between a base table and a global temporary table. This would always have failed, as tables related by a foreign key constraint must both be base tables, or both be global temporary tables without the ON COMMIT DELETE ROWS clause. This has been corrected so that the Foreign Key wizard now prohibits attempting to create a foreign key that is not meet the above criteria.



CR:448910
CR Number:   448910
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3302 27 Nov 2006 Fixed
10.0.0 2538 27 Nov 2006 Fixed
Description
If two servers running on the same Unix machine attempt to use the same alternate server name for a database, and either server had not started the TCP/IP network protocol, the databases on both servers will start successfully, but the alternate server name will not work for either database. This has been fixed, the second database will now fail to start

with a "Server name already in use" error.



Note, if both servers were running the TCP/IP network protocol, which is the default, the error was correctly detected.



CR:448915
CR Number:   448915
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3303 02 Jan 2007 Fixed
Description
If a query contained two or more IN predicates that contained the same number of elements, but one list contained duplicate entries and all the entries in the list with duplicates were present in the other lists, then the query could have returned incorrect results or fail to give an error when an error should have occurred. For example, consider the following query, run against demo.db:



select count(*),

case when DepartmentName in ('R & D', 'R & D') then

DepartmentName

else

'Others'

end

from Departments

group by case when DepartmentName in ('R & D', 'Sales') then

DepartmentName

else

'Others'

end



The query would have returned results as though both IN lists were ('R & D', 'Sales'). This has been fixed so that now the query correctly returns the error -149: "Function or column reference to 'DepartmentName' must also appear in a GROUP BY"



CR:449016
CR Number:   449016
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3304 29 Nov 2006 Fixed
10.0.0 2539 29 Nov 2006 Fixed
Description
Explicitly dropping a database connection that was used within an HTTP session context, could have caused the server to crash, if the connection was actively in use by an HTTP request. The session was being immediately deleted when the database connection was dropped. Now a cancel is issued to the request, then when it terminates, the session is deleted and the connection closed.



CR:449041
CR Number:   449041
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3290 29 Nov 2006 Fixed
10.0.0 2762 29 Nov 2006 Fixed
Description
When rebuilding a database using an external unload/reload (i.e., the -xx option in dbunload, or the equivalent settings in Sybase Central), NCHAR data could potentially have been subject to "lossy" character set conversion operations. This would have resulted in incorrect NCHAR values in the rebuilt database. For this to have occurred, the NCHAR data must have contained characters that had no counterpart in the host operating system's) character set. This has now been fixed.



A workaround for this problem is to specify "charset=utf-8" on the unload and reload connection parameters.



This has been fixed.



CR:449146
CR Number:   449146
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3304 30 Nov 2006 Fixed
10.0.0 2763 30 Nov 2006 Fixed
Description
A query containing a subquery that made use of an aggregate function and had an outer reference, could have returned an incorrect result.



For example, the following query that should have returned several rows, would have returned at most one row:



SELECT t1.w FROM T t1 WHERE t1.x IN (SELECT max(t2.z) FROM T t2 WHERE t2.id = t1.id)



This has been fixed.



CR:449161
CR Number:   449161
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3304 30 Nov 2006 Fixed
10.0.0 2763 30 Nov 2006 Fixed
Description
If the pattern of a LIKE predicate does not begin with a wildcard character (e.g., x LIKE 'abc%'), then an optimization is used that allows an index to be used to filter rows based on the LIKE prefix. If the indexed column was created descending, the wrong answer could have been returned. This is now corrected.



CR:449193
CR Number:   449193
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3311 06 Dec 2006 Fixed
10.0.0 2766 06 Dec 2006 Fixed
9.0.2 3419 06 Dec 2006 Fixed
8.0.3 5476 06 Dec 2006 Fixed
Description
Duplicate variable declarations in Transact-SQL procedures were not detected as syntax errors when the procedure was created. They would then have caused spurious syntax errors during procedure execution. This has been fixed.



CR:449309
CR Number:   449309
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3305 01 Dec 2006 Fixed
10.0.0 2763 01 Dec 2006 Fixed
9.0.2 3384 01 Dec 2006 Fixed
Description
Enhancements were made to the MobiLink Server to allow for future support of currently non-supported consolidated databases.



CR:449317
CR Number:   449317
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3305 01 Dec 2006 Fixed
10.0.0 2764 01 Dec 2006 Fixed
Description
When run on Unix systems, applications attempting to connect will fail, if "clientport" was specified in the tcpip options of the connection string. The client software was binding a UDP socket to both an IPv4 address and an IPv6 address, using the same port.

This cannot be done on UNIX systems unless the socket option SO_REUSEADDR is specified, which was not being done. This has been corrected.



CR:449395
CR Number:   449395
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3329 11 Jan 2007 Fixed
10.0.0 2786 11 Jan 2007 Fixed
Description
When using the MobiLink .NET Direct Row API, it was not possible to set the value of a column in the IDBCommand returned by the GetDeleteCommand method to NULL. This prevented passing a truncate table command down to the remote database using the download_delete_cursor. This problem has now been fixed, and a NULL value can now be used.



CR:449401
CR Number:   449401
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3306 01 Dec 2006 Fixed
10.0.0 2764 01 Dec 2006 Fixed
Description
Character data could have been incorrectly reloaded when rebuilding a database containing at least one table with NCHAR columns, and when doing an unload/reload other than with the -an or -ar command line options specified. In these cases, the data could have been subject to unwanted character set conversions, resulting in incorrect values being loaded into the rebuilt database. This has been fixed. A workaround for this problem is to specify "charset=utf-8" on the unload and reload connection parameters.



CR:449411
CR Number:   449411
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3306 01 Dec 2006 Fixed
10.0.0 2764 01 Dec 2006 Fixed
Description
It was possible that the SQL error STRING_RIGHT_TRUNCATION could have been raised when it should not have been. This was more likely to have occurred when the declared byte length of a character column was near, or greater than one database page in size, and when the value being inserted (or updated) was longer than the declared column length, but only space characters would have been right-truncated in the insertion. If the truncated characters consisted only of spaces then the error should not have been raised. This has been fixed.



CR:449416
CR Number:   449416
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3310 04 Dec 2006 Fixed
10.0.0 2765 04 Dec 2006 Fixed
Description
A connection attempt may have failed, or hang, if the HOST connection parameter was an IPv4 address, and the initial connection attempt to the host failed for some reason, resulting in a search for the server. The server must also have been listening on an IPv6 interface with the client having IPv6 enabled, and the response to the server search that the client received must have come from that IPv6 interface. In other words, the client would have proceeded to connect to an IPv6 address after first trying an IPv4 address.

This has now been fixed.



CR:449439
CR Number:   449439
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3306 06 Dec 2006 Fixed
10.0.0 2764 06 Dec 2006 Fixed
9.0.2 3416 06 Dec 2006 Fixed
Description
Depending on the device and the mechanisms used, UUIDs are guaranteed or are extremely likely to be unique. In the case where there was no host address available, duplicate UUIDs were possible, because the node id was generated randomly. The quality of the random number used for the node id has now been improved for Windows CE, thus making duplicates far less likely.



CR:449459
CR Number:   449459
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3307 04 Dec 2006 Fixed
10.0.0 2764 04 Dec 2006 Fixed
9.0.2 3418 05 Dec 2006 Fixed
Description
If ULTransaction.Commit() failed (for example due to a referencial integraty error), and the then ULTransaction.Rollback() was called, Rollback() would have failed to report that the transaction had already completed. This has now been corrected so that Commit() will only mark the transaction as completed if there were no errors. A work-around is to close the connection and then re-open it. A side-effect of this will be that all prepared statements will be invalidated.



CR:449506
CR Number:   449506
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3309 05 Dec 2006 Fixed
10.0.0 2766 05 Dec 2006 Fixed
9.0.2 3418 05 Dec 2006 Fixed
8.0.3 5476 05 Dec 2006 Fixed
Description
Attempting to execute an INSERT ... SELECT, that did not fill columns defined with default timestamp, may have caused the assertion failure "Attempting to store invalid timestamp value in table ...". This occurred when the database option Truncate_timestamp_values was set to ON, and the value for the database option Default_timestamp_increment was greater then 1. This has been fixed.



CR:449533
CR Number:   449533
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3309 05 Dec 2006 Fixed
10.0.0 2765 05 Dec 2006 Fixed
Description
When a server received an HTTP request that was subsequently canceled, it may have occasionally leaked memory. This would have been very rare, as the cancel had to occur within a very small period of time. This has been fixed.



CR:449536
CR Number:   449536
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3306 06 Dec 2006 Fixed
10.0.0 2764 06 Dec 2006 Fixed
9.0.2 3416 06 Dec 2006 Fixed
Description
Calling the html_decode() function could have caused the server to crash. This has been fixed.



CR:449543
CR Number:   449543
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3356 23 Jan 2007 Fixed
10.0.0 2794 23 Jan 2007 Fixed
Description
Some characters that should be considered as whitespace, such as U+00A0 (no-break space), where not being treated as whitespace by the server. The problem applies to all collations, but has been fixed only in the UCA collations. Legacy collations have not changed.

Note that a new dbicu10.dll is required for this fix.



CR:449554
CR Number:   449554
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3309 05 Dec 2006 Fixed
10.0.0 2765 05 Dec 2006 Fixed
Description
When starting a server with the network protocol option myip=::xxx.xxx.xxx.xxx%n, an invalid address error would have been displayed, and the server would have exited. This address is an IPv4 address embedded in an IPv6 address. IPv6 addresses accept a %n at the end, but IPv4 addresses do not. The server now truncates the IPv4 address at the %, so that the address is no longer rejected.



CR:449577
CR Number:   449577
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3311 05 Dec 2006 Fixed
10.0.0 2766 05 Dec 2006 Fixed
9.0.2 3419 05 Dec 2006 Fixed
Description
On Unix systems, an auto-started server that had shut down would have remained a zombie until the parent process exited. This has been fixed by doing a double fork when spawning the server, in order to ensure all parent-child relationships are erased when it is shutdown.



CR:449590
CR Number:   449590
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3312 07 Dec 2006 Fixed
10.0.0 2767 07 Dec 2006 Fixed
9.0.2 3419 07 Dec 2006 Fixed
9.0.1 2192 07 Dec 2006 Fixed
8.0.3 5476 07 Dec 2006 Fixed
Description
If a date parameter value (a value of type adDate) was inserted into a column, only the year and month were inserted correctly. The day was always 1.



A Visual Basic example:

cmd.CommandText = "INSERT INTO DateTable(cDate) values (?)"

cmd.CommandType = ADODB.CommandTypeEnum.adCmdUnknown

parm = cmd.CreateParameter("inDate", ADODB.DataTypeEnum.adDate, ADODB.ParameterDirectionEnum.adParamInput)

cmd.Parameters.Append(parm)

parm.Value = "2006-12-15"

cmd.Execute()



The value inserted would have been "2006-12-01".



This problem has been corrected, so that the correct date is now inserted.



CR:449600
CR Number:   449600
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3312 08 Dec 2006 Fixed
10.0.0 2767 08 Dec 2006 Fixed
Description
If an UNLOAD <select> statement was executed with the clauses FORMAT ASCII, QUOTES OFF and DELIMITED BY '' (empty delimiter string), the server could have gone into an infinite loop. The code was missing the case of an empty delimiter string, this has now been corrected.



CR:449670
CR Number:   449670
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3340 11 Jan 2007 Fixed
10.0.0 2786 11 Jan 2007 Fixed
Description
An application using the .NET Row Api could receive the error "Unable to find an entry point named native_GetColCSTimestampStruct in DLL mldnet10.dll". This has been fixed.



CR:449676
CR Number:   449676
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3442 31 Jan 2007 Fixed
Description
It was possible for the MobiLink Server to have reported that a synchronization had failed with no apparent error. The failure would happen after performing the user authentication , even though the authentication had been successful. The problem was a result of the size of the synchronization stream, so making almost any change at the remote database would change the size of the synchronization stream, causing the problem to disappear. This problem has now been fixed.



CR:449758
CR Number:   449758
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3313 06 Dec 2006 Fixed
10.0.0 2768 06 Dec 2006 Fixed
Description
The system function html_decode() now decodes more Unicode codepoints given as numeric entities, for example, ÿ. When a Unicode codepoint is specified (for example, ™ for the trademark symbol), the value is converted to a character. If an invalid codepoint is specified, or the codepoint cannot be represented in the database character set, the server will output the codepoint unchanged (still in its &#x form). Previously, codepoints less than 0x7F were converted to characters (for some character sets, codepoints less than 0xFF were converted to characters), and all other codepoints remained in their codepoint form.



CR:449763
CR Number:   449763
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3312 06 Dec 2006 Fixed
10.0.0 2767 06 Dec 2006 Fixed
Description
There was apossibility, although remote, that the MobiLink server may have crashed when using named columns if the type field was null, which is the default.



CR:449783
CR Number:   449783
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3312 06 Dec 2006 Fixed
10.0.0 2767 06 Dec 2006 Fixed
9.0.2 3419 06 Dec 2006 Fixed
Description
Some of the utilities, dbunload, dbtran and dbmlsync were not always honouring the SATMP (version 10.0.0), or the ASTMP (versions prior to 10.0.0) environment variable, when determining a location to store temporary files. When that happened, all the other steps in deciding the temporary directory location were as documented. This has been fixed.



CR:449874
CR Number:   449874
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3314 08 Dec 2006 Fixed
10.0.0 2769 08 Dec 2006 Fixed
9.0.2 3420 08 Dec 2006 Fixed
8.0.3 5477 08 Dec 2006 Fixed
Description
The dbisqlc utility may have terminated abnormally immediately on startup. This problem occurs occasionally. A problem in the GUI initialization code has been fixed.



CR:449881
CR Number:   449881
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3311 07 Dec 2006 Fixed
10.0.0 2766 07 Dec 2006 Fixed
9.0.2 3419 07 Dec 2006 Fixed
Description
If the table names specified in the Unload utility's -t and -e command-line options (or the equivalent Sybase Central settings) were provided in a character set other than the database character set, the tables may not have been unloaded (or excluded, in the case of -e). This problem would commonly have occurred when the OS charset and database charset were different, and characters in the table names required conversion. This has been fixed.



CR:449882
CR Number:   449882
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3312 07 Dec 2006 Fixed
10.0.0 2767 07 Dec 2006 Fixed
Description
Rebuilding of a version 10.0 database, with a UCA CHAR collation, may have failed. In cases where the rebuild completes without failure, other collation related problems could, and likely would, have arisen later on, such as incorrect sorts or sortkey generation. This problem could only have occurred when the -an or -ar dbunload command line options (or the Sybase Central equivalent settings) were used. A work-around is to initialize the new database manually, specifying '-z UCA' (if using dbinit), and then using the -ac dbunload command line option to reload into the new database.



This has been fixed.



CR:449887
CR Number:   449887
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3321 15 Dec 2006 Fixed
10.0.0 2773 15 Dec 2006 Fixed
Description
If while starting up as a Windows service, the server received a stop request from the Stop Server utility, the server may have crashed. This has been fixed.



CR:449917
CR Number:   449917
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3313 08 Dec 2006 Fixed
10.0.0 2768 08 Dec 2006 Fixed
Description
If an application called the ODBC function SQLSetConnectAttrW() with a string argument, there was a chance that the application would have crashed. This problem has now been fixed.



CR:449974
CR Number:   449974
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3314 08 Dec 2006 Fixed
10.0.0 2541 08 Dec 2006 Fixed
Description
The server may have crashed, or failed an assertion with an "Out of memory" error, when receiving Unichar data over a TDS connection (e.g., using jConnect). This has now been fixed.



CR:450088
CR Number:   450088
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3317 11 Dec 2006 Fixed
10.0.0 2770 11 Dec 2006 Fixed
Description
On Unix systems, if a pre-version 10.0 database was reloaded internally that had several dbspaces that were not all present in the current directory, the reload would have hung. This has been fixed. The reload operation will now be aborted and the message "Dbspace for table '<tablename>' not found" will be displayed, as is already the case for version 10.0 to version 10.0 database reloads.



CR:450098
CR Number:   450098
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3317 13 Dec 2006 Fixed
10.0.0 2770 13 Dec 2006 Fixed
Description
When run in very low memory conditions, which in practice would likely be extremely rare, the Unload utility could have crashed when building indexes. This has been fixed.



CR:450135
CR Number:   450135
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3509 12 Dec 2006 Fixed
10.0.0 2771 12 Dec 2006 Fixed
Description
Reorganizing an index could have caused the server to fail an assertion, or to have crashed. This was unlikely to occur unless the server was heavily loaded. This has now been fixed.



CR:450195
CR Number:   450195
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3318 12 Dec 2006 Fixed
10.0.0 2771 12 Dec 2006 Fixed
9.0.2 3422 12 Dec 2006 Fixed
Description
A SQL Anywhere web client procedure connecting to a non HTTP endpoint, may have caused the server to crash, or to have failed silently with no error message. This has been corrected so that the client will now generate the error: "Invalid response from the HTTP server"



CR:450232
CR Number:   450232
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3319 14 Dec 2006 Fixed
10.0.0 2809 26 Feb 2007 Fixed
Description
Following a DML statement that caused a statement-level trigger to fire, the value of the Transact-SQL global variable @@rowcount could have been incorrect . Also, if a DML statement caused multiple statement-level triggers to fire, the value of @@rowcount could have been incorrect in some of the triggers. These problems have been fixed so that the value of @@rowcount now correctly holds the number of rows affected by a DML operation when the operation (along with any triggers) completes. Also, at the beginning of any statement-level triggers, @@rowcount holds the number of rows affected by the statement that caused the trigger to fire.



CR:450247
CR Number:   450247
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2778 02 Jan 2007 Fixed
Description
For tables having unsigned bigint columns defined with "default global autoincrement", a LOAD TABLE statement would not have correctly set the next available value for the column. This could occur, for example, when rebuilding a database using DBUNLOAD. This has been fixed.
Workaround Description
 After rebuilding the database we can issue calls to the sa_reset_identity stored procedure



CR:450259
CR Number:   450259
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3318 14 Dec 2006 Fixed
10.0.0 2772 14 Dec 2006 Fixed
9.0.2 3422 14 Dec 2006 Fixed
Description
When executing a statement that runs for a long time ( for example, "waitfor delay '20:00:00'" ), the application could have crash if the server had gone down. This problem has been fixed.



CR:450346
CR Number:   450346
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3319 13 Dec 2006 Fixed
10.0.0 2772 13 Dec 2006 Fixed
Description
Attempting to connect to a database using a filename specified in a different case than that actually stored on the filesystem, could have caused the following exception when the tables folder was opened:

java.lang.NumberFormatException: null

at java.lang.Integer.parseInt(Unknown Source)

at java.lang.Integer.valueOf(Unknown Source)

at ianywhere.ultralite.Index.<init>(Index.java:122)

at ianywhere.ultralite.Table._loadPrimaryKey(Table.java:481)

...

For example, attempting to connect to the database "application.udb" using the name "Application.udb", would have caused the problem to occur. This has been fixed.



The workaround is to specify the filename (directories do not need to match case) in the same case as the file was stored on disk.



CR:450353
CR Number:   450353
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3324 18 Dec 2006 Fixed
10.0.0 2775 18 Dec 2006 Fixed
9.0.2 3424 18 Dec 2006 Fixed
8.0.3 5481 18 Dec 2006 Fixed
Description
The MobiLink client would gradually have consumed more and more memory when synchronizing tables that contained foreign keys that refer to other tables that were not being synchronized. This has been corrected.



CR:450354
CR Number:   450354
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3320 15 Dec 2006 Fixed
10.0.0 2774 15 Dec 2006 Fixed
Description
If a view was disabled, and there were previously generated objects, such as cursors and prepared statements, that referred to the view being disabled, then future references to these objects could have caused the server to behave erratically, including crashing. The server will now properly deal with cached objects that refer to views that are disabled after the creation of the referencing objects.



CR:450355
CR Number:   450355
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3320 15 Dec 2006 Fixed
10.0.0 2774 15 Dec 2006 Fixed
9.0.2 3423 15 Jan 2007 Fixed
Description
When a table or view is altered, the server finds all cursors (including those created internally for DESCRIBE) that refer to the table or view being altered and automatically closes them. Under some circumstances, the server would have failed to close all such cursors, causing subsequent references to these cursors to behave unpredictably. The results could have ranged from no impact, to a server crash. This problem was likely to happen when the table being altered had previously been used in a cursor, and the reference was eliminated internally by the optimizer as being redundant. For views, the problem could have arisen when the view was flattened by the optimizer, and references to it were removed from the query that was optimized and executed. This has been fixed so that the server now correctly finds and closes all the cursors.



CR:450500
CR Number:   450500
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.0 1194 15 Dec 2006 Fixed
10.0.1 3321 15 Apr 2008 Fixed
Description
When deploying a synchronization model that creates a new database and deployed to file, the batch file to create the database would always have used "remote.db" (or "remote.udb" for UltraLite) for the database file name. The name specified in the wizard was ignored if a remote database was also directly created. Thus recreating the remote from the batch file and attempted to sync would have failed, since the database names were different. Now the batch file will create a remote database file with the same name as was used if deployment directly created the database. If only deploying to file, then the default database file name, <model_name>_remote.<ext>, will be used, which is the same default as the wizard uses for direct creation.



CR:451339
CR Number:   451339
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3321 18 Dec 2006 Fixed
10.0.0 2774 18 Dec 2006 Fixed
Description
After running dbisqlc on Unix in a gnome-terminal, the terminal may no longer have behaved

correctly. Specifically, when input reached the end of a line, it would have wrapper over itself, instead of continuing on the next line. During initialization, wrapping was disabled on the terminal, and was not re-enabled on exit. This is now fixed by re-enabling wrapping on exit.



CR:451343
CR Number:   451343
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3321 15 Dec 2006 Fixed
10.0.0 2774 15 Dec 2006 Fixed
Description
A malformed multipart form-data HTTP request may have caused the server to crash. This has been fixed.



CR:451374
CR Number:   451374
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3321 18 Dec 2006 Fixed
10.0.0 2774 18 Dec 2006 Fixed
Description
When an SD memory card holding a running UltraLite database is removed, the runtime will return an I/O error (SQLE_DEVICE_IO_FAILED). This error is a critical error, meaning that all subsequent calls into the runtime should immediately return this same error until all connections to the database have shutdown and the database is restarted. Unfortunately, this error was not being marked as critical, so it was lost on the next call into the runtime, and the runtime would have crashed the next time it tried to read from, or write to, the database, due to an invalid file handle. This has been fixed.



Further testing revealed that some runtime entry points did not handle other critical errors correctly, and would have caused the runtime to crash if a critical error had been signalled in a earlier call. These have been fixed as well.



CR:451463
CR Number:   451463
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3320 18 Dec 2006 Fixed
9.0.2 3423 18 Dec 2006 Fixed
Description
When running on Windows Vista, performing operations that require administrative privileges will cause a Windows Vista Elevation Consent (or Credentials) prompt to be displayed. The application name shown in the prompt will be "dbelevate". In order for the operation to succeed, the user must provide consent or provide administrative credentials.



Some self-registering DLLs require administrative privileges to register or unregister themselves. During a normal installation, the installer runs in an elevated state and a prompt for dbelevate will not be seen; however, if regsvr32 is used directly, the prompt may be seen. The SQL Anywhere OLE DBV provider, SAOLEDB, is Vista-aware and may request elevation when installed or uninstalled.



CR:451472
CR Number:   451472
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3324 18 Dec 2006 Fixed
10.0.0 2542 18 Dec 2006 Fixed
Description
The MobiLink server may have crashed when using multiple synchronization streams, or the clients were using HTTP non-persistent. This problem would have been seen more quickly if using the -nc switch (set maximun number of network connections) with a small number. No workaround is available. While not eliminated, the probability of this problem occurring has been reduced.



CR:451486
CR Number:   451486
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3324 18 Dec 2006 Fixed
10.0.0 2775 18 Dec 2006 Fixed
9.0.2 3424 18 Dec 2006 Fixed
Description
If an application using the iAnywhere JDBC driver fetched a result set with more than one column, and one of the columns was a blob column, then calling ResultSet.wasNull() after calling ResultSet.getBlob() would not always have indicated the correct 'nullness' of the the blob value that was just fetched. The driver was not properly setting the null bit for blob columns, so calling ResultSet.wasNull() after fetching a blob column would have actually returned the null bit of the previous column fetched. This problem has been fixed.



CR:451551
CR Number:   451551
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3331 02 Jan 2007 Fixed
10.0.0 2779 02 Jan 2007 Fixed
Description
The property sheet for a non-materialized view would not have displayed the view's status (valid, invalid or disabled). This has been fixed.



CR:451555
CR Number:   451555
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3342 24 Jan 2007 Fixed
10.0.0 2786 24 Jan 2007 Fixed
9.0.2 3432 24 Jan 2007 Fixed
Description
The QAnywhere agent was not setting the store property ias_Network.Adapter correctly when the device is on ActiveSync. This has been fixed so that ias_Network.Adapter is now set to 'RndisFn1' when the device is on ActiveSync.



Note that the Remote-NDIS Host "IP address" and "Default gateway" properties must be configured on the Windows CE device in order for name resolution to work properly when connected on ActiveSync.
Workaround Description
 None.



CR:451563
CR Number:   451563
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3330 02 Jan 2007 Fixed
10.0.0 2778 02 Jan 2007 Fixed
Description
An UltraLite application could have produced incorrect results for queries that involved non-trivial ORDER BY expressions when the query did not have the FOR READ ONLY clause. This has been fixed. A work-around is to add the FOR READ ONLY clause, if possible.



CR:451573
CR Number:   451573
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 3439 23 Jan 2007 Fixed
Description
The changes for Engineering case 422775 may have caused the server to use sequential scans when executing a SELECT statement over a large table, even when a much more efficient access method using a clustered index scan was available. The problem was more likely to be noticeable when the table was fairly large, most of the table was not in cache, and the scan returned a fairly large number of rows. The earlier fix caused the server to over estimate the cost of partial index scans with a cold cache. This has now been corrected.



CR:451587
CR Number:   451587
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3330 21 Dec 2006 Fixed
10.0.0 2542 21 Dec 2006 Fixed
Description
If a database had an associated mirror log, and an attempt was made to truncate both the main transaction log and the mirror log using the BACKUP DATABASE statement with the TRANSACTION LOG TRUNCATE clause, the server would have failed assertion 100915 and would not have deleted the mirror log file. The same situation would have occurred if dbbackup was used with "-s -x" on the same database, as this causes the BACKUP DATABASE statement to be executed on the server. This has been fixed. A workaround is to use dbbackup without the "-s" option.



CR:451631
CR Number:   451631
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3333 08 Jan 2007 Fixed
10.0.0 2781 08 Jan 2007 Fixed
Description
A check has been added to detect some page header corruption which could have lead to unpredictable behaviour. This check operates independent of the whether page checksums are enabled. As with page checksums, a fatal error is now signaled if corruption is detected.



CR:451693
CR Number:   451693
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3328 21 Dec 2006 Fixed
10.0.0 2777 21 Dec 2006 Fixed
Description
When the plug-in is in Model mode, creating a new remote database from a Microsoft SQL Server consolidated database, with tables having NTEXT columns, would have resulted in those columns being created as LONG BINARY cloumns in the remote. This has been fixed so that such columns will now be created as LONG NVARCHAR columns.



CR:451699
CR Number:   451699
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2777 20 Dec 2006 Fixed
Description
The change for Engineering case 444112, could have caused a database mirroring server to crash if it attempted to connect to another mirror server, and the attempt failed. This has now been fixed.



CR:451706
CR Number:   451706
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3328 20 Dec 2006 Fixed
10.0.0 2777 20 Dec 2006 Fixed
Description
In the SQL Anywhere Console utility, some database properties selected from the Property Viewer (File->Options->Property Viewer) would not have been displayed. This problem has been fixed.



CR:451712
CR Number:   451712
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3329 21 Dec 2006 Fixed
10.0.0 2777 21 Dec 2006 Fixed
Description
If an application using JAVA in the database called a Java method that had an OUT or an INOUT binary parameter, the call would have failed to return the proper value for the binary output parameter. The new JAVA in the db support was not properly handling [[B arguments in the method signature. This problem has been fixed.



CR:451730
CR Number:   451730
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3329 21 Dec 2006 Fixed
10.0.0 2777 21 Dec 2006 Fixed
9.0.2 3426 21 Dec 2006 Fixed
Description
The method SAConnection.BeginTransaction() could have failed with a "Resource governor 'prepared statement' limit exceeded" exception, if there were many undisposed commands.



Here's an example:



using ( SAConnection conn = new SAConnection( "DSN=SQL Anywhere 10 Demo;UID=dba;PWD=sql" ) )

{

conn.Open();



for ( int i = 0; i < 1000; i++ )

{

SATransaction trans = conn.BeginTransaction();

SACommand cmd = new SACommand( "", conn, trans );

cmd.CommandText = string.Format( "INSERT INTO MyTable( id ) VALUES( {0} )", i );

cmd.ExecuteNonQuery();

trans.Commit();

}

}



The SAConnection.BeginTransaction method executes a SQL command to begin a new transaction, but it was not checking if the number of existing prepared statements had already exceeded the limit before executing the SQL. This has been fixed.



CR:451811
CR Number:   451811
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3355 02 Jan 2007 Fixed
Description
For a synchronized consolidated table T, if delete tracking via shadow table and download timestamp via column were enabled, then deployment would have created a trigger called T_del_del that would have added a row to the delete shadow table T_del when the row was deleted from T. If the download timestamp was changed to use a shadow table, then deployment would have created a trigger called T_mod_del that would also have added deleted rows to the shadow table. If both these triggers existed, then deleting a row would have caused an error as both triggers would have attempted to insert the same row into the shadow table. This has now been fixed so that the delete trigger is called T_del if any shadow tables are used, so conflicting triggers are prevented. Similarly the triggers T_del_ins and T_mod_ins are now called T_ins, and T_mod_upd is now called T_upd.



CR:451827
CR Number:   451827
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3329 02 Jan 2007 Fixed
10.0.0 2777 02 Jan 2007 Fixed
Description
When generating DataSets in Visual Studio 2005, table relationships were not added for multi-column foreign keys. This problem has been fixed.



CR:451863
CR Number:   451863
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 3330 02 Jan 2007 Fixed
10.0.0 2778 02 Jan 2007 Fixed
Description
When run on a machine other than the server's machine, the Log Translation utility (dbtran) would have failed with the error:

Cannot open transaction log directory "<log directory name>"

if the -c option was used to obtain the transaction log contents from a running server, and the log file included a path specification but the specified directory did not exist on the machine where dbtran was invoked. This has been fixed.



CR:451870
CR Number:   451870
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3330 02 Jan 2007 Fixed
10.0.0 2778 02 Jan 2007 Fixed
Description
If a cursor was opened requesting SENSITIVE semantics and the query for the cursor was sufficiently simple to bypass optimization and the cursor was opened on the statement without an intervening DESCRIBE, then prefetching could have been incorrectly enabled for that statement, possibly leading to stale results. This has been fixed.



CR:451941
CR Number:   451941
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)
10.0.1 3332 03 Jan 2007 Fixed
10.0.0 2780 03 Jan 2007 Fixed
9.0.2 3428 03 Jan 2007 Fixed
9.0.1 2194 03 Jan 2007 Fixed
Description
When executing a stored procedure that used a string input parameter with a length exceeding 30 bytes (15 wide characters), the OLE DB provider would have overrun a buffer and a run-time error would have resulted. This problem has been fixed.



CR:451959
CR Number:   451959
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 3333 05 Jan 2007 Fixed
10.0.0 2781 05 Jan 2007 Fixed
Description
The server could have crashed, and the database could have become corrupted, if the database included multiple dbspaces and the files were also encrypted. This has been fixed.



CR:452021
CR Number:   452021
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3331 03 Jan 2007 Fixed
10.0.0 2779 03 Jan 2007 Fixed
Description
In the Table Mapping editor, if a table mapping was selected with a Download Subset setting of "User" or "Remote", then the "Column name:" could not be changed on the Download Subset tab. This has been fixed.



CR:452041
CR Number:   452041
Product Name:   SQL Anywhere
Product Component:   SNMP Extension Agent
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3333 03 Jan 2007 Fixed
10.0.0 2781 03 Jan 2007 Fixed
9.0.2 3429 05 Jan 2007 Fixed
Description
When setting a dynamic trap on the rdbmsDbLimitedResourceTable in the RDBMS MIB, the trap would only have fired if a standard query for the same OID was received after the condition was satisfied. If such a query was not received, the dynamic trap would never be

sent. This has been fixed.



CR:452098
CR Number:   452098
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3332 03 Jan 2007 Fixed
Description
The UltraLite Unload Database to XML utility (ulunload), when used on a database with a security certificate, would have resulted in XML output that did not include the security certificate. Ulunload was accessing an old system table for the security certificate. Certificates are now stored in SYSULDATA, within a row with the name "SyncCertificates".



Note that creating and using databases with security certificates worked, and the certificate was properly used. The problem was in unloading such a database and then reloading it, the certificate would have been lost. As a workaround, the certificate can be re-added from the original certificate file using the -t option to the UltraLite Load XML to Database utility (ulload), as in:



ulload -t <CertificateFile> -c dbf=newDB.udb saved.xml



CR:452110
CR Number:   452110
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3332 03 Jan 2007 Fixed
10.0.0 2780 03 Jan 2007 Fixed
9.0.2 3428 03 Jan 2007 Fixed
Description
If an application used the iAnywhere JDBC driver to connect to an Oracle database with a multi-byte charset using the DataDirect Oracle 5.1 ODBC driver, and then attempted to fetch a long varchar column that had multi-byte data, there was a chance that the fetch would have failed with a conversion or translation error. This problem is actually a bug in the DataDirect Oracle 5.1 ODBC driver but a workaround has now been implemented in the iAnywhere JDBC driver.



CR:452119
CR Number:   452119
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3332 03 Jan 2007 Fixed
10.0.0 2780 03 Jan 2007 Fixed
Description
When creating a new UltraLite database, if the specified trusted root certificates file could not have been opened, no error was reported and a new database was successfully created without any trusted root certificates. Any future attempt to synchronize over TLS or HTTPS would have failed with stream error 207 (STREAM_ERROR_SECURE_NO_TRUSTED_ROOTS). This has been fixed so that now if the trusted roots certificate file cannot be opened, an error will be reported immediately and no database will be created.



CR:452126
CR Number:   452126
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3332 04 Jan 2007 Fixed
10.0.0 2780 04 Jan 2007 Fixed
9.0.2 3428 04 Jan 2007 Fixed
Description
The Certificate Generation utility (gencert) cannot handle certificates with an expiry date beyond January 2038. However, if a validity interval was specified that put the expiry date beyond this, gencert would have created an invalid certificate without reporting an error. This has been fixed so that an interval is specified beyond January 1, 2038, gencert will now reduce the expiry to this date.



CR:452220
CR Number:   452220
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3333 05 Jan 2007 Fixed
10.0.0 2781 05 Jan 2007 Fixed
Description
In some rare cases mostly associated with truncated or malformed characters, some character set conversions could produce incorrect converted characters. For example, if a truncated character existed at the end of a source string, a substitution character might not be generated in the converted string. The problem was more likely to occur if ICU was not installed. It has now been corrected.



CR:452225
CR Number:   452225
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)
9.0.2 3429 05 Jan 2007 Fixed
Description
Attempting to execute a query that references a proxy table with an invalid dotted reference (eg. select c1, p1.c2.foo() from proxy_t p1), would very likely have caused the server to crash. The crash for an invalid dotted reference has now been fixed.



Note that using a valid dotted reference like "select c1, u.f() from proxy_t", where f was a user-defined function owned by user u, would have worked, and will still work.



CR:452230
CR Number:   452230
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3334 05 Jan 2007 Fixed
10.0.0 2781 05 Jan 2007 Fixed
Description
The server would have crashed when using a keyset cursor if it was started with the -b command line option ("run in bulk operations mode"). This has been fixed.



CR:452237
CR Number:   452237
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3333 05 Jan 2007 Fixed
10.0.0 2781 05 Jan 2007 Fixed
Description
If the SA GUI installer for MacOS crashed, or is otherwise uncleanly terminated, the machine may have become slow to respond, consuming close to 100% CPU. The GUI installer for MacOS communicates with the setup script through a special "interactive" mode. When the GUI is cleanly terminated, it sends an "exit" command to the setup script and both sides exit. If the GUI is not cleanly terminated, the setup script receives an error, which leads to the script entering an infinite read loop. This has now been fixed by properly handling this error state.



CR:452285
CR Number:   452285
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3334 05 Jan 2007 Fixed
10.0.0 2782 05 Jan 2007 Fixed
Description
A request for the database property, "FreePages" (e.g., select db_property('FreePages')), could have caused the server to fail assertion 101412 - "Page number on page does not match page requested", if the database file was currently in the process of being grown. This would likely have been a very rare occurence, and has been fixed.



CR:452305
CR Number:   452305
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3334 05 Jan 2007 Fixed
10.0.0 2782 05 Jan 2007 Fixed
Description
The SQL statement given by the ODBC InitString parameter may not have been executed, depending on the statement, which including some CALL statements. This has been fixed.



CR:452329
CR Number:   452329
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3337 08 Jan 2007 Fixed
10.0.0 2783 08 Jan 2007 Fixed
9.0.2 3430 08 Jan 2007 Fixed
Description
The server may have crashed while processing a highly recursive query. This has been fixed so that the error "syntactic limit reached" will now be returned in such a situation.



CR:452414
CR Number:   452414
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3332 08 Jan 2007 Fixed
10.0.0 2780 08 Jan 2007 Fixed
9.0.2 3428 08 Jan 2007 Fixed
Description
When setting dynamic traps for the SNMP Extension agent, the modifiers 'K', 'M', 'G',

or 'T' can now be used to specify numeric values. For example, you can set a

dynamic trap to fire if the current cache size exceeds 200 MB using:



Trap1=1.3.6.1.4.1.897.2.1.1.11.1 > 200M



Note, the modifiers are case insensitive.



CR:452418
CR Number:   452418
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2783 08 Jan 2007 Fixed
Description
When using the iAnywhere Solutions 10 Oracle WP driver (version 5.10.00.124) to insert Unicode characters of surrogate pairs 0xD800 )xDF40 into a NCHAR column, the driver only inserts the first two charactors correctly, the rest data would have been corrupted as:

0xD800 )x2020 0x2020 ...

This problem has now been corrected.



CR:452509
CR Number:   452509
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3339 11 Jan 2007 Fixed
10.0.0 2786 11 Jan 2007 Fixed
Description
UltraLite could have produced incorrect results with queries that involved a derived table containing a GROUP BY clause, if there was an outer reference in an expression within that derived table. This has been fixed, but a work-around would be to add an OPTION (FORCE ORDER) clause to the query.



CR:452515
CR Number:   452515
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)
10.0.1 3338 09 Jan 2007 Fixed
10.0.0 2784 09 Jan 2007 Fixed
9.0.2 3431 09 Jan 2007 Fixed
Description
Use of the "expr AS name" syntax in an argument to the functions XMLATTRIBUTES(), XMLFOREST(), or XMLGEN(), inside a CALL statement argument, could have caused the server to crash. This problem has now been fixed.



A workaround is to use "select * from proc()" rather than "call proc", or to evaluate the expression into a variable before passing it as a call argument.



CR:452516
CR Number:   452516
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3337 09 Jan 2007 Fixed
10.0.0 2783 09 Jan 2007 Fixed
Description
The status history entries in the History tab of the Message Properties dialog were incorrect for the QAnywhere client message store.



(1) The originator of a message did not see a 'received' status for a message that was received and acknowledged by another client,

(2) When a message arrived at a destination, the transmission status was not set to 'transmitted', so the status history did not show that the message was 'transmitted',

(3) The transmission status for system messages (push notifications and network status notifications) was not set to 'local', instead it was set to 'untransmitted',

(4) The transmission status for a message sent to a queue in the same message store was not set to 'local', instead it was set to 'untransmitted'.



These problems have now been corrected.



CR:452538
CR Number:   452538
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3339 11 Jan 2007 Fixed
10.0.0 2785 11 Jan 2007 Fixed
Description
If the Mobilink server was communicating with a client when a network disruption occurred, all network I/O could have paused for up to 2 minutes. This has been fixed.



CR:452542
CR Number:   452542
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3338 09 Jan 2007 Fixed
10.0.0 2784 09 Jan 2007 Fixed
Description
If page corruption was detected (usually via page checksums), UltraLite would have failed an assertion, stopping the database process. Page corruption exceptions are now signaled as SQL errors (SQLE_DEVICE_ERROR), which persist until the database is restarted. The database must be shut down following this error.



CR:452628
CR Number:   452628
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3339 11 Jan 2007 Fixed
10.0.0 2785 11 Jan 2007 Fixed
Description
Exceeding the maximum task limit by executing too many concurrent web client HTTP procedure calls was not detected. This may have resulted in calls unexpectedly hanging. This has now been fixed. When a thread of execution has detected that it has exceeded the task limit, it will now issue a -306 "Deadloack detected" error. This indicates that the last available non-waiting TASK thread had attempted to wait on a synchronization event.



A work around is to increase the task limit (number of TASK threads) using the -gn option.



CR:452629
CR Number:   452629
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3348 16 Jan 2007 Fixed
10.0.0 2789 16 Jan 2007 Fixed
Description
When a database uses blank-padded comparison semantics (dbinit 朾 or CREATE DATABASE BLANK PADDING ON), some queries could have returned incorrect results or indexes on string columns could have been corrupt. Validating the database would have identified which table and index were corrupt. Only strings containing a sequence of two or more non-trailing space characters (慭x20) were handled incorrectly.



After this fix is applied, it is possible that indexes that were valid previously could now be considered corrupt. Running dbvalid will identify which indexes are corrupt and should be rebuilt. If the corruption is in a system index, it may be necessary to unload the database with older software, and reload it with a version with this fix.



CR:452632
CR Number:   452632
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3339 12 Jan 2007 Fixed
10.0.0 2785 12 Jan 2007 Fixed
Description
When data is sent from the client to the MobiLink server and then to the consolidated database, and vice versa, character data is translated to allow the server to deal with the possibility of the two ends using a different character set. If some characters to be translated are invalid, the translator cannot process them, but the MobiLink server was not detecting this. This has been fixed. The MobiLink server now checks for characters that have failed the translation process.



CR:452638
CR Number:   452638
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3420 10 Jan 2007 Fixed
Description
QAnywhere makes extensive use of the JRE, so the MobiLink server when run with the QAnywhere messaging option (-- m), may have encountered instabilities in the JRE under heavy load and low memory conditions. To address this the JRE has now been updated. This update contains fixes that significantly improve the stability of the JRE when running under these conditions.



CR:452650
CR Number:   452650
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3420 10 Jan 2007 Fixed
Description
Instabilities in the Java VM may have been encountered when the MobiLink server was running under heavy load and low memory conditions, and executinging Java synchronization scripts. To address this the JRE has now been updated. This update to the JRE contains fixes that significantly improve the stability of the JRE when running under these conditions.



CR:452652
CR Number:   452652
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3390 10 Apr 2007 Fixed
Description
The ICU modules (dbicu10.dll and dbicudt10.dll) were not installed if the Network database client was the only feature selected for installation. This has been fixed.
Workaround Description
 Until fixed a custom install must be coded/built

by the end-user to push those out. This may

minimally require a standalone engine or server

the way the tests sit and may not be acceptable

in all situations.



CR:452657
CR Number:   452657
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3361 29 Jan 2007 Fixed
10.0.0 2796 29 Jan 2007 Fixed
Description
Some inputs to the UNISTR() function could lead to incorrect results or server behaviour. For example, the result of the following was incorrect:

select unistr( repeat( 'x', 1018 ) || '\u0041' )

The result should be identical to:

select repeat( 'x', 1018 ) || unistr( '\u0041' )

Instead, it was equal to repeat( 'x', 1018 ) || '\u0041'. This problem has been fixed.



CR:452660
CR Number:   452660
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3350 19 Jan 2007 Fixed
10.0.0 2792 19 Jan 2007 Fixed
Description
Non-deterministic functions should not be shared in a query, even if they have the identical arguments. However, a query such as:

SELECT RAND() a, RAND() b

would have incorrectly returned the same result for both a and b. This has been fixed.



Note, this problem did not affect non-deterministic user-defined functions.



As well, non-deterministic functions were being eliminated when ordering. For example, the query:

SELECT * FROM EMPLOYEE ORDER BY rand()

should now order the rows by the value of rand() computed for each row.



CR:452671
CR Number:   452671
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2784 11 Jan 2007 Fixed
Description
Attempting to display the command line usage would have caused the usage window to appear, and then disappear almost instantly. This has been fixed.



CR:452761
CR Number:   452761
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 3438 23 Jan 2007 Fixed
Description
The server may have crashed if a connection executed a Java procedure and the connection received a cancel request while executing a createStatement() call. This has been fixed.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具:ReadASADB。
此工具支持ASA v5.0,v6.0,v7.0,v8.0,v9.0,v10.0,v11.0,v12.0等版本。
恢复Sybase SQL Anywhere的工具在国内应该算首创。

ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具

  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集  包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

ReadASADB适用场景

各种误操作:

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

本工具的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------