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

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

CR:466873

CR Number:   466873 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3485 26 Apr 2007 Fixed 10.0.0 2841 26 Apr 2007 Fixed 9.0.2 3487 26 Apr 2007 Fixed Description If an application made a remote procedure call to a stored procedure in a Microsoft SQL Server database, and one of the arguments to the stored procedure was a string argument of type Input with the value of '' (empty string), then the RPC would have failed with an 'invalid precision value' error. This problem has now been fixed.

CR:466887

CR Number:   466887 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3420 25 Apr 2007 Fixed Description Using encrypted streams could have resulted in failed synchronizations, particularly on Mac systems. This has been fixed.

CR:466968

CR Number:   466968 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 27 Apr 2007 Fixed 10.0.0 2844 27 Apr 2007 Fixed Description Repeated concatenation of a string to another concatenation expression, could have caused the server to use excessive amounts of cache memory, eventually resulting in a stack overflow or a crash. For this to have occurred, a concatenation expression must have repeatedly been performed as the right hand argument of a concatenation expression. For example: declare @var long varchar; declare @counter integer; set @counter = 1; set @var = space(30); calcloop: WHILE @counter < 100000 LOOP set @var = 'string' || @var; set @counter = @counter + 1; END LOOP calcloop; The error did not occur if only the left hand argument of a concatenation expression was a concatenation expression, i.e., set @var = @var || 'string'; This has been fixed.

CR:466989

CR Number:   466989 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3389 25 Apr 2007 Fixed 10.0.0 2840 25 Apr 2007 Fixed 9.0.2 3487 25 Apr 2007 Fixed Description When running on HP-UX Itanium, the server did not search the LD_LIBRARY_PATH when trying to locate shared libraries, instead the SHLIB_PATH is searched. Now both locations are searched. Note that in most cases the script sa_config.sh or sa_config.csh, that is included in the install, is used to set the environment for SQL Anywhere. When sa_config is used, both SHLIB_PATH and LD_LIBRARY_PATH are set, and hence SQL Anywhere will be able to find any libraries it requires. If sa_config is not used, users should work around this issue by setting both SHLIB_PATH and LD_LIBRARY_PATH.

CR:466996

CR Number:   466996 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3486 01 May 2007 Fixed 10.0.0 2842 01 May 2007 Fixed Description It was possible for a dbmlsync synchronization to fail with the following error messages: ... Communication error occurred while sending data to the MobiLink server ... Internal error (???!s). ... Communication error occurred while sending data to the MobiLink server ... Unspecified communication error This problem was most likely to have occurred when a slow network was being used. With a slow network, dbmlsync could have become blocked on a network write. which prevented the sending of a liveness message. To correct this problem, dbmlsync will no longer attempt to send liveness messages when it is blocked on a write. A possible workaround for this problem would be to use the timeout communication parameter to increase the liveness timeout.

CR:467100

CR Number:   467100 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3919 19 Nov 2009 Fixed 10.0.1 3990 19 Nov 2009 Fixed 11.0.1 2354 19 Nov 2009 Fixed 12.0.0 2163 19 Nov 2009 Fixed Description When very rare, a client application using a shared memory connection could have hung forever while executing a statement. This has been fixed.

CR:467122

CR Number:   467122 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3505 30 May 2007 Fixed 9.0.2 3488 26 Apr 2007 Fixed Description The execution time of the CREATE TABLE statement did not scale very well as the number of columns being created increased. The statement could have taken a significant amount of time to create tables with thousands of columns. The performance of the server has been improved so that the CREATE TABLE statement behaves more gracefully as bigger tables are created. Note, this also addresses the problem where deleting a column from a table via the ALTER TABLE statement would have caused a syntax error for values that already existed in other columns.

CR:467128

CR Number:   467128 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3485 26 Apr 2007 Fixed Description The following system stored procedures no longer require DBA authority by default: sa_dependent_views sa_get_dtt sa_check_commit sa_materialized_view_info

CR:467145

CR Number:   467145 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) 10.0.1 3485 27 Apr 2007 Fixed 10.0.0 2842 27 Apr 2007 Fixed 9.0.2 3488 27 Apr 2007 Fixed Description The keybaord accelerator for the "SQL/Stop" menu item was displayed as "Ctrl+Clear", even though there is no "Clear" key on most keyboards. This text has been changed to read "Ctrl+Break".

CR:467246

CR Number:   467246 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3492 09 May 2007 Fixed 10.0.0 2850 16 May 2007 Fixed 9.0.2 3494 16 May 2007 Fixed Description When there were a large number of messages in the message store that were ready for transmission (eg. 200 12KB messages), and the QAnywhere Agent was started on a Windows Mobile 5 device, the synchronization process would have consumed 100% CPU for a significant period of time (eg. 1 minute). Further, if the upload failed after it had started, for whatever reason, each subsequent synchronization would have consumed CPU for a longer period each time. This performance problem has now been significantly alleviated so that synchronizations with QAnywhere will not get progressively longer after upload failures.

CR:467259

CR Number:   467259 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3495 22 May 2007 Fixed 10.0.0 2853 22 May 2007 Fixed Description The server could have crashed when a large number of connections were concurrently executing INSERT or UPDATE statements on tables with CHECK constraints. This was more likely to occur on multi-processor machines. This has been fixed.

CR:467268

CR Number:   467268 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3486 30 Apr 2007 Fixed 10.0.0 2842 30 Apr 2007 Fixed Description Synchronizations that took longer than ten minutes could have been timed-out by the MobiLink server, if the synchronization parameter 'timeout' was set to zero. MobiLink clients send keep-alive bytes to the MobiLink server at an interval of half the timeout value to keep the connection active, UltraLite was not sending these bytes if the timeout value was set to zero. This has been fixed.

CR:467269

CR Number:   467269 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 03 May 2007 Fixed 10.0.0 2844 03 May 2007 Fixed Description For some input values, the UNISTR() function could have entered an endless loop. This has been fixed.

CR:467274

CR Number:   467274 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1506 29 Sep 2008 Fixed 10.0.1 3772 29 Sep 2008 Fixed 11.0.1 1965 13 Nov 2008 Fixed Description When a QAnywhere application (using SQL Anywhere as the message store) queued messages in time zone A, and then the time zone of the device was changed to time zone B with time earlier than time zone A, the queued messages would not have been transmitted until the time in time zone B reached the time that the messages were queued in time zone A. This has been fixed so that the messages queued in time zone A are now sent immediately when the device is online in time zone B. Note that the issue of time zone independence with QAnywhere has not been completely addressed. All time values used in transmission rules refer to local time. Also, the special variable ias_StatusTime, used in transmission rules, refers to local time.

CR:467276

CR Number:   467276 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3486 30 Apr 2007 Fixed 10.0.0 2842 30 Apr 2007 Fixed 9.0.2 3488 30 Apr 2007 Fixed Description The SQL Anywhere OLE DB provider may have failed an assertion if called by ADO with an incorrect set of parameters to Rowset::ReleaseRows. This problem only exists in the 64-bit version of MSADO15.DLL for Windows Vista. It does not exist in the 32-bit version of Vista, nor does it exist in the 64-bit version of Windows 2003. It occurred when ADO calls the SQL Anywhere OLE DB provider to release rows in a rowset that it has not previously fetched rows from. The symptoms include a request to release a rowset with a single row and a pointer to a row handle that is invalid. A work around has been added to the SQL Anywhere OLE DB provider such that a request to release a rowset when no rowset exists will be ignored. The following VBScript sample will fail on 64-bit Windows Vista without the provider workaround: query = "SELECT * FROM Employees" Set recordset = connection.Execute(query) For Each field in recordset.Fields WScript.Echo field.Name propCount = 0 For Each prop in field.Properties 'crashes on 64-bit Vista ... Next Next

CR:467437

CR Number:   467437 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) 10.0.1 3486 30 Apr 2007 Fixed 10.0.0 2842 30 Apr 2007 Fixed 9.0.2 3488 30 Apr 2007 Fixed Description Referencing a column as "IDENTIFIER" .. "IDENTIFIER" (note: two dots) could have caused the server to hang. In cases where the server did not hang, the first identifier would have been ignored. A similar problem existed for columns referenced as "IDENTIFIER" . "IDENTIFIER" .. "IDENTIFIER". For example, the following script would have caused a server hang: CREATE TABLE T1 ( x char(4) NOT NULL, y char(13) NOT NULL, z char(5) NOT NULL, ); CREATE TABLE T2 ( w char(5) NOT NULL, ); SELECT a.x as x, a.y as y, count(b.w) FROM T1 a, T2 b WHERE a.z = b.w Group by a.y, a..x ; -- Note extra '.' Now, the server will generate an error if a query contains a column expression of the form "IDENTIFIER" .. "IDENTIFIER" or "IDENTIFIER" . "IDENTIFIER" .. "IDENTIFIER".

CR:467441

CR Number:   467441 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 02 May 2007 Fixed 10.0.0 2844 02 May 2007 Fixed Description The built-in MobiLink authentication classes that authenticate to external LDAP, POP3 and IMAP servers were unable to read a property if the ScriptVersion of the property was defined as 'ml_global'. It is now possible to define both the authenticate_user connection script and MobiLink properties needed for authentication using the special 'ml_global' connection script. Note that the ml_global property can be over-ridden with a script version specific property, similar to the way connection scripts work.

CR:467446

CR Number:   467446 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) 10.0.1 3487 01 May 2007 Fixed 10.0.0 2843 01 May 2007 Fixed Description If auditing of database activity was enabled, certain failed connection attempts could have caused the server to crash. This has been fixed.

CR:467468

CR Number:   467468 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3487 01 May 2007 Fixed 10.0.0 2843 01 May 2007 Fixed Description The server could have crashed, or became deadlocked, when using snapshot isolation. This could only have happened if the snapshot transaction made use of a long index value. This has now been fixed.

CR:467495

CR Number:   467495 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) 10.0.1 3488 03 May 2007 Fixed 10.0.0 2844 03 May 2007 Fixed Description It was possible for an UPDATE or DELETE statement executed at isolation level 0, to have been blocked on a row lock for a row that was not actually affected by the statement. For this to have occurred, the row of the table must have matched all of the local simple predicates for the table, but be rejected by a later subquery or join predicat, or a predicate involving a user defined function. This behaviour has been changed. Now, UPDATE and DELETE statements at isolation level 0 will only take INTENT or EXCLUSIVE locks on the rows that are actually modified by the statement. Further, this change adjusts the locking behaviour at isolation level 1 so that it is less likely for an INTENT or EXCLUSIVE lock to be taken on a row not affected by an UPDATE or DELETE statement, but this is not guaranteed at isolation level 1. With isolation levels 0 and 1, update anomalies may occur and not all anomalies are prevented by the locking mechanism. Application developers should use caution when using isolation level 0 or 1 with UPDATE and DELETE statements to ensure that the semantics are acceptable to them.

CR:467502

CR Number:   467502 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3487 01 May 2007 Fixed 10.0.0 2844 01 May 2007 Fixed Description A warning message output by the UltraLite Database Initialization utility may have been misleading. When column subsets in a table T that were referenced in a publication PUB, were used to build an UltraLite database, the following warning was displayed: ignoring column subset for publication 'PUB', table 'T' -- all columns will be added Actually, the column subset was being used to build the UltraLite table, it's just that columns not in the subset were being properly excluded from the UltraLite table schema. The message was intended to warn the user in regard to synchronization publications, as UltraLite always synchronizes all of the rows of a table that is specified in a sync publication. Part of the confusion is due to overloading the concept of a publication as a set of tables plus columns to be included in the schema, with the concept of a publication as a set of tables to be synchronized. In order to make this clearer, the warning has been changed to: ignoring column subset for synchronization publication 'PUB', table 'T' -- UltraLite synchronizes entire rows"

CR:467507

CR Number:   467507 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3490 04 May 2007 Fixed 10.0.0 2847 04 May 2007 Fixed 9.0.2 3493 04 May 2007 Fixed 9.0.1 2211 04 May 2007 Fixed Description When using SQL Server Business Intelligence Development Studio, the Data Flow Task "Preview" and column list functions would have failed when using the SQL Anywhere OLEDB Provider to connect to a SQL Anywhere server. This problem has been fixed.

CR:467522

CR Number:   467522 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 02 May 2007 Fixed 10.0.0 2844 02 May 2007 Fixed Description When making a remote procedure call to a stored procedure in a Microsoft SQL Server database, if one of the arguments to the stored procedure was a string argument of type Input with a value of NULL, then the RPC would have failed with an "Invalid precision value' error. This problem has now been fixed.

CR:467528

CR Number:   467528 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3419 01 May 2007 Fixed 10.0.0 2844 01 May 2007 Fixed Description Applications running on AIX systems, and providing the CPORT option in the connection string, would have failed to connect if IPv6 was enabled. This has now been fixed.

CR:467580

CR Number:   467580 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 03 May 2007 Fixed 10.0.0 2844 03 May 2007 Fixed Description If a function was declared non-deterministic and it was used in a SELECT INTO (variable) statement, then the function could have been executed extra times. For this to have occurred, the function reference must not have contained any column references. This problem could also have occurred for SELECT statements, if a column were fetched using GET DATA requests. This problem has been fixed.

CR:467586

CR Number:   467586 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) 10.0.1 3488 02 May 2007 Fixed 10.0.0 2844 02 May 2007 Fixed 9.0.2 3491 02 May 2007 Fixed Description After a failed integrated login, calls to the system function EVENT_PARAMETER( 'User' ) in the ConnectFailed event, could have returned garbage characters. This has been fixed so that calls to EVENT_PARAMETER( 'User' ) will now return the empty string if the user is not known.

CR:467587

CR Number:   467587 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 03 May 2007 Fixed 10.0.0 2844 03 May 2007 Fixed Description The server may have crashed if it was not able to get the network interfaces from the operating system. This has been fixed.

CR:467590

CR Number:   467590 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 03 May 2007 Fixed Description If concatenation was performed in procedural code (either using the concatenation operator or string() function), and one of the arguments had an error, then the server could have crashed. This has been fixed.

CR:467594

CR Number:   467594 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3489 04 May 2007 Fixed 10.0.0 2845 04 May 2007 Fixed 9.0.2 3492 04 May 2007 Fixed Description Calling SADataReader may have caused extra characters to have been returned for string values. A miscalculation of the strings length has been fixed.

CR:467621

CR Number:   467621 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 03 May 2007 Fixed Description The Server Licensing utility, dblic, is used to modify the server's licensing information. In version 10.0.1, with the introduction of license files, dblic operates on the license file instead of the server executable. As an extension, it is possible to still specify the name of the server executable as the argument to dblic. When doing this though, the contents of the license file was being written out over top of the server executable, rendering it unusable. This has been fixed so that it is now possible to specify either the name of the license file or the server executable and dblic will modify only the license file.

CR:467652

CR Number:   467652 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 04 May 2007 Fixed 10.0.0 2845 04 May 2007 Fixed Description If a procedure had a query that referenced a table that was then modified by an ALTER TABLE statement, later execution of the procedure could have caused the server to crash. This has been fixed. See also Engineer case 443016

CR:467712

CR Number:   467712 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3489 28 May 2007 Fixed 10.0.0 2845 07 May 2007 Fixed 9.0.2 3492 07 May 2007 Fixed Description A .NET application would have crashed when trying to send a text message, if the QAManager is closed. Problems with detecting that message repository objects were open have been corrected. Now, the message: "The QAManager is not open." (error code 1021) will be returned.

CR:467733

CR Number:   467733 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3597 12 Nov 2007 Fixed Description When editing a stored procedure which had more than about 1000 lines, CPU usage could have gone to 100%, even without doing anything. This same problem affected the Interactive SQL utility dbisql as well, when editing large SQL files. The problem was caused by the amount of tokenizing being done for syntax highlighting. This has been fixed.

CR:467737

CR Number:   467737 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3496 10 May 2007 Fixed Description When SQL Anywhere was installed in a directory path containing non-ASCII characters, on a system for which the ANSI code page was different from the OEM code page (such as a typical English Windows installation), the server and client libraries may not have been able to access Unilib data files. The problem could show up as an "invalid parameter" error from SORTKEY/COMPARE, or failure to create certain character set converters. The path was erroneously being converted from the OEM codepage to UTF16, rather than from the ANSI codepage to UTF16. This has now been corrected.

CR:467747

CR Number:   467747 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3489 04 May 2007 Fixed 10.0.0 2845 04 May 2007 Fixed Description A second situation similar to Engineering case 467468 was found where the server could have crashed, or became deadlocked, when using snapshot isolation. As with the previous issue, this could only have happened if the snapshot transaction made use of a long index value. This has now been fixed as well.

CR:467783

CR Number:   467783 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3489 07 May 2007 Fixed 10.0.0 2845 07 May 2007 Fixed 9.0.2 3492 07 May 2007 Fixed Description When executing a statement, the "Execution time" message displayed in the "Messages" pane could have been displayed before all of the asynchronous messages caused by a statement had been displayed. This has been corrected to that the execution time message follows the asynchronous messages. Asynchronous messages are those generated explicitly by the MESSAGE statement, or implicitly by CREATE DATABASE.

CR:467789

CR Number:   467789 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) 10.0.1 3489 07 May 2007 Fixed 10.0.0 2845 07 May 2007 Fixed 9.0.2 3492 07 May 2007 Fixed Description Interrupting a SQL statement would not have also aborted any subsequent statements which were pending execution. For example, if a number of statements were entered in the "SQL Statements" field each separated by the command delimiterand then executed, attempting to abort them by clicking the "interrupt" toolbar button, would only have aborted the statement currently executing when the button was aborted; the remaining statements would have continued to be executed. This has been fixed so that the remaining statements are not executed.

CR:467800

CR Number:   467800 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3489 08 May 2007 Fixed 10.0.0 2847 08 May 2007 Fixed 9.0.2 3493 08 May 2007 Fixed Description Attempting to create a proxy table to a table that has a computed index on a remote Oracle server, would have failed with the error "column not found". As part of creating a proxy table to an existing remote table, the server will also attempt to create indexes on the proxy table to match the indexes on the remote table. In this case, the name returned for the computed column was not an actual column name, but an expression name. The server now verifies that the column name truly is the name of a column in the proxy table when automatically creating indexes on proxy tables.

CR:467861

CR Number:   467861 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 May 2007 Third Party Problem Description OLEDB driver retuns error when executing stored procedure with parameters

CR:467873

CR Number:   467873 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3489 07 May 2007 Fixed Description The dblib functions db_change_char_charset() and db_change_nchar_charset() may not have set the error correctly if they failed, and an error was already set from the last request. This has been fixed so that the error is now set correctly.

CR:467970

CR Number:   467970 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3487 08 May 2007 Fixed 10.0.0 2843 08 May 2007 Fixed Description In the presence of a thread deadlock error, an HTTP or SOAP stored procedure or function could have caused the server to appear to hang indefinitely. This problem would only have occurred if the HTTP or SOAP procedure or function being initiated happened to be the last unblocked database request task (i.e., on a server with a -gn value of x, x-1 request tasks would need to be blocked already). This has been fixed.

CR:468023

CR Number:   468023 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3490 15 May 2007 Fixed Description When performing a 10.0.1 upgrade of a 10.0.0 install on Windows, when the FIPS option was selected the dbfips10.dll is not updated. This has been fixed. EBFs with this change will now update the dbfips10.dll.

CR:468031

CR Number:   468031 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3492 09 May 2007 Fixed Description Under some conditions, the qastop utility would have failed to shutdown the QAnywhere Agent. When this occurred, qaagent would hang and the process would have to be terminated. This has been fixed.

CR:468033

CR Number:   468033 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 29 May 2007 Fixed 10.0.0 2857 29 May 2007 Fixed 9.0.2 3504 29 May 2007 Fixed Description Inout parameters were not returned by SADataAdapter.Update when using SADataAdapter and stored procedures to update data. This problem has now been fixed.

CR:468129

CR Number:   468129 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3490 09 May 2007 Fixed 10.0.0 2847 09 May 2007 Fixed Description When an error occurs during synchronization, the MobiLink server should display the full details of the error, including the MobiLInk user name, remote ID, script version, row values (if available), etc. However, if no -vr command line option was specified, the row values were not displayed in the error context by the MobiLink server. This has been corrected.

CR:468148

CR Number:   468148 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3494 09 May 2007 Fixed 10.0.0 2851 09 May 2007 Fixed Description In some cases, executing queries that contained more than one procedure in the FROM clause could have caused the server to crash. This has been fixed.

CR:468319

CR Number:   468319 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) 10.0.1 3490 14 May 2007 Fixed 10.0.0 2848 14 May 2007 Fixed 9.0.2 3494 14 May 2007 Fixed Description It was possible, although very unlikely and timing dependent, that the server could have hung, or even less likely crashed, when a connection was disconnected. This has been fixed.

CR:468343

CR Number:   468343 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3491 14 May 2007 Fixed 10.0.0 2848 14 May 2007 Fixed 9.0.2 3548 27 Aug 2007 Fixed Description If an application attempted to connecting using the TCP parameter DoBroadcast=None and specified an alternate server name, rather than the real server name, in the ENG parameter, the connection would have failed. This has been fixed. Note that the fix requires both an updated server and updated client library.

CR:468347

CR Number:   468347 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3490 14 May 2007 Fixed Description MobiLink clients would never have timed-out a connection if the timeout synchronization parameter was set to zero. This has been fixed so that connections will now timeout after the maximum timeout period of 10 minutes if the server has not responded in this period.

CR:468358

CR Number:   468358 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 30 May 2007 Fixed 10.0.0 2857 30 May 2007 Fixed 9.0.2 3506 30 May 2007 Fixed Description If the server returned the error "Dynamic memory exhausted", it will be followed by diagnostic information about the cache usage that is printed to a file. During this diagnostic printing the server may have crashed. This has been fixed.

CR:468456

CR Number:   468456 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3491 14 May 2007 Fixed 10.0.0 2848 14 May 2007 Fixed Description For certain MobiLink server errors, such as authentication failure, a second error may have appeared later in the log: "Download failed with client error xxx" when download acks had been turned on. This could have been confusing, since it suggested the error originated on the client, when the true error was reported further up in the server log. This has been corrected; the second error message will no longer appear.

CR:468462

CR Number:   468462 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) 10.0.1 3491 14 May 2007 Fixed 10.0.0 2848 14 May 2007 Fixed 9.0.2 3495 11 Mar 2011 Fixed Description If BCP IN was used to populate a table owned by a user other than the connected user, it would have failed with either a 'table not found' error, or the server could have crashed. In some cases, if the connected user also owned a table with the same name as the table being populated, then the server would have attempted to add rows to the wrong table. This problem has now been fixed.

CR:468558

CR Number:   468558 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3493 23 May 2007 Fixed 10.0.0 2851 23 May 2007 Fixed Description The MobiLink plug-in may have failed to create an index on the timestamp column used for timestamp-based synchronization if the consolidated database was an Oracle consolidated database. The script the plug-in uses (in ml-template.zip) has been fixed and the column is now properly indexed.

CR:468582

CR Number:   468582 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3488 17 May 2007 Fixed Description The SQL Anywhere 10.0.1 Maintenance Release was not updating the ADO.NET Data Provider file: iAnywhere.Data.SQLAnywhere.dll. This has been fixed so that susequent EBFs will update this file.

CR:468602

CR Number:   468602 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3490 14 May 2007 Fixed 10.0.0 2849 14 May 2007 Fixed Description The MobiLink file transfer utility mlfiletransfer did not display national characters properly on the command line. This has been fixed.

CR:468630

CR Number:   468630 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3498 16 May 2007 Fixed 10.0.0 2850 16 May 2007 Fixed 10.0.1 3493 16 May 2007 Fixed Description The iAnywhere JDBC Driver currently supports the ResultSet.getBlob() method even though this method is optional in the JDBC specification. However, the ResultSet.getBlob().getBinaryStream() method (which is also optional in the specification) was not supported. Some applications insist that Blob.getBinaryStream() be supported if getBlob() is supported. As a result, the iAnywhere JDBC Driver now supports ResultSet.getBlob().getBinaryStream().

CR:468631

CR Number:   468631 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) 10.0.1 3419 15 May 2007 Fixed 10.0.0 2849 15 May 2007 Fixed 9.0.2 3497 15 May 2007 Fixed Description All of the GUI applications shipped with SQL Anywhere for Mac OS X, such as the Interactive SQL utility and DBLauncher, would have stopped working after applying updates to Mac OS X, specifically Security Update 2007-004. The applications would either have crashed, or displayed a message similar to the following: The library dbput9_r could not be loaded. This may be because the provider is being re-loaded (in which case you need to restart the viewer) or because the library could not be found in the Adaptive Server Anywhere installation. Service management will not be available. or: Link (dyld) error: Library not loaded: libdbserv9_r.dylib Referenced from: /Applications/SQLAnywhere9/System/bin/dbsrv9 Reason: image not found This has been corrected.

CR:468726

CR Number:   468726 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3498 17 May 2007 Fixed Description The server could have returned incorrect results, or in some cases crashed, when executing statements with predicates of the form "expression compare (subquery)". This has been fixed. Note that BETWEEN predicates involving subqueries also qualify as they are interpreted as two compare predicates (see example below). Example: select s_suppkey, s_name, s_address, s_phone, total_revenue from supplier, revenue1 where s_suppkey = supplier_no and ( select max(total_revenue) from revenue1 ) between (total_revenue-0.01) and (total_revenue+0.01) order by s_suppkey

CR:468735

CR Number:   468735 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3492 16 May 2007 Fixed 10.0.0 2850 16 May 2007 Fixed 9.0.2 3498 16 May 2007 Fixed Description If a QAnywhere message in the server database with an expiration date, was synchronized down to a client device before it had expired, the message would not have transitioned to an expired state, and hence would not have been deleted by the default server delete rule. This has been fixed. Note that a QAnywhere message in the server database with an expiration date, that is not delivered to the client device before it expires, will also transition to an expired state and be deleted by the default server delete rule. This was the case before this change.

CR:468745

CR Number:   468745 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3508 04 Jun 2007 Fixed Description If the option to view the Readme.txt file, or the iAnywhere Online Resources page, was selected during an install, the corresponding application would not have run. However, the install script would have waited for the user to dismiss the (invisible) application(s), and the install would have appeared to be hung. This has been fixed. Workaround Description  Deselect the view the read me box.

CR:468783

CR Number:   468783 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3492 16 May 2007 Fixed 10.0.0 2850 16 May 2007 Fixed 9.0.2 3497 16 May 2007 Fixed Description Clicking the Name column heading in the table editor, would not have sorted the column names correctly. Specifically, all column names starting with upper-case letters were sorted before all column names starting with lower-case letters. This has been fixed. A similar fix has been made for the Data Type, Value and Comment columns.

CR:468862

CR Number:   468862 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3492 16 May 2007 Fixed Description Previouly, the MobiLink server only supported "blocking download ack" mode. Now, the MobiLink server also supports "nonblocking download ack" mode. This mode may be controlled with the "-nba+" (use nonblocking download ack) or "-nba-" (use blocking download ack) command line options, with "-nba-" being the default. Nonblocking download acknowledgement mode provides a significant performance advantage over blocking download acknowledgement mode, but may not be compatible with some existing scripts. The following is the documentaion update: MobiLink now supports two modes of download acknowledgement: blocking and non-blocking. Prior to this change, MobiLink only supported blocking download acknowledgement. When you turn on download acknowledgement, the default continues to be blocking. Note: Download acknowledgement is not on by default. To turn it on, use the dbmlsync "SendDownloadACK" extended option or the UltraLite "Send Download Acknowledgment" synchronization parameter. Download acknowledgement is not required to ensure that data is successfully downloaded. Download acknowledgement simply allows you to get acknowledgement of a successful download immediately (in the download); otherwise the acknowledgement occurs in the next upload. To set non-blocking download acknowledgement, use the new mlsrv10 option -nba+. Non-blocking download acknowledement is recommended because it provides a significant performance advantage over blocking download acknowledgement. However, non-blocking download acknowledgement cannot be used in the following cases: - Clients prior to 10.0.0 do not support non-blocking acknowledgement. - You cannot use non-blocking acknowledgement with the Notifier scripts that are generated by MobiLink Model mode. QAnywhere messaging uses non-blocking download acknowledgement. You cannot change this setting for QAnywhere: You will get an error if you specify both -m and -nba- on the mlsrv10 command line. To provide extra optional functionality to the new non-blocking download acknowledgement, two new MobiLink events have been added: nonblocking_download_ack and publication_nonblocking_download_ack. nonblocking_download_ack connection event ----------------------------------------- Function: When using non-blocking download acknowledgement, this event lets you update your database based on the successful application of the download. Parameter name Description Order -------------- ----------- ----- s.remote-id VARCHAR(128) N/A s.username VARCHAR(128) 1 s.last_download TIMESTAMP 2 This event is only called when using non-blocking download acknowledgement. When in non-blocking mode, the download transaction is committed and the synchronization ends when the download is sent. This event is called when the synchronization client acknowledges a successful download. This event is called on a new connection, after the end_synchronization script of the original synchronization. The actions of this event are committed along with an update to the download time in the MobiLink system tables. Due to the special nature of this script, any connection-level variables set during the synchronization are not available when this event is executed. For example, the following script adds a record to the table download_pubs_acked. The record contains the remote ID, first authentication parameter, and the download timestamp. INSERT INTO download_pubs_acked( rem_id, auth_parm, last_download ) VALUES( {ml s.remote_id}, {ml a.1}, {ml s.last_publication_download} ) publication_nonblocking_download_ack connection event ----------------------------------------------------- Function: When using non-blocking download acknowledgement, this event lets you update your database based on the successful application of the download of this publication. Parameter name Description Order -------------- ----------- ----- s.remote-id VARCHAR(128) N/A s,username VARCHAR(128) 1 s.last_publication_download TIMESTAMP 2 s.publication_name VARCHAR(128) 3 s.subscription_id VARCHAR(128) 4 This event is only called when using non-blocking download acknowledgement. When in non-blocking mode, the download transaction is committed and the synchronization ends when the download is sent. When the synchronization client acknowledges a successful download, this event is called once per publication in the download. This event is called on a new connection and after the end_synchronization script of the original synchronization. The actions of this event are committed along with an update to the download time in the MobiLink system tables. Due to the special nature of this script, any connection-level variables set during the synchronization are not available when this event is executed. For example, the following script adds a record to a table called download_pubs_acked. The record contains the publication name, the first authentication parameter, and a download timestamp: INSERT INTO download_pubs_acked( pub_name, auth_parm, last_download ) VALUES( {ml s.publication_name}, {ml a.1}, {ml s.last_publication_download} )

CR:468864

CR Number:   468864 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3493 17 May 2007 Fixed 10.0.0 2851 17 May 2007 Fixed Description Servers running on Unix systems, and attempting to use an alternate server name, may have failed to start, giving the error "Alternate server name is not unique", even though no other server on the machine or network was using that server name. This has been fixed.

CR:468867

CR Number:   468867 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3493 16 May 2007 Fixed 9.0.2 3498 16 May 2007 Fixed Description When run on Windows CE devices, 1MB per of address space was reserved by the server for each thread, although only a portion was actually allocated, or "committed". This has been changed for Windows CE PocketPC 2003 and newer devices, as the server now implements the -gss command line option for these devices. The -gss option sets the stack size per internal execution thread. The default and minimum stack size is 64K and the maximum is 512K.

CR:468878

CR Number:   468878 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3496 23 May 2007 Fixed 10.0.0 2854 23 May 2007 Fixed Description After executing a statement, the toolbar buttons could have remained disabled, even though they should have been enabled. This problem was timing dependent, so it tended to appear on some machines from time to time, but not on others at all. This has now been fixed. Note that the menu items and accelerator keys corresponding to the toolbar buttons were enabled correctly and were functional.

CR:468882

CR Number:   468882 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) 10.0.1 3493 16 May 2007 Fixed 10.0.0 2850 16 May 2007 Fixed 9.0.2 3498 16 May 2007 Fixed Description In certain situations, for example, when the database server was shutting down, DBLauncher may not have displayed all of the messages it received from the database server, making it look like the database server had hung. This has been fixed.

CR:468897

CR Number:   468897 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3498 17 May 2007 Fixed Description If an embedded SQL application allocated a SQLCA, some of the contents of the allocated SQLCA could have been left uninitialized after calling db_init. It was also possible, although likely rare, that a call to sqlerror_message using an allocated SQLCA could have caused the application to crash. Using the sqlca pointer included in DBLib did not have this problem. This has been fixed so that the allocated SQLCA is now properly initialized as part of db_init, and calls to sqlerror_message will not cause a crash. A workaround is to zero out the allocated SQLCA memory after allocating it and before calling db_init. The allocated SQLCA (say app_sqlca) can be zeroed out using: memset( app_sqlca, 0, sizeof( SQLCA ) )

CR:468905

CR Number:   468905 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 May 2007 Fixed Description When running at snapshot isolation, a positioned update or delete to a row previously updated by another connection may have blocked in some cases, even though it was possible to have immediately given an update conflict error. This is fixed. Note, in general blocking is still allowed when snapshot transactions do updates or deletes (unless the "blocking" option is off). This change only gives the conflict error earlier in some restricted cases.

CR:469002

CR Number:   469002 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3493 17 May 2007 Fixed 9.0.2 3498 17 May 2007 Fixed Description When run on Windows CE, the reserved stack sizes for all threads in the QAnywhere agent, the Listener and the MobiLink client have been changed to be as follows: qaagent.exe: 64 KB dblsn.exe: 64 KB dbmlsync.exe: 128 KB Previously, 1MB per thread of address space was reserved, while only a portion was actually allocated, or "committed".

CR:469020

CR Number:   469020 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3498 17 May 2007 Fixed Description The internal data structure for a cursor cannot exceed 64K. When a cursor would be larger than 64K, a diagnostic was not always generated. This was corrected.

CR:469145

CR Number:   469145 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3499 18 May 2007 Fixed Description If the QAnywhere Agent is started on Windows CE with a spacey path in the startline connection parameter, for example: qaagent -c "...;startline=\Program Files\Sybase\ASA9\dbsrv9 -o dbsrv.txt -c 20m -gd all -gp 4096 -n qanywhere -gk all -qw -gn 10" then it would have failed to start the database server with the error "InternalError: Unable to start database server". A problem with passing double quotes in the connection string has been fixed.

CR:469146

CR Number:   469146 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3494 18 May 2007 Fixed 10.0.0 2851 18 May 2007 Fixed Description If the return type of a method in a WSDL document contained the method name, the WSDL compiler would have generated an incorrent C# method signature for the asynchronous method call. For example: public WSResult AsyncCategoryBrowseResponseResponse CategoryBrowse(CategoryBrowseRequest request) // incorrect should be: public WSResult AsyncCategoryBrowse(CategoryBrowseRequest request) // correct A problem with the generation of asynchronous C# method signatures has been corrected.

CR:469151

CR Number:   469151 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3494 18 May 2007 Fixed 10.0.0 2851 18 May 2007 Fixed Description The MobiLink server now closes non-persistent HTTP connections without waiting for the client to close the connection, as there is no need to hang on to the connection after the HTTP response is sent. This change modestly improves server resource usage when using non-persistent HTTP.

CR:469259

CR Number:   469259 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3496 23 May 2007 Fixed Description The server may have crashed during the execution of an IN predicate of the form "{column} IN ( const, ...)". This would have occurred if the IN predicate was part of a control statement's condition, or part of the WHEN clause of a trigger definition; or at least one IN list entry needed an implicit type conversion in order to perform the compare. This has been fixed.

CR:469411

CR Number:   469411 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3509 04 Jun 2007 Fixed Description Calls to the ODBC function SQLNativeSql() could have caused a crash in the ODBC driver. If the character set of the database was UTF8, a crash could have occurred or incorrect results could have been returned. This problem has been fixed.

CR:469436

CR Number:   469436 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 2853 23 May 2007 Fixed 10.0.1 3496 23 May 2007 Fixed Description The server would have incorrectly marked all updates applied by SQL Remote as having caused a conflict when being applied to the consolidated database. This would have caused the resolve update trigger to fire when there was in fact no conflict, and would also have caused the update that was just applied to the consolidated to be echoed back to the remote database. This would have caused the row at the remote database to be temporarily set back to an older value. This problem has now been fixed so that the server will properly detect conflicts at the consolidated database.

CR:469523

CR Number:   469523 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 29 May 2007 Fixed 10.0.0 2857 29 May 2007 Fixed 9.0.2 3504 29 May 2007 Fixed Description If a view was updated with an UPDATE statement that contained a VERIFY clause, the server may have crashed or incorrectly used the VERIFY clause. This would only have happened if the view and the base table had a different column ordering in the select list. This has been fixed.

CR:469570

CR Number:   469570 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3496 24 May 2007 Fixed 9.0.2 3501 24 May 2007 Fixed Description If the default command file for the Listener utility (dblsn,txt) was used implicitly, then having the -q option in the command file would have had no effect on the gui, instead of minimizing it. The desired behavior was achieved if the same command file was used explicitly (i.e. dblsn.exe @dblsn.txt). This problem has been fixed.

CR:469674

CR Number:   469674 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3508 01 Jun 2007 Fixed Description The number of rows being sent by MobiLink to an UltraLite client could have been more than the number of rows the UltraLite client actually inserted. Rows could have been lost by UltraLite during synchronization when the primary key for a table was not the first index in the table. This situation could have occurred when changing the primary key via the UltraLite Schema Painter application. This problem has now been fixed. Newly created schemas (or altered schemas) will ensure the primary key is the first index for every table. For existing databases, UltraLite will check after loading the schema, that the primary key is the first index in every table and it will make it so if necessary. A workaround to this issue would be to unload and reload the schema and/or the database.

CR:469685

CR Number:   469685 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3496 24 May 2007 Fixed 10.0.0 2855 24 May 2007 Fixed Description The server could have incorrectly accepted an outer reference as a parameter to the ROWID() function, without throwing an error. For example, the following query would not have returned an error: SELECT * FROM table1, some_procedure( ROWID( table1 ) ) The behaviour of such a function call was undefined; a query containing an illegal outer reference may have returned unintuitive or inconsistent results. This has been corrected so that the server now correctly returns an error when the ROWID() function is called with an illegal outer reference as an argument.

CR:469699

CR Number:   469699 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3501 24 May 2007 Fixed Description An attempt by a version 9.0.2 DLL to self-register itself on Windows Vista would have resulted in the regsvr32 process going into an infinite loop waiting for the self-registration to complete. This could have happened during any of the EBF installs from 9.0.2 build 3476 on. The problem would also have manifest itself after any of these EBFs have been installed by manually executing a regsvr32 command on a DLL. Since any 9.0.2 DLL that requires registration has already performed the registration step as part of the initial 9.0.2 install, the re-registration failure during an EBF install should not cause any problem, and the regsvr32 process can be safely terminated. In a similar fashion, any attempt to unregister a DLL (regsvr32 /u) once the EBF was applied would also have failed. This problem has now been fixed.

CR:469705

CR Number:   469705 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3527 16 Jul 2007 Fixed Description If an existing database that contained materialized views and indexes on these views, was unloaded using the Unload utility or the DBTools function DBUnload, then the definitions of these indexes was not unloaded. This problem has now been resolved.

CR:469731

CR Number:   469731 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) 25 May 2007 Fixed Description Attempting to start a real database with the DatabaseName "utility_db", would have resulted in one of two different error messages (permission denied or naming conflict), depending on the situation. This has been corrected, the name "utility_db" is now reserved for the utility database. Other databases attempting to use this name will see the error SQLE_DB_ALIAS_RESERVED_UTILDB (-985) "The database name 'utility_db' is reserved for the utility database."

CR:469827

CR Number:   469827 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 30 May 2007 Fixed 10.0.0 2857 30 May 2007 Fixed Description The server may have erroneously reported the error "Right Truncation of string data" when data was converted to CHAR or VARCHAR as part of a query (eg a CAST operation). This would have occurred if the database was created with a multi-byte collation, and a column contained NCHAR data of sufficient length (depending on the collation in use, but always at least 8192 bytes). This has now been fixed. Workaround Description  None

CR:469851

CR Number:   469851 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3497 25 May 2007 Fixed 10.0.0 2855 25 May 2007 Fixed Description If a rule was created whose condition expression contained a newline character, once saved to a ".qar" file, the file could not have been read properly. Embedded newlines were not being escaped with the line continuation character when they were written. This has ben fixed so that the condition is now saved correctly.

CR:469896

CR Number:   469896 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3498 28 May 2007 Fixed 10.0.0 2855 28 May 2007 Fixed Description Selecting a different value in the "Encoding" combobox did not correctly update the preview of table data in the Import Wizard. This has been corrected.

CR:469973

CR Number:   469973 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 28 May 2007 Fixed 10.0.0 3503 28 May 2007 Fixed Description On Windows Vista systems, the server would have left a minimized command-shell window visible in the Windows taskbar when starting Java in the database. Self-registering DLLs, such as the ODBC driver or the dbctrs perfmon plugin DLL, could also have shown a minimized command-shell window, but it was very short-lived. Both these problems have now been corrected

CR:469974

CR Number:   469974 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 29 May 2007 Fixed 10.0.0 2856 29 May 2007 Fixed Description An application would have failed to autostart the engine when using a quoted StartLine value that contained spaces in the path. For example, the following startline would have failed with SQLE_UNABLE_TO_CONNECT_OR_START: StartLine="\Program Files\uleng10.exe" This problem has been fixed. This problem can be worked-around by making the opening quote the second character: StartLine=\"Program Files\uleng10.exe" or by enclosing the entire quoted value in single quotes: StartLine='"\Program Files\uleng10.exe"'

CR:469976

CR Number:   469976 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) 31 May 2007 Fixed Description The server may have returned incorrect results when evaluating a query that contained a procedure call in the FROM clause if the body of the procedure contained only a single statement, and an unqualified column reference was passed to the procedure as an argument. In order for this incorrect behaviour to have occurred the column reference passed to the procedure had to have the same name as a column in a table referenced by the statement in the body of the procedure. This problem has now been fixed.

CR:469977

CR Number:   469977 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 31 May 2007 Fixed 10.0.0 2857 31 May 2007 Fixed Description If a server was started on Windows Vista and the default port number 2638 was in use, the server may give the error "Unable to initialize communications links" and fail to start. This would only have happened if a port number was not specified using the -x server option. The correct behaviour is to choose a different port and start on that port. This has been fixed.

CR:470050

CR Number:   470050 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3502 05 Jun 2007 Fixed 10.0.0 2860 05 Jun 2007 Fixed Description It was possible when rebuilding a database (version 10 or earlier) to version 10 using dbunload -an, -ar or -ac, that the new database would have been missing some objects. This would only have occurred if the database being unloaded contained GLOBAL TEMPORARY TABLES that had foreign keys, or comments using COMMENT ON, on them. The resulting database could have been missing indexes and/or comments on indexes for any tables, including base tables, that were to be created after those for the GLOBAL TEMPORARY TABLE. This has now been fixed. The fix requires a new dbtools library, as well as the updated script files, unload.sql and unloadold.sql.

CR:470052

CR Number:   470052 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 29 May 2007 Fixed Description On Japanese Windows systems, when browsing for a file in SQL Anywhere Explorer, UltraLite udb and pdb files would not have been displayed when the file type was "All UltraLite Database Files (.udb, .pdb)", even though they did exist. This has been fixed.

CR:470056

CR Number:   470056 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 29 May 2007 Fixed 10.0.0 2856 29 May 2007 Fixed Description Attempting to include a column with an approximate data type (real, float or double) in an index would have caused a warning dialog to be displayed discouraging this practice. The dialog was provided with an OK button only. This has been corrected so that now both OK and Cancel buttons are provided, with Cancel cancelling the operation.

CR:470058

CR Number:   470058 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3499 29 May 2007 Fixed 10.0.0 2857 29 May 2007 Fixed Description If a database contained a user-defined message that included an embedded quote, attempting to rebuild the database would have failed when the resulting CREATE MESSAGE statement was executed. This has been fixed.

CR:470173

CR Number:   470173 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   5.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 31 May 2007 Fixed 10.0.0 2859 31 May 2007 Fixed 9.0.2 3507 31 May 2007 Fixed Description After using Sybase Central to create a proxy table to a table in Paradox, fetching from that table would have failed with a "could not find the object" error message. The method Sybase Cenral used to qualify the table name with the database name was not supported by Paradox. This problem has been fixed by implementing a work around in the server to modify the qualified table name so that it is supported by Paradox.

CR:470176

CR Number:   470176 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3502 04 Jun 2007 Fixed 10.0.0 2860 04 Jun 2007 Fixed Description There was no implementation for the ODBC function SQLSynchronizeW() in the Runtime, even though it is defined in ulodbc.h. This has been corrected by implementing SQLSynchronizeW().

CR:470195

CR Number:   470195 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 30 May 2007 Fixed 10.0.0 2857 30 May 2007 Fixed 9.0.2 3506 30 May 2007 Fixed Description If an event was fired using the TRIGGER EVENT statement with a list of event parameter values, the server could have crashed when the event handler attempted to access the parameters via the event_parameter() function. This has been fixed.

CR:470198

CR Number:   470198 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 30 May 2007 Fixed Description The utility SetupVSPackage.exe was not respecting the language setting as defined by DBLANG. This has been fixed.

CR:470202

CR Number:   470202 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3516 03 Jul 2007 Fixed Description Named parameters found in scripts would have been parsed and incorrectly substituted for, when found in comments and quoted strings. This could have caused parameters to be passed in the wrong order, or an error message to be generated, when the number of parameters did not match what was expected. This has been fixed. Note, the following forms of comments are recognized: -- (two hyphens) // (two forward slashes) /* */ The first two forms cause the script text to be ignored until the end of a line. The last form causes all text between the "/*" and "*/ to be ignored. This form of comment cannot be nested. Any other type of vendor specific comment will not be recognized and should not be used to comment out references to a named parameter. Workaround Description  None.

CR:470274

CR Number:   470274 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3511 08 Jun 2007 Fixed Description If a query used certain internal system procedures on the NULL-supplying side of an outer join, the wrong results could have been returned. The following procedures had this characteristic, and have been corrected: - sa_rowgenerator - sa_report_blocking - sa_lockinfo - sa_report_deadlocks - sa_performance_diagnostics - sa_performance_statistics