resume connection

Resumes a suspended connection.

resume connection
 to data_server.database
[skip transaction | execute transaction]

data_server: The name of the data server that holds the database whose connection is to be resumed.

skip transaction: instructs Replication Server to resume execution with the second transaction in the connection’s queue. The first transaction is written to the database exceptions log.

execute transaction: overrides the Replication Server restriction against the application of system transactions after a DSI startup if the system transaction is the first transaction in the DSI queue.

Resumes the connection to the pubs2 database in the SYDNEY_DS data server:

resume connection to SYDNEY_DS.pubs2

Resuming a connection allows replication activities for the suspended database to begin again.
Suspend connections so you can alter them with alter connection or perform maintenance on the suspended database. Connections are also suspended during subscription materialization or dematerialization.
Replication Server can suspend a database connection because of an error.
resume connection is also used to resume a connection suspended because of an error.
If you determine that the system transaction was executed, use the skip transaction clause.
Use the execute transaction clause only if a system transaction has failed to execute and you have corrected the problem that prevented its execution. A system transaction has no enclosing begin tran/commit tran pair. If Replication Server is restarted with a system transaction as the first transaction, you see this message:
```
E. 1998/02/16 14:43:49. ERROR #5152 DSI (206 hookip01.rdb1) - dsisched.c (2196)
 There is a system transaction whose state is not known. DSI will be shut down.
```
Determine whether the database has executed this transaction and use skip transaction or execute transaction as appropriate.

resume connection requires “sa” permission.