提供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:632362
CR Number:   632362
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2445 15 Jun 2010 Fixed
11.0.1 2450 15 Jun 2010 Fixed
10.0.1 4084 15 Jun 2010 Fixed
Description
If a connection set the dedicated_task option to 'On', then there was a chance a request for this connection would have hung. This was more likely for connections where many requests are sent one after the other. This has been fixed.



CR:632401
CR Number:   632401
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2545 15 Jun 2010 Fixed
12.0.1 2944 20 Sep 2010 Fixed
Description
The SQL Anywhere JDBC driver has provided support for PreparedStatement.setBlob(), ResultSet.getBlob() and ResultSet.getClob() for some time now; but support for PreparedStatement.setClob() was not available in the SQL Anywhere JDBC driver until now. The SQL Anywhere JDBC driver now supports two of the three PreparedStatement.setClob() methods. They are:



PreparedStatement.setClob( int parameterIndex, Clob x ), and

PreparedStatement.setClob( int parameterIndex, Reader reader, long length )



However, support for the method:



PreparedStatement.setClob( int parameterIndex, Reader reader )



is still not available in the SQL Anywhere JDBC driver.



It should be noted that when using the PreparedStatement.setClob( int parameterIndex, Clob x ) overload, the user supplied Clob implementation only needs to support the Clob.length() and Clob.getCharacterStream() methods. Also, for large strings and large character streams, the new PreparedStatement.setClob() methods within the SQL Anywhere JDBC driver are preferable over the PreparedStatement.setString() and PreparedStatement.setCharacterStream() methods in terms of both performance and memory usage.



CR:632413
CR Number:   632413
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.0 2545 17 Jun 2010 Fixed
11.0.1 2452 17 Jun 2010 Fixed
12.0.1 2946 20 Sep 2010 Fixed
Description
On Vista and later versions of Windows, the Windows Performance Monitor utility (perfmon) could not have monitored a database server which was running as a Windows service. This problem has been fixed.



CR:632417
CR Number:   632417
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.0 2545 15 Jun 2010 Fixed
11.0.1 2451 15 Jun 2010 Fixed
12.0.1 2944 20 Sep 2010 Fixed
Description
If a Java or CLR external environment had been started, and an application then attempted to execute an "alter database upgrade" command, or if the Upgrade utility (dbupgrad) was run, then the upgrade would have failed due to the fact that the database was still in use by the external environment(s). This problem has now been fixed and the external environments will now be shut down provided they are idle at the time the database upgrade is attempted.



CR:632434
CR Number:   632434
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2451 23 Jun 2010 Fixed
Description
Version 11.x of the Relay Server is not compatible with version 7 of Microsoft's Internet Information Server (IIS7). The Relay Server has now been updated to support IIS7. New IIS7 set up instructions will be available in %sqlany11%\MobiLink\RelayServer\IIS\iis7_setup.txt.



CR:632435
CR Number:   632435
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.0 2545 16 Jun 2010 Fixed
12.0.1 2944 20 Sep 2010 Fixed
Description
When copying cells from a result set, a newline character was inadvertently added to the copied value, even if cells from a single row were copied. This newline has been removed in those cases.



CR:632436
CR Number:   632436
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.0 2545 16 Jun 2010 Fixed
12.0.1 2944 20 Sep 2010 Fixed
Description
The Tip of the Day which referred to the Connect Assistant has been removed. The Connect Assistant was removed in version 12.0.0.



CR:632438
CR Number:   632438
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.0 2545 16 Jun 2010 Fixed
11.0.1 2451 16 Jun 2010 Fixed
10.0.1 4085 16 Jun 2010 Fixed
12.0.1 2545 20 Sep 2010 Fixed
Description
When running the Unload utility to create a new database with the same settings (dbunload -ar), it may have immediately failed with the error "Too many connections to database being replaced". This would have been rare, and retrying the unload would likely have resulted in success. This has been fixed.



CR:632446
CR Number:   632446
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.0 2545 16 Jun 2010 Fixed
11.0.1 2451 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
The MobiLink server stream options set in the Deploy Synchronization Model wizard would not have been set in the batch file created to run the MobiLink server. This has been fixed. A workaround is to edit the generated batch file to add the stream options.



CR:632488
CR Number:   632488
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.0 2545 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
If the option Optimization_goal had the setting 'First-row', then validating a table would have been extremely slow, whether validating with the Validation utility, or with a VALIDATE statement. This has been fixed



A work-around is to set the optimization goal to 'All-rows' before validation.



CR:632516
CR Number:   632516
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.0 2545 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
The Remote Task wizard offered three unsupported options for the battery level condition: "Less than 25%", "Less than 50%" and "Less than 75%". These options have now been removed from the wizard.



CR:632519
CR Number:   632519
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2545 16 Jun 2010 Fixed
11.0.1 2451 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
Changes made to INOUT script parameters in .NET scripts were ignored unless the script accepted all the possible parameters for the event. This has been fixed.



CR:632526
CR Number:   632526
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.0 2545 16 Jun 2010 Fixed
11.0.1 2451 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
The Plan Viewer window could have opened with a width that was wider than the monitor if the "SQL Statements" field contained a SQL statement which was itself longer than could be displayed on the monitor. This has been fixed.



CR:632530
CR Number:   632530
Product Name:   UltraLiteJ
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2545 16 Jun 2010 Fixed
11.0.1 2451 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
The UltraLiteJ Database Unload utility (ULjUnload) would have output control characters (other than \t \r \n) or non-ASCII characters (>= \u007f) into its XML output without escaping them. This would have made the resulting XML file unreadable by many tools, including the UltraLite Load XML to Database utility (ulload). This has been fixed.



CR:632538
CR Number:   632538
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.0 2545 17 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
If an error window (or any other modal window) was open, it was impossible to close any Interactive SQL window, even if the error window was not owned by the Interactive SQL window that was attempting to be closed. This has been fixed.



CR:632545
CR Number:   632545
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.0 2545 17 Jun 2010 Fixed
11.0.1 2451 17 Jun 2010 Fixed
10.0.1 4085 17 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
Pressing a non-character key (e.g LeftArrow, Alt, Space, etc.) could have inserted a hollow box character to the SQL Statements field. This has been fixed.



This problem was more readily seen on Linux systems than on Windows.



CR:632608
CR Number:   632608
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.0 2545 17 Jun 2010 Fixed
11.0.1 2452 17 Jun 2010 Fixed
10.0.1 4085 17 Jun 2010 Fixed
12.0.1 2946 20 Sep 2010 Fixed
Description
The performance for fetching BLOB columns was much slower compared with the managed OLE DB provider. This problem has been corrected.



CR:632612
CR Number:   632612
Product Name:   MobiLink
Product Component:   iAS Branded ODBC Drivers
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2562 17 Jun 2010 Fixed
11.0.1 2473 17 Jun 2010 Fixed
10.0.1 4106 17 Jun 2010 Fixed
12.0.1 2946 20 Sep 2010 Fixed
Description
The iAnywhere ODBC driver for Oracle could have crashed, if an application made a request to convert an invalid SQL statement (for instance, a SQL statement containing a '{' that was not followed by 'call') to native SQL by calling SQLNativeSQLW. This has been fixed.



CR:632627
CR Number:   632627
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.0 2545 18 Jun 2010 Fixed
12.0.1 2946 20 Sep 2010 Fixed
Description
Database documentation that was generated from the SQL Anywhere plug-in for Sybase Central would not have shown scroll bars when viewed with the Safari browser. This has been fixed.



CR:632640
CR Number:   632640
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)
7.0.0 2545 18 Jun 2010 Fixed
Description
When deploying a Synchronization Model to an UltraLite database on Mac OS X systems, it would have failed with the error "Cannot create an UltraLite database because the ulinit utility can only be run on Windows and Linux." Mac OS X systems are supported, so this error is no longer raised, and the message has been updated to include Mac OS X as well.



CR:632732
CR Number:   632732
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.0 2545 18 Jun 2010 Fixed
12.0.1 2946 20 Sep 2010 Fixed
Description
On Unix systems, the Performance Statistics utility (dbstats) could not have monitored a database server that was running under a different user id. This has been fixed.



CR:632736
CR Number:   632736
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.0 2545 18 Jun 2010 Fixed
12.0.1 2947 20 Sep 2010 Fixed
Description
On Mac OS X systems, Sybase Central would have crashed when importing a configuration file and clicking the "Save" button. This has been fixed.



CR:632739
CR Number:   632739
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.0 2545 18 Jun 2010 Fixed
12.0.1 2947 20 Sep 2010 Fixed
Description
On Mac OS x systems, the "..." button in the result set table was several times wider than it should have been. This has been corrected.



CR:632743
CR Number:   632743
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2545 18 Jun 2010 Fixed
11.0.1 2453 18 Jun 2010 Fixed
10.0.1 4086 18 Jun 2010 Fixed
12.0.1 2947 20 Sep 2010 Fixed
Description
The text fields on the second page of the Index Consultant were too narrow to display even their default values. This problem was most apparent on Mac OS X systems, although it could also have occurred on any platform if the font used by the application was sufficiently large, or if the look-and-feel for that platform had a wide border for text fields. This has been fixed.



CR:632766
CR Number:   632766
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 2947 18 Jun 2010 Fixed
Description
The Table Mapping editor was missing a "Download Delete Subset" cascading menu, which meant it was not possible to set the download delete subset setting for multiple table mappings in a single operation. This has been fixed.



CR:632770
CR Number:   632770
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.0 2545 21 Jun 2010 Fixed
12.0.1 2947 20 Sep 2010 Fixed
Description
When deploying a configuration file to multiple servers, the window titled "Deploy Configuration" could have stayed open indefinitely with the last status line "Checking Relay Server configurations". This would have happened if the security token for any backend server was empty. This has now been fixed.



CR:632776
CR Number:   632776
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.0 2545 22 Jun 2010 Fixed
12.0.1 2947 20 Sep 2010 Fixed
Description
The descriptions for Relay Servers were always shown as empty in the "Deploy Configuration File" window, even if they were not empty. This has been fixed.



CR:632869
CR Number:   632869
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 22 Jun 2010 Fixed
11.0.1 2454 22 Jun 2010 Fixed
12.0.1 2950 20 Sep 2010 Fixed
Description
Using the -ppv command line option ("print periodic performance values") could have degraded the MobiLink server's performance if there were many unsubmitted error reports. This was most noticable when using -ppv 1, and there were more than one thousand unsubmitted reports. This has been fixed by removing the NUM_UNSUBMITTED_ERROR_RPTS value from the -ppv output. The number of unsubmitted error reports can still be found by using the SQLAnywhere Monitor for MobiLink, or by counting the lines output by "dbsupport -lc".



CR:632873
CR Number:   632873
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.0 2554 22 Jun 2010 Fixed
11.0.1 2468 22 Jun 2010 Fixed
12.0.1 2975 20 Sep 2010 Fixed
Description
Concurrent updates to an IMMEDIATE REFRESH text index may have corrupted the index. This has been fixed.



CR:632874
CR Number:   632874
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.0 2483 21 Jun 2010 Fixed
11.0.1 2454 21 Jun 2010 Fixed
Description
Under very rare circumstances, sequential scans of tables that had rows deleted within the past minute may have returned too few rows. Subsequent scans of the table would have returned the correct number of rows.



This has been fixed.



Note, this problem was extremely rare in builds prior to the changes made for Engineering case 625189, it would have been slightly more likely in later builds, due to increased frequency of cleaner invocation.



CR:632875
CR Number:   632875
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.0 2550 22 Jun 2010 Fixed
11.0.1 2461 22 Jun 2010 Fixed
10.0.1 4093 22 Jun 2010 Fixed
12.0.1 2965 20 Sep 2010 Fixed
Description
The server would have crashed if a client application attempted to connect while the

server was shutting down after failing to start. This has been fixed.



CR:632880
CR Number:   632880
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 2950 21 Jun 2010 Fixed
Description
On Mac OS X systems, the Add, Edit, Delete, Update and Cancel Row toolbar buttons were too small (16x16 rather than 32x32). This has been fixed.



CR:632889
CR Number:   632889
Product Name:   MobiLink
Product Component:   iAS Branded ODBC Drivers
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 22 Jun 2010 Fixed
11.0.1 2455 22 Jun 2010 Fixed
10.0.1 4087 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
When using the iAS Oracle ODBC Driver, a call to SQLGetStmtAttr that queried the SQL_ATTR_CONCURRENCY, SQL_ATTR_CURSOR_TYPE, SQL_ATTR_CURSOR_SENSITIVITY or SQL_ATTR_QUERY_TIMEOUT attributes could have returned a random value for the attribute. The driver now throws an "Optional feature not implemented" error (SQL State HYC00) for the SQL_ATTR_CONCURRENCY, SQL_ATTR_CURSOR_TYPE, and SQL_ATTR_CURSOR_SENSITIVITY attributes. When the SQL_ATTR_QUERY_TIMEOUT is queried, a zero is returned, and no error is reported.



CR:632893
CR Number:   632893
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.0 2546 21 Jun 2010 Fixed
12.0.1 2950 28 Sep 2010 Fixed
Description
The MobiLink replay utility could have crashed when concurrent connections to the MobiLink server were made on non-Windows systems. This has been fixed.



CR:632902
CR Number:   632902
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.0 2546 22 Jun 2010 Fixed
12.0.1 2950 20 Sep 2010 Fixed
Description
Attempting to add or update a row in a table by using a file to supply a column value, could have crashed Sybase Central (or silently failed with the Interactive SQL utility), if the file contents were larger than the database column could hold. This has been fixed.



CR:632984
CR Number:   632984
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.0 2546 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
Use of the -f (or --filedir) command line option on the UltraLite Unload Database utility (ulunload) would have mangled the specified directory. This would have prevented the utility from functioning properly, and generated an error similar to the following:

Error: Cannot open data file <mangled characters> for table T



This has now been fixed. A workaround is to store BLOB/CLOB data in the current directory.



CR:632988
CR Number:   632988
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.0 2546 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
It was possible for the MobiLink Server Log File Viewer to crash when selecting the "Messages" or "Summaries" tab for the first time. This crash would have happened only very rarely, and has now been fixed.



CR:633000
CR Number:   633000
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.0 2546 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
When editing a DECIMAL value, the editor could have truncated some of the least significant digits from the initial value. Now, those digits are preserved.



CR:633003
CR Number:   633003
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.0 2549 29 Jun 2010 Fixed
11.0.1 2458 29 Jun 2010 Fixed
12.0.1 2958 20 Sep 2010 Fixed
Description
Attempting to execute an UPDATE statement on a table with multiple indexes and lazy loading, could have failed in various ways by throwing Java exceptions. This was corrected



CR:633007
CR Number:   633007
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
The following English error message could have been logged in the MobiLink server log on a non-English system:

"Error canceling message. Cannot cancel a message that has already been downloaded to its recipient or is in a final state." This message has now been localized.



CR:633011
CR Number:   633011
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.0 2546 22 Jun 2010 Fixed
11.0.1 2455 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
The Login Mapping wizard's last page did not always display the current login_mode option setting correctly. This has been fixed.



CR:633015
CR Number:   633015
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.0 2546 22 Jun 2010 Fixed
11.0.1 2455 22 Jun 2010 Fixed
10.0.1 4087 22 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
If an application called a Java external environment procedure that returned result sets, then those result sets would not have been cleaned up for a long time after the application was done with them. The result sets now get cleaned up in a more timely fashion.



CR:633019
CR Number:   633019
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.0 2553 22 Jun 2010 Fixed
12.0.1 2972 20 Sep 2010 Fixed
Description
It was not possible to edit BIT values in the "Results" panel. This has been fixed.



CR:633021
CR Number:   633021
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2455 24 Jun 2010 Fixed
10.0.1 4087 24 Jun 2010 Fixed
Description
When using the external system procedure xp_startsmtp, if the SMTP authentication failed the server would not have closed the TCP connection to the SMTP server. This has been fixed.



CR:633031
CR Number:   633031
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   6.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 23 Jun 2010 Fixed
11.0.1 2455 23 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
Sybase Central could have silently crashed on startup if an OEM.INI file was installed which contained an entry before a section header. This has been fixed; the entry is now ignored.



Note, this problem also affected the Interactive SQL and Console utilities, as well as the MobiLink Monitor.



CR:633032
CR Number:   633032
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.0 2546 23 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
Replicating a "Point EMPTY" geometry object via Mobilink could have reported errors. In particular "Spatial library error: 25" could have been reported. This problem has been fixed.



CR:633041
CR Number:   633041
Product Name:   UltraLite
Product Component:   Sample Application
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 23 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
When running the UltraLite sample application on a Windows desktop, if no employee ID had been entered, a dialog is presented where one can be specified. Clicking on Cancel would have resulted in nothing happening. Now, the dialog box will be canceled when Cancel is clicked.



CR:633117
CR Number:   633117
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.0 2547 28 Jun 2010 Fixed
12.0.1 2954 20 Sep 2010 Fixed
Description
The following issues have been fixed for queries that bypass the optimizer:



1. the number of cached pages for an index was not saved for the graphical plans

2. complex expressions used in the WHERE clause may have produced different errors than the optimizer

3. predicate selectivities were not normalized, this was a different behaviour than the optimizer



CR:633118
CR Number:   633118
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.0 2578 14 Sep 2010 Fixed
11.0.1 2490 14 Sep 2010 Fixed
12.0.1 3026 20 Sep 2010 Fixed
Description
The Deployment Wizard did not deploy V3.5 and V4.0 .Net assemblies. They have now been added to the list of files we deploy.



CR:633120
CR Number:   633120
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 23 Jun 2010 Fixed
11.0.1 2455 23 Jun 2010 Fixed
10.0.1 4088 23 Jun 2010 Fixed
9.0.2 3971 23 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
Microsoft's SQL Server 2005/2008 Replication software allocates a 0x200 byte buffer for the TYPE_NAME column of the DBSCHEMA_PROVIDER_TYPES rowset. It then creates a DBBINDING structure identifying the length of the buffer as 0x300 bytes. When the SQL Anywhere OLE DB provider initializes the buffer with nulls, a stack overrun occurs and Microsoft's Replication software faults. As a work-around for Microsoft's bug, the SQL Anywhere OLE DB provider will no longer initialize the consumer's buffer with nulls.



CR:633125
CR Number:   633125
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 23 Jun 2010 Fixed
11.0.1 2454 23 Jun 2010 Fixed
10.0.1 4088 23 Jun 2010 Fixed
9.0.2 3971 23 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
Improvements to the DBSCHEMA_PROVIDER_TYPES rowset have been made to make it more consistent with Microsoft SQL Server.



CR:633132
CR Number:   633132
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   5.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 2952 23 Jun 2010 Fixed
Description
If the Interactive SQL utility, Sybase Central, or the Console utility had been redeployed (i.e. installed by any means other than the standard SQL Anywhere product installer), the ability to check for software updates was still presented to the user, but there was no way for it to make the check. Attempting to check for updates would have opened a status window which would say that it was analyzing the installed software, but would never have completed. Checking for software updates is supported only from the Interactive SQL utility, Sybase Central, or the Console utility which has been installed by the SQL Anywhere installer. Now, if redeployed software is run, the following changes to the user interface will be made:

1. (All) The Help menu items related to checking for updates are removed

2. (Interactive SQL utility) In the "Options" window, the "Update Checker" tab is removed for SQL Anywhere and UltraLite.



CR:633147
CR Number:   633147
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)
14 Mar 2011 Fixed
Description
Text indexes are now supported on materialized views.



The following syntax is used to create a text index on an an immediate or a manual materialized view:

CREATE TEXT INDEX [ IF NOT EXISTS ] text-index-name

ON [ owner.]imv-name( column-name, ... )

[ IN dbspace-name ]

[ CONFIGURATION [ owner.]text-configuration-name ]

[ IMMEDIATE REFRESH ]



Once a text index on a materialized view is created, it cannot be refreshed or truncated. The only

operation a user can perform on the text index is DROP. The text index on a materialized view will

be maintained by the server whenever the underlying materialized view is refreshed or updated.

If the materialized view is altered - for example, immediate materialized view is converted to manual -

the text index changes accordingly.



CR:633152
CR Number:   633152
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.0 2555 24 Jun 2010 Fixed
12.0.1 2976 20 Sep 2010 Fixed
Description
The window used to display a single cell value in a result set could have been too narrow to view the components it contains. The text which gives the length of the value could be abbreviated with an ellipsis, or hidden altogether on a system using a Japanese character set. The same thing could have happened regardless of the character set if certain large sized fonts are used as the computer's default font. This has now been fixed.



CR:633155
CR Number:   633155
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.0 2546 12 Jul 2010 Fixed
12.0.1 2953 20 Sep 2010 Fixed
Description
When deploying a Synchronization Model on Linux, Unix or Mac systems, the .sh files generated for the MobiLink server, remote database, synchronization client and consolidated database could have failed if command-line options (such as a connection string) or deployment options (such as the MobiLink server name) contained spaces. This has been fixed. The options are now quoted in the generated .sh files. A workaround is to edit the generated files to quote the options with spaces.



CR:633229
CR Number:   633229
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 4088 24 Jun 2010 Fixed
Description
Execution of a SELECT ... INTO table_name statement would have failed with "Syntax error near '('" if the source query contained UNIQUEIDENTIFIER columns and the statement was attempting to create a permanent table. This has been fixed.



CR:633232
CR Number:   633232
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.0 2573 24 Aug 2010 Fixed
11.0.1 2485 24 Aug 2010 Fixed
12.0.1 3016 20 Sep 2010 Fixed
Description
The server could have crashed under certain circumstances where malformed data existed in the database, and an attempt was made to generate statistics over this data either implicitly or explicitly. Customer applications that do not insert this malformed data are not likely to be impacted. The server now treats malformed data as NULL for the purpose of statistics collection.



CR:633243
CR Number:   633243
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.0 2546 24 Jun 2010 Fixed
12.0.1 2953 20 Sep 2010 Fixed
Description
If an ASE consolidated database was added to a project, it would have been shown as a "SQL Server" database in the user interface. Now, the database type text is "Adaptive Server Enterprise".



This affects the following parts of the UI:

1. The "Product" column on the "Consolidated Databases" tab

2. The property sheet for a consolidated database

3. The "Display Name and Description" page of the Add Consolidated Database Wizard

4. The "Consolidated Database Schema" page of the Create Synchronization Model Wizard

5. The "Consolidated Database Deployment Destination" page in the Deploy Synchronization Model Wizard

6. The "Consolidated Database Schema" page of the Update Schema Wizard



CR:633257
CR Number:   633257
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.0 2549 29 Jun 2010 Fixed
11.0.1 2458 29 Jun 2010 Fixed
12.0.1 2958 20 Sep 2010 Fixed
Description
When synchronizing a table with NOT NULL LONG BINARY or NOT NULL LONG VARCHAR columns, downloading an update to such a column could have resulted in an UljException -300 "Run time SQL error -- fatal". This has been fixed.



CR:633268
CR Number:   633268
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2546 28 Jun 2010 Fixed
11.0.1 2456 28 Jun 2010 Fixed
12.0.1 2953 20 Sep 2010 Fixed
Description
The changes for Engineering case 632526 may have caused the "SQL" field in the Plan Viewer window to become unusably short after the "Get Plan" button was clicked. This has been fixed.



CR:633269
CR Number:   633269
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.0 2546 28 Jun 2010 Fixed
12.0.1 2951 20 Sep 2010 Fixed
Description
Attempting to deploy a task containing characters that were not supported by the consolidated database, would have crashed Sybase Central. For example, setting a task description containing Japanese into a latin1252 database. The crash has been fixed. The new behavior in this situation depends on the consolidated database. In most cases the string will be degraded with the unsupported characters replaced. MYSQL will raise an error.



CR:633275
CR Number:   633275
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2548 29 Jun 2010 Fixed
11.0.1 2457 29 Jun 2010 Fixed
12.0.1 2957 20 Sep 2010 Fixed
Description
If a database mirroring server was shut down via the console (or via a HUP signal on Unix), it could have hung. This has been fixed. As a workaround, use the Stop Server utility (dbstop) to stop the server.



CR:633364
CR Number:   633364
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2547 28 Jun 2010 Fixed
12.0.1 2954 20 Sep 2010 Fixed
Description
The Moblink server could have randomly, although rarely, reported the error:

"Stream Error: Mismatched end-to-end encryption keys"



when establishing an end to end encryption link with Ultralite on the iphone. This has been fixed.



CR:633371
CR Number:   633371
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.0 2547 28 Jun 2010 Fixed
12.0.1 2954 20 Sep 2010 Fixed
Description
The Interactive SQL utility (dbisql) would not have started when using the -nogui command line option on a Linux computer which did not have a graphical environment. This has been fixed.



CR:633373
CR Number:   633373
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.0 2546 28 Jun 2010 Fixed
12.0.1 2952 21 Sep 2010 Fixed
Description
If a procedure used in the FROM clause of a statement was inlined, crashes or incorrect errors may have been reported if the following conditions hold:



1. the procedure contains a single statement having common table expressions (CTEs) defined using WITH [RECURSIVE] clause.

2. the procedure parameters are used inside the CTEs in any expression (e.g., WHERE predicate, select list item, etc.)

3. the procedure parameters are outerreferences in the FROM clause



This has been fixed. The workaround is to add an extra statement inside the procedure to make it not a candidate for inlining (e.g., " if 1 = 0 then return end if;")



CREATE PROCEDURE CRASH ( @databaseid INTEGER, @tableid INTEGER, @rowid BIGINT )



WITH RECURSIVE SIMPLE

( databaseid, tableid, rowid, mtableid, mrowid, stableid, srowid ) AS

(

SELECT databaseid, tableid, rowid, stableid, srowid, stableid, srowid

FROM ATABLE

WHERE databaseid = @databaseid AND stableid = @tableid AND srowid = @rowid

UNION ALL

...





SELECT databaseid, changeno, rowchangeno

FROM T rc

WHERE EXISTS (SELECT * FROM CRASH( rc.databaseid, rc.tableid, rc.rowid ) )



CR:633376
CR Number:   633376
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 2954 28 Jun 2010 Fixed
Description
In the Create Synchronization Model wizard, if a download subset was setup by user or remote ID using a joined table, and the joined table was also synchronized, then the download subset clause generated for that table would have joined the table to itself. This has been fixed. A workaround is to change the download subset in the table mapping editor to not use a joined relationship table.



CR:633379
CR Number:   633379
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.0 2547 29 Jun 2010 Fixed
12.0.1 2954 21 Sep 2010 Fixed
Description
The Interactive SQL utility would have crashed if the "Approximate" box in the Spatial Viewer window was checked before a query had been entered. This has been fixed by disabling the box when appropriate.



CR:633465
CR Number:   633465
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.0 2554 15 Jul 2010 Fixed
11.0.1 2467 15 Jul 2010 Fixed
12.0.1 2974 21 Sep 2010 Fixed
Description
Under rare circumstances, Application Profiling or diagnostic tracing could have caused the server to crash when the application being profiled used UPDATE statements with complex FROM clauses. This has been fixed.



A workaround is to avoid capturing the PLANS_WITH_STATISTICS level.



CR:633470
CR Number:   633470
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.0 2546 28 Jun 2010 Fixed
12.0.1 2954 21 Sep 2010 Fixed
Description
The SQL Anywhere Monitor launcher now includes support for a new switch, "-t", which will start the Monitor Developer Edition with TLS (i.e. HTTPS). In order to use this new feature, you an encryption certificate is needed along with its associated password.



The parameters for this switch are as follows:

-t <Encryption Certificate> <Certificate Password>



Where <Encryption Certificate> is the fully-qualified path to an encryption certificate and <Certificate Password> is the password for the certificate.



For example:

C:\> samonitor.exe -d C:\path\to\db\samonitor.db -t C:\path\to\cert\cert.cer myPassword



Note that this switch is not supported with the Production (i.e. Standalone) Edition of the Monitor.



CR:633486
CR Number:   633486
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.0 2553 28 Jun 2010 Fixed
12.0.1 2971 21 Sep 2010 Fixed
Description
Dragging and dropping within the Favorites sidebar did not work consistently and have been fixed. Specifically, the following actions did work correctly:

1. Dropping at the end of the list did nothing. Now the dragged item is moved to the end of the list.

2. Dropping an item to a location farther down the list would move it one higher than the indicated drop location. Now items are dropped where indicated.



CR:633488
CR Number:   633488
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.0 2549 29 Jun 2010 Fixed
12.0.1 2957 21 Sep 2010 Fixed
Description
On Unix systems, a process's address space can be limited by using "ulimit -v" or by various methods of setting system-wide defaults that are dependent on the version of Unix. The 64-bit SQL Anywhere server was not taking that limit into account when computing a maximum cache size and insufficient address space would have been left available for the server's other address space needs. This problem has been fixed.



Note, this issue is similar to Engineering case 586837, but only affects version 12.0.



CR:633490
CR Number:   633490
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.0 2548 28 Jun 2010 Fixed
12.0.1 2957 21 Sep 2010 Fixed
Description
The samonitor.sh file used to start and stop the SQL Anywhere Monitor on Linux was missing a "launch" option in the Developer Edition. This has been fixed. The "launch" option can be used to both start the SA Monitor and open up a web browser to the Monitor's web interface at the same time, rather than requiring the user to go through two separate steps.



CR:633503
CR Number:   633503
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.0 2548 29 Jun 2010 Fixed
12.0.1 2957 21 Sep 2010 Fixed
Description
When attempting to name or rename a task, if the new name contained characters that were not allowed in a file name (e.g. "\" or "?"), the property sheet for the remote task would simply refuse to close without explanation. This has been fixed so that an error message is now displayed.



CR:633520
CR Number:   633520
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.0 2548 29 Jun 2010 Fixed
12.0.1 2957 20 Sep 2010 Fixed
Description
The "Rows awaiting upload" checkbox was enabled in the property sheet for a Remote Task even if that task was associated with a Remote Schema Name for a SQL Anywhere database. Now, the checkbox is disabled in this case.



CR:633524
CR Number:   633524
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.0 2553 12 Jul 2010 Fixed
12.0.1 2957 21 Sep 2010 Fixed
Description
When running application profiling, or manually diagnostic tracing with host variables, the server may have hang. This has been fixed. A workaround is to avoid enabling the host-variable tracing level.



CR:633527
CR Number:   633527
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 2957 29 Jun 2010 Fixed
Description
When creating a Remote Task or when setting a task's properties checking the "AC Power" checkbox, and selecting "Computer is running on AC power" from a combobox, was required to specify that a task should run only when the remote computer was running on AC power. Now, the combobox has been removed and the checkbox text simply says "Computer is running on AC power".



CR:633600
CR Number:   633600
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.0 2546 29 Jun 2010 Fixed
11.0.1 2456 29 Jun 2010 Fixed
12.0.1 2953 21 Sep 2010 Fixed
Description
Some Visual Studio integration related problems were not handled by SetupVSPackage.exe, but were problems caused by SA installer when installing the SA ADO.NET provider and the SA Visual Studio Integration Package. Some of these problems were

1. Incorrect machine.config file.

2. SA ADO.NET provider assemblies were not added to GAC.

3. SA ADO.NET provider assemblies did not show up in Visual Studio Add Reference dialogbox.

4. Visual Studio failed to create DataSets or Entity Framework Models using SA data sources.



Re-installation of SQL Anywhere was usually required to fix these problems. Now all Visual Studio integration related code has been implemented in SetupVSPackage.exe, and any Visual Studio integration problem should be fixed by running SetupVSPackage. It will perform the following tasks:



1. Add / Remove assemblies of SA ADO.NET provider and integration package to / from GAC.

2. Register or unregister SA ADO.NET provider in machine.config.

3. Create registry keys for SA integration package

4. Create registry keys for Visual Studio Add Reference dialogbox.

5. Copy / Remove SSDLToSA12.tt to / from Visual Studio 2010 folder (%VS_DIR%\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\DBGen).

6. Register or unregister SA ADO.NET provider in %SQL Server 2008 DIR%\100\DTS\ProviderDescriptors\ProviderDescriptors.xml which is used by SQL Server Integration Service.

7. Setup Visual Studio IDE for SA integration package.



SetupVSPackage.exe is executed by the SQL Anywhere installer when installing or uninstalling SQL Anywhere, but SetupVSPackage.exe can be run separately. Two versions of SetupVSPackage.exe will be installed:

1. %SQLANY%\Assembly\V4\SetupVSPackage.exe - This version is built using .NET Framework 4, this version should be used if .NET Framework 4 is installed.

2. %SQLANY%\Assembly\V2\SetupVSPackage.exe - This version is built using .NET Framework 2, this version should be used if .NET Framework 4 is not installed.



A performance issue when running SetupVSPackage.exe for Visual Studio 2008 and 2010 has also been fixed.



CR:633610
CR Number:   633610
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.0 2559 30 Jun 2010 Fixed
10.0.1 4090 30 Jun 2010 Fixed
11.0.1 2458 27 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
The "Find/Replace" dialog could have failed to find text when the "Look in selection" box was checked. This was most likely to happen if the selection started far from the start of the text, and ended close to the end of the text. This has been fixed.



CR:633633
CR Number:   633633
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.0 2549 30 Jun 2010 Fixed
12.0.1 2958 21 Sep 2010 Fixed
Description
When attempting to start the server on a machine with 256 or more processors, the server would have failed to start with assertion failure 109511: "Memory allocation size too large". This has been fixed. A workaround is to reduce the number of processors used by the server with the -gt or -gtc command line options.



CR:633636
CR Number:   633636
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.0 2549 30 Jun 2010 Fixed
12.0.1 2958 21 Sep 2010 Fixed
Description
The messages pane height was not being set to the number of lines specify in the Options dialog. This has been fixed. At the same time, the components related to the Messages pane height are now disabled in the Options dialog until the "Show separate Message pane" box is checked, since the height is used only when this box is checked.



CR:633643
CR Number:   633643
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.0 2549 30 Jun 2010 Fixed
12.0.1 2958 21 Sep 2010 Fixed
Description
The "Deploy Configuration File" window indicated that a Relay Server URL was to be entered, which was not correct. What was supposed to be entered was the URL suffix (everything after the host and port number). The label for the field has been changed to "Relay server URL suffix" and an example has been added under the field to illustrate typical values.



Also, the code which was supposed to populate the "Relay Server URL suffix" field with whatever value was used previously was incorrect, and has been fixed.



CR:633685
CR Number:   633685
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.0 2549 30 Jun 2010 Fixed
11.0.1 2458 30 Jun 2010 Fixed
12.0.1 2959 21 Sep 2010 Fixed
Description
Under rare situation, the Relay Server Outbound Enabler (RSOE) may have crashed during channel renewal. This has been fixed.



CR:633740
CR Number:   633740
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2458 30 Jun 2010 Fixed
Description
Blobs and Clobs in temporary tables were not always being freed. This has been corrected, truncation of temporary tables will now free blobs within the freed rows.



CR:633744
CR Number:   633744
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2549 30 Jun 2010 Fixed
11.0.1 2458 30 Jun 2010 Fixed
10.0.1 4091 30 Jun 2010 Fixed
12.0.1 2959 21 Sep 2010 Fixed
Description
On Mac OS X systems, the name of a saved history file was given the extension "..sq", rather than ".sql", when an explicit file extension was not entered. This has been fixed.



CR:633747
CR Number:   633747
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.0 2550 06 Jul 2010 Fixed
11.0.1 2461 06 Jul 2010 Fixed
10.0.1 4093 06 Jul 2010 Fixed
12.0.1 2965 21 Sep 2010 Fixed
Description
Unsetting the public option Oem_string would have caused the server to crash. This has been fixed.



CR:633753
CR Number:   633753
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.0 2553 13 Jul 2010 Fixed
11.0.1 2465 13 Jul 2010 Fixed
10.0.1 4098 13 Jul 2010 Fixed
12.0.1 2971 21 Sep 2010 Fixed
Description
If an application deleted a row from a table with a unique index, then subsequently called an external environment procedure, and the external environment procedure then re-added the row using the server-side connection, the application would have received an assertion failure (200112) message on rollback. This problem has now been fixed.



CR:633758
CR Number:   633758
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.0 2549 05 Jul 2010 Fixed
12.0.1 2959 21 Sep 2010 Fixed
Description
The MobiLink Replay utility (mlreplay) had an unnecessary stack size restriction that could have caused it to crash with a stack overflow error if large objects and arrays were placed on the stack when using the replay library. This stack size restriction has been removed.



CR:633773
CR Number:   633773
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.0 2555 05 Jul 2010 Fixed
11.0.1 2468 05 Jul 2010 Fixed
10.0.1 4100 05 Jul 2010 Fixed
12.0.1 2976 21 Sep 2010 Fixed
Description
The method used for an internal database server timer on Linux to support request timing (-zt option,) and row access times in the graphical plan with statistics, was unreliable. This has been fixed.



CR:633775
CR Number:   633775
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.0 2559 27 Jul 2010 Fixed
11.0.1 2459 27 Jul 2010 Fixed
10.0.1 4091 27 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
Exporting source control commands from the "Custom Source Control Options" window could have caused the Interactive SQL utility to crash on Mac OS X systems. This has been fixed.



CR:633784
CR Number:   633784
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)
11.0.1 2459 05 Jul 2010 Fixed
10.0.1 4091 05 Jul 2010 Fixed
12.0.0 2559 28 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
The "Tools" button on the "Connect" window, and any toolbar buttons in Sybase Central which have drop-down arrows, were drawn without the usual button border and background gradient on Linux and Solaris computers. This has now been fixed so that they have the correct background and border.



CR:633795
CR Number:   633795
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.0 2557 05 Jul 2010 Fixed
11.0.1 2472 05 Jul 2010 Fixed
12.0.1 2982 21 Sep 2010 Fixed
Description
Under rare circumstances, a query with a CONTAINS clause or predicate could have returned incorrect results when executed on a connection with snapshot isolation. For the problem to have occurred, the query would have had to have used an IMMEDIATE text index with a high volume of updates. This has been fixed.



CR:633799
CR Number:   633799
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2459 05 Jul 2010 Fixed
10.0.1 4091 05 Jul 2010 Fixed
12.0.0 2559 27 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
The "Find/Replace" window could have opened without any components if it was opened from a window used to view a stored procedure or view. The window typically contained only a grey or white rectangle. The problem happened only when opening a file in the editor window, or when clicking "File/New". This has now been fixed.



CR:634029
CR Number:   634029
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2559 05 Jul 2010 Fixed
11.0.1 2459 27 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
Pressing Shift+F10 while a syntax-highlighting editor had focus should have opened its context menu, but did not happen consistently. This has now been fixed."



CR:634032
CR Number:   634032
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)
11.0.1 2459 06 Jul 2010 Fixed
10.0.1 4092 06 Jul 2010 Fixed
12.0.0 2559 26 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
The 'Find/Replace' toolbar button did not work in an editor window if the toolbar had been undocked. This has been fixed by preventing the toolbar from being undocked.



A workaround is to use the menu item or F3 key to open the 'Find/Replace' window.



CR:634033
CR Number:   634033
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.0 2549 05 Jul 2010 Fixed
12.0.1 2961 21 Sep 2010 Fixed
Description
When loading shapes into a round-earth spatial reference system, certain valid shapes may have incorrectly generated the error "Invalid polygon: multiple exterior rings" (Error Code -1451) This would have occurred for polygons with holes (i.e., polygons defined by two or more rings), and was most likely to occur when the hole appeared near the edge of the exterior ring. There was a small possibility that the reported error could instead have been "Invalid polygon nesting" (Error Code -1450), "Invalid polygon: no exterior ring" (Error Code -1449), or that any of these errors could occur for a valid polygon (with or without holes) whose exterior ring crossed the equator. This has been fixed.



CR:634055
CR Number:   634055
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2459 06 Jul 2010 Fixed
12.0.0 2559 27 Jul 2010 Fixed
12.0.1 2986 21 Sep 2010 Fixed
Description
When editing a stored procedure or view in a separate window, the "Undo" toolbar button was not enabled following a paste. This has been fixed.



CR:634180
CR Number:   634180
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 2961 06 Jul 2010 Fixed
Description
Selecting multiple columns in the Data tab for a table in an UltraLite database was not possible. This has been fixed.



CR:634181
CR Number:   634181
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 3057 05 Oct 2010 Fixed
12.0.0 2593 05 Oct 2010 Fixed
11.0.1 2504 05 Oct 2010 Fixed
10.0.1 4130 05 Oct 2010 Fixed
Description
The amount of data in CHAR, NCHAR or BINARY variables could have exceeded the declared length of the variable when data was appended using the string concatenation operator (||). This has been fixed.



CR:634184
CR Number:   634184
Product Name:   MobiLink
Product Component:   MobiLink Agent
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2550 05 Jul 2010 Fixed
12.0.1 2964 21 Sep 2010 Fixed
Description
The MobiLink agent for central administration of remotes could not be configured as a Windows service with dbsvc. This has been fixed.



CR:634189
CR Number:   634189
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2550 06 Jul 2010 Fixed
11.0.1 2460 06 Jul 2010 Fixed
10.0.1 4093 06 Jul 2010 Fixed
12.0.1 2964 21 Sep 2010 Fixed
Description
If a connection string was made up of parameters coming from the connection string and from the data source, and the UID and PWD/ENP parameters were not all in the connection string or all in the data source, the PWD/ENP parameters would have been ignored. For example, if DSN "foo" contained a UID but no PWD, then the connection string "DSN=foo;PWD=secret" would ignore the PWD field. This has been fixed.





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

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

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

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

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

各种误操作:

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

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

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


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

Sybase ASE数据库恢复工具READSYBDEVICE:

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

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

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

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

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


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

SQL Server数据库恢复工具SQLRescue:

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

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

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

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

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

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

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