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

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

CR:755372

CR Number:   755372 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 1795 16 Jan 2014 Fixed 12.0.1 4058 16 Jan 2014 Fixed Description If the Certificate Creation utility (createcert) was used without the -3des option, a compatibility warning was displayed warning that the resulting certificate would not be compatible with older versions of the software. The build numbers shown in this message were incorrect. This has been corrected.

CR:755388

CR Number:   755388 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 1794 17 Jan 2014 Fixed Description With UltraLite for WinRT, file transfers with the stream parameter compression=zlib would have failed, resulting in MobiLink communication error code 224. This has been fixed.

CR:755389

CR Number:   755389 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 1795 17 Jan 2014 Fixed Description A $links request could have failed when a $orderby was used that included a non-key property of the related entity type. This has been fixed.

CR:755513

CR Number:   755513 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 1803 17 Jan 2014 Fixed Description The message used to shutdown the OData server (dbosrv16) was too generic. This has now been chabged from 'shutdown' to 'shutdown_sap_sqla_odata'. Note, older dbostop16 utilities will not be able to shutdown newer OData Server, and new dbostop16 utilities will not be able to shutdown older servers.

CR:755522

CR Number:   755522 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) 1796 20 Jan 2014 Fixed Description The Quick Setup script for the Apache Relay Server would have generated a RSConfigFile directive inside <LocationMatch /srv/iarelayserver..> tag. This directive is no longer produced now.

CR:755524

CR Number:   755524 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 1802 23 Jan 2014 Fixed 12.0.1 4060 23 Jan 2014 Fixed 11.0.1 3100 23 Jan 2014 Fixed Description Under rare circumstances, queries using hash filters could have caused the server to crash. This was more likely in environments with a heavy load, and/or cursors held open for long periods of time. This has been fixed.

CR:755529

CR Number:   755529 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 1796 20 Jan 2014 Fixed 12.0.1 4058 20 Jan 2014 Fixed Description Creating a certificate with an expiry date beyond 2050 would have resulted in a certificate that expired 100 years before the expected expiry date. This has been fixed.

CR:755531

CR Number:   755531 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) 17 Jan 2014 Fixed Description When using $format, it did not accept long forms of content-types, for example: $format=application/atom, $format=application/json, or $format=application/atom+xml. This has been fixed.

CR:755676

CR Number:   755676 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 1800 21 Jan 2014 Fixed 12.0.1 4059 21 Jan 2014 Fixed Description In very rare, timing dependent cases, establishing a connection with a non-default maximum packet size connection parameter could have caused a loaded server to crash. The default maximum packet size for a server can be specified using the -p server option. A client application can request a different packet size using the CBSize connection parameter. Mirroring servers containing Engineering case 750502 change would also have used a non-default maximum packet size. This has now been fixed.

CR:755767

CR Number:   755767 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 1803 23 Jan 2014 Fixed 12.0.1 4061 23 Jan 2014 Fixed Description Iif the OUTPUT statement was attempting to write a string which contained characters whose Unicode representation was greater than U+FFFF (known as "supplementary characters"), the statement would have failed with the message "Could not save result set. Input length = 1" This has been fixed.

CR:755792

CR Number:   755792 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) 21 Jan 2014 Diagnostic Provided Description Feature request to have a command in dbisql that displays the list of reserved keywords.

CR:755797

CR Number:   755797 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 1803 22 Jan 2014 Fixed Description HTTP header names in batch requests were not case-insensitive. This would have resulted in valid HTTP headers being ignored in the parts of a batch request. This has been fixed.

CR:755840

CR Number:   755840 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.0 4852 22 Jan 2014 Fixed Description When initializing a cloud on Windows, checking the "Use FIPS encryption" checkbox would not have initialized the cloud for FIPS. This has been fixed.

CR:756026

CR Number:   756026 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 1803 23 Jan 2014 Fixed Description The following new features have been added to the OData Producer. Please see documentation for full details. - The OData Producer now supports Optimistic Concurrency Control as defined by versions 2.0 of the OData Specification. Using the OSDL model definition file (see Example 1), a developer may specify a set of properties on an Entity Type to define the concurrency token of the Entity. - The OData Producer now supports Service Operations using HTTP GET and POST methods as specified by version 2.0 of the OData Specification. Developers must declare explicitly what service operations to expose in an OSDL file. - OData Producer uses less objects when caching metadata for users that have (from the OData Producers perspective) identical access. - OSDL files support added escape sequences in quoted strings - Associations are now annotated as referential constraints in the metadata and association properties of referential constraints are now visible by default. Association may also have OnDelete attributes in the metadata which documents how the dependent entity instance is affected when the associated principal entity instances is delete. - The log generated by OData Producers has been enhanced to identify the producer and request associated with each log event. - OData server supports multiple producers dbosrv16 can now host multiple producers, each connecting to a different database. All producers share the same options configuration file and are hosted on the same port. The producer configuration file syntax has been augmented for this feature. - The OData producer now supports a greater subset of the OData Service Definition Language (OSDL). The new supported syntax adds the ability to: - Explicitly set the name of tables that are exposed through the producer - Explicitly include/exclude columns - Define entity sets with generated keys - Define associations between entities, including complex associations that use an underlying association table - Define navigation properties

CR:756028

CR Number:   756028 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 1810 04 Feb 2014 Fixed 12.0.1 4065 04 Feb 2014 Fixed Description Under rare circumstances, a server that was performing request level logging could have crashed when executing stored procedure code. This has been fixed.

CR:756032

CR Number:   756032 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   16.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1803 24 Jan 2014 Fixed 12.0.1 4061 24 Jan 2014 Fixed Description If two subscribed publication articles contain two of the same tables and both contained the same list of columns, when adding a synchronization subscription to the second publication the database server would have erroneously reported the error: SQLCODE -1325: Column subset for table '%1' in publication '%2' does not match that specified in publication '%3' This has been fixed.

CR:756038

CR Number:   756038 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 1803 23 Jan 2014 Fixed Description If an OData server was shutdown and immediately restarted, it could have failed to connect to its port or shutdown port. This has been fixed.

CR:756118

CR Number:   756118 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 1808 28 Jan 2014 Fixed 12.0.1 4064 28 Jan 2014 Fixed Description The server may have incorrectly returned the non-fatal assertion error 106104 "Field unexpected during compilation" for an IN list predicate, if the IN list contained expressions with column references for which the value was unknown at open time. This has been fixed. Workaround Description  The workaround for this question is: 1 - Change the 'case' statement as described below for a new code described in item 2: Y.CODI_IMP IN (2, (CASE WHEN P.SUBST_PAR = 'S' THEN 9 ELSE 0 END), 30)) AS TDDEDUCAO 2 - New code: ( Y.CODI_IMP IN (2, 30) OR (P.SUBST_PAR = 'S' AND Y.CODI_IMP = 9) OR (P.SUBST_PAR <> 'S' AND Y.CODI_IMP = 0) )

CR:756129

CR Number:   756129 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 1804 24 Jan 2014 Fixed Description Queries comparing a timestamp with time zone column to a string literal could have returned incorrect results. This has been fixed.

CR:756266

CR Number:   756266 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 4854 27 Jan 2014 Fixed Description When running a cloud based on SAODE SP3, and when using SQL Anywhere version 12 to run the Primary server, the Cloud would have failed to see any software updates. It would also have failed to synchronize usage information. This has been fixed.

CR:756394

CR Number:   756394 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 1835 25 Feb 2014 Fixed 12.0.1 4078 25 Feb 2014 Fixed Description Under exceptional rare circumstances, the server may have crashed when trying to reuse a cached query plan if tables used in the query were dropped and recreated. This has been fixed.

CR:756565

CR Number:   756565 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 1810 30 Jan 2014 Fixed Description Parameters of the function substringof() were used in the wrong order, and has now been corrected. The intended meaning of substringof( s1, s2 ) was return whether or not s1 is a substring of s2. The OData server was doing the opposite, return whether or not s2 is a substring of s1.

CR:756681

CR Number:   756681 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 1829 18 Feb 2014 Fixed 12.0.1 4071 18 Feb 2014 Fixed Description In rare cases, the server could have returned an error like: "Table '_^_^_22072007_^_^_759_^_^_22072007_^_^_' not found" for an internal temporary table if an INSERT, UPDATE, or DELETE statement triggered the change of an immediate materialized view. The problem only happened when the very first INSERT, UPDATE, or DELETE of the table in a connection was executed in a nested block, for example a trigger or procedure. In this case subsequent DML operations on the table may then have returned the above error. This has been fixed.

CR:756707

CR Number:   756707 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   6.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1815 05 Feb 2014 Fixed 12.0.1 4066 05 Feb 2014 Fixed 11.0.1 3100 05 Feb 2014 Fixed Description Sybase Central could have crashed if it was running and something was done to change the Windows desktop theme. This same problem could have been encountered when using a Remote Desktop Connection with a low-bandwidth connection; in that configuration, Remote Desktop may automatically change the desktop theme to satisfy the bandwidth limitations. This issue was partially fixed by the changes for Engineering case 752610, but this change goes beyond it by fixing the following problems as well: - On the Search panel, the "Search" button enabling logic and the button's clicking logic would stop working after the look-and-feel changed. - Sybase Central could have crashed if any of the following panels/windows were open when the look and feel were closed: 1. "Results" on the "Search" pane 2. The list of plug-in in the "Sybase Central Plug-ins" window. 3. The connection profiles window 4. The About window 5. The Disconnect window - The background color of items in details panels would have been painted gray (rather than white) after switching look-and-feel. - Drop-down toolbar buttons (e.g. "Tools") did not draw their arrow, and did not open when clicked.

CR:756745

CR Number:   756745 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1813 03 Feb 2014 Fixed 12.0.1 4065 03 Feb 2014 Fixed Description Simulating the time in between synchronizations when replaying a persistent connection could have caused the synchronization to timeout. This has been fixed.

CR:756777

CR Number:   756777 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 1849 10 Mar 2014 Fixed 12.0.1 4084 10 Mar 2014 Fixed Description In rare cases, the server may have crashed when executing an invalid plan that contained an equi-join to a correlated subquery. This has been fixed.

CR:756786

CR Number:   756786 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 1815 05 Feb 2014 Fixed 12.0.1 4066 05 Feb 2014 Fixed Description In the Console utility (dbconsole), if the Connections panel was configured to show the last reported statement, and the statement was longer than 255 characters, a "Right truncation of string data" error would have been reported. This has been fixed.

CR:756801

CR Number:   756801 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 1814 04 Feb 2014 Fixed 12.0.1 4065 04 Feb 2014 Fixed Description The builtin SQL functions HTTP_BODY, HTTP_HEADER and HTTP_RESPONSE_HEADER were returning an empty string when the required value did not exist, instead of NULL as documented. This has been corrected so that they now return NULL when the required value does not exist. As well, the builtin function HTTP_RESPONSE_HEADER has been corrected to recognize the special header name @HttpStatus and return the status code if given @HttpStatus.

CR:756878

CR Number:   756878 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 1815 04 Feb 2014 Fixed Description Improperly encoded URIs could have caused an internal server error. For example, executing the query "http://localhost:8105/odata/Filter03/T6?$filter=c1 eq '%'" against the OData producer, would have caused the following internal server error: HTTP ERROR: 500 Problem accessing /odata/Filter03/T6. Reason: while trying to invoke the method com.sybase.odata.producer.util.RequestWrapper.getParameterMap() of a null object loaded from field com.sybase.odata.producer.handler.AbstractHandler.request of an object loaded from local variable 'this' This has been fixed. Clients will now get HTTP ERROR: 400 Bad Request <?xml version="1.0" encoding="utf-8"?> <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> <code>30175</code> <message xml:lang="en-US">An error occured while parsing the request URI at offset 59.</message> </error>

CR:756886

CR Number:   756886 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 1822 10 Feb 2014 Fixed 12.0.1 4068 10 Feb 2014 Fixed Description Mirroring servers now log more detailed information to the console log in the following cases: - when failover occurs and the mirror server takes over as the primary "Now running as primary server" is now logged. Previously, "Database <name> (<file>) started at <date/time>" was logged, which was incorrect because the database was already started and was not restarted. - if the mirror server was behind applying operations and caused the primary to block for more than 10 seconds, "primary blocked for <number> seconds waiting for the mirror to catch up" is logged. - transaction log start and current offsets are now displayed when starting up a database and at other transitions (such as when the transaction log is restarted). - if there was an unexpected error that caused applying the transaction log to fail, a message is displayed and the database is not automatically restarted

CR:756960

CR Number:   756960 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 1817 29 Sep 2014 Fixed Description If starting a database on a server with the -udf abort option failed due to an assertion failure, trying to start another database with the same name would have returned a "database name is not unique" error. This has been fixed.

CR:757009

CR Number:   757009 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 1829 18 Feb 2014 Fixed 12.0.1 4070 18 Feb 2014 Fixed 11.0.1 3112 18 Feb 2014 Fixed Description When the server executed an ALTER TABLE statement, or loaded the table definition of a table with a unique index (primary key, table/column unique constraint or unique index) it did not derive the unique property to non-unique declared indexes that were defined on a superset of the columns of a unique index. For example: If a table has a primary key on columns (col1, col2) and there is another index on columns (col2, col3, col1) then this other index is unique as well. The optimizer relies very much on this unique property of an index for cardinality estimation. So the server may have used an non-optimal plan if above conditions were true. This has now been fixed.

CR:757144

CR Number:   757144 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Infrastructure Status:   Closed OS:   Generic Original Version:   1.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.0 4869 07 Feb 2014 Fixed Description Under rare circumstances, load calculations on a cloud server could have looped with an error: value outside of range for destination. Restarting the server would then eliminate the error. This has been fixed.

CR:757146

CR Number:   757146 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 1818 13 Feb 2014 Fixed 12.0.1 4069 13 Feb 2014 Fixed 11.0.1 3110 13 Feb 2014 Fixed Description Under rare circumstances, the server could have crash when executing an ALTER MATERIALIZED VIEW IMMEDIATE REFRESH statement. This has been fixed.

CR:757264

CR Number:   757264 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 4068 10 Feb 2014 Fixed Description In timing dependent cases, a mirror or copy node could have crashed while shutting down due to an error detected while applying the transaction log - such as a transaction log mismatch. This crash could have only occurred after the databases were shut down and communications completed. This has been fixed.

CR:757265

CR Number:   757265 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 1822 12 Feb 2014 Fixed 12.0.1 4068 12 Feb 2014 Fixed Description The Outbound Enabler may have crashed on startup while creating an HTTPS up-channel and down-channel at the same time before using them. This has been fixed.

CR:757273

CR Number:   757273 Product Name:   SQL Anywhere Product Component:   OData Server Status:   Closed OS:   Generic Original Version:   16.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1822 10 Feb 2014 Fixed Description Long-form formats like application/json were not supported with the $format query option. This has been corected by adding support for the following long-form constants: application/xml application/atom+xml application/json */*

CR:757274

CR Number:   757274 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 1822 10 Feb 2014 Fixed Description The system procedure sp_parse_json() would have failed to parse escaped character sequences in strings. In particular, it would not have parsed \ (escape double quote), nor any escaped character near the end of the string. For example, this statement would not have handled the \ sequences and would have generated an error: call sp_parse_json( myvar, [{s:this is \quoted text\.}] ); This has been fixed.

CR:757282

CR Number:   757282 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1822 11 Feb 2014 Fixed Description The Outbound Enabler was taking longer than necessary to shut down. This has been fixed by removing unneeded operations and to tune for a faster shutdown response.

CR:757492

CR Number:   757492 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 1825 13 Feb 2014 Fixed 12.0.1 4069 13 Feb 2014 Fixed 11.0.1 3110 13 Feb 2014 Fixed Description When a multibyte character string with a truncated last character was unloaded, the last two bytes of a character may be added to the end of the string as ASCII characters. This has been fixed.

CR:757516

CR Number:   757516 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 1825 12 Feb 2014 Fixed 12.0.1 4069 12 Feb 2014 Fixed Description Calling the ODBC function SQLBulkOperations() with SQL_ADD could have failed to insert rows without returning an error if the number of rows multiplied by the number of columns was more than 65535. This has been fixed.

CR:757529

CR Number:   757529 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 1832 20 Feb 2014 Fixed 12.0.1 4047 20 Feb 2014 Fixed Description A security issue with the Unload utility (dbunload) has been corrected.

CR:757696

CR Number:   757696 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1826 18 Feb 2014 Fixed Description In some cases, an updated row in a table marked as synchronize all would have been uploaded as an UPDATE with a pre and post image, rather than an INSERT, which is what all rows in such a table are expected to be uploaded as. Also, if there was an uncommitted update on a row in that type of table, it wouldnt be uploaded at all. These bugs have been fixed.

CR:757937

CR Number:   757937 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 1827 18 Feb 2014 Fixed 12.0.1 4071 18 Feb 2014 Fixed 11.0.1 3112 18 Feb 2014 Fixed Description Attempting to save the SQL for an event that contained whitespace before the BEGIN keyword would have resulted in a syntax error. This has been fixed.

CR:757959

CR Number:   757959 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 1850 11 Mar 2014 Fixed 12.0.1 4085 11 Mar 2014 Fixed Description Under exceptionally rare circumstances, the server may have returned too many rows from a parallel hash semi-join if the build site is the preserved table. This has been fixed.

CR:758063

CR Number:   758063 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 1838 28 Feb 2014 Fixed 12.0.1 4081 28 Feb 2014 Fixed Description When the system procedure sa_server_messages() was called from services, in such a way that it returned an empty result set, it could have put the server in a state where further concurrent calls to sa_server_messages() could have caused a server crash. This has been fixed.

CR:758073

CR Number:   758073 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 1831 19 Feb 2014 Fixed 12.0.1 4072 19 Feb 2014 Fixed 11.0.1 3113 19 Feb 2014 Fixed Description The Visual Studio 2010 compiler could have crashed when generating Entity Data Models. This has now been fixed.

CR:758327

CR Number:   758327 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1833 21 Feb 2014 Fixed 12.0.0 4075 21 Feb 2014 Fixed Description When the PHP external environment on Windows was used during an HTTP request (with thread-safe PHP), the PHP process may have crashed or behaved incorrectly. This has been fixed.

CR:758332

CR Number:   758332 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 1852 21 Feb 2014 Fixed Description For certain geometries, ST_Buffer may report a ring not closed error. This has been fixed.

CR:758422

CR Number:   758422 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 1858 19 Mar 2014 Fixed 12.0.1 4089 19 Mar 2014 Fixed Description When starting the database server with a minimum multiprogramming level (command line option "-gnl <value>") that was higher than the default maximum, the database server would not have adjusted the maximum setting. The number of threads would never have gone higher than the maximum. This has been fixed. If the minimum (-gnl) value exceeds the maximum value, then the maximum and initial MultiProgrammingLevel settings will be readjusted to this minimum.

CR:758543

CR Number:   758543 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 1865 25 Mar 2014 Fixed 12.0.1 4101 15 Apr 2014 Fixed Description The server could have become deadlocked when attempting to drop a user with a table in-use. This has been fixed.

CR:758564

CR Number:   758564 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 1837 28 Feb 2014 Fixed 12.0.1 4081 28 Feb 2014 Fixed Description LineStrings in Round Earth SRSs could have been represented incorrectly. This could have happened for LineStrings with segments crossing equator from South to North. Additionally, under very rare circumstances, such LineStrings could have caused a stack overflow exception. This has been fixed. In the existing databases, LineStrings that cross equator from South to North and are stored in a Round Earth SRS (for example, 4326) should be reloaded in order to be stored in the correct representation.

CR:758580

CR Number:   758580 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 1952 17 Jun 2014 Fixed 12.0.1 4136 17 Jun 2014 Fixed Description When a reusable plan for a statement in a stored procedure was executed from the plan cache, in certain cases the reused plan failed to obtain schema locks on all of the tables occurring in the statement. As a result, another connection was not blocked from performing concurrent DDL on a table in use by the cached plan. This scenario could have caused data corruption that could lead to a non-recoverable database. This has been fixed.

CR:758811

CR Number:   758811 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 1844 06 Mar 2014 Fixed 12.0.1 4083 06 Mar 2014 Fixed Description In rare, timing dependent cases, if a connection was running a procedure and a DDL operation occurred, the server could have crashed. In order for the crash to have occurred, the procedure needed to have a statement that referenced a view or multiple tables. This has been fixed. In rare, timing dependent cases, if multiple connections were running the same procedure concurrently and a DDL operation occurred, the server could have hung. In order for the hang to have occurred, the procedure needed to have had multiple statements that referenced the same view. This has also been fixed.

CR:758812

CR Number:   758812 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 1838 28 Feb 2014 Fixed 12.0.1 4081 28 Feb 2014 Fixed 11.0.1 3117 28 Feb 2014 Fixed Description The property sheet for a table column would not have allowed changing the columns Compress values or Maintain BLOB indexes for large values settings if the columns type was a domain, even if the domains base type supported these settings. This has been fixed.

CR:758899

CR Number:   758899 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 1839 28 Feb 2014 Fixed 12.0.1 4081 28 Feb 2014 Fixed Description Spatial operations may, in rare cases, have crashed the server. This has been fixed.

CR:758922

CR Number:   758922 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 4877 03 Mar 2014 Fixed Description SQL Anywhere, on-demand edition now supports a new AddCloudSoftwareUpdateFromFile task. The new task adds cloud software to the cloud, given a cloud software update package file local to the Partner server. If your cloud is running in High Availability mode when adding the cloud software, the update package file should be copied to both Partners before running the AddCloudSoftwareUpdateFromFile task."

CR:758927

CR Number:   758927 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 4889 03 Mar 2014 Fixed Description When adding a new host to a SQL Anywhere, on-demand edition SP4 Cloud, if cloud software older than SP4 was specified for the host, it would have failed with an error like: "File or directory /opt/saondemand100/data/staging/SD-z6b9/Bin64/libeay32.dll not found" This has been fixed.

CR:759114

CR Number:   759114 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 1843 05 Mar 2014 Fixed 12.0.1 4083 05 Mar 2014 Fixed Description Attempting to fetch the date 0000-01-00 as either a java.sql.Timestamp or java.sql.Date using the SQL Anywhere JDBC Driver would have resulted in the wrong value being returned and all subsequent timestamp values being incorrect. This date is not representable within Java, hence the value now returned will be 0001-01-01 and all subsequent timestamp values will now be correct. Note that this change is most significant when querying the mv_known_stale_at column from SYS.SYSVIEW since 0000-01-00 represents a materialized view that is either fresh or in an unknown state. The value will now be returned as 0001-01-01 instead.

CR:759129

CR Number:   759129 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 1843 05 Mar 2014 Fixed 12.0.1 4083 05 Mar 2014 Fixed Description If a Java stored procedure was defined such that the number of OUT parameters in the stored procedure definition was not equal to the number of OUT parameters in the Java signature, then the server would have returned an ArrayOutOfBounds exception when the procedure was called. This problem was introduced by the fixes for Engineering case 691193, and has now been fixed.

CR:759139

CR Number:   759139 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 1843 05 Mar 2014 Fixed Description The "custom" source control option -- the one in which a command line is entered to check in / check out / etc. -- was broken. Attempting to enable it resulted in an error message "Interactive SQL could not load the interface library for your source control system." This has now been fixed.

CR:759209

CR Number:   759209 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 1865 25 Mar 2014 Fixed 12.0.1 4092 25 Mar 2014 Fixed Description The server may have loaded too large a value, and NaN/INF values, into DOUBLE, FLOAT and REAL columns by LOAD TABLE and OPENSTRING. This has been fixed. The server will now generate an error for these values.

CR:759243

CR Number:   759243 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1844 05 Mar 2014 Fixed 12.0.1 4083 05 Mar 2014 Fixed Description In some situations, it was possible for an HTTPS synchronization to fail, though no actual stream error code would have been reported. This has been fixed.

CR:759373

CR Number:   759373 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1845 10 Mar 2014 Fixed 12.0.1 4083 10 Mar 2014 Fixed Description In the Views folder, clicking the Last Refresh Time or Known Stale Time column headings to sort the views by one of these columns would have produced incorrect results. This has been fixed.

CR:759431

CR Number:   759431 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 1868 19 Mar 2014 Fixed 12.0.1 4093 19 Mar 2014 Fixed Description The search condition "<expression> IS [ NOT ] ( type-name, ... )" may have incorrectly evaluated to FALSE, or have caused a server crash. This has been fixed.

CR:759461

CR Number:   759461 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1850 11 Mar 2014 Fixed 12.0.1 4085 11 Mar 2014 Fixed Description It was possible for the Relay Server to have incorrectly reported fatal error RSF13011 (Failed allocating shared memory block for client traffic statistic collector of backend server 'XXX' in backend farm 'YYY'). After this fatal error, the Relay Server would no longer have communicated with backend server XXX in backend farm 'YYY' until the Relay Server Host Manager was restarted. While there continue to be legitimate reasons for the RSF13011 error to be reported, the problem that would have led to the incorrect reporting of the RSF13011 error has now been fixed.

CR:759525

CR Number:   759525 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 1859 20 Mar 2014 Fixed Description If a web procedure URL was badly formed, the server could have crashed when the procedure was called. This has been fixed.

CR:759618

CR Number:   759618 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 1853 14 Mar 2014 Fixed 12.0.1 4087 14 Mar 2014 Fixed Description A failed ALTER TABLE statement could have corrupted the database. For corruption to occur, the table being altered must have contained no data, but must have contained some at some point. The error most likely involved was column not found. Assertion failures possible included 201135 (page freed twice), 201503 (Record X not present on page Y), 200106 (attempting to add row twice), 200131 (Invalid page found in index), 106200 (Unable to undo index changes during rollback), 100700 (Unable to find table definition X for record referenced in rollback log), or 101422 (Attempt to write an invalid page). This has been fixed.

CR:759714

CR Number:   759714 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 4909 17 Mar 2014 Fixed Description The "Download" link has been removed from the "Cloud Software" panel for the Cloud. References to the Usage Server have been removed. The following hyperlinks have been removed from the Cloud's "Overview" page: "Activate the cloud", "Refresh activation state", "Send usage information", "Log in to Usage Server". On the Cloud overview page, the "Licensing" properties are now displayed all the time. Previously, they appeared only after the cloud was activated. The "Licensing" section now includes two new links: "Add Licenses" and "Remove Licenses" for managing cloud licenses.

CR:759830

CR Number:   759830 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 1857 18 Mar 2014 Fixed 12.0.1 4089 18 Mar 2014 Fixed 11.0.1 3126 18 Mar 2014 Fixed Description An application using the ADO.Net Manager Provider could have failed with the error Unable to load DLL dbdata16.dll when calling SAConnectionStringBuilder.ToString. Ths has now been corrected.

CR:760022

CR Number:   760022 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1857 19 Mar 2014 Fixed 12.0.1 4089 19 Mar 2014 Fixed Description If auditing was on and the database contained events that were executed, the output from dbtran -g could have contained lines like the following: --CONNECT-1025-0000952657-failure-2014-03-18 09:36 indicating a possible connection failure. This has been fixed. These lines do not indicate a connection failure. They can be safely ignored and will not show up in transaction logs created with fixed servers.

CR:760057

CR Number:   760057 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 1872 03 Apr 2014 Fixed Description Some LDAP servers allowed a zero length password to unexpectedly allow a user to successfully authenticate. This has been corrected.

CR:760128

CR Number:   760128 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 1857 18 Mar 2014 Fixed Description In certain cases, a user that had the appropriate system privilege to create a procedure, function, view, trigger, or sequence, but did not have the appropriate privilege to alter it, was still able to alter the object. This has been fixed.

CR:760144

CR Number:   760144 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 1858 19 Mar 2014 Fixed 12.0.1 4089 19 Mar 2014 Fixed Description When performing an absolute or relative fetch, the SELECT list expressions for rows that are not returned were evaluated. These were not strictly needed and if they contained expensive operations such as UDFs this could have been slower than necessary. If the Row_counts option was TRUE and the query optimizer could not accurately estimate the number of rows to be returned, the server simulates an ABSOLUTE fetch to position 1000000000 in order to count the rows. Before this change, all select list expressions were evaluated for these rows. These unneeded evaluations are now skipped. A change in behaviour is that side effects and errors are no longer observed in some cases. There may still be more executions than client fetches due to factors such as prefetching.

CR:760153

CR Number:   760153 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1979 14 Jul 2014 Fixed Description Creating a Deployment Wizard installation which included the Interactive SQL utility, the MobiLink Profiler or the Console utility, but not Sybase Central, would have failed to include JComponents1600.jar. This has been fixed.

CR:760165

CR Number:   760165 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 1857 19 Mar 2014 Fixed Description The SetBytes methods of the ResultSet and Table classes would have truncated the byte array argument if the array was larger than 32 KB. This has been fixed. The same incorrect behaviour would also have occurred with the SetString method of ResultSet and Table, and with the SetParameterBytes method of PreparedStatement. These cases have also been fixed.

CR:760339

CR Number:   760339 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1859 21 Mar 2014 Fixed Description A number of issues related to the "Save as ODBC Data Source" dialog when running 64-bit software on 64-bit Windows, have been corrected: -- The dialog appeared to give the option of creating both 32 and 64-bit versions of a user data source. This option applies only to creating system DSNs, and is now disabled. -- When trying to create both a 32 and 64 bit system DSN, but the 32-bit could not be created, the error message was irrelevant. This has been fixed; the error message now says why the data source could not be created. -- Data sources could be created with non-canonical forms of the connection parameter names. This would have prevented the Data Source utility (dbdsn) from listing the data source completely. This has been fixed. -- Creating a system data source could have caused up to three elevation prompts if a 32-bit data source was also created. Now, there is at most one prompt. -- The dialog allowed creation of a user data source, even if there was already a system data source of the same name. Similarly, it allowed creation of a system data source with the same name as an existing user data source. This was very poor practice and could have lead to unexpected results if a user didn't realize that user data sources take precedence, and so the practice is now simply disallowed.

CR:760362

CR Number:   760362 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1846 24 Mar 2014 Fixed 12.0.1 4090 24 Mar 2014 Fixed Description If the SQL Anywhere ODBC driver, or the Sybase IQ ODBC driver version 15.x or later, was used to connect to a database with the database option 'quoted_identifier' set to 'off', or to a database on a 9.0.2 or earlier server, the ODBC driver would have failed to establish some properties of the DBMS. When quoted_identifier was 'off': 1. For a Sybase IQ DBMS, the driver would have reported [SQL Anywhere] in messages rather than [Sybase IQ]. 2. For a Sybase IQ DBMS, the driver would have reported "SQL Anywhere" instead of "Sybase IQ" for SQLGetInfo(SQL_DBMS_NAME). 3. For a Sybase IQ DBMS, the driver would not have used the "SYS.SYSIQVINDEX" table for SQLStatistics, but would have used "SYS.SYSINDEX" instead. 4. For a Sybase IQ DBMS, the ODBC driver will report the wrong server version number (e.g., 12.0.1 rather than 15.4) for SQLGetInfo(SQL_DBMS_VER). In addition, when quoted_identifier was 'off' or the server was version 9.0.2 or earlier: 5. The ODBC driver would not have known the correct CHARSET setting. 6. The ODBC driver may have had the wrong setting for the case sensitivity of the database and may have affected SQLGetTypeInfo and other schema query functions. 7. The ODBC driver may have had the wrong setting for the odbc_distinguish_char_and_varchar option. 8. The ODBC driver may have had the wrong setting for the odbc_describe_binary_as_varbinary option. Other than these issues, there are no other known side-effects. This problem has been fixed.

CR:760526

CR Number:   760526 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 1865 26 Mar 2014 Fixed 12.0.1 4092 26 Mar 2014 Fixed Description Under rare circumstances, the server could have crashed when checking whether a stored procedure could be in-lined. This has been fixed.

CR:760644

CR Number:   760644 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 1868 28 Mar 2014 Fixed Description When using the OData Producer as a servlet in a webserver, the paths were relative to a current directory, which was unpredictable by the servlet. This has been fixed. The OData Producer will now search the servlets context first, then the current directory. For security reasons, the producer configuration and model files should be located in the WEB-INF/ directory (or equivalent). This context may now include .WAR files. For OData Producers deployed using the OData Server utility (dbosrv16), paths are relative to the current directory when the server was launched.

CR:760873

CR Number:   760873 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 1868 31 Mar 2014 Fixed 12.0.1 4093 31 Mar 2014 Fixed 11.0.1 3130 31 Mar 2014 Fixed Description Named parameter lookup performed poorly. The GetInputParameterValues method has now been rewritten to improve the speed of named parameter lookup.

CR:760874

CR Number:   760874 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 1867 27 Mar 2014 Fixed 12.0.1 4093 27 Mar 2014 Fixed Description If the system procedure sa_server_option() was used to change the 'IdleTimeout' or 'LivenessTimeout' option values to less than 0 or more than 32767, connections may have been incorrectly dropped. This has been corrected so that an error is now given if a value less than 0 or more than 32767 is specified for these options. In both cases, a value of 0 means there is no timeout.

CR:761039

CR Number:   761039 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1882 14 Apr 2014 Fixed 12.0.1 4100 14 Apr 2014 Fixed 11.0.1 3146 02 May 2014 Fixed Description Under exceptionally rare circumstances, the server may have crashed when executing UPDATE or DELETE statements that bypass the optimizer if the number of columns of the table was evenly divisible by 32, and all the column values were needed in the statement and an index had been chosen. This has been fixed.

CR:761107

CR Number:   761107 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 1878 07 Apr 2014 Fixed 12.0.1 4097 07 Apr 2014 Fixed Description The server may have returned an incorrect result set if an OrderedGroupBy strategy used an index and the GroupBy query block contained an outer reference after the query rewrite. This has been fixed.

CR:761197

CR Number:   761197 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 1941 06 Jun 2014 Fixed 12.0.1 4121 06 Jun 2014 Fixed 11.0.1 3162 06 Jun 2014 Fixed Description The database server may have crashed if any one dbspace file reached the maximum size of 0x10000000 pages. If a single dbspace needs more space and cannot be split into multiple dbspaces, a larger page size is required. For example, the dbspace size limit for a 2K page size is 512GB while a 4K page size may create dbspaces up to 1TB in size. When a single file gets too big, the server will now detect this situation, version 11 and 12 servers will display a failed assertion message and shut down. Version 16 and later servers will display a failed assertion message and shut down only the affected database.

CR:761217

CR Number:   761217 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 1872 02 Apr 2014 Fixed Description The OData Producer did not properly parse odata batch request boundaries from the Content-Type header field. In particular, a content type of the form: Content-Type: multipart/mixed; boundary=batch_e30b82d3-3d8a-430d-b66f-9fec1df8ae19; charset=utf-8 would have resulted in a 404 error. This has been fixed.

CR:761500

CR Number:   761500 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 1881 10 Apr 2014 Fixed 12.0.1 4098 10 Apr 2014 Fixed Description The system procedure sa_recompile_views may have returned an unexpected error if it was executed outside the reload.sql script with non-standard settings for the database options quoted_identifiers and ansi_close_cursors_on_rollback. This has been fixed.

CR:761569

CR Number:   761569 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) 12.0.1 4201 05 Jan 2015 Fixed Description Version 12 UltraLite now supports 64-bit architectures for iOS (arm64 and x86_64).

CR:761652

CR Number:   761652 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 1882 14 Apr 2014 Fixed 12.0.1 4099 14 Apr 2014 Fixed Description In rare cases the server may have returned SQLCODE -150 or failed assertion 106104 when optimizing an aggregation query that qualified for optimizer bypass. This could have occurred when the aggregate function was within the left-hand side of a dot-notation function expression (primarily occurring within spatial queries), such as ST_Geometry::ST_EnvelopeAggr(column).ST_AsWKB(). This has been fixed.

CR:761748

CR Number:   761748 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 1886 15 Apr 2014 Fixed 12.0.1 4101 15 Apr 2014 Fixed Description If the transaction log was renamed while the MobiLink client (dbmlsync) was performing a sync operation, and no transactions were in progress, the SQL Anywhere server would have generated the new log in a way that would have caused dbmlsync to send downloaded rows for upload. This problem has been fixed

CR:761750

CR Number:   761750 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 1880 10 Apr 2014 Fixed Description User who have permission to access stored procedures or database functions through roles, may not have access to the corresponding service operations in OData. The affected operations would not have appeared in the metadata, and the user would have received 404 errors trying to invoke them. This has been fixed. As a work around, database administrators should directly grant execute permission on given stored procedures or functions to the affected users.

CR:761751

CR Number:   761751 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 1824 14 Apr 2014 Fixed 12.0.1 4086 14 Apr 2014 Fixed Description The OpenSSL vulnerability known as Heartbleed impacted some components of SQL Anywhere software as follows: - SQL Anywhere Server when using TLS (Transport Layer Security) communications and/or HTTPS web services, though only to the networks that can access the server. Calling external web services over HTTPS from the database server were also affected. - MobiLink Server when using TLS and/or HTTPS communications, though only to the networks that can access the MobiLink server. - Relay Server Outbound Enabler Affected Versions (note that all platforms were impacted by the vulnerability): - SQL Anywhere 12.0.1 builds 3994-4098 - SQL Anywhere 16.0 builds 1690-1880 This vulnerability has been resolved by replacing the OpenSSL libraries with corrected versions. Once this SP has been applied, regenerate any certificates that were being used, and then change any passwords/keys associated with SQLA web service calls or TLS authentication.

CR:761933

CR Number:   761933 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 1882 11 Apr 2014 Fixed Description In rare cases, the server may have crashed while parsing an incorrect IN search condition. This has been fixed.

CR:761990

CR Number:   761990 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   16.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1904 06 May 2014 Fixed Description If the cardinality estimate of the left hand side of a JOIN EXISTS was less than 1, a NestedLoopsSemijoin (JNLS) would always have be chosen based on cost. This could have led to poor performance in some cases. A more robust optimization has now been implemented.

CR:762038

CR Number:   762038 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1885 14 Apr 2014 Fixed 12.0.1 4100 14 Apr 2014 Fixed Description When reviewing recommendations from a tracing session, and the database had been shut down, a java.lang.IndexOutOfBoundsException could have occurred. This has been fixed.

CR:762046

CR Number:   762046 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1885 14 Apr 2014 Fixed 12.0.1 4100 14 Apr 2014 Fixed Description The SQL Anywhere Plug-in tooltip for the Connect window had its text truncated. This has been fixed.

CR:762171

CR Number:   762171 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 1886 16 Apr 2014 Fixed Description When hovering between column headings in the right pane, the cursor may not have been drawn as a resize cursor. This has been fixed.

CR:762254

CR Number:   762254 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 4102 21 Apr 2014 Fixed Description If an application made a standard connection to the server, and a second connection through the dbtools interface (for example, by calling the DBUnload function), and both connections used TLS with FIPS, the application could have crashed. This has been fixed.

CR:762317

CR Number:   762317 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1910 21 Apr 2014 Fixed 12.0.1 4110 29 Apr 2014 Fixed Description If a computer supported IPv6, but had IPv4 disabled, the database server would have failed to start if TCP/IP or HTTP were being used. In addition, a SQL Anywhere client application running on such a machine could have failed to find servers using TCP/IP. These problems have now been fixed.

CR:762531

CR Number:   762531 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 1892 22 Apr 2014 Fixed Description The Create Procedure wizard would have crashed when creating a procedure for a Java external environment. This has been fixed.