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

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

CR:327642

CR Number:   327642 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 1622 12 Aug 2003 Fixed 9.0.0 1204 12 Aug 2003 Fixed 8.0.3 4751 12 Aug 2003 Fixed 8.0.2 4301 12 Aug 2003 Fixed 8.0.1 3128 12 Aug 2003 Fixed Description User functions that had a procedure id (proc_id in SYSPROCEDURE) that was greater that 32k would have always returned NULL. This has been fixed, these functions now return the correct return value. Workaround Description  No workaround

CR:327668

CR Number:   327668 Product Name:   UltraLite Product Component:   Native UltraLite for Java Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4745 08 Aug 2003 Fixed 8.0.2 4299 08 Aug 2003 Fixed Description Attempting to delete all rows matching a certain criteria, assuming there was an appropriate index, may have missed some rows or deleted the wrong rows. For example: t.findBegin(); <specify search criteria using t.set*(...)> t.findFirst(); t.delete(); while( t.findNext() ) { t.delete(); } would have skipped some rows because delete() modified the search criteria. If there were an odd number of rows matching the search criteria, this approach would have deleted rows that did not match the search criteria. Table.delete(), Table.truncate(), and Table.deleteAllRows() have now been changed so as to cancel all edit and search modes.

CR:327704

CR Number:   327704 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 1617 12 Aug 2003 Fixed 9.0.0 1202 12 Aug 2003 Fixed 8.0.3 4746 12 Aug 2003 Fixed 8.0.2 4299 12 Aug 2003 Fixed 8.0.1 3127 12 Aug 2003 Fixed Description A connection over namedpipes, which used a communication buffer size greater than the default 1460 bytes, could have failed with a communication error, if a request or response was larger than the default packet size. The communication buffer size is specified with the -p server option or the CommBufferSize (CBSIZE) connection parameter. This has now been fixed so that communication errors no longer occur.

CR:327708

CR Number:   327708 Product Name:   UltraLite Product Component:   UltraLite for eMbedded Visual Basic Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4745 11 Aug 2003 Fixed 8.0.2 4299 11 Aug 2003 Fixed Description Attempting to delete all rows matching a certain criteria, assuming there was an appropriate index, may have missed some rows or deleted the wrong rows. For example: t.findBegin(); <specify search criteria using t.set*(...)> t.findFirst(); t.delete(); while( t.findNext() ) { t.delete(); } would have skipped some rows because delete() modified the search criteria. If there were an odd number of rows matching the search criteria, this approach would have deleted rows that did not match the search criteria. Table.delete(), Table.truncate(), and Table.deleteAllRows() have now been changed so as to cancel all edit and search modes.

CR:327728

CR Number:   327728 Product Name:   UltraLite Product Component:   UltraLite for AppForge MobileVB Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4745 11 Aug 2003 Fixed 8.0.2 4299 11 Aug 2003 Fixed Description Attempting to delete all rows matching a certain criteria, assuming there was an appropriate index, may have missed some rows or deleted the wrong rows. For example: t.findBegin(); <specify search criteria using t.set*(...)> t.findFirst(); t.delete(); while( t.findNext() ) { t.delete(); } would have skipped some rows because delete() modified the search criteria. If there were an odd number of rows matching the search criteria, this approach would have deleted rows that did not match the search criteria. Table.delete(), Table.truncate(), and Table.deleteAllRows() have now been changed so as to cancel all edit and search modes.

CR:327823

CR Number:   327823 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1617 11 Aug 2003 Fixed 9.0.0 1202 11 Aug 2003 Fixed 8.0.3 4746 11 Aug 2003 Fixed 8.0.2 4299 11 Aug 2003 Fixed 8.0.1 3127 11 Aug 2003 Fixed Description It was possible for an autoincrement (or global autoincrement) default on a numeric column to overflow and cause other values in the row to have been corrupted. This hasnow been fixed.

CR:327840

CR Number:   327840 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 1624 19 Aug 2003 Fixed 9.0.0 1205 19 Aug 2003 Fixed 8.0.3 4753 19 Aug 2003 Fixed 8.0.2 4302 19 Aug 2003 Fixed Description When updating data with a data adapter, DBConcurrency was not thrown if an attempt to execute a DELETE, INSERT or UPDATE statement resulted in no rows being affected. This problem has now been fixed.

CR:327932

CR Number:   327932 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 22 Aug 2003 Fixed 9.0.0 1206 22 Aug 2003 Fixed 8.0.3 4757 22 Aug 2003 Fixed 8.0.2 4304 22 Aug 2003 Fixed 8.0.1 3128 22 Aug 2003 Fixed Description ASA Windows applications including the server, dbremote, dbmlsync and dbmlsrv would fail to find quoted UNC style filenames specified on the command line. For example, passing the database file as "\\server\share\dir\my.db" would have failed with the error "Could not open/read database file: \server\share\dir\my.db" Attempting to use connection strings such as "...;dbf=\\server\share\dir\my.db;..." would have succeeded only if the server myengine was already running (even if the database my.db wasn't running), but would have failed if myengine was not running, due to this problem. This has been fixed so that quoted command line arguments of the form "\\server\share\etc" no longer removes the first back slash. Note that running a database from a file server can corrupt the database and is generally not recommended.

CR:327943

CR Number:   327943 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.1 1622 08 Aug 2003 Fixed 9.0.0 1204 12 Aug 2003 Fixed 8.0.3 4751 12 Aug 2003 Fixed 8.0.2 4301 12 Aug 2003 Fixed Description Before the Conjunctive Normal Form (CNF) algorithm is applied to a WHERE clause, disjunctions of the form "X = 10 OR X = 20 OR X IN (40, 50)" are now transformed into IN lists (i.e., X IN (10, 20, 40, 50)). Also, disjunctions of the form "X = 10 OR X = 20 OR X=30" are also transformed into IN lists (i.e., X IN (10, 20, 30)). These transformations reduce the number of predicates in a WHERE clause, hence some of the rewrite optimizations (such as CNF) that are done for WHERE clauses, may not have been done prior to this change, and the query may now perform much better.

CR:328051

CR Number:   328051 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 4752 15 Aug 2003 Fixed 8.0.2 4302 15 Aug 2003 Fixed Description Complex SELECT INTO statements executed inside a stored procedure may have failed after the first call to the procedure. This has now been fixed, Work arounds are: (1) rewrite SELECT .. INTO statement as an EXECUTE IMMEDIATE statement (2) rewrite SELECT .. INTO statement as an INSERT statement (the table inserted into must be created first in this case)

CR:328084

CR Number:   328084 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4748 12 Aug 2003 Fixed 8.0.2 4300 12 Aug 2003 Fixed Description Predicates referring to undeclared host variables and string columns, were not considered sargable. Hence, the predicates wouldn't have been used for an index scan if an appropriate index existed. For example: create table T (c varchar(100) NOT NULL, b int NOT NULL, PRIMARY KEY (c, b) ); select ulplan( 'SELECT * from T WHERE T.c = ? and T.b = ? '); The plan for the above query wouldn't contained an index scan, when in fact the primary key index would have been appropriate to be used here. This is now fixed.

CR:328174

CR Number:   328174 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 1622 14 Aug 2003 Fixed 9.0.0 1204 14 Aug 2003 Fixed Description After entering a query, the shortcuts on the third screen of the Index Consultant, Ctrl+PageUp and Ctrl+PageDown were not wrking correctly. They did not switch tabs as expected. This is now fixed.

CR:328178

CR Number:   328178 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1622 18 Aug 2003 Fixed 9.0.0 1111 18 Aug 2003 Fixed Description If the dbdsn utility was run with -w command-line option to write out the data source definition, and the DSN already existed, the user was prompted as to whether or not to overwrite the existing DSN. However, the DSN would have been overwritten regardless of the user's response. This has now been fixed.

CR:328180

CR Number:   328180 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) 8.0.3 4751 14 Aug 2003 Fixed 8.0.2 4301 14 Aug 2003 Fixed 8.0.1 3128 14 Aug 2003 Fixed Description Some of the download scripts take an optional timestamp parameter (last_download_timestamp). This timestamp can be modified by creating a modify_last_download_timestamp script which is called before the download scripts. The unmodified timestamp was being passed to the connection scripts, now the modified timestamp is used. Table scripts were not affected.

CR:328181

CR Number:   328181 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 1622 20 Aug 2003 Fixed 9.0.0 1204 20 Aug 2003 Fixed Description When running the Index Consultant from Sybase Central, the 'Review a saved analysis' radio button on the third dialog could have been selected, even when the corresponding list was empty. Now this radio button is not selectable if the list is empty.

CR:328222

CR Number:   328222 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 1622 19 Aug 2003 Fixed 9.0.0 1204 19 Aug 2003 Fixed Description When displaying the current log file settings in the Change Log File Settings wizard, the initial focus was being set to the Back button, so that hitting Enter would have moved to the previous page. Now, the initial focus is set to the Next button, so that hitting Enter moves to the next page.

CR:328353

CR Number:   328353 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 1111 18 Aug 2003 Fixed 9.0.0 1204 18 Aug 2003 Fixed 8.0.3 4752 18 Aug 2003 Fixed 8.0.2 4302 18 Aug 2003 Fixed Description If a Monitor session had enough users to cause a vertical scrollbar to be shown in the chart in the 'By User' view, then the overview outline would not have been the correct height when the view was changed to 'By Sync'. This has now beed corrected.

CR:328354

CR Number:   328354 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 1625 20 Aug 2003 Fixed 9.0.0 1205 20 Aug 2003 Fixed 8.0.3 4754 20 Aug 2003 Fixed 8.0.2 4303 20 Aug 2003 Fixed 7.0.4 3484 20 Aug 2003 Fixed Description Prior to this fix, if the server added an index entry to an upgraded version 4 database, the index could have become corrupted. For this corruption to occur, the value being inserted must not have been fully hashed (i.e. was longer than ~9 bytes). The symptom of the corruption was that querying the index for entries with a particular value returned an incorrect (usually fewer) number of rows. Range searches would have produced the expected number of rows. While the server has been fixed and the database will no longer be corrupted, Validate Table/Index will not catch any existing corruption. A work around would be to unload/reload to a later format database.

CR:328376

CR Number:   328376 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1625 18 Aug 2003 Fixed 9.0.0 1205 18 Aug 2003 Fixed 8.0.3 4754 18 Aug 2003 Fixed 8.0.2 4303 18 Aug 2003 Fixed 8.0.1 3128 18 Aug 2003 Fixed Description DBISQL could have reported an internal error if there was more than one DBISQL window open, and one of the windows was closed by clicking its close icon in the title bar, while DBISQL was executing a statement, but was blocked. This is now fixed.

CR:328387

CR Number:   328387 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 1623 18 Aug 2003 Fixed 9.0.0 1204 18 Aug 2003 Fixed 8.0.3 4752 18 Aug 2003 Fixed 8.0.2 4302 18 Aug 2003 Fixed Description A query with a WHERE clause containing duplicate IN lists may have returned incorrect results if the following conditions were true: (1) the duplicate IN list must have been on a base or view column (e.g., T.X IN (2,3)) (2) the duplicate IN list must have appeared in a disjunct with another IN list on the same column (e.g., "(T.X IN (4, 5) OR T.X IN (2,3))" ) (3) the WHERE clause was in Conjuctive Normal Form This is now fixed.

CR:328444

CR Number:   328444 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 1625 20 Aug 2003 Fixed 9.0.0 1205 20 Aug 2003 Fixed 8.0.3 4754 20 Aug 2003 Fixed 8.0.2 4303 20 Aug 2003 Fixed Description Queries that contained an outer reference from a subquery to a grouped query block would have failed with the error "Function or column reference to 'x' must also appear in a GROUP BY". This was not a requirement if the subquery appeared inside an argument to an aggregate function as in the following: select manager_id, max( (select emp_id from employee where salary=e.salary) ) from employee e group by manager_id This has now been fixed.

CR:328462

CR Number:   328462 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 1628 19 Aug 2003 Fixed 9.0.0 1205 19 Aug 2003 Fixed Description Running version 9.0.0 of the MobiLink server, on a consolidated database that had not been upgraded to version 9.0, would have shown the error "Column 'last_download_time' not found". Now, the MobiLink server will verify that all the expected tables and their columns exist and if they don't, an error will be displayed message and the MobiLink server shutdown. The only workaround is to run the upgrade script for the appropriate consolidated database.

CR:328466

CR Number:   328466 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 1628 19 Aug 2003 Fixed 9.0.0 1205 19 Aug 2003 Fixed 8.0.3 4753 19 Aug 2003 Fixed 8.0.2 4302 19 Aug 2003 Fixed Description When attempting to save data to an mlm file, if there was insufficient disk space, an error message would have been displayed, and a zero lemgth file would have been created. If an existing file was being overwritten, the existing file would be replaced by a zero length file. Now, if there is insufficient space to write an mlm file, the error message is displayed and nothing is written to disk.

CR:328482

CR Number:   328482 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) 7.0.4 3484 22 Aug 2003 Fixed Description If a table had a self-referencing foreign key and a LOAD TABLE operation on the table failed, the server would have failed with assertion 104002. This has been fixed

CR:328661

CR Number:   328661 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 1616 21 Aug 2003 Fixed 9.0.0 1201 21 Aug 2003 Fixed Description The query details pane of the Index Consultant displays virtual indexes recommended for each query. The user can view details about these indexes by clicking the appropriate button. If there were multiple virtual indexes with similar column signatures recommended on a single table, the details for the wrong index would sometimes have been displayed. This has been fixed.

CR:328664

CR Number:   328664 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 1628 21 Aug 2003 Fixed 9.0.0 1209 21 Aug 2003 Fixed Description The Index consultant would have used inconsistent index ids in displayed plans. When viewing plans with virtual indexes, the index names (which include a numeric identifier) would not have matched the identifiers assigned in the generated script. This has been fixed.

CR:328669

CR Number:   328669 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 1625 20 Aug 2003 Fixed 9.0.0 1205 20 Aug 2003 Fixed 8.0.3 4754 20 Aug 2003 Fixed 8.0.2 4303 20 Aug 2003 Fixed Description The Serializable attribute was not supported for AsaException, AsaError and AsaErrorCollection. The Serializable attribute has now been added.

CR:328678

CR Number:   328678 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 1625 21 Aug 2003 Fixed 9.0.0 1205 21 Aug 2003 Fixed Description Executing a SELECT INTO statement that used a procedure call in the FROM clause and specified the schema of the procedure call using a WITH clause, would have crashed the server. This has been fixed.

CR:328695

CR Number:   328695 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 2231 25 Feb 2004 Fixed 9.0.1 1826 25 Feb 2004 Fixed 9.0.0 1278 25 Feb 2004 Fixed 8.0.3 4931 25 Feb 2004 Fixed 8.0.2 4385 25 Feb 2004 Fixed 8.0.1 3152 25 Feb 2004 Fixed Description For ADO applications using client-side cursors, when adding a record to a table containing a char or varchar column, using an ADO recordset, the value in the ADO recordset was padded with blank spaces up to the maximum length of the column. This padding behavior occurred as soon as the assignment took place (well before the new record was transmitted to the database). This has been fixed. Previously, the DBCOLUMNFLAGS field of the DBCOLUMNINFO structure for char and varchar columns included DBCOLUMNFLAGS_ISFIXEDLENGTH. This was incorrect. This flag is no longer set for char and varchar columns.

CR:328699

CR Number:   328699 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 1626 21 Aug 2003 Fixed 9.0.0 1205 21 Aug 2003 Fixed Description Attempting to use a connection string with curly braces: driver=Adaptive Server Anywhere ...;links=tcpip{port=...;host=...} would have succeeded, but attempting to use a connection string with round braces: driver=Adaptive Server Anywhere ...;links=tcpip(port=...;host=...) would have failed. The problem has now been corrected

CR:328702

CR Number:   328702 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 1625 21 Aug 2003 Fixed 9.0.0 1205 21 Aug 2003 Fixed Description The Create, Unload and Extract Database wizards allowed choosing the MDSR encryption algorithm when creating a database on any version 8 or later server. However, this would result in the error "Database creation failed: MDSR is not available" unless the server was a version 8 Windows server. Now, the MDSR option can only be chosen in the wizards if the server is a version 8 Windows server.

CR:328847

CR Number:   328847 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 4762 08 Sep 2003 Fixed 9.0.0 1208 08 Sep 2003 Fixed 8.0.3 4672 08 Sep 2003 Deferred 8.0.2 4306 08 Sep 2003 Fixed 8.0.1 3129 08 Sep 2003 Fixed Description If an application fetched character columns using the OLEDB driver and the length of the data was more than 200 bytes, then the data returned could have been truncated. This problem has been fixed.

CR:328881

CR Number:   328881 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.1 1628 22 Aug 2003 Fixed 9.0.0 1207 22 Aug 2003 Fixed 8.0.3 4758 22 Aug 2003 Fixed 8.0.2 4304 22 Aug 2003 Fixed 8.0.1 3128 22 Aug 2003 Fixed 7.0.4 3484 22 Aug 2003 Fixed Description If a DTC transaction was unenlisted while another DTC action was running, the server may have crashed. This would have been seen if an application ran concurrent DTC actions from multiple threads against the same connection. This problem has been fixed.

CR:328939

CR Number:   328939 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 1628 04 Sep 2003 Fixed 9.0.0 1111 04 Sep 2003 Fixed 8.0.3 4764 04 Sep 2003 Fixed 8.0.2 4307 04 Sep 2003 Fixed Description An incorrect input parameter length or value could have been passed when calling a remote procedure on an ODBC class remote server. This problem could also have caused a server crash in rare situations. It is now fixed.

CR:328946

CR Number:   328946 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 1625 21 Aug 2003 Fixed 9.0.0 1205 21 Aug 2003 Fixed Description If an ASA database contained MobiLink Client setup data, upgrading to 9.0.0 would have failed with the following message . Error in file upgrad60.sql at line 3134 with sqlcode -116 SQL error (-116) -- Table must be empty Upgrade failed The upgrade fails on attempting to add a NOT NULL column with a default value to a non-empty table in a single alter table statement. The fix was to make the column NOT NULL later using a second alter statement. A work around is to synchronize all publications, delete all subscriptions and synchronization users, upgrade to 9.0.0 and then recreate the users and subscriptions.

CR:328956

CR Number:   328956 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1625 18 Aug 2003 Fixed 9.0.0 1205 18 Aug 2003 Fixed 8.0.2 4303 18 Aug 2003 Fixed 8.0.1 3128 18 Aug 2003 Fixed 7.0.4 3484 18 Aug 2003 Fixed 8.0.3 4754 21 Aug 2003 Fixed Description If the minimum log_sent value in the SYSREMOTEUSER table pointed to the middle of an operation in the transaction log, then dbremote would still have sent data starting at the beginning of the transaction pointed to by the bad offset. Now, dbremote will return an error (No log operation at offset X) in this situation.

CR:328984

CR Number:   328984 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1625 21 Aug 2003 Fixed 9.0.0 1205 21 Aug 2003 Fixed 8.0.3 4754 21 Aug 2003 Fixed 8.0.2 4303 21 Aug 2003 Fixed Description When entering dates on the "Data" tab of a database table, all dates were assumed to be in "YMD" order, even if the "Date_order" option was set differently. Now, the setting of "Date_order" is respected.

CR:329001

CR Number:   329001 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1625 19 Aug 2003 Fixed 9.0.0 1111 19 Aug 2003 Fixed 8.0.3 4754 19 Aug 2003 Fixed 8.0.2 4303 19 Aug 2003 Fixed 7.0.4 3484 19 Aug 2003 Fixed Description An embedded SQL application may have crashed with SIGBUS on 64-bit UNIX platforms or received the error "SQL ERROR (-758) SQLDA data type invalid". The SQL preprocessor was generating the sqldabc field in the SQLDA structure incorrectly for 64-bit platforms. This has now been fixed. Workaround: use the flag -DLONG_IS_64BITS when compiling 64-bit embedded SQL application.

CR:329009

CR Number:   329009 Product Name:   MobiLink Product Component:   Sample Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1625 21 Aug 2003 Fixed 9.0.0 1205 21 Aug 2003 Fixed Description If ASA shared software was installed on a path containing space, step2 of the SIS_CarDealer example would have failed to start the Beeper java application. This problem is now fixed.

CR:329090

CR Number:   329090 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) 8.0.2 4304 22 Aug 2003 Fixed 9.0.0 1207 22 Aug 2003 Fixed 9.0.1 1628 22 Aug 2003 Fixed 8.0.3 4758 22 Aug 2003 Fixed Description If a user attempted to insert a long binary value into a proxy table using a host variable, there was a chance the server would have crashed. This problem has been fixed.

CR:329124

CR Number:   329124 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 21 Aug 2003 Fixed 9.0.0 1206 21 Aug 2003 Fixed 8.0.3 4757 21 Aug 2003 Fixed 8.0.2 4304 21 Aug 2003 Fixed Description Inserting a long binary constant into a proxy table, would have caused the inserted value to have been corrupted. This problem has now been fixed.

CR:329234

CR Number:   329234 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 1626 22 Aug 2003 Fixed 9.0.0 1205 22 Aug 2003 Fixed Description When issuing virtual index manipulation statements and specifying a table creator, the creator was being ignored for the CREATE and DROP statements. For example, the following two statements are legal and should create two separate virtual indexes: CREATE VIRTUAL INDEX testidx ON USER1.tab1(col1) CREATE VIRTUAL INDEX testidx ON USER2.tab1(col1) However, they were incorrectly both resolving to the same table and hence the second statement failed with an error that the index already exists. This has now been fixed.

CR:329267

CR Number:   329267 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1643 30 Sep 2003 Fixed 9.0.0 1218 30 Sep 2003 Fixed 8.0.3 4789 30 Sep 2003 Fixed 8.0.2 4319 30 Sep 2003 Fixed Description AsaDataAdapter Update method would have fail if the UpdateCommand was generated by AsaCommandBuilder and the query was upper case. The GetSchema method compared strings case-sensetively and failed to identify the key columns. This has now been fixed by changing the string comparison to case-insensitive when setting the key columns and unique columns in GetSchema method.

CR:329294

CR Number:   329294 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.1 1628 22 Aug 2003 Fixed 9.0.0 1207 22 Aug 2003 Fixed 8.0.3 4758 22 Aug 2003 Fixed 8.0.2 4304 22 Aug 2003 Fixed Description When converting a NULL constant to a string type (ie CHAR, VARCHAR, LONG VARCHAR, BINARY, VARBINARY, LONG BINARY), the size would be initialized to 32767 if no length was provided. Now, the size is initialized to 0. For example, the following queries would have returned a column described as length 32767: SELECT CAST( NULL AS CHAR ) --> now CHAR(0) SELECT 'abc' UNION ALL SELECT NULL --> now CHAR(3) SELECT '' UNION ALL SELECT NULL --> now CHAR(0) SELECT IF 1=1 THEN 'abc' ELSE NULL ENDIF --> now CHAR(3)

CR:329322

CR Number:   329322 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 1627 22 Aug 2003 Fixed 9.0.0 1206 22 Aug 2003 Fixed Description When deleting a table with an index, a trigger, or a foreign key with update and/or delete actions, the Indexes, Triggers and System Triggers folders would not be updated accordingly. In addition, when creating or deleting a foreign key, the System Triggers folder would not be updated. Now, these folders are refreshed automatically when these operations occur.

CR:329326

CR Number:   329326 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1627 22 Aug 2003 Fixed 9.0.0 1206 22 Aug 2003 Fixed Description SyncProgressDialog would not return control to the calling form once synchronization completed. This has been fixed. The CustDB sample (SyncProgressDialog was disabled in the 9.0.0ga version of CustDB) has also been updated.

CR:329327

CR Number:   329327 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1628 21 Aug 2003 Fixed 9.0.0 1206 21 Aug 2003 Fixed 8.0.3 4757 21 Aug 2003 Fixed 8.0.2 4304 21 Aug 2003 Fixed 8.0.1 3128 21 Aug 2003 Fixed 7.0.4 3484 21 Aug 2003 Fixed Description If a server running on a Unix platform, was started as a daemon (i.e. with -ud), then making remote ODBC connections would have failed with error -656. This problem has been fixed.

CR:329337

CR Number:   329337 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 1625 22 Aug 2003 Fixed 9.0.0 1205 22 Aug 2003 Fixed Description If the contents of the Utilities tab page was sorted by clicking on the Name or Description column heading, there was no way to return to the default ordering (other than editing or deleting the .scUserPreferences42 file). Now, the contents of the tab page always retain the default ordering, with the exception that the order may be reversed; that is, the utilities are always sorted by similar functionality.

CR:329432

CR Number:   329432 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1624 21 Aug 2003 Fixed 9.0.0 1207 02 Sep 2003 Fixed Description A query containing a UNION with a large number of branches would have caused an assertion failure: "101505 - Memory allocation size too large". Previously, at most: N = (page_size - 112) / 8 union branches were permitted with 32-bit engines, and at most: N = (page_size - 112) / 16 were allowed with 64-bit engines. For 2K pages and 32-bit engine, this was about 242 branches of a union. This assertion failure no longer occurs for unions with a large number of branches.

CR:329434

CR Number:   329434 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 1628 21 Aug 2003 Fixed 9.0.0 1206 21 Aug 2003 Fixed Description When creating a new object using a wizard, or duplicating an object using the clipboard, if the owner of the new object could have been specified, then the PUBLIC group was included in the owner list. However, choosing PUBLIC as the owner for the new object would always have resulted in a permission error. Now, PUBLIC is always excluded from the list of owners.

CR:329517

CR Number:   329517 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 1628 22 Aug 2003 Fixed 9.0.0 1206 22 Aug 2003 Fixed Description Shrinking or growing the cache could have caused the server to crash or stop with an assertion failure, or for the database to become corrupt. If a cursor was sitting on a page that was removed from the cache, the server would have crashed the next time the page was referenced. If the cache was to have grown before the cursor was referenced again, the cursor would have been referencing the wrong page. Cache shrinking could also have resulted in server crashes, if the cache page size was greater than 4k. This has now been fixed. A work around would be to disable cache resizing.

CR:329521

CR Number:   329521 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 1628 22 Aug 2003 Fixed 9.0.0 1207 22 Aug 2003 Fixed 8.0.3 4758 22 Aug 2003 Fixed 8.0.2 4304 22 Aug 2003 Fixed 8.0.1 3128 22 Aug 2003 Fixed 7.0.4 3484 16 Oct 2003 Fixed Description Attempting to insert a NULL value into a NUMERIC or DECIMAL column with "default autoincrement" could have led to a server crash. The NULL value must have been cast to NUMERIC. The following statement would have caused the crash: INSERT INTO T( x ) SELECT CAST( NULL AS NUMERIC ) For other column types, there was a possibility that the value returned from @@identity would be incorrect after inserting a NULL value. The correct value should be 0. This problem is now fixed.

CR:329528

CR Number:   329528 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 1628 22 Aug 2003 Fixed 9.0.0 1207 22 Aug 2003 Fixed 8.0.3 4758 22 Aug 2003 Fixed 8.0.2 4304 22 Aug 2003 Fixed 8.0.1 3128 22 Aug 2003 Fixed Description Joins on more than one attribute, executed with merge join, would have incorrectly returned rows where a join attribute was NULL in both tables, provided that it was not the first attribute containing NULL. Rows with NULL join attributes will now be rejected as NULL = NULL is Unknown, not True.

CR:329570

CR Number:   329570 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) 8.0.3 4778 10 Sep 2003 Fixed 8.0.2 4313 11 Sep 2003 Fixed 7.0.4 3490 11 Sep 2003 Fixed Description If a database's collation was 1254TRK , built-in functions could not be referenced if the function name was in upper case. This has been fixed.

CR:329604

CR Number:   329604 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 1628 02 Sep 2003 Fixed 9.0.0 1207 02 Sep 2003 Fixed Description The new feature 'SELECT TOP <integer1> START AT <integer2>' could have caused the server to crash if integer2 was 0 and integer1 was <= 1024, and an ORDER BY clause was specified for the query that was not satisfied by an index. The START AT clause does not accept 0 as a valid value, and should have given an error message. After this change, the following error message is given: INVALID_CURSOR_RANGE 09W07 -674L "statement's size limit is invalid."

CR:329736

CR Number:   329736 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 1628 02 Sep 2003 Fixed 9.0.0 1208 02 Sep 2003 Fixed Description A keyset-driven cursor (ESQL scroll) could have caused the server to crash if the query contained a derived table with a TOP n or ORDER BY clause. For example: select R.x, R.y, DT.y dty from R, ( select top 20 y from T order by 1 ) dt This crash has now been fixed.

CR:329774

CR Number:   329774 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 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 Description The First, Last, Next, and Previous menu items were enabled, but had no effect if the table was disabled. They are now disabled if the table is disabled.

CR:329788

CR Number:   329788 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 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 Description The MIN/MAX optimization (documented in "ASA SQL User's Guide/Optimization for minimum or maximum functions") was not being applied for queries containing predicates with host variables (in Ultralite), or database variables (if plan caching was used). For example, a query of the form: SELECT min( R.y ) FROM R WHERE R.x = ? should be converted to: SELECT MIN( R.y) FROM ( SELECT FIRST R.y FROM R WHERE R.x = ? and R.y IS NOT NULL ORDER BY R.x ASC, R.y ASC ) as R(y) (assuming that an index exists on R(x,y) ). Further, a query in a stored procedure that used SQL variables (CREATE VARIABLE or DECLARE) or procedure/function parameters, would not have allowed the optimization when a query was optimized for plan caching. A symptom of this is that a stored procedure would execute more slowly after a few initial iterations, and a query in the procedure met the conditions for this optimization. A work-around would be to set MAX_PLANS_CACHED=0 to prevent plan caching. Both these problems have now been fixed.

CR:329901

CR Number:   329901 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 1628 02 Sep 2003 Fixed 9.0.0 1208 02 Sep 2003 Fixed 8.0.3 4762 02 Sep 2003 Fixed 8.0.2 4306 02 Sep 2003 Fixed Description As of 8.0.2, pipelined versions of hash and sort operators were introduced. This allowed the materialization of result rows from the operator to be deferred instead of occuring immediately in the operator. For UNION based queries, some branches of the union may require materialization while others do not. Previously, all rows were materialized in a work table. Now, a work table will be placed at the top of each branch that requires materialization, unless all branches require materialization. This reduces the overhead of unnecessarily materialized rows.

CR:329903

CR Number:   329903 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 1666 21 Oct 2003 Fixed 9.0.0 1228 21 Oct 2003 Fixed 8.0.3 4812 21 Oct 2003 Fixed 8.0.2 4331 21 Oct 2003 Fixed Description A query with a large WHERE clause, containing a large number of conjunctive and disjunctive predicates of literals, could have caused the server to hang with 100% cpu usage and eventually run out of memory. This has been fixed.

CR:329924

CR Number:   329924 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.1 1628 26 Aug 2003 Fixed 9.0.0 1111 26 Aug 2003 Fixed 8.0.2 4306 26 Aug 2003 Fixed 8.0.3 4762 26 Aug 2003 Fixed Description When a second file or session was opened, the chart pane would have remained scrolled at the same position it was at for the first file or session. Similarly, when the Monitor was started, the chart pane did have a scrollbar, but when a session was closed, the scrollbar remained visible. Now, when a second session is opened the chart pane is scrolled to the beginning, and when a session is closed, the scrollbar disappears.

CR:329994

CR Number:   329994 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   5.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1655 05 Nov 2003 Fixed Description The optimizer was not estimating the selectivity of predicates that involved special values such as CURRENT TIMESTAMP. Now, the selectivity of these predicates is estimated using the values of the expression at optimization time. This may lead to slightly inaccurate estimates if the query is executed a significant period after optimization, but is still likely to yield a better estimate than the guessed selectivity.

CR:330075

CR Number:   330075 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.1 1628 03 Sep 2003 Fixed 9.0.0 1209 03 Sep 2003 Fixed 8.0.3 4763 03 Sep 2003 Fixed 8.0.2 4306 03 Sep 2003 Fixed 8.0.1 3129 03 Sep 2003 Fixed Description A multi-threaded client application, which had multiple connections concurrently using the same debug logfile (using the LogFile connection parameter) on multiple connections, could have been missing debug messages, or possibly have crashed. Problems were more likely on a multiprocessor machine. This has been fixed.

CR:330127

CR Number:   330127 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3484 29 Aug 2003 Fixed 8.0.2 4307 29 Aug 2003 Fixed 8.0.3 4764 29 Aug 2003 Fixed 9.0.0 1209 29 Aug 2003 Fixed 9.0.1 1628 29 Aug 2003 Fixed Description If a TDS (jConnect or Open Client) application made a request which returned a large amount of data (several Kb or more), and then sent a cancel request, the server could have gone to 100% CPU usage, attempting to send the cancel response. While the server was attempting to send the cancel response, checkpoints or DDL would have caused all connections to hang. Fetching a large result set with older versions of jConnect, could hang after running out of memory and sending a cancel request, causing the engine to hang indefinitely. (Current JConnect EBFs may get an java.lang.ArrayIndexOutOfBoundsException instead of hanging.) Now the server will no longer go to 100% CPU usage or cause all connections to hang when processing a TDS cancel. If the server is unable to send the TDS cancel response for 60 seconds, it will drop the connection.

CR:330140

CR Number:   330140 Product Name:   SQL Anywhere Product Component:   JDBC 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 1729 24 Dec 2003 Fixed 9.0.0 1255 24 Dec 2003 Fixed 8.0.3 4874 24 Dec 2003 Fixed 8.0.2 4359 24 Dec 2003 Fixed Description Entering a table name in the Import Wizard, qualified by owner name, Would have caused an exception reporting that the table did not exist, even if it did or if the wizard was to create the table. This has been fixed.

CR:330234

CR Number:   330234 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4307 29 Aug 2003 Fixed 8.0.3 4764 29 Aug 2003 Fixed 9.0.0 1209 29 Aug 2003 Fixed 9.0.1 1628 29 Aug 2003 Fixed Description The TIMESTAMP_FORMAT used when one connection queried another connection's last request time (i.e. connection_property('LastReqTime',some_other_conn_id)) would have been the other connection's format, not the current connection. This has been fixed. This change also fixes the case where the server could have crashed if a connection queried another connection's last request time at the instant that the other connection was being created.

CR:330282

CR Number:   330282 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 1666 28 Oct 2003 Fixed 9.0.0 1228 28 Oct 2003 Fixed 8.0.3 4812 28 Oct 2003 Fixed 8.0.2 4332 28 Oct 2003 Fixed Description Whether the server cached and reused an access plan for a query embedded in a stored procedure or function, was based on any variance of the estimated execution cost of the access plans generated in two ways: - plans generated during the so-called "training period", when the values of any variables are evaluated prior to optimization (and can be considered known constants), and - a plan generated without knowledge of the values of those variables, hence representing a "generic" plan. Unfortunately, estimated costs from the optimizer alone were insufficient criteria with which to base this decision. Now, strict plan equivalence is necessary prior to marking a plan as reuseable for subsequent invocations of the procedure. As a workaround, users may turn plan caching off entirely by setting the option MAX_PLANS_CACHED to 0.

CR:330286

CR Number:   330286 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.0 1209 29 Aug 2003 Fixed 9.0.1 1628 29 Aug 2003 Fixed Description The File Open/Save dialog was not consistently setting its initial directory to the directory that was used last. Now, the initial directory is set correctly. Note: The file ".isqlSettings9" should be deleted after applying this fix (this is the file in which the initial file dialog directories are saved). The location of this file varies, depending on the operating system used.

CR:330380

CR Number:   330380 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 1111 29 Aug 2003 Fixed 9.0.1 1628 29 Aug 2003 Fixed Description Sending an HTTP header broken into two lines would have resulted in a 400 Bad Request error. Multi-line headers are now supported.

CR:330407

CR Number:   330407 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) 9.0.1 1648 16 Oct 2003 Fixed 9.0.0 1220 16 Oct 2003 Fixed 8.0.3 4794 16 Oct 2003 Fixed 8.0.2 4323 16 Oct 2003 Fixed Description It was possible for the server to crash if two or more connections were dropping and reloading procedures concurrently. This has now been fixed. Workaround Description  None.

CR:330437

CR Number:   330437 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 1628 05 Sep 2003 Fixed 9.0.0 1111 05 Sep 2003 Fixed Description The DriveType database property has now been added for servers running on the various Unix platforms, (previously it was only available on Windows). This property gives information about the drive on which the database file is located. Possible values include: "CD", "FIXED", "RAMDISK", "REMOTE", "REMOVABLE", and "UNKNOWN". Note, unlike Windows, this type of drive information may not be readily available on some Unix versions Therefore, depending on the flavour of Unix and the type of drive, it may not be possible to determine the drive type and "UNKNOWN" will be returned.

CR:330440

CR Number:   330440 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 1624 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 Description Under certain circumstances, dbisqlc could have crashed when run on HP-UX on Itanium. For example: if the ESC key was pressed while in the Connection dialog box. This has been fixed.

CR:330441

CR Number:   330441 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic 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 1210 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 The -zt command line option for dbmlsrv was mistakenly shown in the usage displayed on Unix platforms. This switch is only available on Windows and now is only shown when usage is displayed when running on Windows.

CR:330481

CR Number:   330481 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 1628 04 Sep 2003 Fixed 9.0.0 1211 04 Sep 2003 Fixed 8.0.3 4767 04 Sep 2003 Fixed 8.0.2 4308 04 Sep 2003 Fixed Description For a query where IN-list merging took place, followed by CNF to DNF conversion, the result of the conversion may have been incorrect. This could only have happened if a literal altered by the IN-list merging appeared in more than one conjunct. For example, in the following, the predicate N1.N_NAME = 'GERMANY' appears in two conjuncts and the second appearance is changed to N1.N_NAME IN ('GERMANY', 'FRANCE') by IN-list merging. (N1.N_NAME = 'GERMANY' or N2.N_NAME = 'GERMANY') and (N1.N_NAME = 'FRANCE' or N2.N_NAME = 'FRANCE') and (N1.N_NAME = 'GERMANY' or N1.N_NAME = 'FRANCE') and (N2.N_NAME = 'FRANCE' or N2.N_NAME = 'GERMANY') This has been fixed. Note that this is the same problem that was partially fixed for 328387.

CR:330623

CR Number:   330623 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1628 05 Sep 2003 Fixed 9.0.0 1211 05 Sep 2003 Fixed Description The HTTPS synchronization stream defaulted to port 80 when connecting to a MobiLink server via a proxy server. It now correctly defaults to port 443.

CR:330648

CR Number:   330648 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1628 05 Sep 2003 Fixed 9.0.0 1211 05 Sep 2003 Fixed 8.0.3 4769 05 Sep 2003 Fixed 8.0.2 4309 05 Sep 2003 Fixed Description Sybase Central could have crashed when unloading a database directly into a new database if an error occurred while reloading the data. The dbunload utility with the -an parameter would have reported an error at the point that Sybase Central crashed. This has been fixed so that Sybase Central now reports the error and no longer crashes.

CR:330991

CR Number:   330991 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 1628 08 Sep 2003 Fixed 9.0.0 1212 08 Sep 2003 Fixed Description Running 7.x versions of UltraLite-based clients against 9.x MobiLink server would have failed with the server reporting that the download failed with error -85. This has been fixed.

CR:331020

CR Number:   331020 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 1112 08 Sep 2003 Fixed 9.0.0 1212 08 Sep 2003 Fixed Description If a client application made more than one TLS connection, some memory would have been leaked for each connection after the first. This has been fixed.

CR:331112

CR Number:   331112 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.1 1628 08 Sep 2003 Fixed 9.0.0 1214 08 Sep 2003 Fixed 8.0.3 4776 08 Sep 2003 Fixed 8.0.2 4310 08 Sep 2003 Fixed Description Forgetting to specify the sync stream type would have resulted in a null dereferencing when synchronizing. This has now been fixed.

CR:331147

CR Number:   331147 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 1631 12 Sep 2003 Fixed 9.0.0 1215 12 Sep 2003 Fixed 8.0.3 4778 12 Sep 2003 Fixed 8.0.2 4313 12 Sep 2003 Fixed 8.0.1 3131 12 Sep 2003 Fixed 7.0.4 3490 12 Sep 2003 Fixed Description If a table had a computed column with an expression that referenced a user defined function, and had a foreign key defined, then an unload/reload operation would have failed. The failure would have occurred during the reload phase, creating the foreign key. This was due to the values of the computed column being recalculated during the creation of the foreign key, but at this stage of the reload, the user defined function had not yet been defined. This has been fixed by not recalculating computer column values when creating foreign keys.

CR:331278

CR Number:   331278 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 1628 09 Sep 2003 Fixed 9.0.0 1214 09 Sep 2003 Fixed Description The cost of querying an xml column using the Openxml() function, in a lateral derived table, would have exhibited nonlinear slowdown as the size of the table increased. This would have become quite noticeable starting at a few thousand documents. The problem has been fixed.

CR:331323

CR Number:   331323 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.1 1628 09 Sep 2003 Fixed Description A foreign key's settings for Check on commit, Allow nulls, as well as its Update and Delete actions, are now modifiable from the property sheet. Note that in order to change these settings, the Foreign Key is actually dropped and re-created with the new settings.

CR:331328

CR Number:   331328 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 1628 09 Sep 2003 Fixed 9.0.0 1214 09 Sep 2003 Fixed 8.0.3 4775 09 Sep 2003 Fixed 8.0.2 4312 09 Sep 2003 Fixed Description If a stored procedure contained a statement like ALTER TABLE t1 RENAME t2 the statement would fail the second time the procedure was called, with the error: Table 't2' not found This has been fixed. A workaround is to execute the statement using EXECUTE IMMEDIATE.

CR:331392

CR Number:   331392 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.1 1629 10 Sep 2003 Fixed Description The Remote Server wizard has been extended to allow for the creation of an external login to the remote server for the current user. This support has been added to allow an immediately connection to a remote server created from within the Migrate Database wizard, even when an external login is required.

CR:331462

CR Number:   331462 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) 7.0.4 3489 09 Sep 2003 Fixed Description Attempting to insert a long string in a multi-byte character set into a proxy table, could have resulted in the data being corrupted. This problem has been fixed.

CR:331508

CR Number:   331508 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 1629 10 Sep 2003 Fixed 9.0.0 1214 10 Sep 2003 Fixed Description Attempting to access a remote server from a local server running on a 64-bit platform, where the local database had a page size of 1024, would have caused the server to fail with assertion 101508 "Reference to heap memory is not in first page of heap". This problem has been fixed.

CR:331547

CR Number:   331547 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 1629 10 Sep 2003 Fixed 9.0.0 1214 10 Sep 2003 Fixed 8.0.3 4776 10 Sep 2003 Fixed 8.0.2 4312 10 Sep 2003 Fixed Description The connection-dropped callback function was not being called for TCPIP or SPX connections. This has been fixed.

CR:331554

CR Number:   331554 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.1 1629 11 Sep 2003 Fixed Description After changing one or more column widths in the Table Editor, the new column width settings would be lost and the original settings restored, when you saved or reverted the changes to the table or selected another item in the left pane. Now, the column widths are retained in the .scUserPreferences42 file, in the same way that column widths are retained for other items.

CR:331652

CR Number:   331652 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1630 10 Sep 2003 Fixed 9.0.0 1215 10 Sep 2003 Fixed 8.0.3 4777 10 Sep 2003 Fixed 8.0.2 4312 10 Sep 2003 Fixed 8.0.1 3131 10 Sep 2003 Fixed 7.0.4 3505 26 Nov 2003 Fixed Description Output and variant type parameters were not supported by the OLEDB driver. The following C++ example contains both variant type parameters and output parameters. class CInP1OutP2Accessor { public: CComVariant m_varP1; CComVariant m_varP2; BEGIN_PARAM_MAP(CInP1OutP2Accessor) // SET_PARAM_TYPE( DBPARAMIO_INPUT ) // Default COLUMN_ENTRY_TYPE(1, DBTYPE_VARIANT, m_varP1) SET_PARAM_TYPE( DBPARAMIO_OUTPUT ) COLUMN_ENTRY_TYPE(2, DBTYPE_VARIANT, m_varP2) END_PARAM_MAP() }; When variant type parameters were used, the OLEDB driver would have failed with an assertion error. The OLEDB driver would not have returned the proper value for an output parameter. These problems have now been fixed.

CR:331657

CR Number:   331657 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 1630 10 Sep 2003 Fixed Description An application connected via TDS (ie using jConnect, and using Dynamic Prepared Statements, may have crashed when the statement was deleted. This problem has been fixed.

CR:331682

CR Number:   331682 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4778 12 Sep 2003 Fixed 8.0.2 4313 12 Sep 2003 Fixed Description The MobiLink server would have shutdown immediately, after succesfully starting up, if it used the tcpip, http or https communications link and no HOST parameter was specified (which defaults to localhost), and localhost could not be resolved. This has been corrected. Workaround Description  Use one of two workarounds: - define "localhost" in /etc/hosts (usually defined to "127.0.0.1" - specify the HOST parameter: dbmlsrv8 -x tcpip{HOST=servername} ...

CR:331789

CR Number:   331789 Product Name:   SQL Anywhere Product Component:   DBLIB 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 1632 16 Sep 2003 Fixed 9.0.0 1217 16 Sep 2003 Fixed 8.0.3 4779 16 Sep 2003 Fixed 8.0.2 4313 16 Sep 2003 Fixed 8.0.1 3131 16 Sep 2003 Fixed 7.0.4 3490 16 Sep 2003 Fixed Description After a multi-threaded windows application called db_fini, SQLFreeEnv, etc to finalize the client database interface (dblib, ODBC, etc), there could have been unfreed thread handles remaining. This has been fixed so that all thread handles created by the client database interface are now freed. Note the client database interface library will only free all resources after it has been finalized the same number of times it has been initialized.

CR:331826

CR Number:   331826 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1631 16 Sep 2003 Fixed 9.0.0 1215 16 Sep 2003 Fixed 8.0.3 4778 16 Sep 2003 Fixed 8.0.2 4313 16 Sep 2003 Fixed 8.0.1 3131 16 Sep 2003 Fixed 7.0.4 3490 16 Sep 2003 Fixed Description Attempting to execute an INPUT statement with a "FORMAT SQL" clause, without having previously executed a statement which returned a result set, would have caused dbisql to have reported an internal error. This has been fixed to now report an error message. In a related problem, if an INPUT statement did not include a table name, and the file format was not "SQL", an error message should have been displayed but was not. Now, the error message is properly displayed.

CR:331845

CR Number:   331845 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 1632 17 Sep 2003 Fixed 9.0.0 1113 17 Sep 2003 Fixed Description If a server using Web Services was shut down, the server process may not have completely shut down, (on Win32 platforms the server icon would have been left displayed). When this happened, the database files would have been closed and the communications links shut down sufficiently to allow another server to start with the same name, and on the same files, so it could have appeared as if there were two servers running with the same name. This has been fixed.

CR:331994

CR Number:   331994 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Oct 2003 Not a Bug Description Attempting to start a server on RedHat Linux 9.0, could have caused the server to hang (or possibly crash), due to the new Native POSIX Thread Library (NPTL) included in RedHat 9.0. This library is incompatible with the threading model used in previous Linux versions. Setting the environment variable LD_ASSUME_KERNEL: export LD_ASSUME_KERNEL=2.4.1 can be used as a work around to resolve the hanging problem. Please see the RedHat 9.0 RELEASE-NOTES for further details. Servers from version 8.0.2 and above, do not experience this issue and therefore the setting of LD_ASSUME_KERNEL should not be necessary to run these servers on RedHat 9.0.

CR:332134

CR Number:   332134 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 1632 17 Sep 2003 Fixed 9.0.0 1216 17 Sep 2003 Fixed 8.0.3 4779 17 Sep 2003 Fixed 8.0.2 4313 17 Sep 2003 Fixed Description If the Compute clause for a column contained a subquery, with an unresolved reference to a column name that matched one of the columns in the table, then the server could have crashed while creating the computed value. For example: create table t (c1 int); alter table t add c2 int compute( (select c1+1) ) This problem has now been resolved.

CR:332139

CR Number:   332139 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1659 17 Sep 2003 Fixed 9.0.0 1225 17 Sep 2003 Fixed 8.0.3 4805 17 Sep 2003 Fixed 8.0.2 4328 17 Sep 2003 Fixed 8.0.1 3134 17 Sep 2003 Fixed 7.0.4 3498 17 Sep 2003 Fixed Description The INPUT statement would have failed to import any data if the FORMAT ASCII clause was specified, the input file did not contain values for all of the columns listed in the INPUT statement, and one of the omitted columns was of type BINARY, VARBINARY, or LONG BINARY. This has been fixed.

CR:332163

CR Number:   332163 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 1628 18 Sep 2003 Fixed 9.0.0 1213 18 Sep 2003 Fixed 8.0.3 4772 18 Sep 2003 Fixed 8.0.2 4310 18 Sep 2003 Fixed Description After a successful load of a large table, the server creates a histogram for each column in the table to represent the data distribution for the column values. The histogram is subsequently refined in response to queries executed by the server. Over time it was possible for the histogram quality to degrade, causing the server to incorrectly assume zero selectivity for some equality predicates. This problem has been corrected.

CR:332181

CR Number:   332181 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 1633 19 Sep 2003 Fixed 9.0.0 1217 19 Sep 2003 Fixed Description When doing a sequential scan of a large table, the server could have crashed. The crash occurred when attempting to free memory used for doing scatter reads at IO completion time. This has been fixed by deferring the free until the next scatter read or until the file is no longer in use.

CR:332213

CR Number:   332213 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1633 19 Sep 2003 Fixed 9.0.0 1217 19 Sep 2003 Fixed 8.0.3 4780 19 Sep 2003 Fixed 8.0.2 4314 19 Sep 2003 Fixed 8.0.1 3131 19 Sep 2003 Fixed Description The executeUpdate() method of the PreparedStatement clase would sometimes have returned the wrong update counter. The counter kept growing after each call to executeUpdate(), even though there was no actual rows updated. This is now fixed.