<?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: Restarting fast_start parallel rollback in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238510#M890825</link>
    <description>Hi Nikee,&lt;BR /&gt;&lt;BR /&gt;Now for the integrity of database you better let oracle perform recovery.&lt;BR /&gt;for next time just do shutdown about.&lt;BR /&gt;&lt;BR /&gt;HTH.</description>
    <pubDate>Mon, 05 Apr 2004 02:08:29 GMT</pubDate>
    <dc:creator>Printaporn_1</dc:creator>
    <dc:date>2004-04-05T02:08:29Z</dc:date>
    <item>
      <title>Restarting fast_start parallel rollback</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238508#M890823</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;9.2.0.4.0 on HP-UX &lt;BR /&gt;&lt;BR /&gt;SMON: Restarting fast_start parallel rollback &lt;BR /&gt;&lt;BR /&gt;I shut a DB down badly by killing the DB service during a very large transaction. It's been up again for 2hrs but it's still recovering and nothing else will run with any reasonable speed. Lots of IO.&lt;BR /&gt;&lt;BR /&gt;Is there any way of bypassing/shortcutting/stopping the recovery process? I am happy to abandon all work done since the last committed transaction pre-abort.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Also the UNDO tablespace is not releasing the space used by the uncommited blocks. How can I free-up the UNDO tablespace?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Nikee</description>
      <pubDate>Fri, 02 Apr 2004 15:05:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238508#M890823</guid>
      <dc:creator>Nikee Reddy</dc:creator>
      <dc:date>2004-04-02T15:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: Restarting fast_start parallel rollback</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238509#M890824</link>
      <description>Hi Nikee&lt;BR /&gt;&lt;BR /&gt;The message means SMON is starting PQ slaves to perform rollback.&lt;BR /&gt;&lt;BR /&gt;The parameter FAST_START_PARALLEL_ROLLBACK determines the maximum number of processes that can exist for performing parallel rollback. This parameter is useful on systems in which some or all of the transactions are long running.&lt;BR /&gt;&lt;BR /&gt;FALSE indicates that parallel rollback is disabled&lt;BR /&gt;LOW limits the number of rollback processes to 2 * CPU_COUNT&lt;BR /&gt;HIGH limits the number of rollback processes to 4 * CPU_COUNT&lt;BR /&gt;&lt;BR /&gt;LOW is the default setting for the parameter.&lt;BR /&gt;&lt;BR /&gt;may this might help u&lt;BR /&gt;&lt;BR /&gt;With Regards &lt;BR /&gt;Hari</description>
      <pubDate>Sat, 03 Apr 2004 06:25:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238509#M890824</guid>
      <dc:creator>Hari Kumar</dc:creator>
      <dc:date>2004-04-03T06:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: Restarting fast_start parallel rollback</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238510#M890825</link>
      <description>Hi Nikee,&lt;BR /&gt;&lt;BR /&gt;Now for the integrity of database you better let oracle perform recovery.&lt;BR /&gt;for next time just do shutdown about.&lt;BR /&gt;&lt;BR /&gt;HTH.</description>
      <pubDate>Mon, 05 Apr 2004 02:08:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restarting-fast-start-parallel-rollback/m-p/3238510#M890825</guid>
      <dc:creator>Printaporn_1</dc:creator>
      <dc:date>2004-04-05T02:08:29Z</dc:date>
    </item>
  </channel>
</rss>

