oracle ORA-01207:文件比控制文件更新 - 旧的控制文件

最新推荐文章于 2024-05-25 19:55:22 发布

丑大狗

最新推荐文章于 2024-05-25 19:55:22 发布

阅读量5k

点赞数

分类专栏： ORACLE DATABASE

本文链接：https://blog.csdn.net/u011478909/article/details/52027878

版权

ORACLE DATABASE 专栏收录该内容

56 篇文章 1 订阅

订阅专栏

SQL> startup
ORACLE instance started.

Total System Global Area 956198912 bytes
Fixed Size            2234120 bytes
Variable Size          620759288 bytes
Database Buffers      327155712 bytes
Redo Buffers            6049792 bytes
Database mounted.
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '+DATA2/orcl/datafile/system.256.917734557'
ORA-01207: file is more recent than control file - old control file

启动数据库报错。

先执行如下命令生成controlfile trace

SQL> alter database backup controlfile to trace as '/home/oracle/control.sql';

查看文件内容如下：

[oracle@hadoop01 ~]$ cat control.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="orcl"
--
-- 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 "ORCL" NORESETLOGS  ARCHIVELOG
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    MAXINSTANCES 32
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 (
    '+DATA/orcl/onlinelog/group_1.262.917467235',
    '+DATA/orcl/onlinelog/group_1.263.917467239'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 2 (
    '+DATA/orcl/onlinelog/group_2.264.917467241',
    '+DATA/orcl/onlinelog/group_2.265.917467245'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 3 (
    '+DATA/orcl/onlinelog/group_3.269.917467587',
    '+DATA/orcl/onlinelog/group_3.270.917467591'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 4 (
    '+DATA/orcl/onlinelog/group_4.271.917467595',
    '+DATA/orcl/onlinelog/group_4.272.917467599'
  ) SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '+DATA2/orcl/datafile/system.256.917734557',
  '+DATA2/orcl/datafile/sysaux.257.917734593',
  '+DATA2/orcl/datafile/undotbs1.259.917734633',
  '+DATA2/orcl/datafile/users.263.917734657',
  '+DATA2/orcl/datafile/example.258.917734617',
  '+DATA2/orcl/datafile/undotbs2.261.917734647',
  '+DATA2/orcl/datafile/users.260.917734639'
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 '+DATA2';
-- ALTER DATABASE REGISTER LOGFILE '+DATA2';
-- 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 '+DATA/orcl/tempfile/temp.266.917467257' REUSE;
-- 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 "ORCL" RESETLOGS  ARCHIVELOG
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    MAXINSTANCES 32
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 (
    '+DATA/orcl/onlinelog/group_1.262.917467235',
    '+DATA/orcl/onlinelog/group_1.263.917467239'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 2 (
    '+DATA/orcl/onlinelog/group_2.264.917467241',
    '+DATA/orcl/onlinelog/group_2.265.917467245'
  ) SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '+DATA2/orcl/datafile/system.256.917734557',
  '+DATA2/orcl/datafile/sysaux.257.917734593',
  '+DATA2/orcl/datafile/undotbs1.259.917734633',
  '+DATA2/orcl/datafile/users.263.917734657',
  '+DATA2/orcl/datafile/example.258.917734617',
  '+DATA2/orcl/datafile/undotbs2.261.917734647',
  '+DATA2/orcl/datafile/users.260.917734639'
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 '+DATA2';
-- ALTER DATABASE REGISTER LOGFILE '+DATA2';
-- 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

-- Create log files for threads other than thread one.
ALTER DATABASE ADD LOGFILE THREAD 2
  GROUP 3 (
    '+DATA/orcl/onlinelog/group_3.269.917467587',
    '+DATA/orcl/onlinelog/group_3.270.917467591'
  ) SIZE 50M BLOCKSIZE 512 REUSE,
  GROUP 4 (
    '+DATA/orcl/onlinelog/group_4.271.917467595',
    '+DATA/orcl/onlinelog/group_4.272.917467599'
  ) SIZE 50M BLOCKSIZE 512 REUSE;

-- 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/orcl/tempfile/temp.266.917467257' REUSE;
-- End of tempfile additions.
--

修改control.sql文件保留如下部分：

STARTUP NOMOUNT;
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS  ARCHIVELOG
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    MAXINSTANCES 32
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 (
    '+DATA/orcl/onlinelog/group_1.262.917467235',
    '+DATA/orcl/onlinelog/group_1.263.917467239'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 2 (
    '+DATA/orcl/onlinelog/group_2.264.917467241',
    '+DATA/orcl/onlinelog/group_2.265.917467245'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 3 (
    '+DATA/orcl/onlinelog/group_3.269.917467587',
    '+DATA/orcl/onlinelog/group_3.270.917467591'
  ) SIZE 50M BLOCKSIZE 512,
  GROUP 4 (
    '+DATA/orcl/onlinelog/group_4.271.917467595',
    '+DATA/orcl/onlinelog/group_4.272.917467599'
  ) SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '+DATA2/orcl/datafile/system.256.917734557',
  '+DATA2/orcl/datafile/sysaux.257.917734593',
  '+DATA2/orcl/datafile/undotbs1.259.917734633',
  '+DATA2/orcl/datafile/users.263.917734657',
  '+DATA2/orcl/datafile/example.258.917734617',
  '+DATA2/orcl/datafile/undotbs2.261.917734647',
  '+DATA2/orcl/datafile/users.260.917734639'
CHARACTER SET AL32UTF8
;

RECOVER DATABASE

ALTER SYSTEM ARCHIVE LOG ALL;

ALTER DATABASE OPEN;

然后sqlplus 执行control.sql文件，报如下错误：

ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-12720: operation requires database is in EXCLUSIVE mode

因为是rac环境，所以需要做进一步操作。

alter system set cluster_database=FALSE scope=spfile sid='*';
shutdown immediate;

完成上面两步之后再次执行control.sql

SQL> @control
ORACLE instance started.

Total System Global Area  956198912 bytes
Fixed Size		    2234120 bytes
Variable Size		  620759288 bytes
Database Buffers	  327155712 bytes
Redo Buffers		    6049792 bytes

Control file created.

ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required



System altered.


Database altered.

执行：

alter system set cluster_database=true scope=spfile sid='*';
shutdown immediate;

恢复rac环境

然后srvctl start database -d orcl 即可

丑大狗

关注

0
点赞
踩
3

收藏

觉得还不错? 一键收藏
0
评论
oracle ORA-01207:文件比控制文件更新 - 旧的控制文件

SQL> startupORACLE instance started.Total System Global Area 956198912 bytesFixed Size 2234120 bytesVariable Size 620759288 bytesDatabase Buffers 327155712 bytes
复制链接

扫一扫