Overview of Instance and Crash Recovery
doc的原話,記錄一下
[@more@]Overview of Instance and Crash Recovery
Crash recovery is used to recover from a failure either when a single-instance database fails or all instances of an Oracle Real Application Clusters database fail. Instance recovery refers to the case where a surviving instance recovers a failed instance in an Oracle Real Application Clusters database.
The goal of crash and instance recovery is to restore the data block changes located in the cache of the terminated instance and to close the redo thread that was left open. Instance and crash recovery use only online redo log files and current online datafiles. Oracle recovers the redo threads of the terminated instances together.
Crash and instance recovery involve two distinct operations: rolling forward the current, online datafiles by applying both committed and uncommitted transactions contained in online redo records, and then rolling back changes made in uncommitted transactions to their original state.
Crash and instance recovery have the following shared characteristics:
Redo the changes using the current online datafiles (as left on disk after the failure or
SHUTDOWN
ABORT
)Use only the online redo logs and never require the use of the archived logs
Have a recovery time governed by the number of terminated instances, amount of redo generated in each terminated redo thread since the last checkpoint, and by user-configurable factors such as the number and size of redo log files, checkpoint frequency, and the parallel recovery setting
Oracle performs this recovery automatically on two occasions:
At the first database open after the failure of a single-instance database or all instances of an Oracle Real Applications Cluster database (crash recovery).
When some but not all instances of an Oracle Real Application Clusters configuration fail (instance recovery). The recovery is performed automatically by a surviving instance in the configuration.
The important point is that in both crash and instance recovery, Oracle applies the redo automatically: no user intervention is required to supply redo logs. However, you can set parameters in the database server that can tune the duration of instance and crash recovery performance. Also, you can tune the rolling forward and rolling back phases of instance recovery separately.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/19602/viewspace-1047823/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- SQL Server進行Crash RecoverySQLServer
- MySQL crash recovery恢復慢分析MySql
- MySQL:Innodb crash recovery一些程式碼MySql
- vertx instance
- GPU InstanceGPU
- 沃趣微講堂 | PXC、MGC&MGR原理與實踐對比(八):PXC、MGC和MGR crash recoveryGC
- Flutter OverviewFlutterView
- dart class overviewDartView
- [英] TensorFlow OverviewView
- Overview of Availability in a CDBViewAI
- 3.2.1 Mounting a Database to an InstanceDatabase
- 3.1.5.6 Forcing an Instance to Start
- 7-Overview-namesView
- 8-Overview-NamespacesViewnamespace
- 10-Overview-AnnotationsView
- 2.4 Overview of Services in a CDBView
- 高通USB overviewView
- DeepLearning – Overview of Sequence modelView
- Spring Cloud: Overview 概述SpringCloudView
- Rockchip RK3588 - Rockchip Linux Recovery recovery原始碼分析Linux原始碼
- crash日誌分析
- Crash日誌解析
- 解析 crash log(一)
- Android Native Crash 收集Android
- C++ instance的使用C++
- RMAN Duplicate RAC to Single Instance
- 9-Overview-Labels and SelectorsView
- 11-Overview-Field SelectorsView
- 12-Overview-Recommended LabelsView
- Overview-(概述 What is Kubernetes)View
- 4-Overview-Kubernetes APIViewAPI
- 2.6.2 Overview of Flashback PDB in a CDBView
- 2.2.7 Overview of PDB Lockdown ProfilesView
- 2.2.6 Overview of Common Audit ConfigurationsView
- An Overview of PostgreSQL & MySQL Cross ReplicationViewMySqlROS
- 【Machine Teaching】An Overview of Machine TeachingMacView
- 3.1.5.2 Starting an Instance, and Mounting and Opening a DatabaseDatabase
- Property [title] does not exist on this collection instance
- 回顧 crash log 分析