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

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

CR:550095

CR Number:   550095 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 3755 18 Nov 2008 Fixed Description If a query execution plan contained a Group-By Hash operator and one of the aggregates computed was marked as DISTINCT, then the server could have crashed while executing the statement. In order for the crash to occur, specific characteristics needed to be present in the statement. Thishas now been fixed.

CR:550103

CR Number:   550103 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2120 01 Dec 2008 Fixed 11.0.0 1542 01 Dec 2008 Fixed 10.0.1 3812 04 Dec 2008 Fixed Description Attempting to query a proxy table with a SELECT statement that used the FOR XML RAW clause would have failed with an "invalid expression" error. This problem has now been fixed.

CR:550116

CR Number:   550116 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 10.0.1 3797 12 Nov 2008 Fixed 9.0.2 3752 12 Nov 2008 Fixed 11.0.1 2113 25 Nov 2008 Fixed Description In rare cases, a stored procedure call could have caused a server crash. This has been fixed.

CR:550120

CR Number:   550120 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2113 14 Nov 2008 Fixed 11.0.0 1533 14 Nov 2008 Fixed Description An UltraLite .NET synchronization initiated by the SYNCHRONIZE SQL statement would have hung if no global listener was provided via the DatabaseManager::SetGlobalListener method. The unmanaged code always registered a global sync listener to send sync status messages, but the managed code only created a listener for these messages if the DatabaseManager::SetGlobalListener method was called, which resulted in the hang. Now the unmanaged code now only registers a global sync listener when SetGlobalListener is called.

CR:550159

CR Number:   550159 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 3798 13 Nov 2008 Fixed Description The ia32-libs package is required to install SQL Anywhere on 64-bit Ubuntu distributions. It is also required to run any 32-bit software on 64-bit Ubuntu distributions. Futhermore, resolving host names from 32-bit applications will fail on 64-bit Ubuntu installations, unless the package lib32nss-mdns is installed. See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479144

CR:550236

CR Number:   550236 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2030 27 Nov 2008 Fixed 11.0.0 1541 27 Nov 2008 Fixed Description If a query execution plan included parallelism and specific expression types were used, it was possible for memory corruption or assertion failures to occur when the query was executed. The following expression types could have caused the problem: SORTKEY() COMPARE() CONVERT( <date, time, or timestamp>, <string expression> ) In order for the failure to occur, further specific characteristics needed to be present in the string parameters to the above functions. This problem has been fixed.

CR:550246

CR Number:   550246 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 2114 13 Nov 2008 Fixed 10.0.1 3799 13 Nov 2008 Fixed Description If an application attempted to create a proxy table to a SQL Anywhere or Micrsoft SQL Server remote server, and the remote table had an XML column, then the server would have returned an undefined data type error. This problem has now been fixed.

CR:550247

CR Number:   550247 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2020 14 Nov 2008 Fixed 11.0.0 1534 14 Nov 2008 Fixed Description The MobiLink Deployment wizard could have crashed with a missing resource exception. This has been fixed.

CR:550252

CR Number:   550252 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 2114 14 Nov 2008 Fixed 11.0.0 1535 14 Nov 2008 Fixed 10.0.1 3799 14 Nov 2008 Fixed Description If an application made a remote procedure call that contained output parameters of type Float, and the remote server for that RPC was using one of the SAJDBC or ASEJDBC classes, then the value of the Float output parameter would always have been 0. This problem has now been fixed.

CR:550260

CR Number:   550260 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2114 17 Nov 2008 Fixed 11.0.0 1535 17 Nov 2008 Fixed Description When using UltraLite .NET, the ULConnection's SyncResult was not updated after doing a synchronization via the SYNCHRONIZE SQL statement. This has been fixed.

CR:550267

CR Number:   550267 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 2114 14 Nov 2008 Fixed 11.0.0 1535 14 Nov 2008 Fixed Description If an application set the java_vm_options option, and then attempted to start the Java VM on a Unix system, there was a chance the extra VM options would not have been used when the VM was launched. This problem has now been fixed. Note that this problem does not exist on Windows platforms.

CR:550362

CR Number:   550362 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 2026 21 Nov 2008 Fixed 11.0.0 1530 21 Nov 2008 Fixed 10.0.1 3804 21 Nov 2008 Fixed Description In a database mirroring system, if the transaction log on the primary server was renamed via a backup, the mirror server could have reported various failed assertions, for example: 100902, 100903: Unable to find table definition for table referenced in transaction log 100904: Failed to redo a database operation For this problem to have occurred, other connections must have been making changes to the database at the time the log is renamed. The problem seemed to occur more frequently if many old log files were present on the primary server. The copy of the transaction log on the mirror server would have been corrupted as a result of this problem. When the log was renamed, there was a small window during which another connection could force a log page to be sent to the mirror before the mirror was notified that the log was renamed. The transaction log lock is now held across this window.

CR:550379

CR Number:   550379 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   6.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2110 14 Nov 2008 Fixed 11.0.0 1531 14 Nov 2008 Fixed Description Sybase Central would have failed to load plugins on start-up when it was run on Korean Windows systems. The wrong codepage was being used to read the .jrp file. This has been fixed.

CR:550416

CR Number:   550416 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 2021 17 Nov 2008 Fixed 11.0.0 1536 17 Nov 2008 Fixed 10.0.1 3800 17 Nov 2008 Fixed Description If an application executed a Java in the database stored procedure, and then subsequently canceled the request, in very rare cases the server may have crashed if the cancel request coincided with the Java request actually finishing. This problem has now been fixed.

CR:550418

CR Number:   550418 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 2114 17 Nov 2008 Fixed 11.0.0 1536 17 Nov 2008 Fixed Description The Python module would have sent all "string" host variable data as varchar data. This would have resulted in an unwanted character set conversion when the desired type was binary. This has been fixed. As well, Python scripts can now pass an instance of sqlanydb.Binary in the variable data list. This will cause the value to be sent as binary data.

CR:550502

CR Number:   550502 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 2021 17 Nov 2008 Fixed 11.0.0 1537 17 Nov 2008 Fixed Description There was a small possibility that canceling an HTTP request to a SQLAnywhere service, as the server was shutting down, may have caused the server to crash. This has been fixed.

CR:550503

CR Number:   550503 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 2115 18 Nov 2008 Fixed 11.0.0 1537 18 Nov 2008 Fixed Description When running in console mode, if a SQL statement caused a warning, and the "-q" command line option was not used, the Interactive SQL utility would have prompted the user to press ENTER before continuing. This has been corrected so that the warning message is now printed, and the user is not prompted. This was the behavior in version 10.0.1 and earlier.

CR:550506

CR Number:   550506 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Nov 2008 Fixed Description In order to determine if a stored procedure returns a result set, the iAS Oracle ODBC issues a query to the Oracle database when the DSN option, "Procedure returns results" is checked. However, this query was not in an optimal form and the Oracle server needed to compile it every time before execution. The query has now been rewritten by using host variables, so that the actual SQL statement is always been the same, and the Oracle server can use it from the hash without recompiling it. To further improve the query, an extra connection parameter, ProcOwner (the long form) or POwner (the short form), has been introduced in the iAS Oracle ODBC driver. This parameter can be given as follows: -c "uid=...;pwd=...;powner=my_procedure_owner;..." If this connection parameter is given, the query will be limited to the stored procedures owned by the given owner only. Please note, if not all the stored procedures used in the synchronization have a single owner, this extra connection parameter should not be used.

CR:550525

CR Number:   550525 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 2025 18 Nov 2008 Fixed 11.0.0 1538 18 Nov 2008 Fixed Description If a communication error occurred during the last few bytes of the upload, or first few bytes of the download, UltraLiteJ would have assumed that the upload failed and revert the progress for it. In this scenario, MobiLink may have actually accepted the upload and thus its progress offsets would conflict with the client. This has been fixed.

CR:550536

CR Number:   550536 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 2024 18 Nov 2008 Fixed 11.0.0 1537 18 Nov 2008 Fixed 10.0.1 3802 18 Nov 2008 Fixed Description If an application was using Java in the database and the Java VM run out of memory, then the Java VM would have remained alive even though Java in the database requests could no longer be made. The Java VM will now exit in this situation, and new Java in the database requests will now automatically restart a new Java VM.

CR:550555

CR Number:   550555 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 2115 18 Nov 2008 Fixed 11.0.0 1537 18 Nov 2008 Fixed Description The server could have crashed when executing the WRITE_CLIENT_FILE() function, or when unloading a table to a client file. This failure was more likely when the data being written was large (on the order of tens of megabytes), and when the server was heavily loaded. This has been fixed.

CR:550669

CR Number:   550669 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2026 24 Nov 2008 Fixed 11.0.0 1539 24 Nov 2008 Fixed Description If a query plan contained a hash-based operator (group-by, distinct, or join) and the plan allowed at least one other operator to consume memory at the same time as the hash-based operator, then the execution plan could have been slower than it should have been. This slowness would also have resulted from high CPU usage. The slow behaviour did not occur if the hash-based operator appeared in a parallel execution plan, but only occurred in specific memory configurations. This slowdown has been fixed.

CR:550676

CR Number:   550676 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 2116 19 Nov 2008 Fixed 11.0.0 1537 19 Nov 2008 Fixed 10.0.1 3802 19 Nov 2008 Fixed 9.0.2 3756 19 Nov 2008 Fixed Description Attempting to construct a string value longer than the server's maximum string length (2^31-1) would have resulted in silent trucation of string data. For example, the statement: select length(repeat('a', 2000000000) || repeat('b', 2000000000)) returns 2147483647 (i.e., 2^31-1) characters, but does not raise a SQL error to indicate the operation failed and truncated the string data. This has been fixed so that SQL Error -1313 MAX_STRING_LENGTH_EXCEEDED will now be generated whenever an operation attempts to construct a string value longer than the server's internal maximum string length.

CR:550687

CR Number:   550687 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 2024 19 Nov 2008 Fixed 11.0.0 1537 19 Nov 2008 Fixed Description In very rare circumstances, a server acting as a mirror in a High Availability setup may have spuriously hit assertion 100917 - "Unable to re-read a transaction log page" while shutting down. This has been fixed.

CR:550693

CR Number:   550693 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 2024 18 Nov 2008 Fixed 11.0.0 1537 18 Nov 2008 Fixed Description The server could have generated bad query execution plans due to incorrect index statistics. This has now ben corrected.

CR:550694

CR Number:   550694 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 2024 19 Nov 2008 Fixed 11.0.0 1537 19 Nov 2008 Fixed 10.0.1 3802 19 Nov 2008 Fixed Description A string ending with an incomplete multi-byte character may have had extra characters appended to its escaped representation as generated by an UNLOAD TABLE statement. This has been fixed.

CR:550695

CR Number:   550695 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 2138 03 Feb 2009 Fixed Description Under rare circumstances, the server could have crashed while trying to load trigger definitions from the catalog. The error was likely to have occurred while trying to compile an invalid query. This problem has now been fixed.

CR:550716

CR Number:   550716 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2116 19 Nov 2008 Fixed 11.0.0 1537 19 Nov 2008 Fixed 10.0.1 3802 19 Nov 2008 Fixed Description If an application updated a proxy table and then queried the TransactionStartTime property, the value returned by the property would not have been properly updated. This problem has now been fixed.

CR:550723

CR Number:   550723 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 2116 19 Nov 2008 Fixed 11.0.0 1537 19 Nov 2008 Fixed Description If the Data tab for a table or view was selected, columns were added, modified or removed from the table or view, and the Data tab was selected again, then the column changes would not have been reflected in the Data tab. This has been fixed.

CR:550725

CR Number:   550725 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 4175 31 Jan 2011 Fixed Description A query with many predicates (original or inferred) was slower than some earlier versions, due to many semantic transformations in the parse tree. This has been fixed.

CR:550729

CR Number:   550729 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 2116 19 Nov 2008 Fixed 11.0.0 1537 19 Nov 2008 Fixed 10.0.1 3802 19 Nov 2008 Fixed Description The user-supplied comment clause provided by the WITH COMMENT clause that may accompany the BACKUP statement was written to the backup.syb log in the database character set, rather than the OS character set. All other information, such as database name is written in OS charset. This has now been fixed.

CR:550803

CR Number:   550803 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 2116 20 Nov 2008 Fixed 11.0.0 1538 20 Nov 2008 Fixed 10.0.1 3803 20 Nov 2008 Fixed Description When using the system procedure xp_sendmail(), if the message body contained a period "." on a line by itself, text following that line would have been removed from the message that was sent. A line containing a single period is the end-of-message marker for the SMTP protocol. When sending a line that begins with a single period, clients must precede it with another period character, which xp_sendmail() was not doing. This has been fixed.

CR:550838

CR Number:   550838 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 2028 20 Nov 2008 Fixed 11.0.0 1538 20 Nov 2008 Fixed 10.0.1 3803 20 Nov 2008 Fixed Description The server was not utilizing 100% of all CPUs with a workload that should have been mostly CPU bound with interleaving I/O. This would likely have occurred on lightly loaded servers. This has been fixed.

CR:550839

CR Number:   550839 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 2026 24 Nov 2008 Fixed 11.0.0 1539 24 Nov 2008 Fixed 10.0.1 3805 24 Nov 2008 Fixed Description Dynamic cache size tuning was not enabled while databases were recovering at server startup. Prior to 9.0.0, dynamic cache size tuning was enabled during recovery. This has now been fixed.

CR:550841

CR Number:   550841 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 2116 20 Nov 2008 Fixed 11.0.0 1538 20 Nov 2008 Fixed 10.0.1 3803 20 Nov 2008 Fixed Description Entity headers and a response body should not have been returned by a web service having explicitly set a 'Not Modified' HTTP status via a call to sa_set_http_header ( '@HttpStatus', '304' ). The following response headers were being returned: Transfer-Encoding: chunked Expires: ... GMT Content-Type:... As an artifact of the chunked transfer encoding, a response body consisting of a 0 chunk length was returned. This has been corrected so that a response body and the above headers will not be sent by the server when a 304 'Not Modified' HTTP status has been explicitly set.

CR:550956

CR Number:   550956 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 2002 20 Nov 2008 Fixed 11.0.0 1527 20 Nov 2008 Fixed Description The Relay Server may have reported the error "Internal error! Session number out of sync." when handling a server response. When this error occurred, further traffic going through the same Relay Server to this particular responding backend server, had an increased chance of failure. This would have reduced the quality of service to the affected Relay ServerS serving the backend server where the problem first arose. The problem also would not have cleared itself until the affected Relay Server was restarted. Traffic going through other Relay Servers in the Relay Server farm, traffic going through the same Relay Server to other backend farms, or traffic going through the same Relay Server to other servers within the same backend farm would not have been affected. This problem has now been fixed.

CR:550957

CR Number:   550957 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 2008 20 Nov 2008 Fixed 11.0.0 1528 20 Nov 2008 Fixed Description The Relay Server cannot grow the pre-allocated shared memory dynamically and it is essential that users start up the server with sufficient memory to handle foreseeable peak traffic. As well. there has been no tool for users to determine the amoumt of shared memory Relay Server was using. Now, a snap shot of shared memory usage is reported in the log file whenever the log is archived. That is when rshost.exe -ua is executed, the running Relay Server will log the current shared memory usage, archive and then truncate the log file.

CR:550985

CR Number:   550985 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 2014 21 Nov 2008 Fixed 11.0.0 1530 21 Nov 2008 Fixed Description There are documented rules for making Relay Server configuration changes in a Relay Server farm environment. When those rules were violated, a farm of Relay Servers may have resulted in heterogeneous backend farm and server indices on different Relay Servers. When a tcp load-balancer, instead of a http load-balancer, was used to maintain client-RS affinity, client sessions could not survive moving across Relay Servers in such Relay Server farms. This has been fixed by remoings the need to keep the indices in sync across all Relay Servers.

CR:550989

CR Number:   550989 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 2014 24 Nov 2008 Fixed 11.0.0 1531 24 Nov 2008 Fixed Description When the Relay Server was relaying normal Afaria traffic, it would have reported the following error and warning: ... <F0B1S0R0> IIS ReadClient error(10054): Connection was forcibly closed by the remote host. ... <F0B1S0R0> Failed reading from client. Aborting this request. ... <F0B1S1R1> Communication warning! Backend server disconnected before finishing response. These are expected, as Afaria traffic uses false http content-length. The Relay Server will now suppress these messages for Afaria traffic.

CR:550991

CR Number:   550991 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 2014 24 Nov 2008 Fixed 11.0.0 1531 24 Nov 2008 Fixed Description Client type information was not available in Relay Server log. Alternatively, users may have been able to derive the client type by looking at the optional user-agent header logging in the Web server's access log. However user-agent headers can be uncontrollable on certain mobile application platforms. Changes have been made which now allows the Relay Server to identify the following 11 types of known clients using a combination of user-agent header and proprietary header: Afaria dblsn DBMLSync MLClient // All pre-11.0.1 ml clients MLFileTransfer MLLightPoll MLMonitor UltraLite UltraLiteJ QAnywhere QAnywhereUL These client types, and the full client information (usually including build and version), will be logged by the Relay Server under verbosity level 1 or higher.

CR:550999

CR Number:   550999 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 2033 24 Nov 2008 Fixed 11.0.0 1535 24 Nov 2008 Fixed Description If an error occurred while the Relay Server Outbound Enabler was attempting to renew the up channel, it did not try again. Current client sessions going through the Outbound Enabler would not have survived. This has been fixed so that the Outbound Enabler now attempts again to renew the up channel, in order to preserve active client sessions.

CR:551002

CR Number:   551002 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 2033 21 Nov 2008 Fixed 11.0.0 1537 21 Nov 2008 Fixed Description When a backend farm or backend server was disabled, the associated Relay Sserver Outbound Enabler could still have connected to a Relay Server even though further new relay service to that farm or server was blocked. This problem has been fixed.

CR:551003

CR Number:   551003 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 2033 24 Nov 2008 Fixed 11.0.0 1538 24 Nov 2008 Fixed Description When a backend server entry was removed from the Relay Server configuration file, and the rshost -u command was applied, the removed backend server should have been disabled, but it was not. This is now fixed.

CR:551112

CR Number:   551112 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 2117 24 Nov 2008 Fixed 11.0.0 1539 24 Nov 2008 Fixed 10.0.1 3805 24 Nov 2008 Fixed Description If a database mirroring server encounters a failed assertion, the desired behaviour is for the server to exit. This allows the mirroring partner server to detect that a failure has occurred and take an appropriate action. After a failed assertion on Windows, the server was exiting in such a way as to cause Windows to display a dialog noting the abnormal exit. This prevented the server from actually exiting until action was taken to clear the dialog, and thus prevented the partner server from being notified. This has been fixed. In addition to this change, customers should consider configuring dbsupport to ensure that it does not prompt when a failure occurs. For example: dbsupport -cc autosubmit or dbsupport -cc no A future version of the software may avoid the need to configure dbsupport to prevent prompting in this situation.

CR:551124

CR Number:   551124 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 2117 25 Nov 2008 Fixed 11.0.0 1539 25 Nov 2008 Fixed 10.0.1 3805 25 Nov 2008 Fixed Description Typing completion would have inadvertently added the table's owner name when completing a column name after a table alias in the following places: 1. The column list in a SELECT statement select C. from customers C ^ 2. The WHERE clause in a DELETE statement delete from customers C where C. ^ 3. The SET or WHERE clauses of an UPDATE statement update Customers C set C. ^ update Customers C set C.City = 'Waterloo' where C. ^ This has been fixed by suppressing adding the owner's name if the inserted text immediately follows a table alias.

CR:551146

CR Number:   551146 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 2117 24 Nov 2008 Fixed Description When creating or renaming an object, if the name specified was a SQL keyword, Sybase Central could have erroneous issued a warning that the specified name would need to be double-quoted when used in a SQL script. This has been fixed. Now, Sybase Central only issues a warning if the specified name is both a SQL keyword and a SQL reserved word.

CR:551255

CR Number:   551255 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 2138 14 Jan 2009 Fixed 11.0.0 1561 14 Jan 2009 Fixed Description In certain circumstances, the server could have crashed, or otherwise failed, when executing mutliple LOAD TABLE statements concurrently when in in-memory no write mode (i.e., the server was started with the "-im nw" option). This failure was far more likely to occur if one or more of the LOAD TABLE statements failed with a SQL Error, as would be the case if the file being loaded from could not be located or opened. There was also a very small window of opportunity where the server could have crashed, or failed an assertion, even if none of the LOAD TABLE statements failed. This has now been fixed.

CR:551259

CR Number:   551259 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 2032 24 Nov 2008 Fixed 11.0.0 1539 24 Nov 2008 Fixed 10.0.1 3805 24 Nov 2008 Fixed Description If a mirror server encountered a failed assertion, the primary server could have hung when the mirror server was stopped. This has been fixed.

CR:551261

CR Number:   551261 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 2028 24 Nov 2008 Fixed 11.0.0 1540 24 Nov 2008 Fixed Description Index scans done with a snapshot isolation level could have returned incorrect results if there were concurrent UPDATE and DELETE statements to the underlying table. This has been fixed.

CR:551262

CR Number:   551262 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 2028 25 Nov 2008 Fixed 11.0.0 1540 25 Nov 2008 Fixed Description If a cached plan for a MERGE statement was reused, the MERGE statement could have failed to perform the required updates. In particular, this problem could have affected immediate materialized view maintenance, if the view was updated multiple times by the same connection. This has been fixed.

CR:551264

CR Number:   551264 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2012 24 Nov 2008 Fixed 11.0.0 1530 24 Nov 2008 Fixed Description On Windows systems, if msvcr71.dll is not on the path and Java, the Notifier, QAnywhere or SQLPassthrough were being used, then the MobiLink server would have failed to start with an error stating that MSVCR71.DLL could not be loaded. This has been fixed. A work around is to put msvcr71.dll on the path. It is installed with the JRE.

CR:551297

CR Number:   551297 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2129 17 Dec 2008 Fixed 11.0.0 1552 17 Dec 2008 Fixed Description When unloaded using the Unload utilities external unload (i.e., dbunload -xx or -xi), a table containing binary values could have had the contents of these values truncated. The binary values would typically have to have been longer than approximately 500 bytes for this bug to occur. This has been fixed. A workaround is to use an internal unload.

CR:551406

CR Number:   551406 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3738 06 Jan 2009 Fixed Description A MobiLink server with messaging enabled, using an ASE consolidated database, could have logged errors such as the following when a QAnywhere client synchronizes: Stored procedure 'ml_qa_upsert_global_prop' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output). (ODBC State = 42000, Native error code = 2812) Error: Unable to insert into table 'ml_qa_global_props_client' using upload_insert This problem may have been as a result of the fix made for Engineering case 546131. That fix involved MobiLink creating this stored procedure at startup if it does not exist. In order for MobiLink to be able to create the stored procedure, the database option "ddl in tran" needed to be true. Therefore, there are two possible workarounds for this problem: Workaround 1: Set "ddl in tran" to true in the database by executing the following SQL statements on the database, where database_name is the name of the database used as the QAnywhere server message store. use master go sp_dboption database_name, "ddl in tran", true go Workaround 2: If workaround 1 is not desirable, execute the following SQL statements on the database to make the changes described in case 546131: drop trigger ml_qa_repository_trigger go create trigger ml_qa_repository_trigger on ml_qa_repository for delete as delete from ml_qa_repository_props from deleted d, ml_qa_repository_props p where d.msgid = p.msgid delete from ml_qa_delivery from deleted d, ml_qa_delivery p where d.msgid = p.msgid delete from ml_qa_status_history from deleted d, ml_qa_status_history p where d.msgid = p.msgid go drop procedure ml_set_device_address go create procedure ml_set_device_address @device varchar(255), @medium varchar(255), @address varchar(255), @active char(1), @ignore_tracking char(1), @source varchar(255) as declare @d varchar( 255 ) if @active = 'y' begin update ml_device_address set active = 'n' where address = @address and medium = @medium and active = 'y' and device_name <> @device end select @d=device_name from ml_device_address where device_name = @device and medium = @medium if @d is null begin insert into ml_device_address( device_name, medium, address, active, ignore_tracking, source ) values( @device, @medium, @address, @active, @ignore_tracking, @source ) end else begin if @source = 'tracking' begin update ml_device_address set address = @address, active = @active, ignore_tracking = @ignore_tracking, source = @source where device_name = @device and medium = @medium and ignore_tracking = 'n' end else begin update ml_device_address set address = @address, active = @active, ignore_tracking = @ignore_tracking, source = @source where device_name = @device and medium = @medium end end go exec sp_procxmode 'ml_set_device_address', 'anymode' go create procedure ml_qa_upsert_global_prop @client varchar(128), @name varchar(128), @modifiers integer, @value varchar(16384) as begin if exists( select 1 from ml_qa_global_props gp where gp.client = @client and gp.name = @name ) update ml_qa_global_props set modifiers = @modifiers, value = @value where client = @client and name = @name else insert into ml_qa_global_props (client,name,modifiers,value) values( @client, @name, @modifiers, @value ) end go exec sp_procxmode 'ml_qa_upsert_global_prop', 'anymode' go These SQL statements make the changes to the server message store that are done automatically if database option "ddl in tran" is true. Note, MobiLink system schema changes can only be made in a major release, so these documented workarounds are provided. Later versions contain these fixes.

CR:551433

CR Number:   551433 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2119 26 Nov 2008 Fixed 11.0.0 1540 26 Nov 2008 Fixed Description Calling to the StartServer or WaitForServerShutdown methods when using the Dbmlsync .NET API, would have caused problems for some values of the timeout parameter. If the timeout value was greater than 2147483647, the WaitForServerShutdown method would always have returned DBSC_ERR_TIMED_OUT, and the StartServer method would also have returned DBSC_ERR_TIMED_OUT, unless the call was able to connect to an existing dbmlsync server on the port specified. The calls will now treat values greater than 2147483647 as equivalent to DBSC_INFINITY.

CR:551442

CR Number:   551442 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 2028 26 Nov 2008 Fixed 11.0.0 1540 26 Nov 2008 Fixed 10.0.1 3806 26 Nov 2008 Fixed Description The changes for Engineering case 547228 did not fully eliminate the assertions and other failures that could have occurred when committing deleted rows containing short strings. This has been corrected.

CR:551458

CR Number:   551458 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 2119 26 Nov 2008 Fixed 11.0.0 1540 26 Nov 2008 Fixed 10.0.1 1806 26 Nov 2008 Fixed Description If an application that was connected using jConnect called DatabaseMetaData.getPrimaryKeys() to get the primary key information for a table, the key sequence of the primary key would not have been returned correctly. This problem has now been fixed.

CR:551460

CR Number:   551460 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 2119 26 Nov 2008 Fixed 11.0.0 1540 26 Nov 2008 Fixed Description In very rare circumstances the server could have crashed when executing Java, HTTP web procedures, or Remote Data Access RPC calls. This has been fixed.

CR:551562

CR Number:   551562 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2030 28 Nov 2008 Fixed 11.0.0 1541 28 Nov 2008 Fixed Description If an execution plan contained an index-only retrieval scan and the scan had a predicate on a NUMERIC/DECIMAL or short string column, then it was possible for the scan to return the wrong result, omitting rows from the scan that should have been returned. This has been fixed.

CR:551589

CR Number:   551589 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2030 26 Nov 2008 Fixed 11.0.0 1541 26 Nov 2008 Fixed Description The batch file uljdbtserv.cmd did not work when SQL Anywhere was installed in a path that contained spaces. It also relied on environment variables other than SQLANY11. These problems have now been fixed.

CR:551593

CR Number:   551593 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 1856 27 Nov 2008 Fixed 11.0.0 1541 27 Nov 2008 Fixed Description When the MobiLink system tables were not present on the consolidated database, the MobiLink server would have displayed the following error on start-up: [-10076] The MobiLink server was unable to calculate the timestamp precision on the consolidated database using the ml_scripts_modified table. Timestamp precision related warnings will not be generated. This has been fixed. The following error will now be displayed: [-10100] The MobiLink system table 'ml_user' is missing or a table column is missing

CR:551602

CR Number:   551602 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3759 01 Dec 2008 Fixed Description The file sbgse2.dll was a new file added in a 9.0.2 EBF for the support of FIPS encryption. The EBF installer was incorrectly installing this file only when MobiLink was installed. It was therefore possible to break FIPS encryption by installing an EBF. For example: - 9.0.2.GA was installed with Mobilink deselected, - FIPS is installed, again with Mobilink deselected, - a 9,0,2 EBF is installed accepting all the defaults. FIPS gets broken because sbgse2.dll does not get installed. This has been fixed. The installer now checks if FIPS is installed before copying sbgse2.dll.

CR:551611

CR Number:   551611 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 2030 27 Nov 2008 Fixed 11.0.0 1541 27 Nov 2008 Fixed 10.0.1 3808 27 Nov 2008 Fixed Description If an application had uncommitted data in a local temporary table, and then called a Java, or any other, external environment procedure, there was a chance the server would have crashed if the application subsequently performed a rollback later on after the Java or external environment procedure had completed. This problem has now been fixed. Note that this problem will not show up if the local temporary table is declared with "on commit preserve rows" or "not transactional".

CR:551615

CR Number:   551615 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2032 05 Dec 2008 Fixed 11.0.0 2124 05 Dec 2008 Fixed Description With Microsoft SQL Server 2005 and higher, the check for the existance of an index on given table did not work with tables under schemas that did not have a corresponding user. This has been fixed. A workaround is to deploy to file and then modify the SQL file to use the sys.schemas table wherever the sysusers table is currently used, and change the id, uid column references to object_id and schema_id for that table.

CR:551622

CR Number:   551622 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 2211 17 Apr 2009 Fixed Description The system procedure sa_get_user_status() required the connection calling the procedure to have DBA authority in order to obtain information about users other than the current user. Calling sa_get_user_status() from a procedure owned by a user with DBA authority was not sufficient to return information about other users. This has been fixed. Now, if sa_get_user_status() is called from a procedure owned by a DBA, information about all users will be returned. In addition to an updated server, this fix requires the sa_get_user_status() procedure to be updated.

CR:551686

CR Number:   551686 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 2030 28 Nov 2008 Fixed 11.0.0 1541 28 Nov 2008 Fixed Description If a statement contained a work table, and evaluation of the expressions for the work table generated an error (for example, string trunctation or data overflow), then the server could have incorrectly returned an assertion failure error message (assertion 106502) instead of returning the appropriate error code. This assertion failure would have occurred only if expressions in the work table were not nullable. This problem has been fixed.

CR:551690

CR Number:   551690 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 2030 28 Nov 2008 Fixed 11.0.0 1541 28 Nov 2008 Fixed 10.0.1 3808 28 Nov 2008 Fixed 9.0.2 3759 28 Nov 2008 Fixed Description If a request was made that was larger than the packet size, then, in rare timing dependent cases, the connection could have hung until it was cancelled or dropped. Examples of requests larger than the packet size include executing a statement with long SQL text, or executing a statement with large host parameters. This has now been fixed.

CR:551692

CR Number:   551692 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 2121 02 Dec 2008 Fixed 11.0.0 1543 02 Dec 2008 Fixed 10.0.1 3809 02 Dec 2008 Fixed Description If a query consisted of a non-zero number of UNION DISTINCT operations, followed by a non-zero number UNION ALL operations, the result set could have had twice as many columns as were specified by the query. The leftmost columns would have been correct, while the rightmost extra columns were bogus. The alorithm for creating the selection list for the overall query was flawed, and has now been corrected.

CR:551695

CR Number:   551695 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2120 28 Nov 2008 Fixed 11.0.0 1541 28 Nov 2008 Fixed Description The Table editor would have allowed the removal of all columns from a new table (that is, a table which had yet to be saved to the database) by selecting all columns and then selecting Edit -> Undo, clicking the Undo toolbar button, or typing Ctrl-Z. This has been fixed. Now attempting to remove all columns from a new table causes an error dialog to be displayed.

CR:551700

CR Number:   551700 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 2121 02 Dec 2008 Fixed 11.0.0 1544 02 Dec 2008 Fixed Description Column widths in the debugger Details panel were not persistent. This has been fixed so that column widths are saved in user preferences.

CR:551739

CR Number:   551739 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2120 28 Nov 2008 Fixed 11.0.0 1542 28 Nov 2008 Fixed 10.0.1 3809 28 Nov 2008 Fixed Description When a TCP/IP connection abnormally disconnected from the server (for example due to the DROP CONNECTION statement), there was a chance that a network buffer was leaked. This has been fixed.

CR:551740

CR Number:   551740 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 2120 28 Nov 2008 Fixed 11.0.0 1542 28 Nov 2008 Fixed 10.0.1 1809 28 Nov 2008 Fixed 9.0.2 3761 28 Nov 2008 Fixed Description If a query contained an outer join and a predicate of that included the concatenation operator (||), then the server could have returned the incorrect answer for the query. In the incorrect case, the outer join was converted to an inner join. This has been fixed. For example, the following two queries should be equivalent, but the first incorrectly returned no rows: select R.row_num || 'z' x, string(R.row_num ,'z') y from dummy D left outer join rowgenerator R on 1=0 where x = 'z' select R.row_num || 'z' x, string(R.row_num ,'z') y from dummy D left outer join rowgenerator R on 1=0 where y = 'z'

CR:551747

CR Number:   551747 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 2032 28 Nov 2008 Fixed 11.0.0 1542 28 Nov 2008 Fixed 10.0.1 3809 28 Nov 2008 Fixed Description Deadlocks could have occurred more often than expected at isolation level 3, if more than one transaction attempted to update the same row concurrently. This has been corrected.

CR:551749

CR Number:   551749 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 2031 28 Nov 2008 Fixed 11.0.0 1542 28 Nov 2008 Fixed 10.0.1 3809 28 Nov 2008 Fixed Description Connections that had executed a Java stored procedure would have taken three seconds longer than necessary when attempting to disconnect. Connections that were not used to make Java stored procedure calls are unaffected by this problem. The problem has now been fixed. Note that this problem was introduced in the changes made for Engineering case 548322.

CR:551750

CR Number:   551750 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 2120 28 Nov 2008 Fixed 11.0.0 1542 28 Nov 2008 Fixed 10.0.1 3809 28 Nov 2008 Fixed Description Executing a Java stored procedure that attempted to fetch resources using getResourceAsStream() or getResource(), would have had the fetch of the resource fail. This problem has now been fixed. Note that due to differences in compression schemes, it is strongly recommended that jars containing textual resources be created without compression turned on. For jars containing binary resources (ex. movies or images), using a compressed jar will work fine.

CR:551751

CR Number:   551751 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 2120 28 Nov 2008 Fixed 11.0.0 1542 28 Nov 2008 Fixed Description Attempting to use the QAnywhere Server to cancel a message in an Ultralite Client Message Store would have failed with a NullPointerException. This problem was more likely to occur when using the Sybase Central plugin to connect to an Ultralite client database and then attempting to cancel a message. This has been fixed.

CR:551752

CR Number:   551752 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 2031 02 Dec 2008 Fixed 11.0.0 1544 02 Dec 2008 Fixed Description Calling the system procedure sa_server_messages() could have resulted in the server crashing. This problem would have been rare, requiring a busy server to reproduce. This has been fixed.

CR:551813

CR Number:   551813 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2030 01 Dec 2008 Fixed 11.0.0 1541 01 Dec 2008 Fixed 10.0.1 3808 01 Dec 2008 Fixed Description Messages printed to the MobiLink server log could have been mangled on systems with non-English character sets. This would have happened most often on errors from QAnywhere or the Notifier. This has now been fixed.

CR:551820

CR Number:   551820 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 2121 02 Dec 2008 Fixed 11.0.0 1543 02 Dec 2008 Fixed 10.0.1 3811 02 Dec 2008 Fixed Description If a PARAMETERS statement was run from an Interactive SQL window a dialog was displayed prompting for the values. If the PARAMETERS statement was then rerun, the prompt was not displayed, and the previously values were used. This behavior was not intentional and has been corrected. Now, the prompt is displayed each and every time the PARAMETER statement is executed.

CR:551839

CR Number:   551839 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 2121 02 Dec 2008 Fixed 11.0.0 1541 02 Dec 2008 Fixed Description Host variables used as function arguments did not work correctly. This has now been fixed.

CR:551850

CR Number:   551850 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 3762 02 Dec 2008 Fixed Description Attempting to execute a badly formed UPDATE statement of the form "update test X set X..a = 2", where test is a proxy table, would very likely have lead to a server crash. This problem has now been fixed.

CR:551858

CR Number:   551858 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2030 02 Dec 2008 Fixed 11.0.0 1541 02 Dec 2008 Fixed 10.0.1 3808 02 Dec 2008 Fixed Description If a remote server used character length semantics for a string column (e.g. a SQLAnywhere remote with an nchar column, or an UltraLiteJ remote with a char column), and the column on the remote database was smaller than the column in the consolidated database, then the MobiLink server could have failed to report the truncation. The server was already counting the number of characters in the the column coming out the consolidated, but it wasn't checking the length against the domain info given by the remote. This has now been fixed

CR:551944

CR Number:   551944 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 2122 02 Dec 2008 Fixed 11.0.0 1544 02 Dec 2008 Fixed 10.0.1 3811 02 Dec 2008 Fixed 9.0.2 3762 02 Dec 2008 Fixed Description The fix for Engineering case 549983 introduced a problem such that two simultaneous remote data access requests from two separate connections could have caused the server to crash. This problem has now been fixed.

CR:551953

CR Number:   551953 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2122 02 Dec 2008 Fixed 11.0.0 1544 02 Dec 2008 Fixed Description It was possible for the MobiLink client .NET API to have thrown an unhandled socket exception when attempting to disconnect from a socket that had been forcibly closed by the operating system. This exception is now caught and handled within the dbmlsync .NET API.

CR:551956

CR Number:   551956 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2147 05 Feb 2009 Fixed 11.0.0 1571 05 Feb 2009 Fixed 10.0.1 3842 05 Feb 2009 Fixed 9.0.2 3789 05 Feb 2009 Fixed Description When the TargetType parameter to the ODBC function SQLGetData() is SQL_C_DEFAULT, the driver selects the default C data type based on the SQL data type of the source. For NCHAR types, the Microsoft ODBC driver selects a SQL_C_CHAR binding. Microsoft acknowledges in its knowledgebase article http://support.microsoft.com/default.aspx/kb/293659 that to do so is an error, but states that it does this to support older legacy applications. The SQL Anywhere ODBC driver selected a SQL_C_WCHAR binding. This caused problems with applications like Microsoft Access, that expected the Microsoft ODBC behaviour. This problem in Access could have been seen when setting up a linked table using the SQL Anywhere ODC driver to a database table containing NCHAR, NVARCHAR, or LONG NVARCHAR column types. The resulting table columns were displayed with "#deleted" values. To conform to the Microsoft ODBC driver behaviour, the SQL Anywhere ODBC driver has been changed. Now,the SQL Anywhere ODBC driver selects a SQL_C_CHAR binding for NCHAR, NVARCHAR, and LONG NVARCHAR (including NTEXT) types when the "MS Applications ( Keys In SQLStatistics)" checkbox is selected in the ODBC Administrator configuration dialog for SQL Anywhere datasources. This option can also be specified as the connection parameter "KeysInSQLStatistics=YES" in a SQL Anywhere ODBC driver connection string. This change affects any ODBC function, like SQLBindCol, SQLBindParameter, and SQLGetData, where SQL_C_DEFAULT can be specified.

CR:551967

CR Number:   551967 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 2122 02 Dec 2008 Fixed 11.0.0 1544 02 Dec 2008 Fixed Description Attempting to view a column value which contained image data would have crashed Sybase Central. This has been fixed.

CR:551978

CR Number:   551978 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 2122 02 Dec 2008 Fixed 11.0.0 1544 02 Dec 2008 Fixed 10.0.1 3811 02 Dec 2008 Fixed 9.0.2 3762 02 Dec 2008 Fixed Description If an application called ResultSet.getString() on a uniqueidentifier column, the iAnywhere JDBC driver would have incorrectly returned a string of binary bytes. This problem has now been fixed and the iAnywhere JDBC driver now returns a properly formatted GUID string.

CR:552057

CR Number:   552057 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 2122 03 Dec 2008 Fixed 11.0.0 1545 03 Dec 2008 Fixed 10.0.1 3812 03 Dec 2008 Fixed Description In general, applications that use Java in the database support install the classes and jars to be used into the database. Doing so allows the database to be moved from one machine to another, or from one platform to another. The other benefit of installing classes and jars into the database is that the SQL Anywhere class loader can then be used to fetch the classes and resources from the database allowing each connection that is using Java in the database support to have its own instance of these classes and its own copy of static variables within these classes. In VERY rare cases, it is beneficial to have the system class loader load a class instead of the SQL Anywhere class loader. The only real reason for having the system class loader load the class is that statics within classes loaded by the system class loader can then be shared across all connections using Java in the database support. There are of course many reasons why the system class loader should not be used: 1) since statics are shared across all connections, there is an issue with the security of data 2) mixing classes loaded by the SA class loader and the system class loader can lead to the VM throwing IllegalAccess and ClassCast exceptions 3) there is now the danger that the system class loader will get used for loading classes that should actually have been loaded by the SA class loader Because of these potentially serious problems, it has always been STRONGLY recommended that all classes and jars to be used for Java in the database support be explicitly installed within the database. However, for those rare cases where the class really needs to be loaded by the system class loader, the server's classpath argument (-cp) can be used to add directories and jars to the classpath that the server builds for launching the JVM. Unfortunately, as of version 10.0, the server's classpath argument was being ignored when launching the JVM. This problem has now been fixed and the server's classpath argument is now properly appended to the classpath the server builds when launching the VM. Again, the use of the server's classpath argument is STRONGLY discouraged; instead, it is STRONGLY recommended that all classes and jars to be used for Java in the database support be installed explicitly in the database.

CR:552066

CR Number:   552066 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 2124 03 Dec 2008 Fixed 11.0.0 1545 03 Dec 2008 Fixed 10.0.1 3813 03 Dec 2008 Fixed Description If a SQL Anywhere database used with Replication Server was unloaded using the Unload utility (dbunload), some tables and procedures used by Replication Server would not have been included. This has been fixed.

CR:552067

CR Number:   552067 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2246 15 Dec 2008 Fixed 11.0.0 1618 20 May 2009 Fixed 10.0.1 3894 20 May 2009 Fixed Description The server could have become deadlocked if the 'wait after end' option was used when performing a backup. For the deadlock to have occurred, there must have been an active transaction when the backup attempted to truncate the log, and then a checkpoint and commit must have occurred, in that order on separate connections, between the time that the backup attempted to truncate the log and when the backup noticed that there was an active transaction (a very short time interval). This has now been corrected. A work around in most cases is to omit the 'wait after end' option, as it is often not required. Workaround Description  None.

CR:552077

CR Number:   552077 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 2032 04 Dec 2008 Fixed 11.0.0 1545 04 Dec 2008 Fixed 10.0.1 3812 04 Dec 2008 Fixed Description The server could have become deadlocked when frequently executing UPDATE ststements on the same set of rows. This would only have occurred if the table being updated had a non-unique index defined. This has now been fixed.

CR:552094

CR Number:   552094 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 2124 08 Dec 2008 Fixed 11.0.0 1545 08 Dec 2008 Fixed Description When AES_FIPS or AES256_FIPS database encryption was used for a long enough period of time, the server would have eventually failed to allocate memory, due to a small memory leak. This included use of the encrypt() or hash() functions with FIPS algorithms, or if the -fips server command line option was used. There was also a leak on the client side of approximately 1k per TLS connection attempted. All of these leaks have now been fixed.

CR:552144

CR Number:   552144 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2124 05 Dec 2008 Fixed Description The SQL script file passed to UltraLites ALTER DATABASE SCHEMA FROM FILE statement and used by the SQL Passthrough feature, must have been in a specific format. Each SQL statement must have ended with go on a line by itself. For example: ALTER TABLE T RENAME R go This format was assumed and if 'go' was not found on a line by itself, nothing would have been executed, but no error would have been generated. Now, the error SQLE_SCRIPT_MISSING_DELIMITER (-1315) is generated if 'go' is not found on a line by itself. Moreover, with this change the file may end with 'go<eof>' (previously, it had to be 'go\n'). Note that even single line script files must end with the go separator. This includes SQL Passthrough scripts. So the following is a correct example of adding a SQL Passthrough script: call ml_add_passthrough_script( script1, null, null, ALTER TABLE T RENAME R\ngo ) If an error occurs and only part of the file is applied, the database must be shutdown and restarted (and the schema will as it was prior to the ALTER DATABASE statement).

CR:552171

CR Number:   552171 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 2033 18 Dec 2008 Fixed 11.0.0 1553 18 Dec 2008 Fixed Description When applying a series of renamed transaction logs to the server, or when the MobiLink client (dbmlsync) reads a series of renamed transaction logs, the error "Missing transaction log(s) after file ..." cound have been reported. The offsets reported in the error message (between the end of one log and the start of the next) can be subtracted to determine the size of gap; this apparent gap would have been exactly 24 bytes. With a 4K pagesize, this would have happened to roughly 1 out of every 4000 renamed logs; it is less likely with a larger pagesize. It was only a problem when the affected log was the last one before the online (currently active) log. This has been fixed. Note, despite the reported gap, no data was actually lost from the logs. The data can be recovered by using dbtran to generate a .SQL script and then applying this to the database.

CR:552186

CR Number:   552186 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 3812 04 Dec 2008 Fixed Description Truncating a table with deleted rows could have caused the server to fail assertion 201501 - "Page for requested record not a table page or record not present on page". For this to have occurred, the table must have contained string data shorter than a page, and one of those short values (which had to have come from one of the deleted rows) must have been held active in an open cursor or variable. This has now been fixed.

CR:552189

CR Number:   552189 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 2032 05 Dec 2008 Fixed 11.0.0 1545 05 Dec 2008 Fixed 10.0.1 3812 05 Dec 2008 Fixed Description The changes for Engineering case 545904 introduced a problem where the server could have issued a variety of assertions, including "200610: Attempting to normalize a non-continued row" while concurrently updating rows containing blobs. For this to have occurred, the string values must have been less than a page size, but larger than the column's inline amount. This has been fixed.

CR:552196

CR Number:   552196 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2124 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed Description Quoted SQL identifiers that were part of the Interactive SQL utility's command line were inadvertently stripped of their quotes before being passed to the database. This has been fixed. For example, the following command line was not being handled correctly: dbisql -c "uid=dba;pwd=sql" CREATE TABLE "123TEST" ( c INT )

CR:552210

CR Number:   552210 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3764 08 Dec 2008 Fixed Description After selecting the Network tab in the ODBC Administrator (ODBCAD32) for ASA 9.0.2 data sources, it was not possible to configure RSA_TLS_FIPS. The RSA_TLS option would have been selected and the suboptions string would have been garbled. This problem has been fixed.

CR:552226

CR Number:   552226 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 2124 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed Description The cast of a LONGVARCHAR value to VARCHAR value could have caused a crash. This has now been fixed.

CR:552293

CR Number:   552293 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 2032 05 Dec 2008 Fixed 11.0.0 2032 05 Dec 2008 Fixed Description Execution of a query with a left outer join could have caused database corruption when the null-supplying table supplied a null row, and that table was subsequently updated. This has now been corrected.

CR:552302

CR Number:   552302 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 2031 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed 10.0.1 3814 08 Dec 2008 Fixed Description If the HTTP listener was enabled, the server may have crashed on shutdown. There is no risk of data corruption. This has been fixed.