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

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

CR:537391

CR Number:   537391 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1433 28 Jul 2008 Fixed 11.0.1 1896 20 Nov 2008 Fixed Description A connection may have held table or row locks even after a DDL statement had failed. This has been fixed.

CR:537399

CR Number:   537399 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) 11.0.0 1431 16 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description The search condition REGEXP, and the system function REGEXP_SUBSTR(), were treating _ (underscore) and % (percent) as meta characters to match any character or any characters respectively. Also, if a caret (^) was in a character class, but not the first character after the open square bracket (for example [a-e^d]), then it was treated as a subtraction character class operator. These behaviours were different than other tools such as Perl, Java, .NET, etc. This has now been fixed so that _ and % are not meta characters for REGEXP and REGEXP_SUBSTR(); and a caret which is not the first character after the open square bracket now matches a caret. The search condition SIMILAR TO has not been changed. For SIMILAR TO, _ matches one character, % matches any number of characters and [a-e^d] matches a, b, c and e.

CR:537555

CR Number:   537555 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1458 11 Aug 2008 Fixed 10.0.1 3743 11 Aug 2008 Fixed 11.0.1 1918 20 Nov 2008 Fixed Description Dropping a table could, in rare circumstances, have caused the server to fail assertion 102806 "Unable to delete row from SYSTABLE". This has been fixed.

CR:537558

CR Number:   537558 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1436 18 Jul 2008 Fixed 10.0.1 3731 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description A side effect of the combined fixes for Engineering cases 533936 and 536335 was to cause Sybase Central to crash when attempting to expand the table tree view in the MobiLink plugin. This problem has now been fixed.

CR:537560

CR Number:   537560 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) 11.0.0 1265 16 Jul 2008 Fixed 10.0.1 3727 16 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description It was possible for calls to DB_Property( 'DriveType' ) on AIX systems to erroneously return "UNKNOWN". A buffer used to enumerate the various mounted filesystems may have been too small. This has been fixed.

CR:537575

CR Number:   537575 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1433 21 Jul 2008 Fixed 11.0.1 1879 20 Nov 2008 Fixed Description Sybase Central would have crashed if it was connected to the utility database and then connected to another database running on the same server. This has been fixed.

CR:537579

CR Number:   537579 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1431 17 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description The QAnywhere client (qaagent) would have silently initialized a new database the first time it was run. This has been fixed so that it now is mandatory to initialize a new database as a QAnywhere message store by running qaagent with -si, as a separate step.

CR:537595

CR Number:   537595 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1431 17 Jul 2008 Fixed 10.0.1 3727 17 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description The changes for Engineering case 534179 introduced a problem where the QAnywhere Server's logging messages could have been output as garbled text. This has now been corrected.

CR:537609

CR Number:   537609 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) 11.0.0 1431 17 Jul 2008 Fixed 10.0.1 3727 17 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description If a synchronization contained tables for which no rows were uploaded or downloaded, the MobiLink server would have allocated more memory than was neccessary. This has been fixed so that the memory usage will be proportional to the number of columns in empty tables multiplied by the number of upload transactions. In tests with 50 concurrent syncs of 200 empty tables with 6 columns per table, the peak memory used by MobiLink server dropped by 178MB, or about 3kB per column. Systems that synchronize many empty tables, or use transactional uploads (i.e. the -tu option on dbmlsync), will see improved performance with this fix.

CR:537610

CR Number:   537610 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) 11.0.0 1432 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description Some queries with an illegal CONTAINS search condition could have caused the server to crash. This has now been fixed.

CR:537616

CR Number:   537616 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1266 17 Jul 2008 Fixed 10.0.1 3727 17 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description Under rare circumstances, the server could have gone into an infinite loop after a non-recurring scheduled event was run. Any attempts to communicate with the database on which the event was scheduled would have blocked. This has been fixed.

CR:537620

CR Number:   537620 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1431 17 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description The sync_request phase time was incorrect in the MobiLink monitor. It was usually 0, but could be negative. This has been fixed.

CR:537747

CR Number:   537747 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1432 17 Jul 2008 Fixed 10.0.1 3728 17 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description If an application used the iAnywhere JDBC driver with either a Microsoft SQL Server, or DB2, ODBC driver, and the application did not explicitly close Statement or PreparedStatement objects, then it was possilbe that the application would have hung at garbage collection time. This problem has now been fixed.

CR:537748

CR Number:   537748 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) 11.0.0 1266 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description When running the server in 'in memory' mode, the server would still have enforced the per-connection temporary space limit, even though no temporary files are used when running in 'in memory' mode. This has been fixed.

CR:537774

CR Number:   537774 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1432 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description Under rare circumstances, clients running on Unix systems, could have crashed on disconnect. This has now been fixed.

CR:537786

CR Number:   537786 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) 11.0.0 1444 21 Jul 2008 Fixed 11.0.1 1903 20 Nov 2008 Fixed Description As of version 11.0.0, DML operations on temporary tables are allowed to have full transactional semantics (i.e. commit and rollback) on read-only databases. However, the support for this feature was not fully enabled. This has been corrected. Additionally, the creation of savepoints for temporary objects on read-only databases is also now supported.

CR:537787

CR Number:   537787 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1432 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description If a C++ application had been created using the DBSync API, it was possible that this application would not have been able to connect to the a MobiLink client started in server mode, if the machine supported IPv6. This has now been fixed.

CR:537800

CR Number:   537800 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1432 18 Jul 2008 Fixed 10.0.1 3729 18 Jul 2008 Fixed 9.0.2 3697 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description If an application executed a remote query with a malformed field or dotted reference in the select list, then it was possible that the server could have crashed. An example of such a query is: select c1.ref(), max( c2 ), c2 from t1 where c1.ref() is a meaningless expression. This problem has now been fixed and a proper error message will be returned to the application.

CR:537804

CR Number:   537804 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) 11.0.0 1432 18 Jul 2008 Fixed 10.0.1 3729 18 Jul 2008 Fixed 9.0.2 3697 18 Jul 2008 Fixed 11.0.1 1891 20 Nov 2008 Fixed Description When the size of a long varchar or long binary column exceeded 32 KB on Windows, or 1 KB on Windows Mobile, the column may not have been read correctly by the OLE DB provider. This problem has been fixed.

CR:537917

CR Number:   537917 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1433 18 Jul 2008 Fixed 10.0.1 3730 18 Jul 2008 Fixed 11.0.1 1892 20 Nov 2008 Fixed Description A download_delete_cursor script that returned NULL and non-NULL values for the primary key columns of a synchronized table would have made the MobiLink client behave erratically: the client could have deleted rows that should not have been deleted, or could have displayed the following error message: SQL statement failed: (100) Row not found This problem has been fixed. The MobiLink server will now complain if a download_delete_cursor returns NULL as well as non-NULL values for the primary key columns of a synchronized table, and will then abort the synchronization. The download_delete_cursor script must return NULL values for all the primary key columns (the MobiLink client will delete all the rows from the corresponding sync table) or non-NULL values (the client will delete specific rows specified by the primary key values).

CR:537923

CR Number:   537923 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) 11.0.0 1433 21 Jul 2008 Fixed 11.0.1 1892 20 Nov 2008 Fixed Description Execution of some queries involving procedure calls could caused a server crash. This is fixed.

CR:537962

CR Number:   537962 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) 11.0.0 1444 28 Jul 2008 Fixed 10.0.1 3735 28 Jul 2008 Fixed 11.0.1 1903 20 Nov 2008 Fixed Description If an error occurred when executing a Java or .NET synchronization script, and operations had been performed on the connection returned from the DBConnectionContext.getConnection method, it was possible for those operations to have been committed to the consolidated database. In order for this to have occurred, the Java or .NET synchronization script would have to have been executed before any SQL scripts were executed in the transaction by the MobiLink Server. As a workaround, a SQL synchronization script that does nothing could be defined that executes at the start of the transaction. For example, define a begin_upload connection event that calls a stored procedure, that does nothing, to prevent a problem in the handle_uploadData event resulting in operations performed in the handle_uploadData event from being accidentally committed. This problem has now been fixed.

CR:537965

CR Number:   537965 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) 10.0.1 3730 23 Jul 2008 Fixed Description Executing a STOP JAVA command may have, in rare circumstances, caused the server to crash. This has been fixed.

CR:538098

CR Number:   538098 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) 11.0.0 1436 21 Jul 2008 Fixed 11.0.1 1895 20 Nov 2008 Fixed Description The space previously used by deleted rows was not being reclaimed and reused on the mirror server of a mirroring system. As a result, the mirror server's database could have grown faster than the database on the primary server. This space would have eventually be reclaimed if the mirror server became the primary server. This has been fixed.

CR:538099

CR Number:   538099 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1436 22 Jul 2008 Fixed 10.0.1 3731 22 Jul 2008 Fixed 9.0.2 3699 22 Jul 2008 Fixed 11.0.1 1895 20 Nov 2008 Fixed Description Attempting to copy a large number of values in the "Results" pane could have caused Interactive SQL (dbisql) to crash. This has been foxed so that an error message is now displayed and the copy is aborted.

CR:538128

CR Number:   538128 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) 11.0.0 1436 22 Jul 2008 Fixed 11.0.1 1895 20 Nov 2008 Fixed Description Attempting to upgrade the mirrored database in a mirroring system, using the Upgrade utility (dbupgrad), or by executing an ALTER DATABASE UPGRADE statement, would have resulted in transaction log entries which could not be replayed on the mirror server. An error will now be given if an upgrade is attempted on a database which is currently being mirrored.

CR:538145

CR Number:   538145 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) 11.0.0 1436 23 Jul 2008 Fixed 11.0.1 1894 20 Nov 2008 Fixed Description MobiLink servers with web edition licenses had an incorrect feature set. This has now been corrected.

CR:538146

CR Number:   538146 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) 11.0.0 1436 22 Jul 2008 Fixed 11.0.1 1895 20 Nov 2008 Fixed Description Under some update patterns, concurrent changes to text indexes created with the IMMEDIATE REFRESH clause, could have caused assertion failure 110400. This has now been fixed.

CR:538156

CR Number:   538156 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3731 23 Jul 2008 Fixed Description Long running MobiLink Monitors could have hang or crashed with a RuntimeException "the monitor doesn't send any-order commands". This has been fixed.

CR:538275

CR Number:   538275 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3702 25 Jul 2008 Fixed Description If a query execution plan contained a Group-by Ordered (GrByO) operator in a particular stylized access plan pattern containing an outer joing, and the group-by node had a string or NUMERIC value in the result, then it was possible for the server to crash while processing the statement. The crash would have depended on the order and values of rows processed by the plan. This has been fixed.

CR:538292

CR Number:   538292 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1459 13 Aug 2008 Fixed 11.0.1 1919 20 Nov 2008 Fixed Description When Sybase Central was used to create a proxy table to a remote table in an ADS database, accessing the proxy table to perform queries or updates would have failed. This problem has now been fixed. It should be noted that in order to use proxy tables to an ADS table, the ADSODBC class must be used. Using the generic ODBC class will continue to cause access problems for ADS proxy tables.

CR:538303

CR Number:   538303 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) 11.0.0 1437 23 Jul 2008 Fixed 10.0.1 3731 23 Jul 2008 Fixed 11.0.1 1896 20 Nov 2008 Fixed Description If while executing an ATTACH TRACING statement, the tracing server was stopped, the server being traced could have crashed. This has been fixed.

CR:538305

CR Number:   538305 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) 11.0.0 1437 23 Jul 2008 Fixed 11.0.1 1896 20 Nov 2008 Fixed Description The server console's checkpoint begin and end messages were not being displayed when the server was run in 'in memory' mode with Checkpoint only (-im c). This has been fixed.

CR:538306

CR Number:   538306 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) 11.0.1 1926 25 Jul 2008 Fixed 11.0.0 1439 25 Nov 2008 Fixed Description If multiple connections executed DDL statements concurrently, then, under very rare circumstances, it was possible for the server to behave incorrectly. This problem has been resolved.

CR:538317

CR Number:   538317 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1437 22 Jul 2008 Fixed 11.0.1 1896 20 Nov 2008 Fixed Description The Windows Mobile Deployment wizard was always writing to sqlany11.cab, rather than the filename specified by the user. This has been fixed.

CR:538324

CR Number:   538324 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1460 13 Aug 2008 Fixed 11.0.1 1920 20 Nov 2008 Fixed Description Attempting to create a table with a varchar(36) column with a default of newid() would have failed with a syntax error. The column could have been later altered to add the newid() default, but the generated default values would have been garbage. These two bugs have now been fixed.

CR:538346

CR Number:   538346 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3699 24 Jul 2008 Fixed Description When the QAnywhere Agent was started for the first time, and another the qaagent to fail to start with an error similar to: InternalError: User 'DBA' has the row in 'ml_qa_global_props_client' locked Source statement: CREATE SYNCHRONIZATION SUBSCRIPTION TO ml_qa_user_group.ml_qa_repository_pub FOR "sender-rules" OPTION sv='ml_qa_2' This has been fixed by now having the QAnywhere Agent acquire exclusive locks on tables involved in the publication, before creating the synchronization subscription.

CR:538347

CR Number:   538347 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) 11.0.0 1438 23 Jul 2008 Fixed 10.0.1 3731 23 Jul 2008 Fixed 11.0.1 1897 20 Nov 2008 Fixed Description If the MobiLink server was started unsuccessfully (i.e invalid parameter, unable to connect to database, invalid stream specified), and no logging option was specified (-o or -ot), then the server would have displayed an error dialog and waited for the shutdown button to be pressed. After waiting about a minute for the manual shutdown, the server could then have crashed. This has been fixed. Note, this problem should only have occurred on systems where a GUI was used.

CR:538480

CR Number:   538480 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1408 25 Jul 2008 Fixed 10.0.1 3698 25 Jul 2008 Fixed 9.0.2 3701 25 Jul 2008 Fixed 11.0.1 1841 20 Nov 2008 Fixed Description In rare circumstances, the server could have crashed while disconnecting if -zl, -zp, sa_server_option( 'RememberLastStatement', 'YES' ) or sa_server_option( 'RememberLastPlan', 'YES' ) were used. This has been fixed.

CR:538484

CR Number:   538484 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3701 25 Jul 2008 Fixed Description The server allows the use of host variables with the INSERT statement, to insert multiple rows into the database in a single request. Under certain circumstances, the server could have crashed when block inserts were executed in the server. This has been fixed so that the server now generates an error message instead in these circumstances.

CR:538547

CR Number:   538547 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) 11.0.0 1438 24 Jul 2008 Fixed 11.0.1 1897 20 Nov 2008 Fixed Description The search conditions SIMILAR TO and REGEXP, and the fuction REGEXP_SUBSTR() could have given incorrect results for some patterns if the string being searched was more than 250 bytes in length. The search string could be 250 bytes in length if it contained as few as 63 characters and the database character set was multi byte (including NCHAR strings). It was possible that a pattern would not have matched a string that it should have. In rare cases the server could even have crashed. This has now been fixed.

CR:538694

CR Number:   538694 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1439 24 Jul 2008 Fixed 10.0.1 3732 24 Jul 2008 Fixed 11.0.1 1898 20 Nov 2008 Fixed Description An application that did not explicitly close Statement, PreparedStatement or CallableStatement objects may, in rare cases, have crashed when closing a Connection object. This problem has now been fixed.

CR:538698

CR Number:   538698 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) 11.0.0 1447 31 Jul 2008 Fixed 11.0.1 1907 20 Nov 2008 Fixed Description The 'tempfilename' property would have returned a value when running in In-Memory mode, even though neither supported In-Memory modes use a temporary file. This has been fixed so that the 'tempfilename' property now returns NULL when the server is running in In-Memory mode.

CR:538700

CR Number:   538700 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1438 24 Jul 2008 Fixed 11.0.1 1896 20 Nov 2008 Fixed Description UltraLiteJ did not work with cookie injecting proxy servers, such as the Relay Server. This has been fixed. Note that on the BlackBerry, the MDS may cache cookies for the devices that go through it, and so UltraLiteJs cookie behaviour may be different from other remotes. In particular, cookies sent to the remote may be cached for longer than the duration of a sync. When using a proxy other than the Relay Server, ensure that the optional cookie fields, defined in RFCs 2109 and 2965 dealing with cookie caching, are properly set, or disable this feature in your MDS. The Relay Server is unaffected by this caching, but other cookie injecting proxies may be affected by it.

CR:538737

CR Number:   538737 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) 11.0.0 1266 25 Jul 2008 Fixed 11.0.1 1898 20 Nov 2008 Fixed Description When a mirror server was started in preferred mode, it was possible for the synchronization between the primary and the mirror to have failed. This has now been fixed.

CR:538743

CR Number:   538743 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1438 24 Jul 2008 Fixed 11.0.1 1897 20 Nov 2008 Fixed Description When attempting to use a MobiLink Java Start class that made use of UltraLiteJ, an error similar to "<Main> [-10150] Linkage error while loading class: 'jdbssint' Error description: 'ianywhere/ultralitej/Configuration'" would have occurred, and the server would have failed to start. The problem was due to class name conflicts, which have been corrected.

CR:538862

CR Number:   538862 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) 11.0.0 1440 25 Jul 2008 Fixed 11.0.1 1899 20 Nov 2008 Fixed Description If ALTER DATABASE UPGRADE was executed twice, using the same connection, the second execution would have failed. The upgrade scripts did not remove some temporary objects used by the scripts. This has been fixed.

CR:538863

CR Number:   538863 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1440 25 Jul 2008 Fixed 11.0.1 1899 20 Nov 2008 Fixed Description The Database Documentation Wizard could have crashed Sybase Central if it ran out of memory. A number of changes have been made to reduce the amount of memory needed to generate documentation, so that it now reports an out-of-memory error and leaves the program in a state where it can safely continue working.

CR:538865

CR Number:   538865 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1266 25 Jul 2008 Fixed 10.0.1 3731 25 Jul 2008 Fixed 11.0.1 1896 20 Nov 2008 Fixed Description Applications using TLS on Mac OS X systems, may have experienced crashes. This has been fixed.

CR:538882

CR Number:   538882 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3704 29 Jul 2008 Fixed Description If the stored procedure debugger was used to trace execution of a procedure containing a variable defined as UNIQUEIDENTIFIER, the value and datatype for the variable would not have been displayed. This has been fixed.

CR:538883

CR Number:   538883 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) 11.0.0 1440 28 Jul 2008 Fixed 10.0.1 3734 28 Jul 2008 Fixed 11.0.1 1900 20 Nov 2008 Fixed Description If the ansi_close_cursors_on_rollback option was set to 'ON', and request logging of plans was enabled, the server could have crashed. This has been fixed.

CR:538904

CR Number:   538904 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1447 31 Jul 2008 Fixed 10.0.1 3737 31 Jul 2008 Fixed 9.0.2 3705 31 Jul 2008 Fixed 11.0.1 1907 20 Nov 2008 Fixed Description If an application using the iAnywhere JDBC driver called the method ResultSet.isLast() when the result set was positioned on the last row, the call would have correctly returned a value of 'True', but the result set position would have been move to be after the last row. The problem has now been fixed. Note, this problem does not occur if the result set is not positioned on the last row.

CR:538912

CR Number:   538912 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1441 28 Jul 2008 Fixed 11.0.1 1900 20 Nov 2008 Fixed Description Right-clicking on a result set, then selecting the item "Copy/Copy Cell" from the menu, would only have copied the cell value if the cell had previously been left-clicked. This has been corrected so that left-clicking is no longer necessary.

CR:538920

CR Number:   538920 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1441 28 Jul 2008 Fixed 11.0.1 1900 20 Nov 2008 Fixed Description The Database Documentation wizard would have reported an unhelpful error message when a user, which was not a member of the SYS group, logged in . The wizard used a number of queries which referenced system tables without the appropritate creator qualifier. This has been fixed.

CR:538931

CR Number:   538931 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) 11.0.0 1442 28 Jul 2008 Fixed 11.0.1 1901 20 Nov 2008 Fixed Description The Create Service Wizard would have provided default paths for 32-bit executables when 64-bit executables were available on a 64-bit version of Windows. This has been corrected so that default paths for 64-bit executables are now provided if they are available; otherwise, default paths for 32-bit executables are provided.

CR:538936

CR Number:   538936 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1442 28 Jul 2008 Fixed 10.0.1 3734 28 Jul 2008 Fixed 11.0.1 1901 21 Nov 2008 Fixed 9.0.2 3922 27 Nov 2009 Fixed Description The Dbmlsync Integration Component could have crashed during a call to the Run method. As well, the OS would sometimes have detected a heap error. This has been fixed.

CR:538953

CR Number:   538953 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) 11.0.0 1441 28 Jul 2008 Fixed 11.0.1 1901 21 Nov 2008 Fixed Description The Relay server may have failed to relay http responses for a several minutes after seeing an rsoe uuid mismatch on down channel connect. This would have been rare, as it required the down channel to be renewed right before an up channel renewal, plus the up channel renewal must have renewed the uuid before the down channel was authenticated. The Relay Server would have eventually detected an error on writing over the failed down channel and would have been able to recover, however http responses or portions of it relayed within that period were lost. This problem has been fixed and a rsoe uuid mismatch should not occur on a down channel unless this is caused by invalid running duplicated instances of the Relay Server with the same backend server identity.

CR:538954

CR Number:   538954 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3727 28 Jul 2008 Fixed Description Server Initiated Synchronizations, using persistent connections, didn't scale well as it required persistent resource per connected client on the backend server, as well as onintermediaries like the Redirector or Relay Server. This limitation may have caused large deployments to require a server farm, which is not supported until version 11.x. Now with this change, an alternative solution is provided based on light weight polling. This alternative is based on a new caching notifier in the MobiLink server, and a client API for polling the notification (MobiLink Lightweight Polling API). The caching notifier refreshes the current set of notifications by executing a request_cursor against the database at a setable frequency. The cache is exposed for clients to poll without involving database access, nor authentication via the same MobiLink server port. Caching notifier A caching notifier is a notifier with a request_cursor that return a result set with 1, 2 or 3 columns. The first column is the key of the notification, the optional second column is the subject of the notification and the optional third column is the content of the notification. A caching notifier doesn't need gateways or tracking information in order to push notifications down to clients. Clients are expected to initiate connection and poll at the cache refresh frequency. Users may define multiple caching notifiers for different business logic, and they can co-exist with other regular or caching notifiers. MLLP API Development resources are found under the following location %SQLANY10%\MobiLink\ListenerSDK\windows\src\mllplib.h %SQLANY10%\MobiLink\ListenerSDK\windows\x86\mllplib.dll %SQLANY10%\MobiLink\ListenerSDK\windows\x86\mllplib.exp %SQLANY10%\MobiLink\ListenerSDK\windows\x86\mllplib.lib (import library for the dll) MLLP client will dynamically load various ML client stream library. Example MLLP client app Please see %SQLANYSH10%\samples\MobiLink\SIS_CarDealer_LP2 Workaround Description  Not quite a workaround.

CR:538963

CR Number:   538963 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) 11.0.0 1444 29 Jul 2008 Fixed 11.0.1 1903 21 Nov 2008 Fixed Description The Relay server was holding on to workers when finished serving Afaria traffic. A new command line option "-af" has been added to the Relay Server Outbound Enabler (rsoe) so that the Relay Server will be notified when the backend server disconnects. The relay server will then abort waiting for the entire content length to be satisfied. Without this option, rsoe will not notifiy the Relay Server when the backend disconnects and a worker in the Relay Server has finished relaying responses from an Afaria server, but will wait for more data until a timeout (default 8 minutes) before exiting. Older Relay Servers are not compatible with this newer rsoe. Newer Relay Server remains backward compatible with an older rsoe though.

CR:539056

CR Number:   539056 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) 11.0.0 1440 28 Jul 2008 Fixed 10.0.1 3734 28 Jul 2008 Fixed 9.0.2 3702 28 Jul 2008 Fixed 11.0.1 1900 21 Nov 2008 Fixed Description For a statement of the form "EXEC <linked_server_name>..dba.myproc", Microsoft SQL Server 2005 passes a statement of the form {?=call "dba"."myproc" } to the SQL Anywhere OLE DB provider. It passes in a single integer parameter for binding with a status of DB_E_UNAVAILABLE. The SQL Anywhere OLE DB provider had always checked the status of parameters and accepted one of DBSTATUS_S_DEFAULT, DBSTATUS_S_ISNULL, or DBSTATUS_S_OK. Any other status was flagged with an error. As such, the above example would have failed with an error. Since the parameter is OUTPUT-only, the status of the parameter can be ignored, as the status for any OUTPUT parameters will be set after the statement has been executed and any OUTPUT parameters will be filled in. The OLE DB provider behaviour has been changed to ignore the incoming status of OUTPUT-only parameters. This allows the EXEC statement to execute successfully.

CR:539077

CR Number:   539077 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1444 29 Jul 2008 Fixed 10.0.1 3735 29 Jul 2008 Fixed 11.0.1 1903 21 Nov 2008 Fixed Description The changes for Engineering case 533936 introduced a problem where calling the JDBC method Statement.cancel() did not work for queries that did not return a result set. This has been fixed.

CR:539085

CR Number:   539085 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1487 31 Jul 2008 Fixed 10.0.1 3761 10 Sep 2008 Fixed 11.0.1 1947 21 Nov 2008 Fixed Description A number of changes have been made to improve the performance of the Interactive SQL utility over networks with high latency. All the changes are related to minimizing the number of server requests.

CR:539091

CR Number:   539091 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) 11.0.0 1266 29 Jul 2008 Fixed 10.0.1 3735 29 Jul 2008 Fixed 11.0.1 1898 21 Nov 2008 Fixed Description The 64-bit server for Sun Solaris performed poorly when executing queries. This has been fixed.

CR:539094

CR Number:   539094 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) 11.0.0 1444 29 Jul 2008 Fixed 10.0.1 3735 29 Jul 2008 Fixed 11.0.1 1903 21 Nov 2008 Fixed Description If an application was using the iAnywhere JDBC driver to generate one or more result sets by making DatabaseMetaData calls, then there was a chance the DatabaseMetaData result sets would not have been garbage collected until connection close time. Note that at most 3 of these result sets would have remained open until connection close. This problem has now been fixed.

CR:539095

CR Number:   539095 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) 11.0.0 1444 28 Jul 2008 Fixed 11.0.1 1903 21 Nov 2008 Fixed Description If a mirroring server was accidentally started a second time, the second instance could have crashed after displaying an error. This has been fixed.

CR:539106

CR Number:   539106 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) 11.0.0 1505 25 Sep 2008 Fixed 10.0.1 3771 25 Sep 2008 Fixed 11.0.1 1963 20 Nov 2008 Fixed Description In some cases where expressions were evaluated in stored procedures or batches outside of SELECT, INSERT, UPDATE or DELETE statements, it was possible for the expressions to be evaluated incorrectly. The incorrect behaviour would have appeared if arithmetic expressions were used with one argument a DATE, TIME, or TIMESTAMP, or both arguments were strings. In these cases, the incorrect domain could have been used for the arithmetic expression if it were used in an IF, CASE, IN, or concatenation operation. For example, the following select improperly returned '0002', the correct answer should be a numeric with value 2. create variable @v_res long varchar; set @v_res = if 1=1 then '0002' else '1' - '2' endif; select @v_res This problem could have also resulted in conversion errors being returned in cases where they should not, or missed in cases where they should have been generated. This problem has now been fixed.

CR:539113

CR Number:   539113 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) 11.0.0 1444 29 Jul 2008 Fixed 11.0.1 1903 20 Nov 2008 Fixed Description Attempting to execute queries with some illegal constructs involving the CONTAINS search condition, couls have lead to a server crash. This has been fixed.

CR:539128

CR Number:   539128 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1446 29 Jul 2008 Fixed 11.0.1 1905 21 Nov 2008 Fixed Description If an UltraLiteJ database had a publication defined that contained only some of the synchronizable tables, and that publication was synchronized, any changes waiting to be uploaded in the tables that were not yet sync'ed would have been lost. They would still have been in the database, but would have been marked as having been uploaded. Also, UltraLiteJ was incorrectly identifying to MobiLink that tables being synchronized were in all publications currently sync'ed and UltraLiteJ was incorrectly sending the last download time of publications. Both of these problems have been fixed.

CR:539257

CR Number:   539257 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1444 29 Jul 2008 Fixed 11.0.1 1903 21 Nov 2008 Fixed Description If an UltrLiteJ synchronization failed, an error complaining about a dropped connection would sometimes have been printed to the log. This has been fixed.

CR:539289

CR Number:   539289 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1446 31 Jul 2008 Fixed 10.0.1 3735 31 Jul 2008 Fixed 11.0.1 1905 21 Nov 2008 Fixed Description Applications using iAnywhere JDBC driver may have hung when calling the method ResultSet.get*(). This has been fixed. Note, this problem was introduced with the changes for Engineering case 533936.

CR:539308

CR Number:   539308 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) 11.0.0 1445 30 Jul 2008 Fixed 11.0.1 1904 21 Nov 2008 Fixed Description On Windows CE devices, the text of the server usage message was mangled. The message box dialog on CE was expecting utf-16 text, but was incorrectly being passed OS charset text. This has been fixed.

CR:539309

CR Number:   539309 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3737 01 Aug 2008 Fixed 11.0.0 1448 01 Aug 2008 Fixed 11.0.1 1908 21 Nov 2008 Fixed Description If the MobiLink Server had been started with the -nba+ switch, it was possible for the MobiLink Server to have crashed if a non-blocking download acknowledgment was received from a remote database, and the MobiLink Server had lost all its connections with the consolidated database. The MobiLink server will now properly report that all connections to the consolidated database have been lost.

CR:539356

CR Number:   539356 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1447 31 Jul 2008 Fixed 10.0.1 3737 31 Jul 2008 Fixed 11.0.1 1907 20 Nov 2008 Fixed Description The Interactive SQL utility (as well as all the graphical administration tools) did not work with authenticated servers. This has been corrected.

CR:539358

CR Number:   539358 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1446 30 Jul 2008 Fixed 11.0.1 1905 20 Nov 2008 Fixed Description Multiple ORDER BY expressions could have caused an exception when there existed an index with fewer columns than the number of ORDER BY expressions. This has been fixed.

CR:539496

CR Number:   539496 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) 11.0.0 1446 31 Jul 2008 Fixed 11.0.1 1906 21 Nov 2008 Fixed Description At verbosity level 3 or above the Relay Server was logging a faulty protocol version of the connecting Outbound Enabler. The Relay Server also did not completely log the OE_REQUEST_RS_PEER_LIST packet. Although these problems were not affecting the Relay Server's functionality, they have been fixed.

CR:539499

CR Number:   539499 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1447 31 Jul 2008 Fixed 10.0.1 3737 31 Jul 2008 Fixed 11.0.1 1907 21 Nov 2008 Fixed Description If the Overview, Details Table or Graph were disabled in the MobiLink Monitor, closing the Monitor and restarting it would have resulted in a Java null pointer exception. This has been fixed. A workaround is to edit the settings file (.mlmMonitorSettings in version 10 and earlier, .mlMonitorSettings11 in version 11) to restore display of the disabled feature. For the Overview, change ShowOverview=false to ShowOverview=true. For the Table, change ShowTable. For the Graph, change ShowGraph.

CR:539609

CR Number:   539609 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) 11.0.0 1447 31 Jul 2008 Fixed 11.0.1 1907 21 Nov 2008 Fixed Description When running in In-Memory, No-Write mode, only one LOAD TABLE statement was allowed to execute on the database at a time. This was due to the fact that LOAD TABLE, when not running in In-Memory mode, uses the checkpoint log for its page-level undo information, and there can only be one page-level undo operation active on a given database at a time. However, the In-Memory No-Write mode does not use a checkpoint log and therefore has no need of page-level undos. This has been fixed for performance reasons. As a consequence, when running in No-Write mode, multiple, concurrent LOAD TABLE statements may now be active at any point in time, to the same or different tables.

CR:539620

CR Number:   539620 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) 11.0.0 1432 31 Jul 2008 Fixed 11.0.1 1855 21 Nov 2008 Fixed Description In certain rare and highly timing sensitive cases, the server could have hung when shutting down, if an xp_cmdshell() procedure was still running. This has been fixed.

CR:539627

CR Number:   539627 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2031 27 Nov 2008 Fixed 11.0.0 1543 27 Nov 2008 Fixed 10.0.1 3811 27 Nov 2008 Fixed Description Some lines printed to the MobiLink server log would not have caused LogListeners to fire. In particular, warning 10082, "MobiLink server has swapped data pages to disk out:<...> concurrently used pages:<...>", never triggered LogListeners. This has been fixed.

CR:539637

CR Number:   539637 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1447 31 Jul 2008 Fixed 11.0.1 1907 21 Nov 2008 Fixed Description The Check for Updates feature in the Interactive SQL utility (as well as all the graphical administration tools) would always have returned "Unable to contact update server". This has been fixed.

CR:539681

CR Number:   539681 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1469 25 Aug 2008 Fixed 11.0.1 1929 21 Nov 2008 Fixed Description If a connection string included the LINKS parameter, but included an unrecognized protocol type (eg. due to a typo), the error message would have been: "Trying to add unknown port", which was not indicitive of the problem. This has been corrected so that the message is now: "Trying to add unknown port '<port>'" where <port> is the invalid port type. Workaround Description  Use the correct parameter.

CR:539756

CR Number:   539756 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1448 05 Aug 2008 Fixed 11.0.1 1907 21 Nov 2008 Fixed Description On systems other than Windows, the Database Documentation wizard would have displayed the generated HTML files in a poorly formatted way. There was nothing wrong with the HTML files, it was just that the component used to display them was inadequate. This has been corrected so that the wizard now attempts to find an installed web browser and uses that to display the files instead. Note, users can always view the documentation using whatever browser they choose, as a work around to this issue. There was nothing wrong with the HTML files. It was just that the component used to display them was inadequate. Users can always view the documentation using whatever browser they choose to work around this issue.

CR:539772

CR Number:   539772 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2314 11 Sep 2009 Fixed 10.0.1 3961 11 Sep 2009 Fixed Description Installs created by the SQL Anywhere Deployment wizard would only have appeared in the Add or Remove Programs list in Control Panel, for the users that installed the MSI. This behaviour has been changed. The install will now appear in the Add or Remove Programs list for all users.

CR:539799

CR Number:   539799 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1448 05 Aug 2008 Fixed 10.0.1 3739 05 Aug 2008 Fixed 11.0.1 1908 24 Nov 2008 Fixed Description Notifier errors were cataglorized as MobiLink server errors. Errors such as failing to resolved a delivery path to a remote device, and/or failing a push attempt, was resulting in an error line in the MobiLink server log that began with an "E.". This also caused an new entry in the system event log. Notifier errors can be highly repeatative, if the business logic was not implemented in a way that minimized failing attempts. Since these failures are not affecting syncs, they have been recataglorized as informational messages that begin with "I." instead. Two sub labels, "<SISI>" and "<SISE>" have also been added to differentiate notifier informational message and notifier error message. Notifier informational message will now take on the following format: I. YYYY-MM-DD HH:MM:SS. <Main> <SISI> ... Notifier error message will now take on the following format: I. YYYY-MM-DD HH:MM:SS <Main> <SISE> ...

CR:539805

CR Number:   539805 Product Name:   SQL Anywhere Product Component:   Server Status:   Open OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Customer contact us asking for some feature like Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION'. After some researches I received the following answer from internal newsgroup (sybase.internal.asa.helpdesk) I believe the SA feature that can provide functionality similar to what Oracle's autonomous transactions do is events. In SA, events run as independent transactions with their own transaction control and can be triggered from within other transactions without affecting the triggering transaction. Here is an example: CREATE TABLE t1( c1 int ); CREATE EVENT ev HANDLER BEGIN INSERT INTO t1 VALUES( 99 ); commit; END; INSERT INTO t1 VALUES (1); TRIGGER EVENT ev; ROLLBACK The effect of the code above is to rollback the transaction that triggered the event but retain the committed transaction executed by the event. Howerver cust argue that 'Event' at SQL Anywhere are not equal of Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION'. According cust with 'Events' he cannot capture its return, but with Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION' he can. Checking the SQL Anywhere 10 manual, we can see: Event errors are logged to the database server console. After each execution of an event handler, a COMMIT occurs if no errors occurred. A ROLLBACK occurs if there was an error. Event handlers execute on a separate connection, with the permissions of the event owner. To execute with authority other than DBA, you can call a procedure from within the event handler: the procedure executes with the permissions of its owner. The separate connection does not count towards the ten-connection limit of the personal database server. So, cust request to us open a feature request to implement at SQl Anywhere a feature like Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION'.

CR:539807

CR Number:   539807 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) 11.0.0 1267 05 Aug 2008 Fixed 10.0.1 3739 05 Aug 2008 Fixed 11.0.1 1908 24 Nov 2008 Fixed Description On Mac OS X systems, if the server was started on a non-default port (i.e. other than 2638), and with an IPv6 address as the value for the MyIP option, a UDP listener would not have been started on the default port. As a result, the server would not have been able to locate the server via broadcasts unless the sever's port was explicitly specified in the client's connection string. This has now been fixed.

CR:539812

CR Number:   539812 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1448 05 Aug 2008 Fixed 10.0.1 3739 05 Aug 2008 Fixed 11.0.1 1908 24 Nov 2008 Fixed Description The MobiLink server name given by the -zs command line option was not shown in the title bar of the MobiLink server window. This problem is corrected.

CR:539813

CR Number:   539813 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1461 05 Aug 2008 Fixed 10.0.1 3746 05 Aug 2008 Fixed 11.0.1 1921 24 Nov 2008 Fixed Description A new command line option (-sv) has been added to the MobiLink Listener to allow for specifying the script version used for authentication. The default value is ml_global.

CR:539933

CR Number:   539933 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Sep 2008 DEFER Description A newer database release has been supplied that fixes various issues with long-running servers.

CR:540048

CR Number:   540048 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1461 19 Aug 2008 Fixed 10.0.1 3746 19 Aug 2008 Fixed 11.0.1 1921 24 Nov 2008 Fixed Description When attempting to set the non_keywords option to a value that contained a keyword already listed in the current value of the non_keywords option, an invalid option setting error would have been reported. This has been fixed.

CR:540071

CR Number:   540071 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1453 07 Aug 2008 Fixed 10.0.1 3741 07 Aug 2008 Fixed 11.0.1 1913 24 Nov 2008 Fixed Description If an application used a prepared statement to insert an empty string via a parameter marker into a long varchar column of a proxy table, then the server may have hung, or have given a strange error. Note that inserting an empty string as a string literal works just fine. This problem has now been fixed.

CR:540090

CR Number:   540090 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1452 06 Aug 2008 Fixed 11.0.1 1912 24 Nov 2008 Fixed Description After installing SQL Anywhere version 11.0.0 on a non-1252 code page system (such as Chinese, Japanese or Korean), the demonstration database (demo.db) does not contain image data in the Photo column of the Products table. The column values are NULL. This problem has been resolved. The mkdemo.sql script has been revised to use client-side reads (READ_CLIENT_FILE function) to populate the Photo column of the Products table. To correct existing demo.db databases: 1 start demo.db using dbeng11 or dbsrv11 2 change to the scripts directory of the install 3 run the following script: SET TEMPORARY OPTION allow_read_client_file = 'on'; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\TankTop.jpg' ) WHERE Products.ID=300; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\V-Neck.jpg' ) WHERE Products.ID=301; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\CrewNeck.jpg' ) WHERE Products.ID=302; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\CottonCap.jpg' ) WHERE Products.ID=400; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\WoolCap.jpg' ) WHERE Products.ID=401; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\ClothVisor.jpg' ) WHERE Products.ID=500; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\PlasticVisor.jpg' ) WHERE Products.ID=501; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\HoodedSweatshirt.jpg' ) WHERE Products.ID=600; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\ZippedSweatshirt.jpg' ) WHERE Products.ID=601; UPDATE Products SET Photo=READ_CLIENT_FILE( 'adata\CottonShorts.jpg' ) WHERE Products.ID=700;

CR:540092

CR Number:   540092 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1452 06 Aug 2008 Fixed 11.0.1 1912 24 Nov 2008 Fixed Description The Interactive SQL utility could have crashed if a DESCRIBE statement was executed together with an OUTPUT statement that immediately followed it. This has been fixed.

CR:540094

CR Number:   540094 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) 11.0.0 1452 06 Aug 2008 Fixed 10.0.1 3740 06 Aug 2008 Fixed 11.0.1 1912 24 Nov 2008 Fixed Description In rare circumstances, an outgoing mirroring connection attempt to a partner, or to the arbiter, may have hung indefinitely. This has been fixed.

CR:540195

CR Number:   540195 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1453 08 Aug 2008 Fixed 10.0.1 3736 08 Aug 2008 Fixed 11.0.1 1913 24 Nov 2008 Fixed Description When a connection attempted to autostart a server, but then failed to connect, the client incorrectly attempted to autostart the server three times in some cases. This has been fixed so that the client will now only attempt to autostart the server once.

CR:540200

CR Number:   540200 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) 11.0.0 1460 13 Aug 2008 Fixed 10.0.1 3746 25 Aug 2008 Fixed 11.0.1 1922 24 Nov 2008 Fixed Description When running the MobiLink server with minimal verbosity, and using the MobiLink Listener (dblsn), the message "Disconnected from consolidated database" would have appeared in the server log. This has been corrected. The connection used by dblsn will now be reused by the next dblsn client.

CR:540201

CR Number:   540201 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) 11.0.0 1266 07 Aug 2008 Fixed 10.0.1 3741 07 Aug 2008 Fixed 11.0.1 1913 24 Nov 2008 Fixed Description On Mac OS X systems, an application may have taken a very long time to connect to a server if the server was found through an LDAP server and both the client and the server are IPv6-enabled. On Mac OS X, in order to establish a connection to a link-local IPv6 address, the scope (interface) ID must be specified. If a scope ID is not specified, it defaults to 0. A connection attempt where the scope ID is incorrect may take a long time to time out and fail. When a link-local IPv6 address was registered with LDAP, the scope ID was not included in the IP address that was registered. Doing so would not be useful, since scope IDs for the same link can vary from machine to machine. If an application obtained such a link-local address from LDAP and attempts to connect to it, in effect it will attempt a connection with a scope ID of 0. This has been fixed so that now an attempt to if the scope ID is 0 is refused on Mac OS X systems, including when the HOST connection parameter is used in the connection string with a link-local IPv6 address with no interface ID specified. Note that if the wrong non-zero interface ID is specified, a connection will still be attempted.

CR:540205

CR Number:   540205 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) 11.0.0 1453 06 Aug 2008 Fixed 10.0.1 3741 06 Aug 2008 Fixed 9.0.2 3708 06 Aug 2008 Fixed 11.0.1 1913 24 Nov 2008 Fixed Description If a remote server was defined using one of the Remote Data Access JDBC classes, then changing the value of the quoted_identifier option would not have resulted in changing the value of the quoted_identifier option on the remote. This problem has now been fixed.

CR:540219

CR Number:   540219 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) 11.0.0 1453 07 Aug 2008 Fixed 11.0.1 1913 24 Nov 2008 Fixed Description If an application called a procedure that references a proxy table, and that procedure was subsequently used in the FROM clause of a SELECT statement along with the WITH clause, then there was a chance the the server would have crashed. This problem has now been fixed.

CR:540220

CR Number:   540220 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) 9.0.2 3708 07 Aug 2008 Fixed Description The server could have hung, or even crashed, if an HTTP or HTTPS connection was cancelled (i.e. the client application closed the socket) while a request was being processed. This has been fixed.