sysadmin skip_bad_repserver

Instructs Replication Server to skip a failed replication definition request the next time Replication Agent starts.

Use sysadmin skip_bad_repserver_cmd with the replication definition change request change process. See Replication Server Administration Guide Volume 1 > Managing Replicated Tables before you use sysadmin skip_bad_repserver_cmd.

Warning! Use sysadmin skip_bad_repserver_cmd carefully. If you execute the command, and then restart the Replication Agent without executing the corrected replication definition command in the primary Replication Server, primary data may replicate using the wrong replication definition version.

Syntax

sysadmin skip_bad_repserver_cmd, pds_name, pdb_name

Parameters

pds_name – The primary data server name.
pdb_name – The primary database name.

Examples

Example 1 – In this example, sysadmin skip_bad_repserver_cmd instructs Replication Server and Replication Agent to skip the last failed replication definition command in the pubs2 database of the SYDNEY_DS data server:
```
sysadmin skip_bad_repserver_cmd, SYDNEY_DS, pubs2
```

Usage

pds_name and pdb_name identify the specific Replication Agent that is affected by the failed replication definition request.
Use sysadmin skip_bad_repserver_cmd to instruct Replication Server to skip a failed replication definition request sent by a Replication Agent. When a replication definition command fails at the primary Replication Server, Replication Agent shuts down. If you restart Replication Agent, the failed command executes again unless Replication Server skips the command. After you execute sysadmin skip_bad_repserver_cmd, execute the corrected replication definition request at the Replication Server before starting the Replication Agent.

Permissions

sysadmin skip_bad_repserver_cmd requires “sa” permission.