9 Monitor

9.1 Events Tab

The Events tab shows the Message Id, Timestamp, Code, Severity, Message, and details of Oracle GoldenGate events pertaining to corresponding deployment (Deployment, Oracle GoldenGate) or respective processes and services. The Oracle GoldenGate events are displayed for all targets, except the Oracle GoldenGate Service Manager.

The Process column is shown for Oracle GoldenGate target (classic) and Deployment target (MA). These parent targets show cumulative events for the child targets. The Events are in a descending order of event timestamp, ordered by the latest event in the table.

Viewing Event Metrics

By default, this metric is disabled. The Message Id is shown as No Data Available, in case the Event Metric is not enabled. Therefore to view the Event Metric in the UI, you need to enable the metrics. See Enabling/Disabling Metrics to enable and view metric data.

Sort: You can sort the table by clicking on the Message Id, TimeStamp, Code, Severity, and Process columns. All events are displayed in a descending order of event timestamp by default; latest event is displayed on top. By default, 20 events are displayed on a page.

Search: You can search for any string from the events using the Search box. Search is case insensitive and it can be based on any of the following fields: Severity, Error codes, or any message text from the event. For example, if you want to look up for events of Severity ERROR, then only ERROR events are displayed in UI.

Download: Click Export to export all the events. Similarly, in case of Deployment target (MA) and Oracle GoldenGate target (classic), you can view the event messages of all the processes on the Events tab. For more information about setting alerts for Events, see Setting Alerts for Events.

Purge: You can view historical data up to a month. Historical data is purged automatically on a monthly basis. You an modify the retention period of the data. To do this, execute the following in the Oracle Enterprise Manager repository:
 gc_interval_partition_mgr.set_retention('SYSMAN', 'gg_log_events_e', <number of partitions to retain>);
Here, the number of partitions can be 1, 2, 3,…N, where N represents number of months. For more information, see Management Repository Data Retention Policies in Enterprise Manager Cloud Control Administrator's Guide.