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

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

CR:731821

CR Number:   731821 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 3855 11 Feb 2013 Fixed Description If a database was stopped when its maintenance plan was executed, the database would not have been backed up. This has been fixed for full backups. Incremental backups will not be created for stopped databases.

CR:731823

CR Number:   731823 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1439 08 Feb 2013 Fixed 12.0.1 3855 08 Feb 2013 Fixed Description Calling the ODBC function SQLGetInfo to retrieve the version of the ODBC driver (i.e. SQLGetInfo( dbc, SQL_DRIVER_VER, ?) would have returned a string that did not include the build number of the driver. This has been corrected so that the string now contains the build number. For version 12.0.1, the string returned was ?2.00.0001? As of this change, the value returned is ?2.01.xxxx?where xxxx is the build number.

CR:731843

CR Number:   731843 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 1440 11 Feb 2013 Fixed Description The OData server could have failed to start because one of the ports (shutdown or server port) could not be used, but the port number was not included in the error message. This has been corrected.

CR:731886

CR Number:   731886 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 1443 13 Feb 2013 Fixed Description The OData server could have started and reported that it was listening on a port that was already in use. This has been fixed.

CR:731939

CR Number:   731939 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 1446 15 Feb 2013 Fixed 12.0.1 3858 15 Feb 2013 Fixed Description Binary values could have been unexpectedly truncated when being displayed to a console window, or in Interactive SQL if the program was configured to display result sets as text. This has been fixed.

CR:731940

CR Number:   731940 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) Description If a database was stopped when its maintenance plan was executed, the database would not have been backed up. This has been fixed for full backups. Incremental backups will not be created for stopped databases.

CR:731945

CR Number:   731945 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 1443 11 Feb 2013 Fixed Description The Fast Launcher feature of Interactive SQL and Sybase Central has an option to automatically terminate the Fast Launcher process if the program is not used for some number of minutes. The mechanism for terminating the process could have failed, leaving running, but unused processes, which were visible in the Windows Task Manager. This has been fixed.

CR:731965

CR Number:   731965 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 1443 12 Feb 2013 Fixed Description If a user ID and an encrypted password was given on the Interactive SQL utility's command line, the "Connect" dialog would have always opened, even if the user ID and password were sufficient to open a connection. This has been fixed. Now, Interactive SQL will attempt to open the connection with the given connection parameters.

CR:731978

CR Number:   731978 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1444 12 Feb 2013 Fixed Description ODBC (and JDBC) escape sequence support has been enhanced to include the following functions. {fn TIMESTAMPADD(<interval>, <integer-expr>, <timestamp-expr>)} Returns the timestamp calculated by adding <integer-expr> intervals of type <interval> to <timestamp-expr>. Valid values of <interval> are shown below. {fn TIMESTAMPDIFF(<interval>, <timestamp-expr1>, <timestamp-expr2>)} Returns the integer number of intervals of type <interval> by which <timestamp-expr2> is greater than <timestamp-expr1>. Valid values of <interval> are shown below. These escape functions are mapped directly to the SQL Anywhere DATEADD/DATEDIFF functions. The <interval> type can be one of the following: <interval> SQL Anywhere DATEADD/DATEDIFF date-part mapping ========================= ========================================== SQL_TSI_YEAR YEAR SQL_TSI_QUARTER QUARTER SQL_TSI_MONTH MONTH SQL_TSI_WEEK WEEK SQL_TSI_DAY DAY SQL_TSI_HOUR HOUR SQL_TSI_MINUTE MINUTE SQL_TSI_SECOND SECOND SQL_TSI_FRAC_SECOND MICROSECOND Examples: // Number of days in February, 2013 SELECT {fn TIMESTAMPDIFF(SQL_TSI_DAY, '2013-02-01T00:00:00', '2013-03-01T00:00:00' )} 28 // Timestamp for 28 days after February 1, 2013 SELECT {fn TIMESTAMPADD(SQL_TSI_DAY, 28, '2013-02-01T00:00:00' )} 2013-03-01 00:00:00.000000

CR:732114

CR Number:   732114 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 1595 05 Jul 2013 Fixed 12.0.1 3933 05 Jul 2013 Fixed Description The first insert of a blob into a table after the database was started may have taken longer under the following conditions: - the blob to insert was longer than its column INLINE value - the table contained a large number of blobs that were longer than about 8 database pages (blobs with blob index) - the columns containing these blobs were created with a blob index (default) - large parts of the table were not in cache This has been fixed. To work around the problem the blob indexes can be dropped by running the following statement for all long varchar or binary columns with blobs longer than 8 pages: alter table <table-name> alter <columns-name> no index To fix the problem in existing databases rebuild the database or drop and recreate the blob index by running ALTER TABLE. This must be done with a fixed version of the server and only on table columns with above conditions.

CR:732156

CR Number:   732156 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 1445 15 Feb 2013 Fixed 12.0.1 3857 15 Feb 2013 Fixed 11.0.1 2942 15 Feb 2013 Fixed Description Validating a database on a server with concurrent activity could have resulted in failed assertions, or a server crash. This has now been fixed.

CR:732247

CR Number:   732247 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 1447 15 Feb 2013 Fixed 12.0.1 3858 15 Feb 2013 Fixed Description In rare timing dependent cases, if the primary server was stopped, the mirror server could have failed to take over as the new primary server. This has been fixed.

CR:732338

CR Number:   732338 Product Name:   SQL Anywhere Product Component:   Documentation Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1447 15 Feb 2013 Fixed Description Feature selection/de-selection switches for the setup.exe command-line are now as follows: Switch: Feature: SERVER64 SQL Anywhere Server (64-bit) CLIENT64 SQL Anywhere Client (64-bit) SERVER32 SQL Anywhere Server (32-bit) CLIENT32 SQL Anywhere Client (32-bit) MOBILE SQL Anywhere for Windows Mobile UL UltraLite ML64 MobiLink (64-bit) ML32 MobiLink (32-bit) SR64 SQL Remote (64-bit) SR32 SQL Remote (32-bit) AT64 Administration Tools (64-bit) AT32 Administration Tools (32-bit) SM64 SQL Anywhere Monitor (64-bit) SM32 SQL Anywhere Monitor (32-bit) RS64 Relay Server (64-bit) SAMPLES Samples FIPS FIPS-approved Strong Encryption CAC CAC Authentication HA High Availability IM In-Memory Mode SON Read-only scale-out Server and Client features are now separately selectable in both 64-bit and 32-bit installs. The following features have been removed: ECC Strong Encryption, QAnywhere, and Relay Server (32-bit). See also the Comments section of the following DocCommentXchange page: http://dcx.sybase.com/index.html#sa160/en/dbprogramming/using-silent-install-deploy.html*d5e50990

CR:732453

CR Number:   732453 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 1477 11 Mar 2013 Fixed 12.0.1 3870 11 Mar 2013 Fixed 11.0.1 2954 11 Mar 2013 Fixed Description If an application made a Java External Environment call to a Java method that made server side requests, then the Java External Environment may have hung when the Java method created or prepared a large number of server-side statements but did not explicitly close statements that were no longer needed. This problem has now been fixed.

CR:732565

CR Number:   732565 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1861 25 Mar 2014 Fixed 12.0.1 4090 25 Mar 2014 Fixed Description MSI installs generated using the Deployment wizard would have always contained the same upgradecode property. This was causing the behavior that installing a newer version of SQL Anywhere would cause the older version to be uninstalled. This has been fixed by changing the upgradecode property to a distinct code for each major revision of SQL Anywhere.

CR:732583

CR Number:   732583 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 1451 19 Feb 2013 Fixed Description The system procedure sp_parse_json() would not have accepted quoted strings containing the characters ?:{}? This has been fixed, these characters are now accepted. Note that SQLAnywhere does not permit the characters [?or ]?inside identifiers, and so it follows that these will not be accepted in JSON quoted strings. Also, sp_parse_json() would have accepted bare pairs that were not in a row. This has been fixed to match with JSON standards. For example, the following would not have given an error, but is now no longer accepted: call sp_parse_json('tvar','a:b'); The FOR JSON clause would have escaped the forward slash character (?? in double quoted text. This has been fixed and forward slashes will no longer be escaped.

CR:732584

CR Number:   732584 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 1451 19 Feb 2013 Fixed 12.0.1 3860 19 Feb 2013 Fixed Description When editing a binary table value in either the Interactive SQL utility, or Sybase Central, an assertion error would have been reported if the existing value was not null. This has been fixed.

CR:732594

CR Number:   732594 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 1451 19 Feb 2013 Fixed Description The "Plan Viewer" menu item could have been incorrectly disabled if there had not yet been a connection to a database. This has been fixed.

CR:732615

CR Number:   732615 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 1451 19 Feb 2013 Fixed Description On 64-bit systems, the feature selection option for the 32-bit server feature would not have installed the feature when set to 1 (i.e., SERVER32=1). This has been fixed.

CR:732617

CR Number:   732617 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 1451 19 Feb 2013 Fixed Description It was not possible to cancel statements which contained a brace character ( { or } ), even if the brace was in a comment. This has been fixed so that such statements can now be canceled.

CR:732727

CR Number:   732727 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 1453 22 Feb 2013 Fixed Description Under rare circumstances, executing a stored procedure call could have crashed the server. This has been fixed.

CR:732730

CR Number:   732730 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 1452 22 Feb 2013 Fixed Description Under some circumstances, the array concatenation operator could have failed to evaluate correctly. This has been fixed.

CR:732731

CR Number:   732731 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 1452 22 Feb 2013 Fixed Description Issuing a CALL PROCEDURE statement from a client where the procedure accepted a ROW or ARRAY argument, but did not have one in its result set, could have failed, either with SQLCODE -1599 (Invalid use of collection type), or (on ODBC with smart describing enabled), by disconnecting the client. This has been fixed. A workaround is to put the procedure in the FROM clause of a SELECT statement, rather than call it immediately.

CR:732736

CR Number:   732736 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 3859 25 Feb 2013 Fixed Description If the StopDatabase or StopDatabaseCopy parameter was unconditionally set to 0, and user connections existed at the time of task invocation, the database or database copy would have stopped. This has been fixed.

CR:732743

CR Number:   732743 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1848 22 Feb 2013 Fixed 12.0.1 3860 22 Feb 2013 Fixed 11.0.1 2945 22 Feb 2013 Fixed Description Original description for Engineering case 706876: A Microsoft Data Link Error could have occurred with newer versions of Microsoft software when using the SQL Anywhere OLE DB provider. When the Test Connection button was clicked, the following message would have been displayed when the error occurred: Test connection failed because not all properties can be set. Window Handle (BAD VALUE) Continue with test connection? [Yes] [No] The message was informational only and Yes can be clicked. If the credentials and other connection information were correct, the connection succeeded. This problem has been fixed. Instead of returning a NULL window handle to the Microsoft software, the OLE DB Window Handle property is now marked as unsupported, which removes the warning message. === The solution to this problem was incorrect. Some applications require support for the Window Handle property and terminate if not supported (e.g., ROWSETVIEWER application). The problem has been corrected. The Window Handle property value was improperly described as 32-bit in a 64-bit application.

CR:732745

CR Number:   732745 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 1471 05 Mar 2013 Fixed 12.0.1 3867 05 Mar 2013 Fixed 11.0.1 2952 05 Mar 2013 Fixed Description If a SELECT statement with an INTO clause contained a variable in the select list, then the temporary table was created with a not-nullable or nullable column definition depending on the value of the variable. This has been fixed. The column definition will now always be nullable in this context.

CR:732853

CR Number:   732853 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1453 22 Feb 2013 Fixed 12.0.1 3861 22 Feb 2013 Fixed 11.0.1 2946 22 Feb 2013 Fixed Description Attempting to create a Mobilink project using Sybase Central on a 64-bit platform could in some cases have caused Sybase Central to crash. This problem was most noticeable on Solaris and Mac platforms. The problem has now been fixed.

CR:732857

CR Number:   732857 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1451 22 Feb 2013 Fixed Description The samonitor.bat and run_migrator.cmd files may not have been updated by a support package. This has been fixed.

CR:732943

CR Number:   732943 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 1452 22 Feb 2013 Fixed Description Various batch and jdp* files may not have been updated by a support package. This has been fixed.

CR:732957

CR Number:   732957 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3861 22 Feb 2013 Fixed Description One of the Relay Server Outbound Enabler's debug messages (-v 4) "Successfully retrieved relay servers peer list.." was logged before the RSOE tried to read the list. Thus it was misleading and could have lead to an incorrect diagnosis. This fix is simply to re-word the message to "Successfully posted peer list request..".

CR:732958

CR Number:   732958 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 1453 22 Feb 2013 Fixed Description The existing affinity flag in the Relay Server Record has been extended to carry a value of x?when the Relay Server told the client to expire the affinity cookie. This can be useful for troubleshooting.

CR:732959

CR Number:   732959 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 1453 22 Feb 2013 Fixed 12.0.1 3861 22 Feb 2013 Fixed Description A pinpointed status page may have mistakenly report that the server was not found when IAS-RS-SERVER was not the last parameter in the URL query. This has been corrected.

CR:732975

CR Number:   732975 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1453 22 Feb 2013 Fixed 12.0.1 3862 22 Feb 2013 Fixed Description The Apache Quick Setup script contained some bash specific syntax that caused errors when run on Linux systems running Ubuntu. Ubuntu uses dash, not bash, as the default shell interpreter. This has been fixed.

CR:733096

CR Number:   733096 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 1453 26 Feb 2013 Fixed Description OData filters running against SQL Anywhere databases, using startswith(), substringof() and indexof(), with long search strings would have returned nothing. To correct this, search strings are now restricted to 254 bytes for SQL Anywhere databases. If longer strings are supplied, searches will only use the first 254 bytes. This restriction does not apply to OData queries against ASE databases.

CR:733155

CR Number:   733155 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1472 12 Mar 2013 Fixed 12.0.1 3868 12 Mar 2013 Fixed Description During silent installs of a SQL Anywhere Monitor SP, the Migration tools progress window was being displayed. This has been fixed so that the progress window is no longer displayed during a silent install.

CR:733171

CR Number:   733171 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 1453 27 Feb 2013 Fixed 12.0.1 3864 27 Feb 2013 Fixed Description The Relay Server provided no option to inject the X-Original-URL header. This has been fixed by injecting the header whenever the original request didnt contain such a header. The injected header value is URL-encoded.

CR:733174

CR Number:   733174 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 1451 26 Feb 2013 Fixed Description When the test window in the MobiLink plug-in is opened, it first deploys the synchronization model to the consolidated database and to a newly created remote database. In the past, changes were made directly to the databases to prepare for synchronization. This behavior is now changed so that SQL files are generated containing the changes to be made. The SQL files are then automatically applied to the databases. This is consistent with the way deployment is handled when the deployment wizard is used. This should result in no user visible change in behavior, but it will ensure that going forward behavior seen when testing a synchronization model in the test window is consistent with that seen when the model is actually deployed using the deployment wizard.

CR:733180

CR Number:   733180 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 1453 26 Feb 2013 Fixed Description In the MobiLink plug-in, the popup menu for a synchronization model now contains a new item, Duplicate? This item creates a copy of the synchronization model in the same project. The name the user provides is used for the name of the copy, as well as the script version and publication name values of the new synchronization model. This feature is useful, when there is a working synchronization system and a copy of it is required as a starting place for making the next version of the system.

CR:733181

CR Number:   733181 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 1453 26 Feb 2013 Fixed 12.0.1 3864 26 Feb 2013 Fixed Description When executing a statement with a parallel execution strategy, it was possible for the statement to fail to complete with an error such as the following: All threads are blocked [-307] ['40W06'] This problem was more likely to occur with a UNION query where multiple branches could use parallel execution. This problem has now been fixed.

CR:733306

CR Number:   733306 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 1546 15 May 2013 Fixed 12.0.1 3902 15 May 2013 Fixed 11.0.1 2985 15 May 2013 Fixed Description The server would have returned the error "Correlation name ... not found" for a query when the following conditions were true: - the query contained a proxy table and a nested query block with an outer reference - the nested query block used a view with a non-flattable select statement - the outer reference in the nested query block could have been pushed into the select statement of the view For example, in the following query T1 is a proxy and would have returned the error "Correlation name 'V0' not found". create view V1 as select 2 as col1 union select 1; select ( select col1 from V1 where col1 = V0.c21 ) as D from T2 V0, T1; This has been fixed.

CR:733309

CR Number:   733309 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1462 28 Feb 2013 Fixed 12.0.1 3864 28 Feb 2013 Fixed Description If an UltraLite application placed a cursor on a row and then moved to before the first row and then back to that row again, the row may have been skipped the second time if the row was updated while the cursor was positioned before the first row. This has been fixed.

CR:733313

CR Number:   733313 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 1462 28 Feb 2013 Fixed 12.0.1 3864 28 Feb 2013 Fixed 11.0.1 2948 28 Feb 2013 Fixed Description The mirror partner server in a mirroring setup may have failed to take over immediately as primary, and instead restarted, when the primary mirrored database became unavailable but the server was still running. This could have happened when the primary mirror server was shutting down, or if the STOP DATABASE?statement has been used on the primary server. This has been fixed.

CR:733438

CR Number:   733438 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 1463 01 Mar 2013 Fixed Description The OData Producer could not access metadata of a SQL Anywhere table (and therefore not do any operations on it) when it, as a result of the user connecting, could only view a subset of the columns. For example, the table ColumnPerm is defined below as owned by dba and user httpAuthUser3 is granted select on only the id and v1 columns CREATE TABLE dba.ColumnPerm( id INTEGER NOT NULL DEFAULT AUTOINCREMENT, v1 VARCHAR(128) NOT NULL, v2 VARCHAR(128) NOT NULL, PRIMARY KEY( id ) ) go GRANT SELECT( id, v1 ) ON dba.ColumnPerm to httpAuthUser3 go This has been fixed. When an OData Producer connects using httpAuthUser3 (in the example above), it will see meta data for table ColumnPerm with columns id and v1 (but not v2).

CR:733443

CR Number:   733443 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1463 28 Feb 2013 Fixed 12.0.1 3865 28 Feb 2013 Fixed Description Building the PHP external environment using phpize, or by integrating into the PHP source code, would have failed. On version 16, it will fail to find libdblib at the configure stage. On both versions, it will fail to produce a useable PHP module. This has been fixed.

CR:733469

CR Number:   733469 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 1463 01 Mar 2013 Fixed Description The automatic text completer used in the Interactive SQL utility could have behaved incorrectly in a CREATE TRIGGER statement. The following have been fixed: - When suggesting SQL statements, "CREATE TRIGGER" could have appeared in the list of suggestions twice. - When writing a CREATE TRIGGER statement, the text completer would have suggested only "CREATE TRIGGER" statements rather than keywords that matched what was typed so far. - Only SQL keywords and owner names were suggested. Now, table names are also suggested. Issues related to other types of CREATE statements have been fixed: - CREATE ROLES and CREATE LDAP SERVER statements were never suggested. They are now suggested where appropriate. - If the second token in a CREATE statement was misspelled the completer would have suggested only statements which started with the keyword CREATE. Pressing Enter would then have replaced the entire statement text with one of the CREATE statements, which was seldom the user's intent.

CR:733471

CR Number:   733471 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 1463 01 Mar 2013 Fixed 12.0.1 3865 01 Mar 2013 Fixed Description The Outbound Enabler was performing unnecessary operations when an internal restart was caused by an up-channel failure. This change eliminates the unnecessary operations, so recovery time, and clarity in logged operations, are improved.

CR:733583

CR Number:   733583 Product Name:   MobiLink Product Component:   MobiLink Agent Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1464 01 Mar 2013 Fixed 12.0.1 3865 01 Mar 2013 Fixed Description The MobiLink Agent for central administration of remote databases could have executed a given task ID concurrently if the task was running on a schedule and also was server-initiated. This has been fixed. Although tasks may run concurrently in general, only one instance of a given task ID should be executing at any given time.

CR:733645

CR Number:   733645 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 1469 04 Mar 2013 Fixed Description The Precision and Scale attributes for Edm.Decimal properties in the metadata document may have incorrectly displayed values outside of the allowed range for Edm.Decimals if the underlying DECIMAL or NUMERIC column used a precision greater than 58, or a scale greater than 29 (the maximums as defined in the OData spec). This has been fixed. Note that this is only an issue in the metadata document itself. The actual values for Edm.Decimal properties are enforced to be within the allowed range as defined in the OData spec.

CR:733726

CR Number:   733726 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 1469 04 Mar 2013 Fixed 12.0.1 3866 04 Mar 2013 Fixed 11.0.1 2951 04 Mar 2013 Fixed Description If an application using the SQL Anywhere JDBC Driver failed to explicitly close all open connections before attempting to exit, then there was a chance the Java VM would have crashed. This was most noticeable on Unix platforms. This problem has now been fixed.

CR:733902

CR Number:   733902 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) 12.0.1 3895 28 May 2013 Fixed Description The ADO.NET provider for .NET 4.0 was requiring assemblies from .NET 4.5 and would not run properly. This has now been fixed.

CR:733905

CR Number:   733905 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 1471 05 Mar 2013 Fixed 12.0.1 3867 05 Mar 2013 Fixed Description Attempting to export a result set which contained character data to a Microsoft Access database would have failed with a message saying that 'there is no data type in the destination database that corresponds to "char".' This has been fixed.

CR:733912

CR Number:   733912 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1753 05 Dec 2013 Fixed 12.0.1 4028 05 Dec 2013 Fixed Description The File Hiding utility (dbfhide) would have crashed if an input file was larger than 65528 (64k-8) bytes. This has been fixed so that an error is now displayed if the file is too large.

CR:733915

CR Number:   733915 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 1471 05 Mar 2013 Fixed 12.0.1 3867 05 Mar 2013 Fixed Description When installing sub-components in silent mode, for example with: setup -silent ?-install sqlany64,sqlanyclnt32 the installer may have given an error like: The following option names are invalid or are not exposed by the registration key provided: sqlanyclnt32 sqlany64 Another symptom of the same problem could be seen using the -list_packages switch, for example: setup ?-list_packages would have output garbled messages. This has been fixed.

CR:733922

CR Number:   733922 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1471 05 Mar 2013 Fixed 12.0.1 3867 05 Mar 2013 Fixed 11.0.1 2952 05 Mar 2013 Fixed Description When run on Unix systems, the uninstaller always returned an error code of 1. This has been fixed.

CR:733923

CR Number:   733923 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3867 07 Mar 2013 Fixed 16.0.0 1471 07 Mar 2013 Fixed Description The Additional Connection Parameters on the Advanced page of the ODBC configuration dialog is used to specify rarely used connection parameters that do not appear on other pages of the wizard. The problem was that once a parameter was added in this page, it could not have been removed again. The value of the parameter could have been modified, but could only be deleted by editing it directly in the registry or by recreating the datasource. This problem has been fixed.

CR:734038

CR Number:   734038 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 1473 11 Mar 2013 Fixed 12.0.1 3869 11 Mar 2013 Fixed Description The database property TimeWithoutClientConnection has been added. The description for this database property is: Returns the elapsed time in seconds since a CmdSeq or TDS client connection to the database existed. If there has not been a CmdSeq or TDS connection since the database started then the time since the database started is returned. If one or more CmdSeq or TDS connections are currently connected, 0 is returned.

CR:734042

CR Number:   734042 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 1471 06 Mar 2013 Fixed 12.0.1 3867 06 Mar 2013 Fixed Description Query plans containing a HashGroupBy operator could have under-performed in some cases. This was only possible when there were a large number of groups (~10,000 or more) and where the data types of the aggregate functions included strings, bit vectors, numerics, or other BLOBs. This has now been fixed.

CR:734049

CR Number:   734049 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 1470 06 Mar 2013 Fixed 12.0.1 3866 06 Mar 2013 Fixed 11.0.1 2952 06 Mar 2013 Fixed Description If the trigger definition resulting from ALTER TRIGGER statement execution conflicted with an existing trigger, the original trigger could have been deleted, and a wrong error returned. This has been fixed. This change also introduces a change in the algorithm used to decide the order of firing triggers when an ORDER clause is not specified, or multiple triggers with the same order and combination of events were created. For example, this may change the order in which triggers created with UPDATE ORDER 2? UPDATE, DELETE ORDER 2?and UPDATE OF <col> ORDER 2?are fired. Note that documentation explicitly recommends specifying different ORDER values for triggers with the same event. If your database contains such sets of triggers, and the order of firing is important, please alter the triggers to reorder them accordingly. In general, both UPDATE ORDER 1 and UPDATE OF <col> ORDER 1 triggers will fire before any UPDATE ?ORDER 2 triggers are fired. A unique ordering between UPDATE and UPDATE OF <col> triggers is still recommended.

CR:734068

CR Number:   734068 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 1472 07 Mar 2013 Fixed Description A MobiLink Server with the integrated Relay Server Outbound Enabler could have crashed on shutdown. This has now been fixed.

CR:734077

CR Number:   734077 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3869 14 Mar 2013 Fixed 11.0.1 2953 14 Mar 2013 Fixed 16.0.0 1479 21 Mar 2013 Fixed Description Synchronizations with large downloads could have been slowed by up to the liveness timeout when using HTTP, if a network interruption occurred. This has been fixed.

CR:734158

CR Number:   734158 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) 12.0.1 3869 07 Mar 2013 Fixed 16.0.0 1473 07 Mar 2013 Fixed Description Executing a batch or stored procedure that contained the ALTER DATABASE UPGRADE statement would very likely have crashed the server. This problem has now been fixed. Note that executing ALTER DATABASE UPGRADE within a batch or stored procedure is not recommended when using SQL Anywhere 16 and up, since the database will automatically be shut down once the upgrade completes.

CR:734160

CR Number:   734160 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 3869 07 Mar 2013 Fixed Description Attempting to perform a cloud UCI would have failed on hosts that had a large number of IPv4 and IPv6 addresses. This problem has now been fixed.

CR:734192

CR Number:   734192 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11 Mar 2013 DEFER Description scc_repository database unable to be started on VM Workaround Description  Set the following environment variable: SA_DISABLE_DIRECTIO=1

CR:734216

CR Number:   734216 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 1474 11 Mar 2013 Fixed Description If a previously recorded profiling session was opened, the database connection IDs for synchronizations displayed in Synchronization properties, or the Details Table, would have be incorrect. The values saved in the database though would have been correct. This has been fixed.

CR:734315

CR Number:   734315 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 1474 11 Mar 2013 Fixed Description In some cases, the Relay Server Outbound Enabler could have failed to startup without giving a specific startup error, but rather a general initialization error. This had been seen specifically in the integrated RSOE case. This has now been fixed in order to better help resolve startup issues.

CR:734471

CR Number:   734471 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1477 12 Mar 2013 Fixed 12.0.1 3870 12 Mar 2013 Fixed Description For queries with LIKE expressions of the form c LIKE <pattern>? where column c is a numeric data type, the UltraLite runtime would have given a SQLE_CONVERSION_ERROR during query execution if column c contained data whose string length when converted to a string was longer than the domain size of the numeric type. For example, if c is of type INTEGER and a row in table t contained the integer 12345, then the query SELECT c FROM t WHERE c LIKE ?%?would have caused a SQLE_CONVERSION_ERROR because the length of the string ?2345?is greater than 4, the domain size of the INTEGER data type. This has been fixed.

CR:734486

CR Number:   734486 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 1474 11 Mar 2013 Fixed 12.0.1 3869 11 Mar 2013 Fixed Description If the computer on which a server is running was improperly configured, it was possible for property(TcpipAddresses?, property(HttpAddresses?, or property(HttpsAddresses? to return a string with multiple consecutive or trailing semicolon characters, eg. ?.2.3.4;1.2.3.5;;1.2.3.6;;;1.2.3.7? This has been fixed.

CR:734566

CR Number:   734566 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 3870 14 Mar 2013 Fixed Description It was possible for the ConvertCloudPartnerToServer task to be reported as cancelled when the task actually ran successfully. This has been fixed. The status of the ConvertCloudPartnerToServer task should now be accurately reported.

CR:734580

CR Number:   734580 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 1477 12 Mar 2013 Fixed Description The Schedules tab for an event could have shown out-of-date information after a schedule was modified, for example, via its property sheet. This has been fixed.

CR:734589

CR Number:   734589 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 1477 14 Mar 2013 Fixed 12.0.1 3870 14 Mar 2013 Fixed Description In a mirroring configuration, it was possible for the primary mirror server to restart sooner than expected when its partner was converted to a copy node. This has been fixed.

CR:734591

CR Number:   734591 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 1477 14 Mar 2013 Fixed 12.0.1 3870 14 Mar 2013 Fixed Description When using the Foreign Key Wizard to create a foreign key, and choosing to add one or more columns to the foreign table for a foreign key that allowed nulls, the foreign key would actually have prohibited nulls if the foreign table was empty. This has been fixed. In addition, the Foreign Key wizard did not display the SQL to create the columns on the last page of the wizard. This has also been fixed.

CR:734626

CR Number:   734626 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 1478 14 Mar 2013 Fixed Description Attempting to switch between Design, Debug or Application Profiling modes while editing a row in the Data tab for a table or view, would have caused Sybase Central to crash. This has been fixed.

CR:734839

CR Number:   734839 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1497 15 Mar 2013 Fixed 12.0.1 3871 15 Mar 2013 Fixed Description In rare circumstances, a MobiLink client using HTTP would have ignored bytes sent down by the MobiLink server during a download and requested that the MobiLink server resend them. This has been fixed.

CR:734841

CR Number:   734841 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1479 07 May 2013 Fixed 12.0.1 3871 07 May 2013 Fixed Description The Relay Server component may have silently missed error messages with old versions of the language resource. This has been fixed by adding a generic error message indicating the resource library is too old.

CR:734960

CR Number:   734960 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 3871 15 Mar 2013 Fixed Description Updating a column, or a set of columns, that contained exactly the same value and had an index defined, could have caused the server to crash. This has been fixed.

CR:734989

CR Number:   734989 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 1480 18 Mar 2013 Fixed Description In a version 12 or later database, attempting to create a Synchronization Subscription by dragging a publication and dropping it on a MobiLink user (or vice versa), or copying a publication and pasting it to a MobiLink user (or vice versa), would have caused Sybase Central to report an error while attempting to create the subscription. This has been fixed.

CR:735005

CR Number:   735005 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 1559 28 May 2013 Fixed Description If the temporary directory used by the server (specified by one of the SATMP, TMP, TMPDIR, or TEMP environment variables) was longer than about 48 characters (differs by specific platform), clients would not have been able to connect to servers over shared memory, they would simply fail to find the server. This has been fixed.

CR:735124

CR Number:   735124 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1485 21 Mar 2013 Fixed 12.0.1 3873 21 Mar 2013 Fixed Description Calling the Entity Framework function CurrentDateTimeOffset would have resulted in a 'procedure not found' server error. This has now been corrected.

CR:735130

CR Number:   735130 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1485 22 Mar 2013 Fixed 12.0.1 3873 22 Mar 2013 Fixed 11.0.1 2957 22 Mar 2013 Fixed Description Using the Entity Framework in an ASP.NET MVC application could have caused a NullRferenceException. The provider was not checking if the Type.FullName was null before calling the method Type.FullName.StartsWith. This has been corrected.

CR:735151

CR Number:   735151 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 1484 19 Mar 2013 Fixed Description Attempting to revoke all object privileges on a given table or view, from a given user or role, could have resulted in a permission denied?error, even when the user did in fact have permission to revoke the granted privileges. This has been fixed.

CR:735216

CR Number:   735216 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 1585 04 Jul 2013 Fixed 12.0.1 3931 04 Jul 2013 Fixed Description In rare situations, queries containing a Merge Join appearing below another Merge Join may have failed assertion 106104: "Field unexpected during compilation". This has been fixed.

CR:735226

CR Number:   735226 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 1484 19 Mar 2013 Fixed 12.0.1 3873 19 Mar 2013 Fixed Description In rare situations in a high availability mirroring setup, it was possible for the primary mirror server to hang while doing a commit if the connection to the partner server was lost. This has been fixed.

CR:735254

CR Number:   735254 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 1484 21 Mar 2013 Fixed Description Selecting View -> Refresh Folder or View -> Refresh All while viewing object privileges would have caused Sybase Central to crash if a row was selected in the object privilege editor. This has been fixed. Note that the problem did not occur if instead the F5 key was used to perform the refresh.

CR:735267

CR Number:   735267 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 1485 21 Mar 2013 Fixed 12.0.1 3873 21 Mar 2013 Fixed 11.0.1 2957 21 Mar 2013 Fixed Description When using Snapshot isolation, a statement-level or transaction-level snapshot may remain active while other transactions completed. Previously, the time to close the snapshot was proportional to O(N^2) for N transactions that completed with the snapshot open. With one hundred thousand transactions, this could have taken over a minute to close a single snapshot. With one million transactions, this could have taken over 100 days to close a single snapshot. During this time, other transactions were not allowed to start or stop. The server would have appeared to be fully busy on a single core. This performance has been improved; for one hundred thousand transactions, the new algorithm completes in 13 milliseconds (compared to 80205 milliseconds previously). Further, it was possible for the server to crash with specific access plans relating to viewing snapshot meta-data. This has also been fixed. A best practice is to ensure that the number of transactions tracked by the server is minimized; for example, by keeping the length of transaction snapshots short (commit as soon as possible). For statement-level snapshots, the snapshot is closed when the statement is closed. For cursors opened WITH HOLD (for example, using ODBC), the snapshot will not be closed when a COMMIT or ROLLBACK is performed; it is delayed until the statement is closed. Best practice recommends closing these cursors promptly. The sa_snapshots() procedure can be used to monitor active snapshots and sa_transactions() monitors transactions being tracked due to snapshots.

CR:735343

CR Number:   735343 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   16.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1484 20 Mar 2013 Fixed Description The MobiLink server now supports consolidated databases running on Sybase IQ 16.0 servers. For the recommended ODBC drivers for Windows and Linux, please visit the following link: http://www.sybase.com/detail?id=1011880 The Row Level Versioning (RLV) feature introduced in Sybase IQ 16.0 has removed the single-writer?limitation. Therefore the IQ 16.0 server now allows multiple connections modifying a RLV enabled table concurrently. Based on testing, the upload would be ten times faster for synchronizations with RLV enabled tables than with RLV disabled tables. Therefore, in order to get better upload performance, all sync tables are recommended to be RLV enabled. However, if there is any table that cannot be RLV enabled, for instance a sync table that contains BLOBs and/or foreign keys, the upload phase must be serialized. This requirement can be achieved, if the begin_upload connection script is written to include or to use the following SQL statement: LOCK TABLE table_name IN WRITE MODE WAIT time_string where table_name is the name of a table that is defined on the IQ store and the time_string gives the maximum time period to lock the table. The table can be as simple as the one defined as: create table coordinate_upload ( c1 int ) It is not required to have any data. If any of the other MobiLink server transactions is required to modify any IQ tables, all of these transactions must be serialized as well. The same logic mentioned above can be used. This technique is considered more efficient than retries on each of the transactions by the MobiLink server.

CR:735344

CR Number:   735344 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 1486 21 Mar 2013 Fixed 12.0.1 3873 21 Mar 2013 Fixed Description After performing a calibration using the ALTER DATABASE CALIBRATE statement, it was possible for queries to execute slowly on the database due to an error in the recorded calibration data. This problem was most likely to happen with faster computers. This problem has been fixed. A workaround is to use ALTER DATABASE RESTORE DEFAULT CALIBRATION?to remove the incorrect calibration data.

CR:735358

CR Number:   735358 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 1485 21 Mar 2013 Fixed 12.0.1 3873 21 Mar 2013 Fixed 11.0.1 2957 21 Mar 2013 Fixed Description In rare situations in a high availability setup with TLS connections, it was possible for the primary server to hang while doing a commit. This is the same fix that was done for Engineering case 674782, but now available on Unix platforms.

CR:735367

CR Number:   735367 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 1485 21 Mar 2013 Fixed 12.0.1 3873 21 Mar 2013 Fixed Description If an application used variables in the USING clause of a remote server, or the AT clause of a proxy table or procedure, then the server would have leaked memory. This problem has now been fixed.

CR:735368

CR Number:   735368 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 1585 21 Mar 2013 Fixed 12.0.1 3873 21 Mar 2013 Fixed Description Selecting and deleting multiple table privileges could have crashed Sybase Central if there were corresponding column privileges. This has been fixed.

CR:735400

CR Number:   735400 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 06 May 2013 Fixed Description Revoking all column privileges for a given table/grantee/grantor combination could have caused another table privilege editor to be opened in an inconsistent state. Specifically, the editor could have initially shown a row that was marked for deletion. This has been fixed.

CR:735452

CR Number:   735452 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 1486 22 Mar 2013 Fixed Description In a mirroring setup, if a copy node lost its connection to its parent, and MaxDisconnectedTime had been specified, it was possible for the server to noticeably exceed the time before shutting down. This has been fixed. The shutdown time should now be much closer to the MaxDisconnectedTime if the copy node is unable to re-establish a connection to its parent, alternate parent, or the primary.

CR:735454

CR Number:   735454 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 1486 22 Mar 2013 Fixed Description When reading an event trace (.etd) file, the Event Trace Data File Management utility (dbmanageetd) did not correctly decode the event severity associated with events in the log. The severity reported by dbmanageetd was incorrect and filtering by severity level (-fl) would not work correctly. This problem has been fixed. Note that the files themselves are correct and only a new dbmanageetd is required to interpret them correctly.

CR:735595

CR Number:   735595 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 1488 25 Mar 2013 Fixed Description Attempting to connect to a database running on a version 7 or earlier server (for the purposes of unloading/reloading the database into a new version 16 database), would have caused Sybase Central to crash. This has been fixed.

CR:735598

CR Number:   735598 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 1488 25 Mar 2013 Fixed Description When using the wizard to create a table, and selecting a dbspace that the user didnt have permissions on, the error wasnt reported until attempting to save the table, at which point the dbspace couldn't be changed because the wizard had already closed. This has been fixed. Now the error is reported immediately when choosing the dbspace in the wizard. Similarly, when using a wizard to create a materialized view, index or text index, if a dbspace was selected that the user didnt have permissions on, then the error wasnt reported until the Finish button was clicked. This has been fixed. Now the error is reported immediately when choosing the dbspace n the wizard.

CR:735599

CR Number:   735599 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 1488 25 Mar 2013 Fixed 12.0.1 3875 25 Mar 2013 Fixed 11.0.1 2959 25 Mar 2013 Fixed Description When duplicating a materialized view, any change to which dbspace it was located would have been ignored. Now the choice of dbspace is no longer given, and the copied materialized view is created in the same dbspace as the original.

CR:735605

CR Number:   735605 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 1489 26 Mar 2013 Fixed Description Opening the Text Configuration Objects folder or the Create Text Index wizard could have resulted in the error Permission denied: you do not have permission to change remarks for "default_char"? This would only have occurred if the default text configuration objects (SYS.default_char and SYS.default_nchar) didnt already exist in the database and the user did not have permission to set a comment on a text configuration object. This has been fixed.

CR:735654

CR Number:   735654 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1491 26 Mar 2013 Fixed 12.0.1 3876 26 Mar 2013 Fixed Description The SAConnection.Open method would have thrown an exception when opening a version 10.0 or 11.0 database connection using the version 12.0 or 16.0 provider. This has now been corrected.

CR:735807

CR Number:   735807 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 1492 01 Apr 2013 Fixed 12.0.1 3876 01 Apr 2013 Fixed Description Closing a pooled connection could have been blocked when the request was from a multi-threaded application. This has been fixed.

CR:735815

CR Number:   735815 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1491 28 Mar 2013 Fixed 12.0.1 3876 28 Mar 2013 Fixed Description Calling the SAConnection.Close method would have thrown an exception when closing pooled version 10.0 and version 11.0 database connections.

CR:735922

CR Number:   735922 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 1492 28 Mar 2013 Fixed Description In the test window of the MobiLink Plug-in, the client log page would have continued to report Synchronization in progress? even when the MobiLink server did not start correctly during a synchronization and the synchronization had failed and was complete. This has been fixed.