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

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

CR:373255

CR Number:   373255 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) 2966 26 Nov 2004 Fixed 9.0.2 2535 26 Nov 2004 Fixed 9.0.1 1955 26 Nov 2004 Fixed Description It a column name ended in a blank space, the QueryEditor would have trimed the blank space from the end of the name, causing errors. This has been fixed.

CR:373299

CR Number:   373299 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) 2970 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1956 30 Nov 2004 Fixed Description Using the Unload utility dbunload, with the command line options -an (create new database and reload) or -ar (rebuild and replace database), against a server which was not running sharedmemory, would have failed attempting to conmnect to the new database. The generated connection strings used to by -an and -ar to connect to the new database did not include the LINKS parameters. Now, it includes all the parameters specified for the connection to the source database. Note, the server used with dbunload -ar must be on the same machine where dbunload is run, but dbunload -an can now be used against a remote server.

CR:373341

CR Number:   373341 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) 2970 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed Description The plan for a static Ultralite query could have incorrectly contained references to a base table's computed columns, causing a semantic error. This would have occurred if the table being referenced contained a computed column, even though the query did not refer to the computed column directly. This has been fixed.

CR:373382

CR Number:   373382 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) 2970 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1956 30 Nov 2004 Fixed Description If a query contained a join between a remote table and a lateral derived table with an ON clause, the chances were very good that the server would have crashed. This problem has been fixed.

CR:373462

CR Number:   373462 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) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed 9.0.0 1390 30 Nov 2004 Fixed 8.0.3 5191 30 Nov 2004 Fixed 8.0.2 4503 30 Nov 2004 Fixed 7.0.4 3535 30 Nov 2004 Fixed Description If a CREATE TABLE statement failed, for example because of duplicate column names, and no commit or rollback was executed so far, the next attempt to execute a CREATE TABLE statement, on any connection, would have crashed the server or cause an assertion failure 102801. This has now been fixed.

CR:373472

CR Number:   373472 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) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed 9.0.0 1390 30 Nov 2004 Fixed Description The Unload utility dbunload, may not have properly reloaded the contents of the sys.syssync table for databases that were involved in synchronization. This would have caused dbmlsync to always have been checking the last sync status with MobiLink synchronization server, in the first synchronization after the remote database was rebuilt. This problem is noe fixed.

CR:373477

CR Number:   373477 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed 8.0.3 5191 30 Nov 2004 Fixed Description Running the Unload utility dbunload, with both the -ar (rebuild and replace database) and -ek (specify encryption key for new database) command line options, would have failed when attempting to connect to the new database with the error "Unable to open database file "<file>" -- Missing database encryption key." The last step of dbunload -ar is to rename the log file, but the encryption key was not specified when it should have been. This is now fixed, te encryption key is now specified correctly.

CR:373480

CR Number:   373480 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed 9.0.0 1390 30 Nov 2004 Fixed 8.0.3 5191 30 Nov 2004 Fixed Description If a server was started with a server name containing non-7-bit ASCII characters, and the client machine's character set did not match the server machine's character set, applications may not have been able to connect when specifying the server name, (ie ENG parameter). This has been fixed.

CR:373482

CR Number:   373482 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed 9.0.0 1390 30 Nov 2004 Fixed 8.0.3 5191 30 Nov 2004 Fixed Description If a connection string included the TCP parameter VerifyServerName=NO, and contained an incorrect server name, the connection would have failed, essentially, the VerifyServerName parameter was ignored. This has been fixed.

CR:373483

CR Number:   373483 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) 2971 01 Dec 2004 Fixed 9.0.2 2537 01 Dec 2004 Fixed Description If an INSERT statement used a SELECT query that required a work table at the top of the query plan, then the value of NUMBER(*) in the result of the insert could have been improperly set to 0 for all rows. This has been fixed. For example, the following INSERT could have generated the incorrect values: insert into R select 0-row_num, number(*) from rowgenerator where row_num <= 3 order by 1

CR:373519

CR Number:   373519 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) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed Description If a QAnywhere connector was configured to connect to WebSphere MQ, and the connector received a JMS BytesMessage with a zero length, the message would have been ignored. The MobiLink log file would have included a error message indicating "NullPointerException". With this fix, zero length BytesMessage will be received correctly.

CR:373526

CR Number:   373526 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) 2971 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1957 30 Nov 2004 Fixed Description If a QAnywhere connector was configured to connect to WebSphere MQ, and a QAnywhere message sent to the connector contained an InReplyToID,, (QAMessage::setInReplyToID() in C++, QAMessage.InReplyToID property in .NET), then the message would not have been sent onwards to WebSphere MQ. The MobiLink log would show an error indicating an invalid "JMSCorrelationID". If the connector was configured with a dead message address, then the message would be re-addressed to that address. Now, this problem will no longer occur.

CR:373531

CR Number:   373531 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) 2971 01 Dec 2004 Fixed 9.0.2 2538 01 Dec 2004 Fixed 9.0.2 2538 01 Dec 2004 Fixed 9.0.1 1957 01 Dec 2004 Fixed Description The fix for Engineering Case 367366 introduced a problem where attempting to establish a connection to a remote ASA database with a long database name, or a long engine name, could have crashed the server. This problem has been fixed. Workaround Description  None

CR:373541

CR Number:   373541 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Solaris Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2537 30 Nov 2004 Fixed 2971 30 Nov 2004 Fixed Description When run on Unix systems, the MobiLink server may have crashed when using DataDirect's 5.0 Driver Manager. The crash would have occurred when trying to retrieve an error message from the database server. This has been fixed.

CR:373543

CR Number:   373543 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) 2970 30 Nov 2004 Fixed 9.0.2 2537 30 Nov 2004 Fixed 9.0.1 1953 30 Nov 2004 Fixed Description The QAnywhere client library did not have APIs to provide information on the number of messages queued for sending and receiving. This has been addressed by adding methods to QAManagerBase to give this information. For C#, the following enumeration type was added: public enum QueueDepthFilter { /// <summary> /// Count both incoming and outgoing messages. System messages /// and expired messages are not included in any queue depth /// counts. /// </summary> ALL, /// <summary> /// Count only incoming messages. An incoming message is defined /// as a message whose originator is different than the agent ID /// of the message store. /// </summary> INCOMING, /// <summary> /// Count only outgoing messages. An outgoing message is defined /// as a message whose originator is the agent ID /// of the message store, and whose destination is not the /// agent ID of the message store. /// </summary> OUTGOING }; For C#, the following methods were added to QAManagerBase: /// <summary> /// Returns the total depth of all queues, based on a given filter. /// <param name="filter">a filter indicating incoming messages, /// outgoing messages, or all messages</param> /// <exception cref="iAnywhere.QAnywhere.Client.QAException"> /// if there was an error /// </exception> /// <returns>the number of messages</returns> /// </summary> public int GetQueueDepth( QueueDepthFilter filter ); /// <summary> /// Returns the depth of a queue, based on a given filter. /// <param name="filter">a filter indicating incoming messages, /// outgoing messages, or all messages</param> /// <param name="address">the queue name</param> /// <exception cref="iAnywhere.QAnywhere.Client.QAException"> /// if there was an error /// </exception> /// <returns>the number of messages</returns> /// </summary> public int GetQueueDepth( string address, QueueDepthFilter filter ); Similarly, for C++, the following methods were added to QAManagerBase: /** * Returns the total depth of all queues, based on a given filter. * @param filter a filter indicating incoming messages, outgoing messages, * or all messages * @see QueueDepthFilter * @return the number of messages, or -1 if there was an error */ virtual qa_int getAllQueueDepth(qa_short filter) = 0; /** * Returns the depth of a queue, based on a given filter. * @param filter a filter indicating incoming messages, outgoing messages, * or all messages * @see QueueDepthFilter * @param dest the queue name * @return the number of messages in the queue, or -1 if there was an error */ virtual qa_int getQueueDepth(qa_const_string dest, qa_short filter) = 0;

CR:373607

CR Number:   373607 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) 2971 02 Dec 2004 Fixed 9.0.2 2538 02 Dec 2004 Fixed 9.0.1 1957 02 Dec 2004 Fixed 9.0.0 1390 02 Dec 2004 Fixed Description If the first executable statement of a stored procedure was a SELECT ... INTO, then using this procedure in the FROM clause of a SELECT statement would have caused the server to crash. This has been fixed For example: create procedure P1 () begin declare var varchar(128); select first table_name into var from systable; end then select * from P1() would have crashed the server.

CR:373613

CR Number:   373613 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2971 01 Dec 2004 Fixed 9.0.2 2537 01 Dec 2004 Fixed 9.0.1 1957 01 Dec 2004 Fixed 8.0.3 5191 01 Dec 2004 Fixed Description An obsolete Java class could have caused the error "-110 - 'Item ... already exists'", when attempting to install a new version of a Java class previously removed. This has been fixed.

CR:373614

CR Number:   373614 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) 9.0.1 1955 01 Dec 2004 Fixed Description When a later version of Visual Studio .NET was installed and subsequently uninstalled, the .NET installer would fail and popup a message box. For example, if Visual Studio .NET and Visual Studio .NET 2003 were installed and then Visual Studio .NET 2003 was removed, the UL.NET installer would still have thought 2003 was installed. The changes for Engineering Case 368160 attempted to address this problem, but the failure could still have occurred as the UL.NET installer must use two different strategies to integrate into Visual Studio, and only one was correctly fixed. Now both are fixed.

CR:373623

CR Number:   373623 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1958 03 Dec 2004 Fixed 9.0.2 2539 03 Dec 2004 Fixed 2973 03 Dec 2004 Fixed Description When synchronizing a version 6 or version 7 MobiLink client to a version 9 MobiLink server, that was connected to a RDBMS other than ASA, it was possible for the MobiLink server to report an "Invalid datetime format" error after having sent the download stream to the remote. This has now been fixed.

CR:373705

CR Number:   373705 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) 2972 03 Dec 2004 Fixed 9.0.2 2538 03 Dec 2004 Fixed 9.0.1 1958 03 Dec 2004 Fixed Description Ultralite Dynamic SQL could have produced incorrect results with an ANY condition in the WHERE clause, if there was a subquery that contained a reference to a column in the original query. This has been fixed.

CR:373732

CR Number:   373732 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) 2972 02 Dec 2004 Fixed 9.0.2 2538 02 Dec 2004 Fixed Description Statistics for the index on the SYSATTRIBUTE system table may have become incorrect in rare cases. This would have been reported as a validation error. The problem has been fixed.

CR:373733

CR Number:   373733 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Microsoft Windows 98 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1966 20 Dec 2004 Fixed Description When using UltraLite Dynamic SQL, queries with refrences in the SELECT clause, to derived-table columns from the WHERE clause, could have been incorrectly optimized. This has been fixed.

CR:373740

CR Number:   373740 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) 2972 02 Dec 2004 Fixed 9.0.2 2538 02 Dec 2004 Fixed 9.0.1 1958 02 Dec 2004 Fixed Description The Interactive SQL utility dbisql, could have become unresponsive if a statement which returned many large result sets was executed. Interactive SQL would have attempted to display all the result sets, and could eventually run out of memory . Two changes were made to address this problem: 1. The "Show multiple result sets" setting was being ignored. Now the setting is respected, so by default, only the first result set is displayed. 2. Even if the "Show multiple result sets" setting is on, only the first 10 result sets will be displayed.

CR:373752

CR Number:   373752 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) 2971 02 Dec 2004 Fixed 9.0.2 2538 02 Dec 2004 Fixed 9.0.1 1958 02 Dec 2004 Fixed Description Attempting to duplicate a Group by copying it to the clipboard and then pasting it into the Users & Groups folder, would not have copied any of the members. As well, if a Group was copied and pasted into Interactive SQL, the SQL for the group would not have ncluded the statements required to define its members. Both of these problems are now fixed.

CR:373770

CR Number:   373770 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.2 3021 21 Jan 2005 Fixed 9.0.1 1976 21 Jan 2005 Fixed Description Attempts to use the builtin XML functions on proxy tables would have failed with the error "No name for arguement". This problem has been fixed.

CR:373897

CR Number:   373897 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) 9.0.1 1961 14 Dec 2004 Fixed Description When the Index Consultant was run from Interactive SQL, it would have reported that any query could not be optimized due to optimizer/parser errors. The problem was caused by an incorrect query result returned from the server as a result of the changes made for Engineering Case 364372, which was fixed by Engineering Case 374844. With a server with that fix, the Index Consultant now operates normally.

CR:373903

CR Number:   373903 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Open OS:   Windows CE 2.0 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Dec 2004 Third Party Problem Fixed Description PocketBuilder and ASA 9.0.2 When trying to fetch data from a datawindow you get the error: "S1090 - Invalid String or buffer length". This issue doesn't appear in any combination of PB 1.5.2 and 2.0 with ASA 9.0.1. But with 9.0.2, the issue remains. Workaround Description  Disable binding in the connection parameters. "DisableBind = 1"

CR:373919

CR Number:   373919 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2973 06 Dec 2004 Fixed 9.0.2 2539 06 Dec 2004 Fixed 9.0.1 1958 06 Dec 2004 Fixed Description If the Unload Database wizard was used to unload the data, but not the structure, from a subset of a database's tables, then all types of tables were listed in the wizard. This was misleading, since the wizard should only unload the data from base tables; that is, the data from proxy and global temporary tables should not be unloaded. Now, only base tables are listed in the wizard when choosing to unload data only. When choosing to unload the tables' structure, then all types of tables are listed as before.

CR:373931

CR Number:   373931 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2973 06 Dec 2004 Fixed 9.0.2 2539 06 Dec 2004 Fixed Description In some circumstances, attempting to unload the data from one or more tables by selecting the tables, and then choosing "Unload Data..." from the File menu, would have caused Sybase Central to crash. This has been fixed. In addition, the "Unload Data..." menu item is now only available for base tables. It was previously available to proxy tables and global temporary tables as well, which was incorrect, as the Unload Data dialog can only be used to unload data from a base table.

CR:374053

CR Number:   374053 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) 2987 17 Dec 2004 Fixed 9.0.2 2544 17 Dec 2004 Fixed 9.0.1 1964 17 Dec 2004 Fixed Description When using UltraLite Dynamic SQL, it would have taken a long time (approx 30 minutes) to create tables, when there were more than 200 tables already. This has been fixed.

CR:374061

CR Number:   374061 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) 2980 07 Dec 2004 Fixed 9.0.2 2541 08 Dec 2004 Fixed Description The QAnywhere Agent could have sent or received messages with an "ondemand" policy, without it calling QAManager.TriggerSendReceive. This has been fixed. Now, when qaagent is started with "ondemand" policy, messages are sent and received only when a client application calls QAManager.TriggerSendReceive, as documented.

CR:374070

CR Number:   374070 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2976 07 Dec 2004 Fixed 9.0.2 2540 08 Dec 2004 Fixed 9.0.1 1959 08 Dec 2004 Fixed 8.0.3 5193 08 Dec 2004 Fixed Description The ASA client dbmlsync, could have crashed, either while creating the upload, or at the end of the synchronization. This was more likely to occur with very large uploads. This behaviour has been corrected.

CR:374085

CR Number:   374085 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2976 07 Dec 2004 Fixed 9.0.2 2540 08 Dec 2004 Fixed Description The MobiLink listener's -x option (MobiLink stream parameters) did not accept stream parameters enclosed in braces. Braces are now allowed after this change. For example, both of the following are now allowed: dblsn.exe -x tcpip(host=localhost) dblsn.exe -x tcpip{host=localhost}

CR:374122

CR Number:   374122 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) 2944 07 Dec 2004 Fixed 9.0.2 2529 08 Dec 2004 Fixed 9.0.1 1941 08 Dec 2004 Fixed 9.0.0 1382 08 Dec 2004 Fixed Description Any user with DBA authority could have connected to a web service, regardless of the restrictions placed on that web service by the USER clause. Now the USER clause restrictions are respected. For example, if the following SQL was executed: grant connect to hurz identified by 'sql'; create service test type 'html' user hurz as select * from systable; grant connect to newdba identified by 'sql'; grant DBA to newdba; then both hurz and newdba (as well as any other user with DBA authority) could have connected to the service test.

CR:374123

CR Number:   374123 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) 2976 07 Dec 2004 Fixed 9.0.2 2540 08 Dec 2004 Fixed 9.0.1 1959 08 Dec 2004 Fixed 9.0.0 1391 08 Dec 2004 Fixed Description The function http_variable() would have returned a non-obvious ordering for variables with multiple values. For example, for the following request: http://localhost/foo?id=1&id=2&id=3&id=4&id=5 http_variable() would return the values for id in the following order: 1, 5, 4, 3, 2 The function was adding variables (and their values), either after the first occurrence of the variable, or at the end of the list. Now, variables and their values are added after the last occurrence of the variable, or at the end of the list.

CR:374162

CR Number:   374162 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) 2977 07 Dec 2004 Fixed 9.0.2 2540 08 Dec 2004 Fixed Description In localized versions of ASA, the English string 'SubQ' (used as an abbreviation for subquery) was inconsistently translated in the long query plan (i.e. from the plan() function). It would appear translated in some contexts, and not in others. This prevented users from easily scanning the query plan looking for the same word to locate the subquery responsible for a given selectivity This has been fixed so that 'SubQ' always appears in the localized language of the plan.

CR:374301

CR Number:   374301 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 1586 11 Jan 2005 Fixed 9.0.2 3021 21 Jan 2005 Fixed 9.0.1 1976 21 Jan 2005 Fixed Description Attempting to synchronize via HTTPS through an Internet Information Services web server, with a VeriSign certificate, would have failed. This has been corrected.

CR:374308

CR Number:   374308 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) 10.0.0 1563 20 Dec 2004 Fixed 9.0.2 3142 20 Dec 2004 Fixed 9.0.1 1963 20 Dec 2004 Fixed Description Extremely complex queries with many equality predicates, for which the optimizer underestimated the number of rows in the result set due to highly correlated predicates, may have had inefficient query plans. This fix introduces a new approach for dealing with such queries. Now, the optimizer evaluates for very complex and cheap queries, some static qualities of the enumerated plans that are not dependent on cost, or number of rows.

CR:374353

CR Number:   374353 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) 2978 09 Dec 2004 Fixed 9.0.2 2541 09 Dec 2004 Fixed Description The QAnywhere Agent, when run with "automatic" policy, could have performed message synchronizations very slowly where the download portion of the synchronization was interrupted and then restarted. This has been fixed, now synchronizations will recover in a more timely manner when the downloads are interrupted and restarted.

CR:374441

CR Number:   374441 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) 2978 09 Dec 2004 Fixed 9.0.2 2541 09 Dec 2004 Fixed Description When using the UltraLite Engine, connections to a database could have failed with error SQLE_UNRECOGNIZED_OPTION, if the StartLine connection parameter was provided for autostarting the engine. This has been fixed.

CR:374445

CR Number:   374445 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) 2979 10 Dec 2004 Fixed 9.0.2 2541 10 Dec 2004 Fixed Description When running the Index Consultant from Interactive SQL, the 'Show Plan with Virtual Indexes' button would have beeen disabled on non-English platforms, regardless of whether any virtual indexes had been recommended. The same problem could have appeared when using the Index Consultant from Sybase Central, if a previously saved analysis was viewed. This has been fixed.

CR:374451

CR Number:   374451 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2979 09 Dec 2004 Fixed 9.0.2 2541 09 Dec 2004 Fixed 9.0.1 1961 09 Dec 2004 Fixed 8.0.3 5194 09 Dec 2004 Fixed Description An application using the iAnywhere JDBC Driver would have leaked memory if it called Connection.getMetaData() repeatedly. This problem has been fixed.

CR:374452

CR Number:   374452 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) 2979 09 Dec 2004 Fixed 9.0.2 2541 09 Dec 2004 Fixed 9.0.1 1961 09 Dec 2004 Fixed 8.0.3 5194 09 Dec 2004 Fixed Description If a proxy table to a DB2 table with a CLOB column, was used in a query, then selecting that CLOB column would have failed with an unsupported datatype error. This problem has been fixed.

CR:374459

CR Number:   374459 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2979 10 Dec 2004 Fixed 9.0.2 2541 10 Dec 2004 Fixed Description If a client connection to an UltraLite engine crashed, or terminated without properly calling DatabaseManager::Shutdown, and had autostarted the engine, the engine would not automatically shutdown. This has been fixed.

CR:374490

CR Number:   374490 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2979 10 Dec 2004 Fixed 9.0.2 2541 10 Dec 2004 Fixed 9.0.1 1961 10 Dec 2004 Fixed 8.0.3 5194 10 Dec 2004 Fixed Description If the environment variables TMP or TEMP were not set, the MobiLink client dbmlsync, would have given the error: "Unable to open temporary file "MLSY\xxxx" -- No such file or directory" and refused to start. This problem is now fixed.

CR:374535

CR Number:   374535 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) 2980 10 Dec 2004 Fixed 9.0.2 2541 10 Dec 2004 Fixed 9.0.1 1961 10 Dec 2004 Fixed Description The Ultralite Dynamic SQL parser did not support the Datetime() function and incorrectly generated a syntax error. This has been fixed.

CR:374580

CR Number:   374580 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2981 13 Dec 2004 Fixed 9.0.2 2542 13 Dec 2004 Fixed 9.0.1 1961 13 Dec 2004 Fixed 8.0.3 5195 13 Dec 2004 Fixed Description An InvalidCastException would have been thrown when filling a DataTable using AsaDataAdapter, if a returned TIME column was mapped to a STRING column in the DataTable. This problem has been fixed.

CR:374595

CR Number:   374595 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2982 13 Dec 2004 Fixed 9.0.2 2542 13 Dec 2004 Fixed 9.0.1 1961 13 Dec 2004 Fixed Description After performing a large upload, there was a long pause at the end of synchronization. This pause would have occurred after the message "Disconnnecting from Mobilink server" was printed in the log, but before the message "Synchronization Completed". This has been fixed, although the pause may still occur during a synchronization when the MobiLink client expects to subsequently perform another synchronization before it shuts down, (for example because a schedule option has been specified, or more than one -n switch has been specified on the commandline, or the restart option in the sp_hook_dbmlsync_end hook has been used). In these cases the pause at the end of the earlier synchronization is offset by a time savings in the following synchronization.,

CR:374602

CR Number:   374602 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) 2981 13 Dec 2004 Fixed 9.0.2 2542 13 Dec 2004 Fixed 9.0.1 1961 13 Dec 2004 Fixed Description Interactive SQL could have failed with an internal error (NullPointerException) when one of its windows was closed, and all of the following were true: - more than one window had been opened by clicking the "Window/New Window" menu item - more than one window was closed in quick succession This was was more likely to have occurred on busy machines. It has now been fixed.

CR:374620

CR Number:   374620 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) 2982 10 Dec 2004 Fixed 9.0.2 2542 10 Dec 2004 Fixed Description When calling UltraLite_TableSchema::GetIndexSchema( ordinal ), if the ordinal was greater then the number of indexes in that table schema, an error would have been generated, and an illegal UltraLite_IndexSchema object would have been returned. Using a method on that object would have then caused a crash (illegal memory access). This is now fixed.

CR:374630

CR Number:   374630 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) 2982 13 Dec 2004 Fixed 9.0.2 2542 13 Dec 2004 Fixed 9.0.1 1961 13 Dec 2004 Fixed Description On Mac OS X, script files, which did not have a file extension, were not able to be selected by the "Run Script" menu item. . A ".sql" was always added to the file name. This has now been changed so that a ".sql" file extention is no longer required.

CR:374705

CR Number:   374705 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2985 13 Dec 2004 Fixed 9.0.2 2543 13 Dec 2004 Fixed 9.0.1 1962 13 Dec 2004 Fixed 8.0.3 5196 13 Dec 2004 Fixed Description When the Unload utility dbunload, was run with the command line option -ar (rebuild and replace database), the old transaction log file may not have been deleted after the database was successfully rebuilt, even if there was no replication/synchronization involved in the original database. This problem has been fixed.

CR:374709

CR Number:   374709 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) 2985 13 Dec 2004 Fixed 9.0.2 2543 13 Dec 2004 Fixed Description If the server was attempting to start the TCPIP link, but could not bind to port 2638, possibly because it is already in use, it would not have chosen a random port to listen on. This has been fixed. Note, this problem only affected servers on Windows and Netware systems, it did not affect servers running on Unix systems.

CR:374714

CR Number:   374714 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2985 13 Dec 2004 Fixed 9.0.2 2543 13 Dec 2004 Fixed 9.0.1 1962 13 Dec 2004 Fixed Description Executing a statement using Interactive SQL that sends messages back to the client (ex. ALTER DATABASE UPGRADE, or CREATE DATABASE, or MESSAGE ... TO CLIENT), could have caused Interactive SQL to crash, if the connection was via the iAnywhere JDBC driver. This has now been fixed. While the problem exists on all platforms, the crash has only been seen on AIX systems.

CR:374727

CR Number:   374727 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2985 14 Dec 2004 Fixed 9.0.2 2543 14 Dec 2004 Fixed 9.0.1 1962 14 Dec 2004 Fixed Description When using the iAnywhere JDBC Driver to connect to a DB2 database using the IBM DB2 ODBC driver, and the method ResultSet.getObject() was used on a BLOB column, the iAnywhere JDBC Driver would have failed with the error "Failed to map result on column ? to a Java class" where ? is the column number. This problem has been fixed.

CR:374752

CR Number:   374752 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) 2985 14 Dec 2004 Fixed 9.0.2 2543 14 Dec 2004 Fixed 9.0.1 1963 14 Dec 2004 Fixed 9.0.0 1392 14 Dec 2004 Fixed Description If a server was listening on more than one HTTPS port, it was possible that HTTP requests for services created with SECURE ON would have been redirected to an HTTPS port that could not handle the request. This has been fixed. For example, given a server started with the following command line options: -xs http,https(port=443;dbn=db1),https(port=444;dbn=db2) db1.db db2.db If "sec" was a secure service in db2, then HTTP requests for "/db2/sec" would have been redirected (via the 301 status code) to port 443 rather than 444. In most cases, this would result in a "404 Not Found" status, but could possibly have executed the wrong service. In this case, if db1 had a service called "db2/sec".

CR:374822

CR Number:   374822 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) 2986 14 Dec 2004 Fixed 9.0.2 2543 14 Dec 2004 Fixed 9.0.1 1963 14 Dec 2004 Fixed Description Recovery of transactions requiring the Wait_for_commit option to be ON could have failed assertion 100904 "Failed to redo a database operation". For this to have occurred, the following must have been true: - The WAIT_FOR_COMMIT option must have been on as a temporary option (not a user-level option) - A connection must have started a transaction - A subsequent checkpoint must have occurred while the transaction started was still active (ie. had not been committed or rolled back). - Additional operations on the transaction must have been performed that *required* the WAIT_FOR_COMMIT option and must have been written to disk (likely due to a commit) - The server must have gone down dirty before any other checkpoint occurred. This has been fixed, the Wait_for_commit option is now always on during recovery.

CR:374840

CR Number:   374840 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2986 14 Dec 2004 Fixed 9.0.2 2543 14 Dec 2004 Fixed 9.0.1 1963 14 Dec 2004 Fixed 8.0.3 5196 14 Dec 2004 Fixed Description Calling the Connection.getCatalog() method, when using the iAnywhere JDBC Driver, would have yielded a string with extra characters. Note that this problem only existed if the JDBC Driver was used to connect to a server other than an ASA server. The problem has been fixed.

CR:374844

CR Number:   374844 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 1961 14 Dec 2004 Fixed Description The changes for CR 364372 could have caused, in rare situations, an incorrect result set to be returned. This has been fixed.

CR:374846

CR Number:   374846 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) 2995 21 Dec 2004 Fixed 9.0.2 2546 21 Dec 2004 Fixed 9.0.1 1966 21 Dec 2004 Fixed Description Issuing a CREATE VIRTUAL INDEX statement on a proxy table would have caused the server to crash. A crash could also have occurred if the Index Consultant was run against a workload containing queries over proxy tables. This has been fixed. Note that although virtual index creation is allowed on proxy tables, such indexes are not meaningful and are not considered by the optimizer.

CR:374870

CR Number:   374870 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3004 10 Jan 2005 Fixed 9.0.2 2549 10 Jan 2005 Fixed 9.0.1 1970 10 Jan 2005 Fixed Description The Palm HotSync Conduit Installation Utility (dbcond9.exe) may have crashed when installing or uninstalling a conduit on Windows NT 4.0, if the HotSync Manager was not available. This has been fixed. Workaround Description  None

CR:374874

CR Number:   374874 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2986 14 Dec 2004 Fixed 9.0.2 2543 14 Dec 2004 Fixed 9.0.1 1964 14 Dec 2004 Fixed Description When using a cursor for which prefetch could be enabled, the fetch performance of many rows may have been slower than expected. In order for this problem to have occurred, the bound size, or described size, of the columns would have to have been fairly small (less than 50 bytes), and the number of rows prefetched must have been reduced by the maximum memory used for buffering prefetch data (see the PrefetchBuffer connection parameter). This has now been fixed.

CR:374895

CR Number:   374895 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) 2986 15 Dec 2004 Fixed 9.0.2 2543 15 Dec 2004 Fixed Description Attempting to start a server on NetWare that supported both ecc_tls encryption and https, would have failed with the error - 'Missing or invalid encryption DLL "dbrsa9s.nlm"'. When starting a server with both ecc_tls and rsa_tls encryption, the server would have started, but rsa_tls would not have been supported. This has been fixed.

CR:374975

CR Number:   374975 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) 2998 22 Dec 2004 Fixed 9.0.2 2546 22 Dec 2004 Fixed 9.0.1 1967 22 Dec 2004 Fixed Description Under some circumstances, the Index Consultant could claim a benefit for the query or workload, even though no indexes were recommended. This has been fixed. Note that the same problem could have occurred in the Sybase Central Index Consultant as well, although it is less likely. It has been fixed there as well.

CR:374976

CR Number:   374976 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) 2988 15 Dec 2004 Fixed 9.0.2 2544 15 Dec 2004 Fixed 9.0.1 1964 15 Dec 2004 Fixed 8.0.3 5197 15 Dec 2004 Fixed 8.0.2 4506 15 Dec 2004 Fixed Description The debugger would have shown all connections on the server, instead of only showing those connections to the database that the debugger was connected to. This has been fixed.

CR:374988

CR Number:   374988 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) 2986 15 Dec 2004 Fixed 9.0.2 2544 15 Dec 2004 Fixed 9.0.1 1964 15 Dec 2004 Fixed 8.0.3 5197 15 Dec 2004 Fixed Description An INSERT statement, using the ON EXISTING clause to insert the result set of a query involving a remote table, into a local table, would have failed with a syntax error. The server will now execute these statements correctly. For example, instead of generating a syntax error, the following will cause table 'bar' to contain one row: CREATE SERVER asademo CLASS 'asaodbc' USING 'driver=Adaptive Server Anywhere 9.0;dbn=asademo'; CREATE TABLE foo(c1 int) AT 'asademo...'; create table bar( c1 int primary key ); insert into foo values(1); insert into foo values(1); insert into foo values(1); commit; insert into bar on existing skip select * from foo; select * from bar

CR:374990

CR Number:   374990 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) 2988 16 Dec 2004 Fixed 9.0.2 2544 16 Dec 2004 Fixed Description The server could have exhibited slower than expected insert performance on a multiprocessor machine when multiple clients were repeatedly attempting to insert into a table containing an index, primary key or unique constraint. Specifically, this problem occured when the clients were doing repeated inserts to the end of an index (such as is the case with an autoincrement primary key column). In this case, the server running on multiprocessor machines with more CPUs could exhibit relatively little performance improvement over the server on machines with fewer CPUs. This has been fixed.

CR:375084

CR Number:   375084 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2989 16 Dec 2004 Fixed 9.0.2 2544 16 Dec 2004 Fixed 9.0.1 1965 16 Dec 2004 Fixed 8.0.3 5197 16 Dec 2004 Fixed Description If a request-level log contained host variable information for a TDS connection, the system procedure sa_get_request_times would not have recorded the host variable information in the satmp_request_hostvar table. This has been fixed.

CR:375088

CR Number:   375088 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) 2989 17 Dec 2004 Fixed 9.0.2 2544 17 Dec 2004 Fixed Description If a client application was connected via jConnect or the Open Client interface, and the application attempted to query a UNIQUEIDENTIFIER column, the query would have failed with the error "Attempted conversion between an illegal pair of types". This problem has now been fixed. Note that in addition to getting a new server, a new version of jcatalog.sql will have to be run against the database with the UNIQUEIDENTIFER column, to fully implement this fix.

CR:375097

CR Number:   375097 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) 2989 17 Dec 2004 Fixed 9.0.2 2453 17 Dec 2004 Fixed 9.0.1 1965 17 Dec 2004 Fixed 9.0.0 1392 17 Dec 2004 Fixed Description When running on NetWare 5.1 with service pack 8, the ASA server would not start up if TCPIP or HTTP was used. When the -z (display debugging information) command line option was used, the message "TCP/IP link, function bind, error code 10038" was displayed on the console. This has been fixed. Note that at the time of this fix, NetWare 5.1 SP 8 was still in beta.

CR:375102

CR Number:   375102 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) 2989 17 Dec 2004 Fixed 9.0.2 2544 17 Dec 2004 Fixed 9.0.1 1965 17 Dec 2004 Fixed Description In rare cases, the optimizer may have produced plans that omitted a sort. For example, the following query requires 2 sorts to properly calculate the 3 window functions. select sum(emp_id) over (order by emp_fname, emp_lname), sum(emp_id) over (partition by emp_lname), sum(emp_id) over (partition by emp_lname, emp_fname) from employee Previously, it would only have used one. This has been fixed.

CR:375197

CR Number:   375197 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows NT Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2992 20 Dec 2004 Fixed 9.0.2 2545 20 Dec 2004 Fixed 9.0.1 1965 20 Dec 2004 Fixed Description A problem with GROUPING SETS, that could have caused server crashes, has been fixed.

CR:375203

CR Number:   375203 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1965 17 Dec 2004 Fixed Description On Linux and HP-UX systems, if a large number of clients were doing synchronizations at the same time against DB2, the Mobilink server could have crashed. The error would be "Error: Unable to dump exception information. Received exception while processing exception." or "Error: An unexpected exception has been detected in native code outside the VM." This is a stack overflow problem. This has been fixed by increasing the size of the stack on these platforms.

CR:375205

CR Number:   375205 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) 2989 17 Dec 2004 Fixed 9.0.2 2544 17 Dec 2004 Fixed 9.0.1 1965 17 Dec 2004 Fixed Description When adding or removing Java classes or JAR files in a database, a class might have appeared in the All Java Classes folder, but not in the Java Packages or JAR files folder. This has been fixed. Now, all sub-folders of the Java Objects folder are kept synchronized.

CR:375236

CR Number:   375236 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2992 20 Dec 2004 Fixed 9.0.2 2545 20 Dec 2004 Fixed 9.0.1 1965 20 Dec 2004 Fixed 8.0.3 5198 20 Dec 2004 Fixed Description Under rare situations, calls to functions that took string parameters, could have crashed the server. This was only a problem on Unix systems, and has now been fixed.

CR:375256

CR Number:   375256 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) 2992 20 Dec 2004 Fixed 9.0.2 2545 20 Dec 2004 Fixed 9.0.1 1965 20 Dec 2004 Fixed 9.0.0 1392 20 Dec 2004 Fixed Description In the Java class description and source details panels, the line and column indicators were missing from the status bar. This has now been fixed.

CR:375268

CR Number:   375268 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) 2995 21 Dec 2004 Fixed 9.0.2 2546 21 Dec 2004 Fixed Description Interactive SQL (and the ASA plug-in for Sybase Central) were displaying UNIQUEIDENTIFIER values as hexadecimal strings, of the form "0xaabbccddeeffgghhiijjkkllmmnnoopp". Now it displays them using the usual GUID notation: "aabbccdd-eeff-gghh-iijj-kkllmmnnoopp".

CR:375325

CR Number:   375325 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) 2977 11 Jan 2005 Fixed 9.0.2 2531 11 Jan 2005 Fixed 9.0.1 1971 11 Jan 2005 Fixed Description On non-English platforms, db_property('PlatformVer') and db_property('CompactPlatformVer') could have returned mangled strings. This problem also affected graphical plans, which include these properties in their output. The problem could have caused Interactive SQL to fail to display the results of a query containing these functions. This has been fix. The descriptive string returned from the OS was not being converted to the server's character set, now it is. This was only likely to cause problems when connected to a database using jConnect, but it may possibly have affected the ODBC and ESQL drivers as well, and was most likely to affect servers running on Chinese and Japanese non-Windows OS versions.

CR:375327

CR Number:   375327 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) 2995 21 Dec 2004 Fixed 9.0.2 2453 21 Dec 2004 Fixed 9.0.1 1966 21 Dec 2004 Fixed Description If the -o switch was used on the server to specify a message log output file, and the file could not be opened, a message was displayed in the server console window, and the server started anyway. This has been fixed, now if the output file cannot be opened, the server will report an error and will not start.

CR:375341

CR Number:   375341 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) 2998 22 Dec 2004 Fixed 9.0.2 2546 22 Dec 2004 Fixed 9.0.1 1967 22 Dec 2004 Fixed Description The Index Consultant may have reported 'identifier ... too long' during analysis, and failed to continue. This could have happened if the queries being analyzed were over tables with long names and columns with long names. This has been fixed.

CR:375348

CR Number:   375348 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) 2995 20 Dec 2004 Fixed 9.0.2 2453 20 Dec 2004 Fixed Description Calls to web services client functions could have failed with error -981 ("Unable to connect to the remote host specified by '<URL>'") when the server was running on NetWare systems. This would only happen if more than one client called web services client functions at the same time. This has now been fixed.

CR:375368

CR Number:   375368 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) 2996 21 Dec 2004 Fixed 9.0.2 2546 21 Dec 2004 Fixed 9.0.1 1966 21 Dec 2004 Fixed Description UltraLite UNICODE ODBC did not handle DECL_DECIMAL properly. The conversion to string, required by the ODBC definition, did not append a null delimiter character to the converted string with UNICODE. This has been fixed.

CR:375369

CR Number:   375369 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) 2996 21 Dec 2004 Fixed 9.0.2 2546 21 Dec 2004 Fixed 9.0.1 1966 21 Dec 2004 Fixed 9.0.0 1393 21 Dec 2004 Fixed Description When debugging a procedure or a Java class, if the editor was open when the breakpoints dialog was closed, it scrolled back to line 1. This has been fixed.

CR:375421

CR Number:   375421 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3002 06 Jan 2005 Fixed 9.0.2 2548 06 Jan 2005 Fixed 9.0.1 1969 06 Jan 2005 Fixed Description The MobiLink server may have hung, with 100% CPU usage, when fetching user scripts containing Japanese characters, if the consolidated database was an Oracle database with Japanese character set JA16SJISTILDE, and the MobiLink server was running on a Japanese OS and used the Data Direct native ODBC driver 4.20.00.xx for Oracle. A work around for a problem in the Data Direct driver has been implemented.

CR:375586

CR Number:   375586 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 1609 11 Feb 2005 Fixed 9.0.2 3032 11 Feb 2005 Fixed 9.0.1 1986 11 Feb 2005 Fixed Description The following Connection events were missing from the combo box in the Connection Script wizard: authenticate_parameters, begin_publication, end_publication, and modify_error_message. This meant that it was not possible to use Sybase Central to create scripts for these events. These events have now been added.

CR:375757

CR Number:   375757 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   HP-UX Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3002 04 Jan 2005 Fixed 9.0.2 2548 04 Jan 2005 Fixed 9.0.1 1969 04 Jan 2005 Fixed 8.0.3 5200 04 Jan 2005 Fixed Description If a BACKUP or RESTORE statement was executed from the Open Client Isql utility, while the backup.syb file was marked as read-only, the server could have crashed. This has been fixed.

CR:375851

CR Number:   375851 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3008 10 Jan 2005 Fixed 9.0.2 2551 10 Jan 2005 Fixed 9.0.1 1971 10 Jan 2005 Fixed Description When using UltraLite Dynamic SQL, a LIKE condition could have produced incorrect results, if the left operand was a column which occurred first in an index, and that column was larger than 126 characters. This has now been fixed.

CR:375971

CR Number:   375971 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3009 11 Jan 2005 Fixed 9.0.2 2551 11 Jan 2005 Fixed 9.0.1 1972 11 Jan 2005 Fixed 8.0.3 5203 11 Jan 2005 Fixed 7.0.4 3536 11 Jan 2005 Fixed Description An application could have hung, received a communication error, or have possibly seen other incorrect behaviour, when doing a fetch with prefetch enabled, and then immediately doing a commit, rollback, or another fetch with an absolute or negative offset. It was rare on multiprocessor machines, and would have been even rarer on single processor machines. As well, there may have been other timing dependent cases which could have failed. This has been fixed.

CR:376019

CR Number:   376019 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.3 5201 07 Jan 2005 Fixed 8.0.2 4511 07 Jan 2005 Fixed Description Executing queries containing the GROUP BY clause could have caused the server to crash. The changes for Engineering Case 332010, and a related change for case 363861, introduced the problem, which has now been fixed.

CR:376104

CR Number:   376104 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) 3008 11 Jan 2005 Fixed 9.0.2 2551 11 Jan 2005 Fixed Description When processing an INSERT statement, the value of in inserted expression could have had the wrong value if it was a complex expression involving NUMBER(*). This has now been fixed. For example, the following would have generated incorrect results: BEGIN DECLARE LOCAL TEMPORARY TABLE t ( row_number INTEGER ); INSERT t SELECT 2 + NUMBER(*) AS row_number ORDER BY dummy_col; SELECT * FROM t; END;

CR:376133

CR Number:   376133 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   7.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 7.0.4 3536 07 Jan 2005 Fixed Description The MobiLink server could have behaved incorrectly, (invoked the begin_synchronization scripts, for instance), or even crashed, if there were network or client problems before the server received the full upload stream. This problem is now fixed.

CR:376202

CR Number:   376202 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3023 27 Jan 2005 Fixed 9.0.1 1978 27 Jan 2005 Fixed Description Installing an EBF may have abnormally terminated as it was about to copy files to the target system. This has been fixed.

CR:376210

CR Number:   376210 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 1586 24 Jan 2005 Fixed 9.0.2 3021 24 Jan 2005 Fixed 9.0.1 1976 24 Jan 2005 Fixed Description The server could have crashed while performing Index Consultant analysis on a complex query. This was only likely to happen in queries with numerous equality predicates, and either an ORDER BY, GROUP BY, or SELECT DISTINCT clause. This has been fixed.

CR:376229

CR Number:   376229 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) 3005 07 Jan 2005 Fixed 9.0.2 2550 07 Jan 2005 Fixed Description Version 6.0.x clients were not able to connect to 9.0.2 servers over TCP/IP. This has been fixed.

CR:376444

CR Number:   376444 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3008 11 Jan 2005 Fixed 9.0.2 2551 11 Jan 2005 Fixed 9.0.1 1971 11 Jan 2005 Fixed Description If a view V1 caused a warning to be given when referenced (e.g. the result returned is non-deterministic), and another view V2 referenced V1, and the definition of V2 was output into the reload.sql script by DBUNLOAD before the definition of V1, then V2 may not have appeared in the database after the reload.sql script has run. This has been fixed. ALTER VIEW ... RECOMPILE did not handle a warning being set while building a cursor for the view. The warning is now cleared before making catalog changes and then is restored.

CR:376453

CR Number:   376453 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.3 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.0 1595 28 Jan 2005 Fixed 9.0.2 3024 28 Jan 2005 Fixed 9.0.1 1979 28 Jan 2005 Fixed 8.0.3 5211 28 Jan 2005 Fixed 8.0.2 4516 28 Jan 2005 Fixed Description An ADO .Net application that attempted to obtain the primary keys from a query on a table using the OLEDB provider, may have been returned incorrect results when the table had more than one primary key column and/or columns with unique constraints or unique indexes. A sample code fragment follows: DataTable Table = new DataTable(textTableName.Text); OleDbDataAdapter adapter; OleDbConnection connection = new OleDbConnection(textConnectionString.Text); using (connection) { try { connection.Open(); adapter = new OleDbDataAdapter("select * from dba." + textTableName.Text + " where 1=0", connection); adapter.MissingSchemaAction = MissingSchemaAction.AddWithKey; adapter.Fill(Table); listBox1.Items.Clear(); foreach(DataColumn col in Table.PrimaryKey) { listBox1.Items.Add(col.ColumnName); } } catch (Exception ex) { MessageBox.Show(ex.Message); } } The DataTable PrimaryKey property is an array of columns that function as primary keys for the data table. This problem has been fixed. One of the elements that ADO.Net uses in deciding whether a column belongs in this set is the column metadata rowset. IColumnsRowset::GetColumnsRowset - Returns a rowset containing metadata about each column in the current rowset. This rowset is known as the column metadata rowset and is read-only. The optional Metadata Column DBCOLUMN_KEYCOLUMN is described to contain one of the values VARIANT_TRUE or VARIANT_FALSE or NULL. VARIANT_TRUE The column is one of a set of columns in the rowset that, taken together, uniquely identify the row. The set of columns with DBCOLUMN_KEYCOLUMN set to VARIANT_TRUE must uniquely identify a row in the rowset. There is no requirement that this set of columns is a minimal set of columns. This set of columns may be generated from a base table primary key, a unique constraint or a unique index. VARIANT_FALSE The column is not required to uniquely identify the row. This column used to contain VARIANT_TRUE or VARIANT_FALSE. It now contains NULL since OLEDB cannot correctly set the value. As a result, ADO.Net uses other means for determining which columns belong in the PrimaryKey columns property.

CR:376554

CR Number:   376554 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3009 11 Jan 2005 Fixed 9.0.2 2551 11 Jan 2005 Fixed Description Upgrading an Oracle 8.1.7 database server, used as a consolidated database by MobiLink, from ASA version 9.0.1 to version 9.0.2 would have failed if the standard upgrade script MobiLink\upgrade\9.0.1\upgrade_ora.sql was used. This script has beed fixed. The failure was as a result of trying to upgrade the data in QAnywhere system tables, so if QAnywhere is not being used, or the existing QAnywhere data does not matter, the failure can be ignored, and the rest of the script executed. If any QAnywhere data is required to be preserved, the fixed script is needed.

CR:376567

CR Number:   376567 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3009 11 Jan 2005 Fixed 9.0.2 2551 11 Jan 2005 Fixed Description Message delivery would have been slow to QAnywhere clients using the "automatic" policy, with push notifications enabled. Message delivery to the server was fast, but the server was slow using push notifications to the message addressee to indicate that a message for the addressee was available. By default, the delay in the notification could be up to 60 seconds. This has been fixed. As a work-around however, the server option "ianywhere.qa.server.autoRulesEvaluationPeriod" can be set in the server configuration file to a lower number, for example 5000 (milliseconds), to speed-up notification check process.

CR:376606

CR Number:   376606 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) 3009 14 Jan 2005 Fixed 9.0.2 2551 14 Jan 2005 Fixed 9.0.1 1972 14 Jan 2005 Fixed 8.0.3 5203 14 Jan 2005 Fixed Description Creating a COMMENT on a local temporary table would have caused the server to fail with assertion 201501 - "Page for requested record not a table page or record not present on page". Example: declare local temporary table temp1(c1 int); comment on table temp1 is 'my comment'; Now an error is returned when attempting to add a comment to a local temporary table.

CR:376608

CR Number:   376608 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) 3009 13 Jan 2005 Fixed 9.0.2 2551 13 Jan 2005 Fixed 9.0.1 1972 13 Jan 2005 Fixed 8.0.3 5203 13 Jan 2005 Fixed Description If an Open Client application opened a cursor which cuased the warning: "cursor options changed", the application would have failed to open the cursor. This problem has now been fixed. There are situations where Open Client applications are not expecting warnings, so certain warnings that are known to not be handled are suppressed, while other warnings are sent as the client actually expects them. The "cursor options changed" warning has been added to this list of warnings not to be returned to an Open Client applications.