Oracle 10g控制文件备份到文件与手工恢复

Oracle 10g控制文件备份到文件与手工恢复

测试使用alter database backup controlfile to trace命令备份Oracle10g控制文件

以及在丢失控制文件的情况下恢复控制文件之--备份控制文件

查看alter database backup controlfile to trace的默认路径
SQL> show parameter user_dump_dest;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
user_dump_dest string /data/oracle/admin/asp/udump
这是下面的备份控制文件语句默认备份的位置.

执行备份控制文件：
SQL> alter database backup controlfile to trace;
Database altered.

/data/oracle/admin/asp/udump下面会有很多跟踪文件 如何确认是哪一个是备份的控制文件文本呢

SQL> select a.spid from v$process a, v$session b where a.addr=b.paddr and b.username='SYS';
SPID
------------
31331

SQL> !ls -l /data/oracle/admin/asp/udump | grep 31331
-rw-r----- 1 oracle oinstall 6830 Jul 4 23:50 sdk_ora_31331.trc

这样就找到了对应的文件了

附：其实可以指定备份的路径和文件名：
SQL> alter database backup controlfile to trace as '/home/oracle/sdk_control.ctl';
Database altered.

查看文件 蓝色字体部分标记了对应的建立控制文件的语句：

注意这里面记录了两种情况：

Set #1. NORESETLOGS case

SQL> !cat /data/oracle/admin/asp/udump/sdk_ora_31331.trc
/data/oracle/admin/asp/udump/sdk_ora_31331.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /data/oracle/product/10.2.0/db_1
System name: Linux
Node name: RedHat10g
Release: 2.6.9-78.ELsmp
Version: #1 SMP Wed Jul 9 15:39:47 EDT 2008
Machine: i686
Instance name: sdk
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 31331, image: oracle@redhat10g (TNS V1-V3)

*** SERVICE NAME:(SYS$USERS) 2013-07-04 23:50:42.686
*** SESSION ID:(159.17) 2013-07-04 23:50:42.686
*** 2013-07-04 23:50:42.686
-- 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=redhat10g_%t_%r_%s.dbf
--
-- DB_UNIQUE_NAME="asp"
--
-- 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=/data/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 "ASP" NORESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/data/oracle/oradata/asp/redo01.log' SIZE 50M,
GROUP 2 '/data/oracle/oradata/asp/redo02.log' SIZE 50M,
GROUP 3 '/data/oracle/oradata/asp/redo03.log' SIZE 50M
-- STANDBY LOGFILE
DATAFILE
'/data/oracle/oradata/asp/system01.dbf',
'/data/oracle/oradata/asp/undotbs01.dbf',
'/data/oracle/oradata/asp/sysaux01.dbf',
'/data/oracle/oradata/asp/users01.dbf',
'/data/oracle/oradata/asp/dgbc01.dbf',
'/data/oracle/oradata/asp/dgbc02.dbf',
'/data/oracle/oradata/asp/dgbc03.dbf',
'/data/oracle/oradata/asp/dgbc04.dbf',
'/data/oracle/oradata/asp/dgbc05.dbf',
'/data/oracle/oradata/asp/dgbc06.dbf'
CHARACTER SET WE8ISO8859P1
;
-- 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 '/data/archive/redhat10g_1_562360180_1.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/data/archive/redhat10g_1_817828234_1.dbf';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- Set Database Guard and/or Supplemental Logging
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
-- 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 TEMP ADD TEMPFILE '/data/oracle/oradata/asp/temp01.dbf'
SIZE 20971520 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
-- 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 "ASP" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/data/oracle/oradata/asp/redo01.log' SIZE 50M,
GROUP 2 '/data/oracle/oradata/asp/redo02.log' SIZE 50M,
GROUP 3 '/data/oracle/oradata/asp/redo03.log' SIZE 50M
-- STANDBY LOGFILE
DATAFILE
'/data/oracle/oradata/asp/system01.dbf',
'/data/oracle/oradata/asp/undotbs01.dbf',
'/data/oracle/oradata/asp/sysaux01.dbf',
'/data/oracle/oradata/asp/users01.dbf',
'/data/oracle/oradata/asp/dgbc01.dbf',
'/data/oracle/oradata/asp/dgbc02.dbf',
'/data/oracle/oradata/asp/dgbc03.dbf',
'/data/oracle/oradata/asp/dgbc04.dbf',
'/data/oracle/oradata/asp/dgbc05.dbf',
'/data/oracle/oradata/asp/dgbc06.dbf'
CHARACTER SET WE8ISO8859P1
;
-- 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 '/data/archive/redhat10g_1_562360180_1.dbf';
-- ALTER DATABASE REGISTER LOGFILE '/data/archive/redhat10g_1_817828234_1.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
-- Set Database Guard and/or Supplemental Logging
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
-- 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 '/data/oracle/oradata/asp/temp01.dbf'
SIZE 20971520 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
-- End of tempfile additions.
--

下一篇 从这个备份的文本文件来手工恢复控制文件。