Maximum Availability Architecture (MAA) Best Practices
-
Posted by Quest Customer Learning Team
- Last updated 5/01/23
- Share
Providing the highest levels of availability is the main goal of Oracle’s Maximum Availability Architecture (MAA), which has been available for more than a decade. What started as a set of blueprints and best practices for high availability (HA) for the Oracle Database has evolved into the de-facto standard when it comes to operating the Oracle Database in the most resilient way on-premises, on Engineered Systems or in the Cloud. Consequently, most Oracle customers look at MAA as a database administrator (DBA) task to implement. This session looks at Oracle MAA from a slightly different angle, as MAA should really be considered by the DBA as well as by developers and even by non-Oracle customers. For DBAs, this session will explain the main aspects of how to ensure HA for the Oracle Database; developers will get to see how certain features can make an application more available when MAA standards are followed. Last but not least, for those looking at alternative database solutions, this session will provide an idea as to what failures and preventative measures need to be considered to make any database more available.
Read the full whitepaper
Premium Content: access is limited to Quest Corporate and Professional members.
Membership has its perks. Get unlimited access to the latest Oracle updates, event session replays, strategic content centers and special members-only programming, plus big discounts on conference registration, with a Quest Corporate or Professional membership. Quest is where you learn.