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

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

CR:644526

CR Number:   644526 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 21 Oct 2010 Fixed 12.0.0 2600 21 Oct 2010 Fixed 11.0.1 2512 21 Oct 2010 Fixed 10.0.1 4137 21 Oct 2010 Fixed Description If a long index entry (the equivalent of a 250 character or longer ASCII string) was deleted from an index, there was the possibility of index corruption and the server crashing. This has been fixed.

CR:644529

CR Number:   644529 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 3066 13 Oct 2010 Fixed 12.0.0 2596 13 Oct 2010 Fixed Description When deleting a resource in the SQL Anywhere Monitor, it was possible that after the delete completed, the Configure, Remove, Start/Stop and Repair buttons would still have been enabled, even though no resource was selected. This has been fixed.

CR:644682

CR Number:   644682 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 3067 13 Oct 2010 Fixed 12.0.0 2597 13 Oct 2010 Fixed 11.0.1 2509 13 Oct 2010 Fixed Description Using a reserved word as a label in a Transact-SQL procedure would have made the procedure unusable. This has been fixed.

CR:644703

CR Number:   644703 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 3067 14 Oct 2010 Fixed 12.0.0 2597 14 Oct 2010 Fixed Description When using ST_AsSVG, ST_AsSVGAttr, ST_AsText or ST_AsXML to output SVG, if the Attribute SVG format option was specified, an invalid SVG document could have been generated. In particular, if an SVG shape attribute was generated, and the same SVG shape attribute was explicitly specified by the Attribute SVG format option, the resulting SVG document contained a duplicate attribute. For example, if ls was a linestring geometry: select ls.ST_AsSVG( 'Attribute=fill="blue"' ) would have resulted in an invalid SVG document with a duplicate attribute. This has been fixed by only outputting the generated attribute or the attribute from the Attribute SVG format option, but not both, when there is a duplicate attribute.

CR:644733

CR Number:   644733 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2510 18 Oct 2010 Fixed Description If a server acting as a mirror in a mirroring system required access to transaction log files on the primary that had been deleted, the mirror server would not have reported an error. The mirror server would have continued to stay running, but would not have received updates from the primary server. This has been fixed so that the mirror server will now report the error and shut down.

CR:644855

CR Number:   644855 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) 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 If the Interactive SQL utility (dbisql) was open, and the results of a query were displayed, changing the Windows desktop theme from "Windows XP" to "Windows Classic", or otherwise changing the Window style from "XP" to "Classic", would have caused dbisql to crash. This has been fixed. This issue could have manifest itself any time the Windows look-and-feel was changed from something other than Windows Classic to Windows Classic. It would also have affected Sybase Central if a table was selected in the "Folders" panel. This issue only occurred on Windows computers. Operation on other operating systems was not affected.

CR:644908

CR Number:   644908 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 3385 28 Jun 2011 Fixed 12.0.0 2702 28 Jun 2011 Fixed 11.0.1 2628 28 Jun 2011 Fixed 10.0.1 4241 28 Jun 2011 Fixed Description After an ALTER TABLE statement, some views may have been incorrectly marked as INVALID. The problem only occurred for views in which the altered table occurs multiple times in the logical expansion of the view definition. This has been fixed.

CR:644976

CR Number:   644976 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 3069 19 Oct 2010 Fixed 12.0.0 2598 19 Oct 2010 Fixed Description If an application made at least five connections, and then all were disconnected, the messages "Disconnecting shared memory client, process id not found" and "Disconnected ... client's AppInfo is ..." could have incorrectly been logged to the server's message window. This was most likely to have occurred with an application using the SQL Anywhere JDBC driver. As a workaround, disabling connection pooling would prevent the messages from being displayed. This has been fixed so that these messages are not displayed for pooled connections.

CR:644992

CR Number:   644992 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.1 3069 19 Oct 2010 Fixed 12.0.0 2598 19 Oct 2010 Fixed Description If the SQL Anywhere Monitor was particularly busy when a user attempted to load the Monitor's web-based UI, it was possible that the Flash Player debugger could have reported a null-pointer exception. If the Flash Player debugger was not installed, this problem would have manifest itself as a slower than usual load time. This has been fixed.

CR:645001

CR Number:   645001 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 3072 25 Oct 2010 Fixed 12.0.0 2599 25 Oct 2010 Fixed Description If parallel access plans were considered by the SQL Anywhere Optimizer, then it was possible for queries to fail assertions 105804,105805, or 105816, "Cannot build parallel ...". This has been fixed. See: "SQL Anywhere Server - SQL Usage Query optimization and execution Query execution algorithms Parallelism during query execution Parallelism in queries" or: http://dcx.sybase.com/index.html#1200en/dbusage/queryopt-s-4716396.html*d5e30658

CR:645005

CR Number:   645005 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3069 19 Oct 2010 Fixed 12.0.0 2598 19 Oct 2010 Fixed 11.0.1 2510 19 Oct 2010 Fixed 10.0.1 4135 19 Oct 2010 Fixed Description When using the Unload or Extract Database wizards, if unload/extract into a new database was chosen, and Strong encryption was specified with an encryption key that didn't match the confirm encryption key, then the wizards would have continued to report a key mismatch error even after the encryption type was changed to Simple (where the encryption key is not used). This has been fixed.

CR:645138

CR Number:   645138 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 3072 18 Oct 2010 Fixed 12.0.0 2599 18 Oct 2010 Fixed 11.0.1 2511 18 Oct 2010 Fixed Description In very rare cases, a primary mirroring server could have crashed on shutdown if the database was being updated. This has been fixed.

CR:645142

CR Number:   645142 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 3072 19 Oct 2010 Fixed 12.0.0 2599 19 Oct 2010 Fixed Description On Windows systems, the server's process heap could have become corrupt. The only circumstance under which this was likely to occur was if a dialog was displayed (to locate a dbspace, for example) when starting a database specified on the command line. This has been fixed.

CR:645161

CR Number:   645161 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 3071 22 Oct 2010 Fixed 12.0.0 2599 22 Oct 2010 Fixed Description The graphical and long plans may have contained incorrect total estimated runtime information. This has been fixed. Note, this problem did not affect the quality of the plan found by the Optimizer, only the final estimated runtimes shown in the graphical and long plans were incorrect.

CR:645223

CR Number:   645223 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 3076 19 Oct 2010 Fixed 12.0.0 2601 19 Oct 2010 Fixed 11.0.1 2513 19 Oct 2010 Fixed Description The Relay Server for IIS7 could have unexpectedly disconnected persistent http connections after finishing relaying a server response. This has been fixed.

CR:645325

CR Number:   645325 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 3079 25 Oct 2010 Fixed 12.0.0 2602 25 Oct 2010 Fixed Description Spatial queries that applied a predicate that measured distance (ST_WithinDistance, ST_WithinDistanceFilter, or ST_Distance) may have caused a server crash when the optional unit name was supplied to the predicate, and the optimizer chooses a parallel plan. For example, the following query would have caused a crash if the optimizer chose a parallel plan: select count(*) from my_table where my_table.geometry.ST_WithinDistance( new ST_Point( 0, 0, 4326 ), 10, 'kilometre') = 1 This has been fixed.

CR:645468

CR Number:   645468 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 4137 20 Oct 2010 Fixed Description In rare situations, the value for Index Statistics reported in graphical plans may have been incorrect. This has been fixed.

CR:645496

CR Number:   645496 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 3074 21 Oct 2010 Fixed 12.0.0 2600 21 Oct 2010 Fixed Description For geometries in Round Earth spatial reference systems with lat, lon, z, or m axis order or, with units of measurement other than degrees, an incorrect result could have been returned by the following methods: ST_XMin, ST_XMax, ST_YMin, ST_YMax, ST_LonWest, ST_LonEast, ST_LatSouth, ST_LatNorth This has been fixed.

CR:645497

CR Number:   645497 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 3074 21 Oct 2010 Fixed 12.0.0 2600 21 Oct 2010 Fixed Description No messages would have been when right-clicking a synchronization profile, selecting "Synchronize...", and then clicking OK. This has been fixed.

CR:645529

CR Number:   645529 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 3074 21 Oct 2010 Fixed 12.0.0 2600 21 Oct 2010 Fixed 11.0.1 2512 21 Oct 2010 Fixed Description When run on Windows desktop, UltraLite now supports long paths when creating, opening, or deleting databases.

CR:645630

CR Number:   645630 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 3075 22 Oct 2010 Fixed 12.0.0 2600 22 Oct 2010 Fixed Description When editing DATE, TIME, or TIMESTAMP values in a result set, the usual date/time editor was not being make available, forcing the value to be edited as a string. This has been fixed.

CR:645635

CR Number:   645635 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 3075 21 Oct 2010 Fixed 12.0.0 2600 21 Oct 2010 Fixed 11.0.1 2513 21 Oct 2010 Fixed Description HTTP requests made to SQL Anywhere services that utilize the built-in HTTP Session mechanism (created with sa_set_http_option) may, on rare occasions, have caused the server to crash. This has been fixed.

CR:645659

CR Number:   645659 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3075 22 Oct 2010 Fixed 12.0.0 2600 22 Oct 2010 Fixed 11.0.1 2513 22 Oct 2010 Fixed Description Under some conditions, the QAManager Close() method could have taken up to a minute to return. This has been fixed. The Close() method will now always complete in a reasonable amount of time.

CR:645664

CR Number:   645664 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3088 02 Nov 2010 Fixed 12.0.0 2606 02 Nov 2010 Fixed 11.0.1 2519 02 Nov 2010 Fixed 10.0.1 4143 02 Nov 2010 Fixed Description Attempting o unload and reload a database that contained a proxy table with a unique constraint would have failed with the error: "feature 'alter remote table' not implemented ". This problem has now been fixed. The "alter table...add unique" statement is no longer unloaded for proxy tables.

CR:645665

CR Number:   645665 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2512 22 Oct 2010 Fixed Description When a message was received by the QAManager.GetMessage method when the QAManager was opened in AcknowledgementMode.IMPLICT_ACKNOWLEDGEMENT and the QAnywhere Agent was running with automatic policy, it was possible that the acknowledgement would not have been transmitted to the receiver until the next time the message store was synchronized with the MobiLink server. This has been fixed. Now the received message is immediately acknowledged.

CR:645666

CR Number:   645666 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 3104 25 Oct 2010 Fixed 12.0.0 2615 25 Nov 2010 Fixed Description The server supports the optional use of the LIMIT/OFFSET clauses in SELECT statements as an alternative to the TOP/START AT clauses. If such a statement was used within a view definition then the server would have ignored the LIMIT/OFFSET specification and would have returned the entire result set of the underlying view query. This has been fixed so that the server now pays attention to the LIMIT/OFFSET clauses used within view definitions.

CR:645759

CR Number:   645759 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 3076 25 Oct 2010 Fixed 12.0.0 2601 25 Oct 2010 Fixed Description Attempting to drop a temp table created by sa_copy_cursor_to_temp_table() could have failed with an error. For example, the following sequence could have given a permission error for a user without DBA authority: BEGIN DECLARE myCursor CURSOR FOR SELECT 123; OPEN myCursor; CALL sa_copy_cursor_to_temp_table( 'myCursor','myTempTable' ); drop table myTempTable; END Permission denied: you do not have permission to use the "DROP TABLE" statement SQLCODE=-121, ODBC 3 State="42000" Further, in some cases, the temp table created by the procedure could not have been found by a reference at a different scope level. The following sequence of statements would have returned an error for that reason: BEGIN DECLARE myCursor CURSOR FOR SELECT 123; OPEN myCursor; CALL sa_copy_cursor_to_temp_table( 'myCursor','myTempTable' ); END; go select * from myTempTable These problems have been fixed. In order to get the full fix, the database must be either created with the fixed server, or upgraded using the "ALTER DATABASE UPGRADE" statement using the fixed server software. As well, the sa_copy_cursor_to_temp_table procedure now uses "CREATE LOCAL TEMPORARY TABLE" to create the table.

CR:645771

CR Number:   645771 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.1 3076 22 Oct 2010 Fixed 12.0.0 2601 22 Oct 2010 Fixed Description With nightly maintenance set to its default settings, Relay Server farm metrics would not have been condensed into a representative daily value after two weeks. This has been fixed.

CR:645801

CR Number:   645801 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 3093 08 Nov 2010 Fixed 12.0.0 2608 08 Nov 2010 Fixed 11.0.1 2521 08 Nov 2010 Fixed 10.0.1 4145 08 Nov 2010 Fixed Description In an environment with each server in a mirroring system having two network connections, each on one of three separate networks, so that a failure in one of the networks would still allow two of the nodes to communicate, a network outage could have resulted in both partner servers acting as a primary server. This has been fixed.

CR:645838

CR Number:   645838 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 3104 03 Nov 2010 Fixed 12.0.0 2609 22 Nov 2010 Fixed Description The SQL Anywhere server erroneously allowed the Reserved_keywords option to be specified at the user and connection levels. Setting the option value at these levels could have caused problems with recovery, and for unloading and reloading a database. This has been corrected by no longer allowing non-PUBLIC settings for the Reserved_keywords option. This change now does the following: 1. Temporary and user specific settings are no longer allowed 2. Existing settings for non-PUBLIC users are ignored during execution 3. Removal of existing user specific settings is allowed in order to allow cleanup 4. dbunload sets the public option setting at the beginning of the reload script 5. dbunload ignores non-PUBLIC settings in the database being unloaded

CR:645926

CR Number:   645926 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3079 25 Oct 2010 Fixed 12.0.0 2602 25 Oct 2010 Fixed 11.0.1 2514 25 Oct 2010 Fixed 10.0.1 4139 25 Oct 2010 Fixed Description If an Open Client or jConnect application attempted to prepare and execute a statement with a large number of parameters, then the server would have failed the request, or in rare cases, could have crashed. This problem has now been fixed.

CR:645948

CR Number:   645948 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3079 25 Oct 2010 Fixed 12.0.0 2602 25 Oct 2010 Fixed 11.0.1 2514 25 Oct 2010 Fixed 10.0.1 4139 25 Oct 2010 Fixed Description The LITERAL_PREFIX and LITERAL_SUFFIX characters returned by SQLGetTypeInfo for binary data types were apostrophes. If these characters were used in an INSERT statement, the value stored was incorrect. For example: Store binary 0x1234 into column. INSERT INTO test (binary_col) VALUES ('1234'); The result is 0x31323334. If the LITERAL_PREFIX was 0x and the LITERAL_SUFFIX was NULL, then the value stored was correct. INSERT INTO test (binary_col) VALUES (0x1234); This problem has been corrected. The following types will now return 0x in the LITERAL_PREFIX column and NULL in the LITERAL_SUFFIX column: long binary varbinary binary

CR:645952

CR Number:   645952 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3079 26 Oct 2010 Fixed 12.0.0 2602 26 Oct 2010 Fixed 11.0.1 2514 26 Oct 2010 Fixed 10.0.1 4139 26 Oct 2010 Fixed Description The ODBC functions SQLColumns and SQLProcedureColumns incorrectly returned a NULL value for the CHAR_OCTET_LENGTH column for XML and ST_GEOMETRY data types. ST_GEOMETRY is a new data type supported by SQL Anywhere in version 12. This has been fixed and the correct value of 2147483647 is now returned.

CR:645953

CR Number:   645953 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 3079 25 Oct 2010 Fixed 12.0.0 2602 25 Oct 2010 Fixed 11.0.1 2514 25 Oct 2010 Fixed 10.0.1 4139 25 Oct 2010 Fixed Description The DBSCHEMA_PROVIDER_TYPES rowset schema incorrectly returned 0x in the LITERAL_PREFIX column for varbit types. The apostrophe character (') is now returned in the LITERAL_PREFIX and LITERAL_SUFFIX columns instead.

CR:645959

CR Number:   645959 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3079 25 Oct 2010 Fixed 12.0.0 2602 25 Oct 2010 Fixed 11.0.1 2514 25 Oct 2010 Fixed 10.0.1 4139 25 Oct 2010 Fixed Description Microsoft SQL Server has introduced two data types DBTYPE_DBTIME2 and DBTYPE_DBTIMESTAMPOFFSET that are not part of the OLE DB specification. Support for conversions between these two types and DBTYPE_STR, DBTYPE_WSTR, DBTYPE_DBDATE, DBTYPE_DBTIME, and DBTYPE_DBTIMESTAMP has now been added to the SQL Anywhere OLE DB provider. DBTYPE_DBTIME2 differs from DBTYPE_DBTIME in that fractional seconds are included. The type corresponds to the Microsoft SQL Server TIME data type. DBTYPE_TIMESTAMPOFFSET adds support for a timezone offset (hours/minutes). The type corresponds to the Microsoft SQL Server DATETIMEOFFSET data type.

CR:645986

CR Number:   645986 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) 12.0.1 3079 26 Oct 2010 Fixed 12.0.0 2602 26 Oct 2010 Fixed 11.0.1 2514 26 Oct 2010 Fixed 10.0.1 4139 26 Oct 2010 Fixed Description If the database server reported a "definite" rowcount for a query but then returned fewer than that many rows, dbisqlc could have displayed a subset of the rows, or possibly no rows at all. This has now been fixed. When using the "Connect with an ODBC Data Source" option in the "Action" dropdown list of the "Login" tab of the connection dialog with the 64-bit versions of the dbisqlc utility and dbmlsync, no DSNs would have been displayed; and the 32-bit versions would only have shown DSNs that used an ODBC driver with the same major version of SQLAnywhere as dbisqlc and dbmlsync. This has been fixed, so that 32-bit and 64-bit versions now display all SQLAnywhere DSNs defined for SQLAnywhere version 6.0 and up. Dbisqlc did not correctly handle certain connection string components which did not have a shortform (such as the new "Server" parameter). This problem has been fixed.

CR:646150

CR Number:   646150 Product Name:   MobiLink Product Component:   MobiLink Agent Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3116 28 Oct 2010 Fixed 12.0.0 2617 28 Oct 2010 Fixed Description The MobiLink Agent for central adminstration of remote databases would have given an obscure error message like: Task task1 (ID 50): command number 1 not executed, error code 0 when a task was executed that connected to a remote database, and the adapter library (eg. mlauladapt12.dll) for that remote database was missing from the agent deployment. This has been fixed so that a clearer error message is now displayed.

CR:646169

CR Number:   646169 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2468 28 Oct 2010 Fixed Description When run on a machine with 25 or more logical processors, the server may have hung. This hang would only have occurred on Windows and Linux systems. This problem has been fixed. A workaround is to reduce the number of logical processors the server uses by specifying -gtc <num>, where num is less than or equal 24.

CR:646269

CR Number:   646269 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2518 02 Nov 2010 Fixed 10.0.1 4142 02 Nov 2010 Fixed Description The MobiLink Server could have crashed under heavy load if the client load was a mix of old (prior to version 10) and new (version 10 or later) clients. THis has now been fixed. A work around is to specify the -cn switch with a value of the twice the value of -w plus 1. Eg. if using the default value of -w (5), specify -cn 11. Version 12 is not affected as it no longer supports old clients.

CR:646305

CR Number:   646305 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3081 27 Oct 2010 Fixed 12.0.0 2602 27 Oct 2010 Fixed Description When running the uninstall for SQL Anywhere 12, after installing ado.net components, the uninstall could have failed with the following error: "Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action SetupVSPackageUninstall, entry: SetupVSPackageUninstall library: C:\Windows\Installer\MSIA8A0.tmp" This has been fixed.

CR:646335

CR Number:   646335 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 3081 29 Oct 2010 Fixed 12.0.0 2603 29 Oct 2010 Fixed Description In rare cases, the SQL Anywhere Monitor could have failed to fetch DBSpace names for a given SA resource; at the same time, a ConcurrentModificationException would have been reported to the message log. This has been fixed. As a workaround, clicking the "refresh data" link in the SQL Anywhere Monitor afterwards should fetch the DBSpace names without problem.

CR:646349

CR Number:   646349 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 3081 28 Oct 2010 Fixed 12.0.0 2603 28 Oct 2010 Fixed 11.0.1 2515 28 Oct 2010 Fixed Description The SQL Anywhere BINARY datatype was mapped to SQL Server's BINARY datatype. This could have resulted in incorrect values when exporting SQL Anywhere tables to SQL Server, as the SQL Anywhere BINARY datatype is variable length, and the SQL Server BINARY datatype is fixed length. This has been corrected by mapping the SQL Anywhere Binary datatype to SQL Server's VARBINARY datatype.

CR:646356

CR Number:   646356 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3081 29 Oct 2010 Fixed 12.0.0 2603 29 Oct 2010 Fixed 11.0.1 2515 29 Oct 2010 Fixed 10.0.1 4140 29 Oct 2010 Fixed Description The error SQLE_MEMORY_ERROR could have been reported on Windows Mobile devices when a removable media card was ejected, or when the device returned from standby. The operation should have been silently retried for a few seconds and then SQLE_DEVICE_IO_FAILED reporting if the operation still failed. This has now been corrected.

CR:646431

CR Number:   646431 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) 10.0.1 4156 14 Dec 2010 Fixed Description In timing dependent cases, the server could have hung with 100% CPU usage. This has been fixed.

CR:646518

CR Number:   646518 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3082 29 Oct 2010 Fixed 12.0.0 2603 29 Oct 2010 Fixed Description In rare cases, UltraLite for Mac OS X could have gone into an endless loop while writing to the stream during a synchronization. This has been fixed.

CR:646543

CR Number:   646543 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 3082 29 Oct 2010 Fixed 12.0.0 2603 29 Oct 2010 Fixed Description Spatial queries that constructed large geometry values for output may have been slow to respond to a cancel command. This has been fixed.

CR:646675

CR Number:   646675 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 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 Description In DBISQL, and Sybase Central, SQL is displayed in a syntax highlighting editor that is restricted to using fixed-width fonts. The editor's display can be thought of as being divided into a grid of fixed-width rows and columns. The column width is based on the character width of the display font, which is called the "em width". Some languages, such as Japanese, Chinese, and Korean, contain characters that are wider than the em width. When the widths of these characters were not integral multiples of the em width, subsequent characters on the line were drawn without respecting the editor's grid of fixed column widths. This led to occasional problems where selected text was not drawn with the correct colors, and more importantly, prevented the text completer from making appropriate suggestions. This has been fixed.

CR:646687

CR Number:   646687 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3083 29 Oct 2010 Fixed 12.0.0 2604 29 Oct 2010 Fixed 11.0.1 2517 29 Oct 2010 Fixed 10.0.1 4141 29 Oct 2010 Fixed Description If a large number of concurrent connections simultaneously executed remote queries that required partial or no passthrough processing, and several of the queries made heavy usage of aliases, then the server could have crashed. This problem has now been fixed.

CR:646703

CR Number:   646703 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 3094 09 Nov 2010 Fixed 12.0.0 2608 09 Nov 2010 Fixed 11.0.1 2522 09 Nov 2010 Fixed 10.0.1 4144 09 Nov 2010 Fixed Description In rare circumstances, reading a substring of a value from a compressed column (not starting at the first byte) could have caused assertion failure 201501 - "Page ... for requested record not a table page". Note that the Interactive SQL utility (dbisql) fetches long values in pieces, so selecting the value using dbisql (without using substrings) may cause this problem. This only happens on compressed columns with blob indexes. This has been fixed.

CR:646830

CR Number:   646830 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 3086 01 Nov 2010 Fixed 12.0.0 2605 01 Nov 2010 Fixed 11.0.1 2518 01 Nov 2010 Fixed 10.0.1 4142 01 Nov 2010 Fixed Description In very rare cases, the server may have crashed using long identifiers in SQL statements. This has been fixed.

CR:646846

CR Number:   646846 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 3086 02 Nov 2010 Fixed 12.0.0 2605 02 Nov 2010 Fixed Description VALIDATE TABLE could have reported a validation failure if an index on the table contained 65 or more columns, and a row existed whose index hash value was less than 256 bytes in length. This problem has been fixed.

CR:646858

CR Number:   646858 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 3101 18 Nov 2010 Fixed 12.0.0 2611 18 Nov 2010 Fixed 11.0.1 2525 18 Nov 2010 Fixed Description Under very rare circumstances, the server could crash during database cleaner execution. This has been fixed.

CR:646862

CR Number:   646862 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3087 03 Nov 2010 Fixed 12.0.0 2605 03 Nov 2010 Fixed Description Attempting to read a large Unicode string from an UltraLite database while using the engine could have caused a buffer overrun. This has been fixed.

CR:647005

CR Number:   647005 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2518 02 Nov 2010 Fixed Description The CE Deployment Wizard Installer would have throw an exception when clicking the 'Deploy to Mobile Device Now' button on a system which did not have ActiveSync installed. This has been fixed so that the following error is now issued: Error: Microsoft Activesync is not installed. CEAppMgr.exe is not detected. .CAB file will not be deployed.

CR:647066

CR Number:   647066 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 3087 03 Nov 2010 Fixed 12.0.0 2605 03 Nov 2010 Fixed 11.0.1 2519 03 Nov 2010 Fixed Description The Stored Procedure Debugger was sometimes unable to set breakpoints for statements in procedures that should have allowed breakpoints. This has been fixed.

CR:647076

CR Number:   647076 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 3087 03 Nov 2010 Fixed 12.0.0 2605 03 Nov 2010 Fixed 11.0.1 2519 03 Nov 2010 Fixed Description When starting the server on recent versions of Linux using the -ux or -ui command line options, or when auto-starting a server that required a GUI-based evaluation splash screen, the server may have crashed or hang. The crash would have occurred mostly on recent versions of Linux running a GTK theme engine (e.g. Clearlooks). The hang could have happened with any supported GTK version after dismissing the evaluation splash screen. This has now been fixed. A workaround is to run without the GUI.

CR:647077

CR Number:   647077 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 3153 03 Nov 2010 Fixed 12.0.0 2647 03 Nov 2010 Fixed 11.0.1 2563 03 Nov 2010 Fixed Description When run on Mac OS X systems, the server would have exited with the error "Failed to become daemon" if both the -um and -ud command line options were specified. This was due to a limitation in the OS X GUI infrastructure. This has been fixed. The -um flag is now ignored if -ud is specified. A workaround is to use dbspawn instead of -ud.

CR:647154

CR Number:   647154 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3116 30 Nov 2010 Fixed 12.0.0 2617 30 Nov 2010 Fixed 11.0.1 2532 30 Nov 2010 Fixed 10.0.1 4156 30 Nov 2010 Fixed Description The denial-of-service attack addressed by the changes for Engineering case 610115 could still have occurred if idle timeout had been turned off on the server using the command line option -ti 0, or the system procedure sa_server_option('IdleTimeout',0). If the idle_timeout value was not 0, the server was not susceptible. This has now been corrected.

CR:647162

CR Number:   647162 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 3086 03 Nov 2010 Fixed 12.0.0 2606 04 Nov 2010 Fixed Description Selecting an Event object in the Details pane, then right-clicking the same event in the tree to enable or disable it, would have thrown an exception. This has been fixed.

CR:647163

CR Number:   647163 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 3097 16 Nov 2010 Fixed 12.0.0 2610 16 Nov 2010 Fixed Description Several different spatial queries could potentially have caused server crashes, either when the Cancel was pressed, or when a SQL error was encountered while executing a parallel plan. This has been fixed.

CR:647187

CR Number:   647187 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 3088 03 Nov 2010 Fixed 12.0.0 2606 03 Nov 2010 Fixed 11.0.1 2519 03 Nov 2010 Fixed 10.0.1 4143 03 Nov 2010 Fixed Description When attempting to insert a string into a proxy table that was the result of calling a builtin function, if the builtin function returned an empty string, then there was a chance that the Remote Data Access layer would have inserted a NULL value instead. For example, a statement like: INSERT INTO my_proxy_table(my_column) SELECT RTRIM( ' ' ) may have inserted NULL instead of '' into to my_proxy_table. This problem has now been fixed.

CR:647225

CR Number:   647225 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 3093 08 Nov 2010 Fixed 12.0.0 2608 08 Nov 2010 Fixed 11.0.1 2521 08 Nov 2010 Fixed Description Attempts to edit table data in the "Results" panel would have failed with the error "Savepoint ... could not be found.", if the Transact-SQL transaction mode was Unchained. This has been fixed. Note that the default transaction mode is Chained.

CR:647327

CR Number:   647327 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 3094 09 Nov 2010 Fixed 12.0.0 2608 09 Nov 2010 Fixed Description In a CHECK constraint, the syntax OWNER.FunctionName() or Geometry.ST_Method1().ST_Method2() was not being accepted. This has been fixed.

CR:647331

CR Number:   647331 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.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 Execution of an extremely complicated remote query that needed to be processed in either no passthrough or partial passthrough mode, could have resulted in a server failure. The server now properly returns error -890.

CR:647341

CR Number:   647341 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3094 09 Nov 2010 Fixed 12.0.0 2608 09 Nov 2010 Fixed 11.0.1 2522 09 Nov 2010 Fixed Description The OUTPUT...FORMAT FIXED statement wrote DECIMAL, DOUBLE, NUMERIC, SMALLINT, and TINYINT values left-aligned. They are now correctly written right-aligned, like the other numeric data types. Note, There is no guarantee that FIXED format files created by DBISQL use the same column widths as DBISQLC.

CR:647345

CR Number:   647345 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3105 04 Nov 2010 Fixed 12.0.0 2615 04 Nov 2010 Fixed 11.0.1 2528 04 Nov 2010 Fixed 10.0.1 4151 04 Nov 2010 Fixed Description The data for an upload stream may not have been fully uploaded into the consolidated database if the consolidated database was running on Microsoft SQL Server and errors occurred in the upload. For this to have occurred, the connection property, XACT_ABORT must have been set 'ON' in the consolidated database, and the handle_error script must have returned 1000 (skip the row and continue processing). This problem has now been fixed.

CR:647472

CR Number:   647472 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3090 08 Nov 2010 Fixed 12.0.0 2607 08 Nov 2010 Fixed Description If SQL Anywhere was installed with an install key which contains only a subset of the whole install, such as the ALK Personal Server w/ Sync key which includes the Personal server but not the Network server, and then the Deployment wizard for Windows was run, it was not possible to select the personal server for deployment. The only database that was listed was UltraLite. The visible components have now been corrected, to show the Personal Server.

CR:647495

CR Number:   647495 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 3090 05 Nov 2010 Fixed 12.0.0 2607 05 Nov 2010 Fixed 11.0.1 2520 05 Nov 2010 Fixed 10.0.1 4144 05 Nov 2010 Failed Description On recent versions of Linux (with SELinux enabled), programs with executable stacks were forbidden. The program would have failed to start with an error like: dbeng12: error while loading shared libraries: libdbserv12_r.so: cannot enable executable stack as shared object requires: Permission denied This would have potentially happened with any SQL Anywhere binary, and has now been fixed. A work around is to either disable SELinux, or run execstack -c on the problematic binaries.

CR:647524

CR Number:   647524 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 3090 08 Nov 2010 Fixed 12.0.0 2607 08 Nov 2010 Fixed Description The server could have crashed when processing an operation that updated an index. This has now been fixed.

CR:647547

CR Number:   647547 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 3091 08 Nov 2010 Fixed 12.0.0 2607 08 Nov 2010 Fixed Description When using Adaptive Server Enterprise 15.5 as the consolidated database, checking the MobiLink System Setup could have incorrectly reported a changed or corrupt setup, with several differences reported for columns changing type from numeric to integer, like the following: Table 'ml_database' has changed: Column 'rid' has changed: type from numeric to integer If the only differences reported were "type from numeric to integer" then the error can be safely ignored. This has been fixed.

CR:647663

CR Number:   647663 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 3095 10 Nov 2010 Fixed 12.0.0 2609 10 Nov 2010 Fixed 11.0.1 2522 10 Nov 2010 Fixed 10.0.1 4146 10 Nov 2010 Fixed Description A server running as the primary in a mirroring system could have hung when the mirror server was started. This was more likely to occur after the fix for Engineering case 637057 was applied. This has been fixed.

CR:647682

CR Number:   647682 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 3102 09 Nov 2010 Fixed 12.0.0 2612 09 Nov 2010 Fixed 11.0.1 2525 09 Nov 2010 Fixed 10.0.1 4149 09 Nov 2010 Fixed Description Key constraint checking and validation errors were possible when indexing long index values if the relative position of the corresponding index columns (foreign and primary) within their respective tables were not identical. This has been fixed.

CR:647701

CR Number:   647701 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 3093 09 Nov 2010 Fixed 12.0.0 2608 09 Nov 2010 Fixed Description Simulated clients of the MobiLink Replay utility (mlreplay) could have timed out prematurely on Linux with the following message in the log: "Unable to select socket status. The system-specific error code is 4 (hex 00000004)". This has been fixed.

CR:647802

CR Number:   647802 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 3351 13 May 2011 Fixed 12.0.0 2682 13 May 2011 Fixed 11.0.1 2618 10 Jun 2011 Fixed Description The server may have failed assertion 106104 "field unexpected during compilation" for queries containing correlated subselects in the WHERE clause. The WHERE subselect predicate must have been of the form "T.X = (subselect referencing R.Y)" where R.Y was an outer reference. This has now been fixed.

CR:647830

CR Number:   647830 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 3094 09 Nov 2010 Fixed 12.0.0 2608 09 Nov 2010 Fixed Description In the SQL Anywhere Monitor web application, there were inconsistencies in how lists of resources were sorted. In some cases resources were sorted by name in a case sensitive manner, other times resources were sorted by name in a case insensitive manner, and in one case the list of resources wasn't sorted at all. This has been fixed. Now, all lists of resources are sorted by name in a case insensitive manner.

CR:647836

CR Number:   647836 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 3147 11 Jan 2011 Fixed 12.0.0 2629 11 Jan 2011 Fixed 11.0.1 2996 07 Jun 2013 Fixed Description Runtime errors (for example, conversion errors) during the execution of parallel plans may have caused the server to crash. This was most likely to have occurred when running spatial queries. This has been fixed.

CR:647851

CR Number:   647851 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows NT Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3110 25 Nov 2010 Fixed 12.0.0 2615 25 Nov 2010 Fixed 11.0.1 2529 25 Nov 2010 Fixed 10.0.1 4152 25 Nov 2010 Fixed Description During HTTPS synchronizations, MobiLink clients could have crashed in MobiLink's RSA encryption library. This has been fixed.

CR:647854

CR Number:   647854 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) 12.0.1 3094 09 Nov 2010 Fixed 12.0.0 2608 09 Nov 2010 Fixed 11.0.1 2522 09 Nov 2010 Fixed 10.0.1 4146 09 Nov 2010 Fixed Description When running the fetchtst tool for testing the performance of queries (in samples-dir\SQLAnywhere\PerformanceFetch) on a SQL statement larger than 10K, fetchtst may have crashed. This has now been fixed.

CR:647872

CR Number:   647872 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2590 15 Nov 2010 Fixed Description After installing the 12.0.0 2589 EBF for Windows CE, starting the server would have caused the console window to briefly flash, and then the server would have shut down. This has been fixed.

CR:648045

CR Number:   648045 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   AIX Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3101 17 Nov 2010 Fixed 12.0.0 2611 17 Nov 2010 Fixed 11.0.1 2525 17 Nov 2010 Fixed Description When the Interactive SQL utility (dbisql) was run on AIX systems, interrupting a long-running statement by pressing CTRL-C would have resulted in dbisql crashing. This has been fixed.

CR:648158

CR Number:   648158 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 3104 19 Nov 2010 Fixed 12.0.0 2612 19 Nov 2010 Fixed 11.0.1 2526 19 Nov 2010 Fixed Description Attempting to use an index in a non-system dbspace with a database that was upgraded from 10.x, would have caused an assertion. This has been fixed. Workaround Description  rebuild the database using dbunload -u to do an unordered unload avoiding the corrupt PK's

CR:648179

CR Number:   648179 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 3104 18 Nov 2010 Fixed 12.0.0 2612 18 Nov 2010 Fixed 11.0.1 2526 18 Nov 2010 Fixed 10.0.1 4150 18 Nov 2010 Fixed Description The server could have entered a state where it would consume 100% of a single CPU (ie. one 'core') and never leave that state. The problem was caused by a race condition when more than one thread simultaneously attempted to reference a foreign key index for the very first time; however, the effects of the race condition may not be observed until the server attempts to shut down. This problem has been fixed.

CR:648191

CR Number:   648191 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 3096 11 Nov 2010 Fixed 12.0.0 2609 11 Nov 2010 Fixed 11.0.1 2523 11 Nov 2010 Fixed Description In the Text Configuration Object wizard, the minimum term length could have been set to a value that exceeded the maximum term length. This has been fixed.

CR:648204

CR Number:   648204 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3096 15 Nov 2010 Fixed 12.0.0 2609 15 Nov 2010 Fixed 11.0.1 2523 15 Nov 2010 Fixed Description The changes made for Engineering case 644855 could have resulted in the Interactive SQL utility (and Sybase Central) crashing when displaying a result set if run on Windows Vista or Windows 7. This has been fixed.

CR:648209

CR Number:   648209 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 3097 15 Nov 2010 Fixed 12.0.0 2610 15 Nov 2010 Fixed Description Shared memory connections using the IDLE connection parameter were being dropped after about thirty seconds. This has been fixed.

CR:648218

CR Number:   648218 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 3097 16 Nov 2010 Fixed 12.0.0 2610 16 Nov 2010 Fixed 11.0.1 2523 16 Nov 2010 Fixed Description An aggregate computation on the left side of join may have produced incorrect results when more than one group was generated as a result of a GROUP BY. This has been fixed.

CR:648493

CR Number:   648493 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3101 18 Nov 2010 Fixed 12.0.0 2611 18 Nov 2010 Fixed 11.0.1 2525 18 Nov 2010 Fixed 10.0.1 4149 18 Nov 2010 Fixed Description If Perseat licensing was used, the error "Database server connection limit exceeded" may have been reported when it should not have. In order for this have occurred, in addition to Perseat licensing, the -gm server option, or http connections to disabled databases, must have also been used. When this problem occurred, the first time the error was reported was correct behaviour, but after disconnecting connections, the error may have continued when it should not have. This has now been fixed.

CR:648497

CR Number:   648497 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3100 16 Nov 2010 Fixed 12.0.0 2611 16 Nov 2010 Fixed 11.0.1 2524 16 Nov 2010 Fixed 10.0.1 4148 16 Nov 2010 Fixed Description When a consolidated was running on an Oracle server, the MobiLink server would not have advanced the next_last_download timestamp value (it is used for generating the download in the next synchronization) after it had run for certain time, even if a synchronization did contain a download request. After this occurred, the MobiLink server would have downloaded the same rows over and over again. This has now been fixed. The work around is to restart the MobiLink server.

CR:648499

CR Number:   648499 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 3102 18 Nov 2010 Fixed 12.0.0 2612 18 Nov 2010 Fixed 11.0.1 2524 18 Nov 2010 Fixed Description Incorrect results were possible when an aggregate function was used in an ORDER BY clause, and when the GROUP BY expressions were contained in the ORDER BY expressions. This has been corrected.

CR:648518

CR Number:   648518 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 3104 22 Nov 2010 Fixed 12.0.0 2614 22 Nov 2010 Fixed 11.0.1 2526 22 Nov 2010 Fixed 10.0.1 4150 22 Nov 2010 Fixed Description In very rare cases, the server may have crashed if the cache was low on memory and a SELECT statement contained a very large IN list predicate. This has been fixed. The server will now return the error SQLSTATE_SYNTACTIC_LIMIT.

CR:648631

CR Number:   648631 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3101 18 Nov 2010 Fixed 12.0.0 2611 18 Nov 2010 Fixed 11.0.0 2525 18 Nov 2010 Fixed Description In rare cases, executing a batch statement could have caused a server crash. This has been fixed.

CR:648786

CR Number:   648786 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 3105 23 Nov 2010 Fixed 12.0.0 2614 23 Nov 2010 Fixed 11.0.1 2527 23 Nov 2010 Fixed Description If the primary server in a mirroring system lost quorum, just as an update caused log pages to be sent to the mirror, the primary server could have hung. This has been fixed.

CR:648790

CR Number:   648790 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 3102 18 Nov 2010 Fixed 12.0.0 2612 18 Nov 2010 Fixed 11.0.1 2525 18 Nov 2010 Fixed Description After applying the fix for Engineering case 635815, if an application executed a statement of the form: INSTALL JAVA [NEW | UPDATE] JAR 'jar-name' FROM expression then there was a chance the server would have crashed. This problem has now been fixed.

CR:648799

CR Number:   648799 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 3143 04 Jan 2011 Fixed 12.0.0 3268 04 Jan 2011 Fixed 11.0.1 2541 06 Jan 2011 Fixed Description In some cases, the server could have returned an error ("Parameter error") for a statement using OPENSTRING with a VALUE specifying a field reference or other complex expression. For example, the following sequence could generate this error: declare local temporary table T_strs( str long varchar ); insert into T_strs values ('1,a1\n2,a2'), ('3,b1\n4,b2'); select * from T_strs T cross apply openstring( value T.str ) with( a char(10) ) as O This has been fixed. Statements such as the above are now processed correctly without an error.

CR:648839

CR Number:   648839 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3101 18 Nov 2010 Fixed 12.0.0 2612 18 Nov 2010 Fixed Description When a consolidated database was running on an Oracle server and the MobiLink server login ID did not have permission to access the Oracle gv$transaction table, data that was modified in the Oracle database (without commit) before the MobiLink server started the download could have been excluded in the download stream. Data would never have been downloaded to this remote database, if a timestamp based download was used in their synchronization logic. This has been corrected so that now if the login ID does not have permission to access the gv$transaction table, the MobiLink server will fail the synchronization, if the sync contains a download request, and the generate_next_last_download_timestamp script is not defined. For synchronization logic that does not use timestamp based download, users must grant Select permission to the MobiLink server login ID, or create a script for the generate_next_last_download_timestamp event. This script can be defined as an ignored script using the syntax, '--{ml_ignore}'.

CR:648973

CR Number:   648973 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 3104 18 Nov 2010 Fixed 12.0.0 2612 18 Nov 2010 Fixed 11.0.1 3576 18 Nov 2010 Fixed Description In very rare situations, the server could have crashed while shutting down a connection-scoped external environment process. This problem has now been fixed.

CR:648987

CR Number:   648987 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 3104 18 Nov 2010 Fixed 12.0.0 2612 18 Nov 2010 Fixed Description Entering a string longer than 2048 characters in any of several fields in dialogs of the Relay Server plugin would have caused Sybase Central to crash when the 'OK' or 'Apply' buttons on the dialog were clicked. The fields that caused this issue were: - ID and Description on the "Create Backend Server Farm" dialog - ID, Security Token and Description on the "Create Backend Server" dialog - Description on the "Create Relay Server" dialog These fields now limit input to 2048 characters.

CR:649044

CR Number:   649044 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 3104 19 Nov 2010 Fixed 12.0.0 2612 19 Nov 2010 Fixed 11.0.1 2526 19 Nov 2010 Fixed Description When a backend server drops a connection without providing any HTTP response, IIS ver7 may inject "200 OK" as a response to the client. This may have caused MobiLink clients to be fooled to spin into an infinite loop by repeatedly getting 200OK at high frequency. This change will allow the Relay Server to detect this case and explicit send a "400 Bad request with on backend server response" response.

CR:649123

CR Number:   649123 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3104 22 Nov 2010 Fixed 12.0.0 2613 22 Nov 2010 Fixed 11.0.1 2526 22 Nov 2010 Fixed Description If editing table data using the "Results Panel", (or the "Data" tab in Sybase Central), failed because of a database error, the result would have been a crash (version 11.0.1 and earlier), or an incomplete error message (12.0.0 and later). This has been fixed so that the software does not crash, and the complete error message is displayed.

CR:649135

CR Number:   649135 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3106 22 Nov 2010 Fixed 12.0.0 2613 22 Nov 2010 Fixed 11.0.1 2521 22 Nov 2010 Fixed Description MobiLink clients (except UltraLiteJ) could have failed to authenticate to third party servers when using digest HTTP authentication. In particular, it would have failed when the algorithm was "MD5-Sess" instead of "MD5". This has been fixed.