2. Implementing Oracle9i Data Guard Michael New Senior Technical Consultant ThinkSpark Session id: 36226

3. Data Guard - Outline  Concepts  Architecture  Best practices  Implementation

4. Concepts  Differentiate High Availability approaches  Enhanced protection modes – Maximum Protection – Maximum Availability – Maximum Performance  Standby Redo Logs (SRLs)  Automatic gap resolution  Data Guard broker – Data Guard Manager (OEM) – Command-line interface (CLI)

5. Concepts Protection ModeData loss Divergence Maximum Protection Maximum Availability Maximum Performance Protection ModeData loss Divergence Maximum Protection Maximum Availability Maximum Performance None Some None Yes Minimal

6. Architecture Source: Oracle9i Data Guard Concepts and Administration

7. Architecture  Log Transport ( LGWR, ARC, FAL, RFS) – Archive log permissions, destinations, transmission, reception & transmission failure resolution – LGWR or ARC can write from primary to standby  Log Apply ( MRP or LSP ) – Managed recovery (not read-only) mode – SQL apply mode  Role Management – Primary or Standby – Switchovers, graceful or forced failovers  Data Guard Broker ( DMON )

8. Best Practices  FORCE LOGGING mode  Identical sites  Initialization parameters  Oracle network  Standby redo logs (SRLs)  Monitoring  FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

9. FORCE LOGGING Mode  New feature to Release 9.2  Prevents unlogged direct writes from propagating to standby  Overrides NOLOGGING transactions   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

10. Identical Sites  Logical structures – partition names, directories/files, privileges, accounts, etc.  Network configurations – Oracle – O/S  Hardware environments   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

11. Initialization Parameters….  Use SPFILE  Initialization settings (except 4)  No environment variables  STANDBY_ARCHIVE_DEST=LOG_ARCHIVE_DEST1  LOG_ARCHIVE_DEST_3 = … ALTERNATE …  LOG_ARCHIVE_DEST_1 = … ARCH …  Disable ARCHIVE_LAG_TARGET  Unset DB_CREATE_ONLINE_LOG_DEST_n  Tune CONTROL_FILE_RECORD_KEEP_TIME   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

12. Initialization Parameters  LOG_ARCHIVE_DEST_2 attributes – OPTIONAL – LGWR – ASYNC – NOAFFIRM – REOPEN – MAX_FAILURE – DELAY – NET_TIMEOUT   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

13. Oracle Network…  Static SID registration  Connect-time failover  Alternate standby location  Session Data Unit (SDU) setting   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

14. Oracle Network  Same network file structure  Listeners – Database clients – stop stby lsnr – Redo log & DBA traffic  tnsnames.ora files – Local node – database clients – DBAs   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

15. Standby Redo Logs  SRLs on all sites  Same # SRLs on all sites  Same SRL names on all sites  Redo logs & SRLs the same size  # SRL groups = 1 + (# redo log groups)  SRL groups < MAXLOGFILES  SRL members < MAXLOGMEMBERS   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

16. Monitoring  OEM Data Guard Diag Pack events  Alert log ORA- errors  Alert log non ORA- errors  V$ views - scripts (White Paper, Appendix 3)   FORCE LOGGING  Identical sites  init.ora  Oracle Net  SRLs  Monitoring

17. Implementation….  FORCE LOGGING  Identical sites – O/S clocks – /etc/hosts – Environment variables & DBA scripts  Initialization parameters (SPFILE)  Oracle network configuration files  ARCHIVELOG mode & automatic archiving  Backup primary database  Create standby control file

18. Implementation  Copy backup to standby site  Recover standby database – Mount standby database – Create SRLs – Start new listeners – Recover standby – Place standby in managed recovery mode – Enable LOG_ARCHIVE_DEST_STATE_2 on primary – Set protection mode on primary – Verify standby works  Enable Data Guard broker

19. Next Steps….  Michael New, Michael.New@ThinkSpark.com, 800-846-4082, ext. 104Michael.New@ThinkSpark.com  Recommended sessions – Oracle Data Guard: Maximum Data Protection at Minimum Cost – Data Guard SQL Apply: Back to the Future  Recommended demos and/or hands-on labs – Using Data Guard Manager to Manage a Standby Database

20. Next Steps….  See Your Business in Our Software – Visit the DEMOgrounds for a customized architectural review, see a customized demo with Solutions Factory, or receive a personalized proposal. Visit the DEMOgrounds for more information.  Relevant web sites to visit for more information – Oracle High Availability Guidelines & Recommendations: M. Burke, 2003, ThinkSpark – info@thinkspark.cominfo@thinkspark.com – Data Guard Overview: http://otn.oracle.com/deploy/availability/htdocs/odg_overvie w.html

21. Next Steps  Relevant web sites to visit for more information – Data Guard Technical White Paper on OTN: http://otn.oracle.com/deploy/availability/pdf/DG92_TWP.pdf http://otn.oracle.com/deploy/availability/pdf/DG92_TWP.pdf – Data Guard Technology Overview Presentation on OTN: http://otn.oracle.com/deploy/availability/pdf/DataGuardTech nologyOverview.pdf http://otn.oracle.com/deploy/availability/pdf/DataGuardTech nologyOverview.pdf – Data Guard Primary Site & Network Configuration Best Practices: http://otn.oracle.com/deploy/availability/pdf/MAA_DG_NetB estPrac.pdf http://otn.oracle.com/deploy/availability/pdf/MAA_DG_NetB estPrac.pdf

22. Reminder – please complete the OracleWorld online session survey Thank you.

23. A Q & Q U E S T I O N S A N S W E R S

25. Implementing Oracle9i Data Guard Michael New Senior Technical Consultant ThinkSpark Session id: 36226

26. Implement B&R – DG is HA (not B&R) Solution  B&R addresses database integrity & recovery  DG is HA solution to reduce MTTR, premised on reliable B&R solution  Without B&R, data loss possible with DG because of – Primary / secondary loss of network communication – Standby maintenance downtime – Hardware failure due to multiple devices – Hardware failure during role reversal – logical corruption (if propagated to the standby)

27. ThinkSpark For more than 15 years, ThinkSpark has been a world-class technology partner to those businesses that have invested in Oracle technologies and solutions. ThinkSpark has delivered unmatched Oracle database expertise, Oracle systems integration skills, Oracle education services and Oracle license management insights to thousands of businesses across the country and around the globe. Headquartered in Dallas, ThinkSpark's more than 100 professionals serve clients across all industries through facilities in Austin, Dallas, Houston, Las Vegas, Oklahoma City and San Antonio. For more information about ThinkSpark, call (888) 262-6043 from the U.S., Canada and Mexico or visit ThinkSpark on the World Wide Web at http://www.thinkspark.com/.http://www.thinkspark.com/