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

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

CR:470282

CR Number:   470282 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3503 06 Jun 2007 Fixed 10.0.0 2861 06 Jun 2007 Fixed Description An erroneous conversion error could have been raised when executing a query if it referenced a derived table which was empty on the right side of a left outer join, and the derived table contained a GROUP BY clause and had a NUMERIC item in its SELECT list. This has been fixed.

CR:470292

CR Number:   470292 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) 10.0.1 3500 05 Jun 2007 Fixed 10.0.0 2858 05 Jun 2007 Fixed Description Under heavy load the server could have crashed without any assertions in the system log or the console log. This has been fixed. Workaround Description  The recommendation is use -hx switch which will instruct ASA to change the way that server does threading internally. This switch makes ASA use the OS threads for it's multitasking instead of doing co-oparative Multitasking internally.

CR:470296

CR Number:   470296 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 31 May 2007 Fixed Description The ODBC driver could have allocated a large amount of memory when using a shared memory connection. This would have been very rare, and only occurred with large responses. This h has been fixed. Note, this problem could also have occurred with embedded SQL applications, and is now fixed as well.

CR:470313

CR Number:   470313 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 3503 06 Jun 2007 Fixed Description A query may have failed with the message 'Assertion failed: 106104 "Field unexpected during compilation"' when a simple select that should bypass the optimizer was executed. The problem would only have occurred if the select used a unique index and an additional search condition contained a column reference on the right hand side. For example: create table T1 ( pk int primary key, a int, b int ); select * from T1 where pk=1 and a=b; This has been fixed.

CR:470315

CR Number:   470315 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3512 26 Jun 2007 Fixed Description The default name of a primary key constraint is "primary". If a table was created with a constraint name that was not the default, Sybase Central would have crashed silently when navigating to the Data tab. For example, navigating to the Data tab for the following table definition would have caused Sybase Central to crash: CREATE TABLE t1 ( c INTEGER NOT NULL, CONSTRAINT "cn" PRIMARY KEY("c" ASC) This problem has now been fixed.

CR:470335

CR Number:   470335 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3500 01 Jun 2007 Fixed 10.0.0 2859 01 Jun 2007 Fixed Description To determine if a downloaded file has changed, the MobiLink File Transfer utility calculates a hash of its copy of the file and sends it up to the server. The server calculates a hash of its own copy and compares it with the hash of the remote file, and if they don't match, it transmits its entire copy of the file down to the remote. However, if the only change to the file is that extra bytes had been appended to the end, the file was transmitted incorrectly and the resulting file on the remote contained only the new portion -- the original portion of the file was lost. This has been fixed.

CR:470414

CR Number:   470414 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) 10.0.1 3501 01 Jun 2007 Fixed 10.0.0 2859 01 Jun 2007 Fixed Description If a Remote Data Access server was created where the underlying ODBC driver was not a Unicode driver, then using Remote Procedure Calls (RPC) with that remote server would not have worked correctly. This problem has now been fixed.

CR:470546

CR Number:   470546 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) 10.0.1 3502 04 Jun 2007 Fixed Description A query with a procedure call in the FROM clause, that had a column or variable parameter that matched the name of one of the procedure's own result columns, would have failed with the error -890 "statement size or complexity exceeds server limits". This is fixed.

CR:470559

CR Number:   470559 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) 10.0.1 3502 05 Jun 2007 Fixed 10.0.0 2859 05 Jun 2007 Fixed Description The server could have crashed when starting up a database, if the start event of the database contained an HTTP/SOAP call. This has been fixed.

CR:470562

CR Number:   470562 Product Name:   UltraLite Product Component:   UltraLite for eMbedded Visual Basic Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3510 07 Jun 2007 Fixed Description When synchronizing with stream parameters pointing to a MobiLink server on a different machine, carrying out several synchronization operations in a row could have produced errors such as SQLE_COMMUNICATIONS_ERROR or SQLE_SYNC_INFO_INVALID. This would not have occurred if the stream parameters string was empty and the defaults were used. This has been fixed.

CR:470582

CR Number:   470582 Product Name:   UltraLite Product Component:   SQL Preprocessor Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3503 07 Jun 2007 Fixed 10.0.0 2861 07 Jun 2007 Fixed 9.0.2 3510 07 Jun 2007 Fixed Description The error 'Function or Column name reference "Unknown" must also appear in GROUP BY', may have been erroneously raised when an IF expression involved an aggregate function. For example: IF count(n) > 50 THEN 'good' ELSE 'bad' ENDIF This has been corrected.

CR:470594

CR Number:   470594 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3502 05 Jun 2007 Fixed 10.0.0 2861 05 Jun 2007 Fixed Description The MobiLink Listener would likely have failed to send confirmation of notification delivery or confirmation of actions, if persistent connections were explicitly turned off (ie dblsn.exe -pc- ). This problem has been fixed.

CR:470660

CR Number:   470660 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3506 15 Jun 2007 Fixed 9.0.2 3509 15 Jun 2007 Fixed Description Items in the "Edit" menu were not enabled and did not perform consistently: 1. The "Edit/Copy" menu item is now enabled if a results table has focus and at least one row is selected. 2. If the Results panel is selected, the "Edit/Paste" menu item is no longer enabled. 3. If a results table was focused, the "Edit/Delete" menu item could have been clicked, but nothing would have happened. Now, the menu item will cause the row to be deleted, the same as if the DELETE key had been pressed. 4. The "Cut", "Undo", "Redo", "Find/Replace", "Find Next", and "Go To" menu items are now enabled only if the "SQL Statement" field has focus. Previously, they were enabled even if the "Results" panel was selected.

CR:470680

CR Number:   470680 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3506 14 Jun 2007 Fixed 10.0.0 2865 14 Jun 2007 Fixed 9.0.2 3513 14 Jun 2007 Fixed Description When running the Windows Performance Monitor in a Terminal Services session other than session 0, it was not possible to monitor database services running in session 0. On XP, system services and the primary desktop are all in session 0. On Vista, only the system services run in session zero. The behaviour has been changed so that when the Windows Performance Monitor (perfmon) is started (actually, when "add counters" is selected for the first time), perfmon will monitor a database server in the local session if one exists and is providing statistics. If there is no server running in the current session, perfmon will monitor a database server in session 0 if one exists and is providing statistics. If there is no database server providing statistics in the local session or in session 0, perfmon will display statistics for a database server if one is subsequently started in the local session ONLY. To monitor a database server that runs in session 0 (eg, a system service) from a session other than session 0, the database server must be started before perfmon is started.

CR:470685

CR Number:   470685 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3509 05 Jun 2007 Fixed Description When attempting to fetch an unsigned integer from a table on a remote server, the value returned would always have been 0 if the local server was running on a 64-bit little endian machine. This problem has been fixed.

CR:470812

CR Number:   470812 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3501 06 Jun 2007 Fixed 10.0.0 2859 06 Jun 2007 Fixed Description If the QAnywhere Agent was started with a custom policy (ie. transmission rules) where each rule was a scheduled rule, QAnywhere would still have behaved as though the policy was automatic. The messages put in a queue would have been transmitted immediately, and push notifications would have resulted in an immediate message transmission, instead of message transmissions happening on the defined schedule. This has been fixed so that the transmission rules are now all scheduled rules, message transmissions happen only at the scheduled times.

CR:470839

CR Number:   470839 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) 10.0.1 3503 07 Jun 2007 Fixed 10.0.0 2861 07 Jun 2007 Fixed Description When running the Windows CE install in Maintenance mode, the Start Copy Dialog did not contain the list of components to be installed. This has been fixed.

CR:470854

CR Number:   470854 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) 10.0.1 3503 07 Jun 2007 Fixed Description When printing an error report to the console with "dbsupport -pc", binary data is represented in the form of a hex dump. For non-printable characters, the hexadecimal representation was incorrect. This has been fixed.

CR:470999

CR Number:   470999 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3614 17 Dec 2007 Fixed Description It was not possible to build the PHP driver for SQL Anywhere 10 on Unix systems. The config.m4 script that is used as part of the PHP build procedure has now been updated to use version 10 software.

CR:471006

CR Number:   471006 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3503 08 Jun 2007 Fixed 10.0.0 2862 08 Jun 2007 Fixed 9.0.2 3510 08 Jun 2007 Fixed Description EXECUTE permission was not granted to the group SA_DEBUG for the system procedures sa_proc_debug_version and java_debug_version. If a user that was granted membership in SA_DEBUG was not also a DBA, attempting to use the procedure debugger would have failed and possibly caused Sybase Central to crash. This has been corrected for newly initialized databases. For existing databases, the permissions can be granted by executing the following: grant execute on dbo.sa_proc_debug_version to sa_debug go grant execute on dbo.java_debug_version to sa_debug go Workaround Description  Manually (from a DBA login) grant those permissions seem to enable procedure debugging [at least] without any errors.

CR:471007

CR Number:   471007 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) 10.0.1 3503 07 Jun 2007 Fixed 10.0.0 2862 07 Jun 2007 Fixed Description When the MobiLink client (dbmlsync)was run with table locking enabled, this is the default and is the case unless the extended option locktables is set to off, the expected behaviour is for synchronizations to fail unless dbmlsync can obtain locks on the tables being synchronized. A problem that would have allowed synchronizations to continue when dbmlsync failed to obtain the locks, has now been fixed.

CR:471044

CR Number:   471044 Product Name:   MobiLink Product Component:   scripts Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3503 08 Jun 2007 Fixed 10.0.0 2862 08 Jun 2007 Fixed Description When accessing column values in the upload using Java direct row handling, the ResultSet.getObject() method could have returned null instead of an object representing the column value. Methods such as ResultSet.getString(), ResultSet.getInteger() etc. would have worked correctly. This is now fixed.

CR:471045

CR Number:   471045 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3508 20 Jun 2007 Fixed 9.0.2 3551 31 Aug 2007 Fixed Description The memory usage of the MobiLink server with QAnywhere messaging enabled would have increased by a small amount at each client synchronization. The amount of increase was reduced by about 90% by changes made for Engineering case 471798. This increase has now been reduced by a further 5%. While not completely resolved, the memory increase has been significantly reduced, and it continues to be addressed.

CR:471110

CR Number:   471110 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 3504 12 Jun 2007 Fixed 10.0.0 2862 12 Jun 2007 Fixed Description If an event handler attempted to create a temporary table via SELECT ... INTO #temptab, or it attempted to create a view and the SELECT list included a string column with CHAR length semantics, the server would have crashed. This has been fixed.

CR:471148

CR Number:   471148 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) 10.0.1 3504 08 Jun 2007 Fixed 10.0.0 2862 08 Jun 2007 Fixed Description When the server was run on Linux x86 or x86-64 systems, in an X-Window environment where GTK libraries were available, and the command line options -ui or -ux were specified when the GUI console was invoked or when running the Developer Edition regardless of command line options, it may have crashed on shutdown. The integrity of the data in the database was not compromised. This has been fixed.

CR:471149

CR Number:   471149 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) 10.0.1 3504 08 Jun 2007 Fixed 10.0.0 2862 08 Jun 2007 Fixed Description When run on Windows 2000, the MobiLink Server was unable to determine the IP address of the remote client, and thus was unable to ignore a request when the stream option 'ignore' was specified. This has been fixed.

CR:471155

CR Number:   471155 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) 10.0.1 3500 08 Jun 2007 Fixed 10.0.0 2857 08 Jun 2007 Fixed Description The Unload utility could have crashed if the userid specified in the -ac connection parameter was 'dba', but used a non-default password (i.e. not 'sql'), and the userid of the source connection (i.e., -c parameter) was 'dba' as well. This has been fixed. Note, it is recommended that when using -ac that the destination database have default dba credentials. The password can then be changed after dbunload completes.

CR:471293

CR Number:   471293 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) 10.0.1 3505 12 Jun 2007 Fixed 10.0.0 2863 12 Jun 2007 Fixed Description An HTTP request made to a DISH service may have caused a server crash if the DISH service exposed a SOAP service with the following characteristics: - the SOAP service was created with DATATYPE ON or IN, specifying that parameter types are to be mapped from SQL to XMLSchema data types (rather than exclusively to xsi:string), - one or more parameters within the stored procedure called by the SOAP service were (SQL) XML data types. This has been fixed. VARCHAR, LONG VARCHAR, and XML are mapped to XMLSchema type STRING (xsi:string). Most client toolkits including the SQL Anywhere SOAP client will automatically HTML_ENCODE data types that map to xsi:string.

CR:471326

CR Number:   471326 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) 10.0.1 3505 12 Jun 2007 Fixed 10.0.0 2864 12 Jun 2007 Fixed Description The execution time reported in the request-level log for a statement could have been much to high. This would only have happened in the second or subsequent request-level logs that were split using the -on or on command line options. This has been fixed. Workaround Description  None. Appears to be a bug in the profile/analysis tool ?

CR:471339

CR Number:   471339 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) 10.0.1 3505 12 Jun 2007 Fixed 10.0.0 2863 12 Jun 2007 Fixed Description UltraLite clients will now send their version and build number up to the MobiLink server during synchronization. A line similar to the following will appear in the server log: Request from "UL 10.0.0.2862" for: ...

CR:471413

CR Number:   471413 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) 10.0.1 3505 12 Jun 2007 Fixed 10.0.0 2864 12 Jun 2007 Fixed Description If a BACKUP statement was executed that used one of the TRANSACTION LOG backup options, and the database did not use a transaction log file, then the server would have crashed. This has been fixed. The server now returns the error "Syntax error near 'backup option'".

CR:471415

CR Number:   471415 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) 10.0.1 3505 12 Jun 2007 Fixed 10.0.0 2864 12 Jun 2007 Fixed Description If the public option MAX_TEMP_SPACE was inadvertently dropped (ie set public.MAX_TEMP_SPACE=), the server would have crashed the next time it checked the free temp space. This has been fixed.

CR:471431

CR Number:   471431 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) 10.0.1 3505 12 Jun 2007 Fixed Description If an "UPDATE OF column-list" trigger was defined, the trigger could have been fired in some cases where no column in the associated list had in fact been modified. BEFORE UPDATE triggers should fire if a column in the column-list appears in the SET clause of the associated UPDATE statement, while AFTER UPDATE triggers should fire if the value of a column in the column-list has been modified by the UPDATE statement. A positioned update would have caused all BEFORE UPDATE and AFTER UPDATE triggers to fire regardless of whether a column in their column-list appeared in the SET clause or was modified by the update. Further, if a searched update included all columns in the SET clause, but did not modify the value of any column, AFTER UPDATE triggers would have been fired inappropriately. This has been fixed.

CR:471575

CR Number:   471575 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3506 13 Jun 2007 Fixed 10.0.0 2864 13 Jun 2007 Fixed 9.0.2 3513 13 Jun 2007 Fixed Description If an application used the iAnywhere JDBC Driver to connect to a DB2 server, and attempted to use PreparedStatement.setBoolean(), the JDBC driver would have thrown an exception. Calling PreparedStatement.setBoolean() resulted in the driver binding a parameter of type SQL_BIT, even though DB2 does not support SQL_BIT. This has been fixed so that a parameter of type SQL_TINYINT is now used for DB2.

CR:471582

CR Number:   471582 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) 10.0.1 3505 13 Jun 2007 Fixed 10.0.0 2863 13 Jun 2007 Fixed Description The MobiLink clients will now include its version and build number with each synchronization, and the MobiLink server will display this information in its log. As a result, the MobiLink log will now contain lines like the following: Request from "Dbmlsync Version 11.0.0.1036 Debug Internal Beta" for: remote ID: e08b39d1-e3fa-4157-969b-8d8679324c00, user name: template_U1, version: template_test instead of lines like this: Request from "MLSync" for: remote ID: 45ef79ab-195e-4f76-805b-95eef2773e8f, user name: template_U1, version: template_test

CR:471584

CR Number:   471584 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3507 15 Jun 2007 Fixed 10.0.0 2865 15 Jun 2007 Fixed Description Erroneous results could have been obtained for a query containing a left out join, where FOR READ ONLY was not specified, and where a temporary table was required (for example, to order the results of the join). This has now been corrected.

CR:471644

CR Number:   471644 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) 10.0.1 3509 22 Jun 2007 Fixed Description In some situations, if a statement contained a subselect in the SELECT list of a query block that was aliased, and the alias was referred to in the WHERE clause of the query, then the statement would have failed with the following error: *** ERROR *** Assertion failed: 106104 (...) Field unexpected during compilation (SQLCODE: -300; SQLSTATE: 40000) This has been fixed.

CR:471688

CR Number:   471688 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Jun 2007 Fixed Description Viewing a result set generated by SELECT or CALL statements would have caused the server to place schema locks on the table(s) associated with the result. Theses locks could have subsequently prevented modifying those tables in other applications, such as Sybase Central. This has been changed so that the Interactive SQL utility now releases database locks once the result set has been completely read (and cached), as long as there are no uncomitted changes in the current transaction.

CR:471692

CR Number:   471692 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3513 14 Jun 2007 Fixed Description Multi-byte characters in push notifications may have been lost. This problem has been fixed. Note, multi-byte characters are supported in UDP notifications, but SMS notifications are restricted to 7-bit ascii.

CR:471696

CR Number:   471696 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 3506 14 Jun 2007 Fixed 10.0.0 2865 14 Jun 2007 Fixed 9.0.2 3513 14 Jun 2007 Fixed Description The 32-bit and 64-bit versions of the SQL Anywhere library that provides support for the Windows Performance Monitor could not coexist. If the 64-bit library was registered last, only the 64-bit version of the Performance Monitor would have been able to monitor SQL Anywhere servers (both 32-bit and 64-bit servers). If the 32-bit version was registered last, only the 32-bit version of the Performance Monitor would have been able to monitor SQL Anywhere servers (both 32-bit and 64-bit servers). The area of the registry that contains performance monitoring information and, in particular the path to the support library, is shared by both 32-bit and 64-bit applications, unlike other areas of the registry which have been split into 32-bit and 64-bit versions. The problem has been fixed by having the 32-bit and 64-bit support libraries register using different service names.

CR:471710

CR Number:   471710 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) 10.0.1 3507 15 Jun 2007 Fixed Description When submitting an error report with dbsupport, minidumps larger than 1Mb in size would silently have been omitted from the submission. Only the crash log would have been included. Also, when printing an error report with dbsupport, minidumps larger than 1Mb in size would not have been printed. These issues would typically only have occurred on Unix systems, since Windows minidumps are much smaller. This has been fixed.

CR:471765

CR Number:   471765 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 3508 19 Jun 2007 Fixed Description If a table had a column of type uniqueidentifier, varbit, long varbit, xml, nchar, nvarchar or long nvarchar, the column would not have been in the result set of the system procedure sp_columns. This has been fixed. To get this fix into an existing database, the database needs to be rebuild.

CR:471798

CR Number:   471798 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) 10.0.1 3507 15 Jun 2007 Fixed 10.0.0 2865 15 Jun 2007 Fixed Description The MobiLink server could have leaked 2K bytes of memory per synchronization if compressed streams were being used (ie. the "compression" client option was not "none"). The leak depended directly on how the first uploaded bytes of the synchronization flow on the network between the client and server, so the leak was somewhat random from client's point of view. The synchronization was not affected by the leak. This has now been fixed.

CR:471802

CR Number:   471802 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) 10.0.1 3507 15 Jun 2007 Fixed Description The dbsupport utility can be used to submit, via the Internet, diagnostic information and crash reports, or to submit feature statistics. When dbsupport prompted the user to submit a particular crash report, and the user declined, it still attempted to submit feature statistics, which is not desired. When dbsupport was configured with "dbsupport -cc no", the intended behavior is to not prompt for permission to submit reports, and to not submit reports. Although the crash reports were not being submitted, dbsupport still attempted to submit feature statistics, which is also not desired. These issues have been fixed.

CR:471825

CR Number:   471825 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3508 19 Jun 2007 Fixed Description When unloading UltraLite database to SQL, the UltraLite Unload utility would have missed any tables where IsNeverSynchronized() would have returned true. This has been corrected

CR:471931

CR Number:   471931 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) 10.0.1 3553 15 Oct 2007 Fixed Description The MobiLink server could have crashed when calling a stored procedure which generated error messages that were longer than 256 characters. This has been fixed.

CR:471948

CR Number:   471948 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) 10.0.1 3560 19 Jun 2007 Fixed 9.0.2 3515 19 Jun 2007 Fixed Description If an HTTPS connection attempt failed because of licensing (i.e. too many connections), the client would have received a plain-text error message, instead of handshake data. HTTPS clients would have interpreted this as a protocol error. This has been fixed.

CR:471958

CR Number:   471958 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3509 21 Jun 2007 Fixed 10.0.0 2868 21 Jun 2007 Fixed Description If the primary key of a table being synchronized, was not defined as the initial column or columns of the table, it was possible for the MobiLink Server to crash while processing the download_delete_cursor for that table. It was more likely for the MobiLink Server to crash if the options -b or -vr were specified on the MobiLink server command line. The problem has now been fixed.

CR:471967

CR Number:   471967 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) 10.0.0 3508 19 Jun 2007 Fixed Description The MobiLink server may have crashed when executing a user script which contained named parameters, and a parameter failed to bind. Unfortunately, this bind failure was also not being recorded to the log. The bind failure recording and crash have been fixed.

CR:471981

CR Number:   471981 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 3508 19 Jun 2007 Fixed 9.0.2 3515 19 Jun 2007 Fixed Description Attempting to create proxy tables to an Oracle server in an SA database with a mult-byte character set, would likely have failed with a "table not found" error if the table owner and name were not specified in uppercase in the create existing table location string. This problem has now been fixed.

CR:472034

CR Number:   472034 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 3512 19 Jun 2007 Fixed 10.0.0 2870 19 Jun 2007 Fixed Description Validating a table with full check, would have caused the server to crash if the column order of a foreign key did not match the column order of the referenced primary key. This has been fixed.

CR:472071

CR Number:   472071 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3510 22 Jun 2007 Fixed Description If a query contained a recursive union that appeared on the right side of a nested loops join and the recursive union selected a hash execution strategy, then the statement could have failed with the following error: Run time SQL error -- *** ERROR *** Assertion failed: 106105 (...) Unexpected expression type dfe_PlaceHolder while compiling [-300] ['40000'] For example, the following statement could cause this error. with recursive Ancestor( child) as ( (select row_num from rowgenerator R1 where R1.row_num = 1 ) union all (select R2.row_num+100 from Ancestor, rowgenerator R2 where Ancestor.child = R2.row_num ) ) SELECT * FROM sys.dummy D1, Ancestor for read only In the case of this error, the server would continue to process other statements (a non-fatal assertion failure). This has been fixed. Workaround Description  The error does not occur at all on MSSQL server. This should not be the workaround.

CR:472073

CR Number:   472073 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 3508 19 Jun 2007 Fixed Description Delete statements that do not bypass optimization, and load CHECK constraints, would have failed if there was a syntax error in CHECK constraint definition. This has been fixed.

CR:472078

CR Number:   472078 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) 10.0.1 3508 19 Jun 2007 Fixed Description The server could have crashed if a MESSAGE statement contained certain types of substr or byte_substr expressions. These expressions must have used a negative start value that specified a starting point before the beginning of the string for a crash to have occurred. For example: "message byte_substr( 'a', -5, 1 )". This has been fixed.

CR:472081

CR Number:   472081 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3532 19 Jun 2007 Fixed Description If a connection string contained LINKS=TCPIP(host=<hostname>;...), where <hostname> was an invalid host name, the client library may not have given an error as expected. This would only have occurred with threaded clients on Linux. This has been fixed.

CR:472222

CR Number:   472222 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3512 26 Jul 2007 Fixed Description If the UltraLite language DLLs were removed from the installation, the UltraLite ODBC driver may have caused Sybase Central and dbisql to crash. The ODBC driver now explicitly checks for missing resources and reports an error if no resources are found.

CR:472228

CR Number:   472228 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3509 20 Jun 2007 Fixed 10.0.0 2867 20 Jun 2007 Fixed Description The Mobilink Redirector now support "IIS6 in IIS5 isolation mode". IIS5 allows processing of multiple persistent HTTP request responses within a single entry into the web server extension. However IIS6 in IIS5 isolation mode disallows that possibly due to the stricter HTTP system driver. To work around this, the redirector will exit the extension after a single request-response cycle, while persisting the backend connection for later use. This change should increase concurrency, especially when the backend servers are the bottleneck. To turn on IIS5 isolation mode on a IIS6 server using the IIS Manager, right click on IIS Manager->Web Sites and select Properties. Bring up the Service page and select the "IIS 5.0 isolation mode".

CR:472237

CR Number:   472237 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) 10.0.1 3508 21 Jun 2007 Fixed Description The MobiLink server is now supported on Windows x64. The supported consolidated databases are SQL Anywhere and Oracle (see Engineering case 472238 for details). An x64 JRE install is required, which is available at: http://downloads.sybase.com/swd/detail.do?baseprod=144&client=ianywhere&relid=10260 To install this JRE: Download and run SA_1001_JRE_UPD.exe. The install will locate an existing SQL Anywhere 10 installation, and install a Java Runtime Environment for x64. To install the x64 MobiLink server: 1) Install the EBF normally on a x64 computer, and then go to Add/Remove Programs (Programs and Features in Vista), select SQL Anywhere 10 and click on the Change button. Check that Modify is selected and click on the Next button. 2) The Select Features dialog will appear and it will show the MobiLink for x64 features under "MobiLink". 32 bit MobiLink features will be displayed under "MobiLink (32 bit)". Check the checkboxes for MobiLink to install MobiLink for x64 and click on the Next button. 3) Click the Next button on the next dialog to implement the modifications. 4) Click the Finish button on the last dialog to complete the installation.

CR:472238

CR Number:   472238 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) 10.0.1 3504 21 Jun 2007 Fixed Description The "iAnywhere Solutions 10 - Oracle" ODBC driver is now supported on Windows x64 systems.

CR:472239

CR Number:   472239 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 3508 21 Jun 2007 Fixed Description Branded, third-party ODBC drivers are no longer shipped with MobiLink. Version 10.0.0 and up already do not ship with branded, third-party ODBC drivers. The drivers that are no longer shipping are: iAnywhere Solutions 9 - DB2 Wire Protocol iAnywhere Solutions 9 - Oracle Wire Protocol iAnywhere Solutions 9 - Sybase ASE These drivers are now deprecated, although they will continue to be tested to make sure MobiLink and other components still work with them. If a problem is encountered with one of these drivers that cannot be worked around, a fix cannot be made, the options are to directly use a recommended third-party ODBC driver (see http://www.sybase.com/detail?id=1011880), or to move to version 10.0.1 or higher. The aforementioned link will be updated, recommending: - An IBM ODBC driver for DB2 - Our own (iAnywhere Solutions 9 - Oracle) ODBC driver for Oracle (now shipping with 9.0.2 as of this change) - A DataDirect ODBC driver for ASE

CR:472245

CR Number:   472245 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3509 21 Jun 2007 Fixed 10.0.0 2867 21 Jun 2007 Fixed Description A call to SQLCancel() by an ODBC application may have failed, if the attempt was to cancel a multi-row insert. The results may have varied, but it the application could have appeared to be hung. The ODBC driver attempts to execute multi-row inserts as a single operation. If the operation failed, it attempted to insert rows one at a time. In the case where the multi-row insert failed due to the operation being cancelled, the driver was left in a bad state. Now, the driver does not bother trying again if the original statement failed because it was cancelled.

CR:472262

CR Number:   472262 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   5.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3513 27 Jun 2007 Fixed Description The "Start In" property of the Sybase Central shortcut (Start menu item) was incorrectly set. This could have resulted in Sybase Central failing to start. This has been fixed.

CR:472364

CR Number:   472364 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) 10.0.1 3511 26 Jun 2007 Fixed Description UltraLite allows a publication to be created with a predicate for each of its tables. This allows users to filter rows in a table being synchronized. If the predicate contained a subquery, it was possible that the predicate evaluated to the wrong result, either allowing all rows to be uploaded, or none to be uploaded. This has been fixed. Also, note that there are two errors in the documentation. Under UltraLite Database Management and Reference/Working with UltraLite Databases/Working with UltraLite publications/Publishing a subset of rows from an UltraLite table, the following are incorrect: "Palm OS: You cannot use a CREATE PUBLICATION statement with a WHERE clause on this platform." In fact, a WHERE clause can be used on Palm OS. The paragraph "What you cannot use in a WHERE clause" In fact, you can use columns from tables not in the article (or even not in the publication). You can also use subqueries.

CR:472369

CR Number:   472369 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3517 22 Jun 2007 Fixed Description When running the Linux x86 (32-bit) server, the value of the NativeProcessorArchitecture property would always have been "X86," even if the engine was running on a system with an x86-64 CPU. This has been fixed.

CR:472386

CR Number:   472386 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) 10.0.1 3509 22 Jun 2007 Fixed Description If a database containing global autoincrement columns was rebuilt, and the setting of the global_database_id option was 0, the next available value for these columns stored in SYS.SYSTABCOL.max_identity was not set. This has been fixed. As a workaround, execute the following after rebuilding the database: set option public.global_database_id=1; set option public.global_database_id=0;

CR:472390

CR Number:   472390 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 3509 22 Jun 2007 Fixed Description If a statement other than a SELECT statement converted a value of type NUMERIC or DECIMAL to a string, then the conversion could have been incorrect. There could have been insufficient trailing 0 characters for the declared scale of the value. This has been fixed. For example, the following batch would have returned 12.34 and 12.34000, now the two values should both be 12.34000: begin declare @num numeric(10,5); declare @str char(20); set @num = 12.34; set @str = @num; select @str, cast( @num as char(20) ); end Further, the data type of division in the NUMERIC/DECIMAL domain could have been incorrect for a non-SELECT statement. This has been fixed as well.

CR:472400

CR Number:   472400 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3510 22 Jun 2007 Fixed 9.0.2 3527 12 Jul 2007 Fixed Description In some cases, if a query contained an unflattened derived table on the null-supplying side of an outer join and the derived table contained a constant, then the statement could have failed with an assertion failure message: Run time SQL error -- *** ERROR *** Assertion failed: 106105 (...) Unexpected expression type dfe_PlaceHolder while compiling (SQLCODE: -300; SQLSTATE: 40000) For example, the following query demonstrates this problem: SELECT * FROM SYS.dummy D1 LEFT JOIN ( select c1 from ( select distinct D2.dummy_col, 31337 c1 from dbo.rowgenerator R1 , sys.dummy D2 ) DT1 ) DT2 ON (D1.dummy_col=DT2.c1-31337) This has now been fixed.

CR:472478

CR Number:   472478 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) 10.0.1 3508 22 Jun 2007 Fixed Description The iAnywhere JDBC driver has now been enhanced to support the DB2 Mainframe ODBC driver. The iAnywhere JDBC driver now checks the DBMS name of the DB2 driver, if it is the DB2 Mainframe driver it will set the appropriate default result set type and other attributes.

CR:472479

CR Number:   472479 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) 10.0.1 3510 22 Jun 2007 Fixed Description If a cursor contained a LONG VARCHAR or LONG NVARCHAR column, and it was retrieved using a GET DATA request, then the request could fail with the error: -638 "Right truncation of string data" In some cases, this situation could have caused the server to crash. This has now been fixed.

CR:472482

CR Number:   472482 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) 10.0.1 3510 22 Jun 2007 Fixed Description If a cursor was opened with a query that referenced proxy tables, and attempted to refetch a row, then the server would have failed assertion 101701. This problem has now been fixed and the server now correctly gives an error indicating that cursors involving remote tables are not scrollable.

CR:472484

CR Number:   472484 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) 10.0.1 3509 22 Jun 2007 Fixed Description If an application made a request that executed a JAVA call, and then attempted to shut down the database while the JAVA call was still active, then the server would either have hung or crashed. This problem has now been fixed.

CR:472486

CR Number:   472486 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3597 07 Nov 2007 Fixed 9.0.2 3582 07 Nov 2007 Fixed Description On Linux IA64 systems, the server may cause "floating-point assist" faults. These warnings are as result of operations on denormal (quantities too small to be represented in normalized form) floats and doubles in the server, and can be considered harmless, especially if the number of warnings is low. The Itanium CPU is incapable of operating on denormal numbers in hardware and enters software emulation mode when such an operation is requested. The Linux kernel detects this and displays a performance warning, as the software emulation entails a performance penalty. The correctness of server operations is not compromised. All the same, the server has been modified to minimize internal use of denormal numbers. However, the warnings will still appear if the server is explicitly requested to operate on denormals (for instance, with the statement "SELECT 2.25e-309").

CR:472489

CR Number:   472489 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) 10.0.1 3509 22 Jun 2007 Fixed Description The .NET 2.0 framework introduced a new namespace 'System.Transactions', which contains classes for writing transactional applications. Client applications can create and participate in distrubuted transactions with one or multiple participants. These applications can implicitly create transactions using TransactionScope class. The connection object can detect the existence of an ambient transaction created by the TransactionScope and automatically enlist. The applications can also create a CommittableTransaction, and call the EnlistTransaction method to enlist. Distributed transaction has significant performance overhead. It is recommand to use database transactions for non-distributed transactions.

CR:472503

CR Number:   472503 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) 10.0.1 3510 26 Jun 2007 Fixed Description Deploying a synchronization model created with an exisiting UltraLite database could have caused an error. This problem has been fixed.

CR:472505

CR Number:   472505 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) 10.0.1 3511 26 Jun 2007 Fixed Description While performing a backup, the server could have crashed in a high availability environment if one or more of the transaction logs was deleted. It was possible to truncate a transaction log when the database file was mirrored, but this is no longer the case. An error is now returned when attempting to truncate a transaction log while it's involved in mirroring.

CR:472507

CR Number:   472507 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) 10.0.1 3511 26 Jun 2007 Fixed 10.0.0 2873 16 Jul 2007 Fixed Description If a statement contained a hash join with a complex ON condition containing non-equality predicates that should not be executed in parallel, then it was possible for the join to be incorrectly costed by the optimizer as if it were executed in parallel. This could have lead to sub-optimal execution strategies, a server crash or a wrong answer. This has now been fixed. For example, the following statement could exhibit this problem: select * from sysdomain D1 left join sysdomain D2 on D1.type_id = D2.type_id and 0 = ( select D1.type_id - D2.type_id from sys.dummy )

CR:472508

CR Number:   472508 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) 10.0.1 3511 26 Jun 2007 Fixed Description If a query contained an outer join that had a derived table on the null-supplying side, and the derived table contained a complex expression and the join condition contained a non-equality predicate that referenced this complex expression that was further used after the join, then the statement could have failed with a non-fatal assertion failure error: Assertion failed: 102501 (...) Work table: NULL value inserted into not-NULL column For example, the following statement could cause this problem: with D(c1,c2) as ( select row_num-1, 0 from dbo.rowgenerator R1 where R1.row_num <= 101 union all select 123456789, 0 from sys.dummy where 1=0 ) select D1.c1, D1.c2 * 23 x, D2.c1 from D D1 left join D D2 on D1.c1 = D2.c1 and D2.c1 = 3 and x - D2.c2 = 0 This has been fixed.

CR:472510

CR Number:   472510 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) 10.0.1 3510 26 Jun 2007 Fixed Description A server started with several databases could have crashed on shutdown if more than one alternate server name was used. This has been fixed.

CR:472613

CR Number:   472613 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) 10.0.1 3515 29 Jun 2007 Fixed Description If a highly uncompressible string (i.e. one such that compression increases the size of the data or reduces the size by less than about 14 bytes) was inserted into a compressed column, fetching that value from the column would have resulted in decompression errors. This was the result of an assumption that the stored length of the column was less than or equal to the actual length of the string. This has been fixed.

CR:472617

CR Number:   472617 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3519 26 Jun 2007 Fixed Description The Interactive SQL window could have stopped repainting when executing a long-running query. This has been fixed.

CR:472619

CR Number:   472619 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) 10.0.1 3511 26 Jun 2007 Fixed Description The Unload utility would have reported a syntax error if the tsql_variables option was set to 'on'. This option controls how variable references starting with @ are handled. The unload script now temporarily sets the option to the default value (off).

CR:472620

CR Number:   472620 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) 10.0.1 3511 26 Jun 2007 Fixed 10.0.0 2869 26 Jun 2007 Fixed Description Mini core files generated on Linux as a results of a crash are too big. The server was including executable segments in the core files. This has been fixed by discarding executable segments, and any data segments that exceed 2MB in size.

CR:472623

CR Number:   472623 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3512 26 Jun 2007 Fixed Description If a query was executed that used a merge join, and the null-supplying input of the merge join was a derived table that contained an unquantified expression in its select list and the join condition contained a non-equality predicate referencing this unquantified expression, the statement would have fail with the following message: Assertion failed: 106105 (...) - Unexpected expression type dfe_FieldOrigRid while compiling For example, the following query could have generated this problem: SELECT T1.col1 FROM ( select NULL col1, row_num col2, (select dummy_col from sys.dummy ) col3 from dbo.rowgenerator ) T1 FULL JOIN ( select dummy_col c1, dummy_col+1 c2 from sys.dummy D1 ) T2 ON (T1.col2=T2.c1) AND (T1.col3=T2.c2) This has been fixed.

CR:472632

CR Number:   472632 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Linux Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3513 27 Jun 2007 Fixed 9.0.2 3519 27 Jun 2007 Fixed Description Messages with a NULL originator in the server message store, would have caused message processing to halt. This has been fixed as follows: the QAnywhere Agent has been changed so that messages with a NULL originator will not be uploaded until the store ID is set on the client. The QAnywhere connector has been changed so that if a message with NULL originator somehow gets into the server message store, the message will be marked as unreceivable and skipped, not halting further message processing.

CR:472645

CR Number:   472645 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) 10.0.1 3511 26 Jun 2007 Fixed Description If a transaction log file on the primary server in a database mirroring environment was grown using ALTER DBSPACE TRANSLOG ADD, the statement would have been sent to the mirror server, but would have been ignored. This has been fixed. The log on the mirror will now be correctly grown when the mirror server receives this statement from the primary server.

CR:472648

CR Number:   472648 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3557 10 Sep 2007 Fixed Description The MobiLink server could have entered into an infinity loop and generated a very large output file, or have even crashed, if the execution of an upload_fetch, download_cursor, or download_delete_cursor script caused an error, or if the number of columns in the result set generated by any of these cursors did not match the number of columns defined in the corresponding remote table, and the handle_error or handle_odbc_error script returned 1000 when these errors occurred. This problem has been fixed. The MobiLink server will now abort the synchronization if any of these unrecoverable errors occur during synchronization. The errors in the user-defined scripts must be fixed.

CR:472768

CR Number:   472768 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) 10.0.1 3512 26 Jun 2007 Fixed Description The Unload utility was generating the reload.sql script using newline (linefeed) characters to separate lines on Windows, rather than the generally accepted carriage return/linefeed characters. This has been fixed. On other platforms, the script will continue to use newline characters as line separators.

CR:472772

CR Number:   472772 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3542 08 Aug 2007 Fixed 10.0.0 2878 08 Aug 2007 Fixed Description Mini-core dumps generated by the server on Linux systems may not have loaded properly in the debugger, or would not have shown any stack traces. In order to limit the size of the mini-core files on Linux, the size of a single data segment in the dump was limited, to 2MB. On some Linux systems this was not sufficient so it has been increased to 5MB.

CR:472773

CR Number:   472773 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3521 06 Jul 2007 Fixed Description If an event has a query that references a proxy table, and the remote data access class was either SAJDBC or ASEJDBC, then the server would have crashed once the event completed. This problem has now been fixed. NOTE that there is no problem if the remote data access class is ODBC based.

CR:472777

CR Number:   472777 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3512 26 Jun 2007 Fixed Description When the Certificate Creation utility (createcert) prompted for an encryption type, RSA vs ECC, it accepted lowercase 'r' or 'e', but not uppercase 'R' or 'E'. This has been corrected.

CR:472778

CR Number:   472778 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) 10.0.1 3535 30 Jul 2007 Fixed Description Secure-streams startup errors, for example when a bogus certificate identity password was used, would not have prevented the server from starting. The error would only have been detected on the first synchronization. This may have resulted in a server crash, depending on the error. This has been fixed.

CR:472829

CR Number:   472829 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3512 28 Jun 2007 Fixed Description If an application executes a Java stored procedure, and then the server crashed (for an unrelated reasons) while the Java method was still executing, there was a chance the JVM will not have shut down cleanly. This problem has now been fixed.

CR:472920

CR Number:   472920 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3510 27 Jun 2007 Fixed Description A mobile webservices client application could have failed with a NullReferenceException when processing a SOAP response that contained elements described as <any> in the WSDL description. This has been fixed. Note: this problem occurs when processing <row> elements contained within <SimpleDataset> elements in result sets returned by SQL Anywhere SOAP services.

CR:472922

CR Number:   472922 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) 10.0.1 3515 28 Jun 2007 Fixed Description In certain circumstances, a complex statement (large number of query elements) could have caused the server to crash. This has been fixed.

CR:472928

CR Number:   472928 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) 10.0.1 3508 27 Jun 2007 Fixed Description AS of 10.0.1 build 3341, it was possible to use the Data Source utility (dbdsn) to create DSNs for the iAnywhere Oracle driver DSNs". Although it was possible to install the iAnywhere Oracle driver and not have dbdsn installed. If for example, MobiLink was installed without SQL Anywhere, the iAnywhere Oracle driver would have been install without dbdsn. This has been fixed.

CR:472948

CR Number:   472948 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 13 Aug 2007 Fixed Description There were two problems related to foreign keys to unique constraints (in this description, unique constraint is assumed to be a unique constraint other than the primary key). For each problem, assume there is one table (P) with a unique constraint and another table (F) with a foreign key referencing that unique constraint. The first problem was that updating a row in P that was referenced by F would not have generated the necessary foreign key violation error. This would have lead to rows in F with no corresponding row in P. Note that this wasnt a problem when referencing primary keys because primary keys should not be updated in UltraLite. The second problem occurred when the foreign key from F to P was declared as CHECK ON COMMIT. When a row was deleted from P, temporarily violating RI, but a new row was added before the transaction was committed that kept RI in tact, an error would still have been raised. Since the foreign key was declared as CHECK ON COMMIT, the error should not have occurred. Both of these problems have been fixed.

CR:472972

CR Number:   472972 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) 10.0.1 3515 29 Jun 2007 Fixed Description Calling the system procedure sa_describe_query() could have caused the server to crash. This has now been fixed.

CR:473062

CR Number:   473062 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 3515 28 Jun 2007 Fixed 10.0.0 2871 28 Jun 2007 Fixed Description The server would have crashed if an invalid reference was made to a function: name..function() (note the two dots). This has been fixed.

CR:473187

CR Number:   473187 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 3516 29 Jun 2007 Fixed Description The "Server name <name> already in use" message could have contained incorrect characters instead of the name. In rare cases, this could have caused the server to crash on startup if the server name was in use. This has now been fixed.

CR:473203

CR Number:   473203 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3521 06 Jul 2007 Fixed Description When using the iAnywhere Solutions 10 - Oracle ODBC driver to fetch data by calling SQLGetData(), the data could have been truncated, if the column was not a BLOB column, and the buffer size passed into SQLGetData was less than the actual data length. This problem is now fixed.