远程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:727676
CR Number:   727676
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 1432 01 Feb 2013 Fixed
12.0.1 3852 01 Feb 2013 Fixed
11.0.1 2936 01 Feb 2013 Fixed
Description
The MobiLink Log File Viewer in Sybase Central was unable to read log files that contained lines which were longer than 8192 bytes. Now, lines up to 65536 bytes are supported.



Note, line length in log files can become very long when the MobiLink server "-vr" option (display column values) is used.



CR:727729
CR Number:   727729
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 3840 03 Jan 2013 Fixed
Description
Executing a specific statement involving DateTimeOffset and an empty HashSet in LINQ against the Entity Framework would have resulted in an "Unknown EdmType: DateTimeOffset" error. This has now been corrected.



CR:727737
CR Number:   727737
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)
16.0.0 1872 02 Apr 2014 Fixed
12.0.1 4095 02 Apr 2014 Fixed
Description
Some clauses of the CREATE SPATIAL REFERENCE SYSTEM statement were incorrectly recorded in the transaction log. This has been fixed



CR:727756
CR Number:   727756
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 3834 24 Dec 2012 Fixed
Description
With UltraLiteJ for Android, data synchronization over HTTPS using default trusted certificates from the system store would have failed on Android 4.0 (Ice Cream Sandwich) or later. The location of the system trusted certificate store, and APIs to retrieve certificates, changed in Ice Cream Sandwich. Now the Android version is detected at runtime to determine how to retrieve the certificates.



CR:727765
CR Number:   727765
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 3834 24 Dec 2012 Fixed
Description
If the SQLANY12 environment variable had a trailing slash, the path to the Driver= line in the DSN would have been constructed incorrectly by the Data Source utility (dbdsn). This has been fixed.



CR:727769
CR Number:   727769
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 3834 24 Dec 2012 Fixed
Description
When comparing databases, a CREATE TRIGGER statement would have been marked as an unrecognized statement if it included a trigger owner; for example, CREATE TRIGGER trigger-owner.trigger-name BEFORE INSERT ON table-owner.table-name... . This has been fixed.



Note that while the trigger owner is syntactically valid, it is ignored by the server.



CR:727777
CR Number:   727777
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 3834 24 Dec 2012 Fixed
Description
When comparing databases, applying the generated script to convert database 1 to database 2 would have failed if one database contained a table and the other database contained a view, such that the table and view shared the same owner and name. The same problem would also have occurred for procedures and functions. These problems have been fixed so that the generated script now contains the required statement to drop the object from database 1 before creating the object from database 2.



CR:727860
CR Number:   727860
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
In extremely rare timing dependent cases, a database server could have crashed if a mirrored database or mirror server was stopped, or dropped from the mirroring setup. This has been fixed.



Also in rare timing dependent cases, when dropping an arbiter server from a mirroring setup, it was possible for old state information to be left behind in the arbiter server抯 state file. This could have caused difficulties later on if the same server was started as a high availability server for the mirroring system. This has been fixed as well.



CR:728223
CR Number:   728223
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 1403 02 Jan 2013 Fixed
12.0.1 3839 02 Jan 2013 Fixed
Description
If an HTTP request was incorrectly formatted in a particular way, the server could have crashed. This has been fixed.



CR:728245
CR Number:   728245
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1403 03 Jan 2013 Fixed
Description
慏igital Signature?has been added to the default Key Usage for non-certificate authorities for the Certificate Creation utility (createcert). Some OpenSSL implementations return an error if the peer certificate does not have 慏igital Signature?in its key usage.



CR:728260
CR Number:   728260
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
In order to support better software protection from potential SQL injection threats, the following restriction will be applied to databases created by SQL Anywhere 16.0.0.



Identifiers:

The following characters are currently not permitted in identifiers:

Double quotes

Control characters (any character less than 0x20)

Backslashes

In addition to the above, the following characters will now not be permitted in an identifier:

Square brackets ([])

Back quotes (`)



Aliases:

1. select-list : expression [ [ AS ] alias-name ]

The new restrictions on identifiers now apply to the characters permitted in an alias-name.

2.select-list : alias-name = expression (Transact-SQL dialect)

The new restrictions on identifiers now apply to the characters permitted in a Transact-SQL dialect alias-name.



Notes:

New restrictions described above will only be applied if the database is created using SQL Anywhere 16.0.0 software.

Databases upgraded to version 16.0.0 as well as all databases created and/or upgraded to older versions will continue to apply the current restrictions and continue to allow newly prohibited characters inside identifiers and aliases.

If pre-version 16.0.0 database has any square brackets or back quotes in an identifier, they must be removed before performing a reload; otherwise the reload will fail.



CR:728261
CR Number:   728261
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3839 03 Jan 2013 Fixed
Description
The MobiLink Replay utility (mlreplay) was not sending liveness commands to the MobiLink server correctly when using HTTP. This has been fixed.



CR:728335
CR Number:   728335
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)
16.0.0 1405 04 Jan 2013 Fixed
12.0.1 3840 04 Jan 2013 Fixed
Description
When setting SAParameter.DbType to DbType.DateTime2, an IndexOutOfRangeException could have been thrown. The data type conversion was missing for DbType.DateTime2. This has now been corrected.



CR:728436
CR Number:   728436
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Importing TINYINT data using the INPUT statement would have caused the Interactive SQL utility to report an internal exception. This has been fixed.



CR:728446
CR Number:   728446
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1405 04 Jan 2013 Fixed
12.0.1 3840 04 Jan 2013 Fixed
Description
When the error message 揝QL statement failed: (-782) Cannot register 'sybase.asa.dbmlsync' since another exclusive instance is running?was generated and the database character set of the remote database was different from the OS character set, the message would be displayed in the wrong character set and may have been unreadable. This problem affected only this error message, and has now been fixed.



CR:728449
CR Number:   728449
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 3840 04 Jan 2013 Fixed
11.0.1 2923 04 Jan 2013 Fixed
Description
When using communication compression on HP-UX, or on Linux with a recent glibc version, a communication error could have occurred on the compressed connection. This has been fixed



CR:728458
CR Number:   728458
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 3840 07 Jan 2013 Fixed
11.0.1 2923 07 Jan 2013 Fixed
Description
The server may have behaved badly, including crashes or corruptions, when using a recent version of Linux with glibc 2.11 or higher. This has been fixed.



CR:728460
CR Number:   728460
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 1405 07 Jan 2013 Fixed
1.0.0 3840 07 Jan 2013 Fixed
Description
The UpgradeCloudInfrastructure event may have been logged as an error in the Cloud Console's Events & Tasks page even though the upgrade succeeded. If this was the case, the UpgradeCloudInfrastructure will have the red X icon indicating an error, even though all Subevents and related tasks were successful. This has been fixed.



CR:728589
CR Number:   728589
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)
16.0.0 1410 10 Jan 2013 Fixed
12.0.1 3842 10 Jan 2013 Fixed
11.0.1 2926 10 Jan 2013 Fixed
05 Mar 2013 Fixed
Description
Calling Entity Framework SaveChanges could have caused a NullReferenceException if the entity model had properties with 揻ixed?concurrency mode. This has now been fixed.



CR:728597
CR Number:   728597
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 3842 08 Jan 2013 Fixed
11.0.1 2926 08 Jan 2013 Fixed
Description
Crashes and data corruption were possible due to silent I/O failures on Red Hat Linux 6, as well as other Linux distributions with kernel versions greater than 2.6.38. The most likely manifestation of this bug was assertion 200505 ("checksum failure on page x").



This problem is related to a possible bug in the transparent huge pages (THP) feature introduced in these operating system versions. Red Hat bug 891857 has been created to track this issue.



The problem can be triggered by calling an external environment, xp_cmdshell, or other procedure that causes a fork while other I/O is occurring. A known limitation with the Linux kernel limits the use of fork while doing O_DIRECT I/O operations. Essentially what can happen is that the data can come from or go to the wrong process?memory after the fork. SQL Anywhere performs O_DIRECT I/O operations according to the documented safe usage. However, THP appears to cause further problems and the O_DIRECT I/O data comprising database page reads/writes appears to get lost.



This has been fixed by disabling THP on the SQL Anywhere cache memory where possible. We are working with Red Hat to identify a solution within the operating system.



There are two possible workarounds:

1. disable THP on a system-wide basis with one of the following methods:

echo never > /sys/kernel/mm/transparent_hugepage/enabled

echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled

boot with transparent_hugepage=never

2. disable O_DIRECT I/O for database file reads/writes with one of the following methods:

use the -u flag on the server command line

set SA_DISABLE_DIRECTIO=1 in the environment before starting the server



Transparent huge pages cannot be disabled just for the SQL Anywhere cache memory on Red Hat Enterprise Linux 6. SQL Anywhere now disables direct I/O if transparent huge pages are enabled and cannot be disabled on a per-allocation basis. A warning will be printed as the database file is being opened to indicate that direct I/O is disabled due to this bug. This is similar to how SQL Anywhere handles file systems that do not support direct I/O.



Customers using RHEL 6 who wish to continue using direct I/O should use the previously-stated command to disable THP at the system level.



CR:728720
CR Number:   728720
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)
16.0.0 1409 11 Jan 2013 Fixed
12.0.1 3842 11 Jan 2013 Fixed
Description
A long delay may have been observed when right-clicking in the SQL Statements panel, especially if the internet connection was slow, or if there was no internet connected at all. This has been fixed. Note, the problem does not occur if the documentation has been installed locally.



CR:728734
CR Number:   728734
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 3840 08 Jan 2013 Fixed
Description
Crashes and data corruption are possible due to silent I/O failures on Red Hat Linux 6, as well as other Linux distributions with kernel versions greater than 2.6.38. The most likely manifestation of this bug is assertion 200505 (checksum failure on page X).



This problem is related to a possible bug in the transparent huge pages (THP) feature introduced in these operating system versions. Red Hat bug 891857 has been created to track this issue.



The problem can be triggered by calling an external environment, xp_cmdshell, or other procedure that causes a fork while other I/O is occurring. A known limitation with the Linux kernel limits the use of fork while doing O_DIRECT I/O operations. Essentially what can happen is that the data can come from or go to the wrong process?memory after the fork. SQL Anywhere performs O_DIRECT I/O operations according to the documented safe usage. However, THP appears to cause further problems and the O_DIRECT I/O data comprising database page reads/writes appears to get lost.



Until this is fixed, there are two possible workarounds:

1. disable THP on a system-wide basis with one of the following methods:

echo never > /sys/kernel/mm/transparent_hugepage/enabled

echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled

boot with transparent_hugepage=never

2. disable O_DIRECT I/O for database file reads/writes with one of the following methods:

use the -u flag on the server command line

set SA_DISABLE_DIRECTIO=1 in the environment before starting the server



CR:728742
CR Number:   728742
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1537 02 May 2013 Fixed
12.0.1 3899 02 May 2013 Fixed
Description
If a database contained a materialized view that used key joins, then unloading and subsequently reloading the database would have failed. This problem has now been fixed.



CR:728776
CR Number:   728776
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1409 09 Jan 2013 Fixed
12.0.1 3842 09 Jan 2013 Fixed
11.0.1 2926 09 Jan 2013 Fixed
Description
Attempting to import data into a table for which the user did not have permission to select rows, they would have failed with the incorrect error message "The table you selected ... does not exist."



Similarly, the same bad error message would have been presented when exporting into a database table for which the user did not have permission to select rows.



These problems have been fixed. The error message now clearly indicates that you don't have permission to select from the table.



Users could encounter this problem when executing the INPUT or OUTPUT USING statements, or when using the Import or Export wizards.



CR:728789
CR Number:   728789
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1409 09 Jan 2013 Fixed
12.0.1 3842 09 Jan 2013 Fixed
Description
If the SQLCONNECT environment variable was used to specify default connection values, and the length of the SQLCONNECT value was greater than or equal to 255 bytes, the SQLCONNECT value was ignored. This has been fixed so that SQLCONNECT values up to a length of 1023 bytes are accepted.



CR:728863
CR Number:   728863
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3842 10 Jan 2013 Fixed
Description
A MobiLink client using HTTP could have hung, or an error could have been reported, when it automatically attempted to reestablish a lost connection. This has been fixed.



CR:728865
CR Number:   728865
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)
16.0.0 1410 10 Jan 2013 Fixed
Description
The Index Consultant would have reported an error message when opened if the SQL statement being analyzed contained a semicolon as part of an identifier name or a literal string. This has been fixed.



CR:728886
CR Number:   728886
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1418 17 Jan 2013 Fixed
12.0.1 3846 17 Jan 2013 Fixed
11.0.1 2930 17 Jan 2013 Fixed
Description
When the "Show all result sets" option is on, the Interactive SQL utility will display all the result sets returned by a query. If a statement produced more than one result set, and the Export Wizard was used to export those result sets, clicking the "Next" button on the first page would have returned an error saying that only one result set can be exported to an ODBC data source. This message would have been returned even when not exporting to a database. This has been fixed. The Export Wizard now supports exporting multiple result sets to text files, HTML files, and XML files.



CR:728972
CR Number:   728972
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1411 10 Jan 2013 Fixed
Description
The header for the first column (the row header "Property Name") of the Server and Database property lists could have been truncated if the header text was longer than the longest property name being shown in the table. This problem was readily apparent when running the program in French, but it affected all languages. This has been fixed. The first column is now sized wide enough for the header text and the names of the properties shown in the table.



CR:729006
CR Number:   729006
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 1412 11 Jan 2013 Fixed
12.0.1 3843 11 Jan 2013 Fixed
11.0.1 2927 11 Jan 2013 Fixed
Description
Creating a procedure with a right curly-bracket "}" in procedure_name(e.g CREATE PROCEDURE 揚1{}?)? would have failed. This has been fixed.



CR:729137
CR Number:   729137
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3843 14 Jan 2013 Fixed
Description
When running a non-English synchronization profile, attempts to synchronize an UltraLite database from the Sybase Central UltraLite plug-in, via the Synchronization wizard, could have failed with a message reporting that the synchronization profile can抰 be found (and the name of the profile will be mangled). This has been fixed.



CR:729261
CR Number:   729261
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)
Description
If a server was running with IP address monitoring enabled, the server could have crashed if more than one IP address was removed from the machine within the IP address monitoring period (default 2 minutes). This could have happened if the machine was suspended or hibernated and moved to another network where more than one of the previous IP addresses were no longer available. This has been fixed.



CR:729292
CR Number:   729292
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3844 15 Jan 2013 Fixed
11.0.1 2928 15 Jan 2013 Fixed
Description
The unload support utility for pre-10.0 database (dbunlspt) may have behaved badly, including crashing, failing assertions, or database file corruption, when using a recent version of Linux with glibc 2.11 or higher. This has been fixed.



CR:729394
CR Number:   729394
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 3845 15 Jan 2013 Fixed
11.0.1 2929 15 Jan 2013 Fixed
Description
In very rare cases, a database could have failed to start with the error "Fatal error: undo log corrupted after log rename". In order for this to have occurred, all of the following needed to be true:

1) a connection to the database had an outstanding transaction

2) while there was this outstanding transaction, the transaction log was renamed or truncated

3) the database had no free pages and needed to grow during the checkpoint that was part of renaming or truncating the transaction log

4) the connection from 1) still had an outstanding transaction during the last checkpoint before the database stopped or was backed up

5) the database was not shut down cleanly, or it was backed up

6) attempting to start the database from 5) required recovery and could have in rare cases failed with the error "Fatal error: undo log corrupted after log rename".



Other failures may have been possible if all of the above conditions applied. This has been fixed to avoid corrupting the undo log.



CR:729396
CR Number:   729396
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 3845 15 Jan 2013 Fixed
Description
Attempting to fetch the 揚RECISION?column of the DatabaseMetaData.getTypeInfo() result set, using one of the ResultSet.getXXX( String ) methods, would have resulted in the incorrct error: 揷olumn number 0 is invalid? Using one of the ResultSet.getXXX( int ) methods would have worked fine. This problem has been fixed.



CR:729427
CR Number:   729427
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)
16.0.0 1423 23 Jan 2013 Fixed
12.0.1 3848 23 Jan 2013 Fixed
11.0.1 2932 23 Jan 2013 Fixed
Description
The MobiLink server could have crashed when using HTTP and a misconfigured HTTP proxy. The server now reports an error and kills the synchronization when this occurs.



CR:729541
CR Number:   729541
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 Relay Server mistakenly logged session errors from the Outbound Enabler as a failure in initializing the random number generator. This has been fixed.



CR:729556
CR Number:   729556
Product Name:   UltraLite
Product Component:   SQL Preprocessor
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1417 17 Jan 2013 Fixed
12.0.1 3845 17 Jan 2013 Fixed
Description
The UltraLite runtime could have caused an application to crash during the optimization of a query with many JOINs (typically more than 12). This has been fixed.



CR:729661
CR Number:   729661
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 17 Jan 2013 Fixed
12.0.1 846 17 Jan 2013 Fixed
Description
If the host running the cloud primary had a large number of IPv4 and IPv6 addresses, then there was a chance that other cloud servers would have failed to start up because they could not connect to the cloud primary. This problem has now been fixed.



CR:729777
CR Number:   729777
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 1443 13 Feb 2013 Fixed
12.0.1 3856 13 Feb 2013 Fixed
Description
The "Overview" panel for a database shows the mirrored state of a database. If the deprecated command line option "-xp{partner=...;arbiter=...}" were specified, the mirroring configuration was not shown on the "Overview" panel. This has been corrected so that now it is.



CR:729836
CR Number:   729836
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 1419 21 Jan 2013 Fixed
1.0.0 3846 21 Jan 2013 Fixed
Description
In some situations dbcloudarbiterstate.txt was not preserved properly while running RepairServer task. This has been fixed.



CR:729852
CR Number:   729852
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)
16.0.0 1419 18 Jan 2013 Fixed
12.0.1 3846 18 Jan 2013 Fixed
Description
The Text Completer has an option to open automatically when typing to suggest object names. Opening the Query Editor window had an inadvertent side-effect of always turning off this option. This has been fixed so the Query Editor no longer permanently turns off the option.



CR:729867
CR Number:   729867
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)
16.0.0 1422 22 Jan 2013 Fixed
12.0.1 3847 22 Jan 2013 Fixed
Description
After calling the system procedure sa_server_option( 慠equestTiming? ... ), connections may have gathered or returned request timing values inconsistently. In particular, request timing may have been enabled when the connection was established but disabled immediately after changing the option, or request timing may have been disabled when the connect was established but ignored when the option was enabled. Also, if a pooled connection was reused, the values tracked by request timing where not reset as they would be if a new connection was established. This has been fixed so that request timing is enabled or disabled at connect time (including when reusing a pooled connection). Once the connection has been established, request timing will remain enabled or disabled for the connection until it is disconnected, regardless of sa_server_option( 慠equestTiming? ... ) calls during the life of the connection. In addition, if a pooled connection is reused when request timing is enabled, the values tracked by request timing are reset.



Note that the database and server properties that correspond to those enabled by the 杬t server option are only updated for connections that have request timing enabled or disabled at their individual connection time.



CR:729869
CR Number:   729869
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)
16.0.0 1419 21 Jan 2013 Fixed
12.0.1 3846 21 Jan 2013 Fixed
Description
The Relay Server converted server responses containing malformed headers into a '400 Bad Request' response without logging an error. This fix added a new RSE_CLIENT_RESPONSE_HEADER_ERR(4016) error when this now happens.



CR:729871
CR Number:   729871
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)
16.0.0 1419 21 Jan 2013 Fixed
12.0.1 3846 21 Jan 2013 Fixed
Description
The Relay Server was considering server responses that contained headers with empty values as malformed, and was converting the responses to a '400 Bad Request' response. This fix is to relax this case and relay the response without changing it or raising an error.



CR:729873
CR Number:   729873
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)
16.0.0 1419 21 Jan 2013 Fixed
12.0.1 3846 21 Jan 2013 Fixed
Description
The Relay Server automatically sends down instruction to the client to expire the affinity cookie when the backend server response code falls into the error range, except for 401 and 407 authentication challenges. Debug information of this expiring activity was not available in the Relay Server log at any verbosity level. This fix is to add a message at verbosity 4 and above for this activity.



CR:729894
CR Number:   729894
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)
16.0.0 1419 21 Jan 2013 Fixed
Description
The error ID and error name column in the Relay Server Record did not capture RSE4008 and RSE4016. This has been fixed.



CR:730023
CR Number:   730023
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3847 22 Jan 2013 Fixed
Description
The SQL Anywhere JDBC Driver would have thrown a SQLException with a 揘ot Implemented?message when calling an optional JDBC method that was not supported by the JDBC Driver. This has been corrected so that the JDBC 4.0 SQL Anywhere JDBC Driver now throws the new SQLFeatureNotSupportedException. Since SQLFeatureNotSupportedException is a JDBC 4.0 feature, the JDBC 3.0 Driver will continue to throw a SQLException instead.



CR:730024
CR Number:   730024
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3847 22 Jan 2013 Fixed
Description
The SQL Anywhere JDBC Driver would have incorrectly throw a 揘ot Implemented?exception when PreparedStatement.setNull() was called with either java.sql.Types.BLOB or java.sql.Types.CLOB. This problem has now been fixed.



CR:730094
CR Number:   730094
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)
16.0.0 1423 23 Jan 2013 Fixed
Description
When the Relay Server encountered an invalid SAP Passport, it would have reported an error in English without providing an error code, while continuing to relay the request. This has been fixed by replacing the error with a localized warning RSW104 indicating that an invalid passport has been ignored.



CR:730111
CR Number:   730111
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 1423 28 Jan 2013 Fixed
12.0.1 3849 28 Jan 2013 Fixed
Description
Attempting to creating a primary key on a table with an existing primary key could have return an 揑ndex name not unique?error, rather than an error reporting the existence of a primary key. This has been fixed.



CR:730134
CR Number:   730134
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)
16.0.0 1423 23 Jan 2013 Fixed
Description
When a relay error occured early enough, there may not have been enough information to calculate the relay KPI. The result was a wrong KPI value shown in the Relay Server record. This has been fixed by replacing the wrong value with zero when the KPI cannot be calculated due to a failure. The occurrence of the error is already recorded in the same RSR.



CR:730149
CR Number:   730149
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 1445 14 Feb 2013 Fixed
12.0.1 3857 14 Feb 2013 Fixed
11.0.1 2942 14 Feb 2013 Fixed
Description
On rare occasions the server would have crashed on shutdown when running on Linux systems. The crash would have occurred when stopping shared memory connections. This problem has now been fixed.



CR:730237
CR Number:   730237
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)
16.0.0 1584 27 Jun 2013 Fixed
Description
The SQL Anywhere topology widget height did not show all nodes without scrolling the widget. This has now been fixed to initially show all child nodes.



CR:730248
CR Number:   730248
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1423 24 Jan 2013 Fixed
12.0.1 3848 24 Jan 2013 Fixed
Description
When using the table editor to change a column抯 data type, Sybase Central could have crashed if a domain had previously been created in the same Sybase Central session. This has been fixed.



CR:730250
CR Number:   730250
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1423 24 Jan 2013 Fixed
12.0.1 3848 24 Jan 2013 Fixed
Description
Attempting to delete one or more objects by selecting the objects, pressing the Delete key, and then quickly pressing the Y key to confirm the deletion before the confirm dialog was displayed, could have caused Sybase Central to crash. This has been fixed.



CR:730251
CR Number:   730251
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 1418 23 Jan 2013 Fixed
Description
The Upgrade Database wizard could not have been used to upgrade a database unless the user was granted exercise rights on the SERVER OPERATOR system privilege, even though the wizard didn抰 make use of this system privilege. Now the wizard no longer requires the SERVER OPERATOR system privilege.



CR:730270
CR Number:   730270
Product Name:   SQL Remote for SQL Anywhere
Product Component:   File Messaging for Adaptive Server Anywhere
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1436 04 Feb 2013 Fixed
12.0.1 3850 06 Feb 2013 Fixed
11.0.1 2914 06 Feb 2013 Fixed
Description
SQL Remote always assumes that all databases involved in replication share the same character set. By default, SQL Remote will always apply source CHAR data to a target database using the default character set for the operating system it is running on, ignoring the source data character set.



When using a database character set that is different than the default character set for the operating system, dbremote must be instructed to perform explicit data conversion to that character set on its connection string:



e.g. dbremote -c 揅HARSET=utf8;厰



or instruct dbremote to always use the CHAR character set of the target database to apply the remote CHAR data:



e.g. dbremote -c 揅HARSET=none;厰



CR:730271
CR Number:   730271
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)
16.0.0 1423 24 Jan 2013 Fixed
12.0.1 3848 24 Jan 2013 Fixed
Description
Syncs could have failed when using HTTP and using an HTTP intermediary that was setting a 揅onnection: Keep-alive?header, but was actually creating a new connection for each HTTP request. This has now been corrected.



CR:730384
CR Number:   730384
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3849 28 Jan 2013 Fixed
Description
Pressing the F1 key while an error window was open after executing a SQL statement with the Interactive SQL utility, would have cased dbisql to crash. This has been fixed.



CR:730475
CR Number:   730475
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1426 28 Jan 2013 Fixed
12.0.1 3849 28 Jan 2013 Fixed
Description
When viewing a NULL binary value in the Long Value window, the Save button was incorrectly enabled. If the Save button was clicked, Interactive SQL would have crashed. This has been fixed;. Now, the button is not enabled if the value is NULL.



CR:730485
CR Number:   730485
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)
16.0.0 1426 28 Jan 2013 Fixed
12.0.1 3849 28 Jan 2013 Fixed
Description
The Interactive SQL utility shows result sets using a scrollable table, which can be searched. With "Match case" selected in the "Find in Results" window, dbisql would still have performed a case-insensitive search. This has been fixed.



Also, It was possible for the table cell which contained the matched text to be hidden under the "Find in Results" window. Now, the window is automatically moved out of the way.



CR:730642
CR Number:   730642
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)
16.0.0 1431 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
Description
If multiple threads attempted to access a connection pool concurrently (by modifying it to add/remove a connection), an InvalidOperationException would have been thrown. This has been corrected.



CR:730652
CR Number:   730652
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)
16.0.0 1429 29 Jan 2013 Fixed
Description
If the Fast Launcher was enabled, but was unable to initialize, the Interactive SQL utility or Sybase Central would have crashed when the Fast Launcher was subsequently disabled. This has been fixed.



CR:730761
CR Number:   730761
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 3851 30 Jan 2013 Fixed
Description
If the Unix setup script was run from a path containing spaces (including the default behaviour for the Mac DMG file), it would not have run correctly. One example of bad behaviour was improper display of the version numbers. The graphical installers would also have failed to display the license text properly. This has been fixed.



CR:730762
CR Number:   730762
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1430 30 Jan 2013 Fixed
12.0.1 3851 30 Jan 2013 Fixed
11.0.1 2935 30 Jan 2013 Fixed
Description
In the Breakpoints window, selecting an existing breakpoint to edit may not have selected the right server name. This has been fixed.



CR:730770
CR Number:   730770
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 3851 30 Jan 2013 Fixed
16.0.0 1430 02 May 2013 Fixed
Description
The Relay Server for IIS may have leaked memory. This has been fixed.
Workaround Description
 The Relay server for IIS may have leaked memory.



CR:730776
CR Number:   730776
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 1431 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
Description
In very rare, timing dependent cases, it was possible for one or more copy nodes to have failed an assertion after the primary was shutdown and the mirror took over as the primary. The assertion would have indicated a problem applying operations from the transaction log (for example assertion 100903). This problem has now been corrected.



CR:730783
CR Number:   730783
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)
16.0.0 1430 30 Jan 2013 Fixed
12.0.1 3851 30 Jan 2013 Fixed
Description
In rare circumstances, synchronizations could have failed if another thread was performing operations on the database at the same time. This has been fixed.



CR:730785
CR Number:   730785
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 3851 30 Jan 2013 Fixed
Description
The Deployment wizard may not have worked corrctly on UNIX platforms. The version number may not have been displayed correctly and/or the list of components may have been empty. This has now been fixed.



CR:730789
CR Number:   730789
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)
16.0.0 1430 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
Description
The INPUT statement and the Import wizard could have failed while importing spatial data if the source column did not have a SRID constraint, the data contained an embedded non-zero SRID, and Interactive SQL was creating a new table to hold the imported data. This has now been fixed.



CR:730797
CR Number:   730797
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)
16.0.0 1430 30 Jan 2013 Fixed
12.0.1 3851 30 Jan 2013 Fixed
11.0.1 2935 30 Jan 2013 Fixed
Description
The fix for Engineering case 728776 introduced a bug which caused the CREATE TABLE ON clause of the INPUT statement to fail with a message saying that the destination table did not exist. This has been fixed.



CR:730800
CR Number:   730800
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)
16.0.0 1430 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
11.0.1 2935 31 Jan 2013 Fixed
Description
Some uniqueidentifier column values could have been displayed as "(IMAGE)" in the result set table. This has been fixed.



CR:730890
CR Number:   730890
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 1431 30 Jan 2013 Fixed
Description
When displaying the last state change time for LDAP servers, the values displayed in the LDAP Servers folder did not include a time zone, while the values displayed on the LDAP server property sheet included the server抯 time zone, which was incorrect. Now the values clearly indicate that LDAP server last state change times are in Coordinated Universal Time (UTC).



CR:730893
CR Number:   730893
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)
16.0.0 1430 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
11.0.1 2935 31 Jan 2013 Fixed
Description
On the Create Database wizard抯 揅onnect to the Database?page, the server name shown would have been incorrect if a new local server was started, then the database creation was cancelled and the database file name was changed. This has been fixed.



CR:730896
CR Number:   730896
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 1431 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
Description
On the Fragmentation tab for a database, selecting a table or index in the list and then attempting to change the selection while the previous selection抯 bitmap was being loaded, may have caused Sybase Central to hang until the loading completed. This has been fixed. Now the loading of the previous selection抯 bitmap is canceled and the loading of the new selection抯 bitmap is started.



CR:730900
CR Number:   730900
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Jan 2013 Fixed
Description
When attempting to connect to two databases with the same server and database names, but with the servers on different subnets, Sybase Central would have reported 揧ou are already connected to this database?when the second connection was attempted. This has been fixed. Now Sybase Central will connect to both databases as long as the servers?machine names differ.



CR:730907
CR Number:   730907
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1431 30 Jan 2013 Fixed
12.0.1 3851 30 Jan 2013 Fixed
Description
When selecting the Data tab for a table or view, clicking Cancel in the 揕oading Data?dialog then attempting to fetch the Data didn't always cancel the loading. This has now been corrected.



CR:730919
CR Number:   730919
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)
16.0.0 1432 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
Description
Clicking the Cancel button in the Spatial Viewer window could have failed to cancel the execution. At that point, the Spatial Viewer could not then be closed. This problem has been fixed, and execution can now be cancelled.



CR:730928
CR Number:   730928
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)
16.0.0 1431 31 Jan 2013 Fixed
12.0.1 3851 31 Jan 2013 Fixed
Description
The Interactive SQL utility could have crashed when viewing binary values if the long value window was closed before the server returned the complete cell value. This has been fixed.



CR:730932
CR Number:   730932
Product Name:   UltraLite
Product Component:   UL Java Provider for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1432 01 Feb 2013 Fixed
Description
When working with an UltraLite database from Sybase Central or the Interactive SQL utility, some errors displayed by those tools may now display slightly different (more detailed) information in the error message.



CR:731014
CR Number:   731014
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
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
Description
If the MobiLink server had been started with a command line in which the maximum number of concurrent database worker threads (-wm option) was a value less than the initial number of concurrent database worker threads (-w option, default value 5), then the MobiLink Server would have failed to start. The MobiLink Server will now print a warning to the MobiLink Server log indicating that it has reduced the initial number of concurrent database worker threads to the maximum number of concurrent database worker threads that was specified on the command line.



CR:731017
CR Number:   731017
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 1432 01 Feb 2013 Fixed
Description
On the Grantees, Roles or System Privileges tabs for a user, role or system privilege, if the New Grantees/Granted Roles/Granted System Privileges dialog was opened and an object was selected for which there was already a row in the privilege editor, then no privileges would have been granted. This has been fixed.



CR:731021
CR Number:   731021
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 1432 01 Feb 2013 Fixed
Description
On the Grantees, Roles or System Privileges tabs for a user, role or system privilege, the Grantor was not shown until the changes were saved to the database. This has been fixed.



CR:731040
CR Number:   731040
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 1432 01 Feb 2013 Fixed
1.0.0 3852 01 Feb 2013 Fixed
Description
When using the SQL Anywhere On-Demand edition with a cloud that had reduced functionality because it had not been activated following 1000 core hours use, it was not possible to update the proxy settings for the cloud. As a consequence, the cloud could not be activated if the proxy settings were incorrect. The AlterCloud task is now permitted when the cloud has entered reduced functionality.



CR:731071
CR Number:   731071
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1432 01 Feb 2013 Fixed
Description
When connected to an SAP HANA database, attempting to display BINARY, VARBINARY, or LONG VARBINARY data would have resulted in a message saying that the result set could not be displayed. This has been fixed.



CR:731172
CR Number:   731172
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1433 05 Feb 2013 Fixed
Description
The Interactive SQL utility did not display BLOB types of data from SAP HANA tables correctly. This has been fixed.



CR:731199
CR Number:   731199
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1433 01 Feb 2013 Fixed
Description
Attempting to connect to a SAP HANA database using a system ODBC data source, would have failed with a message which said that the host name and port were missing. This has been fixed.



Note that connecting using user data sources worked as expected. If was only system data sources that were affected by this problem.



CR:731211
CR Number:   731211
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)
16.0.0 1479 01 Mar 2013 Fixed
12.0.1 3871 14 Mar 2013 Fixed
11.0.1 2949 14 Mar 2013 Fixed
Description
A query of the form 搒elect * from T, R where T.X IN (R.X, T.Y )?may have had a suboptimal execution plan if an index existed on the column T.X. This has been fixed.



CR:731291
CR Number:   731291
Product Name:   SQL Anywhere
Product Component:   OData Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1447 05 Feb 2013 Fixed
Description
The producer configuration option ServiceRoot, as used by the OData Server, was ignored and the default /odata was always used. This has been fixed.



CR:731308
CR Number:   731308
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1436 05 Feb 2013 Fixed
Description
When working with the MobiLink plug-in, a connection to a consolidated database is usually required. The connection is opened automatically when it is needed. If the saved connection information is no longer sufficient, the "Connect" window opens to prompt for credentials. If the "Connect" window opened as a result of testing a synchronization model, it could have opened behind a status window which was opened by the Test window. This would have prevented the entering of database credentials, and the software would subsequently have reported an internal error. This has been fixed.



CR:731334
CR Number:   731334
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1436 06 Feb 2013 Fixed
Description
If a SQL Anywhere 16 database was created with 揹binit -pd?or 揅REATE DATABASE ?SYSTEM PROCEDURE AS DEFINER ON? or if an older database was upgraded using 揹bupgrad -pd y?or 揂LTER DATABASE UPGRADE ?SYSTEM PROCEDURE AS DEFINER ON? then attempting to perform a 揊ORWARD TO? or make use of any of the sp_remote_... procedures, would have failed with an invalid userid or password error. This problem has now been fixed. A database upgrade will be required to apply this fix.



Note that two possible workarounds are:

1) create an externlogin for dbo, or

2) set the new extern_login_credentials database option to 揕ogin_user?



CR:731345
CR Number:   731345
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1480 06 Feb 2013 Fixed
Description
Sybase Central could have crashed while testing a synchronization model if a test synchronization was cancelled while rows were being fetched for the "Data" tab, and if the database server was a little slow in returning the data. This has been fixed.



CR:731386
CR Number:   731386
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 1478 05 Feb 2013 Fixed
Description
When comparing databases, if the parser encountered a COMMENT ON statement for which the corresponding CREATE <object-type> statement could not be found, then an 揢nknown error?would have been reported. Now the COMMENT ON statement is reported in the SQL Scripts tab as an unhandled statement.



CR:731448
CR Number:   731448
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1437 06 Feb 2013 Fixed
Description
Execution of loops with a large number of iterations could have been slower in 16.0.0 than in 12.0.1. For the problem to have occurred, the loop condition, or statements executed in the loop, had to use variables. This has been fixed.



CR:731461
CR Number:   731461
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)
16.0.0 1443 12 Feb 2013 Fixed
12.0.1 3856 12 Feb 2013 Fixed
Description
ADO.NET provider did not convert 憈imestamp with timezone?values correctly when the regional date settings of the client did not match the date settings of the database. The provider will now return .NET DateTimeOffset values to the client. The client can then convert the .NET DateTimeOffset values to a desired format.



CR:731483
CR Number:   731483
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 1632 09 Aug 2013 Fixed
12.0.1 3951 09 Aug 2013 Fixed
Description
Several issues with database mirroring and read-only scale-out have now been fixed.



1) If the mirror or copy node was requesting pages from the primary or parent (it had recently started and had not caught up to the current log operation) and renamed log files required by the mirror or copy node had been deleted on the primary or parent since the mirror or copy node started requesting pages, then the mirror or copy node could have stopped applying log operations or failed with the assertion 100904. This has been fixed so that that primary or parent now correctly detects this case (a required renamed log file has been deleted) and logs the message "Database <DBName> mirroring: failure when requesting pages on remote server <ServerName>: missing transaction log with start offset <Offset>" (where <DBName>, <ServerName> and <Offset> are replaced with appropriate values). If this occurs, the mirror or copy node will log the message " Database "asatest" mirroring: database is not compatible with primary; files must be replaced?and the database and possibly the server will stop.



2) The message "Database server shutdown due to incompatible files for database mirroring?could have been displayed if an incompatible log file was detected even though the server was not stopped. If there is more than one database running on the server, the affected database is stopped, but the server is not stopped. This has been fixed so that this message is only logged if the server is actually being stopped.



3) In rare timing depending cases, after one or more ALTER DATABASE SET PARTNER FAILOVER statements, neither partner could have taken the role of primary. This has been fixed. As a workaround, the ALTER DATABASE ... FORCE START statement can be used to force a partner to take over as partner if this problem occurred.



4) If a copy node or async mirror got significantly behind writing log pages, it could have caused requests to the primary database to block for more than a minute. This has been fixed so that the primary will not be blocked for more than about 10 seconds.



CR:731504
CR Number:   731504
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 1437 06 Feb 2013 Fixed
Description
When comparing databases, if the source or definition for a procedure, function, view, materialized view, trigger or event contained a multi-line comment with a line that contained only the text 揼o? then Sybase Central would have reported that it had encountered an unhandled statements. This has been fixed.



CR:731600
CR Number:   731600
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1438 07 Feb 2013 Fixed
Description
When creating a MobiLink project, or when adding a consolidated database to a project, an inappropriate error message could have been raised saying that a database connection could not be made. The problem was specific to connecting to databases using an ODBC Data Source which contained a user id, and not giving a user id in the new project and add consolidated database wizards. This has been fixed.



CR:731731
CR Number:   731731
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 1439 07 Feb 2013 Fixed
12.0.1 3855 07 Feb 2013 Fixed
11.0.1 2970 06 Mar 2013 Fixed
Description
When running on Solaris systems, if the server had accepted a new connection, but the client side closed its socket right away, the TCP listener would have been stopped and the message "TCP Listener shutting down (130)" was be displayed on the server console. 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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------