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

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

CR:768186

CR Number:   768186 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 2006 23 Sep 2014 Fixed 12.0.1 4163 23 Sep 2014 Fixed Description The server may have returned poor selectivity estimates for equi-sarg searches on a floating-point type column. Some changes have been made to improve the accuracy of these estimations.

CR:768311

CR Number:   768311 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 2003 20 Aug 2014 Fixed 12.0.1 4156 07 Aug 2014 Fixed Description Under exceptionally rare circumstances, the server may have crashed when running the system function CONNECTION_PROPERTY() for a connection other than the one making the request, if the queried property was a connection option but not a connection statistic. This has been fixed.

CR:768346

CR Number:   768346 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 Description The server wopuld have incorrectly returned the error "Invalid recursion" for a query that contained proxy tables and the UNNEST construct. This has been fixed.

CR:768379

CR Number:   768379 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 1994 13 Aug 2014 Fixed 12.0.1 4150 13 Aug 2014 Fixed Description The MobiLink server with integrated Outbound Enabler could have crashed. This has been fixed.

CR:768466

CR Number:   768466 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 1990 31 Jul 2014 Fixed 12.0.1 4146 31 Jul 2014 Fixed Description In rare cases, the server would have appeared to not have processed requests for a duration of 30 seconds. For this to have occurred. the auto multiprogramming level adjustment had to have been active and there had to have been many client side connections that were blocked. This has now been fixed.

CR:768513

CR Number:   768513 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 2000 20 Aug 2014 Fixed Description When defining MobiLink server Command Lines, two of the available options are sl java and sl dnet. These are used to pass startup parameters to the Java VM or .NET CLR used to process Java or .NET scripts. The value entered for these options in the MobiLink Server Command Line Properties dialog were automatically enclosed in quotes when generating a MobiLink server command line (eg sl java -c c:\myjava ). This was incorrect, the MobiLink server expects these option values to be enclosed in brackets or braces. This has been fixed so that if the value entered is already surrounded by brackets or braces, nothing will be added to it, otherwise the value will be enclosed in brackets. (ex sl java( -c c:\myjava)

CR:768514

CR Number:   768514 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1990 05 Aug 2014 Fixed 12.0.1 4146 05 Aug 2014 Fixed Description On some RedHat distributions, if the SQL Anywhere Monitor was configured as a service that started automatically when the computer was rebooted, it may have sporadically failed to start. This has been fixed.

CR:768652

CR Number:   768652 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1993 12 Aug 2014 Fixed Description Sybase Central would have failed assertions, or behaved incorrectly, when running on a machine with a Turkish locale, regardless of the databases collation or the server machines locale. This has been fixed. Workaround Description  1. create a batch file for Sybase Central, using command: scjview -batch 2. open file "scjview.bat" and insert " -Duser.language=en -Duser.country=US" after "C:\Program Files\SQL Anywhere 16\bin64\jre170\bin\java.exe" 3. start Sybase Central by running modified batch file "scjview.bat" === scjview.bat (Work-Around) === setlocal set path=C:\Program Files\SQL Anywhere 16\bin64;;%path% set classpath=C:\Program Files\SQL Anywhere 16\java\sybasecentral1600.jar;C:\Program Files\SQL Anywhere 16\java\jsyblib1600.jar;C:\Program Files\SQL Anywhere 16\java\SCEditor1600.jar "C:\Program Files\SQL Anywhere 16\bin64\jre170\bin\java.exe" -Duser.language=en -Duser.country=US -Duser.variant=US -Xmx536m -Dsybase.native.executable="C:\Program Files\SQL Anywhere 16\bin64\scjview.exe" -Dsun.java2d.noddraw=true -Dsun.java2d.d3d=false -ea com.sybase.central.viewer.SybaseCentral -installdir="C:\Program Files\SQL Anywhere 16\bin64" endlocal

CR:768684

CR Number:   768684 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 1992 06 Aug 2014 Fixed 12.0.1 4148 06 Aug 2014 Fixed Description The server may have returned the error 'Invalid expression' or crashed, if common table expressions were used in statements with proxy tables. This has now been fixed.

CR:768717

CR Number:   768717 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 1993 06 Aug 2014 Fixed 12.0.1 4142 06 Aug 2014 Fixed Description The ADO.NET provider now supports Entity Framework 6. A new dll (iAnywhere.Data.SQLAnywhere.EF6.dll) has been added to %SQLANY%\Assembly\V4.5 directory. SetupVSPackage still registers the v4.5 dll. To use the new Entity Framework 6 provider, register it in app.config or web.config. For example: <?xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" /> </configSections> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" /> </startup> <connectionStrings> <add name="Entities" connectionString="metadata=res://*/Model1.csdl|res://*/Model1.ssdl|res://*/Model1.msl;provider=iAnywhere.Data.SQLAnywhere;provider connection string='datasourcename="SQL Anywhere 12 Demo"'" providerName="System.Data.EntityClient" /> </connectionStrings> <system.data> <DbProviderFactories> <clear /> <add name="SQL Anywhere 12 Data Provider" invariant="iAnywhere.Data.SQLAnywhere" description=".Net Framework Data Provider for SQL Anywhere 12" type="iAnywhere.Data.SQLAnywhere.SAFactory, iAnywhere.Data.SQLAnywhere.EF6, Version=12.0.1.41474, Culture=neutral, PublicKeyToken=f222fc4333e0d400" /> </DbProviderFactories> </system.data> <entityFramework> <providers> <provider invariantName="iAnywhere.Data.SQLAnywhere" type="iAnywhere.Data.SQLAnywhere.SAProviderServices, iAnywhere.Data.SQLAnywhere.EF6, Version=12.0.1.41474, Culture=neutral, PublicKeyToken=f222fc4333e0d400" /> </providers> </entityFramework> </configuration>

CR:768718

CR Number:   768718 Product Name:   SQL Anywhere Product Component:   JDBC Client Library 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 When using the JDBC driver in a multithreaded Java application on Windows, a crash may have occurred in the heap management run-time code (HeapFree). This problem also appeared when using the MobiLink Profiler, since it uses the JDBC driver. This problem has been fixed.

CR:768791

CR Number:   768791 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2013 17 Sep 2014 Fixed 12.0.1 4162 17 Sep 2014 Fixed Description The server could have hung attempting to schedule a recurring event. This has been fixed.

CR:768875

CR Number:   768875 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 1993 11 Aug 2014 Fixed 12.0.1 4148 11 Aug 2014 Fixed 11.0.1 3183 11 Aug 2014 Fixed Description Attempting to create a maintenance plan could have failed if the Allow_nulls_by_default database option was set to Off the first time the Maintenance Plans folder was selected for that database in Sybase Central. This has been fixed.

CR:768882

CR Number:   768882 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 2003 26 Aug 2014 Fixed 12.0.1 4156 26 Aug 2014 Fixed Description Under rare circumstances, executing a procedure defined with SQL SECURITY INVOKER could have cashed a server crash. This has been fixed.

CR:768926

CR Number:   768926 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 2000 05 Sep 2014 Fixed Description The installers default feature selection on Windows x64, combined with a limitation of InstallShield, resulted in the 32-bit OLEDB driver not being registered as a COM server. This has been fixed. Workaround Description  You have to select (install) the 32-bit administration tools to cause the OLE DB provider to be registered.

CR:769059

CR Number:   769059 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 2000 13 Aug 2014 Fixed 12.0.1 4155 13 Aug 2014 Fixed Description Wide INSERT statements (i.e., prepared insert statements which insert more than one row at a time) require that each host variable/parameter appear exactly once within VALUES clause and not be nested within an expression. In some cases, a repeat host variable name would not have been detected and the resulting inserted row could have contained an incorrect value within one of the columns. This has now been fixed. Incorrect wide inserts will now return SQL code -155 (Invalid host variable).

CR:769065

CR Number:   769065 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 1994 13 Aug 2014 Fixed Description The message that reports an update count would have reported the wrong action (INSERT, UPDATE, DELETE or MERGE) if a number of statements were executed at once, and were not separated by a command delimiter. This has been fixed.

CR:769156

CR Number:   769156 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2007 09 Sep 2014 Fixed 12.0.1 4157 09 Sep 2014 Fixed Description Given a simple stored procedure such as the following: create procedure sp_test( in @a integer, in @b integer ) begin select @a + @b as c; end Binding two host variables and executing SELECT * FROM sp_test(?, ?)" just after starting the database server, then the error "Not enough values for host variables" might have resulted. Subsequent execution attempts would have succeeded. A similar problem would have occurred when "SELECT * FROM sp_test(?, ?)" was executed immediately after (dropping and then) creating the stored procedure. This has now been fixed.

CR:769159

CR Number:   769159 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 2000 20 Aug 2014 Fixed 12.0.1 4155 20 Aug 2014 Fixed Description When attempting to connect to a secure SMTP server using the system procedure xp_startsmtp(), the connection would not have timed out. This has been fixed.

CR:769347

CR Number:   769347 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 2017 24 Sep 2014 Fixed 12.0.1 4165 24 Sep 2014 Fixed Description The UPDATE and DELETE statements do not support ordinal column numbers in the ORDER BY clause. DELETE statements that bypass the optimizer did not return an error if ordinal column numbers were used in the ORDER BY. This has been fixed. For UPDATE and DELETE statements the SQL reference correctly documents: "You cannot use ordinal column numbers in the ORDER BY clause." But for DELETE statements the syntax must be changed from [ ORDER BY { expression | integer } [ ASC | DESC ], ... ] to [ ORDER BY expression [ ASC | DESC ] , ...]

CR:769356

CR Number:   769356 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 1698 22 Sep 2014 Fixed 12.0.1 4163 22 Sep 2014 Fixed Description Under exceptionally rare circumstances, the server may have crashed during concurrent execution of a stored procedure that contained a LOAD TABLE statement. This has been fixed.

CR:769394

CR Number:   769394 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 2007 11 Sep 2014 Fixed 12.0.1 4157 09 Sep 2014 Fixed Description Using UltraLite on iOS 8 beta software resulted in synchronization errors with HTTPS. This has been fixed

CR:769501

CR Number:   769501 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 2017 24 Sep 2014 Fixed 12.0.1 4165 24 Sep 2014 Fixed Description Query plans involving parallel hash joins running in memory-constrained environments may have failed to return all of the rows from the join. These query plans may also be used by internal operators, such as those that do table validation and foreign key building, causing these statements to also fail. This has now been fixed. The problem can avoided by disabling parallel query execution (set option PUBLIC.max_query_tasks=1), and can be made less likely by increasing the amount of memory available to the server.

CR:769515

CR Number:   769515 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 2004 22 Aug 2014 Fixed 12.0.1 4156 22 Aug 2014 Fixed Description If the system procedure sa_validate() was called with a table or materialized view name only, then only one of the possibly several owner.name objects was validated. For example, given two tables named "Products" as follows: CREATE TABLE FarmEquipment.Products(...); CREATE TABLE HighwayEquipment.Products(...); the following statement would only have validated one of them at random: SELECT * FROM sa_validate( 'Products' ); Even if the user execting the SELECT was the owner of a table called "Products", it may not have been the table that is validated. In other words, the statement above was not equivalent to: VALIDATE TABLE Products; The documentation states that all tables/materialized views matching the specified object name are validated. This problem has been fixed. The work-around is to specify the table/materialized view owner (the second argument).

CR:769615

CR Number:   769615 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2002 25 Aug 2014 Fixed Description Prefetch performance may have been slightly lower than it should have been. This has been fixed so that prefetch performance is better in some cases, depending on the operating system and the data being fetched.

CR:769672

CR Number:   769672 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2015 19 Sep 2014 Fixed Description The MobiLink server log files created on Unix systems did not give read permission to anyone except for the user who has created the files. This has not been corrected. Now the MobiLink server log files will have read permission set for the group and other users as well. Note, this change will apply to dbremote and dbmlsync logs as well.

CR:769689

CR Number:   769689 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 2003 04 Sep 2014 Fixed Description Queries with predicates of the form: "not exists(subquery)" could have had a sub-optimal execution plan. This has been fixed. The conditions for which this could happen must include: (1) (subquery) was correlated with the main query block (2) (subquery) has a very small size comparing to the table[s] referenced by the correlations

CR:769879

CR Number:   769879 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 2005 05 Sep 2014 Fixed Description Previously, DBISQL did not commit when disconnecting from a SAP HANA database even if its "Commit on exit or disconnect" option was selected. This has been fixed.

CR:770143

CR Number:   770143 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 1994 05 Sep 2014 Fixed 12.0.1 4150 05 Sep 2014 Fixed Description The version of OpenSSL now used by the server (as well as all SQL Anywhere products) is 1.0.1i.

CR:770200

CR Number:   770200 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 2011 08 Sep 2014 Fixed 12.0.1 4160 08 Sep 2014 Fixed Description The unused Batik JAR file JS.JAR has been removed from the list of JAR files that the Interactive SQL utility searches for on startup.

CR:770324

CR Number:   770324 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 2012 09 Sep 2014 Fixed Description The Broadcast Repeater utility (dbns16) did not start. This problem has been fixed.

CR:770430

CR Number:   770430 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 2018 26 Sep 2014 Fixed 12.0.1 4166 26 Sep 2014 Fixed Description A server thread can go into an infinite loop attempting to update an index, eventually resulting in a server hang. The index in question is not corrupt, the server was just misinterpreting an index key. The is fixed so that the key is now interpreted correctly.

CR:770488

CR Number:   770488 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2023 02 Oct 2014 Fixed 12.0.1 4178 05 Jan 2015 Fixed Description UltraLite would have failed to sync using HTTPS on iOS 8. This has now been fixed.

CR:770496

CR Number:   770496 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 2015 18 Sep 2014 Fixed 12.0.1 4163 18 Sep 2014 Fixed Description Under exceptionally rare circumstances, the Unload utility (dbunload) would have returned the error "Primary key for table 'sa_unload_stage2' is not unique". For this to have occurred, the unloaded database must have contained foreign keys with very high ids, and the constraint name of the foreign key must have been renamed. This has been fixed.

CR:770500

CR Number:   770500 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 2013 15 Sep 2014 Fixed 12.0.1 4061 15 Sep 2014 Fixed Description Under exceptionally rare circumstances, the server may have crashed when executing the function CONNECTION_PROPERTY() for a connection other than the own executors connection, if the queried property was an connection option, but not a connection statistic. This has been fixed.

CR:770510

CR Number:   770510 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 2017 24 Sep 2014 Fixed 12.0.1 4165 24 Sep 2014 Fixed Description Under rare circumstances, the server could have crashed executing query plans involving group-by operators above parallel scans when operating in memory-constrained environments. This has been fixed. The problem can be avoided by disabling parallel query execution (set option PUBLIC.max_query_tasks=1), or made less likely by increasing the amount of memory available to the server.

CR:770576

CR Number:   770576 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 2013 15 Sep 2014 Fixed 12.0.1 4161 15 Sep 2014 Fixed Description On Red Hat Enterprise Linux 7, the Interactive SQL utility could not check for updates, nor could they open online help if the computer it was running on required a network proxy to reach the internet. This has been fixed so that on non-Windows platform, the software will use the proxy information in the http_proxy environment variable, if set. Note, this problem also affected Sybase Central and the Console utility, which are fixed as well.

CR:770593

CR Number:   770593 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2021 15 Sep 2014 Fixed 12.0.1 4170 15 Sep 2014 Fixed Description When installing the SQL Anywhere Monitor on a non-Windows platform, if the DISPLAY variable was not set the install would have hung at the end trying to open a browser. This has been corrected by no longer launching a browser in this case.

CR:770597

CR Number:   770597 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 2013 23 Sep 2014 Fixed 12.0.1 4163 23 Sep 2014 Fixed Description The server may have crashed while updating a histogram. This has been fixed.

CR:770747

CR Number:   770747 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 2014 16 Sep 2014 Fixed 12.0.1 4162 16 Sep 2014 Fixed Description The Interactive SQL utility (dbisql) could have consumed more disk space than was required under certain circumstances. This has now been corrected.

CR:770760

CR Number:   770760 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 2014 18 Sep 2014 Fixed 12.0.1 4162 18 Sep 2014 Fixed Description Visual Studio 2012/2013 would have failed to generate a Entity Framework 6 data model using a SQL Anywhere database. This has been corrected. The steps for generating Entity Framework 6 data models (Entity Framework 6 Tools for Visual Studio 2012 & 2013 should be installed): - Run SetupVSPackage.exe with /v 6 option to register the Entity Framework 6 Provider. - Install Entity Framework NuGet Package for the Visual Studio project. - Modify app.config file to add the Entity Framework 6 provider. Heres an example: <providers> <provider invariantName="iAnywhere.Data.SQLAnywhere" type="iAnywhere.Data.SQLAnywhere.SAProviderServices, iAnywhere.Data.SQLAnywhere.EF6, Version=16.0.0.20144, Culture=neutral, PublicKeyToken=f222fc4333e0d400" /> - Build the Visual Studio project. - Run Entity Data Model Wizard.

CR:770843

CR Number:   770843 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2015 19 Sep 2014 Fixed 12.0.1 4163 19 Sep 2014 Fixed Description when comparing databases, SQL Central would have appeared to hang if the database contained a large procedure definition. This has been fixed.

CR:770940

CR Number:   770940 Product Name:   SQL Anywhere Product Component:   OData Server Status:   Closed OS:   Generic Original Version:   16.5 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2015 18 Sep 2014 Fixed Description When an entity modification request violates a check constraint, the OData producer responded with an internal server error like: <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> <code>30000</code> <message xml:lang="en-US">An unexpected error occurred in the producer. Contact the server administrator for more details.</message> </error> This has been fixed. Check constraints will now return either 30144, 30145 or 30146 errors, similar to unique constraint violations, depending on the type of request (INSERT, UPDATE or DELETE).

CR:770952

CR Number:   770952 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2015 19 Sep 2014 Fixed 12.0.1 4163 19 Sep 2014 Fixed Description The following issues related to the Database Documentation wizard have been fixed: On Windows systems: Sybase Central could have become unresponsive for about a minute when viewing the generated documentation, and the directory was specified from the root of the drive but did not include the drive letter. On non-Windows systems: Generating the documentation to a directory with a space in its name, and then attempting to open the documentation would have failed.

CR:770956

CR Number:   770956 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 2015 19 Sep 2014 Fixed 12.0.1 4163 19 Sep 2014 Fixed Description A query with WITH RECURSIVE and FOR XML/JSON clauses could have returned an error when used in a stored procedure definition. This has been fixed. Note, affected procedures will need to be recreated with the fixed version of the server.

CR:770967

CR Number:   770967 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 2016 19 Sep 2014 Fixed 12.0.1 4163 19 Sep 2014 Fixed Description The following issues have been fixed: If a post login procedure did not return a result set, the Interactive SQL utility would have crashed. Also, a race condition could have caused the window containing the post login messages to appear on-screen at the same time as the "Connecting to database" status window. When this occurred, neither window could have been closed.

CR:771044

CR Number:   771044 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 2017 24 Sep 2014 Fixed 12.0.1 4165 24 Sep 2014 Fixed Description The server may have incorrectly returned the error: 'Function or column reference to '<user-name>' in the ORDER BY clause is invalid', if a select statement used a user-defined function with an owner name in the ORDER BY clause; e.g. ORDER BY <user-name>.<function-name(...). This has been fixed.

CR:771105

CR Number:   771105 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 2021 03 Oct 2014 Fixed 12.0.1 4170 03 Oct 2014 Fixed Description The global variable @@error could have been set incorrectly for the first error encountered in a stored procedure or batch. This has been fixed.

CR:771281

CR Number:   771281 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 2025 20 Oct 2014 Fixed 12.0.1 4174 20 Oct 2014 Fixed Description The server may have appeared to hang while creating a histogram on a NUMERIC column that had an index. This has been fixed.

CR:771288

CR Number:   771288 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 2017 24 Sep 2014 Fixed 12.0.1 2017 25 Sep 2014 Fixed Description When specifying a certificate for use in a secure web service call, the call could have failed (with a TLS handshake error) if multiple certificates were specified using certificate=. For example, this could have happened if using certificate=xp_read_file( certificate_file ) and the file contained more than one certificate. This has been fixed.

CR:771300

CR Number:   771300 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 2017 25 Sep 2014 Fixed Description Synchronizations over HTTP could have failed if the command line option wn was greater than one. This has been fixed.

CR:771364

CR Number:   771364 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 2018 25 Sep 2014 Fixed 12.0.1 4166 25 Sep 2014 Fixed Description When searching in SQL Central if the server was shut down, or the connection to the database was dropped from another application, then SQL Central would have shown multiple error dialogs, each of which needed to be closed before SQL Central could be used again. This has been fixed.

CR:771379

CR Number:   771379 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 2018 25 Sep 2014 Fixed 12.0.1 4166 25 Sep 2014 Fixed Description The web server port was not displayed in the Overview tab. This has been fixed

CR:771429

CR Number:   771429 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 2018 26 Sep 2014 Fixed 12.0.1 4166 26 Sep 2014 Fixed Description The Interactive SQL utility would have crashed when using the Import Wizard to import a shape file, and that shape file had an associated .DBF file which contained a DATE, TIME, or TIMESTAMP column. This has been fixed.

CR:771431

CR Number:   771431 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 2020 01 Oct 2014 Fixed 12.0.1 4169 01 Oct 2014 Fixed Description In specific circumstances, if there were concurrent connections executing the same procedure it was possible for the server to crash. The conditions were rare and timing dependent, and have now been fixed.

CR:771441

CR Number:   771441 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 2018 29 Sep 2014 Fixed 12.0.1 4166 29 Sep 2014 Fixed Description Creating a JSON service that called a procedure which set the CharsetConversion option would have caused the server to crash. This has been fixed.

CR:771444

CR Number:   771444 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 2018 29 Sep 2014 Failed 12.0.1 4166 29 Sep 2014 Fixed Description JSON services would have returned an empty document if an SQL error occurred. This has been fixed so that an object containing one row with two keys, status: error, and message: <text of the SQL error message>, is now returned.

CR:771541

CR Number:   771541 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2019 29 Sep 2014 Fixed Description Attempting to have the MobiLink server bind a virtual IP address while specifying the host stream parameter, would have resulted in error -10259 Network address '<host>' is not local on some platforms. This has been corrected so the server will print warning 10126 '<host>' might not be a local address, instead.

CR:771542

CR Number:   771542 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 2020 30 Sep 2014 Fixed 12.0.1 4168 30 Sep 2014 Fixed Description Executing CREATE SUBSCRIPTION or DROP SUBSCRIPTION statements could have failed if they used a subscription-value. This has been fixed.

CR:771618

CR Number:   771618 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 2020 30 Sep 2014 Fixed Description The server may have crashed when using ARRAY or ROW type values in statements that needed to convert them to strings. This has been fixed. Note, the problem does not happen in DDL and DML statements.

CR:771622

CR Number:   771622 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 2020 23 Oct 2014 Fixed 12.0.1 4179 23 Oct 2014 Fixed Description The COUNT_BIG() aggregate function is intended to be used in cases where the number of rows is larger than can be represented in an INTEGER. When initially implemented for SQL-level compatibility, COUNT_BIG() was an alias for COUNT(), returning an INTEGER and restricted to the same supported input cardinalities. COUNT_BIG() has been corrected to now return a BIGINT. When executing a parallel query plan with a COUNT_BIG() over a table larger than representable in an INTEGER (approximately 2 billion rows), an error such as Value SUM() out of range for destination was returned. This is now corrected. The SUM(x) aggregate function now returns BIGINT if x is of type BIGINT. When using COUNT_BIG() in sliding window queries, the window was re-scanned for each row of the window instead of decrementing the count when rows were removed. This has been corrected. The graphical plan for window operators now displays the PARTITION BY, ORDER BY, and window functions computed by the operator. It also shows whether rows are removed from the functions by inverting the aggregate (e.g., SUM, COUNT, COUNT_BIG) or by rescanning the window (e.g., MIN,MAX). Rescanning the buffer is slower and proportional to the square of the maximum buffer size. The COUNT_BIG aggregate is now supported for incremental maintenance materialized views. When printing COUNT_BIG with no argument, it is now printed as COUNT_BIG(*). If COUNT_BIG() was used in a subquery that was flattened by semantic transformations, it was possible for the function to improperly return NULL instead of 0 (the classic count bug). This has now been corrected.

CR:771690

CR Number:   771690 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 2020 01 Oct 2014 Fixed 12.0.1 4169 01 Oct 2014 Fixed Description In very rare cases, the server may have crashed while executing the system procedure xp_cmdshell() if the client connection calling the procedure was cancelled. This has been fixed.

CR:771708

CR Number:   771708 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2020 01 Oct 2014 Fixed 12.0.1 4169 01 Oct 2014 Fixed Description When using the SQL Anywhere .NET Data Provider, if the BulkCopyTimeout property was set to 0, an exception would have occurred during a call to WriteToServer. This has been fixed. The value 0 means that there is no timeout.

CR:771709

CR Number:   771709 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2020 01 Oct 2014 Fixed 12.0.1 4169 01 Oct 2014 Fixed Description When using the UltraLite .NET Data Provider, if the BulkCopyTimeout property was set to 0, an exception would hace occurred during a call to WriteToServer. This has now been fixed. The value 0 means that there is no timeout.

CR:771731

CR Number:   771731 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 2030 21 Oct 2014 Fixed 12.0.1 4179 21 Oct 2014 Fixed Description If an ALTER failed between START and STOP SYNCHRONIZATION SCHEMA CHANGES there was a possibility that the server would have failed assertion 107101 ("Table lock inconsistency"). This has been fixed.

CR:771766

CR Number:   771766 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2023 03 Oct 2014 Fixed Description UltraLite will now use the systems trusted roots if no trusted root certificate is provided. Also, the install package now includes a compiled library in the usual place. The script build.sh is no longer used to produce the library after installing.

CR:771780

CR Number:   771780 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 2042 12 Nov 2014 Fixed 12.0.1 4188 12 Nov 2014 Fixed Description If an application made an external environment call and then subsequently used STOP EXTERNAL ENVIRONMENT or STOP JAVA to shut down the external environment then there was a very small chance the server could have hung or crashed if the external environment crashed at the same time as the stop request. A similarly rare problem could have occurred if the connection was dropped at the same time the external environment crashed. This problem has now been fixed.

CR:771866

CR Number:   771866 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 2022 06 Oct 2014 Fixed Description Errors in batch change sets where formatted as multipart, contrary to the OData specification. For example: --batch_5f3ccbef-11fe-4dcc-a546-02ba2e746d72 Content-Type: multipart/mixed; boundary=cs_025fc4e4-fd30-4372-8fa4-5b941ee66915 --cs_025fc4e4-fd30-4372-8fa4-5b941ee66915 Content-Type: application/http Content-Transfer-Encoding: binary HTTP/1.1 400 Bad Request RepeatabilityResult: accepted Content-Type: application/json;charset=utf-8 { "error" : { "code" : "30063", "message" : { "lang" : "en-US", "value" : "An entity instance with this key already exists." } } } --cs_025fc4e4-fd30-4372-8fa4-5b941ee66915-- --batch_5f3ccbef-11fe-4dcc-a546-02ba2e746d72-- should be: --batch_5f3ccbef-11fe-4dcc-a546-02ba2e746d72 Content-Type: application/http Content-Transfer-Encoding: binary HTTP/1.1 400 Bad Request RepeatabilityResult: accepted Content-Type: application/json;charset=utf-8 { "error" : { "code" : "30063", "message" : { "lang" : "en-US", "value" : "An entity instance with this key already exists." } } } --batch_5f3ccbef-11fe-4dcc-a546-02ba2e746d72-- This has now been fixed.

CR:771873

CR Number:   771873 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 2022 06 Oct 2014 Fixed 12.0.1 4171 06 Oct 2014 Fixed Description If the Interactive SQL utility (dbisql) was run as a command-line program, it was possible for dbisql to report that it could not connect to the database, and then proceed to execute a statement anyway. In this scenario, dbisql would set its return code to 9 (could not connect) which was inconsistent with the fact that it actually executed the statement. For this to have occurred, all of the following would have had to be true: - A valid connection string and a statement must have been specified on the command line, - The database server had to be unreachable when dbisql started - The database server must then have become available as dbisql completeed its startup sequence This has been fixed. If the database server is unavailable when dbisql initially attempts to connect, it will now simply shut down, rather than attempting to execute the given statement.

CR:771878

CR Number:   771878 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 2022 06 Oct 2014 Fixed 12.0.1 4171 11 Nov 2014 Fixed Description If a client-side backup was terminated, or failed due a communication error or other unexpected error, database and transaction log file growth could have had poor performance. This has been fixed. Also, if the server was shut down while a backup was in progress, the backup could have reported a protocol error. This has been fixed so that a "Database server not found" error is now returned.

CR:771963

CR Number:   771963 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 2023 09 Oct 2014 Fixed Description A new OData Producer option has been created which allows service operations to use the names of the result set columns from the database when naming the properties of the ComplexType used in the ReturnType. Previously, if a stored procedure returned a result set, the OData Producer would only have used generated names (rtn1, rtn2, rtn3, ). A side effect when using the new option is that it is possible that column names from the database are invalid OData identifiers, or there are duplicate column names in the result set, which can produce invalid metadata. In this situation, users will need to either change the names of the result set columns in the database, write a wrapper stored procedure with different columns names in the result set, or revert to using generated column names. Option [producer-name].ServiceOperationsColumnNames = { generate | database } Description Specifies whether the names of the columns in the metadata should be generated (rtn1, rtn2, ) or whether the names from the database should be used. The default setting is generate.

CR:771964

CR Number:   771964 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 2030 21 Oct 2014 Fixed Description If a service operation had been defined to call a function, attempting to call the service operation would have resulted in an unexpected error in the OData Producer. This has now been fixed.

CR:772022

CR Number:   772022 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2023 08 Oct 2014 Fixed 12.0.1 4172 08 Oct 2014 Fixed Description If an application fetched a result set that contained long varchar, long binary or long nvarchar columns, then the SQL Anywhere JDBC driver would have fetched the result set one row at a time in order to ensure the full column value of the long columns could be retrieved. For result sets that do not contain long columns, the SQL Anywhere JDBC Driver fetched multiple rows at a time instead. Applications can use the Statement.setMaxFieldSize() method to attempt to limit the amount of data the JDBC Driver retrieves, however calling this method did not make the JDBC driver fetch multiple rows at a time. The SQL Anywhere JDBC driver will now fetch multiple rows at a time for result sets that contain long columns if Statement.setMaxFieldSize() is called and the value passed in to setMaxFieldSize() is less than or equal to 32K. The behaviour for result sets that do not contain long columns remains the same and the JDBC driver will continue to fetch multiple rows at a time for these result sets.

CR:772035

CR Number:   772035 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 2023 09 Oct 2014 Fixed Description A stored procedure with a input parameter whose name was an invalid OData identifier would only have encountered problems when the service operation was called. A stored procedure with a input parameter whose name is an invalid OData identifier will now generate an error when the service operation is defined.

CR:772116

CR Number:   772116 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2049 28 Nov 2014 Fixed 12.0.1 4194 28 Nov 2014 Fixed Description Execution of sSubqueries whose predicates were sized datatypes, such as char, varchar, and binary, could have crashed due to a data alignment exception. This has been fixed.

CR:772133

CR Number:   772133 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2024 10 Oct 2014 Fixed 12.0.1 4173 10 Oct 2014 Fixed Description Calling the system function ML_GET_SERVER_NOTIFICATION() would have failed on iOS using a client identity stored in the database. This has been fixed.

CR:772523

CR Number:   772523 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 2027 16 Oct 2014 Fixed 12.0.1 4176 16 Oct 2014 Fixed Description Under exceptionally rare circumstances, the server may have crashed when executing complex statements with proxy tables. This has been fixed.

CR:772559

CR Number:   772559 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 2033 16 Oct 2014 Fixed 12.0.1 4176 16 Oct 2014 Fixed Description SQL Anywhere, MobiLink, and UltraLite, servers and clients, no longer support the SSLv3 protocol. All TLS connections must now be TLSv1 or higher.

CR:772744

CR Number:   772744 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 2029 20 Oct 2014 Fixed Description Applications calling the dbtools function DBLogFileInfo() could have crashed. This has been fixed.

CR:772826

CR Number:   772826 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 2030 21 Oct 2014 Fixed Description When the Interactive SQL utility (dbisql) was run as a console application and connection parameters were specified, but the database password was not, dbisql would have exited without connecting. Now, dbisql will prompt for a password, given that the "-q" (quiet) option was not specified. Since a password is not required on the command line, the password will not be visible with OS utilities used to view process command lines.

CR:772828

CR Number:   772828 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 2030 21 Oct 2014 Fixed Description If the URI for a service operation was specified with missing input parameters, the OData Producer will now pass a NULL value into the underlying stored procedure or function. If a default value existed for the input parameter to the stored procedure or function, the OData Producer would have used the default value, which was contrary to the OData specifications.

CR:772899

CR Number:   772899 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 2030 23 Oct 2014 Fixed Description The OData producer allowed properties and navigational properties to have the same name as the containing type (for example, Entity type T1 could have a property called T1 and a navigational property called T1), contrary to the OData specification. Association names could have the same name as a complex type or entity type. The most common occurrence for this issue would be when the producer generated associations for a database Table that had a self-referring foreign key. While some OData clients ignored these naming restrictions, others such as Microsoft's would not have worked with a service whose metadata contained these name conflicts. This has been fixed. OSDL files with such name conflicts now produce errors, and generated navigational properties and associations are given better names.

CR:772919

CR Number:   772919 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 2030 24 Oct 2014 Fixed 12.0.1 4179 24 Oct 2014 Fixed Description Running the Mac OS X installer setup from the Terminal application would have displayed a reference to the SQL Anywhere Supported Platforms web page with an old URL (i.e. http://www.ianywhere.com/products/supported_platforms.html). This has been corrected to http://scn.sap.com/docs/DOC-35654

CR:773123

CR Number:   773123 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 2051 03 Dec 2014 Fixed 12.0.1 4196 03 Dec 2014 Fixed Description When computing a set operation (ST_Union, ST_Intersection, ST_Difference, ST_SymDifference), the value NULL was incorrectly returned if one of the inputs was an empty curve (e.g., 'LineString EMPTY'). This has been fixed.

CR:773198

CR Number:   773198 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 2036 03 Nov 2014 Fixed 12.0.1 4138 03 Nov 2014 Fixed Description Under rare circumstances, the server may have crashed while executing a query with OPENXML functions. This has now been fixed.

CR:773279

CR Number:   773279 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2046 21 Nov 2014 Fixed 12.0.1 4191 21 Nov 2014 Fixed Description Turning off The Interactive SQL utility's COMMIT_ON_EXIT option had no effect for the session in which it was turned off. This has now been fixed.

CR:773420

CR Number:   773420 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 2036 03 Nov 2014 Fixed 12.0.1 4184 03 Nov 2014 Fixed Description If more than 254 databases were specified on the command line when starting the database server, the server would have quit without giving an error. This has been fixed. A "Too many databases specified: <dbname>" error will now be generated.

CR:773422

CR Number:   773422 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 03 Nov 2014 Fixed 12.0.1 4184 03 Nov 2014 Fixed Description Under some conditions, when importing from a file containing long string values into a table with fixed length fields the server could have failed assertion 100914. This has been fixed

CR:773426

CR Number:   773426 Product Name:   SQL Anywhere Product Component:   Server Status:   Open OS:   Microsoft Windows Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 2049 12.0.1 4194 Description Under exceptionally rare circumstances, the server would have taken a long time to build the final query plan. This may have occurred for very complex and large queries. During this time DDL statements were blocked, which caused subsequent requests to block as well. This has been fixed.

CR:773529

CR Number:   773529 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 2041 03 Nov 2014 Fixed Description The EncryptedPassword (ENP) connection parameter is used to specify an encrypted password. It is a substitute for the Password (PWD) connection password. The intent of the ENP connection parameter is to disguise the actual password used to authenticate to a database. The current implementation obfuscates the password. There are some issues with this implementation: - The encrypted password could have been used to authenticate to the database by anyone from any computer who also had the corresponding user ID. - The ODBC Configuration for SQL Anywhere dialog of the ODBC Data Source Administrator (Windows-only) could have been used to return the encrypted password in clear text. - The encrypted password could have been decrypted with some effort. Encrypted password support has been enhanced with the following goals in mind: - Ability to restrict use to a particular computer or a particular computer/user. - Inability to reverse-engineer an encrypted password using the ODBC Configuration for SQL Anywhere dialog. - Better encryption algorithms to ensure that the encrypted password cannot be decrypted. - These enhancements to be available across all supported client platforms. A password can be encrypted on a computer such that it can only be decrypted on that computer. Anyone who can log on to the computer can use the encrypted password and corresponding user ID to authenticate to a database. It cannot be used on any other computer. A password can be encrypted on a computer by a user such that it can only be decrypted on that computer for that user. It cannot be used on any other computer by the same or other user. The Data Source utility (dbdsn) supports a new option -pet a|c|u, a specifying how the encrypted password may be used. If -pet a is specified, the password is encrypted for use on any computer. If -pet c is specified, the password is encrypted for use on this computer only. If -pet u is specified, the password is encrypted for use on this computer by this user only. The -pe option which provides simple obfuscation continues to be supported; however, its use is deprecated. Note that encryption for options -pet c and -pet u must be performed on the computer or computer/user for which it is intended to be used (decrypted). Note also that -pet u is not appropriate for client applications that are implemented as Windows services. Although -pet u can be used for a Windows System DSN, it may be more appropriate to use -pet c (since this form of encrypted password can be used by any user of the computer). The ODBC Data Source Administrator dialog is changed as follows: - The Encrypt password option is no longer a checkbox but is now used to select from different encryption options including none, for use on any computer, for use on this computer only, and for use on this computer and this user only. - The dialog can no longer be used to change the level of password encryption for an existing password, unless it was previously unencrypted. If the level of encryption is to be changed, then the password must be reentered. The ODBC Configuration for SQL Anywhere driver for Oracle dialog is also modified accordingly. These features allow a database administrator to restrict database access to a user on a particular computer without revealing the actual plain text password to the user. It also prevents the current password from being decrypted to memory and consequently subject to inspection. When successful decryption is restricted to a particular computer or computer/user, it no longer matters that the encrypted password is presented in plain text. For example, the encrypted password in the following connection string cannot be used by anyone other than the computer/user for whom it was created. dbping -d -c "Host=server-pc; Server=DemoServer; UID=DBA; ENP=05a17731bca92f97002100c39d906b70f3272fe76ad19c0e8bd452ad4f9ea9" The new encrypted password features are not supported by client libraries prior to this change. The File Hiding utility (dbfhide) options -wm (computer-only) and -w (computer/user-only) are now supported on all platforms for which dbfhide is available. The dbfhide tool can be used to encrypt an entire connection string to a file for use by most of the database tools that accept connection strings (e.g., dbping -d -c @credentials.hidden). Note that the encrypted password support described here is a client feature (storage of passwords on the client) and should not be confused with encryption of passwords over the wire during authentication, a default feature of SAP SQL Anywhere and optional in products like SAP Adaptive Server Enterprise (ASE).

CR:773535

CR Number:   773535 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 2041 03 Nov 2014 Fixed Description Backend farms and backend servers can now be automatically configured with default properties when auto_config=yes is specified in the [Options] section in the Relay Server configuration file. When auto_config is turned on, the Relay Server becomes a Trust On First Use (TOFU) system where Outbound Enablers can connect with unseen backend farm ids and backend server ids. A group of Outbound Enablers belonging to the same backend farm may connect with a farm-wide token. When the Relay Server processes the first Outbound Enabler connection with unseen farm name, a new backend farm configuration will be created. The Relay Server updates the original configuration file and then persists the supplied token in a new backend farm property named token. Other backend farm properties are initialized to the default values. The auto farm configuration persists across Relay Server restarts. Similarly, backend server configuration is also created and persisted per Outbound Enabler with unique server ids within the backend farm. The token supplied by all outbound enablers belonging to the same auto farm must match the farm-wide token, otherwise, access is to be denied. Other backend farm and server configuration can co-exist with auto_config=yes in the configuration file. Backend farms with farm-wide tokens can also be specified in the new token property of the [backend_farm] section in the Relay Server configuration file, so as to reserve the farm name before the Relay Server starts up. This feature is suitable for demos, integration testing, training and other administration free environments. Configurations created by this auto config feature can be further updated in on-line manner by using local rshost or remote AdminChannel. The auto_config property can also be changed in on-line manner using those tools

CR:773538

CR Number:   773538 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 2038 04 Nov 2014 Fixed Description The graphical plan did not show the value for "Final plan build time" in the "Advanced Details" of the top node under "Global Optimizer Statistics". This has been fixed.

CR:773549

CR Number:   773549 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) 04 Nov 2014 Fixed Description The response returned from a repeatable request may have been truncated or corrupted when GZIP or other compression related encodings were used. This has been fixed.

CR:773629

CR Number:   773629 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 2048 25 Nov 2014 Fixed 12.0.1 4193 25 Nov 2014 Fixed Description When the path for the server command line option -a ("apply named transaction log file") was wrong (the path is relative to the database path, not the server path) the server still seemed to go through recovery even though it did not. This has been fixed. Now server will return an error in such situations.

CR:773683

CR Number:   773683 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 2038 05 Nov 2014 Fixed 12.0.1 4185 05 Nov 2014 Fixed Description The server may have crashed if a DELETE statement that deleted rows from a local table also referenced proxy tables. This has been fixed.

CR:773703

CR Number:   773703 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 2038 05 Nov 2014 Fixed 12.0.1 4185 05 Nov 2014 Fixed Description Under exceptionally rare circumstances, the server may have leaked an internal connection with the connection name "INT:FlushStats", and therefore could not complete the database and server shutdown when requested. This has now been fixed.

CR:773811

CR Number:   773811 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 2040 06 Nov 2014 Fixed Description The OData Server could have crashed on Linux systems when using an INI file and no LIBRARY_PATH was specified in the INI file. This has been fixed.

CR:773812

CR Number:   773812 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 2041 11 Nov 2014 Fixed 12.0.1 4187 11 Nov 2014 Fixed Description The version of OpenSSL used by all SQL Anywhere products is now 1.0.1j.

CR:773894

CR Number:   773894 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 2042 11 Nov 2014 Fixed 12.0.1 4188 11 Nov 2014 Fixed Description When an ADO.NET application enlisted with a transaction coordinator, a constant GUID was supplied by the SQL Anywhere ADO.NET Data Provider. This prevented additional .NET applications, running on the same system, from doing the same. The following error message may have been seen. "A resource manager with the same identifier is already registered with the specified transaction coordinator. (Exception from HRESULT: 0x8004D102)" This problem has now been fixed so that instead of a constant GUID, a new one is generated each time enlistment occurs.

CR:773983

CR Number:   773983 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 2045 11 Nov 2014 Fixed Description A request for a raw binary value would have been return with a content-type of (or equivalent) 'text/plain', when it should have be 'application/octet-stream'. This has been fixed.