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

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

CR:717571

CR Number:   717571 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   5.0.00 Fixed Version Build Resolution Date Closure Code (If Appropriate) 23 Aug 2012 Fixed Description If the username given in the AUTHORIZATION clause of the CREATE SCHEMA statement did not match the current user, the statement succeeded anyway and the objects created were owned by the current user. This has been fixed so as to behave as documented, the userid must match the userid of the current user, an error will occur if it does not.

CR:717582

CR Number:   717582 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3782 23 Aug 2012 Fixed Description When running on Mac OS X and iOS systems, it is possible that writes to an UltraLite database file could have been reordered by the underlying hardware/storage device under certain circumstances, possibly resulting in a corrupt database file. This has been corrected by having UltraLite make extra calls to request the hardware complete writes in order when required.

CR:717689

CR Number:   717689 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 3782 24 Aug 2012 Fixed Description If an 11.x or 12.x database was upgraded using either the Upgrade utility, or ALTER DATABASE UPGRADE, then external environments would no longer have started. This problem has now been fixed. Note that in order to apply this fix, the database will need to be upgraded again once this fix has been properly deployed.

CR:717690

CR Number:   717690 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3782 24 Aug 2012 Fixed Description Certain applications often make decisions based on the set of data types returned when making a SQLGetTypeInfo() ODBC call or a DatabaseMetaData.getTypeInfo() JDBC call. An example of such an application is the "Export to ODBC Database" functionality in MS Access where the application will use the data type information returned by the SQLGetTypeInfo() call to decide what column types should be included in the subsequent CREATE TABLE statement. In some rare cases, the choices the application makes due to the existence of certain data types may not be the most appropriate and it is sometimes useful to hide the fact that the ODBC or JDBC driver supports certain data types. The new SuppressInfoForDataTypes connection option can be used for both the SQL Anywhere ODBC Driver and the SQL Anywhere JDBC Driver to instruct to the driver to not return data type information for certain data types. The set of data types to suppress should be specified as a comma separated list. For example, the application could have the following on the ODBC or JDBC connection string: SuppressInfoForDataTypes=nvarchar,long nvarchar;varbit The above would then instruct the driver that data type information for the nvarchar, long nvarchar and varbit data types should not be returned for this specific connection when the application makes a SQLGetTypeInfo() or DatabaseMetaData.getTypeInfo() call. It should be noted that the suppression only applies to returning data type information from the driver. The application is still free to use the data type in column declarations and when retrieving result sets.

CR:717694

CR Number:   717694 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 3782 24 Aug 2012 Fixed Description Execution times of prefetches increased when compared with previous releases. This has been fixed.

CR:717784

CR Number:   717784 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 3783 27 Aug 2012 Fixed 12.0.0 2807 27 Aug 2012 Fixed 11.0.1 2861 27 Aug 2012 Fixed Description On Windows 8 and Windows 2012 systems, the platform-related properties would have indicated an "unrecognized Windows version". Support for these two platforms has now been added.

CR:717881

CR Number:   717881 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Cloud Console Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.1 4246 28 Aug 2012 Fixed 1.0.0 3784 28 Aug 2012 Fixed Description When viewing backups for a host or a database, a sorted column would still have shown a sort arrow when switching to a new host or database, but the column would not be sorted. This has been fixed.

CR:717944

CR Number:   717944 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 3791 14 Sep 2012 Fixed 11.0.1 2872 14 Sep 2012 Fixed Description In rare cases, calling the system procedure sa_transactions(), may have lead to a server crash. This has been fixed.

CR:717965

CR Number:   717965 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Cloud Console Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.1 4247 29 Aug 2012 Fixed 1.0.0 3784 29 Aug 2012 Fixed Description The "Backups" and "Back Up & Restore" panels did not show a column indicating the backup result. If a backup failed, a file size of 0 was the only indication. Unfortunately, a pending backup also shows a file size of 0. A 'Backup Result' column has now been added, which will show and the file size is blank unless the backup succeeds.

CR:717966

CR Number:   717966 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 3787 29 Aug 2012 Fixed 11.0.1 2867 29 Aug 2012 Fixed Description The time to process an HTTP or HTTPS request that contained a large number of input variables may have been longer than expected. This has been fixed.

CR:718046

CR Number:   718046 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3787 06 Sep 2012 Fixed 11.0.1 2868 06 Sep 2012 Fixed Description When creating an ADO.NET Entity Data Model using an existing stored procedure, some of the SQL Anywhere data types were not mapped correctly. This would have been seen when clicking the "Get Column Information" button in the "Add Function Import..." dialog. This has been corrected.

CR:718122

CR Number:   718122 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 3785 31 Aug 2012 Fixed 11.0.1 2864 31 Aug 2012 Fixed Description If a connection updated a table and subsequently left a cursor open past a COMMIT or ROLLBACK, other connections would not have been able to lock the entire table in share mode (i.e. LOCK TABLE t IN SHARE MODE) until the updating connection closed the cursors and did a COMMIT or ROLLBACK. This has been fixed.

CR:718127

CR Number:   718127 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 3799 02 Oct 2012 Fixed Description When importing or exporting to an UltraLite database using the Interactive SQL utility, LONG BINARY and LONG VARCHAR datatypes could have been truncated or an error reported. This has now been fixed.

CR:718130

CR Number:   718130 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 31 Aug 2012 Fixed Description When using a Web browser to ping the MobiLink server, the "404 Not Found" response could have contained extra bytes at the end. This has been fixed.

CR:718270

CR Number:   718270 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 3786 04 Sep 2012 Fixed 11.0.1 2866 04 Sep 2012 Fixed Description In the Create User wizard, attempting to create a user without a password and setting the login policy to something other than "root" would have caused the login policy setting to be ignored. This has been fixed.

CR:718317

CR Number:   718317 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3787 05 Sep 2012 Fixed Description A query using sub-queries with a UNION may have returned incorrect results. For example: select (select 1) union select 2" the sub-query (select 1) was not evaluated properly. This has now been fixed.

CR:718369

CR Number:   718369 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 3787 05 Sep 2012 Fixed 11.0.1 2867 05 Sep 2012 Fixed Description Attempting to insert a string literal containing multi-byte characters into an nchar based proxy column may have actually inserted mangled data into the remote column, if the local database character set was not UTF8. This problem has now been fixed. Note that inserting multi-byte character data using an nchar based variable or column as the source works fine. As a result, using an nchar based variable instead of a string literal is a possible work around for this problem.

CR:718375

CR Number:   718375 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 3787 05 Sep 2012 Fixed Description In rare cases, a copy node whose parent was not the primary or root could have failed assertion 100927 immediately after a log rename. In very rare cases, a mirror or copy node that was automatically restarted immediately after a log rename could have incorrectly restarted as a non-mirrored read-write database. The automatic restart could have occurred for a number of reasons, including rare cases of a lost connection to the parent server. Both of these problems have now been fixed.

CR:718489

CR Number:   718489 Product Name:   SQL Anywhere Product Component:   Other Status:   Closed OS:   Generic Original Version:   10.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3788 07 Sep 2012 Fixed Description Calling a stored procedure from any driver that uses the SQL Anywhere C API runtime library (eg. python, perl, ruby) would have returned incorrect values for the second and subsequent string (binary, varchar, long binary, or long varchar) OUT parameters. All string prameters would have been given the value of the first string parameter. This has been fixed.

CR:718497

CR Number:   718497 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 3788 06 Sep 2012 Fixed Description Creating a REMOTE SERVER definition with a USING clause that contained both "DRIVER=SQL Anywhere Native" and "DSN=..." would have resulted in the connection string used to connect to the remote SA server not containing the items in the DSN entry. This problem has now been fixed.

CR:718525

CR Number:   718525 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 3788 07 Sep 2012 Fixed 11.0.1 2869 07 Sep 2012 Fixed Description In very rare situations, the server could crash when using the OPENSTRING clause, string concatenation, substring operation, or attempting to execute a LOAD TABLE statement. The problem was most likely to have occurred when cache pressure was very high. This problem has been fixed.

CR:718761

CR Number:   718761 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3790 13 Sep 2012 Fixed 11.0.1 2871 13 Sep 2012 Fixed Description SABulkCopy would have failed with an OutOfMemoryException when copying large tables using a DataReader. This problem has been fixed.

CR:718762

CR Number:   718762 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3790 12 Sep 2012 Fixed 11.0.1 2871 12 Sep 2012 Fixed Description The Function Import?construct within the Entity Framework would have failed with a NullReferenceException for return types of "None". This problem has been fixed.

CR:718875

CR Number:   718875 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 3791 17 Sep 2012 Fixed Description In a mirroring setup, if a copynode or the mirror was still connected to its parent or partner, and was busy receiving a lot of pages from its parent, and needed to restart for some reason, the server could have waited until it wasnt as busy before restarting. A mirrored database may need to restart in many situations. For example, a restart is required when a copynodes parent has changed, or when a mirror is converted to a copy node. This has been fixed, so the server will restart much sooner after deciding it needs to restart, and will not wait until there is a break in receiving information from its parent or partner.

CR:718970

CR Number:   718970 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Infrastructure Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.1 4364 17 Sep 2012 Fixed 1.0.0 3791 17 Sep 2012 Fixed Description Creating an incremental backup could have failed if the machine hosting the corresponding full backup was not currently running a server capable of running the database being backed up. This has been fixed. Now a full backup (to a different host) will be done. However, if the incremental backup is being done through a maintenance plan with a specific host name, no backup will be done.

CR:719080

CR Number:   719080 Product Name:   MobiLink Product Component:   ASA Client Status:   Closed OS:   Generic Original Version:   11.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3791 13 Sep 2012 Fixed Description If the MibiLink client executable (dbmlsync) had been located in a directory that was specified in the PATH environment variable that contained two consecutive backslashes (for example, c:\\sa12\bin64), the Dbmlsync .NET API could have failed to start the dbmlsync process. This problem has now been fixed. A workaround to this problem is to set the "server path" property using the SetProperty method to specify the location of the dbmlsync executable.

CR:719089

CR Number:   719089 Product Name:   SQL Anywhere Product Component:   JDBC Client Library Status:   Closed OS:   Linux Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3795 25 Sep 2012 Fixed 11.0.1 2876 25 Sep 2012 Fixed Description A JDBC application that connected using the SQL Anywhere JDBC driver, and then subsequently exited with a large number of connections still open, could in rare cases crash or hang. This problem has now been fixed.

CR:719105

CR Number:   719105 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 3791 17 Sep 2012 Fixed Description In some circumstances, the primary server in a mirroring setup may not have allowed the mirror to take over as primary when an ALTER DATABASE SET PARTNER FAILOVER occurred. The server would have waited until all active transactions were committed. This has been fixed. Now, the failover will occur as soon as the servers are synchronized, and the mirror has all the committed transactions from the primary. Any transactions that have not been committed will be lost when the failover occurs.

CR:719107

CR Number:   719107 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Infrastructure Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.1 4364 17 Sep 2012 Fixed 1.0.0 3791 17 Sep 2012 Fixed Description In the cloud, the FailoverToCloudPartner task could have been reported as cancelled, even if it ran successfully. This has been fixed so that the status of the FailoverToCloudPartner task should now be accurately reported.

CR:719111

CR Number:   719111 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 3791 14 Sep 2012 Fixed Description User-defined counters are implemented as UNSIGNED INTEGER, but their values could not be set or adjusted using values that were greater than 2147483647. This has been corrected so that values can now range up to 4294967295.

CR:719112

CR Number:   719112 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3792 17 Sep 2012 Fixed Description Data conversion errors could have occurred when passing DateTimeOffset parameters to a stored procedure using the Entity Framework function import. This problem has been fixed.

CR:719220

CR Number:   719220 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 3794 17 Sep 2012 Fixed 11.0.1 2875 17 Sep 2012 Fixed Description In rare timing dependent cases, the changes for Engineering case 713113 mau have caused a mirror or copy node to fail assertion 100927 when starting the database. The assertion text was "Transaction log page number 0x<first-hex-number> from parent or partner is not expected page number 0x<second-hex-number>", where the first-hex-number was one lower then second-hex-number. If this assertion failure occurred, restarting the mirror or copy node should succeed. This has been fixed.

CR:719292

CR Number:   719292 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 3792 18 Sep 2012 Fixed Description Attempting to connect to a database by specifying an IPv6 address would most likely have failed. This has been fixed. Note, in the Connect window, a new IPv6 address can be entered in the Host field. If the address ends in a colon and a port number, the host portion of the address must be enclosed in square brackets. This is as documented. An IPv6 address can also be entered without a port number and without square brackets in the Host field. When entering a port number in the Port field, the square brackets will be added automatically.

CR:719334

CR Number:   719334 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Microsoft Windows 2000 Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3811 01 Nov 2012 Fixed 11.0.1 2893 07 Nov 2012 Fixed Description The cardinality estimation for an index with descending (DESC) columns may have been incorrect. This has been fixed. The conditions for this issue to happen, for a query Q, were: 1 - The index on the table T was of the form <X1, ? Xk, ?gt; with k > 1 2 - The first k-1 columns in the prefix of the index had predicates of the form T.Xi = constant in the query Q 3 - The column k had the predicate of the form T.Xk \theta constantk (\theta n {<, <=, >, >=}), or T.Xk between constantk and constank+1 in the query Q 4 - The column T.Xk was declared DESC in the index.

CR:719385

CR Number:   719385 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 20 Sep 2012 Fixed Description The SQL Anywhere ADO.NET provider now supports Entity Framework 5. EF 5 is the latest release of Entity Framework. It comes with Visual Studio 2012, or it can be downloaded as Visual Studio 2012 NuGet package.

CR:719397

CR Number:   719397 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 3797 18 Sep 2012 Fixed 12.0.0 2812 18 Sep 2012 Fixed 11.0.1 2878 18 Sep 2012 Fixed Description Under rare conditions, the server or client library could have crashed when attempting an LDAP operation (eg. registering the server, searching LDAP for servers when connecting). This has been fixed.

CR:719402

CR Number:   719402 Product Name:   MobiLink Product Component:   iAS Branded ODBC Drivers Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3793 20 Sep 2012 Fixed 11.0.1 2874 20 Sep 2012 Fixed Description Messages generated by the iAS ODBC driver for Oracle could have contained unreadable characters at the end, if the message length was equal to or greater than 256 characters. This problem is now fixed.

CR:719422

CR Number:   719422 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 3792 19 Sep 2012 Fixed Description UltraLiteJ for Android now supports system events for: - Table modifications, - Commits, - Synchronization completion. An UltraLiteJ application registers and waits for system events on a Connection. However, events are system-wide so that a Connection can receive notifications of the above events that are triggered from Connections on other threads. An event is encapsulated by the following class: public interface ULjEvent { // event types final short TABLE_MODIFIED_EVENT = 1; final short COMMIT_EVENT = 2; final short SYNC_COMPLETE_EVENT = 3; /** * Returns the event type. */ short getType(); /** * Returns a named parameter for the event. */ String getParameter( String name ) throws ULjException; }; The following methods have been added to the Connection class: /** Waits for an event notification. * * This call blocks until a notification is received or until the given * wait period expires. To wait indefinitely, set the wait_ms parameter to * -1. To cancel a wait, use the cancelWaitForEvent method. * * @param waitms The time, in milliseconds to wait (block) before returning. * @return The event that occurred within the wait time, or null if no * notification was received within the wait time. * * @see ULjEvent * @see cancelWaitForEvent */ public ULjEvent waitForEvent( int wait_ms ) throws ULjException; /** Register to receive notifications of a system event. * * @param event_type The type of event to register for. * @param object_name The object to which the event applies. (for example, * a table name). * * @see ULjEvent */ public void registerForEvent( short event_type, String object_name ) throws ULjException; /** Unregister to receive notifications of a system event. * * @param event_type The type of event to unregister for. * @param object_name The object to which the event applies. (for example, * a table name). * * @see ULjEvent */ public void unregisterForEvent( short event_type, String object_name ) throws ULjException; /** Cancels any waitForEvent calls on this connection. * * @see waitForEvent */ public void cancelWaitForEvent() throws ULjException; Note that the object_name parameter of register/unregisterForEvent is only used for event type ULjEvent.TABLE_MODIFIED_EVENT. In that case the object_name is the table name for which to receive notifications of modifications, or "*" for all tables. Pass null for the object_name for the other event types.

CR:719484

CR Number:   719484 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 3811 07 Nov 2012 Fixed Description A query having a theta (subquery) predicate may have crashed the server during query optimization. One of the conditions for this issue to have occurred was that the subquerys select items and groupby expressions were base table columns of the same index, and the subquery was a grouped query block. For example: Select * from T where T.X = (select R.X where ? Group by R.Y) and there existed an index on R on columns <X,Y>. This has now been fixed.

CR:719503

CR Number:   719503 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 3793 19 Sep 2012 Fixed 11.0.1 2874 19 Sep 2012 Fixed Description The server would have failed assertion 107400 - Internal parse tree error, if a query used proxy tables and contained a common table expression in a derived table, and the derived table was flatted. This has been fixed

CR:719505

CR Number:   719505 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 3793 20 Sep 2012 Fixed Description UltraLiteJ for Android has a new method, DatabaseInfo.getNumberRowsToUpload( String pubList, int threshold ), that provides the same functionality as the UltraLiteC API ULConnection::CountUploadRows( const char * pubList, ul_u_long threshold ).

CR:719710

CR Number:   719710 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 3798 25 Sep 2012 Fixed 11.0.1 2879 25 Sep 2012 Fixed Description Executing an ALTER TABLE statement on an empty table could have caused a server crash on a subsequent table scan of the table. This has been fixed.

CR:719719

CR Number:   719719 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 3794 25 Sep 2012 Fixed Description When using the SQL Anywhere C API, the information returned by sql_column_info would always have indicated that nulls were not allowed. This has been fixed.

CR:719758

CR Number:   719758 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows 2000 Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3805 16 Oct 2012 Fixed 11.0.1 3792 16 Oct 2012 Fixed Description The .Net Provider could have incorrectly thrown an "Unknown PrimitiveTypeKind DateTimeOffset" exception. This has been fixed.

CR:719834

CR Number:   719834 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 3795 25 Sep 2012 Fixed Description The Relay Server Outbound Enabler was logging response bytes at verbosity 9, but should have been logging them at verbosity 5 or higher. This has been fixed.

CR:719932

CR Number:   719932 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 3796 26 Sep 2012 Fixed 11.0.1 2877 26 Sep 2012 Fixed Description In a mirroring setup during a forced failover, it was possible for the new mirror to get stuck in a situation where the database would print the following error to the console log: primary not available or mirror log longer than primary? and proceed to restart. This could often be fixed by executing a transaction on the new primary after the failover was complete. This bug has been fixed, and the mirror server should now start up without difficulty.

CR:720066

CR Number:   720066 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 3798 27 Sep 2012 Fixed Description If a connection could not be made to the root or primary server from a copy node that did not already have a mirror definition, the copy node could have crashed after about max_retry_connect_time from when the copy node was started. This has been fixed.

CR:720219

CR Number:   720219 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 3798 28 Sep 2012 Fixed Description Executing a SET MIRROR OPTION option-name = NULL statement would not have correctly changed the behavior of currently running databases for the auto_failover and synchronization_mode options. Once the database was restarted on a partner server, the option value would then have been correctly interpreted as the default value for the option. This has been fixed so that the default value for the option is effective immediately after the SET MIRROR OPTION option-name = NULL statement is executed or applied.

CR:720280

CR Number:   720280 Product Name:   SQL Anywhere Product Component:   Utilities Status:   Closed OS:   Solaris Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Trying to source the sa_config.csh script file (generated by the Unix installer) would have failed with the error "Missing ]". This has been fixed.

CR:720288

CR Number:   720288 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 3798 28 Sep 2012 Fixed Description The SQL Preprocesor (sqlpp) would have incorrectly reported a warning or possibly an error if the file it was preprocessing had static SQL containing "TIMESTAMP WITH TIME ZONE". The most likely sqlpp warning was "Warning! W2661 near 'with': Unrecognized SQL syntax". This has now been fixed.

CR:720298

CR Number:   720298 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 3799 01 Oct 2012 Fixed 11.0.1 2880 01 Oct 2012 Fixed Description Under rare circumstances, calling the system procedure sa_index_statistics() could have caused the server to crash. This has been fixed.

CR:720303

CR Number:   720303 Product Name:   MobiLink Product Component:   Java Plugin for Sybase Central Status:   Closed OS:   Microsoft Windows NT Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3816 05 Dec 2012 Fixed Description In a client-only installation, the Services wizard would not have allowed the creation of a Windows service. This was incorrect, as it prohibited creating a MobiLink service, and has been fixed.

CR:720384

CR Number:   720384 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 3799 01 Oct 2012 Fixed 11.0.1 2880 01 Oct 2012 Fixed Description Under very rare circumstances, the server may have crashed when running the procedure sp_forward_to_remote_server, or any of the Remote Data Access procedures (i.e sp_remote_columns, sp_remote_tables, etc). This has been fixed.

CR:720419

CR Number:   720419 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3800 03 Oct 2012 Fixed Description LONG VARCHAR columns could have contained incorrect results for the second and subsequent queries using that datatype.

CR:720462

CR Number:   720462 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 3802 09 Oct 2012 Fixed 11.0.1 2884 09 Oct 2012 Fixed Description Under very rare circumstances, the server may have crashed when running the system procedures sa_char_terms or sa_nchar_terms, or some internal text index related procedures, with invalid arguments. This has been fixed.

CR:720473

CR Number:   720473 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Generic Original Version:   8.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Oct 2012 Fixed Description An application that connected using either the SQL Anywhere ODBC Driver or the SQL Anywhere JDBC Driver, with a userid that did not have SELECT ANY TABLE privilege, would have retrieved the wrong result set when calling either SQLTables or DatabaseMetaData.getTables() when the request was for base tables only. In particular, dbo owned system tables would have been incorrectly returned in the result set. This problem did not exist if the application connected with a userid that had SELECT ANY TABLE privilege. The problem has now been fixed and dbo owned system table information no longer gets returned if the request explicitly asks for base table information only.

CR:720488

CR Number:   720488 Product Name:   UltraLiteJ Product Component:   Runtime Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 02 Oct 2012 Fixed Description When creating a config (class ConfigPersistent), setting a row score flush size greater than 0 would have turned on both row limiting and lazy loading, however this was not immediately reflected by getLazyLoadIndexes(). Furthermore, a subsequent call to setLazyLoadIndexes( false ) would not have turned off lazy loading as the row score flush size was still set. This has been fixed. ConfigPersistent.setRowScorFlushSize() with a value greater than zero immediately marks lazy loading as on. ConfigPersistent.setLazyLoadIndexes() with false immediately sets the row score flush size to zero.

CR:720489

CR Number:   720489 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 3801 05 Oct 2012 Fixed 11.0.1 2882 05 Oct 2012 Fixed Description In very rare timing dependent cases, when a high availability mirror was taking over as primary, it could have hung or failed assertions 100924 or 100925. In order for this to have occurred, the mirror must have had active read-only connections using temporary tables and performing commits or rollbacks, as well as certain other conditions. This has been fixed.

CR:720564

CR Number:   720564 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 3806 17 Oct 2012 Fixed Description If the MobiLink client (dbmlsync) was running on a schedule, the MobiLink Server could not be located, and dbmlsync did not know the status of the last synchronization, it was possible for dbmlsync to have shut down. The problem is now fixed, and dbmlsync will remain running on a schedule, even if the MobiLink Server cannot be located.

CR:720592

CR Number:   720592 Product Name:   SQL Anywhere Product Component:   OLEDB Client Library Status:   Closed OS:   Generic Original Version:   9.0.2 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3800 03 Oct 2012 Fixed 11.0.1 2881 03 Oct 2012 Fixed Description If the values 'SYSTEM TABLE', SYSTEM VIEW?or 'GLOBAL TEMPORARY' were specified as the TABLE_TYPE restriction for either of the SQL Anywhere OLE DB DBSCHEMA_TABLES or DBSCHEMA_TABLES_INFO rowsets, an empty rowset was returned. If TABLE? VIEW? or TEXT?was specified as the TABLE_TYPE restriction, there was no problem. This problem has been corrected. To correct the problem in an existing database, the Upgrade utility must be used once the problem resolution fix (EBF) has been installed.

CR:720607

CR Number:   720607 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 3800 04 Oct 2012 Fixed Description When the SQL Preprocessor was run with the "-e u" command line option (Flag syntax that is not supported by UltraLite) it would have incorrectly reported the TIMESTAMP WITH TIME ZONE syntax as a language extension. This has been fixed so that it is no longer reported as a language extension.

CR:720643

CR Number:   720643 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Solaris Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 04 Oct 2012 Presently Not Targeted For Any Future Release Of This Product Description -

CR:720725

CR Number:   720725 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 3801 05 Oct 2012 Fixed Description If a subquery using a LIKE predicate, scaned an index in reverse order but another earlier index scan used the index in forward order, or vice versa, the LIKE scan would have accessed the table in the wrong order. For example: SELECT c.name, d.b FROM fwd c, (SELECT TOP 2 name FROM fwd2 WHERE name LIKE a%?ORDER BY name ASC) AS d( b ) WHERE c.name LIKE j%?br> ORDER BY c.name DESC This has been fixed.

CR:720804

CR Number:   720804 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 3828 07 Dec 2012 Fixed 11.0.1 2910 07 Dec 2012 Fixed Description If a backwards index scan blocked on a locked row, it would have continued onto the next row after it resumed, rather than retrying the current row. This has been fixed.

CR:720811

CR Number:   720811 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 3801 09 Oct 2012 Fixed 11.0.1 2882 09 Oct 2012 Fixed Description A high availability mirror or a copy node server running on Windows could have failed assertion 112002 during a transaction log rename. This has been fixed. If the high availability mirror was busy applying log pages, failing over due to the other partner being preferred, or due to the ALTER DATABASE SET PARTNER FAILOVER statement, could have been delayed for a minute or more. This has also been fixed.

CR:721039

CR Number:   721039 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 3803 09 Oct 2012 Fixed 11.0.1 2885 09 Oct 2012 Fixed Description Dropping a connection that had previously made an external environment call to a connection scoped external environment, could, in very rare cases, have caused the server to crash. This problem has now been fixed.

CR:721068

CR Number:   721068 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 3815 10 Oct 2012 Fixed Description Under rare circumstances, a Statement interrupted by user?error could have been returned from parallel query executionm, instead of the correct runtime error. Other possible behaviours under the same circumstances were returning an Unexpected error?error, or a server crash. This has been fixed.

CR:721070

CR Number:   721070 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 3803 10 Oct 2012 Fixed 11.0.1 2885 10 Oct 2012 Fixed Description The REGEXP search condition and the REGEXP_SUBSTR function could have incorrectly matched or failed to match regular expressions with ^ or $ followed immediately by a character that had special meaning in a regular expression if it was escaped. For example, REGEXP_SUBSTR( 'A', '^A' ) was incorrectly returning NULL. This has been fixed.

CR:721288

CR Number:   721288 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 3804 11 Oct 2012 Fixed Description In rare cases, if a copy node was renaming the transaction log while a child copy node was requesting log pages, the parent copy node could have failed with "Fatal Error: Internal database error". Note that a child copy node only requests pages until the child has all the log pages that the parent has (after that the parent sends the updated log pages as they are written). Also, in very rare cases, if a copy node or mirror was renaming the transaction log while the connection to the parent or partner dropped, the could node or mirror could have crashed. These issues have now been fixed.

CR:721300

CR Number:   721300 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 1980 15 Jul 2014 Fixed 12.0.1 4139 15 Jul 2014 Fixed Description Copy nodes which used a partner server name as a parent (as opposed to the primary or mirror), could have failed to connect to this parent. In this case, the initial connection to the parent could have succeeded, but if the parent database or server was restarted, the copy node was unable to connect. This has been fixed.

CR:721318

CR Number:   721318 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 3804 12 Oct 2012 Fixed Description The changes for Engineering case 674232 broke JAX-WS support for multiple databases on a server. The generated WSDL document omitted the database name in the targetNamespace. For example, targetNamespace="http://localhost:8082/WS" instead of targetNamespace="http://localhost:8082/demo/WS". As a result, all the URL references to web services could have gone to the wrong database. It would have gone to the database that was started first. This problem can not be worked around using the DBN option, as follows: dbsrv12 -xs http(port=8082;dbn=test) "%SQLANYSAMP12%\demo.db" test.db as the targetNamespace is correct but the wsdlLocation is wrong. The correct workaround is to edit the source files generated by wsimport and make the corrections. This problem has been fixed.

CR:721394

CR Number:   721394 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 3809 29 Oct 2012 Fixed 11.0.1 2891 29 Oct 2012 Fixed Description The server may have failed assertions 111706, 111707, or 201200, if a procedure call was used in a SELECT statement, one of the specified arguments exceeded its declared parameter size, and the procedure used the argument in a DML statement. This has been fixed.

CR:721396

CR Number:   721396 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 3798 12 Oct 2012 Fixed Description Two new methods have now been added to UltraLiteJ for Android: PreparedStatement.getParameterCount() and PreparedStatement.getParameterType( int ).

CR:721398

CR Number:   721398 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 3803 12 Oct 2012 Fixed Description A new method, Connection.getState(), has been added to UltraLiteJ for Android for consistency with UltraLiteJ for BlackBerry.

CR:721401

CR Number:   721401 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 3804 12 Oct 2012 Fixed Description UltraLiteJ for Android now has the capability to get error parameters from ULjException objects. The methods ULjException.getParameterCount(), ULjException.getParameter( int ), SQLInfo.getParameterCount(), and SQLInfo.getParameter( int ) have been added.

CR:721437

CR Number:   721437 Product Name:   SQL Anywhere Product Component:   ISQL Status:   Closed OS:   Generic Original Version:   10.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3804 15 Oct 2012 Fixed 11.0.1 2886 15 Oct 2012 Fixed Description The "Check for Updates" menu item in the Interactive SQL utility, Sybase Central, and DBConsole would have always reported that the update server was unavailable if a network proxy was used to access the internet. This has been corrected so that now if an HTTP proxy is configured for the computer, the proxy will be used and the check for updates will succeed. Note that if the computer is set to automatically configure its proxy, the HTTP proxy must also be set explicitly for the update checker work function properly.

CR:721534

CR Number:   721534 Product Name:   SQL Anywhere Product Component:   ODBC Client Library Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3812 02 Nov 2012 Fixed Description If an application made a remote procedure call to an Oracle server, then the server would have incorrectly forced a commit operation to occur on the Oracle server. This problem has now been fixed.

CR:721582

CR Number:   721582 Product Name:   MobiLink Product Component:   Utilities Status:   Closed OS:   Generic Original Version:   9.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3806 16 Oct 2012 Fixed Description The usage description of the -sv switch for the MobiLink Listener utility for Windows devices (dblsn), was missing the placeholder of the script version. This has now been corrected.

CR:721637

CR Number:   721637 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3813 02 Nov 2012 Fixed 11.0.1 2894 02 Nov 2012 Fixed Description An ADO .Net application could have failed to fetch from a proxy table with blob columns. The error returned would have been: Cursor is restricted to FETCH NEXT operations? This problem has now been fixed.

CR:721757

CR Number:   721757 Product Name:   SQL Anywhere Product Component:   ADO.Net Managed Provider Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3809 26 Oct 2012 Fixed 11.0.1 2891 26 Oct 2012 Fixed Description The Password field in the connection string (file App.config) could have been inadvertently removed during execution when running the Entity Framework application. This problem has been fixed.

CR:721778

CR Number:   721778 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 3809 31 Oct 2012 Fixed Description When a connection was pooled and reused by SQL Anywhere's connection pooling, in some cases there were some behavior differences compared to getting a new (unpooled) connection. Note that the type of connection pooling affected is controlled by the ConnectionPool connection parameter and enabled by default, but this connection pooling is not used by the ADO.Net driver. The specific behaviors that differed between reusing a pooled connection and getting a new unpooled connection were: 1) a "SET rowcount <value>" statement done on a connection that was then cached and reused could have incorrectly continued using this setting. 2) a "SET TEMPORARY OPTION secure_feature_key = <value>" statement done on a connection that was then cached and reused could have incorrectly persisted using this option. 3) the @@identity value could have incorrectly returned an identify value from before the connection was cached and reused. These problems have been fixed so that the cached and reused connections will have the same behavior as completely new connections.

CR:721874

CR Number:   721874 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 3807 26 Oct 2012 Fixed Description Applications that associate themselves to edit .js or .vbs files, like UltraEdit, could have caused the quick setup script to fail. This has been fixed.

CR:721933

CR Number:   721933 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3807 19 Oct 2012 Fixed Description Unique keys could have been created incorrectly in the following situations: 1) If a CREATE TABLE defined a column as nullable then placed that column in an unique constraint, the column would have remained nullable. For example: CREATE MyTable( pkey INT PRIMARY KEY, num INT NULL, CONSTRAINT un_num UNIQUE( num ) ) 2) A GEOMETRY column could have been placed in a unique constraint. 3) An ALTER TABLE which added a UNIQUE constraint could have included a nullable column. This has been fixed. When a table is now created, columns in unique constraints are forced to be not null and GEOMETRY columns are not allowed in unique constraints (as previously documented). When adding a unique constraint on a nullable column, an error will now occur. The correct procedure is to first alter the column to be not null, then alter the table to add a unique constraint.

CR:721950

CR Number:   721950 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 3824 09 Nov 2012 Fixed Description Under rare circumstances, execution of a query using a MergeJoin operator could have crashed the server. This has been fixed.

CR:721976

CR Number:   721976 Product Name:   SQL Anywhere Product Component:   Server Status:   Closed OS:   Generic Original Version:   4.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 16.0.0 1415 18 Jan 2013 Fixed Description In some cases, when a CHECK constraint was defined on a table, errors in the constraint were not detected when the constraint was created, even if they could have been detected at creation time. These errors were instead reported when the check constraint was evaluated. For example, the following CREATE TABLE would have succeeded but the subsequent INSERT would have failed with an error. create table T_ColumnCheck( x long varchar, check (x is distinct from COUNT( DISTINCT ( 1 ) )) ); insert into T_ColumnCheck(x) values(1) This has been fixed. Some errors can not be detected when the constraint is created (for example, data exceptions).

CR:721977

CR Number:   721977 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 3811 30 Oct 2012 Fixed 11.0.1 2893 30 Oct 2012 Fixed Description Under very rare circumstances, the server may have crashed when encountering a thread deadlock during a login packet receive. This has been fixed

CR:721986

CR Number:   721986 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   12.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3809 29 Oct 2012 Fixed Description Attempting to drop a table that was still referenced by a foreign key would not have returned an error, but would have lefte the database in an incorrect state. This has been fixed. DROP TABLE will now signal SQLE_TABLE_IN_USE in this case..

CR:722071

CR Number:   722071 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 3810 31 Oct 2012 Fixed Description When attempting to execute a statement which contained an incomplete multi-line comment, the error message mentioned that there was an error at the end of the SQL statement, but did not indicate that the problem was an unterminated comment. Now, the error message makes that explicit.

CR:722245

CR Number:   722245 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) 16.0.0 1430 29 Jan 2013 Fixed 12.0.1 3851 29 Jan 2013 Fixed 11.0.1 2935 29 Jan 2013 Fixed Description Calling PreparedStatement.setNull() and passing in a SQL type of java.sql.Types.NULL, would have incorrectly returned a bad datatype?error. This problem has now been fixed and java.sql.Types.NULL is now allowed in setNull() calls.

CR:722314

CR Number:   722314 Product Name:   SQL Anywhere Product Component:   Sybase Central Plug-in Status:   Closed OS:   Microsoft Windows Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) Description Searching a database that contained hundreds of users would have taken a very long time and would likely have caused Sybase Central to run out of memory. This has been fixed.

CR:722429

CR Number:   722429 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 3810 23 Nov 2012 Fixed Description Calling the system procedure sa_iometrics() with invalid arguments may have caused the server to crash. This has been fixed.

CR:722440

CR Number:   722440 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 3811 01 Nov 2012 Fixed 11.0.1 2893 01 Nov 2012 Fixed Description In rare timing dependent cases, two partners attempting to determine roles could have restarted their databases unnecessarily a number of times until their role was finally determined. Also, in rare timing dependent cases, a running copy node that was able to reconnect to its parent server could unnecessarily have restarted its database. In order for this to have occurred, the parent server would needed to have been unavailable for long enough for the copy node to connect to the root or alternate parent. These issues have been fixed.

CR:722466

CR Number:   722466 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 3813 29 Oct 2012 Fixed 11.0.1 2894 29 Oct 2012 Fixed Description In rare circumstances, preforming bulk inserts and deletes of large amounts of data may have caused the server to fail assertion 200130. This has been fixed.

CR:722646

CR Number:   722646 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) 16.0.0 1386 18 Dec 2012 Fixed 12.0.1 3832 18 Dec 2012 Fixed Description When an application that was connected using Open Client or jConnect executed a query that involved parameters, and the query generated a syntax error, the server could have crashed. For the crash to occur at least one of these parameters had to have been a string or binary parameter that was greater than 250 bytes in length, and an additional tinyint, smallint, int or bigint parameters followed the string or binary parameter. This problem has now been fixed.

CR:722739

CR Number:   722739 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 3811 31 Oct 2012 Fixed Description If a string of between half a page size and one page size in length was inserted into a compressed column, the string could have caused a full page to be allocated to hold the compressed data, which usually took up a very small percentage of the page. No other strings would be able to use the same page. This has been fixed. Note that it is not possible to gain back the wasted?space until the compressed string is completely rewritten, and ALTER TABLE t SET comp_col=comp_col?will not do it either. The easiest way is to ALTER TABLE t ALTER comp_col NOT COMPRESSED? followed by ALTER TABLE t ALTER comp_col COMPRESSED? This only needs to be done once. Depending on how much data is in the column, doing this may be slow and will likely increase the database file size. But once its done, all the strings will be properly, and efficiently, compressed, and any wasted?pages will now exist in the database file as free pages that can be re-used.

CR:722800

CR Number:   722800 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 3811 31 Oct 2012 Fixed Description UltraLiteJ queries that used an index with a DESC column that contained NULLs, may have returned wrong results. The query must not have had a lower bound condition for the DESC column for this problem to have occurred. Depending on any ORDER BY clauses, the query may have returned no rows, or may have returned rows containing nulls when the query had a predicate on that column. For example: CREATE TABLE "T" ( "pk" bigint NOT NULL PRIMARY KEY, "x" integer NULL ) CREATE INDEX "idx1" on "T" ( "x" DESC ) WITH MAX HASH SIZE 0 And the following data: insert into T(pk,x) values(1, -20) insert into T(pk,x) values(2, null) insert into T(pk,x) values(3, 10) And the following queries: SELECT pk FROM T WHERE x >= 5 ORDER BY x DESC -> UL will return the wrong results (no rows, when it should return the row with pk=3). SELECT pk FROM T WHERE x <= 10 ORDER BY x ASC -> UL will return no rows when it should return the rows with pk=1 and 3 SELECT pk FROM T WHERE x <= 10 ORDER BY x DESC -> UL will return all rows (including the row pk=2,x=null when it should return the rows with pk=1 and 3 This has been fixed.

CR:722938

CR Number:   722938 Product Name:   UltraLite Product Component:   UltraLite Engine Status:   Closed OS:   Generic Original Version:   12.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3813 05 Nov 2012 Fixed Description PROBLEM: With UltraLiteJ for Android, when synchronizing a large number of tables with a SyncObserver the following JNI exception was likely to occur: "E/dalvikvm(26683): JNI ERROR (app bug): local reference table overflow (max=512)". The native code to call the SyncObserver was not freeing local references to Java String objects containing the table name. SOLUTION: Fixed

CR:722972

CR Number:   722972 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 3811 31 Oct 2012 Fixed 11.0.1 2893 31 Oct 2012 Fixed 10.0.1 4352 31 Oct 2012 Fixed Description Server may have run out of memory and crashed when executing the system procedure sa_get_request_times(), especially when running with databases that had large page sizes. This has been fixed.

CR:722976

CR Number:   722976 Product Name:   SAP Sybase SQL Anywhere on-demand edition Product Component:   Infrastructure Status:   Closed OS:   Generic Original Version:   1.0.0 Fixed Version Build Resolution Date Closure Code (If Appropriate) 1.0.1 1236 01 Nov 2012 Fixed 1.0.0 3811 01 Nov 2012 Fixed Description It was possible, in rare circumstances, for a database backup to fail, leaving the backup marked as Pending?in the console. If this backup was deleted, parts of the cloud data directory on the host containing the backup, could have been deleted, including other tenant databases, server certificates, log files, etc. This could have caused any number of problems with the cloud. This has been fixed.

CR:723007

CR Number:   723007 Product Name:   UltraLite Product Component:   Runtime Libraries Status:   Closed OS:   Generic Original Version:   11.0.1 Fixed Version Build Resolution Date Closure Code (If Appropriate) 12.0.1 3811 31 Oct 2012 Fixed Description UltraLite queries that used an index with a DESC column that contains NULLs, may have returned wrong results. The query must not have had a lower bound condition for the DESC column for this problem to have occurred. Depending on any ORDER BY clauses, the query may have returned no rows, or may have returned rows containing nulls, when the query had a predicate on that column. For example: CREATE TABLE "T" ( "pk" bigint NOT NULL PRIMARY KEY, "x" integer NULL ) CREATE INDEX "idx1" on "T" ( "x" DESC ) WITH MAX HASH SIZE 0 And the following data: insert into T(pk,x) values(1, -20) insert into T(pk,x) values(2, null) insert into T(pk,x) values(3, 10) And the following queries: SELECT pk FROM T WHERE x >= 5 ORDER BY x DESC -> UL will return the wrong results (no rows, when it should return the row with pk=3). SELECT pk FROM T WHERE x <= 10 ORDER BY x ASC -> UL will return no rows when it should return the rows with pk=1 and 3 SELECT pk FROM T WHERE x <= 10 ORDER BY x DESC -> UL will return all rows (including the row pk=2,x=null when it should return the rows with pk=1 and 3 This has been fixed.