Send Queue

Use this page to monitor important statistics about the send queue for the selected ER node and its target nodes and replicates.

ER collects information from the logical logs and places the data to be transferred in the send queue.

The send queue resides in memory and is managed by the Reliable Queue Manager (RQM). The CDR_QUEUEMEM configuration parameter specifies the amount of memory in the space that is available for the data queues.

• Send Queue Statistics: This section shows detailed information about the send queue at the current ER node.
  • Transactions in Queue: The total number of transactions that are waiting to be sent to the target node. This value is the total of transactions in memory and transactions spooled.
  • Transactions in Memory: Transactions that are in the queue memory.
  • Transactions Spooled: Transactions that have been spooled to disk because the queue memory was full or the replicate is suspended.
  • Memory in Use: The current amount of memory used by data.
  • Capture Log Position: The position in the logical log that was last read and where data was last capture for replication..
  • Last Data Acknowledged: The position in the logical log of the last data applied at the target node.
  • Pending Acknowledgements: The number of acknowledgements received from target nodes that are waiting for processing by the source node.
  • Suspended Nodes: The number of nodes that are in a suspended state. When a node is in a suspended state, ER captures and accumulates changes to the source database, but does not transmit the data to the target database. Data synchronization is required to restart replication.
  • Total Transactions Queued: The number of complete transactions that have been queued at this node.
  • Total Data Queued: The cumulative total of data that has been queued at this node.
  • Total Transactions Spooled: The number of transactions ever spooled to disk at a time.
  • Maximum Memory Data: The maximum amount of space used in memory, at one time, for transaction data.
  • Maximum Memory Headers: The maximum amount of space used in memory for transaction headers.
• Target Nodes: This tab displays a list of target nodes to which the current server replicates data.
  • Target Node: Name of the partner node to which the current node is sending transactions.
  • Connection State: The state of the connection to the peer node; possible values are:
    • INIT
    • INTR
    • ABORT
    • SHUT
    • SLEEP
    • RUN
    • STOP
    • TIMEOUT
    • BLOCK
    • SUSPEND
  • NIF State: The network information state; possible values are:
    • Never Connected
    • Disconnected
    • Timeout
    • Logic error
    • Start error
    • Admin close
    • Connected
    • Connecting
    • Local server
  • Last Data ACKed: The log position on the source node for the last data sent and acknowledged by a target node.
• Replicates: This tab displays a list of the defined replicates for the ER node.
  • Replicate Name: The name of the replicate that defines the relationship of the source node with the target node.
  • Target Node: The nodes defined in the replicate where data is to be applied.
  • Last Data Acknowledged: The log position on the source node for the last data sent and acknowledged by a target node.