Google it ....

Showing posts with label Oracle Exadata. Show all posts
Showing posts with label Oracle Exadata. Show all posts

Tuesday, February 22, 2022

Exadata CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: 8888

 Today we faced below problem while trying to connect cellcli on Exadata Storage Cell

"CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: 8888"
[root@testcel01 ~]# cellcli -e list physicaldisk detail

CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: 8888.
[root@testcel01 ~]#
Cell server is not running actually and we need to solve this problem.
To solve this problem, you need to start cell daemon:
[root@testcel01 ~]# service celld start
1: ERROR: Resource temporarily unavailable
rds-ping failed on 192.168.10.27
1: ERROR: Resource temporarily unavailable
rds-ping failed on 192.168.23.16
1: 90 usec
1: 134 usec

Starting the RS, CELLSRV, and MS services...
Getting the state of RS services... running
Starting CELLSRV services...
The STARTUP of CELLSRV services was successful.
Starting MS services...
The STARTUP of MS services was successful.
[root@testcel01 ~]# 
[root@testcel01 ~]#
Cell server daemon was started successful. You can check its status:
[root@testcel01 ~]# service celld status
rsStatus: running
msStatus: running
cellsrvStatus: running
[root@testcel01 ~]#

Friday, February 9, 2018

12C Database reports KFOD Error During Oracle Exadata Database Machine Discovery in OEM: "DiscoveryWarning: kfod returns status 126"

During Oracle Exadata Database Machine Discovery in Oracle Enterprise Manager (OEM) appears error:
The following errors are found during discovery. 
Please examine the error messages and the targets being discovered if any. 
DiscoveryWarning: kfod returns status 126. 
Please check the OSSCONF environment variable and make sure that 
cellinit.ora and cellip.ora are readable by the EM agent. 
DiscoveryWarning: /u01/app/oracle/product/12.2.0.1/dbhome_1/bin/kfod: line 22: 
/u01/agent12c/agent12c/sysman/emd/%ORACLE_HOME%/bin/kfod.bin: No such file or directory 
/u01/app/oracle/product/12.2.0.1/dbhome_1/bin/kfod: line 22: 
exec: /u01/agent12c/agent12c/sysman/emd/%ORACLE_HOME%/bin/kfod.bin: 
cannot execute: No such file or directory
cause:This is a known bug in the kfod wrapper script: Unpublished BUG 19682778 - 121021GIPSU: KFOD FILE IN RAC HOME NOT CORRECT AFTER APPLYING GIPSU
Workaround:
- Change the first line in the kfod wrapper script "$OHOME/bin/kfod.bin"
       OHOME=%ORACLE_HOME%
       to
       OHOME=<DB_Home>      Eg. OHOME=/u01/app/oracle/product/12.2.0.1/dbhome_1

Your kfod file must look like this:
cd $ORACLE_HOME
pwd
/u01/app/oracle/product/12.2.0.1/dbhome_1
cd bin/

cat kfod

#!/bin/sh
#
# $Header: opsm/utl/kfod.sbs
#
# kfod
#
# Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.
#
#    NAME
#      kfod - KFOD utility
#
#    DESCRIPTION
#      This is a script which is a wrapper on top of kfod.bin
#      This script is only shipped to the DATABASE home
#
#    MODIFIED   (MM/DD/YY)
#        samjo   05/21/14 - Creation
OHOME=/u01/app/oracle/product/12.2.0.1/dbhome_1
ORACLE_HOME=${OHOME}
export ORACLE_HOME

exec $OHOME/bin/kfod.bin "$@"