Get Source Database (Extract) Information from Target side (Replicate)

           There might be few other ways you can find as I know below one of the way you can get the source database information. If you set it up heart beat table in target & Source side. By logging into target database  where replicates are running there is way too you can find source databases information by querying  heart beat table.  

select * from gguser.ggs_heartbeat;

select SRC_DB,EXTRACT_NAME from gguser.ggs_heartbeat;

-- To find last  Commit information

SELECT

    ggs_heartbeat.src_db AS src_db,

    ggs_heartbeat.extract_name AS extract_name,

    ggs_heartbeat.source_commit AS source_commit,

    ggs_heartbeat.target_commit AS target_commit

FROM

    gguser.ggs_heartbeat

WHERE

    ggs_heartbeat.src_db LIKE 'SUNIL%';

OGG-02755 Unable to process metadata record for SCHEMA_NAME.TABLE_NAME from trail seq# 0 at RBA 1635.

During the resetting, up of golden gate fixes My target replicates are keeping on abending with below error.

OGG-02755 Unable to process metadata record for SCHEMA_NAME.TABLE_NAME from trail seq# 0 at RBA 1635.

After long troubleshoot with help of my colleague comes to know that Encryption key differs from source to target which causing this issue. Any Metadata errors in Golden gate it might be related to Encryption so To fix this issue make sure you have right ENCKEY in BOTH Source and Target and restart the Replicates will run without any issues after that.  Update ENCKEY file with right Encryption from source. and start Extract. 

OGG-01028 Formatting error

A few days back  My extract keeps on abending with below error in one of new environment set up.  After research on Come to know that we need to add below parameters in for Extract parameter files and restart the Extract. 

-- Add below parameters to extract parameter files  

-- Make sure you adding right character set. 

SETENV (NLS_LANG="AMERICAN_AMERICA.WE8MSWIN1252")

TRANLOGOPTIONS INCLUDEREGIONID

and start extract 

OGG-06601 Oracle GoldenGate Capture for Oracle, dodspu.prm: Mismatch between the length of seqno from checkpoint (9) and recovery (devil) for extract trail

Error: -

OGG-06601  Oracle GoldenGate Capture for Oracle, dodspu.prm:  

Mismatch between the length of seqno from checkpoint (9) and recovery (devil) for extract trail 

PUMP is Abended with Above Error on Source side . Golden Gate Version in Both Sides Are 12.2.0.1.1. 

Occurring Scenarios :- 

usually when system/cluster/db  maintenance happens on Target side  when properly not stopped GG during the period of maintenance You might Get into this scenario where PUMP will keep on Abend with Above error. 

On the Target System, process works fine, but not receive new trails, because pump process are abended.

GGSCI (lab2.learnwithmedb.net) 001> info SUNILRT01

REPLICAT SUNILRT01 Last Started 2017-03-20 12:08 Status RUNNING

Checkpoint Lag 00:00:00 (updated 00:00:09 ago)

Process ID 13563

Log Read Checkpoint File ./dirdat/rt000045

2017-04-09 09:53:31.004144 RBA 308786567545 

Go to the source system.

GGSCI (host) 010> info SUNILPU 

EXTRACT SUNILPU                               Status ABENDED

Checkpoint Lag 06:10:32 (updated 00:00:01 ago) 

Process ID 13213 

Log Read Checkpoint File ./dirdat/EX000130

2017-04-09 05:59:02.000012 RBA 238799 

Copy the red line above, to reposition extract process avoiding data loss.

GGSCI (host) 4> STOP SUNILEX

GGSCI (host) 4> ALTER SUNILEX ETROLLOVER

GGSCI (host) 5> ALTER SUNILEX BEGIN 2017-04-09 04:59:02.000012 ( from above output from info SUNILPU )

GGSCI (host) 6> START SUNILEX

GGSCI (host) 010> info SUNILPU

EXTRACT SUNILPU                               Status ABENDED

Checkpoint Lag 06:10:50 (updated 00:00:02 ago) 

Process ID 13213 

Log Read Checkpoint File ./dirdat/EX000130

2017-04-09 05:59:02.000012 RBA 238799 

Go ./dirdat/EX*, to find new trail generated by etrollover.

GGSCI (host) 010> sh ls -lart ./dirdat/EX* (use second red line copied)

-rw-r----- 1 oracle oinstall 83729605 Apr 22 00:12 ./dirdat/EX000127

-rw-r----- 1 oracle oinstall 83821063 Apr 22 00:35 ./dirdat/EX000128

-rw-r----- 1 oracle oinstall 99998927 Apr 22 01:52 ./dirdat/EX000129

-rw-r----- 1 oracle oinstall   563291 Apr 22 02:30 ./dirdat/EX000130

-rw-r----- 1 oracle oinstall     3291 Apr 22 06:52 ./dirdat/EX000131 (this is the new trail, genereted by etrollover)

GGSCI (host) 014> STOP SUNILPU

GGSCI (host) 015> ALTER SUNILPU extseqno 131 extrba 0

GGSCI (host) 016> START SUNILPU

After you perform above steps , check Pump and replicat process until they are online and running continuously. 

ERROR: sending message to EXTRACT SUNIL (Timeout waiting for message).

This is one of the issues that I have faced with GoldenGate 11.

One group is constantly giving me this "Timeout waiting for message" error after few minutes of starting the group.

As you see below the Time Since Chkpt is like 18 hours!!!.

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     SUNIL      00:00:01      18:50:04

So, when you try getting the stats you get timeout warning error:

GGSCI () 9> stats SUNIL, status

Sending STATS request to EXTRACT SUNIL ...

ERROR: sending message to EXTRACT SUNIL (Timeout waiting for message).

Tried to STOP the extract and still the same error:

GGSCI () 10> stop SUNIL

Sending STOP request to EXTRACT SUNIL ...

ERROR: sending message to EXTRACT SUNIL (Timeout waiting for message).

Basically, this group is hung and only way to stop this is to kill (kill SUNIL) and restart. Well, this is not going to be accepted.

GGSCI (phlq1rfftorp001) 8> start extractSUNIL

Sending START request to MANAGER ...

EXTRACT SUNIL starting

GGSCI (phlq1rfftorp001) 9> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING

EXTRACT     RUNNING     DP1FT       00:00:00      00:00:03

EXTRACT     STARTING    SUNIL       00:00:00      02:31:49