Network Communication Issues in GoldenGate

Please check ggerror.log file:-- Network Communication Issues in GoldenGate

ERROR   OGG-01033  Oracle GoldenGate Capture for Oracle, extpump.prm:  There is a problem in network communication, a remote file problem, encryption keys for target and source do not match (if using ENCRYPT) or an unknown error. (Remote file used is /opt/app/t1mm1d56/ggs/trails/rt000377, reply received is Could not create /opt/app/t1mm1d56/ggs/trails/rt000377).

WARNING OGG-01525  Oracle GoldenGate Capture for Oracle, extpump.prm:  Failed to open trace output file, 'gglog-EXTPUMP.dmp', error 13 (Permission denied).

To FIX:

Restart the manager processm, answer "y" when prompted.

Step 1:

GGSCI (hltd212) 64> stop mgr
Manager process is required by other GGS processes.
Are you sure you want to stop it (y/n)?

Step 2: please try to restart mgr and others process after stopped like below

GGSCI (hltd212) 65>start mgr

UNIQUE Constraint Violation issue in Oracle Golden Gate

Please check ggerror.log file :-- UNIQUE Constraint Violation issue in Oracle Golden Gate

WARNING OGG-00869  Oracle GoldenGate Delivery for Oracle, st3_rep1.prm:  OCI Error ORA-00001: unique constraint (NIM.SYS_C0074582) violated (status = 1), SQL <INSERT INTO "NIM"."MCWARNING" ("ACTIVITYDEFINITIONID","WARNINGMESSAGE") VALUES (:a0,:a1)>.

WARNING OGG-01004  Oracle GoldenGate Delivery for Oracle, st3_rep1.prm: 
Aborted grouped transaction on 'NIM.MCWARNING', Database error 1 (ORA-00001: unique constraint (NIM.SYS_C0074582) violated).

To FIX:

Step 1:

edit param st3_rep1

Step2 :

Uncomment the HANDLECOLLISIONS parameter then restart.  To uncomment take out the two dashes in front of the parameter.

Once the lag is dimished, again comment this out and restart the thread i.e. restart the process.

LONG RUNNING TRANSACTION issue in Oracle GoldenGate

Please check ggerror.log file :--- LONG RUNNING TRANSACTION issue in Oracle GoldenGate

GGS WARNING     190  Oracle GoldenGate Capture for Oracle, extgrp1.prm:  Long Running Transaction: XID 313.5.780269, Items 3, Extract EXTGRP1, Redo Thread 1, SCN 2912.2575963070 (12509520729022), Redo Seq #147217, Redo RBA 150735888.

To FIX:

*Monitor and see if the LRT will clear on its own.  If a lag starts to happen and it reaches 30 minutes then perform the following step to skip the transaction.*

send extgrp1 skiptrans 313.5.780269

extgrp1:- GG extract process name
skiptrans:- keyword
313.5.780269:-- LRT

BAD COLUMN INDEX issue in Oracle GoldenGate

Please check gg log file to fix: -- BAD COLUMN INDEX issue in Oracle GoldenGate

ERROR   OGG-01161  Oracle GoldenGate Delivery for Oracle, st5_rep1.prm:  Bad column index (10) specified for table NIM.LSRVINFO, max columns = 10.

To FIX:

This usually means the the columns on the target and source do not match.  Compare the tables on target and source to see if all columns match.  Update target to match source by adding a column or removing a column or altering the size of a column, etc...  In this case we needed to add a column.

gglst1d2:/appl/gg/ggs/ $ sqlplus nim_st5/nim_st5

SQL*Plus: Release 11.1.0.7.0 - Production on Fri Oct 7 08:11:05 2011
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production

SQL> Alter table nim_st5.lsrvinfo add ORIGINALFOCDUEDATE timestamp(6);
Table altered.

ARCHIVE LOG MISSING in Oracle GoldenGate

Please check ggerror.log file : ARCHIVE LOG MISSING in Oracle GoldenGate

ERROR   OGG-00446  Oracle GoldenGate Capture for Oracle, extgrp1.prm:  Opening ASM file +IPAG_RECOVERY/1_14170_778456717.dbf in DBLOGREADER mode: (308) ORA-00308: cannot open archived log '+IPAG_RECOVERY/1_14170_778456717.dbf'

ORA-17503: ksfdopn:2 Failed to open file +IPAG_RECOVERY/1_14170_778456717.dbf ORA-15173: entry '1_14170_778456717.dbf' does not exist in directory '/'Not able to establish initial position for sequence 14170, rba 94987280.

To FIX:

Restore archivelogs using RMAN on the source database, then restart GG.  The first archive log sequence that is missing can be found in the error message, "'Not able to establish initial position for sequence 14170". 

To find the last archive log missing run the SQL the first archive log listed minus one will be the last archive log missing, in this case it would be 14271.  So in order to fix the above error a restore from 14170 to 14270 would need to be performed.

SQL> select THREAD#, SEQUENCE#, COMPLETION_TIME , DELETED from gv$archived_log where DEST_ID = 1 and DELETED = 'NO' order by THREAD#, SEQUENCE#;

   THREAD#  SEQUENCE# COMPLETIO DEL
---------- --------- -------- --
         1      14271 31-MAR-13 NO
         1      14272 31-MAR-13 NO
         1      14273 31-MAR-13 NO
         1      14274 31-MAR-13 NO

${ORACLE_HOME}/bin/rman target / catalogrman102/cat@rmandb.snt.bst.bls.com

RMAN>  run { restore archivelog from logseq=14170 until logseq=14270; }

Foreign Key Issues in Oracle GoldenGate

Please check ggerror.log file :

Database error 2292 (OCI Error ORA-02292: integrity constraint (CRA.PT_PT_FK) violated - child record found (status = 2292), SQL <DELETE FROM "CRA"."PROJTASK"  WHERE "PROJTASKID" = :b0>).

Solution:

Disable the foreign key on the mirror database and restart process.

DATA LOSS ISSUE on source side in GoldenGate

Please check gg log file:--

ERROR   OGG-01973  Oracle GoldenGate Capture for Oracle, elci3t1d.prm:  The redo record indicates data loss on object 80,238.

To FIX:

Query the database with the folloiwng query then exclude the table from the extract.  In this case it was the workorder table.

select owner, object_name from dba_objects where object_id=80238 or data_object_id=80238;

GGSCI (nmsis) 18> edit param ELCI3T1D

TABLEEXCLUDE  MER.WORKORDER;

SAVE AND EXIT