Live Reporting in a Unidirectional Replication Environment

Oracle GoldenGate supports homogenous and heterogeneous transfer of data, with capabilities for transformation, filteration, and conversion on either or both systems in the configuration (support varies by database platform). Oracle GoldenGate supports different reporting topologies that enable you to customize the configuration of processes, based on your requirements for scalability, availability, and performance.

Here are some guidelines for choosing a reporting configuration:

  • It is recommended that you use a secondary database to run reports because it reduces the load on the application database, allowing more resources to be available on the replicated database. Another advantage of using Oracle GoldenGate for offloading reporting to a secondary database is that the secondary database can be optimized specifically for those reports.

  • Create additional indexes, use materialized views to replace common joins, use modified storage parameters, or other database tools to ensure the reports run at an optimal speed.

  • Oracle GoldenGate transformation routines can be used to flatten or modify the structure of the data to improve the performance of the reporting server. This becomes popular in a data fabric architecture, which allows the consumer of the real-time data in many open-source Data Warehouse solutions although the original transactional data only exists in traditional/legacy databases. See Consolidation to know more about using additional databaess for generating reports.


Configuration elements for creating a standard reporting configuration in Microservices Architecture

See the Reporting sample script for this scenario to test the reporting and analysis feature of Oracle GoldenGate.