Sep 24, 2014
Oracle disaster recovery software helps companies to dramatically reduce the amount of downtime they experience during an unscheduled outage.
Recent statistics from the American Sustainable Business Council and Small Business Majority revealed IT failures cost organizations a median average of US$3,000 a day. Furthermore, 25 per cent of SMEs do not re-open after closing due to a major system collapse.
So what problems could affect a database? According to Oracle, here are five potential issues that may result in significant downtime if not adequately prepared for:
1. Site failure
When a production database becomes completely unavailable at a primary location, it is considered a site failure. All tiers of an application will be out of commission, with the most common causes being natural disasters and power outages.
The quickest way to commence operations is to failover to a standby database at a secondary site.
2. Data corruption
Data corruption can cause important parts of a database to fail. This may occur when operating system or node-related issues corrupt Oracle blocks or if a datafile is accidentally removed.
3. Human error
According to the Uptime Institute, 70 per cent of all data center outages can be traced back to human error. Oracle claims this is typically due to operator failings or application code bugs.
As such, sections of the database become unavailable and problems can arise with transactional or logical data.
4. Computer shutdown
When just a single instance of the database fails (rather than the whole cluster) it is usually a problem in one of three main areas - the software, hardware or operating system.
5. Clusterwide failure
There are a number of potential causes for a clusterwide failure, including severe database corruption, disk storage problems and issues with the last node on an RAC cluster.
Without a standby database, recovery from this type of incident could take hours or even days.