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

@T - @W - @I:@J - @P - "@M @U @V" - @R - @L - @E

Note that the problem did not affect growth of the transaction log.

Note, a potential workaround is to modify the query so that it is no longer suitable for the semantic transformation that flattens the query block.

A workaround for this issue is to run the deployment wizard as an administrator.

select * from saoledblink..SYS.syscollation;

would have failed with the error:

Msg 7356, Level 16, State 1, Line 1

The OLE DB provider "SAOLEDB.11" for linked server "saoledblink" supplied nconsistent metadata for a column. The column "collation_order" (compile-time ordinal 4) of object ""SYS"."syscollation"" was reported to have a "DBCOLUMNFLAGS_ISFIXEDLENGTH" of 0 at compile time and 16 at run time.

The problem occurred for BINARY(n) columns. The DBCOLUMNFLAGS_ISFIXEDLENGTH schema attribute was set true (0x10) at run time. This problem has been fixed.

Note, in addition to getting an updated server, an ALTER DATABASE UPGRADE must be execute on each database, to update the metadata for jConnect and Open Client applications.

defaultShowResultsForAllStatements=false

defaultShowMultipleResultSets=false

These lines, if present, control the default behavior for displaying results. In the "Options" window, these options are displayed in the "Results Processing" box on the "Results" tab when "SQL Anywhere", "UltraLite", or "Sybase IQ" are selected. The default for both options is "false".

An optional prefix can be used to limit the effect to a specific database type. If no prefix is present, the directive applies to all database types. The prefixes are:

SQLAnywhere. For SQL Anywhere

Ultralite. For Ultralite

SybaseIQ. For IQ

For example,

defaultShowResultsForAllStatements=true

would change the default for all database types to show results for all statements, but

SQLAnywhere.defaultShowResultsForAllStatements=true

would change the default only for SQL Anywhere databases. The defaults for Ultralite and IQ would be unaffected. If a directive appears both with and without a prefix, the prefixed one has precendence for the given database type.

These directives can be specified independently. If one is missing, its default value (false) is assumed.

Notes:

1. These lines control only the default values for the two preferences. The defaults are used only if no saved user perferences are found. The user preferences are saved each time DBISQL is run.

2. "defaultShowMultipleResultSets" does not apply to UltraLite because UltraLite statements cannot return more than one result set.

Examples:

CALL SA_SET_HTTP_HEADER( '@HTTPSTATUS', '999:User Code'); // outputs status code with message: '999 User Code'

CALL SA_SET_HTTP_HEADER( '@HTTPSTATUS', '999'); // output status code only with no text message: '999'

Limitations/Recommendations:

- Status codes must be >= 100 and <= 999.

- A user defined status text message is not translated into database character-set when logged (log protocol option).

- It is recommended that user defined status messages are in English.

HTTP status code/message additions:

305 Use Proxy

307 Temporary Redirect

415 Unsupported Media Type

416 Requested Range Not Satisfiable

417 Expectation Failed

505 HTTP Version Not Supported

Changes to DBSCHEMA_PROVIDER_TYPES:

Changed CHAR type so that IS_FIXEDLENGTH is now FALSE (0).

Changed NCHAR type so that IS_FIXEDLENGTH is now FALSE (0).

Changed NUMERIC type so that IS_FIXEDLENGTH is now TRUE (1).

Changed DECIMAL type so that IS_FIXEDLENGTH is now TRUE (1).

Changed LONG NVARCHAR type so that IS_LONG is now TRUE (1).

As a result of these changes, "compile time" results will now agree with "run time" results (ref. MS Linked Servers).

Support was added for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.

Changes to DBSCHEMA_COLUMNS:

The COLUMN_FLAGS column of the OLE DB schema rowset has been corrected.

The DBCOLUMNFLAGS_ISFIXEDLENGTH indicator is now set on for fixed length types (e.g., smallint, float, money).

The DBCOLUMNFLAGS_ISLONG indicator is now set on for LONG types (e.g., LONG VARCHAR).

Added support for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.

Changes to DBSCHEMA_PROCEDURE_COLUMNS:

Added support for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.

Changes to DBSCHEMA_PROCEDURE_PARAMETERS:

Added support for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.

An example:

select * from

product p

where exists (select 30 as id from dummy, product p2 where p2.id-1 > 30+p.id )

and p.id+1 = 301 and exists(select 1 from sales_order_items soi where soi.id > p.id)

Note that newer versions of jConnect and Open Client support microsecond precision, so no rounding to 1/300th of second will occur if an application uses these newer versions.

Note that applications may be forced to use small threshold values if they have many transactions awaiting synchronization. This is fixed by synchronizing more frequently.

Expecting 1 parameters in script, but only found 4: update ml_qa_global_props set modifiers = ?, value = ? where client = ? and name = ?

Unable to open upload_update .

This has been fixed by a change to the upload_update script for the table ml_qa_global_props, version ml_qa_2.

For example:

Given a table Test that had synchronization disabled, after the sequence

INSERT INTO Test( num, val ) VALUES( 1, 0 )

UPDATE Test SET val = 2 WHERE num = 1

COMMIT

it would have no longer been possible to alter the schema of table Test. Attempts to do so would have resulted in UltraLiteJ Error[-121]: Permission denied: unsynced transactions

This has now been fixed.

For example, if the query below has the plan "p<xx> Exchange p<xx>", the output of the Exchange operator must preserve the ordering of the rows on "p.id" provided by the scans of the index "xx". This query crashed the server before this fix. The prefilter predicate is "now() > now()".

select * into #temp1 from product;

create index xx on #temp1(id);

select p.id from #temp1 p where now() > now() order by p.id;

For example, the following two lines of dbinfo:

Respect letter-case when comparing: No ('A' equal to 'a')

Collation sequence: 1252LATIN1 (Code Page 1252, Windows Latin 1, Western)

have been replaced by:

CHAR collation sequence: 1252LATIN1(CaseSensitivity=Ignore)

CHAR character set encoding: windows-1252

NCHAR collation sequence: UCA(CaseSensitivity=Ignore; AccentSensitivity=Ignore; PunctuationSensitivity=Primary)

NCHAR character set encoding: UTF-8

which matches the output displayed by the Initialization utility.

Examples:

CREATE SERVICE echo ...

CREATE SERVICE echo_elem URL ELEMENTS ...

CREATE SERVICE echo_path URL ON ...

HTTP Requests:

PUT echo?id=1 HTTP/1.1 ==>

HTTP_VARIABLE('id') == 1,

HTTP_HEADER('@HTTPQUERYSTRING') == id=1

PUT echo_elem/one/two?id=1 HTTP/1.1 ==>

HTTP_VARIABLE('id') == 1,

HTTP_VARIABLE('url1') == one,

HTTP_VARIABLE('url2') == two,

HTTP_HEADER('@HTTPQUERYSTRING') == id=1

PUT echo_path/one/two?id=1 HTTP/1.1 ==>

HTTP_VARIABLE('id') == 1,

HTTP_VARIABLE('url') == one/two,

HTTP_HEADER('@HTTPQUERYSTRING') == id=1

For more information on in-lining procedures see "SQL Anywhere 11.0.1 � SQL Anywhere Server - SQL Usage � Query Processing � Query optimization and execution � Semantic query transformations � In-lining simple system procedures "

http://dcx.sybase.com/index.html#1101en/dbusage_en11/ug-optimizer-s-4906935.html

Note, the installer for the 10.0.1 3976 EBF worked correctly.

with a comma in their names, provided the name is properly quoted.

This problem also affected applications using dbmlsync through the dbtools interface. They could have crashed when DBToolsFini was called. This has now been fixed.

As a workaround, the following command may be run to fix the permissions of the JAR files:

find $SQLANY11 -name "*.jar" -exec chmod 444 {} \;

Transaction log file '<logfile1>' overlaps with transaction log file '<logfile2>'

This has been fixed.

See also Engineering case 608095.

Note, there are very few ODBC drivers that do not support UNICODE entry points. As a result, this problem affects a very small number of applications that use remote servers.

Note that this problem does not affect versions of Open Client prior to 15.5.

To specify a maximum cache size that will leave less than 512MB available, the new "-chx <size>" option can be used instead of "-ch <size>". Note, however, that the use of -chx is strongly discouraged unless great care is taken to evaluate what cache size can safely be used in a specific installation. To use very large caches, the use of 64-bit software is recommended.

On 64-bit systems, address space is extremely large and -ch and -chx are equivalent but -ch is preferred.

For example:

select datepart( ms, '14:44:33.9876543211' )

would have returned 128, instead of the expected result of 987.

This has been fixed by truncating the number of seconds in a timestamp at 9 decimal places before it is used.

For example, the following query would have failed:

SELECT test.Column1 FROM proxy_t test GROUP BY test.column1

whereas the following queries:

SELECT test.column1 FROM proxy_t test GROUP BY test.column1,

and

SELECT test.Column1 FROM proxy_t test GROUP BY test.Column1

would have succeed. This problem would only have occurred if the local database was case sensitive and proxy_t was a proxy table. This has now been fixed.

Additional changes to the application were also made to improve usability. First, functionality that required an active database connection such as the Execute button are disabled if there is no active connection. Second, a simple SELECT statement is generated based on the table selected from the table list control.

Note, this can be worked around by setting the reserved_keywords option to 'limit'.

Note, this problem was introduced by the changes for Engineering case 609739.

Note, users who do not have this fix can still view the underlying data by manually by querying the sa_diagnostic_* tables as described in the documentation.

assertion 100904: failed to redo a database operation - Error: Table 'sa_load_table_data_X' not found

This has been fixed.

Workarounds for this problem are to add WITH CHECKPOINT ON to the LOAD TABLE statement (which makes the problem much less likely to occur, but does not completely eliminate it), or to use WITH ROW LOGGING instead.

Also, fill_sqlda could have filled a sqlda with negative sqllen values for the types DT_VARCHAR, DT_NVARCHAR or DT_BINARY with input sqllen values of 32765 or more.

This has been fixed so that the error "Invalid sqllen field in SQLDA" is returned, and fill_sqlda never fills with a negative sqllen value.

CircularString (-20 -20, 20 -20, 20 20, -20 20, -20 -20)

The duplicated points might not have been noticed, because operations that input a curve drop duplicated points. The extra point could be detected in the output of ST_AsText('version=1.1') though. This has been fixed.

IANYWHERE.MOBILINK.CLIENT.DLL

IANYWHERE.DATA.SQLANYWHERE.DLL

but they were not included in the assembly/v2 directory.

These files were being deployed directly into the GAC, but were not being put into the assembly/v2 directory. This has been corrected, and they are now installed into both locations.

As a workaround, automatic loading of the UltraLite plugin can be disabled by editing the file "$HOME/.sybase/Sybase Central 6.0.0/.scUserPreferences600" and changing the line

"ProviderData/ultralite1101/Autoload=true" to read "ProviderData/ultralite1101/Autoload=false".

For example:

select * from T where (T.X = 10 and T.Y = 20 ) OR ( T.Z = 30 and T.W = 40)

create index XY on T(X, Y)

create index ZW on T(Z, W)

A possible access plan is the union of the index scans: T<XY> UNION T<ZW>.

SELECT ... FROM dirTab WHERE file_name='...'

where dirTab is a directory access table, then the server would have incorrectly returned a result set in cases where the specified file_name extended beyond the subdir limit of the directory access server. This problem has now been fixed and a proper empty result set now gets returned for file names that violate the subdir limit.

A workaround is to periodically issue an inconsequential DDL statement to the server (for example, CREATE TABLE FOO(id int); DROP TABLE FOO). This will flush the plan caches and allow each connection to use fully-cached plans for these simple statements.

This issue had no impact on statements involving more than one table, or on statements that are not subject to plan caching.

A workaround is to increase the amount of memory available to the server.

"Unable to start specified database: Cannot use log file '%1' since it is shorter than expected".

No data was actually been lost, but the log metadata would have needed to be patched by hand to allow the database to recover. This problem, while very rare, was more likely on systems with very large transactions running on a small number of connections. This has been fixed.

For example,

        HRESULT hr = rowset::InsertRow( hChapter, hAccessor, pData, NULL );

would have resulted in a memory leak, since phRow (the 4th argument) is NULL. This problem may have occurred when using the provider with SQL Server Integration Services (SSIS).

This problem has been fixed.

Note, this problem was seen with SQL Server Integration Services applications on 64-bit Windows platforms, it does not appear in ADO applications.

"Error for: Method makeUniqueConstraints threw exception for reference $HELPER in template script-defs\remote.vm"

This has been fixed.

See also Engineering case 617811.

- procedure P1 generates a result set using a SELECT which references another procedure P2 in the FROM clause

- P1 did not include a RESULT clause defining the result set

- the procedure id of P1 was less than that for P2

This has been fixed.

Note, service types: HTML, XML, RAW, JSON may contain a NULL statement only with AUTHORIZATION ON, DISH services always contain a NULL statement and SOAP services must contain a (non-NULL) statement.

The SQL Anywhere 12 plug-in could not be loaded because it uses components that are not accessible. Please change the classpath in the plug-in properties.

java.lang.ClassNotFoundException: ianywhere.sa.plugin.SAPlugin

This has been fixed.

Workaround 1: Launching Sybase Central from Terminal would correctly register the plugins.

Workaround 2: Set the LANG environment variable in the Finder's environment. To do this, add the LANG environment variable to ~/.MacOSX/environment.plist, log out, then log back in.

Note, launching Sybase Central from Terminal would correct the problem.

For example, the following example incorrectly returned the error "Transform from SRID 4326 to 0 not supported. SQLCODE=-1444, ODBC 3 State="HY000"":

with recursive V( id, geom) as (

select 1, new ST_Point(0,0,4326)

union all

select id-1, null from V where id=0

)

select * from V

This has been fixed.

the authentication property of the Network server. The has now been corrected. The Personal server was not affected.

Note, when creating proxy tables to Oracle tables that contain varchar2 columns, the Oracle ODBC driver does not provide enough information for SQL Anywhere to correctly map the varchar2 columns to nvarchar columns. It is therefore strongly recommended that an explicit column list be used when creating proxy tables to Oracle tables containing varchar2 columns, and that the explicit column list appropriately maps the varchar2 columns to nvarchar columns.

For example:

1) suppose the domain controller was Windows machine DC, and

2) suppose the application was running on Windows machine App with Windows userid AppUser, and

3) suppose the database server was running on Windows machine SAServ with Windows userid ServUser, and

4) suppose the domain controller had a Windows user group GRP of which AppUser was a member, and

5) suppose the database did not grant explicit integrated login privileges to AppUser but instead had granted integrated login privileges to GRP instead,

then there was a chance that the application would fail to establish an integrated login to the db userid that GRP was mapped to. This problem has now been fixed.

For example, the following could have given an error inappropriately:

select ST_GeomFromText( 'Polygon ((-7.2 57.914477861, -7.127601901 57.8, -6.9 57.8, -6.9 57.980214095, -7.2 57.936174862, -7.2 57.914477861), (-6.974221298 57.904050613, -7.041167328 57.904889847, -7.061722824 57.953496719, -6.974221298 57.904050613))' ) g, 

ST_GeomFromText( 'Polygon ((-7.006389618 57.881387711, -6.993610382 57.918611526, -7.077777863 57.879999161, -7.006389618 57.881387711))' ) m, 

g.ST_SymDifference( m ) 

This has been fixed.

ST_Point::ST_X()

ST_Point::ST_Y()

ST_Point::ST_M()

ST_Point::ST_Z()

ST_Point::ST_Lat()

ST_Point::ST_Long()

ST_Point::ST_X(Double)

ST_Point::ST_Y(Double)

ST_Point::ST_M(Double)

ST_Point::ST_Z(Double)

ST_Point::ST_Lat(Double)

ST_Point::ST_Long(Double)

They have been corrected.

The following illustrates the problem, note that the clause consuming the substitution parameter is commented out:

create function bad_params(str long varchar, len int)

returns long varchar

url 'http://127.0.0.1/no_serv

Also, if a synchronization profile was first copied to the clipboard and then modified before being pasted back from the clipboard into Sybase Central, then the pasted synchronization profile would have contained the modifications. This behaviour was at odds with all standard clipboard implementations and has been corrected. Now, a copy of the synchronization profile is placed in the clipboard and a copy is pasted from the clipboard so that the pasted object exactly matches the copied object.

Usage:

-x http(...;log_bad_request={yes|no})

-x https(...;log_bad_request={yes|no})

-x oe(...;log_bad_request={yes|no})

The default value for these noew options is "no".

If log_bad_request is enabled and a request disconnects before the server receives a complete set of HTTP headers, the server will print these errors:

[-10117] Stream Error: Failed reading an incomplete HTTP request

[-10117] Stream Error: This connection will be abandoned because of previous errors

If log_bad_request is enabled and a request contains an unknown User-Agent or unknown request type, the server will print these errors:

[-10117] Stream Error: Unknown HTTP User-Agent or request type

[-10117] Stream Error: This connection will be abandoned because of previous errors

This option is most useful when debugging network issues. For example, you can connect to the ML server using a web browser on the remote device and if the device can reach the server, then these errors will be printed.

systems were not affected. This has been fixed.

A workaround is to set max_client_statements_cached to 0 before creating the request log. Note that if a request log is to be analyzed using the tracetime.pl Perl script, it must also be generated with max_client_statements_cached set to 0.

- ST_IntersectsRect should return NULL, but was returning FALSE

- ST_Relate( ST_Point() ) should return NULL, but was returning 'FFFFFFFFF'

- ST_SnapToGrid( ST_Point(), x, y, z, m ) should return NULL, but was returning an empty point

This has been fixed.

were being accessed concurrently. This has been fixed.

ST_LineString::ST_LineStringAggr

ST_Geometry::ST_LinearUnHash

ST_Geometry::ST_Transform

new ST_LineString

new ST_CircularString

new ST_CompoundCurve

new ST_Polygon

new ST_CurvePolygon

new ST_GeomCollection

new ST_MultiCurve

new ST_MultiLineString

new ST_MultiPoint

new ST_MultiPolygon

new ST_MultiSurface

These methods have been fixed.

On Mac OS X where the operating system does not provide interfaces to control processor affinity, exact processor topology cannot be determined, so SQL Anywhere treats each logical processor as a separate package or "socket". On multicore and SMT processors, OSX users should purchase the correct license for the hardware they are using, but install a license that will allow the correct amount of concurrency. For example on a quad-core i7 with two threads per core, purchase a license for 1 CPU "socket" but install a license for 8 cpu "sockets" since each processor thread will be treated as a separate CPU socket.

Feature tracking code has also been changed so that the 3-level topology, CPU brand string and CPU info registers (which do not form a unique machine identifier) are reported when crash reports are sent to Sybase.

at idle checkpoint time. The performance of checkpoints has been improved to reduce the length of this interval.

Note that ID 3857 as been defined by authority EPSG to refer to this modified spherical Mercator projection. Before this code was defined by EPSG, some applications used an application-defined code 900913 (*) to represent this SRS. The code 3857 is recommended, but compatibility with older applications can be achieved by manually copying the SRS at id 3857 to id 900913 if necessary.

In addition, comments are no longer automatically defined for spatial reference systems and units of measure that are pre-defined in a newly created database or created using the sa_install_feature(''st_geometry_predefined_srs') or sa_install_feature('st_geometry_predefined_uom').

(*) The code 900913 is selected by these application because of the resemblance between 9 and lowercase g, giving (900913 == google).

http://www.google.com/webhp?hl=xx-hacker&tab=iw

- the on_tsql_error database option was set to 'conditional' or 'stop'

- the continue_after_raiserror database option was set to 'off'

- a RAISERROR statement was executed in a procedure with an exception handler

- the exception handler executed a RESIGNAL statement

then the procedure's caller would not have been able to obtain the error code used in the RAISERROR statement by examining the SQLCODE variable. The SQLCODE value would be -631 (SQLE_RAISERROR_STMT).

2) If:

- the on_tsql_error database option was set to 'conditional' or 'stop'

- the continue_after_raiserror database option was set to 'off'

- a RAISERROR statement was executed in a trigger with an exception handler

- the exception handler executed a RESIGNAL statement

then the error would not have been seen by the statement which caused the trigger to fire.

This has been fixed. In case 1 above, the value of SQLCODE will now be the error code used in the RAISERROR statement. In case 2, the error will now not be suppressed by the trigger.

INSERT INTO directoryTab(file_name, contents) VALUES( 'he''l''lo.txt', 0x0 )

where directoryTab was a directory access table, then the resulting file would incorrectly have been named "he'l'lo.txtxt", instead of the expected name "he'l'lo.txt". This problem has now been fixed.

For example, the following query returned the wrong answer:

select new ST_Point( 1, 2, 3, 4, 504326 )

.ST_SnapToGrid( new ST_Point( 3, 4, 504326 ),

0.1, 0.2, 10, 10 )

Note, a workaround is to add the table to the remote schema by using the Update Schema menu item to update the remote schema.

Here is a list of the files:

(1) .NET 2.0 / 3.0

...\Assembly\V2\iAnywhere.Data.SQLAnywhere.config

...\Assembly\V2\iAnywhere.Data.SQLAnywhere.dll

...\Assembly\V2\iAnywhere.Data.SQLAnywhere.xml

...\Assembly\V2\policy.11.0.iAnywhere.Data.SQLAnywhere.dll

(2) .NET 3.5

...\Assembly\V3.5\iAnywhere.Data.SQLAnywhere.v3.5.config

...\Assembly\V3.5\iAnywhere.Data.SQLAnywhere.v3.5.dll

...\Assembly\V3.5\iAnywhere.Data.SQLAnywhere.v3.5.xml

...\Assembly\V3.5\policy.11.0.iAnywhere.Data.SQLAnywhere.v3.5.dll

(3) .NET 4.0

...\Assembly\V4\iAnywhere.Data.SQLAnywhere.v4.0.config

...\Assembly\V4\iAnywhere.Data.SQLAnywhere.v4.0.dll

...\Assembly\V4\iAnywhere.Data.SQLAnywhere.v4.0.xml

...\Assembly\V4\policy.11.0.iAnywhere.Data.SQLAnywhere.v4.0.dll

...\Assembly\V4\SSDLToSA11.tt

The iAnywhere.Data.SQLAnywhere assembly reference can be added in Visual Studio with the Add Reference dialog. Use the one depending on the .NET project as follows:

iAnywhere.Data.SQLAnywhere for .NET 2 should be used for .NET 2.0 / 3.0 projects

iAnywhere.Data.SQLAnywhere for .NET 3.5 should be used for .NET 3.5 projects

iAnywhere.Data.SQLAnywhere for .NET 4 should be used for .NET 4 projects

SSDLToSA11.tt is used for generating database schema DDL for Entity Data Models. The SQL Anywhere installer copies this file to the Visual Studio 2010 directory. The DDL Generation property should be set to this file when generating database schema DDL for Entity Data Models.

A related change has also been made to the values accepted for the SCREEN_FORMAT option by dbisqlc on UNIX platforms. Prior to this change, dbisqlc accepted both "TEXT" (for the default columnar display) and "ASCII" (for comma-separated values). These options have been renamed to COLUMNS and CSV respectively. The old values of TEXT and ASCII are still accepted but are deprecated.

There are a number of workarounds:

- Minimize and then restore the dbisql window, or

- Resize the window, or

- Turn off the fast launcher for dbisql

BIGINT

BIT

DECIMAL

DOUBLE

FLOAT

INTEGER

NUMERIC

REAL

SMALLINT

TINYINT

1) Processing of the batch stops immediately upon encountering a SQL exception or result set. If processing of the batch stops, then a BatchUpdateException will be thrown by Statement.executeBatch(). Calling getUpdateCounts() on the BatchUpdateException will return an integer array of row counts where the set of counts prior to the batch failure will contain a valid non-negative update count; while all counts at the point of the batch failure and beyond will contain a -1. Casting the BatchUpdateCount to a SQLException will provide additional details as to why batch processing was stopped.

2) The batch is only cleared when Statement.clearBatch() is explicitly called. As a result, calling Statement.executeBatch() repeatedly will re-execute the batch over and over again. In addition, calling Statement.execute( sql ) or Statement.executeQuery( sql ) will correctly execute the statement with the "sql" argument, but will not clear the underlying batch. Hence, calling Statement.executeBatch() followed by Statement.execute( sql ) followed by Statement.executeBatch() will execute the set of batched statements, then execute "sql" and then execute the set of batched statements again.

whether a delete is pending.

Note, this same problem has the potential to affect Sybase Central, DBConsole, and MobiLink Monitor, though their symptoms are likely to be different.

Note that a workaround for this problem is to increase the amount of memory that is available to the server.

Also, the line and column shown in the status bar of the main DBISQL window is no longer updated if the caret (insertion point) is moved in the text field that shows the SQL in the "ISQL Error" window.

For example, consider the following code:

/*

Lorem ipsum

*/

select 123;

If the caret is anywhere within the comment, or on the blank line before the SELECT statement, pressing SHIFT+F9 now executes the SELECT statement. Previously, an error message saying the caret was not on a statement would have been displayed.

Note, this problem does not occur with the 32-bit versions of the MobiLink server.

A workaround is to restart both servers and perform another BACKUP/RENAME.

For example:

conn = DatabaseManager.createDatabase( config );

conn.release();

This has now been fixed.

Note, that you the OLD values for rows that have been updated were not visible; the INSERT derived table only supports the FINAL correlation. To see both the OLD and FINAL row values, use the MERGE statement instead of the INSERT statement.

"Reader Exception: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

This has been fixed.

Example:

In the following query, both expr1 and expr2 should return true (the docs state that they are equivalent).

select ST_Geometry::ST_GeomFromWKT('Polygon ((1 1, 3 1, 3 3, 1 3, 1 1))', 0) rect1

, new ST_Point( 0, 2, 0 ) p1

, new ST_Point( 2, 0, 0 ) p2

, new ST_Polygon( p1, p2 ) rect2

, rect1.ST_Intersects( rect2 ) expr1

, rect1.ST_IntersectsRect( p1, p2 ) expr2

;

Result:

rect1,p1,p2,rect2,expr1,expr2

Polygon ((1 1, 3 1, 3 3, 1 3, 1 1)),Point (0 2),Point (2 0),Polygon ((0 0, 2 0, 2 2, 0 2, 0 0)),true,false

This has been fixed.

If the setting for SQL_ATTR_METADATA_ID is SQL_TRUE, the string argument of catalog functions are treated as identifiers. The case is not significant. For nondelimited strings, the driver removes any trailing spaces and the string is folded to uppercase. For delimited strings, the driver removes any leading or trailing spaces and takes literally whatever is between the delimiters.

If the setting is SQL_FALSE, the string arguments of catalog functions are not treated as identifiers. The case is significant. They can either contain a string search pattern or not, depending on the argument. The default value is SQL_FALSE.

The following example changes the default setting for the entire connection.

rc = SQLSetConnectAttr( hdbc, SQL_ATTR_METADATA_ID, (SQLPOINTER)SQL_TRUE, SQL_IS_UINTEGER );

This setting is important for case-sensitive databases. For example, the table name "customers" does not match the table name "Customers" in a function such as SQLPrimaryKeys() unless the SQL_ATTR_METADATA_ID attribute has been set to SQL_TRUE.

geom1.ST_xxx( geom2 ) <> 1

geom1.ST_xxx( geom2 ) = 0

geom1.ST_xxx( geom2 ) = ( subquery )

geom1.ST_xxx( geom2 ) = geom3.ST_yyy( geom4 )

where ST_xxx and ST_yyy could be any of the following spatial predicates:

ST_Intersects

ST_IntersectsFilter

ST_IntersectsRect

ST_Overlaps

ST_Contains

ST_ContainsFilter

ST_Within

ST_WithinFilter

ST_Covers

ST_CoversFilter

ST_CoveredBy

ST_CoveredByFilter

ST_Equals

ST_EqualsFilter

ST_OrderingEquals

This has now been fixed.

SQL_ATTR_METADATA_ID

SQL_ATTR_ROW_NUMBER

SQL_ATTR_ROW_ARRAY_SIZE

SQL_ATTR_PARAMSET_SIZE

SQL_ATTR_MAX_LENGTH

SQL_ATTR_MAX_ROWS

The driver was using SQLUINTEGER for these statement attributes. It has been corrected to now use SQLULEN.

would have prevented the list of database properties from refreshing. This has been fixed.

One context was correlated subqueries. The semantics of a correlated DML statement are poorly defined and hard to implement. The following query is not allowed:

select * from (insert into newids select outerproduct.id) referencing (final as insertedids), product as outerproduct

The other context was common table expressions, again because the semantics are unclear.

A workaround is to uncheck the 揅ommit after every statement� option.

For example, the error message for the following query could incorrectly report:

"A geometry with SRID= is not supported for method 4326."

select new st_point(0, 0, 4326) p

from sys.dummy

where p.ST_Envelope().st_intersectsfilter(p) = 1

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

"A geometry with SRID=4326 is not supported for method ST_Envelope()."

Error -20 during transformation.

For example, if the geometry contained points close to the poles of the Earth, this error could have been returned. This error could also have been returned when viewing a geometry in the spatial viewer.

The Mercator projection (and other cylindrical projections) can not transform polar points because the y coordinate would need to be infinite (cylindrical projections treat the Earth as a rubber balloon in a glass cylinder and inflate the balloon; the projection is taken from the sides of the glass cylinder, and the polar points never touch the sides).

This has been fixed; when transforming a geometry from a lat/long system to a Cartesian system, if a point close to the North or South pole fails to transform the server moves the latitude of the point a small distance away from the pole along the same longitude. The distance moved is slightly more than (1e-10 radians). This shifting is used only if the point fails to transform without shifting.

Invalid Date-time segment. Year value out of range

and aborted any synchronization requests, if the consolidated database was running on an ASE server with a database that was using a multi-byte charset, and the MobiLink server was running on a Windows system that was using a non-English Date format. This problem has now been fixed.

The first case occurred if a sync request was made while another synchronization was already taking place. It was expected that another sync will begin once the current one has finished, but this did not always happen.

The second case occurred if a sync request was made while using a Transactional Manager. It was expected that only sync requests resulting from changes to the database will be delayed until the transaction is committed. However, this delay was occurring for other types of sync requests as well.

These two cases have now been fixed.

Note that this problem also affects Sybase Central.

Note, this problem also affected the Interactive SQL utility, Sybase Central, and the SQL Anywhere Console utility.

Note, if the Data Flow consists of more than 10 tables that are to be migrated to SQL Server from a SQL Anywhere server, the Personal server should not be used since each table is moved asynchronously on a separate connection (i.e., more than 10 simultaneous connections will be made to the SQL Anywhere server and the number of simultaneous connections is limited with the Personal server).

then an incorrect column name could have been reported in the error message. This only happened if there was another ADD, ALTER or DROP column clause in the statement. This has been fixed.

Note that this fix is only for the SQL Anywhere JDBC driver. The iAnywhere JDBC driver will continue to return a ResultSet based on ODBC sorting standards.

Menu Item New Accelerator

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

SQL/History Ctrl+Command+H

SQL/Previous SQL Ctrl+Command+LeftArrow

SQL/Next SQL Ctrl+Command+RightArrow

The following accelerators for buttons on the Spatial Viewer have been changed for OS X only:

Button New Accelerator

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

History Ctrl+Command+H

Previous SQL Ctrl+Command+LeftArrow

Next SQL Ctrl+Command+RightArrow

Save Image Command+S

Hide SQL Shift+Command+H

Zoom In Command+Plus

Zoom Out Command+Minus

Reset View Command+R

Draw Outlined Polygons Command+P

The tooltips for the above buttons now display the correct key name as well. Previouly, the tooltip displayed the Windows/Linux/Solaris accelerator key name instead of the Mac one.

Importing a table from ASE which had TIMESTAMP columns into a new table would have failed. The ASE TIMESTAMP type was being misinterpreted as being equivalent to the SQL Anywhere TIMESTAMP type, which is false.

Exporting data from SQL Anywhere into ASE would have reported various conversion issues for SQL Anywhere DECIMAL values.

Also, clicking the close button (the "X" in the toolbar) aborted the entire process of creating the DSN; now, clicking the close button is the same as clicking the "No" button, which leaves the "Saves as ODBC Data Source" window open.

Note: Engineering case 626480 included new versions of the Certicom and OpenSSL libraries. This problem only affects Mac OS X clients with these new libraries connecting to servers on a different operating system also with these new libraries.

Note, this fix also affects the "Data" tab for tables and views in Sybase Central.

Note that in addition to supporting the ASADataSource class, the SQL Anywhere and iAnywhere JDBC drivers now offer an SADataSource class as well.

In a related issue, if the Remote Schema Name cannot be deleted because there are agents still managing databases with that Remote Schema Name, an error message is now shown explaining that condition as plainly as possible. Previously, the underlying error message from the consolidated database was displayed, which was not helpful.

create or replace spatial reference system "WGS84_orig"

identified by 50000

type round earth

storage format 'oRiginal'

This has been corrected so that the case is normalized.

For the complete fix to this problem, use the Upgrade utility (dbupgrad) to upgrade existing databases with fixes for the OLE DB schema rowset support (metadata support).

For example, the following query was permitted while it should be rejected:

select count(*), geometry.ST_Envelope()

from ( select row_num, new ST_Point( row_num, row_num, 0 ) geometry from rowgenerator ) D

This has been fixed.

"Got unexpected data when receiving authentication result. Check version of MobiLink server (opcode=0)"

This has been fixed to provide more information on the problem. The most common authentication error is now:

"Invalid userid or password (auth_status=NNNN)"

Other errors, for example due to an expired password, are similar.

SELECT * FROM customers C

WHERE C.

it should have suggested the columns in the "Customers" table, but it did not. This has been fix so that now it does.

select geometry

from table_containing_ST_Curves

where geometry.ST_IntersectsRect( new ST_Point( 0, 0 ), new ST_Point( 10, 10 ) ) = 1;

Also, the server could have crashed while executing a plan with an outer join if the null-supplying side contained an IN-list with either NUMERIC or string values.

These problems have now been fixed.

- user-defined function

- argn

- http_header

- http_response_header

- http_variable

- isdate

- isnumeric

- next_connection

- next_database

- next_http_header

- next_http_response_header

- next_http_variable

- next_soap_header

- patindex

- soap_header

- stuff

For example, the following queries would have incorrectly returned a non-NULL value for the column "b" of the derived table "D":

select *

from rowgenerator left join ( select dummy_col , argn( 1, 137, dummy_col ) b from sys.dummy ) D on 1=0

where row_num=1

select *

from rowgenerator left join ( select dummy_col , isnumeric( dummy_col ) b from sys.dummy ) D on 1=0

where row_num=1

This has been fixed.

Note that this problem does not exist for external environment other than Java.

foreign key on a table, if the creation of the first foreign key on the table had automatically added a new column to the foreign table. This has been fixed.

SELECT * FROM sys.sys

This problem would have affected text completion in SELECT, DELETE, and UPDATE statements and has now been fixed.

For 12.0.0, ECC curve support for end-to-end encryption, the createcert and createkey utilities, and for the TLS protocol for both MobiLink and SA, has been extended to support the 15 curves recommended by NIST:

sect163k1 sect283k1 sect571k1 secp256r1

sect163r2 sect283r1 sect571r1 secp384r1

sect233k1 sect409k1 secp192r1 secp521r1

sect233r1 sect409r1 secp224r1

PreparedStatement.setClob( int parameterIndex, Clob x ), and

PreparedStatement.setClob( int parameterIndex, Reader reader, long length )

However, support for the method:

PreparedStatement.setClob( int parameterIndex, Reader reader )

is still not available in the SQL Anywhere JDBC driver.

It should be noted that when using the PreparedStatement.setClob( int parameterIndex, Clob x ) overload, the user supplied Clob implementation only needs to support the Clob.length() and Clob.getCharacterStream() methods. Also, for large strings and large character streams, the new PreparedStatement.setClob() methods within the SQL Anywhere JDBC driver are preferable over the PreparedStatement.setString() and PreparedStatement.setCharacterStream() methods in terms of both performance and memory usage.

A work-around is to set the optimization goal to 'All-rows' before validation.

This problem was more readily seen on Linux systems than on Windows.

This has been fixed.

Note, this problem was extremely rare in builds prior to the changes made for Engineering case 625189, it would have been slightly more likely in later builds, due to increased frequency of cleaner invocation.

server was shutting down after failing to start. This has been fixed.

Error: Cannot open data file �<mangled characters>� for table T

This has now been fixed. A workaround is to store BLOB/CLOB data in the current directory.

"Error canceling message. Cannot cancel a message that has already been downloaded to its recipient or is in a final state." This message has now been localized.

Note, this problem also affected the Interactive SQL and Console utilities, as well as the MobiLink Monitor.

1. the number of cached pages for an index was not saved for the graphical plans

2. complex expressions used in the WHERE clause may have produced different errors than the optimizer

3. predicate selectivities were not normalized, this was a different behaviour than the optimizer

1. (All) The Help menu items related to checking for updates are removed

2. (Interactive SQL utility) In the "Options" window, the "Update Checker" tab is removed for SQL Anywhere and UltraLite.

The following syntax is used to create a text index on an an immediate or a manual materialized view:

CREATE TEXT INDEX [ IF NOT EXISTS ] text-index-name

ON [ owner.]imv-name( column-name, ... )

[ IN dbspace-name ]

[ CONFIGURATION [ owner.]text-configuration-name ]

[ IMMEDIATE REFRESH ]

Once a text index on a materialized view is created, it cannot be refreshed or truncated. The only

operation a user can perform on the text index is DROP. The text index on a materialized view will

be maintained by the server whenever the underlying materialized view is refreshed or updated.

If the materialized view is altered - for example, immediate materialized view is converted to manual -

the text index changes accordingly.

This affects the following parts of the UI:

1. The "Product" column on the "Consolidated Databases" tab

2. The property sheet for a consolidated database

3. The "Display Name and Description" page of the Add Consolidated Database Wizard

4. The "Consolidated Database Schema" page of the Create Synchronization Model Wizard

5. The "Consolidated Database Deployment Destination" page in the Deploy Synchronization Model Wizard

6. The "Consolidated Database Schema" page of the Update Schema Wizard

"Stream Error: Mismatched end-to-end encryption keys"

when establishing an end to end encryption link with Ultralite on the iphone. This has been fixed.

1. the procedure contains a single statement having common table expressions (CTEs) defined using WITH [RECURSIVE] clause.

2. the procedure parameters are used inside the CTEs in any expression (e.g., WHERE predicate, select list item, etc.)

3. the procedure parameters are outerreferences in the FROM clause

This has been fixed. The workaround is to add an extra statement inside the procedure to make it not a candidate for inlining (e.g., " if 1 = 0 then return end if;")

CREATE PROCEDURE CRASH ( @databaseid INTEGER, @tableid INTEGER, @rowid BIGINT )

WITH RECURSIVE SIMPLE

( databaseid, tableid, rowid, mtableid, mrowid, stableid, srowid ) AS

(

SELECT databaseid, tableid, rowid, stableid, srowid, stableid, srowid

FROM ATABLE

WHERE databaseid = @databaseid AND stableid = @tableid AND srowid = @rowid

UNION ALL

...

SELECT databaseid, changeno, rowchangeno

FROM T rc

WHERE EXISTS (SELECT * FROM CRASH( rc.databaseid, rc.tableid, rc.rowid ) )

A workaround is to avoid capturing the PLANS_WITH_STATISTICS level.

The parameters for this switch are as follows:

-t <Encryption Certificate> <Certificate Password>

Where <Encryption Certificate> is the fully-qualified path to an encryption certificate and <Certificate Password> is the password for the certificate.

For example:

C:\> samonitor.exe -d C:\path\to\db\samonitor.db -t C:\path\to\cert\cert.cer myPassword

Note that this switch is not supported with the Production (i.e. Standalone) Edition of the Monitor.

1. Dropping at the end of the list did nothing. Now the dragged item is moved to the end of the list.

2. Dropping an item to a location farther down the list would move it one higher than the indicated drop location. Now items are dropped where indicated.

Note, this issue is similar to Engineering case 586837, but only affects version 12.0.

1. Incorrect machine.config file.

2. SA ADO.NET provider assemblies were not added to GAC.

3. SA ADO.NET provider assemblies did not show up in Visual Studio Add Reference dialogbox.

4. Visual Studio failed to create DataSets or Entity Framework Models using SA data sources.

Re-installation of SQL Anywhere was usually required to fix these problems. Now all Visual Studio integration related code has been implemented in SetupVSPackage.exe, and any Visual Studio integration problem should be fixed by running SetupVSPackage. It will perform the following tasks:

1. Add / Remove assemblies of SA ADO.NET provider and integration package to / from GAC.

2. Register or unregister SA ADO.NET provider in machine.config.

3. Create registry keys for SA integration package

4. Create registry keys for Visual Studio Add Reference dialogbox.

5. Copy / Remove SSDLToSA12.tt to / from Visual Studio 2010 folder (%VS_DIR%\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\DBGen).

6. Register or unregister SA ADO.NET provider in %SQL Server 2008 DIR%\100\DTS\ProviderDescriptors\ProviderDescriptors.xml which is used by SQL Server Integration Service.

7. Setup Visual Studio IDE for SA integration package.

SetupVSPackage.exe is executed by the SQL Anywhere installer when installing or uninstalling SQL Anywhere, but SetupVSPackage.exe can be run separately. Two versions of SetupVSPackage.exe will be installed:

1. %SQLANY%\Assembly\V4\SetupVSPackage.exe - This version is built using .NET Framework 4, this version should be used if .NET Framework 4 is installed.

2. %SQLANY%\Assembly\V2\SetupVSPackage.exe - This version is built using .NET Framework 2, this version should be used if .NET Framework 4 is not installed.

A performance issue when running SetupVSPackage.exe for Visual Studio 2008 and 2010 has also been fixed.

Also, the code which was supposed to populate the "Relay Server URL suffix" field with whatever value was used previously was incorrect, and has been fixed.

A workaround is to use the menu item or F3 key to open the 'Find/Replace' window.

1. Click the column header to sort by that column

2. Click "Yes" when asked to fetch the remaining rows

3. Cancel fetching the rows

4. Click a different column header to sort by some other column

This has now been fixed.

1. Click the column header to sort by that column

2. click "Yes" (or press Enter) when asked to fetch the remaining rows

3. Immediately press the F5 key.

The crash will occur once the entire result set had been read. This has now been fixed.

Note, it is recommended that the database server not be servicing other connections while database validation is taking place.

-kp dbengX/dbsrvX server option:

Specifies the Kerberos server principal and enable Kerberos authenticated connections to the database server.

Syntax:

-kp server-principal

Applies to:

all OSes except Windows Mobile

Remarks:

This option specifies the Kerberos server principal used by the database server. Normally, the principal used by the database server for Kerberos authentication is server-name@default-realm, where default-realm is the default realm configured for the Kerberos client. Use this option if you want to use a different server principal, such as the more standard format server-name/hostname@myrealm. If OpenClient or jConnect Kerberos authenticated connections are made to the server, the server principal must be specified by the application (see SERVICE_PRINCIPAL_NAME for jConnect).

The -kr option cannot be specified if the -kp option is specified.

Specifying this option enables Kerberos authentication to the database server.

See also:

<same list as -kr option documents, with the addition of the -kr option>

Example:

The following command starts a database server that accepts Kerberos logins and uses the principal myserver/mymachine.sybase.com@SYBASE.COM for authentication.

dbeng12 -kp myserver/mymachine.domain.com@MYREALM -n myserver C:\kerberos.db

For the most reliable synchronization, a device should be paired with a BES (BlackBerry Enterprise Server) or the application should use BIS communication (application provider can join RIM partner program for free and then apply to use the BIS protocol).

the new behaviour as per the documentation.

This general problem affected a number of other aspects of dbisql behavior, and have also been corected:

1. The "Lookup Table Name" window, the "Lookup Procedure Name" window, and the text completer made case-sensitive searches for matching object names if connected to a case-sensitive SQL Anwyhere database.

2. The INPUT USING statement would have failed if the table name in the FROM clause did not match the exact case of an existing table in the case-sensitive database from which data was being imported.

3. In the Query Editor, the list of available columns did not show any columns unless the table name matched the case of the database table name (affects: "Columns", "GROUP BY", and "ORDER BY" tabs; "Expression Editor" window). Also, the "Table pattern" field on the "Tables" tab was applied in a case-sensitive way.

fixed.

EXEC owner.procedure_name :parm1, :parm2, ...

where :parm1, etc. are bound parameters.

The SQL Anywhere OLE DB provider has been improved to now handle this syntax.

1) SELECT {table columns} FROM {table} WHERE {primary key col1 = val1, primary key col2 = val2, ... }

2) UPDATE {table} SET ... WHERE {primary key col1 = val1, primary key col2 = val2, ... }

3) DELETE FROM {table} SET ... WHERE {primary key col1 = val1, primary key col2 = val2, ... }

This has been fixed. As a work-around, the statements can be change to include "OPTIONS( FORCE OPTIMIZATION )", or the server can be started with the following command line switch: "-hW AllowSimpleUserCache".

msiexec /i sqlany11.msi SQLANYDIR="{path to install directory}\xxx xxxxxxxx xx"

the install could have failed. This has been fixed.

-ap ""

This problem has been fixed.

Note, a workaround is to specify the parameter using a single comma. For example -ap , This passes a single empty authentication parameter but does not cause the "out of memory" error.

The following is an example output after the fix.

<Main> [-10133] java.lang.Exception: Notifier(Simple).request_cursor: Failed to prepare request cursor

<Main> [-10133] at ianywhere.ml.notifier.Notifier.connectDB(Notifier.java:390)

<Main> [-10133] at ianywhere.ml.notifier.Scheduler.connectDB(Scheduler.java:360)

<Main> [-10133] at ianywhere.ml.notifier.Scheduler.run(Scheduler.java:428)

<Main> [-10133] at java.lang.Thread.run(Thread.java:619)

<Main> [-10133] Caused by: java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Column 'bogus_content' not found

<Main> [-10133] at ianywhere.ml.jdbcodbc.IConnection.nativePrepareStatement(Native Method)

<Main> [-10133] at ianywhere.ml.jdbcodbc.IConnection.prepareStatement(IConnection.java:554)

<Main> [-10133] at ianywhere.ml.notifier.Notifier.connectDB(Notifier.java:388)

<Main> [-10133] ... 3 more

<Main> <SISI><Scheduler(0:1)>: Shutdown

<Main> <SISI><Scheduler(0:1)>: Disconnected from database

For example, the following statement is accepted by version 9.0, but rejected by version 10.0 and above:

select convert( time, '11:45am', 14 ) tm_conv

The behavour of converting from strings to TIME changed from version 9.0 of SQL Anywhere to version 10.0 and later, with version 10.0 and later applying the same rules that conversions from string to timestamp used. The string '11:45am' does not precisely match the format style 14 (hh:nn:ss:sss) because it contains an "am" indicator that is not present in the style.

Parsing of formatted time strings has been enhanced so that the time portion of a string is accepted provided that it matches the format [hh:nn:ss.ssssssAA]. The time string must specify the hour digits, but all other time parts are optional. The AM/PM indicator is always accepted whether or not time parts are omitted. Note that this now permits up to six digits to represent microseconds after the seconds. This change affects the conversion of string to TIME and also to TIMESTAMP, so there is a consistent parsing. The following is rejected after this change, even though it was accepted in 9.0:

select convert( time, '1991-02-03 11:45', 101 )

The string does not match the style format 101 (mm/dd/yyyy).

Further, in some cases it was possible to generate invalid timestamps with string conversions. This has also been fixed.

read-only in the Download Delete Subset tab when the download delete subset option is "Same" and the download subset option is "Custom".

A workaround is to temporarily disable auditing on the main database, create the tracing database, and then re-enable it.

For example:

select n_comment from nation group by cube (n_comment) HAVING n_comment like 'alw%';

The result set would have contained all the rows with n_comment for which the predicate "n_comment LIKE 'alw%' is TRUE, but also the row "(NULL)". This has now been fixed.

As a work around, the reload.sql file can be edited to double the embedded quotes and escape other characters requiring escaping in these statements.

A partial workaround is to decrease the frequency of checkpoints; the hang is most likely to occur during a checkpoint. Of course, decreasing the checkpoint frequency will increase recovery time.

- results from a user-defined function with numeric Expression Caching (any data type)

- a LIKE predicate

- a CAST of a string to an approximate number (REAL, DOUBLE, or FLOAT)

- the SORTKEY or COMPARE builtin function

- the REMAINDER or MOD builtin functions with arguments of type NUMERIC or DECIMAL

- the MEDIAN aggregate function

- a spatial data type

If the memory usage exceeded what was allowed for one connection, the statement would have failed with a dynamic memory exhausted error. This has been fixed.

Permission denied: you do not have permission to execute the procedure "sajvm_JavaWorker"

would have been reported in the server console. This problem has now been fixed.

Interactive SQL reaches 100% CPU when larger sql files are opened and scrolled. Depending on the machine processor (Pentium IV or older Pentium D), the performance gets very bad, or, according to customer's test, DBISQL can even hang.

- incorrectly prompt that there were active connections when shutting down the server

- incorrectly determine if an unconditional dbstop or STOP SERVER was required

- incorrectly enforce the -gm connection limit

This has been fixed.

could have recorded the length of the document before prefiltering as the final length. This could have caused the scores reported by the CONTAINS queries to differ (in most cases be lower) than expected. The problem did not affect the text indexes built using no external libraries.

For example: If the following two values (documents)

'<html><body>A <b>very</b> nice day...</body></html>'

'<html><body>Peace and quiet at home</body></html>'

were indexed using a tag-removing prefilter, the lengths of the actual text were not equal, but the lengths recorded by the index would have included the lengths of the tags, making the document lengths equal. This has now been fixed.

Note, this problem would also have affected the "Data" tabs in Sybase Central.

1) the C data type of the parameter was SQL_C_WCHAR or SQL_C_CHAR

2) the type of parameter was SQL_PARAM_INPUT_OUTPUT, but the corresponding parameter used in the SQL statement was input-only

Due to this problem, the data for the user-defined named parameters in the MobiLink server may have been truncated after each use when the named parameter was defined as {ml u.varname} and the parameter used in the SQL statement was input-only. This has now been fixed.

Also, unloading a version 10 or later database containing a table with a primary key index that had been renamed would have failed to preserve the new name for the index. This has been fixed.

SELECT * FROM openquery(SALINK, 'exec test_proc 1')

This problem has been fixed. When parameters are present in the SQL query, the statement is passed unchanged to the server. When no parameters are present, the OLE DB provider rewrites the "exec" statement using CALL and appends parameter marker place holders (in order to support ADO's ADODB.CommandTypeEnum.adCmdStoredProc).

- MSSqlToSA.xml --- mapping SQL Server 2008 data types to SA data types.

- SAToMSSql10.xml --- mapping SA data types to SQL Server 2008 data types.

These files will be installed to "%SA%\Assembly\V2" folders. The utility SetupVSPackage.exe will copy them to, or remove them from, the "%SQL Server 2008 Dir%\DTS\Binn" folder.

- The "Check for Software Updates" menu item was missing

- The text for submenus were indented more than was required

- There were a number of spurious separators at the end of certain menus.

1) Change the target Framework of the VS project.

When creating a new project, there is a drop down above the list of project types that contains ".NET Framework 4"; change this to ".NET Framework 2.0", ".NET Framework 3.0", or ".NET Framework 3.5".  If a version 4 project has already been created, change the target framework by right-clicking on the project in the Solution Explorer, and selecting "Properties" in the context menu.  The target framework can be set on the "Application" tab.燱hen changing the target framework, there is no longer access to .NET 4.0 features; to use newer features, use the next workaround.

2) Tell the MobiLink server to load the version 4 framework.

To do this, add -clrVersion=v4.0.30319 to the -sl dnet options.  The "30319" is the specific build number of the framework installed and may be different on your machine.  To find the correct version, look in the .NET install location, which is typically "c:\WINDOWS\Microsoft.NET\Framework\".  The clrVersion to specify is the v4.0 sub-directory there.

A workaround is to manually revoke any sequence permissions granted by the user about to be dropped, then re-grant them from a user that will not be dropped. The original grantor can then be dropped.

Also, the MobiLink server was not able to distinguish between empty strings in varchar(8) or smaller columns, binary(16) or smaller values made of only 0s, the integer 0, and null values when filtering the download. This could have caused rows to be incorrectly filtered from the download. For example, if an empty string was uploaded in a row, and the only difference between a downloaded row and that uploaded row was that the empty string became null, the row would have been ommitted from the download and the remote would not have received that update.

These issues have been fixed.

Note that the logging options are presented as if they are separate, independent options, even though there are underlying dependencies between some of the them. For example, logging triggers also logs procedures and SQL. This is a server behavior rather than a Console utility behavior.

A workaround is to adjust the value over which the variance function is computed so that a tiny amount of variance is introduced. For example, instead of:

SELECT VARIANCE(mycolumn) FROM mytable

use:

SELECT VARIANCE(mycolumn + 0.00000001*myprimarykey) FROM mytable

select Comp from customers C1, customers C2

the completer will include "Company (C1 - customers)" and "Company (C2 - customers)". If the second item is selected, the completed text will read:

select C2.CompanyName from customers C1, customers C2

Previously, "Comp" would be replaced by "CompanyName", which was ambiguous.

"Error: Database cannot be started -- /mnt/share/demo.db is not a database"

This has now been fixed.

- the UltraLite engine (uleng12) was started from one directory and dbisql was launched from another

- the -c option to dbisqlL specified a relative path

The result would have been that dbisql would have displayed the connection dialog, when it should have immediately connected to the database. This has been fixed.

2. The documentation states that only the first 128 characters of each parameter are sent to the MobiLink server, but no limit was actually enforced. This resulted in corrupt data being sent to the MobiLink server if a value was excessively large. This has been fixed. Extremely large strings (greater than 21K characters) are now truncated prior to sending to the MobiLink server, and the MobiLink server will however report an error now if the authentication parameters' lengths exceed the server's limit of 128 bytes.

To fix such tables in existing databases the table needs to get recreated or a database upgrade needs to be run.

"Assertion failed: 201117 Attempt to close a file marked as dirty".

This has now been corrected.

To patch a MobiLink system setup

1. Shut down ML servers

2. execute the sql in %SQLANY12%\MobiLink\Setup\syncmss_ebf.sql

The patch only updates stored procedures, no data will be disturbed by this script. If the MobiLink system setup was installed using 12.0.0.2566 or later then this patch does not need to be applied.

CREATE TABLE Test ( c INT PRIMARY KEY );

DESCRIBE INDEX FOR TABLE test;

This has been fixed.

For example:

SetupVSPackage.exe /i --- not install SQL Anywhere Explorer and SQL Anywhere Toolbar

SetupVSPackage.exe /i /sae --- install SQL Anywhere Explorer and SQL Anywhere Toolbar

Note, this new option only applies to Visual Studio 2005 and 2008. SQL Anywhere Explorer and SQL Anywhere Toolbar are still disabled for Visual Studio 2010. The SetupVSPackage.exe utility always install or uninstalls both the SQL Anywhere Explorer and SQL Anywhere Toolbar together. The '/sae' option only applies to '/i', use of the '/u' option always removes everything.

Database with this problem will need to have the affected geometries re-inserted after applying this fix.

This change also fixes the interpretation of parameters to the ST_Polygon( ST_Point, ST_Point ) constructor. Previously, if the parameter points were close to the International Date Line, an invalid polygon (with edges longer than 180 degrees) could have been constructed. This has been fixed.

For example, consider: ST_Polygon( new ST_Point( 170, 10, 4326 ), new ST_Point( -170, 20, 4326 ) ). Now, this will be interpreted as equivalent to: new ST_Polygon( 'Polygon((170 10, -170 10, -170 20, 170 20, 170 10))', 4326 ) which is a polygon crossing the date line.

In general, the constructor will choose the interpretation that generates the polygon that fits into a single hemisphere.

In addition, a new connection parameter has been added to ODBC which allows a specific string to be defined that is returned in the SQLTables() result set for materialized views. This new connection parameter is called MATVIEW, and is a string that will be returned in the TABLE_TYPE column for materialized views.

For example, to have the SQLTables() function return materialized views as type TABLE, connect as follows:

uid=dba;pwd=sql;eng=...;matview=table

This new option can be used to override this default and return to the previous behaviour. The same string is also used when SQLTables() is called with an explicit TableType filter.

For example:

dbping -d -c "start=dbeng10;eng=server_name"

would have returned an error, but leave a server named server_name running. This has been fixed so that the autostarted server is now stopped if the connection fails.

when the server was running on Windows 7, Windows 2008, or Windows 2008 R2. This has been fixed.

Long types are now mapped to SQL Anywhere long types. For example, an adLongVarChar column is now mapped to "LONG VARCHAR" instead of "CHAR(0)".

Wide types are now mapped to SQL Anywhere nchar types instead of char types. For example, adWChar is now mapped to "NCHAR" and adLongVarWChar is now mapped to "LONG NVARCHAR".

An adSingle column with no specifed precision will now default to REAL rather than FLOAT(0), which generated a syntax error.

An adDecimal column with no specified precision and scale will now default to DECIMAL rather than DECIMAL(0,0), which generated a syntax error.

An adNumeric column with no specified precision and scale will now default to NUMERIC rather than NUMERIC(0,0), which generated a syntax error.

An adLongVarBinary column will map to the IMAGE type rather than BINARY(0), which generated a syntax error.

An adCurrency column is now supported and will map to a column of type MONEY.

An adDate column is now supported and will map to a column of type DATETIME.

If a table or column name is not defined, OLEDB will no longer fault with a NULL pointer reference. Instead, the name "undefined" will be used.

The following code fragment is a VBScript example for creating a table using ADOX statements.

Set db = CreateObject( "ADOX.Catalog" )

Set ntable = CreateObject( "ADOX.Table" )

ntable.Name = "testTable"

ntable.Columns.Append "Col_1", adNumeric

ntable.Columns.Append "Col_2", adDate

ntable.Columns.Append "Col_3", adChar, 32

ntable.Columns.Append "Col_4", adVarChar, 32767

ntable.Columns.Append "Col_5", adLongVarChar

ntable.Columns.Append "Col_6", adLongVarWChar

db.Tables.Append ntable

create or replace function foo() returns int begin return 1; end;

call foo();

create or replace procedure foo() begin select 2; end;

call foo();

This has been fixed so that if client statement caching is disabled by setting the max_client_statement_cached option to 0 for the connection, such a statement is now described correctly.

Note that the documentation is correct.

This change also includes the following enhancements:

- When a listener terminates, it now always writes a console message identifying the protocol and the network address, ie. HTTPS, {::}:443

- An IgnoreCodes protocol option has been added to HTTP and HTTPS protocols

A time specified as hours followed by the AM/PM designator could not have been converted to a timestamp. For example:

select cast( '11am' as time );

The work-around is to include minutes:

select cast( '11:00am' as time );

A time that included microseconds, but did not include seconds could not have been converted to a timestamp. For example:

select cast('00:00:.930' as time)

The work-around is to include seconds:

select cast('00:00:00.930' as time)

These problems have been fixed.

The information displayed in the Topology Widget is as follows:

Server Name - The name of the node given when creating the scale-out system. See "CREATE MIRROR SERVER statement" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/create-mirror-server-statement.html*d5e37248

Type - The node type defined when creating the scale-out system. See "CREATE MIRROR SERVER statement" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/create-mirror-server-statement.html*d5e37248

State - The connection status of the node. Can be one of "connected" or "disconnected". See "sa_mirror_server_status system procedure" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/sa-mirror-server-status-sysproc.html*d5e70531

Connections - The current number of connections to this node. See "sa_mirror_server_status system procedure" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/sa-mirror-server-status-sysproc.html*d5e70531

Last Updated - The time the server information was last updated. See "sa_mirror_server_status system procedure" in the docs http://dcx.sybase.com/index.html#1200en/dbreference/sa-mirror-server-status-sysproc.html*d5e70531. Note that this value is not necessarily the same as the last time the Monitor fetched topology information for this scale-out system.

1) Validation was being done online.

2) The table contained blobs.

3) Table blobs were being heavily modified by other concurrent requests.

4) The right timing happened between the validation process and the blob update

process.

This has been fixed.

A workaround is to issue deletes over a non-transactional temporary table multiple times.

1. The text completer now opens automatically when typing. This can be turned off from the Options window by clearing the "Open automatically" box on the "Text Completion" page.

2. SQL statements and keywords are now included in the list of suggestions.

3. The completer now correctly handles databases where strings are treated as case-sensitive but identifiers are not.

4. Performance has been improved.

5. The keyboard accelerators for use when the completion list is open have changed:

Old Accelerator New Accelerator Function

Tab Ctrl+A Show a context-free list of matches

+ Ctrl+Plus Add the item with its parameter list

* Ctrl+Asterisk Add the item with its parameter and type list

" Ctrl+Apostrophe Add the item enclosed in quotation marks

6. In addition to the Enter key, pressing the Tab key while the completer list is open accepts the selected item and closes the completer.

7. Columns from internal text tables are no longer shown.

8. Completed database object names, which are also SQL keywords, are automatically quoted.

9. If a function key is pressed, or if the menu bar is used while the completer is open, the selected completion item is added, the completer is closed, and then the function key (if any) is processed.

10. The "Text Compeleter" tab in the Options window has been clarified. Options to control whether tables, views, stored procedures, and SQL functions have been removed; the SQL parsing in good enough to guide the selection of the suggested items.

For example:

create index idx on T(X);

select max(T.X) from T;

Also, the OLE DB provider's TABLES schema rowset included an unnecessary and undocumented column "PREFIXSYSOWNED". This column has been removed from the rowset to match similar behavior of the stored procedure than produces theTABLES_INFO schema rowset.

The OLE DB provider's TABLE_CONSTRAINTS schema rowset support procedure fails with the error "Column 'check' not found". This has been fixed.

The Upgrade utility (dbupgrad) should be used to update the OLE DB schema rowset support in any database used with ADO, ADOX or OLE DB.

http://localhost/dbname?arg

http://localhost/dbname/?arg

The problem existed for both secure and insecure services, and has now been fixed.

- The owner name is no longer added to completed table, view, or procedure names if there is only one object in the system catalog with the given name.

- A new option has been added: "The Enter key completes text". When the option is checked, pressing the Enter key completes the text with the selected item. When the option is not checked, pressing Enter will insert a newline into the text editor, but will not complete any text. This option is checked by default. If multi-line SQL statements are usually typed, it may be that leaving this option unchecked will result in fewer inadvertent completions being done.

Note: If the arrow keys are used to change the selection in the completer list, or one of the list items is selected, pressing Enter will complete the text with the selected item. In all cases, pressing the Tab key will close the completer and complete the text in the editor.

- The completer can now complete method names for spatial columns. e.g. if the insertion point immediately follows "ST_" in any of the following statements, the completer will show only methods for the spatial column "Shape":

select S.Shape.ST_ from SpatialShapes S

select Shape.ST_ from SpatialShapes S

delete from SpatialShapes where Shape.ST_

delete from SpatialShapes S where S.Shape.ST_

update set Description='x' from SpatialShapes S where S.Shape.ST_

(Note: This is not a complete list of supported syntaxes)

When trying to complete a method name for an object other than a table/view column, the completer will suggest method names as well as other database objects whose names match the method name prefix. For example, if the insertion point is at the end of the following statement:

select (new Point()).ST_

the completer will list spatial methods, but also st_geometry_dump, StartDate, Status, etc.

Note that the point is moot for the vast majority of deployments, because most deployments: (a) have one true column ordering, and (b) do downloads. MobiLink currently does not support downloads to remotes with different column orderings with the same names using the same script version. Use different script versions, each with a known column ordering, to support downloads to different column orderings.

Note, the text file containing the Agent names must have each Agent name on its own line.

A = B

A <> B

A [NOT] IN ( ... )

A = ANY ( ... )

A <> ANY ( ... )

A = ALL ( ... )

A <> ALL ( ... )

where A was a geometry column with a spatial index, extra rows may have been returned if the optimizer chose a plan that accessed the index with a scan predicate. This has been fixed.

ORA-03145: I/O streaming direction error

This would have occurred when the driver was used to send NULL BLOBs to a table in an Oracle database and then the rows were fetched back from this table using the same database connection, and the Oracle database was running with a multi-byte character set. This has now been fixed.

1. Right-click "Remote Schema Names" in the "Folders" panel and click the new "Import" menu item.

2. When adding a consolidated database to a project, either with the Project wizard or the Consolidated Database wizard, the wizards will automatically check if there are any remote schema names defined in the consolidated database that are not already in the project. If there are, the wizards will ask if they should be imported.

Note that this problem does not apply to new Alert List and Resource List widgets.

The following illustrates the issue:

create user web identified by web;

create procedure web.sp_test()

begin

select 1;

end;

create service test type 'HTML' user web authorization off secure off url off as call sp_test();

A "DROP user web" command crashes the server if one or more database connections for the user "web" happen to be pooled.

For example, the following query could have caused a crash:

SELECT *

FROM tablename

WHERE geometry_column.ST_Transform( 0 ).ST_Intersects( new ST_Point( 0, 0, 0 ) ) = 1

This has been fixed.

For example, if asatest.db is an Adaptive Server Anywhere 9 database, the following would start a server that was left running:

dbping -d -c "uid=dba;pwd=sql;dbf=asademo.db;start=dbsrv11 -x none"

This has now been fixed.

1. The result set table's long value window

2. The query tree (left hand pane) of the Plan Viewer

This has been corrected.

To workaround the problem, use code that explicitly invokes the initialize() method prior to connecting to the database. For example:

// password = password to access database

// config = config object to access database

// MyEncryptionControl = user defined class extending EncryptionControl

EncryptionControl enc = new MyEncryptionControl();

enc.initialize( password );

config.setPassword( password );

config.setEncryption( enc );

conn = DatabaseManager.connect( config );

CREATE PUBLICATION pub1 ...

CREATE PUBLICATION pub2 ...

DROP PUBLICATION pub1

This has been fixed.

This fix also affects the "Data" tab for tables and views in Sybase Central.

DBSPAWN ERROR: -85

Communication error

The communication error could also have occurred if the server was started without dbspawn. This has been fixed.

Page x of database file "<database file name>" references a table (y) that doesn't exist

or

Orphaned page (x) found in database file "<database file name>".

The database server could have left some pages in a state where they cannot be reused. The database would have continued to function normally in this state but it is possible to regain the lost pages by rebuilding the database file. This most likely would have occurred in a non-system dbspace, and has now been fixed.

Any table with the suffix "_download_only" will be marked as download-only. Tables can also be set to download-only by specifying "SYNCHRONIZE DOWNLOAD" for the sync constraint clause of the "CREATE TABLE" and "ALTER TABLE" SQL statements.

Another related change is that the sync type for a table can only be changed if it doesn't have any unsynchronized changes that need to be uploaded. Previously, the runtime was more permissive in this regard, and changing the type with unsynchronized changes could have unforeseen consequences.

In addition to "Initiate For All Recipients", a new "Cancel For All Recipients" context menu item has been added which requests that the given task be cancelled by all of its recipients.

Also, while UltraLite accepts the 'ENCODING' load option, it does not perform character set translation: the encoding of the data file must match the database. The preferred method for unloading and reloading UltraLite databases is XML files via the ulunload and ulload tools. Additionally, the ulinit tool is able to load schema and data directly from a SAS database.

Aa valid location must now be specified for your current SQL Anywhere install, and moving past the location pane in the wizard is prevented until a valid location is given. If a non-existent directory is given for the target directory, it will be created.

select row_num, if row_num < 1 then 1+row_num/0 endif x

from rowgenerator

order by x

option(force no optimization)

The sub-expression 1+row_num/0 should never be evaluated as the condition row_num<1 is never true. However, in a simple statement processed by bypassing the query optimizer, if a Sort was needed to order the rows of the result, an error could be incorrectly given. This problem has been fixed.

If an existing immediate text indexes is suspected of being effected by this problem then the text index needs to be refreshed after applying this fix.

The first new feature is two additional options for sending alert notifications via email, found under Administration -> Configuration -> Edit... -> Alert Notification

The new options behave as follows:

- "Only send email notifications for high-priority alerts", when set, will filter emails sent to operators in such a way that operators will only receive email notification when high-priority alerts are raised. Medium and low priority alerts will continue to be raised and will be viewable/resolvable from the main web-based UI as before.

- "Do not send more than the given number of email notifications per day", when set, places a hard cap on the number of email notifications sent to each operator per day. When an operator has reached their cap of email notifications for a day, an email is sent to them alerting them of this fact, as well as informing them of ways to reset the cap. This cap is reset every night at midnight, at which point the operators can once again begin to receive email notifications. Alternatively, an administrator can click the "Reset Email Notification Sent Count" button to immediately reset the caps so that operators may begin to receive email notifications again.

The second set of changes affects how the Alert Widget deletes alerts. Previously, the user would select one or more alerts and click the delete button, deleting those alerts. However, in the case of even just a few hundred alerts, this becomes unmanageable. With this change, when the user clicks the delete button on an Alert Widget, a new dialog is displayed.

Its three options behave as follows:

- "Delete selected alerts" is the same as the 12.0.0 behaviour. Only those alerts selected in the Alert Widget will be deleted.

- "Delete alerts received before" will delete all alerts received before the given time. Note that this option will only delete the alerts for resources included in this Alert Widget; if a resource's alerts are not being shown in the Alert Widget, its alerts will not be deleted by this option.

- "Delete alerts for the following resource" will delete all alerts for the selected resource. The list of resources to choose from is the same as the list of resources whose alerts are viewable from the Alert Widget.

dialects. Now, these menu items and toolbar buttons are no longer displayed.

For example, the statement

SELECT 1 + :x + :x:y + :x

would generate incorrect results when a value was substituted for :x. A work-around would be to remove the :y from the statement, since host indicator variables are parsed but not processed in UltraLite.

One workaround is to start the polygon on a different point around its ring.

To implement this new behaviour, do the following when configuring the resource for monitoring:

- When providing connection information in the new SA resource wizard, provide a comma separated list of hostname:port values for the "Host" input (e.g. "my-primary-server:2638,my-mirror-server:49152"). See http://dcx.sybase.com/index.html#1200en/dbadmin/host-con-parm.html*d5e18361 for more information.

- In the "Other" input, add "NODETYPE=primary". See http://dcx.sybase.com/index.html#1200en/dbadmin/node-type-conparm.html*d5e18888 for more information.

- In the "Server" input, use the alternate server name for your mirroring system. See http://dcx.sybase.com/index.html#1200en/dbadmin/dbserver-s-41861441.html*d5e16685 for more information.

If the the location of both the primary and mirror servers is not specified, the behaviour is the same as before (i.e. an availability alert is raised for the primary and no switch to the new primary occurs).

"Location" can now be used to specify the host name and port of the database server. The form is hostname:port (e.g., username-pc:3628). "Location" is mapped to the SQL Anywhere "Host" connection parameter for version 12 or later and the "CommLinks" connection parameter for version 11 or earlier.

"Initial Catalog" can now be used to specify the database to connect to when more than one database has been started by a SQL Anywhere database server. "Initial Catalog" is mapped to the SQL Anywhere "DatabaseName" (DBN) connection parameter.

governor" error. This has been fixed.

- If a catalog name is specified as one of the schema restrictions, the procedure will make sure it matches the current catalog. If it does not, a single row will be returned with NULLs.

- Any rowset that can return a catalog name in a column will now return the current database name in that column instead of NULL.

- The rows returned in the DBSCHEMA_PROVIDER_TYPES rowset have been slightly reordered for better results with Microsoft tools. This was done since Microsoft tools ignore the BEST_MATCH column and use the first row that matches the datatype it is searching for.

- In the DBSCHEMA_PROVIDER_TYPES schema, the XML datatype will now set the DATA_TYPE column to 141 (DBTYPE_XML), the IS_LONG column to 1 and return 2GB instead of 32767 for COLUMN_SIZE.

- In the DBSCHEMA_PROVIDER_TYPES schema, the TIMESTAMP WITH TIME ZONE datatype will now set the DATA_TYPE column to 146 (DBTYPE_DBTIMESTAMPOFFSET). This is supported in version 12 or later of SQL Anywhere.

- An entry for the REAL datatype was missing from the DBSCHEMA_PROVIDER_TYPES rowset. This row has been added.

To install these updates into a database, the Upgrade utility (dbupgrad), or the ALTER DATABASE UPGRADE statement can be used.

Running CabWiz ...

CabWiz Command Line:

"C:\Program Files\SQL Anywhere 11\ce\cabwiz\cabwiz.exe" "C:\Documents and Settings\admin\Desktop\sqlany11.inf" /dest "C:\Documents and Settings\admin\Desktop\" /compress

CabWiz Output:

Windows CE CAB Wizard

Error: Section [SourceDisksNames] - path C:\Program Files\SQL Anywhere 11\ultralite\ce\ARM.50 not found

Error creating .CAB file

C:\Documents and Settings\admin\Desktop\sqlany11.CAB

This has been fixed.

This has been fixed so that the ALTER TABLE statements will now fail.

fixed.

Note that this fix is a follow-up Engineering case 641477.

Also, the "Edit in Window" menu item was visible if a binary column value was clicked in the Results panel, and then the "..." button was clicked. This has been fixed as well.

- When the user selected a widget's "Settings..." menu item, it was possible that metrics which were present in the widget would not have appeared as selected in the list of metrics

- When creating a default dashboard for an SA resource, the table widget included on the dashboard would have been missing its Free Disk Space metrics

- If the user wanted to create resource-based dashboards during the process of adding a new user, it was possible that a widget may be missing metrics or display them improperly

These problems have now been fixed.

Function '<function-name>' has invalid parameter 'expression' ('OUT')

The correct error now reported is:

Result set not permitted in '<function-name>'

For version 12.0.0, this problem was most likely to be encountered when using string literals in different blocks of a Union, as follows:

SELECT 'String1', col1, col2 FROM table1 WHERE predicate1

UNION

SELECT 'String2', col1, col2 FROM table2 WHERE predicate2

For versions prior to 12.0.0 this problem was much more obscure, and likely required a constant string occurring both in a non-simple output expression and in a WHERE clause predicate.

This has been fixed.

For example, consider the following table and view:

CREATE TABLE admin_group.employee(

pk INTEGER PRIMARY KEY,

fname CHAR(100) NOT NULL,

lname CHAR(100) NOT NULL,

cname CHAR(100) );

CREATE VIEW admin_group.v AS

SELECT e.fname AS first_name, e.lname AS last_name,

e.cname AS company_name

FROM admin_group.employee e;

In the query:

SELECT <expr> FROM admin_group.v;

the following expressions would have been described with the base table column names:

CAST( first_name AS VARCHAR(100))

(first_name)

This has been fixed so that both of the expressions above will now be described as 'first_name'.

Additionally, expressions such as ISNULL( <col1>, <col2> ) could have been described differently depending on the nullability of the first column. For example, ISNULL( first_name, company_name ) would have been described as 'fname', whereas ISNULL( company_name, first_name ) would have been described as 'isnull( employee.fname as first_name,employee.cname as company_name)'. For consistency, both of the above expressions will now be described by unparsing the expression.

HandleNotification: Error receiving for sidx=<session_index> system error ({error code})

With this change, the error is now less likely to occur.

1. Arbitrary expressions were allowed in the FROM/USING clause of LOAD TABLE. If a variable was used, its value was logged to the transaction log; however, if the expression was anything other than a literal string or a variable (eg. 'c:\\tmp\\'+filename_var), the original expression would have been logged including the names of variables whose values would be unknown at recovery. The problem was fixed by only allowing a string or a variable for the file name (as documented).

2. If a LOAD TABLE statement was logged that used a variable in the FROM/USING clause and the statement was affected by database options such that the option values had to be logged with the statement, the variable name rather than its value would have been logged. This problem has been fixed.

3. When using LOAD TABLE ... WITH CONTENT LOGGING, the data logged was in the character set in which the server parsed the input file (either CHAR or NCHAR charset), rather than the original input file's character set. If the LOAD TABLE statement had an ENCODING clause, the data would have been re-translated during recovery as if it were in the specified ENCODING and potentially mangling the data. Fixed by logging an exact copy of the original input data.

4. If a LOAD TABLE statement did not contain an ENCODING clause (in which case the server assumes CHAR charset), the statement written to the log would not have one either. If the log were translated and executed against a database with a different collation, the file could be translated incorrectly since the default encoding would be different. This problem has been fixed by always logging an ENCODING clause.

5. If a LOAD TABLE statement contained an ENCODING clause that specified a 'UTF16' encoding of unspecified endian, the logged statement would also have contained an ENCODING clause with an unspecified endian. If recovery were performed on a server with the opposite endian, or if the log was translated then executed on a server with the opposite endian, the statement would not interpret the input file correctly. This problem has been fixed by never logging ambiguous names for encodings.

6. LOAD TABLE ... FORMAT XML ... WITH CONTENT LOGGING did not actually log any data and was not recoverable. This problem has been fixed.

7. LOAD TABLE ... FORMAT XML ... USING COLUMN (which is the statement that is logged for a LOAD TABLE ... FORMAT XML ... WITH CONTENT LOGGING) would have crashed the server. This problem has been fixed.

8. LOAD TABLE USING CLIENT FILE ... WITH FILE NAME LOGGING was permitted by the server and the server would then have logged a statement that referenced a client file. Access to the client file requires an active connection from the client and therefore this statement was not recoverable. This problem has been fixed by requiring WITH CONTENT LOGGING when loading from a client file. If the logging type is not specified when loading from a client file, content logging is assumed.

9. When recovering a LOAD TABLE ... WITH CONTENT LOGGING or executing LOAD TABLE ... USING COLUMN, the server would have leaked a small amount of memory for each row of data fetched from the table containing the pieces of the original file image. This problem has been fixed.

10. When executing LOAD TABLE ... USING COLUMN ... ENCODING..., the server did not check for a conflict between the specified encoding and the encoding of the column's datatype. This problem has been fixed by reporting an error if the encodings conflict.

11. LOAD TABLE and UNLOAD TABLE did not allow the ESCAPE CHARACTER to be more than 1 byte. It can now be an arbitrary string, but it is recommended that it should be no longer than one (potentially multibyte) character.

12. When using UNLOAD TABLE with a QUOTE or ESCAPE CHARACTER which was not encoded identically in both CHAR and NCHAR character sets, the quotes may not be doubled up or escape sequences may not be issued where necessary depending on the datatype of the column being unloaded. This problem has been fixed.

13. When using UNLOAD TABLE with a QUOTE or ESCAPE CHARACTER which were not encoded identically in both CHAR and NCHAR character sets and the destination charset, the quotes or escape characters could have been translated incorrectly when converting to the destination character set. This problem has been fixed.

14. ALTER DBSPACE RENAME allowed a variable to be used for the new file name but the variable name rather than its value was logged, which meant that the statement was unrecoverable. This problem has been fixed by logging the variable's value instead.

15. The SQL generated by the Log Translation utility (dbtran) for LOAD TABLE ... WITH CONTENT LOGGING (ie inserts into a temporary table) did not work correctly due to the temporary table's name being fully qualified with the user's name. This problem has been fixed.

Note: please see the section "Query processing phases" for a definition of bypass queries.

For example, if ls was a linestring geometry:

select ls.ST_AsSVG( 'Attribute=fill="blue"' )

would have resulted in an invalid SVG document with a duplicate attribute.

This has been fixed by only outputting the generated attribute or the attribute from the Attribute SVG format option, but not both, when there is a duplicate attribute.

This issue could have manifest itself any time the Windows look-and-feel was changed from something other than Windows Classic to Windows Classic. It would also have affected Sybase Central if a table was selected in the "Folders" panel.

This issue only occurred on Windows computers. Operation on other operating systems was not affected.

See: "SQL Anywhere Server - SQL Usage � Query optimization and execution � Query execution algorithms � Parallelism during query execution � Parallelism in queries"

or:

http://dcx.sybase.com/index.html#1200en/dbusage/queryopt-s-4716396.html*d5e30658

Note, this problem did not affect the quality of the plan found by the Optimizer, only the final estimated runtimes shown in the graphical and long plans were incorrect.

For example, the following query would have caused a crash if the optimizer chose a parallel plan:

select count(*)

from my_table

where my_table.geometry.ST_WithinDistance( new ST_Point( 0, 0, 4326 ), 10, 'kilometre') = 1

This has been fixed.

ST_XMin, ST_XMax, ST_YMin, ST_YMax, ST_LonWest, ST_LonEast, ST_LatSouth, ST_LatNorth

This has been fixed.

For example, the following sequence could have given a permission error for a user without DBA authority:

BEGIN

DECLARE myCursor CURSOR FOR SELECT 123;

OPEN myCursor;

CALL sa_copy_cursor_to_temp_table( 'myCursor','myTempTable' );

drop table myTempTable;

END

Permission denied: you do not have permission to use the "DROP TABLE"

statement

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

Further, in some cases, the temp table created by the procedure could not have been found by a reference at a different scope level. The following sequence of statements would have returned an error for that reason:

BEGIN

DECLARE myCursor CURSOR FOR SELECT 123;

OPEN myCursor;

CALL sa_copy_cursor_to_temp_table( 'myCursor','myTempTable' );

END;

go

select * from myTempTable

These problems have been fixed. In order to get the full fix, the database must be either created with the fixed server, or upgraded using the "ALTER DATABASE UPGRADE" statement using the fixed server software. As well, the sa_copy_cursor_to_temp_table procedure now uses "CREATE LOCAL TEMPORARY TABLE" to create the table.

This change now does the following:

1. Temporary and user specific settings are no longer allowed

2. Existing settings for non-PUBLIC users are ignored during execution

3. Removal of existing user specific settings is allowed in order to allow cleanup

4. dbunload sets the public option setting at the beginning of the reload script

5. dbunload ignores non-PUBLIC settings in the database being unloaded

For example: Store binary 0x1234 into column.

INSERT INTO test (binary_col) VALUES ('1234');

The result is 0x31323334.

If the LITERAL_PREFIX was 0x and the LITERAL_SUFFIX was NULL, then the value stored was correct.

INSERT INTO test (binary_col) VALUES (0x1234);

This problem has been corrected. The following types will now return 0x in the LITERAL_PREFIX column and NULL in the LITERAL_SUFFIX column:

long binary

varbinary

binary

DBTYPE_DBTIME2 differs from DBTYPE_DBTIME in that fractional seconds are included. The type corresponds to the Microsoft SQL Server TIME data type.

DBTYPE_TIMESTAMPOFFSET adds support for a timezone offset (hours/minutes). The type corresponds to the Microsoft SQL Server DATETIMEOFFSET data type.

When using the "Connect with an ODBC Data Source" option in the "Action" dropdown list of the "Login" tab of the connection dialog with the 64-bit versions of the dbisqlc utility and dbmlsync, no DSNs would have been displayed; and the 32-bit versions would only have shown DSNs that used an ODBC driver with the same major version of SQLAnywhere as dbisqlc and dbmlsync. This has been fixed, so that 32-bit and 64-bit versions now display all SQLAnywhere DSNs defined for SQLAnywhere version 6.0 and up.

Dbisqlc did not correctly handle certain connection string components which did not have a shortform (such as the new "Server" parameter). This problem has been fixed.

Task task1 (ID 50): command number 1 not executed, error code 0

when a task was executed that connected to a remote database, and the adapter library (eg. mlauladapt12.dll) for that remote database was missing from the agent deployment. This has been fixed so that a clearer error message is now displayed.

A workaround is to reduce the number of logical processors the server uses by specifying

-gtc <num>, where num is less than or equal 24.

A work around is to specify the -cn switch with a value of the twice the value of -w plus 1. Eg. if using the default value of -w (5), specify -cn 11. Version 12 is not affected as it no longer supports old clients.

"Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action SetupVSPackageUninstall, entry: SetupVSPackageUninstall library: C:\Windows\Installer\MSIA8A0.tmp"

This has been fixed.

writing to the stream during a synchronization. This has been fixed.

Error: Microsoft Activesync is not installed. CEAppMgr.exe is not detected. .CAB file will not be deployed.

A workaround is to run without the GUI.

become daemon" if both the -um and -ud command line options were specified. This was due

to a limitation in the OS X GUI infrastructure. This has been fixed. The -um flag is now ignored if -ud is specified.

A workaround is to use dbspawn instead of -ud.

INSERT INTO my_proxy_table(my_column) SELECT RTRIM( ' ' )

may have inserted NULL instead of '' into to my_proxy_table. This problem has now been fixed.

Note that the default transaction mode is Chained.

was not being accepted. This has been fixed.

needed to be processed in either no passthrough or partial

passthrough mode, could have resulted in a server failure.

The server now properly returns error -890.

Note, There is no guarantee that FIXED format files created by DBISQL use the same column widths as DBISQLC.

dbeng12: error while loading shared libraries: libdbserv12_r.so: cannot enable executable stack as shared object requires: Permission denied

This would have potentially happened with any SQL Anywhere binary, and has now been fixed.

A work around is to either disable SELinux, or run execstack -c on the problematic binaries.

like the following:

Table 'ml_database' has changed:

Column 'rid' has changed:

type from numeric to integer

If the only differences reported were "type from numeric to integer" then the error can be safely ignored. This has been fixed.

The work around is to restart the MobiLink server.

INSTALL JAVA [NEW | UPDATE] JAR 'jar-name' FROM expression

then there was a chance the server would have crashed. This problem has now been fixed.

For example, the following sequence could generate this error:

declare local temporary table T_strs( str long varchar );

insert into T_strs values ('1,a1\n2,a2'), ('3,b1\n4,b2');

select *

from T_strs T cross apply openstring( value T.str ) with( a char(10) ) as O

This has been fixed. Statements such as the above are now processed correctly without an error.

For synchronization logic that does not use timestamp based download, users must grant Select permission to the MobiLink server login ID, or create a script for the generate_next_last_download_timestamp event. This script can be defined as an ignored script using the syntax, '--{ml_ignore}'.

- ID and Description on the "Create Backend Server Farm" dialog

- ID, Security Token and Description on the "Create Backend Server" dialog

- Description on the "Create Relay Server" dialog

These fields now limit input to 2048 characters.

For example:

WHERE

(T.A1 = c11 and T.A2 = c12 and ... and T.Ak =c1k) OR

.....

(T.A1 = cN1 and T.A2 = cN2 and .... and T.Ak =cNk)

AND

(other predicates)

The values for c11, c12, ..., cNk are constants, and N is large. The following sargable IN predicates were generated from the original predicates:

T.A1 IN {c11,c21, ..., cN1} AND

...

T.Ak IN { c1k, ..., cNk}

If there existed an index on table T with a prefix on any combination of the columns T.A1, ..., T.Ak, then a partial index scan using the sargable IN predicates could have been chosen in the best access plan. For example, if an index 'idx1' existed on T < A2, Ak > then the partial index scan [ {c12, ..., cN2} JNL {c1k, ..., cNk} JNL T <idx1>] may have been used in the best access plan. The original predicate would still have been applied after the index scan as a postfilter.

This optimization was not implemented starting with SA 10.0.0, as multiindex scans introduced in SA 11.0.0 and enhanced in SA 11.0.1 provided more general access methods using any combination of UNION and INTERSECTION of indexes. Multiindex scans performed better than the above optimization for small to medium size DNF predicates. However, multiindex scans can be inefficient when the number of predicates is large, for example, DNF predicates having 1,000 or more terms. This new feature addresses, in a very general way, these extreme cases and other cases when multiindex index scans use the same index. A multicolumn inmemory table is built with the exact combinations used in a DNF term, and this table is joined with the index scan. In the example above, if an index 'idx2' on T<A1, A2,..., Ak> exists, the access method

[{(c11,c12,...,c1k), (c21,c22,...,c2k),..., (cN1, cN2, ..., cNk)} JNL T<idx2>]

will be built.

Prior to this change the following multiindex scan was considered:

T<idx2: (c11,c12,...,c1k)> UNION T<idx2: (c21,c22,...,c2k)> UNION ... UNION T<idx2: (cN1,cN2,...,cNk)>

This multiindex scan could have been inefficient if N was greater than 1,000.

For example, open the Interactve SQL utility (dbisql), connect to database and enter the following:

select * from foo;

select 'hello'

Since there is no table foo, the first statement generates an error dialog with a 'Stop' and 'Continue' button. Hitting escape here is now the same as pressing the 'Stop' button.

create table [ab'cd] (i int )

This has now been fixed so that the driver now supports table names with embedded quotes enclosed in brackets.

CREATE FUNCTION ...

RETURNS ...

BEGIN

DECLARE variable ...

SELECT ... INTO variable FROM ...

RETURN variable

END

and the SELECT statement within the function referenced proxy tables, then there was a chance the server would have crashed. This problem has now been fixed.

An example would be

SELECT * FROM table WHERE c1 = 10 ORDER BY c2

where c1 and c2 each were the first column in different indexes.

The workaround is to rewrite the SQL statement to not use window functions.

1. the outer join is of the form : T as T1 LEFT OUTER JOIN T as T2 ON(p)

2. the ON predicate p has only equijoins, and at least two equijoins

3. p is of the form : T1.c1 = T2.c1 and T1.c3 = T2.c2

4. there exists an unique index on T < c1,c2>

This has been fixed.

This affected all programs that use the "Connect" window to connect to a SQL Anywhere database -- the Interactive SQL utility, Sybase Central, and the Console utility. A workaround is to add "astop=no" to the "(other)" field on the "Advanced Options" tab.

Note, Engineering case 650345 is a similar issue in the Administration tools connection dialog.

For example, the query:

SELECT SUM( java_p(...) ) FROM ...

involves repeatedly calling java_p and the performance of such queries will be improved with this fix. In addition, the query:

SELECT SUM( java_p(...) ), AVG( java_p(...) ) FROM ...

also involves repeatedly calling java_p, and again the performance of such queries will be improved with this fix. But, the query:

SELECT SUM(java_p(...)), AVG(java_p2(...)) FROM ...

which involves repeatedly calling both java_p and java_p2 will not benefit from this performance improvement.

could be poor when dynamic adjustment of the multiprogramming level is enabled. This has been fixed.

Note, both desktop and device side applications must be updated simultaneously.

To patch an existing MobiLink system setup:

1. Shut down the MobiLink servers

2. execute the SQL in %SQLANY12%\MobiLink\Setup\syncmss_ebf.sql

The patch only updates stored procedures, no data will be disturbed by this script. MobiLink systems setup after installing this fix do not need the patch to be applied.

Note that this change did not affect the software itself.

A workaround is to pre-grow the temporary file using the ALTER DBSPACE statement, or by creating a DiskSpace event to periodically grow the temporary file.

The same issue was fixed for earlier version by Engineering case 580773.

In addition, http authentication options, proxy options, and proxy authentication options, have been added in version 12.0.1.

For example, the following set of calls would have inserted incorrect data into the table test:

PreparedStatement pstmt = con.prepareStatement( "insert into test values(?,?)" );

pstmt.setInt(1, 1001);

pstmt.setString(2, "this is row #1" );

pstmt.addBatch();

pstmt.setInt(1, 2001);

pstmt.setString(2, "this is row #2" );

pstmt.addBatch();

pstmt.setInt(1, 3001);

pstmt.setString(2, "this is row #3" );

pstmt.addBatch();

// note the fact that we are switching datatypes below

pstmt.setNull(1, java.sql.Types.SMALLINT);

pstmt.setString(2, "this is row #4" );

pstmt.addBatch();

pstmt.executeBatch();

Again, note that this problem would not have occurred if instead of using java.sql.Types.SMALLINT, the application instead used java.sql.Types.INTEGER. In addition, if the call to setNull() was not in the last row of the batch, then again this problem would not have occurred, even if the application switched datatypes for the setNull() call.

113300 or 113302 "failed to build cursor to validate". This problem has been fixed and the underlying error is now reported: SQL error (-1515) -- Support for spatial is not available for this CPU.

Note, the system view must be recreated by upgrading or rebuilding the database for the new view definition to be used.

2 - TOP supports the 'ALL' limit indicating that all rows are to be returned after the specified 'startat';

3 - the maximum value for (limit + offset) is now 9223372036854775807 = 2^64-1

The new grammar is as follows:

TOP range_expression range_offset

TOP T_ALL range_offset

LIMIT range_expression [OFFSET range_expression]

range_expression:

integer_or_var | '(' simple_expression ')'

simple_expression:

integer_or_var | simple_expression '+' simple_expression

| simple_expression '-' simple_expression

| simple_expression '*' simple_expression

| '(' simple_expression ')'

range_offset: /* empty */

| T_START T_AT range_expression

Note that the 'STOP SERVER' syntax is new to version 12 (older servers support 'STOP ENGINE').

need to shut down or kill SQL Remote when it is sending multi-part messages to its subscribers.

Note that the root value is case sensitive (i.e. "FiLe:///SDCard/me.blob" is ok but "FiLe:///sdcard/me.blob" is not).

Description of case 636018:

Queries involving indexes containing long values could have returned incorrect results. Index corruption was possible, but not likely..

SELECT ... FROM dirtab WHERE file_name = '...'

where dirtab was a directory access table and the file_name string literal contained non-ASCII characters, there was a chance the server would have crashed. This problem has now been fixed.

updated rows using @@rowcount and sqlcount. This has now been corrected.

- On the response to the first HTTP request in the session, or specifically, anytime a cookie was set, if the response was long and came in small packets.

- A small number of bytes were leaked on Upchannel and Dnchannel creation.

This has been fixed.

This behaviour has changed so that the MobiLink server will retry to make connections, when it is running as a Windows services. The retries are once a minutes for ten minutes. If it still cannot make a connection after that, it will refuse to startup.

Also, it was noticed that synchronizations were not initially listed in chronological order if the log file contained output for more than one run of the MobiLink Server. This has also been fixed.

The variable {is_online} can be used to check whether the client device is connected to a network on which the MobiLink server of the agent can be reached. Note that this variable is not equivalent to a ping of the MobiLink host machine, nor of the MobiLink server itself. The host machine may be offline and the variable will still evaluate to 1 (true). This variable evaluates to 1 if and only if the client device is connected to a network such that there is a route to the IP address of the MobiLink server. This variable is supported for agents running on Windows and Windows Mobile operating systems.

The variable {network_conn_name} evaluates to the name of the network connection that will be used by the agent for communication with its MobiLink server. This variable is only supported on Windows operating systems. The list of possible network connection names for a given Windows-based device can be obtained by going to Control Panel/Network Connections on Windows XP, or going to Control Panel/Network and Sharing Center on Windows Vista and Windows 7. Alternatively, the list of network connection names can be obtained from the information returned by the ipconfig command line utility. The network connection name for the loopback connection (destination IP address 127.0.0.1) is "Loopback interface". If there is no network connection that can be used by the agent to communicate to the MobiLink server, this variable evaluates to "?".

A remote task can have a "random delay interval", which is an interval N, in seconds, with which each agent generates a random number of seconds in [0, N) to delay each task execution. If the task is a scheduled task, the random delay is generated before the first task execution, and used for each execution. The task is executed at the scheduled times offset by the random delay. This ensures that the deltas of the task execution times are consistent with the schedule. It is not recommended that the random delay interval be larger than smallest delta time of a scheduled task. If the task is an "on demand" task, that is initiated by the server, the random delay is generated and used to delay the execution each time the task is initiated. If the task is a "run on receipt" task, the random delay is generated and used to delay the execution at the first and only time the task is executed.

Valid keys include:

relative-tolerance-percent=<double>

absolute-tolerance=<double>

The value for relative-tolerance-percent specifies the maximum variation (in percent) in the distance from the centre point of the ST_CircularString segment to the interpolated ST_LineString segment, relative to the radius of the ST_CircularString segment. This value defaults to 0.3, which gives 40 points in a complete circle. Its minimum value is 0, meaning the absolute-tolerance setting is always used.

The value for absolute-tolerance specifies the maximum absolute variation (in linear units) in the distance from the centre point of the ST_CircularString segment to the interpolated ST_LineString segment. This value defaults to the tolerance specified by the SRID. Its minimum value is also the tolerance specified by the SRID.

If neither key is specified, the defaults are used. If only one key is specified, the other one is set to its minimum value. If both keys are specified, the minimum number of points will be produced such that both restrictions are satisfied.

Regardless of the setting, there will be at least 3 points per curve segment. Additional points may be added to ensure the ST_Envelope of the ST_LineString is the same as that of the original ST_CircularString. Furthermore, no two consecutive points on the interpolated ST_LineString will be within tolerance of each other.

{ml s.new_username} and {ml s.new_remote_id}

These new named parameters are not available through question marks (?) in any MobiLink server events.

The values of the s.new_username and s.new_remote_id parameters would be the MobiLink user name (used for user authentication) and the remote ID, respectively, if the user name and remote ID are new in the consolidated database (they are not in the ml_user and ml_database tables). Otherwise, their values will be NULL: more precisely, the s.new_username will be NULL if the MobiLink user name is already in the ml_user table, and the s.new_remote_id will be NULL if the remote_id is already in the ml_database table.

Syntax

st_geometry_load_shapefile( shp_filename

, srid

, table_name

[, table_owner [, shp_encoding ] ] )

Arguments

- shp_filename A VARCHAR(512) parameter that identifies the location of the ESRI shape file. The file name must have the extension .shp and must have an associated .shx and .dbf file with the same base name located in the same directory. The path is relative to the database server, not the client application.

- srid An INTEGER parameter that identifies the SRID for the geometries in the shape file.

- table_name A VARCHAR(128) parameter the specifies the name of the created table.

- table_owner An optional VARCHAR(128) parameter the specifies the owner of the created table. The default owner is the current user.

- shp_encoding An optional VARCHAR(50) parameter that identifies the encoding to use when reading the shape file. The default encoding is ISO-8859-1.

Remarks

The st_geometry_load_shapefile system procedure first creates the table "table_owner"."table_name" using the column names a types from the ESRI shape file. Then the procedure loads the data from the shape file into the new table. If loading the data from the shape file fails, the created table remains.

This procedures makes use of the sa_describe_shapefile system procedure and the LOAD TABLE ... FORMAT SHAPEFILE statement.

Permissions

RESOURCE authority is required.

If the -gl option has been set to DBA, DBA authority is required.

If the -gl option has been set to NONE, loading the data will fail.

Side effects

Automatic commit

See also

sa_describe_shapefile

LOAD TABLE

Admin tools load shapefile wizard

Example

The following examples creates the table "esri_load" with spatial reference system 1000004326 and loads the data from c:\esri\shapefile.shp:

call st_geometry_load_shapefile( 'c:\\esri\\shapefile.shp', 1000004326, 'esri_load' );

� GetUploadTransaction (this callback may be called several times based on how many syncs and upload transactions appear in the recorded protocol file being replayed)

� GetDownloadApplyTime

� ReportEndOfReplay

� DelayStartOfReplay

The purpose of the above callbacks has not changed with the addition of this new feature. The differences are the repetitionNum and numRepetitions parameters will no longer always be 1 and GetUploadTransaction may now be called concurrently.

Another new option has been added as well, -ls, which tells the Replay utility to log statistics about each simulated client. In particular, using the 杔s option will log the total running time, the total time spent replaying, and the total number of repetitions completed successfully, failed, or skipped for each simulated client. The Replay utility will still log a summary just before exiting containing the total number of repetitions completed successfully, failed, or skipped, as well as the total time spent replaying and the total running time, even when the 杔s option is used.

A new "Use column default instead of a trigger" option has been added to both the Timestamp Download Options page of the Create Synchronization Model Wizard and the Download Type tab of the Table Mapping Editor.

This feature is required for Sybase IQ and is now the default option for SQL Anywhere. DB2 and MySQL only allow one automatic timestamp column per table, so the default for those consolidated database types is to use triggers.

The following column defaults are used:

- For SQL Anywhere and Sybase IQ: DEFAULT TIMESTAMP

- For DB2: GENERATED ALWAYS FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP

- For MySQL: DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

Note that a trigger must be used if a shadow table is used to hold the timestamp column.

serialized. The requirement for serializing uploads with Sybase IQ is described in the following topic:

MobiLink - Server Administration

� Using MobiLink server technology

� MobiLink consolidated databases

� Sybase IQ consolidated database

public delegate void ULSyncProgressedDlg( IAsyncResult result, ULSyncProgressData data )

This method is invoked during synchronization to provide progress information. Unlike the SyncProgressed method of the ULSyncProgressListener interface, the synchronization is not being held up during calls to this method and it is safe to do GUI work or make UL.NET API calls.

public IAsyncResult ULConnection.BeginSynchronize()

Creates a new thread to do a synchronization and then returns immediately.

public IAsyncResult ULConnection.BeginSynchronize( Control control, ULSyncProgressedDlg dlg, object state )

Creates a new thread to do a synchronization and then returns immediately. The ULSyncProgressedDlg method is invoked on the provided Control object regularly during sync to provide progress information.

public void ULConnection.CancelSynchronize( IAsyncResult asyncResult )

Tells the synchronization thread to terminate and then returns immediately.

public void ULConnection.EndSynchronize( IAsyncResult asyncResult )

Blocks until an asynchronously launched synchronization terminates. A ULException is thrown if the sync failed.

public bool ULSyncProgressData.IsFinalSyncProgress

This property is true if this is the final sync progress message for a sync.

Note, opening a database with 12.0.1 will upgrade the database so that it is no longer compatible with 12.0.0.

iAnywhere.Mobilink.Client.dll

iAnywhere.QAnywhere.Client.dll

iAnywhere.QAnywhere.Resources.dll

iAnywhere.QAnywhere.ws.dll

These files were being installed in the Global Assembly Cache (GAC), but an additional copy was not also put in the assembly\v2 directory. This has been corrected so that these files are now installed in both locations.

- Loading of (multi)polygons belonging to round earth spatial reference systems.

- Loading of complex (multi)polygons (i.e., polygons defined by many rings or rings containing many points)

- Spatial set operations (e.g., ST_Union, ST_Intersection, etc.) applied to complex geometries

- Spatial predicates (e.g., ST_Contains, ST_Intersects, etc.) where one of the geometries is complex

- Spatial predicates where one of the geometries is a point

-w <count> set the initial number of concurrent database worker threads (up to -wm)

-wm <count> set the maximum number of concurrent database worker threads

Notes:

- The -w option has been changed to be the _initial_ number of concurrent database worker threads

- The -wm option now defaults to -w, ie. no automatic adjustment will occur when -wm is unset. In other words, the automatic adjustment is triggered by the presence of the -wm option

- The number of database worker threads is now automatically adjustable anywhere between the initial (-w) value and the -wm value

- The -wu value is not automatically adjusted, and its meaning remains basically the same, with one important difference: If not specified, uploads may be applied on any or all database worker threads (which is now a variable number). If specified, uploads may only be applied concurrently on the given number of database worker threads. So by default, when feature attempts to ramp up the number of database worker threads in an attempt to increase throughput, contention may increase in the short term until it is detected and the thread-count is eventually decreased.

- The automatic adjustment means that some customers may find optimal throughput only when -wu is set explicitly, because leaving it unset causes download throughput to be artificially limited by the contention of the uploads. Setting -wu is most likely to be required in high-load environments where uploads are constantly intermixed with download-only synchronizations.

- If contention in the consolidated is the cause of throughput degradation, then this new feature will reduce the number of worker threads REGARDLESS of the cause of the contention (eg. other syncs vs. a contentious batch process outside of syncs).

- Each ML server in a farm makes thread-count decisions independently. Over time, on average, each server in an ML farm should end up at the same thread-count number assuming a uniform load distributed evenly across the farm.

This problem has been fixed in the upgrade scripts for Oracle.

The following steps can be used to correct the problem if the Oracle consolidated database had already been upgraded with the old upgrade scripts:

1) Shut down all MobiLink servers;

2) Execute the SQL file against the Oracle consolidated database with the following command line:

sqlplus LoginID/Password@TNSServerName @%SQLANY12%\MobiLink\Upgrade\fix_ora.sql

Replace the LoginID, Password, and TNSServerName in the above command line with your own login information.

For example:

create index idx1 on T(C1, C2);

select * from T where T.C1 = 10 and T.C2 IS NOT NULL

The query Q may have, depending on the selectivity of the predicates "T.C1 = 10" and "T.C2 IS NOT NULL", the following plan:

T<idx1>

where the partial index scan on <idx1> is set as follows:

idx1:

c1 = 10

NULL < c2

upgrade_x.sql

where x can be sa, ase, mss, ora, db2, and mys; and represent upgrade scripts for SQL Anywhere, Sybase ASE, Microsoft SQL Sever, Oracle, DB2, and MySQL, respectively. These upgrade script files can be found in MobiLink\Upgrade\x.y.z of the SQL Anywhere installation, where x.y.z stands for the earlier version that is currently in use. For instance, when upgrading from MobiLink version 9.0.2 to version 12.0.1 with an Oracle consolidated database, the upgrade script needed is upgrade_ora.sql that can be found in the directory, MobiLink\Upgrade\9.0.2 in the SQLAnywhere 12.0.1 installation.

document and text index content. Text indexes indexing long documents will benefit the most from this improvement.

The following example gives a better idea of how this new feature can be used. Note that this example uses a directory access server for demonstration but this new feature is not at all restricted to the type of remote data access server.

SSuppose a dba has a database that is sometimes started on machine A with the server name server1 and at other times the database is started on machine B with the server name server2. Now suppose the dba wants to set up a directory access server that points to the local drive d:\users on machine B which is also the network driver w:\users on machine A.

In addition, the dba wants to set up a single proxy table that all users can use to get the listing of their own directory located at users\userM. With the addition of variables in the USING and AT clause, the dba can now accomplish everything needed with a single directory access server and a single proxy table as follows:

First, with the database running on machine B connect as dba and execute the following in DBISQL

-- define the directory access server with variables in the using clause

-- the two variables in this example are for the root of the directory access server and the subdirectory level

create server dir class 'directory' using 'root={@directory}\\users;subdirs={@subdirs}';

-- next create explicit extern logins for each user that will be allowed to use the directory access server

create externlogin dba to dir;

create externlogin user1 to dir;

create externlogin user2 to dir;

...

create externlogin userM to dir;

-- now use one of the user accounts to create the single proxy table that all users will use

create variable @directory long varchar;

set @directory = 'd:';

create variable @subdirs varchar(10);

set @subdirs = '7';

create variable @curuser varchar(128);

set @curuser = 'user1';

create variable @server varchar(128);

set @server = 'dir';

-- this will now create a proxy table that points to @directory\users\@curuser on directory access server @server

create existing table dbo.userdir at '{@server};;;{@curuser}';

-- we no longer need the variables so clean them up

drop variable @curuser;

drop variable @subdirs;

drop variable @directory;

-- we also no longer need an extern login mapping for dba

drop externlogin dba to dir;

-- now create a procedure that all users will use to view the contents of their individual user directory

create procedure dbo.listmydir()

begin

declare @directory long varchar;

declare @subdirs varchar(10);

declare @server varchar(128);

declare @curuser varchar(128);

-- for this example we always use the "dir' remote data access server

set @server = 'dir';

-- the root directory is based on the SQL Anywhere server the user is connect to

set @directory = if property('name') = 'server1' then 'w:' else 'd:' endif;

-- the subdir limit is based on the connected user

set @curuser = user_name();

-- all users get a subdir limit of 7 except user2 who gets a limit of 1

set @subdirs = convert( varchar(10), if @curuser = 'user2' then 1 else 7 endif);

-- now we are all set to go

-- with all the variables set above the proxy table dbo.userdir now points to @directory\@curuser and has a subdir limit of @subdirs

select * from dbo.userdir;

end

grant execute on dbo.listmydir to public;

If userN where userN is not in (user1, user2, ... userM) attempts to use dbo.listmydir(), the select statement will fail due to the fact that userN does not have an extern login mapping for directory access server "dir".

If, on the other hand, users userI and userJ where userI and userJ are both in (user1, user2, ... userM) attempt to use dbo.listmydir(), then userI will get a listing of his/her own directory located at users\userI and userJ will get a listing of his/her own directory located at users\userJ even though both query the exact same dbo.userdir proxy table. In addition, if the database now moves from machine B to machine A, then all will continue to work since the @directory variable in the USING clause will now get set to "w:\users" instead of "d:\users".

The new grammar is as follows:

TOP range_expression range_offset

TOP T_ALL range_offset

LIMIT range_expression [OFFSET range_expression]

range_expression:

integer_or_var

| '(' simple_expression ')'

;

simple_expression:

integer_or_var

| simple_expression '+' simple_expression

| simple_expression '-' simple_expression

| simple_expression '*' simple_expression

| '(' simple_expression ')'

;

range_offset: /* empty */

| T_START T_AT range_expression

When the "Initialize with settings for central administration of remote databases" option is selected, the defaults are changed for the following deployment settings:

- On the New SQL Anywhere Remote Database page, the "Create a remote SQL Anywhere database" option is not selected.

- On the New UltraLite Remote Database page, the "Create a remote UltraLite database" option is not selected.

- On the Existing Remote Database page, the "Connect to the remote database to directly apply the changes" option is not selected.

- On the MobiLink User and Synchronization Profile page (formerly MobiLink User or MobiLink User and Subscription) the following are changed:

- The user name is set to {ml_username}.

- The password is set to {ml_password}.

- The "Register this user in the consolidated database for MobiLink authentication" option is not selected.

With this option selected, deployment with create a remote database SQL file that can be used in a remote task. The {ml_username} and {ml_password} macro values are replaced with the MobiLink user and password being used by the MobiLink Agent when the SQL is executed on the remote database.

. the help topics are displayed using the master help file sqlanywhere_[LL]12.chm when full HTMLHelp documentation is installed, or

. if sqlanywhere_[LL]12.chm is not found, the help topics are displayed using context sensitive help file sacshelp12.chm, or

. if sacshelp12.chm is also not found, the help topics are displayed in DocCommentXchange with system's default internet browser

Please note that before this change, the Help buttons used dbco[LL]12.chm, which was installed in the bin32 folder by the main software installer. Now dbco[LL]12.chm is longer be provided.

[LL] is the language code of the help files.

"Average Request time"

"Average Backend server processing time"

"Average Response time"

"Average Request Completion time"

The problem has been fixed.

The Deployment Wizard's MobiLink User and Subscription page (for SQL Anywhere databases) and MobiLink User page (for UltraLite remote databases) have been merged into the MobiLink User and Synchronization Profile page, which has an option to specify the synchronization profile name. For SQL Anywhere remote databases, the same name is used for the synchronization subscription. The default name combines the publication name and MobiLink user name, since the profile is linked to the publication and user. It is automatically updated to be of the form <publication name>_<MobiLink user name> when the mobilink user name is changed, but is uncoupled when it is directly edited. The deployment option to name the synchronization profile replaces the option to name the subscription for a SQL Anywhere remote database that was added in version 12.0.0. This feature removes the need to manually create a synchronization profile after deploying a synchronization model to use with central administration of remote databases.

The server must be defined with the CREATE SERVER statement to use this system procedure. TThe arguments are as follows:

@server_name Use this CHAR(128) parameter to specify the server the SQL statement will be executed on.

@sql Use this LONG VARCHAR parameter to specify the SQL statement to execute on the remote server.

Note that an ALTER DATABASE UPGRADE is required to get the new stored procedure.

Permissions: None

Side effects: There are no local side effects to executing this stored procedure; however, since the SQL statement that gets executed on the remote is completely arbitrary, there may be side effects on the remote server.

Example:

The following very simple example uses the sp_forward_to_remote_server() stored procedure and a local function to determine the number of tables that a remote SQL Anywhere 12 database has.

-- create the remote data access server

create server rem class 'saodbc' using 'driver=SQL Anywhere 12;...';

-- assume extern logins are not needed

-- create the local function that in turn calls sp_forward_to_remote_server

create function fetch_num_remote_tables(in server char(128) ) returns int

begin

declare num_tables int;

declare curs cursor for call sp_forward_to_remote_server( server, 'select count(*) from sys.systable' );

open curs;

fetch next curs into num_tables;

close curs;

return num_tables;

end

-- fetch the number of tables from the remote server

select fetch_num_remote_tables( 'rem' )

New connection parameters to control the cache size limits are:

'cache_min_size' - The minimum cache size, in bytes, with k and m suffixes as with 'cache_size'.

'cache_max_size' - The maximum cache size, in bytes, with k and m suffixes as with 'cache_size'.

There are platform and memory size-specific defaults for these values. The default maximum size is limited to 20Mb for devices and 50Mb for desktops. Normally, the application should not have to specify any cache-size parameters.

The new database option 'cache_allocation' is used to explicitly resize the cache. The value is a percentage of the minimum-to-maximum range. A value of zero means the minimum size, and a value of 100 means the maximum size. The 'cache_allocation' property returns the current cache size as a percentage value.

Property for Connection Time

A new connection property, ConnectedTime, returns the total length of time in seconds that a connection has been connected. There are also database and server-level versions of the same name; these return the total time that all connections to the database/server have been connected. Two notes of caution for the database and server versions:

The database and server level properties are updated only when a request completes for the connection or the connection disconnects. The database/server properties can therefore lag behind for connections that are idle or busy executing for a long time in the server. The property is updated only at the end of the operation to reduce the overhead needed to maintain the property.

The database and server level properties include time accrued by any connection, and this includes database events and background server connections (such as the cleaner)

User-Defined Counters

The SA performance counter mechanisms provides a way to monitor statistics in a running server. In some cases, a database application has similar statistics that would be useful to measure when monitoring a performance issue. To that end, new user-defined counters are defined. These are not set by the server, and must be set or incremented explicitly by calling one of two new functions. The counters can be read using any of the methods supported for performance counters (property functions, dbo.sa_performance_statistics(), performance monitor).

There are two classes of counter, RAW and RATE. The RAW counters are displayed as an absolute value in the performance monitor, while RATE counters are shown by measuring the change of the counter during a measurement interval. For example, a RAW counter would be appropriate for showing the current number of keys remaining in a key pool; this value would fluctuate up and down over time. Alternatively, a RATE counter would be appropriate for showing how quickly keys are being used from a key pool. The counter would increase monotonically over time as keys are used, and the performance monitor would show the rate that keys are used per second.

The new counters are named UserDefinedCounterRaw01, ..., UserDefinedCounterRaw05 and UserDefinedCounterRate01,...,UserDefinedCounterRate05. These counters are recorded at the scope of connection / database / server.

Two new functions are provided to increment these values or set them to a new absolute value:

create function dbo.sa_user_defined_counter_add(

in counter_name varchar(128),

in delta bigint default 1,

in apply_to_con int default 1,

in apply_to_db int default 1,

in apply_to_server int default 1 )

returns int

internal name 'sa_user_defined_counter_add'

The sa_user_defined_counter_add() system procedure adjusts a user-defined counter by an amount (delta). The counter_name parameter is the text name of the counter to adjust. By default, the counter is adjusted by 1 at the connection, database, and server scopes. The parameters apply_to_con, apply_to_db, and apply_to_server can be either 0 (do not apply) or 1 (do apply) to control the scopes where the delta is applied. To accomodate future expansion, the delta parameter is declared as a bigint. However, values outside of the range of an int generate an error. The function returns 1 if the delta was applied, otherwise 0.

create function dbo.sa_user_defined_counter_set(

in counter_name varchar(128),

in value bigint,

in apply_to_con int default 1,

in apply_to_db int default 0,

in apply_to_server int default 0 )

returns int

internal name 'sa_user_defined_counter_set'

The sa_user_defined_counter_set() system procedure changes a user-defined counter to a new value. The counter_name parameter is the text name of the counter to adjust. By default, the counter is set to the specified value at the connection, database, and server scopes. The parameters apply_to_con, apply_to_db, and apply_to_server can be either 0 (do not apply) or 1 (do apply) to control the scopes where the value is applied. To accomodate future expansion, the value parameter is declared as a bigint. However, values outside of the range of an int generate an error. The function returns 1 if the value was applied, otherwise 0.

Concurrent access to counters are applied atomically so it is safe to increment a counter from multiple concurrent requests or to set a counter from concurrent requests.

New scope for properties:

The following properties were previously maintained for a single connection only. In version 12.0.1, these properties are accumulate to the database and engine level, and they can now be retrieved using database_property() and property():

ApproximateCPUTime -- approximation of CPU time spent by connection/db/server

ReqCountXXX -- count of times connection entered state XXX={Unscheduled,Active,BlockIO,BlockLock,BlockContention}

ReqTimeXXX -- total time connection spent in state XXX={Unscheduled,Active,BlockIO,BlockLock,BlockContention}

The accumulation for these properties is done at the end of a request; this means that executing requests don't update the database/server properties until the request completes.

New scope for counters:

Perviously, some performance counters were defined at scope "con" or "con/eng". In version 12.0.1., these are instead defined as "con/db/eng" so that the property can be attributed to a particular database when the server is running more than one database.

Bytes_Received

Bytes_Received_Uncomp

Bytes_Sent

Bytes_Sent_Uncomp

Carver_Heap_Pages

Client_Stmt_Cache_Hits

Client_Stmt_Cache_Misses

Client_Stmt_Track_Mem

Client_Stmt_Tracked

Commit

Cursor

Heaps_Carver

Heaps_Locked

Heaps_Query

Heaps_Relocatable

Open_Cursor

Packets_Received

Packets_Received_Uncomp

Packets_Sent

Packets_Sent_Uncomp

Query_Heap_Pages

Query_Mem_Active_Curr

Query_Mem_Grant_Failed

Query_Mem_Grant_Granted

Query_Mem_Grant_Requested

Query_Mem_Grant_Waited

Query_Mem_Grant_Waiting

Requests_Received

Rollback

Statement

With this change, these counters can now be retrieved using property(), db_property(), or connection_property().

global_database_id

ml_remote_id

Options which are temporary or connection-based by nature do not have a commit side effect. These are:

commit_flush_timeout

commit_flush_count

isolation_level

cache_allocation

-gns, -gnl, and -gnh) will now generate an error if they are used on the personal server. For 12.0.0, these options were silently ignored, now for 12.0.1 using any of these options on the personal server will generate the following warning:

Warning: option X is ignored by Personal Server.

X can be one of -gna, -gnh, -gnl, or -gns

Also, when a server acting as primary (S1) accepted an inbound connection from the mirror (S2), S1 attempted to make an asynchronous outbound connection to S2 if one did not already exist. If this connection attempt failed, S2 would have failed to receive updates from S1.

These problems have now been fixed.

- Known values for expressions are now dumped in the plans. For example, a stored procedure parameter known at the optimization time is dumped as 'parm1[100]' if its name is 'parm1' and its known value is '100'.

- For long plans generated by the application profiling, extra information related to the optimization process is now dumped. For example, 'Plan [ Total Cost Estimate: 3.5657, Costed Best Plans: 1, Costed Plans: 13, Optimization Time: 0.074541, Estimated Cache Pages: 590 ]' This type of information is already present for long plans generated by calling the explanation() function.

- Information related to the cached plan of a statement is now dumped in its long plan.

- Predicates used to generate fence posts for a partial index scan are now dumped in the long plans generated by the application profiling. This type of information is already present for long plans generated by calling the explanation() function.

Also, graphical plans with statistics saved during tracing did not actually contain any statistics. This has been fixed.

1) The DBSC_Event structure now has a new integer field 'val3'. As with the other data fields in the structure, the meaning of the value in the val3 field depends on the type of event.

2) The event, DBSC_EVENTTYPE_DOWNLOAD_COMMITTED now has 2 parameters. In the DBSC_Event structure for the event, val1 contains the number of rows inserted or updated during the download. val2 contains the number of rows deleted by the download.

3) The new event, DBSC_EVENTTYPE_UPLOAD_START event has been added. The event is generated when dbmlsync begins to send the upload to the MobiLink server.

4) The new event DBSC_EVENTTYPE_UPLOAD_SENT event has been added. The event is generated when dbmlsync completes sending the upload to the MobiLink server. For synchronizations that use transactional or incremental upload (where the upload is sent as more than 1 segment) a separate UPLOAD_SENT event is generated after each segment is sent. In the DBSC_Event structure for the event, val1 contains the number of insert operations contained in upload, . val2 contains the number of update operations contained in the upload and val3 contains the number of delete operations contained in the upload.

5) The new event, DBSC_EVENTTYPE_DOWNLOAD_START event has been added. The event is generated when dbmlsync begins to process the download.

These event changes will apply to the C++ and .NET version of the API. They will also appear in the synchronize_results and synchronizae_parameters tables when the SYNCHRONIZE SQL statement is used.

All of these new events can be enabled/disabled by using the SetProperty method to set the 'enable status' property.

1) The server could have crashed or otherwise failed in rare cases when one or more read-only scale-out children were added to a node. This could have occurred if one node was stopped or restarted.

2) If a parent node was restarted and had a lower log offset than it's child, the child could have shutdown with the message "Database server shutdown due to incompatible files for database mirroring." Restarting the child node after the parent caught up to primary would succeed. Now the child node no longer stops and the child node will start applying log changes once its parent gets to a higher log offset.

3) If a parent copy node was started with child nodes already running, a child node and possibly other nodes could have hung.

4) If a copy node was connected to it's alternate parent, and then it's alternate parent stopped, the copy node may have stopped applying updates. The copy should have connected to the primary server to receive updates but was actually not receiving updates. Note that sa_mirror_server_status may show that the node which is not receiving updates is connected, when in fact it was not. Now the copy node will connect to the primary server if neither the parent nor alternate parent servers are available.

5) An ALTER MIRROR SERVER statement that only changed the alternate parent was ignored until the server being altered was restarted. For example, if ServerC had parent ServerB:

ALTER MIRROR SERVER 'ServerC' AS COPY FROM SERVER 'ServerB' OR SERVER 'ServerA'

was ignored by ServerC until it was restarted. Now the alternate parent is effective on the server being altered once it has applied the log offset with the ALTER MIRROR SERVER statement.

6) Attempting to SET MIRROR OPTION auto_add_server to the alternate server name for the primary server incorrectly resulted in an error.

7) If read-only scale-out copy nodes had a primary server as their root node, and the primary server failed over to the mirror server, then all client connections to all copy nodes were incorrectly dropped.

Also, on 12.0.0 for Windows, the cache could have failed to stabilise. This has also been fixed.

The following example routes an https request destined for 'securehost' (default port 443) through a proxy host named 'squid' listening on port 8080:

create or replace procedure test()

URL 'https://securehost/service'

TYPE 'HTTP:GET'

PROXY 'http://squid:8080';

Note that at least since version 10i, Oracle has recommended using Network Time Protocol (NTP) to synchronize the clocks on all nodes in a cluster, and NTP typically runs by default on Unix and Linux. With cluster nodes properly configured to use NTP, their clocks should all be within 200 microseconds to 10 milliseconds (depending on the proximity of the NTP server). Since Windows Server 2003, the Windows Time Service implements the NTP version 3 protocol and it runs by default. Also, as of version 11gR2, Oracle Clusterware includes the Oracle Cluster Time Synchronization Service (CTSS) to either monitor clock synchronization or, if neither NTP or Windows Time Service is running, it will actively maintain clock synchronization. However CTSS and Windows Time Service are less accurate than NTP,

To avoid missing rows when Oracle RAC node clocks differ by up to one second more than the time between fetching the next_last_download_timestamp and the rows to be downloaded, now the MobiLink server will subtract one second from the next_last_download_timestamp fetched from the consolidated database, if

1) the Oracle account used by the MobiLink server has execute permission for SYS.DBMS_UTILITY,

2) the consolidated database is an Oracle RAC system,

and (only for MobiLink version 12.0.0 and up)

3) there is no generate_next_last_download_timestamp script.

For Oracle RAC node clocks that may differ by greater amounts, you can avoid the problem by defining a generate_next_last_download_timestamp, modify_next_last_download_timestamp or modify_last_download_timestamp script to compensate for the maximum node clock difference.

A workaround is to use the Marquee Tool, or change the zoom to fix the display, or disable the Utilization Graph to prevent the problem.

- An index existed in which the first column (say col1) was specified to be in descending order

- The query contained a search condition of the form "col1 LIKE expression" where the expression started with non-wildcard characters.

- The query contained an ORDER BY starting with col1

This has been corrected.

- An index existed in which the first column (say col1) was specified to be in descending order

- The query contained a search condition of the form "col1 LIKE expression" where the expression started with non-wildcard characters.

- The query contained an ORDER BY starting with col1

This has been corrected.

-100 "Database server not found".

CASCADE 0

if referential action is NULL 1

SET NULL 2

SET DEFAULT and RESTRICT 3

These values, derived from the ODBC SQLForeignKeys result set, did not match the following OLEDB constants defined for these referential actions.

DBUPDELRULE_NOACTION = 0x0

DBUPDELRULE_CASCADE = 0x1

DBUPDELRULE_SETNULL = 0x2

DBUPDELRULE_SETDEFAULT = 0x3

Furthermore, the DBSCHEMA_FOREIGN_KEYS rowset should have returned strings rather than integers for the UPDATE_RULE or DELETE_RULE referential actions. The OLE DB specification states:

If a rule was specified, the UPDATE_RULE or DELETE_RULE value is one of the following:

"CASCADE" � A <referential action> of CASCADE was specified.

"SET NULL" � A <referential action> of SET NULL was specified.

"SET DEFAULT" � A <referential action> of SET DEFAULT was specified.

"NO ACTION" � A <referential action> of NO ACTION was specified.

Providers should return NULL only if they cannot determine the UPDATE_RULE or DELETE_RULE. In most cases, this implies a default of NO ACTION.

Also, the fix for Engineering case 620136 did not handle the situation when there was no declared Primary Key in the primary table but there were table or column (not nullable) Unique Constraints that permitted the addition of foreign keys.

These problems have been fixed. The Upgrade utility should be used to update the OLE DB schema rowset support in any database used with ADO, ADOX or OLE DB.

SELECT t.c FROM t WITH (UPDLOCK) WHERE t.pk = 1

UPDATE t SET c = 2 WHERE t.pk = 1

concurrently at isolation level 3, a deadlock would have occurred if both connections managed to issue the SELECT before either issued the UPDATE. This has been fixed.

For example:

select if T2.a2 is null then 99999 else 11111 endif as v011,

(select count(*) from T1 where T1.a1 = v011) as c

from T2,T3

where T2.a2 = T3.a3

group by v011

This has been fixed.

This issue had at least one other symptom: If a file was opened, "Options" for the editor was selected, either by right-clicking as described above or by opening the Options window, then clicked "OK", subsequent changes in the Editor would not have caused the Interactive SQL utility's window title text to include an asterisk. The asterisk indicates that there are unsaved changes in the editor.

Timeout: 3600 seconds

SendBufferSize: 1048576 bytes (1 MB)

ReceiveBufferSize: 1048576 bytes (1 MB)

Note, if a text index was created or updated using a server with this problem, it may be necessary to rebuild the index with an updated server if problems are encountered with the index.

No change in behavior from earlier builds of version 11 should be seen with this software change.

Before attempting to build the sample in Eclipse, ensure that the sub-directory names are as show below. Note that all names are lower case and that hyphens (-) should be used, not underscores (_), where applicable.

libs

res

src

libs\armeabi

res\drawable-hdpi

res\drawable-ldpi

res\drawable-mdpi

res\layout

res\menu

res\values

src\com

src\com\sybase

src\com\sybase\custdb

- the WHILE statement

- a list of DECLARE statements within a batch, procedure, function, or trigger

- UNSIGNED exact numeric types

This has been fixed.

The work-around is to rewrite

expression in ( ? )

as

expression = ?.

Note that this problem only affected remote requests from ASE to SQL Anywhere. The problem did not affect making remote requests from SQL Anywhere to ASE via Remote Data Access.

WARN/dalvikvm(641): ReferenceTable overflow (max=512)

...

ERROR/dalvikvm(641): Failed adding to JNI local ref table (has 512 entries)

...

ERROR/dalvikvm(641): VM aborting

The memory overflow condition would have occurred during a Connection.synchronize( SyncParms parms ) call, where a SyncObserver was defined in the SyncParms. This has been fixed.

Option DBA.Compression contains invalid value -1

The value -1 is a valid value, it was the blank padding that was causing the option to be treated as invalid. This problem has been fixed.

Similarly, in cases where a primary server lost its connections to both the mirror and arbiter servers as a checkpoint was performed, the next time the primary and mirror servers were connected and attempt to synchronize, the mirror server may have in rare situations reported "Database "<name>" mirroring: database is not compatible with primary; files must be replaced" and then stop with the message "Database server shutdown due to incompatible files for database mirroring". This has been fixed to reduce the possibility of this occurring. It is possible for this to still occur, so then the database running on the current primary must be manually copied or backed up to the mirror server so that the server can successfully synchronize again.

The primary server could have hung, again in rare situations, if only one of the two connections between it and the mirror server was dropped, for example due to a liveness timeout. This has been fixed.

When the mirror server was becoming the primary server there was a small possibility it could have hung after reporting it was starting a checkpoint and then reporting it was recovering. This has been fixed.

To workaround the problem, change this line in the generated batch file:

set CONNECTION=%1

to this:

set CONNECTION=%~1

Migrating SQL Anywhere Monitor database

Connecting...

Can't connect to source database.

[Sybase][JDBC Driver][SQL Anywhere]Specified database not found

Rolling back files in /opt/samonitor12 ...

wc: ./.ebf_20110601-1149/samonitor.db: Permission denied

Cleaning up ...

This has been fixed so that the following error message is now displayed:

The setup program was unable to stop a running instance of SQL Anywhere Monitor.

Please stop it manually and run the setup program again.

A workaround is to stop the SQL Anywhere Monitor service manually, then re-run the EBF installer.

Alternatively, the driver can be registered manually using the following command:

regsvr32.exe %SQLANY12%\Bin64\ulodbc12.dll

ERROR! Could not load the Java virtual machine DLL: /opt/sqlanywhere/sun/jre160_x86/lib/i386/client/libjvm.so

This has been fixed. A workaround is to run "setenforce 0" as root.

For example, the following query would not report an error and would behave as if the

full text query was 'apple NEAR[2] oranges':

SELECT *

FROM t CONTAINS( 'apple NEAR[ 2b ] oranges' )

Note that the following query was correctly reporting an error:

SELECT *

FROM t CONTAINS( 'apple NEAR[ b ] oranges' )

For example:

Select *

from T1, T2

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

The predicate "T1.X = (select e1 from R where p(R,T1, T2) )" has a subselect and references both tables T1 and T2 from the main query block.

[preferences]

directory={preferences files directory|

where "preferences_files_directory" is a fully-qualified directory name, e.g. "c:\work\prefs". The directory name should not end in a separator (backslash on Windows; forward slash on Unix and Mac OS X).

Preferences files include:

.isqlPreferences12_32

.isqlPreferences12_64

.isqlHistory12

.jlogon12

.textCompleter12

.SybaseCentralEditor610

.scUserPreferences610_32

.scUserPreferences610_64

among others.

In rare cases, UltraLite incorrectly computed where to resume the download. When this occurred, the subsequently resumed download was effectively corrupted, likely causing a synchronization error. (To recover, the download must have been rolled back.)

When resuming a download, the server continued to use the original 'timeout' specification, but UltraLite used the default. If a non-default timeout value was specified, the resumed download may have timed out even though the network connection was fine (though it still maked progress).

Sometimes the sync-info (or sync-result) 'partial_download_retained' flag was false after trying to resume a download when there was still a partial download present. (Workaround is to only make use of this flag when first set - attempting to subsequently resume when there is no partial download is safe and returns an error.)

As well, the following problem is fixed:

The COMMITTING_DOWNLOAD sync observer state was signaled later than it should have been. The observer saw UltraLite was still receiving the download, when in fact it had begun committing the download.

A similar problem affected the TLS packet encryption parameters on the Network page.

Both of these problems have now been fixed.

servers. This has been fixed so that servers can now recover logs that exhibit this problem.

1. On the "General" panel in the Options window, the first group box title was changed from "Command Files" to "SQL Script Files" and the first checkbox, "Echo command files to log" has been renamed "Echo SQL script files to log".

2. The "Commands" tabs in the Options window (there are three of them: one for SQL Anywhere, one for UltraLite, and one for IQ) have been renamed from "Commands" to "Execution".

3. The command-line help now clearly refers to SQL statements as "statements" rather than "commands".

4. The "Command History" window has been renamed "History"

E. 2011-03-14 08:33:50. Error registering with DBLSN code: -1

The error message was displayed in a message box, even when qaagent was executed in quiet mode. This has been fixed. Now, qaagent is more tolerant to dblsn slowness at startup. Also, a message box is not displayed when qaagent is executed in quiet mode (-q or -qi), and the message is logged in the qaagent console and log file.

1) The server would not have been recognized on the second sync that the same remote was synchronizing and would treat the second sync as a first sync. That is to say the server would not have used state information it had from the first sync when processing the second. Third and subsequent sync's were not affected. This would have had no impact unless the first synchronization had failed.

2) Two entries would have been made in the ml_database table for each remote. One would contain the blank padded remote id and the other would contain the unpadded id.

This behaviour has now been fixed. Now, on first synchronization the remote_id assigned to the remote database will be blank padded.

1. The driver name for the data source was always "SQL Anywhere 12" rather than "Sybase IQ". This prevented the data source from being listed in the "Data Source Names" window unless you checked "Show all data sources". Also, to connect using the data source, the SQL Anywhere ODBC driver had to be installed.

2. Creating a system data source would fail on machines that did not have "dbdsn" installed. This would be a problem on computers running Vista or Windows 7 which have IQ installed, but not SQL Anywhere.

CREATE SERVER remote-server CLASS 'saodbc' USING 'driver=SQL Anywhere Native;...'

where the the USING clause contains the key pair "driver=SQL Anywhere Native", and the remainder of the USING clause provides all the connection parameters necessary to successfully connect to the remote SQL Anywhere server, then the remote data access layer will load the SQL Anywhere ODBC driver directly and bypass the Windows ODBC Driver Manager on Windows based platforms and the SQL Anywhere ODBC Driver Manager on UNIX platforms. The benefit to loading the SQL Anywhere ODBC driver directly is that, although the ODBC driver still needs to be installed, it no longer needs to be registered if it is only being used for the remote data access support. What's more, if there are multiple copies of the ODBC driver installed, then loading the ODBC driver directly will guarantee that the ODBC driver for the current server version gets used rather than one that was registered with a previous version of SQL Anywhere. It should be noted that if the application also makes use of non-SQL Anywhere remote servers or if there are SQL Anywhere remote servers defined without the "driver=SQL Anywhere Native" key pair, then the remote data access layer will still use a Driver Manager for those other remote servers.

The workaround for this problem is to use the SQL->Stop menu item, which always works.