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

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

CR:558756

CR Number:   558756 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.1 2147 04 Feb 2009 Fixed 11.0.0 1570 04 Feb 2009 Fixed 10.0.1 3841 04 Feb 2009 Fixed 9.0.2 3788 04 Feb 2009 Fixed Description Attempting to execute a query that referenced a view containing a remote query, could have crashed the server. The crash would have occurred if the remote query had both GROUP BY and HAVING clauses, and/or aliases. This problem has now been fixed.

CR:558915

CR Number:   558915 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2149 10 Feb 2009 Fixed 11.0.0 1617 10 Feb 2009 Fixed 10.0.1 3894 10 Feb 2009 Fixed Description When deploying a Synchronization Model to file, any characters in .SQL files that are not supported by the OS console code page would be changed to a substitution character, even though the character would have been displayed correctly in the MobiLink plug-in. This has been fixed so that .SQL files now use UTF-8 character encoding. The generated .bat or .sh file is still written using the console code page, since it must run in a console, but the UTF-8 character encoding is now specified when the Interactive SQL utility is invoked in the .bat or .sh file.

CR:558953

CR Number:   558953 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 05 Feb 2009 Fixed Description Executing a CONNECT statement could have caused the Interactive SQL utility (dbisql) to connect to the wrong database if a connection had been already made to a database, and the CONNECT statement did not specify an engine name (ENG) or database name (DBN). This has been fixed.

CR:558973

CR Number:   558973 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.1 2147 05 Feb 2009 Fixed 11.0.0 1571 05 Feb 2009 Fixed Description Using the ATLER EXTERNAL ENVIRONMENT ... LOCATION statement to set the executable path to a MBCS string, could have caused the server to subsequently fail to launch the external environment. When fetching the external environment location from the catalog, the server was not subsequently converting the string to the OS charset. This has now been fixed.

CR:558984

CR Number:   558984 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2148 05 Feb 2009 Fixed 11.0.0 1571 05 Feb 2009 Fixed Description The JDBC sample applications incorrectly contained references to the SQL Anywhere 10 ODBC driver. This has been fixed. Comments were also added that explain the DriverManager.registerDriver and DriverManager.getConnection code.

CR:559185

CR Number:   559185 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.1 2148 05 Feb 2009 Fixed 11.0.0 1571 05 Feb 2009 Fixed Description Attempting to execute a CONNECT statement could have crashed the Interactive SQL utility (dbisql) if it was started without an initial connection. This has been fixed.

CR:559192

CR Number:   559192 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2046 19 Feb 2009 Fixed 10.0.1 3850 20 Feb 2009 Fixed Description If an application fetched columns of type NUMERIC, DATE, TIME, or TIMESTAMP, and the column was bound as a string in the client application, then performance could have decreased. The slowdown was most apparent in statements where a large number of rows were fetched with relatively little server processing per row. This has now been fixed.

CR:559197

CR Number:   559197 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.1 2148 06 Feb 2009 Fixed 11.0.0 1571 06 Feb 2009 Fixed Description When creating a new user, or changing an existing user's Profile authority setting, Sybase Central would not have always updated its group memberships in the Users & Groups folder. This has been fixed.

CR:559258

CR Number:   559258 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2295 10 Aug 2009 Fixed 10.0.1 3941 10 Aug 2009 Fixed Description The stored procedure debugger failed to report information about the size of string and numeric data types when debugging a stored procedure. This has been corrected.

CR:559360

CR Number:   559360 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.1 2148 06 Feb 2009 Fixed 11.0.0 1571 06 Feb 2009 Fixed Description Sybase Central allowed for explicitly adding members to, or removing members from, the diagnostics group, but in some instances the members would not have actually been added or removed. This has been fixed by no longer permitting this. Now members can be added to, or removed from, the diagnostics group implicitly by granting or revoking Profile authority via the user's properties dialog. In addition, Sybase Central no longer allows deleting the diagnostics, rs_systabgroup and SA_DEBUG groups, nor change any of these groups to users.

CR:559372

CR Number:   559372 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.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description If an application used one of the connection scoped external environments (i.e. PHP, PERL or one of the external C environments); and the external environment failed to start up due to high server load or time-out, then there was a chance the external environment executable would not have ended. This problem has now been fixed.

CR:559383

CR Number:   559383 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description When configuring an ODBC FileDSN on Windows, NEWPWD=* incorrectly showed up in the Advanced tab of the configuration dialog. The NEWPWD=* parameter was not actually added to the FileDSN though. This has been fixed.

CR:559399

CR Number:   559399 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2211 19 Mar 2009 Fixed 11.0.0 1605 19 Mar 2009 Fixed Description If the deleted_length of a text index was greater than 50% of the doc_length, the server should refresh the text index. However, it was possible to get into a state where the pending length was very small and the deleted_length was very large, yet refreshes still did not occur. The check for the pending_length was occurring too early and prevented the server from ever checking the pending length. As a result, the index was never being refreshed. This has been corrected so that the server now checks that one condition or the other is true to continue to the refresh code. Workaround Description  CR 559399: Not certain how this affects a production usage in any but manual refresh mode but there seems to be no obvious workaround, if it could ever be a major issue\ for the customer. Since the value for pending_length seems to be maintained correctly, that value could form the basis of deteriming an excessively stale text index.

CR:559402

CR Number:   559402 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2148 09 Feb 2009 Fixed 11.0.0 1571 09 Feb 2009 Fixed Description In previous versions of SQL Anywhere, a password connection parameter was not written to a FILEDSN (.dsn file). Beginning with version 11.0.0, the password is written to the .dsn file in the format "Password={some pwd}". This behavior is not in keeping with the spirit of the ODBC specification which states, "the PWD keyword is not stored in a .dsn file". This change in behavior occurred as a result for a change to the SQL Anywhere ODBC driver to return "Password={some pwd}", instead of "PWD={some pwd}" in the connection string. Also, "Userid=user" was returned instead of "UID=user". The Microsoft driver manager only recognizes the UID and PWD forms of the connection parameters, which caused it to add the Password parameter. This problem has been corrected. The SQL Anywhere ODBC driver will now return "UID={user};PWD={some pwd}" in the connection string, as it did in earlier versions. This will result is the Driver Manager no longer including the password.

CR:559403

CR Number:   559403 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.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description If a connection with a Configuration object failed, for example due to an incorrect password, a connection then with a corrected configuration object would have caused a SQLE_CONFIG_IN_USE error to have been thrown. This has been fixed.

CR:559412

CR Number:   559412 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.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description The OUTPUT USING statement could have failed to export the results of a DESCRIBE statement. This has been fixed.

CR:559413

CR Number:   559413 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.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed 10.0.1 3844 09 Feb 2009 Fixed Description If many connections made concurrent external environment requests, and some of these requests failed due to thread deadlock, then attempting to close one of these connections may have caused the client to hang. This problem has now been fixed.

CR:559431

CR Number:   559431 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.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description Attempting to execute an INPUT USING statement would have cause the Interactive SQL utility to crash if the connection string was empty or missing. This has been fixed.

CR:559440

CR Number:   559440 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.1 2148 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description When run on Linux systems, a server that had been handling TCP/IP connections could have displayed the message "epollerr: Bad file descriptor" in the console on shutdown. Also, under very rare circumstances on all UNIX platforms, the server could have experienced problems handling TCP/IP connections. Both of these problems have now been fixed.

CR:559446

CR Number:   559446 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.1 2044 09 Feb 2009 Fixed 11.0.0 1572 09 Feb 2009 Fixed Description If a server running on Linux systems with GTK libraries installed was auto-started, or started by the Start Server utility (dbspawn), in an X Window environment, an empty window titled "SQL Anywhere Developer Edition" would have remained visible until the server was shut down. This has been fixed.

CR:559481

CR Number:   559481 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2149 17 Feb 2009 Fixed Description Executing an ALTER TABLE statement could have caused unneccessary database growth.

CR:559600

CR Number:   559600 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2149 10 Feb 2009 Fixed Description Executing a "MESSAGE .. TO CLIENT FOR CONNECTION conn-id IMMEDIATE" statement shortly before the target connection abnormally disconnected could have resulted in the message callback being called after an API request returned an error. The abnormal disconnect could have been caused by a liveness timeout, idle timeout, DROP CONNECTION, server shut down, or other conditions. Depending on the application's message callback routine, this could have resulted in a crash or other incorrect behaviour. This has been fixed so that the message callback will not be called after an API request has returned an error due to an abnormal disconnect.

CR:559632

CR Number:   559632 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2150 10 Feb 2009 Fixed 11.0.0 1573 10 Feb 2009 Fixed 10.0.1 3845 10 Feb 2009 Fixed Description An embedded SQL PREPARE or OPEN request could have caused the application to crash in rare cases, if the connection was dropped before, or during, the request. This has been fixed.

CR:559636

CR Number:   559636 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2312 16 Mar 2010 Fixed 11.0.1 2410 16 Mar 2010 Fixed Description MobiLink clients, except UltraLiteJ, now support a new network protocol option on Windows Mobile and desktop, 'network_adapter_name', which allows clients to explicitly specify the name of the network adapter to be used to connect to a MobiLink server. Example: "network_adapter_name=Serial on USB".

CR:559653

CR Number:   559653 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed 10.0.1 3853 24 Feb 2009 Fixed Description When connected to an authenicated SQL Anywhere database from the MobiLink plug-in in Sybase Central using the "Generic ODBC DSN" option, the connection would have been read-only. This has been fixed.

CR:559678

CR Number:   559678 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.1 2149 18 Feb 2009 Fixed 11.0.0 1573 18 Feb 2009 Fixed Description Incorrect results could have been obtained with queries containing IF search expressions, aggregate functions, or references to columns not specified in the GROUP BY clause. These are now diagnosed as errors.

CR:559694

CR Number:   559694 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.1 2150 18 Feb 2009 Fixed 11.0.0 1573 18 Feb 2009 Fixed Description The persistent store was not being properly closed on open failure (such as authentification failure) with write-at-end configuration. This could have lead to problems reconnecting to the database. The store is now closed on an open failure.

CR:559810

CR Number:   559810 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.1 2150 13 Feb 2009 Fixed 11.0.0 1574 13 Feb 2009 Fixed 10.0.1 3846 13 Feb 2009 Fixed Description If an INSERT statement inserted a string into a CHAR or VARCHAR column with character-length semantics, then it was possible for the server to fail with the following assertion failure: 100914: string too long when recording operation in transaction log. In order for the failure to occur, the inserted string must have had byte-length semantics and it must have contained more characters than the column definition. Further specific characteristics of the database and statement were needed to reproduce the problem. This problem has been fixed.

CR:559813

CR Number:   559813 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2148 10 Feb 2009 Fixed Description The server would have reported the number of processors detected and some imposed limits. The messages have been changed so that they will now report: - number of processors detected (changed format) - processor limits imposed by Edition, licenses purchased, and -gt option - max number of processors that will be used Also, the Edition limit that is imposed during licensing is now also imposed by the server itself. For some Unix systems, the number of processors used can not be limited. If the number to be used exceeds the per-processor license limitation, an additional message is reported, and is unchanged from previous versions.

CR:559822

CR Number:   559822 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.1 2151 13 Feb 2009 Fixed 11.0.0 1574 13 Feb 2009 Fixed 10.0.1 3846 13 Feb 2009 Fixed Description If the optimizer selected a parallel execution plan for a query with a GROUP BY operator on the right hand side of a nested loops join, and the group by contained an AVG or other composite aggregate function, then it was possible for the statement to incorrectly generate the error: "Field unexpected during compilation". In this case the server would have continue to process other requests. This problem has been fixed. A workaround is to disable parallel plans by setting Max_query_tasks=1 as a connection option, or in the query OPTIONS clause.

CR:559844

CR Number:   559844 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed Description If a query execution plan used a multiple index scan with an Except Merge operator (EM), then it was possible for the statement to fail with an assertion failure such as the following: Assertion failed: 106502 - NULL in not-NULL work table column In order for the failure to occur, one of the indexed columns in the query must have been declared not-NULL. This has been fixed. Workaround Description  Alter the last line of the Companies view definition in this way: from FFUsers.AllCompanies where AllCompanies.Deleted = 0

CR:559864

CR Number:   559864 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.1 2150 13 Feb 2009 Fixed 11.0.0 1573 13 Feb 2009 Fixed 10.0.1 3846 13 Feb 2009 Fixed Description Connecting, disconnecting, and reconnecting using the same connection handle would have caused error -298 "Attempted two active database requests" in dbcapi. For example: conn = sqlany_new_connection(); sqlany_connect( conn, <connection_string> ); sqlany_disconnect( conn ); sqlany_connect( conn, <connection_string> ); The last sqlany_connect() call would have returned error -298. This has been fixed. The workaround is to call sqlany_free_connect() and allocate and new handle.

CR:559897

CR Number:   559897 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2150 11 Feb 2009 Fixed 11.0.0 1573 11 Feb 2009 Fixed Description If a critical error occurred and an application then called db_fini, without first closing the connection, the database could have become corrupted. This has been fixed.

CR:559898

CR Number:   559898 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) 11.0.1 2150 11 Feb 2009 Fixed 11.0.0 1574 11 Feb 2009 Fixed 10.0.1 3846 11 Feb 2009 Fixed 9.0.2 3791 11 Feb 2009 Fixed Description If an application made use of one of the Remote Data Access JDBC classes, and the application then disconnected abnormally, then the connection to the remote server was never closed. The problem did not exist if the application used one of the Remote Data Access ODBC classes instead. This problem has now been fixed.

CR:559941

CR Number:   559941 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2150 17 Feb 2009 Fixed 11.0.0 1574 17 Feb 2009 Fixed Description NULL values were not being handled properly in single-valued SELECT queries. The value was treated as if it was not null, and an unpredicatable value was used. This has been corrected.

CR:560044

CR Number:   560044 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) 12.0.0 2330 18 Mar 2010 Fixed 11.0.1 2412 18 Mar 2010 Fixed Description In some cases, an error was generated for expressions that contained only values that were known at open time. For example, the following generated a "division by zero" error: select if 1=0 then 1/0 else 42 endif val This problem occurred because the expression '1/0' was evaluated as part of building the access plan for the query. Constant expression trees were evaluated at open time in a bottom-up fashion so that the value can be used at execution time (avoiding multiple evaluations and supporting optimizations). In some cases, the expression was not actually needed, as in the above example with an IF expression. In these cases, the constant folding process could have generated an error that would not have been returned if the constant literals were replaced with field references. This has been changed. Errors generated during constant folding are no longer returned at open time. Instead, the constant expression tree is left in its original structure and evaluated at execution time if the value is needed. This execution-time evaluation will generate the related error if the value is actually needed. Workaround Description  Workaround:Rewriting the trigger to check for a divisor of 0 outside of the update statement will solve the problem.

CR:560045

CR Number:   560045 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3797 24 Feb 2009 Fixed Description When the QAnywhere consolidated database contained a large number of messages that satisfied a delete rule, and there were QAnywhere clients synchronizing frequently, it was possible that delete rules would have always failed because of database deadlock errors such as: Error: [QA] Problem evaluating transmission rules for user ianywhere.server.deleteRules: Problem updating object in repository using key "delete from ml_qa_repository from ml_qa_repository mbr where msgid in (select msgid from ml_qa_messages ml_qa_messages where status > 20 and (syncstatus = 1 or originator in ('ianywhere.connector.beajms','ianywhere.server')))": java.sql.SQLException: [Sybase][ODBC Driver][Adaptive Server Anywhere]Deadlock detected: [Sybase][ODBC Driver][Adaptive Server Anywhere]Dea Error: dlock detected This has been fixed. It is possible that some deadlock errors will still occur, but the errors will not prevent delete rules from deleting old messages.

CR:560056

CR Number:   560056 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.1 2150 12 Feb 2009 Fixed 11.0.0 1574 12 Feb 2009 Fixed 10.0.1 3846 12 Feb 2009 Fixed Description If a connection was forcibly closed by the server (via DROP CONNECTION, liveness or idle timeout), or was closed by the client libraries because of a liveness timeout, the client application could have crashed if the next operation it attempted was to open a cursor without preparing it. This has been fixed.

CR:560069

CR Number:   560069 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.1 2276 08 Jul 2009 Fixed 11.0.0 1652 08 Jul 2009 Fixed 10.0.1 3931 08 Jul 2009 Fixed Description When executing a VALIDATE statement, or running the Validation utility (dbvalid), table validation would have failed to report errors when an index did not contain all the rows in the table. This has now been corrected. Note, when validating a database with a 10.0.1 server between 3920 and 3930 inclusive, it was also possible for errors to be reported, when in fact there were no error. I this case, the 10.0.1 server should be updated to a build number of 3931 or higher, and the validation rerun to see if the errors are still reported.

CR:560080

CR Number:   560080 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3846 12 Feb 2009 Fixed 9.0.2 3792 12 Feb 2009 Fixed Description If a user-defined function was created with the DETERMINISTIC keyword, the parsed version of the CREATE FUNCTION sstatement that was placed in the catalog did not contain this keyword. The function may not then have been treated as deterministic, and if it was unloaded, the CREATE FUNCTION statement would also not have contained the keyword. This has been fixed. Note, to fix existing user-defined functions created with DETERMINISTIC, the function will need to be recreated.

CR:560107

CR Number:   560107 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 2151 13 Feb 2009 Fixed 11.0.0 1574 13 Feb 2009 Fixed 10.0.1 3846 13 Feb 2009 Fixed Description Table names in case insensitive databases are required to be unique under case insensitive comparisons, e.g., names FOO and foo refer to the same table. In some cases, the server may have allowed multiple tables with the same name that differed only in case to be created. This has been fixed so that the server will now generate the expected error. Note, once a database contains multiple tables with the same names, all variations of the name will refer to the same (somewhat non-deterministic) instance of the table. The situation can be corrected by dropping and recreating the tables. Any existing data needs to be saved and restored as necessary.

CR:560109

CR Number:   560109 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.1 2150 12 Feb 2009 Fixed Description A reboot was required after the SQL Anywhere Monitor was installed when it was to be used as a service. This problem has now been fixed, and a reboot should no longer be required.

CR:560351

CR Number:   560351 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.1 2151 13 Feb 2009 Fixed 11.0.0 1574 13 Feb 2009 Fixed 10.0.1 3846 13 Feb 2009 Fixed Description Columns of type UNIQUEIDENTIFIER were being fetched in binary format in the SQL Anywhere C API (php, Perl, Python and Ruby), where as they should have been returned as strings. This has been fixed.

CR:560678

CR Number:   560678 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.1 2154 17 Feb 2009 Fixed 11.0.0 1575 17 Feb 2009 Fixed 10.0.1 3847 17 Feb 2009 Fixed Description If a database's CHAR collation was a tailored UCA collation with a sorttype specified, then comparisons for catalog strings (such as table names and user names) would have incorrectly ignored the sorttype. For example, the Swedish collation UCA(locale=swe; sorttype=phonebook) considers 'v' and 'w' to be different characters at the primary level; however, those letters would have been considered equal during catalog string comparisons, as if the catalog collation were UCA(locale=swe) with no sorttype specified. This problem has been fixed.

CR:560902

CR Number:   560902 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.1 2153 17 Feb 2009 Fixed 11.0.0 1570 17 Feb 2009 Fixed Description Complex queries involving proxy tables may have cause the server to crash. Some known instances of this issue have been fixed.

CR:560908

CR Number:   560908 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2155 17 Feb 2009 Fixed Description When the UltraLiteJ Database Transfer tool was run on a BlackBerry device or simulator, a user may have left the password field blank assuming that the utility would use the default password "dba". However, leaving the password field blank would have resulted in a failure to connect to the database. This has been corrected. If the password is now left empty, the default password will be used to connect to the specified database.

CR:560924

CR Number:   560924 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.1 2149 17 Feb 2009 Fixed Description Executing an ALTER TABLE statement could have caused unneccessary database growth.

CR:560935

CR Number:   560935 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 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed 10.0.1 3853 24 Feb 2009 Fixed 9.0.2 3798 24 Feb 2009 Fixed Description Restoring a database from a backup archive using the RESTORE DATABASE command with the RENAME option could have corrupted the transaction log associated with the restored database. Translating the transaction log file using the dbtran.exe utility would have resulted in an error indicating that the log was missing a CONNECT operation. This has been fixed.

CR:560943

CR Number:   560943 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2156 20 Feb 2009 Fixed 10.0.1 3849 20 Feb 2009 Fixed 9.0.2 3795 20 Feb 2009 Fixed 11.0.0 1578 20 Feb 2009 Fixed Description The dbmlsync ActiveX component was not able to launch the dbmlsync application properly on Windows if some or all of the dbmlsync options are given by a file, and the dbmlsync command line contained the option @filename. This problem has now been fixed.

CR:561067

CR Number:   561067 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) 9.0.2 3794 18 Feb 2009 Fixed 11.0.1 2167 05 Mar 2009 Fixed Description The QAnywhere Agent (qaagent) now attempts to reconnect to the message store database when the connection is dropped. Notes: - The initial database connection will be retried a given number of times if the first connection fails - Command line options for connection retries and retry delay: -cr <n> (n is the number of retries to connect after a failure) -cd <n> (n is delay, in seconds, between retries) - The defaults are 3 retries with a 10 second delay between retries - If all retries fail, the QAnywhere Agent displays an error and waits to be shut down - If a database connection fails during operation, the QAnywhere Agent will go through termination steps, including finalizing connections, terminating threads and external processes, and then re-starts.

CR:561095

CR Number:   561095 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2149 18 Feb 2009 Fixed 11.0.0 1573 18 Feb 2009 Fixed Description Incorrect results could have been obtained with queries containing IF search expressions, aggregate functions, or references to columns not specified in the GROUP BY clause. These are now diagnosed as errors.

CR:561118

CR Number:   561118 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2150 18 Feb 2009 Fixed 11.0.0 1573 18 Feb 2009 Fixed Description The persistent store was not being properly closed on open failure (such as authentification failure) with write-at-end configuration. This could have lead to problems reconnecting to the database. The store is now closed on an open failure.

CR:561122

CR Number:   561122 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.1 2184 26 Feb 2009 Fixed 9.0.2 3799 24 Mar 2009 Fixed Description The .NET QAManagerBase class now supports ExceptionListener delegates, which allows for applications to be notified of QAExceptions that occur while receiving messages on the background thread. The following are the relevant APIs: /// <summary> /// ExceptionListener delegate definition. /// </summary> /// <param name="ex">The exception that occurred.</param> /// <param name="msg">The message that was received, or null if the message /// could not be constructed.</param> public delegate void ExceptionListener( QAException ex, QAMessage msg ); /// <summary> /// Sets an <see cref="ExceptionListener"/> delegate to receive QAExceptions /// when processing QAnywhere messages asynchronously. /// </summary> /// <param name="address">The address of messages.</param> /// <param name="listener">The exception listener to register.</param> public void SetExceptionListener( string address, ExceptionListener listener ); In 10.0.x and later, the .NET and Java QAManagerBase class now supports exception listeners. The .NET and Java QAManagerBase class now supports a property, RECEIVER_INTERVAL, that represents the maximum wait interval (in milliseconds) in the background receiver thread for receiving messages. The default is 60000 milliseconds. As with other QAManager properties, this property must be set before calling an Open() method. The .NET and Java QAManagerBase class now supports a ReOpen() method that can be called in an ExceptionListener or MessageListener to re-establish connections to the message store database. Following is the API description. /// <summary> /// Reopens the QAManagerBase. This re-establishes connections to the message /// store, without releasing any resources. This method may called in a /// message or exception listener, and in that case it is not necessary to /// call Start() again. This method simply executes Close() then Open() if /// not called in a listener, and in that case Start() must be called to /// restart receiving of messages. /// </summary> /// <exception cref="iAnywhere.QAnywhere.Client.QAException"> /// if there is a problem reopening the manager. /// </exception> public void ReOpen();

CR:561127

CR Number:   561127 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2158 24 Feb 2009 Fixed Description By default, the reload.sql script generated by the Unload utility (dbunload_) includes calls to a temporary procedure (sa_unload_display_table_status) to display progress messages when loading tables and creating indexes. The -qr command line option will now suppress generation of these calls.

CR:561311

CR Number:   561311 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2156 20 Feb 2009 Fixed Description Executing a MESSAGE ... IMMEDIATE statement shortly before a connection was disconnected, could, in rare timing dependent cases, have caused the application to crash, or the message callback to run after the connection was disconnected. This has been fixed.

CR:561321

CR Number:   561321 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.1 2156 20 Feb 2009 Fixed Description When aggregate functions processed a NULL value for one or more rows, they generate the following warning: (SQLCODE 109) "Null value eliminated in aggregate function". If the aggregate function was specified with DISTINCT for its argument, this warning was not set for execution plans that used the SingleRowGroupBy or OrderedGroupBy execution algorithms. This has now been corrected.

CR:561378

CR Number:   561378 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2156 20 Feb 2009 Fixed 11.0.0 1578 24 Feb 2009 Fixed Description The Relay Server Outbound Enabler could have logged one of the following error messages in the log file: "Failed to retrieve session[x]" or "Session mismatch: session[x].snum=y instead of z" or "Session mismatch: session[x].sfp=y instead of z". when a client unexpectedly disconnected from a Relay Server in the middle of sending a request, or receiving a response. These errors would have happened in a Relay Server farm environment with more than one Relay Servers in the farm and in particular, in the general case when using an Afaria client or a QAnywhere client running a listener. This has now been fixed.

CR:561524

CR Number:   561524 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.1 2156 20 Feb 2009 Fixed 11.0.0 1578 20 Feb 2009 Fixed Description Under very specific and rare memory conditions, the server could have crashed while performing a sort. This has been fixed.

CR:561553

CR Number:   561553 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 2156 20 Feb 2009 Fixed 11.0.0 1578 20 Feb 2009 Fixed 10.0.1 3850 20 Feb 2009 Fixed 9.0.2 3797 20 Feb 2009 Fixed Description When a query of the form "SELECT f(c) from t where t.c < 5", where f() was a user-defined function and t was a proxy table, was executed the server would have attempted to push the "where c < 5" to the remote server in order to reduce the number of rows being returned. Unfortunately, due to the fix for Engineering case 555959, this behaviour was changed such that the WHERE clause was no longer getting pushed to the remote, resulting in more rows being fetched from the remote than necessary. Note that the fix for case 555959 resulted in a performance degradation only, the resulting result set was still correct. Nevertheless, this has now been resolved and the WHERE clause will now properly be pushed to the remote server when it is safe to do so.

CR:561554

CR Number:   561554 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.1 2156 24 Feb 2009 Fixed 11.0.0 1578 24 Feb 2009 Fixed Description It was possible for the server to crash while processing a specific builtin function in the context of a procedure. This has been fixed.

CR:561596

CR Number:   561596 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2156 24 Feb 2009 Fixed 10.0.1 3946 24 Feb 2009 Fixed Description Incorrect values were being used by the SQL scanner for some hexadeciml constants. This was corrected

CR:561603

CR Number:   561603 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.1 2156 20 Feb 2009 Fixed 11.0.0 1578 20 Feb 2009 Fixed Description Synchronizing with UltraLiteJ, through the Relay Server to a MobiLink server farm with more than one server, would have caused erratic behaviour. This has been fixed.

CR:561616

CR Number:   561616 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2251 26 May 2009 Fixed 10.0.1 3897 26 May 2009 Fixed Description Application errors could have occurred after opening and closing more than 255 connections. Each .NET connection allocated two SQLCAs, but only one was freed when the connection was closed. The other would not have been freed until the connection was garbage collected. This has been fixed. A workaround for this problem is to call GC.Collect() regularly.

CR:561801

CR Number:   561801 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.1 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed Description In rare circumstances, selecting a table in the tree and clicking its Data tab, would either have caused an "Invalid ORDER BY specification" error or the table's rows would not be sorted by the primary key. This has been fixed.

CR:561813

CR Number:   561813 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2157 24 Feb 2009 Fixed Description The MobiLink server could have crashed when using the -xo option ("specify network protocol and options for version 8 and 9 clients"). Monitoring pre-10.0.0 synchronizations would also have had erratic behaviour. These issues have been fixed.

CR:561816

CR Number:   561816 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed Description The Relay Server State Manage (rshost) would have crashed if its configuration file was missing or invalid, or if a non-switched command line argument was used (i.e. one that was not preceded with '-' in Unix, or '-' or '/' in Windows). This has been fixed.

CR:561820

CR Number:   561820 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed Description The iAS ODBC driver for Oracle could have leaked memory when fetching binary data (CLOB, BLOB, NCLOB, LONG VARCHAR, and LONG RAW) from an Oracle database. This problem would only have occurred when sending the fields as part of the MobiLink download stream to the remote. This has now been fixed.

CR:561825

CR Number:   561825 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2182 24 Feb 2009 Fixed 11.0.0 1592 24 Feb 2009 Fixed Description The PHP external environment did not expose all of the $_SERVER fields during an HTTP request, as specified by the CGI/1.1 specification. This has been fixed.

CR:561831

CR Number:   561831 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2194 31 Mar 2009 Fixed Description The PHP external environment, when used in the HTTP context, was not sending the appropriate HTTP status code back to the client. This has been fixed.

CR:561839

CR Number:   561839 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.1 2157 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed Description There was a possibility, although small, that a busy SQL Anywhere server may have truncated HTTP response data. This has been fixed.

CR:561989

CR Number:   561989 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.1 2158 24 Feb 2009 Fixed 11.0.0 1580 24 Feb 2009 Fixed Description The Interactive SQL utility (dbisql) would have failed to launch on Windows machines when run as a console application, if a connection parameter was given and the parameter value contained a space. This has been fixed.

CR:562026

CR Number:   562026 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2147 25 Feb 2009 Fixed Description Using the UltraLiteJ Database Load utility (ULjLoad) with the -a, -i or -f options may have caused the tool to crash or produce incorrect results. The rows loaded without the -i switch would still be synced to the server. The -a switch would not load schema information from an existing database file. The -f switch would crash the tool. These problems have now been fixed.

CR:562027

CR Number:   562027 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2158 25 Feb 2009 Fixed 11.0.0 1580 25 Feb 2009 Fixed 10.0.1 3853 25 Feb 2009 Fixed Description When running on Sun SPARC systems, the MobiLink client (dbmlsync) would have complained about "missing transaction log files", if there were any offline transaction log files bigger than 2GB. This problem now been fixed.

CR:562037

CR Number:   562037 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2156 25 Feb 2009 Fixed Description When using the UltraLiteJ Database Load utility (uljload) with the -d option, in combination with the -a option, in order to load data into an existing database with the schema information in it, no data was loaded into the database. This has been fixed.

CR:562039

CR Number:   562039 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2158 25 Feb 2009 Fixed 11.0.0 1580 25 Feb 2009 Fixed 10.0.1 4070 13 May 2010 Fixed Description The start times for synchronizations reported by the MobiLink Monitor and the MobiLink Server, when used with the -vm option, could have been incorrect if the MobiLink Server had been running for several days. Also, the output for the -vm option could have been incorrect if a request used non-blocking download acks, and phase durations reported by -vm option could have been slightly different than phase times reported by the MobiLink Monitor. These issues have now been fixed.

CR:562083

CR Number:   562083 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2159 26 Feb 2009 Fixed 11.0.0 1582 26 Feb 2009 Fixed 10.0.1 3854 26 Feb 2009 Fixed Description The MobiLink server could have silently ignored bad HTTP requests. In particular, subsequent requests received by MobiLink server B, for a session started in MobiLink server A, would have been silently ignored. The error was particularly likely to appear if an HTTP intermediary was misbehaving and sending different HTTP requests for the same session to different MobiLink servers. This has been fixed, and this case will now issue an error.

CR:562171

CR Number:   562171 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.1 2160 26 Feb 2009 Fixed 11.0.0 1582 26 Feb 2009 Fixed Description The SQL Anywhere server generates "expression error" messages for generic semantical problems in queries. Under certain circumstances, the server could have generated an expression error with a parameter that did not point to the correct problematic part of the query. For example, the following query: select manager_id, sum(emp_id), max(manager_id) over (order by manager_id rows between manager_id preceding and salary following) as max_mgr from employee where manager_id > 5 group by manager_id, salary, max_mgr would have resulted in an error "Expression error near 'employee.manager_id > 5'", rather than the more appropriate "Expression error near 'max(employee.manager_id) over( ... ) ... as max_mgr". The real problem with this query is that the alias 'max_mgr' cannot refer to a window aggregate expression, as the alias is part of the group by list. This problem has been resolved.

CR:562181

CR Number:   562181 Product Name:   UltraLite Product Component:   UltraLite for M-Business Anywhere Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2160 27 Feb 2009 Fixed 11.0.0 1582 27 Feb 2009 Fixed Description The UltraLite M-Business component was missing the following methods: Class SyncParms: String getPublications() setPublications( String publication_list ) These methods are used to set the publications that will be used for synchronization (publications control which tables get synchronized). The publications are specified as a comma separated string. Earlier versions of the UltraLite M-Business API used a "publication mask" to identify the publications for synchronization. A mask was an internal number representing a set of publications. The publication mask methods were removed in version 11.0, and these methods were meant to replace them.

CR:562216

CR Number:   562216 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) 08 May 2009 Fixed Description Using database files with empty filenames like ".db" or " .db" caused various problem. different kind of problems. Now, for database, dbspace, transaction log and mirror log files, the server no longer allows file names like this.

CR:562227

CR Number:   562227 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2160 26 Feb 2009 Fixed Description Aggregates in sub-queries, containing outer references, were not always handled correctly. This could have resulted in: - bogus diagnostics regarding misplaced aggregation - some illegal usages were not diagnosed - incorrect results in some cases This has been corrected.

CR:562235

CR Number:   562235 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   6.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Feb 2009 Fixed Description When a new column is added in the table editor, the column now defaults to allowing or prohibiting nulls, depending on the value of the PUBLIC allow_nulls_by_default option. as well,changing a column's data type to a domain (either in the table editor or in the column property sheet) now updates the column's nulls setting to allow or prohibit nulls, depending on the chosen domain's nulls setting. If the domain does not explicitly allow or prohibits nulls, then the column's nulls setting is not updated.

CR:562236

CR Number:   562236 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2251 29 May 2009 Fixed 11.0.0 1621 29 May 2009 Fixed 10.0.1 3897 29 May 2009 Fixed 9.0.2 3840 29 May 2009 Fixed Description In some cases, client applications running on Solaris systems may have hung while communicating with the server through shared memory. Other symptoms may also have included communication errors between the client and the server. This was more likely to happen on multi-processor machines. This has been fixed.

CR:562245

CR Number:   562245 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2160 27 Feb 2009 Fixed 11.0.0 1582 27 Feb 2009 Fixed 10.0.1 3854 27 Feb 2009 Fixed Description Using the MobiLink file-based download to transfer files on Palm devices to a VFS volume, could have failed. The error reported would have been STREAM_ERROR_INTERNAL. On some devices, VFSFileSeek returns an EOF error when seeking to the end of file, but the seek actually succeeds. A work around for this problem has been implemented.

CR:562258

CR Number:   562258 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) 11.0.1 2160 02 Mar 2009 Fixed Description On Windows 2003, and sometimes on Windows XP, it was possible to start both a personal server and network server which listened on the same TCPIP port. If this occurred, clients could unexpectedly, and unreliably, get "Database server not found" errors. This has been fixed As part of this change, network servers on Windows Vista and Windows 2008 no longer start a TCPIP listener on the 127.0.0.1:<port> address by default. Connections to this address are still accepted by the TCPIP listener which starts on the 0.0.0.0:<port> address.

CR:562318

CR Number:   562318 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.1 2160 26 Feb 2009 Fixed 11.0.0 1582 26 Feb 2009 Fixed Description A column check constraint's property sheet did not show the constraint's column, while a table check constraint's property sheet showed a "Column:" label with an no column name. A boolean test on the constraint type was inverted. This has been fixed.

CR:562398

CR Number:   562398 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.1 2160 26 Feb 2009 Fixed Description Aggregates in sub-queries, containing outer references, were not always handled correctly. This could have resulted in: - bogus diagnostics regarding misplaced aggregation - some illegal usages were not diagnosed - incorrect results in some cases This has been corrected.

CR:562414

CR Number:   562414 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.1 2160 26 Feb 2009 Fixed 11.0.0 1582 26 Feb 2009 Fixed 10.0.1 3854 26 Feb 2009 Fixed Description In exceptionally rare circumstances, the server could have hung during startup. This hang would only have occurred when the server was run on a multi-processor machine. This has been fixed.

CR:562456

CR Number:   562456 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.1 2160 27 Feb 2009 Fixed 11.0.0 1582 27 Feb 2009 Fixed Description Changing a column's data type via its property sheet would have been reflected immediately in the Table editor when switching pages in the property sheet. As well, the change would not have been reverted if Cancel was clicked in the property sheet. This has been fixed.

CR:562534

CR Number:   562534 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3856 02 Mar 2009 Fixed 9.0.2 3801 02 Mar 2009 Fixed Description Executing a query of the form "select ... into #temp ...", or a query with a stored procedure in the FROM clause, may have caused the server to crash. This would have occurred if the statement contained a CONVERT or CAST function call to a user-defined type, or a WITH( column-name <user-defined type>, ...) clause. This has been fixed.

CR:562535

CR Number:   562535 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.1 2164 02 Mar 2009 Fixed 11.0.0 1584 02 Mar 2009 Fixed 10.0.1 3856 02 Mar 2009 Fixed Description The server may have crashed when trying to build a plan containing a hash filter. This has been fixed.

CR:562605

CR Number:   562605 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2161 02 Mar 2009 Fixed 11.0.0 1583 02 Mar 2009 Fixed 10.0.1 3855 02 Mar 2009 Fixed Description If more than one of the dblocate filtering options (-p, -s, -ss) was used and a hostname or IP address was specified, only one was used. There was an implicit ordering and only the first of the ordering that was specified would have been used; the second and subsequent options would have been ignored. The ordering was: hostname/IP address specified on command line -p -s -ss This has been fixed. If more than one of these options is specified, they are all now applied.

CR:562619

CR Number:   562619 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2161 02 Mar 2009 Fixed Description Incompatible configurations could not have been used for connections. For example, a database created with shadow paging would not have permited a connection using a configuration that specified "at end" processing. This has been corrected. Now, the physical configuration from the database, not the configuration, is used when connecting to the database.

CR:562627

CR Number:   562627 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2197 02 Apr 2009 Fixed 10.0.1 3874 02 Apr 2009 Fixed Description SQL Anywhere supports the "UPDATE( colname )" condition that can be evaluated by trigger code to determine if the value of the specified column has been modified from its current value in the row. The server was failing to evaluate the condition correctly when the column value was modified internally during statement execution. As one example, if the user statement did not modify the column value, but a BEFORE trigger did, then the condition in an AFTER trigger failed to evaluate to TRUE when it should. This has been fixed so that the server will now evaluate the condition correctly, regardless of when the column value is modified,

CR:562656

CR Number:   562656 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.1 2161 02 Mar 2009 Fixed 11.0.0 1583 02 Mar 2009 Fixed 10.0.1 3855 02 Mar 2009 Fixed Description Attempting to fetch data from a proxy table, when connected using a non-DBA user, would have failed if the remote server was one of SAJDBC or ASEJDBC. A permissions problem on the global temporary table used to hold the rows fetched from the remote server has now been fixed in newly created databases. For existing databases, log in with a DBA user and execute the following statement: grant select,insert,update,delete on dbo.omni_rset_fetch_table to PUBLIC

CR:562689

CR Number:   562689 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2162 02 Mar 2009 Fixed Description Using the concatenation operator '+' with VARCHAR and UUID did not produce correct results. This has been fixed.

CR:562826

CR Number:   562826 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.1 2166 05 Mar 2009 Fixed 11.0.0 1585 05 Mar 2009 Fixed 10.0.1 3857 05 Mar 2009 Fixed Description When backing up a database with no transaction log, a client-side transaction-log only backup (i.e. using the Backup utility) would have caused the server to crash. A transaction-log only server side backup (i.e. using the BACKUP statement) did not cause a crash. Although a server side backup did not cause a crash, the SQL error that was issued in this case gave no indication as to what the failure actually was, i.e., it reported "Syntax error near 'backup option'". As well as fixing the crash, a more useful SQL error code/message for the server-side case is now displayed: "Error during backup/restore: No files are part of this backup".

CR:562827

CR Number:   562827 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2162 02 Mar 2009 Fixed Description Using the concatenation operator '+' with VARCHAR and UUID did not produce correct results. This has been fixed.

CR:562829

CR Number:   562829 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3858 09 Mar 2009 Fixed 9.0.2 3803 09 Mar 2009 Fixed Description When querying a proxy table mapped to a remote ASE or Microsoft SQL Server table, if the remote table had a varchar(255) column, then fetching data from that column would have resulted in data truncation. This was due to an off-by-one error, which has now been corrected. Workaround Description  Use varchar(254) or varchar(256) and higher.

CR:562833

CR Number:   562833 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2165 04 Mar 2009 Fixed 11.0.0 1584 04 Mar 2009 Fixed 10.0.1 3856 04 Mar 2009 Fixed Description When the MobiLink Server had a large number of synchronizations running concurrently (in the range of 10000), a MobiLink Monitor connected to it could have become unresponsive, and not displayed new information in a timely manner. This has been fixed.

CR:562838

CR Number:   562838 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3856 03 Mar 2009 Fixed 9.0.2 3801 03 Mar 2009 Fixed Description Applications using the Broadcast Repeater utility were not able to find servers running on Linux machines on a different subnet using broadcasts. The server's broadcast response was being malformed. This has now been corrected.