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

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

CR:486864

CR Number:   486864 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 3612 07 Dec 2007 Fixed Description A server running with the -b command line option (run in bulk operations mode) would have accepted more than one connection. This has been corrected.

CR:486877

CR Number:   486877 Product Name:   MobiLink Product Component:   Charset Conversion (UNILIB) Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3616 13 Dec 2007 Fixed Description When generating the download stream, in very rare circumstances, it was possible for MobiLink to have incorrectly translated a string if the remote database used a multi-byte character set. It was likely that the ending byte(s) of one string would end up at the start of the next string in the same row. This problem has now been fixed.

CR:486889

CR Number:   486889 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 1301 07 Dec 2007 Fixed Description In rare cases, an error encountered while executing a trigger could have resulted in a server crash. This has been fixed.

CR:486896

CR Number:   486896 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3613 11 Dec 2007 Fixed Description The Deployment wizard did not deploy the utility dbspawn.exe when either the Personal or Network servers were selected. This has been corrected by adding dbspawn.exe to the "server core" list of files to be deployed.

CR:487001

CR Number:   487001 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 3613 07 Dec 2007 Fixed 3593 07 Dec 2007 Fixed Description The server could have hung in very rare timing dependent cases if it was using the -z or -zr command line options for diagnostic messages and request level logging. This has been fixed.

CR:487008

CR Number:   487008 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3614 11 Dec 2007 Fixed 9.0.2 3593 11 Dec 2007 Fixed Description The changes made for Engineering case 484553 incorrectly had the PWD value replaced with all asterisks "*" in the OutConnectionString parameter of the SQLDriverConnect() function. This has been corrected. Workaround Description  Currently if the user must have this functionality they must rollback to some earlier build, but this will effectively bar Optionally allowing/forcing the connection to always prompt is somewhat functional but can be quite a lot of user interface overhead and is clear a change of functionality in an existing product.

CR:487014

CR Number:   487014 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1144 07 Mar 2008 Fixed 10.0.1 3654 10 Mar 2008 Fixed Description Diagnostic tracing with Scope: origin Origin: external Tracing type: statements_with_variables Condition: none would not have recorded any statements with an external origin. An incorrect string comparison was being used to determine whether a statement needed to be logged. This has been fixed.

CR:487141

CR Number:   487141 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) 9.0.2 3594 11 Dec 2007 Fixed Description If an HTTP connection was refused because of licensing restrictions, in rare cases, the server could have crashed. This has been fixed.

CR:487142

CR Number:   487142 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 3617 17 Dec 2007 Fixed 9.0.2 3596 17 Dec 2007 Fixed Description In some specific situations, an UPDATE statement could have failed to complete. It would continue to execute until cancelled. This has been fixed.

CR:487164

CR Number:   487164 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3668 17 Apr 2008 Fixed Description The Index Consultant may have caused the server to crash when a complex query was analyzed. For example, a query with a subselect in the select list. This has been fixed.

CR:487166

CR Number:   487166 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1142 04 Mar 2008 Fixed 10.0.1 3652 05 Mar 2008 Fixed Description If a deadlock occurred in a database that had tracing with high levels of detail attached, and the tracing data was saved and viewed from Profiling mode in Sybase Central, the primary keys for rows that had caused the deadlock would not have been reported in the Deadlocks tab. This has been fixed. This behaviour is only considered invalid if tracing data is saved in the database that is being profiled. If tracing data is saved in an external tracing database, primary key values for rows in the original database cannot be reported.

CR:487169

CR Number:   487169 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3615 11 Dec 2007 Fixed 9.0.2 3594 11 Dec 2007 Fixed Description The Listener may have displayed an error dialog shortly after startup when handling notifications. This problem was timing sensitive, subsequent errors would have gone into the log file and to the console only. This has been fixed so that errors in handling notification will no longer cause an error dialog to be displayed. A workaround is to add the -oq switch to the dblsn command line.

CR:487178

CR Number:   487178 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3615 11 Dec 2007 Fixed Description The server will no longer fail assertion 102300 - "File associated with given page id is invalid or not open", when executing DROP DBSPACE if the dbspace had beed deleted.

CR:487247

CR Number:   487247 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 3615 11 Dec 2007 Fixed Description The server keeps track of dependencies of views on other views and tables. In databases with an extremely large number of objects, the dependency information could have become inaccurate. In order for the problem to have manifest itself, some of the dependent or referenced objects must have had object ids that were greater than 4G (2^32). This has been fixed. For existing databases, problematic views must be recompiled with an updated version of the software. If the actual number of current objects is much smaller than 4G, then the problem can be resolved by unloading and reloading the database without the need for a server software update. The reload should result in a compacting of the used object id space.

CR:487269

CR Number:   487269 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) 10.0.1 3615 12 Dec 2007 Fixed Description The CE 5.0 client libraries, qaagent, dbmlsync and dblsn could crash when shutting down. This has been fixed.

CR:487335

CR Number:   487335 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 3616 12 Dec 2007 Fixed 9.0.2 3595 12 Dec 2007 Fixed Description It was possible for an HTTP request to an SA DISH service to hang the server while consecutively altering services. This has been fixed.

CR:487339

CR Number:   487339 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 3617 17 Dec 2007 Fixed Description If an older client (version 8.0 or 9.0) synchronized against the MobiLink server in a way that a second synchronization was attempted before the first finished (the client was terminated before the server was finished), the server would have allowed the second synchronization to proceed. This has been corrected so that subsequent synchronizations will fail until the first has competed. This problem does not apply to version 10.0 clients, as their new protocol detects and handles this situation in a different manner.

CR:487364

CR Number:   487364 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3616 13 Dec 2007 Fixed Description When converting a string from one character set to another, it was possible for the translated string to have been truncated in very rare situations. For the problem to have occurred, a conversion using ICU was required, which typically meant that a multibyte charset other than UTF-8 was involved, which is similar to Engineering case 484960. This problem has been fixed. Note, this problem does not affect the database server, but does affect other components in SQL Anywhere.

CR:487411

CR Number:   487411 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3617 30 Jan 2008 Fixed Description A keyset cursor is used when there is a possibility that a row could otherwise be updated multiple times. For example, a keyset cursor is needed if there are triggers, or if an UPDATE modifies columns in an index used by the UPDATE's plan. In some situations, an UPDATE statement could have used a keyset cursor in cases where it was not necessary, thus leading to slower performance. This has been fixed.

CR:487443

CR Number:   487443 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3618 17 Dec 2007 Fixed Description It was possible for the database administration utilities, or other applications which made use of the DBTools interface, to have crashed when attempting to access a file that was in use. This has been fixed. Workaround Description  MOVE everything to a Windows box!

CR:487496

CR Number:   487496 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 3617 17 Dec 2007 Fixed Description The selectivity estimates used by the optimizer could have had reduced quality in some cases. In particular, if a database was used on two platforms with different endianness, the selectivity estimates could have been wrong immediately after starting on the other platform. The selectivity estimates would have gradually improved with use on the new platform, or until a CREATE STATISTICS command was used to recreate the estimates. This has been fixed.

CR:487505

CR Number:   487505 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 3617 14 Dec 2007 Fixed 3596 14 Dec 2007 Fixed Description On Windows CE, starting a second server while one is already running should display the existing server, unless the existing server is in quiet mode (started with the command line option -qi or -qw). After pressing the Hide button on a server, starting a second server did not display the existing server. This has been fixed so that the first server is now displayed when a second server is started, even if the Hide button is pressed.

CR:487507

CR Number:   487507 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3617 17 Dec 2007 Fixed 9.0.2 3596 17 Dec 2007 Fixed Description If a 32-bit server was used on a system that had more than 4GB of memory available, then dynamic cache sizing could have selected cache sizes that were inappropriately small. Inappropriately small cache selected in this way would have affected query performance such that they could be very slow, worse even then if that cache size had been set at startup time. This problem has been fixed. Note, this problem can be avoided by using the -ca 0 engine switch to disable dynamic cache sizing.

CR:487516

CR Number:   487516 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3618 18 Dec 2007 Fixed Description If a database had been initialized with the -b option (blank padding of strings for comparisons), then the log scanning would not have read the delete_old_logs database option properly. The log scanning code would always have used the default value of 'Off', regardless of the value set in the database. This problem has now been fixed.

CR:487520

CR Number:   487520 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3617 17 Dec 2007 Fixed Description When the server was run on Windows CE devices with the -qw or -qi command line options, a menu bar containing the menu "Menu" would have been displayed, but no server window. This has been fixed so that no part of the server is now visible if the -qw or -qi options are used.

CR:487581

CR Number:   487581 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3618 17 Dec 2007 Fixed 9.0.2 3597 17 Dec 2007 Fixed Description Initializing a scheduled transmission rule containing an "EVERY" clause and a "START DATE" clause set to a date that had already passed, in the QAnywhere server or in the QAnywhere Ultralight Agent, would have caused the rule to be immediately and repeatedly executed many times on startup. This has been fixed.

CR:487673

CR Number:   487673 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) 11.0.0 1247 18 Dec 2007 Fixed 10.0.1 3619 28 May 2008 Fixed Description The changes for Engineering case 471948 introduced a problem such that when the server was very close to the connection limit, either the limit set by licensing or the hard-coded limit in the Personal Server, new HTTP connections may have been rejected incorrectly. This has been fixed.

CR:487686

CR Number:   487686 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3597 18 Dec 2007 Fixed Description If the MobiLink client dbmlsync did not receive an ack/nack from the MobiLink server after sending an upload, it has no way of knowing whether the upload was successfully applied. The best way to resolve this situation is to perform an 'extra exchange' with the server before the next synchronization to request the status of the upload. Previously, this extra exchange was performed on the first synchronization after dbmlsync started up. This has been changed so that it will now perform the exchange any time there has been an un-acknowledged upload.

CR:487687

CR Number:   487687 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3619 18 Dec 2007 Fixed 9.0.2 3597 18 Dec 2007 Fixed Description If the MobiLink client dbmlsync failed during the brief time between when an upload was completed and when state information in the database was updated, then the server would not have been queried at the start of the next sync to determine if the upload was successfully applied to the consolidated database. This problem would have occurred extremely rarely, and in most cases would have been harmless. The result was simply that the next synchronization took a little longer because an upload was built and uploaded, then rejected by the server, and a new correct upload was built and uploaded. However if the failure occurred on a subscription's first synchronization, it could have resulted in operations being uploaded to the server twice, which would usually have caused the synchronization to fail with server side errors. This has been fixed so that the syssync table is updated prior to the end of the upload. As a result an extra exchange may occur when the end of the upload was not sent, but the client should never fail to do an extra exchange when it is required.

CR:487688

CR Number:   487688 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3597 18 Dec 2007 Fixed Description It was possible for the MobiLink client dbmlsync to upload operations for a subscription that did not belong to that subscription, when all of the following were true: 1) A subscription, S1, was created to some publication P1, and a second subscription, S2, was also created for P1 (either by dropping S1 and recreating it or by creating a new subscription to P1 with a different MobiLink User.) 2) During the first synchronization of S2, dbmlsync successfully sent an upload but did not receive an ack/nack from the MobiLink server. 3) The upload was not successfully applied to the consolidated database by the server. When all these conditions were TRUE it was possible for operations that occurred before subscription S2 was created to be uploaded when subscription S2 was synchronized. This behavior has been corrected. Now, only operations that occurred after subscription S2 was created will now be uploaded when subscription S2 is synchronized.

CR:487689

CR Number:   487689 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3619 18 Dec 2007 Fixed 9.0.2 3597 18 Dec 2007 Fixed Description If the MobiLink client dbmlsync did not receive an ack/nack from the server after sending an upload it has no way of knowing whether the upload was successfully applied to the server. The best way to resolve this situation is to perform an 'extra exchange' with the server before the next synchronization to request the status of the upload, but dbmlsync did not perform this extra exchange after an unacknowledged upload that occurred during the first synchronization of a subscription. This would not have resulted in any data loss, but might have increased the time required for the next synchronization as it might cause two uploads to be built and sent to the MobiLink server. This has been corrected so that an extra exchange is now performed in this case to eliminate the possibility of sending two uploads.

CR:487690

CR Number:   487690 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3619 19 Dec 2007 Fixed 9.0.2 3597 19 Dec 2007 Fixed Description Normally, the MobiLink client dbmlsync ignores the server side state on the first synchronization of a subscription, although there was a problem where dbmlsync might have respected the server side state on a first synchronization, if an exchange was performed with the server to confirm the progress offsets of other subscriptions that had previously synchronized. As a result of this, data could have been lost and synchronizations could have failed with the error "Progress offset mismatch, resending upload from consolidated database's progress offset" being reported twice. This has been fixed.

CR:487721

CR Number:   487721 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 3619 19 Dec 2007 Fixed Description When IMAP, POP3 or LDAP authentication was enabled for a synchronization model, the generated authenticate_user event would have used the incorrect case for the class name, and the generated MobiLink server command line would not have enabled Java scripts with mlsupport.jar in the class path. Both problems have been fixed. The workaround is to manually fix the script and command line.

CR:487783

CR Number:   487783 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3621 03 Jan 2008 Fixed Description If a database mirroring system was using a mode other than "synchronous", loss of quorum did not force the primary server to restart and wait for one of the other two servers to become available. This has been fixed.

CR:487847

CR Number:   487847 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3620 20 Dec 2007 Fixed Description In very rare cases, execution of a DROP EVENT statement to drop a scheduled event could have crashed the server. This has been fixed.

CR:487869

CR Number:   487869 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 3620 21 Dec 2007 Fixed Description When using Text Completion, the list would not have contained any database objects if opened immediately after an owner name which was followed by a period, for example: SELECT * FROM myUser. Now, database objects are listed correctly. This problem only affected those owners which did not own any stored procedures.

CR:487950

CR Number:   487950 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) 9.0.2 3597 21 Dec 2007 Fixed Description The changes for Engineering case 484160 introduced a problem such that running databases without the SYSEXTERNLOGINS system table (version 5.5.05 or earlier) could have lead to a server crash when dropping users. This has been corrected.

CR:487972

CR Number:   487972 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3621 03 Jan 2008 Fixed Description When running the Extraction utility (dbxtract) on a large database, an equally large database would have been created, even though the amount of extracted data may have been significantly less. In cases such as this, the majority of pages in the new database would have been free pages. This has been corrected. Workaround Description  The problem does not occur if you extract to a reload file and use that to load data into a fresh database.

CR:488094

CR Number:   488094 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 3621 02 Jan 2008 Fixed Description A failing DROP TABLE statement could have caused table pages to be leaked. This could only have happened if pages had been allocated to the table's arenas between the last checkpoint and the failed DROP TABLE. Database validation would not have detected these leaked pages. This has been fixed. A workaround for this problem is to always issue a checkpoint before attempting a DROP TABLE that has a chance of failing.

CR:488097

CR Number:   488097 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) 9.0.2 3601 02 Jan 2008 Fixed Description The changes for Engineering case 485200, that forced the server to use the local setting of the Quoted_identifier option when connecting to an ASE remote server, was incomplete. Attemptiong to create a proxy table to an ASE remote server would have failed if the location string included the catalog name. This problem has now been fixed.

CR:488115

CR Number:   488115 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) 9.0.2 3601 02 Jan 2008 Fixed Description If a Java class was loaded and initialized by the forName() method and an exception was thrown during the class initialization, then the caller would have seen the incorrect exception java.lang.NoClassDefFoundError for class java/lang/VMAlreadyThrown. This has been fixed.

CR:488116

CR Number:   488116 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) 9.0.2 3601 02 Jan 2008 Fixed Description In very rare circumstances, the server may have crashed, or returned unexpected JVM exceptions like "IllegalAccessException", if multiple connection JVMs attempted to load the same class simultaneously. This has been fixed.

CR:488129

CR Number:   488129 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) 10.0.1 3621 02 Jan 2008 Fixed Description A numeric value longer than 80 digits may have been silently truncated to 80 characters when implicitly converted to a string value. One instance where this could have occurred was from within a column DEFAULT specification, e.g.: create table test (col1 numeric(108,38) default 1111111111222222222233333333334444444444555555555566666666667777777777.12345678901234567890123456789012345678) The value stored in the catalog (the SYSTABCOL "default" column) would have been truncated to: 1111111111222222222233333333334444444444555555555566666666667777777777.12345678 This has been fixed.

CR:488218

CR Number:   488218 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3624 08 Jan 2008 Fixed Description The Deployment Wizard was failing to create the following two registry entries: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 10.0 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 10.0 Admin This has been corrected.

CR:488265

CR Number:   488265 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 3628 03 Jan 2008 Fixed Description SQL Anywhere does not permit direct manipulation of catalog tables. Any attempt to do so should result in a permission denied error. Under certain circumstances though, an attempt to perform one of these prohibited operations could have caused the server to behave erratically or crash. The server will now correctly report a permission denied error.

CR:488271

CR Number:   488271 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 3623 07 Jan 2008 Fixed Description When the MobiLink server displayed warnings about the amount of memory that was swapped to disk, the number reported for "concurrent pages" was the maximum number of concurrent pages for current instance of the server. This created the impression that the page usage always increased. This has been corrected so that this number is now the number of concurrent pages in use at the time of the warning.

CR:488272

CR Number:   488272 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 3623 07 Jan 2008 Fixed Description When the MobiLink server can not store all the data needed for all the synchronizations in the cache memory (-cm flag), it must swap some to a temporary file. This data could have been written to the file more often than needed. This has now been fixed.

CR:488274

CR Number:   488274 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) 10.0.1 3622 04 Jan 2008 Fixed Description Applications attempting to make a TLS connection may have crashed. This has been fixed.

CR:488275

CR Number:   488275 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 3622 04 Jan 2008 Fixed Description It was possible for downloaded rows that contained long varchar or long binary columns to have been corrupted. Symptoms ranged from garbage characters read from a row to crashing the database. The problems were caused by an uninitialized variable, so the operations that can trigger the bug were varied. This has now been corrected.

CR:488324

CR Number:   488324 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3624 22 Jan 2008 Fixed Description When deployed to a Windows Mobile 6 device with the language set to Japanese, it was not possible to shut down the server once it was started. The menu was not there to shut down, or get version info. This would have happened on both Standard and Professional devices, and in the emulators for both types of device. This has now been fixed.

CR:488350

CR Number:   488350 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 3624 07 Jan 2008 Fixed Description When using the SET OPTION statement to change value of a database option, the absence of any value signifies a request to delete the option setting altogether. On the other hand, specifying the empty string ('') is considered a request to set the option value to be the empty string. However, the empty string was being treated the same way as the absence of the option value. Note that the problem is seen only when the SET OPTION statement is executed through dbisqlc, or another Embedded SQL application that makes use of the corresponding DBLIB API call. Sending the SET OPTION statement directly to the server for execution does not exhibit the erroneous behaviour. This has been fixed so that the server will no longer treat the empty string as a request to delete the option setting.

CR:488404

CR Number:   488404 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 3624 07 Jan 2008 Fixed 9.0.2 3605 07 Jan 2008 Fixed Description The value returned for the Connection and Database property QueryCachePages would have been incorrect. This has now been corrected.

CR:488406

CR Number:   488406 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3624 07 Jan 2008 Fixed Description In a very rare situation, attempting to execute a CREATE DATABASE statement could have resulted in a server crash. This has been fixed.

CR:488410

CR Number:   488410 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) 10.0.1 3624 07 Jan 2008 Fixed 9.0.2 3605 07 Jan 2008 Fixed Description A server running with AWE enabled may have performed poorly, or failed an out of memory assertion. This has been fixed.

CR:488514

CR Number:   488514 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 3629 09 Jan 2008 Fixed 9.0.2 3609 09 Jan 2008 Fixed Description When running on Windows Server 2008 (which has not yet been released by Microsoft), the server could have crashed while performing an integrated login when the INTEGRATED_SERVER_NAME was blank. This has been corrected

CR:488520

CR Number:   488520 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Solaris Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3628 15 Jan 2008 Fixed 9.0.2 3608 15 Jan 2008 Fixed Description On Unix systems, 64-bit ODBC applications required LONG_IS_64BITS to be defined at compilation time. Failure to do this would most likely have resulted in a crash in the application. This has been fixed

CR:488666

CR Number:   488666 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3631 24 Jan 2008 Fixed Description In very rare, timing-related circumstances, the server could have appeared to hang while executing a backup. The backup could have been a server-side backup or a client-side backup. This has been fixed.

CR:488676

CR Number:   488676 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2149 10 Jan 2008 Fixed 11.0.1 2344 05 Nov 2009 Fixed 9.0.2 3606 05 Nov 2009 Fixed 10.0.1 3984 06 Nov 2009 Fixed Description The HTTP option 'buffer_size' was limited to 64000 (64KB). On slow networks and/or large uploads or downloads, the overhead due to HTTP could have been significant. The 'buffer_size' option is now limited to 1000000000 (1GB). When using slow networks to perform HTTP or HTTPS synchronizations, tests could be done with larger values for 'buffer_size' to see if synchronization times improve. For versions 11.0.1 and up, this change only applies to the -xo option of the MobiLink server. The -x option already allows larger values.

CR:488680

CR Number:   488680 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 3625 10 Jan 2008 Fixed Description The server could have crashed if it was run with TCP/IP disabled, and diagnostic tracing was attempted. This has been fixed.

CR:488685

CR Number:   488685 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 2732 08 Dec 2009 Fixed Description Database recovery could have failed if the transaction log being recovered contained statements which caused checkpoints and recovery needed to be restarted. This has been fixed.

CR:488699

CR Number:   488699 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3626 11 Jan 2008 Fixed Description Table expressions with brackets may have caused syntax errors. For example, Select * from (table1) left join table2 This was corrected by adjusting the syntax to handle more general bracketing.

CR:488754

CR Number:   488754 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3630 18 Jan 2008 Fixed Description If a variable of type nchar, nvarchar or long nvarchar was declared, and then used in a query involving a remote table, then it was likely that the server would have failed with the error "not enough host variables". A simple example of a query that would have given this error is: SELECT * FROM remote_t WHERE c1 = @nvar In this example, if the table remote_t was a proxy table, and the variable @nvar was of type nchar, nvarchar or long nvarchar, then the server would have failed to execute the query with the "not enough host variables" error. This problem has now been fixed.

CR:488765

CR Number:   488765 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 3627 14 Jan 2008 Fixed Description Starting the utility database could have caused the server to fail assertion 200500. This has been fixed.

CR:488844

CR Number:   488844 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3631 21 Jan 2008 Fixed Description Unique indexes could have unexpectedly grown in size over time. As well, the server could have crashed while performing index maintenance. The server keeps deleted unique index entries until commit or rollback, in order to avoid having to do key range locking. In some cases the deleted entries were not being reclaimed properly. This has now been corrected.

CR:488857

CR Number:   488857 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 3628 15 Jan 2008 Fixed Description If an UPDATE statement contained a SET clause that assigned a value to a variable, then the variable could have been assigned a value that had a length or precision/scale that exceeded the declared domain of the variable. This would have caused subsequent operations with the variable to use this longer value. This problem only affected variables of type NUMERIC/DECIMAL or string types. This problem has now been fixed. For example: create variable @text varchar(3); update T set @text = 'long long string', salary = salary Previously, the update statement would pass and the value of @text was set to 'long long string'. Now, the statement fails with an error (provided the string_rtruncation option has its default value): Right truncation of string data [-638] ['22001']

CR:488859

CR Number:   488859 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 3628 14 Jan 2008 Fixed Description The Interactive SQL utility's Index Consultant could have failed to recommend indexes on a query containing the word "GO" in an identifier (For example, SELECT * FROM CATEGORY), complaining that it could only analyze one query at a time. This has been fixed.

CR:488862

CR Number:   488862 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3628 15 Jan 2008 Fixed Description The MobiLink client could have reported internal error 1003 during , and would have most likely occurred when the increment size was quite large, or if the server was slow to apply the upload. This has now been corrected.

CR:488941

CR Number:   488941 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3629 16 Jan 2008 Fixed Description The OPEN operation for a cursor that used a query that referenced proxy tables may have caused the server to crash. This would only have happened if the final cursour type was KEYSET. This has been fixed.

CR:488967

CR Number:   488967 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.0 19 Mar 2008 Fixed Description An existing stored procedure or user-defined function can now be recompiled using ALTER PROCEDURE owner.procname RECOMPILE or ALTER FUNCTION owner.funcname RECOMPILE The process of recompiling causes the procedure or function definition stored in the catalog to be re-parsed and verified that it is syntactically correct. For procedures that generate a result set but do not provide a RESULT clause, the server will also attempt to determine the result set characteristics for the procedure and store that information in the catalog. This can be useful if a table referenced by the procedure has been altered to add, remove or rename columns since the procedure was created. The preserved source for a procedure or function is not changed by recompiling. Procedures and functions whose definition are hidden via ALTER PROCEDURE owner.procname SET HIDDEN can be recompiled, and their definitions will remain hidden.

CR:488993

CR Number:   488993 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 3628 16 Jan 2008 Fixed Description A very specific form of database corruption could in rare instances have been undetected by the database validation tools. This has been fixed.

CR:489072

CR Number:   489072 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3629 16 Jan 2008 Fixed Description The server may have crashed while executing an image backup if all the files of the database were no longer accessible. The most likely scenerio for this problem to occur when the database was started in read-only mode on a network share, and the network connection was lost. This has been fixed and the BACKUP statement will now fail with an error.

CR:489098

CR Number:   489098 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3630 21 Jan 2008 Fixed Description If the Log Translation utility (dbtran) detected an error during execution, the SQL file it had generated up to that point was normally deleteed to ensure that a partial file was not used by accident. The -k command line option has now been added to prevent the SQL file from being erased if an error is detected. This may be useful when attempting to salvage transactions from a damaged log.

CR:489100

CR Number:   489100 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3631 24 Jan 2008 Fixed Description The MobiLink server must hold all table data needed for currently active synchronizations. When the total concurrent amount of table data exceeded the server's cache memory (-cm option) by more than 4200MB the server could have failed. This has been fixed.

CR:489152

CR Number:   489152 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3629 18 Jan 2008 Fixed Description If in error, the operating system date was set to a date in the far future, some servers and tools that collected feature logging information in sadiags.xml may have crashed. This has been fixed.

CR:489167

CR Number:   489167 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3629 17 Jan 2008 Fixed Description If an application used version 9 or earlier client software, and connected to a version 10.0.1 server, the server could have crashed or an incorrect character set could have been used. Also, if the application used the CHARSET connection parameter, the connection would have failed. This has been fixed.

CR:489179

CR Number:   489179 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 3631 22 Jan 2008 Fixed 9.0.2 3611 22 Jan 2008 Fixed Description Load table could have failed when loading data into a table that contained a self-referencing foreign key. As of Engineering Case 395054 the wait_for_commit option was set to 'off' for LOAD TABLE so that errors could be detected immediately. Now wait_for_commit for LOAD TABLE is set to 'on' if the table has a self-referencing foreign key, otherwise it is sett 'off' as before.

CR:489236

CR Number:   489236 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1348 22 Jan 2008 Fixed Description If a database is auto-started by executing DBVALID, the database will now be started in read-only mode. This was done to avoid making changes to the database in case it was intended to be used as part of a backup/recovery plan. Once a backup copy of a database has been started in read-write mode, transaction logs from the original database cannot be applied to it. If DBVALID connects to a database that is already running and the database was not started in read-only mode, DBVALID will now display a warning: "WARNING: database being validated was not started read-only" If a database requires recovery, it will fail to start in read-only mode. Note that most databases created by DBBACKUP will be marked as needing recovery. If a database to be validated requires recovery, and the user wishes to force it to be started read-write, specifying a valid value for the DBS connection parameter will allow the database to be started and recovery performed. For example: dbvalid -c "UID=DBA;PWD=sql;DBF=mycopy.db;DBS=-n mycopy" dbvalid -c "UID=DBA;PWD=sql;DBF=mycopy.db;DBS=-dh" would both allow dbvalid to execute if mycopy.db required recovery. The database could also be pre-started before running DBVALID.

CR:489238

CR Number:   489238 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3630 18 Jan 2008 Fixed Description When the Data Source utility dbdsn was used to create an ODBC data source for the iAnywhere Solutions Oracle ODBC Driver (using the -or switch) on UNIX, the driver name in the data source would have been incorrect (libdboraodbc10.so rather than libdboraodbc10_r.so). This has now been corrected.

CR:489239

CR Number:   489239 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3637 18 Jan 2008 Fixed Description The Apache redirector did not support the Mobilink client's HTTP persistent connection. Clients that attempted to use persistaent connections would have been switched to non-persistent HTTP after the first request. This has been corrected.

CR:489245

CR Number:   489245 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) 11.0.0 1008 18 Jan 2008 Fixed Description The Secure Stream Server Certificate page in the Deploy Synchronization Model Wizard mentions that the generated batch file will prompt for the password, but the generated batch file does not do this. This has been fixed.

CR:489258

CR Number:   489258 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 3630 18 Jan 2008 Fixed Description The HTTP synchronization parameter buffer_size was not always respected, particularly when using zlib compression, which could have caused upload performancto degrade for large uploads. This has been fixed. Also the default values for buffer_size have been increased as follows: Palm - 4K CE - 16K all other platforms - 64K and the maximum value for buffer_size has been increased from 64K to 1G.

CR:489266

CR Number:   489266 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 3630 22 Jan 2008 Fixed Description The MobiLink server could have silently failed a ping request from a 9.0.2 or earlier MobiLink client if the client's command line contained any options of upload_only and/or download_only. This problem has now been fixed.

CR:489337

CR Number:   489337 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 3631 22 Jan 2008 Fixed Description A connection attempting to execute an UNLOAD TABLE statement on more than one table concurrently could have lead to a server deadlock. This could also have happened when executing the Unload Database utility (dbunload). This has beed fixed.

CR:489427

CR Number:   489427 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) 11.0.0 1008 23 Jan 2008 Fixed Description When deploying to an existing remote database, the generated batch file needs to provide a password, but it did not prompt for one. The work around is to edit the generated batch file. This has been fixed so that it will now prompt for a password when using an existing remote database.

CR:489435

CR Number:   489435 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) 10.0.1 3631 22 Jan 2008 Fixed Description Attempting to execute a "MESSAGE ... TO CLIENT" statement using the Interactive SQL utility (dbisql) on Unix platforms, would very likely have caused it to hang. This problem has now been fixed.

CR:489436

CR Number:   489436 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1194 22 Feb 2008 Fixed Description If a statement contained a large number of query expressions (UNION, INTERSECT, EXCEPT), or other complex features such as subqueries, and, further, the statement had a large number of scalar expressions, then the statement could have taken longer to process than earlier releases. This has been fixed. Workaround Description  None.

CR:489443

CR Number:   489443 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 3631 22 Jan 2008 Fixed Description When using Java in the database and attempting to have the server execute a non-static Java method, a strange NullPointerException method would have been returned. A proper IllegalAccessException method, indicating that the method being executed is not static, will now be returned.

CR:489444

CR Number:   489444 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.0 1013 23 Jan 2008 Fixed 10.0.1 3633 23 Jan 2008 Fixed Description If an application that used Java in the database attempted to call a static Java method in a class that had constructors, but no constructor with 0 arguments, then the call would have failed with an InstantiationException. This problem has now been fixed.

CR:489538

CR Number:   489538 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1016 29 Jan 2008 Fixed 10.0.1 3634 29 Jan 2008 Fixed Description When examining the properties of a foreign key that was created as CHECK ON COMMIT, the properties would always have been reported that CHECK ON COMMIT was off. This has been fixed.

CR:489542

CR Number:   489542 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) 11.0.0 1170 26 Mar 2008 Fixed 10.0.1 3664 26 Mar 2008 Fixed 9.0.2 3642 26 Mar 2008 Fixed Description In very rare situations, the server could have hung while trying to drop a Remote Data Access connection. This problem has now been fixed.

CR:489597

CR Number:   489597 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3632 24 Jan 2008 Fixed Description The MobiLink server would have reported an incorrect error if the server was running in blocking ack mode, but an event for non blocking ack (-nba+) mode has been defined. The error reported was: "There is no download data script defined for table:.. ". This has been corrected.

CR:489598

CR Number:   489598 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 3632 24 Jan 2008 Fixed 9.0.2 3612 24 Jan 2008 Fixed Description 'Assertion 100904: Failed to redo a database operation' is generated when the server fails to recover the database based on information stored in the transaction log. This assertion never included the actual reason for the recovery failure. The actual error message is now included in the assertion message. In many cases the cause of the recovery failure was failure to find a data file that was used in a LOAD TABLE statement. In cases where the data file had been deleted recovery could not continue. The fact that the file is missing is now incorporated into the assertion message.

CR:489600

CR Number:   489600 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.0 1009 25 Jan 2008 Fixed 10.0.1 3632 25 Jan 2008 Fixed Description In rare circumstances, after a backed-up copy of a database was started, or after a database had undergone recovery, the Validation utility (dbvalid) could have caused the server to fail assert 101412 - "Page number on page does not match page requested". Even though the server failed the assertion, the database file was not corrupt, and the database should have continued to operate normally. This has been fixed.

CR:489605

CR Number:   489605 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) 9.0.2 3612 24 Jan 2008 Fixed Description In case-sensitive databases, dbspace names were also case-sensitive. DDL statements referring to the dbspace names were required to specify the dbspace names exactly as they appeared in the catalog. This has been fixed. Note, it is possible that a database could contain two dbspaces with the same name in different cases. This change would prevent these dbspaces from being differentiated. This would be a problem when migrating to versions 10 or later as well.

CR:489694

CR Number:   489694 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3624 24 Jan 2008 Fixed Description Support has now been added for Windows Mobile 5 SmartPhone Edition and Windows Mobile 6 Standard edition. All SQL Anywhere Windows CE functionality is supported on the SmartPhone, except for the following: - the SharedMemory communication protocol is not supported. The TCP/IP communication protocol is used even if no protocol is specified, and a server name must always be specified when making a connection, or the connection will fail. - the preferences dialog on the database server and MobiLink client is not supported. The preferences dialog normally appears if no command line options are used. - the ODBC and OLEDB connection prompt dialog is not supported. This dialog normally may appear depending on the DriverCompletion parameter to SQLDriverConnect, or the DBPROP_INIT_PROMPT OLEDB property. - the Unload / Reload support is not available. This includes dbunload.exe, dbrunsql.exe and the unload support server.

CR:489741

CR Number:   489741 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3633 25 Jan 2008 Fixed Description If an application using the iAS Oracle driver issued a "call procedure_name" statement (without open and close parentheses) through the ODBC functions SQLPrepare or SQLExecDirect, and the procedure "procedure_name" returned a result set, the driver could have crashed when the "Procedure returns results" check-box was checked on Windows, or the "ProcResults" entry was set to 'yes' on UNIX. This has now been fixed.

CR:489744

CR Number:   489744 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 Nov 2008 Fixed Description VALIDATE TABLE did not correctly handle tables with more than 256 rows on a table page. The problem has been fixed. VALIDATE TABLE has also been enhanced to allow validation to proceed on very large tables or, more precisely, on tables whose last page number was very large. Prior to this change, error 08W13 (-86) "Not enough memory to start" could have been reported. Note that if the table is actually very large relative to the cache, validation may take a very long time.

CR:489871

CR Number:   489871 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.0 1133 15 Feb 2008 Fixed 10.0.1 3647 22 Feb 2008 Fixed 9.0.2 3621 22 Feb 2008 Fixed Description There were several problems possible when the -m server command line option was used to truncate database transaction log files at checkpoint. Some of these problems were, but were not limited to, assertions indicating that the log could not be deleted or restarted while a virus scanner or disk defragmenter was accessing the log file; and occasionally having zero byte transaction log file remaining after a system failure. These problems should no longer occur as the transaction log file is no longer deleted and recreated at checkpoint time when the -m option is being used. Instead the file gets truncated to one page in size and then continues to be used. A side effect of this change is that there will be a one page log file remaining after a successful shutdown of a database, instead of no log file.

CR:489889

CR Number:   489889 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.0 1011 25 Jan 2008 Fixed 10.0.1 3633 25 Jan 2008 Fixed 9.0.2 3613 25 Jan 2008 Fixed Description When executing an UPDATE on a remote table with a cursor range, the cursor range would have been ignored, and all rows would have instead been updated. For example, executing the following: UPDATE TOP 2 proxy_t SET proxy_t.data = 'Hello' ORDER BY proxy_t.pkey ASC; would have updated all rows in the table. This problem has now been fixed.

CR:489903

CR Number:   489903 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1011 28 Jan 2008 Fixed 10.0.1 3645 19 Feb 2008 Fixed Description Some HTTP intermediaries add more information to the HTTP User-Agent header. This was causing failed synchronizations, and has now been fixed. Note that any intermediary that removes the information put into the User-Agent by the MobiLink client will cause synchronizations to fail.