DG不能自动mount导致数据库不能正常启动：ORA-01157、ORA-01110、ORA-17503、ORA-15001、ORA-15001

最新推荐文章于 2024-06-17 09:43:44 发布

zhou1862324

最新推荐文章于 2024-06-17 09:43:44 发布

阅读量1.9k

点赞数

分类专栏： RAC

本文链接：https://blog.csdn.net/zhou1862324/article/details/17250301

版权

本文介绍了Oracle数据库在DG自动挂载失败后，启动时遇到的ORA-01157、ORA-01110、ORA-17503和ORA-15001错误。通过分析日志发现INDX磁盘组未自动挂载，原因是asm_diskgroups参数只配置了UNID。解决方案是将INDX添加到该参数中，从而确保两个磁盘组都能正确挂载。

摘要由CSDN通过智能技术生成

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