Delete Transactions from the Exceptions Log

Use stored procedures to delete transactions from the RSSD exceptions log.

rs_delexception – deletes a single transaction from the exceptions log. The syntax is:
```
rs_delexception [transaction_id]
```
With no parameters, rs_delexception displays a summary of transactions in the exceptions log. If you supply a valid transaction_id, rs_delexception deletes a transaction. You can find the transaction_id for a transaction by using either rs_helpexception or rs_delexception with no parameters.
For example, to delete the transaction with ID number 1234, enter:
```
rs_delexception 1234
```
rs_delexception_id – deletes a range of transactions identified by transaction ID. The syntax is:
```
rs_delexception_id transaction_id_start [,transaction_id_end]
```
For example, to delete all transactions with ID numbers between 1234 and 9800, inclusive,enter:
```
rs_delexception_id 1234, 9800
```
rs_delexception_date – deletes a range of transactions identified by transaction date. The syntax is:
```
rs_delexception_date transaction_date_start [,transaction_date_end]
```
For example, to delete from the exceptions log all transactions that have originating dates between 1st October 2010 and 31st October 2010, inclusive, enter:
```
rs_delexception_date "10/01/2010", "10/31/2010"
```
rs_delexception_range – deletes a range of transactions identified by originating site or user, or destination site. The syntax is:
```
rs_delexception_range 
{{"origin"|"org"}, "origin_data_server.origin_database" | 
, {"destination"|"dest"}, "destination_data_server.destination_database" | 
, "user", "origin_user"}
```
For example, to delete from the exceptions log the transactions that originated from the south_db database of the SYDNEY_DS data server, enter:
```
rs_delexception_range "org", "SYDNEY_DS.south_db"
```

See the descriptions of the stored procedures in Replication Server Reference Manual > RSSD Stored Procedures for complete usage information and more examples.