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

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

CR:641280

CR Number:   641280 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2582 14 Sep 2010 Fixed 12.0.1 3036 28 Sep 2010 Fixed Description Attempting to execute a START JAVA command from the Interactive SQL utility (dbisql) would have failed if it was installed from a 64 bit MSI created by the Deployment wizard. The error message would have been: "***** SQL error: External environment could not be started, 'external executable' could not be found". This has been corrected.

CR:641285

CR Number:   641285 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2582 14 Sep 2010 Fixed 12.0.1 3037 28 Sep 2010 Fixed Description It was possible that the SQL Anywhere Monitor would have allowed read-only users to resolve alerts. This has been fixed. Now, only operators and administrators may resolve alerts.

CR:641291

CR Number:   641291 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2582 14 Sep 2010 Fixed 12.0.1 3037 28 Sep 2010 Fixed Description Large downloads on BlackBerry devices, and simulators, would have started to fail with communication errors because the garbage collector would have done full GCs and locked out the liveness thread. This has been fixed by ensuring that all downloaded rows are row limited (requires enabling of row limiting and lazy loading).

CR:641296

CR Number:   641296 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3089 04 Nov 2010 Fixed 12.0.0 2606 04 Nov 2010 Fixed 11.0.1 2520 04 Nov 2010 Fixed Description When choosing to localize with the Deployment wizard, the Installation Wizard would have appeared localized, but Language was not set in the registry on the target machine. This has been corrected so that the SQL Anywhere Language registry entry is now set to match the deployment language.

CR:641299

CR Number:   641299 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2582 14 Sep 2010 Fixed 12.0.1 3037 22 Sep 2010 Fixed Description When adding a new consolidated database to a MobiLink project, it is scanned to see if any remote schema names have been installed previously and copies them into the project file. However, if there were multiple remote schema names, only one would have been imported. This has been fixed.

CR:641308

CR Number:   641308 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2582 14 Sep 2010 Fixed 12.0.1 3037 22 Sep 2010 Fixed Description The 64-bit versions of the Log Translation utility (dbtran), SQL Remote (dbremote) or the MobiLink client (dbmlsync), could have crashed when processing a transaction log containing an ALTER SYNCHRONIZATION SUBSCRIPTION statement. This has been fixed.

CR:641328

CR Number:   641328 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) 12.0.1 3083 01 Nov 2010 Fixed 12.0.0 2604 01 Nov 2010 Fixed 11.0.1 2517 01 Nov 2010 Fixed Description A statement such as the following could have incorrectly given an error: select row_num, if row_num < 1 then 1+row_num/0 endif x from rowgenerator order by x option(force no optimization) The sub-expression 1+row_num/0 should never be evaluated as the condition row_num<1 is never true. However, in a simple statement processed by bypassing the query optimizer, if a Sort was needed to order the rows of the result, an error could be incorrectly given. This problem has been fixed.

CR:641360

CR Number:   641360 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3047 24 Sep 2010 Fixed 12.0.0 2587 24 Sep 2010 Fixed 11.0.1 2499 24 Sep 2010 Fixed 10.0.1 4126 24 Sep 2010 Fixed Description The server may have returned an incorrect result set for a query that contained a GROUP BY clause with distinct arguments, and the GROUP BY was executed using the low memory strategy. This has been fixed. Workaround Description  While there is a sort of self-healing that occurs after this aggregate causes an incorrect result to be return, the customer's main concern is that this effects a report that is submitted to a federal regulatory agency and the inaccuracy is subject to fines. So since this is intermittent and often goes undetected any workaround is problematic unless it can be proven to address the underlying problem.

CR:641434

CR Number:   641434 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3043 21 Sep 2010 Fixed 12.0.0 2585 21 Sep 2010 Fixed 11.0.1 2497 21 Sep 2010 Fixed Description If a large number of connections that had made external environment calls all shut down at the same time, then there was a chance the server would have hung one of the clients trying to shut down. In some cases, all the requests to shut down the connections would have succeeded, but the server would have subsequently hung when asked to terminate. Both of these problems have now been fixed.

CR:641485

CR Number:   641485 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3038 20 Sep 2010 Fixed 12.0.0 2583 20 Sep 2010 Fixed 11.0.1 2495 20 Sep 2010 Fixed 10.0.1 4122 20 Sep 2010 Fixed Description Attempting to make a connection with invalid TCPIP protocol options could have caused a crash in the client library. This has been fixed.

CR:641487

CR Number:   641487 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 2495 16 Sep 2010 Fixed 10.0.1 4122 16 Sep 2010 Fixed Description If a server was started with -o <file name>, then stopped and immediately started again with the same -o <file name>, the server could have failed to start with the errors "Invalid database server command line" or "Can't open Message window log file: <file name>". This failure was rare and timing dependent, and has now been fixed so the second server will successfully start.

CR:641490

CR Number:   641490 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 4095 01 Apr 2014 Fixed Description Under exceptionally rare circumstances, the server may have crashed while executing a parallel plan with outer joins in the parallel plan parts. This has been fixed.

CR:641702

CR Number:   641702 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4129 01 Oct 2010 Fixed Description The MSI install built using the Deployment wizard did not include the Charsets directory. This is used by the Unload Support feature, and has now been added.

CR:641777

CR Number:   641777 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3051 30 Sep 2010 Fixed 12.0.0 2590 30 Sep 2010 Fixed Description The EBF installs for SQL Anywhere and the SQL Anywhere Monitor did not copy the ReadMe_EBF.html file to the product folder. This has been corrected so that now it is.

CR:641793

CR Number:   641793 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3040 20 Sep 2010 Fixed 12.0.0 2584 20 Sep 2010 Fixed 11.0.1 2496 20 Sep 2010 Fixed Description In very rare cases, the server could have hang if an external environment call was made at the same time that the server performed some maintenance on the database. This has now been corrected.

CR:641806

CR Number:   641806 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3044 24 Sep 2010 Fixed 12.0.0 2585 24 Sep 2010 Fixed 11.0.1 2499 24 Sep 2010 Fixed Description The date_format, timestamp_format and uuid_has_hyphens options stored in a text configuration were not respected during an immediate text index update. Immediate text index updates incorrectly used the current connection option values. This has been fixed. If an existing immediate text indexes is suspected of being effected by this problem then the text index needs to be refreshed after applying this fix.

CR:641965

CR Number:   641965 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3042 21 Sep 2010 Fixed 12.0.0 2584 21 Sep 2010 Fixed Description The Relay Server could have failed to reconnect the Outbound Enabler's down channel, and displayed the following error message: "RSE1015: Invalid first 'OE_DNCHANNEL_RECONNECT' packet from the outbound enabler". This has been fixed.

CR:641994

CR Number:   641994 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3039 20 Sep 2010 Fixed Description With the release of the 12.0.0 SQL Anywhere Monitor, it is possible to monitor more resources than previously possible. Unfortunately though, monitoring large numbers of resources presents a challenge in the number of alerts it's possible to receive. To this end, new functionality has been added to the Monitor to make both filtering and deleting large sets of alerts easier. The first new feature is two additional options for sending alert notifications via email, found under Administration -> Configuration -> Edit... -> Alert Notification The new options behave as follows: - "Only send email notifications for high-priority alerts", when set, will filter emails sent to operators in such a way that operators will only receive email notification when high-priority alerts are raised. Medium and low priority alerts will continue to be raised and will be viewable/resolvable from the main web-based UI as before. - "Do not send more than the given number of email notifications per day", when set, places a hard cap on the number of email notifications sent to each operator per day. When an operator has reached their cap of email notifications for a day, an email is sent to them alerting them of this fact, as well as informing them of ways to reset the cap. This cap is reset every night at midnight, at which point the operators can once again begin to receive email notifications. Alternatively, an administrator can click the "Reset Email Notification Sent Count" button to immediately reset the caps so that operators may begin to receive email notifications again. The second set of changes affects how the Alert Widget deletes alerts. Previously, the user would select one or more alerts and click the delete button, deleting those alerts. However, in the case of even just a few hundred alerts, this becomes unmanageable. With this change, when the user clicks the delete button on an Alert Widget, a new dialog is displayed. Its three options behave as follows: - "Delete selected alerts" is the same as the 12.0.0 behaviour. Only those alerts selected in the Alert Widget will be deleted. - "Delete alerts received before" will delete all alerts received before the given time. Note that this option will only delete the alerts for resources included in this Alert Widget; if a resource's alerts are not being shown in the Alert Widget, its alerts will not be deleted by this option. - "Delete alerts for the following resource" will delete all alerts for the selected resource. The list of resources to choose from is the same as the list of resources whose alerts are viewable from the Alert Widget.

CR:641998

CR Number:   641998 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3045 22 Sep 2010 Fixed 12.0.0 2586 22 Sep 2010 Fixed 11.0.1 2498 22 Sep 2010 Fixed Description When in Debug mode, the SQL editor for a view, trigger, procedure, function or event, contained a menu item and toolbar button for the Query Editor, even though the contents of the editor could not be modified. Similarly, the SQL editor for a trigger, procedure or function, contained menu items for translating the SQL to Watcom-SQL or Transact-SQL dialects. Now, these menu items and toolbar buttons are no longer displayed.

CR:642010

CR Number:   642010 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) 12.0.1 3043 21 Sep 2010 Fixed 12.0.0 2585 21 Sep 2010 Fixed 11.0.1 2497 21 Sep 2010 Fixed Description If a Initialization utility command line used exceptionally long filenames and encryption key, and the encryption key contained at least one single quote character, the resulting database may have been unusable. The server would always have reported an incorrect encryption key. This has been fixed.

CR:642015

CR Number:   642015 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2497 21 Sep 2010 Fixed 10.0.1 4124 21 Sep 2010 Fixed Description Due to an uninitialized variable in the iAnywhere JDBC driver, applications using the driver (such as the MobiLink server) could have crashed when trying to access a result set. This problem has now been fixed.

CR:642131

CR Number:   642131 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2566 21 Sep 2010 Fixed Description On Linux systems, the Relay Server could have failed to reconnect the Outbound Enabler's down channel, and displayed the following error message: "RSE1015: Invalid first 'OE_DNCHANNEL_RECONNECT' packet from the outbound enabler". This has been fixed.

CR:642172

CR Number:   642172 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3044 21 Sep 2010 Fixed 12.0.0 2585 21 Sep 2010 Fixed Description Even with the changes for Engineering case 629453, on Ubuntu systems, clicking on a result set cell and choosing 'Edit in Window' would have opened the edit dialog and left focus in the cell. This has been fixed.

CR:642173

CR Number:   642173 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) 12.0.1 3044 21 Sep 2010 Fixed 12.0.0 2585 21 Sep 2010 Fixed 11.0.1 2498 21 Sep 2010 Fixed Description Erroneous results were returned when host indicator variables were used multiple times. This has been corrected. For example, the statement SELECT 1 + :x + :x:y + :x would generate incorrect results when a value was substituted for :x. A work-around would be to remove the :y from the statement, since host indicator variables are parsed but not processed in UltraLite.

CR:642237

CR Number:   642237 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3044 22 Sep 2010 Fixed 12.0.0 2586 22 Sep 2010 Fixed Description Certain shapes of polygons when being loaded in a round-earth SRID, would have incorrectly given an invalid polygon error. An example of this is: "select new ST_Polygon( 'Polygon((90 0, 90 -10, 100 -10, 100 0, 97 0, 97 10, 93 10, 93 0, 90 0))', 4326 )" This has been fixed. One workaround is to start the polygon on a different point around its ring.

CR:642245

CR Number:   642245 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3044 22 Sep 2010 Fixed 12.0.0 2585 22 Sep 2010 Fixed Description Calling Synchronize with a ULSyncProgressListener would have resulted in a thread left hanging after the sync had completed, which could have resulted in the application executable remaining locked after the application had shut down, requiring a device reset. This has been fixed.

CR:642249

CR Number:   642249 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3045 23 Sep 2010 Fixed 12.0.0 2586 23 Sep 2010 Fixed Description If a synchronization model from version 10 or 11 was added to a version 12 synchronization project, the column mapping directions were not displayed correctly for upload-only or download-only table mappings. This was only a display problem; the synchronization scripts were generated correctly. This has been fixed.

CR:642285

CR Number:   642285 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3045 23 Sep 2010 Fixed 12.0.0 2586 23 Sep 2010 Fixed Description Under rare circumstances, an exception (java.lang.NullPointerException) could have been thrown when switching to another synchronization model in the project. This has been fixed.

CR:642313

CR Number:   642313 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3066 12 Oct 2010 Fixed 12.0.0 2596 12 Oct 2010 Fixed 11.0.1 2509 12 Oct 2010 Fixed Description Execution of the statement "BACKUP DATABASE DIRECTORY '' TRANSACTION LOG RENAME TRANSACTION LOG ONLY" would have left a gap in the offsets between the renamed transaction log and the live transaction log. This would have affected replication, synchronization and the ability to recover from backups. This has been fixed. Workaround Description  Create an actual backup of the transaction log by putting a non-empty value in the DIRECTORY clause. If this is done, the offsets will match properly.

CR:642329

CR Number:   642329 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) 12.0.1 3046 23 Sep 2010 Fixed 12.0.0 2586 23 Sep 2010 Fixed 11.0.1 2499 23 Sep 2010 Fixed Description An attempt to use an exception name in a procedure when the exception had not been declared did not report an error. This has been fixed.

CR:642398

CR Number:   642398 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2566 23 Sep 2010 Fixed Description When running on Linux systems, if the Relay Server State Manager (rshost) was not running and a client made a request invoking the client module, this request could have crashed the module. This has been fixed.

CR:642399

CR Number:   642399 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Linux Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2566 23 Sep 2010 Fixed Description When connecting a device that supports the OMA Device Management protocol directly to an Apache based Relay Server, the device would have displayed an error stating Invalid Host Address. The Afaria Server still provisions the device, but the Afaria OMA-DM Server logs state: "... authentication: no credentials in message . When sending the response back to the client, the Relay Server (when run on Linux systems) was incorrectly setting the content-type header as text/plain instead of application/vnd.syncml.dm+wbxml. This has now been fixed.

CR:642441

CR Number:   642441 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3080 29 Oct 2010 Fixed 12.0.0 2602 29 Oct 2010 Fixed Description When using the Browse button in the Deployment wizard to select the directory where the .msi file is to be created, the resulting file would only have been 199 kb in size and would have generated an error when attempting to run it. The problem would not have occurred when deploying to the default location, or manually typing or pasting in the location. This has been fixed. Workaround Description  Create the .msi in the default location, or manually type in the location.

CR:642460

CR Number:   642460 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3046 24 Sep 2010 Fixed 12.0.0 2587 24 Sep 2010 Fixed 11.0.1 2509 13 Oct 2010 Fixed Description Starting a copy node server while updates were being applied at the primary server, could have resulted in a variety of failures, including assertion failures 100902 or 100903, or checksum failures. This has been fixed.

CR:642524

CR Number:   642524 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3052 30 Sep 2010 Fixed 12.0.0 2501 30 Sep 2010 Fixed 11.0.1 2501 30 Sep 2010 Fixed 10.0.1 4128 30 Sep 2010 Fixed Description The server could have become unresponsive when processing index scans in which a residual predicate continually rejected candidate rows for the duration of the scan. This has been fixed.

CR:642563

CR Number:   642563 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3052 29 Sep 2010 Fixed 12.0.0 2591 29 Sep 2010 Fixed 11.0.1 2501 29 Sep 2010 Fixed Description When running the install generated by the Deployment wizard, the ADO.NET provider was not registered correctly. Running the utility setupvspackage.exe manually after the install finished would have correctly registered the .NET provider. This has now been fixed.

CR:642568

CR Number:   642568 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3069 18 Oct 2010 Fixed 12.0.0 2598 18 Oct 2010 Fixed 11.0.1 2510 18 Oct 2010 Fixed 10.0.1 4135 18 Oct 2010 Fixed Description If a synchronization failed with a protocol error, some later synchronization could have failed with a translator or right truncation error. It was also possible that instead of failing, the later sync could have made use of the failed syncs to, for example, insert it into the consolidated. These issues have been fixed.

CR:642575

CR Number:   642575 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3051 12 Oct 2010 Fixed 12.0.0 2594 12 Oct 2010 Fixed Description Diagnostic tracing could have hung, or dropped connections, or possibly crashed the server, if a connection was canceled or a connection to the tracing database was dropped. Mirroring or read-only scale-out could also have hung or dropped connections if a connection was canceled. This has been fixed.

CR:642600

CR Number:   642600 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3066 13 Oct 2010 Fixed 12.0.0 2596 13 Oct 2010 Fixed 11.0.1 2502 13 Oct 2010 Fixed Description When attempting to start the server on a TeamPad series model of a Fujitsu CE device, the server would always have failed, report the error "Not enough memory". This problem has been fixed

CR:642765

CR Number:   642765 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12 Oct 2010 DEFER Description 11.0.1 SQL Anywhere Monitor can not detect long running queries

CR:642826

CR Number:   642826 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4127 27 Sep 2010 Fixed Description A NullPointerException could have occurred when the DetailsList lost focus. This has been fixed.

CR:642827

CR Number:   642827 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3046 27 Sep 2010 Fixed 12.0.0 2586 27 Sep 2010 Fixed 11.0.1 2499 27 Sep 2010 Fixed Description The Relay Server for IIS7 would have failed to stream Afaria downloads, and was causing the Afaria client to timeout. This has been fixed.

CR:642833

CR Number:   642833 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3068 27 Sep 2010 Fixed 12.0.0 2599 27 Sep 2010 Fixed Description When under heavy load, the server may have crashed when receiving multiple requests on an HTTP connection. This has been fixed.

CR:642836

CR Number:   642836 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3050 27 Sep 2010 Fixed 12.0.0 2589 27 Sep 2010 Fixed Description When monitoring a primary server in a mirrored environment and a failover occurred, the Monitor would have continued to report the primary was unavailable, rather than failing over to the new primary and continuing to Monitor. It is now possible to configure the resource such that when a failover occurs, the Monitor will switch to the new primary and continue monitoring. In this case, rather than an availability alert, the user will get a "Mirror Unavailable" alert. To implement this new behaviour, do the following when configuring the resource for monitoring: - When providing connection information in the new SA resource wizard, provide a comma separated list of hostname:port values for the "Host" input (e.g. "my-primary-server:2638,my-mirror-server:49152"). See http://dcx.sybase.com/index.html#1200en/dbadmin/host-con-parm.html*d5e18361 for more information. - In the "Other" input, add "NODETYPE=primary". See http://dcx.sybase.com/index.html#1200en/dbadmin/node-type-conparm.html*d5e18888 for more information. - In the "Server" input, use the alternate server name for your mirroring system. See http://dcx.sybase.com/index.html#1200en/dbadmin/dbserver-s-41861441.html*d5e16685 for more information. If the the location of both the primary and mirror servers is not specified, the behaviour is the same as before (i.e. an availability alert is raised for the primary and no switch to the new primary occurs).

CR:642865

CR Number:   642865 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3050 28 Sep 2010 Fixed 12.0.0 2588 28 Sep 2010 Fixed 11.0.1 2500 28 Sep 2010 Fixed 10.0.1 4127 28 Sep 2010 Fixed Description The SQL Anywhere OLE DB provider was ignoring the Location and Initial Catalog connection parameters. This problem has been fixed. "Location" can now be used to specify the host name and port of the database server. The form is hostname:port (e.g., username-pc:3628). "Location" is mapped to the SQL Anywhere "Host" connection parameter for version 12 or later and the "CommLinks" connection parameter for version 11 or earlier. "Initial Catalog" can now be used to specify the database to connect to when more than one database has been started by a SQL Anywhere database server. "Initial Catalog" is mapped to the SQL Anywhere "DatabaseName" (DBN) connection parameter.

CR:642889

CR Number:   642889 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) 12.0.1 3050 28 Sep 2010 Fixed 12.0.0 2590 28 Sep 2010 Fixed 11.0.1 2500 28 Sep 2010 Fixed Description The changes for Engineering case 615994 introduced a problem where refreshing the Domains folder, after having selected a non-proxy table's Columns tab, would have caused a "Resource governor" error. This has been fixed.

CR:642971

CR Number:   642971 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3050 28 Sep 2010 Fixed 12.0.0 2590 28 Sep 2010 Fixed 11.0.1 2500 28 Sep 2010 Fixed Description The utility SetupVSPackage.exe would have thrown the error "Object reference not set to an instance of an object.", if the .NET Framework 4.0 was not installed. This problem has been fixed.

CR:642980

CR Number:   642980 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3047 26 Oct 2010 Fixed 12.0.0 2588 26 Oct 2010 Fixed 11.0.1 2499 26 Oct 2010 Fixed 10.0.1 4126 26 Oct 2010 Fixed Description A number of corrections and improvements have been made to the SQL Anywhere OLE DB schema rowset support procedures: - If a catalog name is specified as one of the schema restrictions, the procedure will make sure it matches the current catalog. If it does not, a single row will be returned with NULLs. - Any rowset that can return a catalog name in a column will now return the current database name in that column instead of NULL. - The rows returned in the DBSCHEMA_PROVIDER_TYPES rowset have been slightly reordered for better results with Microsoft tools. This was done since Microsoft tools ignore the BEST_MATCH column and use the first row that matches the datatype it is searching for. - In the DBSCHEMA_PROVIDER_TYPES schema, the XML datatype will now set the DATA_TYPE column to 141 (DBTYPE_XML), the IS_LONG column to 1 and return 2GB instead of 32767 for COLUMN_SIZE. - In the DBSCHEMA_PROVIDER_TYPES schema, the TIMESTAMP WITH TIME ZONE datatype will now set the DATA_TYPE column to 146 (DBTYPE_DBTIMESTAMPOFFSET). This is supported in version 12 or later of SQL Anywhere. - An entry for the REAL datatype was missing from the DBSCHEMA_PROVIDER_TYPES rowset. This row has been added. To install these updates into a database, the Upgrade utility (dbupgrad), or the ALTER DATABASE UPGRADE statement can be used.

CR:642996

CR Number:   642996 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3051 29 Sep 2010 Fixed 12.0.0 2590 29 Sep 2010 Fixed 11.0.1 2501 29 Sep 2010 Fixed 10.0.1 4128 29 Sep 2010 Fixed Description If a database encrypted with AES_FIPS or AES256_FIPS was copied to a CE device, the server would have been unable to start it. This has been fixed.

CR:643019

CR Number:   643019 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3051 29 Sep 2010 Fixed 12.0.0 2590 29 Sep 2010 Fixed 11.0.1 2501 29 Sep 2010 Fixed Description In rare situations, data corruption may have occurred during up channel renewal when the backend server was under high load. By default, channel renewal occurs whenever 2G of data has been uploaded to the Outbound Enabler. Since the up channel renewal mechanism has been replaced by chunk encoding in the version 11.0 Apache Relay Server, and all IIS Relay Servers, this issue only applies to version 12.0 Apache or IIS Relay Servers working against older Outbound Enablers (earlier than 11.0.1.2446) which don't support chunking. Up to 64k of upload data could have been lost when this problem occurred. This problem has now been fixed.

CR:643157

CR Number:   643157 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2512 22 Oct 2010 Fixed Description When running the deployment wizard, if the main SQL Anywhere install did not include all components, the deployment could have failed. For example, if UltraLite was not present, the Deployment Wizard for Windows Mobile would have raised the following error: Running CabWiz ... CabWiz Command Line: "C:\Program Files\SQL Anywhere 11\ce\cabwiz\cabwiz.exe" "C:\Documents and Settings\admin\Desktop\sqlany11.inf" /dest "C:\Documents and Settings\admin\Desktop\" /compress CabWiz Output: Windows CE CAB Wizard Error: Section [SourceDisksNames] - path C:\Program Files\SQL Anywhere 11\ultralite\ce\ARM.50 not found Error creating .CAB file C:\Documents and Settings\admin\Desktop\sqlany11.CAB This has been fixed.

CR:643187

CR Number:   643187 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3050 29 Sep 2010 Fixed 12.0.0 2590 29 Sep 2010 Fixed Description The Unix installer now sets up the SQLANYSAMP12 environment variable in the sa_config and sample_config scripts. On Unix systems, the sample_config script may be used to create a per-user copy of the samples. This is useful for a multi-user installation. With this change, the sample_config script will now set the SQLANYSAMP12 environment variable. The sample_config script will also generate a file (sample_env) to set the SQLANYSAMP12 environment variable, which if present will be picked up by the sa_config script. The sa_config script is used to set up environment variables for Unix. If the user has run the sample_config script to create a per-user copy of the samples, it will use the generated settings file to set SQLANYSAMP12 to point to the user's copy of the samples. If the user is running a single-user installation, the sa_config script will set SQLANYSAMP12 to $SQLANY12/samples (default setting for single-user installations).

CR:643196

CR Number:   643196 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3052 30 Sep 2010 Fixed 12.0.0 2591 30 Sep 2010 Fixed Description Progress messages are sent every 5% of the total estimated duration, but if no message has been sent (i.e. the percentage complete has not changed by 5%) for five minutes, another message should be sent anyway. These repeated messages were not being sent - this has been fixed.

CR:643221

CR Number:   643221 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3052 30 Sep 2010 Fixed 12.0.0 2591 30 Sep 2010 Fixed Description When loading a shapefile containing complex geometries, status messages may not have been printed every 5 minutes (as per the documentation), but could be delayed for arbitrary periods of time. During these periods the CPU usage of the engine would appear very high. This has been fixed.

CR:643230

CR Number:   643230 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3052 30 Sep 2010 Fixed 12.0.0 2591 30 Sep 2010 Fixed 11.0.1 2501 30 Sep 2010 Fixed Description The datatypes sysname and uniqueidentifierstr were both being mapped to char(0) in Micrsoft's SQL Server Integration Services. This has been corrected so that sysname is now mapped to varchar(30), and uniqueidentifierstr is now mapped to char(36).

CR:643281

CR Number:   643281 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3053 30 Sep 2010 Fixed 12.0.0 2591 30 Sep 2010 Fixed Description In very rare and timing dependent cases, the server could have crashed after disconnecting a TCP/IP connection. This has been fixed.

CR:643286

CR Number:   643286 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) 12.0.1 3953 01 Oct 2010 Fixed 12.0.0 2592 01 Oct 2010 Fixed 11.0.1 2502 01 Oct 2010 Fixed 10.0.1 4129 01 Oct 2010 Fixed Description A mirror server could have crashed if multiple errors occurred on startup. A mirror server uses -xp, and the crash could have occurred if the database failed to start and the TCP/IP protocol failed to start. This has been fixed.

CR:643296

CR Number:   643296 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3044 30 Sep 2010 Fixed 12.0.0 2585 30 Sep 2010 Fixed Description The use of sequence generators would have caused the server to crash when it was run in in-memory mode. This has been fixed.

CR:643314

CR Number:   643314 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) 12.0.1 3052 30 Sep 2010 Fixed 12.0.0 2591 30 Sep 2010 Fixed 11.0.1 2502 30 Sep 2010 Fixed 10.0.1 4129 30 Sep 2010 Fixed Description Canceling an external stored procedure may have caused the server to crash. This has been fixed.

CR:643317

CR Number:   643317 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) 12.0.1 3052 08 Nov 2010 Fixed 12.0.0 2591 01 Oct 2010 Fixed 11.0.1 2502 01 Oct 2010 Fixed 10.0.1 4129 01 Oct 2010 Fixed Description Canceling a call to xp_sendmail(), xp_startmail(), xp_stopmail(), xp_startsmtp(), or xp_stopsmtp(), may have caused a server crash. The external stored procedures that manage SMTP mail state did not protect against the case were two threads can try to access the same SMTP state. This has been fixed.

CR:643342

CR Number:   643342 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3053 01 Oct 2010 Fixed 12.0.0 2591 01 Oct 2010 Fixed 11.0.1 2502 01 Oct 2010 Fixed Description If an external environment call encountered a thread deadlock error, then there was a very small chance the application or event connection would have hung. This problem has now been fixed.

CR:643355

CR Number:   643355 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) 12.0.1 3052 04 Oct 2010 Fixed 12.0.0 2591 04 Oct 2010 Fixed 11.0.1 2502 04 Oct 2010 Fixed 10.0.1 4129 04 Oct 2010 Fixed Description Setting the value of an OUT parameter in an external stored procedures would have persisted, even without calling the set_value() function. This has been fixed.

CR:643418

CR Number:   643418 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3067 04 Oct 2010 Fixed 12.0.0 2597 04 Oct 2010 Fixed Description Opening the property sheet for a remote task before deploying it could prevent it from being executed by the MobiLink Agent if its SQL condition was empty and no other condition had been specified. This has been fixed.

CR:643421

CR Number:   643421 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3067 04 Oct 2010 Fixed 12.0.0 2597 04 Oct 2010 Fixed 11.0.1 2509 04 Oct 2010 Fixed 10.0.1 4134 04 Oct 2010 Fixed Description If an application was attempting to connect to a server and the server shut down between the time the protocol connection was made and the time the database connection was attempted, the application could have crashed. This has been fixed.

CR:643423

CR Number:   643423 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3054 04 Oct 2010 Fixed 12.0.0 2592 04 Oct 2010 Fixed Description When monitoring a SQL Anywhere resource that was under heavy load, it was possible that metrics being recorded could have been inaccurate. Most often this would have manifest itself as CPU Usage metric values being reported that were greater than 100%. This issue has now been fixed.

CR:643456

CR Number:   643456 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) 12.0.1 3061 06 Oct 2010 Fixed 12.0.0 2594 06 Oct 2010 Fixed 11.0.1 2506 06 Oct 2010 Fixed 10.0.1 4132 06 Oct 2010 Fixed Description If ALTER TABLE was used to reduce the length of a string column to less than the value of the INLINE or PREFIX values for that column, and then the database was unloaded, the reload script would have contained CREATE TABLE statements that would be rejected by the server. This has been fixed so that the ALTER TABLE statements will now fail.

CR:643457

CR Number:   643457 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) 12.0.1 3054 04 Oct 2010 Fixed 12.0.0 2592 04 Oct 2010 Fixed 11.0.1 2503 04 Oct 2010 Fixed Description Clicking the Back or Next button may not have updated the toolbar buttons properly. This has been fixed.

CR:643463

CR Number:   643463 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3054 04 Oct 2010 Fixed 12.0.0 2592 04 Oct 2010 Fixed Description If an application attempted to fetch a long binary value from a proxy table, and the underlying Remote Data Access server was JDBC based, then there was a chance the value would have been returned truncated. It should be noted that JDBC based Remote Data Access server classes have been deprecated and all attempts should be made to switch to an ODBC based Remote Data Access server class if at all possible. Nevertheless, the original truncation problem with the JDBC based Remote Data Access server classes has been fixed.

CR:643571

CR Number:   643571 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3057 05 Oct 2010 Fixed 12.0.0 2593 05 Oct 2010 Fixed Description The UltraLite Information utility (ulinfo) is supposed to display a list of the valid user IDs in an UltraLite database. In some cases, this list was not being displayed. This is now fixed.

CR:643576

CR Number:   643576 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3057 05 Oct 2010 Fixed 12.0.0 2593 05 Oct 2010 Failed Description Sybase Central could have crashed when deleting a deployed Remote Task while the "Results" panel was selected. This has been fixed.

CR:643587

CR Number:   643587 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 4130 05 Oct 2010 Fixed Description The server may have hung while processing data for encrypted connections. This has been fixed.

CR:643590

CR Number:   643590 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) 12.0.1 3060 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed 11.0.1 2505 07 Oct 2010 Fixed 10.0.1 4131 07 Oct 2010 Fixed Description When using the include_file parameter of the external system procedures xp_sendmail and xp_sendmail, they may have failed depending on the length of the file. This has been fixed.

CR:643596

CR Number:   643596 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3057 06 Oct 2010 Fixed 12.0.0 2593 06 Oct 2010 Fixed 11.0.1 2504 06 Oct 2010 Fixed 10.0.1 4130 06 Oct 2010 Fixed 9.0.2 4060 07 Mar 2012 Fixed Description When executing a query that involved window functions, proxy tables and dotted references, if the query was invalid due to a missing GROUP BY reference, then there was a chance the server would have failed to return the error. In some cases, the server would even have crashed. This problem has now been fixed. Note that this fix is a follow-up Engineering case 641477.

CR:643598

CR Number:   643598 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3057 05 Oct 2010 Fixed 12.0.0 2593 05 Oct 2010 Fixed Description The "Edit in Window" menu item was inadvertently shown when editing binary columns, and has now been removed. Editing the hex value in the table cell is still supported, as is loading a value from a file, but editing the hex value in a separate window was never supported. Also, the "Edit in Window" menu item was visible if a binary column value was clicked in the Results panel, and then the "..." button was clicked. This has been fixed as well.

CR:643642

CR Number:   643642 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3089 04 Nov 2010 Fixed 12.0.0 2606 04 Nov 2010 Fixed 11.0.1 2520 04 Nov 2010 Fixed 10.0.1 4144 04 Nov 2010 Fixed Description Revoking all table permissions from a grantee that were granted by a particular grantor did not always remove the corresponding SYSTABLEPERM row. This has now been fixed.

CR:643660

CR Number:   643660 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3057 05 Oct 2010 Fixed 12.0.0 2593 05 Oct 2010 Fixed 11.0.1 2505 05 Oct 2010 Fixed Description The DATEPART and HOUR functions would have returned the Hours partion of timestamps based on a 12 hour clock instead of a 24 hour clock. As a result, any afternoon timestamps would have returned the wrong Hours value. This has been fixed.

CR:643675

CR Number:   643675 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3060 05 Oct 2010 Fixed 12.0.0 2594 05 Oct 2010 Fixed Description When a user was in the process of creating a new widget for the SQL Anywhere Monitor, it was possible that certain metrics would not have been selectable. This problem was more likely to manifest itself if the SQL Anywhere Monitor was particularly busy at the time of creating the widget. For example, when creating a Table Widget for an SA resource, it was possible that the "Free Disk Space" category would not have let the user select which dbspace they wished to see free disk space for. This problem could also have manifest itself in the following ways: - When the user selected a widget's "Settings..." menu item, it was possible that metrics which were present in the widget would not have appeared as selected in the list of metrics - When creating a default dashboard for an SA resource, the table widget included on the dashboard would have been missing its Free Disk Space metrics - If the user wanted to create resource-based dashboards during the process of adding a new user, it was possible that a widget may be missing metrics or display them improperly These problems have now been fixed.

CR:643681

CR Number:   643681 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3061 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed Description If a temporary function was incorrectly defined to return a result set, calling the function would have given the error: Function '<function-name>' has invalid parameter 'expression' ('OUT') The correct error now reported is: Result set not permitted in '<function-name>'

CR:643698

CR Number:   643698 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) 12.0.1 3059 05 Oct 2010 Fixed 12.0.0 2593 05 Oct 2010 Fixed 11.0.1 2505 05 Oct 2010 Fixed Description On Mac OS systems, the Create Database wizard would have remained open after successfully creating a database. With the Cancel button disabled, it was necessary to click the Close box to close the wizard. Now, the wizard is automatically closed when database creation is successful.

CR:643701

CR Number:   643701 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4131 05 Oct 2010 Fixed 9.0.2 3988 05 Oct 2010 Fixed Description HP uses the character set name hp15CN as an alias for GB2312. Support for this alias has been added. Current builds of 11.0.1 and up already handled this alias.

CR:643703

CR Number:   643703 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3053 06 Oct 2010 Fixed 12.0.0 2593 06 Oct 2010 Fixed Description The MobiLink Replay utility (mlreplay) may have logged download success messages before the download was fully completed. In the Replay utility, a download is complete once it has received all the data from the MobiLink server and the download apply time has been reached. Prior to this change, mlreplay would have logged the download success message after receiving all the data from the MobiLink server, but before the download apply time had been reached. This has been fixed.

CR:643728

CR Number:   643728 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3059 06 Oct 2010 Fixed 12.0.0 2593 06 Oct 2010 Fixed Description Attempting to open the text completer while editing a stored procedure in Sybase Central would have resulted in the completer appearing and then immediately disappearing. This has been fixed.

CR:643763

CR Number:   643763 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2605 03 Nov 2010 Fixed 11.0.1 2519 03 Nov 2010 Fixed 10.0.1 4143 03 Nov 2010 Fixed Description Execution of a query block that output a string constant could have caused the server crash if the optimizer chose a parallel execution plan. The likelyhood of such a crash increased under high server load and when the query occurred inside a stored procedure. This problem has now been fixed. For version 12.0.0, this problem was most likely to be encountered when using string literals in different blocks of a Union, as follows: SELECT 'String1', col1, col2 FROM table1 WHERE predicate1 UNION SELECT 'String2', col1, col2 FROM table2 WHERE predicate2 For versions prior to 12.0.0 this problem was much more obscure, and likely required a constant string occurring both in a non-simple output expression and in a WHERE clause predicate. This has been fixed.

CR:643787

CR Number:   643787 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3060 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed 11.0.1 2506 07 Oct 2010 Fixed Description REFRESH TEXT INDEX on MANUAL or AUTO text index could have caused database recovery to fail. For the problem to have occurred, the statement had to have been executed under SNAPSHOT isolation, which must also have been enabled on the database as part of the changes being recovered. This has now been fixed.

CR:643802

CR Number:   643802 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3060 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed 11.0.1 2505 07 Oct 2010 Fixed 10.0.1 4131 07 Oct 2010 Fixed Description A web procedure that references another computer by name may have failed to connect if both machines supported IPv6, but the web server on the remote computer was not listening on any IPv6 addresses. This has been fixed.

CR:643805

CR Number:   643805 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3060 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed Description In rare cases, if procedure profiling was used on a database with events defined, the server could have hung. This has been fixed.

CR:643812

CR Number:   643812 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3060 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed 11.0.1 2505 07 Oct 2010 Fixed Description When a backend server was using an id longer than 44 characters, the client may not have been able to access the backend server. This has been fixed.

CR:643822

CR Number:   643822 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3060 06 Oct 2010 Fixed 12.0.0 2594 06 Oct 2010 Fixed 11.0.1 2505 06 Oct 2010 Fixed 10.0.1 4131 06 Oct 2010 Fixed 9.0.2 3988 07 Oct 2010 Fixed Description Schema locks were not being released when the execution of ExecuteReader() encountered an exception. If a BeginTransaction was called, a Rollback or Commit should be called by the application to release the locks. Now, if BeginTransaction is not called, the transaction will be automatically rolled when an exception is encountered.

CR:643936

CR Number:   643936 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) 12.0.1 3068 20 Oct 2010 Fixed 12.0.0 2598 20 Oct 2010 Fixed 11.0.1 2511 20 Oct 2010 Fixed 10.0.1 4137 20 Oct 2010 Fixed Description Unexpected column names could have been reported for complex expressions in the SELECT list of a statement. The problem mostly affected queries over views, for which the name of the base table column, rather than the name of the view column, could have been reported. For example, consider the following table and view: CREATE TABLE admin_group.employee( pk INTEGER PRIMARY KEY, fname CHAR(100) NOT NULL, lname CHAR(100) NOT NULL, cname CHAR(100) ); CREATE VIEW admin_group.v AS SELECT e.fname AS first_name, e.lname AS last_name, e.cname AS company_name FROM admin_group.employee e; In the query: SELECT <expr> FROM admin_group.v; the following expressions would have been described with the base table column names: CAST( first_name AS VARCHAR(100)) (first_name) This has been fixed so that both of the expressions above will now be described as 'first_name'. Additionally, expressions such as ISNULL( <col1>, <col2> ) could have been described differently depending on the nullability of the first column. For example, ISNULL( first_name, company_name ) would have been described as 'fname', whereas ISNULL( company_name, first_name ) would have been described as 'isnull( employee.fname as first_name,employee.cname as company_name)'. For consistency, both of the above expressions will now be described by unparsing the expression.

CR:643953

CR Number:   643953 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3061 07 Oct 2010 Fixed 12.0.0 2594 07 Oct 2010 Fixed 11.0.1 2507 07 Oct 2010 Fixed 10.0.1 4132 07 Oct 2010 Fixed Description In the Extract Database wizard for UltraLite, when checking or unchecking publications using the space bar instead of the mouse, the Next button would not have been enabled or disabled appropriately. This has been fixed.

CR:643960

CR Number:   643960 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 2506 07 Oct 2010 Fixed Description The changes for Engineering case 635800 introduced a problem for applications running on Palm devices. Applications could have hung while saving or restoring state, for example on database shutdown. This has now been fixed.

CR:644075

CR Number:   644075 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 2507 12 Oct 2010 Fixed Description The DROP PUBLICATION statement was not being autocommitted, like other schema changing statements. This has been fixed.

CR:644090

CR Number:   644090 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3061 12 Oct 2010 Fixed 12.0.0 2595 12 Oct 2010 Fixed Description The MobiLink Replay utility (mlreplay) could have incorrectly calculated the download apply time when multiple simulated clients were replaying the recorded protocol. This has been fixed.

CR:644105

CR Number:   644105 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3062 12 Oct 2010 Fixed 12.0.0 2595 12 Oct 2010 Fixed Description When a heavy download occurred, the Relay Server Outbound Enabler may have unnecessarily timed out the Up channel. This has been fixed by relaxing the Up channel liveness timeout when the Down channel is busy.

CR:644112

CR Number:   644112 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3062 12 Oct 2010 Fixed 12.0.0 2595 12 Oct 2010 Fixed 11.0.1 2507 12 Oct 2010 Fixed Description When the backend machine was under heavy load, a standalone Relay Server Outbound Enabler may have reported the following internal error HandleNotification: Error receiving for sidx=<session_index> system error ({error code}) With this change, the error is now less likely to occur.

CR:644122

CR Number:   644122 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) 12.0.1 3057 12 Oct 2010 Fixed 12.0.0 2594 12 Oct 2010 Fixed 11.0.1 2505 12 Oct 2010 Fixed Description A number a LOAD TABLE fixes have been made. 1. Arbitrary expressions were allowed in the FROM/USING clause of LOAD TABLE. If a variable was used, its value was logged to the transaction log; however, if the expression was anything other than a literal string or a variable (eg. 'c:\\tmp\\'+filename_var), the original expression would have been logged including the names of variables whose values would be unknown at recovery. The problem was fixed by only allowing a string or a variable for the file name (as documented). 2. If a LOAD TABLE statement was logged that used a variable in the FROM/USING clause and the statement was affected by database options such that the option values had to be logged with the statement, the variable name rather than its value would have been logged. This problem has been fixed. 3. When using LOAD TABLE ... WITH CONTENT LOGGING, the data logged was in the character set in which the server parsed the input file (either CHAR or NCHAR charset), rather than the original input file's character set. If the LOAD TABLE statement had an ENCODING clause, the data would have been re-translated during recovery as if it were in the specified ENCODING and potentially mangling the data. Fixed by logging an exact copy of the original input data. 4. If a LOAD TABLE statement did not contain an ENCODING clause (in which case the server assumes CHAR charset), the statement written to the log would not have one either. If the log were translated and executed against a database with a different collation, the file could be translated incorrectly since the default encoding would be different. This problem has been fixed by always logging an ENCODING clause. 5. If a LOAD TABLE statement contained an ENCODING clause that specified a 'UTF16' encoding of unspecified endian, the logged statement would also have contained an ENCODING clause with an unspecified endian. If recovery were performed on a server with the opposite endian, or if the log was translated then executed on a server with the opposite endian, the statement would not interpret the input file correctly. This problem has been fixed by never logging ambiguous names for encodings. 6. LOAD TABLE ... FORMAT XML ... WITH CONTENT LOGGING did not actually log any data and was not recoverable. This problem has been fixed. 7. LOAD TABLE ... FORMAT XML ... USING COLUMN (which is the statement that is logged for a LOAD TABLE ... FORMAT XML ... WITH CONTENT LOGGING) would have crashed the server. This problem has been fixed. 8. LOAD TABLE USING CLIENT FILE ... WITH FILE NAME LOGGING was permitted by the server and the server would then have logged a statement that referenced a client file. Access to the client file requires an active connection from the client and therefore this statement was not recoverable. This problem has been fixed by requiring WITH CONTENT LOGGING when loading from a client file. If the logging type is not specified when loading from a client file, content logging is assumed. 9. When recovering a LOAD TABLE ... WITH CONTENT LOGGING or executing LOAD TABLE ... USING COLUMN, the server would have leaked a small amount of memory for each row of data fetched from the table containing the pieces of the original file image. This problem has been fixed. 10. When executing LOAD TABLE ... USING COLUMN ... ENCODING..., the server did not check for a conflict between the specified encoding and the encoding of the column's datatype. This problem has been fixed by reporting an error if the encodings conflict. 11. LOAD TABLE and UNLOAD TABLE did not allow the ESCAPE CHARACTER to be more than 1 byte. It can now be an arbitrary string, but it is recommended that it should be no longer than one (potentially multibyte) character. 12. When using UNLOAD TABLE with a QUOTE or ESCAPE CHARACTER which was not encoded identically in both CHAR and NCHAR character sets, the quotes may not be doubled up or escape sequences may not be issued where necessary depending on the datatype of the column being unloaded. This problem has been fixed. 13. When using UNLOAD TABLE with a QUOTE or ESCAPE CHARACTER which were not encoded identically in both CHAR and NCHAR character sets and the destination charset, the quotes or escape characters could have been translated incorrectly when converting to the destination character set. This problem has been fixed. 14. ALTER DBSPACE RENAME allowed a variable to be used for the new file name but the variable name rather than its value was logged, which meant that the statement was unrecoverable. This problem has been fixed by logging the variable's value instead. 15. The SQL generated by the Log Translation utility (dbtran) for LOAD TABLE ... WITH CONTENT LOGGING (ie inserts into a temporary table) did not work correctly due to the temporary table's name being fully qualified with the user's name. This problem has been fixed.

CR:644464

CR Number:   644464 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3278 24 Jan 2011 Fixed 12.0.0 2635 24 Jan 2011 Fixed 11.0.1 2550 24 Jan 2011 Fixed 10.0.1 4173 24 Jan 2011 Fixed Description If a database had two or more 'post_login_procedure' option settings, then attempting to connect to the database would have failed with a "Subquery cannot return more than one row" error. This has been fixed.

CR:644477

CR Number:   644477 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3066 13 Oct 2010 Fixed 12.0.0 2596 13 Oct 2010 Fixed Description Text completion in SQL that was loaded from a Favorite may not have worked correctly if the SQL spanned multiple lines. This has been fixed.

CR:644491

CR Number:   644491 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3068 18 Oct 2010 Fixed 12.0.0 2597 18 Oct 2010 Fixed 11.0.1 2510 18 Oct 2010 Fixed 10.0.1 4135 18 Oct 2010 Fixed Description A bypass query that contained an invalid cursor range could have caused the server to crash in certain conditions. This has been fixed. Note: please see the section "Query processing phases" for a definition of bypass queries.

CR:644508

CR Number:   644508 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) 12.0.1 3074 19 Oct 2010 Fixed 12.0.0 2600 19 Oct 2010 Fixed 11.0.1 2512 19 Oct 2010 Fixed 10.0.1 4138 19 Oct 2010 Fixed Description A SQL Anywhere HTTP procedure may have failed when configured with a PROXY clause to connect through an Apache forwarding proxy version 2.0.X. This has been fixed. Changes have also been made to improve WebClientLogging (-zoc) messages when connecting through a proxy.