All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Example 10: Reporting Commands in Goldengate

It is required to evaluate the extract status, and details and replicat status, lag details. Further also any long running transactions etc.

About Manager	info all status manager send manager childstatus
About Extract	info extract ext1, detail send extract ext1 status stats extract ext1 stats extract ext2 reportrate hr --> hr, min, sec can be used to check the processing rate send extract myload2, getlag lag extract ext2
About Replicat	info replicat rep1, detail send replicat rep1 status stats replicat rep1 stats replicat myload2 reportrate sec --> hr, min, sec can be used to check the processing rate send replicat myload2, getlag lag replicat myload2*
About Long Running Transactions	Oracle Golden Gate Replication will not propagate transactions to the destination which have NOT been committed on the source yet. However Oracle Golden gate will write the open transaction data to the dirtemp directory in the home directory. This data will then be read back later when the transaction is committed and needs to be propagated to the destination. This is especially true when bulk transactions are run, processing a large account of the uncommitted data, which then has to be written temporarily to the dirtemp location. SET LINES 300 COL start_time FOR A20 COL sid FOR 99999 COL serial# FOR 999999 COL username FOR A20 COL status FOR A10 COL schemaname FOR A10 COL process FOR A10 COL machine FOR A15 COL program FOR A30 COL module FOR A35 COL logon_time FOR A20 SELECT t.start_time,s.sid,s.serial#,s.username, s.status, s.schemaname, s.process,s.machine, s.program, s.module, used_ublk, used_urec, TO_CHAR(s.logon_time,'mon-dd-yyyy HH24:MI:SS') logon_time FROM v$transaction t, v$session s WHERE s.saddr = t.ses_addR ORDER BY start_time;