Oracle Maximum Availability Best Practices for Oracle ... · –New MAA Best Practices show you how to accurately determine transport or apply lag using either the Data Guard Broker
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Note: Many of the following slides contain links to MAA Best Practices or My Oracle Support Notes that provide additional details. Click on the text box in the top right-hand corner of the slides to be taken directly to the paper or note that is referenced
• Oracle Enterprise Manager is the simplest way to monitor a Data Guard / Active Data Guard configuration
• But what if you don’t use OEM? – New MAA Best Practices show you how to accurately determine transport or apply
lag using either the Data Guard Broker or SQL *Plus command line – Uses v$dataguard_stats on standby – Explains how to utilize compute_time and datum_time to assess if a standby has
become disconnected – Also includes guidance for monitoring the overall health of the Data Guard
configuration
13
What’s New if using Data Guard Broker or SQL Command Line
• New MAA Best Practice paper for both 11.2 and 12.1 • Deep dive on SYNC performance tuning
– Test results that illustrate performance gains when using best practices – For example, proper online log file sizes with a large banking customer improved
performance by 30% – Frequent log switches force a checkpoint on the standby which results in increased
I/O thereby affecting performance – Single member standby redo log placed on fast storage
• New whitepaper covers redo apply performance for both 11.2 and 12.1 • How to tune with examples for various scenarios
– Tuning using top five wait events – Test results that illustrate performance gains when using best practices
• New installation and usage instructions for standby statspack – RAC considerations documented in the paper – Using in-memory ASH report when you can’t install standby statspack
• New MAA Best Practices for both 11.2 and 12.1 • Discussion on how switchovers have changed for 12.1
– Single command – New validate option prior to switchover
• How to assess your role transition timings and where the time is being spent • Optimizations to make role transitions faster with 11.2.0.2 and higher
– _defer_eor_orl_arch_for_so"=TRUE – _switchover_to_standby_option"= OPEN_ALL_IGNORE_SESSIONS – Default behavior for 11.2.0.4 and 12.1
Architecture for consolidating databases and simplifying operations Oracle Multitenant
GL OE
AP Self-contained PDB for each application • Portability (via pluggability) • Rapid provisioning (via clones) • Applications run unchanged • PDB upgrades via plug/unplug
Shared memory and background processes • More applications per server
Common operations performed at CDB level • Manage many as one (upgrade, backups, HA) • Granular control when appropriate • Simple DR
PDBs
Root
CDB
MAA Best Practices: Database Consolidation with Oracle Multitenant
( embedded url)
MAA and Multitenant • Solutions for planned / unplanned outages
• Prior to 12.1.0.2 all files associated with a new PDB had to be in place on the standby – If not, apply would stop and you would need
to copy over new files to the standby to continue
• 12.1.0.2 CREATE PLUGGABLE DATABASE statement has a new clause, STANDBYS=NONE – Allows for deferral of file instantiation on the standby – Structure of the PDB created on but files belonging to the PDB are marked as OFFLINE/RECOVER at the
standby – Affected PDB cannot be opened in this state, all other PDBs can be opened Read/Only with Active Data
Guard
What’s New - Operational Best Practices
My Oracle Support: MOS Note 1916648.1
Using Deferred PDB Recovery and STANDBYS=NONE with
• Data Guard considerations with Multitenant – Data Guard generally handles PDB plugin and
creation without need for user intervention
• Support note addresses operational best practices for cases where manual intervention is required – Cloning existing PDB to new PDB in same container database – Cloning a PDB from another CDB via Manifest File – Performing a remote PDB clone via Database link
• Database In-Memory on Exadata / SuperCluster – Tables can be mirrored in-memory across instances / nodes – Data stored in-memory doesn’t need to be re-populated if instance or node goes
down – Simply specify the DUPLICATE sub-clause of the INMEMORY attribute
• Two methods to duplicate – Duplicate = mirror column store on one other node – Duplicate all = table is replicated across all nodes in the cluster
• Transparent Role Transitions in a Data Guard Configuration – No manual intervention is required with FSFO and DG Broker
• Configuration makes use of: • Oracle Grid Infrastructure Bundled Agent (XAG) • DBFS for shared GoldenGate files (trails and checkpoint files) • Role based services • Integrated Extract (with HANDLEDLFAILOVER option for ASYNC DG) • Integrated Replicat is recommended
• New MAA Best Practices – Use all existing MAA Best practices – Create security IP lists to limit access – Oracle Net encryption – Transparent Data Encryption (TDE) – Install Oracle Restart for TAF
42
MAA Best Practices: Disaster Recovery for
Hybrid Cloud - Primary on Premises, Standby in Cloud
About LinkedIn LinkedIn operates the world’s largest professional network on the Internet with more than 380 million members in over 200 countries and territories.
Connect the world's professionals to make them more productive and successful.
Encrypting data with the Master Key and Wallet Method Encrypts GG trail file while its being transmitted over TCP/IP.
Storage Snapshot Optimization Allows Third Party Snapshot technologies to take storage snapshots without putting the database or associated data files in BACKUP mode.
Recovering tables and table partitions
Very useful in logical corruption scenarios, no need to restore entire database or tablespace.
Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.