远程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:665004
CR Number:   665004
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3321 04 Apr 2011 Fixed
12.0.0 2666 04 Apr 2011 Fixed
11.0.1 2585 04 Apr 2011 Fixed
10.0.1 4206 04 Apr 2011 Fixed
Description
When trying to connect using the Ruby DBI interface, the driver did not raise an error if the username/password was invalid. Instead it silently failed. This has been fixed.



CR:665116
CR Number:   665116
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2589 12 Apr 2011 Fixed
Description
The UltraLite Unload utility (ulunload) would not have unloaded an empty Synchronization Profile, such as:



CREATE SYNCHRONIZATION PROFILE "sp" ''



The query used to obtain the profile string for a specified Synchronization Profile returned null. This would have resulted in the profile being skipped during the unload. This has been fixed.



CR:665140
CR Number:   665140
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2586 05 Apr 2011 Fixed
Description
For MobiLink clients that support ECC TLS, support has now been added for RFC 4492 and 256-bit AES ECC cipher suites as well, in addition to the Draft 3 128-bit AES ECC cipher suite they previously supported.



CR:665158
CR Number:   665158
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2586 05 Apr 2011 Fixed
Description
For servers that support ECC TLS, support has now been added for RFC 4492 and 256-bit AES ECC cipher suites as well, in addition to the Draft 3 128-bit AES ECC cipher suite they previously supported.



CR:665176
CR Number:   665176
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3513 28 Nov 2011 Fixed
12.0.0 2767 28 Nov 2011 Fixed
Description
The NEXTVAL operation on sequences did not return an error when executed in a read-only database. This has been corrected. The operation should return an error because the sequence value cannot be updated in the catalog table.



CR:665184
CR Number:   665184
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3365 02 Jun 2011 Fixed
12.0.0 2691 02 Jun 2011 Fixed
Description
The server would have incorrectly returned the error "XPath parser error: syntax error at or before character 0 <--" if a stored procedure contained a SELECT statement with an openxml clause that used a variable for the xpath string. This has been fixed.



CR:665195
CR Number:   665195
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1587 02 Jul 2013 Fixed
12.0.1 3928 02 Jul 2013 Fixed
Description
If a column or variable name was misspelled in a function that was inlined, and the scope into which inlining was performed contained an object with a matching name, incorrect results, or an incorrect error, could have been returned. This has been fixed.



Example:



CREATE FUNCTION func1( @a integer)

RETURNS INTEGER

BEGIN

DECLARE @ret INTEGER;

SET @ret = ( a + 10 ) / 100;

RETURN @ret;

END;



SELECT a, func1( b + c ) as ret

FROM tab;



Expected error is 慍olumn 揳 not found.



CR:665200
CR Number:   665200
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2586 06 Apr 2011 Fixed
Description
The redirector for Apache could have crashed during a synchronization. This has been fixed.



CR:665212
CR Number:   665212
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3401 25 Jul 2011 Fixed
Description
Statements using user-defined functions eligible for inlining could have failed unexpectedly. This problem could have affected databases created with earlier versions and reloaded to a version 12 database if such databases contained views referencing inlinable user-defined functions. Such databases could have failed to be reloaded. This has now been fixed.



CR:665325
CR Number:   665325
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)
12.0.1 3323 06 Apr 2011 Fixed
12.0.0 2667 06 Apr 2011 Fixed
11.0.1 2586 06 Apr 2011 Fixed
Description
When validating a database using the VALIDATE statement or the Validation utility (dbvalid), the operation could not have been cancelled. This has been fixed.



CR:665522
CR Number:   665522
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)
12.0.1 3324 08 Apr 2011 Fixed
12.0.0 2667 08 Apr 2011 Fixed
11.0.1 2587 08 Apr 2011 Fixed
Description
The attachment specified by the attachname parameter of the system procedure xp_sendmail() may not have been received properly by the recipient's mail client. This has been fixed.



CR:665524
CR Number:   665524
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3324 08 Apr 2011 Fixed
12.0.0 2667 08 Apr 2011 Fixed
11.0.1 2587 08 Apr 2011 Fixed
Description
An exclusive table lock on a non-transactional global shared temporary table could have caused the server to crash on subsequent INSERT, UPDATE or DELETE statements. This has been fixed.



All conditions must have been met (non-transactional, shared global temp table,

and LOCK TABLE WITH EXCLUSIVE) for the crash to have occurred. If any of these three can be relaxed, the crash will be avoided.



CR:665535
CR Number:   665535
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3325 11 Apr 2011 Fixed
12.0.0 2668 11 Apr 2011 Fixed
Description
When exporting to a database in the MobiLink Monitor, the values exported to the per-table details table (called mlm_by_table by default) were the per-sync values instead of the per-table values. This has been fixed.



CR:665538
CR Number:   665538
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3324 08 Apr 2011 Failed
Description
ZLIB compression has been added to UltraLiteJ for the Android. This is accomplished with the following addition methods:

setZlibCompression( boolean )

setZlibDownloadWindowSize( int )

setZlibUploadWindowSize( int )

zlibCompressionEnabled()



CR:665630
CR Number:   665630
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3328 13 Apr 2011 Fixed
12.0.0 2670 13 Apr 2011 Fixed
11.0.1 2589 13 Apr 2011 Fixed
Description
Upgrading a database that had been created with the -dba switch (to set the DBA username and password) could have failed. This has been fixed.
Workaround Description
 Rebuild the database using the unload database



CR:665657
CR Number:   665657
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Windows CE 2.0
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3328 13 Apr 2011 Fixed
12.0.0 2670 13 Apr 2011 Fixed
11.0.1 2589 13 Apr 2011 Fixed
Description
The problems described here affect Windows CE 5.x kernels only. Note that Windows Mobile 6 platforms use the Windows CE 5.x kernel.



With version 11.x, the server was not able to create a cache larger than 32MB. Attempting to do so would have caused the error "Not enough memory".



With version 12.x, the server would have automatically and erroneously restricted the cache size to a size smaller than 32MB.



The default maximum cache size was erroneously restricted to a value less than 32MB.



The "percentage" notation for cache sizes (eg, "-c 50p") erroneously based the percentage on a value that was less than 32MB, rather than the total system memory as documented.



These problems have been corrected.



CR:665665
CR Number:   665665
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3326 12 Apr 2011 Fixed
12.0.0 2669 12 Apr 2011 Fixed
Description
The server could have crashed when increasing the CurrentMultiProgrammingLevel using the system procedure sa_server_option() if there wasn't enough memory available. This has been fixed.



CR:665670
CR Number:   665670
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3325 11 Apr 2011 Fixed
12.0.0 2668 11 Apr 2011 Fixed
11.0.1 2587 11 Apr 2011 Fixed
Description
The execution tree in the Plan Viewer window could have partially obscured the bottom part of the tree drawing if a display option for the plan was changed to make it larger (by turning on "Show percent cost", for example). This has been fixed.



CR:665673
CR Number:   665673
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3327 12 Apr 2011 Fixed
12.0.0 2669 12 Apr 2011 Fixed
Description
If the Interactive SQL utility was launched from a program using the Apache Portable Runtime, and standard output and/or standard error file handles were redirected, an internal error could have been reported. This has been fixed.



CR:665684
CR Number:   665684
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)
12.0.1 3325 11 Apr 2011 Fixed
12.0.0 2668 11 Apr 2011 Fixed
11.0.1 2587 11 Apr 2011 Fixed
Description
If an application attempted to establish a Remote Data Access connection to an ASE server, and that connection request failed over to a different ASE server, then the Remote Data Access connection request would have failed. This problem has now been fixed.



CR:665710
CR Number:   665710
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3329 14 Apr 2011 Fixed
12.0.0 2670 14 Apr 2011 Fixed
11.0.1 2591 14 Apr 2011 Fixed
Description
When executing a SELECT statement such as "(select 1)" that begins with open parenthesis, the dbisqlc utility would have reported a syntax error. This problem has been fixed.



CR:665799
CR Number:   665799
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3326 12 Apr 2011 Fixed
12.0.0 2669 12 Apr 2011 Fixed
11.0.1 2588 12 Apr 2011 Fixed
10.0.1 4209 12 Apr 2011 Fixed
Description
On Windows systems, a minidump might not have been generated under certain circumstances. This has been fixed.



CR:665837
CR Number:   665837
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3326 11 Apr 2011 Fixed
12.0.0 2669 11 Apr 2011 Fixed
11.0.1 2588 11 Apr 2011 Fixed
Description
The changes for Engineering case 661112 introduced a bug where the MobiLink client could have crashed, or the check of the certificate_name, certificate_company, or certificate_unit could have failed, if any of the certificate fields were encoded as Unicode in the server's certificate. This has been fixed.



CR:665884
CR Number:   665884
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2598 12 Apr 2011 Fixed
Description
The UltraLite Load utility (ulload) would have crashed if the input XML contained a synchronization profile, but no tables. This has been fixed.



CR:665966
CR Number:   665966
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3479 19 Oct 2011 Fixed
12.0.0 2750 19 Oct 2011 Fixed
Description
A query whose execution used a parallel HashGroupBy operator, may have returned an incorrect result if the MIN or MAX aggregate function was used, or may have caused the server to crash if an aggregate function was used on a numeric or string expression. This has been fixed. A workaround for the problem is to set the database option max_query_tasks to 1.



CR:665980
CR Number:   665980
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 2056 15 Dec 2014 Fixed
12.0.1 4201 15 Dec 2014 Fixed
Description
The Index Consultant could have failed if the tables involved had text indexes. This has been fixed.



CR:665981
CR Number:   665981
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 2056 15 Dec 2014 Fixed
Description
The Index Consultant will no longer print debugging messages to the console window.



CR:666011
CR Number:   666011
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3327 13 Apr 2011 Fixed
12.0.0 2669 13 Apr 2011 Fixed
Description
When a root server was committing and sending log pages to a copy node, the root server could have experienced poor performance. Root servers which had frequent commits, and copy nodes running on slow computers or connected through high latency connections, would have shown the most noticeable poor performance. This has been fixed so that the performance of the copy node latency will have a smaller affect on the root node by using the equivalent of asynchronous log page synchronization.



When using the "SET MIRROR OPTION synchronization_mode = '<value>'" statement, where <value> was asynchronous or asyncfullpage, the server was incorrectly treating this as a synchronous synchronization. This has been fixed as well.



CR:666013
CR Number:   666013
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)
12.0.1 3327 12 Apr 2011 Fixed
12.0.0 2669 12 Apr 2011 Fixed
11.0.1 2589 12 Apr 2011 Fixed
10.0.1 4210 12 Apr 2011 Fixed
Description
Using Sybase Central's searching capabilities to search for a single backslash would have caused Sybase Central to crash. This has been fixed.



CR:666024
CR Number:   666024
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3327 12 Apr 2011 Fixed
Description
Using Sybase Central's searching capabilities to search in a Version 11.0 or earlier database would have caused Sybase Central to crash. This has been fixed.



CR:666123
CR Number:   666123
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1958 26 Jun 2014 Fixed
12.0.1 4130 26 Jun 2014 Fixed
Description
The server did not respond to a cancel during execution of a REGEXP or LIKE predicate if the first operand was a very long constant expression. This has been fixed.



CR:666132
CR Number:   666132
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3537 05 Jan 2012 Fixed
Description
In some cases, expressions could have been evaluated with incorrect domain information. The affected information included:

- precision and scale for NUMERIC values

- length for string values

- differences between string types (e.g., char/varchar/long varchar or binary/varbinary/long binary)



For example, the following statement would have incorrectly returned:

a a_string

1.0000 "1.0000"



select case when dummy_col=0 then 1 else cast(2 as numeric(10,4) ) end case a

, cast( a as varchar ) a_string

from sys.dummy



However, the following statement would have incorrectly returned:

a a_string

1 "1"



select case when 0=0 then 1 else cast(2 as numeric(10,4) ) end case a

, cast( a as varchar ) a_string

from sys.dummy



The incorrect behaviour affected expressions that were partly or fully evaluated at query open time or in procedural code, and affected IF, CASE, NULLIF, ARGN, COALESCE and some other related expression types. This problem has now been fixed.



CR:666182
CR Number:   666182
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3328 15 Apr 2011 Fixed
12.0.0 2589 15 Apr 2011 Fixed
12.0.0 2671 18 Apr 2011 Fixed
Description
An HTTP request over a persistent keep-alive connection to a SQL Anywhere HTTP server may have failed if a previous request on that connection had sent an unexpected body. This has been fixed.



For HTTP methods other than POST, the body may be retrieved using HTTP_VARIABLE('TEXT') or HTTP_VARIABLE('BODY') as dictated by the Content-Type. An HTTP POST method is assumed to have a Content-Type of application/x-www-form-urlencoded unless otherwise specified (as with any other HTTP method, alternate Content-Types may be accessed using HTTP_VARIABLE('TEXT') or HTTP_VARIABLE('BODY')).



CR:666232
CR Number:   666232
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3328 14 Apr 2011 Fixed
12.0.0 2670 14 Apr 2011 Fixed
11.0.1 2589 14 Apr 2011 Fixed
10.0.1 4210 14 Apr 2011 Fixed
Description
The "Go To Table" and "Go To Foreign Key" menu items for the ER Diagram tab did not always work. The "Go To Table" menu item did nothing if the database tree node was collapsed. The "Go To Foreign Key" menu item did not work at all. These have now been fixed.



CR:666434
CR Number:   666434
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3329 15 Apr 2011 Fixed
12.0.0 2670 15 Apr 2011 Fixed
11.0.1 2591 15 Apr 2011 Fixed
Description
When using output redirection for a READ statement that referenced a file containing another READ statement, the dbisqlc utility would have reported an error such as "invalid file number". This problem has been corrected.



Example: "READ file1.sql >& output.txt"



file1.sql:

read file2.sql

go

SELECT ...



file2.sql:

SELECT ...



CR:666566
CR Number:   666566
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3328 18 Apr 2011 Fixed
12.0.0 2671 18 Apr 2011 Fixed
Description
After performing an unload of a resource database, the SQL Anywhere Monitor server console would have shown 'Permission denied' errors for serveral system procedures. Graphing the metrics for "free disk space" would have displayed incorrect values (a horizontal line as if nothing changed). This is caused by the server policy to preserve permissions granted or revoked on objects owned by dbo user that are created in a newly initialized database.



The following describe the steps required to correct this whenever an unload of a database is performed:



1. log in to SQL Anywhere Monitor Web UI as the user 'administrator'.

2. click Administrator on the left pane to open an Administrator dialog

3. under Resource tab, select the resource that had been dbunloaded

4. click Stop button to stop monitoring the resource

5. click Repair... and enter DBA uid/pwd to repair the resource database

6. after done, click Start to start monitoring the DB



After the above steps, the resource should function correctly.



CR:666639
CR Number:   666639
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3331 19 Apr 2011 Fixed
12.0.0 2672 19 Apr 2011 Fixed
11.0.1 2592 19 Apr 2011 Fixed
Description
The detection of processor geometry (number of physical processors, cores and threads) was incorrect for certain Intel x86/x64 processors, including the Intel Xeon E5405. The server would have detected all cores and threads as belonging to a single physical processor. This problem has been corrected.



CR:666731
CR Number:   666731
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2596 25 Apr 2011 Fixed
16.0.0 1915 05 Nov 2013 Fixed
12.0.1 4115 05 Nov 2013 Fixed
Description
Under rare circumstances, the server could have hung when values for WHERE or SUBSCRIBE

BY clauses were being changed in a table with an article. This has been fixed. This fix covers additional cases that were not covered by Engineering case 654952.



CR:666801
CR Number:   666801
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2586 19 Apr 2011 Fixed
Description
The Redirector for Apache on Windows now supports Apache 2.2.15. This newer webserver offers enhanced security.



CR:666845
CR Number:   666845
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3332 19 Apr 2011 Fixed
12.0.0 2672 19 Apr 2011 Fixed
11.0.1 2593 19 Apr 2011 Fixed
Description
The Relay Server admin and monitor extensions may have slowly leaked memory. Eventually, admin or monitoring requests would have failed without any trace in the HTTP error log, IIS access log, or in the Relay Server log. This problem has been fixed so that recycling is no longer necessary. To workaround this problem, users may setup application pool recycling for the admin and monitoring extension.



CR:666960
CR Number:   666960
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3344 19 Apr 2011 Fixed
12.0.0 2678 19 Apr 2011 Fixed
11.0.1 2602 19 Apr 2011 Fixed
Description
When connected to an ASE database, the "Help" menu could have contained redundant separators. This has been fixed.



CR:667001
CR Number:   667001
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3338 08 Jun 2011 Fixed
11.0.1 2617 08 Jun 2011 Fixed
10.0.1 4239 08 Jun 2011 Fixed
Description
If a stored procedure or a user defined function with the hidden definition appeared on the stack when an error occurred, subsequent call to the TRACEBACK function could have returned the statements from the hidden definition. This has been fixed so that the output of the TRACEBACK function now contains the string '<hidden>' instead of the statements from the hidden procedures or user defined functions.



CR:667109
CR Number:   667109
Product Name:   SQL Remote for SQL Anywhere
Product Component:   SQL Remote for Adaptive Server Anywhere
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3367 03 Jun 2011 Fixed
Description
If SQL remote (dbremote) was running in continuous mode, it was possible for it to have have reported "Execution Complete", but no errors or warnings would have been printed to the dbremote log indicating why the process had stopped. This has been fixed.



CR:667115
CR Number:   667115
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2594 20 Apr 2011 Fixed
Description
The language for the SQL Monitor UI was always set to the browser's language no matter what the user's preferred language was. This has been fixed. The UI language is now set as the user's language when they login, or when the current user changes the language in the user settings dialog.



CR:667142
CR Number:   667142
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3335 21 Apr 2011 Fixed
12.0.0 2673 21 Apr 2011 Fixed
11.0.1 2595 21 Apr 2011 Fixed
Description
In very rare timing dependent cases, the server could have crashed when a database was stopping. Also in rare cases, it was possible for an automatically started database to not automatically stop when there where no longer any connections to it. Both of these problems have now been fixed.



CR:667152
CR Number:   667152
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3335 21 Apr 2011 Fixed
Description
Some internal optimization algorithms have been generalized and improved. This may change plans for queries.



CR:667179
CR Number:   667179
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3548 23 Jan 2012 Fixed
11.0.1 2744 23 Jan 2012 Fixed
Description
The Start Server in Background utility (dbspawn), when used with -p option to specify the OS process id, was reporting a process id for the started server of 0 on Windows Vista, Windows 7 and Windows 2008. Windows XP, Windows 2003 and Unix were not affected. This has been fixed so that the process id of the started server is reported correctly.



CR:667314
CR Number:   667314
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3336 21 Apr 2011 Fixed
12.0.0 2675 25 Apr 2011 Fixed
11.0.1 2598 25 Apr 2011 Fixed
Description
If more than one connection attempted to install or remove Java external environment objects at the same time, then there was a chance the server would have crashed or failed assertions. This problem has now been fixed.



CR:667316
CR Number:   667316
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3336 21 Apr 2011 Fixed
Description
When unloading a database, the server would have incorrectly output a "dynamic result sets" clause for non-external environment procedures in the reload.sql file. This problem has now been fixed and the "dynamic result sets" clause is now only output for external environment procedures.



There are a few points of note:

1) this problem would only have occurred with stored procedures that were created using an older SA 12.0.1 server

2) this fix will only affect new procedures that are created

3) the existence of the "dynamic result sets" clause for non-external environment procedures is in fact a no-op and does not affect performance or behaviour of the non-external environment procedure.



CR:667441
CR Number:   667441
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3337 25 Apr 2011 Fixed
12.0.0 2674 25 Apr 2011 Fixed
11.0.1 2597 25 Apr 2011 Fixed
10.0.1 4214 25 Apr 2011 Fixed
Description
Misleading error messages would have been returned to the client when opening a connection using an invalid DSN. This problem has been fixed.



CR:667518
CR Number:   667518
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3338 25 Apr 2011 Fixed
12.0.0 2675 25 Apr 2011 Fixed
Description
When merging recent data distribution information into a table's histogram, the server could have allocated up to one database page worth of data outside of the database cache and then failed to free the memory. The leak could eventually have caused the server to fail due to a lack of memory on 32-bit platforms, or due to lack of swap space on 32-bit or 64-bit platforms. This has now been corrected.



CR:667519
CR Number:   667519
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3336 25 Apr 2011 Fixed
Description
The following get-by-name APIs were missing from ResultSet for UltraLiteJ for Android and have now been added:

java.io.InputStream getBlobInputStream( String name )

boolean getBoolean( String name )

byte[] getBytes( String name )

java.io.Reader getClobReader( String name )

java.util.Date getDate( String name )

DecimalNumber getDecimalNumber( String name )

double getDouble( String name )

float getFloat( String name )

long getLong( String name )

int getSize( String name )

String getString( String name )

UUIDValue getUUIDValue( String name )

boolean isNull( String name )



CR:667520
CR Number:   667520
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3338 25 Apr 2011 Fixed
12.0.0 2674 25 Apr 2011 Fixed
11.0.1 2598 25 Apr 2011 Fixed
Description
A new command line option 'uninstallall' (or 'ua') has been added to SetupVSPackage.exe. When specified, the 'uninstallall' option will cause SetupVSPackage to remove all versions of SQL Anywhere assemblies from the Global Assembly Cache.



For example:

SetupVSPackage.exe /ua



CR:667668
CR Number:   667668
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3338 26 Apr 2011 Fixed
Description
The following two extensions have been made to the -xa option:

1) The dbn= value can be "*", which means any database can use this server as an arbiter.

2) The auth= value can be:

a) omitted, which means no validation of the authentication string provided by a mirror server is done.

b) a single value, which means all databases must use the same authentication string.

c) a list of values with the same number of entries as specified by dbn= (i.e. previous behavior)



CR:667672
CR Number:   667672
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3342 02 May 2011 Fixed
12.0.0 2676 02 May 2011 Fixed
11.0.1 2600 02 May 2011 Fixed
Description
The Entity Framework function 'DiffDays' was not mapped to the SQL Anywhere function 'Days'.



For example:

Entities db = new Entities();

var query = db.SalesOrders.Select( x => x ).Where( x => EntityFunctions.DiffDays( x.OrderDate, DateTime.Now ) > 100 );

string trace = ( ( ObjectQuery ) query ).ToTraceString();



This problem has been fixed.



CR:667675
CR Number:   667675
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3339 27 Apr 2011 Fixed
12.0.0 2675 27 Apr 2011 Fixed
Description
After the Database Documentation Wizard completed, a prompt asked whether to view the generated documentation. If "Yes" was clicked, a browser window was supposed to open to show the documentation, but the browser failed to open if the path to the generated files contained a space. This has now been fixed.



CR:667686
CR Number:   667686
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3339 27 Apr 2011 Fixed
12.0.0 2675 27 Apr 2011 Fixed
11.0.1 2599 27 Apr 2011 Fixed
Description
If an application attempted to cancel or drop a connection that was in the process of making a connection-scoped external environment call, then there was a very small chance the server would have crashed. This problem has now been fixed.



CR:667716
CR Number:   667716
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3339 27 Apr 2011 Fixed
Description
A new name type ul_name_type_qualified has been added to ul_column_name_type in tjhe header ulcpp.h. When this new name type is used in conjunction with the GetColumnName function in the ULResultSetSchema class, a qualified name for the associated column in the ResultSet can be obtained, if possible. If the column represents a correlated table, then that qualified name is used; if the column represents a table column, then that qualified name is used; if the column has an alias name, then that name is used. Otherwise, an empty string is returned.



CR:667720
CR Number:   667720
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3339 27 Apr 2011 Fixed
Description
The following methods have been implemented in ResultSetMetadata for UltraLiteJ for Android:

String getAliasName( int column_no )

String getDomainName( int column_no )

String getCorrelationName( int column_no )

String getQualifiedName( int column_no )

String getTableColumnName( int column_no )

String getTableName( int column_no )

String getWrittenName( int column_no )



Previously, they returned the value "N.Y.I.". They now return values that closely approximate those returned by the UltraLiteJ runtime for Blackberry.



CR:667762
CR Number:   667762
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3340 27 Apr 2011 Fixed
12.0.0 2675 27 Apr 2011 Fixed
11.0.1 2599 27 Apr 2011 Fixed
Description
SetupVSPackage.exe would have failed to add some dlls to the Global Assembly Cache on 64 bit Windows systems. This problem has been fixed.



Also, a new command line option 'salocation' (or 'sal') has been added to SetupVSPackage to allow specifying the SQL Anywhere install location. If 'salocation' is specified, SetupVSPackage will use it to locate the necessary dlls. If 'salocation' is not specified, SetupVSPackage will use SQL Anywhere registry keys to locate the dlls.



CR:667900
CR Number:   667900
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3340 27 Apr 2011 Fixed
12.0.0 2676 27 Apr 2011 Fixed
11.0.1 2599 27 Apr 2011 Fixed
Description
If the Transact-SQL ROWCOUNT option was used to limit the number of rows returned by a cursor, the cursor may have skipped the first row in the result set in some cases. This incorrect behaviour only occurred for queries in which optimization was bypassed, and the plan contained a SortTopN operator, rather than a RowLimit operator. This incorrect behaviour was introduced as part of the fix for Engineer case 653706, and has now been fixed.



CR:667901
CR Number:   667901
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3340 27 Apr 2011 Fixed
12.0.0 2676 27 Apr 2011 Fixed
11.0.1 2599 27 Apr 2011 Fixed
10.0.1 4296 08 Nov 2011 Fixed
Description
If an application connected via jConnect and then subsequently attempted to use the {} JDBC escape sequence when making a stored procedure call, then there was a chance the server would have returned an incorrect "variable @p0 not found" error at the time the stored procedure statement or result set was closed. This problem has now been fixed.



CR:667902
CR Number:   667902
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2596 27 Apr 2011 Fixed
Description
SQL Anywhere EBF installs would have failed to update the SQL Anywhere Monitor (Developer) database (samonitor.db) if the SQL Anywhere Monitor had been used after the EBF build date. This has now been fixed.



CR:667907
CR Number:   667907
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 4216 27 Apr 2011 Fixed
Description
When creating a server message store for QAnywhere in Sybase Central, the process could have failed with the error message "Can't find MobiLink setup scripts". It has now been fixed.



Note, this problem occurred only on Linux systems.



CR:667927
CR Number:   667927
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3328 27 Apr 2011 Fixed
12.0.0 2670 27 Apr 2011 Fixed
11.0.1 2589 27 Apr 2011 Fixed
Description
The SQL Anywhere .NET Provider, running in 64-bit mode, might have inadvertently attempted to load a 32-bit language resource DLL (e.g., dblgen12.dll) and failed with an error. This problem has been corrected.



CR:667930
CR Number:   667930
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3340 27 Apr 2011 Fixed
12.0.0 2676 27 Apr 2011 Fixed
Description
In rare situations, the server could have crashed when generating or updating a histogram for a string column. This problem has been corrected.



CR:667932
CR Number:   667932
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3340 02 May 2011 Fixed
12.0.0 2676 02 May 2011 Fixed
Description
For a table with no foreign keys, SQLForeignKeys would have returned a single row with NULLs in most columns. This problem could have resulted in a java.lang.NullPointerException in the Interactive SQL utility's Query Editor. This has been fixed so that when the table has no foreign keys, no rows will be returned.



CR:667934
CR Number:   667934
Product Name:   UltraLite
Product Component:   Analyser Java Classes
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3340 27 Apr 2011 Fixed
Description
The attempt to add a second primary key was not diagnosed in an ALTER TABLE statement. This has been corrected.



CR:668109
CR Number:   668109
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3341 02 May 2011 Fixed
12.0.0 2676 02 May 2011 Fixed
11.0.1 2676 02 May 2011 Fixed
Description
Attempting to start two High Availability partner servers without state files (for example, starting them for the first time) could have, in rare timing dependent cases, failed to have one server start as the primary. If this occurred, one partner started as the mirror, and the other partner server looped indefinitely attempting to determine which role it should take. This has been fixed.



Also, if a mirror server was in the middle of taking over as the primary when it was shutdown, the database shutdown could have hung until any remaining connections were disconnected. This has been fixed.



CR:668136
CR Number:   668136
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3342 02 May 2011 Fixed
12.0.0 2677 02 May 2011 Fixed
Description
An SQL Anywhere resource may have generated an alert for "No Recent Backup Recorded", even though a client-side backup had recently been done. This has been corrected so that the alert now clearly indicates that it pertains to server-side backups only.



CR:668141
CR Number:   668141
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3341 02 May 2011 Fixed
12.0.0 2676 02 May 2011 Fixed
11.0.1 2600 02 May 2011 Fixed
10.0.1 4218 02 May 2011 Fixed
Description
Calling the method SATcpOptionsBuilder.ClientPort could have caused the exception InvalidCastException to have been thrown.



For example:

SATcpOptionsBuilder options = new SATcpOptionsBuilder( "localonly=yes;port=6873" );

string cport = options.ClientPort;



This problem has been fixed.



CR:668396
CR Number:   668396
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3348 02 May 2011 Fixed
Description
Join queries with predicates in the WHERE or ON clauses that involved columns not in indexes have now been improved.



CR:668397
CR Number:   668397
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3343 02 May 2011 Fixed
Description
The SQL Passthrough feature was removed in version 12 and three associated tables (sync_passthrough_progress, sync_passthrough_script, and sync_passthrough_status) were dropped. The Unload utility did not properly handle the case where a pre-version 12 database contained these tables and they were not empty. This has been fixed.



CR:668425
CR Number:   668425
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3341 02 May 2011 Fixed
12.0.0 2676 02 May 2011 Fixed
Description
The MobiLink client now prints information about the operating system and machine architecture on which it is running to the log. It also prints the platform for which the executable was compiled. This is similar to what the MobiLink server and the database server already do.



CR:668603
CR Number:   668603
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3344 03 May 2011 Fixed
12.0.0 2678 03 May 2011 Fixed
11.0.1 2602 24 May 2011 Fixed
Description
In rare cases, an application could have failed to connect because of a TCP/IP communication link failure. No specific reason for the failure would have been logged to the file specified by the LOGFILE connection parameter. This has been fixed.



Note, this problem affected the .Net provider, the ODBC, JDBC and OLEDB drivers as well.



CR:668612
CR Number:   668612
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3344 04 May 2011 Fixed
12.0.0 2678 04 May 2011 Fixed
Description
The MobiLink Replay utility (mlreplay) could have crashed when synchronizing unsigned big integers using the Replay API. This has been fixed.



CR:668716
CR Number:   668716
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3740 31 May 2012 Fixed
11.0.1 2820 31 May 2012 Fixed
Description
In rare circumstances, a database with snapshot isolation enabled could have triggered

an assertion while updating values indexed by an immediate text index. This problem required high contention on the base table. This has been fixed.



CR:668757
CR Number:   668757
Product Name:   SQL Remote for SQL Anywhere
Product Component:   Database Tools Interface
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3346 04 May 2011 Fixed
Description
SQL Remote for SQL Anywhere (dbremote) now supports HTTP and HTTPS as a message type for SQL Remote messages for remote databases. Users wishing to use the HTTP or HTTPS message type from a remote database will configure the remote database using the SET REMOTE OPTION command, in the same way that the FILE, FTP and SMTP message type is configured. The HTTP/HTTPS message type uses the following control parameters that are set by the SET REMOTE OPTION statement:



url : Specify the server name or IP address and optionally the port number of the HTTP server being used, separated by a semi-colon. If requests are being passed through the Relay Server, you can optionally add an URL suffix to indicate which server farm the request should be passed to. url=抯erver-name[:port-number][url_suffix]



https : Specify whether to use HTTPS (https=YES) or HTTP (https=NO).



certificate : To make a secure (HTTPS) request, a client must have access to the certificate used by the HTTPS server. The necessary information is specified in a string of semicolon-separated key/value pairs. You can use the file key to specify the file name of the certificate, or you can use the certificate key to specify the server certificate in a string. You cannot specify a file and certificate key together. The following keys are available:

file : The file name of the certificate.

certificate : The certificate itself.

company : The company specified in the certificate.

unit : The company unit specified in the certificate.

name : The common name specified in the certificate.

Certificates are required only for requests that are either directed to an HTTPS server, or can be redirected from a non-secure to a secure server. Only PEM formatted certificates are supported.

certificate=択ey=value[:key=value]'



user : The HTTP server user ID. Authenticates to third-party HTTP server and gateways using RFC 267 Basic Authentication. user=抲serid



password : The HTTP server password. Authenticates to third-party HTTP server and gateways using RFC 267 Basic Authentication. password=抪assword



debug : When set to YES, all HTTP commands and response are displayed in the output log. This information can be used for troubleshooting HTTP support problems. The default is NO.



proxy : Specifies the URI of a proxy server. For use when SQL Remote must access the network through a proxy server. Indicates that SQL Remote is to connect to the proxy server and send the request to the message server through it. proxy=抙ttp://proxy-server[:port-number]



client_port : Identifies the port number on which SQL Remote communicates using HTTP. It is provided for and recommended only for connections through firewalls that filter "outgoing" TCP/IP connections. You can specify a single port number, ranges of port numbers, or a combination of both. Specifying a low number of client ports could result in SQL Remote being unable to send and receive messages if the operating system has not released the ports in a timely manner after SQL Remote closes the port on a previous run. client_port=抧nnn[-mmmm]



Unlike the FTP or SMTP message type, which relies on a third-party FTP or E-mail server, the HTTP message type makes use of the web services functionality that exists in the SQL Anywhere database engine to act as

the HTTP server, which we refer to as a "message server". In order to setup the message server, you only need to run the sr_add_message_server on the consolidated database, and ensure that the database server has

been started with the -xs http[s] switch. If starting the HTTP[S] listener on a database server hosting the consolidated database is a performance or security concern, then you can use a separate database server, as long as the database you run sr_add_message_server on has identical SQL Remote definitions to your consolidated database. For more information on how to setup a consolidated database to be a message server, how to setup a separate message server, or how to use the Relay Server to forward HTTP requests from remote database to the message server, please read the tutorials and full documentation.



The SQL Remote documentation has been updated to include information about the new message type. In the SQL Anywhere installation directory, see:

documentation/en/pdf/sqlremote1201.pdf



CR:668765
CR Number:   668765
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3345 05 May 2011 Fixed
12.0.0 2679 05 May 2011 Fixed
Description
When running the Deployment Wizard, clearing the default MSI name in the Destination Path page of the wizard and clicking the Next button would have caused an unhandled exception. This occurred due to the fact that the filename was not valid. This has been corrected by graying out the Next button if the filename is left blank.



CR:668766
CR Number:   668766
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3354 18 May 2011 Fixed
12.0.0 2684 18 May 2011 Fixed
Description
When creating a 64-bit Deployment wizard MSI install, containing both 64-bit and 32-bit software, only one set of Sybase Central plugins would have been registered when installing on a 64-bit system. This has been corrected so that both 32-bit and 64-bit plugins are now registered.



CR:668768
CR Number:   668768
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3353 16 May 2011 Fixed
12.0.0 2684 16 May 2011 Fixed
Description
After uninstalling a Deployment wizard .MSI install made with default contents, several .JPR files would have been left behind in the SQL Anywhere 12\java directory.

This has been fixed so that these files are now correctly uninstalled.



CR:668771
CR Number:   668771
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3359 25 May 2011 Fixed
12.0.0 2687 25 May 2011 Fixed
Description
When building a Deployment wizard install MSI, and select Chinese (ZH) as the deployment language. progress messages would have been displayed in English. This has been corrected so that they are now displayed in Chinese.



CR:668791
CR Number:   668791
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3345 05 May 2011 Fixed
12.0.0 2679 05 May 2011 Fixed
11.0.1 2603 05 May 2011 Fixed
Description
When the Relay Server Outbound Enabler failed a backend connection test, it may have crashed, or have been unable to recover even after the backend became available again. This has been fixed.



CR:668820
CR Number:   668820
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3345 04 May 2011 Fixed
Description
Calling the method DatabaseManager.release() would have caused the error: "No implementation found for native Lcom/ianywhere/ultralitejni12/implementation/JniDbMgr;.release ()V". This has been corrected by implementing the method DatabaseManager.release().



Note that prior to this fix, UltraLiteJ for Android would have done the equivalent of DatabaseManager.release() when the UltraLiteJ application terminated. Now it is possible for the application to execute DatabaseManager.release() at a specific point in time.



CR:668832
CR Number:   668832
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3347 06 May 2011 Fixed
12.0.0 2680 06 May 2011 Fixed
11.0.1 2604 06 May 2011 Fixed
Description
The dblsn command line option -qi prevents the tray icon or window from being displayed. This behaviour is identical to the -qi option of the database server. The option has existed since 11.0.1, but was not referenced in the usage text or the documentation. The usage text has been corrected



CR:668833
CR Number:   668833
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3347 06 May 2011 Fixed
12.0.0 2680 06 May 2011 Fixed
11.0.1 2604 06 May 2011 Fixed
Description
The dbmlsyc command line option -qi prevents the tray icon or window from being displayed. This behaviour is identical to the -qi option of the database server. The option has existed since 11.0.1, but was not referenced in the usage text or the documentation. The usage text has been corrected



CR:668855
CR Number:   668855
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Linux
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2586 09 May 2011 Fixed
Description
Attempting to start Sybase Central on Linux systems would have failed with the error message:



"The library /opt/sqlanywhere11/lib32/libulhltool11_r.so could not be loaded. This may be because the provider is being re-loaded (in which case you need to restart the viewer) or because the library could not be found in the SQL Anywhere installation. Service management will not be available."



This has been corrected.



CR:668989
CR Number:   668989
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3347 09 May 2011 Fixed
12.0.0 2680 09 May 2011 Fixed
11.0.1 2604 09 May 2011 Fixed
Description
In rare timing dependent cases, a transaction which was successfully committed on a primary server could have been lost. In order for there to have been a chance of this occurring, all of the following needed to be true:

- the application was connected to a primary server that lost quorum (the server lost the connection to both the mirror and arbiter servers)

- the application stayed connected to this server (the old primary server) even though the network connection to other servers dropped

- the application was in the middle of committing a transaction between the time that the old primary server lost its connection to the mirror and arbiter server, and when the old primary server restarted as the new mirror server because it lost quorum

- the old mirror server took over as the new primary (the mirror server must have been able to connect to the arbiter server for this to occur)



This has been fixed so that the application may now receive the new error for this situation, "The transaction may not be committed because the primary server lost quorum."



CR:669009
CR Number:   669009
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3301 05 May 2011 Fixed
Description
When upgrading from 12.0.0 to 12.0.1, if the 12.0.0 samples had been installed to a non-default location, the upgrade to 12.0.1 installed any new or reorganized samples to the default sample location. This has now been fixed.



Note that 12.0.1 EBFs can be now applied directly to 12.0.0 installations - effectively performing an upgrade. Therefore if a 12.0.0 installation has not yet been upgraded to 12.0.1, use of a 12.0.1 EBF with this fix will avoid this problem. If a 12.0.0 installation had been upgraded with a build without this fix, uninstalling the product will not remove all the sample files. Those files will need to be removed manually.



CR:669032
CR Number:   669032
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 4222 06 May 2011 Fixed
Description
When starting the 64-bit Linux server with the GTK GUI, and neither the server name nor the database file is specified (e.g. using the icon), a dialog is presented to enter server startup information. When this dialog closed, the server may have crashed. This has now been fixed.



CR:669218
CR Number:   669218
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3347 06 May 2011 Fixed
12.0.0 2680 06 May 2011 Fixed
12.0.0 2604 06 May 2011 Fixed
Description
Using an encrypted command file did not work on big endian computers (typically running Solaris or AIX). The symptom was an error message "Could not decrypt command file." This has been fixed.



CR:669227
CR Number:   669227
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3347 06 May 2011 Fixed
12.0.0 2680 06 May 2011 Fixed
11.0.1 2604 06 May 2011 Fixed
Description
On systems running Windows Vista or later, when using the Visual Studio Add Connection wizard the SQL Anywhere .NET provider listed USER DSNs only in the ODBC Data Sources drop-down list. The SYSTEM DSNs are omitted. This problem has been corrected. The SetupVSPackage tool must be run to install this fix.



It should be noted that on 64-bit Windows, only the 64-bit SYSTEM DSNs are listed (after this correction). Any 32-bit SYSTEM DSNs are not displayed. In Visual Studio 2008's design environment (which is 32-bit on 64-bit platforms), the Test Connection button will attempt to establish a connection using the 32-bit equivalent of the 64-bit DSN. If the 32-bit DSN does not exist, the test will fail.



CR:669235
CR Number:   669235
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3349 10 May 2011 Fixed
12.0.0 2681 10 May 2011 Fixed
11.0.1 2605 10 May 2011 Fixed
Description
When starting the QAnywhere Agent (qaagent) with the command line option "-qi", the MobiLink Listener and the MobiLink Client processes were not also launched with "-qi" options, resulting in system tray icons on Windows Mobile devices. This has been corrected.



CR:669242
CR Number:   669242
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3354 04 Jul 2011 Diagnostic Provided
12.0.0 2684 06 May 2011 Fixed
11.0.1 2606 06 May 2011 Fixed
Description
An ArrayIndexOutOfBoundsException could have been thrown during a COMMIT. This has been fixed.



CR:669407
CR Number:   669407
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3348 09 May 2011 Fixed
Description
When uninstalling on Solaris, it was possible to see an error like:

find: stat() error /opt/sybase/sqlanywhere12/sun/jre160/lib: no such file or directory



This has been fixed. It should be noted that despite the error, the uninstaller would have completed successfully.



CR:669408
CR Number:   669408
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3355 20 May 2011 Fixed
Description
On Unix, if SQL Anywhere was installed into the default location as user A, logging in as user B and checking for updates would have failed with an error like, "Could not check for updates." The installed.ini file only had read and write permissions for the current user and group. This has been fixed by giving broader permissions on the file so it could be used by "other" users.



CR:669411
CR Number:   669411
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3350 10 May 2011 Fixed
12.0.0 2682 10 May 2011 Fixed
11.0.1 2606 11 May 2011 Fixed
Description
When run on some Linux distributions, the Interactive SQL utility (or any of the graphical administration tools) may not have displayed Chinese characters correctly. This has been fixed.



Workaround:

1. Shut down any graphical administration tools (Sybase Central, Interactive SQL (dbisql), the MobiLink Monitor, SQL Anywhere Monitor, or SQL Anywhere Console utility (dbconsole) that are running.

2. Run the following commands:

mkdir $SQLANY12/sun/jre160_x86/lib/fonts/fallback

ln -s /usr/share/fonts/truetype/arphic/*.ttc $SQLANY12/sun/jre160_x86/lib/fonts/fallback

ln -s /usr/share/fonts/truetype/wqy/*.ttc $SQLANY12/sun/jre160_x86/lib/fonts/fallback



CR:669412
CR Number:   669412
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3364 31 May 2011 Workaround
12.0.0 2690 31 May 2011 Workaround
11.0.1 2615 31 May 2011 Workaround
Description
When run on Linux systems, the Service utility (dbsvc) requires the LSB init-functions. Some Linux distributions do not installed by default so the must be installed manually in order to use dbsvc

For example, on Fedora, run the following command:

yum install redhat-lsb redhat-lsb.i686



CR:669431
CR Number:   669431
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3349 11 May 2011 Fixed
12.0.0 2681 11 May 2011 Fixed
11.0.1 2606 11 May 2011 Fixed
Description
When attempting to cancel a Remote Data Access request to an ODBC based remote server, there was a very small chance that the server would have become unresponsive if all three of the following was true:

- the local server was running on a Windows based system

- the local server had a restricted (or small) number of CPUs or cores (either due to the limitations of the server machine or VM, or as a result of using the -gt or -gtc command line option)

- the remote server was not defined to utilize the new "driver=SQL Anywhere Native" feature



This problem has now been fixed.



CR:669435
CR Number:   669435
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2604 09 May 2011 Fixed
Description
On Unix systems, when using the Service utility (dbsvc) to create a service for the MobiLink client (dbmlsync), the following error would have been reported:



svc_t_dbmlsync: No such file or directory



This was due to the file svc_t_dbmlsync not having been installed in the bin32/dbsvc_scripts directory. This has been corrected.





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