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

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

CR:552304

CR Number:   552304 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 2032 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed Description If the OS and database character sets were not the same, localized server window messages pertaining to checkpoints and events could have been mangled. This has been fixed.

CR:552311

CR Number:   552311 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 2129 17 Dec 2008 Fixed 11.0.0 1553 17 Dec 2008 Fixed 10.0.1 3818 17 Dec 2008 Fixed Description If a SELECT statement contained a procedure call with arguments that contained column references to other tables in the from clause, the server may have return a "Column not found" error for these column references. This would have occurred when the query rewrite process can remove tables from the query. For example: create table T1( a int primary key ) create table T2( a int primary key, c int ) create procedure P1 ( u int ) begin select a from T1 where a = u; end select dt.* from T1 left outer join T2 on T1.a = T2.a, lateral( P1(T2.c) ) dt For every row in T1 the left outer join can return at most one row because of the join on primary keys. So the query rewrite removed the left outer join and the table T2 from the query which caused a "Column T2.c not found" error for the procedure argument. This has been fixed.

CR:552312

CR Number:   552312 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 2033 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed 10.0.1 3814 08 Dec 2008 Fixed 9.0.2 3764 08 Dec 2008 Fixed Description The changes made for Engineering case 541615 introduced a problem where attempting to create a proxy table to a DB2 or Microsoft SQL Server table using Sybase Central could have failed with a strange conversion error, instead of creating the proxy table. This problem has now been corrected.

CR:552314

CR Number:   552314 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2124 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed 10.0.1 3814 08 Dec 2008 Fixed 9.0.2 3764 08 Dec 2008 Fixed Description If an application called the ResultSet.getBlob() method, and if fetching the blob should have thrown a valid SQLException, then quite often the exception would not have been thrown and an empty blob would have instead been returned to the client. This problem has now been fixed.

CR:552319

CR Number:   552319 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Dec 2008 Fixed Description If an operation (INSERT, UPDATE or DELETE) occurred on a remote database, and the operation belonged to one or more publications that were subscribed to by different users, then the operation would have been uploaded once for each user that had subscribed to a publication containing it. This has been fixed so that the operation will now only be uploaded once. For example, suppose two publication P1 and P2 are defined that both contain a table T1. Two ML users, U1 and U2 are defined on the remote. U1 is subscribed to P1, and U2 is subscribed to P2. A row is inserted into T1 in an operation I'll call O. The old behaviour would have been to upload O when the subscription between U1 and P1 was synchronized, then upload it again when the subscription between U2 and P2 was synchronized. The new behaviour is that O will be uploaded for the subscription that is synchronized first (U1-P1 or U2-P2), and not uploaded when the other subscription is synchronized.

CR:552321

CR Number:   552321 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2124 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed 10.0.1 3814 08 Dec 2008 Fixed Description If an error or warning occurred when commiting, the MobiLink server would not have reported any error or warning messages. If it was an error, the MobiLink server would have just failed the synchronization request without giving any reasons. This problem is fixed.

CR:552323

CR Number:   552323 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 2125 08 Dec 2008 Fixed 11.0.0 1547 08 Dec 2008 Fixed Description The conversion of NUMERIC values to or from VARCHAR was incorrect. This has now been corrected. UltraLiteJ should now produce the same conversions as does UltraLite.

CR:552355

CR Number:   552355 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 2124 09 Dec 2008 Fixed 11.0.0 1546 09 Dec 2008 Fixed Description The table editor could have crashed when the Compressed column heading was selected. It could also have crashed when opening, if the last time a column heading was selected in the Table editor, the Compressed column was selected. This has been fixed.

CR:552454

CR Number:   552454 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2033 09 Dec 2008 Fixed Description The Import Wizard would have shown an empty combobox of databases when importing from an Oracle database. Clicking on the combobox would have caused the Interactive SQL utility to report a NullPointerException. This has been fixed. The combobox is now hidden in this case.

CR:552465

CR Number:   552465 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 2125 09 Dec 2008 Fixed 11.0.0 1548 09 Dec 2008 Fixed Description If an application attempted to migrate tables containing unique constraints, either by using sa_migrate or Sybase Central, then there was a possibility that the migration would have failed because some of the foreign keys could not have been created. This problem has now been fixed, but only if the remote data access class involved is one of SAODBC or SAJDBC.

CR:552473

CR Number:   552473 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2033 09 Dec 2008 Fixed Description When attempting to export results to an Oracle database using the iAnywhere Oracle ODBC driver, the Export wizard would have inappropriately prompted for a database name and then reported a NullPointerException when the "Next" button was clicked. This has been fixed. The "Database" combobox is no longer displayed in this case.

CR:552488

CR Number:   552488 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 3815 09 Dec 2008 Fixed Description The server could have failed assertion 201138 - "Attempt to allocate page ... beyond end of dbspace". For the assertion to have occurred, the database must have had an additional (non-primary) dbspace, and an operation such as TRUNCATE, DROP TABLE, DROP INDEX, etc must have been performed on an object in that dbspace. This has now been fixed.

CR:552493

CR Number:   552493 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 2033 09 Dec 2008 Fixed 11.0.0 1548 09 Dec 2008 Fixed 10.0.1 3815 09 Dec 2008 Fixed Description When rebuilding databases on Windows Mobile devices, the Unload utility (dbunload) could have failed with the error "Table SYSPROCP not found". If the unload was successful, reloading the new database by running the resulting reload.sql file with the Script Execution utility (dbrunsql) could have failed with the error "Cursor not open" when executing a call statement. Both of these problem have now been corrected.

CR:552501

CR Number:   552501 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2033 09 Dec 2008 Fixed Description The Export wizard could have crashed when exporting to ASE, using the ASE Organic ODBC driver, into a new table. This has been fixed.

CR:552503

CR Number:   552503 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 2124 08 Dec 2008 Fixed 10.0.1 3805 08 Dec 2008 Fixed Description SQL statements which don't contain Transact-SQL OUTER JOINs, OUTER JOINs, KEY JOINs, or NATURAL JOINs will now skip some of the optimizations implemented in the server, which will improve the DESCRIBE time.

CR:552587

CR Number:   552587 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 2126 09 Dec 2008 Fixed 11.0.0 1549 09 Dec 2008 Fixed 10.0.1 3815 09 Dec 2008 Fixed 9.0.2 3765 09 Dec 2008 Fixed Description If an application created a remote server and then accessed that remote server using a different case than the one specified on the CREATE SERVER statement, the server would have incorrectly opened additional connections to the remote server. For example, suppose the application executed the following CREATE SERVER statement: CREATE SERVER MyServer CLASS ... and then created two proxy tables as follows: CREATE EXISTING TABLE table1 AT 'myserver...' CREATE EXISTING TABLE table2 AT 'MYserver...' If the application now queried "table1", the remote data access layer would have correctly established a connection to the remote and returned the requested data. If the application then queried "table2", the data access layer should reuse the connection previously established to the remote, but the server instead would have created a new connection to the remote. This problem has now been fixed.

CR:552591

CR Number:   552591 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) 9.0.2 3765 09 Dec 2008 Fixed Description If an Open Client or jConnect application executed a query that involved the use of host variables within a batch, then the server would have crashed, rather than giving the "Host variables may not be used within a batch" error message. This problem has now been fixed.

CR:552595

CR Number:   552595 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 2128 16 Dec 2008 Fixed 11.0.0 1552 16 Dec 2008 Fixed 10.0.1 3818 16 Dec 2008 Fixed Description In exceptionally rare conditions, typically while the server was under heavy load or processing many backups on many databases simultaneously, a backup could hang and the CPU usage of the server could have gone to 100%. This has been fixed. A workaround is to use a higher value on the -gn command line switch.

CR:552620

CR Number:   552620 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 2033 10 Dec 2008 Fixed 11.0.0 1550 10 Dec 2008 Fixed 10.0.1 3816 10 Dec 2008 Fixed Description After the server had started a database that required recovery, it could have crashed when running a cleaner. This has now been fixed.

CR:552627

CR Number:   552627 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2533 26 Apr 2010 Fixed 11.0.1 2429 26 Apr 2010 Fixed 12.0.1 2891 15 Sep 2010 Fixed Description If the language DLL was missing, the utilities createcert, viewcert, createkey, and mlfiletransfer would all have continued to execute, but would not have output any string resources. These utilities will now fail in this case with an appropriate error message. Also, the usage text for createcert and viewcert will now display the options in alphabetical order.

CR:552638

CR Number:   552638 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.1 2119 10 Dec 2008 Fixed 11.0.0 1541 10 Dec 2008 Fixed Description The Relay server may have run out of shared memory when under high load. This was more likely to have occurred when the Relay Server was hosting a large number of backend servers. This has been fixed by leaving spare room in shared memory according to the startup configuration. The user specified amount of shared memory is left for relaying traffic.

CR:552644

CR Number:   552644 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.1 2033 10 Dec 2008 Fixed 11.0.0 1541 10 Dec 2008 Fixed Description Up channel recovery upon the Relay Server Outbound Enabler detecting a communication error may have sometimes failed on some active sessions. This has been corrected. Note, normal up channel renewal was not affected by this fix.

CR:552648

CR Number:   552648 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 2126 10 Dec 2008 Fixed 11.0.0 1549 10 Dec 2008 Fixed 10.0.1 3815 10 Dec 2008 Fixed Description Renaming a transaction log via a BACKUP statement could have failed as a result of a transient sharing violation error on Windows. The error may have been caused by a virus scanner or other software accessing the file as it is being renamed. This has been fixed.

CR:552649

CR Number:   552649 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.1 2033 10 Dec 2008 Fixed 11.0.0 1546 10 Dec 2008 Fixed Description The Relay Server Outbound Enabler would have held on to a backend connections until the application timed out, when the request/response processing of the associated session had failed. Tnis has been fixed so that the Relay Server will now forward a command to the Outbound Enabler to explicitly disconnect the faulty session.

CR:552653

CR Number:   552653 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 2034 11 Dec 2008 Fixed 11.0.0 1550 12 Dec 2008 Fixed 10.0.1 3816 11 Dec 2008 Fixed Description Some situations, similar to those fixed for Engineering case 545904, allowed the server to hang while concurrently updating rows containing blobs. This has been fixed.

CR:552658

CR Number:   552658 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.1 2033 10 Dec 2008 Fixed 11.0.0 1546 10 Dec 2008 Fixed Description The Relay Server may have crashed under stress and the Outbound Enabler may not have been able to recover connections to it, even when IIS replenished the service with a new worker. These potential crashes have been fixed.

CR:552672

CR Number:   552672 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 2126 12 Dec 2008 Fixed 11.0.0 1550 12 Dec 2008 Fixed Description The combination of the HAVING clause containing a single-row subquery, and a temporary table referenced in the ORDER BY and/or GROUP BY clauses, could have produced incorrect results or a crash. This has now been fixed.

CR:552716

CR Number:   552716 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.1 2033 11 Dec 2008 Fixed 11.0.0 1548 11 Dec 2008 Fixed Description The Relay Server's throughput may have been reduced significantly when under load with Afaria traffic. This was caused by Afaria traffic not terminating persistent http sessions properly, when using Connection: close header. IIS did not release its resources until the connection's Keep-Alive timeout. Per-process resource limits cap the throughput when enough sessions are waiting to be timed out by IIS. This has been fixed bay having the Relay Server terminate Keep-Alive connections regardless of the presence of the Connection: close header, in the case where content-length is violated. Since Afaria traffic always violates content-length on the last request, in both of their POST and GET sessions, IIS will no longer hold on to keep-alive resources when the last request of their session exit the web server extension. This change also stops the Relay Server from complaining about content-length violations, if the client identifies itself as an Afaria client. The I/O error only is being suppressed. A user workaround is to increase web garden size (i.e. adding more worker processes) of the application pool associated with the rs_client.dll web server extension. This user workaround is inefficient though, letting limited resources to be held idle for unnecessary amount of time. With this fix, per process resource caps are no longer a reason for increasing the web garden size.

CR:552720

CR Number:   552720 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.1 2033 10 Dec 2008 Fixed 11.0.0 1548 10 Dec 2008 Fixed Description When the Relay Server was under heavy load, with verbosity set to 4 or higher, it may have occassionally reported an OE_BACKEND_DISCONNECTED error. This was due to another session having taken over the request id. This was not harmful to known client types, as all known clients initiates their own disconnect. However, this may have caused the Relay Server to hold onto resource for the worker waiting for that packet. This would have timeout in 100 sec, and was transparent to the client. This has been fixed, the client worker is no longer held up until it ties out, as the faulty discarding has being removed.

CR:552729

CR Number:   552729 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 2033 10 Dec 2008 Fixed 11.0.0 1550 10 Dec 2008 Fixed Description Under rare circumstances, the server could have crashed, or failed an assertion, if it needed to grow a database file quickly by a large amount (e.g., as a result of inserting a very large blob). Furthermore, there was a possibility for corruption affecting the data that triggered the file growth. This has now been fixed.

CR:552739

CR Number:   552739 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2034 15 Dec 2008 Fixed 11.0.0 1552 15 Dec 2008 Fixed 10.0.1 3818 15 Dec 2008 Fixed Description For an ADO/OLE DB application, if the CursorLocation was adUseClient and the size of the query was larger than 4K characters, then the SQL Anywhere OLE DB provider would have crashed. Also, if the client query contained single quotes (apostrophes), then the query metadata would not have been obtained. Both of these problems have now been fixed.

CR:552760

CR Number:   552760 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 15 Dec 2008 Fixed 11.0.0 1550 15 Dec 2008 Fixed 10.0.1 3817 15 Dec 2008 Fixed Description If the default port number was already in use (eg. by another server), the server may have failed to start TCP/IP, rather than choosing a different port number. If the -z command line option was used, the error "TCP/IP link, function bind, error code 10013" would have been displayed on the server console. This would only have happened on Windows Server 2003, and has now been fixed.

CR:552767

CR Number:   552767 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2033 11 Dec 2008 Fixed 11.0.0 1550 11 Dec 2008 Fixed Description A QAnywhere application could have reported a deadlock error from the SQL Anywhere server, if the application was attempting to retrieve a message from the message store while the QAnywhere agent was synchronizing. This has now been fixed.

CR:552771

CR Number:   552771 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 2126 11 Dec 2008 Fixed 11.0.0 1550 11 Dec 2008 Fixed Description Using a poorly formed connection string ("-c" command line option) could have caused the Interactive SQL utility (dbisql) to crash on startup. This has been fixed.

CR:552779

CR Number:   552779 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2128 16 Dec 2008 Fixed 11.0.0 1552 16 Dec 2008 Fixed 10.0.1 3818 16 Dec 2008 Fixed Description When executing an "OUTPUT" statement, dbisqlc would have executed the current query two extra times. Some output file formats require a particular date format to be used and in version 10.0.0 and later, changing the date format option on a connection does not affect cursors that are already open. To work around this change of behaviour, dbisqlc closed the current query, changed the DATE_FORMAT option to the format required by the output file format and then reopened the query to write the result set to the output file. It then closed the query again, restored the old DATE_FORMAT option, and reopened the query. Thus the query was executed a total of three times. Note that the Java-based dbisql has always executed the query a total of two times (once for the original query, once for the OUTPUT statement). That behaviour is not addressed by this change. The problem in dbisqlc has been corrected in most cases by avoiding the close/set-date-format/reopen operations if the requested output file format does not have a mandated date format or if the current date format matches the date format required by the output file format. If the specified output file format requires a specific date format and it is different from the current date format, the query will still be executed two extra times. To avoid executing the query multiple times, set the DATE_FORMAT option for the current connection as listed below before executing the query for the first time: Output file format DATE_FORMAT setting DBASEII MM/DD/YY DBASEIII YYYMMDD FOXPRO YYYMMDD WATFILE YYYY/MM/DD Output file formats not listed above do not have a mandated date format and dbisqlc will not close/reopen the current query to execute the OUTPUT statement.

CR:552888

CR Number:   552888 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2127 12 Dec 2008 Fixed 11.0.0 1550 12 Dec 2008 Fixed 10.0.1 3817 12 Dec 2008 Fixed 9.0.2 3766 12 Dec 2008 Fixed Description If an application called PreparedStatement.setBlob(), and if the underlying java.sql.Blob implementation misbehaved, then there was a chance that the iAnywhere JDBC driver would have failed when the PreparedStatement was executed. Workarounds have now been implemented in the iAnywhere JDBC driver to attempt to handle the Blob implementation misbehaviour.

CR:552921

CR Number:   552921 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 28 Jan 2009 Fixed Description When assigning the result of a bitwise NOT operation on a value of type Bit, TinyInt or Unsigned SmallInt to the same type, the error "Value -1 out of range for destination" was returned. This was due to these types being converted to an Integer before applying the operation. This has been fixed

CR:552931

CR Number:   552931 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2034 15 Dec 2008 Fixed 11.0.0 1550 15 Dec 2008 Fixed 10.0.1 3817 15 Dec 2008 Fixed Description When executing a batch command which returned multiple resultsets, if fetching the second or subsequent resultset caused an error, no exception was returned to the application. This problem has now been fixed.

CR:553064

CR Number:   553064 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 2127 12 Dec 2008 Fixed 11.0.0 1550 12 Dec 2008 Fixed 10.0.1 3817 12 Dec 2008 Fixed Description If an application accidentally defined a Remote Data Access server that used the SAJDBC class and connected back to the same database as the local user connection, then an error indicating that the server definition was circular was not displayed. This problem is now fixed and an error message is now displayed. Note that this problem does not affect SAODBC class remote servers.

CR:553103

CR Number:   553103 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2124 12 Dec 2008 Fixed 10.0.1 3800 12 Dec 2008 Fixed Description During the optimization process, the optimizer creates and maintains order properties for all physical operators placed in the access plans generated as part of the search space generation process. These order properties are used to decide if SORT physical operators are needed, for example to satisfy an ORDER BY clause at the root of the access plan. Maintaining and tracking order properties are expensive operations as described in [1]. For performance reasons, the optimizer will now build and maintain only those order properties needed by an interesting order property, such as the one imposed by an ORDER BY clause. This change does not affect in anyway the performance of the order optimization, it just makes the optimization process more efficient. [1]Database System with Methodology for Generalized Order OptimizationMatthew Young-Lai, Anisoara Nica, 2007 US Patent 7,359,922.

CR:553289

CR Number:   553289 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 2133 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed Description If a query execution plan contained a SORT operator in a parallel execution strategy, it was possible for the server to crash while processing the request. This type of plan can be used during a CREATE INDEX statement. The crash was timing and load dependent and would have predominantly affected servers processing requests from multiple connections. This problem has been fixed.

CR:553300

CR Number:   553300 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2034 15 Dec 2008 Fixed 10.0.1 3817 15 Dec 2008 Fixed Description Network error messages in the MobiLink monitor, the SA Monitor, the Notifier or the QAnywhere server could have been garbled on non-English machines. This has been fixed.

CR:553309

CR Number:   553309 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 2128 16 Dec 2008 Fixed 11.0.0 1552 16 Dec 2008 Fixed Description A cursors position in a result set was not always correct after changes were made (i.e. inserts, updates and deletes). This has been corrected.

CR:553310

CR Number:   553310 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 2128 16 Dec 2008 Fixed 11.0.0 1552 16 Dec 2008 Fixed 10.0.1 3818 16 Dec 2008 Fixed Description An application that uses the iAnywhere JDBC driver must now have the jodbc.jar built with the same build number as the dbjodbc and mljodbc shared objects. If the jar and shared objects are out of sync, a SQLException will be thrown at connect time and the connection will be refused.

CR:553312

CR Number:   553312 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2034 16 Dec 2008 Fixed 10.0.1 3818 16 Dec 2008 Fixed 11.0.0 1565 22 Jan 2009 Fixed Description If the MobiLink Monitor's Details Table, Utilization Graph, or Overview panes were disabled, when reenabled they might not be visible, under some circumstances, or a program error may have occurred. Also, resizing a pane or the application, could have produced unexpected results. These problems have been fixed. Now when resizing the application, only the Chart pane size is changed; and when resizing a pane, only the panes on either side of the splitter bar are affected.

CR:553387

CR Number:   553387 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2035 17 Dec 2008 Fixed 11.0.0 1552 17 Dec 2008 Fixed 10.0.1 3818 17 Dec 2008 Fixed Description The following fixes have been made to support MobiLink in DB2 Mainframe Compatibility Mode - The ml_pt_script table did not have an explicit ROWID column. This was required for the CLOB column. Some D2M deployments support an implicit ROWID, and some do not, inluding compatibility mode. Fixed by adding an explicit ROWID column. - The SQL used for JCL-based CREATE PROCEDURE statements included the SQL body of the stored procedure. This worked most of the time, but not under compatibility mode. Now, the external-procedure form of CREATE PROCEDURE is used, which doesn't include the body (which of course isn't necessary because it is in the *.xmit files). - The SQL used to create the SQL-based D2M stored procedures didn't escape single quotes. This wasn't noticed because D2M treats most unquoted text between single quotes as a string, so it just worked. Single quotes are now escaped in the procedure body, inside the call to DSNTPSMP. - The D2M ml_add_pt_script stored procedure didn't work under compatibility mode, for several reasons: 1) it had a VARCHAR( 256 ) parameter (the flags for the SQL Passthrough script) that caused conversion problems inside the procedure when run under compatibility mode. This parameter has been changed to VARCHAR( 255 ). 2) it referenced a Unicode string, which isn't supported under compatibility mode. This has been fixed by replacing it with a non-Unicode string. 3) it used a form of the SIGNAL statement that isn't supported under compatibility mode. This has been corrected.

CR:553469

CR Number:   553469 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 3822 24 Dec 2008 Fixed Description Backups done where the checkpoint log was copied (WITH CHECKPOINT LOG COPY), did not mark the dbspaces as active. This allowed databases that possibly required recovery to be started in read-only mode. If this was done, it could have lead to assertion failures as the server tried to flush pages that had been dirtied. This has been fixed.

CR:553482

CR Number:   553482 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 2034 17 Dec 2008 Fixed 11.0.0 1552 17 Dec 2008 Fixed 10.0.1 3821 17 Dec 2008 Fixed Description Prior to executing the "begin_connection_autocommit" script, the MobiLink server will temporarily turn on auto-commit on the ODBC connection, due to restrictions with some consolidated databases. On ASE consolidated databases, this will generate a warning (SQL_SUCCESS_WITH_INFO) in the ODBC driver: "AutoCommit option has changed to true. All pending statements on this transaction (if any) are committed." This warning was being generated whether the begin_connection_autocommit script was defined or was absent. This has been fixed. The server will now only turn on auto-commit when the script is defined and will only execute the script if it is defined. If the script is defined, it is still possible to see this warning logged in the MobiLink server console log. This is expected behaviour.

CR:553491

CR Number:   553491 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 2129 16 Dec 2008 Fixed 11.0.0 1552 16 Dec 2008 Fixed 10.0.1 3817 16 Dec 2008 Fixed Description The Apache redirector module would have crashed when used with the Sun built Apache web server that currently ships with the Solaris operating system. This has been fixed.

CR:553520

CR Number:   553520 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 2034 18 Dec 2008 Fixed 11.0.0 1552 18 Dec 2008 Fixed Description If a database server acting as mirror lost its connections to the arbiter and primary server, the database being mirrored did not restart and wait for the connections to be re-established. This has been fixed.

CR:553561

CR Number:   553561 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2130 22 Dec 2008 Fixed 11.0.0 1553 22 Dec 2008 Fixed Description The OUTPUT statement would have unnecessarily re-executed the query which generated the last result set, if the Interactive SQL utility was run in windowed mode and the result set had not already been displayed. This has been fixed so that the statement is not re-executed in this case.

CR:553600

CR Number:   553600 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 2133 05 Jan 2009 Fixed 11.0.0 1553 05 Jan 2009 Fixed Description A query of the form: "SELECT * FROM table-expression" could have been misdiagnosed as a syntax error when there was exactly one column in the select list. This has now been fixed.

CR:553687

CR Number:   553687 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 3819 17 Dec 2008 Fixed Description Tables storing CHAR and NCHAR values longer than approximately 126 bytes, may have used two bytes of storage more per value than was necessary. If the column's PREFIX value was smaller than 126, then strings longer than the specified prefix value would have used two extra unnecessary bytes as well. This has been fixed. Note, rebuilding the database after applying this fix will remove all of the unneeded bytes.

CR:553689

CR Number:   553689 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 2136 12 Jan 2009 Fixed 11.0.0 1560 12 Jan 2009 Fixed Description If a query contained at least two predicates on the same column T.A with the following conditions: 1. there existed an equality predicate T.A = expression, with a selectivity estimation of selectivity1, and the expression was not a constant 2. there existed a range predicate on T.A with constant bounds (for example, T.A > 111), with a selectivity estimation of selectivity2 3. there existed an index on column T.A, where the column T.A may have been the only column in the index, or the index had a prefix of other columns before T.A, all of which are equated with constants in the query: e.g., the index idx<C1, C2, A> is defined, and the predicates 'T.C1 = 10 and T.C2 = 20 and T.A > 111 and T.A = R.X' are used in the query. 4. The selectivity estimation of the range predicate was much larger then the selectivity estimation of the equality predicate, i.e., selectivity1 << selectivity2 Such a query had an overestimated number of rows, and the execution plan chosen by the optimizer may have been inefficient. This has been fixed.

CR:553693

CR Number:   553693 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 2035 18 Dec 2008 Fixed 11.0.0 1553 18 Dec 2008 Fixed 10.0.1 3819 18 Dec 2008 Fixed Description If a server had many external environment requests active, and several of these external environment requests were subsequently cancelled at the same time, there was a chance the server would have crashed. There was a very small window where a cancel request could have been ignored by the external connection. This has now been fixed.

CR:553719

CR Number:   553719 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 2037 05 Jan 2009 Fixed 11.0.0 1553 05 Jan 2009 Fixed 10.0.1 3829 05 Jan 2009 Fixed Description The Unload utility (dbunload) was not able to rebuild a pre-Version 10 database if the variable SATMP was unset, but variable ASTMP was set. Dbunload would have returned a connection error in this case. This has been fixed. Note, as workaround the SATMP variable can be set.

CR:553720

CR Number:   553720 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 2129 23 Dec 2008 Fixed 11.0.0 1553 23 Dec 2008 Fixed 10.0.1 3819 23 Dec 2008 Fixed Description If an HTTP/1.1 client made a request on a keep-alive connection, and then after receiving the response, did not send another full request over the connection for one minute, the connection would have timed out and sent a 408 Request Timeout status message. This is consistent with the HTTP/1.1 specification, but if the HTTP client was Apache, it would have been confused by the error message. The behaviour has been changed so that the error status code is suppressed (and the connection is simply closed) if all of the following are true: - A complete request and response have previously been sent on the connection - No data has been received on the connection since the most recent response was sent - The keep-alive timeout has expired

CR:553748

CR Number:   553748 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2129 18 Dec 2008 Fixed 11.0.0 1553 18 Dec 2008 Fixed 10.0.1 3819 18 Dec 2008 Fixed 9.0.2 3769 18 Dec 2008 Fixed Description When using the iAS ODBC driver for Oracle, calling SQLColAttribute with an attribute code of SQL_DESC_TYPE_NAME would not have returned the type names of columns. This has now been fixed.

CR:553752

CR Number:   553752 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2130 22 Dec 2008 Fixed 11.0.0 1553 22 Dec 2008 Fixed 9.0.2 3770 22 Dec 2008 Fixed 10.0.1 3820 24 Dec 2008 Fixed Description If a CREATE SYNCHRONIZATION SUBSCRIPTION statement was executed with an OPTION clause that gets the option value from a variable (e.g. OPTION sv=@Var) and the variable was set to null, then the server may have crashed, or inserted a random option value into the catalogs. This has been fixed so that the server now returns a sql error (SQLSTATE_BAD_SYNC_OPTION_VALUE) "Synchronization option '%1' contains semi-colon, equal sign, curly brace, or is null".

CR:553759

CR Number:   553759 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2129 18 Dec 2008 Fixed 11.0.0 1553 18 Dec 2008 Fixed 10.0.1 3819 18 Dec 2008 Fixed Description The "Replace All" action in the syntax highlighting editor could have corrupted the text if the action was restricted to the selected text. This has been fixed.

CR:553775

CR Number:   553775 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 2038 06 Jan 2009 Fixed 11.0.0 1553 06 Jan 2009 Fixed Description While synchronizing a large download using "direct TCP" on BlackBerry devices (not through the BES), the synchronization would have failed with "... Max connections opened". This has been fixed. Note: For IDENT BlackBerry devices, the default is Direct TCP connections. For non-IDENT BlackBerry devices, the default is BES connections. Using the URL suffix ";deviceside=false" forces Direct TCP connections.

CR:553897

CR Number:   553897 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 2130 18 Dec 2008 Fixed 11.0.0 1553 18 Dec 2008 Fixed Description If an application used one of the C_ODBC32, C_ODBC64, C_ESQL32 or C_ESQL64 external environments and specified .dll or .so in the external name clause, then the external environment would have incorrectly added an extra .dll or .so to the shared object name and then give an error. This problem has now been fixed. Note that a workaround is to not specify the .dll or .so in the external name clause.

CR:553901

CR Number:   553901 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 2035 18 Dec 2008 Fixed 11.0.0 1553 18 Dec 2008 Fixed Description On rare occasions, a mirror server could have crashed, or failed an assertion on shutdown, particularly if the arbiter and primary were being shut down at the same time. On Linux, the problem could have also manifest itself as a hang in libc's __lll_mutex_lock_wait. This has been fixed.

CR:553911

CR Number:   553911 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 2130 22 Dec 2008 Fixed 11.0.0 1553 22 Dec 2008 Fixed 10.0.1 3819 22 Dec 2008 Fixed Description The Service utility (dbsvc) included with versions 10.0.0 and up, did not recognize services created with pre-10.0 versions of dbsvc. This has been fixed. Old services can now be viewed, deleted, started and stopped. If an old service is created using the patched dbsvc, the new service will no longer be visible by pre-10.0 dbsvc.

CR:554067

CR Number:   554067 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 2130 22 Dec 2008 Fixed 11.0.0 1553 22 Dec 2008 Fixed Description A Windows application using the iAnywhere JDBC driver, could have hung if all of the following conditions were true: 1) the application installed a message handler connections 2) the application shared a connection amongst multiple threads 3) one of the threads executed a statement that returned an asynchronous message 4) at the same time another thread used the same connection and called createStatement(), prepareStatement() or prepareCall(), before the asynchronous message was returned from the server This problem has now been fixed.

CR:554080

CR Number:   554080 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2130 22 Dec 2008 Fixed 11.0.0 1553 22 Dec 2008 Fixed 10.0.1 3820 22 Dec 2008 Fixed Description Applications which used the EncryptedPassword connection parameter could have crashed when attempting to connect. This has been fixed.

CR:554106

CR Number:   554106 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2036 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed 10.0.1 3820 24 Dec 2008 Fixed Description The ODBC driver would have issued an HY090 error if any of the connection string parameter to SQLConnect were specified as a combination of a NULL pointer and SQL_NTS. This situation is permitted by the ODBC specification. As a result, this restriction has now been removed.

CR:554242

CR Number:   554242 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2134 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed 10.0.1 3821 24 Dec 2008 Fixed Description The Validation utility (dbvalid) was not validating materialized views by default. The utility was generating a list of tables to validate that only included base tables. This has been corrected incorporate initialized materialized views in either the fresh or stale state.

CR:554265

CR Number:   554265 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 2132 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed Description If more than one message store connection was open, and the connections were broken from outside of Sybase Central, attempting to then disconnect from within Sybase Central could have caused Sybase Central to crash. This has been fixed.

CR:554271

CR Number:   554271 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2036 24 Dec 2008 Fixed 10.0.1 3821 24 Dec 2008 Fixed Description If the MobiLink client (dbmlsync) was run against a database with a character set that was different from the operating system's character set, then errors generated by the database would have been garbled when displayed in the dbmlsync log. This has been corrected so that these messages will now be displayed correctly.

CR:554273

CR Number:   554273 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 2132 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed Description If a database mirroring system was running in asynchronous mode and experienced a very high rate of transaction log page updates, the mirror server could have crashed or reported a failed assertion. This has been fixed.

CR:554369

CR Number:   554369 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 2133 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed Description Using the property sheet to rename a primary key, foreign key or unique constraint, could have caused Sybase Central to crash. This has been fixed.

CR:554373

CR Number:   554373 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 2133 24 Dec 2008 Fixed 11.0.0 1553 24 Dec 2008 Fixed Description Sybase Central would have crashed if the server was shut down while the Performance Monitor tab was displayed. This has been fixed.

CR:554383

CR Number:   554383 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 2144 29 Jan 2009 Fixed 11.0.0 1568 29 Jan 2009 Fixed 10.0.1 3839 29 Jan 2009 Fixed Description In the MobiLink Monitor Details Table, if the optional column "connection_retries", or optional columns starting with "download_" or "sync_", were enabled, the column labels for these columns would have been misaligned by one or two columns. A similar problem would have occurred when exporting to a database, where that data was exported to incorrect columns in the database tables. Both of these problems have been fixed.

CR:554708

CR Number:   554708 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2044 14 Apr 2009 Fixed Description Attempting to install an EBF against an Evaluation, Developer, Web or Runtime edition of 11.0.0 would have failed with a missing directory table entry error. This has been fixed in version 11.0.1.

CR:554764

CR Number:   554764 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2133 05 Jan 2009 Fixed 11.0.0 1553 05 Jan 2009 Fixed 10.0.1 3827 05 Jan 2009 Fixed Description When running on heavily loaded Unix systems, applications using a large number of connections may have crashed. This has been fixed. Workaround Description  Not a workaround.

CR:554779

CR Number:   554779 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2038 06 Jan 2009 Fixed 11.0.0 1553 06 Jan 2009 Fixed 10.0.1 3830 06 Jan 2009 Fixed Description It was not possible to retrieve index or key information through calls to the SAConnection.GetSchem method. The SAConnection.GetSchema method was using a view which did not include the primary keys. This problem has been fixed.

CR:554781

CR Number:   554781 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 2135 05 Jan 2009 Fixed 11.0.0 1556 05 Jan 2009 Fixed Description In a database mirroring system, if the mirror server was starting while the transaction log on the primary server was being renamed, the primary server could have crashed. This has been fixed.

CR:554782

CR Number:   554782 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 2005 05 Jan 2009 Fixed Description For particular forms of statements, it was possible for the server to incorrectly return the following error when trying to open a cursor: The optimizer was unable to construct a valid access plan [-727] ['WI010'] In order for the problem to have occurred, the statement must have referred to only a single table and used only columns satisfied by an index. Further, snapshot isolation must have been enabled. This has now been fixed. As a workaround, the statement hint "options(force optimization)" can be included to avoid the error.

CR:554854

CR Number:   554854 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 2134 06 Jan 2009 Fixed Description If the evaluation of certain expressions resulted in an error code, it was possible for memory to be leaked. When this memory leak occured in an INSERT, UPDATE, DELETE, or SELECT statement, the memory leak would have been transient. In the case of stored procedures and triggers, this leak could have lead to a slow increase in the size of the main heap. In that case, less memory would have been available for caching file pages, or other purposes, until a reboot. This problem has been fixed.

CR:554876

CR Number:   554876 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 2134 06 Jan 2009 Fixed 11.0.0 1553 06 Jan 2009 Fixed Description If an application established an HTTP session from the PHP external environment, then the server may have hung or crashed. This problem has now been fixed.

CR:554880

CR Number:   554880 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2134 06 Jan 2009 Fixed Description If the Server Monitor was used to monitor several servers, and one or more of those servers were down, then it was likely that the server monitor requests would have started to time out, and cause communication errors within the browser. This problem has now been fixed.

CR:554886

CR Number:   554886 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 2134 06 Jan 2009 Fixed 11.0.0 1553 06 Jan 2009 Fixed 10.0.1 3830 06 Jan 2009 Fixed Description Some particular constructions of the LIST aggregate could have caused the server to crash while processing the statement containing the LIST aggregate. In order for the crash to occur, the LIST must have contained an ORDER BY clause. This has been fixed.

CR:554889

CR Number:   554889 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 09 Jan 2009 Fixed 11.0.0 1559 09 Jan 2009 Fixed 10.0.1 3832 09 Jan 2009 Fixed Description Simple SELECT, UPDATE, and DELETE statements with a specific predicate structure could have caused the server to crash. A workaround to avoid the crash is to set the option Max_plans_cached=0. This problem has been fixed.

CR:554998

CR Number:   554998 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2133 06 Jan 2009 Fixed 11.0.0 1553 06 Jan 2009 Fixed 10.0.1 3827 06 Jan 2009 Fixed Description When ADO asks for the schema information related to a query (e.g., SELECT * FROM Products), it requests a number of attributes like "IDNAME", "TABLENAME", etc. The SQL Anywhere OLE DB provider returns a DBID for schema rowset columns that matches Microsoft's declared DBID. For example, the schema column DBCOLUMN_IDNAME is defined in Microsoft's OLEDB.H header file as follows: extern const OLEDBDECLSPEC DBID DBCOLUMN_IDNAME = {DBCIDGUID, DBKIND_GUID_PROPID, (LPOLESTR)2}; This is what the OLE DB provider would return as the DBID for the "IDNAME" column. This strategy works for many ADO methods that request schema information. However, the following example illustrates a problem with the ADO RecordSet Save() method. Dim strConnection = "PROVIDER=SAOLEDB;ServerName=demo;DatabaseName=demo;USERID=DBA;PASSWORD=sql" Dim strSQLStatement = "SELECT ID, Name FROM Products" Dim strXMLLocation = "c:\\temp\\products.xml" Dim objADOConnection As New ADODB.Connection Dim objADORecordSet As New ADODB.Recordset objADOConnection.Open(strConnection) objADORecordSet.Open(strSQLStatement, objADOConnection, ADODB.CursorTypeEnum.adOpenStatic, ADODB.LockTypeEnum.adLockOptimistic) If Not (objADORecordSet.EOF And objADORecordSet.BOF) Then objADORecordSet.MoveFirst() objADORecordSet.Save(strXMLLocation, ADODB.PersistFormatEnum.adPersistXML) End If For reasons unknown, the ADO RecordSet Save() method returns the error "catastrophic failure". The SQL Anywhere OLE DB provider has been changed to return only the "property ID" part of the DBID. This is equivalent to returning the following structure. extern const OLEDBDECLSPEC DBID DBCOLUMN_IDNAME = {NULL, DBKIND_PROPID, (LPOLESTR)2}; This permits the ADO RecordSet Save() method to complete successfully.

CR:555007

CR Number:   555007 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.1 2135 06 Jan 2009 Fixed 11.0.0 1553 06 Jan 2009 Fixed 10.0.1 3830 06 Jan 2009 Fixed Description Sybase Central could have crashed when attempting to change the visible columns (via View -> Choose Columns...), or column widths, while the MobiLink 11 node was selected in the tree. In addition, when in Model mode, the list of columns under the View -> Sort menu would sometimes not have contained all the displayed columns when the MobiLink 11 node was selected in the tree. Both of these issues have now been fixed.

CR:555024

CR Number:   555024 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2135 06 Jan 2009 Fixed 11.0.0 1558 06 Jan 2009 Fixed Description When the server was run on Unix systems, the PHP external environment would have reported all errors, warnings, etc, even when PHP was explicitly configured not to do so. This has been fixed.

CR:555033

CR Number:   555033 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2135 07 Jan 2009 Fixed Description Providing the function ML_GET_SERVER_NOTIFICATION() with long MobiLink stream parameters (longer than 128 characters) could have caused the results of the function call to be incorrect. This has been fixed so that the poll will now work with arbitrary length stream parameters

CR:555034

CR Number:   555034 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 2135 08 Jan 2009 Fixed 11.0.0 1558 08 Jan 2009 Fixed 10.0.1 3831 08 Jan 2009 Fixed Description Push notifications over a SYNC gateway may have stopped working after the listener reconnected. The was timing dependent and was more likely to have occurred when there was a proxy, a redirector, or a relay server being used between the listener and the SYNC gateway of the MobiLink server. The listener may have reconnected to the SYNC gateway when the IP address of the remote device had been changed, when the QAAgent registered with the listener on startup, or a communication error had occurred. This problem has now been fixed.

CR:555054

CR Number:   555054 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.1 2135 08 Jan 2009 Fixed 11.0.0 1558 08 Jan 2009 Fixed Description Sybase Central was allowing the modification or deletion of the QAnyNotifier_client notifier. Doing so could have caused problems with QAnywhere. To prevent any problems, it is now only possible to modify the notifier's description, polling interval and event SQL.

CR:555056

CR Number:   555056 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 2038 07 Jan 2009 Fixed 11.0.0 1558 07 Jan 2009 Fixed Description A new feature was added to the Interactive SQL utility (dbisql) in version 11.0.0, which automatically released database locks after executing queries when it was run as a windowed application. This feature was on by default, and was undocumented. It unfortunately also broke the locking tutorial, and introduced an unexpected behavioral change. The behavioral change has now been rectified. Automatic lock releasing is now OFF by default. This is a behavioral change from 11.0.0, but it makes dbisql consistent with older versions. Also, users can now control the automatic lock releasing feature explicitly. The "Result Set" tab in the "Options" window contains a new checkbox called "Automatically release locks". Check this if dbisql is to release locks after executing a statement.

CR:555059

CR Number:   555059 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2143 26 Jan 2009 Fixed 11.0.0 1567 26 Jan 2009 Fixed 10.0.1 3838 26 Jan 2009 Fixed 9.0.2 3785 26 Jan 2009 Fixed Description When using Microsoft's AppVerifier (a development/debugging tool), the tool may have reported various errors, such as the use of an invalid handle in client libraries (ODBC, dblib, etc) or in the database server. These problems have been fixed and the database server and client libraries now run cleanly under AppVerifier. Note, without the use of AppVerifier it would have been extremely rare for users to encounter these problems.

CR:555181

CR Number:   555181 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 2135 07 Jan 2009 Fixed 11.0.0 1559 07 Jan 2009 Fixed Description In very rare circumstances, cancelling a DDL statement could have caused the server to crash, cause corruption or possibly other erratic behaviour. The cancel would need to have been detected after a DDL completed successfully, but before the DDL was auto-committed, which is a very tiny window. Whether or not a problem would be caused by a cancel at that time, and if so, the nature of that problem also depended on the DDL itself and what the connection did afterwards. This problem has been fixed.

CR:555185

CR Number:   555185 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2038 08 Jan 2009 Fixed 11.0.0 1559 08 Jan 2009 Fixed 10.0.1 3831 08 Jan 2009 Fixed Description It was not possible to retrieve the columns for a primary key index using the method SAConnection.GetSchema. The SAConnection.GetSchema method was using a view which did not include the columns for primary keys. This problem has been fixed.

CR:555208

CR Number:   555208 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2135 08 Jan 2009 Fixed 11.0.0 1559 08 Jan 2009 Fixed 10.0.1 3831 08 Jan 2009 Fixed Description Interactive SQL utility options, which were set from a .SQL file while it was running as a console application, would not have been saved. This has been corrected so that now they are.

CR:555211

CR Number:   555211 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 2135 08 Jan 2009 Fixed 11.0.0 1559 08 Jan 2009 Fixed Description Sybase Central would have crashed when attempting to use the Column property sheet to rename a column that had not yet been saved to the database. This has been fixed.

CR:555228

CR Number:   555228 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 2135 08 Jan 2009 Fixed 11.0.0 1559 08 Jan 2009 Fixed 10.0.1 3831 08 Jan 2009 Fixed Description Under some circumstances the server could have crashed when a table was dropped. This has bben fixed.

CR:555236

CR Number:   555236 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 28 Jan 2009 Fixed 11.0.0 1568 28 Jan 2009 Fixed 10.0.1 3839 28 Jan 2009 Fixed Description SQLColumns returns a result set including COLUMN_SIZE, BUFFER_LENGTH, and CHAR_OCTET_LENGTH among other things. For a column typed NCHAR(30) or NVARCHAR(30), the COLUMN_SIZE was returned as 30 and the BUFFER_LENGTH as 30. The BUFFER_LENGTH should have been 60. For CHAR_OCTET_LENGTH, NULL is returned, whereas it should have ben 60 as well. From the ODBC standand: "COLUMN_SIZE": For character types, this is the length in characters of the data; The defined or maximum column size in characters of the column or parameter (as contained in the SQL_DESC_LENGTH descriptor field). For example, the column size of a single-byte character column defined as CHAR(10) is 10. "BUFFER_LENGTH": The defined or the maximum (for variable type) length of the column in bytes. This is the same value as the descriptor field SQL_DESC_OCTET_LENGTH. "CHAR_OCTET_LENGTH": The maximum length in bytes of a character or binary data type column. For all other data types, this column returns a NULL. These problems have been fixed.

CR:555245

CR Number:   555245 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2135 09 Jan 2009 Fixed Description Under rare circumstances, selecting a table type in the Query Editor could have caused an internal error. This problem was highly timing-dependent. This has been fixed.

CR:555250

CR Number:   555250 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 2135 09 Jan 2009 Fixed Description The name of the current user did not appear in the list of owners in the Import Wizard on the page that asks "Where do you want to save the data" if the current user does not own any database objects. Now, the user name always appears in the list of owners.