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

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

CR:586362

CR Number:   586362 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 2306 26 Aug 2009 Fixed 10.0.1 3951 26 Aug 2009 Fixed Description If an application made use of a global temporary table in an external environment via a server-side connection, then there was a chance that the server may have failed an assertion, hung, or crashed, when the application connection closed. This problem has now been fixed.

CR:586414

CR Number:   586414 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2302 20 Aug 2009 Fixed Description When running the Interactive SQL utility in a command window, if the output was redirected to a file, and the "-q" command line option was not specified, error messages would not have been displayed in the command window. This was a problem because the user had to press ENTER to continue the script, but the message saying to do that was redirected to the file. This has been corrected spo that the error output is now sent to the STDERR device, which is displayed in the console . To workaround this problem, use the "-q" command line option. That will print the error message in the console and will not prompt the user to press a key to continue.

CR:586427

CR Number:   586427 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 2302 19 Aug 2009 Fixed Description A typo in the message displayed when connecting to an unsupported database type has been fixed.

CR:586596

CR Number:   586596 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2306 26 Aug 2009 Fixed Description The SQL Anywhere server allows specification of the isolation level for a query as part of query text via the OPTION clause. This specification is valid only for the current statement and is meant to override other specifications of isolation level, e.g., those provided by the setting for the database option isolation_level, and cursor flags provided by the application at PREPARE and OPEN times. The server failed to honour the per statement specification for isolation level and used instead other specifications. This problem has been resolved. Now the isolation level specified in the query text is given the highest precedence.

CR:586604

CR Number:   586604 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   6.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2242 20 Aug 2009 Fixed Description On Solaris systems, if the directory /usr/ucb precedes /bin and /usr/bin in the PATH, the installer could have failed. Fixed by prepending /bin and /usr/bin to our local copy of PATH.

CR:586629

CR Number:   586629 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 2303 21 Aug 2009 Fixed 10.0.1 3947 21 Aug 2009 Fixed Description OPENXML namespaces may have caused the server to crash. This has been fixed.

CR:586829

CR Number:   586829 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2307 01 Sep 2009 Fixed 10.0.1 3952 01 Sep 2009 Fixed 11.0.0 1654 30 Aug 2010 Fixed Description UPDATE and DELETE statements could have acquired intent locks on tables that were not modified by the statement, possibly introducing concurrency or deadlock problems to an existing application. This has been fixed.

CR:586837

CR Number:   586837 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 2304 21 Aug 2009 Fixed 10.0.1 3948 21 Aug 2009 Fixed Description On Unix systems, the 64-bit server may have failed to start when the virtual memory user limit (ulimit -v) was low relative to the sum of the physical memory and swap space. This has been fixed.

CR:586868

CR Number:   586868 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2304 26 Aug 2009 Fixed Description When using SMTP to send email alerts, an incorrect error message could have been reported when an error occurred. This has been fixed.

CR:587028

CR Number:   587028 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 3949 26 Aug 2009 Fixed 9.0.2 3881 26 Aug 2009 Fixed Description The fix for Engineering case 581991 could have inadvertently turned on the feature for a new database architecture even if it was not requested. This has now been fixed. This could only have affected a database that was created using 9.0.2 build 3867-3880 or 10.0.1 build 3930-3948. The query: select * from sa_db_properties() where propname = 'HasTornWriteFix'; can be used to determine if the setting is ON or OFF. Turning the setting OFF requires a rebuild of the database using an engine with this fix.

CR:587036

CR Number:   587036 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 2308 01 Sep 2009 Fixed 10.0.1 3953 01 Sep 2009 Fixed 9.0.2 3884 01 Sep 2009 Fixed Description If a LONG VARCHAR column containing multi-byte data was fetched by the OLE DB provider, the resulting string may have contained appended null characters. As a result, the Length attribute of the string (e.g., strTxt.Length) may have been larger than expected. This problem has been fixed.

CR:587040

CR Number:   587040 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2305 26 Aug 2009 Fixed Description If the SQL Anywhere Monitor encountered an internal error and attempted to restart data collection, there was a chance that data collection would not have restarted correctly. This has been fixed.

CR:587193

CR Number:   587193 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) 25 Aug 2009 Duplicate Description Under certain circumstances, the server could failed an assertion, or crashed, while processing queries containing large strings. This has been fixed.

CR:587214

CR Number:   587214 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 2306 26 Aug 2009 Fixed 10.0.1 3950 26 Aug 2009 Fixed Description When HTTP client debugging was turned on, calling the HTTP client procedure would have resulted in a request time-out. This problem was introduced by the changes made for Engineering case 565244, and would have occurred when client logging was initiated, either with the -zoc command line option, or by calling the system procedure sa_server_option(), to set the 'WebClientLogFile' file name. This has now been fixed.

CR:587246

CR Number:   587246 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.1 2306 28 Aug 2009 Fixed 10.0.1 3951 28 Aug 2009 Fixed Description If a synchronization model was created that contained mappings with errors, and then the mappings were deleted or disableds, the sync model could still not have been deployed. The workarounds to this were to either recreate or enable the mapping, or manually edit the sync model file and remove the scripts with errors. This has been fixed.

CR:587256

CR Number:   587256 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2307 28 Aug 2009 Fixed 10.0.1 3951 28 Aug 2009 Fixed Description If a database with a foreign key declared as "NOT NULL" was unloaded or rebuilt, the resulting reload.sql or database contained the foreign key without "NOT NULL" declared. This has been fixed.

CR:587308

CR Number:   587308 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2309 10 Sep 2009 Fixed Description The UltraLiteJ runtime would have crashed if a SQL statement had too many terms (exceeding 150). UltraLiteJ used a fixed size stack to store the tokens of the statement when parsing it. The problem has now been resolved by growing the stack when necessary.

CR:587396

CR Number:   587396 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 2306 26 Aug 2009 Fixed Description If two or more connections, or two or more events, that made CLR calls closed or completed simultaneously, then there was a chance the CLR external environment may have hung. This problem has now been fixed.

CR:587402

CR Number:   587402 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 2306 26 Aug 2009 Fixed Description If an application made an external environment call, and another connection that also made an external environment call closes at the exact same time, then there was a very small chance that the server would have incorrectly returned a thread deadlock error, rather than allowing the external environment call to go through. This problem has been fixed.

CR:587404

CR Number:   587404 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 2306 26 Aug 2009 Fixed Description If an application made repeated calls to the CLR external environment, then the CLR environment (not the server) would have leaked memory. This problem has now been fixed.

CR:587429

CR Number:   587429 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2304 26 Aug 2009 Fixed Description No limit on the size of a CONTAINS query was imposed. This has been fixed. After this change, a CONTAINS query cannot contain more than 300 valid terms (terms that are not in the STOPLIST and are within permitted term length range).

CR:587671

CR Number:   587671 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) 11.0.1 2317 16 Sep 2009 Fixed 10.0.1 3963 16 Sep 2009 Fixed Description The server may have crashed when trying to find matching materialized view candidates. This would have happened when a materialized view candidate had a very complex SELECT clause, and the server was close to stack overflow or had too little cache space. This has been fixed.

CR:587699

CR Number:   587699 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2309 01 Sep 2009 Fixed Description If the DBTools function DBSynchronizeLog() was called when no callback routines (errorrtn, msgrtn, warningrtn, logrtn, progress_msg_rtn, progress_index_rtn, msgqueuertn, confirmrtn) were defined, it would have crashed. This problem has been fixed. It is no longer necessary to define all callback routines. A workaround is to define each of the callback routines. Example: a_sync_db sync; . . . sync.confirmrtn = (MSG_CALLBACK) ConfirmCallback;

CR:587795

CR Number:   587795 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2307 28 Aug 2009 Fixed Description Updates or deletes to temporary tables may have caused the engine to crash if the temporary file had corrupted pages. This has been fixed.

CR:587856

CR Number:   587856 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2341 02 Nov 2009 Fixed 10.0.1 3982 02 Nov 2009 Fixed Description An application that was connected via jConnect or Open Client, that attempted to insert or retrieve a date value prior to January 1,1753, would have been incorrectly received an invalid date value error for the insert, and would have been returned the date January 1, 1753 for the fetch. This problem has now been fixed. Note that application must use newer versions of jConnect or Open Client in order to get date support for dates prior to January 1, 1753. Also, the restriction of January 1, 1753 using jConnect or Open Client still exists for datetime values.

CR:587873

CR Number:   587873 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 2307 28 Aug 2009 Fixed Description If an application made a CLR external environment call and then subsequently cancelled the CLR request, there was a chance that the CLR external environment would crash. This problem has now been fixed.

CR:587888

CR Number:   587888 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 2307 28 Aug 2009 Fixed Description Previously, if an application connected to a Web Edition server and attempted to make use of a directory access server, the Web Edition server would fail the request with a "this server is not licensed to support the 'Remote Data Access' feature" error. This problem has now been fixed. Note that attempting to make use of other remote data access server classes will still give the "not licensed" error when the application is connected to a Web Edition server.

CR:588055

CR Number:   588055 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2308 01 Sep 2009 Fixed Description When running the CREATE ENCRYPTED/DECRYPTED DATABASE '<newdb>' FROM '<sourcedb>' statement, if the transaction or mirror log name stored in the source database file was unqualified, we would have tried to locate it with respect to the engine's current working directory rather than the location of the database file. For example, if the engine was running in the directory /foo, the statement CREATE ENCRYPTED DATABASE 'new.db' FROM '/bar/source.db' was issued, and the transaction log name stored in source.db was 'source.log,' we would have tried to open /foo/source.log. If the current working directory had a version of the log file that was incompatible with the source database, the operation would fail. This has been fixed.

CR:588076

CR Number:   588076 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 2308 01 Sep 2009 Fixed Description If a proxy table existed in a case-sensitive database, and the proxy table had an index on it, unloading and reloading the database would have failed with the error "Cannot create item (<index_name>) in the specified dbspace". This has been fixed.

CR:588253

CR Number:   588253 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 3884 01 Sep 2009 Fixed Description A database upgrade would not have added execute permissions to "public" on the recreated procedure sp_password. This has been fixed.

CR:588329

CR Number:   588329 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2309 08 Sep 2009 Fixed 10.0.1 3956 08 Sep 2009 Fixed Description If an application connected via jConnect used the method CallableStatement to execute a stored procedure, then there was a chance the connection would have terminated with a protocol error. This problem would only have occurred if the stored procedure had an argument named @p# where # was an integer between 0 and n-1 with n representing the number of arguments in the stored procedure. For example, if an application connected via jConnect used CallableStatement to execute a stored procedure named test, and if test had 3 arguments, and if one of the arguments in test was named @p0, @p1 or @p2, then the server would have dropped the connection with a protocol error. This problem has now been fixed. It should be noted that this problem does not affect applications using the iAnywhere JDBC driver.

CR:588497

CR Number:   588497 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 2309 08 Sep 2009 Fixed Description Execution of the MERGE statement within SQL Anywhere could have caused the server to crash under some specific circumstances. This problem has now been resolved.

CR:588498

CR Number:   588498 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 2309 08 Sep 2009 Fixed 10.0.1 3956 08 Sep 2009 Fixed Description If a server attempted to abandon or cancel a request to start an external environment, due to the server being extremely busy or overloaded, then there was a very small chance the server would have hung. This problem has now been fixed.

CR:588499

CR Number:   588499 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 2310 08 Sep 2009 Fixed 9.0.2 3885 08 Sep 2009 Fixed Description The server would have stopped the TCP listener and printed the message "TCP Listener shutting down (130)" to the console log, if it has accepted a new client connection but the client side has already gone. This has been fixed.

CR:588539

CR Number:   588539 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 2309 08 Sep 2009 Fixed 10.0.1 3956 08 Sep 2009 Fixed Description If an application attempted to access a JDBC based Remote Data Access server, and the tsql_variables option was set to ON, then the server would have failed the request with a syntax error. This problem has now been fixed.

CR:588692

CR Number:   588692 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 2310 08 Sep 2009 Fixed 10.0.1 3956 08 Sep 2009 Fixed Description On Unix systems, if the transaction log for a primary server was not located in the server's current working directory, and was renamed when the mirror server was unavailable and the primary server was restarted, synchronization would have failed when the mirror server then became available again. This has been fixed.

CR:588720

CR Number:   588720 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 2313 08 Sep 2009 Fixed 10.0.1 3956 08 Sep 2009 Fixed Description If an application started Java, then subsequent connections to the server may have found that the option settings for date_format, time_format, timestamp_format and date_order were different than expected. This problem has now been fixed.

CR:588740

CR Number:   588740 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 2309 08 Sep 2009 Fixed 11.0.0 1654 08 Sep 2009 Fixed 10.0.1 3956 08 Sep 2009 Fixed 9.0.2 3885 08 Sep 2009 Fixed Description We learned that in the interest of improved performance, Microsoft Windows explicitly prevents certain documented methods of guaranteeing that data has been written to the physical storage medium from working on IDE/SATA/ATAPI drives (SCSI drives are unaffected). Recoverability after a power outage could be compromised. The database server now performs additional operations to flush data to disk to improve recoverability. In testing, there was no measurable performance degradation by this change. Relevant third-party articles: http://perspectives.mvdirona.com/2008/04/17/DisksLiesAndDamnDisks.aspx http://msdn.microsoft.com/en-us/library/dd979523%28VS.85%29.aspx http://research.microsoft.com/apps/pubs/default.aspx?id=70554 http://groups.google.com/group/microsoft.public.win32.programmer.kernel/browse_frm/ thread/4590ed3a4133828f/406cfb3a9deae044

CR:588917

CR Number:   588917 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 3893 22 Sep 2009 Fixed Description The policy file for .NET 2.0 was installed incorrectly. This has now been corrected.

CR:588921

CR Number:   588921 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 2310 08 Sep 2009 Fixed Description If an application attempted to query a non-nullable bigint column from a proxy table, and the remote server class was asejdbc, then the request would have failed with a strange conversion error. This problem has now been fixed.

CR:588924

CR Number:   588924 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2313 09 Sep 2009 Fixed 10.0.1 3960 09 Sep 2009 Fixed Description If a timestamp column was defined with "not null default [utc] timestamp", and an insert specified a null value for that column, then the insert would have failed with a SQL error. In version 9 and earlier, the insert used the default instead and did not fail. This behaviour has now been restored.

CR:588940

CR Number:   588940 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 2310 05 Oct 2009 Fixed Description When using the Import Wizard to import data from a file, if the file specified did not exist, an incomplete error message was displayed. This has been corrected so that the message is now complete.

CR:588950

CR Number:   588950 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 2310 08 Sep 2009 Fixed Description The Import Wizard could have crashed when clicking the Back button on the "Where do you want to save the data" page, if "In an existing table" was selected but no table was selected in the list. This has been fixed.

CR:589219

CR Number:   589219 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 2310 08 Sep 2009 Fixed Description If many connections attempted to make CLR external environment calls simultaneously, then there was a chance that some of the requests would have failed with a strange unhandled exception error. These unhandled exception errors would come from the CLR external environment, and not from the server itself. This problem has now been fixed.

CR:589236

CR Number:   589236 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2320 28 Sep 2009 Fixed Description The MobiLink server could have crashed following a failed synchronization. This has now been fixed.

CR:589406

CR Number:   589406 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 2311 09 Sep 2009 Fixed Description Creating a text configuration object, or creating a text index from a text configuration, did not qualify object names when they were logged in the transaction log. This has now been corrected.

CR:589437

CR Number:   589437 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2313 09 Sep 2009 Fixed Description A single-value SELECT could have produced incorrect results when the select list involved non-trivial expressions (such as function calls). This has been corrected.

CR:589624

CR Number:   589624 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 3968 10 Sep 2009 Fixed Description Some string operations, involving concatenation and substring on compressed columns, may have caused the fetch request to hang forever. This has been fixed.

CR:589646

CR Number:   589646 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 2314 11 Sep 2009 Fixed 11.0.0 1654 11 Sep 2009 Fixed 10.0.1 3961 11 Sep 2009 Fixed Description The number of bytes required to store a bitstring column value could have been under reported. This could then have potentially caused buffer overruns in client applications. This has been fixed so that the correct byte suze is now reported.

CR:589655

CR Number:   589655 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 2304 10 Sep 2009 Fixed Description No limit on the size of a CONTAINS query was imposed. The query length was not checked, and number of terms was not counted. This could have lead to queries that would have taken very long to execute, or to server crashes. This has been fixed. Now, a CONTAINS query cannot contain more than 300 valid terms (terms that are not in the STOPLIST and are within permitted term length range).

CR:589666

CR Number:   589666 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2314 14 Sep 2009 Fixed Description When converting NUMERIC values to a VARCHAR, the server could have truncated the results when the precision of the NUMERIC value exceeded 30. This has been fixed by changing the conversion to produce a VARCHAR with size 2 plus the precision of the source NUMERIC value.

CR:589762

CR Number:   589762 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 3961 11 Sep 2009 Fixed 9.0.2 3889 11 Sep 2009 Fixed Description The server would have crashed if the system functions db_property('LogFileFrangments') or sa_db_properties() were executed against the utility database. This has been fixed.

CR:589802

CR Number:   589802 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 2314 14 Sep 2009 Fixed 10.0.1 3961 14 Sep 2009 Fixed Description Applications would have been able to connect to a database using the database's alternate server name, and then create, stop, and drop other databases on the same server. This has been fixed, all of these operations are now disallowed when connected through an alternate server name.

CR:589821

CR Number:   589821 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2314 14 Sep 2009 Fixed Description If the remainder() function was used with DECIMAL arguments and the value of the second argument was zero, then NULL would have been returned and an error was not generated when the divide_by_zero_error option was set to On (the default value). This has been fixed.

CR:589829

CR Number:   589829 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 2314 14 Sep 2009 Fixed 11.0.0 1654 14 Sep 2009 Fixed Description Selecting the Data tab for either an invalid or disabled view, or a disabled or truncated materialized view, would have caused Sybase Central to crash when attempting to recompile and/or refresh the view. This has been fixed.

CR:589848

CR Number:   589848 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 2317 21 Sep 2009 Fixed Description SQL Anywhere server could have generated a spurious "cardinality violation" error when executing the MERGE statement if the statement being executed did not contain any WHEN MATCHED clauses, or none of the specified WHEN MATCHED clauses were unconditional, and there were at least two rows in the input data set that matched a single target row and don't qualify for any of the WHEN MATCHED clauses. This has been corrected so that the server will now silently ignore these duplicate rows instead of generating a cardinality violation error.

CR:590017

CR Number:   590017 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2314 16 Sep 2009 Fixed Description When converting NUMERIC values to a VARCHAR, the server could have truncated the results when the precision of the NUMERIC value exceeded 30. This has been fixed by changing the conversion to produce a VARCHAR with size 2 plus the precision of the source NUMERIC value.

CR:590020

CR Number:   590020 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2315 14 Sep 2009 Fixed Description When run on Unix systems, queries of the form "SELECT ... FROM directory_access_table WHERE file_name=...", where directory_access_table was a proxy table to a directory access server, would have returned an empty result set. This problem would only have occurred if the server had been updated to include the fix for Engineering case 569934. This problem has now been fixed and the server will now properly return a result set.

CR:590030

CR Number:   590030 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2315 15 Sep 2009 Fixed Description A new "OR REPLACE" clause can now be optionally specified in the CREATE SYNCHRONIZATION PROFILE statement. If this clause is present, and the profile named in the statement already exists, then it will be replaced. Otherwise, it will be created.

CR:590041

CR Number:   590041 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 2316 16 Sep 2009 Fixed 10.0.1 3963 16 Sep 2009 Fixed Description If query optimization with matching materialized views generated an error while processing a materialized view candidate, the error was still returned to the application. For example, if a materialized view candidate contained additional tables for which the user did not have SELECT permissions, the error "Permission denied: you do not have permission to select from "tablename" would have been returned. This has been fixed. Now, if an error is encountered while processing a materialized view candidate, the error is ignored and the view is not used in the view matching process.

CR:590045

CR Number:   590045 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2313 14 Sep 2009 Fixed Description When executing a SELECT DISTINCT query against a newly created table with no data, the runtime would have crashed with a NullPointerException. This has been fixed.

CR:590048

CR Number:   590048 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 15 Sep 2009 Fixed Description The "SYNCHRONIZE OFF" table constraint in a CREATE TABLE statement may have failed when the same statement had column defaults specified as well. For example, the statement "create table t ( id int primary key default autoincrement, c2 int, synchronize off)" would have crashed the runtime. This has been corrected.

CR:590061

CR Number:   590061 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2315 15 Sep 2009 Fixed Description If a MobiLink server had a connection from a MobiLink Monitor, or a SQL Anywhere Monitor, it could have hung while printing warning 10082, "MobiLink server has swapped data pages to disk ... ". This was due to a deadlock between the thread printing the warning and a thread sending a monitor event. This has been fixed.

CR:590098

CR Number:   590098 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2363 14 Dec 2009 Fixed Description A server crash could have occurred while running the Index Consultant. This has been fixed.

CR:590156

CR Number:   590156 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 2316 15 Sep 2009 Fixed 10.0.1 3962 15 Sep 2009 Fixed 9.0.2 3980 15 Sep 2009 Fixed Description The server may have incorrectly rewritten WHERE, ON, or HAVING clauses, causing no rows, or too few rows, to be returned. This would have happened when the server found redundant conjuncts and try to remove them. This has been fixed. A sample of this type of query: select 1 from T where a = 1 and ( b = 2 or c = 8 ) and ( d = 4 or e = 10 ) and ( a = 1 or e = 7 or c = 9 )

CR:590210

CR Number:   590210 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2316 17 Sep 2009 Fixed 11.0.0 1654 17 Sep 2009 Fixed 10.0.1 3963 17 Sep 2009 Fixed 9.0.2 3891 17 Sep 2009 Fixed Description The SQL Anywhere OLE DB provider implementation of IMultipleResults::GetResult() returned an incorrect 'rows affected' count for inserts, updates, and deletes. In this situation, the result returned by OleDbCommand.ExecuteNonQuery(), which called the GetResult() method, was -1. This problem has now been fixed to return the correct 'rows affected' count.

CR:590215

CR Number:   590215 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 2317 17 Sep 2009 Fixed Description Database corruption was possible in certain rare circumstances. This has been fixed.

CR:590243

CR Number:   590243 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.1 2316 16 Sep 2009 Fixed Description Sorting a list of messages on the "Messages" and "Archived Messages" tabs by the "Status Time" column, would not have sorted the messages correctly. The comparator for the date column had been based on the string representation of the date, rather than the date itself. This has been fixed.

CR:590374

CR Number:   590374 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2316 16 Sep 2009 Fixed Description Calling the QAManager.close() method, immediately after receiving a message asynchronously, could have caused the manager to hang indefinitely. This has been fixed

CR:590383

CR Number:   590383 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   6.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2316 16 Sep 2009 Fixed 11.0.0 1654 16 Sep 2009 Fixed 10.0.1 3963 16 Sep 2009 Fixed 9.0.2 3891 16 Sep 2009 Fixed Description On UNIX systems, there were directories left in the temporary directory, with names of the form __SQLAnyCli__X_Y, where X is a process number and Y is an alphanumeric number. This usually happened when a SQL Anywhere client application was terminated abnormally. An example of this was the PHP driver running within the Apache web server. This has been fixed.

CR:590401

CR Number:   590401 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 2316 17 Sep 2009 Fixed Description If an application used a JDBC based Remote Data Access class, and the application subsequently changed the setting for quoted_identifier or ansinull, then the new setting would not get sent to the remote server. This problem has now been fixed.

CR:590468

CR Number:   590468 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) 17 Sep 2009 Fixed Description When opening a database's ER Diagram tab and creating, modifying or deleting a table or foreign key, the ER Diagram would not have been updated automatically. The ER Diagram tab had to be manually refreshed via View -> Refresh Folder, or View -> Refresh All, in order to see the changes. Now the ER diagram is kept up-to-date automatically.

CR:590471

CR Number:   590471 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) 17 Sep 2009 Fixed Description When the set of tables shown in the ER Diagram was limited (by selecting File -> Choose ER Diagram Tables...), and then subsequently renaming one the tables that had been selected in the Choose ER Diagram Tables dialog, the table would then no longer have appeared in the ER Diagram. This has been fixed.

CR:590569

CR Number:   590569 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 2316 17 Sep 2009 Fixed Description Only users with DBA authority should be able to execute COMMENT ON DBSPACE statements, but the server was failing to check for this permission. This has been fixed. The server now ensures that the user has DBA authority before executing a COMMENT ON DBSPACE statement.

CR:590591

CR Number:   590591 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 3963 17 Sep 2009 Fixed Description If the server was started on Netware, and multiple connections that had made Java calls shut down at the same time, then there was a chance the server would have crashed. This problem has now been fixed.

CR:590602

CR Number:   590602 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 2317 21 Sep 2009 Fixed Description Executing a SQL statement, immediately followed by an OUTPUT statement and nothing else, would have cause an internal error if the "Show separate Messages pane" option was set on. This has been fixed.

CR:590607

CR Number:   590607 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2317 01 Oct 2009 Fixed Description Incorrect results may have been obtained for functions with a variable number of arguments, when NULL was specified as the first argument. This has been corrected.

CR:590633

CR Number:   590633 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2317 18 Sep 2009 Fixed Description Symbols from the Dbmlsync C++ API could pollute the user's default namespace. These symbols are now segregated into their own namespace named "DbmlsyncClient11". Existing Dbmlsync C++ API applications will still be able to compile without modification, since the dbmlsynccli.hpp header file now also includes "using namespace DbmlsyncClient11". Those wishing to exclude the USING command, and be forced to reference the symbols using the namespace, can define a macro called MULTIPLE_DBMLSYNC_API_VERSIONS in their source code.

CR:590692

CR Number:   590692 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2322 29 Sep 2009 Fixed 10.0.1 3968 29 Sep 2009 Fixed Description The server may have modified the wrong table when executing an UPDATE or DELETE on a view, if the view was specified in the FROM table-list as well. This has been fixed.

CR:590702

CR Number:   590702 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0.1 2321 29 Sep 2009 Fixed Description In some cases, executing query plans with a HashGroupBy and a Distinct could have required up to twice as much CPU time than necessary. This has been fixed. The presence of this issue can be identified by examining a graphical plan with statistics. If the estimated number of rows coming out of a HashGroupBy or a Distinct is small (less than 100), and the actual number of rows is large (many thousands or more), the hash operator may be operating less efficiently than possible. The performance penalty for a query suffering from this problem is unlikely to exceed 100% (i.e twice as slow).

CR:590803

CR Number:   590803 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2317 21 Sep 2009 Fixed Description When using the debugger in Sybase Central, sometimes a breakpoint was hit and the error "The source code could not be displayed for the <procedure/event/trigger> because the database filter is excluding it." was incorrectly shown. This has now been fixed.

CR:591001

CR Number:   591001 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2318 22 Sep 2009 Fixed 10.0.1 3965 22 Sep 2009 Fixed 9.0.2 3893 22 Sep 2009 Fixed Description In very rare circumstances, the server may have crashed when it should have returned the sql error SQLSTATE_SYNTACTIC_LIMIT. This may have occurred when loading very compley view definitions, or executing a SELECT INTO into table statement. This has been fixed.

CR:591002

CR Number:   591002 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.1 2321 21 Sep 2009 Fixed 11.0.0 1654 21 Sep 2009 Fixed 10.0.1 3968 21 Sep 2009 Fixed 9.0.2 3896 21 Sep 2009 Fixed Description The changes for Engineering case 582782 could have caused the MobiLink server to be much slower for small sync than servers without the fix. This problem would have occurred when a consolidated database was running on an Oracle RAC. The slowness is in the Oracle server: fetching the minimum starting time of the open transactions from gv$transaction can take as much as a couple of seconds and it is much slower than from v$transaction. This has now been corrected.

CR:591061

CR Number:   591061 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 2318 22 Sep 2009 Fixed 22 Sep 2009 Fixed 11.0.0 1654 22 Sep 2009 Fixed 10.0.1 3965 22 Sep 2009 Fixed Description If a database had a partial write to the checkpoint log, then it was possible that database recovery could have failed in a case which was actually recoverable. This only affected encrypted databases. This has now been fixed.

CR:591275

CR Number:   591275 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 2320 23 Sep 2009 Fixed Description The JDBC based Remote Data Access classes are generally not recommended due to their higher resource requirements and significantly lower performance, when compared to the ODBC based Remote Data Access classes. However, for those applications where an ODBC based Remote Data Access class is not an option, improvements have now been made to increase the performance of fetching results from a remote server using a JDBC based Remote Data Access class. Nevertheless, even with these performance improvements, the recommendation is still to use ODBC based Remote Data Access classes instead of the JDBC based classes whenever possible.

CR:591301

CR Number:   591301 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2329 09 Oct 2009 Fixed Description The server may have returned too many result rows if the query contained a DETWEEN predicate with constants, and a parallel index-only scan was used. This has been fixed.

CR:591546

CR Number:   591546 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 2334 13 Oct 2009 Fixed 10.0.1 3977 21 Oct 2009 Fixed Description When the server executed a CREATE VIEW statement, and the view's SELECT statement referenced a materialized view that was not yet initialized, the statement would have failed with the error "Cannot use materialized view 'viewname' because it has not yet been initialized". The script generated by dbunload -n could have failed trying to recompile views. This has been fixed.

CR:591824

CR Number:   591824 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.1 2320 24 Sep 2009 Fixed Description When running on Windows Vista, menu items that toggle a property on or off would not always have shown the check mark next to the menu item's text. Similarly, menu items that choose a value from a mutually exclusive set of values would not always show a sphere next to the currently selected value. Both of these problems have now been fixed.

CR:591832

CR Number:   591832 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2320 25 Sep 2009 Fixed 10.0.1 3966 25 Sep 2009 Fixed Description When using the debugger in the Sybase Central, a NullPointerException could have been thrown when leaving debugging mode. This would likely have occurred infrequently, but has now been fixed.

CR:591833

CR Number:   591833 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2325 02 Oct 2009 Fixed 11.0.0 1654 02 Oct 2009 Fixed 10.0.1 3969 02 Oct 2009 Fixed Description The ADO.NET provider could have failed to unpack and load dbdata.dll. A race condition has been fixed.

CR:591837

CR Number:   591837 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.0 2543 01 Jun 2010 Fixed 11.0.1 2443 01 Jun 2010 Fixed 10.0.1 4078 01 Jun 2010 Fixed 12.0.1 2928 15 Sep 2010 Fixed Description The Index Consultant in the Interactive SQL utility would have failed to process queries containing line-terminated comments (ie -- or //). This has been fixed. As a work around, removing the comments allowed the analysis to proceed.

CR:592018

CR Number:   592018 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2320 25 Sep 2009 Fixed Description It was possible for the Interactive SQL utility (dbisql) to have crashed when clicking the File/New menu item, or by pressing CTRL+N, when connected to a database and the contents of a file was being displayed. The problem was timing dependent, and was more pronounced the longer the database latency was. This has been fixed.

CR:592035

CR Number:   592035 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 2320 25 Sep 2009 Fixed Description Clicking the "Get Plan" button in the Plan Viewer window could have caused the Interavtive SQL utility to crash if it, or another Plan Viewer window, was executing a statement at that time. This has been fixed.

CR:592269

CR Number:   592269 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2321 28 Sep 2009 Fixed Description Very large dates or timestamp values, such as "9999-12-31", would not have synchronized. The synchronization would have failed, possibly due to the exception "UltraLiteJ Error[-85]: Communication error Unexpected end of file from server", and the MobiLink sync log may have shown an error like "[-10308] Upload data for column 15 of table 'SalesOrder_1_0_getlist' is invalid"; however the column identified was not the column causing the problem. It was also possible that no error was detected, but that subsequent columns may have been corrupted. This has been fixed.

CR:592421

CR Number:   592421 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2324 01 Oct 2009 Fixed Description Executing the utility SASetupAspNet.exe would have caused an unhandled exception "Could not load file or assembly iAnywhere.Data.SQLAnywhere" to be thrown. This problem has been fixed.

CR:592425

CR Number:   592425 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 2323 29 Sep 2009 Fixed Description When the server starts, the port numbers on which the server is listening are displayed on the console, but only if they were not supplied on the command line (using the -x tcpip(port=xxx) switch). This has been fixed - the port numbers are now always displayed.

CR:592454

CR Number:   592454 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2323 29 Sep 2009 Fixed Description If left running for a long time, there may be a gradual degradation in responsiveness of the SQL Anywhere Monitor. For this to have occurred, a SQL Anywhere resource would have had to be unavailable at the time the Monitor was started. The performance degradation would not normally have been noticeable until sufficient time had passed. There were no other visible symptoms of this problem.

CR:592467

CR Number:   592467 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 2325 01 Oct 2009 Fixed Description There was an arbitrary limit of 1000 on the number of messages which could be shown on the "Messages" or "Archive Messages" tabs for a message store. That limit has now been relaxed. If there is enough memory to display all the messages, they will be displayed. Under low memory conditions, only the last 1000 messages will be displayed, but a warning message will now be displayed in this case.

CR:592589

CR Number:   592589 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 2328 09 Oct 2009 Fixed 11.0.0 1654 09 Oct 2009 Fixed 10.0.1 3972 09 Oct 2009 Fixed Description Some computed bitstring values (i.e. those produced as a result of a set_bit, &, |, ^ or ~) might not have hashed properly. Operations that can hash bitstring values during their execution (for example, select distinct of a bit column) could have returned incorrect results. This has been fixed, but existing tables containing affected values will require an unload/reload. Alternatively, if c is an affected column in table t, "update t set c = ~c" can be run twice with a server containing the fix.

CR:592638

CR Number:   592638 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 11.0.1 2324 01 Oct 2009 Fixed Description Some DELETE operations may corrupted the database. This occurred when a row was deleted from a multi-level index which was sufficienly full that no index-page reduction was required, and no subsequent operations modified the database page in question. This has been fixed.