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

47 scandict

48 scannocp

58 rusdict

59 rusnocs

63 cyrdict

64 cyrnocs

65 elldict

69 hundict

71 hunnocs

70 hunnoac

72 turdict

74 turnocs

73 turnoac

1 thaidict

This has been corrected so that appropriate keys are now generated. It is highly recommended that any columns which store SORTKEY values using these collations be recomputed, as comparisons and sort order will be affected.

select 11 % 2

would have incorrectly reported an error, instead of the correct result of 1 being returned. This has been fixed.

In addition, when editing a column in the table editor or Column property sheet, or creating a domain or function in the corresponding wizards, it was possible to specify a size value that would exceed the database maximum (32767/maximum_character_length for CHAR and VARCHAR; 8191 for NCHAR and NVARCHAR). This problem has also been fixed.

Because Ultralite error callback is active during the upgrade process, the application is notified of errors during the conversion process. For example, SQLE_CONVERSION_ERROR reports all values that could not be converted in its parameters. Errors do not mean the process failed. The final SQL code after the statement returns is a 130 warning in this case. These warnings describe operations of the conversion process and do not stop the upgrade process.

Note: There is no mechanism to support the renaming of tables, columns or publications. Also, renaming a table is processed as a DROP TABLE and CREATE TABLE operation.

Caution: Resetting the device during the upgrade process leaves the database unusable.

To upgrade the schema with this new statement:

1. Define a new schema by creating a SQL script of DDL statements. The character set of the SQL script file must match the character set of the database you want to upgrade.

The UltraLite utilities ulinit or ulunload can be used to extract the DDL statements required for this script. Use these utilities to ensure that the DDL statements required are syntactically correct.

- For ulunload, use the 杗 and 杝 [file] options.

- For ulinit, use the 杔 [file] option.

See the UltraLite Database Management and Reference documentation for details.

2. Review the script and ensure that:

- That non-DDL statements have not been included. Including non-DDL statements does not have the expected effect.

- Words in the SQL statement are separated by spaces.

- Only one SQL statement can appear in each line.

- Comments are prepended with '--' and only occur at the start of a line.

3. Backup the existing database.

4. Run the new statement using the following syntax:

ALTER DATABASE SCHEMA FROM FILE �<filename>�

For example:

ALTER DATABASE SCHEMA FROM FILE 'MySchema.sql'

5. The existing database is upgraded with the new schema using the following process:

- Both the new and existing database schemas are compared to see what differs.

- The schema of the existing database is then altered accordingly.

- Rows that do not fit the new schema are dropped. When this occurs, a SQLE_ROW_DROPPED_DURING_SCHEMA_UPGRADE (130) warning is raised.

For example, if a uniqueness constraint was added to a table, and there are multiple rows with the same values, all but one row will be dropped.

Alternately, if an attempt to change a column domain causes a conversion error, then that row will be dropped. That is, say a VARCHAR column is converted to an INT column, if the value for a row is 揂BCD�, then that row is dropped.

Lastly, if the new schema has new foreign keys where the foreign row doesn't have a matching primary row, these rows are also dropped.

If dropping rows is not the desired behavior of the schema upgrade, detect the warning and restore from backup.

Login procedure 'sp_login_environment' caused SQLSTATE '0AW04'

Triggers and procedures not supported in runtime server

This has been corrected so that the runtime server will no longer attempt to invoke the login procedure.

A workaround would be to execute:

set PUBLIC.login_procedure=''

To take advantage of this optimization, you should now define your publications as disjoint (not sharing any tables) whenever possible. This will result in a major performance improvement when one subscription is being synchronized more frequently than another.

For example, suppose publications P1 and P2 share no tables. P2 is synchronized daily and P1 is synchronized hourly. Each time P1 is synchronized, its progress is advanced by 1000. The following table shows the segment of log scanned for each synchronization based on the old and new behavior:

log scanned log scanned

Action P1's progress P2's progress (old behavior) (new behavior)

sync P1 1000 1000 1000-2000 1000-2000

sync P1 1000 2000 1000-3000 2000-3000

sync P1 1000 3000 1000-4000 3000-4000

sync P1 1000 4000 1000-5000 4000-5000

You should be able to define your publications as disjoint except where two publications contain the same table but with different WHERE clauses. Defining disjoint publications should never limit functionality because the dbmlsync -n option can accept a comma separated list of publications which causes the union of the publications to be synchronized.

For example, suppose table T1 is to be synchronized throughout the day, and tables T1 and T2 are to be synchronized at the end of the day. Previously, you might have defined your publications as follows:

- P1 contains T1

- P2 contain T1 and T2.

- Synchronize during the day with the dbmlsync option -n P1

- Synchronize at the end of the day with the dbmlsync option -n P2

In order to take advantage of the new optimization, two publications should be defined: P1 contains T1, and P2 contains T2. During the day dbmlsync will synchronize using the -n P1 option. At the end of the day dblmsync will synchronize using -n P1,P2. This does the same thing, but is much more efficient with the new log scanning behavior.

... Failed to start QAnywhere Agent (register with DBLsn)

... Error registering with DBLSN code: -1

This was due to the MobiLink Listener crashing, and has been fixed.

Note, this problem affected the Interactive SQL utility, DBConsole, and the MobiLink Monitor as well, which have also been fixed.

SQLAllocHandle( ..., SQL_HANDLE_STMT, ...) (returns SQL_SUCCESS)

SQLExecDirect( ..., "select ...", ... ) (returns SQL_SUCCESS)

SQLExecDirect( ..., "insert...", ...) (returns SQL_ERROR)

SQLFreeStmt( ..., SQL_UNBIND) with the same statement handle.

The number of columns of the result set was not reset to zero when the same statement handle was reused. This problem has now been fixed.

stmt.setTimestamp( pnum, new java.sql.Timestamp(System.currentTimeMillis()) );

executing the INSERT statement would have failed with a SQLE_CONVERSION_ERROR. The microseconds were not scaled into nanoseconds, and vice versa. This has been fixed.

For example "mlsrv10 -sl java ( opt1 ) -sl java (opt2 ) ..." now correctly parses as "mlsrv10 -sl java( opt1 opt2 ) ..."

For example, the following should return 1 row, but did not return any rows:

create table T1 ( d int, e int, f char(5) ,g char(5) );

insert into T1 values ( 5, 2, '4E', 'N' );

select * from T1

where ( d is not null or d is NULL )

and ( e = 2 or e is NULL )

and ( g <> 'Y' or g is null )

and e = 2

This has been fixed.

Note, this fix now makes it easier to paste data from dbisql into Excel: Set the default field delimiter to a tab ("\t" -- a backslash followed by the lower-case letter T), then copy the data from the table in the usual way.

A workaround would be to use the BACKUP DATABASE statement with the TRANSACTION LOG TRUNCATE clause to truncate the log.

After executing a SETUSER WITH PERMISSIONS userid statement, some of the current options for userid may not be respected. Similarly, the next SETUSER command which should have set the options back, may have caused the original options to not be respected.

Both of these problems have now been fixed.

I. 2007-04-11 11:21:54. There are 23 processes running

This is useful in diagnosing problems on Windows CE devices with Windows Mobile 5, and previous OSes, because there is a fixed limit of 32 processes that can be running at once. After that, the OS will start shutting down applications in a not completely deterministic way.

On Windows, the -qw switch now completely suppresses the creation of the server window. As before, a systray icon is created but that icon is now created immediately upon startup. Previously, a minimized server window was created momentarily before the systray icon was created. In 9.0.2, the menu for the systray icon allowed the user to open the server window via the "Restore" menu item but "Restore" has now been disabled (which is consistent with 10.x & the fact that -qw is supposed to prevent the creation of a server window).

On UNIX, the -qw switch suppresses all messages from going to the console after the 'press q to quit' message has been displayed.

Note, in general it is good practice to insure that no version 10 server is running when rebuilding databases prior to version 10.

A workaround is to specify the undocumented dbunload options -so and -sn, to set the options for the unload and reload servers respectively, as follows:

dbunload -so " -ch 40p" -sn " -c 40p" ...

Note the space before the -c switches, these are required. Mnemonic: -so sets the additional switches for the "Old" server, -sn sets the additional switches for the "New" server.

For .NET applications, the SQLCA limit also represents the database connection limit, since a new sqlca is used for each connection. Also, an internal SQLCA is used by each .NET application, so the effective connection limit for .NET apps is 63 minus the number of running .NET clients.

Note that the runtime's connection limit is 64.

select xmlelement( name e, IF 1=1 THEN cast( '<e1/>' as xml ) ELSE '' ENDIF )

A workaround to avoid the quoting without the fix is to make all branches of the IF the same type:

select xmlelement( name e, IF 1=1 THEN cast( '<e1/>' as xml ) ELSE cast( '' as xml ) ENDIF )

1. The -gi option controls the ip tracker polling interval. The default is 10 seconds.

example: dblsn.exe -gi 30

2. The -ga option is for asynchronous ip tracking. The -gi option is ignored when -ga is used.

example: dblsn.exe -ga

By default, the MobiLink server now queries the minimum transaction starting time from master..systransactions and then sends this timestamp to the client as the last download timestamp. In the next synchronization for this client, the MobiLink server will use this timestamp as the last download time for download. In order to get the starting time, the user ID the MobiLink server uses to connect to an ASE server must have select permission and the master..systransactions table. If the user does not have proper permissions, the MobiLink server will present a

warning message and get the download time from the ASE function getdate(), reverting to the old behaviour where rows could be missed in the download. With this change, it's now possible that the MobiLink server may send duplicate data to clients, if there are any open transactions that modified any tables in the synchronization database or any databases on the ASE

database server when MobiLink server is doing a download. Although the clients are able to handle duplicate data, this behavior may reduce MobiLink server performance.

The MobiLink server now includes two new command line switches so you can the behaviour of the MobiLink server with respect to tables with the 'datarows' locking scheme. The -dr switch can be used to tell MobiLink that none of the synchronizing tables use the 'datarows' locking scheme. The -dt switch can be used to force MobiLink to detect transactions only within the current database when determining the last download time that will be sent to the remote database. The -dt switch should be used if all the synchronizing tables are located in a single database, as this could reduce duplicate data sent by the MobiLink server to the clients.

By default, the MobiLink server now queries the minimum transaction starting time from master..systransactions and then sends this timestamp to the client as the last download timestamp. In the next synchronization for this client, the MobiLink server will use this timestamp as the last download time for download. In order to get the starting time, the user ID the MobiLink server uses to connect to an ASE server must have select permission and the master..systransactions table. If the user does not have proper permissions, the MobiLink server will present a warning message and get the download time from the ASE function getdate(), reverting to the old behaviour where rows could be missed in the download. With this change, it's now possible that the MobiLink server may send duplicate data to clients, if there are any open transactions that modified any tables in the synchronization database or any databases on the ASE database server when MobiLink server is doing a download. Although the clients are able to handle duplicate data, this behavior may reduce MobiLink server performance.

The MobiLink server now includes a new command line switch so you can the behaviour of the MobiLink server with respect to tables with the 'datarows' locking scheme. The -dr switch can be used to tell MobiLink that none of the synchronizing tables use the 'datarows' locking scheme. The -dt switch on the MobiLink server has also been enhanced to include Adaptive Server Enterprise in addition to Microsoft SQL Server. The -dt switch can be used to force MobiLink to detect transactions only within the current database when determining the last download time that will be sent to the remote database. The -dt switch should be used if all the synchronizing tables are located in a single database, as this could reduce duplicate data sent by the MobiLink server to the clients.

For example:

declare @var long varchar;

declare @counter integer;

set @counter = 1;

set @var = space(30);

calcloop:

WHILE @counter < 100000 LOOP

set @var = 'string' || @var;

set @counter = @counter + 1;

END LOOP calcloop;

The error did not occur if only the left hand argument of a concatenation expression was a concatenation expression, i.e., set @var = @var || 'string';

This has been fixed.

Note that in most cases the script sa_config.sh or sa_config.csh, that is included in the install, is used to set the environment for SQL Anywhere. When sa_config is used, both SHLIB_PATH and LD_LIBRARY_PATH are set, and hence SQL Anywhere will be able to find any libraries it requires. If sa_config is not used, users should work around this issue by

setting both SHLIB_PATH and LD_LIBRARY_PATH.

... Communication error occurred while sending data to the MobiLink server

... Internal error (???!s).

... Communication error occurred while sending data to the MobiLink server

... Unspecified communication error

This problem was most likely to have occurred when a slow network was being used. With a slow network, dbmlsync could have become blocked on a network write. which prevented the sending of a liveness message. To correct this problem, dbmlsync will no longer attempt to send liveness messages when it is blocked on a write.

A possible workaround for this problem would be to use the timeout communication parameter to increase the liveness timeout.

Note, this also addresses the problem where deleting a column from a table via the ALTER TABLE statement would have caused a syntax error for values that already existed in other columns.

sa_dependent_views

sa_get_dtt

sa_check_commit

sa_materialized_view_info

Note that the issue of time zone independence with QAnywhere has not been completely addressed. All time values used in transmission rules refer to local time. Also, the special variable ias_StatusTime, used in transmission rules, refers to local time.

A work around has been added to the SQL Anywhere OLE DB provider such that a request to release a rowset when no rowset exists will be ignored. The following VBScript sample will fail on 64-bit Windows Vista without the provider workaround:

query = "SELECT * FROM Employees"

Set recordset = connection.Execute(query)

For Each field in recordset.Fields

WScript.Echo field.Name

propCount = 0

For Each prop in field.Properties 'crashes on 64-bit Vista

...

Next

Next

For example, the following script would have caused a server hang:

CREATE TABLE T1 (

x char(4) NOT NULL,

y char(13) NOT NULL,

z char(5) NOT NULL,

);

CREATE TABLE T2 (

w char(5) NOT NULL,

);

SELECT a.x as x, a.y as y,

count(b.w)

FROM T1 a,

T2 b

WHERE a.z = b.w

Group by a.y, a..x ; -- Note extra '.'

Now, the server will generate an error if a query contains a column expression of the form

"IDENTIFIER" .. "IDENTIFIER"

or

"IDENTIFIER" . "IDENTIFIER" .. "IDENTIFIER".

Note that the ml_global property can be over-ridden with a script version specific property, similar to the way connection scripts work.

ignoring column subset for publication 'PUB', table 'T' -- all columns will be added

Actually, the column subset was being used to build the UltraLite table, it's just that columns not in the subset were being properly excluded from the UltraLite table schema. The message was intended to warn the user in regard to synchronization publications, as UltraLite always synchronizes all of the rows of a table that is specified in a sync publication. Part of the confusion is due to overloading the concept of a publication as a set of tables plus columns to be included in the schema, with the concept of a publication as a set of tables to be synchronized. In order to make this clearer, the warning has been changed to:

ignoring column subset for synchronization publication 'PUB', table 'T' -- UltraLite synchronizes entire rows"

See also Engineer case 443016

Note that the fix requires both an updated server and updated client library.

updates to Mac OS X, specifically Security Update 2007-004. The applications would either have crashed, or displayed a message similar to the following:

The library dbput9_r could not be loaded. This may be because the provider is being re-loaded (in which case you need to restart the viewer) or because the library could not be found in the Adaptive Server Anywhere installation. Service management will not be available.

or:

Link (dyld) error: Library not loaded: libdbserv9_r.dylib Referenced from: /Applications/SQLAnywhere9/System/bin/dbsrv9 Reason: image not found

This has been corrected.

Note that BETWEEN predicates involving subqueries also qualify as they are interpreted as two compare predicates (see example below).

Example:

select s_suppkey,

s_name,

s_address,

s_phone,

total_revenue

from supplier, revenue1

where s_suppkey = supplier_no

and ( select max(total_revenue)

from revenue1

) between (total_revenue-0.01) and (total_revenue+0.01)

order by s_suppkey

Note that a QAnywhere message in the server database with an expiration date, that is not delivered to the client device before it expires, will also transition to an expired state and be deleted by the default server delete rule. This was the case before this change.

The following is the documentaion update:

MobiLink now supports two modes of download acknowledgement: blocking and non-blocking. Prior to this change, MobiLink only supported blocking download acknowledgement. When you turn on download acknowledgement, the default continues to be blocking.

Note: Download acknowledgement is not on by default. To turn it on, use the dbmlsync "SendDownloadACK" extended option or the UltraLite "Send Download Acknowledgment" synchronization parameter. Download acknowledgement is not required to ensure that data is successfully downloaded. Download acknowledgement simply allows you to get acknowledgement of a successful download immediately (in the download); otherwise the acknowledgement occurs in the next upload.

To set non-blocking download acknowledgement, use the new mlsrv10 option -nba+.

Non-blocking download acknowledement is recommended because it provides a significant performance advantage over blocking download acknowledgement. However, non-blocking download acknowledgement cannot be used in the following cases:

- Clients prior to 10.0.0 do not support non-blocking acknowledgement.

- You cannot use non-blocking acknowledgement with the Notifier scripts that are generated by MobiLink Model mode.

QAnywhere messaging uses non-blocking download acknowledgement. You cannot change this setting for QAnywhere: You will get an error if you specify both -m and -nba- on the mlsrv10 command line.

To provide extra optional functionality to the new non-blocking download acknowledgement, two new MobiLink events have been added: nonblocking_download_ack and publication_nonblocking_download_ack.

nonblocking_download_ack connection event

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

Function: When using non-blocking download acknowledgement, this event lets you update your database based on the successful application of the download.

Parameter name Description Order

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

s.remote-id VARCHAR(128) N/A

s.username VARCHAR(128) 1

s.last_download TIMESTAMP 2

This event is only called when using non-blocking download acknowledgement. When in non-blocking mode, the download transaction is committed and the synchronization ends when the download is sent. This event is called when the synchronization client acknowledges a successful download. This event is called on a new connection, after the end_synchronization script of the original synchronization. The actions of this event are committed along with an update to the download time in the MobiLink system tables.

Due to the special nature of this script, any connection-level variables set during the synchronization are not available when this event is executed.

For example, the following script adds a record to the table download_pubs_acked. The record contains the remote ID, first authentication parameter, and the download timestamp.

INSERT INTO download_pubs_acked( rem_id, auth_parm, last_download )

VALUES( {ml s.remote_id}, {ml a.1}, {ml s.last_publication_download} )

publication_nonblocking_download_ack connection event

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

Function: When using non-blocking download acknowledgement, this event lets you update your database based on the successful application of the download of this publication.

Parameter name Description Order

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

s.remote-id VARCHAR(128) N/A

s,username VARCHAR(128) 1

s.last_publication_download TIMESTAMP 2

s.publication_name VARCHAR(128) 3

s.subscription_id VARCHAR(128) 4

This event is only called when using non-blocking download acknowledgement. When in non-blocking mode, the download transaction is committed and the synchronization ends when the download is sent. When the synchronization client acknowledges a successful download, this event is called once per publication in the download. This event is called on a new connection and after the end_synchronization script of the original synchronization. The actions of this event are committed along with an update to the download time in the MobiLink system tables.

Due to the special nature of this script, any connection-level variables set during the synchronization are not available when this event is executed.

For example, the following script adds a record to a table called download_pubs_acked. The record contains the publication name, the first authentication parameter, and a download timestamp:

INSERT INTO download_pubs_acked( pub_name, auth_parm, last_download )

VALUES( {ml s.publication_name}, {ml a.1}, {ml s.last_publication_download} )

Note that the menu items and accelerator keys corresponding to the toolbar buttons were enabled correctly and were functional.

A workaround is to zero out the allocated SQLCA memory after allocating it and before calling db_init. The allocated SQLCA (say app_sqlca) can be zeroed out using:

memset( app_sqlca, 0, sizeof( SQLCA ) )

Note, in general blocking is still allowed when snapshot transactions do updates or deletes (unless the "blocking" option is off). This change only gives the conflict error earlier in some restricted cases.

qaagent.exe: 64 KB

dblsn.exe: 64 KB

dbmlsync.exe: 128 KB

Previously, 1MB per thread of address space was reserved, while only a portion was actually allocated, or "committed".

qaagent -c "...;startline=\Program Files\Sybase\ASA9\dbsrv9 -o dbsrv.txt -c 20m -gd all -gp 4096 -n qanywhere -gk all -qw -gn 10"

then it would have failed to start the database server with the error "InternalError: Unable to start database server". A problem with passing double quotes in the connection string has been fixed.

For example:

public WSResult AsyncCategoryBrowseResponseResponse CategoryBrowse(CategoryBrowseRequest request) // incorrect

should be:

public WSResult AsyncCategoryBrowse(CategoryBrowseRequest request) // correct

A problem with the generation of asynchronous C# method signatures has been corrected.

A workaround to this issue would be to unload and reload the schema and/or the database.

SELECT * FROM table1, some_procedure( ROWID( table1 ) )

The behaviour of such a function call was undefined; a query containing an illegal outer reference may have returned unintuitive or inconsistent results. This has been corrected so that the server now correctly returns an error when the ROWID() function is called with an illegal outer reference as an argument.

will see the error SQLE_DB_ALIAS_RESERVED_UTILDB (-985) "The database name 'utility_db' is reserved for the utility database."

Self-registering DLLs, such as the ODBC driver or the dbctrs perfmon plugin DLL, could also have shown a minimized command-shell window, but it was very short-lived.

Both these problems have now been corrected

StartLine="\Program Files\uleng10.exe"

This problem has been fixed.

This problem can be worked-around by making the opening quote the second character:

StartLine=\"Program Files\uleng10.exe"

or by enclosing the entire quoted value in single quotes:

StartLine='"\Program Files\uleng10.exe"'

Note, the following forms of comments are recognized:

-- (two hyphens)

// (two forward slashes)

/* */

The first two forms cause the script text to be ignored until the end of a line.

The last form causes all text between the "/*" and "*/ to be ignored. This form of comment cannot be nested.

Any other type of vendor specific comment will not be recognized and should not be used to comment out references to a named parameter.

- sa_rowgenerator

- sa_report_blocking

- sa_lockinfo

- sa_report_deadlocks

- sa_performance_diagnostics

- sa_performance_statistics

Note, this problem could also have occurred with embedded SQL applications, and is now fixed as well.

For example:

create table T1 ( pk int primary key, a int, b int );

select * from T1 where pk=1 and a=b;

This has been fixed.

For example, navigating to the Data tab for the following table definition would have caused Sybase Central to crash:

CREATE TABLE t1

(

c INTEGER NOT NULL,

CONSTRAINT "cn" PRIMARY KEY("c" ASC)

This problem has now been fixed.

For example:

IF count(n) > 50 THEN 'good' ELSE 'bad' ENDIF

This has been corrected.

1. The "Edit/Copy" menu item is now enabled if a results table has focus and at least one row is selected.

2. If the Results panel is selected, the "Edit/Paste" menu item is no longer enabled.

3. If a results table was focused, the "Edit/Delete" menu item could have been clicked, but nothing would have happened. Now, the menu item will cause the row to be deleted, the same as if the DELETE key had been pressed.

4. The "Cut", "Undo", "Redo", "Find/Replace", "Find Next", and "Go To" menu items are now enabled only if the "SQL Statement" field has focus. Previously, they were enabled even if the "Results" panel was selected.

grant execute on dbo.sa_proc_debug_version to sa_debug

go

grant execute on dbo.java_debug_version to sa_debug

go

Note, it is recommended that when using -ac that the destination database have default dba credentials. The password can then be changed after dbunload completes.

- the SOAP service was created with DATATYPE ON or IN, specifying that parameter types are to be mapped from SQL to XMLSchema data types (rather than exclusively to xsi:string),

- one or more parameters within the stored procedure called by the SOAP service were (SQL) XML data types.

This has been fixed. VARCHAR, LONG VARCHAR, and XML are mapped to XMLSchema type STRING (xsi:string). Most client toolkits including the SQL Anywhere SOAP client will automatically HTML_ENCODE data types that map to xsi:string.

Request from "UL 10.0.0.2862" for: ...

BEFORE UPDATE triggers should fire if a column in the column-list appears in the SET clause of the associated UPDATE statement, while AFTER UPDATE triggers should fire if the value of a column in the column-list has been modified by the UPDATE statement.

A positioned update would have caused all BEFORE UPDATE and AFTER UPDATE triggers to fire regardless of whether a column in their column-list appeared in the SET clause or was modified by the update. Further, if a searched update included all columns in the SET clause, but did not modify the value of any column, AFTER UPDATE triggers would have been fired inappropriately.

This has been fixed.

Request from "Dbmlsync Version 11.0.0.1036 Debug Internal Beta" for: remote ID: e08b39d1-e3fa-4157-969b-8d8679324c00, user name: template_U1, version: template_test

instead of lines like this:

Request from "MLSync" for: remote ID: 45ef79ab-195e-4f76-805b-95eef2773e8f, user name: template_U1, version: template_test

*** ERROR *** Assertion failed: 106104 (...) Field unexpected during compilation (SQLCODE: -300; SQLSTATE: 40000)

This has been fixed.

Note, multi-byte characters are supported in UDP notifications, but SMS notifications are restricted to 7-bit ascii.

Run time SQL error -- *** ERROR *** Assertion failed: 106105 (...)

Unexpected expression type dfe_PlaceHolder while compiling [-300] ['40000']

For example, the following statement could cause this error.

with recursive Ancestor( child) as

( (select row_num from rowgenerator R1 where R1.row_num = 1 )

union all

(select R2.row_num+100

from Ancestor, rowgenerator R2

where Ancestor.child = R2.row_num

)

)

SELECT *

FROM sys.dummy D1, Ancestor

for read only

In the case of this error, the server would continue to process other statements (a non-fatal assertion failure). This has been fixed.

To turn on IIS5 isolation mode on a IIS6 server using the IIS Manager, right click on IIS Manager->Web Sites and select Properties. Bring up the Service page and select the "IIS 5.0 isolation mode".

http://downloads.sybase.com/swd/detail.do?baseprod=144&client=ianywhere&relid=10260

To install this JRE:

Download and run SA_1001_JRE_UPD.exe. The install will locate an existing SQL Anywhere 10 installation, and install a Java Runtime Environment for x64.

To install the x64 MobiLink server:

1) Install the EBF normally on a x64 computer, and then go to Add/Remove Programs (Programs and Features in Vista), select SQL Anywhere 10 and click on the Change button.

Check that Modify is selected and click on the Next button.

2) The Select Features dialog will appear and it will show the MobiLink for x64 features under "MobiLink". 32 bit MobiLink features will be displayed under "MobiLink (32 bit)".

Check the checkboxes for MobiLink to install MobiLink for x64 and click on the Next button.

3) Click the Next button on the next dialog to implement the modifications.

4) Click the Finish button on the last dialog to complete the installation.

iAnywhere Solutions 9 - DB2 Wire Protocol

iAnywhere Solutions 9 - Oracle Wire Protocol

iAnywhere Solutions 9 - Sybase ASE

These drivers are now deprecated, although they will continue to be tested to make sure MobiLink and other components still work with them. If a problem is encountered with one of these drivers that cannot be worked around, a fix cannot be made, the options are to directly use a recommended third-party ODBC driver (see http://www.sybase.com/detail?id=1011880), or to move to version 10.0.1 or higher. The aforementioned link will be updated, recommending:

- An IBM ODBC driver for DB2

- Our own (iAnywhere Solutions 9 - Oracle) ODBC driver for Oracle (now shipping with 9.0.2 as of this change)

- A DataDirect ODBC driver for ASE

Also, note that there are two errors in the documentation. Under UltraLite � Database Management and Reference/Working with UltraLite Databases/Working with UltraLite publications/Publishing a subset of rows from an UltraLite table, the following are incorrect:

"Palm OS: You cannot use a CREATE PUBLICATION statement with a WHERE clause on this platform."

In fact, a WHERE clause can be used on Palm OS.

The paragraph "What you cannot use in a WHERE clause"

In fact, you can use columns from tables not in the article (or even not in the publication). You can also use subqueries.

set option public.global_database_id=1;

set option public.global_database_id=0;

For example, the following batch would have returned 12.34 and 12.34000, now the two values should both be 12.34000:

begin

declare @num numeric(10,5);

declare @str char(20);

set @num = 12.34;

set @str = @num;

select @str, cast( @num as char(20) );

end

Further, the data type of division in the NUMERIC/DECIMAL domain could have been incorrect for a non-SELECT statement. This has been fixed as well.

Run time SQL error -- *** ERROR *** Assertion failed: 106105 (...)

Unexpected expression type dfe_PlaceHolder while compiling (SQLCODE: -300; SQLSTATE: 40000)

For example, the following query demonstrates this problem:

SELECT *

FROM SYS.dummy D1

LEFT JOIN

( select c1

from ( select distinct D2.dummy_col, 31337 c1

from dbo.rowgenerator R1 , sys.dummy D2

) DT1

) DT2

ON (D1.dummy_col=DT2.c1-31337)

This has now been fixed.

Distributed transaction has significant performance overhead. It is recommand to use database transactions for non-distributed transactions.

For example, the following statement could exhibit this problem:

select *

from sysdomain D1 left join sysdomain D2 on D1.type_id = D2.type_id and 0 = ( select D1.type_id - D2.type_id from sys.dummy )

Assertion failed: 102501 (...) Work table: NULL value inserted into not-NULL column

For example, the following statement could cause this problem:

with D(c1,c2) as (

select row_num-1, 0

from dbo.rowgenerator R1

where R1.row_num <= 101

union all

select 123456789, 0

from sys.dummy where 1=0

)

select D1.c1, D1.c2 * 23 x, D2.c1

from D D1 left join D D2 on D1.c1 = D2.c1 and D2.c1 = 3 and x - D2.c2 = 0

This has been fixed.

Assertion failed: 106105 (...) - Unexpected expression type dfe_FieldOrigRid while compiling

For example, the following query could have generated this problem:

SELECT T1.col1

FROM

( select NULL col1, row_num col2,

(select dummy_col from sys.dummy ) col3

from dbo.rowgenerator

) T1

FULL JOIN

( select dummy_col c1, dummy_col+1 c2

from sys.dummy D1

) T2

ON (T1.col2=T2.c1) AND (T1.col3=T2.c2)

This has been fixed.

in the corresponding remote table, and the handle_error or handle_odbc_error script returned 1000 when these errors occurred. This problem has been fixed. The MobiLink server will now abort the synchronization if any of these unrecoverable errors

occur during synchronization. The errors in the user-defined scripts must be fixed.

NOTE that there is no problem if the remote data access class is ODBC based.

Note: this problem occurs when processing <row> elements contained within <SimpleDataset> elements in result sets returned by SQL Anywhere SOAP services.

The first problem was that updating a row in P that was referenced by F would not have generated the necessary foreign key violation error. This would have lead to rows in F with no corresponding row in P. Note that this wasn抰 a problem when referencing primary keys because primary keys should not be updated in UltraLite.

The second problem occurred when the foreign key from F to P was declared as CHECK ON COMMIT. When a row was deleted from P, temporarily violating RI, but a new row was added before the transaction was committed that kept RI in tact, an error would still have been raised. Since the foreign key was declared as CHECK ON COMMIT, the error should not have occurred.

Both of these problems have been fixed.

As a workaround, a driver manager such, as unixODBC, can be installed, or the ODBCINI environment variable can be set to point to the DSN file in question. The second work around would require the FileDSN parameter to be changed to DSN.

For example, the following statement could have exhibited this behaviour:

SELECT row_num

FROM rowgenerator R2

WHERE

( SELECT sum( 1 )

FROM sys.dummy D1

WHERE D1.dummy_col = R2.row_num

) >= 0

This has been fixed.

A workaround is to disable client statement caching for the connection by setting the max_client_statements_cached temporary option to 0.

Example:

The derived table T4 contains a subselect "( select dummy_col from sys.dummy T2 where 1 = T3.row_num ) as c1". T4 is redundant in this query and it is eliminated by the outer join elimination process. The query Q1 is equivalent to " SELECT DISTINCT T1.dummy_col FROM sys.dummy T1 "

Q1:

SELECT DISTINCT T1.dummy_col

FROM

sys.dummy T1

left outer join

( select row_num c0,

( select dummy_col from sys.dummy T2 where 1 = T3.row_num ) as c1

from dbo.rowgenerator T3

) T4

on 1=1

HKEY_CLASSES_ROOT\TypeLib\{A385EA65-7B23-4DC3-A444-2E759FF30B14}

This key is now removed when both components have been unregistered.

create view V_shubshub( x ) as

select dummy_col from sys.dummy D3

union all

select dummy_col from sys.dummy D4

go

create temporary function F_tt(in a1 smallint)

returns decimal(16,5)

begin

return 0.0

end

go

SELECT *

FROM

(

select F_tt( ( select dummy_col from sys.dummy D1 ) ) x

from sys.dummy D2

) AS T1

WHERE NOT EXISTS(

SELECT 1

FROM V_shubshub T2

WHERE T1.x=T2.x

)

In version 8.0, the following error was returned:

-266 42W27 "QOG_BUILDEXPR: could not build sub-select"

in version 9.0 and later, the following error was given:

"Run time SQL error -- *** ERROR *** Assertion failed: 102604 (...) Error building sub-select"

In versions prior to 8.0, it was possible for an incorrect answer to be returned without an error being returned.

This has been fixed.

dbeng10 web.db -xs HTTPS(SSLv2=N)

A workaround is to edit the generated batch file to use semicolons instead of comma for the stream parameters by changing this line:

set STREAM="%STREAM_TYPE%(port=%PORT%,tls_type=%TLS_TYPE%,fips=%FIPS%,certificate=%CERTIFICATE%)"

to the following:

set STREAM="%STREAM_TYPE%(port=%PORT%;tls_type=%TLS_TYPE%;fips=%FIPS%;certificate=%CERTIFICATE%)"

Assertion failed: 106105 (...) Unexpected expression type dfe_PlaceHolder while compiling

For example, the following statement could have this problem:

SELECT *

FROM

dbo.rowgenerator T1

LEFT JOIN

(

SELECT dummy_col c1

FROM sys.dummy T2

UNION ALL

SELECT 12345 c1

FROM ( select distinct id from sales_order_items order by id asc ) T3

) T4

ON 1=1

WHERE T1.row_num < 10

This has been fixed.

When a client disconnects during execution of an external function call, the server will no longer crash.

Also, if a row was selected in the "Table Mappings" table that had a non-empty status column, the Status tab would have been selected.

These problems have been fixed.

The following steps are a work around:

- From the Control Panel launch the Add or Remove Programs application.

- In the SQL Anywhere 10 item click the Change button.

- In the maintenance Welcome dialog select the Modify option.

- In the Select Features dialog deselect the ADO.NET Data Provider feature and proceed with installation maintenance (this will uninstall the feature).

- Repeat the above, but this time select the ADO.NET Data Provider and proceed with installation maintenance (this will reinstall the correct version of the feature).

For example:

create table T( x int not null, y int null compute( if x is null then 123 else x endif ) )

go

CREATE TRIGGER "ChangeX" BEFORE INSERT, UPDATE ON T

REFERENCING NEW AS new_row

FOR EACH ROW

BEGIN

message string('Trigger: ',new_row.x,',',new_row.y);

if new_row.x is null then

SET new_row.x = 4;

end if;

END

go

insert into T(x) values( NULL )

After the above insert, T contains one row (4,NULL). The result for y is inconsistent with the definition of the computed column.

The following non-fatal assertion failures could be reported in this case:

Assertion failure 106900 Expression value unexpectedly NULL in read

or

Assertion failure 106901 Expression value unexpectedly NULL in write

This has been fixed. An attempt to put a NULL value into a column declared NOT NULL that is used in a computed column will result in an error message:

23502 -195 "Column '%1' in table '%2' cannot be NULL"

This checking is performed before triggers fire, and this represents an intentional change in behaviour.

or the CREATE COMPRESSED DATABASE statement tried to create a compressed db file larger

than 4GB then the resulting file would have been corrupted. This has been fixed so that the server now returns the error "Database creation failed" if the resulting file would be larger than 4GB.

For example, the following query shows this problem:

select D0.type_id

from sys.sysdomain D0

intersect all

select D1.type_id

from sys.sysdomain D1

where exists ( select * from sys.sysdomain D2 where D2.type_id = D1.type_id )

This has been fixed.

For example:

SELECT *

FROM

( SELECT DISTINCT DT1c2

FROM ( SELECT (select dummy_col from sys.dummy D3 ) as alias1,

( select row_num from dbo.rowgenerator R4 where row_num-1 = alias1 )

FROM dbo.rowgenerator R5

) DT1( DT1c1, DT1c2 )

) DT2

WHERE EXISTS(

SELECT 1

FROM (

SELECT 1

FROM sys.dummy D0

UNION ALL

SELECT 2

FROM sys.dummy D1

) DT3( "DT3c1")

WHERE DT2.DT1c2 >= DT3.DT3c1 <<<<<------------- DT2.DT1c2 contains the subselect "( select row_num from dbo.rowgenerator R4 where row_num-1 = alias1 )"

)

Note that this fetching nvarchar or long NVarChar data from a blank padded database using a TDS client was not affected.

Option "<option-name>" is on the options watch list

If OptionWatchAction is set to 'error', an attempt to set an option in the watch list will result in an error:

Cannot set database option "<option-name>" because it is on the options watch list

The values of db_property('OptionWatchList') and db_property('OptionWatchAction') can be used to determine the current settings.

Example:

call dbo.sa_server_option('OptionWatchList','automatic_timestamp,float_as_double,tsql_hex_constant')

Note that the size of the string specified for OptionWatchList is limited to 128 bytes (the maximum for the "val" parameter to sa_server_option).

a.) continue developer the DBShrink in ASA 9.x, it means, fix the limitation to handle cbd file over 4 Gb.

b.) Return to include this in ASA 10, in where it was removed.

dblog -il -ir -is dbname.db

For example:

SELECT COUNT(*) FROM kb_baseclass INNER JOIN customer ON kb_baseclass=customer

WHERE customer IN (SELECT client FROM contact)

For example, the following script generates an overflow error:

create table types_bitwise( e_ubigint unsigned bigint );

select e_ubigint & 12345678901234567890 from types_bitwise;

This problem could also have occurred if the unary bitwise operator NOT were performed on a numeric argument. This issue has been fixed.

For example:

SACommand cmd = new SACommand("INSERT INTO t VALUES (1)", conn);

try

{

cmd.ExecuteNonQuery();

}

catch (Exception ex)

{

Console.WriteLine("Insert failed. " + ex.Message + "\n" + ex.StackTrace);

}

try

{

cmd.ExecuteNonQuery();

}

catch (Exception ex)

{

Console.WriteLine("Insert failed. " + ex.Message + "\n" + ex.StackTrace);

}

This problem has been fixed.

The following is an example:

CREATE FUNCTION foo( IN arg VARCHAR(3) )

RETURNS VARCHAR(10)

DETERMINISTIC

BEGIN

DECLARE retVal VARCHAR(10);

SET retVal = 'RETURNVALU';

RETURN retVal;

END

Dim cmd As New ADODB.Command

cmd.CommandText = "foo"

cmd.CommandType = ADODB.CommandTypeEnum.adCmdStoredProc

cmd.let_ActiveConnection(con)

cmd.Prepared = True

cmd.Parameters.Refresh()

cmd.Parameters(1).Value = "abc"

cmd.Execute()

MsgBox(cmd.Parameters(0).Value)

A work-around is to not prepare the command (ie. cmd.Prepared = False).

BYTE ORDER MARK { ON | OFF }

The semantics are identical to those used by the server's LOAD TABLE and UNLOAD TABLE statements. If omitted, "ON" is the assumed value. The BYTE ORDER MARK clause is relevant only when reading or writing ASCII formatted files encoded with UTF-8 or UTF-16 (and its variants). Attempts to use the BYTE ORDER MARK clause with FORMAT clauses other than ASCII, or with any other encoding, will result in an error.

NOTE (for 9.0.2 only): It is also important to run the MobiLink server with the command line option

-sl java ( -Dianywhere.qa.db.upgradeDeliveryColumns=true )

in order to get the most out of this performance improvement. This option causes the MobiLink server to reorganize the QAnywhere message store tables, and add further indexes to these tables, to obtain optimal performance of MobiLink with QAnywhere.

For example, the following batch illustrates the problem. It would have returned 2.0, rather than the correct 2.6:

BEGIN

DECLARE varNumeric NUMERIC;

DECLARE LOCAL TEMPORARY TABLE ltBUG (Dummy NUMERIC);

SET varNumeric = 1.3;

INSERT INTO ltBUG (Dummy) VALUES (ISNULL(varNumeric, 0) + ISNULL(varNumeric, 0));

SELECT * FROM ltBUG;

END;

This issue has been fixed.

Error: Unable to read from the 'tcpip' network connection. Unable to read 2 bytes.

Error: [-10034] No download confirmation from remote database

This problem has been fixed

For further information on the option Materialized_view_optimization, please refer to the SQL Anywhere� Server - Database Administration 爉anual.

An error (-5011: 0x80040706) has occurred while running the setup.

Please make sure you have finished any previous setup and closed other applications.

If the error still occurs, please contact your vendor: Sybase, Inc.

Spawning the CE deployment installer at the end of the CE Desktop install was unstable on Windows Vista. The deployment installer is no longer automatically deployed when installing on Windows Vista, but displays a message that deployment can be done by selecting "Deploy SQL Anywhere for Windows Mobile" from the Start menu.

create trigger statement stored in the catalog. As a result, the reload of a hidden trigger definition would have caused the SQL error: "Table ... not found", if the DBA user couldnot access the trigger without table owner. This has been fixed.

In order to unload an existing database with this problem, the trigger definition will need to be recreated and then hidden first.

create variable v char(128);

set v = 'abc';

insert into proxy_t(char_col) values(v);

whereas, the following had a chance of inserting a NULL, instead of the concatenated value:

create variable v char(128);

set v = 'abc' || 'def';

insert into proxy_t(char_col) values(v);

This problem has now been fixed.

Once a user had created a temporary procedure, the server would have allowed the creation of another temporary or permanent procedure by the same, resulting in duplicate procedures. The creation of duplicate temporary or permanent procedures is now not permitted. Note that the server already prevents the creation of a duplicate temporary or permanent procedure when the already existing procedure is a permanent one.

An improvement to the optimizer has been made so that the performance of complex queries with expensive table scans, under cetain circumstances, does not suffer even when good statistics are not available.

dbinit -zn UCA(locale=swe;sorttype=phonebook)

After the assertion, there was a very small chance of corruption that may be present even if the server reports a successful recovery. Therefore, validation is recommended. If problems are detected, then they should be handled with normal procedures (e.g. restore to backup, or attempt to salvage using an unload and reload with a server that has the bug fix).

It is possible to check the value of the internal counter involved in the bug by starting a transaction and running the query "select start_sequence_number from sa_transactions()". It is best to upgrade to a fixed server regardless of the value, but a larger value indicates a workload that is more likely to eventually trigger the counter overflow that causes the problem.

For example, in the following update the columns T1.b and T2.c are set to the same expression @val

update T1, T2

set T1.b = @val, T2.c = @val

where T1.a = T2.a

This has been fixed.

Increasing the amount of cache memory using the -cm server option is a work around for this problem.

Here are two examples:

1) This UPDATE statement has in its update clause first a non-updatable table expression V1 and then the updatable table T1. It does not update column "b" of table T1.

update ( select sum(T2.c) as xxx from DBA.T2 ) as V1( xxx) ,T1

set T1.b = isnull(V1.xxx,0)

where V1.xxx = T1.a and V1.xxx is not null and T1.a is not null

2) This UPDATE has two table expressions V1 and T1 in the update clause after view replacement of V11. If the order of the table expressions in the update clause is like in the example above, the UPDATE does not change any rows.

create view V11 as select T1.b, isnull( V1.xxx, 0 ) as v2_2

from ( select sum(T2.d) as xxx

from T2 ) V1 right outer join T1 on V1.xxx = T1

update V11 set b = v2_2

This problem has been fixed.

Default values were being wrapped in parentheses (), for example DEFAULT (0), which lead to sytax errors. Default valuess that start (after skipping white space) with open parentheses "(" and end with close parentheses ")", are now recognized and are automatically stripped.

Specifying the clause DEFAULT getdate(*) also lead to a syntax error. All occurrences of "(*)" in DEFAULT strings are now replaced with "()". Previously, only DEFAULT NEWID(*) was being recognized, this change handles all such functions.

Ulinit was failing to quote table names with leading underscore characters "--".

The now(), current_timestamp(), and getdate() functions in DEFAULT strings are now replaced with the string "current timestamp". This is equivalent in operation and the only syntax that UltraLite supports.

Added quoting to all uses of table names. Specifically the CREATE INDEX and ALTER TABLE ... ADD FOREIGN KEY statements were problematic.

Ulinit was making use of NVARCHAR data types. nut UltraLite does not support this data type.

When the collation specification argument to the SORTKEY or COMPARE functions referred to a valid SQLAnywhere legacy collation, the server would silently use the UCA instead. For example, SORTKEY( 'a', '1252LATIN1' ) would generate the same result as SORTKEY( 'a', 'UCA' ).

A small amount of memory would be leaked any time a connection was disconnected, provided that the connection had used SORTKEY or COMPARE at least once with a collation specification that was non-numeric and was not one of the built-in ASE compatibility labels.

When an invalid collation specification was passed to the COMPARE function, the error message that was generated (INVALID_PARAMETER_W_PARM, error -1090) did not correctly substitute the collation specification.

For example, COMPARE( 'str1', 'str2', 'invalidcollationlabel' ) would generate the message "Function 'compare' has invalid parameter '3' ('str2')". It now generates the message "Function 'compare' has invalid parameter '3' ('invalidcollationlabel')".

Applications can determine if a database has the fix by querying the new db_property( 'HasNCHARLegacyCollationFix' ). For servers released prior to this fix, this function will return NULL. For 10.x databases running on a server with this fix, this function will return 'On' if the database was created by an engine with the fix AND uses a legacy NCHAR collation. Otherwise, it returns 'Off'. For databases created after version 10, this function will return 'On'. This approach allows newly-created 10.x databases that use a UCA NCHAR collation to be started with older software.

When the server starts a database that was created by a server released prior to this fix and the database uses a non-UCA NCHAR collation and has at least one table defined to use an NCHAR column, the following warning message will be displayed in the server's message window (the text & url are yet to be finalized):

Warning: database \"%1\" is using an NCHAR collation which for which a fix has been made available. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/nchar_collation_warning.html

Note that a database created by a server prior to this release could still have problems sorting NCHAR data if NCHAR uses a legacy collation but the warning is only displayed if NCHAR columns exist.

-do disable offline logscan (cannot use with -x)

When this new option is used, dbmlsync will not attempt to scan any offline transaction logs. Therefore, dbmlsync with -do should be able to synchronize a database that is stored with all the other databases in a single directory, as long as this database does not have any offline transaction log files. However, if actual offline transaction log files are requested (for instance, if the minimum progress offset is located

in an offline transaction log or if an uncommitted transaction starts from an offline transaction log), dbmlsync with -do will raise an error and refuse to run the synchronization.

ASA ADO.NET provider that comes with ASIQ 12.7 SDK

ASA ADO.NET provider that comes with ASA 9.0.1, 9.0.2 and 9.0.3 - all providers produce same behavior

Sybase IQ 12.6 ESD9 on Windows and Sun Solaris.

Microsoft Visual Studio 2005

When running stored procedure from within VB application by using ASA ADO.NET Provider, an error "-180 - AsaError:Cursor not open" will happen. In Java ISQL, same procedure works fine.

Example 1: Binding UltraLite table to AGDBSet

connection = databaseManager.openConnection( openParms );

agdbSet = connection.getTableAGDBSet( "ULProduct" );

Example 2: Binding UltraLite result set to AGDBSet

statement = connection.prepareStatement( "select prod_id, prod_name, price from ULProduct order by price" );

resultSet = statement.executeQuery();

agdbSet = resultSet.getAGDBSet();

An example of such a query is:

SELECT col1

from remote_procedure_1()

where col2 = (select c1 from remote_procedure 2())

This problem has now been fixed.

connected" would have been logged by the QAManager, but was not reported back to the application. It should be noted that a QAManager will autostart the database server when the Open method is called. The issue was that when the database server was shut down after Open had been called, then subsequent QAManager operations would have failed because the database connection had been terminated, but the error codes returned to the application do not indicate that the connection to the database was bad, thus not allowing the application to Close and Open the QAManager to recover from the error. This has been fixed. If the ErrorCode of a QAException is greater than or equal to 2000, then the error means the same as ErrorCode - 1000, and also that a database connection failure has occurred (ie. SQL Anywhere native code -101). When a database connection error is detected, it is possible to re-Open a QAManager without recreating it and setting its properties and message listeners again. This is done by calling Close() then Open() again. Note that the properties of the QAManager cannot be changed after the first Open() and subsequent Open() calls, and must supply the same acknowledgement mode.

Note that the SQLAnywhere installation is performed from an elevated process and will not be affected by this bug.

ADOQuery1.SQL[0] := 'select * from Customers where GivenName = :fname';

ADOQuery1.Parameters.ParamByName('fname').Value := '';

ADOQuery1.ExecSQL;

This problem has been fixed. A null pointer passed to the provider for a parameter will now be treated as an empty string when passed to the database server.

Note that because the mobile webservices runtime (iawsrt.jar) is built with JDK 1.5, Java mobile webservices applications must be compiled with JDK 1.5 and up as well.

For example: A select on the following view may have failed with a permissions error for table T1:

create view V1 as select * from T1 join T2, T1 join T3

This problem has been fixed.

The first option is Priority. This option sets the priority level at which requests from a connection are executed. This option can take one of the following values:

CRITICAL

HIGH

ABOVE NORMAL

NORMAL

BELOW NORMAL

LOW

BACKGROUND

By default, all connections will get a Priority value of NORMAL. Any user can set the Priority option without DBA permission.

The second option is Max_Priority. This option controls the maximum priority level a connection can have. The default value for this option is NORMAL. Connections would needs DBA authority in order to change the Max_Priority option. A connection can always lower its priority level, but cannot raise it higher than the value of Max_Priority. An attempt to do so would raise a permission denied error. The scheduling semantic of the different priority levels allow all requests to get some CPU time despite the priority level of the request. Higher priority request will get more time slices than lower priority ones.

Note, The Background_Priority option is deprecated as of this release. It will still be recognized but will be removed in future releases. Currently, if a users sets the Background_priority option to ON, it will cause requests to execute at the BACKGROUND priority level. When the option is turned back to FALSE, requests will execute at whatever value the option Priority is set to.

For example, consider a table with the following schema:

CREATE TABLE Tab1( pk int not null primary key, value varchar(1) not null )

CREATE INDEX val_index ON Tab1( value )

The following statement could possibly update more than one row:

UPDATE Tab1 SET value = 憍� WHERE value = 憏�

However, since there is an index on value, this update would have only updated at most one row. This has been fixed and it will now update all qualifying rows.

Files missing or regkey invalid.

This has now been fixed.

Note, when this problem is noticed, rebuilding the affected database with the fix will eliminate the extra pages from the extension arena.

The sa_conn_compression_info procedure could have reported incorrect compression rates or packet compression rates if more than about two million bytes had been transferred since the server started. This has been fixed as wll. In order to get the fixed sa_conn_compression_info procedure, the ALTER DATABASE UPGRADE PROCEDURE ON statement must be executed (this will also upgrade the database to the current version, if necessary).

CREATE PROCEDURE mystring( IN instr XML )

EXTERNAL NAME 'xmlfunc@xmltools.dll';

XML parameters are passed in the same manner as LONG VARCHAR parameters. XML parameters are available when using the "new" external function call API.

Note that the problem does not affect backups where a log rename is performed after each backup, since in that case the logs will not contain overlapping sections. The problem can be avoided in version 10 by applying all of the logs at one time using the -ar or -ad options, which will cause the server to skip logs that are included by subsequent logs.

1) IP tracking was sometimes not firing BEST_IP_CHANGE event when the Listener was run on Windows CE.

2) Engineering case 466446 introduced a problem in the Listener where options following the options -ga or -gi may have been misinterpreted.

3) Asynchronous IP tracking (-ga) was not working on Windows CE devices.

Note, the Listener command line option -ga has been deprecated and asynchronous IP tracking is now implicit. The default of -gi has been changed from 10 seconds to 60 seconds. The polling mechanism now serves only as a backup. Users should not need to use -gi except for trouble shooting.

- the procedure was owned by a user with DBA authority

- the procedure contained a single SELECT statement and no other statements

- permission to execute the procedure was granted to a non-DBA user

- the procedure's SELECT referenced a table for which the procedure owner had not been granted permissions

This has been fixed. A workaround is to add a statement such as "if 1 = 0 then return end if;" to the start of the procedure.

SQL statement failed: (-141) Table 'sysarticlecol' not found.

This problem has been fixed.

SET REMOTE "FILE" OPTION "PUBLIC"."Directory" = '\\\\MACHINE\\Folder\\Subfolder';

were not being preserved when the database was unloaded. Given the above option setting, the reload.sql file would have contained:

SET REMOTE "FILE" OPTION "PUBLIC"."Directory" = '\\MACHINE\Folder\Subfolder';

which, on reload, would be incorrectly interpreted as "\MACHINE\Folder\Subfolder", causing SQL Remote to fail. This has been corrected.

- the caller has DBA authority

- the procedure is called from another procedure owned by a user having DBA authority

- execute permission has been granted

To correct the problem in existing databases without rebuilding or upgrading, the call to dbo.sp_checkperms in dbo.sa_disk_free_space can be removed.

default_timestamp_increment = 10000

truncate_timestamp_values = 'On'

the UltraLite database produced when running the UltraLite Initialization utility ulinit on this database would have caused problems when synchronizing. MobiLink would have complained about timestamp precision mismatches. Ulinit was not setting the timestamp_increment from the SA default_timestamp_increment value.

The workaround is to set the timestamp_increment setting on the ulinit command line, using

the -o keyword=value option, as follows:

ULINIT <existing options> -o timestamp_increment=1000

For example:

CREATE TABLE test(col NVARCHAR(8191));

CREATE VIEW test_view AS SELECT col from test;

or, the following, when issued on a UTF-8 database:

CREATE TABLE test(col VARCHAR(8191 CHAR));

CREATE VIEW test_view AS SELECT col from test;

would have failed with SQL error CHAR_FIELD_SIZE_EXCEEDED (-1093): "The size of the character column, variable, or value data type exceeds 32767". This has been fixed.

Note, a work around is to make the current user the owner of the MobiLink system setup.

SET TEMPORARY OPTION isql_show_multiple_result_sets='on';

EXIT 123;

worked, but

SET TEMPORARY OPTION isql_show_multiple_result_sets='on';

CREATE VARIABLE retcode INT;

SET retcode = 123;

EXIT retcode;

did not, the return code was always zero. This has been fixed.

For example, using named parameters when calling a procedure:

SACommand cmd = new SACommand( "MyProc", conn );

cmd.CommandType = CommandType.StoredProcedure;

SAParameter p4 = new SAParameter( "p4", SADbType.Integer );

p4.Direction = ParameterDirection.Output;

cmd.Parameters.Add( p4 );

SAParameter p3 = new SAParameter( "p3", SADbType.NChar, 30 );

p3.Direction = ParameterDirection.Output;

cmd.Parameters.Add( p3 );

SAParameter p2 = new SAParameter( "p2", SADbType.Char, 20 );

p2.Direction = ParameterDirection.InputOutput;

p2.Value = "222";

cmd.Parameters.Add( p2 );

SAParameter p1 = new SAParameter( "p1", SADbType.Integer );

p1.Direction = ParameterDirection.Input;

cmd.Parameters.Add( p1 );

cmd.ExecuteNonQuery();

given following procedure definition;

CREATE PROCEDURE MyProc( in p1 int, inout p2 char(20), out p3 nchar(30), out p4 int )

BEGIN

SET p2 = p2 + 'abc';

SET p3 = '333xyz';

SET p4 = p1 * 4;

END

Using named parameters in a query:

SACommand cmd = new SACommand( "UPDATE MyTable SET name = :name WHERE id = :id", conn );

SAParameter p1 = new SAParameter( "id", SADbType.Integer );

p1.Direction = ParameterDirection.Input;

p1.Value = 1;

cmd.Parameters.Add( p1 );

SAParameter p2 = new SAParameter( "name", SADbType.Char, 40 );

p2.Direction = ParameterDirection.Input;

p2.Value = "asdasd";

cmd.Parameters.Add( p2 );

cmd.ExecuteNonQuery();

A work around is to use the MyIP connection option on the client, and the MyIP TCP/IP option on the server and to make sure that they match.

Note, this problem also affected the iAnywhere JDBC driver, which is used by the Interactive SQL utility dbisql.

CREATE TRIGGER owner.name ...

then Sybase Central would have displayed the trigger SQL with the trigger's owner replaced by the trigger's name, such as:

ALTER TRIGGER name.name ...

This has been fixed. Now the SQL is displayed correctly as:

ALTER TRIGGER name ...

That is, the owner (which is syntactically valid, but is ignored by the

engine)

is removed from the source.

event handlers.

While there is no fix to ASA software, customers are advised to apply the HP-UX 11.00 patch PHNE_27886 or later (and all dependencies).

For example:

select prod_id.sum(sales) from sales group by prod_id order by prod_id

This query was intended to be "select prod_id, sum(sales) ..." but a typo replaced a comma with a period. If the table prod_id was a remote table, then the above mistyped query would have crashed the server. This problem has now been fixed.

For example:

create variable v int;

select sum(x) over ( partition by v ) from t

This has beenfixed.

This has been fixed.

Error: Invalid datetime format.

SELECT 999, count(*) FROM TABLE

where the incorrect result was a row for each row in the table, instead of a single row. Constants were not being marked as aggregates when they occurred in aggregate selections. This has been fixed.

subquery's best plan did not have the RowLimit operator, which may have resulted in the choice of a poor performing plan. This has been fixed.

For example, the query:

select * from R where R.X = (select max(R.X) from R )

would have had the cost of the plan "R<idx_x>:[ RL [ R<idx_x> ]]" overestimated by the optimizer. Hence, it was more likely to use "R<seq> JH [GrH [ R<seq>]]" as the best plan, which computed the subquery as a derived table. This plan may have been inefficient for queries where the table R was very large.

Q:

select * from R where R.X = (select max(R.X) from R )

A work around for this problem would be to ensure that the ColumnValue method is not called more than once for a single index by storing the value retrieved by the first call in a variable and working with that value.

A workaround for this problem is to set the option Max_query_tasks=1 to avoid all parallel access plans. That change will degrade performance for some queries, but will avoid the crash.

The file machine.config is an XML-formatted file, and is usually found in c:\Windows\Microsoft.NET\Framework\v2.0.50727\config. Data providers are listed in the <DbProviderFactories> sub-section of the <system.data> section of the file. A subset of the file is shown below:

<configuration>

(configuration for other providers)

<system.data>

<DbProviderFactories>

<add name="Odbc Data Provider" invariant="System.Data.Odbc" description=".Net Framework Data Provider for Odbc" type="System.Data.Odbc.OdbcFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>

(configuration for other providers)

<add name="SQL Anywhere Data Provider" invariant="iAnywhere.Data.AsaClient" description=".Net Framework Data Provider for SQL Anywhere" type="iAnywhere.Data.AsaClient.AsaFactory, iAnywhere.Data.AsaClient, Version=9.0.2.3585, Culture=neutral, PublicKeyToken=f222fc4333e0d400" />

</DbProviderFactories>

</system.data>

(configuration for other providers)

</configuration>

The bug was that the install truncated the file at the point where the "SQL Anywhere Data Provider" entry should have been added. This left the XML file in an inconsistent state, due to the <DbProviderFactories>, <system.data> and <configuration> sections not being closed. As well, entries that occurred after the <DbProviderFactories> section were missing entirely. Any data providers from other database vendors that were listed in the file after the SQL Anywhere provider would also have been deleted.

To fix the problem, the file needs to be restored manually. Ideally, if there is a backup of this file, it can be restored from the backup.

If that is not the case, the file will need to be manually edited to add the provider line above and close the <DbProviderFactories>, <system.data> and <configuration> sections. There is a file called machine.config.default in the same directory as the machine.config. This file contains the default settings for the machine.config, and can be used to restore the missing sections. Any installs for other products that modified the machine.config the file will also need to be rerun.

"Error deleting transaction log file"

to

"Error renaming transaction log file before deleting it. Error code: %d/%d"

The first number of the Error code means the error type (0 - POSIX error number, 1 - OS error number). On Unix and Netware, both error types mean POSIX error numbers. The second number is the actual error code. On Windows the POSIX error numbers can be found in the header errno.h.

Note that the chosen column's type should be able to be implicitly compared with a string, or errors may occur when downloading with the generated download script.

The following new files are included in the install:

ultralite\x64

ultralite\x64\uleng10.exe

ultralite\x64\ulstop.exe

ultralite\x64\mlczlib10.dll

ultralite\x64\mlcrsa10.dll

ultralite\x64\mlcecc10.dll

ultralite\x64\lib

ultralite\x64\lib\vs8

ultralite\x64\lib\vs8\ulrt.lib

ultralite\x64\lib\vs8\ulimp.lib

ultralite\x64\lib\vs8\ulrt10.dll

ultralite\x64\lib\vs8\ulbase.lib

ultralite\x64\lib\vs8\ulrsa.lib

ultralite\x64\lib\vs8\ulecc.lib

ultralite\x64\lib\vs8\ulrtc.lib

ultralite\x64\lib\vs8\ulimpc.lib

ultralite\x64\lib\vs8\ulrtc10.dll

[Sybase][iAnywhere Solutions - Oracle][Oracle]ORA-06553: PLS-306: wrong number or types of arguments in call to {procedure name}

This problem could have caused the MobiLink server to fail the download, when a download_cursor or download_delete_cursor event was written as:

{ call package_name.procedure_name ( ?, ?, ...) } or

{ call schema_name.package_name.procedure_name( ?, ?, ... ) }

This problem has been fixed. Now this event can be written as:

{ call [schema_name.][package_name.]procedure_name( ?, ?, ... ) }

The workaround, and required behaviour with the fix, is to specify a DBA user name for the tracing database that does not currently exist in the target database. The wizard has been modified to alert the user to this.

A workaround is to create the other index after the foreign key index has been created, or to declare an additional index with the correct column order.

SQL Anywhere� Server - Programming > Exit codes

Software component exit codes

A workaround is to drop and recreate statistics on the table in question.

Note, any backups of encrypted databases using this clause should be considered invalid and recreated with an updated server.

been fixed.

Note that this change only applies to the -x option, and not to the -xo option.

- Could not find subscription id for subscription of <ML user> to <publication>.

or

- SQL statement failed: (-101) Not connected to a database

if all the following were true:

1) the synchronization was scheduled and the time before the next scheduled sync was more than a 2 minutes

2) for some row in the syssync table, "log_sent" was greater than "progress". (This occurs when dbmlsync sends an upload to the MobiLink server, but does not receive an ack/nack to indicate that the upload was applied to the consolidated database or not)

3) hovering was enabled

This problem has now been fixed.

A workaround is to deploy to a SQL file and manually edit the SQL.

Scope: origin

Origin: external

Tracing type: statements_with_variables

Condition: none

would not have recorded any statements with an external origin. An incorrect string comparison was being used to determine whether a statement needed to be logged. This has been fixed.

the primary keys for rows that had caused the deadlock would not have been reported in the Deadlocks tab. This has been fixed.

This behaviour is only considered invalid if tracing data is saved in the database that is being profiled. If tracing data is saved in an external tracing database, primary key values for rows in the original database cannot be reported.

Note, this problem does not affect the database server, but does affect other components in SQL Anywhere.

Note, this problem can be avoided by using the -ca 0 engine switch to disable dynamic cache sizing.

in the QAnywhere Ultralight Agent, would have caused the rule to be immediately and repeatedly executed many times on startup. This has been fixed.

1) A subscription, S1, was created to some publication P1, and a second subscription, S2, was also created for P1 (either by dropping S1 and recreating it or by creating a new subscription to P1 with a different MobiLink User.)

2) During the first synchronization of S2, dbmlsync successfully sent an upload but did not receive an ack/nack from the MobiLink server.

3) The upload was not successfully applied to the consolidated database by the server.

When all these conditions were TRUE it was possible for operations that occurred before subscription S2 was created to be uploaded when subscription S2 was synchronized. This behavior has been corrected. Now, only operations that occurred after subscription S2 was created will now be uploaded when subscription S2 is synchronized.

SELECT * FROM myUser.

Now, database objects are listed correctly. This problem only affected those owners which did not own any stored procedures.

A workaround for this problem is to always issue a checkpoint before attempting a DROP TABLE that has a chance of failing.

create table test (col1 numeric(108,38) default 1111111111222222222233333333334444444444555555555566666666667777777777.12345678901234567890123456789012345678)

The value stored in the catalog (the SYSTABCOL "default" column) would have been truncated to: 1111111111222222222233333333334444444444555555555566666666667777777777.12345678

This has been fixed.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 10.0

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 10.0 Admin

This has been corrected.

For versions 11.0.1 and up, this change only applies to the -xo option of the MobiLink server. The -x option already allows larger values.

Select * from (table1) left join table2

This was corrected by adjusting the syntax to handle more general bracketing.

SELECT * FROM remote_t WHERE c1 = @nvar

In this example, if the table remote_t was a proxy table, and the variable @nvar was of type nchar, nvarchar or long nvarchar, then the server would have failed to execute the query with the "not enough host variables" error. This problem has now been fixed.

For example:

create variable @text varchar(3);

update T set @text = 'long long string', salary = salary

Previously, the update statement would pass and the value of @text was set to 'long long string'. Now, the statement fails with an error (provided the string_rtruncation option has its default value):

Right truncation of string data [-638] ['22001']

ALTER PROCEDURE owner.procname RECOMPILE

or

ALTER FUNCTION owner.funcname RECOMPILE

The process of recompiling causes the procedure or function definition stored in the catalog to be re-parsed and verified that it is syntactically correct. For procedures that generate a result set but do not provide a RESULT clause, the server will also attempt to determine the result set characteristics for the procedure and store that information in the catalog. This can be useful if a table referenced by the procedure has been altered to add, remove or rename columns since the procedure was created. The preserved source for a procedure or function is not changed by recompiling. Procedures and functions whose definition are hidden via

ALTER PROCEDURE owner.procname SET HIDDEN

can be recompiled, and their definitions will remain hidden.

For example:

dbvalid -c "UID=DBA;PWD=sql;DBF=mycopy.db;DBS=-n mycopy"

dbvalid -c "UID=DBA;PWD=sql;DBF=mycopy.db;DBS=-dh"

would both allow dbvalid to execute if mycopy.db required recovery. The database could also be pre-started before running DBVALID.

Palm - 4K

CE - 16K

all other platforms - 64K

and the maximum value for buffer_size has been increased from 64K to 1G.

Note, it is possible that a database could contain two dbspaces with the same name in different cases. This change would prevent these dbspaces from being differentiated. This would be a problem when migrating to versions 10 or later as well.

- the SharedMemory communication protocol is not supported. The TCP/IP communication protocol is used even if no protocol is specified, and a server name must always be specified when making a connection, or the connection will fail.

- the preferences dialog on the database server and MobiLink client is not supported. The preferences dialog normally appears if no command line options are used.

- the ODBC and OLEDB connection prompt dialog is not supported. This dialog normally may appear depending on the DriverCompletion parameter to SQLDriverConnect, or the DBPROP_INIT_PROMPT OLEDB property.

- the Unload / Reload support is not available. This includes dbunload.exe, dbrunsql.exe and the unload support server.

VALIDATE TABLE has also been enhanced to allow validation to proceed on very large tables or, more precisely, on tables whose last page number was very large. Prior to this change, error 08W13 (-86) "Not enough memory to start" could have been reported.

Note that if the table is actually very large relative to the cache, validation may take a very long time.

For example, executing the following:

UPDATE TOP 2 proxy_t

SET proxy_t.data = 'Hello'

ORDER BY proxy_t.pkey ASC;

would have updated all rows in the table. This problem has now been fixed.

Note that any intermediary that removes the information put into the User-Agent by the MobiLink client will cause synchronizations to fail.

The problematic expressions include the following:

COMPRESS CONNECTION_EXTENDED_PROPERTY CSCONVERT DATEFORMAT DB_EXTENDED_PROPERTY DB_ID DECOMPRESS DECRYPT ENCRYPT EVENT_CONDITION EVENT_PARAMETER EXTENDED_PROPERTY GET_IDENTITY HASH HEXTOINT HTTP_HEADER HTTP_VARIABLE ISDATE ISNUMERIC LIKE LOCATE NEXT_HTTP_HEADER NEXT_HTTP_VARIABLE NEXT_SOAP_HEADER PROPERTY_NAME PROPERTY_NUMBER REPLACE REVERSE SOAP_HEADER SORTKEY TO_CHAR TO_NCHAR UNICODE USER_ID VAREXISTS WRITE_CLIENT_FILE

select top ? table_name

from SYS.SYSTAB

order by table_id

This had been fixed.

- isolation_level option [compatibility]

- max_query_tasks option [database]

- optimization_goal option [database]

- optimization_level option [database]

- optimization_workload option [database]

The server will now raise an "invalid option setting" error in a predictable fashion if one of the unsupported options is used in the clause. There was a possibility of the server leaking a small amount of memory that has also been corrected.

For example, the following sequence could have incorrectly return 104.0 instead of 104.6.

create variable @vnum numeric(20,4)

set @vnum = ( select max(103.5) ) + 1

dbunlspt.exe will now start with the same default cache size as the server, and grow no larger than 40% of physical memory.

This has been fixed.

201417 "Invalid count or free space offset detected on a table page"

101412 "Page number on page does not match page requested"

Note that a value-sensitive cursor can be selected either explicitly, by cursor flags (ODBC keyset-driven, ESQL/SP scroll), or implicitly if the cursor type is changed by the query optimizer (for example, if a sort is used for an updatable cursor). This problem has been fixed. In engines with the fix for this problem, the affected cursor will return an error if it is used after the TRUNCATE or COMMIT. The error returned is: CURSOR_INVALID_STATE 24000 -853 "Cursor not in a valid state"

An example of such a query is:

SELECT col1

from remote_procedure_1()

where col2 = (select c1 from remote_procedure 2())

This problem has now been fixed.

1. Find all lines containing the "cut" command that uses the "-f" argument

2. For all such lines if a comma immediately follows the "-f", remove this comma

For example, the line:

OS_REL_1=`echo $OS_REL | cut -d. -f,1`

should become:

OS_REL_1=`echo $OS_REL | cut -d. -f1`

Note, this problem should not happen if the application is the MobiLink server. The MobiLink server does not call the ODBC function SQLColAttribute().

For example:

SELECT DISTINCT last_name FROM people ORDER BY birth_date

This has now been corrected.

For example:

SELECT TOP 14 * FROM table ORDER BY table.column

when there was no index that could be used to order the data. This has now been fixed.

Note that the problem was restricted to UNIQUEIDENTIFIER columns which could not be null and which did not have default values.

1) A procedure call in the FROM clause consists of a single SELECT statement and nothing else

2) The FROM clause inside the procedure from 1) also consists of a single SELECT and nothing else

then the procedure from 2) may be looked up in the context of the current connection rather than the owner of the procedure in 1). This is fixed.

Note that this is not a security hole since the incorrect lookup is done in the context of the current connection.

select user_id from sysuser where user_name='DBA'

insert into tauto with auto name values(1,2,'',4)

WITH AUTO NAME was being accepted, but ignored, for these types of INSERT statements. This has been changed so that the statement will now give a syntax error.

This was corrected. The work-around is to specify FOR READ ONLY on the query.

attempting to synchronize. This has now been fixed.

Syntax:

CREATE MATERIALIZED VIEW

...

[ CHECK { IMMEDIATE | MANUAL } REFRESH ]

Syntax Rules:

When used, the CHECK clause has the following effect:

1. The server performs the normal language checks that would be carried out if CREATE STATEMENT was executed without the clause and any errors generated are reported returned as usual.

2. The server does not carry out the actual creation of the view which means that certain errors, such as the specified name already existing in the database, are not generated and the CHECK clause can be used even for an existing view. This feature can be useful when a user is considering changing the definition of an existing view but does not know if the new proposed definition will be accepted by the server.

3. If CHECK IMMEDIATE REFRESH is used then the server will also verify that the syntax used is valid for an immediate view and will raise any appropriate errors.

4. The server makes no changes to the database and nothing is recorded in the transaction log.

5. The statement performs an implicit commit at the beginning of execution and a rollback at the end to release all locks obtained during execution.

For example, if connected as user u1 and the following executed:

select * from t;

setuser u2;

select * from t;

then the second SELECT could have incorrectly returned the results for u1.t instead of u2.t. This has been fixed. Setting the database option max_client_satements_cached to 0 will workaround this problem.

A work around would be to deploy to a SQL file and edit the file using the recommended data type mappings that are documented in this section of the documentation:

MobiLink - Server Administration > MobiLink Data Mappings Between Remote and Consolidated Databases

Note, this fix does not apply to the Dbmlsync Integration Component running on Windows CE systems.

the check is only done once at startup.

Note that the statement data was still saved in the tracing database - it was just not linked to the trigger, and was displayed in the Profiling mode in the Details tab with

"Procedure or Trigger Name" set to NULL.

A workaround would be to use datatypes TEXT, NTEXT, and IMAGE which correspond to the new datatypes.

This has been fixed.

delete from ml_qa_status_history where msgid not in (select msgid from ml_qa_repository)

go

commit

go

drop trigger ml_qa_repository_trigger

go

create trigger ml_qa_repository_trigger on ml_qa_repository for delete

as

delete from ml_qa_repository_props from deleted d, ml_qa_repository_props p

where d.msgid = p.msgid

delete from ml_qa_delivery from deleted d, ml_qa_delivery p

where d.msgid = p.msgid

delete from ml_qa_status_history from deleted d, ml_qa_status_history p

where d.msgid = p.msgid

go

The workaround is to edit the reload script and change all occurrences of 'aes_encrypt' to 'encrypt'.

call sa_server_option('RequestFilterDB', <db-id> )

query plans from statements executed on other databases on the same server would still have appeared in the request log. This has been fixed.

Also, in some cases actual statistics were not reported for recursive unions. This has been fixed.

For example:

rc = SQLGetInfo(hdbc, SQL_CONVERT_VARCHAR, (SQLPOINTER)&bitmask, sizeof(bitmask), NULL);

This will return with the SQL_CVT_WVARCHAR bit set in bitmask which indicates that the conversion is possible. However, attempting to do the conversion will return an error. This is illustrated by the preparing the following statement for execution:

SELECT {fn CONVERT(Surname,SQL_WVARCHAR)} FROM Employees

The error is "[42000][Sybase][ODBC Driver]Syntax error or access violation".

This problem has been fixed. Support has been added for conversion to types SQL_WCHAR, SQL_WLONGVARCHAR, SQL_WVARCHAR, and SQL_GUID.

Example:

INSERT INTO R ( T.X, R.Y) values (1,2) will now return an error because the column T.X cannot be found.

Note, if the application needs these threads to be notified of the shutdown, then the application must register a shutdown hook with the Java VM.

public class SampleClass {

private static Uninit uniniter = null;

public static Connection conn = null;

static {

try {

uniniter = new Uninit();

System.runFinalizersOnExit( true );

conn = DriverManager.getConnection( "jdbc:sybase:TDS:RemoteServer:2638", props );

}

catch ( Exception e ) {

System.out.println( "Error: " + e.getMessage() );

e.printStackTrace();

}

}

....

}

A workaround is to perform the upgrade and request that jConnect support not be added. This can be done using the "-i" option of dbupgrad, or with: ALTER DATABASE UPGRADE JCONNECT OFF

- conversion of multibyte strings to wide character strings (DBTYPE_WSTR) was not being done correctly for non-UTF8 character sets.

- DBTYPE_BYREF parameters were not supported.

- the provider would have crashed in the OLE DB Execute method when prepared statements did not have their parameter information set using the OLE DB SetParameterInfo method.

A workaround previous to this new feature would be to code the script as a stored procedure call.

For example:

CREATE TABLE test(col1 long varchar, col2 char(1000))

// ... insert long data into col1

ALTER TABLE TEST MODIFY col2 CHAR(10)

ALTER TABLE TEST MODIFY col2 CHAR(1000)

VALIDATE TABLE TEST

A workaround to the validation failure is to rebuild the database using dbunload or the Unload wizard in Sybase Central.

For example the following query will return rows with value 0 and 8 for column "a":

SELECT a FROM T1

WHERE

( a > 0 AND a < 2 ) OR ( a > 1 AND a < 3 ) OR ( a > 2 AND a < 4 ) OR

( a > 3 AND a < 5 ) OR ( a > 4 AND a < 6 ) OR ( a > 5 AND a < 7 ) OR

( a > 6 AND a < 8 ) OR ( a > 8 AND a < 10 ) OR ( a > 9 AND a < 11 ) OR

( a > 10 AND a < 12 ) OR ( a > 11 AND a < 13 ) OR ( a > 12 AND a < 14 )

This has been fixed.

For example, on a UCA database:

select if repeat('a', 1024) || 'a' = repeat('a', 1024) ||'b'

then 'equal'

else 'not equal'

endif

would return 'equal'. This has been fixed.

to use the Index Consultant.

{call procedure_name( ?, ? )}

for consolidated databases running on an Oracle server, the iAS ODBC driver for Oracle may have given the error:

ORA-06553: PLS-306: wrong number or types of arguments in call to 'procedure_name'

if the stored procedure returned a result set and the word, "call" was not all in lower-case. This has now been fixed.

Note that using multibyte characters in server and/or database names is not recommended for profiling, especially if the tracing database is started on a different physical server than the database being profiled.

In addition, the METHODS clause for a DISH service may now be modified to only allow the POST HTTP method (i.e. METHODS 'POST') which effectively disables access to the WSDL (which is returned by an HTTP GET request), but permits the processing of SOAP requests (which use HTTP POST).

Note that SQL Server application developers should test intended SOAP client toolkits to ensure that an HTTP GET request is not made to the DISH service prior to issuing the SOAP request. Some clients may do this to determine whether or not the definitions to the SOAP operations have changed.

- New METHODS value:

NONE

The NONE specifier, when provided, must be the only value in the METHODS clause, e.g.: METHODS 'NONE'. For ease of use, 'NONE' is applicable for any SERVICE. It is intended to be used only for SOAP services, it is not a substitute for SERVICE DISABLE, since a SOAP SERVICE with METHODS 'NONE' will still process requests proxied through a DISH service. When a SOAP service is disabled, it will not process any request through any service.

- the applicaiton had registered a DB_CALLBACK_CONN_DROPPED callback using db_register_a_callback()

- the application called db_fini to free the resources associated with a sqlca.

- there was a least one active connection associated the sqlca (i.e. there was a connection that had not been disconnected)

This was more likely to occur on a Unix system (including Linux and Mac OSX), than on Windows systems. This has been fixed.

A work-around is to ensure that all connections are disconnected prior to calling db_fini();

For example:

select repeat(N'',row_num) x

from rowgenerator

group by x

This has now been fixed.

A work-around is to place the comma-separated table expressions in parentheses. For a query such as:

SELECT * FROM tab1, tab2, tab2 LEFT OUTER JOIN tab4 ON tab4.x = tab1.y

the work-around is to rewrite the query as:

SELECT * FROM ( tab1, tab2, tab2 ) LEFT OUTER JOIN tab4 ON tab4.x = tab1.y

- the server was running on one of the Unix platforms (Linux, Solaris, AIX, HP-UX, or Mac OSX), and the executable was located in a nonstandard location. i.e. it is not in bin32 or bin64 directory

- the associated license file was in the same directory as the server (which is where it should be)

- the PATH environment variable did not contain the directory where the executable was located

- the support libraries (libdbserv10_r.so, libdbtasks10_r.so, etc) were located in a different directory than the executable

- the user's current working directory was not the same directory as where the executable was located

- when attempting to start the server a full or relative pathname to the executable was specified

This has been fixed. The server will now start correctly.

Work arounds include:

- add the directory that contains the server executable to the PATH

- make the executable directory the current directory before starting the server

- name the directory that contains the executable bin32 or bin64

create login policy test1 password_expiry_on_next_login = on;

create user u1 identified by sql login policy test1 force password change off;

attempting to connect to u1 using DBISQL caused a prompt for a new password. The "force password change off" clause on the CREATE USER statement should have prevented this prompt. This has been fixed.

The following .NET example can be used to illustrate the problem. Suppose another connection is inserting rows into the Customers table. Then the following example should result in an error when "blocking" is "off".

OleDbConnection conn2 = new OleDbConnection("Provider=SAOLEDB;DSN=SQL Anywhere 10 Demo");

conn2.Open();

OleDbTransaction trans2 = conn2.BeginTransaction(IsolationLevel.ReadCommitted);

OleDbCommand cmd2 = new OleDbCommand("SELECT FIRST Surname FROM Customers", conn2, trans2);

OleDbDataReader reader2 = cmd2.ExecuteReader();

while (reader2.Read())

{

String s = reader2.GetString(0);

MessageBox.Show(s);

}

Triggers and procedures not supported in runtime server

This has now been corrected.

incorrect predicate selectivity estimates could have lead to lower quality query access plans. When "expr" was an expression referencing one (or more) columns of table with correlation name T, selectivity estimates could have be updated with the assumption that "expr(T.y)" was constant for the duration of the query. This has been fixed.

For example:

SELECT t.x, t.y, t.z

FROM tx AS t

WHERE t.x <= t.y + 1

For OEM servers, once an application has executed the "SET TEMPORARY OPTION CONNECTION_AUTHENTICATION=" statement, the application can then turn around and execute a "SELECT connection_property( 'Authenticated' )" statement. If the result is "YES", then the connection was properly authenticated and all is well. If, however, the result is "NO", then the application can execute a "SELECT db_property( 'Authenticated' )" statement. If the result of this statement is "YES", then the database has been properly authenticated and the connection authentication failed because the CONNECTION_AUTHENTICATION string is incorrect. If, on the other hand, the result of querying the Authenticated database property is "NO", then the connection authentication failed because the database has not been properly authenticated. In this case, the customer should examine the DATABASE_AUTHENTICATION string to determine what is wrong.

For non-OEM servers, the result of querying these new properties will always be "NO".

Examples of such commands are:

INSERT INTO TestTable (ID,Name) VALUES(?,?)

?=CALL TestProcedure(?,?)

This problem has been fixed. The provider now returns the correct settings. A work around is to use the SetParameterInfo() method to set the DBPARAMFLAGS_ISINPUT or DBPARAMFLAGS_ISOUTPUT flags in the DBPARAMBINDINFO structure.

For example:

SACommand cmd = new SACommand();

cmd.CommandText = "UPDATE customers SET name='1' WHERE name='1'";

cmd.ExecuteNonQuery();

This problem has been fixed.

This has been fixed.

1. The provider was incorrectly calculating a very long timeout period.

2. Dropped connections were not being recycled.

These problems have now been fixed.

libXp-1.0.0-8.1.el5.i386 "X Org X11 libXp runtime library"

tail: `-1' option is obsolete; use `-n 1'

Try `tail --help' for more information.

An error occurred while attempting to extract files in /opt/sybase/ 

The way in which the head and tail utilities were being invoked by the installer was incompatible with some older versions of the Gnu head and tail utilities included on Linux. This has been fixed by replacing the use of head and tail in the setup script with appropriate sed commands.

For example, in the following statement, a division by zero error could be incorrectly returned for a keyset-driven (value sensitive) cursor.

select if TMS_1.x = 'zzz' and 1/QT2.y > 0 then 12 endif

from (

SELECT x, y

FROM TMS_2

GROUP BY x,y

) AS QT2

join TMS_1

ON TMS_1.x = QT2.x

Note, a work around is to use a tmpfs based ramdisk, or start the server with the -u (use buffered disk I/O).

Note, this problem did not affect Internet Explorer 6 or Firefox 2.0.0.

This has been fixed. Now, specifying any non-positive number for the -idl option will reset the incremental download size to -1.

Note that finalizing Connection objects can cause the same crash.

In the following example, the ON condition of the LEFT OUTER JOIN in the EXISTS subquery references the table 't1', which is a table used in the FROM clause of the main query block. This query may return incorrect result for some instances of the database.

select * from t1

where exists(

select 1

from t4

left outer join t2 on ( t2.c1 = t4.c1 and t2.c1 = t1.c1 )

where t4.c1=1

)

Note, any existing views compiled with an older version of the server will continue to have potentially incorrect dependency information in the catalog. Existing views can be made to have the correct dependency information by being recompiled, either implicitly during a DDL operation on one of the referenced tables, or explicitly.

Note that since Sybase Central makes use of sa_text_index_statistics() in order to display information on text indexes, Sybase Central will also not work as expected.

SELECT TOP var1 START AT var2 * FROM ...

and the query referenced a proxy table, and the query could have been handled in full passthru, then the query would have failed with a 'column not found' or 'bad cursor range' error. This problem has now been fixed.

For example:

SELECT * FROM MyTable WHERE col LIKE 'abc%' ORDER BY col DESC

The implementation of LIKE predicates with reversed index scans was erroneous. This has now been corrected.

Sample output follows:

I. 2008-06-05 14:48:36. <1> PHASE: start_time: 2008-06-05 14:48:36.048

I. 2008-06-05 14:48:36. <1> PHASE: duration: 175

I. 2008-06-05 14:48:36. <1> PHASE: sync_request: 0

I. 2008-06-05 14:48:36. <1> PHASE: receive_upload: 19

I. 2008-06-05 14:48:36. <1> PHASE: get_db_worker: 0

I. 2008-06-05 14:48:36. <1> PHASE: connect: 18

I. 2008-06-05 14:48:36. <1> PHASE: authenticate_user: 51

I. 2008-06-05 14:48:36. <1> PHASE: begin_sync: 69

I. 2008-06-05 14:48:36. <1> PHASE: apply_upload: 0

I. 2008-06-05 14:48:36. <1> PHASE: prepare_for_download: 1

I. 2008-06-05 14:48:36. <1> PHASE: fetch_download: 4

I. 2008-06-05 14:48:36. <1> PHASE: wait_for_download_ack: 0

I. 2008-06-05 14:48:36. <1> PHASE: end_sync: 0

I. 2008-06-05 14:48:36. <1> PHASE: send_download: 10

I. 2008-06-05 14:48:36. <1> PHASE: get_db_worker_for_download_ack: 0

I. 2008-06-05 14:48:36. <1> PHASE: connect_for_download_ack: 0

I. 2008-06-05 14:48:36. <1> PHASE: nonblocking_download_ack: 0

Note, a work-around is to manually edit the reload script to make the reload work.

{call procedure_name( ?, ? )}

for consolidated databases running on an Oracle server, the iAS ODBC driver for Oracle may have given the error:

ORA-06553: PLS-306: wrong number or types of arguments in call to 'procedure_name'

if the stored procedure returned a result set and the word, "call" was not all in lower-case. This has now been fixed.

Note, the iAS ODBC driver for Oracle in version 9.0.2 is actually the driver from version 10.0.1. Versions of the driver with this fix are 10.0.1 3686 or later.

In the future, customers will be able to update the JRE themselves by following instructions which will be made available shortly.

"SQL statement failed: (-265) Procedure 'ml_qa_sync_rule_0' not found" would have occurred in the MobiLink client (dbmlsync). This has been fixed.

Note, the iAS ODBC driver for Oracle in version 9.0.2 is actually the driver from version 10.0.1. Versions of the driver with this fix are 10.0.1 3715 or later.

In related issues, the toolbar button for opening this wizard was missing, and the "Create a client message store" item should have been removed from the Task list on non-Windows machines, but was not. These have been fixed as well.

See Engineering case 536015 for a related issue.

connection_extended_property

connection_property

db_extended_property

db_property

estimate

estimate_source

event_condition

event_condition_name

event_parameter

experience_estimate

http_body

http_header

http_variable

index_enabled

index_estimate

next_connection

next_database

next_http_header

next_http_variable

next_soap_header

property

rewrite

soap_header

varexists

watcomsql

For web services based on sessions, connection properties such as SessionLastTime could also have been affected by this (among other builtins). This incorrect behaviour was masked in version 10.0.1 for web services using sessions.

Java:

The following methods, added to interface ianywhere.ml.script.ServerContext are used to register or unregister listeners:

/**

* Adds the specified LogListener to receive a notification

* when info is printed.

* method {@link LogListener#messageLogged} will be called.

*

* @param ll the LogListener to be notified on warning

*/

public void addInfoListener( LogListener ll );

/**

* Remove the specified LogListener from the list of

* listeners to receive a notification

* when info is printed.

*

* @param sl the listener which will no longer be notified

*/

public void removeInfoListener( LogListener ll );

The following constant, added to class ianywhere.ml.script.LogListener, is returned by LogMessage.getType() for info messages:

public static final int INFO = 2;

Example:

The following code registers a listener of type MyLogListener to receive notifications of info messages.

// ServerContext serv_context;

serv_context.addInfoListener(

new MyLogListener( ll_out_file ));

The following code shows an example of processing those messages:

class MyLogListener implements LogListener {

FileOutputStream _out_file;

public TestLogListener( FileOutputStream out_file ) {

_out_file = out_file;

}

public void messageLogged( ServerContext sc,

LogMessage msg ) {

String type;

String user;

try {

if(msg.getType() == LogMessage.ERROR) {

type = "ERROR";

} else if(msg.getType() == LogMessage.WARNING) {

type = "WARNING";

} else if(msg.getType() == LogMessage.INFO) {

type = "INFO";

} else {

type = "UNKNOWN!!!";

}

user = msg.getUser();

if( user == null ) {

user = "NULL";

}

_out_file.write(

("Caught msg type=" + type +

" user=" + user +

" text=" +msg.getText() +

"\n").getBytes() );

_out_file.flush();

} catch( Exception e ) {

// if we print the exception from processing an info message,

// we may recurse indefinately

if( msg.getType() != LogMessage.INFO ) {

// Print some error output to the MobiLink log.

e.printStackTrace();

}

}

}

}

.NET:

Callback functions can be registered to the following event, added to interface iAnywhere.MobiLink.Script.ServerContext, to receive notifications about info messages:

/// <summary>

/// Triggered when the MobiLink server prints info

/// </summary>

event LogCallback InfoListener;

The following, added to enum iAnywhere.MobiLink.Script.LogMessage.MessageType, can be returned by the Type property of the LogMessage class

/// <summary>

/// A log info message.</summary>

INFO

Example:

The following code defines a callback that will process an info message.

internal class TestLogListener {

public TestLogListener( StreamWriter output_file,

LogMessage.MessageType expected_type )

{

_output_file = output_file;

_expected_type = expected_type;

}

public void errCallback( ServerContext sc, LogMessage lm )

{

string type;

string user;

if( lm.Type != _expected_type ) {

_output_file.WriteLine( "Message type not expected!!" );

return;

}

if( lm.Type==LogMessage.MessageType.ERROR ) {

type = "ERROR";

} else if( lm.Type==LogMessage.MessageType.WARNING ) {

type = "WARNING";

} else if( lm.Type==LogMessage.MessageType.INFO ) {

type = "INFO";

} else {

type = "INVALID TYPE!!";

}

if( lm.User == null ) {

user = "null";

} else {

user = lm.User;

}

if( (lm.Text.IndexOf( "10017" ) > 0) ||

(lm.Text.IndexOf( "10018" ) > 0) ||

(lm.Text.IndexOf( "10020" ) > 0)

|| (lm.Type == LogMessage.MessageType.INFO

&& lm.Text.IndexOf( "MobiLink server started" ) < 0 )

) {

return;

}

_output_file.WriteLine( "Caught msg type=" + type +

" user=" + user +

" text=" + lm.Text );

_output_file.Flush();

}

StreamWriter _output_file;

private LogMessage.MessageType _expected_type;

}

The following code adds the callback to the InfoListener event.

// ServerContext _sc;

TestLogListener itll = new TestLogListener(

log_listener_file,

LogMessage.MessageType.INFO );

sc.InfoListener += new LogCallback(itll.errCallback);

CREATE TABLE GROUPO.MyTable(

DATA2 varchar(16),

DATA1 varchar(16),

PKEY int NOT NULL default autoincrement,

CONSTRAINT PKeyConstraint PRIMARY KEY (PKEY)

) ;

CREATE VIEW DBA.MyView( PKEY, DATA_1, DATA2)

AS SELECT PKEY, DATA1, DATA2 FROM MyTable;

Consider the following queries.

SELECT PKEY, DATA_1, DATA2 as D2 FROM MyView

SELECT PKEY, DATA1 as DATA_1, DATA2 as D2 FROM MyTable

In both cases, the OLE BD provider would return the following for DBCOLUMN_BASECOLUMNNAME and DBCOLUMN_BASETABLENAME for these queries.

PKEY MyTable

DATA_1 MyTable

D2 MyTable

Of course, the DATA_1 and D2 columns are not found in MyTable.

With this fix, the provider now returns the correct column names.

PKEY MyTable

DATA1 MyTable

DATA2 MyTable

The problem remained however if an HTTP session was used to call a service that specified a different user id. A SA web application using HTTP sessions should only use TEMPORARY and/or USER specific options when all requests within the HTTP session context access SA services defined with the same user id. Similarly, accessing an authenticated SERVICE would require that the HTTP request belonging to a session provide the same user id from request to request. To address this, a new HTTP OPTION called SessionTimeout has been added to make HTTP session time-out criteria persistent in all cases. It can be set from within an HTTP request that has defined, or will define, a SessionID. The context of the setting is preserved throughout the HTTP session, until it expires, is deleted or changed (with a subsequent SA_SET_HTTP_OPTION call).

- New SA_SET_HTTP_OPTION option SessionTimeout

The value of this HTTP OPTION is specified in minutes. It is subject to the minimum and maximum constraints of the HTTP_SESSION_TIMEOUT database option. A newly created session is implicitly assigned the current or default PUBLIC/USER HTTP_SESSION_TIMEOUT.

The following example sets a given HTTP session time-out to 5 minutes:

call SA_SET_HTTP_OPTION('SessionTimeout', '5');

An empty value resets the option to its default value, or as set by the PUBLIC or USER scope HTTP_SESSION_TIMEOUT database option.

call SA_SET_HTTP_OPTION('SessionTimeout', ''); // resets the time-out to 30 minutes - the default value of the HTTP_SESSION_TIMEOUT database option

SET OPTION PUBLIC.HTTP_SESSION_TIMEOUT=1 // New HTTP sessions calling SA_SET_HTTP_OPTION('SessionTimeout', '') set session time-out to 1 minute

SET OPTION USERA.HTTP_SESSION_TIMEOUT=15 // New HTTP sessions calling SA_SET_HTTP_OPTION('SessionTimeout', '') set session time-out to 15 minutes for USERA

NOTE: HTTP session default criteria is derived from the current PUBLIC/USER HTTP_SESSION_TIMEOUT database option setting. Any subsequent changes to this option will not implicitly affect existing HTTP sessions. The default timeout setting for HTTP sessions that always use the same user id remains unchanged. However, an HTTP request belonging to a session that calls a service with an alternate user id will force its cache to be cleared and the option defaults of the current user to be loaded. Therefore, when the session switches users all TEMPORARY options are lost and the current PUBLIC/USER options are assigned.

- New CONNECTION_PROPERTY('SessionTimeout')

Returns the time-out value in minutes for a given database connection belonging to an HTTP session. The value is the current setting for SA_SET_HTTP_OPTION('SessionTimeout', 'X').

A value of 0 is returned if the database connection does not belong to an HTTP session. As before, the HTTP_SESSION_TIMEOUT database option may be queried to determine the PUBLIC/USER default values.

- Summary of changes

TEMPORARY and USER scope options are preserved when HTTP requests belonging to a session execute SA services defined with a specific (the same) user id.

SessionTimeout HTTP_OPTION has been added to provide an HTTP session context time-out criteria. Its use is recommended in place of setting a TEMPORARY HTTP_SESSION_TIMEOUT database option since it is guaranteed to persist for the life of the session.

A workaround is to disable the dependent view before executing the ALTER statement, followed by a re-enabling of the view.

A workaround is to set the worker recycling option for IIS to ON, in order to keep the leak under control.

create index idx on t(a asc, b asc, c asc)

The UltraLite Initialize Database utility (ulinit) would have created the index as:

create index idx on t(c asc, b asc, a asc).

reversing the order of the columns. This has been corrected and ulinit will now create the index in the same order as the reference database.

For example:

stream=http(host=myhost;url_suffix=root/(MyName)/ml;port=80)

This has now been fixed.

In addition the processing of DATE values has modified with this change. The TZ offset if provided with an input DATE value is now ignored, and the TZ offset is no longer appended to an output DATE value (within the HTTP/SOAP response).

Note, this is a follow-up to Engineering case 530790.

for applications using ianywhere.ml.jdbcodbc.IDriver, use:

ianywhere.ml.jdbcodbc.IConnection.SA_TRANSACTION_SNAPSHOT

ianywhere.ml.jdbcodbc.IConnection.SA_TRANSACTION_STATEMENT_SNAPSHOT

ianywhere.ml.jdbcodbc.IConnection.SA_TRANSACTION_STATEMENT_READONLY_SNAPSHOT

for applications using ianywhere.ml.jdbcodbc.jdbc3.IDriver, use:

ianywhere.ml.jdbcodbc.jdbc3.IConnection.SA_TRANSACTION_SNAPSHOT

ianywhere.ml.jdbcodbc.jdbc3.IConnection.SA_TRANSACTION_STATEMENT_SNAPSHOT

ianywhere.ml.jdbcodbc.jdbc3.IConnection.SA_TRANSACTION_STATEMENT_READONLY_SNAPSHOT

Also, if connecting using a QAnywhere connection profile was not possible, Sybase Central would have crashed rather than reporting the error. This has been corrected as well.

'Illegal column definition: Column 'xxx' inline value '-32768' is invalid"

This has now been fixed. A workaround is to use the value 32767. Doing so does not affect the amount of inline space available for the column as there is always some page overhead that is unusable for prefix data.

See also Engineering case 534294 for a related issue.

The following table contains a description of the printed values:

Value Description

TCP_CONNECTIONS Number of TCP connections currently opened

PAGES_USED Number of cache pages used

PAGES_LOCKED Number of cache pages loaded into memory

TCP_CONNECTIONS_OPENED Total number of connections ever opened

TCP_CONNECTIONS_CLOSED Total number of connection ever closed

TCP_CONNECTIONS_REJECTED Total number of connection ever rejected

TCP_BYTES_READ Total number of bytes ever read

TCP_BYTES_WRITTEN Total number of bytes ever written

ML_NUM_CONNECTED_CLIENTS Number of connected sync client

PAGES_SWAPPED_OUT Total number of pages ever swapped to disk

PAGES_SWAPPED_IN Total number of pages ever read from disk

PAGES_IN_STREAMSTACK Number of pages held by the network streams

CPU_USAGE Amount of CPU time used by MobiLink server in microseconds

NUM_COMMITS Total number of commits

NUM_ROLLBACKS Total number of rollbacks

NUM_SUCCESS_SYNCS Total number of successful syncs

NUM_FAILED_SYNCS Total number of failed syncs

NUM_ERRORS Total number of errors

NUM_WARNINGS Total number of warnings

DB_CONNECTIONS Number of database connections in use

RAW_TCP_STAGE_LEN Length of the network work queue

STREAM_STAGE_LEN Length of the high level network processing queue

HEARTBEAT_STAGE_LEN Length of the queue for periodic, non-sync work

CMD_PROCESSOR_STAGE_LEN Length of the queue for sync work

NUM_ROWS_DOWNLOADED Total number of rows sent to remotes

NUM_ROWS_UPLOADED Total number of rows received from remotes

FREE_DISK_SPACE Disk space available on the temp disk in bytes

LONGEST_DB_WAIT Longest length of time an active sync has been waiting for the database

LONGEST_SYNC Age of the oldest sync in ms

NUM_UNSUBMITTED_ERROR_RPTS Number of unsubmitted error reports

MEMORY_USED Bytes of RAM in use. Windows only.

SERVER_IS_PRIMARY 1 if the server is primary; 0 otherwise

Further, in some cases the plan text for a simple statement could show the table name instead of the correlation name. This has also been fixed.

Example:

SA server uses ISO-8859-1 charset,

client specifies Accept-Charset:UTF-8,IBM850;q=0.8,ISO-8859-1;q=0.5

Although least preferred by the client, SA will respond with ISO-8859-1 if SA_SET_HTTP_OPTION('AcceptCharset', '+'); has been called (from within a procedure servicing the HTTP request).

Invalid or corrupt network interface library: xxxxx

This has been corrected so that now the MobiLink server issues the message:

Failed to load library xxxxx

he documentation for the load library message indicates that a license may be required, which is appropriate in this case.

An example:

select dim1, dim2, sum (val1), stddev (val2)

from tt

group by cube (dim1, dim2)

having dim1 is not null or dim2 is not null

select x from ( select V1.*, row_number() over ( order by b ) AS x

from ( select *, 7 as b from T1 order by 1 ) V1

) V2

is used on column "b" of the nested table expression "V1", and column "b" is a constant there. This has been fixed.

Note, this change does not affect the SIMILAR TO search expression, which continues to use the collation to determine character equivalence and evaluate character class ranges.

The search condition SIMILAR TO has not been changed. For SIMILAR TO, _ matches one character, % matches any number of characters and [a-e^d] matches a, b, c and e.

Additionally, the creation of savepoints for temporary objects on read-only databases is also now supported.

select c1.ref(), max( c2 ), c2 from t1

where c1.ref() is a meaningless expression. This problem has now been fixed and a proper error message will be returned to the application.

SQL statement failed: (100) Row not found

This problem has been fixed. The MobiLink server will now complain if a download_delete_cursor returns NULL as well as non-NULL values for the primary key columns of a synchronized table, and will then abort the synchronization.

The download_delete_cursor script must return NULL values for all the primary key columns (the MobiLink client will delete all

the rows from the corresponding sync table) or non-NULL values (the client will delete specific rows specified by the primary

key values).

InternalError: User 'DBA' has the row in 'ml_qa_global_props_client' locked

Source statement: CREATE SYNCHRONIZATION SUBSCRIPTION TO ml_qa_user_group.ml_qa_repository_pub FOR "sender-rules" OPTION sv='ml_qa_2'

This has been fixed by now having the QAnywhere Agent acquire exclusive locks on tables involved in the publication, before creating the synchronization subscription.

Note, this problem should only have occurred on systems where a GUI was used.

Note that on the BlackBerry, the MDS may cache cookies for the devices that go through it, and so UltraLiteJs cookie behaviour may be different from other remotes. In particular, cookies sent to the remote may be cached for longer than the duration of a sync. When using a proxy other than the Relay Server, ensure that the optional cookie fields, defined in RFCs 2109 and 2965 dealing with cookie caching, are properly set, or disable this feature in your MDS. The Relay Server is unaffected by this caching, but other cookie injecting proxies may be affected by it.

Note, this problem does not occur if the result set is not positioned on the last row.

Caching notifier

A caching notifier is a notifier with a request_cursor that return a result set with 1, 2 or 3 columns. The first column is the key of the notification, the optional second column is the subject of the notification and the optional third column is the content of the notification. A caching notifier doesn't need gateways or tracking information in order to push notifications down to clients. Clients are expected to initiate connection and poll at the cache refresh frequency. Users may define multiple caching notifiers for different business logic, and they can co-exist with other regular or caching notifiers.

MLLP API

Development resources are found under the following location

%SQLANY10%\MobiLink\ListenerSDK\windows\src\mllplib.h

%SQLANY10%\MobiLink\ListenerSDK\windows\x86\mllplib.dll

%SQLANY10%\MobiLink\ListenerSDK\windows\x86\mllplib.exp

%SQLANY10%\MobiLink\ListenerSDK\windows\x86\mllplib.lib (import library for the dll)

MLLP client will dynamically load various ML client stream library.

Example MLLP client app

Please see %SQLANYSH10%\samples\MobiLink\SIS_CarDealer_LP2

fixed.

For example, the following select improperly returned '0002', the correct answer should be a numeric with value 2.

create variable @v_res long varchar;

set @v_res = if 1=1 then '0002' else '1' - '2' endif;

select @v_res

This problem could have also resulted in conversion errors being returned in cases where they should not, or missed in cases where they should have been generated. This problem has now been fixed.

Also, UltraLiteJ was incorrectly identifying to MobiLink that tables being synchronized were in all publications currently sync'ed and UltraLiteJ was incorrectly sending the last download time of publications. Both of these problems have been fixed.

Note, this problem was introduced with the changes for Engineering case 533936.

Note, users can always view the documentation using whatever browser they choose, as a work around to this issue.

There was nothing wrong with the HTML files. It was just that the component used to display them was inadequate. Users can always view the documentation using whatever browser they choose to work around this issue.

Notifier informational message will now take on the following format:

I. YYYY-MM-DD HH:MM:SS. <Main> <SISI> ...

Notifier error message will now take on the following format:

I. YYYY-MM-DD HH:MM:SS <Main> <SISE> ...

After some researches I received the following answer from internal newsgroup (sybase.internal.asa.helpdesk)

I believe the SA feature that can provide functionality similar to what

Oracle's autonomous transactions do is events.

In SA, events run as independent transactions with their own transaction

control and can be triggered from within other transactions without

affecting the triggering transaction.

Here is an example:

CREATE TABLE t1( c1 int );

CREATE EVENT ev

HANDLER

BEGIN

INSERT INTO t1 VALUES( 99 );

commit;

END;

INSERT INTO t1 VALUES (1);

TRIGGER EVENT ev;

ROLLBACK

The effect of the code above is to rollback the transaction that triggered

the event but retain the committed transaction executed by the event.

Howerver cust argue that 'Event' at SQL Anywhere are not equal of Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION'.

According cust with 'Events' he cannot capture its return, but with Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION' he can.

Checking the SQL Anywhere 10 manual, we can see:

Event errors are logged to the database server console.

After each execution of an event handler, a COMMIT occurs if no errors occurred. A ROLLBACK occurs if there was an error.

Event handlers execute on a separate connection, with the permissions of the event owner. To execute with authority other than DBA, you can call a procedure from within the event handler: the procedure executes with the permissions of its owner. The separate connection does not count towards the ten-connection limit of the personal database server.

So, cust request to us open a feature request to implement at SQl Anywhere a feature like Oracle's 'PRAGMA AUTONOMOUS_TRANSACTION'.

To correct existing demo.db databases:

1 start demo.db using dbeng11 or dbsrv11

2 change to the scripts directory of the install

3 run the following script:

SET TEMPORARY OPTION allow_read_client_file = 'on';

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\TankTop.jpg' )

WHERE Products.ID=300;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\V-Neck.jpg' )

WHERE Products.ID=301;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\CrewNeck.jpg' )

WHERE Products.ID=302;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\CottonCap.jpg' )

WHERE Products.ID=400;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\WoolCap.jpg' )

WHERE Products.ID=401;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\ClothVisor.jpg' )

WHERE Products.ID=500;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\PlasticVisor.jpg' )

WHERE Products.ID=501;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\HoodedSweatshirt.jpg' )

WHERE Products.ID=600;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\ZippedSweatshirt.jpg' )

WHERE Products.ID=601;

UPDATE Products

SET Photo=READ_CLIENT_FILE( 'adata\CottonShorts.jpg' )

WHERE Products.ID=700;

address, the scope (interface) ID must be specified. If a scope ID is not specified, it defaults to 0. A connection attempt where the scope ID is incorrect may take a long time to time out and fail. When a link-local IPv6 address was registered with LDAP, the scope ID was not included in the IP address that was registered. Doing so would not be

useful, since scope IDs for the same link can vary from machine to machine. If an application obtained such a link-local address from LDAP and attempts to connect to it, in effect it will attempt a connection with a scope ID of 0. This has been fixed so that now an attempt to if the scope ID is 0 is refused on Mac OS X systems, including when the HOST connection parameter is used in the connection string with a link-local IPv6 address with no interface ID specified.

Note that if the wrong non-zero interface ID is specified, a connection will still be attempted.

to attempt to connect to the Web Edition server would have resulted in the error "This server is not licensed to support 'ODBC' connections". This has been corrected.

E. 2008-08-06 16:24:34. Timed out trying to readTimed out trying to read 7 bytes.

This has been fixed.

For example:

select filename, file_id from t1 where

(

exists (select * from t1 except select * from t2)

OR

exists (select * from t2 except select * from t1)

)

A similar problem affected the display of long text values, and it has also been fixed.

/opt/IBM/ldap/V6.1/lib64/libibmldap.a

and the 32-bit library is in:

/opt/IBM/ldap/V6.1/lib/libibmldap.a

This has been fixed.

Note that you still need to ensure that the directory with the LDAP libraries are in the LIBPATH. For example, for 64-bit libraries:

export LIBPATH=/opt/IBM/ldap/V6.1/lib64:$LIBPATH

and for 32-bit libraries:

export LIBPATH=/opt/IBM/ldap/V6.1/lib:$LIBPATH

As a work around to use SQL Anywhere LDAP support with AIX 6, create links in /usr/lib as follows (must be root):

cd /usr/lib

ln -s /opt/IBM/ldap/V6.1/lib64/libibmldap.a libibmldap64.a

ln -s /opt/IBM/ldap/V6.1/lib/libibmldap.a

1. When inserting a GIF file into a binary column, a thumbnail is now displayed. Previously, the thumbnail remained empty.

2. The image format and dimensions were not displayed when viewing a binary column value which contained a GIF image.

1 - HAVING predicate was not dumped in the long plan for any GroupBy physical operator. 2 - HAVING predicate was not dumped for GroupBySortedSets physical operators in the graphical plan.

3 - The number of extension pages was missing in "Table Reference" section of the graphical plan.

4 - The 'Estimated Cache Pages' was missing in the long plan.

if the connection had no changes to commit. This has been fixed.

To work around this issue, the demo.db database can be recreated using the dbinit, dbisql and the Scripts\mkdemo.sql script. Alternatively, the dbunload tool with the -ap option can be used to rebuild the database.

*** ERROR *** Assertion failed: 106104 (...) Field unexpected during compilation (SQLCODE: -300; SQLSTATE: 40000)

This has been fixed.

- the REFERENCES clauses of CREATE and ALTER TABLE statement

- the TABLE, [MATERIALIZED] VIEW, PRIMARY KEY, COLUMN and INDEX clauses of the COMMENT ON statement

- DROP and ALTER INDEX statements