DG不能自动mount导致数据库不能正常启动:ORA-01157、ORA-01110、ORA-17503、ORA-15001、ORA-15001
2013-12-10 20:39
585 查看
DG不能自动mount导致数据库不能正常启动:ORA-01157、ORA-01110、ORA-17503、ORA-15001、ORA-15001
现象:
每次重启整个CRS之后,DB都不能自动开启到OPEN状态,查看alert日志报错:
SUCCESS: diskgroup UNID was mounted
Thu Nov 14 21:46:01 2013
Create Relation SWEEPERR
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 2364838615
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Thu Nov 14 21:46:05 2013
ALTER DATABASE OPEN MIGRATE
Errors in file /opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ORA-01157: cannot identify/lock data file 21 - see DBWR trace file
ORA-01110: data file 21: '+INDX/nc/datafile/INDX.256.820323481'
ORA-17503: ksfdopn:2 Failed to open file +INDX/nc/datafile/INDX.256.820323481
ORA-15001: diskgroup "INDX" does not exist or is not mounted
ORA-15001: diskgroup "INDX" does not exist or is not mounted
Errors in file /opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ORA-01157: cannot identify/lock data file 22 - see DBWR trace file
ORA-01110: data file 22: '+INDX/nc/datafile/INDX.257.820323659'
ORA-17503: ksfdopn:2 Failed to open file +INDX/nc/datafile/INDX.257.820323659
ORA-15001: diskgroup "INDX" does not exist or is not mounted
从alert日志可以看出,INDX DG的文件不能被读到,
查看发现INDX DG处于DISMOUNT状态。
分析:
ASM中创建了2个DG:UNID,INDX.每次只有UNID会被自动mount,而INDX不能被自动MOUNT。
查看asm_diskgroups参数发现只设置了UNID,这就是为什么每次INDX不会被自动MOUNT的原因了。
SQL>
SQL> show parameter asm
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups string UNID
SQL> show parameter pfile
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string
解决办法:
将INDX添加到asm_diskgroups参数中。
spfile:alter system set asm_diskgroups='UNID','INDX' scope=both;
pfile:修改pfile中asm_diskgroups参数。
现象:
每次重启整个CRS之后,DB都不能自动开启到OPEN状态,查看alert日志报错:
SUCCESS: diskgroup UNID was mounted
Thu Nov 14 21:46:01 2013
Create Relation SWEEPERR
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 2364838615
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Thu Nov 14 21:46:05 2013
ALTER DATABASE OPEN MIGRATE
Errors in file /opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ORA-01157: cannot identify/lock data file 21 - see DBWR trace file
ORA-01110: data file 21: '+INDX/nc/datafile/INDX.256.820323481'
ORA-17503: ksfdopn:2 Failed to open file +INDX/nc/datafile/INDX.256.820323481
ORA-15001: diskgroup "INDX" does not exist or is not mounted
ORA-15001: diskgroup "INDX" does not exist or is not mounted
Errors in file /opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ORA-01157: cannot identify/lock data file 22 - see DBWR trace file
ORA-01110: data file 22: '+INDX/nc/datafile/INDX.257.820323659'
ORA-17503: ksfdopn:2 Failed to open file +INDX/nc/datafile/INDX.257.820323659
ORA-15001: diskgroup "INDX" does not exist or is not mounted
从alert日志可以看出,INDX DG的文件不能被读到,
查看发现INDX DG处于DISMOUNT状态。
分析:
ASM中创建了2个DG:UNID,INDX.每次只有UNID会被自动mount,而INDX不能被自动MOUNT。
查看asm_diskgroups参数发现只设置了UNID,这就是为什么每次INDX不会被自动MOUNT的原因了。
SQL>
SQL> show parameter asm
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups string UNID
SQL> show parameter pfile
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string
解决办法:
将INDX添加到asm_diskgroups参数中。
spfile:alter system set asm_diskgroups='UNID','INDX' scope=both;
pfile:修改pfile中asm_diskgroups参数。
相关文章推荐
- ASM路径问题导致数据库不能正常启动 -- 报:ORA-03113: end-of-file on communication channel
- DBA手记之:数据库启动报ORA-01157和ORA-01110错误
- Oracle11.2.0.1.0集群数据库不能正常启动,报ORA-01078,ORA-01565,ORA-17503,ORA-12547错误
- ORA-01251错误oracle服务启动无法连接误删非法删除数据文件导致数据库不能打开ORA-01122 ORA-01251
- oracle客户端监听器不能自动启动,导致连接数据库失败
- 服务器突然断电造成oracle实例不能正常启动报ora-01172 ora-01151的解决方法
- oracle 启动时出现ORA-01157: cannot identify/lock data和ORA-01110: data file 错误
- 数据库flash_recovery_area满导致数据库启动报错ORA-03113错误
- 电脑位数(32位或者64位)问题导致eclipse不能正常启动
- Freebsd系统故障导致系统不能正常启动的恢复数据方法[图] 推荐
- hibernate中关于数据库方言导致不能自动生成数据库表的问题
- Eclipse非正常关闭导致不能正常启动
- Windows7蓝屏导致Oracle回滚段损坏(ORA-01115和ORA-27070)数据库无法启动的问题处理
- win10 占用80端口 导致 wamp apache服务不能正常启动
- 先安装SQL2008 R2后安装AD导致无法正常登陆数据库(无法启动MSSQLSERVER)
- Oracle 11g 参数修改错误导致数据库无法启动的处理方法.[ORA-01034,ORA-27101]
- Oracle数据库启动时出现ORA-01157和ORA-01110问题
- 磁盘空间满导致oracle不能正常使用:错误关键字ORA-09817 No space left on device
- ORA-01078,LRM-00109参数文件问题,导致数据库无法启动
- oracle数据库启动时出现ORA-01157和ORA-01110问题