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

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

CR:489917

CR Number:   489917 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) 10.0.1 3633 30 Jan 2008 Fixed Description Certain specific forms of statements could have caused the server to crash, or to report assertion failures 101504, 101514, or 101515. This has been fixed.

CR:490036

CR Number:   490036 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1129 12 Feb 2008 Fixed 10.0.1 3641 12 Feb 2008 Fixed Description When making continuous ODBC connections and disconnections using SQLConnect and SQLDisconnect, a memory leak would have occurred in the application. The process heap would have continued to grow as the application looped. To reproduce the memory leak, the application must have allocated and freed environment and connection handles around the SQLConnect and SQLDisconnect calls, to ensure that the SQL Anywhere ODBC driver was loaded and unloaded from memory. This problem has been fixed.

CR:490092

CR Number:   490092 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 1015 29 Jan 2008 Fixed 10.0.1 3634 29 Jan 2008 Fixed Description In rare cases, attempting to create a procedure or event containing the BACKUP DATABASE statement would have caused a server crash. The crash was due to an unparsing error, which has now been corrected.

CR:490180

CR Number:   490180 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) 10.0.1 3634 29 Jan 2008 Fixed Description If a query used certain types of expressions that used strings, and a parallel execution strategy was selected by the query optimizer, then the server could have crashed under certain conditions. This has been fixed. The problematic expressions include the following: COMPRESS CONNECTION_EXTENDED_PROPERTY CSCONVERT DATEFORMAT DB_EXTENDED_PROPERTY DB_ID DECOMPRESS DECRYPT ENCRYPT EVENT_CONDITION EVENT_PARAMETER EXTENDED_PROPERTY GET_IDENTITY HASH HEXTOINT HTTP_HEADER HTTP_VARIABLE ISDATE ISNUMERIC LIKE LOCATE NEXT_HTTP_HEADER NEXT_HTTP_VARIABLE NEXT_SOAP_HEADER PROPERTY_NAME PROPERTY_NUMBER REPLACE REVERSE SOAP_HEADER SORTKEY TO_CHAR TO_NCHAR UNICODE USER_ID VAREXISTS WRITE_CLIENT_FILE

CR:490192

CR Number:   490192 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 1016 29 Jan 2008 Fixed 10.0.1 3634 29 Jan 2008 Fixed Description The embedded SQL OPEN statement did not allow any of the snapshot isolation levels to be specified in the ISOLATION LEVEL clause. This has been corrected. The workaround is to use the isolation_level option.

CR:490209

CR Number:   490209 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows CE 2.11 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1137 29 Feb 2008 Fixed 10.0.1 3650 29 Feb 2008 Fixed 9.0.2 2553 29 Feb 2008 Fixed Description An error would have been reported when some valid options were entered in the dbmlsync option dialog on CE. The options affected included -q -Q -qc -o -ot -os and -wc. This has been fixed.

CR:490210

CR Number:   490210 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 1016 29 Jan 2008 Fixed 10.0.1 3634 29 Jan 2008 Fixed Description When viewing the properties of a table in the UltraLite plug-in for Sybase Central, it was possible to change the tables synchronization type of Normal, Always or Never. Doing this would have created a new table with a different suffix (either empty, _nosync or _allsync), however the original table would not have been dropped. This has been fixed.

CR:490227

CR Number:   490227 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1016 30 Jan 2008 Fixed 10.0.1 3634 30 Jan 2008 Fixed Description The SQL Preprocessor (sqlpp) could have generated incorrect code for SET OPTION statements. Correct code was generated for single SET OPTION statements, but incorrect code was generated if the SET OPTION was contained within a batch, procedure definition, etc. This has been fixed.

CR:490229

CR Number:   490229 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1018 30 Jan 2008 Fixed 10.0.1 3635 30 Jan 2008 Fixed Description An application using the iAS ODBC driver for Oracle may have crashed if a SQL statement caused an error on the Oracle database server or the OCI library, and if the error message returned from the Oracle server or the OCI library was greater than 466 bytes in length. This problem is now fixed.

CR:490303

CR Number:   490303 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 1129 19 Feb 2008 Fixed Description The server allows for objects, such as views, to be disabled. When a view is disabled, its definition is maintained in the database in an uncompiled state, and the view is not available to be referenced by queries. Once disabled, a view needs to be explicitly enabled before it becomes usable again. The server now allows users to grant permissions on disabled objects. Any granted permissions are retained in the database and become effective once the object is enabled.

CR:490312

CR Number:   490312 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1021 04 Feb 2008 Fixed 10.0.1 3635 04 Feb 2008 Fixed Description Attempting to unload a database using the Sybase Central Unload wizard, that was not currently connected to, into an XML or SQL file would have failed with a null pointer exception. This has been fixed.

CR:490412

CR Number:   490412 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 3624 21 Feb 2008 Fixed Description In very rare, timing-related circumstances, the server could have become extremely slow when processing Java requests in the database, or disconnects from connections with attached Java VMs. This may have happened if a large number of connections were executing Java functions or if connections with attached Java VMs received a cancel. This has now been fixed.

CR:490471

CR Number:   490471 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1021 04 Feb 2008 Fixed 10.0.1 3635 04 Feb 2008 Fixed Description When connected to two UltraLite databases and attempting to unload the first into the second, when the Finish was clicked on the page that asked for the destination database, the wizard would not have noticed the change in the selected destination database on that page and then tried to load into the default destination database, which in this case was the same database as the source database. This has been fixed so that the wizard now correctly records the selection, and/or correctly pops up a dialog letting the user know that the source database is the same as the destination database.

CR:490481

CR Number:   490481 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1021 04 Feb 2008 Fixed 10.0.1 3635 04 Feb 2008 Fixed Description When attempting to shut down a MobiLink server using mlstop, as well as pressing 'q' on UNIX or clicking on the 'Shut down' button on Windows simultaneously, then the MobiLink server could have crashed. This problem was due to a race condition, which has now been corrected.

CR:490504

CR Number:   490504 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 1022 04 Feb 2008 Fixed 10.0.1 3636 04 Feb 2008 Fixed Description If a Hash Group By algorithm did not have enough memory to operate, and it was converted to a low-memory execution strategy, it was possible for grouped rows to be returned even though they did not match the HAVING clause specified in the statement. This has been fixed.

CR:490564

CR Number:   490564 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 1031 08 Feb 2008 Fixed 10.0.1 3639 08 Feb 2008 Fixed 9.0.2 3618 08 Feb 2008 Fixed Description A recordset update may have failed when one of more column values were null. The OLEDB provider failed to correctly identify the primary key columns in a table, and this resulted in an UPDATE statement containing a WHERE clause that was overly complex. This problem has now been fixed.

CR:490590

CR Number:   490590 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1024 04 Feb 2008 Fixed 10.0.1 3637 04 Feb 2008 Fixed Description Synchronizations using TLS, HTTP, or compression could have failed. Also, mlfiletransfer, dblsn, and all components connecting to the MobiLink server could have failed. The failure manifestation was highly data-dependent, but the most likely error was a protocol error. Synchronizations from older (ie. versions 8 & 9) clients were not affected by this problem. In the extremely unlikely event that the lost bytes go unnoticed by the other end of the network connection, or internally in MobiLink server, then there might be lost data. For example, in a row operation, a sequence of bytes in the middle of a VARCHAR column value may have been removed. This has been fixed.

CR:490594

CR Number:   490594 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 1024 04 Feb 2008 Fixed 10.0.1 3637 04 Feb 2008 Fixed Description In a low memory situation, the Hash Broup By algorithm could have failed to compute the value of composite aggregates (eg AVG )for some groups. The value of the composite aggregate was incorrectly set to NULL. This has been fixed.

CR:490798

CR Number:   490798 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 1018 05 Feb 2008 Fixed 10.0.1 3635 05 Feb 2008 Fixed Description In a TOP n START AT m clause, the values of n and m were previously restricted to being constants or variables. They are now allowed to be host variable references. For example: select top ? table_name from SYS.SYSTAB order by table_id

CR:490862

CR Number:   490862 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3641 13 Feb 2008 Fixed 9.0.2 3620 13 Feb 2008 Fixed Description A QAnywhere .NET application could have crashed with a memory access vio;ation when terminating. This was due to a race condition, which has been fixed.

CR:490909

CR Number:   490909 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1029 06 Feb 2008 Fixed Description If a cursor for a statement containing ORDER BY was opened with the option Ansi_update_constraints set to a value other than 'off', then the statement could have incorrectly been opened as READ ONLY, even if cursor flags requesting an updatable cursor were specified. This has been fixed.

CR:490930

CR Number:   490930 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 1030 07 Feb 2008 Fixed 10.0.1 3639 07 Feb 2008 Fixed Description Under very rare circumstance, and likely with heavy concurrency, the server could have crashed. A race condition in the row locking code has been corrected.

CR:491010

CR Number:   491010 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1141 04 Mar 2008 Fixed 10.0.1 3652 04 Mar 2008 Fixed Description The database option database_authentication defined in saopts.sql, or authenticate.sql, could have silently failed to have been set during a create or upgrade of a database. Statement in the scripts used during a create or update of a database were ignored if either the 'go' terminator was not lowercase, or an end of file was reached with no 'go' following the statement. This has been fixed.

CR:491015

CR Number:   491015 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 1034 11 Feb 2008 Fixed 10.0.1 3641 11 Feb 2008 Fixed Description A server with AWE enabled (ie -cw) could have crashed when running a database containing encrypted tables. This has been corrected.

CR:491104

CR Number:   491104 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1036 12 Feb 2008 Fixed 10.0.1 3641 12 Feb 2008 Fixed Description Any modifications to the client message store properties, after the clients first synchronization, would not have been propagated to the server message store as expected. This had been fixed.

CR:491108

CR Number:   491108 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 1129 12 Feb 2008 Fixed 10.0.1 3641 12 Feb 2008 Fixed Description The ALTER and DROP TABLE statements can cause checkpoints to happen under certain circumstance. If these statements were executed on tables, where the table data had not changed since the last checkpoint, the server did a checkpoint anyway. These checkpoints caused the server to do unnecessary serialized work, and could have caused inefficiencies. The problem was most likely to be observed when large amounts of schema changes were being carried out, e.g., during a database schema reload. This has been changed so that the server will no longer cause an unnecessary checkpoint to occur.

CR:491111

CR Number:   491111 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) 10.0.1 3640 11 Feb 2008 Fixed 10.0.0 2900 19 Feb 2008 Fixed Description Scrolling the horizontal scrollbar to the right and then refreshing the list did not update the column headers. This has been fixed.

CR:491121

CR Number:   491121 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 1033 11 Feb 2008 Fixed 10.0.1 3640 11 Feb 2008 Fixed Description When run on Windows systems, the server's "about" box would not have opened when selecting "About SQL Anywhere..." after right clicking on the system tray icon. This has now been fixed.

CR:491180

CR Number:   491180 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1131 19 Feb 2008 Fixed 10.0.1 3644 19 Feb 2008 Fixed 9.0.2 3622 19 Feb 2008 Fixed Description On Windows CE devices, in rare cases it was possible for a database stored on a flash storage memory to not recover after the device shutdown abnormally. Flash storage memory includes flash memory cards and the standard storage memory on Windows Mobile 5 and 6 devices. This has been fixed.

CR:491267

CR Number:   491267 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 1037 12 Feb 2008 Fixed 10.0.1 3641 12 Feb 2008 Fixed Description The server could have crashed when there were many short transactions on a busy server. This was more likely to have occurred when running on Unix system and multiprocessor machines. It was not likely to have occurred when runnig on a single processor Windows machine. A race condition has been corrected.

CR:491315

CR Number:   491315 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 1130 14 Feb 2008 Fixed 10.0.1 3643 14 Feb 2008 Fixed Description Version 10.0.0 of SQL Anywhere added support for the OPTION clause in the SELECT statement. The OPTION clause has now been extended to the INSERT, UPDATE, DELETE, SELECT, UNION, EXCEPT, and INTERSECT statements. The clause allows users to override the settings for the following connection level options at the statement level: - isolation_level option [compatibility] - max_query_tasks option [database] - optimization_goal option [database] - optimization_level option [database] - optimization_workload option [database] The server will now raise an "invalid option setting" error in a predictable fashion if one of the unsupported options is used in the clause. There was a possibility of the server leaking a small amount of memory that has also been corrected.

CR:491380

CR Number:   491380 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 1045 15 Feb 2008 Fixed 10.0.1 3643 15 Feb 2008 Fixed Description If a statement, other than SELECT, INSERT, UPDATE, or DELETE, used a subselect expression that returned a NUMERIC or DECIMAL data type, then the subsequent operations using the subselect value could have inappropriately truncated the numeric result. This has been fixed. For example, the following sequence could have incorrectly return 104.0 instead of 104.6. create variable @vnum numeric(20,4) set @vnum = ( select max(103.5) ) + 1

CR:491388

CR Number:   491388 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 1039 15 Feb 2008 Fixed 10.0.1 3642 15 Feb 2008 Fixed Description Updating or deleting from a large table could have caused index corruption. For this problem to have occurred, a large number of rows (consecutive in index order) needed to be updated or deleted. This has been fixed.

CR:491399

CR Number:   491399 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 1039 14 Feb 2008 Fixed 10.0.1 3642 14 Feb 2008 Fixed Description When the 10.0 version of dbunload was used to unload a pre-10.0 database, the "unload support engine" (dbunlspt.exe) was spawned with a cache size equal to 40% of physical memory. For most databases, this is unnecessarily large. This has been changed so that dbunlspt.exe will now start with the same default cache size as the server, and grow no larger than 40% of physical memory.

CR:491400

CR Number:   491400 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 1039 14 Feb 2008 Fixed 10.0.1 3642 14 Feb 2008 Fixed Description The marquee in the overview panel would have flashed excessively when connected to a MobiLink server. This has been fixed. A workaround is to drag out the marquee to a new region, or to pause the auto scrolling.

CR:491414

CR Number:   491414 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1038 13 Feb 2008 Fixed 10.0.1 3638 14 Feb 2008 Fixed Description The Index Consultant wizard was not working correctly with the ENTER key. The Default button was not properly set, and focus was not properly set on some pages of the wizard. This has been fixed.

CR:491787

CR Number:   491787 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 1151 12 Mar 2008 Fixed 10.0.1 3657 12 Mar 2008 Fixed Description If a server was running in a high availability mirroring system and a client connection was cancelled or dropped, the server could have crashed. This has been fixed.

CR:491885

CR Number:   491885 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 1152 13 Mar 2008 Fixed 9.0.2 3634 13 Mar 2008 Fixed Description If a value-sensitive cursor was opened with the 'WITH HOLD' clause, and it referenced a table that was affected by a TRUNCATE statement, then the server could have reported assertion failures when the cursor was used after the truncate. This problem also occurred if the cursor referenced a temporary table declared with the 'ON COMMIT DELETE ROWS' clause and if the cursor was used after a commit. Assertions that could be reported in this situation include the following, although this list is not exhaustive: 201417 "Invalid count or free space offset detected on a table page" 101412 "Page number on page does not match page requested" Note that a value-sensitive cursor can be selected either explicitly, by cursor flags (ODBC keyset-driven, ESQL/SP scroll), or implicitly if the cursor type is changed by the query optimizer (for example, if a sort is used for an updatable cursor). This problem has been fixed. In engines with the fix for this problem, the affected cursor will return an error if it is used after the TRUNCATE or COMMIT. The error returned is: CURSOR_INVALID_STATE 24000 -853 "Cursor not in a valid state"

CR:491909

CR Number:   491909 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 1132 19 Feb 2008 Fixed Description The database option Scale was being used for the default scale for a specification such as NUMERIC(10). This has been corrected so that the scale used to supply the value is now 0. Additionally, supplying a numeric scale larger than the precision was not diagnosed. This has been corrected as well

CR:491910

CR Number:   491910 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1054 19 Feb 2008 Fixed 10.0.1 3645 19 Feb 2008 Fixed 9.0.2 3623 19 Feb 2008 Fixed Description In rare cases, concurrent execution of DML and DDL statements could have crashed the server. This has now been fixed.

CR:492018

CR Number:   492018 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1142 04 Mar 2008 Fixed 10.0.1 3652 04 Mar 2008 Fixed Description If a service that could not interact with the desktop failed to start, the error message describing the cause of the failure would not have been logged to the Event Log. This has been fixed.

CR:492031

CR Number:   492031 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3646 20 Feb 2008 Fixed Description In order to drop a table from the database, it must first be removed from all publications. Failing to remove the table from any publications prior to attempting to drop it would have resulted in an error. However, the UltaLite database would have been left in a corrupt state after the error was returned, as the operation was not fully rolled back. This has now been fixed.

CR:492148

CR Number:   492148 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1138 29 Feb 2008 Fixed 10.0.1 3651 29 Feb 2008 Fixed Description If the Connection.synchronize() function failed with an exception, the message in the exception did not contain any relevant details. For example, the text for a SQLE_PRIMARY_KEY_NOT_UNIQUE( -193) error did not include the table name ("Primary key for table '-n/a-' is not unique."). This has now been corrected.

CR:492188

CR Number:   492188 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 1134 26 Feb 2008 Fixed 10.0.1 3649 26 Feb 2008 Fixed Description In rare circumstances, the server could have crash when attempting the execute an external Java procedure. This has now been fixed.

CR:492197

CR Number:   492197 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1133 25 Feb 2008 Fixed 10.0.1 3647 25 Feb 2008 Fixed Description A client which sent malformed communications protocol to the MobiLink server, could have casused the server to crash. This has been fixed.

CR:492227

CR Number:   492227 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 1067 26 Feb 2008 Fixed 10.0.1 3649 26 Feb 2008 Fixed Description The server may have crashed if an ALTER TABLE statement attempted to rename a column, and there already existed a foreign key with referential action for this table. This has been fixed.

CR:492302

CR Number:   492302 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1134 22 Feb 2008 Fixed 10.0.1 3648 22 Feb 2008 Fixed 9.0.2 3626 22 Feb 2008 Fixed Description A query that involved more than one "Remote Procedure Call" in the FROM clause, could have caused the server to crash. An example of such a query is: SELECT col1 from remote_procedure_1() where col2 = (select c1 from remote_procedure 2()) This problem has now been fixed.

CR:492332

CR Number:   492332 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 1065 25 Feb 2008 Fixed 10.0.1 3649 25 Feb 2008 Fixed Description Materialized view maintenance could result in assertions and server crashes if there were other active connections (including internal connections). This has now been fixed.

CR:492344

CR Number:   492344 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3649 25 Feb 2008 Fixed Description An erroneous conversion error could have been detected when an IF expression involved an aggregate. For example: "IF count(n) > 50 THEN 'good' ELSE 'bad' ENDIF" This has been corrected.

CR:492346

CR Number:   492346 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 1061 22 Feb 2008 Fixed 10.0.1 3648 22 Feb 2008 Fixed Description When using Java in the database, a method that called System.out.println with a very long string would very likely have cause the client application to hang. This problem has now been fixed.

CR:492347

CR Number:   492347 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 1134 25 Feb 2008 Fixed 10.0.1 3649 25 Feb 2008 Fixed Description In certain conditions, executing statements with the ARGN() fuction could have caused the server to crash. This has been fixed.

CR:492348

CR Number:   492348 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 1068 25 Feb 2008 Fixed 10.0.1 3649 25 Feb 2008 Fixed Description If an application had more than one CallableStatement open on the same connection, then there was a chance that closing the CallableStatements would have caused a hang in the application. It should be noted that the problem does not exist with Statement and PreparedStatement objects. This problem has now been fixed.

CR:492353

CR Number:   492353 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1057 25 Feb 2008 Fixed 10.0.1 3648 25 Feb 2008 Fixed 9.0.2 3626 25 Feb 2008 Fixed Description In rare cases, the server could have crashed on shutdown if the cache priming page collection was enabled. Page collection is enabled by default, or if -cc or -cc+ were provided on the command line. This has now been fixed. The workaround is to use -cc- to disable cache priming page collection.

CR:492356

CR Number:   492356 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 1142 04 Mar 2008 Fixed Description If the procedure debugger was used to set a breakpoint in a stored procedure and then many connections called that procedure and hit the breakpoint, the server could have hung. This has been fixed. Workaround Description  Don't debug in production and if you must do not go for lunch while sitting on a breakpoint. Consider disabling debugging with the -sk switch.

CR:492387

CR Number:   492387 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1074 29 Feb 2008 Fixed 10.0.1 3654 11 Mar 2008 Fixed 9.0.2 3632 11 Mar 2008 Fixed Description The install would have failed on Unix systems which contained a version of coreutils 6.9 or newer (such as Ubuntu Linux 8.04). The failures would likely have occurred while checking that the target system meets the minimum requirements for SQL Anywhere, or while verifying the amount of free disk space available. The "setup" install script can be modified to work around this issue as follows: 1. Find all lines containing the "cut" command that uses the "-f" argument 2. For all such lines if a comma immediately follows the "-f", remove this comma For example, the line: OS_REL_1=`echo $OS_REL | cut -d. -f,1` should become: OS_REL_1=`echo $OS_REL | cut -d. -f1`

CR:492433

CR Number:   492433 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1134 25 Feb 2008 Fixed Description Errors logged to the Windows error log sometimes may have had "MobiLink Client" incorrectly spelled as "MobiLin Client". This has now been corrected.

CR:492533

CR Number:   492533 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3630 05 Mar 2008 Fixed Description In very rare, timing-related circumstances, calling a Java procedure, or making a request than references a remote JDBC clase server, may have failed with the error "No suitable driver", if a cancel had been received. When this happened, all JVM's, or the database, would have had to have been restarted to resolve the problem. This has been fixed.

CR:492540

CR Number:   492540 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 1065 25 Feb 2008 Fixed 10.0.1 3649 25 Feb 2008 Fixed Description If the last transaction log page received by a server acting as database mirror was completely filled, and the primary server was then shut down, the mirror could have failed to start. This has been fixed.

CR:492667

CR Number:   492667 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1067 26 Feb 2008 Fixed 10.0.1 3649 26 Feb 2008 Fixed Description If a Windows application called the function SQLColAttribute() with SQL_DESC_OCTET_LENGTH when using the iAS ODBC driver for Oracle, it could have been returned the transfer octet length in characters, rather than in bytes. Due to this problem, the application could have incorrectly truncated data. This problem has now been fixed. Note, this problem should not happen if the application is the MobiLink server. The MobiLink server does not call the ODBC function SQLColAttribute().

CR:492675

CR Number:   492675 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 1135 26 Feb 2008 Fixed 10.0.1 3650 26 Feb 2008 Fixed 10.0.0 2903 26 Feb 2008 Fixed Description Incorrect results could have been returned for for some DISTINCT ORDER BY combinations. This would have occurred when a DISTINCT clause was used and there were no unique indexes that could be used to guarantee distinctness, there was an ORDER BY clause and no indexes exist to effect that ordering and not all of the the ORDER BY constituents were found in the SELECT list. For example: SELECT DISTINCT last_name FROM people ORDER BY birth_date This has now been corrected.

CR:492780

CR Number:   492780 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3662 25 Mar 2008 Fixed 9.0.2 3643 28 Mar 2008 Fixed Description When an ODBC datasource was modified on Windows, the permission settings on the registry key were modified. This has been corrected.

CR:492783

CR Number:   492783 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1169 25 Mar 2008 Fixed 10.0.1 3663 25 Mar 2008 Fixed 9.0.2 3641 25 Mar 2008 Fixed Description If an application using the iAnywhere JDBC driver called ResultSet.getDouble() to fetch a numeric value, then there was a chance the JDBC driver would have thrown an "invalid numeric string" exception. This problem would only have happened if the application was using the Java print service and the default locale was a European one. Note that calling ResultSet.getBigDecimal() did not have the same problem, hence calling ResultSet.getBigDecimal().doubleValue() is a workaround for this problem. The original problem has now been fixed.

CR:492788

CR Number:   492788 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1137 27 Feb 2008 Fixed 10.0.1 3650 27 Feb 2008 Fixed Description Trying to use the named parameter ODBC_State with the report_odbc_error script would have resulted in an error, with ODBC_State being reported as an invalid system parameter. This has been fixed.

CR:492814

CR Number:   492814 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 1524 28 Oct 2008 Fixed 10.0.1 3789 28 Oct 2008 Fixed 9.0.2 3746 28 Oct 2008 Fixed 11.0.1 1998 14 Nov 2008 Fixed Description A user without administrator permission was unable to start, stop or delete SQL Anywhere services on a Windows 2003 machine, even if that user had been granted permission by an administrator to control those services. This has been fixed.

CR:492960

CR Number:   492960 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) 11.0.0 1070 29 Feb 2008 Fixed 10.0.1 3650 29 Feb 2008 Fixed Description Server-initiated synchronization requires the SendDownloadAck extended option to be enabled, but this would not be enabled for a SQL Anywhere remote database that had been setup for SIS through deployment from a synchronization model. This has been fixed. The workaround for this is to enable SendDownloadAck on the remote advanced options page when deploying.

CR:493049

CR Number:   493049 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 1138 29 Feb 2008 Fixed 10.0.1 3651 29 Feb 2008 Fixed 9.0.2 3629 29 Feb 2008 Fixed Description If the very first request to a remote server was executed by an user event at the time the server was shutting down, or during a server startup that fails, then the server may have crashed. This has been fixed.

CR:493071

CR Number:   493071 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 1138 29 Feb 2008 Fixed 10.0.1 3651 29 Feb 2008 Fixed Description The server could have crashed if a connection was attempted at the same time as a connection was in the process of disconnecting. The likelihood of this occurring would have been extremely rare due to the very small timing window. This has now been fixed.

CR:493096

CR Number:   493096 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 1138 03 Mar 2008 Fixed 10.0.1 3651 03 Mar 2008 Fixed Description When a server has more than 200 concurrent connections, the liveness timeout should be automatically increased by the server to avoid possible dropped connections. This was not being done until the server had at least 1000 concurrent connections. This has been corrected.

CR:493210

CR Number:   493210 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) 11.0.0 1141 04 Mar 2008 Fixed Description The Deployment wizard would have failed when deploying a synchronization model with a table with a LOB column on an Oracle consolidated database with timestamp download, or using shadow tables to record deletions. The Deployment wizard was attempting to create a trigger specifying LOB columns, however, Oracle does not support creating triggers with LOB columns specified. This has been fixed by creating the triggers on the table, rather than the columns.

CR:493217

CR Number:   493217 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 1142 04 Mar 2008 Fixed 10.0.1 3652 04 Mar 2008 Fixed Description In certain rare situations calls to the MOD() function with NUMERIC or DECIMAL arguments, could have caused the server to crash, or to report an unexpected error. This has been fixed.

CR:493219

CR Number:   493219 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1182 08 Apr 2008 Fixed 10.0.1 3671 08 Apr 2008 Fixed Description When using non-persistent HTTP, the length of the end_synchronization phase in the Monitor could have been shown as taking a long time (at least equal to the connection timeout interval), even though the sync successfully completed much earlier. The strange display made it hard to interpret what was going on. This has been fixed.

CR:493330

CR Number:   493330 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1148 11 Mar 2008 Fixed 10.0.1 3656 11 Mar 2008 Fixed Description When running Visual FoxPro the behaviour of the ODBC driver was different between version 9.0 and version 10.0. Version 10.0 reported different error messages when closing connections. This has been fixed so the behaviour is now consistant between versions.

CR:493337

CR Number:   493337 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1142 05 Mar 2008 Fixed 10.0.1 3652 05 Mar 2008 Fixed Description MobiLink clients could have failed to parse Set-Cookie HTTP headers sent by web servers and would have returned the error STREAM_ERROR_HTTP_HEADER_PARSE_ERROR. This has been fixed.

CR:493442

CR Number:   493442 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1145 11 Mar 2008 Fixed 10.0.1 3654 11 Mar 2008 Fixed Description Very large or very small numbers could have been displayed in exponential notation. This was different from previous versions of the software where numbers were displayed in plain decimal notation. Now, very large and very small numbers are displayed in decimal notation again. Also, the numbers that are written by the OUTPUT statement are now also similarly formatted using normal decimal notation.

CR:493478

CR Number:   493478 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 1143 06 Mar 2008 Fixed 10.0.1 3653 06 Mar 2008 Fixed Description Incorrect results could have been returned for for some queries with row limitation (using FIRST, TOP, and/or START AT clauses), when a query was not read-only and when a temporary table was required to execute the query. For example: SELECT TOP 14 * FROM table ORDER BY table.column when there was no index that could be used to order the data. This has now been fixed.

CR:493578

CR Number:   493578 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 1152 10 Mar 2008 Fixed 10.0.1 3657 10 Mar 2008 Fixed Description Attempting to add a row to a table which contained a UNIQUEIDENTIFIER column using the table in the "Results" panel could have caused Sybase Central to crash. This problem affected the Interactive SQL utility dbisql as well. It has now been fixed. Note that the problem was restricted to UNIQUEIDENTIFIER columns which could not be null and which did not have default values.

CR:493708

CR Number:   493708 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1145 10 Mar 2008 Fixed 10.0.1 3654 10 Mar 2008 Fixed Description Older MobiLink clients (version 8 and 9) may have failed to synchronize with an "Out of memory" error. This error should have been reported as "unknown character set". This has been corrected. The character translation mechanism can no longer translate characters from DECKanji or Turkish8 (possibly others). There is no workaround for this issue.

CR:493715

CR Number:   493715 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1145 11 Mar 2008 Fixed 10.0.1 3654 11 Mar 2008 Fixed Description If a database requires recovery, executing "START DATABASE {database name} FOR READ ONLY" would fail with the error "Unable to start specified database: unable to start database {database name}". This has been fixed; the error message will now read "Unable to start specified database: not expecting any operations in transaction log".

CR:493729

CR Number:   493729 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1145 10 Mar 2008 Fixed 10.0.1 3654 10 Mar 2008 Fixed 9.0.2 3632 10 Mar 2008 Fixed Description A problem introduced by changes for Engineering case 489871 made it possible for database recovery to fail with databases using the -m switch to truncate the transaction log at each checkpoint. This was not an issue if -m was not being used. This has been fixed.

CR:493730

CR Number:   493730 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 1145 10 Mar 2008 Fixed 10.0.1 3655 10 Mar 2008 Fixed 9.0.2 3632 10 Mar 2008 Fixed Description In rare, timing dependent cases, the server could have hung on multi-processor systems with one processor at 100% usage when iterating through connection handles (for example by using sa_conn_list or sa_conn_info). This was extremely unlikely on single processor systems, or on a server that had a low rate of connects and disconnects. This has been fixed.

CR:493738

CR Number:   493738 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1162 26 Mar 2008 Fixed 10.0.1 3662 26 Mar 2008 Fixed Description Performing an ALTER TABLE statement on a table with blob columns may have caused corruption in the database. The most likely symptom of this would have been a crash when selecting from a table that has been altered. This has now been fixed.

CR:493741

CR Number:   493741 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1147 11 Mar 2008 Fixed 10.0.1 3656 11 Mar 2008 Fixed Description An attempt to alter a column to DEFAULT NULL would have been ignored. This has now been corrected.

CR:493744

CR Number:   493744 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 1150 11 Mar 2008 Fixed 10.0.1 3656 11 Mar 2008 Fixed Description In the following situation: 1) A procedure call in the FROM clause consists of a single SELECT statement and nothing else 2) The FROM clause inside the procedure from 1) also consists of a single SELECT and nothing else then the procedure from 2) may be looked up in the context of the current connection rather than the owner of the procedure in 1). This is fixed. Note that this is not a security hole since the incorrect lookup is done in the context of the current connection.

CR:493757

CR Number:   493757 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 1145 11 Mar 2008 Fixed 10.0.1 3655 11 Mar 2008 Fixed Description The server could have crashed when inserting a row into a wide clustered index (one on many columns, or on long strings). This has now been fixed.

CR:493762

CR Number:   493762 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 1145 10 Mar 2008 Fixed 10.0.1 3655 10 Mar 2008 Fixed Description Incorrect results could be obtained for for some queries that used indexes in which there was more than one nullable column. This was corrected.

CR:493882

CR Number:   493882 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 1148 11 Mar 2008 Fixed Description SQL Anywhere allows the user to control how the affects of the LOAD TABLE statement are logged for recovery purposes. Some new forms of recovery logging, namely CONTENT LOGGING and ROW LOGGING, are supported in version 11 of the server. These forms of logging require that the database be upgraded or created with the new server. Further, CONTENT LOGGING is the default used by SQL Anywhere when the data source for the LOAD TABLE statement is an expression or a client file. The LOAD TABLE statement would have failed with an error if the database was being run without a transaction log and the logging type in effect is not FILENAME LOGGING, the old logging type. This has been corrected so that the server now accepts all logging types as valid when the database is running without a transaction log because there is nothing to be logged in this scenario, thereby allowing LOAD TABLE to execute without error.

CR:494020

CR Number:   494020 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 1152 13 Mar 2008 Fixed 10.0.1 3657 13 Mar 2008 Fixed Description In very rare cases, the server may have crashed on recovery, or failed to recover with other errors, most likely related to database page access. This problem was only possible if the server crashed in the midst of a checkpoint. This has now been fixed.

CR:494029

CR Number:   494029 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   MacOS Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1150 11 Mar 2008 Fixed 10.0.1 3656 11 Mar 2008 Fixed Description The -uc option (Start server in console mode) was not support by the server when run on MacOS systems. This has now been corrected.

CR:494052

CR Number:   494052 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) 11.0.0 1150 11 Mar 2008 Fixed Description When exiting an unchanged synchronization model, the MobiLink plug-in could have prompted to save it if a table mapping was selected and then the Events tab was switched to. This has been fixed.

CR:494151

CR Number:   494151 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1076 13 Mar 2008 Fixed Description Text index operations on a database created without the default "DBA" user would have failed with an error. This has been fixed. A work-around is to create the database with the default "DBA" user. Note that it is not enough to add the user after the database is created. The work-around will only be sufficient if the following query returns "1": select user_id from sysuser where user_name='DBA'

CR:494155

CR Number:   494155 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1170 26 Mar 2008 Fixed 10.0.1 3664 26 Mar 2008 Fixed Description UltraLite requires that each table have a primary index. Using SQL statements, it was possible to remove or rename this primary key, which would eventually have lead to a crash of the UltraLite application. Attempting to remove or rename a table's primary key will now result in an error.

CR:494182

CR Number:   494182 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 1076 13 Mar 2008 Fixed Description If a version 10.x database was updated using the version 11 beta, then the upgraded database would have been missing some system foreign key mappings. The problem was most evident when the customer tried to unload the upgraded database. This problem has now been fixed.

CR:494184

CR Number:   494184 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 1076 13 Mar 2008 Fixed 10.0.1 3657 13 Mar 2008 Fixed 9.0.2 36535 13 Mar 2008 Fixed Description The SACommandBuilder class did not implement the QuoteIdentifier method. The QuoteIdentifier method has now been added.

CR:494259

CR Number:   494259 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1156 17 Mar 2008 Fixed 10.0.1 3659 17 Mar 2008 Fixed Description A column could have been altered to have a different datatype, even when column was in a foreign key or constraint. This is now disallowed.

CR:494266

CR Number:   494266 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1078 18 Mar 2008 Fixed Description The Create Trigger wizard would have generated a trigger with an invalid REFERENCING clause. The clause was created as a comment, so while the statement would have compiled, attempting to uncomment the REFERENCING clause and saving the trigger would have failed. This has been fixed.

CR:494272

CR Number:   494272 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) 11.0.0 1152 13 Mar 2008 Fixed Description Running a generated SQL file for a new remote database, for a DB2 consolidated, with a table with Graphic columns could have given a syntax error. The DB2 consolidated Graphic types would have been mapped to long binary types in the SA remote database, however a length for the column would have been specified resulting in a syntax error. A workaround would be to manually edit the generated SQL file. This has been fixed.

CR:494280

CR Number:   494280 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3658 17 Mar 2008 Fixed Description After installing an application from a Microsoft Windows Installer package that was created using the Deployment Wizard, if the application was created with Visual Studio 2005 C# and used System.Data.OleDb, updating the database would have generated an error for which there was no text. This has been corrected.

CR:494283

CR Number:   494283 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 1233 14 May 2008 Fixed Description If an INSERT statement contained a VALUES clause (Syntax 1), it should not contain WITH AUTO NAME. For example, consider the following statement: insert into tauto with auto name values(1,2,'',4) WITH AUTO NAME was being accepted, but ignored, for these types of INSERT statements. This has been changed so that the statement will now give a syntax error.

CR:494295

CR Number:   494295 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1212 14 Mar 2008 Fixed Description Attempting to execute a query that used the CONTAINS clause on a table owned by another user would have failed with a "table not found" or "Permission denied" error. This has now been fixed.

CR:494297

CR Number:   494297 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1152 13 Mar 2008 Fixed 10.0.1 3657 13 Mar 2008 Fixed Description When the Unload utility dbunload is used with a 10.0 or later database, the version of dbunload used must match the version of the server used to access the database. If an older dbunload is used with a newer server, or vica versa, an error is now reported. This is most likely to occur if dbunload connects to an already-running server. The same restriction applies to the Extraction utility dbxtract.