Improved Stable Queue Management

Replication Server 15.1 simplifies stable queue management.

Enhanced queue dump commands provide flexibility in identifying the stable queues, controlling the stable queue contents to dump, and supporting additional output file options. Replication Server 15.1 also includes new commands that allow you to delete and restore specific transactions from the Stable Queue Manager (SQM).

For more information about the stable queue management, see the Replication Server Administration Guide Volume 1. For details about the following commands, see the Replication Server Reference Manual.

• Changes to sysadmin dump_queue
  The sysadmin dump_queue syntax has been modified to provide flexibility to stable queue management.
• Changes to sysadmin sqt_dump_queue
  The sysadmin sqt_dump_queue syntax has been modified to provide flexibility to stable queue management.
• Modified resume connection Command
  The resume connection skip transaction option has been enhanced to support skipping a specified number of transactions in the connection queue before resuming the connection.
• Modified sysadmin log_first_tran Command
  A new option n has been added to the sysadmin log_first_tran command. Use the new option to specify the number of transactions to write to the database exceptions log, and to either the Replication Server log or the alternative log file specified by the sysadmin dump_file command.
• New sysadmin sqm_zap_tran Command
  sysadmin sqm_zap_tran deletes a specific transaction from the stable queue and returns a message stating the number of deleted commands. The transaction is identified through the local queue ID (LQID).
• New sysadmin sqm_unzap_tran Command
  sysadmin sqm_unzap_tran restores a transaction in the stable queue and returns a message stating the number of restored transaction commands. The transaction is identified through the LQID.
• New sysadmin dump_tran Command
  Use sysadmin dump_tran to dump the statements of a specific stable queue transaction into a log file. The transaction is identified through the LQID.