6/14/12

About the Monitoring Points

About the Monitoring Points

A monitoring point (abbreviated as MP) is a piece of information that is captured from the Oracle GoldenGate replication solution by the Oracle GoldenGate Monitor Agent. Together, the various monitoring points present an accurate view of the overall status and health of the Oracle GoldenGate environment. When you select an object in the Navigation Tree or Diagram View, the monitoring points that are appropriate for that object are displayed in the Attributes panel.
Monitoring Point Checkpoint Position Description Can be a combination of a series of read checkpoint positions in multiple data source log files, or write checkpoint positions in multiple GoldenGate trail files. The composite checkpoint is that which was written most recently by Capture or Delivery. Capture writes both read and write checkpoints, and Delivery writes only read checkpoints. Each Checkpoint Position consists of an RBA (relative bye address) of a record in the file and a file sequence number. It represents the values of the associated checkpoints that were persisted to disk as the MP was published in shared memory, right after the checkpoint was written. Different databases use different representations of the position of a record in the log. Therefore, instead of numeric values, this MP is published as a string of characters that contains the composite checkpoint in text format encoded in UTF8. For each checkpoint within the composite checkpoint, the checkpoint type, the values of the RBA, file sequence number, and timestamp will be separated by line-feed characters as displayed by the GGSCI SEND <group-name> STATUS command. Valid for Capture, Data Pump, Delivery. Connected End of File Indicates whether the Oracle GoldenGate Monitor Agent is connected to (and monitoring) the selected process. Valid for Capture, Data Pump, Delivery, Manager. Indicates whether or not the selected process has reached the end of the input from its data source (transaction log or trail file). The value can be TRUE (at end of file) or FALSE. Valid for Capture, Data Pump, Delivery. The version of Oracle GoldenGate that the selected Manager instance represents. The version reflects the major, minor, and maintenance version levels. Valid for Manager. The name of the process group that is associated with the selected process. The group name is a logical identifier that also includes the checkpoint file, parameter file, and other files that are associated with a specific instance of a process type. Valid for Capture, Data Pump, Delivery. The name of the system that is selected in the Navigation Tree or Diagram View. The time difference between the Last Operation Timestamp and the Last Processed Timestamp. This MP represents the true lag between the Oracle GoldenGate process and its data source. The lag value in this MP should match the value that is returned from the GGSCI command SEND <group> GETLAG. Valid for Capture, Data Pump, Delivery.

GGS Version Group Name

Host Name Lag

Last Checkpoint Timestamp The time when the last checkpoint was written by the process. Valid for Capture, Data Pump, Delivery. Last Operation Timestamp Last Processed Timestamp The time when an operation (insert, update, delete) was committed in the data source, as recorded in the transaction log. Valid for Capture, Data Pump, Delivery. The time when a valid record was returned to the selected process. For Capture, this time value is assigned when the record is processed after the container transaction
1/3

moonfish.us.oracle.com:5500/monitor/faces/helppages/main.jspx?topic=f1_alert_definition_html&_afrL

6/14/12

About the Monitoring Points

commits (not the time when the record is read from the transaction log). For a Data Pump or Delivery, this time value is returned immediately, because all transactions in the trail are known to be committed. Last Write Timestamp The time when the last buffer of trail records were flushed to the trail file by Capture or a Data Pump, or the time when the last batch of SQL statements were executed against the target database by Delivery. Do not use this attribute to calculate lag. Use the Lag attribute. Valid for Capture, Data Pump, Delivery. The port on which the Manager process is running on its local system. The default port number is 7809, but a different port could be specified for this Manager and can be identified by viewing the Manager parameter file or by issuing the INFO MANAGER command in GGSCI (if Manager is running). Valid for Manager. Inserts, Updates, Deletes, Truncates The total number of insert, update (including primary key updates), delete, or truncate operations that were processed by the selected Oracle GoldenGate process in its current run session. The statistic reflects the total operations performed on all of the tables that are specified in the parameter file for that process. Note: if any tables are mapped to targets in the Capture configuration, the statistics will reflect the total operations for all of the targets. Valid for Capture, Data Pump, Delivery. An event message from the Oracle GoldenGate error log. The name of the selected object. Valid for Trail and Database objects. The total number of active transactions that are being processed by the selected process. These are transactions for which a commit or rollback record has not been processed yet. Valid for Capture, Data Pump, Delivery. The path name of the selected trail, which is appended with the two-character logical name. Valid only for a Trail. A 64-bit Julian GMT timestamp in microseconds that represents the time that an Oracle GoldenGate component receives its startup information after it has been created. Valid for Capture, Data Pump, Delivery, Manager. The run status of the selected process. The value can be Starting, Running, Stopped, Abended, or Aborted. Valid for Capture, Data Pump, Delivery, and Manager. The total number of operations that were discarded by the selected Oracle GoldenGate process in its current run session. The records are written to the discard file for that process. Valid for Capture, Data Pump, Delivery. The total number of DDL operations that were processed by the selected Oracle GoldenGate process in its current run session. Valid for Capture, Data Pump, Delivery. The total number of errors that were ignored by the process in its current run session. Valid for Capture, Data Pump, Delivery. The total number of row fetches that the selected process performed in its current run session. A fetch must be done sometimes to obtain row values when the information is incomplete or absent in the transaction log. Valid for Capture. The total number of row fetches that the selected process was unable to perform in its current run session. Valid for Capture. The total number of transactions that have been processed by the selected process. Valid for Capture, Data Pump, Delivery. The type of database. Examples are Oracle and SQL Server. Valid for Capture, Delivery. The version of the selected database. Valid for Capture, Delivery. The full path name of the directory that contains the executable file for the selected Manager process. This is the home directory of the Oracle GoldenGate installation.
2/3

Manager Port

Mapped Total Mapped Total Mapped Total Mapped Total

Message Name Open Transactions

Path Start Time

Status Total Discards

Total Executed DDLs Total Ignores Total Row Fetch Attempts

Total Row Fetch Failures Total Transactions Type Version Working Directory

moonfish.us.oracle.com:5500/monitor/faces/helppages/main.jspx?topic=f1_alert_definition_html&_afrL