sysadmin sqm_zap

Deletes a specific transaction from the stable queue and returns a message stating the number of deleted commands.

Syntax

sysadmin sqm_zap_tran {, q_number, | server [,database]},
        q_type, lqid 
        [, {L0 | L1 | L2 | L3}]
        [, {RSSD | client | “log” | file_name}]

Parameters

q_number | server[, database] – Identifies the stable queue. Use either q_number or server[, database] to specify the queue number. You can use admin who, admin who, sqm, and admin who, sqt to identify the queue number.
q_type – The queue type of the stable queue. Values are “0” for outbound queues and “1” for inbound queues. Use admin who, admin who, sqm, and admin who, sqt to identify the queue type.
lqid – The local queue ID of any command of a stable queue transaction. lqid identifies the transaction to delete from the stable queue. Format: seg,blk,row.
L0 – Dumps the contents of the deleted transaction. This is the default behavior if L0, L1, L2, or L3 is not specified.
L1 – Dumps only the begin and end commands of the deleted transaction.
L2 – Dumps the begin and end commands of the deleted transaction together with the first 100 characters of the other commands in the deleted transaction.
L3 – Dumps all the commands of the deleted transaction. All other commands are printed as comments, except for SQL statements. You can use L3 only when you use the file_name option or the sysadmin dump_file command to specify an alternate log file. You cannot use L3 with RSSD or client options.
RSSD – Forces output to system tables in the RSSD.
client – Forces output to the client that issued the command.
"log" – Forces output to the Replication Server log file.
file_name – Forces output into the file_name log file. You can also set an alternate log file using the sysadmin dump_file command.

Examples

Example 1 – Deletes the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction to the Replication Server log:
```
sysadmin sqm_zap_tran, 103, 1, 0, 15, 2
```
Example 2 – Deletes the transaction of the inbound queue for SYDNEY_DS.pubs2 with LQID 0:15:2 and dumps the transaction to the Replication Server log:
```
sysadmin sqm_zap_tran, SYDNEY_DS, pubs2, 1, 0, 15,
     2, “log”
```
Example 3 – Deletes the transaction of queue 103:1 with LQID 0:15:2 and dumps the begin and end commands of the transaction to the Replication Server log:
```
sysadmin sqm_zap_tran, 103,1, 0, 15, 2, L1
```
Example 4 – Deletes the transaction of queue 103:1 with lqid 0:15:2 and dumps the transaction to the Replication Server log. All the commands are truncated at 100 characters:
```
sysadmin sqm_zap_tran, 103,1, 0, 15, 2, L2
```
Example 5 – Deletes the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction to the SYDNEY_RS.log file:
```
sysadmin sqm_zap_tran, 103,1, 0, 15, 2, L3,
     SYDNEY_RS.log
```
Example 6 – Deletes the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction to the RSSD:
```
sysadmin sqm_zap_tran, 103, 1, 0, 15, 2, RSSD
```
Example 7 – Deletes the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction to the client:
```
sysadmin sqm_zap_tran, 103, 1, 0, 15, 2, client
```

Usage

The Replication Server must be in standalone mode to use sysadmin sqm_zap_tran.
Use sysadmin dump_queue to locate the transaction you want to delete.
sysadmin sqm_zap_tran marks a transaction in a stable queue as deleted. When Replication Server processes the queue, it ignores the marked transaction.
You can restore a transaction using sysadmin sqm_unzap_tran. The sysadmin sqm_unzap_tran command removes the delete mark from the transaction.
If you delete a transaction and then restart Replication Server in normal mode, the part of the queue holding the transaction may have been processed. If it was, you cannot restore the transaction with sysadmin sqm_unzap_tran.
sysadmin sqm_zap_tran dumps the transaction marked for deletion into one of these:
- Replication Server log
- Alternate log file
- RSSD
- Client issuing the command
To dump queues into the RSSD or client, the last argument of sysadmin dump_queue must be RSSD or client.

If the RSSD or client option is not specified, or if the "log" option is specified, output goes into the Replication Server log.

If an alternative log file for dumping queues is specified through the sysadmin dump_file command or through the file_name option, the output goes into the alternative dump file.

Permissions

sysadmin sqm_zap_command requires “sa” permission.