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

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

CR:494310

CR Number:   494310 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) 11.0.0 1076 14 Mar 2008 Fixed 10.0.1 3657 14 Mar 2008 Fixed Description If a materialized view was dropped as the result of dropping a user, and this was done concurrently with other database requests, the server could crashed, or failed assertions. Database corruption was also possible. This has now been fixed.

CR:494319

CR Number:   494319 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) 11.0.0 1152 18 Mar 2008 Fixed 10.0.1 3659 18 Mar 2008 Fixed 9.0.2 3637 18 Mar 2008 Fixed Description If the Unload utility was used to perform an internal unload (-ii or -ix command line option) from a Windows client while connected to a Unix server, unloaded data files would have been created with a backslash character in the file name instead of being placed in a sub-directory of the server's current working directory. Furthermore, the generated reload.sql script referenced these data files using forward slashes, making it unusable without modification. A work around is to append a forward slash to the end of the directory name passed to the dbunload utility.

CR:494356

CR Number:   494356 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 3661 10 Jul 2008 Fixed 9.0.2 3638 19 Mar 2008 Fixed Description A QAnywhere .NET application could have hung if a QAManager API method was interrupted by an exception in one thread and another thread subsequently called a method on the QAManager that was interrupted. This has been fixed. Workaround Description  A QAnywhere .NET application could have hung if a QAManager API method was interrupted by an exception in one thread, and another thread subsequently called a method on the QAManager that was interrupted. This has been fixed.

CR:494364

CR Number:   494364 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1153 17 Mar 2008 Fixed Description End-to-end encryption could have failed, or hang, the synchronization, although the probability of failure was quite low. This has now been corrected.

CR:494414

CR Number:   494414 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1153 19 Mar 2008 Fixed 10.0.1 3658 19 Mar 2008 Fixed Description An application could have crashed if an invalid protocol option was used in the connection string (for example links=tcpip(invalid=value) ). This has been fixed.

CR:494431

CR Number:   494431 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) 11.0.0 1159 18 Mar 2008 Fixed 10.0.1 3659 18 Mar 2008 Fixed Description An error could have incorrectly been given when converting a string such as '+123' to one of the following types: INT, UNSIGNED INT, BIGINT, UNSIGNED BIGINT. A redundant '+' is permitted at the beginning of the string when converting to a number. Prior to the changes for Engineering case 392468 (10.0.1 build 3476), the conversion incorrectly gave an error for BIGINT and UNSIGNED BIGINT, but the correct behaviour was given for INT and UNSIGNED INT. In 10.0.1 build 3476 and later, the error was generated incorrectly for all of the above listed types. This problem has been fixed.

CR:494448

CR Number:   494448 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) 11.0.0 1172 17 Mar 2008 Fixed 10.0.1 3658 17 Mar 2008 Fixed Description Catalog information about a materialized view could have been inaccurate following execution of a REFRESH MATERIALIZED VIEW statement that had failed. This has been fixed.

CR:494449

CR Number:   494449 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) 11.0.0 1192 17 Mar 2008 Fixed 10.0.1 3659 17 Mar 2008 Fixed Description Under rare circumstances, the server could have crashed while executing a trigger defined for multiple events. This has been fixed.

CR:494450

CR Number:   494450 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1215 29 Apr 2008 Fixed 10.0.1 3685 29 Apr 2008 Fixed Description Global shared temporary tables were being unloaded as regular global temporary tables (ie non-shared). This has been fixed.

CR:494462

CR Number:   494462 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1157 18 Mar 2008 Fixed 10.0.1 3659 18 Mar 2008 Fixed 9.0.2 3637 18 Mar 2008 Fixed Description When attempting to call a stored procedure in an ADO application, the OLE DB provider could have returned an "invalid parameter type" error. The order of the parameters in the procedure was not determined correctly by the provider. This has been corrected. Workaround Description  Recreating the procedures/functions a number of times until the procparm order matches the actual definition. Once the system catalog has the expected order (if ever) never modify them again.

CR:494579

CR Number:   494579 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1160 19 Mar 2008 Fixed 10.0.1 3660 19 Mar 2008 Fixed Description When changing a column's DEFAULT value to "No default value", a syntax error would have been reported. The plugin was incorrectly executing the statement ALTER TABLE t ALTER c DROP DEFAULT. This has been fixed so that the plugin now uses the correct syntax ALTER TABLE t ALTER c DEFAULT NULL.

CR:494583

CR Number:   494583 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1211 24 Apr 2008 Fixed 10.0.1 3683 24 Apr 2008 Fixed Description The Index Consultant wizard leaves the Interactive SQL utilirt (dbisql) is a state such that autocommit is on. This has been fixed.

CR:494708

CR Number:   494708 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) 11.0.0 1160 19 Mar 2008 Fixed 10.0.1 3660 19 Mar 2008 Fixed 9.0.2 3638 19 Mar 2008 Fixed Description It was possible for the server to fail assertions 201866 - "Checkpoint Log: Page 0x%x is invalid" or 201864 - "Checkpoint log: Invalid page number on page 0x%x", for a database containing a corrupted page in the checkpoint log. This could have occurred in cases where it was safe for the server to ignore the corruption and recover the database. This has been fixed. The assertions never occurred in databases that didn't contain corruption.

CR:494710

CR Number:   494710 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1160 19 Mar 2008 Fixed 10.0.1 3660 19 Mar 2008 Fixed Description Incorrect results could have been returned when there was an ORDER BY clause that caused a temporary table to be generated. For this to hace occurred there must have been a subquery expression in the select list that referred to a table that could be updated, and the query had to have been potentially updateable (FOR READ ONLY was not specified). This was corrected. The work-around is to specify FOR READ ONLY on the query.

CR:494963

CR Number:   494963 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) 11.0.0 1171 27 Mar 2008 Fixed 10.0.1 3664 27 Mar 2008 Fixed Description When there were at least three joins in a query table expression and there was a reference from the ON condition to a column in a table at least three preceding, an incorrect syntax error may have occurred. This has been corrected.

CR:494983

CR Number:   494983 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) 11.0.0 1166 24 Mar 2008 Fixed 10.0.1 3661 24 Mar 2008 Fixed Description If the last page of the transaction log was only partially written, perhaps due to a power failure, it was possible that the database would not have been able to recover on startup. It is most probable that this would have occurred on Windows CE. The likely error would have been a failure to validate the checksum on the page. This has been fixed.

CR:495001

CR Number:   495001 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 3661 20 Mar 2008 Fixed Description If an application made concurrent connections with both YES and NO boolean parameter values, the application could have crashed or the boolean connection parameters could have been interpreted incorrectly. This has been fixed.

CR:495092

CR Number:   495092 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3640 25 Mar 2008 Fixed Description Messages displayed by many of the utilities (ie dbunload, dbvalid, etc) may have been truncated. The message display buffer size has been increased to correct this problem. Workaround Description  None.

CR:495093

CR Number:   495093 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1168 25 Mar 2008 Fixed Description When modifying the SQL text for a materialized view, if the original materialized view had a refresh type of 'Immediate', then an error would have occurred while attempting to save the view. In addition, a temporary view (with a name ending in an IP address and timestamp) would have remained. Both of these issues have been fixed.

CR:495145

CR Number:   495145 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1164 24 Mar 2008 Fixed 10.0.1 3662 24 Mar 2008 Fixed Description HTTP or HTTPS synchronizations may have failed or hung, particularly on slow or low-quality networks. This has been fixed.

CR:495146

CR Number:   495146 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1164 24 Mar 2008 Fixed 10.0.1 3662 24 Mar 2008 Fixed Description Synchronizations with may have failed or hung, particularly on slow or low-quality networks. This has been fixed.

CR:495147

CR Number:   495147 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1164 24 Mar 2008 Fixed Description Synchronizations using end-to-end encryption may have failed or hung. This has been fixed.

CR:495225

CR Number:   495225 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) 11.0.0 1166 24 Mar 2008 Fixed 10.0.1 3662 24 Mar 2008 Fixed Description When editing a synchronization model, if one or more rows in the column mapping editor were marked for deletion, attempting to revert changes to the model could have caused Sybase Central to crash. The same problem could have occurred when attempting to select another item in the tree and answering "No" to the "Do you want to save changes?" dialog. This has now been fixed.

CR:495231

CR Number:   495231 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) 11.0.0 1166 24 Mar 2008 Fixed 10.0.1 3662 24 Mar 2008 Fixed Description Executing a COMMENT ON INTEGRATED LOGIN statement could have caused the server to crash, or to fail an assertion, if executed concurrently with other commands. This has been corrected.

CR:495236

CR Number:   495236 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) 11.0.0 1166 24 Mar 2008 Fixed 10.0.1 3662 24 Mar 2008 Fixed Description There was a chance that the server would have crashed when making the connection to a remote server using one of the JDBC based Remote Data Access classes. This problem has been fixed.

CR:495240

CR Number:   495240 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) 11.0.0 1170 27 Mar 2008 Fixed 10.0.1 3664 27 Mar 2008 Fixed Description If an ALTER <column> statement encountered an error, subsequent statements could have erroneously failed with the error SQLE_SCHEMA_UPGRADE_NOT_ALLOWED, and/or the runtime could have experienced a crash at some later point. This has been fixed.

CR:495369

CR Number:   495369 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) 11.0.0 1514 09 Oct 2008 Fixed 10.0.1 3779 09 Oct 2008 Fixed 11.0.1 1976 14 Nov 2008 Fixed Description The performance of some queries has degraded from what it was in version 9. Further optimizations have been added so that the performance has been restored.

CR:495375

CR Number:   495375 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1168 25 Mar 2008 Fixed 10.0.1 3662 25 Mar 2008 Fixed 9.0.2 3640 25 Mar 2008 Fixed Description The result set returned when SAConnection.GetSchema("ProcedureParameter") was called, would have been in an unpredictable order. This has been fixed by adding an ORDER BY clause to the query statement.

CR:495381

CR Number:   495381 Product Name:   UltraLite Product Component:   MobiLink Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3642 28 Mar 2008 Fixed Description If ulview.exe was used to build a USM file and a column was added to the primary key of a table after adding the same column to an index, would have resulted in protocol error when attempting to synchronize. This has now been fixed.

CR:495396

CR Number:   495396 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) 11.0.0 1174 26 Mar 2008 Fixed 10.0.1 3665 31 Mar 2008 Fixed 9.0.2 3644 31 Mar 2008 Fixed Description If a client connection went away (eg. the client application crashed), it was possible for the server to have crashed. This was very rare and timing-dependent. It has now been fixed.

CR:495406

CR Number:   495406 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1182 08 Apr 2008 Fixed Description In SQL Anywhere, the language supported for the definition of manual views is a proper subset of the SQL supported by the server. Further, the language permitted for immediate views is a proper subset of that supported for manual views. A new clause has now been added to the CREATE MATERIALIZED VIEW statement to allow users to validate the statement without actually creating the view. Syntax: CREATE MATERIALIZED VIEW ... [ CHECK { IMMEDIATE | MANUAL } REFRESH ] Syntax Rules: When used, the CHECK clause has the following effect: 1. The server performs the normal language checks that would be carried out if CREATE STATEMENT was executed without the clause and any errors generated are reported returned as usual. 2. The server does not carry out the actual creation of the view which means that certain errors, such as the specified name already existing in the database, are not generated and the CHECK clause can be used even for an existing view. This feature can be useful when a user is considering changing the definition of an existing view but does not know if the new proposed definition will be accepted by the server. 3. If CHECK IMMEDIATE REFRESH is used then the server will also verify that the syntax used is valid for an immediate view and will raise any appropriate errors. 4. The server makes no changes to the database and nothing is recorded in the transaction log. 5. The statement performs an implicit commit at the beginning of execution and a rollback at the end to release all locks obtained during execution.

CR:495506

CR Number:   495506 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) 11.0.0 1171 28 Mar 2008 Fixed 10.0.1 3664 28 Mar 2008 Fixed Description SQL statements that are executed both before and after a SETUSER statement may have ncorrectly referred to the wrong user's objects. For example, if connected as user u1 and the following executed: select * from t; setuser u2; select * from t; then the second SELECT could have incorrectly returned the results for u1.t instead of u2.t. This has been fixed. Setting the database option max_client_satements_cached to 0 will workaround this problem.

CR:495514

CR Number:   495514 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1170 28 Mar 2008 Fixed 9.0.2 3642 28 Mar 2008 Fixed Description The MobiLink system table ml_qa_status_history in a consolidated database would have grown without limit. This happened with all QAnywhere supported consolidated database types. This has been fixed so that when delete rules cause messages to be deleted in the consolidated database, the corresponding rows in the table ml_qa_status_history are now deleted. An existing ASA consolidated database will be automatically upgraded with the fix for this problem. For other consolidated databases, the MobiLink setup script for that database must be executed.

CR:495574

CR Number:   495574 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) 11.0.0 1170 27 Mar 2008 Fixed 10.0.1 3664 27 Mar 2008 Fixed Description The server could have crashed, or failed assertions, when scanning many values from an index containing many and/or wide columns. This has now been fixed.

CR:495578

CR Number:   495578 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1170 28 Mar 2008 Fixed 10.0.1 3664 28 Mar 2008 Fixed Description The method ULDataReader.GetBytes() would have returned null if invoked for a binary(n), or a long binary, column containing an empty string (ie. a zero length not null value). This has been fixed. GetBytes() will now returns a zero length array of bytes.

CR:495677

CR Number:   495677 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1171 27 Mar 2008 Fixed Description The builtin function regexp_substr() could, in some cases, have lead to the following non-fatal assertion failure: 106901 "Expression value unexpectedly NULL in write". This assertion would have failed if the arguments to regexp_substr() were all expressions marked as not-NULL. This has been fixed.

CR:495686

CR Number:   495686 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1171 28 Mar 2008 Fixed Description The server supports an extension to the MERGE statement that allows for an error be raised under certain circumstances. The server will now pay attention to the ERROR clause and generate an error as expected. In addition, the ERROR clause of the MERGE statement has been changed to to use RAISERROR instead.

CR:495700

CR Number:   495700 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1191 28 Apr 2008 Fixed 9.0.2 3654 28 Apr 2008 Fixed 10.0.1 3691 14 May 2008 Fixed Description As of Engineering case 408481, exists() subqueries were not flattened during rewrite optimizations if the subquery contained more than two tables in the FROM clause, and it was not known if the subquery returned at most one row. Now, for a subquery to not be flattened, it must also contain other nested subqueries.

CR:495701

CR Number:   495701 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) 11.0.0 1178 02 Apr 2008 Fixed 10.0.1 4078 02 Jun 2010 Fixed Description The server allows an application to raise a customized error by means of the RAISERROR statement. The server also provides for a built-in global variable, SQLCODE, whose value can be examined to determine the specific error raised during the execution of the last statement on the current connection. The server will now report the correct user specified error number for SQLCODE instead of a fixed -631.

CR:495702

CR Number:   495702 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) 11.0.0 1171 28 Mar 2008 Fixed Description For some column data types in a consolidated database, a new remote database could have been created with inappropriate types. For example, a column with the ASE UNICHAR type was previously mapped to a LONG BINARY column type in a new SQL Anywhere remote database. This has now been corrected. A work around would be to deploy to a SQL file and edit the file using the recommended data type mappings that are documented in this section of the documentation: MobiLink - Server Administration > MobiLink Data Mappings Between Remote and Consolidated Databases

CR:495705

CR Number:   495705 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1216 30 Apr 2008 Fixed 10.0.1 3685 30 Apr 2008 Fixed 9.0.2 3659 30 Apr 2008 Fixed Description When the MobiLink Client was launched using the Dbmlsync Integration Component, it was possible to view the username and password in the dbmlsync command line in plain text. This has been corrected so that the Dbmlsync Integration Component will encrypt all the command line options and settings before passing them to dbmlsync. Dbmlsync will then decrypt the options and settings. Note, this fix does not apply to the Dbmlsync Integration Component running on Windows CE systems.

CR:495872

CR Number:   495872 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1177 31 Mar 2008 Fixed 10.0.1 3667 31 Mar 2008 Fixed Description If a query contained a "GROUP BY GROUPING SETS" or CUBE clause, it was possible for the server to fail the query with an assertion failure such as: 102501 "Work table: NULL value inserted into not-NULL column". The problem would only have occurred for specific query access plans if there were no rows input to the GROUP BY. This has now been fixed.

CR:495929

CR Number:   495929 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) 11.0.0 1181 03 Apr 2008 Fixed 10.0.1 3670 03 Apr 2008 Fixed Description Attempting to execute a query that references a proxy table that contained nchar or nvarchar columns, may have failed assertion 106808. The server was incorrectly setting the semantics to byte length, instead of character length, when describing nchar and nvarchar columns in proxy tables. This problem has now been fixed.

CR:495943

CR Number:   495943 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3645 02 Apr 2008 Fixed Description If the constant 0.0 (one decimal separator and all digits zero) was used in the select list of a SELECT statement, it would have been described as a numeric(0,0), and a SELECT statement with an INTO <permanent_table> clause would have failed with a syntax error. This has been fixed so that the constant 0.0 is now correctly described as numeric(1,0).

CR:495956

CR Number:   495956 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) 11.0.0 1174 31 Mar 2008 Fixed 10.0.1 3667 31 Mar 2008 Fixed Description Executing the statement ALTER DATABASE <dbfile> MODIFY LOG ON, where no transaction log name was specified, would have disabled transaction logging for that database, equivalent to specifying "... LOG OFF". This has been fixed. Including a transaction log filename in the statement would have behaved correctly.

CR:495960

CR Number:   495960 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) 11.0.0 1170 22 Apr 2008 Fixed 10.0.1 3670 22 Apr 2008 Fixed Description In very rare and timing-dependent situations, a cancelled backup could have caused the request, and ultimately the server, to hang. Typically, for this problem to have occurred, the cancel would have had to occur quite quickly after the backup began. This has been fixed.

CR:495962

CR Number:   495962 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) 11.0.0 1177 31 Mar 2008 Fixed 10.0.1 3667 31 Mar 2008 Fixed Description If an application issued a statement like "DELETE FROM t WHERE c = @v", and the table t was a proxy table and @v was a variable of type nchar, nvarchar or long nvarchar, then the query would have failed with a "not enough host variables" error. This problem has now been fixed.

CR:495980

CR Number:   495980 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) 11.0.0 1177 01 Apr 2008 Fixed 10.0.1 3668 01 Apr 2008 Fixed Description In order to optimize database access, the MobiLink scripts can be considered "read-only" when the -f option is specified. In this mode, the ml_global version of scripts would have been checked for changes before each synchronization. This has been corrected so that the check is only done once at startup.

CR:496061

CR Number:   496061 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) 11.0.0 1178 01 Apr 2008 Fixed 10.0.1 3669 01 Apr 2008 Fixed Description If a BEFORE trigger changed an update back to the original value of the row, then the update would still have been logged, even though it was a no-op. This is now only done if a resolve trigger is fired, which matches the behaviour of previous versions.

CR:496068

CR Number:   496068 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) 11.0.0 1178 01 Apr 2008 Fixed 10.0.1 3669 01 Apr 2008 Fixed Description If a DML statement modified a table, and also referred to the table indirectly through a non-inlined procedure call, then anomalies could have occurred. This has been fixed by forcing a work table for any DML statement that references a procedure call.

CR:496071

CR Number:   496071 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) 11.0.0 1186 03 Apr 2008 Fixed 10.0.1 3672 03 Apr 2008 Fixed 9.0.2 3647 03 Apr 2008 Fixed Description The server uses column statistics in order to estimate the number of rows that satisfy a given predicate. The column statistics are maintained as histograms that attempt to capture the data distribution of values in the database for a given column. The server could have incorrectly estimated the selectivity of BETWEEN predicates under certain circumstances. Note that a BETWEEN predicate might be inferred by the server if the query contains appropriate conjunctive predicates. As an example, "c1 >= 5 AND c1 <= 10" is semantically equivalent to "c1 BETWEEN 5 AND 10". This estimation problem has been resolved.

CR:496087

CR Number:   496087 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 3750 07 Nov 2008 Fixed Description In rare instances, assertion failure 201822 "Checkpoint log: attempt to allocate before recovery is complete" could have been reported during database recovery. The problem has been fixed. If this problem is encountered, recovery with a server containing this fix should complete normally.

CR:496094

CR Number:   496094 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) 11.0.0 1178 01 Apr 2008 Fixed 10.0.1 3669 01 Apr 2008 Fixed Description Using the REWRITE() function on a some forms of queries could have resulted in the server going into an infinite loop. This has been fixed.

CR:496102

CR Number:   496102 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1211 25 Apr 2008 Fixed Description The MobiLink server would have sent user authentication status 4000 to a client if it was not able to run the user authentication scripts if errors had already occurred before it had a chance to invoke these scripts, or it could not successfully run the scripts due to errors when executing the scripts, or errors occurred internally in the server. Then the client would generated the error: "Invalid MobiLink username, password, or script version". This has now been fixed. The MobiLink server will send the error code, 11310 and error message "Unable to authenticate the user" to the clients. The long description for this error code is "The MobiLink server was not able to authenticate the user. Please check the MobiLink server message log for more details".

CR:496106

CR Number:   496106 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1198 17 Apr 2008 Fixed 10.0.1 3678 17 Apr 2008 Fixed Description When deploying a Synchronization Model to a Microsoft SQL Server database, in which the name of the table owners were different then the current user's username, an error would have occurred. This has been fixed.

CR:496109

CR Number:   496109 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1210 23 Apr 2008 Fixed Description Creating a synchronization model, where a synchronized remote table did not have all columns synchronized, would have caused a warning that that it was not compatible with an UltraLite remote database, since UltraLite publications can not use column subsets. However, such a synchronization model could still such as: [-10050] "Expecting 8 columns in cursor, but found 7". This has been fixed. Now, synchronization models cannot be deployed to an UltraLite remote database unless all columns are synchronized in the synchronized remote tables.

CR:496110

CR Number:   496110 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 3644 03 Apr 2008 Fixed Description Incorrect results may have been obtained for queries involving GROUP BY, ORDER BY and HAVING clauses, where no indexes exist to implement the grouping and the ordering, and where the grouping was such that the ordering could not have been implied Plans of this situation would have shown two temporary tables being present. This has now been corrected.

CR:496113

CR Number:   496113 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) 11.0.0 1178 02 Apr 2008 Fixed 10.0.1 3669 02 Apr 2008 Fixed Description Under rare circumstances, during diagnostic tracing with the 'plans_with_statistics' tracing level set, query plan information for a DML statement could have been missing. In such cases, viewing the plan for the statement in the Profiling Mode would not be possible. This has been fixed.

CR:496114

CR Number:   496114 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) 11.0.0 1173 03 Apr 2008 Fixed 10.0.1 3670 03 Apr 2008 Fixed Description Graphical plans with detailed statistics that contained an index scan would not have shown values for the statistic CacheReadIndInt, and the values for CacheReadIndLeaf would have included internal and index leaf page reads. This has now been fixed.

CR:496131

CR Number:   496131 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) 11.0.0 1178 03 Apr 2008 Fixed Description Graphical plans with detailed statistics could have contained invalid values for the statistic "Estimated pages in cache". Under rare circumstances, invalid values could also have been displayed for the "Estimated rows", "Estimated pages" and "Estimated row size" statistics. This has been corrected.

CR:496241

CR Number:   496241 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) 11.0.0 1198 17 Apr 2008 Fixed 10.0.1 3678 17 Apr 2008 Fixed Description If application profiling data was stored in an external tracing database, trigger names may not have been attached to the statements executed within the triggers. This has been fixed. Note that the statement data was still saved in the tracing database - it was just not linked to the trigger, and was displayed in the Profiling mode in the Details tab with "Procedure or Trigger Name" set to NULL.

CR:496242

CR Number:   496242 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1188 07 Apr 2008 Fixed Description For Microsoft SQL Server's new datatypes VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX), a new remote database could have been created with inappropriate types. Micrsoft's ODBC driver returns the same metadata for VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX) as for TEXT, NTEXT, and IMAGE, but with a size of 0. This has been fixed so that new remote databases will now be created with correct types. A check has been added for a size of 0 on these particular data types in order to identify them correctly. A workaround would be to use datatypes TEXT, NTEXT, and IMAGE which correspond to the new datatypes.

CR:496281

CR Number:   496281 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 1963 24 Sep 2008 Fixed 11.0.0 1538 20 Nov 2008 Fixed Description The ml_remote_id option would have incorrectly been set to the string value 'null' when reset using the UltraLite plugin. This has been fixed.

CR:496407

CR Number:   496407 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1199 17 Apr 2008 Fixed 10.0.1 3678 17 Apr 2008 Fixed 9.0.2 3653 17 Apr 2008 Fixed Description In exeptionally rare circumstances, the server may have crashed trying to collect information about database pages to be loaded (cache warming) the next time the database was started. This has been fixed.

CR:496429

CR Number:   496429 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) 11.0.0 1181 04 Apr 2008 Fixed 10.0.1 3670 04 Apr 2008 Fixed Description Graphical plans for Group By queries that were executed in parallel, did not report group by expressions or aggregates in the tooltip and details pane for GroupBy below Exchange. This has been fixed.

CR:496435

CR Number:   496435 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1181 04 Apr 2008 Fixed 10.0.1 3670 04 Apr 2008 Fixed Description An application using the iAnywhere JDBC driver on Unix systems, could have crashed when making a connection. This problem has now been fixed.

CR:496438

CR Number:   496438 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1181 03 Apr 2008 Fixed 10.0.1 3670 03 Apr 2008 Fixed 9.0.2 3645 03 Apr 2008 Fixed Description An application using the iAnywhere JDBC driver, that had many threads that were opening and closing connections or statements, may have crashed during garbage collection. This problem has now been fixed.

CR:496439

CR Number:   496439 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) 11.0.0 1181 04 Apr 2008 Fixed Description When a database application attempted to use a feature that had been secured, using the -sf server option, the error message that resulted did not state the correct feature name. This problem has been fixed.

CR:496450

CR Number:   496450 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) 11.0.0 1215 29 Apr 2008 Fixed 10.0.1 3685 29 Apr 2008 Fixed Description Attempting to execute an ALTER TABLE statement to add a computed column that involved a Java call would have caused the server to either fail to start the Java VM, or to hang. This problem has now been fixed.

CR:496453

CR Number:   496453 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1208 23 Apr 2008 Fixed Description The Connect Assistant would have failed to find servers if they were on a different subnet. This has been fixed.

CR:496526

CR Number:   496526 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) 11.0.0 1189 11 Apr 2008 Fixed 10.0.1 3675 11 Apr 2008 Fixed Description When inserting rows using an opened cursor, rather than using an INSERT statement, computed columns would not have been properly evaluated. This has been fixed.

CR:496538

CR Number:   496538 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) 11.0.0 1190 14 Apr 2008 Fixed 10.0.1 3676 14 Apr 2008 Fixed Description The Interactive SQL utility dbisql would have reported an internal error when attempting to open a SQL file which was larger than about 5 MB. This has been fixed so that it now an reports an error saying that there was not enough memory to open the file.

CR:496545

CR Number:   496545 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1182 07 Apr 2008 Fixed 10.0.1 3670 07 Apr 2008 Fixed Description The Certificate Creation utility createcert would have generated invalid server certificates when signing them using a CA certificate generated by gencert (the previous certificate generation utility). Although the server certificate itself looked fine, clients would not have been able to properly identify the trusted CA certificate that signed it, and so it would have been rejected as untrusted, even when the client had the correct CA certificate in its list of trusted CAs. This has been fixed.

CR:496546

CR Number:   496546 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1182 08 Apr 2008 Fixed Description Using a CONTAINS search in a SELECT INTO could have failed with an error, or caused the server to crash. This is now fixed.

CR:496551

CR Number:   496551 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1084 07 Apr 2008 Fixed Description Changing a Materialized View and then refreshing the folder, would have caused the plug-in to throw a NullPointer Exception. This has been fixed

CR:496567

CR Number:   496567 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3664 04 Apr 2008 Fixed Description The MobiLink system table ml_qa_status_history in a consolidated database would have grown without limit. The problem only occurs for ASE consolidated databases. To correct this in existing ASE consolidated databases, the trigger ml_qa_repository_trigger needs to be changed by running the following script on the consolidated database after it has been initialized with the MobiLink setup script: delete from ml_qa_status_history where msgid not in (select msgid from ml_qa_repository) go commit go drop trigger ml_qa_repository_trigger go create trigger ml_qa_repository_trigger on ml_qa_repository for delete as delete from ml_qa_repository_props from deleted d, ml_qa_repository_props p where d.msgid = p.msgid delete from ml_qa_delivery from deleted d, ml_qa_delivery p where d.msgid = p.msgid delete from ml_qa_status_history from deleted d, ml_qa_status_history p where d.msgid = p.msgid go

CR:496568

CR Number:   496568 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1182 07 Apr 2008 Fixed 10.0.1 3670 12 May 2008 Fixed Description The iAS ODBC driver for Oracle could have shown poor performance when concurrent access was required by multi-threaded applications, such as the MobiLink server. This problem has been corrected.

CR:496715

CR Number:   496715 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1185 08 Apr 2008 Fixed Description Very rarely, a query that used index only retrieval, together with snapshot isolation, may have returned a wrong result. This has been corrected

CR:496719

CR Number:   496719 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) 11.0.0 1206 21 Apr 2008 Fixed 10.0.1 3682 21 Apr 2008 Fixed Description When rebuilding, by unloading and reloading, a version 9.0 database that had Remote Data aAcess servers defined, there was a possibility that the reload would have failed with a "capability 'aes_encrypt' not found" error. This problem has now been fixed. The workaround is to edit the reload script and change all occurrences of 'aes_encrypt' to 'encrypt'.

CR:496762

CR Number:   496762 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1185 08 Apr 2008 Fixed Description If a database being unloaded was created with accent sensitivity on, or "french", the CREATE DATABASE statement included in the reload.sql file created by dbunload would not have contained the ACCENT RESPECT, or ACCENT FRENCH, clause. This has been fixed.

CR:496897

CR Number:   496897 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1186 09 Apr 2008 Fixed 10.0.1 3673 09 Apr 2008 Fixed 9.0.2 3647 09 Apr 2008 Fixed Description An application using the iAnywhere JDBC driver would have leaked memory when making multiple DatabaseMetaData calls. The driver was not releasing references to Java strings. This problem has been fixed.

CR:496899

CR Number:   496899 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1186 08 Apr 2008 Fixed 10.0.1 3673 08 Apr 2008 Fixed 9.0.2 3647 08 Apr 2008 Fixed Description An application using the iAnywhere JDBC driver would have leaked memory when executing statements that returned multiple result sets. Executing statements that return a single result set will not be affected by this problem. The driver was failing to implicitly close pending result sets for statements that returned multiple result sets. This has now been fixed.

CR:496906

CR Number:   496906 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3647 08 Apr 2008 Fixed Description The server, and client applications, would have leaked memory on Solaris SPARC 64-bit and Solaris x64 when negotiating a shared memory connection. This has been fixed.

CR:496921

CR Number:   496921 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) 11.0.0 1189 11 Apr 2008 Fixed Description When deploying a synchronization model to an encrypted database, the encryption key would have been visible in the messages dialog, as well as in the scripts generated for the remote database. This has been fixed by trimming the DBKEY out of the connection string.

CR:496937

CR Number:   496937 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 3674 09 Apr 2008 Fixed 10.0.0 2908 09 Apr 2008 Fixed Description When run on Mac OS X systems, an IndexOutOfBoundsException could have been thrown when navigating the object tree. This has been fixed.

CR:496969

CR Number:   496969 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Windows CE 2.11 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1200 18 Apr 2008 Fixed 10.0.1 3679 18 Apr 2008 Fixed 9.0.2 3654 18 Apr 2008 Fixed Description When the QAnywhere Agent was running on a device that was not connected to a network, each time a QAnywhere application queued a message the CPU usage increased slightly. This has been fixed so that now, when the device is not connected to a network, queueing a message uses about the same amount of CPU regardless of whether or not the QAnywhere Agent is running. Moreover, the required CPU usage stays constant as messages are queued.

CR:497105

CR Number:   497105 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) 11.0.0 1188 11 Apr 2008 Fixed 10.0.1 3675 11 Apr 2008 Fixed Description If request log filtering by database was enabled using: call sa_server_option('RequestFilterDB', <db-id> ) query plans from statements executed on other databases on the same server would still have appeared in the request log. This has been fixed.

CR:497114

CR Number:   497114 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1190 14 Apr 2008 Fixed Description Executing the system procedure sa_materialized_view_can_be_immediate() with the name and owner of an immediate materialized view that had a definition containing a LIKE 'x%' predicate, could have failed with an error that the view was not eligible to be an immediate materialized view. This has been fixed.

CR:497117

CR Number:   497117 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1212 28 Apr 2008 Fixed 10.0.1 3683 28 Apr 2008 Fixed Description Applications could have crashed after specific sequences of PREPAREs and EXECUTEs, or OPENs, if the option max_statement_count was increased from its default value. In particular, for the crash to have occurred a connection must have done at least 50 PREPAREs, then at least 500 EXECUTEs or OPENs, then have had at least 50 statements concurrently prepared or opened. This has been fixed.

CR:497121

CR Number:   497121 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) 11.0.0 1194 16 Apr 2008 Fixed 10.0.1 3677 16 Apr 2008 Fixed Description In some cases, actual node statistics were not reported for 'hash filter' and 'hash filter parallel' in graphical plan with detailed statistics, including node statistics. Also, in some cases actual statistics were not reported for recursive unions. This has been fixed.

CR:497256

CR Number:   497256 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1194 11 Apr 2008 Fixed 10.0.1 3677 11 Apr 2008 Fixed 9.0.2 3650 11 Apr 2008 Fixed Description When calling the ODBC function SQLGetInfo(), the driver will return an indication that conversion from SQL_VARCHAR to SQL_WVARCHAR is possible using the ODBC CONVERT function. For example: rc = SQLGetInfo(hdbc, SQL_CONVERT_VARCHAR, (SQLPOINTER)&bitmask, sizeof(bitmask), NULL); This will return with the SQL_CVT_WVARCHAR bit set in bitmask which indicates that the conversion is possible. However, attempting to do the conversion will return an error. This is illustrated by the preparing the following statement for execution: SELECT {fn CONVERT(Surname,SQL_WVARCHAR)} FROM Employees The error is "[42000][Sybase][ODBC Driver]Syntax error or access violation". This problem has been fixed. Support has been added for conversion to types SQL_WCHAR, SQL_WLONGVARCHAR, SQL_WVARCHAR, and SQL_GUID.

CR:497264

CR Number:   497264 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) 11.0.0 1189 11 Apr 2008 Fixed 10.0.1 3675 11 Apr 2008 Fixed Description In rare cases, an HTTP request with a SessionID may have caused the server to crash. This has been fixed.

CR:497458

CR Number:   497458 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1189 11 Apr 2008 Fixed 10.0.1 3676 11 Apr 2008 Fixed Description Undefined errors could have occurred if ULDatabaseManager::CreateDatabase() was called with a null collation. This has been fixed so that a SQLE_INVALID_PARAMETER ULException will now be thrown for a null collation.

CR:497467

CR Number:   497467 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) 11.0.0 1190 11 Apr 2008 Fixed 10.0.1 3676 11 Apr 2008 Fixed 9.0.2 3650 11 Apr 2008 Fixed Description The unparsing of an alias was incorrect in some cases. The alias was represented as a '*' in an unparsed statement. This may have been observed in plans generated when using the -zx server command line option to log expensive queries. This has been fixed.

CR:497495

CR Number:   497495 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 3688 06 May 2008 Fixed Description The OUTPUT statement was writing DECIMAL numbers with thousands separators. This was an inadvertent change from previous versions and caused an ambiguity when writing ASCII files if the field separator was the same as the thousands separator. This has been fixed.

CR:497501

CR Number:   497501 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1176 14 Apr 2008 Fixed Description The server was ignoring the correlation name of columns in the column list of the INSERT statement. This has been fixed so that if the correlation name exists and it doesn't match the name of the INSERT INTO table, then the error (SQLSTATE_COLUMN_NOT_FOUND 52003 -143L) is now returned. Example: INSERT INTO R ( T.X, R.Y) values (1,2) will now return an error because the column T.X cannot be found.

CR:497502

CR Number:   497502 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) 11.0.0 1190 14 Apr 2008 Fixed 10.0.1 3676 14 Apr 2008 Fixed Description If an application that was using Java in the database support spawned additional threads that were still running when the database was shut down, then the JVM would havel continued running until these additional threads shut down. This problem has now been fixed. Note, if the application needs these threads to be notified of the shutdown, then the application must register a shutdown hook with the Java VM.

CR:497504

CR Number:   497504 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) 11.0.0 1190 14 Apr 2008 Fixed 10.0.1 3676 14 Apr 2008 Fixed 9.0.2 3650 14 Apr 2008 Fixed Description If an application that was using Remote Data Access support executed a remote query that was very complex, then there was a possibility that the server would have crashed. This problem has been fixed.

CR:497511

CR Number:   497511 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1195 17 Apr 2008 Fixed 10.0.1 3677 17 Apr 2008 Fixed Description The diagnosis of invalid GROUP BY expressions has been enhanced.

CR:497515

CR Number:   497515 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1190 14 Apr 2008 Fixed 10.0.1 3676 14 Apr 2008 Fixed Description The Interactive SQL utility dbisql could have crashed on startup if it been configured to enable source control support. The crash depended on using the default Windows source control system (i.e. NOT the "custom" option), and would only have occurred if the source control system asked dbisql to display a message in response to opening the source control project. This has now been fixed.