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

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

CR:477367

CR Number:   477367 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3545 21 Aug 2007 Fixed 8.0.3 5570 23 Aug 2007 Fixed Description When download acknowledgement was enabled, the MobiLink client would have incorrectly failed to send a download ack for a synchronization if a previous synchronization during the same run had encountered a server side download error. As a result the server would report the following error: Error: Unable to read from the 'tcpip' network connection. Unable to read 2 bytes. Error: [-10034] No download confirmation from remote database This problem has been fixed

CR:477370

CR Number:   477370 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   MacOS Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3543 16 Aug 2007 Fixed Description When attempting to install an EBF on MacOS using the GUI installer, the installer would have prompted for an installation key and subsequently rejected any keys given. This has now been fixed. As a workaround, the command line installer can be used to apply EBFs on MacOS.

CR:477420

CR Number:   477420 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3551 24 Aug 2007 Fixed Description The behaviour of setting indicator variables when no rows were fetched was changed in the dblib library from that of previous versions. While the behaviour in this case was considered to be undefined, the behaviour has been reverted back to the original behaviour.

CR:477492

CR Number:   477492 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) 14 Aug 2007 Fixed Description Indexes on materialized views would not have been recreated by an internal rebuild, i.e., dbunload -ar or -an. A workaround is to do a two-stage rebuild; unload the database first to files, and then reload using the reload.sql script. This has been fixed.

CR:477494

CR Number:   477494 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 3551 20 Aug 2007 Fixed Description Stale materialized views were not used by the optimizer when the option materialized_view_optimization was set to STALE. This has been corrected. For further information on the option Materialized_view_optimization, please refer to the SQL Anywhere Server - Database Administration manual.

CR:477505

CR Number:   477505 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 3547 15 Aug 2007 Fixed Description The Unload utility (dbunload) can be used to unload materialized view data when given the command line options "-d -t <mat_view_name(s)>". The changes for Engineering case 469705 introduced a problem where data for materialized views was also being unloaded to disk during a "normal" unload. This has been fixed.

CR:477526

CR Number:   477526 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3542 15 Aug 2007 Fixed Description Applications running on HP-UX and using the iAnywhere ODBC Driver Manager, may have had connection attempts fail if the connection string contained non-ASCII characters. This would have been true for the MobiLink server, Remote Data Access connections and applications using the iAnywhere JDBC driver. This has been fixed.

CR:477617

CR Number:   477617 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 3596 07 Nov 2007 Fixed Description After running the Windows CE install on a Windows Vista system, immediately choosing to deploy to a Windows CE device would have caused the deployment install to crash with the following error: An error (-5011: 0x80040706) has occurred while running the setup. Please make sure you have finished any previous setup and closed other applications. If the error still occurs, please contact your vendor: Sybase, Inc. Spawning the CE deployment installer at the end of the CE Desktop install was unstable on Windows Vista. The deployment installer is no longer automatically deployed when installing on Windows Vista, but displays a message that deployment can be done by selecting "Deploy SQL Anywhere for Windows Mobile" from the Start menu.

CR:477637

CR Number:   477637 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 3548 17 Aug 2007 Fixed Description If the network connection to the primary server (S1) in a database mirroring system was lost, a failover to the mirror server (S2) would have occurred as expected. However, once the network connection was restored, S1 would have reported that its database files were incompatible with the current primary (S2). This has been fixed.

CR:477714

CR Number:   477714 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3549 17 Aug 2007 Fixed 9.0.2 3544 30 Aug 2007 Fixed Description The ALTER TRIGGER SET HIDDEN statement incorrectly removed the table owner from the create trigger statement stored in the catalog. As a result, the reload of a hidden trigger definition would have caused the SQL error: "Table ... not found", if the DBA user couldnot access the trigger without table owner. This has been fixed. In order to unload an existing database with this problem, the trigger definition will need to be recreated and then hidden first.

CR:477738

CR Number:   477738 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3531 20 Aug 2007 Fixed Description On Unix systems, the certificate utilities viewcert and createcert, were only being installed with ECC components and not with RSA components. Also, libdbcecc10_r.so, the new ECC support library for viewcert and createcert, was never installed at all. This has been fixed. On platforms where the utilities are supported, the EBF installer will now install viewcert and createcert if SQL Anywhere or MobiLink RSA libaries have been previously installed. The library libdbcecc10_r.so will be installed only if SQL Anywhere or MobiLink ECC libraries have been previously installed.

CR:477777

CR Number:   477777 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 3548 17 Aug 2007 Fixed Description When attempting to insert a value into a string column of a proxy table using a variable, there was a chance the value inserted may have been NULL. This problem only happened if the string column involved the evaluation of an expression (like concatenation). For example, the following should work fine: create variable v char(128); set v = 'abc'; insert into proxy_t(char_col) values(v); whereas, the following had a chance of inserting a NULL, instead of the concatenated value: create variable v char(128); set v = 'abc' || 'def'; insert into proxy_t(char_col) values(v); This problem has now been fixed.

CR:477892

CR Number:   477892 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3549 20 Aug 2007 Fixed 9.0.2 3544 20 Aug 2007 Fixed Description If an application was using the iAnywhere JDBC driver and called ResultSet.getBlob().getBytes() on a char, varchar or binary column that had an empty value in it, then the driver would have incorrectly returned null, instead of returning a 0-length byte [] value. This problem did not occur for empty long varchar or long binary columns. This problem has now been fixed.

CR:477918

CR Number:   477918 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 3549 20 Aug 2007 Fixed Description In a database mirroring system running in async mode, if a heavy volume of update activity occurred on the primary server for an extended period of time, the mirror server could have crashed as a result of running out of memory. This has been fixed.

CR:477995

CR Number:   477995 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 3550 20 Aug 2007 Fixed Description Attempting to run an archive backup (ie. BACKUP DATABASE TO ... ) would have caused a server crash if the database being backed up had no transaction log file. This has been fixed.

CR:478018

CR Number:   478018 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 3548 20 Aug 2007 Fixed Description The certificate utilities createcert and viewcert are now available on Mac OS X. They will be added if RSA components have been previously installed.

CR:478022

CR Number:   478022 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3550 20 Aug 2007 Fixed 9.0.2 3545 20 Aug 2007 Fixed Description Applying Microsoft's XML security patch KB 936181 (MSXML 4.0 dll version 4.20.9848.0) to Windows Vista systems, would have caused the UltraLite Load utility to crash. This problem does not show up on Windows XP. A work around has been implemented to prevent the crash.

CR:478055

CR Number:   478055 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 3558 11 Sep 2007 Fixed Description The server allows users to create temporary stored procedures that exist for the duration of the connection that creates the procedures. When creating these temporary stored procedures the server disallows the specification of an owner, i.e., temporary procedures are always owned by the user creating them. If a temporary procedure was referenced by ia qualified owner name in a query, the server would have failed to find the temporary procedure. The server now correctly finds qualified temporary procedures. A work around is to refer to temporary procedure by name only. Once a user had created a temporary procedure, the server would have allowed the creation of another temporary or permanent procedure by the same, resulting in duplicate procedures. The creation of duplicate temporary or permanent procedures is now not permitted. Note that the server already prevents the creation of a duplicate temporary or permanent procedure when the already existing procedure is a permanent one.

CR:478059

CR Number:   478059 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3550 21 Aug 2007 Fixed Description The UltraLite engine would have leaked process handles at a rate of one per client process per second. The engine was regularly opening a handle to each client process to determine if they were still running, but these handles were not being closed. These handles are now closed.

CR:478062

CR Number:   478062 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 3547 21 Aug 2007 Fixed Description On a busy server, it was possible that a failed HTTP connection may have caused the server to crash. This has been fixed.

CR:478064

CR Number:   478064 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 3547 22 Aug 2007 Fixed Description An HTTP request having multiple empty variables may not have always represented the variable as null, but sometimes as the empty string ''. This has been fixed.

CR:478072

CR Number:   478072 Product Name:   Mobilink Integration Product Component:   Deployment Status:   Closed OS:   Generic Original Version:   8.0 ebf 14516 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Sep 2007 Fixed Description ASA portaldatabase and mobilink services still use jconn2.jar

CR:478076

CR Number:   478076 Product Name:   Mobilink Integration Product Component:   Deployment Status:   Closed OS:   Generic Original Version:   8.0 ebf 14516 Fixed Version Build Resolution Date Closure Code (If Appropriate) 07 Sep 2007 Fixed Description The path to jconn3.jar should be included in the setenv.bat as CLASSPATH variable

CR:478153

CR Number:   478153 Product Name:   MobiLink Product Component:   QAnywhere 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 3576 26 Oct 2007 Fixed Description When the MobiLink server was running with QAnywhere messaging enabled and a JMS connector was configured and there is a high volume of JMS traffic between QAnywhere clients and a JMS system, the Java VM running in MobiLink would have used a continuously increasing amount of heap memory and may eventually have reached an out-of-memory condition. This has been fixed. Workaround Description  None available.

CR:478160

CR Number:   478160 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) 23 Aug 2007 Fixed Description The UNLOAD SELECT statement allows the INTO clause of the SELECT statement to be specified. However, the INTO clause is not meaningful in the context of the UNLOAD statement, and was being silently ignored. The use of the INTO clause in the UNLOAD SELECT statement will now generate a syntax error.

CR:478161

CR Number:   478161 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 3550 23 Aug 2007 Fixed Description On UNIX systems, if the primary and mirror servers were both run on the same machine and the environment variable SATMP either pointed to the same location for both, or was unset, the mirror server may have shut down with the error "The alternate server name provided is not unique". This would have occurred if the primary server was killed with the signal SIGKILL, or if it is brought down by an abnormal event, and it did not have a chance to delete temporary files. This has been fixed.

CR:478217

CR Number:   478217 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 3554 11 Sep 2007 Fixed Description Executing some simple forms of INSERT, UPDATE and DELETE statements could have caused the server to crash when used with particular host variable values. This has been fixed.

CR:478298

CR Number:   478298 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 3552 24 Aug 2007 Fixed Description When running the Unload utility on a database that was the primary site for a Sybase Replication Server, the REPLICATE ON clause was not being added to the ALTER TABLE and ALTER PROCEDURE statements in the reload.sql file. This has been fixed.

CR:478491

CR Number:   478491 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   AIX Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3575 09 Oct 2007 Fixed Description The MobiLink server would have crashed on startup when run on AIX 5.3 TL06 systems. This has now been resolved by having the installer turn off the execute bit on all shared objects on AIX so that the libraries will not be preload into the OS library cache.

CR:478498

CR Number:   478498 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 3535 23 Aug 2007 Fixed Description The optimizer relies on accurate statistics to generate efficient access plans. Statistics may be obtained from column and index statistics among other sources. Absence of good statistics can cause the optimizer to pick access plans that execute slowly causing complex queries to suffer. An improvement to the optimizer has been made so that the performance of complex queries with expensive table scans, under cetain circumstances, does not suffer even when good statistics are not available.

CR:478500

CR Number:   478500 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 3551 10 Nov 2008 Fixed Description The Swedish tailoring of the UCA collation did not conform to the 2005 standards of the Swedish Academy. In that standard, V and W were changed to be considered different characters at the primary level. To support this change a new tailoring has been implemented. To avoid incompatibilities with existing Swedish databases, the new tailoring was implemented as the "phonebook" sorttype variant of the Swedish UCA tailoring. For example: dbinit -zn UCA(locale=swe;sorttype=phonebook)

CR:478618

CR Number:   478618 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 3594 05 Nov 2007 Fixed 10.0.0 2890 05 Nov 2007 Fixed Description A server running a database that had handled more than roughly a billion transactions or snapshot scans in total since the database was created, could have failed assertion 201502 "inconsistent page modification value". A single query may start many snapshot scans, so the problem was much more likely if using snapshot isolation. The problem is now fixed. After the assertion, there was a very small chance of corruption that may be present even if the server reports a successful recovery. Therefore, validation is recommended. If problems are detected, then they should be handled with normal procedures (e.g. restore to backup, or attempt to salvage using an unload and reload with a server that has the bug fix). It is possible to check the value of the internal counter involved in the bug by starting a transaction and running the query "select start_sequence_number from sa_transactions()". It is best to upgrade to a fixed server regardless of the value, but a larger value indicates a workload that is more likely to eventually trigger the counter overflow that causes the problem.

CR:478654

CR Number:   478654 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 3553 29 Aug 2007 Fixed Description A blob column defined with the INLINE or PREFIX specification, with a size that was near the database page size, could have caused the server to crash. This problem would have only occurred if the INLINE or PREFIX specifier was within approximately 50 bytes of the database page size, and string data longer than that amount was inserted into the table. This has now been fixed.

CR:478704

CR Number:   478704 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3553 27 Aug 2007 Fixed Description When connecting to a MobiLink server via HTTP or HTTPS, the Monitor sent more HTTP or HTTPS requests than necessary. Excessive flushing caused most requests to be shorter than they should have been. This has been fixed.

CR:478752

CR Number:   478752 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 3553 27 Aug 2007 Fixed Description Cancelling a database validation could have caused the server to crash. The validation could have been issued from dbvalid, the Sybase Central plugin, or from the VALIDATE DATABASE statement. A crash from this problem would have been relatively rare, as it could only have happened during a relatively small window of opportunity within a validation, but would have been more likely in databases with many indexes per table. This has now been fixed.

CR:478909

CR Number:   478909 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 3553 29 Aug 2007 Fixed Description After having established a keep-alive connection from a browser request, a shutdown may have caused the server to crash. This is a timing issue that has only been seen when using Firefox. This has been fixed.

CR:478915

CR Number:   478915 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3554 30 Aug 2007 Fixed Description The server may have crashed, or failed assertion 101518, if an UPDATE statement contained multiple tables in the table-list, and columns from all the tables were set to the same expression. For example, in the following update the columns T1.b and T2.c are set to the same expression @val update T1, T2 set T1.b = @val, T2.c = @val where T1.a = T2.a This has been fixed.

CR:478925

CR Number:   478925 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3629 17 Jan 2008 Fixed Description When using the UltraLite Unload utility to unload an UltraLite database to SQL Statements, the owner would have been included in the CREATE PUBLICATION statement. The statement would not habe been valid syntax for UltraLite. This has been fixed.

CR:479032

CR Number:   479032 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3553 30 Aug 2007 Fixed Description When the UltraLite Synchronization utility's (ulsync) output was redirected to a file, and sync progress messages were requested with -v, those messages would not have been written on some patch levels of Windows Vista. Writes to standard output for the progress messages were being discarded when standard output of the owning executable (ulsync.exe) was not connected to a console. This has been fixed by using a callback function to report messages, rather than writing messages directly to stdout.

CR:479053

CR Number:   479053 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 3554 30 Aug 2007 Fixed 9.0.2 3549 26 Sep 2007 Fixed Description For some CPU bound queries, execution times could have been longer with Unix servers than execution times compared to an equivalent Windows server. This has been fixed.

CR:479061

CR Number:   479061 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 3554 30 Aug 2007 Fixed 9.0.2 3549 30 Aug 2007 Fixed Description Executing a DROP DATABASE statement could have caused a server crash or failed assertion if the database being dropped needed recovery. This has been corrected.

CR:479086

CR Number:   479086 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3554 30 Aug 2007 Fixed 9.0.2 3549 30 Aug 2007 Fixed Description When importing data into an existing table, the "Preview" table in the Import Wizard would have shown values in BINARY columns as "[B@" followed by up to 8 numbers and letters. The value from the file is now correctly displayed.

CR:479090

CR Number:   479090 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 3554 30 Aug 2007 Fixed Description When the MobiLink listener (dblsn) used both non-persistent connections (i.e. using -pc- switch explicitly) and confirmation, the notifier may have missed doing some fallback pushes when the listener was in the middle of confirming a previous notification. The problem has been fixed.

CR:479098

CR Number:   479098 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 3554 30 Aug 2007 Fixed Description When the HTTP server was under heavy load for a long period of time it was possible that it could have transitioned into a state where many contiguous requests were incorrectly rejected with a 503 error; 'Service Temporarily Unavailable'. This has been fixed, HTTP requests are now only rejected in this way when resources such as memory or licensing are unavailable.

CR:479191

CR Number:   479191 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 1869 25 Jun 2008 Fixed 10.0.1 3718 25 Jun 2008 Fixed 11.0.0 1413 13 Nov 2008 Fixed Description When SQL Remote was scanning the active transaction to determine which operations to send, it was possible for the process to have crashed when it had reached the end of the active transaction log. This has been fixed.

CR:479203

CR Number:   479203 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 3554 30 Aug 2007 Fixed Description The server could have crashed during recovery of a database that had gone down dirty while it was heavily-loaded. This has been fixed. The database file itself was not damaged and using an server with this fix will allow recovery to proceed.

CR:479204

CR Number:   479204 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 3554 31 Aug 2007 Fixed Description When request logging of plans was enabled, and a procedure that was being used in a query was dropped immediately before the cursor was closed, the server rare circumstances could have crashed. This has been fixed.

CR:479237

CR Number:   479237 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 3554 31 Aug 2007 Fixed Description The MobiLink server could have exhausted cache memory when multiple version 8.0 or 9.0 MobiLink clients were concurrently synchronizing large numbers of tables. The server could have crashed, or shut down with the message "Unable to allocate memory.". THis has now been fixed. Increasing the amount of cache memory using the -cm server option is a work around for this problem.

CR:479320

CR Number:   479320 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 3557 10 Sep 2007 Fixed Description On databases with multi-byte character sets, or when using multi-byte values (such as NCHAR), the string trim functions, trim(), ltrim() and rtrim() may have left blanks or extraneous bytes in the portion of the string that was intended to be trimmed. For this to have occurred, multi-byte characters must have appeared within the string data. This is now fixed.

CR:479327

CR Number:   479327 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 3560 13 Sep 2007 Fixed Description If an UPDATE statement on a view has more than one table expression in the update clause after view flattening, and the table expression that would have been updated is in the update clause preceded by a non-updatable table expression, then the UPDATE did not change any rows. Here are two examples: 1) This UPDATE statement has in its update clause first a non-updatable table expression V1 and then the updatable table T1. It does not update column "b" of table T1. update ( select sum(T2.c) as xxx from DBA.T2 ) as V1( xxx) ,T1 set T1.b = isnull(V1.xxx,0) where V1.xxx = T1.a and V1.xxx is not null and T1.a is not null 2) This UPDATE has two table expressions V1 and T1 in the update clause after view replacement of V11. If the order of the table expressions in the update clause is like in the example above, the UPDATE does not change any rows. create view V11 as select T1.b, isnull( V1.xxx, 0 ) as v2_2 from ( select sum(T2.d) as xxx from T2 ) V1 right outer join T1 on V1.xxx = T1 update V11 set b = v2_2 This problem has been fixed.

CR:479467

CR Number:   479467 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 3556 10 Sep 2007 Fixed Description Getting the query plan for a statement, using the SQL functions PLAN, EXPLANATION or GRAPHICAL_PLAN, could have caused the server to crashed if the plan for the statement had been cached. This has been fixed.

CR:479560

CR Number:   479560 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3514 10 Sep 2007 Fixed Description On RedHat Enterprise 5 systems with kernel versions prior to 2.6.21, if a SQL Anywhere executable crashed, the crash handler would have written a crash log, but it would have failed to write out a minicore dump. This issue has been fixed.

CR:479694

CR Number:   479694 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 3557 10 Sep 2007 Fixed Description The problems described in Engineering cases 468864 and 478161 (inability to reuse an alternate server name if a server using it terminated abruptly) may still have occurred on Unix operating systems. On Linux systems these problems could still have occurred when the file systems used were other than ext2 and ext3. This has been fixed

CR:479812

CR Number:   479812 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 3357 11 Sep 2007 Fixed Description If a manifest was installed in a JAR file, and then that JAR file was installed into a database, calling class.getPackage() would always have returned null, even though the package was properly defined in the manifest file. The class loader was reading the manifest file and defining packages via the parent class loader, but was incorrectly assuming that the parent class loader would keep track of the packages and handle the getPackage() call. The SA class loader now keeps track of all defined packages and handles the getPackage() call itself.

CR:479816

CR Number:   479816 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 3559 11 Sep 2007 Fixed 9.0.2 3556 11 Sep 2007 Fixed Description Executing a REORGANIZE TABLE could have caused the server to fail assertion 100701 - "Unable to modify indexes for a row referenced in rollback log -- transaction rolled back". This has been fixed.

CR:479825

CR Number:   479825 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 3558 11 Sep 2007 Fixed Description A number of problems with the UltraLite Database Initialization utility have been fixed. Default values were being wrapped in parentheses (), for example DEFAULT (0), which lead to sytax errors. Default valuess that start (after skipping white space) with open parentheses "(" and end with close parentheses ")", are now recognized and are automatically stripped. Specifying the clause DEFAULT getdate(*) also lead to a syntax error. All occurrences of "(*)" in DEFAULT strings are now replaced with "()". Previously, only DEFAULT NEWID(*) was being recognized, this change handles all such functions. Ulinit was failing to quote table names with leading underscore characters "--". The now(), current_timestamp(), and getdate() functions in DEFAULT strings are now replaced with the string "current timestamp". This is equivalent in operation and the only syntax that UltraLite supports. Added quoting to all uses of table names. Specifically the CREATE INDEX and ALTER TABLE ... ADD FOREIGN KEY statements were problematic. Ulinit was making use of NVARCHAR data types. nut UltraLite does not support this data type.

CR:479829

CR Number:   479829 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1010 24 Jan 2008 Fixed 10.0.1 3628 24 Jan 2008 Fixed Description Errors (like sticky I/O errors) reported while closing the connection would have had incomplete error messages (i.e. I/O failed for '-n/a-'). This has been fixed.

CR:479953

CR Number:   479953 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3559 11 Sep 2007 Fixed 9.0.2 3555 11 Sep 2007 Fixed Description A call to SADataReader.Read() could have caused an exception after calling SADataReader.NextResult(), if the resultset was empty. The SADataReader.Read() method was failing to check the resultset before fetching data. This problem has been fixed.

CR:479959

CR Number:   479959 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 3558 11 Sep 2007 Fixed Description The SORTKEY & COMPARE system functions did not support legacy ASA collations correctly. The following problems have been fixed. When the collation specification argument to the SORTKEY or COMPARE functions referred to a valid SQLAnywhere legacy collation, the server would silently use the UCA instead. For example, SORTKEY( 'a', '1252LATIN1' ) would generate the same result as SORTKEY( 'a', 'UCA' ). A small amount of memory would be leaked any time a connection was disconnected, provided that the connection had used SORTKEY or COMPARE at least once with a collation specification that was non-numeric and was not one of the built-in ASE compatibility labels. When an invalid collation specification was passed to the COMPARE function, the error message that was generated (INVALID_PARAMETER_W_PARM, error -1090) did not correctly substitute the collation specification. For example, COMPARE( 'str1', 'str2', 'invalidcollationlabel' ) would generate the message "Function 'compare' has invalid parameter '3' ('str2')". It now generates the message "Function 'compare' has invalid parameter '3' ('invalidcollationlabel')".

CR:479966

CR Number:   479966 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 3559 12 Sep 2007 Fixed Description The row limitation FIRST or TOP n may have been ignored, and more rows returned, if the select statement had an ORDER BY clause and all rows returned were equal with regard to the ORDER BY clause. This has been fixed. Workaround Description  Add DISTINCT

CR:480055

CR Number:   480055 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 3560 12 Sep 2007 Fixed Description In some circumstances, backups could have taken longer to complete than expected. This problem would have been noticed only if the total size of the database files was greater than 2GB, and was more likely to be noticed when backing up a very small fraction of that database size (e.g., such as when doing a TRANSACTION LOG ONLY backup with a small transaction log). This has been fixed.

CR:480072

CR Number:   480072 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 3564 19 Sep 2007 Fixed Description If a database was using a non-UCA collation (such as UTF8BIN) for NCHAR, the server could have produced unexpected results such as different orderings, or result sets, for the same data or corrupt indexes on NCHAR columns containing long strings. In some cases the server may have crashed if the query ran a sorting strategy. This has been fixed, but existing databases must be unloaded and reloaded. A new capability bit has been added so that databases created with the fixed engine cannot be started by servers without the fix. Applications can determine if a database has the fix by querying the new db_property( 'HasNCHARLegacyCollationFix' ). For servers released prior to this fix, this function will return NULL. For 10.x databases running on a server with this fix, this function will return 'On' if the database was created by an engine with the fix AND uses a legacy NCHAR collation. Otherwise, it returns 'Off'. For databases created after version 10, this function will return 'On'. This approach allows newly-created 10.x databases that use a UCA NCHAR collation to be started with older software. When the server starts a database that was created by a server released prior to this fix and the database uses a non-UCA NCHAR collation and has at least one table defined to use an NCHAR column, the following warning message will be displayed in the server's message window (the text & url are yet to be finalized): Warning: database \"%1\" is using an NCHAR collation which for which a fix has been made available. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/nchar_collation_warning.html Note that a database created by a server prior to this release could still have problems sorting NCHAR data if NCHAR uses a legacy collation but the warning is only displayed if NCHAR columns exist.

CR:480085

CR Number:   480085 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3560 12 Sep 2007 Fixed 9.0.2 3556 12 Sep 2007 Fixed Description If transaction log files for multiple databases were stored in a single directory, the MobiLink client dbmlsync might not have been able to synchronize any of these databases, even if there were no offline transaction log files for any of these databases. To resolve this, a new command line option has been added to dbmlsync: -do disable offline logscan (cannot use with -x) When this new option is used, dbmlsync will not attempt to scan any offline transaction logs. Therefore, dbmlsync with -do should be able to synchronize a database that is stored with all the other databases in a single directory, as long as this database does not have any offline transaction log files. However, if actual offline transaction log files are requested (for instance, if the minimum progress offset is located in an offline transaction log or if an uncommitted transaction starts from an offline transaction log), dbmlsync with -do will raise an error and refuse to run the synchronization.

CR:480103

CR Number:   480103 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 3569 27 Sep 2007 Fixed Description The server may have failed assertion 101412, as well as oither assertion errors, if the query contained a GROUP BY clause with a grouping expression of type char or varchar. For this probel to have occurred, the query must also have used an Indexed Group By, or the indexed grouping for a Hash Group By, as a low memory strategy; and during the grouping the group rows had to be updated (e.g. due to the LIST function). This has been fixed.

CR:480108

CR Number:   480108 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Sep 2007 DEFER Description Tested and reproduced with: ASA ADO.NET provider that comes with ASIQ 12.7 SDK ASA ADO.NET provider that comes with ASA 9.0.1, 9.0.2 and 9.0.3 - all providers produce same behavior Sybase IQ 12.6 ESD9 on Windows and Sun Solaris. Microsoft Visual Studio 2005 When running stored procedure from within VB application by using ASA ADO.NET Provider, an error "-180 - AsaError:Cursor not open" will happen. In Java ISQL, same procedure works fine.

CR:480125

CR Number:   480125 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 3560 13 Sep 2007 Fixed 9.0.2 3557 13 Sep 2007 Fixed 8.0.3 5575 13 Sep 2007 Fixed Description A database with a corrupt checkpoint log could have grown large during database recovery instead of failing with an assertion error. In some cases the database could have grown so large that a fatal error: disk full could have been caused. This type of corruption in the checkpoint log is now detected and assertion 201864 is raised in such an instance. This type of corruption is likely to be caused by a disk problem.

CR:480204

CR Number:   480204 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3564 14 Sep 2007 Fixed 9.0.2 3559 20 Sep 2007 Fixed Description If an application called the methods ResultSet.getTime(), ResultSet.getDate() or ResultSet.getTimestamp() using a java.util.Calendar object, then the iAnywhere JDBC driver would have returned the wrong result. This problem has now been fixed.

CR:480208

CR Number:   480208 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 3592 31 Oct 2007 Fixed 9.0.2 3578 31 Oct 2007 Fixed Description If a proxy table to a table on a Microsoft SQL Server remote server had a long character column, attempting to insert a string longer than 254 characters into that column would very likely have caused SQL Server to have returned a "partial update/insert" warning. This problem has now been fixed.

CR:480211

CR Number:   480211 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3560 12 Sep 2007 Fixed 9.0.2 3556 12 Sep 2007 Fixed Description When one connection was blocking on a WAITFOR statement, all other connections were also blocked until it finishes. This problem has been fixed.

CR:480217

CR Number:   480217 Product Name:   UltraLite Product Component:   UltraLite for M-Business Anywhere Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3557 11 Sep 2007 Fixed Description When using UltraLite database for M-Business Anywhere, MIMEList POD may be used to display data from the database in tabular format. The new feature is only intended to use with the MIMEList POD. Please note that it is not supporting the full AGDBSet attributes and methods. The following code snippets show the two ways to bind to the AGDBSet object: Example 1: Binding UltraLite table to AGDBSet connection = databaseManager.openConnection( openParms ); agdbSet = connection.getTableAGDBSet( "ULProduct" ); Example 2: Binding UltraLite result set to AGDBSet statement = connection.prepareStatement( "select prod_id, prod_name, price from ULProduct order by price" ); resultSet = statement.executeQuery(); agdbSet = resultSet.getAGDBSet();

CR:480317

CR Number:   480317 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3561 13 Sep 2007 Fixed Description The Server Licensing dblic may have crashed when it was asked to license the server executable instead of the corresponding license file. With the introduction of license files in 10.0.1, dblic now operates on the license file instead of the server executable file, but tries to automatically determine the name of the license file from the executable file name. In this case however the utility crashed while doing this. This has been fixed.

CR:480423

CR Number:   480423 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 3561 13 Sep 2007 Fixed 9.0.2 3557 13 Sep 2007 Fixed Description A query that involved more than one Remote Procedure Call in the FROM clause could have caused the server to crash. An example of such a query is: SELECT col1 from remote_procedure_1() where col2 = (select c1 from remote_procedure 2()) This problem has now been fixed.

CR:480434

CR Number:   480434 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3571 28 Sep 2007 Fixed Description The iAS ODBC driver for Oracle could have returned numeric data with a comma "," as the decimal point on some international installations if the Oracle database used commas as the decimal point. However, the MobiLink server is able to handle numeric data that uses commas as a decimal point for download, which would have caused it to abort the synchronization. This problem has now been fixed.

CR:480450

CR Number:   480450 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 3561 14 Sep 2007 Fixed Description The server may have crashed calling an external function using the old-style API, if that function attempted to return an unsupported data type. This has been fixed so that this situation will return the error "Expression has unsupported data type".

CR:480532

CR Number:   480532 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3562 14 Sep 2007 Fixed Description The QAnywhere server's logging mechanism was allocating a large amount of additional memory for each new client. This could have caused the Moblink server to run out of memory when working with a large number of clients. This has been fixed.

CR:480547

CR Number:   480547 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 3562 14 Sep 2007 Fixed Description If a scheduled event was created with a start time that included milliseconds, the event may have fired once, but then not have fired again. This has been fixed. As a workaround, the schedule's start time can be altered to exclude the milliseconds component.

CR:480659

CR Number:   480659 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3563 18 Sep 2007 Fixed 9.0.2 3558 18 Sep 2007 Fixed Description The Interactive SQL utility could have become unresponsive immediately after loading a .SQL file. This problem would have been very rare and timing-dependent, and would more likely have occurred on systems with fast processors. This has been fixed.

CR:480738

CR Number:   480738 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 Starting with version 10.0, the number of potential plans the optimizer can choose from has increased dramatically due to parallel access plan enumeration, and usage of materialized views. With very complex queries (joins of more than 20 tables), for which the optimizer enumerates parallel plans as well as non-parallel plans, the valid best plan may not have been found before pruning took place. This has been fixed.

CR:480759

CR Number:   480759 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3580 15 Oct 2007 Fixed 9.0.2 3569 15 Oct 2007 Fixed Description When making a call to a QAManager with the DBF and AutoStart connection parameters, the database server would not have been autostarted. Instead, a -101 error "not connected" would have been logged by the QAManager, but was not reported back to the application. It should be noted that a QAManager will autostart the database server when the Open method is called. The issue was that when the database server was shut down after Open had been called, then subsequent QAManager operations would have failed because the database connection had been terminated, but the error codes returned to the application do not indicate that the connection to the database was bad, thus not allowing the application to Close and Open the QAManager to recover from the error. This has been fixed. If the ErrorCode of a QAException is greater than or equal to 2000, then the error means the same as ErrorCode - 1000, and also that a database connection failure has occurred (ie. SQL Anywhere native code -101). When a database connection error is detected, it is possible to re-Open a QAManager without recreating it and setting its properties and message listeners again. This is done by calling Close() then Open() again. Note that the properties of the QAManager cannot be changed after the first Open() and subsequent Open() calls, and must supply the same acknowledgement mode.

CR:480776

CR Number:   480776 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 25 Sep 2007 Fixed Description Queries with access plans that did scans of unique indexes, may have returned incorrect results when using snapshot isolation. This has been corrected.

CR:480878

CR Number:   480878 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 3564 19 Sep 2007 Fixed Description Synchronization of a recreated database could have fail if the remote id was still the same. By default a new database will have a randomly generated UUID for a remote id. This has been fixed.

CR:480895

CR Number:   480895 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 3564 20 Sep 2007 Fixed 9.0.2 3559 20 Sep 2007 Fixed Description When registering the performance monitor counters DLL (dbctrs9.dll or dbctrs10.dll) manually from a non-elevated process on Windows Vista (eg, regsvr32 dbctrs10.dll), the performance counters may not have actually been registered correctly, even though regsvr32 reported that the dll was successfully registered. This problem has now been fixed. Note that the SQLAnywhere installation is performed from an elevated process and will not be affected by this bug.

CR:480937

CR Number:   480937 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3564 20 Sep 2007 Fixed 9.0.2 3559 20 Sep 2007 Fixed Description If an application using the iAnywhere JDBC Driver fetched an unsigned tinyint value in the range of 128 to 255, then the JDBC driver would have incorrectly thrown an overflow exception. This problem has been fixed by having the JDBC driver promote unsigned tinyint values to smallint.

CR:481000

CR Number:   481000 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 3568 21 Sep 2007 Fixed 10.0.0 2884 21 Sep 2007 Fixed 9.0.2 3561 21 Sep 2007 Fixed Description Borland Delphi converts an empty string parameter to a VARIANT type wide string with a NULL data pointer. When Borland Delphi was used with the SQL Anywhere OLE DB provider, this would have resulted in the application crashing. The following code fragment illustrates the situation. ADOQuery1.SQL[0] := 'select * from Customers where GivenName = :fname'; ADOQuery1.Parameters.ParamByName('fname').Value := ''; ADOQuery1.ExecSQL; This problem has been fixed. A null pointer passed to the provider for a parameter will now be treated as an empty string when passed to the database server.

CR:481017

CR Number:   481017 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 3564 20 Sep 2007 Fixed Description When run on Linux systems, the server may have displayed unpredictable behaviour involving scheduled events, mirroring, the request_timeout option, and possibly other functionality in the server that relied on timers at start-up. There was a greater probability of this occurring on multi-processor machines. This has been fixed.

CR:481022

CR Number:   481022 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 3566 20 Sep 2007 Fixed Description A Java mobile webservices application compiled with JDK 1.5 could have failed with an error at the server saying "'SOAP-ENV' is an undeclared namespace." This has been fixed. Note that because the mobile webservices runtime (iawsrt.jar) is built with JDK 1.5, Java mobile webservices applications must be compiled with JDK 1.5 and up as well.

CR:481036

CR Number:   481036 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) 25 Sep 2007 Fixed Description If a view's select-statement contained a key join and the same table was referenced multiple times, then attempting to query the view would have failed with a permissions error for users that only had select permission on the view. For example: A select on the following view may have failed with a permissions error for table T1: create view V1 as select * from T1 join T2, T1 join T3 This problem has been fixed. Workaround Description  I will notify the customer that a work around would be to add in the columns that the tables should be joined on.

CR:481099

CR Number:   481099 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 3592 30 Oct 2007 Fixed 9.0.2 3578 30 Oct 2007 Fixed Description If a server already had a database running, and that database was not the utility database, then attempting to connect to the utility database would have failed for a TDS based connection. This problem has been fixed. Workaround Description  As long as a connection remains open to the utility db, it will not shut down and can still be connected to. Therefore, if you create a dummy connection and leave it open, other connections can connect, do the work they need to do, and then disconnect freely. Another possible option would be to open one connection and leave it open until you are sure that the utility db will not be needed any more before closing it.

CR:481103

CR Number:   481103 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) 24 Sep 2007 Fixed Description Two new connection options have been added to allow connections to execute requests at different priority levels. The first option is Priority. This option sets the priority level at which requests from a connection are executed. This option can take one of the following values: CRITICAL HIGH ABOVE NORMAL NORMAL BELOW NORMAL LOW BACKGROUND By default, all connections will get a Priority value of NORMAL. Any user can set the Priority option without DBA permission. The second option is Max_Priority. This option controls the maximum priority level a connection can have. The default value for this option is NORMAL. Connections would needs DBA authority in order to change the Max_Priority option. A connection can always lower its priority level, but cannot raise it higher than the value of Max_Priority. An attempt to do so would raise a permission denied error. The scheduling semantic of the different priority levels allow all requests to get some CPU time despite the priority level of the request. Higher priority request will get more time slices than lower priority ones. Note, The Background_Priority option is deprecated as of this release. It will still be recognized but will be removed in future releases. Currently, if a users sets the Background_priority option to ON, it will cause requests to execute at the BACKGROUND priority level. When the option is turned back to FALSE, requests will execute at whatever value the option Priority is set to.

CR:481114

CR Number:   481114 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 3570 27 Sep 2007 Fixed 10.0.0 2884 27 Sep 2007 Fixed Description The server could have failed to report an I/O error, such as a full disk, when using asynchronous I/O on Linux kernels 2.6.12 and higher. This has been corrected.

CR:481125

CR Number:   481125 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 3603 13 Nov 2007 Fixed Description If an application was trying to fetch data from a char/varchar column through SQLGetData, and if the buffer size passed to SQLGetData was less than the length of the data that was to be fetched, the iAS ODBC driver for Oracle could have returned the total length of the data minus the length of a NULL terminator to the client in the last call to the SQLGetData function. This may have caused the application to report data truncation errors. This problem has now been fixed.

CR:481139

CR Number:   481139 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   5.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3560 24 Sep 2007 Fixed Description Renaming a table or view could have caused unpredictable behaviour if other parsed objects, such stored procedures, user-defined functions, or views, refered to the renamed object and parsed forms of these referencing procedures or views were already in server memory. The potential unpredictable behaviour would have included incorrect results, server faults, or server assertions. The server was failing to invalidate in-memory copies of parsed objects on a table or view rename. Now, parsed object definitions are unloaded and reloaded after the RENAME.

CR:481235

CR Number:   481235 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3568 24 Sep 2007 Fixed 9.0.2 3561 24 Sep 2007 Fixed Description The iAnywhere JDBC driver could have incorrectly given conversion errors when fetching numeric data. For the problem to have occurred, the numeric column had to follow a long char or varchar, or a long binary or long varbinary column in the result set. This problem was not likely to have occurred using the SQL Anywhere ODBC driver or the DataDirect ODBC drivers, but could have occurred using the iAywhere Oracle ODBC driver. The problem has now been fixed.

CR:481236

CR Number:   481236 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) 11.0.0 1070 28 Feb 2008 Fixed Description Verification of the MobiLink System Setup would have failed for varchar column length differences on a UTF8 Oracle database when the MobiLink System Setup was installed with nls_length_semantics='CHAR'. This has now been fixed by having the MobiLink System Setup set nls_length_semantics='BYTE' in the current session. Note that existing MobiLink System Tables that were installed with char length semantics will still not pass the check and upgrading will not fix the existing varchar columns.

CR:481254

CR Number:   481254 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3573 04 Oct 2007 Fixed Description An UPDATE statement would have updated only one row, even if more rows satisfied the WHERE conditions, if the column in the WHERE clause was indexed. For example, consider a table with the following schema: CREATE TABLE Tab1( pk int not null primary key, value varchar(1) not null ) CREATE INDEX val_index ON Tab1( value ) The following statement could possibly update more than one row: UPDATE Tab1 SET value = x WHERE value = y However, since there is an index on value, this update would have only updated at most one row. This has been fixed and it will now update all qualifying rows.

CR:481289

CR Number:   481289 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 3568 25 Sep 2007 Fixed Description Data retrieved into DT_NSTRING embedded SQL host variables were not blank padded for blank padded databases. This has been fixed.

CR:481415

CR Number:   481415 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Solaris Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3570 28 Sep 2007 Fixed Description Attempting to use the "-install" option in the Unix install would have resulted in the failure: Files missing or regkey invalid. This has now been fixed.

CR:481427

CR Number:   481427 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 a NULL for the parameter would have returned a random value instead of NULL. This has been corrected.

CR:481432

CR Number:   481432 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 3569 26 Sep 2007 Fixed Description The changes to the UltraLite runtime for Engineering case 480878, caused it to not send the upload progress in the first synchronization, which is what the MobiLink server expects. However, this change also caused the runtime to stopped sending the last download timestamp on the first synchronization as well. This resulted in the MobiLink server using a default timestamp of 0000-01-00 00:00:00.000000, which could be rejected by the consolidated database as an invalid timestamp. This has been fixed so that the runtime now sends the last download timestamp on the first synchronization, but not the upload progress.

CR:481450

CR Number:   481450 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) 10.0.1 3572 02 Oct 2007 Fixed 9.0.2 3564 02 Oct 2007 Fixed Description On Unix systems, if a client application left TCPip connections open when dblib, or the ODBC driver, was unloaded (for instance, at application shutdown time), the application may have crashed. There was a higher chance of seeing this on multi-processor machines. This has been fixed.