Designing a highly available database system involves taking various elements and combining them to suit your business needs and requirements. At the beginning of architecting a new high available Oracle database system it’s important to understand the need to make design and infrastructure decisions in the context of meeting Service Level Agreements (SLA). The SLA targets can be usually achieved with different technical solutions in scope of your available budget.
This article describes ground components that every DBA or Infrastructure architect should understand before building a high available database system with minim allowed downtime. It covers major elements of Service Level Agreements, different types of Oracle database downtime, etc. It’s is a first part from series of articles focusing on a topic Oracle database High Availability Strategy, Architecture and Solutions that I posted on my Website: http://www.dadbm.com.