<?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: SERVICE GUARD needs reboot? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629842#M237464</link>
    <description>You won't need to reboot unless you install kernel patches (ie: PHKL_XXXXX). If you end up needing to reboot for some reason that I can't identify, do a cmhaltpkg (pkg_name), then a cmrunpkg -n (node)*the_other_server* (pkg_name), then do a cmhaltnode and reboot.</description>
    <pubDate>Wed, 21 Sep 2005 13:52:19 GMT</pubDate>
    <dc:creator>Jon M Zellhoefer</dc:creator>
    <dc:date>2005-09-21T13:52:19Z</dc:date>
    <item>
      <title>SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629838#M237460</link>
      <description>there are two superdome system(11.23pi)managed service guard.and they are 4 packages each other.first server one have ora_pkg1 package is using by shared mode to access data from two servers.&lt;BR /&gt;second, server one has pkg1 package is using exclusive mode to access achive and dump files.&lt;BR /&gt;third, server one has pkg3 package is waching oracle daemon.&lt;BR /&gt;fourth, server one has pkg5 package is checking gigabit card.&lt;BR /&gt;server two is like that.&lt;BR /&gt;from this weeks, try to upgrade oracle 9.2.0.5 to 9.2.0.6. &lt;BR /&gt;does it needs to reboot system? if needs,&lt;BR /&gt;i want to know what orders do I have to proceed in SERVICE GUARD.&lt;BR /&gt;specifically, for example, first shutdown oracle, second, cmhaltnode -f system1.....&lt;BR /&gt;&lt;BR /&gt;becase this is operating system in permanently, after one system patch is ended,&lt;BR /&gt;other system have to proceed work.&lt;BR /&gt;Thanks Reguards.</description>
      <pubDate>Tue, 20 Sep 2005 03:11:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629838#M237460</guid>
      <dc:creator>???_185</dc:creator>
      <dc:date>2005-09-20T03:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629839#M237461</link>
      <description>Unless the newwer version of Oracle requires some network or kernel patches or a kernel tune, I see no reason why you would need a reboot.&lt;BR /&gt;Check with Oracle if there are patch or kernel change requirements</description>
      <pubDate>Tue, 20 Sep 2005 03:25:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629839#M237461</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2005-09-20T03:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629840#M237462</link>
      <description>A patch update from oracle, in your case 9.2.0.5 to 9.2.06 doesn't require reboot.&lt;BR /&gt;OS patch update are not required in this case</description>
      <pubDate>Tue, 20 Sep 2005 03:59:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629840#M237462</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-09-20T03:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629841#M237463</link>
      <description>if system must be reboot, what order do I have to proceed?&lt;BR /&gt;two system is clustered by mc service guard.&lt;BR /&gt;but, it needs to be running for users.&lt;BR /&gt;i mean the first server have to be reboot and then second server have to be reboot..&lt;BR /&gt;could you check the reboot order?&lt;BR /&gt;1. cmhaltnode -f server1 -&amp;gt; in first server&lt;BR /&gt;after first server is rebooted,&lt;BR /&gt;2. cmrunnode server1&lt;BR /&gt;3.cmhaltnode -f server2 -&amp;gt; in second srever&lt;BR /&gt;after second server is rebooted?&lt;BR /&gt;4.cmrunnode server2&lt;BR /&gt;is right? is there anything to add?</description>
      <pubDate>Wed, 21 Sep 2005 00:42:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629841#M237463</guid>
      <dc:creator>???_185</dc:creator>
      <dc:date>2005-09-21T00:42:25Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629842#M237464</link>
      <description>You won't need to reboot unless you install kernel patches (ie: PHKL_XXXXX). If you end up needing to reboot for some reason that I can't identify, do a cmhaltpkg (pkg_name), then a cmrunpkg -n (node)*the_other_server* (pkg_name), then do a cmhaltnode and reboot.</description>
      <pubDate>Wed, 21 Sep 2005 13:52:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629842#M237464</guid>
      <dc:creator>Jon M Zellhoefer</dc:creator>
      <dc:date>2005-09-21T13:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629843#M237465</link>
      <description>Hi zungwon&lt;BR /&gt;&lt;BR /&gt;1) Stop al the packages on node one&lt;BR /&gt;  cmhaltpkg packagex&lt;BR /&gt;2) Stop the services on node 1&lt;BR /&gt;   cmhaltnode node1&lt;BR /&gt;3) Start package one node2&lt;BR /&gt;   cmrunpkg -n node2 packageX&lt;BR /&gt;4) reboot node1&lt;BR /&gt;   shutdown -r 0&lt;BR /&gt;&lt;BR /&gt;Perform the same steps if your are updating node one&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Sep 2005 14:06:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629843#M237465</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-09-21T14:06:05Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629844#M237466</link>
      <description>First off, I wouldn't do the -f unless I had to...instead, shutdown each package on the node, move them to the other node...with cmrunpkg -n node2 mypackagename...then do the cmhaltnode...&lt;BR /&gt;&lt;BR /&gt;But - if you oracle is on disks that are controlled by MC/SG - then you need to upgrade oracle while the package is running!&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Wed, 21 Sep 2005 15:18:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629844#M237466</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-09-21T15:18:25Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629845#M237467</link>
      <description>reboot steps:&lt;BR /&gt;&lt;BR /&gt;1. shutdown Oracle&lt;BR /&gt;2. stop crs (/sbin/init.d/init.crs stop)&lt;BR /&gt;3. stop packages (cmhaltpkg &lt;PACKAGE_NAME&gt;)&lt;BR /&gt;4. stop nodes (cmhaltnode &lt;NODE_NAME&gt;)&lt;BR /&gt;5. shutdown cluster (cmhaltcl -f -v)&lt;BR /&gt;6. reboot server (shutdown -ry now)&lt;BR /&gt;&lt;BR /&gt;or&lt;BR /&gt;&lt;BR /&gt;1. shutdown Oracle&lt;BR /&gt;2. stop crs (/sbin/init.d/init.crs stop)&lt;BR /&gt;3. shutdown cluster (cmhaltcl -f -v)&lt;BR /&gt;4. reboot server (shutdown -ry now)&lt;/NODE_NAME&gt;&lt;/PACKAGE_NAME&gt;</description>
      <pubDate>Wed, 21 Sep 2005 16:40:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629845#M237467</guid>
      <dc:creator>Hakan Aribas</dc:creator>
      <dc:date>2005-09-21T16:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629846#M237468</link>
      <description>there is ora_pkg pakcages two server is using shared volume.i think it doesn't affect oracle upgrade.&lt;BR /&gt;I have other problems.&lt;BR /&gt;after this process :&lt;BR /&gt;1) Stop al the packages on node one&lt;BR /&gt;cmhaltpkg packagex&lt;BR /&gt;2) Stop the services on node 1&lt;BR /&gt;cmhaltnode node1&lt;BR /&gt;3) Start package one node2&lt;BR /&gt;cmrunpkg -n node2 packageX&lt;BR /&gt;i didn't shutdown node1 system.&lt;BR /&gt;and i want to shutdown node2 system in one hour.&lt;BR /&gt;and then, i'll upgrade two node system.&lt;BR /&gt;how can I shutdown node2 package?&lt;BR /&gt;is it OK that just type like  "cmhaltnode node2"&lt;BR /&gt;&lt;BR /&gt;last, after reboot two system, if type like this "cmruncl", can these system is being  operated normally?"&lt;BR /&gt;&lt;BR /&gt;THANKS  REGUARDS.</description>
      <pubDate>Wed, 21 Sep 2005 22:10:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629846#M237468</guid>
      <dc:creator>???_185</dc:creator>
      <dc:date>2005-09-21T22:10:23Z</dc:date>
    </item>
    <item>
      <title>Re: SERVICE GUARD needs reboot?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629847#M237469</link>
      <description>Do a cmhaltpkg packageX on node2, then cmhaltnode, then cmhaltcl, then reboot.&lt;BR /&gt;&lt;BR /&gt;When they are up and running - cmruncl&lt;BR /&gt;&lt;BR /&gt;Unless of course you have AUTOSTART_CMCLD=1 in /etc/rc.config.d/cmcluster&lt;BR /&gt;&lt;BR /&gt;then the cluster will start at boot (I don't do this - I always start manually - in case you don't want the cluster up and running - due to a hardware failure ot what have you - IE - you should troubleshoot your system prior to running the cluster in the event of some failure).&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Thu, 22 Sep 2005 07:59:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-needs-reboot/m-p/3629847#M237469</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-09-22T07:59:45Z</dc:date>
    </item>
  </channel>
</rss>

