Use these attributes to view detailed Q replication receive queue data for the DB2 apply replication server.
Agents The number of Q Apply agents.
Apply Image Name The z/OS image name of the apply server.
Apply Server Name The job name of the apply server.
Apply Site Name The name of the apply site.
Apply Sleep Time The number of milliseconds that Q Apply agents for this receive queue were idle while waiting for work.
Apply System ID The SMF system ID of the apply server.
Apply Workload State The state of the workload as determined by the apply server. The following values are valid:
Available Transactions The number of transactions that are currently being processed by the apply server, but have not yet been applied
Collection Time The date and time of the data sampling. By default, this value is displayed as MM/DD/YY hh:mm:ss, where MM is the month, DD is the day, YY is the year, hh is the hour, mm is the minute, and ss is the second.
Consistency Group Name The name of the consistency group. A consistency group, which is also known as a queue map, is a single send queue and receive queue pair. A workload is made up of one or more consistency groups.
Consistency Group Synchronization State The synchronization state of the consistency group. The following values are valid:
Current Memory The amount of memory in bytes that the Q Apply browser thread used for reading transactions from this queue.
DB2 Apply Server The DB2 subsystem or the DB2 group attach name.
Deadlock Retries The number of times that the Q Apply program reapplied row changes because of lock timeouts and deadlocks.
Heartbeat Latency The average elapsed milliseconds between the time that heartbeat messages were sent by the Q Capture program and the time that they were received by the Q Apply program.
Job Dependencies The number of transactions that are delayed because of job name dependencies.
Key Dependencies The total number of replication key constraints that were detected, forcing transactions to be serialized.
Maximum Available Commit A time stamp that represents the highest source transaction commit time of the transactions that have been read for all consistency groups for this workload.
Memory Full Time The number of seconds that the Q Apply program was unable to build transactions from this receive queue because its agents were using all the available memory to apply transactions.
Minimum Available Commit A time stamp that represents the highest common source transaction commit time across all transactions that have been read for all consistency groups for this workload.
Monster Transactions The number of transactions that exceeded the memory limit for the receive queue that was set in the IBMDB2_RECVQUEUES table.
MQ Bytes Read The number of bytes that were read from this receive queue.
Next Apply Up To Time A time stamp that represents the next stop point for this consistency group. Only transactions with a source transaction commit time up to the value of this time stamp are applied. Transactions are not applied if the source transaction commit time is later than the value of this time stamp.
OKSQLSTATE Errors The number of row changes that caused an SQL error that is defined as acceptable in the OKSQLSTATES field of the IBMQREP_TARGETS table. The Q Apply program ignores these errors.
Oldest Commit LSN The commit log sequence number (LSN) from the source recovery log that corresponds to the oldest transaction that was applied.
Oldest Commit LSN 10 Byte Maximum The commit log sequence number (LSN) from the source recovery log that corresponds to the oldest transaction that was applied. This attribute displays a log sequence number with a maximum length of 10 bytes, for example, 0000:0000:0000:89B3:6919. With DB2 for z/OS Version 11, the size of the log sequence number is greater than 10 bytes and cannot be contained in this attribute. For a log sequence number that is greater than 10 bytes, the value is set to N/A. However, the Oldest Commit LSN attribute displays a log sequence number with a maximum length of 24 bytes.
Oldest Commit Sequence An internal log marker that corresponds to the oldest transaction that was applied.
Oldest Commit Sequence 10 Byte Maximum An internal log marker that corresponds to the oldest transaction that was applied. This attribute displays a log sequence number with a maximum length of 10 bytes, for example, 0000:0000:0000:89B3:6919. With DB2 for z/OS Version 11, the size of the log sequence number is greater than 10 bytes and cannot be contained in this attribute. For a log sequence number that is greater than 10 bytes, the value is set to N/A. However, the Oldest Commit Sequence attribute displays a log sequence number with a maximum length of 24 bytes.
Oldest In-flight Transactions A time stamp that represents the source commit time of the oldest currently in-flight transaction. An in-flight transaction has not been fully applied and committed at the target.
Origin Node The parent node of the workspace.
Queue Depth The number of messages on the queue.
Queue Manager Name The name of the WebSphere MQ queue manager that the Q Apply program uses.
Queue Percent Full The fullness of the queue as a percentage.
Queue Start Time The time stamp at the Q Apply server when the receive queue was started.
Receive Queue Name The name of the receive queue.
RI Dependencies The total number of referential integrity (RI) conflicts that were detected, forcing transactions to be serialized.
RI Retries The number of times that the Q Apply program had to reapply row changes because of referential integrity (RI) conflicts when the transactions that they were part of were executed in parallel.
Rows Applied The number of insert, update, and delete operations from this receive queue that the Q Apply program applied to the target.
Rows Not Applied The number of rows that were unable to be applied and were entered in the IBMDB2_EXCEPTIONS table.
Rows Processed The number of rows that were applied but might not yet be committed to the target.
Rows Read The number of rows that were read from this receive queue.
Spilled Rows The number of rows that the Q Apply program sent to temporary spill queues while targets were being loaded or while Q subscriptions were placed into a spill state by the spillsub parameter of the MODIFY or asnqacmd command.
Spilled Rows Applied The number of spilled rows that were applied to the target.
Transactions Applied The number of transactions from this receive queue that the Q Apply program committed to the target.
Transactions Read The number of transactions that were read from this receive queue.
Transactions Serialized The number of transactions that conflicted with another transaction, because of either a row conflict or a referential integrity conflict. In these cases, the Q Apply program suspends parallel processing and applies the row changes within the transaction in the order that they were committed at the source.
Unique Dependencies The total number of unique index constraints that were detected, forcing transactions to be serialized.
Unique Retries The number of times that the Q Apply program tried to reapply rows that were not applied in parallel because of unique index constraints.
Workload Name The name of the workload.