sysadmin sqm_unzap_tran
Restores a specific transaction into the stable queue and returns a message stating the number of restored commands.
sysadmin sqm_unzap_tran {, <q_number>, | <server> [,<database>]},
<q_type>, <lqid>
[, {L0 | L1 | L2 | L3}]
[, {RSSD | client | “log” | <file_name>}]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.
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.
The local queue ID of any command of a stable queue transaction. <lqid> identifies the transaction to restore into the stable queue. Format: <seg>,<blk>,<row>.
Dumps the contents of the restored transaction. This is the default behavior if L0, L1, L2, or L3 is not specified.
Dumps only the begin and end commands of the restored transaction.
Dumps the begin and end commands of the restored transaction together with the first 100 characters of the other commands in the restored transaction.
Dumps all the commands of the restored 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.
Forces output to system tables in the RSSD.
Forces output to the client that issued the command.
Forces output to the Replication Server log file.
Forces output to the <file_name> log file. You can also set an alternate log file using the sysadmin dump_file command.
- Restores the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction into the Replication Server log:
sysadmin sqm_unzap_tran, 103, 1, 0, 15, 2
- Restores the transaction of the inbound queue for SYDNEY_DS.<pubs2> with LQID 0:15:2 and dumps the transaction into the Replication Server log:
sysadmin sqm_unzap_tran, SYDNEY_DS, pubs2, 1, 0, 15, 2, “log”
- Restores the transaction of queue 103:1 with LQID 0:15:2 and dumps the begin and end commands of the transaction into the Replication Server log:
sysadmin sqm_unzap_tran, 103,1, 0, 15, 2, L1
- Restores the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction into the Replication Server log. All the commands are truncated at 100 characters:
sysadmin sqm_unzap_tran, 103,1, 0, 15, 2, L2
- Restores the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction into the SYDNEY_RS.log file:
sysadmin sqm_unzap_tran, 103,1, 0, 15, 2, L3, SYDNEY_RS.log
- Restores the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction into the RSSD:
sysadmin sqm_unzap_tran, 103, 1, 0, 15, 2, RSSD
- Restores the transaction of queue 103:1 with LQID 0:15:2 and dumps the transaction to the client:
sysadmin sqm_unzap_tran, 103, 1, 0, 15, 2, client
The Replication Server must be in standalone mode to use sysadmin sqm_unzap_tran.
sysadmin sqm_unzap_tran removes the delete mark from a transaction in a stable queue. Use this command to restore a transaction that you marked deleted using sysadmin sqm_zap_tran.
Use sysadmin dump_queue to locate the transaction you want to restore.
- sysadmin sqm_unzap_tran dumps the restored transaction contents 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.