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

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

CR:592670

CR Number:   592670 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 2325 01 Oct 2009 Fixed Description A connection failure could have occurred following an application crash. This would have occurred when there was an active temporary table and a commit or rollback had been executed following the first fetch using the temporary table. This has been corrected.

CR:592728

CR Number:   592728 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 2325 01 Oct 2009 Fixed Description The list of TCP/IP protocol options in the Connect dialog was incorrect. The list should not have contained the options 'TDS' or 'BroadcastListener', and the option 'SendBufferSize' was missing. These have been fixed. Note, these issues affected the Connect dialog when connecting to SQL Anywhere, regardless of which program was being used -- DBISQL, Sybase Central, or DBConsole.

CR:592784

CR Number:   592784 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2325 02 Oct 2009 Fixed 10.0.1 3969 02 Oct 2009 Fixed Description Calls to the ODBC function SQLGetTypeInfo() always returned 0 in the CASE_SENSITIVE metadata column for the XML data type. For case-sensitive databases, string comparisions of columns and variables of type XML is case sensitive. Therefore, SQLGetTypeInfo() has been fixed to returned 1 in this case.

CR:592860

CR Number:   592860 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 2329 14 Oct 2009 Fixed 10.0.1 3973 14 Oct 2009 Fixed Description On Unix systems, starting the server as a daemon could have hung if a fatal error occurred while starting up. This included Linux Standalone and Network services installed with the Service utility (dbsvc) as 'automatic on startup'. This has been fixed.

CR:592873

CR Number:   592873 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2326 06 Oct 2009 Fixed 10.0.1 3970 06 Oct 2009 Fixed Description By specifying the primary key in a separate clause of the CREATE TABLE statement, the UltraLite runtime allowed tables to be created with Long column types (ie. BLOBS, CLOBS) as primary keys. For example: 'CREATE TABLE t1( v1 LONG VARCHAR, PRIMARY KEY(v1))' The use of long datatypes in indexes is not supported by UltraLite, and inserting into the resulting table would have resulted in a crash. This has been corrected, long datatypes are now flagged as invalid when used in an index.

CR:592887

CR Number:   592887 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 3977 20 Oct 2009 Fixed 11.0.0 1654 20 Oct 2009 Fixed 11.0.1 2334 20 Oct 2009 Fixed Description Some database corruptions could have caused the cleaner to attempt to reference pages beyond the end of the database. This situation is now caught, and the server will halt with assertion failure 201301.

CR:592912

CR Number:   592912 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 2324 05 Oct 2009 Fixed 11.0.0 1654 05 Oct 2009 Fixed 10.0.1 3969 05 Oct 2009 Fixed Description In some cases, the database server was not able to fully recover from a crash, and displayed an assertion failure message. The server console would have shown that the server was able to recover the database, and a checkpoint was completed successfully, but then assertion failure 100920 was displayed: "Transaction log page X is corrupted." This problem has now been fixed.

CR:592976

CR Number:   592976 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 2327 06 Oct 2009 Fixed Description When using the debugger in the Sybase Central, right-clicking in the Editor to show the popup menu would have make the cursor disappear. This has now been fixed.

CR:592981

CR Number:   592981 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 2327 05 Oct 2009 Fixed Description Generating SQL procedures using the iAnywhere WSDL compiler (WSDLC) may have failed if the target WSDL (Web Services Description Language) contained an operation with a message referencing a complex fault type. This has been fixed. Generating fault stubs for WSDLC -l sql ... is not supported. The fault message type is now ignored and the SQL for the SOAP procedure is generated as expected.

CR:593118

CR Number:   593118 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 2328 03 Nov 2009 Fixed Description Only users with DBA authority should be able to reset a login policy, even if it is for themselves. The server was failing to check for this permission. This has been fixed. The server now ensures that only users with DBA authority can reset a login policy.

CR:593120

CR Number:   593120 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 2327 06 Oct 2009 Fixed 10.0.1 3970 06 Oct 2009 Fixed 9.0.2 3899 06 Oct 2009 Fixed Description The QAnywhere server could have stopped sending and receiving messages with an Enterprise Messaging Server, through its JMS connector, when connectivity to the EMS was interrupted and subsequently restored. This has been fixed.

CR:593135

CR Number:   593135 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 2328 08 Oct 2009 Fixed 11.0.0 1654 08 Oct 2009 Fixed Description The server could have become deadlocked soon after starting a database. For this to have occurred, the database in question must have had a large dbspace, which must have been rapidly growing, and recent inserts and updates must either have failed, or have been undone by another transaction. This problem has now been fixed.

CR:593143

CR Number:   593143 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 2328 06 Oct 2009 Fixed Description When running the database transfer tool on a BlackBerry Bold, the buttons were too small to display all text. Only the first character, plus some ellipses showed up on all buttons. This has been fixed. Now, all buttons display normally. However, the layout of the buttons is affected. They are aligned to the left, instead of in the center. After the fix, buttons on other models of the BlackBerry remain legible.

CR:593273

CR Number:   593273 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 2331 19 Oct 2009 Fixed Description The server could have crash when attempting to execute a statement having a WHERE clause with a disjunction on sargable predicates, such that each predicate can be used for a partial index scan. This has been fixed. For example: select * from R left outer join T where R.X = 10 OR R.Y = T.Y Both "R.X = 10" and "R.Y = T.Y" are sargable. An index must exist for on R<X> and R<Y>. Workaround Description  SELECT workorder_b.workorderid FROM workorder workorder_a, (compjobdependency , workorder workorder_b) LEFT OUTER JOIN compjob ON workorder_b.compjobid = compjob.compjobid LEFT OUTER JOIN componentunit ON compjob.compid = componentunit.compid LEFT OUTER JOIN functions ON componentunit.compid = functions.compid and ( compjobdependency.functionid is NULL or compjobdependency.functionid = functions.functionid ) WHERE ( workorder_a.compjobid = compjobdependency.compjobid ) and ( compjobdependency.dependsonid = workorder_b.compjobid ) and ( workorder_b.filed = 0 ) And ( workorder_b.WOStatus in (1,2,3,5,6) ) And ( workorder_b.duedate is not null ) and ( workorder_a.workorderid = 1000058123 ) and (compjobdependency.functionid is NULL OR functions.functionid is not null)

CR:593329

CR Number:   593329 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 2328 07 Oct 2009 Fixed 11.0.0 1654 07 Oct 2009 Fixed Description When a database was run on a server started in "in-memory" mode (-im connand line option), and a checkpoint was performed during recovery, the server could have hung on shutdown. This has been fixed.

CR:593334

CR Number:   593334 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2334 20 Oct 2009 Fixed 10.0.1 3977 20 Oct 2009 Fixed 9.0.2 3906 20 Oct 2009 Fixed Description The error "Fatal error: Could not write to file" could have been returned from the server when attempting to write to a file in a clustered environment. While the clustering service was performing some tasks, it was possible that the database server would be given an error ERROR_NOT_READY when attempting to perform an operation on the file. The server now retries the operation several times in this circumstance.

CR:593347

CR Number:   593347 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 2331 08 Oct 2009 Fixed 10.0.1 3975 08 Oct 2009 Fixed Description An application connected using the iAnywhere JDBC Driver, and calling the method PreparedStatement.setBlob() to insert a blob of length between 64M and 256M, would have seen the insert take much longer than if the application used the method PreparedStatement.setBinaryStream() instead. This problem has now been fixed, and in addition, also improves the performance of using PreparedStatement.setBinaryStream(). Note that using setBlob() requires significantly less memory than using setBinaryStream(), and also, for blob values greater than 256M in size, setBlob() may actually be the only option.

CR:593428

CR Number:   593428 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 3972 08 Oct 2009 Fixed 9.0.2 3901 08 Oct 2009 Fixed Description If an application executed a query containing a large number of proxy tables on a 64-bit server, and the query ended up being executed in NO PASSTHRU mode, then there was a chance the server would have failed assertion 101508 instead of giving the "syntactic limit exceeded" error. This problem has now been fixed, and the "syntactic limit exceeded" error is now properly returned.

CR:593472

CR Number:   593472 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2334 21 Oct 2009 Fixed 10.0.1 3977 21 Oct 2009 Fixed 9.0.2 3906 21 Oct 2009 Fixed Description If a subquery contained an equality predicate with an outer reference, and the left and right expressions of the equality predicate had different domains, then the computed result set may have been incorrect. The equality predicate must have been of the form "local column = outer reference column". This problem has now been fixed. For example: select * from R, S where R.X NOT IN ( select T.X from T where T.N = S.I) where the column T.N is of type numeric and the column S.I is of type integer.

CR:593523

CR Number:   593523 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 2331 15 Oct 2009 Fixed Description The addition of fractional days to a timestamp value would have been incorrect. This was corrected.

CR:593676

CR Number:   593676 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2329 13 Oct 2009 Fixed 10.0.1 3973 13 Oct 2009 Fixed Description When using the SQL Anywhere ODBC driver, the transaction isolation level can be set with a call to the ODBC function SQLSetConnectAttr(). The following is an example for setting the transaction isolation level to "readonly-statement-snapshot": SQLSetConnectAttr( dbc, SA_SQL_ATTR_TXN_ISOLATION, (SQLPOINTER)SA_SQL_TXN_READONLY_STATEMENT_SNAPSHOT, SQL_IS_INTEGER ); The following isolation level options are available. SQL_TXN_READ_UNCOMMITTED SQL_TXN_READ_COMMITTED SQL_TXN_REPEATABLE_READ SQL_TXN_SERIALIZABLE SA_SQL_TXN_SNAPSHOT SA_SQL_TXN_STATEMENT_SNAPSHOT SA_SQL_TXN_READONLY_STATEMENT_SNAPSHOT When any of the "snapshot" isolation levels were selected, the ODBC driver would have set the transaction isolation level incorrectly upon connecting to the server. The following is an example of a SET statement that was executed: SET TEMPORARY OPTION isolation_level = readonly-statement-snapshot; This would have resulted in a syntax error and the server options would not have been changed. This problem has been fixed. The ODBC driver will now generate the following correct syntax with quotes around the isolation level value. SET TEMPORARY OPTION isolation_level = 'readonly-statement-snapshot';

CR:594121

CR Number:   594121 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 2331 13 Oct 2009 Fixed Description The value of property('StartTime') could have been returned as NULL if used in an event that was fired immediately after the server was started. This has been fixed.

CR:594130

CR Number:   594130 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 2331 14 Oct 2009 Fixed Description If the Interactive SQL utility, Sybase Central, or DBConsole reported an internal error, and the link to check for software updates was clicked, it would not say that updates were available, even if they were. This has been fixed.

CR:594288

CR Number:   594288 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3904 14 Oct 2009 Fixed Description The message for SQLE_INDEX_NOT_UNIQUE errors did not contain the index or table names. This has been fixed so that the error is now set with the appropriate parameters.

CR:594317

CR Number:   594317 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows NT Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2335 22 Oct 2009 Fixed Description If a synchronization had failed during the download, but before MobiLink had been able to generate any data for the download, then the MobiLink server would have placed the synchronization in the restartable state. When the same remote database synchronized again, there was a chance that the MobiLink server would not have been able to find the previous synchronization to cancel it, preventing the remote database from synchronizing. This problem has now been fixed. A workaround to this problem would be to stop and start the MobiLink server. Workaround Description  None.

CR:594327

CR Number:   594327 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 2331 15 Oct 2009 Fixed 10.0.1 3975 15 Oct 2009 Fixed Description If an application called the method DatabaseMetaData.getDatabaseProductVersion() on a closed Connection object, then the iAnywhere JDBC Driver would have thrown a NullPointerException, instead of returning the appropriate SQLException. This problem has now been fixed.

CR:594373

CR Number:   594373 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 2332 16 Oct 2009 Fixed Description When used with a BIGINT argument, the INTTOHEX function could have returned an incorrect value. This has been corrected.

CR:594463

CR Number:   594463 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) 19 Oct 2009 Fixed Description The server could have crashed if the definition of a declared temporary table used in a procedure was modified. This has been fixed.

CR:594465

CR Number:   594465 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 2331 15 Oct 2009 Fixed Description The addition of fractional days to a timestamp value would have been incorrect. This was corrected.

CR:594470

CR Number:   594470 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 2332 15 Oct 2009 Fixed Description Attempting to call the system procedure sa_performance_statistics(), could have resulted in the failure of assertion 109510 on machines with many CPUs. This has been fixed.

CR:594476

CR Number:   594476 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2331 16 Oct 2009 Fixed Description On Linux systems, invoking the Service utility (dbsvc) with the options "-l -cm" would have given unexpected results. In particular, it would not have displayed the service creation command. This has been fixed.

CR:594479

CR Number:   594479 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 19 Oct 2009 Fixed Description On Linux systems, the Service utility (dbsvc) did not accept localized confirmations for overwrite or delete. For example, in the German version, when dbsvc asked to confirm overwriting or deleting a service, it showed the language specific options (J/N), but it expected a 'Y' for confirmation. This has been fixed.

CR:594492

CR Number:   594492 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 2332 19 Oct 2009 Fixed Description In rare cases, a database mirroring server could have crashed at shutdown. This has been fixed.

CR:594528

CR Number:   594528 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 2332 19 Oct 2009 Fixed 10.0.1 3975 19 Oct 2009 Fixed Description In very rare situations, the server could have failed assertion 104908 at shutdown. This has been fixed.

CR:594568

CR Number:   594568 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 2401 26 Feb 2010 Fixed Description Queries executed with a plan that involved parallel hash joins that caused a run-time error (for example, a conversion error) could have occasionally hung. This has been fixed. A workaround is to disable parallel plans (i.e. set MAX_QUERY_TASKS = 1).

CR:594666

CR Number:   594666 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 2332 19 Oct 2009 Fixed Description If an application called the ODBC function ResultSet.getCursorName(), then the iAnywhere JDBC Driver would have returned a truncated cursor name. The JDBC driver was incorrectly assuming that the returned length from SQLGetCursorNameW was in bytes, when in fact the value returned is in characters. This problem has been fixed, and the full cursor name is now properly returned.

CR:594708

CR Number:   594708 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 2332 19 Oct 2009 Fixed Description When a SQL Anywhere database that was being monitored by the SQL Anywhere Monitor, had a percentage of cache used that was over the user-set threshold in the Monitor, the Monitor could have failed to raise the corresponding memory usage alert. This has been fixed.

CR:594711

CR Number:   594711 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 2341 02 Nov 2009 Fixed Description The cardinality estimation of an index having more than one sargable equality predicate on a prefix column could have been incorrectly set to 0%. At least one of the sargable predicates must have been an equality with a constant and at least one of the sargable predicates must have been an equality with a non-constant expression. This has been fixed. For example: There exists an index on T <X,Y>: create index T_xy on T (X,Y) Select * from T, R where T.X = 1 and T.X = R.X and T.Y > 10

CR:594888

CR Number:   594888 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2328 19 Oct 2009 Fixed 10.0.1 3972 19 Oct 2009 Fixed Description The performance of ODBC metadata functions, such as SQLPrimaryKeys, SQLTables, and SQLColumns, has been improved for case-sensitive databases. This performance improvement will not occur for case-sensitive databases if SQLSetStmtAttr is called to set the SQL_ATTR_METADATA_ID attribute to SQL_TRUE. However, by default, this attribute is set to SQL_FALSE. When set to SQL_FALSE, case-sensitive databases will now enjoy the same performance as case-insensitive databases. Please note that when the SQL_ATTR_METADATA_ID attribute is set to SQL_TRUE, the string arguments to metadata functions are treated as identifiers, not strings (or patterns like "co%"). Identifiers can be delimited, in which case leading and trailing spaces are removed. Identifiers need not be delimited, in which case trailing spaces are removed.

CR:594897

CR Number:   594897 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 2333 19 Oct 2009 Fixed Description The initial directory used by the file browsing windows in the graphical administration tools was "C:\Windows\System32" on Vista and Windows 7. The inappropriate initial directory was chosen only when the application was launched from an icon (e.g. in the "Start" menu.) This has now been changed to the system-defined user home directory, which is the initial directory used on Windows XP.

CR:594913

CR Number:   594913 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) 10.0.1 3977 22 Oct 2009 Fixed Description UltraLite primary key constraints must be named "primary". This requirement was not being enforced when the primary key was defined. This has been corrected so that now it is. Databases that have primary key constraints not named "primary" should be rebuilt.

CR:594914

CR Number:   594914 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2333 19 Oct 2009 Fixed Description The Relay Server had been relying on standard http cookie reflection or header reflection from the client to maintain affinity of the http session. However, some mobile devices suffer from thin http support, where both cookie and header reflection are not supported. So, the Relay Server Outbound Enabler (RSOE) now injects an IAS-RS-AFQ header at the first HTTP request of all session. The value of the header is the affinity token for the rest of the request belonging to the session. The backend server is responsible for transporting the affinity token to their client in their application protocol. The client is responsible for inserting the following query parameter to the query string of the subsequent responding URL. IAS-RS-AFQ=<affinity_token> The relay server will respect this affinity control when affinity information was not found in standard cookie nor in proprietary header.

CR:594916

CR Number:   594916 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 2333 20 Oct 2009 Fixed 10.0.1 4213 20 Apr 2011 Fixed Description In some circumstances, the server may have failed to recover a database with assertion failure 201135 - "page freed twice". Some newly allocated database pages were not being initialized. This has been fixed.

CR:594917

CR Number:   594917 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2332 20 Oct 2009 Fixed Description Backend farm Outbound Enabler security requirements and client security can be specified by client_security and/or backend_security properties of the backend farm in the Relay Server configuration file. These setting were not enforced though until the first Relay Server configuration update. This problem has now been fixed so that these setting are enforced immediately after Relay Server startup.

CR:594922

CR Number:   594922 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2332 19 Oct 2009 Fixed Description The Relay Server at log level 3+ will produce packet header logging in the RS-OE protocol. The Relay Server at log level 5+ will also produce packet header logging plus the hex dump of the payload. This has been changed to now suspress level 3 packet header logging when verbosity level is 5 or above.

CR:594929

CR Number:   594929 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 2335 20 Oct 2009 Fixed Description If an application called a CLR stored procedure at exactly the same time that another connection or event that made a CLR stored procedure call terminated, then there was a small chance the server would have incorrectly returned a thread deadlock error instead of completing the CLR call. This problem has now been fixed.

CR:595100

CR Number:   595100 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2334 20 Oct 2009 Fixed Description The Connect to Database dialog had strings overlapping text boxes. The "Connection String:" string and the "Specify Custom User" string overlapped their text boxes. This has been corrected.

CR:595104

CR Number:   595104 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 2333 21 Oct 2009 Fixed Description The Relay Server may be set up to autostart by the first RSOE connection. Concurrent autostarts were unnecessarily failing some of the RSOE connections that attempted to spawn the state manager (rshost.exe), but lost the race. This left those losing RSOE connections in an idle failed startup state, requiring users to restart them. The following error message would have been shown on the RSOE console and log file: 400 Auto started rshost.exe but it exited with return code <?>. This has been fixed by suppressing the startup error for the failed connections, as long as the connections can attach to the stage manager started by others.

CR:595276

CR Number:   595276 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3915 13 Nov 2009 Fixed 10.0.1 4025 10 Feb 2010 Fixed Description Procedures containing XML generation functions (XMLAGG, XMLELEMENT, etc.) that were simultaneously executed by large numbers of connections, could have caused the server to crash. This has been fixed. A workaround is to rewrite procedures that cause this behaviour to use the XML generation functions as EXECUTE IMMEDIATEs with a trim. For example, : CREATE PROCEDURE FOO() BEGIN SELECT XMLELEMENT('foo'); END; could be rewritten as: CREATE PROCEDURE FOO() BEGIN EXECUTE IMMEDIATE trim('SELECT XMLELEMENT(''foo'')'); END; Note that such rewritten procedures will no longer be able to take advantage of plan caching.

CR:595294

CR Number:   595294 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) 10.0.1 3976 22 Oct 2009 Fixed Description The install or uninstall process could have left the machine.config file in a bad state. This has been fixed.

CR:595416

CR Number:   595416 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   MacOS Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2449 22 Aug 2012 Fixed Description Support has now been added for Mac OS X 10.6

CR:595494

CR Number:   595494 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 2511 19 Oct 2010 Fixed 10.0.1 4136 19 Oct 2010 Fixed Description When running on Windows Vista or later, if the server encountered a fatal error it was possible to see a Windows crash dialog as well as a "Send Error Report" dialog. This has been fixed.

CR:595502

CR Number:   595502 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2336 23 Oct 2009 Fixed Description The Relay Server may have incorrectly reported that shared memory was exhausted and then failed to relay further traffic after a rare memory abuse. This fix improves the memory manager by detecting and reporting incidents when a block of shared memory is freed by more than one process, and will allow the Relay Server to continue following the abuse. The detection was added without introducing extra computational overhead. The error report has the following format in the relay server log: E. 2009-10-22 14:39:32. <1036.440.ShmDebug> Internal Error! Freeing already freed memory!: 00011390 The error message is useful in reporting issue to tech support so that we can identify defects in the higher level logic and eliminate the source of the rare abuse.

CR:595504

CR Number:   595504 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 2335 23 Oct 2009 Fixed 10.0.1 3978 23 Oct 2009 Fixed Description If an authenticated application connected to an authenticated database and executed an external environment call, then there was a chance the external call would fail with an authentication violation error. This problem has now been fixed.

CR:595624

CR Number:   595624 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 2331 23 Oct 2009 Fixed Description The Relay Server Outbound Eeabler (RSOE) will verify routing of the relayed packets, and issue session mismatch errors when a routing issue occurs. One of the verifications was checking against a session finger print (sfp). The error message contained useful elements like session index, observed sfp and expected sfp, but the message being logged in the RSOE log was mangled so that it was not possible to use the detail information in the message to diagnose routine issues effectively. This has now been corrected.

CR:595699

CR Number:   595699 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 2335 26 Oct 2009 Fixed 11.0.0 1654 26 Oct 2009 Fixed 10.0.1 3979 26 Oct 2009 Fixed Description In very rare cases, the Windows and Linux server may have hung and stopped processing requests if request level logging was turned on. This has been fixed.

CR:595744

CR Number:   595744 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2336 26 Oct 2009 Fixed Description After an HTTP request failure, the Relay Server Outbound Enabler (ROSE) would have unnecessarily failed an HTTP client retrying an HTTP request on the session using the acquired session cookie. This has been fixed by adding support in RSOE for this kind of resume.

CR:595745

CR Number:   595745 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2336 26 Oct 2009 Fixed Description After a session was interrupted due to client disconnecting from the Relay Server, the Relay Server Outbound Enabler (RSOE) may have logged cancelled operations on the session using incorrect backend connection context information. This has been fixed. Along with this fix, a typo was corrected where sfp was being logged as spf.

CR:595746

CR Number:   595746 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2338 27 Oct 2009 Fixed Description If the Interactive SQL utility executed a DROP statement which included an "IF EXISTS" clause, subsequent statements in the same batch would not have been parsed correctly. The symptom was that an unexpected error message would have been displayed, which referred to more than one of the statements which followed the DROP statement. This has been fixed.

CR:595878

CR Number:   595878 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) 9.0.2 3932 18 Dec 2009 Fixed Description Under rare circumstances, the server could have crashed when processing an INSERT ... SELECT statement. This has been fixed.

CR:595997

CR Number:   595997 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 2338 28 Oct 2009 Fixed Description When using a Synchronization Model with a Microsoft SQL Server consolidated database that had a table with a UNIQUEIDENTIFIER or TIMESTAMP primary key column, and using snapshot download and downloading of deletes, the following error would have occurred for the generated download_delete_cursor script: [-10002] Consolidated database server or ODBC error: ODBC: [Microsoft][ODBC SQL Server Driver]Restricted data type attribute violation This has been fixed.

CR:595999

CR Number:   595999 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) 12.0.0 2061 09 Nov 2009 Fixed 11.0.1 2346 10 Nov 2009 Fixed 10.0.1 3985 10 Nov 2009 Fixed Description With versions of the server that included the changes made for Engineering case 555808, queries with a recursive union could have failed to match rows on the recursive passes. Although there was nothing wrong with the fix itself, the changes exposed the underlying problem, which has now been fixed. A workaround is to drop indexes on the table(s) being queried recursively, although there may a performance implications to doing this, which could be significant.

CR:596021

CR Number:   596021 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 2338 27 Oct 2009 Fixed 11.0.0 1654 27 Oct 2009 Fixed Description Database recovery using in-memory mode would have failed with assertion 201865. The database must have had multiple dbspaces for this assertion to have occurred. This has been fixed. A workaround is to recover without in-memory mode, but thist will cause the database on disk to be modified.

CR:596034

CR Number:   596034 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 2350 08 Dec 2009 Fixed Description Attempting to run a silent install using an MSI file created by the Deployment wizard, could have failed with the error: Error 2769: Custom Action CAD_writeStrings did not close 3 MSIHANDLEs. This has been corrected by no longer using MSIHANDLEs in custom actions, but rather using PMSIHANDLE variables, which are automatically freed when they go out of scope.

CR:596235

CR Number:   596235 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 2340 29 Oct 2009 Fixed Description When deploying a Synchronization Model to a new UltraLite database, if the remote schema had LONG NVARCHAR columns, an error would have occurred because UltraLite does not support LONG NVARCHAR columns. This has been fixed so that a warning is now given, and a LONG VARCHAR column is used instead in the new UltraLite database.

CR:596417

CR Number:   596417 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 2341 30 Oct 2009 Fixed Description There was a scenario, although rare, where an UltraLiteJ client may have hung and no longer have been able to synchronize when MobiLink server farms are involved. This has been fixed.

CR:596419

CR Number:   596419 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2343 03 Nov 2009 Fixed 11.0.0 1654 04 Nov 2009 Fixed 10.0.1 3983 04 Nov 2009 Fixed 9.0.2 3912 04 Nov 2009 Fixed Description When autostarting a database, database-specific options (such as -ds) which had values containing quotation marks were not handled correctly. For example, the following would not have worked correctly: dbisqlc -c "dbf=my.db;dbs=\"d:\tmp\spacey path\"" This problem has now been corrected. Note that using quotation marks on the command line to start a database server worked correctly: dbeng11 my.db -ds "d:\tmp\spacey path" A related problem was found and fixed in dbisqlc which handled the START DATABASE statement itself, and constructed a connection string containing a "dbs=-ds ..." parameter, rather than passing the START DATABASE statement to the server. Dbisqlc was not putting quotes around a -ds parameter that contained spaces.

CR:596641

CR Number:   596641 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2341 30 Oct 2009 Fixed 10.0.1 3982 30 Oct 2009 Fixed 9.0.2 3911 30 Oct 2009 Fixed Description If all of the following conditions were met, then SQL Remote would have continued to hold locks in the database until the next time that it needed to send the results of a SYNCHRONIZE SUBSCRIPTION to a remote database: 1) SQL Remote was running in send-only mode (-s) 2) SQL Remote was running in continuous mode 3) SQL Remote was satisfying a resend request for user "X", and was forced to re-scan the transaction logs 4) While scanning the transaction log, a SYNCHRONIZE SUBSCRIPTION operation was scanned for a user "Y" 5) User "Y" had already been sent the results of the SYNCHRONIZE SUBSCRIPTION operation in a previous run of SQL Remote. This has been fixed by releasing the locks when the send phase of dbremote reaches the end of the transaction log and determines that the SYNCHRONIZE SUBSCRIPTION operation does not need to be sent to the remote user. The problem can be worked around by stopping and starting the dbremote process that was running in send-only mode.

CR:596656

CR Number:   596656 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 2353 19 Nov 2009 Fixed 10.0.1 3990 04 Nov 2009 Fixed Description If an application made an external environment call, and the external environment procedure subsequently made a server-side call that required acquiring a lock that was already held by the connection making the external environment call, then there was a chance the application would hang. This problem has now been fixed.

CR:605029

CR Number:   605029 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2342 02 Nov 2009 Fixed Description When the Relay Server Outbound Enabler (RSOE) loses a connection to the Relay Server, it will attempt to recovery the connection at a rate controlled by the -d switch. The reattempt may have unnecessarily failed, causing more reattempts before the service was restored. This has been fixed. The fix also improves error reporting on the RSOE so that it will report the HTTP response code and message in an error in cases when the web server rejects the request before it reaches the Relay Server extension.

CR:605032

CR Number:   605032 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2342 02 Nov 2009 Fixed Description Under rare situation, the Relay Server may have notified the Relay Server Ooutbound Enabler (RSOE) to disconnect a stale backend connection when the HTTP response had been completed, but the RSOE didn't indicate that the backend server connection had been completed within a tolerable latency. When this happened on a request that was not the first one of a HTTP session, the Relay Server didn't fill in available OE and session indexes to optimize the lookup of the backend session, and caused the RSOE to perform extra work to lookup the session. The RSOE was also logging misleading invalid indices because of this. This problem has now been corrected.

CR:605039

CR Number:   605039 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 2342 02 Nov 2009 Fixed Description When using using the "-im nw" command line option (in-memory, no-write mode ), the server does not use a temporary file for the database; however, sa_disk_free_space() was returning a row for the temporary dbspace. This has been fixed.

CR:605058

CR Number:   605058 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2344 03 Nov 2009 Fixed 10.0.1 3985 04 Nov 2009 Fixed 9.0.2 3914 04 Nov 2009 Fixed Description If a client-side cursor UPDATE was performed using the SQL Anywhere OLE DB provider, and the column was of type VARCHAR(n), where n was greater than or equal to 256 and the column value was originally NULL, then an error message similar to the following would have been issued by ADO: Row cannot be located for updating. Some values may have been changed since it was last read. The OLE DB provider was failing to return DBSTATUS_S_ISNULL for the column value and returned an empty string instead. This caused ADO to generate an UPDATE statement with a WHERE clause expression of the form "column = ?" and a bound value of '' (a zero-length string). This problem has been fixed. ADO will now generate an UPDATE statement with a WHERE clause expression of the form "column IS NULL". A workaround is to use a server-side cursor.

CR:605071

CR Number:   605071 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2050 03 Nov 2009 Fixed 11.0.1 2343 04 Nov 2009 Fixed Description The Relay Server, in general, is not forward compatible with future versions of the Relay Server Ooutbound Enabler (RSOE). Changes have now been made which will allow future version of RSOE to fallback to a protocol version that is compatible with the Relay Server in use at the time. New Relay Servers will no longer reject connections from newer RSOEs, but will request a protocol version adjustment. This fix also contains an independent change that allows the RSOE to work with legacy 11.0.x Relay Servers without patching the Relay Server with the capability to request a protocol version adjustment. Heterogeneous Relay Server farms, with a mix of new and old Relay Servers, has also been enabled by this change. This can be useful in progressive Relay Server farm upgrades. Here is the compatibility matrix following this change: RS RS 11.0.0.ga-1529 11.0.0.1530 and up 11.0.1.ga and up 12.0 beta and up RSOE 11.0.0.ga-1529 YES YES RSOE 11.0.0.1530 and up NO YES 11.0.1.ga and up 12.0 beta and up

CR:605250

CR Number:   605250 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) 12.0.0 2050 03 Nov 2009 Fixed 11.0.1 2343 04 Nov 2009 Fixed Description It was possible that for a long running query alert to have been generated with "null" as the query text in the alert. In most circumstances, this was caused by the server option "RememberLastStatement" being turned off. This has been corrected so that when this situation now occurs the alert text has been updated to suggest that the user turn on RememberLastStatement, rather than presenting the unhelpful query text of "null".

CR:605253

CR Number:   605253 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3913 03 Nov 2009 Fixed Description Sybase Central would have throw an exception on startup on Windows 7 systems. The Windows XP theme that Sybase Central used did not work poperly in JDK 1.4.2. That theme is no longer used on a Windows 7 system, the classic Windows theme is used instead.

CR:605385

CR Number:   605385 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 2343 04 Nov 2009 Fixed Description When installing 11.0.1 on Mac OS X 10.6 (Snow Leopard), the registration key panel had problems displaying the key as entered. Sometimes, nothing would have been displayed, other times mangled characters would have been displayed. This has been fixed.

CR:605386

CR Number:   605386 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 2343 04 Nov 2009 Fixed Description When any of the Java based administration tools (Interactve SQL, Sybase Central, Mobilink Monitor, DBConsole) were launched on Mac OS X systems, two copies of the admin tool icons were being displayed on the Dock. This has been fixed.

CR:605393

CR Number:   605393 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 2343 04 Nov 2009 Fixed 11.0.0 1654 04 Nov 2009 Fixed 10.0.1 3984 04 Nov 2009 Fixed 12.0.0 2051 04 Nov 2009 Fixed Description The value being maintained for the CacheFree property was not as documented and was of limited use. The value now returned is the number of cache images that contain no useful data. The values for the properties CacheFree+CachePinned+CacheFile should give the current cache size (i.e. number of images currently in the cache). The values for the properties CacheFile+CacheFree should give an upper bound on the number of pages immediately available for reuse (without resorting to growing the cache).

CR:605412

CR Number:   605412 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) 12.0.0 2051 05 Nov 2009 Fixed 11.0.1 2343 05 Nov 2009 Fixed Description If client_security (or server_security) was set to 'on' in the Relay Server for Apache running on Linux, the Relay Server may have unnecessarily failed the client's (or Outbound Enabler's) HTTPS requests. This has been fixed.

CR:605413

CR Number:   605413 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) 12.0.0 2051 05 Nov 2009 Fixed 11.0.1 2343 05 Nov 2009 Fixed 10.0.1 3984 05 Nov 2009 Fixed 11.0.0 1654 05 Nov 2009 Fixed Description If the server attempted to open a database file concurrently with antivirus software, the database could have failed to start, or the server could have failed with an assertion error. This has been fixed by adding a retry for sharing violations on a file open.

CR:605414

CR Number:   605414 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) 12.0.0 2051 06 Nov 2009 Fixed 11.0.1 2358 06 Nov 2009 Fixed 10.0.1 3984 06 Nov 2009 Fixed Description On very rare occasions, if the number of allowed connections was exceeded, the HTTPS server may have sent the "Service temporarily unavailable" 503 response in plaintext. This has been fixed.

CR:605417

CR Number:   605417 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3984 06 Nov 2009 Fixed 9.0.2 3913 06 Nov 2009 Fixed Description The QAManagerFactory.getInstance() method of the QAnywhere .NET client would have thrown the exception System.DllNotFoundException when the native library qany9.dll or qany10.dll was missing. This exception may have been unexpected by a QAnywhere application, and has now been fixed. A QAException is now thrown in this situation, with ErrorCode 1000 (QAException.COMMON_INIT_ERROR) and Message containing the System.DllNotFoundException.

CR:605433

CR Number:   605433 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 2347 10 Nov 2009 Fixed Description If an application attempted to execute an UPDATE statement that updated a local table, but had a subquery in the SET clause that accessed a proxy table, then the server would have crashed. This problem has now been fixed.

CR:605645

CR Number:   605645 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) 12.0.0 2052 13 Jan 2010 Fixed 11.0.1 2371 08 Jan 2010 Fixed 10.0.1 4014 13 Jan 2010 Fixed Description On rare occasions, the execution of a VALIDATE DATABASE statement could have reported spurious orphaned page errors. This has been fixed.

CR:605651

CR Number:   605651 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) 12.0.0 2052 06 Nov 2009 Fixed 11.0.1 2344 06 Nov 2009 Fixed 10.0.1 3984 06 Nov 2009 Fixed Description The MobiLink server would have thrown the exception IllegalCastException when assigning the null reference to the Value property of an IDataParameter when using the MobiLink Direct Row API to download data. This has been fixed. A work around is to assign DBNull.Value instead.

CR:605653

CR Number:   605653 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 2344 05 Nov 2009 Fixed 10.0.1 3984 05 Nov 2009 Fixed Description If a REORGANIZE TABLE statement failed due to the table having been locked, then subsequent attempts to execute a REORGANIZE TABLE syatement would have also failed. The error would have been that a reorgorganize was already in progress. This has been fixed.

CR:605668

CR Number:   605668 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 2344 06 Nov 2009 Fixed 10.0.1 3984 06 Nov 2009 Fixed Description If an application that was connected via jConnect or Open Client attempted to insert or retrieve a datetime or time value, then the date portion of the value was limited to January 1, 1753 or later, and the time portion was restricted a precision of 1/300th of a second. Now, if an application uses newer versions of jConnect and Open Client, then the date portion of datetime values will span the full range from 0001-01-01 to 9999-12-31, and the time portion will now be handled in microsecond precision.

CR:605675

CR Number:   605675 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) 12.0.0 2052 06 Nov 2009 Fixed 11.0.1 2344 06 Nov 2009 Fixed Description For a MySQL synchronization model, any events with comments would have had the comments lost when deploying the model directly to a MySQL consolidated database. Thus the special "--{ml_ignore}" comment to ignore a script, would have been lost. This has been fixed. A workaround is to deploy to a file, and then run the deployed file.

CR:605792

CR Number:   605792 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2053 09 Nov 2009 Fixed 11.0.1 2344 09 Nov 2009 Fixed 11.0.0 1654 09 Nov 2009 Fixed 10.0.1 3985 09 Nov 2009 Fixed Description If an internal connection was the cause of a diagnostic message, it might have been identified with the phrase 'another user'. A more descriptive string identifying the connection will now be used. For example, one might now get a diagnostic message such as: User 'Cleaner' has the row in 'x' locked (SQLCODE: -210; SQLSTATE: 42W18)

CR:605803

CR Number:   605803 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2344 09 Nov 2009 Fixed 10.0.1 3985 09 Nov 2009 Fixed 9.0.2 3914 09 Nov 2009 Fixed Description When uploading data into a SQL Anywhere database from Microsoft SQL Server using the Linked Server mechanism, SQL Server could have reported that it had received inconsistent metadata information and failed the upload. This was due to the SQL Anywhere OLE DB provider returning inconsistent column lengths for VARCHAR and NVARCHAR columns when using the UTF8 character set collation. For example, an NVARCHAR(100) column length would have been reported as 400, which is the octet length for this column using the UTF8 collation, but the "ulColumnSize" field of the DBCOLUMNINFO structure should contain the maximum length in characters for DBTYPE_STR and DBTYPE_WSTR columns, not the maximum length in bytes. This problem has been corrected.

CR:605818

CR Number:   605818 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2055 09 Nov 2009 Fixed 11.0.1 2345 09 Nov 2009 Fixed Description The Relay Server Outbound Enabler (RSOE) may not have issued timely liveness packet on the down channel when the backend server was loaded. This may have caused a down channel read timeout on the Relay Server. Also, the Relay Server may not have issued timely liveness packets on the up channel when the it was loaded, This may have caused an up channel read timeout on the RSOE. Both of these problems are now fixed.

CR:605823

CR Number:   605823 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) 12.0.0 2055 09 Nov 2009 Fixed 11.0.1 2345 09 Nov 2009 Fixed Description For an IBM DB2 synchronization model, any events with comments would have had the comments lost when deploying the model directly to a DB2 consolidated database. Thus the special "--{ml_ignore}" comment to ignore a script, would have been lost. This has been fixed. A workaround is to deploy to file and run the deployed file.

CR:605843

CR Number:   605843 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2052 09 Nov 2009 Fixed 11.0.1 2344 09 Nov 2009 Fixed Description When non-persistent http was used, and there was a significant latency for the backend server to close the socket after writing all response bytes and before the next request of the same session come into the Relay Server Outbound Enabler (RSOE), the RSOE may have mistakenly failed the new request when the Relay Server timed out waiting for the close of the previous request. This has been fixed.

CR:605873

CR Number:   605873 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2075 09 Nov 2009 Fixed 11.0.1 2353 09 Nov 2009 Fixed Description Two minor problems have been corrected: 1) The logging of unilitialized session indexes has been fixed 2) Reword logging of backend socket closing activities to "DoneReceive EOF" instead of "disconnecting" or "socket close"

CR:605874

CR Number:   605874 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2056 10 Nov 2009 Fixed 11.0.1 2346 10 Nov 2009 Fixed Description When the Relay Server Outbound Enabler (RSOE) timed out an up channel connection, the RSOE would have recovered the connection, but it may have resulted in an invalid opcode being received in error from the Relay Server, and then cause the RSOE to disconnect both the up and down channels and restart. This is now fixed so that the RSOE will handle the reconnect properly without causing a more substaintial restart before restoring the service.

CR:606014

CR Number:   606014 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 2059 11 Nov 2009 Fixed 11.0.1 2346 11 Nov 2009 Fixed 11.0.0 1654 11 Nov 2009 Fixed Description When the script sqlanydb.py was run, it would not have propagated some fetch-related errors to the application. This has been fixed. Support has been added for Connection and Cursor .messages and .errorhandler attributes as outlined in PEP 249. Support has been added for SPARC 64 (and other platforms where sizeof(c_void_p) != sizeof(c_int)).

CR:606024

CR Number:   606024 Product Name:   SQL Remote for SQL Anywhere Product Component:   Database Tools Interface Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2078 20 Nov 2009 Fixed 11.0.1 2354 20 Nov 2009 Fixed Description A logic bug in the server may have caused database indexes to become corrupt under certain circumstances. The corruption would typically have manifest itself by generating SQLCODE -189 when deleting from an indexed column, followed by raising assertion 106200 - "Unable to undo index changes during rollback". The possibility of corruption was greater when using large page sizes with non-unique indexes over a small number of short columns. This problem has now been fixed. The corruption can be eliminated by dropping the affected index and recreating it with a server with this fix.

CR:606038

CR Number:   606038 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) 12.0.0 2059 10 Nov 2009 Fixed 11.0.1 2346 10 Nov 2009 Fixed 10.0.1 3986 10 Nov 2009 Fixed Description If an application attempted to create a proxy table to a Micosoft SQL Server table that contained a varchar(max) or nvarchar(max) column, then the server would have incorrectly mapped the varchar(max) columns to varchar(1) and the nvarchar(max) columns to nvarchar(1). This problem has now been fixed and the server now correctly maps varchar(max) columns to long varchar and nvarchar(max) columns to long nvarchar.

CR:606227

CR Number:   606227 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   HP-UX Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2355 16 Nov 2009 Fixed 10.0.1 3992 16 Nov 2009 Fixed Description When running running on HPUX, Solaris or AIX systems, it was possible for the server to crash while receiving IPv6 traffic. This has been fixed.