远程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:740130
CR Number:   740130
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 1553 23 May 2013 Fixed
12.0.1 3906 23 May 2013 Fixed
Description
Under very rare circumstances, DML operations on a table with an immediate text index that used an external prefilter or termbreaker library, could have caused assertion failures or other issues with the database server. This problem has now been fixed.



CR:740222
CR Number:   740222
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 4604 24 May 2013 Fixed
Description
When describing a cloud server running on a Linux host, the TCP addresses listed may have include ::1. This has been fixed.



CR:740226
CR Number:   740226
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1553 23 May 2013 Fixed
12.0.1 3906 23 May 2013 Fixed
Description
Using '*' when specifying the publication list would have caused the UltraLite runtime to crash during a synchronization. This has been fixed.



CR:740328
CR Number:   740328
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 1555 24 May 2013 Fixed
12.0.1 3908 24 May 2013 Fixed
Description
The Relay Server would have incorrectly stopped relaying and reported the error RSE4008 with 揗alformed HTTP chunk when it encountered chunked server responses with valid extensions or trailers (see RFC2616 section 3.6.1). This has been fixed. Logging of the extensions and trailers were added for log level 4 and higher.



CR:740334
CR Number:   740334
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1554 24 May 2013 Fixed
12.0.1 3907 24 May 2013 Fixed
11.0.1 2989 24 May 2013 Fixed
Description
The ICommandPersist interface methodes, LoadCommand, DeleteCommand, and SaveCommand, did not qualify system tables references with an owner name. This has been corrected.



CR:740400
CR Number:   740400
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 1555 27 May 2013 Fixed
12.0.1 3908 27 May 2013 Fixed
Description
In rare cases, a copy node or mirror server could have used more memory than expected. If this occurred, the extra memory would typically have been less than 1MB. This has been fixed.



CR:740412
CR Number:   740412
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1555 24 May 2013 Fixed
12.0.1 3908 24 May 2013 Fixed
Description
The 32-bit version of the Version 9 or earlier physical store library (dboftsp.dll) was not installed on a 64-bit OS when the 32-bit Client feature was selected. Furthermore, dboftsp.dll was not installed when the MobiLink or SQL Remote features were selected. This has been fixed.



CR:740414
CR Number:   740414
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1555 27 May 2013 Fixed
12.0.1 3908 27 May 2013 Fixed
Description
The SQL Anywhere Extension Agent library (dbsnmp*.dll) was not being installed on a 64-bit systems. The 64-bit install needs to put down the 32-bit dbsnmp*.dll to support Microsoft SNMP, which is a 32-bit only service. This has been fixed.



CR:740440
CR Number:   740440
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 1558 27 May 2013 Fixed
12.0.1 3909 27 May 2013 Fixed
Description
The Relay Server would have responsed with "HTTP 200 OK" to requests that didn抰 carry User-Agent headers, without actually performing the relay. The Relay Server uses the User-Agent header (or alternatively the IAS-RS-User-Agent header) to group metrics for aggregated statistics. A fix has been made so that requests that don抰 carry User-Agent or IAS-RS-User-Agent headers are now processed, and their metrics are collected under the group with User-Agent 揰unknown_. This problem was reported when using the Relay Server with Windows 8 Store app which accesses NetWeaver Gateway OData services via the Relay Server and SUP 2.2.



CR:740441
CR Number:   740441
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 1558 27 May 2013 Fixed
Description
If certain SMTP errors occured during xp_sendmail, the error code and text returned by xp_get_mail_error_code() and xp_get_mail_error_text() may have been 250 and 2.0.0 Reset state respectively, regardless of what actual error occurred. This has been fixed to return the correct SMTP error details.



CR:740486
CR Number:   740486
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 1559 28 May 2013 Fixed
12.0.1 3910 28 May 2013 Fixed
Description
Clients are not expected to use expired affinity, however not all client development can support proprietary expiry defined by the Relay Server. For that reason, the Outbound Enabler was relaxed to let in new requests with expired affinity. This relaxation was found to be incomplete. Under certain access sequence, a POST request may still suffer errors like the following:

RS16: RSE4015: Outbound enabler of backend server 'S0' in backend farm 'RSTEST02.F0' reports session error OEE_SESSION_ACCESS_FAILED(1051) with parameters 'RS_CLI_REQUEST_CONTINUE', 'disconnected at the middle of a request', '_unused_'

OE16: OEE1051: The Outbound Enabler was unable to access the session with ridx=0 sidx=0 snum=0000 sfp=01aa9daa on a RS_CLI_REQUEST_CONTINUE packet due to disconnected at the middle of a request

RS12: RSE4004: Outbound enabler of backend server 'S0' in backend farm 'MLVM-SARSX64.F0' reports session error OEE25100 with parameters '_unused_', '_unused_', '_unused_'

OE12: Session was disconnected at the middle of a packet sequence. Aborting sidx=0



The problematic sequence has been identified and a fix has been made so that the OE can handle the POST that falls into that sequence. If the traffic is RESTful, a user workaround is to turn off all affinity injection from the Relay Server using the active_cookie=no and active_header=no property in the backend_farm configuration section of the affected backend farm and clear HTTP cookies from the client after the Relay Server configuration has been updated.



CR:740488
CR Number:   740488
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1559 28 May 2013 Fixed
12.0.1 3910 28 May 2013 Fixed
11.0.1 2990 28 May 2013 Fixed
Description
Attempting to create a table column or domain with an empty string as the default value would have caused the object to be created with no default value. This has been fixed.



CR:740548
CR Number:   740548
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)
16.0.0 1727 08 Nov 2013 Fixed
12.0.1 4010 08 Nov 2013 Fixed
Description
Information returned by the system procedure sa_mirror_server_status() was not updated for the hour after a daylight savings time change that changed the local time to be an hour earlier. The sa_mirror_server_status row corresponding to the server that was running the sa_mirror_server_status query was note affected. This has been fixed.



CR:740559
CR Number:   740559
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 1559 29 May 2013 Fixed
12.0.1 3910 29 May 2013 Fixed
Description
The affinity information injected by the Relay Server carries information for addressing the socket opened from the Outbound Enabler to the backend server. This was required for end-to-end persistent connections between Client-RS and OE-Backend, while the shared RS-OE connection is always persistent. Such socket level affinity calls for affinity information isolation per socket on the client side. This proprietary isolation requirement was found to be too restrictive. Partners have been releasing their clients or utilizing third party client software in solutions using the Relay Server where the isolation requirement has not been met. Not all development environments or third party clients can support the implementation of the isolation. A change has now been made to introduce an optional relaxation from the Relay Server so that it will reduce the level of addressing information to backend server level instead of socket level. Persistent connection between Client-RS can still be maintained as the Relay Server will work with the Outbound Enabler to transform the OE-Backend accesses into non-persistent transient access. The net result is a liberation on developing integration between the client and the Relay Server.



A new backend_farm property called socket_level_affinity has been added for controlling the behavior in a per backend farm manner. The liberation described above is DISABLED by default (i.e. socket_level_affinity=yes is the default). Online configuration update of this property is supported.



External Requirements

Updating to this new Relay Server, with socket_level_affinity=no, doesn抰 require deploying a client to clear previous affinity cookie assigned by the Relay Server. Also, the Outbound Enabler doesn抰 need to be upgraded in order to enjoy the liberation. This is an internal behavior change which continues to require the backend servers to allow non-persistent HTTP traffic and/or broken up persistent HTTP traffic. This backend server requirement remains regardless of whether the liberation is used or not. If liberation is enabled, the backend server doesn抰 need to support or allow persistent HTTP connection.



CR:740636
CR Number:   740636
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1560 29 May 2013 Fixed
12.0.1 3911 29 May 2013 Fixed
11.0.1 2991 29 May 2013 Fixed
Description
The MobiLink user password and new password could have been shown in MobiLink server log files in plain text. This would have occured if the password and new password, as named-parameters, were referenced in any user authentication scripts, and the MobiLink server was running with the 杤c command line option. This as been corrected. Now the MobiLink server will replace the password and new password with asterisks "*", and then log them.



CR:740649
CR Number:   740649
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 1559 05 Jun 2013 Fixed
12.0.1 3915 05 Jun 2013 Fixed
Description
Under very rare conditions, the server may have entered an infinite loop while performing massive amounts of concurrent inserts. This has now been corrected.



CR:740651
CR Number:   740651
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 3912 30 May 2013 Fixed
11.0.1 2992 30 May 2013 Fixed
Description
If the Unload utility (dbunload) was run on a database that had a user with an expired password, or if a new user had been created that was forced to change their password on first login, the resulting reload script would have contained an ALTER USER statement that would have failed with a syntax error. This problem has been fixed. The correct "ALTER USER <user-id> FORCE PASSWORD CHANGE ON" syntax is now correctly generated in the reload script.



CR:740695
CR Number:   740695
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 1566 04 Jun 2013 Fixed
12.0.1 3914 04 Jun 2013 Fixed
Description
The ADO.NET provider could have thrown an exception when closing a pooled connection which used an integrated login. This has now been fixed.



CR:740701
CR Number:   740701
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 1561 30 May 2013 Fixed
Description
Calling the system stored procedure dbo.sp_objectpermission() would in some cases have returned the string 'NULL' in some of the result columns, instead of returning the NULL value. This problem has been fixed. Note that a database upgrade is required to get this fix.



CR:740708
CR Number:   740708
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 1613 18 Jul 2013 Fixed
12.0.1 3952 09 Aug 2013 Fixed
Description
In SYSUSER, SYSEXTERNLOGIN and SYSLDAPSERVER system views, columns containing password hashes were visible to users without SELECT ANY TABLE privilege. This has been fixed.



Note that in order to apply this fix, existing version 16.0 database will need to be upgraded once the server containing the fix is deployed. New databases created with the fixed version of the server do not need to be upgraded.



CR:740710
CR Number:   740710
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Jan 2014 Fixed
Description
The MobiLink server now supports the 杁t command line option for Oracle only:

-dt detect transactions only within the current database (for Microsoft SQL Server, Adaptive Server Enterprise and Oracle only)



When this option is used on the command line with Oracle, the MobiLink server will fetch the earliest starting time of the open transactions only that have modified any tables to the current database schema in the prepare_for_download phase, and then the MobiLink server will use this time that is named the next_last_download_timestamp to generate the download stream for the client in the next sync. With this option the MobiLink server may considerably reduce redundant download for any clients that use a timestamp-based download on a busy Oracle database server.

In order to use this new command line option, the user ID the MobiLink server uses to connect to the Oracle database must have a selection permission of the following global views on the Oracle database:

GV$TRANSACTION, GV$SESSION, GV$LOCKED_OBJECT



CR:740747
CR Number:   740747
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 1584 31 May 2013 Fixed
12.0.1 3913 31 May 2013 Fixed
Description
The Apache Relay Server did not respect the client's application timeout header (IAS-RS-App-Timeout-Minute). If the client's application timeout header value eas smaller than Apache's 'Timeout' directive, the Apache Relay Server would have taken longer to timeout the client's request, upto Apache's Timeout directive. This has been fixed.



CR:740784
CR Number:   740784
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)
16.0.0 1563 31 May 2013 Fixed
12.0.1 3913 31 May 2013 Fixed
Description
When OPENSTRING() is used in the FROM clause, the ROWID() function can be used to get the row number of each row read from the string. In execution plans where the same OPENSTRING() was executed more than one time, the ROWID() values for second and subsequent executions would not have given the correct line number: they would have continued to increase. In addition, error messages for rows loaded from the string value could have reported incorrect line numbers. This has been fixed.



CR:740787
CR Number:   740787
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 1562 31 May 2013 Fixed
12.0.1 3913 31 May 2013 Fixed
Description
The connection property ApproximateCPUTime was reporting twice the amount of CPU time consumed by a connection. This has been corrected.



CR:740792
CR Number:   740792
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 1563 03 Jun 2013 Fixed
Description
The system function xp_getenv() could have become "sql security definer" in databases initialized to run system procedures as definer. However, all new procedures in version 16 and higher are supposed to remain as 搒ql security invoker. This would have happened if a version 16 database was initialized with either the -pd flag for dbinit, or the "system procedure as definer on" clause was used in either the CREATE DATABASE or the ALTER DATABASE UPGRADE statements. This has now been fixed.



In order to repair the function in an existing database, run ALTER DATABASE UPGRADE PROCEDURE ON with an upgraded server.



CR:740795
CR Number:   740795
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 1563 03 Jun 2013 Fixed
Description
Java is not pre-installed with Mac OS X versions 10.7(Lion) and above. In order to use the administration tools on Mac OS X, Java SE Runtime Environment 7(JRE 1.7) must be manually installed. Without a JRE properly installed, the admin tools silently fail to start. When the admin tools were selected in the install, the user should have been notified that they will need to install JRE 1.7 if it was not already installed. This has been improved by providing the messages from 揑nstall SQL Anywhere application and/or setup from 揟erminal application. The messages will be displayed if JRE 1.7 is not installed on the system (Mac OS X) when installing the components that require Java.



CR:740799
CR Number:   740799
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 1636 03 Jun 2013 Fixed
12.0.1 3953 03 Jun 2013 Fixed
Description
Performance of the server when run on Linux systems was much slower than when run on Windows. The performance of the server has now been improved so the speed on Linux should now be comparable to speeds on Windows.



CR:740808
CR Number:   740808
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 1570 10 Jun 2013 Fixed
12.0.1 3910 10 Jun 2013 Fixed
Description
Multithreading .NET application could have failed with an access violation exception. Fixed by modifying thread synchronization code for some interface functions, and code for managed connection pooling.



CR:740842
CR Number:   740842
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)
16.0.0 1567 04 Jun 2013 Fixed
12.0.1 3915 04 Jun 2013 Fixed
11.0.1 2994 04 Jun 2013 Fixed
Description
When using the ODBC Data Source Administrator to configure a SQL Anywhere 11 ODBC data source, the Database File 揃rowse button would have returned a truncated string. Only the first 7, or 3 characters, of the file path are returned (depending on bitness). This problem has now been fixed.



CR:740879
CR Number:   740879
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1583 21 Jun 2013 Fixed
12.0.1 3924 21 Jun 2013 Fixed
Description
If a SQL Anywhere MobiLink client database had been rebuilt using the Unload utility (dbunload), and it previously had been upgraded using the Ugrade utility (dbupgrad) or using the ALTER DATABASE UPGRADE command, then subsequent synchronizations could have resulted in dbmlsync sending up the wrong schema definition to the MobiLink Server, or it could have resulted in a crash of the dbmlsync process. This can be worked around by dropping and re-creating all the SYNCHRONIZATION SUBSCRIPTIONS in the remote database after the rebuild or upgrade. This issue has now been resolved.



CR:740895
CR Number:   740895
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 1566 03 Jun 2013 Fixed
12.0.1 3914 03 Jun 2013 Fixed
Description
If a NULL byte was used in the string provided to the DELIMITED BY, ROW DELIMITED BY, COMMENTS INTRODUCED BY, QUOTE, or ESCAPE CHARACTER clauses of a LOAD TABLE statement or OPENSTRING expression, then the server would have used all characters prior to the first null byte as the argument to the option. For example, if the user specified DELIMITED BY '#\x00@' then the server would use '#' as the column delimiter. This problem has been fixed.



CR:740897
CR Number:   740897
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 1583 04 Jun 2013 Fixed
Description
If a web service was created with authentication off, attempting to execute the procedure while specifying a user that required LDAP authentication would have failed. This has been fixed.



CR:740992
CR Number:   740992
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 1567 05 Jun 2013 Fixed
Description
SQL keywords from the CREATE FUNCTION statement are now suggested properly. Previously, opening the text completer when the caret was after the function name, but before the BEGIN keyword, would cave caused the Interactive SQL utility to suggest only CREATE FUNCTION and CREATE FUNCTION...BEGIN...END. A similar issue with the CREATE PROCEDURE statement was also fixed.



CR:741078
CR Number:   741078
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 1568 05 Jun 2013 Fixed
12.0.1 3915 05 Jun 2013 Fixed
Description
A server could, in rare cases, have failed assertion 104301 ("Attempt to free a user descriptor with non-zero reference count") on database shutdown if there were active external environment calls at the time of shutdown request. This problem has now been fixed.



CR:741082
CR Number:   741082
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 4097 08 Apr 2014 Fixed
Description
On Windows, event log entries for version 12.0.1 MobiLink and SQL Anywhere database server services would have shown the service name only on the General tab of the Event Viewer/Windows Logs/Application window. There was no accompanying message.

For example, the following text could have been displayed:

SQLANYe_test12



As a workaround, the Details tab can be used to see the missing message for this event. This problem has now been fixed so that the Details tab will include the message, as in the following:

SQLANYe_test12: Starting service SQLANYe_test12



CR:741205
CR Number:   741205
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 1570 07 Jun 2013 Fixed
12.0.1 3910 07 Jun 2013 Fixed
Description
The Relay Server and the Outbound Enabler were not designed for clients that did not maintain affinity isolation. The Outbound Enabler has been incrementally patched to fulfill such a need. The new Relay Server liberation option (socket_level_affinity=no) is an efficient way to have the Relay Server transform the traffic so that the relay mechanism will no longer be exposed to unintended use. In other words, the net effect is to support the previously unintended use with the liberation option. Liberation is not turned on by default and some customers may be willing to upgrade their Outbound Enabler, but not the Relay Server in the DMZ. So testing of such unintended use without liberation has been increased, and yet another case where such unintended use may still fail without using liberation has been found. This change is to fix the Outbound Enabler to deal with such a case. A workaround is to use liberation by explicitly setting socket_level_affinity=no.



CR:741303
CR Number:   741303
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1577 14 Jun 2013 Fixed
12.0.1 3921 14 Jun 2013 Fixed
Description
A DATE datatype would have included time components if the value supplied contained a time component. As a result, queries could have returned incorrect results when providing a DATE only predicate value. UltraLite now stores DATE datatypes correctly when setting or changing the value.



CR:741408
CR Number:   741408
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 1581 13 Jun 2013 Fixed
12.0.1 3923 13 Jun 2013 Fixed
Description
Relay Server for Apache correctly sets the HTTP status code on the client's HTTP response, however, it didn't return that same HTTP status code back to the Apache webserver. This caused the wrong HTTP status code to be printed in Apache's access_log.

This has now been fixed.



CR:741432
CR Number:   741432
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 1575 12 Jun 2013 Fixed
Description
JSON Edm.DateTime values were being returned relative to the local time zone instead of UTC. This has been fixed.



CR:741546
CR Number:   741546
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 1576 14 Jun 2013 Fixed
Description
Authenticating with an LDAP server may have failed, even when the correct user name and password were given. This is dependent on the LDAP server being used and would not have been intermittent (i.e. if it failed, it failed all the time). This has been fixed.



CR:741547
CR Number:   741547
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 1576 14 Jun 2013 Fixed
Description
Authenticating with LDAP using an empty password could have caused the server to crash. This has been fixed.



CR:741572
CR Number:   741572
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3941 22 Jul 2013 Fixed
Description
UltraLite could have returned incorrect results for queries using LIKE 'C%', where C contained 'large'/multi-byte characters. This affected only UTF-8 encoded databases (created with utf8_encoding=yes, which is the default). This has now been corrected.



CR:741704
CR Number:   741704
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 1581 19 Jun 2013 Fixed
12.0.1 3923 19 Jun 2013 Fixed
Description
The changes for Engineering case 735654 were incomplete. Using a 11.0.1 database with a 12.0.1 or 16.0.0 .net provider and server, could still have resulted in the exception " Invalid option 'timestamp_with_time_zone_format' -- no PUBLIC setting exists". This has now been corrected.



CR:741707
CR Number:   741707
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 1588 02 Jul 2013 Fixed
12.0.1 3924 02 Jul 2013 Fixed
Description
An access violation exception in the ADO.NET provider could have caused the database server to crash. This has been fixed.



CR:741721
CR Number:   741721
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1580 18 Jun 2013 Fixed
12.0.1 3922 18 Jun 2013 Fixed
11.0.1 3000 18 Jun 2013 Fixed
Description
Calling the SAConnection.ConnectionString property could have caused the provider to crash with a NullReferenceException. This has now been fixed.



CR:741724
CR Number:   741724
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 1583 18 Jun 2013 Fixed
12.0.1 3924 20 Jun 2013 Fixed
Description
If a DSN contained a connection string with double quotes (eg. 搒erver=MyServer;start=抎beng16 -o \攆ile with spaces.txt\ ), the output from dbdsn -cm (intended to be a dbdsn command that would re-create the DSN) would have incorrectly escaped the double quotes. This has been fixed.



CR:741870
CR Number:   741870
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 1582 19 Jun 2013 Fixed
12.0.1 3923 19 Jun 2013 Fixed
Description
If the database server was started with the 杅ips option, but the FIPS library was not available, the server would have given an error and then hung. The server process would have to have been killed. This has been fixed.



CR:741954
CR Number:   741954
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1592 02 Jul 2013 Fixed
12.0.1 3931 02 Jul 2013 Fixed
Description
Performance of schema API calls could have been poor for large schemas. Querying any table would have been slow with Sybase Central and Interactive SQL when the schema was large. This has been fixed.



CR:741971
CR Number:   741971
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1583 27 Jun 2013 Fixed
Description
A TLS error (for example, a problem with a server抯 certificate) that occurred when executing a secure web service may have returned the error 揟he secure connection to the remote host failed: <NULL> or 揌TTP request failed. Status code 0挃. On MacOS systems, the message 揟he TLS handshake failed, error code 0 would have been displayed on the server console. This has been fixed.



CR:742010
CR Number:   742010
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)
16.0.0 1584 27 Jun 2013 Fixed
12.0.1 3925 27 Jun 2013 Fixed
11.0.1 3003 27 Jun 2013 Fixed
Description
A mirror server or copy node could have crashed if snapshot isolation was enabled and read-only connections were committed or rolled back. This has been fixed.



CR:742013
CR Number:   742013
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1584 27 Jun 2013 Fixed
12.0.1 3925 27 Jun 2013 Fixed
Description
Starting a database could have taken 10 seconds or more longer than it should have taken if the -ar, -ad or -xp database options were used with servers running on Windows. This could have occurred if files other than the database and current transaction log files for the server that was attempting to start the database were in the same directory as the database's log file, and these files were locked by the current server or another process. For example, if a single directory contained database files in use by a different server process, or a console log file in use by the server starting the database, a server starting the database with -ar, -ad or -xp would have started slowly. This has now been fixed.



As a workaround, the database files could be put in a directory containing only the database files for a single database.



CR:742016
CR Number:   742016
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)
16.0.0 1584 27 Jun 2013 Fixed
Description
If a certificate used one of a number of algorithms (including SHA256, SHA384, and SHA512) for signing, SQL Anywhere would not have been able to use it for TLS or HTTPS. An error code of 12357 or 12394 may have been displayed. This has been fixed.



CR:742023
CR Number:   742023
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1576 27 Jun 2013 Fixed
Description
Methods of the C++ DatabaseManager class could have failed or returned null, but not set any error in the supplied ULError object. For example, OpenConnection would return null but set the error code to 0 (NOERROR) if the database-manager was not initialized. Now an error is set.



CR:742037
CR Number:   742037
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 1584 27 Jun 2013 Fixed
Description
Requests to update or delete may return incorrect errors in an environment with many clients modifying entities.



CR:742161
CR Number:   742161
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1607 27 Jun 2013 Fixed
Description
The conditions for a restartable download to be available have been improved. This only applies to UltraLite clients at this time that have been upgraded to build 1584.



IMPORTANT: These newer UltraLite clients may in rare cases cause older 16.0 MobiLink servers (prior to build 1584) to crash due to a previously undetected bug.



CR:742293
CR Number:   742293
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1599 11 Jul 2013 Fixed
12.0.1 3935 11 Jul 2013 Fixed
11.0.1 3012 11 Jul 2013 Fixed
Description
A case sensitive database with the DBA user name spelled in a way other than 慏BA (for example, 慸BA or 慸ba) and password other than 憇ql could have failed to be unloaded. This has been fixed.



CR:742355
CR Number:   742355
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 1588 02 Jul 2013 Fixed
12.0.1 3924 02 Jul 2013 Fixed
Description
SQL Anywhere ADO.NET drivers without the fix for Engineering case 741707, could have sent invalid connection pooling requests to the server which could have resulted in a server crash. This has been fixed so that the server will not crash even if the client makes invalid connection pooling requests.



SQL Anywhere ADO.NET drivers without the 714707 fix may have requests fail with the error "Run time SQL error -- *** ERROR *** Assertion failed: 104909". The ADO.NET driver needs to be updated if this occurs.



CR:742365
CR Number:   742365
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)
16.0.0 1592 05 Jul 2013 Fixed
12.0.1 3931 05 Jul 2013 Fixed
Description
A number of incorrect behaviors could have occurred when using database mirroring, including:

- in rare, timing dependent cases, a mirror or copy node could have crashed, hung or failed assertion 102010

- when a mirror or copy node reconnected to the primary or parent, it was possible for it to not request, write or apply log pages.

- when a mirror was yielding to a preferred server, or the "ALTER DATABASE SET PARTNER FAILOVER" statement was executed on the primary, it was possible for the previous mirror to not take over as the primary (both partner servers could have had the mirror role)



These problems have been fixed.



CR:742377
CR Number:   742377
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 1588 04 Jul 2013 Fixed
12.0.1 3929 04 Jul 2013 Fixed
Description
The SQL Anywhere Monitor could have raised alerts for high memory usage incorrectly. This has been fixed.



CR:742543
CR Number:   742543
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1594 04 Jul 2013 Fixed
12.0.1 3932 04 Jul 2013 Fixed
Description
When iterating through the parameters of a SACommand using 揻oreach (SAParameter param in command.Parameters), the first iteration would have worked, but subsequent iterations would not have had the parameters. This has now been corrected.
Workaround Description
 Use instead:

for (int i = 0; i < command.Parameters.Count; i++)



CR:742549
CR Number:   742549
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)
16.0.0 1592 04 Jul 2013 Fixed
12.0.1 3931 04 Jul 2013 Fixed
Description
The Validation utility (dbvalid) would have returned EXIT_BAD_DATA(=2) if an invalid object name was included in the object-name-list. If these obests are not found, ideally the error EXIT_FAIL(=1) should be returned instead. This has been fixed.



CR:742551
CR Number:   742551
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 1592 02 Jul 2013 Fixed
12.0.1 3931 02 Jul 2013 Fixed
Description
The SQL Anywhere Monitor did not localize the desktop for the 慳dmin user properly. This has now been fixed.



CR:742630
CR Number:   742630
Product Name:   MobiLink
Product Component:   MobiLink Profiler
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1593 04 Jul 2013 Fixed
Description
After opening the Sample Range Properties window, some counts could have been incorrect in the Events tab for subsequent invocations of the Sample Properties or Sample Range Properties windows. This problem has been fixed.

A workaround is to re-open the profiling session after opening the Sample Range Properties window.



CR:742729
CR Number:   742729
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 1594 04 Jul 2013 Fixed
12.0.1 3932 04 Jul 2013 Fixed
Description
If launching the SQL Anywhere Monitor failed, the error message would have been garbled for FR and DE locales. This has been fixed.



CR:742733
CR Number:   742733
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1598 08 Jul 2013 Fixed
Description
When calling a procedure without a RESULT clause using ODBC and JDBC, the performance was not as fast as it could have been. This has been fixed so that the performance has been improved.



CR:742768
CR Number:   742768
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1725 24 Oct 2014 Fixed
Description
The Deployment wizard would have accepted an invalid product code. Now, the Next button is disabled until a valid product code is entered.



CR:742779
CR Number:   742779
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1595 08 Jul 2013 Fixed
Description
Connection status in the SQL Anywhere Connection widget was not localized. This has been fixed.



CR:742780
CR Number:   742780
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 1595 08 Jul 2013 Fixed
12.0.1 3933 08 Jul 2013 Fixed
Description
Sparkline in the Table widget would have always displayed the one hour graph when a different scale was chosen, another dashboard was selected, and then the original dashboard was reselected. This has been fixed.



CR:742857
CR Number:   742857
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1602 12 Jul 2013 Fixed
12.0.1 3937 12 Jul 2013 Fixed
11.0.1 3013 12 Jul 2013 Fixed
Description
When reading Long Varchar or Long Binary columns using SADataReader, the results could have been truncated to 65535 chars. This has now been fixed.



CR:742862
CR Number:   742862
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1598 08 Jul 2013 Fixed
12.0.1 3934 08 Jul 2013 Fixed
Description
On Windows systems, if the database server address cache file (sasrv.ini) was not writable by the current user, repeated connection attempts to a non-cached server may have been slow. This has been fixed.



CR:742872
CR Number:   742872
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1598 09 Jul 2013 Fixed
12.0.1 3934 09 Jul 2013 Fixed
Description
The server could have become unresponsive or extremely slow if it was involved in multiple high-availability configurations (for example, if it was running a number of read-only copy nodes), and there were networking problems causing loss of connectivity. This would have been more noticeable on single-processor machines. This has been fixed.



CR:742949
CR Number:   742949
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)
16.0.0 1600 10 Jul 2013 Fixed
Description
If a user was logged into a mirror or a copy node, or an object owned by that user was in use on a mirror or copy node, and the user was dropped on the primary server using the REVOKE CONNECT statement, the mirror or copy node would have stopped with a fatal assertion. This has been fixed. Connections logged in as the dropped user, as well as connections using objects owned by that user, will now be dropped before the user is dropped.



CR:742979
CR Number:   742979
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 1599 10 Jul 2013 Fixed
Description
If data from a text file was imported, the contents of the file could have been misinterpreted, resulting in garbage characters being imported. For this to happen, the file must have been encoded in Unicode, must have contained a literal string (enclosed in apostrophes) which contained a backslash ( "\" ) character, and the string must have contained characters which cannot be expressed in 7-bit ASCII. This has been fixed.



CR:743027
CR Number:   743027
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1606 16 Jul 2013 Fixed
12.0.1 3939 16 Jul 2013 Fixed
11.0.1 3014 16 Jul 2013 Fixed
Description
HTTP Basic authentication in persistent HTTP synchronizations could have reported the error: -1305: MobiLink communication error -- code: 216. This has been fixed.



Note, this fix also applies to UltraLite and UltraLiteJ for Android.



CR:743046
CR Number:   743046
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 1600 10 Jul 2013 Fixed
12.0.1 3935 10 Jul 2013 Fixed
Description
When the Apache httpd shutdown raced ahead of the Outbound Enabler shutdown, the Up channel may never have been gracefully shutdown, as Apache terminates the worker process non-gracefully. This could in turn could have caused the Relay Server State Manager (rshost) to leak System V semaphores on shutdown. The 搃pcs 杝 command can be used to review System V semaphore being used. This has been fixed by eliminating the latency on Up channel shutdown so that the race condition is much less likely to happen. This change is not a complete solution, but it reduces the possibility of this problem occurring.



CR:743048
CR Number:   743048
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 1605 15 Jul 2013 Fixed
12.0.1 3938 15 Jul 2013 Fixed
Description
Opening of pooled connections was taking longer than necessary. Open performance of pooled connections has now been improved by caching and reusing some internal values.



CR:743069
CR Number:   743069
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 1598 11 Jul 2013 Fixed
Description
When manually submitting an error report with a command like: dbsupport -sc ... , usage statistics would have been submitted, but the report itself would not. This has been fixed.



CR:743243
CR Number:   743243
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 1606 12 Jul 2013 Fixed
Description
Users could not use Sybase Central to view the contents of a view owned by SYS unless they had exercise rights on the SELECT ANY TABLE system privilege. This has now been corrected.



CR:743341
CR Number:   743341
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 1605 15 Jul 2013 Fixed
12.0.1 3938 15 Jul 2013 Fixed
Description
In rare cases, if an application made an external environment call that in turn performed a server-side request, then the server could have crashed or lost an update if the server-side request resulted in a deadlock error. This problem has now been fixed.



CR:743364
CR Number:   743364
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Linux
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3924 17 Jul 2013 Fixed
Description
The fix for Engineering case 740747 - "The Apache Relay Server did not respect the client's application timeout header" was incomplete for Apache 2.2.21 and 2.2.24 on Linux systems. This has been fixed.



CR:743367
CR Number:   743367
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 3950 07 Aug 2013 Fixed
11.0.1 3024 07 Aug 2013 Fixed
Description
Sybase Central would have reported an internal error on startup if it was configured to run with recent updates of the Java Virtual Machine (JVM), for example, 1.6.0 update 45, and if the Fast Launcher was turned on. This has been fixed.



CR:743448
CR Number:   743448
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1609 19 Jul 2013 Fixed
Description
If a column with a default was added to a table with existing data and the default was subsequently changed, some rows in the table could have been left in an inconsistent state resulting in assertions, crashes or incorrect results. This has now been fixed. A work around would be to unload and reload the table before the second ALTER.



CR:743465
CR Number:   743465
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 1606 16 Jul 2013 Fixed
12.0.1 3939 16 Jul 2013 Fixed
Description
Metric collection was not being done for most metrics. This has been fixed



CR:743469
CR Number:   743469
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 1726 11 Nov 2013 Fixed
Description
Setting the element of an array in a procedure could have caused the server to crash under some circumstances. This has been fixed.



CR:743562
CR Number:   743562
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 1608 18 Jul 2013 Fixed
Description
Using the 慏BCreatedVersion DBTools method against a version 16 database would have returned an incorrect value. This has been fixed.



CR:743572
CR Number:   743572
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 4658 18 Jul 2013 Fixed
Description
Clicking on a backup's 'backup result' link in the 'Back Up & Restore' panel for a database may have resulted in the error:

The task which created this backup (BP-XXXX) could not be found.



This has been fixed.



CR:743578
CR Number:   743578
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)
16.0.0 1644 08 Aug 2013 Fixed
12.0.1 3958 08 Aug 2013 Fixed
Description
In extremely rare, timing dependent cases, the server could have crashed when a database was starting. This has been fixed.



CR:743587
CR Number:   743587
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)
16.0.0 1607 18 Jul 2013 Fixed
12.0.1 3939 18 Jul 2013 Fixed
Description
When duplicating a user via copy-and-paste or drag-and-drop, the password for the new user was copied from the original user. Now, Sybase Central prompts for the new user抯 password.



CR:743592
CR Number:   743592
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 3019 29 Jul 2013 Fixed
Description
When rebuilding a database that used SQL Remote replication, the rebuild may have failed because a user id was already in use for a system user id in the new software version. The problem only occurred when the customer created database users with server version 6.0.3.2928 or before, and never rebuild the database using dbunload option -m. This has been fixed.



CR:743662
CR Number:   743662
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 1631 09 Aug 2013 Fixed
12.0.1 3950 09 Aug 2013 Fixed
Description
On a heavily loaded server, client connections could have been incorrectly dropped in timing dependent cases. If this occurred, the client would likely get "Communication error" error and the server would report " Disconnecting Client - 120 seconds since last contact" (or a different number of seconds) in the console log.



This has been fixed so the dropped connections are less likely. Note that these errors can still correctly occur if there is a network issue or if either the client or server computers completely bog down (most likely due to limited resources).



CR:743684
CR Number:   743684
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 1608 18 Jul 2013 Fixed
Description
The Extract Database wizard would have reported that the SELECT ANY TABLE system privilege was required, when in fact the SYS_REPLICATION_ADMIN_ROLE role is actually what is required. This has been fixed.



CR:743685
CR Number:   743685
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 4659 18 Jul 2013 Fixed
Description
If a user was on the Databases panel and filtered the list, then chose another panel, switching back to the Databases panel may have refreshed the databases list, but not have reapplied the filter. This has been fixed.



CR:743688
CR Number:   743688
Product Name:   MobiLink
Product Component:   MobiLink Profiler
Status:   Closed
OS:   Generic
Original Version:   16.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16.0.0 1608 19 Jul 2013 Fixed
Description
If the MobiLink Profiler database (MLProfilerDB) was closed while a profiling session was active then the profiling session was ended, a Java RuntimeException internal error would have occurred. This has been fixed. Now appropriate error dialogs are displayed.



CR:743689
CR Number:   743689
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 4659 19 Jul 2013 Fixed
Description
Changing the properties for a maintenance plan and setting an incremental backup schedule would not have save it if the 慚ake incremental backups checkbox was not selected. This has been fixed.



CR:743691
CR Number:   743691
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 4659 19 Jul 2013 Fixed
Description
In the Apply Maintenance Plan wizard, the user can choose to apply the plan to databases that use another plan. If the user gave an invalid maintenance plan name, or a maintenance plan that had no databases assigned to it, all databases would have been chosen. This has been fixed.



CR:743692
CR Number:   743692
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 1608 19 Jul 2013 Fixed
12.0.1 3940 19 Jul 2013 Fixed
Description
Servers with the fix for Engineering case 742355 could have returned garbage characters for connection_property( 'Name' ), if there were non-ASCII characters in the CON connection parameter. This has been fixed.



CR:743743
CR Number:   743743
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 1612 23 Jul 2013 Fixed
12.0.1 3941 23 Jul 2013 Fixed
Description
When an ADO.NET connection was closed and returned to the connection pool by the SQL Anywhere .NET Data Provider, the connection name was cleared. However, when the pooled connection was reclaimed from the pool, the ConnectionName was not restored. This problem has now been corrected.



CR:743761
CR Number:   743761
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 4660 22 Jul 2013 Fixed
Description
When editing Event Subscriptions for a user, the list of objects took longer and longer to populate when adding or removing an object. This has been fixed.



CR:743778
CR Number:   743778
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 1625 02 Aug 2013 Fixed
Description
Validation of a recently truncated table using a read-only server may have caused a crash. This has been fixed



CR:743779
CR Number:   743779
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 4660 23 Jul 2013 Fixed
Description
Typing a very long expression in the Search box or a Filter box would have resulted in a horizontal scroll bar appearing. 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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------