加入收藏 | 设为首页 | 会员中心 | 我要投稿 李大同 （https://www.lidatong.com.cn/）- 科技、建站、经验、云计算、5G、大数据,站长网!
当前位置： 首页 > 百科 > 正文

控制文件损坏重建

发布时间：2020-12-12 15:00:29 所属栏目：百科 来源：网络整理
导读：SQL startup ORACLE instance started. Total System Global Area 5010685952 bytes Fixed Size 2261848 bytes Variable Size 3154119848 bytes Database Buffers 1845493760 bytes Redo Buffers 8810496 bytes ORA-01103: database name 'VERIFY' in contro
SQL> startup
ORACLE instance started.


Total System Global Area 5010685952 bytes
Fixed Size 2261848 bytes
Variable Size 3154119848 bytes
Database Buffers 1845493760 bytes
Redo Buffers 8810496 bytes
ORA-01103: database name 'VERIFY' in control file is not 'RESTORE1'



SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning,OLAP,Data Mining and Real Application Testing options
[oracle@newr5108g ~]$ vi pfile_bak




create controlfile reuse database restore1 noresetlog sarchivelog
LOGFILE
GROUP 1 '/data/OraData_0425/restore1/redo01.log',
GROUP 2 '/data/OraData_0425/restore1/redo02.log',
GROUP 3 '/data/OraData_0425/restore1/redo03.log',
GROUP 4 '/data/OraData_0425/restore1/redo04.dbf',
GROUP 5 '/data/OraData_0425/restore1/redo05.dbf',
GROUP 6 '/data/OraData_0425/restore1/redo06.dbf',
GROUP 7 '/data/OraData_0425/restore1/redo07.dbf',
GROUP 8 '/data/OraData_0425/restore1/redo08.dbf',
GROUP 9 '/data/OraData_0425/restore1/redo09.dbf',
GROUP 10 '/data/OraData_0425/restore1/redo10.dbf'
DATAFILE
'/data/OraData_0425/restore1/sysaux01.dbf',
'/data/OraData_0425/restore1/system01.dbf',
'/data/OraData_0425/restore1/undotbs01.dbf',
'/data/OraData_0425/restore1/users01.dbf',
'/data/OraData_0425/restore1/users02.dbf',
'/data/OraData_0425/restore1/users03.dbf',
'/data/OraData_0425/restore1/users04.dbf',
'/data/OraData_0425/restore1/users05.dbf'
CHARACTER SET ZHS16GBK;


[oracle@newr5108g ~]$ sqlplus / as sysdba


SQL*Plus: Release 11.2.0.4.0 Production on Tue Apr 25 15:51:21 2017


Copyright (c) 1982,2013,Oracle. All rights reserved.




Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning,Data Mining and Real Application Testing options


SQL> @1.sql Control file created. ----------------------------------- Tue Apr 25 15:51:24 2017 create controlfile reuse database restore1 noresetlogs archivelog LOGFILE GROUP 1 '/data/OraData_0425/restore1/redo01.log',GROUP 2 '/data/OraData_0425/restore1/redo02.log',GROUP 3 '/data/OraData_0425/restore1/redo03.log',GROUP 4 '/data/OraData_0425/restore1/redo04.dbf',GROUP 5 '/data/OraData_0425/restore1/redo05.dbf',GROUP 6 '/data/OraData_0425/restore1/redo06.dbf',GROUP 7 '/data/OraData_0425/restore1/redo07.dbf',GROUP 8 '/data/OraData_0425/restore1/redo08.dbf',GROUP 9 '/data/OraData_0425/restore1/redo09.dbf',GROUP 10 '/data/OraData_0425/restore1/redo10.dbf' DATAFILE '/data/OraData_0425/restore1/sysaux01.dbf','/data/OraData_0425/restore1/system01.dbf','/data/OraData_0425/restore1/undotbs01.dbf','/data/OraData_0425/restore1/users01.dbf','/data/OraData_0425/restore1/users02.dbf','/data/OraData_0425/restore1/users03.dbf','/data/OraData_0425/restore1/users04.dbf','/data/OraData_0425/restore1/users05.dbf' CHARACTER SET ZHS16GBK WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command Default Temporary Tablespace will be necessary for a locally managed database in future release Tue Apr 25 15:51:25 2017 Successful mount of redo thread 1,with mount id 273269180 Completed: create controlfile reuse database restore1 noresetlogs archivelog LOGFILE GROUP 1 '/data/OraData_0425/restore1/redo01.log','/data/OraData_0425/restore1/users05.dbf' CHARACTER SET ZHS16GBK Tue Apr 25 15:51:38 2017 alter database mount ORA-1100 signalled during: alter database mount... alter database open Initializing SCN for created control file Database SCN compatibility initialized to 1 Tue Apr 25 15:51:43 2017 LGWR: STARTING ARCH PROCESSES Tue Apr 25 15:51:43 2017 ARC0 started with pid=22,OS id=28261 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES Tue Apr 25 15:51:44 2017 ARC1 started with pid=23,OS id=28263 Tue Apr 25 15:51:44 2017 ARC2 started with pid=24,OS id=28265 Tue Apr 25 15:51:44 2017 ARC3 started with pid=25,OS id=28267 ARC1: Archival started ARC2: Archival started ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH ARC2: Becoming the heartbeat ARCH Thread 1 advanced to log sequence 6 (thread open) Thread 1 opened at log sequence 6 Current log# 4 seq# 6 mem# 0: /data/OraData_0425/restore1/redo04.dbf Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Tue Apr 25 15:51:45 2017 SMON: enabling cache recovery Archived Log entry 1 added for thread 1 sequence 3 ID 0x104a1d47 dest 1: Archived Log entry 2 added for thread 1 sequence 4 ID 0x104a1d47 dest 1: ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Archived Log entry 3 added for thread 1 sequence 5 ID 0x104a1d47 dest 1: [28257] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:3661451402 end:3661451852 diff:450 (4 seconds) Dictionary check beginning Tablespace 'TEMP' #3 found in data dictionary,but not in the controlfile. Adding to controlfile. Dictionary check complete Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery ********************************************************************* WARNING: The following temporary tablespaces contain no files. This condition can occur when a backup controlfile has been restored. It may be necessary to add files to these tablespaces. That can be done using the SQL statement: ALTER TABLESPACE <tablespace_name> ADD TEMPFILE Alternatively,if these temporary tablespaces are no longer needed,then they can be dropped. Empty temporary tablespace: TEMP ********************************************************************* Database Characterset is ZHS16GBK No Resource Manager plan active ********************************************************** WARNING: Files may exists in db_recovery_file_dest that are not known to the database. Use the RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If files cannot be cataloged,then manually delete them using OS command. One of the following events caused this: 1. A backup controlfile was restored. 2. A standby controlfile was restored. 3. The controlfile was re-created. 4. db_recovery_file_dest had previously been enabled and then disabled. ********************************************************** replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Tue Apr 25 15:51:48 2017 ----------------------------- SQL> alter database open; Database altered. SQL>

（编辑：李大同）

【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!
    相关内容
      推荐文章
        站长推荐
        热点阅读

          【免责声明】本站内容转载自互联网，其发布内容言论不代表本站观点，如果其链接、内容的侵犯您的权益，烦请提交相关链接至邮箱bqsm@foxmail.com我们将及时予以处理。

          建议您使用1920×1080分辨率、谷歌浏览器Google Chrome、Microsoft Edge以获得本站的最佳浏览效果

          Copygight © 2008-2022 https://www.lidatong.com.cn/ All Rights Reserved. 李大同