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

 

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!

如有问题,请联系我!

QQ :289965371 联系我们获取数据库技术支持!
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:653055
CR Number:   653055
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3268 23 Dec 2010 Fixed
12.0.0 2627 23 Dec 2010 Fixed
11.0.1 2541 23 Dec 2010 Fixed
Description
Any parameters entered on the MobiLink Monitor's command line with a Multibyte Character Set would have been mangled. This has been fixed.



CR:653058
CR Number:   653058
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3268 23 Dec 2010 Fixed
12.0.0 2627 23 Dec 2010 Fixed
11.0.1 2541 23 Dec 2010 Fixed
10.0.1 4165 23 Dec 2010 Fixed
Description
When creating a rule with a "Custom" schedule type, the schedule that was saved could have been incorrect if "Run rule every" was turned off in the "Schedule Editor" window. The rule was saved such that it was run every 10 minutes. This has been fixed.



CR:653070
CR Number:   653070
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3144 04 Jan 2011 Fixed
12.0.0 2631 04 Jan 2011 Fixed
11.0.1 2545 04 Jan 2011 Fixed
Description
A COMMIT could have failed after a failed synchronization involving clobs or blobs. The failure could have left the blobs and/or clobs present in the transaction log in a bad state. This has been corrected. A work-around is to disconnect and then to reconnect to the database.



CR:653122
CR Number:   653122
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 4001 27 Jan 2011 Fixed
Description
The ADO.NET provider would have returned an empty string for an error message in some scenarios. This problem has been fixed.



CR:653125
CR Number:   653125
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 4000 18 Jan 2011 Fixed
Description
During the loading of data using "ulconv load", columns whose values were NULL may have been set to default values. This has been fixed.



CR:653158
CR Number:   653158
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3275 14 Jan 2011 Fixed
12.0.0 2632 14 Jan 2011 Fixed
Description
The methods ULConnection.CountUploadRows, ULConnection.GetLastDownloadTime, and ULConnection.ResetLastDownloadTime would have failed on Windows desktop when provided named publications instead of ULConnection.SYNC_ALL_DB. This has been fixed.



CR:653183
CR Number:   653183
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3273 12 Jan 2011 Fixed
12.0.0 2631 12 Jan 2011 Fixed
Description
The NUM_CONNECTED_SYNCS ppv metric and the "Synchronizations", "Started Synchronization Rate", "Synchronizations Started", and "Unknown Connected Clients" metrics incorrectly considered syncs that had failed during the download and were waiting to be restarted as being connected and so would show an incorrect value in the log or in the SA Monitor. Also, as a consequence, the server would prompt for confirmation to kill active syncs during hard shutdown even if all the syncs in the system are waiting to be restarted. This has been fixed.



CR:653184
CR Number:   653184
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 3134 04 Jan 2011 Fixed
Description
It was possible for the server to crash while opening a statement that used a parallel execution plan if specific types of errors were detected while building the plan. One particular form of the error causing this problem could arise when using a spatial predicate on systems with Pentium III processors. Instead of reporting an error, it was possible under specific circumstances for the server to crash. This has now been fixed.



CR:653185
CR Number:   653185
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 3143 04 Jan 2011 Fixed
Description
Specific spatial operations could have caused a server crash when running on systems with Pentium III processors. This has been fixed. These operations now correctly return an error.



CR:653245
CR Number:   653245
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 3270 05 Jan 2011 Fixed
12.0.0 2629 05 Jan 2011 Fixed
11.0.1 2542 05 Jan 2011 Fixed
Description
The value for the column "columns" for the system view SYS.SYSFOREIGNKEYS is generated using a LIST() function, but the function did not include an ORDER BY and so the result returned could have varied. This has been fixed by adding an ORDER BY clause.

Note, the system view must be recreated by upgrading or rebuilding the database for the new view definition to be used.



CR:653316
CR Number:   653316
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 3286 09 Feb 2011 Fixed
12.0.0 2644 09 Feb 2011 Fixed
Description
When deleting rows from an UltraLite database, the Interactive SQL utility would have incorrectly reported the number of rows affected by a DELETE. The message "1 row(s) deleted" would have been shown in the Message pane, regardless of how many rows were deleted. This has been fixed.



CR:653467
CR Number:   653467
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3274 12 Jan 2011 Fixed
12.0.0 2632 12 Jan 2011 Fixed
Description
If an UltraLite database had a table with a LONG VARCHAR column, and that column contained XML data, attempting to view that data in the Interactive SQL utility's cell editor (in the XML Outline tab) could have failed with the error: "An invalid XML character (Unicode: 0x0) was found in the element content of the document". This is now fixed.



CR:653470
CR Number:   653470
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3143 04 Jan 2011 Fixed
12.0.0 2627 04 Jan 2011 Fixed
11.0.1 2541 04 Jan 2011 Fixed
Description
MobiLink clients (except UltraLiteJ) could have failed to authenticate to third party servers or proxies when using digest HTTP authentication. In particular, if the third party server's or proxy's response contained nextnonce attribute in the Authentication-Info header. This has been fixed.



CR:653540
CR Number:   653540
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 3152 05 Jan 2011 Fixed
12.0.0 2628 05 Jan 2011 Failed
Description
The Relay Server State Manager (rshost) could have crashed if initialization failed. Specifically, if creating the shared memory failed. This has been fixed.



CR:653588
CR Number:   653588
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 3269 11 Jan 2011 Fixed
12.0.0 2628 11 Jan 2011 Fixed
11.0.1 2542 11 Jan 2011 Fixed
10.0.1 4166 11 Jan 2011 Fixed
Description
If tracing was suddenly detached (because, for example, the server receiving the tracing data was shut down) at the same time as a deadlock occurred, a deadlock victim may have failed to write a ROLLBACK to the transaction log. This may have lead to an incorrect partial commit of a deadlocked transaction. This has been fixed. This problem is expected to be very rare.



CR:653590
CR Number:   653590
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 3269 10 Jan 2011 Fixed
12.0.0 2628 10 Jan 2011 Fixed
11.0.1 2543 10 Jan 2011 Fixed
10.0.1 4167 10 Jan 2011 Fixed
Description
Diagnostic tracing, or application profiling to LOCAL DATABASE could not be used when the server was started with the command line option -sb 0 (disable broadcast listener). This has been corrected. A workaround is to manually supply a connection string (ATTACH TRACING TO <connstr>) with the DoBroadcast=NO option, rather than using the LOCAL DATABASE clause.



CR:653591
CR Number:   653591
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 3272 10 Jan 2011 Fixed
12.0.0 2630 10 Jan 2011 Fixed
11.0.1 2543 10 Jan 2011 Fixed
10.0.1 4167 10 Jan 2011 Fixed
Description
Attempting to attach tracing to an older version database file could have caused the server to crash. This has been fixed so that attempting to attach tracing to an older version file now returns the error "ATTACH TRACING could not connect to the tracing database" (-1097).



CR:653606
CR Number:   653606
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)
3270 04 Jan 2011 Fixed
12.0.0 2628 04 Jan 2011 Fixed
Description
Entering an invalid TIME value when editing a result set could have caused then Interactive SQL utility to report an internal error. This has been fixed.



CR:653706
CR Number:   653706
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 3093 05 Jan 2011 Fixed
11.0.1 2541 05 Jan 2011 Fixed
Description
The 'TOP limit START AT startat' and 'LIMIT limit OFFSET offset' constructs now support 1 - simple arithmetic expressions for 'limit', 'offset', 'startat' arguments;

2 - TOP supports the 'ALL' limit indicating that all rows are to be returned after the specified 'startat';

3 - the maximum value for (limit + offset) is now 9223372036854775807 = 2^64-1



The new grammar is as follows:

TOP range_expression range_offset

TOP T_ALL range_offset

LIMIT range_expression [OFFSET range_expression]



range_expression:

integer_or_var | '(' simple_expression ')'



simple_expression:

integer_or_var | simple_expression '+' simple_expression

| simple_expression '-' simple_expression

| simple_expression '*' simple_expression

| '(' simple_expression ')'



range_offset: /* empty */

| T_START T_AT range_expression



CR:653743
CR Number:   653743
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 3270 06 Jan 2011 Fixed
Description
The Import wizard would have reported an internal error when importing a shapefile if no spatial reference system was selected. This has been fixed.



CR:653884
CR Number:   653884
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3272 06 Jan 2011 Fixed
12.0.0 2629 06 Jan 2011 Fixed
Description
The Mobilink Server would have logged the error "Light weight poll request failed" after every poll attempt from an Ultralite client (through the use of the ML_GET_SERVER_NOTIFICATION function), even if the polls were actually successful. This has been fixed



CR:653929
CR Number:   653929
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)
11.0.1 2543 07 Jan 2011 Fixed
Description
The Interactive SQL utility ignoring the setting of the "Automatically refetch results" option and assumed it was on. This has been fixed.



CR:653930
CR Number:   653930
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3272 07 Jan 2011 Fixed
12.0.0 2630 07 Jan 2011 Fixed
11.0.1 2543 07 Jan 2011 Fixed
10.0.1 4167 07 Jan 2011 Fixed
Description
The Console utility could have stopped refreshing database and/or server properties after changing the set of properties which were displayed, even after it was restarted. The problem was sensitive to the speed with which properties were selected or unselected. This has been fixed.



CR:654078
CR Number:   654078
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 3150 07 Jan 2011 Fixed
12.0.0 2630 07 Jan 2011 Fixed
Description
While running a VALIDATE DATABASE statement, the server could have erroneously reported assertion failures indicating checksum failures or other errors that would indicate database corruption. The problem could only have occurred if the database file was being actively extended at the same time as the validation was being performed, and even in those circumstances the problem would have occurred only very rarely. The database was not actually corrupt and would have been valid when restarted. This has now been fixed.



CR:654244
CR Number:   654244
Product Name:   MobiLink
Product Component:   RelayServer plug-in for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3273 10 Jan 2011 Fixed
Description
On some Chinese Windows systems, the fields for entering the MAC address for back end servers was too narrow to see both digits of each byte of the address. This has been fixed.



CR:654249
CR Number:   654249
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 3273 10 Jan 2011 Fixed
12.0.0 2631 10 Jan 2011 Fixed
Description
The External Environments folder was erroneously including an entry for dbmlsync. This has been fixed.



CR:654253
CR Number:   654253
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 3274 11 Jan 2011 Fixed
12.0.0 2632 11 Jan 2011 Fixed
11.0.1 2545 11 Jan 2011 Fixed
10.0.1 4169 11 Jan 2011 Fixed
Description
In versions of the Interactive SQL utility 10.0.0 and later, using an ISQL parameter for the value of an option in a SET OPTION statement did not work because the parameter was not substituted correctly. This has been fixed.



CR:654259
CR Number:   654259
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3273 10 Jan 2011 Fixed
12.0.0 2631 10 Jan 2011 Fixed
11.0.1 2544 10 Jan 2011 Fixed
10.0.1 4168 10 Jan 2011 Fixed
Description
The changes for Engineering case 650489 may have caused execution remote procedure calls to an ASE remote server to fail with a strange "unchained transaction mode" error. This problem has now been fixed.



CR:654282
CR Number:   654282
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 3149 24 Feb 2011 Fixed
12.0.0 2632 25 Feb 2011 Fixed
Description
On the Format page of the the Options->Editor dialog, when selecting "Custom" from the Foreground or Background drop downs, the custom color selection dialog would have appeared with a color menu over top of it. This has been fixed so that the menu now closes before the color selection dialog opens.



CR:654284
CR Number:   654284
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 3273 11 Jan 2011 Fixed
12.0.0 2631 11 Jan 2011 Fixed
11.0.1 2544 11 Jan 2011 Fixed
10.0.1 4168 11 Jan 2011 Fixed
Description
The server could have crashed if the STOP SERVER or STOP ENGINE statement was called from an event or HTTP connection. This has been fixed.



Note that the 'STOP SERVER' syntax is new to version 12 (older servers support 'STOP ENGINE').



CR:654294
CR Number:   654294
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 3279 11 Jan 2011 Fixed
12.0.0 2637 11 Jan 2011 Fixed
Description
When canceling a query involving spatial operations, there was a small probability the server could have crashed, or failed to release resources. This has been fixed.



CR:654425
CR Number:   654425
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3274 11 Jan 2011 Fixed
12.0.0 2631 11 Jan 2011 Fixed
Description
In the Options window, the components for editing the quitting time were enabled even if the "Quitting time" checkbox was not checked. Now, the components are disabled when the checkbox is not checked.



CR:654434
CR Number:   654434
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3149 12 Jan 2011 Fixed
12.0.0 2631 12 Jan 2011 Fixed
11.0.1 2545 12 Jan 2011 Fixed
11.0.0 1618 12 Jan 2011 Fixed
10.0.1 4169 12 Jan 2011 Failed
Description
When sorting the plug-in names in the Plug-in dialog, an exception would have been thrown if a plug-in was first reloaded. This has been fixed.



CR:654446
CR Number:   654446
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3276 17 Jan 2011 Fixed
12.0.0 2633 17 Jan 2011 Fixed
11.0.1 2547 17 Jan 2011 Fixed
10.0.1 4171 17 Jan 2011 Fixed
Description
If there were multiple applications running simultaneously, the ADO.NET provider could have failed to load dbdata.dll. This has now been fixed.



CR:654635
CR Number:   654635
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 3274 13 Jan 2011 Fixed
12.0.0 2632 13 Jan 2011 Fixed
Description
If HTMLHelp documentation for SQL Anywhere was installed, it was possible for the Index Consultant to open DCX help under some circumstances. This has been fixed.



CR:654636
CR Number:   654636
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 3274 13 Jan 2011 Fixed
12.0.0 2632 13 Jan 2011 Fixed
Description
Opening a .saplan file in the "Plan Viewer" window and clicking the "Print" button did not do anything. This has been corrected so that it prints the plan. There was no problem printing plans which were generated by clicking the "Get Plan" button.



CR:654648
CR Number:   654648
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3275 13 Jan 2011 Fixed
12.0.0 2632 13 Jan 2011 Fixed
11.0.1 2546 13 Jan 2011 Fixed
Description
The substr() function was permitting LONG VARCHAR values to be used as the first argument to the function. This has been corrected



CR:654684
CR Number:   654684
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3275 13 Jan 2011 Fixed
12.0.0 2632 13 Jan 2011 Fixed
11.0.1 2546 13 Jan 2011 Fixed
Description
References to derived table columns may have been incorrect when temporary tables were present and the derived table was used to load the temporary table. This has been corrected.



CR:654759
CR Number:   654759
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3275 13 Jan 2011 Fixed
12.0.0 2632 13 Jan 2011 Fixed
Description
Changes to the members list were not saved when the OK button in the property sheet for a destination alias. Also, the Apply button was not enabled after a member was added, removed, or edited. Both of these problems have now been fixed.



CR:654790
CR Number:   654790
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 3275 14 Jan 2011 Fixed
12.0.0 2633 17 Jan 2011 Fixed
11.0.1 2546 14 Jan 2011 Fixed
10.0.1 4170 14 Jan 2011 Fixed
9.0.2 3999 14 Jan 2011 Fixed
Description
In very rare cases, the server may have crashed with a floating point exception when slightly loaded. This has been fixed.



CR:654801
CR Number:   654801
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 3285 03 Feb 2011 Fixed
12.0.0 2643 08 Feb 2011 Fixed
11.0.1 2558 08 Feb 2011 Fixed
Description
The SQL Anywhere Optimizer may have incorrectly pruned, without costing, optimal plans during query optimization. This has been fixed. This incorrect pruning would most probably have affected the final execution plans for complex, but inexpensive (i.e., the optimal plan has a small runtime) queries.



CR:654938
CR Number:   654938
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 3278 18 Jan 2011 Fixed
12.0.0 2635 18 Jan 2011 Fixed
11.0.1 2550 18 Jan 2011 Fixed
10.0.1 4173 18 Jan 2011 Fixed
Description
In rare cases, a corrupt TCP packet could have caused the server to crash. The server now validates the packet header before do anything with the packet. If it is corrupt, the packet is dropped.



CR:654952
CR Number:   654952
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)
16.0.0 1724 19 Jan 2011 Fixed
12.0.1 4007 06 Nov 2013 Fixed
11.0.1 2548 06 Nov 2013 Fixed
Description
Under rare circumstances, the server could have hung when SUBSCRIBE BY values were being changed for an article while large numbers of connections were updating tables in the database. This has now been fixed. A workaround is to avoid changing SUBSCRIBE BY values simultaneously with connections performing INSERT, UPDATE or DELETE operations.



CR:654981
CR Number:   654981
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3275 17 Jan 2011 Fixed
12.0.0 2633 17 Jan 2011 Fixed
11.0.1 2546 17 Jan 2011 Fixed
10.0.1 4170 17 Jan 2011 Fixed
Description
The Console utility could have stopped refreshing connection properties after changing the set of properties which were displayed, even after restarting DBConsole. This has been fixed.



CR:655157
CR Number:   655157
Product Name:   SQL Remote for SQL Anywhere
Product Component:   SQL Remote for Adaptive Server Anywhere
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3276 17 Jan 2011 Fixed
12.0.0 2634 17 Jan 2011 Fixed
11.0.1 2547 17 Jan 2011 Fixed
10.0.1 4171 17 Jan 2011 Fixed
Description
If there were any missing messages, SQL Remote would have asked for a resend after it had reached its receive polls given by the -rp option. This resend logic could have caused the publisher to re-scan the transaction log(s) and slow down replicating new transactions, especially on heavy load databases. This has been changed so that when a message in a multi-part message series (SQL Remote will generate multiple messages for a single transaction to form a multi-part message when the transaction is too big to fit in a single message) is missing, SQL Remote will not immediately ask for a resend, if the received messages are not followed by any messages that contain a commit or any messages that belong to another multi-part message series. This new logic will help users who

need to shut down or kill SQL Remote when it is sending multi-part messages to its subscribers.



CR:655351
CR Number:   655351
Product Name:   SQL Remote for SQL Anywhere
Product Component:   SQL Remote for Adaptive Server Anywhere
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3277 18 Jan 2011 Fixed
12.0.0 2634 18 Jan 2011 Fixed
Description
Temporary files created by SQL Remote and Log Translation utility may not have been deleted. This problem has been fixed.



CR:655358
CR Number:   655358
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2551 21 Jan 2011 Fixed
10.0.1 4173 21 Jan 2011 Fixed
Description
During the loading of data using the UltraLite Load XML to Database utility (ulload), columns whose values were NULL may have been set to default values. This has been fixed.



CR:655524
CR Number:   655524
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 3360 25 May 2011 Fixed
12.0.0 2688 25 May 2011 Fixed
11.0.1 2612 25 May 2011 Fixed
Description
A MERGE statement on a table that had a column with DEFAULT AUTOINCREMENT would have increased the autoincrement value for every matching row independently of whether the value had already been used for an INSERT or not. This behaviour has been improved so that the server only generates a new autoincrement value if the matching branch is an INSERT and the value will be used.



CR:655533
CR Number:   655533
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 3277 21 Jan 2011 Fixed
12.0.0 2635 21 Jan 2011 Fixed
Description
Under rare circumstances, inserting the result from the Round Earth linestring() function, or using the linestring() function in a query, could have crashed the server, if the line string crossed the equator. This has been fixed.



CR:655544
CR Number:   655544
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 3277 20 Jan 2011 Fixed
12.0.0 2635 20 Jan 2011 Fixed
Description
The 'Next' button and the 'Create' button were disabled in the Add Resource page when an invalid time was entered. This has been fixed.



CR:655570
CR Number:   655570
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 3277 20 Jan 2011 Fixed
12.0.0 2635 20 Jan 2011 Fixed
Description
The tab order on the Edit Configuration:Maintenance tab was not correct.. This has been fixed.



CR:655573
CR Number:   655573
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 3150 04 Feb 2011 Fixed
Description
The integrated Outbound Enabler could have crashed Mobilink, if in a Relay Server farm environment, one of the Relay Servers in the farm was down. This has been fixed.



CR:655574
CR Number:   655574
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 3284 04 Feb 2011 Fixed
12.0.0 2641 04 Feb 2011 Fixed
Description
The integrated Outbound Enabler library was not being unloaded correctly when the Mobilink server shutdown. The library eventually unloaded when the MobiLink server executable exited and no bad side effects where observed as a result, but this condition is now fixed.



CR:655599
CR Number:   655599
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 3277 20 Jan 2011 Fixed
12.0.0 2635 20 Jan 2011 Fixed
Description
It was not possible to drag and drop the second operators in the Add Resource page. This has been fixed.



CR:655607
CR Number:   655607
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 3277 21 Jan 2011 Fixed
12.0.0 2635 21 Jan 2011 Fixed
11.0.1 2549 21 Jan 2011 Fixed
Description
The text in the Favorites sidebar could have disappeared if the mouse was moved over it. This has been fixed.



CR:655749
CR Number:   655749
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 3279 03 Feb 2011 Fixed
12.0.0 2637 03 Feb 2011 Fixed
11.0.1 2552 03 Feb 2011 Fixed
10.0.1 4174 03 Feb 2011 Fixed
Description
Execution of an INSERT ... ON EXISTING SKIP statement did not report the correct number of inserted and updated rows using @@rowcount and sqlcount. This has been fixed



CR:655780
CR Number:   655780
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)
12.0.1 3277 24 Jan 2011 Fixed
12.0.0 2635 24 Jan 2011 Fixed
10.0.1 4173 24 Jan 2011 Fixed
11.0.1 2635 24 Jan 2011 Fixed
Description
The method MLResultSet.getBigDecimal(L/java/lang/String;) unnecessarily threw a 'method not supported' exception. This has been fixed.



CR:655810
CR Number:   655810
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 3105 21 Jan 2011 Fixed
12.0.0 2636 21 Jan 2011 Fixed
Description
The MobiLink client was not freeing some memory when it shrank its cache. This would have caused its memory usage to increase over time. This memory leak has now been fixed.



CR:655880
CR Number:   655880
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Open
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3278 24 Jan 2011 Fixed
12.0.0 2636 24 Jan 2011 Fixed
11.0.1 2551 24 Jan 2011 Fixed
Description
Second and subsequent '%' characters were not being handled properly in LIKE clauses. This was corrected.



CR:655939
CR Number:   655939
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 3105 21 Jan 2011 Fixed
12.0.0 2636 21 Jan 2011 Fixed
Description
The MobiLink client may have crashed while attempting to grow its dynamic cache if a memory allocation failed. This has been fixed.



CR:655945
CR Number:   655945
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3278 01 Feb 2011 Fixed
12.0.0 2636 01 Feb 2011 Fixed
Description
On the database Fragmentation tab, the shortcuts for Zoom In (Ctrl++) and Zoom Out (Ctrl+-) did not work with the numeric keypad. This has been fixed.



CR:655953
CR Number:   655953
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3278 24 Jan 2011 Fixed
12.0.0 2636 24 Jan 2011 Fixed
11.0.1 2551 24 Jan 2011 Fixed
Description
Several memory leaks have been fixed in the MobiLink client. These leaks would primarily affect applications using the dbmlsync API.



CR:655955
CR Number:   655955
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 3278 24 Jan 2011 Fixed
12.0.0 2636 24 Jan 2011 Fixed
Description
Several memory leaks have been fixed in the MobiLink Client.



CR:655956
CR Number:   655956
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2559 07 Feb 2011 Fixed
10.0.1 4180 07 Feb 2011 Fixed
Description
If a server was handling a large number of requests, and a large number of those requests made external environment calls that resulted in server side calls coming back into the server and those server side calls were similar in nature, then there was a chance that the server would have crashed when one or more of the connections making external environment calls closed. This problem has now been fixed.



CR:655969
CR Number:   655969
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3152 24 Jan 2011 Fixed
12.0.0 3278 24 Jan 2011 Fixed
Description
Accessing values of LONG BINARY STORE AS FILE on BlackBerry devices would have failed if the filename started with "file://", but was not all lowercase. This has been fixed. The string "file://" is now case insensitive as it should be.



Note that the root value is case sensitive (i.e. "FiLe:///SDCard/me.blob" is ok but "FiLe:///sdcard/me.blob" is not).



CR:655972
CR Number:   655972
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3278 21 Jan 2011 Fixed
12.0.0 2636 21 Jan 2011 Fixed
11.0.1 2551 21 Jan 2011 Fixed
10.0.1 4173 21 Jan 2011 Fixed
Description
The fix for Engineering case 636018 missed a case, which has now been corrected.



Description of case 636018:

Queries involving indexes containing long values could have returned incorrect results. Index corruption was possible, but not likely..



CR:655981
CR Number:   655981
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3281 27 Jan 2011 Fixed
12.0.0 2638 27 Jan 2011 Fixed
11.0.1 2554 27 Jan 2011 Fixed
10.0.1 4176 27 Jan 2011 Fixed
Description
Values for the ApproximateCPUTime property is never expected to decrease between calls, as it represents an estimate of accumulated CPU time for a connection. However, for connections that had accumulated approximately 1000 seconds of CPU time, the counter could have periodically receded by approximately 400 seconds.



CR:655987
CR Number:   655987
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3338 24 Jan 2011 Fixed
12.0.0 2675 24 Jan 2011 Fixed
Description
The "Apply" button on the property sheet for a Remote Task was not enabled when various changes were made. Now, the button is enabled correctly.



CR:655989
CR Number:   655989
Product Name:   MobiLink
Product Component:   RelayServer plug-in for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3278 24 Jan 2011 Fixed
12.0.0 2637 24 Jan 2011 Fixed
Description
Sybase Central would have crashed whenu attempting to open a Relay Server configuration file which was zero-length, or that contained only whitespace. This has been fixed.



CR:656087
CR Number:   656087
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3279 24 Jan 2011 Fixed
12.0.0 2637 24 Jan 2011 Fixed
Description
When connecting from Sybase Central to an UltraLite database with multi-byte characters in its file name, the database name would have appeared with mangled characters. This has been fixed.



CR:656093
CR Number:   656093
Product Name:   SQL Remote for SQL Anywhere
Product Component:   SQL Remote for Adaptive Server Anywhere
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3278 24 Jan 2011 Fixed
12.0.0 2636 24 Jan 2011 Fixed
Description
The Log Translation utility (dbtran) and SQL Remote could left temporary files undeleted after execution. This has been fixed.



CR:656162
CR Number:   656162
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Windows CE 2.11
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2553 26 Jan 2011 Fixed
Description
When building a CAB file to deploy SQL Anywhere for Windows Mobile, a start menu folder "sqlany12" would have been created, the folder name should have been "sqlany11". This has been corrected.



CR:656264
CR Number:   656264
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 3283 01 Feb 2011 Fixed
12.0.0 2640 01 Feb 2011 Fixed
11.0.1 2556 01 Feb 2011 Fixed
Description
When connected to a database that had the same character set as the OS, and a query like the following was executed:

SELECT ... FROM dirtab WHERE file_name = '...'



where dirtab was a directory access table and the file_name string literal contained non-ASCII characters, there was a chance the server would have crashed. This problem has now been fixed.



CR:656272
CR Number:   656272
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3279 25 Jan 2011 Fixed
12.0.0 2637 25 Jan 2011 Fixed
11.0.1 2552 25 Jan 2011 Fixed
10.0.1 4174 25 Jan 2011 Fixed
Description
The INSERT ON EXISTING SKIP statement did not report the correct number of inserted and

updated rows using @@rowcount and sqlcount. This has now been corrected.



CR:656291
CR Number:   656291
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3280 25 Jan 2011 Fixed
12.0.0 2637 25 Jan 2011 Fixed
Description
If a Destination Alias defined in a Server Store was deleted, the alias was still shown in Sybase Central until the QAnywhere server completed the deletion. That could have taken up to a minute, or could never have happened if the QAnywhere server was not running. If deleting the alias was tried a second time, an obscure error message would have been displayed saying that the alias could not be deleted. Now, the Destination Alias is removed from Sybase Central as soon as the user deletes it, the same as in earlier versions of Sybase Central.



CR:656454
CR Number:   656454
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3279 26 Jan 2011 Fixed
12.0.0 2638 26 Jan 2011 Fixed
Description
When connected to a database that contained one or more publications, and the property sheet for a Publication was opened and an Article was selected in the "Subscribe by restriction" tab, the Editor pane at the bottom of the tab would have been disabled except when the 'expression' radio button was checked. When the Editor pane was disabled it was still possible to right click on it to reveal a pop-up menu that allowed for search and replace in the box. The menu is now disabled when the Edit pane is disabled.



CR:656481
CR Number:   656481
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3280 26 Jan 2011 Fixed
12.0.0 2637 26 Jan 2011 Fixed
11.0.1 2553 26 Jan 2011 Fixed
10.0.1 4175 26 Jan 2011 Fixed
Description
An application using the ADO .Net provider, and calling the method SAConnection(), could not have successfully connected to an IQ 12.7 server. A run-time error (iAnywhere.Data.SQLAnywhere.SAException) would have occurred when the provider tried to parse the server version string. This problem has been resolved.



CR:656645
CR Number:   656645
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 3281 27 Jan 2011 Fixed
12.0.0 2638 27 Jan 2011 Fixed
Description
Dates shown in the Graph widget were localized but not in the correct order (they showed "MM DD" instead of "DD MM"). This has been fixed.



CR:656650
CR Number:   656650
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 3281 27 Jan 2011 Fixed
12.0.0 2638 27 Jan 2011 Fixed
11.0.1 2554 27 Jan 2011 Fixed
Description
The system procedure sa_db_list() did not validate its database id parameter if the value was a positive integer. This would have resulted in a single row result set containing the value provided. Now, if the value is not a valid database id, the procedure will return an empty result set.



CR:656660
CR Number:   656660
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 3281 31 Jan 2011 Fixed
12.0.0 2638 31 Jan 2011 Fixed
Description
During a Relay Server outage, the SQL Anywhere Monitor did not display the the "Unavailable since" time, but cleared the "Up since" time only. A farm outage alert was also not raised. Only a sustained outage alert was raised after the threshold time elapsed. When the Relay Server came back up again, data collection did not resume and the "Up since" time was not updated. These problems have now been fixed.



CR:656671
CR Number:   656671
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)
31 Jan 2011 Fixed
Description
MobiLink does not allow column-based conflict detection for tables that have large (eg. BLOB) columns, but that option could have been selected for such a table in a Synchronization Model in the Table Mapping editor. An error would not have been reported until synchronizing after deploying the model. This has been fixed so that a table mapping error will now occur in the Table Mapping editor.



CR:656680
CR Number:   656680
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 3303 16 Mar 2011 Fixed
12.0.0 2658 16 Mar 2011 Fixed
11.0.1 2575 16 Mar 2011 Fixed
Description
The Interactive SQL utility could have become unresponsive when executing a statement which returned a result set if the entire result set cannot be returned due to a row lock. This has been fixed.



CR:656691
CR Number:   656691
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 3284 07 Feb 2011 Fixed
12.0.0 2642 07 Feb 2011 Fixed
Description
If a query was rewritten by the optimizer to use a materialized view, the query would incorrectly have returned zero rows if a spatial predicate was applied to the rows originating from the view. This has been fixed.



CR:656716
CR Number:   656716
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3283 03 Feb 2011 Fixed
12.0.0 2641 03 Feb 2011 Fixed
11.0.1 2557 03 Feb 2011 Fixed
Description
The Relay Server could have leaked heap memory under the following conditions:

- On the response to the first HTTP request in the session, or specifically, anytime a cookie was set, if the response was long and came in small packets.

- A small number of bytes were leaked on Upchannel and Dnchannel creation.



This has been fixed.



CR:656828
CR Number:   656828
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 3283 03 Feb 2011 Fixed
12.0.0 2641 03 Feb 2011 Fixed
Description
Adding the CHECK IMMEDIATE REFRESH clause to a CREATE MATERIALIZE VIEW statement would have caused the server to crash. This has been fixed.



CR:656839
CR Number:   656839
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 3282 31 Jan 2011 Fixed
12.0.0 2640 31 Jan 2011 Fixed
Description
If an INSERT or UPDATE statement affecting the value of a spatial column was canceled, or a run-time error was encountered during execution, there was a possibility that the server would have failed assertion 112701: "Failed to convert geometry to EWKB for the redo log -- transaction rolled back [-301] ['40W01']". This has been fixed.



CR:656844
CR Number:   656844
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3281 31 Jan 2011 Fixed
12.0.0 2639 31 Jan 2011 Fixed
Description
ULPod may have caused AvantGo clients to crash when calling the method TableAGDBSet getTableAGDBSet. This has been fixed.



CR:656847
CR Number:   656847
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 3282 01 Feb 2011 Fixed
12.0.0 2640 01 Feb 2011 Fixed
11.0.1 2555 01 Feb 2011 Fixed
Description
If a derived table was joined with the rest of the query using a Join Nested Loops operator, the performance of the query may have suffered when the derived table had to be computed many times due to many rows generated by the left hand side of the Join Nested Loops. The optimizer was choosing such a plan if the estimated number of rows of the left hand side was very small. If this estimation was wrong (e.g., the optimizer estimates one row for the left hand side but in reality the left hand side produces 1,000 rows), the derived table was computed many, many times during execution. This has been fixed so that the optimizer considers only Join Hash or Join Sort Merge operators for the derived tables if it is correct to do so.



CR:656863
CR Number:   656863
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3281 01 Feb 2011 Fixed
12.0.0 2639 01 Feb 2011 Fixed
Description
If a synchronization model had script errors that were fixed without opening the Events editor or saving the model, attempting to deploy the model would have erroneously failed because of a script error. This has been fixed.



CR:656897
CR Number:   656897
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 3281 31 Jan 2011 Fixed
12.0.0 2639 31 Jan 2011 Fixed
11.0.1 2554 31 Jan 2011 Fixed
Description
Attempting to execute a SQL statement that was made up only of full-width space characters (U+3000, the "Ideographic Space") would have caused the Interactive SQL utility to crash. This has been fixed.



CR:656998
CR Number:   656998
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)
12.0.1 3290 31 Jan 2011 Fixed
11.0.1 2563 04 Feb 2011 Fixed
9.0.2 4004 04 Feb 2011 Fixed
Description
Remote queries with many aliases in grouped derived tables may have taken a long time to execute. This has been fixed.



CR:657026
CR Number:   657026
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 3282 01 Feb 2011 Fixed
12.0.0 2640 01 Feb 2011 Fixed
11.0.1 2555 01 Feb 2011 Fixed
Description
The MobiLInk server would immediately refuse to startup, if it could not make any connections to the consolidated database, even when it was running as a Windows service.

This behaviour has changed so that the MobiLink server will retry to make connections, when it is running as a Windows services. The retries are once a minutes for ten minutes. If it still cannot make a connection after that, it will refuse to startup.



CR:657068
CR Number:   657068
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3284 07 Feb 2011 Fixed
12.0.0 2642 07 Feb 2011 Fixed
11.0.1 2558 07 Feb 2011 Fixed
Description
In the MobiLink Server Log File Viewer, selecting a synchronization could have resulted in the window becoming unresponsive if the synchronization contained hundreds of thousands of messages. This has been fixed.



Also, it was noticed that synchronizations were not initially listed in chronological order if the log file contained output for more than one run of the MobiLink Server. This has also been fixed.



CR:657185
CR Number:   657185
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3099 01 Feb 2011 Fixed
Description
The MobiLink Agent for central administration of remote databases now supports a file delete command that does not fail if the file to be deleted does not exist. The existing behaviour of failing if the file to be deleted does not exist is the default.



CR:657198
CR Number:   657198
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3043 01 Feb 2011 Fixed
Description
The MobiLink Replay utility (mlreplay) and mlgenreplayapi tool now log any command line options in the log. If any of the command line options are passwords, then the passwords will be replaced with a string of *.



CR:657199
CR Number:   657199
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3045 01 Feb 2011 Fixed
Description
The os <size> command line option can be used to limit the maximum size of a log file produced by the MobiLink Replay utility (mlreplay) or the mlgenreplayapi tool. When the log reaches the specified size (minimum 10 KB), it will be renamed to YYMMDDxx.rlg and a new log file is started with the original name.



CR:657200
CR Number:   657200
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3055 01 Feb 2011 Fixed
Description
The MobiLink Agent for central administration of remote databases now supports two new variables for task conditions, {is_online} and {network_conn_name}.



The variable {is_online} can be used to check whether the client device is connected to a network on which the MobiLink server of the agent can be reached. Note that this variable is not equivalent to a ping of the MobiLink host machine, nor of the MobiLink server itself. The host machine may be offline and the variable will still evaluate to 1 (true). This variable evaluates to 1 if and only if the client device is connected to a network such that there is a route to the IP address of the MobiLink server. This variable is supported for agents running on Windows and Windows Mobile operating systems.



The variable {network_conn_name} evaluates to the name of the network connection that will be used by the agent for communication with its MobiLink server. This variable is only supported on Windows operating systems. The list of possible network connection names for a given Windows-based device can be obtained by going to Control Panel/Network Connections on Windows XP, or going to Control Panel/Network and Sharing Center on Windows Vista and Windows 7. Alternatively, the list of network connection names can be obtained from the information returned by the ipconfig command line utility. The network connection name for the loopback connection (destination IP address 127.0.0.1) is "Loopback interface". If there is no network connection that can be used by the agent to communicate to the MobiLink server, this variable evaluates to "?".



CR:657201
CR Number:   657201
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3046 01 Feb 2011 Fixed
Description
The MobiLink Replay utility command line options n <number of simulated clients> and sci <simulated client information file> can now be used together as long as the number of simulated clients specified by the n option is less than or equal to the number of simulated clients in the simulated client information file. If the sci and n options are used together, the number of simulated clients mlreplay will run will be the number specified by n. Allowing these two options to be used together allows one simulated client information file specifying x simulated clients to be used to replay recorded protocol with 1 to x simulated clients, where as before, it could only be used to replay recorded protocol with exactly x simulated clients.



CR:657203
CR Number:   657203
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3055 01 Feb 2011 Fixed
Description
The MobiLink Agent for central administration of remote databases now supports a random delay for task execution. The motivation for this feature is to address scalability issues in a large deployment of centrally administered remote databases. If a given task sends results to the MobiLink server after execution, or causes a remote database to synchronize with the server, and it is triggered simultaneously across a large number of remotes, then setting a random delay for the task will uniformly distribute the synchronization workload for the server over a configurable period of time.



A remote task can have a "random delay interval", which is an interval N, in seconds, with which each agent generates a random number of seconds in [0, N) to delay each task execution. If the task is a scheduled task, the random delay is generated before the first task execution, and used for each execution. The task is executed at the scheduled times offset by the random delay. This ensures that the deltas of the task execution times are consistent with the schedule. It is not recommended that the random delay interval be larger than smallest delta time of a scheduled task. If the task is an "on demand" task, that is initiated by the server, the random delay is generated and used to delay the execution each time the task is initiated. If the task is a "run on receipt" task, the random delay is generated and used to delay the execution at the first and only time the task is executed.



CR:657204
CR Number:   657204
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 3050 01 Feb 2011 Fixed
Description
A new option has been added to control interpolation of ST_CircularString geometries called st_geometry_interpolation. It takes a set of key=value pairs as: key1=value1;key2=value2;....



Valid keys include:

relative-tolerance-percent=<double>

absolute-tolerance=<double>



The value for relative-tolerance-percent specifies the maximum variation (in percent) in the distance from the centre point of the ST_CircularString segment to the interpolated ST_LineString segment, relative to the radius of the ST_CircularString segment. This value defaults to 0.3, which gives 40 points in a complete circle. Its minimum value is 0, meaning the absolute-tolerance setting is always used.



The value for absolute-tolerance specifies the maximum absolute variation (in linear units) in the distance from the centre point of the ST_CircularString segment to the interpolated ST_LineString segment. This value defaults to the tolerance specified by the SRID. Its minimum value is also the tolerance specified by the SRID.



If neither key is specified, the defaults are used. If only one key is specified, the other one is set to its minimum value. If both keys are specified, the minimum number of points will be produced such that both restrictions are satisfied.



Regardless of the setting, there will be at least 3 points per curve segment. Additional points may be added to ensure the ST_Envelope of the ST_LineString is the same as that of the original ST_CircularString. Furthermore, no two consecutive points on the interpolated ST_LineString will be within tolerance of each other.





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

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

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

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

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

各种误操作:

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

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

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


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

Sybase ASE数据库恢复工具READSYBDEVICE:

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

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

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

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

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


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

SQL Server数据库恢复工具SQLRescue:

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

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

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

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

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

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

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