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

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

CR:365083

CR Number:   365083 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2410 26 Aug 2004 Fixed 9.0.1 1910 26 Aug 2004 Fixed 9.0.0 1354 26 Aug 2004 Fixed Description If either the MobiLink Synchonization server or the MobiLink client encountered an HTTP header in a request or a reply that was larger than 256 bytes, the synchronization would fail. This has been fixed.

CR:365147

CR Number:   365147 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) 9.0.2 2425 07 Sep 2004 Fixed 9.0.1 1918 08 Sep 2004 Fixed 9.0.0 1359 08 Sep 2004 Fixed 8.0.3 5156 08 Sep 2004 Fixed 8.0.2 4471 08 Sep 2004 Fixed 7.0.4 3532 08 Sep 2004 Fixed Description When using the -m command line option (truncate transaction log after checkpoint), if a transaction log file was being actively defragmented or virus scanned at the time a checkpoint occurred, then the server could have failed with assertion 101201. The operating system will not allow the file to be recreated until the virus scan or defragmentation has completed. As a result, the server will now wait and retry the operation several times. A workaround would be to remove the transaction log file from the list of files that are actively scanned or defragmented.

CR:365154

CR Number:   365154 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   7.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1906 26 Aug 2004 Fixed Description MobiLink clients now support Digest HTTP authentication to third-party HTTP proxies and servers as described in RFC 2617, in addition to Basic authentication. The same synchronization parameters are used to supply the userid and password as for Basic authentication. The HTTP server or proxy configuration determines whether Basic or Digest is used in the "WWW-Authenticate" or "Proxy-Authenticate" HTTP header they send to the client. The difference between Basic and Digest is that Digest employs various security mechanisms to protect the password and to protect from common types of attacks, while with Basic, the password is sent in clear text. However, HTTPS provides far better security than Digest, so it is recommended that Basic HTTP authentication be used with HTTPS for full security. The only situation where Digest authentication is really useful is when connecting through a client-side proxy which doesn't support HTTPS directly, but requires authentication.

CR:365173

CR Number:   365173 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2413 26 Aug 2004 Fixed 9.0.1 1913 26 Aug 2004 Fixed Description If an ODBC application called SQLGetInfoW() to get the user name or collation sequence from a database using a Multibyte Character Set, then the conversion to UNICODE would likely have been wrong. This problem has been fixed.

CR:365188

CR Number:   365188 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 2426 31 Aug 2004 Fixed 9.0.1 1915 01 Sep 2004 Fixed 9.0.0 1356 01 Sep 2004 Fixed 8.0.3 5153 01 Sep 2004 Fixed 8.0.2 4468 01 Sep 2004 Fixed Description If a view was defined with the "WITH CHECK OPTION" clause and had predicates using subqueries, then opening an updatable cursor or executing an UPDATE statement might have caused a server crash. This has been fixed. For example: create view products as select p.* from prod as p where p.id = any(select soi.prod_id from sales_order_items soi KEY JOIN sales_order so where so.order_date > current date ) with check option The following INSERT statement would have crashed the server: insert into products (id) values ( 1001 )

CR:365210

CR Number:   365210 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) 9.0.2 2413 26 Aug 2004 Fixed 9.0.1 1912 26 Aug 2004 Fixed Description When the QAnywhere Agent was invoked in quiet mode (-q command line option) on Windows CE, the window did not appear in the System Tray. Now, when qaagent is invoked with -q, the window is minimized in the system tray. As well, a new command line option has been added: -qi, which causes the window to be completely hidden (and not appear in the System Tray). This is similar behaviour to the database server.

CR:365223

CR Number:   365223 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.2 2413 27 Aug 2004 Fixed 9.0.1 1913 27 Aug 2004 Fixed Description The MobiLink Synchronization server may displayed a "Protocol error" message and aborted the synchronization, if - it was running without the command line option -s or with -s n, where n > 1; - errors occurred during upload of table data; - the handle_error (hand_odbc_error) script returned 1000; and - the upload was a transactional upload. This problem has been fixed.

CR:365330

CR Number:   365330 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2414 27 Aug 2004 Fixed 9.0.1 1913 27 Aug 2004 Fixed 9.0.0 1355 27 Aug 2004 Fixed Description When an ODBC application retrieved certain metadata values in Unicode, like the column name of a result set column, the returned value could have been truncated. This could have occurred, even though the specified buffer was large enough to hold the Unicode value. It was also probable that no truncation error would have been returned to the application. Both of these problem have now been fixed.

CR:365342

CR Number:   365342 Product Name:   UltraLite Product Component:   Code Generator Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2986 15 Dec 2004 Fixed 9.0.2 2543 15 Dec 2004 Fixed 9.0.1 1963 15 Dec 2004 Fixed Description The UltraLite Generator ulgen, could have crashed when generating code that included an index with the same column specified more than once. In some cases, it would run correctly, but then the application that used the generated code would have crashed when executing the query that used an index with the same column specified more than once. Having a column specified multiple times in an index is not supported by UltraLite (and would not provide any performance benefits anyway). An error message is now displayed and the application exits. The workaround to this problem is to remove the extra column definitions from the index definition.

CR:365453

CR Number:   365453 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) 9.0.2 2433 15 Sep 2004 Fixed 9.0.1 1921 15 Sep 2004 Fixed 9.0.0 1362 15 Sep 2004 Fixed 8.0.3 5158 15 Sep 2004 Fixed Description Calling a wrapper procedure for a Java class which returned a result set would have leaked memory and could have crashed the server. This has now been fixed.

CR:365457

CR Number:   365457 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.2 4468 31 Aug 2004 Fixed Description It was possible for the optimizer to chose a query access plan that did a sequential scan of a base table, even when a suitable and more efficient clustered index was available, resulting in poor performance. This choice was particularly bothersome for reasonably wide range scans, (thousands of rows), over very large tables, (millions of rows). The server now does a better job of costing clustered index scans.

CR:365460

CR Number:   365460 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) 9.0.2 2417 30 Aug 2004 Fixed 9.0.1 1914 30 Aug 2004 Fixed 9.0.0 1356 30 Aug 2004 Fixed 8.0.3 5153 30 Aug 2004 Fixed 8.0.2 4467 30 Aug 2004 Fixed Description An application that used GetData to retrieve an unbound column on the first row, could have had poor performance, if prefetch was enabled and some, but not all columns, were bound before the first fetch. This poor performance would have been particularly noticeable if the first few rows of the query were expensive to evaluate. Applications which used the iAnywhere JDBC driver, on queries which had columns with type LONG VARCHAR or LONG BINARY, were also affected by this poor performance. This has been fixed.

CR:365465

CR Number:   365465 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2412 31 Aug 2004 Fixed 9.0.1 1912 31 Aug 2004 Fixed Description The redirector for Apache would have truncated HTTP headers that were longer than 128 bytes. This has been fixed.

CR:365466

CR Number:   365466 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2412 31 Aug 2004 Fixed 9.0.1 1913 31 Aug 2004 Fixed Description The redirector for Apache would have forwarded the 'Authorization' header. This has been changed so that the redirector now ignores this header and does not forward it. It is not expected that webservers will run behind the redirector, hence there is no need to forward this Authorization header, which could contain a userid and a password in clear text in the case of Basic authentication.

CR:365480

CR Number:   365480 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.3 5153 31 Aug 2004 Fixed 8.0.2 4467 31 Aug 2004 Fixed Description When running on NetWare systems, if the ASA server failed with a fatal error, the NetWare server would have abended. This has been fixed.

CR:365498

CR Number:   365498 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 2418 01 Sep 2004 Fixed 9.0.1 1915 01 Sep 2004 Fixed Description Executing a query that involved a proxy table and the openxml() function, as in the following example: select * from proxy_test p, (select PKID, C1 from openxml( @varxml, '//testxml/test') with(PKID int 'PKID', C1 varchar(255) 'C1')) t where p.PKID = t.PKID could have caused a server crash. This problem has been fixed.

CR:365502

CR Number:   365502 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2978 09 Dec 2004 Fixed 9.0.2 2541 09 Dec 2004 Fixed 9.0.1 1960 09 Dec 2004 Fixed 9.0.0 1391 09 Dec 2004 Fixed Description When upgrading Mobilink from version 6.0.x, 7.0.x or 8.0.x, if the consolidated database was Oracle version 8i, the upgrade script would have failedwith the following error: ERROR at line 1: ORA-06550: line 1, column 7: PLS-00905: object FPSADMIN.ML_SCRIPT_UPGRADE is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored execute ml_script_upgrade -- failed The problem is that Oracle 8i does not support the conversion from LONG to CLOB. This has been fixed by using an Oracle provided function TO_LOB() instead. Workaround Description  Two workarounds, I'd urge the use of either of them to get them implemented in the upgrade scripts Workaround #1 In the two CREATE OR REPLACE PROCEDURE statements in question, replace "long" with "longchar" Workaround #2 Replace the two CREATE OR REPLACE PROCEDURE statements in question, and the exec line after that, with insert into ml_script select script_id, script, script_language from ml_script_temp / commit / and insert into ml_script_version select version_id, name, description from ml_script_version_temp / commit / Note: Why make it complicated when a single insert does the job?

CR:365508

CR Number:   365508 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) 9.0.2 2405 31 Aug 2004 Fixed 9.0.1 1908 31 Aug 2004 Fixed 9.0.0 1352 31 Aug 2004 Fixed 8.0.3 5148 31 Aug 2004 Fixed 8.0.2 4462 31 Aug 2004 Fixed Description When used with multiple Java Threads, and Synchronized Java Methods, Java Stored Procedures could have produced unexpected results. This has niw been fixed.

CR:365537

CR Number:   365537 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2421 07 Sep 2004 Fixed 9.0.1 1916 07 Sep 2004 Fixed Description When rebuilding a database with the Unload utility dbunload, and using the command line options -an or ar along with the -ap option, a START connection parameter in an ODBC data source was ignored, if the connection string contained a DSN parameter and no START parameter. This problem has been fixed

CR:365603

CR Number:   365603 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) 9.0.2 2420 31 Aug 2004 Fixed 9.0.1 1915 01 Sep 2004 Fixed 8.0.3 5159 15 Sep 2004 Fixed 8.0.2 4474 15 Sep 2004 Fixed Description Making an RPC call, or executing a FORWARD TO statement, may have failed to return a result set, even though one was returned by the remote server. Note that this problem only happened when the Remote Data Access class was either ASAJDBC or ASEJDBC. This has been corrected.

CR:365688

CR Number:   365688 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 09 Sep 2004 Presently Not Targeted For Any Future Release Of This Product Description Enhance dbltm to allow stored procedures written in Watcom SQL to be sent correctly to Replication Server. Workaround Description  Re-write stored procedures in Transact-SQL

CR:365707

CR Number:   365707 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 2426 09 Sep 2004 Fixed 9.0.1 1915 02 Sep 2004 Fixed 9.0.0 1357 02 Sep 2004 Fixed Description The JOIN MERGE FULL OUTER join method was not considered by the optimizer during optimization of queries using FULL OUTER JOINs. This has been fixed.

CR:365730

CR Number:   365730 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) 9.0.2 2419 02 Sep 2004 Fixed 9.0.1 1915 02 Sep 2004 Fixed 9.0.0 1357 02 Sep 2004 Fixed 8.0.3 5154 02 Sep 2004 Fixed 8.0.2 4469 02 Sep 2004 Fixed Description If a server attempted to start what appeared to be a valid database file, and the database failed to start for any reason, then unexpected behavior could have occurred on future requests to the same server. The unexpected behavior could have included server crashes, assertions, and possibly database corruption. This has been fixed.

CR:365731

CR Number:   365731 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2420 07 Sep 2004 Fixed 8.0.3 5154 08 Sep 2004 Fixed Description When a dialog was opened from another dialog (rather than from the main window), closing the topmost dialog would have returned focus to the main window, instead of the initial dialog. This has been corrected.

CR:365797

CR Number:   365797 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) 9.0.2 2419 02 Sep 2004 Fixed 9.0.1 1915 02 Sep 2004 Fixed 9.0.0 1357 02 Sep 2004 Fixed Description The changes for Engineering Case 364610 prevented the Interactive SQL utility dbisql, when using the iAnywhere JDBC driver, from connecting to the utility database. This is now fixed. Note, this was not a problem when connecting via jConnect.

CR:365837

CR Number:   365837 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.1 1929 05 Oct 2004 Fixed 9.0.0 1371 05 Oct 2004 Fixed Description After completing an Index Consultant analysis, if the 'Requests' pane of the analysis was selected and a particular statement was viewed, the server would have appeared to be hung at 100% CPU usage. This only occurred when there were a large number (many thousands) of captured SQL statements. It was also more likely to occur when the captured SQL statement strings were very similar to each other, or were very long. The server was not actually hung, and would have eventually displayed the details for the request, although this would have taken an inordinate amount of time. This has been corrected.

CR:365928

CR Number:   365928 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2421 07 Sep 2004 Fixed 9.0.1 1916 07 Sep 2004 Fixed Description When rebuilding a databse with the Unload utility dbunload and using the -ar or -an command line options, if the original database had page checksums enabled, the new database would not have had page checksums enabled. This has been fixed.

CR:365929

CR Number:   365929 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1922 17 Sep 2004 Fixed 9.0.2 2529 17 Sep 2004 Fixed 2925 17 Sep 2004 Fixed Description An UltraLite application would have crashed on the final step of the following sequence: - Execute a query that contains a temp table - Suspend and close the connection - Re-connect to the database - Apply a new schema file This has been fixed.

CR:365938

CR Number:   365938 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2421 07 Sep 2004 Fixed Description A crash in the UltraLite runtime libraries would have occurred if the "page_size" connection parameter was specified with a value that did not match the database being opened, or if you a database with 2Kb pages was opened without specifying "page_size=2k". Now, the page_size parameter (or lack of it) is ignored if the database already exists.

CR:365940

CR Number:   365940 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2425 07 Sep 2004 Fixed 9.0.1 1918 07 Sep 2004 Fixed 9.0.0 1359 07 Sep 2004 Fixed 8.0.3 5156 07 Sep 2004 Fixed 8.0.2 4471 07 Sep 2004 Fixed Description If the trantest sample application (PerformanceTransaction), was executed with -a odbc -n <threadcount> and the thread count was higher than one it may have crashed in NTDLL.DLL. This has been fixed.

CR:365953

CR Number:   365953 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 2529 20 Sep 2004 Fixed 9.0.1 1922 20 Sep 2004 Fixed 9.0.0 1364 20 Sep 2004 Fixed 8.0.3 5160 20 Sep 2004 Fixed 8.0.2 4476 20 Sep 2004 Fixed Description If a user-defined function contained a COMMIT, calling the function in a SELECT statement within a batch or procedure would have caused the cursor for the batch or procedure to be closed if the cursor was not declared WITH HOLD. This may have resulted in unexpected error messages like "Column '@var' not found". Now these cursors will not be closed.

CR:365955

CR Number:   365955 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) 9.0.2 2421 07 Sep 2004 Fixed 9.0.1 1916 07 Sep 2004 Fixed Description On Windows CE, the C++ API method QATextMessage.readText(string, length) returned the number of qa_char's read, including the null terminator, when there were fewer qa_char's available than the number requested. This problem has been fixed. The method now returns the number of non-null qa_char's read, as documented.

CR:366062

CR Number:   366062 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.2 2425 09 Sep 2004 Fixed 9.0.1 1918 09 Sep 2004 Fixed 9.0.0 1360 09 Sep 2004 Fixed Description Incorrect results could have been generated by UltraLite Dynamic SQL when there existed a DISTINCT clause, a join of tables in the FROM clause, and there are no group-by expressions in the select list, for at least one of the tables. For example: SELECT DISTINCT b.key FROM tab_a a, tab_b b WHERE a.column = b.key This situation requires a temporary table which will now be generated.

CR:366096

CR Number:   366096 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2426 07 Sep 2004 Fixed 9.0.1 1918 08 Sep 2004 Fixed Description A call to the RANK(), DENSE_RANK(), PERCENT_RANK(), or CUME_DIST() functions now reports error -154 : "Wrong number of parameters to function", when called with an argument. Previously, the error -134 : "Feature not implemented", would have been given.

CR:366099

CR Number:   366099 Product Name:   SQL Anywhere Product Component:   Documentation Status:   Closed OS:   Microsoft Windows Original Version:   7.0.4 Fixed Version Build Resolution Date Closure Code (If Appropriate) 08 Sep 2004 Fixed Description Expand explanation on Message property of database in doc set

CR:366150

CR Number:   366150 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) 9.0.2 2425 08 Sep 2004 Fixed 9.0.1 1918 08 Sep 2004 Fixed 9.0.0 1359 08 Sep 2004 Fixed 8.0.3 5156 08 Sep 2004 Fixed 8.0.2 4471 08 Sep 2004 Fixed Description The server could have become deadlocked when executing the system procedure sa_locks. For this to have occurred, two connections must have been issuing sa_locks calls concurrently, or the user definition for the owning connection was not in cache, which is not a likely occurence. This problem has been fixed.

CR:366155

CR Number:   366155 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2921 09 Sep 2004 Fixed 9.0.2 2921 21 Jan 2005 Fixed Description When the Listener utility was started with the -t command line option, (enable or disable remote tracking for a remote database), without using a -x option for device tracking, the -t option would have been silently ignored. This behavior has been changed so that the listener will no longer start up, but will instead fail with an error.

CR:366167

CR Number:   366167 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) 2922 09 Sep 2004 Fixed 9.0.2 2427 09 Sep 2004 Fixed 9.0.1 1919 09 Sep 2004 Fixed 9.0.1 1919 09 Sep 2004 Fixed 8.0.3 5157 09 Sep 2004 Fixed 8.0.2 4472 09 Sep 2004 Fixed Description Database recovery could have failed when mixing Transact-SQL and Watcom SQL dialects for Create/Drop table statements. This has been fixed. The following example could have caused database recovery to fail if the server crashed before the next checkpoint. create global temporary table #test (col1 int, col2 int); drop table #test; create global temporary table #test (col1 int, col2 int); drop table #test; A workaround is to only use #table_name for creation of local temporary tables.

CR:366170

CR Number:   366170 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1970 15 Dec 2004 Fixed Description When using an Oracle stored procedure to insert multiple rows with a multiple row array, the version 4.20.00.28 iAnywhere Solutions Oracle WP driver would fail with the error "ORA-01460: unimplemented or unreasonable conversion requested (ODBC State = HY000, Native error code = 1460)". Single row inserts worked fine. This only affected Windows systems, and has been fixed in version 4.20.00.81(B0067,U0062) of the driver. The following files have been updated: wqora19.dll wqora19r.dll wqora19s.dll wqicu19.dlll In the DSN setting, the option "Procedure Returns Results" must be selected.

CR:366233

CR Number:   366233 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) 9.0.2 2528 10 Sep 2004 Fixed 9.0.1 1919 10 Sep 2004 Fixed 9.0.0 1361 10 Sep 2004 Fixed 8.0.3 5158 10 Sep 2004 Fixed 8.0.2 4472 10 Sep 2004 Fixed Description If a stored procedure contained a statement that performed a sequential scan of a global temporary table, executing the statement could have caused the server to crash. This problem would have occurred if the following conditions held: - The statement plan was cached - The table was declared as "ON COMMIT DELETE ROWS" - The table had more than 100 pages when the plan was cached - COMMIT was called before the statement was executed This problem has been fixed. The crash could be avoided by setting the option 'Max_plans_cached' to 0.

CR:366267

CR Number:   366267 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 2529 16 Sep 2004 Fixed 9.0.1 1921 16 Sep 2004 Fixed 9.0.0 1363 16 Sep 2004 Fixed 8.0.3 5129 16 Sep 2004 Fixed 8.0.2 4474 01 Oct 2004 Fixed Description When the database option Ansi_close_cursors_on_rollback was set to 'ON', the Validation utility dbvalid would have failed to validate all the tables in the database. The error 'cursor not open' would have been displayed. This has been fixed.

CR:366282

CR Number:   366282 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) 9.0.2 2427 10 Sep 2004 Fixed 9.0.1 1918 10 Sep 2004 Fixed 8.0.3 5157 10 Sep 2004 Fixed 8.0.2 4472 10 Sep 2004 Fixed Description The CREATE SCHEMA statement was not being logged correctly in the transaction log if it contained at least one CREATE VIEW statement. The statement logged was the last CREATE VIEW statement, instead of the entire CREATE SCHEMA statement. As a consequence, the CREATE SCHEMA statement was not recoverable. Also, recovery could have failed with a "Failed to redo an operation" assertion, if the logged CREATE VIEW statement could not have been executed, e.g., because it referred to a table created within the original CREATE SCHEMA statement. This problem has been resolved.

CR:366292

CR Number:   366292 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 2426 09 Sep 2004 Fixed 9.0.1 1918 09 Sep 2004 Fixed 9.0.0 1360 09 Sep 2004 Fixed Description If a database created with version 6, 7 or 8 software, was upgraded using the Upgrade utility dbupgrad, or by executing the ALTER DATABASE UPGRADE statement, then the resulting reload.sql script generated by the Unload utility dbunload, would have contained a CREATE PROCEDURE statement for sa_proc_debug_detach_from_connection which would have failed. This has been fixed. Workarounds include dropping the procedure after the upgrade, or simply not performing the upgrade (since it should be unnecessary).

CR:366293

CR Number:   366293 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2426 10 Sep 2004 Fixed Description Static C++ applications, running on Palm devices, may have had data truncated from the beginning of values fetched from the database. The amount missing depended on which column was fetched. The first column was always fetched properly. This has been fixed.

CR:366362

CR Number:   366362 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) 9.0.2 2427 10 Sep 2004 Fixed 9.0.1 1919 10 Sep 2004 Fixed 9.0.0 1360 10 Sep 2004 Fixed Description If a result set returned a LONG VARCHAR or LONG BINARY column, and one of the values of that column was empty, then retrieving that empty result would have caused the iAnywhere JDBC driver to leak memory. This problem has been fixed.

CR:366364

CR Number:   366364 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) 9.0.2 2427 10 Sep 2004 Fixed 9.0.1 1919 10 Sep 2004 Fixed 8.0.3 5157 10 Sep 2004 Fixed 8.0.2 4472 10 Sep 2004 Fixed Description Database validation, using either the Validation utility dbvalid, or executinmg the VALIDATE DATABASE statement, could have failed to detect some corrupted LONG VARCHAR columns. Assertion 202000 is now generated when a corrupted LONG VARCHAR is encountered.

CR:366375

CR Number:   366375 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 2428 13 Sep 2004 Fixed 9.0.1 1919 13 Sep 2004 Fixed Description When evaluating the use of an index to satisfy a range predicate on a table that was occupying a large fraction of the server cache, the query optimizer could have failed to make use of the index, resulting in poor query access plans. This problem has been resolved.

CR:366401

CR Number:   366401 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.2 2529 22 Sep 2004 Fixed 9.0.1 1925 22 Sep 2004 Fixed 9.0.0 1368 22 Sep 2004 Fixed 8.0.3 5164 22 Sep 2004 Fixed 8.0.2 4479 22 Sep 2004 Fixed Description Rebuilding databases on Unix systems, using the Unload utility dbunload with the -ar or -an command line options, would have failed during the rebuild operation, if the source database had table or row constraints that specified stored procedures. This has been fixed.

CR:366422

CR Number:   366422 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.2 2420 13 Sep 2004 Fixed 9.0.1 1919 13 Sep 2004 Fixed 9.0.0 1361 13 Sep 2004 Fixed Description If a procedure had a subquery that involved a remote table, and if that subquery generated a warning, then the server would have incorrectly given an error rather than returned the result of the subquery. For example: SET @c = (SELECT count(*) FROM t) where t is a remote table. In this case, if the table t was empty, then a NOT FOUND warning would have been generated when the subquery was evaluated and instead of setting the variable @c to 0, the server would have returned the error "ASA Error -823: OMNI cannot handle expressions involving remote tables inside stored procedures ". This problem has now been fixed.

CR:366428

CR Number:   366428 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) 9.0.2 2422 13 Sep 2004 Fixed 9.0.1 1919 13 Sep 2004 Fixed 9.0.0 1361 13 Sep 2004 Fixed 8.0.3 5158 13 Sep 2004 Fixed 8.0.2 4472 13 Sep 2004 Fixed Description The AsaCommandBuilder class could not have generated INSERT, UPDATE or DELETE statements for parameterized queries if the parameters were not provided. Now, if the command is a stored procedure, the AsaClient will call AsaCommandBuilder.DeriveParameters to add parameters for the SELECT command. If the command is text, the AsaClient will add some dummy parameters.

CR:366503

CR Number:   366503 Product Name:   MobiLink Product Component:   Charset Conversion (UNILIB) Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 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 1928 30 Sep 2004 Fixed Description When using the .NET scripting, Character fields moving to or from the database may have been corrupted if they contained non-ascii characters. These fields will now be bound as Unicode. Current user code can remain unchanged and should continue to work.

CR:366510

CR Number:   366510 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) 2928 23 Sep 2004 Fixed 9.0.2 2529 23 Sep 2004 Fixed 9.0.1 1925 23 Sep 2004 Fixed Description The quality of access plans chosen for queries with joins to tables with few rows, that can make use of indexes, has been improved.

CR:366532

CR Number:   366532 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) 9.0.2 2427 13 Sep 2004 Fixed 9.0.1 1918 13 Sep 2004 Fixed 9.0.0 1360 13 Sep 2004 Fixed 8.0.3 5157 13 Sep 2004 Fixed 8.0.2 4471 13 Sep 2004 Fixed Description Computed columns with JAVA expressions may have be incorrectly parsed, causing the error: "ASA Error -94: Invalid type or field reference". This problem occurred if the computed column belonged to a table B, and there existed another table A, used in the same statement, having a column with the same name as the JAVA class name. This has been fixed. For example: The following query returned the error "ASA Error -94: Invalid type or field reference": select * FROM A WHERE A.ID NOT IN ( SELECT B.ID FROM B ); Table B has the computed column "EntityAddressId" referencing the JAVA class "Address", and table A has a base table column named "Address". Note that the computed column doesn't have to be referenced in the query. CREATE TABLE A ( ID int, "Address" varchar (10) ); CREATE TABLE B ( ID int, "EntityAddressId" numeric(10,0) NULL COMPUTE (Address >> FindAddress(0, '/', 0)), );

CR:366552

CR Number:   366552 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) 9.0.2 2434 15 Sep 2004 Fixed 9.0.1 1921 15 Sep 2004 Fixed 9.0.0 1363 15 Sep 2004 Fixed 8.0.3 5159 15 Sep 2004 Fixed 8.0.2 4474 15 Sep 2004 Fixed Description When making a remote procedure call to a remote server whose class was either ASAJDBC or ASEJDBC, if the remote procedure was a Transact-SQL procedure, with either an INOUT or OUT argument that returned a result set, then it was likely that the rows in the result set will not have been returned. The INOUT or OUT parameters were incorrectly being fetched first, prior to fetching the result set. In JDBC, fetching the value of an OUT or INOUT parameter will close all result sets. Now the values of OUT or INOUT parameters are fetched only when the procedure has completed execution.

CR:366562

CR Number:   366562 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) 9.0.2 2432 10 Sep 2004 Fixed 9.0.1 1919 10 Sep 2004 Fixed 9.0.0 1361 10 Sep 2004 Fixed 8.0.3 5158 10 Sep 2004 Fixed 8.0.2 4472 10 Sep 2004 Fixed Description If the subsume_row_locks option is on and a table T is locked exclusively, the server should not obtain row locks for the individual rows in T when executing an UPDATE. This was not the case if T was updated through a join (or if T had triggers, computed columns, etc.), or if T was modified via a keyset cursor. Now, no locks are aquired in this situation.

CR:366568

CR Number:   366568 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) 2950 09 Nov 2004 Fixed 9.0.2 2531 09 Nov 2004 Fixed Description If MobiLink Server was the only component selected for installation, the licensing utility dblic.exe was not installed and the MobiLink Server could not have been re-licensed after installation. This has been fixed.

CR:366574

CR Number:   366574 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   5.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 14 Sep 2004 Fixed 9.0.1 1920 14 Sep 2004 Fixed Description Queries specifying the "TOP n" clause, that were optimized with the Optimization_goal set to "all-rows" may have had a less than optimal access plan. Such queries are now costed based on the estimated cost to produce first n rows instead of using the estimated total cost.

CR:366682

CR Number:   366682 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.3 5167 05 Oct 2004 Fixed 8.0.2 4489 05 Oct 2004 Fixed Description A query that satisfied the following conditions would have incorrectly failed with the error "Invalid use of an aggregate function": - it used an ANY, ALL, IN, or NOT IN subquery - the subquery used a grouped derived table or view - the derived table or view aliased an aggregate function - the alias was used in another column of the derived table or view For example: select 1 where 1 not in ( select b from (select sum(1) as b, b + 1 as c) dt ) This problem has now been fixed.

CR:366705

CR Number:   366705 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2420 13 Sep 2004 Fixed 9.0.1 1919 13 Sep 2004 Fixed Description A user-defined data type can now be renamed using: ALTER {DOMAIN | DATATYPE} usertype RENAME newname The name of the user type is updated in SYSUSERTYPE. Note that any procedures, triggers, views or events which refer to the user data type must be recreated, as they will continue to refer to the old name. Renaming of Java data types is not permitted.

CR:366752

CR Number:   366752 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) 2925 17 Sep 2004 Fixed 9.0.2 2925 21 Jan 2005 Fixed Description If a CREATE UNIQUE INDEX statement was executed for a local temporary table, a subsequent ROLLBACK could have caused the server to fail with assertion 100705. The CREATE INDEX statement was not performing an automatic COMMIT, now it does. A workaround is to execute an explicit COMMIT prior to the CREATE INDEX statement. Note, If the temporary table was created without ON COMMIT PRESERVE ROWS and the table was non-empty, execution of the CREATE INDEX statement will now delete all of the rows in the table, because of the added commit. Due to the addition of the commit, a CREATE INDEX on a local temporary table can no longer be used in a trigger or within an atomic compound statement. will release any locks held by the connection, and will close cursors not opened WITH HOLD. Workaround Description  avoiding the non-unique row inserts might help

CR:366763

CR Number:   366763 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) Description A new "Derived Table" node is now shown in query execution plans. In the graphical plan, these nodes show the name of the derived table and list of columns that are actually computed. The derived table nodes appear where a derived table or view appeared in the query text and was not combined with the rest of the query by "flattening". Also, these derived table nodes appear where the query processor generates a derived table, for example as input to a UNION, INTERSECT, or EXCEPT. The following query has three Derived table nodes in the graphical plan. One is associated with 'MyDerivedTable', which was specified in the query. Two others are generated for the inputs of the UNION. The derived table nodes can be used to find the expressions used as input to the UNION. select emp_id from employee union all select dept_id from ( select top 5 dept_id from department order by dept_name desc ) MyDerivedTable

CR:366765

CR Number:   366765 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2433 14 Sep 2004 Fixed 9.0.1 1920 14 Sep 2004 Fixed 9.0.0 1362 14 Sep 2004 Fixed Description Attempting to delete a user with one or more subscriptions, when connected to an Oracle database using the "iAnywhere Solutions 9 - Oracle Wire Protocol" ODBC driver, would have failed to delete the user. The problem was that the rows in ml_subscription were not being deleted before the row in ml_user. This has now been fixed.

CR:366920

CR Number:   366920 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 2429 16 Sep 2004 Fixed 9.0.1 1922 16 Sep 2004 Fixed 9.0.0 1363 16 Sep 2004 Fixed 8.0.3 5159 16 Sep 2004 Fixed 8.0.2 4475 16 Sep 2004 Fixed Description Calling the DATEPART() function, with the date-part CalWeekOfYear, would have returned the wrong week number if the year started with a Friday, Saturday or Sunday and the day of the date-expression passed was a Sunday, but not the very first one. For example: DATEPART( cwk, '2005/01/09' ) would have incorrectly returned 2 instead 1. This has now been fixed.

CR:366930

CR Number:   366930 Product Name:   UltraLite Product Component:   UltraLite Schema Painter Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2930 29 Sep 2004 Fixed 9.0.2 2529 29 Sep 2004 Fixed 9.0.1 1927 29 Sep 2004 Fixed 9.0.0 1369 30 Sep 2004 Fixed Description It was possible to get a schema file into a state where creating a foreign key was not possible. In the Schema Painter, attempting to create a foreign key would have resulted in the error: SQLCODE -113 Column in foreign key has a different definition than primary key, even though the domains of the columns appeared to be the same. This problem occurred when the domain for the column did not have a size, or precision and scale, thus making the domain_info irrelevant when checking for column compatibility in foreign key creation. Now, if the column type does not take a size, or precision and scale, the domain_info is not compared. A work around is to convert the database schema definition from USM to XML, and back again: ulxml.exe -toxml schema.usm schema.xml rename schema.usm schema_old.usm ulxml.exe -tousm schema.xml schema.usm The new schema.usm will then allow creating a foreign key.

CR:366969

CR Number:   366969 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.2 2434 16 Sep 2004 Fixed 9.0.1 1921 16 Sep 2004 Fixed Description Ultralite Dynamic SQL did not diagnose a duplicate name for a foreign key (within a table). It would have failed without an error code being set. This has been corrected.

CR:366983

CR Number:   366983 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) 9.0.2 2434 16 Sep 2004 Fixed 9.0.1 1921 16 Sep 2004 Fixed 9.0.0 1363 16 Sep 2004 Fixed Description When using the debugger in Sybase Central to debug a Java class with Java object local variables, a NullPointer Exception would have been thrown, when stopped at a breakpoint, if a local variable was NULL. This has been fixed.

CR:367116

CR Number:   367116 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 2435 17 Sep 2004 Fixed 9.0.1 1922 17 Sep 2004 Fixed 9.0.0 1363 17 Sep 2004 Fixed 8.0.3 5159 17 Sep 2004 Fixed 8.0.2 4475 17 Sep 2004 Fixed Description Executing a LOCK TABLE ... IN EXCLUSIVE MODE statement on a table did not prevent other transactions from subsequently obtaining exclusive locks on rows in the table when executing INSERT ... ON EXISTING UPDATE statements. Although it would have prevented explicit UPDATE statements from subsequently updating rows. This could have resulted in applications deadlocking unexpectedly. This has been fixed.

CR:367160

CR Number:   367160 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.2 2529 17 Sep 2004 Fixed 9.0.1 1922 17 Sep 2004 Fixed 9.0.0 1364 17 Sep 2004 Fixed Description Ultralite Dynamic SQL would have erroneously reported an overflow error for integers larger than 2147483647. A problem computing the precision correctly has been fixed.

CR:367198

CR Number:   367198 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.1 1957 30 Nov 2004 Fixed 8.0.3 5191 30 Nov 2004 Fixed 2971 30 Nov 2004 Fixed 9.0.2 2537 21 Jan 2005 Fixed Description In some very rare cases, an UltraLite application may have marked a column as a primary key, as well as an index column, thus causing the MobiLink server to crash when the application synchronized. This problem has been fixed. Now, the MobiLink server will give a protocol error when this situation is detected. To avoid the protocol error, the table will need to be dropped and recreated. Workaround Description  Some workarounds are implemented to avoid the scenario on the customer side -- not sure about the details yet

CR:367221

CR Number:   367221 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) 9.0.2 2529 17 Sep 2004 Fixed 9.0.1 1922 17 Sep 2004 Fixed Description When selecting from a single proxy table, the rowcount value returned by the server was incorrectly always 1, instead of -1. As a result, applications which rely on the rowcount information would have assumed that the query only had a single row in the result set. Returning a rowcount of -1 tells the application that the rowcount information is an estimate only and should not be relied upon. Note that after this fix, the rowcount for remote queries will always be -1 even if the ROW_COUNTS option is set.

CR:367222

CR Number:   367222 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 1922 20 Sep 2004 Fixed Description LDAP functionality had been inadvertently removed from both the server and client software. As a result, the LDAP TCPIP parameter would not have been recognized, and connection attempts would not have tried LDAP. This functionality has now been restored.

CR:367232

CR Number:   367232 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2436 20 Sep 2004 Fixed 9.0.1 1922 20 Sep 2004 Fixed 9.0.0 1364 20 Sep 2004 Fixed 8.0.3 5160 20 Sep 2004 Fixed 8.0.2 4475 20 Sep 2004 Fixed Description If a database created with the UTF8 collation, had a column that contained a 5 or 6 byte Chinese character sequence, ODBC client applications would likely have crashed fetching the column. This has been fixed. This problem was introduced by the changes for Engineering Case 364608.

CR:367252

CR Number:   367252 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) 9.0.2 2529 20 Sep 2004 Fixed 9.0.1 1922 20 Sep 2004 Fixed 9.0.0 1364 20 Sep 2004 Fixed 8.0.3 5160 20 Sep 2004 Fixed Description If the get_identity() function was used to allocate an identity value for a table, but the table itself was not modified by the current connection, or any other connection, then the value of the SYSCOLUMN.max_identity column was not updated at the next checkpoint. If the database was shutdown and restarted, get_identity() would then have re-used values previously generated. This has been fixed. Note that the use of an empty table having an autoincrement column, together with get_identity(), may still have resulted in values being re-used if the database was not shut down cleanly and values were allocated since the last checkpoint. Depending on how the values were used, it may have been possible to correct the starting value in a DatabaseStart event by calling sa_reset_identity() with the next value to use. For example: declare maxval unsigned bigint; set maxval = (select max(othercol) from othertab); call sa_reset_identity('IDGenTab', 'DBA', maxval);

CR:367267

CR Number:   367267 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) 9.0.2 2529 20 Sep 2004 Fixed 9.0.1 1922 20 Sep 2004 Fixed Description When using CREATE INDEX, Ultralite Dynamic SQL could have created an invalid index, if one or more of the columns being indexed were already used in another index. This problem has been corrected.

CR:367312

CR Number:   367312 Product Name:   SQL Remote for SQL Anywhere Product Component:   Smtp Messaging for Adaptive Server Anywhere Status:   Closed OS:   Linux Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2927 23 Sep 2004 Fixed 9.0.2 2529 23 Sep 2004 Fixed 9.0.1 1924 23 Sep 2004 Fixed 9.0.0 1366 23 Sep 2004 Fixed Description When run on Unix platforms, the SMTP message link for the ASA Message Agent dbremote, would have started and then reported "Execution Complete", with no errors. This was due to dbremote attempting to load the library libdbencode9_r.so, rather than the correct library libdbencod9_r.so. Now dbremote loads the correct library. A work around is to create the following symbolic in the $ASANY9/lib directory: "ln -s libdbencod9_r.so libdbencode9_r.so". Note, this problem also affected the SMTP message link for the ASE Message Agent ssremote, on Unix platforms.

CR:367331

CR Number:   367331 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) 9.0.2 2529 22 Sep 2004 Fixed 9.0.1 1924 22 Sep 2004 Fixed 9.0.0 1366 22 Sep 2004 Fixed 8.0.3 5162 22 Sep 2004 Fixed 8.0.2 4476 22 Sep 2004 Fixed 7.0.4 3532 22 Sep 2004 Fixed Description In rare circumstances, it is possible for database corruption to occur if the machine running the database server was put into suspend or hibernate mode, while the server was still running. This has now been fixed for the majority of cases. It still possible on very heavily loaded servers, as the OS may suspend the machine while the server is still preparing for it.

CR:367337

CR Number:   367337 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) 9.0.2 2529 20 Sep 2004 Fixed 9.0.1 1923 20 Sep 2004 Fixed Description Attempting to get the application information of a jConnect or Open Client application, using SELECT CONNECTION_PROPERTY( 'APPINFO', ... ), would have always returned NULL for APPINFO. Now, the server will attempt to display the application name, the application host and the application PID, if that information has previously been provided by the application at connect time. It should be noted that in some cases, the application information provided by the client is not completely accurate; however, the server will still display the inaccurate information.

CR:367342

CR Number:   367342 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) 9.0.2 2529 20 Sep 2004 Fixed 9.0.1 1923 20 Sep 2004 Fixed 9.0.0 1365 20 Sep 2004 Fixed 8.0.3 5161 20 Sep 2004 Fixed 8.0.2 4476 20 Sep 2004 Fixed Description If the first byte of the DELIMITED BY string for a LOAD TABLE statement was greater than or equal to 0x80, the LOAD TABLE statement would not have recognized any delimiters in the input file. This is now fixed.

CR:367366

CR Number:   367366 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) 9.0.2 2529 21 Sep 2004 Fixed 9.0.1 1923 21 Sep 2004 Fixed Description If a Remote Data Access server was created in a database to connect back to the same database, then creating proxy tables would have hung the server. This problem was originally addressed in ASA 7.0.0, but subsequent changes necessitated a different fix. Now, the error "Unable to connect, server definition is circular", (SQLCODE -657), will be generated, but only for ODBC connections. JDBC connections will still have problems.

CR:367378

CR Number:   367378 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 21 Sep 2004 Fixed 9.0.1 1923 21 Sep 2004 Fixed Description The server could have become hung in an endless loop while performing a sort. When in this loop, the server would not have responded to the cancel request. For the problem to have occurred, a sort must have been performed with a small amount of memory available to the connection, followed by a decrease in the amount of available memory. The problem could have occurred even with large cache sizes, if a child of the sort consumed most, but not all, of the connection's allotted memory. Extra checks have now been added for out-of-memory situations when sorting.

CR:367396

CR Number:   367396 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.2 2529 21 Sep 2004 Fixed 9.0.1 1923 21 Sep 2004 Fixed 9.0.0 1365 21 Sep 2004 Fixed Description Ultralite Dynamic SQL would have failed with a conversion error, when attempting to convert character strings to and from LONGVARCHAR columns, and binary values to and from LONGBINARY columns. This problem has been corrected

CR:367451

CR Number:   367451 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) 2927 23 Sep 2004 Fixed 9.0.2 2529 23 Sep 2004 Fixed 9.0.1 1924 23 Sep 2004 Fixed Description If a Remote Data Access server was created in a database to connect back to the same database, then creating proxy tables would have hung the server. This is a followup to Engineering Case 367366, which resolved the problem with circular ODBC connections. Now, the error "Unable to connect, server definition is circular", (SQLCODE -657), will be generated for circular JDBC connections as well.

CR:367456

CR Number:   367456 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) 2928 24 Sep 2004 Fixed 9.0.2 2529 24 Sep 2004 Fixed 9.0.1 1925 24 Sep 2004 Fixed 9.0.0 1366 24 Sep 2004 Fixed Description If a web client made an HTTP or HTTPS connection to a the database server, it could have caused other connections to hang, until the HTTP or HTTPS connection either completed, or was killed. This now has been fixed.

CR:367464

CR Number:   367464 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2441 23 Sep 2004 Fixed 9.0.1 1924 23 Sep 2004 Fixed 9.0.0 1366 23 Sep 2004 Fixed 8.0.3 5162 23 Sep 2004 Fixed 8.0.2 4477 23 Sep 2004 Fixed Description The ASACommandBuilder class could not derive parameters if the stored procedure name was quoted. Fixed by parsing the command text and using an unquoted procedure name for deriving parameters.

CR:367470

CR Number:   367470 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) 9.0.2 2529 22 Sep 2004 Fixed 9.0.1 1924 22 Sep 2004 Fixed Description In the "Backup Database" wizard, the "Browse" button on the third page allows an existing file to be chosen, or to provide the name of a new file. If a new file name was provided, but without an extension, the value of the file name text field in the wizard would have ended in ".*" -- which was wrong. Now, the name typed is copied to the text field verbatim.

CR:367528

CR Number:   367528 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) 9.0.2 2441 22 Sep 2004 Fixed 9.0.1 1924 22 Sep 2004 Fixed 9.0.0 1365 22 Sep 2004 Fixed 8.0.3 5161 22 Sep 2004 Fixed 8.0.2 4477 22 Sep 2004 Fixed Description Autodial was not responding, even when the network_name parameter was specified. Autodial functionality has now been restored.

CR:367533

CR Number:   367533 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2529 22 Sep 2004 Fixed 9.0.1 1924 22 Sep 2004 Fixed Description The server could have crashed when requested to generate an access plan for a remote query, either by the dbisql plan feature, or an explicit call to the explanation() function, when that query would have been executed in full passthrough mode. An example of such a query is 'INSERT INTO T VALUES(2)' where T is a proxy table. The server will now return no plans for such queries.

CR:367549

CR Number:   367549 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) 2927 23 Sep 2004 Fixed 9.0.2 2529 23 Sep 2004 Fixed Description The Interactive SQL utility dbisql, could have displayed the wrong table's data when launched from Sybase Central. This would have happened if the "View Data in Interactive SQL" menu item for a table had previously been clicked, and the resulting Interactive SQL window was left open. When trying to view the data for a different table, the new Interactive SQL window showed the data for the previous table, not the one selected. This has now been fixed.

CR:367550

CR Number:   367550 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 2441 22 Sep 2004 Fixed Description With the collation 874THAIBIN, the Thai digits (0xF0-0xF9) would have compared and sorted equal to their ASCII equivalents (0-9). The Thai digits will now sort with the other Thai characters, in binary order.

CR:367568

CR Number:   367568 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 22 Sep 2004 Fixed Description Collation 1252NOR has been added to provide Norwegian ordering and comparisons for Windows Code Page 1252. When creating a new database on Windows systems using the cp1252 codepage, if no collation is specified, and the language setting for the system is Norwegian (or the environment variable ASLANG is set to "no"), then 1252NOR will be chosen. Previously, 1252LATIN1 would have been chosen.

CR:367630

CR Number:   367630 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2927 24 Sep 2004 Fixed Description When notifying a SIS Listener with SMS listening from Rogers AT&T enabled, the Notifier would have given an error that the network_provider_id=ROGERS was not recognized. This was due to Rogers having recently changed their network provider id from 'ROGERS AT&T' to 'ROGERS'. A fix has been made so that newly created ASA consolidated databases, or new MobiLink installs for other consolidates, will contain the new network_provider_id 'ROGERS'. Existing databases can be updated by the following work around: - Stop MobiLink and thus stop the Notifier. - Use the MobiLink plugin to update the network_provider_id from 'ROGERS AT&T' to 'ROGERS'. - Restart the MobiLink Server with the notifier.

CR:367661

CR Number:   367661 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) 9.0.2 2442 23 Sep 2004 Fixed 9.0.1 1925 23 Sep 2004 Fixed 9.0.0 1366 23 Sep 2004 Fixed 8.0.3 5162 23 Sep 2004 Fixed 8.0.2 4478 23 Sep 2004 Fixed Description Executing an INSERT ... ON EXISTING UPDATE statement could have caused a deadlock in the server, if another transaction was updating the table that was being modified, and a checkpoint (or DDL statement) was pending. This has been fixed.

CR:367663

CR Number:   367663 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) 2928 24 Sep 2004 Fixed 9.0.2 2444 24 Sep 2004 Fixed 9.0.1 1925 24 Sep 2004 Fixed 8.0.3 5162 24 Sep 2004 Fixed 8.0.2 4478 24 Sep 2004 Fixed Description The server could have failed to drop a temporary table on a database opened read-only. This would only have occurred if the temporary table was declared using Transact-SQL syntax, (ie "#table_name"). This has been fixed.

CR:367688

CR Number:   367688 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   5.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2928 28 Sep 2004 Fixed 9.0.2 2529 28 Sep 2004 Fixed 9.0.1 1926 28 Sep 2004 Fixed 8.0.3 5164 28 Sep 2004 Fixed 8.0.2 4479 28 Sep 2004 Fixed Description Support for textual options to the Transact-SQL statement SET TRANSACTION ISOLATION LEVEL, have been added for compatibility with Sybase ASE and Microsoft SQL Server. Applications can now issue the following variants: SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED SET TRANSACTION ISOLATION LEVEL READ COMMITTED SET TRANSACTION ISOLATION LEVEL REPEATABLE READ SET TRANSACTION ISOLATION LEVEL SERIALIZABLE which correspond to setting the isolation level of the connection to 0, 1, 2, or 3 respectively.

CR:367689

CR Number:   367689 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 5162 24 Sep 2004 Fixed 8.0.2 4478 24 Sep 2004 Fixed Description When running on NetWare systems, executing complex queries could have caused the server to abend with CPU Hog Timeout. This has been fixed by adding more yields, and checks for stack overflows, in the optimizer.

CR:367691

CR Number:   367691 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 8.0.3 5004 23 Sep 2004 Fixed 8.0.2 4478 23 Sep 2004 Fixed Description On AIX systems running version 4.3.1, applications, including the ASA utilities such as dblocate, would have failed to find any network servers over TCP/IP, if the host=xxx parameter was not specified. Code specific to AIX 4.3.1 to find the broadcast mask was incorrect. This has now been fixed.

CR:367695

CR Number:   367695 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 2928 28 Sep 2004 Fixed 9.0.2 2529 28 Sep 2004 Fixed 9.0.1 1925 28 Sep 2004 Fixed Description If queries that required temporary tables were used, and then a schema upgrade was done, it was possible that a crash could have occurred when these queries were then run after the upgrade. A crash would not have occurred if the database was restarted after the schema upgrade. Temporary table structures were not being preserved across a schema upgrade. They are now restored at the end of the schema upgrade.

CR:367716

CR Number:   367716 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   8.0.2 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 The userid 'dbo' was unable to use EXECUTE IMMEDIATE to execute a string containing a multi-statement batch. This restriction has now been removed.

CR:367733

CR Number:   367733 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) 27 Sep 2004 Workaround Description Ability to get the port number of the server inside of the engine ia sa_eng_properties system procedure

CR:367742

CR Number:   367742 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) 2928 24 Sep 2004 Fixed 9.0.2 2529 24 Sep 2004 Fixed 9.0.1 1925 24 Sep 2004 Fixed 9.0.0 1366 24 Sep 2004 Fixed Description When Sybase Central was connected to a database using the iAnywhere JDBC driver, and a database error occurred, it would have been treated internally as a closed connection. The error would not have been reported though, as there really were no closed connections. This has been fixed.