After the tables are synchronized, you can view the progress of the synchronization using the message log files you created with each command line, serverOut.txt, rem1.txt, and rem2.txt. The default location of these files is the directory where the command was run.
To detect errors in your MobiLink synchronization server log fileOpen your log file in a text editor. For this tutorial, the log file is serverOut.txt.
Scan down the left side of the file. A line beginning with I. contains an informational message, and a line beginning with E. contains an error message.
To detect errors in your MobiLink synchronization client log fileOpen a client log file, such as rem1.txt or rem2.txt, in a text editor.
Search the file for the string COMMIT. If it appears, your synchronization was successful.
Search the file for the string ROLLBACK. If the transaction was rolled back, there were errors that prevented it from completing.
Scan down the left side of the file. An error has occurred if you see a line that begins with an E.. Your synchronization has completed successfully if your log file does not contain errors.
ExampleThe following example shows sample error messages that you could encounter when reviewing the MobiLink server log:
E. 2010-04-12 14:49:14. Error code from MobiLink server: -10355 E. 2010-04-12 14:49:14. Server error: Message: The table 'Product' has no upload_update script. Table Name: Product |
This message indicates that an error has occurred before data could be uploaded. The message implies that the required upload_update script does not exist in the Product synchronization table of the consolidated database.
Further readingFor more information about MobiLink log files, see Logging MobiLink server actions.
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0 |