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

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

CR:574929

CR Number:   574929 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 2254 03 Jun 2009 Fixed Description When an UltraLiteJ client did a ping-only synchronization to a MobiLink server, the authenticate_user connection event was not fired. This has been fixed. A work around is to sync a single table (download only) with a different script version, where that script does not have any upload or download scripts.

CR:575116

CR Number:   575116 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 2254 03 Jun 2009 Fixed Description The changes for Engineering case 569934 enhanced performance for directory access queries of the form: SELECT [...,]contents[,...] FROM dir_table WHERE [...AND] file_name=[string|variable] [AND...] These quesries now execute much faster as the "file_name=" predicate evaluation is now pushed down into the directory access server. Unfortunately, if the "file_name=" was specified as a fully qualified reference as in "dir_table.file_name=", then the predicate would not have been pushed down. This problem has now been fixed.

CR:575121

CR Number:   575121 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 3906 10 Jun 2009 Fixed Description n exceptionally rare circumstances, the server may have crashed when using user-defined data types with a DEFAULT clause. This has been fixed. Workaround Description  None.

CR:575142

CR Number:   575142 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3906 11 Jun 2009 Fixed Description Invalid metadata could have been constructed for a UNION DISTINCT operation. The Interactive SQL utility uses this metadata for display purposes when connected to an UltraLite database. This could have resulted in abnormal terminations for statements such as: "SELECT 1 UNION DISTINCT SELECT 2". This has now been corrected.

CR:575149

CR Number:   575149 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 2254 16 Jun 2009 Fixed 11.0.0 1626 16 Jun 2009 Fixed Description The changes made for Engineering case 556453 introduced a bug that caused the Interactive SQL utility (dbisql) to crash when attempting to edit a DATE value in a result set. This has been fixed.

CR:575181

CR Number:   575181 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 2255 04 Jun 2009 Fixed Description If an UltraLite application had more than one open table or result set, and an attempt was made to execute the SQL SYNCHRONIZE statement, the UltraLite runtime would have returned the error SQLE_SCHEMA_UPGRADE_NOT_ALLOWED (-953). This has now been fixed.

CR:575323

CR Number:   575323 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 3903 08 Jun 2009 Fixed Description When executing a query that referenced a proxy table in another SQL Anywhere database, and made use of the newid(), strtouuid() or uuidtostr() system functions, it may have executed much slower than expected. This problem has now been fixed.

CR:575325

CR Number:   575325 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 2255 04 Jun 2009 Fixed Description When doing concurrent database operations during a synchronization, uploaded LONG VARCHAR or LONG BINARY columns could have been corrupted in the consolidated database. This is now fixed.

CR:575490

CR Number:   575490 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2266 25 Jun 2009 Fixed 10.0.1 3914 25 Jun 2009 Fixed Description Wide-fetching a query that referenced a proxy table could have returned the last row multiple times, instead of returning no rows and the SQLE_NOTFOUND warning. This has been fixed.

CR:575493

CR Number:   575493 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 2260 16 Jun 2009 Fixed Description The Unload Database or Upgrade Database wizards in the UltraLite plugin for Sybase Central could have failed if the XML file was located in a path that contained spaces. This has been fixed.

CR:575495

CR Number:   575495 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 2255 05 Jun 2009 Fixed 11.0.0 1627 05 Jun 2009 Fixed Description When an INSERT or UPDATE was pending upload on a row, and there was a no-sync DELETE on the same row, there may have been a row left in the row page store for the table after the clean-up that is done after a successfull upload. Had Index Persistence been turned off for the database and a row with the same primary key been inserted or downloaded afterwards, there would have been a primary key violation the next time the database was shutdown and re-connected to. Also, primary key violations could have occurred on databases with Index Persistence tuirned off after error recovery from failed synchronizations. These problems have now been fixed.

CR:575516

CR Number:   575516 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 2255 09 Jun 2009 Fixed Description When editing a Synchronization Model, deleting the "timestamp column name" (or another text box's contents) and then trying to switch to another Synchroniation Model without saving changes, would have caused an error to occur. This has been fixed.

CR:575517

CR Number:   575517 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 2255 09 Jun 2009 Fixed Description When using the Table Mapping editor, changed the sorting order of table mappings in the GUI may have displayed a prompt to save the model, even though no changes were made. This has been fixed.

CR:575538

CR Number:   575538 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 2221 08 Jun 2009 Fixed Description When the Relay Server Outbound Enabler's attempts to re-establish its channels to a Relay Server failed (for example, RelayServer still down), it could have occasionally quit further attempts. This has been fixed.

CR:575539

CR Number:   575539 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 2255 08 Jun 2009 Fixed Description If the Relay Server Outbound Enabler (RSOE) was connected to an Apache RelayServer, and then RSHOST was shutdown through a command line (rshost -s), then this would have caused the RSOE's up channel to enter a loop and issue an "Invalid opcode!" error message. This has been fixed.

CR:575556

CR Number:   575556 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 2364 15 Dec 2009 Fixed Description Executing queries with full outer joins or Transact SQL outer joins could have caused the server to crash, or behave unexpectedly, if a CONTAINS clause was present in the same query block as the join. This has been fixed. Note, with Transact SQL outer joins, a CONTAINS clause is permitted only in the WHERE clause, and can only reference the preserved side of the join, not the null-supplying side.

CR:575755

CR Number:   575755 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 2261 19 Jun 2009 Fixed Description The Maintenance Release and EBF installs were not correctly updating the product version number in the .NET configuration file 'machine.config'. This has been fixed.

CR:575760

CR Number:   575760 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 2256 08 Jun 2009 Fixed Description When there is only one connection, the maximum number of prefetch rows has been increased to 10000. If there is more than one connection, the maximum number of prefetch rows remains unchanged at 1000. Performance may improve when all of the following conditions are met: - an application has only one connection - fetching a result set with many thousands of rows - each row in the result set has small number of columns - the data size of the fetched columns is small - prefetch is enabled - the connection is over TCP/IP (shared memory connections are not likely to see a significant performance improvement)

CR:575782

CR Number:   575782 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 2256 09 Jun 2009 Fixed 11.0.0 1628 09 Jun 2009 Fixed Description Under certain rare circumstance, a mirror server may have crashed on shutdown when processing a transaction log rename request. This has been fixed.

CR:575783

CR Number:   575783 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 2256 08 Jun 2009 Fixed Description When adding a SQL Anywhere resource to the SQL Anywhere Monitor, it was possible for the authorization dialog could have appeared twice. This has been fixed.

CR:575787

CR Number:   575787 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 2256 09 Jun 2009 Fixed 11.0.0 1628 09 Jun 2009 Fixed Description The transaction log on the mirror server in a mirroring system may have become corrupt under rare circumstances. One example would be the mirror server processing a log rename request when the primary server disconnects. Should corruption occur, the database on the mirror server would have failed to start with the error "Can't use log file since it is shorter than expected." This has been fixed.

CR:575790

CR Number:   575790 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) 8.0.2 2256 09 Jun 2009 Fixed Description If an application connected using the iAnywhere JDBC driver and fetched a large number of numeric values, then the fetch could have taken a long time. The iAnywhere JDBC driver has now been improved to fetch numeric values in a much quicker fashion if the numeric column has a precision that is less than or equal to 18 and a scale of 0. No performance improvements have been made if the scale is nonzero or if the scale is zero but the precision is greater than 18.

CR:575983

CR Number:   575983 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 2257 09 Jun 2009 Fixed 11.0.0 1629 09 Jun 2009 Fixed Description When editing a DATE or TIMESTAMP value in a result set, the editor would not have accepted dates in the ISO format (YYYY-MM-DD). This has been corrected so that the ISO format is now accepted.

CR:576008

CR Number:   576008 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 2257 11 Jun 2009 Fixed Description If a query contained a LIKE predicate with a non-string value (Integer, Date, etc.), then it was possible for the predicate to evaluate a little more slowly than it could have. The non-string value was converted to NCHAR before the comparison, and this imposed additional overhead that was not present in previous versions. It is equivalent and faster to perform the comparison using VARCHAR, which is now how the comparison is done.

CR:576009

CR Number:   576009 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 2257 10 Jun 2009 Fixed 11.0.0 1629 10 Jun 2009 Fixed 10.0.1 3905 10 Jun 2009 Fixed 9.0.2 3845 10 Jun 2009 Fixed Description The size of the stack used by some database server threads was not governed by the -gs and -gss server command line options. Some of these threads used stacks that were excessively large (1MB) for a CE environment, and could have lead to problems loading DLL's on some CE systems. These stack sizes have been reduced to 64K or less. The default stack size for request tasks is unchanged at 96K. Some versions did not allow a -gss value of less than 96K, but now values as low as 64K are permitted.

CR:576016

CR Number:   576016 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3906 12 Jun 2009 Fixed Description Use of the "-f" command line option did not behave consistently when the fast launcher option was on. It would work correctly the first time, but subsequently running "dbisql -f filename" with a different file, would have opened the first file again. This has been fixed.

CR:576120

CR Number:   576120 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3860 08 Jul 2009 Fixed Description The MobiLink server would have reported [-10001] 'Protocol error' during synchronizations, if a DROP INDEX had been issued against the UltraLite remote database. This has been fixed.

CR:576213

CR Number:   576213 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 2258 11 Jun 2009 Fixed 11.0.0 1631 12 Jun 2009 Fixed 10.0.1 3907 12 Jun 2009 Fixed Description If a SELECT statement included an alias specified as a single-quoted string, and the string contained a double quote or backslash, a syntax error should have been given, but was not. This has been fixed; an error will be reported in this case.

CR:576252

CR Number:   576252 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2257 11 Jun 2009 Fixed Description Support for SQL Anywhere Explorer and SQL Anywhere Toolbar has been disabled for Visual Studio 2010. They still support Visual Studio versions 2005 and 2008.

CR:576257

CR Number:   576257 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2257 11 Jun 2009 Fixed Description Changes have been made to the iAnywhere JDBC driver in order to improve fetch times for Date, Time and Timestamp values. Applications that are fetching a large number of Date, Time and/or timestamp values from the same ResultSet object, will now see a large improvement.

CR:576263

CR Number:   576263 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) 10.0.1 3906 12 Jun 2009 Fixed 9.0.2 3847 12 Jun 2009 Fixed Description If the CREATE DATABASE statement was used to create a database with a filename that contained a \n (for example CREATE DATABASE 'c:\\new.db'), the file_name column in the SYSFILE system table could have been incorrect. An incorrect file_name value would only have occurred if the CREATE DATABASE statement was issued when connected to a database other than the utility_db. This has been fixed. Note, this problem did not affect the Initialization utility (dbinit), or applications calling the dbtools library.

CR:576447

CR Number:   576447 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.0.1 2258 12 Jun 2009 Fixed 11.0.0 1630 12 Jun 2009 Fixed Description The SQL Anywhere Python support module (sqlanydb.py) did not set the rowcount attribute for UPDATE, INSERT or DELETE statements. This has been corrected.

CR:576448

CR Number:   576448 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Linux Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2262 19 Jun 2009 Fixed 11.0.0 1636 19 Jun 2009 Fixed Description When run on Unix systems, if the redirector was configured to route to more than one backend, and one of the backend servers went down, the redirector could have failed to route requests to the live backend. In this case, the redirector would have added the error message "No machine is available to handle request" to the error log. This has been fixed. Workaround Description  None.

CR:576500

CR Number:   576500 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 2258 15 Jun 2009 Fixed Description When a Synchronization Model was being generated for a MySQL database, columns that had been defined as nchar and nvarchar in the MySQL database, would have been mapped as char and varchar in the Synchronization Model. This has been fixed.

CR:576501

CR Number:   576501 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 2260 15 Jun 2009 Fixed Description If a Synchronization Model had a table mapping that was upload-only or download-only, then attempting to synchronize would have caused a warning that some scripts were missing. This has ben fixed by generating ignored scripts for the unneeded upload or download scripts, which suppressed the warnings. A workaround is to disable the warning, or create dummy scripts.

CR:576669

CR Number:   576669 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 2258 15 Jun 2009 Fixed Description Executions of a BACKUP DATABASE TO ... archive backup statement, using the "with checkpoint log no copy" clause, would have been slower than necessary, particularly when the transaction log file was large. This has been fixed.

CR:576689

CR Number:   576689 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 2258 12 Jun 2009 Fixed 11.0.0 1631 12 Jun 2009 Fixed Description SQL Anywhere HTTP client procedures defined with a PROXY clause would have caused the server to crash. This has been fixed.

CR:576709

CR Number:   576709 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 2328 06 Oct 2009 Fixed Description A mirror transaction log file could have become corrupted after the file was grown. The error received would have been "Error: Cannot open transaction log file -- <mirror file name> is an invalid transaction log mirror." The server was failing to update the mirror log file size at the appropriate time. This has been fixed.

CR:576913

CR Number:   576913 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 3908 16 Jun 2009 Fixed 9.0.2 3849 16 Jun 2009 Fixed Description If an application executed a remote query that must be handled in NO PASSTHRU mode, and the query contained many tables, then it was possible for the server to fail assertion 101508, instead of giving the "syntactic limit exceeded" error. This problem has now been fixed, and the error is now properly returned.

CR:577092

CR Number:   577092 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 2260 16 Jun 2009 Fixed 11.0.0 1633 16 Jun 2009 Fixed Description Previously, the SQL Anywhere Python driver (sqlanydb.py) raised an OperationalError for all database errors. The driver now raises an IntegrityError for the following SQLCODEs: SQLCODE Error -193 Primary key for table '%1' is not unique : Primary key value ('%2') -194 No primary key value for foreign key '%1' in table '%2' -195 Column '%1' in table '%2' cannot be NULL -196 Index '%1' for table '%2' would not be unique

CR:577109

CR Number:   577109 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 2260 16 Jun 2009 Fixed 11.0.0 1633 16 Jun 2009 Fixed 10.0.1 3909 16 Jun 2009 Fixed Description If an application maked use of the Java in the database feature, and a JAVA stored procedure wrapper was defined such that the number of SQL arguments in the stored procedure was greater than the number of arguments defined in the Java method signature, then calling the Java stored procedure may have crashed the server. This problem has now been fixed, and a Java signature mismatch error will now be returned.

CR:577129

CR Number:   577129 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 2260 17 Jun 2009 Fixed Description On some Linux distributions (eg Suse 11), the server may have taken an exceedingly long time to write out a mini-core dump. This has been fixed.

CR:577142

CR Number:   577142 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 2260 17 Jun 2009 Fixed Description The MobiLink server would not have skipped a script that was defined to be ignored, if the script contained white space (spaces, tabs, and/or line-breaks) before the special prefix, '--{ml_ignore}'. This problem is fixed now.

CR:577297

CR Number:   577297 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 2268 03 Jul 2009 Fixed 10.0.1 3918 03 Jul 2009 Fixed Description If a procedure was used in the FROM clause of a query, it was possible for the server to crash if the procedure result set had a particular form. This has been fixed.

CR:577321

CR Number:   577321 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3846 18 Jun 2009 Fixed Description The MobiLink server with messaging (-m command line option) could have crash when used with an ASE 12.5.3 consolidated database server and the ASE ODBC driver version 15.0.0.140. This problem was introduced by the changes for Engineering case 560045, and has now been fixed.

CR:577334

CR Number:   577334 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2260 19 Jun 2009 Fixed 11.0.0 1634 19 Jun 2009 Fixed 10.0.1 3910 19 Jun 2009 Fixed Description When using the SQL Anwhere C API (drivers for PHP, Perl, Python, and Ruby), applications executing RAISERROR with a user-defined error, would have seen the correct error code returned, but the error message was returned as "Unknown error". This has been fixed.

CR:577512

CR Number:   577512 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 2275 21 Jul 2009 Fixed Description Sybase Central plugins for Ultralite & QAnywhere were not being registered when deployed by the Deployment wizard. This has now been corrected.

CR:577532

CR Number:   577532 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2261 19 Jun 2009 Fixed Description An application running under a Java VM in server mode, and fetching a large result set, will now retrieve the result set much faster.

CR:577548

CR Number:   577548 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 2268 03 Jul 2009 Fixed 10.0.1 3917 03 Jul 2009 Fixed Description It was possible for the server to apply stale values in an UPDATE statement if concurrent requests issued UPDATE statements at isolation level 0 or 1. This would occur with particular timing when the UPDATE statements did not bypass the query optimizer, and neither UPDATE statement contained a join, or a subquery converted to a join. This has been fixed.

CR:577714

CR Number:   577714 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2261 22 Jun 2009 Fixed 11.0.0 1635 22 Jun 2009 Fixed 10.0.1 3911 22 Jun 2009 Fixed Description The ADO.Net sample program LinqSample was not working correctly. This has now been fixed.

CR:577928

CR Number:   577928 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 2271 07 Jul 2009 Fixed 10.0.1 3921 07 Jul 2009 Fixed Description It was possible for the server to crash when executing an UPDATE or DELETE statement for particular execution plans. This has been fixed.

CR:577932

CR Number:   577932 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 2277 21 Jul 2009 Fixed Description When deploying SQL Anywhere using the Deployment wizard, the PHP Extenv DLLs were being deployed (php-<PHP version>_sqlanywhere_extenv11.dll), but not the PHP SQL Anywhere DLLs (php-<PHP_version>_sqlanywhere.dll). These have now been added to the list of files deployed.

CR:577938

CR Number:   577938 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   4.3.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2262 23 Jun 2009 Fixed 11.0.0 1636 23 Jun 2009 Fixed 10.0.1 3912 23 Jun 2009 Fixed Description Sybase Central could have occasionally reported an internal error on startup, when the Fast Launcher option was turned on. This has been fixed.

CR:577974

CR Number:   577974 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2266 26 Jun 2009 Fixed 11.0.0 1640 26 Jun 2009 Fixed 10.0.1 3915 26 Jun 2009 Fixed Description Using an ADO.NET Entity Data Model object with an ASP.NET Web Site project did not work correctly. This has been corrected.

CR:577984

CR Number:   577984 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 2176 23 Jun 2009 Fixed 11.0.0 1590 23 Jun 2009 Fixed Description When the Relay Server Outbound Enabler (rsoe) was shutdown, the message "<UpChannel-xxxx> networkRead: interrupted error errCode: 218, sysCode: 0" was written to the log file. This is a lower level error indicating the blocking read operation had been interrupted. This error message is redundant and confusing, and has been removed. An informational message will still be printed at a higher level.

CR:578001

CR Number:   578001 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 2263 23 Jun 2009 Fixed 11.0.0 1636 23 Jun 2009 Fixed Description If an ODBC escape sequence was used that was preceded by a keyword, it was mangled by the Interactive SQL utility. The first and last characters were stripped off. This has now been fixed.

CR:578130

CR Number:   578130 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 2265 23 Jun 2009 Fixed 11.0.0 1637 23 Jun 2009 Fixed 10.0.1 3913 23 Jun 2009 Fixed Description If LOAD TABLE, or OPENSTRING were used, and all of the following conditions were true: - ENCODING 'UTF-8' was specified - the destination table has both CHAR and NCHAR columns - the CHAR encoding was not UTF-8 - file data that was destined for a CHAR column contained illegal characters or characters which could not be converted losslessly to the CHAR encoding the server could have crashed. This problem has been fixed.

CR:578153

CR Number:   578153 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) 9.0.2 3852 23 Jun 2009 Fixed 11.0.1 2268 06 Jul 2009 Fixed 11.0.0 1641 06 Jul 2009 Fixed 10.0.1 3917 06 Jul 2009 Fixed Description If a database created with a version 9 or earlier server was backed up via the Backup utility (dbbackup), or the BACKUP DATABASE statement, the backup copy could not have been unloaded using the Unload utility from version 10 or later. This has been fixed.

CR:578172

CR Number:   578172 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2265 25 Jun 2009 Fixed 11.0.0 1639 25 Jun 2009 Fixed 10.0.1 3914 25 Jun 2009 Fixed Description Calls to the methods SADataReader and SADataAdapter would not have returned any data for temporary tables. An AutoCommit when opening a data reader would have dropped temporary tables. This has now been fixed.

CR:578191

CR Number:   578191 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 2266 25 Jun 2009 Fixed 11.0.0 1639 25 Jun 2009 Fixed 10.0.1 3914 25 Jun 2009 Fixed 9.0.2 3854 25 Jun 2009 Fixed Description If a server had request-level logging enabled (eg -zr sql command line option) while the stored procedure debugger was being used (ie Sybase Central was in "Debug mode"), the server could have crashed. This problem has been fixed.

CR:578292

CR Number:   578292 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 95 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2270 14 Aug 2009 Fixed 11.0.0 1644 07 Jul 2009 Fixed Description If a scheduled event was defined, and the event made a CLR external environment call, then the server's, and the CLR external environment's, memory usage would have continued to grow in size with each execution of the event. Note that this problem was specific to the CLR external environment. The problem has now been fixed such that the server will now grow and shrink as needed, and the CLR external environment will shrink whenever garbage collection kicks in.

CR:578346

CR Number:   578346 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 2265 24 Jun 2009 Fixed Description On parallel systems, highly concurrent (tens of connections) temporary table modifications are now faster.

CR:578365

CR Number:   578365 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 2265 24 Jun 2009 Fixed 11.0.0 1639 24 Jun 2009 Fixed 10.0.1 3914 24 Jun 2009 Fixed Description In extremely rare circumstances, the internal representation of the lower bound of an index scan could have become corrupted for servers run on 32 bit systems. The problem could have manifested itself in many ways, although the most likely would have been an incorrect result set being returned. This has now been corrected.

CR:578385

CR Number:   578385 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 2265 25 Jun 2009 Fixed Description Following an initial install of version 11.0.1, the installer would have left incorrect information as to the version of the documentation that was installed, 11.0.0 instead of 11.0.1. Any method of checking for documentation updates, via the web page, at the end of install, using dbsupport, or using the Admin Tools, would then have used the incorrect version. This has now been corrected.

CR:578401

CR Number:   578401 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2265 25 Jun 2009 Fixed 11.0.0 1639 25 Jun 2009 Fixed Description The iAnywhere Solutions ODBC driver for Oracle could have held the socket descriptor and service handle, even when the database connection had been disconnected. This could have resulted in the driver running out of service handles with the following error: "ORA-12519: TNS:no appropriate service handler found". The OCI function, OCIServerDetach, was missing in the logoff function. This has now been corrected.

CR:578612

CR Number:   578612 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2270 07 Jul 2009 Fixed Description An INSERT statement, with a VALUES clause containing subquery expressions, could have caused a crash. This has been corrected.

CR:578616

CR Number:   578616 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 2266 25 Jun 2009 Fixed 11.0.0 1639 25 Jun 2009 Fixed Description If a server had a large number of connections making external environment calls, to the same database-scoped external environment, and the external environment process crashed due to heavy load, out of memory or some other reason, then there was a small chance the server would also have crashed. This has now been fixed.

CR:578617

CR Number:   578617 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 2266 25 Jun 2009 Fixed Description On Unix systems, an ANSI-only (no wide call support) ODBC driver is now available. The name of the driver is libdbodbcansi11_r. Only a threaded variant is provided. On Mac OS X, in addition to the dylib, the driver is also available in bundle form (dbodbcansi11_r.bundle). Certain frameworks, such as Real Basic, do not work with the dylib and require the bundle. The regular SQL Anywhere ODBC driver treats SQLWCHAR strings as UTF-16 strings. Starting in SQL Anywhere 10, when Unicode support in the Unix ODBC drivers was first introduced, the driver could not have been used with some ODBC driver managers, such as iODBC, which treated SQLWCHAR strings as UTF-32 strings. When dealing with Unicode-enabled drivers, these driver managers would translate narrow calls from the application to wide calls into the driver. An ANSI-only driver gets around this behaviour, allowing the driver to be used with such driver managers, as long as the application does not make any wide calls. Wide calls through iODBC, or any other driver manager with similar semantics, remain unsupported.

CR:578636

CR Number:   578636 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 2266 26 Jun 2009 Fixed Description Support has now been added for the SQL statements CREATE PUBLICATION, ALTER PUBLICATION and DROP PUBLICATION. This change also includes support for publication predicates.

CR:578818

CR Number:   578818 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 2266 09 Jul 2009 Fixed 11.0.0 1645 09 Jul 2009 Fixed Description A busy server could have crashed, or given an error, when updating a text index defined with the IMMEDIATE REFRESH clause. This has been fixed.

CR:578859

CR Number:   578859 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 2266 03 Jul 2009 Fixed Description The GUI launchers for the 11.0.1 Administration Tools no longer worked after Java for Mac OS X v10.5 Update 4 was installed. The following error messages would have appeared in the logs: [JavaAppLauncher Warning] Java application launched from PPC or bad stub. Relaunching in 32-bit, and tagging sub-processes to prefer 32-bit with $JAVA_ARCH=i386. [JavaAppLauncher Error] This process is [i386] and was re-exec'd from [i386], but for some reason we are trying re-exec to []. [JavaAppLauncher Error] unable to find a version of Java to launch This has been fixed. There are two workarounds: 1. Use the command line launchers instead of the GUI launchers. 2. Run the following from a terminal: . <SQL Anywhere 11 Installation Directory>/System/bin64/sa_config.sh for TOOL in DBConsole.app InteractiveSQL.app MobiLinkMonitor.app SybaseCentral.app ; do chmod +w "$SQLANY11/../$TOOL/Contents/MacOS/ JavaApplicationStub" ; cp /System/Library/Frameworks/JavaVM.framework/ Versions/A/Resources/MacOS/JavaApplicationStub64 "$SQLANY11/../$TOOL/ Contents/MacOS/JavaApplicationStub" ; done Note, the portion of the script from "for" to "done" should be one single line.

CR:578933

CR Number:   578933 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 3856 03 Jul 2009 Fixed 11.0.0 1641 03 Jul 2009 Fixed 11.0.1 2268 03 Jul 2009 Fixed Description The FORWARD TO statement could have truncated the forwarded statements to roughly a database page size in length. This has been fixed.

CR:578975

CR Number:   578975 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 2269 03 Jul 2009 Fixed Description Under certain conditions, it was possible for the server to hang when performing operations with long strings. This has been fixed.

CR:578990

CR Number:   578990 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2267 03 Jul 2009 Fixed 10.0.1 3924 13 Jul 2009 Fixed 9.0.2 3863 13 Jul 2009 Fixed Description If an application called DatabaseMetaData.getSystemFunctions(), the string returned would have contained the functions named dbname and username. The correct function names are database and user. This problem has now been fixed.

CR:578998

CR Number:   578998 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1910 14 Jul 2009 Fixed Description When an application connected using the iAnywhere JDBC driver and attempted to describe the metadata of a table or result set that contained a char column, the metadata would have returned the type name of the column as Char, but the SQL type would still have come back as Types.VARCHAR. If a JDBC application wanted to get the JDBC driver to return the SQL type of Char columns as Types.CHAR, then the application was required to set the "odbc_distinguish_char_and_varchar" database option. As of SQL Anywhere 12 the new SQL Anywhere JDBC driver, and the deprecated iAnywhere JDBC driver, now return the type name Char and SQL type Types.CHAR for table and result set columns of type Char, and the typename Varchar and the SQL type Types.VARCHAR for columns of type Varchar, regardless of the database option setting.

CR:579018

CR Number:   579018 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 3916 03 Jul 2009 Fixed 11.0.0 1641 03 Jul 2009 Fixed 11.0.1 2267 03 Jul 2009 Fixed Description If an application created a proxy table and specified the remote owner in the location clause, then attempting to access the proxy table would have failed with a syntax error if the remote owner name was a keyword. This problem has now been fixed.

CR:579150

CR Number:   579150 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 3857 03 Jul 2009 Fixed Description The server may have crashed if a statement that referenced a proxy table was very complex and used alias names that depended on many other alias names. This has been fixed.

CR:579215

CR Number:   579215 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 1641 03 Jul 2009 Fixed 11.0.1 2267 03 Jul 2009 Fixed Description The SQL Anywhere Python driver (sqlanydb.py) would have failed to load on Mac OS X systems as a result of failing to load the SQL Anywhere C API runtime library. The driver was looking for dbcapi.dll or libdbcapi_r.so, whereas on Mac OS X the file name is libdbcapi_r.dylib. This has now been corrected.

CR:579219

CR Number:   579219 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 2271 03 Jul 2009 Fixed 10.0.1 3921 08 Jul 2009 Fixed Description Calling the function SQLGetInfo() function with the SQL_SQL92_STRING_FUNCTIONS information type returns a bitmask indicating which SQL 92 functions are supported by the database server. The following bits should not be returned: SQL_SSF_CONVERT SQL_SSF_SUBSTRING SQL_SSF_TRIM_BOTH SQL_SSF_TRIM_LEADING SQL_SSF_TRIM_TRAILING as SQL Anywhere does not support the above SQL 92 functions (e.g., SELECT TRIM(BOTH ' ' FROM ' abc '). Only the following following bits should be returned. SQL_SSF_LOWER SQL_SSF_UPPER This problem has been fixed.

CR:579233

CR Number:   579233 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 2267 03 Jul 2009 Fixed 11.0.0 1641 03 Jul 2009 Fixed Description When using the SQL Anywhere Python database interface (sqlanydb.py) the Cursor.rowcount attribute value was inaccurate under when calling executemany. The rowcount attribute was set to the number of rows affected/returned by the last execute in the series. This has been fixed. The rowcount attribute will now contain the sum of the row counts of the executes (or -1 if unknown). Also, when the server returned an estimated, rather than an exact row count, Cursor.rowcount was set to a negative number, the absolute value of which was the estimate. Cursor.rowcount will now be set to -1 in this case.

CR:579404

CR Number:   579404 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.0 1642 01 Jul 2009 Fixed 11.0.1 2268 01 Jul 2009 Fixed Description If MobiLick Client (dbmlsync) had been running as a server, and a client application had executed the ShutdownServer() method, the exit code from the dbmlsync executable would have been EXIT_FAIL, which indicated a general failure. This would also have resulted in the progress message text changing to "Synchronization Failed" on shutdown, although it was difficult to see on a desktop system. The dbmlsync executable now returns EXIT_OKAY in this situation, which also results in the progress message text changing to "Synchronization Succeeded" on shutdown.

CR:579816

CR Number:   579816 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) 9.0.2 3857 03 Jul 2009 Fixed 10.0.1 3915 03 Jul 2009 Fixed 11.0.0 1640 03 Jul 2009 Fixed 11.0.1 2266 03 Jul 2009 Fixed Description A new connection parameter has been added to the ODBC driver. This parameter (ESCAPE) allows you to specify the escape character used in the LIKE clause of SQL statements generated by the ODBC driver when returning a list of tables or columns. By default the ODBC driver uses the tilde character (~), but some applications do not properly query the ODBC driver to see what escape character is used, and assume that it is the backslash character (\). With this new connection parameter, users can specify the escape character in the connection string to make these applications work properly. "DSN=My Datasource;UID=xxx;PWD=xxx;ESCAPE=\;ENG=myserver"

CR:579826

CR Number:   579826 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 2271 07 Jul 2009 Fixed Description It was possible for an INSERT statement to fail with an inappropriate error "Invalid host variable". This error could have been given if a wide insert was performed on a table, followed by a procedure or batch statement issuing an INSERT to the same table. This has been corrected. The problem can be avoided using "options(force optimization)" on the INSERT statement. Workaround Description  The only work around at this point is to not do a bulk insert.

CR:579837

CR Number:   579837 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2278 07 Jul 2009 Fixed Description The iAnywhere Solutions Oracle ODBC driver could not recognize synonyms of stored procedures. Thus an application, such as the MobiLink server, that uses this driver was not able to execute procedure synonyms if the DSN used by the application was configured with the "Procedure returns results" check box checked. This problem has now been fixed.

CR:579948

CR Number:   579948 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 2303 20 Aug 2009 Fixed Description The system procedure sa_index_density(), could have reported 'Cannot convert' errors. This has been fixed by changing the datatypes of the result set columns "density" and "skew" from numeric(8,6) to double. As a result, the definition of the sa_index_density procedure in the database must be replaced for the fix to take effect. This can be accomplished by executing: ALTER DATABASE UPGRADE PROCEDURE ON A workaround is to rebuild the database prior to running sa_index_density. Re-creating or reorganizing the offending index may also be a workaround.

CR:579981

CR Number:   579981 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 2270 07 Jul 2009 Fixed Description The second argument for the system function get_identity() is the number of values to allocate. If this value was 0, the function did not adjust the next available value for the table. If no inserts into a table defined with a DEFAULT AUTOINCREMENT column had been made, get_identity('<table-name>',0) returned NULL. This has been fixed. A value of 1 will now be returned in this case.

CR:580004

CR Number:   580004 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 2270 07 Jul 2009 Fixed 11.0.0 1645 07 Jul 2009 Fixed 10.0.1 3920 07 Jul 2009 Fixed 9.0.2 3860 07 Jul 2009 Fixed Description When describing arguments of a stored procedure called with non-positional arguments, no information was returned from the server. For example: CREATE PROCEDURE foo ( IN a INTEGER, OUT b INTEGER ) BEGIN SET b = a * 2 END No information was returned when describing input arguments for the statement "call foo( b=?, a=?)". This has been fixed.

CR:580012

CR Number:   580012 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2270 07 Jul 2009 Fixed Description The changes for Engineering case 576257 resulted in a substantial performance improvement within the iAnywhere JDBC driver when fetching a large number of Date, Time or Timestamp values. New changes, which build on these earlier changes, make fetching Date, Time and Timestamp values even faster, when using the iAnywhere JDBC driver.

CR:580016

CR Number:   580016 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2271 08 Jul 2009 Fixed 10.0.1 3921 08 Jul 2009 Fixed Description Unexpected behavior could have occurred when IN predicates were used in subqueries in INSERT, UPDATE, and DELETE statements. This has been corrected.

CR:580057

CR Number:   580057 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2270 07 Jul 2009 Fixed Description Using Sybase Central to triggering an event in a 9.x database, would have produced the error "Procedure 'sa_conn_list' not found" after the event was triggered. This has been fixed.

CR:580133

CR Number:   580133 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2272 14 Jul 2009 Fixed 11.0.0 1647 14 Jul 2009 Fixed Description The OUTPUT USING statement's ability to export results to Excel files has been improved: 1. The CREATE TABLE ON clause is now supported. Previously, consistently creating tables was not possible, although exporting to existing tables worked. 2. If the table name was quoted with backticks, the output operation would have failed. This has been fixed. 3. The OUTPUT statement would not have worked at all if the USING clause contained "driver=" rather than "dsn=". This has been fixed. 4. Exporting a result set which contains primary key columns with the CREATE TABLE ON clause would have failed, as the Excel ODBC driver does not support the required SQL to designate primary keys. This limitation has now been worked around. For datatypes that the OUTPUT statement cannot handle, such as BINARY or LONG BINARY, the user must do the conversion to a supported type explicitly. Note that the Interactive SQL utility in version 10 and earlier did allow exporting BINARY columns, although it simply treated bytes as characters when it wrote them to the Excel file. It's unclear whether that was a "good thing" in general. To emulate that behavior in now, use the following: SELECT ID, Name, Description, Size, Color, Quantity, UnitPrice, CAST(Photo AS LONG VARCHAR ) FROM Products; OUTPUT USING 'DSN=MyEXCELDSN' INTO tabProducts CREATE TABLE ON Also note that the Microsoft Excel ODBC driver treats the file as read-only by default. To write to the file, turn off the "Read only" flag in the DSN or, if not using a DSN, include "ReadOnly=0" as a connection parameter in the OUTPUT statement. For example: SELECT * FROM Departments; OUTPUT USING 'Driver=Microsoft Excel Driver (*.xls); dbq=c:\test\test.xls;ReadOnly=0' INTO Departments CREATE TABLE ON

CR:580146

CR Number:   580146 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 2274 14 Jul 2009 Fixed 11.0.0 1648 14 Jul 2009 Fixed 10.0.1 3925 14 Jul 2009 Fixed Description If an application attempted to drop a user that had externlogins defined, then the server would have given an error indicating that externlogins were defined. The server behaviour has now been changed to quietly drop externlogins as part of dropping a user.

CR:580168

CR Number:   580168 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 2266 07 Jul 2009 Fixed 11.0.0 1640 07 Jul 2009 Fixed 10.0.1 3915 07 Jul 2009 Fixed 9.0.2 3855 07 Jul 2009 Fixed Description When a NUMERIC or DECIMAL column with precision greater than 47 was fetched using OLE DB, ODBC, or JDBC, a memory buffer overrun would have occurred. This would have resulted in a corrupted heap. The client application may then terminate unexpectedly due to the corrupted heap. This problem has been fixed.

CR:580174

CR Number:   580174 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2271 08 Jul 2009 Fixed 11.0.0 1645 08 Jul 2009 Fixed 10.0.1 3921 08 Jul 2009 Fixed Description If an application using the iAnywhere JDBC driver, created a scrollable, updateable Statement or PreparedStatement, created a ResultSet object off of the Statement or PreparedStatement object, called ResultSet.updateRow() to perform a positioned update of a row in the ResultSet, and then positioned the ResultSet to a row before the updated row, attempting to call next() to go beyond the updated row would have failed. A similar problem exists if the application positions the ResultSet beyond the updated row and then tries to call previous(). Both problems have now been fixed.

CR:580186

CR Number:   580186 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 2270 07 Jul 2009 Fixed Description An INSERT statement, with a VALUES clause containing subquery expressions, could have caused acrash. This has been corrected.

CR:580190

CR Number:   580190 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 2272 09 Jul 2009 Fixed 11.0.0 1646 09 Jul 2009 Fixed 10.0.1 3822 09 Jul 2009 Fixed Description If an error had occurred while the MobiLink client (dbmlsync) was applying a download, and there had also been referential integrity errors that dbmlsync could not resolve, then dbmlsync would have reported that the download had been committed, even though it had been rolled back. This has been corrected so that dbmlsync now correctly reports that the download was rolled back.

CR:580191

CR Number:   580191 Product Name:   MobiLink 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 2275 08 Jul 2009 Fixed Description Spacy tokens need to be quoted with double quotes. If the quoted token further contains spacy sub token then nested double quotes are need, and they need to be escaped with escape sequence. This was not working correctly when used in a MobiLink Listener (dblsn) configuration file. For example: -l "subject=$remote_id; content=sync cardealer; action='run dbmlsync.exe -c \"filedsn=c:\my fdsns\CarDealer.dsn\" -ot dbmlsync.log -k -e sa=on';" This works correctly on the command line, because the tokenizer of the commandline processor in the OS supports escaping double quotes using a backslash, but using the same command in a configuration file would have failed. This problem has been fixed by improving the common configuration file parsing routine to support <slash><slash> and <slash><double quote> as escape sequences for <slash> and <double quote> respectively. The escape mechanism is effective only inside a quoted token.

CR:580222

CR Number:   580222 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 2272 09 Jul 2009 Fixed 11.0.0 1646 09 Jul 2009 Fixed 10.0.1 3922 09 Jul 2009 Fixed Description If the MobiLink Server had been started with "-s 1" command line option, to indicate that the server should always apply changes to the consolidated database one row at a time, then the MobiLink Server would still have executed SAVEPOINT commands. SAVEPOINT commands are not needed when running in single row mode, so they are no longer executed when the MobiLink Server had been started with "-s 1".

CR:580353

CR Number:   580353 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2273 13 Jul 2009 Fixed 10.0.1 3924 13 Jul 2009 Fixed Description Queries with TOP or START AT clauses were incorrectly flagged with an error when they exceeded 64K. This restriction has now been removed.

CR:580390

CR Number:   580390 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2273 14 Jul 2009 Fixed 11.0.0 1648 14 Jul 2009 Fixed 10.0.1 3925 14 Jul 2009 Fixed Description If both a BEFORE UPDATE and a BEFORE UPDATE OF trigger were defined on the same table, and the BEFORE UPDATE OF trigger was not the first to fire when an update was performed using INSERT ... ON EXISTING UPDATE, then the BEFORE UPDATE OF trigger would not have fired at all. This has now been fixed. Workaround Description  Flatten the triggers into a simple before update trigger and use if update( ), or (possibly) switch away form on existing and explicitly coding a condition if exists subquery to decide.