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

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

CR:304262

CR Number:   304262 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4653 01 May 2003 Fixed 8.0.2 4249 01 May 2003 Fixed 8.0.1 3113 01 May 2003 Fixed 7.0.4 3475 25 Jul 2003 Fixed Description If more than about 200 characters were specified in the parameters text area of a service's property sheet, then the next time the property sheet was opened, the parameters would be empty. This has been fixed.

CR:304465

CR Number:   304465 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4565 09 Jan 2003 Fixed 8.0.2 4200 09 Jan 2003 Fixed 8.0.1 3092 09 Jan 2003 Fixed Description The system procedures sp_tsql_environment and sp_reset_tsql_environment were setting options using option names that did not match the case in the SYSOPTION system table. This caused problems with databases created with certain collations. These procedures have now been changed to use option names with a case matching those in the SYSOPTION table. Workaround Description  Change case in the systemprocedures e.g. instead of SET TEMPORARY OPTION AUTOMATIC_TIMESTAMP='OFF'; use SET TEMPORARY OPTION Automatic_timestamp='OFF';

CR:304478

CR Number:   304478 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4559 06 Jan 2003 Fixed 8.0.2 4098 06 Jan 2003 Fixed 8.0.1 3090 06 Jan 2003 Fixed 8.0.0 2359 06 Jan 2003 Fixed Description When connecting to a busy Mobilink server using HTTP or HTTPS, the communication error 65 (Unable to connect a socket) could have occurred. A failed connect attempt caused an error condition to be set that prevented retries. This has been corrected.

CR:304495

CR Number:   304495 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 4559 06 Jan 2003 Fixed 8.0.2 4098 06 Jan 2003 Fixed Description When using DBISQL and the JDBC-ODBC bridge any attempts to execute a batch with variying multiple result sets would have failed. For example: begin select 1,2; select 3 end This problem has now been fixed.

CR:304512

CR Number:   304512 Product Name:   SQL Remote for SQL Anywhere Product Component:   Database Tools Interface Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4563 10 Jan 2003 Fixed 8.0.2 4099 10 Jan 2003 Fixed 8.0.1 3092 10 Jan 2003 Fixed 8.0.0 2360 10 Jan 2003 Fixed Description When an offline transaction log ended with a zero-byte string for the last valid log operation, SQL Remote could have reported "Log operation at offset X0 has bad data at offset X1" (where X1 > X0 ), if this last log operation was on the last log page, or "Transaction log file file_name1 overlaps with log file file_name2", if this last log operation was not on the last log page (log files contain one or more unused pages). This problem could have happened in DBMLSync and DBLTM as well. The problem has been fixed. Workaround Description  Workaround is to re-extract all 12 users.

CR:304559

CR Number:   304559 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 4675 26 May 2003 Fixed 8.0.2 4259 26 May 2003 Fixed 8.0.1 3116 26 May 2003 Fixed Description When attempting to change the list of filtered owners for a WIN_LATIN5 (Turkish) database, the error "ASA Error -143: Column '@p0' not found" would have been displayed. This has been fixed.

CR:304584

CR Number:   304584 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4547 06 Jan 2003 Fixed 8.0.2 4088 06 Jan 2003 Fixed Description Starting the Mobilink server with two instances of an HTTP based stream could have caused the stream to behave erratically. This is now fixed. For example: dbmlsrv8 -c ... -x http {port=22222} -x http {port=88888}

CR:304604

CR Number:   304604 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 4560 07 Jan 2003 Fixed 8.0.2 4098 07 Jan 2003 Fixed Description Queries containing FULL OUTER JOINs and at least five (5) quantifiers may have suffered from a poor access plan. In particular, in such cases the ASA optimizer would only have considered nested-loop full outer join (JNLFO) for each FULL OUTER JOIN in the query. This problem has been corrected.

CR:304698

CR Number:   304698 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4563 07 Jan 2003 Fixed 8.0.2 4099 07 Jan 2003 Fixed 8.0.1 3092 07 Jan 2003 Fixed 7.0.4 3406 07 Jan 2003 Fixed Description If the 8.0 ASAprov oledb provider was used to connect to a database running on an ASA 7.0 server or the codepage for the database character set was not installed, the connection will fail with the error: "The system does not support conversion between Unicode and the requested character set, substituting the current ansi codepage". This is now treated as a warning instead of an error.

CR:304715

CR Number:   304715 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) 8.0.3 4563 10 Jan 2003 Fixed 8.0.2 4099 10 Jan 2003 Fixed 8.0.1 3092 10 Jan 2003 Fixed Description If errors occurred during upload DELETEs (for example, deleting rows that do not exist in the consolidated database) and the MobiLink server was running in a multiple-row mode (the command line switch -s X was used with X > 1 or no -s was specified), it may not have updated the progress offset in the consolidated database, but it would have informed the client to update the progress offset in the remote database. Therefore, the progress offset in the consolidated database would have been smaller than that in the remote database after the synchronization. In the next synchronization, DBMLsync would have complained with the error "mismatch progress offset" and then uploaded the transactions that have been uploaded in previous synchronization again, if all the previous transaction log files were still available. However, if "Delete_old_logs" was on in the remote database, the previous transaction log files may have been deleted, and then DBMLsync would have complained with "missing transaction log(s) before file log_file_name". These problems are now fixed.

CR:304766

CR Number:   304766 Product Name:   SQL Remote for SQL Anywhere Product Component:   Database Tools Interface Status:   Closed OS:   Solaris Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4552 24 Jan 2003 Fixed 8.0.2 4206 27 Jan 2003 Fixed 8.0.1 3096 27 Jan 2003 Fixed 8.0.0 2360 27 Jan 2003 Fixed 7.0.4 3411 25 Jun 2003 Fixed Description If the connection that was used for processing incoming messages was dropped, SQL Remote for ASA would have gone into an infinite loop display the error: "SQL statement failed: (-101) Not connected to a database". The errors SQLE_CONNECTION_TERMINATED and SQLE_NOT_CONNECTED were not handled properly. This problem is now fixed. Workaround Description  *** Wednesday, January 08, 2003 10:19:34 AM *** rdomarat *** Stop dropping connections....

CR:304839

CR Number:   304839 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Solaris Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4630 07 Apr 2003 Fixed Description Using the dbunload utility with the -ar (or -an) and -o <outputfile> command line options would successfully have rebuilt a database, but the output messages would still have appeared on the console and not have been placed in the specified output file. This is now fixed.

CR:304918

CR Number:   304918 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 4564 10 Jan 2003 Fixed 8.0.2 4200 10 Jan 2003 Fixed Description Attempting to call a Java method immediately after upgrading a database to add Java support, caused a misleading error message "not a public Java class." The documentation of the ALTER command states "If you add Java in the database, you must restart the database before it can be used." BUT this could be missed while working through the "Invoice sample." The message has been changed to now say "The database needs to be restarted for this Java related command."

CR:304950

CR Number:   304950 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4565 13 Jan 2003 Fixed 8.0.2 4200 13 Jan 2003 Fixed Description During a ULSynchronize call, the ul_synch_info output fields were not necessarily set. This would only have been a problem if ULInitSynchInfo was not called before each synchronization (because ULInitSynchInfo clears all output fields), but the documentation did not explicitly state this was a requirement. Now all output fields are always set, so it's possible to call ULSynchronize twice without an intermediate ULInitSynchInfo call if desired.

CR:304960

CR Number:   304960 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) 8.0.3 4566 13 Jan 2003 Fixed 8.0.2 4201 13 Jan 2003 Fixed 7.0.4 3408 13 Jan 2003 Fixed Description When making a connection to an ASA remote server, via ODBC, the Remote Data Access layer now names the remote connection ASACIS_? where "?" gets replaced with the connection id of the local connection. This feature is useful if a customer needs to drop the remote connection in order to cancel a remote request.

CR:304975

CR Number:   304975 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 4566 13 Jan 2003 Fixed 8.0.2 4201 13 Jan 2003 Fixed Description When attempting to create a proxy table to a MS SQL Server table that had a uniqueidentifier column, the Remote Data Access layer would fail with an unsupported datatype error. As of this change, the proxy table now successfully gets created with the uniqueidentifier column being mapped to a local column with a user-defined data type of uniqueidentifierstr, who's base thpe is char(36). Hence querying the uniqueidentifierstr column will force the SQL Server ODBC driver to convert the uniqueidentifier column to a string. Users can then use strtouuid to map the uniqueidentifiersrt to a uniqueidentifier. The sa_migrate scripts have also been modified such that migrating a SQL Server table with a uniqueidentifier column will result in creating a base table that also has a uniqueidentifier column. The migrate scripts will handle converting the uniqueidentifiersrt to a uniqueidentifier prior to inserting the value into the base table.

CR:305093

CR Number:   305093 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) 8.0.3 4569 22 Jan 2003 Fixed 8.0.2 4205 22 Jan 2003 Fixed 8.0.1 3096 22 Jan 2003 Fixed 7.0.4 3411 22 Jan 2003 Fixed Description Dbmlsync would have incorrectly deleted rows from the download stream which had NULL foreign key values, if all of the following were true: - table T contained a foreign key and one or more of the columns of row R involved in the FK was NULL. - another row, R2, existed in the download stream that dbmlsync had to delete, due to a legitimate RI violation, involving the same foreign key in which R had a NULL value. This behaviour has been corrected. Workaround Description  none

CR:305107

CR Number:   305107 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 07 Feb 2003 Fixed 8.0.2 4212 07 Feb 2003 Fixed 8.0.1 3099 07 Feb 2003 Fixed 7.0.4 3416 07 Feb 2003 Fixed Description When the provider copied column values to its data buffer, a column could have been partially overwritten by a subsequent column, if an intervening column was the empty string. This has been fixed.

CR:305153

CR Number:   305153 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1100 18 Jun 2003 Fixed 8.0.3 4699 18 Jun 2003 Fixed 8.0.2 4275 18 Jun 2003 Fixed 7.0.4 3466 18 Jun 2003 Fixed 8.0.1 3120 19 Jun 2003 Fixed Description If an integrated logon was invalid (ie the logon request was coming from a machine on a different domain and cannot be properly verified) then the connection would seem to have succeeded even though the client would eventually time out. The problem has been resolved and a proper error message is now returned immediately.

CR:305297

CR Number:   305297 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Jan 2003 Fixed Description When rebuilding a database into a new database with a different collation, statistics for string columns will no longer be reloaded

CR:305313

CR Number:   305313 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 4568 16 Jan 2003 Fixed 8.0.2 4203 16 Jan 2003 Fixed 8.0.1 3095 16 Jan 2003 Fixed 8.0.0 2360 16 Jan 2003 Fixed Description The database server could report a "Fatal error: database error" when a sequential scan was being performed on a temporary table using group reads (which requires a database initialized with 8.0.0 or later and the table must be 'large'). The problem would have occurred very infrequently and would only have occurred if the temporary table pages were located near the end of the temporary file. This problem has now been fixed. Workaround Description  Use dbisqlc

CR:305412

CR Number:   305412 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 4568 16 Jan 2003 Fixed 8.0.2 4119 16 Jan 2003 Fixed 8.0.1 3095 16 Jan 2003 Fixed 7.0.4 3410 16 Jan 2003 Fixed Description If a blob column was updated using oledb (eg. through ADO cursors ), the ASA provider could have crashed. This is now fixed.

CR:305454

CR Number:   305454 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4573 28 Jan 2003 Fixed 8.0.2 4208 31 Jan 2003 Fixed 8.0.1 3097 31 Jan 2003 Fixed Description When positioning to the last row in a result set containing only 1 row, the RowCount value reported would have been 0, when it should have been 1. This could have occurred using SQLExtendedFetch() or SQLFetchScroll() with a FetchOrientation of SQL_FETCH_LAST, or with the RDO MoveLast, and a result set with exactly one row. The problem has been fixed.

CR:305469

CR Number:   305469 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4567 15 Jan 2003 Fixed 8.0.2 4203 15 Jan 2003 Fixed 8.0.1 3095 15 Jan 2003 Fixed Description In dbmlsync, when the sp_hook_dbmlsync_download_end hook was called, an extra entry with the name 'continue' was being added to the #hook_dict table. The value for this entry was alway FALSE. The entry was unintentional, undocumented and has now been removed.

CR:305477

CR Number:   305477 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4567 16 Jan 2003 Fixed 8.0.2 4107 16 Jan 2003 Fixed Description Database scripts that took longer then the 'contd_timeout' setting could have caused the HTTP link to time-out a connection, which would have caused the synchronization to fail. This has been fixed.

CR:305487

CR Number:   305487 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 4567 15 Jan 2003 Fixed 8.0.2 4106 15 Jan 2003 Fixed 8.0.1 3095 15 Jan 2003 Fixed Description The Import Wizard could have failed to import a file if all of the following conditions were true: - data was being imported into a new table (i.e. the table did not exist before running the Import Wizard), - the file being imported was ASCII, FIXED, or SQL, - the name of a column was changed from the defaults ("Column1", "Column2", etc.) The wizard would have failed with a message saying that Column1 (or whatever the original column name was) could not be found. This problem has now been corrected.

CR:305551

CR Number:   305551 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 15 Jan 2003 Fixed 8.0.2 4201 15 Jan 2003 Fixed Description A new command line switch, "-vp -- show progress offsets", has been added to the MobiLink server. With this command line switch, (-v+ may also be used), the MobiLink server will log the consolidated and remote progress offsets in its output file for each publication in every synchronization. The publications may include those that are explicitly involved in the current synchronization, as well as the ones that are not explicitly involved, but are in the same remote database. If the consolidated progress offsets do not match the remote progress offsets, the MobiLink server will print these offsets in its output file, no matter whether this switch is used or not.

CR:305568

CR Number:   305568 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows CE 2.11 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4565 15 Jan 2003 Fixed 8.0.2 4201 15 Jan 2003 Fixed 8.0.1 3093 15 Jan 2003 Fixed Description Since 8.0.0 we have shipped dbtool8.dll and dbmlsync.exe for CE. The dbtool8 DLL contained most of the logic for dbmlsync and the executable just did command line processing, then called the DLL. The dbmlsync executable is now linked against a static library containing the same code that goes into dbtool8.dll, resulting in an executable that no longer depends on the DLL and consumes about 240K less memory. The dbtool8 DLL for CE will continue to be shipped, as it is required by dbremote and can be used through the dbtools interface to programatically access dbmlsync's functionality

CR:305630

CR Number:   305630 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4106 16 Jan 2003 Fixed 8.0.3 4568 16 Jan 2003 Fixed 9.0.0 499 16 Jan 2003 Fixed Description When run against a database initialized with a Turkish collation sequence, dbmlsync would have failed to initialize the TCPIP communication stream. The error returned would be: "Invalid communication type: 'tcpp'". TCPIP should now initalize correctly.

CR:305634

CR Number:   305634 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.3 4568 16 Jan 2003 Fixed 8.0.2 4204 16 Jan 2003 Fixed 8.0.1 3095 16 Jan 2003 Fixed Description When building the upload stream dbmlsync may have displayed a message box with the caption "Assertion Failure" and the text "File 'mergeupd.c' at line #873. Try to enter debugger?", (the line number in the text of the message might have varied). This message would have been reported if the extended option SendTriggers was set to 'off' (this is the default), a row that belonged to one of the publications being synchronized was deleted, then inserted inside of a trigger then deleted again. This has now been fixed.

CR:305678

CR Number:   305678 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 4568 16 Jan 2003 Fixed 8.0.2 4108 16 Jan 2003 Fixed Description A request to a remote server, that is taking a long time, can now be cancelled provided the remote class is ODBC based. If the cancellation is successful, control will be returned to the client with an appropriate error message; if on the other hand the request can not be cancelled, then the engine will continue to wait until the request completes.

CR:305784

CR Number:   305784 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) 8.0.2 4208 29 Jan 2003 Fixed 8.0.1 3097 29 Jan 2003 Fixed 8.0.3 4574 29 Jan 2003 Fixed 9.0.0 517 29 Jan 2003 Fixed Description When building an upload, if dbmlsync encountered a certain sequence of operations for a row being uploaded, it could have uploaded an incorrect operation on that row, created an invalid upload stream, or displayed a message box with the caption "Assertion Failure" and the text "File 'mergeupd.c' at line #873. Try to enter debugger?". The line number in the text of the message would have varied. The sequences that could have caused this problem were, (although it might not reproduce consistently): - insert a row R, stop synchronization delete, delete row R, start synchronization delete, insert a row with the same primary key as R - if the dbmlsync extended option "SendTriggers" was off, insert a row R, delete row R inside of a trigger, insert a row with the same primary key as R - if the dbmlsync extended option "SendTriggers" was off, insert a row R, update row R inside trigger so that it belonged to no publication, update row R so that it again belongs to the publication This is now fixed.

CR:305817

CR Number:   305817 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 4569 20 Jan 2003 Fixed 8.0.2 4108 20 Jan 2003 Fixed Description Pressing the ESCAPE key while a menu was open did not close it. Now it does.

CR:305860

CR Number:   305860 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 4569 17 Jan 2003 Fixed 8.0.2 4204 17 Jan 2003 Fixed Description If a result set had a column of type unsigned smallint, unsigned int or unsigned bigint, and the value of the column was greater than the largest smallint, int or bigint (respectively), then retrieving the column using the ASA JDBC-ODBC bridge would have resulted in a "value out of range error". This problem has now been fixed.

CR:305871

CR Number:   305871 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 4569 20 Jan 2003 Fixed 8.0.2 4108 20 Jan 2003 Fixed 8.0.1 3095 20 Jan 2003 Fixed 8.0.0 2360 20 Jan 2003 Fixed Description If an attempt is made to execute a SQL statement after disconnecting from a database, dbisql will attempt to reopen the connection and execute the statement. This reopening of the connection would have failed if the connection auto-started the . That is, if a DSN, FDSN, or DBF connection parameter was given. This has now been fixed.

CR:305885

CR Number:   305885 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1068 26 May 2003 Fixed Description If a connection belonging to the plug-in was closed outside of Sybase Central, either due to a DROP CONNECTION statement being executed on another connection or the server being shutdown, the error "Connection already closed" would have been displayed on subsequent attempts to execute a statement and the user was required to explicitly disconnect the already closed connection. Now, when a closed connection exception is detected, the connection is automatically removed from the plug-in's list of registered connections. In addition, any other connections to databases on the same server are tested to see whether the connections are still open. Note that closed connections are only removed if the main viewer window has focus and there are no unsaved changes. If a property sheet, wizard or dialog is opened, then the closed connection messages will continue to be displayed until the main viewer window is active again.

CR:305902

CR Number:   305902 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 4569 20 Jan 2003 Fixed 8.0.2 4204 20 Jan 2003 Fixed 8.0.1 3095 20 Jan 2003 Fixed 7.0.4 3410 20 Jan 2003 Fixed Description It was possible that any of the following commands could have written the OPTION clause incorrectly to the database: CREATE SYNCHRONIZATION USER, ALTER SYNCHRONIZATION USER, CREATE SYNCHRONIZATION SUBSCRIPTION, ALTER SYNCHRONIZATION SUBSCRIPTION, CREATE SYNCHRONIZATION SITE, ALTER SYNCHRONIZATION SITE, CREATE SYNCHRONIZATION DEFINITION, ALTER SYNCHRONIZATION DEFINITION, CREATE SYNCHRONIZATION TEMPLATE, ALTER SYNCHRONIZATION TEMPLATE. This has now been fixed.

CR:305913

CR Number:   305913 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 4552 27 Jan 2003 Fixed 8.0.2 4206 27 Jan 2003 Fixed Description If the following procedure was created using Sybase Central, a syntax error would result when trying to rebuild the database: create procedure mytest() as select 1 go Note that the procedure ends with a SELECT statement having no FROM clause. The server treats the "go" as an alias for the last SELECT list item; otherwise, a syntax error would be given when trying to save the procedure definition in Sybase Central. The "go" is included in the preserved-source string and causes a syntax error on rebuild.This problem is similar to issue 302757. The trailing "go" is now removed when saving the procedure definition. . Workaround Description  none

CR:305936

CR Number:   305936 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 4569 21 Jan 2003 Fixed 8.0.2 4108 21 Jan 2003 Fixed Description Clicking the window close button, (the title bar button with an "X" in it), would not have closed the dialogs listed below: - the dialog which reports errors in SQL statements - the data prompt dialog used for the INPUT ... PROMPT statement. This has been fixed now so that the dialogs close.

CR:306021

CR Number:   306021 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 4570 22 Jan 2003 Fixed 8.0.2 4111 22 Jan 2003 Fixed 8.0.1 3096 22 Jan 2003 Fixed 8.0.0 2360 22 Jan 2003 Fixed Description An isolation level 3 scan could have returned null values unexpectedly. This is now fixed.

CR:306023

CR Number:   306023 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4570 21 Jan 2003 Fixed 8.0.2 4206 21 Jan 2003 Fixed 7.0.4 3411 21 Jan 2003 Fixed Description The ASAProv OLEDB provider could have failed when accessed by multiple threads concurrently, with failures more likely to have occurred on multi processor machines than single processor machines. One instance of this failure was the error DB_E_BADTYPENAME(0x80040E30) from ICommandWithParameters::SetParameterInfo. This is now fixed.

CR:306063

CR Number:   306063 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4212 07 Feb 2003 Fixed 8.0.3 4577 06 Feb 2003 Fixed Description Inserting a row could have caused assertion 200601. This would only occur when doing an insert using the 'ON EXISTING UPDATE' clause. The row being inserted must not have been in the table (ie. no update happened). The table to which the row was being inserted also needed to have been involved in replication for the assertion to occur. The resulting database file was not corrupt. This has been fixed.

CR:306120

CR Number:   306120 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4570 27 Jan 2003 Fixed 8.0.2 4112 27 Jan 2003 Fixed Description When creating a column in the UltraLite schema painter, if the default value chosen was not compatible with the column datatype chosen, the schema painter would have issued an uninformative error message. It now indicates that the column type and the default do not match.

CR:306122

CR Number:   306122 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4570 22 Jan 2003 Fixed 8.0.2 4112 22 Jan 2003 Fixed Description When creating an index with the UltraLite Schema Painter, if an index name was specified that already existed, the existing one was over written without warning. The index creation dialog now prevents a user from creating an index with the name of an existing index.

CR:306125

CR Number:   306125 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4571 23 Jan 2003 Fixed 8.0.2 4114 27 Jan 2003 Fixed 7.0.4 3412 27 Jan 2003 Fixed Description With ANSI_INTEGER_OVERFLOW set to 'on', select 470488670*16 would have returned -1062115872 on Unix platforms. This has been corrected so that the behaviour is to return an overflow error.

CR:306131

CR Number:   306131 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4570 22 Jan 2003 Fixed 8.0.2 4206 22 Jan 2003 Fixed 7.0.4 3411 22 Jan 2003 Fixed Description When a table is added to a Mobilink consolidated database, it is assigned a unique tableid. Scripts created to work on this table will use this tableid when loaded from the database. If the tableid had a value greater than 65535, it was possible that the script would not have loaded, or the wrong script would have been loaded. This has been corrected.

CR:306135

CR Number:   306135 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 4570 22 Jan 2003 Fixed 8.0.2 4206 22 Jan 2003 Fixed 8.0.1 3096 22 Jan 2003 Fixed 8.0.0 2360 22 Jan 2003 Fixed Description It was difficult to enter the following types of numbers as values when editing a table in the "Results Pane": - Negative numbers (e.g. "-123") - Real numbers that began with a decimal point (e.g. ".123") - Numbers in exponential notation (e.g. "1.23e2") For example, typing the number -123, would have caused a beep when the "-" was typed and would not have allowed it to be entered in the editing box for the table data. A workaround for this was to type the number without the minus signt, then add the minus sign after. This bug affects ASA plug-in for Sybase Central as well. This is now fixed in both dbisql and Sybase Central.

CR:306157

CR Number:   306157 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 4570 22 Jan 2003 Fixed 8.0.2 4206 22 Jan 2003 Fixed Description If a user disconnected from Sybase Central, which had been connected to a database server via the JDBC-ODBC bridge, and had selected from a table and viewed its data, Sybase Central would have quietly exited. This problem has now been fixed.

CR:306170

CR Number:   306170 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4563 05 Feb 2003 Fixed 8.0.2 4211 05 Feb 2003 Fixed 8.0.1 3099 05 Feb 2003 Fixed Description In a Visual Basic RDO application, when updating columns in a result set, the updates fail after the first rowset has been processed. A MoveNext would fail with an error "Not Enough fields allocated in SQLDA". The problem has been fixed.

CR:306179

CR Number:   306179 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Solaris Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4576 05 Feb 2003 Fixed 8.0.2 4123 05 Feb 2003 Fixed Description When used on the dbping command-line, the -o switch was not being parsed correctly. Therefore, instead of sending its output to a file, dbping -o would display the usage message. This has been corrected.

CR:306204

CR Number:   306204 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4570 27 Jan 2003 Fixed 8.0.2 4112 27 Jan 2003 Fixed Description The UltraLite Schema Painter would not have properly updated the icons for columns in the primary key, if the operation was cancelled. For example: - Edit an existing table - Alter the primary key by adding a column to it - Cancel the editing of the table Refreshing the application would make it appear as though the column that was added to the primary key (but should have been discarded) was in fact in the primary key. This has been fixed.

CR:306233

CR Number:   306233 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4570 27 Jan 2003 Fixed Description The UltraLite Schema Painter would have displayed a meaningless error message when cancelling a save. For example: - Load a schema file - Make a change to the schema file (add a column to a table for instance) - Choose to create a new schema file and provide a filename - When a message box informs that the previous schema must be closed choose OK. - When a message box informs that the previous schema has changes that should be saved, click Cancel. The error message indicated that a file already exists. It no longer displays that message but returns the user to the new schema file dialog.

CR:306245

CR Number:   306245 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4572 27 Jan 2003 Fixed 8.0.2 4115 27 Jan 2003 Fixed Description When altering a primary key for a table in the UltraLite Schema Painter, if the user pressed Cancel and then went to alter the key again, the columns that were added but cancelled appear to be back in the primary key. This has been fixed.

CR:306301

CR Number:   306301 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4567 23 Jan 2003 Fixed 8.0.2 4105 23 Jan 2003 Fixed Description When using multiple threads with UltraLite (and hence multiple connections), rows could have been lost or not visible, the database could have appeared corrupt, or synchronization could have failed. The incorrect connection number could have been used in any given call. This has been fixed.

CR:306324

CR Number:   306324 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 4575 04 Feb 2003 Fixed 8.0.2 4209 04 Feb 2003 Fixed Description Attempting to create an event with a "WAIT AFTER END" clause would have crashed the server. For example: create event MyEvent schedule MySchedule start time '10:00PM' on ('Thu','Fri') handler begin backup database directory 'd:\\backup' wait after end transaction log truncate end This has now been fixed.

CR:306336

CR Number:   306336 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3414 03 Feb 2003 Fixed Description If a function had a badly defined return statement as in the following case: create function f() returns varchar(10) begin return systable.table_id; end then using the function would have resulted in a server crash. This problem has now been fixed and server will now return an appropriate error message.

CR:306344

CR Number:   306344 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4572 30 Jan 2003 Fixed 8.0.2 4114 30 Jan 2003 Fixed 8.0.1 3096 30 Jan 2003 Fixed 8.0.0 2360 30 Jan 2003 Fixed Description When calling the Mobilink system procedure ml_add_table_script on DB2 with a "null" script parameter value, it would have failed with the message: SQL4302N Java stored procedure or user-defined function "DB2ADMIN.ML_ADD_TABLE_SCRIPT", specific name "SQL021223140150845" aborted with an exception "[IBM][CLIDriver] CLI0115E SQLSTATE=38501". Note, the name "SQL021223140150845" may be different on different systems. Both ml_add_connection_script and ml_add_table_script had this bug, which has been fixed.

CR:306467

CR Number:   306467 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 4578 11 Feb 2003 Fixed 8.0.2 4212 11 Feb 2003 Fixed 8.0.1 3099 11 Feb 2003 Fixed 7.0.4 3416 11 Feb 2003 Fixed Description Calling sa_get_eng_properties on a operating system platform with a large amount of memory, would have displayed properties like "MainHeapBytes" as a negative number. This can also be demonstrated by calling the property() function directly. Example: select property( 'MainHeapBytes' ); This has been fixed.

CR:306470

CR Number:   306470 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) 7.0.4 3416 29 Jan 2003 Fixed Description Databases created with a 7.0.4.3407 server would have failed to start with any newer release of the server, (e.g., any 8.x server), with a "capability 27 missing" error. This problem has now been fixed.

CR:306474

CR Number:   306474 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4580 31 Jan 2003 Fixed 8.0.2 4216 17 Feb 2003 Fixed 8.0.1 3100 17 Feb 2003 Fixed 7.0.4 3419 17 Feb 2003 Fixed Description If a blob column was updated using the ASA provider,(eg. through ADO cursors ), it could have crashed or updated the data incorrectly. This has been fixed.

CR:306536

CR Number:   306536 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 4576 05 Feb 2003 Fixed 8.0.2 4123 05 Feb 2003 Fixed Description If a query contained a grouped subquery in the HAVING clause, and the grouped subquery referenced an aggregate function from the main query, then an incorrect result set may have been returned. This is now fixed. The example below illustrates this issue: the subquery is a grouped query and the aggregate function "min(p.quantity)" is an aggregation that must be computed in the main query block: select id from product p where quantity < 28 group by id having ( select COUNT(*) from product p1 where 28 >= min(p.quantity) ) > 0

CR:306580

CR Number:   306580 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 4578 10 Feb 2003 Fixed 8.0.2 4212 10 Feb 2003 Fixed 8.0.1 3099 10 Feb 2003 Fixed 7.0.4 3416 10 Feb 2003 Fixed Description Queries with LIKE predicates containing a NULL escape character were being evaluated as if there was no escape character. Now LIKE predicates containing a NULL escape character evaluate to NULL. This new behaviour matches the ANSI standard.

CR:306609

CR Number:   306609 Product Name:   MobiLink Product Component:   HotSync Conduit Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4572 28 Jan 2003 Fixed 8.0.2 4207 28 Jan 2003 Fixed Description The following applies to UltraLite synchronization on the Palm using the HotSync conduit. When no synchronization stream parameters were specified by the application in the ul_synch_info passed to PalmExit, the conduit will check the registry as documented for parameters to use. If the registry contains no parameters, a default of tcpip to localhost is used. Previously, specifying no synchronization stream parameters required setting ul_synch_info.stream_parms to NULL. Now, a setting of NULL or an empty string will cause the registry to be checked for parameters to use. If an application needs to force default parameters (overriding the registry), it should set ul_synch_info.stream_parms = "stream=tcpip;host=localhost";

CR:306639

CR Number:   306639 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 4639 21 Apr 2003 Fixed 8.0.2 4243 21 Apr 2003 Fixed Description Executing a MESSAGE statement while in passthrough mode using DBISQL would have caused a server crash, if the DBISQL connection was made using jConnect. An error (-707 Statement is not allowed in passthrough mode) is now reported. Workaround Description  none

CR:306643

CR Number:   306643 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4572 28 Jan 2003 Fixed 8.0.2 4207 28 Jan 2003 Fixed 8.0.1 3096 28 Jan 2003 Fixed Description When trying to create a new service, checking the properties of an existing service, or creating a new integrated login, it was possible to for Sybase Central to crash if a large number of local users were defined on the system. This is now fixed.

CR:306763

CR Number:   306763 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 4573 30 Jan 2003 Fixed 8.0.2 4208 30 Jan 2003 Fixed Description If the TCPIP parameter MyIP, was not a valid IP address, (or the keyword NONE), (i.e. "-x tcpip(MyIP=mypcname)"), a value of 255.255.255.255 was used instead. This has been fixed, only IP addresses (in standard "dot notation") or the word "none" are allowed. Anything else will give an error on startup.

CR:306920

CR Number:   306920 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 517 29 Jan 2003 Fixed 8.0.3 4574 29 Jan 2003 Fixed 8.0.2 4120 29 Jan 2003 Fixed 8.0.1 3097 29 Jan 2003 Fixed Description If the following conditions were all true: - the -x switch was specified on the dbmlsync command line - the progress value on the remote was behind the progress value on the consolidated - the LockTables extended option was set to 'off' then dbmlsync would have failed to generate an upload and report the following error : "No log operation at offset of n in the current transaction log" The number n would be the ending log offset of the current transaction log. This has been fixed.

CR:306963

CR Number:   306963 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 4574 31 Jan 2003 Fixed 8.0.2 4209 31 Jan 2003 Fixed 8.0.1 3098 31 Jan 2003 Fixed 8.0.0 2360 31 Jan 2003 Fixed Description A query in which an ORDER BY DESC was satisfied with a trie-based index could have returned no rows, instead of the intended results. This could also have happened with an ORDER BY ASC, if it was satisfied with a descending index. This has now been fixed. Workaround Description  Customer has a workaround that drops the primary key, runs the query and then adds the primary key back to the table.

CR:306988

CR Number:   306988 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 4573 30 Jan 2003 Fixed 8.0.2 4208 30 Jan 2003 Fixed Description Starting a server with both the -x tcpip(DoBroadcast=NO) and -sb 0 switches would have caused it to crash. This has been fixed.

CR:307143

CR Number:   307143 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 4576 05 Feb 2003 Fixed 8.0.2 4209 05 Feb 2003 Fixed 8.0.1 3099 05 Feb 2003 Fixed Description If a view or derived table was defined with a constant column and the constant column was equated with another constant in a query, the server may have crashed. This has been fixed. The example below illustrates this case, the column X is defined to be 0 in the derived table DT definition and it is equated with the constant 2 in the predicate "DT.X = 2": create table #temp1 (X int); insert into #temp1 select * from ( select X=0 from product p1, product p2 where p1.id = p2.quantity ) AS DT(X) where DT.X = 2 ;

CR:307157

CR Number:   307157 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 4576 04 Feb 2003 Fixed 8.0.2 4209 05 Feb 2003 Fixed Description If a join predicate is of the form "L.X = R.X" where L.X is a unique column, and R.X is not a foreign key column, then the estimated selectivity for the predicate "L.X = R.X" is now computed based on the number of distinct values of the column R.X. For this estimates to be close to the real selectivity, R.X must have an up-to-date histogram or an index on <R.X> must exist. Note, for an index to be useful, the database must have been created with an 8.0 2 or later server.

CR:307174

CR Number:   307174 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 4574 31 Jan 2003 Fixed 8.0.2 4120 31 Jan 2003 Fixed 8.0.1 3097 31 Jan 2003 Fixed 8.0.0 2360 31 Jan 2003 Fixed Description When connected to a database via the JDBC-ODBC bridge, empty strings in LONG VARCHAR columns were displayed as NULL, rather than empty strings. This has been fixed. This problem affected the ASA plug-in for Sybase Central as well.

CR:307194

CR Number:   307194 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4574 31 Jan 2003 Fixed 8.0.2 4120 31 Jan 2003 Fixed 8.0.1 3097 31 Jan 2003 Fixed Description If a JAVA or .NET handler for the report_error event was defined and it used parameters and no script was defined for the handle_error event, Mobilink would report an error similar to: "Not enough arguments to execute script: "moderr.report_error". 5 arguments are needed only 0 are available.". This is now fixed.

CR:307239

CR Number:   307239 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 07 Feb 2003 Fixed 8.0.2 4211 07 Feb 2003 Fixed Description Specifying a File DSN as part of the connection string could have caused any of utilities to crash. This has been fixed.

CR:307354

CR Number:   307354 Product Name:   UltraLite Product Component:   Code Generator Status:   Closed OS:   Microsoft Windows NT Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4591 26 Feb 2003 Fixed 8.0.2 4218 26 Feb 2003 Fixed Description Under certain rare conditions, the "Get" functions generated by the C++ API would have been missing code fragments, resulting in compilation errors and/or erroneous results. This has now been fixed. Workaround Description  The workaround is add by hand this declaration declare: ul_dfp_bool result_2

CR:307381

CR Number:   307381 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 4574 31 Jan 2003 Fixed 8.0.2 4209 31 Jan 2003 Fixed 8.0.1 3097 31 Jan 2003 Fixed 8.0.0 2360 31 Jan 2003 Fixed 7.0.4 3414 31 Jan 2003 Fixed Description Selecting the "Insert spaces" option in the editor's "Customize" dialog, would have been ignored, and would have been set back to "Keep tabs". This has been fixed.

CR:307385

CR Number:   307385 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 4572 31 Jan 2003 Fixed 8.0.2 4120 31 Jan 2003 Fixed Description The MobiLink server could have crashed on shutdown. This was unlikely to have affected synchronizations. It has now been fixed.

CR:307388

CR Number:   307388 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 4576 31 Jan 2003 Fixed 8.0.2 4123 31 Jan 2003 Fixed Description When a second MobiLink monitor attempted to connect, it would have received an "unable to read N bytes" error. It now will get an error indicating that another user is monitoring.

CR:307415

CR Number:   307415 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4574 03 Feb 2003 Fixed 8.0.2 4209 03 Feb 2003 Fixed 7.0.4 3414 03 Feb 2003 Fixed Description When using the Remote Data Access feature to attempt to create a proxy table to a Microsoft Access database, the server may have failed with a "table not found message". This problem occurred when the file path of the Access database was longer than 63 characters. The problem has now been fixed.

CR:307579

CR Number:   307579 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4575 04 Feb 2003 Fixed 8.0.2 4209 04 Feb 2003 Fixed Description When attempting to drop a table, with the UltraLite schema painter, on a newly created schema file could have failed with SQLCODE 0. Attempting to drop the table again, would have properly dropped the table. This is now fixed so that the table is dropped on the first attempt.

CR:307606

CR Number:   307606 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) 8.0.3 4579 13 Feb 2003 Fixed 8.0.2 4214 13 Feb 2003 Fixed 8.0.1 3100 13 Feb 2003 Fixed Description When upgrading to a new minor release of Adaptive Server Aanywhere, after having applied an EBF to the previous version where the EBF was newer than the minor version being installed, the performance counters could have failed to install correctly. During installation, the user may see an error message such as "unable to register dbctrs8.dll: -4". For example, if a user installed 8.0.1 GA followed by 8.0.1.3080 EBF, then upgraded to 8.0.2 GA, the installation may fail because 8.0.1.3080 EBF is newer than 8.0.2GA. This is now fixed, but the problem may be worked around by deleting the dbctrs8.ini and sqlactnm.h files in the win32 directory before installing 8.0.2 GA.

CR:307615

CR Number:   307615 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 4575 04 Feb 2003 Fixed 8.0.2 4123 04 Feb 2003 Fixed 8.0.1 3098 04 Feb 2003 Fixed Description The MobiLink option -vh dumps out the schema, but it didn't display the column names, it substituted the name with Column #n. This option has been improved. For clients that don't send the column names to MobiLink, the schema logging will be the same as before; but for clients that do send the column names, MobiLink will now substitute the column names in place of Column #n.

CR:307751

CR Number:   307751 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) 8.0.3 4576 05 Feb 2003 Fixed 8.0.2 4210 05 Feb 2003 Fixed 8.0.1 3099 05 Feb 2003 Fixed 8.0.0 2360 05 Feb 2003 Fixed 7.0.4 3415 05 Feb 2003 Fixed Description If when executing a .SQL file using the READ statement, the file contained a CONNECT statement where the user name was a parameter to the .SQL file, and it was enclosed in double-quotation marks, the CONNECT statement would have failed. For example, if the following statements were in a file called TEST.SQL: PARAMETERS user_name; GRANT CONNECT TO "{user_name}" IDENTIFIED BY "{user_name}"; GRANT DBA TO "{user_name}"; CONNECT USER "{user_name}"; and were executed by: READ TEST.SQL [test] an error would have occurred that the user "USER" did not exist. This has been fixed. A workaround for the problem is to remove the quotation marks from the CONNECT statement.

CR:307945

CR Number:   307945 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Microsoft Windows NT Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 13 Feb 2003 Fixed Description If a client application did not specify the CommLinks, (or LINKS), parameter in a connection string and links other than Shared Memory had already been used by the client application, then the running links were used instead of links=shmem. Now, not specifying the LINKS parameter is always the same as specifying links=shmem. Note: if an ODBC data source only had the shared memory link selected, then no CommLinks parameter was specified on the connection.

CR:307980

CR Number:   307980 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1099 16 Jun 2003 Fixed 8.0.2 4275 18 Jun 2003 Fixed 8.0.3 4699 24 Jun 2003 Fixed Description If a query used SELECT FIRST, the optimizer might have chosen a poor access plan; in particular, the optimizer might have made a poor choice of the index to use with a particular query. In the reported case, the customer had a query of the form SELECT FIRST * FROM base_table WHERE <condition> ORDER BY <indexed column> In this case, the <condition> in the WHERE clause was highly selective, and could be used as a sargable predicate (that is, the engine could use an index on base_table). However, because of a costing error, the optimizer instead chose a plan utilizing the index on the column specified in the ORDER BY clause, a much more expensive choice in real terms. This has now been fixed, but as a workaround, one could replace SELECT FIRST with SELECT TOP 1.

CR:307991

CR Number:   307991 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 4576 07 Feb 2003 Fixed 8.0.2 4211 28 May 2003 Fixed 8.0.1 3099 07 Feb 2003 Fixed 8.0.0 2360 07 Feb 2003 Fixed Description When displaying data for views that referenced proxy tables, duplicate rows would have been shown, if the connection to the database was made using jConnect. This has been fixed so that the correct rows are now displayed.

CR:308011

CR Number:   308011 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 4576 05 Feb 2003 Fixed 8.0.2 4211 05 Feb 2003 Fixed 8.0.1 3099 05 Feb 2003 Fixed 8.0.0 2360 05 Feb 2003 Fixed Description The server could have crashed after warning of a fatal error, (most likely due to an out of disk condition). This has been fixed.

CR:308012

CR Number:   308012 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1651 28 Oct 2003 Fixed Description In the Create Database wizard, on the Collations page, there is an option to choose to create the database with the default collation, but the actual collation name was not displayed. Now it is.

CR:308031

CR Number:   308031 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) 8.0.3 4583 18 Feb 2003 Fixed 8.0.2 4216 18 Feb 2003 Fixed Description As an ASE compatibility feature, ASA was zero-padding binary strings for TDS connections, (ie jConnect). Since the ASA behaviour did not match ASE behaviour, (ASA zero-padded nullable strings, whereas ASE zero-padded not null strings), and zero-padding gave the impression that a zero-padded binary value was equivelent to a non zero-padded binary value in ASA, when in reality it was not, the zero-padding feature has now been removed. ASA will no longer zero-pad binary for a TDS connection.

CR:308123

CR Number:   308123 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3477 10 Jul 2003 Fixed Description If a view contained a UNION and was defined with a SELECT *, which was no longer valid as columns had been added to the tables referenced in the view, a query referencing that view could have caused a server hang. This has been fixed.

CR:308131

CR Number:   308131 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 07 Feb 2003 Fixed 8.0.2 4212 07 Feb 2003 Fixed Description The UltraLite Schema Painter allows schema files to be read and stored as XML files. Loading a schema in XML format and saving it and then attempting to load another XML file (without shutting down the schema painter) would have caused an error message saying the file didnt exist or was invalid. This is fixed. A workaround would be to shut down the Schema Painter after saving an XML file and start it up again to load another file.

CR:308177

CR Number:   308177 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.02 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 07 Feb 2003 Fixed 8.0.2 4223 06 Mar 2003 Fixed Description In rare cases, it was possible that the server could have crashed when a TCP or SPX connection was being dropped due to a liveness or idle timeout, or through use of the DROP CONNECTION statement. This would only have happened on Win32 platforms and has now been fixed.

CR:308245

CR Number:   308245 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4579 10 Feb 2003 Fixed 8.0.2 4213 10 Feb 2003 Fixed 8.0.1 3100 10 Feb 2003 Fixed 7.0.4 3417 10 Feb 2003 Fixed Description When function IRowsetLocate::GetRowAt was called to fetch result set rows using bookmarks; for static and keyset cursors, ASAProv may have missed a row due to an invalid offset for some bookmark values. This is now fixed.

CR:308297

CR Number:   308297 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 4577 07 Feb 2003 Fixed 8.0.2 4212 07 Feb 2003 Fixed Description If a forward-only, read-only cursor was opened with a query that was optimized to use a merge join, then the error: -187 "Illegal cursor operation attempt" 09W02 could have been returned. For example, this error would be returned when re-fetching the current row. This has now been fixed.

CR:308323

CR Number:   308323 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 4577 07 Feb 2003 Fixed 8.0.2 4212 07 Feb 2003 Fixed 8.0.1 3099 28 May 2003 Fixed Description If a SQL stored procedure was defined as an external java procedure and the access modifier for the java method was private, calling the stored procedure would have executed the method instead of giving an error. Now, the server will report a PROCEDURE_NOT_FOUND error when such procedure is called.

CR:308327

CR Number:   308327 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 11 Feb 2003 Fixed 8.0.2 4122 11 Feb 2003 Fixed Description UltraLite schemas created by the Schema Painter, or ulxml utility, would have had their case-sensitivity reversed. For case sensitive databases, when case should have been respected, it was ignored, and for case insensitive database, when case need not have been respected it was. This has been corrected.

CR:308329

CR Number:   308329 Product Name:   UltraLite Product Component:   CodeWarrior plugin Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4580 13 Feb 2003 Fixed 8.0.2 4214 13 Feb 2003 Fixed Description This change works around a problem in Codewarrior 6 and 7, where they would sometimes not handle compiling an application with an empty segment. This problem would have lead to an error while running the application, such as "Application has just read from low memory... ". A fix was put into a Codewarrior 7 patch, which was included in all versions of Codewarrior 8 and 9. The empty segment in the Codewarrior 7 Certicom runtime has been removed. Workaround Description  Ask customer to apply a patch to Code Warrior 7.

CR:308330

CR Number:   308330 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) 8.0.3 4577 07 Feb 2003 Fixed 8.0.2 4212 07 Feb 2003 Fixed Description Attempting to connect, using jConnect, to a UTF8 database using a userid which contained non-ASCII characters, would have failed. This has now been fixed.

CR:308346

CR Number:   308346 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 4574 10 Feb 2003 Fixed 8.0.2 4120 10 Feb 2003 Fixed Description Table names were being duplicated in the table expression lists on the Joins page of the Query Editor. Table names should now only be listed once.

CR:308347

CR Number:   308347 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 4577 13 Feb 2003 Fixed 9.0.0 530 13 Feb 2003 Fixed Description If a client application did not specify the CommLinks or LINKS parameter in a connection string, and links other than Shared Memory had already been used by the client application, then the running links were used instead of links=shmem. Now not specifying the links connection parameter is always the same as specifying links=shmem. Note that if an ODBC data source only had the shared memory link selected, then no CommLinks parameter was specified on the connection.