Sybase数据库技术,数据库恢复

• 首页
• 关于
• 订阅
• 归档
• 留言
• 标签
• 免费ASE测试环境
• 镜像站
• 恢复工具

CR:762532

CR Number:   762532 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 1896 22 Apr 2014 Fixed 12.0.1 4105 25 Apr 2014 Fixed Description The Overview page did not show the arbiter and mirror server names. This has been corrected.

CR:762535

CR Number:   762535 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 1893 22 Apr 2014 Fixed Description The Interactive SQL utility would have crashed if given a SQL file on the command line that did not exist and if the "on error" option was "continue" or "notify_continue". This has been fixed.

CR:762605

CR Number:   762605 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1894 23 Apr 2014 Fixed 12.0.1 4103 28 Apr 2014 Fixed Description The "Find/Replace" window for the syntax highlighting editor could have hung when searching up for a whole word if the search text appeared in the editor, but not as a separate word, and if the caret position was initially after the search text. This has been fixed. This prolem also affects the Interactive SQL utility. It has been present since version 9.0.2, possibly earlier.

CR:762606

CR Number:   762606 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1894 23 Apr 2014 Fixed 12.0.1 4103 23 Apr 2014 Fixed Description In the DBMirror sample that is included with the SQL Anywhere software, the mirror setup SQL script contained a typographical error so no mirror partner was established. The "mirror" partner merely acted as a copy node. Attempts to connect to the mirror partner would have failed. This problem has been corrected.

CR:762615

CR Number:   762615 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1895 23 Apr 2014 Fixed Description When communications occurred between the Outbound Enabler and the backend server with the command line option -cs containing https=1, the Outbound Enabler may have crashed or reported OEE1048 with missing detail. For example: OEE1048: The communication between the Outbound Enabler and the backend server failed with [MLC24: ???] while performing secured write. sidx=0 socket=01028188 sfp=58f2ed03 A workaround to diagnose the communication error in the case where the RSOE didnt crash is to look at the Relay Server log as the detail is sent there and reported as an OEE1048 embedded in RSE4015 with details. The crash has been fixed and the details in RSOE log have been restored. An example after the fix: OEE1048: The communication between the Outbound Enabler and the backend server failed with [MLC24: Server certificate not trusted. The system-specific error code is 336134278 (hex 14090086).] while performing secured write. sidx=0 socket=01028188 sfp=58f2ed03

CR:762616

CR Number:   762616 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 1897 28 Apr 2014 Fixed 12.0.1 4105 28 Apr 2014 Fixed 11.0.1 4105 28 Apr 2014 Fixed Description Under very rare circumstances, executing a query with a cached parallel plan could have crashed the server. This has been fixed.

CR:762676

CR Number:   762676 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 1895 25 Apr 2014 Fixed Description Importing from a CSV file which contained unquoted values could have failed if the values contained apostrophes or quotation marks in the middle of the value. This has been fixed.

CR:762683

CR Number:   762683 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 1895 25 Apr 2014 Fixed Description Importing data from a text file into a SAP HANA database could have failed with the message "Could not create table ... incorrect syntax near "long" ..." This problem would have occurred when importing character data into a new table. This has been fixed.

CR:762695

CR Number:   762695 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 1895 25 Apr 2014 Fixed Description If an attempt to cache a plan for a procedure statement caused execution of a poor quality reusable plan, this behavior would repeat with a fixed period of executions. This has been fixed.

CR:762775

CR Number:   762775 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 1896 25 Apr 2014 Fixed Description When connected to an ASE server using the "Generic ODBC Database" option in the "Connect" window, the Interactive SQL title was empty. Now, the text contains the server name, database name, login id and user id (if known). This was the same behavior as version 12, before this bug was introduced.

CR:762786

CR Number:   762786 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 1896 25 Apr 2014 Fixed 12.0.1 4105 25 Apr 2014 Fixed Description When the RSOE used -cs https=1 and a client had disconnected before receiving all response bytes from the backend server, subsequent communications with the backend server may have suffered from false OEE1048(MLC53) SSL handshake errors. This has been fixed. The RSOE may also have suffered false OEE1048(MLC8) SSL read errors when -cs https=1 was used. This has also been fixed.

CR:762797

CR Number:   762797 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1896 25 Apr 2014 Fixed 12.0.1 4105 25 Apr 2014 Fixed Description The text completer could have crashed when opened in an incomplete or poorly-formed SELECT...FROM clause. This has been fixed.

CR:762878

CR Number:   762878 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 1897 28 Apr 2014 Fixed Description If a CREATE OR REPLACE PROCEDURE/FUNCTION statement was executed on the primary server, and user connections needed to be dropped to apply this statement on a mirror/copy node, the procedure or function was not replaced on the mirror/copy node and no error was reported. This has been fixed. Note that CREATE PROCEDURE/FUNCTION and ALTER PROCEDURE/FUNCTION statements were not affected.

CR:762941

CR Number:   762941 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 1901 29 Apr 2014 Fixed Description Numeric data from columns with a FLOAT(precision) type used in a remote database might not have been uploaded into a HANA consolidated database correctly when the Precision was less than 25 and the HANA server revision number was greater than 66. This problem has now been fixed. A workaround for this problem is to start the MobiLink server with the hidden option, -hwg-

CR:762942

CR Number:   762942 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1900 29 Apr 2014 Fixed 12.0.1 4106 29 Apr 2014 Fixed Description The Interactive SQL utility (dbisql) could have crashed if the text completer was opened in poorly formed SQL. In order to crash, the caret would have to follow an unmatched quotation mark. This has been fixed.

CR:763011

CR Number:   763011 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 1901 29 Apr 2014 Fixed Description JSON attributes gidh, gurih and g__nexth, XML gidh elements, and XML attributes such as xml:base and href, would not have been encoded properly if they contained non-ASCII characters or ASCII characters that had special meaning in URLs. For example if an entity instance had a string key value of "A#1" and the entity set was called "Orders" the "#" and "" would not be properly encoded. While IDs are now properly encoded, titles and names are not. This has been fixed. All hyper link attributes are now encoded to use % escape sequences so they can be used as-is in HTTP requests.

CR:763021

CR Number:   763021 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 1901 29 Apr 2014 Fixed 12.0.1 4108 02 May 2014 Fixed Description A dbtools sample was expected to perform a backup of the Demo database as a way to demonstrate how to load and use the dbtools dynamic library. On Mac OS X, the dbtools sample would have failed to load the dbtools dynamic library, so it would return to the shell without performing the backup or producing any output. This has been fixed.

CR:763031

CR Number:   763031 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 1901 30 Apr 2014 Fixed 12.0.1 4107 30 Apr 2014 Fixed Description In very rare, timing dependent cases, starting a server with a mirrored database could have failed with the server failing assertion 101426. This has been fixed.

CR:763149

CR Number:   763149 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) 16.0.0 1903 01 May 2014 Fixed 12.0.1 4108 01 May 2014 Fixed Description If the Interactive SQL utility (dbisql) had been launched from Sybase Central to debug a stored procedure, and then closed while at a breakpoint, dbisql would have crashed. This has been fixed.

CR:763156

CR Number:   763156 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 1903 02 May 2014 Fixed Description An unlikely security vulnerability in the server has been fixed.

CR:763231

CR Number:   763231 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 4956 02 May 2014 Fixed Description If a certificate did not exist in the database, executing the statement DROP CERTIFICATE IF EXISTS <name> would have raised a certificate not found error (i.e. the if exists was ignored). This has been fixed.

CR:763241

CR Number:   763241 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 1905 05 May 2014 Fixed 12.0.1 4108 05 May 2014 Fixed Description In rare cases, the database server may have crashed while request level logging was turned on. This has been fixed.

CR:763414

CR Number:   763414 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1909 06 May 2014 Fixed Description The number of messages that could be displayed in the Interactive SQL utility's Messages panel was limited to 1000. This fixed limit has been removed.

CR:763523

CR Number:   763523 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1972 07 Jul 2014 Fixed 12.0.1 4135 07 Jul 2014 Fixed Description In UltraLiteJ, methods accessing uniqueidentifier values could have had an incorrect byte order. This has been fixed.

CR:763545

CR Number:   763545 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 1910 08 May 2014 Fixed 12.0.1 4110 08 May 2014 Fixed Description SET MIRROR OPTION auto_failover = 'On' was incorrectly being treated as 'Off'. As a workaround, SET MIRROR OPTION auto_failover = 'Yes' can be used. This has been fixed so that both 'On' and 'Yes' are now supported.

CR:763548

CR Number:   763548 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 1910 07 May 2014 Fixed Description OData requests to update a single nullable property could not have updated the property to null. This has been fixed.

CR:763621

CR Number:   763621 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) 16.0.0 1911 08 May 2014 Fixed Description If a web service of type JSON returned a floating-point number between -1 and 1, it would not have included a leading zero (eg. It would be returned .5 rather than 0.5). The JSON standard requires the leading zero. This has been corrected.

CR:763708

CR Number:   763708 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 1912 09 May 2014 Fixed Description The OData Producer would have rejected a configuration file that had multiple producers when it mistakenly thought the service roots were duplicates or subpaths of each other (for example, /a and /ab). This has been fixed.

CR:763803

CR Number:   763803 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 1914 13 May 2014 Fixed 12.0.1 4115 13 May 2014 Fixed Description Loading the following polygon: POLYGON((-1 -1, -1 1, 0 0, 1 1, 1 -1, -1 -1)) would have resulted in an invalid polygon error. This has been fixed. There is no known workaround.

CR:763804

CR Number:   763804 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 1914 13 May 2014 Fixed Description Differing case for Edm.Guid values in the request URL and request body could have caused an UPDATE to fail with an error message that the entity key cannot be modified. This has been fixed.

CR:763851

CR Number:   763851 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 1915 13 May 2014 Fixed Description Fetching the ServerNodeAddress connection property may have returned incorrect values for HTTP connections. For example, it may have returned an empty string for remote connections, or it may have returned a valid IP address for a local connection. This has been fixed.

CR:763854

CR Number:   763854 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 1915 13 May 2014 Fixed Description Many clients, including .NET, would not have specified the charset on the content type HTTP request header and would assume that the default for JSON and XML requests was UTF-8. The OData Producer always assumed that HTTP requests were ISO-8859-1 based on RFC 2616. This would have resulted in non-ASCII characters being incorrectly read. This has been fixed. The OData Producer now assumes UTF-8 for JSON and XML requests and ISO-8859-1 for plain text requests.

CR:763863

CR Number:   763863 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Microsoft Windows NT Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1919 20 May 2014 Fixed Description Running the Relay Server IIS 7.0 quick setup script on a system without a preexisting IIS installation, and then accessing SimpleTestApp.htm through IIS which was installed by the quick setup script would have resulted in a 404.4 response. The problem was that the StaticFileModule required for the demo was not installed. This has been fixed and the message associated with the install step has been extended to explain that the installation is neither minimal nor full and users are encouraged to customize the list of features to fit their actual web server needs.

CR:763864

CR Number:   763864 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Microsoft Windows NT Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1919 20 May 2014 Fixed Description Most Relay Server customers are not SQL Anywhere customers, but the Relay Server quick setup script was setting up services with a default SQL Anywhere prefix in the service name. This change overrides the default prefix to now be Relay Server instead in the IIS6 and IIS7/8 quick setup scripts.

CR:763866

CR Number:   763866 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 1915 13 May 2014 Fixed 12.0.1 4115 13 May 2014 Fixed Description The odbc.h header file that was used to compile ODBC applications could have provided an inconsistent definition of HWND and SQLHWND for 64-bit Windows and other 64-bit platforms. For 64-bit compilers, the type might resolve to a 32-bit integer which is incorrect. Window handles, like other handles, should always be 64-bit pointer-type objects for a 64-bit executable. This problem has been fixed.

CR:763867

CR Number:   763867 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 1915 13 May 2014 Fixed 12.0.1 4115 13 May 2014 Fixed Description The SQLErrorW, SQLDataSourcesW, and SQLGetDescRecW functions were incorrectly returning a byte count, rather than a character count. For example, the column name "ABC" has a character count of 3, but the wide character (Unicode) string "ABC" occupies 6 bytes. The byte count (6 in this example) was returned. This has been corrected. This problem could have also impacted the values returned by SQLError, SQLDataSources, and SQLGetDescRec if the driver manager called their "wide" equivalents. This problem is also corrected. In addition, SQLGetDescRec could return a random field name for a descriptor when there was no field name (for example, a bookmark column has no field name). There was also the extremely rare possibility of a segment violation fault. These problems have been corrected.

CR:763964

CR Number:   763964 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 1916 15 May 2014 Fixed Description The text "SAP Sybase IQ" was incorrectly displayed in the Categories list on the Options window. This has been corrected so that the text "SAP IQ" is now displayed.

CR:764027

CR Number:   764027 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1932 28 May 2014 Fixed Description When doing a ping operation using the MobiLink client (dbmlsync), the MobiLink server would have reported the following error: [-10410] The client failed to send a complete sequence of commands Ping request failed Other than the error message, the ping operation would have behaved correctly. This has been fixed so that the warning is now prevented from being issued.

CR:764049

CR Number:   764049 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 May 2014 DEFER Description An application using node.js would have crashed when the server returned NULL values. This has been fixed in version 1.0.1 of the driver, and the updated node module has been published to the node package manager (https://www.npmjs.org/package/sqlanywhere) and GitHub.

CR:764052

CR Number:   764052 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 1918 16 May 2014 Fixed Description Filter expressions using startswith(s1,s2) would have translated to a LOCATE() SQL function call, which does not result in the SQL Anywhere optimizer using indexes. This has been improved so that if the search string is a literal or parenthesized literal, whose length is less than 126, LIKE will now be used If the searched item is a column reference, a LIKE hint will be provided.

CR:764055

CR Number:   764055 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 1918 16 May 2014 Fixed Description Operations that compute expressions with string or NUMERIC types now have slightly improved performance.

CR:764062

CR Number:   764062 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 1917 16 May 2014 Fixed Description On servers where the number of connections executing at a lower priority level exceeded the number of connections executing at a higher priority level, more CPU cycles would have been given to the lower priority tasks. This has been fixed.

CR:764064

CR Number:   764064 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 1989 30 Jul 2014 Fixed 12.0.1 4145 30 Jul 2014 Fixed Description If a CLR stored procedure attempted to create an SAConnection using the connection string from the SAServerSideConnection object; the server and CLR External Environment would both have crashed. For example, if calling a CLR stored procedure resulted in code similar to the following being executed on the CLR External Environment side: SAConnection local_conn = new SAConnection( SAServerSideConnection.Connection.ConnectionString ); Local_conn.Open() then both the SQL Anywhere Server and the corresponding CLR External Environment would crash. This problem has now been fixed.

CR:764130

CR Number:   764130 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 1915 16 May 2014 Fixed 12.0.1 4104 16 May 2014 Fixed Description Some additional fixes were required for Engineering case 761751.

CR:764386

CR Number:   764386 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 2048 25 Nov 2014 Fixed 12.0.1 4193 25 Nov 2014 Fixed Description If an application executed a query against a Microsoft SQL Server proxy table that contained SELECT FIRST or a subquery in an IF EXISTS( ), then there was a chance the Remote Data Access layer would incorrectly send the SELECT FIRST to the remote server. Note that a similar problem existed with remote Oracle servers as well. These problems have now been fixed and the Remote Data Access layer will now send a TOP 1 instead. Workaround Description  rewrite the IF-Statement IF (SELECT count(*) FROM <proxy table> ...) > 0 THEN

CR:764411

CR Number:   764411 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 1925 22 May 2014 Fixed 12.0.1 4119 22 May 2014 Fixed 11.0.1 3156 22 May 2014 Fixed Description If the first line of the HTTP response from an outbound client HTTP request was split across two or more packets then the server would have failed to accept the response from the remote server. This has been fixed.

CR:764425

CR Number:   764425 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 1924 22 May 2014 Fixed Description In some cases the server cache would not shrink. This would have happened after a drop in server activity that prompted rapid cache growth. The rapid cache growth had to have happened because of an allocation of pages for heap or temporary table pages. Although the cache was not able to shrink, it would have been reused. This has now been fixed.

CR:764516

CR Number:   764516 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 1925 22 May 2014 Fixed Description In the "Connect" dialog for an UltraLite database, if "Tools/Copy Connection String to Clipboard" was clicked, the database encryption key (if set) was copied in clear text to the clipboard. This has been corrected so that the key is now replaced by three asterisks, the same as for the connection password.

CR:764620

CR Number:   764620 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 1926 23 May 2014 Fixed Description The system procedure sa_certificate_info() was returning binary data for the Serial Number field of a certificate. This has been fixed so that it now returns a hexadecimal representation of the serial number.

CR:764632

CR Number:   764632 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 1926 26 May 2014 Fixed Description When using the Import Wizard to import shape file data into a database, the wizard showed a page which prompted for a table in which to save the data. That page included a component that listed all of the owners in the database. That list inadverently contained system-defined role names. This has been corrected so that these names are no longer in the list.

CR:764783

CR Number:   764783 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 1931 28 May 2014 Fixed Description GET requests with $top=0 should be allowed on collections but return no result. and an HTTP 500 error. This has been fixed.

CR:764810

CR Number:   764810 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 1959 02 Jun 2014 Fixed 12.0.1 4130 02 Jun 2014 Fixed Description On Linux and Mac OSX platforms, the server was not accepting denormal double values in INSERT statements. This has been fixed.

CR:764849

CR Number:   764849 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) 16.0.0 1938 02 Jun 2014 Fixed 12.0.1 4119 02 Jun 2014 Fixed Description If a very long string was unloaded from a database and was loaded into a second database with a different character set, the LOAD TABLE statement may have returned the SQL error: -1313, Maximum string length exceeded. This was only likely to happen if the length of the string was within a page size of the string limit of 2GB-1. This has been fixed.

CR:764913

CR Number:   764913 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 1933 30 May 2014 Fixed Description The following features are not supported on Linux/ARM and these features have now been disabled on this platform: - Remote Data Access - External Stored Procedures (note these are native dlls and shared objects that are loaded in process) - External Environments (including JAVA, CLR, PERL, PHP, C_ODBC and C_ESQL external environments) - LDAP UA - Kerberos Authentication

CR:764973

CR Number:   764973 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 1951 16 Jun 2014 Fixed 12.0.1 4126 16 Jun 2014 Fixed Description In rare, timing dependent cases, the server could have failed assertion 101201 - "Deferred growth not suspended for checkpoint" after a cancelled backup which did a log rename or truncate. This has been fixed.

CR:765031

CR Number:   765031 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 1945 13 Jun 2014 Fixed 12.0.1 4124 13 Jun 2014 Fixed Description A polygon in a Round Earth SRS could have failed to be represented correctly if it contained an edge on the equator going east to west and crossing latitude 0. This has been fixed.

CR:765281

CR Number:   765281 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   16.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1958 25 Jun 2014 Fixed Description In low memory situations, or where the maximum cache size was set low, it was possible for the UltraLite runtime to crash. This has been fixed.

CR:765332

CR Number:   765332 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 1944 10 Jun 2014 Fixed 12.0.1 4122 10 Jun 2014 Fixed Description If the alias name in a SQL statement was longer than 128 characters, a SQL Anywhere .NET data provider client application could have crashed. Example: SELECT 'string' AS "alias...name" FROM dummy Similarily, if a SQL column expression contained more than 128 characters, a .NET client application could have crashed. Example: SELECT 1+2+3+...+1000 FROM dummy These problems have been fixed. Alias and expression names are now restricted to at most 128 characters by the SQL Anywhere .NET data provider. As a work-around for the first case, restrict the length of alias names to at most 128 characters. Example: SELECT 'string' AS expr FROM dummy As a work-around for the second case, use an alias name and restrict the length of its name to at most 128 characters. Example: SELECT 1+2+3+...+1000 AS expr FROM dummy

CR:765334

CR Number:   765334 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 1946 13 Jun 2014 Fixed 12.0.1 4124 13 Jun 2014 Fixed Description In a .NET application, a buffer overrun could have resulted when using an SADataReader to get the value of a very long column value. Example: SELECT SPACE(1147483643) FROM dummy The possible buffer overrun has been corrected.

CR:765363

CR Number:   765363 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 1942 09 Jun 2014 Fixed Description In timing dependent cases, the server could have crashed, or otherwise failed, if a backup was cancelled. This has been fixed.

CR:765434

CR Number:   765434 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2006 28 Aug 2014 Fixed 12.0.1 4157 28 Aug 2014 Fixed Description Creating a publication with an article greater than 256 bytes in length would have resulted in crash of the UltraLite runtime. This has been corrected so that articles of up to 2048 bytes in length are now supported. SQLE_STRING_PARM_TOO_LONG is now reported when a publication predicate is >=2048 bytes. The database must be created or rebuilt to access the larger publication article size. Older databases will continue to work with a max publication article size of 256 bytes. Databases created or rebuild with this change will run on older runtimes provided publication articles are <= 256 bytes.

CR:765443

CR Number:   765443 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 1946 09 Jun 2014 Fixed 12.0.1 4124 09 Jun 2014 Fixed 11.0.1 3166 09 Jun 2014 Fixed Description Reading beyond the end of a file (e.g., for a LOAD TABLE statement from a 0-length file) on Linux when the file is on a remote NFS drive may cause the server to crash. This will only happen if O_DIRECT is enabled over NFS in Linux kernel versions 3.5, 3.6, and 3.7. Details of the kernel bug can be found here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/nfs/direct.c?id=67fad106a219e083c91c79695bd1807dde1bf7b9 This has been fixed. Direct I/O will no longer be used for remote file systems on these Linux versions. Upgrading the Linux kernel to at least 3.8 is the only workaround.

CR:765449

CR Number:   765449 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 1944 10 Jun 2014 Fixed 12.0.1 4122 10 Jun 2014 Fixed Description The Relay Server keeps records of statistics per type of client and there is an internal limit of 1600 types per backend server in the backend farm. When this limit was reached the Relay Server would have issued an RSF13011 error and failed the relay. This has been fixed with the following changes: - The Relay Server no longer creates new metrics until the rs_monitor.dll has been accessed. Most partners dont distribute rs_monitor.dll. - If rs_monitor.dll has been accessed and the number of client types of a backend server has exceeded 1600, a new RSW107 warning is issued instead of the RSF13011 fatal error. - In the RSW107 situation, the Relay Server will continue to relay the traffic, but no new metrics are created for the new client type.

CR:765512

CR Number:   765512 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 1945 11 Jun 2014 Fixed 12.0.1 4123 11 Jun 2014 Fixed Description When the Outbound Enabler used a secure HTTPS connection to the backend server, if the connection to the backend server was re-used after it was recycled, it was possible for the Outbound Enabler to have crashed. This has been fixed.

CR:765566

CR Number:   765566 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 1945 12 Jun 2014 Fixed 12.0.1 4123 12 Jun 2014 Fixed Description Certain syntactically-invalid queries using SELECT FROM DML constructs could have caused the server to crash. This has been fixed.

CR:765821

CR Number:   765821 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 1933 16 Jun 2014 Fixed 12.0.1 4122 16 Jun 2014 Fixed Description Server could have hang while executing a stored procedure that invoked other stored procedures. This has been fixed.

CR:765825

CR Number:   765825 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 1951 16 Jun 2014 Fixed 12.0.1 4126 16 Jun 2014 Fixed 12.0.1 4126 10 Oct 2014 Fixed Description IQ customers might experience a failure invoking the stored procedure sa_checkpoint_execute with a database assertion failure. This has now been fixed.

CR:765928

CR Number:   765928 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1952 18 Jun 2014 Fixed Description Transient device write failures (that is, OS file-write primitives intermittently reporting failure) could have resulted in subsequent UltraLite database corruption. This has been fixed. Note, device I/O errors still require the database to be restarted. Corrupt databases can be detected with the Validate API or ulvalid utility.

CR:765979

CR Number:   765979 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 1953 19 Jun 2014 Fixed 12.0.1 4127 19 Jun 2014 Fixed Description Calls to connection_property( 'TempFilePages' ) could have incorrectly returned values greater than 2 billion when 0 should have been returned. This has been fixed.

CR:765993

CR Number:   765993 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 1954 20 Jun 2014 Fixed 12.0.1 4128 20 Jun 2014 Fixed Description The server allows one extra connection beyond the connection limit as long as that connection has the DROP CONNECTION privilege (or DBA authority prior to version 16). This is to allow that connection to drop other connections if all connections to a server become blocked. However, once this extra connection was made, the server would not have allowed new connections until, (a) that extra connection went away, or (b) two other database connections went away. This has been fixed (b) above has been changed to one other database connection goes away.

CR:766053

CR Number:   766053 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) 20 Jun 2014 Fixed Description If a PHP string variable X points to the same content as variable Y, and variable Y is bound to a SQL Anywhere parameter using sasql_stmt_bind_param, the contents of variable X would have been corrupted. This has been fixed.

CR:766057

CR Number:   766057 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) 04 Jul 2014 Fixed Description In rare cases, the mirror could have taken many minutes to become synchronized if the primary was not committing any changes. During this time, if the primary failed the mirror could not take over as primary. Also, during this time a measurable amount of network traffic would be observed between the primary and mirror. This has been fixed.

CR:766113

CR Number:   766113 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 1965 02 Jul 2014 Fixed 12.0.1 4132 02 Jul 2014 Fixed Description The ADO.NET provider would not have been able to roll back a transaction if CHAINED option was OFF. This has ben fixed by setting CHAINED option to ON after opening a database connection.

CR:766115

CR Number:   766115 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 1954 20 Jun 2014 Fixed 12.0.1 4128 20 Jun 2014 Fixed Description Visual Studio 2013 integration was not supported. SetupVSPackage has now been modified to create registry keys for Visual Studio 2013.

CR:766132

CR Number:   766132 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1967 03 Jul 2014 Fixed Description If the ODBC driver or other client interfaces ran out of memory they could have crashed. This has been fixed.

CR:766224

CR Number:   766224 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 1954 25 Jun 2014 Fixed Description When running the SQLA SP installer in silent mode on Linux, it could incorrectly have given the error "The registration key provided is invalid." This has been fixed.

CR:766303

CR Number:   766303 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 1959 25 Jun 2014 Fixed Description The server usage text should display the switches in alphabetical order. "-sbx" was not placed properly. This has been fixed.

CR:766369

CR Number:   766369 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1960 26 Jun 2014 Fixed 12.0.1 4130 26 Jun 2014 Fixed Description When running sqlpp on Linux systems with a recent version of glibc, a syntax error could have been reported for perfectly good code. Moreover, the "near" text may have appeared mangled. For example, running the following statements through sqlpp: EXEC SQL BEGIN DECLARE SECTION; EXEC SQL END DECLARE SECTION; would have resulted in the following error: test.sqc(35): Error! E2636 near 'AREARE': Incorrect Embedded SQL syntax This has been fixed. There is no known workaround for this.

CR:766464

CR Number:   766464 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 1961 26 Jun 2014 Fixed 12.0.1 4131 26 Jun 2014 Fixed Description Host name and Relay Server version information have now been removed from the status page when accessed through the client or server extension. The information still remains available via the optional admin or monitor extensions. The admin and monitor extensions are expected to be accessible by administrators only.

CR:766511

CR Number:   766511 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 1962 27 Jun 2014 Fixed 12.0.1 4131 27 Jun 2014 Fixed Description In Visual Studio, incorrect major version information for the SQL Anywhere plugin may have been shown in the "Choose Data Source" and "Add Connection" dialogs on non-English systems. This has been corrected.

CR:766532

CR Number:   766532 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 4231 27 Jun 2014 Fixed Description If invalid HTTP parameters were provided to the database server running on Unix systems, the server may have detected, but tyhen hung. This has been fixed.

CR:766935

CR Number:   766935 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1969 07 Jul 2014 Fixed 12.0.1 4143 07 Jul 2014 Fixed Description UltraLite Initialize Database utility would have reported ?missing string? as the description for some collations (ulinit -Z). This has been fixed.

CR:767046

CR Number:   767046 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 1972 07 Jul 2014 Fixed Description If the Data Source utility (dbdsn) was used to create, modify, or delete a DSN, and the Driver connection parameter was used, the driver name would have needed to match the installed driver name exactly. This has been fixed so that the name is now case-insensitive.

CR:767047

CR Number:   767047 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) 07 Jul 2014 Fixed Description If a database was initialized or upgraded with the SQL SECURITY INVOKER model using version 16 software, then calling any of the procedures below would have incorrectly verified procedure permissions using the current logged in user, instead of the current effective user. This would have led to incorrect 'permission denied' errors if any these procedures were called from another procedure that was defined with SQL SECURITY DEFINER, and the owner of that outer procedure had permission to execute any of these system procedures, but the logged in user did not have the same permissions. This problem has now been fixed. The affected system procedures are: - sa_server_option - sa_db_option - sp_create_secure_feature_key - sp_alter_secure_feature_key - sp_drop_secure_feature_key Note, the original permission denied problem still exists if the database is initialized or upgraded with the legacy SQL SECURITY DEFINER model.

CR:767050

CR Number:   767050 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 1973 08 Jul 2014 Fixed 12.0.1 4136 08 Jul 2014 Fixed Description Under rare circumstances, the server could have failed a fatal assertion with a Dynamic memory exhausted error. This has been fixed.

CR:767053

CR Number:   767053 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 2050 02 Dec 2014 Fixed 12.0.1 4196 02 Dec 2014 Fixed Description Applications that attempted to make server side calls in a CLR External Environment would only have worked with .NET 2.0 or 3.5. Applications could use the CLR External Environment with assemblies targeted at .NET 4.0 or 4.5, provided those assemblies did not make server side calls back to the SQL Anywhere server. This problem has now been fixed, and new CLR External Environment executables have now been included for use with .NET 4.0 or 4.5. It should be noted that only one CLR External Environment can be launched per database. Hence applications need to decide prior to starting the CLR External Environment which version of .NET should be used. By default, the server will launch the CLR External Environment that will allow server side calls using either the .NET 2.0 or 3.5 Provider. If an application needs to make server side calls using .NET 4.0; then the following ALTER EXTERNAL ENVIRONMENT statement must be executed prior to starting the CLR External Environment: ALTER EXTERNAL ENVIRONMENT CLR LOCATION 'dbextclr[VER_MAJOR]_v4.0 ' Similarly, if an application needs to make server side calls using .NET 4.5; then the following ALTER EXTERNAL ENVIRONMENT statement must be executed: ALTER EXTERNAL ENVIRONMENT CLR LOCATION 'dbextclr[VER_MAJOR]_v4.5 ' If the application needs to go back to .NET 2.0 or 3.5; then the following ALTER EXTERNAL ENVIRONMENT statement must be executed: ALTER EXTERNAL ENVIRONMENT CLR LOCATION 'dbextclr[VER_MAJOR] ' Note that in each of the above [VER_MAJOR] should NOT be replaced with one of 12 or 16. It is best to keep [VER_MAJOR] as is in order to ensure a smooth transition to a newer version of SQL Anywhere if needed.

CR:767121

CR Number:   767121 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 1973 08 Jul 2014 Fixed 12.0.1 4136 08 Jul 2014 Fixed Description If an application attempted to execute an ALTER EXTERNAL ENVIRONMENT statement on a case sensitive database, then the server would return an external environment not found error if the environment name was specified in mixed or upper case. This problem has now been fixed.

CR:767365

CR Number:   767365 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 1982 18 Jul 2014 Fixed Description Execution of an ALTER TABLE ADD with multiple add clauses, each containing a default value, may have caused server assertion failures. This has been fixed. Workaround Description  Add the columns by executing ALTER TABLE for each column.

CR:767530

CR Number:   767530 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 1992 06 Aug 2014 Fixed 12.0.1 4148 06 Aug 2014 Fixed Description The SQL Anywhere ODBC sample inside the C example directory (odbc.c) used ODBC 2.0 calls and could not link against the SQL Anywhere Driver Manager for Unix on Unix platforms. This has been corrected so that the sample now utilizes ODBC 3.0 calls and can link against the driver manager successfully.

CR:767595

CR Number:   767595 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 1989 18 Jul 2014 Fixed Description For same-machine HTTP connections, connection_property(ClientNodeAddress) would have returned an IP address (usually 127.0.0.1 or ::1). For same-machine connections, this property should return an empty string. This has been fixed.

CR:767780

CR Number:   767780 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 1986 22 Jul 2014 Fixed 12.0.1 4142 22 Jul 2014 Fixed Description The server could have taken a long time to shutdown if the built-in HTTP server was used during previous executions of any server on the same computer. Other side effects of this problem may also have been seen: - If the sadiags.xml file was large then the merge-to-disk operation that automatically happens at midnight each day may have taken a long time and any other operation that caused a feature to be counted would have blocked until the merge was complete. I.e. some operations at midnight may have been seen to hang or take longer than usual to complete. - Mobilink servers could also suffer the slow shutdown (or midnight sync) problem if a database server was running on the same computer and that database server had generated a large sadiags.xml file. This has been fixed. A work-around is to delete the sadiags.xml file prior to shutting down the server. This should only be expected to improve the shutdown time if the size of the file is large (e.g. over 100K bytes). Workaround Description  Regular delete the "sadiags.xml" file from the "diagnostics" folder.

CR:767793

CR Number:   767793 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 1987 25 Jul 2014 Fixed 12.0.1 4143 25 Jul 2014 Fixed Description In rare, timing dependent cases, when the primary went down and the mirror failed over to become the new primary, it was possible the transaction log on the new primary to contain operations that were never applied to the database. This could have resulted in the database file on the primary being different from the database file on the mirror and any copy nodes. The mirror or copy nodes could have failed with errors or assertions related to applying the transaction log. This issue was possible, but extremely unlikely and never observed, if the synchronization_mode was synchronous. It had been observed if the synchronization mode was asynchronous or asyncfullpage. This has been fixed.

CR:767799

CR Number:   767799 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 1983 21 Jul 2014 Fixed 12.0.1 4140 21 Jul 2014 Fixed Description When attempting to create a database with the reserved name utility_db(a very rare use case), the server would have leaked memory. This has been fixed.

CR:767805

CR Number:   767805 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 1980 21 Jul 2014 Fixed 12.0.1 4140 21 Jul 2014 Fixed Description The server could have crashed when performing a query containing a CUBE or ROLLUP, or that specified grouping sets. This was only possible when the server was operating in a memory-constrained environment. This has been fixed.

CR:767808

CR Number:   767808 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 1983 21 Jul 2014 Fixed Description If the Information utility (dbinfo), or the Validation utility (dbvalid), or the VALIDATE DATABASE statement, was run against a database and a backup of that database was done shortly thereafter, there may have been problems recovering the backup. This has been fixed.

CR:767873

CR Number:   767873 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 1983 21 Jul 2014 Fixed 12.0.1 4141 21 Jul 2014 Fixed Description The server could have crashed when performing a recursive union query. This would only have occurred when running the query against a server with a very small buffer pool or many active memory-intensive queries. This has now been fixed.

CR:767881

CR Number:   767881 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1989 24 Jul 2014 Fixed 12.0.1 4142 24 Jul 2014 Fixed Description When SQL Remote was generating messages, if a change had been made to a column with a numeric or decimal data type, SQL Remote would have failed to add information to the message that would have allowed the receiving side to have performed conflict resolution. This issue has now been fixed.

CR:767963

CR Number:   767963 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2007 19 Aug 2014 Fixed 12.0.1 4157 19 Aug 2014 Fixed Description Calling the system procedure xp_cmdshell() could have caused the server to shut down on UNIX in rare, timing-dependent events. This has been fixed. There is no known workaround.

CR:768034

CR Number:   768034 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 2014 18 Sep 2014 Fixed 12.0.1 4162 18 Sep 2014 Fixed Description In rare timing dependent cases, a synchronized mirror server could have failed to take over as primary when the old primary went down. In order for this problem to have occurred the mirror database must have restarted while the primary server was still running. This has been corrected.

CR:768174

CR Number:   768174 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 1987 25 Jul 2014 Fixed 12.0.1 4143 25 Jul 2014 Fixed Description When using the SQL Anywhere .NET Data Provider, decimal values would have been displayed with trailing zeroes removed. For example, instead of 5.1000, it would have been displayed as 5.1. This was an unintentional change in behavior which has now been corrected.