ITPub博客

首页 > Linux操作系统 > Linux操作系统 > 11.2打开数据库碰到ORA-214错误

11.2打开数据库碰到ORA-214错误

原创 Linux操作系统 作者:yangtingkun 时间:2011-02-17 21:15:52 0 删除 编辑

客户的测试服务器在没有关闭数据库的情况下,重启了系统,出现了这个错误。

 

 

数据库版本是11.2.0.2 for Linux 6 x86-64

由于数据库在打开使用的过程中,操作系统上执行了reboot操作,导致了ORA-214的错误,详细的错误信息为:

SQL> startup
ORACLE instance started.

Total System Global Area 4275781632 bytes
Fixed Size 2233336 bytes
Variable Size 3087010824 bytes
Database Buffers 1174405120 bytes
Redo Buffers 12132352 bytes
ORA-00214: control file '/opt/oracle/fast_recovery_area/MOBILEDB/control02.ctl' version 482 inconsistent with file '/data1/oradata/mobiledb/MOBILEDB/control01.ctl' version 451

不过我并没有亲眼看到这个错误,这个错误信息是客户发过来的,当我登录服务器执行启动命令打算重现问题时:

[oracle@Oracle111 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.2.0 Production on Thu Feb 17 14:27:25 2011

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

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 4275781632 bytes
Fixed Size                  2233336 bytes
Variable Size            3087010824 bytes
Database Buffers         1174405120 bytes
Redo Buffers               12132352 bytes
Database mounted.
Database opened.
SQL> show parameter control_file

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
control_file_record_keep_time        integer     7
control_files                        string      /data1/oradata/mobiledb/MOBILE
                                                 DB/control01.ctl, /opt/oracle/
                                                 fast_recovery_area/MOBILEDB/co
                                                 ntrol02.ctl

询问客户,客户说没有进行过恢复操作,检查alert文件:

Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =28
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /opt/oracle/product/11.2.0/db/dbs/spfilemobiledb.ora
System parameters with non-default values:
  processes                = 150
  sga_target               = 1536M
  control_files            = "/data1/oradata/mobiledb/MOBILEDB/control01.ctl"
  control_files            = "/opt/oracle/fast_recovery_area/MOBILEDB/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "/opt/oracle/fast_recovery_area"
  db_recovery_file_dest_size= 4977M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=mobiledbXDB)"
  audit_file_dest          = "/opt/oracle/admin/MOBILEDB/adump"
  audit_trail              = "DB"
  db_name                  = "MOBILEDB"
  open_cursors             = 300
  pga_aggregate_target     = 1657M
  diagnostic_dest          = "/opt/oracle"
Thu Feb 17 11:47:07 2011
PMON started with pid=2, OS id=3601
Thu Feb 17 11:47:07 2011
.
.
.
MMON started with pid=16, OS id=3631
Thu Feb 17 11:47:08 2011
MMNL started with pid=17, OS id=3633
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
Thu Feb 17 11:47:08 2011
ALTER DATABASE   MOUNT
Successful mount of redo thread 1, with mount id 3104105148
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Thu Feb 17 11:47:12 2011
ALTER DATABASE OPEN
Thread 1 opened at log sequence 69
  Current log# 3 seq# 69 mem# 0: /data1/oradata/mobiledb/MOBILEDB/redo03.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
[3644] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:4891584 end:4891624 diff:40 (0 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Thu Feb 17 11:47:13 2011
QMNC started with pid=21, OS id=3648
Completed: ALTER DATABASE OPEN
Thu Feb 17 11:47:13 2011
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Starting background process CJQ0
Thu Feb 17 11:47:13 2011
CJQ0 started with pid=22, OS id=3662
Thu Feb 17 11:57:13 2011
Starting background process SMCO
Thu Feb 17 11:57:13 2011
SMCO started with pid=20, OS id=3698
Thu Feb 17 13:32:40 2011
ALTER SYSTEM SET sga_max_size='4096M' SCOPE=SPFILE;
Thu Feb 17 13:41:07 2011
ALTER SYSTEM SET processes=1000 SCOPE=SPFILE;
Thu Feb 17 14:16:37 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =168
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /opt/oracle/product/11.2.0/db/dbs/spfilemobiledb.ora
System parameters with non-default values:
  processes                = 1000
  sga_max_size             = 4G
  sga_target               = 1536M
  control_files            = "/data1/oradata/mobiledb/MOBILEDB/control01.ctl"
  control_files            = "/opt/oracle/fast_recovery_area/MOBILEDB/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "/opt/oracle/fast_recovery_area"
  db_recovery_file_dest_size= 4977M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=mobiledbXDB)"
  audit_file_dest          = "/opt/oracle/admin/MOBILEDB/adump"
  audit_trail              = "DB"
  db_name                  = "MOBILEDB"
  open_cursors             = 300
  pga_aggregate_target     = 1657M
  diagnostic_dest          = "/opt/oracle"
Thu Feb 17 14:16:38 2011
PMON started with pid=2, OS id=2678
Thu Feb 17 14:16:38 2011
PSP0 started with pid=3, OS id=2680
.
.
.
MMNL started with pid=17, OS id=2710
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
Thu Feb 17 14:16:40 2011
ALTER DATABASE   MOUNT
ORA-214 signalled during: ALTER DATABASE   MOUNT...
Thu Feb 17 14:16:40 2011
Checker run found 2 new persistent data failures
Thu Feb 17 14:17:24 2011
alter database open
ORA-1507 signalled during: alter database open...
Thu Feb 17 14:17:56 2011
alter database open
ORA-1507 signalled during: alter database open...
Thu Feb 17 14:17:57 2011
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 2
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Thu Feb 17 14:18:02 2011
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Thu Feb 17 14:18:04 2011
Instance shutdown complete
Thu Feb 17 14:18:12 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =168
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /opt/oracle/product/11.2.0/db/dbs/spfilemobiledb.ora
System parameters with non-default values:
  processes                = 1000
  sga_max_size             = 4G
  sga_target               = 1536M
  control_files            = "/data1/oradata/mobiledb/MOBILEDB/control01.ctl"
  control_files            = "/opt/oracle/fast_recovery_area/MOBILEDB/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "/opt/oracle/fast_recovery_area"
  db_recovery_file_dest_size= 4977M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=mobiledbXDB)"
  audit_file_dest          = "/opt/oracle/admin/MOBILEDB/adump"
  audit_trail              = "DB"
  db_name                  = "MOBILEDB"
  open_cursors             = 300
  pga_aggregate_target     = 1657M
  diagnostic_dest          = "/opt/oracle"
Thu Feb 17 14:18:12 2011
PMON started with pid=2, OS id=2756
Thu Feb 17 14:18:12 2011
PSP0 started with pid=3, OS id=2758
Thu Feb 17 14:18:13 2011
.
.
.
Thu Feb 17 14:18:14 2011
MMNL started with pid=17, OS id=2788
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
Thu Feb 17 14:18:14 2011
ALTER DATABASE   MOUNT
ORA-214 signalled during: ALTER DATABASE   MOUNT...
Thu Feb 17 14:19:26 2011
Starting ORACLE instance (normal)
Thu Feb 17 14:20:35 2011
alter database open
ORA-1507 signalled during: alter database open...
alter database mount
ORA-214 signalled during: alter database mount...
Thu Feb 17 14:21:20 2011
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 2
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
ARCH: Archival disabled due to shutdown: 1089
Thu Feb 17 14:21:23 2011
Stopping background process VKTMShutting down archive processes

Archiving is disabled
Thu Feb 17 14:21:25 2011
Instance shutdown complete
Thu Feb 17 14:27:33 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =168
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /opt/oracle/product/11.2.0/db/dbs/spfilemobiledb.ora
System parameters with non-default values:
  processes                = 1000
  sga_max_size             = 4G
  sga_target               = 1536M
  control_files            = "/data1/oradata/mobiledb/MOBILEDB/control01.ctl"
  control_files            = "/opt/oracle/fast_recovery_area/MOBILEDB/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "/opt/oracle/fast_recovery_area"
  db_recovery_file_dest_size= 4977M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=mobiledbXDB)"
  audit_file_dest          = "/opt/oracle/admin/MOBILEDB/adump"
  audit_trail              = "DB"
  db_name                  = "MOBILEDB"
  open_cursors             = 300
  pga_aggregate_target     = 1657M
  diagnostic_dest          = "/opt/oracle"
Thu Feb 17 14:27:34 2011
PMON started with pid=2, OS id=2962
Thu Feb 17 14:27:34 2011
PSP0 started with pid=3, OS id=2964
Thu Feb 17 14:27:35 2011
.
.
.
MMNL started with pid=17, OS id=2994
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
Thu Feb 17 14:27:35 2011
ALTER DATABASE   MOUNT
Successful mount of redo thread 1, with mount id 3104082775
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Thu Feb 17 14:27:39 2011
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
 parallel recovery started with 15 processes
Started redo scan
Completed redo scan
 read 29 KB redo, 31 data blocks need recovery
Started redo application at
 Thread 1: logseq 69, block 87640
Recovery of Online Redo Log: Thread 1 Group 3 Seq 69 Reading mem 0
  Mem# 0: /data1/oradata/mobiledb/MOBILEDB/redo03.log
Completed redo application of 0.02MB
Completed crash recovery at
 Thread 1: logseq 69, block 87699, scn 1018311
 31 data blocks read, 31 data blocks written, 29 redo k-bytes read
Thread 1 advanced to log sequence 70 (thread open)
Thread 1 opened at log sequence 70
  Current log# 1 seq# 70 mem# 0: /data1/oradata/mobiledb/MOBILEDB/redo01.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
[3004] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:907194 end:907484 diff:290 (2 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Thu Feb 17 14:27:42 2011
QMNC started with pid=36, OS id=3038
Completed: ALTER DATABASE OPEN

只是重启了两次,而没有人去修改控制文件,难道Oracle就自愈了这个问题。后来询问客户得知,当时正在向操作系统上挂载新的目录,而控制文件control01.ctl就处于被挂载的目录下,而客户执行的reboot也是为了验证目录在重启后能否自动挂载。

观察控制文件的不一致信息发现,control01.ctl比非挂载点上的control02.ctl的版本低,很可能是由于挂载重现了问题,而导致这个文件的需要在操作系统级别恢复,当最后成功挂载后,这个文件的状态也恢复了正常,因此错误也就消失了。

 

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/4227/viewspace-687470/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论
暂无介绍

注册时间:2007-12-29

  • 博文量
    1955
  • 访问量
    10523147