BUG:Failed to create or upgrade OLR

2024-04-18 02:18
文章标签 failed bug create olr upgrade

本文主要是介绍BUG:Failed to create or upgrade OLR,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

64位CPU安装32位 ORACLE
参考链接: http://blog.csdn.net/robinson_0612/article/details/8294969
patch: p8670579_112010_LINUX.zip
如果之前也装CRS没有清除干净也可能出现这样的问题。
链接: http://candon123.blog.51cto.com/704299/467663

1、安装时的环境   
  操作系统(Oracle linux 5.5 32bit)   
  [root@node1 ~]# cat /etc/issue    
  Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)   
  Kernel \r on an \m   
  Oracle版本   
  Oracle 11g RAC R2(32bit)   
  宿主机系统   
  Win7 64bit + vmware server 2.0.2   
 
2、错误再现 
  [root@node1 ~]# /u01/app/11.2.0/grid/root.sh  
  Running Oracle 11g root.sh script... 
   
  The following environment variables are set as: 
      ORACLE_OWNER= grid 
      ORACLE_HOME=  /u01/app/11.2.0/grid 
   
  Enter the full pathname of the local bin directory: [/usr/local/bin]:  
     Copying dbhome to /usr/local/bin ... 
     Copying oraenv to /usr/local/bin ... 
     Copying coraenv to /usr/local/bin ... 
   
  Creating /etc/oratab file... 
  Entries will be added to the /etc/oratab file as needed by 
  Database Configuration Assistant when a database is created 
  Finished running generic part of root.sh script. 
  Now product-specific root actions will be performed. 
  2012-12-12 21:20:04: Parsing the host name 
  2012-12-12 21:20:04: Checking for super user privileges 
  2012-12-12 21:20:04: User has super user privileges 
  Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params 
  Creating trace directory 
  Failure with signal 11 from command: /u01/app/11.2.0/grid/bin/ocrconfig -local -upgrade grid oinstall 
  Failed to create or upgrade OLR 
 
  #查看日志文件 
  [grid@node1 ~]$ cd $ORACLE_HOME/log/node1 
  [grid@node1 node1]$ pwd 
  /u01/app/11.2.0/grid/log/node1 
  [grid@node1 node1]$ ls 
  admin  agent  alertnode1.log  client  crsd  cssd  ctssd  diskmon  evmd  gipcd  gnsd  gpnpd  mdnsd  ohasd  racg  srvm 
  [grid@node1 node1]$ tail -30 alertnode1.log 
  Oracle Database 11g Clusterware Release 11.2.0.1.0 - Production Copyright 1996, 2009 Oracle. All rights reserved. 
  2012-12-12 21:20:06.347 
  [client(14059)]CRS-2106:The OLR location /u01/app/11.2.0/grid/cdata/node1.olr is inaccessible. 
   Details in /u01/app/11.2.0/grid/log/node1/client/ocrconfig_14059.log. 
  #也可以根据上面的描述查看日志的详细信息,此处省略 
 
3、问题分析 
  关于这个问题,Meatlink 上[ID 1068212.1]有关于这个问题的描述,同时也说明明了由bug 8670579所引起的,而且还是未公开的,说是 
  不认识新的AMD芯片,我倒... 
  一起来看看解决办法吧。  
 
  Cause 
 Unpublished bug 8670579 which relates to the identification of newer AMD chips and therefore only affect platforms  
 using the newer AMD chips. 
 Solution 
 If the error occurs during the installation of the GRID Infrastructure the patch has to be applied,  
 before the root.sh Script. in the installation is run: 
 a.) Run a installation (grid/runInstaller) to the prompt where it requests to run orainstroot.sh and <GRID_HOME>/root.sh 
 b.) Run orainstroot.sh on all nodes, but not root.sh 
 c.) Open another session with the Oracle User and apply Patch 8670579 on all nodes (with opatch apply). 
 d.) Continue with the root.sh from the installation. 
 If you hit this bug, and have already started root.sh then: 
 - Deconfigure Clusterware on the failed host with <GRID_HOME>/install/rootcrs.pl -deconfig -force 
 - Install the Patch as Oracle User (opatch apply) 
 - Rerun root.sh 
 
  上面的描述说明了两种情况。 
 a. 仅仅在所有节点执行了orainstroot.sh,还没有执行root.sh 
   那么使用grid用户再开一个session, 
   在所有节点使用opatch来打补丁(8670579) 
   再运行root.sh 
 b. 已经执行了root.sh 
   使用root帐户先deconfigure之前的配置 
   使用grid再打补丁(grid), 
   重新运行root.sh 

解决步骤:
1、 [root@rac1 install]# ./rootcrs.pl -deconfig -verbose -force    清除之前配置的文件
2012-12-24 02:05:07: Parsing the host name
2012-12-24 02:05:07: Checking for super user privileges
2012-12-24 02:05:07: User has super user privileges
Using configuration parameter file: ./crsconfig_params
PRCR-1035 : Failed to look up CRS resource ora.cluster_vip.type for 1
PRCR-1068 : Failed to query resources
Cannot communicate with crsd
PRCR-1070 : Failed to check if resource ora.gsd is registered
Cannot communicate with crsd
PRCR-1070 : Failed to check if resource ora.ons is registered
Cannot communicate with crsd
PRCR-1070 : Failed to check if resource ora.eons is registered
Cannot communicate with crsd
ACFS-9200: Supported
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4000: Command Stop failed, or completed with errors.
Failure at scls_scr_setval with code 8
Internal Error Information:
  Category: -2
 Operation: failed
  Location: scrsearch3
  Other: id doesnt exist scls_scr_setval
  System Dependent Information: 2
CRS-4544: Unable to connect to OHAS
CRS-4000: Command Stop failed, or completed with errors.
error: package cvuqdisk is not installed
Successfully deconfigured Oracle clusterware stack on this node
2、 grid@rac1[/home/grid]cd/oracle/app/crs_home/OPatch/
grid@rac1[/oracle/app/crs_home/OPatch]./opatchapply /tmp/oracle/8670579
Invoking OPatch 11.1.0.6.6
Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation.  All rights reserved.
Oracle Home       : /oracle/app/crs_home
Central Inventory : /oracle/app/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.6
OUI version       : 11.2.0.1.0
OUI location      : /oracle/app/crs_home/oui
Log file location : /oracle/app/crs_home/cfgtoollogs/opatch/opatch2012-12-24_02-13-13AM.log
Patch history file: /oracle/app/crs_home/cfgtoollogs/opatch/opatch_history.txt
--------------------------------------------------------------------------------
The patch has more than one Archive Action but there is no Make Action.
--------------------------------------------------------------------------------
ApplySession applying interim patch '8670579' to OH '/oracle/app/crs_home'
Running prerequisite checks...
OPatch detected the node list and the local node from the inventory.  OPatch will patch the local system then propagate the patch to the remote nodes.
This node is part of an Oracle Real Application Cluster.
Remote nodes: 'rac2'
Local node: 'rac1'
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/oracle/app/crs_home')
Is the local system ready for patching? [y|n]

User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '8670579' for restore. This might take a while...
Backing up files affected by the patch '8670579' for rollback. This might take a while...
Patching component oracle.network.rsf, 11.2.0.1.0...
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/ahseteco.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/am11rkg.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/amsha.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/cpui32.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/sha.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/x931rand.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/am11dkg.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/am931rnd.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/amsharnd.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/ghash.o"
Updating archive file "/oracle/app/crs_home/lib/libnnz11.a"  with "lib/libnnz11.a/shacomm.o"
Copying file to "/oracle/app/crs_home/lib/libnnz11.so"
ApplySession adding interim patch '8670579' to inventory
Verifying the update...
Inventory check OK: Patch ID 8670579 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 8670579 are present in Oracle Home.
The local system has been patched.  You can restart Oracle instances on it.
Patching in rolling mode.
The node 'rac2' will be patched next.
Please shutdown Oracle instances running out of this ORACLE_HOME on 'rac2'.
(Oracle Home = '/oracle/app/crs_home')
Is the node ready for patching? [y|n]
n
User Responded with: N
#这里提示节点2是否已准备好,我这里选择了n,所以下面给出了错误提示 
162.  #我这里采取的是单节点patch的方法
ApplySession exits on request
You may exit the patching session and patch remaining nodes later from an un-patched node.  Do you want to continue?
Do you want to proceed? [y|n]
n
User Responded with: N
#接下来单独在第二个节点patch,之后在执行root.sh,一路高歌阿... 
 #注意patch的时候check一下ORACLE_HOME环境变量以及perl -v 查看perl的版本,应当高于5.00503 
#感觉Oracle 11g 32 bit版本问题挺多的。尽可能安装64bit测试。还有一点说明,安装oracle database后也要patch 8670579,否则dbca报错。 
另外一节点:
3、 grid@rac2[/tmp/oracle]cd/oracle/app/crs_home/OPatch
grid@rac2[/oracle/app/crs_home/OPatch] ./opatch apply /tmp/oracle/8670579
Invoking OPatch 11.1.0.6.6
Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation.  All rights reserved.
Oracle Home       : /oracle/app/crs_home
Central Inventory : /oracle/app/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.6
OUI version       : 11.2.0.1.0
OUI location      : /oracle/app/crs_home/oui
Log file location : /oracle/app/crs_home/cfgtoollogs/opatch/opatch2012-12-24_02-19-40AM.log
4、 之后执行ROOT.sh一切顺利

这篇关于BUG:Failed to create or upgrade OLR的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/913503

相关文章

android java.io.IOException: open failed: ENOENT (No such file or directory)-api23+权限受权

问题描述 在安卓上,清单明明已经受权了读写文件权限,但偏偏就是创建不了目录和文件 调用mkdirs()总是返回false. <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/><uses-permission android:name="android.permission.READ_E

UserWarning: mkl-service package failed to import

安装完成anaconda,并设置了两个环境变量  之后再控制台运行python环境,输入import numpy as np,提示错误 D:\InstallFolder\Anaconda3\lib\site-packages\numpy\__init__.py:143: UserWarning: mkl-service package failed to import, therefore

Python安装llama库出错“metadata-generation-failed”

Python安装llama库出错“metadata-generation-failed” 1. 安装llama库时出错2. 定位问题1. 去官网下载llama包 2.修改配置文件2.1 解压文件2.2 修改配置文件 3. 本地安装文件 1. 安装llama库时出错 2. 定位问题 根据查到的资料,发现时llama包中的execfile函数已经被下线了,需要我们手动修改代码后

Typora配置PicGo时,提示Failed to fetch

Typora配置PicGo时,提示Failed to fetch 两者配置的端口不一致造成的 打开Typora,选择文件-偏好设置-图像-验证图片上传选项,点击验证图片上传选项 会提示错误:Failed to fetch,此时可以发现typora中设置的上传端口为36677 打开PigGo,选择PicGo设置-设置server,会发现监听端口为36678 修改监听接口为366

Tomcat启动报错:transport error 202: bind failed: Address already in use

Tomcat启动报错:transport error 202: bind failed: Address already in use 了,上网查找了下面这篇文章。也是一种解决办法。 下文来自:http://blog.csdn.net/sam031503/article/details/7037033 tomcat 启动日志报出以下错误:  ERROR: transport err

GTK中创建线程函数g_thread_new和g_thread_create的区别

使用GThread函数,需要引用glib.h头文件。 这两个接口的核心区别就是  g_thread_create 是旧的接口,现在已经不使用了,而g_thread_new是新的接口,建议使用。 g_thread_create: g_thread_create has been deprecated since version 2.32 and should not be used in n

SpringBoot启动报错Failed to determine a suitable driver class

两种解决办法 1.在Application类上加 ` @EnableAutoConfiguration(exclude={DataSourceAutoConfiguration.class}) package com.example.demo3;import org.springframework.boot.SpringApplication;import org.springframewo

Create and manage temporary, permanent, and undo tablespaces

Create and manage temporary, permanent, and undo tablespaces 关于tablespace的操作语句有三大类,分别是create tablespace、alter tablespace、drop tablespace 表空间如标题所说,总体也分为三大类,temporary tablespace 、system/sysaux/users

Failed to pull selection解决办法

今天在使用DDMS导出文档到PC端的时候,明明在file explorer里面有文件,导出时候就是失败,出现了“Failed to pull selection”错误。百度了一下,还是重启Eclipse最靠谱。

JavaBug系列-解决SpringBoot返回Xml结构的问题

JavaBug系列之SpringBoot返回Xml结构的问题 Java医生一、关于错误信息二、如何解决问题 Java医生 本系列记录常见Bug,以及诊断过程和原因 作者:Java医生 教学: Java企业项目辅导,专注于辅导新入职员工,解决各种问题! V:study_51ctofx 一、关于错误信息 如图,SpringBoot请求返回Xml格式信息 通过以上信息分析,