Introduction of Oracle Golden Gate Job Support:
Get Oracle GoldenGate Job Support today by IDESTRAININGS! It is the perfect platform from India to provide job support services. In the early stages of your career, you are given plenty of projects that you cannot handle all alone.
If you need professional job support from India, join in VJS, and then you will not only help complete your project or work, but will provide you with effective job support to solve such cases in the future.
If you want to know more info about Oracle GoldenGate job support? First, let you know briefly about Oracle Golden Gate. Oracle GoldenGate Job Support is used as the duplicate data of various platforms. It is used to capture or transfer or extract the data from the source database.
Overview of Oracle GoldenGate Job Support: Topologies of Oracle GoldenGate Job Support
- Uni-directional: Data is replicated in one direction from source to target
- Bi-Directional: The data flows in both direction and stays synced up between site A and site B
- Peer to Peer: Similar to Bi-directional but involves more that 2 databases which stay synced up
- Broadcast: Data from source is sent to multiple destinations
- Consolidation: Data from multiple sources is delivered to one destination DB
- Cascading: Data from one source is sent to multiple destination
GoldenGate Components
Manager: This process is for creating other Golden gate processes. This is used as source of running the target configuration and finding new Golden gate process. The manager process also manages the disk space by clearing the old file files. Each Golden gate installation requires only one managerial process.
Extract: Extract the DDL transactions from Oracle Redo Logs and the Extract of the DDL. The Extract then writes these data changes as trail or extracts files
Data Pump: The pump process option is also an extracted process in the Golden Gate Setup. This process copies the trail files that contain data for the target system.
Replicat: The process of reflection in the Golden Gate Configuration is applicable. This process runs at the end of the data delivery chain in the target database. This approach reads the target tracking files and applies data changes to target systems.
Trail/Extract Files: The source database creates trial files for use in the pump system for transferring to remote databases or using a local copy in the source database.
Checkpoint: The Extract Pump to track the progress of these processes & the impersonation processes use check points. This policy refers in the Oracle DBA and in the location where the data has changed or applied from the trail files. This can be useful when restoring the process or finding the starting point after failure.
Collector: The collector system runs on the target system and writes data changes from the root database in the target trail file called RMTTRAIL. It will reboot files before copying it to RMTTRAIL