Oracle GoldenGate (OGG) on OCI is a fully managed, cloud-native solution for real-time replication between Oracle and non-Oracle databases. But to maintain low-lag, data consistency, and high availability, monitoring performance is critical.
This post lays out a practical, hands-on guide to monitoring GoldenGate performance in OCI and outlines key metrics, tools, and proactive alerting practices.
1. Use the OCI Console for GoldenGate Metrics
Oracle GoldenGate in OCI natively integrates with OCI Monitoring. From the GoldenGate deployment dashboard, you can observe:
- Lag: Seconds of delay between source commit and target apply.
- Throughput: Data volume processed per minute (MB/s or records/s).
- Process health: Extract, replicat, and distribution service status.
Make sure to:
- Tag deployments by environment (Prod, Test)
- Filter metrics by Deployment OCID or compartment
- Configure historical views for trend analysis
2. Monitor the Most Critical Metrics
Focus on the following KPIs:
|
Metric |
Description |
|
Extract Lag |
Delay between source commit and extract checkpoint |
|
Replicat Lag |
Delay between delivery of trail file and target apply |
|
Checkpoint Lag |
Time since last successful checkpoint (in seconds) |
|
Bytes per Second |
Ingested and applied data throughput |
|
Discarded or Abended Records |
Records rejected or failed due to transformation rules |
|
Process Status |
Whether extract/replicat/distribution services are running |
|
Pump Queue Size |
If increasing, indicates bottleneck between extract and replicat |
Set thresholds for alerts, such as:
- Replicat Lag > 30s
- Extract Process down for > 2 minutes
3. Set Up OCI Alarms and Notifications
Use OCI Monitoring + Alarms to detect early warning signals:
- Use Notifications to:
o Send alerts to email, Slack, PagerDuty
o Trigger OCI Functions to restart failed services or tag resources
4. Enable GoldenGate Logging and Diagnostics
Enable enhanced logging to get visibility into:
- Transformation errors
- Mapping issues
- DB connectivity drops
Logs can be integrated with OCI Logging and Logging Analytics:
- Route GoldenGate logs to centralized log groups
- Create custom alerts on specific log patterns (e.g., ORA-, DISCARDED)
5. Use Performance Metrics in Admin UI
GoldenGate deployments in OCI come with a built-in Admin Service UI:
- Monitor individual process health
- Analyze memory and thread usage
- View trail file statistics
- Perform diagnostics on source/target latency
Use this UI during live incidents to trace bottlenecks in end-to-end pipeline.
6. Monitor Network Latency and Load
Since GoldenGate replication is often cross-region or hybrid, monitor:
- Network bandwidth utilization
- Dropped packets or high latency on the VNICs
- Use VNIC Flow Logs and OCI Network Monitoring to validate consistency
Also monitor Load Balancers (if GoldenGate connects through one) for backend health.
7. Apply GoldenGate Performance Tuning Practices
- Enable parallel Replicat for high-volume apply
- Tune trail file sizes and buffer cache
- Adjust checkpoint frequency based on latency tolerance
- Use batch commit intervals for high-throughput targets
- Avoid large uncommitted transactions on source
8. Automate with Service Connector Hub
Stream metrics or logs to:
- Object Storage for archival
- Logging Analytics for deeper insights
- Functions for automated failover or restart
- SIEM platforms (Splunk, ELK) for security correlation
9. Use GoldenGate REST APIs for Custom Dashboards
OCI GoldenGate exposes a rich REST API:
- Query real-time metrics
- Extract health and replication lag data
- Automate restart of failed processes
- Build Grafana dashboards or integrate with existing NOC tools
10. Perform Periodic Lag Audits and Tests
- Simulate controlled load to test replication response time
- Capture lag over time to spot trends or regressions
- Benchmark different replication topologies (hub-spoke, bi-directional, etc.)
GoldenGate is powerful, but it’s only as reliable as your visibility into its operations. Proactive monitoring ensures that latency doesn’t silently grow, replication doesn’t fall behind, and transformations don’t fail unnoticed.
By combining OCI-native monitoring, alarms, structured logging, and performance tuning, you can achieve near-zero latency replication across your data ecosystem.
- GitHub Copilot Coding Agent - May 20, 2025
- Enabling Natural Language Queries in Oracle E-Business Suite with OCI Generative AI - April 20, 2025
- Agentic AI basics – A Simple Introduction - February 8, 2025
