| SyncChanges Server Runs (danch2520m000) |  |
| use.session.to view the server runs. In other words, the runtime history of the synchronization object. When you start the session, an overview dialog is started. When you double-click a record a details dialog is started. The following fields are displayed in the overview dialog: Synchronization Object (and description). Server Run Run Status (Running, Stopped, or Interrupted) Run Start Time Run End Time Start Commit Time End Commit Time In the details dialog, all relevant server run attributes are displayed. You can run the following commands in the overview and in the details dialog: Check Run Status: use this command to manually refresh the server runs: the server runs are displayed for the current synchronization object again, and a check is performed whether the status of a run is Running. Purge Server Runs: starts the Purge Server Runs (danch2220m000) session. Show Log File: use this command to view the content of the log file. In addition, you can start the Print SyncChanges Server Runs (danch2420m000) session through the Print command.
Fields | Description
Synchronization Object | The synchronization object for which the run was executed.
Server Run | The sequence number of the server run.
Run Status | The server run's current status.
Stopped Because | This field indicates why the server was stopped. Possible values: Not Applicable, Completed, User Intervention, and Error.
Run Start Time | The time at which the server run process was started.
Run End Time | The time at which the server run process was ended.
Start User | The user who started the server run.
End User | The user who stopped the server run.
Bus Component | The bus component (communication channel) that was used to transfer the data.
Start After Transaction ID | This indicates the transaction after which the current run started. If the previous run was stopped or interrupted, the end commit time of the previous run is not accurate enough to continue the next run. In that case the last transaction ID of the previous run is used as the 'transaction to start after' for the current run.
Continue Previous Run | If this check box is selected, the server run continued where the previous run ended. That is: the run started at the first database transaction after the last transaction that was processed by the previous run.
Start Commit Time | The start of the commit time interval specified for the server run. This means that all transactions processed will have a commit time greater than or equal to this start commit time.
End Commit Time | The end of the commit time interval specified for the server run.
First Transaction Processed | The ID of the first transaction that is processed by the server.
Last Transaction Processed | The ID of the last transaction that is processed by the server.
Log File | The path of the log file that is used to log the server's output.
Configuration Library | The configuration library that is used during the server process.
Polling Frequency | The number of times per second the audit trail is checked to detect whether a transaction has occurred.
Buffer Size | The size, in Mb, of the memory that is used to buffer transactions. When this limit is exceeded, the buffering process will swap data to file.
Read Delay | The delay, in seconds, between logging a transaction in the audit files and the reading of the transaction by the synchronization server. A delete delay is only necessary for databases that use 'dirty reads': For more information refer to Read Delay.
Tracing | This check box indicates whether tracing was done. Detailed technical information is stored in Trace File in the synchronization object's Log Folder.
Trace Level | The level of detail for the trace: Low: only events are logged to show the server activity and the processing steps being executed. For each transaction being processed only the transaction ID and commit time is written. Medium: in addition to the events, some transaction data are logged. For the transaction data, only the status at the beginning of the process (just after reading the transaction from the audit trail), the status at the end of the process (just before sending the result to the store), and the status in case of errors are included. High: events and transaction data details are logged. The status of the transaction data after each process step is logged. This can result in a very large trace file.
Trace File | The path of the trace file. This file can be used for trouble-shooting and gives more detailed information than the server log file. It shows the server activity, for example, what transactions were read and how they are processed. It does not only log exceptions, but also transactions that were processed successfully. The amount of data that is stored depends on the Trace Level.