resetlogs noresetlogs
2015-06-17 12:46
381 查看
SQL> select * from v$version where rownum=1;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
SQL> !cat /etc/issue
Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)
Kernel \r on an \m
我们在通过重建控制文件时，到底以哪种方式，resetlogs还是noresetlogs呢？
关于控制文件的创建过程，参考之前写过的文章http://blog.itpub.net/29876893/viewspace-1575070/，在备份的创建 控制文件的脚本中，也详细介绍了重建的过程，交代了resetlogs和noresetlogs两种方式，细则给出了添加TEMP表空间的数据文件。
SQL> alter database backup controlfile to trace;
数据库已更改。
SQL> select value from v$diag_info where name='Default Trace File';
VALUE
--------------------------------------------------------------------------------
/u01/app/oracle/diag/rdbms/orcl3939/orcl3939/trace/orcl3939_ora_22671.trc
打开控制文件的创建语句的备份trace文件：
*** 2015-06-17 12:17:18.453
*** SESSION ID:(125.7) 2015-06-17 12:17:18.454
*** CLIENT ID:() 2015-06-17 12:17:18.454
*** SERVICE NAME:(SYS$USERS) 2015-06-17 12:17:18.454
*** MODULE NAME:(sqlplus@localhost.localdomain (TNS V1-V3)) 2015-06-17 12:17:18.454
*** ACTION NAME:() 2015-06-17 12:17:18.454
-- The following are current System-scope REDO Log Archival related
-- parameters and can be included in the database initialization file.
--
-- LOG_ARCHIVE_DEST=''
-- LOG_ARCHIVE_DUPLEX_DEST=''
--
-- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf
--
-- DB_UNIQUE_NAME="orcl3939"
--
-- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
-- LOG_ARCHIVE_MAX_PROCESSES=4
-- STANDBY_FILE_MANAGEMENT=MANUAL
-- STANDBY_ARCHIVE_DEST=?/dbs/arch
-- FAL_CLIENT=''
-- FAL_SERVER=''
--
-- LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
-- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
-- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
-- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
-- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
-- LOG_ARCHIVE_DEST_STATE_1=ENABLE
--
-- Below are two sets of SQL statements, each of which creates a new
-- control file and uses it to open the database. The first set opens
-- the database with the NORESETLOGS option and should be used only if
-- the current versions of all online logs are available. The second
-- set opens the database with the RESETLOGS option and should be used
-- if online logs are unavailable.
-- The appropriate set of statements can be copied from the trace into
-- a script file, edited as necessary, and executed when there is a
-- need to re-create the control file.
--
-- Set #1. NORESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- Additional logs may be required for media recovery of offline
-- Use this only if the current versions of all online logs are
-- available.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL3939" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/orcl3939/redo01.log' SIZE 50M BLOCKSIZE 512,
GROUP 2 '/u01/app/oracle/oradata/orcl3939/redo02.log' SIZE 50M BLOCKSIZE 512,
GROUP 3 '/u01/app/oracle/oradata/orcl3939/redo03.log' SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
'/u01/app/oracle/oradata/orcl3939/system01.dbf',
'/u01/app/oracle/oradata/orcl3939/sysaux01.dbf',
'/u01/app/oracle/oradata/orcl3939/undotbs01.dbf',
'/u01/app/oracle/oradata/orcl3939/user01.dbf',
'/u01/app/oracle/oradata/orcl3939/example01.dbf',
'/u01/app/oracle/oradata/orcl3939/chao.dbf',
'/u01/app/oracle/oradata/orcl3939/big_file',
'/u01/app/oracle/oradata/orcl3939/undo_w.dbf',
'/u01/app/oracle/oradata/orcl3939/a.dbf',
'/u01/app/oracle/oradata/orcl3939/v.dbf'
CHARACTER SET AL32UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- Database can now be opened normally.
ALTER DATABASE OPEN;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp01.dbf'
SIZE 2526M REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
ALTER TABLESPACE TEMP_WANG ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp_wang.dbf'
SIZE 31457280 REUSE AUTOEXTEND OFF;
-- End of tempfile additions.
--
-- Set #2. RESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- The contents of online logs will be lost and all backups will
-- be invalidated. Use this only if online logs are damaged.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL3939" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/orcl3939/redo01.log' SIZE 50M BLOCKSIZE 512,
GROUP 2 '/u01/app/oracle/oradata/orcl3939/redo02.log' SIZE 50M BLOCKSIZE 512,
GROUP 3 '/u01/app/oracle/oradata/orcl3939/redo03.log' SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
'/u01/app/oracle/oradata/orcl3939/system01.dbf',
'/u01/app/oracle/oradata/orcl3939/sysaux01.dbf',
'/u01/app/oracle/oradata/orcl3939/undotbs01.dbf',
'/u01/app/oracle/oradata/orcl3939/user01.dbf',
'/u01/app/oracle/oradata/orcl3939/example01.dbf',
'/u01/app/oracle/oradata/orcl3939/chao.dbf',
'/u01/app/oracle/oradata/orcl3939/big_file',
'/u01/app/oracle/oradata/orcl3939/undo_w.dbf',
'/u01/app/oracle/oradata/orcl3939/a.dbf',
'/u01/app/oracle/oradata/orcl3939/v.dbf'
CHARACTER SET AL32UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
-- Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp01.dbf'
SIZE 2526M REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
ALTER TABLESPACE TEMP_WANG ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp_wang.dbf'
SIZE 31457280 REUSE AUTOEXTEND OFF;
-- End of tempfile additions.
--
上面红色字体已经交代了了什么时候该用resetlogs和noresetlogs创建。如果当前数据库的REDO LOG都可用时，可以通过noresetlogs参数重建控制文件，此时oracle可以通过日志文件中读取redo信息，记录到控制文件中，由于redo中记录的信息足以重演所有提交成功的事务，所有最终能够实现完全恢复，成功打开数据库，此时的数据库就如断电一样之后的实例恢复，数据没有损失，重做日志可以继续向前写入。
但是oracle认为在resetlogs方式下，当前的日志文件已经损失，那么就意味着oracle可能丢失提交成功的数据，恢复将是一次不完全的介质恢复，resetlogs会强制清空或者重建在线日志文件。
完成恢复后需要以resetlogs方式打开数据库的几种常见情况：
1.在执行了不完全恢复之后
2.在使用了备份的控制文件进行恢复后
3.使用带有resetlogs选项创建的控制文件恢复之后
是个小知识点，希望和大家共勉！
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
SQL> !cat /etc/issue
Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)
Kernel \r on an \m
我们在通过重建控制文件时，到底以哪种方式，resetlogs还是noresetlogs呢？
关于控制文件的创建过程，参考之前写过的文章http://blog.itpub.net/29876893/viewspace-1575070/，在备份的创建 控制文件的脚本中，也详细介绍了重建的过程，交代了resetlogs和noresetlogs两种方式，细则给出了添加TEMP表空间的数据文件。
SQL> alter database backup controlfile to trace;
数据库已更改。
SQL> select value from v$diag_info where name='Default Trace File';
VALUE
--------------------------------------------------------------------------------
/u01/app/oracle/diag/rdbms/orcl3939/orcl3939/trace/orcl3939_ora_22671.trc
打开控制文件的创建语句的备份trace文件：
*** 2015-06-17 12:17:18.453
*** SESSION ID:(125.7) 2015-06-17 12:17:18.454
*** CLIENT ID:() 2015-06-17 12:17:18.454
*** SERVICE NAME:(SYS$USERS) 2015-06-17 12:17:18.454
*** MODULE NAME:(sqlplus@localhost.localdomain (TNS V1-V3)) 2015-06-17 12:17:18.454
*** ACTION NAME:() 2015-06-17 12:17:18.454
-- The following are current System-scope REDO Log Archival related
-- parameters and can be included in the database initialization file.
--
-- LOG_ARCHIVE_DEST=''
-- LOG_ARCHIVE_DUPLEX_DEST=''
--
-- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf
--
-- DB_UNIQUE_NAME="orcl3939"
--
-- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
-- LOG_ARCHIVE_MAX_PROCESSES=4
-- STANDBY_FILE_MANAGEMENT=MANUAL
-- STANDBY_ARCHIVE_DEST=?/dbs/arch
-- FAL_CLIENT=''
-- FAL_SERVER=''
--
-- LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
-- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
-- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
-- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
-- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
-- LOG_ARCHIVE_DEST_STATE_1=ENABLE
--
-- Below are two sets of SQL statements, each of which creates a new
-- control file and uses it to open the database. The first set opens
-- the database with the NORESETLOGS option and should be used only if
-- the current versions of all online logs are available. The second
-- set opens the database with the RESETLOGS option and should be used
-- if online logs are unavailable.
-- The appropriate set of statements can be copied from the trace into
-- a script file, edited as necessary, and executed when there is a
-- need to re-create the control file.
--
-- Set #1. NORESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- Additional logs may be required for media recovery of offline
-- Use this only if the current versions of all online logs are
-- available.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL3939" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/orcl3939/redo01.log' SIZE 50M BLOCKSIZE 512,
GROUP 2 '/u01/app/oracle/oradata/orcl3939/redo02.log' SIZE 50M BLOCKSIZE 512,
GROUP 3 '/u01/app/oracle/oradata/orcl3939/redo03.log' SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
'/u01/app/oracle/oradata/orcl3939/system01.dbf',
'/u01/app/oracle/oradata/orcl3939/sysaux01.dbf',
'/u01/app/oracle/oradata/orcl3939/undotbs01.dbf',
'/u01/app/oracle/oradata/orcl3939/user01.dbf',
'/u01/app/oracle/oradata/orcl3939/example01.dbf',
'/u01/app/oracle/oradata/orcl3939/chao.dbf',
'/u01/app/oracle/oradata/orcl3939/big_file',
'/u01/app/oracle/oradata/orcl3939/undo_w.dbf',
'/u01/app/oracle/oradata/orcl3939/a.dbf',
'/u01/app/oracle/oradata/orcl3939/v.dbf'
CHARACTER SET AL32UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- Database can now be opened normally.
ALTER DATABASE OPEN;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp01.dbf'
SIZE 2526M REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
ALTER TABLESPACE TEMP_WANG ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp_wang.dbf'
SIZE 31457280 REUSE AUTOEXTEND OFF;
-- End of tempfile additions.
--
-- Set #2. RESETLOGS case
--
-- The following commands will create a new control file and use it
-- to open the database.
-- Data used by Recovery Manager will be lost.
-- The contents of online logs will be lost and all backups will
-- be invalidated. Use this only if online logs are damaged.
-- After mounting the created controlfile, the following SQL
-- statement will place the database in the appropriate
-- protection mode:
-- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL3939" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/orcl3939/redo01.log' SIZE 50M BLOCKSIZE 512,
GROUP 2 '/u01/app/oracle/oradata/orcl3939/redo02.log' SIZE 50M BLOCKSIZE 512,
GROUP 3 '/u01/app/oracle/oradata/orcl3939/redo03.log' SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
'/u01/app/oracle/oradata/orcl3939/system01.dbf',
'/u01/app/oracle/oradata/orcl3939/sysaux01.dbf',
'/u01/app/oracle/oradata/orcl3939/undotbs01.dbf',
'/u01/app/oracle/oradata/orcl3939/user01.dbf',
'/u01/app/oracle/oradata/orcl3939/example01.dbf',
'/u01/app/oracle/oradata/orcl3939/chao.dbf',
'/u01/app/oracle/oradata/orcl3939/big_file',
'/u01/app/oracle/oradata/orcl3939/undo_w.dbf',
'/u01/app/oracle/oradata/orcl3939/a.dbf',
'/u01/app/oracle/oradata/orcl3939/v.dbf'
CHARACTER SET AL32UTF8
;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/ORCL3939/archivelog/2015_06_17/o1_mf_1_1_%u_.arc';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
-- Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp01.dbf'
SIZE 2526M REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
ALTER TABLESPACE TEMP_WANG ADD TEMPFILE '/u01/app/oracle/oradata/orcl3939/temp_wang.dbf'
SIZE 31457280 REUSE AUTOEXTEND OFF;
-- End of tempfile additions.
--
上面红色字体已经交代了了什么时候该用resetlogs和noresetlogs创建。如果当前数据库的REDO LOG都可用时，可以通过noresetlogs参数重建控制文件，此时oracle可以通过日志文件中读取redo信息，记录到控制文件中，由于redo中记录的信息足以重演所有提交成功的事务，所有最终能够实现完全恢复，成功打开数据库，此时的数据库就如断电一样之后的实例恢复，数据没有损失，重做日志可以继续向前写入。
但是oracle认为在resetlogs方式下，当前的日志文件已经损失，那么就意味着oracle可能丢失提交成功的数据，恢复将是一次不完全的介质恢复，resetlogs会强制清空或者重建在线日志文件。
完成恢复后需要以resetlogs方式打开数据库的几种常见情况：
1.在执行了不完全恢复之后
2.在使用了备份的控制文件进行恢复后
3.使用带有resetlogs选项创建的控制文件恢复之后
是个小知识点，希望和大家共勉！
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- Android属性动画完全解析(下)，Interpolator和ViewPropertyAnimator的用法
- 关于MyEclipse（jsp+Tomcat）与 SQLSERVER 2012 JDBC连接的问题解决方法
- ArcPad 10 的安装和部署
- mini-httpd源码分析-port.h
- Java_Web三大框架之Struts2
- 银行卡号验证js(银行卡号Luhm校验)
- Ubuntu 14.04下安装GitLab指南
- mac 查看端口号情况
- XML：特殊字符转换
- startActivity与startActivityForResult的使用小结
- PD915温度太高，通过设置BIOS降底CPU的核心电压来降温。
- PAT分支-15. 日K蜡烛图(15) C语言作答
- 子龙山人 opengl系列 - 网址
- java用org.apache.poi包操作excel
- go项目工程目录组织和GOPATH设置
- 安装WSUS服务器
- day05 Java基础
- “失落者”当当：踩不准步点 归宿在哪里
- 【ACM】顺时针打印矩阵
- 尽快报告坏消息