sysadmin dump_tran

Description

Dumps the statements of a specific stable queue transaction into a log file.

Syntax

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

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 dump. Format: seg,blk,row.

num_cmds: Specifies the number of commands to dump.

L0: Dumps the contents of the specified 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 specified transaction.

L2: Dumps the begin and end commands of the specified transaction, together with the first 100 characters of the other commands in the transaction.

L3: Dumps all the commands of the specified 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 the 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 the output into the file_name log file. You can set an alternate log file using the sysadmin dump_file command.

"next"[, num_cmds]: This option continues the last run of sysadmin dump_tran. “next"[, num_cmds] starts from where the last run of sysadmin dump_tran for a particular transaction left off, and dumps the same number of commands that the last run did. You can use num_cmds to override the value of previous cnt or num_cmds.

You cannot use "next"[, num_cmds] without a prior invocation of sysadmin dump_tran.

Examples

Example 1

Dumps the transaction of queue 103:1 with LQID 0:15:2 into the Replication Server log:

sysadmin dump_tran, 103, 1, 0, 15, 2

Example 2

Dumps 10 commands of the transaction of the inbound queue for SYDNEY_DS.pubs2 with LQID 0:15:2 into the Replication Server log:

sysadmin dump_tran, SYDNEY_DS, pubs2, 1, 0, 15, 2,
     10, “log”

Example 3

Dumps only the begin and end commands of the transaction of queue 103:1 with LQID 0:15:2 into the Replication Server log:

sysadmin dump_tran, 103,1, 0, 15, 2, L1

Example 4

Dumps all of the commands of the transaction of queue 103:1 with LQID 0:15:2 into the Replication Server log. All the commands are truncated at 100 characters:

sysadmin dump_tran, 103,1, 0, 15, 2, L2

Example 5

Dumps the transaction of queue 103:1 with LQID 0:15:2 into the SYDNEY_RS.log file:

sysadmin dump_tran, 103,1, 0, 15, 2, L3, SYDNEY_RS.log

Example 6

Dumps the transaction of queue 103:1 with LQID 0:15:2 into the RSSD:

sysadmin dump_tran, 103, 1, 0, 15, 2, RSSD

Example 7

Dumps transaction of queue 103:1 with LQID 0:15:2 to the client:

sysadmin dump_tran, 103, 1, 0, 15, 2, client

Example 8

Dumps, in chunks, the transaction of queue 103:1 with LQID 0:15:2 into the Replication Server log. "next" dumps the transaction from where the last run of sysadmin dump_tran left off. In this example, the first call to sysadmin dump_tran dumps the first 10 commands of the transaction, the second call dumps the next 10 command of the transaction, and the last call dumps the next 20 commands of the transaction:

sysadmin dump_tran, 103,1, 0, 15, 2, 10 
sysadmin dump_tran, “next”
sysadmin dump_tran, “next”, 20

Usage

Use sysadmin dump_tran to dump the contents of a stable queue transaction identified by the LQID.
Output from sysadmin dump_tran goes to one of the following:
- Replication Server log
- Alternate log file
- RSSD
- Client issuing the command
To dump a stable queue transaction into the RSSD or a client, the last argument of sysadmin dump_tran must be RSSD or client.

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

If an alternative log file for dumping the stable queue transaction is specified through the sysadmin dump_file command or through the file_name option, the output goes to the alternative dump file.
Specify the maximum sysadmin dump_tran command length by setting the queue_dump_buffer_size configuration parameter.

Dumping to the RSSD

If the RSSD option is used, the dump is written in two system tables in the RSSD, rs_queuemsg and rs_queuemsgtxt.

If the transaction is dumped to the RSSD, the system tables are first cleared of the segments with the same q_number, q_type, seg, and blk as the transaction being dumped.

For information about the contents of the rs_queuemsg system table, see Chapter 8, “Replication Server System Tables.”

The rs_queuemsgtxt system table holds the text of commands dumped from the stable queue. If the text of a command exceeds 255 characters, it is stored in multiple rows numbered with the q_seq column.

Dumping to the client

If the client option is used, the dump is written to the client issuing the command, such as isql or Replication Server Manager.

Permissions

sysadmin dump_tran requires “sa” permission.