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

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

CR:530126

CR Number:   530126 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 1243 23 May 2008 Fixed Description SQL Anywhere allowed the use of the system procedure sa_get_user_status() to obtain sensitive information about all users in the database, regardless of whether the user invoking the procedure had DBA authority. This has been corrected so that the server now restricts the result set to one row corresponding to the current user when invoked by a user without DBA privileges. Users with DBA authority are now provided a result set with one row for each user in the database.

CR:530273

CR Number:   530273 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 1408 27 May 2008 Fixed 10.0.1 3697 27 May 2008 Fixed 11.0.1 1840 14 Nov 2008 Fixed Description If there were more than 100 connections actively using Java in the database support at the same time, then the JVM would have crashed, or the server could have hung. This problem has now been fixed.

CR:530287

CR Number:   530287 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 1414 20 Jun 2008 Fixed 10.0.1 3719 16 Jul 2008 Fixed 11.0.1 1871 14 Nov 2008 Fixed Description Indexes containing values longer than approx 250 bytes could have become corrupt when an entry was deleted from the index. This has now been fixed.

CR:530302

CR Number:   530302 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 1407 27 May 2008 Fixed 10.0.1 3770 15 Sep 2008 Fixed 11.0.1 1836 14 Nov 2008 Fixed Description Attempting to executing a batch which did not take a host variable, but included the :var syntax, could have resulted in a communication error. The :var syntax can be used in a CREATE or ALTER SERVICE statement. This has now been fixed.

CR:530309

CR Number:   530309 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 1407 27 May 2008 Fixed 11.0.1 1836 14 Nov 2008 Fixed Description the component that displayed an explanation of the selected connection parameter on the "Advanced" page of the "Connect" dialog, was unreasonably short on Japanese systems. This has been fixed.

CR:530318

CR Number:   530318 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 1408 27 May 2008 Fixed 10.0.1 3696 27 May 2008 Fixed 11.0.1 1839 14 Nov 2008 Fixed Description When diagnostic tracing was enabled, with PLANS or PLANS_WITH_STATISTICS as the tracing type, some plans or cursor information could have failed to have been saved. Alternatively, some plans that did not fit the timing cut-off in ABSOLUTE_COST or RELATIVE_COST_DIFFERENCE conditions, could have benn incorrectly saved. These problems have now been fixed.

CR:530339

CR Number:   530339 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1244 27 May 2008 Fixed 10.0.1 3696 27 May 2008 Fixed 9.0.2 3670 27 May 2008 Fixed Description If an application had a connection enlisted in Microsoft's Distributed Transaction Coordinator (DTC), and it issued a commit on the distributed transaction, then there was a chance the server would have hung when a request to enlist in the DTC came in at the same time as the two phase commit. This problem has now been fixed.

CR:530427

CR Number:   530427 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 1408 27 May 2008 Fixed 11.0.1 1839 14 Nov 2008 Fixed Description The table selection page of the Export wizard contained two controls with the same mnemonic ('e'). This has been fixed.

CR:530533

CR Number:   530533 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1408 27 May 2008 Fixed 11.0.1 1840 14 Nov 2008 Fixed Description The detailed results from the "Test Connection" tool in the "Connect" dialog could have contained corrupt characters when running on Windows systems. This would have occured when the language for non-Unicode programs (i.e. the "system locale") was set to something other than English (e.g. Japanese), and the machine's location was set to a country which in which English is spoken (e.g. United States). The non-English characters were corrupted. This has been fixed.

CR:530534

CR Number:   530534 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1235 27 May 2008 Fixed 10.0.1 3693 27 May 2008 Fixed Description The changes made for Engineering case 491400, to correct a problem with the marquee in the overview panel flashing excessively when connected to a MobiLink server, introduced drawing artifacts when the horizontal scroll bar was used to move the marquee. This has been fixed.

CR:530539

CR Number:   530539 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 1408 27 May 2008 Fixed 11.0.1 1840 14 Nov 2008 Fixed Description Pressing ALT+I in the "Add to Favorites" dialog did not set the focus to the list of favorites folders. This has been corrected so that now it does.

CR:530576

CR Number:   530576 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) 11.0.0 1408 27 May 2008 Fixed 10.0.1 3697 27 May 2008 Fixed 9.0.2 3671 27 May 2008 Fixed 11.0.1 1840 14 Nov 2008 Fixed Description The http_encode() function was not encoding the 0x1f character. This has been fixed. This character is now encoded to "%1F".

CR:530579

CR Number:   530579 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 1407 27 May 2008 Fixed 11.0.1 1839 14 Nov 2008 Fixed Description A new MobiLink server option, -vo, now shows SQL passthrough activity in the MobiLink server. Prior to this option it was impossible to know what was happening on the server when debugging SQL Passthrough.

CR:530587

CR Number:   530587 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 1408 03 Jun 2008 Fixed 10.0.1 3699 03 Jun 2008 Fixed 11.0.1 1843 14 Nov 2008 Fixed Description When viewing the server messages from the SQL Anywhere Console utility (dbconsole0 or from the Sybase Central, there was a possibility that messages could have been duplicated or lost. This has been fixed.

CR:530594

CR Number:   530594 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 1408 28 May 2008 Fixed 10.0.1 3697 28 May 2008 Fixed 9.0.2 3671 28 May 2008 Fixed 11.0.1 1840 14 Nov 2008 Fixed Description Closing a ResultSet object may, in very rare cases, crash the iAnywhere JDBC driver. This problem has now been fixed.

CR:530596

CR Number:   530596 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 04 Jun 2008 Fixed 10.0.1 3703 04 Jun 2008 Fixed 11.0.1 1848 14 Nov 2008 Fixed Description If a multi-threaded JDBC application attempted to make a connection on one thread while the Java VM was shutting down, there was a chance that the application would have crashed. Note that this problem was specific to Unix platforms only. The problem has now been fixed.

CR:530597

CR Number:   530597 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 1840 28 May 2008 Fixed 11.0.0 1408 14 Nov 2008 Fixed Description The option to continue executing statements after encountering an error with an Interactive SQL statement (such as INPUT, OUTPUT, READ, PARAMETERS, DESCRIBE) was not given. Now it is. This problem did not affect normal SQL statements.

CR:530710

CR Number:   530710 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3714 19 Jun 2008 Fixed Description Executing an INSERT or an UPDATE that fails, could, in some cases, have caused the database server to fail an assertion. A specific assertion that was likely to have been seen as a result of this failure was: 201501 - "Page for requested record not a table page or record not present on page." For this problem to have occurred, the failing INSERT or UPDATE must have been to a table that had blob columns containing data less than approximately one database page in length, but longer than the column's inline amount. This has now been corrected. This has been fixed.

CR:530736

CR Number:   530736 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.0 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1484 08 Sep 2008 Fixed 10.0.1 3760 08 Sep 2008 Fixed 9.0.2 3721 08 Sep 2008 Fixed 11.0.1 1942 14 Nov 2008 Fixed Description The changes for Engineering case 491180 (enable write through on CE) introduced a dependency on the file note_prj.dll, which may not have been included on non-standard Windows CE devices. On these devices, the server may have failed to start with an error that it could not find the server or one of its components. The Standard Windows Mobile devices were not affected. This has been corrected and note_prj.dll is now loaded dynamically, and if it is not found, the server will not enable write through on pre CE 5 devices.

CR:530776

CR Number:   530776 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 1409 29 May 2008 Fixed 10.0.1 3706 29 May 2008 Fixed 11.0.1 1850 14 Nov 2008 Fixed Description When a database created by a newer version for SQL Anywhere (eg version 11) was started by an older version of SQL Anywhere (eg version 10), the server would have read some pages, other than the definition page, from the database before verifying that the capabilities of the file and server were compatible. The server now tests the capability bits of a database file against the capabilities supported by the server sooner in the database startup process. There are no known user-visible effects caused by checking the capabilities later, other than when starting an encrypted database created by newer software, the server will no longer prompt for an encryption key before reporting that the capabilities are incompatible.

CR:530790

CR Number:   530790 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 1411 12 Jun 2008 Fixed 10.0.1 3709 12 Jun 2008 Fixed 11.0.1 1842 14 Nov 2008 Fixed Description When running the Application Wizard, Sybase Central would have failed to connect to the tracing database if the server had been started with broadcast ignored (-sb 0). This has been corrected. Sybase Central now will include the machine name and port in the connection string when attaching to the tracing database.

CR:530917

CR Number:   530917 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1255 03 Jun 2008 Fixed 10.0.1 3701 03 Jun 2008 Fixed Description An application could have hung when opening a pooled connection. The hang was as a result of two problems: 1. The provider was incorrectly calculating a very long timeout period. 2. Dropped connections were not being recycled. These problems have now been fixed.

CR:530920

CR Number:   530920 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 1408 09 Jun 2008 Fixed 10.0.1 3706 09 Jun 2008 Fixed 11.0.1 1842 14 Nov 2008 Fixed Description During diagnostic tracing with at least one tracing level of type optimization_logging_with_plans, an incorrect row size could have been reported for a table that had been created immediately before the statement referencing the table was executed. This has been fixed.

CR:530923

CR Number:   530923 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1422 09 Jul 2008 Fixed 10.0.1 3723 09 Jul 2008 Fixed 9.0.2 3691 09 Jul 2008 Fixed 11.0.1 1882 14 Nov 2008 Fixed Description Occasionaly, a DB_E_BADACCESSORHANDLE error would have been returned by the OLE DB IMultipleResults::GetResult method. This error could have occurred if the DBPARAMS structure that was passed to the ICommand::Execute method was disposed by the client before all the result rowsets from a stored procedure call were returned by calls to the GetResult method. On the final call to GetResult, output parameters may have become available. As a result, the DBPARAMS structure was required to be intact for each call to GetResult. This problem has been fixed. When Execute is called, if it is determined that there are no output parameters, then the DBPARAMS structure will be ignored on subsequent calls to GetResult.

CR:530930

CR Number:   530930 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 1408 03 Jun 2008 Fixed 11.0.1 1842 14 Nov 2008 Fixed Description The bold title text that appears on the "Advanced" page of the "Connect" window was not displayed consistently. Specifically, the text (e.g. "AppInfo [APP]") would not have been displayed if the Connect Assistant was not initially visible when the "Connect" window was opened, and was then made visible before the "Advanced" page was initially selected. This has now been fixed, as well as a fix for an intermittent problem that caused the description field at the bottom of the "Advanced" page from being too short to display more than one line.

CR:530954

CR Number:   530954 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) 9.0.2 3672 30 May 2008 Fixed Description The Interactive SQL utility, (as well as other adinistration tools, such as Sybase Central and the SQL Anywhere Console) may have failed to start on newer Linux systems including Linux Red Hat Enterprise 5. These Administration Tools rely on libXp.so.6 which may not have been installed by default. For example, installing the following package solves the problem on RHE5: libXp-1.0.0-8.1.el5.i386 "X Org X11 libXp runtime library"

CR:530994

CR Number:   530994 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 1410 05 Jun 2008 Fixed 11.0.1 1854 14 Nov 2008 Fixed Description The SQL Anywhere server allows for the creation of tables with a very large number of columns and/or indexes. The speed at which the server processes operations involving such large schemas has now been significantly improved.

CR:531081

CR Number:   531081 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 3674 03 Jun 2008 Fixed Description The changes for Engineering case 486744 introduced a problem where the server could have crashed while executing a BEFORE UPDATE row level trigger. This has been fixed.

CR:531094

CR Number:   531094 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1249 03 Jun 2008 Fixed 10.0.1 3698 03 Jun 2008 Fixed 9.0.2 3672 03 Jun 2008 Fixed Description The installer may failed on some versions of Linux. Symptoms may have ncluded incorrect reporting of available disk space, and messages such as: tail: `-1' option is obsolete; use `-n 1' Try `tail --help' for more information. An error occurred while attempting to extract files in /opt/sybase/ The way in which the head and tail utilities were being invoked by the installer was incompatible with some older versions of the Gnu head and tail utilities included on Linux. This has been fixed by replacing the use of head and tail in the setup script with appropriate sed commands.

CR:531126

CR Number:   531126 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 1408 03 Jun 2008 Fixed 11.0.1 1843 14 Nov 2008 Fixed Description The "Connect" window was displayed on startup even if the "-c" command line option was given and the connection parameters were sufficient to connect. This has been corrected so that the "Connect" window is no longer displayed in this case.

CR:531128

CR Number:   531128 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 1408 03 Jun 2008 Fixed 11.0.1 1841 14 Nov 2008 Fixed Description On Unix systems, when starting the MobiLink client (dbmlsync) in server mode after having recently shutdown an instance of dbmlsync in server mode, if the same port number was reused on the -sp option it was possible for dbmlsync to have failed to start and report an error similar to "unable to bind to port ...". This problem has now been fixed.

CR:531154

CR Number:   531154 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 1408 03 Jun 2008 Fixed 11.0.1 1843 14 Nov 2008 Fixed Description The "Browse" button on the "DBConsole" pane of the "Options" window could have been enabled inappropriately , even when message logging was not turned on. This has been fixed.

CR:531160

CR Number:   531160 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 11 Jun 2008 Fixed 11.0.1 1855 14 Nov 2008 Fixed Description If a statement used a keyset operator, it was possible for the statement to evaluate expressions that should not be evaluated. In order for this failure to appear, the statement must contain some unflattened views or derived tables (such as grouped, distinct, or top-N views). Keyset operators are used to support values sensitive cursors, and they are also used for some UPDATE, DELETE or MERGE statements. This has been fixed. For example, in the following statement, a division by zero error could be incorrectly returned for a keyset-driven (value sensitive) cursor. select if TMS_1.x = 'zzz' and 1/QT2.y > 0 then 12 endif from ( SELECT x, y FROM TMS_2 GROUP BY x,y ) AS QT2 join TMS_1 ON TMS_1.x = QT2.x

CR:531295

CR Number:   531295 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) 10.0.1 3702 04 Jun 2008 Fixed 9.0.2 3674 04 Jun 2008 Fixed Description The server could have crashed while optimizing complex queries. This has been fixed

CR:531314

CR Number:   531314 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 04 Jun 2008 Fixed 11.0.1 1847 14 Nov 2008 Fixed Description Double-clicking a .SAPLAN file on a Windows machine did not always work properly. The new "Plan Viewer" window was not automatically activated. If the "Fast launcher" option was on, the wrong plan file could have been opened under some circumstances. Both of these problems have been fixed.

CR:531323

CR Number:   531323 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1408 03 Jun 2008 Fixed 11.0.1 1846 14 Nov 2008 Fixed Description If the QAnywhere Agent for Ultralite experienced a failed synchronization then there was a chance that subsequent synchronizations would then have failed with a -193 primary key not unique error. This has been fixed

CR:531334

CR Number:   531334 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 09 Jun 2008 Fixed 10.0.1 3706 09 Jun 2008 Fixed 11.0.1 1850 14 Nov 2008 Fixed Description On Linux systems, starting a database that is stored on a non-tmpfs based ramdisk could have failed. This has been fixed. Note, a work around is to use a tmpfs based ramdisk, or start the server with the -u (use buffered disk I/O).

CR:531348

CR Number:   531348 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1254 03 Jun 2008 Fixed 10.0.1 3701 03 Jun 2008 Fixed 9.0.2 3674 03 Jun 2008 Fixed Description Table locks were not released by the SABulkCopy() method when SABulkCopyOptions.LockTable is specified. This problem has been fixed.

CR:531523

CR Number:   531523 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 1409 04 Jun 2008 Fixed 11.0.1 1847 14 Nov 2008 Fixed Description Cancelling a statement could have taken several seconds if the statement returned more than 500K of data as text, and it was configured to display results as text. This has been fixed.

CR:531525

CR Number:   531525 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3674 04 Jun 2008 Fixed Description MobiLink with QAnywhere messaging enabled used approximately 400 KB of heap memory for each QAnywhere client that synchronizes with it. This occurred until the prepared statement cache size (default 200 for SA consolidated databases) was reached, and then each new QAnywhere client caused a cached statement to be dropped and a new statement to be prepared. This behaviour has been changed for SA consolidated databases only. Now the MobiLink server will use a constant amount of heap memory for QAnywhere client synchronizations, and will not overflow the prepared statement cache as many clients synchronize.

CR:531532

CR Number:   531532 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 03 Jun 2008 Fixed 10.0.1 3701 03 Jun 2008 Fixed 11.0.1 1847 14 Nov 2008 Fixed Description If a connection was dropped, or the server went down with a fatal error while connecting with ODBC, OLE DB or ADO.NET, or while calling the DBLib functions db_change_char_charset or db_change_nchar_charset, the client application could have crashed. This has been now been fixed.

CR:531577

CR Number:   531577 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 04 Jun 2008 Fixed 11.0.1 1847 14 Nov 2008 Fixed Description When editing an unsigned column value, if a value larger than the largest signed value was entered, zero would have been incorrectly saved as the column value. This has been fixed so that the value entered is now saved.

CR:531716

CR Number:   531716 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 1409 05 Jun 2008 Fixed 11.0.1 1848 17 Nov 2008 Fixed Description The HTML files created by the "Generate Database Documentation" feature of the plug-in would have contained titles that Internet Explorer 7 could not display if Sybase Central was running on a non-English machine. This has been fixed. Note, this problem did not affect Internet Explorer 6 or Firefox 2.0.0.

CR:531718

CR Number:   531718 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 05 Jun 2008 Fixed 10.0.1 3705 05 Jun 2008 Fixed 9.0.2 3675 05 Jun 2008 Fixed 11.0.1 1849 17 Nov 2008 Fixed Description If an application using the iAnywhere JDBC driver attempted to perform a batched insert (using addBatch()/executeBatch()) and the batch size was large (greater than 500), then performance of the batch insert would have degraded significantly when long string columns were involved in the batch. The driver was allocating more memory than necessary, and making several small allocations instead of a few large ones. This problem has now been corrected.

CR:531730

CR Number:   531730 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 05 Jun 2008 Fixed 10.0.1 3703 05 Jun 2008 Fixed 11.0.1 1848 17 Nov 2008 Fixed Description After modifying the incremental download size of the QAnywhere Agent using the -idl option, it would not have been possible to reset the size to the default value of -1. Attempting to set the size to -1 would have left the incremental download size unchanged. This has been fixed. Now, specifying any non-positive number for the -idl option will reset the incremental download size to -1.

CR:531766

CR Number:   531766 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 1409 05 Jun 2008 Fixed 10.0.1 3703 05 Jun 2008 Fixed 11.0.1 1848 17 Nov 2008 Fixed Description If a JMS message bound for a QAnywhere client was missing its native address, and no default address was specified for the JMS connector, the QAnywhere Server would have reported a NullPointerException. This has been fixed. The server now reports the proper error message

CR:531768

CR Number:   531768 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 1409 05 Jun 2008 Fixed 11.0.1 1848 17 Nov 2008 Fixed Description UltraLite appeared in the list of databases to which the Interactive SQL utility could connect on Solaris and OS/X machines. UltraLite is not supported on either of these platforms, and so UltraLite databases have been removed from the user interface on these platforms.

CR:531784

CR Number:   531784 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) 9.0.2 3675 05 Jun 2008 Fixed Description If an Open Client or jConnect application executed a query that involved the use of host variables within a batch, then the server would have crashed. This has been fixed so that the query now correctly fails with the error message "Host variables may not be used within a batch".

CR:531962

CR Number:   531962 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 1409 05 Jun 2008 Fixed 10.0.1 3704 05 Jun 2008 Fixed 9.0.2 3675 05 Jun 2008 Fixed 11.0.1 1849 17 Nov 2008 Fixed Description If an application attempted to use a Statement, PreparedStatement or ResultSet object at the same time that the underlying Connection object was closed on a different thread, then there was a chance the application would have crashed.The problem has now been fixed. Note that finalizing Connection objects can cause the same crash.

CR:531967

CR Number:   531967 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 1409 05 Jun 2008 Fixed 10.0.1 3705 05 Jun 2008 Fixed 11.0.1 1849 17 Nov 2008 Fixed Description The QAnywhere Server would have throw an ObjectRepositoryException if it was configured to use a delete rule with an empty condition clause. That is, if a rule was given that had nothing written to the right of the equals sign. One such rule might look like: "AUTO=" This has been fixed. Specifying an empty condition clause now specifies that all available messages should be deleted.

CR:531993

CR Number:   531993 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 1409 09 Jun 2008 Fixed 11.0.1 1849 17 Nov 2008 Fixed Description On the MobiLink client's setup dialog, clicking either the "cmdline help" or "extended option help" buttons would have caused dbmlsync to shutdown without displaying the help dialog. This has now been fixed.

CR:532086

CR Number:   532086 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1454 08 Aug 2008 Fixed 10.0.1 3741 08 Aug 2008 Fixed 11.0.1 1914 17 Nov 2008 Fixed Description If a server had many concurrent connections using Java in the database support, then there was a chance the server could either have hung, or crashed intermittently. These hangs or crashes could also have occurred at server shutdown time. These problems have now been fixed.

CR:532102

CR Number:   532102 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) 10.0.1 3706 09 Jun 2008 Fixed 9.0.2 3676 09 Jun 2008 Fixed Description The changes made for Engineering case 483518 caused the server to crash if a call to the graphical_plan() function was made within an event handler. This has now been corrected.

CR:532109

CR Number:   532109 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) 10.0.1 3706 20 Jun 2008 Fixed 9.0.2 3682 20 Jun 2008 Fixed Description A query containing a derived table, or a subquery with a OUTER JOIN whose ON condition references tables from outside the query block, may have returned incorrect results. This has been fixed. In the following example, the ON condition of the LEFT OUTER JOIN in the EXISTS subquery references the table 't1', which is a table used in the FROM clause of the main query block. This query may return incorrect result for some instances of the database. select * from t1 where exists( select 1 from t4 left outer join t2 on ( t2.c1 = t4.c1 and t2.c1 = t1.c1 ) where t4.c1=1 )

CR:532116

CR Number:   532116 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1409 09 Jun 2008 Fixed 11.0.1 1850 17 Nov 2008 Fixed Description Synchronizations through a server that required Digest HTTP authentication would have failed if the server required a reauthentication in the middle of the synchronization. This has been fixed so that the client will now successfully reauthenticate and continue the synchronization.

CR:532185

CR Number:   532185 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 1409 09 Jun 2008 Fixed 10.0.1 3706 09 Jun 2008 Fixed 11.0.1 1852 17 Nov 2008 Fixed Description SQL Anywhere keeps track of dependencies of views on other views and tables. For view definition queries that involve more than two UNION, EXCEPT or INTERSECT branches and/or sub-queries, the server's computation of the dependency information could have been incorrect, leading to erroneous behaviour. This has beed fixed so that the server now computes the dependency information correctly. Note, any existing views compiled with an older version of the server will continue to have potentially incorrect dependency information in the catalog. Existing views can be made to have the correct dependency information by being recompiled, either implicitly during a DDL operation on one of the referenced tables, or explicitly.

CR:532238

CR Number:   532238 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) 10.0.1 3707 09 Jun 2008 Fixed Description In SQL Anywhere 10, SOAP web services used the server's HTTP HOST header to generate the namespace returned in the SOAP response. This behaviour was changed in SQL Anywhere 11 to always use the namespace sent in the SOAP request for the response. This change in behaviour has now been integrated into 10.0 in order to better support SOAP clients built with version 10.0 and connect to a server that has been upgraded to version 11.0.

CR:532254

CR Number:   532254 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 1410 09 Jun 2008 Fixed 10.0.1 3707 09 Jun 2008 Fixed 11.0.1 1853 17 Nov 2008 Fixed Description A server that had registered itself with LDAP tried could have crashed when trying to start a database using an alternate server name, if an error occurred in reading the saldap.ini file. This has been fixed.

CR:532276

CR Number:   532276 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 1410 12 Jun 2008 Fixed 10.0.1 3708 12 Jun 2008 Fixed 9.0.2 3678 12 Jun 2008 Fixed 11.0.1 1855 17 Nov 2008 Fixed Description A large query containing a 'WITH' clause could have crashed the server. The server was failing to recognize a SYNTACTIC_LIMIT error for such queries. This has now been corrected.

CR:532280

CR Number:   532280 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 12 Jun 2008 Fixed 10.0.1 3708 12 Jun 2008 Fixed 11.0.1 1855 17 Nov 2008 Fixed 9.0.2 3909 28 Oct 2009 Fixed Description The server could have behaved erroneously when new procedures were created from within event handlers, or after having executed the SETUSER statement. Although rare, in the worst case a user could have been allowed to be dropped while still connected. These problems have been corrected so that the server now behaves correctly.

CR:532314

CR Number:   532314 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 1522 24 Oct 2008 Fixed 10.0.1 3787 24 Oct 2008 Fixed 11.0.1 1994 17 Nov 2008 Fixed Description If creating a tracing database resulted in an error, the real cause of the error would have been missing from the error dialog details. This has been fixed.

CR:532450

CR Number:   532450 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 1410 10 Jun 2008 Fixed 11.0.1 1854 17 Nov 2008 Fixed Description It was possible for execution of an OUTPUT statement to cause the statement, which generated the previous results, to be reexecuted unnecessarily. Reexecution of the statement could have resulted in poor performance, or error messages if the statement could not be reexecuted (for example, because it was a stored procedure call with side-effects). This has now been fixed.

CR:532452

CR Number:   532452 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 10 Jun 2008 Fixed 10.0.1 3707 10 Jun 2008 Fixed 11.0.1 1854 17 Nov 2008 Fixed Description The changes for Engineering case 530534 (which was a followup fix to Engineering case 491400) were incomplete, resulting in the Overview marquee not updating when zoomed out with the marquee at the leftmost position. This has been fixed.

CR:532475

CR Number:   532475 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 1262 10 Jun 2008 Fixed Description The system procedure dbo.sa_text_index_statistics() can be used to obtain information about existing text indexes in the database. Depending upon the current state of the tables with text indexes defined on them, the server could have failed to return the expected information for all existing text indexes in the database. This has been corrected so that the server will now return the correct answer, regardless of the current state of the server. Note that since Sybase Central makes use of sa_text_index_statistics() in order to display information on text indexes, Sybase Central will also not work as expected.

CR:532521

CR Number:   532521 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 11 Jun 2008 Fixed 10.0.1 3708 11 Jun 2008 Fixed 11.0.1 1855 17 Nov 2008 Fixed Description If a query like the following was excuted: SELECT TOP var1 START AT var2 * FROM ... and the query referenced a proxy table, and the query could have been handled in full passthru, then the query would have failed with a 'column not found' or 'bad cursor range' error. This problem has now been fixed.

CR:532626

CR Number:   532626 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 11 Jun 2008 Fixed 10.0.1 3708 11 Jun 2008 Fixed 11.0.1 1854 17 Nov 2008 Fixed Description In certain rare situations, it was possible for the server to hang when starting a database. This has been fixed.

CR:532636

CR Number:   532636 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 18 Jun 2008 Fixed 11.0.1 1861 17 Nov 2008 Fixed Description The list of statistics displayed on a version 10 or later server's Statistics tab was incomplete; specifically, it excluded statistics introduced in version 10. This has been fixed.

CR:532638

CR Number:   532638 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 16 Jun 2008 Fixed 11.0.1 1860 17 Nov 2008 Fixed Description Incorrect results may have been obtained from queries when there was a LIKE search condition combined with an ORDER BY ... DESC clause, when both of these clauses specified a column that was the first column in an index. For example: SELECT * FROM MyTable WHERE col LIKE 'abc%' ORDER BY col DESC The implementation of LIKE predicates with reversed index scans was erroneous. This has now been corrected.

CR:532668

CR Number:   532668 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 1410 11 Jun 2008 Fixed 10.0.1 3708 11 Jun 2008 Fixed 11.0.1 1855 17 Nov 2008 Fixed Description The SORTKEY function did not allow the first parameter to be BINARY if the second parameter (the collation id) was not an integer. Similarly, COMPARE did not allow either of the first two parameters to be BINARY if the third parameter (the collation id) was not an integer. For example, SORTKEY( cast( 'a' as binary ), 'dict' ) would have reported the error "Cannot convert weCHAR values.

CR:532793

CR Number:   532793 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Jul 2008 Fixed Description ODBC Driver by Sybase: The iAnywhere MobiLink application hangs during connection failover event.

CR:532796

CR Number:   532796 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 1411 18 Jun 2008 Fixed 10.0.1 3712 18 Jun 2008 Fixed 11.0.1 1860 17 Nov 2008 Fixed Description If a database was started with an alternate server name on an already-running server, in rare cases, subsequent TCP connection attempts to the server may have failed. This has been fixed.

CR:532802

CR Number:   532802 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 13 Jun 2008 Fixed 10.0.1 3710 13 Jun 2008 Fixed 9.0.2 3679 13 Jun 2008 Fixed 11.0.1 1857 17 Nov 2008 Fixed Description Closing a ResultSet object may have, in very rare cases, crashed the iAnywhere JDBC driver. This problem has now been fixed.

CR:532807

CR Number:   532807 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 1410 13 Jun 2008 Fixed 10.0.1 3709 13 Jun 2008 Fixed 11.0.1 1856 17 Nov 2008 Fixed Description The Server Message Store wizard could have failed to complete with the message "Could not install QAnywhere support. Request to start/stop database denied". This would have occurred if a server was already running and it was not started with the "-gd DBA" or "-gd all" command line options, and "Create an ODBC data source" was checked in the wizard. This has now been fixed.

CR:532816

CR Number:   532816 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16 Jun 2009 Fixed Description Automatic creation of a tracing database (either through the Profiling wizard or the Tracing wizard) could have failed if the database used secondary dbspaces with absolute (hard-coded) paths. This could have arisen when the machine on which the profiling/tracing database was being created didn't have a directory structure that matched the one for the production database, and was especially likely if the two machines ran different operating systems. If the two machines involved are running the same OS, the presence of the missing drives / directories is now simulated, if possible. Otherwise, the workaround is to unload the database to the same machine, start the copy, and move the dbspace files on the copy to directories that can be specified with relative paths. Then, issue ALTER DBSPACE RENAME commands to point the main dbspace at the new dbspaces. The database can now be copied to the machine that will host the tracing database.

CR:532819

CR Number:   532819 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 1411 18 Jun 2008 Fixed 10.0.1 3712 18 Jun 2008 Fixed 11.0.1 1860 17 Nov 2008 Fixed Description If a START DATABASE statement or an attempt to autostart a database on an already-running server, failed due to an alternate server name conflict, a second attempt to start the database with the same (conflicting) alternate server name would have succeeded when it should have failed as well. This has now been fixed.

CR:532825

CR Number:   532825 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 1437 12 Jun 2008 Fixed 11.0.1 1896 17 Nov 2008 Fixed Description A new logging option has been added to the MobiLink server. The -vm command line option will cause the server to print to the log the duration of each sync and the duration of each sync phase whenever a sync completes. The sync phases are the same as those displayed in the MobiLink monitor. Each value is prefixed with "PHASE: " to aid searching for and printing the values. Sample output follows: I. 2008-06-05 14:48:36. <1> PHASE: start_time: 2008-06-05 14:48:36.048 I. 2008-06-05 14:48:36. <1> PHASE: duration: 175 I. 2008-06-05 14:48:36. <1> PHASE: sync_request: 0 I. 2008-06-05 14:48:36. <1> PHASE: receive_upload: 19 I. 2008-06-05 14:48:36. <1> PHASE: get_db_worker: 0 I. 2008-06-05 14:48:36. <1> PHASE: connect: 18 I. 2008-06-05 14:48:36. <1> PHASE: authenticate_user: 51 I. 2008-06-05 14:48:36. <1> PHASE: begin_sync: 69 I. 2008-06-05 14:48:36. <1> PHASE: apply_upload: 0 I. 2008-06-05 14:48:36. <1> PHASE: prepare_for_download: 1 I. 2008-06-05 14:48:36. <1> PHASE: fetch_download: 4 I. 2008-06-05 14:48:36. <1> PHASE: wait_for_download_ack: 0 I. 2008-06-05 14:48:36. <1> PHASE: end_sync: 0 I. 2008-06-05 14:48:36. <1> PHASE: send_download: 10 I. 2008-06-05 14:48:36. <1> PHASE: get_db_worker_for_download_ack: 0 I. 2008-06-05 14:48:36. <1> PHASE: connect_for_download_ack: 0 I. 2008-06-05 14:48:36. <1> PHASE: nonblocking_download_ack: 0

CR:532846

CR Number:   532846 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1264 12 Jun 2008 Fixed 11.0.1 1856 04 Dec 2008 Fixed Description Columns with data types of LONG BINARY or LONG VARCHAR were not stored correctly during a synchronization download. This has now been corrected.

CR:532850

CR Number:   532850 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 13 Jun 2008 Fixed 10.0.1 3709 13 Jun 2008 Fixed 9.0.2 3678 13 Jun 2008 Fixed 11.0.1 1856 17 Nov 2008 Fixed Description Executing a CREATE EXISTING TABLE statement to create a proxy table when the remote table has an unsupported index on it, could have caused the statement to fail. This problem has now been fixed.

CR:532859

CR Number:   532859 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) 10.0.1 3736 31 Jul 2008 Fixed Description It was possible to get gaps between transaction logs when using the Backup Database command to rename a transaction log, or when using dbmlsync -x to rename and restart a transaction log. It was also possible, although more unlikely, to have a transaction log that was missing a transaction that was already committed to the database. This has been fixed.

CR:532999

CR Number:   532999 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 13 Jun 2008 Fixed 10.0.1 3710 13 Jun 2008 Fixed 11.0.1 1857 17 Nov 2008 Fixed Description The database property 'VersionStorePages' was reporting the total number of pages in the temporary file rather than the number of pages in the version store. This has now been fixed.

CR:533010

CR Number:   533010 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 1410 13 Jun 2008 Fixed 11.0.1 1857 17 Nov 2008 Fixed Description When using the new ULODBC class to map a proxy table to a table within a non-UTF8 MBCS UltraLite database, and then attempting to fetch string data from that proxy table, there was a chance the data would have had additional garbage characters. This problem has been fixed.

CR:533012

CR Number:   533012 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 1410 13 Jun 2008 Fixed 10.0.1 3710 13 Jun 2008 Fixed 11.0.1 1857 17 Nov 2008 Fixed Description The connection property 'IsDebugger' has been added to allow connections which are currently being used to run the procedure debugger to be distinguished from normal connections. The value of connection_property('IsDebugger',number) will be 'Yes' if "number" corresponds to the connection number of a debugger connection, and 'No' otherwise.

CR:533013

CR Number:   533013 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) 10.0.1 3712 17 Jun 2008 Fixed Description When executed from within a login procedure, a BACKUP statement, an external function call, a web service request, a Java request or a remote procedure call could have caused the requesting connection to hang indefinitely. In certain cases, such as when executing a BACKUP statement, this hang could eventually cause other connections to hang as well. This has been fixed.

CR:533028

CR Number:   533028 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 1264 16 Jun 2008 Fixed 11.0.1 1857 04 Dec 2008 Fixed Description If a database contained materialized views, and one of the base tables referenced by a materialized view contained foreign key constraints, then the Unload utility (dbunload) could have generated a reload script that would have failed to execute. The reload script would have contained ALTER TABLE ... ADD FOREIGN KEY statements after the creation of materialized views. The server now allows the reload script to execute without errors. Note, a work-around is to manually edit the reload script to make the reload work.

CR:533055

CR Number:   533055 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 1411 18 Jun 2008 Fixed 10.0.1 3714 18 Jun 2008 Fixed 11.0.1 1862 17 Nov 2008 Fixed Description If a LIKE predicate contained specific forms of patterns, and it referred to a column contained in an index, then it was possible for the server to crash when opening the statement containing the LIKE predicate. This has been fixed.

CR:533249

CR Number:   533249 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 16 Jun 2008 Fixed 10.0.1 3715 19 Jun 2008 Fixed 11.0.1 1860 17 Nov 2008 Fixed Description The download phase of a synchronization could have failed with a -194 error ("No primary key value for foreign key"). This was most likely to have occurred during large synchronzations or when the database engine is under considerable stress. This has now been fixed.

CR:533264

CR Number:   533264 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 17 Jun 2008 Fixed 11.0.1 1860 17 Nov 2008 Fixed Description Synchronization profiles were incorrectly appearing in the Extended Database Properties tab of an UltraLite databases property sheet. This has been corrected.

CR:533270

CR Number:   533270 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 17 Jun 2008 Fixed 11.0.1 1860 17 Nov 2008 Fixed Description The default Precision and Scale values for an UltraLite database are 30, 6 respectively. When creating a table using the plug-in for Sybase Central, these values were used as defaults for numeric columns, even when the databases default Precision and Scale values were different. This has been fixed.

CR:533327

CR Number:   533327 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 1411 18 Jun 2008 Fixed 11.0.1 1861 17 Nov 2008 Fixed Description Certain illegal column domains were not being diagnosed, such as VARCHAR(-1). This has been corrected.

CR:533459

CR Number:   533459 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3680 18 Jun 2008 Fixed Description In some cases indexes could be left in a bad state after a large number of rows are deleted. Depending on the subsequent operations the problem could either have corrected itself, or lead to index corruption. Any table which ever had a row count that was 256 or more, less than its maximum row count could potentially have encountered this bug. The most common symptom was queries that returned less rows than expected. This has now been corrected. Databases that are suspected of having index corruption should be rebuilt (eg. ulunload/ulload or start with a new db and synchronize it)

CR:533478

CR Number:   533478 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 19 Jun 2008 Fixed 10.0.1 3713 19 Jun 2008 Fixed 11.0.1 1861 17 Nov 2008 Fixed Description A multi-threaded client application, using the ADO .Net provider, could have crashed, hung or leaked memory if it did not handle thread synchronization properly. This problem has now been fixed.

CR:533570

CR Number:   533570 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 19 Jun 2008 Fixed 10.0.1 3714 19 Jun 2008 Fixed 11.0.1 1862 17 Nov 2008 Fixed Description If a row was deleted, the delete rolled back, and then the row was updated, a snapshot scan may have seen the updated value before the update was committed. This has now been fixed.

CR:533600

CR Number:   533600 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 19 Jun 2008 Fixed 10.0.1 3714 19 Jun 2008 Fixed 9.0.2 3681 19 Jun 2008 Fixed 11.0.1 1862 17 Nov 2008 Fixed Description When using a derived table in a remote query, if one or more columns from the derived table were referenced in the WHERE clause of the query, and the query was going to be processed in full passthru, then the engine would have returned with a "correlation name not found" error. This problem has now been fixed.

CR:533604

CR Number:   533604 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 1411 19 Jun 2008 Fixed 10.0.1 3714 19 Jun 2008 Fixed 9.0.2 3681 19 Jun 2008 Fixed 11.0.1 1862 17 Nov 2008 Fixed Description If a multi-threaded JDBC application generated a ResultSet object on one thread, at about the same time that the underlying Statement object was closed on another thread, then the application may in very rare cases have crashed, if that ResultSet object was subsequently closed. The same problem could have occurred if the ResultSet object was generated at about the same time that the underlying Connection object was closed. This problem has now been fixed.

CR:533612

CR Number:   533612 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 24 Jun 2008 Fixed 10.0.1 3715 24 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description On a slow devices, the QAnywhere client (qaagent) would sometimes have given the following error messages at start up: "Error registering with DBLSN code: -1" and "Failed to start QAnywhere Agent (register with DBLsn)". This has been fixed so that the QAnywhere client is now much more tolerant to lengthy dblsn startup times.

CR:533724

CR Number:   533724 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 1412 24 Jun 2008 Fixed 10.0.1 3717 24 Jun 2008 Fixed 9.0.2 3683 24 Jun 2008 Fixed 11.0.1 1868 17 Nov 2008 Fixed Description The server would have crashed if the sa_locks() system procedure was executed when it was running in bulk operation mode (-b server command line option). This has been fixed. Workaround Description  Don't use -b

CR:533726

CR Number:   533726 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) 20 Jun 2008 Fixed Description Spaces and tabs were not allowed to be used before the "GO" command delimiter keyword. This has been corrected so that they are now allowed.

CR:533728

CR Number:   533728 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 1411 20 Jun 2008 Fixed 10.0.1 3715 20 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description A small window of opportunity existed in the QAnywhere server where a statement could be closed and removed from the statement cache, just as another thread was preparing the statement to be closed. This resulted in some operations being performed on a closed statement, resulting in a JDBC error. This has been fixed

CR:533729

CR Number:   533729 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 20 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description The 64-bit version of the UltraLite .NET component could have throw an "Unknown ULDbType" exception when opening a table. This has been fixed.

CR:533746

CR Number:   533746 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 1411 19 Jun 2008 Fixed 10.0.1 3715 19 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description If a download was interrupted by a network failure, it was possible for the MobiLink client (dbmlsync) to fail to create a restartable download file. Furthermore, dbmlsync would have displayed a network error to the dbmlsync log, but then attempted to apply the partial download, which would almost certainly have failed. This has been fixed so that dbmlsync now creates a restartable download file and does not attempt to apply the partial download.