Once you have changed the attributes of a database connection, you can resume activity on the connection either in Sybase Central or by using the resume connection command.
To resume a database connection from the command line, enter:
resume connection to data_server.database [skip [n] transaction | execute transaction]
When the connection is resumed, Replication Server retrieves rows from the rs_lastcommit system table so that it can find the correct place in the transaction stream to begin submitting transactions.
The optional skip [n] transaction clause instructs Replication Server skip a specified number of transactions in the connection queue before resuming the connection. The first n transactions are written to the exceptions log.
The skip [n] transaction clause is necessary if the first n transactions cause Replication Server to suspend the connection and the cause of the failure cannot be corrected. For example, the transaction may have produced a data server error that is assigned the retry_stop or stop_replication error action. Or, perhaps it was necessary to use suspend connection and the with nowait clause to manually interrupt the transaction.
WARNING! If you execute resume connection with the skip transaction clause, you must correct any inconsistency that results from the lost transaction. Only use the skip transaction clause when the condition causing the transaction to fail cannot be corrected.
The optional execute transaction clause instructs Replication Server to execute the first transaction in the connection’s queue. Use this clause only when a system transaction has failed to execute. See “Duplicate detection for system transactions” on page 294 in the Replication Server Administration Guide Volume 2 for information about error handling for system transactions.
