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

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

CR:660387

CR Number:   660387 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3295 28 Feb 2011 Fixed 12.0.0 2651 28 Feb 2011 Fixed 11.0.1 2568 28 Feb 2011 Fixed Description Incorrect results were possible for a deeply nested (at least a depth of three) aggregate subquery. This has been corrected.

CR:660428

CR Number:   660428 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3153 08 Mar 2011 Fixed 12.0.0 2652 08 Mar 2011 Fixed 11.0.1 2568 08 Mar 2011 Fixed Description The MobiLink server could have crashed during shutdown if user spawned Java threads printed to System.out or System.err after the ShutdownListeners were notified of shutdown. This has been made much less likely to happen. A work around is to ensure all user threads are stopped before the ShutdownListeners return.

CR:660432

CR Number:   660432 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 3296 01 Mar 2011 Fixed Description Creating a variable with an initial value specified as a host variable did not give a syntax error in some cases. This has been fixed.

CR:660446

CR Number:   660446 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 3297 01 Mar 2011 Fixed 12.0.0 2652 01 Mar 2011 Fixed 11.0.1 2569 01 Mar 2011 Fixed Description Performing a backup with a TRANSACTION LOG RENAME would have caused read-only connections to the database on the mirror server to be dropped. This has been fixed.

CR:660501

CR Number:   660501 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 3297 01 Mar 2011 Fixed 12.0.0 2652 01 Mar 2011 Fixed 11.0.1 2569 01 Mar 2011 Fixed Description Incorrect results were possible when executing a query with an IN list consisting of a single host variable. This has been corrected. The work-around is to rewrite expression in ( ? ) as expression = ?.

CR:660611

CR Number:   660611 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3297 02 Mar 2011 Fixed 12.0.0 2653 02 Mar 2011 Fixed Description When the MobiLink Replay utility used HTTP, wasn't providing the correct ml-client-id headers and instead always generated GUIDs. This has been fixed so that the ml-client-id header is now always set to the remote ID.

CR:660629

CR Number:   660629 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 3297 01 Mar 2011 Fixed 12.0.0 2652 01 Mar 2011 Fixed 11.0.1 2569 01 Mar 2011 Fixed Description When connected to an ASE 15.5 server and attempting to make a remote request to SQL Anywhere, there was a chance the request would have failed with an "unkown token 35" error. This problem has now been fixed. Note that this problem only affected remote requests from ASE to SQL Anywhere. The problem did not affect making remote requests from SQL Anywhere to ASE via Remote Data Access.

CR:660656

CR Number:   660656 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 3297 02 Mar 2011 Fixed 12.0.0 2652 02 Mar 2011 Fixed 11.0.1 2569 02 Mar 2011 Fixed Description After updating an external environment object via File->Update..., the object's Contents tab would not always have reflected the changes made to the object. This has been fixed.

CR:660691

CR Number:   660691 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 3339 21 Apr 2011 Fixed 12.0.0 2675 21 Apr 2011 Fixed 11.0.1 2599 21 Apr 2011 Fixed Description When accessing a directory or file using a Directory Access Server, if the name of the directory or file contained a multi-byte character where one of the bytes in the character was 0x5C, then the Directory Access Server would have failed to find the directory or file. This problem has now been fixed.

CR:660797

CR Number:   660797 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 3297 02 Mar 2011 Fixed Description During a large (at least 15 MB) data synchronization, the UltraLiteJ native library for Android could have caused a Dalvik VM memory overflow condition similar to the following: WARN/dalvikvm(641): ReferenceTable overflow (max=512) ... ERROR/dalvikvm(641): Failed adding to JNI local ref table (has 512 entries) ... ERROR/dalvikvm(641): VM aborting The memory overflow condition would have occurred during a Connection.synchronize( SyncParms parms ) call, where a SyncObserver was defined in the SyncParms. This has been fixed.

CR:660813

CR Number:   660813 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 3297 02 Mar 2011 Fixed 12.0.0 2653 02 Mar 2011 Fixed 11.0.1 2569 02 Mar 2011 Fixed Description If the database was blank padded and the database option Compression was set to be -1, .SQL Remote would have logged the following warning message in its output file: Option DBA.Compression contains invalid value -1 The value -1 is a valid value, it was the blank padding that was causing the option to be treated as invalid. This problem has been fixed.

CR:660834

CR Number:   660834 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.0 2653 03 Mar 2011 Fixed 11.0.1 2569 03 Mar 2011 Fixed Description The server could have hung for thirty seconds or more when it was establishing a mirror or diagnostics connection to another server. This has been fixed.

CR:660851

CR Number:   660851 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 3300 08 Mar 2011 Fixed 12.0.0 2656 08 Mar 2011 Fixed 11.0.1 2572 08 Mar 2011 Fixed Description When a primary server lost its connections to both the mirror and arbiter servers as a checkpoint was performed, the database on the primary may not have been recoverable. Typically, it would fail assertion 100904. This has been fixed. Similarly, in cases where a primary server lost its connections to both the mirror and arbiter servers as a checkpoint was performed, the next time the primary and mirror servers were connected and attempt to synchronize, the mirror server may have in rare situations reported "Database "<name>" mirroring: database is not compatible with primary; files must be replaced" and then stop with the message "Database server shutdown due to incompatible files for database mirroring". This has been fixed to reduce the possibility of this occurring. It is possible for this to still occur, so then the database running on the current primary must be manually copied or backed up to the mirror server so that the server can successfully synchronize again. The primary server could have hung, again in rare situations, if only one of the two connections between it and the mirror server was dropped, for example due to a liveness timeout. This has been fixed. When the mirror server was becoming the primary server there was a small possibility it could have hung after reporting it was starting a checkpoint and then reporting it was recovering. This has been fixed.

CR:660995

CR Number:   660995 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 3298 03 Mar 2011 Fixed 12.0.0 2653 03 Mar 2011 Fixed 11.0.1 2570 03 Mar 2011 Fixed Description When connected to a Relay Server, and no Outbound Enabler providing the backend service had connected yet, the connection was expected to timeout within the application timeout time specified by the client. However on IIS7, some J2SE http clients may have become stuck writing to a server that was no longer reading and eventually failed the write and then perform a delayed internal retry without processing the response sent by the web server. This change modifies the Relay Server to provide the expected fail fast experience according to the timeout against such J2SE clients.

CR:661008

CR Number:   661008 Product Name:   UltraLite Product Component:   UL Java Provider for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3298 04 Mar 2011 Fixed Description Right-clicking on an UltraLite database in the UltraLite Sybase Central plug-in, will show a list of database properties, one of which is the database file name. If the file name contained multi-byte characters, they could have been displayed as mangled characters. This has now been fixed.

CR:661034

CR Number:   661034 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 3298 04 Mar 2011 Fixed Description Under rare conditions, the server could have hung while executing a query with multiple GROUP BY clauses. This may have occurred when the workload executing on the server suddenly changed (i.e. if many requests arrived almost simultaneously). This has been fixed. A workaround is to disable intra-query parallelism for the affected query (SET TEMPORARY OPTION MAX_QUERY_TASKS=1).

CR:661035

CR Number:   661035 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3299 08 Mar 2011 Fixed 12.0.0 2655 08 Mar 2011 Fixed 11.0.1 2571 08 Mar 2011 Fixed Description When deploying a Synchronization Model for an existing remote database and only deploying to file, the generated Windows batch file would have failed when execute. For example, a "You are not connected to a database" error could have occurred when the batch file tried to apply the generated SQL file to the remote database. This has been fixed. To workaround the problem, change this line in the generated batch file: set CONNECTION=%1 to this: set CONNECTION=%~1

CR:661036

CR Number:   661036 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 3319 04 Mar 2011 Fixed 12.0.0 2665 04 Mar 2011 Fixed 11.0.1 2584 04 Mar 2011 Fixed Description Activity executing on the utility_db could have caused a crash, memory corruption, or other unpredictable behaviour, if the cache were to shrink at the same time. This problem has been fixed.

CR:661066

CR Number:   661066 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) 12.0.1 3324 05 Apr 2011 Fixed 12.0.0 2667 05 Apr 2011 Fixed 11.0.1 2587 05 Apr 2011 Fixed Description If a range of values was supplied for the TCP/IP option ClientPort, connection attempts may have been slow if the server was not found, or if multiple hosts were supplied for the Host option. This has been fixed.

CR:661112

CR Number:   661112 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 3315 24 Mar 2011 Fixed 12.0.0 2665 24 Mar 2011 Fixed 11.0.1 2583 24 Mar 2011 Fixed Description It was possible for synchronizations to fail if any of the 'certificate_name', 'certificate_company', or 'certificate_unit' parameters were supplied, even though the value of these parameters matched the corresponding field values in the server's certificate, if they were encoded as Unicode in the server's certificate. This has been corrected.

CR:661180

CR Number:   661180 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3364 02 Jun 2011 Fixed 12.0.0 2691 02 Jun 2011 Fixed Description On Linux systems, if the SQL Anywhere Monitor EBF was installed as a non-root user, and the SQL Anywhere Monitor service had been started by the root user, the following error messages would have been displayed: Migrating SQL Anywhere Monitor database Connecting... Can't connect to source database. [Sybase][JDBC Driver][SQL Anywhere]Specified database not found Rolling back files in /opt/samonitor12 ... wc: ./.ebf_20110601-1149/samonitor.db: Permission denied Cleaning up ... This has been fixed so that the following error message is now displayed: The setup program was unable to stop a running instance of SQL Anywhere Monitor. Please stop it manually and run the setup program again. A workaround is to stop the SQL Anywhere Monitor service manually, then re-run the EBF installer.

CR:661188

CR Number:   661188 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3298 07 Mar 2011 Fixed Description The 64-bit UltraLite ODBC driver (Bin64\ulodbc12.dll) was not being correctly registered. This would have resulted in the failure of Interactive SQL and/or Sybase Central to load an UltraLite database. The has been fixed. Alternatively, the driver can be registered manually using the following command: regsvr32.exe %SQLANY12%\Bin64\ulodbc12.dll

CR:661193

CR Number:   661193 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 3302 15 Mar 2011 Fixed Description Atempting to call a Java external environment stored procedure or function with a very long binary or string input argument, could have taken a very long time to execute. This problem has now been fixed.

CR:661198

CR Number:   661198 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 3325 08 Apr 2011 Fixed 12.0.0 2668 08 Apr 2011 Fixed 11.0.1 2587 08 Apr 2011 Fixed Description On Fedora 14 Linux systems with SELinux enabled, the SQL Anuywhere Monitor and the Administration tools would have failed to launch. Launching on the command line would have shown an error message like: ERROR! Could not load the Java virtual machine DLL: /opt/sqlanywhere/sun/jre160_x86/lib/i386/client/libjvm.so This has been fixed. A workaround is to run "setenforce 0" as root.

CR:661225

CR Number:   661225 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.0 2654 04 Mar 2011 Fixed 11.0.1 2570 04 Mar 2011 Fixed Description A network environment that was sensitive to HOST header inspection on http traffic, may have caused the Outbound Enabler to fail to connect to the Relay Server, or it may have connected to the wrong server. This has been fixed.

CR:661242

CR Number:   661242 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3298 07 Mar 2011 Fixed Description A silent install of SQL Anywhere Monitor in which the location of the database (DIR_SQLANY_MONITOR) was not specified, would have caused the database to be installed to %SystemDrive%\CommonDocFolder. This has been fixed so that the correct default location is now used (%ALLUSERSPROFILE%\Documents\SQL Anywhere Monitor 12).

CR:661431

CR Number:   661431 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1585 27 Jun 2013 Fixed 12.0.1 3927 27 Jun 2013 Fixed Description The graph could have displayed data deleted by a maintenance run if it was open when the maintenance plan ran. This is not a bug because the graph only gets new points not all points. The real bug was the fact that automatic browser refreshes were not happening every hour, just once after the first hour. This has now been fixed.

CR:661440

CR Number:   661440 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) 12.0.1 3332 10 Jun 2011 Fixed 12.0.0 2672 19 Apr 2011 Fixed 11.0.1 2593 19 Apr 2011 Fixed 10.0.1 4213 19 Apr 2011 Fixed Description In rare cases, the server may have crashed while performing DDL and DML operations concurrently. This has been fixed.

CR:661453

CR Number:   661453 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 3299 08 Mar 2011 Fixed 12.0.0 2655 08 Mar 2011 Fixed 11.0.1 2571 08 Mar 2011 Fixed Description If the distance parameter of the proximity search condition contained letters, the server could have silently failed, and returned some result, instead of reporting an error. This has been fixed. For example, the following query would not report an error and would behave as if the full text query was 'apple NEAR[2] oranges': SELECT * FROM t CONTAINS( 'apple NEAR[ 2b ] oranges' ) Note that the following query was correctly reporting an error: SELECT * FROM t CONTAINS( 'apple NEAR[ b ] oranges' )

CR:661459

CR Number:   661459 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3299 07 Mar 2011 Fixed 12.0.0 2654 07 Mar 2011 Fixed 11.0.1 2571 07 Mar 2011 Fixed 10.0.1 4193 07 Mar 2011 Fixed Description The .NET provider was incorrectly assuming that a Sybase IQ 12.7 server supported the NCHAR datatype. This resulted in a failure to establish a connection to a Sybase IQ 12.7 server. This problem has been fixed.

CR:661493

CR Number:   661493 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3299 08 Mar 2011 Fixed Description The certificate utilities, Certificate Viewer (viewcert), Certificate Creation (createcert), and Key Pair Generator (createkey), now run on 64-bit Windows.

CR:661622

CR Number:   661622 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 3326 11 Apr 2011 Fixed 12.0.0 2668 11 Apr 2011 Fixed 11.0.1 2586 11 Apr 2011 Fixed Description Execution of a query with a subselect predicate correlated on two different tables from the main query block may have caused an assertion failure in the server. This has now been fixed For example: Select * from T1, T2 where T1.X = (select e1 from R where p(R,T1, T2) ) and .. The predicate "T1.X = (select e1 from R where p(R,T1, T2) )" has a subselect and references both tables T1 and T2 from the main query block.

CR:661633

CR Number:   661633 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) 12.0.1 3303 15 Mar 2011 Fixed 12.0.0 2658 17 Mar 2011 Fixed 11.0.1 2572 17 Mar 2011 Fixed Description Execution of an "UPDATE ... PUBLICATION ... WHERE .." statement with a complex WHERE clause may have caused the server to crash. This has been fixed.

CR:661663

CR Number:   661663 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 3305 09 Mar 2011 Fixed Description For each outgoing HTTPS web procedure connection, a small amount of memory was leaked which could eventually have lead to memory exhaustion. This has been fixed.

CR:661791

CR Number:   661791 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 3315 30 Mar 2011 Fixed Description A query containing a join between two or more tables could have returned an incorrect result if the executed query plan used an Index-Only Scan of some index T_idx over table T. For the problem to have occurred, a column T.col must have participated in a non-equality join predicate (e.g. "T.col < S.col", or "T.col BETWEEN S.col1 AND S.col2"), and there must have existed one or more columns in index T_idx preceeding T.col that did not participate in equality predicates. This has been fixed.

CR:661849

CR Number:   661849 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 3300 10 Mar 2011 Fixed 12.0.0 2656 10 Mar 2011 Fixed 11.0.1 2572 10 Mar 2011 Fixed Description When using the Service utility (dbsvc) to start a Relay Server service with a large configuration on a slow machine, it may have reported startup errors while the service was still in the pending start state. A fix was made to the Relay Server to correct this problem.

CR:661930

CR Number:   661930 Product Name:   UltraLite Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3301 10 Mar 2011 Fixed 12.0.0 2656 10 Mar 2011 Fixed Description In some cases, the UltraLite Database Unload utility (ulunload) would have generated foreign keys in its XML output file that were not really in the database being unloaded. This has been fixed.

CR:662000

CR Number:   662000 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3301 10 Mar 2011 Fixed 12.0.0 2656 10 Mar 2011 Fixed Description Attempting to insert a variable of type LONG BINARY into a proxy could have taken a very long time, even though the variable was only a few megabytes in length. This problem has been resolved and the performance of inserting LONG BINARY variables into proxy tables has been greatly improved. Note that this fix also improves the performance of inserting LONG VARCHAR and LONG NVARCHAR variables into proxy as well.

CR:662025

CR Number:   662025 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) 12.0.1 3303 10 Mar 2011 Fixed 12.0.0 2659 10 Mar 2011 Fixed Description In some cases, the server would have displayed recovery progress messages incorrectly when recovering a large transaction log. In this situation, either no messages would have been displayed or an incorrect percentage would have been displayed. This has been fixed.

CR:662054

CR Number:   662054 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) 12.0.1 3300 10 Mar 2011 Fixed 12.0.0 2655 10 Mar 2011 Fixed 11.0.1 2572 10 Mar 2011 Fixed Description When deploying, the directory used by the Interactive SQL utility, Sybase Central, the Console utility, and the MobiLink Monitor, can now be specified. To do this, an OEM.ini file must be deployed along with these utilities. The file must contain the following lines: [preferences] directory={preferences files directory| where "preferences_files_directory" is a fully-qualified directory name, e.g. "c:\work\prefs". The directory name should not end in a separator (backslash on Windows; forward slash on Unix and Mac OS X). Preferences files include: .isqlPreferences12_32 .isqlPreferences12_64 .isqlHistory12 .jlogon12 .textCompleter12 .SybaseCentralEditor610 .scUserPreferences610_32 .scUserPreferences610_64 among others.

CR:662072

CR Number:   662072 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 3301 11 Mar 2011 Fixed Description When deploying a Synchronization Model with conflict resolution to a SQL Anywhere or Sybase IQ database, the SQL generated to create a global temporary table checked twice for an existing table. Although this did not cause any errors, the generated SQL has been fixed so that it now only checks once for an existing table before creating a global temporary table.

CR:662074

CR Number:   662074 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3300 10 Mar 2011 Fixed 12.0.0 2656 10 Mar 2011 Fixed Description The following UltraLite resumable-download problems are now fixed: In rare cases, UltraLite incorrectly computed where to resume the download. When this occurred, the subsequently resumed download was effectively corrupted, likely causing a synchronization error. (To recover, the download must have been rolled back.) When resuming a download, the server continued to use the original 'timeout' specification, but UltraLite used the default. If a non-default timeout value was specified, the resumed download may have timed out even though the network connection was fine (though it still maked progress). Sometimes the sync-info (or sync-result) 'partial_download_retained' flag was false after trying to resume a download when there was still a partial download present. (Workaround is to only make use of this flag when first set - attempting to subsequently resume when there is no partial download is safe and returns an error.) As well, the following problem is fixed: The COMMITTING_DOWNLOAD sync observer state was signaled later than it should have been. The observer saw UltraLite was still receiving the download, when in fact it had begun committing the download.

CR:662232

CR Number:   662232 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3301 17 Mar 2011 Fixed 12.0.0 2657 17 Mar 2011 Fixed Description The performance of database changes on first update (commit) after starting up has been improved.

CR:662233

CR Number:   662233 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 3301 11 Mar 2011 Fixed 12.0.0 2657 11 Mar 2011 Fixed 11.0.1 2573 11 Mar 2011 Fixed Description The connection properties on the Advanced page of the Connect dialog were not filled when attempting to reconnect following a disconnect. For this problem to have occurred, the IQ plug-in for the Interactive SQL utility would needed to have been loaded. That plug-in is loaded by default starting in version 12.0.1. A similar problem affected the TLS packet encryption parameters on the Network page. Both of these problems have now been fixed.

CR:662248

CR Number:   662248 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 1823 23 Jan 2014 Fixed 12.0.1 4062 23 Jan 2014 Fixed 11.0.1 3113 23 Jan 2014 Fixed Description In rare, timing and data-dependent cases, the server could have hung or crashed during execution of parallel query plans. This has now been fixed.

CR:662419

CR Number:   662419 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 3328 04 Apr 2011 Fixed 12.0.0 2670 04 Apr 2011 Fixed Description A mirror node in a mirroring system could have failed to recover its database if the database used sequence generators, and the primary and mirror roles switched between the servers. This has been fixed so that servers can now recover logs that exhibit this problem.

CR:662421

CR Number:   662421 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 14 Mar 2011 Fixed Description The nomenclature used to refer to .SQL script files and individual SQL statements has been made consistent throughout the software. This change affects the wording in some error messages, and the following UI elements: 1. On the "General" panel in the Options window, the first group box title was changed from "Command Files" to "SQL Script Files" and the first checkbox, "Echo command files to log" has been renamed "Echo SQL script files to log". 2. The "Commands" tabs in the Options window (there are three of them: one for SQL Anywhere, one for UltraLite, and one for IQ) have been renamed from "Commands" to "Execution". 3. The command-line help now clearly refers to SQL statements as "statements" rather than "commands". 4. The "Command History" window has been renamed "History"

CR:662452

CR Number:   662452 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 3302 15 Mar 2011 Fixed 12.0.0 2658 15 Mar 2011 Fixed 11.0.1 2574 15 Mar 2011 Fixed Description Attempting to start a connection-scoped external environment, and then canceling the start request before the external environment completed the startup process, could have caused the server to crash. This problem has now been fixed.

CR:662456

CR Number:   662456 Product Name:   MobiLink Product Component:   QAnywhere client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3303 17 Mar 2011 Fixed 11.0.1 2575 17 Mar 2011 Fixed 12.0.0 2659 17 Mar 2011 Fixed Description On a Windows Mobile device, the QAnywhere Agent (qaagent) would have sometimes given the following error messages at start up: E. 2011-03-14 08:33:50. Error registering with DBLSN code: -1 The error message was displayed in a message box, even when qaagent was executed in quiet mode. This has been fixed. Now, qaagent is more tolerant to dblsn slowness at startup. Also, a message box is not displayed when qaagent is executed in quiet mode (-q or -qi), and the message is logged in the qaagent console and log file.

CR:662466

CR Number:   662466 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 2569 14 Mar 2011 Fixed Description Some potential security issues have been fixed.

CR:662477

CR Number:   662477 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3302 15 Mar 2011 Fixed Description When resuming a download, the sent and received statistics are restored from the previous sync and continue as expected from that point, except the byte counts, which were reset to zero. This has now been fixed. The byte counts (like the row statistics) are cumulative for resumed downloads. These statistics are available to the synchronization observer callback and are contained in the sync-results object.

CR:662639

CR Number:   662639 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3303 17 Mar 2011 Fixed 12.0.0 2659 17 Mar 2011 Fixed 11.0.1 2575 17 Mar 2011 Fixed Description When a SQL Anywhere database is used as a remote database, the MobiLink client (dbmlsync) generates a remote ID which is a GUID for the database during the first synchronization. This remote ID is used by the Mobilink server to identify the remote. MobiLink keeps a list of synchronizing remotes in the ml_database table. When a blank padded SA database was used as a remote, a remote ID would have been generated during the first synchronization, sent to the MobiLink server and stored in the ml_database table. On all subsequent synchronizations, a blank padded version of the remote id would then have been sent. The results of this were: 1) The server would not have been recognized on the second sync that the same remote was synchronizing and would treat the second sync as a first sync. That is to say the server would not have used state information it had from the first sync when processing the second. Third and subsequent sync's were not affected. This would have had no impact unless the first synchronization had failed. 2) Two entries would have been made in the ml_database table for each remote. One would contain the blank padded remote id and the other would contain the unpadded id. This behaviour has now been fixed. Now, on first synchronization the remote_id assigned to the remote database will be blank padded.

CR:662749

CR Number:   662749 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 3305 18 Mar 2011 Fixed Description Proxy support for the Relay Server Outbound Enabler may only have worked with HTTPS against some HTTP 1.1 proxy servers. The down channel using HTTP instead of HTTPS would have connected successfully at first but then would have been dropped by the proxy after a period of being idle. This problem is proxy specific and is does not affect all HTTP proxy environments. This problem has been fixed in the Outbound Enabler so that HTTP will now also work. The workaround is to use HTTPS.

CR:662766

CR Number:   662766 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3321 06 Apr 2011 Fixed 12.0.0 2666 06 Apr 2011 Fixed 11.0.1 2586 06 Apr 2011 Fixed Description When using the Deployment wizard to build an MSI install containing both 64-bit and 32-bit software, the jvm.dll in the sun\jre160_x64\bin\server directory was being replaced by the 32-bit version. This could have occurred whenever two different files were included with the same name, in a directory with the same name, and with the same parent directory. This has been corrected.

CR:662770

CR Number:   662770 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) 17 Mar 2011 Fixed Description There were three "Update Checker" tabs in the "Options" window -- one for SQL Anywhere, one for UltraLite, and one for IQ. Now there is just one, and it appears in the list on the left side of the window, after "Compatibility".

CR:662896

CR Number:   662896 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Microsoft Windows Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3309 22 Mar 2011 Fixed 12.0.0 2661 22 Mar 2011 Fixed 11.0.1 2579 22 Mar 2011 Fixed 10.0.1 4201 22 Mar 2011 Fixed 9.0.2 4010 22 Mar 2011 Fixed Description When using the OLEDB provider, if a statement was prepared, executed, and then the ADO MoveFirst() (OLE DB RestartPosition() ) method was called when the cursor type was forward-only, the statement would have become unprepared. Subsequent attempts to execute the prepared statement would then have failed. This problem has been corrected.

CR:662919

CR Number:   662919 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 17 Mar 2011 Fixed Description The SQL/Stop menu item used to have "Ctrl+Break" as its accelerator. This accelerator has been removed on all platforms except Windows because the accelerator did not work. Ctrl+Break continues to be supported in Windows.

CR:662942

CR Number:   662942 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3304 18 Mar 2011 Fixed 12.0.0 2659 18 Mar 2011 Fixed Description Charting metric data may have omitted some ending data points. This has been fixed.

CR:662944

CR Number:   662944 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3304 18 Mar 2011 Fixed Description On Mac OS X, the tool tips for the "zoom in", "zoom out", "reset view", and "save image" buttons in the "Value of Column" dialog indicated that the Control key should be held down to activate the button. This was incorrect, it should have shown the Command key. This has now been fixed.

CR:663056

CR Number:   663056 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) 12.0.1 3346 06 May 2011 Fixed 12.0.0 2679 06 May 2011 Fixed 11.0.1 2602 06 May 2011 Fixed 10.0.1 4222 06 May 2011 Fixed Description In exceptional rare situations the server could have crashed or failed assertions 106808, 100913, or 111706 if very long property values are queried. This has been fixed by truncating property values to the max varchar length of 32000 bytes.

CR:663061

CR Number:   663061 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 3306 23 Mar 2011 Fixed 12.0.0 2660 23 Mar 2011 Fixed 11.0.1 2577 23 Mar 2011 Fixed Description Proxy support for the Relay Server Outbound Enabler may only have worked with HTTPS against some HTTP 1.1 proxy servers. The down channel using HTTP instead of HTTPS would have connected successfully at first but then would have been dropped by the proxy after a period of being idle. This problem is proxy specific and it does not affect all HTTP proxy environments. This problem has been fixed in the Relay Server so that an update to the Outbound Enabler is not required (see Engineering case 662749). The workaround is to use HTTPS, or apply the Outbound Enabler fix from case 662749.

CR:663123

CR Number:   663123 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 3305 18 Mar 2011 Fixed Description Creating an ODBC data source for IQ from the Connect dialog did create a DSN, but it was not created correctly. The following issues have been fixed: 1. The driver name for the data source was always "SQL Anywhere 12" rather than "Sybase IQ". This prevented the data source from being listed in the "Data Source Names" window unless you checked "Show all data sources". Also, to connect using the data source, the SQL Anywhere ODBC driver had to be installed. 2. Creating a system data source would fail on machines that did not have "dbdsn" installed. This would be a problem on computers running Vista or Windows 7 which have IQ installed, but not SQL Anywhere.

CR:663171

CR Number:   663171 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 3323 29 Mar 2011 Fixed Description The Relay Server may not have responded to HTTP GET requests for non-relay purposes. For example, using a browser to visit the rs_admin extension would have resulted in a connection drop without a response. A load-balancer trying to test the Relay Server service via the rs_server extension, would also have resulted in a connection drop without a response regardless of the status of the relay service. This has been fixed so that a useful response is now provided when HTTP GET requests are issued against various Relay Server extensions.

CR:663259

CR Number:   663259 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 3306 21 Mar 2011 Fixed Description The Remote Data Access feature is now capable of loading the SQL Anywhere ODBC driver directly. If a remote server is defined similar to the following: CREATE SERVER remote-server CLASS 'saodbc' USING 'driver=SQL Anywhere Native;...' where the the USING clause contains the key pair "driver=SQL Anywhere Native", and the remainder of the USING clause provides all the connection parameters necessary to successfully connect to the remote SQL Anywhere server, then the remote data access layer will load the SQL Anywhere ODBC driver directly and bypass the Windows ODBC Driver Manager on Windows based platforms and the SQL Anywhere ODBC Driver Manager on UNIX platforms. The benefit to loading the SQL Anywhere ODBC driver directly is that, although the ODBC driver still needs to be installed, it no longer needs to be registered if it is only being used for the remote data access support. What's more, if there are multiple copies of the ODBC driver installed, then loading the ODBC driver directly will guarantee that the ODBC driver for the current server version gets used rather than one that was registered with a previous version of SQL Anywhere. It should be noted that if the application also makes use of non-SQL Anywhere remote servers or if there are SQL Anywhere remote servers defined without the "driver=SQL Anywhere Native" key pair, then the remote data access layer will still use a Driver Manager for those other remote servers.

CR:663261

CR Number:   663261 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 3308 22 Mar 2011 Fixed 12.0.0 2650 22 Mar 2011 Fixed Description The Relay Server Outbound Enabler on MacOS may have failed to receive all download data from the backend server. If Relay Server for Apache was used, then it would have appended a 500 HTTP error page to the data, which most likely would have caused client failure. This has now been fixed.

CR:663264

CR Number:   663264 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   7.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Mar 2011 Fixed Description If executing a statement causes an error, the window which shows the error now includes line numbers beside the SQL statement lines. This can make it easier to see which line caused the error when executing a compound statement.

CR:663279

CR Number:   663279 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 3308 22 Mar 2011 Fixed 12.0.0 2661 22 Mar 2011 Fixed 11.0.1 2578 22 Mar 2011 Fixed Description Clicking the "Stop" toolbar button in the Interactive SQL utility often did not stop execution if many short-running statements were being executed. It did work correctly if executing a single long-running statement. This has been fixed. The workaround for this problem is to use the SQL->Stop menu item, which always works.

CR:663283

CR Number:   663283 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   8.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3305 21 Mar 2011 Fixed 12.0.0 2660 21 Mar 2011 Fixed 11.0.1 2576 21 Mar 2011 Fixed Description The server may have chosen less that optimal plans for queries with predicates of the form 'T.X=(unknown expression)' if an index on T(X) existed. The '(unknown expression)' could have been, for example, a variable whose value was not used for queries inside the procedures, or could have been a complex expression (i.e. "R.Y+1"). This has now been fixed.

CR:663307

CR Number:   663307 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3308 22 Mar 2011 Fixed Description UltraLite now supports the 'armv7' architecture when targeting iOS. With the just-released Xcode and SDK versions, the default includes armv7.

CR:663442

CR Number:   663442 Product Name:   MobiLink Product Component:   RelayServer plug-in for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 22 Mar 2011 Fixed Description It was not possible to set the logging verbosity for backend server farms from the Farm property sheet. This has now been corrected.

CR:663459

CR Number:   663459 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 3309 23 Mar 2011 Fixed 12.0.0 2661 23 Mar 2011 Fixed 11.0.1 2579 23 Mar 2011 Fixed Description Attempting to autostart a database server on Windows CE when one was already running was incorrectly giving the error: "Unable to start specified database: server exit code -11728" (where the number could vary). This has been fixed to return the correct error: "Database server already running" Note that on Windows CE only one database server can be running at a time, even if when attempting to start a second server with a different name.

CR:663470

CR Number:   663470 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 3310 23 Mar 2011 Fixed 12.0.0 2662 23 Mar 2011 Fixed 11.0.1 2581 23 Mar 2011 Fixed 10.0.1 4202 23 Mar 2011 Fixed Description On CE devices, if multiple applications were running simultaneously, the library dbdata.dll could have been deployed multiple times to the temp directory. This problem has been fixed. Additionally, the version number has been added to the native dll name (i.e. dbdata12.dll). This will allow running multiple versions of the provider simultaneously on Windows CE.

CR:663502

CR Number:   663502 Product Name:   UltraLiteJ Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3309 23 Mar 2011 Fixed Description A new UltraLiteJ utility, ULjExportBuilder, has be added. This utility takes an existing J2SE UltraLiteJ database and produces a more compact file that can be deployed to J2SE or RIM clients. An equivalent database can then be created from the exported file. usage: ULjExportBuilder database-file exported-file The required two arguments are file names. The database must not be encrypted and must be a shadow-page database (the default). To invoke the export functionality from a Java program, create an object com.ianywhere.ultralitej.pgmsutility.ULjExportBuilder (there are no arguments passed to the constructor) and then invoke the export method with one argument which is a two-element String array containing the names of the database and export files respectively. The exported file can placed on a client device using, for example, a MobiLink file transfer. The database may be imported using an import method which has three arguments: java.io.InputStream which is used to read the exported file String to specify the name of the database null (no encryption) or an EncryptionControlObject which will be used to encrypt pages within the database. (1) On Rim devices the methods are: DatabaseManager.importDatabaseFileME (import to a RIM file in flash or on an SD-card) DatabaseManager.importDatabaseObjectStore (import to the Rim Object store) (2) On J2SE: DatabaseManager.importDatabaseFile (import to a file )

CR:663573

CR Number:   663573 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3310 24 Mar 2011 Fixed 12.0.0 2662 24 Mar 2011 Fixed Description The SQL Anywhere Monitor's server console, would have shown the following incorrect error message: [Sybase][JDBC Driver][SQL Anywhere]Could not load dynamic library 'dbsrvmon11' (SQLCODE: -620, SQLSTATE: HY000) An incorrect version number being assigned when a monitor object was removed. This has been fixed.

CR:663596

CR Number:   663596 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 3311 23 Mar 2011 Fixed 12.0.0 2662 23 Mar 2011 Fixed Description Attempting to insert a variable of type long binary, varchar or nvarchr into a proxy or IQ table that had been generated using the REPEAT() function could have caused an incorrect value to be inserted. It should be noted that this problem would only have occurred if the fix for Engineering case 662000 had already been applied. This problem has now been fixed.

CR:663629

CR Number:   663629 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3311 24 Mar 2011 Fixed 12.0.0 2662 25 Mar 2011 Fixed Description When replaying a recorded protocol file more than once with the same client without using the ap option, all replay sessions after the first would have failed due to a progress mismatch warning received from the MobiLink server (this is expected). However, the error message that appears in the MLReplay log in this situation does not make it clear that the problem will disappear if the ap option is used. So, the MobiLink Replay utility has been changed so that when it receives an unexpected progress mismatch from the MobiLink server, an error message saying so is logged, which points the user to use the ap option.

CR:663786

CR Number:   663786 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3311 25 Mar 2011 Fixed 12.0.0 2581 25 Mar 2011 Fixed Description The Server Enumeration utility (dblocate) may have failed to list some running database servers if many (over around 50) servers were running in the TCP/IP subnet. This problem was more likely if the -d option ("brief list of databases running on each server"). This has been fixed by increasing the UDP receive buffer size used by dblocate. For some Unix/Linux operating systems, in order for this change to take effect, the system maximum UDP receive buffer size may need to be increased. On Linux, this can be done by increasing the sysctl net.core.rmem_max setting.

CR:663835

CR Number:   663835 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) 11.0.1 2581 25 Mar 2011 Fixed Description When the Outbound Enabler shut down, on going client requests may have taken 3 times the application timeout value to abort. This has been fixed.

CR:663936

CR Number:   663936 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 3311 25 Mar 2011 Fixed 12.0.0 2662 25 Mar 2011 Fixed Description On Unix systems, the second field in the Relay Server's log, which is the thread ID, may shown a negative number. The type used to store the thread ID value was not big enough on Unix systems, as thread IDs tend to be large, and could have overflowed. This has now been fixed.

CR:663937

CR Number:   663937 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   9.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3326 12 Apr 2011 Fixed 11.0.1 2588 12 Apr 2011 Fixed 10.0.1 4209 12 Apr 2011 Fixed 12.0.0 2669 12 Apr 2011 Fixed Description In the Interactive SQL utility, setting the "on_error" option to "continue" was not preventing warnings from being displayed in a popup window. This has been corrected so that when the option is set to "continue", warnings are now displayed in the "Messages" pane.

CR:663940

CR Number:   663940 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 3314 29 Mar 2011 Fixed Description In very rare cases, a spatial query that applied one of the following methods to a complex geometry value may have returned an incorrect result, or an error: 1. all set operations: ST_Union, ST_Intersection, ST_Difference, ST_SymDifference 2. certain aggregation functions: ST_UnionAggr, ST_IntersectionAggr 3. certain spatial predicates: ST_Intersects, ST_Overlaps, ST_Within, ST_Disjoint, ST_Touches, ST_Crosses, ST_Contains, ST_Relate This has been fixed.

CR:663987

CR Number:   663987 Product Name:   MobiLink Product Component:   Relay Server Status:   Closed OS:   Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3475 17 Oct 2011 Fixed Description The Relay Server Outbound Enabler is now able to initiate SSL connections to the backend server. In the -cs option, HTTPS=1 is used to enable an SSL connection to the backend server. When SSL is enabled, the -cs option can take the values 'trusted_certificates', 'identity' and 'identity_password' for server and/or client authentication.

CR:663991

CR Number:   663991 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) 12.0.1 3320 04 Apr 2011 Fixed 12.0.0 2665 04 Apr 2011 Fixed 11.0.1 2584 04 Apr 2011 Fixed 10.0.1 4205 04 Apr 2011 Fixed Description Under some circumstances, queries with cached plans and queries containing complex correlated subqueries may have returned incomplete results if they were executed as parallel plans. This has been fixed. Note, a workaround is to disable intra-query parallelism (set MAX_QUERY_TASKS=1).

CR:664139

CR Number:   664139 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 3314 29 Mar 2011 Fixed 12.0.0 2664 29 Mar 2011 Fixed 11.0.1 2583 29 Mar 2011 Fixed Description When a Relay Server starts up, its description was logged and the startup verbosity was applied properly, but those values were not stored correctly for later consumption. Such as for the admin tool to export the configuration or for the next configuration update to properly determine if an updated was required. This problem has been fixed.

CR:664140

CR Number:   664140 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3315 30 Mar 2011 Fixed 12.0.0 2665 30 Mar 2011 Fixed 11.0.1 2583 30 Mar 2011 Fixed Description Sometime the MobiLink Listener (dblsn) could have taken a few minutes to shutdown if the shutdown was initiated by the QAnywhere Agent (qaagent). This problem has been fixed.

CR:664247

CR Number:   664247 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 3314 29 Mar 2011 Fixed 12.0.0 2664 29 Mar 2011 Fixed 11.0.1 2583 29 Mar 2011 Fixed Description If the system procedure sa_get_user_status() was run on a database with an extremely high number of user definitions, the procedure would have blocked DDL statements and could not have been cancelled until its result had been materialized. This has been fixed.

CR:664280

CR Number:   664280 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) 03 Aug 2011 Fixed Description In some cases, a sub-select that had no outer references, or a user defined function with no non-constant parameters in the select list, was evaluated when the column was first fetched from a cursor. Now these expressions are evaluated as soon as the row is returned.

CR:664283

CR Number:   664283 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 3314 29 Mar 2011 Fixed 12.0.0 2664 29 Mar 2011 Fixed 11.0.1 2583 29 Mar 2011 Fixed Description Relay Server enable/disable events were not broadcast to connected Outbound Enablers. For example, disabling the last Relay Server from a Relay Server farm was not going to suffer the issue described in Engineering case 664284, but when adding a Relay Server to the Relay Server farm, it would also not have woken up the Outbound Enablers to start utilizing the new Relay Server. The user workaround is to restart the Outbound Enabler. This problem has been fixed.

CR:664284

CR Number:   664284 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 3327 29 Mar 2011 Fixed 12.0.0 2669 29 Mar 2011 Fixed Description The Relay Server Outbound Enabler would have stopped discovering Relay Servers after the last Relay Server was disabled from a server farm. The Outbound Enabler would have become unusable until restarted. This is fixed so that the Outbound Enabler will now attempt to discover new Relay Servers at the rate specified by the existing Outbound Enabler -d switch.

CR:664292

CR Number:   664292 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 3315 01 Apr 2011 Fixed 12.0.0 2665 01 Apr 2011 Fixed 11.0.1 2583 27 Apr 2011 Fixed Description In rare situations, the server could have crashed if a log truncation or rename (dbbackup -x or -xo or -r) took place while the server was processing a large number of transactions, especially long-running transactions. This has been fixed. No workaround for this problem is known, except to avoid performing log truncation or renaming when the server is handling large numbers of inserts, updates or deletes.

CR:664348

CR Number:   664348 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) 12.0.1 3315 30 Mar 2011 Fixed 11.0.1 2583 30 Mar 2011 Fixed Description In very rare timing dependent cases, the server could have crashed or hung on shutdown if there were active client requests during shutdown. The databases would have already been stopped before the failure, so there was no chance of data loss. This has been fixed.

CR:664390

CR Number:   664390 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 3315 30 Mar 2011 Fixed Description End-to-end encryption (e2ee) has been added to UltraLiteJ for the Android platform. This was accomplished by using the new methods in the StreamHTTPSParms interface: void setE2eePublicKey( String file_name ) String getE2eePublicKey() The file_name is the name of an RSA public key file used in the encryption.

CR:664490

CR Number:   664490 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 3317 01 Apr 2011 Fixed Description Cancelling a query that referenced spatial functions could have caused the server to crash, although the probability was exceedingly small. This has been fixed.

CR:664506

CR Number:   664506 Product Name:   SQL Anywhere Monitor Product Component:   SQL Anywhere Monitor Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3315 01 Apr 2011 Fixed 12.0.0 2665 01 Apr 2011 Fixed Description Steady Relay Server metrics, like peak values, values associated with idle farms, and idle error counts, may not have shown correctly in graphs inside the SQL Anywhere Monitor. The work around is to view them as current values instead of graphing. This issue has been fixed.

CR:664507

CR Number:   664507 Product Name:   UltraLite Product Component:   UltraLite.NET Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3326 11 Apr 2011 Fixed 12.0.0 2669 11 Apr 2011 Fixed 11.0.1 2588 11 Apr 2011 Fixed Description ULDataAdapter class may have reported the error SQLE_TOO_MANY_TEMP_TABLES even if the Dispose() method was invoked. This has been fixed.

CR:664633

CR Number:   664633 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3315 31 Mar 2011 Fixed 12.0.0 2665 31 Mar 2011 Fixed 11.0.1 2583 31 Mar 2011 Fixed Description A synchronization using FIPS end-to-end-encryption could have corrupted a FIPS encrypted UltraLite database. This has been corrected.

CR:664681

CR Number:   664681 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) 10.0.1 4207 05 Apr 2011 Fixed Description Server may have hang unexpectedly. This has been fixed.

CR:664695

CR Number:   664695 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) 12.0.1 3317 01 Apr 2011 Fixed 12.0.0 2665 01 Apr 2011 Fixed 11.0.1 2584 01 Apr 2011 Fixed Description In rare situations, the server could have erroneously reported the error "Not enough memory" at startup. This problem has been corrected.

CR:664702

CR Number:   664702 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 3343 03 May 2011 Fixed 12.0.0 2678 03 May 2011 Fixed Description Queries using the spatial cast function TREAT( type1 AS type2 ) could have failed to return a syntax error when it was used incorrectly, and instead could have returned meaningless result sets. This has been fixed.

CR:664865

CR Number:   664865 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 2584 04 Apr 2011 Fixed Description In rare timing dependent cases, after a primary server relinquished ownership and had became the mirror server, it may not have received log page updates from the new primary. A high availability primary server relinquishes ownership when the partner is preferred, or due to a ALTER DATABASE SET PARTNER FAILOVER statement. If this problem occurred, restarting the mirror server would have caused it to start receiving log updates again. This has been fixed.