INFO REPLICAT
Use INFO REPLICAT
to retrieve the processing history of a
Replicat group. The output of this command includes:
-
The status of Replicat (
STARTING
,RUNNING
,STOPPED
orABENDED
).STARTING
means that the process has started but has not yet locked the checkpoint file for processing. -
(Oracle Database) The Replicat mode: non-integrated or integrated.
-
Whether or not Replicat is in coordinated mode and, if so, how many threads it currently uses.
-
Approximate Replicat lag.
-
The trail from which Replicat is reading.
-
Replicat run history, including checkpoints in the trail.
-
Information about the Replicat environment.
The basic command displays information only for online (continuous) Replicat groups. Tasks are excluded.
Replicat can be stopped or running when INFO REPLICAT
is
issued. In the case of a running process, the status of RUNNING
can mean
one of the following:
-
Active
: Running and processing (or able to process) data. This is the normal state of a process after it is started. -
Suspended
: The process is running, but suspended due to anEVENTACTIONS SUSPEND
action. In a suspended state, the process is not active, and no data can be processed, but the state of the current run is preserved and can be continued by issuing theRESUME
command. The RBA in theINFO
command reflects the last checkpointed position before the suspend action. To determine whether the state is active or suspended, issue theSEND REPLICAT
command with theSTATUS
option.
About Lag
Checkpoint Lag
is
the lag, in seconds, at the time the last checkpoint was written to the checkpoint file. For
example, consider the following:
-
Current time = 15:00:00
-
Last checkpoint = 14:59:00
-
Timestamp of the last record processed =14:58:00
Assuming these values, the lag is reported as 00:01:00 (one minute, the difference between 14:58 and 14:59).
A lag value of UNKNOWN
indicates that Replicat could be
running but has not yet processed records, or that the source system's clock is ahead of the
target system's clock (due to clock imperfections, not time zone differences).
To learn more about lag information, see LAG REPLICAT
. For complete end to end lag, use the heartbeat table
functionality. See ADD HEARTBEATTABLE
.
Admin Client Syntax
INFO REPLICAT group_name
[, SHOWCH [checkpoint_number]]
[, DETAIL]
[, TASKS | ALLPROCESSES]
-
group_name
-
The name of a Replicat group or a wildcard (*) to specify multiple groups. For example,
T*
shows information for all Replicat groups whose names begin with T. -
SHOWCH [
checkpoint_number
]
-
Displays current checkpoint details, including those recorded to the checkpoint file and those recorded to the checkpoint table, if one is being used. The database checkpoint display includes the table name, the hash key (unique identifier), and the create timestamp. Specify a value for checkpoints-number to include the specified number of previous checkpoints as well as the current one.
-
DETAIL
-
Displays detail information. For an Oracle target,
DETAIL
displays the name of the inbound server when Replicat is in integrated mode.If Replicat is in coordinated mode,
DETAIL
will display only the active threads. For example, if a Replicat namedCR
was created with a maximum of 15 threads, but only threads 7-9 are running,INFO REPLICAT
group_name
withDETAIL
will show only the coordinator thread (CR
),CR007
,CR008
, andCR009
. Checkpoints exist for the other threads, but they are not shown in the command output.To view
LOGBSN
information with theDETAIL
output, issue theDBLOGIN
command before you issueINFO REPLICAT
. If the command is issued for a specific thread ID of a coordinated Replicat, only theLOGBSN
for that thread is displayed. Otherwise, theLOGBSN
s for all threads are displayed. For more information about recovering Extract by using theLOGBSN
, see Restarting a Primary Extract after System Failure or Corruption. -
TASKS
-
Displays only Replicat tasks. Tasks that were specified by a wildcard argument are not displayed by
INFO REPLICAT
. -
ALLPROCESSES
-
Displays all Replicat groups, including tasks.
Examples
- The following example run the command from the Admin
Client.
INFO REPLICAT repe REPLICAT REPE Initialized 2019-11-20 23:54 Status STOPPED Description demo replicat Checkpoint Lag 00:00:00 (updated 00:00:14 ago) Log Read Checkpoint File ea000000000 First Record RBA 0 Settings Profile default_security Encryption Profile LocalWallet