By default, the MobiLink server watches the execution time of each SQL script and issues a warning message when the execution
time of the script reaches 10 minutes. Long running scripts are more likely to cause contention and blocking in the consolidated
database, which can significantly reduce overall throughput.
You can use the -tf option to cancel statements that exceed the threshold.
The default value can be reset to zero or a positive integer and its units are in minutes. When it is set to zero, the -tc
option is disabled and the MobiLink server does not watch any script execution.
When the timeout threshold is a non-zero value, the MobiLink server shows the warning message in an exponential way. The warning
is shown when the execution time first passes the time specified; the warning is shown again when the execution time passes
2 times the given time, then 4 times the given time, and so on.
The warning message contains the connection ID used for the current synchronization and a context that includes the following,
if they are available: Remote ID, ML User Name, Modified User Name, Transaction, Table Name, Row Values and Script Version.
The timeout warning context is shown regardless of the verbose settings of the MobiLink server.
When the consolidated database is running on an Oracle database server and the timeout warning message occurs, a database
user with DBA authority may need to check the consolidated database to determine the cause of the problem. The ServiceName
and SERIAL# of the connection used by the synchronization can be found in the warning message. If the synchronization connection
is stopped, the MobiLink server terminates the current synchronization.