重建控制文件,并且不干净的关闭数据库测试

重建控制文件,并且不干净的关闭数据库测试:

数据库SHUTDOWN ABORT,删除CONTROLFILE

SQL> startup nomount;
ORACLE instance started.

Total System Global Area  419430400 bytes
Fixed Size                  2021248 bytes
Variable Size             171968640 bytes
Database Buffers          243269632 bytes
Redo Buffers                2170880 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "XUEXI" RESETLOGS  ARCHIVELOG
  2      MAXLOGFILES 16
  3      MAXLOGMEMBERS 3
  4      MAXDATAFILES 100
  5      MAXINSTANCES 8
  6      MAXLOGHISTORY 292
  7  LOGFILE
  8    GROUP 1 '/oradata/xuexi/redo01.log'  SIZE 50M,
  9    GROUP 2 '/oradata/xuexi/redo02.log'  SIZE 50M,
 10    GROUP 3 '/oradata/xuexi/redo03.log'  SIZE 50M,
 11    GROUP 4 '/oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log'  SIZE 50M,
 12    GROUP 5 (
 13      '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log',
 14      '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log'
 15    ) SIZE 50M,
 16    GROUP 7 (
 17      '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log',
 18      '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log',
 19      '/oradata/logfile07.log'
 20    ) SIZE 100M
 21  -- STANDBY LOGFILE
 22  DATAFILE
 23    '/oradata/xuexi/system01.dbf',
 24    '/oradata/xuexi/undotbs01.dbf',
 25    '/oradata/xuexi/sysaux01.dbf',
 26    '/oradata/xuexi/users01.dbf',
 27    '/oradata/xuexi/XUEXI/datafile/o1_mf_tomf_8yqwrdoj_.dbf',
 28    '/oradata/xuexi/omf2.dbf',
 29    '/oradata/xuexi/XUEXI/datafile/testimp01.dbf',
 30    '/oradata/xuexi/XUEXI/datafile/testimp011.dbf',
 31    '/oradata/xuexi/XUEXI/datafile/testo1.dbf',
 32    '/oradata/xuexi/XUEXI/datafile/testo2.dbf'
 33  CHARACTER SET AL32UTF8
 34  ;

Control file created.

SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-01100: database already mounted

SQL> recover database ;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

 

SQL> RECOVER DATABASE USING BACKUP CONTROLFILE;
ORA-00279: change 1917689 generated at 10/04/2013 21:15:57 needed for thread 1
ORA-00289: suggestion : /archive/1_102_822387818.dbf
ORA-00280: change 1917689 for thread 1 is in sequence #102

Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log '/archive/1_102_822387818.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

ORA-00308: cannot open archived log '/archive/1_102_822387818.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory

显然这里缺少102这个归档,因为他是当前日志文件,所以我们需要把日志复制到归档目录下,但是那个日志是102呢,这样就可以确定
[oracle@localhost bdump]$ tail -n 4000 alert_xuexi.log |grep Current
  Current log# 4 seq# 100 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log
  Current log# 4 seq# 100 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log
  Current log# 5 seq# 101 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log
  Current log# 5 seq# 101 mem# 1: /oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log
  Current log# 7 seq# 102 mem# 0: /oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log
  Current log# 7 seq# 102 mem# 1: /oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log
  Current log# 7 seq# 102 mem# 2: /oradata/logfile07.log
  可以确认/oradata/logfile07.log就是需要的归档
cp /oradata/logfile07.log /archive/1_102_822387818.dbf

SQL> recover database using backup controlfile
ORA-00279: change 1917689 generated at 10/04/2013 21:15:57 needed for thread 1
ORA-00289: suggestion : /archive/1_102_822387818.dbf
ORA-00280: change 1917689 for thread 1 is in sequence #102

Specify log: {=suggested | filename | AUTO | CANCEL}
AUTO
完成后即可
当然也快手动输入你确认的当前归档如下:
SQL> recover database using backup controlfile
ORA-00279: change 1917689 generated at 10/04/2013 21:15:57 needed for thread 1
ORA-00289: suggestion : /archive/1_102_822387818.dbf
ORA-00280: change 1917689 for thread 1 is in sequence #102

Specify log: {=suggested | filename | AUTO | CANCEL}
/oradata/logfile07.log
Log applied.
Media recovery complete.
SQL> alter database open resetlogs;

SQL> alter database open resetlogs;

Database altered.
Log applied.
Media recovery complete.

alter database backup controlfile to trace 全文
/opt/oracle/admin/xuexi/udump/xuexi_ora_5686.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /opt/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      localhost.localdomain
Release:        2.6.18-164.el5
Version:        #1 SMP Tue Aug 18 15:51:48 EDT 2009
Machine:        x86_64
Instance name: xuexi
Redo thread mounted by this instance: 1
Oracle process number: 18
Unix process pid: 5686, image: oracle@localhost.localdomain (TNS V1-V3)

*** SERVICE NAME:(SYS$USERS) 2013-10-04 21:38:20.304
*** SESSION ID:(146.91) 2013-10-04 21:38:20.304
*** 2013-10-04 21:38:20.304
-- 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="xuexi"
--
-- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
-- LOG_ARCHIVE_MAX_PROCESSES=2
-- STANDBY_FILE_MANAGEMENT=MANUAL
-- STANDBY_ARCHIVE_DEST=?/dbs/arch
-- FAL_CLIENT=''
-- FAL_SERVER=''
--
-- LOG_ARCHIVE_DEST_1='LOCATION=/archive'
-- LOG_ARCHIVE_DEST_1='OPTIONAL REOPEN=300 NODELAY'
-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC'
-- LOG_ARCHIVE_DEST_1='REGISTER 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 "XUEXI" NORESETLOGS  ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/oradata/xuexi/redo01.log'  SIZE 50M,
  GROUP 2 '/oradata/xuexi/redo02.log'  SIZE 50M,
  GROUP 3 '/oradata/xuexi/redo03.log'  SIZE 50M,
  GROUP 4 '/oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log'  SIZE 50M,
  GROUP 5 (
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log'
  ) SIZE 50M,
  GROUP 7 (
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log',
    '/oradata/logfile07.log'
  ) SIZE 100M
-- STANDBY LOGFILE
DATAFILE
  '/oradata/xuexi/system01.dbf',
  '/oradata/xuexi/undotbs01.dbf',
  '/oradata/xuexi/sysaux01.dbf',
  '/oradata/xuexi/users01.dbf',
  '/oradata/xuexi/XUEXI/datafile/o1_mf_tomf_8yqwrdoj_.dbf',
  '/oradata/xuexi/omf2.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp01.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp011.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo1.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo2.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 '/archive/1_1_822350387.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350760.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822330757.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350003.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822349246.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350252.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822374325.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822387818.dbf';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- All logs need archiving and a log switch is needed.
ALTER SYSTEM ARCHIVE LOG ALL;
-- 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 TEMP1 ADD TEMPFILE '/oradata/xuexi/temp011.dbf'
     SIZE 19922944  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 5120M;
-- 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 "XUEXI" RESETLOGS  ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/oradata/xuexi/redo01.log'  SIZE 50M,
  GROUP 2 '/oradata/xuexi/redo02.log'  SIZE 50M,
  GROUP 3 '/oradata/xuexi/redo03.log'  SIZE 50M,
  GROUP 4 '/oradata/XUEXI/onlinelog/o1_mf_4_8yqwxqsh_.log'  SIZE 50M,
  GROUP 5 (
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1d59_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_5_8yqx1gvx_.log'
  ) SIZE 50M,
  GROUP 7 (
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m1ro_.log',
    '/oradata/XUEXI/onlinelog/o1_mf_7_8zl9m3gj_.log',
    '/oradata/logfile07.log'
  ) SIZE 100M
-- STANDBY LOGFILE
DATAFILE
  '/oradata/xuexi/system01.dbf',
  '/oradata/xuexi/undotbs01.dbf',
  '/oradata/xuexi/sysaux01.dbf',
  '/oradata/xuexi/users01.dbf',
  '/oradata/xuexi/XUEXI/datafile/o1_mf_tomf_8yqwrdoj_.dbf',
  '/oradata/xuexi/omf2.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp01.dbf',
  '/oradata/xuexi/XUEXI/datafile/testimp011.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo1.dbf',
  '/oradata/xuexi/XUEXI/datafile/testo2.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 '/archive/1_1_822350387.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350760.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822330757.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350003.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822349246.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822350252.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822374325.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/archive/1_1_822387818.dbf';
-- 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 TEMP1 ADD TEMPFILE '/oradata/xuexi/temp011.dbf'
     SIZE 19922944  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 5120M;
-- End of tempfile additions.
--

时间: 2024-09-20 05:59:56

重建控制文件,并且不干净的关闭数据库测试的相关文章

重建控制文件时resetlogs与noresetlogs的使用情况

重建控制文件时resetlogs与noresetlogs的使用情况 控制文件中记录着数据库的数据文件,日志文件,备份数据等信息,更为重要的,控制文件中还记录了数据库的检查点 和scn信息,这些信息在数据恢复的过程中将起到关键性作用. 一个正常运行的数据库,通常控制文件都存在多份镜像,这些镜像的内容是完全相同的,oracle缺省就创建多份控制 文件更说明了控制文件的重要: SQL> select name from v$controlfile; NAME ---------------------

oracle重建控制文件丢失数据文件导致悲剧

数据库最初故障 Thu Sep 25 09:27:26 2014 MMON started with pid=15, OS id=1968 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = F:\oracle Thu Sep 25 09

[20121105]重建控制文件少一个数据文件的情况.txt

[20121105]重建控制文件少一个数据文件的情况.txt 我的测试数据库经常做各种测试,resetlogs很多次,产生很多incarnation.今天想通过重建控制文件来清除这些信息. 我的控制文件的脚本是以前建立的,少包括一个数据文件.自己就拿这个做一个测试看看. 建立控制文件少包括'/u01/app/oracle11g/oradata/test/test01.dbf' STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "TEST"

ORACLE控制文件的重建

oracle|控制 数据库系统运行一段时间后有很多参数需要调整,有些参数可在$ORACLE_HOME/dbs/initXXX.ora文件中调整,而有些参数必须要在ORACLE的控制文件中调整.如ORACLE的缺省数据文件个数为30个,在系统需要扩表空间而数据文件个数不够时就需要进行调整. 一种方法是将所有数据全倒出来,重建库,再将数据倒进出.这种方法较麻烦. 二种方法是只重建控制文件,因为数据文件个数的限制参数存放在控制文件中. 以下是一种较好的重建控制文件的方法: 1. 备份数据库中的数据,以

Oracle损坏控制文件的恢复方法

一: 损坏单个控制文件 损坏单个控制文件是比较容易恢复的,因为一般的数据库系统,控制文件都不是一个,而且所有的控制文件都互为镜相,只要拷贝一个好的控制文件替换坏的控制文件就可以了. 1.控制文件损坏,最典型的就是启动数据库出错,不能mount数据库 SQL>startup ORA-00205: error in identifying controlfile, check alert log for more info 查看报警日志文件,有如下信息 alter database  mount M

控制文件多工

Oracle之控制文件   基于服务器参数文件(SPFILE)与初始化参数两个启动文件的不同,所以在为控制文件建立多工的操作也存在差异,首先,我们介绍下在Spfile启动的情况下,为控制文件建立多工的操作: 这里我准备了两个磁盘:一个是oracle安装的磁盘(SDA1),另外一个是已经格式化好的测试的磁盘(SDB1) 在SPFILE的环境下建立多工的步骤有四步: 1.修改SPFILE参数文件里的内容:2.shutdown 数据库:3.做物理控制文件的copy:4.startup数据库,检查结果:

探索ORACLE之RMAN_07控制文件丢失恢复

探索ORACLE之RMAN_07控制文件丢失恢复 作者:吴伟龙   Name:Prodence Woo QQ:286507175  msn:hapy-wuweilong@hotmail.com 1.     控制文件(controlfile)丢失恢复 基于控制文件的复合多路径性,它的丢失分为两种,一种是其中某个控制文件的损坏或丢失,另外一种是所有控制文件均丢失.基于第一种情况,只需把好的控制文件复制一份在损坏或丢失的那个控制文件路径下即可.第二种情况下则需要通过备份信息来对控制文件进行恢复或手工

Oracle 控制文件(CONTROLFILE)

--============================= -- Oracle 控制文件(CONTROLFILE) --=============================   一.Oracle 控制文件         为二进制文件,初始化大小由CREATE DATABASE指定,可以使用RMAN备份         记录了当前数据库的结构信息,同时也包含数据文件及日志文件的信息以及相关的状态,归档信息等等         在参数文件中描述其位置,个数等等.通常采用分散放开,多路复用

控制文件中MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS等参数的说明

CONTENTS -------- 1. What are the maximun number of datafiles ? MAXDATAFILES 2. What are the maximun number of redolog groups ? MAXLOGFILES 3. What are the maximun number of members for a redolog group ? MAXLOGMEMBERS 4. What are the maximun number o