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

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

CR:606229

CR Number:   606229 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) 11.0.1 2347 10 Nov 2009 Fixed 10.0.1 3986 10 Nov 2009 Fixed 9.0.2 3915 10 Nov 2009 Fixed Description When using the SQL Anywhere OLE DB provider, a memory leak cpuld have occurred when fetching data LONG VARCHAR or long VARBINARY columns. This problem has been fixed.

CR:606247

CR Number:   606247 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2063 11 Nov 2009 Fixed 11.0.1 2349 12 Nov 2009 Fixed Description When unloading VARCHAR or LONG VARCHAR data, the special characters "(double quote) and `(apostrophe) were not replaced by their escaped counterparts " and ' in XML. This may have caused the unloaded XML file to be invalid. In addition the characters \r(carriage return), \n(line break) and \t(tab) were not replaced by the character references and . As a result the these characters were being treated exactly the same as empty spaces in the unloaded XML file. These problems have now been fixed.

CR:606273

CR Number:   606273 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 2347 11 Nov 2009 Fixed Description When the SQL statement ALTER TABLE ADD FOREIGN KEY was executed, the system table sysfkcol did not contain the foreign columns for the new foreign key. This meant that the foreign key relation would have been corrupt once the database reboots. This has been fixed.

CR:606440

CR Number:   606440 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) 11.0.1 2349 12 Nov 2009 Fixed 10.0.1 3987 12 Nov 2009 Fixed Description If a DSN was created using the Data Source utility (dbdsn), attempting to modified the userid or password of the DSN using the ODBC Administrator would have reported no errors, but it would have failed to change either of these fields. This has been fixed.

CR:606445

CR Number:   606445 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 2063 13 Nov 2009 Fixed Description When setting up a download subset in a synchronization model, either by Mobilink user or remote id, the list for choosing a column to match included columns with incompatible types. This has been corrected so now columns with incompatible types are not listed.

CR:606464

CR Number:   606464 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2349 11 Nov 2009 Fixed Description Queries with null-supplying derived tables, which have constants in the select list, may have failed with "Run time SQL error -- *** ERROR *** Assertion failed: 106105". This has been fixed.

CR:606465

CR Number:   606465 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 2077 20 Nov 2009 Fixed 11.0.1 2354 20 Nov 2009 Fixed 10.0.1 3990 20 Nov 2009 Fixed Description If the "kerberos" connection parameter, or its short form "krb", was given on the command line, the Interactive SQL utility would not have connected to the database unless a userid was also given. This has been fixed.

CR:606626

CR Number:   606626 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2350 13 Nov 2009 Fixed Description When using the Interactive SQL utility (dbisqlc) to connect, and attempting to use integrated logins or kerberos, (i.e. dbisqlc -c "integrated=yes" or dbisqlc -c "kerberos=yes"), it would have displayed the connection dialog without first attempting to connect. Similarly, the the statements CONNECT USING 'integrated=yes' and CONNECT USING 'kerberos=yes' with dbisqlc, would also have displayed the connection dialog without first attempting to connect. This has been fixed so that a connection with be attempted in these cases and if the connection attempt is successful, the connection dialog will not be displayed.

CR:606629

CR Number:   606629 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2064 12 Nov 2009 Fixed 11.0.1 2350 12 Nov 2009 Fixed Description When the XML input to ULjLoad contained one of the two following scenarios, ULjLoad would have rejected the file, even when it should have accepted it. 1. If a foreign key constraint comes before the definition of the primary table; 2. If the order of the tables in the data part does not follow the order of the tables in the schema part; These problems have been fixed, but rearranging the schema definition or the data in the XML will workaround these problems.. Workaround Description  Workarounds exist to these problems; rearranging the schema definition or the data in the XML will fix them.

CR:606642

CR Number:   606642 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) 11.0.1 2350 13 Nov 2009 Fixed 10.0.1 3987 13 Nov 2009 Fixed 9.0.2 3916 13 Nov 2009 Fixed Description If a division by zero error occurred in a result set, the SQL Anywhere OLE DB provider would have returned DB_S_ENDOFROWSET instead of 0x800a000b (divide by zero). For example, the following SELECT statement will result in a division by zero error if the column value for "num" is 3: SELECT num/(num-3) FROM divisionby0 This problem has been fixed. ADO will now set the correct error number (11) and description (Division by zero) from the error code returned by OLE DB.

CR:606651

CR Number:   606651 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 2354 20 Nov 2009 Fixed 10.0.1 3990 20 Nov 2009 Fixed Description The creation of a proxy procedure for a procedure on a remote server may have caused a server crash, or failed assertion 201503, if a proxy procedure with the same name had been dropped as part of the execution of a DROP REMOTE SERVER statement. This has now been fixed. A work around for the problem is to drop all proxy procedures belonging to a remote server before executing the DROP REMOTE SERVER statement.

CR:606658

CR Number:   606658 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 2065 13 Nov 2009 Fixed 11.0.1 2350 13 Nov 2009 Fixed Description When shuting down the Relay Server for Apache on Linux, one persistent System V semaphore for IPC was being leaked between Relay Server components. This has been fixed.

CR:606660

CR Number:   606660 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 2072 17 Nov 2009 Fixed 11.0.1 2347 17 Nov 2009 Fixed Description When working with clients that don't support communication liveness, such as MobiLink 9.x clients, the Relay Server will timeout a client after being idle for 8 minutes, if the web server has not timed out the client earlier. Increasing the web server liveness timeout will not resolve the situation. The solution is to use the IAS-RS-App-Timeout-Minute header in the http request. For example, to set a 20 minute timeout for a big download with a MobiLink version 9.x client, simply add custom_header=IAS-RS-App-Timeout-Minute:20 to the HTTinkP synchronization communication option. This timeout header is an existing but undocumented feature in all released version of the Relay Server. There is no software change involved.

CR:606678

CR Number:   606678 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2350 13 Nov 2009 Fixed Description If a database contained BINARY type data that ended with one or more bytes of 0's, the 0's would have be truncated by ULjUnload when written to the output. This has been fixed.

CR:606683

CR Number:   606683 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) 11.0.1 2352 18 Nov 2009 Fixed Description The build number on policy.11.0.iAnywhere.Data.SQLAnywhere.dll is incorrect. This has been corrected.

CR:606726

CR Number:   606726 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 2066 16 Nov 2009 Fixed 11.0.1 2350 16 Nov 2009 Fixed Description If the Table editor or the Column property sheet was used to change a column's data type and its unique setting to 'not unique', then the change from 'unique' to 'not unique' would have been ignored. This has been fixed.

CR:606823

CR Number:   606823 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3015 24 Aug 2010 Fixed Description The date at the beginning of the connection attempt information generated by the LogFile connection parameter was not necessarily in the locale format. This also affected the information in the Show Details dialog when using the ODBC Administrator's Test Connection feature. This has been fixed so these dates are now in the locale format.

CR:606826

CR Number:   606826 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 2066 16 Nov 2009 Fixed 11.0.1 2350 16 Nov 2009 Fixed Description An incomplete startup of the Relay Server on Linux due to resource limitations, may have left many persistent System V semaphores behind. This would have caused a permanent semaphore resource drain to the system until they were either manually deleted, or the system was rebooted. This issue has now been fixed.

CR:606828

CR Number:   606828 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2324 20 May 2010 Fixed Description When creating a Synchronization Model with a Sybase ASE consolidated database, the following error may have occurred when installing the MobiLink system setup: [Sybase][ODBC Driver][ASE] Foreign key table qualifier must be name of current database This has been fixed.

CR:606833

CR Number:   606833 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 2191 17 Dec 2009 Fixed Description Malformed or unexpected HTTP and HTTPS requests would sometimes have been closed by the MobiLink server without issuing a response. This has been corrected so that the MobiLink server now issues an HTTP or HTTPS error prior to closing the socket.

CR:606835

CR Number:   606835 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 2066 17 Nov 2009 Fixed 11.0.1 2350 17 Nov 2009 Fixed 11.0.0 1654 17 Nov 2009 Fixed 10.0.1 3988 17 Nov 2009 Fixed Description The reason reported by the server for failing to start a database may have been incorrect. When attempting to open a file, the server will retry on certain errors. If it retries too many times it just reports 'database not found'. This behaviour was much more likely with the changes for Engineering case 605413, as sharing violations were now retried. This behaviour has now been changed so that the server reports the last OS error when it fails to open the database file.

CR:606840

CR Number:   606840 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2439 21 May 2010 Fixed Description When running on Windows Vista or Windows 7 systems, menu items that toggle a property on or off would not always have shown the check mark next to the menu item's text. Similarly, menu items that choose a value from a mutually exclusive set of values would not always have shown a sphere next to the currently selected value. Both of these problems have been fixed.

CR:606841

CR Number:   606841 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 2066 16 Nov 2009 Fixed 11.0.1 2350 16 Nov 2009 Fixed 10.0.1 3988 16 Nov 2009 Fixed Description When using the Table wizard to create a new table, if the F5 key was pressed before saving the table, and answering 'No' to the "Do you want to save changes" dialog, would either have caused Sybase Central to crash or have caused the dialog to have been displayed repeatedly. This has been fixed.

CR:606848

CR Number:   606848 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2492 09 Sep 2010 Fixed Description Executing a REORGANIZE TABLE statement on a table having an IMMEDIATE text index would have caused the index size to double. Additionally, under some rare circumstances, incorrect results could have been returned for subsequent full text queries. This has been fixed. Note, if there exists a text index in a database affected by this problem, it should be dropped and recreated to reclaim the space and avoid possible wrong results for full text queries.

CR:606858

CR Number:   606858 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2153 17 Nov 2009 Fixed 11.0.1 2350 17 Nov 2009 Fixed 10.0.1 3988 17 Nov 2009 Fixed Description A possible, but unlikely, security hole involving secure communications on MacOS systems has been fixed.

CR:606882

CR Number:   606882 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2211 14 Jan 2010 Fixed Description When the MobiLink client's startup/options dialog was used to enter options, such as the publication or MobiLink password, it was possible that the synchronization would complete successfully, but the client would then crash when shutting down. This has been fixed.

CR:606888

CR Number:   606888 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 2088 27 Nov 2009 Fixed 11.0.1 2357 27 Nov 2009 Fixed 10.0.1 3993 27 Nov 2009 Fixed Description When redeploying a synchronization model to a SQL Anywhere remote database using the wizard initialized with the last settings, the extended options for the SQL Anywhere client could have been corrupted. This has been fixed.

CR:606991

CR Number:   606991 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 2365 16 Dec 2009 Fixed Description Starting a database, which had been backed up on a Windows CE device, could have caused "Assertion Failed: 201129 (version.build) File is shorter than expected". This problem was introduced in Engineering case 576669. This has now been fixed.

CR:607048

CR Number:   607048 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 2071 17 Nov 2009 Fixed 11.0.1 2351 17 Nov 2009 Fixed Description When using the Table Editor for SQL Anywhere or UltraLite, or when using the Table Mapping Editor for MobiLink, a check box would sometimes have required two single clicks to change its value. This has been corrected so that only a single click is sufficient.

CR:607061

CR Number:   607061 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) 11.0.1 2351 17 Nov 2009 Fixed Description The DBTools function DBCreatedVersion() was not able to handle databases that used strong encryption. This has been fixed.

CR:607117

CR Number:   607117 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 2072 17 Nov 2009 Fixed 11.0.1 2352 17 Nov 2009 Fixed Description Use of the WEEKS() and DAYS() functions could have erroneously thrown an OVERFLOW exception. This has now been corrected.

CR:607234

CR Number:   607234 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 2072 19 Nov 2009 Fixed 11.0.1 2352 19 Nov 2009 Fixed 11.0.0 1654 19 Nov 2009 Fixed Description The SQL Anywhere Python database interface, now works with Python 3.x.

CR:607303

CR Number:   607303 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 2073 19 Nov 2009 Fixed 11.0.1 2352 19 Nov 2009 Fixed Description If F5 was pressed, or View -> Refresh Folder was selected, while creating a new table in the Table Editor and Yes was answered when prompted to save the table, right-clicking to display a popup menu would have failed. This has been fixed.

CR:607330

CR Number:   607330 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2353 18 Nov 2009 Fixed 10.0.1 3990 18 Nov 2009 Fixed Description The SQL Anywhere C API was fetching the TINYINT data type as a signed value. This has been fixed.

CR:607425

CR Number:   607425 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2352 18 Nov 2009 Fixed 9.0.2 3918 18 Nov 2009 Fixed Description The number of nullable columns in a table is limited. This limitation is based on the page size of the database. For 4K pages, the limit is approximately 32000 columns. Attempting to add too many nullable columns to a table using ALTER TABLE would have resulted in a failed assertion, rather than an error message. This has been fixed.

CR:607636

CR Number:   607636 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2076 19 Nov 2009 Fixed 11.0.1 2354 19 Nov 2009 Fixed Description Under virtually all circumstances, the Database Information utility (ULjInfo) would have terminated abnormally when opening a valid database file. The error message would have been "getOrdinal(string) not supported". This has been corrected.

CR:607651

CR Number:   607651 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 2224 25 Jan 2010 Fixed 11.0.1 2380 25 Jan 2010 Fixed 10.0.1 4018 25 Jan 2010 Fixed Description In extremely rare circumstances, fetching a string from a table could have caused the server to hang. This would only have occurred if the string was longer than the prefix size of the column, but less than the page size of the database, and a string manipulation function such as TRIM() was being used, and another connection was attempting to update the string at the same time. This has been fixed.

CR:607874

CR Number:   607874 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2362 07 Dec 2009 Fixed Description The SQL Anywhere C API version of DBD::SQLAnywhere perl driver did not fetch floating point/double values correctly (incorrect values would have been returned). This problem has been fixed.

CR:607881

CR Number:   607881 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) 12.0.0 2211 20 Nov 2009 Fixed 11.0.1 2375 08 Jan 2010 Fixed Description The MobiLink server would have reported error -10152 if a Java class loaded for scripting contained overloaded methods, and would have failed with an AmbiguousMatchException if a .NET class contained overloaded methods. This restriction has been lifted. This is most useful for the authenticate_parameters script, as now remotes can send different numbers of authentication parameters and the MobiLink server will choose the method that most closely matches those parameters. For example, suppose a class Test exists: public class Test { public static String auth( InOutInteger status, String user_name, String p1, String p2 ) { return "insert into j_authparm_T2 (pk, c1, c2, c3) values (?,?,?,?)"; } public static String auth( InOutInteger status, String user_name, String p1, String p2, String p3 ) { return "insert into j_authparm_T2 (pk, c1, c2, c3, c4) values (?,?,?,?,?)"; } } Then the auth method can be registered as the script for the authenticate_parameters event: call ml_add_java_connection_script( 'the version', 'authenticate_parameters', 'Test.auth' ) and invoking dbmlsync with different -ap switches will give different behaviour: "-ap parm1,parm2" will call the first 'auth' overload "-ap parm1,parm2,parm3" will call the second 'auth' overload "-ap parm1" will print the error, "[-10362] No overload matching 'auth(ianywhere.ml.script.MLInOutInteger, java.lang.String, java.lang.String)' was found in class 'Test'", because there are not enough parameters to call any of the overloads "-ap parm1,parm2,parm3,parm4" will invoke the second 'auth' overload, but the returned SQL will cause error "[-10094] Expecting 3 authentication parameter(s) from client, but received 4 for script insert into j_authparm_T2 (pk, c1, c2, c3, c4) values (?,?,?,?,?)" because the MobiLink server will accept a Java or .NET authentication_parameters script if it has the same number of parameters or fewer, but SQL authentication_parameters scripts must match the exact number of parameters. Some future version of the server may place that restriction on Java and .NET authentication_parameters scripts as well.

CR:607934

CR Number:   607934 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 2079 23 Nov 2009 Fixed 11.0.1 2354 23 Nov 2009 Fixed Description The system functions DAYS() and WEEKS(), when called with a single argument under J2ME, could have generated incorrect results that were off by one. This was now been corrected.

CR:607936

CR Number:   607936 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2079 23 Nov 2009 Fixed 11.0.1 2354 23 Nov 2009 Fixed Description When a nullable column had a column default specified, and a row with that column set to null was inserted, the null value is ignored and the column default value was inserted instead. This behaviour was incompatible with UltraLite and SQL Anywhere. More seriously, when a nullable column had a column default specified, and the table with that column was altered by an ALTER TABLE statements, all the rows with null values in that column would have been replaced by the column defaults. The following SQL statements were affected. In all these cases, null values would have been replaced by column defaults. 1. INSERT () VALUES (); 2. INSERT () select-statement; 3. ALTER TABLE ADD column-definition; 4. ALTER TABLE DROP column-name; 5. ALTER TABLE ALTER column-definition. This has been corrected. Now all the null values are preserved in these scenarios.

CR:608095

CR Number:   608095 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) 11.0.1 2356 24 Nov 2009 Fixed Description When continually making ODBC connections/disconnections, using SQLConnect()/SQLDisconnect(), a memory leak would have occurred in the application. The process heap would continue to grow as the application looped. This has been fixed.

CR:608101

CR Number:   608101 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 2082 23 Nov 2009 Fixed 11.0.1 2355 23 Nov 2009 Fixed Description When processing a synchronization download, rows with VARCHAR columns that had the total size exceeding the database page size would still have been downloaded and processed. Following the synchronization, if these rows were deleted, the database would have been in an error state. For example, if the page size is 256, then the maximum size of VARCHAR columns is 243, due to page overhead. However, UltraLiteJ would have accepted a VARCHAR of 244 bytes long during download. This has been fixed. Now UltraLiteJ will properly reject rows that are too big due to VARCHAR columns' sizes, which means the synchronization will fail.

CR:608106

CR Number:   608106 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2083 23 Nov 2009 Fixed 11.0.1 2355 23 Nov 2009 Fixed 10.0.1 3992 23 Nov 2009 Fixed Description If an application called ResultSet.getObject() on a tinyint column, and the column value ranged from 128 to 255, then the JDBC driver would have incorrectly thrown a SQLException with a conversion error. This problem has now been fixed.

CR:608314

CR Number:   608314 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2365 17 Dec 2009 Fixed Description When the Application Profiling wizard was run on an encrypted database, it would have failed with the error: "This database does not support encrypted tables." This has now been fixed.

CR:608321

CR Number:   608321 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 2084 24 Nov 2009 Fixed 11.0.1 2356 24 Nov 2009 Fixed Description A host variable used by itsself as an item in an IN list could have caused a crash (Null pointer exception). This has now been corrected.

CR:608332

CR Number:   608332 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 2085 24 Nov 2009 Fixed 11.0.1 2356 24 Nov 2009 Fixed Description When executing a SQL statement that lead to an internal conversion between Numeric types, the source Numeric value may have been corrupted by the conversion. For example, if a value 5.12 in a Numeric(5,2) column was converted to a Numeric(5,1) column, the source value would have been changed to 5.10 after the conversion. This has been fixed.

CR:608339

CR Number:   608339 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 2355 24 Nov 2009 Fixed Description On 11.0.1, builds 2309 through 2312 inclusive contained the fix for Engineering case 588740; however, builds 2313 through 2354 inclusive accidentally reverted back to the old behaviour. This regression has been fixed. Note, testing has shown that the new correct behaviour can cause a significant performance degradation for server running databases without a transaction log (where every commit becomes a checkpoint). The amount of degradation will depend on the application, and on the hardware in use.

CR:608342

CR Number:   608342 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 2085 25 Nov 2009 Fixed 11.0.1 2356 25 Nov 2009 Fixed 10.0.1 3992 25 Nov 2009 Fixed Description A server participating in a mirroring system may, on rare occasions, have crashed if an outgoing connection to another server participating in the mirroring system failed. This has now been fixed.

CR:608354

CR Number:   608354 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 2095 01 Dec 2009 Fixed 11.0.1 2358 01 Dec 2009 Fixed Description The use of a host variable as the right operand of a LIKE operator, could have given incorrect results when an index was used to optimize the search condition. This was corrected.

CR:608552

CR Number:   608552 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 2088 26 Nov 2009 Fixed 11.0.1 2357 26 Nov 2009 Fixed 10.0.1 3993 26 Nov 2009 Fixed Description In rare cases, the executing the ATTACH TRACING statement could have caused the server to crash. This has been fixed.

CR:608728

CR Number:   608728 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) 11.0.1 2360 04 Dec 2009 Fixed 10.0.1 3996 04 Dec 2009 Fixed Description If a connection string was made up of parameters coming from different sources (i.e. the connection string itself, DSNs or file DSNs, SQLCONNECT environment variable), and the UID and PWD/ENP parameters were not specified in the same source, the PWD/ENP would have been ignored. For example, if DSN "foo" contained a UID but no PWD, then the connection string "DSN=foo;PWD=secret" would ignore the PWD field. This has been fixed.

CR:608737

CR Number:   608737 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 2096 01 Dec 2009 Fixed 11.0.1 2359 01 Dec 2009 Fixed Description When utilities or applications attempt to connect to a database with 10000 or more rows and 5 or more indexes, the exception 'java.lang.OutOfMemoryError: Java heap space exception' could have occurred if lazy index loading was disabled. This has been fixed. The handling of large numbers of indexes has been improved and utilities now use lazy loading, but it is possible for this exception to still occurr for large databases. A work around is to increase the heap space in the java starting line by adding the VM option -Xmx256m. This also applies to the batch file that starts uljunload, uljload and uljinfo.

CR:608742

CR Number:   608742 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 2088 26 Nov 2009 Fixed 11.0.1 2357 26 Nov 2009 Fixed Description The following statements were added e added in version 11.0.1: CREATE ENCRYPTED [TABLE] DATABASE newfile FROM oldfile KEY newkey [ALGORITHM alg] [OLD KEY oldkey] CREATE DECRYPTED DATABASE newfile FROM oldfile KEY oldkey Execution of either of these statements in the Interactive SQL utility would have left the values of "oldKey" or "newKey" in plain text in the command history. This has been corrected so that these values are now obfuscated.

CR:608743

CR Number:   608743 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 4010 06 Jan 2010 Fixed Description When installing an MSI created by the Deployment wizard which contained Sybase Central and one or more plugins, on Windows Vista or Windows 7, it would have failed with the error: "The exception unknown software exception (0xc000000d) occurred in the application at location 0x10001d3d." The install would have completed, but the plugins were not correctly registered. This has been fixed.

CR:608747

CR Number:   608747 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Microsoft Windows NT Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2089 27 Nov 2009 Fixed 11.0.1 2357 27 Nov 2009 Fixed Description The Relay Server Outbound Enabler may have reported session mismatch errors when an Afaria client disconnect their POST channel. This has been fixed.

CR:608750

CR Number:   608750 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2089 27 Nov 2009 Fixed 11.0.1 2357 27 Nov 2009 Fixed Description If an application called ResultSet.getObject() on an unsigned smallint, int or bigint column, then the JDBC driver may have given a conversion error. This problem has now been fixed such that calling ResultSet.getObject() on an unsigned column will now promote the datatype. Hence, calling ResultSet.getObject() on an unsigned smallint column will now return an int; similarly, an unsigned int column will now return a long, and an unsigned bigint column will now return a BigDecimal. It should be noted that most applications prefer to have full control on the column object so it is always better to use one of the getShort(), getInt(), getLong() and getBigDecimal() methods explicitly rather than using an implicit method like getObject().

CR:608751

CR Number:   608751 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2089 27 Nov 2009 Fixed 11.0.1 2357 27 Nov 2009 Fixed Description If an application called IBlob.getBytes() with a position value <= 0, or a length value < 0, then the getBytes() method would have incorrectly returned NULL. The JDBC driver now correctly throws a SQLException for these cases.

CR:608904

CR Number:   608904 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2357 01 Dec 2009 Fixed 11.0.0 1654 01 Dec 2009 Fixed 10.0.1 3994 01 Dec 2009 Fixed 9.0.2 3925 01 Dec 2009 Fixed Description Additional drive flushing was added to improve recoverability (see Engineering case 588740); however, this flushing could have made the server significantly slower when no transaction log was present due to every commit causing a checkpoint. This performance issue has been addressed by reverting to the old flushing behaviour when no transaction log is being used.

CR:609049

CR Number:   609049 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2358 01 Dec 2009 Fixed Description Some server, database, or connection properties may have shown values that were too large, or that have rolled over. This would only have happened on single core machines running the Personal server (dbeng11) on Unix platforms (but not Linux). This has been fixed.

CR:609050

CR Number:   609050 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 2228 10 Feb 2010 Fixed Description Query execution strategies that required the materialization of intermediate results (e.g. DISTINCT) may have used excessive memory when strings or blobs longer than the PREFIX length, but shorter than a page size, were involved in the query. This may have caused the query execution engine to switch to a low-memory strategy causing poor performance. This has been fixed. Note, using compressed columns will avoid the bad-code path and is a suitable work-around for this problem.

CR:609062

CR Number:   609062 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2095 01 Dec 2009 Fixed 11.0.1 2358 01 Dec 2009 Fixed Description The MobiLink client (dbmlsync) was leaving a small fixed amount of memory unfreed on shutdown. This should not have been visible to users, and has now been fixed.

CR:609096

CR Number:   609096 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 2096 01 Dec 2009 Fixed 11.0.1 2358 01 Dec 2009 Fixed Description Rows containing non-ascii7 characters in VARCHAR() columns (but not LONG VARCHAR columns) would have resulted in strings padded at the end with '\u0000' characters. For example (using SQL escape sequences) the string 'Ann\u00E9e' would have downloaded as 'Ann\u00E9e\u0000' the and string 'Enqu\u00EAte qualit\uooE9 deux' would have downloaded as 'Enqu\u00EAte qualit\uooE9 deux\u0000\u0000'. This has been fixed.

CR:609310

CR Number:   609310 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 2097 02 Dec 2009 Fixed 11.0.1 2359 02 Dec 2009 Fixed Description The fix for Engineering case 570493, in very rare cases, could have caused the server to hang with one CPU at 100% usage when shutting down a database with many events. This has been fixed.

CR:609449

CR Number:   609449 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows NT Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2352 02 Dec 2009 Fixed Description FIPS 140-2 certified encryption is now supported by the MobiLink server on 64-bit (x64) Windows. If the "FIPS-approved Strong Encryption" feature is not already installed, proceed as follows after applying the EBF: - From Add & Remove Programs, select SQL Anywhere 11 and click the Change button. - Select the Add option and enter the Add-on Registration Key and click Next. - In the dialog, ensure that the "FIPS-approved Strong Encryption" feature is selected and proceed. If the "FIPS-approved Strong Encryption" feature is already installed, proceed as follows after applying the EBF: - From Add & Remove Programs, select SQL Anywhere 11 and click the Change button. - Select the Modify option and de-select the "FIPS-approved Strong Encryption" feature, to temporarily remove it, and proceed. - Again from Add & Remove Programs, select SQL Anywhere 11 and click the Change button. - Select the Modify option and select the "FIPS-approved Strong Encryption" feature and proceed.

CR:609454

CR Number:   609454 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2368 24 Dec 2009 Fixed 10.0.1 4005 24 Dec 2009 Fixed Description When trying to bind null values for string or blob columns, the SQL Anywhere C API would have crashed in the call to sqlany_execute(). This has been fixed. Also, when binding null values, dbcapi required a valid type to be specified. This is no longer required.

CR:609701

CR Number:   609701 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) 10.0.1 4010 04 Dec 2009 Fixed 9.0.2 3934 04 Dec 2009 Fixed Description The sample ECC certificate eccroot.crt shipped with versions 9.x and 10.x expired on November 17, 2009. As a result, the sample server certificate sample.crt has also expired, since it was signed by eccroot.crt. These have been replaced by new sample ECC certificates. The new server certificate is called eccserver.crt, and its password is "test". The file name for the signing certificate is still eccroot.crt but the certificate itself is different.

CR:609704

CR Number:   609704 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2100 04 Dec 2009 Fixed 11.0.1 2360 04 Dec 2009 Fixed 10.0.1 3996 04 Dec 2009 Fixed Description When calling the SQL Anywhere C API function sqlany_clear_error() the resulting SQLSTATE value would have been set to the empty string instead of "00000". This has been fixed.

CR:609706

CR Number:   609706 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 2100 07 Dec 2009 Fixed 11.0.1 2361 09 Dec 2009 Fixed 11.0.0 1654 09 Dec 2009 Fixed 10.0.1 4034 23 Feb 2010 Fixed Description When running, the database cleaner could have interfered wth transactions by causing locking attempts to fail. This has been fixed by having the requesting transaction wait for the cleaner.

CR:609707

CR Number:   609707 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2363 10 Dec 2009 Fixed Description When running the MobiLink server in a server farm, it was possible for the MobiLink server to have printed errors to the MobiLink log that dealt with problems on operations to the ml_active_remote_id table. These errors are now suppressed, and more meaningful warnings or errors are printed to the MobiLink log.

CR:609708

CR Number:   609708 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2360 07 Dec 2009 Fixed 10.0.1 3996 07 Dec 2009 Fixed Description When using the SQL Anywhere C API and binding parameters for prepared statements and calling sqlany_execute() multiple times, the second and subsequent calls to sqlany_execute() would have failed with the error "Cursor already open". The problem was introduced as part of the changes for Engineering case 560351. This has now been fixed.

CR:609736

CR Number:   609736 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2101 04 Dec 2009 Fixed 11.0.1 2360 04 Dec 2009 Fixed 10.0.1 3996 04 Dec 2009 Fixed Description If an application had a connection that was holding on to table locks, and the same application had other connections that were blocked in the server waiting for the table locks to be released, then there was a chance the application would have hung if the connection holding on to the table locks subsequently called Connection.createStatement(). This problem has now been fixed.

CR:609739

CR Number:   609739 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2101 04 Dec 2009 Fixed 11.0.1 2365 04 Dec 2009 Fixed 10.0.1 4001 04 Dec 2009 Fixed Description When an application retrieved a Blob object by calling ResultSet.getBlob(), and the application subsequently retrieved the Blob's InputStream by calling Blob.getBinaryStream(), the applications performance would have been severely impacted if the application called InputStream.read( byte[] ) or InputStream.read( byte[], int, int ) on the Blob InputStream. This problem has now been fixed. Note that a workaround is to use Blob.getBytes() directly, instead of using the Blob InputStream.

CR:609944

CR Number:   609944 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2103 10 Dec 2009 Fixed 11.0.1 2362 10 Dec 2009 Fixed Description When running the Relay Server Outbound Enabler (ROSE) and the backend server on slow machines, the RSOE may have failed to notify the Relay Server (RS) that the backend connection for a non-persistent http request had been closed, which would have caused the RS to hold on to resources for an extended period of time, making the RS less scalable. This problem has been fixed.

CR:609953

CR Number:   609953 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 2103 08 Dec 2009 Fixed 11.0.1 2360 08 Dec 2009 Fixed Description The HTTP server may have crashed due to certain circumstances. This has been fixed.

CR:610115

CR Number:   610115 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2362 08 Dec 2009 Fixed 10.0.1 3998 08 Dec 2009 Fixed 9.0.2 3929 08 Dec 2009 Fixed Description The database server was vulnerable to a particular type of denial-of-service attack. This has been fixed.

CR:610118

CR Number:   610118 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2181 08 Dec 2009 Fixed Description When using the UltraLiteJ Database Transfer desktop application for USB transfer, the utility may have crashed with the error "A fatal error has been detected by the Java Runtime Environment". This would have been seen when the desktop application started ("Start" is pressed in the GUI) before the BlackBerry application was started("Next" is pressed on the final screen). This problem occurs with BlackBerry Desktop Manager 5.0.1, but it could have occurred in other versions as well. In order to function properly, the BlackBerry application must start before the desktop application. This has been resolved. The BlackBerry application's on-screen instruction of the correct order of starting the two pieces has been updated.

CR:610141

CR Number:   610141 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 2107 08 Dec 2009 Fixed 11.0.1 2361 08 Dec 2009 Fixed Description When the Relay Server State Manager was run on Linux with the -os command line option, it would have generated many small archive output log files once the archiving process had started. The logger's size counter wasn't being reset after successfully generating the first output archive file. This has now been fixed.

CR:610279

CR Number:   610279 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 2363 10 Dec 2009 Fixed Description The use of a host variable in the left operand of a LIKE operator could have given incorrect results. This was corrected.

CR:610505

CR Number:   610505 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2110 09 Dec 2009 Fixed 11.0.1 2362 09 Dec 2009 Fixed 10.0.1 3999 09 Dec 2009 Fixed Description Attempting to renaming an index (or text index) to an invalid name, would have resulted in unexpected behaviour of following statements related to the index. This has been fixed.

CR:610520

CR Number:   610520 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 2362 10 Dec 2009 Fixed Description The STRING() SQL function would have returned NULL when any of the parameters were null. This has been corrected so that if any parameters passed to the STRING() function are non-NULL, then any NULL parameters are treated as empty strings. This now conforms with the SQL Anywhere server.

CR:610533

CR Number:   610533 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2111 10 Dec 2009 Fixed 11.0.1 2362 10 Dec 2009 Fixed 10.0.1 3999 10 Dec 2009 Fixed Description If an application retrieved a ResultSet via a DatabaseMetaData call, and the application subsequently retrieved the underlying Statement object of that ResultSet by calling ResultSet.getStatement(), then attempting to close that DatabaseMetaData Statement object could have crashed the application. The problem with closing DatabaseMetaData Statement objects has now been fixed. Note that in general, applications do not explicitly need to close DatabaseMetaData Statement objects; hence the chances of an application crashing due to this problem are rare. Closing the ResultSet of a DatabaseMetaData call is not uncommon and not affected by this.

CR:610718

CR Number:   610718 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 2363 10 Dec 2009 Fixed 10.0.1 3999 10 Dec 2009 Fixed Description If an application executed an UPDATE statement, and the UPDATE statement involved proxy tables, then the server may have crashed when the UPDATE statement could not be handled in full passthrough mode. This problem has now been fixed, and a proper error message is returned.

CR:610723

CR Number:   610723 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 2363 10 Dec 2009 Fixed 10.0.1 3999 10 Dec 2009 Fixed Description If the Data Source utility (dbdsn) was used to create an ODBC data source, but the -c option was not specified, a data source would have been created containing "LINKS=ShMem,TCPIP". This has been fixed, the -c option is now required when -w is used.

CR:610724

CR Number:   610724 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) 11.0.1 2363 15 Dec 2009 Fixed 10.0.1 4001 15 Dec 2009 Fixed Description Problems with an LDAP server could have caused a SQL Anywhere server, or a client application using it, to hang. Calls to the LDAP library were synchronous, so if the LDAP server was hung and did not respond, the SA server would have waited forever for a response. This has been fixed by making the LDAP library calls asynchronous and adding a timeout.

CR:610948

CR Number:   610948 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 2365 16 Dec 2009 Fixed Description Attempting to execute an ALTER TABLE statement that added a primary or foreign key would have returned a Runtime SQL error (SQLCODE -300) if the option row_counts had been turned on. The workaround is to temporarily turn the option off. This has been fixed.

CR:610974

CR Number:   610974 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 2363 14 Dec 2009 Fixed Description If a REFRESH MATERIALIZED VIEW staement was executed with the WITH ISOLATION LEVEL SNAPSHOT clause, and database recovered was later attempted using the transaction log, recovery would have failed when attempting to access the view. This has been fixed.

CR:610982

CR Number:   610982 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) 12.0.0 2208 11 Jan 2010 Fixed 11.0.1 2373 11 Jan 2010 Fixed 11.0.0 1654 11 Jan 2010 Fixed 10.0.1 4013 11 Jan 2010 Fixed 9.0.2 3943 11 Jan 2010 Fixed Description When installing SQL Anywhere on a Windows system that used a multibyte character set as the ANSI code page, the SQL Anywhere performance monitor counters may not have been registered correctly and no error message would have been displayed. At startup, the server would have displayed the message "Unable to initialize NT performance monitor data area; server startup continuing". This problem has now been fixed.

CR:611017

CR Number:   611017 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) 11.0.1 2365 16 Dec 2009 Fixed 10.0.1 4002 16 Dec 2009 Fixed 9.0.2 3924 16 Dec 2009 Fixed Description When the OLE DB provider's GetNextRows method was called, the next row would not have been read if the previous row had NULL column values. This problem was introduced by the changes for Engineering case 605058, and has now been fixed.

CR:611168

CR Number:   611168 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2366 21 Dec 2009 Fixed 10.0.1 4003 21 Dec 2009 Fixed Description ODBC drivers support standard escape sequences in bound data as a driver-independent way to specify date and time literals, outer joins and procedure calls. The SQL Anywhere driver was failing to recognize these escape sequences when embedded in a bound parameter that contained a Unicode string. This has been fixed.

CR:611184

CR Number:   611184 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 2364 15 Dec 2009 Fixed Description Attempting to convert a string to a UUID when the string included braces as the first and last characters, would have resulted in a conversion error. This has been fixed.

CR:611227

CR Number:   611227 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 2365 16 Dec 2009 Fixed 10.0.1 4001 16 Dec 2009 Fixed Description The MESSAGE statement did not allow specifying the EVENT, SYSTEM LOG and DEBUG ONLY clauses at the same time. This has now been corrected.

CR:611262

CR Number:   611262 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 18 Jan 2010 Presently Not Targeted For Any Future Release Of This Product Description Customer try to setup Mobilink Server with Consolidate Database ASE Cluster Edition using the SDK15 ODBC driver. According to SDK document, the SDK ODBC Driver "libsybdrvodb.so" require third party Driver Manager. With the ODBC DSN, Mobilink Server try to load the ODBC driver when the client sync. request, then Mobilink Server will crash.

CR:611350

CR Number:   611350 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 2363 15 Dec 2009 Fixed Description The server may have hung while generating a cache dump. This has been fixed.

CR:611361

CR Number:   611361 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2365 16 Dec 2009 Fixed Description Using Sybase Central to cancel a system message that resided in a QAnywhere Client database would have resulted in an unhandled Null Pointer Exception. This has been fixed

CR:611368

CR Number:   611368 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2365 16 Dec 2009 Fixed Description The Interactive SQL utility (dbisql) was using only the "sqlconnect" environment variable when connecting from the command line, where it should have been using "SQLCONNECT", as it did in version 10 and earlier. Now, dbisql will look for "SQLCONNECT", and if that variable is not set, it will look for "sqlconnect". This is the same algorithm used by the non-graphical command line tools (e.g. dbping). Note, the "ULSQLCONNECT" environment variable is now treated the same way. This change only affects machines running non-Windows operating systems.

CR:611373

CR Number:   611373 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 1835 15 Dec 2009 Fixed 11.0.1 2376 15 Dec 2009 Fixed 10.0.1 4001 15 Dec 2009 Fixed 15 Jan 2010 Fixed Description The MobiLink server could have occasionally given the following error: A downloaded value for table 'table_name' (column #column_number) was either too big or invalid for the remote schema type and then aborted the synchronization, when a client was trying to download data from a table that contained NCHAR, NVARCHAR or LONG NVARCHAR columns, even when NCHAR, NVARCHAR or LONG NVARCHAR data was uploaded in a previous synchronization. This problem has now been fixed.

CR:611414

CR Number:   611414 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) 11.0.1 2365 17 Dec 2009 Fixed 10.0.1 4001 17 Dec 2009 Fixed Description When using the iAS Oracle ODBC driver, attempting to execute an INSERT, UPDATE, or DELETE statement with SQLExecDirect immediately after executing a SELECT statement with the same statement handle, would have failed with the following error message: ORA-24333: zero iteration count This problem is fixed now.

CR:611611

CR Number:   611611 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2365 16 Dec 2009 Fixed 10.0.1 4002 16 Dec 2009 Fixed Description If an application executed a query similar to the following: select * from T where price * (1 - discount) > 500 and the table T was a remote table, then it was possible the query would have returned the wrong result. This was due to fact that the Remote Data Access layer sometimes failed to include the parenthesis when generating queries to be executed on remote servers. This problem has now been fixed.

CR:611877

CR Number:   611877 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3923 17 Dec 2009 Fixed Description The Listener utility (dblsn) was failing to recognize the operating system when run on Windows 6.x systems, which may have resulted in crashes. This has been fixed. Note, the Listener utility now tracks the following new Windows 6.x versions: Windows Server 2008 Windows Vista Windows 7 Windows Server 2008R2 Future versions will be tracked as "Unrecognized Windows NT ?.?"