55 Which statement about recovering from the loss of a redo log group is true? A. If the lost redo l
2015-11-26 10:53
701 查看
55
Which statement about recovering from the loss of a redo log group is true?
A. If the lost redo log group is ACTIVE, you should first attempt to clear the log file.
B. If the lost redo log group is CURRENT, you must clear the log file.
C. If the lost redo log group is ACTIVE, you must restore, perform cancel-based incomplete recovery, and
open the database using the RESETLOGS option.
D. If the lost redo log group is CURRENT, you must restore, perform cancel-based incomplete recovery,
and open the database using the RESETLOGS option.
Correct Answer: D
Section: (none)
Explanation
Explanation/Reference:
Explanation:
If the lost redo log group is CURRENT, you must restore, perform cancel-based incomplete recovery, and
open the database using the RESETLOGS option. A redo log group with a CURRENT status indicates that
LGWR is currently writing to it. To recover from this failure, you must restore the database from a whole
backup and perform cancel-based incomplete recovery. Then, you should open the database using the
RESETLOGS option.
The option that states if the lost redo log group is ACTIVE, you should first attempt to clear the log file is
incorrect. If the lost redo log group has a status of ACTIVE, it is needed for instance recovery. In that
situation, you should first attempt to perform a checkpoint. After the checkpoint, the log file is no longer
required for instance recovery.
The option that states if the lost redo log group is CURRENT, you must clear the log file is incorrect. You
would clear the log file only if the status of the lost redo log group was INACTIVE. After clearing the log file,
the log file may be reused.
The option that states if the lost redo log group is ACTIVE, you must restore, perform cancel-based
incomplete recovery, and open the database using the RESETLOGS option. These actions are only
necessary if the log file has a CURRENT status, which indicates LGWR is currently writing to it.
Which statement about recovering from the loss of a redo log group is true?
A. If the lost redo log group is ACTIVE, you should first attempt to clear the log file.
B. If the lost redo log group is CURRENT, you must clear the log file.
C. If the lost redo log group is ACTIVE, you must restore, perform cancel-based incomplete recovery, and
open the database using the RESETLOGS option.
D. If the lost redo log group is CURRENT, you must restore, perform cancel-based incomplete recovery,
and open the database using the RESETLOGS option.
Correct Answer: D
Section: (none)
Explanation
Explanation/Reference:
Explanation:
If the lost redo log group is CURRENT, you must restore, perform cancel-based incomplete recovery, and
open the database using the RESETLOGS option. A redo log group with a CURRENT status indicates that
LGWR is currently writing to it. To recover from this failure, you must restore the database from a whole
backup and perform cancel-based incomplete recovery. Then, you should open the database using the
RESETLOGS option.
The option that states if the lost redo log group is ACTIVE, you should first attempt to clear the log file is
incorrect. If the lost redo log group has a status of ACTIVE, it is needed for instance recovery. In that
situation, you should first attempt to perform a checkpoint. After the checkpoint, the log file is no longer
required for instance recovery.
The option that states if the lost redo log group is CURRENT, you must clear the log file is incorrect. You
would clear the log file only if the status of the lost redo log group was INACTIVE. After clearing the log file,
the log file may be reused.
The option that states if the lost redo log group is ACTIVE, you must restore, perform cancel-based
incomplete recovery, and open the database using the RESETLOGS option. These actions are only
necessary if the log file has a CURRENT status, which indicates LGWR is currently writing to it.
相关文章推荐
- 53 Which statement about using RMAN stored scripts is true? A. To create and execute an RMA
- NGUI OnDrag 中的Delta
- UE 查找字符串显示列表
- 遇到:Invalid layout of java.lang.String at value 这样的问题,
- UIView的layoutSubviews和drawRect方法何时调用
- android.useDeprecatedNdk=true 添入工程根目录下的新建 gradle.properties 文件
- iOS UITableView 用法二:源码示例
- UltraEdit恢复默认设置(如何彻底删除UE以前的设置)
- light oj 1012 Guilty Prince(dfs )
- UI神器-SOUI
- easyui的页面等待提示层,即mask
- js中return false,return,return true的用法及区别
- request和request.form和request.querystring的区别
- Qt Bluetooth 文档
- 【Android开发bug】Dropping event due to no window focus
- 进击的KFC:UI(五)手势识别器
- Android UI开发详解之ActionBar
- UEditor编辑器上传图片开发流程
- ueditor编辑器和at.js集成
- /Users/xxx/Library/Developer/Xcode/DerivedData/MAR-akbwbarcniqxy/build/products/debug-iphoneos