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

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

CR:625496

CR Number:   625496 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2367 13 Apr 2010 Fixed Description In some cases, the server could have incorrectly returned an overflow error when computing a division of DOUBLE values. This has been fixed. A workaround is to use the following server command line "-hW OverflowError2".

CR:625515

CR Number:   625515 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2367 13 Apr 2010 Fixed 11.0.1 2422 13 Apr 2010 Fixed 10.0.1 4056 13 Apr 2010 Fixed Description Sybase Central did not allow stopping a Windows service in a "Delete pending" state. This is now fixed. The Stop menu item is now enabled for running services, regardless of whether a delete is pending.

CR:625625

CR Number:   625625 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2370 13 Apr 2010 Fixed 11.0.1 2423 13 Apr 2010 Fixed 10.0.1 4057 13 Apr 2010 Fixed Description Sybase Central would have generated an error when attempting to create a notifier, gateway or carrier with any of the following characters in its name: '[', ']', '^', '%', '_'. A similar error would have occurred when attempting to rename a notifier, gateway or carrier and any of these characters were used in the new name. This has been fixed.

CR:625641

CR Number:   625641 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) 12.0.0 2371 13 Apr 2010 Fixed 11.0.1 2423 13 Apr 2010 Fixed 10.0.1 4057 13 Apr 2010 Fixed Description The Interactive SQL utility could have reported an error on some Windows computers that its preferences or history file could not be saved. The error message quoted a file name which typically included a directory under the "Documents and Settings" directory which was not the home directory of the current user. This has been fixed. Note, this same problem has the potential to affect Sybase Central, DBConsole, and MobiLink Monitor, though their symptoms are likely to be different.

CR:625647

CR Number:   625647 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2376 14 Apr 2010 Fixed 11.0.1 2424 14 Apr 2010 Fixed Description Changing the timestamp_format option from its default value of "YYYY-MM-DD HH:NN:SS.SSS" could have caused a "Cannot convert '<value>' to a timestamp" error to have occurred when selecting the Events or Maintenance Plans folders in the tree. This has been fixed.

CR:625759

CR Number:   625759 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2424 13 Apr 2010 Fixed 10.0.1 4057 13 Apr 2010 Fixed Description When in the Procedure debugger, clicking on the header of the breakpoint icon column caused an error. This has been fixed.

CR:625800

CR Number:   625800 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2424 14 Apr 2010 Fixed 10.0.1 4057 14 Apr 2010 Fixed Description Registering the plug-in, but not loading it immediately, would have caused an exception to occur. This has been fixed.

CR:625819

CR Number:   625819 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2392 21 Apr 2010 Fixed 11.0.1 2427 21 Apr 2010 Fixed Description If checkpoints on a mirror server took a long time to complete, possibly due to a large cache with many dirty pages, then applications performing updates on the primary server could have been blocked until the checkpoint completed. This has been fixed.

CR:625866

CR Number:   625866 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2376 14 Apr 2010 Fixed 11.0.1 2424 14 Apr 2010 Fixed Description A SQL statement whose text exceeded 64K could have caused a crash.This has been corrected.

CR:625933

CR Number:   625933 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2376 14 Apr 2010 Fixed 11.0.1 2424 14 Apr 2010 Fixed Description If an application that was connected to a server running on a big endian machine attempted to query data via the Remote Data Access feature with the 64-bit ASE ODBC driver, then there is a chance the server would have incorrectly reported a truncation error. This problem has now been fixed.

CR:626091

CR Number:   626091 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) 12.0.0 2376 15 Apr 2010 Fixed 11.0.1 2424 15 Apr 2010 Fixed Description When SQLAnywhere reported the ASE label for the "Big5" character set, it incorrectly reported "Big5". SQLAnywhere now reports "cp950" as the ASE label for the Big5 character set. As far as SQL Anywhere and ICU are concerned, these two character sets are distinct (but very similar), but ASE makes no such distinction. The ASE version of the label is generally not used directly by SQL Anywhere, but is provided to users who need to use ASE libraries. Typically, a client would obtain the ASE label via a call such as db_extended_property( 'charset', 'ase' ).

CR:626145

CR Number:   626145 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2383 16 Apr 2010 Fixed Description If the Stored Procedure Debugger was connected to a database, execution of SQL Anywhere Web Service procedures for that database could have been very slow. This has been fixed.

CR:626151

CR Number:   626151 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2385 16 Apr 2010 Fixed 11.0.1 2425 16 Apr 2010 Fixed 10.0.1 4059 16 Apr 2010 Fixed Description If an application connected to an authenticated server made an external environment call, and the call took more than 30 seconds to complete, then the application would have hung. The check for ensuring that an external connection was properly authenticated was incorrect, and has now been fixed.

CR:626209

CR Number:   626209 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2384 16 Apr 2010 Fixed 11.0.1 2425 16 Apr 2010 Fixed Description In very rare cases, the server may have crashed if a simple SELECT statement that bypassed optimization used a BETWEEN predicate with a high value that was not known until execution time. This has been fixed.

CR:626241

CR Number:   626241 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2390 21 Apr 2010 Fixed 11.0.1 2427 21 Apr 2010 Fixed Description The UltraLiteJ Database Load utility (ULjLoad) would have failed with a syntax error for tables with a name that was a reserved word, and either it was involved in a foreign key, or it had data in the source XML file. This has been fixed.

CR:626255

CR Number:   626255 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2390 20 Apr 2010 Fixed 11.0.1 2427 20 Apr 2010 Fixed 10.0.1 4060 20 Apr 2010 Fixed Description If a statement in an event caused a deadlock or blocking error the first time it was executed, an assertion error (107001 Duplicate table in UPDATE statement) could have been given the next time the event was executed. Now an "invalid statement" error is given in this case. A workaround is to define the body of the event as a procedure and call the procedure from the event.

CR:626295

CR Number:   626295 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) 12.0.0 2385 19 Apr 2010 Fixed 11.0.1 2425 19 Apr 2010 Fixed 10.0.1 4059 19 Apr 2010 Fixed Description If a remote query that involved GROUP BY was executed in no-passthrough mode, and the server ran into a low memory situation, then there was a chance the query would have failed with an "update operation attempted on non-updatable remote query" error. This problem has now been fixed and the query will now successfully complete without error. Note that a workaround for this problem is to increase the amount of memory that is available to the server.

CR:626420

CR Number:   626420 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2390 20 Apr 2010 Fixed 11.0.1 2427 20 Apr 2010 Fixed Description If the server executed a 'SET rowcount' statement with a host variable inside a batch, then the server would have crashed. This has been fixed.

CR:626459

CR Number:   626459 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2388 19 Apr 2010 Fixed 11.0.1 2426 19 Apr 2010 Fixed 10.0.1 4060 19 Apr 2010 Fixed Description A UDP Gateway's property sheet would have shown the default destination port as -1. This has been corrected so that the correct value of 5001 is now shown.

CR:626460

CR Number:   626460 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) 12.0.0 2388 19 Apr 2010 Fixed Description With the Indexes folder selected in the tree, attempting to delete a foreign key and its primary constraint in a single delete operation could have crashed Sybase Central. This has been fixed.

CR:626469

CR Number:   626469 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) 12.0.0 2389 20 Apr 2010 Fixed 11.0.1 2426 20 Apr 2010 Fixed Description In rare situations, the UltraLite plugin could have caused Sybase Central to crash when being closed. This has been fixed.

CR:626474

CR Number:   626474 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) 12.0.0 2389 20 Apr 2010 Fixed 11.0.1 2426 20 Apr 2010 Fixed 10.0.1 4060 20 Apr 2010 Fixed Description The SQL cited in the "ISQL Error" window did not display blank lines. As a result, the line number in the database error message might not have corresponded to the displayed SQL if the statement contained blank lines. This has been fixed. Also, the line and column shown in the status bar of the main DBISQL window is no longer updated if the caret (insertion point) is moved in the text field that shows the SQL in the "ISQL Error" window.

CR:626480

CR Number:   626480 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2370 20 Apr 2010 Fixed 11.0.1 2426 20 Apr 2010 Fixed 10.0.1 4111 20 Apr 2010 Fixed Description An extension to the TLS protocol for session renegotiation has been made to fix a recently discovered vulnerability (RFC 5746). Although SQL Anywhere software is not directly vulnerable, third-party servers that it communicates through may be vulnerable. SA clients now support this TLS extension which will allow vulnerable third-party servers to be secured.

CR:626481

CR Number:   626481 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) 12.0.0 2389 20 Apr 2010 Fixed 11.0.1 2426 20 Apr 2010 Fixed Description The caret had to be within a statement's text for the "single step" menu item (SHIFT+F9) to work. This restriction has now been relaxed so that if the caret is in whitespace or a comment before a statement, "single step" executes the next statement. For example, consider the following code: /* Lorem ipsum */ select 123; If the caret is anywhere within the comment, or on the blank line before the SELECT statement, pressing SHIFT+F9 now executes the SELECT statement. Previously, an error message saying the caret was not on a statement would have been displayed.

CR:626617

CR Number:   626617 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2533 26 Apr 2010 Fixed 11.0.1 2428 26 Apr 2010 Fixed 12.0.1 2888 15 Sep 2010 Fixed Description Synchronization requests from clients prior to version 11 that were using a UTF8-encoded database, would have failed against 64-bit MobiLink servers running on Unix systems. This has been fixed. Note, this problem does not occur with the 32-bit versions of the MobiLink server.

CR:626622

CR Number:   626622 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2390 20 Apr 2010 Fixed Description If a spatial reference system was created with SRID a and then a subsequent SRS was created with SRID a (either by modifying or dropping/creating), then the stale settings from the first spatial reference system could have been used. The stale values would have persisted until the server was restarted. This has been fixed.

CR:626662

CR Number:   626662 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) 12.0.0 2391 21 Apr 2010 Fixed 11.0.1 2427 21 Apr 2010 Fixed 10.0.1 4061 21 Apr 2010 Fixed Description The Load Database wizard would crash on a second attempt if the first attempt failed, or was canceled, before completion. This has been fixed.

CR:626666

CR Number:   626666 Product Name:   UltraLite Product Component:   Sample Application Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2392 21 Apr 2010 Fixed 11.0.1 2427 21 Apr 2010 Fixed 10.0.1 4061 21 Apr 2010 Fixed Description The UltraLite CustDB sample application About dialog incorrectly stated "for Windows CE" for all Windows platforms. This has been removed from the dialog text.

CR:626769

CR Number:   626769 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2392 21 Apr 2010 Fixed 11.0.1 2427 21 Apr 2010 Fixed 10.0.1 4061 14 Jun 2010 Fixed Description If old transaction log files on a primary server were deleted while the server was running, subsequent BACKUP/RENAME operations would not have resulted in the copies of these logs on the mirror server being deleted. This has been fixed. A workaround is to restart both servers and perform another BACKUP/RENAME.

CR:626779

CR Number:   626779 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2393 21 Apr 2010 Fixed 11.0.1 2427 21 Apr 2010 Fixed Description Some harddisk drivers on Windows and Linux are known not to execute drive cache FLUSH commands when applications request them; however, all platforms may be affected by similar issues. When the database server shuts down because of a system shutdown, reboot or hibernate, the database server now delays a short while (3 seconds) after the last I/O is performed to allow a little bit of time for cached data in the drives to be written to the disk. On UNIX platforms, shutting down the server via SIGTERM is assumed to be due to a system shutdown or reboot.

CR:626951

CR Number:   626951 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4061 26 Apr 2010 Fixed 11.0.1 2428 26 Apr 2010 Fixed 12.0.0 2395 26 Apr 2010 Fixed Description The iAS Oracle ODBC driver could not detect connection status correctly when a connection was forcibly disconnected by the server. Due to this problem, an application, such as the MobiLink server, might not re-establish a new connection and would have reported the same errors repeatedly. This problem is fixed now.

CR:627054

CR Number:   627054 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2400 26 Apr 2010 Fixed 11.0.1 2429 26 Apr 2010 Fixed 10.0.1 4063 26 Apr 2010 Fixed Description If the system procedure sa_describe_query() was executed with null as the query parameter then the server would have crashed. This has been fixed.

CR:627061

CR Number:   627061 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) 12.0.0 2396 26 Apr 2010 Fixed 11.0.1 2428 26 Apr 2010 Fixed Description The table on the Synchronization Information page of the Database property sheet was editable, although changing the values had no effect. This has been corrected so that the table is now read-only.

CR:627062

CR Number:   627062 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2405 28 Apr 2010 Fixed 11.0.1 2405 28 Apr 2010 Fixed 10.0.1 4064 28 Apr 2010 Fixed Description An INSERT ... ON EXISTING UPDATE DEFAULTS OFF statement did not update columns defined with DEFAULT LAST USER. This has been fixed. Workaround Description  None.

CR:627167

CR Number:   627167 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2400 27 Apr 2010 Fixed Description Because concatenation did not coerce operands to character, a ClassCastException could have been thrown when a non-character operand of concatenation was given. This has been corrected.

CR:627228

CR Number:   627228 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2430 27 Apr 2010 Fixed 10.0.1 4063 27 Apr 2010 Fixed Description Under very rare circumstances the server could have crashed at startup while updating the SYSHISTORY table. This has been fixed.

CR:627238

CR Number:   627238 Product Name:   UltraLite Product Component:   Sample Application Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2401 26 Apr 2010 Fixed 11.0.1 2429 26 Apr 2010 Fixed 10.0.1 4063 26 Apr 2010 Fixed Description The Include directory reference for the UltraLite CustDB sample on Windows Mobile 6 platforms was incorrect. The Windows Mobile 6 platform Include directory pointed to the %sqlanyX%\h directory, but should have pointed to %sqlanyX%\SDK\Include. While correcting this, it was noted that there were inconsistencies in the quoting of the Include directory across the projects. Now all references are quoted.

CR:627266

CR Number:   627266 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2445 21 May 2010 Fixed 11.0.1 2438 21 May 2010 Fixed 10.0.1 4073 21 May 2010 Fixed 9.0.2 3966 21 May 2010 Fixed Description An "Out of Memory" assertion may have been raised by the SQL Anywhere OLE DB provider, which may have been indicative of heap corruption. This problem may arise when binding parameters that are described as DBTYPE_IUNKNOWN (a type used for LONG VARCHAR parameters). This problem has been fixed.

CR:627381

CR Number:   627381 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2403 27 Apr 2010 Fixed 11.0.1 2430 27 Apr 2010 Fixed Description The changes for Engineering case 619360 introduced a problem such that when creating a database on a BlackBerry SDCard, or flash file store (file:///store), and then releasing the database connection without doing any reads, a Null Pointer exception could have resulted. For example: conn = DatabaseManager.createDatabase( config ); conn.release(); This has now been fixed.

CR:627392

CR Number:   627392 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2404 27 Apr 2010 Fixed Description Selecting from a DML derived table that used INSERT ON EXISTING UPDATE, would not have returned any rows for rows that were updated. However, the rows were still updated as expected. This has been fixed. Note, that you the OLD values for rows that have been updated were not visible; the INSERT derived table only supports the FINAL correlation. To see both the OLD and FINAL row values, use the MERGE statement instead of the INSERT statement.

CR:627397

CR Number:   627397 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2571 19 Aug 2010 Fixed 11.0.1 2482 19 Aug 2010 Fixed 12.0.1 3010 15 Sep 2010 Fixed Description In very rare cases the server may have crashed when releasing a query plan of a DML statement from the plan cache, and the statement had triggers and publications and used string or numeric values. This has been fixed.

CR:627403

CR Number:   627403 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) 12.0.0 2421 10 May 2010 Fixed 11.0.1 2427 10 May 2010 Fixed Description If the Relay Server Outbound Enabler (RSOE) lost connectivity to the Relay Server, and was attempting to restart the worker threads at the same time that it was about to time out a thread working an active request, it was possible for the RSOE to have crashed. This has now been fixed.

CR:627407

CR Number:   627407 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2445 21 May 2010 Fixed 11.0.1 2438 21 May 2010 Fixed 10.0.1 4073 21 May 2010 Fixed 9.0.2 3966 21 May 2010 Fixed Description .NET applications using the SQL Anywhere OLE DB provider may have failed with the following error for OleDbDataReader.Close(): "Reader Exception: Attempted to read or write protected memory. This is often an indication that other memory is corrupt." This has been fixed.

CR:627526

CR Number:   627526 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) 12.0.0 2406 28 Apr 2010 Fixed 11.0.1 2430 28 Apr 2010 Fixed Description Attempts to create, edit, or modify Windows Mobile proxy ports from the "Connect" dialog would have silently failed on Windows Vista or Windows 7 if user access control (UAC) was enabled. This has been fixed.

CR:627527

CR Number:   627527 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2406 29 Apr 2010 Fixed Description Selecting from a DML derived table over a table that had computed columns, would have crashed the server. This has been fixed.

CR:627528

CR Number:   627528 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2406 28 Apr 2010 Fixed 11.0.1 2430 28 Apr 2010 Fixed Description If the Support utility (dbsupport) attempted to send an email, either by explicit command using the -cet option or when a crash occurred, and the configured mail server was either non-existent, running on a different port, or down at the time of the attempt (i.e. the connection to the mail server failed), then dbsupport would have crashed. This has been fixed.

CR:627544

CR Number:   627544 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2406 29 Apr 2010 Fixed Description When deploying a Synchronization Model to files, the generated .bat or .sh files would have invoked programs (such as dbisql and dbmlsync) without specifying the program's folder, relying on the execution search path to find the program. If an incompatible version of the program was found earlier in the path, it would have been used instead of the compatible version. A workaround was to put the compatible version earlier in the path. This has been fixed. Now the SQLANYnn environment variable (where 'nn' is the version number) is used if it is defined. Also, if the 64-bit version of a program exists it will be used instead of the 32-bit version.

CR:627580

CR Number:   627580 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2407 29 Apr 2010 Fixed Description Calling ST_IntersectsRect would have returned incorrect results if the second point was not above and to the right of the first point. Example: In the following query, both expr1 and expr2 should return true (the docs state that they are equivalent). select ST_Geometry::ST_GeomFromWKT('Polygon ((1 1, 3 1, 3 3, 1 3, 1 1))', 0) rect1 , new ST_Point( 0, 2, 0 ) p1 , new ST_Point( 2, 0, 0 ) p2 , new ST_Polygon( p1, p2 ) rect2 , rect1.ST_Intersects( rect2 ) expr1 , rect1.ST_IntersectsRect( p1, p2 ) expr2 ; Result: rect1,p1,p2,rect2,expr1,expr2 Polygon ((1 1, 3 1, 3 3, 1 3, 1 1)),Point (0 2),Point (2 0),Polygon ((0 0, 2 0, 2 2, 0 2, 0 0)),true,false This has been fixed.

CR:627631

CR Number:   627631 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) 12.0.0 2543 07 Jun 2010 Fixed 11.0.1 2445 07 Jun 2010 Fixed 10.0.1 4079 07 Jun 2010 Fixed 12.0.1 2931 15 Sep 2010 Fixed Description In rare cases, a database server used for mirroring could have crashed when the connection to its partner was dropped. This has been fixed.

CR:627634

CR Number:   627634 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2406 29 Apr 2010 Fixed 11.0.1 2430 29 Apr 2010 Fixed 10.0.1 4064 29 Apr 2010 Fixed 9.0.2 3963 29 Apr 2010 Fixed Description The ODBC driver did not support setting of the SQL_ATTR_METADATA_ID attribute for connections using SQLSetConnectAttr(). This setting governs how the string arguments of catalog functions are treated. However, the driver does support this attribute at the statement level using SQLSetStmtAttr(). For SQLSetConnectAttr(), the ODBC driver returned a "driver not capable" error. This problem has been corrected. If the setting for SQL_ATTR_METADATA_ID is SQL_TRUE, the string argument of catalog functions are treated as identifiers. The case is not significant. For nondelimited strings, the driver removes any trailing spaces and the string is folded to uppercase. For delimited strings, the driver removes any leading or trailing spaces and takes literally whatever is between the delimiters. If the setting is SQL_FALSE, the string arguments of catalog functions are not treated as identifiers. The case is significant. They can either contain a string search pattern or not, depending on the argument. The default value is SQL_FALSE. The following example changes the default setting for the entire connection. rc = SQLSetConnectAttr( hdbc, SQL_ATTR_METADATA_ID, (SQLPOINTER)SQL_TRUE, SQL_IS_UINTEGER ); This setting is important for case-sensitive databases. For example, the table name "customers" does not match the table name "Customers" in a function such as SQLPrimaryKeys() unless the SQL_ATTR_METADATA_ID attribute has been set to SQL_TRUE.

CR:627649

CR Number:   627649 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2545 16 Jun 2010 Fixed 11.0.1 2451 16 Jun 2010 Fixed 12.0.1 2933 15 Sep 2010 Fixed Description The PHP driver would have crashed when trying to open multiple result sets using SASQL_USE_RESULT or sasql_real_query() and sasql_use_result(). This has been fixed.

CR:627657

CR Number:   627657 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.1 2431 03 May 2010 Fixed Description The list of SQL functions suggested by the editor's Text Completer was incomplete when connected to a version 11.0 database. This has been fixed.

CR:627672

CR Number:   627672 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2408 03 May 2010 Fixed 11.0.1 2431 03 May 2010 Fixed Description Running the VALIDATE INDEX statement would have committed any previously uncommitted transactions. The VALIDATE INDEX statement no longer performs a COMMIT on its connection.

CR:627679

CR Number:   627679 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2408 03 May 2010 Fixed Description Queries which used a spatial predicate in any comparison other than "= 1" could have returned a subset of the correct result set. For example, queries using any of the following comparisons in the WHERE clause could have returned too few rows: geom1.ST_xxx( geom2 ) <> 1 geom1.ST_xxx( geom2 ) = 0 geom1.ST_xxx( geom2 ) = ( subquery ) geom1.ST_xxx( geom2 ) = geom3.ST_yyy( geom4 ) where ST_xxx and ST_yyy could be any of the following spatial predicates: ST_Intersects ST_IntersectsFilter ST_IntersectsRect ST_Overlaps ST_Contains ST_ContainsFilter ST_Within ST_WithinFilter ST_Covers ST_CoversFilter ST_CoveredBy ST_CoveredByFilter ST_Equals ST_EqualsFilter ST_OrderingEquals This has now been fixed.

CR:627756

CR Number:   627756 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) 12.0.0 2409 03 May 2010 Fixed 11.0.1 2431 03 May 2010 Fixed 11.0.0 1654 03 May 2010 Fixed Description Copying and pasting a table in Sybase Central would have failed if the table had a primary key with a comment and the owner of the table was changed in the Table Duplicate dialog. This has been fixed.

CR:627776

CR Number:   627776 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2442 03 May 2010 Fixed 11.0.1 2436 03 May 2010 Fixed 10.0.1 4072 03 May 2010 Fixed Description On big-endian machines, the 64-bit iAS ODBC driver could have returned random values when an application was trying to retrieve the following statement attributes: SQL_ATTR_METADATA_ID SQL_ATTR_ROW_NUMBER SQL_ATTR_ROW_ARRAY_SIZE SQL_ATTR_PARAMSET_SIZE SQL_ATTR_MAX_LENGTH SQL_ATTR_MAX_ROWS The driver was using SQLUINTEGER for these statement attributes. It has been corrected to now use SQLULEN.

CR:627780

CR Number:   627780 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) 12.0.0 2410 03 May 2010 Fixed 11.0.1 2431 03 May 2010 Fixed 10.0.1 4065 03 May 2010 Fixed Description The Start Server in Background utility (dbspawn) would have failed to start a database server if the full path to the server executable was given and that path contained a space. This has now been fixed.

CR:627784

CR Number:   627784 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2410 03 May 2010 Fixed Description When creating a Synchronization Model, clearing the Subscription Name field or the Synchronization Field would caused an inappropriate error message. This has been fixed.

CR:627788

CR Number:   627788 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2410 03 May 2010 Fixed 11.0.1 2431 03 May 2010 Fixed 10.0.1 4065 03 May 2010 Fixed Description Selecting the database property "name" for viewing using the SQL Anywhere Console utility would have prevented the list of database properties from refreshing. This has been fixed.

CR:627887

CR Number:   627887 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Windows 2000 Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2429 10 May 2010 Fixed Description Under certain circumstances, newly created MobiLink projects could have appeared twice in the list of projects. This has been fixed.

CR:627895

CR Number:   627895 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2417 04 May 2010 Fixed 11.0.1 2433 04 May 2010 Fixed Description Since the change made for Engineering case 616657, very large indexes (3 or more levels) may have become corrupted resulting in an illegal cast java error. When the page size was increased, the number of rows in the table required to trigger this problem increased significantly. A work around would be to increase the page size. This has now been fixed.

CR:627956

CR Number:   627956 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) 12.0.0 2416 04 May 2010 Fixed 11.0.1 2433 04 May 2010 Fixed Description When executing a batch of statements, if an INPUT USING statement failed to connect to the source database, an error message was displayed, but execution continued unconditionally. Now, the "on_error" setting is respected.

CR:627968

CR Number:   627968 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2418 05 May 2010 Fixed Description If a FOR statement used a CALL PROCEDURE(), then the server could have crashed while executing the statement. This has been fixed.

CR:628115

CR Number:   628115 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2418 05 May 2010 Fixed Description Invalid options to ST_AsBinary() could have caused the server to crash with a stack overflow. This has been fixed.

CR:628127

CR Number:   628127 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2419 06 May 2010 Fixed Description When creating a new remote database schema in a synchronization model from a SQL Anywhere consolidated database schema containing VARBIT or LONG VARBIT columns, those columns would be converted to VARCHAR and LONG VARCHAR columns. This has been fixed. Now VARBIT and LONG VARBIT columns are copied to new SQL Anywhere remote databases. UltraLite does not support VARBIT or LONG VARBIT types, so such columns are still converted for new UltraLite databases, but a warning is now given.

CR:628176

CR Number:   628176 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2434 06 May 2010 Fixed Description The changes for Engineering case 626303 caused the rollback after a synchronization failure to possibly corrupt the database. This has been corrected.

CR:628253

CR Number:   628253 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2421 10 May 2010 Fixed 11.0.1 2434 10 May 2010 Fixed 10.0.1 4067 10 May 2010 Fixed Description The Interactive SQL utility option isql_print_result_set was being ignored. This has been corrcted so that it is once again respected.

CR:628256

CR Number:   628256 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) 12.0.0 2420 06 May 2010 Fixed 11.0.1 2434 06 May 2010 Fixed Description The Interactive SQL utility (dbisql) could have reported an internal error if a column header for a result was clicked, dbisql had not already cached the entire result and then fetching the remaining rows was canceled. This has been fixed.

CR:628275

CR Number:   628275 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) 12.0.0 2420 06 May 2010 Fixed 11.0.1 2434 06 May 2010 Fixed 10.0.1 4067 06 May 2010 Fixed Description Clicking Finish in the Load Database wizard would have caused Sybase Central to crash if a database id was not specified on the last page of the wizard. This has been fixed.

CR:628295

CR Number:   628295 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2442 19 May 2010 Fixed Description Select from DML derived tables were allowed in two contexts that have now been excluded by this fix. One context was correlated subqueries. The semantics of a correlated DML statement are poorly defined and hard to implement. The following query is not allowed: select * from (insert into newids select outerproduct.id) referencing (final as insertedids), product as outerproduct The other context was common table expressions, again because the semantics are unclear.

CR:628304

CR Number:   628304 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2421 10 May 2010 Fixed 11.0.1 2434 10 May 2010 Fixed Description If the MINIMUM TERM LENGTH setting of the text configuration used to build a text index was changed to a value greater than 1, prefix terms in phrase queries of full text search could have behaved differently depending on their position in the phrase. This has been fixed.

CR:628436

CR Number:   628436 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) 12.0.0 2424 10 May 2010 Fixed 11.0.1 2435 10 May 2010 Fixed 10.0.1 4069 10 May 2010 Fixed Description In extremely rare timing dependent cases, if a communication error occurred on a mirror or diagnostic tracing server-to-server connection, the server could have crashed, failed an assertion or hung. This has been fixed.

CR:628443

CR Number:   628443 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) 12.0.0 2424 10 May 2010 Fixed 11.0.1 2434 10 May 2010 Fixed Description Reconfiguring the fast launchers (Interactive SQL and Sybase Central) could have caused the launchers to become unresponsive. The symptom was that there could have been multiple dbisql.exe / scjview.exe processes on the computer rather than just one. This has now been fixed.

CR:628553

CR Number:   628553 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2428 10 May 2010 Fixed 11.0.1 2435 10 May 2010 Fixed Description Execution of an INPUT statement which used an explicit encocoding of "utf-16" would have worked if the input file had the same endianness as the platform, but would have failed if the endianess was different, even if the byte-order-mark was present in the file. This has been fixed.

CR:628564

CR Number:   628564 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2549 05 Jul 2010 Fixed 11.0.1 2459 05 Jul 2010 Fixed 12.0.1 2960 15 Sep 2010 Fixed Description The Interactive SQL utility would have returned a function sequence error when connected to an UltraLite database and a query was executed if the Commit after every statement option was checked (under Tools/Options/UltraLite/Commands). This has now been fixed. A workaround is to uncheck the Commit after every statement option.

CR:628573

CR Number:   628573 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.1 2456 22 Jun 2010 Fixed 10.0.1 4088 22 Jun 2010 Fixed Description The system procedure xp_startsmtp may have returned error code 104 depending on the SMTP server being used. This has been fixed.

CR:628587

CR Number:   628587 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) 12.0.0 2431 11 May 2010 Fixed 11.0.1 2435 11 May 2010 Fixed 10.0.1 4069 11 May 2010 Fixed Description A multithreaded application could have failed to load the unmanaged dll. This has now been corrected.

CR:628687

CR Number:   628687 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2430 11 May 2010 Fixed Description When converting a string (EWKT or EWKB) to a geometry, the assertion 100103 could have failed if the embedded SRID was not known in the database. The assertion would have caused the current request to fail instead of returning an appropriate error message. This has been fixed; such conversions will now return the error: -1409 "Unknown spatial reference system (%1)".

CR:628705

CR Number:   628705 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2430 11 May 2010 Fixed Description In some cases, the substitution parameters for error messages from spatial operations could have been incorrect. For example, the error message for the following query could incorrectly report: "A geometry with SRID= is not supported for method 4326." select new st_point(0, 0, 4326) p from sys.dummy where p.ST_Envelope().st_intersectsfilter(p) = 1 This has been fixed. The following message is now returned: "A geometry with SRID=4326 is not supported for method ST_Envelope()."

CR:628735

CR Number:   628735 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2435 17 May 2010 Fixed 11.0.1 2436 17 May 2010 Fixed Description A full text query with a non-alphanumeric character in a prefix string could have caused a server crash. This has been fixed.

CR:628836

CR Number:   628836 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2432 12 May 2010 Fixed 11.0.1 2436 12 May 2010 Fixed Description Shutting down a database could have caused an assertion failed error 104301 if a GRANT PROFILE had failed because the "diagnostics" user was not a group. This has been fixed.

CR:628843

CR Number:   628843 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2433 14 May 2010 Fixed 11.0.1 2436 14 May 2010 Fixed Description If an application connected to a 64-bit Linux server subsequently used the ASE ODBC driver to query proxy tables mapped to an ASE server, and the proxy tables contained long varchar or long binary data, then the long data might have been returned with extra characters or bytes. This problem has now been fixed.

CR:628947

CR Number:   628947 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2433 14 May 2010 Fixed Description When transforming a geometry using a Mercator-style projection, the transform could have failed with an error such as the following: Error -20 during transformation. For example, if the geometry contained points close to the poles of the Earth, this error could have been returned. This error could also have been returned when viewing a geometry in the spatial viewer. The Mercator projection (and other cylindrical projections) can not transform polar points because the y coordinate would need to be infinite (cylindrical projections treat the Earth as a rubber balloon in a glass cylinder and inflate the balloon; the projection is taken from the sides of the glass cylinder, and the polar points never touch the sides). This has been fixed; when transforming a geometry from a lat/long system to a Cartesian system, if a point close to the North or South pole fails to transform the server moves the latitude of the point a small distance away from the pole along the same longitude. The distance moved is slightly more than (1e-10 radians). This shifting is used only if the point fails to transform without shifting.

CR:628952

CR Number:   628952 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2433 14 May 2010 Fixed 11.0.1 2436 14 May 2010 Fixed 10.0.1 4070 14 May 2010 Fixed Description The MobiLink server would have shown the following error: Invalid Date-time segment. Year value out of range and aborted any synchronization requests, if the consolidated database was running on an ASE server with a database that was using a multi-byte charset, and the MobiLink server was running on a Windows system that was using a non-English Date format. This problem has now been fixed.

CR:629053

CR Number:   629053 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2539 14 May 2010 Fixed 11.0.1 2436 14 May 2010 Fixed 12.0.1 2911 15 Sep 2010 Fixed Description When sorting a column in the Data Details panel, an error could have occurred stating "Error reading row. Accessing a closed connection object." This has been fixed.

CR:629056

CR Number:   629056 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2546 28 Jun 2010 Fixed 11.0.1 2456 28 Jun 2010 Fixed 10.0.1 4093 28 Jun 2010 Fixed 12.0.1 2954 15 Sep 2010 Fixed Description Attempting to connect with the connection parameter DatabaseName (DBN), but not DatabaseFile (DBF), to a database that was not running on a network server could have incorrectly resulted in the error "Request to start/stop database denied". This error could have also occurred on the personal server if the -gd option was used. This has been fixed so that this now results in the "Specified database not found" error.

CR:629058

CR Number:   629058 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2539 17 May 2010 Fixed 11.0.1 2436 17 May 2010 Fixed 10.0.1 4070 17 May 2010 Fixed 12.0.1 2910 15 Sep 2010 Fixed Description A Java VM running inside the MobiLink server could have run out of memory if the server had many requests with different script versions and some sync scripts made calls to DBConnectionContext.getConnection(). This has been fixed.

CR:629073

CR Number:   629073 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2437 17 May 2010 Fixed 11.0.1 2436 17 May 2010 Fixed 10.0.1 4071 17 May 2010 Fixed Description If a stored procedure or user-defined function contained a statement that referenced a connection level variable (created with CREATE VARIABLE), then it was possible for the statement to behave improperly if plan caching was used by the server. The statement could have used the NULL SQL value for the variable instead of giving an error if the variable were dropped, and the statement could have used incorrect type information if the variable was dropped and then recreated with a different data type. This has been fixed.

CR:629078

CR Number:   629078 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) 12.0.0 2437 17 May 2010 Fixed 11.0.1 2436 17 May 2010 Fixed Description Sybase Central could have run out of memory when displaying a view, trigger, procedure, event or external environment object in the right pane. This would normally have occurred only if the Tasks pane was showing in the left pane. This has been fixed.

CR:629153

CR Number:   629153 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) 12.0.0 2440 17 May 2010 Fixed 11.0.1 2437 17 May 2010 Fixed 10.0.1 4072 17 May 2010 Fixed Description If an application attempted to start an external environment session, and other connections were being established, or were closing, at exactly the same time, then there was a very small chance that the server could have crashed. This problem has now been fixed.

CR:629277

CR Number:   629277 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) 12.0.0 2442 18 May 2010 Fixed 11.0.1 2438 18 May 2010 Fixed Description The QAnywhere Standalone Clients would not synchronize when expected to in two cases. The first case occurred if a sync request was made while another synchronization was already taking place. It was expected that another sync will begin once the current one has finished, but this did not always happen. The second case occurred if a sync request was made while using a Transactional Manager. It was expected that only sync requests resulting from changes to the database will be delayed until the transaction is committed. However, this delay was occurring for other types of sync requests as well. These two cases have now been fixed.

CR:629284

CR Number:   629284 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2442 18 May 2010 Fixed 11.0.1 2438 18 May 2010 Fixed 10.0.1 4072 18 May 2010 Fixed Description The Visual Studio "Add Connection" wizard will display SQL Anywhere and Adaptive Server Anywhere ODBC Data Source names in the pick list when the SQL Anywhere .NET provider is used for the connection. SQL Anywhere integration with Visual Studio has been improved to also show Sybase IQ ODBC Data Source names in the pick list.

CR:629304

CR Number:   629304 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2442 18 May 2010 Fixed 11.0.1 2438 18 May 2010 Fixed 10.0.1 4072 18 May 2010 Fixed Description The values for DataSourceProductVersion and DataSourceProductVersionNormalized returned by the SAConnection.GetSchema method didn't match the ADO.NET specification. The normalized version string should have been like nn.nn.nn.nnnn. For example, SQL Server 2008 would return "DataSourceProductVersion = 10.00.1600, DataSourceProductVersionNormalized = 10.00.1600". SQL Anywhere was returning "DataSourceProductVersion = 12.0.0.1234, DataSourceProductVersionNormalized = 12.0.0". This has now been corrected.

CR:629312

CR Number:   629312 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) 18 May 2010 Fixed Description When using the Python driver (sqlanydb.py), inserting a value larger than 2^32 into a BIGINT column would have resulted in a truncated integer value. This has been fixed.

CR:629411

CR Number:   629411 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2574 05 Jul 2010 Fixed 11.0.1 2459 17 Aug 2010 Fixed 12.0.1 3018 15 Sep 2010 Fixed Description The database option UUID_HAS_HYPHENS has been re-added. It can have the values On (default) and Off. If a uniqueidentifer value is converted to a string, then the string contains hyphens if the option value is On.

CR:629415

CR Number:   629415 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.0 2540 19 May 2010 Fixed Description When deleting Agent events from a consolidated database there is a prompt for a date. Events that were created BEFORE this date are deleted. Messages ON this date would also have been deleted if their timestamp was before the current time of day when the user elected to delete the Agent events. This has been fixed.

CR:629417

CR Number:   629417 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) 12.0.0 2540 19 May 2010 Fixed 11.0.1 2438 19 May 2010 Fixed 10.0.1 4073 19 May 2010 Fixed 12.0.1 2916 15 Sep 2010 Fixed Description If an application attempted to execute a Java external environment procedure, and the target method was part of a class that had a private constructor, then calling the Java external environment procedure would have failed with an IllegalAccessException. This problem has now been fixed.

CR:629437

CR Number:   629437 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2540 19 May 2010 Fixed 12.0.1 2916 15 Sep 2010 Fixed Description The user name in the status message in the Installing the MobiLink System Setup dialog would have been truncated if it was more than a few characters. This has been improved, although very long names may still be truncated. A workaround is to wait until the task finished, as the completion dialog shows the full name.

CR:629453

CR Number:   629453 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2540 20 May 2010 Fixed 12.0.1 2916 15 Sep 2010 Fixed Description when editing table data in the Results pane, clicking the "Edit in Window" menu item could have left the focus on the table rather than moving it to the resulting editing window. This has been fixed. This problem affected Linux systems only.

CR:629458

CR Number:   629458 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) 12.0.0 2540 20 May 2010 Fixed 11.0.1 2438 20 May 2010 Fixed 10.0.1 4073 20 May 2010 Fixed 12.0.1 2916 15 Sep 2010 Fixed Description Clicking the Close button in the title bar of the Query Editor was considered equivalent to clicking the OK button. This was incorrect; it should have been equivalent to clicking the Cancel button. This has been fixed.