Sybase数据库技术，数据库恢复专家

CREATE SYNCHRONIZATION PROFILE "sp" ''

The query used to obtain the profile string for a specified Synchronization Profile returned null. This would have resulted in the profile being skipped during the unload. This has been fixed.

Example:

CREATE FUNCTION func1( @a integer)

RETURNS INTEGER

BEGIN

DECLARE @ret INTEGER;

SET @ret = ( a + 10 ) / 100;

RETURN @ret;

END;

SELECT a, func1( b + c ) as ret

FROM tab;

Expected error is 慍olumn 揳� not found�.

All conditions must have been met (non-transactional, shared global temp table,

and LOCK TABLE WITH EXCLUSIVE) for the crash to have occurred. If any of these three can be relaxed, the crash will be avoided.

setZlibCompression( boolean )

setZlibDownloadWindowSize( int )

setZlibUploadWindowSize( int )

zlibCompressionEnabled()

With version 11.x, the server was not able to create a cache larger than 32MB. Attempting to do so would have caused the error "Not enough memory".

With version 12.x, the server would have automatically and erroneously restricted the cache size to a size smaller than 32MB.

The default maximum cache size was erroneously restricted to a value less than 32MB.

The "percentage" notation for cache sizes (eg, "-c 50p") erroneously based the percentage on a value that was less than 32MB, rather than the total system memory as documented.

These problems have been corrected.

When using the "SET MIRROR OPTION synchronization_mode = '<value>'" statement, where <value> was asynchronous or asyncfullpage, the server was incorrectly treating this as a synchronous synchronization. This has been fixed as well.

- precision and scale for NUMERIC values

- length for string values

- differences between string types (e.g., char/varchar/long varchar or binary/varbinary/long binary)

For example, the following statement would have incorrectly returned:

a a_string

1.0000 "1.0000"

select case when dummy_col=0 then 1 else cast(2 as numeric(10,4) ) end case a

, cast( a as varchar ) a_string

from sys.dummy

However, the following statement would have incorrectly returned:

a a_string

1 "1"

select case when 0=0 then 1 else cast(2 as numeric(10,4) ) end case a

, cast( a as varchar ) a_string

from sys.dummy

The incorrect behaviour affected expressions that were partly or fully evaluated at query open time or in procedural code, and affected IF, CASE, NULLIF, ARGN, COALESCE and some other related expression types. This problem has now been fixed.

For HTTP methods other than POST, the body may be retrieved using HTTP_VARIABLE('TEXT') or HTTP_VARIABLE('BODY') as dictated by the Content-Type. An HTTP POST method is assumed to have a Content-Type of application/x-www-form-urlencoded unless otherwise specified (as with any other HTTP method, alternate Content-Types may be accessed using HTTP_VARIABLE('TEXT') or HTTP_VARIABLE('BODY')).

Example: "READ file1.sql >& output.txt"

file1.sql:

read file2.sql

go

SELECT ...

file2.sql:

SELECT ...

The following describe the steps required to correct this whenever an unload of a database is performed:

1. log in to SQL Anywhere Monitor Web UI as the user 'administrator'.

2. click Administrator on the left pane to open an Administrator dialog

3. under Resource tab, select the resource that had been dbunloaded

4. click Stop button to stop monitoring the resource

5. click Repair... and enter DBA uid/pwd to repair the resource database

6. after done, click Start to start monitoring the DB

After the above steps, the resource should function correctly.

BY clauses were being changed in a table with an article. This has been fixed. This fix covers additional cases that were not covered by Engineering case 654952.

There are a few points of note:

1) this problem would only have occurred with stored procedures that were created using an older SA 12.0.1 server

2) this fix will only affect new procedures that are created

3) the existence of the "dynamic result sets" clause for non-external environment procedures is in fact a no-op and does not affect performance or behaviour of the non-external environment procedure.

java.io.InputStream getBlobInputStream( String name )

boolean getBoolean( String name )

byte[] getBytes( String name )

java.io.Reader getClobReader( String name )

java.util.Date getDate( String name )

DecimalNumber getDecimalNumber( String name )

double getDouble( String name )

float getFloat( String name )

long getLong( String name )

int getSize( String name )

String getString( String name )

UUIDValue getUUIDValue( String name )

boolean isNull( String name )

For example:

SetupVSPackage.exe /ua

1) The dbn= value can be "*", which means any database can use this server as an arbiter.

2) The auth= value can be:

a) omitted, which means no validation of the authentication string provided by a mirror server is done.

b) a single value, which means all databases must use the same authentication string.

c) a list of values with the same number of entries as specified by dbn= (i.e. previous behavior)

For example:

Entities db = new Entities();

var query = db.SalesOrders.Select( x => x ).Where( x => EntityFunctions.DiffDays( x.OrderDate, DateTime.Now ) > 100 );

string trace = ( ( ObjectQuery ) query ).ToTraceString();

This problem has been fixed.

String getAliasName( int column_no )

String getDomainName( int column_no )

String getCorrelationName( int column_no )

String getQualifiedName( int column_no )

String getTableColumnName( int column_no )

String getTableName( int column_no )

String getWrittenName( int column_no )

Previously, they returned the value "N.Y.I.". They now return values that closely approximate those returned by the UltraLiteJ runtime for Blackberry.

Also, a new command line option 'salocation' (or 'sal') has been added to SetupVSPackage to allow specifying the SQL Anywhere install location. If 'salocation' is specified, SetupVSPackage will use it to locate the necessary dlls. If 'salocation' is not specified, SetupVSPackage will use SQL Anywhere registry keys to locate the dlls.

Note, this problem occurred only on Linux systems.

Also, if a mirror server was in the middle of taking over as the primary when it was shutdown, the database shutdown could have hung until any remaining connections were disconnected. This has been fixed.

For example:

SATcpOptionsBuilder options = new SATcpOptionsBuilder( "localonly=yes;port=6873" );

string cport = options.ClientPort;

This problem has been fixed.

Note, this problem affected the .Net provider, the ODBC, JDBC and OLEDB drivers as well.

an assertion while updating values indexed by an immediate text index. This problem required high contention on the base table. This has been fixed.

� url : Specify the server name or IP address and optionally the port number of the HTTP server being used, separated by a semi-colon. If requests are being passed through the Relay Server, you can optionally add an URL suffix to indicate which server farm the request should be passed to. url=抯erver-name[:port-number][url_suffix]�

� https : Specify whether to use HTTPS (https=YES) or HTTP (https=NO).

� certificate : To make a secure (HTTPS) request, a client must have access to the certificate used by the HTTPS server. The necessary information is specified in a string of semicolon-separated key/value pairs. You can use the file key to specify the file name of the certificate, or you can use the certificate key to specify the server certificate in a string. You cannot specify a file and certificate key together. The following keys are available:

file : The file name of the certificate.

certificate : The certificate itself.

company : The company specified in the certificate.

unit : The company unit specified in the certificate.

name : The common name specified in the certificate.

Certificates are required only for requests that are either directed to an HTTPS server, or can be redirected from a non-secure to a secure server. Only PEM formatted certificates are supported.

certificate=択ey=value[:key=value]'

� user : The HTTP server user ID. Authenticates to third-party HTTP server and gateways using RFC 267 Basic Authentication. user=抲serid�

� password : The HTTP server password. Authenticates to third-party HTTP server and gateways using RFC 267 Basic Authentication. password=抪assword�

� debug : When set to YES, all HTTP commands and response are displayed in the output log. This information can be used for troubleshooting HTTP support problems. The default is NO.

� proxy : Specifies the URI of a proxy server. For use when SQL Remote must access the network through a proxy server. Indicates that SQL Remote is to connect to the proxy server and send the request to the message server through it. proxy=抙ttp://proxy-server[:port-number]�

� client_port : Identifies the port number on which SQL Remote communicates using HTTP. It is provided for and recommended only for connections through firewalls that filter "outgoing" TCP/IP connections. You can specify a single port number, ranges of port numbers, or a combination of both. Specifying a low number of client ports could result in SQL Remote being unable to send and receive messages if the operating system has not released the ports in a timely manner after SQL Remote closes the port on a previous run. client_port=抧nnn[-mmmm]�

Unlike the FTP or SMTP message type, which relies on a third-party FTP or E-mail server, the HTTP message type makes use of the web services functionality that exists in the SQL Anywhere database engine to act as

the HTTP server, which we refer to as a "message server". In order to setup the message server, you only need to run the sr_add_message_server on the consolidated database, and ensure that the database server has

been started with the -xs http[s] switch. If starting the HTTP[S] listener on a database server hosting the consolidated database is a performance or security concern, then you can use a separate database server, as long as the database you run sr_add_message_server on has identical SQL Remote definitions to your consolidated database. For more information on how to setup a consolidated database to be a message server, how to setup a separate message server, or how to use the Relay Server to forward HTTP requests from remote database to the message server, please read the tutorials and full documentation.

The SQL Remote documentation has been updated to include information about the new message type. In the SQL Anywhere installation directory, see:

documentation/en/pdf/sqlremote1201.pdf

This has been fixed so that these files are now correctly uninstalled.

Note that prior to this fix, UltraLiteJ for Android would have done the equivalent of DatabaseManager.release() when the UltraLiteJ application terminated. Now it is possible for the application to execute DatabaseManager.release() at a specific point in time.

"The library /opt/sqlanywhere11/lib32/libulhltool11_r.so could not be loaded. This may be because the provider is being re-loaded (in which case you need to restart the viewer) or because the library could not be found in the SQL Anywhere installation. Service management will not be available."

This has been corrected.

- the application was connected to a primary server that lost quorum (the server lost the connection to both the mirror and arbiter servers)

- the application stayed connected to this server (the old primary server) even though the network connection to other servers dropped

- the application was in the middle of committing a transaction between the time that the old primary server lost its connection to the mirror and arbiter server, and when the old primary server restarted as the new mirror server because it lost quorum

- the old mirror server took over as the new primary (the mirror server must have been able to connect to the arbiter server for this to occur)

This has been fixed so that the application may now receive the new error for this situation, "The transaction may not be committed because the primary server lost quorum."

Note that 12.0.1 EBFs can be now applied directly to 12.0.0 installations - effectively performing an upgrade. Therefore if a 12.0.0 installation has not yet been upgraded to 12.0.1, use of a 12.0.1 EBF with this fix will avoid this problem. If a 12.0.0 installation had been upgraded with a build without this fix, uninstalling the product will not remove all the sample files. Those files will need to be removed manually.

It should be noted that on 64-bit Windows, only the 64-bit SYSTEM DSNs are listed (after this correction). Any 32-bit SYSTEM DSNs are not displayed. In Visual Studio 2008's design environment (which is 32-bit on 64-bit platforms), the Test Connection button will attempt to establish a connection using the 32-bit equivalent of the 64-bit DSN. If the 32-bit DSN does not exist, the test will fail.

find: stat() error /opt/sybase/sqlanywhere12/sun/jre160/lib: no such file or directory

This has been fixed. It should be noted that despite the error, the uninstaller would have completed successfully.

Workaround:

1. Shut down any graphical administration tools (Sybase Central, Interactive SQL (dbisql), the MobiLink Monitor, SQL Anywhere Monitor, or SQL Anywhere Console utility (dbconsole) that are running.

2. Run the following commands:

mkdir $SQLANY12/sun/jre160_x86/lib/fonts/fallback

ln -s /usr/share/fonts/truetype/arphic/*.ttc $SQLANY12/sun/jre160_x86/lib/fonts/fallback

ln -s /usr/share/fonts/truetype/wqy/*.ttc $SQLANY12/sun/jre160_x86/lib/fonts/fallback

For example, on Fedora, run the following command:

yum install redhat-lsb redhat-lsb.i686

- the local server was running on a Windows based system

- the local server had a restricted (or small) number of CPUs or cores (either due to the limitations of the server machine or VM, or as a result of using the -gt or -gtc command line option)

- the remote server was not defined to utilize the new "driver=SQL Anywhere Native" feature

This problem has now been fixed.

svc_t_dbmlsync: No such file or directory

This was due to the file svc_t_dbmlsync not having been installed in the bin32/dbsvc_scripts directory. This has been corrected.

Also in rare timing dependent cases, partner servers starting for the first time could have fail to have chosen a primary after the changes for Engineering case 663964.

These problems have been fixed.

1) if no transaction-logs-directory was given on its command line; and

2) if the length of the transaction log name including its absolute path was greater than 128 bytes.

This problem is now fixed and the length of the transaction log name plus its absolute path has been extended to 1024 bytes.

A write failed with error code: (6), The handle is invalid.

Fatal error: disk full when writing to "???"

This has been fixed.

- the probe input of the hash join had already consumed a lot of memory for hash tables

- a child of the hash join returned an error

- a hash based parent query node of the hash join needed to allocate memory for the hash table and is restricted by the memory governor, so that it had to acquire memory from other hash based query nodes.

This problem has been fixed.

select isdate('1234+')

While the following query failed with a runtime error indicating the date string was not acceptable:

select date('1234+')

This problem has been fixed. The "isdate" query now returns 0. At a minimum, the timezone indicator (+) must be followed by hours. For example, '2011+5' is acceptable.

Also, if a date string contained a timezone offset of "+" or "-" and was followed by the Z (Zulu) timezone indicator (e.g., '1234-12-31+Z'), no error was diagnosed. This has been corrected.

Note, this change also affect the other SQL Anywhere client libraries as well, i.e. DBLib, OLEDB, ADO.NET, etc.

AddDays, AddHours, AddMicroseconds, AddMilliseconds, AddMinutes, AddMonths, AddSeconds, AddYears, DiffHours, DiffMicroseconds, DiffMilliseconds, DiffMinutes, DiffMonths, DiffSeconds, DiffYears.

For example:

Entities db = new Entities();

var query = db.SalesOrders.Select( x => x ).Where( x => EntityFunctions.DiffDays( x.OrderDate, DateTime.Now ) > 100 );

string trace = ( ( ObjectQuery ) query ).ToTraceString();

This problem has been corrected by adding new function handlers for mapping Entity Framework datetime functions to the SQL Anywhere functions 'DATEADD' and 'DATEDIFF'.

1) The UPDATE statement modifies a table that had a primary key, UNIQUE constraint, or unique index.

2) The UPDATE statement modified a column included in the primary key, UNIQUE constraint, or unique index, such that the new value matched a value already existing in the index.

3) The modified table had an AFTER ROW or AFTER STATEMENT trigger

This problem has been corrected.

- all group by expressions in the subquery were constants

- the subquery had a COUNT aggregate

- the subquery did not affect any table rows

- the outer join condition referenced a constant grouping column of the subquery

For example: If table T1 has no row with a1 < 44 then the query does not return rows in any circumstances.

select *

from T2 left outer join

( select 111 c1, count(*) c2 from T1 where a1 < 44 ) V on T2.a2 = V.c1

This has been fixed.

Note that this fix only applies to ODBC based Remote Data Access servers. The fractional seconds precision will still be truncated to 3 digits of precision for JDBC based Remote Data Access servers.

DBLogFileInfo function

Obtains the log file and mirror log file information of a non-running database.

Prototype

short DBLogFileInfo ( const a_log_file_info * );

Parameters

A pointer to a structure. See a_log_file_info structure

.

Return value

A return code, as listed in Software component exit codes

.

Remarks

The DBLogFileInfo function returns the log file and mirror log file paths of a non-running database file. Note that this entry point will only work for databases that have been created with SQL Anywhere 10.0.0 and up.

-----------------------------------------------

Here is the necessary information for the new a_log_file_info structure:

typedef struct a_log_file_info {

unsigned short version; // set this to DB_TOOLS_VERSION_NUMBER

MSG_CALLBACK errorrtn;

const char * dbname; // database file name spec

const char * encryption_key; // database file encryption key

char * logname; // buffer for returning log file name

size_t logname_size; // size of the logname buffer

char * mirrorname; // buffer for returning mirror log file name

size_t mirrorname_size; // size of the mirrorname buffer

void * reserved; // reserved for internal use, must set to NULL

} a_log_file_info;

Remote would have generated the warning message:

Deleting duplicate message from ...

and then deleted the duplicate pinging messages.

This problem is fixed so that all the duplicate pinging messages are now processed without complaint.

external name 'MyTest.DLL::MyNameSpace.MyTestClass.MyMethod() int'

would have failed to execute MyNameSpace.MyTestClass.MyMethod, but an external name clause like:

external name 'MyTest.dll::MyNameSpace.MyTestClass.MyMethod() int'

would successfully find and execute MyMethod. This problem has been fixed.

Note that a workaround is to simply lower case the ".dll" portion of the assembly name.

Note, the newdemo.bat file is referenced by the SQL Anywhere documentation whenever it is desirable to start with a newly initialised version of the demonstration database.

CASE expression-1 WHEN expression-2 THEN expression-3, ... [ ELSE expression-4 ] { END | END CASE }.

It was not possible to use a subquery as expression-1. This has now been fixed.

Also, the message "Number of tables that will always be uploaded:" was incorrect and misleading and the number displayed was invalid. This message has been changed to "Number of tables that are in publications:" and the output has been corrected.

For example:

Select *

from T1, T2

where 10 = (select e1 from R where p(R,T1, T2) ) and ..

This has now been fixed.

MIRROR - When the NodeType connection parameter is set to MIRROR, and you have connected to a copy node or the primary server, the connection is redirected to the mirror server.

READONLY - When the NodeType connection parameter is set to READONLY, and you have connected to a copy node or the primary server, the connection is redirected to the copy node in its branch with the lowest load. If there are no copy nodes, the connection is redirected to the mirror server. If you have connected to the mirror node the connection is accepted since the mirror server does not know the status of the copy nodes. READONLY is used to connect to any read-only server, either a copy node or the mirror.

2) If a High Availability or read-only scale-out server failed to connect to another server, there may not have been any indication of the failed connect. This has been fixed by logging a message to the console for each failed connection.

3) A High Availability or read-only scale-out server may have displayed the message "... recovery n% complete" where n was a number less than zero or much greater than 100. This has been fixed.

Also, the method DatabaseManager.connect() now returns SQLE_INVALID_PARAMETER if passed a NULL configuration.

There are two possible workarounds:

1) Turn off intra-query parallelism by setting the Max_query_tasks option to 1, or

2) Set the Log_deadlocks option to 'off'

This problem has been fixed.

Module C:\Program Files\SQL Anywhere 12\BIN64\ulodbc12.dll failed to register. HRESULT -2147024703. Contact your support personnel.

This has been fixed.

[-10002] Consolidated database server or ODBC error: ODBC: [Microsoft][SQL Server Native Client 10.0][SQL Server]

Cannot drop the table '#elbat_yraropmet_ymmud_a_si_siht', because it does not exist or you do not have permission.

(ODBC State = 42S02, Native error code = 3701)

This error would have occurred in one of the following situations:

1) a deadlock was detected during upload;

2) an error occurred in a trigger that was defined on an upload table; or

3) the 'XAXT_ABORT' option was set to 'ON' in one of the user-defined scripts.

This problem is fixed now.

Note that restarting the database server eliminates the problem

Note, this change also affects the ADO .NET provider, the OLE DB provider, MobiLink server, Relay Server Outbound Enabler, database server, all SA software requiring TCPIP running on Windows.

For example, if x is of type signed integer and there are rows in T where x is NULL, and there is an index on x with max hash size 4, then the following statement would have returned a result set that included rows where X is NULL:

SELECT * FROM T WHERE x >= -2147483648

This has now been fixed.

"Recursive column %1: conversion from '%2' to '%3' loses precision ".

2) If an ALTER MIRROR SERVER statement was executed to adjust a copy node's connection string, that copy node may have temporarily failed to connect properly to other servers. This has also been fixed.

The crash can be worked around by disabling intra-query parallelism by setting the database option MAX_QUERY_TASKS=1.

As part of this change, the message that is displayed when the Java Virtual Machine can't start has been improved to include the actual JVM error.

Also, when attempting to update a blob column that was NULL using a ULTable object, the column value would have remained NULL. This has also been fixed.

For example, if "Test Connection" was used when configuring a Datasource Name (DSN), using the ODBC Datasource Administrator on a system with Microsoft Firewall Client installed then a 20-second delay occurs after the OK button is clicked.

A work-around has been developed for this problem. If the Firewall Client DLL is present when the SQL Anywhere ODBC driver is unloaded, the Windows Socket libraries are not unloaded by the driver. This avoids the 20-second delay. In this case, the Windows Socket libraries are unloaded when the client application terminates.

these options during startup recovery, or when applying changes on a mirror server. This has been fixed.

Other changes have been made as well to reuse Java objects and reduce the creation of temporary objects during the download.

These changes were made to improve memory useage during synchronization.

A workaround to this issue would be to add any synchronization user or synchronization subscriptions to the database. For example, if a publication "p1" was defined for download only, execute "CREATE SYNCHRONIZATION SUBSCRIPTION TO p1 TYPE 'tcpip'". This would define TCP/IP as the default communication type when synchronizing the publication, which is the default that would be chosen anyway.

1. The UPDATE statement is using the syntax:

UPDATE [ row-limitation ] table-expression [, ...] ]

SET set-item[, ...]

[ WHERE search-condition ]

[ ORDER BY expression [ ASC | DESC ] , ...]

[ OPTION( query-hint, ... ) ]

2. The statement must have had at least two query blocks (e.g., a derived table, subselect, subqueries).

3. The 'table expression' contained a Left Outer Join at the root of the tree

4. The Left Outer Join was a redundant join. Removing the Left Outer Join from the original statement generates an equivalent statement.

This has been fixed.

For example:

update LP join PR on PR.PR1 = LP.LP1

join LS on LS.LS2 = PR.PR2

join SC on SC.SC1 = LS.LS2

left outer join PC on PC.PC1 = LS.LS1

set LP.LP2 = LS.LS1

where

PR.PR3 = 10 and

LS.LS3 = 20 and

SC.SC2 = 30

and SC.SC2 = (select max(id) from product )

[Sybase][ODBC Driver][Adaptive Server Anywhere]Server '<server-name>': [Microsoft][ODBC Driver Manager] Driver does not support this function (-660)

A call was being made to SQLPrimaryKeys() to determine which columns in the table belong to the primary key. Access does not support this function, so this error is now ignored for the 'MSACCESSODBC' server class.

Links:

http://www.kb.cert.org/vuls/id/680620

http://www.kb.cert.org/vuls/id/238678

CREATE MIRROR SERVER "scaleout_child" AS COPY connection_string = 'server=scaleout_child;host=winxp-2:6878';

CREATE MIRROR SERVER "TheArbiter" AS ARBITER connection_string = 'server=scaleout_child;host=winxp-2:6878';

Note that there is no database server in the HA system that is running with the server name "TheArbiter": it is just being used as a placeholder in the mirror server definitions to hold the connection string for the arbiter.

2. Copy nodes could have reported a log mismatch error in certain cases involving a failure of both the primary server and the arbiter. This problem has been fixed.

3. There was a race condition that could have allowed an arbiter server to create two separate internal states for the same mirroring system. This problem has been fixed.

For the error to occur in version 11, the first cursor would need to be explicitly declared FOR READ ONLY, because FOR UPDATE is the default (c.f. documentation for DECLARE CURSOR statement). In version 12.0.0 and later, cursor updatability depends upon cursor type (c.f. documentation for SELECT and PREPARE statements) but defaults to FOR READ ONLY for ESQL.

Note: existing corrupted blob indexes must be dropped and recreated after the fix is applied. This can be done using:

alter table <table> alter <column> no index

alter table <table> alter <column> index

Note, this problem also affected SQL Anywhere clients running on the Mac.

A write failed with error code: (6), The handle is invalid.

Fatal error: disk full when writing to "???"

This has been fixed.

For example, if a table was defined as:

CREATE TABLE t(

c1 INT PRIMARY KEY,

c2 LONG VARCHAR,

c3 LONG VARCHAR )

and the row[ 1, null, 'b' ] was downloaded, reading c3 would have failed. Rows [2, 'a', 'b'], [3, 'a', null ] and [4, null, null ] would have been okay.

This has been fixed.

As a work around, the "Create sequences" section could be manually moved to before the "Create tables" section in the reload.sql file.

Also, the ULSyncProgressData.FLAG_IS_BLOCKING flag could have been set erroneously when the state was ULSyncProgressData.STATE_CANCELLED. This too has been fixed.

A simple example of a query that demonstrates this error is:

select ST_Geometry::ST_GeomFromText( 'MultiPolygon( ( ( -10 -10, -11 -10, -11 -11, -10 -11, -10 -10 ) ), ( ( 2 2, 2.5 1, 1 1, 1 2, 0 2, 0 0, 3 0, 3 2, 2 2 ) ) )' ).ST_Union( ST_Geometry::ST_GeomFromText( 'Polygon( ( 1 1, 2.5 1, 2 2, 1 2, 1 1 ) )' ) )

The only work around is to break up the MultiPolygon and perform the unions in a different order.

This has been fixed.

"The address given is invalid. The address must be a directory name with no path separators."

and then aborted the message receiving thread when it was able to retrieve all the names of the message files in the given directory from a FTP server, but for some reasons (such as network problems) was not able to retrieve the contents of a file from the server. This problem is fixed so that the error message is now:

"Unable to retrieve message file 'xxxx' from the FTP server."

Another way to avoid the problem is to create and destroy the ODBC Environment only once in an application and connect/disconnect as often as desired.

SQLAllocHandle( SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv );

SQLSetEnvAttr( henv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0 );

loop

connect/disconnect many times

endloop

SQLFreeHandle( SQL_HANDLE_ENV, henv );

Note, Microsoft has published http://support.microsoft.com/kb/2624911, which describes the problem with Windows Vista and Windows 7.

Note that a database upgrade is needed in order to get this fix.

A workaround is to ensure that the SELECT statement inside the inner procedure is not subject to simple query caching. If this slowdown is observed, the workaround can be implemented by adding a predicate that is not a tautology, but which is always known to be true for the data, to the inner select. For example, if a certain column is always greater than zero, adding the predicate col >= 0 is sufficient to avoid the problem. Note that simple predicates such as 1=1 will be detected as data-independent tautologies and removed.

Note that this problem would not be seen on Mac OS X systems.

The workaround is to manually drop the sequence before issuing the CREATE statement.

For example:

CREATE TABLE IF NOT EXISTS t ( c INT PRIMARY KEY )

This has been fixed. Now, statements are selected properly.

This same problem also affected the behavior of the "Single Step" menu item which also relies on being able to select the next statement.

Note, row limiting is required to make use of this improvement.

- the columns in a table created by the SELECT ... INTO [ LOCAL TEMPORARY TABLE ] table-name

- the columns in a view

- sa_describe_query and sa_describe_cursor domain_name_with_size and widths

- the EXPRTYPE returned data type length

These operations have been fixed to return the correct lengths.

After changing the synchronization_mode while the mirror server was connected, the mirror could have failed to take over as primary (including if the synchronization_mode was changed from 'async' or 'asyncfullpage' to 'synchronous'). This has been fixed. A side effect of this fix is the database on the mirror server automatically stops and restarts if the synchronization_mode is changed between an asynchronous mode and 'synchronous'.

If the mirror database stopped and immediately restarted, in rare timing dependent cases, it was possible that the mirror would fail to take over as the primary if the primary failed. This has been fixed.

This has been fixed so that servers that have less than about 20 committed transactions per second will no longer hang. There may also be slightly improved performance when using copy nodes.

For example:

$sth = $dbh->prepare("BEGIN SELECT * FROM Departments ORDER BY DepartmentID;SELECT TOP 10 * FROM SalesOrders ORDER BY ID;END");

$sth->execute();

do {

while (my $data = $sth->fetch) {

print "@$data\n";

}

print "---end of data---\n";

} while (defined $sth->more_results());

In a mirroring system, if an event was in use on a mirror or copynode, and DDL to alter or drop the event was applied on the primary server, the mirror or copynode using the event may have given an assertion and shut down. This has been fixed. Now, if the event is running on the mirror or copynode, the connection the event is running on will be dropped, causing the event to be cancelled, and the following message will be printed to the server console: "Dropping connections that are preventing the transaction log from being applied."

This problem could have made it appear as if the order of commands changed when a remote task was deployed, if the remote task was deployed shortly after adding a command. In fact, the ordering of the commands was incorrect immediately after the command was added. If Sybase Central was started and the task was viewed without deploying it, the added command would have been at the end of the command list.

For example:

create or replace PROCEDURE test1( )

BEGIN

ALTER TABLE ixddl6 ADD CONSTRAINT FK_primary

FOREIGN KEY (x)

REFERENCES ixddl5(pk)

match unique simple on delete set null

END

"database is not compatible with primary; files must be replaced" and

"Database server shutdown due to incompatible files for database mirroring."

This has been fixed.

Code First enables a different development workflow: defining data model objects by simply writing C# or VB.NET classes mapping to database objects without ever having to open a designer or define an XML mapping file. Optionally, additional configuration can be performed by using data annotations or the Fluent API. Model can be used to generate a database schema or map to an existing database.

Here's an example which creates new database objects using the model:

using System;

using System.Collections.Generic;

using System.ComponentModel.DataAnnotations;

using System.Data.Entity;

using System.Data.Entity.Infrastructure;

using System.Linq;

using iAnywhere.Data.SQLAnywhere;

namespace CodeFirstExample

{

[Table( "EdmCategories", Schema = "DBA" )]

public class Category

{

public string CategoryId { get; set; }

[MaxLength( 64 )]

public string Name { get; set; }

public virtual ICollection<Product> Products { get; set; }

}

[Table( "EdmProducts", Schema = "DBA" )]

public class Product

{

public int ProductId { get; set; }

[MaxLength( 64 )]

public string Name { get; set; }

public string CategoryId { get; set; }

public virtual Category Category { get; set; }

}

[Table( "EdmSuppliers", Schema = "DBA" )]

public class Supplier

{

[Key]

public string SupplierCode { get; set; }

[MaxLength( 64 )]

public string Name { get; set; }

}

public class Context : DbContext

{

public Context() : base() { }

public Context( string connStr ) : base( connStr ) { }

public DbSet<Category> Categories { get; set; }

public DbSet<Product> Products { get; set; }

public DbSet<Supplier> Suppliers { get; set; }

protected override void OnModelCreating( DbModelBuilder modelBuilder )

{

modelBuilder.Entity<Supplier>().Property( s => s.Name ).IsRequired();

}

}

class Program

{

static void Main( string[] args )

{

Database.DefaultConnectionFactory = new SAConnectionFactory();

Database.SetInitializer<Context>( new DropCreateDatabaseAlways<Context>() );

using ( var db = new Context( "DSN=SQL Anywhere 12 Demo" ) )

{

var query = db.Products.ToList();

}

}

}

}

Here's another example which maps to an existing database:

using System;

using System.Collections.Generic;

using System.ComponentModel.DataAnnotations;

using System.Data.Entity;

using System.Data.Entity.Infrastructure;

using System.Linq;

using iAnywhere.Data.SQLAnywhere;

namespace CodeFirstExample

{

[Table( "Customers", Schema = "GROUPO" )]

public class Customer

{

[Key()]

public int ID { get; set; }

public string SurName { get; set; }

public string GivenName { get; set; }

public string Street { get; set; }

public string City { get; set; }

public string State { get; set; }

public string Country { get; set; }

public string PostalCode { get; set; }

public string Phone { get; set; }

public string CompanyName { get; set; }

public virtual ICollection<Contact> Contacts { get; set; }

}

[Table( "Contacts", Schema = "GROUPO" )]

public class Contact

{

[Key()]

public int ID { get; set; }

public string SurName { get; set; }

public string GivenName { get; set; }

public string Title { get; set; }

public string Street { get; set; }

public string City { get; set; }

public string State { get; set; }

public string Country { get; set; }

public string PostalCode { get; set; }

public string Phone { get; set; }

public string Fax { get; set; }

[ForeignKey( "Customer" )]

public int CustomerId { get; set; }

public virtual Customer Customer { get; set; }

}

public class Context : DbContext

{

public Context() : base() { }

public Context( string connStr ) : base( connStr ) { }

public DbSet<Contact> Contacts { get; set; }

public DbSet<Customer> Customers { get; set; }

}

class Program

{

static void Main( string[] args )

{

Database.DefaultConnectionFactory = new SAConnectionFactory();

Database.SetInitializer<Context>( null );

using ( var db = new Context( "DSN=SQL Anywhere 12 Demo" ) )

{

foreach ( var customer in db.Customers.ToList() )

{

Console.WriteLine( "Customer - " + string.Format( "{0}, {1}, {2}, {3}, {4}, {5}, {6}, {7}, {8}, {9}",

customer.ID, customer.SurName, customer.GivenName, customer.Street, customer.City,

customer.State, customer.Country, customer.PostalCode, customer.Phone, customer.CompanyName ) );

foreach ( var contact in customer.Contacts )

{

Console.WriteLine( " Contact - " + string.Format( "{0}, {1}, {2}, {3}, {4}, {5}, {6}, {7}, {8}, {9}, {10}",

contact.ID, contact.SurName, contact.GivenName, contact.Title, contact.Street, contact.City,

contact.State, contact.Country, contact.PostalCode, contact.Phone, contact.Fax ) );

}

}

}

}

}

}

Additional assembly references need to be add to run these examples: EntityFramework, iAnywhere.Data.SQLAnywhere.v4.0, System.ComponentModel.DataAnnotations, System.Data.Entity.

In high availability or read-only scale-out, if the connection to the primary or parent server was dropped just after the mirror or copy node had determined its role, the mirror or copy node could have failed to start with the errors:

"database is not compatible with primary; files must be replaced" and

"Database server shutdown due to incompatible files for database mirroring."

This has been fixed. Note that attempting to restart the mirror or copy node after receiving this error should succeed in this case.

New and simplified configuration and logging conventions:

- Configuration file: <physical directory of the rs.dll>/rs.config

- Relay Server log file location: <physical directory of rs.dll>/Log/rs.log

The removal of the use of shared memory improves security and simplifies flow control signals, as there is one less resource to monitor. The new IIS Relay Server must be set up with a single application pool with web garden size = 1.

The workaround is to restart the rshost process. This has been fixed

Also, the method Connection.getDatabaseProperty() was exposed for UltraLiteJ Android; and the method DatabaseInfo.getRelease() was modified to return the full software release, including the build number.

Note, if a server that does not have this fix, and has many IP addresses, connects to a server with this fix, the fixed server will give a protocol error.

SQL error (-1474) -- SRID 0 is referenced by column ... of table ...

This has been fixed.

Documentation:

Connection::getNewUUID method

Returns a new UUID value.

Syntax

UUID getNewUUID()

example:

uuid = conn.getNewUUID();

SQLType.toString method

Returns the string name of the specified SQL column type constant or BAD_SQL_TYPE if not a recognized type.

Syntax

String toString(UInt16 code)

Parameters

code The SQL column type constant.

example:

uuid_str = conn.getNewUUID().toString();

1) When the consolidated database was running on a MySQL server, the MobiLink server could have immediately failed a status-check request when the server was not able to lock the remote ID;

2) When the consolidated database was running on a SQL Anywhere server, if the remote ID could not be locked in the upload transaction, the server would have shown the following warning message:

"Retrying the upload after deadlock in the consolidated database"

and then retried the upload transaction one more time.

If so, please document the prototype for Perl for db_register_a_callback function.

Note, SQL Anywhere version 12.0 does not attempt to generate a cache.dmp file.

"database is not compatible with primary; files must be replaced" and

"Database server shutdown due to incompatible files for database mirroring."

This has been fixed.

For example:

select {fn extract(month from '2011-05-07')}, {fn position('b' in 'abc')}

would have failed with syntax errors. If an uppercase keyword was used, the query would have succeeded:

select {fn extract(month FROM '2011-05-07')}, {fn position('b' IN 'abc')}

This problem has been fixed.

Note: In Interactive SQL, the braces { and } must be doubled-up (i.e. {{ and }} ).

A possible work-around for the problem is to use an insensitive or keyset-driven cursor type.

and an error handler within the stored procedure was invoked, an incorrect SQLCODE (0 or

the error code of a different error that occurred prior to the cancel) could have been reported. An incorrect error message could also have been reported by the ERRORMSG() function. This has been fixed.

- In certain cases when a copy node lost its connection to its parent and then encountered a log mismatch with the parent after it reconnected, a single CPU would remain at 100% utilization indefinitely.

- When cancelling a CREATE EVENT statement while processing a procedure profile (sa_procedure_profile, sa_procedure_profile_summary), a single CPU would have remained at 100% utilization until no connections were processing profile information

- While waiting for connections to drop when yielding to a mirroring partner, a CPU would have remained at 100% utilization until all connections were dropped.

The specified service is running. The service will be deleted when it is stopped.

Service "<svc name>" was deleted successfully.

This has been fixed. If the service is running, only the first message is displayed, otherwise only the second is displayed.

.A workaround is to specify a user when connecting to the UltraLite database to update the remote schema.

The error message displayed when a table in a table mapping can't be found in the corresponding schema has also been fixed. The message now correctly includes the table name that could not be found, instead of displaying '{0}' for the table name.

Another problem is also addressed with this change. Previously if you changed the remote table for a table mapping, some options could change to their defaults, such as the direction changing to bidirectional. Now the synchronization direction and other synchronization options are maintained.

- HTTP METHOD was not supported,

- request URL was malformed,

- the HTTP listener specifies that the DBN was required but the database name was not within the URL path.

This has been corrected. Now if a request has faulted due to any of the above reasons, the HTTP method (@M) and version (@V) will emit the string "???". The given request line is pre-pended with a ">>>" and emitted for the (@U) format place holder.

For example:

A request of the form:

BLAH /sample/test HTTP/1.0

will emit the following for LogFormat="@M @U @V"

"??? >>> BLAH /sample/test HTTP/1.0 ???"

- Service start time in UTC.

- Status capture time in UTC.

- Status refresh interval, or indication that manual refresh is expected.

1. If an end-time was specified (i.e., "BETWEEN start-time AND end-time"), then:

a. Seconds were being ignored. For example, an end-time of '23:59:59' was being interpreted as '23:59:00'.

b. The end-time was tested as an exclusive endpoint rather than an inclusive endpoint, contrary to the documentation of the BETWEEN ... AND clause. For example, the schedule "BETWEEN '9:00' AND '17:00' EVERY 60 MINUTES" would cause the event to fire last at 16:00, rather than 17:00.

2. If an end-time was not specified (i.e., "START TIME start-time"), the end-time for each day was implicitly being treated as '23:59:00' exclusive, instead of '23:59:59' inclusive.

The combined effect of these error were that no scheduled events would fire in the minute from 23:59:00 until midnight. This has been fixed.

Note, this extends the changes made by Engineering case 660851.

Note, this applies to addresses in connection strings (using the LINKS or HOST parameters), the -x and -xs switches on the server, and URLs in web service procedures.

Note, it is recommended that large binary parameters be set using PreparedStatement.appendBytesParameter().

1. An error was encountered while starting the database

2. Logs were being applied to a database at startup with -a, -ad or -ar but the -as switch was not used

3. The engine was requested to stop while the database was starting.

This has now been fixed.

User 'a_ml_user_name' has the row in 'ml_database' locked (ODBC State = 40001, Native error code = -210)

The new synchronization must also have contained an upload that included upload rows for multiple synchronization tables, and reused the database connection that was used for processing the redundant synchronization. This problem is fixed now.

Note, all connections used by a MobiLink server are shown in the MobiLink server logging file with a prefix SPID when a minimal verbosity is specified in the MobiLink command line.

FARM_CHANNEL_CONNECT_WITH_INVALID_SERVER_IDX 2006

SERVER_DISCONNECT_EARLY 3014

FARM_FAIL_ACCESS 12000

SERVER_FAIL_NEWING_CLIENT_STATISTIC 13011

This has been fixed.

1) The derived table contained a procedure call in its FROM clause and the procedure argument expression contained the outer reference.

2) The derived table contained a OPENSTRING clause in its FROM clause and its value expression contained the outer reference.

3) The derived table contained another derived table and the outer reference was inside this other derived table.

The below query shows an example of condition 3).

select ( select V0.e from (

select T3.e from T3 where T3.e = T2.c ) V0

) c1,

max(T1.b) as c2

from T1 join T2 on T1.a = T2.c

This problem has been fixed. The engine will now correctly return the error SQLE_INVALID_GROUP_SELECT, since the outer reference column has to be specified in the GROUP BY clause. Specifying the outer reference column in the GROUP BY clause (in the above example: group by T2.c) is also the work around to this problem.

Setup is automated but also interactive. It creates a demo application and a Quick Reference Guide to assist in subsequent Relay Server server maintenance. The Quick Reference is launched automatically as part of the setup.

Setup is comprised of the following major steps:

1. Introduction

2. Customization

3. Create a Backup

4. Deploy and Start the Relay Service

5. Generate and Launch the Quick Reference

6. Launch the Relay Server Status Page

7. Launch the SimpleTestApp Client

8. Shut down

To deploy the Relay Server components to Microsoft IIS 6.0 on Windows Server 2003, run rs-setup.bat from the SQLANY12%/RelayServer/IIS/quicksetup_iis6 directory

Interactive SQL could not be launched.

Please change the plug-in properties and

add the isql.jar file to its path.

was due to Sybase Central expecting ISQL.jar to be installed. This has been corrected by adding a dependency on ISQL.jar when an install of Sybace Central is created.

- the application was connected to a primary server that lost quorum (the server lost the connection to both the mirror and arbiter servers)

- the application stayed connected to this server (the old primary server) even though the network connection to other servers dropped

- the application was in the middle of committing a transaction between the time that the old primary server lost its connection to the mirror and arbiter server, and when the old primary server restarted as the new mirror server because it lost quorum

- the old mirror server took over as the new primary (the mirror server must have been able to connect to the arbiter server for this to occur)

This problem has now been fixed.

forward_x509_identity = yes

In the case were there is a chain of SAP intermediaries, the client identity headers may already present in the request. However not all clients may be granted a permission to act as such forwarder. So the default behavior is to replace the existing headers with the identity of the forwarder. To grant permission for a forwarder to forward its client identity without being overwritten by its identity, the following new pair of backend farm properties may be in the Relay Server configuration file:

forwarder_certificate_subject = <match-string>

forwarder_certificate_issuer = <match-string>

The <match-string> is used to check against a serialized form of the corresponding compound name field in the certificate. A '?' can be used to match any character and a '*' can be used to match any string. A '\' can be used as the leading escape character for '?', '*' or '\' of they need to be matched literally.

For example:

forwarder_certificate_subject = 'CN = mySapWD??.my.com, OU = Sybase, O = SAP, *'

forwarder_certificate_issuer = 'CN = quicksigner, OU = security department, O = my coop, L = my city, S = my state, C = my country'

To obtain the subject or issuer string of a forwarder, simply perform a forwarding without setting up the match requirement. The following error messages in the Relay Server log will reveal the full subject or issuer which fails the default empty match-string:

Forwarder certificate subject '<full-subject-string>' does not match pattern '' required in farm '<farm>'

Forwarder certificate issuer '<full-issuer-string>' does not match pattern '' required in farm '<farm>'

This problem can be worked-around by creating a symlink for gcc-4.2 -> gcc in the /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin and similar Simulator directories, or by modifying the makefile or build.sh used by UltraLite.

Setup is automated but also interactive. It installs IIS7, turns on required IIS7 features, configures IIS7 for Relay Server, creates a demo application and a Quick Reference Guide to assist in subsequent Relay Server server maintenance. The Quick Reference is launched automatically as part of the setup.

Setup is comprised of the following major steps:

1. Introduction

2. Customization

3. Install IIS7 and Required Features

4. Create a Backup

5. Deploy and Start the Relay Service

6. Generate and Launch the Quick Reference

7. Launch the Relay Server Status Page

8. Launch the SimpleTestApp Client

9. Shut down

To deploy the Relay Server components to Microsoft IIS 7.0 or 7.5 on Windows Server 2008/Windows Server 2008 R2, run rs-setup.bat from the SQLANY12%/RelayServer/IIS/quicksetup_iis7 directory.

For example:

create variable mykey varchar(50);

set mykey='TheActualEncryptionKey';

select * from openstring(...) with (...) option (encrypted key mykey);

[dbisql]

lockedPreferences=fastLauncherEnabled

fastLauncherEnabled=false

As well, mlgenreplayapi will now create the directory specified by the -d option (the directory in which to put the generated code) when it does not exist.

In a related issue, the above error message should have been displayed, but was not, in a number of other cases. This has also been fixed.

W. 2011-10-28 21:23:36. <5608.2420.F5fcB0S456bR0> Server response NOT completed. Remaining 0 of 0 bytes.

Restarting the Outbound Enabler would have resolved the issue. This has now been fixed so that client requests will not be affected by the delay and restarting Outbound Enabler is no longer required.

Gtk-CRITICAL **:gtk_text_buffer_emit_insert:assertion 'g_utf8_validate (text, len, NULL)' faild

This problem has been fixed. As a consequence, the message output in the MobiLink server log when a synchronization request is received from a SA remote will change from:

Request from "Dbmlsync Version 16.0.0.3940" for: remote ID: ...

to:

Request from "Dbmlsync 16.0.0.3940" for: remote ID: ...

Also, if a transaction only modified temporary tables, it was possible that the transaction log would have been committed to disk although it didn't need to be.

These problems have been fixed.

LastCommitRedoPos: This property is available at both the connection-level and the database-level. The value returned is the redo log position after the last COMMIT operation was written to the transaction log by the connection or database.

LastWrittenRedoPos: This is a database-level property only. The value returned is the last redo position for which a write was issued to disk. The write is not necessarily synced to the physical medium as it may still be cached by the OS, disk controller or disk drive.

LastSyncedRedoPos: This is a database-level property only. The value returned is the last redo position for which a write was issued to disk and the data was synched to the physical medium. Data prior to this position is expected to be present on disk even in the event of a power failure.

Note, not all secured features add entries to the transaction log. For example, the READ_FILE secured feature blocks access to xp_read_file which would not get logged; however, the REMOTE_DATA_ACCESS secured feature blocks access to statements such as CREATE SERVER does get logged.

/**

* Enables or disables restartable HTTP. With restartable HTTP enabled,

* UltraLiteJ can tolerate network interruptions, so synchronizations will fail

* less often on unreliable networks.

* <p>

* To use restartable HTTP, both UltraLiteJ and the MobiLink server must have

* applied CR#690250.

*

* @param isRestartable Pass true to enable restartable HTTP, and false to

* disable. The default is false.

* @see #isRestartable()

*/

public void setRestartable( boolean isRestartable );

/**

* Returns true if restartable HTTP will be used, and false otherwise.

*

* @return Whether restartable HTTP will be used.

* @see #setRestartable(boolean)

*/

public boolean isRestartable();

To use this change, both remotes and servers must be upgraded. It is safe to upgrade only one of the remote or the server, as long as setRestartable is not called on the remote.

- Connection A opened a cursor that included fetching rows from a procedure

- Connection B dropped the procedure used by connection A

- Connection A then closed its cursor

This problem has been fixed.

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".

Note, as expected no data is logged to the transaction log in this case.

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.

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.

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.

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.

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:

揟o open 揓ava 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.

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.

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.

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.

Also, the Certificate Viewer utility (viewcert) will now also correctly display the signature algorithm for certificates signed using SHA-2.

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.

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.)

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

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.

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.

encrypted system tables. This has been fixed.

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

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.

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.

- 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

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.

[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.

Note, an ALTER DATABASE UPGRADE will need to be performed on existing databases in order to get the new jConnect metadata procedures.

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.

[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.

be specified".

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.

Note, the default liveness timeout for synchronization and file transfer connections is 100 seconds for BlackBerry, J2SE and J2ME platforms, and 240 seconds (the default for UltraLite/MobiLink) for Android platforms.

The class documentation for the Java class follows:

/**

* Contains information about the network streams for a synchronization.

* This is useful if you wish to authenticate against some other server in

* the enterprise using the client-side certificate and HTTP headers.

*

* To enable collection of network stream data, add collect_network_data=1 to

* your -x switches. This adds additional per sync memory overhead to store

* the data. If using TLS or HTTPS with client-side certificates, add

* trusted_certificates=<certificate file> to have the server ask the client to send

* a certificate during the TLS handshake, incurring a time and network cost.

*

* You can obtain a NetworkData object by invoking the getNetworkData method

* of the DBConnectionContext class. When using HTTP or HTTPS, it will contain

* the header data for the last HTTP request received by the server before the

* authenticate scripts are invoked.

*

* @see DBConnectionContext

*

* @examples

* The following example shows how to get a NetworkData object from the

* DBConnectionContext, and prints the data it contains to the log.

*

* <pre>

* public class OrderProcessor {

* DBConnectionContext _cc;

*

* public OrderProcessor( DBConnectionContext cc ) {

* _cc = cc;

* }

*

* // The method used for the authenticate_user event.

* public void AuthUser() {

* NetworkData nd = _cc.getNetworkData();

* if( nd != null ) {

* if( nd.isHTTP() ) {

* System.out.println( "http" );

* String user_agent = nd.getHTTPHeaderValue( "user-agent" );

* System.out.println( " user-agent: " + user_agent.substring( 0, user_agent.indexOf( '/' ) ) );

* } else {

* System.out.println( "no http" );

* }

* if( nd.isTLS() ) {

* System.out.println( "tls" );

* CertPath certs = nd.getCertificateChain();

* if( certs != null ) {

* System.out.println( " client-side cert:" );

* int n = 1;

* for( Certificate c : certs.getCertificates() ) {

* System.out.println( " cert " + n++ );

* X509Certificate c509 = (X509Certificate) c;

* System.out.println( " Subject: " + c509.getSubjectX500Principal().getName() );

* System.out.println( " Issuer: " + c509.getIssuerX500Principal().getName() );

* }

* } else {

* System.out.println( " no client cert" );

* }

* } else {

* System.out.println( "no tls" );

* }

* if( nd.isEndToEndEncrypted() ) {

* System.out.println( "e2ee" );

* } else {

* System.out.println( "no e2ee" );

* }

* } else {

* System.out.println( "NULL networkdata" );

* }

* }

* }

*

* </pre>

*/

public interface NetworkData

{

/**

* Returns true if this sync is using HTTP or HTTPS, and false otherwise.

*

* @return True if this sync is using HTTP or HTTPS, and false otherwise.

*/

public boolean isHTTP();

/**

* Returns the value of the last header received by the server with the supplied

* name.

*

* @param the header name to the return the value for

*

* @return the last header value associated with the supplied header-name

*

* @see NetworkData#getHTTPHeaderValues

* @see NetworkData#getHTTPHeaders

*/

public String getHTTPHeaderValue( String name );

/**

* Returns all the header values received by the server associated

* with the supplied name.

*

* @param the header name to the return the values for

*

* @return the header values associated with the supplied header-name

*

* @see NetworkData#getHTTPHeaderValue

* @see NetworkData#getHTTPHeaders

*/

public List<String> getHTTPHeaderValues( String name );

/**

* Returns a Map that maps header names to a List of header-values.

*

* @return a Map containing all the headers received by the server.

*

* @see NetworkData#getHTTPHeaderValue

* @see NetworkData#getHTTPHeaderValues

*/

public Map<String, List<String> > getHTTPHeaders();

/**

* Returns true if this sync is using TLS, and false otherwise.

*

* @return True if this sync is using TLS, and false otherwise.

*/

public boolean isTLS();

/**

* Returns a java.security.cert.CertPath containing any certificates

* sent by the client. The certificates are all

* java.security.cert.X509Certificate objects.

*

* This function will return a non-null value only if isTLS() is true,

* the client supplies a certificate using the "identity" stream

* parameter, and the trusted_certificates option is set on the server.

* A non-null CertPath will contain the certificates in order,

* from the self-signed certificate to the peer certificate.

*

* @return A CertPath containing the X509 certificates that identify the

* client, or null if no such certificates were provided.

*/

public java.security.cert.CertPath getCertificateChain();

/**

* Returns true if this sync is end-to-end encrypted, and false otherwise.

*

* @return True if this sync is end-to-end encrypted, and false otherwise.

*/

public boolean isEndToEndEncrypted();

}

This method was added to the Java DBConnectionContext class:

/**

* Returns information about the network streams for a synchronization.

* This is useful if you wish to authenticate against some other server in

* the enterprise using the client-side certificate and HTTP headers.

*

* To enable collection of network stream data, add collect_network_data=1 to

* your -x switches. This adds additional per sync memory overhead to store

* the data.

*

* @return information about the network streams used for the request, or

* null if collection has not been enabled.

* @see NetworkData

*/

NetworkData getNetworkData();

The .NET class documentation follows:

namespace iAnywhere.MobiLink.Script

{

/// <summary>

/// Contains information about the network streams for a synchronization.

/// </summary>

/// <remarks>

/// This is useful if you wish to authenticate against some other server in

/// the enterprise using the client-side certificate and HTTP headers.

///

/// To enable collection of network stream data, add collect_network_data=1 to

/// your -x switches. This adds additional per sync memory overhead to store

/// the data. If using TLS or HTTPS with client-side certificates, add

/// trusted_certificates=<certificate file> to have the server ask the client to send

/// a certificate during the TLS handshake, incurring a time and network cost.

/// You can obtain a NetworkData object by invoking the getNetworkData method

/// of the DBConnectionContext class. When using HTTP or HTTPS, it will contain

/// the header data for the last HTTP request received by the server before the

/// authenticate scripts are invoked.

///

/// </remarks>

/// <example>

/// The following example shows how to get a NetworkData object from the

/// DBConnectionContext, and prints the data it contains to the log.

/// <code>

/// using iAnywhere.MobiLink.Script;

/// using System.Collections.Generic;

/// using System.Security.Cryptography.X509Certificates;

///

/// public class OrderProcessor {

/// DBConnectionContext _cc;

///

/// public OrderProcessor( DBConnectionContext cc ) {

/// _cc = cc;

/// }

///

/// public void AuthUser() {

/// NetworkData nd = _cc.NetworkData;

/// if( nd != null ) {

/// if( nd.IsHTTP ) {

/// PrintLn( "http" );

/// string user_agent = nd.GetHTTPHeaderValue( "user-agent" );

/// PrintLn( " user-agent: " + user_agent.Substring( 0, user_agent.IndexOf( '/' ) ) );

/// } else {

/// PrintLn( "no http" );

/// }

/// if( nd.IsTLS ) {

/// PrintLn( "tls" );

/// X509Certificate2Collection certs = nd.ClientCertificates;

/// if( certs != null ) {

/// PrintLn( " client-side cert:" );

/// int n = 1;

/// foreach( X509Certificate2 x509 in certs ) {

/// PrintLn( " cert " + n++ );

/// PrintLn( " Subject: " + x509.SubjectName.Name );

/// PrintLn( " Issuer: " + x509.IssuerName.Name );

/// }

/// } else {

/// PrintLn( " no client cert" );

/// }

/// } else {

/// PrintLn( "no tls" );

/// }

/// if( nd.IsEndToEndEncrypted ) {

/// PrintLn( "e2ee" );

/// } else {

/// PrintLn( "no e2ee" );

/// }

/// } else {

/// PrintLn( "NULL networkdata" );

/// }

/// }

/// }

/// </code>

/// </example>

public interface NetworkData

{

/// <summary>

/// Returns true if this sync is using HTTP or HTTPS, and false otherwise.

/// </summary>

/// <returns>

/// True if this sync is using HTTP or HTTPS, and false otherwise.

/// </returns>

bool IsHTTP {

get;

}

/// <summary>

/// Returns true if this sync is using TLS or HTTPS, and false otherwise.

/// </summary>

/// <returns>

/// True if this sync is using TLS or HTTPS, and false otherwise.

/// </returns>

bool IsTLS {

get;

}

/// <summary>

/// Returns the existing connection to the MobiLink consolidated database.

/// </summary>

bool IsEndToEndEncrypted {

get;

}

/// <summary>

/// Returns the value of the last header received by the server with the supplied

/// name.

/// </summary>

/// <param name="name"> the header name to the return the value for </param>

/// <return>

/// The last header value associated with the supplied header-name.

/// </return>

///

/// <seealso cref="GetHTTPHeaderValues"/>

/// <seealso cref="HTTPHeaders"/>

///

string GetHTTPHeaderValue( string name );

/// <summary>

/// Returns all the header values received by the server associated with

/// the supplied name.

/// </summary>

/// <param name="name"> the header name to the return the values for </param>

/// <return>

/// The header values associated with the supplied header-name.

/// </return>

///

/// <seealso cref="GetHTTPHeaderValue"/>

/// <seealso cref="HTTPHeaders"/>

///

IList<string> GetHTTPHeaderValues( string name );

/// <summary>

/// Returns a dictionary that maps header names to a list of header-values.

/// </summary>

/// <return>

/// A dictionary of header name-value pairs.

/// </return>

///

/// <seealso cref="GetHTTPHeaderValue"/>

/// <seealso cref="GetHTTPHeaderValues"/>

///

IDictionary<string, IList<string> > HTTPHeaders {

get;

}

/// <summary>

/// Returns an X509Certificate2Collection containing any certificates

/// sent by the client.

/// </summary>

/// <remarks>

/// This function will return a non-null value only if isTLS() is true,

/// the client supplies a certificate using the "identity" stream

/// parameter, and the trusted_certificates option is set on the server.

/// A non-null CertPath will contain the certificates in order,

/// from the self-signed certificate to the peer certificate.

/// </remarks>

/// <return>

/// An X509Certificate2Collection containing the X509 certificates that identify

/// the client, or null if no such certificates were provided.

/// </return>

X509Certificate2Collection ClientCertificates {

get;

}

}

}

The following property was added to the .NET DBConnectionContext:

/// <summary>

/// Returns information about the network streams for a synchronization.

/// </summary>

/// <remarks>

/// This is useful if you wish to authenticate against some other server in

/// the enterprise using the client-side certificate and HTTP headers.

///

/// To enable collection of network stream data, add collect_network_data=1 to

/// your -x switches. This adds additional per sync memory overhead to store

/// the data.

/// </remarks>

///

/// <returns> information about the network streams used for the request, or

/// null if collection has not been enabled.

/// </returns>

///

/// <seealso cref="NetworkData"/>

NetworkData NetworkData {

get;

}

1) The transaction log was renamed (and a new one started) at the end of a backup of the primary

2) The mirror or copy node caught up and applies some operations from new transaction log

3) The mirror or copy node lost connection with its partner or parent

4) The mirror or copy node reestablished connection with its partner or parent

Note that if the mirror or copy node restarted prior to reconnecting, corruption would not have occurred. If corruption did occur, an 'invalid transaction log' assertion failure on the mirror or copy node was the most likely outcome. This problem has been fixed.

Also, if a copy node (call it CN) has a parent that was not the primary (call it NP), it was possible for CN to stop applying transactions altogether. CN would have remained running as a read-only node but it would not have applied transactions until the database was manually restarted. For CN to enter this state, the following sequence of events must have occurred:

1) CN and NP become disconnected or CN just wasn't running yet

2) NP renamed the transaction log and started a new one (which happens as a result of copying actions performed at the primary)

3) CN and NP reconnect (or CN was started)

In this case, CN will now display a "Recovery complete" message in the console log.

Note that the SQL client API is no longer supported by default. If the SQL client API is needed, the QAnywhere message store must be initialized using qaagent -si with the new option -sqlapi.

dbeng12 -n jcs -c nonsense

However, if the argument to -c started with the a character associated with memory units (k, m, g), no usage text was displayed. For example:

dbeng12 -n jcs -c garbage

dbeng12 -n jcs -c magic

dbeng12 -n jcs -c k

This has been corrected so that the usage text is now displayed.

Note: The farm name and server id in the URL remain case sensitive.

- agg_arg was a complex expression

- a complex sub-expression of the agg_arg was used in the WHERE (or in an ON condition)

- the optimizer selected an execution strategy involving "distinct-by-rowids" (for example, there was an EXISTS subquery)

This problem has been fixed.

For example, the following query could have caused the SELECT statement to fail with the assertion failure error:

create table T_DBR_1( x int );

create table T_DBR_2( x int );

insert into T_DBR_1 select row_num from sa_rowgenerator(1,10);

insert into T_DBR_2 select row_num from sa_rowgenerator(1,100);

commit;

select count(*), sum( complex_expr1+2 )

from (

select case R1.x*10 when 11 then R1.x end case complex_expr1

, 99+R2.x as complex_expr2

from T_DBR_1 R1 left join T_DBR_2 R2 on R1.x = R2.x

where exists ( select * from dbo.rowgenerator R3 where R3.row_num+1 = R1.x )

) D

where complex_expr1 <> 12

or complex_expr2+2 <> 11

A workaround has been implemented to avoid the problem with double values, but the above note still applies.

- TCP load balancer without stickiness was used in front of a Relay Server farm of size greater than 1; and

- an application session had more than one HTTP request; and

- the session had crossed over to a Relay Sever different from the one where the session started and an I/O error or timeout occurred with the client connection.

The problem was that the Outbound Enabler was misinforming the Relay Server for a change in upward packet destination, when a session was migrated from one Relay Server to another, on a clear request-response boundary. This has now been fixed so that the Outbound Enable is stopped from misinforming the Relay Server.

The usage is:

mlsrvXX ... -x tls(...;trusted_certificates=certificate_file) ...

mlsrvXX ... -x https(...;trusted_certificates=certificate_file) ...

Used in the simplest way, the trusted_certificates option provides validation of clients, but without other capabilities like certificate revocation lists. To implement a certificate revocation list and otherwise integrate with your enterprise certificate infrastructure, you'll need to make use of the NetworkData.ClientCertificates API, described in the email forwarded below.

The simplest example to illustrate this is:

client --> ML server --> Enterprise certificate infrastructure

Use the trusted_certificates option to ensure the client certificate is valid, then use the NetworkData.ClientCertificates API to further authenticate the certificate in the authenticate_user script (written in Java or .NET).

- TCP load balancer without stickiness was used in front of a Relay Server farm of size greater than 1; and

- an application session had more than one HTTP request; and

- the session had crossed over to a Relay Sever different from the one where the session started and an I/O error or timeout occurred with the client connection.

The problem was that the Outbound Enabler was misinforming the Relay Server for a change in upward packet destination, when a session was migrated from one Relay Server to another, on a clear request-response boundary. This has now been fixed so that the Relay Server is protected from being misinformed by Outbound Enablers older than 12.0.1.3574.

For more information on Windows processor groups, see the following:

http://blogs.msdn.com/b/saponsqlserver/archive/2010/09/28/windows-2008-r2-groups-processors-sockets-cores-threads-numa-nodes-what-is-all-this.aspx

http://msdn.microsoft.com/en-us/library/windows/desktop/dd405503

In addition to supporting more than 64 processors on Windows, SQL Anywhere now uses the hardware topology as reported by Windows for license enforcement on all supported versions of Windows except Windows 2003 and Windows XP 64-bit edition where the operating system is known to misrepresent the actual topology. Previously, SQL Anywhere relied solely on its own hardware detection on x86 and x64 Windows platforms. By relying on the topology reported by Windows, SQL Anywhere will have a more consistent view of the topology when running in a VM.

These processor topology changes include fixes on other platforms too. On Solaris prior to this change, if the standalone engine was run within a processor set it would bind itself to a single random processor in the set. Now if the standalone engine is run within a processor set, it binds to the lowest numbered processor in the set. Outside of a processor set, the behaviour has not changed: we bind to the lowest processor that is not bound to any set.

Also on Solaris, the database server considered processors that were online but non-interruptible as offline. SQL Anywhere would not bind to such a processor. This problem has also been fixed.

SQL Anywhere now properly avoids processors that are offline when the server starts; however, no attempt is made to adapt to processors that are taken offline or brought online during runtime.

SAConnection conn = new SAConnection( connectString );

conn.Open();

.

.

.

conn.Close();

Note that this was not a problem with the mechanism that pushes log pages to copy nodes and mirror, but with the way the offset was reported.

varying timezone offsets. This has been fixed.

Note that the server must be started with a secure feature key (-sk) to make use of this feature.

- searching for the zero or null value (or empty string/binary, etc) would have resulted in an incorrect result set

-) rows with zero or null values may have been intermixed order-wise when scanning the index (i.e. select * from mytable order by col_in_bad_index)

This has been fixed.

Note, primary keys, unique keys (constraints) and not null indexes are not affected by this problem.

Small XML documents with a length less than or equal to 32 KB can be uploaded into and downloaded from an Oracle database with Oracle PL/SQL statements. However, when the length of XML documents is great than 32 KB, the upload XML documents may need to be uploaded into a (global) temporary table by the upload_insert and upload_update scripts and the upload data can then be converted and stored into the actual sync table in the end_upload_rows or end_upload script.

The following section gives sample upload and download scripts to upload and download XMLTYPE objects between an Oracle consolidated and SQLAnywhere remote databases. Here we assume our upload table is defined as

create table test (pk int not null primary key, c1 XMLTYPE)

in the Oracle consolidated database and

create table test (pk int not null primary key, c1 XML)

in the SA remote database. Then the upload and download scripts for the test table could be defined below:

1) All XML documents are less than or equal to 32KB long:

The upload and download scripts can be written as

a) upload_insert:

declare v_pk integer; v_c1 clob; x_c1 xmltype;

begin

v_pk := {ml r.pk};

v_c1 := {ml r.c1};

x_c1 := XMLTYPE.createXML( v_c1 );

insert into test values( v_pk, x_c1 );

end;

b) download_cursor:

select pk, XMLSERIALIZE( content c1 ) from test

This upload_insert script works well, when the XML data length is less than or equal to 32 KB. However, if the XML data length is greater than 32 KB, the Oracle server could complain with the following error:

ORA-01460: unimplemented or unreasonable conversion requested

when the MobiLink server was trying to execute the upload_insert script with the upload data.

2) Some of the XML documents are greater than 32KB long:

If there are any XML documents greater than 32 KB long, we are not able to use Oracle PL/SQL to upload data into the Oracle XMLTYPE columns. To work-around this problem, the upload XML data needs to be uploaded in a global temporary table:

a) upload_insert:

The upload_insert script will upload the XML documents into a global temporary table in the Oracle consolidated database and the global temporary table is defined as

create global temporary table tmp_test (pk int, c1 CLOB)

then the upload_insert script can written as

insert into tmp_test values( {ml r.pk}, {ml r.c1} )

Please note, the c1 column in the temporary table must have the CLOB data type.

b) end_uoload_rows:

The end_upload_rows script first retrieves the XML documents from the global temporary table, converts it to XML documents, and then stores the XML data into the test table. Here is the end_upload_rows script:

insert into test (pk, c1) (select pk, XMLTYPE.createXML(c1) from tmp_test

***** SQL error: Syntax error near 'xxx' on line 1

Also, during reload, extra apostrophes would be displayed in progress messages containing table, index, view, procedure or trigger names. This problem has been fixed.

Also, a structure used to query the OS version on Windows Mobile / Windows CE devices was not initialized correctly; however, it is not believed ever to have caused a problem. This problem has also been fixed.

Auto-parenting uses sa_mirror_server_status() to determine what servers are connected. In a read-only scale-out setup, it was possible for sa_mirror_server_status() to report a copy node as connected when it was actually shut down. This would have happened when the copy node and its parent were shut down in quick succession. This has been fixed. Now, the copy node will appear as connected for up to two minutes, at which point the server will be marked as disconnected.

For example:

public class BlogContext : DbContext

{

public DbSet<Blog> Blogs { get; set; }

}

[Table( "Blogs" )] // [Table( "Blogs", Schema = "GROUPO" )]

public class Blog

{

public int BlogId { get; set; }

public string Name { get; set; }

public string Url { get; set; }

public int Rating { get; set; }

}

This has now been fixed.

"The backend farm rejected this client security"

NCHAR

NVARCHAR

LONG NVARCHAR

VARBIT

LONG VARBIT

XML

This has been fixed.

<UpChannel-0000> 499 RS_CLI_SESSION_BEGIN(snum=0000 sfp=995770b6 ridx=0)

<UpChannel-0000> 557 RS_CLI_REQUEST_BEGIN(oidx=0 snum=0000 sfp=995770b6 ridx=0 sidx=0)

This has been fixed to complete the logging like the following:

<UpChannel-0000> 499 RS_CLI_SESSION_BEGIN(snum=0000 sfp=7329322a ridx=0 appt=2 per=1)

<UpChannel-0000> 557 RS_CLI_REQUEST_BEGIN(oidx=0 snum=0000 sfp=7329322a ridx=0 sidx=0 appt=2 per=0)

public void validateDatabase(

int flags,

ValidateDatabaseProgressListener listener,

String tableName )

The interfaces ValidateDatabaseProgressData, and ValidateDatabaseProgressListener have also been added.

A workaround is to use the interactive prompt instead.

ULPreparedStatement::AppendParameterStringChunk

ULResultSet::GetStringChunk

ULResultSet::AppendStringChunk

Note that it is highly recommended that application developers and DBAs always review their web application code for possible security vulnerabilities before they are put into production. The Open Web Application Security Project (https://www.owasp.org) contains more information on how to secure your web application.

In addition to hashing support, performance improvements were made to indexing to reduce the number of pages written when committing inserts, updates and deletes.

1. The numbers rendered through the browser were aggregated and averaged across all requests going to the same backend server. So individual request tracing was not viewable.

2. The Monitor was not included in any rebundling of the Relay Server.

The verbose logging (-v 4) of the Relay Server Outbound Enabler (RSOE) of the DoneReceive event has now been enhanced to include a Since Last Sent (sls) number. The sls measures number of millisecond elapsed since the completion time of the last send that occurred on the same socket that had just completed a receive operation. This can be used as a measure of the backend server processing time, which includes the communication cost of sending the last packet (as the OS can declare completion before the packet is actually flushed) between the RSOE and the backend server (which normally should be minimal when they are local to each other). Here is a sample log line:

<Backend-0000> DoneReceive: sidx=0 ridx=0 socket=01227b58 sfp=f6c1ee75 len=65514 usage=8192 (12%) sls=0

If the backend server also reports a value for the overall request-response processing time, the associated sls value can be used to verify the qualify of the measurement without need to insert third party sniffing tools, which may, in some cases, change the network topology and invalidate the study.

Note that fetching nchar values defined with the nchar, nvarchar or long nvarchar base datatypes is not affected by this problem.

Note, this failure could also have occurred for MobiLink clients loading a client identity. This has been fixed as well.

The solution to this problem is to update the Java Runtime Environment to version 1.6.0_31 or later. Instructions for doing this are contained in a white paper called "Updating the SQL Anywhere Java Runtime Environment", available from the Sybase web site here:

http://www.sybase.com/detail?id=1058536

There are no code changes for this issue.

Similarly, if a database was created with any version of 10.0.0, and then upgraded to any version of 10.0.1 or later, the Unload utility could erroneously have generate SQL to re-create the SQL Anywhere internal function "sa_ansi_standard_packages".

During a reload, these problems would have generated a message such as the following:

***** SQL error: Item 'jdbc_functioncolumns' already exists

These problems have been fixed.

Note, this change also relates to the Interactive SQL utility as well. Sybase Central and the Interactive SQL utility were not reviewed for compatibility.

view\status bar

view\Toolbars\Standard Toolbars

view\Toolbars\Context Bar

view\Toolbars\Context Title

When these items were checked a blue box appeared beside the item instead of a check mark. This has been fixed.

Note, this problem would also have occurred with the SQL Anywhere plugin for Sybase Central, which is fixed as well.

Also, a bound has been placed on the total amount of header data that can be sent in an HTTP request. If a request exceeds the bound, the server will return an HTTP error code and abort the request. This bound is controllable with the header_limit HTTP option. For example, "-x http(header_limit=200000)" will raise the limit to 200000 bytes. The default value is 64000 bytes.

A workaround is to set the option MAX_QUERY_TASKS to 1 for transactions that are known to participate in deadlocks.

Note: this change is fixed the English resource only.

A workaround is either to use regular TIMESTAMP types, or use a 32-bit server.

If a copy node lost its host name because of a network problem at any point, the copy node's parent would have been unable to connect to the copy node. This would have appeared in the logs like the copy node connected to the parent without any problems, but the parent would have been unable to connect back. The parent would then drop the connections and the copy node would have made the connection again, causing an infinite cycle that caused the copy node to be unable to stay connected or receive log pages. This has been fixed.

If a copy node tried to connect to its parent, but was unable to resolve the parent's host name during connection due to network problems, the copy node would have connected to the primary and never tried to connect to its parent again. This has been fixed.

A workaround is to use PreparedStatement.getBlobOutputStream(int) to get an OutputStream object, and use that to write the parameter value.

The following APIs have been added:

Connection.rollbackPartialDownload()

SyncParms.setAdditionalParms( String v )

SyncParms.getAdditionalParms()

SyncParms.setKeepPartialDownload( boolean c )

SyncParms.getKeepPartialDownload()

SyncParms.setResumePartialDownload( boolean c )

SyncParms.getResumePartialDownload()

SyncResult.getPartialDownloadRetained()

Note that this change also greatly improves the performance of loading classes from the database.

Note, this option was added by Engineering case 696647.

Per client shared memory consumption

Per client virtual memory consumption

Global shared memory level

This change also introduces a new user control in the Relay Server configuration:

[backend_farm]

max_client_buffer = <memory size>

When the Relay Server consumes more than the "max_client_buffer" amount of virtual memory to buffer server response for a slow reading client, an urgent flow control signal will be sent to the Outbound Enabler to pause reading further server responses for this client. The Relay Server will signal the Outbound Enabler to resume the reading responses for the client when the client has consumed enough of the responses until only half of "max_client_buffer" worth of server responses for the client is left in the Relay Server. The default value of "max_client_buffer" is 1M. The "max_client_buffer" property can be adjusted online and the change takes effect immediately without restarting the Relay Server.

Similarly, per client shared memory is also being monitored, and isolated per client throttling was added. There is no user control for this element of the flow control system, as this element doesn't directly prevent shared memory exhaustion but it prevents deadlocking of the down-channel.

Monitoring of the global shared memory level has also been added, so that flow control can be triggered on any client even if their personal quota has not yet been reached. No new user control has been introduced for this element of the flow control system, but the behavior of the existing "shared_mem" control in the Relay configuration has changed. Previously, this value was used only for specifying the extra amount of shared memory for buffering traffic and state tracking, in addition to the amount implied by the configuration. The property had an effect of an amount equal to its size on the startup allocation. Online adjustment to the value had no effect on the total allocation until the Relay Server is restarted. Now, this property has an effect of an amount three times its value on the startup allocation of shared memory, and is broken down as follows:

- one third for buffering traffic and state tracking where user thought is enough at startup time.

- one third for future online growth of the number of tenants, and backend farm size of the tenants.

- one third as an extra blanket inside the auto calculated shared memory low water mark for triggering flow control.

The sum of these values are pooled together for all functional needs without usage partitioning. The factoring is for calculating the gross startup amount and also users to understand the new implications of online adjustment of this value. Online adjustment to this value still has no effect on the total allocation, but it does change the global shared memory low water mark for triggering flow control. Because of one third factor as a blanket inside the low water mark, users can make adjustments to the flow control behavior without restarting the Relay Server.

Here are some new usages of the shared_mem property in terms of online adjustments:

The administrator doesn't foresee growth in number of tenants and/or their size and so wants to reduce the shared memory low watermark in order to reduce triggering of unnecessary flow control. The shared_mem property can be reduced online. The change doesn't decrease allocation until restart, but it does reduce the blanket amount immediately by an amount equal to the change.

The administrator has seen some of the following after their Relay Server had been running for some time:

Substantial growth in number of tenants

Substantial growth in size of the backend farm

Substantial growth in number of clients

Growth in http response size

Addition of slower clients or slower network to the clients

Upgraded to faster network between RS and OE

and wants to increase the global shared memory low water mark so that flow control kicks sooner to protect against global shared memory exhaustion. This can be done by increasing "shared_mem" online without restarting the Relay Server. The change doesn't increase allocation until restart but it increase the blanket amount immediately by an amount equal to the change.

The "shared_mem" value to now allowed to be bigger than 4G.

This change has extended the existing protocol between the Relay Server and the Outbound Enabler so that upgrading to a new Outbound Enabler is required for this feature. The new Relay Servers and Outbound Enablers are backward compatible with older versions, but flow control cannot take place and so the Relay Server is not protected against memory exhaustion.

Before these changes, the Relay Server can run out of resource due to reaching the hard limit of shared memory or reaching the limit on virtual memory. This could have had different causes, including, but not limited to, an increase in the number of clients or backend farms/servers, http response size, and sustained slow reads from clients. Some exhaustion may have lead to deadlocks and the symptom may not have been fatal as current Relay Servers will resolve the deadlock, but the requests could still have been failed and shared resources were blacked-out during the deadlock period.

sers might experience

A workaround for this problem is to recreate the message store using qaagent -si, if that is possible.

Note, the iAS ODBC driver for Oracle must be upgraded to the same EBF level as the MobiLink server when the consolidated database is running on an Oracle server and the synchronization tables contain CLOBs or BLOBs.

This fix also strengthens validation of the cookie format, improves HTTP status codes, and provides finer HTTP status messages for easier diagnosis.

The responses being changed are summarized in the following table:

New response New response expires cookie? Old response as a record of behavior change

500 Relay server failed creating client traffic record n 500 Relay server error

500 Relay server failed initializing server access n 500 Relay server error

500 Relay server failed writing locking request list n 500 Relay server error

500 Relay server failed creating request n 500 Relay server error

500 Relay server failed initializing request n 500 Relay server error

500 Relay server failed adding initialized request n 500 Relay server error

401 The backend farm client_security property in the

Relay Server configuration disallow this type of client transport y 401 The backend farm rejected this client security

500 Relay server failed initializing backend farm access n 500 Relay server error

400 Bad affinity query y 401 Bad affinity query

400 Bad session id y 401 Bad session id

404 Backend farm is missing from URL y 404 Not found

404 Backend farm not found y 404 Not found

503 The backend farm is currently disabled n 404 The backend farm is currently disabled

400 Backend server encoded in cookie not found y --No change --

400 Bad request with no response from backend server y --No change--

Note, the HTTP status messages will remain generic for the Relay Server for Apache, which may not follow the new status codes. This Relay Server for Apache issue will be addressed as a separate platform dependent issue which is independent to this one.

Test connection failed because not all properties can be set.

Window Handle (BAD VALUE)

Continue with test connection?

[Yes] [No]

The message was informational only and Yes can be clicked. If the credentials and other connection information were correct, the connection succeeded. This problem has been fixed. Instead of returning a NULL window handle to the Microsoft software, the OLE DB Window Handle property is now marked as unsupported, which removes the warning message.

Note that the field separator was already being used when copying entire rows of values.

500 Abort due to version of this Relay Server extension conflicts with the version of the running rshost

Note, this change also fixes some error responses that didn't terminate the header list with \r\n.

- Improved script interaction, especially questions with (Y/n) choices. Defaults have been added to speed up progress.

- Output log is now flushed timely to give complete log if script is stopped at any time.

- Removed the option of keeping test services running to overcome a hanging problem.

- Wording has been improved in several places.

A workaround is to disable intra-query parallelism for the affected query.

select ... from directory_access_table where ... file_name like 'abc%' ...

the server would have returned a syntax error. This problem only existed if the comparison value (i.e. 'abc%') had no directory separators. For example, a query of the form:

select ... from directory_access_table where ... file_name like 'abc\def%' ...

would have worked just fine. This problem has now been fixed.

Also when using the VALIDATE TABLE or VALIDATE INDEX statements, the server could fail to report orphaned blobs when they did, in fact, exist. Whether or not this problem occurred depended on random contents of memory as well as the number of DML operations applied to the table prior to validation. This problem has been fixed.

When reporting a validation problem, the server returns an error to the client but also displays additional information in the server console. For orphaned blobs, a blank message was erroneously displayed in the console. This problem has been fixed.

of the column type definition. This has been fixed. Now values for NUMERIC columns will be cast to the column data type if needed.

1. The wizard would have installed the cloud software on all hosts which did not already have it, even if the hosts were not running the servers selected. Now, software is installed only on the servers selected.

2. The wizard would have reported that it was installing software even if it was only checking whether software needed to be installed. Now, the wizard reportss it is installing only if it really is installing software.

3. When cloud software was downloaded for both Windows and Linux, the wizard did not prevent attempting to use the software on a server which was running the wrong operating system. Now it does.

/** Adds a message header to each HTTP request. If addCustomHTTPHeader is called

* more than once with the same name parameter, the values are concatenated together

* into a comma-seperated list.

* <p>

* The following standard headers are set by ULj and cannot be changed using

* addCustomHTTPHeader: Connection, Content-Length, User-Agent, Content-Type, and

* Content-Length. Other headers may also be modified by the Java VM.

* <p>

* Not available on Android. On Android, specify a custom_header parameter using

* setExtraParameters

*

* @param name The name of the header

* @param value The value of the header

*/

public void addCustomHTTPHeader( String name, String value );

/** Returns a Hashtable containing the HTTP headers specified using addCustomHTTPHeader

*

* @return Returns a Hashtable containing the HTTP

* headers specified using addCustomHTTPHeader

*/

public java.util.Hashtable getCustomHTTPHeaders();

Custom cookies can be specified by calling addCustomHTTPHeader with "Cookie" as the header name.

/**

* Sets the userid and password used for Basic HTTP authentication as

* described in RFC 2617.

* <p>

* With Basic authentication, passwords are included in HTTP headers in

* clear text; however, you can use HTTPS to encrypt the headers and

* protect this password.

*

* @param userid The userid to use

* @param password The password to use

*/

public void setHTTPUserIDAndPassword( String userid, String password );

/**

* Returns the userid previously set by setHTTPUserIDAndPassword.

*

* @returns The userid previously set by setHTTPUserIDAndPassword

*/

public String getHTTPUserID();

/**

* Returns the password previously set by setHTTPUserIDAndPassword.

*

* @returns The password previously set by setHTTPUserIDAndPassword

*/

public String getHTTPPassword();

/** Enables or disables ZLIB compression.

* <p>

* By default, ZLIB compression is disabled

* <p>

* Only available for Android and BlackBerry

* <p>

* Corresponds to MobiLink client network protocol option "compression=zlib".

*

* @param enable Set to true to enable ZLIB compression, or false to disable

* ZLIB compression.

*/

public void setZlibCompression( boolean enable );

/** Sets the download window size for ZLIB compression.

* <p>

* Only available for Android and BlackBerry

* <p>

* Corresponds to MobiLink client network protocol option "zlib_download_window_size".

*

* @param size The compression window size specification, inclusively

* ranging from 9 to 15. This parameter is the base two

* logarithm of the window size. (the size of the history

* buffer)

*/

public void setZlibDownloadWindowSize( int size );

/** Sets the upload window size for ZLIB compression.

* <p>

* Only available for Android and BlackBerry

* <p>

* Corresponds to MobiLink client network protocol option "zlib_upload_window_size".

*

* @param size The compression window size specification, inclusively

* ranging from 9 to 15 for Android and 10 to 15 for BlackBerry.

* This parameter is the base two

* logarithm of the window size. (the size of the history

* buffer)

*/

public void setZlibUploadWindowSize( int size );

/** Sets the name of the file containing the end-to-end public key.

* <p>

* By default, this value is null, indicating that end-to-end encryption is

* not used.

* <p>

* Corresponds to MobiLink client network protocol option "e2ee_public_key".

*

* @param public_key The name of RSA public key file used in the encryption.

*/

public void setE2eePublicKey( String public_key );

/** Get the name of the file containing the end-to-end public key.

*

* @return the name of the file containing the end-to-end public key.

*/

public String getE2eePublicKey();

And there are also BlackBerry-specific methods to change the encryption type. ECC end-to-end encryption is available only for BlackBerry.

/**

* Pass this to setE2eeType to use RSA-based end-to-end encryption

*/

public final short E2EE_RSA = 0;

/**

* Pass this to setE2eeType to use ECC-based end-to-end encryption

*/

public final short E2EE_ECC = 1;

/**

* Set the type of end-to-end encryption to use. Pass one of StreamHTTPParms.E2EE_RSA or

* StreamHTTPParms.E2EE_ECC. The default is StreamHTTPParms.E2EE_RSA.

* <p>

* Only available on BlackBerry. ECC encryption is not supported on other platforms.

*

* @see StreamHTTPParms.E2EE_RSA

* @see StreamHTTPParms.E2EE_ECC

* @param type One of E2EE_RSA or E2EE_ECC

*/

public void setE2eeType( short type );

/**

* Returns the end-to-end encryption type being used.

* <p>

* Only available on BlackBerry. ECC encryption is not supported on other platforms.

* @return the end-to-end encryption type being used

*/

public short getE2eeType();

The public key used must be DER encoded.

The public key needed for end-to-end encryption can either be stored on an SD card or the device object store. When using an SD card, the parameter to setPublicKey should have the form "sdcard://<path>" where "<path>" is the absolute path to the file on the card. e.g. "file:///SDCard/ulj/public_key.der". When using the object store, use the file transfer utility built into ULj to download the file from the MobiLink server. To use file transfer to transfer a key it must have an extension of ".der".

In a related problem, if a server was using an annotated build, and the host also had an unannotated version of the software installed (with the same version number), the initial "Version" value in the property sheet was incorrect. This has also been fixed.

Server Properties

Create Rule

Edit Event Subscription

Fixed by minor sizing adjustments to these dialogs.

1) When the Relay Server is loaded with a high volume of requests and payload, transfer rate per client may thin out to a point that it cannot satisfy a preset requirement of IIS. The result is a dropping of connections and a Timer_MinBytesPerSecond event in the HTTPERR log. A change has been made in section 5b of the setup script to disable this minimum transfer rate requirement.

2) The Relay Server uses a default application timeout of 8 minutes. A change has been made in section 5b of the setup script to configure the connection timeout value of the web server to be 1 minute higher than the default application timeout. The client application can lower the timeout on a per request basis. The purpose of this change is to remove timeout issue due to mismatch timeout settings along the chain.

http://www.sybase.com/detail?id=1058536

There are no code changes for this issue. Note, that this problem does not occur with Solaris 10.

The following API was added:

Connection.changeEncryptionKey( String newKey )

For consistency the following APIs were added, which are equivalent to setDatabaseKey and getDatabaseKey respectively:

ConfigPersistent.setEncryptionKey( String key )

String ConfigPersistent.getEncryptionKey()

Following are examples of situations that cause the cache to grow large:

- a large upload

- an upload with with many blob values

- using the -cl option to force the cache to be large

- running on a machine with a large amount of memory

dbisql -c "links=tcpip(DoBroadcast=bogus)"

This problem has been fixed.

CHECKSUM { ON | OFF }

Attempting to execute a START DATABASE statement in the Interactive SQL utility with this clause would have resulted in an inappropriate error message which complained of an unexpected keyword. This has been fixed.

Engineering Description:

The CHECKSUM clause was added in 12.0.0. I'm not sure how this got missed. I noticed the omission when I started to look at adding support for the new MIRROR ON clause of START DATABASE.

Behaviour Changes:

n/a

Admin Tools, Installers and Other Affected Software:

n/a

Documentation Changes:

n/a

Testing Requirements:

A test was added to the ISQL grammar test suite.

Example:

CREATE SERVER ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ

CLASS 'SAODBC'

USING 'SQL Anywhere 12 CustDB';

CALL sp_remote_tables('ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ');

CALL sp_remote_columns ('ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ', 'ULCustomer');

CALL sp_servercaps ('ABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJABCDEFGHIJ');

The first two calls succeed. The sp_servercaps() call would have failed as the argument was limited to 64 characters, which is too short.

This problem has been fixed. The sp_servercaps() now accepts up to 128 characters.

Note that this problem does not affect ODBC based remote servers.

line utilities were not reported to the user. This has been fixed.

Note, there are two workarounds for this problem, both of which are considered better JDBC programming practices. The first is to use the ResultSet returned by calling executeQuery() directly and thereby avoid the second unnecessary call to getResultSet(). The other approach is to call execute() instead of executeQuery(), followed by a call to getResultSet().

- S1 must initially have been the primary, failed or otherwise have shutdown, causing a failover to S2

- S2 took over as primary

- while S1 was restarting, S2 must have lost quorum and have been shutting down

In which case it was possible for S1 to have become primary again, even though it was missing the transactions from when S2 was primary.

This has been fixed to ensure that S1 will not be primary in this case, and S2 will continue to be primary once it restarts.

1. Asynchronous Programming

The new asynchronous programming feature provides a simple technique to make code asynchronous.

Asynchronous code can make the user interface of client applications more responsive, it can also make server applications more scalable. Writing asynchronous code has traditionally involved installing a callback (also called continuation) to express the logic that occurs after the asynchronous operation finishes. This complicates the structure of asynchronous code as compared with synchronous code.

.NET 4.5 allows call into asynchronous methods without using callbacks, and without splitting code across multiple methods or lambda expressions.

The 'async' modifier specifies that a method is asynchronous. When calling an async method, a task is returned. When calling an 'await' statement against the task, the current method exits immediately. When the task finishes, execution resumes in the same method.

Calling an async method does not allocate any additional threads. It may use the existing I/O completion thread briefly at the end.

The following methods were added in SQL Anywhere ADO.NET provider to support asynchronous programming:

SAConnection.OpenAsync

SACommand.ExecuteDbDataReaderAsync

SACommand.ExecuteNonQueryAsync

SACommand.ExecuteReaderAsync

SACommand.ExecuteScalarAsync

SADataReader.GetFieldValueAsync

SADataReader.IsDBNullAsync

SADataReader.NextResultAsync

SADataReader.ReadAsync

SABulkCopy.WriteToServerAsync

Here are some examples:

internal async Task Execute()

{

using (SAConnection conn = new SAConnection("DSN=SQL Anywhere 16 Demo"))

{

SACommand command = new SACommand("select 1", conn);

int result = MethodAsync(conn, command).Result;

command = new SACommand("select top 10 * from SalesOrders", conn);

using (DbDataReader reader = await command.ExecuteReaderAsync())

{

while (await reader.ReadAsync())

Console.WriteLine(String.Format("{0}", reader[0]));

}

}

}

private async Task<int> MethodAsync(SAConnection conn, SACommand cmd)

{

await conn.OpenAsync();

await cmd.ExecuteNonQueryAsync();

return 1;

}

private async Task ExecuteSqlTransaction()

{

using (SAConnection connection = new SAConnection("DSN=SQL Anywhere 16 Demo"))

{

await connection.OpenAsync();

SACommand command = connection.CreateCommand();

SATransaction transaction = await Task.Run<SATransaction>(() => connection.BeginTransaction());

command.Connection = connection;

command.Transaction = transaction;

command.CommandText = "Delete From Departments Where (DepartmentID = 777 OR DepartmentID = 888)";

await command.ExecuteNonQueryAsync();

command.CommandText = "Insert into Departments(DepartmentID, DepartmentName) VALUES (777, 'HR')";

await command.ExecuteNonQueryAsync();

command.CommandText = "Insert into Departments(DepartmentID, DepartmentName) VALUES (888, 'Supporting')";

await command.ExecuteNonQueryAsync();

await Task.Run(() => transaction.Commit());

Console.WriteLine("Both records are written to database.");

}

}

private async Task AsyncSqlBulkCopy()

{

using (SAConnection conn = new SAConnection("DSN=SQL Anywhere 16 Demo"))

{

await conn.OpenAsync();

DataTable dt = new DataTable();

using (SACommand cmd = new SACommand(selStmt, conn))

{

SADataAdapter adapter = new SADataAdapter(cmd);

adapter.Fill(dt);

using (SABulkCopy bcp = new SABulkCopy(conn))

{

bcp.DestinationTableName = destTable;

await bcp.WriteToServerAsync(dt);

}

}

}

}

2. SACredential class.

A new class SACredential has been added for setting the credentials outside of the connection string via the new Credential property of SAConnection. Now the developer can create a SACredential object with a UserId and a SecureString Password to hold the credential values of a connection. This helps mitigate the memory dump vulnerability of keeping the User Name and Password in the connection string.

Here's an example:

private void OpenConnection()

{

SecureString password = new SecureString(); // txtPassword.SecurePassword;

password.MakeReadOnly();

SACredential credential = new SACredential( "dba", password );

using ( SAConnection conn = new SAConnection( "DSN=SQL Anywhere 16 Demo", credential ) )

{

conn.Open();

}

}

For example:

CREATE TABLE t1( a1 INT PRIMARY KEY )

CREATE TABLE t2( a2 INT PRIMARY KEY )

SELECT t1.a1, t2.a2 FROM t1, t2 ORDER BY t1.a1 DESC

Also, a query with a reverse index scan on the right hand side of a cross join may not have returned any rows.

For example:

SELECT t1.a1, dt.a FROM t1, (SELECT a2 FROM t2 ORDER BY a2 DESC) AS dt( a ) ORDER BY t1.a1 ASC

Both these issues have now been fixed.

with the predicate 'T.A = R.A' was incorrectly computed always using the predicate 'T.A > constant'. This may have affected the quality of the best plans for such queries. This has been fixed.

- the database character set was different from the operating system character set

- the database name (or alias) contained characters other than 7-bit ASCII characters

- an "ALTER DATABASE SET PARTNER FAILOVER" statement was executed, or a preferred partner was defined and the current primary was the non-preferred partner.

This has been fixed.

- the IIS7 auto install could not be invoked if the appcmd.exe utility was missing. This issue has been fixed so that appcmd.exe utility is not needed before triggering IIS7 [re]installation.

- the IIS7 Relay Server setup script could not handle a machine not having a domain suffix.

- the IIS6 & IIS7 Relay Server setup scripts were referencing sleep.exe which is not a standard utility on Windows. The reference has been removed.

- The "Replaying 0 bytes ..." message was confusing and has been suppressed.

- Added "Response headers submitted for sending" message.

- Logging Content-length expectation up front.

- Enhance Content-length replay status with remaining length.

- Added user friendly response status and header logging so that users don't need to suffer level 5 payload logging which is heavier and less readable.

- Moved user friendly request header logging from log level 5 to log level 4 so that user don't need to suffer level 5 payload logging which is heavier an less readable.

Relay Server configuration example:

[backend_farm]

description = a backend server farm

id = RSTEST02.F0

renew_overlapped_cookie= yes

Online update of the of the renew_overlapped_cookie property is supported.

Also, text index validation could have returned an error later than necessary. This has been fixed in version 12.0.1 and later.

fixed.

This has been fixed.

"The following option names are invalid or are not exposed by the registration key provided".

This has been fixed.

Note, a work around is to stop and restart copy node servers that cannot connect to their running parent.

- the application was connected to a primary server that lost quorum (the server lost the connection to both the mirror and arbiter servers)

- the application stayed connected to this server (the old primary server) even though the network connection to other servers dropped

- the application was in the middle of committing a transaction between the time that the old primary server lost its connection to the mirror and arbiter server, and when the old primary server restarted as the new mirror server because it lost quorum

- the old mirror server took over as the new primary (the mirror server must have been able to connect to the arbiter server for this to occur)

This has been fixed.

A work around is to manually run the CleanCloud task and then run the UpgradeCloudInfrastructure task again.

Engineering Description:

Note, a database with more than eight thousand columns that is run with a server that contains this fix cannot be run on an older server. Doing so will result in startup error -1007 "Unable to start specified database: '%1' is an invalid transaction log" on the older, unfixed server.

Note that in order to apply this fix, the database will need to be upgraded again once this fix has been properly deployed.

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.

For example:

select (select 1) union select 2"

the sub-query (select 1) was not evaluated properly. This 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.

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.

A workaround to this problem is to set the "server path" property using the SetProperty method to specify the location of the dbmlsync executable.

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.

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, �> 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.

This problem is now fixed.

- 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.

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.

For example:

SELECT c.name, d.b FROM fwd c,

(SELECT TOP 2 name FROM fwd2 WHERE name LIKE 慳%� ORDER BY name ASC) AS d( b )

WHERE c.name LIKE 慾%�

ORDER BY c.name DESC

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.

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.

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.

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.

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.

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.

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).

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.

Note that it is not possible to gain back the 搘asted� space until the compressed string is completely rewritten, and 揂LTER TABLE t SET comp_col=comp_col� will not do it either. The easiest way is to 揂LTER TABLE t ALTER comp_col NOT COMPRESSED�, followed by 揂LTER 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 it抯 done, all the strings will be properly, and efficiently, compressed, and any 搘asted� pages will now exist in the database file as free pages that can be re-used.

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.

SOLUTION: Fixed

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.

For example:

CREATE TABLE Foo ( num INT PRIMARY KEY DEFAULT AUTOINCREMENT, b1 BINARY(1), b2 BINARY(1), b3 BINARY(1) )

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, 0, 7 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, null, 8 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, 0, 9 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, null, 10 )

SELECT * FROM Foo ORDER BY b1, b2, b3 could result in an ordering like:

row: 0, 0, 7

row: 0, null, 8

row: null, 0, 9

row: null, null, 10

DROP INDEX Foo.I

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

SELECT * FROM Foo ORDER BY b1, b2, b3

row: null, null, 10

row: null, 0, 9

row: 0, null, 8

row: 0, 0, 7

This has been fixed.

For example:

CREATE TABLE Foo ( num INT PRIMARY KEY DEFAULT AUTOINCREMENT, b1 BINARY(1), b2 BINARY(1), b3 BINARY(1) )

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, 0, 7 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( 0, null, 8 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, 0, 9 )

INSERT INTO Foo( b1, b2, b3 ) VALUES( null, null, 10 )

SELECT * FROM Foo ORDER BY b1, b2, b3 could result in an ordering like:

row: 0, 0, 7

row: 0, null, 8

row: null, 0, 9

row: null, null, 10

DROP INDEX Foo.I

CREATE INDEX I ON Foo( b1, b2, b3 ) WITH MAX HASH SIZE 3

SELECT * FROM Foo ORDER BY b1, b2, b3

row: null, null, 10

row: null, 0, 9

row: 0, null, 8

row: 0, 0, 7

This has been fixed.

For example, in the following, c2 is not evaluated properly:

select * from (select id + id as c1, c1 as c2 from T) as DT(c1,c2)

This has been fixed.

The synchronization model could not be deployed.

Error for: Rendering macro APPEND_VAR

This has been fixed. A workaround is to enable that option and redeploy.

UltraLiteJ Error[-300]: Run time SQL error -- recordRowID 5832712

This has been fixed. When the maximum number of pages is reached, UltraLiteJ will now report SQLE_DBSPACE_FULL (UltraLiteJ Error[-604]: A dbspace has reached its maximum file size).

Applications encountering this error may be using too small a value for the database page size.

This has been fixed.

Cannot load DLL or shared object: 'ml.net12.dll' for Script Language: '.net'

For Java scripts, a similar error could have been displayed on operating systems with case-sensitive file names, or errors fetching Java scripts on Windows.

These problems have been fixed.

1 - iAnywhere.Data.SQLAnywhere.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.dll � for .NET 2

2 - iAnywhere.Data.SQLAnywhere.v3.5.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v3.5.dll � for .NET 3.x and 2

3 - iAnywhere.Data.SQLAnywhere.v4.0.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v4.0.dll � for .NET 4

4 - iAnywhere.Data.SQLAnywhere.v4.5.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v4.5.dll � for .NET 4.5

SetupVSPackage.exe has also been updated. A new option 憊ersion� has been added.

1 - If the version is �4�, SetupVSPackage.exe registers the v4 dll in machine.config file.

2 - If the version is �4.5�, SetupVSPackage.exe registers the v4.5 dll in machine.config file.

3 - When the version is not specified, SetupVSPackage.exe registers the v4.5 dll in machine.config file if .NET 4.5 is installed; otherwise, it registers the v4.0 dll in machine.config file.

Examples:

1 - SetupVSPackage.exe /i /v 4.5 � register the v4.5 dll

2 - SetupVSPackage.exe /i /v 4 � register the v4.0 dll

3 - SetupVSPackage.exe /i � register the v4.5 dll if .NET 4.5 is installed; otherwise, register the v4.0 dll.

SetupVSPackage.exe should be run to register the v4.0 provider for .NET 4 applications and register the v4.5 provider for .NET 4.5 / Entity Framework 5 applications.

As a workaround, prefetch can be disabled.

a. Setup without a domain

b. Let user enter the domain manually and test again.

Also, the setup step has been clarified so that using the domain user account for Relay Server State Manager service is a valid option if local online maintenance feature is not needed.

1 - The Relay Server State Manager could not start as the generated configuration contained removed properties (start and auto_stop). This has been fixed so that the invalid properties is no longer generated.

2 - Many links in the generated quick reference documentation no longer worked, and have now been fixed.

3 - The quick reference only demonstrated the use of the detailed status page, using the rs_admin extension only. Now a full set of pin-pointed status pages are added to the troubleshooting section.

The build script for the UltraLite library (SQLAnywhere/ultralite/iphone/build.sh) now selects which architectures to build based on the version of Xcode. Xcode 4.5 and later will build armv7 and the new armv7s. Older versions of Xcode will build armv6 and armv7 as before. An armv7s version of the obfuscated source is now included.

As a workaround, the client connection that is hung can be dropped using DROP CONNECTION. This will cause the client connection to immediately report an error.

SQLCODE=-836 "Procedure 'P1' is no longer valid"

Further, the database where the statement was executed could have failed to recover after a failure.

For example:

create or replace procedure dba.P1()

begin

select if 1=1 then 1000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 end if;

end

create or replace procedure dba.P2()

begin

select if 1=1 then 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001 end if;

end

For example:

select ROWID(T)

from sys.dummy T

group by dummy_col

This has been fixed. The following error is now returned:

Function or column reference to 'ROWID' must also appear in a GROUP BY

SQLCODE=-149, ODBC 3 State="42000"

To avoid the error, include the ROWID function in the GROUP BY list.

The only reliable workaround is to use an older version of glibc.

As a workaround, when stopping a mirror partner that is currently determining the role with an affected build, it is recommended that the server is terminated instead of stopped normally.

If this database corruption occurs, the database is corrupted but the transaction log is not. The database can be fully recovered by applying the current transaction log file(s) to a backup.

Also, version support for the ADO.NET v4 provider to the Entity Framework is now limited to Entity Framework versions 4.4.x and up.

A workaround is to disable intra-query parallelism for affected queries.

-890 "Statement size or complexity exceeds server limits"

In some cases, a statement processing an XML document could not have been stopped by cancelling or dropping the connection. This has been fixed

A work around is to restart the server that is not writing or applying changes.

For example:

create procedure usr.FullName( ...;

COMMENT TO PRESERVE FORMAT ON PROCEDURE "USR"."FullName" IS ...;

The same problem would have occurred for functions, triggers, views, and events. These issues have been fixed.

-134 "Feature 'OPENXML with non-constant query' not implemented"

-1159 "Non-constant or unknown text query string."

In order for the error to be returned, the variable must have been used in a larger expression such as a cast or string concatenation. The failure would have occurresd intermittently, for example on the 11th execution of the statement. This has been fixed.

- synchronization including downloaded deletes

- concurrent commit operation during the synchronization download cleanup phase

- shutdown (or application termination) soon after the synchronization completes

This has now been corrected.

For example, the following predicates are now optimized as follows (where, UDF is a user-defined function):

x=3 and x in (1,2,3) --> x=3

x>=3 and x in (1,2,3) --> x=3

x>3 and x in (1,2,3) --> FALSE

x=2 and x in (1,2,UDF(3)) --> x=2

x=3 and x in (1,2,UDF(3)) --> x=3 and x in (1,2,UDF(3))

Note, line length in log files can become very long when the MobiLink server "-vr" option (display column values) is used.

Note that while the trigger owner is syntactically valid, it is ignored by the server.

Also in rare timing dependent cases, when dropping an arbiter server from a mirroring setup, it was possible for old state information to be left behind in the arbiter server抯 state file. This could have caused difficulties later on if the same server was started as a high availability server for the mirroring system. This has been fixed as well.

Identifiers:

The following characters are currently not permitted in identifiers:

Double quotes

Control characters (any character less than 0x20)

Backslashes

In addition to the above, the following characters will now not be permitted in an identifier:

Square brackets ([])

Back quotes (`)

Aliases:

1. select-list : expression [ [ AS ] alias-name ]

The new restrictions on identifiers now apply to the characters permitted in an alias-name.

2.select-list : alias-name = expression (Transact-SQL dialect)

The new restrictions on identifiers now apply to the characters permitted in a Transact-SQL dialect alias-name.

Notes:

New restrictions described above will only be applied if the database is created using SQL Anywhere 16.0.0 software.

Databases upgraded to version 16.0.0 as well as all databases created and/or upgraded to older versions will continue to apply the current restrictions and continue to allow newly prohibited characters inside identifiers and aliases.

If pre-version 16.0.0 database has any square brackets or back quotes in an identifier, they must be removed before performing a reload; otherwise the reload will fail.

This problem is related to a possible bug in the transparent huge pages (THP) feature introduced in these operating system versions. Red Hat bug 891857 has been created to track this issue.

The problem can be triggered by calling an external environment, xp_cmdshell, or other procedure that causes a fork while other I/O is occurring. A known limitation with the Linux kernel limits the use of fork while doing O_DIRECT I/O operations. Essentially what can happen is that the data can come from or go to the wrong process� memory after the fork. SQL Anywhere performs O_DIRECT I/O operations according to the documented safe usage. However, THP appears to cause further problems and the O_DIRECT I/O data comprising database page reads/writes appears to get lost.

This has been fixed by disabling THP on the SQL Anywhere cache memory where possible. We are working with Red Hat to identify a solution within the operating system.

There are two possible workarounds:

1. disable THP on a system-wide basis with one of the following methods:

echo never > /sys/kernel/mm/transparent_hugepage/enabled

echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled

boot with transparent_hugepage=never

2. disable O_DIRECT I/O for database file reads/writes with one of the following methods:

use the -u flag on the server command line

set SA_DISABLE_DIRECTIO=1 in the environment before starting the server

Transparent huge pages cannot be disabled just for the SQL Anywhere cache memory on Red Hat Enterprise Linux 6. SQL Anywhere now disables direct I/O if transparent huge pages are enabled and cannot be disabled on a per-allocation basis. A warning will be printed as the database file is being opened to indicate that direct I/O is disabled due to this bug. This is similar to how SQL Anywhere handles file systems that do not support direct I/O.

Customers using RHEL 6 who wish to continue using direct I/O should use the previously-stated command to disable THP at the system level.

This problem is related to a possible bug in the transparent huge pages (THP) feature introduced in these operating system versions. Red Hat bug 891857 has been created to track this issue.

The problem can be triggered by calling an external environment, xp_cmdshell, or other procedure that causes a fork while other I/O is occurring. A known limitation with the Linux kernel limits the use of fork while doing O_DIRECT I/O operations. Essentially what can happen is that the data can come from or go to the wrong process� memory after the fork. SQL Anywhere performs O_DIRECT I/O operations according to the documented safe usage. However, THP appears to cause further problems and the O_DIRECT I/O data comprising database page reads/writes appears to get lost.

Until this is fixed, there are two possible workarounds:

1. disable THP on a system-wide basis with one of the following methods:

echo never > /sys/kernel/mm/transparent_hugepage/enabled

echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled

boot with transparent_hugepage=never

2. disable O_DIRECT I/O for database file reads/writes with one of the following methods:

use the -u flag on the server command line

set SA_DISABLE_DIRECTIO=1 in the environment before starting the server

Similarly, the same bad error message would have been presented when exporting into a database table for which the user did not have permission to select rows.

These problems have been fixed. The error message now clearly indicates that you don't have permission to select from the table.

Users could encounter this problem when executing the INPUT or OUTPUT USING statements, or when using the Import or Export wizards.

1) a connection to the database had an outstanding transaction

2) while there was this outstanding transaction, the transaction log was renamed or truncated

3) the database had no free pages and needed to grow during the checkpoint that was part of renaming or truncating the transaction log

4) the connection from 1) still had an outstanding transaction during the last checkpoint before the database stopped or was backed up

5) the database was not shut down cleanly, or it was backed up

6) attempting to start the database from 5) required recovery and could have in rare cases failed with the error "Fatal error: undo log corrupted after log rename".

Other failures may have been possible if all of the above conditions applied. This has been fixed to avoid corrupting the undo log.

Note that the database and server properties that correspond to those enabled by the 杬t server option are only updated for connections that have request timing enabled or disabled at their individual connection time.

When using a database character set that is different than the default character set for the operating system, dbremote must be instructed to perform explicit data conversion to that character set on its connection string:

e.g. dbremote -c 揅HARSET=utf8;厰

or instruct dbremote to always use the CHAR character set of the target database to apply the remote CHAR data:

e.g. dbremote -c 揅HARSET=none;厰

Also, It was possible for the table cell which contained the matched text to be hidden under the "Find in Results" window. Now, the window is automatically moved out of the way.

Note that connecting using user data sources worked as expected. If was only system data sources that were affected by this problem.

Note that two possible workarounds are:

1) create an externlogin for dbo, or

2) set the new extern_login_credentials database option to 揕ogin_user�

1) If the mirror or copy node was requesting pages from the primary or parent (it had recently started and had not caught up to the current log operation) and renamed log files required by the mirror or copy node had been deleted on the primary or parent since the mirror or copy node started requesting pages, then the mirror or copy node could have stopped applying log operations or failed with the assertion 100904. This has been fixed so that that primary or parent now correctly detects this case (a required renamed log file has been deleted) and logs the message "Database <DBName> mirroring: failure when requesting pages on remote server <ServerName>: missing transaction log with start offset <Offset>" (where <DBName>, <ServerName> and <Offset> are replaced with appropriate values). If this occurs, the mirror or copy node will log the message " Database "asatest" mirroring: database is not compatible with primary; files must be replaced� and the database and possibly the server will stop.

2) The message "Database server shutdown due to incompatible files for database mirroring� could have been displayed if an incompatible log file was detected even though the server was not stopped. If there is more than one database running on the server, the affected database is stopped, but the server is not stopped. This has been fixed so that this message is only logged if the server is actually being stopped.

3) In rare timing depending cases, after one or more ALTER DATABASE SET PARTNER FAILOVER statements, neither partner could have taken the role of primary. This has been fixed. As a workaround, the ALTER DATABASE ... FORCE START statement can be used to force a partner to take over as partner if this problem occurred.

4) If a copy node or async mirror got significantly behind writing log pages, it could have caused requests to the primary database to block for more than a minute. This has been fixed so that the primary will not be blocked for more than about 10 seconds.

{fn TIMESTAMPADD(<interval>, <integer-expr>, <timestamp-expr>)}

Returns the timestamp calculated by adding <integer-expr> intervals of type <interval> to <timestamp-expr>. Valid values of <interval> are shown below.

{fn TIMESTAMPDIFF(<interval>, <timestamp-expr1>, <timestamp-expr2>)}

Returns the integer number of intervals of type <interval> by which <timestamp-expr2> is greater than <timestamp-expr1>. Valid values of <interval> are shown below.

These escape functions are mapped directly to the SQL Anywhere DATEADD/DATEDIFF functions.

The <interval> type can be one of the following:

<interval> SQL Anywhere DATEADD/DATEDIFF date-part mapping

========================= ==========================================

SQL_TSI_YEAR YEAR

SQL_TSI_QUARTER QUARTER

SQL_TSI_MONTH MONTH

SQL_TSI_WEEK WEEK

SQL_TSI_DAY DAY

SQL_TSI_HOUR HOUR

SQL_TSI_MINUTE MINUTE

SQL_TSI_SECOND SECOND

SQL_TSI_FRAC_SECOND MICROSECOND

Examples:

// Number of days in February, 2013

SELECT {fn TIMESTAMPDIFF(SQL_TSI_DAY, '2013-02-01T00:00:00', '2013-03-01T00:00:00' )}

28

// Timestamp for 28 days after February 1, 2013

SELECT {fn TIMESTAMPADD(SQL_TSI_DAY, 28, '2013-02-01T00:00:00' )}

2013-03-01 00:00:00.000000

- the blob to insert was longer than its column INLINE value

- the table contained a large number of blobs that were longer than about 8 database pages (blobs with blob index)

- the columns containing these blobs were created with a blob index (default)

- large parts of the table were not in cache

This has been fixed.

To work around the problem the blob indexes can be dropped by running the following statement for all long varchar or binary columns with blobs longer than 8 pages:

alter table <table-name> alter <columns-name> no index

To fix the problem in existing databases rebuild the database or drop and recreate the blob index by running ALTER TABLE. This must be done with a fixed version of the server and only on table columns with above conditions.

Switch: Feature:

SERVER64 SQL Anywhere Server (64-bit)

CLIENT64 SQL Anywhere Client (64-bit)

SERVER32 SQL Anywhere Server (32-bit)

CLIENT32 SQL Anywhere Client (32-bit)

MOBILE SQL Anywhere for Windows Mobile

UL UltraLite

ML64 MobiLink (64-bit)

ML32 MobiLink (32-bit)

SR64 SQL Remote (64-bit)

SR32 SQL Remote (32-bit)

AT64 Administration Tools (64-bit)

AT32 Administration Tools (32-bit)

SM64 SQL Anywhere Monitor (64-bit)

SM32 SQL Anywhere Monitor (32-bit)

RS64 Relay Server (64-bit)

SAMPLES Samples

FIPS FIPS-approved Strong Encryption

CAC CAC Authentication

HA High Availability

IM In-Memory Mode

SON Read-only scale-out

Server and Client features are now separately selectable in both 64-bit and 32-bit installs. The following features have been removed: ECC Strong Encryption, QAnywhere, and Relay Server (32-bit).

See also the Comments section of the following DocCommentXchange page: http://dcx.sybase.com/index.html#sa160/en/dbprogramming/using-silent-install-deploy.html*d5e50990

Note that SQLAnywhere does not permit the characters 慬� or 慮� inside identifiers, and so it follows that these will not be accepted in JSON quoted strings.

Also, sp_parse_json() would have accepted bare pairs that were not in a row. This has been fixed to match with JSON standards.

For example, the following would not have given an error, but is now no longer accepted:

call sp_parse_json('tvar','a:b');

The FOR JSON clause would have escaped the forward slash character (�/�) in double quoted text. This has been fixed and forward slashes will no longer be escaped.

A workaround is to put the procedure in the FROM clause of a SELECT statement, rather than call it immediately.

A Microsoft Data Link Error could have occurred with newer versions of Microsoft software when using the SQL Anywhere OLE DB provider. When the Test Connection button was clicked, the following message would have been displayed when the error occurred:

Test connection failed because not all properties can be set.

Window Handle (BAD VALUE)

Continue with test connection?

[Yes] [No]

The message was informational only and Yes can be clicked. If the credentials and other connection information were correct, the connection succeeded. This problem has been fixed. Instead of returning a NULL window handle to the Microsoft software, the OLE DB Window Handle property is now marked as unsupported, which removes the warning message.

===

The solution to this problem was incorrect. Some applications require support for the Window Handle property and terminate if not supported (e.g., ROWSETVIEWER application).

The problem has been corrected. The Window Handle property value was improperly described as 32-bit in a 64-bit application.

This should result in no user visible change in behavior, but it will ensure that going forward behavior seen when testing a synchronization model in the test window is consistent with that seen when the model is actually deployed using the deployment wizard.

All threads are blocked [-307] ['40W06']

This problem was more likely to occur with a UNION query where multiple branches could use parallel execution. This problem has now been fixed.

- the query contained a proxy table and a nested query block with an outer reference

- the nested query block used a view with a non-flattable select statement

- the outer reference in the nested query block could have been pushed into the select statement of the view

For example, in the following query T1 is a proxy and would have returned the error "Correlation name 'V0' not found".

create view V1 as select 2 as col1 union select 1;

select ( select col1 from V1 where col1 = V0.c21 ) as D from T2 V0, T1;

This has been fixed.

For example, the table ColumnPerm is defined below as owned by dba and user httpAuthUser3 is granted select on only the id and v1 columns

CREATE TABLE dba.ColumnPerm(

id INTEGER NOT NULL DEFAULT AUTOINCREMENT,

v1 VARCHAR(128) NOT NULL,

v2 VARCHAR(128) NOT NULL,

PRIMARY KEY( id ) )

go

GRANT SELECT( id, v1 ) ON dba.ColumnPerm to httpAuthUser3

go

This has been fixed. When an OData Producer connects using httpAuthUser3 (in the example above), it will see meta data for table ColumnPerm with columns id and v1 (but not v2).

- When suggesting SQL statements, "CREATE TRIGGER" could have appeared in the list of suggestions twice.

- When writing a CREATE TRIGGER statement, the text completer would have suggested only "CREATE TRIGGER" statements rather than keywords that matched what was typed so far.

- Only SQL keywords and owner names were suggested. Now, table names are also suggested.

Issues related to other types of CREATE statements have been fixed:

- CREATE ROLES and CREATE LDAP SERVER statements were never suggested. They are now suggested where appropriate.

- If the second token in a CREATE statement was misspelled the completer would have suggested only statements which started with the keyword CREATE. Pressing Enter would then have replaced the entire statement text with one of the CREATE statements, which was seldom the user's intent.

Note that this is only an issue in the metadata document itself. The actual values for Edm.Decimal properties are enforced to be within the allowed range as defined in the OData spec.