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

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

CR:297919

CR Number:   297919 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.0 469 09 Dec 2002 Fixed Description If the first argument of the ROUND() function was decimal, the result of the function had the same datatype, precision and scale as the first argument. If the second argument was negative, it was possible that the result would have had a larger precision that the first argument, and return an error. For example, the following should both return 1000.000: SELECT round(1232.955,-3) SELECT round(953.343,-3) The second returned an error since it required a larger precision. Now, the precision of the result is adjusted. A workaround is to cast the first argument to have a larger precision: select round( cast(953.343 as numeric(7,3)),-3) In normal usage, the first argument would be a column or variable with a sufficiently large precision.

CR:298000

CR Number:   298000 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.3 4510 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed 8.0.1 3128 21 Aug 2003 Fixed Description If a Java stored procedure executed a query which referenced a proxy table, rows could have been omitted from the result set. A common appearance of the problem would have exhibited as missing every other row of a result from a proxy table. This is now fixed.

CR:298001

CR Number:   298001 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4576 05 Feb 2003 Fixed 8.0.2 4212 05 Feb 2003 Fixed 8.0.1 3099 05 Feb 2003 Fixed Description When calling a SQL procedure that declared an external java method which produced a result set, dbisql when using the JDBC-ODBC bridge would have reported an invalid cursor operation. This problem is now fixed. Workaround Description  The first thing to do is to include a description of the result set. I also modified the result_set() procedure to accept the table name as an argument and to pass this on to the Java routine. ALTER procedure DBA.result_set(in table_name char(20)) res

CR:298285

CR Number:   298285 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4506 23 Oct 2002 Fixed 8.0.2 4076 23 Oct 2002 Fixed 8.0.1 3062 23 Oct 2002 Fixed Description In rare circumstances, indexes could be corrupted by internal server cursors. Internal server cursors are used by the server during the execution of many types of statement, usually to access system tables. This is now fixed.

CR:298299

CR Number:   298299 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) 8.0.3 4505 21 Oct 2002 Fixed 8.0.2 4076 21 Oct 2002 Fixed Description Due to an off-by-one error in the logic which filtered system procedures out of the list of procedures received from the server, the "Lookup Procedure Name" dialog could have shown a single system procedure, depending on the order in which procedure names were returned from the server. The first item in the list was never subject to the filter. This is now fixed.

CR:298372

CR Number:   298372 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4534 02 Dec 2002 Fixed 8.0.2 4086 02 Dec 2002 Fixed 8.0.1 3080 02 Dec 2002 Fixed 8.0.0 2355 02 Dec 2002 Fixed 7.0.4 3393 02 Dec 2002 Fixed Description The server would have crashed on shutdown, when running on Windows CE .NET. This is now fixed.

CR:298374

CR Number:   298374 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4505 23 Oct 2002 Fixed 8.0.2 4076 23 Oct 2002 Fixed 8.0.1 3061 23 Oct 2002 Fixed Description The server provides concurrency control for reading and updating the column statistics so that any changes to the statistics can take place safely in the presence of multiple simultaneous requests accessing the same statistics. The concurrency control method used could have caused the server to slow down unacceptably at very high rates of access (in one test the problem was observed after the number of concurrent users exceeded approximately 1500). The server now uses an improved concurrency control method and the problem should no longer occur.

CR:298383

CR Number:   298383 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) 8.0.3 4506 23 Oct 2002 Fixed 8.0.2 4076 23 Oct 2002 Fixed 8.0.1 3062 23 Oct 2002 Fixed 8.0.0 2351 23 Oct 2002 Fixed 7.0.4 3382 23 Oct 2002 Fixed Description The Import Wizard could have reported an internal error if, on the second page, the "Use an existing table" radio button was selected and the name of a nonexistent table was entered, and then went on to the import the file. Now, users are not allowed to leave the second page if the table does not exist.

CR:298410

CR Number:   298410 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.3 4513 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed 8.0.1 3069 05 Nov 2002 Fixed Description The following changes have been made: Added: property( 'LicensesInUse' )- determines the numbers of "seats" or "concurrent users" currently connected to the network server. Each "seat" or "concurrent user" is determined by the number of unique client network addresses connected to the server, not the number of connections. For example, if three client machines are connected to a server, and each client machine has two connections, select property( 'LicensesInUse' ) is '3'. Corrected: property('ProcessCPU') - now correctly returns the total process time in seconds. It was incorrectly returning two times the property('ProcessCPUUser') on Windows platforms. Corrected: db_property('IdleCheck'),db_property('IdleChkpt') and statistics "Idle Actives/sec" and "Idle Checkpoints/sec" - now return correct values (before they always had values of 0)

CR:298423

CR Number:   298423 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) 8.0.3 4506 23 Oct 2002 Fixed 8.0.2 4076 23 Oct 2002 Fixed 8.0.1 3062 23 Oct 2002 Fixed 8.0.0 2351 23 Oct 2002 Fixed 7.0.4 3382 23 Oct 2002 Fixed Description The configured caret color used by the syntax highlighting editor in DBISQL was being ignored. This meant that the caret color would remain the system default caret color (the color you'd see used for the caret in Notepad, for example). Now the configured color is used.

CR:298511

CR Number:   298511 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) 8.0.3 4509 31 Oct 2002 Fixed 8.0.2 4076 31 Oct 2002 Fixed 8.0.1 3066 31 Oct 2002 Fixed Description Queries with views or derived tables in the null-supplying side of an outer join (left outer, right outer or full outer joins) may have returned an incorrect result set under these conditions: - there was a local predicate referencing only the view in the WHERE clause of the main query block and this predicate was not null-rejecting (for example, "View.column is null"). - the view or derived table could not have been flattened (e.g., it is a grouped view, or it contains an UNION) - the OUTER join could not have been transformed into an inner join Example: SELECT * FROM employee a LEFT OUTER JOIN ( SELECT * FROM employee UNION SELECT * FROM employee ) b ON (a.emp_id = b.emp_id) WHERE b.emp_id IS NULL This is now fixed.

CR:298526

CR Number:   298526 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4507 24 Oct 2002 Fixed 8.0.2 4076 24 Oct 2002 Fixed 8.0.1 3062 24 Oct 2002 Fixed Description When using the OLEDB driver to retrieve schema rowsets, the rowset properties were sometimes incorrect and could have (depending on the application) caused every second row to be missing. The properties which could be wrong were DBPROPSET_ROWSET, DBPROP_BOOKMARKS and DBPROP_IRowsetLocate and have been corrected.

CR:298559

CR Number:   298559 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 3597 22 Oct 2002 Fixed Description In MobiLink Monitor's New Watch (or Edit Watch) dialog, the table listing conditions did not make it clear what unit of time was being used. It would show seconds and milliseconds, always using a period for the decimal separator. This has been fixed. Times in the table are now displayed in ISO 8601 format.

CR:298595

CR Number:   298595 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 4510 31 Oct 2002 Fixed 8.0.2 4076 31 Oct 2002 Fixed 8.0.1 3066 31 Oct 2002 Fixed 8.0.0 2351 31 Oct 2002 Fixed Description The MobiLink server could have failed with an ODBC function sequence error when a zero length blob was inserted or a statement-based update was issued, with blobs that were NULL or zero length. This has now been fixed.

CR:298598

CR Number:   298598 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4567 13 Jan 2003 Fixed Description The data from the rs_lastcommit table was being unloaded from the database twice when dbunload was run. Besides being listed in the excludeobject table, as a table requiring its data to be unloaded, there was explicit code to unload the data from rs_lastcommit in dbtools. This code has been removed.

CR:298602

CR Number:   298602 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4507 23 Oct 2002 Fixed 8.0.2 4076 23 Oct 2002 Fixed 8.0.1 3062 23 Oct 2002 Fixed 7.0.4 3382 23 Oct 2002 Fixed Description Fetching the second row of a result set in an updateable cursor, where one of the columns had more than 200 bytes of data, would have resulted in an error. This has now been fixed.

CR:298604

CR Number:   298604 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) 8.0.3 4507 24 Oct 2002 Fixed 8.0.2 4076 24 Oct 2002 Fixed 8.0.1 3062 24 Oct 2002 Fixed 8.0.0 2382 24 Oct 2002 Fixed Description On Unix, with the option -v+, Mobilink could have output some wrong SQL statements in the log file when Mobilink logged native SQL statements. When doing the conversion between multibyte and Unicode characterss, a NULL termination character was missed. This is now fixed.

CR:298612

CR Number:   298612 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4507 23 Oct 2002 Fixed 8.0.2 4076 23 Oct 2002 Fixed 8.0.1 3062 23 Oct 2002 Fixed Description If a query contained a predicate that trivially evaluates to FALSE (e.g., c1 BETWEEN 5 and 10), the optimizer would have realized that the predicate would have caused the result set to be empty. However, in some cases (e.g., if a GroupByHash appeared in the plan above the filter), the server could still have caused memory to be allocated. Depending upon the estimated size of the result set without the predicate that evaluates to FALSE, enough memory could have been allocated that could result in the server running out of available memory. This problem has now been fixed.

CR:298807

CR Number:   298807 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) 8.0.3 4508 28 Oct 2002 Fixed 8.0.2 4076 28 Oct 2002 Fixed Description Providing connection information on dbisql's command line, (in either the argument to the "-c" option or in the SQLCONNECT environment variable), would have caused it to fail to connect if all of the following were true: 1. the "-odbc" option was used, and 2. connection was to the default local server, and 3. no data source was specified a in the connection parameters This is now fixed. . In this case, DBISQL would open the "Connect" dialog from which you could successfully log in.

CR:298849

CR Number:   298849 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) 8.0.3 4552 17 Jan 2003 Fixed 8.0.2 4095 17 Jan 2003 Fixed Description The server now allows one extra connection above the connection limit, to allow a user with dba privileges to connect and drop other connections, in case of an intentional or accidental denial-of-service attack. Note that "connection limit" here refers to either the hard-coded 10-connection limit of the personal server, or the value specified by the -gm switch, and has nothing to do with licensing.

CR:298851

CR Number:   298851 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 3599 28 Oct 2002 Fixed 8.0.1 3063 28 Oct 2002 Fixed 7.0.4 3382 28 Oct 2002 Fixed Description If primary keys for uploaded data contains string columns, dbmlsync running on CE may have produced an incorrect upload stream, if non-UTF8 characters were involved. This problem is now fixed.

CR:298858

CR Number:   298858 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 3599 28 Oct 2002 Fixed 8.0.1 3063 28 Oct 2002 Fixed 7.0.4 3382 28 Oct 2002 Fixed Description Dbmlsync may have crashed, due to a buffer overrun, if it encountered non-blob strings longer that 32759 bytes (the ASA limit is 32767). The problem is now fixed.

CR:298906

CR Number:   298906 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) 8.0.3 4545 10 Dec 2002 Fixed 8.0.2 4092 10 Dec 2002 Fixed 8.0.1 3084 10 Dec 2002 Fixed 8.0.0 2357 10 Dec 2002 Fixed Description Calling a Java in the Database object which created a zip file using 'java.util.zip.ZipOutputStream', with either JDK 1.1.8 or 1.3, would have reported a bad CRC error. This has now been fixed.

CR:298907

CR Number:   298907 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) 8.0.2 3599 28 Oct 2002 Fixed Description Selecting a plan view node with a large amount of detail HTML would not cause the right-hand detail viewer to update in an acceptable amount of time. This could be reproduced by getting the graphical plan for a simple query (select * from some_table), selecting any node, and then re-selecting the root (SELECT) node. Toggling between two nodes would eventually have caused the rendering delay to increase. This response time has been improved (although a delay is still noticeable) and the performance no longer degrades with repeated selections.

CR:298914

CR Number:   298914 Product Name:   UltraLite Product Component:   Code Generator Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4537 03 Dec 2002 Fixed 8.0.2 4087 03 Dec 2002 Fixed Description The UltraLite analyzer would have generated code for some queries that declared the same variable name twice. This has been fixed. Workaround Description  Manually delete the duplicate definitions after ulgen has generated the code.

CR:298948

CR Number:   298948 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) 8.0.2 3600 28 Oct 2002 Fixed 8.0.1 3064 28 Oct 2002 Fixed Description The server could have leaked memory when calling a trigger on a table that contained columns with check constraints. This is now fixed.

CR:298957

CR Number:   298957 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) 8.0.3 4508 28 Oct 2002 Fixed 8.0.2 4076 28 Oct 2002 Fixed 8.0.1 3065 31 Oct 2002 Fixed Description When a procedure which did not return a result set was opened in Embedded SQL using EXEC SQL OPEN, the procedure was executed and the SQLE_PROCEDURE_COMPLETE warning was returned. After receiving this warning, attempting to close the cursor gave a SQLE_CURSOR_NOT_OPEN error, and attempting to open a cursor with the same name gave a SQLE_CURSOR_ALREADY_OPEN error. Now the cursor is in the closed state if the open returns SQLE_PROCEDURE_COMPLETE, and opening a cursor with the same name will succeed.

CR:299030

CR Number:   299030 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 4078 12 Nov 2002 Fixed 8.0.1 3072 12 Nov 2002 Fixed 8.0.0 2353 12 Nov 2002 Fixed 7.0.4 3388 12 Nov 2002 Fixed Description After rebuilding an ASA primary database using dbunload -ar, running the Replication Agent would fail with the following error: Unable to find log offset ... Error processing log due to missing log(s) Dbunload did not save the current transaction log and reset the start and relative log offset in the rebuilt database. This has been fixed.

CR:299055

CR Number:   299055 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.1 3073 14 Nov 2002 Fixed 8.0.2 4080 14 Nov 2002 Fixed 8.0.3 4519 14 Nov 2002 Fixed 9.0.0 444 14 Nov 2002 Fixed Description You no longer need DBA authority to connect the Mobilink Server to an ASA database.

CR:299058

CR Number:   299058 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4509 31 Oct 2002 Fixed 8.0.2 4076 31 Oct 2002 Fixed 8.0.1 3065 31 Oct 2002 Fixed 7.0.4 3383 31 Oct 2002 Fixed Description Tilde (~) characters were not allowed in unquoted file names. Attempting to use them caused the error "Lexical error". This problem has been fixed.

CR:299060

CR Number:   299060 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 4509 04 Nov 2002 Fixed 8.0.2 4076 04 Nov 2002 Fixed Description ASA now supports slightly larger standard cache sizes by allowing the cache to be allocated in up to 4 contiguous pieces where only two were allowed previously. Some DLLs load at addresses which fragment the address space and limit the amount of memory that can be allocated with only two pieces. With this change, perhaps 100MB to 200MB of additional memory may be allocated for a standard cache, depending on the system. For AWE caches, this change means that more address space will now be available for mapping to physical memory which will reduce the number of mapping operations which must be performed. Also with this change, the minimum AWE cache size has changed from (3GB-256MB) to 2MB. It is recommended, however, that a traditional cache be used if a traditional cache of the desired size can be allocated. Recall that AWE caches do not support dynamic cache sizing and that AWE cache page images are locked in memory and therefore they cannot be swapped out if memory is needed by other processes in the system.

CR:299066

CR Number:   299066 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 05 Nov 2002 Fixed 9.0.0 1214 05 Nov 2002 Fixed 8.0.3 4777 05 Nov 2002 Fixed 8.0.2 4312 05 Nov 2002 Fixed 8.0.1 3069 05 Nov 2002 Fixed 7.0.4 3386 11 Sep 2003 Fixed Description If an UPDATE statement used an index on a column defined with DEFAULT TIMESTAMP, it could have looped infinitely. This is now fixed.

CR:299081

CR Number:   299081 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4510 31 Oct 2002 Fixed 8.0.2 4076 31 Oct 2002 Fixed 8.0.1 3064 31 Oct 2002 Fixed Description When using ASA as a consolidated database for MobiLink, if any of the tables to be synchronized were located on a remote server (ie proxy tables), the MobiLink server would have encountered the following error: "Feature 'remote savepoints' not implemented" and failed the synchronization. This case is now detected and silently worked around.

CR:299102

CR Number:   299102 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4520 15 Nov 2002 Fixed 8.0.2 4080 15 Nov 2002 Fixed 8.0.1 3074 15 Nov 2002 Fixed Description The table sys.dummy was previously implemented as a real table. As the single row was fetched from this table, the corresponding table page was temporarily latched while reading the column out (as is done for all base tables). Since the dummy table contains only one row, there was a strong possibility that multiple clients would be concurrently attempting to latch the same page. This could lead to reduced opportunities for parallelism, and in some cases could lead to the formation of convoys. These symptoms could be observed by noting that the CPU use on a multi-processor system dropped to about one processor, while many requests were active or unscheduled; at the same time, many of the active requests referenced the sys.dummy table. To address this issue, the sys.dummy table is now implemented in a manner that bypasses the latch on the table page. This is only possible because the dummy table has known contents which can not be modified. Further, the sys.dummy table no longer appears in Lock nodes in the graphical plan, and if only the sys.dummy table is present, a Lock node may now be omitted where it was previously required.

CR:299106

CR Number:   299106 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4508 15 Nov 2002 Fixed 8.0.2 4076 15 Nov 2002 Fixed 8.0.1 3064 15 Nov 2002 Fixed Description A point of contention existed which could have reduced concurrency on SMP machines, when using work tables (tables used for operations such as sort, group-by, and distinct). This situation could be recoqnized by observing CPU use on a mult-processor system at about 1 CPU, while the number of active requests was high, the HashContention property was high ('Contention: Hash Chains' performance counter), and many of the active requests were using work tables. The point of contention has been removed.

CR:299109

CR Number:   299109 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4028 18 Nov 2002 Fixed 8.0.2 4080 18 Nov 2002 Fixed 8.0.1 3054 18 Nov 2002 Fixed Description Search conditions of the form "col LIKE '<prefix>%' " can usually use an index (ie sargable), if the prefix does not contain any wild card characters. For these conditions, the engine infers range bounds of the form "col >= '<prefix>' AND col < '<prefix#>'", where <prefix#> indicates a version of the prefix string that has been incremented. For example, if the following appears in a query: emp_lname like 'SI%' then the optimizer will add additional predicates: emp_lname >= 'SI' AND emp_lname < 'SJ' Note that the last character, 'I', has been incremented to the next character in the collation; in this case, 'J'. For prefix strings that consisted only of the last character of the collation sequence (for example, 'Z'), the server did not form the incremented prefix, did not form the upper bound for the column and the lower bound was not included. Because of this, an index would not be used for the column. Now, for conditions of the form: emp_lname like 'ZZ%' the lower bound will be added by the optimizer as follows: emp_lname >= 'ZZ'. An index will be selected for this column, if it would have been used for the added range predicate. Note that conditions such as "emp_lname LIKE 'SZ%'" are treated by adding: emp_lname >= 'SZ' AND emp_lname < 'T' and can use an index before and after this change.

CR:299110

CR Number:   299110 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4031 15 Nov 2002 Fixed 8.0.2 4076 15 Nov 2002 Fixed 8.0.1 3056 15 Nov 2002 Fixed Description In some circumstances, fetching backward on an index scan could have caused the index scan to fetch all rows prior to the current position, back to the beginning of the table. Even without backward fetches from the client, this situation could have arisen due to prefetching. This situation can be detected by higher-than expected running times combined with a larger than expected CacheReadIndLeaf property (the 'Cache Reads: Index Leaf' performance counter).

CR:299117

CR Number:   299117 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4028 15 Nov 2002 Fixed 8.0.2 4075 15 Nov 2002 Fixed 8.0.1 3054 15 Nov 2002 Fixed Description A point of contention was present that could cause convoy phenomena to form. These phenomena could be detected by seeing that the CPU usage on a multi-CPU system dropped to about 1 CPU, while the number of active requests was high and the 'Contention: Engine' performance counter or EngineContention engine property was high.The convoys were most likely to form with requests that accessed a table through an index, with all of the indexed pages in cache. This point of contention has been removed.

CR:299119

CR Number:   299119 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4032 01 Nov 2002 Fixed 8.0.2 4076 01 Nov 2002 Fixed 8.0.1 3057 01 Nov 2002 Fixed Description Queries having DISTINCT and ORDER BY may have returned the incorrect order if the ORDER BY clause was satisfied by an index and DISTINCT was executed as a DistinctHash. Example: select DISTINCT T.y from T where T.x > 100 order by T.x If an index scan was used for the table T (the index on T.x) and DistinctHash was used, the result may not have been sorted. This is now fixed.

CR:299120

CR Number:   299120 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4028 19 Nov 2002 Fixed 8.0.2 4080 19 Nov 2002 Fixed 8.0.1 3054 19 Nov 2002 Fixed Description Simple queries such as the following: SELECT * FROM T WHERE T.x = ? would not have used an index on T.x, if the value of the host variable was NULL. In order for this issue to appear, the query must have been sufficiently simple to bypass optimization. For example, it must have contained only one table with no aggregates nor disjuncts. The predicate T.x = ? will match no rows if the host variable is NULL. While no rows were returned before this change, a complete sequential scan of the table was performed. This scan is not longer done. Further, the graphical plan would not have shown the sequential scan in this case, as the graphical plan does not use the optimizer bypass.

CR:299125

CR Number:   299125 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 3057 31 Oct 2002 Deferred Description For FIRST ROW optimization, the optimizer governor favors the plans with no materialization (e.g., no SORT or HashJoin operators). Only if a very cheap materializing plan (i.e., N times cheaper than the best non-materializing plan) is found, will the best plan be set to the very cheap plan. In some cases however, the very cheap plans were incorrectly discarded and an expensive non-materializing plan was chosen as the best plan. This has been corrected.

CR:299222

CR Number:   299222 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) 8.0.3 4510 10 Dec 2002 Fixed 8.0.2 4076 10 Dec 2002 Fixed 8.0.1 3065 10 Dec 2002 Fixed 8.0.0 2351 10 Dec 2002 Fixed Description Under certain conditions, an empty result set was not produced when GROUP BY was used and no rows were obtained. The one-row result set contained meaningless values. This has been fixed.

CR:299223

CR Number:   299223 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4539 02 Dec 2002 Fixed 8.0.2 4088 05 Dec 2002 Fixed 8.0.1 3082 05 Dec 2002 Fixed Description A valid query containing a CASE expression in both the SELECT list and the GROUP BY clause, may have failed with SQLCODE -149. For this to have occurred, the CASE expression must omit the final ELSE clause. A simple reproducible is SELECT CASE dummy_col WHEN 0 THEN 'Q1' WHEN 1 THEN 'Q2' END from dummy GROUP BY CASE dummy_col WHEN 0 THEN 'Q1' WHEN 1 THEN 'Q2' END; This has been corrected.

CR:299224

CR Number:   299224 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) 8.0.3 4510 31 Oct 2002 Fixed 8.0.2 4076 31 Oct 2002 Fixed 8.0.1 3065 31 Oct 2002 Fixed 8.0.0 2351 31 Oct 2002 Fixed Description Under certain conditions, an empty result set was not produced when GROUP BY was used and no rows were obtained. The one-row result set contained meaningless values. This has been fixed.

CR:299231

CR Number:   299231 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4510 04 Nov 2002 Fixed 8.0.2 4076 04 Nov 2002 Fixed Description Attempts to connect to more than one server via jConnect would have failed, if the servers were running on the same machine. The error message would report that the database could not be started. This has been fixed.

CR:299246

CR Number:   299246 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4510 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed Description With the UltraLite Java runtime (ulrt.jar) that did not include secure stream classes from Certicom, attempting to use the HTTPS protocol would have given a stack trace. This has been fixed. The HTTPS option is now disabled unless the UltraLite Java runtime includes the secure stream classes from Certicom.

CR:299297

CR Number:   299297 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   7.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4537 02 Dec 2002 Fixed 8.0.2 4087 02 Dec 2002 Fixed 8.0.1 3081 02 Dec 2002 Fixed 7.0.4 3394 02 Dec 2002 Fixed Description The database server could have reported a fatal error or assertion failure due to a failed IO operation. The error message displayed may have been "Fatal error: Unknown device error", "Fatal error: no error", "A write failed with error code: (1453)", "A write failed with error code: (1450)", or some other form of fatal error or assertion failure message. Certain errors such as 1450 and 1453 can (apparently) be reported by NT during "normal" operation. The server now retries IOs that fail with one of these particular error codes up to 100 times. If the IO does not succeed after 100 attempts, the server will now report the error as a fatal error (same message as before). It is impossible to know whether 100 attempts will give the OS sufficient time to remedy whatever problems it is having. It is believed that the OS reports these errors when available memory is low. A work around may be to ensure that the system is not low on memory.

CR:299301

CR Number:   299301 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.1 3068 07 Nov 2002 Fixed 8.0.2 4076 07 Nov 2002 Fixed 8.0.3 4511 07 Nov 2002 Fixed 9.0.0 430 07 Nov 2002 Fixed Description Running the dbunload utility with options -ar or -an would not have created a reload.sql file that had check constraints turned off. This may have caused errors when loading data into the new database. This is now fixed.

CR:299351

CR Number:   299351 Product Name:   UltraLite Product Component:   Analyser Java Classes Status:   Closed OS:   Microsoft Windows NT Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3389 14 Nov 2002 Fixed Description The UltraLite analyzer was generating a C++ function prototype for the Open method of a ULResultSet object with duplicate variable names. This would happen if a host variable was used more than twice to represent a value for the same column in a query. For example: SELECT * from T where x > ? OR x < ? OR x = ?. This has been fixed, the parameter names are now unique. Workaround Description  The workaround is to delete the duplicates by hand. But the customer has many statement like this and it would be a lot of work for him.

CR:299361

CR Number:   299361 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4510 01 Nov 2002 Fixed 8.0.2 4076 01 Nov 2002 Fixed 8.0.1 3067 01 Nov 2002 Fixed Description During checkpoints, more writes might have been performed than necessary to write out table bitmaps. Unnecessary writes are no longer done.

CR:299362

CR Number:   299362 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) 8.0.1 3066 31 Oct 2002 Fixed Description UltraLite applications written for Palm devices would have failed to link, with an unresolved symbol ULLoadUnaligned32 error, as of build 3055. This has now been corrected.

CR:299364

CR Number:   299364 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) 8.0.3 4511 05 Nov 2002 Fixed 8.0.3 4076 05 Nov 2002 Fixed Description Using DBISQL with the JDBC-ODBC bridge and executing SQL with no command delimiters as in the following example: create table dbtran_T1( pk integer not null, c1 varchar(100) null, primary key(pk) ) INSERT INTO dbtran_T1 VALUES (1,'rm1') INSERT INTO dbtran_T1 VALUES (2,'rm2') COMMIT WORK would very likely have caused dbisql to crash or silently exit. This problem has now been fixed.

CR:299368

CR Number:   299368 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4511 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed Description If the server was running in bulk mode (see the "-b" command line option) and a transaction caused a rollback, then in some rare situations it was possible for the database to become inconsistent as far as the catalog is concerned. This problem has now been corrected. As a consequence of this fix, the server will now employ the rollback log during the bulk mode and not use the transaction log as before.

CR:299440

CR Number:   299440 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4514 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed Description When using large fonts with Windows,, the MobiLink Monitor's New Watch and Edit Watch dialogs could have truncated text in the Remove button and in the time units combo box, if a time-based property was selected. This has been fixed.

CR:299441

CR Number:   299441 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Dec 2002 Workaround Description DBISQL(java) reports for a result set multible times There was an error reading the results of the SQL statement. The displayed results maybe incorrect or incomplete The same result set does not give an error in dbisqlc.

CR:299466

CR Number:   299466 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4510 01 Nov 2002 Fixed 8.0.2 4076 01 Nov 2002 Fixed 8.0.1 3067 01 Nov 2002 Fixed Description The network server now supports the LocalOnly TCP option (eg. -x tcpip(LocalOnly=YES), which restricts connections to the local machine. Connection attempts from remote machines will not find this server (regardless of connection parameters), and dblocate running on remote machines will not see this server. This parameter effectively turns the netwark server into a personal server, without the personal server limitations(i.e. no connection limit, no two CPU limit, etc.)

CR:299521

CR Number:   299521 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4547 13 Dec 2002 Fixed 8.0.2 4093 13 Dec 2002 Fixed 8.0.1 3085 13 Dec 2002 Fixed Description An update statements that sets a date column to the same value like: UPDATE T1 set Col1=Col1 may crash the engine. After rebuilding the db file the problem does not happen. The db file was created with version 7 and the data in the column are maybe wrong or corrupted. but we should not crash. dbvalid did not return any error.

CR:299546

CR Number:   299546 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) 8.0.3 4513 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed Description If executing a statement resulted in a long error message being returned from the server, then retrieving that error message using the JDBC-ODBC bridge would likely have crashed the application or resulted in very strange behaviour. This problem has now been fixed.

CR:299548

CR Number:   299548 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) 8.0.3 4513 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed 8.0.1 3069 05 Nov 2002 Fixed 8.0.0 2352 05 Nov 2002 Fixed Description Pressing the F8 key while DBISQL was busy executing a statement, would have caused it to report an internal error. This has been fixed.

CR:299561

CR Number:   299561 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 3384 05 Nov 2002 Fixed 7.0.2 1606 05 Nov 2002 Fixed Description Calling the system procedure sa_locks() multiple times, while the server was busy, may have caused the server to crash. This is now fixed.

CR:299575

CR Number:   299575 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 4513 05 Nov 2002 Fixed 8.0.2 4076 05 Nov 2002 Fixed 8.0.1 3069 05 Nov 2002 Fixed 8.0.0 2352 05 Nov 2002 Fixed Description If the main Sybase Central window was partially off screen, any dialogs that were opened may also have been partially off screen. This has now been fixed.

CR:299584

CR Number:   299584 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4616 21 Mar 2003 Fixed 8.0.2 4231 21 Mar 2003 Fixed Description After a row is added to an oledb rowset (ADO recordset), its edit state is set to DBPENDINGSTATUS_NEW (ADO adEditAdd). If column values are then set for the row, the edit state should not change, but the ASA provider was changing it to DBPENDINGSTATUS_CHANGED (ADO adEditInProgress). Now it will no longer do this for newly added rows, so they will retain their DBPENDINGSTATUS_NEW (aado adEditAdd) state until the row is committed to the database or the changes are rolled back.

CR:299615

CR Number:   299615 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) 8.0.3 4537 03 Dec 2002 Fixed 8.0.2 4087 03 Dec 2002 Fixed Description The following sequence of statements would have resulted in a server crash: create table table1 (col1 int, col2 int, col3 int ); create view v1 as select col1, col2, col3 from table1; alter view v1 (col1) as select col1, col2, col3 from table1; The ALTER VIEW statement included a column list for the view which did not match the SELECT list. An error is now reported.

CR:299630

CR Number:   299630 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 3601 05 Nov 2002 Fixed Description When applying the 8.0.1 maintenance patch to an 8.0.0 installation, the encryption libraries (libdbtls8[_r].so) do not get upgraded to the 8.0.1 version. A side affect of this, is that applying 8.0.1 EBFs to an upgraded 8.0.0 install will not apply the EBF as the encryption library is of an older 8.0.0 version. This is now fixed with the 8.0.2 patch, but a work around would be: In the maintenance install directory, copy the file 'encryption_ml' in the 'files' directory to 'encryption' and rerun the install. This will ensure that the encryption libraries get updated. A regular 8.0.1 EBF can be applied to the updated 8.0.0 install.

CR:299664

CR Number:   299664 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4526 25 Nov 2002 Fixed 8.0.2 4083 25 Nov 2002 Fixed 8.0.1 3076 25 Nov 2002 Fixed 7.0.4 3391 25 Nov 2002 Fixed Description Using the ASA oledb provider to access a database from Powerbuilder would have failed as of versions 7.0.4.3382, 8.0.1.3062 and 8.0.2.4076. This was due to a problem introduced as part of the fix for issue 270447. This problem has now been corrected.

CR:299721

CR Number:   299721 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.04 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4515 11 Nov 2002 Fixed 8.0.2 4076 11 Nov 2002 Fixed 8.0.1 3070 11 Nov 2002 Fixed 8.0.0 2352 11 Nov 2002 Fixed 7.0.4 3386 11 Nov 2002 Fixed Description The VALIDATE TABLE statement, or the dbvalid utility, could have spuriously reported missing index entries. When checking a foreign combined index, (ie 5.x format), with the FULL CHECK option, entries containing some, but not all, nulls would have generated a spurious report of a missing index entry. This is now fixed.

CR:299754

CR Number:   299754 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 4078 12 Nov 2002 Fixed 8.0.1 3072 12 Nov 2002 Fixed 8.0.0 2353 12 Nov 2002 Fixed 7.0.4 3388 12 Nov 2002 Fixed Description Executing a statement which contained two consecutive comments, and the first comment contained an unmatched quotation mark, and the second comment contained a question mark, would have caused dbisql to report the error: "JZ0SA: Prepared Statement: Input parameter not set, index: 0". For example, the statement below would not have executed: CREATE PROCEDURE test AS BEGIN -- "a -- ? END This problem, which is related to issue 217915, has been fixed.

CR:299786

CR Number:   299786 Product Name:   UltraLite Product Component:   Analyser Java Classes Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 11 Nov 2002 Fixed 8.0.2 4077 11 Nov 2002 Fixed Description The UltraLite analyzer was generating a macro that was not defined, when processing a query that used the STR() function with the last 2 (optional) parameters omitted. The analyzer has been changed so that it generates the defined macro with the default parameters supplied, if they are not specified. A workaround is to add the macro: #define UL_STR_CHAR_DOUBLE( l, dst, s1 ) \ ULStr( UL_STRING(dst), s1, (ul_s_long)10, (ul_s_long)0 ) to the users ulprotos.h file. This workaround only works if both optional parameters to the function are omitted.

CR:299822

CR Number:   299822 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 4516 14 Nov 2002 Fixed 8.0.2 4077 14 Nov 2002 Fixed Description Connection.getTable(), TableSchema.getOptimalIndex() and TableSchema.getIndex() would have returned SQLE_CLIENT_OUT_OF_MEMORY when the table or index requested could not be found. Now SQLE_INDEX_NOT_FOUND or SQLE_COLUMN_NOT_FOUND is correctly returned.

CR:299855

CR Number:   299855 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Windows CE 2.11 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 3027 21 Nov 2002 Fixed Description When attempting a connection from an aplication running on a 32-bit Windows platform, and specify a non-existant datasource name, the ODBC Driver Manager will report an error. On Unix or Windows CE, when not using a Driver Manager, a similar error will now be reported by the ODBC driver. Previously no error was reported and the driver would go ahead and attempt to connect, often resulting in a non-informative error message such as 'database server not found'. An unexpected side effect of this change is that a connection string that contained an invalid datasource name could have connected successfully, if there was enough additional connection parameters to establish a connection. With the new change, an error will be reported instead.

CR:299872

CR Number:   299872 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) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 3602 12 Nov 2002 Fixed 8.0.1 3070 12 Nov 2002 Fixed Description In some circumstances when a connection was established while the server was shutting down the server could crash. Database files are not affected. This affected UNIX servers only and has been fixed.

CR:299936

CR Number:   299936 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4514 08 Nov 2002 Fixed 8.0.2 4076 08 Nov 2002 Fixed 8.0.1 3069 08 Nov 2002 Fixed Description A new property, QueryCachedPlans, has been added which shows how many query execution plans are currently cached. This property can be retrieved using the CONNECTION_PROPERTY function to show how many query execution plans are cached for a given connection, or DB_PROPERTY can be used to count the number of cached execution plans across all connections. This property can be used in combination with QueryCachePages, QueryOptimized, QueryBypassed, and QueryReused to help determine the best setting for the MAX_PLANS_CACHED option.

CR:299947

CR Number:   299947 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 11 Nov 2002 Fixed 8.0.2 4077 11 Nov 2002 Fixed 8.0.1 3071 11 Nov 2002 Fixed Description Expressions of the form '0-(expr)' could have given the wrong answer, namely '(expr)', where (expr) is any expression. For example: select 0-1; ---> gives 1 incorrectly select 0.0-1.0; ---> gives 1 incorrectly Now the correct answer is returned.

CR:299979

CR Number:   299979 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 4516 12 Nov 2002 Fixed Description If a version 8.0.1 installation was upgraded to version 8.0.2, the ASA performance counter objects would have appeared twice in the list of objects in the NT performance monitor. This has now been fixed.

CR:300072

CR Number:   300072 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4565 17 Jan 2003 Fixed Description Two new statistics have been added to the Windows Performance Monitor; a database object, "Connection Count" and an engine object "Comm: Licenses In Use", to track the number of connections in use.

CR:300073

CR Number:   300073 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.3 4518 13 Nov 2002 Fixed 8.0.2 4079 13 Nov 2002 Fixed 8.0.1 3073 13 Nov 2002 Fixed Description When using an external procedure or function written in Delphi, the server could have crashed with a floating point exception. The DLL would have enabled a number of floating point exceptions that are masked by default. While the proper fix would be to rewrite the external procedure or function, the server will now reset/restore the floating point control word at appropriate points. Code, such as the following, can be used to explicitly set the floating point control word: const MCW_EM = DWord($133f); begin Set8087CW(MCW_EM); end;

CR:300081

CR Number:   300081 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Novell NetWare Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4569 20 Jan 2003 Fixed 8.0.2 4204 20 Jan 2003 Fixed 8.0.1 3095 20 Jan 2003 Fixed Description Executing a CREATE SERVER statement with an unsupported class on NetWare would have succeeded, but executing a CREATE EXISTING TABLE on that server would have caused the NetWare server to abend. This has now been fixed. Note that 'asajdbc' is the only supported class on NetWare.

CR:300084

CR Number:   300084 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.3 4540 05 Dec 2002 Fixed Description The option APPEND { ON | OFF } has been added to the UNLOAD and UNLOAD TABLE statements. The default for APPEND is OFF. With APPEND ON the output file will not be overwritten if it already exists. Instead, the engine will append any unloaded data to the end of the file.

CR:300109

CR Number:   300109 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 4078 12 Nov 2002 Fixed 8.0.1 3072 12 Nov 2002 Fixed 7.0.4 3388 12 Nov 2002 Fixed Description Columns were always being reported as not nullable through the ASA provider. This was most noticeable when generating datasets in Visual Studio .NET. The AllowDBNull property would always be false, even if a column allowed nulls. This has been corrected.

CR:300115

CR Number:   300115 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) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 4078 12 Nov 2002 Fixed Description When executing multiple consecutive MESSAGE ... TYPE WARNING TO CLIENT statements, dbisql may not have displayed the messages in the correct order. For example, when executing the following compound statement: begin message 'one' type warning to client; message 'two' type warning to client; end message "two" would have displayed before the message "one". This problem has been fixed.

CR:300125

CR Number:   300125 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4537 02 Dec 2002 Fixed 8.0.2 4087 02 Dec 2002 Fixed 8.0.1 3081 02 Dec 2002 Fixed 8.0.0 2356 02 Dec 2002 Fixed 7.0.4 3394 02 Dec 2002 Fixed Description When reading a script file which contained an EOF character, (0x1A), DBISQL would have reported a "Lexical Error" rather than interpreting the character as an end-of-file marker. Now the end-of-file character is recognized correctly. Note that the end-of-file character is optional in script (.SQL) files.

CR:300128

CR Number:   300128 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 3602 12 Nov 2002 Fixed 8.0.1 3072 12 Nov 2002 Fixed Description The minimum cache size calculated by a server running on a Windows platform would have been different from one running on a UNIX platform. This change makes the behaviour consistent. Assuming that no -cl parameter was specified when starting a server: 1) Prior to this change, if -c was specified, a Windows server would set the min cache size to be the same value as the -c value (i.e. the same as the initial value) whereas a UNIX server would make the min cache size 2MB. This change makes all platforms use the Windows behaviour in this situation: min cache size is the same as the initial cache size. 2) Prior to this change, if _no_ -c was specified, the initial cache size is computed by the server to be an appropriate size based on the size of the database(s) being started. A Windows server would use this initial cache size value as the minimum cache size, whereas a UNIX server would make the min cache size 2MB. This change makes all platforms set the minimum cache size to a platform-specific minimum value as follows: CE: 600K, all other Windows platforms: 2M, all UNIX platforms: 8M

CR:300139

CR Number:   300139 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4516 12 Nov 2002 Fixed 8.0.2 4078 12 Nov 2002 Fixed 8.0.1 3072 12 Nov 2002 Fixed Description Under Windows 95, there was no response to a right-click on the server icon in the system tray. This has now been fixed.

CR:300192

CR Number:   300192 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 4517 12 Nov 2002 Fixed 8.0.2 4079 12 Nov 2002 Fixed Description When running the server on NetWare 4.x, it required that TCPIP.NLM be already loaded on the NetWare server. This requirement has been removed, it is now loaded dynamically.

CR:300203

CR Number:   300203 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4517 14 Nov 2002 Fixed 8.0.2 4079 14 Nov 2002 Fixed 8.0.1 3072 14 Nov 2002 Fixed Description Using Syntax 2 of the FORWARD TO statement could have caused the local ASA server to crash. An example is as follows: forward to SOME_REMOTE_SERVER; select * from systable; ===> CRASH Whereas the following: forward to SOME_REMOTE_SERVER {select * from systable} was not a problem. This has now been fixed.

CR:300214

CR Number:   300214 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 4517 14 Nov 2002 Fixed 8.0.2 4079 14 Nov 2002 Fixed Description Calling TableSchema.isColumnGlobalAutoIncrement() with an invalid column name would have caused a crash. It now throws a SQLException with SQLE_COLUMN_NOT_FOUND.

CR:300231

CR Number:   300231 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) 8.0.3 4516 14 Nov 2002 Fixed 8.0.2 3602 14 Nov 2002 Fixed Description When multiple threads running Java code tried to disconnect at about the same time, a thread deadlock was possible. This has been fixed.

CR:300349

CR Number:   300349 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4523 21 Nov 2002 Fixed 8.0.1 3075 21 Nov 2002 Fixed Description Estimates for search conditions are updated as queries are evaluated, based on the number of times that a predicate is found to be true. Before this change, conditions that were found in disjunctive clauses (OR'ed conditions) might not have been used to update the statistics. Similarly, conditions appearing in IS [NOT] {TRUE|FALSE|UNKNONWN} conditions, also might not have updated the stored selectivity estimates. For example, the following query would not have updated the selectivity of column T.x nor T.y. SELECT * FROM T WHERE T.x = 1 OR T.y = 2 Note that only the first predicate that is evaluated for a given table can be used to reduce the selectivity estimate for a condition, but any predicate can raise the estimate.

CR:300375

CR Number:   300375 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 4518 15 Nov 2002 Fixed 8.0.2 4079 15 Nov 2002 Fixed 8.0.1 3073 15 Nov 2002 Fixed 8.0.0 2353 15 Nov 2002 Fixed Description When editing a BIT value and then switching to a new row the change would be lost. This has now been fixed. This problem occurred in dbisql as well.

CR:300401

CR Number:   300401 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) 8.0.3 4518 15 Nov 2002 Fixed 8.0.2 3603 15 Nov 2002 Fixed 8.0.1 3073 15 Nov 2002 Fixed 7.0.4 3388 15 Nov 2002 Fixed Description Running the dbexpand utility on Unix platforms, was taking a long time to expand a compressed database file. This has now been greatly improved.

CR:300402

CR Number:   300402 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) 8.0.3 4503 21 Nov 2002 Fixed 8.0.2 4076 21 Nov 2002 Fixed 8.0.1 3060 21 Nov 2002 Fixed 8.0.0 2350 21 Nov 2002 Fixed 7.0.4 3386 21 Nov 2002 Fixed Description Executing the system procedure, xp_startmail, would have returned either 0 (success) or 2 (failure), which maked diagnosing xp_starmail failures difficult. Now xp_startmail, (as well as xp_sendmail and xp_stopmail), returns one of the following: Value Description 0 Success 2 xp_startmail failed 3 xp_stopmail failed 5 xp_sendmail failed 11 Ambiguous recipients 12 Attachment not found 13 Disk full 14 Failure 15 Invalid session 16 Text too large 17 Too many files 18 Too many recipients 19 Unknown recipient 20 Login failure 21 Too many sessions 22 User abort 23 No MAPI 24 xp_startmail not called (xp_sendmail and xp_stopmail only)

CR:300404

CR Number:   300404 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4518 15 Nov 2002 Fixed 8.0.2 4079 15 Nov 2002 Fixed 8.0.1 3073 15 Nov 2002 Fixed 8.0.0 2353 15 Nov 2002 Fixed Description Specifying -mn "" on the dbmlsync commmand line would have caused it to crash. This has been fixed.

CR:300425

CR Number:   300425 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4527 15 Nov 2002 Fixed 8.0.2 4099 13 Jan 2003 Fixed Description In order to make cost based decisions on which indexes to use, the optimizer needs to know some physical properties or statistics of the various candidate indexes. These statistics include the number of leaf pages in and the depth of an index. The server was obtaining the approximate index statistics by performing run time sampling of indexes which could have been an expensive operation, especially when optimizing small queries with a large number of potential indexes to choose from. The server will now maintain the required statistics as each index is updated. Not only will the statistics now be available to the optimizer at virtually no cost, the statistics will also be accurate. The new statistics will persist in SYSATTRIBUTE in the form of one row for each statistics for an index. The rows in SYSATTRIBUTE will only be created when required, e.g., a row for index depth will be created only when the index depth increases to 2. The statistics will be maintained for all indexes including those on catalog tables. Also, the VALIDATE statement will now verify that the statistics on the specified index(es) are accurate and will generate an error otherwise.

CR:300469

CR Number:   300469 Product Name:   UltraLite Product Component:   Code Generator Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4519 18 Nov 2002 Fixed Description If a statement had a host variable whose datatype could not be determined from the context of the query (for example, SELECT NULLIF( ?, ? )), the analyzer would have generated an error message like: "Statement at null(-1) could not be processed". In 7.x, the analyzer would not have generated an error message at all, but would have generated code that could not have been compiled. The analyzer now generates an error message that indicates which host variable is in question and that the user should use the CAST() function to set the datatype.

CR:300483

CR Number:   300483 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4519 15 Nov 2002 Fixed 8.0.2 4080 15 Nov 2002 Fixed 8.0.1 3073 15 Nov 2002 Fixed Description Under some circumstances, the statistics gathering in the server during query execution could have caused a divide by zero floating point exeception. Usually, these exceptions do not cause any significant problems. The problem has been fixed.

CR:300502

CR Number:   300502 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4519 14 Nov 2002 Fixed 8.0.2 4080 14 Nov 2002 Fixed 8.0.1 3073 14 Nov 2002 Fixed 8.0.0 2353 14 Nov 2002 Fixed Description If errors occurred during the Prepare_for_download and/or Download events, the MobiLink server would have commited the upload on the server side quietly, without notifying the client. The ASA client would the have displayed the error "communication error..." and rolled back the upload. In the next run, dbmlsync would again have complained with "Progress offset mismatch, resending upload from the consolidated database's progress offset". This problem is now fixed.

CR:300534

CR Number:   300534 Product Name:   UltraLite Product Component:   Code Generator Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4519 15 Nov 2002 Fixed 8.0.2 4080 15 Nov 2002 Fixed 8.0.3 3076 22 Nov 2002 Fixed Description The analyzer could have generated code after a generated return statement. This code was only defined for the Palm platform and it was defined to free memory. This has been fixed.

CR:300584

CR Number:   300584 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) 8.0.3 4526 25 Nov 2002 Fixed 8.0.2 4083 25 Nov 2002 Fixed 8.0.1 3076 25 Nov 2002 Fixed Description An assertion failure could have been generated when using an aggregate function in a GROUP BY clause. For example, the following query could have caused the assertion failure: 102300 (8.0.1.3067) File associated with given page id is invalid or not open select DT.TID from sys.syscolumn C, ( select T.table_name, max( table_id ) TID from sys.systable T group by T.table_name ) DT where C.column_name = DT.table_name group by DT.TID In order for the problem to have occurred, an intervening work table must have appeared between the first GROUP BY clause and the second. THis has now been fixed.

CR:300649

CR Number:   300649 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 1630 10 Sep 2003 Fixed 9.0.0 1245 27 Nov 2003 Fixed 8.0.3 5000 06 May 2004 Fixed Description The list of statistics displayed on the Statistics tab for a server was incorrect and incomplete. Several database statistics were incorrectly included in the list (their values would always be displayed as zero) and many server statistics were missing. Now, the list contains the complete set of server statistics, which is a subset of the results returned from the stored procedure sa_eng_properties().

CR:300775

CR Number:   300775 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4532 09 Dec 2002 Fixed 8.0.2 4085 09 Dec 2002 Fixed 8.0.1 3078 09 Dec 2002 Fixed 8.0.0 2354 09 Dec 2002 Fixed Description Attempting to apply an EBF on machines having only the Client portion (i.e., no database server) of Adaptive Server Anywhere installed would have failed. This has been fixed.