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

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

CR:562951

CR Number:   562951 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 2165 04 Mar 2009 Fixed Description If a database was created with the DBA user specified as "dba" (or Dba, DBa, DbA, dBA, dBa, dbA), unloading the database would have failed. This has been fixed.

CR:562957

CR Number:   562957 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3806 17 Mar 2009 Fixed Description The server may have crashed when executing a Group By Indexed strategy for a SELECT statement. This has been fixed.

CR:562962

CR Number:   562962 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   6.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2165 03 Mar 2009 Fixed 11.0.0 1584 03 Mar 2009 Fixed Description The QAnywhere message transmission status code which formerly displayed as "Local", is now displayed as "Do_not_transmit". This change was made to match the documentation.

CR:562971

CR Number:   562971 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2165 03 Mar 2009 Fixed Description Attempting to export data from a SQL Anywhere database into an UltraLite database would have failed if a value being exported was null and the target column in the UltraLite database was a unique identifier column. This is now fixed.

CR:562972

CR Number:   562972 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2165 04 Mar 2009 Fixed Description Attempting to export data from a SQL Anywhere database into an UltraLite database could have failed if a value being exported was a Date. This would happen when the option return_date_time_as_string was set to off. This is now fixed.

CR:563040

CR Number:   563040 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 19 Mar 2009 Fixed Description If an application used the CURRENT TIMESTAMP constant in an insert into a proxy table, there was a possibility that the server would have crashed. Note that the remote server needed to be either ASE, SQL Server, Oracle or generic ODBC, for this problem to occur. This problem has now been fixed.

CR:563117

CR Number:   563117 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 2164 04 Mar 2009 Fixed 11.0.0 1584 04 Mar 2009 Fixed Description When the Relay Server Outbound Enabler (rsoe) was started with http instead of https (i.e. -cr https=1;... ), it would not have been able to communicate with a newly added relay server. The workaround is to restart rsoe. This has been fixed.

CR:563118

CR Number:   563118 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 2164 05 Mar 2009 Fixed 11.0.0 1584 05 Mar 2009 Fixed Description If a communication error occurred at an early stage of the Relay Server Outbound Enabler (rsoe) attempting to establish the up channel with the Relay Server, the RSOE would have continued to fail to reconnect forever. This has been fixed. The workaround is to restart the RSOE.

CR:563132

CR Number:   563132 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 2166 04 Mar 2009 Fixed 11.0.0 1585 04 Mar 2009 Fixed Description An adddition fix was needed to avoid a boundary mis-routing problem introduced by the original fix for Engineering case 561378.

CR:563143

CR Number:   563143 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 2166 05 Mar 2009 Fixed 11.0.0 1584 05 Mar 2009 Fixed Description When a QAnywhere consolidated database contained a large number of messages that satisfied a delete rule, and the MobiLink server was shut down, the server would not have actually terminated until all messages had been deleted, which could have been a very long period of time. When delete rules are executed, old messages are deleted in batches of 100 at a time until there are no more messages satisfying the delete condition. However, there was no mechanism to stop the execution of delete rules on MobiLink server shutdown. Such a mechanism has now been added for delete and archive rules.

CR:563171

CR Number:   563171 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2166 05 Mar 2009 Fixed Description The MobiLink server would have failed synchronizations from version 10.0.1 and later clients, when they connected via HTTP. The error would have been 'HTTP error 404' (not found), and most clients would have reported this as the error. This has been fixed.

CR:563202

CR Number:   563202 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 2166 05 Mar 2009 Fixed Description The Interactive SQL utility (dbisql) would have reported an internal error when attempting to use the Import Wizard to import data from a SQL Anywhere database while connected to an UltraLite database. This has been fixed.

CR:563319

CR Number:   563319 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2168 06 Mar 2009 Fixed Description When creating or upgrading a database, the server looks for a file called authenticate.sql, which is used to set the database_authentication option. The file should reside in the <install_dir>\scripts directory, but the server would continue to look elsewhere if it was not found there. This has been fixed so that it looks for this file only in the scripts directory.

CR:563344

CR Number:   563344 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2183 20 Mar 2009 Fixed 9.0.2 3807 20 Mar 2009 Fixed Description In certain situations, the server could have crashed while processing a hash join. This has been fixed.

CR:563352

CR Number:   563352 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2166 05 Mar 2009 Fixed 11.0.0 1585 05 Mar 2009 Fixed Description Prebuilt binary libraries for PHP 5.2.8 have now been added.

CR:563394

CR Number:   563394 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 2167 06 Mar 2009 Fixed Description Execution of LOAD TABLE statement will now use asynchronous IO in order to improve performance. Actual performance gains will vary depending on hardware and database configuration but tests have shown an approximate doubling of performance. Asynchronous IO is only used when accessing a local data file (not a client file, etc).

CR:563404

CR Number:   563404 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 2167 06 Mar 2009 Fixed 11.0.0 1585 06 Mar 2009 Fixed 10.0.1 3857 06 Mar 2009 Fixed Description Synchronizations could have failed with protocol errors when some, but not all, of the parameters for a delete command in the .NET irect row API were set to DBNull.Value or null. This has been fixed so that an exception will be thrown when attempting to execute the command.

CR:563405

CR Number:   563405 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 2168 06 Mar 2009 Fixed 11.0.0 1585 06 Mar 2009 Fixed 10.0.1 3858 06 Mar 2009 Fixed Description The MobiLink server could have crashed if a IDataReader returned by MLUploadData was not closed. If the server didn't crash it would have leaked memory. The crash would have occurred at a random time after the synchronization completed. This has been fixed. Note that enclosing the use of the IDataReader in a 'using' block will automatically close it.

CR:563499

CR Number:   563499 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 2168 06 Mar 2009 Fixed 11.0.0 1586 06 Mar 2009 Fixed Description When processing a GROUP BY statement with a specific number of aggregates, it was possible for the server to crash. This has been fixed.

CR:563533

CR Number:   563533 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 3877 14 Apr 2009 Fixed Description Transactions could have failed with the error SQLSTATE_PREEMPTED being incorrectly returned to the application.

CR:563535

CR Number:   563535 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 2222 06 Mar 2009 Fixed 11.0.0 1598 12 Mar 2009 Fixed Description Worker threads are created to process the stream data from clients, and perform the database activities for each synchronization. Two sets of workers were being created, one set for pre version 10 clients, and another set for current clients (version 10 and later). Now, when the -xo switch is not specified, the MobiLink server no longer creates the threads to process the old client requests.

CR:563541

CR Number:   563541 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 2047 09 Mar 2009 Fixed Description The server could have used an incorrect selectivity estimate for a predicate containing IS [NOT] TRUE, IS [NOT] FALSE, or IS [NOT] UNKNOWN. This could have lead to ineffecient access plans. This has been fixed.

CR:563545

CR Number:   563545 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 2175 13 Mar 2009 Fixed 11.0.0 1589 13 Mar 2009 Fixed 10.0.1 3861 13 Mar 2009 Fixed Description When executing several remote queries, if the remote queries contained NChar variables in the WHERE clause, then some of the queries may have returned an incorrect result. This problem has now been fixed.

CR:563592

CR Number:   563592 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 2170 09 Mar 2009 Fixed 11.0.0 1586 09 Mar 2009 Fixed 10.0.1 3860 12 Mar 2009 Fixed 12 Mar 2009 Fixed Description When run on Windows systems, both the MobiLink server and the Relay Server Outbound Enabler (RSOE) could have held onto sockets for longer than necessary. This would have caused both to use up sockets faster than necessary, possibly exhausting system socket limits. With the RSOE, needless timeouts could also have occurred. This behaviour was particularly evident with non-persistent HTTP/HTTPS connections, and appeared to be very much OS and machine dependent. This has been fixed.

CR:563693

CR Number:   563693 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 2184 24 Mar 2009 Fixed 11.0.0 1593 24 Mar 2009 Fixed Description n some cases, it was possible for the server to report an error when processing a statement that explicitly, or implicitly, used sys.dummy. The error would have been reported as SQLCODE -300: '*** ERROR *** Assertion failed: 106105 (11.0.x.xxxx) "Unexpected expression type dfe_FieldOrigRID while compiling"' For example, the following statement could have caused this behaviour: select TE1.xidx from (select * from sys.dummy) as D, TE1 where exists ( select * from TE2 where TE2.x = TE1.xidx and TE2.xidx <= 1 ) For the incorrect behaviour to have occurred, the statement must have had a reference (explicit or implicit) to sys.dummy, where the dummy_col field was not referenced, and there must have been an exists join optimization used, where a generated distinct on rowids was needed. This has now been fixed.

CR:563736

CR Number:   563736 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 2173 13 Mar 2009 Fixed 11.0.0 1588 13 Mar 2009 Fixed 10.0.1 3860 13 Mar 2009 Fixed 9.0.2 3803 13 Mar 2009 Fixed Description If an ODBC DSN explicitly specified an isolation level, and that DSN was then used within the Interactive SQL utility (dbisql), then the isolation level specification would have been ignored. This problem has been fixed.

CR:563832

CR Number:   563832 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 2173 12 Mar 2009 Fixed 11.0.0 1588 12 Mar 2009 Fixed Description The Windows makefiles for the PerformanceFetch, PerformanceInsert, and PerformanceTransaction SQL Anywhere samples could not have been used to build the sample applications, as they referenced directories that no longer existed in the version 11.0 installation. This has now been fixed.

CR:563835

CR Number:   563835 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 2182 18 Mar 2009 Fixed 11.0.0 1592 18 Mar 2009 Fixed Description The server uses column statistics to aid with query optimization. The statistics are stored in the database catalog and are loaded into memory on demand, and unloaded when not used for a period of time. Under very rare circumstances, when running on multi processor systems, it was possible for the server to think that no statistics existed for a specific column. The problem was likely to have been self correcting over time and there were no correctness issues. However, it was possible that the absence of column statistics may have caused some queries to run inefficiently. This problem has been resolved.

CR:563839

CR Number:   563839 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2156 12 Mar 2009 Fixed Description The SQL Passthrough feature was originally written as a plugin to the MobiLink server in Java. A number of issues were found, including using extra database connections, which needed to be addressed. The feature has now been re-written as a core part of the MobiLink server, so it no longer requires a Java VM on startup. When SQL Passthrough was being used, ie. when there was at least one row in the the ml_passthrough_script table, the MobiLink server could have used twice the number of consolidated database connections than necessary, (ie. up to twice the -w value). When creating these extra connections, the MobiLink server would, during a synchronization, make another consolidated database connection, perform some work, disconnect that connection, then resume the synchronization. In other words, penalizing each synchronization with the time/cost of connecting and disconnecting to the consolidated database. Besides the performance and database connection penalties, these connects/disconnects could also have made the MobiLink server reach OS socket limits faster, potentially causing failures. Most MobiLink clients (ie. dbmlsync, dbtools sync interface, dbmlsync ActiveX integration component, and all UltraLite runtimes -- except UltraLiteJ, which doesn't support SQL Passthrough) have been updated as part of this fix. This change will cause newer clients to fail if run against an the 11.0.1 GA server. Thus MobiLink clients of version 11.0.1 2156 or later will require a MobiLink server of version 11.0.1 2156 or later.

CR:563844

CR Number:   563844 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 2182 19 Mar 2009 Fixed 11.0.0 1592 19 Mar 2009 Fixed 10.0.1 3865 19 Mar 2009 Fixed Description The MobiLink client (dbmlsync) would have occationally reported the error: Failed writing remote id file to '<filename>' Despite the error, synchronizations would have continued successfully, and the remote id file would have appeared on the disk in good order. This problem has been fixed.

CR:563848

CR Number:   563848 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2173 13 Mar 2009 Fixed 11.0.0 1588 13 Mar 2009 Fixed 10.0.1 3860 13 Mar 2009 Fixed 9.0.2 3803 13 Mar 2009 Fixed Description If an ODBC application called SQLColAttribute() on a long varchar, long nvarchar or long binary column, with an attribute value of SQL_DESC_DISPLAY_SIZE, then the ODBC driver would have incorrectly returned the value 65535. This problem has been fixed and the driver now returns the value 2147483647.

CR:564010

CR Number:   564010 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 2174 12 Mar 2009 Fixed 11.0.0 1589 12 Mar 2009 Fixed 10.0.1 3861 12 Mar 2009 Fixed 9.0.2 3804 12 Mar 2009 Fixed Description The server may have crashed if a floating point value was converted to a string, and then subsequently cast to a string with a too small size. This has been fixed.

CR:564025

CR Number:   564025 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 3868 24 Mar 2009 Fixed Description Messages generated by the MESSAGE ... TO EVENT LOG statement were not printed to the system event log when the server was started with the -qi switch. This has been fixed.

CR:564046

CR Number:   564046 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 2174 13 Mar 2009 Fixed 11.0.0 1589 13 Mar 2009 Fixed 10.0.1 3861 13 Mar 2009 Fixed Description The changes for Engineering case 559413 introduced a problem where attempting to cancel a Java call could have caused the Jave VM to stop responding. This has now been fixed.

CR:564066

CR Number:   564066 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 2174 13 Mar 2009 Fixed 11.0.0 1589 13 Mar 2009 Fixed 10.0.1 3861 13 Mar 2009 Fixed Description When an HTTP connection that had made an external environment call was closed at the exact same time that the external environment exited, there was a chance that the server would have crashed. This problem has now been fixed.

CR:564277

CR Number:   564277 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 2187 25 Mar 2009 Fixed 10.0.1 3868 25 Mar 2009 Fixed Description If a simple statement was processed and bypassed the optimizer, it was possible for the server to choose an index that was less efficient than the best one, leading to poor performance. This problem would have occurred if the WHERE clause contained equality and range predicates. This has been fixed. A workaround can be achieved using the following command line switch on the server start line or the "OPTIONS(FORCE OPTIMIZATION)" in the query text. -hW AllowBypassCosted

CR:564304

CR Number:   564304 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 3836 14 May 2009 Fixed Description The server may have crashed when simple SELECT statements are executed against the utility database. This has been fixed.

CR:564435

CR Number:   564435 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2175 16 Mar 2009 Fixed 11.0.0 1589 16 Mar 2009 Fixed 10.0.1 3861 16 Mar 2009 Fixed 9.0.2 3804 16 Mar 2009 Fixed Description In an ADO/OLE DB application, when a UNIQUEIDENTIFIER (or GUID) was used as a parameter in a query, an error message like "Cannot convert 0x to a uniqueidentifier" may have resulted, or the query may simply have failed to return any results. This problem has been fixed. Sample schema: create table uuidtable( pkey int, uuid uniqueidentifier, stringform uniqueidentifierstr ); Sample query: select * from uuidtable where uuid = ? The following .NET/OLE DB example shows typical uniqueidentifier parameter binding: OleDbCommand cmd = new OleDbCommand(txtSQLStatement.Text.Trim(), _conn); OleDbParameter param1 = new OleDbParameter(); param1.ParameterName = "@p1"; param1.DbType = System.Data.DbType.Guid; cmd.Parameters.Add(param1); cmd.Parameters[0].Value = new Guid("41dfe9f9-db91-11d2-8c43-006008d26a6f");

CR:564472

CR Number:   564472 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2176 13 Mar 2009 Fixed 11.0.0 1590 13 Mar 2009 Fixed 10.0.1 3862 13 Mar 2009 Fixed Description The Interactive SQL utility (dbisql) could have reported an internal error if, when connected to an UltraLite database, the text completer was opened in a SELECT statement and the caret was immediately after a period. This has been fixed.

CR:564475

CR Number:   564475 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Mar 2009 Fixed Description When in the new Watch dialog, when selecting 'user' or 'sync' as a property to set a condition for, if 'Add' was pressed, nothing would have happened. This has been fixed.

CR:564479

CR Number:   564479 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 2197 02 Apr 2009 Fixed 11.0.0 1599 02 Apr 2009 Fixed Description When run on BlackBerry devices, the download of a large download_delete_cursor of a table with many columns, UltraLiteJ could have reported an out of memory error when the BlackBerry ran out of object handles. This would have occurred even when many of the deletes were to be ignored by the client. The handles used by a download are a factor of the number of rows times the number of columns in each row. This has been fixed. UltraLiteJ normally applies the download after all rows have been received, however, now it immediately rejects deletes for non-existant client rows, and reduces significantly the handles used by all other download deletes. In an ideal situation, the download_delete_cursor script would reduce the number of rows sent by not sending any download deletes if the last download timestamp was the newer value, or if the row corresponding to the delete was never on the client (creation date greater than last download timestamp).

CR:564639

CR Number:   564639 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2222 18 Mar 2009 Fixed 11.0.0 1613 19 Mar 2009 Fixed 9.0.2 3833 19 Mar 2009 Fixed Description When MobiLink servers with QAnywhere messaging were set up in a server farm, push notifications could have stopped working in some circumstances. In particular, if the MobiLink server(s) handling synchronization requests from QAnywhere clients were different from the server that initiated the push notification (as would have been the case if the notifications were the result of outbound JMS messages in a server running a JMS connector), only the first push notification would have been sent, and no further notifications would have been sent. This has now been fixed. It should be noted that, in a MobiLink server farm deployment, there could be a latency of at most the automatic rules evaluation period to send a push notification to a client as a result of an outbound message to that client. This is due to scalabilty factors in a situation where there is a high volume of outbound messages being processed by the MobiLink server.

CR:564677

CR Number:   564677 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 2180 16 Mar 2009 Fixed 11.0.0 1591 16 Mar 2009 Fixed 10.0.1 3863 16 Mar 2009 Fixed 9.0.2 3806 16 Mar 2009 Fixed Description A failed COMMENT ON PROCEDURE statement could have prevented the procedure from being dropped. This has been fixed. Note, a workaround is to stop and restart the database before attempting to drop the procedure.

CR:564679

CR Number:   564679 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 2181 17 Mar 2009 Fixed Description An INPUT ststement, with multiple references to the same host variable, could have been handled incorrectly when the leftmost reference was the host variable by itself in the VALUES list, and another reference occurred in an expression that was more complicated than just the host variable by itself. For example, INPUT INTO tab( pk, col1 ) VALUES( :hv, 100 - :hv ) This has been fixed so that the final substitution for non-leftmost host-variable references is delayed so that the type of the first reference can be established.

CR:564701

CR Number:   564701 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 2151 17 Mar 2009 Fixed Description Executing a CREATE TABLE IF NOT EXISTS ... statement would have failed if the table existed, but had not yet been used since the database was started. This has been fixed.

CR:564828

CR Number:   564828 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 2052 17 Mar 2009 Fixed 11.0.0 1591 17 Mar 2009 Fixed 10.0.1 3863 17 Mar 2009 Fixed Description Following a cursor OPEN for a simple select statement that bypasses optimization, the SQLCOUNT value could have been incorrectly set to 0, when the number of rows was to be exact (ie. Row_counts was 'on'), and the number of rows was estimated to be 0 . This has been fixed so that the correct setting is now -1 in these cases.

CR:564829

CR Number:   564829 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 2182 18 Mar 2009 Fixed 11.0.0 1592 18 Mar 2009 Fixed 10.0.1 3864 18 Mar 2009 Fixed Description When the MobiLink server was listening for HTTP and/or HTTPS requests, and a load balancer or any other utility (eg. the RSOE) performed a simple TCP/IP connect, then an immediate close without sending any bytes, the MobiLink server would have taken four minutes to time out the socket. If too many such connections happened in a short time, the MobiLink server could have run out of sockets earlier than necessary. This has been fixed.

CR:564857

CR Number:   564857 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3893 13 May 2009 Fixed 11.0.0 1616 13 May 2009 Fixed 11.0.1 2240 13 May 2009 Fixed Description In very rare circumstances, SQL Anywhere .NET provider could have crashed the work process in IIS. This problem has been fixed

CR:564866

CR Number:   564866 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2181 17 Mar 2009 Fixed Description An INPUT ststement, with multiple references to the same host variable, could have been handled incorrectly when the leftmost reference was the host variable by itself in the VALUES list, and another reference occurred in an expression that was more complicated than just the host variable by itself. For example, INPUT INTO tab( pk, col1 ) VALUES( :hv, 100 - :hv ) This has been fixed so that the final substitution for non-leftmost host-variable references is delayed so that the type of the first reference can be established.

CR:565050

CR Number:   565050 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 2182 18 Mar 2009 Fixed 11.0.0 1592 18 Mar 2009 Fixed Description The Import wizard could have crashed if the "Next" button, on the page which asks for a destination table name, was clicked before the page has initialized. This has been fixed.

CR:565054

CR Number:   565054 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2182 19 Mar 2009 Fixed 10.0.1 3865 19 Mar 2009 Fixed Description Calling the ODBC functiom SQLColAttribute( ..., SQL_DESC_BASE_COLUMN_NAME, ... ) could have incorrectly returned the correlation name, instead of the base column name. This has been fixed so that the base column name is returned. If there is no base column, the column alias is returned. Note, this fix requires both an updated ODBC driver and server.

CR:565061

CR Number:   565061 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2182 18 Mar 2009 Fixed Description Dbisqlc would have reported an error, and then crashed, if there was a version mismatch with the language DLL (e.g., dblgen11.dll). This problem has been fixed.

CR:565097

CR Number:   565097 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 2183 19 Mar 2009 Fixed Description The metadata returned for a query with a UNION operator, could have been incorrect. This has now been corrected

CR:565102

CR Number:   565102 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 2182 19 Mar 2009 Fixed Description If an application executed a PHP external environment procedure, and the PHP procedure subsequently called exit, then the server would have taken up to 5 seconds to return control to the application, and would then have displayed a dropped connection message in the console. This problem has now been fixed.

CR:565104

CR Number:   565104 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2182 19 Mar 2009 Fixed 11.0.0 1592 19 Mar 2009 Fixed Description The php process may have crashed after completing a php external environment call. This has been fixed.

CR:565110

CR Number:   565110 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 2183 19 Mar 2009 Fixed 11.0.0 1592 19 Mar 2009 Fixed 10.0.1 3866 19 Mar 2009 Fixed 9.0.2 3807 19 Mar 2009 Fixed Description When binding a column in ODBC, the column type, a buffer and a length are specified. For static types (int, long, double, time, etc) the ODBC driver ignores the length specified because the length is constant. The ODBC driver should have been treating SQL_GUID columns as static as well, but was incorrectly respecting the length specified, which sometimes resulted in truncated values. This has been fixed.

CR:565232

CR Number:   565232 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 2218 22 Apr 2009 Fixed 11.0.0 1609 28 Apr 2009 Fixed 10.0.1 3884 28 Apr 2009 Fixed Description In very rare circumstances, if a complex view which cannot be unflattened (e.g., a grouped view) was used multiple times in the same statement, the optimizer may have generated an access plan which computes an incorrect result set. One of the conditions for this to have occurred was for a predicate of the form " V.X theta [ANY|ALL] ( select aggregate(e) from V as V1 where ... )" to be present in one of the query blocks of the statement. This has been fixed.

CR:565244

CR Number:   565244 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 2183 20 Mar 2009 Fixed 10.0.1 3866 20 Mar 2009 Fixed Description The SQL Anywhere HTTP server will generate error responses that may be classified into two categories: System and User error messages. System error messages are generated for the following conditions: protocol errors, time-out and cancel. User error messages are generally caused by a SQL error. It is recommended that the application handle SQL errors within an EXCEPTION clause and render application specific error responses. By default a User error message is output in the body of the response as HTML or plain-text when the SERVICE is configured as TYPE 'HTML' or 'RAW' respectively. User error messages may have been returned using chunk-mode transfer encoding, while keeping the connection alive. In the event that the web service encountered an error when outputting its response, or was explicitly canceled by dropping its database connection, the response message was prematurely truncated. A change has been made to make the default behaviour more consistent, SQL errors explicitly handled by the application are not affected by these changes. By default System and User error messages: - do not use chunk mode transfer encoding - explicitly set 'Connection: close' response header - shutdown the HTTP connection once the error message is sent Any pending (pipelined) requests following the request encountering the error are terminated. Also, an error response is guaranteed to close the HTTP connection. Interrupting a response (already underway such that the response headers have already been sent) will truncate the output and close the HTTP connection. User error messages that are explicitly caught by the EXCEPTION clause may also CALL SA_SET_HTTP_HEADER('Connection', 'close') prior to issuing the error page to force the HTTP connection to close after the response has been sent.

CR:565255

CR Number:   565255 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2183 19 Mar 2009 Fixed Description A multi-threaded embedded SQL application could have crashed if db_fini was called with the last active SQLCA at the same time as db_init was called with another SQLCA. The crash was very timing dependent. A race condition has been corrected.

CR:565257

CR Number:   565257 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 2183 19 Mar 2009 Fixed Description In rare situations, access to a mirrored database could be blocked, making the mirroring servers appear to hang. This has been fixed.

CR:565283

CR Number:   565283 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 2187 25 Mar 2009 Fixed 11.0.0 1595 25 Mar 2009 Fixed 10.0.1 3868 25 Mar 2009 Fixed Description When evaluating predicates outside of DML statements (for example, in SET or IF statements in procedures, triggers, events, or batches), the server could have improperly treated UNKNOWN as FALSE. For example, the following statement should set @str2 to NULL, but it was incorrectly being set to FALSE: SET @str2 = if NULL like 'a' then 'TRUE' else 'FALSE' endif; This has been fixed.

CR:565286

CR Number:   565286 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 2186 24 Mar 2009 Fixed 10.0.1 3866 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed Description The server could have released locks on rows prematurely. Data corruption, crashes, unexplained deadlocks and incorrect query results were all possible. For this to have occurred though, there must have been a significant amount of contention for a particular row. This has now been corrected.

CR:565441

CR Number:   565441 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2181 20 Mar 2009 Fixed Description Changes have been made to the MobiLink client to accomodate the changes made to the MobiLink server for Engineering case 563839. Therefore, running the 11.0.1 GA MobiLink server with SQL passthrough enabled (i.e. rows have been added to the ml_passthrough_script table), with 11.0.1 MobiLink clients (dbmlsync) from an EBF will cause synchronizations to fail with the message: This client is newer than your MobiLink server. You must upgrade your MobiLink server before you can synchronize. In order to resolve this problem, the MobiLink server must be upgraded as well. As a temporary work around, SQL Passthrough can be disabled by deleting all the rows in the ml_passthrough_script table and restarting the Mobilink server.

CR:565447

CR Number:   565447 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 2203 08 Apr 2009 Fixed 11.0.0 1602 08 Apr 2009 Fixed Description Index corruption was possible if an index contained many (more than 64,000) consecutive entries that differed by the same constant amount. A check to ensure that the count value does not overflow when merging pages was missed. This has been corrected.

CR:565474

CR Number:   565474 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 2184 24 Mar 2009 Fixed 10.0.1 3867 24 Mar 2009 Fixed Description An HTTP client procedure may have hung when receiving chunk mode encoded data. For this problem to have occurred, the client needed to identify itself as an HTTP/1.1 version client (by default it identifies itself as HTTP/1.0). This may be done in the following ways: SET 'HTTP(VER=1.1)' TYPE 'HTTP:POST' and length of the values for input parameter equal or exceed 8192 bytes TYPE 'HTTP:POST' SET 'HTTP(CH=ON)' This has been fixed.

CR:565624

CR Number:   565624 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1596 30 Mar 2009 Fixed 10.0.1 3872 30 Mar 2009 Fixed Description Under certain non-deterministic conditions, a server-side backup could have blocked other tasks, such as remote procedure calls, HTTP requests, and external environments from running. As well, in certain very rare and timing sensitive conditions, it is also possible that a backup could have hung indefinitely while starting. Both of these problems have now been fixed.

CR:565651

CR Number:   565651 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2190 30 Mar 2009 Fixed 11.0.0 1596 30 Mar 2009 Fixed 10.0.1 3872 30 Mar 2009 Fixed Description If an application executed a query like "select ... for t where c = v', where c was a char or varchar column, v was as variable of type nchar or nvarchar, and t was a proxy table to a remote table in Microsoft SQL Server, then the query would have failed with SQL Server reporting the error "The data types varchar and ntext are incompatible in the equal to operator." This problem has now been corrected.

CR:565663

CR Number:   565663 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 2186 24 Mar 2009 Fixed 11.0.0 1593 24 Mar 2009 Fixed Description The German (DE), French (FR), and Chinese (ZH) language help files were missing for Sybase Central 6.0.0. This has now been corrected.

CR:565664

CR Number:   565664 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 2186 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed Description When run on machines with only one network adapter, checking the box "Only show local servers" in the "Find Servers" dialog would not have displayed local servers. This has been fixed.

CR:565667

CR Number:   565667 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2184 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed Description The methods QAManagerBase.SetMessageListener and QAManagerBase.SetExceptionListener would have throw a QAException with error code COMMON_NOT_OPEN_ERROR, when called before an Open() call. This has been fixed. Now, SetMessageListener and SetExceptionListener can be called any time after the creation of a QAManagerBase object, as in earlier versions of QAnywhere.

CR:565678

CR Number:   565678 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 2187 25 Mar 2009 Fixed 11.0.0 1594 25 Mar 2009 Fixed Description When the server was started with the -fips command line option ('All strong encyption done using FIPS approved modules'), attempting to create an unencrypted database would have failed with the error "The simple algorithm is not available in FIPS mode". This has been fixed

CR:565835

CR Number:   565835 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 2187 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed 10.0.1 3868 24 Mar 2009 Fixed 9.0.2 3809 24 Mar 2009 Fixed Description The server may have crashed if the procedure debugger's connection, and the debugged connection, stopped at the same time. This has been fixed.

CR:565837

CR Number:   565837 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 2189 27 Mar 2009 Fixed 11.0.0 1595 27 Mar 2009 Fixed 10.0.1 3871 27 Mar 2009 Fixed Description When using the INPUT statement with dbisqlc, column inputs may have failed if the length of the input record exceeded the capacity of the input buffer. This failure could have been signalled by a conversion error, or it could have gone undetected (the remaining columns having been truncated or set to the null value. This problem has now been fixed.

CR:565839

CR Number:   565839 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 2187 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed Description If an application used one of the connection scoped external environments (i.e. PHP, PERL or one of the external C environments) and the SA server was running on a non-Windows platform, then there was a chance the external environment process would not have gone away once the application disconnected. This problem was introduced by the changes made for Engineering case 559372, and has now been fixed.

CR:565844

CR Number:   565844 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 2222 08 Mar 2010 Fixed Description When using MobiLink servers in a server farm (by specifying the -ss command line option), servers could have crashed and/or unexpectedly caused failed synchronizations. The problem was more noticeable in environments with poor network quality or where retries after synchronization failures occurred very quickly after the original synchronization. This has been fixed.

CR:565874

CR Number:   565874 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2187 24 Mar 2009 Fixed 11.0.0 1594 24 Mar 2009 Fixed Description If an alias or correlation name was entered in the Query Editor, and then the "OK" button was clicked while the editor for the alias or correlation name was still open, the editor's value could have been ignored. This has been fixed. Note, a workaround is to press ENTER after typing in the alias/correlation name, and then click the "OK" button.

CR:565880

CR Number:   565880 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 2187 25 Mar 2009 Fixed 11.0.0 1594 25 Mar 2009 Fixed Description If an application used either the C_ODBC32 or C_ODBC64 external environments, then the server may have reported a connection dropped error when the application disconnected. This problem has now been fixed.

CR:565891

CR Number:   565891 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   6.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2187 25 Mar 2009 Fixed 11.0.0 1594 25 Mar 2009 Fixed Description When run on Unix systems, the server would have crashed or hang if a client application attempted to connect and disconnect in a tight loop. Another symptom may have been that the client would have received the following error: -832 Connection Error: Found server but communication error occurred. For this to have occurred, the connection must have been via shared memory, the application must have previously connected and disconnected successfully so as to unload the client libraries (ODBC, DBLIB, or DBCAPI), and the time between the last disconnect and the new connect was within 10ms. This has been fixed.

CR:566033

CR Number:   566033 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 2188 26 Mar 2009 Fixed Description When running the SQL Anywhere Deployment wizard, the MSM installer type option actually created an MSI installer type. This has been fixed.

CR:566043

CR Number:   566043 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2194 31 Mar 2009 Fixed 11.0.0 1597 31 Mar 2009 Fixed 10.0.1 3873 31 Mar 2009 Fixed 9.0.2 3812 31 Mar 2009 Fixed Description When working with .NET data sources and the OLEDB adapter using Visual Studio, the Configure Dataset with Wizard dialog may have resulted in "Dynamic SQL generation is not supported against a SelectCommand that does not return any base table information." or theTableAdapter Query Configuration Wizard dialog may have resulted in "Failed to get schema for this query". The SQL Anywhere OLE DB provider has been corrected.

CR:566046

CR Number:   566046 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 2188 26 Mar 2009 Fixed 11.0.0 1595 26 Mar 2009 Fixed 10.0.1 3869 26 Mar 2009 Fixed Description If the maximum value in an autoincrement column after performing a LOAD TABLE statement was a negative value, the SYSTABCOL.max_identity value for that column would have been set to a negative value. This would have caused subsequent inserts into the table, which did not provide a value for the autoincrement column, to generate errors. This situation could have arisen when rebuilding a database having a table with an autoincrement column and only negative values in the column. Note that the use of negative values with autoincrement columns is discouraged. This has been fixed so that the max_identity value in this situation will now be set to zero after the LOAD TABLE statement completes.

CR:566058

CR Number:   566058 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 2052 25 Mar 2009 Fixed Description Under very rare circumstances, a query plan using a hash join in an EXISTS subquery could have caused the server to crash. This has been fixed.

CR:566071

CR Number:   566071 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 2187 26 Mar 2009 Fixed 11.0.0 1594 26 Mar 2009 Fixed Description If an application used either the C_ODBC32 or C_ODBC64 external environments, then returning result sets from the external environment could have taken a long time, and resulted in thread deadlock errors due to the fact that the C_ODBC external environments were not turning autocommit off. This problem has now been fixed.

CR:566165

CR Number:   566165 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 2189 27 Mar 2009 Fixed 11.0.0 1595 27 Mar 2009 Fixed 10.0.1 3869 27 Mar 2009 Fixed Description In very rare circumstances, the server could have crashed if the procedure debugger run a 'step into' or 'step over' request at the end of a procedure or trigger. This has been fixed.

CR:566207

CR Number:   566207 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2189 26 Mar 2009 Fixed Description The QAnywhere plug-in for Sybase Central now supports the connection retry command line options for the Agent (see Engineering case 561067).

CR:566372

CR Number:   566372 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 2195 01 Apr 2009 Fixed 11.0.0 1598 01 Apr 2009 Fixed 10.0.1 3873 01 Apr 2009 Fixed Description Data inserted into a compressed column may have caused a decompression error when retrieved. This would only have occurred if the data was already compressed so that compression would result in increased data length, the column was created with the NO INDEX clause, and the data length was very close to a multiple of 8 times the database page size. An error in calculating the maximum possible length for the compressed data has been fixed.

CR:566450

CR Number:   566450 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 2190 31 Mar 2009 Fixed 11.0.0 1596 31 Mar 2009 Fixed Description When executing queries involving index scans, the boundary values for the scans could, in some cases, have been evaluated incorrectly causing the queries to fail to return any results. This has been fixed

CR:566651

CR Number:   566651 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 2195 01 Apr 2009 Fixed 10.0.1 3873 01 Apr 2009 Fixed Description A SERVICE may invoke a procedure that explicitly sets the 'Connection' and 'Content-Length' HTTP response headers using the SA_SET_HTTP_HEADER system procedure. The setting of the 'Content-Length' was ignored, and the setting of 'Connection:close' implicitly disabled chunked-mode transfer encoding. Changes have been made to provide greater control over SQLAnywhere HTTP server responses. The following is a summary of the new behaviour: Client is HTTP/1.0: The server does not support Keep-Alive and Chunk-mode operation for this HTTP version. By default the server never sets the 'Transfer-Encoding' header and always sets 'Connection: close' header, shutting down the connection once the response has been sent. A SERVICE procedure may set the 'Content-Length' header but setting the 'Connection' header is ignored. Client is HTTP/1.1: By default the server responses use chunked-mode transfer encoding and automatically set the 'Transfer-Encoding: chunked' header. If the SERVICE procedure explicitly sets a 'Content-Length' header to some value, then the 'Content-Length' header is sent in place of the 'Transfer-Encoding' header and the response body is not chunk-mode encoded. Note: It is an error for a SERVICE procedure to set both a 'Content-Length' and 'Transfer-Encoding' header. The server will assume 'Connection: keep-alive' if the client does not send a 'Connection' request header. If a client explicitly sends a 'Connection: close' request header and/or the SERVER procedure explicitly sets 'Connection: close' the server will shutdown the connection once the response has been sent. Setting Content-Length In most cases data will need to be buffered in order to calculate the Content-Length. Therefore, it is recommended to use chunk-mode transfer encoding whenever possible. If 'Content-Length' must be set, then care must be taken to ensure that the result-set is not character set translated when the response is composed. It is recommended that the 'CharsetConversion' http option is set to off when returning textual data. Also, setting 'Content-Length' should only be done within a TYPE 'RAW' SERVICE since some services (i.e. 'HTML', 'JSON') add content to the response. A check has been added to ensure that the actual length of the response matches the value of 'Content-Length' header. If the values do not match then the server will shutdown the connection, once the response has been sent, regardless of whether or not a 'Connection: keep-alive' response header has been sent.

CR:566673

CR Number:   566673 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 2194 31 Mar 2009 Fixed 11.0.0 1597 31 Mar 2009 Fixed Description Exporting data from a SQL Anywhere database to a MySQL table could have failed if the Interactive SQL utility (dbisql) was asked to create a table for the data, and the data contained any of the following SQL Anywhere types: TINYINT, UNSIGNED SMALLINT, UNSIGNED INT, UNSIGNED BIGINT, or TIMESTAMP. The mapping of data types between SA and MySQL was incorrect, this has been fixed.

CR:566685

CR Number:   566685 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 2195 31 Mar 2009 Fixed 10.0.1 3873 31 Mar 2009 Fixed Description If a simple statement was processed by the server and bypassed the query optimizer, it was possible for the server to choose an inefficient plan if the statement contained a specific form of contradiction. For example, the following statement could have generated a plan that would have read all rows from TRange: select * from TRange where x1 = 3 and x2 between 2 and 1 A more efficient plan would recognize that the BETWEEN predicate is never true (2 > 1), and uses a prefilter to avoid fetching any rows from TRange. This has been fixed so that the more efficient plan is selected.

CR:566688

CR Number:   566688 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 2194 31 Mar 2009 Fixed 11.0.0 1597 09 Sep 2009 Fixed Description Prebuilt binary libraries for PHP 5.2.9 have now been added.

CR:566689

CR Number:   566689 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 2194 31 Mar 2009 Fixed 11.0.0 1598 31 Mar 2009 Fixed Description Importing a table into an UltraLite database may have failed if it contained NCHAR or NVARCHAR columns. This has been fixed so that the importer converts NCHAR and NVARCHAR columns into VARCHAR columns. The operation may still fail if the UltraLite database cannot represent the characters being imported, so this is guaranteed to work only if the UltraLite database is created with a UTF8BIN collation sequence.

CR:566693

CR Number:   566693 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 2196 01 Apr 2009 Fixed 10.0.1 3874 01 Apr 2009 Fixed 9.0.2 3816 01 Apr 2009 Fixed Description On certain processors other than x86 and x86_64 (64 bit HP-UX for example), the server may have crashed in extremely rare conditions when using a connection number to get connection information. Examples of getting this type of connection information include getting a connection property for another user, or calling sa_conn_info. This has now been fixed.

CR:566703

CR Number:   566703 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 2195 01 Apr 2009 Fixed 11.0.0 1598 01 Apr 2009 Fixed Description The PHP external environment was passing strings as LONG VARCHAR, which was causing character set conversion between the server and the PHP process. This would have corrupted binary data. This has been corrected so that all strings are now passed as LONG BINARY, which means that no character set conversion will be done.

CR:566705

CR Number:   566705 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) 12.0.1 3782 24 Aug 2012 Fixed 11.0.1 2860 24 Aug 2012 Fixed Description In the PHP external environment, calling phpinfo() would have showed no useful information for the sqlanywhere_extenv module. This has been fixed. Now, server version information, as well as the names of the server, database, and user are displayed.

CR:566711

CR Number:   566711 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 2194 31 Mar 2009 Fixed 11.0.0 1598 31 Mar 2009 Fixed Description The PHP external environment process would have crashed if the system procedures sa_http_php_* were called from the Interactive SQL utility, or anywhere outside of an HTTP server request. This has been fixed

CR:566805

CR Number:   566805 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 2195 31 Mar 2009 Fixed 11.0.0 1598 31 Mar 2009 Fixed 10.0.1 3873 31 Mar 2009 Fixed Description Creating a string object shorter than, but within roughly a database page size of, the 2^31-1 (2GB) upper length limit could have incorrectly resulted in the SQL error MAX_STRING_LENGTH_EXCEEDED. This has been fixed.

CR:566828

CR Number:   566828 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 2188 31 Mar 2009 Fixed Description Errors that occurred while running a SQL passthrough script in schema-diffing mode were not being marked as critical, which could have caused the database schema to become corrupted. This has been fixed.

CR:566830

CR Number:   566830 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 2195 31 Mar 2009 Fixed 11.0.0 1598 31 Mar 2009 Fixed Description It was not possible to export NUMERIC values to a new MySQL table if the precision of the source column was greater than 15. This has been fixed. Note that exporting data into an existing table did not have this problem.

CR:566957

CR Number:   566957 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 2196 01 Apr 2009 Fixed 11.0.0 1599 01 Apr 2009 Fixed Description The server may have crashed when executing a DML statement that modified tables in an additional dbspace while a lazy checkpoint was in progress. This problem was introduced by the changes for Engineering case 547392, and has now been fixed.