9.1.1 Overview
HEARTBEATTABLE
for Oracle GoldenGate for
Distributed Applications and Analytics (GG for DAA), you need to:
- Specify
GGSCHEMA
inGLOBALS
with any value, for example,GGSCHEMA GGADMIN
. - Enable
ENABLE_HEARTBEAT_TABLE
inGLOBALS
. - Execute
ADD HEARTBEATTABLE
fromGGSCI
.
In Oracle GoldenGate for RDBMS, the HEARTBEATTABLE
records are applied
to the following target HEARTBEATTABLE
tables:
GGADMIN.GG_HEARTBEAT
and
GGADMIN.GG_HEARBEAT_HISTORY
.
Two Modes of HEARTBEATTABLE
in GG for DAA:
In Mode 1 (as user data), the records that are handled by GG for DAA are
written to HEARTBEATTABLE
files. For example, table
GGADMIN.GG_HEARTBEAT
is stored in file dirtmp/<replicat
name>-hb.json
. Here, the records are written to the replicat file
hb.json.
Table GGADMIN.GG_HEARTBEAT_HISTORY
is
stored in dirtmp/<replicat-name>hb <date>.json
. Here, the
History records re written to thehb-<date>.json
file.
To apply HEARTBEATTABLE as user data:
- Disable
HEARTBEATTABLE
by specifyingDISABLEHEARTBEATTABLE
in the replicat parameter file. - Specify
HEARTBEATTABLE
tables in the replicat MAP statements:MAP GGADMIN.GG_HEARTBEAT, TARGET GGADMIN.GG_HEARTBEAT; MAP GGADMIN.GG_HEARTBEAT_HISTORY, TARGET GGADMIN.GG_HEARTBEAT_HISTORY;
When applied as user data, the HEARTBEAT
records
GG_HEARTBEAT
and GG_HEARTBEAT_HISTORY
are
written to the handler as if they are user tables. The HEARTBEAT
records are not stored in tables like RDBMS, but in .json
files.
Mode 2 (as passthrough) enables you to send a statement directly to a
non-Oracle system, such as Kafka without first being interpreted by GG for DAA. You
do not need to explicitly add MAP for GG_HEARTBEAT
,
GG_HEARTBEAT_HISTORY
tables in replicate parameter file. You must add
ENABLE_HEARTBEAT_TABLE
in GLOBALS
file.
Restart of ggsci, manager and other child processes are recommended after any
changes in GLOBALS
file.