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

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

CR:324770

CR Number:   324770 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.1 1583 10 Jul 2003 Fixed 9.0.0 1180 10 Jul 2003 Fixed Description This change fixes a problem where the QueryEditor was throwing an exception) if the query was terminated with a semicolon.

CR:324771

CR Number:   324771 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.0 1063 10 Jul 2003 Fixed Description Unloading the ASA plug-in would have caused Sybase Central to crash. This is now fixed.

CR:324774

CR Number:   324774 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.1 1583 10 Jul 2003 Fixed 9.0.0 1180 10 Jul 2003 Fixed Description The QueryEditor was not correctly adding parenthesis around the GROUP BY list for the ROLLUP operator. The parenthesis are now added.

CR:324840

CR Number:   324840 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1602 24 Jul 2003 Fixed 9.0.0 1194 24 Jul 2003 Fixed Description If SQL Anywhere for Windows was installed and the program folder was changed to be to be something other than the default, then the 'Deploy SQL Anywhere for CE' entry would still have been created in the default group. This has been fixed so that it is now created in the correct program folder Workaround Description  Manually clean up the program groups.

CR:324841

CR Number:   324841 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1584 11 Jul 2003 Fixed 9.0.0 1180 11 Jul 2003 Fixed 8.0.3 4715 11 Jul 2003 Fixed 8.0.2 4282 11 Jul 2003 Fixed Description When a procedure returns multiple result sets, the SQLMoreResults() function is used in ODBC to move to the next result set. If that next statement returned a warning, SQLMoreResults would have completed without opening the result set. The problem is now fixed, and SQLMoreResults will return SQL_SUCCESS_WITH_INFO indicating that the result set is open, but that a warning was returned.

CR:324845

CR Number:   324845 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1584 14 Jul 2003 Fixed 9.0.0 1180 14 Jul 2003 Fixed 8.0.3 4715 14 Jul 2003 Fixed 8.0.2 4282 14 Jul 2003 Fixed Description The connection between the ISAPI redirector and MobiLink could have timed out during data synchronization, resulting in the data synchronization failing. This was fixed by keeping the connection open. A work around is to increase the system timeout interval, (default is 4 minutes), by setting the following registry key (value is in seconds): \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay

CR:324846

CR Number:   324846 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.1 1589 14 Jul 2003 Fixed 9.0.0 1182 14 Jul 2003 Fixed Description Trivial contradictions in a CHECK constraint that could have caused a server crash when an INSERT or UPDATE of any row in the table was done has now been fixed. For example, given a table T with not-null column X, a CHECK constraint of the form CHECK( T.x is NULL) would have caused a server on the insertion or update of any row in table T.

CR:324897

CR Number:   324897 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) 9.0.1 1589 14 Jul 2003 Fixed 9.0.0 1183 14 Jul 2003 Fixed 8.0.3 4721 14 Jul 2003 Fixed 8.0.2 4286 14 Jul 2003 Fixed Description If a DELETE TRIGGER statement failed, a subsequent DELETE of a row from the table would have caused a server hang. For this to have occurred, the trigger must have failed due to an attempt to delete a row that still had foreign keys referencing it, The Wait_for_commit option must have been off, and the table being deleted from must have had a trie-based index as the index with lowest index id [e.g. the pk index if a pk exists]. This has now been fixed. Workaround Description  non

CR:324914

CR Number:   324914 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.1 1587 09 Jul 2003 Fixed 9.0.0 1180 09 Jul 2003 Fixed Description When running dbisql on a Chinese Windows XP machine, typing Chinese characters in any text field would have displayed as boxes if support for the GB18030 font had not been installed. This affected Sybase Central and DBConsole as well. This has now been fixed.

CR:324927

CR Number:   324927 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.1 1588 14 Jul 2003 Fixed 9.0.0 1109 14 Jul 2003 Fixed Description Starting the server with the communications protocol SPX on a multi-processor NetWare machine, would have caused the server to abend. This has been fixed.

CR:324931

CR Number:   324931 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.1 1576 10 Jul 2003 Fixed 9.0.0 1180 10 Jul 2003 Fixed Description The Escape key would only have closed the Find/Replace dialog when the Find field had focus. This has been fixed.

CR:324932

CR Number:   324932 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.1 1587 10 Jul 2003 Fixed 9.0.0 1180 10 Jul 2003 Fixed 8.0.3 4718 10 Jul 2003 Fixed 8.0.2 4283 10 Jul 2003 Fixed Description Dropping tables or adding foreign keys could have resulted in an invalid schema. Also the Schema Painter was not properly detecting foreign key cycles, which could have caused problems during synchronizations. MobiLink requires that parent tables be synchronized before child tables and this condition wasn't being guaranteed by the schema created in the Schema Painter. Both of these problems have now been fixed. In order to fix an invalid schema, use the (fixed) ulxml tool or Schema Painter to write the schema out to as an XML file, then reload it back in. The process of reloading it will correct the table order.

CR:324972

CR Number:   324972 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1643 25 Sep 2003 Fixed 9.0.0 1218 25 Sep 2003 Fixed 8.0.3 4789 25 Sep 2003 Fixed 8.0.2 4319 25 Sep 2003 Fixed 8.0.1 3132 25 Sep 2003 Fixed Description A Visual Basic application using the OLEDB driver could have failed with the error "Run-time error '-2147467259 (80004005)': Unspecified error" if the function DoEvents was called. The dboledbax.dll is a COM object, thus has an entry point DLLCanUnloadNow(), which is called infrequently by Visual Basic, whenever DoEvents is called. Each time it was called though, the routine would have returned TRUE (meaning "it is OK to be unloaded"). Eventually, Visual Basic would have unloaded the DLL, even though it was still in use. This has now been fixed. Calls to DLLCanUnloadNow() will now only return TRUE when the DLL can safely be unloaded.

CR:324988

CR Number:   324988 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1610 21 Aug 2003 Fixed 9.0.0 1215 11 Sep 2003 Fixed 8.0.3 4739 21 Aug 2003 Fixed 8.0.2 4296 21 Aug 2003 Fixed Description For queries with more than one table and equijoins predicates (e.g., 'key joins'), the error "Dynamic Memory Exhausted" may have been generated if the server ran with a very small cache. This issue has been fixed. An Example: select * from systable T key join syscolumn C key join sysuserperm U

CR:324989

CR Number:   324989 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.1 1588 10 Jul 2003 Fixed 9.0.0 1180 10 Jul 2003 Fixed 8.0.3 4719 10 Jul 2003 Fixed 8.0.2 4284 10 Jul 2003 Fixed Description Starting dbisqlc on a Windows machine with a connection string that specified a character set different from the OS character set (e.g. "cs=cp1251"), would have caused it to crash on shutdown. This is now fixed. Note, any executable that used the Unicode translation library, (dbunic9.dll on 9.0.0 or libunic.dll otherwise), and which also loaded and unloaded the DBLIB or ODBC client libraries could have encountered this problem.

CR:324993

CR Number:   324993 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.0 1109 14 Jul 2003 Fixed Description The HTTP service would have returned an internal HTTP server error (500), when the socket buffer became full. The service should have continued sending in blocking mode. This is now fixed.

CR:325000

CR Number:   325000 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.1 1588 11 Jul 2003 Fixed 9.0.0 1181 11 Jul 2003 Fixed 8.0.3 4719 11 Jul 2003 Fixed 8.0.2 4284 11 Jul 2003 Fixed Description If a query's WHERE clause satisfied the conditions given below, the server would have crashed during optimization. This problem has now been fixed. (1) the WHERE clause must have contained a tautology (found in the original WHERE clause or generated by a rewrite optimization) (2) there were at least two equijoin predicates referring to the same column. (ie, there were at least two predicates of the form "T.col1 = R.col1 AND T.col1 = S.col1"). For example: T.col1 = R.col1 and T.col1 = S.col1 and ( (T.col2 >=100000 and T.col2 < 2000000 and expr1 >= 1000) or (T.col2 >=2000000 and expr1 >= 10000) ) In this case a tautology was generated by one of the rewrite optimizations, namely "T.col2 < 2000000 OR T.col2 >= 2000000".

CR:325020

CR Number:   325020 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) 9.0.1 1575 17 Sep 2003 Fixed 9.0.0 1104 17 Sep 2003 Fixed 8.0.3 4706 17 Sep 2003 Fixed Description An UPDATE statement that modified multiple tables, could have caused the server to crash or to generate bad column statistics. This problem has been resolved.

CR:325022

CR Number:   325022 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) 9.0.1 1587 17 Sep 2003 Fixed 9.0.0 1107 17 Sep 2003 Fixed 8.0.3 4719 17 Sep 2003 Fixed 8.0.2 4284 17 Sep 2003 Fixed Description While updating column statistics in response to queries involving BETWEEN predicates, the server could have crashed. Whether the crash occured or not, depended upon the particular query plan chosen for execution. This has now been fixed.

CR:325023

CR Number:   325023 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.1 1588 18 Sep 2003 Fixed 9.0.0 1181 18 Sep 2003 Fixed Description In some cases, the server could have computed invalid selectivity estimates which were displayed as negative numbers in the query plans generated by the server. This problem has been resolved.

CR:325024

CR Number:   325024 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1583 18 Sep 2003 Fixed 9.0.0 1108 18 Sep 2003 Fixed 8.0.3 4719 18 Sep 2003 Fixed 8.0.2 4284 18 Sep 2003 Fixed 8.0.1 3123 18 Sep 2003 Fixed Description If a stored procedure contained code for creating another database object, (such as another stored procedure) and a SET USER command was executed while the stored procedure was running, it was possible for the object to have been created with an incorrect user in the transaction log. This problem has been resolved.

CR:325029

CR Number:   325029 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1212 04 Sep 2003 Fixed 9.0.0 1112 04 Sep 2003 Fixed 8.0.3 4770 04 Sep 2003 Fixed 8.0.2 4309 04 Sep 2003 Fixed Description When run on AIX machines with the Power4 processor, shared memory applications could have been disconnected from the server unexpectedly. The Power4 chip has a weak-memory ordering architecture. This fix puts the required memory barrier instructions at proper places in the shared memory communication protocol. Workaround: The bindprocessor command can be used to bind both the client and the server to the same CPU.

CR:325032

CR Number:   325032 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   4.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1589 15 Jul 2003 Fixed 9.0.0 1182 15 Jul 2003 Fixed 8.0.3 4720 15 Jul 2003 Fixed 8.0.2 4286 15 Jul 2003 Fixed Description When run on Windows machines, certain graphical objects could have been inadvertently displayed underneath the Windows task bar. Note that this problem was also present in Sybase Central, the Database Object Debugger, and DBConsole. These objects included: - The splash window - Context menus - Property sheets, dialogs, wizards - the editor window for stored procedures and dialogs opened from the editor The problem was especially noticeable if the taskbar was docked to the left or top edge of the screen. This has been fixed.

CR:325034

CR Number:   325034 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Windows CE 2.11 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4537 22 Jul 2003 Fixed 8.0.2 4122 22 Jul 2003 Fixed Description Install on a device running Windows CE 4.1 would have failed. This was due to the INF file used by CE Application manager only supported versions up to 4.0. Version 4.1 did not exist when 8.0.2 originally shipped. This has now been fixed. There are two work around options: 1) Install ASA 8.0.2 for Windows CE on the desktop machine, but choose _NOT_ to deploy to the device. Then install an EBF for ASA for Windows CE, build 4122 or later, which will allow the install to the device toc work correctly. 2) Edit <ASA_DIR>\ce\asa_ce.inf with a text editor In each of the following sections, change "VersionMax" to something larger than 4.1 ( for example, 5.0 ) --------------------------------------------------------------------- [CEDevice.MIPS.30] ; for MIPS processor ProcessorType = 4000 ; processor value for MIPS R3900 VersionMin = 3.0 VersionMax = 4.0 <-- change this to 5.0 [CEDevice.ARM.30] ; for StrongARM processor ProcessorType = %ArmProcessor% ; processor value for ARM VersionMin = 3.0 VersionMax = 4.0 <-- change this to 5.0 [CEDevice.X86.30] ; for X86 processor ProcessorType = x86 ; VersionMin = 3.0 VersionMax = 4.0 <-- change this to 5.0 --------------------------------------------------------------------- Workaround Description  None.

CR:325039

CR Number:   325039 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1589 11 Jul 2003 Fixed 9.0.0 1182 11 Jul 2003 Fixed 8.0.3 4720 11 Jul 2003 Fixed 8.0.2 4285 11 Jul 2003 Fixed Description Certain Unicode characters would have incorrectly compared as equal, possibly resulting in a corrupt index, if they differed only in the high byte. For example, an index containing a string column with these characters could have failed to find rows previously inserted, resulting in invalid index entries after deleting rows. This has been fixed.

CR:325093

CR Number:   325093 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.1 1589 11 Jul 2003 Fixed 9.0.0 1182 11 Jul 2003 Fixed 8.0.3 4719 11 Jul 2003 Fixed 8.0.2 4284 11 Jul 2003 Fixed Description If the server was started with the -qs command line option, and a usage error occurred, a usage dialog would have appeared on Windows platforms. The usage dialog is now suppressed if -qs is on the command line. Note that including -qs within @filename or @environment variable command line expansion will not suppress the usage dialog. Also, if a usage error now occurs, a message is appended to the -oe error log file on all platforms.

CR:325174

CR Number:   325174 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1589 14 Jul 2003 Fixed 9.0.0 1183 14 Jul 2003 Fixed Description With UltraLite, LONG VARCHAR and LONG BINARY values cannot be compared. Since comparisons are required to implement GROUP-BY and ORDER-BY, columns with LONG VARCHAR and LONG BINARY data types cannot be specified in either ORDER-BY or GROUP-BY. This situation will now be signaled as an error.

CR:325231

CR Number:   325231 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.1 1589 15 Jul 2003 Fixed 9.0.0 1182 15 Jul 2003 Fixed Description Cancelling an HTTP request could have caused the server to crash. This has been fixed.

CR:325292

CR Number:   325292 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Windows CE 2.11 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1608 28 Jul 2003 Fixed 9.0.0 1198 28 Jul 2003 Fixed 8.0.3 4737 28 Jul 2003 Fixed 8.0.2 4294 28 Jul 2003 Fixed Description The sample program simplece, may have crashed with a Fatal Application Error, when run on a Windows CE .NET 4.1 device. This has been fixed. Workaround Description  There is no workaround

CR:325396

CR Number:   325396 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) 8.0.3 4721 15 Jul 2003 Fixed 8.0.2 4286 15 Jul 2003 Fixed 8.0.1 3123 15 Jul 2003 Fixed Description The "Time_format", "Date_format", and "Timestamp_format" options were being ignored when displaying table data with the "Data" tab. This is fixed and these options are now respected.

CR:325403

CR Number:   325403 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.1 1591 15 Jul 2003 Fixed 9.0.0 1183 15 Jul 2003 Fixed 8.0.3 4720 15 Jul 2003 Fixed 8.0.2 4286 15 Jul 2003 Fixed Description Calling a proxy stored procedure (e.g. dbo.sp_remote_tables) would have resulted in a heap page being left locked in the server's cache. If the procedure was called many times, this could have exhausted the cache as well as cause the temporary file to grow. This is now fixed.

CR:325415

CR Number:   325415 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.1 1591 16 Jul 2003 Fixed 9.0.0 1183 16 Jul 2003 Fixed Description Some error messages related to debugging Java in the database would have been displayed as "null" rather than their correct text. This has been fixed.

CR:325421

CR Number:   325421 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.1 1591 15 Jul 2003 Fixed 9.0.0 1183 15 Jul 2003 Fixed Description When inserting or updating table data via the table's "Data" tab, if the server was shutdown or the connection was dropped before the insert or update was completed, any attempt to change the selected item in the tree or close Sybase Central would have resulted in an infinite number of error dialogs being displayed. This has been fixed.

CR:325437

CR Number:   325437 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.1 1619 21 Aug 2003 Fixed 9.0.0 1203 21 Aug 2003 Fixed 8.0.3 4748 21 Aug 2003 Fixed 8.0.2 4300 21 Aug 2003 Fixed Description Queries with many nested 'ANY (subquery)' predicates may have had a large OPEN time, due to rewrite optimizations applied while flattening subqueries. For this to have occurred, all the subqueries had to have been flattenable and many equality predicates were part of the original query or could have be inferred for some of the subqueries. For example: select * from t0 where t0.c2 in (select t1.c2 from t1 where t1.c2 in (select t2.c2 from t2 where t2.c2 in (select t3.c2 from t3 where t3.c2 in (select t4.c2 from t4 where t4.c2 in (select t5.c2 from t5 where t5.c2 in (select t6.c2 from t6 where t6.c2 in (select t7.c2 from t7 where t7.c2 in (select t8.c2 from t8 where t8.c2 in (select t9.c2 from t9 where t9.c2 in (select t10.c2 from t10 where t10.c2 in (select t11.c2 from t11 where t11.c2 in (select t12.c2 from t12 where t12.c2 in (select t13.c2 from t13 where t13.c2 in (select t14.c2 from t14 where t14.c2 in (select t15.c2 from t15 where t15.c2 in (select t16.c2 from t16 where t16.c2 = 30))))))))))))))))

CR:325453

CR Number:   325453 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1628 04 Sep 2003 Fixed 9.0.0 1111 04 Sep 2003 Fixed 8.0.3 4765 04 Sep 2003 Fixed 8.0.2 4307 04 Sep 2003 Fixed 8.0.1 3129 04 Sep 2003 Fixed 7.0.4 3486 04 Sep 2003 Fixed Description It was possible for the round() function to have returned an incorrect result. The number returned may have been truncated, instead of rounded, if the digit to be rounded was a 5. For example, 69.345 may have been 'rounded' to 69.34. This has been fixed.

CR:325533

CR Number:   325533 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1595 18 Jul 2003 Fixed 9.0.0 1188 18 Jul 2003 Fixed 8.0.3 4724 18 Jul 2003 Fixed 8.0.2 4286 18 Jul 2003 Fixed Description When SQLPP was supplied with a user-specified collation sequence, with a name that differed from an ASA standard collation sequence, when an Ultralite database was being generated, nothing would have been generated and the error message: Cannot generate UltraLite collation sequence for <name of collation> would be displayed. This was corrected. Workaround Description  None really [short of sticking with one of the standard collations] While it would appear that it may be possible to bypass this problem by working with a reference database that was initialized with a iAnywhere supplied collation, the -z switch s

CR:325545

CR Number:   325545 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.1 1594 15 Jul 2003 Fixed 9.0.0 1186 15 Jul 2003 Fixed Description When in the "Results Table" pane, clicking the "Copy Cell" context menu item for a BINARY column would not have copied the column data. Instead, a string of the form "[B@xxxxxx" would have been copied (with the x's being random hex digits.) Note that this bug affected the table "Data" tab in the ASA plug-in for Sybase Central as well. Both are now fixed.

CR:325668

CR Number:   325668 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1597 22 Jul 2003 Fixed 9.0.0 1189 22 Jul 2003 Fixed 8.0.3 4726 22 Jul 2003 Fixed 8.0.2 4289 22 Jul 2003 Fixed Description The dbunload utility was not adding the CLUSTERED keyword to the CREATE INDEX statement in the reload.sql file for clustered indexes, clustered primary keys, and clustered foreign keys. This has been fixed.

CR:325674

CR Number:   325674 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.1 1595 15 Jul 2003 Fixed 9.0.0 1097 15 Jul 2003 Fixed Description When adding or editing column properties on the "Columns" tab for a Table object, it was possible to select invalid values. This would have caused an error message that the values were invalid, but now the software is better at filtering out invalid values. Specifically, the following changes have been made: 1. The default size for a CHAR field is now 1. It was zero, which was not valid. 2. The up/down buttons for the spin boxes used to edit the size, scale, and precision fields are now enabled properly. Previously, clicking on a disabled button would still have done something. 3. Typing or pasting an invalid value into a spin box, then saving the table, would have saved a value which was loosely based on the invalid value. Now the last valid value for the spin box is saved.

CR:325694

CR Number:   325694 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.1 1187 16 Jul 2003 Fixed 9.0.0 1109 16 Jul 2003 Fixed Description Connections could have been dropped if the client was using TLS encryption and was running on Windows 95, 98, or ME. This has been fixed.

CR:325713

CR Number:   325713 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Windows CE 2.0 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1604 29 Jul 2003 Fixed 9.0.0 1196 29 Jul 2003 Fixed 8.0.3 4733 29 Jul 2003 Fixed 8.0.2 4294 29 Jul 2003 Fixed Description When running on Windows CE, the AsaClient would have failed with an unhandled exception on opening a database connection, if the code-page of the database was not supported by the device. Now the AsaClient will check the code page of the database and if it is not installed on the device, the AsaClient will throw an exception to inform the application.

CR:325731

CR Number:   325731 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.1 1595 16 Jul 2003 Fixed 9.0.0 1188 16 Jul 2003 Fixed Description When running the Index Consultant and capturing a large number of queries, the server could have reported that it was out of memory. Even if this did not occur, the server's memory usage would have been substantially increased every time capturing was run on a large number of queries. The memory loss could also have caused performance problems. This has been fixed. A workaround for this problem is to restart the server after running the capturing phase of the Index Consultant.

CR:325734

CR Number:   325734 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.1 1595 17 Jul 2003 Fixed 9.0.0 1187 17 Jul 2003 Fixed 8.0.3 4723 17 Jul 2003 Fixed 8.0.2 4287 17 Jul 2003 Fixed 8.0.1 3124 17 Jul 2003 Fixed Description The QueryEditor keeps a statement open so that sample results can be displayed. As the query is changed the statement is closed, recreated, and executed. The statement was being left open, leaving the table locked. Now, when the QueryEditor's dialog has been closed the statement is also closed.

CR:325741

CR Number:   325741 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.1 1187 18 Jul 2003 Fixed 9.0.0 1109 18 Jul 2003 Fixed 8.0.3 4724 18 Jul 2003 Fixed 8.0.2 4291 21 Jul 2003 Fixed 8.0.1 3125 21 Jul 2003 Fixed 7.0.4 3476 21 Jul 2003 Fixed Description When the server was running on NetWare, if a string containing the '%' character was displayed on the server console (through the MESSAGE statement or request-level logging), the server could have displayed garbage or crashed. This has been fixed.

CR:325782

CR Number:   325782 Product Name:   UltraLite Product Component:   SQL Preprocessor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1595 18 Jul 2003 Fixed 9.0.0 1188 18 Jul 2003 Fixed 8.0.3 4724 18 Jul 2003 Fixed 8.0.2 4286 18 Jul 2003 Fixed Description When SQLPP was supplied with a user-specified collation sequence file that did not exist, the SQLPP utility would have crashed. This is now fixed.

CR:325853

CR Number:   325853 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1628 03 Sep 2003 Fixed Description When exporting a table to an Excel spreadsheet using the OUTPUT statement, all the column values were being written out as labels (strings). Now, the following data conversions are used instead: SQL Type Excel Type TINYINT, SMALLINT Integer INTEGER, BIGINT Numeric FLOAT, REAL, DOUBLE, DECIMAL, NUMERIC Numeric BIT BoolErr (everything else) Label

CR:325861

CR Number:   325861 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.1 1594 16 Jul 2003 Fixed 9.0.0 1109 16 Jul 2003 Fixed 8.0.3 4724 16 Jul 2003 Fixed 8.0.2 4287 16 Jul 2003 Fixed Description In some rare situations a 64-bit server could have failed to correctly read column statistics that were created in the database by a 32-bit server. The failure could also have lead to the 64-bit server crashing. This has been fixed.

CR:325868

CR Number:   325868 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.1 1596 21 Jul 2003 Fixed 9.0.0 1109 21 Jul 2003 Fixed 8.0.3 4725 21 Jul 2003 Fixed 8.0.2 4289 21 Jul 2003 Fixed Description Starting the evaluation version of the MobiLink server would have showed the 60-day evaluation notice and waited for user input. Pressing 'Enter' would have caused the notice to have been re-displayed again. The evaluation screen message that asks the user to hit 'Y' or 'Yes' to accept the license agreement, was not being displayed. This is now fixed, but a work around is to enter 'Y' or 'YES' to confirm acceptance of the evaluation license agreement.

CR:325869

CR Number:   325869 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.1 1596 21 Jul 2003 Fixed 9.0.0 1109 21 Jul 2003 Fixed Description A NullReferenceException could have been thrown when AsaDataReader was finalized by .NET CLR. This problem has been fixed.

CR:325911

CR Number:   325911 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.1 1596 21 Jul 2003 Fixed 9.0.0 1188 21 Jul 2003 Fixed Description With Appforge MobileVB, if a persistent_name was specified upon opening, a table could later be reopened to it's current position as long as it was not closed. If a table was closed, then the table should not be reopen to it's current position. It was always reopening to the current position, wether or not the table was closed. This is now fixed.

CR:326018

CR Number:   326018 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.1 1597 22 Jul 2003 Fixed 9.0.0 1189 22 Jul 2003 Fixed 8.0.3 4726 22 Jul 2003 Fixed 8.0.2 4289 22 Jul 2003 Fixed 8.0.1 3124 22 Jul 2003 Fixed Description Fetching an ESQL DT_STRING, DT_DATE, DT_TIME, or DT_TIMESTAMP host variable (or type array of char) where the length of the char array was one, did not add the null character. This has been fixed so that the null character is set (note no data is actually copied into the host variable's character array other than the null character, since there is only space for the null character). Fetching an ESQL DT_STRING with length zero on a blank padded database could have caused dblib to crash. This case was only possible when using an SQLDA, and has been fixed so that no data is copied (not even the null character).

CR:326025

CR Number:   326025 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.1 1597 22 Jul 2003 Fixed 9.0.0 1189 22 Jul 2003 Fixed 8.0.3 4726 22 Jul 2003 Fixed 8.0.2 4289 22 Jul 2003 Fixed Description Attempting to convert a string like 'May 1999' to a date or timestamp, would have failed with a conversion error when the Date_order option was set to 'DMY'. The value will now be converted using a default day of 1.

CR:326072

CR Number:   326072 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1597 23 Jul 2003 Fixed 9.0.0 1109 23 Jul 2003 Fixed 8.0.3 4726 23 Jul 2003 Fixed 8.0.2 4289 23 Jul 2003 Fixed 8.0.1 3124 23 Jul 2003 Fixed 7.0.4 3475 23 Jul 2003 Fixed Description If a database which had no user DBA (i.e. a REVOKE CONNECT FROM DBA had been done) was unloaded and reloaded on Unix using: - dbunload -ar or -an or - the Sybase Central Unload wizard and a new database file was specified then the new database would have had a user DBA and the userid used to do the unload would have had the password SQL. With builds 7.0.4.3469, 8.0.1.3121 or 8.0.2.4279 higher, the error "Invalid user ID or password" would be displayed. Earlier builds did not display any error. This has now been fixed.

CR:326078

CR Number:   326078 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) 9.0.1 1657 08 Sep 2003 Fixed Description The Upgrade, Backup, Restore, Validate, Compress, Uncompress and Create Backup Images database wizards could not have been cancelled. In addition, they did not display any status information when their operations completed. Now, a messages dialog, similar to the one used by the Create Database wizard, is displayed. The dialog always indicates whether the operation succeeded or failed, and whether the operation can be cancelled before it completes.

CR:326083

CR Number:   326083 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.1 1600 21 Jul 2003 Fixed 9.0.0 1109 21 Jul 2003 Fixed Description If a database was initialized with a collation other than UTF8, non-English characters may have appeared to have been handled incorrectly by the stored procedure debugger. For example, adding a variable with an accented character to a watch window could have caused a syntax error. The "locals" window worked correctly though. The server was not converting the strings coming from the debugger, (which are UTF8), to the database character set. This is now fixed.

CR:326118

CR Number:   326118 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1598 23 Jul 2003 Fixed 9.0.0 1190 23 Jul 2003 Fixed Description UltraLite Dynamic SQL did not support "+" as a concatenation operator. Thus, SELECT 'A' + 'B' did not produce the intended result 'AB'. This support has now been added.

CR:326148

CR Number:   326148 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2335 09 Jun 2004 Fixed Description DBRemote and DBMLSync can now specify the location of old mirror logs. This is helpful in situations where the offline mirror logs are located in directory other than where the mirror transaction log resides, or if dbremote/dbmlsync connects via a client-server connection. For dbremote, a new command line option "-ml" was added, and for dbmlsync, a new extended option MirrorLogDirectory (MLD) was created. Transaction logs in this directory will only be affected if the "delete_old_logs" database option is set to 'ON' or 'DELAY'.

CR:326150

CR Number:   326150 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1598 23 Jul 2003 Fixed 9.0.0 1109 23 Jul 2003 Fixed 8.0.3 4727 23 Jul 2003 Fixed 8.0.2 4290 23 Jul 2003 Fixed 8.0.1 3124 23 Jul 2003 Fixed 7.0.4 3475 23 Jul 2003 Fixed Description The MobiLink server may have crashed when using cursored uploads. This is now fixed, but a workaround is to disable the statement cache (-hwC+) in versions 8.0.0 and later. No workaround is available for earlier versions.

CR:326164

CR Number:   326164 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.1 1601 21 Jul 2003 Fixed 9.0.0 1193 21 Jul 2003 Fixed 8.0.3 4730 21 Jul 2003 Fixed 8.0.2 4291 21 Jul 2003 Fixed Description The server could have crashed when sampling trie-based indexes. For this to have occurred, there must have been no entries in the index being sampled, while there were rows in the underlying table. This could only have occurred if another transaction had concurrently deleted the last row in the table, while the sampling was in progress. This has now been fixed.

CR:326172

CR Number:   326172 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1598 23 Jul 2003 Fixed 9.0.0 1190 23 Jul 2003 Fixed 8.0.3 4727 23 Jul 2003 Fixed 8.0.2 4290 23 Jul 2003 Fixed Description When connected to a MobiLink server, and displaying the chart in By User view, synchronizations could have been shown in the wrong rows when new rows were added (unless they happened to be added in alphabetical order). A workaround to fix the chart is to change to By Worker Thread then back to By User. This problem has been fixed.

CR:326176

CR Number:   326176 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.1 1600 21 Jul 2003 Fixed 9.0.0 1190 21 Jul 2003 Fixed Description If a batch statement was prepared and then executed more than once, the server could have crashed if a checkpoint occurred between executions of the batch. This has been fixed.

CR:326219

CR Number:   326219 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1598 23 Jul 2003 Fixed 9.0.0 1109 23 Jul 2003 Fixed 8.0.3 4727 23 Jul 2003 Fixed 8.0.2 4290 23 Jul 2003 Fixed 8.0.1 3123 23 Jul 2003 Fixed Description Some pages that were allocated then freed by the database server, may not have been reused after the next checkpoint. This problem could have resulted in the server growing the database file unnecessarily, as the file would have been grown to create new free pages rather than using existing free pages within the database file. However, all of the free pages would have been recognized and reused if the server was shut down and restarted (until the first checkpoint occurred afterwards). This problem only affected databases created with 8.0.0 or later and which had a page size of at least 2K. It has now been fixed.

CR:326227

CR Number:   326227 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.1 1598 21 Jul 2003 Fixed 9.0.0 1190 21 Jul 2003 Fixed 8.0.3 4727 21 Jul 2003 Fixed Description The AsaClient dynamically loads the dbdatax.dll at runtime. The LoadLibrary call was failing on Windows ME. This is now fixed.

CR:326236

CR Number:   326236 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) 9.0.2 2302 07 May 2004 Fixed Description The data in one or more tables can now be unloaded from within Sybase Central, without stepping through the Unload Database wizard. By selecting the desired tables in the right pane, and then choosing the File -> Unload Data... menu item, an Unload Data dialog will be displayed. This dialog allows specifying the same relevant options as available in the Unload Database wizard, but with all the options on a single page for quicker access.

CR:326320

CR Number:   326320 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.1 1623 15 Aug 2003 Fixed 9.0.0 1204 15 Aug 2003 Fixed 8.0.3 4748 15 Aug 2003 Fixed 8.0.2 4300 15 Aug 2003 Fixed Description When a NULL constant is converted to a NUMERIC, a precision and scale of (1,0) is now used instead of the default set by the options Precision and Scale. This is particularly important for UNION queries such as the following: select unit_price from product union all select NULL from dummy Previously, the data type of the result would have been desribed as a NUMERIC(30,6) (with default precision and scale settings). Now, it is described as NUMERIC(15,2), the data type of the unit_price column. Explicit conversions to NUMERIC will use (1,0), if the conversion does not provide a precision and scale. For example: SELECT cast( NULL as numeric ) A, cast( NULL as numeric(15,2) ) B will be described as: A NUMERIC(1,0) B NUMERIC(15,2) Now, the behaviour of NULL constants is more consistent with that of other constants, where the precision and scale is selected to be as small as possible. Workaround Description  Change the database defaults to be large enough

CR:326342

CR Number:   326342 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1601 23 Jul 2003 Fixed 9.0.0 1193 23 Jul 2003 Fixed 8.0.3 4730 23 Jul 2003 Fixed 8.0.2 4292 23 Jul 2003 Fixed Description If a batch or procedure returned multiple result sets and one of the result sets generated a warning, then the JDBC driver would have failed to return the remainder of the result sets. This problem has now been fixed.

CR:326369

CR Number:   326369 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.1 1601 25 Jul 2003 Fixed 9.0.0 1193 25 Jul 2003 Fixed Description Starting the server on Windows 95 would have resulted in the server crashing, if Winsock 2 was not installed. This has been fixed so that the server no longer crashes, but in order to use TCP/IP, SPX or HTTP/HTTPS on Windows 95, Winsock 2 must be installed.

CR:326377

CR Number:   326377 Product Name:   SQL Remote for SQL Anywhere Product Component:   Vim Messaging for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1684 04 Nov 2003 Fixed 9.0.0 1235 04 Nov 2003 Fixed 8.0.3 4830 04 Nov 2003 Fixed 8.0.2 4340 04 Nov 2003 Fixed Description When accessed via the VIM message link, messages were not always deleted from a ccMail mailbox after being processed. Messages are now deleted after being processed.

CR:326388

CR Number:   326388 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.1 1628 03 Sep 2003 Fixed 9.0.0 1208 03 Sep 2003 Fixed 8.0.3 4761 03 Sep 2003 Fixed 8.0.2 4305 03 Sep 2003 Fixed 8.0.1 3129 03 Sep 2003 Fixed 7.0.4 3484 03 Sep 2003 Fixed Description If the command delimiter option was set to something other than the default, and the delimiter appeared in a quoted filename, the filename would have been truncated. Quoted filenames are used in the following statements: INPUT, OUTPUT, READ, START DATABASE, START LOGGING, and STOP DATABASE. This has been fixed. The workaround for this problem is to not change the command delimiter option.

CR:326406

CR Number:   326406 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.1 3128 14 Aug 2003 Fixed 8.0.2 4303 14 Aug 2003 Fixed 8.0.3 4754 14 Aug 2003 Fixed 9.0.0 1205 14 Aug 2003 Fixed 9.0.1 1129 14 Aug 2003 Fixed Description Rebuilding a 5.x database, using either dbunload or Sybase Central, could have failed with a syntax error, if the option Non_keywords was set. This has been fixed. Workaround Description  to set the Non_Keywords option to blank before starting unload the db using Sybase Central JAva Edition - ASA 8.02

CR:326454

CR Number:   326454 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2250 17 Mar 2004 Fixed 9.0.1 1835 17 Mar 2004 Fixed Description Creating a proxy table that referenced an ASE remote server, using server class aseodbc, would have failed if the remote table name contained a '$' character. If the server class was asejdbc, then creating the proxy table would have succeeded, but the proxy table would have been unusable. Both problems have now been fixed.

CR:326460

CR Number:   326460 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.1 1603 24 Jul 2003 Fixed 9.0.0 1195 24 Jul 2003 Fixed 8.0.3 4732 24 Jul 2003 Fixed 8.0.2 4293 24 Jul 2003 Fixed 8.0.1 3125 25 Jul 2003 Fixed Description When using ODBC and fetching multi-byte characters from a UTF8 database, a truncation error could have occurred, even though the correct target buffer length and type were set in SQLBindCol. The ODBC driver used the length of the user's buffer as the length of its own internal buffer. Since one UTF8 character can occupy 1, 2, 3, 4 or more bytes, a larger internal buffer is required. This has been fixed.

CR:326462

CR Number:   326462 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1602 22 Jul 2003 Fixed 9.0.0 1194 22 Jul 2003 Fixed 8.0.3 4731 22 Jul 2003 Fixed 8.0.2 4293 22 Jul 2003 Fixed 8.0.1 3125 22 Jul 2003 Fixed Description SQLGetDescField and SQLColAttribute were returning SQL_FALSE for the SQL_DESC_UNSIGNED attribute for non-numeric types such as SQL_CHAR, implying that these were signed types. The ODBC standard states that: "This read-only SQLSMALLINT record field is set to SQL_TRUE if the column type is unsigned or non-numeric, or SQL_FALSE if the column type is signed." Also, SQL_TINYINT was treated as signed when ASA does not support a signed tinyint. This has been corrected. The following types are now considered signed. SQL_C_NUMERIC or SQL_NUMERIC SQL_DECIMAL SQL_C_FLOAT or SQL_REAL SQL_C_DOUBLE or SQL_DOUBLE SQL_BIGINT SQL_C_SBIGINT SQL_C_LONG or SQL_INTEGER SQL_C_SLONG SQL_C_SHORT or SQL_SMALLINT SQL_C_SSHORT The rest are unsigned types including SQL_C_TINYINT or SQL_TINYINT and SQL_C_STINYINT since ASA does not support a signed tinyint.

CR:326505

CR Number:   326505 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1644 30 Sep 2003 Fixed 9.0.0 1218 30 Sep 2003 Fixed 8.0.3 4790 30 Sep 2003 Fixed 8.0.2 4321 30 Sep 2003 Fixed 8.0.1 3132 30 Sep 2003 Fixed 7.0.4 3494 30 Sep 2003 Fixed Description A client application could have crashed when preparing and executing an oledb command object to open a rowset. This is now fixed.

CR:326614

CR Number:   326614 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.1 1603 23 Jul 2003 Fixed Description The embedded SQl call db_start_engine, was returning a non-zero value and setting the SQLCODE to SQLE_ENGINE_ALREADY_RUNNING (-96) if a server was already running. The SQLCODE is now set to 0 since this is a successful condition. The call db_start_database was returning 0 and setting the SQLCODE to SQLE_ALIAS_CLASH (-77) if the database was already running. Non-zero is now returned and the SQLCODE is now set to 0 since this also is a successful condition.

CR:326616

CR Number:   326616 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.1 1603 23 Jul 2003 Fixed 9.0.0 1195 23 Jul 2003 Fixed 8.0.3 4732 23 Jul 2003 Fixed 8.0.2 4293 23 Jul 2003 Fixed 8.0.1 3125 23 Jul 2003 Fixed Description Executing an unsupported statements when connected to the utility_db could have reduced the cache memory available. Executing many unsupported statements could have caused performance degradation or even caused the server to run out of memory. When connected to the utility_db database, statements such as CREATE DATABASE, START DATABASE, etc are supported. Unsupported statements give the error "Permission denied: you do not have permission to execute a statement of this type" (-121). This has been fixed so that available cache memory is not reduced by unsupported utility_db statements.

CR:326619

CR Number:   326619 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1648 30 Sep 2003 Fixed 9.0.0 1220 30 Sep 2003 Fixed 8.0.3 4794 30 Sep 2003 Fixed 8.0.2 4323 30 Sep 2003 Fixed 8.0.1 3133 30 Sep 2003 Fixed 7.0.4 3495 30 Sep 2003 Fixed Description An application using the ASA provider was not able to get DBPROPSET_DATASOURCEINFO when using DataLinks. This problem has been fixed.

CR:326656

CR Number:   326656 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.1 1603 24 Jul 2003 Fixed 9.0.0 1109 24 Jul 2003 Deferred Description If ASA was installed in a directory which contained non-ASCII characters, the Unicode translation library, (a component of ASA), would not have been able to locate its data files. Certain character set translations would also not have been available and other problems could also have arisen.

CR:326658

CR Number:   326658 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.1 1602 24 Jul 2003 Fixed 9.0.0 1109 24 Jul 2003 Fixed Description When using the Debugger in Sybase Central, switching from debug mode to design mode could have caused it to appear to hang. It was the server that was actually hung, which also prevented any new connections from being established. This is now fixed.

CR:326720

CR Number:   326720 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.1 3125 24 Jul 2003 Fixed 8.0.2 4294 24 Jul 2003 Fixed 8.0.3 4733 24 Jul 2003 Fixed 9.0.0 1196 24 Jul 2003 Fixed 9.0.1 1604 24 Jul 2003 Fixed Description Calling the system procedure xp_startsmtp, with smtp_sender=null, could have resulted in the server crashing. This has been fixed.

CR:326733

CR Number:   326733 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.1 1604 25 Jul 2003 Fixed 9.0.0 1109 25 Jul 2003 Fixed 8.0.3 4733 25 Jul 2003 Fixed 8.0.2 4294 25 Jul 2003 Fixed Description The functions xp_startmail, xp_startsmtp, xp_sendmail, xp_cmdshell, xp_read_file, and xp_write_file would have failed on Windows CE if character set conversion was required between the database character set and the OS character set. This has now been fixed.

CR:326745

CR Number:   326745 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.1 1604 25 Jul 2003 Fixed 9.0.0 1196 25 Jul 2003 Fixed 8.0.3 4733 25 Jul 2003 Fixed 8.0.2 4294 25 Jul 2003 Fixed Description If a stored procedure, which opened a cursor on another stored procedure call, was called many, many times, by an application usin jConnect or Open Client, the result set for the second stored procedure may have been described to the client even though no data would ever have been returned for that result set. This problem has now been fixed.

CR:326758

CR Number:   326758 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.1 1604 29 Jul 2003 Fixed 9.0.0 1196 29 Jul 2003 Fixed 8.0.3 4733 29 Jul 2003 Fixed 8.0.2 4294 29 Jul 2003 Fixed Description If an ADO application attempted to fetch and display columns that contained unsigned, tinyint, or bigint (64 bit) values, an error could have occurred or an incorrect value could have been displayed. These included the following types and sample values: tinyint 255 bigint 9223372036854775807 unsigned bigint 18446744073709551615 unsigned int 4294967295 unsigned smallint 65535 A tinyint type was treated as a signed value when it is not. A bigint type was treated as a 32-bit value when it is not. An unsigned bigint type was treated as a signed, 32-bit value when it is not. An unsigned int type was treated as a signed value when it is not. An unsigned smallint type was treated as a signed value when it is not. These datatypes are now handled correctly.

CR:326785

CR Number:   326785 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.1 1628 09 Sep 2003 Fixed Description The BACKUP DATABASE statement would have overwritten existing files when performing image backups. A new clause, ON EXISTING ERROR, has now been added to the statement. An error will now be given if any of the files to be created by the backup already exist. This new clause applies only to image backups. The syntax for image backups is now: BACKUPDATABASE DIRECTORYbackup-directory [WAITBEFORESTART] [WAITAFTEREND] [DBFILEONLY] [TRANSACTIONLOGONLY] [TRANSACTIONLOGRENAME[MATCH]] [TRANSACTIONLOGTRUNCATE] [ ON EXISTING ERROR ] If the -s command line option for DBBACKUP is used to cause a BACKUP DATABASE statement to be executed, the ON EXISTING ERROR clause will be included by default. If the -y option is specified for DBBACKUP, this clause is not added. When -y is not specified, any attempt to overwrite an existing file will cause an error to be returned. No prompting to replace files will be done when -s is specified.

CR:326799

CR Number:   326799 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.1 1605 29 Jul 2003 Fixed 9.0.0 1109 29 Jul 2003 Fixed 8.0.3 4734 29 Jul 2003 Fixed 8.0.2 4294 29 Jul 2003 Fixed 8.0.1 3125 29 Jul 2003 Fixed Description The MobiLink server may have generated an ODBC error, "function sequence error", when uploading a table with blob columns. This would only have occurred if: - the table had a nullable column before the blob column - an index column followed the blob column - the data for the column before the blob column was NULL This has been fixed, but a workaround is to make sure there are no index columns following any blob columns.

CR:326962

CR Number:   326962 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1608 31 Jul 2003 Fixed 9.0.0 1108 31 Jul 2003 Fixed 8.0.3 4737 31 Jul 2003 Fixed 8.0.2 4295 31 Jul 2003 Fixed Description Connecting to the utility database using the iAnywhere JDBC Driver, when running in a Japanese environment, and then attempting to execute a CREATE DATABASE command with Japanese characters in the database name, would have failed with an error that the database '??' could not be created. A similar error would have occurred when using Sybase Central connnected via the iAnywhere JDBC Driver. This problem has now been corrected.

CR:326980

CR Number:   326980 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.1 1608 01 Aug 2003 Fixed 9.0.0 1198 01 Aug 2003 Fixed 8.0.3 4737 01 Aug 2003 Fixed 8.0.2 4295 01 Aug 2003 Fixed Description Now, when the server detects a deadlock situation, if there is a transaction with a blocking_timeout specified, the one with the earliest deadline will be chosen as the victim to be cancelled.

CR:327019

CR Number:   327019 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.1 1610 01 Aug 2003 Fixed 9.0.0 1199 01 Aug 2003 Fixed 8.0.3 4739 01 Aug 2003 Fixed 8.0.2 4296 01 Aug 2003 Fixed 8.0.1 3126 01 Aug 2003 Fixed 7.0.4 3478 01 Aug 2003 Fixed Description When an application using the OLEDB driver was connected to a database with the Turkish collation, (1254TRK), some calls to get metadata would have failed. This problem has now been fixed.

CR:327068

CR Number:   327068 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) 18 May 2005 DEFER Description

CR:327081

CR Number:   327081 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.1 1610 05 Aug 2003 Fixed 9.0.0 1199 05 Aug 2003 Fixed 8.0.3 4739 05 Aug 2003 Fixed 8.0.2 4296 05 Aug 2003 Fixed 8.0.1 3126 05 Aug 2003 Fixed 7.0.4 3478 05 Aug 2003 Fixed Description The error 'Count field incorrect' could have occurred when executing an UPDATE statement command and setting a binary column to the value of a variable. This is nowfixed.

CR:327184

CR Number:   327184 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.1 3127 06 Aug 2003 Fixed Description A 'Fatal Error: (some error message)' could have been generated sporadically by the server when a database was started in read-only mode. This has been fixed. Workaround Description  None.

CR:327225

CR Number:   327225 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   HP-UX Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4756 21 Aug 2003 Fixed 8.0.2 4303 30 Jul 2003 Fixed 7.0.4 3478 21 Aug 2003 Fixed Description A query containing a UNION with a very large number of branches would have caused an assertion failure: "101505 - Memory allocation size too large". Now, the server no longer asserts, but instead the statement fails with an error indicating that a syntactic limit has been reached.

CR:327231

CR Number:   327231 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.1 1609 01 Aug 2003 Fixed 9.0.0 1198 01 Aug 2003 Fixed Description After entering a query and moving to the second screen of the Index Consultant, the shortcuts Alt+m, Alt+p did not switch between the two radio buttons as expected. As well, on the third screen, when selecting the Plan Viewer, Esc did not cause it to exit. These problems have now been fixed.

CR:327291

CR Number:   327291 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.1 1611 05 Aug 2003 Fixed 9.0.0 1109 05 Aug 2003 Fixed Description Calling a stored procedure that called another stored procedure, with the following conditions: - the called procedure was called in a FROM clause - the called procedure used a WITH clause to specify the schema - the calling procedure was called more than once with no intervening event that would have caused the procedure definition to be unloaded would have caused a server crash. This has been fixed.

CR:327298

CR Number:   327298 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.1 1611 05 Aug 2003 Fixed 9.0.0 1199 05 Aug 2003 Fixed 8.0.3 4740 05 Aug 2003 Fixed 8.0.2 4297 05 Aug 2003 Fixed Description A VersionNotFoundException would have been thrown when updating a deleted row with the DataAdapter without first setting the DataRowVersion property of DeleteCommand's parameters to 'Original'. This problem is now fixed.

CR:327304

CR Number:   327304 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.1 1611 05 Aug 2003 Fixed 9.0.0 1109 05 Aug 2003 Fixed 8.0.3 4740 05 Aug 2003 Fixed 8.0.2 4299 05 Aug 2003 Fixed 8.0.1 3127 05 Aug 2003 Fixed 7.0.4 3479 05 Aug 2003 Fixed Description If a user's password was changed to something containing a semi-colon (';'), connecting as that user was no longer possible, except from a another connection by a user with dba authority and not specifying a password. This has been fixed - the GRANT statement will now fail if the password contains a semi-colon.

CR:327306

CR Number:   327306 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.1 1611 07 Aug 2003 Fixed 9.0.0 1199 07 Aug 2003 Fixed 8.0.3 4740 07 Aug 2003 Fixed 8.0.2 4297 07 Aug 2003 Fixed Description A NullReferenceException would have occurred when calling ExecuteScalar if the command did not return a resultset. This problem has been fixed.

CR:327312

CR Number:   327312 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.1 1611 07 Aug 2003 Fixed 9.0.0 1199 07 Aug 2003 Fixed 8.0.3 4740 07 Aug 2003 Fixed 8.0.2 4297 07 Aug 2003 Fixed Description When using the AsaDataAdapter to fill a DataTable that included a varbinary column with a value of empty string, an ArgumentNullException was thrown. The AsaClient was failing to convert the binary column to a byte array for empty strings. This has been fixed by returning a zero-length byte array for empty binary values.

CR:327432

CR Number:   327432 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.1 1618 12 Aug 2003 Fixed 9.0.0 1202 12 Aug 2003 Fixed 8.0.3 4745 12 Aug 2003 Fixed 8.0.2 4300 12 Aug 2003 Fixed Description For very complex WHERE clauses in disjunctive form, new IN predicates are now generated that can be used as sargable predicates. For an IN predicate of the form "T.X IN ( constant_1, constant_2, ...)" to be generated, it is necessary to have in each term of the disjunction a predicate of the form "T.X = constant_i". In the example below, query Q1 is now transformed into query Q2, where two new sargable IN predicates are generated. Example: Q1: select * from T where (T.X = c1 and T.Y = c2) or (T.X =c3 and T.Y = c4) or (T.X = c5 and T.Y = c6) or (T.X =c7 and T.Y = c8) or (T.X = c9 and T.Y = c10) or (T.X =c11 and T.Y = c12) Q2: select * from T where T.X IN ( c1, c3, c5, c7, c9, c11) and T.Y IN (c2, c4, c6, c8, c10, c12) and T.X IN ( (c1, c2), (c3, c4), (c5, c6), (c7,c8), (c9,c10), (c11,c12) )

CR:327567

CR Number:   327567 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1648 30 Sep 2003 Fixed 9.0.0 1220 30 Sep 2003 Fixed 8.0.3 4794 30 Sep 2003 Fixed 8.0.2 4323 30 Sep 2003 Fixed Description When calling AsaDataAdapter.Fill( DataTable ), a NullReferenceException would have been thrown if MissingSchemaAction was AddWithKey and the table already had a primary key. This has been fixed.