%1
%1 row(s) were ignored in uploading data into table %2
<OE>: %1
'%1'
A passthrough script failed at the remote client, run_order: %1, script_id: %2, error_code: %3, error_text: '%4'
An error occurred reading the remote client's synchronization log
Client synchronization logs will be shown in the MobiLink server message log file or the MobiLink server messages window
Either %1 does not exist or it does not contain any recorded protocol files (files with extension mlr)
Error detected during multi-row operation, performing rollback before retrying in single row mode
Expecting at most %1 parameter(s) in cursor, but found %2
For table '%1', the number of entries in the ml_column table is greater than the number of columns in the remote table
Initial cache size is smaller than the minimum cache size. Increasing initial size to %1 bytes
Initial cache size is too small. Increasing from %1 to %2 bytes
Invalid log verbosity options: '%1'
Loading a client Java VM
Maximum cache size is smaller than the initial cache size. Increasing maximum size to %1 bytes
Maximum cache size is too small. Increasing from %1 to %2 bytes
Maximum number of database connections set to %1 (must be at least the number of database worker threads)
Minimum cache size is too small. Increasing from %1 to %2 bytes
MobiLink server has suspended network reads on this synchronization due to a limit on concurrent synchronizations
MobiLink server has swapped data pages to disk out:%1 in:%2 concurrently used pages:%3
MobiLink server restarted network reads on this synchronization due to a drop in the number of concurrent synchronizations
MobiLink table '%1' is damaged
No handle_error script is defined. The default action code (%1) will decide the error behavior
No RTNotifier was started. Therefore, no remote tasks will be received by any agents
ODBC function %1 is not supported by the driver
ODBC Isolation level (%1) is not supported
ODBC statement option %1 has changed from %2 (%3) to %4 (%5)
ODBC statement option %1 has changed from %2 to %3
Performance warning -- database connections have been recycled at a rate of %1%%
Publication '%1' is not referenced by any table
Resolve the timestamp precision mismatch by setting the SQL Anywhere DEFAULT_TIMESTAMP_INCREMENT option on the remote database
to %1 and TRUNCATE_TIMESTAMP_VALUES to 'On'. UltraLite remotes must set the TIMESTAMP_INCREMENT option to %2
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
Spatial library warning: '%1'
Synchronization request from client '%1' was rejected
Table '%1' has at least one timestamp column. Due to a timestamp precision mismatch, downloaded timestamps can lose precision,
resulting in inconsistent data
Table '%1' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision,
defeating download filtering
The client has provided %1 authentication parameter(s), but no authenticate_parameters script exists
The command line option '%1' is ignored
The conflict detection and resolution approach used by table '%1' is deprecated
The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are %1 in
the consolidated database and %2 in the remote database. 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 digit(s) in the fractional second while the remote database timestamps are precise to %2 digit(s)
The current SQL statement has been running for too long in the consolidated database. The connection ID is %1
The following option has been deprecated: %1
The forced conflict resolution approach for table '%1' is deprecated
The MobiLink server is currently running with -zf that will reduce its performance
The MobiLink server will record all synchronizations
The ODBC driver '%1' 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 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
The Z/M values were dropped from the upload spatial data
There are too many remote tasks to send to agent, %1, at one time. The maximum number of remote tasks an agent can receive
at one time is 255
Unable to access ASE table 'master..systransactions'. The MobiLink server will use system time for download
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 'gv$transaction'. Access is needed 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 lock the remote ID '%1', will try again
Unable to open the file to store the client synchronization logs. The filename is '%1'
Unable to record the schema
Unable to retrieve the column data types for table '%1' 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'. 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
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0 |