Behind the scene – Integrated Capture

GoldenGate Integrated Extract bring some advantages to business and to the administrator.

It also bring new things to Database and DBA ūüôā

Have you debug GoldenGate operations on Database?

I have it, so I’ll show the tricks.

Connection thru Oracle databases:

When you register your GoldenGate extract, it is registered in the database DBA views. It also create an point to start the capture – check SCN returned from GG registration.

GGSCI (grepora as ggate@grepdb) 10> register extract E_REP database
INFO    OGG-02003  Extract E_REP successfully registered with database at SCN 298357743941.

In the database side, when you register the extract, it fire some alerts on database alert_*.log

Like this:

GoldenGate CAPTURE CP04 for OGG$CAP_E_REP started with pid=38, OS id=27066592
CAPTURE OGG$CAP_E_REP: Start SCN: 7298357743941 (0x48055145.000006a3)
CAPTURE OGG$CAP_E_REP: First SCN: 7298357743941 (0x48055145.000006a3)
CAPTURE OGG$CAP_E_REP: Required Checkpoint SCN: 0 (0x0000.00000000)
CAPTURE OGG$CAP_E_REP: Captured SCN: 0 (0x0000.00000000)
CAPTURE OGG$CAP_E_REP: Applied SCN: 0 (0x0000.00000000)
CAPTURE OGG$CAP_E_REP: Capture Type: DOWNSTREAM
CAPTURE OGG$CAP_E_REP: Logminer Id: 458
CAPTURE OGG$CAP_E_REP: Source Database: COREDB
First applied SCN of the GoldenGate path from capture (OGG$CAP_E_REP) to propagation () to apply (OGG$E_REP) is set to SCN: 7298357743941 (0x48055145.000006a3)
GoldenGate CAPTURE CP04 for OGG$CAP_E_REP with pid=38, OS id=27066592 is in combined capture and apply mode.
Capture OGG$CAP_E_REP is handling 1 applies.
  -- capture is running in apply-state checkpoint mode.
GoldenGate downstream capture OGG$CAP_E_REP uses downstream_real_time_mine: FALSE
Starting persistent Logminer Session with sid = 458 for GoldenGate Capture OGG$CAP_E_REP
LOGMINER: Parameters summary for session# = 458
LOGMINER: Number of processes = 0, Transaction Chunk Size = 1
LOGMINER: Memory Size = 60M, Checkpoint interval = 1000M
LOGMINER: SpillScn 0, ResetLogScn 7116144954722
LOGMINER: summary for session# = 458
LOGMINER: StartScn: 7298358258174 (0x06a3.480d29fe)

In Oracle database, what GoldenGate will mean?
MEANS few things.

Will find registered process on some dba view.

SQLPLUS> select CAPTURE_NAME,CAPTURE_USER,FIRST_SCN from dba_capture;

CAPTURE_NAME       CAPTURE_USER   FIRST_SCN
--------------------------------------------
OGG$CAP_E_REP    GGATE         7298357743941


SQLPLUS> select id,name from dba_logmnr_session;
        ID       NAME
---------------------------------
       456  OGG$CAP_E_REP

SQLPLUS> select SERVER_NAME,STATUS,USER_COMMENT,START_SCN from DBA_XSTREAM_OUTBOUND;
                                                                    
SERVER_NAME    STATUS   USER_COMMENT                  START_SCN
----------------------- ---------------------------------------
OGG$E_REP   DETACHED E_REP GoldenGate Extract  7298357743

SQLPLUS> select SERVER_NAME,CREATE_DATE,USER_COMMENT from SYS.XSTREAM$_SERVER;
 
SERVER_NAME   CREATE_DATE                USER_COMMENT
------------------------------------------------------------------------------
OGG$E_REP  04/08/17 20:00:30,428026   E_REP GoldenGate Extract

Transactions made before it will be lose.

In first GoldenGate Integrate extract startup will inform in ggserr.log

OGG-02065  Oracle GoldenGate Capture for Oracle, e_rep.prm:  Integrated capture dictionary initialization in progress. State of logmining server: MINING (PROCESSED SCN = 7298358147459).
OGG-02065  Oracle GoldenGate Capture for Oracle, e_rep.prm:  Integrated capture dictionary initialization in progress. State of logmining server: LOADING (step 38 of 68).
OGG-02065  Oracle GoldenGate Capture for Oracle, e_rep.prm:  Integrated capture dictionary initialization in progress. State of logmining server: LOADING (step 68 of 68).
OGG-02248  Oracle GoldenGate Capture for Oracle, e_rep.prm: Logmining server DDL filtering enabled.

This process should increase Oracle Database CPU and Memory utilization.

When GoldenGate Integrate Extract working, will append LOGMINER infos on alert_*.log

LOGMINER: Begin mining logfile for session 456 thread 1 sequence 110429, +DGFRA/onlinelog/group_23.308.907862971
LOGMINER: End   mining logfile for session 456 thread 1 sequence 95230, +DGFRA/onlinelog/group_34.302.907863101
LOGMINER: Begin mining logfile for session 456 thread 1 sequence 95231, +DGFRA/onlinelog/group_33.292.909679041

 

Pay attention, in alert_*log LOGMINER does not register which process is capturing (eg. E_REP) but it prints de ID for session, that can be related to dba_logmnr_session.

In next post I will cover more about this debug on v$session / v$trancation view.

Our blog crew have reviewed many Integrated Extract errors. If you have some issue, review below:

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s