远程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:723010
CR Number:   723010
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3831 13 Nov 2012 Fixed
Description
Under rare circumstances, the server may have returned the error SQLSTATE_INVALID_RECURSION for a recursive select statement. This has been fixed.



CR:723017
CR Number:   723017
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3809 01 Nov 2012 Fixed
11.0.1 2892 01 Nov 2012 Fixed
Description
On Mac OS X 8 systems, the MobiLink Server may have failed to start, with startup error 揢nable to bind socket? This has been fixed.



CR:723024
CR Number:   723024
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.1 3811 01 Nov 2012 Fixed
Description
An index with multiple columns, and any nullable column except the last one in the index, may have been incorrectly ordered.



For example:

CREATE TABLE Foo ( num INT PRIMARY KEY DEFAULT AUTOINCREMENT, b1 BINARY(1), b2 BINARY(1), b3 BINARY(1) )

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, 0, 7 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, null, 8 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, 0, 9 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, null, 10 )

SELECT * FROM Foo ORDER BY b1, b2, b3 could result in an ordering like:

row: 0, 0, 7

row: 0, null, 8

row: null, 0, 9

row: null, null, 10

DROP INDEX Foo.I

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

SELECT * FROM Foo ORDER BY b1, b2, b3

row: null, null, 10

row: null, 0, 9

row: 0, null, 8

row: 0, 0, 7



This has been fixed.



CR:723092
CR Number:   723092
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3816 02 Nov 2012 Fixed
Description
An index with multiple columns and any nullable column except the last one in the index may have been incorrectly ordered.



For example:

CREATE TABLE Foo ( num INT PRIMARY KEY DEFAULT AUTOINCREMENT, b1 BINARY(1), b2 BINARY(1), b3 BINARY(1) )

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, 0, 7 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, null, 8 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, 0, 9 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, null, 10 )

SELECT * FROM Foo ORDER BY b1, b2, b3 could result in an ordering like:

row: 0, 0, 7

row: 0, null, 8

row: null, 0, 9

row: null, null, 10

DROP INDEX Foo.I

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

SELECT * FROM Foo ORDER BY b1, b2, b3

row: null, null, 10

row: null, 0, 9

row: 0, null, 8

row: 0, 0, 7



This has been fixed.



CR:723096
CR Number:   723096
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.1 3812 02 Nov 2012 Fixed
11.0.1 2894 02 Nov 2012 Fixed
Description
If the SQL Anywhere server was registered with an ActiveDirectory LDAP server and an LDAP error occurred at just the right time, the LDAP entry could have been corrupted. When the server then shutdown, no new server with the same server name would have been able to start. This has been fixed.



CR:723102
CR Number:   723102
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3820 06 Nov 2012 Fixed
Description
UltraLite could have returned incorrect results when a subquery made reference to its own expressions.

For example, in the following, c2 is not evaluated properly:



select * from (select id + id as c1, c1 as c2 from T) as DT(c1,c2)



This has been fixed.



CR:723135
CR Number:   723135
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3814 02 Nov 2012 Fixed
Description
If a directory in quotes with a trailing backslash inside the quotes (i.e. 搈y directory name\? was supplied to a utility requiring a directory name, the name of the directory used would have been incorrect (in this case my directory name?with a trailing quote). The affected tools were: dbbackup, dbunload, dbtran (-m switch), dbremote (-ml switch) and the server (-dt, -ad, and -ds switches). This has been fixed. The trailing quote will now be stripped from the directory name.



CR:723212
CR Number:   723212
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.1 3813 05 Nov 2012 Fixed
Description
If a MobiLink project in Sybase Central contained a SQL Anywhere consolidated database, and that database was being monitored by the SQL Anywhere Monitor, tables which were owned by the Monitor were being displayed in the user interface. They have now been removed, because they should never take part in a synchronization.



CR:723333
CR Number:   723333
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3814 06 Nov 2012 Fixed
Description
On Linux systems, executing "samonitor stop" could have failed to stop the SQL Anywhere Monitor. This has now been corrected.



CR:723368
CR Number:   723368
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 3814 06 Nov 2012 Fixed
Description
When deploying a synchronization model with a SQL Anywhere remote database, an error could have occurred if the "Save message log to the following file (using -ot option)" option was unchecked on the "Verbosity For SQL Anywhere Remote Synchronization Client" page of the "Deploy Synchronization Model Wizard". The error message would state:



The synchronization model could not be deployed.

Error for: Rendering macro APPEND_VAR



This has been fixed. A workaround is to enable that option and redeploy.



CR:723443
CR Number:   723443
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3815 06 Nov 2012 Fixed
Description
String concatenation expressions in UltraLite could have given incorrect results, in such a way that a substring was missing from the correct result. For example, the SQL query "SELECT ISNULL('a','') + ISNULL(NULL, '') + 'b'" would have given the result 慴?when the correct result was 慳b? This has been fixed.



CR:723590
CR Number:   723590
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2897 07 Nov 2012 Fixed
Description
If a database exceeded the limit of allowed database pages, the database would have become corrupted and the application may have encountered the SQLE_ERROR:



UltraLiteJ Error[-300]: Run time SQL error -- recordRowID 5832712



This has been fixed. When the maximum number of pages is reached, UltraLiteJ will now report SQLE_DBSPACE_FULL (UltraLiteJ Error[-604]: A dbspace has reached its maximum file size).



Applications encountering this error may be using too small a value for the database page size.



CR:723698
CR Number:   723698
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3819 15 Nov 2012 Fixed
11.0.1 2901 15 Nov 2012 Fixed
Description
A client application could recieved the exception OptimisticsConcurrencyException when updating tables with computed columns. This has now been fixed.



CR:723706
CR Number:   723706
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 3816 08 Nov 2012 Fixed
Description
In very rare cases, it was possible for the server to have crashed when an HTTP connection is accepted. This has been fixed.



CR:723710
CR Number:   723710
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3816 09 Nov 2012 Fixed
11.0.1 2898 09 Nov 2012 Fixed
Description
On Mac OS X systems, use of the server option -um allows the server to run with a GUI (through DBLauncher). It was not displayed though in the server's usage message. This has now been corrected.



CR:723719
CR Number:   723719
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3823 28 Nov 2012 Fixed
Description
A permissions error could be given when calling a procedure or functions that had been inlined. This has been fixed.



CR:723757
CR Number:   723757
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 3816 09 Nov 2012 Fixed
11.0.1 2898 09 Nov 2012 Fixed
Description
The changes made for Engineering case 72143 broke the fast launchers for Interactive SQL and Sybase Central on computers that use a system-level network proxy. The symptom was that attempting to turn on the fast launcher would caused Interactive SQL or Sybase Centralto become unresponsive. This has been fixed.



CR:723835
CR Number:   723835
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 3817 12 Nov 2012 Fixed
Description
Under certain circumstances, the NOT NULL clause for a foreign key specification would have been ignored. When determining the nullability of an indexed column the fact that a foreign key could be specified as NOT NULL was not being taken into account. This has been fixed.



CR:723843
CR Number:   723843
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Infrastructure
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.0 3868 06 Mar 2013 Fixed
Description
The StartServer task could have started database copies on the server that were not stopped when the StopServer task was executed for the server. This has been fixed.



CR:723889
CR Number:   723889
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3817 12 Nov 2012 Fixed
Description
When using a secured connection between the Relay Server Outbound Enabler and the local backend server, it was possible fior the Outbound Enabler to have crashed when disconnecting. This has been fixed.



CR:723960
CR Number:   723960
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3828 06 Dec 2012 Fixed
11.0.1 2910 07 Dec 2012 Fixed
Description
Under specific circumstances, the server could have crashed when applying updates via SQL Remote. This has been fixed.



CR:723969
CR Number:   723969
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3817 13 Nov 2012 Fixed
Description
The Unix installer may have returned an error like 搒amples/sample_env32.sh: No such file or directory", when the selected components did not require the sample directory.

This has been fixed.



CR:723981
CR Number:   723981
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3819 13 Nov 2012 Fixed
Description
In a synchronization model, if the Events editor was used to create a script using the .NET language and deployed the synchronization model, the MobiLink server could have given an error like the following:



Cannot load DLL or shared object: 'ml.net12.dll' for Script Language: '.net'



For Java scripts, a similar error could have been displayed on operating systems with case-sensitive file names, or errors fetching Java scripts on Windows.



These problems have been fixed.



CR:724069
CR Number:   724069
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3818 15 Nov 2012 Fixed
Description
The SQL Anywhere Unix installer may not have installed the Start Server (dbspawn) and Stop Server (dbstop) utilities when 揝QL Anywhere Monitor?developer edition) was selected as a component to install. Running a command like samonitor.sh {start|stop} would have failed due to the missing dbspawn and dbstop executables. This has now been corrected.



CR:724258
CR Number:   724258
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3819 16 Nov 2012 Fixed
Description
A web procedure created using the PROXY clause may have returned the error: '-981: 揢nable to connect to the remote host specified by ?lt;URL>敂 ', depending on the type and configuration of the proxy server being used. This would only have occurred for HTTP requests, HTTPS requests would have worked. This has been fixed.



CR:724284
CR Number:   724284
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 21 Nov 2012 Fixed
Description
In some network environments, a synchronization would have failed with a StringIndexOutOfBound exception due to Set-Cookie: response headers with multiple cookies. This has been fixed.



CR:724287
CR Number:   724287
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Infrastructure
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 1253 16 Nov 2012 Fixed
1.0.0 3819 16 Nov 2012 Fixed
Description
If a cloud server required a proxy server to access the internet, it would have been unable to contact the SAODE usage server, and the cloud would have stopped functioning after 1000 hours. This has been fixed. There is now an option (through the AlterCloud task) to set the proxy server for the cloud.



CR:724349
CR Number:   724349
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
If a variable was used as an OUTPUT parameter for a procedure, the value was not cast to the data type of that variable. This resulted in local or global variables that had values larger than its data type, or values with a different type than its variable declaration. This has been fixed.



CR:724355
CR Number:   724355
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1417 16 Jan 2013 Fixed
12.0.1 3845 16 Jan 2013 Fixed
11.0.1 2929 16 Jan 2013 Fixed
Description
In very rare circumstances, the server may have crashed while performing a query sort operation if the sort key was very long and the query was low on cache space. This has been fixed.



CR:724359
CR Number:   724359
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3819 16 Nov 2012 Fixed
Description
If a database contained a Remote Server definition with a variable reference in its srvinfo column, then clicking the Overview panel would have caused a 搗ariable not found?error to be reported. This has been fixed.



CR:724507
CR Number:   724507
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1426 28 Jan 2013 Fixed
12.0.1 3849 28 Jan 2013 Fixed
11.0.1 2933 28 Jan 2013 Fixed
Description
In rare circumstances, a server that was running diagnostic tracing to a remote server may have crashed if the diagnostic tracing server or database stopped, or if the diagnostic tracing server or database stopped and tracing was detached at the same time. This has been fixed.



CR:724518
CR Number:   724518
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1873 02 Apr 2014 Fixed
12.0.1 4095 02 Apr 2014 Fixed
Description
When using the MobiLink autodial feature, it was possible for the connection attempt to fail initially. Later connection attempts would generally have worked. This has now been corrected.



CR:724543
CR Number:   724543
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.1 3819 19 Nov 2012 Fixed
11.0.1 2901 19 Nov 2012 Fixed
Description
In very rare cases, the server could have crashed while parsing a request-level log file using the system procedure sa_get_request_times(). This problem was introduced by the changes for Enginnering case 722122, and has now been fixed.



CR:724550
CR Number:   724550
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 23 Nov 2012 Fixed
11.0.1 2903 26 Nov 2012 Fixed
Description
The CacheFree server statistic could have underflowed and presented extremely large values. This has been fixed.



CR:724639
CR Number:   724639
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3817 19 Nov 2012 Fixed
Description
A new library (iAnywhere.Data.SQLAnywhere.v4.5.dll) has been added for supporting .NET 4.5 and Entity Framework 5. Now 4 versions of SA ADO.NET provider are shipped:

1 - iAnywhere.Data.SQLAnywhere.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.dll ?for .NET 2

2 - iAnywhere.Data.SQLAnywhere.v3.5.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v3.5.dll ?for .NET 3.x and 2

3 - iAnywhere.Data.SQLAnywhere.v4.0.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v4.0.dll ?for .NET 4

4 - iAnywhere.Data.SQLAnywhere.v4.5.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v4.5.dll ?for .NET 4.5



SetupVSPackage.exe has also been updated. A new option 憊ersion?has been added.

1 - If the version is ?? SetupVSPackage.exe registers the v4 dll in machine.config file.

2 - If the version is ?.5? SetupVSPackage.exe registers the v4.5 dll in machine.config file.

3 - When the version is not specified, SetupVSPackage.exe registers the v4.5 dll in machine.config file if .NET 4.5 is installed; otherwise, it registers the v4.0 dll in machine.config file.



Examples:

1 - SetupVSPackage.exe /i /v 4.5 ?register the v4.5 dll

2 - SetupVSPackage.exe /i /v 4 ?register the v4.0 dll

3 - SetupVSPackage.exe /i ?register the v4.5 dll if .NET 4.5 is installed; otherwise, register the v4.0 dll.



SetupVSPackage.exe should be run to register the v4.0 provider for .NET 4 applications and register the v4.5 provider for .NET 4.5 / Entity Framework 5 applications.



CR:724701
CR Number:   724701
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3820 19 Nov 2012 Fixed
11.0.1 2902 19 Nov 2012 Fixed
Description
When MobiLink clients starts up, it deletes temporary files left by any previous instance of the software that might have exited abnormally. This cleanup was not occurring when the SATMP environment variable was set. This has been fixed.



CR:724847
CR Number:   724847
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 3821 20 Nov 2012 Fixed
12.0.0 2819 20 Nov 2012 Fixed
Description
In certain circumstances, running the Information utility to get table usage and sizes ("dbinfo -u"), calling the system procedure sa_table_page_usage(), or executing "VALIDATE DATABASE", could have caused assertion failure 109510 "Memory allocation size is too large". This problem has been fixed.



CR:724850
CR Number:   724850
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 2004 27 Aug 2014 Fixed
12.0.1 4156 27 Aug 2014 Fixed
Description
DataTable.Load() , ULTable.GetSchemaTable(), or use of ULIndexSchema object could have thrown the exceptions: "Too many temporary tables in connection" or "Attempted to read or write protected memory. This is often an indication that other memory is corrupt?if used repeatedly. The method ULIndexSchema.Close() has been added, and should be called when an application has finished with an ULIndexSchema instance. This method is also now called internally by UL.Net objects that use ULIndexSchema.



CR:724900
CR Number:   724900
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 22 Nov 2012 Fixed
Description
Temporary tables, functions and variables were not dropped after a pooled connection was closed (returned to the connection pool). This has now been corrected.



CR:724960
CR Number:   724960
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3843 11 Jan 2013 Fixed
Description
If the Relay Server had been acting as an intermediary for a backend server that required authentication (such as an IIS Server), it was possible that the authentication handshake between the client and backend server could have failed, despite the client having provided the proper username and password for authentication. This has now been fixed.



CR:725019
CR Number:   725019
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3823 27 Nov 2012 Fixed
11.0.1 2905 27 Nov 2012 Fixed
Description
The syntactical construct "numeric( precision, scale )" would have returned the error "Syntax error near ')'" if the scale value was greater than the precision value. This has been fixed so that the syntax error message now contains the scale value.



CR:725104
CR Number:   725104
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 22 Nov 2012 Fixed
Description
When the MobiLink Server was using an embedded Outbound Enabler, and connectivity issues occurred between the Relay Server and the MobiLink Server while the embedded OE was busy uploading requests, the service may not have recovered. A restart of the MobiLink Server was needed in this case. This problem has been fixed.



CR:725107
CR Number:   725107
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 22 Nov 2012 Fixed
Description
A 'value out of range' SQLException could have occurred in the data collector of the SQL Anywhere Monitor for Relay Server. This has been fixed



CR:725110
CR Number:   725110
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3824 03 Dec 2012 Fixed
11.0.1 2906 03 Dec 2012 Fixed
Description
Under rare circumstances, the server may have crashed when the system procedure sa_locks() was trying to collect row locking information for global temporary tables. This has been fixed.



CR:725179
CR Number:   725179
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 23 Nov 2012 Fixed
Description
Diagnostic tracing also collected information from Cleaner task connections. This has been removed.



CR:725184
CR Number:   725184
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1522 25 Apr 2013 Fixed
12.0.1 3891 25 Apr 2013 Fixed
Description
SQL Anywhere permits the use of identical foreign key CONSTRAINT names on different tables. Some third-party software tools cannot handle duplicate constraint names. As a result, the sample database demo.db that is shipped with SQL Anywhere has been modified so that it now has unique foreign key constraint names. The constraint name FK_CustomerID_ID in the GROUPO.Contacts table has been renamed to FK_CustomerID_ID2. The constraint name FK_ProductID_ID2 in the GROUPO.MarketingInformation table has been renamed to FK_ProductID_ID2.



CR:725197
CR Number:   725197
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 26 Nov 2012 Fixed
11.0.1 2903 26 Nov 2012 Fixed
Description
Using the PHP external environment in an HTTP request, could have returned an HTTP status code of 500 even when it was successful. This was most likely to happen on Windows systems, and has now been fixed.



CR:725201
CR Number:   725201
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 23 Nov 2012 Fixed
11.0.1 2903 23 Nov 2012 Fixed
Description
If an application loaded the SQL Anywhere JDBC Driver into a private ClassLoader, there was a small chance that the application would have crashed when the private ClassLoader was garbage collected. This problem has now been fixed.



CR:725206
CR Number:   725206
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1387 19 Dec 2012 Fixed
12.0.1 3833 19 Dec 2012 Fixed
11.0.1 2916 19 Dec 2012 Fixed
Description
A FETCH RELATIVE {offset}, where the offset was greater than 1, could have failed with a "Connection was terminated" error if the fetch was not the first fetch on the cursor, and prefetch was enabled for the fetch. For this to have ocurred, the rows between the last fetch and the requested rows row had to have values that were greater than 250 bytes. This has been fixed.



As a workaround, prefetch can be disabled.



CR:725212
CR Number:   725212
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3822 26 Nov 2012 Fixed
Description
The Relay Server IIS7 quick setup script was using %USERDNSDOMAIN% as the domain of the machine and that didn't always work. The script has now been changed to test if the FQDN can be resolved, and if not it will offer two options:

a. Setup without a domain

b. Let user enter the domain manually and test again.



Also, the setup step has been clarified so that using the domain user account for Relay Server State Manager service is a valid option if local online maintenance feature is not needed.



CR:725215
CR Number:   725215
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
The following corrections have been made to the IIS6 and IIS7 quick setup:

1 - The Relay Server State Manager could not start as the generated configuration contained removed properties (start and auto_stop). This has been fixed so that the invalid properties is no longer generated.

2 - Many links in the generated quick reference documentation no longer worked, and have now been fixed.

3 - The quick reference only demonstrated the use of the detailed status page, using the rs_admin extension only. Now a full set of pin-pointed status pages are added to the troubleshooting section.



CR:725302
CR Number:   725302
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3823 29 Nov 2012 Fixed
Description
When running on Windows systems, the database server could have hung for up to three minutes when running as a system service when the system was first booting up. This has been fixed.



CR:725391
CR Number:   725391
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1431 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
11.0.1 2935 31 Jan 2013 Fixed
Description
If an Open Client or jConnect application attempted to perform a positioned update on a table that had an NCHAR based column in the primary key, then there was a chance the application would have hung. This problem has now been fixed. Note that this problem did not affect non-TDS based clients.



CR:725392
CR Number:   725392
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3823 27 Nov 2012 Fixed
11.0.1 2905 27 Nov 2012 Fixed
Description
When setting options using the system procedure sa_server_option(), the documentation states that 'YES/NO' as well as 'ON/OFF' can be used for any settings that accept Boolean values. There were two options that would accept 'ON/OFF', but not 'YES/NO', ProcedureProfiling and DeadlockLogging. This has been fixed.



CR:725451
CR Number:   725451
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3823 28 Nov 2012 Fixed
Description
The execution of SELECT INTO statements in stored procedures may have been inefficient to compute. This has been fixed.



CR:725546
CR Number:   725546
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)
09 Jan 2015 Fixed
Description
UltraLite now supports the new armv7s architecture in Xcode 4.5 for A6 chip devices (iPhone 5 and iPad).



The build script for the UltraLite library (SQLAnywhere/ultralite/iphone/build.sh) now selects which architectures to build based on the version of Xcode. Xcode 4.5 and later will build armv7 and the new armv7s. Older versions of Xcode will build armv6 and armv7 as before. An armv7s version of the obfuscated source is now included.



CR:725553
CR Number:   725553
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3824 03 Dec 2012 Fixed
11.0.1 2906 03 Dec 2012 Fixed
Description
A client request which required a server to server request could have hang if the server to server connection was dropped while the client request was using it. For example, if a client request (such as a commit) resulted in writing to the transaction log on a primary high availability server, and the connection to the mirror (the server to server connection) dropped while the client request was attempting to send log pages to the mirror, the client request could have hung. Similarly, this could have occurred during a client request if a connection to a diagnostic server dropped during the client request. Note that only the single client request was hung and the server was still operating normally otherwise. This has been fixed so that the client request will not hang.



As a workaround, the client connection that is hung can be dropped using DROP CONNECTION. This will cause the client connection to immediately report an error.



CR:725583
CR Number:   725583
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3821 28 Nov 2012 Fixed
Description
Execution of "[not] exists(subquery)" expressions in stored procedures may have been inefficient to compute. This has been fixed.



CR:725599
CR Number:   725599
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1287 24 Dec 2012 Fixed
12.0.1 4124 13 Jun 2014 Fixed
Description
In some cases, invalid DEFAULT values were allowed when executing a CREATE TABLE statement. In specific instances, these invalid default values could have caused a server crash. This has now been corrected.



CR:725600
CR Number:   725600
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1287 24 Dec 2012 Fixed
12.0.1 4124 13 Jun 2014 Fixed
Description
Some queries with invalid ORDER BY clause specifications could have failed to give an error, given an inappropriate error, or caused a server crash. This has been fixed.



CR:725601
CR Number:   725601
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 4124 18 Jun 2014 Fixed
Description
An error could have been incorrectly returned when creating a procedure, trigger, view, or event if there was a constant literal for a number. For the problem to occur, the number must have been larger than can fit in a NUMERIC type, but in range for a DOUBLE value (alternatively, it could have been a number smaller than can fit in a NUMERIC type but non-zero when interpreted as a DOUBLE). When the problem occurred, an error such as the following might have been returned:

SQLCODE=-836 "Procedure 'P1' is no longer valid"



Further, the database where the statement was executed could have failed to recover after a failure.



For example:

create or replace procedure dba.P1()

begin

select if 1=1 then 1000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 end if;

end

create or replace procedure dba.P2()

begin

select if 1=1 then 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001 end if;

end



CR:725602
CR Number:   725602
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)
16.0.0 1287 24 Dec 2012 Fixed
12.0.1 4124 13 Jun 2014 Fixed
Description
If a grouped query contained a ROWID function in the SELECT list or the HAVING clause, where the primary key of the table of the ROWID was in the GROUP BY list but the ROWID function was not in the GROUP BY list, then an inappropriate error (揈xpression error? was returned.



For example:

select ROWID(T)

from sys.dummy T

group by dummy_col



This has been fixed. The following error is now returned:

Function or column reference to 'ROWID' must also appear in a GROUP BY

SQLCODE=-149, ODBC 3 State="42000"



To avoid the error, include the ROWID function in the GROUP BY list.



CR:725690
CR Number:   725690
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1504 09 Apr 2013 Fixed
12.0.1 3882 09 Apr 2013 Fixed
11.0.1 2969 09 Apr 2013 Fixed
Description
Under rare circumstances, if recovery operations performed on a database included changes affecting immediate text indexes, there was a potential for triggering assertions failures or server crashes. There is also a potential for generating incorrect score values or incorrect results for subsequent queries using the text index. These problems have now been corrected.



CR:725692
CR Number:   725692
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)
16.0.0 1584 27 Jun 2013 Fixed
Description
The connection widgets lists all connections to the SA resource (server). There can be more than one database on the server and the connections showed up with no indication of which database they were on. The database name for the connection is now shown.



CR:725700
CR Number:   725700
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3824 30 Nov 2012 Fixed
Description
The performance of the SAParameterCollection.AddParameters method has been improved.



CR:725718
CR Number:   725718
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 3826 05 Dec 2012 Fixed
11.0.1 2908 05 Dec 2012 Fixed
Description
When running the server on Linux systems with a recent glibc version, the server could have crashed. This was more likely when a system with many CPUs was being used. This has now been fixed.



The only reliable workaround is to use an older version of glibc.



CR:725779
CR Number:   725779
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3827 10 Dec 2012 Fixed
Description
When installing an EBF, the installer could have erroneously terminated and rolled back the install. This has been fixed.



CR:725820
CR Number:   725820
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3817 03 Dec 2012 Fixed
11.0.1 2908 03 Dec 2012 Fixed
Description
If a high availability partner was stopped while it was attempting to determine its role, the database may have been corrupted. If this corruption occurred, attempting to start the database would likely fail with the 100904 assertion "Failed to redo a database operation." This has now been fixed.



As a workaround, when stopping a mirror partner that is currently determining the role with an affected build, it is recommended that the server is terminated instead of stopped normally.



If this database corruption occurs, the database is corrupted but the transaction log is not. The database can be fully recovered by applying the current transaction log file(s) to a backup.



CR:725821
CR Number:   725821
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3817 03 Dec 2012 Fixed
Description
The Entity Framework reference in the ADO.NET v4 provider for the 12.0.1.3797 EBF incorrectly refered to the Entity Framework 5.x assemblies. This has been fixed.



Also, version support for the ADO.NET v4 provider to the Entity Framework is now limited to Entity Framework versions 4.4.x and up.



CR:725827
CR Number:   725827
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3822 03 Dec 2012 Fixed
Description
With UltraLiteJ for Android, the network protocol options 搃dentity?and 搃dentity_password?for authentication of the client during MobiLink synchronization, are now supported. These network protocol options must be set as 揺xtra?parameters with the UltraLiteJ API StreamHTTPParms.setExtraParameters().



CR:725849
CR Number:   725849
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3826 03 Dec 2012 Fixed
Description
When converting .NET values of SAParameter to native types, the provider always allocated new unmanaged memory, which may have been slow. To improve performance, unmanaged memory is now cached and reused.



CR:725854
CR Number:   725854
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3826 03 Dec 2012 Fixed
Description
The .NET values of SAParameter have been converted to native types to improve performance. The native values are now cached and reused if they are not changed since the last execution of the command. Also, several other changes have been made to reduce the time for accessing the properties and methods of SAParameter and SAParameterCollection.



CR:726235
CR Number:   726235
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1418 06 Dec 2012 Fixed
12.0.1 3846 18 Jan 2013 Fixed
11.0.1 2997 04 Mar 2013 Fixed
Description
Under rare, timing and execution plan dependent circumstances, execution of a parallel query plan could have caused the server to hang. This has been fixed.



A workaround is to disable intra-query parallelism for affected queries.



CR:726268
CR Number:   726268
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3827 06 Dec 2012 Fixed
11.0.1 2909 06 Dec 2012 Fixed
Description
Under rare circumstances, using Sybase Central抯 search functionality may not have have been able to locate a search hit when it was double-clicked. This has been fixed.



CR:726388
CR Number:   726388
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3828 07 Dec 2012 Fixed
11.0.1 2910 07 Dec 2012 Fixed
Description
Some XML documents could have caused the server to allocate excessive memory while processing OPENXML. This has been fixed. These types of documents now return the error:

-890 "Statement size or complexity exceeds server limits"



In some cases, a statement processing an XML document could not have been stopped by cancelling or dropping the connection. This has been fixed



CR:726393
CR Number:   726393
Product Name:   UltraLiteJ
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3828 06 Dec 2012 Fixed
Description
The UltraLiteJ Database Transfer utility would not have transfered databases on 64bit only Windows systemss. An 揈rror transferring database?dialog would have been displayed immediately after clicking on the 揝tart?button. This has been fixed.



CR:726396
CR Number:   726396
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1416 15 Jan 2013 Fixed
12.0.1 3845 15 Jan 2013 Fixed
Description
If a SQL batch contained multiple DECLARE statements for local variables with assignments of the default value or an initial value, then the assignments were only executed for the last DECLARE variable-name statement of the batch. This has been fixed.



CR:726508
CR Number:   726508
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3828 07 Dec 2012 Fixed
Description
If a query used the user_name() or suser_name() builtin function, then the described length of the column was LONG VARCHAR, even though the value would be at most 128 bytes. This has been corrected so that the described type is now VARCHAR(128). Any materialized views that use these builtins in the select list should be rebuilt after this change.



CR:726536
CR Number:   726536
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1432 31 Jan 2013 Fixed
12.0.1 3852 31 Jan 2013 Fixed
11.0.1 2936 31 Jan 2013 Fixed
Description
When using the START EXTERNAL ENVIRONMENT statement to start a connection-scoped external environment, and then disconnecting later on without actually making any external environment calls to the connection-scoped external environment, then there was a small chance the server would have crashed. This problem has now been fixed.



CR:726546
CR Number:   726546
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 3829 12 Dec 2012 Fixed
Description
The LastReqTime connection property could have had an incorrect time stamp compared to current time. This would have only occurred if the server had been running for more than 24 hours. This has been fixed.



CR:726715
CR Number:   726715
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3829 12 Dec 2012 Fixed
11.0.1 2911 12 Dec 2012 Fixed
Description
The server could in some cases, have crashed while performing a BCP IN request if an error was generated while servicing the BCP request. This problem has now been fixed.



CR:726720
CR Number:   726720
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3830 12 Dec 2012 Fixed
Description
In very rare timing dependent cases, it was possible for a mirror server connection between two servers to have only been partially established. If this was the case, the mirror or copy node with the partially established connection would not have written or applied changes. In particular, a mirror would have stayed in the 'synchronizing' state when it should have become 'synchronized'. This has been fixed.



A work around is to restart the server that is not writing or applying changes.



CR:726945
CR Number:   726945
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3830 12 Dec 2012 Fixed
11.0.1 2912 12 Dec 2012 Fixed
Description
Attempting to start external environments would have failed if an Version 10.0 database, with a large number of objects, was upgraded. This problem has now been fixed.



CR:726951
CR Number:   726951
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3831 17 Dec 2012 Fixed
11.0.1 2913 17 Dec 2012 Fixed
Description
In rare timing dependent cases, if the primary server was stopped, the mirror server would have failed to take over as the new primary server. This has been fixed.



CR:726952
CR Number:   726952
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3830 12 Dec 2012 Fixed
11.0.1 2912 12 Dec 2012 Fixed
16.0.0 1383 17 Dec 2012 Fixed
Description
The MobiLink Client would not have reported error messages generated by the MobiLink server for a synchronization where progress offsets were checked against the server values at the beginning of the synchronization and found to be different from the server side values. This has been fixed.



CR:726959
CR Number:   726959
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1472 08 Mar 2013 Fixed
12.0.1 3868 08 Mar 2013 Fixed
Description
In a high availability mirroring setup, if the connection between the mirroring partners dropped, but the connections to the arbiter were stable, it was possible for the primary to have restarted. This has been fixed.



CR:727045
CR Number:   727045
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1382 17 Dec 2012 Fixed
12.0.1 3831 17 Dec 2012 Fixed
Description
If the case of the procedure owner and/or name differed between the procedure抯 definition statement and its source statement in the reload script generated by dbunload, then attempting to compare the databases would have thrown an assertion.

For example:

create procedure usr.FullName( ...;

COMMENT TO PRESERVE FORMAT ON PROCEDURE "USR"."FullName" IS ...;



The same problem would have occurred for functions, triggers, views, and events. These issues have been fixed.



CR:727087
CR Number:   727087
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3831 13 Dec 2012 Fixed
11.0.1 2913 13 Dec 2012 Fixed
Description
If a stored procedure statement contained an OPENXML statement with a variable used in an XPATH value, or a CONTAINS condition with a variable used in the query parameter, then the statement could have failed incorrectly with an error:

-134 "Feature 'OPENXML with non-constant query' not implemented"

-1159 "Non-constant or unknown text query string."

In order for the error to be returned, the variable must have been used in a larger expression such as a cast or string concatenation. The failure would have occurresd intermittently, for example on the 11th execution of the statement. This has been fixed.



CR:727093
CR Number:   727093
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)
16.0.0 2010 09 Sep 2014 Fixed
12.0.1 4159 09 Sep 2014 Fixed
Description
In extremely rare, timing dependent cases a database could have been corrupted if a server crashed or was terminated during a checkpoint, and then was terminated again during recovery. This has been fixed.



CR:727096
CR Number:   727096
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 3831 17 Dec 2012 Fixed
11.0.1 2913 17 Dec 2012 Fixed
16.0.0 1381 17 Dec 2012 Fixed
Description
Clicking the "Single Step" menu item executes the SQL statement containing the editing caret, then selects the next statement in the "SQL Statements" panel. If the SQL statements were separated by the word "GO", the single stepping could have failed depending on the specific statement being executed, resulting in a syntax error that referred to a trailing letter "G" in the statement. This has been fixed.



CR:727144
CR Number:   727144
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1426 29 Jan 2013 Fixed
12.0.1 3849 29 Jan 2013 Fixed
Description
When executing SQL statements and queries with many parameters, they could have taken a long time to complete in an UltraLite.Net application. This has been fixed.



CR:727192
CR Number:   727192
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3831 17 Dec 2012 Fixed
Description
Comparing databases could have failed if extended characters were used in one or more of the connection parameters for either of the databases. For example, if a database name was specified that contained characters other than 7-bit ASCII. This has been fixed.



CR:727198
CR Number:   727198
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3833 18 Dec 2012 Fixed
Description
Specific forms of the LIKE predicate could have caused the server to crash. As well, the wrong answer could have been returned for a LIKE predicate that compared non-string values. These problems have now been fixed.



CR:727245
CR Number:   727245
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3856 05 Feb 2013 Fixed
Description
UltraLite could have signaled -305 or -309 errors, and the crashed or possibly failed to upload all rows, after the following sequence:

- synchronization including downloaded deletes

- concurrent commit operation during the synchronization download cleanup phase

- shutdown (or application termination) soon after the synchronization completes

This has now been corrected.



CR:727315
CR Number:   727315
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3832 17 Dec 2012 Fixed
11.0.1 2915 17 Dec 2012 Fixed
16.0.0 1386 17 Dec 2012 Fixed
Description
Under rare circumstances, the server may have crashed if RememberLastStatement was turned on and a statement being executed was too complex. This has been fixed.



CR:727357
CR Number:   727357
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3832 18 Dec 2012 Fixed
11.0.1 2915 18 Dec 2012 Fixed
Description
If a version 16 or later MobiLink client connected to a version 12 or earlier MobiLink server, the server would have printed a confusing error. It will now print an 'unrecognized version' error.



CR:727360
CR Number:   727360
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3832 18 Dec 2012 Fixed
11.0.1 2915 18 Dec 2012 Fixed
Description
The MobiLink server may have crashed if the upload stream contained updates for tables with BLOB or spatial columns. Other requirements were that the updates caused conflict updates, and the script version contained conflict detection/resolution scripts. This problem is now fixed.



CR:727601
CR Number:   727601
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)
16.0.0 1387 24 Dec 2012 Fixed
12.0.1 3833 24 Dec 2012 Fixed
Description
If a statement contained an IN predicate on a column and one or more other sargable predicates on the column, then the statement might not have executed as efficiently as it could have. When optimizing predicates, the range of values within the IN list was not considered when finding tautologies, contradictions, or a narrower interval of validity. This has been fixed.



For example, the following predicates are now optimized as follows (where, UDF is a user-defined function):

x=3 and x in (1,2,3) --> x=3

x>=3 and x in (1,2,3) --> x=3

x>3 and x in (1,2,3) --> FALSE

x=2 and x in (1,2,UDF(3)) --> x=2

x=3 and x in (1,2,UDF(3)) --> x=3 and x in (1,2,UDF(3))



CR:727658
CR Number:   727658
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1389 24 Dec 2012 Fixed
Description
The Deploy wizard in the MobiLink Plug-in generates a summary file that shows all the choices made during the deploy process. Each line in this file was terminated with a \n character. Some Windows editors do not recognize this a line terminator, they expect \r\n. The wizard now terminates the lines of the summary file with the appropriate line terminator for the operating system on which it is running.



CR:727669
CR Number:   727669
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1416 15 Jan 2013 Fixed
12.0.1 3843 15 Jan 2013 Fixed
Description
Under rare circumstances, a simple statement using variables or builtin functions could have returned incorrect results. This could only happen if the simple statement was processed by bypassing the query optimizer. This has been fixed.





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