远程Sybase数据库技术支持,联系手机:13811580958,QQ:289965371!

 

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

如有问题,请联系我!

QQ :289965371 点击这里给我发消息
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:636557
CR Number:   636557
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2562 03 Aug 2010 Fixed
11.0.1 2474 03 Aug 2010 Fixed
10.0.1 4106 03 Aug 2010 Fixed
12.0.1 2989 23 Sep 2010 Fixed
Description
Attempting to delete properties and transmission rules from the clients defined within a Server Message Store, could have failed either with or without an error message. This has been fixed.



CR:636558
CR Number:   636558
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 2564 03 Aug 2010 Fixed
11.0.1 2476 03 Aug 2010 Fixed
12.0.1 2994 23 Sep 2010 Fixed
Description
All of the items in the "File" menu (and others) would have been disabled after clicking a source control-related menu item, if that source control action failed. This would have occurred when using the "custom" source control option. This has been fixed.



CR:636565
CR Number:   636565
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 2562 29 Jul 2010 Fixed
12.0.1 2988 23 Sep 2010 Fixed
Description
The TCP/IP protocol option table on the "Network" tab of the "Connect" dialog could have become disabled under some circumstances. The table was being disabled only if a parameter was entered on the "Network" or "Advanced Options" tabs, the tabs were hidden by clicking the "Advanced" button, then clicking "Connect" or "Tools/Test Connection" and declining to use the hidden connection parameters. This has been fixed, now the table is never disabled.



CR:636568
CR Number:   636568
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2562 29 Jul 2010 Fixed
12.0.1 2988 23 Sep 2010 Fixed
Description
The QAManagerBase.close method could have hung when using a SQL Anywhere database as a message bus (ie. the message store is initialized with qaagent -sil). This has been fixed.



CR:636572
CR Number:   636572
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 2562 03 Aug 2010 Fixed
11.0.1 2474 03 Aug 2010 Fixed
10.0.1 4106 03 Aug 2010 Fixed
12.0.1 2989 23 Sep 2010 Fixed
Description
If an application executed a remote query, and the query involved an IF or CASE expression in the select list, then the query would always have been processed in partial or no passthru mode, even if there was only one remote server involved. This restriction has now been relaxed such that remote queries containing IF or CASE expressions in the select list will now be executed in full passthru whenever possible, but only if the remote server is another SA server.



CR:636651
CR Number:   636651
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2571 19 Aug 2010 Fixed
11.0.1 2482 19 Aug 2010 Fixed
10.0.1 4111 20 Aug 2010 Fixed
12.0.1 3010 23 Sep 2010 Fixed
Description
The use of START AT or FIRST in a subquery may have resulted in incorrect results. This was corrected.



CR:636654
CR Number:   636654
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 2562 29 Jul 2010 Fixed
Description
The Validation utility, or a VALIDATE INDEX statement, may have failed spuriously when run on indexes with 33 to 64 columns, if any columns beyond the 32nd were sorted in ascending order. This has been fixed.



CR:636655
CR Number:   636655
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 2562 03 Aug 2010 Fixed
12.0.1 2989 23 Sep 2010 Fixed
Description
The server may have crashed when defining foreign keys that auto-created columns in the referencing table. This has been fixed.



CR:636660
CR Number:   636660
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 2562 03 Aug 2010 Fixed
11.0.1 2474 03 Aug 2010 Fixed
10.0.1 4106 03 Aug 2010 Fixed
12.0.1 2989 23 Sep 2010 Fixed
Description
SQL Anywhere web server required that the last boundary of a multi-part/formdata HTTP request be terminated with a carriage-return line-feed. This restriction has now been relaxed, the server will now accept the last boundary as valid even if it is not terminated with a CR/LF.



CR:636664
CR Number:   636664
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 2565 04 Aug 2010 Fixed
12.0.1 2995 23 Sep 2010 Fixed
Description
When connected to a 10.x or 11.x database running on a 12.x server, selecting the Procedures & Functions folder in the tree would have caused Sybase Central to crash if objects owned by the user dbo were not being filtered out. This has been fixed.



CR:636694
CR Number:   636694
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2566 03 Aug 2010 Fixed
12.0.1 2990 23 Sep 2010 Fixed
Description
The Host parameter (hostname:port) was not being written, or updated, in the registry entry for a DSN created using the ODBC administrator and the "Start and connect to a database running on another computer" option on the Login tab. This has now been corrected.



CR:636715
CR Number:   636715
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2565 10 Aug 2010 Fixed
11.0.1 2477 10 Aug 2010 Fixed
10.0.1 4109 10 Aug 2010 Fixed
12.0.1 2996 24 Sep 2010 Fixed
Description
The iAS ODBC driver for Oracle would have returned a wrong value for a parameter indicator through the ODBC API, SQLBindparameter( ..., c_type, ..., param_type, ..., &indicator ), if it was called with the following parameters:

1) the C data type of the parameter was SQL_C_WCHAR or SQL_C_CHAR

2) the type of parameter was SQL_PARAM_INPUT_OUTPUT, but the corresponding parameter used in the SQL statement was input-only



Due to this problem, the data for the user-defined named parameters in the MobiLink server may have been truncated after each use when the named parameter was defined as {ml u.varname} and the parameter used in the SQL statement was input-only. This has now been fixed.



CR:636767
CR Number:   636767
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3979 03 Aug 2010 Fixed
Description
In exceptionally rare conditions, the server may have crashed when expanding a very large view definition that contained a UNION, INTERSECT, or EXCEPT query node and the available cache was too small. This has been fixed. The server will now return a SQLSTATE_SYNTACTIC_LIMIT error in these cases.



CR:636770
CR Number:   636770
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 2563 03 Aug 2010 Fixed
11.0.1 2474 03 Aug 2010 Fixed
12.0.1 2990 24 Sep 2010 Fixed
Description
If the database option Chained was set to OFF, upgrading the database would have failed with the error: "COMMIT/ROLLBACK not allowed within atomic operation". This has been fixed by temporarily setting the option to ON within the upgrade script when needed.



CR:636780
CR Number:   636780
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 2563 03 Aug 2010 Fixed
12.0.1 2990 24 Sep 2010 Fixed
Description
If a NO MINVALUE clause was explicitly specified in a CREATE SEQUENCE or ALTER SEQUENCE statement, the minvalue for the sequence would have been set at zero, instead of the documented default, 1. If a NO MAXVALUE clause was explicitly specified, the maxvalue would have been set to zero, instead of the default, 2^63-1. In both cases, the problem can be worked around by simply removing the NO MINVALUE or NO MAXVALUE clause if the default values are desired. This has now been corrected.



CR:636801
CR Number:   636801
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3038 16 Sep 2010 Fixed
12.0.0 2582 16 Sep 2010 Fixed
11.0.1 2495 16 Sep 2010 Fixed
10.0.1 4122 16 Sep 2010 Fixed
Description
Unloading a version 9 database with a table with named primary key constraint could have failed if the primary key was referenced by an index hint in a view. This has been fixed.



Also, unloading a version 10 or later database containing a table with a primary key index that had been renamed would have failed to preserve the new name for the index. This has been fixed.



CR:636807
CR Number:   636807
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 2564 03 Aug 2010 Fixed
12.0.1 2994 24 Sep 2010 Fixed
Description
The MobiLink Agent for central administration of remotes could have allowed a regular task to run concurrently with a high priority task. This was incorrect, since a high priority task is supposed to run when no other tasks are running and exclude other tasks from starting while it is present on the agent. The incorrect behavior would only have occurred if at least two regular tasks were running concurrently, and then a high priority task was deployed to the agent. This has been fixed.



CR:637026
CR Number:   637026
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 2564 03 Aug 2010 Fixed
11.0.1 2476 03 Aug 2010 Fixed
12.0.1 2994 23 Sep 2010 Fixed
Description
Characters from a charset other than the one the computer usually operates in could have been displayed as boxes in the text above the tabs in the right pane. This has been fixed.



CR:637036
CR Number:   637036
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2564 03 Aug 2010 Fixed
12.0.1 2994 24 Sep 2010 Fixed
Description
In the ODBC Administrator's datasource configuration dialog, the encryption field should have been treated like a password field, displaying it as a collection of asterisks, but instead it was being displayed in plain text. This has been fixed.



CR:637037
CR Number:   637037
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 2562 03 Aug 2010 Fixed
11.0.1 2473 03 Aug 2010 Fixed
10.0.1 4106 03 Aug 2010 Fixed
9.0.2 3978 03 Aug 2010 Fixed
12.0.1 2988 24 Sep 2010 Fixed
Description
When a stored procedure was invoked through the Microsoft SQL Server Linked Server mechanism using an "EXEC" statement and specifying parameters, the call would have failed with a syntax error. The following is an example of a SQL Server query that is forwarded to a SQL Anywhere server:

SELECT * FROM openquery(SALINK, 'exec test_proc 1')



This problem has been fixed. When parameters are present in the SQL query, the statement is passed unchanged to the server. When no parameters are present, the OLE DB provider rewrites the "exec" statement using CALL and appends parameter marker place holders (in order to support ADO's ADODB.CommandTypeEnum.adCmdStoredProc).



CR:637047
CR Number:   637047
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 2564 04 Aug 2010 Fixed
12.0.1 2994 24 Sep 2010 Fixed
Description
The minimum width for the Plan Viewer window could have been less than 1024 pixels, and thus not completely visible on smaller monitors. This has been fixed.



CR:637049
CR Number:   637049
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 2564 04 Aug 2010 Fixed
12.0.1 2994 24 Sep 2010 Fixed
Description
In certain rare cases, the Connection List widget could have failed to populate. A race condition between the request for connection information and the establishment of a connection has been corrected.



CR:637057
CR Number:   637057
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.1 3053 20 Sep 2010 Fixed
12.0.0 2591 20 Sep 2010 Fixed
11.0.1 2502 20 Sep 2010 Fixed
Description
If the network connection between a primary server and a mirror server was temporarily broken, the primary server could have stopped sending updates to the mirror server. This has been fixed.



CR:637063
CR Number:   637063
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2564 04 Aug 2010 Fixed
12.0.1 2994 24 Sep 2010 Fixed
Description
During a soft shutdown, the MobiLink server did not stop accepting new requests. This has been fixed. Now, when a new request connects during shutdown, the server will abort the request and print a new error, -13074: "Aborting request that started during shutdown".



CR:637125
CR Number:   637125
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 2567 09 Aug 2010 Fixed
11.0.1 2478 09 Aug 2010 Fixed
10.0.1 4111 09 Aug 2010 Fixed
12.0.1 3000 24 Sep 2010 Fixed
Description
If an application executed a remote query that required the server to make a remote connection to another SA database, then there was a very rare chance that the server would have incorrectly failed the remote connection with the error: "unable to connect, server definition is circular". This problem has now been fixed.



CR:637146
CR Number:   637146
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 2564 04 Aug 2010 Fixed
11.0.1 2476 04 Aug 2010 Fixed
12.0.1 2994 24 Sep 2010 Fixed
Description
Two xml mapping files have been added to support SQL Server 2008 Integration Services:

- MSSqlToSA.xml --- mapping SQL Server 2008 data types to SA data types.

- SAToMSSql10.xml --- mapping SA data types to SQL Server 2008 data types.



These files will be installed to "%SA%\Assembly\V2" folders. The utility SetupVSPackage.exe will copy them to, or remove them from, the "%SQL Server 2008 Dir%\DTS\Binn" folder.



CR:637165
CR Number:   637165
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 2565 04 Aug 2010 Fixed
11.0.1 2476 04 Aug 2010 Fixed
12.0.1 2995 24 Sep 2010 Fixed
Description
The following defects related to the menu bar, which occurred only on Mac OS X systems, have now been fixed:

- The "Check for Software Updates" menu item was missing

- The text for submenus were indented more than was required

- There were a number of spurious separators at the end of certain menus.



CR:637169
CR Number:   637169
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2565 04 Aug 2010 Fixed
11.0.1 2476 04 Aug 2010 Fixed
10.0.1 4106 04 Aug 2010 Fixed
12.0.1 2994 28 Sep 2010 Fixed
Description
Starting with Visual Studio 2010, class libraries built with with the default project settings will no longer work with a MobiLink server running with its default CLR version. There are two workarounds for this:



1) Change the target Framework of the VS project.

When creating a new project, there is a drop down above the list of project types that contains ".NET Framework 4"; change this to ".NET Framework 2.0", ".NET Framework 3.0", or ".NET Framework 3.5". If a version 4 project has already been created, change the target framework by right-clicking on the project in the Solution Explorer, and selecting "Properties" in the context menu. The target framework can be set on the "Application" tab.燱hen changing the target framework, there is no longer access to .NET 4.0 features; to use newer features, use the next workaround.



2) Tell the MobiLink server to load the version 4 framework.

To do this, add -clrVersion=v4.0.30319 to the -sl dnet options. The "30319" is the specific build number of the framework installed and may be different on your machine. To find the correct version, look in the .NET install location, which is typically "c:\WINDOWS\Microsoft.NET\Framework\". The clrVersion to specify is the v4.0 sub-directory there.



CR:637174
CR Number:   637174
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 2565 05 Aug 2010 Fixed
11.0.1 2476 05 Aug 2010 Fixed
10.0.1 4109 05 Aug 2010 Fixed
12.0.1 2995 24 Sep 2010 Fixed
Description
If a file was inserted using the "Edit/Insert File" menu item, the file would have been locked by dbisql until dbisql was closed. If the Fast Launcher option was turned on, the file was locked until the Fast Launcher also shut down (which by default happens after 30 minutes of inactivity). Now, the file is unlocked as soon as its text has been added to the "SQL Statements" field.



CR:637200
CR Number:   637200
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 2565 05 Aug 2010 Fixed
12.0.1 2995 24 Sep 2010 Fixed
Description
If a user with DBA authority granted usage permissions on a sequence not owned by it to another user, that user with DBA authority could not have been dropped unless the permissions were also revoked; a foreign key violation error would have been reported. By contrast, permissions on other database objects granted by a user who is about to be dropped are revoked automatically. This has been fixed so that the necessary sequence permissions are also revoked automatically.



A workaround is to manually revoke any sequence permissions granted by the user about to be dropped, then re-grant them from a user that will not be dropped. The original grantor can then be dropped.



CR:637203
CR Number:   637203
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2567 10 Aug 2010 Fixed
11.0.1 2479 10 Aug 2010 Fixed
10.0.1 4111 10 Aug 2010 Fixed
12.0.1 3001 24 Sep 2010 Fixed
Description
The column alignment used by the OUTPUT statement for the FIXED file format was often inappropriate for the data type. In general, numbers should be right-aligned, while everything else is left-aligned. This has been fixed.



CR:637290
CR Number:   637290
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 2568 12 Aug 2010 Fixed
11.0.1 2480 12 Aug 2010 Fixed
12.0.1 3004 24 Sep 2010 Fixed
Description
On a machine with IPv6 enabled but not configured, the function property('TcpipAddresses') would have returned "(::):2638" as one of the addresses. This is the IPv6 INADDR_ANY address, and it is not useful to clients for making connections. If HTTP or HTTPS was in use, the functions property('HttpAddresess') and property('HttpsAddresses') would have had the same problem. This has been fixed so that now this address will no longer be listed.



CR:637309
CR Number:   637309
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 18 Aug 2010 Fixed
11.0.1 2489 18 Aug 2010 Fixed
10.0.1 4116 18 Aug 2010 Fixed
12.0.1 3024 24 Sep 2010 Fixed
Description
The MobiLink server could have crashed at the end of a version 9 or earlier synchronization request, or while processing the upload stream from a version 10 or later synchronization request.



Also, the MobiLink server was not able to distinguish between empty strings in varchar(8) or smaller columns, binary(16) or smaller values made of only 0s, the integer 0, and null values when filtering the download. This could have caused rows to be incorrectly filtered from the download. For example, if an empty string was uploaded in a row, and the only difference between a downloaded row and that uploaded row was that the empty string became null, the row would have been ommitted from the download and the remote would not have received that update.



These issues have been fixed.



CR:637313
CR Number:   637313
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 2567 10 Aug 2010 Fixed
12.0.1 3000 24 Sep 2010 Fixed
Description
When copying a number from a result set to the clipboard, the thousands separator was included in the copied number. This has been corrected so that the separator is removed.



CR:637326
CR Number:   637326
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 3073 19 Oct 2010 Fixed
12.0.0 2599 19 Oct 2010 Fixed
11.0.1 2512 19 Oct 2010 Fixed
Description
An error could have occurred when deploying a Synchronization Model for an ASE consolidated database when a synchronized table had a MONEY or SMALLMONEY column and conflict resolution was enabled for the table mapping. ASE would have reported the error "Can't specify a length or scale on type 'money'" when deployment tried to create a temporary table for conflict resolution, and incorrectly specified the length and scale for MONEY columns. This would also have occurred for a Microsoft SQL Server consolidated database with a synchronized table having a MONEY or SMALLMONEY column, and for an IBM DB2 consolidated database with a synchronized table having a LONG VARCHAR column. These problems have been fixed. Now the generated SQL does not specify length or scale for MONEY or SMALLMONEY columns with ASE and Microsoft SQL Server, or for LONG VARCHAR with IBM DB2.



CR:637333
CR Number:   637333
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2565 06 Aug 2010 Fixed
11.0.1 2477 06 Aug 2010 Fixed
10.0.1 4109 06 Aug 2010 Fixed
12.0.1 2996 24 Sep 2010 Fixed
Description
When using the ADO.NET Provider with a .NET Framework 4.0 Client Profile, Visual Studio 2010 generated some compile errors. This problem has been fixed.



CR:637336
CR Number:   637336
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 2572 23 Aug 2010 Fixed
11.0.1 2484 23 Aug 2010 Fixed
12.0.1 3012 24 Sep 2010 Fixed
Description
Dropping a text index used within a view could have caused the assertion failure message: "Unable to delete row from SYSTABLE". This could have happen when the view definition contained a CONTAINS predicated that could have be satisfied by the text index. This has been fixed. A workaround is to drop the view, then drop the text index.



CR:637340
CR Number:   637340
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 2571 09 Aug 2010 Fixed
11.0.1 2483 09 Aug 2010 Fixed
10.0.1 4111 09 Aug 2010 Fixed
12.0.1 3011 24 Sep 2010 Fixed
Description
If a Unix server was started with a server name longer than 32 bytes, shared memory connections to it may have been dropped. This has been fixed.



CR:637445
CR Number:   637445
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3051 28 Sep 2010 Fixed
Description
The splash screens for the SQL Anywhere Console utility (dbconsole), the MobiLink Monitor, and the SQL Anywhere Monitor contained program names that were always in English. These mane have now been localized.



CR:637446
CR Number:   637446
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 3314 30 Mar 2011 Fixed
Description
Exporting TIME values to a DB2 database with an OUTPUT USING statement in the Interactive SQL utility would have failed. This has been fixed.



CR:637447
CR Number:   637447
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3040 20 Sep 2010 Fixed
12.0.0 2584 20 Sep 2010 Fixed
11.0.1 2496 20 Sep 2010 Fixed
10.0.1 4123 20 Sep 2010 Fixed
Description
The ALT left cursor and ALT right cursor keys on Solaris systems control the desktop and cannot be used to view executed SQL statements. The get around this limitation, the keys used now for viewing previous and next SQL statements on Solaris systems are the keys CTRL-up cursor and CTRL-down cursor respectively.



CR:637453
CR Number:   637453
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)
11.0.1 2456 06 Aug 2010 Fixed
Description
With the changes for Engineering case 576252, support for SQL Anywhere Explorer and SQL Anywhere Toolbar was disabled for Visual Studio version 2010. Now, SQL Anywhere Explorer and SQL Anywhere Toolbar have been disabled for Visual Studio versions 2005 and 2008 as well.



CR:637456
CR Number:   637456
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 3278 24 Jan 2011 Fixed
12.0.0 2636 24 Jan 2011 Fixed
Description
Attempting to import NCHAR types from ASE using the INPUT statement or the Import Wizard, would have failed with the message "Cannot convert '' to a varbit". This has been fixed.



CR:637464
CR Number:   637464
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)
25 Mar 2011 Fixed
Description
As of version 10.0, the database server started accepting a number of new values for the request level logging option, SQL, PLAN, HOSTVARS, etc. The Console utility though still only allowed the older YES and NO values. This has now been corrected so that the Console utility now accepts these new values. These new options appear on the "Console" page in the "Options" dialog.



Note that the logging options are presented as if they are separate, independent options, even though there are underlying dependencies between some of the them. For example, logging triggers also logs procedures and SQL. This is a server behavior rather than a Console utility behavior.



CR:637476
CR Number:   637476
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3324 07 Apr 2011 Fixed
Description
Importing data from a database that was not a SQL Anywhere or UltraLite database into an UltraLite database, using the Interactive SQL INPUT statement or the Import Wizard, could have failed. This would have occurred if a new table was to be created for the imported data and the data contained one or more INTEGER columns. This has been fixed.



CR:637481
CR Number:   637481
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3018 17 Jan 2011 Fixed
12.0.0 2574 17 Jan 2011 Fixed
11.0.1 2486 17 Jan 2011 Fixed
Description
UltraLite client message stores created from Sybase Central did not have their store IDs set, even if a store ID was given in the Client Message Store wizard. Lack of the store ID would have caused a warning message to be displayed when attempting to disconnect from the database and stop the agent from Sybase Central. This has been fixed.



CR:637487
CR Number:   637487
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2566 09 Aug 2010 Fixed
12.0.1 2997 24 Sep 2010 Fixed
Description
In very rare cases, the MobiLink server would have generated the error: 'Function sequence error' and aborted the synchronization request, when an upload stream contained spatial data. This problem has now been fixed.



CR:637505
CR Number:   637505
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 2567 10 Aug 2010 Fixed
11.0.1 2478 10 Aug 2010 Fixed
12.0.1 3000 24 Sep 2010 Fixed
Description
Opening the property sheet for an article that referenced a subset of a table's columns and clicking the Cancel button to close it, would have caused the subset of columns to not have been displayed the next time the property sheet was opened. Pressing F5, or selecting View -> Refresh in the main Sybase Central window, was required to get the property sheet to correctly display the set of columns in the article. This has been fixed.



CR:637620
CR Number:   637620
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 2567 09 Aug 2010 Fixed
11.0.1 2478 10 Aug 2010 Fixed
10.0.1 4111 10 Aug 2010 Fixed
12.0.1 3000 28 Sep 2010 Fixed
Description
In rare circumstances, the server could have crashed while handling multiple TLS connections. This has been fixed.



CR:637621
CR Number:   637621
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 2567 09 Aug 2010 Fixed
12.0.1 3000 24 Sep 2010 Fixed
Description
If an application executed an INSERT statement that contained multiple VALUES lists, and the insert statement involved a remote table, then the server would have failed the INSERT with a "remote server not capable" error. The server will now push the multiple VALUES lists to the remote server, provided the remote server is another SA server and the INSERT statement can be processed in full passthru mode. It should be noted that if the remote SA server is an older version which does not support inserts with multiple values lists, then the remote SA will return a syntax error.



CR:637725
CR Number:   637725
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 2567 10 Aug 2010 Fixed
11.0.1 2479 10 Aug 2010 Fixed
10.0.1 4111 10 Aug 2010 Fixed
12.0.1 3001 24 Sep 2010 Fixed
Description
The Available objects list would have been empty when creating SQL Server Integration Services data source view. This problem has been fixed.



CR:637743
CR Number:   637743
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2567 11 Aug 2010 Fixed
11.0.1 2479 11 Aug 2010 Fixed
10.0.1 4111 11 Aug 2010 Fixed
12.0.1 3001 24 Sep 2010 Fixed
Description
Calls to SQLGetTypeInfo() would have returned the wrong UNSIGNED_ATTRIBUTE column value for TINYINT. The TINYINT datatype is an unsigned type so the column should have contained a 1 rather than a 0. This problem has been fixed so that the UNSIGNED_ATTRIBUTE column result now agrees with the result returned by SQLColAttribute(SQL_DESC_UNSIGNED) for a TINYINT column.



CR:637744
CR Number:   637744
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2567 23 Aug 2010 Fixed
12.0.1 3002 24 Sep 2010 Fixed
Description
Options set on the Advanced page of the ODBC administrator could not have been deleted. Options could have been changed, but to delete them it was necessary to recreate the ODBC datasource, or remove the options manually from the registry. This has now been fixed.



CR:637745
CR Number:   637745
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2569 11 Aug 2010 Fixed
11.0.1 2480 11 Aug 2010 Fixed
10.0.1 4111 11 Aug 2010 Fixed
9.0.2 3981 11 Aug 2010 Fixed
12.0.1 3005 24 Sep 2010 Fixed
Description
If an application executed a remote statement, and the remote statement required the server to execute the statement in either partial or no passthrough mode, then there was a chance the server would have crashed when the statement was overly complex, or if the server cache was exhausted. This problem has now been fixed by reporting an error in this situation.



CR:637769
CR Number:   637769
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 2567 11 Aug 2010 Fixed
11.0.1 2479 11 Aug 2010 Fixed
12.0.1 3002 24 Sep 2010 Fixed
Description
As part of the fix for Engineering case 632873, a problem was introduced where, under rare circumstances, an IMMEDIATE text index could have become corrupt. The corruption may manifest itself by preventing some documents from being found by matching queries. This has been fixed, but it is recommended that IMMEDIATE text indexes that are under heavy contention be recreated following applying this fix.



CR:637861
CR Number:   637861
Product Name:   SQL Anywhere Monitor
Product Component:   Monitor Migrator
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2568 11 Aug 2010 Fixed
12.0.1 3003 24 Sep 2010 Fixed
Description
When migrating data from a previous SQL Anywhere Monitor install while applying an EBF on Linux systems, it was possible that errors arising during the migration process would not have been reported. This has been fixed.



CR:637874
CR Number:   637874
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 2568 12 Aug 2010 Fixed
11.0.1 2479 12 Aug 2010 Fixed
10.0.1 4111 12 Aug 2010 Fixed
12.0.1 3003 24 Sep 2010 Fixed
Description
When computing the VARIANCE, VAR_SAMP, VAR_POP, STDDEV, STDDEV_SAMP, or STDDEV_POP functions, the server could have incorrectly returned a negative value or NULL. This could have happened if the data was in a non-exact numeric column (that is, of type DOUBLE or FLOAT) and there was extremely little actual variance across the values. It most likely could only have happened when all the values were exactly the same. This has now been fixed.



A workaround is to adjust the value over which the variance function is computed so that a tiny amount of variance is introduced. For example, instead of:

SELECT VARIANCE(mycolumn) FROM mytable

use:

SELECT VARIANCE(mycolumn + 0.00000001*myprimarykey) FROM mytable



CR:637877
CR Number:   637877
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 2568 13 Aug 2010 Fixed
11.0.1 2480 13 Aug 2010 Fixed
12.0.1 3004 24 Sep 2010 Fixed
Description
When completing column names for tables that have aliases, the alias is now displayed in the completion list, and the alias is now used in the completed text. For example, if the completer is opened after "Comp" in the following statement:

select Comp from customers C1, customers C2



the completer will include "Company (C1 - customers)" and "Company (C2 - customers)". If the second item is selected, the completed text will read:

select C2.CompanyName from customers C1, customers C2



Previously, "Comp" would be replaced by "CompanyName", which was ambiguous.



CR:637881
CR Number:   637881
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 25 Aug 2010 Fixed
11.0.1 2485 25 Aug 2010 Fixed
10.0.1 4111 25 Aug 2010 Fixed
9.0.2 3982 25 Aug 2010 Fixed
12.0.1 3017 24 Sep 2010 Fixed
Description
When executing a remote query that required partial or no passthru processing, and the query made heavy usage of aliases, then the server could have incorrectly returned error "-890 statement size or complexity exceeds server limits". This problem has now been fixed and the -890 error will now only be returned if the statement size or complexity really does exceed server limits.



CR:637897
CR Number:   637897
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 2583 12 Aug 2010 Fixed
11.0.1 2495 12 Aug 2010 Fixed
10.0.1 4122 12 Aug 2010 Fixed
12.0.1 3038 16 Sep 2010 Fixed
Description
On SUSE 10 systems, the server could have failed to start a database if the database file was mounted on an NFS share. The error given would be something like:

"Error: Database cannot be started -- /mnt/share/demo.db is not a database"



This has now been fixed.



CR:637901
CR Number:   637901
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2568 12 Aug 2010 Fixed
12.0.1 3003 24 Sep 2010 Fixed
Description
The Interactive SQL utility (dbisql) could have failed to connect to an UltraLite database specified on the command line (with -c) under the following conditions:

- the UltraLite engine (uleng12) was started from one directory and dbisql was launched from another

- the -c option to dbisqlL specified a relative path



The result would have been that dbisql would have displayed the connection dialog, when it should have immediately connected to the database. This has been fixed.



CR:637909
CR Number:   637909
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2570 17 Aug 2010 Fixed
11.0.1 2482 17 Aug 2010 Fixed
10.0.1 4111 17 Aug 2010 Fixed
12.0.1 3009 24 Sep 2010 Fixed
Description
Executing a stored procedure and fetching the result set would have thrown the exception "Index was outside the bounds of the array" if the stored procedure selects results from a local temporary table with blob columns. The provider was determining the row buffer length prior to opening the cursor, this has been corrected so that it is done after the cursor has been opened.



CR:637988
CR Number:   637988
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 2568 13 Aug 2010 Fixed
11.0.1 2480 13 Aug 2010 Fixed
10.0.1 4111 13 Aug 2010 Fixed
12.0.1 3004 24 Sep 2010 Fixed
Description
If an incorrect password was supplied in the saldap.ini file, the server could have hung when attempting to register with LDAP. Also, SA client libraries could have hung when using LDAP to find servers. This has been fixed.



CR:637991
CR Number:   637991
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 2568 12 Aug 2010 Fixed
11.0.1 2480 12 Aug 2010 Fixed
12.0.1 3004 24 Sep 2010 Fixed
Description
The Interactive SQL utility could have crashed when completing a DELETE statement, if a table alias was given. This has been fixed.



CR:638001
CR Number:   638001
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 2568 12 Aug 2010 Fixed
11.0.1 2480 12 Aug 2010 Fixed
12.0.1 3004 24 Sep 2010 Fixed
Description
Attempting to start an external environment on a server machine that was overloaded or incorrectly configured, could have resulted in the error "External environment could not be started, 'main thread' not found". Quite often this problem was due to the external environment failing to establish a connection with the server within a specific timeout, either due to the server (or server machine) being overloaded, or due to incorrect configuration. The error message has now been changed to give a more meaningful reason for the failed START EXTERNAL ENVIRONMENT request.



CR:638003
CR Number:   638003
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2568 13 Aug 2010 Fixed
12.0.1 3003 24 Sep 2010 Fixed
Description
A C/C++/Objective-C UltraLite application using a static runtime library would have always linked in the synchronization code, even if the application didn't use, or didn't enable, synchronization. On Mac OS X and iPhone, database applications not using synchronization would have still needed to link to the core, security, and network frameworks. This has been corrected so that only applications which enable synchronization will now include synchronization code. On Mac OS X and iPhone, the core, security, and network frameworks are now only required when using synchronization. As a consequence of this change, synchronization must be enabled to use the ML_GET_SERVER_NOTIFICATION() SQL function.



CR:638011
CR Number:   638011
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2568 13 Aug 2010 Fixed
12.0.1 3004 27 Sep 2010 Fixed
Description
In certain circumstances it was possible that importing SQL Anywhere resources could have failed to report some errors, making it appear that the import was successful when in reality, one or more resources failed to import. This has been fixed. An error will now correctly be reported.



CR:638021
CR Number:   638021
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 2568 13 Aug 2010 Fixed
12.0.1 3004 27 Sep 2010 Fixed
Description
When the legacy option "Pressing the Esc key clears SQL Statements..." was on, and the Text Completer was open, pressing Esc would have both closed the completer and cleaed the SQL Statements field. Now, it just closes the completer.



CR:638147
CR Number:   638147
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 2570 17 Aug 2010 Fixed
11.0.1 2480 17 Aug 2010 Fixed
12.0.1 3009 24 Sep 2010 Fixed
Description
1. SyncParms.setAuthenticationParms( ",a,,b," ) was interpreted as only having two authentication parameters ("a" and "b") when it should be interpreted as 5 parameters ( "", "a", "", "b" and "" ). This has been fixed. Blank parameters are now correctly processed.



2. The documentation states that only the first 128 characters of each parameter are sent to the MobiLink server, but no limit was actually enforced. This resulted in corrupt data being sent to the MobiLink server if a value was excessively large. This has been fixed. Extremely large strings (greater than 21K characters) are now truncated prior to sending to the MobiLink server, and the MobiLink server will however report an error now if the authentication parameters' lengths exceed the server's limit of 128 bytes.



CR:638148
CR Number:   638148
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 2569 16 Aug 2010 Fixed
12.0.1 3005 24 Sep 2010 Fixed
Description
When running on systems other than Linux, if the Relay Server State Manager (rshost) was not running and a client made a request invoking the client module, this request could have crashed the module. This has been fixed.



CR:638153
CR Number:   638153
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 2480 16 Aug 2010 Fixed
Description
If none of the $SATMP, $TMP, $TMPDIR or $TEMP environment variables were set and the Relay Server State Manager (rshost) was started without the -o command line option specified, rshast would have failed to start. Under these conditions, rshost uses '/' as the root directory and fails due to write premissions. This has been fixed.



CR:638160
CR Number:   638160
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 3047 24 Sep 2010 Fixed
12.0.0 2587 24 Sep 2010 Fixed
Description
Typing a Ctrl-V while viewing a spatial reference system's Definition tab, a system trigger's SQL tab, a Java class's Description tab, or an external environment object's Contents tab, would have caused Sybase Central to either crash or hang when another object was selected in the tree. This has been fixed.



CR:638161
CR Number:   638161
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3059 05 Oct 2010 Fixed
12.0.0 2593 05 Oct 2010 Fixed
Description
When double-clicking a search result for an item in the Fragmentation tab, Sybase Central would have selected the item in the Fragmentation tab, but then would have reported "The result could not be shown because it no longer exists". This has been fixed.



CR:638207
CR Number:   638207
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 26 Aug 2010 Fixed
11.0.1 2485 26 Aug 2010 Fixed
10.0.1 4113 26 Aug 2010 Fixed
12.0.1 3017 27 Sep 2010 Fixed
Description
A LOAD TABLE statement would have failed assertion 111706 "Attempting to store invalid string value in table "{table name}", column "{column name}" if the table had a column with user datatype uniqueidentifier. The problem only happened if a user datatype was used. This has been fixed.



To fix such tables in existing databases the table needs to get recreated or a database upgrade needs to be run.



CR:638231
CR Number:   638231
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 2569 16 Aug 2010 Fixed
11.0.1 2480 16 Aug 2010 Fixed
10.0.1 4112 16 Aug 2010 Fixed
12.0.1 3005 27 Sep 2010 Fixed
Description
The property SAConnection.State would have indicated that the connection was still open even after the connection had been dropped. This has now been corrected.



CR:638242
CR Number:   638242
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2570 16 Aug 2010 Fixed
11.0.1 2481 16 Aug 2010 Fixed
12.0.1 3008 27 Sep 2010 Fixed
10.0.1 4149 18 Nov 2010 Fixed
Description
In rare situations, when multiple instances of the MobiLink client (dbmlsync) were run concurrently on the same machine, one or more of the instances may have crashed. It was possible that this problem might also have manifest itself as corrupt data sent to the MobiLink server, but that would have been extremely unlikely. This behaviour has been fixed.



CR:638260
CR Number:   638260
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 2570 16 Aug 2010 Fixed
11.0.1 2481 16 Aug 2010 Fixed
12.0.1 3008 27 Sep 2010 Fixed
10.0.1 4290 25 Oct 2011 Fixed
Description
If a database with multiple dbspaces failed to start (for any of a variety of reasons such as an invalid log file), the server could have erroneously reported:

"Assertion failed: 201117 Attempt to close a file marked as dirty".



This has now been corrected.



CR:638268
CR Number:   638268
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Linux
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2570 17 Aug 2010 Fixed
11.0.1 2481 17 Aug 2010 Fixed
12.0.1 3008 27 Sep 2010 Fixed
Description
When connecting a device that supports the OMA Device Management protocol directly to an Apache based Relay Server, the device would have displayed an error stating 揑nvalid Host Address. The Afaria Server still provisions the device, but the Afaria OMA-DM Server logs state: "... authentication: no credentials in message . When sending the response back to the client, the Relay Server (when run on systems other than Linux) was incorrectly setting the content-type header as text/plain instead of application/vnd.syncml.dm+wbxml. This has now been fixed.



CR:638271
CR Number:   638271
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 01 Sep 2010 Fixed
11.0.1 2488 01 Sep 2010 Fixed
10.0.1 4116 01 Sep 2010 Fixed
12.0.1 3024 27 Sep 2010 Fixed
Description
The methods ResultSet.getTimestamp() and ResultSet.setTimestamp() quietly manipulated the database timestamp value as UTC. As a result, the javascript methods Date.toString() and ResultSet.toString() would have reported different values offset by the timezone difference. These methods now manage timetamps in localtime relative to ULPOD. Databases with timestamp values stored prior to this fix might contain values that were UTC based.



CR:638273
CR Number:   638273
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2571 20 Aug 2010 Fixed
11.0.1 2483 20 Aug 2010 Fixed
10.0.1 4111 20 Aug 2010 Fixed
12.0.1 3011 27 Sep 2010 Fixed
Description
While connected using the SQL Anywhere or iAnywhere JDBC drivers, attempting to use setNull() in a batch update may have caused the JDBC driver to throw a datatype mismatch SQLException if the datatype specified within the setNull() call differed from other non-null set calls to the same column within the batch update. This problem has now been fixed and the datatype mismatch will now only be thrown if a non-null set call of a different type is made on the same column within a batch update.



CR:638360
CR Number:   638360
Product Name:   MobiLink
Product Component:   scripts
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2566 18 Aug 2010 Fixed
12.0.1 3009 27 Sep 2010 Fixed
Description
The task status uploaded by the MobiLink Agent to the consolidated database may not have been processed. This could have meant that tasks would still have been shown in the MobiLink plug-in for Sybase Central as active, when they had in fact been completed. Task results and execution counts would also not have been updated. After applying this fix, any lost status will be recovered. The trigger for this problem appears to have been random, but was more likely when many tasks were run in a short period of time.



To patch a MobiLink system setup

1. Shut down ML servers

2. execute the sql in %SQLANY12%\MobiLink\Setup\syncmss_ebf.sql



The patch only updates stored procedures, no data will be disturbed by this script. If the MobiLink system setup was installed using 12.0.0.2566 or later then this patch does not need to be applied.



CR:638365
CR Number:   638365
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3009 18 Aug 2010 Fixed
Description
Execution of a DESCRIBE INDEX statement could have failed with a "table not found" error when connected to a case-sensitive database and the table (or owner) name differed from the database object name only by case. For example, when connected to a case-sensitive database, the following DESCRIBE TABLE statement would have failed:

CREATE TABLE Test ( c INT PRIMARY KEY );

DESCRIBE INDEX FOR TABLE test;



This has been fixed.



CR:638368
CR Number:   638368
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2577 02 Sep 2010 Fixed
12.0.1 3024 27 Sep 2010 Fixed
Description
Spurious "109200 Can't parallelize bloom filter" could have been observed which were incorrect. This has been fixed.



CR:638374
CR Number:   638374
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 2570 18 Aug 2010 Fixed
12.0.1 3009 27 Sep 2010 Fixed
Description
The MobiLink Replay utility (mlreplay) could have been run with less than 1 simulated client (using the 杗 option), which could have caused a 揗emory allocation failed error, or for mlreplay to have crashed. This has been fixed so that if mlreplay is run with less than 1 simulated client, it simply prints the usage message (which states the minimum number of simulated clients is 1) and exits.



CR:638468
CR Number:   638468
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)
18 Aug 2010 Fixed
Description
As of Engineering case 637453, support for the SQL Anywhere Explorer and SQL Anywhere Toolbar were removed for Visual Studio 2005 and 2008. A new command line option '/sae' has now been added to the SetupVSPackage.exe utility, to install SQL Anywhere Explorer and SQL Anywhere Toolbar if desired. The default is to still not install the SQL Anywhere Explorer and SQL Anywhere Toolbar.



For example:

SetupVSPackage.exe /i --- not install SQL Anywhere Explorer and SQL Anywhere Toolbar

SetupVSPackage.exe /i /sae --- install SQL Anywhere Explorer and SQL Anywhere Toolbar



Note, this new option only applies to Visual Studio 2005 and 2008. SQL Anywhere Explorer and SQL Anywhere Toolbar are still disabled for Visual Studio 2010. The SetupVSPackage.exe utility always install or uninstalls both the SQL Anywhere Explorer and SQL Anywhere Toolbar together. The '/sae' option only applies to '/i', use of the '/u' option always removes everything.



CR:638473
CR Number:   638473
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 2482 18 Aug 2010 Fixed
Description
If a Relay Server Outbound Enabler (rsoe) was successfully connected to a Relay Server, and the Relay Server was restarted while the rsoe was still running, then the server extension of the Relay Server could have crashed upon receiving the rsoe's new up channel connect request. This crash would have occurred if the rsoe tried to connect with configurations that invalidated the (already running) rsoe authentication, such as changing the farm or server id, that the rsoe was using. This has been fixed.



CR:638477
CR Number:   638477
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 2571 18 Aug 2010 Fixed
11.0.1 2482 18 Aug 2010 Fixed
10.0.1 4111 18 Aug 2010 Fixed
12.0.1 3010 27 Sep 2010 Fixed
Description
In extremely rare circumstances, servers answering queries with keyset cursors may have become unstable, leading to an eventual crash. This has been fixed.



CR:638481
CR Number:   638481
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 2571 19 Aug 2010 Fixed
12.0.1 3010 27 Sep 2010 Fixed
Description
The server could have returned an incorrect name for a temporary connection, or in rare cases the server could have crashed. The crash was more likely when using diagnostics on a mirrored server. The incorrect connection name could have been returned by a call to connection_property( 'Name' ), listed in diagnostic tracing's sa_diagnostic_connection table, or shown in an error such as "User '<user name>' has the row in '<table name>' locked". This has been fixed.



CR:638482
CR Number:   638482
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 4111 19 Aug 2010 Fixed
Description
If diagnostic tracing was enabled on a database and a query used intra-query parallelism, the server may have crashed. This has been fixed.



CR:638484
CR Number:   638484
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 2571 20 Aug 2010 Fixed
11.0.1 2482 20 Aug 2010 Fixed
12.0.1 3010 27 Sep 2010 Fixed
Description
Larger tables with a clustered index that had a significant number of rows inserted at the end of the clustering index, could have exhibited poor local clustering. This could have caused the optimizer to pick sub-optimal plans. This has been fixed.



CR:638492
CR Number:   638492
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2571 20 Aug 2010 Fixed
11.0.1 2482 20 Aug 2010 Fixed
12.0.1 3010 27 Sep 2010 Fixed
Description
For MobiLink clients, except UltraLiteJ, it was possible to receive an "Out of memory" or STREAM_ERROR_MEMORY_ALLOCATION error during TLS or HTTPS synchronizations. Incorrectly attempting a very large memory allocation has bee fixed.



CR:638494
CR Number:   638494
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 2574 19 Aug 2010 Fixed
11.0.1 2486 19 Aug 2010 Fixed
12.0.1 3017 27 Sep 2010 Fixed
Description
Attempting to start an external environment when the server machine was incorrectly configured would have caused the application to wait up to 15 seconds before receiving an error from the server. An incorrectly configured server usually results in the external environment process terminating immediately upon startup; hence the server will now report an appropriate error as soon as it detects that the external environment process terminated while starting up.



CR:638596
CR Number:   638596
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 2571 19 Aug 2010 Fixed
11.0.1 2482 19 Aug 2010 Fixed
12.0.1 3010 27 Sep 2010 Fixed
Description
The use of START AT or FIRST in a subquery may have resulted in incorrect results. This was corrected.



CR:638600
CR Number:   638600
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 2571 19 Aug 2010 Fixed
11.0.1 2483 19 Aug 2010 Fixed
12.0.1 3011 27 Sep 2010 Fixed
Description
When connected using the SQL Anywhere JDBC 4.0 driver, calling DatabaseMetaData.getProcedureColumns() would have returned a result set with the DATA_TYPE column in the metadata result set containing an incorrect JDBC data type for nchar, nvarchar and longnvarchar columns. This problem has now been fixed.



CR:638648
CR Number:   638648
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 2578 07 Sep 2010 Fixed
12.0.1 3012 27 Sep 2010 Fixed
Description
Round Earth polygons with long edges crossing equator could have been interpreted incorrectly, causing queries over such geometries to return incorrect results. This has been fixed.



Database with this problem will need to have the affected geometries re-inserted after applying this fix.



This change also fixes the interpretation of parameters to the ST_Polygon( ST_Point, ST_Point ) constructor. Previously, if the parameter points were close to the International Date Line, an invalid polygon (with edges longer than 180 degrees) could have been constructed. This has been fixed.

For example, consider: ST_Polygon( new ST_Point( 170, 10, 4326 ), new ST_Point( -170, 20, 4326 ) ). Now, this will be interpreted as equivalent to: new ST_Polygon( 'Polygon((170 10, -170 10, -170 20, 170 20, 170 10))', 4326 ) which is a polygon crossing the date line.

In general, the constructor will choose the interpretation that generates the polygon that fits into a single hemisphere.



CR:638738
CR Number:   638738
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2572 20 Aug 2010 Fixed
11.0.1 2483 20 Aug 2010 Fixed
12.0.1 3012 27 Sep 2010 Fixed
Description
Windows CE applications, including SA utilities, requiring aygshell.dll to be present on the device or they would not have loaded. This worked fine on Windows Mobile 5 and later devices, but not for non-Windows Mobile CE 5.0 and 6.0 devices. This has been corrected by trying to dynamically load aygshell.dll if it is present, and skip these functions otherwise. For non-Windows Mobile CE devices, buttons are displayed on the main window for shutdown/hide/etc, instead of relying on creating menus accessible via softkeys since this would require aygshell.dll.



CR:638755
CR Number:   638755
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2578 03 Sep 2010 Fixed
11.0.1 2490 03 Sep 2010 Fixed
12.0.1 3026 27 Sep 2010 Fixed
Description
When an ODBC application made a SQLTables() call, the TABLE_TYPE column in the result set identified materialized views as MATERIALIZED VIEW. While doing so was not against the ODBC specification, there was nevertheless a problem with applications like Microsoft Access and Crystal Reports, which filter out anything that is not marked as TABLE, VIEW, SYSTEM TABLE, ALIAS, SYNONYM, GLOBAL TEMPORARY or LOCAL TEMPORARY. Therefore, the TABLE_TYPE value returned for materialized views has been changed to be VIEW.



In addition, a new connection parameter has been added to ODBC which allows a specific string to be defined that is returned in the SQLTables() result set for materialized views. This new connection parameter is called MATVIEW, and is a string that will be returned in the TABLE_TYPE column for materialized views.



For example, to have the SQLTables() function return materialized views as type TABLE, connect as follows:

uid=dba;pwd=sql;eng=...;matview=table



This new option can be used to override this default and return to the previous behaviour. The same string is also used when SQLTables() is called with an explicit TableType filter.



CR:638764
CR Number:   638764
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 2572 23 Aug 2010 Fixed
12.0.1 3012 27 Sep 2010 Fixed
Description
In rare cases, a server participating in a mirroring system could have hung temporarily, and then resumed processing requests, when dynamic tuning of the server's multi-programming level was enabled . This has been fixed.



CR:638770
CR Number:   638770
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2574 26 Aug 2010 Fixed
11.0.1 2492 08 Nov 2010 Fixed
11.0.0 1654 09 Sep 2010 Fixed
12.0.1 3018 27 Sep 2010 Fixed
Description
When using the Dbmlsync API (either the C++ or .Net version), events are retrieved using the GetEvent method. One of the events that might be returned is DBSC_EVENTTYPE_PROGRESS_INDEX, which includes an integer that is supposed to be between 0 and 1000 and indicates how close the current phase of synchronization is to completion. This value is intended to be used to update a progress indicator. Occasionally, the DBSC_EVENTYPE_PROGRESS_INDEX events would have been generated with values greater than 1000. This happened during the log scan phase of synchronization, when the -x command line option or the LogRenameSize sychronization profile option was used. It could also happen if operations were occurring to the remote database during synchronization. This has been fixed. The index should now always be between 0 and 1000.



CR:638771
CR Number:   638771
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2572 23 Aug 2010 Fixed
12.0.1 3012 27 Sep 2010 Fixed
Description
Some incorrect connection strings could have autostarted a database server, but left the autostarted server running after the connection returned an error.

For example:

dbping -d -c "start=dbeng10;eng=server_name"



would have returned an error, but leave a server named server_name running. This has been fixed so that the autostarted server is now stopped if the connection fails.





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

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

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

ReadASADB适用场景

各种误操作:

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

本工具的应用场景:

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