INFO EXTRACT

Use INFO EXTRACT to view the following information.

  • The status of Extract (STARTING, RUNNING, STOPPED or ABENDED). STARTING means that the process has started but has not yet locked the checkpoint file for processing.

  • Approximate Extract lag.

  • Checkpoint information.

  • Process run history.

  • The trail(s) to which Extract is writing.

  • Status of upgrade to, or downgrade from, integrated capture

Extract can be running or stopped when INFO EXTRACT 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 an EVENTACTIONS 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 the SEND EXTRACT command with the RESUME option in GGSCI. The RBA in the INFO command reflects the last checkpointed position before the suspend action. To determine whether the state is active or suspended, issue the SEND EXTRACT command with the STATUS option.

The basic command displays information only for online (continuous) Extract processes. Tasks are excluded.

About Extract Lag

The Checkpoint Lag field of the INFO EXTRACT output reflects the lag, in seconds, at the time that the last checkpoint was written to the trail. For example, if the following is true...

  • Current time = 15:00:00

  • Last checkpoint = 14:59:00

  • Timestamp of the last record processed = 14:58:00

...then 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 the process 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).

For more precise lag information, use LAG EXTRACT (see "LAG EXTRACT").

Syntax

INFO EXTRACT group_name
[, SHOWCH [n]]
[, DETAIL]
[, TASKS | ALLPROCESSES]
[, UPGRADE | DOWNGRADE]
group_name

The name of an Extract group or a wildcard (*) to specify multiple groups. For example, T* shows information for all Extract groups whose names start with T.

SHOWCH [n]

The basic command shows information about the current Extract checkpoints. Extract checkpoint positions are composed of read checkpoints in the data source and write checkpoints in the trail. The trail type (RMTTRAIL or EXTTRAIL) is also noted.

Optionally, specify a value for n to include the specified number of previous checkpoints as well as the current one.

Note:

You might see irregular indents and spacing in the output. This is normal and does not affect the accuracy of the information.

See Administering Oracle GoldenGate for Windows and UNIX for more information about checkpoints, including descriptions of the types of checkpoints made by each process and the internal metadata entries that are included in the display.

DETAIL

Displays the following:

  • Extract run history, including start and stop points in the data source, expressed as a time.

  • Trails to which Extract is writing.

See Example 1-0 for sample output of DETAIL.

TASKS

Displays only Extract tasks. Tasks that were specified by a wildcard argument are not displayed by INFO EXTRACT.

ALLPROCESSES

Displays all Extract groups, including tasks.

UPGRADE | DOWNGRADE

Valid for an Oracle database only.

  • UPGRADE displays whether the Extract can be upgraded from classic capture mode to integrated capture mode.

  • DOWNGRADE displays whether the Extract can be downgraded from integrated capture mode to classic capture mode.

If Extract cannot be upgraded or downgraded, the reason why is displayed.

A wildcarded Extract name is not allowed with this option.

Before using this command, issue the DBLOGIN command.

Examples

Example 1   
INFO EXTRACT fin*, SHOWCH
Example 2   
INFO EXTRACT *, TASKS
Example 3   (Oracle only)
INFO EXTRACT finance UPGRADE
Example 4   

The following example shows basic INFO EXTRACT output.

EXTRACT                   EXTCUST Last Started 2011-01-05 16:09 Status RUNNING
Checkpoint Lag            00:01:30 (updated 97:16:45 ago)
Log Read Checkpoint File  /rdbms/data/oradata/redo03a.log
                          2011-01-05 16:05:17  Seqno 2952, RBA 7598080
Example 5   

The following is an example of the output of INFO EXTRACT with DETAIL.

EXTRACT    ORAEXT    Last Started 2011-01-15 16:16   Status STOPPED
Checkpoint Lag       00:00:00 (updated 114:24:48 ago)
Log Read Checkpoint  File C:\ORACLE\ORADATA\ORA920\REDO03.LOG
                     2011-01-15 16:17:53 Seqno 46, RBA 3757568

Target Extract Trails:

Trail Name                            Seqno    RBA   Max MB   Trail Type

  c:\goldengate802\dirdat\xx              0  57465       10     RMTTRAIL
  c:\goldengate802\dirdat\jm              0  19155       10     RMTTRAIL

Extract Source                        Begin             End

C:\ORACLE\ORADATA\ORA920\REDO03.LOG    2011-01-15 16:07 2011-01-15 16:17
C:\ORACLE\ORADATA\ORA920\REDO03.LOG    2011-01-15 15:55  2011-01-15 16:07
C:\ORACLE\ORADATA\ORA920\REDO03.LOG    2011-01-15 15:42  2011-01-15 15:55
C:\ORACLE\ORADATA\ORA920\REDO03.LOG   2011-01-15 15:42  2011-01-15 15:42
  Not Available                         * Initialized *   2011-01-15 15:42

Current directory    C:\GoldenGate802

Report file          C:\GoldenGate802\dirrpt\ORAEXT.rpt
Parameter file       C:\GoldenGate802\dirprm\ORAEXT.prm
Checkpoint file      C:\GoldenGate802\dirchk\ORAEXT.cpe
Process file         C:\GoldenGate802\dirpcs\ORAEXT.pce
Error log            C:\GoldenGate802\ggserr.log