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

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

CR:339931

CR Number:   339931 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 4843 19 Nov 2003 Fixed 8.0.2 4346 19 Nov 2003 Fixed Description If an ALTER PUBLICATION statement failed, e.g. a table being added was already part of the publication, then trigger definitions for any tables referenced since the database was started would have been disabled. The triggers would be restored by restarting the database or by executing a successful ALTER PUBLICATION. This has been fixed.

CR:339938

CR Number:   339938 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 1701 27 Nov 2003 Fixed Description When using Windows XP with the XP-style desktop and JDK 1.4.2, time unit drop down lists in the Go To dialog and the New/Edit Watch dialogs would have shown an ellipsis (three dots) instead of "ms" for the default time unit. This is a Java issue (Sun bug number 4867054), for which a work around has been implemented.

CR:339940

CR Number:   339940 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2209 16 Mar 2004 Fixed 9.0.1 1817 16 Mar 2004 Fixed 9.0.0 1266 16 Mar 2004 Fixed 8.0.3 4894 16 Mar 2004 Fixed 8.0.2 4369 16 Mar 2004 Fixed Description The MobiLink ASA Client DBMLSync, and SQL Remote may have deleted old transaction log files that were needed for synchronization. Now, instead of deleting the old transaction log files, a warning will be issued if the database truncation offset is greater than the minimum value of progress offsets from SYSSYNC or the confirm_sent from SYSREMOTEUSER. This warning message will have a prefix of "I." for 802 and "W." for all other versions.

CR:339955

CR Number:   339955 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   4.2.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1645 26 Nov 2003 Fixed 9.0.0 1240 26 Nov 2003 Fixed Description The editor would have thrown an exception when moving the cursor to the next word or previous word when using control + arrow keys, if there was a special punctuation character. Examples of special punctuation characters are: /u2018, /u2019, and /u201d, (open single quote, closing single quote, and double quote). These characters are used by Mocrosoft Word and the problem could have occurred when pasting text from Word into the editor. This problem is now fixed. Note, this problem also affected the editor in Sybase Central.

CR:340046

CR Number:   340046 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 1812 15 Dec 2003 Fixed 9.0.0 1253 15 Dec 2003 Fixed 8.0.3 4866 15 Dec 2003 Fixed 8.0.2 4356 15 Dec 2003 Fixed 8.0.1 3143 15 Dec 2003 Fixed Description An exception could have occurred when moving through a result set that contained rows with column lengths 200 bytes or greater. For example, (assume the following table contains entries with the NOTES column containing 400 characters): create table TBLVARCHAR ( ID unsigned bigint not null, NOTES long varchar, primary key (ID) ); The following is a VB example that selects from this table: rs.Open "SELECT * FROM tblVARCHAR", conn, adOpenStatic, adLockReadOnly ' loop through all recordsets Do While Not rs.EOF For i = 0 To 1 Debug.Print rs.Fields(i).Name, TypeName(rs.Fields(i).Value), rs.Fields(i).Value Next rs.MoveNext Loop rs.Close This problem has been fixed. The GetRowsAt() method now handles long columns.

CR:340047

CR Number:   340047 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1699 21 Nov 2003 Fixed 9.0.0 1242 21 Nov 2003 Fixed 8.0.3 4844 21 Nov 2003 Fixed 8.0.2 4346 21 Nov 2003 Fixed Description When the SQLCONNECT environment variable was set, its parameters would have overridden parameters in the connection string (specified using -c). This has been fixed, the parameters in the connection string now have precedence.

CR:340071

CR Number:   340071 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 1692 24 Nov 2003 Fixed 9.0.0 1246 27 Nov 2003 Fixed 8.0.3 4838 24 Nov 2003 Fixed 8.0.2 4343 24 Nov 2003 Fixed Description Updating a Runtime installation with an EBF, would not have updated the runtime engine, but would have installed the Personal Server. This has now been fixed.

CR:340196

CR Number:   340196 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   4.2.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2292 04 May 2004 Fixed Description When starting the MobiLink server as a service from Sybase Central, Sybase Central would have indicated that it had successfully started, even if it really had failed to start for some reason. This has been corrected, Sybase Central will now indicate a successful start only if the MobiLink server really does start

CR:340235

CR Number:   340235 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 1700 20 Nov 2003 Fixed Description If a ROLLBACK TRANSACTION specified a name which did not match an existing savepoint, no error was given; instead, a full ROLLBACK was performed. An error will now be given if the name does not match one specified in a SAVE TRANSACTION statement or the name on the outermost BEGIN TRANSACTION statement.

CR:340244

CR Number:   340244 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 1700 26 Nov 2003 Fixed 9.0.0 1243 26 Nov 2003 Fixed Description When using the QueryEditor, closing and reopening the database connection would have caused the QueryEditor to have been changed to All. This problem has been fixed.

CR:340293

CR Number:   340293 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 1701 21 Nov 2003 Fixed 9.0.0 1243 21 Nov 2003 Fixed 8.0.3 4846 21 Nov 2003 Fixed 8.0.2 4347 21 Nov 2003 Fixed Description The request level log may have shown "unknown" for some requests. This has been fixed

CR:340371

CR Number:   340371 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1718 10 Dec 2003 Fixed 9.0.0 1252 10 Dec 2003 Fixed 8.0.3 4863 10 Dec 2003 Fixed 8.0.2 4354 10 Dec 2003 Fixed Description If the ASA installation location was anything other than the default location and the HKey_Local_Machine\Software\Adaptive Server Anywhere\x.0\Location registry key was empty or incorrect, an EBF install would not have detected the presence of an existing install and would have failed. This has been fixed.

CR:340384

CR Number:   340384 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 1697 26 Nov 2003 Fixed 9.0.0 1240 26 Nov 2003 Fixed Description When running dbisql, (or Sybase Central), it could have failed with a SecurityException saying that it could not open a registry node or preferences file, when logged on as a non-privileged user. This problem has been fixed.

CR:340386

CR Number:   340386 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1813 17 Dec 2003 Fixed 9.0.0 1254 17 Dec 2003 Fixed Description When the MobiLink server encountered error -10050 (Expecting ? columns in cursor, but found ?) no error was written to logfiles or displayed on the screen. This has been fixed.

CR:340410

CR Number:   340410 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 1712 04 Dec 2003 Fixed 9.0.0 1251 04 Dec 2003 Fixed 8.0.3 4859 04 Dec 2003 Fixed 8.0.2 4353 04 Dec 2003 Fixed Description If an application was started from a very long directory specification (about 80 characters), connected to a database and then crashed or was killed, the server may also have crashed. This has been fixed.

CR:340419

CR Number:   340419 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 1705 24 Nov 2003 Fixed 9.0.0 1245 24 Nov 2003 Fixed 8.0.3 4850 24 Nov 2003 Fixed 8.0.2 4349 24 Nov 2003 Fixed Description It was possible to create userids, passwords and database encryption keys that could not be specified in a connection string. As well, it was possible to start servers with server and database names that could not be specified in a connection string. This has been fixed so that attempting to create a userid, password or database encryption key that is invalid, or attempting to start a server with an invalid server or database name, will fail with an error. Valid userids, passwords, database encryption keys, engine names and database aliases must NOT: - start with whitespace or single or double quotes - end with whitespace - contain semicolons

CR:340421

CR Number:   340421 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1711 03 Dec 2003 Fixed 9.0.0 1251 03 Dec 2003 Fixed Description When using the syntax highlighting editor and changing any of the format values (ie colour, font size etc), the change would not have taken effect immediately. When changing the font size, the cursor would have moved according to the new font size, but the characters were still displayed at the old font size. Format values are changed by opening the Options panel, selecting Editor, and then the Format tab. These problems have been fixed. Note, these problem existed, and have been fixed, in Sybase Central as well. Workaround Description  Don't change the font size. Or, change the size, save it with Make Permanent, close ISQL and reopen.

CR:340488

CR Number:   340488 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1704 24 Nov 2003 Fixed 9.0.0 1245 24 Nov 2003 Fixed Description An UltraLite dynamic SQL application, running on a PALM device, could have crashed when executing a query involving the COUNT() aggregate function. An odd-address reference to a LONG integer could have been referenced, as the Count() expression was being invoked using an invalid prototype. This has been corrected.

CR:340496

CR Number:   340496 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.1 3141 27 Nov 2003 Fixed 8.0.3 4852 27 Nov 2003 Fixed Description If a stored procedure contained a query which referenced a user-defined function, calling the procedure many times could result in reduced performance or a "dynamic memory exhausted" error. This has been fixed. A workaround is to set the Max_plans_cached option to 0 to disable query caching.

CR:340537

CR Number:   340537 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 1704 26 Nov 2003 Fixed 9.0.0 1245 26 Nov 2003 Fixed 8.0.3 4849 26 Nov 2003 Fixed 8.0.2 4348 26 Nov 2003 Fixed Description It was possible for an application using dblib to have crashed, if a parse error occurred on a connection string that was longer than about 50 characters. This has been fixed.

CR:340542

CR Number:   340542 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1706 27 Nov 2003 Fixed 9.0.0 1245 27 Nov 2003 Fixed 8.0.3 4851 27 Nov 2003 Fixed 8.0.2 4348 27 Nov 2003 Fixed Description When recovering a database that has been created before version 8.0.0, and the recovery failed with the error "Database cannot be started -- {log name} not expecting any operations in transaction log", the server would then have crashed. This has been fixed.

CR:340561

CR Number:   340561 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 1712 26 Nov 2003 Fixed 9.0.0 1252 26 Nov 2003 Fixed 8.0.3 4849 09 Dec 2003 Fixed 8.0.2 4348 09 Dec 2003 Fixed Description Queries embedded within stored procedures, or queries involving proxy tables, that contained an ORDER BY clause may have failed with an erroneous syntax error (typically -152 'Invalid ORDER BY specification') or may have returned the data sorted in the opposite order to that desired. This may have occurred for any ORDER BY clause, whether in a SELECT, UPDATE, UNION, or LIST() aggregate function. This erroneous behavior has been corrected.

CR:340562

CR Number:   340562 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2188 26 Nov 2003 Fixed 9.0.1 1703 26 Nov 2003 Fixed 9.0.1 1704 15 Mar 2004 Fixed Description On CE, when a removable media card containing the UltraLite database was ejected while the application is running, the runtime would have reported the error SQLE_MEMORY_ERROR. If the device was turned off and turned back on again (for example, when it enters and leaves power saving mode), it essentially ejects and reinserts all removable media cards, which would have caused this error. This problem has now been fixed, the runtime silently reattempts to access the database file for a few seconds. If it fails after this time, then the card must have been manually ejected and it will return SQL error SQLE_DEVICE_IO_FAILED. If an error callback has been registered, the callback can prompt the user to reinsert the media card and return UL_ERROR_ACTION_TRY_AGAIN to have the runtime retry the operation. If the runtime detects that a different card with another database with the same name is inserted, it will set SQL error SQLE_INCORRECT_VOLUME_ID. Again, the error callback will have the opportunity to prompt the user to reinsert the original card.

CR:340594

CR Number:   340594 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1704 26 Nov 2003 Fixed 9.0.0 1245 26 Nov 2003 Fixed Description Attempting to load a non-usm file, or a ulxml file as if it was a usm file, would have resulted in a crash. This has been fixed and an error is now reported.

CR:340672

CR Number:   340672 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 4349 26 Nov 2003 Fixed 8.0.3 4851 26 Nov 2003 Fixed 9.0.0 1245 26 Nov 2003 Fixed 9.0.1 1706 26 Nov 2003 Fixed Description If a CREATE PROCEDURE statement was executed, and the length of the user name and procedure name together exceed 150 bytes, the server would have crashed. This has been fixed.

CR:340674

CR Number:   340674 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2250 19 Mar 2004 Fixed 8.0.3 4948 19 Mar 2004 Fixed Description If a complex expression could not have been handled by the server, due to some internal limitation, the request would have failed with the error "Invalid expression near '%1'". Now the server will return a more informative error. If a function or procedure call has too many arguments, error -994 - "Too many arguments for function or procedure '%'" is returned. If an IF expression has too many conditional expressions in its condition, or there are too many outer references in a SQL statment, error -890 - "Statement size or complexity exceeds server limits" is returned.

CR:340693

CR Number:   340693 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.2 4349 26 Nov 2003 Fixed 8.0.3 4851 26 Nov 2003 Fixed 9.0.0 1245 26 Nov 2003 Fixed 9.0.1 1705 26 Nov 2003 Fixed Description If focus was not in the SQL Statements window, then after using the "Go To" dialog, the focus would appear to be in the SQL Statements field, but characters typed would not be displayed in the field until it was clicked. This has been fixed, focus will now be in the SQL Statements window after using "Go To".

CR:340721

CR Number:   340721 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 4349 26 Nov 2003 Fixed 8.0.3 4851 26 Nov 2003 Fixed 9.0.1 1706 26 Nov 2003 Fixed 9.0.0 1245 26 Nov 2003 Fixed Description If a BACKUP DATABASE statement attempted to create an archive backup using a name longer than 255 bytes, the server would have crashed. This has now been fixed.

CR:340731

CR Number:   340731 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1245 26 Nov 2003 Fixed 9.0.1 1705 26 Nov 2003 Fixed Description From a column's property sheet, it was not possible to specify the empty string as the default value for a character type column. This has been fixed. Now, selecting the "User-defined" radio button and leaving the text field empty sets the default value to the empty string. Selecting the "No default or computed value" radio button continues to set the default value to null. Note that either selection sets the default value to null for non-character type columns.

CR:340733

CR Number:   340733 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1245 26 Nov 2003 Fixed 9.0.1 1706 26 Nov 2003 Fixed Description From the Domain wizard, it was not possible to create a domain based on a character type with the empty string as the default value. Now, selecting the "This domain has a default value" check box and the "User-defined" radio button, and leaving the text field empty sets the default value to the empty string. Clearing the "This domain has a default value" check box continues to set the default value to null. Note that either selection sets the default value to null for domains based on non-character types.

CR:340736

CR Number:   340736 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 1706 28 Nov 2003 Fixed Description A subquery predicate can be deferred past a Sort operation if a TOP N clause is present. This allows the predicate to be evaluated only for enough rows to satisfy the TOP N clause instead of for every row in the sort. For example, the following query could defer predicate evaluation until after a sort operation (if the User_estimates option is set to 'On'): select TOP 4 D.dept_id, D.dept_head_id, E.emp_id, E.emp_fname, E.dept_id from department D, employee E where D.dept_id = E.dept_id and E.emp_fname = ( select min(E2.emp_fname) from employee E2 where (D.dept_head_id = E2.emp_id,100) ) order by D.dept_id, E.emp_id Prior to 9.0.1, a "Sort Top N" would not be constructed if a predicate was being deferred in this way. In 9.0.1, this was inadvertently changed, leading to a correctness problem: only N rows are returned from the "Sort Top N", and the deferred predicate eliminates some of these. Now, the predicate is associated with the Sort Top N itself. This gives correct results with better performance than 9.0.0: the predicate is only evaluated for the rows that are lower than one of the N previously fetched rows, and the more efficient Sort Top N is used.

CR:340741

CR Number:   340741 Product Name:   UltraLite Product Component:   Native UltraLite for Java Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1245 26 Nov 2003 Fixed 9.0.1 1706 26 Nov 2003 Fixed Description With UltraLite dynamic SQL, it was possible to crash when a GROUP BY clause had several expressions. This has been corrected.

CR:340742

CR Number:   340742 Product Name:   UltraLite Product Component:   Native UltraLite for Java Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1245 26 Nov 2003 Fixed 9.0.1 1706 26 Nov 2003 Fixed Description On some platforms, when using UltraLite dynamic SQL, the LOCATE function may have returned an incorrect result. This has been fixed.

CR:340743

CR Number:   340743 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2245 08 Mar 2004 Fixed 9.0.1 1831 09 Mar 2004 Fixed 9.0.0 1285 09 Mar 2004 Fixed 8.0.3 4943 09 Mar 2004 Fixed 8.0.2 4391 09 Mar 2004 Fixed Description If a LOAD TABLE statement was executed on a global temporary table, an exclusive lock was left on the table until a COMMIT was executed. Other connections attempting to reference the table for the first time would have been blocked until the lock was released. Now, executing a LOAD TABLE statement will cause a COMMIT to be executed at the end of the statement, releasing the lock. If a global temporary table was created with ON COMMIT DELETE ROWS, an error will be given on an attempt to use LOAD TABLE with that table.

CR:340788

CR Number:   340788 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 1710 01 Dec 2003 Fixed 9.0.0 1249 01 Dec 2003 Fixed Description Dropping a named column CHECK constraint by executing an ALTER TABLE statement with a CHECK NULL clause, would have caused a server crash. For example: ALTER TABLE t1 MODIFY c1 CONSTRAINT check1 CHECK NULL This has been fixed.

CR:340797

CR Number:   340797 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1706 27 Nov 2003 Fixed 9.0.0 1245 27 Nov 2003 Fixed 8.0.3 4851 27 Nov 2003 Fixed 8.0.2 4349 27 Nov 2003 Fixed 7.0.4 3506 27 Nov 2003 Fixed Description Some connection parameter values from the dbisqlc connection dialog were being missed, including the CommLinks parameter. This would have caused connections to a remote server initiated via the connection dialog to fail. No -c command line option connection parameter were ignored, nor were those from the CONNECT USING statement. Connection parameters other than the following were ignored by the connection dialog: UID, PWD, CON, DBN, DBF, DBS, ENG, START, AUTOSTOP, INTEGRATED, DSN. This problem has been fixed.

CR:340808

CR Number:   340808 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2201 24 Dec 2003 Fixed 8.0.3 4878 24 Dec 2003 Fixed Description If a SQL Remote, DBMLSync or LTM truncation point exists, dblog will no longer remove the transaction log, unless the corresponding ignore command-line option (-ir, -is and -il respectively) is also supplied. This behaviour is also true of calls made to DBChangeLogName through the DBTools interface.

CR:340813

CR Number:   340813 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1704 26 Nov 2003 Fixed 9.0.0 1245 26 Nov 2003 Fixed 8.0.3 4849 26 Nov 2003 Fixed 8.0.2 4348 26 Nov 2003 Fixed Description If a table or column name contained the percent character "%", the LOAD TABLE statement in the reload.sql may have been incorrect. There was also a chance that the dbunload utility could have crashed. This has been fixed.

CR:340815

CR Number:   340815 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 4351 26 Nov 2003 Fixed 8.0.3 4856 26 Nov 2003 Fixed 9.0.0 1249 26 Nov 2003 Fixed 9.0.1 1710 26 Nov 2003 Fixed 7.0.4 3510 09 Jan 2004 Fixed Description Remote Data Access could have caused a server crash, if a large data value was provided. This has been fixed.

CR:340818

CR Number:   340818 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 1706 28 Nov 2003 Fixed Description If the optimizer chose a Group-By-Hash join, (shown as GrByH in the graphical plan), to compute a GROUP BY containing a distinct aggregate, and the input contained no rows, the server could have leaked memory, although the leaked memory would have been no more than one page. This memory is now released.

CR:340835

CR Number:   340835 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1706 27 Nov 2003 Fixed 9.0.0 1245 27 Nov 2003 Fixed 8.0.3 4851 27 Nov 2003 Fixed 8.0.2 4349 27 Nov 2003 Fixed Description If an application attempted to set a parameter to be an empty binary array (eg. setObject( 1, new byte[0] )), the subsequent executeQuery or executeUpdate call would have resulted in a Java exception. This problem has been fixed.

CR:340844

CR Number:   340844 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 1245 18 Feb 2004 Fixed 9.0.0 1245 27 Nov 2003 Fixed Description Calling the soundex() function could have crashed the server. This would have occurred when passing a string larger than the pagesize of the database. An error is now returned indicating that the string parameter is too long.

CR:340902

CR Number:   340902 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 1813 17 Dec 2003 Fixed 9.0.0 1253 17 Dec 2003 Fixed 8.0.3 4871 17 Dec 2003 Fixed 8.0.2 4358 17 Dec 2003 Fixed Description An UltraLite application, running on Palm devices, would have failed to synchronize new or updated rows after the following sequence: - PalmExit - drop database - PalmLaunch Switching to another applcation, or a reset at any point after the PalmExit, would avoid (or recover from) this condition. This has been fixed.

CR:340911

CR Number:   340911 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1705 28 Nov 2003 Fixed Description When a problem is encountered during self-registration, by the performance monitoring DLLs (dbctrs9.dll and dbmlctrs9.dll), either during installation or by running regsvr32, a message box will now be displayed showing what failed. Previously there was only a single generic error message.

CR:340912

CR Number:   340912 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 1707 27 Nov 2003 Fixed 9.0.0 1246 27 Nov 2003 Fixed 8.0.3 4852 27 Nov 2003 Fixed 8.0.2 4350 27 Nov 2003 Fixed Description The domain types, datetime, image, money, oldbit, smalldatetime, smallmoney, sysname, text, uniqueidentifierstr and real were not supported by the AsaClient. The AsaDbType enum has now been modified to add these domain types.

CR:340915

CR Number:   340915 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 1711 02 Dec 2003 Fixed 9.0.0 1250 02 Dec 2003 Fixed 8.0.3 4857 02 Dec 2003 Fixed 8.0.2 4352 02 Dec 2003 Fixed Description For read only queries, the server did not examine the definition of computed columns, which could have caused the server to omit some possible optimizations. For example: CREATE TABLE T(x int, y int compute(F(x))) -- F(x) is a User Defined Function SELECT x, F(x) from T for read only The above query can be executed as 'SELECT x, y from T' because y is a computed column whose value is pre-computed as F(x). The transformed query eliminates the need to compute F(x) for each value of x in T and, is therefore more efficient. The server now makes this transformation for read only queries.

CR:340916

CR Number:   340916 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 1704 28 Nov 2003 Fixed 9.0.0 1245 28 Nov 2003 Fixed 8.0.3 4851 28 Nov 2003 Fixed 8.0.2 4350 28 Nov 2003 Fixed 7.0.4 3507 28 Nov 2003 Fixed Description Dynamic cache resizing did not work on AIX 5.x platforms. This has been corrected.

CR:340919

CR Number:   340919 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1707 02 Dec 2003 Fixed 9.0.0 1247 02 Dec 2003 Fixed 8.0.3 4852 02 Dec 2003 Fixed 8.0.2 4350 02 Dec 2003 Fixed Description After disconnecting, clicking the Connect menu item to bring up the Connect dialog would have had the fields populated with all of the connection information used by the previous connection, including the password. Now, the password field is left blank.

CR:340921

CR Number:   340921 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 1710 03 Dec 2003 Fixed 8.0.3 4856 03 Dec 2003 Fixed Description Trying to save to a file with an incorrect or unspecified extension, either with the -o command line option or with the File Save dialog, would have resulted in an error message, but a zero length file would also have been created. With an unspecified extension, the error message would have been incorrect. When using the -o option, the error reporting an incorrect name would not have been displayed until the monitoring session ended. The MobiLink Monitor would then have closed, without giving the option to save the session. These problems have now been fixed.

CR:340942

CR Number:   340942 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 1707 02 Dec 2003 Fixed 9.0.0 1247 02 Dec 2003 Fixed Description From the Column property sheet, it was not possible to specify a default value, other than a literal string, for a character column. For example, it was not possible to use a built-in function with a constant expression, such as sqrt(2) as the default value if the column's type was character, varchar or long varchar, since the expression would always have been single-quoted and thus, would have been treated as a literal string. Similarly, it was not possible to specify a non-literal string value default for a domain with a character base type, from the Domain wizard . Both of these problems have now been corrected. A literal string check box has been added to the Column property sheet and the Domain wizard, so whether or not the default value should be treated as a literal string can be specified. The check box is selected by default for character columns and domains with a character base type. When selecting the check box, enclosing the default value text in single-quotes is not required, nor is it required to double-up embedded single quotes and backslashes within the text, since this will be done, (this is the historical behaviour). By clearing the check box, the automatic quoting and escaping behaviour will be turned off and the specified default value text will be passed as is to the server.

CR:340958

CR Number:   340958 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 1707 02 Dec 2003 Fixed 9.0.0 1248 02 Dec 2003 Fixed 8.0.3 4853 02 Dec 2003 Fixed 8.0.2 4350 02 Dec 2003 Fixed Description An InvalidCastException would have been thrown when passing a guid string to an Uniqueidentifier parameter. This is now fixed.

CR:340959

CR Number:   340959 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 1707 02 Dec 2003 Fixed 9.0.0 1121 02 Dec 2003 Fixed Description When running the Console utility, (ie dbconsole) on Unix platforms, clicking the Help button on the Options dialog, (File->Options), would have done nothing. This has been fixed.

CR:340960

CR Number:   340960 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 1707 01 Dec 2003 Fixed Description The graphical plan was displaying some non-ASCII characters as '.'. This has been fixed, all characters are now displayed as is except those less than 0x20, which are displayed escaped as '\xNN'.

CR:340961

CR Number:   340961 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 1710 02 Dec 2003 Fixed 9.0.0 1249 02 Dec 2003 Fixed Description In a case where an expression was used both in the select list and in a local predicate on a procedure call, and was not exactly a procedure column, the value of the expression in the result could have been incorrect. For example, the following query demostrates the problem: select cast(value as varchar(25)) as pvalue from sa_eng_properties() where pvalue ='1' This has been fixed by materializing the expression along with the procedure columns.

CR:340963

CR Number:   340963 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 1707 01 Dec 2003 Fixed 9.0.0 1122 01 Dec 2003 Fixed 8.0.3 4853 01 Dec 2003 Fixed 8.0.2 4350 01 Dec 2003 Fixed Description Creating a database with an eight character mirror log name that was specified without an extension, such as 'dbinit foo.db -m foo45678', could have caused a server crash. This has been fixed.

CR:340964

CR Number:   340964 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1707 01 Dec 2003 Fixed 9.0.0 1248 01 Dec 2003 Fixed 8.0.3 4853 01 Dec 2003 Fixed 8.0.2 4350 01 Dec 2003 Fixed Description When saving the graphical plan for a statement which contained one or more backslash characters, the plan details (in the right pane on the "Plan" tab), did not show the correct SQL -- double backslashes in the original SQL were shown collapsed into a single backslash. For example, the plan for: SELECT '\\' was shown in the plan as: SELECT '\' This has been fixed.

CR:340966

CR Number:   340966 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 1710 04 Dec 2003 Fixed 9.0.0 1248 01 Dec 2003 Fixed 8.0.3 4857 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed 7.0.4 3510 22 Jan 2004 Fixed 8.0.1 3149 05 Feb 2004 Fixed Description An error in common code dealing with string parameters to built-in functions could have caused a server crash. This has now been corrected.

CR:340989

CR Number:   340989 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 1710 02 Dec 2003 Fixed 9.0.0 1249 02 Dec 2003 Fixed Description An internal exception would have been reported if a property sheet for a Domain, Ultralite Statement, or Web Service was opened, and the ESCAPE key was pressed, while one of the tabs had focus. This has been fixed.

CR:340992

CR Number:   340992 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 1710 02 Dec 2003 Fixed 9.0.0 1249 02 Dec 2003 Fixed Description When running on an OS with a German locale, the source dialog in the debugger had the buttons truncated when the display size was 800x600. This has been fixed.

CR:341002

CR Number:   341002 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 1710 04 Dec 2003 Fixed 9.0.0 1251 04 Dec 2003 Fixed Description Queries with more than one equijoin, for which not all of the equijoin predicates were inferred, might have returned an incorrect result set. This has been fixed. A simple example is a query with the WHERE clause containing two equijoins "T1.X = T2.X" and "T2.X = T3.X" , for which we cannot infer the third equijoin "T1.X = T3.X" due to the domains of T1.X and T3.X being incompatible.

CR:341015

CR Number:   341015 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 1710 02 Dec 2003 Fixed 9.0.0 1249 02 Dec 2003 Fixed Description Creating a new breakpoint in the Debugger's Breakpoints dialog, without a connection, would have caused an uncaught exception. The New button is now disabled until a connection is made, so that this exception can no longer occur.

CR:341082

CR Number:   341082 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 1711 03 Dec 2003 Fixed 9.0.0 1250 03 Dec 2003 Fixed 8.0.3 4857 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed 7.0.4 3510 09 Jan 2004 Fixed Description Creating a proxy table may have caused a server crash, if the server name in the location clause was very long. This has now been corrected.

CR:341085

CR Number:   341085 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1250 04 Dec 2003 Fixed 8.0.3 4857 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed Description It was not possible to connect to an ASE or SQL Server database with a userid that did not require a password. This has been fixed so that connections can now be made with userids that have no password.

CR:341100

CR Number:   341100 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 4857 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed 7.0.4 3510 09 Jan 2004 Fixed Description If a FORWARD TO statement was executed, and the server name specified in the statement was very long, there was a possibility it would have caused a server crash. This is now fixed.

CR:341102

CR Number:   341102 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 1711 04 Dec 2003 Fixed 9.0.0 1250 04 Dec 2003 Fixed Description In the Breakpoints dialog, the mnemonic 'E' was used for both the Edit and Enable buttons. This has been fixed so that the mnemonic for the Enable button is now 'b'.

CR:341104

CR Number:   341104 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 1707 02 Dec 2003 Fixed 9.0.0 1248 02 Dec 2003 Fixed 8.0.3 4853 02 Dec 2003 Fixed 8.0.2 4350 02 Dec 2003 Fixed Description An Exception would have been thrown when fetching zero-length long binary column. This is now fixed.

CR:341105

CR Number:   341105 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 1705 02 Dec 2003 Fixed 8.0.3 4851 02 Dec 2003 Fixed Description Compressing an encrypted database now removes any encryption, and marks the (resulting) database as unencrypted. Expanding the compressed database will result in an unencrypted database. A warning is now returned if an encrypted database is compressed through the CREATE COMPRESSED DATABASE statement, or through dbshrink; the warning states that the compressed database is not encrypted.

CR:341106

CR Number:   341106 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 1711 04 Dec 2003 Fixed 9.0.0 1250 04 Dec 2003 Fixed Description If Sybase Central was shutdown, or the plug-in was unloaded, and there was more than one connection open, then not all connections would have been closed. This has been fixed.

CR:341107

CR Number:   341107 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 1711 05 Dec 2003 Fixed 9.0.0 1250 05 Dec 2003 Fixed Description When in Debug mode, putting the cursor before, or at, the current execution line and clicking the "Run To Cursor" toolbar button, would have caused the toolbar "Step Into", "Step Over" and "Step Out" buttons to be disabled. This has been fixed.

CR:341109

CR Number:   341109 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1712 05 Dec 2003 Fixed 9.0.0 1251 05 Dec 2003 Fixed 8.0.3 4857 05 Dec 2003 Fixed 8.0.2 4352 05 Dec 2003 Fixed 7.0.4 3508 05 Dec 2003 Fixed Description The behaviour of an empty connection parameter was changed inadvertently by engineering change 336563. This fix restores the behaviour to be the same as before the change.

CR:341121

CR Number:   341121 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 1712 04 Dec 2003 Fixed 9.0.0 1251 04 Dec 2003 Fixed Description Queries with a subquery, where the right-hand side expression needed to be converted to the domain of the left-hand side expression, (rather than the other way around), may have returned an incorrect result if the conversion resulted in a loss of precision. For example: SELECT * FROM employee WHERE emp_id+0.1 > ALL ( SELECT 1751 from dummy) The problem was that "emp_id+0.1" is a float and "1751" is a smallint, and the conversion from float to smallint loses precision. The fix is to convert the right-hand side expression to the common domain, rather than converting the left-hand side expression to the domain of the right-hand side expression.

CR:341123

CR Number:   341123 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1711 04 Dec 2003 Fixed 9.0.0 1250 04 Dec 2003 Fixed 8.0.3 4857 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed Description Attempting to update or delete rows from a table, when another user had locked the table, would have caused dbisql to hang. Now, an error dialog is displayed that shows which user has the lock.

CR:341221

CR Number:   341221 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 4858 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed Description The ALTER DATABASE statement is documented, and the server correctly parses an ALTER DATABASE statement, but this feature was not implemented until 9.0.0. Now, an ALTER DATABASE statement will return the error "ALTER DATABASE NOT IMPLEMENTED", SQLSTATE 0A000 (SQLCODE -134).

CR:341242

CR Number:   341242 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1712 04 Dec 2003 Fixed 9.0.0 1251 04 Dec 2003 Fixed 8.0.3 4858 04 Dec 2003 Fixed 8.0.2 4352 04 Dec 2003 Fixed 8.0.1 3142 04 Dec 2003 Fixed Description When using SQLProcedureColumns to determine the type and position of a procedure's parameters, the ORDINAL_POSITION of an OUT parameter was always reported as 0, for any and all OUT parameters. For the following procedure: create procedure testargs( in arg1 integer, inout arg2 integer, out arg3 integer ) begin set arg2 = arg1 * arg2; set arg3 = 999; end the ordinal positions for arg1, arg2, and arg3 would have been reported as 1, 2, and 0. This has been corrected and the ordinal positions for arg1, arg2, and arg3 are now reported as 1, 2, and 3.

CR:341244

CR Number:   341244 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 1812 10 Dec 2003 Fixed 9.0.0 1252 10 Dec 2003 Fixed Description If request-level logging was invoked with the option 'SQL+hostvars', either by calling sa_server_option or via the -zr command line option, the calling property('requestlogging') would incorrectly have returned 'NONE'. This has been fixed.

CR:341274

CR Number:   341274 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 1712 04 Dec 2003 Fixed 9.0.0 1251 04 Dec 2003 Fixed Description In the Event wizard, the Event property sheet, and the Translate Log File wizard, when specifying the date, using the up or down arrow keys or clicking the up or down arrow buttons in the year spin box to change the year, the date value would not have been updated. This has been fixed.

CR:341354

CR Number:   341354 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 1714 05 Dec 2003 Fixed 9.0.0 1251 05 Dec 2003 Fixed Description Extraneous debugging messages may have been displayed in the console output by dbmlsrv and dbmlsync, such as: error reading: <number> timeout reading These have been removed. Note that these messages were in addition to normal error messages.

CR:341377

CR Number:   341377 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1714 05 Dec 2003 Fixed 8.0.3 4859 05 Dec 2003 Fixed Description Depending on the platform, the Pause button on the MobiLink Monitor's toolbar could be slightly larger or smaller than the other toolbar buttons. This has been fixed.

CR:341379

CR Number:   341379 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 1740 05 Dec 2003 Fixed 9.0.0 1251 05 Dec 2003 Fixed 8.0.3 4859 05 Dec 2003 Fixed 8.0.2 4353 05 Dec 2003 Fixed Description Creating a table with a unique constraint could have crashed the server, if the default constaint name was long.

CR:341446

CR Number:   341446 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1812 05 Dec 2003 Fixed 9.0.0 1251 05 Dec 2003 Fixed 8.0.3 4860 05 Dec 2003 Fixed 8.0.2 4353 05 Dec 2003 Fixed 8.0.1 3142 05 Dec 2003 Fixed Description A call to SQLNativeSql would have resulted in a truncated string, when the output buffer length was less than twice the length of the input string. This has now been corrected The following C example shows the problem: char sql_stmt_out[24]; strcpy( sql_stmt_in, "select * from customer" ); rc = SQLNativeSql( dbc, sql_stmt_in, SQL_NTS, sql_stmt_out, sizeof( sql_stmt_out ), &len ); The output buffer would have contained only 12 characters (ie 24/2).

CR:341450

CR Number:   341450 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1727 23 Dec 2003 Fixed 8.0.3 4873 23 Dec 2003 Fixed Description If only Sybase Central was selected for installation, it was not possible to connect to a server using the iAnywhere JDBC driver, as the required ODBC files were not installed. Selecting Sybase Central alone, will now install the required ODBC files as well.

CR:341458

CR Number:   341458 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.2 2203 07 Jan 2004 Fixed 9.0.1 1815 07 Jan 2004 Fixed 9.0.0 1259 07 Jan 2004 Fixed 8.0.3 4880 07 Jan 2004 Fixed 8.0.2 4362 07 Jan 2004 Fixed 8.0.1 3145 07 Jan 2004 Fixed Description If an ADO application fetched a binary column into a variable of type VARIANT, only 16 bytes would have been stored. Also, for a non-variant DBTYPE_ARRAY variable, the length was incorrectly set to zero, which meant that no data would have been copied. These problems have now been fixed. Workaround Description  None.

CR:341464

CR Number:   341464 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 1715 08 Dec 2003 Fixed 9.0.0 1251 08 Dec 2003 Fixed Description When modifying a procedure, view, trigger or event in the right-pane of the main window, after saving the changes the caret position and text selection would have been lost and the editor's scroll positions would have been reset to the top and left. This has been fixed. Now, the caret position, text selection and scroll positions are retained after the changes are saved.

CR:341469

CR Number:   341469 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1719 09 Dec 2003 Fixed 9.0.0 1252 09 Dec 2003 Fixed Description When analysing queries containing inequality predicates, where a column involved in the predicate was the ninth or greater column of a table, the Index Consultant (both Sybase Central and ISQL) could have caused a server crash. It may also have caused server assert failures to occur during tuning; assertion 101412 has been observed, and others may have been possible, depending on cache contents when the consultant was run. This has been fixed. A workaround is to remove queries from the workload containing inequality predicates over the 9th or greater columns of the table.

CR:341484

CR Number:   341484 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 1715 08 Dec 2003 Fixed 9.0.0 1251 08 Dec 2003 Fixed 8.0.3 4860 08 Dec 2003 Fixed 8.0.2 4353 08 Dec 2003 Fixed Description When using the AsaDataAdapter, the Fill method would not have returned when the SelectCommand.Cancel method was called. This problem has been fixed.

CR:341501

CR Number:   341501 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 1715 08 Dec 2003 Fixed 9.0.0 1251 08 Dec 2003 Fixed Description When viewing an Index Consultant analysis in Sybase Central, the Query Details pane for a query would have had the With Virtual Indexes button disabled, even if a virtual index existed. When clicking the Without Virtual Indexes button, the Plan Viewer would have disabled the button to Add Virtual Indexes to the plan. Both of these buttons are now enabled properly.

CR:341508

CR Number:   341508 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 1715 08 Dec 2003 Fixed 9.0.0 1251 08 Dec 2003 Fixed Description When viewing an Index Consultant analysis in Sybase Central, the Query Details pane for a query would have had incorrect information in the 'Virtual Indexes used for query' table. The columns of this table have headers that indicate that each row should contain Table/Columns/Type, however the data inserted into the table consisted of Creator/Table/Clustered. This has been fixed and the table now contains the correct data.

CR:341512

CR Number:   341512 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 1715 08 Dec 2003 Fixed 9.0.0 1122 08 Dec 2003 Fixed Description After installation, if Sybase Central was opened and closed without going into debug mode, invalid splitter bar positions for the panes in the debugger details panel would have been saved. The next time Sybase Central was started and put into debug mode, the splitter bar position would have been immediately to the left instead of the proper default position. This has now been fixed.

CR:341528

CR Number:   341528 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   4.2.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1715 08 Dec 2003 Fixed 9.0.0 1121 08 Dec 2003 Fixed Description When in the Editor, moving the cursor to the end of a document and searching up, would have finished without error, but would not have found the texted being searched for. This is now fixed.

CR:341616

CR Number:   341616 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 1812 09 Dec 2003 Fixed 9.0.0 1812 09 Dec 2003 Fixed 8.0.3 4863 09 Dec 2003 Fixed 8.0.2 4354 09 Dec 2003 Fixed Description If the server ran out of memory, it could have crashed instead of reporting an error. On Windows CE, the server would have started without errors, but would not have accepted any connections if the system was low on memory. This has been fixed so that the server reports out of memory errors.

CR:341633

CR Number:   341633 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 1718 09 Dec 2003 Fixed 9.0.0 1251 09 Dec 2003 Fixed 8.0.3 4863 09 Dec 2003 Fixed 8.0.2 4354 09 Dec 2003 Fixed Description Using a writefile could have lead to a corrupted database. That is the virtual database represented by the writefile plus original database would be corrupt, not the original database or the writefile itself. To cause the corruption, the server must have been started on the writefile, a virtual dbspace expanded, the server shutdown and restarted, then the virtual dbspace expanded again. The underlying original database must also have been created with 8.0.0 or later. This problem has now been fixed.

CR:341648

CR Number:   341648 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 1718 10 Dec 2003 Fixed 9.0.0 1252 10 Dec 2003 Fixed 8.0.3 4863 10 Dec 2003 Fixed 8.0.2 4354 10 Dec 2003 Fixed Description Extracting into a new database would have resulted in a crash (if using dbxtract -an) or have caused Sybase Central to exit immediately without error, if there were no tables to be extracted. This has been fixed.

CR:341655

CR Number:   341655 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 1719 17 Dec 2003 Fixed 9.0.0 1253 17 Dec 2003 Fixed 8.0.3 4870 17 Dec 2003 Fixed 8.0.2 4358 17 Dec 2003 Fixed Description The graphical plans for queries containing temporary tables were being constructed incorrectly; any subtree containing a scan node over a temporary table would have been terminated at that point, with the scan node (sequential or index) for the temporary table also missing. This has been fixed.

CR:341661

CR Number:   341661 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 1718 11 Dec 2003 Fixed 9.0.0 1111 11 Dec 2003 Fixed Description When selecting the Data tab of a table, in order to view the data, not all the rows would have been shown. This has been fixed.

CR:341718

CR Number:   341718 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1812 15 Dec 2003 Fixed 9.0.0 1253 15 Dec 2003 Fixed 8.0.3 4866 15 Dec 2003 Fixed 8.0.2 4355 15 Dec 2003 Fixed 7.0.4 3509 15 Dec 2003 Fixed Description If the INPUT INTO statement is run with a FORMAT clause and the table does not exist, for some formats a table is created prior to loading the date. When executed via DBISQLC, the CREATE TABLE statement generated would have failed with a syntax error, if the language setting for ASA was anything other than EN (english). This has been fixed. Note, this problem did not happen with DBISQL. Workaround Description  Use DBSIQL JAVA

CR:341737

CR Number:   341737 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1719 10 Dec 2003 Fixed 9.0.0 1252 10 Dec 2003 Fixed Description When the JDBC driver translated UTF8 data to Unicode, it made the appropriate Java call, but instaed of asking for translation from UTF8 to Unicode, it asked for ASCII to Unicode. Most of the time this did not cause a problem, but when the MobiLink server was started with the -vt switch, (which displays the SQL statements that are being executed by the ODBC driver), these statements could have been displayed incorrectly. This has been corrected. Note that the problem was only a display problem and only occurred on Unix platforms. The correct SQL statements were executed by the ODBC driver.

CR:341757

CR Number:   341757 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1719 09 Dec 2003 Fixed 9.0.0 1252 09 Dec 2003 Fixed 8.0.3 4864 09 Dec 2003 Fixed 8.0.2 4355 09 Dec 2003 Fixed Description Synch stream errors are reported by the MobiLink server when detected during a synchronization. If an error was detected and reported, that same error would have been reported for all subsequent synchronizations that had a stream error, until the MobiLink server was restarted. Note, the fact that an error was being reported was legitimate, it was the reason for the error that may have been erroneous.

CR:341760

CR Number:   341760 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 1719 10 Dec 2003 Fixed 9.0.0 1252 10 Dec 2003 Fixed Description When running the Index Consultant, potential recommended indexes could have been improperly enabled/disabled during tuning. This was especially likely in Sybase Central where several tuning phases were performed. It appears that the only consequence was poorer quality of index recommendations. This is now fixed.

CR:341761

CR Number:   341761 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 1812 11 Dec 2003 Fixed 9.0.0 1253 11 Dec 2003 Fixed 8.0.3 4864 11 Dec 2003 Fixed 8.0.2 4355 11 Dec 2003 Fixed Description If an application that connected to a server via shared memory, did not disconnect before closing, the message "Disconnecting shared memory client, process id not found" could have been displayed multiple times for a single connection in the server console. This problem was more likely to have occurred if all the server tasks were busy processing requests. This has been fixed so the message is only displayed once per connection.

CR:341762

CR Number:   341762 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1726 19 Dec 2003 Fixed 9.0.0 1253 19 Dec 2003 Fixed Description Rerunning the install, or applying an EBF or Maintenance Patch, would have re-enabled the Sybase Central and ISQL fast launchers, even if they had previously been disabled. This has been fixed, the installer will preserve the state of the fast launcher.