failure of the “Grid Installatio…

RAC安装网格配置错误解析

最新推荐文章于 2024-09-03 17:29:35 发布

最新推荐文章于 2024-09-03 17:29:35 发布 · 185 阅读

文章标签：

#运维 #数据库

本文总结了RAC安装过程中出现的网格配置错误及解决办法。包括环境清理不彻底、用户权限不足、文件路径不匹配等问题，并提供了详细的错误日志分析及案例分享。

failure of the “Grid Installation Configuration” rac安装时关于网格配置错误小结

1. 原文：http://blog.ronnyegner-consulting.de/2010/04/17/11g-release-2-for-windows-buggy/

2. The failure of the “Grid Installation Configuration” step could be caused by many different kinds of errors, some of them silent (no useful information in any install logs)导致网格基础配置失败有很多原因，我这次遇到以下几个问题：1，第一次安装失败是环境没有清理干净2.某个脚本执行不了，是由于用户权限不够高3从安装包copy文件到节点一安装目录下时文件找不到，是由于两个zip包解压后的文件未放到同一个目录下

- Useful logs to look at are in \app\11.2.0\grid\cfgtoollogs\crsconfig – rootcrs_.log_OUT and rootcrs_.log

- We saw the same service errors as described in your post, as well as these error messages in the rootcrs_.log file:

StartService(OracleRemoteExecService) waiting for service to complete
service status 4, still waiting
…
service status 4, still waiting
service terminated (0×0)
Warning failed to Stop (OracleRemoteExecService) service. The service has not been started.

These errors do not seem to be a problem. We eventually were able to install RAC and then the DB successfully, and we still saw those errors. Everything seems to be working fine otherwise.

- In one case where the “Grid Installation Configuration” step failed, we saw these error messages:

DiskGroup DATA creation failed with the following message: ORA-15018: diskgroup cannot be createdORA-15307: disk DATA_0000 not discoverable by CSS

This was because the required disks to be used for OCR/voting ASM volume were not ‘online’ on the remote node.

- In another case where the “Grid Installation Configuration” step failed, we could see no useful error messages in any of the logs, but it turned out that our node hostnames could not be resolved by DNS, or by hosts file. Fixing the hostname resolution allowed us to install RAC successfully.

Our conclusion is that the RAC installer is very poor at providing useful error messages :( I was expecting much better from Oracle…

Anyway, I hope this information helps someone!