重建控制文件
Oracle提供两种方式备份控制文件:
1.生成可以重建控制文件的脚本
2.备份二进制的控制文件
如何获得可以重建控制文件的脚本.在mount状态下获得trc文件
sql> alter database backup controlfile to trace as '/home/oracle/crontol_trace.trc';
[oracle@hbgf oracle]$ more /home/oracle/crontol_trace.trc -- 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="uniguard" -- -- 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_10='LOCATION=USE_DB_RECOVERY_FILE_DEST' -- LOG_ARCHIVE_DEST_10='OPTIONAL REOPEN=300 NODELAY' -- LOG_ARCHIVE_DEST_10='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC' -- LOG_ARCHIVE_DEST_10='REGISTER NOALTERNATE NODEPENDENCY' -- LOG_ARCHIVE_DEST_10='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME' -- LOG_ARCHIVE_DEST_10='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)' -- LOG_ARCHIVE_DEST_STATE_10=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 "UNIGUARD" NORESETLOGS NOARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 4672 LOGFILE GROUP 1 '/product/app/oracle/oradata/uniguard/redo01.log' SIZE 50M, GROUP 2 '/product/app/oracle/oradata/uniguard/redo02.log' SIZE 50M, GROUP 3 '/product/app/oracle/oradata/uniguard/redo03.log' SIZE 50M -- STANDBY LOGFILE
DATAFILE '/product/app/oracle/oradata/uniguard/system01.dbf', '/product/app/oracle/oradata/uniguard/undotbs01.dbf', '/product/app/oracle/oradata/uniguard/sysaux01.dbf', '/product/app/oracle/oradata/uniguard/users01.dbf', '/product/app/oracle/oradata/uniguard/info01.dbf', '/product/app/oracle/oradata/uniguard/index01.dbf', '/product/app/oracle/oradata/uniguard/dev01.dbf', '/product/app/oracle/oradata/uniguard/index02.dbf', '/product/app/oracle/oradata/uniguard/dev02.dbf', '/product/app/oracle/oradata/uniguard/dev03.dbf', '/product/app/oracle/oradata/uniguard/dev04.dbf' CHARACTER SET ZHS16GBK; -- 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 '/product/app/oracle/flash_recovery_area/UNIGUARD/archivelog/2012_04_11/o1_mf_1_1_%u_.arc'; -- ALTER DATABASE REGISTER LOGFILE '/product/app/oracle/flash_recovery_area/UNIGUARD/archivelog/2012_04_11/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 '/product/app/oracle/oradata/uniguard/temp01.dbf' SIZE 737148928 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M; -- End of tempfile additions. -- -- Set #2. RESETLOGS case -- -- The following commands will create a new control file and use it
编辑这个trace文件,我们就可以获得创建控制文件的sql.
sql>STARTUP NOMOUNT
sql>CREATE CONTROLFILE REUSE DATABASE "UNIGUARD" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 4672
LOGFILE
GROUP 1 '/product/app/oracle/oradata/uniguard/redo01.log' SIZE 50M,
GROUP 2 '/product/app/oracle/oradata/uniguard/redo02.log' SIZE 50M,
GROUP 3 '/product/app/oracle/oradata/uniguard/redo03.log' SIZE 50M
-- STANDBY LOGFILE
DATAFILE
'/product/app/oracle/oradata/uniguard/system01.dbf',
'/product/app/oracle/oradata/uniguard/undotbs01.dbf',
'/product/app/oracle/oradata/uniguard/sysaux01.dbf',
'/product/app/oracle/oradata/uniguard/users01.dbf',
'/product/app/oracle/oradata/uniguard/info01.dbf',
'/index/oradata/uniguard/index01.dbf',
'/devdata/oradata/uniguard/index01.dbf',
'/devdata/oradata/uniguard/indexdata02.dbf',
'/devdata/oradata/uniguard/dev01.dbf'
CHARACTER SET ZHS16GBK
;
sql>RECOVER DATABASE
sql>ALTER DATABASE OPEN;
sql>ALTER TABLESPACE TEMP ADD TEMPFILE '/product/app/oracle/oradata/uniguard/temp01.dbf'
SIZE 1244667904 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
以上给出生成创建控制文件脚本并重建控制文件的方法，但是具体恢复中遇到的问题可能需要具体对待,当得不到trace文件，可根据这个格式，查看数据文件，更改相关内容再重建.这种方法通常是在没有控制文件(二进制文件)备份的情况下所采用的，如果存在备份应该使用备份的控制文件尝试恢复.
注：
SQL>alter database backup controlfile to '\home\oracle\backup\control.bkp'; //备份二进制控制文件