oracle rac 12.2 执行root.sh报CLSRSC-400_johnyiyang的博客-程序员秘密

技术标签： oracle

今天在rhel7.6安装oracle 12.2 rac的时候，遇到以下报错

CLSRSC-400: A system reboot is required to continue installing.

主要原因由于12c gi开始，acfs默认是安装的，由于acfs在redhat 7.6中不支持导致上述的错误信息.
处理方案一：
大神惜纷飞提供了一种解决方案如链接：
http://www.xifenfei.com/2017/06/rac-12-2-root-sh-clsrsc-400.html

主要报错信息：
2017/06/11 09:55:15 CLSRSC-400: A system reboot is required to continue installing.
The command ‘/u01/app/grid/product/12.2.0/grid/perl/bin/perl -I/u01/app/grid/product/12.2.0/grid/perl/lib -I/u01/app/grid/product/12.2.0/grid/crs/install /u01/app/grid/product/12.2.0/grid/crs/install/rootcrs.pl ‘ execution failed
查询mos发下:ACFS Drivers Install reports CLSRSC-400: A system reboot is required to continue installing (Doc ID 2025056.1),主要是由于12c gi开始，acfs默认是安装的，由于acfs在redhat 7.3中不支持导致上述的错误信息.
[grid@xifenfei01 ~]$ acfsdriverstate -orahome $ORACLE_HOME supported
ACFS-9459: ADVM/ACFS is not supported on this OS version: '3.10.0-514.el7.x86_64'
ACFS-9201: Not Supported

处理方法
停掉crs,kill 进程(如果有不能停掉的，通过kill处理),执行root.sh
[root@xifenfei01 ~]# /u01/app/grid/product/12.2.0/grid/bin/crsctl stop crs -f
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'xifenfei01'
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'xifenfei02' has completed
CRS-4133: Oracle High Availability Services has been stopped.
[root@xifenfei02 ~]# ps -ef|grep d.bin
root      29155  11754  0 10:46 pts/0    00:00:00 grep --color=auto d.bin
 
[root@xifenfei01 ~]# /u01/app/grid/product/12.2.0/grid/root.sh
Performing root user operation.

处理方案二
通过查找文档，发现这是一个oracle acfs bug

ACFS Support On OS Platforms (Certification Matrix). (Doc ID 1369107.1)
ALERT: root.sh Fails With “CLSRSC-400” While Installing GI 12.2.0.1 on RHEL or OL with RedHat
Compatible Kernel (RHCK) 7.3 (Doc ID 2284463.1)

在这里插入图片描述具体psu、spu、bundle patch、ru、rur 的信息请查看mos文档
这是一个oneoff补丁

12.2.0.1及以上版本gridSetup.sh可以直接进行补丁操作
覆盖最新的OPatch工具
unzip p6880880_122010_Linux-x86-64.zip -d $GI_HOME

To apply only Release Updates:
$GI_HOME/gridSetup.sh -applyPSU patch location
To apply only Non-RU patches:
$GI_HOME/gridSetup.sh -applyOneOffs patch location
To apply Release Updates and Non-RU patches in one command:
$GI_HOME/gridSetup.sh -applyPSU patch location -applyOneOffs patch location

1.先解压最新的OPatch工具

 unzip p6880880_12.2.0.1.13_Linux-x86-64.zip  -d  \$ORACLE_HOME

2.安装补丁

 [grid@jla-rac1 grid]$ ./gridSetup.sh -applyOneOffs /data/RU/26247490/26247490/
Preparing the home to patch...
Applying the patch /data/RU/26247490/26247490/...
Successfully applied the patch.
The log can be found at: /opt/u01/app/oraInventory/logs/GridSetupActions2019-11-06_10-48-01AM/installerPatchActions_2019-11-06_10-48-01AM.log
Launching Oracle Grid Infrastructure Setup Wizard...

You can find the log of this install session at:
 /opt/u01/app/oraInventory/logs/GridSetupActions2019-11-06_10-48-01AM /gridSetupActions2019-11-06_10-48-01AM.log

3.执行root.sh无报错

[root@jla-rac1 data]# /opt/u01/12.2.0/grid/root.sh
Performing root user operation.

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /opt/u01/12.2.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]: 
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.


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 script.
Now product-specific root actions will be performed.
Relinking oracle with rac_on option
Using configuration parameter file: /opt/u01/12.2.0/grid/crs/install/crsconfig_params
The log of current session can be found at:
  /opt/u01/app/grid/crsdata/jla-rac1/crsconfig/rootcrs_jla-rac1_2019-11-06_11-08-43AM.log
2019/11/06 11:08:54 CLSRSC-594: Executing installation step 1 of 19: 'SetupTFA'.
2019/11/06 11:08:54 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.
2019/11/06 11:09:16 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.
2019/11/06 11:09:16 CLSRSC-594: Executing installation step 2 of 19: 'ValidateEnv'.
2019/11/06 11:09:20 CLSRSC-363: User ignored prerequisites during installation
2019/11/06 11:09:20 CLSRSC-594: Executing installation step 3 of 19: 'CheckFirstNode'.
2019/11/06 11:09:22 CLSRSC-594: Executing installation step 4 of 19: 'GenSiteGUIDs'.
2019/11/06 11:09:23 CLSRSC-594: Executing installation step 5 of 19: 'SaveParamFile'.
2019/11/06 11:09:27 CLSRSC-594: Executing installation step 6 of 19: 'SetupOSD'.
2019/11/06 11:09:41 CLSRSC-594: Executing installation step 7 of 19: 'CheckCRSConfig'.
2019/11/06 11:09:41 CLSRSC-594: Executing installation step 8 of 19: 'SetupLocalGPNP'.
2019/11/06 11:09:55 CLSRSC-594: Executing installation step 9 of 19: 'ConfigOLR'.
2019/11/06 11:10:02 CLSRSC-594: Executing installation step 10 of 19: 'ConfigCHMOS'.
2019/11/06 11:10:02 CLSRSC-594: Executing installation step 11 of 19: 'CreateOHASD'.
2019/11/06 11:10:06 CLSRSC-594: Executing installation step 12 of 19: 'ConfigOHASD'.
2019/11/06 11:10:21 CLSRSC-330: Adding Clusterware entries to file 'oracle-ohasd.service'
2019/11/06 11:11:08 CLSRSC-594: Executing installation step 13 of 19: 'InstallAFD'.
2019/11/06 11:11:56 CLSRSC-594: Executing installation step 14 of 19: 'InstallACFS'.
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'jla-rac1'
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'jla-rac1' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
2019/11/06 11:12:45 CLSRSC-594: Executing installation step 15 of 19: 'InstallKA'.
2019/11/06 11:12:48 CLSRSC-594: Executing installation step 16 of 19: 'InitConfig'.
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'jla-rac1'
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'jla-rac1' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
CRS-2672: Attempting to start 'ora.driver.afd' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.evmd' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.mdnsd' on 'jla-rac1'
CRS-2676: Start of 'ora.driver.afd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'jla-rac1'
CRS-2676: Start of 'ora.cssdmonitor' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.mdnsd' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.evmd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'jla-rac1'
CRS-2676: Start of 'ora.gpnpd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'jla-rac1'
CRS-2676: Start of 'ora.gipcd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.diskmon' on 'jla-rac1'
CRS-2676: Start of 'ora.diskmon' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.cssd' on 'jla-rac1' succeeded

Disk label(s) created successfully. Check /opt/u01/app/grid/cfgtoollogs/asmca/asmca-191106AM111334.log for details.
Disk groups created successfully. Check /opt/u01/app/grid/cfgtoollogs/asmca/asmca-191106AM111334.log for details.


2019/11/06 11:14:55 CLSRSC-482: Running command: '/opt/u01/12.2.0/grid/bin/ocrconfig -upgrade grid oinstall'
CRS-2672: Attempting to start 'ora.crf' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.storage' on 'jla-rac1'
CRS-2676: Start of 'ora.storage' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.crf' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'jla-rac1'
CRS-2676: Start of 'ora.crsd' on 'jla-rac1' succeeded
CRS-4256: Updating the profile
Successful addition of voting disk 319d6dcea3534fc0bf244abd1bfc2a94.
Successfully replaced voting disk group with +VGJLRAC01.
CRS-4256: Updating the profile
CRS-4266: Voting file(s) successfully replaced
\##  STATE    File Universal Id                File Name Disk group
\--  -----    -----------------                --------- ---------
\1. ONLINE   319d6dcea3534fc0bf244abd1bfc2a94 (AFD:VGJLRAC011) [VGJLRAC01]
Located 1 voting disk(s).
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.crsd' on 'jla-rac1'
CRS-2677: Stop of 'ora.crsd' on 'jla-rac1' succeeded
CRS-2673: Attempting to stop 'ora.storage' on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.crf' on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.gpnpd' on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.mdnsd' on 'jla-rac1'
CRS-2677: Stop of 'ora.drivers.acfs' on 'jla-rac1' succeeded
CRS-2677: Stop of 'ora.crf' on 'jla-rac1' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'jla-rac1' succeeded
CRS-2677: Stop of 'ora.storage' on 'jla-rac1' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'jla-rac1'
CRS-2677: Stop of 'ora.mdnsd' on 'jla-rac1' succeeded
CRS-2677: Stop of 'ora.asm' on 'jla-rac1' succeeded
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'jla-rac1'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'jla-rac1' succeeded
CRS-2673: Attempting to stop 'ora.ctssd' on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.evmd' on 'jla-rac1'
CRS-2677: Stop of 'ora.ctssd' on 'jla-rac1' succeeded
CRS-2677: Stop of 'ora.evmd' on 'jla-rac1' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'jla-rac1'
CRS-2677: Stop of 'ora.cssd' on 'jla-rac1' succeeded
CRS-2673: Attempting to stop 'ora.driver.afd' on 'jla-rac1'
CRS-2673: Attempting to stop 'ora.gipcd' on 'jla-rac1'
CRS-2677: Stop of 'ora.driver.afd' on 'jla-rac1' succeeded
CRS-2677: Stop of 'ora.gipcd' on 'jla-rac1' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'jla-rac1' has completed
CRS-4133: Oracle High Availability Services has been stopped.
2019/11/06 11:16:12 CLSRSC-594: Executing installation step 17 of 19: 'StartCluster'.
CRS-4123: Starting Oracle High Availability Services-managed resources
CRS-2672: Attempting to start 'ora.mdnsd' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.evmd' on 'jla-rac1'
CRS-2676: Start of 'ora.mdnsd' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.evmd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'jla-rac1'
CRS-2676: Start of 'ora.gpnpd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.gipcd' on 'jla-rac1'
CRS-2676: Start of 'ora.gipcd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'jla-rac1'
CRS-2676: Start of 'ora.cssdmonitor' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.diskmon' on 'jla-rac1'
CRS-2676: Start of 'ora.diskmon' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.cssd' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.cluster_interconnect.haip' on 'jla-rac1'
CRS-2672: Attempting to start 'ora.ctssd' on 'jla-rac1'
CRS-2676: Start of 'ora.ctssd' on 'jla-rac1' succeeded
CRS-2676: Start of 'ora.cluster_interconnect.haip' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'jla-rac1'
CRS-2676: Start of 'ora.asm' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.storage' on 'jla-rac1'
CRS-2676: Start of 'ora.storage' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.crf' on 'jla-rac1'
CRS-2676: Start of 'ora.crf' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.crsd' on 'jla-rac1'
CRS-2676: Start of 'ora.crsd' on 'jla-rac1' succeeded
CRS-6023: Starting Oracle Cluster Ready Services-managed resources
CRS-6017: Processing resource auto-start for servers: jla-rac1
CRS-6016: Resource auto-start has completed for server jla-rac1
CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources
CRS-4123: Oracle High Availability Services has been started.
2019/11/06 11:18:03 CLSRSC-343: Successfully started Oracle Clusterware stack
2019/11/06 11:18:03 CLSRSC-594: Executing installation step 18 of 19: 'ConfigNode'.
CRS-2672: Attempting to start 'ora.ASMNET1LSNR_ASM.lsnr' on 'jla-rac1'
CRS-2676: Start of 'ora.ASMNET1LSNR_ASM.lsnr' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.asm' on 'jla-rac1'
CRS-2676: Start of 'ora.asm' on 'jla-rac1' succeeded
CRS-2672: Attempting to start 'ora.VGJLRAC01.dg' on 'jla-rac1'
CRS-2676: Start of 'ora.VGJLRAC01.dg' on 'jla-rac1' succeeded
2019/11/06 11:19:34 CLSRSC-594: Executing installation step 19 of 19: 'PostConfig'.
2019/11/06 11:20:43 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded

本文链接：https://blog.csdn.net/johnyiyang/article/details/103006627

原作者删帖不实内容删帖广告或垃圾文章投诉

智能推荐

kaililinux实现下wifi密码破解（wpa/wpa2）_huihui985211的博客-程序员秘密

1.排除相关干扰并结束线程[email protected]:~# service network-manager stop [email protected]:~# airmon-ng check kill2.启动网卡的监听模式[email protected]:~# airmon-ng start wlan03.确定启动监听[email protected]:~# iwconfig4.显示监听的wifi相关信息，ctrl+c停止[email protected]:~# a...

Hibernate4实战之Hibernate4注解零配置<转>_weixin_30843605的博客-程序员秘密

@Entity，注册在类头上，将一个类声明为一个实体bean(即一个持久化POJO类) 。@Table，注册在类头上，注解声明了该实体bean映射指定的表（table）。@Id用来注册主属性，@GeneratedValue用来注册主属性的生成策略，@Column用来注册属性，@Version用来注册乐观锁，@Transient用来注册不是属性。以上的@Id、@Generated...

数据库中数据长度到底代表什么呢？_莲绛(君卿舞)的博客-程序员秘密

即使已经参加工作快满一年了，但是却连数据库里面数据的长度都一直没搞清楚到底代表什么意思。类型是指数据存储类型，这个大家都知道，比如int类型代表4字节（Byte),1字节=8bit,即1B=8b.子节是计算机文件大小的基本计算单位，主要用于应用层，用于客户来识别文件大小的。而bit是用于物理层，数据链路层的传输的，是基于二进制的传输。所以这里int类型可以存储4*8=32位。可以存储十进制-...

jdk1.7创建最简单的SpringBoot_大音~希声的博客-程序员秘密

1、idea任意创建一个maven项目2、pom.xml<?xml version="1.0" encoding="UTF-8"?><project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ...

softmax_cross_entropy_with_logits_v2 计算的是什么玩意？_brooknew的博客-程序员秘密

Tensorflow 里通过softmax后再计算交叉熵有2个函数：1 softmax_cross_entropy_with_logits_v22 sparse_softmax_cross_entropy_with_logits均涉及两个参数，logits 和 labels ，logits 一般是神经网络的输出，是一个batch乘待分类类型数的二维张量。而labels是已知的标注，同样sh...

stopwatch计时器统计程序耗时_stopwatch.elapsed_贫僧洗发水呢的博客-程序员秘密

stopwatch计时器统计程序耗时一、使用Google Stopwatch1、引入依赖：import com.google.common.base.Stopwatch;2、基础用法：Stopwatch stopwatch = Stopwatch.createStarted(); //创建计时器并开始计时doSomething();log.info("doSomething 耗时: "+ stopwatch.toString()); //stopwatch.toString()会自动选用合适的时