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

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

CR:544787

CR Number:   544787 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 1504 23 Sep 2008 Fixed 11.0.1 1963 27 Nov 2008 Fixed Description If a statement required rows to be sorted and at least two rows had long ORDER BY key values that were equal in the first 256 bytes and the statement was executed with a parallel access plan, it was possible for the two rows to be returned in an order that did not match the ORDER BY clause. This problem has been fixed. Note, it was possible for text indexes that contain long search terms to be affected by this problem when the text index was built or updated. If this occured, the index should be rebuilt with a server containing this fix.

CR:544791

CR Number:   544791 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 1502 24 Sep 2008 Fixed 10.0.1 3771 24 Sep 2008 Fixed 9.0.2 3730 24 Sep 2008 Fixed 11.0.1 1961 27 Nov 2008 Fixed Description In rare timing dependent cases, the server could have hung on shutdown, or possibly failed in other ways, after executing a DROP CONNECTION statement. This has now been fixed.

CR:544925

CR Number:   544925 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 1503 23 Sep 2008 Fixed 11.0.1 1962 27 Nov 2008 Fixed Description A connection may have continued to hold table or row locks even when a DDL statement failed. This has been fixed.

CR:544938

CR Number:   544938 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) 24 Sep 2008 Fixed Description The server supports the [NOT] DETERMINISTIC specification for user defined functions. When used for stored procedures the clause would have failed to generate the expected syntax error. Instead the clause was accepted and then ignored by the server. This has been fixed so that the server will now generate a syntax error when [NOT] DETERMINISTIC is used in the CREATE and ALTER PROCEDURE statements.

CR:544943

CR Number:   544943 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) 11.0.0 1503 23 Sep 2008 Fixed 10.0.1 3769 23 Sep 2008 Fixed 11.0.1 1962 27 Nov 2008 Fixed Description The MobiLink server could have hung, or crashed, when using encrypted streams. The behaviour was highly dependent on both timing and data size. This has now been fixed.

CR:544944

CR Number:   544944 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 1503 23 Sep 2008 Fixed 11.0.1 1962 27 Nov 2008 Fixed Description When calling sp_remote_tables() to get the column information for an UltraLite table, any unsigned columns would have been described as signed columns. This problem has been fixed.

CR:544948

CR Number:   544948 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 1516 15 Oct 2008 Fixed 10.0.1 3780 15 Oct 2008 Fixed 11.0.1 1981 27 Nov 2008 Fixed Description The system function xp_sendmail() would have always encoded the subject line of an email being sent. While this is properly decoded when the email is delivered to an email client, it was not decoded in many instances when sent via SMS. A change has been made to not encode the subject line when the subject contains only 7-bit ascii characters. Attempting to send a message containing non 7-bit ascii characters to a SMS client will still result in the subject line being encoded. It will be up the carrier to properly convert from SMTP to SMS.

CR:544956

CR Number:   544956 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1510 01 Oct 2008 Fixed 10.0.1 3773 01 Oct 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description If MobiLink Client was performing a synchronization, and the status of the last synchronization was unknown, it was possible for the MobiLink Server to have reported that the synchronization had started twice. The MobiLink Log with no extra verbosity might contain the following messages: Request from "Dbmlsync Version 10.0.1.3750" for: remote ID: rem1, user name: rem1, version: v1 Request from "Dbmlsync Version 10.0.1.3750" for: remote ID: rem1, user name: rem1, version: v1 Synchronization complete This problem has been fixed.

CR:544961

CR Number:   544961 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 1503 24 Sep 2008 Fixed 10.0.1 3770 24 Sep 2008 Fixed 11.0.1 1962 27 Nov 2008 Fixed Description The Stored Procedure Debugger was not able to set breakpoints on statements within exception handlers. This has been fixed.

CR:544969

CR Number:   544969 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) 24 Sep 2008 Fixed Description UltraLite treated all cursors declared in embedded SQL as being FOR UPDATE. A query with the FOR READ ONLY clause could still have been updated as the clause was ignored. This has now now fixed. Also with this fix, UltraLite embedded SQL cursors are now considered read only if no clause is present. The previous behaviour can be achieved with sqlpp m HISTORICAL.

CR:544972

CR Number:   544972 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 1511 26 Sep 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description The server could have crashed while optimizing a text query containing a phrase. This has been fixed.

CR:545000

CR Number:   545000 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1504 02 Oct 2008 Fixed 11.0.1 1963 27 Nov 2008 Fixed Description SELECT DISTINCT with more than 16 select-list items would have caused an exception to be thrown. A DISTINCT optimization should have tested that there were 16 or fewer select-list items and failed when that was not so. The omitted test has now been added.

CR:545096

CR Number:   545096 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3767 24 Sep 2008 Fixed Description The latest release of the Perl, PHP, etc language drivers now use the C API that was released with SQL Anywhere 11.0. To allow those new drivers to be backward compatible with 10.0.1, support has been added for this new C API to 10.0.1. Note that the language drivers that ship with 10.0.1 EBFs will continue to be the ESQL version.

CR:545105

CR Number:   545105 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1504 25 Sep 2008 Fixed 11.0.1 1963 27 Nov 2008 Fixed Description The DatabaseInfo methods getDbFormat and getRelease, would have returned incorrect values. Additionally, getRelease now returns a String which reflects both the release version and the build number.

CR:545251

CR Number:   545251 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) 11.0.0 1509 01 Oct 2008 Fixed 10.0.1 3773 01 Oct 2008 Fixed 11.0.1 1967 27 Nov 2008 Fixed Description The MobiLink Listener (dblsn), with IP tracking off (-ni) or default UDP listening off (-nu), may have shutdown unexpectedly after the first notification. This problem was introduced by the changes made for Engineering case 535235. This has now fixed.

CR:545353

CR Number:   545353 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.1 2127 24 Nov 2008 Fixed 10.0.1 3796 12 Dec 2008 Fixed Description The cardinality estimation of the table expression "P key join F", where P is the primary key table and F is the foreign key table, was incorrectly computed in certain cases for multi-column keys. This has been fixed. Now, the cardinality estimation for this class of table expressions is "card(F) \ #of rows in F with at least one NULL value for multi-column key". Example: ALTER TABLE FOREIGN KEY ( fk1, fk2, ..., fkn) references P (pk1, pk2,..., pkn) Q: select * from F, P where F.fk1 = P.pk1 and F.fk2 = P.pk2 and ... and F.fkn = P.pkn returns all rows from the foreign key table F less the rows having at least one NULL for the foreign key columns F.fk1, F.fk2, ..., F.fkn.

CR:545374

CR Number:   545374 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1509 29 Sep 2008 Fixed 10.0.1 3773 29 Sep 2008 Fixed 9.0.2 3732 29 Sep 2008 Fixed 11.0.1 1968 27 Nov 2008 Fixed Description When using the SQL Anywhere ODBC driver, if SQLBindCol was called immediately after a SQLFetch and before calling SQLBulkOperations( SQL_UPDATE_BY_BOOKMARK ), then the SQLBulkOperations update would have failed. This problem has been fixed.

CR:545383

CR Number:   545383 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 1512 07 Oct 2008 Fixed 10.0.1 3775 07 Oct 2008 Fixed 11.0.1 1971 27 Nov 2008 Fixed Description Queries accessing a table via an index could have performed poorly after performing many update and delete operations on the indexed table. If two leaf pages that required cleaning were merged, the second of the two would not have been cleaned, which could have resulted in many almost empty leaf pages. This has been fixed.

CR:545454

CR Number:   545454 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1509 29 Sep 2008 Fixed 11.0.1 1968 27 Nov 2008 Fixed Description The Interactive SQL utility (dbisql) could have crashed if the iAnywhere JDBC-ODBC driver was not installed correctly. This has been changed so that dbisql gives an error message instead.

CR:545455

CR Number:   545455 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 1515 08 Oct 2008 Fixed 10.0.1 3778 08 Oct 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description A server started with the -zl or -zp command line options (or by calling the system procedure sa_server_option() with RememberLastStatement or RememberLastPlan), that services large numbers of HTTP connections could have crashed. This issue would have been rare and highly timing dependent. This has now been fixed.

CR:545463

CR Number:   545463 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2141 01 Oct 2008 Fixed 11.0.0 1565 27 Nov 2008 Fixed Description The Interactive SQL utility (dbisql) would have crashed if a START DATABASE ... ON statement was executed when it was not connected, and had never been connected. This has been fixed.

CR:545468

CR Number:   545468 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 1510 01 Oct 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description Calling either of the system procedures sa_http_php_page() or sa_http_php_page_interpreted() would have resulted in a leading and a trailing space in the output. This has been corrected.

CR:545516

CR Number:   545516 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) 11.0.0 1511 01 Oct 2008 Fixed 10.0.1 3517 08 Oct 2008 Fixed Description The MobiLink server now requires the ASE native ODBC driver, version 15.0.0.320, which can be retrieved from the Sybase Software Developer Kit - 15 ESD #14, for consolidated databases running on ASE 12.5 or ASE 15.0 database servers. This is required due to a bug in the older versions of the ASE native ODBC driver, that has now been fixed.

CR:545519

CR Number:   545519 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 1506 02 Oct 2008 Fixed 11.0.1 1965 27 Nov 2008 Fixed Description The changes for Engineering case 541942 could have cause GLOBAL TEMPORARY tables to be created in the SYSTEM dbspace during database creation. Only databases created by a server with this problem are affected, and can be corrected by rebuilding with a fixed server. This problem has two visible results: Firstly, diagnostic tracing into a local database will cause the database to grow twice as large as expected due to diagnostic data. It will be necessary to rebuild a database this problem in order to prevent this growth from happening with subsequent builds. Secondly, JDBC metadata that is supposed to be unique to each connection will end up being visible to all connections. This can cause a variety of problems for applications that depend on querying this metadata. This manifestation of the problem can be avoided by running dbupgrad with a fixed server against a database with this problem. The presence of this problem in a database can be verified by querying SYSTABLE and noting that all jdbc_* tables have type of BASE.

CR:545528

CR Number:   545528 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.1 2050 01 Oct 2008 Fixed 10.0.1 3752 15 Dec 2008 Fixed Description Inexpensive statements may have taken a long time to optimize (i.e. OPEN time was high), or may have had inefficient access plans. This has now been fixed. The only condition required for this to happen was that the parallel access plans were considered by the optimizer. For more info on intra-query parallelism see: SQL Anywhere Server - SQL Usage Query Optimizer Query optimization and execution Query execution algorithms Parallelism during query execution This change is particularly important when moving to version 11.0.1, from 10.0.1 or 11.0.0, and running the personal server (dbeng11). The 10.0.1 personal server (dbeng10) and 11.0.0 personal server (dbeng11) are restricted to using only one CPU, and only one core if the CPU has multiple cores. Also, the 10.0.1 optimizer did not consider the number of maximum concurrent threads (i.e. ConcurrentThreads global variable), and may generate parallel plans which will not be executed in parallel by the 10.0.1 personal server, only one parallel branch will process all the rows. This is a bug which was fixed in 11.0.0 GA. The 11.0.1 personal server can use all the cores available in one CPU, which means the 11.0.1 optimizer will cost and generate access plans using parallel physical operators when multiple cores are available. This difference in behaviour related to the number of cores allowed to be used by the personal server may result in a very different access plan being executed by 11.0.1 compared to the access plan executed by 11.0.0, for the same SQL statement.

CR:545543

CR Number:   545543 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) 11.0.0 1510 01 Oct 2008 Fixed 10.0.1 3773 01 Oct 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description Unloading and reloading a 9.0.2 db could have failed with a 'capability not found' error if the 9.0.2 db had remote servers defined and contains capabilities that do not exist in later versions. This problem has now been fixed. The unload/reload scripts now check for the existence of each capability in SYSCAPABILITYNAME prior to issuing the ALTER SERVER ... CAPABILITY statement.

CR:545546

CR Number:   545546 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1510 02 Oct 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description When using the Create Database wizard, if a collation's punctuation sensitivity was changed to a value other than its default, then the wizard would have failed to create the database. This has been fixed.

CR:545565

CR Number:   545565 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1510 02 Oct 2008 Fixed 10.0.1 3773 02 Oct 2008 Fixed 11.0.1 1969 27 Nov 2008 Fixed Description When an application called the ODBC fuction SQLTables() to get a list of supported table types, the TEXT table type would not have been listed. In addition, calling SQLTables() to list tables would have incorrectly listed tables of type TEXT as LOCAL TEMPORARY. Similarly, when an application using the iAnywhere JDBC driver called DatabaseMetaData.getTableTypes() to get a list of supported table types, the TEXT table type would not have been listed; and calling DatabaseMetaData.getTables() would have incorrectly identified TEXT tables as LOCAL TEMPORARY. Both the ODBC driver and JDBC driver have now been updated to properly list the TEXT table type and identify tables of type TEXT correctly.

CR:545570

CR Number:   545570 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 1523 24 Oct 2008 Fixed 10.0.1 3788 24 Oct 2008 Fixed 11.0.1 1995 27 Nov 2008 Fixed Description The server could have crashed while inserting rows to a table when also creating statistics on the table. This has been fixed.

CR:545574

CR Number:   545574 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 1512 03 Oct 2008 Fixed 10.0.1 3774 03 Oct 2008 Fixed 11.0.1 1971 27 Nov 2008 Fixed Description In certain circumstances, TLS connections that should have failed, would have actually succeed. This has been fixed. Note that this problem does not occur on Mac OS X systems.

CR:545611

CR Number:   545611 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 1511 03 Oct 2008 Fixed 11.0.1 1970 27 Nov 2008 Fixed Description In some rare cases, errors during execution of a DROP TABLE or DROP MATERIALIZED VIEW statement, could have resulted in locks being held for too long. This has been fixed.

CR:545621

CR Number:   545621 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 3774 02 Oct 2008 Fixed Description The server may crash after a materialized view has been dropped. This has been fixed.

CR:545627

CR Number:   545627 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1511 02 Oct 2008 Fixed 11.0.1 1970 27 Nov 2008 Fixed Description Clicking the "File/Run Script" menu item to run a script file could have caused the Interactive SQL utility to crash with an "Out of memory" error. This has been fixed so that a more ordinary error message is displayed, and running the script is gracefully aborted. This problem could have occurred when the script was very large (thousands of lines) and especially if it contained unclosed block statements.

CR:545640

CR Number:   545640 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) 07 Oct 2008 Fixed Description Attempting to set an HTTP header from within an inner procedure would have resulted in a SQL error indicating that setting of the HTTP header was invalid. This has been fixed so that inner procedures may now modify HTTP response headers. For example: With this fix an HTTP request to the SUB service now succeeds in setting the User-Header within the SUB1 function. create service sub type 'raw' authorization off secure off user dba as call sp_sub(); create procedure sp_sub() begin select sub1(); end; create function sub1() returns long varchar begin call sa_set_http_header('User-Header', 'test'); return 'test'; end;

CR:545641

CR Number:   545641 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1511 02 Oct 2008 Fixed 11.0.1 1970 27 Nov 2008 Fixed Description The Interactive SQL utility (dbisql) could have crashed if the Query Editor window was open and the database connection was lost. This has been fixed.

CR:545646

CR Number:   545646 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) 11.0.0 1511 02 Oct 2008 Fixed 10.0.1 3774 02 Oct 2008 Fixed 11.0.1 1970 27 Nov 2008 Fixed Description Creating a new connection profile by copying an existing profile, could have resulted in the copy having the wrong plugin type. This has been fixed.

CR:545684

CR Number:   545684 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 3771 02 Oct 2008 Fixed Description When optimizing simple SQL statements the server was skipping some of the optimizations implemented to improve DESCRIBE time. This has been corrected. For more information see: SQL Anywhere Server - SQL Usage Query Optimizer Query optimization and execution Query processing phases

CR:545690

CR Number:   545690 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1512 02 Oct 2008 Fixed 10.0.1 3775 02 Oct 2008 Fixed 11.0.1 1972 27 Nov 2008 Fixed Description When a message was sent to a destination alias, the QAnywhere Server may not have immediately generated push notifications for some members of the alias. This could have resulted in the server taking as long as a minute to push notifications to clients. This has been fixed.

CR:545704

CR Number:   545704 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 1512 02 Oct 2008 Fixed 10.0.1 3775 02 Oct 2008 Fixed 11.0.1 1972 27 Nov 2008 Fixed Description When trying to create a Transact-SQL function or procedure, use of the "expr AS name" syntax in the arguments to a function call would have given an error. This has been fixed. A workaround is to write the function or procedure using the Watcom-SQL dialect.

CR:545707

CR Number:   545707 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 1512 02 Oct 2008 Fixed 10.0.1 3775 02 Oct 2008 Fixed 11.0.1 1972 27 Nov 2008 Fixed Description When running on Unix systems, the server could have hung and not proceeded any further while generating a mini-core. This has been fixed.

CR:545713

CR Number:   545713 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 1512 03 Oct 2008 Fixed 11.0.1 1972 27 Nov 2008 Fixed Description On Mac OS X systems, the function sqlany_initialize_interface() in sqlanydll.c would have failed if it attempted to use the default library name (that is, if the second argument to the function was NULL and the environment variable SQLANY_API_DLL was not set). This was due to the default library name having the wrong extension ('so' as opposed to 'dylib'). This has been fixed. As a workaround, the correct library name can be specified in the second argument to sqlany_initialize_interface, the environment variable SQLANY_API_DLL can be set to the correct library name, or the extension can be manually changed in the DEFAULT_LIBRARY_NAME macro in sacapidll.c.

CR:545744

CR Number:   545744 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 1512 03 Oct 2008 Fixed 11.0.1 1972 27 Nov 2008 Fixed Description The server may found, and used, the wrong license file when starting up. This has been corrected. Note: if the server now reports a "License file not found" error after applying this fix, when it started prior to the fix, then the license file was not correctly installed. To correct this, the license file should be moved so that it is in the same directory as the server executable.

CR:545760

CR Number:   545760 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1513 03 Oct 2008 Fixed 11.0.1 1973 28 Nov 2008 Fixed Description The SQL tab for a Trigger, View, Procedure or Event could have contained stale SQL, if the object's SQL was modified and saved to the database in a separate window (opened using the "Edit in New Window" menu item). The problem would only have occurred when the object's SQL tab was displayed in the right pane before the object was modified and saved to the database in the separate window, and the object's SQL was modified and saved to the database in the separate window while the object's SQL tab was not displayed in the right pane of the main Sybase Central window. A similar problem would have occurred if a maintenance plan was modified after having shown its corresponding event's SQL tab. The event's SQL tab would have displayed stale SQL. In both cases, pressing F5 to refresh Sybase Central would have show the object's up-to-date SQL. Pressing F5 is now no longer necessary, as Sybase Central has been corrected to keep such objects' SQL up-to-date.

CR:545762

CR Number:   545762 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) 11.0.0 1515 06 Oct 2008 Fixed 10.0.1 3779 06 Oct 2008 Fixed 11.0.1 1979 28 Nov 2008 Fixed Description The MobiLink system stored procedures for DB2 Mainframe were created with a default isolation level of RR (Repeatable Read = Serializable) instead of CS (Cursor Stability = Read Committed). This has been fixed.

CR:545772

CR Number:   545772 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1513 03 Oct 2008 Fixed 10.0.1 3777 03 Oct 2008 Fixed 11.0.1 1973 28 Nov 2008 Fixed Description If an application was connected using the iAnywhere JDBC driver, and the application subsequently executed a statement that returned more than one result set, then attempting to fetch any result set after the first would have failed with a function sequence error. This problem would only have appeared once the fix for Egineering case 533936 was applied. This has now been fixed.

CR:545785

CR Number:   545785 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 3779 08 Oct 2008 Fixed Description If a SELECT statement referenced a single table and contained a TOP n or FIRST clause, it was possible for a slow execution plan to be picked. In order for this to have occurred, there needed to be at least two indexes that could be used for the plan and the depth of the indexes needed to differ. This has been fixed.

CR:545815

CR Number:   545815 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 1513 06 Oct 2008 Fixed 10.0.1 3777 06 Oct 2008 Fixed 11.0.1 1973 28 Nov 2008 Fixed Description The database server could have leaked memory, and eventually failed with an 'Out of Memory' error, when using TDS connections (eg. jConnect) that fetched string data. This has now been fixed. This fix is in addition to the memory leak that was fixed for Engineering case 543069.

CR:545824

CR Number:   545824 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 1513 06 Oct 2008 Fixed 11.0.1 1973 28 Nov 2008 Fixed Description When doing dynamic cache size tuning, the server could have choosen a cache size which was larger than appropriate. This could have caused performance degradation if other system components were competing for memory. The server was erroneously basing target cache size computations on the server's "peak" working set size, rather than its "current" working set size. This has been corrected.

CR:545899

CR Number:   545899 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 1514 07 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description For particular structures of tables and indexes, it was possible for an ALTER TABLE statement to fail with an assertion failure such as the following: Assertion failed: 201501 - Page for requested record not a table page or record not present on page This has been fixed.

CR:545901

CR Number:   545901 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 1518 15 Oct 2008 Fixed 10.0.1 3782 15 Oct 2008 Fixed 11.0.1 1986 28 Nov 2008 Fixed Description If an application called an external environment procedure immediately after issuing a commit, and the external environment procedure performed server side calls and issues its own commit, then there was a chance the server will have failed assertion 201501 "Page for requested record not a table page or record not present on page". This problem has now been fixed.

CR:545902

CR Number:   545902 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1514 06 Oct 2008 Fixed 11.0.1 1976 28 Nov 2008 Fixed Description If The Interactive SQL utility (dbisql) could not load the DBLIB library it would have crashed, rather than reporting the problem and degrading gracefully. This has been fixed.

CR:545912

CR Number:   545912 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1490 21 Oct 2008 Fixed 11.0.1 1992 28 Nov 2008 Fixed Description The original release of the Express Bug Fix for 11.0.0 1490 would have failed to install on non-English Windows systems. This has been fixed.

CR:545917

CR Number:   545917 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1512 06 Oct 2008 Fixed 11.0.1 1972 28 Nov 2008 Fixed Description When the Relay Server (rshost) or the Relay Server Outbound Enabler (rsoe) RSHOST executables printed the usage message, empty lines and/or garbage characters could have been displayed after the usage message. This has now been fixed.

CR:545933

CR Number:   545933 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 1517 16 Oct 2008 Fixed 10.0.1 3781 16 Oct 2008 Fixed 11.0.1 1981 28 Nov 2008 Fixed Description Attempting to backup a database of size 5GB or larger with the clause "WAIT BEFORE START" could have caused the server to hang. Backups of databases this size and larger cause the server to calibrate the dbspaces, which is done to improve the parallel performance of the backup. However, if the calibration updated the catalog, then the WAIT BEFORE START clause would have caused the backup to wait on itself. This has been fixed by turning off calibration for large databases when the WAIT BEFORE START clause is specified. If desired, the CALIBRATE DATABASE statement can be issued before the backup begins. A workaround is to run the backup without the WAIT BEFORE START clause.

CR:545934

CR Number:   545934 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 1514 07 Oct 2008 Fixed 11.0.1 1976 28 Nov 2008 Fixed Description A database could have failed validation before a checkpoint, and then passed validation after a checkpoint. A possible message that may have been generated in this case was "Database validation failed for page nnnnnn of database file '<file.db>'". In cases such as this, the database was in fact valid, but the validation step was falsely reporting failure. This has been fixed, although there is still a small possibility that when run on an active database, the validation step could still report errors. It is recommended that, where possible, validation occur when there is little or no database activity. A workaround is to issue a checkpoint before running validation.

CR:545949

CR Number:   545949 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1459 07 Oct 2008 Fixed Description Visual Studio 2008 SP1, which contained the support for the Entity Framework, was released after the initial release of SQL Anywhere 11.0.0. Full support for the Entity Framework has now been added to SQL Anywhere.

CR:545950

CR Number:   545950 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 1514 07 Oct 2008 Fixed 11.0.1 1976 28 Nov 2008 Fixed Description The STOPLIST setting specifies the terms to ignore when building a text index. The sample stoplists for English contained words with apostrophes as well as words. An apostrophe is treated as a whitespace for the purposes of stoplist construction, causing such words to be treated as phrases (e.g. you'll is treated as "you ll"). Such words have now been removed from the sample.

CR:545987

CR Number:   545987 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2117 07 Oct 2008 Fixed 11.0.0 1538 21 Nov 2008 Fixed Description In the Text Configuration Object wizard, the defaults for the term breaker and maximum term length were "Generic" and "1" respectively. These were not particularly useful defaults. They have been changed so that the wizard now provides a reasonable default for the term breaker based on the database's CHAR collation, and the maximum term length based on both the database's CHAR collation and the currently selected term breaker. The term breaker now defaults to N-gram if the database's CHAR collation is a Chinese (936ZHO, 950ZHO_HK, 950ZHO_TW, EUC_CHINA, EUC_TAIWAN), Japanese (932JPN, EUC_JAPAN) or Korean (949KOR, EUC_KOREA) collation; otherwise, it defaults to Generic. The maximum term length now defaults to 20 if the Generic term breaker is selected; otherwise, for N-gram it defaults to 2 if the database's CHAR collation is a Chinese, Japanese or Korean collation, and 4 otherwise.

CR:546038

CR Number:   546038 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1514 07 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description Sybase Central could occasionally report an internal error when a table header on the "Data" tab was clicked in order to sort the data. This has been fixed.

CR:546046

CR Number:   546046 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1514 08 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description The QAnywhere plugin could have reported an internal error (NoClassDefFoundError) when connecting to a server message store if the plugin was registered with Sybase Central directly (i.e. using the QAPLUGIN.JAR file) rather rather than by using an installer-created .JPR file. This has been fixed. The workaround is to add "mldesign.jar" to the list on the "Advanced" page of the QAnywhere 11 plugin properties window.

CR:546070

CR Number:   546070 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1514 08 Oct 2008 Fixed 10.0.1 3778 08 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description The operation executed after an embedded SQL application executed a FETCH, could have caused a crash if the cursor was opened without WITH HOLD and a COMMIT or ROLLBACK was done by a procedure or function called by the FETCH. This has been fixed.

CR:546072

CR Number:   546072 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 1514 08 Oct 2008 Fixed 10.0.1 3778 08 Oct 2008 Fixed 9.0.2 3735 08 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description The iAS ODBC driver for Oracle could have crashed when the application tried to create multiple connections concurrently. This problem was more likely to have occurred on Unix systems. This problem has now been fixed.

CR:546074

CR Number:   546074 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 1514 08 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description A database that was initialized with a version 10 server could have become corrupted when run with a version 11 server. The problem could have resulted in the database not starting, failing assertions, or other errors. This has now been fixed. Note that rebuilding a database to a version 11 format will provide performance improvements, while also preventing this problem.

CR:546104

CR Number:   546104 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1516 15 Oct 2008 Fixed 11.0.1 1981 28 Nov 2008 Fixed Description Temporary tables with LONGVARCHAR or LONBINARY columns were not being completely freed. This has been fixed. Note, temporary tables occur when there are no indexes discovered to implement operations such as ORDER BY.

CR:546131

CR Number:   546131 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3738 15 Oct 2008 Fixed Description The following bug fixes, which were originally made only for ASA consolidated databases, have now been implemented for ASE consolidated databases as well: 1 - primary key conflicts for table ml_qa_global_props in upload_insert script (Engineering case 463062), 2 - table ml_qa_status_history unlimited growth problem (Engineering case 495514), 3 - UDP notifications to inactive devices problem (Engineering case 544613).

CR:546164

CR Number:   546164 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1515 08 Oct 2008 Fixed 10.0.1 3779 08 Oct 2008 Fixed 11.0.1 1978 28 Nov 2008 Fixed Description During the execution of server transmission rules, it was possible for the QAnywhere server to repeatedly report a java.util.NoSuchElement exception, and abort the rule execution. This has been fixed.

CR:546171

CR Number:   546171 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1515 08 Oct 2008 Fixed 10.0.1 3779 08 Oct 2008 Fixed 11.0.1 1978 28 Nov 2008 Fixed Description When a delivery condition that referenced message properties was specified for a QAnywhere connector, message transmission to the connecting messaging system would have been disabled. This has been fixed.

CR:546172

CR Number:   546172 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 3779 08 Oct 2008 Fixed Description If a parallel execution plan was executed using an exists join (JE / Exists Join), then it was possible for the statement to return the wrong answer. This has been fixed.

CR:546173

CR Number:   546173 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 1515 08 Oct 2008 Fixed 10.0.1 3779 08 Oct 2008 Fixed 11.0.1 1977 28 Nov 2008 Fixed Description When uploading timestamp data with the .NET Direct Row API, an exception could have been thrown. Even if an exception wasn't thrown, the fractional part of the timestamp would have been incorrect. When downloading timestamps with the .NET Direct Row api, values would have been incorrect by a few seconds. Both of these problems have now been fixed.

CR:546176

CR Number:   546176 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1515 08 Oct 2008 Fixed 11.0.1 1978 28 Nov 2008 Fixed Description When running a farm of MobiLink servers with QAnywhere messaging enabled, the delete rules and archiving process could have logged "deadlock detected" errors in the MobiLink server log. The rules were functioning correctly, but unnecessary database contention was occurring. This has been fixed by having the delete rules and archiving process run only in the primary server.

CR:546256

CR Number:   546256 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) 11.0.0 1515 09 Oct 2008 Fixed 10.0.1 3779 09 Oct 2008 Fixed 11.0.1 1979 28 Nov 2008 Fixed Description When connected to a DB2 Mainframe (D2M) consolidated database, the MobiLink server could have held locks across COMMITs, causing increased contention and sometimes resulting in deadlock or timeout errors. This has been fixed.

CR:546290

CR Number:   546290 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1515 09 Oct 2008 Fixed 10.0.1 3779 09 Oct 2008 Fixed 11.0.1 1979 28 Nov 2008 Fixed Description When connected to a DB2 Mainframe (D2M) database, the iAnywhere JDBC driver could have eld locks across COMMITs, causing increased contention and sometimes resulting in deadlock or timeout errors. This has been fixed.

CR:546294

CR Number:   546294 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.1 1980 03 Feb 2009 Fixed 11.0.0 1515 03 Feb 2009 Fixed Description The server could have failed assertion 104301 - "Attempt to free a user descriptor with non-zero reference count", while trying to drop a user. This assertion was likely to occur when an attempt was made to ALTER the same user in the same server session, and the ALTER had failed due to an error. This has been corrected.

CR:546330

CR Number:   546330 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1515 14 Oct 2008 Fixed 11.0.1 1980 28 Nov 2008 Fixed Description In the UltraLite plug-in, it is possible to view the data of a table by choosing the table in the left pane, and clicking on the Data tab in the right pane. When this was done though, subsequent attempts to change the schema of the database could have failed with the error A schema upgrade is not currently allowed. A result set created when viewing the data was not explicitly closed. This has been fixed.

CR:546367

CR Number:   546367 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) 11.0.0 14 Oct 2008 Fixed Description Sybase Central permitted utility operations while debugging or profiling. In some circumstances, running a utility operation while debugging or profiling could have caused Sybase Central to hang. This has been corrected so that utility operations are now permitted only when in Design mode.

CR:546432

CR Number:   546432 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 1518 17 Oct 2008 Fixed 10.0.1 3784 17 Oct 2008 Fixed 11.0.1 1987 28 Nov 2008 Fixed Description The server may have hung while performing updates to rows containing blobs. This has been fixed.

CR:546439

CR Number:   546439 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1516 15 Oct 2008 Fixed 11.0.1 1981 28 Nov 2008 Fixed Description The Interactive SQL utility would have reported an internal error if the OUTPUT statement operated on a result set that contained a UNIQUEIDENTIFIER column. This has been fixed.

CR:546478

CR Number:   546478 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1520 20 Oct 2008 Fixed 11.0.1 1991 28 Nov 2008 Fixed Description Referential integrity constraint checking could have failed, allowing a primary key to be removed when it still had referencing foreign keys, or preventing the removal of a primary key with no referencing foreign keys. The likelihood of this happening decreased as the number of foreign tables increased. This has now been fixed. Workaround Description  It is possible to delete the troublesome row in SUBMENUS by first deleting the child data in the MNACTION table for menuid = 91 and smnumber = 29. The following SQL statements will accomplish this: delete from mnaction where menuid = 91 and smnumber = 29; delete from submenus where menuid = 91 and smnumber = 29;

CR:546587

CR Number:   546587 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 1520 20 Oct 2008 Fixed 10.0.1 3786 22 Oct 2008 Fixed 11.0.1 1992 28 Nov 2008 Fixed Description If the option Chained was set to off (i.e. auto-commit enabled), executing an INSERT, UPDATE or DELETE statement inside a BEGIN ATOMIC block would have resulted in error -267 "COMMIT/ROLLBACK not allowed within atomic operation". This has been fixed. The DML statement will now be allowed to execute and a commit (or rollback if an error occurs)will be performed automatically at the end of the atomic block.

CR:546736

CR Number:   546736 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) 20 Oct 2008 Fixed Description In CONTAINS queries, the AND NOT (or -) operator applied to all expressions following (to the right of) the operator. This has been fixed so that AND NOT (and its variants listed below) now applies only to its immediate left and right arguments. For example, CONTAINS query 'a AND NOT b OR c' would be evaluated as 'a AND NOT (b OR c)'. After the fix, the meaning of the query is '(a AND NOT b) OR c'. Equivalents to the AND NOT operator are: 'a & NOT b', 'a NOT b', 'a AND -b', 'a & -b', 'a -b'. Note that if hyphen is used, it has to be preceded by a space and immediately followed by it's argument. There are two other legitimate uses for hyphen in a text query: 'a-b' and 'a - b'. The first case is interpreted as the phrase '"a b"', whereas the second is interpreted as 'a b' (='a AND b'). Additionally, interpretation of CONTAINS queries was dependent on exact order of operators and their arguments. For example, query 'a AND b OR c' would be evaluated as 'a AND (b OR c)' and query 'c OR b AND a' would be evaluated as 'c OR (b AND a)'. This has also been fixed by imposing an order of evaluation on all the text query operators as follows: 1) FUZZY, NEAR 2) AND NOT 3) AND 4) OR With the new rules, two examples above are equivalent '(a AND b) OR c' = 'c OR (b AND a)' Full syntax for the CONTAINS queries is described in the documentation: SQL Anywhere Server - SQL Reference Using SQL SQL language elements Search conditions CONTAINS search condition

CR:546742

CR Number:   546742 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1410 16 Oct 2008 Fixed 10.0.1 3708 16 Oct 2008 Fixed 11.0.1 1855 28 Nov 2008 Fixed Description The MobiLink client (dbmlsync) could have crashed when reporting certain TLS or HTTPS errors. Certain TLS errors could have caused a null pointer dereference during creation of the error message string. This has now been corrected.

CR:546854

CR Number:   546854 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 1515 15 Oct 2008 Fixed 10.0.1 3774 15 Oct 2008 Fixed 9.0.2 3733 15 Oct 2008 Fixed 11.0.1 1982 28 Nov 2008 Fixed Description If a query contained DISTINCT, ORDER BY and GROUP BY clauses and an expression in the ORDER BY clause appeared in the the GROUP BY clause, but not in the SELECT list, then the wrong error was returned, namely "Function or column reference to ... must also appear in a GROUP BY." This has been fixed so that the correct error message: "Function or column reference to .. in the ORDER BY clause is invalid." For example, the query: SELECT DISTINCT X FROM T GROUP BY E ORDER BY E Would have returned the error: "Could not execute statement. Function or column reference to 'E' must also appear in a GROUP BY." SQLCODE=-149, ODBC 3 State="42000"

CR:546867

CR Number:   546867 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 3780 15 Oct 2008 Fixed Description A partial index scan using an index with DESC columns, may have been inefficient. For this problem to have occurred, the last column used to define the range must have been in descending (DESC) order, and the index must have contained NULLs. This has been fixed. For example: Previously, the server would have read approximately 85 index leaf and table pages for the query below, now the number of pages read is approximately 10. CREATE TABLE CURRENCY_TABLE (CURRENCY CHAR(10) NOT NULL, DOLLAR_EQUIV NUMERIC(5, 2), PRIMARY KEY (CURRENCY)); INSERT INTO "CURRENCY_TABLE" VALUES ('DOLLAR', 1.00); INSERT INTO "CURRENCY_TABLE" VALUES ('POUND', 1.91); INSERT INTO "CURRENCY_TABLE" VALUES ('DM', .45); INSERT INTO "CURRENCY_TABLE" select 'DM', NULL from sa_rowgenerator(1,20000); commit; create index currency_idx_1 on currency_table( dollar_equiv desc ); call sa_flush_cache(); select count(*) from CURRENCY_TABLE with (index (currency_idx_1 )) where DOLLAR_EQUIV < 1000 option( force optimization);

CR:546869

CR Number:   546869 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 1518 16 Oct 2008 Fixed 10.0.1 3782 16 Oct 2008 Fixed 11.0.1 1986 28 Nov 2008 Fixed Description The property sheet for connectors contained a "Transmission Rules" page. This was incorrect because connectors do not have transmission rules; they have delivery conditions. As a result, that page has been replaced with a new "Delivery Conditions" page in which the single delivery condition for the connector can be typed.

CR:546882

CR Number:   546882 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 1524 28 Oct 2008 Fixed 10.0.1 3789 28 Oct 2008 Fixed 11.0.1 1998 28 Nov 2008 Fixed Description The GrowLog system event that fires when the database transaction log grows can be setup to truncate the transaction log upon its exceeding a certain size. In cases where the database server was very busy, the transaction log would not have been truncated often enough. This may have lead to the transaction log getting significantly larger than the threshold set in the event. This has been fixed, although in a very busy server it is still possible for the log to grow larger than the threshold for short periods of time. Workaround Description  None

CR:546908

CR Number:   546908 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 1515 16 Oct 2008 Fixed 10.0.1 3779 16 Oct 2008 Fixed Description When running the Unload utility (dbunload) to unload a pre-10.0 version database, the directory for the unloaded table data would not have been created. This has now been fixed.

CR:546912

CR Number:   546912 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 16 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description The wrong item could have been edited or deleted if the list that contained the item was sorted. This would have occurred in the following places: 1. List of members for a given destination alias 2. "Properties" tab of client store property sheets 3. The "Client Properties" tab of the property sheet for a server message store 4. The "Members" tab in the property sheet for a destination alias 5. The property sheet for a client in a server message store 6. The "Transmission Rules" or "Deletion Rules" tabs in any property sheet. 7. The "Properties" tab of a connector's property sheet. This has now been fixed.

CR:547033

CR Number:   547033 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 16 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description Opening the property sheet for a table that had an embedded quote in its name or in its owner's name, would have caused Sybase Central to generate an invalid SQL statement causing an error. This has been fixed.

CR:547035

CR Number:   547035 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 16 Oct 2008 Fixed 11.0.1 1986 01 Dec 2008 Fixed Description Attempting to use an UltraLite remote server with the Migrate Database wizard would have caused Sybase Central to crash. This has been fixed.

CR:547036

CR Number:   547036 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 1518 17 Oct 2008 Fixed 10.0.1 3783 17 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description The PacketsSent and PacketsReceived properties were being updated by HTTP and HTTPS connections, even though the HTTP protocol has no real concept of packets. This has been fixed by no longer updating these properties for HTTP and HTTPS connections. The BytesSent and BytesReceived properties will continue to be updated for HTTP and HTTPS connections.

CR:547037

CR Number:   547037 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 1518 17 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description When using the QAnywhere plugin, it was not possible to create an empty destination alias. This has been fixed so that creating an empty alias is now possible.

CR:547041

CR Number:   547041 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 17 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description Some remotes could have synchronized with servers that were not licensed to synchronize with those remotes. This has been corrected.

CR:547045

CR Number:   547045 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Nov 2008 Fixed Description Support has been added to allow exporting a script version's connection and table scripts, as well as its defined column names, to a SQL file by selecting the version object in Sybase Central while in Admin mode, and then choosing File -> Export.... The Version Export wizard prompts for a file name, and when Finish is clicked, a SQL file is created that contains a sequence of required calls to the ml_add_...() procedures.

CR:547049

CR Number:   547049 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 1518 17 Oct 2008 Fixed 10.0.1 3784 17 Oct 2008 Fixed 9.0.2 3740 17 Oct 2008 Fixed 11.0.1 1985 01 Dec 2008 Fixed Description After calling SQLGetTypeInfo, the application would not have been able to get the column names through problem could have prvented exporting MobiLink Monitor data to an Oracle database. This has now been fixed.

CR:547073

CR Number:   547073 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 20 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description Performance of database operations when there was a large transaction log (many transactions awaiting synchronization and/or checkpointing) has been improved. Note, GA versions of the software will not be able to read a database that has been used by UltraLiteJ as of this change. Earlier databases will automatically be upgraded.

CR:547076

CR Number:   547076 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 1519 20 Oct 2008 Fixed 10.0.1 3785 20 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description Executing a "MESSAGE ... TO CLIENT FOR CONNECTION n" statement could have resulted in a message with mangled characters in the message text. For this to have occurred, the source connection and destination connection must have been connected to databases with different collation sequences. This has been fixed.

CR:547078

CR Number:   547078 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1519 20 Oct 2008 Fixed 11.0.1 1988 01 Dec 2008 Fixed Description An ODBC or OLEDB application may have been positioned to an incorrect row when fetching by bookmark value. This would only have happened if the last column of the result set was not bound (for example with SQLBindCol). This has now been fixed.

CR:547084

CR Number:   547084 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 20 Oct 2008 Fixed 10.0.1 3783 20 Oct 2008 Fixed 11.0.1 1987 01 Dec 2008 Fixed Description A connection attempt that resulted in a warning was treated as an error and no connection was created. This was affecting the PHP, Python, and Ruby drivers. This has been fixed. Warnings no longer prevent a successful connection. The actual warning message can still be retrieved as usual.

CR:547198

CR Number:   547198 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3785 20 Oct 2008 Fixed Description Changes for Engineering case 536370 introduced a problem where simple select statements could have caused a server crash for specific forms of table schema and index definition. This has been fixed.

CR:547205

CR Number:   547205 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 1520 21 Oct 2008 Fixed 10.0.1 3786 21 Oct 2008 Fixed 11.0.1 1992 01 Dec 2008 Fixed Description Renaming a column in a table having referential action triggers, could have resulted in a server crash. This has been fixed.