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

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

CR:367743

CR Number:   367743 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) 2928 24 Sep 2004 Fixed 9.0.2 2529 24 Sep 2004 Fixed 9.0.1 1925 24 Sep 2004 Fixed Description Attempting to use a view that referenced a proxy table, and contained a subselect which used an aggregate function, would have failed with the error "invalid use of an aggregate function". This has now been fixed.

CR:367764

CR Number:   367764 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2928 28 Sep 2004 Fixed 9.0.2 2529 28 Sep 2004 Fixed 9.0.1 1925 28 Sep 2004 Fixed 9.0.0 1367 28 Sep 2004 Fixed 8.0.3 5163 28 Sep 2004 Fixed 8.0.2 4478 28 Sep 2004 Fixed Description If the consolidated and remote databases had different collations, the MobiLink Synchronization server may not have respected the column width defined in the remote database for columns defined with char or varchar datatypes. This may have caused the ASA client to crash. Now, the MobiLink server will display an error, and abort the synchronization, if the length of the column value is greater than the column width defined in the remote database.

CR:367863

CR Number:   367863 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2933 12 Oct 2004 Fixed 9.0.2 2529 12 Oct 2004 Fixed 9.0.1 1930 12 Oct 2004 Fixed 9.0.0 1372 12 Oct 2004 Fixed Description If the EXECUTE IMMEDIATE statement was used to perform a CALL containing variables as procedure arguments, the parameter values would have failed to be passed to the called procedure. If the procedure contained OUTPUT parameters, the output variables would not be set when the procedure returned, or a "variable not found" error would have been reported. This has been fixed.

CR:367886

CR Number:   367886 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2929 28 Sep 2004 Fixed 9.0.2 2529 28 Sep 2004 Fixed 9.0.1 1926 28 Sep 2004 Fixed 9.0.0 1368 28 Sep 2004 Fixed Description Attempting to use the Proxy Table wizard to create a proxy table for a remote table that contained a column type not supported by Adaptive Server Anywhere, would have caused Sybase Central to display an internal error. Now, if an unsupported column type is encountered, the wizard restricts the selection of only those columns that are supported.

CR:367913

CR Number:   367913 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) 2929 28 Sep 2004 Fixed 9.0.2 2529 28 Sep 2004 Fixed 9.0.1 1926 28 Sep 2004 Fixed 9.0.0 1368 28 Sep 2004 Fixed Description On systems rinning Windows 95, 98, or ME, with the LDAP feature in use, the database server would have registered the invalid IP address "0.0.0.0" in LDAP, as well as the real machine's address. The list of IP addresses from these versions of Windows includes 0 (i.e. 0.0.0.0). This address is now ignored when creating the list for LDAP.

CR:367932

CR Number:   367932 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) 2929 29 Sep 2004 Fixed 9.0.2 2529 29 Sep 2004 Fixed 9.0.1 1926 29 Sep 2004 Fixed Description Ultralite Dynamic SQL would have failed to prepare a CREATE TABLE statement when one of the columns contained a partition size with a global autoincrement default. For example: CREATE TABLE tab ( rowid int not null primary key, col_a int default global autoincrement( 10000 ) ) This has now been fixed.

CR:367935

CR Number:   367935 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) 2929 28 Sep 2004 Fixed 9.0.2 2529 28 Sep 2004 Fixed 9.0.1 1926 28 Sep 2004 Fixed 9.0.0 1368 28 Sep 2004 Fixed 8.0.3 5164 28 Sep 2004 Fixed 8.0.2 4479 28 Sep 2004 Fixed Description When run on Unix systems, the server could have crashed when a non-DBA user was connected, if auditing was enabled. This has been fixed.

CR:367936

CR Number:   367936 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 2444 28 Sep 2004 Fixed 9.0.1 1926 28 Sep 2004 Fixed 9.0.0 1366 28 Sep 2004 Fixed Description Predicates of the form "constant IS NULL" may have been incorrectly evaluated as FALSE, for special constants such as "CURRENT REMOTE USER" or "CURRENT PUBLISHER". This has been fixed.

CR:367965

CR Number:   367965 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Linux Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2953 15 Nov 2004 Fixed 9.0.2 2452 15 Nov 2004 Fixed Description On Unix systems, the Data Source utility dbdsn uses the ODBCINI, ODBC_INI, ODBCHOME, and HOME environment variables when trying to find the .odbc.ini file, but if no such file was found, it was always created in the user's home directory. This has been fixed - the environment variables listed above will now be useed when creating the file. Workaround Description  Creating the file ahead of time to match the intended usage works but this is an enhancement suggestion. Maybe a new mnemonic switch like -i <path>/<ini_filename> can be added.

CR:368015

CR Number:   368015 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2930 29 Sep 2004 Fixed 9.0.2 2529 29 Sep 2004 Fixed Description The following changes have been made to generate correct values and foreign names in the output SQL stream: 1. UltraLite tables with TIME columns that defaulted to CURRENT TIME, or a specific date, was incorrectly generated. 2. A uniqueidentifier column that defaulted to NEWID was incorrectly generated as new_uuid. 3. Foreign key names were not being output in the ALTER TABLE ADD FOREIGN KEY statement.

CR:368023

CR Number:   368023 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2930 30 Sep 2004 Fixed 9.0.2 2529 30 Sep 2004 Fixed 9.0.1 1927 30 Sep 2004 Fixed Description Attempting to run dbconsol.nlm and connect to a server would have caused an abend. This has been fixed. NOTE: 6.x versions of dbconsol on all platforms fail to connect to servers after version 9.0.0 1223. This is still the case, and there is no workaround.

CR:368053

CR Number:   368053 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) 2930 01 Oct 2004 Fixed 9.0.2 2529 01 Oct 2004 Fixed 9.0.1 2529 01 Oct 2004 Fixed 9.0.0 1369 01 Oct 2004 Fixed 8.0.3 5165 01 Oct 2004 Fixed 8.0.2 4480 01 Oct 2004 Fixed Description If a client application terminated while the last connection to the server was in the process of being disconnected, the server may not have autostopped when it should. In these cases, the server icon and window would still have been active, and the database would have been stopped, but no connections could have been made to the server. Pressing shutdown would have stopped the server though. This problem has now been corrected. Note, this scenario could have occurred in a multithreaded application if all of the following conditions were true: - the server was autostarted by a multithreaded application - the main thread of the application signaled a child thread to shut down - the child thread did a disconnect as part of shutting down - the main thread did not wait for the child thread to complete before ending This has been fixed so that the server will correctly autostop.

CR:368116

CR Number:   368116 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 30 Sep 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1938 27 Oct 2004 Fixed Description If a stored procedure which returned a result set was called from within an atomic compound statement (i.e. BEGIN ATOMIC ... END), an error was correctly given, however, an assertion would result when the database was stopped, (Assertion 104301 - Attempt to free a user descriptor with non-zero reference count). This is fixed, the database will now shut down correctly.

CR:368127

CR Number:   368127 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2930 30 Sep 2004 Fixed 9.0.2 2529 30 Sep 2004 Fixed 9.0.1 1927 30 Sep 2004 Fixed 9.0.0 1369 30 Sep 2004 Fixed 8.0.3 5165 30 Sep 2004 Fixed 8.0.2 4480 30 Sep 2004 Fixed 7.0.4 3533 30 Sep 2004 Fixed Description If a remote server was created using one of the Remote Data Access ODBC classes, opening a cursor on a proxy tables from that server would have leaked about 8 bytes of memory for each remote column. Memory allocated at cursor open time, to hold the indicator for each column, is now freed when the cursor is closed.

CR:368160

CR Number:   368160 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2928 30 Sep 2004 Fixed 9.0.2 2442 30 Sep 2004 Fixed 9.0.1 1927 30 Sep 2004 Fixed Description Installing UltraLite .Net would have failed, if Visual Studio .NET 2005 (8.0) beta was already installed. Now the installer checks, and only installs the UltraLite.NET IDE integration component in the latest 7.x version of Visual Studio .NET. For example if Visual Studio .NET 2005 beta (8.0), Visual Studio .NET 2003 (7.1) and Visual Studio .NET (7.0) are installed, the UltraLite.NET IDE integration component will only be installed in Visual Studio .NET 2003 (7.1) .

CR:368164

CR Number:   368164 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2931 29 Sep 2004 Fixed 9.0.2 2529 29 Sep 2004 Fixed Description The Database Tools library has been reduced in size by approximately 272K.

CR:368167

CR Number:   368167 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2933 13 Oct 2004 Fixed 9.0.2 2529 13 Oct 2004 Fixed 9.0.1 1930 13 Oct 2004 Fixed Description When computing string functions that result in strings with lengths greater than the maximum allowed size of 2GB, the server could have wasted resources. As an example, the following code caused the server to compute a 24GB string before discarding the extra 22GB. begin declare foo long varchar; set foo = 'ABCDabcd'; set foo = repeat( foo, 49152); set foo = repeat( foo, 65536); end; The server will now stop the computation after the maximum allowed size of 2GB has been reached.

CR:368168

CR Number:   368168 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 2530 29 Sep 2004 Fixed 9.0.1 1928 29 Sep 2004 Fixed Description Error messages returned to applications connected to the server via TDS ( e.g. connections using jConnect ), would have been mangled when the OS character set and the client character set were different. The problem was caused by the header of the TDS error message having been mistakenly created in the OS character set, while the main body of the error message was in the client character set. The header is now also created in the client character set.

CR:368170

CR Number:   368170 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2931 01 Oct 2004 Fixed 9.0.2 2529 01 Oct 2004 Fixed 9.0.1 1928 01 Oct 2004 Fixed 9.0.0 1369 01 Oct 2004 Fixed Description When executing a READ statement with parameters, if the file being executed did not contain a PARAMETERS statement, but contained an identifier within braces, dbisql could have reported an internal error. This has been fixed.

CR:368231

CR Number:   368231 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2932 05 Oct 2004 Fixed 9.0.2 2529 05 Oct 2004 Fixed 9.0.1 1929 05 Oct 2004 Fixed 9.0.0 1371 05 Oct 2004 Fixed Description Executing an ALTER VIEW statement with a select statement that would have returned the warning "The result returned is non-deterministic." would have crashed the server. This has been fixed.

CR:368236

CR Number:   368236 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4485 22 Oct 2004 Fixed 8.0.3 5170 22 Oct 2004 Fixed 9.0.0 1375 22 Oct 2004 Fixed 9.0.1 1933 22 Oct 2004 Fixed 9.0.2 2529 22 Oct 2004 Fixed 2938 22 Oct 2004 Fixed Description In rare circumstances, if a database which required recovery was autostarted, the server could hang with the server window still minimized. One situation where this could have occurred was when the database had a "disconnect" event. A workaround is to start the database manually first to allow the database to recover, and then shutdown this engine. This issue has been fixed.

CR:368249

CR Number:   368249 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1376 22 Oct 2004 Fixed 9.0.1 1935 22 Oct 2004 Fixed 9.0.2 2529 22 Oct 2004 Fixed 2939 22 Oct 2004 Fixed Description In complex queries, if the optimizer found an expression (prefilter) that evaluated to FALSE, the optimization time may have been long. This has been fixed.

CR:368251

CR Number:   368251 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2933 12 Oct 2004 Fixed 9.0.2 2529 12 Oct 2004 Fixed 9.0.1 1930 12 Oct 2004 Fixed 8.0.3 5168 12 Oct 2004 Fixed 8.0.2 4482 12 Oct 2004 Fixed Description The server would have failed to return the result set under certain circumstances. One such situation was when the option Row_counts was set to 'ON' and the query access plan had an indexed sort node at the top. This problem has now been fixed.

CR:368274

CR Number:   368274 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) 2931 01 Oct 2004 Fixed 9.0.2 2529 01 Oct 2004 Fixed 9.0.1 1928 01 Oct 2004 Fixed 9.0.0 1369 01 Oct 2004 Fixed Description It was possible for the server to drop TLS connections, when under heavy load. Although rare, it was more likely to occur on a multi-processor machine. If the -z command line option, ("display debugging information"), was used on the server, a message indicating that a bad packet was received would have been displayed on the server console. This has been fixed.

CR:368348

CR Number:   368348 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2931 05 Oct 2004 Fixed 9.0.2 2529 05 Oct 2004 Fixed 9.0.1 1928 05 Oct 2004 Fixed Description Starting dbisql with the "-f" command line option to load a graphical plan file, could have caused it to hang on startup. The symptom was that the splash screen would open, but not close, and the main window would not open. This problem has now been fixed.

CR:368382

CR Number:   368382 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2930 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1928 27 Oct 2004 Fixed Description The QAnywhere Agent Stop utility, qastop, would have returned before the agent had terminated. This has been fixed, qastop now waits for the qaagent process to finish before returning. This allows more reliable control over starting and stopping the QAnywhere Agent under program control.

CR:368388

CR Number:   368388 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 27 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1933 27 Oct 2004 Fixed Description When the QAnywhere Agent was run on Windows CE systems with "automatic" policy, and was idle without any messages having been sent or received, subsequent messages would sometimes appear to be blocked due to the QAnywhere Agent not transmiting the message, even though the device was connected to a network. The problem could usually be worked around by shutting down the QAnywhere Agent, and restarting it while in network coverage. This has been fixed. Now, messages are sent as needed, with automatic policy.

CR:368459

CR Number:   368459 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1936 22 Oct 2004 Fixed 9.0.2 2529 22 Oct 2004 Fixed 2940 22 Oct 2004 Fixed Description A database used as the Replication Server stable queue database could not have been upgraded or unloaded. The RepServer system procedures were no longer executable by rs_systabgroup. This has been fixed.

CR:368475

CR Number:   368475 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5167 05 Oct 2004 Fixed Description Very occasionally, dbisql could have reported an internal error (NullPointerException) when scrolling down in the "Results" pane. This has been fixed.

CR:368540

CR Number:   368540 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3008 14 Jan 2005 Fixed 9.0.2 2551 14 Jan 2005 Fixed 9.0.1 1971 14 Jan 2005 Fixed 8.0.3 5203 14 Jan 2005 Fixed Description When used in Java Stored Procedures, cursors and prepared statements were left open until the connection disconnected. If called repeatedly, they could accumulate until a "resource governor exceeded error" occured. This has been fixed.

CR:368551

CR Number:   368551 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) 2932 05 Oct 2004 Fixed 9.0.2 2529 05 Oct 2004 Fixed 9.0.1 1929 05 Oct 2004 Fixed 9.0.0 1371 05 Oct 2004 Fixed 8.0.3 5167 05 Oct 2004 Fixed 8.0.2 4482 05 Oct 2004 Fixed Description The server could have crashed when executing Java code. This has been fixed.

CR:368574

CR Number:   368574 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed 9.0.1 1933 15 Oct 2004 Fixed 9.0.0 1375 15 Oct 2004 Fixed 8.0.3 5171 15 Oct 2004 Fixed 8.0.2 4485 15 Oct 2004 Fixed Description The execution of a SELECT statement containing JOINs of several tables by applications using the OLEDB provider ASAProv, would have resulted in a memory leak. This has been fixed. Workaround Description  None.

CR:368616

CR Number:   368616 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3534 22 Oct 2004 Fixed Description Complex grouped queries, using aliases in subqueries, may have returned incorrect results. This has been fixed. Workaround Description  Revert back to the ASA 7.0.4 GA build (#2788)

CR:368825

CR Number:   368825 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2936 13 Oct 2004 Fixed 9.0.2 2529 13 Oct 2004 Fixed 9.0.1 1932 13 Oct 2004 Fixed 8.0.3 5169 13 Oct 2004 Fixed Description If a datasource name was specified on the command line that contained an encrypted password, dbisql would not have immediately connected to the database, but would have first displayed the "Connect" dialog. Now an attempt is made to connect immediately, without first displaying the "Connect" dialog. Workaround Description  None short of 'clicking-through' or resorting to dbislqC

CR:368857

CR Number:   368857 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.1 3158 22 Oct 2004 Fixed 8.0.2 3601 22 Oct 2004 Fixed 8.0.3 5002 22 Oct 2004 Fixed Description If a hash join was performed when the server had a very small cache, an incorrect row could be returned. Subsequent fetches would then have failed with the error: -853 "Cursor not in a valid state" This has been fixed. Workaround Description  None acceptable to customer [at least not without an explanation].

CR:368951

CR Number:   368951 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Oct 2004 Not a Bug Description ASA901.1922. Error -946 "result set not permitted" only when using dbisql with iAnywhere jdbc driver. Ok if the dbisql connection uses Jconnect (option checked in advanced tab).

CR:368995

CR Number:   368995 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed 9.0.1 1933 15 Oct 2004 Fixed Description If a procedure contained a query that call the OPENXML() function, and the xpath expression was passed as a variable argument, the error "Feature 'OPENXML with non-constant query' not implemented" would have been reported reported on the 11th call. This has now been fixed.

CR:369013

CR Number:   369013 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) 2934 13 Oct 2004 Fixed 9.0.2 2529 13 Oct 2004 Fixed Description The connection properties IndAdd and IndLookup were always returning the value 0. This has been fixed. Note that the corresponding database properties returned the correct values.

CR:369016

CR Number:   369016 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2936 13 Oct 2004 Fixed 9.0.2 2529 13 Oct 2004 Fixed 9.0.1 1932 13 Oct 2004 Fixed 9.0.0 1373 13 Oct 2004 Fixed 8.0.3 5169 13 Oct 2004 Fixed 8.0.2 4484 13 Oct 2004 Fixed Description When an application using the OLEDB driver provided a DBTYPE_DECIMAL parameter with over 15 digits, the most significant digits would have been lost. For example, if the value 1234567890.123456 was provided as a DBTYPE_DECIMAL parameter, this would have been incorrectly interpreted as 234567890.123456 (the leading 1 would be lost). In particular, this could affect Visual Basic applications using an OleDbDataAdapter on a query with a numeric or decimal typed column, and a generated DataSet. The problem has now been fixed.

CR:369030

CR Number:   369030 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2936 12 Oct 2004 Fixed 9.0.2 2936 12 Oct 2004 Fixed Description If ulisql utility was configured to fetch all data for each column (i.e. not truncate values), attempting to execute a DDL statement after executing a query, would have resulted in the error A schema upgrade is not currently allowed. This has been fixed.

CR:369054

CR Number:   369054 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) 2936 13 Oct 2004 Fixed 9.0.2 2529 13 Oct 2004 Fixed 9.0.1 1932 13 Oct 2004 Fixed Description Under some conditions when the results of a sort did not fit entirely in memory, the sort could have returned rows that were only partially ordered. This has been fixed.

CR:369072

CR Number:   369072 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2939 25 Oct 2004 Fixed 9.0.2 2529 25 Oct 2004 Fixed 9.0.1 1935 25 Oct 2004 Fixed 9.0.0 1376 25 Oct 2004 Fixed 8.0.3 5172 25 Oct 2004 Fixed 8.0.2 4487 25 Oct 2004 Fixed Description When using the OLEDB provider ASAProv, String parameters may not have been passed correctly to stored procedures. This problem has been fixed. The following Visual Basic example calls a stored procedure with a String parameter. Dim sendParam1 As String sendParam1 = "20040927120000" Dim cmd As ADODB.Command cmd = New ADODB.Command With cmd .CommandText = "testproc1" .CommandType = ADODB.CommandTypeEnum.adCmdStoredProc .ActiveConnection = myConn .Prepared = True .Parameters(0).Value = sendParam1 Call .Execute() End With An example of a stored procedure follows. ALTER PROCEDURE "DBA"."testproc1" (in param1 varchar(30)) BEGIN message 'in Parameter [' + param1 + ']'; END

CR:369122

CR Number:   369122 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2936 14 Oct 2004 Fixed 9.0.2 2529 14 Oct 2004 Fixed 9.0.1 1932 14 Oct 2004 Fixed 9.0.0 1374 14 Oct 2004 Fixed 8.0.3 5170 14 Oct 2004 Fixed 8.0.2 4484 14 Oct 2004 Fixed Description The server may have exhibited poor performance if many connections try to concurrently truncate a global temporary table. This was due to each connection attempting to acquire an exclusive lock on the global temporary table definition. Since each connection already has a pointer to the table definition, acquiring an exclusive lock is no longer done.

CR:369145

CR Number:   369145 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2936 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed Description When launched from Sybase Central, dbisql would have connected to the wrong database, if Sybase Central was connected to two (or more) databases and a dbisql session had already been opened and was connected to one of the databases. Subsequent attempts to launch dbisql from Sybase Central would have always connected to whatever database the initial dbisql session was connected. Now, dbisql will reliably connect to the appropriate database.

CR:369150

CR Number:   369150 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2936 14 Oct 2004 Fixed 9.0.2 2529 14 Oct 2004 Fixed 9.0.1 1932 14 Oct 2004 Fixed 8.0.3 5281 29 Jul 2005 Fixed Description If the server command line passed to the Spawn utility dbspawn contained the @filename option, dbspawn would have expanded the contents of the file and then spawned the server. This meant that the server command line would have included the contents of the file. If the file contained certificate passwords or database encryption keys, they would then be visible through the 'ps' command or equivalent. This has been changed, dbspawn will no longer expand the @filename parameter.

CR:369170

CR Number:   369170 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed Description When connected via jConnect, dbisql could have incorrectly reported that the connection to the server was lost if a statement which caused a data conversion error was executed, e.g. "select STRTOUUID ('12345678-1234-5678-9012-123456789012')". Now, the data conversion error will be reported, but an error that the connection has been closed will not.

CR:369234

CR Number:   369234 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5170 15 Oct 2004 Fixed 8.0.2 4485 15 Oct 2004 Fixed Description The server may have occasionally appeared to temporarily hang with CPU usage at 100%. This would have occurred when there were only a few pages of the server's cache available for reuse. The server would have continually reused these few pages rather than immediately grow the cache. This problem has been corrected.

CR:369238

CR Number:   369238 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4487 19 Oct 2004 Fixed 8.0.3 5172 19 Oct 2004 Fixed 9.0.0 1376 19 Oct 2004 Fixed 9.0.1 1935 19 Oct 2004 Fixed 9.0.2 2529 19 Oct 2004 Fixed 2939 19 Oct 2004 Fixed Description If the schema of a table outside of a publication was altered (for example, table "t1"), and a synchronizing table existed, whose name started with this table's name (for example, table "t1_synch"), that had outstanding changes to synchronize, then dbmlsync would incorrectly report that the schema of the synchronizing table had been altered outside of synchronization. This has now been fixed. Workaround Description  Two workarounds: - isolation of schema changes with the -i switch in dbmlsync. - renaming the tables if possible

CR:369272

CR Number:   369272 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed 9.0.1 1933 15 Oct 2004 Fixed 9.0.0 1375 15 Oct 2004 Fixed 8.0.3 5171 15 Oct 2004 Fixed 8.0.2 4485 15 Oct 2004 Fixed Description A call to IRowsetChange::InsertRow() in the OLEDB provider, ASAProv, results in a crash. This call can be made from C++ using a simple table insert: CTable<CAccessor<CSimpleAccessor> > dbSimple; hr = dbSimple.Insert(1); This problem has been fixed.

CR:369273

CR Number:   369273 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed Description When used in Ultralite Dynamic SQL the SWITCH-CASE expression could have caused memory to be over-written. This has now been fixed.

CR:369275

CR Number:   369275 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) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed 9.0.1 1933 15 Oct 2004 Fixed Description Executing a query that used two or more derived tables which each called the OPENXML function, one of which contained an illegal XPATH expression, could have caused the server to crash. This has been fixed.

CR:369278

CR Number:   369278 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2937 15 Oct 2004 Fixed 9.0.2 2529 15 Oct 2004 Fixed 9.0.1 1933 15 Oct 2004 Fixed 9.0.0 1374 15 Oct 2004 Fixed 8.0.3 5170 15 Oct 2004 Fixed 8.0.2 4485 15 Oct 2004 Fixed Description The stored procedure sp_jdbc_stored_procedures is used by jConnect to retrieve stored proc metadata. Unfortunately the definition of the stored procedure was incorrect and the PROCEDURE_TYPE column of the metadata result set was returning whether or not the particular stored proc returned a result set. In actuality, the PROCEDURE_TYPE column should return whether or not the particular stored proc returns a return value. This procedure has now been corrected. Note, new databases will have the corrected procedure, but to update existing databases, run the Upgrade utility dbupgrad.

CR:369335

CR Number:   369335 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) 2937 15 Oct 2004 Fixed 9.0.2 2451 15 Oct 2004 Fixed Description When the server was running on Windows NT 4 systems, the lookup of integrated login groups could have failed if the integrated_login_servername did not begin with two back-slashes "\\". The server will now add two back-slashes to the beginning of the domain servername if necessary.

CR:369410

CR Number:   369410 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) 8.0.2 4485 21 Oct 2004 Fixed 8.0.3 5171 21 Oct 2004 Fixed 9.0.0 1375 21 Oct 2004 Fixed 9.0.1 1933 21 Oct 2004 Fixed 9.0.2 2529 21 Oct 2004 Fixed 2937 21 Oct 2004 Fixed Description If a stored procedure was dropped and then another stored procedure with the same name was immediately created, users who had permission to access the first procedure, and had already called it, will still have been able to access the second procedure, even if they have not explicitly been given permission, until the next time the database was stopped. This has been fixed.

CR:369479

CR Number:   369479 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4486 21 Oct 2004 Fixed 8.0.3 5172 21 Oct 2004 Fixed 9.0.1 1934 21 Oct 2004 Fixed 9.0.2 2451 21 Oct 2004 Fixed 2938 21 Oct 2004 Fixed Description The MobiLink server could have crashed if all the following had occured on the same worker thread: - an error was handled on upload on the last table - a download cursor was opened for the first time on any table - a subsequent sync used the download table script without having an upload error handled, and there were multiple rows to download This is now fixed.

CR:369491

CR Number:   369491 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4486 21 Oct 2004 Fixed 8.0.3 5172 21 Oct 2004 Fixed 9.0.0 1376 21 Oct 2004 Fixed 9.0.1 1934 21 Oct 2004 Fixed 9.0.2 2529 21 Oct 2004 Fixed 2938 21 Oct 2004 Fixed Description When running on Unix systems, the Interactive SQL utility dbisql, would have displayed the usage message when a full path to a SQL script file was given. The leading '/' was was being interpreted as a command line switch on. This has been fixed.

CR:369516

CR Number:   369516 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 21 Oct 2004 Fixed 2939 21 Oct 2004 Fixed Description The Interactive SQL utility dbisql, could have prompted for a seemingly unnecessary second log in, if all of the following were true: - DBISQL was running as a windowed application - not all the connection parameters were supplied on the command line, or in the SQLCONNECT environment variable, to complete the connection - the "Connect" dialog was opened automatically when DBISQL started - the connection was to a slow server This has been fixed.

CR:369521

CR Number:   369521 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5172 21 Oct 2004 Fixed 9.0.0 1376 21 Oct 2004 Fixed 9.0.1 1934 21 Oct 2004 Fixed 9.0.2 2529 21 Oct 2004 Fixed 2938 21 Oct 2004 Fixed Description If the GetCurrentCommand method of the ICommandPersist interface was called, the memory heap could have been corrupted. This problem has been fixed.

CR:369536

CR Number:   369536 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 2529 21 Oct 2004 Fixed 2934 21 Oct 2004 Fixed Description When initializing a database, filenames were added to the SYSFILE system table in the OS character set. The filenames are now added to the SYSFILE system table using the database character set.

CR:369539

CR Number:   369539 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 21 Oct 2004 Fixed 2940 21 Oct 2004 Fixed Description If the engine name in the OS charset (ie ENG= )was not identical to the engine name in the database charset, then dbunload -an could have failed with an error such as "SQL Error: Invalid database server command line". This has now been fixed.

CR:369676

CR Number:   369676 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1935 20 Oct 2004 Fixed 9.0.2 2529 20 Oct 2004 Fixed 2939 20 Oct 2004 Fixed Description The server allowed system datatypes, such as MONEY and UNIQUEIDENTIFIERSTR, to be dropped using the "DROP DATATYPE" statement. An attempt to drop these datatypes will now be rejected with a "permission denied" error.

CR:369692

CR Number:   369692 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 2529 20 Oct 2004 Fixed 2939 20 Oct 2004 Fixed Description Internally, the value of the server's name is stored in the OS's character set. When the Transact-SQL variable @@servername was used in a query, it was not converted to the database's character set and as a result, comparisons could have been incorrect. If the value was returned to a client, the name could have been mangled by going through an incorrect character set translation (db charset to client charset for a string that was in server OS charset). The property( 'name' ) function which returns the same value was already correct. This bug affected the title bar of the dbisqlc window. The problem has now been fixed.

CR:369704

CR Number:   369704 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.2 4487 20 Oct 2004 Fixed 8.0.3 5173 20 Oct 2004 Fixed 9.0.0 1377 20 Oct 2004 Fixed 9.0.1 1935 20 Oct 2004 Fixed 9.0.2 2529 20 Oct 2004 Fixed 2939 20 Oct 2004 Fixed Description When filling a DataSet using the ASADataAdapter object, the AutoIncrement property of DataColumn was not set properly. This has now been fixed.

CR:369735

CR Number:   369735 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 21 Oct 2004 Fixed 2941 21 Oct 2004 Fixed Description Executing a statement with an error and then switching to the Plan tab, would have caused ULISQL to crash. This has been fixed.

CR:369796

CR Number:   369796 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1936 21 Oct 2004 Fixed 9.0.2 2529 21 Oct 2004 Fixed 2940 21 Oct 2004 Fixed Description The ReplyToAddress and InReplyToID properties were not being mapped properly when a message crossed between QAnywhere and JMS. If a QAnywhere generated message was sent to a JMS client via the QAnywhere JMS connector, any ReplyToAddress specified on the QAnywhere message (using setReplyToAddress() in C++ or the ReplyToAddress property in C#) was mapped over to the JMS property QAReplyToAddress. This differed from the documentation, which indicated that the ReplyToAddress was mapped to the JMS property ias_ReplyToAddress. Similarly, the InReplyToID specified on the QAnywhere message (using setInReplyToID() in C++ or the InReplyToID property in C#) was mapped over to the JMS property QAInReplyToID rather than the documented ias_InReplyToID. If a JMS message was sent to a QAnywhere client via the QAnywhere JMS connector, the JMSReplyTo specified on the JMS message (using setJMSReplyTo()) was mapped over to the QAMessage property ias_ReplyToAddress rather than to the actual ReplyToAddress of the message. Hence the ReplyToAddress could not be accessed by calling getReplyToAddress() in C++ or the ReplyToAddress property in C#. Similarly, the JMSCorrelationID specified on the JMS message (using setCorrelationID()) was mapped over to the QAMessage property ias_InReplyToID rather than to the actual InReplyToID of the message. Hence the InReplyToID could not be accessed by calling getInReplyToID() in C++ or the InReplyToID property in C#. This problem has been fixed to behave as documented.

CR:369811

CR Number:   369811 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 2529 21 Oct 2004 Fixed 2940 08 Nov 2005 Fixed Description A database server using SPX would have started up successfully even if another server running SPX was already running with the same name. This has been fixed so that the server will now correctly detect that an another SPX server is already running with the same name and fail to start.

CR:369842

CR Number:   369842 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows NT Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.0 1377 22 Oct 2004 Fixed 9.0.2 2529 22 Oct 2004 Fixed 2940 22 Oct 2004 Fixed 9.0.1 1936 22 Oct 2004 Fixed Description On Windows systems, the Data Source utility dbdsn, would not have listed all of the data sources if the total length of all of the names exceeded about 1024 bytes. This has been fixed.

CR:369956

CR Number:   369956 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 2529 22 Oct 2004 Fixed 2940 22 Oct 2004 Fixed Description If the system tray icon was left-clicked, and the mouse then quickly moved far from the icon, the context menu would have appeared at the mouse location, far from the icon. The menu will now appear next to the icon.

CR:369957

CR Number:   369957 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 22 Oct 2004 Fixed 2940 22 Oct 2004 Fixed Description On Windows 2000 or XP systems, if the keyboard was used to navigate to the system tray icon and the context menu was activated, pressing Esc to cancel the menu would not have caused focus to be restored to the system tray icon. Pressing Tab to navigate would have resulted in a beep. Now, focus is restored to the icon after the menu is canceled.

CR:369977

CR Number:   369977 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) 9.0.0 1382 22 Oct 2004 Fixed 9.0.1 1941 22 Oct 2004 Fixed 9.0.2 2529 22 Oct 2004 Fixed 2944 22 Oct 2004 Fixed Description The Interactive SQL utility dbisql, could have crashed if its window was closed while an INPUT or OUTPUT statement was executing, and it had been launched from Sybase Central. Now, clicking the "File/Exit" menu item when a statement is executing will cause the same "Are you sure?" prompt as would occur when clicking the window's close button.

CR:369985

CR Number:   369985 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 22 Oct 2004 Fixed 2940 22 Oct 2004 Fixed Description When attempting to start ULISQL on operating systems older than Windows 2000, a message would have been displayed complaining that SHGetSpecialFolderPath could not be found in shell32.dll. This entry point is available in newer versions of shell32.dll (sometimes available with updates of Internet Explorer) and in shfolder.dll on older systems. Now, ULISQL will use shfolder.dll if the entry point is not found in shell32.dll.

CR:370045

CR Number:   370045 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) 2940 26 Oct 2004 Fixed 9.0.2 2529 26 Oct 2004 Fixed 9.0.1 1937 26 Oct 2004 Fixed 9.0.0 1379 26 Oct 2004 Fixed 8.0.3 5175 26 Oct 2004 Fixed 8.0.2 4489 26 Oct 2004 Fixed Description Insert performance on systems with three or more processors would have been much poorer than on single processor systems. The drop in performance would have been more noticable as the number of processors increased (and was likely even more noticeable on Unix systems). This problem has now been corrected.

CR:370046

CR Number:   370046 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 25 Oct 2004 Fixed 9.0.2 2529 25 Oct 2004 Fixed Description The following issues have been corrected when filling a DataSet or DataTable with the ULDataAdapter, and the ULDataAdapter.SelectCommand was of type TableDirect. Dynamic SQL SELECT statements were not affected. Only the name and type was specified for new columns when using Fill() with MissingSchemaAction.Add. AllowDBNull, AutoIncrement, ReadOnly, Unique were set only when Fill() with MissingSchemaAction.AddWithKey was used. Column properties are now set for all new columns. When FillSchema() or Fill() with AddWithKey was used with a non-empty DataTable and the columns did not match the source properties with respect to AllowDBNull, AutoIncrement, and Unique, DataException, ArgumentException, and InvalidConstraintException might have occurred. Existing columns are now left as the user specified them. If a data source column was flagged as autoincrementing, the DataColumn might have had its type corrupted, possibly resulting in a loss of data during Fill(). If the DataTable contained data, an ArgumentException was thrown, otherwise, an OverflowException might have been thrown during Fill(). Now exisiting columns do not have their properties modified by Fill() or FillSchema(). New autoincrementing columns of data source type SmallInt, Integer, BigInt, Decimal are flagged as AutoIncrement and may have their type sized up to prevent Fill() errors. Other new autoincrementing columns (in particular UnsignedBigInt) are not marked in the DataTable as AutoIncrement since .NET does not support AutoIncrement with non-signed integer types.

CR:370049

CR Number:   370049 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3534 26 Oct 2004 Fixed Description If for a query, the publications or constraints were built for a table whose correlation name was different than the table name, the error "-142 - Correlation name ... not found" was incorrectly reported. This has been fixed. For example: CREATE TABLE P( one CHAR(4) NOT NULL, two INTEGER NOT NULL PRIMARY KEY ); CREATE TABLE F( two INTEGER NOT NULL REFERENCES P(two), ); CREATE TABLE R( X INTEGER NOT NULL, Y integer not NULL ); CREATE PUBLICATION "Pub_F" ( TABLE F WHERE two = any(select R.X from R where R.Y > 9999 ) ); SELECT PP.two FROM P as PP KEY JOIN F as FF where PP.two < 100 Would have reported Error -142: "Correlation name FF' not found"

CR:370070

CR Number:   370070 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2940 26 Oct 2004 Fixed 9.0.2 2529 26 Oct 2004 Fixed Description The SIS Listener did not accept security options over TCPIP connections if they were specified as part of the MobiLink stream parameters, (ie -x command line option), when communicating tracking information and confirmations with the MobiLink Server. This is now fixed so that rsa_tls and certicom_tls can be used on top of TCPIP.

CR:370071

CR Number:   370071 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2944 04 Nov 2004 Fixed 9.0.2 2529 04 Nov 2004 Fixed 9.0.1 1942 04 Nov 2004 Fixed 8.0.3 5179 04 Nov 2004 Fixed 8.0.2 4496 04 Nov 2004 Fixed Description When the BACKUP DATABASE TO statement failed and returned an error, (for example if the location for the achive file was not writable), then subsequent BACKUP DATABASE TO statements that failed would have caused the server to fail with assertion 104400 (a stack overflow) on Solaris 8 or 9 systems. This has been fixed.

CR:370072

CR Number:   370072 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1944 26 Oct 2004 Fixed 9.0.0 1386 26 Oct 2004 Fixed Description Ultralite Dynamic SQL was failing to correctly evaluate non-trivial expressions involving alias names in the FROM clause, when a temporary table was also required with the query. This has now been corrected

CR:370074

CR Number:   370074 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2452 02 Nov 2004 Fixed Description The MobiLink\upgrade subdirectory contains one subdirectory for upgrading non-ASA consolidated databases from each previous version with different MobiLink system tables. In each of these directories is a readme.txt file. Some of these readme.txt files had headings that were misleading, leaving users to believe that upgrading was a multi-step process, involving a partial upgrade to a previous, but newer, version, then one or more additional upgrades to the current version. This is NOT correct, and the readme.txt files have been corrected. The proper way to upgrade a non-ASA MobiLink consolidated database of version 6.0.x is to run the appropriate setup script from the MobiLink\setup directory, followed by the SQL script from the appropriate MobiLink\upgrade\6.0.x subdirectory. The proper way to upgrade a non-ASA MobiLink consolidated database of version 7.0.x or greater is to run one SQL script from the appropriate MobiLink\upgrade\_version_ subdirectory for the version that is being upgraded from. There are a few special rules for DB2. Consult the documentation for details, under: What's New in SQL Anywhere Studio Upgrading Software and Databases Upgrading MobiLink Upgrading your consolidated database

CR:370082

CR Number:   370082 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1937 26 Oct 2004 Fixed Description Queries using a procedure call in a common table expression would have failed with the error: "-921 - Invalid recursive query". This is now allowed.

CR:370126

CR Number:   370126 Product Name:   UltraLite Product Component:   Analyser Java Classes Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2944 03 Nov 2004 Fixed 9.0.2 2529 03 Nov 2004 Fixed 9.0.1 1941 03 Nov 2004 Fixed Description When using CodeWarrior and Static SQL UltraLite, a statement such as: SELECT DISTINCT x1, x2, ..., xm FROM <table-expression> could have resulted in the UltraLite analyzer generating more code than was necessary. In cases where the number of columns in the select-list was large (for instance 20), the generated function could have been too large for the CodeWarrior compiler to handle. This has now been fixed.

CR:370129

CR Number:   370129 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2452 28 Oct 2004 Fixed Description Japanese characters would not have been displayed properly in the SQL command window of ULISQL. This has been fixed.

CR:370134

CR Number:   370134 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed Description With a new schema that had spaces in its pathname: 1. creating an UltraLite database would have failed with the error: "UltraLite database creation failed. Error: cannot specify additional arguments" 2. generating MobiLink scripts, or ASA SQL, for that database would have failed with the error: "Script generation failed. Possible installation or path issue. Error: only one XML file/sync block can be specified" This problem has been corrected.

CR:370165

CR Number:   370165 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2944 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1941 27 Oct 2004 Fixed Description MobiLink client's synchronizing through Microsoft's ISA Server 2000 proxy server, via HTTP or HTTPS, would have caused the MobiLink server to hang. This has been fixed for non-persisent HTTP connections (synchronization paramter 'persistent=0'), but not for persistent connections.

CR:370166

CR Number:   370166 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1938 27 Oct 2004 Fixed Description When not going through a proxy server, MobiLink clients always used "localhost:80" for the "Host:" HTTP header, instead of using the host and port passed via the synchronization parameters. This has been corrected.

CR:370180

CR Number:   370180 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2452 27 Oct 2004 Fixed 9.0.1 1938 27 Oct 2004 Fixed 9.0.0 1379 27 Oct 2004 Fixed Description If a version 8.x database was being used as a MobiLink Consolidated database, and at least one remote user had successfully synchronized multiple publications, then dbupgrad would have failed to upgrade the database to version 9.x. The Upgrade utility dbupgrad would have reported a primary key violation on the ml_subscription table, or in some circumstances the server could fail an assertion. This has been fixed.

CR:370185

CR Number:   370185 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed Description If the QAnywhere Agent qaagent was stopped by pressing the shutdown button, or using the QAnywhere Agent Stop utility qastop.exe, it could have taken up to 60 seconds to shutdown. This has been fixed.

CR:370190

CR Number:   370190 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1938 27 Oct 2004 Fixed Description QAnywhere messages received by the JMS connector, that contain an invalid JMS Destination, are normally placed in the dead-letter queue (specified using the connector property ianywhere.connector.outgoing.deadMessageAddress). If the dead-letter address referred to a QAnywhere client message store, and that client subsequently received the message, then the copy of that message would have remained in the server repository indefinitely. This problem is now fixed.

CR:370197

CR Number:   370197 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 26 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed Description If a SELECT statement resulted in unnamed columns, the ULDataAdapter object would have named the first unnamed column as "Column1", but then named subsequent unnamed columns as "1", "2", "3", etc. Subsequent fills would not have equated the first unnamed column as mapping to DataTable "Column1" and thus created "Column2", growing the DataTable by one column each time Fill() or FillSchema() was called. Now, unnamed columns are named "Column1", "Column2", etc.. As a workaround, columns may be named using aliasing in the SELECT statement. Example (C#): ULDataAdapter da = new ULDataAdapter( "SELECT MIN(SomeCol), MAX(SomeCol), SUM(SomeCol), AVG(SomeCol) AS Average FROM SomeTable", conn ); DataTableMapping dtm = da.TableMapping( "Table", "MyTable" ); dtm.ColumnMappings.Add( "Column1", "Min" ); dtm.ColumnMappings.Add( "Column2", "Max" ); DataSet ds = new DataSet(); da.Fill( dataSet ); // dataSet now has DataTable "MyTable" with columns "Min", "Max", "Column3", and "Average"

CR:370205

CR Number:   370205 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 28 Oct 2004 Fixed 9.0.2 2529 28 Oct 2004 Fixed Description A call to the C++ methods QAManagerBase::getMessage and QAManagerBase::getMessageTimeout may have returned a NULL value when there was, in fact, a message waiting. A subsequent call to the method QAManagerBase::getLastErrorMsg would indicate that a "Statement interrupted by user" error had occurred. Similarly, a call to the C# methods QAManagerBase.GetMessage and QAManagerBase.GetMessageTimeout would have caused a QAException to be thrown also indicating that a "Statement interrupted by user" error had occurred. The problem has been fixed.

CR:370247

CR Number:   370247 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) 2941 28 Oct 2004 Fixed 9.0.2 2529 28 Oct 2004 Fixed 9.0.1 1938 28 Oct 2004 Fixed 9.0.0 1379 28 Oct 2004 Fixed Description If Ultralite Dynamic SQL attempting to execute a query that used an alias name in the GROUP BY clause, it would have failed with a syntax error. For example, SELECT length( city ) AS city_length, count(*) FROM invoices GROUP BY city_length was diagnosed as erroneous. This has been corrected so that alias names in the GROUP BY clause are now accepted.

CR:370301

CR Number:   370301 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) 2942 27 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1939 27 Oct 2004 Fixed Description The ISNUMERIC() function could have returned TRUE for values which used the letter 'd' or 'D' as the exponent separator (eg. '1d2') on Windows platforms, or for values such as 'NAN', '0x12', 'INF', or 'INFINITY' on UNIX platforms. The function no longer returns TRUE for these values.

CR:370312

CR Number:   370312 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 27 Oct 2004 Fixed 9.0.2 2529 27 Oct 2004 Fixed 9.0.1 1938 27 Oct 2004 Fixed 9.0.0 1380 27 Oct 2004 Fixed 8.0.3 5176 27 Oct 2004 Fixed 8.0.2 4491 27 Oct 2004 Fixed Description A query in a procedure or batch, with an expression that involved remote tables and a unary minus or simple cast operator, would have failed with the error: ASA Error -823: OMNI cannot handle expressions involving remote tables inside stored procedures. This problem has now been fixed so that these operators do now work in expressions involving remote tables.

CR:370317

CR Number:   370317 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 28 Oct 2004 Fixed 9.0.2 2529 28 Oct 2004 Fixed 9.0.1 1938 28 Oct 2004 Fixed Description HTTP synchronizations would have failed if a proxy or web server used ASCII characters that were not beteen 0x20 and 0x7e (except for CR and LF) in their HTTP headers. now only characters less than 0x20 are rejected.

CR:370320

CR Number:   370320 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 29 Oct 2004 Fixed 9.0.2 2529 29 Oct 2004 Fixed Description The Quiet command line option (-q) was missing from the UltraLite XML utility's (ulxml) usage message, as well as the documentation. It has now been added.

CR:370326

CR Number:   370326 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 28 Oct 2004 Fixed 9.0.2 2529 28 Oct 2004 Fixed 9.0.1 1938 28 Oct 2004 Fixed 9.0.0 1380 28 Oct 2004 Fixed 8.0.3 5176 28 Oct 2004 Fixed 8.0.2 4491 28 Oct 2004 Fixed Description The method AsaDataReader.GetSchemaTable() may have caused an InvalidCastException when the data reader had some unique columns and computed columns. This problem has been fixed.

CR:370333

CR Number:   370333 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2452 29 Oct 2004 Fixed 9.0.1 1938 29 Oct 2004 Fixed 9.0.0 1380 29 Oct 2004 Fixed Description If a version 8.x database was being used as a MobiLink Consolidated database, and at least one remote user had successfully synchronized multiple publications, attempting to rebuild using dbunload would have failed when the reload.sql file was run against an empty database. A primary key violation on the ml_subscription table would have occurred. This has now been fixed. Note that the problem did not occur when using the -an or -ar dbunload command line options.

CR:370335

CR Number:   370335 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2941 29 Oct 2004 Fixed 9.0.2 2529 29 Oct 2004 Fixed 9.0.1 1938 29 Oct 2004 Fixed Description On Windows CE, the method QAManagerBase::putMessage would have returned FALSE, and getLastErrorMsg() would have returned the error message "The message store is too large relative to the disk free space on the device", even though there was sufficient space in the message store. This has been fixed.

CR:370339

CR Number:   370339 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) 2941 28 Oct 2004 Fixed 9.0.2 2529 28 Oct 2004 Fixed 9.0.1 1938 28 Oct 2004 Fixed 9.0.0 1380 28 Oct 2004 Fixed Description Correlated subqueries used in computed columns may have caused grouped queries to fail with the error " Function or column reference to ... must also appear in a GROUP BY". This has been fixed. An example: CREATE TABLE R ( X integer not null, Z integer not null, Y integer NULL COMPUTE ((select count(*) from R as old where old.X = R.X)) ) select R.Z from R group by R.Z

CR:370421

CR Number:   370421 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2945 09 Nov 2004 Fixed 9.0.2 2529 09 Nov 2004 Fixed 9.0.1 1944 09 Nov 2004 Fixed 9.0.0 1386 09 Nov 2004 Fixed 8.0.3 5181 09 Nov 2004 Fixed 8.0.2 4497 09 Nov 2004 Fixed Description If the ROUND() function rounded a numeric value, the resulting value may not have fit into the original NUMERIC data types percision. For example: The constant 9.995 is of type NUMERIC(4,3). The result of ROUND(9.995,1) is 10.000 which does not fit into numeric(4,3). As a result the numeric value generated by the ROUND() function could have been invalid and a conversion of this numeric value to a string could have returned '?'. This problem has been fixed. If the numeric value passed to ROUND() is a constant, the resulting data types percision is increased by one, (numeric(5,3) in the above example). If it is not a constant and the resulting value does not fit, then a SQLE_OVERFLOW_ERROR is generated if the option Convertion_error is set, otherwise NULL is returned.

CR:370446

CR Number:   370446 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2942 29 Oct 2004 Fixed 9.0.2 2529 29 Oct 2004 Fixed Description The return values from the UltraLite utilities ULCONV, ULCREATE, ULDBSGEN, ULLOAD, ULSYNC, ULUNLOAD, and ULXML have been changed from negative to positive values. This allows batch files to use ERRORLEVEL.