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

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

CR:580391

CR Number:   580391 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 2272 13 Jul 2009 Fixed 11.0.0 1747 13 Jul 2009 Fixed Description The fix for Engineering case 529193 was not complete, which meant spurious referential integrity constraint violations could have been reported. This has been corrected.

CR:580538

CR Number:   580538 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 2270 09 Jul 2009 Fixed 11.0.0 1644 09 Jul 2009 Fixed Description When connected to a slow server, immediately doing something to modify the contents of the "SQL Statements" field, would have cause the Interactive SQL utility to crash with the exception "java.lang.IllegalStateException: Attempt to mutate in notification". This has now been fixed.

CR:580569

CR Number:   580569 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 2278 20 Jul 2009 Fixed Description On some Linux systems, if the SQL Anywhere Monitor had been configured as a service to be started automatically after a reboot, monitoring could have failed. Automatic services wwere being installed with a priority "09". Some distributions install the network service with priority "10" and the network service would not have started until after the SQL Anywhere services had started, which led to the failure. This has now been fixed. A workaround to correct this problem is to execute the following commands (requires administrator priviledges): /opt/samonitor11/bin32/samonitor.sh uninstall /opt/samonitor11/bin32/samonitor.sh install

CR:580574

CR Number:   580574 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2267 09 Jul 2009 Fixed 11.0.0 1648 15 Jul 2009 Fixed Description The Apache Redirector is now available for Apache 2.2 on Linux. The new file is named mod_iaredirect.so, and is located in <install-dir>/mobilink/redirector/apache/v22.

CR:580590

CR Number:   580590 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 2267 09 Jul 2009 Fixed Description The SQL Anywhere Python Database interface now supports the ability to register callbacks to control how database types are mapped into Python objects when results are fetched from the database server. Callbacks are registered using the new module-level "register_converter" method. This method should be called with the database type as the first parameter, and the conversion function as the second parameter. For example, to request that sqlanydb.py create Decimal objects for data in any column described as having type DT_DECIMAL: import sqlanydb import decimal def convert_to_decimal(num): return decimal.Decimal(num) sqlanydb.register_converter(sqlanydb.DT_DECIMAL, convert_to_decimal) Converters may be registered for the following database types: DT_DATE DT_TIME DT_TIMESTAMP DT_VARCHAR DT_FIXCHAR DT_LONGVARCHAR DT_STRING DT_DOUBLE DT_FLOAT DT_DECIMAL DT_INT DT_SMALLINT DT_BINARY DT_LONGBINARY DT_TINYINT DT_BIGINT DT_UNSINT DT_UNSSMALLINT DT_UNSBIGINT DT_BIT DT_LONGNVARCHAR

CR:580598

CR Number:   580598 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3922 10 Jul 2009 Fixed 9.0.2 3861 10 Jul 2009 Fixed Description Tools such as the Data Source utility (dbdsn), which need to run as an elevate process to perform privileged operations on Windows Server 2008 R2, failed to do so and would have reported errors when run in an unelevated command shell. This has been fixed.

CR:580599

CR Number:   580599 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2273 10 Jul 2009 Fixed 10.0.1 3924 10 Jul 2009 Fixed 9.0.2 3863 10 Jul 2009 Fixed Description The SQL Anywhere JDBC driver getTimeDateFunctions() call did not return the correct names for the CURRENT_DATE, CURRENT_TIME, and CURRENT_TIMESTAMP functions. It returned "current date,current time,current timestamp" instead of "current_date,current_time,current_timestamp". The same problem also existed in the iAnywhere JDBC driver. These problems have now been fixed.

CR:580607

CR Number:   580607 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 2272 13 Jul 2009 Fixed 11.0.0 1647 13 Jul 2009 Fixed 10.0.1 3923 13 Jul 2009 Fixed Description User Impersonation on IIS caused Win32Exception "Access is denied". This has been fixed.

CR:580636

CR Number:   580636 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 2270 10 Jul 2009 Fixed Description The Relay Server can be started automatically by the first Relay Server Outbound Enabler (RSOE) connection, but the connection may have failed within 1.5 seconds if the Selay Server's configuration file was too big. Thhe Relay Server will eventually have finished starting, but the RSOE would not have attempted to reconnect to the Relay Server. This has been fixed by allowing 15 seconds for the Relay Server to startup before giving up the the RSOE connection. RSOE reconnect attempts will be fixed in a separate issue.

CR:580647

CR Number:   580647 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 2272 10 Jul 2009 Fixed Description Setting a TIME column from a java.util.Date, with only time information filled in, could have failed with the Java 2 Micro Edition (J2ME). This has been corrected.

CR:580735

CR Number:   580735 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2272 13 Jul 2009 Fixed 11.0.0 1654 11 Aug 2009 Fixed Description In rare circumstances, transaction log corruption could have occurred, or the server could have haved assertion 100918 ('Invalid redo log page header'), shortly after restarting a database. The probability of this happening on any given database restart was approximately 1/pagesize (ie. for 4K pages, the probability is approximately 0.0002). The corruption was likely to go undetected, and the assertion was unlikely to fire in most cases. However, sites using Mobilink or SQL Remote would have been alerted to the presence of such corruption by errors occurring during synchronization. This has now been fixed.

CR:580743

CR Number:   580743 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 2272 10 Jul 2009 Fixed 11.0.0 1647 10 Jul 2009 Fixed Description Editing a table on the "Data" tab in Sybase Central, or in the "Results" panel of the Interactive SQL utility, could have left the table locked until the tool disconnected from the database. The table lock could in turn have prevented other operations in Sybase Central from completing (e.g. the Unload Database wizard in the SQL Anywhere plug-in, or the Deploy wizard in the MobiLink plug-in). This has been fixed.

CR:580744

CR Number:   580744 Product Name:   SQL Anywhere Monitor Product Component:   Monitor Migrator Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2271 10 Jul 2009 Fixed Description When applying a software update (EBF), the attempt to migrate data from an old SQL Anywhere Monitor database to a new SQL Anywhere Monitor database could have failed with an "Authentication Error". This has been fixed.

CR:580772

CR Number:   580772 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 2272 13 Jul 2009 Fixed 11.0.0 1647 13 Jul 2009 Fixed 10.0.1 3923 13 Jul 2009 Fixed Description Executing a remote query that involved the use of the ROWID() function, where the table specified to ROWID was a remote table, would very likely have caused the server to crash when the query was processed in partial passthru,. This problem has now been fixed.

CR:580773

CR Number:   580773 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 2273 13 Jul 2009 Fixed 11.0.0 1648 13 Jul 2009 Fixed 10.0.1 3924 13 Jul 2009 Fixed Description The server could have hang in some very rare circumstances, when there was considerable temporary file growth. This has now been fixed. A workaround is to pre-grow the temporary file using the ALTER DBSPACE statement, or to create a DiskSpace event to periodically grow the temporary file.

CR:580788

CR Number:   580788 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 2272 13 Jul 2009 Fixed Description The EBF installers for Linux are now capable of installing FIPS components. To initially install the components, the setup script must be invoked with the -regkey (alias -k) command line option, and be passed a registration key that entitles the installation of the FIPS componenents. e.g., ./setup -k <FIPS registration key> or ./setup -regkey <FIPS registration key> It is not possible to specify the registration key through the EBF Installer UI itself. Subsequent invocations of the EBF install will then update previously installed FIPS components without needing to specify a registration key.

CR:581029

CR Number:   581029 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 2273 14 Jul 2009 Fixed 11.0.0 1648 14 Jul 2009 Fixed 10.0.1 3924 14 Jul 2009 Fixed Description The fix for Engineering case 571029 would have caused the Interactive SQL utility to give an "optional feature not implemented" error when exporting data to Excel. This problem has now been fixed.

CR:581032

CR Number:   581032 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 2272 14 Jul 2009 Fixed Description The result set returned by the system procedure sp_sproc_columns() has been changed to include information about parameter modes. The "column_type" column was previously an integer value and was always 0. Now it is a varchar(5), with values 'IN', 'OUT' or 'INOUT'. Also, for functions, the column_name will be returned as @RETURN_VALUE for the function return value; a row for this value was not previously returned.

CR:581036

CR Number:   581036 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 2272 13 Jul 2009 Fixed 11.0.0 1647 13 Jul 2009 Fixed Description Sybase Central running on Windows systems with the zh_HK locale would have defaulted to zh_CN instead of EN. This occurred because jdk1.6 added a new country code for Hong Kong. The problem hass now been fixed.

CR:581046

CR Number:   581046 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 2278 14 Jul 2009 Fixed Description A procedure with the statement MESSAGE ... FOR CONNECTION ... IMMEDIATE did not contain the IMMEDIATE clause in the stored definition of the procedure. This has been fixed. A workaround is to execute the MESSAGE statement using EXECUTE IMMEDIATE.

CR:581050

CR Number:   581050 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 2320 28 Sep 2009 Fixed Description Under certain circumstance, execution of a MERGE statement could have caused the server to raise assertion 100905 ("Articles on the table use do not match those on the table"). The server will now execute the statement correctly.

CR:581249

CR Number:   581249 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 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 create a proxy table using the CREATE EXISTING TABLE statement, and the remote server specified in the location clause does not exist, then the server may have given a strange syntax error instead of giving the "remote server not found" error. This problem has now been fixed and the proper error will now always get returned.

CR:581269

CR Number:   581269 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2276 21 Jul 2009 Fixed 10.0.1 3928 21 Jul 2009 Fixed Description There were no implementations for the datatypes LONG BINARY and LONG VARCHAR. These have now been added.

CR:581403

CR Number:   581403 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 2269 15 Jul 2009 Fixed 11.0.0 1642 15 Jul 2009 Fixed Description It is now possible to specify the ESCAPE connection parameter in the "Connect" dialog when connecting to SQL Anywhere servers. Note, this new feature is actually available for use with all the graphical administration tools.

CR:581417

CR Number:   581417 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 2274 15 Jul 2009 Fixed 11.0.0 2274 15 Jul 2009 Fixed Description Light weight polling against a secondary MobiLink server that is in a MobiLink server farm, may have failed. This is now fixed.

CR:581426

CR Number:   581426 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2280 28 Jul 2009 Fixed Description When the number of concurrent synchronizations was greater than the maximum number of concurrent active synchronizations specified by the -sm command line option, the MobiLink server would have quietly rejected any synchronization requests without showing any error or warning messages. This has been fixed. The MobiLink server will now issue the following warning message: [10101] Synchronization request from client '?' was rejected where ? is the rejected remote ID. A more complete description of this warning code can be found in the documentation. Workaround Description  None

CR:581454

CR Number:   581454 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 2274 16 Jul 2009 Fixed 11.0.0 1649 16 Jul 2009 Fixed Description The following improvements/fixes have been made related to exporting data from a SQL Anywhere database to Excel files, via the Microsoft Excel ODBC driver: 1. Attempting to export CHAR, LONG VARCHAR, NCHAR, NVARCHAR or LONG NVARCHAR values, would have failed with a message that the type was unsupported. Now, these types are mapped to VARCHAR (the closest type supported by the Excel driver). Note that the Excel ODBC driver only supports text column widths up to 255. Attempting to export longer values, will still get an error message. 2. The driver portion of the OUTPUT USING string had to be specified as "Driver=" or "driver=". Now, that part of the string is treated without respect to case, so "DRIVER=" is also accepted. 3. REAL, FLOAT, and BIGINT values could not have been exported due to limitations in the Excel ODBC driver. These limitations have been worked around. 4. Numbers that were not MONEY or SMALLMONEY were exported as CURRENCY (i.e. they were displayed with a dollar sign in the Excel spreadsheet). Now they are exported as numbers. MONEY and SMALLMONEY are still exported as CURRENCY. 5. The Export Wizard would consistently have failed when exporting to tables it had to create. The error message was "Syntax error in the CREATE TABLE statement". This has been fixed.

CR:581542

CR Number:   581542 Product Name:   SQL Remote for SQL Anywhere Product Component:   Extraction Utility for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2275 20 Jul 2009 Fixed 11.0.0 1650 20 Jul 2009 Fixed 10.0.1 3927 20 Jul 2009 Fixed Description If a database had a schema with a very large number of columnsa, it was possible that when dbxtract was run, that the select statement generated to extract the data from some of the tables would have used an incorrect column order. This would likely have resulted in the rebuild failing, since the data types of the columns in the new database would not match the data that have been extracted from the remote database. The problem has now been fixed. Note that this problem only affected dbxtract, and not dbunload.

CR:581580

CR Number:   581580 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) 12.0.0 1912 28 Jan 2010 Fixed 11.0.1 2383 28 Jan 2010 Fixed Description The server may have crashed if a Transact SQL SELECT INTO statement referenced an OPENSTRING expression. This has been fixed.

CR:581586

CR Number:   581586 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 2275 16 Jul 2009 Fixed 11.0.0 1649 16 Jul 2009 Fixed 10.0.1 3926 16 Jul 2009 Fixed Description If the -dt server command line option was used to specify a directory where temporary files were to be created, the server did not use that location when attempting to clean up old temporary files previously left behind when a server did not shut down cleanly. This has been fixed. A workaround is to specify the temporary file location using one of the SATMP, TMP, TMPDIR or TEMP environment variables. Workaround Description  set SATMP or one of the various TEMP environs.

CR:581613

CR Number:   581613 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2275 17 Jul 2009 Fixed Description When deploying a Synchronization Model that added a timestamp column to a MySQL consolidated table for timestamp-based downloads, existing rows would never have been downloaded because of MySQL bug #17392. This bug caused the new timestamp column to have values of 0, instead of the column default. A would around for this problem has been implemented. An UPDATE statement is now generated to follow the generated ALTER TABLE statement that adds the timestamp row. A manual workaround is to update the timestamp column for each row where it is zero, after the column is added.

CR:581622

CR Number:   581622 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 2274 17 Jul 2009 Fixed 11.0.0 1649 17 Jul 2009 Fixed Description If multiple Java classes, or external environment objects, were selected in the right pane and File -> Print... was select from the menu, then multiple Print dialogs would have been shown. Now a single Print dialog is shown.

CR:581709

CR Number:   581709 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 2319 23 Sep 2009 Fixed Description During optimization process, the SQL Anywhere Optimizer optimizes subqueries by considering different alternative strategies for computing the result of the subquery. During othis process, the optimizer doesn't perform any transformations which correspond to each alternative subquery strategies. Instead, the estimated costs of different strategies are used to decide which execution technique will be executed for this SQL statement in the final access plan. The final best access plan is built to reflect the execution strategy chosen for the subquery. In certain cases, when WINDOW subquery strategy was chosen (see Strategy 4 and Strategy 5 below) the final best access plan was missing the rowid expression of the table pushed into the derived table (in the example below, the rowid of the table "sales_order_items soi" from the main query block). This has been fixed. For example: The subquery optimization process supported by the SQL Anywhere Optimizer since version 9.0, is described in the patent [1]. The example below illustrates the five execution strategies considered during the optimization process for a SQL statement using a grouped subquery. This issue is related to a bug introduced in version 10.0.0 when two rowids must be built for each base table to support Snapshot isolation. The bug would have manifest itself if and only if Window Strategy 4 or Window Strategy 5 was chosen in the best access plan. [1] System and Methodology for Cost-based Subquery Optimization Using a Left Deep Tree Join Enumeration Algorithm", Anisoara Nica, US Patent 20040220923, awarded August 2009 Original query Q0: SELECT so.id, so.order_date, p.* FROM sales_order so, sales_order_items soi, product p WHERE so.id = soi.id AND soi.prod_id = p.id AND p.quantity = (SELECT max(soi1.quantity) FROM sales_order_items soi1 WHERE soi1.prod_id = p.id ) SQL Anywhere Optimizer subquery execution strategy 1, Q1, evaluate subquery as an expression: SELECT so.id, so.order_date, p.* FROM sales_order so, sales_order_items soi, product p WHERE so.id = soi.id AND soi.prod_id = p.id AND p.quantity = (SELECT max(soi1.quantity) FROM sales_order_items soi1 WHERE soi1.prod_id = p.id ) SQL Anywhere Optimizer subquery execution strategy 2, Q2, evaluate subquery as an uncorrelated derived table: SELECT so.id, so.order_date, p.* FROM sales_order so, sales_order_items soi, product p, (SELECT max(soi1.quantity), soi1.prod_id FROM sales_order_items soi1 GROUP BY soi1.prod_id ) as DT2 (max, prod_id) WHERE so.id = soi.id AND soi.prod_id = p.id AND p.quantity = DT2.max AND p.id = DT2.prod_id SQL Anywhere Optimizer subquery execution strategy 3, Q3, evaluate subquery as a derived table with Bloom-filter predicates: SELECT so.id, so.order_date, p.* FROM sales_order so, sales_order_items soi, product p, (SELECT max(soi1.quantity), soi1.prod_id FROM sales_order_items soi1 WHERE soi1.prod_id IN Bloom-filter( p.id) GROUP BY soi1.prod_id ) as DT3 (max, prod_id) WHERE so.id = soi.id AND soi.prod_id = p.id AND p.quantity = DT3.max AND p.id = DT3.prod_id SQL Anywhere Optimizer subquery execution strategy 4, Q4, evaluate subquery as an uncorrelated derived table with WINDOW functions: SELECT so.id, so.order_date, p.* FROM sales_order so, product p, //// <<-- NOTE that "sales_order_items soi" was moved inside to the DT4 (SELECT max(soi1.quantity) OVER (PARTITION BY soi1.prod_id ), soi1.prod_id, soi1.id FROM sales_order_items soi1 ) as DT4 (max, prod_id, id) WHERE so.id = DT4.id AND DT4.prod_id = p.id AND p.quantity = DT4.max AND p.id = DT4.prod_id SQL Anywhere Optimizer subquery execution strategy 5, Q5, evaluate subquery as a derived table with WINDOW functions, with Bloom-filter predicates: SELECT so.id, so.order_date, p.* FROM sales_order so, product p, //// <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<------------------------------------------NOTE that "sales_order_items soi" was moved inside to the DT5 (SELECT max(soi1.quantity) OVER (PARTITION BY soi1.prod_id ), soi1.prod_id, soi1.id WHERE soi1.prod_id IN Bloom-filter( p.id) FROM sales_order_items soi1 ) as DT5 (max, prod_id, id) WHERE so.id = DT5.id AND DT5.prod_id = p.id AND p.quantity = DT5.max AND p.id = DT5.prod_id

CR:581747

CR Number:   581747 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 2314 14 Sep 2009 Fixed Description If a statement of the form "SELECT columns FROM table WHERE index_col = value" was opened more than once by a connection, an OPEN or CLOSE request could have failed with one of the following errors: "Cursor already open", "Cursor has not been declared", or "Cursor not open". The statement must have only involved one table, and the where clause must have had one or more predicates of the form col = value which can all be satisfied by one index. This has been fixed.

CR:581752

CR Number:   581752 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 2275 17 Jul 2009 Fixed 11.0.0 1650 17 Jul 2009 Fixed 10.0.1 3927 17 Jul 2009 Fixed Description If the mirror server in a mirroring system failed to start (e.g. due to a TCPIP port conflict), it could have crashed when shutting down. This has been fixed.

CR:581755

CR Number:   581755 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2275 20 Jul 2009 Fixed Description An undocumented feature could have prevented a MobiLink server from starting when multiple MobiLink servers were trying to start at the same time, against the same consolidated database. The error displayed would have been: <main> [-10002] Consolidated database server or ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Primary key for table 'ml_property' is not unique: Primary key value("'ML','server_info','release_version''") (ODBC State = 23000, Native error code = -193) when the consolidated database was running on a SQL Anywhere server. This problem has now been fixed.

CR:581768

CR Number:   581768 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 2275 20 Jul 2009 Fixed Description If the SQL Anywhere Monitor could not send an email alert, a generic "Email server for alerts not configured" alert was raised. This alert has been replaced by a new "Could not send email" alert which includes more descriptive error messages. This was done in an effort to provide more clues for diagnosing issues with email alerts.

CR:581793

CR Number:   581793 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 2275 20 Jul 2009 Fixed 11.0.0 1650 20 Jul 2009 Fixed 10.0.1 3927 20 Jul 2009 Fixed 9.0.2 3865 20 Jul 2009 Fixed Description If a SQL_NUMERIC or SQL_DECIMAL value had a precision sufficiently greater than the bound precision, then an internal buffer would have been overrun. For example, if a bound column was defined as DECIMAL(10,2), and the precision described by the input SQL_NUMERIC_STRUCT parameter value was 40, then an internal buffer would have been overrun. This problem has been fixed.

CR:581829

CR Number:   581829 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 2276 20 Jul 2009 Fixed 11.0.0 1650 20 Jul 2009 Fixed Description The MobiLink Listener (dblsn)would have failed to query an optimal polling interval from secondary MobiLink servers, as the primary notifier was not broadcasting the polling interval to secondary servers. This affected a light weight poller dblsn, but not application using the light weight poller API directly. This has now been corrected.

CR:581830

CR Number:   581830 Product Name:   UltraLite Product Component:   UltraLite for M-Business Anywhere Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2276 21 Jul 2009 Fixed 10.0.1 3946 21 Jul 2009 Fixed Description The implementations of CreationParms::AddRef and CreationParms::Release, contained confusing casting. Both methods cast the POD object to a ConnectionParms object, which has now been fixed.

CR:581957

CR Number:   581957 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 2278 22 Jul 2009 Fixed Description The database option, divide_by_zero_erro, was removed in version 11.0.0. It has now been re-instated. The default setting for the option is On (as it was in version 10), which gives the same behavior as before this change, i.e. an attempt to cause division by zero results in an error.

CR:581958

CR Number:   581958 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 2276 21 Jul 2009 Fixed Description When monitoring several resources, there was a chance that the SQL Anywhere Monitor could have failed with an 'Out of Memory' Exception. The frequency of this error was dependent on the machine the SQL Anywhere Monitor is running. Also, Linux machines would have seen this error slightly more often than Windows machines. This has now been fixed.

CR:581979

CR Number:   581979 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 2277 22 Jul 2009 Fixed 11.0.0 1651 22 Jul 2009 Fixed Description Retrieving property('Platform') on a system running Windows 2008 R2 RC3, would have returned "Windows7". This has been fixed, the property now returns "Windows2008R2".

CR:581980

CR Number:   581980 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 2277 22 Jul 2009 Fixed 11.0.0 1651 22 Jul 2009 Fixed 10.0.1 3928 22 Jul 2009 Fixed Description If an application executed a statement of the form: SELECT ... INTO LOCAL TEMPORARY TABLE localtemptab FROM extenv_proc() where extenv_proc() was an external environment procedure that returned a result set, then the SELECT ... INTO statement would have succeeded, but attempting to subsequently access the newly created localtemptab would have resulted in a 'table not found' error. This problem has now been fixed.

CR:581986

CR Number:   581986 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 2280 29 Jul 2009 Fixed 10.0.1 3934 29 Jul 2009 Fixed Description Executing certain illegal operations on catalog tables could have caused the server to crash after the statement was rejected with an appropriate error. This has been fixed so that the server now works correctly.

CR:581990

CR Number:   581990 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) 21 Jul 2009 Fixed Description The ODBC function SQLTables() can be used to get a list of all schemas (users) by calling the function with the SQL_ALL_SCHEMAS argument. The list of users returned by this function only included users that owned a table. In a newly initialized database, this excluded some users, and in particular the DBA user. Now the complete list of schemas is returned, including those that do not own a table.

CR:581991

CR Number:   581991 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3930 23 Jul 2009 Fixed 9.0.2 3867 23 Jul 2009 Fixed Description In some cases it was possible for a database to become corrupted if the last write to disk was only partial completed, due to a power loss before the write to disk finished. This would have been extremely rare on a desktop machine or laptop using a conventional disk, but would have been much more likely with flash memory on handheld devices. In either case, corruption was more likely if the database file was encrypted. In order to prevent this corruption it is necessary to change the physical format of the database file. With this change in file format, the database should automatically recover from a partial write. WARNING: When choosing to use a database with the new file format described below you give up the ability of being able to use older software that is not aware of the file format change. Therefore, once you create this database you will not be able to start an old server with such a database file. Any attempt to start the server with a build prior to this fix will generate an error "server must be upgraded to start 'database' ( capability 37 missing)". Syntax has been added to dbinit and the create database statement to allow for the creation of databases with this new file format. In order to create a database with this new format, use either: - dbinit -xw mydb.db // -xw (creates a database with the new file format) - CREATE DATABASE mydb.db CAPABILITY 'TORNWRITEFIX' ... Syntax has also been added to dbunload to rebuild databases so that the new database will be created with the new file format. In order to rebuild a database with the old format to one with the new format use: - dbunload.exe -c 'your connection string to your old db' -xw -ar // this will replace your old database with a new one - dbunload.exe -c 'your connection string to your old db' -xw -an new.db // this will create new.db in the new file format while maintaining your old database in the old file format NOTE: make sure to have a backup of your database file before attempting this. Also if your database is strongly encrypted then you'll need to provide the encryption key for both the old database and the new database file using the -ek command line parameter. In order to upgrade a database with this new file format from version 9 to version 10 or version 11 you'll need to use 10.0.1 3930 or greater or 11.0.1 2278 or greater.

CR:582144

CR Number:   582144 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 2276 21 Jul 2009 Fixed Description There were no implementations for the datatypes LONG BINARY and LONG VARCHAR. These have now been added.

CR:582152

CR Number:   582152 Product Name:   UltraLite Product Component:   SQL Preprocessor Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2278 22 Jul 2009 Fixed Description When using the the SQL Preprocessor (sqlpp) command line tool to generate code for UltraLite, the -eu command line option was supposed to flag SQL that UltraLite cannot handle. When this option was on, the following UltraLite-supported statements would have been incorrectly flagged as Disallowed language extensions: CREATE SYNCHRONIZATION PROFILE ... ALTER SYNCHRONIZATION PROFILE ... DROP SYNCHRONIZATION PROFILE ... SYNCHRONIZE ... This has been corrected. The workaround is to not use the -eu command line option on SQLPP.

CR:582186

CR Number:   582186 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 2278 22 Jul 2009 Fixed 11.0.0 1651 22 Jul 2009 Fixed Description The "View Data in Interactive SQL" menu item was not always enabled or disabled appropriately. Specifically, for views owned by SYS, the menu item was disabled, rather than enabled; for invalid, disabled and uninitialized views, the menu item was enabled, rather than disabled. Now, the menu item is only enabled for non-materialized views which are valid, and materialized views which are both enabled and initialized.

CR:582405

CR Number:   582405 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 2278 24 Jul 2009 Fixed 12.0.0 2418 05 May 2010 Fixed Description When processing a simple query that bypassed the query optimizer, in some cases it was possible for the server to crash if. This may have occurred when the query contained the SELECT TOP n clause, and 'n' was was a host variable, rather than a literal constant. This problem has now been corrected.

CR:582589

CR Number:   582589 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2278 24 Jul 2009 Fixed 11.0.0 1652 24 Jul 2009 Fixed 10.0.1 3930 24 Jul 2009 Fixed Description If 10 MobiLink Monitors or SQL Anywhere Monitors connected to the same MobiLink server, and the last to connect then disconnected, then the MobiLink server could have crashed. This has been fixed.

CR:582756

CR Number:   582756 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 2279 28 Jul 2009 Fixed 10.0.1 3932 28 Jul 2009 Fixed 9.0.2 3868 28 Jul 2009 Fixed Description The changes for Engineering case 544187 caused the server to have a limited number of temporary files that it could create in the lifetime of the server process (64K on non-UNIX systems, 4G on UNIX systems). The problem would have shown up as an error writing to an invalid handle, and a fatal "disk full" error would have been reported. On Windows, the message in the server console would have looked like the following: A write failed with error code: (6), The handle is invalid. Fatal error: disk full when writing to "???" This problem has been fixed. A related problem was also fixed where failure to create a temporary file for the utility_db would have cause the server to crash.

CR:582778

CR Number:   582778 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 2323 29 Sep 2009 Fixed Description Calling the system procedure sa_get_histogram(), which is used to obtain the current state of a histogram on a specified column, could have caused the server to deadlock. The probability of such a deadlock taking place was extremely low and depended upon a number of factors. This problem has now been resolved.

CR:582782

CR Number:   582782 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2279 24 Jul 2009 Fixed 11.0.0 1652 24 Jul 2009 Fixed 10.0.1 3931 24 Jul 2009 Fixed 9.0.2 3868 24 Jul 2009 Fixed Description When a consolidated database was running on an Oracle RAC, the MobiLink server could have skipped rows being downloaded to remote databases in a time-based download. In the following situations, rows modified in the Oracle database could be missed from the download stream: 1) the MobiLink server connected to one node on an Oracle RAC; 2) another application, A connected to another node on the same Oracle RAC; 3) application A modifies rows in a synchronization table without commit; 4) a MobiLink client, R1 issues a synchronization request that contains a time-based download from this table; 5) the MobiLink server completes the synchronization request successfully; 6) A commits its transaction; Then the rows modified by application A would not be down loaded to remote R1. This problem has now been fixed. Note, as a result of this change, the Oracle account used by the MobiLink server must now have permission for the GV_$TRANSACTION Oracle system view instead of V_$TRANSACTION. Only SYS can grant this access. The Oracle syntax for granting this access is: grant select on SYS.GV_$TRANSACTION to <user-name>

CR:582789

CR Number:   582789 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 2280 28 Jul 2009 Fixed 11.0.0 1652 28 Jul 2009 Fixed Description The MobiLink server would still have tried to access the ml_scripts_modified table in the consolidated database, even when it was running with MSDTC on and its system objects were installed on an MLSD database specified by the -cs command line switch. This would then have resulted in the MobiLink server reporting the error message: Table "ml_scripts_modified" not found during each synchronization, when a pooled database connection was reused.This problem has now been fixed.

CR:582799

CR Number:   582799 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 2279 24 Jul 2009 Fixed Description The server could have crashed during a LOAD TABLE statement if the DEFAULTS ON clause was used, and a load-time error occurred when evaluating or assigning the default expression. This has been fixed. The workaround is to fix the column default definition so that no error occurs.

CR:582808

CR Number:   582808 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.1 2279 27 Jul 2009 Fixed Description The Apply button on a property sheet could have become enabled even when no changes had been made on the property sheet. For this to have occurred, the property sheet had to contain a formatted text field or spinner control. This is now fixed.

CR:583189

CR Number:   583189 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2281 30 Jul 2009 Fixed Description The server could have crashed in some circumstances after a table definition was reloaded. This has been fixed.

CR:583194

CR Number:   583194 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 2282 05 Aug 2009 Fixed Description The QAnywhere Standalone Clients were not adhering to the synchronization policies as they are defined in the documentation. In several scenarios, the clients would trigger synchronizations even though the policy requirements were not satisfied, although it was never the case that a synchronizations didn't occur when one should have. This has been fixed so that the clients now synchronize only at the appropriate times as defined by the policies.

CR:583241

CR Number:   583241 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2295 10 Aug 2009 Fixed 10.0.1 3940 10 Aug 2009 Fixed Description Under some specific circumstances, the server could have crashed while updating tables with triggers. This has been fixed so that execution of UPDATEs now takes place correctly. A workaround is to recreate the table under question.

CR:583353

CR Number:   583353 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2295 10 Aug 2009 Fixed Description The version of samonitor.sh included with the development version of the SQL Anywhere Monitor on Unix platforms provided a start() method to spawn the database server, but did not provide a stop() method to shut it down. This has been fixed. Note: if the desktop environment has a system tray supported by Java 1.6, it is possible to shut down the server monitor cleanly by right clicking on the SQL Anywhere Monitor logo and choosing "Shutdown"

CR:583380

CR Number:   583380 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 2306 04 Aug 2009 Fixed 9.0.2 3882 04 Aug 2009 Fixed Description The server may have returned the error "-890: Statement size or complexity exceeds server limits", or needed a very long time to complete, for very complex statements that used proxy tables and alias names that depend on many other alias names. During the Describe Output or Open of the statement, the server may have consumed a large amount of cache space and blocked other requests. This has been fixed.

CR:583393

CR Number:   583393 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 2281 30 Jul 2009 Fixed Description When right-clicking the SA Monitor tray icon and selecting "Exit SQL Anywhere Monitor", nothing would happen. This problem has now been fixed, and the SQL Anywhere Monitor now shuts down as expected. This problem was introduced by the changes for Engineering case 575525.

CR:583560

CR Number:   583560 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 2335 22 Oct 2009 Fixed 10.0.1 3978 22 Oct 2009 Fixed Description If an application that was connected to a local server, either via the SQL Anywhere ODBC driver or the iAnywhere JDBC driver, attempted to perform a wide or batched insert into a proxy table and the insert subsequently returned with a conversion or some other error part-way through the insert, then the rows leading up to the error would have been inserted into the proxy table twice. This problem has now been fixed.

CR:584125

CR Number:   584125 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 2298 06 Aug 2009 Fixed 11.0.0 1654 06 Aug 2009 Fixed 10.0.1 3944 06 Aug 2009 Fixed Description Specifying an IPv6 address with a port number for the HOST option, eg. LINKS=tcpip(host=(<ipv6 address>):<port>) would give an SQLE_CONNECTION_ERROR (-832) with the text "Unexpected error 10" or "Mismatched braces near '???'". This only happened when parentheses were used for both the TCP parameter and the HOST option. This has been fixed. As a workaround, use braces to specify the TCP options, eg. LINKS=tcpip{host=(<ipv6 address>):<port>}".

CR:584152

CR Number:   584152 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 2295 11 Aug 2009 Fixed 10.0.1 3941 11 Aug 2009 Fixed Description A statement-level "after update of" trigger would not have fired if the columns in the "of" list were modified by another trigger, but were not present in the set clause of the originating query. This has been fixed. Note, row level triggers do not have this problem.

CR:584304

CR Number:   584304 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 2287 06 Aug 2009 Fixed 10.0.1 3939 06 Aug 2009 Fixed Description If an application executed an external environment procedure and subsequently canceled the external call, then all other external environment requests would have blocked until the external procedure being cancelled acknowledged the cancel request. This problem has now been fixed.

CR:584310

CR Number:   584310 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2288 05 Aug 2009 Fixed 10.0.1 3939 05 Aug 2009 Fixed Description Download performance of the MobiLink server has been improved for tables that contain no BLOB columns, when the consolidated database is running on Microsoft SQL Server.

CR:584322

CR Number:   584322 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 2138 05 Aug 2009 Fixed Description The following new features have been added to the iAnywhere Solutions ODBC driver for Oracle: 1) In order to determine if a stored procedure returns a result set, or if a procedure uses Oracle VARRAYs, the iAnywhere Solutions Oracle ODBC driver needs to describe the stored procedure through Oracle OCI functions. The driver now provides an extra connection parameter, ProcOwner (long form) or POwner (short form), which is used to by tyen driver to describe all the stored procedures invoked by the application. This parameter can be given as followis: -c "uid=...;pwd=...;procowner=my_procedure_owner;..." 2) The iAnywhere Solutions ODBC driver for Oracle now supports VARRAYs used by packaged procedures.

CR:584327

CR Number:   584327 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 2288 06 Aug 2009 Fixed Description In some very rare cases, the SQL Anywhere Monitor could have caused a Java process to consume 100% of the CPU. This has been fixed.

CR:584466

CR Number:   584466 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 2290 06 Aug 2009 Fixed Description The server was only looking at the groups that a user was a direct member of when verifying authorities acquired via group inheritance. This has been corrected so that the server now checks for inheritable authorities through all group memberships, direct and indirect. For example, if 'group1' is a member of 'group2' and 'user1' is member of 'group1', 'user1' will obtain all inheritable authorities of group2 also.

CR:584478

CR Number:   584478 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 2309 07 Aug 2009 Fixed Description BlackBerry devices with OS 4.2 or later, may now read and write UltraLiteJ databases to either the internal flash or the SD (media) Card, in addition to the previously supported persistent store. While the persistent object store of BlackBerry devices is faster, it has limited capacity and is shared with RAM and program storage. Newer devices such as the Bold, Storm and Tour have internal flash (Bold and Storm have almost 1GB) and many devices support SD Cards. Persistent store is 3-4 times faster than internal flash, and internal flash is faster than SD cards. Databases stored on internal flash (URIs begining with "file:///store/") or media cards ("file:///SDCard/") can keep more rows in memory, and/or use a bigger cache to improve performance. Databases names must follow the format for a fully qualified, absolute path file name as described in the file URL format as part of IETF RFCs 1738 and 2396. That RFC dictates that a file URL takes the form: file://<host>/<path> In the form above, <host> is the fully qualified domain name of the system on which the <path> is accessible, and <path> is a hierarchical directory path of the form: <root>/<directory>/<directory>/.../<name>. For BlackBerry devices, the internal flash is accessed using URIs starting with file:///store/ (case sensitive) while the SD media card is accessed using URIs starting with file:///SDCard/ (case sensitive). File paths are case insensitive except for the host portion which is case sensitive. Percent (%) characters have special meaning and relative paths (directories "." and "..") are not allowed. For more information on file name restrictions, please consult the BlackBerry JDE (4.2 or later) API Reference for the javax.microedition.io.file package. The following example creates a configuration for using the media card. The database is store in the directory "ulj" and is called "test.ulj". // BlackBerry media card Sample - use file:///store/ulj/test.ulj // for internal flash Connection conn; ConfigFileME config = DatabaseManager.createConfigurationFileME( "file:///SDCard/ulj/test.ulj" ); try { conn = DatabaseManager.connect(config); } catch(ULjException ex) { conn = DatabaseManager.createDatabase(config); // Create the schema here. } To maintain support for BlackBerry 4.1 devices, a new distribution directory UltraLite\UltraLiteJ\BlackBerry4.2 has been added which contains files for 4.2 or later devices. BlackBerry 4.1 devices and simulators should continue to use the UltraLite\UltraLiteJ\J2meRIM11files. BlackBerry 4.2 and later devices can use either distribution if they do not require SD card or internal flash storage. The UltraLiteJ Database Transfer tool has not been updated.

CR:584486

CR Number:   584486 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 2314 15 Sep 2009 Fixed Description Unloading a SELECT statement into a compressed variable could have caused a server crash. This has been fixed.

CR:584512

CR Number:   584512 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 2291 07 Aug 2009 Fixed 10.0.1 3939 07 Aug 2009 Fixed Description When validating databases, using the VALIDATE DATABASE statement or the Validation utility 'dbvalid -d'), spurious errors could have been reported under rare circumstances. This has been fixed.

CR:584517

CR Number:   584517 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 2291 10 Aug 2009 Fixed 10.0.1 3939 10 Aug 2009 Fixed Description When validating a database, either using the VALIDATE DATABASE statement, or with the Validate utility (dbvalid -d), an error would not have been reported if a transaction log page was encountered in the database file. This has been fixed. Note, this situation would have been due to file corruption on the disk. Transaction log pages are not stored within the database.

CR:584691

CR Number:   584691 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2286 07 Aug 2009 Fixed Description A new "IF NOT EXISTS" clause can now be optionally specified in CREATE TABLE, CREATE INDEX, and CREATE PUBLICATION statements. If this clause is present, and the object named in the statement already exists, then executing the statement will not modify the database and no error will be returned. The complete syntax for the new clause in the various statements are: - CREATE TABLE [IF NOT EXISTS] table-name (...) - CREATE [UNIQUE] INDEX [IF NOT EXISTS] index-name ... - CREATE PUBLICATION [IF NOT EXISTS] publication-name ...

CR:584721

CR Number:   584721 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2291 10 Aug 2009 Fixed 11.0.0 1654 10 Aug 2009 Fixed 10.0.1 3939 10 Aug 2009 Fixed Description When using the SQL Anywhere C API, no error information was returned when a connection attempt failed. This problem was introduced as part of a previous fix to dbcapi, and has now been corrected.

CR:584722

CR Number:   584722 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 2293 10 Aug 2009 Fixed Description When installing EBFs on Unix systems, the installer would not have applied the updates if the destination directory included spaces. This has been fixed.

CR:584873

CR Number:   584873 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Windows CE 2.11 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2297 17 Aug 2009 Fixed Description If the QAnywhere Agent for Ultralite was running using the automatic policy, and a message was sent during a loss of communication with the QAnywhere server, then the message would not have been sent upon re-establishing communication. This has now been fixed so that and unsent messages will be sent shortly after that connection is re-established. A workaround for this problem is to perform an action that will trigger a synchronization (eg. send another message, call triggerSendReceive, etc.)

CR:585013

CR Number:   585013 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2296 11 Aug 2009 Fixed 10.0.1 3942 11 Aug 2009 Fixed Description If an application executed Connection.prepareStatement(), or Connection.prepareCall(), on one connection, and the prepare request took a long time, then attempting to execute Connection.createStatement(), Connection.prepareStatement(), or Connection.prepareCall() on a different connection would have ended up blocking until the original prepare returned. This problem has now been fixed.

CR:585015

CR Number:   585015 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) 12.0.0 2089 27 Nov 2009 Fixed 11.0.1 2357 27 Nov 2009 Fixed Description Exporting numeric values to an Excel spreadsheet would have failed when running the Interactive SQL utility on Windows systems which were configured to use something other than a period for the decimal separator in numbers. This has been fixed. Also, it is now possible to consistently export TIME, DATE, and TIMESTAMP values to Excel spreadsheets.

CR:585018

CR Number:   585018 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2296 11 Aug 2009 Fixed Description Calling the function SetParameter(), could have caused the UltraLite runtime to crash when the database had no base tables. This has been fixed.

CR:585024

CR Number:   585024 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 2296 11 Aug 2009 Fixed Description When inserting or updating a row using a table on the "Result" tab, values read from a file were silently truncated at 1,000,000 characters. This limitation has been removed. Note, this bug affected both the Interactive SQL utility, and the "Data" tab in Sybase Central.

CR:585030

CR Number:   585030 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Aug 2009 Fixed Description The "C" and "P" command line options for SQLPP cause the flagging of SQL syntax during precompilation. The use of "C" is to verify conformance to the core language features of a particular SQL standard, and "P" is to verify conformance to the complete ANSI language, as supported by SQL Anywhere, including optional packages. However, the use of "P" erroneously reported conformance for core language features only, duplicating the output generated by the use of "C". This has been fixed. Using "P" now reports language conformance, including optional ANSI standard packages, as described in the documentation.

CR:585035

CR Number:   585035 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2307 28 Aug 2009 Fixed 9.0.2 3882 28 Aug 2009 Fixed 10.0.1 3952 08 Sep 2009 Fixed Description The QAnywhere server could have stopped sending/receiving messages with an Enterprise Messaging Server, through its JMS connector, when a SQLException was thrown by the JDBC driver. This has been fixed. Where possible, the QAnywhere server should recover gracefully from exceptions thrown by the JDBC driver and continue processing messages.

CR:585046

CR Number:   585046 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 2297 13 Aug 2009 Fixed Description Consider an UltraLite database with a table as follows: CREATE TABLE tbl1(a INTEGER, PRIMARY KEY (a)) INSERT INTO tbl1 VALUES (10000000) Fetching the results using the Interactive SQL utility (dbisql) in command-line mode as follows: dbisql -ul -c "uid=dba;pwd=sql;dbf=c:\temp\test.udb" select a from tbl1 would have returned the value 1000. The value was truncated in the display, and was only an issue when displaying the results to the command shell. This is now fixed.

CR:585056

CR Number:   585056 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2296 14 Aug 2009 Fixed Description If the database option Escape_character was set to OFF, attempting to change a user's password via the NEWPWD connection string parameter would have failed silently. This has been fixed. A workaround is to leave the escape_character setting at its default (ON).

CR:585077

CR Number:   585077 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2296 12 Aug 2009 Fixed Description The Database Transfer utility would have failed to transfer some databases. After establishing the connection, the utility would have immediately finished the transfer, and the progress bar on the client would still have indicated 0%. The log on the desktop utility would have shown a negative value for chunks of data expected. This has been fixed.

CR:585258

CR Number:   585258 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2296 13 Aug 2009 Fixed 10.0.1 3943 13 Aug 2009 Fixed Description The MobiLink server would not have shown any script contents, if the scripts were written in Java or .NET, even when the verbose option (-vc) was specified in its command line. This problem is fixed now.

CR:585282

CR Number:   585282 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2296 14 Aug 2009 Fixed 10.0.1 3943 14 Aug 2009 Fixed Description If an application connected via Open Client or jConnect, and requested a packet size greater than 512 bytes, the SQL Anywhere server would have restricted the packet size to a maximum of 512 bytes. This restriction has now been relaxed such that the maximum Open Client or jConnect packet size is now 4096 bytes for a version 11.0.1 or above server, and 1024 bytes for a version 10.0.1 server.

CR:585306

CR Number:   585306 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 2297 17 Aug 2009 Fixed Description Reading a blob (long binary) value from the database would have taken 7 times longer than it did to write the blob (as tested on a BlackBerry Bold). This has been fixed.

CR:585456

CR Number:   585456 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2297 13 Aug 2009 Fixed 10.0.1 3943 13 Aug 2009 Fixed Description The queue lengths in the Utilization Graph of the MobiLink Monitor could have been incorrect and the RAW_TCP_STAGE_LEN, STREAM_STAGE_LEN, HEARTBEAT_STAGE_LEN, CMD_PROCESSOR_STAGE_LEN metrics printed by the -ppv option could also have been incorrect. These issues have now been corrected.

CR:585530

CR Number:   585530 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 2297 14 Aug 2009 Fixed Description The changes for Engineering case 568426 broke the Table and View permissions grid support for 9.x databases. This has now been fixed.

CR:585713

CR Number:   585713 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 2297 17 Aug 2009 Fixed 10.0.1 3944 17 Aug 2009 Fixed Description Under rare circumstances, the server may have hung when run on Solaris systems. This was more likely to have occurred on machines with greater parallelism (e.g., Niagara chips) under a highly concurrent load. This has been fixed.

CR:585735

CR Number:   585735 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 2297 17 Aug 2009 Fixed Description For some queries, a result set row could have indicated that a column value was not null, even if the value is null. Retrieving this value could then have returned misleading, or invalid data. This has now been fixed.

CR:585979

CR Number:   585979 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 2301 17 Aug 2009 Fixed 11.0.0 1654 17 Aug 2009 Fixed 10.0.1 3945 17 Aug 2009 Fixed 9.0.2 3878 17 Aug 2009 Fixed Description Using the BCP utility to insert data into a table could have failed with a protocol error, if the version of Open Client that BCP used was older. This problem has now been fixed.

CR:586180

CR Number:   586180 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2306 26 Aug 2009 Fixed 10.0.1 3950 26 Aug 2009 Fixed Description Under certain circumstances, the server could have failed an assertion, or crashed, while processing queries containing large strings. This has been fixed.

CR:586188

CR Number:   586188 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 2302 18 Aug 2009 Fixed Description Opening the Events folder could have caused a "Can't decode condition name" error if an event was created via Interactive SQL utility, instead of via Sybase Central. This has been fixed.

CR:586217

CR Number:   586217 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2302 19 Aug 2009 Fixed 11.0.0 1654 19 Aug 2009 Fixed 10.0.1 3946 19 Aug 2009 Fixed Description Methods in the SADataReader clase could have returned an incorrect fraction for datetime and time columns. This has now been corrected.