远程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:712128
CR Number:   712128
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 3755 03 Jul 2012 Fixed
Description
In rare cases, the server could have hung while trying to shut down a database if there were open connections that subsequently had open Remote Data Access connections. This problem has now been fixed.



CR:712421
CR Number:   712421
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4174 22 Jun 2012 Fixed
1.0.0 3752 22 Jun 2012 Fixed
Description
When sorting backups for a host by clicking on the Database column, it did not sort properly. This has been fixed.



CR:712446
CR Number:   712446
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 4174 28 Jun 2012 Fixed
1.0.0 3752 03 Jul 2012 Fixed
Description
Under rare circumstances, the ConvertServerToCloudPartner task could have hung. This has been fixed.



CR:712453
CR Number:   712453
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4174 28 Jun 2012 Fixed
1.0.0 3752 03 Jul 2012 Fixed
Description
A link from a copy database in the Databases panel for a Host would have failed when the database contained accented characters. This has been fixed.



CR:712456
CR Number:   712456
Product Name:   MobiLink
Product Component:   scripts
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3759 06 Jul 2012 Fixed
11.0.1 2837 06 Jul 2012 Fixed
Description
When using the DBRowReader class, it was possible for all the values in a long column to be erroneously returned as NULL. This has been fixed.



CR:712457
CR Number:   712457
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Infrastructure
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4179 28 Jun 2012 Fixed
1.0.0 3754 04 Jul 2012 Fixed
Description
On Linux systems, the RepairServer task was not able to kill a server process during the repair steps. This has been fixed.



CR:712459
CR Number:   712459
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 3798 27 Sep 2012 Fixed
Description
In very rare timing dependent cases, a copy node that was both a parent and a child could have crashed, or failed with an assertion, while the transaction log was being renamed. This has been fixed.



CR:712618
CR Number:   712618
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 3753 28 Jun 2012 Fixed
11.0.1 2832 28 Jun 2012 Fixed
Description
Setting the isql_allow_read_client_file or isql_allow_write_client_file options in the Interactive SQL utility to 'on' or 'off' had no effect. Interactive SQL would always behave as if the option was 'prompt'. This has been fixed.



CR:712710
CR Number:   712710
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 4178 28 Jun 2012 Fixed
1.0.0 3754 03 Jul 2012 Fixed
Description
If a hostname was specified in a maintenance plan, full backups created through that maintenance plan may not have been stored on the specified host. This has been fixed.



CR:712720
CR Number:   712720
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 4185 03 Jul 2012 Fixed
1.0.0 3757 03 Jul 2012 Fixed
Description
If an incremental backup succeeded but validation failed, and another incremental backup was executed on the same database, the resulting incremental backup could have been unusable for recovery. This has been fixed, if an incremental backup is startedn and the most recent full backup (or any backup since) is not marked as "successful", a full backup is done instead.



CR:712721
CR Number:   712721
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 4185 03 Jul 2012 Fixed
1.0.0 3757 03 Jul 2012 Fixed
Description
If an incremental backup succeeded, but validation failed, attempting to validate that backup would have validated the associated full backup plus all incremental backups up to but not including the one specified. If the validation succeeded, the backup would then have been marked as valid, even if the files created by the backup were corrupted. This has been fixed.



CR:712722
CR Number:   712722
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 3754 28 Jun 2012 Fixed
11.0.1 2833 28 Jun 2012 Fixed
Description
Under rare circumstances, rollback of a DML statement that affected a table with at least one immediate text index defined could have caused production assertion failure 200112. This has been fixed.



CR:712851
CR Number:   712851
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 3754 28 Jun 2012 Fixed
Description
A cloud partner could have hung upon losing quorum. This problem has now been fixed.



CR:712884
CR Number:   712884
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 3754 28 Jun 2012 Fixed
11.0.1 2834 28 Jun 2012 Fixed
Description
In very rare timing dependent cases, if a mirroring primary failed over and then failed back, one partner could have received a log mismatch error and shutdown, and transactions that had been submitted could have been lost. Specifically, in order for this to have occurred with partners S1 and S2:

- S1 must initially have been the primary, failed or otherwise have shutdown, causing a failover to S2

- S2 took over as primary

- while S1 was restarting, S2 must have lost quorum and have been shutting down

In which case it was possible for S1 to have become primary again, even though it was missing the transactions from when S2 was primary.



This has been fixed to ensure that S1 will not be primary in this case, and S2 will continue to be primary once it restarts.



CR:712964
CR Number:   712964
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 3755 28 Jun 2012 Fixed
Description
The server could have crashed in very rare cases while attempting to close a connection that had previously made an external environment call if the external environment call subsequently made a server side request that obtained table locks which were still being held when the connection was closed. This problem has now been fixed.



CR:713024
CR Number:   713024
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 3755 29 Jun 2012 Fixed
Description
The Apache setup script now generates <LocationMatch> tags instead of <Location> tags when setting up Apache for RelayServer use. The use of <LocationMatch> allows for a wider range of regular expressions for URL matching, hence, reducing errors resulting from URL-mismatching. This fix also includes changes to the location of generated rs.config and oe.config files (used by the simple test app). The rs.config file is now generated in the RelayServer binaries directory (containing Apache modules and rshost), and the oe.config file is now generated in the same setup scripts directory.



CR:713098
CR Number:   713098
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3755 29 Jun 2012 Fixed
Description
When the Relay Server was restarted, new persistent HTTP requests from persisting client cookies from a previous instance of the Relay Server could have caused truncated responses on new requests from new sessions by the time the backend server could have timed out the persistent connection of the old session. This has been fixed. A workaround is to have clients clear their cookie cache. The Relay Server affinity cookie is implemented as a non-persistent cookie, standard http client implementation shouldn't persist the RS affinity cookie across restart of the http client agent.



CR:713113
CR Number:   713113
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 3755 04 Jul 2012 Fixed
11.0.1 2834 04 Jul 2012 Fixed
Description
In rare timing dependent cases, a mirror or copy node could have crashed or failed assertions (the most likely assertion was 100927). This could have occurred when very frequent transactions were committed on the primary and the mirror or copy node was not applying the operations as fast as it was writing them (i.e. db_property( 'LastWrittenRedoPos' ) is significantly more than db_property( 'CurrentRedoPos' )). This has been fixed.



CR:713129
CR Number:   713129
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4181 03 Jul 2012 Fixed
1.0.0 3755 03 Jul 2012 Fixed
Description
The Change Server Version wizard would have complained about an invalid search after clicking on 'Next'. This has been fixed.



CR:713374
CR Number:   713374
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)
4185 03 Jul 2012 Fixed
1.0.0 3758 03 Jul 2012 Fixed
Description
If a maintenance plan contained a host ID, incremental backups done through that maintenance plan would not have considered that host and would do the incremental backup to the host of the most recent full backup for each database. This has been fixed, if an incremental backup would be done to a host other than the one in the maintenance plan, a full backup to to the maintenance plan's host is done instead.



CR:713388
CR Number:   713388
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 3758 04 Jul 2012 Fixed
Description
Support for the latest release of .NET Framework, .NET 4.5, has now been added. The following features are new in the .NET Framework 4.5 RC:



1. Asynchronous Programming

The new asynchronous programming feature provides a simple technique to make code asynchronous.

Asynchronous code can make the user interface of client applications more responsive, it can also make server applications more scalable. Writing asynchronous code has traditionally involved installing a callback (also called continuation) to express the logic that occurs after the asynchronous operation finishes. This complicates the structure of asynchronous code as compared with synchronous code.

.NET 4.5 allows call into asynchronous methods without using callbacks, and without splitting code across multiple methods or lambda expressions.

The 'async' modifier specifies that a method is asynchronous. When calling an async method, a task is returned. When calling an 'await' statement against the task, the current method exits immediately. When the task finishes, execution resumes in the same method.

Calling an async method does not allocate any additional threads. It may use the existing I/O completion thread briefly at the end.

The following methods were added in SQL Anywhere ADO.NET provider to support asynchronous programming:



SAConnection.OpenAsync



SACommand.ExecuteDbDataReaderAsync

SACommand.ExecuteNonQueryAsync

SACommand.ExecuteReaderAsync

SACommand.ExecuteScalarAsync



SADataReader.GetFieldValueAsync

SADataReader.IsDBNullAsync

SADataReader.NextResultAsync

SADataReader.ReadAsync



SABulkCopy.WriteToServerAsync



Here are some examples:



internal async Task Execute()

{

using (SAConnection conn = new SAConnection("DSN=SQL Anywhere 16 Demo"))

{

SACommand command = new SACommand("select 1", conn);

int result = MethodAsync(conn, command).Result;

command = new SACommand("select top 10 * from SalesOrders", conn);

using (DbDataReader reader = await command.ExecuteReaderAsync())

{

while (await reader.ReadAsync())

Console.WriteLine(String.Format("{0}", reader[0]));

}

}

}

private async Task<int> MethodAsync(SAConnection conn, SACommand cmd)

{

await conn.OpenAsync();

await cmd.ExecuteNonQueryAsync();

return 1;

}



private async Task ExecuteSqlTransaction()

{

using (SAConnection connection = new SAConnection("DSN=SQL Anywhere 16 Demo"))

{

await connection.OpenAsync();

SACommand command = connection.CreateCommand();

SATransaction transaction = await Task.Run<SATransaction>(() => connection.BeginTransaction());

command.Connection = connection;

command.Transaction = transaction;

command.CommandText = "Delete From Departments Where (DepartmentID = 777 OR DepartmentID = 888)";

await command.ExecuteNonQueryAsync();

command.CommandText = "Insert into Departments(DepartmentID, DepartmentName) VALUES (777, 'HR')";

await command.ExecuteNonQueryAsync();

command.CommandText = "Insert into Departments(DepartmentID, DepartmentName) VALUES (888, 'Supporting')";

await command.ExecuteNonQueryAsync();

await Task.Run(() => transaction.Commit());

Console.WriteLine("Both records are written to database.");

}

}



private async Task AsyncSqlBulkCopy()

{

using (SAConnection conn = new SAConnection("DSN=SQL Anywhere 16 Demo"))

{

await conn.OpenAsync();

DataTable dt = new DataTable();

using (SACommand cmd = new SACommand(selStmt, conn))

{

SADataAdapter adapter = new SADataAdapter(cmd);

adapter.Fill(dt);

using (SABulkCopy bcp = new SABulkCopy(conn))

{

bcp.DestinationTableName = destTable;

await bcp.WriteToServerAsync(dt);

}

}

}

}



2. SACredential class.

A new class SACredential has been added for setting the credentials outside of the connection string via the new Credential property of SAConnection. Now the developer can create a SACredential object with a UserId and a SecureString Password to hold the credential values of a connection. This helps mitigate the memory dump vulnerability of keeping the User Name and Password in the connection string.



Here's an example:



private void OpenConnection()

{

SecureString password = new SecureString(); // txtPassword.SecurePassword;

password.MakeReadOnly();



SACredential credential = new SACredential( "dba", password );



using ( SAConnection conn = new SAConnection( "DSN=SQL Anywhere 16 Demo", credential ) )

{

conn.Open();

}

}



CR:713390
CR Number:   713390
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3759 06 Jul 2012 Fixed
11.0.1 2837 06 Jul 2012 Fixed
Description
In some circumstances, such as a transient connection error to the database server, the MobiLink Client process (dbmlsync) that was launched by the QAnywhere agent could have terminated prematurely. When this occurred, the QAnywhere agent could not perform any message transmission, and the only remedy was to restart the QAnywhere agent. This has been fixed by adding the capability to the QAnywhere agent to restart dbmlsync if it detects that the dbmlsync process has terminated.



CR:713455
CR Number:   713455
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3758 04 Jul 2012 Fixed
Description
Support has been added to the MobiLink Server for consolidated databases running on Microsoft SQL Server 2012 servers with the Microsoft native ODBC driver named SQL Server Native Client 11.0, version 2011.110.xxx.xx. This support is limited to Microsoft Windows only.



CR:713458
CR Number:   713458
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 3758 04 Jul 2012 Fixed
Description
The Outbound Enabler was not logging requests at verbosity 1, but the Relay Server does. This has been corrected by lowering the minimum log verbosity level of RS_CLI_SESSION_BEGIN and RS_CLI_REQUEST_BEGIN packets in order to have them logged at verbosity level 1 instead of 3 in the Outbound Enabler. There will now be one log event per HTTP request at log level 1 like the Relay Server does.



CR:713499
CR Number:   713499
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 3790 12 Sep 2012 Fixed
Description
If a connection had multiple uncommitted operations (INSERT, UPDATE, DELETE), and another connection executed a COMMIT, an ArrayIndexOutOfBounds or a cast exception may have occurred. This has been fixed.



CR:713542
CR Number:   713542
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 4187 05 Jul 2012 Fixed
1.0.0 3759 05 Jul 2012 Fixed
Description
The internal procedure dbcloud_compute_unload_key() was testing for the secure feature READFILE twice instead of READFILE and WRITEFILE. This has been corrected. It did not pose any security risk, as the procedure itself does not write any files and the check of the WRITEFILE secure feature is performed again later in the cloud unload/reload code that calls the procedure dbcloud_compute_unload_key().



CR:713557
CR Number:   713557
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 4187 06 Jul 2012 Fixed
1.0.0 3759 06 Jul 2012 Fixed
Description
Some events and tasks took longer than expected to execute. This has been fixed.



CR:713565
CR Number:   713565
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4187 06 Jul 2012 Fixed
1.0.0 3759 06 Jul 2012 Fixed
Description
Sorting a column in any of the details panels did not preserve the setting the next time the panel was visited. This has been fixed.



CR:713566
CR Number:   713566
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4187 06 Jul 2012 Fixed
1.0.0 3759 06 Jul 2012 Fixed
Description
The cloud software panel may not have always refreshed the installed cloud software list. This has been fixed.



CR:713568
CR Number:   713568
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3759 06 Jul 2012 Fixed
11.0.1 2837 06 Jul 2012 Fixed
Description
Mini-dump files generated by SQL Anywhere software on Linux system could have been unusable. This problem was most likely to occur if the process being dumped was using a large number of threads (> 480). This has now been fixed.



CR:713671
CR Number:   713671
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4188 06 Jul 2012 Fixed
1.0.0 3759 06 Jul 2012 Fixed
Description
Attempting to applying a maintenance plan to multiple databases where one or more had accented characters in the name would have failed. This has been fixed.



CR:713681
CR Number:   713681
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 3759 06 Jul 2012 Fixed
Description
If the server was displaying the usage window, or was very early in the start-up process, and the Windows machine the server was running on was suspended, the server could have crashed when the machine was restarted. This has been fixed.



CR:713695
CR Number:   713695
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 3759 09 Jul 2012 Fixed
Description
The fault tolerant HTTP processing in UltraLiteJ for Java 2 Platform Standard Edition (J2SE) did not work correctly. This has been fixed.



CR:713785
CR Number:   713785
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 4191 09 Jul 2012 Fixed
1.0.0 3760 09 Jul 2012 Fixed
Description
In some cases, errors relating to deadlocks or failures due to concurrent operations could have ocurred more often than necessary. These appeared in the diagnostics log, and would have been associated with a slight performance degradation. This has been fixed, Although these errors do continue to appear in properly functioning clouds.



CR:713897
CR Number:   713897
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 3777 10 Jul 2012 Fixed
1.0.0 4192 10 Jul 2012 Fixed
Description
For tenant databases that were very active, validating a backup could have been cancelled before it was complete. If the validation was done as part of a backup, the backup could have been marked as "validation failed". This has been fixed.



CR:713899
CR Number:   713899
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 3764 18 Jul 2012 Fixed
11.0.1 2843 18 Jul 2012 Fixed
Description
A query with a reverse index scan on the left hand side of a join may have resulted in a null pointer exception.



For example:

CREATE TABLE t1( a1 INT PRIMARY KEY )

CREATE TABLE t2( a2 INT PRIMARY KEY )

SELECT t1.a1, t2.a2 FROM t1, t2 ORDER BY t1.a1 DESC



Also, a query with a reverse index scan on the right hand side of a cross join may not have returned any rows.



For example:

SELECT t1.a1, dt.a FROM t1, (SELECT a2 FROM t2 ORDER BY a2 DESC) AS dt( a ) ORDER BY t1.a1 ASC



Both these issues have now been fixed.



CR:713914
CR Number:   713914
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 3761 10 Jul 2012 Fixed
Description
For a pooled CmdSeq connection or HTTP connection, connection_property( 'ApproximateCPUTime' ) incorrectly included CPU time from before the connection was reused, and connection_property( 'LoginTime' ) was not reset when a pooled connection was reused. This has been fixed, so that 'ApproximateCPUTime' now only includes time from when the application connected, and 'LoginTime' is set to the time when the application connected.



CR:713922
CR Number:   713922
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 3768 03 Aug 2012 Fixed
Description
If a query contained two predicates on the same column T.A, of the form 'T.A > constant' and 'T.A = R.A' , and an index on the column T.A exists, the cardinality of the index scan

with the predicate 'T.A = R.A' was incorrectly computed always using the predicate 'T.A > constant'. This may have affected the quality of the best plans for such queries. This has been fixed.



CR:714093
CR Number:   714093
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4193 11 Jul 2012 Fixed
1.0.0 3761 11 Jul 2012 Fixed
Description
The Event Trace Data File Management utility (dbmanageetd) would have shown an incorrect start time and/or end time when the show summary switch (-s) was used. This has been fixed.



CR:714440
CR Number:   714440
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 3763 17 Jul 2012 Fixed
11.0.1 2842 17 Jul 2012 Fixed
Description
In a high availability system, a forced or preferred server fail-over could have failed to restart the database on the primary server if all of the following conditions held:

- the database character set was different from the operating system character set

- the database name (or alias) contained characters other than 7-bit ASCII characters

- an "ALTER DATABASE SET PARTNER FAILOVER" statement was executed, or a preferred partner was defined and the current primary was the non-preferred partner.



This has been fixed.



CR:714525
CR Number:   714525
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 4200 17 Jul 2012 Fixed
1.0.0 3763 17 Jul 2012 Fixed
Description
A mirrored tenant database may have been left in an invalid state if the arbiter of the tenant database was dropped by the task DropServer or DropHost. Checking for the arbiter should have been done prior to dropping the arbiter so that the arbiter can be dropped under the proper condition. This has been fixed.



CR:714642
CR Number:   714642
Product Name:   SQL Remote for SQL Anywhere
Product Component:   Database Tools Interface
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3764 18 Jul 2012 Fixed
Description
If SQL Remote had failed to find a publisher for the database it was connected to, it would have continued to run and could have generated a large number of duplicate messages for a single remote user. This has been corrected so that SQL Remote will now shut down when it determines there is no publisher.



CR:714654
CR Number:   714654
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 3762 18 Jul 2012 Fixed
Description
If a cloud database became unavailable, and it was being monitored by the SQL Anywhere Monitor, the alert details would have claimed the server name to be 'null'. This has been fixed.



CR:714656
CR Number:   714656
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 3765 20 Jul 2012 Fixed
12.0.0 2802 20 Jul 2012 Fixed
11.0.1 2844 20 Jul 2012 Fixed
Description
The server could have crashed when starting a database. If the server was in the process of shrinking the cache, references to memory that were no longer available were possible. This has now been fixed.



CR:714752
CR Number:   714752
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 3766 09 Aug 2012 Fixed
Description
Queries using text indexes with constructs of the form CONTAINS( ... 'xxx*' ... ) may have had poor performance. This has been fixed.



CR:714776
CR Number:   714776
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3765 20 Jul 2012 Fixed
11.0.1 2844 20 Jul 2012 Fixed
Description
In rare timing dependent cases, a high availability mirror or copy node could have incorrectly failed with the assertion 100927. The assertion could have occurred just after the mirror or copy node had connected to its partner or parent and had just started synchronizing. This has been fixed.



CR:714777
CR Number:   714777
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3765 20 Jul 2012 Fixed
Description
In rare cases, a mirroring server could have crashed if it received an invalid request from another mirror server. This has been fixed to no longer crash.



CR:714809
CR Number:   714809
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)
16.0.0 1390 24 Dec 2012 Fixed
12.0.1 3834 24 Dec 2012 Fixed
Description
A result set could have been returned with both the pre-image and the post-image of a row that was updated while the cursor was sitting on it. This has been fixed. Result sets will now return only one copy of the row, the pre-image or the post-image, but not both, depending on the isolation level and when the update is committed.



CR:714896
CR Number:   714896
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 3765 23 Jul 2012 Fixed
Description
Issues with the IIS 6 and IIS& QuickSetup scripts have been corrected:

- the IIS7 auto install could not be invoked if the appcmd.exe utility was missing. This issue has been fixed so that appcmd.exe utility is not needed before triggering IIS7 [re]installation.



- the IIS7 Relay Server setup script could not handle a machine not having a domain suffix.



- the IIS6 & IIS7 Relay Server setup scripts were referencing sleep.exe which is not a standard utility on Windows. The reference has been removed.



CR:714899
CR Number:   714899
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)
11.0.1 2846 24 Jul 2012 Fixed
Description
The server would have returned error code 503 when attempting a connection to an ESMTP server using xp_startsmtp. This has been fixed.



CR:715025
CR Number:   715025
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 3766 23 Jul 2012 Fixed
Description
A Relay Server, which doesn't produce urgent flow control packets according to protocol, could have crashed the Outbound Enabler. No Relay Server has been released with this problem, but a fix has been made so that the Outbound Enabler will give an error and not crash in such situations.



CR:715033
CR Number:   715033
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3766 24 Jul 2012 Fixed
Description
The following changes have been made to the Relay Server level 4 debug log:

- The "Replaying 0 bytes ..." message was confusing and has been suppressed.

- Added "Response headers submitted for sending" message.

- Logging Content-length expectation up front.

- Enhance Content-length replay status with remaining length.

- Added user friendly response status and header logging so that users don't need to suffer level 5 payload logging which is heavier and less readable.

- Moved user friendly request header logging from log level 5 to log level 4 so that user don't need to suffer level 5 payload logging which is heavier an less readable.



CR:715069
CR Number:   715069
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)
11.0.1 2847 26 Jul 2012 Fixed
Description
Sybase Central would have crashed on shutdown if the Services folder was in the process of polling, that is, if the "Enable polling" check box on the Polling tab of a service property sheet was checked. This has been fixed.



CR:715167
CR Number:   715167
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3769 24 Jul 2012 Fixed
Description
The Relay Server affinity cookies were sometime not used properly by third party client software in cases where the same cookie was used concurrently on different HTTP requests. In such situation, the Relay Server behaviour was to let the latest request to take over the connection associated with the affinity cookie. An optional backend farm property called renew_overlapped_cookie has now been introduced. It has a default value of 'No', which maps to the existing behavior. When renew_overlapped_cookie is set to 'Yes', the Relay Server will detect overlap for the farm that has this property explicitly turned on and renew the overlapping cookie by creating a brand new affinity binding. The request with the renewal will still be routed to the same backend server but not the same backend connection as the on going request that it overlapped with. A new backend connection will be created instead.



Relay Server configuration example:

[backend_farm]

description = a backend server farm

id = RSTEST02.F0

renew_overlapped_cookie= yes



Online update of the of the renew_overlapped_cookie property is supported.



CR:715218
CR Number:   715218
Product Name:   SQL Remote for SQL Anywhere
Product Component:   SQL Remote for Adaptive Server Anywhere
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3770 31 Jul 2012 Fixed
12.0.0 2803 31 Jul 2012 Fixed
11.0.1 2848 31 Jul 2012 Fixed
Description
In rare cases, SQL Remote would have started applying a multi-part message before receiving the last piece the message, and then would have ignored all the operations in the last piece of the message when it was received. This has been fixed, SQL Remote will make sure it has received all the pieces of a multi-part message before applying them.



CR:715309
CR Number:   715309
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 3769 26 Jul 2012 Fixed
11.0.1 2847 26 Jul 2012 Fixed
Description
The server was incorrectly accepting the special values NaN, INF, and INFINITY for double and float data types when receiving host variable values. This has been fixed. Now the server will set the SQL error "Value NaN/INF out of range for destination".



CR:715310
CR Number:   715310
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3768 26 Jul 2012 Fixed
Description
If a mirror or copy node was shutdown, and it was actively applying log operations from the primary or its parent, the server could have failed assertion 100904 - "Statement interrupted by user". This has been fixed by not failing this assertion when the server is in the process of shutting down.



CR:715469
CR Number:   715469
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3770 30 Jul 2012 Fixed
11.0.1 2847 30 Jul 2012 Fixed
Description
The interactive response of the Lookup Table Name and Lookup Procedure Name windows in the Interactive SQL utility has been improved.



CR:715473
CR Number:   715473
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.1 3768 26 Jul 2012 Fixed
Description
In extremely rare cases, the server may have crashed on shutdown on multi-CPU machines. This has been fixed.



CR:715480
CR Number:   715480
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3769 30 Jul 2012 Fixed
Description
When using the Unload utility to rebuild a pre-version 10 database, if the connection string contained the server name or the source database name, then the warning 'Rebuild of database with older file format ignoring connection parameter "???"' was printed with question marks for the parameter. This has been fixed so that the parameter name is now displayed in the message.



CR:715583
CR Number:   715583
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 3772 07 Aug 2012 Fixed
11.0.1 2850 07 Aug 2012 Fixed
Description
It was possible to create duplicate indexes for a table in a case-sensitive database if the only difference between the index names was case or accent. For example, both foo and Foo could have been created with same or different definitions. This has now been fixed.



CR:715597
CR Number:   715597
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3769 31 Jul 2012 Fixed
11.0.1 2847 31 Jul 2012 Fixed
Description
Performance of statements that select from a stored procedure call is slightly improved when the call results in a SQLError.



CR:715615
CR Number:   715615
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 3772 09 Aug 2012 Fixed
11.0.1 2850 09 Aug 2012 Fixed
Description
Under rare circumstances, database recovery could have held locks on a new text index. This has been fixed.



Also, text index validation could have returned an error later than necessary. This has been fixed in version 12.0.1 and later.



CR:715672
CR Number:   715672
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3770 30 Jul 2012 Fixed
Description
Attempting to connect Sybase Central to a database running on a version 11.0.0 or earlier server would have caused Sybase Central to crash. This has been

fixed.



CR:715687
CR Number:   715687
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 3771 31 Jul 2012 Fixed
11.0.1 2849 31 Jul 2012 Fixed
Description
When the server collects information about database pages to be used for cache warming in the next database start, it also incorrectly collected information about pages that the database cleaner task reads. This has been fixed so that page recording no longer includes pages read by the cleaner since these pages are different each time.



CR:715799
CR Number:   715799
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3777 14 Aug 2012 Fixed
Description
Two foreign key or unique constraints on the same table could have been created with names that represent the same identifier, but differ only in case. For example 'myFK' and 'myfk'.

This has been fixed.



CR:715843
CR Number:   715843
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 3781 22 Aug 2012 Fixed
11.0.1 2872 13 Sep 2012 Fixed
Description
In rare cases, attempting to use nested procedures with nested transactions and internally generated temporary tables would have failed assertion 201501, 101412, 200505 or others. This problem has now been fixed.



CR:715904
CR Number:   715904
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 3565 01 Aug 2012 Fixed
Description
Installing SQL Anywhere in silent mode on Solaris systems may have resulted in an error like:

"The following option names are invalid or are not exposed by the registration key provided".



This has been fixed.



CR:715906
CR Number:   715906
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3771 01 Aug 2012 Fixed
11.0.1 2849 01 Aug 2012 Fixed
Description
The Support utility (dbsupport) may have crashed while attempting to receive a response from the error reporting site, if the error reporting site was not available. This has not been corrected.



CR:715909
CR Number:   715909
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 3771 01 Aug 2012 Fixed
11.0.1 2849 01 Aug 2012 Fixed
Description
The output from the system procedure sa_locks() could have been incorrect, in that it may have missed reporting some row locks. This has now been corrected. This was a reporting problem only, and did not affect actual locking behaviour.



CR:716036
CR Number:   716036
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 3776 13 Aug 2012 Fixed
Description
The changes for Engineering case 702214 may have made an external environment call take significantly longer when connected to a case sensitive database. This problem has now been fixed.



CR:716037
CR Number:   716037
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 3796 25 Sep 2012 Fixed
Description
If the Down Channel between the Relay Server and the Outbound Enabler was healthy, the Outbound Enabler would not have checked for liveness on the Up Channel. In very rare circumstances, the Down Channel could be healthy, but an intermediary between the Relay Server and Outbound Enabler has closed the socket for the Up Channel at the Relay Server, while leaving the corresponding socket on the Outbound Enabler open. In this scenario, the Outbound Enabler would never have attempted to re-connect the Up Channel, and no communication with the backend server was possible. When the Down Channel is healthy, the Outbound Enabler now increases the time for the liveness by a factor of four instead of disabling the liveness.



CR:716317
CR Number:   716317
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 3803 09 Oct 2012 Fixed
Description
Under some circumstances, especially if a cached plan was used, a select from a DML statement (INSERT, DELETE, UPDATE, or MERGE) may have returned an incorrect result set. This has been fixed.



CR:716390
CR Number:   716390
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 3776 13 Aug 2012 Fixed
11.0.1 2855 13 Aug 2012 Fixed
Description
N ADO .Net client application could have received a NullReferenceException when updating entities using Fixed concurrency mode. This problem has been fixed.



CR:716529
CR Number:   716529
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.0 3774 09 Aug 2012 Fixed
Description
Installing cloud software on multiple hosts with a particular name format may have failed. This has been fixed.



CR:716537
CR Number:   716537
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 3780 09 Aug 2012 Fixed
Description
In a multi-level read-only scale-out configuration, executing the "ALTER MIRROR SERVER ... ALTER PARENT FROM ..." statement could have resulted in read-only scale-out servers not being able to connect to their parent, even if their parent was running. This has been fixed.



Note, a work around is to stop and restart copy node servers that cannot connect to their running parent.



CR:716538
CR Number:   716538
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 3805 14 Aug 2012 Fixed
11.0.1 2887 15 Oct 2012 Fixed
Description
An addition fix was required for Engineering case 714656, where the server could have crashed when auto-starting a database.



CR:716544
CR Number:   716544
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 3780 14 Aug 2012 Fixed
12.0.0 2806 20 Aug 2012 Fixed
11.0.1 2858 20 Aug 2012 Fixed
Description
Explicitly passing in NULL as the 3rd parameter (algorithm) to the encrypt or decrypt function would have resulted in the error: "The string is too long (Parameter 3)" SQLCODE -973, rather than having the encryption/decryption default to AES128. This has been fixed. Not specifying the third parameter at all would have worked properly.



CR:716549
CR Number:   716549
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4225 09 Aug 2012 Fixed
1.0.0 3774 09 Aug 2012 Fixed
Description
Generating a diagnostic log from a host 'Events & Tasks' panel may have failed. This has been fixed.



CR:716625
CR Number:   716625
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 3775 10 Aug 2012 Fixed
Description
In rare timing dependent cases, a transaction which was successfully committed on a primary server could have been lost. In order for there to have been a chance of this occurring, all of the following needed to be true:

- the application was connected to a primary server that lost quorum (the server lost the connection to both the mirror and arbiter servers)

- the application stayed connected to this server (the old primary server) even though the network connection to other servers dropped

- the application was in the middle of committing a transaction between the time that the old primary server lost its connection to the mirror and arbiter server, and when the old primary server restarted as the new mirror server because it lost quorum

- the old mirror server took over as the new primary (the mirror server must have been able to connect to the arbiter server for this to occur)



This has been fixed.



CR:716746
CR Number:   716746
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4228 10 Aug 2012 Fixed
1.0.0 3775 10 Aug 2012 Fixed
Description
On the Backups panel for a host, clicking a column to sort it would not have worked properly. This has now been fixed.



CR:716907
CR Number:   716907
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4232 14 Aug 2012 Fixed
1.0.0 3777 14 Aug 2012 Fixed
Description
Sometimes, connections to a cloud would not show its HA information properly on the Console's Cloud Overview panel. This has been fixed.



CR:716908
CR Number:   716908
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3787 05 Sep 2012 Fixed
11.0.1 2867 05 Sep 2012 Fixed
9.0.2 4354 05 Sep 2012 Fixed
Description
Attempting to upgrade a database initialized with software prior to version 10, to version 10 or higher, on a computer running Linux that uses a 3.x kernel may have failed. This was most likely on systems with more than 4 GB of RAM, or with 32-bit software. This has now been fixed.



CR:716916
CR Number:   716916
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 4232 15 Aug 2012 Fixed
1.0.0 3777 15 Aug 2012 Fixed
Description
The UpgradeCloudInfrastructure task could have failed during stage 1 if cloud software or hosts were recently dropped. This has been fixed.



A work around is to manually run the CleanCloud task and then run the UpgradeCloudInfrastructure task again.







Engineering Description:



CR:716984
CR Number:   716984
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4233 15 Aug 2012 Fixed
1.0.0 3778 15 Aug 2012 Fixed
Description
When viewing backups for a host in the Cloud Console and changing to a new page, selecting a new host to show its backups would remain on that page still showing the first hosts backups. This has been fixed.



CR:717011
CR Number:   717011
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Cloud Console
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4233 17 Aug 2012 Fixed
1.0.0 3778 17 Aug 2012 Fixed
Description
In the 'Backups' or 'Back Up & Restore' tabs of the Cloud Console, the backup validation result would have shown the result from the previous row if the backup had failed. This has been fixed



CR:717014
CR Number:   717014
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 4233 17 Aug 2012 Fixed
1.0.0 3778 17 Aug 2012 Fixed
Description
Under rare circumstances, incremental backups could have incorrectly been assigned to full backups, and/or created on the wrong host. This has been fixed.



CR:717024
CR Number:   717024
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3787 16 Aug 2012 Fixed
11.0.1 2867 16 Aug 2012 Fixed
Description
Attempting the execute a CREATE EXISTING TABLE that referenced a remote server using IBM's NotesSQL ODBC driver version 8.5.1 would have resulted in mangled column names. The statement would likely have failed with a Syntax error (SQLCODE=-131, ODBC 3 State=42000). This problem has now been fixed.



CR:717096
CR Number:   717096
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 3779 17 Aug 2012 Fixed
Description
The Export Wizard in the Interactive SQL utility had the "Include column names" check box incorrectly disabled when the user elected not to escape text data. These two options are, in fact, independent. Now, the "Include column names" check box is always enabled.



CR:717100
CR Number:   717100
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 3779 17 Aug 2012 Fixed
11.0.1 2857 17 Aug 2012 Fixed
Description
Unchecking the "Escape text data" box in the Export Wizard did not turn off escaping of text data. This has been corrected so that now it does.



CR:717187
CR Number:   717187
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 3779 20 Aug 2012 Fixed
11.0.1 2857 20 Aug 2012 Fixed
Description
The Interactive SQL utility's OUTPUT statement can write data to a text file. Special characters in the data can be escaped, or not, as specified by the ESCAPES clause. If ESCAPES OFF was specified, special characters were not escaped, but the quote character (an apostophe, by default) was not being doubled up as it should have been. As a result, the generated text file could not be subsequently processed by the INPUT statement because the quotes were not matched. This has been fixed.



CR:717313
CR Number:   717313
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 3781 22 Aug 2012 Fixed
11.0.1 2859 22 Aug 2012 Fixed
Description
Archive backups would have suspended checkpoints until the next COMMIT or ROLLBACK. This would have prevent checkpoints, and commands that implicitly issued checkpoints, from running until that point. This has been fixed.



CR:717316
CR Number:   717316
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 3784 29 Aug 2012 Fixed
11.0.1 2862 29 Aug 2012 Fixed
Description
In some circumstances, the server could have crashed, failed assertions, or rarely, could have returned incorrect data, when working with tables that contained more than eight thousand columns. This has been fixed.



Note, a database with more than eight thousand columns that is run with a server that contains this fix cannot be run on an older server. Doing so will result in startup error -1007 "Unable to start specified database: '%1' is an invalid transaction log" on the older, unfixed server.



CR:717363
CR Number:   717363
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 3789 10 Sep 2012 Fixed
11.0.1 2870 10 Sep 2012 Fixed
Description
The ADO.NET provider was generating inefficient queries, using CHARINDEX, for some Entity Framework functions, such as StartsWith, EndsWith, and Contains. This problem has been fixed.



CR:717377
CR Number:   717377
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 3803 21 Aug 2012 Fixed
Description
A query involving CASE or IF, with references to a sub-query, could have crashed UltraLite when the query was executed. This has been fixed.



CR:717388
CR Number:   717388
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Agent
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4240 22 Aug 2012 Fixed
1.0.0 3781 22 Aug 2012 Fixed
Description
If there were several system servers on a host, all of which were not running, the cloud agent may not have run an agent action on that host within the timeout period of the action. This has been fixed.



CR:717390
CR Number:   717390
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3781 22 Aug 2012 Fixed
11.0.1 2859 22 Aug 2012 Fixed
Description
The Support utility (dbsupport) could have crashed if Error Reporting server was down. This has been fixed.



CR:717474
CR Number:   717474
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Aug 2012 Fixed
Description
If an owner was given on a CREATE TABLE or CREATE VIEW statement within a CREATE SCHEMA statement, and the owner did not match the current user, the object was created anyway if the current user had DBA authority. This has been fixed so that objects cannot be created using CREATE SCHEMA for a user other than the current user.



CR:717497
CR Number:   717497
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
27 Aug 2012 Fixed
Description
A DESCRIBE of certain types of queries (eg. recursive) from an embedded SQL application could have resulted in the error -700: "SQLDA fields inconsistent for a multi-row SQLDA". This has been fixed.



CR:717545
CR Number:   717545
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Solaris
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3782 23 Aug 2012 Fixed
Description
On Solaris systems, the setup script run by the install would have failed with the message "Bad string" when run on systems with a multi-byte charset locale. This has been fixed.
Workaround Description
 Set the locals to a single-byte characterset.





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