Client :: startPause - Pause Server
When pausing the server no more transactions can be committed until pausing the server is stopped ( stopPause() ). The server will pause after all running transactions have been finished (commit or rollback).
Pause functions can be used for keeping the database in a consistent state while backing up the database without closing the server. Pause commands should not be used when running long transactions as large imports or database reorganization.
Transactions will not be committed anymore after pausing the server. The timeout interval for committing transactions is 10 minutes. When not being able to start committing the transaction within the timeout interval the transaction is canceled.
Any application may access the database in the pause state as long as not writing to the database, i.e. as long as not storing transactions to the database.
For allowing storing data to the database again you must use the StopPause () function.
Implementation overview
- Pause server after 5 minutes
Client :: startPause ( ) - Pause server after application-defined timeout
Client :: startPause ( iWait )
Implementation details
-
Pause server after 5 minutes
Client :: startPause ( )
When there is any transaction still running after 5 minutes, the server will not pause and the function throws an exception. When expecting long transactions, a timeout interval should be passed ( startPause( iWait ) ).
to list
-
Pause server after application-defined timeout
Client :: startPause ( int32 iWait )
When there is any transaction still running after the time interval passed in iWait , the server will not pause and the function throws an exception.
- iWait
- Number of seconds to wait
The system waits the given number of seconds before executing the request.
to list
- iWait
- Number of seconds to wait