Operating System - HP-UX
1832095 Members
3174 Online
110038 Solutions
New Discussion

EMS /rdbms not avilable error

 
SOLVED
Go to solution
jayachandran.g
Regular Advisor

EMS /rdbms not avilable error

Hi All

When I tried to add a monitoring request to EMS in GUI it is giving error
"Resource /rdbms not available"

I want to add monitoring requests only to LAN card not to any oracle then too I’m getting this error.

In the web I found that this error would appear when the database is not running

"Monitor the resource for changes only. Since the value represents the time an application server was started, a change to this value is a valid indication that the server was restarted."

Where or how to check the above process are running or not...


#ps -af | grep -i ems is giving the output
" root 1113 1 0 Mar 7 ? 0:00 /etc/opt/resmon/lbin/emsagent"


It seems that I'm in the middle of the sea
and as far I see I found no light house... to call me ....

help me... !!!!!!!
19 REPLIES 19
Robert-Jan Goossens
Honored Contributor
Solution

Re: EMS /rdbms not avilable error

Hi,

Could you post your HPUX version ?

Is snmpdm running ?

# ps -ef | grep snmp
root 1327 1 0 Oct 14 ? 0:00 /usr/sbin/snmpdm
root 279 24547 0 10:12:22 pts/ta 0:00 grep snmp

Regards,
Robert-Jan
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi Robert

My HPUX version is

HP-UX B.11.00 U 9000/800 139454651

SNMP output

root 940 1 0 Mar 7 ? 0:55 /usr/sbin/snmpdm
root 975 1 0 Mar 7 ? 0:00 /usr/lbin/cmsnmpd

Here is something that I have understood/observed

Iâ m opening my EMS and adding a monitor request, EMS is connecting to "resource class" (may be this is considred as database) Which is having tree like architecture that it can monitor like
/net --> /interfaces --> /lan --> /status
-->lan Name.


The problem is connection to resource class is failing it seems. This is what I have understood from the docs... may be wrong....
Robert-Jan Goossens
Honored Contributor

Re: EMS /rdbms not avilable error

could you check if patch PHSS_27858 is installed ?

# swlist -l patch | grep PHSS_27858

Robert-Jan
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi Robert

swlist -l patch | grep PHSS_27858

PHSS_27858 Patch is not installed.

Robert-Jan Goossens
Honored Contributor

Re: EMS /rdbms not avilable error

Hi,

Just for my curiosity, are you monitoring a database with ems ?

Try to use the command interface.

# /etc/opt/resmon/lbin/monconfig

Regards,
Robert-Jan
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi Robert-Jan

I'm not sure on enablening the monior to lan cards using monconfig. Because the outout of config server

One thing that is found is in the all the monitor demons are not up and running.

only 7 or 9 is upand running. even registar demon is down.

jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi Robert-Jan

I'm not sure on enablening the monior to lan cards using monconfig. I'm working on it.

One thing that is found is that all the monitor demons are not up and running.

only 7 or 9 is upand running. even registar demon is down.



RAC_1
Honored Contributor

Re: EMS /rdbms not avilable error

Restart EMS and try.

/sbin/init.d/diagnostics stop
/sbin/init.d/diagnostics start
There is no substitute to HARDWORK
Andrew Merritt_2
Honored Contributor

Re: EMS /rdbms not avilable error

Don't get confused between the Event Monitoring Service, which is what you are configuring through the SAM gui under Resource Management, and the EMS Hardware Monitors, which is what monconfig lists.

What does 'emscli -l' show?

If you already have requests to monitor an Oracle db, but it's not running, that would explain what you are seeing.

What version of EMS are you running? "swlist -l product|grep EMS-Core" will show this.

Andrew
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi Rober-Jan/ RCA


When I start the diagonistic not all my monitor demons are not running. It is starting and getting killed in few seconds.....



jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi All

I'm talking about "Event Monitoring System"
which is accessed through SAM --> Resource Management --> Event monitoring System.

EMS core version is A.03.20.
emscli -l "cmd not found"

Andrew Merritt_2
Honored Contributor

Re: EMS /rdbms not avilable error

Ah, emscli is new with the A.04.00 version of EMS, which is for 11.11 and later. Sorry, I forgot that.

Restarting the diagnostics will have no effect on what you are trying to do, though I'm curious as to what you mean about monitor demons dying.

When you open the "Event Monitoring System" window, are there any existing requests shown? If so, what are they?

Andrew
Robert-Jan Goossens
Honored Contributor

Re: EMS /rdbms not avilable error

Hi,

Could you check the registrar log file.

# tail /etc/opt/resmon/log/registrar.log

Regards,
Robert-Jan
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Hi Andrew/Rober-Jan

Check the outputs

HPSVR:root> resls /net/interfaces/lan/status
Contacting Registrar on HPSVR

NAME: /net/interfaces/lan/status
DESCRIPTION: None
TYPE: /net/interfaces/lan/status is not a valid resource name

and in registar.log
-------------------Start Event---------------
Event 1447 occurred at Wed Mar 29 17:55:01.720369 2006
Process ID: 13181 (/etc/opt/resmon/lbin/registrar) Log Level: Error
send_error_reply: Cannot send error reply to the client:
error code = 15: An error occurred while attempting to send a message: Broken pipe
-------------------End Event-----------------


Hrere are teh process that are running
-------------------Start Event---------------
Event 1447 occurred at Wed Mar 29 17:55:01.720369 2006
Process ID: 13181 (/etc/opt/resmon/lbin/registrar) Log Level: Error
send_error_reply: Cannot send error reply to the client:
error code = 15: An error occurred while attempting to send a message: Broken pipe
-------------------End Event-----------------

and abouth the monitoring demons

Thes are my demons rnning iw wqorking server ...


HP:root> ps -eaf | grep -i /opt/resmon
root 1355 1 0 Feb 6 ? 2:11 /etc/opt/resmon/lbin/pkgmond
root 1156 1 0 Feb 6 ? 9:06 /etc/opt/resmon/lbin/p_client
root 11411 6953 0 Mar 28 ? 0:00 /etc/opt/resmon/lbin/registrar
root 1184 1 0 Feb 6 ? 0:37 /etc/opt/resmon/lbin/clustermon
root 12534 1 0 Mar 28 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 13417 1 0 Mar 28 ? 0:41 /etc/opt/resmon/lbin/lanmond

but these demons are not working running in the server which is haveing problem.....

HPSVR1:root>ps -eaf | grep -i /opt/resmon
root 1156 1 0 Feb 6 ? 9:06 /etc/opt/resmon/lbin/p_client
root 1355 1 0 Feb 6 ? 2:11 /etc/opt/resmon/lbin/registrar





Robert-Jan Goossens
Honored Contributor

Re: EMS /rdbms not avilable error

Could you post the output of

# swlist -l product | grep EMS
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

HI

here is the output

EMS-Config A.03.20 EMS Config
EMS-Core A.03.20 EMS Core Product
EMS-DiskMonitor A.03.20 EMS Disk Resource Monitor
EMS-KRMonitor A.11.00.04 EMS Kernel Resource Monitor
EMS-MIBMonitor A.03.20 EMS MIB Resource Monitor Product
EMS-RdbmsMon A.03.20 EMS Database Monitor
PHCO_16280 1.0 du(1) value for non-HP NFS systems incorr
ect
PHCO_17867 1.0 ioinitrc, assign ttys for B,C class syste
ms
PHCO_18901 1.0 extendfs_hfs fix for large file systems
PHKL_22771 1.0 fix device and file system swap problems
PHKL_24905 1.0 VxFS mount/unmount problems.
PHSS_26871 1.0 EMS (A.03.20) & HA Monitors (A.03.20) pat
ch
Sup-Tool-Mgr B.11.00.26.07 Support Tools Manager for HPUX systems
Robert-Jan Goossens
Honored Contributor

Re: EMS /rdbms not avilable error

# swlist -a state -l fileset | grep EMS

all configured ?

if you have lsof installed check if tcp port 1712 is in use ?

Robert-Jan
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

Yes It was checked already and found that the port was in use...

When I stoppe all the process it was in Time_Wait status...
jayachandran.g
Regular Advisor

Re: EMS /rdbms not avilable error

In some cases I have found that once we edit the snmpd.conf after installing the EMS.. then we may require to reinstall the EMS is it true..