OCP-1Z0-053-V12.02-551题

551.Which command will result in a trace file being created with the create controlfile command contained

in it?

A. alter database backup controlfile;

B. alter database backup controlfile to trace;

C. alter database controlfile backup;

D. alter database controlfile backup to '/ora01/oracle/ctrl_backup.ctl';

E. alter database begin controlfile backup;

Answer: B

答案解析: 

Backing Up Control Files

Use the ALTER DATABASE BACKUP CONTROLFILE statement to back up your control files. You have two options:

  • Back up the control file to a binary file (duplicate of existing control file) using the following statement:

    ALTER DATABASE BACKUP CONTROLFILE TO '/oracle/backup/control.bkp';
  • Produce SQL statements that can later be used to re-create your control file:

    ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

    This command writes a SQL script to a trace file where it can be captured and edited to reproduce the control file. View the alert log to determine the name and location of the trace file.

官方文档:http://docs.oracle.com/cd/E11882_01/server.112/e25494/control.htm#i1006485

演示:

sys@TEST0910> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
 
Database altered.
 
找出trace文件的路径
sys@TEST0910> show parameter dump
 
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
background_core_dump                 string      partial
background_dump_dest                 string      /u01/app/oracle/diag/rdbms/tes
                                                 t0910/test0910/trace
core_dump_dest                       string      /u01/app/oracle/diag/rdbms/tes
                                                 t0910/test0910/cdump
max_dump_file_size                   string      unlimited
shadow_core_dump                     string      partial
user_dump_dest                       string      /u01/app/oracle/diag/rdbms/tes
                                                 t0910/test0910/trace
 
 
进入trace文件的路径
[oracle@rtest ~]$ cd /u01/app/oracle/diag/rdbms/test0910/test0910/trace
[oracle@rtest trace]$ ls -lt 按照顺序排列
total 3656
-rw-r----- 1 oracle oinstall 188898 Sep 18 16:10 alert_test0910.log
-rw-r----- 1 oracle oinstall   7037 Sep 18 16:10 test0910_ora_6155.trc
-rw-r----- 1 oracle oinstall    132 Sep 18 16:10 test0910_ora_6155.trm
-rw-r----- 1 oracle oinstall  37725 Sep 18 16:09 test0910_mmon_31198.trc
-rw-r----- 1 oracle oinstall   3716 Sep 18 16:09 test0910_mmon_31198.trm
-rw-r----- 1 oracle oinstall   1011 Sep 18 06:00 test0910_j001_3483.trc

查看里面的内容:

[oracle@rtest trace]$ more test0910_ora_6155.trc
Trace file /u01/app/oracle/diag/rdbms/test0910/test0910/trace/test0910_ora_6155.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
System name:    Linux
Node name:      rtest.localdomain
Release:        2.6.18-308.el5
Version:        #1 SMP Fri Jan 27 17:17:51 EST 2012
Machine:        x86_64
VM name:        VMWare Version: 6
Instance name: test0910
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 6155, image: oracle@rtest.localdomain (TNS V1-V3)
 
 
*** 2013-09-18 16:10:10.439
*** SESSION ID:(96.201) 2013-09-18 16:10:10.439
*** CLIENT ID:() 2013-09-18 16:10:10.439
*** SERVICE NAME:(SYS$USERS) 2013-09-18 16:10:10.439
*** MODULE NAME:(sqlplus@rtest.localdomain (TNS V1-V3)) 2013-09-18 16:10:10.439
*** ACTION NAME:() 2013-09-18 16:10:10.439
 
-- 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="test0910"
--
-- 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 "TEST0910" NORESETLOGS  ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/u01/app/oracle/oradata/test0910/redo01.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 2 '/u01/app/oracle/oradata/test0910/redo02.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 3 '/u01/app/oracle/oradata/test0910/redo03.log'  SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '/u01/app/oracle/oradata/test0910/system01.dbf',
  '/u01/app/oracle/oradata/test0910/sysaux01.dbf',
  '/u01/app/oracle/oradata/test0910/undotbs01.dbf',
  '/u01/app/oracle/oradata/test0910/users01.dbf',
  '/u01/app/oracle/oradata/test0910/example01.dbf',
  '/u01/app/oracle/oradata/test0910/testtb.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/fast_recovery_area/TEST0910/archivelog/2013_09_18/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/fast_recovery_area/TEST0910/archivelog/2013_09_18/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
-- 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 '/u01/app/oracle/oradata/test0910/temp01.dbf'
     SIZE 30408704  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 "TEST0910" RESETLOGS  ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/u01/app/oracle/oradata/test0910/redo01.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 2 '/u01/app/oracle/oradata/test0910/redo02.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 3 '/u01/app/oracle/oradata/test0910/redo03.log'  SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '/u01/app/oracle/oradata/test0910/system01.dbf',
  '/u01/app/oracle/oradata/test0910/sysaux01.dbf',
  '/u01/app/oracle/oradata/test0910/undotbs01.dbf',
  '/u01/app/oracle/oradata/test0910/users01.dbf',
  '/u01/app/oracle/oradata/test0910/example01.dbf',
  '/u01/app/oracle/oradata/test0910/testtb.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/fast_recovery_area/TEST0910/archivelog/2013_09_18/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/fast_recovery_area/TEST0910/archivelog/2013_09_18/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/test0910/temp01.dbf'
     SIZE 30408704  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
-- End of tempfile additions.

 

原文地址:https://www.cnblogs.com/hzcya1995/p/13317234.html