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

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

CR:555390

CR Number:   555390 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.1 2136 08 Jan 2009 Fixed 11.0.0 1559 08 Jan 2009 Fixed 10.0.1 3831 08 Jan 2009 Fixed Description If the option PUBLIC.quoted_identifier was set to 'off', executing the reload script produced by Unload utility (dbunload) would have failed when attempting to set subsequent options. This has been fixed.

CR:555444

CR Number:   555444 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.1 2136 12 Jan 2009 Fixed 11.0.0 1559 12 Jan 2009 Fixed 10.0.1 3831 12 Jan 2009 Fixed Description When synchronizing using HTTPS through an HTTP proxy, MobiLink clients would have incorrectly appended the url_suffix to the HTTP CONNECT request, which could have caused some proxies and servers to fail. This has been fixed.

CR:555450

CR Number:   555450 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2136 12 Jan 2009 Fixed 11.0.0 1559 12 Jan 2009 Fixed 10.0.1 3831 12 Jan 2009 Fixed Description Column names that are greater than 29 bytes in length were being truncated. This has been fixed.

CR:555453

CR Number:   555453 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.1 2136 12 Jan 2009 Fixed 11.0.0 1559 12 Jan 2009 Fixed Description If an encryption key was specified, it was not possible to create a server message store when running on Linux systems. This has been fixed.

CR:555616

CR Number:   555616 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.1 2136 12 Jan 2009 Fixed 11.0.0 1560 12 Jan 2009 Fixed 10.0.1 3832 12 Jan 2009 Fixed Description he MobiLink server was allocating more memory than necessary and thus wasting memory. The amount wasted was approximately equal to 13% of the -cm option value. This has now been fixed.

CR:555617

CR Number:   555617 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2138 13 Jan 2009 Fixed 11.0.0 1561 13 Jan 2009 Fixed 10.0.1 3833 13 Jan 2009 Fixed 3780 13 Jan 2009 Fixed Description When calling SQLForeignKeys(), the result set was not returned in the correct sort order. According to the ODBC standard, the sort orders are: 1. If the foreign keys associated with a primary key are requested, the result set is ordered by FKTABLE_CAT, FKTABLE_SCHEM, FKTABLE_NAME, and KEY_SEQ. 2. If the primary keys associated with a foreign key are requested, the result set is ordered by PKTABLE_CAT, PKTABLE_SCHEM, PKTABLE_NAME, and KEY_SEQ. This has now been corrected.

CR:555621

CR Number:   555621 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 1552 12 Jan 2009 Fixed Description When displaying a graphical plan without statistics, estimates for internal nodes were not included. This has been fixed.

CR:555622

CR Number:   555622 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 2136 12 Jan 2009 Fixed 10.0.1 3831 12 Jan 2009 Fixed Description Lower bounds are imposed on selectivity and cardinality estimates during the optimization process. These bounds are meant to be greater than 0, but less than one row of the result set of a physical operator, and are set to be a very small percentage, which in the case of very big tables, or big intermediate result sets (> 10,000,000 rows), were actually bigger than one row. This has been fixed.

CR:555623

CR Number:   555623 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 2136 12 Jan 2009 Fixed 11.0.0 1560 12 Jan 2009 Fixed 10.0.1 3831 12 Jan 2009 Fixed Description The following fixes have been made to graphical plan descriptions: 1. Range expressions of a partial index scan are now always printed as "low expression <[=] column name <[=] high expression [ASC |DESC]". The low and high expressions can be NULL value if the real fence post was set to NULL value; they can be '*' if the real fence post is not set (this is actually an open range partial index scan). 2. Selectivity estimations are now printed with 9 decimal digits.

CR:555626

CR Number:   555626 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.1 2139 16 Jan 2009 Fixed 11.0.0 1562 16 Jan 2009 Fixed Description If the server used a cached plan for a query with an IN list predicate which contained a variable, and used the IN list predicate to return the rows in descending order using a table index, then the result set may have had fewer rows than it should have. For example, if table T1 had an index on column col, then the following query may have return too few rows: select * from T1 where col in ( 5, Var1 ) order by a desc; This has been fixed.

CR:555765

CR Number:   555765 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 2137 12 Jan 2009 Fixed 11.0.0 1561 12 Jan 2009 Fixed 10.0.1 3833 12 Jan 2009 Fixed Description There was a very small chance that the server would have returned a thread deadlock error on an external environment call in situations where no actual thread deadlock occurred. For this problem to have occurred, a previous valid thread deadlock must have been returned by the server, resulting from a large number of connections attempting to issue an external environment call at the same time. This problem has now been fixed.

CR:555769

CR Number:   555769 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 2137 12 Jan 2009 Fixed 11.0.0 1561 12 Jan 2009 Fixed 10.0.1 3833 12 Jan 2009 Fixed Description If an application, or set of applications, constantly connected, made a Java call, and then subsequently disconnected, then there was a chance the Java VM used by the server would have thrown an 'out of memory' exception. This problem has been fixed.

CR:555789

CR Number:   555789 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.1 2137 13 Jan 2009 Fixed 11.0.0 1561 13 Jan 2009 Fixed Description In very rare circumstances, the server could have reported assertion failures 101428 or 101424 "Writing page with no position in file." when running with AWE enabled and under periods of heavy activity or high server stress. This has been fixed.

CR:555808

CR Number:   555808 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.1 2138 13 Jan 2009 Fixed 11.0.0 1562 15 Jan 2009 Fixed 10.0.1 3833 15 Jan 2009 Fixed Description For a query containing a WITH RECURSIVE table, if the estimated cardinality of the recursive table after the first iteration was lower than 2 rows, the optimizer would not have set the alternative JNL operator if an alternative index existed. The resulting execution plans may have been very inefficient, depending of the number of rows on the right hand side of the JoinHashRecursive operator. This has been fixed. Example: with recursive Ancestor( child) as (select row_num from rowgenerator R1 where R1.row_num = 1 ) UNION ALL (select R2.row_num+100 from Ancestor, rowgenerator R2 where Ancestor.child = R2.row_num ) ) select * from Ancestor Ancestor(child) has exactly one row after the first query block is computed. Computing the second query block is very efficient if the executed plan is "Ancestor<seq> JNL R2<row_num>". However, because the optimizer did not set up the JNL operator, the inefficient plan "Ancestor<seq> JH* R2<seq>" was executed.

CR:555809

CR Number:   555809 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.1 2137 13 Jan 2009 Fixed 11.0.0 1561 13 Jan 2009 Fixed Description The Server Message Store would have been unable to connect to the store after creating it, if an encryption password was specified. This has been fixed.

CR:555827

CR Number:   555827 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.1 2138 13 Jan 2009 Fixed 11.0.0 1561 13 Jan 2009 Fixed Description When using the Create Table wizard to create a new table, or the Table Duplicate dialog to duplicate a table, the default_value for the dbspace option was ignored; that is, the dbspace selection in the wizard or dialog would have always defaulted to "system". This has been corrected so that it now defaults to the value of the default_dbspace option, if the option value corresponds to the name of a dbspace.

CR:555936

CR Number:   555936 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.1 2138 13 Jan 2009 Fixed 11.0.0 1561 13 Jan 2009 Fixed 10.0.1 3833 13 Jan 2009 Fixed Description An attempt to drop a database whose page size was larger than the server's page size, using the 'DROP DATABASE' statement, would have resulted in the error "An attempt to delete database 'database file' failed", leaving the reason for the failure unclear. The server will now raise the more specific error, "Page size too big: 'database file'".

CR:555940

CR Number:   555940 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 2145 02 Feb 2009 Fixed 10.0.1 3840 02 Feb 2009 Fixed Description Simple statements of the form "select TOP n from T order by T.X [asc|desc]" may have had a very inefficient query access plan. This has been fixed.

CR:555959

CR Number:   555959 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.1 2138 13 Jan 2009 Fixed 11.0.0 1562 13 Jan 2009 Fixed 10.0.1 3834 13 Jan 2009 Fixed 9.0.2 3780 13 Jan 2009 Fixed 9.0.1 2212 18 Mar 2009 Fixed Description If an application executed a remote query that involved a User Defined Function, and the call to the function passed in column references as parameters, there was a chance the server would have crashed when the server decided to run the query in partial passthru mode. This problem has now been fixed.

CR:555961

CR Number:   555961 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.1 2138 14 Jan 2009 Fixed Description The server's log window could have contained garbage characters if a language DLL was used that was older than the server. There was also a very small chance that the server could have crashed in this case. This has been fixed.

CR:555963

CR Number:   555963 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2138 13 Jan 2009 Fixed 11.0.0 1561 13 Jan 2009 Fixed 10.0.1 3833 13 Jan 2009 Fixed 9.0.2 3780 13 Jan 2009 Fixed Description If an NCHAR, NVARCHAR, or LONG NVARCHAR parameter was bound as SQL_C_DEFAULT, the binding would have defaulted to SQL_C_CHAR, instead of SQL_C_WCHAR. This has been corrected.

CR:555965

CR Number:   555965 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.1 2138 15 Jan 2009 Fixed Description In rare and timing dependent circumstances, a request could have hung on a heavily loaded server. This has only been observed when the request was a cached statement with host variables containing data larger than the communication buffer size, after a schema change, set option or drop variable. This has been fixed. Note, setting the max_client_statements_cached database option to 0 may workaround this issue.

CR:555973

CR Number:   555973 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 Jan 2009 Diagnostic Provided Description Tested and reproduced with: Product: SQL Anywhere 11.0.0.1526 with UltraliteJ feature OS: Windows XP SP2 BlackBerry Java Development Environment: JDE 4.1.0.185 and MDS 4.1.0.22 20050927 Remote Database for ASA Proxy tables: Oracle 10g After synchronizing UltraliteJ app tables with Consolidate ASA database, BlackBerry application exits with java.lang.OutOfMemoryError. When confirming BlackBerry memory, there's actually 17M free.

CR:555976

CR Number:   555976 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2139 15 Jan 2009 Fixed 11.0.0 1562 15 Jan 2009 Fixed 10.0.1 3834 15 Jan 2009 Fixed Description With the release of SA 10.0.0, identifiers were restricted such that they could no longer include double quotes or backslashes. Unfortunately, if an application wants to create an externlogin to a remote SQL server using secure logins, then the remote login needs to be specified in the form user\domain. As a result, the remote login specification of a create externlogin statement has now been extended to accept both identifiers and strings. Note that no catalog changes have been made; hence, the remote login specification is still restricted to 128 bytes.

CR:555978

CR Number:   555978 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.1 2138 14 Jan 2009 Fixed 11.0.0 1561 14 Jan 2009 Fixed Description Executing a "CREATE PROCEDURE ... LANGUAGE ..." or a "START EXTERNAL ENVIRONMENT ..." statement when connected to a case sensitive database, would have failed with an "external environment not found" error, if the external environment name was not specified in lower-case. This problem has now been fixed.

CR:555985

CR Number:   555985 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2041 14 Jan 2009 Fixed 11.0.0 1561 14 Jan 2009 Fixed 10.0.1 3833 14 Jan 2009 Fixed Description The MobiLink server would given an error message that the classpath was too long if the Java classpath given in the -sl java option was longer than about 3000 characters. This restriction has been removed.

CR:555989

CR Number:   555989 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2041 15 Jan 2009 Fixed 11.0.0 1561 15 Jan 2009 Fixed Description It was possible that the last download timestamp for one or more publications would not have been updated after receiving and applying the download from the server. This has been fixed.

CR:556111

CR Number:   556111 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 2186 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed 10.0.1 3868 24 Mar 2009 Fixed Description In specific situations, it was possible for the server to crash when processing a statement that contained a LIST aggregate function with an ORDER BY specification inside of a subquery. This has been fixed.

CR:556121

CR Number:   556121 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.1 2138 15 Jan 2009 Fixed 11.0.0 1562 15 Jan 2009 Fixed 10.0.1 3834 15 Jan 2009 Fixed Description Changes made as part of the fix for Engineering case 554242, introduced a problem where running the Validation utility (dbvalid) with a user who did not have DBA authority, or execute permission on the dbo.sa_materialized_view_info procedure, would have failed with the error message: Permission denied: you do not have permission to execute the procedure "sa_materialized_view_info" This has been fixed.

CR:556123

CR Number:   556123 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.1 2148 03 Feb 2009 Fixed 11.0.0 1571 03 Feb 2009 Fixed 10.0.1 3843 03 Feb 2009 Fixed Description Under certain circumstances, use of the system procedure sa_row_generator() could have caused the server to crash, or enter an infinite loop. This problem has been fixed. Note that the result set of the stored procedure will be empty when the specified values are not appropriate.

CR:556127

CR Number:   556127 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.1 2046 15 Jan 2009 Fixed 11.0.0 1562 15 Jan 2009 Fixed Description If the server could not find a transaction log file when attempting to start a database that needed recovery, it would have returned the misleading error "Specified database not found" (SQLCODE -83). This has been fixed. The error now returned in this situation is "Cannot open transaction log file -- <filename>" (SQLCODE -106).

CR:556132

CR Number:   556132 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 24 Feb 2009 Fixed Description The name of a .SQL file to run can be specified on the command line without an explicit READ keyword. If the .SQL file requires parameters, it is now possible to give the parameters following the file name without the READ keyword. For example, DBISQL x.sql [parm1] is equivalent to DBISQL READ x.sql [parm1]

CR:556146

CR Number:   556146 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2144 27 Jan 2009 Fixed Description The optimizer may have generated a query access plan that used intra-query parallelism that could not be executed in parallel, by underestimating the execution cost. This has been corrected by adjusting the costing of such enumerated plans during the optimization process so that it is closer to what the server does during query execution. This was done by using a new property of the partial access plans - "partitioned during execution". Hence, less than optimal parallel plans are more likely to be estimated as such by the optimizer.

CR:556154

CR Number:   556154 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 2138 16 Jan 2009 Fixed Description A server participating in mirroring system may have crashed if a mirroring connection timed out due to liveness, or, on very rare occasions, if a connection attempt to the partner or arbiter failed. This has been fixed.

CR:556162

CR Number:   556162 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.1 2139 16 Jan 2009 Fixed 11.0.0 1562 16 Jan 2009 Fixed Description If concurrent connections made DDL changes to the same global temporary table, then it was possible for the server to fail to reapply the resulting transaction log using the "-a" server command line option. Normal recovery should have been performed properly. This has been fixed so that the server will now be able to apply the transaction logs without error. Existing transaction logs will work correctly as expected.

CR:556163

CR Number:   556163 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.1 2138 15 Jan 2009 Fixed Description If the sa_validate() procedure was called without arguments, materialized views were not being validated. This has been fixed. Note, for changes to the sa_validate() procedure to take effect, the database will need to be rebuilt with a server containing this fix.

CR:556175

CR Number:   556175 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.1 2151 13 Feb 2009 Fixed 11.0.0 1574 13 Feb 2009 Fixed 10.0.1 3846 13 Feb 2009 Fixed Description Queries with unflattenable subqueries may have returned incorrect results, or crashed the server. The following conditions must have been true for the incorrect result set to have been, or for the server to have crashed: - the query contained a subquery predicate (e.g., EXISTS() , NOT EXISTS()) which could not be flattened in the main query block, which was used in the cost-based optimization by the SA Optimizer - the subquery predicate was correlated to at least two tables from the main query block - a correlation expression was equated to a constant in the main query block For example: select * from f, i, fi where f.fund_id = 1 <==== f.fund_id is a correlation expression for the NOT EXISTS() predicate and it is equated to a constant and f.fund_id = fi.fund_id and fi.investor_id=i.investor_id and i.investor_id not in ( select ib.investor_id <=== i.investor_id is a correlation expression for the NOT EXISTS() predicate from ba , ib where f.fund_id = ba.fund_id <==== f.fund_id is a correlation expression for the NOT EXISTS() predicate and ib.bank_account_id=ba.account_id )

CR:556292

CR Number:   556292 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2041 16 Jan 2009 Fixed 11.0.0 1562 16 Jan 2009 Fixed Description Output host variables for SQL statements would not have been updated when using the UltraLite engine if a warning had been triggered. This has been fixed.

CR:556296

CR Number:   556296 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Jan 2009 Fixed Description In rare cases, creating a procedure could have caused a server crash. This has been fixed.

CR:556326

CR Number:   556326 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.1 2139 16 Jan 2009 Fixed 11.0.0 1562 16 Jan 2009 Fixed 10.0.1 3834 16 Jan 2009 Fixed 9.0.2 3781 16 Jan 2009 Fixed Description Applications running on Unix systems, and using the iAS ODBC driver for Oracle, could have received an "Out of memory" error when calling SQLTables, SQLColumns, SQLPrimaryKeys, SQLForeignKeys, SQLProcedureColumns, SQLProcedures, or SQLStatistics. This problem has now been fixed.

CR:556340

CR Number:   556340 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) 11.0.1 2139 19 Jan 2009 Fixed 11.0.0 1563 19 Jan 2009 Fixed 10.0.1 3835 19 Jan 2009 Fixed Description Applications fetching data from an NCHAR column that was greater than 32767 bytes, using the Perl, Python, PHP, or Ruby drivers, may have crashed. This has been fixed.

CR:556447

CR Number:   556447 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 2142 26 Jan 2009 Fixed 11.0.0 1566 26 Jan 2009 Fixed 10.0.1 3837 26 Jan 2009 Fixed Description When editing a DATE value in the "Results" pane of the Interactive SQL utility (dbisql), or on the "Data" tab in the SQL Anywhere plug-in for Sybase Central, if the date was typed in, rather than using the date chooser dialog, the value entered was ignored when the value was updated. This has been corrected so that the value entered is now sent to the database.

CR:556453

CR Number:   556453 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 2144 27 Jan 2009 Fixed 11.0.0 1567 27 Jan 2009 Fixed Description Newly added or modified DATE values on the "Data" tab for a table, could have been displayed using the canonical YYYY-MM-DD format rather than that specified in the "Date_format" database option. This has been fixed.

CR:556516

CR Number:   556516 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.1 2139 16 Jan 2009 Fixed 11.0.0 1563 16 Jan 2009 Fixed Description If an application was using one of the JDBC based Remote Data Access classes (i.e. either SAJDBC or ASEJDBC), and the remote login failed, then there was a possibility that the error reported would not contain the actual reason for the failed login. When jConnect throws a JZ00L SQLException, the actual reason for the failed login is usually contained in a chained SQLException, rather than the main SQLException. The server will now report the error on the chained exception instead of reporting the topmost SQLException.

CR:556527

CR Number:   556527 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) 11.0.1 2139 16 Jan 2009 Fixed 11.0.0 1563 16 Jan 2009 Fixed 10.0.1 3835 16 Jan 2009 Fixed Description A new network protocol option 'http_buffer_responses' has been added. When set to 'On', HTTP packets from MobiLink will be completely streamed into an intermediary buffer before being processed, instead of processing the bytes as they are read off the wire. Syntax: http_buffer_responses = { off | on } Protocols: HTTP, HTTPS Default: off Because of the extra memory overhead required, this feature should only be used to work-around HTTP sync stability issues. In particular, the ActiveSync proxy server for Windows Mobile devices will throw away any data that is not read within 15 seconds after the server has closed its side of the connection. Because MobiLink clients process the download as they receive it from MobiLink, there is a chance they will fail to finish reading an HTTP packet within the allotted 15 seconds causing synchronization to fail with stream error code STREAM_ERROR_READ, when synchronizing using non-persistent HTTP. By specifiying 'http_buffer_responses=On', the client will read each HTTP packet in its entirety into a buffer before processing any of it, thereby beating the 15 second timeout.

CR:556539

CR Number:   556539 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.1 2140 20 Jan 2009 Fixed 11.0.0 1567 20 Jan 2009 Fixed 10.0.1 3835 20 Jan 2009 Fixed Description UltraLite and UltraLiteJ were not able to recognize a correlation name following the table name in UPDATE and DELETE statements. Without this ability, WHERE clauses that require the correlation name to disambiguate column references could not be written. For example: update Employee E set salary = salary * 1.05 where EXISTS( SELECT 1 FROM Sales S HAVING E.Sales > Avg( S.sales) GROUP by S.dept_no ) The syntax for UPDATE and DELETE statements was been expanded to correct this.

CR:556552

CR Number:   556552 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 2139 19 Jan 2009 Fixed 11.0.0 1563 19 Jan 2009 Fixed 10.0.1 3835 19 Jan 2009 Fixed Description In certain cases, rebuilding a pre-10.0 database to version 10.0 or later may have failed due to an incorrectly charset-converted database file-name. The SQL error that was reported was: "Cannot access file '<incorrectly-converted-file-name>.db' -- The filename, directory name, or volume label syntax is incorrect." This issue only occurred when using an OS charset whose label was not used prior to version 10.0.0, such as "GBK". Additionally, for this issue to have occurred, the database must have used a different charset than the OS charset - specifically, the filename must contain characters that require translation to be valid in the database charset. This has been fixed.

CR:556724

CR Number:   556724 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 2140 19 Jan 2009 Fixed 11.0.0 1564 19 Jan 2009 Fixed Description Using the "Request Logging" page of a server's property sheet to attempt to enable request level logging for all connections to a database, or for a single connection, would have caused Sybase Central to crash. This has been fixed.

CR:556754

CR Number:   556754 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.1 2141 20 Jan 2009 Fixed 11.0.0 1564 20 Jan 2009 Fixed Description When deleting a row containing a CHAR or BINARY (i.e. string) column, there were some circumstances where the space on the table page for the string might not have been reclaimed. This problem only occurred with string data shorter than approximately one page in size, and the string must have been held active, either in a cursor or in a variable, then inserted into a new row, and then deleted while still held active. The database cleaner must also run after commiting the delete, but before closing the cursor or value holding the string. This has been fixed.

CR:556757

CR Number:   556757 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.1 2149 19 Jan 2009 Fixed 11.0.0 1564 19 Jan 2009 Fixed 10.0.1 3835 19 Jan 2009 Fixed 9.0.2 3782 19 Jan 2009 Fixed Description If a JDBC application called ResultSetMetaData.getColumnTypeName() with an invalid column index, then the application may have crashed. This problem has been fixed.

CR:556771

CR Number:   556771 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2142 26 Jan 2009 Fixed 11.0.0 1566 26 Jan 2009 Fixed Description On Windows platforms other than Windows Vista, performance counters for the server were not visible in the performance monitor when the server was started as a service. The code to check if the process was still alive was using the wrong permissions to open the process. This has been corrected.

CR:556778

CR Number:   556778 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) 12.0.1 3272 07 Jan 2011 Fixed 12.0.0 2630 07 Jan 2011 Fixed 11.0.1 2543 07 Jan 2011 Fixed 10.0.1 4167 07 Jan 2011 Fixed Description The return values of the built-in functions user_id() and suser_id() may have incorrectly been described as not nullable even if the function argument was not nullable. This may have lead to the assertion error 106901 "Expression value unexpectedly NULL in write". This has been fixed so that the functions' results are always described as nullable.

CR:556913

CR Number:   556913 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.1 2141 20 Jan 2009 Fixed 11.0.0 1564 20 Jan 2009 Fixed Description SQL Anywhere JSON services incorrectly encoded the apostophe (') within a string to a double backslash (\\), the backslash was not encoded. This has been fixed so that a backslash is now correctly encoded to a double backslash, and the apostrophe is not encoded.

CR:556925

CR Number:   556925 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2042 22 Jan 2009 Fixed 11.0.0 1565 22 Jan 2009 Fixed 10.0.1 3836 22 Jan 2009 Fixed Description The fix for Engineering case 553312, may have prevented restarting the MobiLink Monitor after disabling the Details Table, Utilization Graph, or Overview panes. This has been fixed. Pane sizes are now also properly restored when re-enabling after restarting.

CR:556960

CR Number:   556960 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2209 14 Apr 2009 Fixed Description The "Join Type" value on the "Join" page of the Query Editor could not be reset to its initial empty value. This has been corrected so that now it can.

CR:556974

CR Number:   556974 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2141 21 Jan 2009 Fixed 11.0.0 1564 21 Jan 2009 Fixed Description Using a QAnywhere JMS connector to communicate with a Websphere MQ JMS provider could have resulted in the following two issues: - The MobiLink server could have reported the error "The property name 'JMSTimestamp' is reserved and cannot be set." when Sending a message from a QAnywhere application to the JMS connector. - The ReplyToAddress of a QAnywhere message originating from a Websphere JMS provider could have contained a malformed queue name. Both of these issues have been corrected.

CR:556989

CR Number:   556989 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.1 2145 03 Feb 2009 Fixed 11.0.0 1569 03 Feb 2009 Fixed Description The server may have crashed, or returned incorrect data, on GET DATA requests if the cursor reused a query access plan for a simple SELECT statement. This has been fixed

CR:557107

CR Number:   557107 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.1 2044 21 Jan 2009 Fixed 11.0.0 1562 21 Jan 2009 Fixed Description When locking a table in exclusive mode (i.e. LOCK TABLE {tablename} IN EXCLUSIVE MODE), the server would first obtain a read lock on the table, increasing the likelihood of deadlocks occurring. This has now been fixed.

CR:557311

CR Number:   557311 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.1 2146 23 Jan 2009 Fixed 11.0.0 1566 23 Jan 2009 Fixed Description A connection established by an HTTP request to an HTTP listener port, would have leaked a small amount of memory when the connection was closed. This has been fixed. Connections to HTTPS listener ports were not affected by this problem.

CR:557328

CR Number:   557328 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.1 2141 23 Jan 2009 Fixed 11.0.0 1565 23 Jan 2009 Fixed 10.0.1 3837 23 Jan 2009 Fixed Description If an application logged on the database using a userid with multibyte characters, and the application subsequently made a Java in the database call, then there was a chance the Java VM would have failed to start if this was the first time a Java call was made since the database was started. This problem has now been fixed. The workaround is to log in using a userid without non-multibyte characters and execute a START JAVA statement. Once the Java VM is successfully started, making Java calls using userids with multibyte characters will work fine.

CR:557332

CR Number:   557332 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.1 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed 10.0.1 3841 02 Feb 2009 Fixed Description If a string column used a UCA collation with accent or case sensitivity, and the column appeared in an index with order DESC, then the server could have returned incorrect answers for LIKE predicates on the column. Problematic LIKE predicates started with a prefix of non-wildcard characters, such as the following: "T.x LIKE '01234%'". This has been fixed.

CR:557363

CR Number:   557363 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 2141 26 Jan 2009 Fixed 11.0.0 1565 26 Jan 2009 Fixed 10.0.1 3836 26 Jan 2009 Fixed Description By default (or with SET 'HTTP(CH=auto)') an SA HTTP client procedure would have sent its HTTP request using chunk mode transfer encoding when posting data that was greater than 2048 bytes. If the server rejected the request with a 501 "Not Implemented" or 505 "HTTP Version Not Supported" status, the procedure would have automatically re-issued the request without using chunk transfer encoding. When in default mode, an SA client would not have used chunk transfer encoding when posting data that was less than 2048 bytes in length. This has now been changed so that the data byte limit is now 8196 bytes, from 2048 bytes, and the status 411 "Length Required" has been added to its criteria for re-issuing the request without using chunk mode transfer encoding.

CR:557465

CR Number:   557465 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.1 2156 23 Jan 2009 Fixed 11.0.0 1578 23 Jan 2009 Fixed 10.0.1 3850 23 Jan 2009 Fixed 9.0.2 3795 23 Jan 2009 Fixed Description In exceptionally rare circumstances, the server may have crashed during the rewrite phase of optimization, when attempting to execute a very large and complex SELECT statement. This may have occurred when the server was close to running ouf of stack space, or was low on cache. The problem was seen with queries containing UNION, EXCEPT, INTERSECT, and deeply nested subselects. This has been fixed. The server will now correctly return the error "-890: Statement size or complexity exceeds server limits".

CR:557507

CR Number:   557507 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2142 26 Jan 2009 Fixed 10.0.1 3837 26 Jan 2009 Fixed Description If the statement: set option public.login_mode='Standard,Integrated' was executed, it would have been recorded in the transaction log as set option public.login_mode='Standard' This could have affected mirroring environments where the login_mode was set correctly on the primary server, but not on the mirror. This has been fixed.

CR:557518

CR Number:   557518 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.1 2039 23 Jan 2009 Fixed 11.0.0 1566 23 Jan 2009 Fixed Description An extremely busy server with multiple CPUs, maxed on processing queries, could have crashed in rare conditions. This has been fixed.

CR:557527

CR Number:   557527 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 2142 26 Jan 2009 Fixed 11.0.0 1566 26 Jan 2009 Fixed 10.0.1 3837 26 Jan 2009 Fixed Description A SQL Anywhere HTTP client function was only able to return a varchar data type. Support has now been added to the HTTP client so that it can also be defined to return binary, varbinary or long binary data types, i.e.: CREATE function client() RETURNS long binary URL 'http://localhost/image_service/...' TYPE 'HTTP:GET' Note, this change only extends the semantic meaning of the returned value, declaring the return data type as binary does not change the behaviour at the transport level. Textual data may still be converted to the database character set based on Content-Type HTTP header or SOAP envelope encoding criteria.

CR:557677

CR Number:   557677 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.1 2144 27 Jan 2009 Fixed 10.0.1 3909 16 Jun 2009 Fixed Description The server automatically collects and updates column statistics during the execution of DML statements. Earlier versions of the server did the auto collection only when a single DML statement affected more than a threshold number of rows, in order to reduce the overhead of collecting statistics on a relative basis. Support was added in release 10.0.1 to also do some automatic statistics collection on all DML statements, including those affecting as few as a single row. A subtle defect in this new support caused the server to miss some opportunities for automatic statistics collection for UPDATE statements, as opposed to the INSERT and DELETE statements. This has now been corrected.

CR:557679

CR Number:   557679 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3835 26 Jan 2009 Fixed 9.0.2 3782 26 Jan 2009 Fixed Description When running a 64-bit version of perfmon, the Adaptive Server Anywhere or SQL Anywhere counters would not have been displayed if the 64-bit version of the counters library (dbctrsX.dll) was registered and the 32-bit version was not. This has been corrected. Note, both versions of the counters library are registered during a normal product installation so it is unlikely that users would encounter this problem.

CR:557685

CR Number:   557685 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.1 2144 27 Jan 2009 Fixed 11.0.0 1567 27 Jan 2009 Fixed 10.0.1 3838 27 Jan 2009 Fixed Description UltraLite and UltraLiteJ erroneously accepted DEFAULT TIMESTAMP as a clause in the CREATE TABLE and ALTER TABLE statements, and treated the clause as if DEFAULT CURRENT TIMESTAMP had been entered. Attempts to execute CREATE TABLE or ALTER TABLE statements with this clause will now result in a syntax error.

CR:557686

CR Number:   557686 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.1 2143 27 Jan 2009 Fixed 11.0.0 1567 27 Jan 2009 Fixed Description The MobiLink server could not start in a server farm if the consolidated databases were running on DB2 or DB2 mainframe database servers, and the MobiLink server in the farm was requested to start with a liveness setting from the ml_property table (the ml_property table in the consolidated database contained a liveness value for the server farm). This problem has now been fixed.

CR:557767

CR Number:   557767 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.1 2145 02 Feb 2009 Fixed 11.0.0 1569 02 Feb 2009 Fixed 10.0.1 3840 02 Feb 2009 Fixed Description If an ALTER TABLE statement needed to rewrite the rows of the table (for example, if a 17th nullable column is added) and the table contained long or compressed strings, the operation could have taken much longer than necessary and the database may have end up with many more free pages than before the ALTER. The number of extra pages would have been approximately the number of pages in the table in question. This has been fixed.

CR:557794

CR Number:   557794 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.1 2144 27 Jan 2009 Fixed 11.0.0 1567 27 Jan 2009 Fixed Description Under certain circumstances, it is possible that database indexes could have become corrupt. This has been fixed.

CR:557802

CR Number:   557802 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.1 2144 27 Jan 2009 Fixed 11.0.0 1567 27 Jan 2009 Fixed 10.0.1 3838 27 Jan 2009 Fixed Description In rare circumstances, server CPU usage could have been unnecessarily high. The problem would only have occurred with certain layouts of memory within a heap, and when certain heap operations were being performed on the heap. This problem has been fixed.

CR:557808

CR Number:   557808 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.1 2044 29 Jan 2009 Fixed 11.0.0 1562 29 Jan 2009 Fixed Description The changes for Engineering case 552171 introduced a problem where occasionally the use of the db_backup() function on a running database server could have returned a corrupt transaction log page. This would have caused the MobiLink client (dbmlsync) to fail the synchronization, or the Backup utility (dbbackup) to fail to recover the newly backed-up file. In both cases, this was a transient failure, and the sync/backup could simply have been restarted when the error was detected. This has now been fixed.

CR:557812

CR Number:   557812 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.1 2187 10 Feb 2009 Fixed 11.0.0 1594 25 Mar 2009 Fixed 10.0.1 3868 25 Mar 2009 Fixed 9.0.2 3791 07 Apr 2009 Fixed Description If an UPDATE or DELETE statement used a keyset cursor and the statement executed at isolation level 0 or 1, it was possible for the statement to update or delete rows improperly. This could have occurred if another transaction deleted a row identified by the UPDATE or DELETE statement and committed, and then another transaction inserted a row and committed before the UPDATE or DELETE statement had finished processing. In this case, the newly inserted row would have been improperly processed by the UPDATE or DELETE statement. DELETE and UPDATE statements use a keyset cursor if there is a possibility that an updated row could be re-processed by the statement (for example if an UPDATE modifies a column in the index scan, or if a join is present). This has now been fixed. A workaround would be to use a higher isolation level (2 or 3).

CR:557818

CR Number:   557818 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2155 24 Feb 2009 Fixed 11.0.0 1611 30 Apr 2009 Fixed Description When running on Windows CE devices, an UltraLite database could have failed to start, reporting SQLE_DYNAMIC_MEMORY_EXHAUSTED, when the default cache size chosen for the database was too large. The default cache size that is now chosen takes the physical memory available in to consideration, and limits our size accordingly. The cache size allocated on Windows was also somewhat reduced. Specifying the cache_size connection parameter with an appropriate value will work around this problem.

CR:557829

CR Number:   557829 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.1 2252 10 Jun 2009 Fixed 11.0.0 1623 10 Jun 2009 Fixed 10.0.1 3900 10 Jun 2009 Fixed Description If the MobiLink Listener (dblsn) was started with the -q option ("run in minimized window"), and it was then restored by double clicking on the icon from the today screen, the "shutdown" button did not appear. This has been fixed.

CR:557837

CR Number:   557837 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) 11.0.1 2146 03 Feb 2009 Fixed 11.0.0 1570 03 Feb 2009 Fixed 10.0.1 3841 03 Feb 2009 Fixed 9.0.2 3789 03 Feb 2009 Fixed Description Incorrect results were possible when there was both an equality condition and another redundant conjunctive expression such as: x >= 2 AND x = 3 with only a column name on one side of the comparison. That column name must also have been the first column in an index. This has now been fixed.

CR:557849

CR Number:   557849 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.1 2143 27 Jan 2009 Fixed 11.0.0 1567 27 Jan 2009 Fixed Description The Interactive SQL utility (dbisql), or the SQL Anywhere plug-in for Sybase Central, could have crashed when opening the "Connect" dialog when run with JRE 1.6.0 update 11. This has been fixed. Note, SQL Anywhere 11.0.0 and 11.0.1 ship with JRE 1.6.0 update 4, which does not suffer from this problem.

CR:557870

CR Number:   557870 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.1 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed Description If a table containing columns declared as compressed strings was used in a parallel plan that contained a parallel hash join, it was possible, in rare circumstances, for the server to have crashed. This has been fixed.

CR:557924

CR Number:   557924 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3785 28 Jan 2009 Fixed Description If a connection string containing the "verify=no" TCP option was passed to the Interactive SQL utility (dbisql) and the -jconnect option was used, the dbisql would have crashed. This has now been fixed.

CR:557938

CR Number:   557938 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.1 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed Description It was possible for a deadlock to have occurred in the database server if the QAnywhere server was performing delete rules and archiving messages at the same time. Furthermore, the exception thrown by this deadlock exposed another problem in the QAnywhere server error handling where it was possible for a transaction to be left open, causing other connections to block due to unreleased table locks. Both of these issues have been fixed.

CR:557953

CR Number:   557953 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 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed 10.0.1 3839 29 Jan 2009 Fixed Description The Index Consultant may have caused the server to crash following query optimization. The class of queries for which this could happen was characterized by the existence of a comparison or EXISTS() subquery predicate in one of the query blocks. For example: select * from sales_order_items soi1, sales_order_items soi2 where soi1.id = soi2.id AND soi1.quantity < ( select avg( quantity ) from sales_order_items soi3 where soi3.prod_id = soi1.prod_id ); This has now been fixed.

CR:557955

CR Number:   557955 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed 10.0.1 3839 29 Jan 2009 Fixed 9.0.2 3786 29 Jan 2009 Fixed Description Calls the function SQLGetInfo() would have incorrectly returned SQL_CB_NULL for SQL_CONCAT_NULL_BEHAVIOR. As the result of the server concatenating a string and NULL is the string, calls to SQLGetInfo() have now been corrected to return SQL_CB_NON_NULL for SQL_CONCAT_NULL_BEHAVIOR.

CR:557960

CR Number:   557960 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2147 05 Feb 2009 Fixed 11.0.0 1571 05 Feb 2009 Fixed Description The UltraLite Unload utility (ulunload), when run with the -s option "Unload schema as SQL statements", would have generated invalid unique constraints when they contained more than one column. This has been fixed.

CR:557973

CR Number:   557973 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.1 2183 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed 10.0.1 3868 24 Mar 2009 Fixed Description If an index already existed on a particular set of columns, attempting to create a unique index over the same set of columns might have failed, if the index contained deleted, but not cleaned, entries. This has been fixed. Note, a work around would be to call sa_clean_database manually before creating the index.

CR:558001

CR Number:   558001 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.1 2147 03 Feb 2009 Fixed 11.0.0 1570 03 Feb 2009 Fixed Description Under certain circumstances, the server could have computed, and displayed, incorrect statistics, For example, the selectivity may have been reported as infinite. This were likely no side effects on query performance related to this defect, which has now been corrected.

CR:558084

CR Number:   558084 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2144 29 Jan 2009 Fixed Description A new tailoring of the Japanese UCA collation has been added which defines primary-level differences between all Hiragana letters, as well as primary-level differences between all Katakana letters. This new tailoring will permit correct equality comparisons of Hiragana and Katakana letters in case-insensitive collations. The new collation is used by specifying a collation of UCA(locale=ja;sorttype=direct;...).

CR:558085

CR Number:   558085 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.1 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed 10.0.1 3838 29 Jan 2009 Fixed Description The MobiLink server now supports two new command options, -vR show the remote ID in each logging message -vU show the ML user name in each logging message When both -vR and -vU are specified, the MobiLink server will add the remote ID and the MobiLink user to each message logged: yyyy-mm-dd hh:mm:ss. <sync_id> ({remote_id},{user_name}) When started with -vR and without -vU, the prefix will be just the remote_id: yyyy-mm-dd hh:mm:ss. <sync_id> (remote_id,) and the MobiLink user name will be empty. When started with -vU and without -vR, the prefix will be just the user name: yyyy-mm-dd hh:mm:ss. <sync_id> (,user_name) and the remote ID will be empty. The new feature may be useful for MobiLink users who are running the MobiLink server with the command options -on or -os, as the logging messages for a synchronization can span multiple MobiLink server logging files, which makes it is hard to find out the remote ID and MobiLink user name for a given sync ID from such logs. This extra logging information will only apply to the synchronization threads. For the main thread of the MobiLink server, the logging messages will still contain the following prefix, yyyy-mm-dd hh:mm:ss. <Main> because there is no remote ID or MobiLink user name for the main thread. These two command line options will not be affected by the -v+ option, that is, the MobiLink server will not add the remote ID or the ML user name into its logging messages, even if the -v+ option is used. Therefore, the description for the -v+ option has been changed to - "show all verbose logging specified with lower case letters".

CR:558108

CR Number:   558108 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2145 02 Feb 2009 Fixed 11.0.0 1568 02 Feb 2009 Fixed 10.0.1 3839 02 Feb 2009 Fixed 9.0.2 3786 02 Feb 2009 Fixed Description Calling the function SQLGetTypeInfo() would have returned an incorrect AUTO_UNIQUE_VALUE column value in the result set for non-numeric types. The value return would have been 0, but according to the ODBC specification a NULL should have been returned. ODBC specificatrion for AUTO_UNIQUE_VALUE : Whether the data type is autoincrementing: SQL_TRUE if the data type is autoincrementing. SQL_FALSE if the data type is not autoincrementing. NULL is returned if the attribute is not applicable to the data type or the data type is not numeric. The behaviour has been corrected to follow the ODBC specification.

CR:558232

CR Number:   558232 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.1 2145 02 Feb 2009 Fixed 11.0.0 1569 02 Feb 2009 Fixed 10.0.1 3840 02 Feb 2009 Fixed Description The MobiLink Monitor has a default filter which highlights failed synchronizations in red. Failed synchronizations logged by the MobiLink Server were not being shown in the Monitor in red as the server was telling the Monitor that every sync was successful. This has been fixed.

CR:558286

CR Number:   558286 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3914 22 Jul 2009 Fixed Description A query may have taken a very long time to execute if it contained an uncorrelated subquery in an ANY or ALL predicate that referenced a procedure that was not inlinable. The problem was due to the subquery plan that was generated not having a work table above the procedure call, so every repeated subquery execution caused the procedure to reexecute. This has been fixed.

CR:558446

CR Number:   558446 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.1 2147 05 Feb 2009 Fixed 11.0.0 1571 05 Feb 2009 Fixed 10.0.1 3843 05 Feb 2009 Fixed 9.0.2 3789 05 Feb 2009 Fixed Description Executing an insert statement of the form: 'INSERT INTO <remote table> ON EXISTING UPDATE SELECT * FROM <table>', would have caused the server to correctly return an error; but, if the application attempted to execute an insert statement of the form: 'INSERT INTO <table> ON EXISTING UPDATE SELECT * FROM <remote table>', the server would have crashed. The problem has now been fixed and the server now correctly returns an error in both cases.

CR:558481

CR Number:   558481 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 2146 02 Feb 2009 Fixed 11.0.0 1570 02 Feb 2009 Fixed Description The Interactive SQL utility (dbisql) could have crashed when executing a statement which returned a result set, if the redirection operator ( ">#" ) was used to save the result set to a file. This has been fixed. Note, this problem only affected graphical operation of the program.

CR:558510

CR Number:   558510 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.1 2188 03 Feb 2009 Fixed 11.0.0 1570 03 Feb 2009 Fixed Description A table in the QAnywhere for Ultralite schema could have been created improperly, resulting in a failure to initialize the message store with the error (-131) "param 1: timestamp". This has been fixed

CR:558554

CR Number:   558554 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2146 03 Feb 2009 Fixed Description If a user-defined domain was created with char-length semantics, the Unload utility (dbunload) would not have preserved this attribute. This has now been fixed.

CR:558580

CR Number:   558580 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.1 2149 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description Incorrect results could have been obtained with queries containing a temporary table on left side of a LEFT OUTER JOIN. This has been fixed.

CR:558713

CR Number:   558713 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3844 06 Feb 2009 Fixed Description If a simple SELECT statement was executed with the option Row_counts set to 'on', the returned row count value on open may have incorrectly been zero. This has been fixed

CR:558739

CR Number:   558739 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.1 2147 05 Feb 2009 Fixed 11.0.0 1570 05 Feb 2009 Fixed Description After deploying a synchronization model with logical deletes to a DB2 consolidated database, and then synchronizing, either of the following synchronization errors would have occurred for the MobiLink server (depending on the database setup): [IBM][CLI Driver][DB2/NT] SQL1216N Graphic data and graphic functions are not supported for this database. SQLSTATE=56031 [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "N''" was found following ", ?, ?, ?, ?, ''". Expected tokens may include: "<space>". SQLSTATE=42601 This has been fixed. A workaround is to deploy to a file and edit the consolidated SQL file to change instances of four single quotes to two single quotes.

CR:558753

CR Number:   558753 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.1 2147 04 Feb 2009 Fixed 11.0.0 1570 04 Feb 2009 Fixed Description Attempting to cancel an external environment request while the server was very heavily loaded may have caused the server to crash. Note that this problem would have been quite rare. The problem has now been fixed.