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

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

CR:690734

CR Number:   690734 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 3504 16 Nov 2011 Fixed Description The MIN and MAX aggregate functions would have returned an error when using an argument of type "timestamp with time zone" or "xml": Cannot convert timestamp with time zone to a numeric or Cannot convert xml to a numeric Further, using an "numeric" before computing the aggregate. This has been fixed. The MIN and MAX aggregates no longer attempt to cast these types to "numeric".

CR:690768

CR Number:   690768 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 3527 15 Dec 2011 Fixed 11.0.1 2729 15 Dec 2011 Fixed Description In order to prevent the possibility of having two primary servers running at the same time when there was no connection between the two partners, the arbiter would have refused a role switch from "mirror" to "primary" if it had a connection to the current primary. If a mirroring partner server was unable to connect to its partner server after the connection dropped, it was possible for the server to be unable to decide whether to take the role of primary or mirror server. A work around for this problem was to use the syntax "ALTER DATABASE <mymirroreddb> FORCE START" to force the database to start up as primary, and should only have been used if there was no other primary server running. This problem has been fixed, and the server should now be able to decide to take a role of either "primary" or "mirror" server.

CR:691036

CR Number:   691036 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 3506 18 Nov 2011 Fixed 11.0.1 2714 18 Nov 2011 Fixed Description When using the -sf server option to disable certain features other than "database", the CREATE DATABASE statement could have failed. This has been fixed.

CR:691040

CR Number:   691040 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 3748 18 Jun 2012 Fixed Description When fetchingd a string value containing trailing blanks from a proxy table, the trailing blanks would have been stripped. This problem has now been fixed and the string value will be exactly as returned by the underlying driver.

CR:691106

CR Number:   691106 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 3508 21 Nov 2011 Fixed Description The Relay Server Outbound Enabler's down channel would have responded slowly to new requests when there were on-going heavy downloads. This has been fixed by internal tuning of the Outbound Enabler's down channel. In testing, two concurrent 1G reponses were making the Outbound Enabler take 18 sec to satisfy another pair of clients waiting for 10x10k responses. After tuning, it took only 0.5 sec to satisfy the lighter responses without jeopardizing the aggregated download throughput.

CR:691167

CR Number:   691167 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 3507 21 Nov 2011 Fixed Description The request timing counters record the number of times, and the duration, a connection blocks waiting for various resources (disk accesses, locks, etc.). These counters were normally only available when the server was run with the -zt option, or when enabled with sa_server_option('RequestTiming', 'on'). As of this change, the ReqTimeBlockIO and ReqCountBlockIO properties are always available, regardless of the -zt setting. These properties are cheap to maintain, relative to the others, because the time required to wait for a disk access is much larger than that required to update the property.

CR:691168

CR Number:   691168 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 3508 21 Nov 2011 Fixed Description Load table operations were not permitted on temporary tables in a read-only database, even though other DML operations (INSERT/UPDATE/DELETE/TRUNCATE) were. This has been fixed. Note, as expected no data is logged to the transaction log in this case.

CR:691178

CR Number:   691178 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 3508 21 Nov 2011 Fixed 11.0.1 2716 21 Nov 2011 Fixed Description Attempting to make a Kerberos connection with a large Kerberos ticket could have failed with the error "Kerberos login failed". This would have occurred with a Kerberos ticket size approaching 8K, which was possible if the ticket was part of a large number of Active Directory groups. This has been fixed.

CR:691204

CR Number:   691204 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 3512 25 Nov 2011 Fixed Description In a high availability mirroring configuration, it is possible to drop the mirror server definition for a partner server currently acting as a mirror. If the dropped server later tried to connect to the primary server as a copy node, the primary server would still have thought the server was its partner, rather than a copy node. This has been fixed. Also, in a read-only scale out mirroring configuration, it is possible to drop the mirror server definition for a copy node. If that copy node was connected to the primary server at the time of the drop, the mirror server definition would not have been removed from the system tables. This to has been fixed.

CR:691207

CR Number:   691207 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 3508 22 Nov 2011 Fixed Description An ArrayIndexOutOfBoundsException could have occurred when reconnecting to an UltraLiteJ database if a previous connection had used a large amount of storage for temporary tables. This has been fixed.

CR:691215

CR Number:   691215 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 3513 28 Nov 2011 Fixed 12.0.0 2767 28 Nov 2011 Fixed Description Different system catalog views, DESCRIBE, and the dbunload schema information, showed different base type names for the domain Signed Integer. The base type names shown were "int" or "integer". This has been fixed. Now the base type name "integer" is consistently returned.

CR:691304

CR Number:   691304 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 3509 22 Nov 2011 Fixed Description The changes for Engineering case 686407 introduced a problem for shared memory connections where calling connection_property( 'LastReqTime' ) could have reported an inaccurate value. This has been fixed.

CR:691322

CR Number:   691322 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 3512 22 Nov 2011 Fixed Description The ENCRYPTED KEY option of the OPENSTRING statement was recently extended to permit the encryption key to be specified as a variable (see Engineering case 688888). In certain scenarios this feature could have caused either a crash, or an inappropriate error - SQLCODE -851 "Decryption error: Missing encryption key". This has been fixed.

CR:691327

CR Number:   691327 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3513 01 Dec 2011 Fixed 11.0.1 2721 01 Dec 2011 Fixed Description If the Notifier had encountered an unexpected error (such as a deadlock) when executing one of the Notifier events, subsequent attempts to execute the same Notifier Event would have resulted in an "Invalid Cursor State" error. This has been corrected so that the Notifier no longer reports the "Invalid Cursor State" error on subsequent attempts. Stopping and starting the MobiLink Server would also have resolved the issue.

CR:691453

CR Number:   691453 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) 09 Sep 2013 Fixed Description The functions Upper(), UCase(), Lower(), and LCase() could have incorrectly described the length of the output based on the length of the input if input collation was UCA. This has been fixed. Output is now described as LONG (N)VARCHAR.

CR:691589

CR Number:   691589 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 3512 25 Nov 2011 Fixed Description 1. ALTER TABLE would have allowed the addition of a UNIQUE constraint with nullable columns. This would have resulted in corruption of row store for the table, and would have lead to ArrayIndexOutOfBounds exceptions or corrupt data being read. 2. ALTER TABLE ADD constraint would not have added existing table rows to the new index. SELECT with ORDER BY using the new constraint would have returned less rows, and it was possible to INSERT rows that violated the constraint. 3. ALTER TABLE ALTER column would not have properly modified the column definition. 4. ALTER TABLE ADD column, DROP column or ALTER column, would have corrupted the in-memory state when lazy loading, resulting in SQLE_ERROR in subsequent operations on a given table. All the above issues have been corrected.

CR:691654

CR Number:   691654 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 3512 25 Nov 2011 Fixed 11.0.1 2718 25 Nov 2011 Fixed Description MobiLink clients that output localized error messages, now output a more detailed error message for connection failures on Windows desktop and devices, in addition to doing so for network read and write errors as they did before.

CR:691657

CR Number:   691657 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 3512 30 Nov 2011 Fixed 11.0.1 2718 30 Nov 2011 Fixed Description When using the Deployment Wizard, a temporary list of files is generated to pass over to makecab.exe based on the temporary directory path (%TMP%); e.g. makecab.exe /F C:\DOCUME~1\user\Local Settings\Temp\1\sql6.tmp. If the %TMP% variable contained a space, this would not work correctly, although the MSI file would still have been generated, but it would not have contained the necessary files. This has been fixed.

CR:691662

CR Number:   691662 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 3516 28 Nov 2011 Fixed Description DELETE query blocks (e.g. a main query block in a DELETE statement or a query block of a DML DELETE derived table) were restricted from flattening subqueries defined in the WHERE clause. An exception was that subquery flattening was done if and only if the cardinality of the DELETE query block was not affected. The restriction has now been removed, which may significantly improve the performance of some DELETE statments. With this change, any subquery which qualifies for flattening is flattened similar with SELECT/UPDATE query blocks.

CR:691732

CR Number:   691732 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 3625 28 Nov 2011 Fixed Description The database server now accepts the -gta command line option to control which logical processors the database server is permitted to use. The argument to -gta is a comma-separated list of processor numbers and/or ranges. For example: -gta 3,5-7 allows the database server to run on processors 3, 5, 6 and 7. The lower endpoint of a range may be omitted in which case it is assumed to be zero. The upper endpoint of a range may be omitted in which case it is assumed to be the highest cpu known to the OS. The database server will only use logical processors specified by -gta but it may not use all of them if the license does not allow it, or if one or more of the specified logical processors does not exist or is offline. If the set of processors specified by -gta exceeds the license limits, the server will use the lowest-numbered logical processors specified by -gta up to but not exceeding the license limits. In particular, the server does not choose logical processors in the order listed by -gta and it does not attempt to maximize concurrency within the license limit and the specified -gta option. If the set of processors specified by -gta does not match any online processors, the server acts as if -gta was not specified and uses up to the licensed number of processors starting at processor 0. Note that -gta cannot be used at the same time as -gt or -gtc. A usage message will be displayed when -gta is used with either -gt or -gtc.

CR:691736

CR Number:   691736 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3514 29 Nov 2011 Fixed Description When connected to a version 11 or earlier database, clicking the database's Overview panel would have displayed a "Table 'sysmirrorserver' not found" error. This has been fixed. A check of database version has now been added before querying the SYS.SYSMIRRORSERVER table.

CR:691739

CR Number:   691739 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 3513 28 Nov 2011 Fixed Description The detailed Relay Server status page, via the rs_admin.dll and rs_monitor.dll, were showing a heading and an empty list of fully available farms when there were no fully available farms. This has now been changed to not show the heading when the list is empty. The issue with partially available farms and unavailable farms has also been fixed.

CR:691879

CR Number:   691879 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 3530 29 Nov 2011 Fixed Description If an IPv6 address was used in the HOST or LINKS parameters of a connection string, on a machine that did not support IPv6, the client would have displayed the message "No IP address found for <IPv6 address>". This has been fixed. The error message will now read "No valid host names or addresses given". If the LOG= parameter is also used, the message "Ignoring IPv6 address <IPv6 address>" is written to the log for each IPv6 address found.

CR:691891

CR Number:   691891 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3514 30 Nov 2011 Fixed Description If all the consolidated tables were already mapped in a synchronization, and the New Table Mappings menu or toolbar button was used, the user would have been incorrectly prompted to update the remote schema instead of the consolidated schema. Also, unchecking the option to add a table to the remote schema when adding a table mapping, would have resulted in the new table mapping having no remote table. These problems have now been fixed.

CR:691893

CR Number:   691893 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 3513 30 Nov 2011 Fixed Description When installing an MSI file created by the Deployment wizard, the install would have partially completed and then failed, rolling back the install. This has been fixed.

CR:691976

CR Number:   691976 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 3517 07 May 2013 Fixed Description Aggregated download throughput, using one or more Outbound Enablers, has been improved significantly across all kinds of loads when there is bandwidth left in the link to the Relay Server. Running multiple OEs still remains an option to further improve throughput over a single OE. In our test environment, it now takes about 12 OEs in order to become network bound. Previously, even with 64 OEs with network bounding client load (i.e. RS/OE slows down the traffic to the point that it is no longer network bound) it was not possible to max-out the link. When the load is not sufficient to cause a network bounding situation, the Relay Server can now achieve close to 90% of the direct throughput where the clients are directly accessing the backend server.

CR:691979

CR Number:   691979 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3515 30 Nov 2011 Fixed Description The SQL Anywhere JDBC 4 Driver (sajdbc4.jar) now contains the proper manifest information to allow it to be loaded as an OSGI bundle.

CR:692013

CR Number:   692013 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 3517 02 Dec 2011 Fixed Description If a copy node in a read-only scale out setup was converted to be a partner mirror server, the primary mirror server could not have been restarted. This has been fixed.

CR:692127

CR Number:   692127 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 3517 01 Dec 2011 Fixed Description A new database server property, 'ProcessID', has been added. This proberty returns the PID of the server process.

CR:692216

CR Number:   692216 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 3519 02 Dec 2011 Fixed 11.0.1 2724 02 Dec 2011 Fixed Description A problem with TDS secure logins has been corrected.

CR:692243

CR Number:   692243 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 3518 05 Dec 2011 Fixed Description The [NOT|AUTO] COMPRESSED option is now supported in the OPTIONS list of the OPENSTRING clause. This is useful for reading in files created using UNLOAD with the COMPRESSED option.

CR:692249

CR Number:   692249 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) 12.0.1 3512 05 Dec 2011 Fixed Description On Mac OS X 10.7 Lion, the Java administration tools (Sybase Central, Interactive SQL, etc) would have silently failed if Java was not installed. Previous versions of Mac OS X included a Java runtime, but on Lion it is a separately installed component. Use the following method to initiate the Java runtime installation or confirm it is currently installed: 1.Go to Applications > Utilities > Java Preferences. 2.Open the Java Preferences. 3.If Java is not installed, you receive the following message: To open Java Preferences," you need a Java runtime. Would you like to install one now? 4.Click Install and follow the prompts. The Java runtime is downloaded and installed.

CR:692307

CR Number:   692307 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 3534 09 Jan 2012 Fixed 11.0.1 2735 09 Jan 2012 Fixed Description In blank padded and case insensitive databases using INSERT ON EXISTING UPDATE when updating a value which was logically equivalent but physically different could have failed due to constrain violations. This has been fixed. The server now does constraint checking using logical representations.

CR:692340

CR Number:   692340 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 3519 05 Dec 2011 Fixed 11.0.1 2724 05 Dec 2011 Fixed Description Machine and OS information have now been added to the Relay Server Outbound Enabler log. As well, timezone offset information has been added to the Relay Server and the Outbound Enabler logs.

CR:692342

CR Number:   692342 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 3520 06 Dec 2011 Failed Description Attempting to start the Relay Server Outbound Enabler with the command line option "-cs status_url" would have failed. This has been fixed and a usage text for -cs status_url, which was missing, has been added."

CR:692346

CR Number:   692346 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 3519 08 Dec 2011 Fixed 11.0.1 2725 08 Dec 2011 Fixed Description The Relay Server Outbound Enabler would have crashed after showing the usage text due to an invalid parameter. This has been fixed.

CR:692376

CR Number:   692376 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 3525 12 Dec 2011 Fixed Description After the changes for Engineering case 666434 ("dbisqlc could report errors when using output redirection for nested READ statements"), dbisqlc did not always correctly close all files opened for READ statements. If enough files were opened for READ statements during a session, dbisqlc could have reported "too many open files". This problem has been fixed.

CR:692504

CR Number:   692504 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 3520 09 Dec 2011 Fixed 12.0.0 2768 09 Dec 2011 Fixed 11.0.1 2725 09 Dec 2011 Fixed Description Entity Famework queries could have returned incorrect result when using parameters. This has been fixed.

CR:692583

CR Number:   692583 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 3524 12 Dec 2011 Fixed 11.0.1 2726 12 Dec 2011 Fixed 9.0.2 4050 12 Dec 2011 Fixed Description In some rare cases, the server would have hung when a connection queried another connection's LastStatement property. This has been fixed. The work-around is to not use the -zl command line option, or to turn off the RememberLastStatement server option.

CR:692598

CR Number:   692598 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 3522 12 Dec 2011 Fixed 11.0.1 2725 12 Dec 2011 Fixed Description An HTTPS synchronization could have failed on 64-bit Windows with STREAM_ERROR_SECURE_HANDSHAKE, depending on what trusted certificates were provided. This failure would have been more likely to occur when using the OS's CA certificate store. Certicom has provided updated libraries which correct this problem.

CR:692604

CR Number:   692604 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 3522 08 Dec 2011 Fixed 11.0.1 2725 08 Dec 2011 Fixed Description The server could have run out of memory after processing many HTTP requests. This has been fixed.

CR:692617

CR Number:   692617 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 3522 12 Dec 2011 Fixed 11.0.1 2725 12 Dec 2011 Fixed Description When the dbisqlc OUTPUT_FORMAT option 'ASCII' was renamed to 'TEXT' in version 11.0.0, the ability to generate the old format that dbisqlc called 'TEXT', which was fixed-width with column headers, was lost. Now, setting the OUTPUT_FORMAT to 'COLUMNS' will generate the old TEXT format.

CR:692867

CR Number:   692867 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 3524 09 Dec 2011 Fixed 11.0.1 2726 09 Dec 2011 Fixed Description The changes for Engineering case 677962 introduced a situation where, in rare timing dependent cases, a server could have hung when it was shutting down a database which was a high availability mirror or a copy node. This has been fixed.

CR:692899

CR Number:   692899 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 3524 12 Dec 2011 Fixed Description The changes for Engineering case 691204 introduced a problem where, in rare timing dependent cases, a high availability server or a copy node server could have crashed when shutting down, or when a DROP MIRROR SERVER statement was executed for a connected copy node.

CR:692981

CR Number:   692981 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 1808 29 Jan 2014 Fixed 12.0.1 4064 29 Jan 2014 Fixed Description Within stored procedure code, ARGN and some other builtins, IF expressions, conjunction or disjunction of predicates, could have eagerly evaluated all of the subselects in subexpressions. For example, expression ARGN( 1, (select 1/max(v) from t1), (select 1/min(k) from t2), (select 1/0 from dummy) ) would have evaluated all of the subselects (and returned an error) before noting that only the first of the subselects needed to be evaluated, and no error returned. This has been fixed. NOTE: The evaluation of subselects in procedural expressions now matches the evaluation in queries. For disjunctions and conjunctions, the order of evaluation of predicates is not guaranteed.

CR:693005

CR Number:   693005 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3525 12 Dec 2011 Fixed 11.0.1 2728 12 Dec 2011 Fixed Description If a JDBC application was launched, and no language resource DLL or shared object was located, the application would have gone into a loop consuming virtual memory until an "out-of-memory" error occurred. This problem has been fixed.

CR:693111

CR Number:   693111 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 3578 17 Feb 2012 Fixed 11.0.1 2761 17 Feb 2012 Fixed Description On Windows Mobile / CE, database files were not always properly flushed when necessary. The file metadata was the most likely data not to have been flushed, and assertion failure 201129 (File shorter than expected) was the most likely corruption to be seen in the event of a full power outage (eg if the CE device battery runs out). This problem has been fixed. Also, the server's '-u' (use buffered IO) command line switch was ignored on Unix platforms that supported direct IO. This problem has also been fixed.

CR:693135

CR Number:   693135 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 3526 14 Dec 2011 Fixed Description On Mac OS X, servers or client applications that made many TCP/IP connections requiring broadcasts to other servers could have sent many more UDP broadcast packets than required. In extreme cases, this could have flooded the network with UDP packets, affected an entire subnet's performance. Connection strings such as links=tcpip (with no broadcast=) or host=hostname (with no port) use broadcasting to other servers and could have had this problem. This has been fixed.

CR:693255

CR Number:   693255 Product Name:   SQL Remote for SQL Anywhere Product Component:   Extraction Utility for Adaptive Server Anywhere Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3527 14 Dec 2011 Fixed 11.0.1 2729 14 Dec 2011 Fixed Description If the publisher's address for a database contained a UNC path, or if the address for a remote user contained a UNC path, the Unload and Extraction utilities would have failed to escape the string properly, resulting in an address in the new database with missing backslash characters. This has now been fixed.

CR:693319

CR Number:   693319 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) 16.0.0 1516 19 Apr 2013 Fixed 12.0.1 3889 19 Apr 2013 Fixed 11.0.1 2973 19 Apr 2013 Fixed Description The sql functions set_bit() and get_bit() incorrectly accepted the value 0 for the bit-position parameter. This has been fixed. Now these functions return an error.

CR:693325

CR Number:   693325 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 3528 15 Dec 2011 Fixed 12.0.0 2770 15 Dec 2011 Fixed Description The MobiLink replay utility (mlreplay) could have crashed when the version of the recorded protocol was incompatible with the version of the replay utility replaying it. This has now been fixed.

CR:693344

CR Number:   693344 Product Name:   MobiLink Product Component:   Synchronization Server Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3540 11 Jan 2012 Fixed Description The MobiLink server and clients now support certificates signed using SHA-2. Previously, only MD5 and SHA-1 were supported. Also, the Certificate Viewer utility (viewcert) will now also correctly display the signature algorithm for certificates signed using SHA-2.

CR:693418

CR Number:   693418 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 3528 16 Dec 2011 Fixed Description A partner mirror server could have hung when stopping the mirrored database in rare timing dependent cases after executing an ALTER MIRROR SERVER for the arbiter server. This problem was introduced by the changes made for Engineering case 688291 and has now been fixed.

CR:693422

CR Number:   693422 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 1758 09 Dec 2013 Fixed 12.0.1 4031 09 Dec 2013 Fixed Description The default value specified in a CREATE [ OR REPLACE ] VARIABLE statement within a procedure, function, or trigger would have been ignored. Example: create or replace procedure foo () begin create or replace variable @v int = 123; end; call foo(); select @v; -- should return 123 but would have returned NULL This has been fixed. As a workaround set the default or initial value for the variable in a separate statement after the variable has been created.

CR:693539

CR Number:   693539 Product Name:   SQL Anywhere Product Component:   DBLIB Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3529 16 Dec 2011 Fixed 12.0.0 2770 16 Dec 2011 Fixed 11.0.1 2730 16 Dec 2011 Fixed Description The changes for Engineering case 635466 introduced a problem where, on machines under heavy load, TCP connection attempts could have failed with an incorrect error code. On certain operating systems, the connection attempt could have hung. This has been fixed.

CR:693560

CR Number:   693560 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 3713 17 Jan 2012 Fixed 12.0.0 2785 29 Mar 2012 Fixed 12.0.0 2786 29 Mar 2012 Fixed 10.0.1 4309 29 Mar 2012 Fixed Description Under very rare circumstances, a server could hang if it had a large number of processors and was executing a query with a parallel hash join. This was more likely on systems with large numbers of cores (more than 8). This has been fixed. A workaround is to disable intra-query parallelism by setting option MAX_QUERY_TASKS=1. (This only needs to be done for the statement or connection experiencing the problem, if it can be isolated.)

CR:693569

CR Number:   693569 Product Name:   UltraLite Product Component:   Sample Application Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3529 19 Dec 2011 Fixed Description When the 'Names' sample was loaded into Xcode 4.2, several warnings would have been reported. Even after this change, there will still be a prompt to remove the obsolete 'PREBINDING' build setting. It is recommended that this build setting be removed. The other warnings have been addressed. The most significant change is that the project format has been upgraded to Xcode 3.2-compatible format. Some other minor enhancements have also been made to the sample, such as specifying the UltraLite temp_dir. See the DataAccess class' openConnection method for more details.

CR:693579

CR Number:   693579 Product Name:   MobiLink Product Component:   Monitor Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3520 20 Dec 2011 Fixed Description When using the "Export to Database" functionality of the MobiLink Monitor on a 64-bit Linux systems, a dialog with an exception like the following would have been displayed: Error! The DBLIB library could not be loaded. This can happen if your SQL Anywhere installation has been corrupted. You will not be able to search for database servers. /opt/sqlanywhere12/lib32/libdblib12_r.so.1: /opt/sqlanywhere12/lib32/libdblib12_r.so.1: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch) Dismissing the dialog would allow the Monitor to continue, but the "Find" button would not have been available to search for SQL Anywhere database servers. Workaround: . /opt/sqlanywhere12/bin64/sa_config.sh export LD_LIBRARY_PATH=/opt/sqlanywhere12/lib64:$LD_LIBRARY_PATH /opt/sqlanywhere12/bin64/mlmon

CR:693670

CR Number:   693670 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 3531 20 Dec 2011 Fixed Description When a copy node server in a mirroring setup was not running an arbiter or partner server for another database, any connections from a server running mirroring to the copy node would have consistently dropped and reconnected for no apparent reason. This has been fixed.

CR:693690

CR Number:   693690 Product Name:   UltraLite Product Component:   Sample Application Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3530 20 Dec 2011 Fixed Description When the 'CustDB' sample was loaded into Xcode 4.2, several warnings would have been reported. Even after this change, there will still be a prompt to remove the obsolete 'PREBINDING' build setting. It is recommended that this build setting be removed. The other warnings have been addressed. The most significant change is that the project format has been upgraded to Xcode 3.2-compatible format. Some other minor enhancements have also been made to the sample, such as specifying the UltraLite temp_dir. See the DataAccess class' openConnection method for more details.

CR:693819

CR Number:   693819 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 3532 21 Dec 2011 Fixed 12.0.0 2770 21 Dec 2011 Fixed 11.0.1 2732 21 Dec 2011 Fixed Description When the server was running with the -fips command line option (Requires that only FIPS-approved algorithms should be used for strong database and communication encryption), it was still able to start simple-encrypted databases. This has been fixed, such databases will now fail to start.

CR:693900

CR Number:   693900 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) 12.0.1 3531 21 Dec 2011 Fixed Description The SQL Anywhere Monitor database gathers monitoring data over time, and this data is reduced according to the maintenance settings. If data reduction settings allowed more data to be gathered than the default settings, when the maintenance plan did run it may not have been able to successfully prune the gathered data. This has been fixed.

CR:693917

CR Number:   693917 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 3591 01 Mar 2012 Fixed Description If a copy node in a mirroring setup became unresponsive, it was possible for its parent to hang. This has been fixed.

CR:693928

CR Number:   693928 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3537 05 Jan 2012 Fixed Description When the StartServer method in the dbmlsync API is used to start a dbmlsync server, the dbmlsync commandline is now obfuscated making it harder for someone with access to the machine to discover the dbmlsync commandline.

CR:693938

CR Number:   693938 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 3533 22 Dec 2011 Fixed 11.0.1 2734 22 Dec 2011 Fixed Description In very rare circumstances, the server could have become deadlocked or hung. In some cases , database mirroring would have been involved and very specific timing was required; however, the problem could have occurred in other situations and would also have required very specific timing. This problem has now been fixed.

CR:693964

CR Number:   693964 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 3851 30 Jan 2013 Fixed Description A user that did not have DBA authority was able to alter a SQL procedure that they owned into an external or external environment stored procedure. This problem has now been fixed.

CR:693999

CR Number:   693999 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 3533 22 Dec 2011 Fixed Description When using the Unload utility (dbunload), if an APPINFO connection parameter was specified for the source database (-c option), the APPINFO value was ignored and a warning message printed stating such. This bahaviour has now been changed, the APPINFO value is now passed to the source database and a warning message is printed stating that the rebuild may fail if the source database has an older file format (version 9.0 or older). Connections to the target database (-ac option) are unaffected by this change. Both the previous and new behaviour is to pass the APPINFO value to the target database.

CR:694002

CR Number:   694002 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 3533 22 Dec 2011 Fixed 11.0.1 2734 22 Dec 2011 Fixed Description In extremely rare timing dependent cases, the server could have hung when the db_property function was called. The only known case of this occurring involved mirror servers, but this problem may have affected servers not involved in mirroring. This has now been fixed.

CR:694022

CR Number:   694022 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 3533 03 Jan 2012 Fixed Description In UltraLiteJ for Android, the API StreamHTTPParms.setExtraParameters( String ) has now been added. The classes StreamHTTPParms/StreamHTTPSParms contain a number of methods to set MobiLink client network protocol options as properties, eg. setHost( String ). However, there were no methods to cover all possible MobiLink client network protocol options. This API can now be used to specify a semi-colon-delimted list of options that are appended to the options that are generated by the property settings for the class. The meaning of the option list for this API is as specified in the documentation of MobiLink client network protocol options.

CR:694137

CR Number:   694137 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 3534 03 Jan 2012 Fixed 12.0.0 2771 03 Jan 2012 Fixed 11.0.1 2734 03 Jan 2012 Fixed Description There were two problems with attempting to encrypt a table using the ALTER TABLE <table_name> ENCRYPTED statement: 1. Executing the ALTER TABLE statement incorrectly succeeded on a database that did not support encrypted tables (i.e. one that is not encrypted or fully encrypted). 2. If a database was created with version 10 to support encrypted databases, but was being executed on a version 11 or later server, the same ALTER TABLE statement would have fail with error -1047 "This database does not support encrypted tables". These problems have now been fixed. In the first case, the ALTER statement will now return error -1047, and in the second case, the ALTER statement will succeed.

CR:694143

CR Number:   694143 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 3536 05 Jan 2012 Fixed 12.0.0 2772 05 Jan 2012 Fixed 11.0.1 2734 05 Jan 2012 Fixed Description When using the CREATE ENCRYPTED TABLE DATABASE statement on a fully encrypted database, the resulting database had all table and index pages encrypted, rather than only the pages for encrypted system tables. This has been fixed.

CR:694165

CR Number:   694165 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 3724 03 May 2012 Fixed Description An interactive quick setup feature has been added to help users running on an Apache web server to configure the web server for Relay Server, create a demo application, and generate a Quick Reference guide. This quick setup is divided into two main steps: 1- Configure the Apache web server for Relay Server Run ap-setup.sh script, which consists of the following sections: 1. Introduction 2. Validation 3. Create Backup 4. Deploy the Relay Server 5. Deploy the SimpleTestApp page and Quick Reference 6. Introduction to test setup script (part two) 2- Create and start Relay Server test services Run rs-test-setup.sh script, which consists of the following sections: 1. Introduction 2. Create and deploy Relay Server and Outbound Enabler test services 3. Start the Apache web server and the test services 4. Launch the SimpleTestApp 5. Launch the Relay Server status page 6. Generate and launch the Quick Reference guide 7. Shut down

CR:694466

CR Number:   694466 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3533 04 Jan 2012 Fixed Description The Compare Databases window could have reported syntactically-distinct, yet semantically-equivalent, differences between the two databases. The differences were limited to the ordering of the following: 1. Authorities for a user or group 2. Option name-value pairs for a login policy 3. Tables for a publication 4. Columns for an article 5. Option name-value pairs for a mirror server In all of the above cases, the ordering was irrelevant; however, the tool could have reported differences because the comparison could have generated random orderings. For example: GRANT CONNECT,DBA,RESOURCE TO "DBA" IDENTIFIED BY ... vs: GRANT CONNECT,RESOURCE,DBA TO "DBA" IDENTIFIED BY ... These have been fixed. The comparison now provides a consistent ordering as follows: 1. User and group authorities are ordered by authority name. 2. Login policy options are ordered by option name. 3. Publication tables are ordered first by user name, then by table name. 4. Article columns are ordered by column id. 5. Mirror server options are ordered by option name.

CR:694468

CR Number:   694468 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3527 05 Jan 2012 Fixed Description Attempting to compare a tenant database with another database would have caused Sybase Central to crash. This has been fixed.

CR:694479

CR Number:   694479 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 3539 10 Jan 2012 Fixed 12.0.0 2772 10 Jan 2012 Fixed 11.0.1 2737 10 Jan 2012 Fixed Description Attempting to use a server or the Java-based administration tools with large amounts of memory on a Linux system with kernel versions between 3.0 and 3.3 may have resulted in improper system memory calculation. This problem could have manifest itself in many ways. The server may have reported insufficient memory, or may have reported a very low value for its cache size, even when a large amount of system memory is available, e.g.: 8192K of memory used for caching Minimum cache size: 8192K, maximum cache size: 8192K The Java-based administration tools may also report the following error: Invalid maximum heap size: -Xmx0m This has been fixed.

CR:694480

CR Number:   694480 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3527 05 Jan 2012 Fixed Description Selecting a tenant database's Login Mappings folder in the tree would have caused an error. This has been fixed.

CR:694489

CR Number:   694489 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 3535 04 Jan 2012 Fixed Description If a connect to a cloud tenant database was made in the Interactive SQL utility, or Sybase Central, by selecting an action of "Connect to a running database in a cloud" in the "Connect" dialog, and then the connection was disconnected, opening the "Connect" dialog again would not have had the "Action" box initially set to "Connect to a running database in a cloud". This has been corrected so that now it is.

CR:694491

CR Number:   694491 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 3535 04 Jan 2012 Fixed Description If the server's main heap was extremely large and fragmented, and/or an extremely large number of SQL objects had been referenced (ie a large number of table names, column names, etc), checkpoints could have been slower than necessary by using more CPU than necessary. Even in extreme cases, the delay might have been only a few seconds and might generally go unnoticed for normal checkpoints; however, execution of a long sequence of DDL statements that performed implicit checkpoints would have been observed as extremely slow. The problem was caused by some in-memory cleanup that must be performed by the server periodically and was performed on every checkpoint; however, this cleanup doesn't need to be performed when checkpoints are executed in quick succession. Now, SQL Anywhere will perform the cleanup during checkpoint at most once every twenty minutes.

CR:694574

CR Number:   694574 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 26 Sep 2012 Fixed Description The SQL Anywhere Ruby/DBI Driver(1.0.0) now supports the latest Ruby version(1.9.3-p194) and the dbi gem version(0.4.5). The DBI test suites for Ruby/DBI Driver(DBD) are verified and the following problems have been fixed. - dbh.convert_types = false did not return the String value properly. - incorrect value of "precision" and "scale" of the column_info for integer data type. - incorrect value of the number for the affected rows. Also rakefile is changed to use rdoc/task instead of rake/rdoctask(deprecated). New Ruby gem and source are posted under: https://rubygems.org/gems/dbd-sqlanywhere https://github.com/sqlanywhere

CR:694591

CR Number:   694591 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 3537 05 Jan 2012 Fixed Description When the search condition in an IF expression evaluates to UNKNOWN, the IF expression should return NULL (not the "else" branch). For example, the following statement returns (NULL,NULL) select a , if a=1 then 1 else 0 end if as b from openstring(value ',') with( a int ) D If an IF expression was used as an argument to a CASE expression where the predicate is known at open time, then the IF expression was incorrectly evaluated so that UNKNOWN was treated as FALSE, leading to the ELSE branch being returned instead of NULL. For example, the following statement incorrectly returned (NULL,0,0) instead of (NULL,NULL,NULL) select a , if a=1 then 1 else 0 end if as b , case when 1=1 then b end case c from openstring(value ',') with( a int ) D A similar problem could occur with an IF expression used as an argument to NULLIF. This problem has been corrected.

CR:694592

CR Number:   694592 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 3537 05 Jan 2012 Fixed Description Evaluating particular forms of expressions in procedural code could have caused a server crash. This has been fixed.

CR:694593

CR Number:   694593 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 3537 06 Jan 2012 Fixed Description When evaluating the DATENAME() builtin function, it was possible that the server could have crashed. This potential problem has not been observed, and it is now fixed.

CR:694594

CR Number:   694594 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 3537 05 Jan 2012 Fixed Description In some cases, statements that included a DML statement in the FROM clause could have missed some checking that is normally done on statements. This has been fixed.

CR:694605

CR Number:   694605 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 3536 05 Jan 2012 Fixed Description SUP's Sybase Control Center (SCC) may have reported a false positive Relay Server Outbound Enabler (RSOE) status when the up channel or down channel failed to make direct connection to individual Relay Servers in the farm for a sustained period of time when RSOE debug logging is turned on. This was due to RSOE suppressing reporting repeated errors while SCC was scanning only the tail of the RSOE log to determine status. The RSOE has now been changed to not suppress repeated errors for this issue.

CR:694658

CR Number:   694658 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Windows CE 2.11 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3540 12 Jan 2012 Fixed 11.0.1 2738 12 Jan 2012 Fixed Description If a double-precision floating-point object (SQLDOUBLE) was not aligned on an 8-byte boundary on a Windows Mobile ARM-based device, the SQL Anywhere ODBC driver would have incorrectly issued the following error message when an attempt was made to reference the object (for example, using SQLGetData()): [Sybase][ODBC Driver]Invalid string or buffer length On the ARM hardware platform, a double-precision value consists of two 32-bit words and, when held in memory, the two words must appear consecutively and must both be word-aligned (i.e., a multiple of 4). The ODBC driver has now been corrected to check for an alignment that is a multiple of 4, not 8.

CR:694933

CR Number:   694933 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 3547 24 Jan 2012 Fixed Description Execution of a statement could have crashed the server, or returned incorrect results, if the statement contained derived tables with INSERT, DELETE, UPDATE, MERGE query blocks, and either the updated object was a simple updatable view, or the statement was used inside stored procedures, function, triggers, views, or batch statement. This has been fixed.

CR:695079

CR Number:   695079 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3540 11 Jan 2012 Fixed 11.0.1 2738 11 Jan 2012 Fixed Description When connected via jConnect, the procedure used to query the primary key metadata of a table would have returned too many rows if the table had a primary key column that was also a foreign key reference to another table. This problem has now been fixed. Note, an ALTER DATABASE UPGRADE will need to be performed on existing databases in order to get the new jConnect metadata procedures.

CR:695082

CR Number:   695082 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 3549 24 Jan 2012 Fixed Description Execution of a query with a query block with a FROM clause that was empty, or contained only the DUMMY table, could have crashed the server if the WHERE clause of this query block contained an EXISTS() predicate which could have been flattened. This has been fixed.

CR:695084

CR Number:   695084 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 3540 23 Jan 2012 Fixed Description Execution of a CREATE PROCEDURE statement with a number a parameters that exceeded the limit would not have failed. Now, execution of such a statement will fail with the error: SYNTACTIC_LIMIT 54W01 -890. Note, the maximum number of parameters allowed is a function of the database page size. For example, for a page size of 4k, the limit is ~3620096 parameters.

CR:695095

CR Number:   695095 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 3551 23 Jan 2012 Fixed 11.0.1 2744 23 Jan 2012 Fixed Description When executing a REORGANIZE TABLE statement, the server could have unnecessarily allocated an amount of memory that was proportional to the number of rows in the table. These allocations could have affect performance, and could have caused the cache to grow or, if the cache grew to its limit, could have caused a 'dynamic memory exhausted' failure. This problem has been fixed.

CR:695119

CR Number:   695119 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 3553 11 Jan 2012 Fixed 12.0.0 2774 11 Jan 2012 Fixed 11.0.1 2747 11 Jan 2012 Fixed Description The MobiLink server would not have accepted any status-check requests sent by clients who had lost the last synchronization status. When a status-check request was received, the MobiLink server would have repoprted the error: [Sybase][ODBC Driver][SQL Anywhere]Authentication violation (ODBC State = 08001, Native error code = -98) and then failed the request when all the following conditions were met: 1) The consolidated database was running on an OEM version of a SQL Anywhere server; 2) The consolidated database had been restarted since the MobiLink server was started; and 3) A client required a status-check because it did not get a full response in the last sync request that contained an upload. These problem is fixed now. The immediate work around for this problem is to restart the MobiLink server.

CR:695213

CR Number:   695213 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 3541 11 Jan 2012 Fixed Description When running on Windows systems, the server would have returned the value of property('MachineName') truncated to 15 characters. This has been fixed so it will now return the full name.

CR:695214

CR Number:   695214 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 3540 11 Jan 2012 Fixed Description With UltraLiteJ for Android, a ULjException with code -735 (Invalid parameter) was thrown when using PreparedStatement.set() to set a String parameter with UTF-8 encoded length greater than or equal to 32 KB. This has been fixed. A workaround is to use PreparedStatement.getClobWriter() to get a Writer object, and use that to write the parameter value.

CR:695216

CR Number:   695216 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 3541 12 Jan 2012 Fixed 12.0.0 2773 12 Jan 2012 Fixed 11.0.1 2738 12 Jan 2012 Fixed Description If the server was started with a TLS/HTTPS identity file that required a password, but none was supplied, an unhelpful error message was given ("Error parsing certificate file, error code 20763"). This has been fixed; the error message is now "An identity password must be specified".

CR:695242

CR Number:   695242 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 3549 23 Jan 2012 Fixed 12.0.0 2774 23 Jan 2012 Fixed 11.0.1 2744 23 Jan 2012 Fixed Description On some systems with multiple physical processor packages (ie multiple sockets) using certain Intel x86/x64 processors, including Intel Xeon E5630, the detection of processor geometry could have been incorrect. Too few packages would have been detected but the correct number of logical processors would still have been detected (with some assigned to the incorrect package). This problem was similar to, but different from, Engineer case 666639, and has now been fixed.

CR:695258

CR Number:   695258 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 3579 23 Feb 2012 Fixed 11.0.1 2761 23 Feb 2012 Fixed Description A new connection-level property 'NumLocalTempTables' has been added that returns the number of local temporary tables in use by the connection. Note that even when a local temporary table is dropped or falls out of scope, it is still considered to be "in use" until the next commit.

CR:695370

CR Number:   695370 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 3543 13 Jan 2012 Fixed Description The MobiLink server could have crashed when using the DBRowReader or DBCommand interfaces in the MobiLink .NET-ODBC bridge, if varchar or binary columns longer than a few KB were used. This has been fixed.

CR:695495

CR Number:   695495 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 3547 17 Jan 2012 Fixed 11.0.1 2742 17 Jan 2012 Fixed Description When connected to an older 10.x database, creating a remote server and then attempting to utilize the remote server would likely have caused an incorrectly foreign key violation error. This problem has now been fixed.

CR:695497

CR Number:   695497 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 3546 16 Jan 2012 Fixed Description Only the status page via the rs_admin.dll and rs_mionitor.dll provides full breakdown of status of all farms and servers and the amount of info can be overwhelming for large deployment like hosting environment. The status page via rs_client.dll or rs_server.dll only provides a single Relay Server wide status summary, and the user cannot pinpoint their query to a specific farm for backend server. This change introduces the following two new query parameters for all status pages. ias-rs-farm=<backend-farm-id> ias-rs-server=<backend-server-id> Use of ias-rs-server requires ias-rs-farm to be specified as well. The comparison of the value of these parameters are case sensitive but the name of these parameters are case insensitive. These new parameter can be applied to the status page url via all of the 4 existing extensions and they can co-exist with the ias-rs-refresh-sec parameter. Example status page url: http:\\my.com\rs\admin\rs_admin.dll?ias-rs-farm=myfarm&ias-rs-server=myserver http:\\my.com\rs\client\rs_client.dll?ias-rs-farm=myfarm&ias-rs-status-refresh-sec=20 When addressing rs_client.dll or rs_server.dll while IAS-RS-SERVER is not specified, individual server status will still be reported but the server name are hidden by label of this format: "_#<enumeration>_". In the cases of farm or server not found. The status page will still response with basic RS server information together with an error reporting what was not found. In those cases, no status information of any kind are reported but the viewer can still verify if they have a successful access to the extension of their choice. The pin-pointed status url shares the pre-existing refresh control and it can be used as a basic service monitor in a browser.

CR:695549

CR Number:   695549 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 3718 16 Jan 2012 Fixed Description When the ias-rs-status-refresh-sec url query parameter was specified on a status page url, the Relay Server would have returned the error: HTTP 404 "Not Found". This has been fixed.