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

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

CR:566970

CR Number:   566970 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3817 02 Apr 2009 Fixed 9.0.2 3817 03 Apr 2009 Consult Complete Description When rebuilding a QAnywhere database, the reload of the ml_qa_status_history table could have failed with the error: "No primary key value for foreign key". This has been fixed.

CR:566986

CR Number:   566986 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2196 01 Apr 2009 Fixed Description The version of OpenSSL that is used in the RSA implementation on the Mac has been upgraded to version 0.9.8k. This was done because of a bug in OpenSSL, described here: http://www.openssl.org/news/secadv_20090325.txt. Note that only the third bug listed affected SQL Anywhere, and only on 64-bit Mac.

CR:567017

CR Number:   567017 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2196 01 Apr 2009 Fixed 10.0.1 3874 01 Apr 2009 Fixed Description When using the SQL Anywhere Support utility to check for updates (dbsupport -iu), it may have returned "Error checking for updates. Please try again later." Subsequent retries by the same dbsupport instance would also have failed. A counter variable was not being reset. This has now been fixed.

CR:567157

CR Number:   567157 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 2197 02 Apr 2009 Fixed 11.0.0 1599 02 Apr 2009 Fixed 10.0.1 3874 02 Apr 2009 Fixed Description In very rare circumstances, the server could have crashed during startup while recovering a database that used a mirror transaction log file. This has been fixed.

CR:567163

CR Number:   567163 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 2197 02 Apr 2009 Fixed 11.0.0 1599 02 Apr 2009 Fixed 10.0.1 3874 02 Apr 2009 Fixed Description If an application attempted to start an external environment on a server that was busy stopping or starting external environments for other connections, there was a chance the server would have returned a thread deadlock or 'main communication thread not found' error. There was also a chance, although small, that the server would have crashed in this situation. This problem has now been fixed.

CR:567222

CR Number:   567222 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Windows CE 2.11 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10 Jun 2009 Fixed Description Previous releases of QAnywhere relied on timestamp based synchronizations for message transmission. As a result, modifying the system time on a device could have interfered with the QAnywhere synchronization scheme, and in some cases caused QAnywhere to cease message transmission. This synchronization scheme has now been replaced with a progress counter based scheme in order to improve the reliability of synchronizations by removing the dependency on the device system clock.

CR:567328

CR Number:   567328 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 2197 03 Apr 2009 Fixed 11.0.0 1599 03 Apr 2009 Fixed Description When using an UltraLiteJ database with auto checkpointing and persistent indexes, if two connections were open on separate threads it was possible that changes committed to the database by the second connection may have been lost, and space in the database lost. This would have occurred when one connection was synchronizing (Connection.synchronize()) and the second connection was commiting changes to the database (inserts, updates and/or deletes), and the application terminated abnormally (power lost, crash). If the Connection.synchronize() call completed successfully, or with an ULjException, changes would not have been lost. This has now been fixed.

CR:567336

CR Number:   567336 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 2198 06 Apr 2009 Fixed Description If response headers were added, modified or deleted by the external environment, the (calling) SQL procedure had no way of inspecting and identifying changes to the response headers. This deficiency has been corrected by adding the functions HTTP_RESPONSE_HEADER( header_name ) and NEXT_HTTP_RESPONSE_HEADER( header_name ) for value retrieval and iteration of response headers. Response headers may be modified directly within a SERVICE procedure by calling SA_SET_HTTP_HEADER() or may be modified through an external environment process such as a PHP call through via SA_HTTP_PHP_PAGE. The usage semantics of HTTP_RESPONSE_HEADER() and NEXT_HTTP_RESPONS_HEADER() are the same as for HTTP_HEADER() and NEXT_HTTP_HEADER() respectively, which are used to inspect the request HTTP headers.

CR:567347

CR Number:   567347 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 2201 06 Apr 2009 Fixed 11.0.0 1601 06 Apr 2009 Fixed 10.0.1 3876 06 Apr 2009 Fixed Description If an application connected to a server via Open Client, using a newer version of Open Client 15, then it was likely that cancelling a request would have given a protocol error on the next request to the server. This problem has now been fixed.

CR:567361

CR Number:   567361 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 2198 06 Apr 2009 Fixed Description On some non-Windows platforms, pressing CTRL+C when the Interactive SQL utility (dbisql) was running in console mode could have caused spurious error messages which reported an unexpected signal 11, or "SIGSEV" error. This has been fixed so that these messages no longer appear when CTRL+C is pressed.

CR:567409

CR Number:   567409 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2204 09 Apr 2009 Fixed 11.0.0 1602 09 Apr 2009 Fixed Description If a CREATE TABLE statement was executed using EXECUTE IMMEDIATE and a declared temporary table with the same name already existed, an error was not given. This has been fixed.

CR:567417

CR Number:   567417 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2203 07 Apr 2009 Fixed 10.0.1 3877 07 Apr 2009 Fixed Description The DBLib client library could have crashed if there was a language resource problem, such as a missing language dll or .res file. In order for this crash to have occurred, db_init must have been called at least twice, and then another dblib call must have been made (such as db_string_connect or EXEC SQL CONNECT). This has been fixed, and db_init will now return 0 on language resource problems.

CR:567427

CR Number:   567427 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 2202 07 Apr 2009 Fixed 11.0.0 1601 07 Apr 2009 Fixed 10.0.1 3876 07 Apr 2009 Fixed Description If a transaction running under snapshot isolation attempted to update or delete a row that had been deleted and committed by another transaction, the update or delete would have failed with the wrong error. Typically the error would have been "Unable to find in index 't' for table 't' (SQLCODE: -189; SQLSTATE: WI005)", or it could have failed silently. This has now been fixed.

CR:567541

CR Number:   567541 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 2202 07 Apr 2009 Fixed Description As a result of changes made for Engineering case 545640, SQLAnywhere DISH services were not sending HTTP response headers. This has been fixed.

CR:567543

CR Number:   567543 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 2217 23 Apr 2009 Fixed 11.0.0 1607 23 Apr 2009 Fixed 10.0.1 3883 23 Apr 2009 Fixed 9.0.2 3823 23 Apr 2009 Fixed Description If the WHERE clause of a query block contained many predicates using host variables, it was possible that the PREPARE or OPEN times would have been unnecessarily long. The server was not recognizing the two expressions with host variables were the same. his has been fixed.

CR:567556

CR Number:   567556 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 2201 07 Apr 2009 Fixed 11.0.0 1601 07 Apr 2009 Fixed Description If a SQL Remote user was copied to the clipboard and the Message Types tab was selected, and then right-clicked within the right pane, a Paste menu item would have been shown. This menu item would never have been enabled after a SQL Remote message was copied to the clipboard. This has been fixed so that the menu item is no longer present.

CR:567570

CR Number:   567570 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3819 07 Apr 2009 Fixed Description It was possible for the server to enter a loop while processing some statements that included an implicit or explicit use of the table SYS.DUMMY. This has been fixed.

CR:567590

CR Number:   567590 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 2202 08 Apr 2009 Fixed Description The SQL Anywhere Monitor was setting redundant HTTP headers which would have caused the browser-based interface to function incorrectly when using SSL on Internet Explorer. This has been fixed by removing the redundant HTTP headers.

CR:567699

CR Number:   567699 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2202 08 Apr 2009 Fixed Description There were two scenarios where non-collected metrics could have been displayed by the SQL Anywhere Monitor. The two scenarios were: - If a user was viewing a tab with only one metric on it, went to administration and disabled collection of that metric, and went back to the monitoring tab, that metric's graph would still have been displayed, even though the tab itself was hidden. - If a user disabled collection of a metric that was displayed on a tab with several other metrics, the disabled metric would still have been displayed on the tab along with all the other metrics. These have both been fixed so that only the collected metrics are now displayed.

CR:567754

CR Number:   567754 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2203 08 Apr 2009 Fixed Description When providing a list of DER-encoded trusted root certificates to a MobiLink client for TLS synchronization, the client only accepted the first item in the list and ignored the rest. There was no problem if the list of certificates was PEM-encoded. This has been fixed. Note that this problem affected all MobiLink clients except UltraLiteJ.

CR:567778

CR Number:   567778 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2210 30 Apr 2009 Fixed Description Some of the files required to enable Windows Accessibility features were being installed in the wrong directory. This could have resulted in the Administration tools (eg Sybase Central)not running. This has been fixed.

CR:567790

CR Number:   567790 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 2204 09 Apr 2009 Fixed Description Incorrect results, including bogus error messages, could have been obtained when aliases (from the SELECT list) were referenced in a GROUP BY clause. This has been corrected.

CR:567794

CR Number:   567794 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 2203 09 Apr 2009 Fixed Description If the MobiLink Server was connected to an Oracle consolidated database, and an event was defined that called a stored procedure within a package, it was possible for a crash to have occurred in the iAnywhere Oracle ODBC Driver, which would in turn crash the MobiLink Server. This problem has now been fixed.

CR:567800

CR Number:   567800 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 2203 09 Apr 2009 Fixed Description If an alert email was sent that contained non-ASCII characters (i.e. multi-byte characters), this email would have arrived mangled if the machine running the SQL Anywhere Monitor was using a single-byte character set. This problem has now been fixed.

CR:567906

CR Number:   567906 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2236 07 May 2009 Fixed 11.0.0 1614 07 May 2009 Fixed 10.0.1 3891 07 May 2009 Fixed Description The MobiLink server could have crashed when multiple -x options were specified on the command line, with at least one being HTTP and another being HTTPS. This could have happened, for example, when a VPN connection was created or dropped in the middle of a non-persistent HTTP/HTTPS synchronization, and the network intermediaries were set up such that one path resulted in HTTP and the other resulted in HTTPS. This has been fixed.

CR:567932

CR Number:   567932 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2205 15 Apr 2009 Fixed Description Client-side certificates can now be used to authenticate MobiLink clients to third party server and proxies. The following two synchronization parameters have been added to provide support for this feature: identity - Indicates the file that contains the client's identity. An identity consists of the client certificate, the corresponding private key, and, optionally, the certificates of the intermediary certificate authorities. This parameter is equivalent to MobiLink server's 'identity' parameter. identity_password - An optional parameter that specifies the password used to encrypt the private key found in the identity file. It is only required if the private key in the identity file is encrypted. This parameter is equivalent to MobiLink server's 'identity_password' parameter. Note that MobiLink clients cannot authenticate directly to the MobiLink server using client-side certificates. They can only be used to authenticate to third-party servers and proxies which have been configured to accept client-side certificate authentication and are sitting between the client and MobiLink server. Also note, this feature is not supported in UltraLiteJ, and because of ECC compatibility issues between different versions of Certicom's Security Builder libraries, it is also not supported when using ECC TLS. It is only supported for RSA TLS.

CR:567942

CR Number:   567942 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 2235 07 May 2009 Fixed 11.0.0 1614 07 May 2009 Fixed 10.0.1 3891 07 May 2009 Fixed Description If a query was processed using a parallel execution plan, it was possible for the statement to exceed the setting of the Max_temp_space option by a factor of the number of branches in the plan. This has been fixed.

CR:567944

CR Number:   567944 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 2204 09 Apr 2009 Fixed Description Incorrect results, including bogus error messages, could have been obtained when aliases (from the SELECT list) were referenced in a GROUP BY clause. This was corrected.

CR:568091

CR Number:   568091 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 2205 14 Apr 2009 Fixed Description Under rare circumstances, if starting a database that truncates the transaction log at a checkpoint (i.e., WITH TRUNCATE AT CHECKPOINT clause to the START DATABASE statement or on a server started with the -m command line option) failed, the server may have crashed. This has been fixed.

CR:568216

CR Number:   568216 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 2045 14 Apr 2009 Fixed Description On Advanced Edition servers, the value of the ServerEdition server property was incorrect. This has been corrected.

CR:568217

CR Number:   568217 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2207 14 Apr 2009 Fixed 11.0.0 1604 14 Apr 2009 Fixed 10.0.1 3879 14 Apr 2009 Fixed Description On Mac OS X systems, an archive restore could have failed with an "insufficient space" error, even when enough space to complete the restore was available. This has been fixed.

CR:568219

CR Number:   568219 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 2207 15 Apr 2009 Fixed Description If the amount of available physical memory during an archive restore was low (the threshold is around 20 MB), but this was not the case during the archive backup, then the operation would have failed with an "insufficient memory" error, regardless of the amount of available swap space. This has been fixed.

CR:568233

CR Number:   568233 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 2213 17 Apr 2009 Fixed 11.0.0 1606 17 Apr 2009 Fixed 10.0.1 3882 17 Apr 2009 Fixed Description If a query had multiple uses of a function such as now() and one of the uses was within a COALESCE expression, then it was possible for the query to unexpectedly give different values for the two uses. For example, the following query could return different values for time1 and time2: create temporary function T_W( x int ) returns timestamp begin waitfor delay '00:00:00.500'; return NULL; end select coalesce( T_W(0), now() ) time1, coalesce( T_W(1), now() ) time2 In addition to now(), the following expressions also had this behaviour: getdate() today() current date current time current timestamp current utc timestamp In addition to coalesce() expressions, the same problem could occur with the now() or related function used within these expressions: ISNULL() IFNULL() IF CASE ARGN This has been fixed.

CR:568263

CR Number:   568263 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 2207 14 Apr 2009 Fixed Description A database could have been corrupted by an ALTER TABLE statement which changed the nullability of a column. Because the nullability of a column affects the internal storage format of row, all rows in the table must be reformatteded when the nullability changes. This has been implemented.

CR:568264

CR Number:   568264 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 2306 28 Aug 2009 Fixed 11.0.0 1654 28 Aug 2009 Fixed 10.0.1 3957 28 Aug 2009 Fixed 9.0.2 3950 28 Jan 2010 Fixed Description The server could have hung, consuming CPU, while attempting to shutdown a database if all workers were busy servicing other requests on different databases. This has been fixed. A workaround is to increase the -gn value of the server.

CR:568421

CR Number:   568421 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 2226 28 Apr 2009 Fixed 11.0.0 1610 28 Apr 2009 Fixed 10.0.1 3886 28 Apr 2009 Fixed Description Remote server capabilities were accidentally set OFF during a rebuild of a case-sensitive database. This has been fixed.

CR:568422

CR Number:   568422 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 2210 15 Apr 2009 Fixed 11.0.0 1608 20 Apr 2009 Fixed Description Under rare circumstances, a server participating in a mirroring system may have crashed on database shutdown. This has been fixed.

CR:568426

CR Number:   568426 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2213 17 Apr 2009 Fixed 11.0.0 1605 17 Apr 2009 Fixed 10.0.1 3883 20 Apr 2009 Fixed 9.0.2 3825 20 Apr 2009 Fixed Description When browsing permissions for tables and views, a user might have been listed more than once on the Permissions page of the property sheet for a table or view. Similarly, a table or view might have been listed more than once on the Permissions page of a user's property sheet. When fetching permissions, rows with the same grantee but different grantor, were not properly grouped. This has been fixed.

CR:568431

CR Number:   568431 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 2210 15 Apr 2009 Fixed 11.0.0 1604 15 Apr 2009 Fixed Description If an application executed an external environment stored procedure, and the external process terminated in the middle of the external call, then there was a chance the server would have crashed. This problem has now been fixed.

CR:568436

CR Number:   568436 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2210 15 Apr 2009 Fixed 10.0.1 3879 15 Apr 2009 Fixed Description When running on a Windows machine configured to use the 1252 code page, if the Interactive SQL utility (dbisql) attempted to open a file which contained a Euro sign (), it would have asked for which code page to use to interpret the file. Now, dbisql recognizes that the Euro sign is part of the Windows 1252 code page, and reads the file without prompting. This change also fixes similar behavior when a file contains any of the following characters: U+20AC Euro sign U+017D Latin capital letter Z with caron U+017E Latin small letter Z with caron

CR:568455

CR Number:   568455 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3823 15 Apr 2009 Fixed Description If an application executed a statement of the form IF EXISTS( SELECT ... FROM proc(), remote_tab ...) where proc() was a stored procedure that returned a result set and remote_tab was a proxy table, then itwas likely that the server would have crashed. This problem has now been fixed.

CR:568460

CR Number:   568460 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 2210 16 Apr 2009 Fixed Description All database resources were not completely freed when an ALTER TABLE DROP INDEX statement was executed. In particular, the database pages for the rows and indexes of the table, before the table is rebuilt, were not being freed. This has been corrected.

CR:568468

CR Number:   568468 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 2211 17 Apr 2009 Fixed 10.0.1 3881 17 Apr 2009 Fixed Description The SQL Anywhere server supports the "UPDATE( colname )" condition that can be evaluated in statement-level trigger code to determine if the value of the specified column has been modified from its original value in any of the rows in the row set affected by the UPDATE/INSERT/MERGE statement being executed. The server would have failed to evaluate the condition correctly for multi-row sets under certain circumstances. This has been corrected so that the server will now evaluate the condition correctly.

CR:568475

CR Number:   568475 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 2210 16 Apr 2009 Fixed 11.0.0 1604 16 Apr 2009 Fixed Description On the Basic Dbmlsync page of the Synchronization Profile's property sheet, only a single publication could have been specified. In addition, if a synchronization profile was created with multiple publications via the Interactive SQL utility, then the publications would have been lost when the property sheet was used to modify the synchronization profile. Now the property sheet supports multiple publications.

CR:568632

CR Number:   568632 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 2211 16 Apr 2009 Fixed Description When viewing table data for a SQL Anywhere database, Sybase Central could have reported an internal error. This has been fixed. The problem was highly timing dependent.

CR:568641

CR Number:   568641 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 2211 15 Apr 2009 Fixed 11.0.0 1605 15 Apr 2009 Fixed 10.0.1 3881 15 Apr 2009 Fixed Description Attempting to insert a large long binary value into a MicrosoftS SQL Server proxy table, would have failed with a "wrong precision" error. This problem was introduced by the fix for Engineering case 565651, and has now been fixed.

CR:568645

CR Number:   568645 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 2211 16 Apr 2009 Fixed 11.0.0 1605 16 Apr 2009 Fixed 10.0.1 3881 16 Apr 2009 Fixed Description On very rare occasions, the server may have failed to start on Solaris systems. This has been fixed.

CR:568652

CR Number:   568652 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 2213 17 Apr 2009 Fixed 11.0.0 1605 17 Apr 2009 Fixed Description Adding two columns with default values to a global temporary table would trigger assertion 100712 (page level logging already in progress).

CR:568657

CR Number:   568657 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 2211 16 Apr 2009 Fixed 11.0.0 1605 16 Apr 2009 Fixed Description Signed and unsigned short values were not being translated properly by the SQL Anywhere Python interface. Attempting to use short values would have resulted in errors like "struct.error: bad char in struct format" or "struct.error: unpack requires a string argument of length 1". This has been fixed.

CR:568660

CR Number:   568660 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 2211 17 Apr 2009 Fixed 11.0.0 1605 17 Apr 2009 Fixed 10.0.1 3881 17 Apr 2009 Fixed Description Referential integrity constraints (i.e. primary keys, foreign keys or unique constraints) involving long values may have resulted in unexpected errors. This problem has now been fixed.

CR:568663

CR Number:   568663 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 2217 22 Apr 2009 Fixed 11.0.0 1607 22 Apr 2009 Fixed 10.0.1 3884 22 Apr 2009 Fixed Description The server could have crashed during Application Profiling if any variables or host variables were present in the workload. This has been fixed.

CR:568674

CR Number:   568674 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 2223 20 Apr 2009 Fixed Description Attempting to execute an CREATE ENCRYPTED DATABASE statement to create a database encrypted with simple encryption, or the CREATE DECRYPTED DATABASE statement to decrypt a database encrypted with simple encryption, without having specified an encryption key, would have returned the error (-131 "Syntax error near '(end of line)' on line 1"). This has been fixed. As a workaround, add "KEY 'unused'" to either statement; whatever key is specify will be ignored.

CR:568821

CR Number:   568821 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 2212 17 Apr 2009 Fixed 11.0.0 1605 17 Apr 2009 Fixed Description Querying the deprecated server property MaxMessage, would have caused the server to crash if the property MessageCategoryLimit was set to 0. This has been fixed.

CR:568831

CR Number:   568831 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 2207 17 Apr 2009 Fixed Description A server running in a database mirroring system could have hung while log pages were being sent from the primary server to the mirror server. The primary server periodically sends a "catchup" request to the mirror to ensure that the mirror does not get too far behind in applying log operations that it has received from the primary and written to disk. It was possible for this request to cause a hang if it was received at the same time as an operation for a new connection was being processed in the transaction log. This has been fixed.

CR:568836

CR Number:   568836 Product Name:   UltraLite Product Component:   UltraLite for M-Business Anywhere Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2221 27 Apr 2009 Fixed 10.0.1 3890 27 Apr 2009 Fixed Description Incorrect results could have been obtained when using an index which had nullable columns In some cases, fewer rows were returned than were required. This has been fixed..

CR:568866

CR Number:   568866 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2226 29 Apr 2009 Fixed 10.0.1 3886 29 Apr 2009 Fixed Description The UltraLite Initialize Database utility (ulinit) is used to create an UltraLite database, based on information in the SQL Anywhere database that it is connected to. If the schema being extracted from the SQL Anywhere database contained elements that UltraLite did not support (like column datatypes or default values), the utility would have failed. Ulinit has been changed so that by default, it will attempt to create an UltraLite database that comes as close as possible to the SQL Anywhere database. For example, if a column in the SQL Anywhere database included the DEFAULT TIMESTAMP clause (a default that UltraLite does not support), a warning is generated and a default of CURRENT TIMESTAMP is generated instead. In particular, if a default in the SQL Anywhere database is not supported in the UltraLite database, the default value is ignored and creation continues. This enhancement was made because, in some cases, its possible the SQL Anywhere tables cannot be modified, and yet a reasonable UltraLite alternative is available. The ulinit utility also now has a f switch that can be used to make the utility fail if the exact schema does not match (in other words, the old behavior is given and the utility will fail). This fix also addressed a problem where warnings were emitted into the SQL file if the ulinit utility was run with l.

CR:568972

CR Number:   568972 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 2214 20 Apr 2009 Fixed Description In cases where the standalone version of the SQL Anywhere Monitor and the regular SQL Anywhere Monitor were installed on the same machine, the SQL Anywhere Monitor could have loaded the wrong ODBC driver. This has been fixed. The old incorrect behaviour would, in the vast majority of cases, not have had any noticeable impact on the SQL Anywhere Monitor. The application would still have worked normally. So, the SQL Anywhere Monitor EBF should also be applied when applying a SQL Anywhere EBF. Applying the SQL Anywhere EBF without the SQL Anywhere Monitor EBF could cause the SQL Anywhere Monitor to stop working.

CR:568976

CR Number:   568976 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2229 23 Apr 2009 Fixed 10.0.1 3886 01 May 2009 Fixed Description In rare, timing dependent circumstances, the server may have hung when executing queries using intra-query parallelism. This has been fixed. A workaround is to disable intra-query parallelism by setting the max_query_tasks option to 1.

CR:568984

CR Number:   568984 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 2214 17 Apr 2009 Fixed 11.0.0 1606 17 Apr 2009 Fixed Description If an application connected via HTTP and executed a PHP external environment stored procedure with a long varchar or long binary argument, then there was a very small chance the server would have crashed if the HTTP connection was cancelled at exactly the same time that the PHP external environment call was made. This problem has now been fixed.

CR:568986

CR Number:   568986 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2214 20 Apr 2009 Fixed 11.0.0 1606 20 Apr 2009 Fixed Description Performing a PutMessage operation from the Java QAnywhere Client using UltraLite, or from the Standalone Java QAnywhere Client, would have resulted in a memory leak equal to the size of the content of the message. This has been fixed.

CR:568991

CR Number:   568991 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 2214 20 Apr 2009 Fixed 11.0.0 1606 20 Apr 2009 Fixed 10.0.1 3882 20 Apr 2009 Fixed 9.0.2 3824 20 Apr 2009 Fixed Description Connecting to the server using Open Client and attempting to describe the input parameters of a dynamic statement, would very likely have cause the application to hang. This problem has now been fixed.

CR:569012

CR Number:   569012 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2211 21 Apr 2009 Fixed Description The "UserAgent" HTTP header for QAnywhere/MobiLink communications previously only specified "QAnywhere/11.0.1", and "QAnywhereUL/11.0.1", for SQL Anywhere and UltraLite clients respectively. It did not differentiate between data synchronization and listener components. This has been fixed. Now, the header specifies "QAnywhereSync/11.0.1" for a SQL Anywhere data sync client, "QAnywhereULSync/11.0.1" for a UltraLite data sync client, and "QAnywhereLsn/11.0.1" for a MobiLink listener client.

CR:569013

CR Number:   569013 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2217 21 Apr 2009 Fixed Description MobiLink clients and the certificate utilities would have failed to read PEM-encoded trusted certificates files which contained blank lines before the first PEM header. The PEM parsing code has now been modified to skip leading white space characters.

CR:569020

CR Number:   569020 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 2219 21 Apr 2009 Fixed 11.0.0 1608 21 Apr 2009 Fixed Description 1. When two separate connections (including one that might be synchronizing) are accessing the database in parallel, some lock row conflicts or download conflicts may not have been detected. For example: Connection 1 deletes row with primary key value 2 but does not commit Connection 2 inserts row with primary key value 2 - here there was an undetected row locked or download conflict if connection 2 was synchronizing When connection 1 was rolled back, a database corruption mau have occurred. This has been fixed. 2. Duplicate primary keys during a download were not detected. If the download contained two or more rows with the same primary key, the last row would be kept (this is not neccessarily correct if the download_cursor script does not have an ORDER BY clause). This has been fixed. UltraLiteJ will now report the SQLE_DUPLICATE_ROW_FOUND_IN_DOWNLOAD error when this is detected. Like UltraLite, this error is only reported for duplicate rows in the download_cursor - no detection is done for duplicate rows in the download_delete_cursor, or if the same primary key is in both the download_cursor and download_delete_cursor. 3. The all database synchronization would not have included new tables if the database was synchronized before the table was added (unless the application was restarted). This has been corrected.

CR:569114

CR Number:   569114 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 2214 20 Apr 2009 Fixed Description The SQL Anywhere Monitor, when installed by the standalone installer, was not able to monitor MobiLink servers. The standalone installer was not installing the library mljstrm11.dll as part of the SQL Anywhere support component. This problem does not exist in the edition of SQL Anywhere Monitor included with SQL Anywhere. This has been fixed.

CR:569122

CR Number:   569122 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 2217 21 Apr 2009 Fixed Description When deploying a synchronization model to an UltraLite remote database, the batch file generated to run ulsync had an example CONNECTION string that incorrectly used my_db.db, rather than my_db.udb. A correct CONNECTION string in the batch file is now generated.

CR:569124

CR Number:   569124 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2221 27 Apr 2009 Fixed 10.0.1 3884 27 Apr 2009 Fixed Description When a Synchronization Model was modified to include either handle_DownloadData or handle_UploadData events, the model file could not have then been re-opened. An error message would have been displayed stating "unknown or missing event ID handle_DownloadData" or "unknown or missing event ID handle_UploadData". This has been corrected.

CR:569127

CR Number:   569127 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 2221 27 Apr 2009 Fixed 11.0.0 1608 27 Apr 2009 Fixed 10.0.1 3884 27 Apr 2009 Fixed Description The result set returned from calling the system procedure dbo.sp_jdbc_primarykey() may have contained more rows than it should. This problem was introduced by the changes made for Engineering case 531119, and has now been fixed.

CR:569298

CR Number:   569298 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 2218 22 Apr 2009 Fixed 11.0.0 1607 22 Apr 2009 Fixed 10.0.1 3883 22 Apr 2009 Fixed Description In some cases, it was possible for recursive UNION queries to give incorrect results. This has been fixed.

CR:569307

CR Number:   569307 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 2218 22 Apr 2009 Fixed 10.0.1 3883 22 Apr 2009 Fixed Description A SQLAnywhere service requiring authorization returned realm information based on the request URL. This has been fixed. The realm is now always set to the database name (or its alias) regardless of the request URL.

CR:569314

CR Number:   569314 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2229 30 Apr 2009 Fixed 11.0.0 1611 30 Apr 2009 Fixed 10.0.1 3887 30 Apr 2009 Fixed Description The datepart() function could have returned an incorrect result for the CALWEEKOFYEAR and CALYEAROFWEEK date parts for dates greater than December 29 of years for which January 1 of the following year falls on Tuesday, Wednesday or Thursday. The first week of a year is defined as the week containing the year's first Thursday. All days in that week should have the same CALWEEKOFYEAR and CALYEAROFWEEK values, even for days in the previous year. This has been fixed.

CR:569316

CR Number:   569316 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 2218 21 Apr 2009 Fixed 11.0.0 1607 21 Apr 2009 Fixed 10.0.1 3883 21 Apr 2009 Fixed Description If an application connected using the iAnywhere JDBC driver and created a very large batch, containing either long binary or long varchar parameters, then executing the batch may have given a strange out of memory error dialog after which the application would have crashed. The driver has now been modified to allow such large batches to be executed; however, any such batches that require a very large amount of contiguous memory to be allocated will be executed one row at a time, instead of being batched. In addition, whenever the driver decides to execute a batch one row at a time, a SQLWarning will be returned on the executeBatch() call indicating that the "batch was executed in single row mode due to memory limitations".

CR:569323

CR Number:   569323 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 2218 22 Apr 2009 Fixed Description If the disk that the SQL Anywhere Monitor was resident on was in a low disk space situation, the Monitor would have generated disk space low alerts every 5 minutes instead of the default of generating the alerts every 30 minutes. This has been fixed.

CR:569327

CR Number:   569327 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 2218 22 Apr 2009 Fixed 11.0.0 1607 22 Apr 2009 Fixed Description If an application made an external environment call to a connection scoped external environment process, and that process then set an error and exited, then there was a chance the server would have crashed. This problem has now been fixed.

CR:569330

CR Number:   569330 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 2219 22 Apr 2009 Fixed 11.0.0 1608 22 Apr 2009 Fixed 10.0.1 3884 22 Apr 2009 Fixed Description The server could have crashed, or failed an assertion, if a materialized view had been disabled soon after an update. This has been fixed.

CR:569509

CR Number:   569509 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2218 22 Apr 2009 Fixed Description The MobiLink Listener would have gone into an infinite loop light weight polling continuously, without respecting the polling interval, when communication errors continue to occur. This has now been corrected.

CR:569510

CR Number:   569510 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 2218 22 Apr 2009 Fixed Description HTTP light weight polling may have failed with communication errors. This has been fixed.

CR:569513

CR Number:   569513 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 2214 22 Apr 2009 Fixed Description When an error or a timeout was detected between request phases of an http request-response cycle, the Relay Server outbound Enabler was not disconnecting the backend in a timely manner. This has been corrected.

CR:569516

CR Number:   569516 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 2218 22 Apr 2009 Fixed Description The Relay Server Outbound Enabler (RSOE) may have produced bad http requests. While relaying a packet of a http request, the RSOE would have reconnected to the backend server when the connection was lost, even if it was at the request boundary, producing a bad http request. This has been fixed by introducing a reconnect retry at request boundaries to improve robustness, and replace reconnect with an error for non-boundary packets.

CR:569520

CR Number:   569520 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 2211 22 Apr 2009 Fixed Description Dynamically added backend server farms, or servers, may have been incorrectly disabled. This is fixed.

CR:569543

CR Number:   569543 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 2220 23 Apr 2009 Fixed Description The SQL Anywhere Monitor could have reported "too many errors" or "too many failed syncs" alerts when it should not have. This has been fixed.

CR:569704

CR Number:   569704 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 2246 10 Mar 2010 Fixed Description Very complex queries, with more than 20 tables being joined, that were being optimized using the 'FIRST-ROW' optimization goal, may have had inefficient access plans. This has been fixed.

CR:569753

CR Number:   569753 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 2221 23 Apr 2009 Fixed 11.0.0 1608 23 Apr 2009 Fixed Description A database server acting as the mirror server in a mirroring system, could have hung in rare cases. This has been fixed.

CR:569759

CR Number:   569759 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 2221 27 Apr 2009 Fixed Description Executing the CREATE ENCRYPTED DATABASE or CREATE DECRYPTED DATABASE statement would have caused assertion 100202 if the source database was already running and the filename given in the statement did not contain the '.db' suffix. This has been fixed.

CR:569776

CR Number:   569776 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 2223 28 Apr 2009 Fixed 11.0.0 1609 28 Apr 2009 Fixed Description When processing a SIMILAR TO, REGEXP or REGEXP_SUBSTR expression and the request_timeout option was set, incorrect results could have been returned. If the request_timeout option was not set, it was possible for a cancelled expression to have taken several seconds, or more, to respond. This has been fixed.

CR:569778

CR Number:   569778 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 2218 27 Apr 2009 Fixed 11.0.0 1607 27 Apr 2009 Fixed Description If an application made a PHP external environment call that generated a large message, and then called exit(), there was a small chance that the server would have crashed. This problem has now been fixed.

CR:569784

CR Number:   569784 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 2226 29 Apr 2009 Fixed 11.0.0 1610 29 Apr 2009 Fixed 10.0.1 3886 29 Apr 2009 Fixed Description If a procedure definition did not contain a RESULT clause, and returned its results from a SELECT statement with a TOP n clause that used variables, describing a query of the form: SELECT * FROM proc() could have been incorrectly described by the server as having a single column with the name "expression". The result set returned by the statement would have had the correct schema. This has been fixed. Calling the procedure directly (i.e. call proc()) was not affected by this problem, and would be correctly described, so this statement can be used as a workaround. Describing the schema of the result set using a RESULT clause is also a workaround. To fix procedures created with older servers, an ALTER PROCEDURE <proc> RECOMPILE has to be executed for each such procedure.

CR:569797

CR Number:   569797 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2222 27 Apr 2009 Fixed 11.0.0 1608 27 Apr 2009 Fixed 10.0.1 3884 27 Apr 2009 Fixed 9.0.2 3826 27 Apr 2009 Fixed Description When unloading or extracting a database into a new database that was created with strong encryption, the Unload and Extract Database wizards would have display the encryption key in plain text in the Unload or Extract Database Messages Dialog. This has been corrected so that now the encryption key is displayed as "***".

CR:569931

CR Number:   569931 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) 10.0.1 3887 28 Apr 2009 Fixed 9.0.2 3829 28 Apr 2009 Fixed Description If a user-defined function using the Transact-SQL dialect issued a RAISERROR statement, and that function was called from another Transact-SQL function, the calling application could have failed to receive the error. In some cases, this would result in the application hanging. This has been fixed.

CR:569932

CR Number:   569932 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 2236 08 May 2009 Fixed 11.0.0 1614 08 May 2009 Fixed Description While performing certain operations that require sorting large amounts of data, such as creating an index, established temporary space limits that were set using the "max_temp_space" database option, could have been violated. This has been fixed.

CR:569934

CR Number:   569934 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 2237 27 Apr 2009 Fixed Description The server has been improved such that queries of the form: SELECT [...,]contents[,...] FROM dir_table WHERE [...AND] file_name=[string|variable] [AND...] now execute much faster. In the above example, dir_table is a proxy table to a directory access server, the WHERE clause contains zero or more AND clauses and no OR clauses, and one of the predicates in the WHERE clause is of the form file_name=[string | variable].

CR:569942

CR Number:   569942 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 2223 27 Apr 2009 Fixed 11.0.0 1609 27 Apr 2009 Fixed 10.0.1 3885 27 Apr 2009 Fixed Description If an application that was connected using Open Client executed a query that generated a large column name, then there was a chance the application would have exited with a TDS protocol error. This problem has now been fixed.

CR:569951

CR Number:   569951 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 2223 28 Apr 2009 Fixed Description The number of rows affected was not being reported following the execution of a TRUNCATE TABLE statement. This has been fixed. Execution of a TRUNCATE TABLE statement would have failed with an SQLE_UNCOMMITTED_TRANSACTIONS error ("You cannot synchronize or upgrade with uncommitted transactions <table name>"), if there were any uncommitted transactions, even on the current connection. This has been fixed. The TRUNCATE TABLE statement will now only report an error if there are uncommitted inserts and updates on another transaction. With this respect, TRUNCATE now behaves exactly like DELETE.

CR:569952

CR Number:   569952 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 2223 28 Apr 2009 Fixed 11.0.0 1609 28 Apr 2009 Fixed Description If an error occurred in the middle of the execution of a TRUNCATE TABLE statement (11.0.1) or API (11.0.0, 11.0.1), a rollback of the deletes would not have been done. This has been fixed. Synchronizations with the special truncate table download_delete_cursor may have resulted in a fatal error if a second connection did a commit after the truncate was applied, but before the the synchronization completed. This would have occurred only if there were more than a few rows in the table being truncated (248 for 1K page size). This has been fixed.

CR:570093

CR Number:   570093 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 2235 08 May 2009 Fixed 11.0.0 1614 08 May 2009 Fixed 10.0.1 3891 08 May 2009 Fixed Description If a SELECT statement contained the clause FOR UPDATE BY LOCKS, and a cursor was opened without specifying updatability cursor flags from the client application, then the BY LOCKS specification could have been incorrectly ignored by the server. This would only have happened if the statement was a simple query that was processed bypassing optimization. The consequence of this was that intent locks would not have been taken on the table being scanned. The only API affected by this problem was Embedded SQL. Also, if a statemented executing at isolation 3 used an index scan for a table marked for update, then the rows of the table could have incorrectly been locked with exclusive (write) locks, instead of intent locks. The consequence of this was that other connections attempting to read the row could have blocked, even if the row was ultimately not modified. These problems have now been fixed.

CR:570094

CR Number:   570094 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 2226 28 Apr 2009 Fixed 11.0.0 1610 28 Apr 2009 Fixed 10.0.1 3886 28 Apr 2009 Fixed 9.0.2 3828 28 Apr 2009 Fixed Description The server would have crashed when parsing a procedure that contained a CASE statement with a WHEN clause which had an unary search condition other than ISNULL. When unparsing the WHEN clause the server was expected a binary search condition and crashed when attempting to access the second operand. This has been fixed.

CR:570098

CR Number:   570098 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3894 15 May 2009 Fixed 11.0.0 1617 15 May 2009 Fixed 11.0.1 2243 15 May 2009 Fixed Description In some circumstances, a 10.x server could have hung at shutdown if a parallel backup had been performed, or an outbound HTTP connection (SOAP, etc) had been used. When those features were used on an 11.x server, the server would not have hung at shutdown, but unpredictable behaviour (crash, hang) could have occurred at runtime. This problem has been fixed. Note that the likelihood of encountering the problem with 11.x servers is extremely small.

CR:570115

CR Number:   570115 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 2226 28 Apr 2009 Fixed 11.0.0 1610 28 Apr 2009 Fixed Description Character set translation wasn't being done properly by the SQL Anywhere Python driver. Unicode encoding and decoding errors were possible, as well as incorrect translations. This has been fixed so that conversions are based on the connection's CharSet property.

CR:570116

CR Number:   570116 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2226 28 Apr 2009 Fixed 11.0.0 1610 28 Apr 2009 Fixed Description The mirror server in a mirroring system could have hung while processing log pages received from the primary server. This has been fixed.

CR:570128

CR Number:   570128 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 2226 29 Apr 2009 Fixed Description A small amount of memory was being leaked when a CREATE ENCRYPTED DATABASE or CREATE DECRYPTED DATABASE statement was executed. This has been fixed.