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

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

CR:484359

CR Number:   484359 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 05 Nov 2007 Fixed Description If a user was using the QAnywhere SQL API to receive messages asynchronously with the ml_qa_listen_queue procedure, and another user using the same message store sent a message to this queue (ie. local messaging), the message would not have been received. This has been fixed.

CR:484368

CR Number:   484368 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 3597 08 Nov 2007 Fixed 9.0.2 3582 08 Nov 2007 Fixed Description When attempting to unload and then reload a database created with an older build, using a more recent build, if the database had Remote Data Access servers defined, then there was a chance the reload could have failed with the error: "Server capability name 'encrypt' could not be found in the SYS.SYSCAPABILITYNAME table". This problem has now been fixed.

CR:484452

CR Number:   484452 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 3596 06 Nov 2007 Fixed Description It was possible for UltraLite to allow duplicate entries into unique key indexes, or it could have incorrectly reported a duplicate entry in a unique key. For this to have occurred, a table would need to have been left open while many hundreds of updates were happening to the same row, as well as many other inserts and deletes needed to occur to other tables concurrently. This is now fixed.

CR:484456

CR Number:   484456 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 3596 06 Nov 2007 Fixed Description When running on VMWare, the SQL Anywhere server may have crashed on start-up. There isn't a risk of database corruption. This was due to the server determining that the number of CPUs available was 0. This has been fixed.

CR:484461

CR Number:   484461 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) 06 Nov 2007 Fixed Description If both servers involved in a mirroring system have registered themselves with an LDAP server, the mirror server may not have successfully taken ownership of the database if the primary server failed. The transfer of ownership will succeed though, if the primary server is properly shut down; the problem only occurs if the primary server fails and does not shut down successfully. This has been fixed.

CR:484487

CR Number:   484487 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 06 Nov 2007 Fixed 9.0.2 3591 05 Dec 2007 Fixed Description On Solaris 10 systems, calling the system procedure xp_cmdshell() may have failed if the server's cache was large. This has been fixed. This problem still affects Solaris systems running version 8 and 9; as the problem arises from the implementation of the fork system call and cannot be worked around safely on Solaris versions 8 and 9. A more complete expalanation can be found at: http://developers.sun.com/solaris/articles/subprocess/subprocess.html.

CR:484542

CR Number:   484542 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 3581 06 Nov 2007 Fixed Description If a connection made DML requests against a JDBC class (ASAJDBC or ASEJDBC) remote server, and the disconnect performed an implicit rollback, then a small amount of the server's cache was not freed. This has been fixed.

CR:484543

CR Number:   484543 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 3581 06 Nov 2007 Fixed Description If a connection used a ASAJDBC or ASEJDBC remote server, and only performed CREATE TABLE AT statements against this remote server, then a small amount of the server's cache would not have been freed during the disconnect for this connection. This has been fixed.

CR:484605

CR Number:   484605 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3596 06 Nov 2007 Fixed 9.0.2 3581 06 Nov 2007 Fixed Description Under heavy load, and while another connection was executing DDL statements, calls to a user-defined function could have resulted in a server crash. This has been fixed.

CR:484679

CR Number:   484679 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 3597 07 Nov 2007 Fixed 9.0.2 3582 07 Nov 2007 Fixed Description The server could have crashed, or failed an assertion, when reloading a procedure. This could only have happened if another connection was unloading the procedure almost simultaneously. This has now been fixed.

CR:484698

CR Number:   484698 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 3603 07 Nov 2007 Fixed Description The index density calculation could have been incorrect in certain cases. This has now been corrected.

CR:484704

CR Number:   484704 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 3597 08 Nov 2007 Fixed Description On Linux IA64 systems, "unaligned access" messages may have appeared in the system log while the server was running. The problem that caused these messages has been fixed. The message itself can be considered harmless in this instance, and server operation was not affected.

CR:484798

CR Number:   484798 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 3597 09 Nov 2007 Fixed Description A query using a window function with a RANGE on a date column could have returned a conversion error. This has been fixed.

CR:484881

CR Number:   484881 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Jan 2008 DEFER Description When syncronizing a timestamp value in an UL database running on the desktop against an ASE server via Mobilink, the syncronization fails with an Error showed in the ML log: Error: Invalid datetime format.

CR:484889

CR Number:   484889 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3600 16 Nov 2007 Fixed Description Attempting to unload an UltraLite database while selecting a long list of tables to unload, would have caused Sybase Central to crash. This has been fixed.

CR:484960

CR Number:   484960 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 3600 16 Nov 2007 Fixed Description When any of the components in SQL Anywhere were converting a string from one character set to another, it was possible for the translated string to have been truncated in rare situations. For the problem to have occured, a multibyte character set other than UTF-8 was typically involved. The problem has now been fixed.

CR:484964

CR Number:   484964 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 3600 14 Nov 2007 Fixed 9.0.2 3585 14 Nov 2007 Fixed Description The command line option that represents a memory value, used by all the database tools including dbmlsync, dbremote, dbltm and the MobiLink Server, was not recognizing "g" and "G" as valid characters for a gigabyte of memory. This code is not used by the database server. This has been fixed, so that "1G" or "1g" can now be specify as a valid memory value. As a workaround, "1024M" can be used to represent a gigabyte of memory.

CR:484966

CR Number:   484966 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3599 13 Nov 2007 Fixed Description After connecting to a database containing a unique foreign key, selecting the Indexes folder in the tree would have displayed the error "The values <xxx> cannot fit into a byte" where <xxx> = 129 or 130. This has been fixed.

CR:484980

CR Number:   484980 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 3601 27 Nov 2007 Fixed Description The number of rows returned by a partial index scan of an unique index should be at most one row, if all the columns of the index are used in an equijoin predicate. This number was not being set correctly. This has been fixed.

CR:484981

CR Number:   484981 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 3599 12 Nov 2007 Fixed 9.0.2 3584 12 Nov 2007 Fixed Description If REORGANIZE TABLE was executed in one connection, while simultaneously dropping the primary key or clustered index on the same table in another connection, the server could have crashed. This has been fixed.

CR:484984

CR Number:   484984 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 an older version of either Open Client or jConnect, and then called the system procedure sa_conn_info, there was a chance the client would have crashed. Column names longer than 30 characters are a problem for older TDS clients. The problem has been fixed by properly aliasing the column names in the sa_conn_info select statement.

CR:485004

CR Number:   485004 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3599 14 Nov 2007 Fixed Description A constant at the start of an aggregate selection could have caused erroneous results. An example would be: SELECT 999, count(*) FROM TABLE where the incorrect result was a row for each row in the table, instead of a single row. Constants were not being marked as aggregates when they occurred in aggregate selections. This has been fixed.

CR:485054

CR Number:   485054 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 3616 14 Dec 2007 Fixed Description The optimizer attempts to use an existing index for queries involving the MIN or MAX aggregate function. The cost of this optimization was incorrectly overestimated for subqueries which could have been evaluated as derived tables, so it was possible that the subquery's best plan did not have the RowLimit operator, which may have resulted in the choice of a poor performing plan. This has been fixed. For example, the query: select * from R where R.X = (select max(R.X) from R ) would have had the cost of the plan "R<idx_x>:[ RL [ R<idx_x> ]]" overestimated by the optimizer. Hence, it was more likely to use "R<seq> JH [GrH [ R<seq>]]" as the best plan, which computed the subquery as a derived table. This plan may have been inefficient for queries where the table R was very large. Q: select * from R where R.X = (select max(R.X) from R )

CR:485073

CR Number:   485073 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 Attempting to createg a proxy table may have caused the server to hang. Restarting the server and running the create again would likely not reproduce the hang. This problem has now been fixed.

CR:485160

CR Number:   485160 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 3600 14 Nov 2007 Fixed 10.0.0 2891 14 Nov 2007 Fixed Description If a connection had snapshot isolation enabled, and a non-snapshot transaction was in progress, when a second connection with a snapshot or non-snapshot transaction commited or rolled back without any outstanding snapshot transactions having been started before the transaction in the first connection, then there was a chance of assertion failure 201501 "Page for requested record not a table page or record not present on page" on subsequent snapshot queries. This has been fixed.

CR:485191

CR Number:   485191 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 3600 15 Nov 2007 Fixed 10.0.0 2891 15 Nov 2007 Fixed Description When Snapshot isolation was enabled, pages in the temp file could have been leaked if long running snapshot transactions were used. This is has now been corrected.

CR:485200

CR Number:   485200 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 3600 15 Nov 2007 Fixed 9.0.2 3585 15 Nov 2007 Fixed Description When connecting to ASE or Microsoft SQL Server, the Remote Data Access layer was setting the quoted_identifier option to ON at connect time and then always quoting identifiers when querying data from ASE or SQL Server. Unfortunately, due to a restriction in the ASE server, always using quoted identifiers resulted in problems if the column name was 29 or 30 characters in length. Now, when connecting to ASE or SQL Server remote servers, the quoted_identifier option on the remote is set to match the local setting.

CR:485235

CR Number:   485235 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 3600 15 Nov 2007 Fixed 10.0.0 2891 15 Nov 2007 Fixed Description If a user-defined event executed a statement that referenced a proxy table while the database was being shutdown, the server may have failed an assertion. This has been fixed so that these statements now return an error.

CR:485242

CR Number:   485242 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3601 19 Nov 2007 Fixed 9.0.2 3585 19 Nov 2007 Fixed Description When using the Dbmlsync Integration Component, an exception could have occurred, or corrupt data could have been retrieved, if the UploadRow event or the DownloadRow event was enabled. For this to have occurred, the handler for the above event must have called the ColumnValue method on the IRowTransfer object more than once with the same index, and the index used must have corresponded to a column containing a string or BLOB value. This problem has now been fixed. A work around for this problem would be to ensure that the ColumnValue method is not called more than once for a single index by storing the value retrieved by the first call in a variable and working with that value.

CR:485252

CR Number:   485252 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 3601 27 Nov 2007 Fixed Description In some situations, the server could have crashed when executing a query access plan that was built with parallel scans. This has been fixed. A workaround for this problem is to set the option Max_query_tasks=1 to avoid all parallel access plans. That change will degrade performance for some queries, but will avoid the crash.

CR:485254

CR Number:   485254 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 3600 15 Nov 2007 Fixed Description When using the SQL Anywhere debugger to step through a procedure or function, if the current statement was an INSERT, UPDATE or DELETE, it was possible to step into the trigger that would have been fired when the statement executed, but if more than one trigger would have fired, it was not possible to step through to the next trigger if it existed. This has now been corrected.

CR:485262

CR Number:   485262 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1074 29 Feb 2008 Fixed 10.0.1 3651 03 Mar 2008 Fixed Description If the server crashed during application profiling and was then restarted, Sybase Central would have crashed on an attempt to connect to the restarted database. This has been fixed.

CR:485271

CR Number:   485271 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 3601 19 Nov 2007 Fixed Description For strongly encrypted databases, the statement ATTACH TRACING TO LOCAL DATABASE fails correctly with the SQL error "ATTACH TRACING TO LOCAL DATABASE cannot be used with a strongly encrypted database", but subsequent ATTACH TRACING statements incorrect returned the SQL error "A tracing connection is already active". This has been fixed.

CR:485275

CR Number:   485275 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3582 29 Nov 2007 Fixed Description The changes for Engineering case 482379 had the potential to truncate the .NET 2.0 machine.config file. This could have happened if the 9.0.2 EBFs for builds 3575, 3576 or 3581 were applied. Without this file, problems running .NET applications, or using Visual Studio 2005 may occur. The problem has now been corrected, and the Setup will try to determine if the machine.config file has been corrupted, and display an error dialog if corruption is found. If the new Setup reports that the file may be corrupt, action must be taken to restore the file to a working state. The file machine.config is an XML-formatted file, and is usually found in c:\Windows\Microsoft.NET\Framework\v2.0.50727\config. Data providers are listed in the <DbProviderFactories> sub-section of the <system.data> section of the file. A subset of the file is shown below: <configuration> (configuration for other providers) <system.data> <DbProviderFactories> <add name="Odbc Data Provider" invariant="System.Data.Odbc" description=".Net Framework Data Provider for Odbc" type="System.Data.Odbc.OdbcFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/> (configuration for other providers) <add name="SQL Anywhere Data Provider" invariant="iAnywhere.Data.AsaClient" description=".Net Framework Data Provider for SQL Anywhere" type="iAnywhere.Data.AsaClient.AsaFactory, iAnywhere.Data.AsaClient, Version=9.0.2.3585, Culture=neutral, PublicKeyToken=f222fc4333e0d400" /> </DbProviderFactories> </system.data> (configuration for other providers) </configuration> The bug was that the install truncated the file at the point where the "SQL Anywhere Data Provider" entry should have been added. This left the XML file in an inconsistent state, due to the <DbProviderFactories>, <system.data> and <configuration> sections not being closed. As well, entries that occurred after the <DbProviderFactories> section were missing entirely. Any data providers from other database vendors that were listed in the file after the SQL Anywhere provider would also have been deleted. To fix the problem, the file needs to be restored manually. Ideally, if there is a backup of this file, it can be restored from the backup. If that is not the case, the file will need to be manually edited to add the provider line above and close the <DbProviderFactories>, <system.data> and <configuration> sections. There is a file called machine.config.default in the same directory as the machine.config. This file contains the default settings for the machine.config, and can be used to restore the missing sections. Any installs for other products that modified the machine.config the file will also need to be rerun.

CR:485276

CR Number:   485276 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   7.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3600 15 Nov 2007 Fixed Description When a consolidated database was running on a DB2 or DB2 mainframe server, the MobiLink server, using the native IBM DB2 ODBC driver, may not have retried uploads when deadlocks occurred. This problem has now been fixed.

CR:485285

CR Number:   485285 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 3600 16 Nov 2007 Fixed Description Some memory could have been leaked by the MobiLink server when using non-persistent HTTP or HTTPS (persistent=0 at the client). The size of the leak was proportional to the number of HTTP GET requests, so large downloads would have caused greater leaks. A small leak could have occurred as well if a communication error occurred. The impact of the leaked memory could have included failed synchronizations and/or MobiLink server crashes. This has now been fixed.

CR:485293

CR Number:   485293 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) 11.0.0 1215 28 Apr 2008 Fixed 10.0.1 3685 28 Apr 2008 Fixed Description If diagnostic tracing was started using the Tracing Wizard in Sybase Central, and the connection string specified contained the tracing database's file name, the tracing database would not have been started, and the ATTACH TRACING statement would have failed. This has been fixed so that if the database file name is specified, the database will be started on the current server. The location of the database should be given relative to the database server location.

CR:485338

CR Number:   485338 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 3601 16 Nov 2007 Fixed 10.0.0 2891 16 Nov 2007 Fixed Description When running the server with the command line option -m "truncate transaction log after checkpoint", or when running the Backup utility dbbackup with its command line options that restart the log -r, -x or -xo, the current transaction log was renamed and then, depending on the option used, deleted. If the rename of the transaction log failed, assertion failure 100910 was raised. This message for this assertion has been changed to hopefully give more information about the cause. The message was changed from: "Error deleting transaction log file" to "Error renaming transaction log file before deleting it. Error code: %d/%d" The first number of the Error code means the error type (0 - POSIX error number, 1 - OS error number). On Unix and Netware, both error types mean POSIX error numbers. The second number is the actual error code. On Windows the POSIX error numbers can be found in the header errno.h.

CR:485349

CR Number:   485349 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 3601 20 Nov 2007 Fixed 9.0.2 3586 21 Nov 2007 Fixed Description Predicates of the form "column IS NULL" are eliminated if the column is declared NOT NULL earlier now in the optimization process. This increases the oportunity for rewrite optimizations to be performed.

CR:485377

CR Number:   485377 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 21 May 2009 Fixed Description When you create a synchronization model, if the generated event scripts have errors you are now warned right after the event scripts are generated at the end of the Create Synchronization Model wizard. If you try deploy a model that has event errors, you now get an error before the Deploy Synchronization Model wizard opens. In earlier versions you would not get an error until the end of the Deploy Synchronization Model wizard, in which case you would lose the choices you made in the wizard.

CR:485378

CR Number:   485378 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 3601 03 Dec 2007 Fixed Description In a mirroring system, if the transaction log files on the primary and mirror were incompatible, the mirror server may not have properly detected this condition and shut down. This has been fixed.

CR:485380

CR Number:   485380 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3603 21 Nov 2007 Fixed Description In the Create Synchronization Model wizard, if 'Download Subset by User or Remote ID' used a column in the same table, it would only have been enabled for tables where the column was also synchronized, and was a string type. This has been fixed. Now the column must only exist in the consolidated table. Note that the chosen column's type should be able to be implicitly compared with a string, or errors may occur when downloading with the generated download script.

CR:485425

CR Number:   485425 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 3602 19 Nov 2007 Fixed 9.0.2 3585 19 Nov 2007 Fixed Description When executing a query containing proxy tables that would normally have been handled in 'full passthru' mode, but cannot be handled by the server because it is too complex, would have crashed the server. This has been fixed so that the server now properly returns the error "-890: Statement size or complexity exceeds server limits".

CR:485478

CR Number:   485478 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3595 19 Nov 2007 Fixed Description Support has now been added to deploy native amd64/x64 ESQL and C++ applications to 64 bit Windows platforms (64 bit XP and later). The engine is supported, as well as static and dynamic versions of the in-process runtime library. Encryption is also supported, although FIPS is not. The following new files are included in the install: ultralite\x64 ultralite\x64\uleng10.exe ultralite\x64\ulstop.exe ultralite\x64\mlczlib10.dll ultralite\x64\mlcrsa10.dll ultralite\x64\mlcecc10.dll ultralite\x64\lib ultralite\x64\lib\vs8 ultralite\x64\lib\vs8\ulrt.lib ultralite\x64\lib\vs8\ulimp.lib ultralite\x64\lib\vs8\ulrt10.dll ultralite\x64\lib\vs8\ulbase.lib ultralite\x64\lib\vs8\ulrsa.lib ultralite\x64\lib\vs8\ulecc.lib ultralite\x64\lib\vs8\ulrtc.lib ultralite\x64\lib\vs8\ulimpc.lib ultralite\x64\lib\vs8\ulrtc10.dll

CR:485483

CR Number:   485483 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3605 21 Nov 2007 Fixed Description If an application used the iAnywhere ODBC driver for Oracle to fetch result set from a packaged procedure, the driver would have reported the following error: [Sybase][iAnywhere Solutions - Oracle][Oracle]ORA-06553: PLS-306: wrong number or types of arguments in call to {procedure name} This problem could have caused the MobiLink server to fail the download, when a download_cursor or download_delete_cursor event was written as: { call package_name.procedure_name ( ?, ?, ...) } or { call schema_name.package_name.procedure_name( ?, ?, ... ) } This problem has been fixed. Now this event can be written as: { call [schema_name.][package_name.]procedure_name( ?, ?, ... ) }

CR:485488

CR Number:   485488 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 3635 04 Feb 2008 Fixed Description The server could have crashed when requested to create a tracing database when using the Sybase Central Database Tracing wizard. This would have happened when the name of the DBA user for the tracing database was the same as a name of a DBA user in the existing database. The crash has been fixed. The workaround, and required behaviour with the fix, is to specify a DBA user name for the tracing database that does not currently exist in the target database. The wizard has been modified to alert the user to this. Workaround Description  Do not change the password to the encypted database.

CR:485498

CR Number:   485498 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 3605 22 Nov 2007 Fixed Description The REBUILD clause of the ALTER INDEX statement can be used to recreate the physical data structures underlying the index. If the ALTER INDEX REBUILD statement was interrupted by the user, or failed for any reason, the server could have left the physical structure in an undefined state. The most likely state for the index after a failure was to contain no entries. This situation could have caused subsequent queries using the faulty index to behave erroneously. To rectify this situation, a failed ALTER INDEX REBUILD could be executed again to completion. This has been fixed so that the server will now restore the physical data structures to the same state as the one that existed prior to execution of the failed statement.

CR:485499

CR Number:   485499 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 3603 21 Nov 2007 Fixed Description The server shares physical indexes between compatible primay keys, foreign keys, unique constrains and secondary indexes. Two indexes are considered compatible if the keys for the indexes contain exactly the same columns in the same order and with the same sequencing of values (ascending or descending). When creating a new foreign key index the server could have shared the physical index with an existing index erroneously even when the order of columns did not match. Note that the foreign key constraint was still correctly enforced, but the index was created with an unintended column order which may be problematic for queries that required the specified order for the index to be useful. This has now been fixed. A workaround is to create the other index after the foreign key index has been created, or to declare an additional index with the correct column order.

CR:485568

CR Number:   485568 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 22 Nov 2007 Fixed 9.0.2 3587 22 Nov 2007 Fixed Description Multi-threading applications could have failed with a number of symptoms. These symptoms include 'Resource governor for prepared statements limit exceeded' and 'Communication error' errors, as well as client application crashes. This problem has been fixed.

CR:485574

CR Number:   485574 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 3603 20 Nov 2007 Fixed Description The server could have crashed when attempted to get an exclusive schema lock on a table. This has been fixed.

CR:485576

CR Number:   485576 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 3588 30 Nov 2007 Fixed Description If the encrypt() or decrypt() functions were called a combined total of about 4 billion times, they would fail with the error 'Unable to load encryption dll ""'. This has been fixed.

CR:485584

CR Number:   485584 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 3603 20 Nov 2007 Fixed Description The Interactive SQL utility did not parse the "DESCRIBE objectName" statement correctly unless it was executed on its own, and not part of a sequence of statements. This has been fixed.

CR:485588

CR Number:   485588 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 3601 21 Nov 2007 Fixed Description The QAnywhere Agent could have used an excessive amount of memory during message transmission when a large number of messages were queued. This has been fixed.

CR:485593

CR Number:   485593 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 3613 11 Dec 2007 Fixed 9.0.2 3592 11 Dec 2007 Fixed Description The server could have become deadlocked while running concurrent REORGANIZE TABLE statements on the same table. There can now only be one REORGANIZE TABLE statement executing on a table at a time. Attempts to execute a second REORGANIZE TABLE on the same table will now result in the error SQLSTATE_REORG_ALREADY_IN_PROGRESS.

CR:485597

CR Number:   485597 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 3595 20 Nov 2007 Fixed Description The changes for Engineering case 480208 introduced a problem where attempting to insert a long varchar or binary value into a proxy table on 64-bit platforms could have crashed the server. This problem has been fixed.

CR:485629

CR Number:   485629 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3616 13 Dec 2007 Fixed Description Application Profiling did not provide trigger profiling information. This has been fixed.

CR:485689

CR Number:   485689 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 3611 04 Dec 2007 Fixed Description When attempting to insert a long binary column into a proxy table where the value being inserted was fetched from a local table, there was a chance the server could have hung with up to 100% CPU usage. This problem has been fixed.

CR:485700

CR Number:   485700 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 3605 22 Nov 2007 Fixed Description ALTER INDEX or DROP INDEX statements done while a transaction snapshot was active would always have failed with error -1062 "statement not allowed during snapshot". This has been fixed so that it does so now only if active snapshots remain after the commit that occurs at the beginning of these statements. Normally, this will only happen if there is a cursor opened "WITH HOLD" that is using a snapshot (either statement or transaction).

CR:485702

CR Number:   485702 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3621 03 Jan 2008 Fixed Description The server may have crash while attempting to execute a trigger that had a syntax error. This has been fixed.

CR:485725

CR Number:   485725 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3605 22 Nov 2007 Fixed 10.0.0 2891 22 Nov 2007 Fixed Description If a plug-in was registered using a JPR file that specified a directory in a different case than another registered plug-in that shares the same classloader, a warning was issued about the JAR file being different. This has been fixed.

CR:485799

CR Number:   485799 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 3605 23 Nov 2007 Fixed Description When undoing a failed ALTER TABLE or LOAD TABLE statement, the server could have become deadlocked. This has now been corrected.

CR:485802

CR Number:   485802 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 3605 23 Nov 2007 Fixed Description The query definitions of materialized views in SQL Anywhere are restricted from using certain SQL constructs. As an example, materialized views are prohibited from making references to user defined functions. The server was erroneously rejecting the creation of materialized views that make references to a table with computed columns when the definitions of the computed columns made use of a SQL construct that was not allowed within materialized view definitions. This has been corrected so that the creation of materialized views under these circumstances will no longer result in an error.

CR:485811

CR Number:   485811 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3611 05 Dec 2007 Fixed Description When the Interactive SQL utility dbisql was run as a console application with bad command line options, its return code was always zero. This has been corrected so that now it is 255, as documented: SQL Anywhere Server - Programming > Exit codes Software component exit codes

CR:485815

CR Number:   485815 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 3605 23 Nov 2007 Fixed Description The DATEADD() function did not detect overflow situations. This has been corrected.

CR:485816

CR Number:   485816 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 3608 26 Nov 2007 Fixed Description When using the version 10.0 provider to connect to an older database, if the application did not specify that the parameter.SADbType=SADbType.varchar (or .char), it would have defaulted to NVarChar. This would have resulted in the error 'not enough values for host variables' being returned to the application. This has been corrected so that the provider now maps NChar to Char, NVarChar to VarChar, LongNVarchar to longVarchar and NText to Text, if the server version is 9.

CR:485818

CR Number:   485818 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 3609 27 Nov 2007 Fixed Description The server could have become deadlocked when deleting rows from a table following the execution on an ALTER TABLE statement for a table that had foreign keys referencing that table. This has now been corrected.

CR:485821

CR Number:   485821 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 3612 07 Dec 2007 Fixed 9.0.2 3592 07 Dec 2007 Fixed Description In very rare circumstances, and only on Unix platforms, queries on a given table could have become very long running. The total query cost as reported by a graphical or long text plan of such slow queries, would have been reported as a negative number. This has been fixed. A workaround is to drop and recreate statistics on the table in question. Workaround Description  Drop and recreate statistics.

CR:485874

CR Number:   485874 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 3606 23 Nov 2007 Fixed 9.0.2 3587 23 Nov 2007 Fixed Description Calling the system procedure sa_send_udp() have could have caused the server to crash. This has been fixed.

CR:485875

CR Number:   485875 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 3611 04 Dec 2007 Fixed Description On some combinations of consolidated database and platform, any UUID values retrieved using the MobiLink Java direct row API could have had bytes swapped to the local machine byte ordering. This has been fixed. UUID values retrieved using the getBytes() function are now 16 byte values with the correct byte ordering. UUID values retrieved using the function getString() are strings in the correct UUID format (eg. "12345678-1234-5678-9012-123456789012"). Workaround Description  The uniqueidentifier field can be replaced by a VARCHAR(36) and still use DEFAULT NEWID(). This appears to work fine (although obviously, anything gained by using a uniqueidentifier column type will be lost)

CR:485878

CR Number:   485878 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Microsoft Windows NT Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3608 26 Nov 2007 Fixed Description If a remote database synchronized an NCHAR column that was included in multiple publications, or if a database initialized with a multi-byte character set synchronized a CHAR column that was included in multiple publications, then dbmlsync would have incorrectly reported that a column subset mismatch existed on the column in question. This has been fixed.

CR:485939

CR Number:   485939 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 3606 27 Nov 2007 Fixed 10.0.0 2892 27 Nov 2007 Fixed Description Backups of encrypted databases created by executing the BACKUP DATABASE statement with the "WITH CHECKPOINT LOG RECOVER" clause, may have contained pages that did not decrypt properly. This has been fixed. Note, any backups of encrypted databases using this clause should be considered invalid and recreated with an updated server.

CR:485979

CR Number:   485979 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3619 13 Dec 2007 Fixed 9.0.2 3597 13 Dec 2007 Fixed Description A procedure that was used in the FROM clause of a SELECT statement, may have returned the error "Derived table '<procname>' has no name for column 2". This would have happened if the SELECT statement in the procedure referenced a table without qualifying it with the owner, and only the procedure's owner could select from the table without a qualifying owner (i.e. not the user who executed the CREATE/ALTER PROCEDURE statement). This has been fixed.

CR:486050

CR Number:   486050 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 3608 27 Nov 2007 Fixed Description Logs created during the nonblocking_download_ack synchronization event were being logged with the logger source name of "ianywhere.unknown.category", instead of the remote id name of the client being synchronized as expected. This has been fixed.

CR:486053

CR Number:   486053 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 3606 10 Jan 2008 Fixed Description The server may have crashed if Java VMs from multiple connections attempted to call the same Java interface method for the first time. Due to the very small window where this could have occurred, it would have been exceptionally rare. This has been fixed.

CR:486059

CR Number:   486059 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 3608 27 Nov 2007 Fixed 10.0.0 2892 27 Nov 2007 Fixed Description Using AES_FIPS encryption for an extended period of time (eg. calling the encrypt/decrypt functions hundreds of thousands of times) could have caused the server to report an "out of memory" condition and shut down. This could also have ocurred when running an AES_FIPS-encrypted database. This has been fixed.

CR:486086

CR Number:   486086 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) 11.0.0 1518 16 Oct 2008 Fixed 10.0.1 3782 16 Oct 2008 Fixed 9.0.2 3739 16 Oct 2008 Fixed 11.0.1 1986 14 Nov 2008 Fixed Description Long exception message generated by the provider could have been truncated. This problem has been fixed.

CR:486223

CR Number:   486223 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 3609 29 Nov 2007 Fixed Description Some HTTP intermediaries can convert non-chunked HTTP or HTTPS requests into chunked requests. The MobiLink server currently cannot accept chunked requests, and would have crashed when it received them. This has been fixed so it will now fail the synchronization with the error "unknown transfer encoding" if it receives chunked requests. Note that this change only applies to the -x option, and not to the -xo option.

CR:486224

CR Number:   486224 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 3609 29 Nov 2007 Fixed Description Some HTTP intermediaries can inject a redundant User-Agent HTTP header, resulting in synchronizations failing. This is been fixed so that as long as the first User-Agent is the one the MobiLink server expects, it will allow the redundant header.

CR:486288

CR Number:   486288 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 3616 14 Dec 2007 Fixed 9.0.2 3594 14 Dec 2007 Fixed Description The best plan for a query block with a DISTINCT clause, and one or more joins, may be to use semijoins instead of inner joins based on the expressions used in the select list. Inner joins can be executed as semijoins for tables, derived tables, or views whose expressions are not used in the select list. The server will now make a cost-based decision to use inner joins or semijoins during the optimization phase

CR:486393

CR Number:   486393 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 3610 03 Dec 2007 Fixed 9.0.2 3591 03 Dec 2007 Fixed Description A query with an outer join could have caused the server to hang with 100% CPU usage. This has been fixed.

CR:486422

CR Number:   486422 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 3595 30 Nov 2007 Fixed Description The MobiLink server for Windows x64 now supports both RSA and ECC stream encryption. Note that the MobiLink server does not support FIPS-compliant RSA on Windows x64.

CR:486440

CR Number:   486440 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 3610 03 Dec 2007 Fixed 9.0.2 3590 03 Dec 2007 Fixed Description The server could have crashed when attempting to recover a database with a corrupted transaction log file. This has been fixed.

CR:486446

CR Number:   486446 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3610 03 Dec 2007 Fixed Description When running on a slow network, the MobiLink client dbmlsync could have reported 'Internal Error (1003)'. This problem has been corrected.

CR:486462

CR Number:   486462 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 3611 03 Dec 2007 Fixed 10.0.0 2893 03 Dec 2007 Fixed Description Database corruption could have occurred when execution of a LOAD TABLE statement into a table with existing data failed and rows were subsequently inserted or updated before a database restart. This has been fixed.

CR:486465

CR Number:   486465 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3610 03 Dec 2007 Fixed Description The installer for the SQL Anywhere Explorer SetupVSPackage.exe was failing to check if Visual Studio was installed before installing the integration package, leading to an exception. This has been corrected.

CR:486469

CR Number:   486469 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 3610 04 Dec 2007 Fixed 9.0.2 3590 04 Dec 2007 Fixed Description The Data adapter wizard would have shown errors when generating commands. The errors were cause by exceptions when executing a command which still had an open data reader. Fixed by using new commands.

CR:486476

CR Number:   486476 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 3615 12 Dec 2007 Fixed 9.0.2 3594 12 Dec 2007 Fixed Description Due to a memory leak, calling the the system procedure xp_sendmail() many times, could have caused the server to crash. The memory leak has been fixed, and xp_sendmail will now fail with the error "Insufficient memory" (return code 15), if memory does become exhusted.

CR:486531

CR Number:   486531 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3609 03 Dec 2007 Fixed 9.0.2 3589 03 Dec 2007 Fixed Description The SQL Anywhere Explorer now supports Visual Studio 2008. Registry settings for Visual Studio 2008 are now created, and the integration dll has been modified to support Visual Studio 2008. Note that assemblies built with Visual Studio 2005 can be used in Visual Studio 2008 as well.

CR:486539

CR Number:   486539 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 3620 20 Dec 2007 Fixed 9.0.2 3598 20 Dec 2007 Fixed Description A synchronization could have failed with the error: - Could not find subscription id for subscription of <ML user> to <publication>. or - SQL statement failed: (-101) Not connected to a database if all the following were true: 1) the synchronization was scheduled and the time before the next scheduled sync was more than a 2 minutes 2) for some row in the syssync table, "log_sent" was greater than "progress". (This occurs when dbmlsync sends an upload to the MobiLink server, but does not receive an ack/nack to indicate that the upload was applied to the consolidated database or not) 3) hovering was enabled This problem has now been fixed.

CR:486546

CR Number:   486546 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3611 03 Dec 2007 Fixed Description The Certificate Creation utility createcert allowed users to create certificates using ECC curves that were not supported by MobiLink or SQL Anywhere servers or clients. This has been fixed. The list of supported curves has been reduced to the following seven curves: sect163k1, sect233k1, sect283k1, sect283r1, secp192r1, secp224r1 and secp256r1.

CR:486554

CR Number:   486554 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 3611 04 Dec 2007 Fixed 9.0.2 3586 13 Dec 2007 Fixed Description The changes for Engineering case 485200 resulted in a bug where attempting fetch data from Micrsoft SQL Server or ASE could have failed with an "invalid object name" error. This problem has been fixed.

CR:486556

CR Number:   486556 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 3611 03 Dec 2007 Fixed Description When running on a slow network an UltraLite application could have failes with the error message 'Internal Error (1003)'. This problem has now been fixed. This change is similar to the fix for the MiobiLink client, Engineering case 486446.

CR:486561

CR Number:   486561 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 3592 05 Dec 2007 Fixed Description In some situations, if a keyset-driven cursor was used for a query that contained an IF or CASE expression in the select list, then the IF or CASE expression could have returned an incorrect answer. The answer would have been the expression evaluated for another row of the result set. This has been fixed.

CR:486574

CR Number:   486574 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3615 11 Dec 2007 Fixed Description When deploying a synchronization model, statements to create triggers did not specify the owner (or schema) for the trigger, so permission problems and invalid triggers could have resulted when deploying as a different user than the table owner. This has been fixed so that the owner, or schema, is now specified in the generated SQL for creating and dropping triggers for Oracle, Microsoft SQL Server, ASE and DB2 consolidated databases. In SQL Anywhere databases, a trigger is always owned by the same owner as the table, so the problem did not occur. A workaround is to deploy to a SQL file and manually edit the SQL.

CR:486579

CR Number:   486579 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 3611 04 Dec 2007 Fixed Description A MobiLink client, synchronizing via HTTP, that set the connection timeout to less than the default 240 seconds, could have been disconnected by the MobiLink server with a connection timeout error. This has been fixed.

CR:486656

CR Number:   486656 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 3612 07 Dec 2007 Fixed Description The execution of a LOAD TABLE statement would have caused the server to erroneously fire INSERT triggers declared on the table being loaded. This has been corrected, the server will no longer fire triggers when executing a LOAD TABLE statement.

CR:486744

CR Number:   486744 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 3605 08 Jan 2008 Fixed Description The server may have crashed or returned an unexpected error when attempting to execute an UPDATE statement on a table without the WAIT_FOR_COMMIT=ON clause, and that had a BEFORE UPDATE row level trigger, as well as an AFTER UPDATE row level trigger that used the OLD value of the columns. For this problem to have occurred the BEFORE UPDATE trigger must have changed the NEW value of a column that was not part of the updated columns in the UPDATE's SET clause, and the update operation must update some rows that violate referencial integrity. This has been fixed.

CR:486775

CR Number:   486775 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 3612 05 Dec 2007 Fixed 9.0.2 3592 05 Dec 2007 Fixed Description Executing a remote query that must be handled in no-passthrough mode, and that involved many tables, then there was a chance the query would have caused a server crash. Such crashes would have been more likely with databases that had a smaller page size. This problem has been fixed and the server will now properly give an error when a no-passthrough mode query with too many table nodes is executed.

CR:486777

CR Number:   486777 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 3618 13 Dec 2007 Fixed 9.0.2 3597 13 Dec 2007 Fixed Description In rare cases, opening a cursor on a procedure call or batch statement could have caused a server crash. This has been fixed.

CR:486788

CR Number:   486788 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 3612 07 Dec 2007 Fixed Description The changes for Engineering case 485499 introduced a bug which could have caused the server, under certain circumstances, to crash when creating a foreign key constraint. The problem has been fixed.