Chinaunix首页 | 论坛 | 博客
  • 博客访问: 234801
  • 博文数量: 57
  • 博客积分: 1149
  • 博客等级: 少尉
  • 技术积分: 584
  • 用 户 组: 普通用户
  • 注册时间: 2011-10-29 11:35
文章分类

全部博文(57)

文章存档

2016年(1)

2014年(1)

2013年(2)

2012年(27)

2011年(26)

分类: Oracle

2012-02-16 14:31:37

SQL> alter database backup controlfile to trace

  2  ;

 

数据库已更改。

 

SQL> show parameter user;

 

NAME                                 TYPE

------------------------------------ ---------------------------------

VALUE

------------------------------

license_max_users                    integer

0

parallel_adaptive_multi_user         boolean

TRUE

redo_transport_user                  string

 

user_dump_dest                       string

/u01/app/diag/rdbms/site2/site

2/trace

 

 

 

 

 

 

cat site2_ora_16316.trc | more

Trace file /u01/app/diag/rdbms/site2/site2/trace/site2_ora_16316.trc

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

ORACLE_HOME = /u01/app/oracle/product/10.2.0.1

System name:    Linux

Node name:      centos231

Release:        2.6.18-164.el5

Version:        #1 SMP Thu Sep 3 03:33:56 EDT 2009

Machine:        i686

Instance name: site2

Redo thread mounted by this instance: 1

Oracle process number: 35

Unix process pid: 16316, image: oracle@centos231 (TNS V1-V3)

 

 

*** 2011-07-14 14:33:08.185

*** SESSION ID:(180.374) 2011-07-14 14:33:08.185

*** CLIENT ID:() 2011-07-14 14:33:08.185

*** SERVICE NAME:(SYS$USERS) 2011-07-14 14:33:08.185

*** MODULE NAME:(sqlplus@centos231 (TNS V1-V3)) 2011-07-14 14:33:08.185

*** ACTION NAME:() 2011-07-14 14:33:08.185

 

-- 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="site2"

--

-- 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 "SITE2" NORESETLOGS  NOARCHIVELOG

    MAXLOGFILES 16

    MAXLOGMEMBERS 3

    MAXDATAFILES 100

    MAXINSTANCES 8

    MAXLOGHISTORY 292

LOGFILE

  GROUP 1 '/u01/oradata/site2/redo01.log'  SIZE 50M BLOCKSIZE 512,

  GROUP 2 '/u01/oradata/site2/redo02.log'  SIZE 50M BLOCKSIZE 512,

  GROUP 3 '/u01/oradata/site2/redo03.log'  SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  '/u01/oradata/site2/system01.dbf',

  '/u01/oradata/site2/sysaux01.dbf',

  '/u01/oradata/site2/undotbs01.dbf',

  '/u01/oradata/site2/users01.dbf',

  '/u01/oradata/site2/tg_data1.dbf',

  '/u01/oradata/site2/tg_data2.dbf',

  '/u01/oradata/site2/tg_data3.dbf',

  '/u01/oradata/site2/tg_data4.dbf',

  '/data/tg/users01.dbf',

  '/u01/oradata/site2/system02.dbf',

  '/u01/oradata/site2/users02.dbf',

  '/u01/oradata/site2/users03.dbf',

  '/u01/oradata/site2/users04.dbf',

  '/u01/oradata/site2/users05.dbf',

  '/u01/oradata/site2/users06.dbf',

  '/data/tg/users02.dbf',

  '/data/tg/users03.dbf',

  '/data/tg/users04.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/flash_recovery_area/SITE2/archivelog/2011_07_14/o1_mf_1_

1_%u_.arc';

-- ALTER DATABASE REGISTER LOGFILE '/u01/app/flash_recovery_area/SITE2/archivelog/2011_07_14/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/oradata/site2/temp02.dbf'

     SIZE 10240M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/oradata/site2/temp01.dbf'

     SIZE 10240M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TG_TEMP ADD TEMPFILE '/u01/oradata/site2/tg_temp3.dbf'

     SIZE 2048M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TG_TEMP ADD TEMPFILE '/u01/oradata/site2/tg_temp2.dbf'

     SIZE 2048M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TG_TEMP ADD TEMPFILE '/u01/oradata/site2/tg_temp1.dbf'

     SIZE 2048M 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 "SITE2" RESETLOGS  NOARCHIVELOG

    MAXLOGFILES 16

    MAXLOGMEMBERS 3

    MAXDATAFILES 100

    MAXINSTANCES 8

    MAXLOGHISTORY 292

LOGFILE

  GROUP 1 '/u01/oradata/site2/redo01.log'  SIZE 50M BLOCKSIZE 512,

  GROUP 2 '/u01/oradata/site2/redo02.log'  SIZE 50M BLOCKSIZE 512,

  GROUP 3 '/u01/oradata/site2/redo03.log'  SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  '/u01/oradata/site2/system01.dbf',

  '/u01/oradata/site2/sysaux01.dbf',

  '/u01/oradata/site2/undotbs01.dbf',

  '/u01/oradata/site2/users01.dbf',

  '/u01/oradata/site2/tg_data1.dbf',

  '/u01/oradata/site2/tg_data2.dbf',

  '/u01/oradata/site2/tg_data3.dbf',

  '/u01/oradata/site2/tg_data4.dbf',

  '/data/tg/users01.dbf',

  '/u01/oradata/site2/system02.dbf',

  '/u01/oradata/site2/users02.dbf',

  '/u01/oradata/site2/users03.dbf',

  '/u01/oradata/site2/users04.dbf',

  '/u01/oradata/site2/users05.dbf',

  '/u01/oradata/site2/users06.dbf',

  '/data/tg/users02.dbf',

  '/data/tg/users03.dbf',

  '/data/tg/users04.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/flash_recovery_area/SITE2/archivelog/2011_07_14/o1_mf_1_

1_%u_.arc';

-- ALTER DATABASE REGISTER LOGFILE '/u01/app/flash_recovery_area/SITE2/archivelog/2011_07_14/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/oradata/site2/temp02.dbf'

     SIZE 10240M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/oradata/site2/temp01.dbf'

     SIZE 10240M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TG_TEMP ADD TEMPFILE '/u01/oradata/site2/tg_temp3.dbf'

     SIZE 2048M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TG_TEMP ADD TEMPFILE '/u01/oradata/site2/tg_temp2.dbf'

     SIZE 2048M REUSE AUTOEXTEND OFF;

ALTER TABLESPACE TG_TEMP ADD TEMPFILE '/u01/oradata/site2/tg_temp1.dbf'

     SIZE 2048M REUSE AUTOEXTEND OFF;

-- End of tempfile additions.

--

阅读(1873) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~