RAC环境启动数据库时报错:ORA-01105,ORA-19808 解决方法
RAC环境启动数据库时报错:ORA-01105,ORA-19808 解决方法
[Oracle@RedHat3919 dbs]$ srvctl start instance -d ylao -i ylao2
PRCR-1013 : Failed to start resource ora.ylao.db
PRCR-1064 : Failed to start resource ora.ylao.db on node redhat3920
CRS-5017: The resource action "ora.ylao.db start" encountered the following error:
ORA-01105: mount is incompatible with mounts by other instances
ORA-19808: recovery destination parameter mismatch
. For details refer to "(:CLSN00107:)" in "/oracle/app/grid/grid_home/log/redhat3920/agent/crsd/oraagent_oracle//oraagent_oracle.log".
CRS-2674: Start of 'ora.ylao.db' on 'redhat3920' failed
SQL> show parameter recover
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 4000G
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
SQL> create pfile='/home/oracle/initylao0720.ora' from spfile;
File created.
SQL> alter system set db_recovery_file_dest_size=200G scope=both;
System altered.
[oracle@redhat3919 ~]$ srvctl start instance -d ylao -i ylao2
SQL> show parameter recover
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 200G
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
[oracle@redhat3919 ~]$ oerr ora 19808
19808, 00000, "recovery destination parameter mismatch"
// Cause: The value of parameters DB_RECOVERY_FILE_DEST and
// DB_RECOVERY_FILE_DEST_SIZE must be same in all instances.
// instance. All databases must have same recovery destination
// parameters.
// Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE
// values in all instances.
[oracle@redhat3919 ~]$ oerr ora 01105
01105, 00000, "mount is incompatible with mounts by other instances"
// Cause: An attempt to mount the database discovered that another instance
// mounted a database by the same name, but the mount is not
// compatible. Additional errors are reported explaining why.
// Action: See accompanying errors.
[oracle@redhat3919 ~]$
更多Oracle相关信息见Oracle 专题页面 https://www.linuxidc.com/topicnews.aspx?tid=12
Linux公社的RSS地址:https://www.linuxidc.com/rssFeed.aspx
本文永久更新链接地址:https://www.linuxidc.com/Linux/2020-04/162975.htm
- 数据库启动时报ORA-00845错误解决方法
- 关于启动数据库后提示ora-12505的解决方法
- 删除EM,强制结束EM进程后,启动数据库ORA-00119,ORA-00132报错的解决方法
- 实例启动时报ORA-00845的解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- Oracle实例启动时报错:ORA-32004的解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- 实例启动时报ORA-00845的解决方法
- 修改主机名,无法启动数据库解决方法:ORA-00600: internal error code, arguments: [keltnfy-ldmInit]
- 删除EM,强制结束EM进程后,启动数据库ORA-00119,ORA-00132报错的解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- ORA-00257归档日志写满的解决方法 背景: 在前一篇博客中我们提到了如何启动或关闭oracle的归档(ARCHIVELOG)模式,在我成功设定数据库为归档模式以后, 第二天再次尝试连接数据库,
- RAC 安装patch 后启动实例 报错 ORA-00439 feature not enabled- Real Application Clusters 解决方法
- 启动数据库时提示ORA-03113: 通信通道的文件结尾解决方法
- 一次误修改sga_max_size值过大后导致数据库无法启动的解决方法