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

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

CR:621186

CR Number:   621186 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2299 19 Apr 2010 Fixed Description When launching Sybase Central from Finder on Mac OS X systems, the Unload data wizard would have incorrectly unloaded Multi-byte Character Set data. This has been fixed. Note, launching Sybase Central from Terminal would correct the problem.

CR:621318

CR Number:   621318 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 2302 09 Mar 2010 Fixed Description ST_CircularString arcs that contained an intermediate point that was collinear with the start and end points, but was not on the line segment between them, incorrectly passed trivial validation. This has been fixed.

CR:621443

CR Number:   621443 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 2303 09 Mar 2010 Fixed 11.0.1 2407 09 Mar 2010 Fixed Description If a server was asked to make a very large number of external environment calls at the same time, then there was a small chance the server would become unresponsive for 30 or more seconds. This problem has now been fixed.

CR:621504

CR Number:   621504 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 2304 10 Mar 2010 Fixed 11.0.1 2407 10 Mar 2010 Fixed Description The exception System.NullReferenceException could have resulted when using the SQL Anywhere CE Deployment Wizard (cedeploy) on 64-bit Windows to deploy SQL Anywhere to a Windows Mobile device. This problem has been fixed.

CR:621636

CR Number:   621636 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 2305 10 Mar 2010 Fixed 11.0.1 2407 10 Mar 2010 Fixed Description If a call to an HTTP client procedure failed, the server could have leaked memory. This has been fixed.

CR:621652

CR Number:   621652 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 2309 10 Mar 2010 Fixed 11.0.1 2407 10 Mar 2010 Fixed Description If a server was asked to close a large number of connections that had at some point in time made calls to an external Java environment, then there was a chance the external Java VM would have leaked memory if all the connection close requests occurred at the same time. This problem has now been fixed.

CR:621665

CR Number:   621665 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.0 2309 10 Mar 2010 Fixed 11.0.1 2407 10 Mar 2010 Fixed 10.0.1 4042 10 Mar 2010 Fixed Description If an application was connected via jConnect or Open Client, then the connection name for that TDS based connection would have been empty. This has now been fixed and the connection name for TDS based connections will now default to the application name.

CR:621669

CR Number:   621669 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 2310 11 Mar 2010 Fixed Description If a recursive query contained a geometry column, the server would have incorrectly inferred an SRID of 0 for the column. This could have caused a spurious error to be reported. For example, the following example incorrectly returned the error "Transform from SRID 4326 to 0 not supported. SQLCODE=-1444, ODBC 3 State="HY000"": with recursive V( id, geom) as ( select 1, new ST_Point(0,0,4326) union all select id-1, null from V where id=0 ) select * from V This has been fixed.

CR:621682

CR Number:   621682 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 2310 12 Mar 2010 Fixed Description When alerts were sent out via email from the SQL Anywhere Monitor, it was possible that the alert's title would have displayed in a disproportionately large font when viewed in certain mail programs (e.g. Gmail). This has been fixed.

CR:621697

CR Number:   621697 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 2326 19 Mar 2010 Fixed Description Some variants of the ALTER TEXT CONFIGURATION statement could have crashed the version 12 server, if the database was created with an earlier version of the server and not upgraded to version 12. This has been fixed.

CR:621715

CR Number:   621715 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3959 05 Apr 2010 Fixed Description Installing an EBF on top of an existing 9.0.2 OEM Intel Solaris install would have removed the authentication property of the Network server. The has now been corrected. The Personal server was not affected.

CR:621822

CR Number:   621822 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 2322 18 Mar 2010 Fixed 11.0.1 2410 18 Mar 2010 Fixed 10.0.1 4045 18 Mar 2010 Fixed Description A SQL Anywhere webservice client procedure may have truncated an HTTPS response under certain circumstances. This has been fixed.

CR:621827

CR Number:   621827 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 2408 11 Mar 2010 Fixed 10.0.1 4042 11 Mar 2010 Fixed Description Same machine TCPIP broadcasts did not work correctly on Mac OS 10.6. This means that it may have been possible to start multiple database servers with identical names on the same machine when using Mac OS 10.6. This has now been fixed.

CR:621829

CR Number:   621829 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 2335 26 Mar 2010 Fixed 11.0.1 2413 26 Mar 2010 Fixed 10.0.1 4048 26 Mar 2010 Fixed Description If an application attempted to insert data into a proxy table, and one of the columns was an nchar based column, then there was a chance the data would have been truncated. This problem has now been fixed. Note, when creating proxy tables to Oracle tables that contain varchar2 columns, the Oracle ODBC driver does not provide enough information for SQL Anywhere to correctly map the varchar2 columns to nvarchar columns. It is therefore strongly recommended that an explicit column list be used when creating proxy tables to Oracle tables containing varchar2 columns, and that the explicit column list appropriately maps the varchar2 columns to nvarchar columns.

CR:621893

CR Number:   621893 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 2322 16 Mar 2010 Fixed Description Sybase Central would not have displayed Windows services defined by version 9 and earlier software. This has been fixed.

CR:621997

CR Number:   621997 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) 16 Sep 2011 Fixed Description Functions and procedures may now have subselects and subqueries in their parameter expressions. Before this change, an error was returned if a subselect or a subquery was used anywhere in a parameter expression.

CR:622016

CR Number:   622016 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 2314 15 Mar 2010 Fixed Description Selecting NEW ST_Point( 1, 2 ).ST_Z( 3 ) would have returned Point(1 2). It should have returned Point Z ( 1 2 3 ). Likewise for ST_M( 4 ). This has been fixed.

CR:622017

CR Number:   622017 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 2314 12 Mar 2010 Fixed Description Executing SELECT NEW ST_Point( 1, 2 ).ST_Z() would have returned a value of 0. When there is no Z dimension, ST_Z should return NULL. Likewise for ST_M(), ST_MMin(), ST_MMax(), ST_ZMin(), and ST_ZMax(). This has been corrected.

CR:622021

CR Number:   622021 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 2325 18 Mar 2010 Fixed 11.0.1 2411 18 Mar 2010 Fixed 10.0.1 4045 18 Mar 2010 Fixed Description Following the fix for Engineering case 588740, the server could have performed slowly when deleting large numbers of rows concurrently. This has been fixed.

CR:622024

CR Number:   622024 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 2332 24 Mar 2010 Fixed 11.0.1 2413 24 Mar 2010 Fixed 10.0.1 4047 24 Mar 2010 Fixed Description If an application attempted to perform an integrated login from one Windows machine to a SQL Anywhere database server running on a different Windows machine; and the machine that the database server was running on was not the domain controller; and the Windows userid that the application was using was not explicitly mapped in the database; and the application was expecting that the server would instead map the application's Windows userid to a Windows user group on the Domain Controller, then there was a chance the integrated login would fail to map the Windows group. For example: 1) suppose the domain controller was Windows machine DC, and 2) suppose the application was running on Windows machine App with Windows userid AppUser, and 3) suppose the database server was running on Windows machine SAServ with Windows userid ServUser, and 4) suppose the domain controller had a Windows user group GRP of which AppUser was a member, and 5) suppose the database did not grant explicit integrated login privileges to AppUser but instead had granted integrated login privileges to GRP instead, then there was a chance that the application would fail to establish an integrated login to the db userid that GRP was mapped to. This problem has now been fixed.

CR:622058

CR Number:   622058 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2315 15 Mar 2010 Fixed 11.0.1 2409 15 Mar 2010 Fixed Description When MobiLink listeners were connected to a MobiLink server via a persistent sync gateway connection, shutting down the listener would have caused the MobiLink server to report "Ping request failed" as an informational message. This message was non-harmful, but misleading. The MobiLink server will now report "Listener request completed" instead.

CR:622184

CR Number:   622184 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 2562 29 Jul 2010 Fixed 11.0.1 2474 29 Jul 2010 Fixed 10.0.1 4106 29 Jul 2010 Fixed 12.0.1 2989 15 Sep 2010 Fixed Description All CALL statements had the same hash signature when captured by diagnostic tracing, or the Application Profiling wizard. Now, the name of the procedure is incorporated into the signature. This means that the Summary view of captured statements will contain one entry for every procedure, rather than a single entry for all procedures, which makes it easier to identify procedures that need to be looked at for performance reasons.

CR:622352

CR Number:   622352 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 2321 18 Mar 2010 Fixed Description Some valid multi-polygons were incorrectly rejected. For example, a polygon with a hole containing another polygon could have been incorrectly rejected if the contained polygon touched the outer polygon at all of its vertices. For example, the following could have given an error inappropriately: select ST_GeomFromText( 'Polygon ((-7.2 57.914477861, -7.127601901 57.8, -6.9 57.8, -6.9 57.980214095, -7.2 57.936174862, -7.2 57.914477861), (-6.974221298 57.904050613, -7.041167328 57.904889847, -7.061722824 57.953496719, -6.974221298 57.904050613))' ) g, ST_GeomFromText( 'Polygon ((-7.006389618 57.881387711, -6.993610382 57.918611526, -7.077777863 57.879999161, -7.006389618 57.881387711))' ) m, g.ST_SymDifference( m ) This has been fixed.

CR:622512

CR Number:   622512 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 2322 18 Mar 2010 Fixed 11.0.1 2410 18 Mar 2010 Fixed 10.0.1 4045 18 Mar 2010 Fixed Description If an application was connected via jConnect 7 or Open Client 15.5, and the application fetched a datetime value, then the fractional seconds portion of the value would have been returned with six digits of precision; however, fetching a timestamp value would still have returned 1/300th of a second precision. This problem has been fixed and fetching either datetime or timestamp values using jConnect 7 or Open Client 15.5 will now return the full six digits of precision.

CR:622520

CR Number:   622520 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 2322 18 Mar 2010 Fixed Description The following methods had poorly defined behaviour when applied to an empty point. ST_Point::ST_X() ST_Point::ST_Y() ST_Point::ST_M() ST_Point::ST_Z() ST_Point::ST_Lat() ST_Point::ST_Long() ST_Point::ST_X(Double) ST_Point::ST_Y(Double) ST_Point::ST_M(Double) ST_Point::ST_Z(Double) ST_Point::ST_Lat(Double) ST_Point::ST_Long(Double) They have been corrected.

CR:622552

CR Number:   622552 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 2323 18 Mar 2010 Fixed 11.0.1 2410 18 Mar 2010 Fixed 10.0.1 4045 18 Mar 2010 Fixed Description A misconfigured SQL Anywhere webservice function may have caused the server to crash when the function was executed. The problem was specific to a function declaration (not a procedure) that was configured as TYPE 'HTTP:POST:<mimetype>' (ie. mimetype = text/xml) that declares, but does not utilize, all substitution parameters. This has been fixed. The following illustrates the problem, note that the clause consuming the substitution parameter is commented out: create function bad_params(str long varchar, len int) returns long varchar url 'http://127.0.0.1/no_serv

CR:622720

CR Number:   622720 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.0 2323 18 Mar 2010 Fixed 11.0.1 2410 18 Mar 2010 Fixed Description Application using the Ultralite runtime would have sometimes looped endlessly following a synchronization stream error. This has been fixed.

CR:622759

CR Number:   622759 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2326 19 Mar 2010 Fixed 11.0.1 2411 19 Mar 2010 Fixed 11.0.0 1654 19 Mar 2010 Fixed Description When editing table data in an UltraLite database, Sybase Central would not have confirmed delete, update and cancel operations, even when the corresponding UltraLite plug-in preferences were set to confirm these operations. This has now been fixed.

CR:622761

CR Number:   622761 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2326 19 Mar 2010 Fixed 11.0.1 2411 19 Mar 2010 Fixed 11.0.0 1654 19 Mar 2010 Fixed Description When editing table data in an UltraLite database, if a row was deleted and the connection to the database was immediately dropped, then the delete would not have been committed. This has been fixed.

CR:622767

CR Number:   622767 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2326 19 Mar 2010 Fixed 11.0.1 2411 19 Mar 2010 Fixed Description If a user's property sheet was opened, the password changed, Apply clicked and then the password changed and Apply clicked again, Sybase Central would have crashed. This has been fixed.

CR:622789

CR Number:   622789 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 2326 19 Mar 2010 Fixed 11.0.1 2411 19 Mar 2010 Fixed 10.0.1 4046 19 Mar 2010 Fixed Description Applications running on on Windows 7 64 bit systems could have crashed when canceling the methods EndExecuteReader or EndExecuteNonQuery. This problem has been fixed.

CR:622866

CR Number:   622866 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 2459 30 Jun 2010 Fixed 10.0.1 4091 30 Jun 2010 Fixed Description If the MobiLink Server had been started with the "-xo http" or "-xo https" command line options to accept http[s] synchronizations from version 9 or lower MobiLink clients, and the port that was listening for synchronizations received an HTTP request from an HTTP client other than an UltraLite or SQL Anywhere MobiLink client (for example, a web browser), the MobiLink Server would have reported an HTTP error to the HTTP client, posted an error to the ML Server log, but would not have freed the worker thread in the ML Server. Multiple requests from other HTTP clients would have eventually resulted in no threads available to handle additional synchronizations. This has now been fixed, and the worker thread is returned to the pool of available worker threads after the error is reported.

CR:622871

CR Number:   622871 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2411 19 Mar 2010 Fixed Description A NullPointerException was possible when calling a DATEFORMAT function that had a host variable as the first argument. This has been fixed.

CR:622875

CR Number:   622875 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 2434 14 May 2010 Fixed 11.0.1 2436 14 May 2010 Fixed 10.0.1 4070 14 May 2010 Fixed Description If a procedure or function was simple enough that it was inlined during semantic query transformations, and the procedure or function contained uses of a parameter with a different case than the case in the declared parameter list, then the statement could have failed with an error (column not found). In versions 10.0.1 and 11, only simple procedures would have had this problem. In version 12.0.0 (beta), simple user-defined functions could also have exposed this problem. This has now been fixed.

CR:622889

CR Number:   622889 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2327 22 Mar 2010 Fixed 11.0.1 2411 22 Mar 2010 Fixed 10.0.1 4046 22 Mar 2010 Fixed Description When entering a file location in the Deploy Synchronization Model wizard, typing in a file name that did not include the folder would have resulted in an error when clicking Next. This has been fixed. A workaround is to specify the folder.

CR:622934

CR Number:   622934 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 2326 22 Mar 2010 Fixed 11.0.1 2411 22 Mar 2010 Fixed Description If a file browser was open in Sybase Central, the Interactive SQL utility, the Console utility, or the MobiLink Monitor, it was possible to crash the program by clicking on the main application window, pressing the Esc key, and then closing the file browser. This has been fixed.

CR:622944

CR Number:   622944 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2328 22 Mar 2010 Fixed 11.0.1 2412 22 Mar 2010 Fixed 11.0.0 1654 22 Mar 2010 Fixed Description When attempting to Cut and Paste a synchronization profile, the Paste operation would have failed. This has been fixed. Also, if a synchronization profile was first copied to the clipboard and then modified before being pasted back from the clipboard into Sybase Central, then the pasted synchronization profile would have contained the modifications. This behaviour was at odds with all standard clipboard implementations and has been corrected. Now, a copy of the synchronization profile is placed in the clipboard and a copy is pasted from the clipboard so that the pasted object exactly matches the copied object.

CR:623095

CR Number:   623095 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2331 23 Mar 2010 Fixed 11.0.1 2412 23 Mar 2010 Fixed Description The text completer would have suggested names of text index tables, which was not useful. These table names are no longer listed by the text completer.

CR:623106

CR Number:   623106 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2331 23 Mar 2010 Fixed 11.0.1 2412 23 Mar 2010 Fixed 10.0.1 4047 23 Mar 2010 Fixed Description New http, https and oe stream options have been added to the MobiLink server that will cause it to print additional errors, analogous to the errors printed by the -vf option. Usage: -x http(...;log_bad_request={yes|no}) -x https(...;log_bad_request={yes|no}) -x oe(...;log_bad_request={yes|no}) The default value for these noew options is "no". If log_bad_request is enabled and a request disconnects before the server receives a complete set of HTTP headers, the server will print these errors: [-10117] Stream Error: Failed reading an incomplete HTTP request [-10117] Stream Error: This connection will be abandoned because of previous errors If log_bad_request is enabled and a request contains an unknown User-Agent or unknown request type, the server will print these errors: [-10117] Stream Error: Unknown HTTP User-Agent or request type [-10117] Stream Error: This connection will be abandoned because of previous errors This option is most useful when debugging network issues. For example, you can connect to the ML server using a web browser on the remote device and if the device can reach the server, then these errors will be printed.

CR:623115

CR Number:   623115 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2331 23 Mar 2010 Fixed 11.0.1 2401 23 Mar 2010 Fixed Description Sometimes, when printing the error -10193, "Unable to load Assembly ... into domain ...", the MobiLink server would have failed to print why it failed to load the assembly. Also, the MobiLink server would have spuriously printed this error whenever it failed to find a class in the loaded assemblies. These issues have now been fixed.

CR:623270

CR Number:   623270 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 2334 24 Mar 2010 Fixed 11.0.1 2413 24 Mar 2010 Fixed Description The server would have crashed if a parallel archive backup was executed with TRANSACTION LOG ONLY and TRANSACTION LOG RENAME clauses. This has been fixed.

CR:623276

CR Number:   623276 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2427 28 Apr 2010 Fixed 10.0.1 4060 20 Apr 2010 Fixed Description On Windows systems, a reload of a pre-version 10 database file could have hung. Unix systems were not affected. This has been fixed.

CR:623280

CR Number:   623280 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2332 24 Mar 2010 Fixed 11.0.1 2413 24 Mar 2010 Fixed 10.0.1 4047 24 Mar 2010 Fixed Description Renaming a table using its property sheet, and then attempting to open a column's details on the Property sheet's Columns tab, would have caused Sybase Central to crash. This has been fixed.

CR:623281

CR Number:   623281 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) 12.0.0 2365 09 Apr 2010 Fixed 11.0.1 2422 09 Apr 2010 Fixed 10.0.1 4055 09 Apr 2010 Fixed Description Doing absolute fetches from a cursor would have slowed down after one or more tables had been updated many times. Restarting the server would have resolved the problem. This has been fixed.

CR:623292

CR Number:   623292 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 2333 24 Mar 2010 Fixed 11.0.1 2413 24 Mar 2010 Fixed Description The sa_get_request_times and sa_get_request_profile stored procedures did not properly handle request logs created with a non-zero value for the max_client_statements_cached database option when a connection executed the same statement more than once. The number of uses and time used for such statements was reported incorrectly. This has been fixed. A workaround is to set max_client_statements_cached to 0 before creating the request log. Note that if a request log is to be analyzed using the tracetime.pl Perl script, it must also be generated with max_client_statements_cached set to 0.

CR:623303

CR Number:   623303 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2413 25 Mar 2010 Fixed Description Database corruption was possible when there were multiple connections and UPDATE statements are used with one of them. A COMMIT on a connection, when another connection had an uncommitted UPDATE, could have caused the old row in the UPDATE transaction to be incorrectly given the object_id of where that row appeared in the uncommit log. This was corrected.

CR:623308

CR Number:   623308 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 2333 24 Mar 2010 Fixed Description Several of the spatial methods were returning incorrect results when given empty shapes as input: - ST_IntersectsRect should return NULL, but was returning FALSE - ST_Relate( ST_Point() ) should return NULL, but was returning 'FFFFFFFFF' - ST_SnapToGrid( ST_Point(), x, y, z, m ) should return NULL, but was returning an empty point This has been fixed.

CR:623309

CR Number:   623309 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 2333 26 Mar 2010 Fixed Description Calling method ST_IsWorld() on an empty polygon would have crashed the server. This has been corrected and ST_IsWorld() now returns false for an empty polygon.

CR:623323

CR Number:   623323 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2334 25 Mar 2010 Fixed 11.0.1 2413 25 Mar 2010 Fixed Description On the last page of the Create Database wizard, if a database name was specified that differed from the database file name, then the database name would have been ignored. The database would have appeared in the tree using the file name, not the database name that was specified. This has been fixed.

CR:623432

CR Number:   623432 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 2335 26 Mar 2010 Fixed 11.0.1 2413 26 Mar 2010 Fixed 10.0.1 4048 26 Mar 2010 Fixed Description The database server could have leaked memory in rare circumstances when strings were being accessed concurrently. This has been fixed.

CR:623481

CR Number:   623481 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2335 26 Mar 2010 Fixed 11.0.1 2413 26 Mar 2010 Fixed 10.0.1 4048 26 Mar 2010 Fixed Description If the Set Primary Key wizard was proceeded through without making any changes and the Finish button was clicked, then an extraneous error message would have been shown. Now the wizard simply closes.

CR:623487

CR Number:   623487 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 2336 25 Mar 2010 Fixed Description Many spatial methods had incorrect behaviour and/or generated inappropriate errors or assertions when given empty geometries as input parameters. Specifically, the behaviour of the following functions was incorrect: ST_LineString::ST_LineStringAggr ST_Geometry::ST_LinearUnHash ST_Geometry::ST_Transform new ST_LineString new ST_CircularString new ST_CompoundCurve new ST_Polygon new ST_CurvePolygon new ST_GeomCollection new ST_MultiCurve new ST_MultiLineString new ST_MultiPoint new ST_MultiPolygon new ST_MultiSurface These methods have been fixed.

CR:623597

CR Number:   623597 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2336 26 Mar 2010 Fixed 11.0.1 2414 26 Mar 2010 Fixed Description If a table's property sheet, or its Primary Key wizard, was opened while the table's Data tab was showing, then any attempt to modify the table would have resulted in a "Schema upgrade not currently allowed" error. This has been fixed.

CR:623610

CR Number:   623610 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.0 2337 29 Mar 2010 Fixed 11.0.1 2414 29 Mar 2010 Fixed 10.0.1 4048 29 Mar 2010 Fixed Description Processor topology detection for x86/x64 processors has been improved to detect new SMT processors correctly (ie processors with multiple threads per core that are not the older "hyperthread" implementation). Previously, a quad-core i7 (for example) with two threads per core would be detected as 8 cores rather than 4 cores with 2 threads per core. The algorithm for distributing database server threads among logical processors when using less than the maximum concurrency permitted (via the database server -gtc switch) now correctly takes the 3-level chip/core/thread topology into consideration. Generally, this change does not affect licensing since association of a logical processor with the actual chip containing each logical processor was still correct in the old code with the possible exception of some newer Intel 6-core processors. On Mac OS X where the operating system does not provide interfaces to control processor affinity, exact processor topology cannot be determined, so SQL Anywhere treats each logical processor as a separate package or "socket". On multicore and SMT processors, OSX users should purchase the correct license for the hardware they are using, but install a license that will allow the correct amount of concurrency. For example on a quad-core i7 with two threads per core, purchase a license for 1 CPU "socket" but install a license for 8 cpu "sockets" since each processor thread will be treated as a separate CPU socket. Feature tracking code has also been changed so that the 3-level topology, CPU brand string and CPU info registers (which do not form a unique machine identifier) are reported when crash reports are sent to Sybase.

CR:623758

CR Number:   623758 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2339 30 Mar 2010 Fixed 11.0.1 2414 30 Mar 2010 Fixed Description If an attempt to set a database option in the Options dialog resulted in the error "Invalid setting for option '<option-name>'", the Options dialog would then have shown the invalid option value in the options table the next time the dialog was opened. This has been fixed.

CR:623769

CR Number:   623769 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 2414 26 Mar 2010 Fixed 10.0.1 4049 26 Mar 2010 Fixed Description If a TDS based application using a multi-byte character set, connected to an SA database using a single-byte character set, subsequently fetched a char(n) or varchar(n) value, and the char/varchar value resulted in greater than n bytes when converted to the client's multi-byte character set, then the client would have received an incomplete value. This problem has now been fixed.

CR:623779

CR Number:   623779 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 2547 29 Jun 2010 Fixed 11.0.1 2456 29 Jun 2010 Fixed 10.0.1 4089 29 Jun 2010 Fixed 12.0.1 2954 15 Sep 2010 Fixed Description Servers running databases with large schemas may experience periods of unresponsiveness at idle checkpoint time. The performance of checkpoints has been improved to reduce the length of this interval.

CR:623785

CR Number:   623785 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 2441 18 May 2010 Fixed Description Some popular web mapping and visualization applications (Google Earth, Bing Maps, ArcGIS Online) use a Mercator projection based on a spherical model of the Earth. Ignoring the flattening at the poles can lead to errors of up to 800m in position and up to 0.7 percent in scale, but this simplification allows for more efficient projection in these applications. A new spatial reference system with srs_id=3857 has been added to the results of st_geometry_predefined_srs() and the Sybase Central plug in. This srs_id 3857 can be used to work with coordinates provided from these popular applications. Note that ID 3857 as been defined by authority EPSG to refer to this modified spherical Mercator projection. Before this code was defined by EPSG, some applications used an application-defined code 900913 (*) to represent this SRS. The code 3857 is recommended, but compatibility with older applications can be achieved by manually copying the SRS at id 3857 to id 900913 if necessary. In addition, comments are no longer automatically defined for spatial reference systems and units of measure that are pre-defined in a newly created database or created using the sa_install_feature(''st_geometry_predefined_srs') or sa_install_feature('st_geometry_predefined_uom'). (*) The code 900913 is selected by these application because of the resemblance between 9 and lowercase g, giving (900913 == google). http://www.google.com/webhp?hl=xx-hacker&tab=iw

CR:623805

CR Number:   623805 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2339 26 Mar 2010 Fixed 11.0.1 2414 26 Mar 2010 Fixed Description The Relay Server State Manager (rshost) could have crashed if initialization failed before a log file was successfully created. Failure to create the log file, empty config file or missing required sections, were some of the conditions that could have lead to the crash. This has been fixed.

CR:623891

CR Number:   623891 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 2347 31 Mar 2010 Fixed 11.0.1 2417 31 Mar 2010 Fixed 10.0.1 4078 02 Jun 2010 Fixed Description 1) If: - the on_tsql_error database option was set to 'conditional' or 'stop' - the continue_after_raiserror database option was set to 'off' - a RAISERROR statement was executed in a procedure with an exception handler - the exception handler executed a RESIGNAL statement then the procedure's caller would not have been able to obtain the error code used in the RAISERROR statement by examining the SQLCODE variable. The SQLCODE value would be -631 (SQLE_RAISERROR_STMT). 2) If: - the on_tsql_error database option was set to 'conditional' or 'stop' - the continue_after_raiserror database option was set to 'off' - a RAISERROR statement was executed in a trigger with an exception handler - the exception handler executed a RESIGNAL statement then the error would not have been seen by the statement which caused the trigger to fire. This has been fixed. In case 1 above, the value of SQLCODE will now be the error code used in the RAISERROR statement. In case 2, the error will now not be suppressed by the trigger.

CR:624021

CR Number:   624021 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4051 31 Mar 2010 Fixed Description The documentation erroneously indicated that for Windows and Windows CE, if no trusted certificates were provided, MobiLink clients would automatically load the certificates from the OS's trusted certificate store. This feature has now been implemented.

CR:624034

CR Number:   624034 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2344 30 Mar 2010 Fixed 11.0.1 2415 30 Mar 2010 Fixed Description Clicking a column header name in the Results panel to sort the column when all of the rows had not been fetched yet, could have caused the Interactive SQL utility to report an internal error. The problem was timing-sensitive, and did not happen every time. This has been fixed.

CR:624040

CR Number:   624040 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 2344 30 Mar 2010 Fixed 11.0.1 2415 30 Mar 2010 Fixed Description In the Interactive SQL utility, the DESCRIBE CONNECTION command could have returned garbage characters if the connection string contained non-ASCII characters. This has been fixed.

CR:624041

CR Number:   624041 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2344 29 Mar 2010 Fixed 11.0.1 2415 29 Mar 2010 Fixed 10.0.1 4051 29 Mar 2010 Fixed Description If the action command in the message handler did not contain any arguments, the MobiLink Listener may have crashed. This has been fixed.

CR:624046

CR Number:   624046 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 2344 30 Mar 2010 Fixed Description A DML statement inside a derived table block (i.e. SELECT FROM (INSERT/UPDATE/DELETE/MERGE) REFERENCING (...)) could have failed to respect check constraints. This has been fixed.

CR:624047

CR Number:   624047 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 2345 30 Mar 2010 Fixed 11.0.1 2417 30 Mar 2010 Fixed 11.0.0 1654 30 Mar 2010 Fixed 10.0.1 4051 30 Mar 2010 Fixed Description Validating or unloading an empty table could have caused the server to fail an assertion when the database had been started read-only. This would only have happened if the table contained an index, and a truncate table had just been done. This has been fixed.

CR:624179

CR Number:   624179 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 2345 30 Mar 2010 Fixed 11.0.1 2417 30 Mar 2010 Fixed 10.0.1 4051 30 Mar 2010 Fixed Description If an application executed an INSERT statement that contained a file name with escaped single quotes as follows: INSERT INTO directoryTab(file_name, contents) VALUES( 'he''l''lo.txt', 0x0 ) where directoryTab was a directory access table, then the resulting file would incorrectly have been named "he'l'lo.txtxt", instead of the expected name "he'l'lo.txt". This problem has now been fixed.

CR:624183

CR Number:   624183 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 2346 30 Mar 2010 Fixed 11.0.1 2417 30 Mar 2010 Fixed Description As a result of the changes for Engineering case 585282, the maximum packet size for Open Client and jConnect applications was increased from 512 bytes to 4096 bytes. These changes have been extended to allow Open Client and jConnect applications to now negotiate a maximum packet size of 16000 bytes.

CR:624185

CR Number:   624185 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 2344 30 Mar 2010 Fixed Description When using the ST_SnapToGrid overload that specifies an origin point and x/y/z/m grid sizes, the server could have used the wrong grid size for M coordinates. This has now been corrected. For example, the following query returned the wrong answer: select new ST_Point( 1, 2, 3, 4, 504326 ) .ST_SnapToGrid( new ST_Point( 3, 4, 504326 ), 0.1, 0.2, 10, 10 )

CR:624222

CR Number:   624222 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2523 15 Nov 2010 Fixed Description On Windows Vista and later systems running with a language that was not English, the user needed to be a member of the Administrator group in order to start SQL Anywhere Monitor or configure Sybase Central. This has been fixed.

CR:624352

CR Number:   624352 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.0 2338 01 Apr 2010 Fixed 11.0.1 2414 01 Apr 2010 Fixed Description When run on a Windows CE device, the QAnywhere Agent for UltraLite would have failed to connect with a MobiLink server running on the desktop through ActiveSync, if no -x option was specified. The QAnywhere Agent was using "host=localhost" for its stream parameters when no -x option was specified. Now, the agent does not specify stream parameters in this case, letting the UltraLite sync stream choose the default host IP address.

CR:624373

CR Number:   624373 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.0 2359 06 Apr 2010 Fixed Description For a database created using pre-12.x software and then upgraded using 12.x beta software, Sybase Central would not have supported new 12.x features, such as spatial reference systems and sequences. This has been fixed.

CR:624404

CR Number:   624404 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 2365 09 Apr 2010 Fixed 11.0.1 2422 09 Apr 2010 Fixed 10.0.1 4055 09 Apr 2010 Fixed Description If an event made a call out to the Java external environment, then the Java environment would have leaked memory with every iteration of the event. The result would have been an eventual 'out of memory' exception from the Java VM. This problem has now been fixed.

CR:624405

CR Number:   624405 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 2350 01 Apr 2010 Fixed 11.0.1 2417 01 Apr 2010 Fixed Description Adding a member to an empty destination alias would have caused a crash. This has been fixed.

CR:624555

CR Number:   624555 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2367 13 Apr 2010 Fixed 11.0.1 2422 13 Apr 2010 Fixed Description When adding a new table to the remote database schema in a synchronization model, if the remote schema was based on a consolidated database other than SQL Anywhere, and the table was referenced by foreign keys in other tables already copied from the consolidated schema to the remote schema, then an internal error would have occurred. This has been fixed. Note, a workaround is to add the table to the remote schema by using the Update Schema menu item to update the remote schema.

CR:624574

CR Number:   624574 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2352 01 Apr 2010 Fixed 11.0.1 2418 01 Apr 2010 Fixed 10.0.1 4052 01 Apr 2010 Fixed Description Attempting to connect to a newly created message store at the end of the Client Store wizard could have failed there already was network server running the computer and its "-gd ALL" option was not used. This has been fixed.

CR:624586

CR Number:   624586 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 2393 22 Apr 2010 Fixed 11.0.1 2428 22 Apr 2010 Fixed 10.0.1 4061 22 Apr 2010 Fixed Description The Validate Index statement would have placed an exclusive lock on the table, preventing other connections from accessing the table. Alternatively, the connection performing the validate could have blocked waiting for exclusive access to the table. This has been changed so that Validate Index no longer places an exclusive lock on the table.

CR:624727

CR Number:   624727 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2419 05 Apr 2010 Fixed Description Sybase Central could have crashed when opening the Procedures & Functions folder. This has been fixed.

CR:624801

CR Number:   624801 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 2546 22 Jun 2010 Fixed 11.0.1 2454 22 Jun 2010 Fixed 10.0.1 4087 22 Jun 2010 Fixed 12.0.1 2950 15 Sep 2010 Fixed Description An HTTP protocol option specifying a port with no value would have started a listener on the next available port. Specifying a port with no value, or providing a value of zero, is no longer accepted. All protocol options that take a numeric value will no longer accept an empty value as a zero default.

CR:624809

CR Number:   624809 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) 11.0.1 2420 05 Apr 2010 Fixed Description Support for .NET Framework 4 and Visual Studio 2010 has now been added to the SQL Anywhere ADO.Net provider. Three versions of the provider are installed. One for .NET 2.0 / 3.0, one for .NET 3.5, and one for .NET 4.0. Each version contains both assembly and policy files. Here is a list of the files: (1) .NET 2.0 / 3.0 ...\Assembly\V2\iAnywhere.Data.SQLAnywhere.config ...\Assembly\V2\iAnywhere.Data.SQLAnywhere.dll ...\Assembly\V2\iAnywhere.Data.SQLAnywhere.xml ...\Assembly\V2\policy.11.0.iAnywhere.Data.SQLAnywhere.dll (2) .NET 3.5 ...\Assembly\V3.5\iAnywhere.Data.SQLAnywhere.v3.5.config ...\Assembly\V3.5\iAnywhere.Data.SQLAnywhere.v3.5.dll ...\Assembly\V3.5\iAnywhere.Data.SQLAnywhere.v3.5.xml ...\Assembly\V3.5\policy.11.0.iAnywhere.Data.SQLAnywhere.v3.5.dll (3) .NET 4.0 ...\Assembly\V4\iAnywhere.Data.SQLAnywhere.v4.0.config ...\Assembly\V4\iAnywhere.Data.SQLAnywhere.v4.0.dll ...\Assembly\V4\iAnywhere.Data.SQLAnywhere.v4.0.xml ...\Assembly\V4\policy.11.0.iAnywhere.Data.SQLAnywhere.v4.0.dll ...\Assembly\V4\SSDLToSA11.tt The iAnywhere.Data.SQLAnywhere assembly reference can be added in Visual Studio with the Add Reference dialog. Use the one depending on the .NET project as follows: iAnywhere.Data.SQLAnywhere for .NET 2 should be used for .NET 2.0 / 3.0 projects iAnywhere.Data.SQLAnywhere for .NET 3.5 should be used for .NET 3.5 projects iAnywhere.Data.SQLAnywhere for .NET 4 should be used for .NET 4 projects SSDLToSA11.tt is used for generating database schema DDL for Entity Data Models. The SQL Anywhere installer copies this file to the Visual Studio 2010 directory. The DDL Generation property should be set to this file when generating database schema DDL for Entity Data Models.

CR:624826

CR Number:   624826 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 2359 06 Apr 2010 Fixed 11.0.1 2419 06 Apr 2010 Fixed Description Database corruption was possible when a null byte array was assigned to a host variable using the PreparedStatement set method. This has been corrected.

CR:624832

CR Number:   624832 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 2359 06 Apr 2010 Fixed Description The server could have failed to generate a valid internal representation for a Round Earth polygon of a particular shape if the polygon was crossed by equator. This has been fixed.

CR:624956

CR Number:   624956 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.0 2371 13 Apr 2010 Fixed 11.0.1 2423 13 Apr 2010 Fixed Description With dbisqlc, when invoking the "OUTPUT TO" statement without a FORMAT clause, or before explicitly setting the OUTPUT_FORMAT option at least once in a session, the generated output file would not have been in the expected "TEXT" output format (ie comma-separated values). This problem has been fixed. A related change has also been made to the values accepted for the SCREEN_FORMAT option by dbisqlc on UNIX platforms. Prior to this change, dbisqlc accepted both "TEXT" (for the default columnar display) and "ASCII" (for comma-separated values). These options have been renamed to COLUMNS and CSV respectively. The old values of TEXT and ASCII are still accepted but are deprecated.

CR:624960

CR Number:   624960 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.0 2358 06 Apr 2010 Fixed 11.0.1 2419 06 Apr 2010 Fixed Description Each time a table or index was dropped, 16 bytes of store memory was leaked. This could have resulted in a slow growth of the database file over time with an application that created and dropped many tables or indexes. This has now been fixed.

CR:624971

CR Number:   624971 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4057 13 Apr 2010 Fixed Description The database server could have crashed when recovering a database with multiple dbspaces. This has been fixed.

CR:624974

CR Number:   624974 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 2361 06 Apr 2010 Fixed 11.0.1 2420 06 Apr 2010 Fixed Description Following the changes for Engineering case 621443, if an application made an external environment call, and the external environment crashed during that call, then there was a very rare chance the server would also have crashed. This problem has now been fixed.

CR:624986

CR Number:   624986 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.0 2364 09 Apr 2010 Fixed 11.0.1 2422 09 Apr 2010 Fixed 10.0.1 4055 09 Apr 2010 Fixed Description If the Interactive SQL fast launcher was enabled, and there was enough connection information on startup to attempt a connection, the main dbisql window could have, very occasionally, got into a state where it did not paint correctly. This has been fixed. There are a number of workarounds: - Minimize and then restore the dbisql window, or - Resize the window, or - Turn off the fast launcher for dbisql

CR:624989

CR Number:   624989 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2427 14 Apr 2010 Fixed Description Statements containing predicates of the form T.X = R.X where T.X and R.X have different domains could have had poor performance due to a less than optimal access plan generated by the optimizer. Such predicates were not using a join histogram to estimate the selectivity of the predicate. This has been fixed so that join histograms are now built as long as the domains of the columns are both numeric data types. Numeric datatypes include the following: BIGINT BIT DECIMAL DOUBLE FLOAT INTEGER NUMERIC REAL SMALLINT TINYINT

CR:624991

CR Number:   624991 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2362 09 Apr 2010 Fixed 11.0.1 2420 09 Apr 2010 Fixed 10.0.1 4055 09 Apr 2010 Fixed Description If a table was created with a primary key column declared as GLOBAL AUTOINCREMENT when the global_database_id option was set to 0, a performance warning claiming that the column was not indexed would have been written to the server console. This has been fixed.

CR:625011

CR Number:   625011 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2367 13 Apr 2010 Fixed 11.0.1 2424 13 Apr 2010 Fixed Description The iAnywhere and SQL Anywhere JDBC drivers only supported the PreparedStatement methods addBatch() and executeBatch(). Support has now been added for the Statement methods addBatch(), clearBatch() and executeBatch(). Due to the fact that the JDBC specification is unclear on the behaviour of Statement.executeBatch(), the following notes should be considered when using this method with these JDBC drivers: 1) Processing of the batch stops immediately upon encountering a SQL exception or result set. If processing of the batch stops, then a BatchUpdateException will be thrown by Statement.executeBatch(). Calling getUpdateCounts() on the BatchUpdateException will return an integer array of row counts where the set of counts prior to the batch failure will contain a valid non-negative update count; while all counts at the point of the batch failure and beyond will contain a -1. Casting the BatchUpdateCount to a SQLException will provide additional details as to why batch processing was stopped. 2) The batch is only cleared when Statement.clearBatch() is explicitly called. As a result, calling Statement.executeBatch() repeatedly will re-execute the batch over and over again. In addition, calling Statement.execute( sql ) or Statement.executeQuery( sql ) will correctly execute the statement with the "sql" argument, but will not clear the underlying batch. Hence, calling Statement.executeBatch() followed by Statement.execute( sql ) followed by Statement.executeBatch() will execute the set of batched statements, then execute "sql" and then execute the set of batched statements again.

CR:625189

CR Number:   625189 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 2479 08 Jun 2010 Fixed 11.0.1 2447 08 Jun 2010 Fixed 11.0.0 1654 08 Jun 2010 Fixed Description Repeatedly inserting and deleting rows with long strings may have lead to unconstrained database growth. This was more likely to occur if the server was continually under heavy load. In 11.x servers, snapshot isolation must have been enabled for this problem to have occurred. This has now been corrected.

CR:625219

CR Number:   625219 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2416 04 May 2010 Fixed 11.0.1 2432 04 May 2010 Fixed 10.0.1 4066 04 May 2010 Fixed Description A prepared statement was not being dropped when an exception occurred while calling the method SACommand.ExecuteReader. This problem has been fixed.

CR:625305

CR Number:   625305 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 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 Queries that reported warnings could have caused dbisqlc to crash, hang, report that the prepared-statement resource limit had been exceeded, or misbehave in a variety of other ways. This problem has been fixed.

CR:625314

CR Number:   625314 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2571 18 Aug 2010 Fixed 11.0.1 2482 18 Aug 2010 Fixed 12.0.1 3009 15 Sep 2010 Fixed Description It is now possible to use the Script Execution utility (dbrunsql) to reload a database without displaying the GUI, but still log output messages (results) to a file. Previously, if the -q option was not used the dbrunsql gui was shown regardless of the -g setting. Now, the -q and -g switches work together. If -g- is specified, the GUI will not be shown except for error messages. The -q option now only controls if data and warning messages shall be output to the GUI, the console, and/or an output file.

CR:625325

CR Number:   625325 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2365 13 Apr 2010 Fixed 11.0.1 2422 13 Apr 2010 Fixed 10.0.1 4055 13 Apr 2010 Fixed Description When using the Service utility to delete a service that was running, the warning "The specified service is running. The service will be deleted when is is stopped." was reported. The warning should read "The specified service is running. The service will be deleted when it is stopped." The wording has now been corrected.

CR:625329

CR Number:   625329 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 4056 09 Apr 2010 Fixed Description The Service utility was not reporting the warning "The specified service is running. The service will be deleted when it is stopped." when deleting a running service. It was failing to detect the running state of the service during the delete and failing to report the warning as expected. This has been fixed.

CR:625353

CR Number:   625353 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 2365 13 Apr 2010 Fixed 11.0.1 2422 13 Apr 2010 Fixed 10.0.1 4055 13 Apr 2010 Fixed Description Code that attempted to prevent a divide-by-zero condition may have caused the server to crash. This has now been fixed.

CR:625465

CR Number:   625465 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 2372 13 Apr 2010 Fixed 11.0.1 2424 13 Apr 2010 Fixed Description When deploying SQL Anywhere using the Deployment wizard, the PHP Extenv DLLs: (php-<PHP version>_sqlanywhere_extenv11.dll) and PHP SQL Anywhere DLLs (php-<PHP_version>_sqlanywhere.dll) were included, but not the file dbcapi.dll. This has been corrected so that dbcapi.dll is now deployed as well.

CR:625466

CR Number:   625466 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2420 09 Apr 2010 Fixed 11.0.0 1627 09 Apr 2010 Fixed Description When run on a Windows 2008 Server (AMD64) machine, the Sybase Central fast launcher could have failed to re-launch Sybase Central. This has been fixed.

CR:625493

CR Number:   625493 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 2367 13 Apr 2010 Fixed 11.0.1 2422 13 Apr 2010 Fixed 10.0.1 4056 13 Apr 2010 Fixed Description If an application connected using a version of jConnect that did not support bigtime, and the application subsequently prepared a statement that consisted of a batch of insert and select statements, then there was a chance the server would have incorrectly inserted a value of 00:00:00.0 for the time value if one of the parameters to the insert was of type time. This problem has now been fixed.