Knowledge on Oracle Goldengate
components of goldengate:
Manager,
Collector,
Extract,
Local trails,
Pump,
Replicat,
Remote trails,
checkpointtable,
Manager & Collector: Manager runs on both Source and Target oracle goldengate home with default port number 7809, we introduce different parameters in manager process, example manager purging rules, auto restart parameters, reporting rules etc. In goldengate, DBA interact with oracle goldengate manager process, we send stop and start ogg process request to manager, manager completes the request. when pump tries to copy trail from source to target server, manager calls collector to receive it, collector allows the pump to flush the trail in to remote trail directory.
we can Implement purging rules in manager process to purge old trails in Trail Directory
purgeoldextracts /local_trail/*, usecheckpoints, minkeepdays 2, frequencyminutes 60
we can Implement Autorestart parameters in manager process, if any process abends it will automatically restart the abended process
autorestart extract e*, retries 10, waitminutes 2, resetminutes 1440
create warning in ggserror.log for critical errors
lagcriticalseconds 30
Extract processes:
Extract works on source database, it collects transactions against source database, write data to local trails, as we know that SCN number of database is equal to commit sequence number CSN of goldengate. we can configure extract at table level & schema level. there are different type of extracts, classic and Integrated extracts. Classic extract works on online redo logs / archive logs to collect transactions against source tables where Integrated extract work's with log mining server to extract data against source tables. we can introduce different type of parameters in EXTRACT parameter file depend on type of replication configuration ( DML/DDL).
to be continued .....
components of goldengate:
Manager,
Collector,
Extract,
Local trails,
Pump,
Replicat,
Remote trails,
checkpointtable,
Manager & Collector: Manager runs on both Source and Target oracle goldengate home with default port number 7809, we introduce different parameters in manager process, example manager purging rules, auto restart parameters, reporting rules etc. In goldengate, DBA interact with oracle goldengate manager process, we send stop and start ogg process request to manager, manager completes the request. when pump tries to copy trail from source to target server, manager calls collector to receive it, collector allows the pump to flush the trail in to remote trail directory.
we can Implement purging rules in manager process to purge old trails in Trail Directory
purgeoldextracts /local_trail/*, usecheckpoints, minkeepdays 2, frequencyminutes 60
we can Implement Autorestart parameters in manager process, if any process abends it will automatically restart the abended process
autorestart extract e*, retries 10, waitminutes 2, resetminutes 1440
create warning in ggserror.log for critical errors
lagcriticalseconds 30
Extract works on source database, it collects transactions against source database, write data to local trails, as we know that SCN number of database is equal to commit sequence number CSN of goldengate. we can configure extract at table level & schema level. there are different type of extracts, classic and Integrated extracts. Classic extract works on online redo logs / archive logs to collect transactions against source tables where Integrated extract work's with log mining server to extract data against source tables. we can introduce different type of parameters in EXTRACT parameter file depend on type of replication configuration ( DML/DDL).
to be continued .....
