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

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

CR:743857

CR Number:   743857 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 1663 11 Sep 2013 Fixed 12.0.1 3971 11 Sep 2013 Fixed Description UltraLite may have blocked concurrent database access while synchronizing, during the UL_SYNC_STATE_FINISHING_UPLOAD synchronization state. This has been fixed.

CR:743862

CR Number:   743862 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 4005 21 Nov 2013 Fixed Description UltraLite on iOS previously required that certificates named in synchronization parameters be packaged as resources in the root of the application bundle. Now, if the named certificate resolves to a filename (directly), that file is used instead of searching the bundle. This means any certificate file in the application sandbox is now accessible given the proper path.

CR:743871

CR Number:   743871 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1613 25 Jul 2013 Fixed 12.0.1 3942 25 Jul 2013 Fixed 11.0.1 3017 25 Jul 2013 Fixed Description If the query of a cursor used the OrderedGroupBy algorithm in its execution plan, and was used to perform fetches that reversed direction of the scan, incorrect results could have been returned. This could have been observed for a cursor that fetched the first row, then second, then returned to the first row of an aggregate query. This has been fixed.

CR:743948

CR Number:   743948 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 4664 24 Jul 2013 Fixed Description When a task was chosen to run in the Run new task wizard, if the Task Parameters page had text inputs with the Default prompt text, choosing an item with browse would have overlayed that item name on top of the Default text, making it very hard to read. This has been fixed.

CR:744027

CR Number:   744027 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 1614 24 Jul 2013 Fixed 12.0.1 3942 24 Jul 2013 Fixed Description The SQL Anywhere PHP External Environment supports several versions of the PHP interpreter. The SQL Anywhere install bundle includes a separate PHP external environment dll or shared object for each supported version of PHP. In addition, whenever support for a new version of the PHP interpreter is added, the SQL Anywhere install bundle is updated to include the new PHP external environment dll or shared object for the new version of the PHP interpreter. Going forward, the SQL Anywhere install bundle will no longer be updated with additional PHP external environment dlls or shared objects when support for new versions of the PHP interpreter are added. Instead, the new PHP external environment dlls and shared objects will now only be available on the download site.

CR:744039

CR Number:   744039 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 1614 25 Jul 2013 Fixed 12.0.1 3942 25 Jul 2013 Fixed Description It was not possible to connect to a tracing database when profiling using a client-only install. This has been fixed. Now, only opening an analysis file is prevented in a client-only install.

CR:744044

CR Number:   744044 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 1623 01 Aug 2013 Fixed 12.0.1 3946 01 Aug 2013 Fixed 11.0.1 3020 01 Aug 2013 Fixed Description When testing a connection to a MySQL remote server, Sybase Central could sometimes have reported that the connection failed, when in fact it had succeeded. This has been fixed.

CR:744047

CR Number:   744047 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1726 11 Nov 2013 Fixed Description In some cases, a server with a database containing procedures with nested row parameters could have crashed. This has been fixed.

CR:744130

CR Number:   744130 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 4666 26 Jul 2013 Fixed Description When adding a database, if the user did not have permission to apply maintenance plans and tried to set one for the database, the wizard would have given an error after clicking Finish. Going back to the maintenance plan page to select the default plan would have resulted in the wizard continuously asking for credentials after Finish was clicked. This has been fixed. The maintenance plan page is not shown if the user does not have the permission to set it.

CR:744132

CR Number:   744132 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 4666 26 Jul 2013 Fixed Description If a database name started with a number it could not have been moved with the Move Database wizard. The move would have failed with the error: Error in the search query "database:4" near "database:4". Error code: -20090 (DBCLOUDERR_SEARCH_STRING) This has been fixed.

CR:744212

CR Number:   744212 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 4667 29 Jul 2013 Fixed Description On the Databases panel, columns previously hidden would have re-appeared when revisiting the panel. The Servers panel also had a blank menu for the cloud. These problems have now been fixed.

CR:744228

CR Number:   744228 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 4668 29 Jul 2013 Fixed Description Paging to a page other than page 1 on the Servers or Databases panels, would not have reset the page number if another panel was visited and then the panel was gone back to. This has been fixed.

CR:744299

CR Number:   744299 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 4672 31 Jul 2013 Fixed Description If a 12.0.l database was added to a 16.0 server with the name beginning with a digit, a copy database could not have been created for it. This has been fixed.

CR:744458

CR Number:   744458 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 1646 01 Aug 2013 Fixed Description Mac OSX, SUN, Linux, AIX, and HP platforms no longer require setting the shared library path before launching the Interactive SQL utility. The path is now set by the launcher using the 'LIBRARY_PATHS' setting in the dbisql.ini file.

CR:744754

CR Number:   744754 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 1631 07 Aug 2013 Fixed Description The INPUT statement or the Import wizard in the Interactive SQL utility could have skipped rows from a TEXT formatted input file if it contained strings which were delimited by quotation marks, and the string contained an apostrophe. This has been fixed. Note, there was no problem if the strings were delimited by apostrophes.

CR:744845

CR Number:   744845 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 1631 08 Aug 2013 Fixed 12.0.1 3951 08 Aug 2013 Fixed Description The context menu for the SQL Statements panel includes a "Help on" menu item if there might be online help for the statement under the mouse. Clicking the "Help on" menu item opens help in a browser if local help is not installed. The process of opening the help has been sped up, especially if no help files were installed. How much faster depends on the network connection. Also, the software is now more tolerant of whitespace between keywords. For example, suppose the SQL Statements panel contained the following valid statement, spread across four lines: CREATE VARIABLE retcode INT Clicking "Help on" in the context menu would have failed to open help because of the newlines that separate the tokens. Now, help for the CREATE VARIABLE statement will be opened.

CR:745191

CR Number:   745191 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1638 15 Aug 2013 Fixed 12.0.1 3954 15 Aug 2013 Fixed Description The Outbound Enabler has a fixed limit of 1000 active connections with the backend server per Relay Server. The Outbound Enabler would have crashed when the limit was exceeded. This has been fixed by relaxing the internal limit to 32768 active connections. An OEE1051 error is given when that limit is now exceeded.

CR:745198

CR Number:   745198 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1656 03 Sep 2013 Fixed 12.0.1 3968 03 Sep 2013 Fixed Description The ODBC driver could have exhibited inconsistent behavior when calling a stored procedure with blob parameters. The problem only occurred with data-at-execution-time blob parameters. Blobs of type Varchar worked correctly, but blobs of type binary did not. The problem has now been fixed.

CR:745250

CR Number:   745250 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   16.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1639 15 Aug 2013 Fixed Description After adding a new MobiLink server in the MobiLink Farm Configuration Resource window, the new server was not shown in the "Identify the servers in the farm" field. This has been fixed.

CR:745256

CR Number:   745256 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 4690 15 Aug 2013 Fixed Description If a cloud server required a proxy server to get to the internet, it would have been unable to contact the Cloud Software download site. The Console would have reported: "The list is being updated", stayed like that for a very long time, and then reported: "There is nothing to download". This has been fixed. Note, until SP4 becomes available, to enable current Clouds that have a proxy setting to take advantage of this fix, the new patch "dbcloud-fix-checkforupdates-proxy.patch" must be applied to the Cloud.

CR:745266

CR Number:   745266 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   16.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1639 16 Aug 2013 Fixed Description The "Failed Synchronization Rate" metric did not show a trend when failed synchronization was 0. This has been fixed.

CR:745267

CR Number:   745267 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 1639 19 Aug 2013 Fixed Description The maximum value allowed for the OData Producer PageSize option was only 1000. This was deemed unreasonably small and has now been increased to 1,000,000. The default setting has not been changed.

CR:745394

CR Number:   745394 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 1643 19 Aug 2013 Fixed Description When connected using TDS (Open Client or jConnect), executing a procedure that contained a SELECT INTO statement, could have caused the server to crash. Note that chained mode needed to be off for this to have occurred. This has now been fixed.

CR:745468

CR Number:   745468 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3958 03 Sep 2013 Fixed 11.0.1 3030 03 Sep 2013 Fixed Description If a Directory Access server accessed a file with a size over 4GB, the file length would have been reported as a size smaller than 4GB. This has been fixed.

CR:745564

CR Number:   745564 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 1645 22 Aug 2013 Fixed Description When using the LogFile connection parameter, the timestamp logged before each connection was truncated to only include the first digit of the seconds. This has been fixed.

CR:745646

CR Number:   745646 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 1646 23 Aug 2013 Fixed Description Downloads could have been incorrectly skipped in persistent connections. This has been fixed.

CR:745648

CR Number:   745648 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 1646 23 Aug 2013 Fixed 12.0.1 3959 23 Aug 2013 Fixed Description In rare timing dependent cases, near when a transaction log rename was being performed, the sa_mirror_server_status log_written or log_applied columns could have been inaccurate. This has been fixed.

CR:745838

CR Number:   745838 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   2.2 SP02 PL00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Aug 2013 Consult Complete Description Too many sockets opened between RSOE and SUP

CR:746082

CR Number:   746082 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 1658 05 Sep 2013 Fixed 12.0.1 3969 05 Sep 2013 Fixed Description When an application using ADO.NET had disconnected all of its connections so that they were pooled, an autostarted database, and/or server, could have autostopped, causing the server to need to be autostarted again if the same application connected again. This has been fixed so that in most cases, the presence of a pooled ADO.NET connection will prevent the server from autostopping. Note that in cases where pooled connections cannot be reused (for example, connections using integrated login, or the user's password was changed), the database and/or server may still autostop even with this fix.

CR:746108

CR Number:   746108 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3967 03 Sep 2013 Fixed Description The MobiLink server could have crashed when it was trying to upload updates to tables that contained BLOB columns, if the upload_update script took BLOB columns in its Where clause and the parameters in the script are specified by question marks. To prevent the crash, a workaround is to change the question marks to use named parameters instead. This problem has now been fixed.

CR:746236

CR Number:   746236 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 1709 23 Oct 2013 Fixed 12.0.1 3996 23 Oct 2013 Fixed Description Under very rare circumstances, the server may have crashed during server shutdown if a SQL Anywhere debugger was still connected. This has been fixed.

CR:746290

CR Number:   746290 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 1657 05 Sep 2013 Fixed 12.0.1 3968 05 Sep 2013 Fixed Description On Windows systems, CPUs numbered 32 and above were not detected correctly and treated as offline. This has been fixed

CR:746461

CR Number:   746461 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 1648 06 Sep 2013 Fixed Description The OData Producer now respects Content-Encoding and Accept-Encoding HTTP request headers as specified by the HTTP 1.1 spec: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html The Content-Encoding header is used by clients to indicate the encoding of the request body. The Accept-Encoding header is used by clients to indicate the preferred encoding of the response body.

CR:746575

CR Number:   746575 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 15 Oct 2013 Fixed 12.0.1 3971 15 Oct 2013 Fixed Description When a .NET application disconnected and then reconnected to the server, the timestamp_with_time_zone_format option was not re-established to the required .NET default ('YYYY-MM-DD HH:NN:SS.SSSSSS+HH:NN'). When the connection is pooled, the server resets server options to their defaults. When a connection was retrieved from the connection pool, the SQL Anywhere .NET provider must re-issue a SET TEMPORARY OPTION statement. This lead to a DateTimeOffset (timestamp with time zone) conversion error at run-time. A work-around is to execute a ... SET OPTION PUBLIC.timestamp_with_time_zone_format = 'YYYY-MM-DD HH:NN:SS.SSSSSS+HH:NN' statement which sets the default required for all .NET connections. This problem has been fixed. Workaround Description  SET OPTION PUBLIC.timestamp_with_time_zone_format = 'YYYY-MM-DD HH:NN:SS.SSSSSS+HH:NN'

CR:746586

CR Number:   746586 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 1664 11 Sep 2013 Fixed 12.0.1 3971 11 Sep 2013 Fixed 11.0.1 3039 11 Sep 2013 Fixed Description In rare cases, the server may have crashed or returned an incorrect SQL error if the UPDATE clause of a bypass update statement had an invalid subselect as table-expression. This has been fixed.

CR:746650

CR Number:   746650 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1663 10 Sep 2013 Fixed 12.0.1 3971 10 Sep 2013 Fixed Description The units reported for the system dbpace file size metric was MB and should have been KB. This has been fixed.

CR:746678

CR Number:   746678 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 4714 10 Sep 2013 Fixed Description The XML output from the Event Trace Data File Management utility (dbmanageetd) did not display the correct output of strings if the ETD file was generated by a database that was encoded in something other than UTF-8. This has now been fixed.

CR:746688

CR Number:   746688 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3968 11 Sep 2013 Fixed 11.0.1 3035 11 Sep 2013 Fixed Description The following improvements and bug fixes have been made to the SQL Anywhere OLE DB provider: 1. When a column cannot be fetched in its entirety, set status to DBSTATUS_S_TRUNCATED instead of DBSTATUS_S_OK and length to actual length, not amount fetched. 2. IRowsetUpdate methods InsertRow/Update should insert rows in manual commit mode (i.e., commit in batches) rather than autocommit each row. 3. Improved support for DBTYPE_DBTIMESTAMPOFFSET data types. 4. In order to identify columns that are DEFAULT AUTOINCREMENT, IColumnsInfo::GetColumnInfo now sets the DBCOLUMNFLAGS_ISROWVER bit for those columns. Microsoft defines a column with this attribute as a non-writable versioning column (such as the SQL Server TIMESTAMP) which suits SQL Server. Note, however, that SQL Anywhere supports versioning columns that are writable. 5. Corrected failure to describe money/smallmoney as DBTYPE_CY (currency type). Also corrected OLE DB schema queries DBSCHEMA_COLUMNS, DBSCHEMA_PROCEDURE_COLUMNS, and DBSCHEMA_PROCEDURE_PARAMETERS results for DBTYPE_CY. 6. Corrections to schema rowset information (DBSCHEMA_COLUMNS, DBSCHEMA_PROCEDURE_COLUMNS, and DBSCHEMA_PROCEDURE_PARAMETERS) for datetime/time precision and scale. 7. Corrections to run-time information for datetime/time precision and scale. 8. Add "DATETIME" to list of DBPARAMBINDINFO.pwszDataSourceType types for SetParameterInfo (SQL Server uses this undocumented type name). Type names are usually of the form DBTYPE_xxx (for example, DBTYPE_I4, DBTYPE_STR, DBTYPE_DBTIMESTAMP). 9. Adjust GetConversionSize values for TIME, DATETIME, DATETIMEOFFSET data types (only 6 fractional digits are supported by SQL Anywhere). 10. Fixed memory leak caused by failure to free rows whose refcount is 0 in Update(). 11. Fixed possible memory corruption in calls to IRowsetChange::SetData, IRowsetChange::InsertRow, ISequentialStream::Write, and IRowChange::SetColumns. 12. Fixed performance problem when DataConvert is used when no conversion is required. 13. The LoadCommand, DeleteCommand, and SaveCommand methods of the ICommandPersist interface did not qualify system tables references with an owner name. This has been corrected. 14. The OLE DB provider accepts two cbBookmark values, 1 which is the short DBBMK_FIRST/LAST value, and 4 or 8 depending on the bitness of the provider. The 64-bit provider flags 4 was an illegal value for cbBookmark. The 32-bit provider flags 8 was an illegal value for cbBookmark. The OLE DB provider should accept both 4 and 8 as the length of a bookmark value and fetch the appropriate 32-bit/64-bit bookmark value from memory. This problem has been corrected. The fix affects IRowsetLocate::GetRowsAt, IRowsetLocate::Compare, RowsetLocate::GetRowsByBookmark, IRowsetLocate::Hash, and IRowsetScroll::GetApproximatePosition, and IRowsetExactScroll::GetExactPosition. Both 32-bit and 64-bit providers now support 4-byte and 8-byte bookmark values, in addition to 1-byte values.

CR:746767

CR Number:   746767 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 1761 12 Dec 2013 Fixed 12.0.1 4033 12 Dec 2013 Fixed Description In a .NET application, it was possible to store a decimal number into a NUMERIC/DECIMAL table column when the precision of the decimal number exceeded the precision of the NUMERIC/DECIMAL column by 1. Also, when the stated precision of a decimal value parameter was much less than the actual precision of a decimal value, it is possible to corrupt the heap. parm.Precision = 5; parm.Value = (decimal) 123456789; These problems have now been fixed.

CR:746924

CR Number:   746924 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1671 17 Sep 2013 Fixed 12.0.1 3973 17 Sep 2013 Fixed Description In very rare, timing dependent cases, mirroring servers (likely more than one) could have hung indefinitely. If, while processing ALTER DATABASE SET PARTNER FAILOVER, connections between the primary and mirror servers timed out, or were dropped, before the failover operation completed, the primary server could have stopped accepting connections. The sa_mirror_server_status log_written offset could have been incorrect about the time a log rename occurred.

CR:746935

CR Number:   746935 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 1665 16 Sep 2013 Fixed Description The dbo.sp_list_directory() stored procedure can be used to obtain information about directories and files that are accessible to the SQL Anywhere Server. Currently the sp_list_directory() procedure returns the following three columns: file_path long nvarchar the path of the server accessible file or directory file_type nvarchar(1) either F for file or D for directory file_size unsigned bigint the size of the file or NULL for directories In order to provide more information about the various files and directories, dbo.sp_list_directory() has now been enhanced to return five additional columns. These five additional columns are: owner nvarchar(128) the owner of the file or directory create_date_time* timestamp with time zone the date and time the file or directory was created modified_date_time* timestamp with time zone the date and time the file or directory was last modified access_date_time* timestamp with time zone the date and time the file or directory was last accessed permissions varchar(10) the set of access permissions for the file or directory All other aspects of dbo.sp_list_directory() including the set of system privileges and secure feature privileges remain unchanged. A database either has to be upgraded or initialized in order for applications to obtain this new information from dbo.sp_list_directory(). In addition, if an upgraded or newly initialized database is subsequently moved to an older version of the server, then the new columns will continue to be returned but the values of the new columns will be NULL.

CR:747038

CR Number:   747038 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1674 08 Nov 2013 Fixed Description When the HAVING clause of a query contained predicates of the following form, the server attempted to estimate the selectivity based on the column statistics: - HAVING SUM( column ) <= constant - HAVING SUM( column ) < constant - HAVING SUM( column ) > constant - HAVING SUM( column ) >= constant so that incorrect selectivity could be returned in the following cases: - the column was a number but the constant was not (e.g., it was a date). - the comparison relation was <> or = (these can not be estimated). - the comparison was of the form SUM(column) LIKE string_constant. This has now been corrected.

CR:747053

CR Number:   747053 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 1671 17 Sep 2013 Fixed 12.0.1 3973 17 Sep 2013 Fixed Description If the primary server failed and the mirror took over as the new primary, the old primary could have failed to start and reported "database is not compatible with primary; files must be replaced" in the console log, even though it should have been able to start. In order for this failure to have been reported when it should not have been, there had to be over 64 transaction log pages since the last checkpoint. This has been fixed. Note that this failure (database is not compatible) can still validly occur in certain cases.

CR:747118

CR Number:   747118 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1672 17 Sep 2013 Fixed Description In the MobiLink Plugin, if the MobiLink Server CommandLine was renamed and then deleted it without shutting down Sybase Central, the delete confirmation dialog would have shown the old name for the commandline instead of the new one. This has now been corrected

CR:747141

CR Number:   747141 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 1673 23 Sep 2013 Fixed 12.0.1 3974 23 Sep 2013 Fixed Description In very rare timing dependent cases, a copy node's transaction log could have been corrupted if the primary failed over to the mirror. In order for this to have occurred, the old primary would have needed to still be running and not in the process of stopping during the failover (for example, running extremely slowly due to lack of machine resources). If this problem did occur, the most likely failures would be assertion 100902, 100903 or 100904, but other failures were also possible. This has been fixed.

CR:747205

CR Number:   747205 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 1673 18 Sep 2013 Fixed Description The geospatial method ST_BUFFER is now supported for all geometry types. This method is compatible with the SQL/MM and OGC standards. ST_BUFFER returns the ST_Geometry value that represents all points whose distance from any point of an ST_Geometry value is less than or equal to a specified distance in the given units. ST_GEOMETRY::ST_BUFFER( distance double, unit_name long varchar ) - distance: The distance the buffer should be from the geometry value. Must be greater than or equal to 0. - unit_name: The units in which the distance parameter should be interpreted. Defaults to the unit of the spatial reference system. The unit name must match the UNIT_NAME column of a row in the ST_UNITS_OF_MEASURE view where UNIT_TYPE is 'LINEAR'. - Returns the ST_Geometry value representing all points within the specified distance of the original geometry. The ST_Buffer method generates a geometry that expands a geometry by the specified distance. This method can be used, for example, to find all points in geometry A that are within a specified distance of geometry B. The distance parameter must be a positive value. This method will return an error if distance is negative. If the distance parameter is equal to 0, the original geometry is returned. The ST_Buffer method is best used only when the actual buffer geometry is required. Determining whether two geometries are within a specified distance of each other should be done using ST_WithinDistance instead.

CR:747227

CR Number:   747227 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 1667 20 Sep 2013 Fixed 12.0.1 3974 20 Sep 2013 Fixed Description The MobiLink Server leaked memory when using secure streams on Mac OS X systems. This has now been fixed.

CR:747231

CR Number:   747231 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 1674 19 Sep 2013 Fixed Description The default query to fetch the next 'last download' timestamp was slow when using a HANA consolidated. This has been fixed. The server now caches the results of this query, so its value can be up to 8 seconds out of date. This can result in extra rows being downloaded.

CR:747277

CR Number:   747277 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 1674 19 Sep 2013 Fixed Description A new database property, BackupInProgress, has been added. Querying the property will return 'on' when there is a backup happening, and 'off' otherwise.

CR:747308

CR Number:   747308 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 1681 27 Sep 2013 Fixed 12.0.1 3978 27 Sep 2013 Fixed Description The Entity Framework method Import would have failed to find procedures if the procedures had comments in front of ALTER PROCEDURE. This has now been corrected.

CR:747334

CR Number:   747334 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 1683 27 Sep 2013 Fixed 12.0.1 3979 27 Sep 2013 Fixed Description A client application could have hung when opening a pooled connection following a failed connection. This has now been fixed.

CR:747342

CR Number:   747342 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1676 23 Sep 2013 Fixed Description On Windows systems, the Data Source utility (dbdsn) would have failed with the error User Data Source <name> could not be written to registry when trying to create a DSN with a name longer than 32 characters. This is a Windows limitation so a more appropriate error message is now displayed.

CR:747358

CR Number:   747358 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) 23 Sep 2013 Fixed Description If a proxy was set to reach the internet, it was not used by the software update checker. This has been fixed.

CR:747426

CR Number:   747426 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1674 23 Sep 2013 Fixed Description Now, dbmlsync/dbremote support synchronization/replication for databases in a cloud. Instead of directly accessing the offline transaction log files, dbmlsync/dbremote will retrieve offline transaction logs through the database server. The user ID that is used by dbmlsync/dbremote to connect to the synchronization/replication database must have the READ FILE and WRITE FILE privileges and all the offline transaction log files must be in the online transaction log directory. The database server must have the same level of SP in order to support this feature. Dbmlsync/dbremote will retrieve the offline transaction logs through the server, if the given offline transaction log directory cannot be opened or contains no offline transaction log files, but offline transaction logs are required. Synchronized/replicated offline transaction log files will also be deleted through the server, if the database option, delete_old_logs is set to be On, Delay, or n days.

CR:747538

CR Number:   747538 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) 12.0.1 3977 27 Sep 2013 Fixed Description The UltraLite runtime may have generated UUID values which were not globally unique on iOS 7. This has been fixed.

CR:747637

CR Number:   747637 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 1681 25 Sep 2013 Fixed 12.0.1 4090 20 Mar 2014 Fixed Description If an ODBC application performed a wide or array INSERT, where the number of rows times the number of columns was more than 32767, the INSERT may not have been as efficient as it should have been. This has been fixed so that the wide or array INSERT is more efficient in this case.

CR:747649

CR Number:   747649 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 1681 26 Sep 2013 Fixed 12.0.1 3978 26 Sep 2013 Fixed Description In rare timing dependent cases, a copy node could have failed with a log mismatch message or an assertion failure when a log rename was performed. In order for this problem to have occurred, in addition to processing the log rename, the copy node needed to be transitioning from requesting to receiving log pages from its parent, or a connection to its parent would have had to be dropped and reconnected. This has been fixed.

CR:747714

CR Number:   747714 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 1683 27 Sep 2013 Fixed Description Trying to save the Application Profiling recommendations could have failed. This has been fixed.

CR:747794

CR Number:   747794 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) 27 Sep 2013 Fixed 12.0.1 3978 27 Sep 2013 Fixed Description The server now recognizes when it is running on Windows 8.1 and Windows Server 2012 R2 operating systems.

CR:747798

CR Number:   747798 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 1675 27 Sep 2013 Fixed Description A new system function has been added, READ_SERVER_FILE(). This function reads data from a specified file on the server and returns the full or partial contents of the file as a LONG BINARY value. Syntax: READ_SERVER_FILE( filename ) [, start [ , length] ] Parameters: - filename LONG VARCHAR value indicating the path and name of the file on the server. - start The start position of the file to read, in bytes. The first byte in the file is at position 1. A negative starting position specifies the number of bytes from the end of the file rather than from the beginning. * If start is not specified, a value of 0 is used. * If start is zero and length is non-negative, a start value of 1 is used. * If start is zero and length is negative, a start value of -1 is used. - length The length of the file to read, in bytes. * If length is not specified, the function reads from the starting position to the end of the file. * If length is positive, the function read ends length bytes to the right of the starting position. * If length is negative, the function returns at most length bytes up to, and including, the starting position, from the left of the starting position. Returns: LONG BINARY Remarks: This function returns the full or partial (if start and/or length are specified) contents of the named file as a LONG BINARY value. If the file does not exist or cannot be read, NULL is returned. filename is relative to the starting directory of the database server. The READ_SERVER_FILE function supports reading files larger than 2GB. However, the returned content is limited to 2GB. If the returned content exceeds this limit, a SQL error is returned. If the data file is in a different character set, you can use the CSCONVERT function to convert it. You can also use the CSCONVERT function to address the character set conversion requirements you may have when using the READ_SERVER_FILE server function. If disk sandboxing is enabled, the file referenced in filename must in an accessible location. Privileges: When reading from a file on a client computer: * You must have the READ FILE system privilege. * You must have read permissions on the directory being read from. Standards: SQL/2008 Vendor extension. Example: The following statement reads 20 bytes in a file, starting from byte 100 of the file. SELECT READ_SERVER_FILE( 'c:\\data.txt', 100, 20 ) See also * xp_read_file system procedure * CSCONVERT function [String] * Disk sandboxing

CR:747805

CR Number:   747805 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 1688 27 Sep 2013 Fixed 12.0.1 3980 01 Oct 2013 Fixed 11.0.1 3052 08 Oct 2013 Fixed Description For Syntax 2 of the DELETE statement and Syntax 2 of the UPDATE statement the error detection behaviour of the server has been improved. These two syntax forms allow an additional FROM clause that may contain the table-name of the updated or deleted table, for example: DELETE FROM [owner.]table_1 [ [ AS ] correlation-name ] FROM [owner.]table_1 [ [ AS ] correlation-name ] ... WHERE ... and UPDATE [owner.]table_1 [ [ AS ] correlation-name ] SET columns_1 = ... FROM [owner.]table_1 [ [ AS ] correlation-name ] ... WHERE ... If the DELETE or UPDATE clause and the additional FROM clause have a table reference that contains the same table name, in the above example "table_1", then the server can only decide whether both are identical table references if one of the following conditions is true: - both table references are not qualified by specifying a user ID - both table references are qualified by specifying a user ID - both table references are specified with a correlation name In cases where the server cannot decide whether the above table references are identical or not it will now return an SQL error to prevent the user from unintended semantics like deleting and updating to many rows.

CR:747810

CR Number:   747810 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 1684 30 Sep 2013 Fixed 12.0.1 3980 30 Sep 2013 Fixed Description When a mirror or copy node was shutdown while a connection was blocked on a lock held by an internal connection which was applying log operations, the shutdown could have hung. Note that mirror or copy node databases shutdown and restart automatically for a number of internal reasons, for example, the mirror database can shutdown and restart if the connection between the partner servers becomes disconnect but the primary partner is still running. This has been fixed.

CR:747819

CR Number:   747819 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 1673 30 Sep 2013 Fixed Description When the server encounterd a file error when writing to an ETD file, it should have returned it as a SQL error; but in some cases, the error is not returned. This has been fixed.

CR:747898

CR Number:   747898 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1684 30 Sep 2013 Fixed 12.0.1 3981 30 Sep 2013 Fixed 11.0.1 3047 30 Sep 2013 Fixed Description When using the SQL Anywhere JDBC driver, if two or more addBatch calls are followed by an executeBatch and then the application used executeUpdate in non-batched mode, the application would have crashed. This problem has been fixed. A work-around is to use addBatch/executeBatch for all executions of the prepared statement once addBatch/executeBatch has been used.

CR:747910

CR Number:   747910 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 4738 30 Sep 2013 Fixed Description In certain cases, initialization of the cloud could result in an invalid IPv6 address among those listed for a cloud host. This has been fixed.

CR:748083

CR Number:   748083 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 1900 28 Apr 2014 Fixed Description The server may have crashed when using ARRAY or ROW type values in string operations. This has been fixed.

CR:748096

CR Number:   748096 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 1697 16 Oct 2013 Fixed 12.0.1 3989 16 Oct 2013 Fixed Description If a stored procedure containing a single SELECT statement that uses a key join was inlined, and the connected user was not the procedure owner and has no select permissions on the table(s) in the query, a permission error could have been returned. This has been fixed.

CR:748102

CR Number:   748102 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Agent Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.0 4740 03 Oct 2013 Fixed Description The cloud Agent could hang after an HTTP GET request returned an HTTP status code of 4xx. The most common scenario for this issue was when starting a cloud on the primary server, the Agent would have received a 404 or 401 HTTP error on its first poll request and hang. In that case, the cloud Console would have reportd host disconnected for the host. This has been fixed.

CR:748170

CR Number:   748170 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 1691 04 Oct 2013 Fixed 12.0.1 3984 04 Oct 2013 Fixed Description In rare timing dependent cases, a copy node that had just processed a Log rRename could have failed assertion 200505, if its child was requesting log pages. This has been fixed.

CR:748349

CR Number:   748349 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 2009 09 Sep 2014 Fixed 12.0.1 4159 09 Sep 2014 Fixed Description In extremely rare timing dependent cases, it was possible for the transaction log on a copy node to have become corrupted. In order for the potential corruption to have occurred, the copy node needed to have a parent other than the primary/root server, and the parent must have been writing a page to the transaction log at the same time the child copy node was requesting the last page of the parent's transaction. Note that once the copy node has caught up the log operation of the parent, the parent sends pages to the copy node during commit operations. This problem could have only occurred when the copy node is requesting pages from the parent, and not when the parent is sending pages to the copy node. This has been fixed.

CR:748351

CR Number:   748351 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1697 10 Oct 2013 Fixed 12.0.1 3988 10 Oct 2013 Fixed Description Mirror and copy node servers were not applying transaction log changes as efficiently as they could have been. This has been fixed to be more efficient.

CR:748414

CR Number:   748414 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 1696 08 Oct 2013 Fixed 12.0.1 3987 08 Oct 2013 Fixed Description Relay Server monitoring provided via the SQL Anywhere Monitor may have suffered stack overflow exceptions on the Java data collection client. This is now fixed.

CR:748429

CR Number:   748429 Product Name:   MobiLink Product Component:   MobiLink Profiler Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1696 09 Oct 2013 Fixed Description With some versions of Linux and Unix, the Port field of the Connect to MobiLink Server window was not displayed correctly; it was too narrow for the port number to be visible. This has been fixed.

CR:748450

CR Number:   748450 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 1696 09 Oct 2013 Fixed 12.0.1 3987 09 Oct 2013 Fixed Description In some rare cases, the server may have crashed while processing HTTP/HTTPS requests. This has been fixed.

CR:748531

CR Number:   748531 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1691 09 Oct 2013 Fixed 12.0.1 3984 09 Oct 2013 Fixed Description Synchronizations could have spuriously failed if the MobiLink server was configured to use end-to-end encryption, but the client was not. This has been fixed.

CR:748535

CR Number:   748535 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1697 10 Oct 2013 Fixed 12.0.1 3988 10 Oct 2013 Fixed 11.0.1 3052 10 Oct 2013 Fixed Description The Linux GTK and Mac OS X UI installer improperly reported insufficient disk space if there was more than 2 TB of available disk space. This has been fixed. A workaround is to use setup -nogui to avoid the use of the graphical installer. Alternatively, install to a smaller disk drive.

CR:748538

CR Number:   748538 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1697 10 Oct 2013 Fixed 12.0.1 3988 10 Oct 2013 Fixed 11.0.1 3052 10 Oct 2013 Fixed Description Specifying the command line option -nogui after the option -silent when running the UNIX setup script would have caused the -silent flag to be ignored. This has been fixed. The -nogui option now has no effect if -silent is specified at any point. A workaround is to avoid specifying -nogui when doing a silent install.

CR:748541

CR Number:   748541 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 1697 10 Oct 2013 Fixed Description When upgrading a 32-bit SQL Anywhere installation containing SQL Anywhere Monitor, the 64-bit server would have been installed, whether or not it was previously installed. Similarly, upgrading a 64-bit SQL Anywhere installation containing SQL Anywhere Monitor would have caused the 32-bit server to be installed, whether or not it was previously installed. This has been fixed.

CR:748548

CR Number:   748548 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1704 16 Oct 2013 Fixed 12.0.1 3993 16 Oct 2013 Fixed Description If a database contained subscriptions for more than one MobiLink user, and at least one of those users had a name containing non-alphanumeric characters, then it was possible for synchronizations to fail and generate incorrect error messages. The messages generated may have included, There is no synchronization subscription for user ? to publication ? or Communication protocol mismatch. Unable to negotiate an appropriate communication protocol with the MobiLink server. Other error messages were likely also possible. This has been fixed. Having non-alphanumeric characters in MobiLink user names should now be handled correctly.

CR:748557

CR Number:   748557 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 1697 10 Oct 2013 Fixed 12.0.1 3988 10 Oct 2013 Fixed Description Opening the text completer when connected to an ASE database could have caused the Interactive SQL utility to crash. This has been fixed.

CR:748710

CR Number:   748710 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 1846 07 Mar 2014 Fixed 12.0.1 4083 07 Mar 2014 Fixed Description Under some circumstances, the server could have crashed when executing a procedure with NO RESULT SET clause. This has been fixed.

CR:748717

CR Number:   748717 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1691 15 Oct 2013 Fixed 12.0.1 3988 15 Oct 2013 Fixed Description UltraLiteJ for Android no longer supports ARMv5 CPU architectures. The minimum supported CPU architecture is now ARMv7.

CR:748725

CR Number:   748725 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 1699 15 Oct 2013 Fixed Description When MobiLink uploaded a UUID (GUID) to SAP HANA, hyphens would have been added to the resulting string, resulting in a VARCHAR(40) field instead of a VARCHAR(36). This change removes the hyphens from UUIDs so that UUID columns can now be stored as a VARCHAR(36) in SAP HANA, which matches the SAP HANA default UUID format.

CR:748972

CR Number:   748972 Product Name:   MobiLink Product Component:   MobiLink Profiler Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1704 17 Oct 2013 Fixed Description When the Utilization Graph pane was enabled, if the Chart pane did not have a vertical scroll bar the Zoom To Selection menu and toolbar button might not have worked correctly, and scrolling might not have worked correctly. This has been fixed. A workaround is to disable the Utilization Graph pane, or to resize the Chart pane so that it has a scroll bar.

CR:748976

CR Number:   748976 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 1814 03 Feb 2014 Fixed 12.0.1 4065 03 Feb 2014 Fixed 11.0.1 3106 03 Feb 2014 Fixed Description If a database had one or more of the following public options set differently: - ansinull=On - conversion_error=On - divide_by_zero_error=On - sort_collation=Internal - string_rtruncation=On , and the specified value was then set as a temporary option for the connection creating a materialized view, recovery of the CREATE MATERIALIZED VIEW statement would have failed. This has been fixed. Note that the fix applies only to the CREATE statement executed with the fixed version of the server.

CR:748989

CR Number:   748989 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 4755 17 Oct 2013 Fixed Description The cloud infrastructure would have always returned an error if the AlterCloud task was used to attempt to set a different set of secure features. This problem has now been fixed.

CR:749074

CR Number:   749074 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1705 17 Oct 2013 Fixed Description If the Data Source utility (dbdsn) was used with the -or command line option to create a DSN that used the SQL Anywhere Oracle driver, the driver name would have been incorrect. The driver name should be SQL Anywhere <version> - Oracle rather than iAnywhere Solutions <version> - Oracle". This has been fixed.

CR:749081

CR Number:   749081 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1725 06 Nov 2013 Fixed Description The HANA server would have complained with the following error: "unsupported function included: CURRENT_TIMESTAMP is not supported by generated always" when trying to run the MobiLink server setup script file, synchana.sql against a database running on a HANA server, if the HANA server revision was 1.00.64 or later. This problem has now been fixed.

CR:749169

CR Number:   749169 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 1706 21 Oct 2013 Fixed 12.0.1 3995 21 Oct 2013 Fixed Description In some rare cases, attempting to modify a database file after the server using that file had been shut down using the Stop Server utility (dbstop) would have failed with 'permission denied'. For this to have occurred, the server must have been using the external environment (e.g. php). This is a very timing sensitive bug and rarely reproduces. This has been fixed.

CR:749170

CR Number:   749170 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1717 01 Nov 2013 Fixed 12.0.1 4005 01 Nov 2013 Fixed 11.0.1 3061 01 Nov 2013 Fixed Description When invoked with a very large integer value, the hours() function could have returned an incorrect result. For example, hours function invoked with a 12:00 time and a very large integer argument would return a value like 22:44. This has been fixed.

CR:749256

CR Number:   749256 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 1670 21 Oct 2013 Fixed 12.0.1 3977 21 Oct 2013 Fixed Description Strong encryption now achieved using OpenSSL -------------------------------------------- Prior to this change, SQL Anywhere included a Certicom encryption module that provided strong encryption used throughout the software. Now, SQL Anywhere includes an OpenSSL encryption module for the strong encryption. The Certicom encryption module has been removed. Read the following descriptions to determine how you may be impacted by this change. FIPS encryption now requires the private key of an identity file to be encrypted using AES - OpenSSL FIPS supports AES encryption for the private key of an identity file. New servers using the OpenSSL FIPS encryption module will not start when using an identity file that has its private key encrypted with 3DES. You must re-encrypt the identity file using AES. To do this, run a command similar to the following using an upgraded viewcert utility: viewcert -p -o new-file-name -op new-password -ip old-password old-file-name The new and old passwords can be the same. - The sample server identity file (rsaserver.id) and client identity file (rsaclient.id) have been modified so that the private keys are encrypted using AES rather than 3DES. - Versions of the server that use the Certicom encryption module will not start when using an identity file that has its private key encrypted using AES. Trusted root certificate files specified using trusted_certificates do not need to be modified. Self-signed certificates must now have the Certificate Signing attribute set Self-signed certificates must now have the Certificate Signing attribute set when using the identity encryption option (for example, the -x mlsrvXX and -xs dbsrvXX options). To determine if a certificate has the Certificate Signing attribute set, use the viewcert utility and look for the Certificate Signing attribute in the Key Usage portion of the output. If your self-signed certificates do not have the Certificate Signing attribute set, then you must regenerate the certificates. Create Certificate utility (createcert) now uses AES encryption instead of 3DES The Create Certificate utility (createcert) now uses AES rather than 3DES encryption for encrypting the private key in the server identity file. A new option, -3des, has been added to the Create Certificate utility. Use this option when you want to create a 3DES-encrypted server identity file that can be used by both new and old servers. Note that new servers running in FIPS mode cannot start using 3DES-encrypted certificates; however, if you are not running in FIPS mode, then you can use 3DES-encrypted certificates. View Certificate utility (viewcert) now uses AES encryption instead of 3DES The View Certificate utility (viewcert) now uses AES rather than 3DES encryption when you specify the -p option to PEM-encode the output and when you specify the -ip and -op options to set the password. A new option, -3des, has been added to the View Certificate utility to allow you encrypt output and passwords using 3DES instead of AES. Database server now loads the FIPS driver file, dbfipsXX.dll, at startup Previously, the 32-bit Windows database server loaded the FIPS driver file, dbfipsXX.dll, only when needed. Now, the 32-bit Windows database server always attempts to load dbfipsXX.dll at startup, and keeps it loaded for the life of the server. If loading dbfipsXX.dll fails, then an error is returned only when an attempt is made to use FIPS encryption. Deploying FIPS If you are deploying FIPS encryption, then there are new shared libraries to deploy; these files are included in your software. The former files, sbgse2.dll and libsbgse2.so, are no longer installed by the software. The new files to deploy are: - Windows 64-bit: libeay32.dll, ssleay32.dll, and msvcr100.dll - Windows 32-bit: libeay32.dll, ssleay32.dll, and msvcr90.dll - Linux: libcrypto.so and libssl.so Note: On Windows, although 32-bit and 64-bit FIPS-certified OpenSSL libraries for encryption are provided, you must use the 64-bit libraries on a 64-bit system. MobiLink-related changes and information Connecting to a MobiLink server using client-side certificates now requires the Digital Signature certificate attribute to be set TLS/SSL connections to a MobiLink server using client-side certificates now require the client-side certificate to have the Digital Signature attribute set. If the attribute is not set, then the connection will fail. To determine if a certificate has the Digital Signature attribute set, use the View Certificate utility (viewcert) and look for the Digital Signature attribute in the Key Usage portion of the output. If your client-side certificates do not have the Digital Signature attribute set, then you must regenerate the certificates. FIPS-based end-to-end encryption now requires the private key to be encrypted using AES If the private key file provided to a MobiLink server by the e2ee_private_key file option of the x command-line option is encoded using 3DES and you are running in FIPS mode, then the private key file needs to be regenerated with the private key encrypted using AES. How to update a MobiLink deployment that uses non-FIPS TLS/SSL (includes HTTPS) and client-side certificates 1. If your client-side identity certificates do not have the Digital Signature attribute set and the client connects directly to the MobiLink server, then you must regenerate and deploy client-side certificates with the Digital Signature attribute set. 2. Update the server-side binaries. 3. Update the client-side binaries. How to update a MobiLink deployment that uses FIPS, TLS/SSL (includes HTTPS) and client-side certificates These steps update the client identity certificates twice if the Digital Signature attribute is missing from client-side identity certificates. This procedure can make the update less disruptive because synchronizations can continue without having to coordinate the client-side and server-side updates to occur at the same time. 1. If your current client-side identity certificates do not have the Digital Signature attribute set and the client connects directly to the MobiLink server, then you must regenerate and deploy client-side certificates with the Digital Signature attribute set. 2. Update the server-side binaries (remembering to include the new FIPS driver files) and deploy server identity certificates with AES-encrypted private keys. 3. Update the client-side binaries (remembering to include the new FIPS driver files) and deploy client identity certificates with AES-encrypted private keys. How to update a MobiLink deployment that uses FIPS and end-to-end encryption 1. Regenerate the primary key file referenced by the e2ee_private_key encryption option. 2. Shut down the MobiLink server. 3. Update the MobiLink server binaries, remembering to include the new required FIPS driver files. 4. Change the e2ee_private_key option to point to the new private key file (or replace the old file), updating the e2ee_private_key_password, if required. 5. Restart the MobiLink server. Note, connecting to and creating a MobiLink server resource in the 32-bit Windows SA Monitor that will use FIPS encryption to connect to the MobiLink server, may fail with the error, Failed to load library mlcrsafips12.dll. To work around this, you can either not use FIPS encryption, or use 64-bit SA Monitor. Similarly, connecting to a database server from 32-bit DBISQL, DBConsole, or Sybase Central using FIPS encryption, may also fail with the error, Failed to load library mlcrsafips12.dll. To work around this problems, you can either not use FIPS encryption, or use 64-bit client software.

CR:749295

CR Number:   749295 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 1709 22 Oct 2013 Fixed 12.0.1 3996 22 Oct 2013 Fixed 11.0.1 3057 22 Oct 2013 Fixed Description The Dispose function of SATransaction did not automatically do a rollback. This nhas now been corrected.

CR:749387

CR Number:   749387 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 1710 23 Oct 2013 Fixed 12.0.1 3997 23 Oct 2013 Fixed Description Under certain rare circumstances the server could have become deadlocked. For this to have occurred there must be a table continually undergoing many insertions and deletions. This has been addressed.

CR:749407

CR Number:   749407 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1712 25 Oct 2013 Fixed 12.0.1 3998 25 Oct 2013 Fixed Description If the connection between the MobiLink Notifier and the consolidated database had been disconnected, it was possible for the MobiLink Notifier to have failed to re-connect to the consolidated database. This has now been fixed. A work around to the issue is to restart the MobiLink Server.

CR:749465

CR Number:   749465 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) 12.0.1 3994 23 Oct 2013 Fixed 16.0.0 1691 23 Oct 2013 Fixed Description Previously, an Oracle JRE was shipped with the software for use by clients. Now, the SAP JRE is shipped instead. Upgrading overwrites the JRE directory (%SQLANY16%\binXX\jre170) and its subdirectories. If you are using certificates, then your certificate store (%SQLANY16%\binXX\jre170\lib\security\cacerts) is overwritten, including your certificates. Similarly, fonts you added to the %SQLANY16%\binXX\jre170\lib\fonts\fallback directory to help display characters in the administration tools may be lost. To minimize upgrading steps with regards to the JRE change, create a backup copy of the JRE directory and all of its subdirectories before you upgrade so that you can refer to or restore files (such as cacerts) from the backup, as needed. To restore settings, use the java_vm_options option (SQL Anywhere), and/or the -sl java option (MobiLink) to optimize your Java VM startup settings.

CR:749484

CR Number:   749484 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 1719 01 Nov 2013 Fixed 12.0.1 4004 01 Nov 2013 Fixed Description In rare cases, after a log rename on the primary, a mirror or copy node could have stopped writing and applying changes. In order for this to have occurred, all of the following conditions must have applied: - the mirror or copy node must have been fairly recently started and requesting log pages (in the case of the mirror, not yet synchronized) - the mirror or copy node must have been writing pages from the primary's current log file - the primary log file was renamed - something (such as a virus scanner) must have accessed the renamed log on the primary (or parent), preventing the primary from opening the file when the mirror or copy node requested pages from it This has been fixed so that the primary or parent will attempt to open the renamed log several times before failing. If the file open still fails after multiple attempts, the primary will display the message "Database "<database-name>" mirroring: failure when opening log file <file-name> for remote server <server-name>" and the mirror or copy node will display the message "Database "<database-name>" mirroring: database is not compatible with primary; files must be replaced" and shut down the database.

CR:749610

CR Number:   749610 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 1712 24 Oct 2013 Fixed Description When the Interactive SQL utility was run on Japanese or Chinese Linux, the list of categories in the "Options" window was sized so narrow that the names of the categories were not displayed at all. This has now been corrected. Note, the same sizing issue also occurred with the Options window of the SQL Anywhere Console utility.

CR:749622

CR Number:   749622 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 1713 25 Oct 2013 Fixed 12.0.1 4000 25 Oct 2013 Fixed Description If an archive backup was corrupt in a specific way, it was possible for the database server to crash when attempting to restore it. This has been fixed.

CR:749628

CR Number:   749628 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 1712 25 Oct 2013 Fixed Description During execution of a Validate statement the server would have taken a data lock on the primary key table of any foreign keys of the table being validated. This has been fixed.

CR:749714

CR Number:   749714 Product Name:   SQL Remote for SQL Anywhere Product Component:   Database Tools Interface Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1716 01 Nov 2013 Fixed Description If the SET REMOTE OPTION statement had been used to store message control parameters in the database, it was possible for SQL Remote to have failed to gather the message control parameters from the database in very rare circumstances. The user would typically be prompted with a dialog box to fill in the message control parameters, and all the parameters would be blank. If the message control parameters were manually entered in the dialog, SQL Remote would succeed. This has now been fixed.