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

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

CR:533749

CR Number:   533749 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 23 Jun 2008 Fixed 10.0.1 3715 23 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description The iAS ODBC driver for Oracle could have given mangled error and warning messages to the application when it was running on a operating system that used a multi-byte character set, such as a Japanese or Chinese. This problem is now fixed.

CR:533793

CR Number:   533793 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 23 Jun 2008 Fixed 10.0.1 3716 23 Jun 2008 Fixed 11.0.1 1864 17 Nov 2008 Fixed Description If a server had multiple databases loaded, each with a different character set, the database name returned by the system function "db_property('Name', <dbid>)" could have been improperly character set converted. This could have made the name returned appear garbled. For this to have occurred, the database ID specified by "<dbid>" must have been different from the ID of the database of the connection. This has now been fixed.

CR:533802

CR Number:   533802 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 20 Jun 2008 Fixed 10.0.1 3716 20 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description Execution of a SELECT statement that referenced a procedure call in the FROM clause could have resulted in a server crash. For this to have occurred, the connection must have had several cursors open, or have had several prepared statements. This has now been fixed.

CR:533804

CR Number:   533804 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 20 Jun 2008 Fixed 10.0.1 3715 20 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description When the MobiLink server was under heavy load, the Mobilink monitor may have crashed, hung or disconnect from the Mobilink server. This has now been fixed.

CR:533805

CR Number:   533805 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 20 Jun 2008 Fixed 10.0.1 3715 20 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description If a consolidated database was running on an Oracle 9i or later server, the MobiLink server could have sent clients a next_last_download_time (a timestamp value used to generate a download in the next synchronization) that was earlier than the last_download_time (a timestamp value used to generate the download in the current synchronization). This problem could have caused a MobiLink client to complain when it was trying to apply the downloaded file. This problem has now been fixed.

CR:533830

CR Number:   533830 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 20 Jun 2008 Fixed 11.0.1 1863 17 Nov 2008 Fixed Description If at some point during the current session the Views folder, or a materialized view in the tree, was selected then Sybase Central could have caused shared locks to be held on all manual, valid, non-initialized materialized views. These locks would have prevented the refreshing of any such materialized view via another connection, for example from an ISQL session. This has been fixed.

CR:533936

CR Number:   533936 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1433 08 Jul 2008 Fixed 10.0.1 3723 08 Jul 2008 Fixed 11.0.1 1892 17 Nov 2008 Fixed Description In rare situations, Java applications using the iAnywhere JDBC driver with concurrent connections may have hung, or even crashed. Several fixes have been made to correct race conditions between concurrent connections.

CR:533950

CR Number:   533950 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) 11.0.0 1411 20 Jun 2008 Fixed 11.0.1 1864 17 Nov 2008 Fixed Description The sa_locks() system procedure can be used to get a report on server locks currently held by various connections. Since both base tables and materialized views hold data, locks can be held on objects of either type. The server will now report the type of "MVIEW" for locks held on materialized view instead of the type of "BASE", which will continue to be reported for locks on base tables.

CR:533958

CR Number:   533958 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3680 20 Jun 2008 Fixed Description When the event of a download_cursor, or a download_delete_cursor, in a MobiLink server synchronization logic was written as: {call procedure_name( ?, ? )} for consolidated databases running on an Oracle server, the iAS ODBC driver for Oracle may have given the error: ORA-06553: PLS-306: wrong number or types of arguments in call to 'procedure_name' if the stored procedure returned a result set and the word, "call" was not all in lower-case. This has now been fixed. Note, the iAS ODBC driver for Oracle in version 9.0.2 is actually the driver from version 10.0.1. Versions of the driver with this fix are 10.0.1 3686 or later.

CR:533974

CR Number:   533974 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1494 16 Sep 2008 Fixed 10.0.1 3766 16 Sep 2008 Fixed 11.0.1 1954 17 Nov 2008 Fixed Description When calling a Java stored procedure from the Interactive SQL utility with a SQL argument of type DATE, TIME or TIMESTAMP and a Java argument of type java.sql.Date or java.sql.Time, the server would have returned a parse exception from the JVM. Using dbisqlc to make the same Java stored procedure call would have worked fine. This problem has now been fixed.

CR:533979

CR Number:   533979 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 23 Jun 2008 Fixed 10.0.1 3716 23 Jun 2008 Fixed 11.0.1 1864 17 Nov 2008 Fixed Description The columns from stored procedure result sets were not being excluded when Visual Studio enumerated stored procedure parameters. This has now been corrected.

CR:533994

CR Number:   533994 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 23 Jun 2008 Fixed 11.0.1 1864 17 Nov 2008 Fixed Description The "Messages" tab could have remained selected after executing a statement which returned result sets. This has been corrected so that the first result set tab is now always selected.

CR:534001

CR Number:   534001 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3736 27 Aug 2008 Fixed 9.0.2 3701 27 Aug 2008 Fixed Description The Java Runtime Environments that are included in SQL Anywhere have been updated to version 1.4.2_18 for 9.0.2 and 1.5.0_16 for 10.0.1. These updates include a number of security fixes which do not directly impact SQL Anywhere software, but were done to help those customers whose corporate policies preclude the installation of older JRE updates which contain known security defects. In the future, customers will be able to update the JRE themselves by following instructions which will be made available shortly.

CR:534003

CR Number:   534003 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1411 23 Jun 2008 Fixed 11.0.1 1864 17 Nov 2008 Fixed Description In graphical plans, the operator for a table accessed using an index-only scan was drawn as a table-scan operator, not as an index-scan operator. This has been fixed.

CR:534005

CR Number:   534005 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3683 24 Jun 2008 Fixed Description If the QAnywhere client (qaagent) was started using a rules file for its policy, then shut down and restarted with a syntax error on the command line, in some situations an error such as "SQL statement failed: (-265) Procedure 'ml_qa_sync_rule_0' not found" would have occurred in the MobiLink client (dbmlsync). This has been fixed.

CR:534132

CR Number:   534132 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 04 Jul 2008 Fixed 10.0.1 3717 04 Jul 2008 Fixed 11.0.1 1867 18 Nov 2008 Fixed Description If many rows had been deleted from the end of an index, and the server was under heavy load for some period of time after that, there was a chance that the server could have crashed.

CR:534135

CR Number:   534135 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3681 23 Jun 2008 Fixed Description The iAS ODBC driver for Oracle could have given mangled error and warning messages to the application when it was running on a operating system that used a multi-byte character set, such as a Japanese or Chinese. This problem is now fixed. Note, the iAS ODBC driver for Oracle in version 9.0.2 is actually the driver from version 10.0.1. Versions of the driver with this fix are 10.0.1 3715 or later.

CR:534147

CR Number:   534147 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 04 Jul 2008 Fixed 11.0.1 1867 18 Nov 2008 Fixed Description The server could have crashed following many concurrent updates and/or inserts to a large indexed table. This has now been fixed.

CR:534156

CR Number:   534156 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 24 Jun 2008 Fixed 11.0.1 1867 18 Nov 2008 Fixed Description If the 'datasource', 'host', or 'port' command line options were used, dbisql would not have started, but would not have reported an error. This has been corrected so that these options are now accepted and processed correctly.

CR:534168

CR Number:   534168 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 24 Jun 2008 Fixed 11.0.1 1867 18 Nov 2008 Fixed Description Altering a column with an IMMEDIATE REFRESH text index would have caused the server to fail an assertion. This is fixed.

CR:534179

CR Number:   534179 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1433 24 Jun 2008 Fixed 10.0.1 3730 24 Jun 2008 Fixed 11.0.1 1892 18 Nov 2008 Fixed Description Java messages could have been corrupted on operating systems with non-English character sets. Character set conversion was not being done correctly. This has been fixed

CR:534292

CR Number:   534292 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 24 Jun 2008 Fixed 10.0.1 3717 24 Jun 2008 Fixed 11.0.1 1868 18 Nov 2008 Fixed Description When run on non-Windows platforms, the Server Message Store wizard would have crashed after leaving the second page. This has been fixed. In related issues, the toolbar button for opening this wizard was missing, and the "Create a client message store" item should have been removed from the Task list on non-Windows machines, but was not. These have been fixed as well.

CR:534294

CR Number:   534294 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1421 08 Jul 2008 Fixed 10.0.1 3723 08 Jul 2008 Fixed 11.0.1 1881 18 Nov 2008 Fixed Description The server keeps track of the dependencies of views on other tables and views. When the schema of a table is modified by using the ALTER TABLE statement, the server automatically and atomically recompiles all views whose view definitions depend upon the schema of the table being modified. All views that can be compiled without errors with the new table schema are rebuilt persistently in the catalog and remain valid after reflecting the changes in the table schema. Views that fail to compile are left in a state where the server automatically tries to recompile them in the future. If column permissions, as opposed to table permissions, had been granted on a view dependent on the table being modified, the execution of ALTER TABLE could have failed with referential integrity violations on SYS.SYSTABCOL. This has been corrected so that the server now automatically attempts to restore the old column permissions on views that are recompiled as a consequence of ALTER TABLE. Permissions on columns that no longer exist in the recompiled view(s) are lost. See Engineering case 536015 for a related issue. Workaround Description  Revoke the permission for update gived under view.

CR:534307

CR Number:   534307 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1877 18 Nov 2008 Fixed Description If an application using the iAnywhere JDBC driver attempted to use the optional DatabaseMetaData.getUDTs() method, the driver would have throw a "not yet implemented" exception. The iAnywhere JDBC driver has now been enhanced to return a proper result set for the getUDTs() method if the driver is connected to an SA database. For all non-SA servers, the iAnywhere JDBC driver will continue to throw the "not yet implemented" exception.

CR:534320

CR Number:   534320 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 24 Jun 2008 Fixed 10.0.1 3717 24 Jun 2008 Fixed 11.0.1 1868 18 Nov 2008 Fixed Description Sybase Central could have crashed while using the QAnywhere plugin, if the connection to a server message store was unexpectedly lost. This has been fixed.

CR:534321

CR Number:   534321 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 25 Jun 2008 Fixed 11.0.1 1868 18 Nov 2008 Fixed Description The server could have crashed when processing an HTTP request that required character set conversion. This has been fixed.

CR:534324

CR Number:   534324 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 16 Sep 2008 Fixed 10.0.1 3717 16 Sep 2008 Fixed 11.0.1 1868 18 Nov 2008 Fixed Description Statements that appeared in stored procedures may have used a cached execution plan (see Plan caching in the documentation). In some cases, a stale value of a builtin function could have been returned for subsequent executions of the statement. This has now been corrected. The following builtin functions were affected by this issue: connection_extended_property connection_property db_extended_property db_property estimate estimate_source event_condition event_condition_name event_parameter experience_estimate http_body http_header http_variable index_enabled index_estimate next_connection next_database next_http_header next_http_variable next_soap_header property rewrite soap_header varexists watcomsql For web services based on sessions, connection properties such as SessionLastTime could also have been affected by this (among other builtins). This incorrect behaviour was masked in version 10.0.1 for web services using sessions.

CR:534333

CR Number:   534333 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 25 Jun 2008 Fixed 11.0.1 1868 18 Nov 2008 Fixed Description When calling the system function REGEXP_SUBSTR() with non-ASCII characters, it could have returned an incorrect result, possibly consisting of invalid characters. The input strings were being cast to NCHAR values, and then the resulting NCHAR output was treated as a CHAR, resulting in garbled output if the database character set was not UTF8. This has been fixed.

CR:534356

CR Number:   534356 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1414 27 Jun 2008 Fixed 11.0.1 1870 18 Nov 2008 Fixed Description Very occasionally, the Interactive SQL utility may not have started when the fast launcher option was turned on. This problem has been fixed.

CR:534358

CR Number:   534358 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1413 25 Jun 2008 Fixed 10.0.1 3718 25 Jun 2008 Fixed 11.0.1 1869 18 Nov 2008 Fixed Description Use of any of the TLS options "certificate_name", "certificate_unit", or "certificate_company" would have caused connections to fail with a "TLS handshake failure" error. This has been fixed. As a workaround, the options "name", "unit", and "company" can be used.

CR:534402

CR Number:   534402 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1413 25 Jun 2008 Fixed 11.0.1 1870 18 Nov 2008 Fixed Description Incorrect results were possible when executing queries with a LEFT OUTER JOIN and a WHERE clause whose elements are all from the left hand side of the join. This has been corrected.

CR:534404

CR Number:   534404 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 25 Jun 2008 Fixed 11.0.1 1869 18 Nov 2008 Fixed Description The comparison of two NULL values would have erroneously resulted in TRUE, instead of UNKNOWN. This has now been corrected.

CR:534471

CR Number:   534471 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) 11.0.1 1922 26 Jun 2008 Fixed 11.0.0 1413 25 Nov 2008 Fixed Description The server performs an implicit commit before and after the execution of a CREATE INDEX statement. The act of performing a commit following execution releases any locks obtained by the server during the creation of the index. If the create statement failed due to an error, then the server could have failed to release the locks obtained before the point of failure. There was no other user visible impact and the held locks were released when the connection next performed a COMMIT or ROLLBACK. This has been corrected so that the server now release the held locks automatically.

CR:534482

CR Number:   534482 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 25 Jun 2008 Fixed 11.0.1 1869 18 Nov 2008 Fixed Description If a connection string contained an invalid encryption parameter, or was missing the mandatory trusted_certificates parameter, the error returned would have been: "Could not initialize the encryption DLL: '???'" This has been corrected so that a TLS handshake error will now be returned, as in previous releases.

CR:534496

CR Number:   534496 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 25 Jun 2008 Fixed 10.0.1 3718 25 Jun 2008 Fixed 11.0.1 1869 18 Nov 2008 Fixed Description An expression that converted an integer value to a NUMERIC or a DECIMAL, could have leaked memory in the server if an overflow error was generated. If enough of these expressions were evaluated, server execution could have been impaired. This has been fixed.

CR:534586

CR Number:   534586 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1413 26 Jun 2008 Fixed 11.0.1 1870 18 Nov 2008 Fixed Description Information about column defaults was not being reloaded on subsequent connections after the default information was created. This resulted in column defaults not being automatically generated for NULL columns on INSERTS. Loading of the additional field has now been implemented.

CR:534742

CR Number:   534742 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1412 26 Jun 2008 Fixed 11.0.1 1867 18 Nov 2008 Fixed Description The MobiLink server, and Java and .NET APIs, have been modified to allow users to register to receive notfications whenever an info line is printed to the log (i.e. lines prefixed with "I."). Java: The following methods, added to interface ianywhere.ml.script.ServerContext are used to register or unregister listeners: /** * Adds the specified LogListener to receive a notification * when info is printed. * method {@link LogListener#messageLogged} will be called. * * @param ll the LogListener to be notified on warning */ public void addInfoListener( LogListener ll ); /** * Remove the specified LogListener from the list of * listeners to receive a notification * when info is printed. * * @param sl the listener which will no longer be notified */ public void removeInfoListener( LogListener ll ); The following constant, added to class ianywhere.ml.script.LogListener, is returned by LogMessage.getType() for info messages: public static final int INFO = 2; Example: The following code registers a listener of type MyLogListener to receive notifications of info messages. // ServerContext serv_context; serv_context.addInfoListener( new MyLogListener( ll_out_file )); The following code shows an example of processing those messages: class MyLogListener implements LogListener { FileOutputStream _out_file; public TestLogListener( FileOutputStream out_file ) { _out_file = out_file; } public void messageLogged( ServerContext sc, LogMessage msg ) { String type; String user; try { if(msg.getType() == LogMessage.ERROR) { type = "ERROR"; } else if(msg.getType() == LogMessage.WARNING) { type = "WARNING"; } else if(msg.getType() == LogMessage.INFO) { type = "INFO"; } else { type = "UNKNOWN!!!"; } user = msg.getUser(); if( user == null ) { user = "NULL"; } _out_file.write( ("Caught msg type=" + type + " user=" + user + " text=" +msg.getText() + "\n").getBytes() ); _out_file.flush(); } catch( Exception e ) { // if we print the exception from processing an info message, // we may recurse indefinately if( msg.getType() != LogMessage.INFO ) { // Print some error output to the MobiLink log. e.printStackTrace(); } } } } .NET: Callback functions can be registered to the following event, added to interface iAnywhere.MobiLink.Script.ServerContext, to receive notifications about info messages: /// <summary> /// Triggered when the MobiLink server prints info /// </summary> event LogCallback InfoListener; The following, added to enum iAnywhere.MobiLink.Script.LogMessage.MessageType, can be returned by the Type property of the LogMessage class /// <summary> /// A log info message.</summary> INFO Example: The following code defines a callback that will process an info message. internal class TestLogListener { public TestLogListener( StreamWriter output_file, LogMessage.MessageType expected_type ) { _output_file = output_file; _expected_type = expected_type; } public void errCallback( ServerContext sc, LogMessage lm ) { string type; string user; if( lm.Type != _expected_type ) { _output_file.WriteLine( "Message type not expected!!" ); return; } if( lm.Type==LogMessage.MessageType.ERROR ) { type = "ERROR"; } else if( lm.Type==LogMessage.MessageType.WARNING ) { type = "WARNING"; } else if( lm.Type==LogMessage.MessageType.INFO ) { type = "INFO"; } else { type = "INVALID TYPE!!"; } if( lm.User == null ) { user = "null"; } else { user = lm.User; } if( (lm.Text.IndexOf( "10017" ) > 0) || (lm.Text.IndexOf( "10018" ) > 0) || (lm.Text.IndexOf( "10020" ) > 0) || (lm.Type == LogMessage.MessageType.INFO && lm.Text.IndexOf( "MobiLink server started" ) < 0 ) ) { return; } _output_file.WriteLine( "Caught msg type=" + type + " user=" + user + " text=" + lm.Text ); _output_file.Flush(); } StreamWriter _output_file; private LogMessage.MessageType _expected_type; } The following code adds the callback to the InfoListener event. // ServerContext _sc; TestLogListener itll = new TestLogListener( log_listener_file, LogMessage.MessageType.INFO ); sc.InfoListener += new LogCallback(itll.errCallback);

CR:534774

CR Number:   534774 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1413 26 Jun 2008 Fixed 11.0.1 1870 18 Nov 2008 Fixed Description Non-disabled materialized views were described as having a status of "Valid". Now, the correct term "Enabled" is used, and the term "Valid" is used only for non-materialized views.

CR:534792

CR Number:   534792 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1452 23 Jul 2008 Fixed 10.0.1 3736 23 Jul 2008 Fixed 11.0.1 1912 18 Nov 2008 Fixed Description The OLE DB provider did not correctly support the DBCOLUMN_BASECOLUMNNAME rowset column of the IColumnsRowset::GetColumnsRowset method. This column should contain the name of the column in the data store, which might be different than the column name returned in the DBCOLUMN_NAME column if an alias or a view was used. Here is an example. CREATE TABLE GROUPO.MyTable( DATA2 varchar(16), DATA1 varchar(16), PKEY int NOT NULL default autoincrement, CONSTRAINT PKeyConstraint PRIMARY KEY (PKEY) ) ; CREATE VIEW DBA.MyView( PKEY, DATA_1, DATA2) AS SELECT PKEY, DATA1, DATA2 FROM MyTable; Consider the following queries. SELECT PKEY, DATA_1, DATA2 as D2 FROM MyView SELECT PKEY, DATA1 as DATA_1, DATA2 as D2 FROM MyTable In both cases, the OLE BD provider would return the following for DBCOLUMN_BASECOLUMNNAME and DBCOLUMN_BASETABLENAME for these queries. PKEY MyTable DATA_1 MyTable D2 MyTable Of course, the DATA_1 and D2 columns are not found in MyTable. With this fix, the provider now returns the correct column names. PKEY MyTable DATA1 MyTable DATA2 MyTable

CR:534837

CR Number:   534837 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1414 27 Jun 2008 Fixed 11.0.1 1871 18 Nov 2008 Fixed Description Predicates with AND, OR and NOT expressions along with UNKNOWN could have produced incorrect results. This has now been corrected.

CR:534927

CR Number:   534927 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1874 18 Nov 2008 Fixed Description Control of an HTTP session time-out duration was not passed to subsequent HTTP requests belonging to the same session if a TEMPORARY HTTP_SESSION_TIMEOUT database option had been set (in a previous HTTP request belonging to the session). The scope of the problem applied to all TEMPORARY database options set within an HTTP session context. The problem was due to user id being reset for each HTTP request. This has been corrected so that an HTTP request within a session context will no longer reset its user id if it is identical to the user id of the current service. The problem remained however if an HTTP session was used to call a service that specified a different user id. A SA web application using HTTP sessions should only use TEMPORARY and/or USER specific options when all requests within the HTTP session context access SA services defined with the same user id. Similarly, accessing an authenticated SERVICE would require that the HTTP request belonging to a session provide the same user id from request to request. To address this, a new HTTP OPTION called SessionTimeout has been added to make HTTP session time-out criteria persistent in all cases. It can be set from within an HTTP request that has defined, or will define, a SessionID. The context of the setting is preserved throughout the HTTP session, until it expires, is deleted or changed (with a subsequent SA_SET_HTTP_OPTION call). - New SA_SET_HTTP_OPTION option SessionTimeout The value of this HTTP OPTION is specified in minutes. It is subject to the minimum and maximum constraints of the HTTP_SESSION_TIMEOUT database option. A newly created session is implicitly assigned the current or default PUBLIC/USER HTTP_SESSION_TIMEOUT. The following example sets a given HTTP session time-out to 5 minutes: call SA_SET_HTTP_OPTION('SessionTimeout', '5'); An empty value resets the option to its default value, or as set by the PUBLIC or USER scope HTTP_SESSION_TIMEOUT database option. call SA_SET_HTTP_OPTION('SessionTimeout', ''); // resets the time-out to 30 minutes - the default value of the HTTP_SESSION_TIMEOUT database option SET OPTION PUBLIC.HTTP_SESSION_TIMEOUT=1 // New HTTP sessions calling SA_SET_HTTP_OPTION('SessionTimeout', '') set session time-out to 1 minute SET OPTION USERA.HTTP_SESSION_TIMEOUT=15 // New HTTP sessions calling SA_SET_HTTP_OPTION('SessionTimeout', '') set session time-out to 15 minutes for USERA NOTE: HTTP session default criteria is derived from the current PUBLIC/USER HTTP_SESSION_TIMEOUT database option setting. Any subsequent changes to this option will not implicitly affect existing HTTP sessions. The default timeout setting for HTTP sessions that always use the same user id remains unchanged. However, an HTTP request belonging to a session that calls a service with an alternate user id will force its cache to be cleared and the option defaults of the current user to be loaded. Therefore, when the session switches users all TEMPORARY options are lost and the current PUBLIC/USER options are assigned. - New CONNECTION_PROPERTY('SessionTimeout') Returns the time-out value in minutes for a given database connection belonging to an HTTP session. The value is the current setting for SA_SET_HTTP_OPTION('SessionTimeout', 'X'). A value of 0 is returned if the database connection does not belong to an HTTP session. As before, the HTTP_SESSION_TIMEOUT database option may be queried to determine the PUBLIC/USER default values. - Summary of changes TEMPORARY and USER scope options are preserved when HTTP requests belonging to a session execute SA services defined with a specific (the same) user id. SessionTimeout HTTP_OPTION has been added to provide an HTTP session context time-out criteria. Its use is recommended in place of setting a TEMPORARY HTTP_SESSION_TIMEOUT database option since it is guaranteed to persist for the life of the session.

CR:534931

CR Number:   534931 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1414 04 Jul 2008 Fixed 11.0.1 1871 18 Nov 2008 Fixed Description A query that did a scan of an index when the isolation level was set snapshort, could have returned extra rows. This has now been corrected.

CR:534949

CR Number:   534949 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3727 17 Jul 2008 Fixed 9.0.2 3697 17 Jul 2008 Fixed Description The iAS ODBC driver for Oracle would have truncated the time portion of timestamp values, when the application was trying to fetch the timestamp values using SQLGetData. An internal buffer was too small for a timestamp column. This has been fixed.

CR:534963

CR Number:   534963 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1414 02 Jul 2008 Fixed 10.0.1 3719 02 Jul 2008 Fixed 11.0.1 1871 18 Nov 2008 Fixed Description The server tracks dependencies of views on other views and tables. If a table is referenced by other views, attempting to execute an ALTER TABLE statement on the referenced table could have caused the server to crash under certain circumstances. This has been fixed, the server now carries out the ALTER properly. A workaround is to disable the dependent view before executing the ALTER statement, followed by a re-enabling of the view.

CR:534966

CR Number:   534966 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) 11.0.0 1466 27 Jun 2008 Fixed 11.0.1 1926 19 Nov 2008 Fixed Description Sybase Central did not allow creating, modifying or deleting services for the MobiLink Listener utility (dblsn), the Broadcast Repeater utility (dbns11), and the SQL Anywhere Volume Shadow Copy Service (dbvss11). Attempting to open the properties for one of these types of services would have caused Sybase Central to crash. These problems have been fixed.

CR:534995

CR Number:   534995 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1414 02 Jul 2008 Fixed 11.0.1 1871 19 Nov 2008 Fixed Description When deploying a synchronization model to an UltraLite remote database, the generated <model>_ulsync.bat and dblsn.txt files incorrectly used the version 10 syntax for ulsync. This has now been corrected.

CR:535215

CR Number:   535215 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1415 02 Jul 2008 Fixed 11.0.1 1874 19 Nov 2008 Fixed Description The server supports the ANSI MERGE statement, with some vendor extensions, which can be utilized to merge data from one source into another. Under certain circumstance, the MERGE statement could have behaved incorrectly. As an example, if the MERGE statement was instructed to update multiple rows of the target table based on the same matching conditions, then the values visible for the new row within a BEFORE UPDATE row level trigger could have been incorrect. This problem has been resolved.

CR:535235

CR Number:   535235 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1415 02 Jul 2008 Fixed 10.0.1 3720 02 Jul 2008 Fixed 11.0.1 1874 19 Nov 2008 Fixed Description The Listener utility (dblsn) with persistent connection turned off, may have failed to confirm message delivery or action execution. This may also have caused the MobiLink server to report protocol errors. This has been fixed.

CR:535244

CR Number:   535244 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1413 03 Jul 2008 Fixed 11.0.1 1869 19 Nov 2008 Fixed Description The IIS relay server would have leaked one mutex handle per http request. This has now been fixed. A workaround is to set the worker recycling option for IIS to ON, in order to keep the leak under control.

CR:535363

CR Number:   535363 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 02 Jul 2008 Fixed 11.0.1 1875 19 Nov 2008 Fixed Description The encrypted form of a user password that had been set by a CREATE USER, or an ALTER USER, statement could have been interpreted incorrectly if the transaction log was translated by the Translation utility (dbtran) and the resulting SQL file re-executed. This was likely to be a problem only for databases using multi-byte character sets, and has now been fixed.

CR:535586

CR Number:   535586 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1422 09 Jul 2008 Fixed 10.0.1 3723 09 Jul 2008 Fixed 11.0.1 1882 19 Nov 2008 Fixed Description If an index was defined in the reference database as: create index idx on t(a asc, b asc, c asc) The UltraLite Initialize Database utility (ulinit) would have created the index as: create index idx on t(c asc, b asc, a asc). reversing the order of the columns. This has been corrected and ulinit will now create the index in the same order as the reference database. Workaround Description  None.

CR:535591

CR Number:   535591 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 03 Jul 2008 Fixed 11.0.1 1876 19 Nov 2008 Fixed Description An error would have been reported if a string of connection, or synchronization, parameters used parentheses inside a sublist. For example: stream=http(host=myhost;url_suffix=root/(MyName)/ml;port=80) This has now been fixed.

CR:535592

CR Number:   535592 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 03 Jul 2008 Fixed 11.0.1 1876 19 Nov 2008 Fixed Description If a CREATE EXTERNLOGIN statement was executed with an empty string for the password, the password recorded in the transaction log would have been incorrect. This has been fixed.

CR:535627

CR Number:   535627 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1867 19 Nov 2008 Fixed Description The database properties CleanablePagesAdded and CleanablePagesCleaned could have reported that there were pages to clean when in actuallity there were none. This would have happened if a dbspace with cleanable pages was dropped. This has now been fixed.

CR:535637

CR Number:   535637 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 04 Jul 2008 Fixed 11.0.1 1867 19 Nov 2008 Fixed Description If execution of a LOAD TABLE statement failed, and the table was large, database corruption could have resulted. The server may have freed a page twice. This has been fixed.

CR:535643

CR Number:   535643 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 04 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description Cancelling an ALTER TABLE statement for a large table, may have left the database in a corrupt state. This has been fixed.

CR:535662

CR Number:   535662 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 04 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description A SQL Anywhere JSON SERVICE may have returned unencoded control characters when the server wrote content that was greater than 256 bytes. This has been fixed. Strings containing control characters, such as newline, are now always encoded (i.e. "\n" is returned rather than 0x0A).

CR:535799

CR Number:   535799 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1433 21 Jul 2008 Fixed 10.0.1 3730 21 Jul 2008 Fixed 11.0.1 1892 19 Nov 2008 Fixed Description Executing queries using SELECT FIRST or SELECT TOP N, referencing proxy tables to a remote DB2 server, would have failed with a syntax error. DB2 does not support the FIRST and TOP N syntax; instead, the query must use FETCH FIRST ROW ONLY for FIRST, or FETCH FIRST N ROWS ONLY for TOP N. This problem has now been fixed.

CR:535804

CR Number:   535804 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description Values for SOAP input TIME and DATETIME data types were incorrectly converted to the server's locale if the value contained a negative time zone offset, with a nonzero minute field, i.e. GMT-03:30 (Newfoundland). This has been fixed. In addition the processing of DATE values has modified with this change. The TZ offset if provided with an input DATE value is now ignored, and the TZ offset is no longer appended to an output DATE value (within the HTTP/SOAP response).

CR:535817

CR Number:   535817 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description Sybase Central was not able to attach to a tracing db when the server was set to ignore all broadcasts (-sb 0), and no PORT number was specified. This has been fixed. Note, this is a follow-up to Engineering case 530790.

CR:535849

CR Number:   535849 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description An application using the iAnywhere JDBC driver was not able to change the connection isolation level to one of the SA Snapshot Isolation levels. This problem has now been resolved. To use one of the SA Snapshot Isolation levels, the application can now call the Connection.setTransactionIsolation method with one of the following values: for applications using ianywhere.ml.jdbcodbc.IDriver, use: ianywhere.ml.jdbcodbc.IConnection.SA_TRANSACTION_SNAPSHOT ianywhere.ml.jdbcodbc.IConnection.SA_TRANSACTION_STATEMENT_SNAPSHOT ianywhere.ml.jdbcodbc.IConnection.SA_TRANSACTION_STATEMENT_READONLY_SNAPSHOT for applications using ianywhere.ml.jdbcodbc.jdbc3.IDriver, use: ianywhere.ml.jdbcodbc.jdbc3.IConnection.SA_TRANSACTION_SNAPSHOT ianywhere.ml.jdbcodbc.jdbc3.IConnection.SA_TRANSACTION_STATEMENT_SNAPSHOT ianywhere.ml.jdbcodbc.jdbc3.IConnection.SA_TRANSACTION_STATEMENT_READONLY_SNAPSHOT

CR:535861

CR Number:   535861 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 04 Jul 2008 Fixed 10.0.1 3721 04 Jul 2008 Fixed 11.0.1 1876 19 Nov 2008 Fixed Description Updates to the OLE DB schema support procedures were not installed into the database using the Upgrade utility (dbupgrad) or when executing an ALTER DATABASE UPGRADE statement. They were installed though when the PROCEDURE ON clause was used with ALTER DATABASE UPGRADE. To ensure that dbupgrad will perform the OLE DB update, the ALTER DATABASE UPGRADE support procedures will now update and/or install the latest OLE DB schema support procedures. Since PROCEDURE ON is no longer required for the OLE DB update, you are no longer forced to update other system procedures.

CR:535973

CR Number:   535973 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1418 04 Jul 2008 Fixed 10.0.1 3722 04 Jul 2008 Fixed 11.0.1 1878 19 Nov 2008 Fixed Description Changes made to property values on the "Client Properties" page, in a server message store's property window, would not have been saved if the client was "(Default)". This has been corrected so that they are now saved correctly. Also, if connecting using a QAnywhere connection profile was not possible, Sybase Central would have crashed rather than reporting the error. This has been corrected as well.

CR:535983

CR Number:   535983 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) 11.0.0 1417 07 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description The usage messages for the QAnywhere Stop utility (qastop) did not display correctly on some non-english systems. This has been fixed.

CR:535988

CR Number:   535988 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1418 07 Jul 2008 Fixed 10.0.1 3722 07 Jul 2008 Fixed 11.0.1 1878 19 Nov 2008 Fixed Description Attempting to setting the inline or prefix amount of a blob column to 32768 on a 32K pagesize database would have failed with the error: 'Illegal column definition: Column 'xxx' inline value '-32768' is invalid" This has now been fixed. A workaround is to use the value 32767. Doing so does not affect the amount of inline space available for the column as there is always some page overhead that is unusable for prefix data.

CR:535990

CR Number:   535990 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1416 07 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description The banner for the certificate utilities createcert, viewcert, and createkey could have been mangled on non-English systems. This has been fixed.

CR:536001

CR Number:   536001 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1418 07 Jul 2008 Fixed 11.0.1 1864 19 Nov 2008 Fixed Description When autostopping a database, the server could have failed assertion 201137 - "Concurrent outstanding file growth requests." This would have been very rare, and timing dependeding. It was also possible to see this assertion when shutting down the server while a DDL operation, typically a long running one, was underway. This has now been fixed.

CR:536015

CR Number:   536015 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) 11.0.0 1421 07 Jul 2008 Fixed 10.0.1 3723 07 Jul 2008 Fixed 11.0.1 1881 19 Nov 2008 Fixed Description The ALTER VIEW RECOMPILE statement can be used to rebuild the view definition of an existing view. Among other things, the statement causes the schema of the view columns to be regenerated. If column permissions, as opposed to table permissions, have been granted on a view, then the recompilation could have failed with a foreign key constraint violation on SYS.SYSCOLUMN. The server now remembers all the column permissions on the view that exist before the recompile statement is executed. After the view has been recompiled, the server automatically restores the old column permissions based on column name look-ups in the new view definition. Note that if a column of the view that no longer exists after the recompilation will have the old permissions lost. A workaround is to drop the column permissions and to restore them after the view recompilation. See also Engineering case 534294 for a related issue.

CR:536130

CR Number:   536130 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1425 08 Jul 2008 Fixed 11.0.1 1884 19 Nov 2008 Fixed Description The OUTPUT statement would have written VARBINARY values to TEXT files incorrectly. This has been fixed.

CR:536143

CR Number:   536143 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1476 07 Jul 2008 Fixed 11.0.1 1934 19 Nov 2008 Fixed Description A new MobiLink server command line option, -ppv <period>, has been added which will cause the server to print new, periodic monitoring values every <period> seconds. The suggested period is 60s. If the period is set too small, the log will grow very quickly. These values provide insight into the state of the server, and are useful for determining the health and performance of the MobiLink server. For example, one could look at the DB_CONNECTIONS and LONGEST_DB_WAIT values to look for potential problems with the -w option or in the synchronization scripts. They also provide an easy way to track system wide throughput measures such as the number of rows uploaded or downloaded per second and the number of successful syncs per second. Each row of output is prefixed with "PERIODIC:" to aid searching for and filtering out the values. The following table contains a description of the printed values: Value Description TCP_CONNECTIONS Number of TCP connections currently opened PAGES_USED Number of cache pages used PAGES_LOCKED Number of cache pages loaded into memory TCP_CONNECTIONS_OPENED Total number of connections ever opened TCP_CONNECTIONS_CLOSED Total number of connection ever closed TCP_CONNECTIONS_REJECTED Total number of connection ever rejected TCP_BYTES_READ Total number of bytes ever read TCP_BYTES_WRITTEN Total number of bytes ever written ML_NUM_CONNECTED_CLIENTS Number of connected sync client PAGES_SWAPPED_OUT Total number of pages ever swapped to disk PAGES_SWAPPED_IN Total number of pages ever read from disk PAGES_IN_STREAMSTACK Number of pages held by the network streams CPU_USAGE Amount of CPU time used by MobiLink server in microseconds NUM_COMMITS Total number of commits NUM_ROLLBACKS Total number of rollbacks NUM_SUCCESS_SYNCS Total number of successful syncs NUM_FAILED_SYNCS Total number of failed syncs NUM_ERRORS Total number of errors NUM_WARNINGS Total number of warnings DB_CONNECTIONS Number of database connections in use RAW_TCP_STAGE_LEN Length of the network work queue STREAM_STAGE_LEN Length of the high level network processing queue HEARTBEAT_STAGE_LEN Length of the queue for periodic, non-sync work CMD_PROCESSOR_STAGE_LEN Length of the queue for sync work NUM_ROWS_DOWNLOADED Total number of rows sent to remotes NUM_ROWS_UPLOADED Total number of rows received from remotes FREE_DISK_SPACE Disk space available on the temp disk in bytes LONGEST_DB_WAIT Longest length of time an active sync has been waiting for the database LONGEST_SYNC Age of the oldest sync in ms NUM_UNSUBMITTED_ERROR_RPTS Number of unsubmitted error reports MEMORY_USED Bytes of RAM in use. Windows only. SERVER_IS_PRIMARY 1 if the server is primary; 0 otherwise

CR:536173

CR Number:   536173 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1421 08 Jul 2008 Fixed 11.0.1 1881 19 Nov 2008 Fixed Description If the file containing the trusted certificates specified by the "trusted_certificates" option was not found, the error STREAM_ERROR_SECURE_ADD_TRUSTED_CERTIFICATE was reported, which was not very specific. Now STREAM_ERROR_SECURE_TRUSTED_CERTIFICATE_FILE_NOT_FOUND is reported, as was done in 10.0 and previous versions.

CR:536335

CR Number:   536335 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1417 08 Jul 2008 Fixed 10.0.1 3721 08 Jul 2008 Fixed 11.0.1 1877 19 Nov 2008 Fixed Description If an application generated a result set via one DatabaseMetaData call, and then generated a second result set via another DatabaseMetaData call, then the first result set would have been automatically closed. This behaviour is not incorrect, and is consistent with many other JDBC drivers. However, some applications have had the need to keep two separate DatabaseMetaData result sets open at the same time. The iAnywhere JDBC driver has now been enhanced to allow up to three separate DatabaseMetaData result sets to remain open at the same time.

CR:536347

CR Number:   536347 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2183 03 Mar 2009 Fixed 11.0.0 1592 03 Mar 2009 Fixed 10.0.1 3856 03 Mar 2009 Fixed 9.0.2 3801 03 Mar 2009 Fixed Description Executing a LOAD TABLE statement with the clause CHECK CONSTRAINTS OFF, may have failed if the table being loaded had publications. This has been fixed.

CR:536370

CR Number:   536370 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3749 19 Aug 2008 Fixed Description For workloads that consisted of very inexpensive queries (for example, where each statement was executed in less than a millisecond), the server performance was slower than previous versions. This has been improved. As part of this change, a larger class of statements now bypasses query optimization. The properties QueryBypassed and QueryOptimized can be used to measure how many statements bypass optimization, or use the full query optimizer. The time required when a table was first accessed could have been slower than previous versions. This was particularly true for databases with many columns, and was very noticeable on CE platforms. This has been fixed. Further, in some cases the plan text for a simple statement could show the table name instead of the correlation name. This has also been fixed.

CR:536374

CR Number:   536374 Product Name:   UltraLite Product Component:   HotSync Conduit Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1441 28 Jul 2008 Fixed 10.0.1 3734 28 Jul 2008 Fixed 11.0.1 1900 19 Nov 2008 Fixed Description HotSync may have logged a -305 error for a synchronization failure, and potentially other database corruption. This has been fixed. Workaround Description  None. Smaller data sets (~2 MB) succeed though. Larger data sets over tcpip without hotsync also succeed.

CR:536388

CR Number:   536388 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1421 09 Jul 2008 Fixed 11.0.1 1883 19 Nov 2008 Fixed Description In rare situations, a busy HTTP server may have timeouted a connection as the request was queued, causing the server to crash. This has been fixed.

CR:536541

CR Number:   536541 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1475 10 Sep 2008 Fixed 10.0.1 3756 10 Sep 2008 Fixed 11.0.1 1934 19 Nov 2008 Fixed Description If an application attempted to update or delete from a proxy table joined with a local table, then the server may have failed an assertion, or crashed. The server will now correctly give error -728 'Update operation attempted on non-updatable remote query'.

CR:536543

CR Number:   536543 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1431 17 Jul 2008 Fixed 10.0.1 3727 17 Jul 2008 Fixed 11.0.1 1890 19 Nov 2008 Fixed Description During diagnostic tracing, CONNECT and DISCONNECT request, as well as other information, could have been missing for a connection. DISCONNECT request were missing for some user connections, and CONNECT request and all statistics were missing for internal connections. This has been fixed. As well, some internal connections will be logged with both CONNECT and DISCONNECT requests, while others will not be displayed.

CR:536563

CR Number:   536563 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1423 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 9.0.2 3694 10 Jul 2008 Fixed 11.0.1 1883 19 Nov 2008 Fixed Description The insert performance sample (instest) shipped with SQL Anywhere did not correctly assign values to integer columns on 64-bit big-endian platforms. Depending on the definition of the table being used, may have caused instest to terminate prematurely. The instest sample has now been corrected. This problem can be worked around by modifying the FillItem() function in instest.sqc to use an "int", instead of a "long", in the cast performed for the DT_INT/DT_UNSINT case.

CR:536568

CR Number:   536568 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1264 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 11.0.1 1883 04 Dec 2008 Fixed Description Using the SQL Anywhere Support utility (dbsupport) to check for updates on HP-UX and AIX would have failed to check for 32-bit client updates. This has been fixed.

CR:536588

CR Number:   536588 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) 11.0.0 1423 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 11.0.1 1883 19 Nov 2008 Fixed Description If an application connected using a TDS based client (i.e. jConnect, iAnywhere JDBC) and attempted to use a procedure in the FROM clause of a SELECT statement, then the TDS client may have reported a TDS protocol error. This problem has now been fixed.

CR:536594

CR Number:   536594 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1423 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 11.0.1 1883 19 Nov 2008 Fixed Description If an external function that was defined to return an integer value was assigned to a variable declared as INT, a "Value out of range for destination" error would have been given. This has been fixed.

CR:536608

CR Number:   536608 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1424 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 11.0.1 1884 19 Nov 2008 Fixed Description Calling sa_set_option('AcceptCharset', '+'); from within a stored procedure that is called via an HTTP request should set the response to the database charset whenever possible, but when a client specified the database charset it was only selected when its q-value was among the highest. This has been fixed so that the response uses database charset if specified by the client, regardless of q-value preference. Example: SA server uses ISO-8859-1 charset, client specifies Accept-Charset:UTF-8,IBM850;q=0.8,ISO-8859-1;q=0.5 Although least preferred by the client, SA will respond with ISO-8859-1 if SA_SET_HTTP_OPTION('AcceptCharset', '+'); has been called (from within a procedure servicing the HTTP request).

CR:536620

CR Number:   536620 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1423 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 9.0.2 3694 10 Jul 2008 Fixed 11.0.1 1883 19 Nov 2008 Fixed Description The OLE DB provider's ICommandWithParameters::SetParameterInfo() method may have caused an access violation, depending on the order of parameter indexes in rgParamOrdinals, which is one of the input parameters to the method. The problem may have also occurred if SetParameterInfo() was called after ICommandPrepare::Prepare(). This problem has now been fixed.

CR:536739

CR Number:   536739 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) 11.0.0 1424 10 Jul 2008 Fixed 10.0.1 3724 10 Jul 2008 Fixed 11.0.1 1884 19 Nov 2008 Fixed Description The server could could have raised assertion 102802 - "Unable to undo index changes resulting from a failed column alteration" if an ALTER statement failed, or was cancelled. This has now ben fixed.

CR:536746

CR Number:   536746 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1432 18 Jul 2008 Fixed 10.0.1 3727 18 Jul 2008 Fixed 11.0.1 1891 19 Nov 2008 Fixed Description When an encryption library could not found, the MobiLink server would have issued a misleading message indicating corruption: Invalid or corrupt network interface library: xxxxx This has been corrected so that now the MobiLink server issues the message: Failed to load library xxxxx he documentation for the load library message indicates that a license may be required, which is appropriate in this case.

CR:536805

CR Number:   536805 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1465 20 Aug 2008 Fixed 10.0.1 3747 20 Aug 2008 Fixed 9.0.2 3736 08 Oct 2008 Fixed 11.0.1 1925 19 Nov 2008 Fixed Description Grouping queries containing a CUBE, ROLLUP or GROUPING SETS clause may have returned incorrect results. The query must also have had a HAVING clause with at least one null sensitive predicate (e.g., 'T.C IS NULL' , 'T.C IS NOT NULL' ). This has been fixed. An example: select dim1, dim2, sum (val1), stddev (val2) from tt group by cube (dim1, dim2) having dim1 is not null or dim2 is not null

CR:536808

CR Number:   536808 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1429 14 Jul 2008 Fixed 10.0.1 3725 14 Jul 2008 Fixed 11.0.1 1885 19 Nov 2008 Fixed Description The server tracks dependencies of views on other views and tables. If a view referenced another view and the view definition of the referenced view was "flattened" or "inlined" within that of the referencing view, then the server could have failed to correctly record the dependency information. The server now behaves correctly when recording dependency information in this situation. Any existing views can have their dependency information recorded correctly by being recompiled.

CR:536921

CR Number:   536921 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1458 11 Aug 2008 Fixed 10.0.1 3743 11 Aug 2008 Fixed 9.0.2 3710 11 Aug 2008 Fixed 11.0.1 1918 19 Nov 2008 Fixed Description Applications using the iAnywhere JDBC driver, could have crashed or hung if a process ran out of memory. This has been fixed so that it will now either fail gracefully, or cause an assertion with an appropriate error message, depending on the circumstances. Workaround Description  None.

CR:536966

CR Number:   536966 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3802 04 Mar 2009 Fixed Description The server may have crashed if a rank function (see SQL Functions->Function types->Rank functions in the SQL Usage guide) was used on constants. The row_number() function in the example below: select x from ( select V1.*, row_number() over ( order by b ) AS x from ( select *, 7 as b from T1 order by 1 ) V1 ) V2 is used on column "b" of the nested table expression "V1", and column "b" is a constant there. This has been fixed.

CR:537126

CR Number:   537126 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1429 14 Jul 2008 Fixed 11.0.1 1888 20 Nov 2008 Fixed 10.0.1 3873 31 Mar 2009 Fixed Description When running on multiprocessor machines, statements with joins may have caused a server crash in rare conditions. This is now fixed.

CR:537147

CR Number:   537147 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1440 25 Jul 2008 Fixed 10.0.1 3734 25 Jul 2008 Fixed 11.0.1 1900 20 Nov 2008 Fixed Description If an application prepared a non-INSERT statement (i.e. a DELETE or an UPDATE statement) and used PreparedStatement.addBatch() followed by PreparedStatement.executeBatch() to execute a wide DELETE or wide UPDATE, then the results of executing the batch were unpredictable. Prepared batches were intended to be used for wide inserts only, but the iAnywhere JDBC driver did not restrict the usage to wide inserts. The driver now imposes this restriction and will throw an exception if an application attempts to use addBatch()/executeBatch() on a non-INSERT statement.

CR:537153

CR Number:   537153 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1430 15 Jul 2008 Fixed 11.0.1 1889 20 Nov 2008 Fixed Description On AIX systems, in some very rare circumstances, the server could have crashed while listening for network broadcasts. This has been fixed.

CR:537164

CR Number:   537164 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) 11.0.0 1430 16 Jul 2008 Fixed 11.0.1 1889 20 Nov 2008 Fixed Description The server assigns a unique object id for every object created in the database. The object ids are stored in the catalog table SYS.ISYSOBJECT. When objects are deleted, their ids are reused for new objects when the ids being released are at the end of the currently allocated range. Under concurrent execution of DDL operations it was possible for the server to avoid reusing some object ids even when it was possible to do so. There was no likely adverse effect of this deficiency, which has now been corrected.

CR:537170

CR Number:   537170 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1429 15 Jul 2008 Fixed 11.0.1 1888 20 Nov 2008 Fixed Description The Interactive SQL utility (dbisql) would have crashed when the Plan Viewer window was oipened if the SQL Anywhere plugin was not registered. This has been fixed.

CR:537171

CR Number:   537171 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1431 16 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description The search condition REGEXP and system function REGEXP_SUBSTR() were using the database's collation to determine if a literal, or character class range, in the pattern matched the string. For example, if the database was case insensitive and accent insensitive, matches were case insensitive and accent insensitive as well. Ranges were evaluated using the collation sort order. This resulted in different behavior than other tools such as Perl, Java, .NET, etc. This has been fixed so that REGEXP and REGEXP_SUBSTR() only match a literal in a pattern if it is the exact same character. Ranges in character classes (for example '[A-F]') only match characters which have character set encoding greater than or equal to the encoding of the first character in the range (A in '[A-F]') and less than or equal to the encoding of the second character in the range (F in '[A-F]'). Note, this change does not affect the SIMILAR TO search expression, which continues to use the collation to determine character equivalence and evaluate character class ranges.

CR:537172

CR Number:   537172 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1494 16 Sep 2008 Fixed 11.0.1 1954 20 Nov 2008 Fixed Description In some cases, an execution plan using a parallel execution strategy could have used a low-memory fallback strategy, even though there was sufficient memory for it to complete. The QueryLowMemoryStrategy property would have increased if the low memory strategy for the operator was used. This problem has been fixed.

CR:537177

CR Number:   537177 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1431 17 Jul 2008 Fixed 11.0.1 1890 20 Nov 2008 Fixed Description The search conditions SIMILAR TO and REGEXP, when used with the sub-character classes [[:upper:]] and [[:lower:]], were case insensitive on a case insensitive database. This has been fixed so that [[:upper:]] only matches upper case characters and [[:lower:]] only matches lower case characters, regardless of the database case sensitivity.

CR:537333

CR Number:   537333 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1422 15 Jul 2008 Fixed 11.0.1 1882 20 Nov 2008 Fixed Description HTTP clients going through the Relay Server may now optionally include the IAS-RS-Cookie header with the value set to 'reset' in the first request within the session. This was added in order to defeat the old standard cookie memorized by HTTP proxies, like the Blackberry MDS. If the client has full control of cookie caching, and a new http session will not reuse an old cookie, then implementation of this option is not needed in the client. This feature is suitable for Blackberry devices behind MDS, where the client application does not have real control on when to end the underlying HTTP session.

CR:537337

CR Number:   537337 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1439 16 Jul 2008 Fixed 10.0.1 3733 16 Jul 2008 Fixed 11.0.1 1898 20 Nov 2008 Fixed Description Calling the ODBC function SQLGetProcedureColumns() would have failed with the error -143 "Column 'remarks' not found" when using a SQL Anywhere ODBC driver from a version prior to 10.0 and connected to version 10.0 or later server. This was due the ODBC drivers prior to version 10.0 referencing the SYSPROCPARM.remarks column in the SQLGetProcedureColumns() function, which had been dropped in version 10.0 and later database files. The SYSPROCPARM.remarks column has been re-added as a constant NULL.