Confirming Suspected Problems

Use sysadmin dump_queue to confirm that a suspected problem exists.

1. Log in to the Replication Server.
2. Execute admin who, sqt.
3. Use the output from admin who, sqt to determine which inbound queue has an open transaction.
   Open transactions appear with the state marked “st:O”. The Info column of this row holds the queue number and type. The transaction state is followed by the number of commands and then a local queue ID for the begin transaction command in the form segment:block:row.
   In the following example of admin who, sqt output, the transaction has a queue number of 103 and a queue type of 1, is in an open state and consists of three commands. The begin transaction command is located in segment 21, block 28, row 0:

   103:1 st:O,cmds:3,qid:21:28:0

4. Dump block 28 of segment 21:

   sysadmin dump_queue, 103, 1, 21, 28, 1, RSSD

   Replication Server writes the text of the commands in block 28 of segment 1 into the rs_queuemsg and rs_queuemsgtxt system tables or into the Replication Server log.
5. If you used the RSSD option, view the command information found in rs_queuemsg:

   select * from rs_queuemsg
     where q_number = 103 and q_type = 1 and
     q_seg = 21 and q_blk=28 and q_row = 0

6. Execute a similar query against rs_queuemsgtxt to obtain the text of the command.