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

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

CR:357506

CR Number:   357506 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2333 08 Jun 2004 Fixed 9.0.1 1874 08 Jun 2004 Fixed 8.0.3 5117 08 Jun 2004 Fixed Description Using statement-based scripting, uploaded updates can be ignored by not providing the upload_update script. When an actual update row was encountered on the upload, an error would have been generated indicating the missing script, and the synchronization would have been aborted. This has now been corrected. A workaround would be to provide any of the conflict resolution scripts (resolve_conflict, upload_insert_new_row, or upload_insert_old_row).

CR:357550

CR Number:   357550 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 2397 10 Aug 2004 Fixed 9.0.1 1903 10 Aug 2004 Fixed Description An UPDATE or DELETE statement attempting to modify a local table, when joined with a remote table, or a remote table joined with a local table, should fail with an error indicating that the query could not be executed. However, a recent change removed this error and the server would have either hang or crashed. The problem has been resolved and the original error is now given. Also, attempting to use the PUT statement on a remote table would have caused a server crash. An error is now given.

CR:357556

CR Number:   357556 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2333 08 Jun 2004 Fixed 9.0.1 1874 08 Jun 2004 Fixed Description Trying to save a MobiLink Monitor file on a Macintosh, without entering the extension, would have caused an invalid file format error. This has been fixed.

CR:357653

CR Number:   357653 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 2334 08 Jun 2004 Fixed 9.0.1 1874 08 Jun 2004 Fixed 9.0.0 1328 08 Jun 2004 Fixed Description The HTTP web services component of the server could have crashed if it received a SOAP request with an argument that had a length greater than the database's pagesize. This has been fixed.

CR:357683

CR Number:   357683 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 2342 16 Jun 2004 Fixed 9.0.1 1878 16 Jun 2004 Fixed 9.0.0 1327 16 Jun 2004 Fixed 8.0.3 5120 16 Jun 2004 Fixed 8.0.2 4435 16 Jun 2004 Fixed 7.0.4 3529 06 Aug 2004 Fixed Description When an application closed a cursor, the server was not freeing the cursor's resources before dropping the associated prepared statement or when the connection ended. This caused problems for applications that open many cursors on the same prepared statement. These applications would get errors when attempting to open a cursor, such as "Resource governor for 'cursors' exceeded", if the option MAX_CURSOR_COUNT was not set, or "Cursor not open". Now the cursor's resources are freed when a cursor is closed.

CR:357689

CR Number:   357689 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 2334 10 Jun 2004 Fixed 9.0.1 1874 10 Jun 2004 Fixed 9.0.0 1323 10 Jun 2004 Fixed 8.0.3 5117 10 Jun 2004 Fixed 8.0.2 4432 10 Jun 2004 Fixed Description A row limit (ie 'FIRST' or 'TOP nnn') could have been ignored on DELETE and UPDATE statements. This was most likely to occur on smaller tables and for very simple statements. Example: create table temp1 (nID int not null); insert into temp1 (nID, nid2) values (1); insert into temp1 (nID, nid2) values (1); commit; delete first from temp1; //deletes both rows This problem has been corrected. A workaround is to attach a redundant ORDER BY clause to the statement. delete first from temp1 order by 1+1; //deletes just one row

CR:357694

CR Number:   357694 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) 8.0.3 4936 09 Jun 2004 Fixed 8.0.2 4432 09 Jun 2004 Fixed Description When run on NetWare systems, the server could have caused a 'CPU Hog' abend executing a complex query. This has been fixed by adding additional yields in the optimizer.

CR:357700

CR Number:   357700 Product Name:   SQL Anywhere Product Component:   OLEDB 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 08 Jun 2004 Fixed 9.0.1 1873 08 Jun 2004 Fixed 9.0.0 1321 08 Jun 2004 Fixed 8.0.3 5003 08 Jun 2004 Fixed 8.0.2 4429 08 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:357701

CR Number:   357701 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2329 08 Jun 2004 Fixed 9.0.1 1873 08 Jun 2004 Fixed 9.0.0 1321 08 Jun 2004 Fixed 8.0.3 5003 08 Jun 2004 Fixed 8.0.2 4429 08 Jun 2004 Fixed Description Synchronizing to an ASA remote database using the UTF8 collation could fail with errors or put corrupted data into the database. The same 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. 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:357703

CR Number:   357703 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 2334 10 Jun 2004 Fixed 9.0.1 1874 10 Jun 2004 Fixed 9.0.0 1323 10 Jun 2004 Fixed Description When attempting to connect to a database by specifying an ODBC data source that used an 8.x or earlier driver (for example, "ASA 8.0 Sample" that is installed with 8.x), and choosing to use the iAnywhere JDBC driver, the connection would have failed with the error "The information required to display the database in Sybase Central could not be obtained". Using a pre-9.x data source with the iAnywhere JDBC driver to connect to a database in Sybase Central is now supported.

CR:357824

CR Number:   357824 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2342 11 Jun 2004 Fixed 9.0.1 1878 11 Jun 2004 Fixed 9.0.0 1327 11 Jun 2004 Fixed Description Some files required for MobiLink Java Authentication were not being installed on AIX and HP systems. In particular, mlsupport.jar, pop3.jar, and imap.jar were not being installed. This has been corrected.

CR:357842

CR Number:   357842 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 2335 10 Jun 2004 Fixed 9.0.1 1875 10 Jun 2004 Fixed 9.0.0 1324 10 Jun 2004 Fixed Description If the server received an HTTPS request where the URI (including parameters) or post data was longer than 1024 bytes, it may have responded with error code 408: "Request Time-out". This has been fixed

CR:357845

CR Number:   357845 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Solaris Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1405 19 Apr 2005 Fixed Description A problem using the iAnywhere Solutions ODBC driver for Oracle on Unix systems has been corrected. Downloading Unicode CLOB data could have caused the following error: "INTERNAL ERROR:occurred while storing a BLOB", "Data truncated, column 12. (ODBC State = 01004,Native error code = 0, Column or parameter #12)

CR:357853

CR Number:   357853 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 2335 10 Jun 2004 Fixed 9.0.1 1875 10 Jun 2004 Fixed 9.0.0 1324 10 Jun 2004 Fixed Description Calling the graphical_plan() function on query where a host variable appeared in the document argument to the openxml() function that was inside another graphical_plan() call, would have caused the server to crash. For example: select graphical_plan( 'select * from openxml( graphical_plan(?), ''/'') with (type xml ''.'' ) ') This is now fixed.

CR:357965

CR Number:   357965 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 2361 10 Jun 2004 Fixed 9.0.1 1888 12 Jul 2004 Fixed 9.0.0 1334 12 Jul 2004 Fixed 8.0.3 5128 12 Jul 2004 Fixed 8.0.2 4433 12 Jul 2004 Fixed Description Under certain conditions, SELECT DISTINCT queries with complex ORDER BY expressions may have received an erroneous syntax error. For example, the following query would have failed with SQLCODE -149: Select distinct e.emp_lname + space(50) + '/' + e.emp_fname from employee e, employee e2 where e.emp_id = e2.emp_id and e2.dept_id = 100 and (e.city = 'Needham' or e2.city = 'Burlington' ) order by e.emp_lname + space(50) + '/' + e.emp_fname This problem has been corrected.

CR:357967

CR Number:   357967 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 2338 14 Jun 2004 Fixed 9.0.1 1876 14 Jun 2004 Fixed 9.0.0 1325 14 Jun 2004 Fixed Description Optimizer statistics were also being flushed when procedures were unloaded. This has now been corrected.

CR:357981

CR Number:   357981 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 2361 11 Jun 2004 Fixed 9.0.1 1875 12 Jul 2004 Fixed Description The presence of duplicate indexes increased the optimizer's search space when looking for an appropriate index to use, thus possibly preventing it finding an optimal access plan for some statements. Duplicate indexes are no longer considered during optimization, unless named in an index hint. An index idx1 is considered a duplicate of the index idx2 if and only if the following conditions hold: - idx1 and idx2 are defined on the same columns, having the same order, and having the property ASC/DESC exactly the same for each column. - idx2 is a primary key index, but idx1 is not OR idx2 is declared unique index and idx1 is not OR idx2 is a foreign key index and idx1 is not OR idx2 is declared a clustered index and idx1 is not OR none of the above, in which case the engine randomly chooses idx1 to be the duplicate of idx2. For example, if idx1 is declared as: create index idx1 on T (T.A ASC, T.B DESC ) and idx2 is declared as : create unique index idx2 on T (T.A ASC, T.B DESC) then idx1 is considered a duplicate of idx2. For base tables, an analysis of the index list is performed to flag the duplicate indexes when indexes are loaded, or an index is added or dropped. Note 1: The property of being a duplicate is used only by the optimizer when a statement is optimized. Note 2: It is strongly recommended to drop useless duplicate indexes whenever possible. Note 3: The properties of uniqueness and clusterness are derived from one index to another. In the example above, the engine derives that the index idx1 is also unique because idx2 is unique.

CR:357982

CR Number:   357982 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2335 11 Jun 2004 Fixed 9.0.1 1874 11 Jun 2004 Fixed 9.0.0 1324 11 Jun 2004 Fixed Description A problem affecting any of the ASA executables running on CE devices only, that could have caused memory to be corrupted, has been fixed. The only behavior actually seen as a result of this problem was the inability of CE based executables to create UI elements, such as windows or messageboxes, however it may have caused other problems as well.

CR:357983

CR Number:   357983 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1329 21 Jun 2004 Fixed 9.0.1 1881 15 Jul 2004 Fixed Description A correlated subquery used in a predicate of the form "expr = (correlated subquery)" which, in addition, satisfied the conditions to be executed as a decorrelated subquery, may have caused a crash of the server during optimization. This has been fixed. For example: select * from R where R.X = (select max(T.X) from T where T.Y = R.Y) The above query may be executed by computing the decorrelated subquery, equivalent to the following: select R.* from R, (select max(T.X), T.Y from T group by T.Y) as DT( max, Y) where R.X = DT.max and R.Y = DT.Y Note 1: The decision to decorrelated subquery is done cost-based during optimization. Note 2: The crash would have occurred, if and only if a Sort Merge Join method was considered for joining the decorrelated subquery with the rest of the query block's tables. The Sort Merge Join strategy must have been chosen in the best plan for the crash to happen.

CR:358006

CR Number:   358006 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 2397 19 Jul 2004 Fixed 9.0.1 1892 13 Aug 2004 Fixed Description An estimated cost for using a work table is now added to the total estimated cost of the plan that needs a work table at the root. When both materializing plans and non-materializing plans are costed for a query, the extra cost added when a work table is needed gives a more accurate cost estimate for the whole query. This will improve the optimizer's choice of the most appropriate plan for a query.

CR:358040

CR Number:   358040 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 2336 24 Jun 2004 Fixed 9.0.1 1875 24 Jun 2004 Fixed 9.0.0 1324 24 Jun 2004 Fixed 8.0.3 5117 24 Jun 2004 Fixed 8.0.2 4433 24 Jun 2004 Fixed Description In rare low-memory situations, the server could have crashed or quietly ended. This has been fixed.

CR:358138

CR Number:   358138 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2336 11 Jun 2004 Fixed 9.0.1 1875 11 Jun 2004 Fixed 9.0.0 1324 11 Jun 2004 Fixed 8.0.3 5117 11 Jun 2004 Fixed 8.0.2 4433 11 Jun 2004 Fixed Description Connecting to a database in the MobiLink plug-in by opening the Connect dialog and specifying the connection information, would have caused the information specified (excluding the password) to be saved in the user's .scUserPreferences file under the default connection key "DefConn". The information was saved so that the next time the Connect dialog was opened, it would contain the previous connection information. For security reasons, this feature has been removed. Now, this information is no longer implicitly saved in the user's .scUserPreferences file. Instead, it is persisted in memory for the current Sybase Central session only. Note that the user can still use connection profiles to explicitly persist connection information in the .scUserPreferences file. This change also fixes a problem which could have caused the password to be incorrectly persisted as "***".

CR:358149

CR Number:   358149 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2337 14 Jun 2004 Fixed 9.0.1 1875 14 Jun 2004 Fixed 9.0.0 1325 14 Jun 2004 Fixed Description Operations in a stored procedure or batch, on string variables that were exactly 255 bytes in length, could have caused the resultant string to have become corrupted. This has been fixed.

CR:358151

CR Number:   358151 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2342 16 Jun 2004 Fixed 9.0.1 1878 16 Jun 2004 Fixed 9.0.0 1327 16 Jun 2004 Fixed 8.0.3 5120 16 Jun 2004 Fixed 8.0.2 4435 16 Jun 2004 Fixed Description The Interactive SQL utility dbisqlc, did not display help when the "Help Topics" menu was selected. This has been fixed.

CR:358197

CR Number:   358197 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 2337 11 Jun 2004 Fixed 9.0.1 1875 11 Jun 2004 Fixed 9.0.1 1875 11 Jun 2004 Fixed Description Executing a statement with a view that referenced remote tables and used Common Table Expressions, would likely have caused a server crash. The fix for Engineering Case 352938 was incomplete, as it did not handle views. This has now been corrected.

CR:358200

CR Number:   358200 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 2336 11 Jun 2004 Fixed 9.0.1 1875 11 Jun 2004 Fixed 9.0.0 1324 11 Jun 2004 Fixed Description When connecting to a database with the ASA plug-in, the connection information used is now remembered for the current Sybase Central session, so that the next time the Connect dialog is opened, it contains the previous connection information. For security reasons, the password is remembered only if the SQLCONNECT environment variable is defined and contains the same password. Note that this information is remembered for the current Sybase Central session only, it is not persisted in the users .scUserPreferences file because of security concerns.

CR:358207

CR Number:   358207 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2337 14 Jun 2004 Fixed 9.0.1 1875 14 Jun 2004 Fixed 9.0.0 1325 14 Jun 2004 Fixed Description As of ASA 9.0.0, the ODBC driver allows for the establishment of a message callback function, so that 'message' statements can be send back to the connection. These callback functions are established by calling SQLSetConnectAttr(), but it was not possible to uninstall the message callback function. Now, calling SQLSetConnectAttr() and passing a NULL pointer will disable the message callback function.

CR:358245

CR Number:   358245 Product Name:   UltraLite Product Component:   UltraLite for M-Business Anywhere Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2338 14 Jun 2004 Fixed 9.0.1 1876 14 Jun 2004 Fixed Description On Palm OS devices, a call to UUID.toString() would have returned an empty string. This has been corrected

CR:358246

CR Number:   358246 Product Name:   UltraLite Product Component:   UltraLite for M-Business Anywhere Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2338 14 Jun 2004 Fixed 9.0.1 1876 14 Jun 2004 Fixed Description On Palm devices, when creating a database with the createDatabaseWithParms() function, or opening a connection with the openConnectionWithParms() function, the numerical value in the converted connection string would have become "?". Such fields included reserve_size and page_size. This has been fixed.

CR:358312

CR Number:   358312 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 2338 14 Jun 2004 Fixed 9.0.1 1876 14 Jun 2004 Fixed 9.0.0 1325 14 Jun 2004 Fixed Description The server's HTTPS web services could eventually have exhausted the memory available to the server, which could have resulted in a fatal error. This has been fixed.

CR:358333

CR Number:   358333 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 2342 17 Jun 2004 Fixed 9.0.1 1878 17 Jun 2004 Fixed 9.0.0 1326 17 Jun 2004 Fixed 8.0.3 5120 17 Jun 2004 Fixed 8.0.2 4435 17 Jun 2004 Fixed Description A NullReferenceException could have occurred when fetching long varchar or long binary date using the DataReader object. This problem has been fixed.

CR:358350

CR Number:   358350 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2425 08 Sep 2004 Fixed 9.0.1 1918 08 Sep 2004 Fixed 9.0.0 1359 08 Sep 2004 Fixed 8.0.3 5156 08 Sep 2004 Fixed Description If a table was part of a publication, altering a trigger on that table could have caused the server to fail with assertion 100905 on a subsequent INSERT, UPDATE or DELETE. For this to have occurred, the table must have been referenced in a stored procedure and the procedure must have been called at least once before the ALTER and once after. This has been fixed.

CR:358354

CR Number:   358354 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 2342 17 Jun 2004 Fixed 9.0.1 1878 17 Jun 2004 Fixed Description Insert statements with queries containing non-deterministic functions and EXISTS, ANY, ALL or IN predicates, that were rewritten as a join with a DISTINCT, could have produced incorrect results. In these cases, the distinct operation was applied to the non-deterministic function in addition to the other columns where distinct elimination was required for correctness. Hence, rows which would otherwise have been considered identical were made different by the non-deterministic function, causing the number of rows performed by the insert to be greater than expected. This has been fixed. A workaround is to embed the insert in a compound statement, where the query is run and the inserts are done using a cursor ranging over the query. This is a followup issue to Engineering Case 346886, which missed this special case.

CR:358369

CR Number:   358369 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 2341 16 Jun 2004 Fixed 9.0.1 1877 16 Jun 2004 Fixed Description When connected to a remote server via ODBC and using callable or prepared statements, getting the update count could have returned a function sequence error, instead of giving the proper count. This has now been fixed.

CR:358388

CR Number:   358388 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2338 16 Jun 2004 Fixed 9.0.1 1876 16 Jun 2004 Fixed 9.0.0 1325 16 Jun 2004 Fixed 8.0.3 5119 16 Jun 2004 Fixed Description When the ADDRESS specified for the ASA client dbmlsync, to connect to a Mobilink server, contained the 'security' parameter and the cipher specified was not recognized, dbmlsync would have reported an error indicating that it could not load a DLL (usually dbsock?.dll or dbhttp?.dll). A more meaningful error message is now displayed.

CR:358479

CR Number:   358479 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 2339 16 Jun 2004 Fixed 9.0.1 1877 16 Jun 2004 Fixed 9.0.0 1326 16 Jun 2004 Fixed Description When editing a view, trigger, procedure, function, or event in the right pane of the main Sybase Central window, the Paste menu item and toolbar button were enabled if the clipboard contained something other than text, such as an image. In this case, selecting the menu item or clicking the toolbar button would have done nothing. Now, the Paste menu item and toolbar button are enabled only when the clipboard contains text.

CR:358497

CR Number:   358497 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 2341 16 Jun 2004 Fixed 9.0.1 1877 16 Jun 2004 Fixed 9.0.0 1326 16 Jun 2004 Fixed 8.0.3 5119 16 Jun 2004 Fixed 8.0.2 4435 16 Jun 2004 Fixed Description If a database with auditing enabled required recovery, the server may have indicated during recovery that the log file was invalid. If an audit record in the transaction log was only partially written, the audit record would have appeared corrupt. This is now ignored if the partial audit record is at the end of the log.

CR:358511

CR Number:   358511 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.1 1877 16 Jun 2004 Fixed Description The QAnywhere Client qaagent.exe, version 9.0.1.1830 or later, could have failed to start when run against a message store created with an earlier version of qaagent. The error reported in the log would have been: E.... InternalError: Procedure 'ml_qa_set_global_property' not found E.... Source statement: E.... QAnywhere Agent failed to initialize parameters I.... QAnywhere Agent stopped This problem has been fixed.

CR:358564

CR Number:   358564 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2334 16 Jun 2004 Fixed 9.0.1 1875 16 Jun 2004 Fixed 9.0.0 1325 16 Jun 2004 Fixed Description Two new Traditional Chinese collations have been added, 950ZHO_HK and 950zho_tw. The collation 950ZHO_HK provides support for the Windows Traditional Chinese character set CP950, plus Hong Kong Supplementary Character Set (HKSCS). The collation 950ZHO_TW provides support for the Windows Traditional Chinese character set cp950, but doesn't support HKSCS. Ordering is based on byte-by-byte ordering of the Traditional Chinese characters. The collation 950TWN is now obsolete. Please note that in version 9.0.0 and lower, 950TWN has no support for HKSCS, the new collation that is equivalent to it is 950ZHO_TW. In 9.0.1 and higher, 950TWN does support CP950 plus HKSCS and the new collation that is equivalent to it is 950ZHO_HK. The reason for splitting 950TWN into two collations is that Microsoft Windows allows users to create their own characters in the End User Defined Character (EUDC) area in Windows code pages. HKSCS, is an extension to CP950, which defines its characters also in the EUDC area for CP950 and thus may conflict with existing private characters defined by users who don't use HKSCS and don't have HKSCS installed.

CR:358667

CR Number:   358667 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 2347 18 Jun 2004 Fixed 9.0.1 1881 18 Jun 2004 Fixed 9.0.0 1329 18 Jun 2004 Fixed Description On busy servers, TLS connections may have timed out with the error -829 "TLS handshake failure", after 10 seconds. The TLS timeout time has now been changed to be the same as the connection's liveness timeout time. Note, this problem also affected HTTPS connections as well. The timeout in that case is now set to the same as the idle timeout (the TIMEOUT parameter to HTTPS). This also fixed a server crash that may have occurred if an older dbtls DLL was used.

CR:358679

CR Number:   358679 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 2342 17 Jun 2004 Fixed 9.0.1 1878 17 Jun 2004 Fixed Description The drop down boxes on the Joins page of the QueryEditor did not allow scrolling from the keyboard, only the mouse. This is now fixed.

CR:358783

CR Number:   358783 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1879 17 Jun 2004 Fixed 9.0.2 2343 17 Jun 2004 Fixed Description The Unload utility dbunload, would have reported character set conversion errors when UNILIB character set conversion tables ( the uct files under the charsets\unicode folder ) were not deployed with the database server. The server will nolonger report an error, but if UNILIB character set conversion tables are not present for the server, object names which contain non-English characters can be mangled in messages, when the database character set is different from the client character set.

CR:358785

CR Number:   358785 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 2343 17 Jun 2004 Fixed 9.0.1 1879 18 Jun 2004 Fixed Description Valid nested queries that utilized aliased outer reference expressions could have failed with a syntax error (SQLCODE -149). As an example, the following query (over the asademo database schema) would have failed due to the use of "Q" in the GROUP BY clause of the subquery: select line_id as Q, count(*) from sales_order_items where quantity != 89999 group by line_id having count(*) not in (select max(quantity) from product group by Q, description ) order by 1, 2 It was necessary that both the outer block and the nested subquery both contain aggregation and/or GROUP BY clauses for this problem to have occurred. It has now been fixed.

CR:358843

CR Number:   358843 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2347 22 Jun 2004 Fixed 9.0.1 1881 22 Jun 2004 Fixed 9.0.0 1329 22 Jun 2004 Fixed 8.0.3 5123 22 Jun 2004 Fixed 8.0.2 4437 22 Jun 2004 Fixed Description A memory leak occurred in the OLEDB provider, ASAProv, when a repeated sequence of calls to SetCommandText(), Prepare(), and GetColumnInfo() was executed. These calls could be generated by an ADO Open() call with a SELECT statement containing a number of table JOINs. This problem has now been fixed.

CR:358918

CR Number:   358918 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2393 09 Aug 2004 Fixed 9.0.1 1903 09 Aug 2004 Fixed 9.0.0 1347 09 Aug 2004 Fixed Description Sybase Central would not have started if the "Fast launcher" option was turned on and the TCP/IP port it was configured to use was already in use by some other program. No errors would have been reported; the application would simply have failed to run. This problem also affect the Interactive SQL utility dbisql as well. This has been fixed. You can disable the fast launcher by running: dbisql -uninstall -terminate scjview -uninstall -terminate

CR:358926

CR Number:   358926 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 2344 18 Jun 2004 Fixed 9.0.1 1879 18 Jun 2004 Fixed 9.0.0 1327 18 Jun 2004 Fixed Description Connecting to a database by using the Connect dialog (as opposed to using a connection profile) and then attempting to open Interactive SQL by right-clicking the database and selecting the "Open Interactive SQL" menu item, would have required typing the password before the connection was established in Interactive SQL. This has been fixed. Now, the connection is established automatically using the same password that was specified when connecting to the database in Sybase Central.

CR:358939

CR Number:   358939 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2344 18 Jun 2004 Fixed 9.0.1 1879 18 Jun 2004 Fixed Description When the graphical version of the Dbmlsync Integration Component was used on Windows CE, calls to the function IOleObject::GetMiscStatus would have returned that it was not implemented, (E_NOTIMPL). Thisfunction has now been implemented for Windows CE.

CR:358956

CR Number:   358956 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 1879 18 Jun 2004 Fixed 9.0.2 2344 18 Jun 2004 Fixed Description Executing a CREATE DOMAIN statement in a database with a multibyte collation, such as Japanese, that defined a default value that contained multibyte characters with \x5c as the second byte, would have been displayed as a hexadecimal string in Sybase Central. This problem did not exist if the collation was UTF8. The problem is now fixed.

CR:358965

CR Number:   358965 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2344 21 Jun 2004 Fixed 9.0.1 1879 21 Jun 2004 Fixed Description On the Table Data page of the Plug-in Preferences property sheet (accessible by right-clicking "Adaptive Server Anywhere 9" in the tree and selecting the Preferences... menu item), changing the font selection to another custom font when a custom font was already selected, would not have enabled the Apply button. This has been fixed.

CR:358974

CR Number:   358974 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 2344 21 Jun 2004 Fixed 9.0.1 1879 21 Jun 2004 Fixed Description The QAnywhere client would have automatically set the properties "ias_MimeType" and "ias_MessageType" for each message that i\was sent. This has been changed. Now the property "ias_MimeType" is no longer set for any message, since it did not convey any more information than whether the message content was text or binary, and this information is obtainable by other means. The property "ias_MessageType" is also no longer set for regular messages. It is still set for network status and other system messages that are sent to the "system" queue. The purpose of this change was to reduce the amount of data sent over the network by up to 59 bytes per message.

CR:359136

CR Number:   359136 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 2347 21 Jun 2004 Fixed 9.0.1 1881 21 Jun 2004 Fixed 9.0.0 1329 21 Jun 2004 Fixed 8.0.3 5123 21 Jun 2004 Fixed 8.0.2 4437 21 Jun 2004 Fixed Description UltraLite.NET has a simpler error system and thus does not have the ADO Errors collection. In order to make it easier to move from UltraLite to ASA, two new properties have been added, AsaException.NativeError and AsaInfoMessageEventArgs.

CR:359142

CR Number:   359142 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 1881 21 Jun 2004 Fixed 9.0.2 2347 21 Jun 2004 Fixed Description Two new collations have been added, 1252SPA Spanish, and 874THAIBIN Thai. Collation 1252SPA is similar to 1252LATIN1, but causes N and (N-tilde) to be sorted as separate characters. On a Windows system configured for Spanish, dbinit and the CREATE DATABASE statement will now default to this collation, and will also appear in the Sybase Central Create Database wizard for ASA. Collation 874THAIBIN does not attempt to provide linguistically-correct sorting for Thai characters, but sorts the characters in binary order. The collation does provide character set mappings to cp874 (and TIS-620, which is compatible with cp874). On a Windows system configured for Thai, dbinit and the CREATE DATABASE statement will now default to this collation, and will also appear in the Sybase Central Create Database wizard for ASA.

CR:359212

CR Number:   359212 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2348 25 Nov 2004 Fixed 9.0.1 1882 23 Jun 2004 Fixed 9.0.0 1330 23 Jun 2004 Fixed 8.0.3 5124 23 Jun 2004 Fixed 8.0.2 4438 23 Jun 2004 Fixed Description The debug server log, (output generated bu -z command line option), could have contained extraneous "Communication function <function name> code <number>" diagnostic messages. For example after stopping a database using dbstop. Similarly there could have been extraneous instances of this diagnostic message in the client LogFile. These extraneous diagnostic messages have been removed. Please note that this diagnostic message can still validly occur under some circumstances and may be useful to help Technical Support diagnose other problems. This change also prevents some spurious "connection ... terminated abnormally" messages.

CR:359229

CR Number:   359229 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1886 29 Jun 2004 Fixed 9.0.0 1324 29 Jun 2004 Fixed Description When using the iAnywhere Solutions ODBC driver for DB2, to insert BLOB data bigger than 32K bytes, the data at location 32752 wouldhave been corrupted when fetching BLOB data back in chunks. The trailing byte of a buffer was being set to 0x00. This problem has been corrected.

CR:359242

CR Number:   359242 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 2348 24 Jun 2004 Fixed 9.0.1 1882 24 Jun 2004 Fixed 9.0.0 1329 24 Jun 2004 Fixed 8.0.3 5123 24 Jun 2004 Fixed 8.0.2 4438 24 Jun 2004 Fixed Description The server could have crashed when attempting to get a db_property for a database which is in the process of being started. When a database is being started, a "stub" database object is added to the server's list of databases, which has NULL pointers for a number of fields, including the statistics counter array. Calling the db_property() function would have attempted to get statistics for the stub database. Fixed by only getting properties for active databases.

CR:359265

CR Number:   359265 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 2347 22 Jun 2004 Fixed 9.0.1 1882 22 Jun 2004 Fixed 9.0.0 1329 22 Jun 2004 Fixed Description When run on Sun Solaris systems, the server would have tried to load an incorrect LDAP shared object name, libldap_r.so. This has been corrected, the server now loads libldap.so.

CR:359409

CR Number:   359409 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2351 25 Jun 2004 Fixed 9.0.1 1884 25 Jun 2004 Fixed 9.0.0 1330 25 Jun 2004 Fixed 8.0.3 5125 25 Jun 2004 Fixed 8.0.2 4439 25 Jun 2004 Fixed 8.0.1 3157 25 Jun 2004 Fixed Description When a java.sql.Timestamp type value was inserted into a column of type TIMESTAMP, the conversion of the nanosecond portion of the java timestamp to the microsecond portion of the UlDateTime was incorrect. Thus timestamps like 01:20:60 were possible. This has now been corrected.

CR:359428

CR Number:   359428 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2348 23 Jun 2004 Fixed 9.0.1 1882 23 Jun 2004 Fixed 9.0.0 1330 23 Jun 2004 Fixed 8.0.3 5124 23 Jun 2004 Fixed 8.0.2 4438 23 Jun 2004 Fixed Description A memory leak can have occurred in the ODBC driver if the database server closed the connection for any reason, for example an idle time-out. A pointer to the driver's connection object was being set to null, but the object was not freed. This has now been corrected.

CR:359568

CR Number:   359568 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5122 25 Jun 2004 Fixed Description When using the iAnywhere Solutions ODBC driver for DB2 on Windows systems, (wqdb219.dll), and fetching BLOB data back in chunks, the trailing byte of the buffer would have been set to 0x00. This problem has been corrected.

CR:359575

CR Number:   359575 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5122 06 Aug 2004 Fixed Description When using the iAnywhere Solutions 8 Oracle WP driver for Win32 to connect to Oracle 9i, NCHAR data was not correctly returned from the server. This problem is fixed in version 4.20.0081 of this driver. To update the driver, the following files need to be updated: wqora1919.dll wqora19r.dll wqora19s.dll wqbas19.dll wqbas19r.dll wqicu19.dll wqutl19.dll wqutl19r.dll

CR:359576

CR Number:   359576 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 2350 24 Jun 2004 Fixed Description For collations supporting the languages UKRAINIAN, CZECH, HUNGARIAN, GREEK, HEBREW, ARABIC, TURKISH, DUTCH, LITHUANIAN, THAI, db_property( 'language' ) would not have report those languages. For example, in a 1251CYR database, 'ru,en' would have been reported instead of 'uk,ru,en'. The collation UTF8 was missing all of the above languages. Now, the db_property() function will return all languages supported by ASA and by the specified collation. For many collations, the returned string will change (get longer). So, an application may break if it checks for the entire string, rather than the specific two-letter language code.

CR:359675

CR Number:   359675 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 2350 25 Jun 2004 Fixed 9.0.1 1884 25 Jun 2004 Fixed 9.0.0 2350 25 Jun 2004 Fixed 8.0.3 5124 25 Jun 2004 Fixed 8.0.2 4439 25 Jun 2004 Fixed Description When a binary array of bytes was inserted into a binary column using the OLEDB provider "ASAProv", the data was converted to a hexadecimal string and stored into the binary column. For example: BYTE m_lParm1[2]={0x10,0x5f); would have been stored as the binary value 0x31303566 which is the original binary value stored as a hexadecimal string of characters. This has been fixed so that parameters are not converted from the user's type to a string. Instead, bound parameters are converted to the type specified by the application.

CR:359741

CR Number:   359741 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 2369 13 Jul 2004 Fixed 9.0.1 1892 13 Jul 2004 Fixed 9.0.0 1337 13 Jul 2004 Fixed 8.0.3 5132 13 Jul 2004 Fixed 8.0.2 4447 13 Jul 2004 Fixed Description If a synchronization was performed prior to changing the database options Truncate_timestamp_values to ON and Default_timestamp_increment to a value which would disallow timestamp values with extra digits of precision, the next synchronization would have caused a server crash. The server will now display an assertion indicating that an attempt to store an invalid timestamp value in a temporary table was made. The options must be changed before the first synchronization is performed.

CR:359745

CR Number:   359745 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 2384 03 Aug 2004 Fixed 9.0.1 1900 03 Aug 2004 Fixed 9.0.0 1344 03 Aug 2004 Fixed 8.0.3 5140 03 Aug 2004 Fixed 8.0.2 4454 03 Aug 2004 Fixed Description If a stored procedure declared a temporary table and returnd a result set, opening a cursor on the procedure would have made the temporary table visible outside the procedure. This has been fixed.

CR:359828

CR Number:   359828 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4441 30 Jun 2004 Fixed 8.0.3 5126 30 Jun 2004 Fixed 9.0.1 1886 30 Jun 2004 Fixed Description When the Histogram utility dbhist, was run on non-English systems, mangled characters would have been shown in the title, legend, etc, of the generated Excel chart. This problem has now been corrected.

CR:359844

CR Number:   359844 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 2354 29 Jun 2004 Fixed 9.0.1 1885 29 Jun 2004 Fixed Description If "XML" was chosen in the "Files of type" setting in the "Save" dialog, the file would have been saved with an extension of "sql" rather than "xml". The file contents were correct, just the file name was wrong. This problem affected only Linux and Solaris platforms, and has been fixed.

CR:359877

CR Number:   359877 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2354 30 Jun 2004 Fixed 9.0.1 1885 30 Jun 2004 Fixed 9.0.0 1331 30 Jun 2004 Fixed Description If the Synchronization Client's (dblmsync) extended option Downloadbuffersize, was not set to 0 (the default value is 1 Meg), and a communication error occurred while receiving the download stream from the MobiLink server, the synchronization would have failed, but no error message would have been reported and the sp_hook_dbmlsync_download_com_error hook would not have been called. An error is now issued and the hook is now called in this case.

CR:359889

CR Number:   359889 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2381 28 Jul 2004 Fixed Description If clustered indexes were available to the Index Consultant, a clustered index was almost always recommended on each table. This led to the recommendation of clustered indexes when they provided no benefit (for example, when they were not used for range scans). Clustered indexes are now only recommended if they are actually picked by the optimizer in preference to a non-clustered index for a given query.

CR:360001

CR Number:   360001 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2355 29 Jun 2004 Fixed 9.0.1 1886 29 Jun 2004 Fixed 8.0.3 5126 29 Jun 2004 Fixed 8.0.2 4441 29 Jun 2004 Fixed 9.0.0 1336 19 Jul 2004 Fixed Description The context menu for Results tables could have appeared far from the mouse pointer if the whitespace to the right or below the actual table data was clicked on. This has been fixed so that the context menu always appears where the mouse was clicked.

CR:360041

CR Number:   360041 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 2379 30 Jun 2004 Fixed 9.0.1 1896 30 Jun 2004 Fixed Description On Linux systems, an error dialog window could have been opened without it being made the active window. This made it almost impossible to close without using a mouse, which is contrary to the Section 508 accessibility guidelines. This has been fixed so that the window is now always activated.

CR:360190

CR Number:   360190 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2356 12 Jul 2004 Fixed 9.0.1 1886 12 Jul 2004 Fixed 9.0.0 1332 12 Jul 2004 Fixed 8.0.3 5127 12 Jul 2004 Fixed 8.0.2 4441 12 Jul 2004 Fixed Description SQL Remote (dbremote) may have hung when scanning transaction logs if the server logged a checkpoint that has a previous checkpoint pointing to itself. This problem has been fixed. Note, this problem also affected Mobilink's Synchroniztion Client and the ASA Replication Agent

CR:360196

CR Number:   360196 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2356 30 Jun 2004 Fixed 9.0.1 1886 30 Jun 2004 Fixed 9.0.0 1332 30 Jun 2004 Fixed 8.0.3 5127 30 Jun 2004 Fixed 8.0.2 4441 30 Jun 2004 Fixed Description The ASA OLEDB provider ASAProv did not return the correct error codes as documented by Microsoft. For example, the ICommand::Execute method should have returned DB_E_INTEGRITYVIOLATION when a literal value in the command text violated the integrity constraints for a column, but was returning E_FAIL. This has been corrected. The following additional error codes are also now returned: DB_E_NOTABLE DB_E_PARAMNOTOPTIONAL DB_E_DATAOVERFLOW DB_E_CANTCONVERTVALUE DB_E_TABLEINUSE DB_E_ERRORSINCOMMAND DB_SEC_E_PERMISSIONDENIED

CR:360202

CR Number:   360202 Product Name:   UltraLite Product Component:   UltraLite for AppForge MobileVB Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2350 30 Jun 2004 Fixed 9.0.1 1884 30 Jun 2004 Fixed Description On Palm devices, explicitly closing the connection, would have caused Hotsync to fail with a SQLE_SYNC_INFO_INVALID error. Now, Hotsync on Palm devices will succeed even if the connection is explicitly closed. This does not affect Windows systems.

CR:360207

CR Number:   360207 Product Name:   UltraLite Product Component:   UltraLite for AppForge MobileVB Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2354 30 Jun 2004 Fixed 9.0.1 1885 30 Jun 2004 Fixed Description Some registry entries would have been left when uninstalling UltraLite for AppForge MobileVb, (ulmvbreg -u). Now all registry entries are completely removed.

CR:360237

CR Number:   360237 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Novell NetWare Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2377 21 Jul 2004 Fixed 9.0.1 1895 21 Jul 2004 Fixed 9.0.0 1341 21 Jul 2004 Fixed 8.0.3 5136 21 Jul 2004 Fixed 8.0.2 4450 21 Jul 2004 Fixed Description Memory-intensive operations, such as a sort, hash join, hash group-by, or hash distinct, could have caused the server to fail with a fatal memory exhausted error, if they were executed in an environment where the operation could not be completed completely in the available memory. This issue affected all platforms, and has now been fixed.

CR:360238

CR Number:   360238 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) 2936 14 Oct 2004 Fixed 9.0.2 2529 14 Oct 2004 Fixed 9.0.1 1932 14 Oct 2004 Fixed 9.0.0 1374 14 Oct 2004 Fixed Description The system extended stored procedure xp_cmdshell will now accept command lines up to 8000 bytes.

CR:360242

CR Number:   360242 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2356 30 Jun 2004 Fixed Description The Histogram utility dbhist, would have reported that the histogram contained no data, when Excel was not installed, even if statistics did exist. This error message has been corrected, a new error message "Unable to create Excel Workbook' has been added.

CR:360258

CR Number:   360258 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.1 1887 05 Jul 2004 Fixed 9.0.0 1333 05 Jul 2004 Fixed 8.0.3 5128 05 Jul 2004 Fixed 8.0.2 4442 05 Jul 2004 Fixed 9.0.2 2358 05 Jul 2004 Fixed Description The total accumulated delay caused by the sp_hook_dbmlsync_delay hook was being calculated incorrectly when a synchronization was restarted using the sp_hook_dbmlsync_end hook. As a result the sp_hook_dbmlsync_delay hook might not be called or the delay produced by the hook might be shorter than specified. Following are the specific conditions required to see this problem: - Both an sp_hook_dbmlsync_end hook and an sp_hook_dbmlsync_delay hook have been coded. - During a synchronization the delay hook was called one or more times. Those calls resulted in a total delay D and the maximum accumulated delay parameter was set to some value M. - When the end hook is called it sets the 'restart' parameter to 'sync' or 'true' to restart the synchronization. When the above conditions are met, the sum of delays caused by the delay hook was not being reset before the synchronization was restarted. As a result, on the restarted synchronization, the delay hook would not be called if D >= M. If D < M then the maximum delay that would be allowed before the synchronization occurred would be M - D when it should have been M. The sum of delays is now reset before the synchronization is restarted so that the delay hook will have the same behavior on a restarted synchronization as it does on a first synchronization.

CR:360311

CR Number:   360311 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2368 14 Jul 2004 Fixed 9.0.1 1891 14 Jul 2004 Fixed 9.0.0 1337 14 Jul 2004 Fixed 8.0.3 5132 14 Jul 2004 Fixed 8.0.2 4446 14 Jul 2004 Fixed Description A query with a large number of OR'ed predicates (about 20,000 on Windows systems) may have caused the server to crash. For example: select T2_N.b from T1, T2, T2_N where T1.a = T2.b and T2.b = T2_N.b and ( T1.a = 1 or T1.a = 2 or T1.a = 3 or .... or T1.a = 20000) The number of OR conditions to cause the crash depended on the available stack size. This problem has been fixed. Now these queries return an error "Statement size or complexity exceeds server limits".

CR:360357

CR Number:   360357 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 2357 12 Jul 2004 Fixed 9.0.1 1887 12 Jul 2004 Fixed Description In some circumstances, the UltraLite Schema Painter would have failed to allow the user to create a new schema file. This has been fixed. The following steps demonstrate the problem: - Create a new Schema File - Right click on the schema file in the left pane of the application - Close the schema file and choose not to save it - Attempt to create a new schema file

CR:360361

CR Number:   360361 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) 8.0.3 5127 05 Jul 2004 Fixed 9.0.1 1887 05 Jul 2004 Fixed 9.0.2 2357 05 Jul 2004 Fixed Description In some circumstances, the UltraLite Schema Painter would have crashed when browsing the File menu. This has been fixed. The following could have caused this behaviour: - Start the UltraLite Schema painter and create a new schema - Right click on the schema in the left pane but do not choose any menu items - Select the File menu and choose Close (when asked to save, click No) - Select the File menu again and move over the items in the menu. The application could crash at this point.

CR:360362

CR Number:   360362 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 2357 12 Jul 2004 Fixed Description When creating a new schema file in the UltraLite Schema Painter, if the directory didnt exist, the new schema file would not have been saved properly. Now, the user is prompted whether the new directory should be created.

CR:360455

CR Number:   360455 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2361 12 Jul 2004 Fixed 9.0.1 1888 12 Jul 2004 Fixed 9.0.0 1334 12 Jul 2004 Fixed 8.0.3 5129 12 Jul 2004 Fixed 8.0.2 4443 12 Jul 2004 Fixed Description During unloading or rebuilding a database a non-clustered index may have been recreated as a clustered index. This would have happened if there was at least one table with a clustered index and subsequent unloaded table definitions had a non-clustered index with the same index id as the clustered index. This has now been fixed.

CR:360460

CR Number:   360460 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 2529 21 Sep 2004 Fixed 9.0.1 1924 21 Sep 2004 Fixed Description An UPDATE statement may have failed unexpectedly with the error "No primary key value for foreign key". For this problem to have occurred, multiple rows had to have been updated, the table had to have a trigger that contained a SET TEMPORARY OPTION statement, and the table had to have at least on Foreign Key with a referencial action defined. This problem has been fixed, there is no longer an error in this situation. The workaround is to remove the SET TEMPORARY OPTION statements. Workaround Description  Add CHECK ON COMMIT for the FKs ProfilesAttached and ProfileString ALTER TABLE "BTI"."ProfilesAttached" DROP FOREIGN KEY "Profiles"; ALTER TABLE "BTI"."ProfilesAttached" DROP FOREIGN KEY "Profiles"; ALTER TABLE "BTI"."ProfilesAttached" ADD FOREIGN KEY "Profiles" ( "ProfileID" ) REFERENCES "BTI"."Profiles" ( "ProfileID" ) ON UPDATE CASCADE ON DELETE CASCADE CHECK ON COMMIT; ALTER TABLE "BTI"."ProfileString" DROP FOREIGN KEY "Profiles"; ALTER TABLE "BTI"."ProfileString" DROP FOREIGN KEY "Profiles"; ALTER TABLE "BTI"."ProfileString" ADD NOT NULL FOREIGN KEY "Profiles" ( "ProfileID" ) REFERENCES "BTI"."Profiles" ( "ProfileID" ) ON UPDATE CASCADE ON DELETE CASCADE CHECK ON COMMIT;

CR:360464

CR Number:   360464 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 2358 12 Jul 2004 Fixed 9.0.1 1887 12 Jul 2004 Fixed 9.0.0 1333 12 Jul 2004 Fixed 8.0.3 5128 12 Jul 2004 Fixed 8.0.2 4442 12 Jul 2004 Fixed Description If a grouped query had a base table's column T.A in its select list, and the table T qualified to be eliminated by the join elimination algorithm, then T.A might have been incorrectly renamed. This has been fixed. For example: The query below returned a result set which had the first column renamed "A2": create table T1 ( A1 int primary key); create table T2 ( A2 int, foreign key (A2 ) references T1(A1) ); select A1 from T1 key join T2 group by A1 Note that the query was rewritten by the join elimination algorithm into: select A2 from T2 group by A2 Now, the query is rewritten into: select A2 as A1 from T2 group by A2 A work around for this problem is to alias all the columns referenced in the SELECT list with their own names. For example, the query Q' below is not affected by this bug: Q': select A1 as A1 from T1 key join T2 group by A1

CR:360479

CR Number:   360479 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   7.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2358 12 Jul 2004 Fixed 9.0.1 1887 12 Jul 2004 Fixed 9.0.0 1333 12 Jul 2004 Fixed 8.0.3 5128 12 Jul 2004 Fixed 8.0.2 4442 12 Jul 2004 Fixed Description The ODBC SQLDisconnect() function could have returned a failing error code if the server dropped the client's connection (e.g. for idle time-out reasons), while the connection had a dirty transaction to be committed or rolled back (i.e. SQLExecute, SQLExecDirect or SQLSetPos was called), and SQL_AUTOCOMMIT_OFF option was set ON for the connection. Now, SQLDisconnect() returns SQL_SUCCESS_WITH_INFO and sets the SQLSTATE to 01002 (Disconnect error).

CR:360584

CR Number:   360584 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 2361 12 Jul 2004 Fixed 9.0.1 1884 12 Jul 2004 Fixed Description The Join Nested Block (JNB) operator will no longer be considered a fully pipelined join operator while optimizing with the database option Optimization_goal set to 'first-row'. Although the JNB operator is not a fully materializing operator, it may block and force the usage of a work table. Now, while optimizing for the 'first-row' optimization goal, this operator is less likely to appear in the plan chosen.

CR:360591

CR Number:   360591 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 2361 12 Jul 2004 Fixed 9.0.1 1888 12 Jul 2004 Fixed 9.0.0 1334 12 Jul 2004 Fixed 8.0.3 5129 12 Jul 2004 Fixed 8.0.2 4443 12 Jul 2004 Fixed Description A data reader opened with a select statement would have held a lock on the table, even after the data reader had been closed. This has now been fixed.

CR:360597

CR Number:   360597 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2361 12 Jul 2004 Fixed 9.0.1 1888 12 Jul 2004 Fixed 9.0.0 1334 12 Jul 2004 Fixed 8.0.3 5129 12 Jul 2004 Fixed 8.0.2 4443 12 Jul 2004 Fixed Description Applications attempting Shared memory connections may have hung if the server was forcibly shut down during the connection attempt. This has been fixed.

CR:360678

CR Number:   360678 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2363 12 Jul 2004 Fixed 9.0.1 1889 12 Jul 2004 Fixed 9.0.0 1335 12 Jul 2004 Fixed 8.0.3 5130 12 Jul 2004 Fixed 8.0.2 4444 12 Jul 2004 Fixed Description ADO applications using the ASA OLEDB provider, ASAProv, could have failed with an "invalid rowset accessor" error. The following Visual Basic code example demonstrates the problem: Dim conn As new OleDbConnection() Dim cmd As OleDbCommand Dim reader As OleDbDataReader Try conn.ConnectionString = "Provider=ASAProv;uid=dba;pwd=sql;eng=asademo" conn.Open() cmd = New OleDbCommand("SELECT * FROM DEPARTMENT", conn) reader = cmd.ExecuteReader() While reader.Read() Console.WriteLine(reader.GetInt32(0).ToString() + ", " _ + reader.GetString(1) + ", " + reader.GetInt32(2).ToString()) End While reader.Close() reader = Nothing conn.Close() conn = Nothing Catch ex As Exception MessageBox.Show(ex.Message) End Try This problem has been fixed, the rgStatus array passed to the IAccessor::CreateAccessor method is now correctly initialized.

CR:360694

CR Number:   360694 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 2376 20 Jul 2004 Fixed 9.0.1 1895 20 Jul 2004 Fixed 9.0.0 1340 20 Jul 2004 Fixed 8.0.3 5135 20 Jul 2004 Fixed 8.0.2 4450 20 Jul 2004 Fixed 7.0.4 3527 20 Jul 2004 Fixed Description The server could have deadlocked, and appear to be hung, if a transaction yielded to a checkpoint (by context switching, waiting for a lock or waiting for network I/O) after rolling back to a savepoint. This has been fixed.

CR:360761

CR Number:   360761 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 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 Calling the AsaDataAdapter.Fill method multiple times on the same DataTable that had a primary key, woulkd have caused a 'System.Data.ConstrainException' exception on the second call. Now, if a primary key exists, incoming rows are merged with matching rows that already exist. If no primary key exists, incoming rows are appended to the DataTable. If primary key information is present, any duplicate rows are reconciled and only appear once in the DataTable.

CR:360885

CR Number:   360885 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 2381 28 Jul 2004 Fixed 9.0.1 1898 28 Jul 2004 Fixed 9.0.0 1342 28 Jul 2004 Fixed 8.0.3 5139 29 Jul 2004 Fixed 8.0.2 4454 29 Jul 2004 Fixed Description Using variable assignments in a positioned update, (e.g update T1 set id = @V1, @V1 = @V1 + 1 where current of curs), would have caused a server crash. Now, variable assignments in a positioned update are supported.

CR:360896

CR Number:   360896 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2364 13 Jul 2004 Fixed 9.0.1 1890 13 Jul 2004 Fixed Description When inserting into a numeric column, no error was raised when the precision exceed the precision allowed by the column. The column would have been corrupt if the insert was committed. Now an overflow error is raised on insert.

CR:360904

CR Number:   360904 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2377 20 Jul 2004 Fixed 9.0.1 1895 20 Jul 2004 Fixed Description The reload.sql file generated by the Database Unload utility dbunload, may have contained garbled object names if the connection character set and database character set were different. This problem has now been fixed.

CR:360936

CR Number:   360936 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2372 20 Jul 2004 Fixed 9.0.1 1892 20 Jul 2004 Fixed Description When two instances of the same table are joined on the primary key then, under certain conditions, it is possible to eliminate one of the instances. For example, given the following table: create table T ( A int primary key, B int); the statement: DELETE from T as T0 from T as T0 natural join T as T1 is equivalent to: DELETE from T as T0 where T0.B = T0.B This optimization was only done for SELECT statements when the table to be eliminated was not updatable. Now, this optimization is done for DELETE and UPDATE statements when the table to be eliminated is not the table to be modified.

CR:360966

CR Number:   360966 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 2365 13 Jul 2004 Fixed Description When performing an absolute fetch, the query processor always started either from the first or last row of a cursor. In some cases, it is safe to start from the current row (for example, if none of the tables in the query had been modified since the last absolute fetch). Now, the query processor moves from the current row, if it is safe to do so, possibly improving performance.

CR:361088

CR Number:   361088 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2368 13 Jul 2004 Fixed 9.0.1 1891 13 Jul 2004 Fixed 9.0.0 1337 13 Jul 2004 Fixed Description When a publication contained a table with a foreign key or a chain of foreign keys (ie t1 has an FK to t2, t2 has an FK to t3 etc) to a table listed in the EXCLUDEOBJECT system table and the table listed in the EXCLUDEOBJECT table was not included in the publication being synchronization, then the upload would fail with the message, "Upload aborted aborted at offset...". The message now includes a description of why the upload was aborted.

CR:361115

CR Number:   361115 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 1659 08 Apr 2005 Fixed 9.0.2 2552 08 Apr 2005 Fixed 9.0.1 2009 08 Apr 2005 Fixed Description If Interactive SQL was run in batch mode with the output redirected to a file, executing a statement that caused a warning from the server would appear to have hung. What was happening was that Interactive SQL was waiting for a key to be pressed to continue execution after reporting the warning, the prompt had been suppressed. Now, warnings are displayed without prompting when run in batch mode. Operation in windowed mode has not been changed.

CR:361184

CR Number:   361184 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 2370 16 Jul 2004 Fixed 9.0.1 1892 16 Jul 2004 Fixed 8.0.3 5133 16 Jul 2004 Fixed 8.0.2 4447 16 Jul 2004 Fixed Description A query with a large WHERE clause containing the conjunction and disjunction of many literals could have caused the server to hang with 100% cpu usage and eventually run out of memory and fail with a "Dynamic Memory Exhausted" message. This has been fixed.