FAQ on oracle goldengate from oracle support
FAQ on oracle goldengate from oracle support
Extract process can obtain data
directly from the database transaction logs or from a GoldenGate Vendor Access Module (VAM) where the database
vendor (for example Teradata) will provide the required components that will be
used by Extract to extract the data changes
It can support a number of different business requirements like:
Business Continuity and High Availablity
Data migrations and upgrades
Decision Support Systems and Data Warehousing
Data integration and consolidation
In the absence of Data Pump, the data that the Extract process extracts resides in
memory alone and there is no storage of this data anywhere on the source
system
We also need to enable supplemental logging at the database level otherwise we
will get this error when we try to start the Extract process –
2010-02-08 13:51:21 GGS ERROR 190 No minimum supplemental logging is
enabled. This may cause extract process to handle key update incorrectly if key
column is not in first row piece
commands for enable the suplemental logging
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL)
COLUMNS;
Create The Heartbeat Tables
First, we must set an Oracle GoldenGate GLOBALS parameter that identifies the schema where the heartbeat components will be created. In the source and target OracleGoldenGate installation directory, edit the file GLOBALS and specify the parameter ggschema.
To create the heartbeat objects in the source database, start GGSCI, execute the dblogin command to establish a database connection to the source Pluggable Database, and then execute the add heartbeattable command.
ADD HEARTBEATTABLE [, FREQUENCY number in seconds] [, RETENTION_TIME number in days] | [, PURGE_FREQUENCY number in days]
FREQUENCY
Specifies how often the heartbeat seed table and heartbeat table are updated. For example, how frequently heartbeat records are generated. The default is 60 seconds.
RETENTION_TIME
Specifies when heartbeat entries older than the retention time in the history table are purged. The default is 30 days.
PURGE_FREQUENCY
Specifies how often the purge scheduler is run to delete table entries that are older than the retention time from the heartbeat history . The default is 1 day.
Extract process can obtain data
directly from the database transaction logs or from a GoldenGate Vendor Access Module (VAM) where the database
vendor (for example Teradata) will provide the required components that will be
used by Extract to extract the data changes
It can support a number of different business requirements like:
Business Continuity and High Availablity
Data migrations and upgrades
Decision Support Systems and Data Warehousing
Data integration and consolidation
In the absence of Data Pump, the data that the Extract process extracts resides in
memory alone and there is no storage of this data anywhere on the source
system
We also need to enable supplemental logging at the database level otherwise we
will get this error when we try to start the Extract process –
2010-02-08 13:51:21 GGS ERROR 190 No minimum supplemental logging is
enabled. This may cause extract process to handle key update incorrectly if key
column is not in first row piece
commands for enable the suplemental logging
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL)
COLUMNS;
Create The Heartbeat Tables
First, we must set an Oracle GoldenGate GLOBALS parameter that identifies the schema where the heartbeat components will be created. In the source and target OracleGoldenGate installation directory, edit the file GLOBALS and specify the parameter ggschema.
To create the heartbeat objects in the source database, start GGSCI, execute the dblogin command to establish a database connection to the source Pluggable Database, and then execute the add heartbeattable command.
ADD HEARTBEATTABLE [, FREQUENCY number in seconds] [, RETENTION_TIME number in days] | [, PURGE_FREQUENCY number in days]
FREQUENCY
Specifies how often the heartbeat seed table and heartbeat table are updated. For example, how frequently heartbeat records are generated. The default is 60 seconds.
RETENTION_TIME
Specifies when heartbeat entries older than the retention time in the history table are purged. The default is 30 days.
PURGE_FREQUENCY
Specifies how often the purge scheduler is run to delete table entries that are older than the retention time from the heartbeat history . The default is 1 day.
Comments
Post a Comment