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

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

CR:481467

CR Number:   481467 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3570 26 Sep 2007 Fixed Description Calling the byte_length() function with an integer value for the parameter, would have returned a value inconsistent with SQL Anywhere server. This has been corrected.

CR:481493

CR Number:   481493 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3586 23 Oct 2007 Fixed 9.0.2 3574 23 Oct 2007 Fixed Description In rare timing dependent cases a Unix application could have hung if prefetch was enabled and only part of a result set was fetched. This has been fixed.

CR:481521

CR Number:   481521 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 3570 27 Sep 2007 Fixed Description When synchronizing with HTTP or HTTPS, the MobiLink server could have caused too many HTTP request/response cycles. The extra exchanges and extra bytes on the wire would have made synchronizations take longer. This problem was timing-dependent, and its likelyhood was inversely proportional to the round-trip time between the client and server. This has been fixed.

CR:481607

CR Number:   481607 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 3578 10 Oct 2007 Fixed Description The database file size may have continued to grow, even when it was not expected to. This problem could have occurred any time, but would likely be more noticeable when constantly inserting and deleting the same set of rows (given the conditions outlined below), running without a redo log, or when checkpointing frequently. The main symptom of this problem was that the number of pages allocated to a table's extension arena continues to increase during inserts, deletes or updates when the amount of data in the table remained constant. There were two main ways this problem would have been more readily noticed. First, by running without a transaction log or when checkpointing frequently. In this case, the number of pages in the ISYSTAB extension arena grows. Second, when doing repeated updates, or paired inserts and deletes to a particular set of rows, when the number of overall rows did not increase. For the problem to occur in this case, the rows must have contained any type of CHAR or BINARY value (i.e., VARCHAR, LONG VARCHAR , etc.), and must have values longer than the column's INLINE amount. If the table was truncated or dropped, the extra pages allocated to the extension arena would have been freed up and made available for other uses. This has now been fixed. Note, when this problem is noticed, rebuilding the affected database with the fix will eliminate the extra pages from the extension arena.

CR:481644

CR Number:   481644 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 3570 28 Sep 2007 Fixed 9.0.2 3562 28 Sep 2007 Fixed Description Same machine connections were using communication compression if the COMPRESS connection parameter or -pc server option was specified. This has been fixed so that only remote connections will be compressed. The sa_conn_compression_info procedure could have reported incorrect compression rates or packet compression rates if more than about two million bytes had been transferred since the server started. This has been fixed as wll. In order to get the fixed sa_conn_compression_info procedure, the ALTER DATABASE UPGRADE PROCEDURE ON statement must be executed (this will also upgrade the database to the current version, if necessary).

CR:481645

CR Number:   481645 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 3581 06 Nov 2007 Fixed Description After loading a Java class, it is initialized. The class initialization is performed by the connections's Java VM when the class is used for the first time. If two VM's attempt to initialize the same class concurrently, one needs to wait for the other to complete. If the waiting VM was cancelled, then the class was marked as erroneous, with a status of NoClassDefFoundError, and it did not get initialized. Later during this connection the VM may have returned a NoClassDefFoundError exception or, if the connection attempted to access the class, a server crash would have occurred. This has been fixed.

CR:481649

CR Number:   481649 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 3570 05 Oct 2007 Fixed Description It was possible, although very rare and timing related, for backups to have hung. The backup could hava been been initiated from either the dbbackup utility, or the BACKUP DATABASE statement. When this problem occurred, other requests would have proceeded as normal; however, since a backup prevents checkpoints, any connection that issued a checkpoint would have been blocked. This has now been fixed.

CR:481716

CR Number:   481716 Product Name:   MobiLink 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 1067 25 Jan 2008 Fixed 10.0.1 3649 25 Jan 2008 Fixed Description When deploying a sSnchronization Model to an Adaptive Server Enterprise consolidated database, table references in the generated SQL were not prefixed by the database and owner, so deployment would have failed for tables with a different database or owner than those for the connected user. A workaround is to manually edit the SQL file for the consolidated database. This has been fixed so that table references are now prefixed by database and owner for Adaptive Server Enterprise consolidated databases.

CR:481738

CR Number:   481738 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3572 01 Oct 2007 Fixed Description If the Interactive SQL utility dbisql used the -onerror command line option when connected to an authenticated server , the connection would not have been authenticated. This would have caused some statements to have failed with authentication errors after the grace period had expired. This has been fixed.

CR:481824

CR Number:   481824 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 3571 01 Oct 2007 Fixed Description An XML parameter can now be passed to an external function. CREATE PROCEDURE mystring( IN instr XML ) EXTERNAL NAME 'xmlfunc@xmltools.dll'; XML parameters are passed in the same manner as LONG VARCHAR parameters. XML parameters are available when using the "new" external function call API.

CR:481834

CR Number:   481834 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 3592 05 Oct 2007 Fixed 9.0.2 3579 01 Nov 2007 Fixed Description Applying a transaction log to a database using the server command line option -a, could have failed assertion 100902: "Unable to find table definition for table referenced in transaction log -- transaction rolled back". This would have occurred if one log (B) contained all of the operations of the preceding log (A), plus additional operations, and a sequence of modifications to a table T by one connection, which begin in log A and continued into log B, were active when the backup that created log A was performed. This has been fixed. The fix affects the contents of the transaction log at the time a backup is performed; thus, a fixed server does not permit log backups created prior to the fix to be applied. Note that the problem does not affect backups where a log rename is performed after each backup, since in that case the logs will not contain overlapping sections. The problem can be avoided in version 10 by applying all of the logs at one time using the -ar or -ad options, which will cause the server to skip logs that are included by subsequent logs.

CR:481845

CR Number:   481845 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3586 23 Oct 2007 Fixed 9.0.2 3574 23 Oct 2007 Fixed Description The following fixes have been made to the Listener utility 1) IP tracking was sometimes not firing BEST_IP_CHANGE event when the Listener was run on Windows CE. 2) Engineering case 466446 introduced a problem in the Listener where options following the options -ga or -gi may have been misinterpreted. 3) Asynchronous IP tracking (-ga) was not working on Windows CE devices. Note, the Listener command line option -ga has been deprecated and asynchronous IP tracking is now implicit. The default of -gi has been changed from 10 seconds to 60 seconds. The polling mechanism now serves only as a backup. Users should not need to use -gi except for trouble shooting.

CR:481891

CR Number:   481891 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 3572 02 Oct 2007 Fixed 9.0.2 3564 02 Oct 2007 Fixed Description When similar requests are executed concurrently, there would have be large variations in their response times. This problem would have shown up more on single processor machines. This has been fixed

CR:481893

CR Number:   481893 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 3574 04 Oct 2007 Fixed 9.0.2 3565 04 Oct 2007 Fixed Description Referencing a stored procedure in the FROM clause of a query could have incorrectly returned a "permission denied" error. This would have occurred when the following conditions were true: - the procedure was owned by a user with DBA authority - the procedure contained a single SELECT statement and no other statements - permission to execute the procedure was granted to a non-DBA user - the procedure's SELECT referenced a table for which the procedure owner had not been granted permissions This has been fixed. A workaround is to add a statement such as "if 1 = 0 then return end if;" to the start of the procedure. Workaround Description  Using CALL dba.sp_list() works.

CR:481894

CR Number:   481894 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 3572 02 Oct 2007 Fixed Description In rare cases, calling a secure web procedure could have caused the server to crash. This has been fixed.

CR:481898

CR Number:   481898 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3175 03 Oct 2007 Fixed Description If a Mobilink server with QAnywhere was running on a non-ASA consolidated database and tried to process a message received from a JMS server, a SQL statement could have failed resulting in the message not being properly received by QAnywhere. This has been fixed.

CR:481904

CR Number:   481904 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 3574 04 Oct 2007 Fixed Description Attempting to call a non-existent procedure using the EXECUTE IMMEDIATE statement and the 'WITH RESULT SET OFF' clause (ie. EXECUTE IMMEDIATE WITH RESULT SET OFF 'call sp_nonexist();'), would have caused the connection to hang. This has been corrected so that an error indicating that the procedure does not exist is now reported.

CR:481905

CR Number:   481905 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3574 04 Oct 2007 Fixed 10.0.0 2885 04 Oct 2007 Fixed Description When the MobiLink client dbmlsync was run against a database created using Turkish settings, it would fail shortly after startup with the message: SQL statement failed: (-141) Table 'sysarticlecol' not found. This problem has been fixed.

CR:481922

CR Number:   481922 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 3578 15 Oct 2007 Fixed Description Backslashes in SQL remote options, such as in: SET REMOTE "FILE" OPTION "PUBLIC"."Directory" = '\\\\MACHINE\\Folder\\Subfolder'; were not being preserved when the database was unloaded. Given the above option setting, the reload.sql file would have contained: SET REMOTE "FILE" OPTION "PUBLIC"."Directory" = '\\MACHINE\Folder\Subfolder'; which, on reload, would be incorrectly interpreted as "\MACHINE\Folder\Subfolder", causing SQL Remote to fail. This has been corrected.

CR:481964

CR Number:   481964 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 3573 03 Oct 2007 Fixed 9.0.2 3565 03 Oct 2007 Fixed Description The procedure dbo.sa_disk_free_space contained a redundant permissions check, and has been removed. The procedure can now be called if any of the following conditions hold: - the caller has DBA authority - the procedure is called from another procedure owned by a user having DBA authority - execute permission has been granted To correct the problem in existing databases without rebuilding or upgrading, the call to dbo.sp_checkperms in dbo.sa_disk_free_space can be removed.

CR:481965

CR Number:   481965 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 3574 03 Oct 2007 Fixed Description When using the following SQLAnywhere options with the reference database: default_timestamp_increment = 10000 truncate_timestamp_values = 'On' the UltraLite database produced when running the UltraLite Initialization utility ulinit on this database would have caused problems when synchronizing. MobiLink would have complained about timestamp precision mismatches. Ulinit was not setting the timestamp_increment from the SA default_timestamp_increment value. The workaround is to set the timestamp_increment setting on the ulinit command line, using the -o keyword=value option, as follows: ULINIT <existing options> -o timestamp_increment=1000

CR:481970

CR Number:   481970 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   HP-UX Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3572 03 Oct 2007 Fixed 9.0.2 3564 03 Oct 2007 Fixed Description The setting of the ASTMP_UMASK environment variable would have been ignored on HP-UX systems. Also, the umask setting was ignored in the creation of the lrm_socket on HP-UX and AIX. These problems have now been fixed.

CR:481976

CR Number:   481976 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 1860 24 Jun 2008 Fixed 10.0.1 3712 24 Jun 2008 Fixed 11.0.0 1411 13 Nov 2008 Fixed Description When creating a new synchronization model for an existing remote database, the column order may not have been correct for upload_fetch or upload_fetch_column_conflict events. This has now been fixed. To fix existing synchronization models (after installing this fix), each synchronizing table must be set to 'Not Synchronized', the model saved, and then set back to their previous synchronization settings.

CR:481994

CR Number:   481994 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3576 09 Oct 2007 Fixed Description When using the MobiLink Java DirectRow api, setting or getting data of types Date, Time or Timestamp could have worked incorrectly. When using a ResultSet, the returned value could have been null, When using a PreparedStatement, the value could have been set as null. This has been fixed.

CR:482093

CR Number:   482093 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 3640 10 Jan 2008 Fixed Description If prior to a database going down dirty, a materialized view was refreshed by a connection with the option isolation_level='snapshot' set, or with SNAPSHOT isolation specified for a REFRESH statement, and the no checkpoint occurred between the REFRESH statement execution and the database going down, the database would have failed to recover. This has now been corrected.

CR:482124

CR Number:   482124 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3576 05 Oct 2007 Fixed Description The UltraLite and MobiLink security DLLs/shared objects had entry points that were inconsistent with those used by the SQL Anywhere database server. This has been corrected. The DLLs/shared objects and the binaries that load them, must be at the noted build number or later, or else the DLL/shared object will fail to load and an error (indicating missing/invalid DLL/shared object) will be issued.

CR:482137

CR Number:   482137 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3576 09 Oct 2007 Fixed Description The Deployment Wizard did not deploy the utility dbelevate10.exe, that is required for running on Windows Vista. This has been corrected.

CR:482138

CR Number:   482138 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 3634 29 Jan 2008 Fixed Description The Deployment Wizard would have created an install that did not register the Dbmlsync Integration Component. This has been corrected by having dbmlsynccom.dll and dbmlsynccomg.dll self register when installed. Workaround Description  Execute the regsvr32 commands manually after the install regsvr32 "%SQLANY10%\win32\dbmlsynccom.dll" regsvr32 "%SQLANY10%\win32\dbmlsynccomg.dll"

CR:482373

CR Number:   482373 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 3577 09 Oct 2007 Fixed Description Any MobiLink utility with a GUI could have crashed when it attempted to display a large message (ie. greater than 28,000 bytes), when the application was running in minimized mode. This problem affects only Windows systems, and was more likely to have occurred if the application was running with the full verbosity enabled (-dl command line option). This has now been corrected.

CR:482379

CR Number:   482379 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3581 16 Oct 2007 Fixed 9.0.2 3575 25 Oct 2007 Fixed Description After applying an EBF for SQL Anywhere Windows systems with Visual Studio 2005 installed, there could have been some garbled characters left at the beginning of the machine.config file for .NET Framework 2.0. This would have caused the SQL Anywhere Explorer for Visual Studio 2005 to not work properly. This has been fixed.

CR:482493

CR Number:   482493 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) 9.0.2 3569 10 Oct 2007 Fixed Description The INTERSECT and EXCEPT set operators were using too much stack during optimization process which may have resulted in very complex queries failing with a stack overflow. The stack usage for these operations has now been significantly reduced.

CR:482520

CR Number:   482520 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 3588 24 Oct 2007 Fixed Description An upload that contained invalid or corrupt table data could have crashed the MobiLink server. The MobiLink server will now correctly fail the synchronization when it encounters invalid data..

CR:482591

CR Number:   482591 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1168 25 Mar 2008 Fixed 10.0.1 3662 25 Mar 2008 Fixed 9.0.2 3640 25 Mar 2008 Fixed Description If an application using the iAnywhere JDBC driver had multiple threads trying to create connections, or create statements/prepared statements/callable statements at the same time, then there was a chance the JDBC driver could have crashed. The crashes were actually in the Java VM, and work arounds have now been implemented.

CR:482593

CR Number:   482593 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 3582 25 Oct 2007 Fixed Description If a query contained a subquery that used a hash filter predicate, such as hash(T.x) in hashmap(R.y), then it was possible for the hash filter to inappropriately reject rows that ought to be accepted resulting in an invalid result set. This has been fixed.

CR:482612

CR Number:   482612 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 3569 11 Oct 2007 Fixed Description Executing a very complex query could have caused the server to crash due to a stack overflow. This has been fixed.

CR:482615

CR Number:   482615 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 3579 15 Oct 2007 Fixed Description An unexpected SQL error may have been received when creating views over columns with character length semantics. This could have occurred with NVARCHAR or CHAR length VARCHAR colums when using a database with a multi-byte character set. For example: CREATE TABLE test(col NVARCHAR(8191)); CREATE VIEW test_view AS SELECT col from test; or, the following, when issued on a UTF-8 database: CREATE TABLE test(col VARCHAR(8191 CHAR)); CREATE VIEW test_view AS SELECT col from test; would have failed with SQL error CHAR_FIELD_SIZE_EXCEEDED (-1093): "The size of the character column, variable, or value data type exceeds 32767". This has been fixed.

CR:482640

CR Number:   482640 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 3569 12 Oct 2007 Fixed Description The Interactive SQL utility dbisql may not have displayed multiple result sets when connected with the iAnywhere JDBC driver (which is the default). This has been fixed.

CR:482703

CR Number:   482703 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1217 30 Apr 2008 Fixed 10.0.1 3686 30 Apr 2008 Fixed Description The installed version of the MobiLink system setup could not have been found by the Sybase Central MobiLink Plug-in for Microsoft SQL Server when the default_schema was different than the connected user. This has been fixed so that when checking schema with a Microsoft SQL Server consolidated database, the default_schema is now used. Note, a work around is to make the current user the owner of the MobiLink system setup.

CR:482717

CR Number:   482717 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 3580 15 Oct 2007 Fixed Description If the database option tsql_variables was set to ON (as it would be for OpenClient connections), executing a CREATE DOMAIN statement containing identifiers beginning with @ would have created the domain incorrectly. This would have resulted in the error "not enough values for host variables" on a subsequent operation on a table containing a column defined using the domain. Also, executing a CREATE TRIGGER statement with an identifier beginning with @ prior to the body of the trigger would result in a syntax error. Both of these problems have been fixed.

CR:482741

CR Number:   482741 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3581 15 Oct 2007 Fixed Description If a QAnywhere Server Management Request was used to cancel messages in a Server Store, messages were cancelled even after they had already been downloaded to the message recipient. This could cause consistency problems in the server store and possibly disable message transmissions on the receipient device. This has been fixed.

CR:482742

CR Number:   482742 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3581 15 Oct 2007 Fixed Description QAnywhere documentation lists IAS_TEXT_CONTENT and IAS_BINARY_CONTENT as constants a that can be used to refer to the two different message content types in selector, transmission, and delete rules. However, the QAnywhere server was recognizing the constants IAS_TEXTCONTENT and IAS_BINARYCONTENT instead. This would have caused rules using the documented constants to not work as desired. This has been fixed so that both constant formats are now recognized.

CR:482773

CR Number:   482773 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 3582 18 Oct 2007 Fixed 10.0.0 2886 18 Oct 2007 Fixed Description The ODBC driver could have caused a segmentation fault when used on Unix systems with some ODBC Driver Managers (for example, unixODBC) if the DSN existed but the connection failed (for example, it failed to autostart a server). This has been fixed.

CR:482822

CR Number:   482822 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3581 15 Oct 2007 Fixed Description An INPUT statement could have failed if it referenced a table owned by the current user and there was also a table with the same name which was owned by a different user, and the owner was not given in the INPUT statement. This has now been fixed.

CR:482832

CR Number:   482832 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3582 19 Oct 2007 Fixed Description When the visual form of the Dbmlsync Integration Component was used on Japanese Windows 2000, the font selected for the log window did not support Japanese characters and so these were not rendered correctly. This problem did not occur on Windows XP. This problem has been fixed on Japanese Windows 2000 only, as it does not occur in any other environment.

CR:482833

CR Number:   482833 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 3581 16 Oct 2007 Fixed Description The return code was not set correctly following an EXIT statement if it was executed from a .SQL file, its argument was not a literal exception, and the "Show multiple result sets" option was ON. That is, SET TEMPORARY OPTION isql_show_multiple_result_sets='on'; EXIT 123; worked, but SET TEMPORARY OPTION isql_show_multiple_result_sets='on'; CREATE VARIABLE retcode INT; SET retcode = 123; EXIT retcode; did not, the return code was always zero. This has been fixed.

CR:482839

CR Number:   482839 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3583 22 Oct 2007 Fixed 10.0.0 2887 22 Oct 2007 Fixed 9.0.2 3573 22 Oct 2007 Fixed Description When Microsoft's Business Intelligence Development Studio attempted to insert string values into a row using the OLEDB InsertRow() method, it passed in a pointer to the data to be inserted. For string values (DBTYPE_STR), it sometimes did not pass in a length, which caused the SQL Anywhere provider to insert a string of length zero into the corresponding column. This behavior has been changed. Now, for types DBTYPE_STR and DBTYPE_WSTR, the provider will attempt to determine the string's true length when no length is passed in, with the assumption being that the string is null-terminated.

CR:482841

CR Number:   482841 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 3581 16 Oct 2007 Fixed Description Execution of a LOAD TABLE statement may have performed poorly if it was used on a table containing a column with DEFAULT AUTOINCREMENT. The server was unnecessarily doing a full reverse index scan to determine the new maximum value for the autoincrement column after the LOAD TABLE. This has been fixed.

CR:482851

CR Number:   482851 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3602 19 Nov 2007 Fixed Description The provider now supports using named parameters. If all the parameter names are specified, the provider will map them to the parameter values when the command is executed. The order of parameters does not have to be the same as the order of host variables when using named parameters. For example, using named parameters when calling a procedure: SACommand cmd = new SACommand( "MyProc", conn ); cmd.CommandType = CommandType.StoredProcedure; SAParameter p4 = new SAParameter( "p4", SADbType.Integer ); p4.Direction = ParameterDirection.Output; cmd.Parameters.Add( p4 ); SAParameter p3 = new SAParameter( "p3", SADbType.NChar, 30 ); p3.Direction = ParameterDirection.Output; cmd.Parameters.Add( p3 ); SAParameter p2 = new SAParameter( "p2", SADbType.Char, 20 ); p2.Direction = ParameterDirection.InputOutput; p2.Value = "222"; cmd.Parameters.Add( p2 ); SAParameter p1 = new SAParameter( "p1", SADbType.Integer ); p1.Direction = ParameterDirection.Input; cmd.Parameters.Add( p1 ); cmd.ExecuteNonQuery(); given following procedure definition; CREATE PROCEDURE MyProc( in p1 int, inout p2 char(20), out p3 nchar(30), out p4 int ) BEGIN SET p2 = p2 + 'abc'; SET p3 = '333xyz'; SET p4 = p1 * 4; END Using named parameters in a query: SACommand cmd = new SACommand( "UPDATE MyTable SET name = :name WHERE id = :id", conn ); SAParameter p1 = new SAParameter( "id", SADbType.Integer ); p1.Direction = ParameterDirection.Input; p1.Value = 1; cmd.Parameters.Add( p1 ); SAParameter p2 = new SAParameter( "name", SADbType.Char, 40 ); p2.Direction = ParameterDirection.Input; p2.Value = "asdasd"; cmd.Parameters.Add( p2 ); cmd.ExecuteNonQuery();

CR:482931

CR Number:   482931 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 3571 16 Oct 2007 Fixed Description If corresponding items in two select lists of a INTERSECT or EXCEPT set operator had different data types, the server would have chosen a data type for the corresponding column in the result and automatically converted the columns in each select list appropriately. If the conversion failed, and the server was low on cache memory, then it may returned the assertion 102501 instead of the correct conversion error. This has been fixed.

CR:482952

CR Number:   482952 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 3581 18 Oct 2007 Fixed 9.0.2 3571 18 Oct 2007 Fixed Description The server may have crashed when doing extensive console logging (e.g. when -zr all was used). This was more likely to have occurred on multi-processor machines, and has now been fixed.

CR:482958

CR Number:   482958 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 3584 29 Oct 2007 Fixed Description It was possible, although rare, for the optimizer to select less than optimal access plan for complex queries. This has been fixed.

CR:482977

CR Number:   482977 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 3582 18 Oct 2007 Fixed Description If a global variable had the same name as a procedure's parameter, statements within the procedure could have executed using the wrong variable. For this to have occurred, no other variable references could occur between the last reference to the global variable and the execution of the statement referencing the local variable in the procedure. This has been fixed. One workaround is to use a different name for the global variable.

CR:483065

CR Number:   483065 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3584 12 Nov 2007 Fixed Description The connection property 'CommLink' was not returning 'local' for local TCP/IP connections on some patched Solaris 10 systems. These systems had to have at least two active network interfaces for the problem to occur. This has now been fixed. A work around is to use the MyIP connection option on the client, and the MyIP TCP/IP option on the server and to make sure that they match.

CR:483072

CR Number:   483072 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3582 19 Oct 2007 Fixed Description The SQL Anywhere Deployment wizard would not have deployed the file mlnotif.jar when MobiLink server was selected. This file was missing from the list of files to deploy and has now been added.

CR:483129

CR Number:   483129 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 3575 25 Oct 2007 Fixed 8.0.3 5578 25 Oct 2007 Fixed Description Engineering Case 454858 introduced a problem where attempting to execute concurrent LOAD TABLE statements which used the same global temporary table, would have caused one of the statements to have been blocked. This has been fixed so that the loads now run concurrently once again.

CR:483213

CR Number:   483213 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3582 25 Oct 2007 Fixed Description The ODBC driver was describing NCHAR and NVARCHAR columns as SQL_WCHAR or SQL_WVARCHAR, with the SQL_DESC_OCTET_LENGTH specified as too small, if the column contained surrogate pairs. Depending on the application, this could have resulted in fetched NCHAR data being truncated. This has been fixed so that NCHAR columns now have a SQL_DESC_OCTET_LENGTH which allows for surrogate pairs. Note, this problem also affected the iAnywhere JDBC driver, which is used by the Interactive SQL utility dbisql.

CR:483223

CR Number:   483223 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 3583 19 Oct 2007 Fixed Description The server could have crashed when executing the sa_transactions system procedure. This has been fixed.

CR:483226

CR Number:   483226 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) 19 Oct 2007 Fixed Description The ON EXISTING UPDATE clause of the INSERT statement allows existing rows to be updated based on a primary key look-up. The INSERT statement with this clause uses each input row to either insert the row or update the contents of an existing row. The server fired all applicable INSERT and UPDATE triggers except the statement level UPDATE triggers during the execution of this statement. This has been fixed so that the server will now fire statement level UPDATE triggers as well.

CR:483227

CR Number:   483227 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3606 26 Nov 2007 Fixed 9.0.2 3587 26 Nov 2007 Fixed Description As well as the fixes to correct multi-threaded applications in Engineering case 485568, changes have also been made to thread synchronization to prevent hangs when running on multi-processor machines.

CR:483230

CR Number:   483230 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 3583 19 Oct 2007 Fixed Description Ping synchronizations from a MobiLink client would have failed if the MobiLink Server had been connected to a consolidated database where the authenticate_parameters event existed. This has now been fixed.

CR:483261

CR Number:   483261 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 01 Nov 2007 Fixed 9.0.2 3579 01 Nov 2007 Fixed Description The methods ClearAllPools and ClearPool could have caused an exception if any of the connections in a pool were not opened. This problem has been fixed.

CR:483314

CR Number:   483314 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3583 19 Oct 2007 Fixed Description Interactive SQL could have crashed if the menu item for a recently opened file (at the bottom of the "File" menu) was clicked while a statement was currently being executed. This has been fixed.

CR:483316

CR Number:   483316 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3589 25 Oct 2007 Fixed 9.0.2 3575 25 Oct 2007 Fixed Description The .NET provider could have gone into an endless loop, with very high CPU usage, on termination of the application. This has been corrected.

CR:483335

CR Number:   483335 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 3583 22 Oct 2007 Fixed Description When entering a multi-line rule condition, it would have been saved in a way that caused the line to appear to have been run together when the line was next edited. This has been fixed.

CR:483356

CR Number:   483356 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 3583 22 Oct 2007 Fixed Description The server could have become deadlocked when a connection attempted to block while updating row. This is more likely to happen when the server is under heavy load. This has now been corrected.

CR:483427

CR Number:   483427 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3588 23 Oct 2007 Fixed Description An attempt to stop a MobiLink service using the Service utility dbsvc would have failed with a message like "dbmlstop: No such file or directory". This has been fixed.

CR:483441

CR Number:   483441 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 3591 29 Oct 2007 Fixed Description In a database mirroring system, if the mirror or arbiter connection strings contained any of the DoBroadcast, TDS, BroadcastListener, LocalOnly, ClientPort, VerifyServerName, LDAP, or DLL TCPIP parameters, that server could have crashed, or failed to connect to the partner or arbiter servers. This has now been fixed.

CR:483452

CR Number:   483452 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 30 Oct 2007 Fixed Description The IAS Oracle driver requires Oracle's OCI client libraries. If these libraries are not installed properly, the IAS driver would have silently failed to load. The driver will now load,, but will fail when first used by an application. The application can query the failure and will receive an error which indicates the OCI library is missing.

CR:483518

CR Number:   483518 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 3603 21 Nov 2007 Fixed 9.0.2 3585 21 Nov 2007 Fixed Description In some cases, requesting a graphical plan for a query could have caused the server to fail with a fatal error: 'A read failed with error code: (38), Reached the end of the file. Fatal error: Unknown device error.' This has been fixed.

CR:483533

CR Number:   483533 Product Name:   SQL Anywhere Product Component:   DBLIB 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 3592 31 Oct 2007 Fixed 9.0.2 3579 31 Oct 2007 Fixed Description If the LOGFILE connection parameter was specified, when connecting to either a personal or network server without specifying a server name, the line "Connected to the default personal server" was logged. This was inaccurate, and possibly confusing. The text of this message has now been changed to "Connected to the default SharedMemory server."

CR:483558

CR Number:   483558 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 3574 23 Oct 2007 Fixed Description The value of connection_property('TransactionStartTime') would have been an empty string if the only statement executed since the last COMMIT/ROLLBACK was an INSERT ... SELECT. This has been fixed.

CR:483559

CR Number:   483559 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3589 24 Oct 2007 Fixed 9.0.2 3575 24 Oct 2007 Fixed Description The server could have gone into an endless loop, with very high CPU usage, instead of reporting an error when it ran out of free pages in the cache. This has been fixed.

CR:483578

CR Number:   483578 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 3589 24 Oct 2007 Fixed Description When creating a download using the MobiLink Java direct row API, some actions could haver destabilized the MobiLink server. Setting parameters with incompatible data, or setting columns multiple times with null values that were not nullable, could have caused the MobiLink server to send an invalid row to the synchronization client, or crash. This has been fixed.

CR:483635

CR Number:   483635 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3623 04 Jan 2008 Fixed 9.0.2 3604 04 Jan 2008 Fixed Description If a trigger was created using the Interactive SQL utility with the syntax: CREATE TRIGGER owner.name ... then Sybase Central would have displayed the trigger SQL with the trigger's owner replaced by the trigger's name, such as: ALTER TRIGGER name.name ... This has been fixed. Now the SQL is displayed correctly as: ALTER TRIGGER name ... That is, the owner (which is syntactically valid, but is ignored by the engine) is removed from the source.

CR:483636

CR Number:   483636 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1142 05 Mar 2008 Fixed Description When modifying a procedure, if one or more comments were typed before, or anywhere within, the ALTER PROCEDURE <owner>.<name> portion of the statement, then these comments would have been lost when the statement was saved to the database. However, the editor would have given no indication that this was the case until the procedure was refreshed, for example, by pressing F5. This has been fixed so that the comments are now automatically relocated to the point immediately following the above portion of the statementL, so that they are preserved with the procedure source. In addition, the SQL editor is automatically updated and a message that the statement has been adjusted is displayed. The above also applies to functions, views, materialized views, triggers and event handlers.

CR:483655

CR Number:   483655 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 3599 13 Nov 2007 Fixed Description If an application connected using a TDS based client, and attempted to use a procedure in the FROM clause of a SELECT statement, then the application would have failed with a TDS protocol error. This problem has now been fixed.

CR:483815

CR Number:   483815 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 3590 26 Oct 2007 Fixed 9.0.2 3577 26 Oct 2007 Fixed Description If a procedure that referenced proxy tables was used in the FROM clause of a SELECT statement, and the first statement in the procedure is not a SELECT statement, it was very likely that the server would have crashed. The problem may also happen if such a SELECT was used as the subselect in a DML statement. This has now been fixed.

CR:483845

CR Number:   483845 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 3590 29 Oct 2007 Fixed Description Statements referencing some specific forms of the LIKE predicate could have caused a server crash when the statement was prepared. This has been fixed.

CR:483913

CR Number:   483913 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 3582 08 Nov 2007 Fixed Description If a procedure, trigger, or view was created using EXECUTE IMMEDIATE, or via Sybase Central, a trailing semi-colon included at the end of the definition may not have been stripped out of the preserved source for the object, resulting in problems when the database was unloaded and reloaded. This has been fixed. Re-creating the object without specifying a trailing semi-colon will correct the problem. Workaround Description  There may be many including these ones I've found: 1 - reading the script [1.sql] with the java dbisql 2 - change the SQL for the trigger to have semi-columns after the <stmt\> and/or after the end-if 3 - possibly not using a SQL Batch but single statements in the use of EXEC. IMMED. 3b- possibly reorder the operations inside the batch so the trigger and parsing if-end-case is not exposed. 4 - and avoiding the use of a UNIX newline (linefeed/\x0a) as the line terminator altogether BUT the core failure is purely a function of the server and may crop up in other ways.

CR:483960

CR Number:   483960 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 3591 30 Oct 2007 Fixed Description In very rare circumstances, the server may have crashed if a fatal assertion was encountered during a backup. This has been fixed.

CR:483967

CR Number:   483967 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1257 12 Nov 2007 Fixed Description An OUTPUT...FORMAT FIXED statment, that did not include explicit column widths, could have created files that the INPUT statement could not have subsequently read correctly without also including explicit column widths. This would have occurred if the destination table contained a numeric data type (INT, DECIMAL, etc) in any column other than the last one. This has now been fixed.

CR:484003

CR Number:   484003 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 31 Oct 2007 Fixed Description If a proxy table to a table on a Microsoft SQL Server remote server had a a UUID column, attempting to insert a value generated by newid() into that column would have failed with a syntax error. This problem has now been fixed.

CR:484046

CR Number:   484046 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 3592 31 Oct 2007 Fixed Description Specific forms of the IN predicate could have caused the server to crash. This has been fixed.

CR:484054

CR Number:   484054 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 3595 06 Nov 2007 Fixed Description If a statement used the LOCATE() function on a long string, it could have lead to a reduction in concurrent execution of other statements. Further, it could have caused the statement to take a long time to respond to a cancel operation. Similarly, some queries that used a sequential scan with predicates that reject most of the rows in the table, might have taken a long time to respond to a cancel operation. These problems have now been fixed.

CR:484072

CR Number:   484072 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 01 Nov 2007 Fixed Description Some UPDATE and DELETE statements with aggregate expressions were incorrectly failing with the error "Invalid use of an aggregate function". This has been corrected.

CR:484074

CR Number:   484074 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 31 Oct 2007 Fixed Description A LIKE condition of the form: "column LIKE constant", could have produced incorrect results when the column was not of type CHAR and occurred as the first column of an index. This has been corrected.

CR:484145

CR Number:   484145 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 3597 08 Nov 2007 Fixed Description Using a host variable of type nchar, nvarchar or long nvarchar in a query that references proxy tables would likely have caused the server to report a syntax error, rather than execute the query. The server was not handling nchar based host variables correctly. It would at times assume the data was in the database charset instead of utf8 .This problem has now been fixed.

CR:484160

CR Number:   484160 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 3592 31 Oct 2007 Fixed 9.0.2 3579 31 Oct 2007 Fixed Description Attempts to revoke connect permission from a user that still had an externlogin mapped, would have failed with a strange foreign key error, after which, logging in as the user that was being dropped would have resulted in the user permissions being messed up. The server now properly gives an error indicating the externlogins are still mapped for the user and leaves the user permissions unchanged.

CR:484178

CR Number:   484178 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 3592 01 Nov 2007 Fixed Description Reloading histograms into a database using a 64-bit server may have failed if the database has been run previously with a 32-bit server. This has been fixed.

CR:484194

CR Number:   484194 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 3579 01 Nov 2007 Fixed Description When the server was run on HP-UX 11.00, HTTP connections may not have shut down cleanly, and the server may have hung on shutdown. The cause was a bug in the operating system. While there is no fix to ASA software, customers are advised to apply the HP-UX 11.00 patch PHNE_27886 or later (and all dependencies).

CR:484196

CR Number:   484196 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 01 Nov 2007 Fixed Description On Unix systems, transfers of large blobs to the server over TCP/IP may have been slower than expected. This would have been especially noticeable on 1 Gbps networks. This has been fixed.

CR:484256

CR Number:   484256 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 3592 01 Nov 2007 Fixed 9.0.2 3579 01 Nov 2007 Fixed Description Attempting to execute a query with an invalid dotted reference involving proxy tables, would very likely have caused a server crash. For example: select prod_id.sum(sales) from sales group by prod_id order by prod_id This query was intended to be "select prod_id, sum(sales) ..." but a typo replaced a comma with a period. If the table prod_id was a remote table, then the above mistyped query would have crashed the server. This problem has now been fixed.

CR:484262

CR Number:   484262 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 3592 02 Nov 2007 Fixed Description In very rare circumstances, the server may have issued a fatal checksum assertion for database page 0 while in the process of doing a backup. This has been fixed.

CR:484266

CR Number:   484266 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 01 Nov 2007 Fixed Description The QAnywhere Agent and MobiLink Listener could have crashed when started with the "@file" command line option, if "file" did not exist. This has been fixed.

CR:484269

CR Number:   484269 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 3592 01 Nov 2007 Fixed Description When run on Unix systems, the server could have exhibited poor disk I/O performance on mult-spindle disk systems. This has been fixed.

CR:484272

CR Number:   484272 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 01 Nov 2007 Fixed 9.0.2 3579 01 Nov 2007 Fixed Description The QATransactionalManager class would have failed to re-receive a message with large content (exceeding MAX_IN_MEMORY_MESSAGE_SIZE in size) after it was received once and a rollback was done. This problem applied to the C#, Java and C++ QATransactionalManager classes. This has now been fixed.

CR:484274

CR Number:   484274 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3599 13 Nov 2007 Fixed Description Attempting to execute a query using a window function with a PARTITION BY clause, that consisted of nothing but constants or variables, could have crashed the server. For example: create variable v int; select sum(x) over ( partition by v ) from t This has beenfixed.

CR:484281

CR Number:   484281 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 3592 02 Nov 2007 Fixed Description When sending an attachment over SMTP using xp_sendmail(), there would have been an extraneous zero length file with the same name sent along with the real file attachment. This has been fixed.

CR:484293

CR Number:   484293 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3592 02 Nov 2007 Fixed Description When using the QAnywhere Client SQL API to receive messages, they would not have been synchronized back to the originator. This caused the messages to remain in the "Pending" state indefinitally on the originating client, and on the server. This has now been fixed.

CR:484295

CR Number:   484295 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 3594 05 Nov 2007 Fixed Description If a synchronization model was used to create timestamp-based downloads with an Oracle consolidated database, and the MobiLink server used a different timezone than the consolidated database, then some data might not have been downloaded. The problem was that the trigger generated to maintain the last-modified time used CURRENT_TIMESTAMP, which uses the client's timezone. This has been fixed so that the generated triggers now use SYSTIMESTAMP (which uses the consolidated database's time zone.) A workaround is to manually change the trigger, either in a generated SQL file or deployed in an Oracle consolidated database.