Using sysadmin sqt_dump_queue

Use this command to dump contents of the transaction cache for each inbound queue. sysadmin sqt_dump_queue dumps all the statements of transactions that have not yet been deleted.

Commands are dumped into the Replication Server log or an alternate log file created using the sysadmin dump_file command. In the current version of Replication Server, you cannot dump the transaction cache into the RSSD.

Before using this command, make sure the transaction cache for the database exists using admin who, sqt.

Output from sysadmin sqt_dump_queue shows the state of transactions in the transaction cache: Open, Closed, or Read. Open transactions do not yet have a commit. Closed transactions have a commit but have not yet been completely read. Read transactions have been completely read but have not yet been deleted.

Following is the syntax for the sysadmin dump_queue command:

sysadmin sqt_dump_queue,q_number,q_type,reader [,open]

q_number, q_type – identifies the stable queue to dump. These values can be found by using the admin who command, the admin who, sqm command, and the admin who, sqt command.

reader – identifies the reader you want to dump the stable queue. This parameter applies to features that require multiple readers, such as warm standby applications. You can get the reader number by running admin sqm_readers or admin who, sqt. If you are not using multiple readers, enter “0.”

open – allows you to dump only open transactions. If you use this option, insert a comma before it.

Examples

The following examples demonstrate the use of sysadmin sqt_dump_queue.