Oracle GoldenGate on Disaster Recovery

Transcription

1 Oracle on Disaster Recovery Infrastructure at your Service. Oracle on Disaster Recovery

2 Infrastructure at your Service. About Me Hervé Schweitzer Chief Technology Officer Principal Consultant Mobile Oracle on Disaster Recovery Page 2

3 Who we are dbi services Experts At Your Service > 40 specialists in IT infrastructure > Certified, experienced, passionate Based In Switzerland > 100% self-financed Swiss company > Over CHF 6 mio. turnover Leading In Infrastructure Services > More than 100 customers in CH, D, & F > Over 40 SLAs dbi FlexService contracted dbi services is hiring in Basel & Zürich (career@dbi-services.com) Oracle on Disaster Recovery Page 3

4 Agenda 1. Oracle usual implementation 2. Disaster Recovery 3. Oracle on Disaster Recovery 4. Technical Solution 5. Conclusion Oracle on Disaster Recovery Page 4

5 Oracle usual implementation Page 5 Oracle on Disaster Recovery

6 Oracle usual implementation Usually Oracle is used to replicate OLTP data to: > ODS (Operational Data Store) > Often used as an interim logical area for a Datawarehouse > Database designed to integrate data from multiple sources for additional operations on the data > Data can be scrubbed, resolved for redundancy and checked for compliance according to the business rules > Datawarehouse/BI (Business Intelligence) > Long term reporting or archiving > Analytical reports on current or historical data > Active/Active Replication > Long distance between different office > Data available on each system locally (High Availability) Oracle on Disaster Recovery Page 6

7 Oracle usual implementation Why Oracle 12c? > Can replicate data from any database rdbms (heterogeneous) > Low impact on production database > Read transaction directly from memory (Oracle 12c Integrated Capture) > Otherwise the reads are done from the redo or archive files only > Real-Time replication solution > Allows reporting with live data > Supported with other Oracle products > Oracle Active DataGuard > Oracle Grid Infrastructure resource management > Oracle ODA/Exadata > Fast recovery with low performance impact > Most of the object types are supported > Allow transformation and filtering Oracle on Disaster Recovery Page 7

8 Oracle usual implementation Primary Data Center Server 1 Server 2 ODSDB EXTRACT Trail files Local/Remote REPLICAT Page 8 Oracle on Disaster Recovery

9 Oracle usual implementation Extract EXTRACT example with one additional columns EXTRACT SCOTT USERIDALIAS gg12 DBOPTIONS ALLOWUNUSEDCOLUMN EXTTRAIL /u01/ggtrail/db1/dirdat/sa TABLE scott.*, TOKENS ( TRANSACTION_DATE ('GGHEADER', 'COMMITTIMESTAMP')); Oracle on Disaster Recovery Page 9

10 Oracle usual implementation Replicat REPLICAT example with keeping the deleted rows REPLICAT SCOTT ASSUMETARGETDEFS USERIDALIAS gg12 DISCARDFILE /u01/app/goldengate/product/12.1.2/discard/ SCOTT1_discard.txt, append, megabytes 10 ALLOWDUPTARGETMAP GETINSERTS GETUPDATES IGNOREDELETES MAP SCOTT.*, TARGET SCOTT1.*, COLMAP (USEDEFAULTS, ('TRANSACTION_DATE')); IGNOREINSERTS IGNOREUPDATES GETDELETES UPDATEDELETES MAP SCOTT.*, TARGET SCOTT1.*, COLMAP (USEDEFAULTS, ('TRANSACTION_DATE'), is_deleted = 'Y'); Oracle on Disaster Recovery Page 10

11 Disaster Recovery Page 11 Oracle on Disaster Recovery

12 Disaster Recovery Companies protect their most important applications on a Disaster Recovery site To be protected from major issues such as a earthquake or flood Disaster Recovery should be activated with only few manual interventions (even better: automatically) Oracle on Disaster Recovery Page 12

13 Disaster Recovery Primary Data Center Server 1 Observer Oracle Data Guard 12c Disaster Recovery Data Center Server 1 Standby Observer Server 2 ODSDB Oracle Data Guard 12c Server 2 ODSDB Standby Page 13 Oracle on Disaster Recovery

14 Oracle on Disaster Recovery Page 14 Oracle on Disaster Recovery

15 Oracle on Disaster Recovery Because of "globalization" and 7*24 business requirements, both OLTP and Datawarehouse databases become more and more important Beside the database, integration solutions like Oracle also need to be considered in the Disaster Recovery concept Is it possible to keep Oracle in sync between two databases on the Disaster Recovery site? Oracle on Disaster Recovery Page 15

16 Oracle on Disaster Recovery Primary Data Center DisasterRecovery Data Center 2 Server 1 Oracle Data Guard 12c Server 1 Standby Extract? Extract Server 2 ODSDB Replicat Oracle Data Guard 12c? Server 2 ODSDB Standby Replicat? Page 16 Oracle on Disaster Recovery

17 Oracle on Disaster Recovery configuration available on Disaster Recovery site > Configure on a shared file system > Very rare to have a clustered FS between the primary and DR sites available > Move the configuration to Oracle DBFS > configuration and trail files will be written to a LOB file in the database > itself will generate redo activity > One customer had a database crash with this solution > Configure Oracle on the DR site with Oracle Active DataGuard > This solution has been selected and will be presented in the next slides Oracle on Disaster Recovery Page 17

18 Technical Solution Page 18 Oracle on Disaster Recovery

19 Technical Solution Overview Primary Data Center DisasterRecovery Data Center 2 Server 1 Oracle Data Guard 12c Server 1 Standby With Active Data Guard Extract Extract Server 2 Server 2 ODSDB ODSDB Replicat Replicat Primary DB with another dbid or sid Oracle on Disaster Recovery Page 19

20 Technical Solution Setup on standby EXTRACT running with Active Data Guard on Standby Database GGSCI 1> view extract SCOTT EXTRACT SCOTT TRANLOGOPTIONS MINEFROMACTIVEDG GGSCI 2> info extract SCOTT, detail Target Extract Trails: Trail Name Seqno RBA Max MB Trail Type /u01/ggtrail/db1/dirdat/sa EXTTRAIL Extract Source /u02/oradata/db1/sredog101m1db1.dbf <- Standby redolog file /u02/oradata/db1/sredog102m1db1.dbf <- Standby redolog file Oracle on Disaster Recovery Page 20

21 Technical Solution Switchover Primary Data Center DisasterRecovery Data Center 2 With Active Data Guard Server 1 Standby Oracle Data Guard 12c Server 1 Standby With Active Data Guard Extract Extract Server 2 Server 2 ODSDB ODSDB Replicat Replicat Primary DB with another dbid or sid Oracle on Disaster Recovery Page 21

22 Technical Solution Action needed after a switchover On new Primary modify the EXTRACT GGSCI 1> edit extract SCOTT Only remove the MINEFROMACTIVEDG parameter GGSCI # grep 2> Data start Guard extract ggserr.log SCOTT extract from ggserr.log logfile the SCN# value from role switch message :02:42 ERROR OGG Oracle Capture GGSCI for Oracle, 3> alter scott.prm: extract SCOTT Encountered SCN# a Data Guard role transition. GGSCI Alter 4> Extract start to extract SCN SCOTT and restart Extract, or recreate Extract with the correct number of threads at SCN On new Standby modify the EXTRACT GGSCI 1> edit extract SCOTT add the below parameter TRANLOGOPTIONS MINEFROMACTIVEDG GGSCI 2> start extract SCOTT extract from ggserr.log logfile the SCN# value from role switch message GGSCI 3> alter extract SCOTT SCN# GGSCI 4> start extract SCOTT Oracle on Disaster Recovery Page 22

23 Technical Solution Failover Primary Data Center DisasterRecovery Data Center 2 Server 1 Oracle Data Guard 12c Server 1 Standby With Active Data Guard Extract Extract Server 2 Server 2 ODSDB ODSDB Replicat Replicat Primary DB with another dbid or sid Oracle on Disaster Recovery Page 23

24 Technical Solution Action needed after a Failover On new Primary modify the EXTRACT GGSCI 1> edit extract SCOTT remove the TRANLOGOPTIONS MINEFROMACTIVEDG parameter add the below parameter TRANLOGOPTIONS USEPREVRESETLOGSID GGSCI 2> start extract SCOTT extract from ggserr.log logfile the SCN# value from role switch message GGSCI 3> edit extract SCOTT remove the TRANLOGOPTIONS USEPREVRESETLOGSID parameter GGSCI 4> alter extract SCOTT SCN# GGSCI 5> start extract SCOTT Oracle on Disaster Recovery Page 24

25 Demo Page 25 Oracle on Disaster Recovery

26 Demo environment presentation vmreforatun DB1 Oracle Data Guard 12c vmora12c DB1 Standby With Active Data Guard Extract SCOTT.EMP Extract SCOTT.EMP vmrep12c DB2 Replicat SCOTT1.EMP Replicat SCOTT2.EMP Oracle on Disaster Recovery Page 26

27 Conclusion Page 27 Oracle on Disaster Recovery

28 Conclusion Oracle will always run on both sides; no surprise after a switchover or failover On the disaster site the replicated environment is also available for reporting No additional license costs because Active Data Guard is part of Oracle Both sides must be installed and configured for Oracle Only usable with Classical Extract Oracle on Disaster Recovery Page 28

29 Infrastructure at your Service. Any questions? Please do ask und viele Live Demos am Stand 242 Hervé Schweitzer Chief Technology Officer Principal Consultant Mobile Looking forward to seeing you at booth 242! Oracle on Disaster Recovery Page 29