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

MobiLink server warning messages sorted by code Next Page

Alphabetic list of warning messages


%1!lu! row(s) were ignored in uploading data into table %2!s!
%1!s!
'%1!s!'
A conflict detection script is defined for table '%1!s!', but there is no conflict resolution script
A row in table '%1!s!' could not be updated because it no longer exists in the consolidated database
All delete rows for table '%1!s!' will be ignored because there is no upload_delete script for this table
All insert rows for table '%1!s!' will be ignored because there is no upload_insert script for this table
All update rows for table '%1!s!' will be ignored because there is no upload_update script for this table
An error occurred reading the remote client's synchronization log
Client synchronization logs will be shown in the MobiLink server output file or the console
Error detected during multi-row operation, performing rollback before retrying in single row mode
Expecting at most %1!ld! parameter(s) in cursor, but found %2!ld!
For table '%1!s!', the number of entries in the ml_column table is greater than the number of columns in the remote table
Ignoring updated row (new values)
Ignoring updated row (old values)
Maximum number of database connections set to %1!lu! (must be at least the number of database worker threads plus one)
mlstop will not be able to stop this server
MobiLink server has suspended network reads on this synchronization due to a limit on concurrent synchronizations
MobiLink server has swapped memory pages out:%1!d! in:%2!d! concurrent pages:%3!d!
MobiLink server restarted network reads on this synchronization due to a drop in the number of concurrent synchronizations
MobiLink table '%1!s!' is damaged
No handle_error script is defined. The default action code (%1!ld!) will decide the error behavior
ODBC function %1!s! is not supported by the driver
ODBC Isolation level (%1!s!) is not supported
ODBC statement option %1!s! has changed from %2!lu! to %3!lu!
ODBC statement option %1!s! has changed from %2!s! (%3!lu!) to %4!s! (%5!lu!)
Publication '%1!s!' is not referenced by any table
Retrying the begin_connection transaction after deadlock in the consolidated database
Retrying the begin_synchronization transaction after deadlock in the consolidated database
Retrying the end_synchronization transaction after deadlock in the consolidated database
Retrying the upload after conflicting update in the consolidated database
Retrying the upload after deadlock in the consolidated database
Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision, resulting in inconsistent data
Table '%1!s!' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision, defeating download filtering
Table '%1!s!' has no entry in the ml_table table
The client has provided %1!d! authentication parameter(s), but no authenticate_parameters script exists
The command line option '%1!s!' is ignored
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
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)
The ODBC driver '%1!s!' is deprecated
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
The remote client's synchronization log ended prematurely, and was probably truncated
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
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
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'
The update row for table '%1!s!' is a conflict update and this row is ignored
The upload will be committed and the synchronization aborted. The next time this remote synchronizes, it will ask what happened to the previous upload
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
There is no download data script defined for table: %1!s!. Synchronization has the risk of potentially losing download data
There is no upload data script defined for table: %1!s!. Synchronization has the risk of potentially losing upload data
Unable to access Microsoft SQL Server virtual table 'sys.dm_tran_active_transactions'. The MobiLink server will not use snapshot isolation
Unable to access ORACLE table 'v_$transaction'. Access is needed in order to ensure no data is missed if using timestamp-based downloads
Unable to determine current timestamp from consolidated database
Unable to fetch the download timestamp from the consolidated database
Unable to open the file to store the client synchronization logs. The filename is '%1!s!'
Unable to retrieve the column data types for table '%1!s!' from the consolidated database
Unable to write to the local file that contains remote synchronization logs
Unknown users will be added automatically (when there is no authenticate_user script)
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
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
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