远程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:707006
CR Number:   707006
Product Name:   SQL Anywhere
Product Component:   Documentation
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 May 2012 Fixed
Description
-



CR:707009
CR Number:   707009
Product Name:   SQL Anywhere
Product Component:   Documentation
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 May 2012 DEFER
Description
-



CR:707010
CR Number:   707010
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3744 12 Jun 2012 Fixed
Description
In the table of query results, cell values, entire rows, and entire columns, can be copied to the clipboard. When copying a column or multiple cells, the values were always separated by a comma rather than the ISQL field separator string. This has been corrected so that the field separator is now used.



Note that the field separator was already being used when copying entire rows of values.



CR:707019
CR Number:   707019
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 3664 02 May 2012 Fixed
11.0.1 2807 02 May 2012 Fixed
Description
When the database server was running a database whose page size was smaller than the cache's page size, dynamic cache sizing could have chosen a cache size that was too small, which could have resulted in a performance penalty. This problem has been fixed.



CR:707033
CR Number:   707033
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 3728 03 May 2012 Fixed
Description
When a property was repeated in a section of the Relay Server configuration file, or when a section header separating two sections of the same type of object was missing, the Relay Server would have started without complaints, silently overriding repeated properties. This behaviour has now been corrected to abort the startup with an error.



CR:707037
CR Number:   707037
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 3672 03 May 2012 Fixed
11.0.1 2811 09 May 2012 Fixed
Description
In rare timing dependent cases, a high availability partner or copy node server could have crashed. Additionally, in rare cases, the arbiter could have reported the following message to the console: "arbiter already has two connections". These problems could have occurred when a partner detected loss of quorum, when a copy node was attempting to connect back to its original parent after being connection to an alternate parent or the root server, or if a connection between mirror servers failed. This has been fixed.



CR:707039
CR Number:   707039
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3728 02 May 2012 Fixed
Description
Synchronizations could have hung when using HTTP if an error occurred on the server side. This has been fixed.



CR:707061
CR Number:   707061
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3728 03 May 2012 Fixed
11.0.1 2807 03 May 2012 Fixed
Description
The MobiLink server could have crashed if it had an HTTPS listening port. This has been fixed.



CR:707064
CR Number:   707064
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 3729 03 May 2012 Fixed
Description
When starting the Network Server on Windows, or calculating the 'IsPortableDevice' server property, the server may have taken longer than necessary to obtain information about the computer. This has been fixed, althought the difference in the delay is not likely to be noticeable.



CR:707078
CR Number:   707078
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 3728 03 May 2012 Fixed
Description
When a Relay Server received a request with cookie pointing to a backend that was no longer connected, the Relay Server would have done unnecessary processing and reported twice the request to be aborted with verbosity level 2 or higher. This extra processing has now been removed.



CR:707124
CR Number:   707124
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 3729 03 May 2012 Fixed
Description
Mixing different versions of Relay Server components together on a single server is not supported and may have lead to crashes in some combinations. Now, the SQL Anywhere version and build number are used to detect conflicts. Any conflicts are reported via the following HTTP response status:

500 Abort due to version of this Relay Server extension conflicts with the version of the running rshost



Note, this change also fixes some error responses that didn't terminate the header list with \r\n.



CR:707201
CR Number:   707201
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3729 04 May 2012 Fixed
12.0.0 2790 04 May 2012 Fixed
11.0.1 2808 04 May 2012 Fixed
Description
In rare low-memory situations, a client application could have crashed on startup if TCP/IP was being used. This has now been fixed.



CR:707362
CR Number:   707362
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3729 04 May 2012 Fixed
Description
On BlackBerry devices, and the simulator, when using HTTPS UltraLiteJ would have done an extra HTTPS POST request at the beginning of a synchronization to verify the contents of a certificate. This extra POST was not needed when the StreamHTTPSParms used in the synchronization had null CertificateCompany, CertificateName and CertificateUnit (all three null). This has been fixed. UltraLiteJ now will only do the extra POST if one or more of CertificateCompany, CertificateName and/or CertificateUnit are not null.



CR:707529
CR Number:   707529
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 3670 08 May 2012 Fixed
11.0.1 2810 08 May 2012 Fixed
Description
If the primary server failed in some timing dependent cases, the mirror server could have failed to take over as primary. When this problem occurred, the mirror database would have restarted and be attempting to determine its role until the primary was restarted, or the ALTER DATABASE ... FORCE START statement was executed on the mirror server. This has been fixed.



CR:707534
CR Number:   707534
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 3729 07 May 2012 Fixed
Description
The Relay Server is designed to overload the up-channel liveness for notifing the Outbound Enabler in the case the down-channel is not connected. This gives the Outbound Enabler a chance to increase down-channel puncture data, as the web server can be be set up to buffer the request to a certain amount before passing to the extension for handling and takeover the rest of the reading of the request. This issue was introduced in 12.0.1 when HTTP authentication support was added to the Outbound Enabler, where the test request will fool the Relay Server into thinking the down-channel connection was successful. This fix is to change the Relay Server to deal with the Outbound Enabler behavior change.



CR:707541
CR Number:   707541
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 3729 07 May 2012 Fixed
Description
Unnecessary HTTP headers were being sent in HTTP CONNECT requests. This has been fixed.



CR:707553
CR Number:   707553
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 3729 09 May 2012 Fixed
Description
In rare cases, the first time a mirror server or copy node connected to a high availability primary or a read-only scale-out parent, the primary or parent could have crashed. This has been fixed.



CR:707554
CR Number:   707554
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 3729 08 May 2012 Fixed
Description
The following improvements have been made to the interactive quick setup feature for the Relay Server running on an Apache web server:

- Improved script interaction, especially questions with (Y/n) choices. Defaults have been added to speed up progress.

- Output log is now flushed timely to give complete log if script is stopped at any time.

- Removed the option of keeping test services running to overcome a hanging problem.

- Wording has been improved in several places.



CR:707729
CR Number:   707729
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 3730 09 May 2012 Fixed
Description
The Relay Server may have exhibited undefined response behavior in some error cases. This has been corrected.



CR:707781
CR Number:   707781
Product Name:   MobiLink
Product Component:   iAS Branded ODBC Drivers
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3764 12 Jun 2012 Fixed
12.0.1 2801 17 Jul 2012 Fixed
Description
The iAS ODBC driver for Oracle could have crashed in the OCI library when a query contained results from a proxy server if the size of the result set was greater than the "Array size" given by the DSN. This problem has now been fixed.



CR:707904
CR Number:   707904
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 3679 11 May 2012 Fixed
Description
If the root database restarted soon after a copy node connected to it, the copy node could have, in rare timing dependent cases, crashed or failed assertions. This has been fixed.



CR:707910
CR Number:   707910
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3736 23 May 2012 Fixed
Description
A query with many nested UNION query blocks may have taken a very long time before query execution began. This has been fixed.



CR:707918
CR Number:   707918
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 24 Jul 2012 Fixed
12.0.0 2802 24 Jul 2012 Fixed
11.0.1 2845 24 Jul 2012 Fixed
Description
In rare cases, a query using a parallel NestedLloopsJoin could have caused the server to crash. This has been fixed.



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



CR:707922
CR Number:   707922
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 3732 15 May 2012 Fixed
12.0.0 2791 15 May 2012 Fixed
11.0.1 2813 15 May 2012 Fixed
Description
UPDATE statements generated by the Entity Framework could have failed with a syntax error if the table being updated had a uniqueidentifier key column. This problem has been fixed.



CR:707952
CR Number:   707952
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3731 11 May 2012 Fixed
12.0.0 2791 11 May 2012 Fixed
11.0.1 2812 11 May 2012 Fixed
10.0.1 4329 11 May 2012 Fixed
Description
When using a version 10.0, 11.0 or 12.0 of ADO.NET provider with a version 9.0 server, the .NET string parameters are incorrect mapped to nvarchar. This problem has been fixed.



CR:707971
CR Number:   707971
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 3731 11 May 2012 Fixed
Description
The Compare Databases window would have reported ALTER LOGIN POLICY as an unrecognized statement. This has been corrected.



CR:708057
CR Number:   708057
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 3748 18 Jun 2012 Fixed
Description
When fetching from a directory access table with a query of the form:

select ... from directory_access_table where ... file_name like 'abc%' ...



the server would have returned a syntax error. This problem only existed if the comparison value (i.e. 'abc%') had no directory separators. For example, a query of the form:



select ... from directory_access_table where ... file_name like 'abc\def%' ...



would have worked just fine. This problem has now been fixed.



CR:708087
CR Number:   708087
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 3736 22 May 2012 Fixed
Description
When using the VALIDATE TABLE or VALIDATE INDEX statements, the server could have reported that there was an 'orphaned blob' (ie. a blob that is in the database but not referenced by any row) when there were, in fact, no orphaned blobs. To encounter this problem, there must have been deleted rows in the database that contained unique blobs (not shared by any other row) and either the deletes were uncommitted, or they had been left for the database cleaner to remove at a later time. Rows not cleaned by the cleaner were more likely to be seen on a read-only database, as the database cleaner is disabled for read-only databases. This problem has been fixed.



Also when using the VALIDATE TABLE or VALIDATE INDEX statements, the server could fail to report orphaned blobs when they did, in fact, exist. Whether or not this problem occurred depended on random contents of memory as well as the number of DML operations applied to the table prior to validation. This problem has been fixed.



When reporting a validation problem, the server returns an error to the client but also displays additional information in the server console. For orphaned blobs, a blank message was erroneously displayed in the console. This problem has been fixed.



CR:708177
CR Number:   708177
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)
4.0 3732 14 May 2012 Fixed
Description
If an invalid operation was specified for an SQL sequence, then the server would have incorrectly returned the error SQLSTATE_CORRELATION_NAME_NOT_FOUND, instead of SQLSTATE_INVALID_SEQUENCE_OPERATION. This has been fixed.



CR:708199
CR Number:   708199
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 3732 14 May 2012 Fixed
11.0.1 2813 14 May 2012 Fixed
Description
The server would have returned a syntax error when trying to specify "client" as a secure feature to be enabled or disabled (-sf command line option). This has been fixed.



CR:708252
CR Number:   708252
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 1719 11 Oct 2013 Fixed
12.0.1 4004 11 Oct 2013 Fixed
Description
The LOAD TABLE statement may insert invalid data values into columns of type NUMERIC. For type NUMERIC the server may insert values that exceeded the precision and scale

of the column type definition. This has been fixed. Now values for NUMERIC columns will be cast to the column data type if needed.



CR:708422
CR Number:   708422
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 3733 16 May 2012 Fixed
Description
If a user owned one or more tables, views, procedures or sequence generators, and permissions on these objects were assigned to another user, then deleting the first user could have caused Sybase Central to crash. This has been fixed.



CR:708426
CR Number:   708426
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 3683 18 May 2012 Fixed
Description
In rare timing dependent cases, a mirror server or copy node could have crashed while it, or the mirrored database, was shutting down. In order for the crash to have occurred, a copy node child must have begun to request log pages from the stopping server. This has now been fixed.



CR:708518
CR Number:   708518
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 3683 18 May 2012 Fixed
11.0.1 2815 18 May 2012 Fixed
Description
Mirroring copy nodes could have hung on shutdown with one core at 100% utilization.



CR:708547
CR Number:   708547
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 3733 17 May 2012 Fixed
1.0.1 4132 17 May 2012 Fixed
Description
The following behaviors In the "Change Server Version" wizard have been fixed:



1. The wizard would have installed the cloud software on all hosts which did not already have it, even if the hosts were not running the servers selected. Now, software is installed only on the servers selected.



2. The wizard would have reported that it was installing software even if it was only checking whether software needed to be installed. Now, the wizard reportss it is installing only if it really is installing software.



3. When cloud software was downloaded for both Windows and Linux, the wizard did not prevent attempting to use the software on a server which was running the wrong operating system. Now it does.



CR:708565
CR Number:   708565
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 3733 17 May 2012 Fixed
1.0.1 4133 17 May 2012 Fixed
Description
When logged in as a user who did not have the privileges needed to extract a database, attempting to extract a database from the cloud's "Databases" panel would have caused the Cloud Console to report an internal error. This has been fixed.



CR:708575
CR Number:   708575
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 3747 17 May 2012 Fixed
Description
UltraLitej for BlackBerry and J2SE now support custom HTTP headers. New methods have been added to StreamHTTPParms:



/** Adds a message header to each HTTP request. If addCustomHTTPHeader is called

* more than once with the same name parameter, the values are concatenated together

* into a comma-seperated list.

* <p>

* The following standard headers are set by ULj and cannot be changed using

* addCustomHTTPHeader: Connection, Content-Length, User-Agent, Content-Type, and

* Content-Length. Other headers may also be modified by the Java VM.

* <p>

* Not available on Android. On Android, specify a custom_header parameter using

* setExtraParameters

*

* @param name The name of the header

* @param value The value of the header

*/

public void addCustomHTTPHeader( String name, String value );



/** Returns a Hashtable containing the HTTP headers specified using addCustomHTTPHeader

*

* @return Returns a Hashtable containing the HTTP

* headers specified using addCustomHTTPHeader

*/

public java.util.Hashtable getCustomHTTPHeaders();



Custom cookies can be specified by calling addCustomHTTPHeader with "Cookie" as the header name.



CR:708576
CR Number:   708576
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 3747 17 May 2012 Fixed
Description
UltraLitej for BlackBerry and J2SE now support basic HTTP authentication. New methods have been added to StreamHTTPParms:



/**

* Sets the userid and password used for Basic HTTP authentication as

* described in RFC 2617.

* <p>

* With Basic authentication, passwords are included in HTTP headers in

* clear text; however, you can use HTTPS to encrypt the headers and

* protect this password.

*

* @param userid The userid to use

* @param password The password to use

*/

public void setHTTPUserIDAndPassword( String userid, String password );



/**

* Returns the userid previously set by setHTTPUserIDAndPassword.

*

* @returns The userid previously set by setHTTPUserIDAndPassword

*/

public String getHTTPUserID();



/**

* Returns the password previously set by setHTTPUserIDAndPassword.

*

* @returns The password previously set by setHTTPUserIDAndPassword

*/

public String getHTTPPassword();



CR:708578
CR Number:   708578
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 3747 17 May 2012 Fixed
Description
UltrLitej for BlackBerry and J2SE now support zlib stream compression. Some methods that were previously Android-only are now available for other platforms:



/** Enables or disables ZLIB compression.

* <p>

* By default, ZLIB compression is disabled

* <p>

* Only available for Android and BlackBerry

* <p>

* Corresponds to MobiLink client network protocol option "compression=zlib".

*

* @param enable Set to true to enable ZLIB compression, or false to disable

* ZLIB compression.

*/

public void setZlibCompression( boolean enable );



/** Sets the download window size for ZLIB compression.

* <p>

* Only available for Android and BlackBerry

* <p>

* Corresponds to MobiLink client network protocol option "zlib_download_window_size".

*

* @param size The compression window size specification, inclusively

* ranging from 9 to 15. This parameter is the base two

* logarithm of the window size. (the size of the history

* buffer)

*/

public void setZlibDownloadWindowSize( int size );



/** Sets the upload window size for ZLIB compression.

* <p>

* Only available for Android and BlackBerry

* <p>

* Corresponds to MobiLink client network protocol option "zlib_upload_window_size".

*

* @param size The compression window size specification, inclusively

* ranging from 9 to 15 for Android and 10 to 15 for BlackBerry.

* This parameter is the base two

* logarithm of the window size. (the size of the history

* buffer)

*/

public void setZlibUploadWindowSize( int size );



CR:708638
CR Number:   708638
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 3747 17 May 2012 Fixed
Description
UltraLitej for BlackBerry now supports end-to-end stream encryption. Some methods that were previously Android-only are now available for other platforms:



/** Sets the name of the file containing the end-to-end public key.

* <p>

* By default, this value is null, indicating that end-to-end encryption is

* not used.

* <p>

* Corresponds to MobiLink client network protocol option "e2ee_public_key".

*

* @param public_key The name of RSA public key file used in the encryption.

*/

public void setE2eePublicKey( String public_key );



/** Get the name of the file containing the end-to-end public key.

*

* @return the name of the file containing the end-to-end public key.

*/

public String getE2eePublicKey();



And there are also BlackBerry-specific methods to change the encryption type. ECC end-to-end encryption is available only for BlackBerry.



/**

* Pass this to setE2eeType to use RSA-based end-to-end encryption

*/

public final short E2EE_RSA = 0;

/**

* Pass this to setE2eeType to use ECC-based end-to-end encryption

*/

public final short E2EE_ECC = 1;



/**

* Set the type of end-to-end encryption to use. Pass one of StreamHTTPParms.E2EE_RSA or

* StreamHTTPParms.E2EE_ECC. The default is StreamHTTPParms.E2EE_RSA.

* <p>

* Only available on BlackBerry. ECC encryption is not supported on other platforms.

*

* @see StreamHTTPParms.E2EE_RSA

* @see StreamHTTPParms.E2EE_ECC

* @param type One of E2EE_RSA or E2EE_ECC

*/

public void setE2eeType( short type );



/**

* Returns the end-to-end encryption type being used.

* <p>

* Only available on BlackBerry. ECC encryption is not supported on other platforms.

* @return the end-to-end encryption type being used

*/

public short getE2eeType();





The public key used must be DER encoded.



The public key needed for end-to-end encryption can either be stored on an SD card or the device object store. When using an SD card, the parameter to setPublicKey should have the form "sdcard://<path>" where "<path>" is the absolute path to the file on the card. e.g. "file:///SDCard/ulj/public_key.der". When using the object store, use the file transfer utility built into ULj to download the file from the MobiLink server. To use file transfer to transfer a key it must have an extension of ".der".



CR:708644
CR Number:   708644
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.0 3734 17 May 2012 Fixed
1.0.1 4134 17 May 2012 Fixed
Description
The Schedule tab in the Properties dialog for a scheduled task in a German cloud had an unneeded horizontal scroll-bar. This has been fixed.



CR:708660
CR Number:   708660
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 3741 04 Jun 2012 Fixed
11.0.1 2821 04 Jun 2012 Fixed
Description
If a URL suffix had a leading '/', the URL formed would have been [http|https]://host-name:port-number//url-suffix. This could result in an synchronization error. This differs from UltraLite which ensures that the '/' is not added when there is an leading '.' in the URL suffix. This has been fixed, the leading character of the url_suffix is checked and a '/' is appended only if needed



CR:708672
CR Number:   708672
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 3734 18 May 2012 Fixed
1.0.1 4135 18 May 2012 Fixed
Description
Selecting annotated cloud software in the Create Server wizard would not have resulted in the server using annotated software. This has been fixed.



CR:708777
CR Number:   708777
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 May 2012 Fixed
31 May 2012 Fixed
Description
The UltraLiteJ method DatabaseInfo.getNumberRowsToUpload() could have returned a value that exceeded the actual number of rows that would have been actually uploaded during the next sync. For example, a sequence of operations such as an INSERT, UPDATE, and DELETE of a row should return 0, but would have returned a value that was larger. This has now been fixed.



CR:708790
CR Number:   708790
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 3734 18 May 2012 Fixed
1.0.1 4135 18 May 2012 Fixed
Description
Attempting to set the server version to use a non-annotated cloud software version using the server's property sheet did not work if the annotated software and the new software had the same version number. This has been fixed.



In a related problem, if a server was using an annotated build, and the host also had an unannotated version of the software installed (with the same version number), the initial "Version" value in the property sheet was incorrect. This has also been fixed.



CR:708812
CR Number:   708812
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 4135 24 Aug 2012 Fixed
1.0.0 3734 24 Aug 2012 Fixed
Description
When setting up mirroring for a tenant database, the "Add Database Mirror" wizard would have incorrectly recommended the server that had been selected for the mirror when browsing for the arbiter. Similarly, the list of recommended servers for the mirror could have included the server that had been selected for the arbiter. This has been fixed.



CR:708826
CR Number:   708826
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 3683 23 May 2012 Fixed
Description
In rare, timing dependant cases a copy node in a mirroring read-only-scale-out setup may have crashed. This has been fixed.



CR:709024
CR Number:   709024
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.0 1527 30 Apr 2013 Fixed
Description
When the Schedule Task wizard was canceled after clicking its Finish button, it was possible for the Console to report an internal error if the task had already been scheduled by the time the Cancel button was clicked. This has been fixed.



CR:709189
CR Number:   709189
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 3736 23 May 2012 Fixed
1.0.1 4140 28 May 2012 Fixed
Description
The approximate CPU time for a tenant database could have initially shown 'NaN seconds'. This has been fixed.



CR:709203
CR Number:   709203
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2817 23 May 2012 Fixed
12.0.1 3736 23 May 2012 Fixed
Description
If a jConnect or Open Client connection prepared a statement and called a stored procedure with a set of host variables, then the server could have crashed, or returned an odd "variable already exists" error, if the stored procedure had a parameter or variable named @p0. This problem has now been fixed.



CR:709208
CR Number:   709208
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)
11.0.1 2817 23 May 2012 Fixed
12.0.1 3736 23 May 2012 Fixed
Description
If an INI file was used with the Windows launchers for the Interactive SQL utility, Sybase Central, MobiLink Monitor, the Console utility, or SQL Anywhere Monitor, and the VM arguments exceeded 260 chars, the launcher would have fail. This has been fixed.



CR:709219
CR Number:   709219
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 3741 05 Jun 2012 Fixed
Description
When starting the Outbound Enabler, if the machine where the Relay Server was installed was running, but the Relay Server was not available, the Outbound Enabler would have started, failed to gather a Relay Server peer list, and then done nothing until it was manually shut down. This has been corrected so that the Outbound Enabler will now loop and continue to try and gather the Relay Server peer list until it is successful, or it is told to shut down.



CR:709351
CR Number:   709351
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.0 3737 25 May 2012 Fixed
Description
Previously, if you tried to restore multiple databases where at least one database name contained a '.', the restore backup wizard failed. This has been fixed.



CR:709375
CR Number:   709375
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Infrastructure
Status:   Closed
OS:   Generic
Original Version:   1.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.0 3737 25 May 2012 Fixed
1.0.1 4141 25 May 2012 Fixed
Description
In rare circumstances, mirror server definitions for a database copy could have been deleted. This has been fixed.



CR:709497
CR Number:   709497
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.0 3737 25 May 2012 Fixed
1.0.1 4142 25 May 2012 Fixed
Description
The following dialogs contained scrollbars due to long text for the German and/or French locales:

Server Properties

Create Rule

Edit Event Subscription



Fixed by minor sizing adjustments to these dialogs.



CR:709506
CR Number:   709506
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 3738 28 May 2012 Fixed
Description
The IIS Quick Setup script has had the following enhancements:



1) When the Relay Server is loaded with a high volume of requests and payload, transfer rate per client may thin out to a point that it cannot satisfy a preset requirement of IIS. The result is a dropping of connections and a Timer_MinBytesPerSecond event in the HTTPERR log. A change has been made in section 5b of the setup script to disable this minimum transfer rate requirement.



2) The Relay Server uses a default application timeout of 8 minutes. A change has been made in section 5b of the setup script to configure the connection timeout value of the web server to be 1 minute higher than the default application timeout. The client application can lower the timeout on a per request basis. The purpose of this change is to remove timeout issue due to mismatch timeout settings along the chain.



CR:709509
CR Number:   709509
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.0 3736 25 May 2012 Fixed
1.0.1 4140 25 May 2012 Fixed
Description
The Cloud Initialization utility (dbcloudinit) may be used to re-initialize a cloud on a computer where a cloud was previously running. To re-initialize a cloud, all hosts must be deleted, except for the last cloud partner, and the cloud stopped. When re-initializing a cloud, dbcloudinit will attempt to re-use settings from the previous cloud. In this case on Linux, if running the cloud from the root user account had previously been chosen, and when re-initializing a different account was used, the default port presented for the HTTPS port setting may have been outside the normal default range, for example 40843. This has been fixed.



CR:709513
CR Number:   709513
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 3737 28 May 2012 Fixed
1.0.1 4142 28 May 2012 Fixed
Description
The Rules panel would not have aligned the checkboxes vertically to the top of the grid row. These have been fixed.



CR:709633
CR Number:   709633
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3739 28 May 2012 Fixed
Description
W@hen clicking the column heading of the Current, Average or Maximum columns on the Performance Monitor tab, the corresponding values would have been sorted as strings, not as numeric values. Now the values are sorted numerically. In addition, the values are now right-aligned.



CR:709639
CR Number:   709639
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3738 29 May 2012 Fixed
11.0.1 2818 29 May 2012 Fixed
Description
On Solaris 11 systems, the default quitting time suggested by the Console utility is one hour later than the current time if daylight savings time is in effect. The solution to this problem is to update the Java Runtime Environment to version 1.6.0_31 or later. Instructions for doing this are contained in a white paper called "Updating the SQL Anywhere Java Runtime Environment", available from the Sybase web site:



http://www.sybase.com/detail?id=1058536



There are no code changes for this issue. Note, that this problem does not occur with Solaris 10.



CR:709640
CR Number:   709640
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 3739 28 May 2012 Fixed
Description
The Relay Server Outbound Enabler uses GET requests to monitor backend server status when the -cs command line option is used. The GET request was using an incorrect host header that always pointed to localhost:80. This has been fixed to respect the host and port implied by the -cs option.



CR:709644
CR Number:   709644
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
4145 29 May 2012 Fixed
Description
The Unload Database wizard did not prohibit reloading a subset of a database's tables into a new database when one or more of the selected tables contained a column with a domain data type, even though attempting to do so would always fail. Now, the wizard prohibits this and provides a list of alternatives.



CR:709648
CR Number:   709648
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)
4146 29 May 2012 Fixed
Description
When selecting a procedure or function and then selecting File->Execute in the Interactive SQL utility, the parameter editor table would have included "(Default)" entries for all parameters. Now "(Default)" is included only if the parameter has a default value.



CR:709761
CR Number:   709761
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3740 29 May 2012 Fixed
Description
When attempting to open a log file using the MobiLink Server Log File Viewer, if the file could not be opened for any reason, an error message saying that the file cannot be opened was displayed and then Sybase Central would have reported an internal error. The problem which caused the internal error has been fixed.



CR:709898
CR Number:   709898
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 3741 31 May 2012 Fixed
Description
UltraLiteJ for Android now supports changing the database encryption key as documented for UltraLite.



The following API was added:

Connection.changeEncryptionKey( String newKey )



For consistency the following APIs were added, which are equivalent to setDatabaseKey and getDatabaseKey respectively:

ConfigPersistent.setEncryptionKey( String key )

String ConfigPersistent.getEncryptionKey()



CR:709909
CR Number:   709909
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 3680 31 May 2012 Fixed
11.0.1 2820 31 May 2012 Fixed
Description
In rare, timing depending cases, the server could have crashed. This was more likely to have occurred when multiple database events could start and stop concurrently on multi-core computers. This has been fixed.



CR:709935
CR Number:   709935
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)
4148 31 May 2012 Fixed
Description
When the MobiLink client cache was large, there could have been a long pause after the last synchronization before MobiLink client shut down. This has been fixed.



Following are examples of situations that cause the cache to grow large:

- a large upload

- an upload with with many blob values

- using the -cl option to force the cache to be large

- running on a machine with a large amount of memory



CR:710072
CR Number:   710072
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3742 05 Jun 2012 Fixed
11.0.1 2823 05 Jun 2012 Fixed
Description
Under certain rare circumstances, calling the system procedure sa_locks() could have caused the server to fail a fatal assertion. This has now been fixed.



CR:710078
CR Number:   710078
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 3741 04 Jun 2012 Fixed
Description
When a cookie used by the Relay Server is not encoded properly, it should result in a RSE1003 error, but sometime the error RSE2003 was raised instead. This has been fixed.



CR:710111
CR Number:   710111
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 3741 04 Jun 2012 Fixed
Description
The Relay Server Outbound Enabler report would have reported session errors without parameters to Relay Server, but subsequent errors may have caused a crash. This has been fixed.



CR:710112
CR Number:   710112
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 3741 07 May 2013 Fixed
Description
The Relay Server may have crashed when it received a session error with parameters from the Outbound Enabler. This has been fixed.



CR:710285
CR Number:   710285
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 3743 07 Jun 2012 Fixed
11.0.1 2824 07 Jun 2012 Fixed
Description
Under rare circumstances, a server may have crashed while opening the result set cursor of a batch or stored procedure when the cursor's query was a cached simple SELECT. This has been fixed. A workaround is to turn plan caching off (option Max_plans_cached = 0).



CR:710432
CR Number:   710432
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3742 05 Jun 2012 Fixed
11.0.1 2823 05 Jun 2012 Fixed
Description
The MobiLink server could have crashed if a failed download using HTTP was restarted. This has been fixed.



CR:710978
CR Number:   710978
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3747 18 Jun 2012 Fixed
Description
If there were fewer SQLFreeHandle( SQL_HANDLE_ENV,... ) than SQLAllocHandle( SQL_HANDLE_ENV,... ) calls, and at least one TCP/IP connection had been made, unloading the ODBC driver dll, usually when the application exits, could have taken much longer than it should have. This could also have occurred if there were fewer SQLDisconnect calls than successful SQLConnect calls. This has now been fixed.
Workaround Description
 A.) Make sure all connections get closed before application ends.

B.) Disable Connection Pooling (connection property "CPOOL=NO")



CR:711000
CR Number:   711000
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 3744 11 Jun 2012 Fixed
Description
If an invalid value was given for a network protocol option on the Interactive SQL command line, the program could have reported an internal error. This would have happened only for those options which take a set of specific values. For example, running the following command would have crashed as "bogus" is not an allowable value for the "DoBroadcast" option.



dbisql -c "links=tcpip(DoBroadcast=bogus)"



This problem has been fixed.



CR:711034
CR Number:   711034
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 3744 11 Jun 2012 Fixed
Description
The START DATABASE statement includes the following optional clause:



CHECKSUM { ON | OFF }



Attempting to execute a START DATABASE statement in the Interactive SQL utility with this clause would have resulted in an inappropriate error message which complained of an unexpected keyword. This has been fixed.





Engineering Description:



The CHECKSUM clause was added in 12.0.0. I'm not sure how this got missed. I noticed the omission when I started to look at adding support for the new MIRROR ON clause of START DATABASE.





Behaviour Changes:



n/a



Admin Tools, Installers and Other Affected Software:



n/a



Documentation Changes:



n/a



Testing Requirements:



A test was added to the ISQL grammar test suite.



CR:711129
CR Number:   711129
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 3745 12 Jun 2012 Fixed
Description
In rare timing dependent cases, the server could have crashed if one or more connections were using the blocking_others_timeout temporary option. This has been fixed.



CR:711139
CR Number:   711139
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   12.0.1
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
Under exceptionally rare conditions, the server may have crashed while accepting a new shared memory connection, if the client application exited during connect request processing. This has been fixed.



CR:711141
CR Number:   711141
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3745 12 Jun 2012 Fixed
Description
The ODBC driver could have crashed when executing a block insert statement using data-at-execution time parameters. The problem would only have occurred when mixing data-at-execution time parameters with regular parameters. This has been fixed.



CR:711146
CR Number:   711146
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 3748 24 Aug 2012 Fixed
Description
The Interactive SQL utility has an option to control which result sets from a query to display; just the first one, or all of them. If "Show all result sets" was selected, the widths of columns in the table on the "Results" panels were not automatically sized to show the data. If "Show only the first result set" was selected (which is the default), the columns were automatically sized correctly. This has been corrected.



CR:711219
CR Number:   711219
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 3746 12 Jun 2012 Fixed
Description
Some occurances of Relay Server error messages had the backend farm and server names in the wrong order. Errors affected were: RSF13000, RSF13001, RSF13007, RSF14000, RSF14001, RSF14002, RSF14003. This has now been corrected.



CR:711258
CR Number:   711258
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 3746 12 Jun 2012 Fixed
Description
Some shared memory sizes and other memory usage were logged using a format that cannot display value greater than 4 Gbytes. This has been corrected.



CR:711260
CR Number:   711260
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 3869 12 Mar 2013 Fixed
Description
In a mirrored database configuration on Windows, when the SQL Anywhere service encountered a fatal error, it may have failed to stop and the only way to stop it was to kill the dbsrv1x.exe process. This has been fixed.



CR:711375
CR Number:   711375
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3746 18 Jun 2012 Failed
Description
If the Remote Server name was longer than 64 characters, the system procedure sp_servercaps() would have returned a "right truncation of string data" error.



Example:

CREATE SERVER ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ

CLASS 'SAODBC'

USING 'SQL Anywhere 12 CustDB';



CALL sp_remote_tables('ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ');

CALL sp_remote_columns ('ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ', 'ULCustomer');

CALL sp_servercaps ('ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ');



The first two calls succeed. The sp_servercaps() call would have failed as the argument was limited to 64 characters, which is too short.



This problem has been fixed. The sp_servercaps() now accepts up to 128 characters.



CR:711377
CR Number:   711377
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 3746 18 Jun 2012 Fixed
Description
The text completer for the UltraLite function ML_GET_SERVER_NOTIFICATION would have completed the text as ML_GET_SERVIER_NOTIFICATION (note the extra "I" in "SERVER"). This has been fixed.



CR:711380
CR Number:   711380
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 3746 18 Jun 2012 Fixed
Description
In the SQL Anywhere Monitor, the sparkline for a metric was usually drawn empty. This has now been fixed.



CR:711393
CR Number:   711393
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3747 18 Jun 2012 Fixed
Description
When a non-sticky load balancer was used in front of a Relay Server farm, concurrently requesting larger responses could have resulted in an RSE4003 error. This has been fixed. The workaround is to turn HTTP stickiness on for the load balancer, or to disable Relay Servers until only one remains enabled.



CR:711401
CR Number:   711401
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 3816 12 Nov 2012 Fixed
11.0.1 2899 15 Nov 2012 Fixed
Description
Under rare circumstances, snapshot transactions could have caused the server to fail assertions 200505, 200610, 201501, or 201503. This was more likely to have occurred when other connections had rollbacks of large transactions underway. This has been fixed.



CR:711499
CR Number:   711499
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3747 18 Jun 2012 Fixed
11.0.1 2828 18 Jun 2012 Fixed
Description
If Sybase Central encountered an internal error, and the user elected to send a report to Sybase, they would get a message saying that the report could not be sent, even if it was. This problem also occurred with the Interactive SQL utility, the Console utility, or the MobiLink Monitor, and has been fixed.



CR:711656
CR Number:   711656
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 3748 29 Jun 2012 Fixed
Description
When fetching an unsigned int value from an sajdbc, iqjdbc or asejdbc remote server, the returned value would always have been NULL. This problem has now been fixed.



Note that this problem does not affect ODBC based remote servers.



CR:711685
CR Number:   711685
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 3748 18 Jun 2012 Fixed
Description
The Relay Server was buffering the entire HTTP chunk in server response for validation before relaying to the client at once. Some backend servers produce large chunks, as big as many megabytes. The buffering was consuming memory, and so reducing scalability. The large write also affected timeliness of the flow control evaluation done interleaving on the same line of execution. This has now been fixed by replacing the handling with streaming packets of size no bigger than 64k regardless of chunk boundary. The validation is still performed but now done with state tracking on the go.



CR:711705
CR Number:   711705
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 3750 18 Jun 2012 Fixed
Description
After creating a directory access server that used the new for 12.0.1 "{varname}" syntax in the USING clause, Sybase Central could have crashed when attempting to open the Directory Access Servers folder. This has been fixed.



CR:711791
CR Number:   711791
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 3758 05 Jul 2012 Fixed
11.0.1 2836 05 Jul 2012 Fixed
Description
Recursive queries can not contain aggregate functions. When written using a window (OVER clause), aggregates were improperly allowed. In some cases this could have lead to the server crashing under certain system conditions. This has been fixed, queries with windowed aggregate functions now correctly give an error.



CR:711803
CR Number:   711803
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3749 18 Jun 2012 Fixed
12.0.0 2797 18 Jun 2012 Fixed
11.0.1 2829 18 Jun 2012 Fixed
Description
If the encrypt() or decrypt() functions were called with a non-null string but a null encryption key, the functions returned null. This has been fixed. An encryption key is required, so these functions will now raise an error if the encryption key is null.



CR:711977
CR Number:   711977
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 3751 20 Jun 2012 Fixed
Description
The help screen for several SQL Anywhere utilities (viewcert, createcert, dbcloudadd, dbcloudextract, and dbcloudcmd) tried to format the output for terminal display by splitting at 80 characters. When multi-byte characters were used, the splitting could have happened in the middle of a character, causing that character to display incorrectly. This also affected general output from the dbcloudcmd. This has now been corrected.



CR:712087
CR Number:   712087
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
While using blocking timeout options in the presence of other connections accessing referenced tables, ALTER TABLE ... DROP FOREIGN KEY statements could have caused the server to fail assertion 102813. This has been fixed. Now the alter table statement fails, properly displaying a locking error.



CR:712095
CR Number:   712095
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)
12.0.1 3817 13 Nov 2012 Fixed
11.0.1 2899 13 Nov 2012 Fixed
Description
The Log Translation utility (dbtran) could have crashed if the transaction log ended in an incomplete checkpoint. This problem has been fixed



CR:712099
CR Number:   712099
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 4172 21 Jun 2012 Fixed
1.0.0 3751 21 Jun 2012 Fixed
Description
Errors included in connection string parameters to the cloud command

line utilities were not reported to the user. This has been fixed.



CR:712102
CR Number:   712102
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3757 03 Jul 2012 Fixed
Description
If an application called CallableStatement/PreparedStatement/Statement.executeQuery() and then subsequently called CallableStatement/PreparedStatement/Statement.getResultSet() to retrieve the same result set that was generated by calling executeQuery(), then the JDBC driver would have leaked the memory. This problem has now been fixed.



Note, there are two workarounds for this problem, both of which are considered better JDBC programming practices. The first is to use the ResultSet returned by calling executeQuery() directly and thereby avoid the second unnecessary call to getResultSet(). The other approach is to call execute() instead of executeQuery(), followed by a call to getResultSet().



CR:712115
CR Number:   712115
Product Name:   SAP Sybase SQL Anywhere on-demand edition
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   1.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
1.0.1 4172 21 Jun 2012 Fixed
1.0.0 3751 21 Jun 2012 Fixed
Description
When providing named parameters to tasks through the Cloud Command utility (dbcloudcmd), the parameter name was only recognized if the case matched exactly. This has now been corrected.





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