resume connection

Description

Resumes a suspended connection.

Syntax

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

Parameters

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

database: The name of the database whose connection is to be resumed.

skip [n] transaction: Instructs Replication Server to skip a specified number of transactions in the connection queue before resuming the connection. The skipped transactions are written to the database exceptions log, and to either the Replication Server log or the alternative log file specified by the sysadmin dump_file command. The maximum number of transactions that resume connection can skip is the number of transactions in the DSI outbound queue.

If n is not specified, Replication Server resumes execution with the second transaction in the connection’s queue.

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.

Examples

Example 1

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

resume connection to SYDNEY_DS.pubs2

Example 2

Resumes the connection to the pubs2 database in the SYDNEY_DS dataserver after skipping two transactions. The transactions are logged in the database exceptions log and the Replication Server log:

resume connection to SYDNEY_DS.pubs2 skip 2 transaction

Example 3

Resumes the connection to the pubs2 database in the SYDNEY_DS dataserver after skipping two transactions. The transactions are logged in the database exceptions log and in the SYDNEY_RS.log file. The last sysadmin dump_file command closes the SYDNEY_RS.log file:

sysadmin dump_file SYDNEY_RS.log
resume connection to SYDNEY_DS.pubs2 skip 2 transaction
sysadmin dump_file

Usage

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.

Permissions

resume connection requires “sa” permission.