在Suse 12.4上安装11.2.0.4的rac执行root.sh报错不能启动ora.oc4j资源
报错信息:
v3lhrzgd01:~ # /u01/app/11.2.0/grid/perl/bin/perl -I/u01/app/11.2.0/grid/perl/lib -I/u01/app/11.2.0/grid/crs/install /u01/app/11.2.0/grid/crs/install/rootcrs.pl
Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params
User ignored Prerequisites during installation
Installing Trace File Analyzer
PRKO-2190 : VIP exists for node v3lhrzgd01, VIP name v3lhrzgd01-vip
PRCS-1037 : Single Client Access Name VIPs already exist
PRCS-1028 : Single Client Access Name listeners already exist
OC4J could not be created as it already exists
PRCR-1086 : resource ora.oc4j is already registered
PRCR-1086 : resource ora.cvu is already registered
PRCC-1014 : scan1 was already running
PRCR-1004 : Resource ora.scan1.vip is already running
PRCR-1079 : Failed to start resource ora.scan1.vip
CRS-5702: Resource 'ora.scan1.vip' is already running on 'v3lhrzgd01'
PRCC-1014 : LISTENER_SCAN1 was already running
PRCR-1004 : Resource ora.LISTENER_SCAN1.lsnr is already running
PRCR-1079 : Failed to start resource ora.LISTENER_SCAN1.lsnr
CRS-5702: Resource 'ora.LISTENER_SCAN1.lsnr' is already running on 'v3lhrzgd01'
FirstNode configuration failed at /u01/app/11.2.0/grid/crs/install/crsconfig_lib.pm line 9379.
grid@v3lhrzgd01:~> srvctl start oc4j -v
OC4J could not be started
PRCR-1079 : Failed to start resource ora.oc4j
CRS-2674: Start of 'ora.oc4j' on 'v3lhrzgd01' failed
CRS-2632: There are no more servers to try to place resource 'ora.oc4j' on that would satisfy its placement policy
2020-05-07 14:02:44.406:
[/u01/app/11.2.0/grid/bin/scriptagent.bin(42041)]CRS-5818:Aborted command 'start' for resource 'ora.oc4j'. Details at (:CRSAGF00113:) {1:9523:1159} in /u01/app/11.2.0/grid/log/v3lhrzgd01/agent/crsd/scriptagent_grid/scriptagent_grid.log.
2020-05-07 14:02:44.408:
[crsd(26327)]CRS-2757:Command 'Start' timed out waiting for response from the resource 'ora.oc4j'. Details at (:CRSPE00111:) {1:9523:1159} in /u01/app/11.2.0/grid/log/v3lhrzgd01/crsd/crsd.log.
/u01/app/11.2.0/grid/log/v3lhrzgd01/agent/crsd/scriptagent_grid/scriptagent_grid.log
2020-05-07 14:25:36.468: [ora.oc4j][3278321408]{1:60053:233} [start] /u01/app/11.2.0/grid/bin/oc4jctl.pl: Could not fetch http://127.0.0.1:8888/
2020-05-07 14:25:37.469: [ora.oc4j][3278321408]{1:60053:233} [start] /u01/app/11.2.0/grid/bin/oc4jctl.pl: Could not fetch http://127.0.0.1:8888/
2020-05-07 14:25:38.470: [ora.oc4j][3278321408]{1:60053:233} [start] /u01/app/11.2.0/grid/bin/oc4jctl.pl: Could not fetch http://127.0.0.1:8888/
2020-05-07 14:25:39.472: [ora.oc4j][3278321408]{1:60053:233} [start] /u01/app/11.2.0/grid/bin/oc4jctl.pl: Could not fetch http://127.0.0.1:8888/
2020-05-07 14:25:40.473: [ora.oc4j][3278321408]{1:60053:233} [start] /u01/app/11.2.0/grid/bin/oc4jctl.pl: Could not fetch http://127.0.0.1:8888/
2020-05-07 14:25:41.474: [ora.oc4j][3278321408]{1:60053:233} [start] /u01/app/11.2.0/grid/bin/oc4jctl.pl: Could not fetch http://127.0.0.1:8888/
解决:
v3lhrzgd01:~ # netstat -anp | grep 8888 tcp 0 0 127.0.0.1:8888 0.0.0.0:* LISTEN 3047/python3 v3lhrzgd01:~ # netstat -anp | grep 8888 tcp 0 0 127.0.0.1:8888 0.0.0.0:* LISTEN 3047/python3 v3lhrzgd01:~ # ps -ef|grep 3047 hwdatap+ 3047 1 0 11:45 ? 00:00:00 /usr/bin/python3 /opt/huawei/dataprovider/dataprovider_linux.py > /dev/null 2>&1 root 24684 24620 0 14:37 pts/4 00:00:00 grep --color=auto 3047
看来8888端口被占用了,咨询客户,直接kill掉。kill掉后重新跑root.sh就可以了。
有关dataprovider_linux.py该脚本,搜索华为的官网,找到的信息:
Data Provider for SAP 收集关键的性能数据,例如:CPU使用率,内存使用率等,并将这些性能数据呈现给SAP应用,用于监控事务。
华为与SAP公司都认识到,SAP系统每天都在处理商业事务,对客户的商业来说非常重要。因此,SAP客户需要构建能力,以跟踪和处理这些事务性能。基于此,SAP在SAP软件中提供了扩展的事务监控能力,能够以一定的逻辑,稳定的形式,来呈现SAP支持的许多操作系统和数据库的相关性能信息。为提供这些指标,我们开发了 Data Provider for SAP。
https://support.huaweicloud.com/dpug-sap/sap_01_0002.html
图1展示了在云服务器上的Data Provider for SAP运行的整体框架。
说明如下:
- Data Provider for SAP收集关键的性能数据,包括操作系统、网络、存储方面与SAP架构相关的指标,并将其呈现给SAP应用,用于监控事务。为了保证能够从各个方面对操作环境的性能进行分析,性能数据从各类的资源中收集而来,包括ECS的API、ECS实例的元属性,以及CES。
- SAP操作系统控制器(SAPOSCOL,SAP Operating System Collector)和SAP CIM Provider是从Data Provider for SAP获取数据的SAP组件。
https://support.huaweicloud.com/dpug-sap/sap_01_0010.html
卸载Data Provider(Linux)
本节指导在Linux上 卸载Data Provider。
操作步骤
- 登录到已安装 Data Provider的服务器。
-
执行以下命令,
卸载Data Provider。
rpm -evh dataprovider
-
检查
卸载结果。
执行以下命令,检查进程。
ps -ef | grep python | grep dataprovider
执行完后,将不会看到Data Provider的进程。
在Linux上如何停止Data Provider
日常管理操作中,需要停止 Data Provider。
操作步骤
- 以 “root”帐号,通过密钥或密码的方式,登录到服务器,并进入命令行界面。
-
执行以下命令,在云服务器上
停止Data Provider。
systemctl stop hwdataproviderp3
-
执行以下命令,检查进程。
ps -ef | grep python | grep dataprovider
执行完后,将不会看到Data Provider的进程。
题外: 看起来解决很简单,可是这里我花了大概2小时的时间来排错。
About Me
|
........................................................................................................................ ● 本文作者:小麦苗,部分内容整理自网络,若有侵权请联系小麦苗删除 ● 本文在itpub、博客园、CSDN和个人微 信公众号( DB宝)上有同步更新 ● 本文itpub地址: http://blog.itpub.net/26736162 ● 本文博客园地址: http://www.cnblogs.com/lhrbest ● 本文CSDN地址: https://blog.csdn.net/lihuarongaini ● 本文pdf版、个人简介及小麦苗云盘地址: http://blog.itpub.net/26736162/viewspace-1624453/ ● 数据库笔试面试题库及解答: http://blog.itpub.net/26736162/viewspace-2134706/ ● DBA宝典今日头条号地址: http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826 ........................................................................................................................ ● QQ群号: 230161599 、618766405 ● 微 信群:可加我微 信,我拉大家进群,非诚勿扰 ● 联系我请加QQ好友 ( 646634621 ),注明添加缘由 ● 于 2020-05-01 06:00 ~ 2020-05-30 24:00 在西安完成 ● 最新修改时间:2020-05-01 06:00 ~ 2020-05-30 24:00 ● 文章内容来源于小麦苗的学习笔记,部分整理自网络,若有侵权或不当之处还请谅解 ● 版权所有,欢迎分享本文,转载请保留出处 ........................................................................................................................ ● 小麦苗的微店: https://weidian.com/s/793741433?wfr=c&ifr=shopdetail ● 小麦苗出版的数据库类丛书: http://blog.itpub.net/26736162/viewspace-2142121/ ● 小麦苗OCP、OCM、高可用网络班: http://blog.itpub.net/26736162/viewspace-2148098/ ● 小麦苗腾讯课堂主页: https://lhr.ke.qq.com/ ........................................................................................................................ 使用 微 信客户端扫描下面的二维码来关注小麦苗的微 信公众号( DB宝)及QQ群(DBA宝典)、添加小麦苗微 信, 学习最实用的数据库技术。
........................................................................................................................ |
![]() |
|


