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

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

CR:353712

CR Number:   353712 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) 9.0.2 2295 30 Apr 2004 Fixed 9.0.1 1856 30 Apr 2004 Fixed 9.0.0 1307 30 Apr 2004 Fixed Description If connections were being made concurrently which required a server to be autostarted, in rare timing dependent cases, the server could have hung or crashed, or the client could return one of a number of errors including SQLCODEs -832, -816, -308, -100, -85, -82. This has been fixed. Note it is still possible for the client to get errors when concurrent connects are done which require a server to autostart and different database files are involved, if the EngineName, ServerName or ENG parameter is not specified.

CR:353727

CR Number:   353727 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 06 May 2004 Fixed 9.0.1 1859 06 May 2004 Fixed Description An attempt to upload data via SyncProgressDialog, while the Mobilink server was not running, correctly reported that it encountered a communication error. However, SyncProgressDialog may sometimes report the following message: Synchronization Error. Data was uploaded and committed, but an error occurred during download (SQLCode=SQLE_COMMUNICATIONS_ERROR: Communication error). The SyncProgressDialog was relying on SyncProgressData.SyncResult.UploadOK to determine which message to display, but the SyncResult was only being updated at the end of synchronization. If a successfull synchronization occurred on the same connection, a subsequent synchronization would continue to see the results of the successful synchronization until the synchronization completed (in this case failing), at which time the SyncResult would have been correctly updated to reflect the result of the latter sync. The SyncResult field of SyncProgressData is now properly updated during SyncProgressed callbacks.

CR:353753

CR Number:   353753 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2299 04 May 2004 Fixed 9.0.1 1858 04 May 2004 Fixed 9.0.0 1308 04 May 2004 Fixed 8.0.3 5117 04 May 2004 Fixed 8.0.2 4416 04 May 2004 Fixed Description Running the Validation utility dbvalid to validate a read-only database would have caused the error: A write failed with error code: (5), Access is denied. Fatal error: Unknown device error This has been fixed. Workaround Description  Validate the database in Sybase Central 4.3. You can then use dbvalid at the command line without any error.

CR:353793

CR Number:   353793 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) 9.0.1 1856 30 Apr 2004 Fixed Description When parsing a statements of the type "select rewrite( 'some_string' )" the server may have crashed, if 'some_string' was not a valid SQL statement, for example 'XXXXXXX'. This has now been fixed.

CR:353803

CR Number:   353803 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2307 07 May 2004 Fixed 9.0.1 1862 12 May 2004 Fixed 9.0.0 1312 12 May 2004 Fixed Description SQL statements in the transaction log containing 128 byte identifiers would have prevented the database from recovering after a dirty shutdown. Identifiers shorter than this would not have caused a problem. This has been fixed. As a side effect of this fix, users can no longer create objects which have a length of zero bytes.

CR:353825

CR Number:   353825 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4993 30 Apr 2004 Fixed 9.0.2 2294 30 Apr 2004 Fixed Description The Database Unload utility dbunload could have failed with the message "SQL Error - Cannot access file ...", if the name of the directory provided contained multibyte characters with \x5c as following bytes. The file name in the error message would have contained extra backslash characters (or the Yen sign character in Japanese). The Unload Wizard in Sybase Central had the same problem. This problem has now been fixed.

CR:353828

CR Number:   353828 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4414 30 Apr 2004 Fixed Description When using the Windows Performance Monitor to display MobiLink statistics, the counters were always displayed in English on Japanese, Chinese, French or German Windows. This has now been fixed.

CR:353829

CR Number:   353829 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2295 05 May 2004 Fixed 9.0.1 1858 05 May 2004 Fixed 9.0.0 1308 05 May 2004 Fixed Description When the Listener utility was installed on Palm devices running Palm OS v5.2, and the MESSAGE or MESSAGE_START keyword was not specified in a message handler, the Listener could have crashed when processing such a message. This problem did not occur when using the older Palm OS v3.5.x. This has now been fixed.

CR:353893

CR Number:   353893 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) 9.0.2 2301 04 May 2004 Fixed 9.0.1 1859 04 May 2004 Fixed 9.0.0 1316 21 May 2004 Fixed 8.0.3 5003 21 May 2004 Fixed 8.0.2 4423 21 May 2004 Fixed Description If an event was scheduled to execute only once, and the event completed at the same time as the database was shut down, a server crash could have resulted. This has been fixed.

CR:353902

CR Number:   353902 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2298 04 May 2004 Fixed Description DBISQL could have reported an out-of-memory exception when executing an OUTPUT statement which attempted to export a large amount of data to an Excel, dBASE II, dBASE III, Foxpro, or Lotus 1-2-3 file. This has been fixed. In addition, the following performance-related changes were also made: - A warning message was added to the OUTPUT statement to warn about the inherent limitation of Excel 2.1 and Lotus files, that they cannot contain more than 65534 rows of data. Attempting to write more than this many rows, would have resulted in only the first 65534 rows being written to the file. - When writing Lotus 1-2-3 files, progress messages are now displayed. Previously, the Lotus exporter worked silently. - The algorithm which truncates long data when exporting to dBASE2 and Lotus files has been sped up. In one test case, the time taken to output 125 strings 2000 characters long went from about 8.5 seconds to 0.2 seconds

CR:353913

CR Number:   353913 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) 9.0.2 2298 05 May 2004 Fixed 9.0.1 1857 05 May 2004 Fixed 9.0.0 1308 05 May 2004 Fixed 8.0.2 4416 05 May 2004 Fixed Description The second and subsequent connections over SPX would not have used PORT connection parameters. PORT options were only read when the port was created, and ignored at all other times, which caused problems with subsequent connections that want to use different options. For example: connect using 'con=a;eng=g1;links=spx(dobroadcast=NO;host=host1)' connect using 'con=b;eng=g2;links=spx(dobroadcast=NO;host=host2)' If done from the same application, the second connect would not have worked, as the PORT options would have been ignored, so host2 would not have been looked at. This has now been fixed.

CR:353931

CR Number:   353931 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 04 May 2004 Fixed 9.0.1 1859 07 May 2004 Fixed Description The SMS listener for the Sierra Wireless AirCard 555 network card, (maac555.dll), may have delayed processing of a pre-existing message until a new message arrived. This has now been fixed.

CR:354031

CR Number:   354031 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2299 05 May 2004 Fixed 9.0.1 1858 05 May 2004 Fixed 9.0.0 1308 05 May 2004 Fixed Description The Schema Painter could have crashed when closed, or when closing an open schema file. This would likely have happened only when the open schema file is very large ( greater than 75K in size). This problem has been corrected.

CR:354096

CR Number:   354096 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2309 14 May 2004 Fixed 9.0.1 1863 14 May 2004 Fixed 9.0.0 1313 14 May 2004 Fixed 8.0.3 5117 14 May 2004 Fixed 8.0.2 4420 14 May 2004 Fixed Description The server would go into an infinite loop, with nearly 100 percent cpu usage, when executing a query like the following: select (select systable.first_page from systable where systable.table_id = 1) as id0, id0 as id1 from syscolumn group by id1 The problem occurred under the following conditions: - the query had a subselect in the select list or in the WHERE clause - the subquery had an alias name ("id0" in the above query) and the alias name was aliased by a second alias name ("id0 as id1" see above), so that both alias names were syntaxtically identical - the second alias name was part of a GROUP BY element This problem has been fixed

CR:354101

CR Number:   354101 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2300 05 May 2004 Fixed 9.0.1 1858 05 May 2004 Fixed 9.0.0 1309 05 May 2004 Fixed Description The documentation for the LDAP search_timeout parameter says that "A value of 0 disables this option so that all entries are assumed to be current". This was not the actual behaviour, specifying a timeout of 0 would have forced all LDAP entries to be ignored. This has been fixed, the behaviour now matches the documentation.

CR:354107

CR Number:   354107 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) 9.0.2 2298 05 May 2004 Fixed 9.0.1 1857 05 May 2004 Fixed Description A new collation 1255HEB has been added which provides support for the Windows Hebrew character set cp1255. Ordering is based on byte-by-byte ordering of the Hebrew characters. On Hebrew Windows systems, the database server will choose 1255HEB as the collation for a new database, if no collation is specified. 1255HEB will now appear in the output from "dbinit -l", and in the list of collations in Sybase Central.

CR:354116

CR Number:   354116 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) 9.0.2 2303 11 May 2004 Fixed 9.0.1 1862 11 May 2004 Fixed 9.0.0 1311 11 May 2004 Fixed 8.0.3 5002 11 May 2004 Fixed 8.0.2 4419 11 May 2004 Fixed Description If two transactions perform concurrent operations that involve scanning the table sequentially, and the table contains more than 100 pages of data, there was a chance of database corruption. One of the operations must have been an insert or update, while the other must have performed a sequential scan of the table. Indexed access in conjunction with inserts/updates would not have triggered the problem. This was more likely to occur on multiprocessor and Unix systems [while still possible, it was unlikely to occur on single processor Windows systems].

CR:354117

CR Number:   354117 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2300 05 May 2004 Fixed 9.0.1 1858 05 May 2004 Fixed 9.0.0 1309 05 May 2004 Fixed Description If the time on the machine running an LDAP server was ahead of the time on a machine running an ASA server or client application, LDAP entries would have been considered stale. Using search_timeout=0 is a workaround. This has been fixed, timestamps in the future are now considered current.

CR:354128

CR Number:   354128 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 11 May 2004 Fixed 9.0.1 1860 11 May 2004 Fixed 9.0.0 1311 11 May 2004 Fixed Description Incorrect results (ie extra rows) could have been produced with non-trivial aggregate expressions, such as "sum(x)-sum(y)". This has been corrected

CR:354138

CR Number:   354138 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2300 06 May 2004 Fixed 9.0.1 1858 06 May 2004 Fixed 9.0.0 1309 06 May 2004 Fixed Description If an server running on a multi-homed machine, (ie more than one IP address), registered itself through LDAP, ASA clients may not have been able to connect to it, depending on network topology. The clients would only have attempted to use the first IP address listed in LDAP. This has now been fixed, all IP addresses listed will be tried until a successful connection is made.

CR:354147

CR Number:   354147 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4481 01 Oct 2004 Fixed 8.0.3 5166 01 Oct 2004 Fixed 9.0.0 1370 01 Oct 2004 Fixed 9.0.1 1928 01 Oct 2004 Fixed 9.0.2 2529 01 Oct 2004 Fixed 2931 01 Oct 2004 Fixed Description When the log scanning tools were looking for the log file with the desired starting log offset, if that log file had a transaction in it which began in an earlier log file, but the log file that contained the start of the transaction could not be found, an error would have been reported similar to "Missing transaction log(s) in between file AC.log (ending at offset X) and file AD.log (starting at offset Y)". The offsets reported would have been incorrect, and upon inspection, the ending log offset of AC.log would have likely been the same as the starting log offset of AD.log. The correct error is now reported, "Missing transaction log(s) before file AA.log".

CR:354150

CR Number:   354150 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) 9.0.2 2300 06 May 2004 Fixed 9.0.1 1858 06 May 2004 Fixed Description The optimizer may have chosen a less than optimal plan for simple queries, if more than one index candidate existed, and at least one was an unique index. This has been fixed. For example, for the query: select * from T where T.A = c1 and T.B = c2 if there existed an unique index i1 on columns T.A, T.X1, T.X2 and T.X3 and an index i2 on columns T.A and T.B, the query would have used index i1 instead of i2.

CR:354151

CR Number:   354151 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) 9.0.1 1858 06 May 2004 Fixed 9.0.2 2300 05 May 2004 Fixed Description A new Arabic collation 1256ARA has been added, which supports the Arabic Windows character set cp1256. The collation will now appear in the list generated by the "dbinit -l" listing, and the Sybase Central Create Database wizard. On an Arabic machine, creating a database without specifying the collation, the default will now be 1256ARA instead of 1252LATIN1. The collation is a byte-by-byte ordering which should give reasonable ordering for Arabic. It does not produce an ordering that follows all of the standard rules for ordering Arabic, as this is outside the capabilities of existing ASA collation support.

CR:354153

CR Number:   354153 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 07 May 2004 Fixed 8.0.3 5000 07 May 2004 Fixed Description The column statistics in blank padded databases, for string columns with a declared length of up to 7 characters, could have been displayed with unnecessary blank characters. This problem has now been fixed. For existing databases, where incorrect statistics on some columns are suspected, the problem can be rectified by recreating the statistics on the suspect columns. If nothing is done however, the server will automatically correct the faulty statistics over time. To avoid potential problems with column statistics, they will be dropped by the server on a column whose declared length is modified via an ALTER TABLE.

CR:354155

CR Number:   354155 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   4.2.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2300 07 May 2004 Fixed Description The background color of disabled text components (excluding the syntax highlighting editor) was wrong on Windows. For example, the default Windows XP color scheme has a gray background, but Sybase Central had a white background. This has been fixed. Note, this problem affected all of the graphical administration tools shipped with ASA 9.0.1, including Sybase Central, DBConsole, DBISQL, and the MobiLink Monitor.

CR:354157

CR Number:   354157 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2300 06 May 2004 Fixed 9.0.1 1858 06 May 2004 Fixed 8.0.3 5138 03 Aug 2004 Fixed 8.0.2 4453 03 Aug 2004 Fixed Description When starting a database "read-only" using the "-r" command line option, the server could have failed with assertion 201851, if the database had been created by ASA 8.0.0 or newer. This has now been fixed.

CR:354194

CR Number:   354194 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 06 May 2004 Fixed 9.0.1 1858 06 May 2004 Fixed 9.0.0 1309 06 May 2004 Fixed Description When using the Create Function wizard to create a function in the Transact-SQL dialect, the comment describing the format of the parameter list would have been incorrect. The comment included the "OUTPUT" keyword which is not applicable for functions. This has now been fixed.

CR:354221

CR Number:   354221 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 06 May 2004 Fixed 9.0.1 1859 06 May 2004 Fixed 9.0.0 1309 06 May 2004 Fixed 8.0.3 5000 06 May 2004 Fixed 8.0.2 4417 06 May 2004 Fixed Description The following changes have been made to the OLEDB provider's Rowset property set DBPROPSET_ROWSET. The following Rowset properties were returning TRUE, indicating that the associated interface was supported. They now return FALSE, to indicate that the corresponding interfaces are not supported. DBPROP_IChapteredRowset DBPROP_IParentRowset DBPROP_IRowsetFind DBPROP_IRowsetIndex DBPROP_IRowsetRefresh DBPROP_IRowsetResynch The Rowset property DBPROP_IRowsetIdentity, was returning TRUE, although the IRowsetIdentity interface was not supported. The IRowsetIdentity interface is now implemented. The property continues to return TRUE. The following properties have been removed from the Rowset properties, as they are not Rowset properties, they are View properties. DBPROP_IViewChapter DBPROP_IViewFilter DBPROP_IViewRowset

CR:354282

CR Number:   354282 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2302 07 May 2004 Fixed 9.0.1 1859 07 May 2004 Fixed 9.0.0 1310 07 May 2004 Fixed 8.0.3 5001 07 May 2004 Fixed 8.0.2 4417 07 May 2004 Fixed Description When creating a column, or changing its type, the list of available system-defined default values for types of binary, varbinary or long binary, included the date, time and timestamp values. However, if one of these values was choosen as the default, attempting to save the changes to the column would have resulted in a "Cannot convert <type> to a binary". This has been fixed, the date, time and timestamp types are now excluded from the list of system-defined default values when choosing a binary data type.

CR:354297

CR Number:   354297 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2301 07 May 2004 Fixed 9.0.1 1859 07 May 2004 Fixed Description The QAnywhere Agent was not sending network status notification or push notification messages to the "system" queue. This problem was introduced after the 9.0.1 GA release, in build 1855, and is now fixed.

CR:354300

CR Number:   354300 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2302 11 May 2004 Fixed 9.0.1 1860 11 May 2004 Fixed 9.0.0 1310 11 May 2004 Fixed Description HTTP requests with Message Headers containing empty field-values were rejected with HTTP status code 400 "Bad Request". Since RFC 2616 section 4.2 states that a Message Header field-value is optional, such requests are now allowed.

CR:354317

CR Number:   354317 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2302 11 May 2004 Fixed 9.0.1 1859 11 May 2004 Fixed 9.0.0 1310 11 May 2004 Fixed 8.0.3 5001 11 May 2004 Fixed 8.0.2 4417 11 May 2004 Fixed Description The following changes have been made to correct problems in metadata reporting: The Schema Rowset returned for DBSCHEMA_TABLE_CONSTRAINTS has been corrected. The Schema rowset for DBSCHEMA_PROVIDER_TYPES now includes the types DBTYPE_R4 (FLOAT), DBTYPE_R8 (DOUBLE), and DBTYPE_GUID (UNIQUEIDENTIFIER). The type TINYINT is now described as signed, previously it was described as unsigned. The MAXIMUM_SCALE for DECIMAL and NUMERIC was NULL instead of 127. The MAXIMUM_SCALE for the SMALLINIT, TINYINT and INTEGER types is now NULL, not 0. Schema Rowsets that returned column type information did not include support for the DBTYPE_GUID (UNIQUEIDENTIFIER) type, now they do. In order to implement these changes, the stored procedures in scripts\oleschem.sql must replace the stored procedures in the database.

CR:354337

CR Number:   354337 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2302 11 May 2004 Fixed 9.0.1 1859 11 May 2004 Fixed 9.0.0 1310 11 May 2004 Fixed 8.0.3 5117 11 May 2004 Fixed 8.0.2 4417 11 May 2004 Fixed Description An internal error (IllegalArgumentException) could have been reported by dbisql, when an attempt was made to edit the result set of a stored procedure. The result set should not have been editable in the first place. This has now been corrected. This problem would only have occurred when connecting using the iAnywhere JDBC Driver.

CR:354381

CR Number:   354381 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2308 14 May 2004 Fixed 9.0.1 1863 14 May 2004 Fixed 9.0.0 1312 14 May 2004 Fixed 8.0.3 5117 14 May 2004 Fixed 8.0.2 4420 14 May 2004 Fixed Description When running on Windows 2003, the server could have crashed on startup, if the machine had no TCP/IP address, or was unplugged from the network. This has been fixed.

CR:354579

CR Number:   354579 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5002 11 May 2004 Fixed 8.0.2 4418 11 May 2004 Fixed Description The total connection count, listed on a database's property sheet, would not have been updated each time the property sheet was opened. This has now been fixed.

CR:354599

CR Number:   354599 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2306 11 May 2004 Fixed 9.0.1 1861 11 May 2004 Fixed 9.0.0 1311 11 May 2004 Fixed Description A transaction attempting to checkpoint could have deadlocked with other transactions. The most likely scenario was deadlocking with a transaction attempting a rollback. This was more likely to appear on multi-processor and Unix platforms. This problem has been fixed.

CR:354617

CR Number:   354617 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2313 19 May 2004 Fixed 9.0.1 1865 19 May 2004 Fixed 9.0.0 1314 19 May 2004 Fixed 8.0.3 5117 19 May 2004 Fixed 8.0.2 4422 19 May 2004 Fixed Description If dbisql reported an internal error, the password used in the current connection (if any) was shown in clear text in the error details. It has now been replaced by three asterisks. Note that passwords given as part of a "-c" command line option are still displayed in clear text in the error details.

CR:354689

CR Number:   354689 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2306 12 May 2004 Fixed 9.0.1 1862 12 May 2004 Fixed 9.0.0 1311 12 May 2004 Fixed Description The following changes have been made to correct problems in metadata reporting: The IDBSchemaRowset::GetSchemas method now correctly returns bit masks rather than argument counts to indicate which restriction parameters are supported. When using linked tables with Microsoft SQL Server 2000 Distributed Queries, this problem manifested itself with the message "OLE DB provider 'ASAProv.xxx' returned an invalid schema definition". The DBSCHEMA_TABLES_INFO Schema Rowset used by Microsoft SQL Server 2000 Distributed Queries is now supported. To install the revised schema support, the stored procedures in scripts\oleschem.sql must replace the stored procedures in the database.

CR:354766

CR Number:   354766 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) 9.0.2 2300 12 May 2004 Fixed 9.0.1 1858 12 May 2004 Fixed Description Normally the BACKUP and RESTORE statements append a line to the backup.syb file each time they are executed. This is done to record the backup or restore operation that was performed. To prevent the backup.syb file from being updated, the HISTORY OFF clause can now be added to the statement. For example: BACKUP DATABASE DIRECTORY 'd:\backup' HISTORY OFF

CR:354771

CR Number:   354771 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   6.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2306 12 May 2004 Fixed Description The UltraLite runtime would have ignored all invalid synchronization parameters. If a parameter was misspelt, it would have been ignored and the default value would have been used. Now, if the runtime encounters a parameter it doesn't recognize, synchronization fails and the SQL code SQLE_UNRECOGNIZED_OPTION is set. If an error callback has been provided, it will be called once for each invalid parameter. Duplicates continue to be ignored for now. This change does not affect Java UltraLite.

CR:354773

CR Number:   354773 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2307 13 May 2004 Fixed 9.0.1 1862 13 May 2004 Fixed 9.0.0 1312 13 May 2004 Fixed 8.0.3 5003 13 May 2004 Fixed 8.0.2 4419 13 May 2004 Fixed Description If an external procedure attempted to return a string longer than 65535 bytes, via a single call to the set_value callback function, the string would have been truncated. This has been fixed. A workaround is to call set_value multiple times to build up the result in pieces, each being shorter than 65535.

CR:354778

CR Number:   354778 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5002 12 May 2004 Fixed 8.0.2 4419 12 May 2004 Fixed Description The following changes have been made to correct problems in metadata reporting: The IDBSchemaRowset::GetSchemas method now correctly returns bit masks rather than argument counts to indicate which restriction parameters are supported. When using linked tables with Microsoft SQL Server 2000 Distributed Queries, this problem manifested itself with the message "OLE DB provider 'ASAProv.xxx' returned an invalid schema definition". The DBSCHEMA_TABLES_INFO Schema Rowset used by Microsoft SQL Server 2000 Distributed Queries is now supported. The stored procedures that implement the schema rowsets have been updated so that "uniqueidentifier" is used rather than "UNIQUEIDENTIFIER" . The phrase "not transactional" in the sa_oledb_tableconstraints stored procedure has been changed to "on commit preserve rows". To install the revised schema support, the stored procedures in scripts\oleschem.sql must replace the stored procedures in the database.

CR:354822

CR Number:   354822 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2307 13 May 2004 Fixed 8.0.3 5117 13 May 2004 Fixed Description If the Histogram utility dbhist was not provided with connection arguments (ie -c options), it would have assumed a default connection string of UID=DBA;PWD=SQL. Now, dbhist will no longer assume any default connection arguments, which is consistent with the behaviour of other ASA utilities.

CR:354838

CR Number:   354838 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2307 13 May 2004 Fixed 9.0.1 1862 13 May 2004 Fixed 9.0.0 1312 13 May 2004 Fixed 8.0.3 5117 13 May 2004 Fixed 8.0.2 4419 13 May 2004 Fixed Description If an error occurred on an embedded SQL EXECUTE statement, and there were bound columns with all NULL data pointers, a communication error could have occurred and the connection would have been dropped. An example of bound columns will all NULL data pointers from ESQL is: SQLDA *sqlda = alloc_sqlda( 1 ); sqlda->sqld = 1; sqlda->sqlvar[0].sqltype = DT_INT; sqlda->sqlvar[0].sqldata = NULL; EXEC SQL EXECUTE stmt into descriptor into_sqlda; This has been fixed so that an error is returned and the connection is not dropped.

CR:354843

CR Number:   354843 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Windows CE 2.11 Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2320 19 May 2004 Fixed 9.0.1 1868 25 May 2004 Fixed Description QAnywhere client applications are now supported on the Pocket PC 2002 and Pocket PC 2003 x86 emulators. Only the "scheduled" policy for the QAnywhere Agent is supported though.

CR:354948

CR Number:   354948 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1314 21 May 2004 Fixed 8.0.3 5003 21 May 2004 Fixed 8.0.2 4420 21 May 2004 Fixed Description When the database option Optimization_goal was set to 'First-row', the optimizer did not always respect it for queries with equijoins. This has been fixed.

CR:355012

CR Number:   355012 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2334 09 Jun 2004 Fixed 9.0.1 1874 09 Jun 2004 Fixed 9.0.0 1323 09 Jun 2004 Fixed 8.0.3 5117 09 Jun 2004 Fixed 8.0.2 4432 09 Jun 2004 Fixed Description Calling any of the external mail routines (such as xp_sendmail or xp_startmail) could have caused the server to crash. A problem with passing NULL parameters has been fixed.

CR:355020

CR Number:   355020 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   4.2.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2307 14 May 2004 Fixed 9.0.1 1862 14 May 2004 Fixed 9.0.0 1311 14 May 2004 Fixed Description On the Macintosh, some COMMAND key combinations did not work in the syntax highlighting editor, although the same CONTROL key combinations do work. On the Macintosh, COMMAND should be used instead of CONTROL. For example, on Windows, CONTROL+G to go to a line. On Macintosh, COMMAND+G to go to a line. This has been fixed.

CR:355098

CR Number:   355098 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2329 27 May 2004 Fixed 9.0.1 1873 27 May 2004 Fixed 9.0.0 1321 27 May 2004 Fixed 8.0.3 5117 27 May 2004 Fixed 8.0.2 4429 27 May 2004 Fixed Description An ALTER TABLE statement that added, modified or deleted a table's CHECK constraint, a column's CHECK constraint or renamed a column, had no effect on INSERT, UPDATE or DELETE statements inside stored procedures and triggers, if the procedure or trigger was executed at least once prior to the ALTER TABLE statement. This problem has been fixed.

CR:355123

CR Number:   355123 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2953 12 Nov 2004 Fixed 9.0.2 2531 12 Nov 2004 Fixed 9.0.1 1948 12 Nov 2004 Fixed 9.0.0 1388 12 Nov 2004 Fixed 8.0.3 5184 12 Nov 2004 Fixed 8.0.2 4499 12 Nov 2004 Fixed Description The server could have performed poorly relative to 7.x servers when doing a long sequence of database inserts, updates or deletes. The server was spending longer than necessary cleaning up the cache in preparation for a checkpoint. This time has now been reduced. Also, current servers now estimate the recovery time better. Thus the Recovery_time database option may need to be set to a larger value in order to have the server more closely match the value the 7.x server would have used.

CR:355126

CR Number:   355126 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2308 14 May 2004 Fixed 9.0.1 1863 14 May 2004 Fixed 9.0.0 1312 14 May 2004 Fixed Description When running on Unix platforms, the server could have stopped transferring data over a TCP/IP connection that was using ecc_tls encryption. This would most likely to have happened while transferring large amounts of data, such as blobs, to slow clients. The server would eventually have disconnected the client if the default idle time-out was used. This has been fixed.

CR:355145

CR Number:   355145 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2338 17 Jun 2004 Fixed 9.0.1 1876 17 Jun 2004 Fixed 9.0.0 1325 17 Jun 2004 Fixed 8.0.3 5119 17 Jun 2004 Fixed 8.0.2 4434 17 Jun 2004 Fixed Description A .NET application, using multiple database connections through separate threads, could have hung when updating the same table in different threads. When this situation occurred, one thread would have been blocked in the server (which is expected, as it is blocked against the other connection which is holding a lock on the table as a result of its update), and the other thread would appear to be hang as well, but it would not have been blocked in the server. What was happening was that the first thread had entered a critical section and was waiting for the server's response, while the second thread was waiting to enter the same critical section, thus caused the application hang. This has been fixed. Workaround Description  none obvious short of reverting back to 9.0 GA or 1216 or earlier product.

CR:355245

CR Number:   355245 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2308 18 May 2004 Fixed 9.0.1 1864 18 May 2004 Fixed 9.0.0 1314 18 May 2004 Fixed 8.0.3 5003 18 May 2004 Fixed 8.0.2 4421 18 May 2004 Fixed Description Attempting to unload a database created prior to SQL Anywhere version 5 would have resulted in an error that user "dbo" did not exist. If the dbo user was created, a different error would have been given, since the view dbo.sysusers would not have existed. This has been fixed. A workaround is to run the Upgrade utility dbupgrad before unloading the database.

CR:355262

CR Number:   355262 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2312 19 May 2004 Fixed 9.0.1 1864 19 May 2004 Fixed Description Clicking the "SQL/Start Logging" menu item, and selecting an existing file, would have caused a dialog to be opened which asked if it was OK to overwrite the file. The dialog was misleading as dbisql always appends to the log file, it never overwrites it. This prompt has now been removed.

CR:355292

CR Number:   355292 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2347 09 Jun 2004 Fixed 9.0.1 1874 09 Jun 2004 Fixed 9.0.0 1329 09 Jun 2004 Fixed 8.0.3 5123 09 Jun 2004 Fixed 8.0.2 4437 09 Jun 2004 Fixed Description Updating the version of jConnect to a newer version than the one shipped with ASA (ie newer than 5.5), would have likely have resulted in postioned updates failing with an exception. Versions of jConnect newer than 5.5 support the new status byte that was added to allow distinguishing between a NULL string and an empty string. When performing positioned updates, jConnect sends the KEY column values so that the row being updated can be uniquely identified. This status byte was not supported for KEY columns, but the server was still expecting it, resulting in a protocol error. This has been fixed.

CR:355299

CR Number:   355299 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) 9.0.2 2312 19 May 2004 Fixed 9.0.1 1864 19 May 2004 Fixed 9.0.0 1314 19 May 2004 Fixed 8.0.3 5117 19 May 2004 Fixed 8.0.2 4421 19 May 2004 Fixed Description When the server ran databases created with ASA versions 4.x and earlier (or databases upgraded from ASA versions 4.x and earlier), queries that made use of index scans over fully hashed indexes could have returned incorrect results. An optimization for index scans in older databases was incorrect. This optimization has now been removed, so a drop in performance when using older databases will likely be noticed. An unload/reload is recommended if the resulting performance is not acceptable.

CR:355459

CR Number:   355459 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) 9.0.2 2313 20 May 2004 Fixed 9.0.1 1865 20 May 2004 Fixed 9.0.0 1314 20 May 2004 Fixed 8.0.3 5117 20 May 2004 Fixed 8.0.2 4422 20 May 2004 Fixed Description When sending or receiving multi-piece strings on a heavily loaded system, the server could have deadlocked, causing a hang. This has been fixed. A work around would be to increase the number of tasks available to service requests (-gn). Alternatively, a dba user could use a pre-existing connection with the DEDICATED_TASK option set, to manually break the deadlock by cancelling one or more executing requests.

CR:355474

CR Number:   355474 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2313 20 May 2004 Fixed 9.0.1 1865 20 May 2004 Fixed 9.0.0 1314 20 May 2004 Fixed 8.0.3 5117 20 May 2004 Fixed Description When a query with multiple result sets was opened with ExecuteReader(CommandBehavior.SingleRow), calling NextResult would always have returned false. Only the a single row from the first result set could have been fetched. This problem has been fixed so that a single row is now fetched from each result set, which matches the .Net specifications.

CR:355516

CR Number:   355516 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) 9.0.2 2313 20 May 2004 Fixed 9.0.1 1865 20 May 2004 Deferred Description When being asked for the name of a new file in the utility wizards (for example, the Create Database wizard), clicking the "Browse..." button and choosing an existing file in the file dialog, would have caused a prompt asking to replace the file. This was erroneous, since once returning to the wizard and clicking Next, a "You must specify a new file" error message would have been displayed. This has been fixed. Now, the file dialog no longer asks to replace the file when a new file is required.

CR:355527

CR Number:   355527 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2320 02 Jun 2004 Fixed 9.0.1 1868 02 Jun 2004 Fixed 9.0.0 1317 02 Jun 2004 Fixed 8.0.3 5117 02 Jun 2004 Fixed 8.0.2 4425 02 Jun 2004 Fixed Description If a server goes down dirty (eg. due to a power failure), there can be a partial operation at the end of the log. If such a log was applied to a database by using the -a (apply named transaction log file) server command line option, restarting the server using that database and log file (without -a) could have caused the server to fail to start with the message "not expecting any operations in transaction log". The problem would only have occurred if the incomplete operation was the first operation of a new transaction and there were no other transactions active after all complete operations had been applied. The problem has been fixed by removing the partial operation from the log after the log is applied (or recovery is completed).

CR:355557

CR Number:   355557 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2313 20 May 2004 Fixed 9.0.1 1865 20 May 2004 Fixed 9.0.0 1314 20 May 2004 Fixed Description In some circumstances, idle HTTP client connections did not get disconnected from the server after the HTTP Time-out period had expired. This has been fixed.

CR:355574

CR Number:   355574 Product Name:   SQL Remote for SQL Anywhere Product Component:   File Messaging for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4427 31 May 2004 Fixed 8.0.3 5117 31 May 2004 Fixed 9.0.0 1320 31 May 2004 Fixed 9.0.1 1871 31 May 2004 Fixed 9.0.2 2326 31 May 2004 Fixed Description The SQL Remote Message Agents dbremote and ssremote, the SQL Remote Open Server ssqueue, the Log Transfer Manager dbltm, and MobiLink Client dbmlsync, could have hung when attempting to write a message to the output log that was greater than 64Kb in size. This has now been fixed.

CR:355587

CR Number:   355587 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2314 21 May 2004 Fixed 9.0.1 1865 21 May 2004 Fixed 9.0.0 1315 21 May 2004 Fixed 8.0.3 5003 21 May 2004 Fixed 8.0.2 4422 21 May 2004 Fixed Description On dual cpu machines, after creating an new prepared AsaCommand and inserting new rows in a loop, a communication error would have occurred after some iterations. For example, (VB.NET code): Imports iAnywhere.Data.AsaClient Module Module1 Sub Main() Dim conn As AsaConnection Dim cmd As AsaCommand Dim i As Int32 Try conn = New AsaConnection("uid=dba;pwd=sql;eng=asatest") conn.Open() for i = 1 to 2000 cmd = New AsaCommand("insert into ian values( 1 )", conn) cmd.Prepared() cmd.ExecuteNonQuery() Next Console.WriteLine("Inserted {0} rows", i) conn.Close() Catch e As Exception Console.WriteLine(e.ToString()) End Try End Sub End Module This problem has been fixed.

CR:355595

CR Number:   355595 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3010 13 Jan 2005 Fixed 9.0.2 2552 13 Jan 2005 Fixed 9.0.1 1972 13 Jan 2005 Fixed 8.0.3 5204 13 Jan 2005 Fixed 8.0.2 4511 13 Jan 2005 Fixed Description Calling the ODBC function SQLGetData() with a length of 0 would have failed for SQL_WCHAR. SQLRETURN SQLGetData( SQLHSTMT StatementHandle, SQLUSMALLINT ColumnNumber, SQLSMALLINT TargetType, SQLPOINTER TargetValuePtr, SQLINTEGER BufferLength, SQLINTEGER * IndPtr); SQLGetData can be used to obtain the amount of data available by passing 0 for the BufferLength argument. The amount of data available is returned in the location pointed to by IndPtr. If the amount available cannot be determined, SQL_NO_TOTAL is returned. When the TargetType was SQL_C_WCHAR, the amount of available data was incorrect (a character count rather than byte count was returned). This has been fixed. There were also some problems returning correct indicator values for databases using the UTF8 collation. This has also been fixed.

CR:355776

CR Number:   355776 Product Name:   SQL Anywhere Product Component:   Documentation Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 May 2004 Fixed Description ASA Programming Guide 9.x requires adjustment to remove java features which are no longer supported since version 9.0 (but supported in 8.x). Examples: 1) ASA Programming Guide Introduction to Java in the Database The runtime environment for Java in the database Scope and persistence ------------------------------------------------------------------ SELECT java.lang.Math.abs(-342) ------------------------------------------------------------------ 2) ASA Programming Guide Introduction to Java in the Database The runtime environment for Java in the database Java is case sensitive ------------------------------------------------------------------ SeLeCt java.lang.Math.random(); ------------------------------------------------------------------ 3) ASA Programming Guide Using Java in the Database Special features of Java classes in the database Returning result sets from Java methods ------------------------------------------------------------------ stmt.executeQuery ( "SELECT CAST( JName.lastName " + "AS CHAR( 50 ) )" + "FROM jdba.contact " );

CR:355787

CR Number:   355787 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2322 21 May 2004 Fixed 9.0.1 1870 21 May 2004 Fixed 9.0.0 1318 21 May 2004 Fixed 8.0.3 5117 21 May 2004 Fixed 8.0.2 4426 21 May 2004 Fixed Description An internal error could have been reported in response to pressing the DELETE key when an uneditable result set was displayed in the "Results" panel and the results table had the focus. This has been fixed.

CR:355830

CR Number:   355830 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5003 20 May 2004 Fixed 8.0.2 4423 20 May 2004 Fixed 8.0.1 3157 20 May 2004 Fixed Description A NullPointerException could have occurred in the following situation: - Open a second window, like when editing a stored procedure - Make a change to the procedure, close the window, when it prompts to save changes, respond NO - The window closes, but the Sybase Central window does not have focus - pressing TAB or CTRL-TAB will caused the exception This has now ben corrected

CR:355831

CR Number:   355831 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2315 21 May 2004 Fixed 9.0.1 1866 21 May 2004 Fixed 9.0.0 1315 21 May 2004 Fixed 8.0.3 5117 21 May 2004 Fixed 8.0.2 4423 21 May 2004 Fixed Description Executing an ALTER TABLE statement which attempted to modify a column and then drop the column in the same statement would have caused the server to crash. Attempting to modify and drop a column in the same ALTER TABLE statement will now generate the error "ALTER clause conflict". These changes must be made with separate ALTER TABLE statements.

CR:355929

CR Number:   355929 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2316 25 May 2004 Fixed 9.0.1 1866 25 May 2004 Fixed 9.0.0 1316 25 May 2004 Fixed 8.0.3 5117 25 May 2004 Fixed 8.0.2 4423 25 May 2004 Fixed Description The ASA provider could have loaded the wrong unmanaged dll, (dbdata8.dll or dbdata9.dll), if multiple version of ASA were installed. Now, the ASA provider will search for the unmanaged dll and will continue searching until it finds and loads the right one. If a matching version can not be found, the latest version will be loaded with a warning message.

CR:355965

CR Number:   355965 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) 9.0.2 2316 26 May 2004 Fixed 9.0.1 1866 26 May 2004 Fixed 9.0.0 1316 26 May 2004 Fixed 8.0.3 5117 26 May 2004 Fixed 8.0.2 4423 26 May 2004 Fixed Description When run on SMP systems using processors from Intel's P6 family, (as well as Pentium 4 and XEON), the server could have hung when receiving multi-piece strings via shared memory connections. This problem also affected ODBC, OLEDB and Embedded SQL clients as well. It has been fixed.

CR:355982

CR Number:   355982 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2316 26 May 2004 Fixed 9.0.1 1866 26 May 2004 Fixed 9.0.0 1316 26 May 2004 Fixed Description If an article's property sheet was opened to modify its set of columns, and the Apply button was then clicked, any further changes made to the set of columns in the article would have been ignored until the property sheet was closed and re-opened. This has now been fixed.

CR:356000

CR Number:   356000 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2317 26 May 2004 Fixed 9.0.1 1866 26 May 2004 Fixed 9.0.0 1316 26 May 2004 Fixed Description The schema painter could have crashed when editing a table's properties and renaming a column. The following demonstrates the problem: - Right click an existing table and choose Properties - Select a column (that isnt in an index) and click the Edit button - Rename the column - Click OK on the Column property sheet. - Click OK on the Table dialog and the crash may occur This has been fixed.

CR:356159

CR Number:   356159 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2320 27 May 2004 Fixed 9.0.1 1868 27 May 2004 Fixed 9.0.0 1317 27 May 2004 Fixed Description For queries that specified "SELECT *", metadata support for determining a name, given a column number was missing. Consequently, expresions such as: result_set_schema->GetColumnId( "c4" ) would have resulted in zero being returned. This has been corrected.

CR:356216

CR Number:   356216 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2329 27 May 2004 Fixed 9.0.1 1877 27 May 2004 Fixed 9.0.0 1325 27 May 2004 Fixed 8.0.3 5119 27 May 2004 Fixed 8.0.2 4435 27 May 2004 Fixed 7.0.4 3524 27 May 2004 Fixed Description The creation or execution of a stored procedure may have caused a server crash if the parameter list contained the special values SQLCODE or SQLSTATE, and in the procedure body a Transact-SQL variable was declared (ie variables that start with @). This has nowbeen fixed.

CR:356223

CR Number:   356223 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2320 25 May 2004 Fixed 9.0.1 1868 25 May 2004 Fixed Description If the same outer reference in a subquery appeared in both the GROUP BY list and the SELECT list then error -150 (Invalid use of an aggregate function) would have been reported. For example: select 1 from employee e1 where 1 = (select e1.emp_id from employee e2 group by e1.emp_id) This has been fixed.

CR:356262

CR Number:   356262 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2328 27 May 2004 Fixed 9.0.1 1872 02 Jun 2004 Fixed 9.0.0 1321 02 Jun 2004 Fixed Description The string representation of a double value may be generated with too many digits when the server was run on Linux x86 systems. For example: select cast( cast( 9.9 as double ) as char(30) ) would have returned '9.90000000000000036' instead of '9.9'. This has been corrected.

CR:356390

CR Number:   356390 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2321 27 May 2004 Fixed 9.0.1 1868 27 May 2004 Fixed 9.0.0 1318 27 May 2004 Fixed 8.0.3 5003 27 May 2004 Fixed Description The "do not ask again" checkbox, that is shown when deleting a table record, could have been selected and then the "No" button clicked. This would have resulted in the dialog never being shown again. In 8.x versions, "Yes" would always have been assumed, and in 9.x versions, "No" would always have been assumed. This has been changed so that the buttons now say "Ok" and "Cancel", and the checkbox is ignored when "Cancel" is pressed.

CR:356439

CR Number:   356439 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2320 27 May 2004 Fixed Description The output fields of the ul_synch_info object would not have been updated in the observer callback function when using the UltraLite engine. This has been fixed. The following are the fields of ul_synch_info that could change during synchronization: ul_stream_error stream_error; ul_bool upload_ok; ul_bool ignored_rows; ul_auth_status auth_status; ul_s_long auth_value; ul_bool partial_download_retained;

CR:356446

CR Number:   356446 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) 9.0.2 2321 26 May 2004 Fixed 9.0.1 1868 26 May 2004 Fixed Description The evaluation of the LIKE predicate could have returned incorrect results in some circumstances. For example, the following would have evaluated to FALSE, when it should be TRUE: " '5554' LIKE '%554%' ". This problem has been resolved.

CR:356484

CR Number:   356484 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2321 27 May 2004 Fixed Description Attempting to create a table in the UltraLite Schema Painter with a name greater than 128 characters would have failed with an error message stating that a table with that name already existed, (although it did display the correct SQLCode). The code was assuming that an error assigning a new table a name could only result from an existing table with the same name, which is not the case. The text of the error message has been improved.

CR:356521

CR Number:   356521 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2322 28 May 2004 Fixed 9.0.1 1870 28 May 2004 Fixed 9.0.0 1318 28 May 2004 Fixed Description An erroneous error was detected for INSERT-SELECT statements in which the associated SELECT expressions contained an alias name that matched the column name in the insertion list. For example: INSERT INTO Tab( col_a, col_b) SELECT x AS col_a, y FROM AnotherTab would have exhibited this behavior. This has been corrected.

CR:356595

CR Number:   356595 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2328 16 Jun 2004 Fixed 9.0.1 1872 16 Jun 2004 Fixed 9.0.0 1321 16 Jun 2004 Fixed 8.0.3 5117 16 Jun 2004 Fixed 8.0.2 4428 16 Jun 2004 Fixed Description If a RAISERROR or PRINT statement containted a subselect in the format string or in a PRINT expresstion, the server may have crashed or returned an error. This has been fixed.

CR:356604

CR Number:   356604 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2334 10 Jun 2004 Fixed 9.0.1 1874 10 Jun 2004 Fixed 9.0.0 1323 10 Jun 2004 Fixed Description Compound statements containing Transact-SQL 'SELECT INTO #temptable' syntax would have incorrectly reported error -141 "Table 'temptable' not found", if workload capturing was enabled in the Index Consultant. This has been fixed.

CR:356646

CR Number:   356646 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2314 03 Jun 2004 Fixed 9.0.1 1865 03 Jun 2004 Fixed 9.0.0 1315 03 Jun 2004 Fixed Description The OLE DB driver did not work well on 64-bit Windows systems. A number of memory alignment issues and problems with bookmarks (which were incorrectly assumed to be 32-bit values) were resolved.

CR:356648

CR Number:   356648 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2322 28 May 2004 Fixed Description When editing an existing table in the Table Editor, attempting to delete all columns that existed in the table, and adding one or more new columns to the table, would have resulted in the error "More columns are being dropped from table ... than defined" when saving the changes to the database. Now, the Table Editor prohibits deleting all existing columns from a table, as a table must contain at least one column.

CR:356739

CR Number:   356739 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2363 13 Jul 2004 Fixed 9.0.1 1889 13 Jul 2004 Fixed 9.0.0 1335 13 Jul 2004 Fixed 8.0.3 5130 13 Jul 2004 Fixed 8.0.2 4444 13 Jul 2004 Fixed Description If a trigger on table T referred to a column of T that had been dropped or renamed, then the server could have crashed when processing a query referring to T after the server was restarted. For the crash to have occurred, the referencing query must have been sufficiently complicated to allow predicates to be inferred. The cause of the crash has been fixed, and other changes have already made it impossible to rename or drop columns referenced by triggers.

CR:356753

CR Number:   356753 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2323 28 May 2004 Fixed Description When run on Windows platforms, the ASA Administration tools, (including dbisql and Sybase Central), ignored some keyboard mnemonics when the Windows StickyKeys feature was turned on. This has been fixed so that they mow it work correctly.

CR:356762

CR Number:   356762 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) 9.0.2 2330 07 Jun 2004 Fixed 9.0.1 1873 07 Jun 2004 Fixed 9.0.0 1322 07 Jun 2004 Fixed 8.0.3 5117 07 Jun 2004 Fixed 8.0.2 4431 07 Jun 2004 Fixed Description A non-fatal assertion failure: 105200 "Unexpected error locking row during fetch" could have been reported when executing an outer join with a temporary table on the null-supplying side of an outer join. This would have appeared to an application as error -300 "Run time SQL error" or -853 "Cursor not in a valid state". This has now been fixed.

CR:356790

CR Number:   356790 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5003 28 May 2004 Fixed Description An error would have been reported if an UNLOAD TABLE statement was executed that included an APPEND clause. This has been fixed.

CR:356795

CR Number:   356795 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2323 28 May 2004 Fixed 9.0.1 1870 28 May 2004 Fixed 9.0.0 1319 28 May 2004 Fixed 8.0.3 5117 28 May 2004 Fixed 8.0.2 4426 28 May 2004 Fixed Description On Windows 95, 98 or ME, if a network server had both TCP/IP and SPX connections, the server could have hung with 100% CPU usage. This has been fixed. Note if using a network server, Windows NT, 2000, XP or 2003 are recommended over Windows 95, 98 or ME, to ensure better performance and reliability.

CR:356798

CR Number:   356798 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) 8.0.3 5003 31 May 2004 Fixed Description Messages sent from the server to the client application would have been corrupted if the database character set was different from the client's connection character set. This problem would most likely have occurred on multi-byte character set systems with utf8 databases. This has been fixed.

CR:356853

CR Number:   356853 Product Name:   UltraLite Product Component:   Native UltraLite for Java Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2326 31 May 2004 Fixed 9.0.1 1871 31 May 2004 Fixed Description When creating tables with BIT columns, they had the attribute NULL by default. This has been corrected, by default BIT columns are now set to NOT NULL.

CR:356857

CR Number:   356857 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2326 31 May 2004 Fixed 9.0.1 1871 31 May 2004 Fixed 9.0.0 1320 31 May 2004 Fixed Description Calling Connection.GetNewUUID() would have generated an empty UUID of type Guid,(ie "00000000-0000-0000-0000-000000000000"). This has been fixed.

CR:356858

CR Number:   356858 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2330 31 May 2004 Fixed 9.0.1 1873 07 Jun 2004 Fixed Description Attempting to use the ntile() function would have caused the server to report the non-fatal assertion 106500, "Error building aggregate", rather than report the expected error, "olap extensions not supported". This problem has been fixed.

CR:357187

CR Number:   357187 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) 9.0.2 2329 04 Jun 2004 Fixed Description When using the Create Database wizard to create a database for Windows CE and then copying the database to a Windows CE device, there was no indication given that the log and mirror log file names should refer to directories on the Windows CE device. In fact, if the database was being created on the local computer, then the wizard would attempt to validate the log and mirror log file names for the local computer, asking whether any required directories should be created. This was clearly wrong, since the database was destined for the Windows CE device, not the desktop computer. This has been fixed. Now, when copying the database to the Windows CE device, the wizard indicates that the log and mirror log file names should be relative to the Windows CE machine. In addition, the wizard no longer attempts to validate these file names for the desktop machine. As a side-effect of this change, it is no longer possible to connect to the database on the desktop computer if it is being copied to the Windows CE device, since the log and mirror log file names may be invalid.

CR:357228

CR Number:   357228 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2329 04 Jun 2004 Fixed 9.0.1 1873 04 Jun 2004 Fixed 9.0.0 1321 04 Jun 2004 Fixed 8.0.3 5002 04 Jun 2004 Fixed 8.0.2 4429 04 Jun 2004 Fixed Description When using a database with the UTF8 collation, statements containing non-English characters could fail with the error "Syntax error or access violation", and Unicode bound data stored in the database could be corrupted. This problem would affect any application using ODBC or OLEDB, including Java-based applications using the JDBC-ODBC bridge (8.0) or iAnywhere JDBC Driver (9.0), including DBISQL and Sybase Central. dbmlsync was also affected. The bug was introduced in the following versions and builds: 8.0.2 build 4409 9.0.0 build 1302 9.0.1 build 1852 This problem has been fixed.

CR:357306

CR Number:   357306 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5117 10 Jun 2004 Fixed 8.0.2 4433 11 Jun 2004 Fixed Description The server could have chosen an inefficient execution plan for a query, even after freshly creating statistics for all tables involved in the query. The poor plan was usually caused by poor join selectivity estimation. Now, the server will have more information available after a CREATE STSTISTICS is executed, which should improve the quality of plans chosen.

CR:357339

CR Number:   357339 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2338 15 Jun 2004 Fixed Description In the MobiLink client dbmlsync, ActiveSync is only supported as a communications type on Windows CE and Pocket PC systems. If ActiveSync was specified as the communications type on a non-CE platform, an error message would have been generated indicating that the DLL dbmlas9.dll could not be loaded. Dbmlsync will now print an error stating that ActiveSync is only supported on Windows CE and Pocket PC.

CR:357494

CR Number:   357494 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2333 07 Jun 2004 Fixed 9.0.1 1874 07 Jun 2004 Fixed Description If a large message was sent, the directory containing the QAnywhere store-and-forward database may have temporarily contained many files with the suffix .log. After the messages were synchronized to the QAnywhere server, these temporary files would have been deleted. The amount of disk space consumed by these temporary files was equal to the size of the message. The problem has now been fixed, these temporary files will no longer be created.

CR:357497

CR Number:   357497 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2333 07 Jun 2004 Fixed 9.0.1 1878 07 Jun 2004 Fixed Description If the QAnywhere client agent was being run with an "automatic" synchronization policy, any errors that occurred during message synchronization (a communication break, for example) would have caused the messages to not be synchronized until a subsequent push notification was received from the server, or a new message was sent by a client application. The problem is now fixed.