Oracle Data Guard 11g Release 2 with Oracle Enterprise Manager 11g Grid Control

1. Oracle Data Guard 11g Release 2 with Oracle Enterprise Manager 11g Grid Control

2. Oracle Data Guard 11g Release 2 with Oracle Enterprise Manager 10g Grid Control • Introduction to High Availability • Data Guard Concepts • Managing Data Guard with OEM • Setup Data Guard without OEM

3. Introduction to High Availability • Availability is the degree of accessibility of an application, service or system. It is measured as the percentage of uptime in a given year. • Characteristics of a highly available systems • Reliability • Resiliency • No single point of failure (SPOF) • Recoverability • Timely error detection • Continuous operation

4. Introduction to High Availability Finalize with all stake holders prior to DR planning and implementation • Service Level Agreement (SLA): agreement between two parties specifying levels of availability, performance or operation. In the contract the level of each service should be clearly defined. • Recovery Time Objective (RTO): maximum amount of time that application, service or system can be down before the organization starts suffering unacceptable consequences. • Recovery Point Objective (RPO): maximum amount of data that can be lost without harm to the organization as a result from failure of an application, service or system.

5. Introduction to High Availability Resiliency and protection from failures Unplanned • Site failure • Cluster failure • Computer failure • System failure • Storage failure • Data corruption • Human error • Hang or slowdown • Natural disaster Planned • System and database changes • Data changes • Application changes

6. Introduction to High Availability • Present demand for high availability • Oracle HA solutions as response • Oracle RAC • Oracle Data Guard • Oracle Flashback • Oracle Streams • Oracle Goldengate • How we benefit leveraging Oracle RAC, Oracle Data Guard and Oracle Flashback implementing MAA? • How Oracle RAC, Oracle Data Guard, Oracle Flashback work in tandem in implementing MAA solutions. • Data Guard Configurations • Fast Start failover • Flashback as a way to avoid restoring the primary from backup in case of a failover, converting it to standby and synching it with the new primary. • OEM as a primary tool for managing MAA solutions.

7. Data Guard Concepts • Oracle Data Guard provides the managements, monitoring and automation software to create and maintain one or more standby databases to protect Oracle data from failures, disasters, human errors and data corruption • Data Guard configuration consist of one primary database and one or more standby databases. The databases in a Data Guard configuration may be dispersed geographically. • Managing primary and standby databases can be done using SQL command-line interfaces, Data Guard broker interfaces or using a GUI interface provided with OEM Grid Control.

8. Data Guard Concepts • Primary database: accessed by most applications, can be a single instance or RAC database • Standby database: consistent copy of the primary database. Maintained automatically using redo data. Can be a single-instance or RAC database.

9. Data Guard Concepts Physical Standby database • Provides a block-for-block physically identical copy of the primary database. • Synchronized through Redo Apply. Redo records are shipped and applied to the standby database. • Benefits: • Switchover and failover • Standby database can be open in read only mode while redo apply continues ( Active data Guard). Can not be used when with reporting tools requiring read-write access such as repository creation. • Can be used as a robust DR implementation. Logical Standby database • Provides a logically (transactionally) identical copy of the primary database. Contains the same logical information as the primary database although the physical organization and structure can be different. • Synchronized via SQL Apply. Redo records are shipped to the standby database and mined and applied as a SQL to the standby database. • Additional structures can be created to optimize the reporting workload. • Some restrictions on data types, types of tables and types of DDL and DML operations. • Benefits: • Switchover and failover • Standby database open in read-write mode. Offload production when apps need read-write access but do not modify primary data such as when repositories are created. • Can be used to perform upgrades to primary database with near zero downtime.

10. Data Guard Concepts • Switchover : the primary database transition to a standby role and the standby database transition to the primary role. It is used during the course of a planned maintenance of the primary database and ensure no data loss. Final EOR is applied on the standby database. • Failover: Occurs when the primary database is unavailable. Failover is performed only in case of a failure of the primary database and the failover results in a transition of a standby database to the primary role. Final EOR is not applied on the standby database.

11. Data Guard Concepts • Maximum availability: Archive destination is mandatory with log writer sync and affirm. Set by ‘alter database set standby to maximize availability’. Transactions do not commit until all redo data needed to recover the transactions has been written to the online redo log and to the standby redo log on at least one synchronized standby database. Ensures zero data loss except in case of certain failures when standby can not receive redo from primary. • Maximum performance: Archive destination is either mandatory/optional and transport is log writer or archive process and synchronous or asynchronous. Set by ‘alter database set standby to maximize performance’ .Is the default protection mode. Transactions commit as soon as redo data generated by those transactions has been written to the online log. Offers less data protection than maximum availability mode. • Maximum protection: Archive destination is mandatory with log writer sync and affirm. Set by ‘alter database set standby to maximize protection’. Redo data needed to recover as a transaction must be written to both the online redo log and to the standby database redo log on at least one synchronized standby database before the transaction commits. Ensures zero data loss.

12. Data Guard Concepts New features in 11gR1 • Support up to 9 standby databases. • Real time query capability of physical standby database (New Active Data Guard) feature. • User configurable conditions to initiate fast-start failover. • New Snapshot Data Guard feature. • Transport of redo data using SSL • Support of TDE with Data Guard SQL Apply. New features in 11gR2 • Support up to 30 standby databases. • Integrated support for Application failover. • Compressed table support in logical standby databases. • Automatic redo corruption detection and repair.

13. Data Guard Concepts Lets put it together…

14. Managing Data Guard with OEM • Add physical or logical standby database. • Crate a new physical or logical standby database • Add an existing standby database for management with Data Guard Broker. • Flexible options for creating standby database based on RMAN features for backup and cloning. • Direct cloning using the primary database as a source. • Using a staged backup • Created with create standby database wizard • Created as level 0 and level 1 regular backup • Monitor performance of a standby database • Redo Generation Rate • Redo Apply Rate • Transport Lag • Apply Lag • Monitor the archiving and application of redo log • Verify structure of a Data Guard • Perform Switchover or Failover • Set the type of a standby database (Active Data Guard & Snapshot Data Guard) • Manage a Data Guard configuration and set fast-start failover.

15. Managing Data Guard with OEM • Add physical or logical standby database.

16. Managing Data Guard with OEM • Add physical standby database.

17. Managing Data Guard with OEM • Add physical standby database.

18. Managing Data Guard with OEM • Add physical standby database.

19. Managing Data Guard with OEM • Add physical standby database.

20. Managing Data Guard with OEM • Add physical standby database.

21. Managing Data Guard with OEM • Add physical standby database.

22. Managing Data Guard with OEM • Add physical standby database.

23. Managing Data Guard with OEM • Add physical standby database.

24. Managing Data Guard with OEM • Add physical standby database.

25. Managing Data Guard with OEM • Add physical standby database. • After adding a standby database new options under Data Guard hyperlink appears • What we gain?

26. Managing Data Guard with OEM • Verify structure of a Data Guard

27. Managing Data Guard with OEM Verify structure of a Data Guard • What OEM do for us? • What we need to do if we do it ourselves? Initializing Connected to instance oel55.gj.com:D11P Starting alert log monitor... Updating Data Guard link on database homepage... Skipping verification of fast-start failover static services check. Data Protection Settings: Protection mode : Maximum Performance Redo Transport Mode settings: D11P: ASYNC D11P1: ASYNC Checking standby redo log files.....OK Checking Data Guard status D11P : Normal D11P1 : Normal Checking inconsistent properties Checking agent status Checking applied log on D11P1...OK Processing completed.

28. Managing Data Guard with OEM • Monitor performance of a standby database

29. Managing Data Guard with OEM • Monitor performance of a standby database

30. Managing Data Guard with OEM • Manage a Data Guard configuration

31. Managing Data Guard with OEM • Manage a Data Guard configuration

32. Managing Data Guard with OEM • Manage a Data Guard configuration

33. Managing Data Guard with OEM • Manage a Data Guard configuration

34. Managing Data Guard with OEM • Manage a Data Guard configuration

35. Managing Data Guard with OEM • Manage a Data Guard configuration – Perform a switchover

36. Managing Data Guard with OEM • Manage a Data Guard configuration – Perform a Failover

37. Managing Data Guard with OEM • Manage a Data Guard configuration – Perform a Failover

38. Managing Data Guard with OEM • Manage a Data Guard configuration – Perform a Failover & Reinstate the old physical database

39. Managing Data Guard with OEM • Manage a Data Guard configuration – Perform a Failover & Reinstate the old physical database

40. Managing Data Guard with OEM • Manage a Data Guard configuration – Configure fast-start failover • Select a standby database as a target for the fast-start failover • Configure observer ( specify observer host and observer ORACLE_HOME) • Set failover properties • Enable flashback logging • Enable observer • Fast start failover does NOT work in maximum protection role. In 10g only max availability role was supported for FSFO. Since 11g both maximum performance and maximum availability are supported.

41. Managing Data Guard with OEM • Manage a Data Guard configuration – Configure Observer

42. Managing Data Guard with OEM • Manage a Data Guard configuration – Enable flashback logging

43. Managing Data Guard with OEM • Manage a Data Guard configuration – complete fast-start failover configuration

44. Managing Data Guard with OEM • Manage a Data Guard configuration – complete fast-start failover configuration

45. Managing Data Guard with OEM • Manage a Data Guard configuration – Create logical standby database • Specify ‘Create new logical standby database’ and follow similar steps as create a physical standby database. • SQL Apply Unsupported tables • Specify Backup options • Specify Database location • Specify File locations • Specify Configuration

46. Managing Data Guard with OEM • Manage a Data Guard configuration – Create logical standby database • SQL Apply Unsupported tables

47. Managing Data Guard with OEM • Manage a Data Guard configuration – Create logical standby database

48. Managing Data Guard with OEM • Monitor a Data Guard configuration

49. Managing Data Guard with OEM • Monitor a Data Guard configuration • Redo logs archived and applied

50. Managing Data Guard with OEM • Active Data Guard • What is Active Data Guard? • How to set Active Data Guard?