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

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

CR:570140

CR Number:   570140 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 2227 28 Apr 2009 Fixed 11.0.0 1610 28 Apr 2009 Fixed 10.0.1 3886 28 Apr 2009 Fixed Description Attempting to insert a binary or varbinary variable, or host variable, into a Microsoft SQL Server proxy table with an image column would have failed with an 'invalid precision' error when the length of the binary value was between 8001 and 32768 bytes. This problem has now been fixed.

CR:570141

CR Number:   570141 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 2226 28 Apr 2009 Fixed 11.0.0 1610 28 Apr 2009 Fixed Description In rare cases, the mirror server in a mirroring ssystem could have crashed at shutdown. This has been fixed.

CR:570144

CR Number:   570144 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 2226 29 Apr 2009 Fixed Description The Relay server's configuration file has a 64k size limit that, if exceeded, can caused the Relay Server to fail on start up. This limit has been removed. This limit was not affecting dynamic growth of configuration.

CR:570308

CR Number:   570308 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 2223 28 Apr 2009 Fixed 10.0.1 3885 28 Apr 2009 Fixed 9.0.2 3827 28 Apr 2009 Fixed Description Attempting to return a result set from within a BEGIN ATOMIC block would caused a memory leak in the server. This has been fixed. Note that returning a result set from within an atomic block is not allowed, and an error is issued in this case. This behaviour has not changed.

CR:570369

CR Number:   570369 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2227 30 Apr 2009 Fixed Description The listener may not have substituted action variables properly in some cases. The light weight polling handler would have substituted the variables $ml_user, $ml_password and $ml_connect with undefined values, as they were thought to be irrelevant in unauthenticated light weight polling. This has been fixed. They will be substituted properly into the action string and, if they are not specified, the values will be empty. Action variables in irrelevant contexts would have been substituted with undefined values as well. This is too is fixed, by not not be substituting them at all. For example, using $poll_key in the action string of a non-light-weight-polling handler will now result in $poll_key without substitution instead of an undefined result.

CR:570468

CR Number:   570468 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 2228 29 Apr 2009 Fixed 11.0.0 1611 29 Apr 2009 Fixed 10.0.1 3887 29 Apr 2009 Fixed Description When attempting to create a proxy table, if the connection was subsequently cancelled, either explicitly or implicitly, by shutting down the database or server, then there was a small chance the server would have crashed. This problem has now been fixed.

CR:570473

CR Number:   570473 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2222 29 Apr 2009 Fixed Description On Linux systems, it was possible that the SQL Anywhere Monitor would have failed to start. When the Monitor starts up, it explicitly sets the location of the installed Java VM to ensure it always uses the Java installation shipped with the Monitor. Unfortunately, because of the case-sensitive nature of paths in Linux, it was possible that the path set was not being picked up properly. This has been corrected so that the Monitor now uses the correct case for the path on Linux.

CR:570476

CR Number:   570476 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 2228 30 Apr 2009 Fixed Description A SQLAnywhere service, processing an x-www-urlencoded (standard GET or POST) HTTP request which calls HTTP_VARIABLE() with an @BINARY attribute, will return %-encoded (URL encoded) data. This has been fixed. An @BINARY attribute will now implicitly decode the value without character set translation. A new attribute, @TRANSPORT, has been added to allow the return of data in its raw HTTP transport form. With this change, HTTP_VARIABLE may retrieve x-www-form-urlencoded values in three different forms: * No attribute - return a value that is %-decoded and character set translated to the database character set encoding. %-encoded UTF-8 decoding is supported. This should be the default usage for retrieving textual x-www-form-urlencoded data. * @BINARY should be used to retrieve x-www-form-urlencoded binary data values. The value is %-decoded with no character set translation, UTF-8 %-encoded data is not supported in this mode since %-encoded data are simply decoded into their equivalent byte representation. * @TRANSPORT will return the raw HTTP transport form of the value, where %-encodings are preserved. This change does not impact the usage of @BINARY for multi-part/form-data form based uploads. The use of @TRANSPORT in this case is identical to @BINARY. Prior to this change, the work-around was to HTTP_DECODE the value returned by the HTTP_VARIABLE function when it was called with an @BINARY attribute.

CR:570493

CR Number:   570493 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 2228 30 Apr 2009 Fixed Description In very rare cases, if an event fired while a database was being shutdown, the server could have crashed. This has been fixed.

CR:570503

CR Number:   570503 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 2228 30 Apr 2009 Fixed 11.0.0 1611 30 Apr 2009 Fixed 10.0.1 3887 30 Apr 2009 Fixed Description When using secure streams and an invalid TLS handshake occured, the MobiLink server could have waited for a full network timeout period before disconnecting. This has been fixed. The MobiLink server will now immediately terminate the network connection with a "handshake error" error message.

CR:570650

CR Number:   570650 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 2250 07 May 2009 Fixed Description Using the TRANSACTION LOG TRUNCATE clause on the BACKUP DATABASE statement could have lead to the error "Assertion failed: 100910 Error renaming transaction log file before deleting it." This would have occurred when the user under which the server was running did not have delete permissions on the directory where the transaction log was located. Now, the server no longer deletes and re-creates the transaction log file, instead it truncates the file to one page. This should also prevent any interaction with virus scanners and disk defragmenters, which was often the case when files were being created.

CR:570652

CR Number:   570652 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 2229 01 May 2009 Fixed 11.0.0 1611 01 May 2009 Fixed 10.0.1 3887 01 May 2009 Fixed Description If a version 10.x or later database had a torn (ie "partial") write in the checkpoint log, the server could have reported assertion failures, including 201866 (only on 10.x servers), 201869 (only on 11.x servers), 200502, 200505, or 200512. In the case of a single torn write, these failures should not have been reported, and the database should be recoverable once the server is upgraded to include this fix. If upgrading the server does not resolve the assertion failures, the database is likely corrupt and does not just have a torn write.

CR:570656

CR Number:   570656 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 2229 01 May 2009 Fixed 11.0.0 1611 01 May 2009 Fixed 10.0.1 3888 01 May 2009 Fixed Description If a MobiLink synchronization script included the two characters "ui" inside an {ml ...} structure for named parameters, and the "ui" characters were not part of a named parameter, then MobiLink would have incorrectly replaced the "ui" with a question mark when it sent the command to the consolidated database. For example, the following script would have had no problem, since the "ui" in this case was part of the named parameter "build": INSERT INTO t1(pk,build) VALUES ( {ml r.pk}, {ml r.build}) However, the following script would have failed, because the "ui" in the column list for the insert would have been replaced: {ml INSERT INTO t1(pk,build) VALUES ( r.pk, r.build )} This has now been fixed.

CR:570690

CR Number:   570690 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 2235 30 Apr 2009 Fixed 11.0.0 1614 30 Apr 2009 Fixed Description The "Longest Active Synchronization Time" and the "Longest Active Wait for a Database Worker Thread" metrics were incorrect in the SQL Anywhere Monitor, and the monitoring values printed by the -ppv options LONGEST_SYNC and LONGEST_DB_WAIT, would have been incorrect. These metrics in the Monitor had the incorrect sign, but the absolute values were correct; essentially the graph was drawn upside down. A side effect of this is that the alert on these metrics would never be raised. These issues have been fixed.

CR:570738

CR Number:   570738 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 3892 13 May 2009 Fixed 11.0.1 2237 13 May 2009 Fixed 11.0.0 1617 25 May 2009 Fixed Description In very rare, timing dependent cases, a server backup could have hung while starting up. This has been fixed.

CR:570799

CR Number:   570799 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 2230 05 May 2009 Fixed Description When exporting to an UltraLite database using the Export wizard, the corresponding OUTPUT statements added to the command history would have been incomplete if no password was given for the UltraLite database. This has been fixed.

CR:570884

CR Number:   570884 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) 04 May 2009 Fixed Description The FIPS module is now supported by the SQL Anywhere server and clients on 64-bit Windows, and 32-bit and 64-bit Linux.

CR:570896

CR Number:   570896 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 2233 05 May 2009 Fixed Description In rare circumstances the server may have crashed when a new HTTP connection was created. This has been fixed.

CR:570903

CR Number:   570903 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2233 05 May 2009 Fixed 10.0.1 3890 05 May 2009 Fixed Description In very rare circumstances it was possible for the SQL Anywhere JDBC driver to have caused a crash in the Java VM. The Hotspot log generated for the crash would most likely have indicated that the crash occurred while attempting to construct a class cast exception. This has been fixed.

CR:570915

CR Number:   570915 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3894 19 May 2009 Fixed 9.0.2 3836 20 May 2009 Fixed Description When the iAS ODBC driver for Oracle was used by the MobiLink server to upload multiple CHAR type columns to a consolidated database running on an Oracle 9.2.0.8 server, it could have failed with the error; "ORA-01461: can bind a LONG value only for insert into a LONG column" This problem has now been fixed.

CR:570923

CR Number:   570923 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 2233 05 May 2009 Fixed 10.0.1 3890 05 May 2009 Fixed Description If a database error occurred when trying to install or update the MobiLink System Setup, the error message would have included the SQL statement that was being executed, which could have lead to the message box being too large for the screen. This has been fixed. Now the SQL statement is only shown when the Details are shown.

CR:570928

CR Number:   570928 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3833 07 May 2009 Fixed Description If a statement was executed with a hash group by operator, and there was an aggregate function AGG( DISTINCT x ) for a blob value x, it was possible in some situations for the server to have crashed. This has been fixed.

CR:570940

CR Number:   570940 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2222 08 May 2009 Fixed Description On Japanese Linux systemss, the Service utility (dbsvc) would not have output any messages. This has been fixed.

CR:571029

CR Number:   571029 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3890 13 May 2009 Fixed 11.0.0 1613 13 May 2009 Fixed 11.0.1 2234 13 May 2009 Fixed Description If an application attempted to execute a batch with a long binary or long varchar column, and the values within the long columns were large, and the batch size was also reasonably large, then the iAnywhere JDBC driver may have given an 'out of memory' dialog, even though the Java VM still had lots of memory available. This problem has now been fixed.

CR:571215

CR Number:   571215 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 3897 26 May 2009 Fixed Description If two grouped queries appeared in different outer joins with an unquantified expression in the group-by list, it was possible for NULL to be substituted for the unquantified expression value elsewhere in the query. For example, the following query could have returned NULL incorrectly for columns A1, A2: select today(*) A1, D2.A2, D3.A3 from dummy D1 left join ( select today(*) A2 from sys.dummy group by A2 ) D2 on 1=1 left join ( select today(*) A3 from sys.dummy group by A3 ) D3 on 1=0 This fault could have lead to the following (non-fatal) assertion failure: Run time SQL error -- *** ERROR *** Assertion failed: 102501 (10.0.1.####) Work table: NULL value inserted into not-NULL column SQLCODE=-300, ODBC 3 State="HY000" This has been fixed.

CR:571233

CR Number:   571233 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows 2000 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 2241 13 May 2009 Fixed Description When the -pi option 'ping MobiLink server' was used on the MobiLink client (dbmlsync) command line, dbmlsync would have returne an exit code of 0 (indicating success), even if it was unable to contact the Mobilink server. This has been fixed, and a non-zero exit code will now be returned in this case.

CR:571242

CR Number:   571242 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 3833 06 May 2009 Fixed Description If a non-existent stored procedure was called with argument names in the CALL statement, the server would have returned the misleading error message: "Parameter '' not found in procedure '???'". This has been fixed so that a prcedure not found error is returned.

CR:571252

CR Number:   571252 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 2235 06 May 2009 Fixed 11.0.0 1614 06 May 2009 Fixed Description The INPUT USING, or Import Wizard, was not able to import REAL values from a SQL Anywhere database to an UltraLite database. This has been fixed.

CR:571253

CR Number:   571253 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2235 07 May 2009 Fixed Description When installing only the MobiLink components on Linux systems using the 1.0.1 GA install, the dbfhide utility was not installed. This utility should be installed, as it is used for both MobiLink and Relay Server setup. This has been corrected.

CR:571267

CR Number:   571267 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2235 07 May 2009 Fixed Description In the SQL Anywhere Monitor, the 'Total CPU Time' displayed for MobiLink resources would have been unreasonably large. This was due to the values being scaled as milliseconds, rather than as seconds. This has been fixed and the values are now correctly displayed in seconds.

CR:571282

CR Number:   571282 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 2235 07 May 2009 Fixed 10.0.1 3891 07 May 2009 Fixed Description When creating a synchronization model, if a custom download subset was choosen, without specifying one or more tables to join, then the download_cursor events would not have been generated. Instead errors like the following would have appeared as comments in the Events editor: /* * ERROR: Unexpected error encountered while generating event. * Error for: RHS of #set statement is null. Context will not be modified. table-scripts\download_cursor.vm * [line 59, column 8] */ This problem only happened in the New Synchronization Model wizard, not when custom download subset was enabled in the Mappings editor. The problem has been fixed for new synchronization models. To work around the problem, in the Mappings editor change the Download Subset (Dnld. Sub.) to None and then back to Custom, then switch back to the Events editor.

CR:571284

CR Number:   571284 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 2250 25 May 2009 Fixed 11.0.0 1621 25 May 2009 Fixed 10.0.1 3895 25 May 2009 Fixed Description The server may have crashed following execution of an ALTER TABLE statement that added or modified columns with a DEFAULT or COMPUTE clause, if all materialized views had been dropped since the last server start. This has been fixed. Workaround Description  No workaround.

CR:571436

CR Number:   571436 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 2220 08 May 2009 Fixed 11.0.0 1609 08 May 2009 Fixed 10.0.1 3884 08 May 2009 Fixed Description A statement that used subsumed ORDER BY clauses in aggregate functions would have failed with a syntax error. This type of statement was executed without an error in version 9.0.2, and has now been fixed. For example: select list(e1 ORDER BY e2, e3 ), list( e4 ORDER BY e2,e3,e5) from .... The first ORDER BY clause 'e2, e3' is subsumed by the second ORDER BY clause 'e2,e3,e5'.

CR:571460

CR Number:   571460 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2222 08 May 2009 Fixed Description On Linux systems, the Service utility (dbsvc) would not have honored the -pr (nicelevel) and -a (user) command line options. This has been fixed.

CR:571465

CR Number:   571465 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2236 08 May 2009 Fixed 11.0.0 1614 08 May 2009 Fixed 10.0.1 3891 08 May 2009 Fixed Description If a network error occurred in the MobiLink Monitor, the SQL Anywhere Monitor, QAnywhere, or the Notifier, there could have been garbage characters trailing the error string. For example: "The server monitor was unable to contact the MobiLink server. The host 'mlstress02' is still available. Error: Timed out trying to read 128 bytes.rWms " This has been fixed.

CR:571611

CR Number:   571611 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 3892 08 May 2009 Fixed Description On Linux systems, the server could have used larger amounts of memory than intended under some circumstances. Affected functionality included external function calls, the Java external environment, outbound HTTP connections, and remote data access. This has been fixed.

CR:571620

CR Number:   571620 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 2236 08 May 2009 Fixed 11.0.0 1621 25 May 2009 Fixed Description OEMs now have the ability to prevent users from saving connection passwords with favorites. To do this, add the (new) "allowPasswordsInFavorites" directive to the "dbisql" section of the OEM.INI file: [dbisql] allowPasswordsInFavorites=false Allowable values for this directive are "true" and "false". The default is "true". If this directive is added to OEM.INI, and its value is "false", the visible change is in the "Add to Favorites" window: the checkbox called "Save the connection password" will not be visible, and will be assumed to be unselected.

CR:571624

CR Number:   571624 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) 10.0.1 3892 13 May 2009 Fixed 11.0.0 1615 13 May 2009 Fixed 11.0.1 2237 13 May 2009 Fixed Description If an application executed a query that generated a warning, and that warning was attached to a Statement, PreparedStatement, CallableStatement or ResultSet object, and the object was subsequently closed without calling clearWarnings() first, then the JDBC driver would have leaked memory. This problem has now been fixed.

CR:571625

CR Number:   571625 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) 10.0.1 3892 13 May 2009 Fixed 11.0.0 1615 13 May 2009 Fixed 11.0.1 2237 13 May 2009 Fixed Description If an application called DatabaseMetaData.getCatalogs(), DatabaseMetaData.getSchemas() or DatabaseMetaData.getTableTypes(), then the JDBC driver would have leaked a very small amount of memory. This problem has now been fixed.

CR:571628

CR Number:   571628 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) 10.0.1 3892 13 May 2009 Fixed 11.0.0 1615 13 May 2009 Fixed 11.0.1 2237 13 May 2009 Fixed Description If an application called a stored procedure which in turn called a proxy procedure, and the local stored procedure generated a warning prior to calling the proxy procedure, then the server may have returned the error: "remote server not capable". This problem has now been fixed.

CR:571643

CR Number:   571643 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1615 13 May 2009 Fixed 11.0.1 2237 13 May 2009 Fixed Description When editing a table's schema with the table editor, typing a Ctrl or Alt key combination could have initiated editing of the focused cell and either selected a menu item or opened a menu. This has been corrected so that typing a Ctrl or Alt key combination now performs the latter operation,and does not initiate editing.

CR:571671

CR Number:   571671 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1615 13 May 2009 Fixed 11.0.1 2237 13 May 2009 Fixed Description When editing a synchronization model's mappings with the table or column mapping editors, typing a Ctrl or Alt key combination could have initiated editing of the focused cell and either selected or opened a menu. This has been corrected so that typing a Ctrl or Alt key combination only performs the latter operation, and does not initiate editing.

CR:571806

CR Number:   571806 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 3907 12 Jun 2009 Fixed Description The server may have returned the nonfatal assertion error 102605 "Error building columns" when a query used a complex subselect on the Null supplying side of an outer join. For example: select V1.N1 from T1 V0 left outer join ( select 'M' as N1 from ( select V4.c as xx from T2 as V4,( select count(*) as N3 from T3 ) V3 where V4.b = V3.N3 ) V2 ) V1 on V0.a = V1.N1 This has now been fixed.

CR:571810

CR Number:   571810 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2249 20 May 2009 Fixed Description MobiLink clients (except for UltraLiteJ) now cache the host socket address to avoid extra calls to socket methods, such as getaddrinfo, inet_addr, and gethostbyname, for non-persistent HTTP and HTTPS synchronizations.

CR:571817

CR Number:   571817 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1616 13 May 2009 Fixed 11.0.1 2240 13 May 2009 Fixed Description NCHAR, NVARCHAR, and LONG NVARCHAR values from a SQL Anywhere database were exported as CHAR to an Oracle database if DBISQL had to create a table in the Oracle database to hold the data. This has been fixed.

CR:571957

CR Number:   571957 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 3835 13 May 2009 Fixed 10.0.1 3894 13 May 2009 Fixed 11.0.0 1617 13 May 2009 Fixed 11.0.1 2242 13 May 2009 Fixed Description The server could have generated a dynamic memory exhausted error when trying to execute a very complex statement. This has been fixed. The server will now return the SQL error SQLSTATE_SYNTACTIC_LIMIT.

CR:571988

CR Number:   571988 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1626 13 May 2009 Fixed 11.0.1 2241 13 May 2009 Fixed Description Fetching the connection property 'ServerNodeAddress', would have incorrectly returned the client's node address rather than the server's. This has been fixed.

CR:572122

CR Number:   572122 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 2242 14 May 2009 Fixed Description When a Synchronization Model was created and deployed on Unix systems, the created .sh files had statements like "if [[ value == value ]] ". The "[[", " ]]" and "==" were syntactically incorrect, causing error messages. This has been fixed. Also when running an mlsrv.sh file with an argument that contained spaces, such as "dsn=SQL Anywhere 11 Demo", would have failed. The connection string is now quoted within the file to correct this.

CR:572123

CR Number:   572123 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 2243 14 May 2009 Fixed Description When deploying a Synchronization Model on Unix systems, generated .sh files were not created with executable permissions set. A workaround was to run "chmod a+x" on all of the .sh files. This has been fixed. Now executable permission is set for everyone when .sh files are generated.

CR:572124

CR Number:   572124 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 2242 14 May 2009 Fixed Description Opening a previously deployed and saved Synchronization Model file with a new remote database, and then trying to deploy it using the last settings, would have failed with a file error while recreating the remote database. This has now been fixed. A workaround is to manually delete the remote database and transaction log before redeploying.

CR:572158

CR Number:   572158 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) 11.0.0 1617 14 May 2009 Fixed Description After application of an EBF, Sybase Central, and/or the Interactive SQL utility, may not have been able to connect to a database. The Sybase Central and dbisql fastloaders were not being terminated during the install of the EBF, resulting in a reboot prompt due to locked files. If the reboot prompt was ignored, the locked files are not updated which could result in various connection failures. This has been fixed.

CR:572179

CR Number:   572179 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2243 15 May 2009 Fixed Description On Linux systems, the Service utility (dbsvc) would not have stopped MobiLink services correctly. This has been fixed. The correct command was correctly echoed to the console but not actually executed. A workaround is to execute the command that was echoed.

CR:572187

CR Number:   572187 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) 08 Jul 2009 Fixed Description Multi-index scans which return very few rows were having their cost underestimated during query optimization. This may have resulted in multi-index scans being chosen incorrectly, which may have impacted the performance of the query execution. This has been fixed.

CR:572196

CR Number:   572196 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3836 15 May 2009 Fixed 10.0.1 3894 15 May 2009 Fixed 11.0.0 1618 15 May 2009 Fixed 11.0.1 2244 15 May 2009 Fixed Description It was possible for the MobiLink client (dbmlsync) to have sent an incorrect last download timestamp up to the MobiLink server, if dbmlsync had been running on a schedule, and ALL of the following had occurred during the last synchronization : 1) All of the data in the download stream had been applied, but had not yet been committed to the remote database. 2) An SQL Error had been generated by dbmlsync before the download had been committed. Examples of errors that could have occurred include an error occurring in the sp_hook_dbmlsync_download_ri_violation or the sp_hook_dbmlsync_download_end hooks, or an error occurring as dbmlsync had attempted to resolve referential integrity issues. 3) Another hook had been defined in the remote database that would have executed on another connection. For example, the sp_hook_dbmlsync_download_log_ri_violation or the sp_hook_dbmlsync_all_error hooks would have executed on a separate connection. This problem has now been fixed, and the proper last download timestamp is now sent up to the MobiLink server in the synchronization when this situation occurs.

CR:572347

CR Number:   572347 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 2245 19 May 2009 Fixed 11.0.0 1618 19 May 2009 Fixed Description For specific classes of the UPDATE statement, it was possible for the server to consume too much memory while processing the request. In extreme cases, the server could have failed with an out-of-memory error. This has been fixed.

CR:572544

CR Number:   572544 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 2244 19 May 2009 Fixed 11.0.0 1618 20 May 2009 Fixed Description During full text searches using a text index with a GENERIC term breaker, if a CONTAINS query contained a phrase with a term longer than MAXIMUM TERM LENGTH, the positional information for the term could have been lost. This could have caused incorrect results to be returned. This has now been fixed. Example: Consider a text index on col1 of table t, built using a text configuration with MAXIMUM TERM LENGTH equal to 7, MINIMUM TERM LENGTH equal to 1: SELECT t.* FROM t CONTAINS( col1, '"there is an elephant at the zoo"' ); Before this fix, the query above would be equivalent to: SELECT t.* FROM t CONTAINS( col1, '"there is an at the zoo"' ); and would miss documents containing the phrase "there is an elephant at the zoo".

CR:572547

CR Number:   572547 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2244 15 May 2009 Fixed Description When resetting a SQL Anywhere resource from the SQL Anywhere Monitor, it was possible that the reset dialog would have been dismissed before the reset operation had completed. This has been fixed.

CR:572549

CR Number:   572549 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 2244 15 May 2009 Fixed Description On Solaris systems with a non-UTF8 locale (eg. GB18030), when installing SQL Anywhere to a path containing MBCS characters, the installer would have failed to register the Sybase Central plugins. This has now been fixed.

CR:572556

CR Number:   572556 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) 15 May 2009 Fixed Description If the command line options -nogui and -onerror exit were used, and a connection could not be opened, when there was no command tail and connection parameters are given, dbisql did not quit and entered interactive mode. This has been fixed so that dbisql now quits with error code 9 ("could not connect").

CR:572935

CR Number:   572935 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 2246 20 May 2009 Fixed 11.0.0 1618 20 May 2009 Fixed Description If an UNLOAD ... INTO VARIABLE or UNLOAD ... INTO CLIENT FILE statement was used to unload either a table or a query containing an NCHAR column, the database server could crashed if the NCHAR character set was did not match the destination character set. This problem has been fixed.

CR:572936

CR Number:   572936 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2245 19 May 2009 Fixed Description After running for several days, it was possible that the SQL Anywhere Monitor would have stopped checking if SQL Anywhere resources had updates available. This has been fixed.

CR:572961

CR Number:   572961 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2246 20 May 2009 Fixed Description When the SQL Anywhere Monitor starts, it starts monitoring all the resources that are defined. If many resources were being monitored, this startup process could have taken several minutes, and caused degraded performance on the computer running the Monitor. A change has been made that attempts to alleviate these problems by having the Monitor be more conscious of limited system resources when the it starts. This improves the startup time of the SQL Anywhere Monitor when it is monitoring many resources.

CR:572968

CR Number:   572968 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 2246 20 May 2009 Fixed 11.0.0 1618 20 May 2009 Fixed Description A small amount of memory was being leaked on every synchronization by the QAnywhere Agent for Ultralite. This has been fixed.

CR:572973

CR Number:   572973 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 2254 03 Jun 2009 Fixed 11.0.0 1626 03 Jun 2009 Fixed Description During a large download, an out of memory error could have occurred on BlackBerry devices and simulators. This has been fixed. The row limiting algorithm has been improved, increasing the capacity of large downloads. To enable row limiting, first enable lazy loading of indexes, then use ConfigPersistent.setRowMaximumThreshold() and ConfigPersistent.setRowMinimumThreshold() to appropriate values (try 50,000 / (maximum cols per table + 1)).

CR:573160

CR Number:   573160 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 2249 22 May 2009 Fixed Description If an initial database size was specified in a CREATE DATABASE statement or with the -dbs option on the Initialization utility (dbinit), the resulting database would have been slightly larger (about 2MB) than the requested size. This has been fixed.

CR:573172

CR Number:   573172 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2250 21 May 2009 Fixed 11.0.0 1623 21 May 2009 Fixed 10.0.1 3899 21 May 2009 Fixed Description The server could have become deadlocked if the 'wait after end' option was used when performing a backup. This has now been fixed.

CR:573208

CR Number:   573208 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 2248 22 May 2009 Fixed Description Full text searches, where both arguments to the NEAR operator were the same token, would have matched documents containing a single copy of the token. This has been fixed.

CR:573222

CR Number:   573222 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 2352 20 May 2009 Fixed Description Support for FIPS 140-2 certified encryption has now been added to 64-bit Windows for UltraLite (except UltraLiteJ) and MobiLink clients . If the "FIPS-approved Strong Encryption" feature is not already installed, proceed as follows after applying the EBF: - From Add & Remove Programs, select SQL Anywhere 11 and click the Change button. - Select the Add option and enter the Add-on Registration Key and click Next. - In the dialog, ensure that the "FIPS-approved Strong Encryption" feature is selected and proceed. If the "FIPS-approved Strong Encryption" feature is already installed, proceed as follows after applying the EBF: - From Add & Remove Programs, select SQL Anywhere 11 and click the Change button. - Select the Modify option and de-select the "FIPS-approved Strong Encryption" feature, to temporarily remove it, and proceed. - Again from Add & Remove Programs, select SQL Anywhere 11 and click the Change button. - Select the Modify option and select the "FIPS-approved Strong Encryption" feature and proceed.

CR:573228

CR Number:   573228 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2247 21 May 2009 Fixed 10.0.1 3895 21 May 2009 Fixed Description When concurrent connection requests were made to servers running on multi core or multi processor Unix systems, connections could, in rare cases, have hung, received communication errors, or otherwise failed. This has been fixed.

CR:573427

CR Number:   573427 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 2248 21 May 2009 Fixed 11.0.0 1619 21 May 2009 Fixed Description When creating, duplicating or renaming an object, Sybase Central would have performed a case-sensitive comparison to determine if an object with the same name already existed in the database. Now, a case-insensitive comparison is performed.

CR:573452

CR Number:   573452 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 2248 22 May 2009 Fixed 11.0.0 1619 22 May 2009 Fixed 10.0.1 3895 22 May 2009 Fixed 9.0.2 3837 22 May 2009 Fixed Description Fetching a result set may, on rare occasions, have caused an application that connected using a newer version of Open Client 15 to hang or give a protocol error. In addition, cancelling a request may also have caused the application to hang or give a protocol error. These problems have now been fixed. Please note that if an application does use Open Client 15 to connect to SQL Anywhere, then it will be necessary to update the version of Open Client 15 once this fix is installed.

CR:573456

CR Number:   573456 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 2248 22 May 2009 Fixed Description On Windows x64 systems, attempting to start the MobiLink server with the -xo command line option (specify network protocal and options for version 8 and 9 clients), would have failed with a missing dll error if HTTPS was requested. The dll mlhttps11.dll was missing from the install. This has been corrected.

CR:573614

CR Number:   573614 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 2249 22 May 2009 Fixed 11.0.0 1620 22 May 2009 Fixed Description If requests were made to close several connections at the same time, then the server may have taken much longer than necessary to close all the connections. This problem was very rare and not very noticeable, but has been fixed.

CR:573625

CR Number:   573625 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2271 08 Jul 2009 Fixed 11.0.0 1645 08 Jul 2009 Fixed 10.0.1 3921 08 Jul 2009 Fixed 9.0.2 3860 08 Jul 2009 Fixed Description If an application asked for the connection status through the following ODBC API SQLGetConnectAttr( hdbc, SQL_ATTR_CONNECTION_DEAD, ... ) after an error occurred, the iAnywhere Solutions ODBC driver for Oracle could told the application that the connection was still alive, even though the connection had actually been killed, or had timed out. If this problem occurred for the MobiLink server main connection, in most cases, the server would have displayed the following messages: [10009] MobiLink table 'ml_scripts_modified' is damaged [-10020] Unable to flush scripts and refused any synchronization requests. This MobiLink server would then have needed to be be restarted in order to carry on any synchronization. This problem is fixed now.

CR:573636

CR Number:   573636 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 2249 25 May 2009 Fixed 11.0.0 1620 25 May 2009 Fixed 10.0.1 3896 25 May 2009 Fixed 9.0.2 3838 25 May 2009 Fixed Description After performing a database backup, a warning message of the form "Unable to open backup log '...'" could have been sent to the client and console. Note that this warning came as a "message" to the client, not as a warning SQLCODE from the BACKUP statement. The problem was far more likely to have occurred on Windows Vista or later when running as a non-elevated process, as the server typically tried to write the log into the SQL Anywhere installation directory which is not typically writable by non-elevated pocesses. This problem was fixed by properly detecting which of the possible directories for placement of backup.syb were writable, and adding the %ALLUSERSPROFILE%\SQL Anywhere XX (XX=version number) directory to the list of possible directories. On Vista and later, the %ALLUSERSPROFILE% directory is typically C:\ProgramData. On earlier versions of Windows, it is typically C:\Documents and Settings\All Users\Application Data.

CR:573824

CR Number:   573824 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2250 25 May 2009 Fixed 11.0.0 1621 25 May 2009 Fixed Description The 32-bit Unix versions of the SQL Anywhere ODBC Driver Manager (libdbodm) would have leaked a very small amount of memory for every statement handle that was allocated and subsequently freed. The memory leak problem has now been fixed. Note that the memory leak does not exist with the 64-bit Unix versions of the SQL Anywhere ODBC Driver Manager, and that the SQL Anywhere ODBC Driver Manager does not exist on Windows platforms. It should also be noted that several SQL Anywhere components on Unix platforms use the SQL Anywhere ODBC Driver Manager implicitly, and are therefore impacted by this problem. In particular, the server will use the SQL Anywhere ODBC Driver Manager for performing Remote Data Access operations; as well, the Mobilink Server uses the SQL Anywhere ODBC Driver Manager to talk to the consolidated database. Also, the iAnywhere JDBC driver uses the SQL Anywhere ODBC Driver Manager to make connections.

CR:573839

CR Number:   573839 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 2250 25 May 2009 Fixed 11.0.0 1621 25 May 2009 Fixed Description In the Synchronization Model wizard, when creating a model using a consolidated database and an existing remote database, the mapping editor's column headings could have been incorrect. In particular, the "Consolidated Table" column would have incorrectly been labelled "Mapping Direction". This has been fixed.

CR:573841

CR Number:   573841 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 2250 25 May 2009 Fixed 11.0.0 1621 25 May 2009 Fixed Description When starting a database created by a backup, particularly one created using BACKUP ... WAIT BEFORE START ... WITH CHECKPOINT LOG NO COPY, the server could have failed with an error of the form "Database cannot be started -- <log file name> not expecting any operations in transaction log". This problem has been fixed. As a workaround, add "-a <log file name>" to the server's command line. When recovery completes, the server will shut down. Afterwards, restart the server normally (without the "-a <log file name>" option).

CR:573843

CR Number:   573843 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3851 19 Jun 2009 Fixed Description In an UPDATE statement, no diagnostic error message was issued when a SET clause was not followed by a name. Thisn has been fixed so that an eroor message is now issue for this situation.

CR:573990

CR Number:   573990 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2252 29 May 2009 Fixed 11.0.0 1623 29 May 2009 Fixed 10.0.1 3899 29 May 2009 Fixed Description When calling the SADataReader.GetBytes method into a binary or varbinary column with a null buffer, it would have thrown the exception "no current row of cursor". This problem has been fixed.

CR:574014

CR Number:   574014 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 2251 26 May 2009 Fixed 11.0.0 1621 26 May 2009 Fixed 10.0.1 3897 26 May 2009 Fixed Description In some circumstances, it may have taken longer than expected to shutdown a database when it was started and then immediately stopped. This would only have been noticeable if the following three conditions were true: a) cache collection was enabled on the previous run of the database, b) cache warming was enabled on the current run of the database, c) the server accessed a large number of pages during the cache collection interval, i.e., the first queries executed against the database referenced a large number of pages (as may be the case in a scan of a large table or set of tables). This has been fixed. Note, cache collection is on by default, and is controlled by the -cc server command line option. A workaround is to disable cache warming using the -cr- server command line option.

CR:574022

CR Number:   574022 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2251 27 May 2009 Fixed 11.0.0 1621 27 May 2009 Fixed 10.0.1 3897 27 May 2009 Fixed Description When editing a table's schema using the table editor, the Cut, Paste, Delete and Undo toolbar button enabled states would not have been updated if the Ctrl key accelerators were used to perform these operations. This has been fixed.

CR:574222

CR Number:   574222 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 2251 28 May 2009 Fixed Description During a full text search, with a very long query containing conjunctive or disjunctive expressions only, the server could have failed with the error: "Text query parser error: parse stack overflow at or before character <n>". This has been fixed. Examples of queries that would failed: CONTAINS( col, 'apple & banana & tomato & cucumber & ..... & parsley' ) CONTAINS( col, 'dog | cat | camel | .... | chipmunk' ) where ... is a list of terms separated by the & or | operator.

CR:574314

CR Number:   574314 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2252 28 May 2009 Fixed 11.0.0 1622 28 May 2009 Fixed 10.0.1 3898 28 May 2009 Fixed Description Attempting to modify a service that was already running using the Service utility (dbsvc) with the -w "create service" command line option would have failed. The utility would have deleted the server, but would not have been able to re-create it. This has been fixed. If the service is running, dbsvc will now report an error and will not delete the service.

CR:574337

CR Number:   574337 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 2211 28 May 2009 Fixed Description If MobiLink servers were running in a server farm against a very busy consolidated database, some of the MobiLink servers may have shutdown automatically, due to the fact that they were no longer able to maintain their liveness to the consolidated database. To fix this problem, a new MobiLink server command line option to supply server farm database connection parameters has been added: -ca "keyword=value;..." This new option can be used to let the MobiLink servers connect to another database that is running on a less busy database server, and then the MobiLink servers will use this second database to maintain their state information for the server farm. This second database can be running on an SA, ASE, Microsoft SQL Server, Oracle, DB2, or MySQL database server. However, it must contain the MobiLink server system objects. Note, the -ca command line option must be the same for all the MobiLink servers across the same server farm, otherwise, redundant synchronizations may not be detected and data inconsistency can happen.

CR:574348

CR Number:   574348 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 2252 01 Jun 2009 Fixed Description When deploying a Synchronization Model, and using a secure stream, the Deploy Wizard's Secure Stream Server Certificate page incorrectly referred to an "Identity certificate file" and the File dialog opened by the Browse button only showed certificate files (with .crt and .cer extensions). The wizard should have listed identity files (with a private key as well as a certificate, and .id file extension by iAnywhere convention). This has been fixed. Now the page is called "Secure Stream Server Identity", which refers to an "identity file", and the File dialog by default shows only identity files with .id extension, although listing .crt and .cer files is still an option (in case the .id extension is not used). A workaround is to change the filter to show all file types and choose an identity file.

CR:574352

CR Number:   574352 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 2252 29 May 2009 Fixed Description If a Synchronization Model was deployed to a location that contained a space in the name, or the deployed model contained a space in the name, then the remote and consolidated script files would not have functioned correctly. This has now been corrected. A workaround is to manually edit the files and quote any file paths that contained spaces.

CR:574354

CR Number:   574354 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2250 29 May 2009 Fixed 11.0.0 1622 29 May 2009 Fixed 10.0.1 3898 29 May 2009 Fixed 9.0.2 3840 29 May 2009 Fixed Description The iAS ODBC driver for Oracle could have crash in a stored procedure call, if the stored procedure contained char or varchar type INOUT parameters, and the data length of these parameters was greater than 2000 bytes (1000 bytes for driver versions, 9.0.2 and 10.0.1). This has now been fixed.

CR:574364

CR Number:   574364 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 2252 29 May 2009 Fixed 11.0.0 1622 29 May 2009 Fixed Description If an application accessed a connection-scoped external environment via an HTTP request or from an event, then the external environment would have shut down when the HTTP request finishes or when the event completed. As a result, the next HTTP request or event that accessed the external environment required that the external environment be restarted. The server has now been improved such that starting an external environment is between 20% to 25% faster. Note that applications that use a database-scoped external environment (i.e. Java or CLR) will see a very modest performance improvement.

CR:574473

CR Number:   574473 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 2255 04 Jun 2009 Fixed 11.0.0 1627 04 Jun 2009 Fixed 10.0.1 3903 04 Jun 2009 Fixed Description The conflict() function, used with SQL Remote in RESOLVE UPDATE triggers, did not return correct results. The result of the function was always FALSE. This has been fixed.

CR:574475

CR Number:   574475 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 2250 29 May 2009 Fixed 11.0.0 1624 29 May 2009 Fixed 10.0.1 3900 29 May 2009 Fixed Description Under very rare circumstances, a client-side backup that truncates or renames the log may have hung the server. This has now been fixed.

CR:574693

CR Number:   574693 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 2253 01 Jun 2009 Fixed 11.0.0 1624 01 Jun 2009 Fixed Description The QAnywhere Agent for UltraLite would have given a misleading error message if an invalid username or password was specified in the connection string. The error message that was being generated looked like: Internal error: SQLCODE: -108, SQLSTATE: [] Source statement: SET OPTION isolation_level=read_committed QAnywhere Agent failed to initialize message store This has been fixed so that the agent now returns error code -103 as expected

CR:574697

CR Number:   574697 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2254 04 Jun 2009 Fixed 11.0.0 1626 04 Jun 2009 Fixed 10.0.1 3902 04 Jun 2009 Fixed 9.0.2 3843 04 Jun 2009 Fixed Description If a NUMERIC INOUT parameter was bound as SQL_PARAM_INPUT_OUTPUT, the result that was returned to the caller was always 0. For example: CREATE PROCEDURE _TEST_PROC ( @IN_VAL1 NUMERIC(7, 0), @IN_VAL2 NUMERIC(7, 0), @OUT_VAL NUMERIC(7, 0) OUTPUT ) AS BEGIN SET @OUT_VAL = @IN_VAL1 + @IN_VAL2 END If the statement "CALL PROCEDURE _TEST_PROC( 100, 200, ? )" was prepared, and the third parameter was bound as SQL_PARAM_INPUT_OUTPUT, the result after execution was 0. It should have been 300. If the parameter was bound as SQL_PARAM_OUTPUT, the result returned was correct.This problem has been fixed. Note that in the above Transact SQL procedure, OUT_VAL is an INOUT parameter, since Transact SQL parameters are always INPUT and the addition of the OUTPUT clause makes them INOUT.

CR:574698

CR Number:   574698 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 2253 02 Jun 2009 Fixed 11.0.0 1624 02 Jun 2009 Fixed Description The QAnywhere Java clients could have gone into an endless loop, with 100% CPU usage, if it attempted to uncompress a message whose content has become somehow corrupted. This has been fixed so that the clients now return a suitable error message to indicate that it failed to retrieve the message.

CR:574707

CR Number:   574707 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 2253 01 Jun 2009 Fixed 11.0.0 1624 01 Jun 2009 Fixed 10.0.1 3900 01 Jun 2009 Fixed Description If an application made an external environment request, and the server was under heavy load, then there was a chance the external environment would have taken too long to respond to the request. In such situations, the server would have timed out the request and returned control back to the application. If the external environment responded to the request at exactly the same time the server timed the request out, then there was a very small chance the server would have hung. This has now been fixed.

CR:574708

CR Number:   574708 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 2253 01 Jun 2009 Fixed 11.0.0 1624 01 Jun 2009 Fixed 10.0.1 3900 01 Jun 2009 Fixed Description Executing a query that required a result set to be fetched from a remote table, could have in very rare situations, caused the server to crash. This problem has now been fixed.

CR:574710

CR Number:   574710 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2253 02 Jun 2009 Fixed Description When the SQL Anywhere Monitor was run on Linux systems, and used to monitor a large number of resources, there is a very good possibility that the Monitor would have performed poorly. This problem only existed after applying the 11.0.1 build 2222 EBF. This problem has now been fixed.

CR:574746

CR Number:   574746 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 2253 02 Jun 2009 Fixed 11.0.0 1624 02 Jun 2009 Fixed 10.0.1 3900 02 Jun 2009 Fixed Description If an unknown connection parameter was provided to the ODBC driver, the driver would have given the error: "Parse Error: Invalid or missing keyword near '<unknown parameter>'". Some applications (for example, Crystal Reports in some cases) generate connection parameters which are unknown to SQL Anywhere, which resulted in connection failures. This has been fixed so that unknown connection parameters are now ignored. This returns the ODBC driver to the Adaptive Server Anywhere 9.x and earlier behavior.

CR:574912

CR Number:   574912 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 2254 03 Jun 2009 Fixed 11.0.0 1625 03 Jun 2009 Fixed 10.0.1 3901 03 Jun 2009 Fixed 9.0.2 3842 03 Jun 2009 Fixed Description If a database contained a DISCONNECT event handler called E, and a transaction log containing a DROP EVENT E statement was applied to the database, recovery could have reported failed assertion 100904 ("Failed to redo a database operation ... Event E in use"). This has been fixed.

CR:574920

CR Number:   574920 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 2260 04 Jun 2009 Fixed 10.0.1 3909 04 Jun 2009 Fixed 9.0.2 3849 08 Jun 2009 Fixed Description A client side backup of a database with a path and filename length greater than 69 bytes in the client character set, could have failed or truncated the filename. This has been fixed.