提供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:629534
CR Number:   629534
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 2446 21 May 2010 Fixed
Description
When executing stored procedures in the FROM clause, the performance of the statement was slower than previous versions. The effect was most significant for procedures that return many rows with very little execution cost in the procedure. This has been fixed.



CR:629569
CR Number:   629569
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 2447 25 May 2010 Fixed
11.0.1 2439 25 May 2010 Fixed
Description
As of the changes made for Engineering case 568632, running a DESCRIBE statement in an Interactive SQL utility window always resulted in an error message. This has been fixed.



CR:629577
CR Number:   629577
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 2446 21 May 2010 Fixed
11.0.1 2439 21 May 2010 Fixed
Description
For Unix versions, the server's usage display included incorrect values in the descriptions for the options -n, -p, -tl and -x. This has been fixed.



CR:629595
CR Number:   629595
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 2447 21 May 2010 Fixed
Description
Clicking the ">" buttons on the Editor customization dialog's "Print" tab could have caused the resulting popup menus to appear on the wrong monitor if the computer had two monitors. The problem occurred only if the Options dialog was open on the secondary monitor, and only if the secondary monitor was logically positioned to the right of the primary monitor. This has been fixed.



Note that this problem also affects Sybase Central.



CR:629597
CR Number:   629597
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.0 2447 21 May 2010 Fixed
11.0.1 2439 21 May 2010 Fixed
10.0.1 4073 21 May 2010 Fixed
Description
The initial position of the main window for the MobiLink Monitor could have placed the window underneath the Windows task bar. This has been fixed.



Note, this problem also affected the Interactive SQL utility, Sybase Central, and the SQL Anywhere Console utility.



CR:629606
CR Number:   629606
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 2446 21 May 2010 Fixed
11.0.1 2439 21 May 2010 Fixed
10.0.1 4073 21 May 2010 Fixed
9.0.2 3966 21 May 2010 Fixed
Description
When using SQL Server Integration Services (SSIS), an attempt to migrate tables between SQL Anywhere/Sybase IQ and SQL Server databases would have failed. This problem has been corrected.



Note, if the Data Flow consists of more than 10 tables that are to be migrated to SQL Server from a SQL Anywhere server, the Personal server should not be used since each table is moved asynchronously on a separate connection (i.e., more than 10 simultaneous connections will be made to the SQL Anywhere server and the number of simultaneous connections is limited with the Personal server).



CR:629758
CR Number:   629758
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 2449 25 May 2010 Fixed
11.0.1 2439 25 May 2010 Fixed
10.0.1 4074 25 May 2010 Fixed
Description
The SAConnection.GetSchema method returned incorrect schema data for the DataTypes schema set and the DataSourceInformation schema set. This problem was found using the SQL Server Integration Service's Import and Export Wizard. This has now been corrected.



CR:629759
CR Number:   629759
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 2456 25 May 2010 Fixed
11.0.1 2441 25 May 2010 Fixed
11.0.0 1654 25 May 2010 Fixed
Description
A query that made use of index only retrieval could have returned incorrect results (too few rows) in some cases. This has been fixed.



CR:629768
CR Number:   629768
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 2540 25 May 2010 Fixed
11.0.1 2439 25 May 2010 Fixed
12.0.1 2918 15 Sep 2010 Fixed
Description
The file browser that opened after clicking the "Save" button in the Index Consultant did not prevent interaction with the wizard while it was open. This has been corrected so that it does.



CR:630040
CR Number:   630040
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 2541 26 May 2010 Fixed
11.0.1 2441 26 May 2010 Fixed
12.0.1 2922 15 Sep 2010 Fixed
Description
Messages in the Run Script window could have been truncated. The problem did not occur on all systems; it depended on the selected system font. The problem would have occurred on Windows for example, if "MS UI Gothic" was selected for the desktop icon font. This has been fixed.



CR:630073
CR Number:   630073
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2541 25 May 2010 Fixed
11.0.1 2441 25 May 2010 Fixed
10.0.1 4075 25 May 2010 Fixed
12.0.1 2922 15 Sep 2010 Fixed
Description
The contents of the combobox in the "Schedule Editor" window could have been truncated on some systems, depending on which font was being used by Sybase Central. This has been fixed.



CR:630082
CR Number:   630082
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 2541 26 May 2010 Fixed
11.0.1 2441 26 May 2010 Fixed
10.0.0 4075 26 May 2010 Fixed
12.0.1 2922 15 Sep 2010 Fixed
Description
The "Apply" button in the client properties window (for a given server store) was not enabled correctly, and when it was enabled, it did not consistently apply the changes. This has been fixed.



CR:630179
CR Number:   630179
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2458 01 Jun 2010 Fixed
11.0.1 2522 09 Nov 2010 Fixed
Description
On the Connected Users or All Connected Users tabs, if two or more connections were selected, and clicked on File->Disconnect, then Sybase Central would have crashed. This has been fixed.
Workaround Description
 Disconnect each connection ... one-by-one.



select connection

disconnect

select connection

disconnect

...



CR:630210
CR Number:   630210
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 2542 26 May 2010 Fixed
11.0.1 2441 26 May 2010 Fixed
12.0.1 2923 15 Sep 2010 Fixed
Description
If a GRANT or REVOKE statement was executed for a view which was currently invalid (e.g. because it referenced a table that has been dropped), an error indicating that the view was invalid might have been given. Now, the error is suppressed, but the view is still marked as invalid.



CR:630219
CR Number:   630219
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 2542 26 May 2010 Fixed
11.0.1 2441 26 May 2010 Fixed
12.0.1 2923 16 Sep 2010 Fixed
Description
On non-Windows computers, a proportional font was used when displaying results as text in the Interactive SQL utility. This prevented the columns from lining up correctly. Now, a monospaced font is used. On Windows computers, a monospaced font has always been used.



CR:630225
CR Number:   630225
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)
31 May 2010 Fixed
Description
The sql error message for SQLE_ TOO_MANY_COLUMNS_DELETED (SQLCODE -124) "More columns are being dropped from table '%1' than are defined" was misleading. It has been changed to "Dropping all columns from table '%1' is not allowed".



CR:630226
CR Number:   630226
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 2543 02 Jun 2010 Fixed
11.0.1 2444 02 Jun 2010 Fixed
10.0.1 4079 02 Jun 2010 Fixed
12.0.1 2929 16 Sep 2010 Fixed
Description
If an ALTER TABLE statement had a DROP or ALTER column clause, and the column did not exist,

then an incorrect column name could have been reported in the error message. This only happened if there was another ADD, ALTER or DROP column clause in the statement. This has been fixed.



CR:630338
CR Number:   630338
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 2543 07 Jun 2010 Fixed
11.0.1 2445 07 Jun 2010 Fixed
10.0.1 4080 07 Jun 2010 Fixed
12.0.1 2932 16 Sep 2010 Fixed
Description
If the option row_counts was set to 'On', the system procedures sa_performance_statistics and sa_performance_diagnostics did not return a result set, and the procedure sa_describe_query caused an assertion failed 109512 error. These problems have been fixed.



CR:630359
CR Number:   630359
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 2542 27 May 2010 Fixed
11.0.1 2441 27 May 2010 Fixed
10.0.1 4076 27 May 2010 Fixed
12.0.1 2923 16 Sep 2010 Fixed
Description
The ASE label for the "GBK" character set has been changed from "CP936" to "cp936", as character set names passed to ASE APIs such as cs_locale() are case sensitive. The ASE version of character set labels is generally not used directly by SQL Anywhere, but is provided to users who need to use ASE libraries. Typically, a client would obtain the ASE label via a call such as db_extended_property( 'charset', 'ase' ).



CR:630376
CR Number:   630376
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 2543 01 Jun 2010 Fixed
11.0.1 2444 01 Jun 2010 Fixed
10.0.1 4078 01 Jun 2010 Fixed
12.0.1 2929 16 Sep 2010 Fixed
Description
If a database being mirrored had been enabled for auditing and the mirror servers were restarted, no auditing operations were recorded in the transaction log. This has been fixed.



CR:630392
CR Number:   630392
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2542 28 May 2010 Fixed
12.0.1 2924 16 Sep 2010 Fixed
Description
The SQL Anywhere Console utility (dbconsole) would have displayed a message with the text "java.lang.NullPointerException" and an "OK" button if the "Options" window was opened before a connection had been opened. This has been fixed.



CR:630403
CR Number:   630403
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 2542 28 May 2010 Fixed
12.0.1 2924 16 Sep 2010 Fixed
Description
Sybase Central would have crashed if the Agent Wizard was closed before any file browser that was opened from the wizard. This has been fixed.



CR:630408
CR Number:   630408
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 2461 28 May 2010 Fixed
11.0.1 2442 28 May 2010 Fixed
10.0.1 4076 28 May 2010 Fixed
Description
The method SAConnection.GetSchema() would have returned incorrect data. Database objects owned by system accounts were being included in the result sets. They are now excluded.



CR:630475
CR Number:   630475
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2543 02 Jun 2010 Fixed
11.0.1 2444 02 Jun 2010 Fixed
12.0.1 2929 16 Sep 2010 Fixed
Description
If an application used the SQL Anywhere JDBC driver to obtain the ResultSet from a call to DatabaseMetaData.getPrimaryKeys(), then the driver would incorrectly return a ResultSet that was sorted by catalog, schema, table name and key sequence. This has now been fixed and the ResultSet is now sorted by column name instead.



Note that this fix is only for the SQL Anywhere JDBC driver. The iAnywhere JDBC driver will continue to return a ResultSet based on ODBC sorting standards.



CR:630519
CR Number:   630519
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 2542 28 May 2010 Fixed
11.0.1 2442 28 May 2010 Fixed
10.0.1 4076 28 May 2010 Fixed
12.0.1 2924 16 Sep 2010 Fixed
Description
A query that referenced a view or derived table that contained a select list item that was not a table column could have caused a crash when executing using proxy tables. This has been fixed.



CR:630522
CR Number:   630522
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 2542 28 May 2010 Fixed
11.0.1 2442 28 May 2010 Fixed
10.0.1 4077 28 May 2010 Fixed
12.0.1 2925 16 Sep 2010 Fixed
Description
The Interactive SQL utility (dbisql) could have crashed if more than one dbisql window was opened by clicking the "Window/New Window" menu item, the first window was close, then the "Preferences" item in the "Interactive SQL" menu was clicked. This bug also had the symptom of always showing the preferences for the first window, never for any of the subsequently opened windows. This has been fixed.



CR:630527
CR Number:   630527
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 2543 01 Jun 2010 Fixed
11.0.1 2443 01 Jun 2010 Fixed
12.0.1 2918 16 Sep 2010 Fixed
Description
The ApproximateCPUTime property would have grown in value for blocked connections if the property was queried. This problem was most noticeable for connections that were blocked for long periods of time and for whom this property was frequently queried. This has now been fixed.



CR:630540
CR Number:   630540
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 2461 28 May 2010 Fixed
11.0.1 2442 28 May 2010 Fixed
10.0.1 4076 28 May 2010 Fixed
Description
The method SAConnection.ServerVersion() has been changed to return normalized version strings that match the strings returned by SqlConnection.ServerVersion().



CR:630542
CR Number:   630542
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 2461 28 May 2010 Fixed
11.0.1 2442 28 May 2010 Fixed
10.0.1 4076 28 May 2010 Fixed
Description
In the SADataReader's schema table, , the SCALE property for Date, DateTime, DateTimeOffset, SmallDateTime, Time, Timestamp, and Timestamp with time zone columns, has been changed to 6.



CR:630547
CR Number:   630547
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2542 31 May 2010 Fixed
12.0.1 2958 16 Sep 2010 Fixed
Description
When updating an Oracle consolidated database schema for a Synchronization Model which had used a subset of owners for schema loading, by default the schema would have been loaded for all owners. Now the default is to use the same owner subset.



CR:630884
CR Number:   630884
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 2542 31 May 2010 Fixed
12.0.1 2925 16 Sep 2010 Fixed
Description
On Mac OS X systems, the Interactive SQL utility was, in some cases, using reserved keystrokes for certain menu items and buttons. The following menu accelerators have been changed for Mac OS X only:



Menu Item New Accelerator

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

SQL/History Ctrl+Command+H

SQL/Previous SQL Ctrl+Command+LeftArrow

SQL/Next SQL Ctrl+Command+RightArrow



The following accelerators for buttons on the Spatial Viewer have been changed for OS X only:



Button New Accelerator

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

History Ctrl+Command+H

Previous SQL Ctrl+Command+LeftArrow

Next SQL Ctrl+Command+RightArrow

Save Image Command+S

Hide SQL Shift+Command+H

Zoom In Command+Plus

Zoom Out Command+Minus

Reset View Command+R

Draw Outlined Polygons Command+P



The tooltips for the above buttons now display the correct key name as well. Previouly, the tooltip displayed the Windows/Linux/Solaris accelerator key name instead of the Mac one.



CR:630890
CR Number:   630890
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2543 31 May 2010 Fixed
11.0.1 2443 31 May 2010 Fixed
10.0.1 4078 31 May 2010 Fixed
12.0.1 2928 16 Sep 2010 Fixed
Description
In very rare situations, the server may have crashed when executing a statement that contained a large number of UNION, EXCEPT or INTERSECT clauses. This has been fixed. These statements will now return the sql error "Statement size or complexity exceeds server limits".



CR:630897
CR Number:   630897
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 2542 31 May 2010 Fixed
12.0.1 2925 16 Sep 2010 Fixed
Description
If a SQL favorite contained a TAB character, it could have prevented some, or all, of the other favorites from being loading, and they would have been lost. This has been fixed.



CR:630909
CR Number:   630909
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 2466 31 May 2010 Fixed
11.0.1 2443 31 May 2010 Fixed
10.0.1 4077 31 May 2010 Fixed
Description
Calls to the method SADataAdapter.Update() in batch update mode would have hung when updating large tables. This has been fixed.



CR:630911
CR Number:   630911
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 2465 31 May 2010 Fixed
11.0.1 2443 31 May 2010 Fixed
10.0.1 4077 31 May 2010 Fixed
Description
Some result sets returned by by the method SAConnection.GetSchema() were not sorted. This has been corrected.



CR:630913
CR Number:   630913
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 2466 31 May 2010 Fixed
11.0.1 2443 31 May 2010 Fixed
10.0.1 4077 31 May 2010 Fixed
Description
If some columns had been dropped from a table, SAConnection.GetSchema( "Columns" ) could have returned incorrect ORDINAL_POSITION values for that table. This has been fixed.



CR:631004
CR Number:   631004
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 2571 18 Aug 2010 Fixed
11.0.1 2482 18 Aug 2010 Fixed
12.0.1 3010 16 Sep 2010 Fixed
Description
The range for a correlation coefficient is between -1 and +1, however the corr() system function returned only positive values. This has now been corrected.



CR:631009
CR Number:   631009
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 2543 31 May 2010 Fixed
12.0.1 2928 16 Sep 2010 Fixed
Description
Changes made to an agent's properties would not have been made permanent after clicking any of the items in the agent's "Set" menu. A similar problem affected changes made in the property sheet for a remote database to the description or the agent's connection string. These have been fixed.



CR:631017
CR Number:   631017
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 2467 31 May 2010 Fixed
11.0.1 2443 31 May 2010 Fixed
10.0.1 4078 31 May 2010 Fixed
Description
If an application attempted to create a proxy table to a Microsoft SQL Server table which contained a varbinary(max) column, then the server would have incorrectly mapped the varbinary(max) column to varbinary(1). This problem has now been fixed and the server now correctly maps varbinary(max) columns to long varbinary.



CR:631018
CR Number:   631018
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 2543 01 Jun 2010 Fixed
12.0.1 2928 16 Sep 2010 Fixed
Description
A newly-created remote task command might not have been saved when a different tree item was selected. This happened very occasionally, and has been seen only on Linux computers. This has been fixed.



CR:631019
CR Number:   631019
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.1 3278 21 Jan 2011 Fixed
12.0.0 2636 21 Jan 2011 Fixed
Description
Two issues relating to using the INPUT and OUTPUT statements (and their corresponding wizards) to move data between SQL Anywhere and ASE have been fixed.



Importing a table from ASE which had TIMESTAMP columns into a new table would have failed. The ASE TIMESTAMP type was being misinterpreted as being equivalent to the SQL Anywhere TIMESTAMP type, which is false.



Exporting data from SQL Anywhere into ASE would have reported various conversion issues for SQL Anywhere DECIMAL values.



CR:631022
CR Number:   631022
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 2928 01 Jun 2010 Fixed
Description
When creating an ODBC DSN from the Connect dialog, the prompt that warned that the DSN already existed had a Cancel button. It should not have and has been removed.



Also, clicking the close button (the "X" in the toolbar) aborted the entire process of creating the DSN; now, clicking the close button is the same as clicking the "No" button, which leaves the "Saves as ODBC Data Source" window open.



CR:631023
CR Number:   631023
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2468 02 Jun 2010 Fixed
11.0.1 2443 02 Jun 2010 Fixed
10.0.1 4078 02 Jun 2010 Fixed
Description
SA Clients on Mac OS X systems would have received the error "TLS handshake failure" (SQLCODE -829) when attempting to connect using TLS/RSA to a server running on a different operating system. This has been fixed.



Note: Engineering case 626480 included new versions of the Certicom and OpenSSL libraries. This problem only affects Mac OS X clients with these new libraries connecting to servers on a different operating system also with these new libraries.



CR:631026
CR Number:   631026
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 2469 01 Jun 2010 Fixed
11.0.1 2443 01 Jun 2010 Fixed
10.0.1 4078 01 Jun 2010 Fixed
Description
When using the ADO.NET provider to insert long binary, varchar or nvarchar values with a SQL_BINARY, SQL_VARCHAR or SQL_NVARCHAR parameter type, the parameter type that is passed to the server will be changed to SQL_LONGBINARY, SQL_LONGVARCHAR or SQL_LONGNVARCHAR if the length of the value to be inserted is greater than 32767 bytes.



CR:631028
CR Number:   631028
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 2543 01 Jun 2010 Fixed
11.0.1 2443 01 Jun 2010 Fixed
12.0.1 2928 16 Sep 2010 Fixed
Description
Creating the first user DSN by clicking the "Save as ODBC Data Source" Tools button could have silently failed. This has been fixed.



CR:631030
CR Number:   631030
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 2467 01 Jun 2010 Fixed
11.0.1 2443 01 Jun 2010 Fixed
Description
Databases could not have been created on SD cards and the internal flash of some older RIM devices. There were two problems in the RIM Operating System late in the 4.2.1.x versions, extending to the 4.2.2.48 version, that would have caused problems creating databases on these devices. An input stream could not have been opened until something had been written to the file, and the database file would have been destroyed on the second write to the start of the file. These problems were resolved by reprogramming some of the support for these devices so that the problems were not encountered.



CR:631033
CR Number:   631033
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2543 07 Jun 2010 Fixed
12.0.1 2932 16 Sep 2010 Fixed
Description
Starting in version 12.0.0, on Windows computers numbers are now formatted with the thousands separator that is shown in the Windows Control Panel. With this fix, thousands separators are not shown at all if they have been turned off on the Control Panel. Previously, they were always shown.



Note, this fix also affects the "Data" tab for tables and views in Sybase Central.



CR:631045
CR Number:   631045
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2543 03 Jun 2010 Fixed
11.0.1 2444 03 Jun 2010 Fixed
12.0.1 2930 16 Sep 2010 Fixed
Description
If an application attempted to establish a connection using the ASADataSource class available with the SQL Anywhere JDBC driver, then the application would have received a ClassCastException. This problem has now been fixed.



Note that in addition to supporting the ASADataSource class, the SQL Anywhere and iAnywhere JDBC drivers now offer an SADataSource class as well.



CR:631096
CR Number:   631096
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 2543 01 Jun 2010 Fixed
12.0.1 2929 20 Sep 2010 Fixed
Description
If deleting a Remote Schema Name failed for any reason, it was still removed from the project. Now, it remains in the project.



In a related issue, if the Remote Schema Name cannot be deleted because there are agents still managing databases with that Remote Schema Name, an error message is now shown explaining that condition as plainly as possible. Previously, the underlying error message from the consolidated database was displayed, which was not helpful.



CR:631104
CR Number:   631104
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 2543 01 Jun 2010 Fixed
12.0.1 2929 20 Sep 2010 Fixed
Description
Checking the "Enable Agent logging" checkbox on the "Logging" page of an Agent Configuration File property sheet enables six more check boxes allowing for specifying what kind of messages are to be logged. Previously, the options in the file were not read correctly so that none of those six checkboxes were ever checked, even though the configuration file was correct. This has been fixed.



CR:631113
CR Number:   631113
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 2543 01 Jun 2010 Fixed
11.0.1 2444 01 Jun 2010 Fixed
12.0.1 2929 20 Sep 2010 Fixed
Description
Attempting to execute a CREATE OR REPLACE PROCEDURE statement could have caused a server crash. This has been fixed.



CR:631119
CR Number:   631119
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Solaris
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2544 14 Jun 2010 Fixed
11.0.1 2447 14 Jun 2010 Fixed
10.0.1 4082 14 Jun 2010 Fixed
12.0.1 2939 20 Sep 2010 Fixed
Description
If the empty string was passed into an SQLNativeSQL or SQLPrepare function, it was possible for the iAS Oracle ODBC Driver to have crashed. This has been fixed. The SQLPrepare function will now return the error "Invalid string or buffer length", and the SQLNativeSQL function will now simply set the out parameters to the empty string as well.



CR:631122
CR Number:   631122
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)
12.0.0 2543 01 Jun 2010 Fixed
11.0.1 2444 01 Jun 2010 Fixed
10.0.1 4078 01 Jun 2010 Fixed
12.0.1 2929 20 Sep 2010 Fixed
Description
After right-clicking a procedure or function and selecting "Execute from Interactive SQL", the resulting dialog where the parameters are specified had a row height for the table that was too small. This caused text to be clipped in the "Value" column. This has been fixed.



CR:631141
CR Number:   631141
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 2543 02 Jun 2010 Fixed
12.0.1 2929 20 Sep 2010 Fixed
Description
Clicking the "Data>Show Results as Scrollable Table" or "Data>Show Results as Text" menu items did not make the setting permanent, which could have lead to the wrong format being used when disconnecting and then reconnecting without stopping Interactive SQL. This has been fixed, now these menu items exactly correspond to the "Scrollable table" / "Text" options in the "Options" window, which was the original intent.



CR:631147
CR Number:   631147
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 2471 02 Jun 2010 Fixed
Description
When creating or altering a spatial reference system, the catalog table SYSSPATIALREFERENCESYSTEM.storage_format column contained the case of type from the statement instead of the normalized case. For example, with a statement such as the following the server would have stored 'oRiginal' instead of 'Original'.



create or replace spatial reference system "WGS84_orig"

identified by 50000

type round earth

storage format 'oRiginal'



This has been corrected so that the case is normalized.



CR:631148
CR Number:   631148
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 2543 02 Jun 2010 Fixed
12.0.1 2929 20 Sep 2010 Fixed
Description
When Sybase Central is shut down, it closes any Interactive SQL windows which were opened from within Sybase Central. Part of that closing process may prompt the user to save unsaved changes, or may remind them that closing Interactive SQL will also close any Plan Viewer or Spatial Viewer windows. On Linux systems, if the Interactive SQL window was obscured by Sybase Central when Sybase Central was closed, the prompts could have been hidden by the Sybase Central window. Unless the Interactive SQL window was activated, or the Sybase Central window was moved, the prompts would have been hidden and Sybase Central would not have closed. Now, the Interactive SQL windows are activated and any prompts should appear on top of the Interactive SQL window(s).



CR:631234
CR Number:   631234
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 2543 02 Jun 2010 Fixed
12.0.1 2930 20 Sep 2010 Fixed
Description
It was possible to create a Remote Task with an empty name (which is generally not allowed) by pasting it and then clearing the Name field in the resulting "Paste" dialog. The same problem also affected the pasting of groups. This has been fixed.



CR:631249
CR Number:   631249
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 2472 02 Jun 2010 Fixed
11.0.1 2444 02 Jun 2010 Fixed
10.0.1 4079 02 Jun 2010 Fixed
Description
The result sets returned by calls to SAConnection.GetSchema( "Columns" ) and SAConnection.GetSchema( "DataTypes" ) could have been incorrect. This has been fixed.



CR:631253
CR Number:   631253
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.0 2543 21 Jun 2010 Fixed
12.0.1 2930 20 Sep 2010 Fixed
Description
In the property sheet for a Relay Server farm, if a custom command line for the Relay Server Outbound Enabler was specified, it was not displayed when the property sheet was subsequently opened. This has been fixed.



CR:631269
CR Number:   631269
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 2543 02 Jun 2010 Fixed
12.0.1 2930 20 Sep 2010 Fixed
Description
The Interactive SQL utility could have reported an internal error if the SRID was changed on the "Spatial Preview" tab in the column value window. The problem was most likely to happen if the SRID was changed faster than the database server was able to render the spatial value. This has been fixed.



CR:631280
CR Number:   631280
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 2463 03 Jun 2010 Fixed
11.0.1 2443 03 Jun 2010 Fixed
Description
The MobiLink Server could have hung or crashed on MacOSX 10.6 systems when the server was run as a daemon (using the -ud command line option). This has been fixed.



CR:631330
CR Number:   631330
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 2543 03 Jun 2010 Fixed
11.0.1 2445 03 Jun 2010 Fixed
10.0.1 4079 03 Jun 2010 Fixed
9.0.2 3968 03 Jun 2010 Fixed
12.0.1 2931 20 Sep 2010 Fixed
Description
Some inconsistencies between SQL Anywhere OLE DB column metadata information and run-time column information caused problems with accessing tables via the Microsoft SQL Server "Linked Server" mechanism. These problems affected NCHAR, NVARCHAR,LONG NVARCHAR, VARBIT, LONG VARBIT, and TIMESTAMP WITH TIME ZONE columns. The TIMESTAMP WITH TIMEZONE data type is new to version 12.0.0. These problems have been fixed. Table rows inserted using the OLE DB OpenRowset/InsertRows methods are now done with autocommit turned off. Once the inserts are completed, the rows are committed.



For the complete fix to this problem, use the Upgrade utility (dbupgrad) to upgrade existing databases with fixes for the OLE DB schema rowset support (metadata support).



CR:631404
CR Number:   631404
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 2543 03 Jun 2010 Fixed
11.0.1 2445 03 Jun 2010 Fixed
12.0.1 2931 20 Sep 2010 Fixed
Description
The NOT NULL FOREIGN KEY clause was misdiagnosed as invalid in ALTER TABLE statement. This was been corrected.



CR:631405
CR Number:   631405
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)
11.0.1 2451 16 Jun 2010 Fixed
12.0.0 2545 16 Jun 2010 Fixed
10.0.1 4085 16 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
If a result set contained a column with ROWID values, the iAnywhere Oracle driver would have returned invalid OUT parameters from calls to SQLColAttribute for the SQL_COLUMN_TYPE and SQL_DESC_DISPLAY_SIZE identifiers. As a workaround, the select statement could use ROWIDTOCHAR(ROWID) instead of ROWID. This has been fixed so that the calls to SQLColAttribute will now describe the column in the result set as a SQL_WCHAR of length 18.



CR:631475
CR Number:   631475
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 2543 07 Jun 2010 Fixed
11.0.1 2445 07 Jun 2010 Fixed
10.0.1 4080 07 Jun 2010 Fixed
12.0.1 2932 20 Sep 2010 Fixed
Description
Calls to some system procedures may have caused an server crash if null arguments were used. This has been fixed.



CR:631479
CR Number:   631479
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 2478 07 Jun 2010 Fixed
Description
Spatial methods could have been used in queries in contexts that should not have been allowed, and no error was given. Instead, an invalid answer was returned.



For example, the following query was permitted while it should be rejected:



select count(*), geometry.ST_Envelope()

from ( select row_num, new ST_Point( row_num, row_num, 0 ) geometry from rowgenerator ) D



This has been fixed.



CR:631482
CR Number:   631482
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.0 2543 07 Jun 2010 Fixed
12.0.1 2932 20 Sep 2010 Fixed
Description
On Linux systems, the main DBConsole window would still have been active when the initial "Connect" window was displayed. This would have allowed two "Connect" windows to be open at the same time; the subsequent behavior was not well-defined. This has been fixed so that the main window is now not active when the "Connect" window is open.



CR:631484
CR Number:   631484
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 2478 07 Jun 2010 Fixed
11.0.1 2445 07 Jun 2010 Fixed
11.0.0 1654 07 Jun 2010 Fixed
10.0.1 4107 03 Aug 2010 Fixed
Description
Execution of an ALTER TABLE statement, could have corrupted the table after deleting and committing some rows from it. This has now been fixed.



CR:631493
CR Number:   631493
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 2543 07 Jun 2010 Fixed
12.0.1 2932 20 Sep 2010 Fixed
Description
Clicking a variable name, after clicking the "Variables" button in the Remote Task wizard or property sheet, would have incorrectly resulted in a beep. Now, clicking the variable name inserts the variable name into the "SQL Condition" field.



CR:631525
CR Number:   631525
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 2479 07 Jun 2010 Fixed
11.0.1 2447 07 Jun 2010 Fixed
Description
If a cursor was opened over a query containing a call to the system procedures sa_rowgenerator() or sa_reserved_words(), and the cursor was moved forward and backwards, the server could have returned inconsistent results. The scrolling could have happened implicitly as a result of prefetch and re-fetching columns (for example, using GET DATA). This has been fixed.



CR:631633
CR Number:   631633
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 2544 08 Jun 2010 Fixed
12.0.1 2936 20 Sep 2010 Fixed
Description
The width of the "Search" field in the Deploy Remote Task wizard could have been so small that the component was unusable. This did not happen on all computers, and was dependent on which font (and size) the computer was configured to use. This has been fixed.



CR:631640
CR Number:   631640
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 2544 08 Jun 2010 Fixed
11.0.1 2447 08 Jun 2010 Fixed
12.0.1 2936 20 Sep 2010 Fixed
Description
In very rare cases, the server could have crashed if a database shutdown request was received at the same time that an active connection on the same database executed an external environment call. This problem has now been fixed.



CR:631643
CR Number:   631643
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
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
10.0.1 4084 16 Jun 2010 Fixed
12.0.1 2944 20 Sep 2010 Fixed
Description
Changes made for Engineering case 585456 caused the queue lengths in the Utilization Graph of the MobiLink Monitor, the RAW_TCP_STAGE_LEN, STREAM_STAGE_LEN, HEARTBEAT_STAGE_LEN, CMD_PROCESSOR_STAGE_LEN metrics printed by the -ppv option, and the queue lengths available in the SQL Anywhere Monitor, to possibly have been reported as larger than they actually were. These issues have been fixed.



CR:631647
CR Number:   631647
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 2544 07 Jun 2010 Fixed
12.0.1 2936 20 Sep 2010 Fixed
Description
On Linux systems, opening a window to view a long column value could have caused increased CPU usage, or could have caused dbisql to crash. This problem was intermittent, and depended on how busy the system was when the window was opened. This has been fixed.



CR:631669
CR Number:   631669
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 2544 07 Jun 2010 Fixed
12.0.1 2936 20 Sep 2010 Fixed
Description
Attempting to deploy a remote task to a consolidated database to which connection was not possible wou8ld have resulted in an assertion failure message. This has been fixed so now an error message is displayed saying that the connection failed.



CR:631672
CR Number:   631672
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 2544 08 Jun 2010 Fixed
12.0.1 2936 20 Sep 2010 Fixed
Description
In the Create MobiLink Agent wizard, if creating agents from a file was elected and the file was previewed, then a different file was selected, the preview page was not updated to show all of the agent names in the new file. This has been fixed.



CR:631731
CR Number:   631731
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   11.0.1
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
12.0.1 2946 20 Sep 2010 Fixed
Description
When starting the MobiLink Monitor with the -o or -c command line options, the result of the session should have been saved when the MobiLink server terminated, or the user manually disconnected from the MobiLink server. In the latter case, the output was not being saved and the Monitor was not shutting down. This has now been fixed.



CR:631733
CR Number:   631733
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
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 2451 17 Jun 2010 Fixed
10.0.1 4085 17 Jun 2010 Fixed
12.0.1 2945 20 Sep 2010 Fixed
Description
When connecting the MobiLink Monitor to a MobiLink server, any authentication error resulted in a poor error message from the Monitor, like:

"Got unexpected data when receiving authentication result. Check version of MobiLink server (opcode=0)"



This has been fixed to provide more information on the problem. The most common authentication error is now:

"Invalid userid or password (auth_status=NNNN)"



Other errors, for example due to an expired password, are similar.



CR:631774
CR Number:   631774
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 2100 08 Jun 2010 Fixed
11.0.1 2448 08 Jun 2010 Fixed
Description
The server could have crashed if lock contention was high. This has been fixed.



CR:631777
CR Number:   631777
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 2544 08 Jun 2010 Fixed
12.0.1 2937 20 Sep 2010 Fixed
Description
The Command Editor was inadvertently shown after clicking "Select All" while a tab other than "Commands" was selected for a deployed remote task. This has been fixed.



CR:631781
CR Number:   631781
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 2544 08 Jun 2010 Fixed
11.0.1 2448 08 Jun 2010 Fixed
10.0.1 4081 08 Jun 2010 Fixed
12.0.1 2937 20 Sep 2010 Fixed
Description
The text completer could have failed to suggest column names at the end of a dotted expression if the SQL statement spanned more than one line. For example, if the completer was opened at the end of the following statement:

SELECT * FROM customers C

WHERE C.



it should have suggested the columns in the "Customers" table, but it did not. This has been fix so that now it does.



CR:631797
CR Number:   631797
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 2543 08 Jun 2010 Fixed
11.0.1 2448 08 Jun 2010 Fixed
12.0.1 2932 20 Sep 2010 Fixed
Description
If a column CHECK constraint was defined using references to other columns, it was not being handled as a table CHECK constraint. This has been fixed.



CR:631798
CR Number:   631798
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 2544 08 Jun 2010 Fixed
12.0.1 2937 20 Sep 2010 Fixed
Description
The Procedure Browser window could have crashed if there were no procedures listed, and the mouse was moved over the empty list. This has been fixed.



CR:631800
CR Number:   631800
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 2544 08 Jun 2010 Fixed
12.0.1 2937 20 Sep 2010 Fixed
Description
Queries involving spatial predicates ST_Intersects or ST_IntersectsRect would have missed certain optimization oppotunities when operating over small geometries, or geometries with minimal surface area. This has been fixed. For example, performance of the following query was likely to improve as a result of this change:

select geometry

from table_containing_ST_Curves

where geometry.ST_IntersectsRect( new ST_Point( 0, 0 ), new ST_Point( 10, 10 ) ) = 1;



CR:631890
CR Number:   631890
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.0 2549 05 Jul 2010 Fixed
11.0.1 2459 05 Jul 2010 Fixed
9.0.2 3972 05 Jul 2010 Fixed
12.0.1 2959 20 Sep 2010 Fixed
Description
If an outer join had a materializing operator on the null-supplying side (for example a work table or a sort), then the performance could have been slower than it could have been because expressions from the tables under the null-supplying side were materialized when they were not needed above the join.



Also, the server could have crashed while executing a plan with an outer join if the null-supplying side contained an IN-list with either NUMERIC or string values.



These problems have now been fixed.



CR:631897
CR Number:   631897
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2544 09 Jun 2010 Fixed
11.0.1 2448 09 Jun 2010 Fixed
10.0.1 4082 09 Jun 2010 Fixed
12.0.1 2938 20 Sep 2010 Fixed
Description
In extremely rare timing dependent cases, if a communication error occurred on a connection with the dedicated_task option set in a mirroring configuration, the server could have crashed, asserted or hung. The fix for Engineering case 628436 missed this situation, which has now been fixed.



CR:631904
CR Number:   631904
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 2544 09 Jun 2010 Fixed
11.0.1 2448 09 Jun 2010 Fixed
12.0.1 2938 16 Sep 2010 Fixed
Description
If a server or database was started with a space in the name, then attempting to start external environments would have failed. This problem is specific to servers running on Windows based systems, and has now been fixed..



CR:631946
CR Number:   631946
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2545 18 Jun 2010 Fixed
11.0.1 2452 18 Jun 2010 Fixed
12.0.1 2946 16 Sep 2010 Fixed
Description
An error on startup of the MobiLink server on Mac OS X systems, would have displayed text that was prefixed by random characters and/or yellow highlighting. This has been corrected.



CR:632040
CR Number:   632040
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 2544 14 Jun 2010 Fixed
11.0.1 2448 14 Jun 2010 Fixed
10.0.1 4082 14 Jun 2010 Fixed
12.0.1 2938 16 Sep 2010 Fixed
Description
On 64-bit systems, it was possible for the JDBC driver to crash if some statement attributes were queried. This has now been fixed.



CR:632048
CR Number:   632048
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 2544 14 Jun 2010 Fixed
11.0.1 2449 14 Jun 2010 Fixed
12.0.1 2939 16 Sep 2010 Fixed
Description
If a view or derived table was used on the null-supplying side of an outer join it was possible for the expression to return a non-NULL value for a row of the view that should have been null-supplied. This would have occurred if one of the view columns contained one of the following expressions:

- user-defined function

- argn

- http_header

- http_response_header

- http_variable

- isdate

- isnumeric

- next_connection

- next_database

- next_http_header

- next_http_response_header

- next_http_variable

- next_soap_header

- patindex

- soap_header

- stuff



For example, the following queries would have incorrectly returned a non-NULL value for the column "b" of the derived table "D":



select *

from rowgenerator left join ( select dummy_col , argn( 1, 137, dummy_col ) b from sys.dummy ) D on 1=0

where row_num=1



select *

from rowgenerator left join ( select dummy_col , isnumeric( dummy_col ) b from sys.dummy ) D on 1=0

where row_num=1



This has been fixed.



CR:632050
CR Number:   632050
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 2544 14 Jun 2010 Fixed
11.0.1 2449 14 Jun 2010 Fixed
10.0.1 4082 15 Jun 2010 Fixed
12.0.1 2939 20 Sep 2010 Fixed
Description
If a Java external environment had been started for a particular database, and a connection on that database accidentally attempted to drop the SYS.DUMMY table, then the connection would have hung instead of giving the expected "permission denied" error. This problem has now been fixed.



Note that this problem does not exist for external environment other than Java.



CR:632174
CR Number:   632174
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.0 2544 14 Jun 2010 Fixed
11.0.1 2449 14 Jun 2010 Fixed
12.0.1 2940 20 Sep 2010 Fixed
Description
The Foreign Key wizard could have caused Sybase Central to crash when creating a second

foreign key on a table, if the creation of the first foreign key on the table had automatically added a new column to the foreign table. This has been fixed.



CR:632177
CR Number:   632177
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 2544 14 Jun 2010 Fixed
11.0.1 2449 14 Jun 2010 Fixed
10.0.1 4083 14 Jun 2010 Fixed
12.0.1 2940 20 Sep 2010 Fixed
Description
The text completer would not have suggested any names following a string of the form "owner.partialTableName" if "owner" was the same as "partialTableName". This would have occurred when trying to complete the name of a system table, e.g.:

SELECT * FROM sys.sys



This problem would have affected text completion in SELECT, DELETE, and UPDATE statements and has now been fixed.



CR:632219
CR Number:   632219
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Windows 2000
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2582 29 Mar 2011 Fixed
Description
The MobiLink server running in a server farm against the cluster edition of a consolidated database, would have shutdown too quickly when the node the MobiLink server was connecting to was killed or shut down. This problem has been fixed. When the MobiLink server detects the database connection unusable, it will now attempt to re-establish a connection and pause for 1 second before each retry. By default, the number of retries is 3. Therefore, it would allow the ODBC driver to switch the MobiLInk server database connections to another node within 3 seconds. If the failover of the consolidated database takes more than 3 seconds, the MobiLink server command line option -cr <num> can be used to change the number of retries.



CR:632314
CR Number:   632314
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 2483 14 Jun 2010 Fixed
Description
When the server is started with no command line arguments, a "server startup options" dialog is presented which includes a "Browse..." button to choose the database file. When Browse... was clicked, a non-modal file-open dialog was launched which meant that the "server startup options" dialog could be closed while the file-open dialog was still open. The file-open dialog is now modal and must be closed first.



CR:632315
CR Number:   632315
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 2482 14 Jun 2010 Fixed
11.0.1 2450 14 Jun 2010 Fixed
10.0.1 4084 14 Jun 2010 Fixed
Description
The START JAVA statement would have failed when the server was started through the GUI (DBLauncher) on Mac OS X 10.6. This has been fixed. Servers started via the command line interface (Terminal.app) do not have this problem.



CR:632340
CR Number:   632340
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 2545 15 Jun 2010 Fixed
12.0.1 2943 20 Sep 2010 Fixed
Description
Executing a LOAD TABLE statement on Mac OSX systems would have failed with the error -134 (feature not implemented). This has been fixed.



CR:632342
CR Number:   632342
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 2547 14 Jun 2010 Fixed
11.0.1 2456 14 Jun 2010 Fixed
10.0.1 4089 14 Jun 2010 Fixed
12.0.1 2954 20 Sep 2010 Fixed
Description
Under rare circumstances, the server may have hung while diagnostic tracing was enabled. This has been fixed.



CR:632353
CR Number:   632353
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 2552 12 Jul 2010 Fixed
11.0.1 2464 12 Jul 2010 Fixed
10.0.1 4097 12 Jul 2010 Fixed
12.0.1 2968 20 Sep 2010 Fixed
Description
If the server acting as the primary server in a mirroring system was shut down at the same time as it lost quorum due to a dropped mirror connection, the database on the primary could have been improperly checkpointed, resulting in a failure to recover on the next startup. Also, if a mirror server was starting at the same time the primary server was stopping or restarting, the mirror server could have received log operations that were not written on the primary. This would have resulted in an "incompatible files" message the next time the mirror connected to the primary, and would have forced the database and log to be manually recopied. Both of these problems have now been fixed.



CR:632359
CR Number:   632359
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2545 15 Jun 2010 Fixed
11.0.1 2450 15 Jun 2010 Fixed
12.0.1 2943 20 Sep 2010 Fixed
Description
For 11.0.1, ECC curve support for MobiLink end-to-end encryption has been reduced to the same 7 ECC curves supported by the createcert and createkey utilities and by SA's TLS support.



For 12.0.0, ECC curve support for end-to-end encryption, the createcert and createkey utilities, and for the TLS protocol for both MobiLink and SA, has been extended to support the 15 curves recommended by NIST:

sect163k1 sect283k1 sect571k1 secp256r1

sect163r2 sect283r1 sect571r1 secp384r1

sect233k1 sect409k1 secp192r1 secp521r1

sect233r1 sect409r1 secp224r1





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

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。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------