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

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

CR:617178

CR Number:   617178 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2239 05 Feb 2010 Fixed 11.0.1 2388 05 Feb 2010 Fixed 11.0.0 1654 05 Feb 2010 Fixed 10.0.1 4024 05 Feb 2010 Fixed Description The asynchronous command execution ( BeginExecuteReader and BeginExecuteNonQuery ) could have been blocked by exclusive table locks. This problem has been fixed.

CR:617203

CR Number:   617203 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.0 2235 02 Feb 2010 Fixed 11.0.1 2385 02 Feb 2010 Fixed Description If an ABS() function call was used in a stored procedure, batch statement, or simple SELECT, INSERT, or UPDATE statement, then it was possible for the function to report an overflow error. For this to occur, the argument to the ABS() function must have been a NUMERIC or DECIMAL argument with a precision and scale different from the values specified by database options. This problem has been fixed.

CR:617205

CR Number:   617205 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.0 2233 02 Feb 2010 Fixed Description If a geometry is defined in a round-Earth spatial reference system, attempts to use predicates such as ST_Within() and ST_Contains() should result in an error, as these are not supported on round-Earth geometries. In some cases though, rows could have been rejected before an error was generated, giving the appearance that the predicates were in fact supported. This has been fixed.

CR:617206

CR Number:   617206 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.0 2233 02 Feb 2010 Fixed Description Attempting to compute ST_ConvexHull() or ST_ConvexHullAggr() could have given an error (Value xxxx out of range for coordinate x) if one of the geometries was empty. This has been fixed.

CR:617219

CR Number:   617219 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.0 2233 02 Feb 2010 Fixed 11.0.1 2385 02 Feb 2010 Fixed 10.0.1 4022 02 Feb 2010 Fixed Description If an application connected using Open Client 15.5, and then subsequently attempted to fetch a Time or Timestamp value, then the fetch would have failed with a protocol error. This problem has now been fixed. Note that this problem does not affect versions of Open Client prior to 15.5.

CR:617396

CR Number:   617396 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2248 11 Feb 2010 Fixed Description On 32-bit systems that support dynamic cache sizing, it was possible to set a maximum cache size for the server that would have left insufficient address space for other server operations. The server could then have failed to start, or could have experienced other unpredictable failures. The 32-bit server now automatically reduces the maximum cache size, as well as the initial and minimum cache sizes if necessary, so that at least 512MB of address space is left free for use outside of the cache. On Windows, a 32-bit database server will be limited to a conventional cache of about 1.5GB, 2.5GB or 3.5GB depending on the OS version. To specify a maximum cache size that will leave less than 512MB available, the new "-chx <size>" option can be used instead of "-ch <size>". Note, however, that the use of -chx is strongly discouraged unless great care is taken to evaluate what cache size can safely be used in a specific installation. To use very large caches, the use of 64-bit software is recommended. On 64-bit systems, address space is extremely large and -ch and -chx are equivalent but -ch is preferred.

CR:617397

CR Number:   617397 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2234 04 Feb 2010 Fixed 11.0.1 2387 04 Feb 2010 Fixed 10.0.1 4023 04 Feb 2010 Fixed 9.0.2 3952 04 Feb 2010 Fixed Description By default, the OLE DB provider indicates, through a property settting, that it does not support returning multiple result sets, although the provider is capable of doing so. An undocumented connection option "ASA Multiple Results=TRUE" will enable the returning of multiple result sets. The provider has been changed so that returning of multiple results sets is now supported by default. More specifically, DBPROP_MULTIPLERESULTS is now set to DBPROPVAL_MR_SUPPORTED by default. If desired, the connection option "ASA Multiple Results=FALSE" can be used to change the property value to DBPROPVAL_MR_NOTSUPPORTED. However, there is no known benefit to using this option.

CR:617469

CR Number:   617469 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.0 2236 03 Feb 2010 Fixed Description Execution of the function ST_Boundary() on a collection was including points that should not have been included. The standard states that if a point is included in the boundary of an even number of elements in a collection, then it is not actually part of the boundary for the collection. These were being included incorrectly. This has been fixed.

CR:617470

CR Number:   617470 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.0 2236 03 Feb 2010 Fixed Description When a set operation generated a CircularString, it was output as a LineString. It did not interpolate it, but simply output the control points as LineString control points. This has been fixed.

CR:617606

CR Number:   617606 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.0 2235 03 Feb 2010 Fixed Description Queries using INTERSECT and EXCEPT that were executed with parallel physical operators (e.g., HashIntersect or MergeIntersect), may have returned incorrect results. This has been corrected so that INTERSECT and EXCEPT operators will not be executed in parallel.

CR:617613

CR Number:   617613 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.0 2225 03 Feb 2010 Fixed 11.0.1 2379 03 Feb 2010 Fixed Description If a table was locked by a connection using LOCK TABLE ... WITH HOLD IN EXCLUSIVE MODE and then it was dropped without an intervening commit or rollback, there was a chance that the server could have crashed when the connection disconnected. This has been corrected.

CR:617619

CR Number:   617619 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2246 10 Feb 2010 Fixed 11.0.1 2391 11 Feb 2010 Fixed 10.0.1 4025 11 Feb 2010 Fixed Description If multiple backup statements for the same database were executed concurrently with the WAIT BEFORE START option specified, and there was at least one connection with uncommitted operations, the server could have appeared to hang or run very slowly. This problem has been fixed.

CR:617638

CR Number:   617638 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.0 2236 04 Feb 2010 Fixed Description Under some situations, the server could have crashed while processing an ST_Transform() method to convert a geometry value from one spatial reference system to another. This has been fixed.

CR:617640

CR Number:   617640 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2387 04 Feb 2010 Fixed 10.0.1 4023 04 Feb 2010 Fixed Description Use of a timestamp that had a number of seconds with more than 9 digits after the decimal place could have yielded unexpected results. For example: select datepart( ms, '14:44:33.9876543211' ) would have returned 128, instead of the expected result of 987. This has been fixed by truncating the number of seconds in a timestamp at 9 decimal places before it is used.

CR:617662

CR Number:   617662 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.0 2253 16 Feb 2010 Fixed 11.0.1 2392 16 Feb 2010 Fixed 10.0.1 4027 16 Feb 2010 Fixed Description If an application connected to a case sensitive database executed a remote query that contained a Group By clause, and one of the columns referenced in the Group By had a different case than the column reference in the select list, then the server would have incorrectly failed the query with error -149 "Function or column reference must also appear in a GROUP BY." For example, the following query would have failed: SELECT test.Column1 FROM proxy_t test GROUP BY test.column1 whereas the following queries: SELECT test.column1 FROM proxy_t test GROUP BY test.column1, and SELECT test.Column1 FROM proxy_t test GROUP BY test.Column1 would have succeed. This problem would only have occurred if the local database was case sensitive and proxy_t was a proxy table. This has now been fixed.

CR:617699

CR Number:   617699 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.0 2237 04 Feb 2010 Fixed 11.0.1 2388 04 Feb 2010 Fixed 11.0.0 1654 04 Feb 2010 Fixed 10.0.1 4023 04 Feb 2010 Fixed Description The message "Statement interrupted by user" was not being returned after a user canceled a command. This problem has been fixed.

CR:617804

CR Number:   617804 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.0 2238 08 Feb 2010 Fixed 11.0.1 2388 08 Feb 2010 Fixed 10.0.1 4024 08 Feb 2010 Fixed Description Attempting to execute an INSERT statement with the WITH AUTO NAME clause could have caused the server to crash. This has been fixed.

CR:617811

CR Number:   617811 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4027 16 Feb 2010 Fixed Description If a database server was started with many databases (e.g. 16) that were configured for database mirroring, the mirror server could have hung, causing the primary server to also hang until the mirror server was stopped. This has been fixed. A workaround is to increase the value for the -gn option from its previous setting (default 20) to a value 2 times the number of mirrored databases.

CR:617834

CR Number:   617834 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2238 08 Feb 2010 Fixed 11.0.1 2399 23 Feb 2010 Fixed Description A query with a FULL OUTER JOIN without an ON condition must be interpreted as a KEY FULL OUTER JOIN, but this was not the case. This has been fixed.

CR:618014

CR Number:   618014 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2247 11 Feb 2010 Fixed 11.0.1 2391 11 Feb 2010 Fixed 10.0.1 4026 11 Feb 2010 Fixed Description The TableViewer ADO.Net sample application queries SYSTABLE to determine the table list to display. That query would have incorrectly returned text index tables, if defined, which cannot be directly manipulated. If a query was subsequently issued using a text index table, the error SQLE_TEXT_CANNOT_USE_TEXT_INDEX would have occurred. The query has now been rewritten to only display base tables. Additional changes to the application were also made to improve usability. First, functionality that required an active database connection such as the Execute button are disabled if there is no active connection. Second, a simple SELECT statement is generated based on the table selected from the table list control.

CR:618017

CR Number:   618017 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.0 2239 09 Feb 2010 Fixed Description In some cases, geometry operations were performed with the wrong tolerance or grid size. In these cases, the incorrect tolerance/grid size of 1e-6 would have been used instead of the values from the associated spatial reference system. In certain cases, this could have lead to incorrect answers being returned. This has been fixed.

CR:618049

CR Number:   618049 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.0 2240 08 Feb 2010 Fixed Description Attempting to execute an ATTACH TRACING statement with a LIMIT clause would have failed with a syntax error. This statement can be invoked directly, or by the Application Profiling Wizard or Database Tracing Wizard in the SQL Anywhere plugin for Sybase Central. This has been fixed. Note, this can be worked around by setting the reserved_keywords option to 'limit'.

CR:618100

CR Number:   618100 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.0 2241 09 Feb 2010 Fixed Description When loading from an ESRI shapefile, the geometry values were not converted to the geometry type of the target column. This problem could have lead to geometries of an inappropriate concrete type being stored in a column. This has now been corrected.

CR:618212

CR Number:   618212 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) 12.0.0 2243 09 Feb 2010 Fixed 11.0.1 2389 09 Feb 2010 Fixed 10.0.1 4025 09 Feb 2010 Fixed Description If an application connected using the iAnywhere JDBC driver, and then subsequently called one of the read() overloads of ResultSet.getBlob().getBinaryStream(), if the blob value was a non-NULL zero length long binary value, then the read() method would have incorrectly returned 0, instead of -1 to signal the end of the input stream. This problem has now been fixed. Note, this problem was introduced by the changes for Engineering case 609739.

CR:618244

CR Number:   618244 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2244 09 Feb 2010 Fixed 11.0.1 2390 09 Feb 2010 Fixed 10.0.1 4025 09 Feb 2010 Fixed Description In the Options dialog, when disabling or enabling the fastlauncher checkbox, the "Configure..." button was not disabled or enabled as appropriate as well. This has been fixed

CR:618257

CR Number:   618257 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2254 16 Feb 2010 Fixed 11.0.1 2392 16 Feb 2010 Fixed 10.0.1 4027 16 Feb 2010 Fixed Description In some cases, operations on long strings (blobs) could have leaked memory in the main heap. This memory would not have been reclaimed until the server was restarted. In order for this problem to have occurred, the blob must have been at least 8 database pages long, and must have been accessed using a random-access interface such as byte_substr() with a starting offset of at least 3 times page size. This has been fixed.

CR:618275

CR Number:   618275 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.0 2244 09 Feb 2010 Fixed Description If a table contained a spatial column with spatial indexes, then it was possible in very specific circumstances for the server to hang when committing or rolling back updates or deletes to the table. This has been fixed.

CR:618276

CR Number:   618276 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.0 2244 09 Feb 2010 Fixed Description The st_geometry_describe_type option previously supported 'xml' as a setting. This is no longer permitted.

CR:618278

CR Number:   618278 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.0 2244 09 Feb 2010 Fixed Description A transaction log, which contained any sequence operations, would have caused the server to crash if it was later reapplied (with the -a option). This has been fixed.

CR:618279

CR Number:   618279 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.0 2244 09 Feb 2010 Fixed Description If two or more sequences were used in the same statement, only one would be evaluated, and would supply its results to all sequence references. This has been fixed.

CR:618423

CR Number:   618423 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2247 11 Feb 2010 Fixed 11.0.1 2391 11 Feb 2010 Fixed Description When a download exceeded 4K is size, and the page size had been set to greater than 4K, the synchronization would have failed, possibly with an ArrayIndexOutOfBoundsException. This has been fixed.

CR:618459

CR Number:   618459 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.0 2246 09 Feb 2010 Fixed 11.0.1 2391 09 Feb 2010 Fixed 10.0.1 4025 09 Feb 2010 Fixed Description If a primary server (S1) was somehow frozen for long enough that its connections exceeded the liveness timeout, and then exited the frozen state, the loss of its connection to the mirror server would cause it to send a stale status to the arbiter which should have been disregarded, but was not. Restarting S1 would result in it attempting to become the primary server if a connection to the second mirror server (S2) could not be made, yielding either two primary servers or an alternate server name conflict. This has been fixed. Stale state information will now be disregarded when received.

CR:618587

CR Number:   618587 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 4029 17 Feb 2010 Fixed Description An ALTER DATABASE CALIBRATE DBSPACE TEMPORARY may have caused the server to fail assertion 200501. This has been fixed.

CR:618639

CR Number:   618639 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2248 11 Feb 2010 Fixed 11.0.1 2391 11 Feb 2010 Fixed 10.0.1 4026 11 Feb 2010 Fixed Description When viewing the Application Profiling "Details" pane for a large trace, the pane could have taken a very long time to paint. This has been fixed. Although the pane may still take several seconds to paint, it should be two orders of magnitude faster. Note, users who do not have this fix can still view the underlying data by manually by querying the sa_diagnostic_* tables as described in the documentation.

CR:618644

CR Number:   618644 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.0 2248 11 Feb 2010 Fixed Description Some Round Earth geometries (geometries with SRID=4326) could have been created incorrectly, or failed to be created, if the constructor that used other geometries was used. This has been fixed.

CR:618655

CR Number:   618655 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2246 16 Feb 2010 Fixed Description If data in a CHAR or BINARY column all had the same first 32 bytes, the quality of statistics on the column would have been poor. String histograms in version 10 and later databases are generated with hash keys using the first 32 bytes of the CHAR or BINARY string. This problem has been corrected by generating hash keys using the first 255 bytes of the string, so that different strings will more likely have different hash keys.

CR:618766

CR Number:   618766 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.0 2124 11 Feb 2010 Fixed Description If database mirroring was attempted using a database created prior to version 12 that had not been upgraded, the server would have crashed on startup. This has been fixed. A workaround is to upgrade or rebuild the database.

CR:618804

CR Number:   618804 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) 11.0.1 2395 19 Feb 2010 Fixed Description If a LOAD TABLE ... WITH CONTENT LOGGING statement was executed in a database mirroring environment, and the mirror server was then stopped, restarting the mirror server may have failed with: assertion 100904: failed to redo a database operation - Error: Table 'sa_load_table_data_X' not found This has been fixed. Workarounds for this problem are to add WITH CHECKPOINT ON to the LOAD TABLE statement (which makes the problem much less likely to occur, but does not completely eliminate it), or to use WITH ROW LOGGING instead. Workaround Description  The customer is going to control the timing of when they shutdown their mirror to avoid doing that whil any known load table operations are being applied. Since this is related to a common process in their environment of doing a delete table + load table as a single process, one might be about to avoid this by disconnecting and reconnecting between those; thus always having the connection record immediately before the load table operation. This would make the window of opportunity for this to be exposed as small as is humanly possible; though may not completely eliminate it entirely.

CR:618967

CR Number:   618967 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.0 2258 16 Feb 2010 Fixed 11.0.1 2393 16 Feb 2010 Fixed Description The Interactive SQL utility (dbisql) would have crashed when attempting to export a binary value using an OUTPUT statement with the HEXADECIMAL OFF or HEXADECIMAL ASIS clause. This has been fixed.

CR:618972

CR Number:   618972 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 2258 17 Feb 2010 Fixed 11.0.1 2393 17 Feb 2010 Fixed Description The J2ME Record Store did not record page reads or writes. This has been corrected.

CR:619037

CR Number:   619037 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2262 17 Feb 2010 Fixed 11.0.1 2394 17 Feb 2010 Fixed 10.0.1 4029 17 Feb 2010 Fixed Description If an application opened multiple database metadata result sets, and the application closed the metadata result sets appropriately, there was still a chance that the iAnywhere JDBC driver would have closed one of the open metadata result sets, even though the application had not reached the limit of 3 metadata result sets open at any given time. This problem has now been fixed.

CR:619038

CR Number:   619038 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.0 2263 23 Feb 2010 Fixed Description When running an install created by the 12.0 Beta deployment wizard, it would have recommended the SQL Anywhere 11 folder as the default install location. This has been corrected to default to Program Files\SQL Anywhere 12.

CR:619039

CR Number:   619039 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.0 2260 17 Feb 2010 Fixed 11.0.1 2394 17 Feb 2010 Fixed 10.0.1 4028 17 Feb 2010 Fixed Description The Execute Query menu item was enabled when in the debugger and not at a breakpoint. This has been fixed.

CR:619040

CR Number:   619040 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 2262 18 Feb 2010 Fixed 11.0.1 2394 18 Feb 2010 Fixed Description On Windows systems, the -oe server command line option was ignored if -qi or -qw were also specified. This has been fixed.

CR:619054

CR Number:   619054 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2261 17 Feb 2010 Fixed 11.0.1 2394 17 Feb 2010 Fixed 10.0.1 4029 17 Feb 2010 Fixed Description If the execution of a DELETE statement involved remote tables, and the DELETE statement could not be handled in full passthru, then the server could have failed assertion 201501 "Page for requested record not a table page or record not present on page". This problem has now been fixed, and a proper error message is returned.

CR:619055

CR Number:   619055 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.0 2261 18 Feb 2010 Fixed 11.0.1 2394 18 Feb 2010 Fixed Description If the OS/locale charset did not match the database charset, the contents of the msg_database column in the result set from the sa_server_messages() system procedure would have been mangled. This has now been fixed.

CR:619056

CR Number:   619056 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.0 2260 17 Feb 2010 Fixed Description The server could have crashed while building a text index on very long binary or string values. This has been fixed.

CR:619113

CR Number:   619113 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.0 2272 23 Feb 2010 Fixed 11.0.1 2400 23 Feb 2010 Fixed 10.0.1 4034 23 Feb 2010 Fixed Description In very rare timing depended circumstances, the server may have crashed when querying connection properties for a connection in the process of disconnecting. This has been fixed.

CR:619128

CR Number:   619128 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2262 17 Feb 2010 Fixed 11.0.1 2394 17 Feb 2010 Fixed 10.0.1 4029 17 Feb 2010 Fixed 11.0.0 1654 17 Feb 2010 Fixed Description The server could have failed an assertion, or returned a spurious error, if a query used a keyset cursor or if a keyset cursor was implicitly used in the processing of a DELETE or UPDATE statement. For this to have occurred there must have been concurrent updates (with respect to the lifetime of the keyset). This was most likely to have happened if a global share by all temporary tables was involved. If no temporary tables were involved, only DELETE statements were likely to cause issues. The error most likely to be seen was 'unable to find in index'; assertions included 101412 and 200502 (among others). This has been fixed.

CR:619138

CR Number:   619138 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2277 17 Feb 2010 Fixed 17 Feb 2010 Fixed Description If an embedded SQL application fetched into a SQLDA with a negative sqllen field in a SQLVAR of type DT_VARCHAR, DT_NVARCHAR or DT_BINARY, the fetched value could overrun memory and cause dblib to crash. A negative sqllen could occur if a positive value greater than 32767 was assigned to the sqllen field, since it is 16 bit signed short. Also, fill_sqlda could have filled a sqlda with negative sqllen values for the types DT_VARCHAR, DT_NVARCHAR or DT_BINARY with input sqllen values of 32765 or more. This has been fixed so that the error "Invalid sqllen field in SQLDA" is returned, and fill_sqlda never fills with a negative sqllen value.

CR:619145

CR Number:   619145 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.0 2262 18 Feb 2010 Fixed Description If a query contained a spatial join between two geometry columns that were compared using a relation that was not symmetric (such as ST_Covers), the query could have returned the wrong answer. In order for the wrong answer to be returned, a spatial index must have been used to compute the join. The result set would have missed rows from the index that should have been returned. This has been fixed.

CR:619190

CR Number:   619190 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.0 2274 23 Feb 2010 Fixed 11.0.1 2400 24 Feb 2010 Fixed 10.0.1 4035 24 Feb 2010 Fixed Description A base table with publications was not allowed to be used in any parallel access plan. This has been fixed. Now, a table with publications cannot be used in a parallel plan of a statement if the table is updatable in that statement, and it has publications.

CR:619191

CR Number:   619191 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.0 2263 18 Feb 2010 Fixed Description In some cases, operations that interpolate circular strings to linear segments could have generated duplicate points if the circular string contained more than 3 control points. For example, the following circular string could have generated a duplicate point (20,20) in the result: CircularString (-20 -20, 20 -20, 20 20, -20 20, -20 -20) The duplicated points might not have been noticed, because operations that input a curve drop duplicated points. The extra point could be detected in the output of ST_AsText('version=1.1') though. This has been fixed.

CR:619195

CR Number:   619195 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2418 08 Apr 2010 Fixed Description Generating an MSI install using the Deployment Wizard, should have included these files: IANYWHERE.MOBILINK.CLIENT.DLL IANYWHERE.DATA.SQLANYWHERE.DLL but they were not included in the assembly/v2 directory. These files were being deployed directly into the GAC, but were not being put into the assembly/v2 directory. This has been corrected, and they are now installed into both locations.

CR:619253

CR Number:   619253 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.0 2264 18 Feb 2010 Fixed 11.0.1 2395 18 Feb 2010 Fixed 10.0.1 4029 18 Feb 2010 Fixed Description Executing any query in the Query Database dialog when debugging and at a breakpoint, would have always displayed the error "Invalid plan.". Showing a plan while debugging is not required so the Plan button has been removed.

CR:619254

CR Number:   619254 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2293 05 Mar 2010 Fixed 11.0.1 2405 05 Mar 2010 Fixed 10.0.1 4039 05 Mar 2010 Fixed Description If a database had been initialized with the UCA collation sequence, and to respect accent sensitivity on all UCA string comparisons, it was likely that operations on tables without a SUBSCRIBE BY clause in the publication definition would have failed to replicate. No errors would have been reported, but operations that should have replicated would not have been sent. This has now been fixed.

CR:619257

CR Number:   619257 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.0 2264 18 Feb 2010 Fixed Description When loading string statistics from a database prior to version 12.0, into a version 12.0 database, the string histogram was created but not initialized. In some circumstances, this could have caused the Unload utility (dbunload) to fail. This is fixed by not creating the string histogram when old string statistics are being loaded.

CR:619273

CR Number:   619273 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2401 26 Feb 2010 Fixed Description On Linux systems, Sybase Central would have hung on start-up when loading the UltraLite plug-in. This has been fixed. As a workaround, automatic loading of the UltraLite plugin can be disabled by editing the file "$HOME/.sybase/Sybase Central 6.0.0/.scUserPreferences600" and changing the line "ProviderData/ultralite1101/Autoload=true" to read "ProviderData/ultralite1101/Autoload=false".

CR:619301

CR Number:   619301 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.0 2265 19 Feb 2010 Fixed Description If the database server was launched by dbspawn and it couldn't access a database file due to insufficient permissions, dbspawn would have displayed the error "Specified database file already in use". This has been fixed. It will now display "Database cannot be started -- Access is denied".

CR:619338

CR Number:   619338 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2267 22 Feb 2010 Fixed 11.0.1 2396 22 Feb 2010 Fixed 10.0.1 4033 22 Feb 2010 Fixed Description Attempting to execute a SELECT statement that referenced a stored procedure in the FROM clause could have caused the server to crash. This has been fixed.

CR:619357

CR Number:   619357 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2270 23 Feb 2010 Fixed 11.0.1 2399 23 Feb 2010 Fixed 10.0.1 4034 23 Feb 2010 Fixed Description When an application attempted to make an external environment call, there was a very small chance the server would have crashed if the external environment for that connection shut down at exactly the same time as the application made the external environment call. This problem has now been fixed.

CR:619359

CR Number:   619359 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2302 09 Mar 2010 Fixed 11.0.1 2406 09 Mar 2010 Fixed Description A NullPointerException was possible when there was a small difference in row-limitation thresholds (see ConfigPersistent.setRowMinimumThreshold, setRowMaximumThreshold). This has now been corrected.

CR:619360

CR Number:   619360 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2385 16 Apr 2010 Fixed 11.0.1 2425 16 Apr 2010 Fixed Description UltraLiteJ could not have created a database in BlackBerry internal flash on some models, such as 8300, 9700. This was due to a problem in the BlackBerry software. A solution was found that was not impacted by the bug.

CR:619388

CR Number:   619388 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2265 19 Feb 2010 Fixed 11.0.1 2396 19 Feb 2010 Fixed 10.0.1 4033 19 Feb 2010 Fixed Description When using Sybase Central's fast launcher, the timeout setting was ignored and the launcher continued to run. This has been corrected.

CR:619552

CR Number:   619552 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.0 2271 23 Feb 2010 Fixed 11.0.1 2399 23 Feb 2010 Fixed 11.0.0 1654 23 Feb 2010 Fixed 10.0.1 4022 23 Feb 2010 Fixed Description Queries that used indexed snapshot scans could have returned extra rows. This has been fixed. See also Engineering case 612617.

CR:619558

CR Number:   619558 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.0 2267 22 Feb 2010 Fixed 11.0.1 2396 22 Feb 2010 Fixed Description When using the "Ja_JP" or "JA_JP" locales on AIX, SQL Anywhere incorrectly determined that the OS character set was EUC-JP, whereas AIX actually uses IBM-943 (a.k.a "Windows-31J" and "windows-932") and UTF-8 respectively for those locales. The "ja_JP" locale on all UNIX platforms uses EUC-JP. On AIX 4.2 and earlier, AIX used the IBM-932 character set for the Ja_JP locale. SQL Anywhere does not support AIX 4.2; it does not support the IBM-932 character set which is significantly different from the Windows-932 / Windows-31J character set; and it does not support the "Ja_JP.IBM-932" locale that is available on currently supported versions of AIX. This problem has been fixed.

CR:619595

CR Number:   619595 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.0 2270 24 Feb 2010 Fixed 11.0.1 2399 24 Feb 2010 Fixed 10.0.1 2270 24 Feb 2010 Fixed Description The SQL Anywhere Optimizer now has a new source type for the selectivity estimations of atomic predicates of the form "T.X = R.X", namely JOIN. A selectivity estimation has the "JOIN" source type if it is computed using (1) Primary Key - Foreign Key referential integrity constraints; (2) unique constraints; (3) join histograms. The SQL Anywhere Optimizer uses selectivity estimation sources when redundant predicates are present in a query. Different sources have different qualities, hence predicates with better sources are used when competing predicates are present.

CR:619596

CR Number:   619596 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2398 24 Feb 2010 Fixed Description Partial index scans covered by the same subset of predicates have now normalized cardinality estimation during optimization. Before this change, it would have been possible for partial index scan I1, covered by the predicates {p1,p2, .. pn}, to have had an estimated cardinality greater than another partial index scan I2 covered by a proper subset of predicates P of the set {p1,p2, ..., pn}. This has been fixed.

CR:619597

CR Number:   619597 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2398 24 Feb 2010 Fixed Description Predicates of the form "(p11 and p12 and .. ) OR (p21 and p22 and ... ) OR ( ...)" can be used for multi-index partial scans if for each term "(pi1 and pi2 and ... )" an intersection of indexes can be built. The SQL Anywhere Optimizer failed to build an index scan for a term "(pi1 and pi2 and ... )" if all the predicates can be used in a single index scan. For example: select * from T where (T.X = 10 and T.Y = 20 ) OR ( T.Z = 30 and T.W = 40) create index XY on T(X, Y) create index ZW on T(Z, W) A possible access plan is the union of the index scans: T<XY> UNION T<ZW>.

CR:619613

CR Number:   619613 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2280 01 Mar 2010 Fixed 11.0.1 2403 01 Mar 2010 Fixed 10.0.1 4038 01 Mar 2010 Fixed Description The ODBC functions SQLPrimaryKeys() and SQLForeignKeys() would have returned an incorrect name for the primary key identifier (PK_NAME). It should return the PRIMARY KEY constraint name, but was returning the table name (the "default" primary key name). This problem has been fixed.

CR:619699

CR Number:   619699 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.0 2272 01 Mar 2010 Fixed Description A full text index built on data containing multibyte characters could have contained incorrect characters when an external prefilter and/or term breaker library was used. This has been fixed.

CR:619719

CR Number:   619719 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.0 2268 23 Feb 2010 Fixed 11.0.1 2397 23 Feb 2010 Fixed 11.0.0 1654 23 Feb 2010 Fixed 10.0.1 4033 23 Feb 2010 Fixed Description ADO.Net client applications could have hung in very rare circumstances when fetching data readers. This problem has been fixed.

CR:619728

CR Number:   619728 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2273 25 Feb 2010 Fixed 11.0.1 2400 25 Feb 2010 Fixed Description If rebuilding a database failed for some reason, the Unload utility (dbunload) would have output some unnecessary information to unprocessed.sql. This has been fixed.

CR:619746

CR Number:   619746 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2401 25 Feb 2010 Fixed Description IS NOT NULL predicates were incorrectly being generated for expressions which cannot be null, that is for the null-supplying side of OUTER JOINs. These extra predicates may have resulted in less than optimal access plans. This has been fixed.

CR:619758

CR Number:   619758 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.0 2273 26 Feb 2010 Fixed 11.0.1 2400 26 Feb 2010 Fixed Description When connected to a database running on a Windows Mobile (Windows CE) device, if the database's Overview tab was selected, then Sybase Central would have crashed. This has been fixed.

CR:619911

CR Number:   619911 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2333 24 Mar 2010 Fixed 11.0.1 2413 24 Mar 2010 Fixed Description Executing a query of the form: SELECT ... FROM dirTab WHERE file_name='...' where dirTab is a directory access table, then the server would have incorrectly returned a result set in cases where the specified file_name extended beyond the subdir limit of the directory access server. This problem has now been fixed and a proper empty result set now gets returned for file names that violate the subdir limit.

CR:619926

CR Number:   619926 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.0 2276 26 Feb 2010 Fixed 11.0.1 2401 26 Feb 2010 Fixed Description Stored procedures that contained simple queries over a single table (or the implied DUMMY table), that were run many thousands of times by the same connection, may have consumed more CPU after many thousands of executions. This problem would only have occurred if the same connection executed the same queries in a procedure more than 65000 times before disconnecting. This has been fixed. A workaround is to periodically issue an inconsequential DDL statement to the server (for example, CREATE TABLE FOO(id int); DROP TABLE FOO). This will flush the plan caches and allow each connection to use fully-cached plans for these simple statements. This issue had no impact on statements involving more than one table, or on statements that are not subject to plan caching.

CR:619937

CR Number:   619937 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2400 25 Feb 2010 Fixed 10.0.1 4035 25 Feb 2010 Fixed Description An embedded SQL application that attempted to fetch into a sqlvar of type DT_VARCHAR, DT_NVARCHAR or DT_BINARY, with a negative sqllen, could have crashed due to a memory overrun. A negative sqllen with these types is invalid and should never be passed to DBLib. DBLib has now been fixed to make the memory overrun less likely.

CR:619950

CR Number:   619950 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2276 25 Feb 2010 Fixed 11.0.1 2401 25 Feb 2010 Fixed 11.0.0 1654 25 Feb 2010 Fixed 10.0.1 4036 25 Feb 2010 Fixed Description The Unload utility (dbunload) was failing to add the length information for VARBIT user domain definitions in the reload.sql file. This has been fixed.

CR:619976

CR Number:   619976 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.0 2279 01 Mar 2010 Fixed 11.0.1 2402 01 Mar 2010 Fixed 10.0.1 4037 01 Mar 2010 Fixed Description The server could have crashed when executing an aggregate function that operated on string data when the Group By operator was forced into a low-memory strategy. This has been fixed. A workaround is to increase the amount of memory available to the server.

CR:620095

CR Number:   620095 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 3126 11 Jan 2011 Fixed 12.0.0 2631 11 Jan 2011 Fixed 11.0.1 2544 11 Jan 2011 Fixed 10.0.1 4182 17 Feb 2011 Fixed Description Several stability problems existed with parallel queries when using low-memory strategies, which could have lead to server hangs or crashes. These have been fixed. A workaround for these problems is to disable parallelism by setting the option MAX_QUERY_TASKS=1 for all affected queries.

CR:620110

CR Number:   620110 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.0 2455 25 May 2010 Fixed 11.0.1 2441 25 May 2010 Fixed Description Under rare circumstances, a crashed database could have failed to recover with the message: "Unable to start specified database: Cannot use log file '%1' since it is shorter than expected". No data was actually been lost, but the log metadata would have needed to be patched by hand to allow the database to recover. This problem, while very rare, was more likely on systems with very large transactions running on a small number of connections. This has been fixed.

CR:620136

CR Number:   620136 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.0 2278 26 Feb 2010 Fixed 11.0.1 2401 26 Feb 2010 Fixed 10.0.0 4036 26 Feb 2010 Fixed Description The SQL Anywhere OLEDB provider's result sets for PRIMARY_KEYS and FOREIGN_KEYS did not show the correct constraint name (PK_NAME column). Instead, they listed the table name. This problem has now been corrected.

CR:620253

CR Number:   620253 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.0 2124 25 Mar 2010 Fixed 11.0.1 2413 25 Mar 2010 Fixed Description Permission checking for materialized views was being incorrectly done in some cases, resulting in errors, for example: "Assertion Failed 102907 (11.0.1.xxxx) Could not generate triggers for immediately materialized view". This has been fixed.

CR:620287

CR Number:   620287 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.0 2279 26 Feb 2010 Fixed 11.0.1 2402 26 Feb 2010 Fixed 10.0.1 4037 26 Feb 2010 Fixed 9.0.2 3955 26 Feb 2010 Fixed Description The SQL Anywhere OLE DB provider would have leaked memory if the InsertRow method was called with no row handle return pointer. For example, HRESULT hr = rowset::InsertRow( hChapter, hAccessor, pData, NULL ); would have resulted in a memory leak, since phRow (the 4th argument) is NULL. This problem may have occurred when using the provider with SQL Server Integration Services (SSIS). This problem has been fixed.

CR:620289

CR Number:   620289 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.0 2279 26 Feb 2010 Fixed 11.0.1 2402 26 Feb 2010 Fixed 10.0.1 4037 26 Feb 2010 Fixed 9.0.2 3955 26 Feb 2010 Fixed Description If the length for a data column was described as SQL_NTS (-3), the SQL Anywhere OLE DB provider would not have computed the correct length for the column on 64-bit platforms. This problem has been fixed. Note, this problem was seen with SQL Server Integration Services applications on 64-bit Windows platforms, it does not appear in ADO applications.

CR:620324

CR Number:   620324 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.0 2280 01 Mar 2010 Fixed 11.0.1 2402 01 Mar 2010 Fixed Description The server may have incorrectly set the transfer-encoding when processing an HTTP request that failed with a SQL error. The problem may have occurred when the SQL error was generated from within a sub-select. This has been fixed.

CR:620474

CR Number:   620474 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2291 03 Mar 2010 Fixed 11.0.1 2404 03 Mar 2010 Fixed 10.0.1 4039 03 Mar 2010 Fixed Description If the primary server (S1) in a database mirroring environment was running in a VM and the VM was paused or otherwise inactive for sufficient time that the mirror server's connection to S1 was dropped, causing a failover to the mirror (S2) , then when S1 was resumed it would not have realize that a failover has occurred and would have continued to act as a primary. This has been fixed.

CR:620496

CR Number:   620496 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2286 02 Mar 2010 Fixed 11.0.1 2403 02 Mar 2010 Fixed Description When deploying a synchronization model to a new remote database, if the remote database schema had multiple foreign keys to multiple non-primary key columns in a table, a deployment error could have occurred with the following description: "Error for: Method makeUniqueConstraints threw exception for reference $HELPER in template script-defs\remote.vm" This has been fixed.

CR:620753

CR Number:   620753 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) 04 Mar 2010 DEFER Description Plan Viewer displays wrong information on nodes if the plan consists >= 4 nodes Workaround Description  Not to use plan viewer, instead using sp_showplan.

CR:620795

CR Number:   620795 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2317 15 Mar 2010 Fixed 11.0.1 2409 15 Mar 2010 Fixed 10.0.1 4044 15 Mar 2010 Fixed Description The function count_set_bits may have returned a number that was too large, if a bitwise NOT operation had previously been applied to the operand. This has been fixed.

CR:620977

CR Number:   620977 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 4039 04 Mar 2010 Fixed Description If many databases were started for mirroring on a single server, the server could have hung after running for 30 minutes or more. This has been fixed. See also Engineering case 617811.

CR:620981

CR Number:   620981 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2157 05 Mar 2010 Fixed Description The Relay Server State Manager (rshost) would have crashed on Linux systems when run with no parameters. This has now been fixed.

CR:620985

CR Number:   620985 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2278 04 Mar 2010 Fixed 11.0.1 2401 04 Mar 2010 Fixed Description The MobiLink server would have reported the error, ".NET CLR Host encountered unexpected error." (SQLCODE -10167), instead of error, "Assembly '%1!s!' does not contain '%2!s!'" (SQLCODE -10172), when a .NET method could not be found. This has been fixed.

CR:621019

CR Number:   621019 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.0 2320 16 Mar 2010 Fixed Description In the new dashboard-based interface for the SQL Anywhere Monitor, it was found that the menu buttons for customizing a dashboard and widget were sometimes too difficult to see; particularly when the user is new to the Monitor. In an effort to address this issue, several changes have been made to the Monitor's web-based interface to facilitate the user's recognition of these menu buttons. The most noticeable change is that the dashboard's customize menu button now includes the text "Customize". As well, the old "configure" menu options in both the dashboard and widget customize menus has been renamed to "settings" to avoid confusion between "customizing" and "configuring". Also, in an effort to make the customize menus "pop" more, the menu buttons will now take on a highlighted look when the user mouses over any part of the widget/dashboard title bar; instead of just when the user mouses over the menu button, as it was previously. As a further visual indicator that a widget can be dragged/moved, when the user mouses over the widget title bar, the mouse cursor now changes to a "grabbing hand" cursor.

CR:621038

CR Number:   621038 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.0 2301 08 Mar 2010 Fixed 11.0.1 2406 08 Mar 2010 Fixed Description Executing an ALTER USER statement with LOGIN POLICY clauses, on a database created with version 10.0.1 and not upgraded, could have caused a server crash. This has been fixed. Workaround Description  Rebuild the database. Problem won't happen with database crashed in v11.

CR:621121

CR Number:   621121 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.0 2300 05 Mar 2010 Fixed 11.0.1 2406 05 Mar 2010 Fixed Description If all of the following conditions were true, the result set for a procedure would not have been defined properly after a rebuild: - procedure P1 generates a result set using a SELECT which references another procedure P2 in the FROM clause - P1 did not include a RESULT clause defining the result set - the procedure id of P1 was less than that for P2 This has been fixed.

CR:621159

CR Number:   621159 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.0 2297 08 Mar 2010 Fixed Description Archive backups and databases restored from archive backups could have been corrupt. This has been fixed.

CR:621162

CR Number:   621162 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.0 2303 09 Mar 2010 Fixed 11.0.1 2407 09 Mar 2010 Fixed 10.0.1 4041 09 Mar 2010 Fixed Description A SQL Anywhere 'RAW' web service having been defined with AUTHORIZATION ON, would have failed to the service when it had an AS NULL statement. This has been fixed. Note, service types: HTML, XML, RAW, JSON may contain a NULL statement only with AUTHORIZATION ON, DISH services always contain a NULL statement and SOAP services must contain a (non-NULL) statement.

CR:621179

CR Number:   621179 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2299 08 Mar 2010 Fixed Description When installed on a Mac OS X system to a path with MBCS characters, launching Sybase Central from Finder for the first time would have failed to register the plugins. The following error would have been given: The SQL Anywhere 12 plug-in could not be loaded because it uses components that are not accessible. Please change the classpath in the plug-in properties. java.lang.ClassNotFoundException: ianywhere.sa.plugin.SAPlugin This has been fixed. Workaround 1: Launching Sybase Central from Terminal would correctly register the plugins. Workaround 2: Set the LANG environment variable in the Finder's environment. To do this, add the LANG environment variable to ~/.MacOSX/environment.plist, log out, then log back in.