Oracle GoldenGate and Oracle Data Guard
Oracle GoldenGate and Oracle Data Guard Oracle GoldenGate and Oracle Data Guard
Challenge 3: Fuzziness in Redo Data • Zero Data Loss Guarantee – SYNC Transport – Redo is written in parallel to standby and online redo logs – Commits are not acknowledged to the user until an ACK is received from Standby – Redo state is fuzzy until ACK is received • Commit in both ORL and SRL (Good case) • Commit in ORL but not in SRL • Commit in SRL but not in ORL • Commit in neither ORL nor SRL (Good Case) – Need a way to avoid redo fuzziness during Capture 18 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
Challenge 4: Standbys may Not be Co-located • GoldenGate Files May Need to be Replicated – Checkpoint file – Bounded Recovery file – Trail file – Parameter file – Use shared storage or DBFS 19 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
- Page 1 and 2: Oracle Golden Gate and Oracle Data
- Page 3 and 4: 3 Program Agenda Overview of Oracl
- Page 5 and 6: Oracle GoldenGate Differentiators P
- Page 7 and 8: Program Agenda Overview of Oracle
- Page 9 and 10: Oracle Data Guard Concepts • Swit
- Page 11 and 12: Oracle Data Guard Fast Start Failov
- Page 13 and 14: Data Guard FSFO • Zero Data Loss
- Page 15 and 16: Technical Challenges in Capturing D
- Page 17: Challenge 2: Resetlogs Change on Fa
- Page 21 and 22: Integrated Capture: What is it? 21
- Page 23 and 24: Oracle GoldenGate: Integrated Captu
- Page 25 and 26: Integrated Capture: Engineered for
- Page 27 and 28: Integrated Capture: Deploying On-So
- Page 29 and 30: Redo Transport Integrated Capture (
- Page 31 and 32: Integrated Capture (DBFS): On-Sourc
- Page 33 and 34: Integrated Capture (DBFS): On-Sourc
- Page 35 and 36: On-Database Deployment for DG: Conf
- Page 37 and 38: On-Database Deployment: Param Files
- Page 39 and 40: Role Change Trigger create or repla
- Page 41 and 42: Integrated Capture: Deploying Downs
- Page 43 and 44: Redo Transport Integrated Capture:
- Page 45 and 46: Integrated Capture: Downstream Depl
- Page 47 and 48: Downstream Deployment for Data Guar
- Page 49 and 50: Downstream Deployment for Data Guar
- Page 51 and 52: Downstream Deployment for Data Guar
- Page 53 and 54: Program Agenda Overview of Oracle
- Page 55 and 56: Join the Data Integration Community
- Page 57: 60 Copyright © 2012, Oracle and/or
Challenge 3: Fuzziness in Redo <strong>Data</strong><br />
• Zero <strong>Data</strong> Loss Guarantee<br />
– SYNC Transport<br />
– Redo is written in parallel to st<strong>and</strong>by <strong>and</strong> online redo logs<br />
– Commits are not acknowledged to the user until an ACK is received from<br />
St<strong>and</strong>by<br />
– Redo state is fuzzy until ACK is received<br />
• Commit in both ORL <strong>and</strong> SRL (Good case)<br />
• Commit in ORL but not in SRL<br />
• Commit in SRL but not in ORL<br />
• Commit in neither ORL nor SRL (Good Case)<br />
– Need a way to avoid redo fuzziness during Capture<br />
18 Copyright © 2011, <strong>Oracle</strong> <strong>and</strong>/or its affiliates. All rights reserved.
Change language