<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EMS /rdbms not avilable error in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759210#M258996</link>
    <description>could you check if patch PHSS_27858 is installed ?&lt;BR /&gt;&lt;BR /&gt;# swlist -l patch | grep PHSS_27858&lt;BR /&gt;&lt;BR /&gt;Robert-Jan</description>
    <pubDate>Mon, 27 Mar 2006 06:20:38 GMT</pubDate>
    <dc:creator>Robert-Jan Goossens</dc:creator>
    <dc:date>2006-03-27T06:20:38Z</dc:date>
    <item>
      <title>EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759207#M258993</link>
      <description>Hi All&lt;BR /&gt;&lt;BR /&gt;   When I tried to add a monitoring request to EMS in GUI it is giving error &lt;BR /&gt;"Resource /rdbms not available"&lt;BR /&gt;&lt;BR /&gt; I want to add monitoring requests only to LAN card not to any oracle then too I’m getting this error.&lt;BR /&gt;&lt;BR /&gt;   In the web I found that this error would appear when the database is not running &lt;BR /&gt;&lt;BR /&gt;"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."&lt;BR /&gt;&lt;BR /&gt;    Where or how to check the above process are running or not... &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;#ps -af | grep -i ems is giving the output&lt;BR /&gt;"    root  1113     1  0  Mar  7  ?       0:00 /etc/opt/resmon/lbin/emsagent"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It seems that I'm in the middle of the sea&lt;BR /&gt; and as far I see I found no light house... to call me ....&lt;BR /&gt;&lt;BR /&gt; help me... !!!!!!!&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Mar 2006 02:45:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759207#M258993</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-27T02:45:37Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759208#M258994</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Could you post your HPUX version ?&lt;BR /&gt;&lt;BR /&gt;Is snmpdm running ?&lt;BR /&gt;&lt;BR /&gt;# ps -ef | grep snmp     &lt;BR /&gt;root  1327     1  0  Oct 14  ?         0:00 /usr/sbin/snmpdm&lt;BR /&gt;root   279 24547  0 10:12:22 pts/ta    0:00 grep snmp&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Mon, 27 Mar 2006 03:14:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759208#M258994</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-27T03:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759209#M258995</link>
      <description>Hi Robert&lt;BR /&gt;&lt;BR /&gt;   My HPUX version is &lt;BR /&gt;&lt;BR /&gt;HP-UX B.11.00 U 9000/800 139454651 &lt;BR /&gt;&lt;BR /&gt;    SNMP output&lt;BR /&gt;&lt;BR /&gt;    root   940     1  0  Mar  7  ?         0:55 /usr/sbin/snmpdm&lt;BR /&gt;    root   975     1  0  Mar  7  ?         0:00 /usr/lbin/cmsnmpd&lt;BR /&gt;&lt;BR /&gt; Here is something that I have understood/observed&lt;BR /&gt;&lt;BR /&gt;  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 &lt;BR /&gt;/net --&amp;gt; /interfaces --&amp;gt; /lan --&amp;gt; /status &lt;BR /&gt;--&amp;gt;lan Name.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;   The problem is connection to resource class is failing it seems. This is what I have understood from the docs... may be wrong....&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Mar 2006 05:13:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759209#M258995</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-27T05:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759210#M258996</link>
      <description>could you check if patch PHSS_27858 is installed ?&lt;BR /&gt;&lt;BR /&gt;# swlist -l patch | grep PHSS_27858&lt;BR /&gt;&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Mon, 27 Mar 2006 06:20:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759210#M258996</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-27T06:20:38Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759211#M258997</link>
      <description>Hi Robert&lt;BR /&gt;&lt;BR /&gt;   swlist -l patch | grep PHSS_27858&lt;BR /&gt;&lt;BR /&gt; PHSS_27858 Patch is not installed.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Mar 2006 09:33:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759211#M258997</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-27T09:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759212#M258998</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Just for my curiosity, are you monitoring a database with ems ?&lt;BR /&gt;&lt;BR /&gt;Try to use the command interface.&lt;BR /&gt;&lt;BR /&gt;# /etc/opt/resmon/lbin/monconfig&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Mon, 27 Mar 2006 09:57:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759212#M258998</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-27T09:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759213#M258999</link>
      <description>Hi Robert-Jan&lt;BR /&gt;&lt;BR /&gt;    I'm not sure on enablening the monior to lan cards using monconfig. Because the outout of config server  &lt;BR /&gt;&lt;BR /&gt;     One thing that is found is in the all the monitor demons are not up and running.&lt;BR /&gt;&lt;BR /&gt;   only 7 or 9 is upand running. even registar demon is down.&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Tue, 28 Mar 2006 03:05:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759213#M258999</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-28T03:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759214#M259000</link>
      <description>Hi Robert-Jan&lt;BR /&gt;&lt;BR /&gt;    I'm not sure on enablening the monior to lan cards using monconfig. I'm working on it.&lt;BR /&gt;&lt;BR /&gt;     One thing that is found is that all the monitor demons are not up and running.&lt;BR /&gt;&lt;BR /&gt;   only 7 or 9 is upand running. even registar demon is down.&lt;BR /&gt;&lt;BR /&gt;  &lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Tue, 28 Mar 2006 03:06:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759214#M259000</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-28T03:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759215#M259001</link>
      <description>Restart EMS and try.&lt;BR /&gt;&lt;BR /&gt;/sbin/init.d/diagnostics stop&lt;BR /&gt;/sbin/init.d/diagnostics start</description>
      <pubDate>Tue, 28 Mar 2006 03:08:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759215#M259001</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2006-03-28T03:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759216#M259002</link>
      <description>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.&lt;BR /&gt;&lt;BR /&gt;What does 'emscli -l' show?&lt;BR /&gt;&lt;BR /&gt;If you already have requests to monitor an Oracle db, but it's not running, that would explain what you are seeing.&lt;BR /&gt;&lt;BR /&gt;What version of EMS are you running?  "swlist -l product|grep EMS-Core" will show this.&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Tue, 28 Mar 2006 05:10:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759216#M259002</guid>
      <dc:creator>Andrew Merritt_2</dc:creator>
      <dc:date>2006-03-28T05:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759217#M259003</link>
      <description>Hi Rober-Jan/ RCA &lt;BR /&gt;&lt;BR /&gt;       &lt;BR /&gt;   When I start the diagonistic not all my monitor demons are not running. It is starting and getting killed in few seconds.....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Mar 2006 05:30:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759217#M259003</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-28T05:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759218#M259004</link>
      <description>Hi All&lt;BR /&gt;&lt;BR /&gt; I'm talking about "Event Monitoring System"&lt;BR /&gt;which is accessed through SAM --&amp;gt; Resource Management --&amp;gt; Event monitoring System.&lt;BR /&gt;&lt;BR /&gt;EMS core version is A.03.20.&lt;BR /&gt;emscli -l "cmd not found"&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Mar 2006 10:22:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759218#M259004</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-28T10:22:29Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759219#M259005</link>
      <description>Ah, emscli is new with the A.04.00 version of EMS, which is for 11.11 and later.  Sorry, I forgot that.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;When you open the "Event Monitoring System" window, are there any existing requests shown?  If so, what are they?&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Thu, 30 Mar 2006 04:50:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759219#M259005</guid>
      <dc:creator>Andrew Merritt_2</dc:creator>
      <dc:date>2006-03-30T04:50:06Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759220#M259006</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Could you check the registrar log file.&lt;BR /&gt;&lt;BR /&gt;# tail /etc/opt/resmon/log/registrar.log&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Thu, 30 Mar 2006 04:56:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759220#M259006</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-30T04:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759221#M259007</link>
      <description>Hi Andrew/Rober-Jan&lt;BR /&gt;&lt;BR /&gt;Check the outputs&lt;BR /&gt;&lt;BR /&gt;HPSVR:root&amp;gt; resls /net/interfaces/lan/status&lt;BR /&gt;Contacting Registrar on HPSVR&lt;BR /&gt;&lt;BR /&gt;NAME: /net/interfaces/lan/status&lt;BR /&gt;DESCRIPTION: None&lt;BR /&gt;TYPE: /net/interfaces/lan/status is not a valid resource name&lt;BR /&gt;&lt;BR /&gt;and in registar.log&lt;BR /&gt;-------------------Start Event---------------&lt;BR /&gt;Event 1447 occurred at Wed Mar 29 17:55:01.720369 2006&lt;BR /&gt;Process ID: 13181 (/etc/opt/resmon/lbin/registrar) Log Level: Error&lt;BR /&gt;send_error_reply: Cannot send error reply to the client:&lt;BR /&gt;error code = 15: An error occurred while attempting to send a message: Broken pipe&lt;BR /&gt;-------------------End Event-----------------&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hrere are teh process that are running&lt;BR /&gt;-------------------Start Event---------------&lt;BR /&gt;Event 1447 occurred at Wed Mar 29 17:55:01.720369 2006&lt;BR /&gt;Process ID: 13181 (/etc/opt/resmon/lbin/registrar) Log Level: Error&lt;BR /&gt;send_error_reply: Cannot send error reply to the client:&lt;BR /&gt;error code = 15: An error occurred while attempting to send a message: Broken pipe&lt;BR /&gt;-------------------End Event-----------------&lt;BR /&gt;&lt;BR /&gt;and abouth the monitoring demons&lt;BR /&gt;&lt;BR /&gt;Thes are my demons rnning iw wqorking server ...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HP:root&amp;gt;  ps -eaf | grep -i /opt/resmon&lt;BR /&gt;    root  1355     1  0  Feb  6  ?         2:11 /etc/opt/resmon/lbin/pkgmond&lt;BR /&gt;    root  1156     1  0  Feb  6  ?         9:06 /etc/opt/resmon/lbin/p_client&lt;BR /&gt;    root 11411  6953  0  Mar 28  ?         0:00 /etc/opt/resmon/lbin/registrar&lt;BR /&gt;    root  1184     1  0  Feb  6  ?         0:37 /etc/opt/resmon/lbin/clustermon&lt;BR /&gt;    root 12534     1  0  Mar 28  ?         0:00 /etc/opt/resmon/lbin/emsagent&lt;BR /&gt;    root 13417     1  0  Mar 28  ?         0:41 /etc/opt/resmon/lbin/lanmond&lt;BR /&gt;&lt;BR /&gt;but these demons are not working running in the server which is haveing problem.....&lt;BR /&gt;&lt;BR /&gt;HPSVR1:root&amp;gt;ps -eaf | grep -i /opt/resmon&lt;BR /&gt;    root  1156     1  0  Feb  6  ?         9:06 /etc/opt/resmon/lbin/p_client&lt;BR /&gt;root  1355     1  0  Feb  6  ?         2:11 /etc/opt/resmon/lbin/registrar&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Mar 2006 07:47:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759221#M259007</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-30T07:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759222#M259008</link>
      <description>Could you post the output of&lt;BR /&gt;&lt;BR /&gt;# swlist -l product | grep EMS</description>
      <pubDate>Thu, 30 Mar 2006 08:15:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759222#M259008</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-30T08:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759223#M259009</link>
      <description>HI &lt;BR /&gt;&lt;BR /&gt; here is the output&lt;BR /&gt;&lt;BR /&gt;  EMS-Config            A.03.20        EMS Config&lt;BR /&gt;  EMS-Core              A.03.20        EMS Core Product&lt;BR /&gt;  EMS-DiskMonitor       A.03.20        EMS Disk Resource Monitor&lt;BR /&gt;  EMS-KRMonitor         A.11.00.04     EMS Kernel Resource Monitor&lt;BR /&gt;  EMS-MIBMonitor        A.03.20        EMS MIB Resource Monitor Product&lt;BR /&gt;  EMS-RdbmsMon          A.03.20        EMS Database Monitor&lt;BR /&gt;  PHCO_16280            1.0            du(1) value for non-HP NFS systems incorr&lt;BR /&gt;ect&lt;BR /&gt;  PHCO_17867            1.0            ioinitrc, assign ttys for B,C class syste&lt;BR /&gt;ms&lt;BR /&gt;  PHCO_18901            1.0            extendfs_hfs fix for large file systems&lt;BR /&gt;  PHKL_22771            1.0            fix device and file system swap problems&lt;BR /&gt;  PHKL_24905            1.0            VxFS mount/unmount problems.&lt;BR /&gt;  PHSS_26871            1.0            EMS (A.03.20) &amp;amp; HA Monitors (A.03.20) pat&lt;BR /&gt;ch&lt;BR /&gt;  Sup-Tool-Mgr          B.11.00.26.07  Support Tools Manager for HPUX systems</description>
      <pubDate>Thu, 30 Mar 2006 08:32:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759223#M259009</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-30T08:32:03Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759224#M259010</link>
      <description># swlist -a state -l fileset | grep EMS&lt;BR /&gt;&lt;BR /&gt;all configured ?&lt;BR /&gt;&lt;BR /&gt;if you have lsof installed check if tcp port 1712 is in use ?&lt;BR /&gt;&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Thu, 30 Mar 2006 09:05:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759224#M259010</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-30T09:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759225#M259011</link>
      <description>Yes It was checked already and found that the port was in use...&lt;BR /&gt;&lt;BR /&gt; When I stoppe all the process it was in Time_Wait status...</description>
      <pubDate>Thu, 30 Mar 2006 09:21:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759225#M259011</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-30T09:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: EMS /rdbms not avilable error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759226#M259012</link>
      <description>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..</description>
      <pubDate>Fri, 31 Mar 2006 11:03:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-rdbms-not-avilable-error/m-p/3759226#M259012</guid>
      <dc:creator>jayachandran.g</dc:creator>
      <dc:date>2006-03-31T11:03:06Z</dc:date>
    </item>
  </channel>
</rss>

