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

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

CR:675326

CR Number:   675326 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Windows CE 2.11 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3394 11 Jul 2011 Fixed 11.0.1 2634 11 Jul 2011 Fixed Description When run on a Windows Mobile device, the server could have crashed if the "Authentication parameters" field in an existing "SYNCHRONIZATION PROFILE" was modified. This has now been fixed.

CR:675363

CR Number:   675363 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3395 11 Jul 2011 Fixed 11.0.1 2634 11 Jul 2011 Fixed Description A null pointer exception was possible when a host variable occurred in the HAVING clause This was corrected.

CR:675496

CR Number:   675496 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) 12.0.1 3385 28 Jun 2011 Fixed 11.0.1 2628 28 Jun 2011 Fixed 10.0.1 4241 28 Jun 2011 Fixed Description Explicitly opening the Text Completer when the "SQL Statements" field contained only matching parentheses would have caused the Interactive SQL utility to crash. This has been fixed.

CR:675642

CR Number:   675642 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3387 30 Jun 2011 Fixed 11.0.1 2629 30 Jun 2011 Fixed Description Database corruption was possible when the UltraLiteJ Runtime was under row limitation stress (when the maximum and minimum row limitation values are close together). This has now been corrected.

CR:675686

CR Number:   675686 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) 12.0.1 3369 29 Jun 2011 Fixed 12.0.0 2693 29 Jun 2011 Fixed 11.0.1 2618 29 Jun 2011 Fixed 10.0.1 4241 29 Jun 2011 Fixed Description The server may have failed assertion 101412 - "Page number on pages does not match page requested", if the database/connection option 'chained' was set to 'off'. This has been fixed.

CR:675738

CR Number:   675738 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.1 3415 08 Aug 2011 Fixed 12.0.0 2720 08 Aug 2011 Fixed 11.0.1 2656 08 Aug 2011 Fixed Description Some statements, like CREATE TEXT INDEX and CREATE MATERIALIZED VIEW, record the current database option values that exist at the time the statement was executed in the transaction log. The server would have returned the assertion failure error 100904 - "Invalid option '<option-name>' -- no PUBLIC setting exists", if there was not public setting for one of these options during startup recovery, or when applying changes on a mirror server. This has been fixed.

CR:675805

CR Number:   675805 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3387 29 Jun 2011 Fixed 12.0.0 2703 29 Jun 2011 Fixed 11.0.1 2629 29 Jun 2011 Fixed Description It is possible, although rare, for the machine.config file to contain multiple registered SQL Anywhere ADO.NET providers. When unregistering, the SetupVSPackage.exe utility only removed one SQL Anywhere ADO.NET provider from the machine.config file. This problem has been fixed so that SetupVSPackage.exe now looks for all registered SQL Anywhere ADO.NET providers.

CR:675894

CR Number:   675894 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) 12.0.1 3387 30 Jun 2011 Fixed 11.0.1 2629 30 Jun 2011 Fixed Description In Sybase Central, you can generate HTML documentation for a database to which you are connected. That documentation includes cross-reference information for stored procedures -- a list of procedures a given procedure calls, and a list of the procedures which call the given procedure. This cross-reference information was not being generated for those stored procedures which used the Transact SQL dialect. Cross-reference information for procedures which used the SQL Anywhere dialect were generated fine. This has been fixed so that cross-reference information is generated for stored procedures that are written using either dialect.

CR:676007

CR Number:   676007 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) 12.0.1 3388 04 Jul 2011 Fixed 12.0.0 2703 04 Jul 2011 Fixed 11.0.1 2630 04 Jul 2011 Fixed 10.0.1 4241 04 Jul 2011 Fixed Description The server would have failed to rename the request log correctly if the option RequestLogNumFiles was set to 1. This has been fixed.

CR:676015

CR Number:   676015 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3392 07 Jul 2011 Fixed 12.0.0 2706 07 Jul 2011 Fixed Description Queries involving spatial predicates over an indexed geometry column may have failed to select a plan that used the spatial index if the table was very large (several gigabytes at least). This has been fixed.

CR:676033

CR Number:   676033 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3388 04 Jul 2011 Fixed Description When a statement cannot be executed by the Interactive SQL utility, the error is displayed in an error window. That window contains a "Help" button which, which clicked, can display a menu of relevant help topics (for the error message and for the type of statement being executed). Opening this error window could have taken a non-trivial amount of time if the online documentation for SQL Anywhere was not installed. In those cases, the software had to check with the DocComment Exchange (DCX) server to see if help was available for the statement in question. While the Interactive SQL utility is doing this check, it could be unresponsive. The problem was most acute on machines that were not connected to the internet at all. This has been fixed so that the error dialog opens without delay, and Interactive SQL remains responsive at all times. Workaround Description  You can use ISQLC instead of ISQL, or simply install the local documentation.

CR:676069

CR Number:   676069 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3388 04 Jul 2011 Fixed 11.0.1 2631 04 Jul 2011 Fixed Description The UltraLiteJ Database Unload utility (uljunload) did not allow specifying the page size on a new databases. A new flag -z has been added to uljunload to specify the page size in bytes.

CR:676092

CR Number:   676092 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3483 05 Jul 2011 Fixed 11.0.1 2630 21 Oct 2011 Fixed Description During download deletes, index pages were not being flushed. This has been fixed. Other changes have been made as well to reuse Java objects and reduce the creation of temporary objects during the download. These changes were made to improve memory useage during synchronization.

CR:676102

CR Number:   676102 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) 12.0.1 3488 28 Oct 2011 Fixed 11.0.1 2702 28 Oct 2011 Fixed Description Inserting Unicode strings into a database using an MBCS/ANSI encoding (that is, not UTF-8) could have resulted in corruption of the strings and possibly unbounded store growth. Unicode strings are inserted using the wchar methods in the C++ API, or using .NET. The Unicode conversion routines to and from wchar were not correct and have been fixed.

CR:676210

CR Number:   676210 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) 12.0.1 3396 12 Jul 2011 Fixed 11.0.1 2642 20 Jul 2011 Fixed 10.0.1 4249 20 Jul 2011 Fixed Description Execution of a SET REMOTE OPTION would have failed if the value of the setting was larger then 256 bytes. This was due to the schema of the ISYSREMOTEOPTION table which has a 255 byte limit on the length of the settings column. The server has been changed to provide a more appropriate error message.

CR:676224

CR Number:   676224 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3409 28 Jul 2011 Fixed 11.0.1 2649 28 Jul 2011 Fixed Description If a database had a publication defined using the "download only" or "scripted upload" clauses, but had not defined any synchronization users or synchronization subscriptions, then when a dbunload was run on the database, the "download only" or "scripted upload" clauses of the publication would not have been maintained. This problem has been fixed. A workaround to this issue would be to add any synchronization user or synchronization subscriptions to the database. For example, if a publication "p1" was defined for download only, execute "CREATE SYNCHRONIZATION SUBSCRIPTION TO p1 TYPE 'tcpip'". This would define TCP/IP as the default communication type when synchronizing the publication, which is the default that would be chosen anyway.

CR:676332

CR Number:   676332 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 2633 07 Jul 2011 Fixed Description UPDATE statements with complex table expressions may have caused a server crash. At least the following conditions must have been true: 1. The UPDATE statement is using the syntax: UPDATE [ row-limitation ] table-expression [, ...] ] SET set-item[, ...] [ WHERE search-condition ] [ ORDER BY expression [ ASC | DESC ] , ...] [ OPTION( query-hint, ... ) ] 2. The statement must have had at least two query blocks (e.g., a derived table, subselect, subqueries). 3. The 'table expression' contained a Left Outer Join at the root of the tree 4. The Left Outer Join was a redundant join. Removing the Left Outer Join from the original statement generates an equivalent statement. This has been fixed. For example: update LP join PR on PR.PR1 = LP.LP1 join LS on LS.LS2 = PR.PR2 join SC on SC.SC1 = LS.LS2 left outer join PC on PC.PC1 = LS.LS1 set LP.LP2 = LS.LS1 where PR.PR3 = 10 and LS.LS3 = 20 and SC.SC2 = 30 and SC.SC2 = (select max(id) from product )

CR:676340

CR Number:   676340 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.1 3419 12 Aug 2011 Fixed 11.0.1 2658 12 Aug 2011 Fixed 10.0.1 4258 12 Aug 2011 Fixed Description The database server could have taken longer than expected to perform a backup. During such a backup other database requests may have appeared to stall, and connections to the server may also have been impacted. This should only have occurred if the total size of database files was larger than 5 GB. This has been fixed.

CR:676363

CR Number:   676363 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3415 09 Aug 2011 Fixed 12.0.0 2720 09 Aug 2011 Fixed 11.0.1 2656 09 Aug 2011 Fixed Description When attempting to use Sybase Central to create a proxy table for an Access database, and the remote server used the 'MSACCESSODBC' server class, the following error would have been displayed: [Sybase][ODBC Driver][Adaptive Server Anywhere]Server '<server-name>': [Microsoft][ODBC Driver Manager] Driver does not support this function (-660) A call was being made to SQLPrimaryKeys() to determine which columns in the table belong to the primary key. Access does not support this function, so this error is now ignored for the 'MSACCESSODBC' server class.

CR:676364

CR Number:   676364 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3390 05 Jul 2011 Fixed Description The version of zlib used by the SQL Anywhere and MobiLink clients and servers contained security vulnerabilities documented under US CERT Vulnerability notes VU#680620 and VU#238678. These are fixed in zlib version 1.2.3. SQL Anywhere and MobiLink clients and servers now use zlib version 1.2.5. Links: http://www.kb.cert.org/vuls/id/680620 http://www.kb.cert.org/vuls/id/238678

CR:676495

CR Number:   676495 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3391 05 Jul 2011 Fixed Description 1. A copy node can now act as an arbiter for the database it is copying in a high-availability system with mirroring. The arbiter and both partners must be running the updated software to take advantage of this change. As before, a partner cannot act as arbiter for its own database. When defining the arbiter to refer to a copy node, use an arbitrary mirror server name for the arbiter that does not match the server name of any of the database servers in the HA system. The name of the arbiter mirror server isn't actually used for connecting. For example: CREATE MIRROR SERVER "scaleout_child" AS COPY connection_string = 'server=scaleout_child;host=winxp-2:6878'; CREATE MIRROR SERVER "TheArbiter" AS ARBITER connection_string = 'server=scaleout_child;host=winxp-2:6878'; Note that there is no database server in the HA system that is running with the server name "TheArbiter": it is just being used as a placeholder in the mirror server definitions to hold the connection string for the arbiter. 2. Copy nodes could have reported a log mismatch error in certain cases involving a failure of both the primary server and the arbiter. This problem has been fixed. 3. There was a race condition that could have allowed an arbiter server to create two separate internal states for the same mirroring system. This problem has been fixed.

CR:676505

CR Number:   676505 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3391 06 Jul 2011 Fixed 12.0.0 2705 06 Jul 2011 Fixed Description Under rare, timing dependent conditions, the Relay Server may have reported a fatal error "RSF11016: Freeing already freed memory block in shared memory". The Relay Server's shared memory manager would have protected itself from this illegal operation and continued to operate normally. This error may have occurred right after RSE2000, RSE3008 or Relay Server shutdown. This has been fixed by eliminating the redundant freeing.

CR:676664

CR Number:   676664 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3392 06 Jul 2011 Fixed Description After the changes for Engineering case 661663, passing an invalid certificate to a web procedure (i.e. CREATE FUNCTION ... URL '...' CERTIFICATE '...') may have caused the server to crash when the procedure was executed. This has been fixed.

CR:676668

CR Number:   676668 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3505 18 Nov 2011 Fixed Description Values in long binary and long varchar columns may have become corrupted when used in temporary tables. This may have manifested itself as incorrect values read, or ArrayIndexOutOfBounds exceptions, when values were read or when rows containing these values are deleted or updated. This has been fixed.

CR:676727

CR Number:   676727 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3405 25 Jul 2011 Fixed 11.0.1 2645 25 Jul 2011 Fixed Description When editing a TIMESTAMP column value in the "Results" panel, the editor did not distinguish between AM and PM, always assuming AM. This has been corrected so that the editor now distinguishes between the two.

CR:676844

CR Number:   676844 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3400 18 Jul 2011 Fixed 12.0.0 2710 18 Jul 2011 Fixed 11.0.1 2638 18 Jul 2011 Fixed Description Attempting to perform an unload with reload of a database, using the Unload utility or the dbtools DBUnload function, may have failed with a "Cannot find index named ...' error if the index had a comment. This problem has now been fixed.

CR:676996

CR Number:   676996 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 2640 19 Jul 2011 Fixed 11.0.1 4249 19 Jul 2011 Fixed Description The database server, running a database in read-only mode, could have crashed during database validation. This would only have occurred in very rare circumstances. This has been fixed.

CR:677104

CR Number:   677104 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3393 11 Jul 2011 Fixed Description Current login policy allowed putting a restriction over the number of failed login attempts a user can make before the user's account is locked. However, this restriction did not apply to users with DBA authority. Regardless of the number of failed login attempts, a DBA user was always allowed to login if correct credentials are provided. This made DBA accounts vulnerable to brute force attacks. This has been changed with the new option, max_failed_login_attempts. The value of this option is also applied to users with DBA authority. However, to prevent complete database lock down, an automatic unlock time of 1 minute is also applied. At the time of database restart, a DBA user will also be allowed to make one failed login attempt, regardless of the number of failed login attempts stored in the catalog.

CR:677165

CR Number:   677165 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3412 03 Aug 2011 Fixed 11.0.1 2653 03 Aug 2011 Fixed Description In specific circumstances, it was possible for the server to fail assertion 101519. This has been fixed.

CR:677251

CR Number:   677251 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3402 13 Jul 2011 Fixed 12.0.0 2711 13 Jul 2011 Fixed 11.0.1 2639 13 Jul 2011 Fixed Description If an embedded SQL application or a stored procedure first opened a READ ONLY cursor on a simple SELECT query qualifying for optimizer bypass, and later opened an UPDATE cursor for the same query, a positioned update to the second cursor could have failed with SQLCODE -192 ("Update operation attempted on non-updatable query"). This has been fixed. For the error to occur in version 11, the first cursor would need to be explicitly declared FOR READ ONLY, because FOR UPDATE is the default (c.f. documentation for DECLARE CURSOR statement). In version 12.0.0 and later, cursor updatability depends upon cursor type (c.f. documentation for SELECT and PREPARE statements) but defaults to FOR READ ONLY for ESQL.

CR:677327

CR Number:   677327 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.1 3399 15 Jul 2011 Fixed 11.0.1 2637 15 Jul 2011 Fixed Description In some cases, SQL Anywhere HTTP procedures and the HTTP server would have failed to process received chunked mode transfer encoded data when the chunk length meta-data contained leading zeros. This has been fixed.

CR:677430

CR Number:   677430 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3408 28 Jul 2011 Fixed 12.0.0 2715 28 Jul 2011 Fixed 11.0.1 2648 28 Jul 2011 Fixed Description In extremely rare cases, inserting data into a compressed column that had a blob index may have resulted in the blob index becoming corrupt. This could have resulted in assertion failures if the data was accessed randomly (i.e. using substr(), right(), or similar), and would also have resulted in validation failures. This has been fixed. Note: existing corrupted blob indexes must be dropped and recreated after the fix is applied. This can be done using: alter table <table> alter <column> no index alter table <table> alter <column> index

CR:677515

CR Number:   677515 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3402 22 Jul 2011 Fixed 11.0.1 2639 22 Jul 2011 Fixed Description Running REORGANIZE TABLE on a table with foreign key indexes when the database was under heavy update/delete load, had a chance of corrupting the table. Specifically, the indexes on the table would have contained more values then the table itself. This has been fixed.

CR:677803

CR Number:   677803 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) 12.0.1 3400 18 Jul 2011 Fixed Description If an invalid certificate was encountered by the server running on the Mac, the error reported may have been "Error parsing certificate file, error code 0". This has been fixed, the error code should have been non-zero if an error occurred. Note, this problem also affected SQL Anywhere clients running on the Mac.

CR:677867

CR Number:   677867 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3401 19 Jul 2011 Fixed Description Null values retrieved with ResultSet.getString( col_no ) were returned as an empty string. This has been fixed. Now, null values are retrieved as null with this method.

CR:677962

CR Number:   677962 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) 12.0.1 3401 19 Jul 2011 Fixed 11.0.1 2638 19 Jul 2011 Fixed Description When a database was shut down (for example, as part of server shutdown) and the database was a high availability mirror or a read-only scale-out copy node, the server could have hung in rare timing dependent cases. If the server was hung due to this problem, there would have been messages like the following in the server console: A write failed with error code: (6), The handle is invalid. Fatal error: disk full when writing to "???" This has been fixed.

CR:677966

CR Number:   677966 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 2638 18 Jul 2011 Fixed Description Applications with small row limits (due to tables with a lot of columns), many indexes, or large downloads, may have experienced an ArrayIndexOutOfBounds or ULjException with error code SQLE_ERROR. This has been fixed.

CR:678117

CR Number:   678117 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) 12.0.1 3412 08 Aug 2011 Fixed Description Under rare circumstances, the database server could have crashed or failed an assertion while running diagnostic tracing on a database where a large number of procedures, user-defined functions, triggers or events are being invoked. This has been fixed.

CR:678144

CR Number:   678144 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 2643 21 Jul 2011 Fixed Description A high availability partner server that was under heavy load could have hang when a thread deadlock occurred. This has been fixed so that a request will now receive the error: "All threads are blocked".

CR:678259

CR Number:   678259 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) 12.0.1 3403 20 Jul 2011 Fixed 11.0.1 2643 20 Jul 2011 Fixed Description A SQL Anywhere http procedure call may, on rare occasions, have caused the server to crash. This has been fixed.

CR:678597

CR Number:   678597 Product Name:   SQL Remote for SQL Anywhere Product Component:   SQL Remote for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3405 25 Jul 2011 Fixed 11.0.1 2645 25 Jul 2011 Fixed Description When running in a continuous mode, SQL Remote would have leaked about 10 kilobytes of memory in every attempt of sending messages to its subscribers. This problem has now been fixed.

CR:678600

CR Number:   678600 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 2644 22 Jul 2011 Fixed 12.0.1 3484 24 Oct 2011 Fixed Description When downloading rows with multiple LONG BINARY or LONG VARCHAR columns, they may have been corrupted when earlier clob/blob columns were null. This could have then resulted in a variety of errors including reading random values. For example, if a table was defined as: CREATE TABLE t( c1 INT PRIMARY KEY, c2 LONG VARCHAR, c3 LONG VARCHAR ) and the row[ 1, null, 'b' ] was downloaded, reading c3 would have failed. Rows [2, 'a', 'b'], [3, 'a', null ] and [4, null, null ] would have been okay. This has been fixed.

CR:678780

CR Number:   678780 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 2645 25 Jul 2011 Fixed Description Under heavy row limiting (i.e. large tables, many indexes, or many columns), complex queries involving temp tables may have resulted in a NullPointer Exception. This has been fixed.

CR:678806

CR Number:   678806 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3418 26 Jul 2011 Fixed Description The ENCRYPTED KEY '<key>' clause is now supported in the openstring OPTIONS clause. This is useful for reading in files created using UNLOAD with the ENCRYPTED clause.

CR:678817

CR Number:   678817 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) 12.0.1 3407 27 Jul 2011 Fixed Description A canceled SQL Anywhere HTTP client procedure may, on rare occasions, hang the server. This has been fixed.

CR:678942

CR Number:   678942 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) 12.0.1 3410 03 Aug 2011 Fixed 12.0.0 2717 03 Aug 2011 Fixed 11.0.1 2651 03 Aug 2011 Fixed Description There was a small chance that some statistics could have been reported incorrectly if parallel plans were used. Statistics affected include lock count, and the various io counts. This has been fixed.

CR:678983

CR Number:   678983 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3423 19 Aug 2011 Fixed 12.0.0 2724 19 Aug 2011 Fixed 11.0.1 2662 19 Aug 2011 Fixed Description The MobiLink server could have crashed when synchronizing using HTTP. This has been fixed.

CR:679160

CR Number:   679160 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) 27 Jul 2011 Fixed Description Invoking the SQLDIALECT function can cause server failure under specific, and unlikely, situations. The problem has now been resolved.

CR:679296

CR Number:   679296 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3464 29 Sep 2011 Fixed Description With UltraLiteJ for Android, synchronization with HTTP and E2EE was not possible because the methods setE2eePublicKey() and getE2eePublicKey() were members of the class StreamHTTPSParms. This has been fixed by moving the methods to the base class, StreamHTTPParms.

CR:679356

CR Number:   679356 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3474 12 Oct 2011 Fixed Description When the Relay Server state manager was started with the -os command line option, and the Relay Server extension was published using a user account without write permission of the folder that contained the log file, then auto truncation of the log when the size limit was reached may have failed on IIS7.x with a RSF11013 error where the underlying reason was system error 5 (Access is denied). This issue has been fixed.

CR:679370

CR Number:   679370 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3413 08 Aug 2011 Fixed Description If an application had a proxy procedure defined with an INOUT or OUT parameter of type [n][var]char(m), then calling that proxy procedure would have caused a server crash if the remote returned a value for that parameter that was the full m characters long. This problem has now been fixed.

CR:679403

CR Number:   679403 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3409 29 Jul 2011 Fixed Description Calling ResultSet.getString(i) when column i was of type INT, SMALLINT, UNSIGNED SMALLINT, BIGINT, NUMERIC, REAL or DOUBLE, would have thrown a ULjException with code SQLE_VALUE_IS_NULL when the column value was NULL. This has been fixed so that ResultSet.getString() now returns null in this case.

CR:679408

CR Number:   679408 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3409 02 Aug 2011 Fixed Description If a connection exists on the mirror server (ie, not the primary) when a failover occurs, that connection will persist while that partner becomes the primary. Database operations then performed by that connection (including certain temp-table operations which are valid from read-only connections) could have caused errors or crashes on other servers in the mirroring / HA system. This problem has been fixed.

CR:679415

CR Number:   679415 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3409 29 Jul 2011 Fixed Description Reloading a database that contained a table that referenced a sequence could have failed. This has been fixed. As a work around, the "Create sequences" section could be manually moved to before the "Create tables" section in the reload.sql file.

CR:679436

CR Number:   679436 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3409 29 Jul 2011 Fixed Description After returning false from the SyncProgressed method, or calling CancelSynchronize to cancel a synchronization, it was possible that the Synchronize or EndSynchronize call would have hung. This has been fixed. Also, the ULSyncProgressData.FLAG_IS_BLOCKING flag could have been set erroneously when the state was ULSyncProgressData.STATE_CANCELLED. This too has been fixed.

CR:679580

CR Number:   679580 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) 12.0.1 3410 29 Jul 2011 Fixed 12.0.0 2716 29 Jul 2011 Fixed 11.0.1 2649 29 Jul 2011 Fixed 10.0.1 4253 29 Jul 2011 Fixed Description The server could have crashed if a table was being dropped at the same time as a virtual table was being created. This has been fixed.

CR:679605

CR Number:   679605 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3410 02 Aug 2011 Fixed Description When a geometry had multiple polygons configured in a particular way, the Union of that geometry with another polygon, which was also configured in a particular way, would have caused a 'ring not closed' error. A simple example of a query that demonstrates this error is: select ST_Geometry::ST_GeomFromText( 'MultiPolygon( ( ( -10 -10, -11 -10, -11 -11, -10 -11, -10 -10 ) ), ( ( 2 2, 2.5 1, 1 1, 1 2, 0 2, 0 0, 3 0, 3 2, 2 2 ) ) )' ).ST_Union( ST_Geometry::ST_GeomFromText( 'Polygon( ( 1 1, 2.5 1, 2 2, 1 2, 1 1 ) )' ) ) The only work around is to break up the MultiPolygon and perform the unions in a different order. This has been fixed.

CR:679803

CR Number:   679803 Product Name:   SQL Remote for SQL Anywhere Product Component:   Ftp Messaging for Adaptive Server Anywhere Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3411 04 Aug 2011 Fixed 11.0.1 2652 04 Aug 2011 Fixed Description SQL Remote would have generated the following error message: "The address given is invalid. The address must be a directory name with no path separators." and then aborted the message receiving thread when it was able to retrieve all the names of the message files in the given directory from a FTP server, but for some reasons (such as network problems) was not able to retrieve the contents of a file from the server. This problem is fixed so that the error message is now: "Unable to retrieve message file 'xxxx' from the FTP server."

CR:680025

CR Number:   680025 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3411 02 Aug 2011 Fixed Description If a database had one or more ODBC based remote servers that used the new "driver=SQL Anywhere Native" feature, and if more than one connection attempted to establish a remote connection using these remote server definitions, and if no other connection had previously established a remote server definition using one of these remote server definitions, then there was a very small chance that the server would have crashed on exit. This problem has now been fixed.

CR:680034

CR Number:   680034 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 2652 03 Aug 2011 Fixed Description In a heavy indexing environment (many rows * many cursors with small row limiting values, and small cache size relative to number of index pages in the database), after a synchronization with several open cursors and containing download deletes, subsequent deletes or updates may have resulted in SQLE_ERRORs or NullPointerExceptions. These have been fixed.

CR:680036

CR Number:   680036 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 2652 03 Aug 2011 Fixed 12.0.1 3484 24 Oct 2011 Fixed Description In a heavy indexing environment (many rows * many cursors with small row limiting values and small cache size relative to number of index pages in the database), a synchronization of many download deletes may have become stuck while committing the download. Sometimes, on the BlackBerry OS it would have caused a system wide ForcedStackTrace exception. These have been fixed.

CR:680039

CR Number:   680039 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3411 03 Aug 2011 Fixed 11.0.1 2701 26 Oct 2011 Fixed Description A memory leak could have occurred when using the SQL Anywhere ODBC driver in such a way that the driver was repeatedly loaded and unloaded by the Microsoft ODBC Driver Manager on Windows Vista and Windows 7. This could have occurred when repeatedly creating and subsequently freeing the ODBC Environment as part of calling the SQL Anywhere ODBC driver. This problem occurs under Windows Vista and Windows 7 only as a result of a bug in Microsoft's SHELL32.DLL for these two operating systems. An Activation Context object is leaked on each load of the DLL. A workaround has been developed to avoid the problem. Another way to avoid the problem is to create and destroy the ODBC Environment only once in an application and connect/disconnect as often as desired. SQLAllocHandle( SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv ); SQLSetEnvAttr( henv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0 ); loop connect/disconnect many times endloop SQLFreeHandle( SQL_HANDLE_ENV, henv ); Note, Microsoft has published http://support.microsoft.com/kb/2624911, which describes the problem with Windows Vista and Windows 7.

CR:680180

CR Number:   680180 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3418 12 Aug 2011 Fixed Description Conversions between Date and Time datatypes during direct computation would fail in versions 11.0 and earlier, but in version 12.0, this conversion did not fail. This has been fixed so conversions between dates and times in version 12.0 will now also fail, as these conversions are invalid.

CR:680183

CR Number:   680183 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) 12.0.1 3412 04 Aug 2011 Fixed 12.0.0 2718 04 Aug 2011 Fixed 11.0.1 2653 04 Aug 2011 Fixed Description In rare timing-dependent cases, a multi-threaded client application that made simultaneous connection attempts from different threads may have crashed. This has been fixed.

CR:680196

CR Number:   680196 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) 12.0.1 3412 08 Aug 2011 Fixed 12.0.0 2718 08 Aug 2011 Fixed 11.0.1 2654 08 Aug 2011 Fixed 10.0.1 4255 08 Aug 2011 Fixed Description An application that connected using jConnect version 7 would have found that certain DatabaseMetaData calls returned incorrect results or unexpected errors. These metadata problems have now been corrected. Note that a database upgrade is needed in order to get this fix.

CR:680218

CR Number:   680218 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3412 04 Aug 2011 Fixed Description Calling ULConnection.SetSyncListener would have internally launched a thread that would never terminate. This could have prevented Windows Mobile applications from completely shutting down. This has been fixed.

CR:680231

CR Number:   680231 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3478 04 Aug 2011 Fixed 11.0.1 2653 19 Oct 2011 Fixed Description Databases which are accessed with row limiting enabled (see ConfigPersistent.setRowMinimumThreshold and setRowMaximumThreshold) will now always lazy load indexes.

CR:680242

CR Number:   680242 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3446 08 Sep 2011 Fixed Description Procedures with a SELECT statement that called another procedure may have become slower over time. This happened when the SELECT statement generating the result of the inner procedure qualified for a certain type of caching. This has now been fixed. A workaround is to ensure that the SELECT statement inside the inner procedure is not subject to simple query caching. If this slowdown is observed, the workaround can be implemented by adding a predicate that is not a tautology, but which is always known to be true for the data, to the inner select. For example, if a certain column is always greater than zero, adding the predicate col >= 0 is sufficient to avoid the problem. Note that simple predicates such as 1=1 will be detected as data-independent tautologies and removed.

CR:680348

CR Number:   680348 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3413 08 Aug 2011 Fixed Description When the Text Completer completes a table, view, or procedure name, the owner name is now added if the name would be ambiguous without it. Previously, the owner name could have been added when it wasn't necessary. This has been fixed.

CR:680569

CR Number:   680569 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3417 10 Aug 2011 Fixed Description When run on Unix systems, the system procedure xp_startsmtp(), which Starts an email session under SMTP, would have hung when called with a non-null "trusted_certificates" argument. This has been fixed.

CR:680578

CR Number:   680578 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3415 08 Aug 2011 Fixed 11.0.1 2654 08 Aug 2011 Fixed Description If a table had many rows with the same index value (all columns for a given index were the same), updates and deletes could have been slow. The performance decreased as the number of non-unique indexes with poor value distribution on a given table increased. This has been fixed.

CR:680726

CR Number:   680726 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) 12.0.1 3417 09 Aug 2011 Fixed 12.0.0 2721 09 Aug 2011 Fixed 11.0.1 2657 09 Aug 2011 Fixed Description If a server identity file with an unencrypted private key was provided to the server, the server would have refused to use it, reporting "Error parsing certificate file, error code 4113". This has been fixed. Note that this problem would not be seen on Mac OS X systems.

CR:680755

CR Number:   680755 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3415 08 Aug 2011 Fixed 12.0.0 2720 08 Aug 2011 Fixed 11.0.1 2656 08 Aug 2011 Fixed Description Sybase Central could have crashed when selecting a global temporary table in the tree, then selecting the Data tab in the right-pane and attempting to insert a row into the table. The crash would only have occurred if the table's commit action was DELETE ROWS. This has been fixed so that the Data tab is no longer shown for a GLOBAL TEMPORARY table unless its data is SHARE BY ALL.

CR:680760

CR Number:   680760 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) 12.0.1 3415 10 Aug 2011 Fixed 12.0.0 2720 10 Aug 2011 Fixed 11.0.1 2656 10 Aug 2011 Fixed Description When viewing extended options for a synchronization profile, publication, MobiLink user, or synchronization subscription, the values for the MobiLinkPwd and NewMobiLinkPwd extended options could have been seen in plain text from their tooltips. Now, no tooltips are shown for these values.

CR:680766

CR Number:   680766 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3456 01 Sep 2011 Fixed Description Execution of a CREATE OR REPLACE SEQUENCE statement would have failed with the error "Sequence <sequence name> already exists" if the sequence already existed. This has been fixed. The workaround is to manually drop the sequence before issuing the CREATE statement.

CR:680767

CR Number:   680767 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3447 09 Sep 2011 Fixed 11.0.1 2674 09 Sep 2011 Fixed Description When unloading a database, incorrect CREATE TEXT CONFIGURATION of external term breakers and prefilters were being generated in the reload,sql file. This has been fixed.

CR:680769

CR Number:   680769 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3450 09 Sep 2011 Fixed Description When unloading a database, SEQUENCE generator comments were not included in the reload.sql file. This has been fixed.

CR:680770

CR Number:   680770 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3449 12 Sep 2011 Fixed 11.0.1 2676 12 Sep 2011 Fixed Description When unloading a database, GRANT INTEGRATED/KERBEROS statements containing square brackets were written in the reload.sql file. These statements would have would have generated an 'unexpected statement' error when executed. This has been fixed by always putting double quotes rather than square brackets around the user identifier.

CR:680779

CR Number:   680779 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3446 07 Sep 2011 Fixed 11.0.1 2673 07 Sep 2011 Fixed Description When unloading a database, the ALTER TABLE statement to generate unique constraints in the reload.sql file did not include the CLUSTERED keyword for clustered unique constraints. This has now been corrected.

CR:680917

CR Number:   680917 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) 12.0.1 3418 10 Aug 2011 Fixed 11.0.1 2658 10 Aug 2011 Fixed Description Interactive SQL contains a number of menu items for selecting the current, previous, and next statements. These menu items could hale selected more than just the statement text, or could have selected nothing at all if the statement being selected included the text "IF NOT EXISTS". For example: CREATE TABLE IF NOT EXISTS t ( c INT PRIMARY KEY ) This has been fixed. Now, statements are selected properly. This same problem also affected the behavior of the "Single Step" menu item which also relies on being able to select the next statement.

CR:680920

CR Number:   680920 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3416 10 Aug 2011 Fixed 12.0.0 2720 10 Aug 2011 Fixed 11.0.1 2657 10 Aug 2011 Fixed Description The ISS Application Pool Process (w3wp.exe) may have crashed some time later after handling a request with a URL ending with the Relay Server extension.

CR:681055

CR Number:   681055 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3423 18 Aug 2011 Fixed Description When setting the MobiLink client network protocol options for an Agent, it was not possible to specificy a certificate file name if that name contained any of the following characters: "!@#%^&()+-_". Attempting to do so would have resulted in an error message saying there was a syntax error in the protocol options. This message was incorrectly being display, and is now not shown.

CR:681059

CR Number:   681059 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3417 10 Aug 2011 Fixed 12.0.0 2721 10 Aug 2011 Fixed 11.0.1 2657 10 Aug 2011 Fixed Description The usage text for the Relay Server Outbound Enabler was incorrectly listing 'identity_name' as a value for the -cr option. The value 'identity_name' has now been removed .

CR:681078

CR Number:   681078 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3417 10 Aug 2011 Fixed 12.0.0 2721 10 Aug 2011 Fixed 11.0.1 2657 10 Aug 2011 Fixed Description TLS and HTTPS synchronization would have failed when the client attempted to use a client-side identity with an unencrypted private key. The error reported would have been: "Unable to read the private key". This has now been fixed.

CR:681081

CR Number:   681081 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3423 18 Aug 2011 Fixed Description The connection string an agent uses to connect to a given remote database can be changed by selecting the agent, then selecting a database on the "Managed Remote Databases" panel and clicking the "Set Connection String" menu. If the "Cancel" button was clicked on the resulting window, the changes were made permanent, as if "OK" had been clicked instead. This has been corrected so that the changes in the dialog are discarded when "Cancel" is clicked.

CR:681082

CR Number:   681082 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3507 23 Nov 2011 Fixed Description If deployment of a synchronization model to a consolidated database stopped progressing because another database connection was blocking it, clicking Cancel would have caused Sybase Central to become unresponsive, even after the blocking from the other connection ended. This has been fixed.

CR:681088

CR Number:   681088 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 2661 18 Aug 2011 Fixed Description Memory usage for large downloads containing both deletes and/or updates has been improved, particularly in respect to the number of object handles used on BlackBerry devices. Downloads that delete or update tables with many columns will benefit most from this new algorithm. Note, row limiting is required to make use of this improvement.

CR:681396

CR Number:   681396 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   HP-UX Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3425 12 Aug 2011 Fixed 12.0.0 2726 12 Aug 2011 Fixed 11.0.1 2664 12 Aug 2011 Fixed Description If an Unix machine had many network interfaces (hard to say how many), starting the server may have failed. The only error message displayed was "TCPIP communication link not started". This has been fixed.

CR:681398

CR Number:   681398 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.1 3422 17 Aug 2011 Fixed 11.0.1 2661 17 Aug 2011 Fixed Description The server could have crashed while using the UNLOAD statement to unload data with 'APPEND ON' to a file if that file was also being deleted by some other process. This has been fixed

CR:681404

CR Number:   681404 Product Name:   MobiLink Product Component:   Streams Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3419 15 Aug 2011 Fixed Description A MobiLink client doing an HTTPS synchronization could have crashed if the connection was lost. This has been fixed.

CR:681419

CR Number:   681419 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3422 26 Sep 2011 Fixed 11.0.1 2662 26 Sep 2011 Fixed 10.0.1 4261 26 Sep 2011 Fixed 9.0.2 4034 26 Sep 2011 Fixed Description Multi-threaded OLEDB applications could have experienced an access violation when a rowset was released. This problem was introduced by the changes made for Engineering case 662896 and has now been fixed.

CR:681424

CR Number:   681424 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3419 15 Aug 2011 Fixed Description On Windows Mobile devices, calling GetStringLength(), on a ULValue returned from any of the schema methods in ulcpp11.cpp, could have returned 0 even if it was a valid non-zero length string. This has been fixed.

CR:681545

CR Number:   681545 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3420 15 Aug 2011 Fixed Description If a client's character set was a multi-byte character set, the following operations could have resulted in CHAR or NCHAR sizes larger than they should have been: - the columns in a table created by the SELECT ... INTO [ LOCAL TEMPORARY TABLE ] table-name - the columns in a view - sa_describe_query and sa_describe_cursor domain_name_with_size and widths - the EXPRTYPE returned data type length These operations have been fixed to return the correct lengths.

CR:681551

CR Number:   681551 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3419 15 Aug 2011 Fixed 12.0.0 2722 15 Aug 2011 Fixed Description In rare cases, the server may have hang while trying to flush histogram statistics. This has been fixed.

CR:681571

CR Number:   681571 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3420 15 Aug 2011 Fixed Description If an application attempted to drop a connection that had a cursor on a proxy table open, then there was a chance the server would have crashed. This problem has now been fixed.

CR:681578

CR Number:   681578 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) 16.0.0 1528 25 Apr 2013 Fixed 12.0.1 3895 25 Apr 2013 Fixed Description In rare timing dependent cases, a copy node or async mirror could have failed assertion 100927 ("Transaction log page number ... from parent or partner is not expected page number ... "). This problem could have occurred soon after the copy node started, or soon after the copy node reconnected to a parent. This has been fixed.

CR:681579

CR Number:   681579 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1547 16 May 2013 Fixed 12.0.1 3903 16 May 2013 Fixed 11.0.1 2986 16 May 2013 Fixed Description For certain queries containing the built-in function ARGN(), the ARGN() expression may either have returned an incorrect value due to incorrectly matching an earlier case in the expression, or caused the server to crash. The probability of either failure was very small, and depended on both the database page size and the query text; however, the failure was deterministic for a given database and query text. This has been fixed.

CR:681612

CR Number:   681612 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3421 16 Aug 2011 Fixed Description In a read-only scale-out configuration, the use of CREATE OR REPLACE MIRROR SERVER parent-server (where parent-server is the parent to any copy node) could have resulted in incorrect behaviour. The incorrect behaviour included servers and/or databases stopping, or the copy node not being able to connect. This has been fixed.

CR:681616

CR Number:   681616 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) 16.0.0 1973 08 Jul 2014 Fixed Description The 'asyncfullpage' mirror synchronization_mode performance has been improved to be significantly better than the 'async' synchronization_mode for workloads that can take advantage of it. Note the 'synchronous' synchronization_mode is recommended since both the 'async' and 'asyncfullpage' modes can result in lost transactions if the primary server fails. After changing the synchronization_mode while the mirror server was connected, the mirror could have failed to take over as primary (including if the synchronization_mode was changed from 'async' or 'asyncfullpage' to 'synchronous'). This has been fixed. A side effect of this fix is the database on the mirror server automatically stops and restarts if the synchronization_mode is changed between an asynchronous mode and 'synchronous'. If the mirror database stopped and immediately restarted, in rare timing dependent cases, it was possible that the mirror would fail to take over as the primary if the primary failed. This has been fixed.

CR:681620

CR Number:   681620 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) 12.0.1 3420 16 Aug 2011 Fixed 12.0.0 2723 16 Aug 2011 Fixed 11.0.1 2660 16 Aug 2011 Fixed Description If the MobiLink server was started with an identity file containing an unencrypted private key, it would have fail to start with error "Unable to read the private key.". This has been corrected.