Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » SQL Anywhere 10 - Error Messages » MobiLink Server Warning Messages

Introduction to MobiLink synchronization server warning messages Next Page

MobiLink server warning messages sorted by code


Warning code

Level

Warning Message

10001

1

Maximum number of database connections set to %1!lu! (must be at least the number of database worker threads plus one)

10003

1

ODBC Isolation level (%1!s!) is not supported

10004

1

ODBC function %1!s! is not supported by the driver

10005

1

ODBC statement option %1!s! has changed from %2!s! (%3!lu!) to %4!s! (%5!lu!)

10006

1

ODBC statement option %1!s! has changed from %2!lu! to %3!lu!

10007

2

Retrying the begin_connection transaction after deadlock in the consolidated database

10009

2

MobiLink table '%1!s!' is damaged

10010

2

No handle_error script is defined. The default action code (%1!ld!) will decide the error behavior

10012

2

The consolidated and remote databases disagree on when the last synchronization took place. The remote is being asked to send a new upload that starts at the last known synchronization point

10014

4

Expecting at most %1!ld! parameter(s) in cursor, but found %2!ld!

10015

3

Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision, defeating download filtering

10016

3

Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision, resulting in inconsistent data

10017

3

The consolidated and remote databases have different timestamp precisions. Consolidated database timestamps are precise to %1!d! digit(s) in the fractional second while the remote database timestamps are precise to %2!d! digit(s)

10018

3

The timestamp precision mismatch may be resolved by setting the DEFAULT_TIMESTAMP_INCREMENT option on the remote database to %1!d! and TRUNCATE_TIMESTAMP_VALUES to 'On'

10019

3

The remote database is not capable of matching the timestamp precision of the consolidated database. Your application, schema, and scripts must contain logic that copes with the precision mismatch

10020

3

The timestamp precision mismatch may affect upload conflict detection. Use the -zp option to cause the MobiLink server to use the lowest timestamp precision for conflict detection purposes

10021

3

The remote and consolidated databases have different timestamp precisions, and a timestamp value with a precision higher than the lower-precision side was used for conflict detection purposes. Consider using the -zp option

10022

3

Publication '%1!s!' is not referenced by any table

10023

3

The upload will be rolled back and the synchronization aborted. The next time this remote synchronizes, it will ask what happened to the previous upload

10024

3

Table '%1!s!' has no entry in the ml_table table

10032

2

Unable to open the file to store the client synchronization logs. The filename is '%1!s!'

10033

2

An error occurred reading the remote client's synchronization log

10034

2

Unable to write to the local file that contains remote synchronization logs

10035

2

The remote client's synchronization log ended prematurely, and was probably truncated

10036

2

Client synchronization logs will be shown in the MobiLink server output file or the console

10037

5

Ignoring updated row (new values)

10038

5

Ignoring updated row (old values)

10039

2

Error detected during multi-row operation, performing rollback before retrying in single row mode

10040

2

%1!lu! row(s) were ignored in uploading data into table %2!s!

10041

2

The upload will be committed and the synchronization aborted. The next time this remote synchronizes, it will ask what happened to the previous upload

10043

4

Unable to determine current timestamp from consolidated database

10044

5

A row in table '%1!s!' could not be updated because it no longer exists in the consolidated database

10045

2

Retrying the upload after deadlock in the consolidated database

10048

2

Retrying the begin_synchronization transaction after deadlock in the consolidated database

10049

2

Retrying the end_synchronization transaction after deadlock in the consolidated database

10050

4

%1!s!

10051

1

Unrecognized ODBC driver '%1!s!'. The functionality and quality of ODBC drivers varies greatly. This driver may lack functionality required for successful synchronizations. Use at your own risk

10055

2

The client has provided %1!d! authentication parameter(s), but no authenticate_parameters script exists

10056

4

There is no download data script defined for table: %1!s!. Synchronization has the risk of potentially losing download data

10057

4

There is no upload data script defined for table: %1!s!. Synchronization has the risk of potentially losing upload data

10064

1

Unknown users will be added automatically (when there is no authenticate_user script)

10066

1

mlstop will not be able to stop this server

10068

5

'%1!s!'

10069

5

All insert rows for table '%1!s!' will be ignored because there is no upload_insert script for this table

10070

5

All update rows for table '%1!s!' will be ignored because there is no upload_update script for this table

10071

5

All delete rows for table '%1!s!' will be ignored because there is no upload_delete script for this table

10072

5

The update row for table '%1!s!' is a conflict update and this row is ignored

10073

1

Windows XP Firewall is enabled, and the MobiLink server is not in the exception list. Clients on remote machines may not be able to connect to this server

10074

4

Unable to fetch the download timestamp from the consolidated database

10075

1

Unable to access ORACLE table 'v_$transaction'. Access is needed in order to ensure no data is missed if using timestamp-based downloads

10076

5

A conflict detection script is defined for table '%1!s!', but there is no conflict resolution script

10077

1

You are using a DSN created using an out-of-date ODBC driver '%1!s!'. Please use a DSN created with a recommended driver described at http://www.ianywhere.com/developer/technotes/odbc_mobilink.html

10078

1

Unable to access Microsoft SQL Server virtual table 'sys.dm_tran_active_transactions'. The MobiLink server will not use snapshot isolation

10079

1

The command line option '%1!s!' is ignored

10080

5

Retrying the upload after conflicting update in the consolidated database

10081

3

Unable to retrieve the column data types for table '%1!s!' from the consolidated database

10082

1

MobiLink server has swapped memory pages out:%1!d! in:%2!d! concurrent pages:%3!d!

10083

1

MobiLink server has suspended network reads on this synchronization due to a limit on concurrent synchronizations

10084

1

MobiLink server restarted network reads on this synchronization due to a drop in the number of concurrent synchronizations

10085

1

For table '%1!s!', the number of entries in the ml_column table is greater than the number of columns in the remote table

10086

1

The ODBC driver '%1!s!' is deprecated