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

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

CR:547206

CR Number:   547206 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3786 21 Oct 2008 Fixed Description Non-persistent HTTPS synchronizations could sometimes fail with stream error STREAM_ERROR_WRITE and a system error code of 10053. This has been fixed.

CR:547213

CR Number:   547213 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2116 18 Nov 2008 Fixed 11.0.0 1537 18 Nov 2008 Fixed 10.0.1 3800 18 Nov 2008 Fixed Description The server could have looped forever executing a REORGANIZE TABLE statement. This should only have occurred if the table had a clustered index that contained non-unique values in the clustered column or columns. This has been fixed.

CR:547224

CR Number:   547224 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3785 20 Oct 2008 Fixed Description When selecting data using the Interactive SQL utility, from an UltraLite database that was UTF8 encoded, it was possible for extra garbage characters to have be displayed at the end of the string.For example, if a VARCHAR column contained the string 'fr' (the middle letter is u umlaut) and the database was UTF8 encoded, selecting that column would have displayed a garbage character at the end (typically a box).Note that this was a display problem only. This has been fixed.A possible work around is to cast the data as VARCHAR(x), where x is a value big enough to display the data.

CR:547228

CR Number:   547228 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1520 21 Oct 2008 Fixed 10.0.1 3786 21 Oct 2008 Fixed 11.0.1 1991 01 Dec 2008 Fixed Description n very rare circumstances, the server could have failed a fatal assertion when commiting deleted rows containing short strings (less than a database page in length). The typical assertion seen in this instance was assertion 201501 - "Page for requested record not a table page or record not present on page". This has been fixed.

CR:547234

CR Number:   547234 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.0 1520 21 Oct 2008 Fixed 10.0.1 3785 21 Oct 2008 Fixed 11.0.1 1988 01 Dec 2008 Fixed Description When the UltraLite SQL functions length() and char_length() were used on LONG VARCHAR columns, the results were incorrectly the lengths of the strings in bytes, rather than characters. Note that some characters require multiple bytes internally. The function byte_length() is used to determine the length in bytes of the string. This has been fixed.

CR:547248

CR Number:   547248 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1519 20 Oct 2008 Fixed 10.0.1 3785 20 Oct 2008 Fixed 11.0.1 1988 02 Dec 2008 Fixed Description If the server had shut down due to a start-up error involving a database that participated in mirroring, the shutdown reason would not have been recorded correctly. On Unix systems, it would have been recorded as being a result of a SIGHUP signal. On Windows systems, it would have been recorded as being a result of a request from the console. This has been fixed so that it is now correctly recorded as being a result of a start-up error.

CR:547254

CR Number:   547254 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1519 20 Oct 2008 Fixed 11.0.1 1988 02 Dec 2008 Fixed Description The Interactive SQL utility (dbisql) could have reported an internal error if the "Run Script" menu item was used to execute a script file that caused dbisql to close. This has been fixed.

CR:547385

CR Number:   547385 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1518 21 Oct 2008 Fixed 11.0.1 1987 02 Dec 2008 Fixed Description In rare circumstances, Sybase Central could have crashed when selecting a task in the tasks list. This has been fixed.

CR:547392

CR Number:   547392 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 03 Nov 2008 Fixed 10.0.1 3794 03 Nov 2008 Fixed 11.0.1 2005 02 Dec 2008 Fixed Description Database corruption was possible if a database crashed while a lazy checkpoint was in progress. For corruption to occur, pages must have been allocated during the lazy checkpoint and one of the following must have occurred prior to the checkpoint: - dropping a table or index - truncating a table (that could have been truncated quickly, eg. no triggers) - deleting or replacing long blobs (greater than roughly page size) - [in general] an operation that resulted in pages being freed without the contents being modified This was more likely to have been an issue on heavily loaded servers. This problem has been fixed by temporarily allocating the pages at the start of the lazy checkpoint and then re-freeing them at the end.

CR:547415

CR Number:   547415 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1521 23 Oct 2008 Fixed 11.0.1 1992 02 Dec 2008 Fixed Description If all terms in a CONTAINS query were dropped, due to STOPLIST, MINIMUM and MAXIMUM TERM LENGTH settings of the text index, unnecessary searches in the text index could still have been performed. This has been fixed.

CR:547496

CR Number:   547496 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2032 27 Nov 2008 Fixed 11.0.0 1541 27 Nov 2008 Fixed 10.0.1 3808 27 Nov 2008 Fixed 9.0.2 3760 27 Nov 2008 Fixed Description A long-running HTTP connection to an OEM server would have resulted in an authentication violation. This was corrected by making all HTTP connections authenticated by default.

CR:547498

CR Number:   547498 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2127 24 Nov 2008 Fixed 10.0.1 3796 12 Dec 2008 Fixed Description Outer references are expressions used in a nested query block which reference table columns from the outside of that query block. For example, in the query below, 'T.Z+1' is an expression used in a subquery referencing the base table column T.Z of the base table T which is in the FROM clause of the main query block. Such expressions are now sometimes considered constants inside the nested query block. These constants are used in many optimizations by the SA optimizer, such as order optimization, functional dependencies optimization, and MIN/MAX optimization. Previously, these outer references are always treated as non-constants. Q: select * from T where T.X <> (select max(R.Y) from R where R.Z = T.Z+1)

CR:547504

CR Number:   547504 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3746 29 Oct 2008 Fixed Description A multithreading application using the ADO .Net provider, could have hung due to incorrect thread synchronization. This has been corrected.

CR:547506

CR Number:   547506 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2030 26 Nov 2008 Fixed 11.0.0 1541 26 Nov 2008 Fixed 10.0.1 3807 26 Nov 2008 Fixed Description The server could have become unresponsive when executing a query, if during an index scan very few rows satisfied the WHERE conditions. This has been fixed.

CR:547513

CR Number:   547513 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1520 22 Oct 2008 Fixed 10.0.1 3786 22 Oct 2008 Fixed 9.0.2 3741 22 Oct 2008 Fixed 11.0.1 1992 02 Dec 2008 Fixed Description When running the server on Unix systems and using the -m command line option ("truncate transaction log after checkpoint"), the transaction log was not being truncated on checkpoints. This has been fixed.

CR:547514

CR Number:   547514 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) 21 Oct 2008 Fixed Description The QAnywhere plugin could have crashed Sybase Central when connected to a message store which contained thousands of messages. This has been fixed. Now, only the first 1000 messages are displayed. If there are more messages in the store, a message window will display a message that these are the latest 1000 messages.

CR:547522

CR Number:   547522 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1520 22 Oct 2008 Fixed 11.0.1 1992 02 Dec 2008 Fixed Description If the MobiLink system setup in the consolidated database was corrupt, then using the Check MobiLink System Setup command in the MobiLink plug-in could have caused a Java null pointer exception. This would only have happened if a MobiLink system setup stored procedure incorrectly had no parameters. This bug has been fixed. A workaround is to manually remove the MobiLink system setup and then re-run the command.

CR:547541

CR Number:   547541 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1524 22 Oct 2008 Fixed 11.0.1 1998 02 Dec 2008 Fixed Description Using a server that is in In-memory mode to start a database requiring recovery would have caused the server to fail assertion 201842, "Checkpoint log: failed to write info page". The server running in In-memory mode was unable to use the transaction and/or checkpoint logs for recovery. This has been changed so that the server running in In-memory Never-write mode (-im nw) will now read both logs during recovery only. When in In-memory Checkpoint-only mode (-im c), the server will read the transaction log during recovery only. This is useful for example, to validate a backup copy of a database that requires recovery, without making changes to the backed up copy.

CR:547593

CR Number:   547593 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1520 22 Oct 2008 Fixed 11.0.1 1992 02 Dec 2008 Fixed Description When in the Maintenance Plan wizard, if the checkbox for "Disallow logins while the maintenance plan is running" was checked, then logins would have been disallowed for all databases running on the server. Now, logins are disallowed only for the database in which the maintenance plan is defined.

CR:547594

CR Number:   547594 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1520 23 Oct 2008 Fixed 11.0.1 1992 02 Dec 2008 Fixed Description In the Maintenance Plan wizard, if the checkbox "Validate database pages" was selected, then the generated event handler would have validated tables and materialized views as well, even if the checkbox "Validate tables and materialized views" was not selected. This has been fixed.

CR:547708

CR Number:   547708 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1522 23 Oct 2008 Fixed 10.0.1 3787 23 Oct 2008 Fixed 11.0.1 1993 02 Dec 2008 Fixed Description Attempting to create a database with an apostrophe in a filename or the dba user's password, could have failed with a syntax error. Also, attempting to create a database with a dbkey containing a backslash may have resulted in a database which could not be connected to. These problems have now been fixed.

CR:547713

CR Number:   547713 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1521 22 Oct 2008 Fixed 11.0.1 2001 02 Dec 2008 Fixed Description Sybase Central would have failed to delete a remote server or a directory access server if it had one or more proxy tables. Now, the proxy tables are automatically deleted before the remote server or directory access server is deleted. This fix restores the behaviour to what it was in versions 10 and earlier.

CR:547716

CR Number:   547716 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1521 22 Oct 2008 Fixed 10.0.1 3787 22 Oct 2008 Fixed 11.0.1 1993 02 Dec 2008 Fixed Description Attempting to add a blob to the download stream when using the MobiLink Direct Row API and the MLPreparedStatement.setBytes() method, would have failed. The method would have returned the error "Value is out of range for conversion" if the length of the byte array was larger than 65536 bytes. This problem has now been fixed.

CR:547730

CR Number:   547730 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1521 23 Oct 2008 Fixed 10.0.1 3787 23 Oct 2008 Fixed 11.0.1 2677 02 Dec 2008 Fixed 12.0.1 3450 14 Sep 2011 Fixed Description If a corrupted UltraLite or SQL Anywhere remote client synchronized with a MobiLink server, it was possible for protocol errors to be generated. When this occurred, the MobiLink server console log would have shown the text: I. <1> failed reading command with id:%d and handle:%d I. <1> Synchronization complete This has been fixed. Now, the error message "[-10001] Protocol Error: 400" will be displayed and a synchronization error will be reported.

CR:547738

CR Number:   547738 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 2032 08 Dec 2008 Fixed 11.0.0 1546 08 Dec 2008 Fixed Description Starting with version 10.0.0, the server now uses a new mechanism to evaluate LIKE predicates that start with a prefix of non-wildcard characters. This mechanism is needed to provide correct results with the NCHAR collation. This new algorithm operates by computing sortkey hashes that specify a range of column values that could possibly match the LIKE predicate; the LIKE predicate is retained in some cases where it may further filter these returned rows. These sortkey hashes can be used as index range bounds to quickly filter the set of rows processed by the query. In the case that an index was not selected to process the LIKE predicate, the new implementation could have been more expensive, as it had the additional cost of computing the sortkey hash. The optimization has now been adjusted so that the sortkey hash bounds are used only if the LIKE predicate is used in an index scan. Otherwise, the like_prefix predicate is evaluated by comparing the column string to the pattern prefix character by character. This should give performance that meets or exceeds previous versions.

CR:547779

CR Number:   547779 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1521 23 Oct 2008 Fixed 11.0.1 1994 02 Dec 2008 Fixed Description When creating a maintenance plan, the SQL for the plan's event handler would not always have been displayed in the database's Executed SQL tab. Instead the event SQL would have contained "HANDLER null". This problem would only occur if the handler did not include an SMTP or MAPI password. This has been fixed.

CR:547858

CR Number:   547858 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) 27 Oct 2008 Fixed Description If columns used to build an NGRAM text index contained words shorter than N, some positional information could have been lost. The positional information would also have been lost if a CONTAINS query, that used the NGRAM text index, contained terms shorter than N. For example, if the value 'what a weather' was stored in a column col1 indexed by NGRAM text index with N=4, the following CONTAINS queries would match the row: CONTAINS( col1, '"what a weather"') CONTAINS ( col1, '"what weather"' ) CONTAINS( col1, 'what NEAR[1] weat' ) CONTAINS( col1, 'what NEAR[2] weat' ) This has been fixed, so that only the first and fourth queries will now match the row. Note, all NGRAM text indexes built before this fix should be rebuilt either by using REFRESH TEXT INDEX ... FORCE BUILD (for MANUAL or AUTO REFRESH text indexes), or by dropping and recreating (for IMMEDIATE text indexes).

CR:547905

CR Number:   547905 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3787 24 Oct 2008 Fixed Description If a SQL statement contained comments using %-style comments, then the ODBC driver could have reported a syntax error when the comment contained an unmatched quote. For example: % it's a contraction The ODBC driver has to parse statements looking for ODBC escape sequences, but did not handle %-style comments. This has been fixed.

CR:547906

CR Number:   547906 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2028 24 Oct 2008 Fixed 11.0.0 1540 24 Oct 2008 Fixed 10.0.1 3806 24 Nov 2008 Fixed Description If a column in the consolidated database was larger than the corresponding column in the remote database, then the MobiLink server may have crashed when synchronizing. This has been fixed so that the sync will now abort with the error -10038.

CR:548007

CR Number:   548007 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1522 24 Oct 2008 Fixed 11.0.1 1994 02 Dec 2008 Fixed Description A query that executed using intra-query parallelism did not respect the Priority connection option and would have executed at the 'normal' priority level. This has been fixed.

CR:548032

CR Number:   548032 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1523 24 Oct 2008 Fixed 10.0.1 3788 24 Oct 2008 Fixed 11.0.1 1995 02 Dec 2008 Fixed Description The MobiLink server would have printed the warning, "[10082] MobiLink server has swapped data pages to disk", after it had swapped 5000 pages to disk, or about 20MB of row data. This has been changes so that it now prints this message after the first time the server must swap to disk. This should make it easier to diagnose performance problems when -cm is set slightly too small.

CR:548033

CR Number:   548033 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 10.0.1 3788 24 Oct 2008 Fixed Description When synchronizing through a third-party server or proxy and using TLS or HTTPS, the sync could have failed with the stream error code STREAM_ERROR_READ and system error code 4099 (hex 1003). This has now been fixed.

CR:548043

CR Number:   548043 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 2037 06 Nov 2008 Fixed 11.0.0 1559 03 Dec 2008 Fixed Description Under heavy load, the server could have, in rare situations, generated a log that had an operation that would have been unreadable by the MobiLink client dbmlsync. Dbmlsync would have reported: "Log operation at <location> has bad data at offset <location>". This was likely only possible on multiprocessor systems, and has now been fixed.

CR:548059

CR Number:   548059 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 06 Nov 2008 Fixed 11.0.1 2011 03 Dec 2008 Fixed Description A server started with a 32K page size, and a large cache size (or a very high -gn value), could have failed an assertion during or immediately following server startup. This has been fixed.

CR:548142

CR Number:   548142 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) 27 Oct 2008 Fixed Description The messages "Failed to attach database worker thread", "Error while attaching database worker thread to Java VM" and "Unable to attach worker to VM.", mention worker threads and database worker threads, but these errors can occur on any thread within the server. They have now been changed to "Failed to attach thread", "Error while attaching thread to Java VM" and "Unable to attach thread to .NET runtime." respectively.

CR:548144

CR Number:   548144 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.0 1523 27 Oct 2008 Fixed 10.0.1 3788 27 Oct 2008 Fixed 11.0.1 1995 03 Dec 2008 Fixed Description If a network error occurred during a read from the stream, some MobiLink Java clients could have hung with 100% CPU utilization. This has been fixed. The MobiLink Monitor, the SQL Anywhere Monitor, the Notifier and QAnywhere are all affected by this.

CR:548153

CR Number:   548153 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 27 Oct 2008 Fixed Description When using Interactive SQL to select text strings that include curly brackets or braces ie the characters { and } using the result format text will cause a stack trace in Interactive SQL. Workaround Description  Avoid using text format when selecting strings with curly braces ie :{ or }

CR:548160

CR Number:   548160 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 1998 06 Jan 2009 Fixed 11.0.0 1542 06 Jan 2009 Fixed Description In certain specific circumstances, some expressions in triggers could have caused the server to crash when executing the trigger. This has been fixed.

CR:548173

CR Number:   548173 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1524 29 Oct 2008 Fixed 11.0.1 1999 03 Dec 2008 Fixed Description Repeated update synchronizations, that is where existing client rows are updated, could have caused unnecessary database growth. A row storage problem has now been corrected.

CR:548260

CR Number:   548260 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 2112 12 Nov 2008 Fixed Description The function REGR_R2( Y, X ) incorrectly returned NULL as the answer when COUNT(*) * SUM( Y * Y ) was equal to SUM(Y) * SUM(Y). This has been corrected so that the server will now return the correct answer of 1.

CR:548282

CR Number:   548282 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) 30 Oct 2008 Fixed Description CONTAINS queries with prefix terms that contained non-alphanumeric characters would fail to match rows containing the matching terms. Additionally, if the columns in the CONTAINS query were indexed using NGRAM text index, and the length of the prefix was greater than N, the CONTAINS query would also fail to find matches. If the columns in the CONTAINS query were indexed using a GENERIC text index with MINIMUM TERM LENGTH set to a value other than the default, searches for the phrase with a prefix shorter than MINIMUM TERM LENGTH could fail to find matches. Examples: query with non-alphanumeric characters: ' pre-school* ', ' a_variable_n* ', ' " pre-scho* children " ' query over 4-GRAM indexed columns: ' weath* ', ' " beau* weath* " ' query over columns indexed by GENERIC text index with MINIMUM TERM LENGTH = 3: ' singular no* ending with ', ' " singular no* ending with " ' This has been fixed so that the above examples are now interpreted as the following queries: ' pre-school* ' = '"pre school*"' (GENERIC text index) ' a_variable_n* ' = '"a variable n*"' (GENERIC text index) ' " pre-scho* children " ' = '"pre scho* children"' (GENERIC text index) (Note: STOPLIST and length restrictions are applied to all resulting terms except for the actual prefix, i.e. if 'pre' was in the STOPLIST, the last query would be interpreted as '"scho* children"') ' weath* ' = '"weat eath"' (4-GRAM text index) ' " beau* weath* " ' = '"beau" & "weat eath"' (4-GRAM text index) ' singular no* ending with ' = 'singular no* ending with' (GENERIC text index with MINIMUM TERM LENGTH = 3) ' " singular no* ending with " ' = '"singular ^ ending with"' (GENERIC text index with MINIMUM TERM LENGTH = 3. The ^ in the query represents the fact that the phrases with a single term between 'singular' and 'ending' will be found, and not those with no intervening terms, or multiple intervening terms) The following new rules were added to the CONTAINS query grammar with respect to NGRAM text indexes: 1) If a prefix term is shorter than N, all NGRAMs beginning with the prefix will be matched. For example: on a 4-GRAM text index the query 'a*' will match all the rows that contain at least one 4-GRAM beginning with a, including the following: 'apple pie' (contains appl) 'container' (contains aine) 2) If a prefix term has length N or higher, it is converted to a search for the exact substring equal to the prefix. This is due to the fact that information about the beginning and end of a word is not stored in NGRAM index. Searches for 'apple' or 'appl*' on a 4-GRAM text index will both find rows containing words 'apple' and 'pineapple'. 3) If a prefix term appears in a phrase in the CONTAINS query that will use NGRAM text index, the phrase is converted into an AND of two phrases - one from the beginning of the phrase up to and including the prefix term, and the other one beginning at the term following the prefix term and ending at the last term of the phrase. For example, for a 4-GRAM text index, query ' " where ord* an* relati* distance " ' is interpreted as '"wher here ord*" & "an*" & "rela elat lati" & "dist ista stan tanc ance"' 4) If one of the arguments to NEAR is a prefix, NEAR is converted to AND. For example, for a 4-GRAM text index, query ' app* NEAR orang* ' is interpreted as 'app* & "oran rang"' The following new rules were added to the CONTAINS query grammar with respect to GENERIC text indexes with MINIMUM TERM LENGTH > 1: 1) In a phrase, prefix term shorter than MINIMUM TERM LENGTH will be dropped. For example, on a GENERIC text index with MINIMUM TERM LENGTH = 3, query ' " the g* weather " ' will be interpreted as '"the ^ weather"' and will match both 'the good weather' and 'the bad weather', but not 'the weather is good'. 2) Outside of a phrase, prefix term shorter than MINIMUM TERM LENGTH will match terms that are between MINIMUM and MAXIMUM TERM LENGTH and begin with the specified prefix. For example, on a GENERIC text index with MINIMUM TERM LENGTH = 3, query ' the g* weather ' will be interpreted as 'the & g* & weather' and will match 'the good weather', 'the weather is good', but not 'the bad weather'.

CR:548322

CR Number:   548322 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 30 Oct 2008 Fixed 10.0.1 3790 30 Oct 2008 Fixed 9.0.2 3747 30 Oct 2008 Fixed 11.0.1 2000 03 Dec 2008 Fixed Description If an application calls PreparedStatement.executeBatch(), the iAnywhere JDBC driver is supposed to return an integer array that contains a status for each row in the batch. The iAnywhere JDBC driver was instead returning an integer array containing only two elements. This problem has now been fixed.

CR:548323

CR Number:   548323 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1524 29 Oct 2008 Fixed 10.0.1 3791 03 Nov 2008 Fixed 11.0.1 2000 03 Dec 2008 Fixed Description If many connections were making external environment (or Java) calls at the same time, and the number of worker threads had not been increased by an appropriate amount, then there was a possibility that the server would either have hung or crashed. A thread deadlock error will now be returned instead.

CR:548431

CR Number:   548431 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1524 29 Oct 2008 Fixed 11.0.1 2000 03 Dec 2008 Fixed Description Sybase Central could have crashed when pasting a column in the table editor. The problem would only have occurred if a new column was added, but a name for the new column had not yet been specified. This has been fixed.

CR:548437

CR Number:   548437 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 29 Oct 2008 Fixed 10.0.1 3790 29 Oct 2008 Fixed 11.0.1 2000 03 Dec 2008 Fixed Description Under rare circumstances, a loss of quorum could have resulted in the database file and the transaction log on the primary becoming out of sync. Subsequent attempts to start the database would have failed with the error "Unable to start specified database: Cannot use log file '<name>' since it is shorter than expected". This has been fixed. Note, the likelihood of this problem appearing with 11.0.0 servers was even smaller than with 10.0.1 servers.

CR:548455

CR Number:   548455 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.0 1524 12 Nov 2008 Fixed 10.0.1 3790 12 Nov 2008 Fixed 11.0.1 1999 03 Dec 2008 Fixed Description When attempting to export synchronized data to an Oracle database, the application could have given a false positive for a table's existence, which would have resulted in an export failure since it would not have tried to create the table for the current user. This has been fixed. Also, exports to Oracle previously used the Date data type. Now, for Oracle 9 or later Timestamp is used instead of Date.

CR:548463

CR Number:   548463 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 29 Oct 2008 Fixed 10.0.1 3790 29 Oct 2008 Fixed 11.0.1 2000 03 Dec 2008 Fixed Description Using the Certificate creation utility (createcert) to create certificates or certificates requests would have failed with the error "Error occurred encoding object", when provided non-ASCII input. This has been fixed.

CR:548465

CR Number:   548465 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) 29 Oct 2008 Fixed Description Database startup events that used external environments or web procedures may have failed if the database was specified on the server start line. This has been fixed. Note that databases started later (after the server is up and running) would not have this problem.

CR:548470

CR Number:   548470 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 26 Nov 2008 Fixed 10.0.1 3790 30 Oct 2008 Fixed 11.0.1 2000 26 Nov 2008 Fixed Description If a mirror server had shut down and then very quickly restarted as a preferred server, synchronization may have been delayed by thirty seconds. This has been fixed.

CR:548473

CR Number:   548473 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3762 02 Dec 2008 Fixed Description When a version 9 server was used to run a databases created with version 7 or older, the server could have choosen inefficient query access plans due to errors in estimation of join selectivities. These database do not contain column statistics in the form of domain distribution histograms stored in the system table SYSCOLSTAT, as with later version. This has been corrected so that the server will now do a much better job of estimating these selectivities.

CR:548519

CR Number:   548519 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.0 1525 30 Oct 2008 Fixed 11.0.1 2001 03 Dec 2008 Fixed Description The process for creating the MobiLink stored procedures for DB2 mainframe (D2M) via syncd2m_jcl.sql was not complete. This has been fixed. With the addition of d2mrelod.jcl, the steps are now: 1) Copy syncd2m_jcl.sql and edit it. Change {MLTABLESPACE} to your qualified tablespace, eg. MYDB.MYTS Change {WLMENV} to the name of a WLM associated with your DB2 instance 2) Start DBISQL and connect to DB2 mainframe. File->Run your copy of syncd2m_jcl.sql. 3) From the %SQLANY%\MobiLink\setup directory, FTP to your mainframe, running the following commands after you connect: bin hash cd xmit quote site recfm=fb lrecl=80 quote site cyl put d2mload.xmit put d2mdbrm.xmit quit The two XMIT files on the mainframe are now: USERID.XMIT.D2MLOAD.XMIT USERID.XMIT.D2MDBRM.XMIT where 'USERID' is the username you gave when connecting via FTP. 4) Open a terminal session and run the following commands from the ISPF Command Shell: RECEIVE INDATASET('USERID.XMIT.D2MLOAD.XMIT') RECEIVE INDATASET('USERID.XMIT.D2MDBRM.XMIT') The output is: USERID.ML.LOADLIB USERID.ML.DBRMLIB 5) Copy d2mrelod.jcl and edit it. Change USERID to your mainframe userid. Change DSNDB0T to your DB2 DSN. 6) Run your copy of d2mrelod.jcl 7) Copy d2mbdpk.jcl and edit it. Change USERID to your mainframe userid. Change DB0T to your DB2 SSID. 8) Run your copy of d2mbdpk.jcl The MobiLink schema should now be ready to use.

CR:548580

CR Number:   548580 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) 11.0.0 1530 05 Nov 2008 Fixed 10.0.1 3794 05 Nov 2008 Fixed 11.0.1 1839 03 Dec 2008 Fixed Description Synchronizing a UNIQUEIDENTIFIER field in a remote database to Oracle via MobiLink would have resulted in a 32 character UUID, followed by a NULL character and three other characters (typically also NULL). When sending GUIDs to Oracle, MobiLink was removing the hyphens to match the GUIDs generated by the SYS_GUID() function in Oracle, but was not trimming the ODBC bind length to account for the hyphen removal, thus resulting in 4 extra bytes in the string representation of the UUID in Oracle. These four extra characters have now been removed.

CR:548619

CR Number:   548619 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 03 Nov 2008 Fixed 11.0.1 2001 03 Dec 2008 Fixed Description When using the Foreign Key wizard to create a foreign key, or the Foreign Key Change Settings dialog to drop and re-create a foreign key with new settings, then the "Allows null" setting chosen would have been reversed. That is, if to allow nulls was chosen, then the foreign key would have been created to prohibit nulls, and vise versa. This has now been corrected.

CR:548625

CR Number:   548625 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 2119 27 Nov 2008 Fixed 11.0.0 1541 27 Nov 2008 Fixed 10.0.1 3807 27 Nov 2008 Fixed Description When the -z command line option was used, or when request level logging was enabled, the server could have generated thousands of message of the form: "Internal warning: <x> dispatch took <y> seconds" where x is an object name and y is a number. This would have affected the Windows platform only, and not necessarily on all Windows machines. This has now been fixed. A workaround is turn off the -z option or request level logging.

CR:548626

CR Number:   548626 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 31 Oct 2008 Fixed 10.0.1 3791 03 Nov 2008 Fixed 11.0.1 2001 03 Dec 2008 Fixed Description If a table had a trigger defined that made an external environment call and many connections attempted to access the table at the same time, forcing table locks and simultaneous external environment calls, then there was a chance the server would have hung. This problem has now been fixed.

CR:548627

CR Number:   548627 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1525 03 Nov 2008 Fixed 10.0.1 3790 03 Nov 2008 Fixed 11.0.1 2001 03 Dec 2008 Fixed Description Remote TCP connection attempts to servers running on Unix systems with IPv6 enabled, may have failed with the error "Connection error: An error occurred during the TCPIP connection attempt." This was only likely to happen on machines that were ONLY using IPv6. This has been fixed. As a workaround, the IPv6 address of the server machine can be specified using the HOST parameter.

CR:548710

CR Number:   548710 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1527 31 Oct 2008 Fixed 10.0.1 3791 31 Oct 2008 Fixed 11.0.1 2002 03 Dec 2008 Fixed Description If recovery was attempted on a database that had grown since the last successful checkpoint had been executed, some pages may have become unavailable for reuse. This has now been fixed.

CR:548716

CR Number:   548716 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1526 31 Oct 2008 Fixed 11.0.1 2002 01 Dec 2008 Fixed Description When the server was started with a command line that specified -xs option (comma-separated list of web protocols) without a port, the server 'Overview' did not show the default port. This has been fixed.

CR:548721

CR Number:   548721 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 03 Nov 2008 Fixed 11.0.1 2010 01 Dec 2008 Fixed Description If the CREATE SYNCHRONIZATION PROFILE statement was used to create a synchronization profile with embedded whitespace in the options string, then Sybase Central was not able to parse the string and display the option values on the Synchronization Profile property sheet. This has been fixed.

CR:548724

CR Number:   548724 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3738 31 Oct 2008 Fixed Description When using an ASE consolidated database, the MobiLink server with messaging enabled will log deadlock errors, such as the following, when several QAnywhere clients are synchronizing concurrently: E. 10/07 09:14:13. Error: java.sql.SQLException: [DataDirect][ODBC Sybase Wire Protocol driver][SQL Server]Your server command (family id #0, process id #342) encountered a deadlock situation. Please re-run your command. These errors happen because ASE uses page-level locking by default. This locking level causes deadlocks with many of the SQL statements executed by MobiLink with QAnywhere, especially as many clients are synchronizing concurrently. This problem can be worked around by executing the following SQL statements on the ASE consolidated database, when the database server is not handling other requests: alter table ml_qa_repository lock datarows go alter table ml_qa_delivery lock datarows go alter table ml_qa_notifications lock datarows go alter table ml_qa_global_props lock datarows go alter table ml_qa_status_history lock datarows go alter table ml_qa_repository_props lock datarows go alter table ml_qa_repository_staging lock datarows go alter table ml_qa_status_staging lock datarows go create index ml_qa_delivery_cli on ml_qa_delivery ( client ) go create index ml_qa_delivery_dld on ml_qa_delivery ( client, syncstatus, status ) go create index ml_qa_mstage_user on ml_qa_repository_staging ( mluser ) go create index ml_qa_sstage_user on ml_qa_status_staging ( mluser ) go These SQL statements change the QAnywhere system tables to use row-level locking, and add some indexes for increased performance.

CR:548833

CR Number:   548833 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 03 Nov 2008 Fixed 10.0.1 3792 03 Nov 2008 Fixed 11.0.1 2005 01 Dec 2008 Fixed Description If a server was very busy, and several connections attempted to start external environments at the same time, and if several of the start external environment requests timed out, then, in very rare cases, the server could eventually have become unresponsive. This problem has now been fixed.

CR:548870

CR Number:   548870 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2132 22 Dec 2008 Fixed 11.0.0 1553 22 Dec 2008 Fixed 10.0.1 3821 22 Dec 2008 Fixed Description A database could have become corrupted when deleting rows containing long string (or binary) values that were indexed. The server then may have crashed, or failed an assertion, when attempting to read rows from the table at a later time. The server would likely have crashed during full validation of a table corrupted in this manner. This has been fixed. Dropping and re-creating the index should be a valid workaround.

CR:548890

CR Number:   548890 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 03 Nov 2008 Fixed 11.0.1 2005 01 Dec 2008 Fixed Description The delivery condition for a destination alias may not have been fully visible on the "Members" tab of the alias' property sheet. The cells in the table have their height and width set explicitly . The code which calculated a row's height looked only at data in the second column, rather than using the data in all three columns. This has been fixed.

CR:548895

CR Number:   548895 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1527 03 Nov 2008 Fixed 11.0.1 2003 01 Dec 2008 Fixed Description Sybase Central could have created a dialog, property sheet or wizard whose window was larger than the screen. This would have made it difficult to work with the window. This has been fixed so that Sybase Central now ensures that dialogs, property sheets and wizards are no longer than the screen.

CR:548941

CR Number:   548941 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1544 06 Nov 2008 Fixed 11.0.1 2031 01 Dec 2008 Fixed Description Statements with a CONTAINS clause, and statements over text index stored procedures (for example, sa_text_index_vocab), could have incorrectly returned no results. This problem affected only MANUAL and AUTO REFRESH text indexes, and only occurred when statements that useed a MANUAL or AUTO REFRESH text index had to be executed simultaneously with a REFRESH statement on the same text index. Alternatively, if the statement was prepared or cached by the server before a REFRESH on the text index occurred, an empty result set could also be returned when the prepared statement or cached plan was used after the REFRESH has completed. This has now been fixed.

CR:548981

CR Number:   548981 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 06 Nov 2008 Fixed 11.0.1 2011 01 Dec 2008 Fixed Description The pages allocated for temporary tables was not being recovered after an abnormal shutdown. This has been corrected.

CR:549048

CR Number:   549048 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 2110 04 Nov 2008 Fixed 11.0.0 1530 04 Nov 2008 Fixed Description When displaying results as text, the row count was not being displayed under each result set. This has been corrected so that the count will now be displayed, unless the result is returned from a stored procedure.

CR:549052

CR Number:   549052 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 04 Nov 2008 Fixed 11.0.1 1528 01 Dec 2008 Fixed Description Scheduled transmission rules defined in the MobiLink server for QAnywhere message transmission, could have behaved unexpectedly in some circumstances. The server would have sent push notifications to clients with waiting messages satisfying the condition of a scheduled rule according to the schedule. However, if a client synchronized with the server for any reason, whether or not as a result of a push notification from a scheduled rule, messages satisfying the condition of a scheduled rule would have been transmitted to the client. Thus, the unexpected behaviour was that messages that satisfied the condition of a scheduled rule in the server could have been transmitted from the server to clients at times differing from the times specified in the schedule. This has been fixed so that the transmission of messages that satisfy the conditions of the scheduled rules from the server to clients is now governed more closely by the schedule specified in those rules.

CR:549085

CR Number:   549085 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 2107 08 Jan 2009 Fixed 11.0.0 1559 08 Jan 2009 Fixed 10.0.1 3831 08 Jan 2009 Fixed Description A heavily-loaded server could have hang while running diagnostic tracing with a high detail level. This has been fixed.

CR:549088

CR Number:   549088 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 06 Nov 2008 Fixed 11.0.1 2011 02 Dec 2008 Fixed Description Under rare circumstances, the server could have failed to report the warning "Row has been updated since last time read" (SQLCODE 104), when using a value-sensitive cursor and fetching a row that had been modified since it was last fetched. This has been fixed.

CR:549098

CR Number:   549098 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1528 04 Nov 2008 Fixed 11.0.1 2010 02 Dec 2008 Fixed Description If an application issued an external environment request, and the external environment process crashed for whatever reason at the same time, then there was a chance, although likely rare, that the server would have crashed as well. This problem has now been fixed.

CR:549142

CR Number:   549142 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 06 Nov 2008 Fixed 11.0.1 2108 02 Dec 2008 Fixed Description The LIKE operation could have produced incorrect results. The operation did not operate case insensitively, and the first character of a range was not accepted. This problem has now been fixed.

CR:549218

CR Number:   549218 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 06 Nov 2008 Fixed 10.0.1 3794 06 Nov 2008 Fixed 9.0.2 3750 06 Nov 2008 Fixed 11.0.1 2012 02 Dec 2008 Fixed Description If an application creates a scrollable statement and then scrolls through the result set, calling ResultSet.getRow() will return the correct row number for all rows. Calling ResultSet.getRow() will also return the correct row number when the end of the result set is reached. However, if the application called ResultSet.isLast() while positioned on the last row of the result set and then called ResultSet.getRow(), the row number returned would have been "invalid" or "unknown". This problem has now been fixed. Note that calling ResultSet.getRow() after calling ResultSet.isLast() while positioned on any row other than the last row would have returned the correct row number. Workaround Description  None.

CR:549235

CR Number:   549235 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.0 1530 05 Nov 2008 Fixed 11.0.1 2011 02 Dec 2008 Fixed Description The external names for the D2 Mainframe stored procedures were supposed to be xxxa for version 10, xxxxb for version 11, and xxxxc for version 12. The changes for Engineering case 545762 incorrectly caused the names to be xxxxW. The scripts sent out as xxxxW will still be okay, as the important thing is that major versions differ in the external names by at least one character, so customers can use multiple versions of MobiLink in the same consolidated. This has now been corrected.

CR:549396

CR Number:   549396 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 2116 07 Nov 2008 Fixed 11.0.0 1538 07 Nov 2008 Fixed 10.0.1 3803 19 Nov 2008 Fixed Description Some arithmetic expressions in procedure statements could have been evaluated with the incorrect result domain. This would have occurred when one of the arguments had one of the following domains { BIT, TINYINT, UNSIGNED SMALLINT, SMALLINT } and the other argument was either one of those domains or INT. The result domain would have been INT. In some cases this could have lead to a different result being returned than expected, for example if an overflow would have occurred in the correct result domain. This problem has been fixed.

CR:549419

CR Number:   549419 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 06 Nov 2008 Fixed 9.0.2 3750 06 Nov 2008 Fixed 11.0.1 2013 02 Dec 2008 Fixed Description If an Open Client application that supports retrieving result sets with a large number of columns attempts to perform an encrypted login, the login would have failed with a protocol error. This problem has now been fixed.

CR:549424

CR Number:   549424 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 10 Nov 2008 Fixed 10.0.1 3794 10 Nov 2008 Fixed 11.0.1 2013 02 Dec 2008 Fixed Description A server running a tracing database could have crashed. This has been fixed.

CR:549431

CR Number:   549431 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 06 Nov 2008 Fixed 11.0.1 2013 26 Nov 2008 Fixed Description If a Windows based machine had both 32 and 64 bit client software installed, and an application subsequently attempted to use the iAnwhere JDBC driver, the driver may have thrown the exception UnsatisfiedLinkError indicating that it had attempted to load a dbjodbc11.dll of the wrong bitness. This problem has now been fixed. Note that switching the order in which the Bin32 and Bin64 directories appear in the path will work around this problem.

CR:549453

CR Number:   549453 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1530 07 Nov 2008 Fixed 10.0.1 3794 07 Nov 2008 Fixed 9.0.2 3750 07 Nov 2008 Fixed 11.0.1 2013 26 Nov 2008 Fixed Description When manually unregistering the SQL Anywhere ODBC driver from the command line using "regsvr32 -u dbodbcXX.dll", the unregistration process may have failed and reported error code 0x8000ffff. Note that the failure occurred after the user successfully acknowledged the prompt to allow dbelevate (the "SQL Anywhere elevated operations agent") to run as an administrator. This problem has been fixed. As a work-around, run "regsvr32 -u dbodbcXX.dll" from a command shell which is already elevated.

CR:549461

CR Number:   549461 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 2117 24 Nov 2008 Fixed 11.0.0 1539 24 Nov 2008 Fixed Description When attempting to update data in a proxy table on the "Data" tab in Sybase Central, or by manipulation of the result set in the Interactive SQL utility, the operation would have failed with the error "Feature remove savepoints not implemented." This been fixed.

CR:549466

CR Number:   549466 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2110 07 Nov 2008 Fixed 11.0.0 1530 07 Nov 2008 Fixed 10.0.1 3794 07 Nov 2008 Fixed Description The "-host" and "-port" command line options were completely ignored when connecting to a SQL Anywhere database. This problem also affected the Console utility (dbconsole) as well. It has now been fixed. As a workaround, use the "-c" command line option instead.

CR:549518

CR Number:   549518 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 9.0.2 3751 10 Nov 2008 Fixed Description The Schema Painter Create UltraLite Database Browse dialog was not filtering for database files, but incorrectly filtered by SQL files (*.sql). This has been fixed.

CR:549606

CR Number:   549606 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 11.0.1 2018 26 Nov 2008 Fixed Description If an ALTER TABLE statement added a column with a user-defined type having a default value, subsequent ALTER's affecting the table could have caused a server crash. This has been fixed.

CR:549622

CR Number:   549622 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1531 10 Nov 2008 Fixed 10.0.1 3795 10 Nov 2008 Fixed 11.0.1 2014 26 Nov 2008 Fixed Description A server running on a Linux system, may have hung when under heavy I/O load, and a large number of concurrent request tasks (i.e. large -gn value). Specifically, if -gn was larger than 250, then there was a chance a hang may have occurred. This has been fixed. The workaround is reduce the -gn value.

CR:549628

CR Number:   549628 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1531 07 Nov 2008 Fixed 11.0.1 2014 26 Nov 2008 Fixed Description When starting a backup, if any dbspace files had not already been opened by the server (for example, the file was moved), the server could crash. This has been fixed.

CR:549636

CR Number:   549636 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1531 07 Nov 2008 Fixed 11.0.1 2014 26 Nov 2008 Fixed Description When connected to a SQL Anywhere database in Admin mode of the MobiLink plug-in for Sybase Central, any internal tables used for maintaining text indexes would have been displayed under the Tables folder. This has been corrected so that these tables are now excluded, since they are of no use to users when creating table scripts.

CR:549644

CR Number:   549644 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1531 07 Nov 2008 Fixed 10.0.1 3795 07 Nov 2008 Fixed 11.0.1 2014 26 Nov 2008 Fixed Description When running on Linux systems, a mini core could have been improperly generated under rare circumstances.This has been fixed.

CR:549682

CR Number:   549682 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2024 10 Nov 2008 Fixed 11.0.0 1537 10 Nov 2008 Fixed 10.0.1 3801 19 Nov 2008 Fixed Description In rare, timing-dependent circumstances, multi-threaded client applications with multiple simultaneous TLS connections could have crashed. This has been fixed.

CR:549800

CR Number:   549800 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2152 13 Feb 2009 Fixed 11.0.0 1575 13 Feb 2009 Fixed 10.0.1 3847 13 Feb 2009 Fixed Description The SQL Anywhere ODBC driver incorrectly described a column of type NCHAR as SQL_WVARCHAR (-9), instead of SQL_WCHAR (-8), when the odbc_distinguish_char_and_varchar database option was set 'off'. In the following SQL statement, the two columns should be described as SQL_WCHAR and SQL_WVARCHAR respectively. select cast('abc' as nchar),cast('abc' as nvarchar) This problem did not affect calls to SQLColumns(), but it did affect calls to SQLDescribeCol(). This problem has been fixed. The odbc_distinguish_char_and_varchar option is intended for CHAR columns only. It is provided for backwards compatibility with older versions of the SQL Anywhere ODBC driver. For backwards compatibility, the odbc_distinguish_char_and_varchar option is set 'off' by default. When odbc_distinguish_char_and_varchar option is set 'on', the ODBC driver will describe CHAR columns as SQL_CHAR, rather than SQL_VARCHAR.

CR:549829

CR Number:   549829 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 2021 14 Nov 2008 Fixed 11.0.0 1536 14 Nov 2008 Fixed Description When using the SQL Anywhere PHP driver, calling the sasql_num_rows() function always returned zero if the function sasql_query() was used with the SASQL_USE_RESULT option, or the function sasql_use_result() was called. According to the documentation, the function sasql_num_rows() is supposed to return an estimate with SASQL_USE_RESULT, and an exact value with SASQL_STORE_RESULT. This has now been fixed. The workaround is to use the SASQL_STORE_RESULT option or call the function sasql_store_result().

CR:549846

CR Number:   549846 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 10.0.1 3796 12 Nov 2008 Fixed 11.0.1 2017 01 Dec 2008 Fixed Description In rare cases, monitoring of a heavily loaded server using the system procedure sa_performance_diagnostics, could have caused a server crash. This has been fixed.

CR:549847

CR Number:   549847 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 2023 05 Dec 2008 Fixed 11.0.0 1546 05 Dec 2008 Fixed Description In rare cases, an execution plan using parallelism, and index-only retrieval with a string or numeric column, could have caused a crash or possibly returned a wrong answer. This has been fixed.

CR:549866

CR Number:   549866 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 10.0.1 3797 12 Nov 2008 Fixed 11.0.1 2018 01 Dec 2008 Fixed Description The server could have crashed, or failed assertions, when under heavy load if pages were freed. The assertions were most likely to be about unexpected page types or contents. This has now been fixed.

CR:549932

CR Number:   549932 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 10.0.1 3797 12 Nov 2008 Fixed 11.0.1 2112 01 Dec 2008 Fixed Description The iAnywhere JDBC driver has supported the PreparedStatement.addBatch() and PreparedStatement.executeBatch() methods for quite some time now, but, these methods were only supported for INSERT statements. These methods will now also be supported for UDATE and DELETE statements, provided the underlying connection is to an SA server. If the underlying connection is to a non-SA server, then these methods will still only be supported for INSERT.

CR:549940

CR Number:   549940 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1533 13 Nov 2008 Fixed 10.0.1 3799 13 Nov 2008 Fixed 9.0.2 3753 13 Nov 2008 Fixed 11.0.1 2113 01 Dec 2008 Fixed Description If a transaction log was not completely written out to disk (e.g. during a low disk space scenario), it was possible for the server to crash when trying to apply a partial log operation during recovery. This has been fixed.

CR:549967

CR Number:   549967 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 10.0.1 3797 12 Nov 2008 Fixed 11.0.1 2018 01 Dec 2008 Fixed Description A SELECT ... FOR XML ... over an NCHAR value could have caused a string right truncation error to be generated. For example: SELECT * from table FOR XML AUTO where table is defined with an NCHAR column, e.g.: create table (col1 LONG NVARCHAR); For the error to have occurred, the byte length of the NCHAR value must have been greater than 32767, and the "string_rtruncation" database option must have been set to "on" (which is the default). This has been fixed.

CR:549983

CR Number:   549983 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 12 Nov 2008 Fixed 10.0.1 3797 12 Nov 2008 Fixed 9.0.2 3752 12 Nov 2008 Fixed 11.0.1 2112 01 Dec 2008 Fixed Description If an application executed a query involving both proxy tables and local tables, and the query had IN predicates that contained subqueries involving proxy tables, then there was a chance executing the query would have caused a server crash. This problem has now been fixed.

CR:549999

CR Number:   549999 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.0 1532 13 Nov 2008 Fixed 10.0.1 3797 13 Nov 2008 Fixed 11.0.1 2018 25 Nov 2008 Fixed Description If an Open Client application supports retrieving result sets with a large number of columns, then attempting to perform a Kerberos login using such an application would have failed with a protocol error. This problem has now been fixed.

CR:550080

CR Number:   550080 Product Name:   MobiLink Product Component:   QAnywhere server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2114 18 Nov 2008 Fixed 11.0.0 1536 18 Nov 2008 Fixed 10.0.1 3800 18 Nov 2008 Fixed Description In the Sybase Central QAnywhere Plugin, if when connected to a server message store a client was created, and then the view refreshed, the newly created client would not have been displayed. This has been fixed.

CR:550083

CR Number:   550083 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2114 14 Nov 2008 Fixed 11.0.0 1533 14 Nov 2008 Fixed Description Clicking the "Generate/INSERT statement" menu in the "Results" pane could have incorrectly caused the error "An INSERT statement could not be generated. The results are from more than one table or contain only computed columns." This has been fixed. Note, this problem appeared on the "Data" tab in Sybase Central, and has been fixed as well.