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

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

CR:455002

CR Number:   455002 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3474 26 Mar 2007 Fixed 10.0.0 2824 26 Mar 2007 Fixed Description Attempting to update a view that contained an outer join using a searched update, could have failed if there were NULL-supplied rows, even if the update statement only modified columns from the preserved table. For example, the following sequence could have incorrectly lead to the error CANNOT_UPDATE_NULL_ROW: create view ab as select apk, ax, bpk, bfk, bx from a left outer join b on bfk = apk; update ab set ax='Z' where apk=2 This has been fixed.

CR:455003

CR Number:   455003 Product Name:   UltraLite Product Component:   Analyser Java Classes Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3444 05 Feb 2007 Fixed 9.0.1 2199 05 Feb 2007 Fixed Description The UltraLite generator ulgen could, if there was an unreferenced column and that column was the referencing column of a foreign key, generate an UltraLite database containing that column. This has been corrected.

CR:455022

CR Number:   455022 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3369 05 Feb 2007 Fixed 10.0.0 2801 05 Feb 2007 Fixed Description The ULCommandBuilder class would have created an INSERT statement without values for the primary key columns, when the primary key columns were not DEFAULT AUTOINCREMENT. This has been fixed.

CR:455115

CR Number:   455115 Product Name:   MobiLink Product Component:   Sample Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3367 05 Feb 2007 Fixed 10.0.0 2800 05 Feb 2007 Fixed Description Running build.bat for the SIS_CarDealer sample application (Samples\MobiLink\SIS_CarDealer\build.bat) to generate files for Palm listeners, could have failed. The error "Wrong number of parameters to function 'ml_add_user'" would have been reported when populating the MobiLink SIS tracking tables. It is now fixed.

CR:455140

CR Number:   455140 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 3370 05 Feb 2007 Fixed 10.0.0 2801 05 Feb 2007 Fixed 9.0.2 3444 05 Feb 2007 Fixed Description Executing a query that involved a proxy table, and uses an invalid dotted reference that contained empty fields within the query, would likely have caused the server to crash. An example of an invalid dotted reference with empty fields is: select emp_profile..dependents..count(*) from emp_profile This problem has now been fixed so that attempts to use an invalid dotted reference of the above form will result in an "invalid field reference" error.

CR:455148

CR Number:   455148 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 20 Feb 2007 Fixed 9.0.2 3453 20 Feb 2007 Fixed Description Use of references to procedure in UPDATE statements could have caused the server to crash. The server will now generate an appropriate error message.

CR:455160

CR Number:   455160 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) 10.0.1 3371 06 Feb 2007 Fixed 10.0.0 2801 06 Feb 2007 Fixed Description The Interactive SQL utility could have failed with an internal error (NullPointerException) when saving result sets if the "Show multiple result sets" option was ON and the result sets contained a column wider than the truncation length. This has been fixed.

CR:455170

CR Number:   455170 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3473 20 Mar 2007 Fixed 10.0.0 2823 20 Mar 2007 Fixed Description If a Windows NT system was shutdown or rebooted while a database server was running as a service with desktop interaction enabled, the database server could have crashed during the shutdown. This problem has been fixed.

CR:455256

CR Number:   455256 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3372 06 Feb 2007 Fixed 10.0.0 2802 06 Feb 2007 Fixed Description Synchronizations using encryption may have occasionally taken too long. The primary symption of this problem was the presence of at least one two-minute delay in the middle of a synchronization. This has been fixed.

CR:455321

CR Number:   455321 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) 10.0.1 3370 06 Feb 2007 Fixed 10.0.0 2801 06 Feb 2007 Fixed Description The x86_64 Linux server may have crashed while processing a request. This would only have occurred when glibc-2.3.3 was installed on the system. A work-around in the server has been added to avoid this crash.

CR:455329

CR Number:   455329 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3373 06 Feb 2007 Fixed 10.0.0 2802 06 Feb 2007 Fixed 9.0.2 3445 06 Feb 2007 Fixed 9.0.1 2207 02 Apr 2007 Fixed Description The Interactive SQL utility could have displayed BINARY, LONG BINARY, VARCHAR or LONG VARBINARY values as empty if the "Show multiple result sets" option was on and the truncation length was set to zero. This has been fixed. Note, this problem only affected windowed operation, not console mode.

CR:455330

CR Number:   455330 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3474 26 Mar 2007 Fixed 10.0.0 2824 26 Mar 2007 Fixed 9.0.2 3471 26 Mar 2007 Fixed Description The Unix install could have hung after reporting the following error: "No valid values found for the -w flag". The installer makes a call to the OS to get the size of the current window, which is then used to format the display of the install text. If this call returns an error, the window size is set to a default of 80x24. If however, the call does not return an error but returned a window size of 0x0, the installer would have tried to use this to format the text, leading to problem. This has been fixed by using the default 80x24 size for this case as well.

CR:455342

CR Number:   455342 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) 10.0.1 3375 06 Feb 2007 Fixed 10.0.0 2803 12 Feb 2007 Fixed Description The system procedure sa_db_properties() would have failed to return the value for the database property ConnCount. This has been corrected.

CR:455350

CR Number:   455350 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) 10.0.1 3370 06 Feb 2007 Fixed 10.0.0 2802 06 Feb 2007 Fixed Description A .NET client receiving a SOAP response from a SQL Anywhere SOAP service would have failed to parse the response if the SOAP service was configured with FORMAT 'DNET', and one or more of the response columns was null. This has been fixed. A C# .NET client will now emit a System.DBNull object to represent a null column. XML supports hexBinary and base64Binary representations for BINARY data types. A SQL Anywhere DISH service will now expose all SOAP service elements of type BINARY as base64Binary XML types. This applies to all three SOAP service formats: CONCRETE, DNET and XML. Prior to this change, DNET formatted soap services exposed BINARY data as hexBinary.

CR:455526

CR Number:   455526 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) 10.0.1 3374 07 Feb 2007 Fixed 10.0.0 2802 07 Feb 2007 Fixed Description The server could have deadlocked during concurrent index scans and row updates. This was more likely to have occurred on multiprocessor systems, and with index scans that changed directions. This has now been fixed.

CR:455533

CR Number:   455533 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3464 12 Mar 2007 Fixed Description When connecting to an UltraLite database with a connection string that did not contain a password, the application (such as ULISQL) could have crashed. This has been fixed so that specifying no password is now treated as an empty string password. This fix resolves another potential problem: attempting to add a user with a null password. Calling the C++ method UltraLite_Connection::GrantConnectTo() with NULL as the second parameter could also have crashed the application. This has been resolved as well.

CR:455534

CR Number:   455534 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3374 08 Feb 2007 Fixed 10.0.0 2802 08 Feb 2007 Fixed Description The Validation utility dbvalid could have failed with syntax errors when validating databases if the database charset differed from the operating system charset, specifically when the database charset contained characters that could not be represented in the operating system charset. This has been fixed by having dbvalid connect using the database charset.

CR:455536

CR Number:   455536 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3380 13 Feb 2007 Fixed 10.0.0 2804 13 Feb 2007 Fixed Description An error that there was incorrect syntax near 'FULL' would have occurred when attempting to delete a Connection or Table script from a Sybase ASE consolidated database. The SQL that was used to determine this reference count contained a FULL OUTER JOIN, which isn't supported by ASE. The query has been rewritten.

CR:455542

CR Number:   455542 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) 10.0.1 3402 05 Mar 2007 Fixed 10.0.0 2817 06 Mar 2007 Fixed 9.0.2 3462 06 Mar 2007 Fixed Description If the server was started with the -z option and an application connected using either Open Client or jConnect, it was very likely that the server would have crashed if the application subsequently fetched a large float value. This problem has been fixed.

CR:455647

CR Number:   455647 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) 10.0.1 3375 08 Feb 2007 Fixed 10.0.0 2803 08 Feb 2007 Fixed Description Viewing any numeric property in the property sheet for a web services connector (e.g the HTTP proxy port) would always have displayed the socket timeout, rather than the intended property. This has been fixed.

CR:455649

CR Number:   455649 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3376 12 Feb 2007 Fixed 10.0.0 2803 12 Feb 2007 Fixed Description If the value of the PUBLIC timestamp_format option was changed to something other than the default, Sybase Central could have crashed when the Events or Maintenance Plans folder was selected in the tree. This has been fixed.

CR:455656

CR Number:   455656 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) 10.0.1 3375 12 Feb 2007 Fixed 10.0.0 2803 12 Feb 2007 Fixed Description If the "ianywhere.connector.outgoing.retry.max" property was set in a connector property sheet, it would not have been displayed the next time the property sheet was opened. This property was being included in the list of system properties, and as a result, the property was deliberately not listed on the "Properties" page. This has been corrected so that it is no longer treated as a system property, which allows it appear on the "Properties" page.

CR:455659

CR Number:   455659 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) 10.0.1 3374 08 Feb 2007 Fixed 10.0.0 2802 08 Feb 2007 Fixed 9.0.2 3446 08 Feb 2007 Fixed Description A server crash was possible if concurrent connections were calling and dropping a procedure. For the crash to have occurred, there must have been a specific chain of events. A procedure was called on one connection, a checkpoint occurred, another connection dropped the procedure, and the first connection rolled back. This has been fixed.

CR:455668

CR Number:   455668 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 20 Feb 2007 Fixed 10.0.0 2807 20 Feb 2007 Fixed 9.0.2 3452 20 Feb 2007 Fixed 8.0.3 5504 20 Feb 2007 Fixed Description It was possible for the database server to crash when attempting to run a corrupted database file. Assertion 201418 'Row (page:index) has an invalid offset' has now been added to detect this corruption.

CR:455695

CR Number:   455695 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) 10.0.1 3375 09 Feb 2007 Fixed 10.0.0 3375 09 Feb 2007 Fixed Description The values returned for the "Number" and "ReqTimeUnscheduled" columns of the sa_performance_diagnostics() stored procedure were not correct. This has been fixed.

CR:455704

CR Number:   455704 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) 10.0.1 3375 09 Feb 2007 Fixed 10.0.0 2803 09 Feb 2007 Fixed Description Changing the Server Administration Password from a server message store's property sheet, would have actually changed the Management Request Address. This has been fixed.

CR:455712

CR Number:   455712 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) 10.0.1 3376 13 Feb 2007 Fixed 10.0.0 2803 13 Feb 2007 Fixed Description Esape processing was not being performed on NCHAR string literals. For example, the literal N'\n' was interpreted as an NCHAR string of two characters, a backslash followed by the letter 'n'. Instead, it should be treated as a single new line character. Similarly, N'\\' was treated as two backslash characters instead of one. When unparsing statements such as views and stored procedures, NCHAR string literals were output as if escape processing had been performed. This could have lead to incorrect results in some cases. For example: create procedure TNchar() begin select '\', N'\' end The TNChar procedure would have incorrectly returned a string with two backslash characters instead of one. This has been fixed. Note that hexadecimal escape sequences are interpreted in the CHAR character set, not the NCHAR character set. Use the UNISTR() function for unicode escapes. NOTE: The interpretation of escape characters in NCHAR string literals has changed; if your database contains materialized views affected by this, the views should be refreshed.

CR:455776

CR Number:   455776 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 22 Feb 2007 Fixed 10.0.0 2808 22 Feb 2007 Fixed 9.0.2 3454 22 Feb 2007 Fixed Description When a cursor was opened on a query with a "Nested Loops Semijoin Algorithm" or a "Nested Loops Anti-Semijoin Algorithm" in the execution plan, the cursor could have been repositioned inappropriately on a FETCH RELATIVE 0. Instead of remaining on the current row, a different row or NOTFOUND could have been returned. This has been fixed.

CR:455814

CR Number:   455814 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) 10.0.1 3376 12 Feb 2007 Fixed 10.0.0 2803 12 Feb 2007 Fixed 9.0.2 3447 12 Feb 2007 Fixed Description If an application connected using the iAnywhere JDBC Driver, prepared a callable statement, set the value of a parameter, registered the same parameter as output, and executes the statement, the output value of the INOUT parameter would not always have been correct. In some cases, the output value of the parameter would have incorrectly been set to the input value of the same parameter (i.e. the value would have remained unchanged after the callable statement was executed). This problem has now been fixed.

CR:455922

CR Number:   455922 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Windows CE 2.11 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3454 21 Feb 2007 Fixed Description In some timing-sensitive circumstances the QAnywhere client could have returned incorrect results. Calling QAManagerBase.GetMessageTimeout may have returned NULL if the queue contained unread messages; and an incorrect queue depth value may have been returned by calls to QAManagerBase.GetQueueDepth. These problems have been fixed.

CR:455926

CR Number:   455926 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) 10.0.1 3485 13 Feb 2007 Fixed 9.0.2 3449 13 Feb 2007 Fixed Description An attempt to create a base table with the same name and owner as that of an existing local temporary table is permitted by the server. However, the newly created table could not have been accessed until the local temporary table with the same name and owner was dropped from the current scope. The server will now disallow the creation of a base table in this scenario.

CR:455972

CR Number:   455972 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3379 13 Feb 2007 Fixed 10.0.0 2804 13 Feb 2007 Fixed 9.0.2 3447 13 Feb 2007 Fixed Description A plus character ('+') within a STRING type parameter (eg. var char) to a SQL Anywhere web client configured as type HTTP:GET or HTTP:POST, was received as a space ' ' by an HTTP server. The SQL Anywhere web client was not url-encoding the plus character. This has been corrected.

CR:455973

CR Number:   455973 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3379 13 Feb 2007 Fixed 10.0.0 2804 13 Feb 2007 Fixed 9.0.2 3448 13 Feb 2007 Fixed Description A SQL Anywhere DISH service that was configured with a GROUP clause, but no FORMAT clause, could have caused the server to crash on startup. This problem affected Win64 and some Unix platforms, but did not occur on Win32 platforms. It has now been fixed.

CR:455974

CR Number:   455974 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) 10.0.1 3379 13 Feb 2007 Fixed 10.0.0 2804 13 Feb 2007 Fixed Description If the server had been busy for a while, and the cache had grown somewhat, attempting to creating a proxy table may have caused the server to hang. For this problem to have occurred, the remote database that the proxy table was being created to, had to be on the same server as the local database. This problem has been fixed.

CR:455977

CR Number:   455977 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 12 Feb 2007 Fixed 9.0.2 3439 12 Feb 2007 Fixed Description License information for the Network Server (dbsrv9.exe), Personal Server (dbeng9.exe), Runtime Server (rteng9.exe) and Mobilink server (dbmlsrv9.exe) are now contained in a separate .LIC file, rather than inside the executable file. The license file is stored in the same directory as the executable file. When dblic.exe is run, specify the name of the .LIC file instead of the .exe file that needs to be licensed. Note, when deploying any of these executables, the .LIC file will need to be deployed as well

CR:456070

CR Number:   456070 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 15 Feb 2007 Fixed Description If CreateDatabase was called to create an encrypted database, and an encryption key waspassed via the connection parameters but ULEnableStrongEncryption wasn't called, CreateDatabase would have created an unencrypted database without reporting any warnings or errors. This has been fixed so that CreateDatabase will now fail in this situation with SQLE_ENCRYPTION_NOT_ENABLED. When attempting to connect to an encrypted database and an encryption key was provided, but ULEnableStrongEncryption wasn't called, the runtime would have reported SQLE_BAD_ENCRYPTION_KEY, which could have been misleading. This has been corrected so that the runtime will now report SQLE_ENCRYPTION_NOT_ENABLED for this as well. Also, when attempting to connect to an unencrypted database and an encryption key is provided, but ULEnableStrongEncryption isn't called, the connection will still succeed, but the runtime will now report a warning SQLE_ENCRYPTION_NOT_ENABLED_WARNING. Note that these changes only apply to applications that use the C++ or embedded SQL interfaces and don't use the UltraLite engine. Applications that use the engine, or any of the components, did not have these problems since they always call ULEnableStrongEncryption internally.

CR:456116

CR Number:   456116 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) 10.0.1 3380 14 Feb 2007 Fixed 10.0.0 2805 14 Feb 2007 Fixed Description Attempting to establish a connection to an SA 10 database using jConnect may have failed with an UNRECOGNIZED charset error, even though the database charset was valid. This problem was most prevelent with a CP936 database, although it may have occurred with other database charsets as well. The problem has been fixed. Note that this problem does not affect non-TDS based connections.

CR:456202

CR Number:   456202 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3381 14 Feb 2007 Fixed Description Two problems with generated batch files for dbmlsync and ulsync have been fixed. The default dbmlsync command used in the automatically generated *_dbmlsync.bat file contains the "-qc" switch. This switch caused the window to automatically close upon completion of the synchronization, making it hard to see whether it was successful or not. This has been fixed so that it is no longer in the default command. It can be added if desired by adding "-qc" to the command line options in the Advanced Options for SQL Anywhere Remote Synchronization Client page of the Deploy Synchronization Model Wizard. The automatically generated *_ulsync.bat had a "set PARMS=" line (intended for users to edit if they wanted), which should have been "set PARAMS", that meant that the %PARAMS% environment variable was not used with the ulsync command. The typo has been corrected.

CR:456231

CR Number:   456231 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 22 Feb 2007 Fixed 10.0.0 2809 22 Feb 2007 Fixed 9.0.2 3455 22 Feb 2007 Fixed Description If a statement contained one or more large IN list predicates that were processed using the IN List algortihm, then the statement could have taken a long time to respond to a cancel request. In some cases, a communication error would have occurred when executing such statements. This has been fixed. For more information on the IN List algorithm, see the documentation: SQL Anywhere Server - SQL Usage Query Optimization and Execution Query execution algorithms Miscellaneous algorithms IN List Workaround Description  Use the -tl to avoid timeouts but why does cpu usage go to 100%. I can not reproduce this problem using shared memory but did when I used tcpip.

CR:456232

CR Number:   456232 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3388 16 Feb 2007 Fixed 10.0.0 2808 16 Feb 2007 Fixed 9.0.2 3454 16 Feb 2007 Fixed Description The Interactive SQL utility, or any of the Java administration tools (ie Sybase Central, DBConsole, and MobiLink Monitor) would not have started on machines running German Windows Vista, if installed to "C:\Programme" rather than "C:\Program Files". This problem has been fixed.

CR:456239

CR Number:   456239 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) 10.0.1 3381 15 Feb 2007 Fixed 10.0.0 2805 15 Feb 2007 Fixed Description A query that performs an index scan involving a partially specified key could have returned wrong results. The following are all necessary for a wrong result to be returned: 1) the index had to be over more than one column, 2) the index scan must not have specified a value for the last column 3) the hash for the key must be 243-248 bytes long 4) the key must be a prefix of some indexed value. This has been corrected.

CR:456302

CR Number:   456302 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 15 Feb 2007 Fixed 10.0.0 2806 15 Feb 2007 Fixed 9.0.2 3451 15 Feb 2007 Fixed 9.0.1 2201 19 Feb 2007 Fixed Description The server may have crashed if multiple connections ran the same stored procedure concurrently the first time after the database was started, or an event caused the procedure to be reloaded. For the crash to have occurred, the procedure must have contained a control statement (e.g. IF) with a condition that used a subselect referencing proxy tables. This has been fixed.

CR:456312

CR Number:   456312 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) 10.0.1 3470 02 Mar 2007 Fixed Description If a filename provided to a BACKUP, RESTORE, LOAD TABLE, UNLOAD TABLE, or UNLOAD statement was not a CHAR-based character string (CHAR, VARCHAR, LONG VARCHAR), then the filename could have been incorrectly translated to an operating system file name. An error is now given if a filename is provided to one of the above statements and the filename is not a CHAR-based string. This can happen either if the N'' string literal prefix is used to denote an NCHAR string or if a variable is used and the variable is not CHAR-based.

CR:456317

CR Number:   456317 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3314 15 Feb 2007 Fixed 10.0.0 2769 15 Feb 2007 Fixed 9.0.2 3420 15 Feb 2007 Fixed Description When running in a Terminal Services (aka Remote Desktop or Fast User Switching) session, clients were not be able to use the shared memory communications port reliably. For example, database servers started as a Windows service would only be visible to the primary local login session ("session 0"), and they would be invisible to all other Terminal Services sessions. The behaviour has now been corrected and improved as follows: 1. A database server started in session 0 (ie as a Windows service or on the desktop of the primary login session) will be visible via shared memory to all sessions. 2. A database server will not start if there is already a server running by the same name in session 0 or in the current session. Note that the server _will_ start if there is a database server running with the same name in another session other than session 0. 3. When connecting via shared memory, clients will look for a server by the specified name in the current session first and then in session 0. Note that starting a database server on the desktop of session 0 can prevent a server with the same name from starting as a service; however, this situation is rare because services are normally started when the system starts.

CR:456324

CR Number:   456324 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3451 20 Feb 2007 Fixed Description In UltraLite, the dateformat() function was not properly using mixed case when specified by the format string. For example: Select dateformat( 2007-02-15, DDDdddddd, Mmmmmmmm ) from dummy This function would have incorrectly returned thursday, february instead of Thursday, February. This has been corrected.

CR:456348

CR Number:   456348 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) 10.0.1 3382 15 Feb 2007 Fixed 10.0.0 2806 15 Feb 2007 Fixed Description When the server shutdown on Unix platforms, it may have recorded in the server console that the user requested the shutdown by pressing 'Q' when this was not the case. The correct reason for the shutdown will now be displayed.

CR:456366

CR Number:   456366 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) 10.0.1 3382 19 Feb 2007 Fixed 10.0.0 2806 19 Feb 2007 Fixed Description For a synchronization model that used timestamp downloads, logical deletes, and a non-default name for the timestamp column, a "column not found" error would have been returned when the download_delete_cursor was executed by the MobiLink server. This has been fixed.

CR:456445

CR Number:   456445 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3439 16 Feb 2007 Fixed Description It is not possible to use the Input Method Editor (IME) to enter passwords in the Interactive SQL utility, or any of the Java administration tools, due to a bug in the Java Runtime Environment.

CR:456446

CR Number:   456446 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) 10.0.1 3470 20 Feb 2007 Fixed 10.0.0 2806 20 Feb 2007 Fixed Description The MobiLink server could have hung when run on Unix systems. This has been fixed.

CR:456468

CR Number:   456468 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) 10.0.1 3404 20 Feb 2007 Fixed 10.0.0 2818 08 Mar 2007 Fixed Description When unloading data from a database that is currently connected, if the wizard was terminated after the filename was specified, the new database would have failed to connect with the error: You are already connected to this database. This has been fixed.

CR:456473

CR Number:   456473 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) 9.0.2 3451 19 Feb 2007 Fixed Description When starting a database server on a file for which the server had no write permissions, the server would have reported "Unable to start database server. Unknown error (-29958)". A more appropriate error message is now displayed. In the case of having no write permissions, the server will now display "Unable to start database server. Permission denied"

CR:456484

CR Number:   456484 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) 10.0.0 2806 20 Feb 2007 Fixed Description The MobiLink server FIPS option did not work when HTTPS was used. Specifically, the following would not have loaded a FIPS-compliant encryption DLL/shared object, instead a non-compliant encryption DLL/shared object was loaded: mlsrv10 ... -x https(...;fips=y) Note that this is the full extent of the bug. The following will load the proper DLL/shared object: mlsrv10 ... -x https( ...) -fips mlsrv10 ... -x tls(...;fips=y) mlsrv10 ... -x tls(...) -fips Those requiring FIPS compliance for encryption are urged to always use the -fips option of mlsrv10 and/or on the server. They are also urged to remove the DLLs/shared objects that are not FIPS-compliant. Customers doing the latter would have seen the MobiLink server issue an error about being unable to load mlrsa_tls10.

CR:456492

CR Number:   456492 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3391 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed Description Updating a clustered index on a table that from which rows had been deleted, could have resulted in a the server crashing, or a failed assertion. While there is a small chance that database corruption could result, this is not likely. This has been fixed.

CR:456549

CR Number:   456549 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) 10.0.1 3386 20 Feb 2007 Fixed 10.0.0 2807 20 Feb 2007 Fixed Description A Client Rule file (.QAR file) could have been inadvertently truncated, losing the transmission and deletion rules, if it was viewed in a dialog, but not actually modified. This has been fixed.

CR:456558

CR Number:   456558 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) 10.0.1 3387 20 Feb 2007 Fixed 10.0.0 2807 20 Feb 2007 Fixed Description The MobiLink server may have mistakenly detected conflict updates when synchronizing tables containing columns with a TIME data type; if there was an upload_fetch or upload_fetch_column_conflict script, and at least one of the upload_new_row_insert, upload_old_row_insert, and resolve_conflict scripts. This problem is now fixed.

CR:456561

CR Number:   456561 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) 10.0.1 3391 20 Feb 2007 Fixed Description When a synchronization model was deployed that created shadow tables, the shadow tables would have been created with the connected user as the owner, and the generated triggers would have referred to the shadow tables without specifying the owners. This could have caused the triggers to fail if a base table and shadow table had different owners, and the base table owner could not access the shadow table owner's tables without specifying the owner (eg. if the owners were not in the same group). This has been fixed. Now a shadow table is created with the same owner as the base table, and the triggers and download scripts fully qualify the shadow table name.

CR:456562

CR Number:   456562 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) 10.0.1 3470 20 Feb 2007 Fixed Description When selecting publications in the Extract Wizard, if one publication was selected, the appropriate tables were displayed. However if more than one publication was selected, no tables were displayed. This has been fixed.

CR:456564

CR Number:   456564 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3451 19 Feb 2007 Fixed Description On Windows Vista, services are not allowed to interact with the desktop. Even if "allow interaction with desktop" is enabled, the server will not attempt to do so.

CR:456567

CR Number:   456567 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   2.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3389 22 Feb 2007 Fixed 10.0.0 2806 22 Feb 2007 Fixed Description The Infomaker, PhysicalModel or DataWindow.NET installs could either have failed to launch, or have been launched incorrectly by the main Tools Installer when run from the CD. This has been fixed in SA 10.0.1 by using the fully-qualified paths of the install launchers. A work-around for SA 10.0.0 is to copy the contents of the CD to a hard drive and run the install from there.

CR:456580

CR Number:   456580 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3383 20 Feb 2007 Fixed 9.0.2 3451 20 Feb 2007 Fixed Description The sample programs provided have been changed so that they now correctly handle SQL Anywhere installation pathnames that contain spaces. Previously, the sample programs used the Windows "short" filename (8.3) format, which avoided spaces.

CR:456585

CR Number:   456585 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) 10.0.1 3388 20 Feb 2007 Fixed 10.0.0 2808 20 Feb 2007 Fixed Description Adding a row to a table in the "Results" panel (or on the "Data" tab of a table object in Sybase Central) and then tabbing between the new column values, could have inadvertently changed a "(DEFAULT)" value to "(NULL)". This problem will occur if the table contained a nullable column, followed by one which was not nullable and which also has a default value. This has been fixed.

CR:456608

CR Number:   456608 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3383 20 Feb 2007 Fixed 9.0.2 3451 20 Feb 2007 Fixed Description On Windows Vista, to use AWE (Address Windowing Extension) cache with the database server, the server must be run as an administrator. If not run as an administrator, the server will disable AWE and issue a warning message.

CR:456610

CR Number:   456610 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) 9.0.2 3460 02 Mar 2007 Fixed Description Executing a TRUNCATE TABLE statement on a very large global temporary or permanent table may have blocked other database requests (including connect requests) until its completion. This has been fixed.

CR:456644

CR Number:   456644 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 21 Feb 2007 Fixed 10.0.0 2808 21 Feb 2007 Fixed Description Calling UltraLite_ResultSet.Set did not set NOT NULL when a value was supplied. This could have also have affected the Set methods in various components. This has been fixed.

CR:456675

CR Number:   456675 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3389 21 Feb 2007 Fixed 10.0.0 2808 21 Feb 2007 Fixed 9.0.2 3454 21 Feb 2007 Fixed Description If a result set row could not have been fetched, the full reason for the failure might not have been reported. Typically, the message "Cursor not in a valid state" was displayed without the underlying error indication. Now, all of the available error information is displayed.

CR:456682

CR Number:   456682 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3389 21 Feb 2007 Fixed 10.0.0 2808 21 Feb 2007 Fixed Description The VARBIT and LONG VARBIT data types were missing in the SADbType enum. This has been corrected, SADbType.VarBit was added for the VARBIT data type, and SADbType.LongVarbit was added for the LONG VARBIT data type.

CR:456698

CR Number:   456698 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 21 Feb 2007 Fixed 10.0.0 2808 21 Feb 2007 Fixed Description The special value NULL, used by itself in certain SELECT expressions, could have given incorrect results. For example, the query "select NULL union select NULL" did not give the correct results. This has been corrected.

CR:456703

CR Number:   456703 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) 10.0.1 3389 21 Feb 2007 Fixed 10.0.0 2808 21 Feb 2007 Fixed Description The event source for a service event log entry is incorrectly set to the service name. This results in a message similar to the following: "The description for Event ID ( 1 ) in Source ( SQLANYm_xxx ) cannot be found. ..." This problem has been fixed.

CR:456715

CR Number:   456715 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) 10.0.1 3389 22 Feb 2007 Fixed Description In the "SQL Statements" field, clicking on a statement keyword (e.g. "SELECT", or "INSERT") should open a context menu which contains an item "Help for xxx" (where "xxx" is the keyword). Help was available only for a very select number of statements. This has been corrected so that help is now available for all statements.

CR:456720

CR Number:   456720 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) 10.0.1 3389 21 Feb 2007 Fixed 10.0.0 2808 21 Feb 2007 Fixed Description A race condition existed when the server checked for expired Http connections, which in a rare case could have caused the server to crash. This has been fixed.

CR:456728

CR Number:   456728 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3387 22 Feb 2007 Fixed 10.0.0 2807 22 Feb 2007 Fixed Description The options 'Listening', 'Enable Actions' and 'Prompt Before Actions' were always enabled for the Palm Treo 600 and 650 Listeners, and could not be disabled. This has been fixed so that these options are now configurable.

CR:456732

CR Number:   456732 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) 10.0.1 3388 22 Feb 2007 Fixed 10.0.0 2808 22 Feb 2007 Fixed Description The server would have failed to start a database file which resided on a file system not supporting Direct IO. This is of particular importance to users wishing to run a SQL Anywhere database on a tmpfs filesystem (RAM drive), as tmpfs does not support the use of Direct IO. This only affected Linux and AIX systems. In order to support tmpfs filesystems, the server now automatically disables the use of Direct IO when the database file resides on a file system not supporting it. In such cases an informational message will be sent to the server console and/or log file indicating that DirectIO has been disabled for that file.

CR:456757

CR Number:   456757 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3389 22 Feb 2007 Fixed 10.0.0 2808 22 Feb 2007 Fixed Description When passing an uninitialized or NULL parameter,a SQL Anywhere SOAP client procedure (or function) would have serialized the parameter as an empty XML element. This has been fixed so that a NULL parameter is no longer serialized within the request SOAP envelope.

CR:456783

CR Number:   456783 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 22 Feb 2007 Fixed 10.0.0 2808 22 Feb 2007 Fixed Description When the DEFAULT clause specified a character string for a column in a CREATE or ALTER table statement, and the length of that character string exceeds 126 characters, the characters string was truncated to 125 characters, instead of 126 characters. This has been corrected.

CR:456826

CR Number:   456826 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) 10.0.1 3390 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed Description Attempting to modify a column immediately after viewing a table's data would have caused the error message "A schema upgrade is not currently allowed." The plug-in was neglecting to close the result set which provided the data for the "Data" tab when it was deselected. This has been fixed.

CR:456829

CR Number:   456829 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3394 26 Feb 2007 Fixed 10.0.0 2811 26 Feb 2007 Fixed 9.0.2 3456 26 Feb 2007 Fixed Description When using Server-Initiated Synchronization, the server could have failed with a java.lang.OutOfMemoryError exception due to Java heap memory exhaustion. This would have occurred after many notifications. This is now fixed.

CR:456835

CR Number:   456835 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) 10.0.1 3390 22 Feb 2007 Fixed 10.0.0 2809 22 Feb 2007 Fixed Description If an Agent Rule file had a custom schedule, it was not parsed completely by the QAnywhere plug-in and would have been displayed incorrectly. This has been fixed.

CR:456856

CR Number:   456856 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) 10.0.1 3390 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed Description If a rule had a custom schedule, and the schedule contained start and end times, the rule was misread by the QAnywhere pplug-in and displayed with an end time equal to the start time. This has been fixed.

CR:456867

CR Number:   456867 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) 10.0.1 3390 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed Description The QAnywhere Plug-in could have reported an internal error when attempting to delete a message from a client message store after the database connection had been lost. This has been fixed.

CR:456868

CR Number:   456868 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3390 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed 9.0.2 3455 23 Feb 2007 Fixed Description When Mobilink was synchronizing data to a multi-byte Microsoft SQL Server database, it was possible for the ODBC Driver to fail and return an "Unspecified Error". The connection to the Microsoft SQL Server would have been dropped, and the synchronization would have failed. The problem was in the Microsoft SQL Server ODBC driver, and a workaround has been implemented in the Mobilink Server to avoid it.

CR:456873

CR Number:   456873 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3390 26 Feb 2007 Fixed 10.0.0 2809 26 Feb 2007 Fixed Description Change made to the Interactive SQL utility for Engineering Case 443671 to improve the performance of displaying blob data from SA database, caused an error from the ODBC Driver Manager when displaying blob data from the UltraLite databases. The problem was seen when displaying the contents of a non-empty blob column. No data is returned, and DBISQL would have displayed the following Driver Manager error (SQLSTATE HY009): [Microsoft][ODBC Driver Manager] Invalid argument value This has now been fixed.

CR:456875

CR Number:   456875 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3390 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed 9.0.2 3455 23 Feb 2007 Fixed Description The SQL Anywhere Explorer was not reading the correct Windows registry entry for the language setting, as created by Language Selection utility (dblang). This has been fixed.

CR:456885

CR Number:   456885 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3390 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed 9.0.2 3455 23 Feb 2007 Fixed Description The Add Connection dialog did not close when the ESC key was pressed. This has been fixed.

CR:460670

CR Number:   460670 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3391 26 Feb 2007 Fixed 10.0.0 2809 26 Feb 2007 Fixed Description Visual Studio 2005 checks the property SADataConnectionProperties.IsComplete to determine if the OK button should be enabled or disabled. The provider was not correctly setting this property in some cases. It has now been fixed by setting the property SADataConnectionProperties.IsComplete to TRUE, if both user id and password are entered by the user.

CR:460700

CR Number:   460700 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) 10.0.1 3391 23 Feb 2007 Fixed 10.0.0 2809 23 Feb 2007 Fixed Description Queries that scanned backwards through an index could have produced too few rows in the result set. This would only have happened if the index contained a long value. Note that prefetching can be a cause of backwards scans. This has now been fixed.

CR:460712

CR Number:   460712 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) 10.0.1 3391 26 Feb 2007 Fixed 10.0.0 2810 26 Feb 2007 Fixed Description Using the server command line option -dt "set directory for temporary files" on a Unix systems did not actually set the directory. Furthermore, under most common scenarios, the server would have failed to start if this switch was specified. This has been fixed so that the -dt option now correctly sets the directory where the server puts its temporary files.

CR:460718

CR Number:   460718 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 3456 27 Feb 2007 Fixed Description The Listener used by MobiLink Server-Intitated Synchronization uses a tracking database to store information. A new command line option -z has been added to the Listener utility (dblsn) to allow specifying a non-default location for the temporary tracking database. The -z option takes the location of the tracking database as a parameter. For example, dblsn -z "c:\program files\tracker\"...

CR:460745

CR Number:   460745 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) 10.0.1 3470 26 Feb 2007 Fixed Description As of the release of SQL Anywhere 10.0, synchronization concurrency was reduced. In particular, other threads and processes were blocked from entering the UltraLite runtime during upload, and while waiting for MobiLink to create the download. This has been fixed.

CR:460762

CR Number:   460762 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3391 26 Feb 2007 Fixed 10.0.0 2810 26 Feb 2007 Fixed Description SOAP parameters passed as empty XML elements, eg. <an_empty></an_empty> were incorrectly being treated internally as NULL parameters within a SQL Anywhere SOAP service. This has been fixed. A null parameter may be expressed by not including the given parameter element within the SOAP request, or by providing it with a nil="true" attribute, eg <a_null xsi:nil="true" />. SQL Anywhere SOAP services with FORMAT 'XML' or FORMAT 'CONCRETE' no longer return NULL column values as empty XML elements. Empty XML elements are only returned for VARCHAR data types in order to preserve the empty string symantics. This change, along with Engineering case 455350, synchronizes the behaviour for all SOAP service formats.

CR:460829

CR Number:   460829 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) 10.0.1 3394 26 Feb 2007 Fixed 10.0.0 2811 26 Feb 2007 Fixed Description If a column is declared as "default timestamp" or "default utc timestamp", then the timestamp values generated by the server should be unique for each row inserted or updated. This was not the case; the same value could have been shared for multiple rows affected by an INSERT or UPDATE statement. This has been fixed.

CR:460830

CR Number:   460830 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) 10.0.1 3394 26 Feb 2007 Fixed 10.0.0 2811 26 Feb 2007 Fixed Description Comparisons using UPPER(), LOWER(), UCASE(), or LCASE() could have given incorrect results, equivalent to not using the function at all. For example, consider a database with the UTF8BIN NCHAR collation and 125LATIN1 CHAR collation: create table TChar( x int primary key, c char(1), n nchar(1) ); insert into TChar values( 1, nchar(199), nchar(199) ); insert into TChar values( 2, nchar(231), nchar(231) ); commit The following query should return one row: select T1.x, T2.x from TChar T1, TChar T2 where upper( T1.c ) = T2.n and T1.x <> T2.x but would have incorrectly returned no rows; this was equivalent to removing the upper() function. This has been fixed, altough in cases where it is safe to do so, the functions UPPER(), LOWER(), UCASE() and LCASE() are still removed.

CR:460861

CR Number:   460861 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) 10.0.1 3395 27 Feb 2007 Fixed 10.0.0 2812 27 Feb 2007 Fixed Description Servers involved in a high-availability system were not able to use TLS encryption on connections to each other. This has been fixed. Note that client connections to a high-availability server were not a problem, they are able use TLS.

CR:460873

CR Number:   460873 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) 10.0.1 3470 27 Feb 2007 Fixed 10.0.0 2811 27 Feb 2007 Fixed Description The server could have crashed when stopping a database. This problem would only have happened when a database was shutdown immediately after a transaction had ended, and then only rarely. This has been fixed.

CR:460895

CR Number:   460895 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) 10.0.1 3394 27 Feb 2007 Fixed 10.0.0 2811 27 Feb 2007 Fixed Description Deploying a model, or checking MobiLink System Setup, with a case sensitive Microsoft SQL Server database, could have failed with the following error: A SQL error occured when trying to check for Mobilink system setup in the consolidated database. [Microsoft][SQL Native Client][SQL Server]The multi-part identifier "O.ID" could not be found This has been fixed.

CR:460905

CR Number:   460905 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3395 27 Feb 2007 Fixed 10.0.0 2811 27 Feb 2007 Fixed Description When creating or modifying an event schedule, the component used to specify the event recurrence on specific days of the week would always have used Sunday as the first day of the week. This has been corrected so that the current locale is checked to determine which day should be used for the first day of the week. For example, in French, German, Chinese and Japanese locales, the first day of the week is Monday.

CR:460942

CR Number:   460942 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3470 27 Feb 2007 Fixed 10.0.0 2812 27 Feb 2007 Fixed Description Table names exceeding 128 characters were not handled correctly. In particular, they were being improperly trunctated, allowing duplicate tables with the same apparent name to be created. Such table names are now diagnosed as syntax errors.

CR:461027

CR Number:   461027 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) 10.0.1 3395 27 Feb 2007 Fixed 10.0.0 2812 27 Feb 2007 Fixed 9.0.2 3457 27 Feb 2007 Fixed Description If an application, connected using the iAnywhere JDBC driver, started a request and then attempted to close the connection on a separate thread, it was very likely that the application would have crashed. This problem was most easily reproduced in Sybase Central when a profiling session was cancelled, and an attempts was made to go back to design mode. The problem has now been fixed.

CR:461036

CR Number:   461036 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) 9.0.2 3457 27 Feb 2007 Fixed Description When referencing a proxy table to a remote database with a multi-byte character set, table or column names that had multi-byte characters could have been passed to the remote server mangled. For identifiers in the multi-byte Character set, the server may have incorrectly escaped certain characters and/or changed the case. This problem has been fixed.

CR:461052

CR Number:   461052 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) 10.0.1 3472 21 Mar 2007 Fixed 10.0.0 2823 21 Mar 2007 Fixed Description When comparing a VARBIT or LONG VARBIT value to a value of another domain, both arguments were converted to NUMERIC and then compared. For example: select row_num, cast( cast( row_num as tinyint ) as varbit ) vb from sa_rowgenerator(0,10) where vb >= '00000100' The above query would have returned the empty set; vb would have been converted to NUMERIC and compared to CAST('00000100' AS NUMERIC)==100. This has been fixed. Now, both arguments are converted to LONG VARBIT and compared as bit strings. The above query will now return the following: row_num,vb 4,'00000100' 5,'00000101' 6,'00000110' 7,'00000111' 8,'00001000' 9,'00001001' 10,'00001010' Further, when bit string values were displayed in plan text, they were displayed as a hexadecimal string that did not have a clear relationship to the bitstring value. For example, the bit string CAST( '00000100' AS VARBIT ) was previously displayed as 0x080000000100000004000000 in the plan text. Now, bit string values are displayed in the plan text as a string literal prefixed with B (for example, B'00001010'). The B prefix distinguishes bit strings in the plan text from character strings.

CR:461054

CR Number:   461054 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3457 28 Feb 2007 Fixed 9.0.1 2202 28 Feb 2007 Fixed Description The ASCII function would have returned an incorrect value when passed a zero-length string as an argument. This has been corrected.