<?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: Block corruption issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129403#M727682</link>
    <description>Your next move has a few choices.  One way (the old way) is to recover your files from before the corruption, and roll forward your changes from the archive logs until you are whole again.  If you've just spotted this error and it's new, you're in great shape to recover.  The second and easier way is that hopefully Rman will be able to handle this all for you, as long as the files from before the corruption exist in the backup catalog server somewhere.&lt;BR /&gt;&lt;BR /&gt;Good luck, and I hope you get your recovery working fine.&lt;BR /&gt;&lt;BR /&gt;Incidentally, since this is an HPUX forum, and not a Windows one - if you'd switch to a more robust OS, the chances of this kind of event happening would be seriously reduced.  You ever notice that the cheaper OSs(Windows, and less so, but still in that list, Linux) have more file system and data corruption?  I have, and no offense, but it just gets down to you get what you pay for...</description>
    <pubDate>Tue, 15 Jan 2008 17:26:24 GMT</pubDate>
    <dc:creator>TwoProc</dc:creator>
    <dc:date>2008-01-15T17:26:24Z</dc:date>
    <item>
      <title>Block corruption issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129402#M727681</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;   Rman full/inc backup is failed with the below errors &lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;RMAN-03009: failure of backup command on ch00 channel at 01/13/2008 23:34:38&lt;BR /&gt;ORA-19566: exceeded limit of 0 corrupt blocks for file H:\ORACLE\ORADATA\SVDL\PROTOTYPE_DATA_01.DBF&lt;BR /&gt;RMAN-03009: failure of backup command on ch00 channel at 01/13/2008 23:33:43&lt;BR /&gt;ORA-19566: exceeded limit of 0 corrupt blocks for file H:\ORACLE\ORADATA\SVDL\DL_CONTENT_49.DBF&lt;BR /&gt;-----------------------------------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;This is physical standby database.&lt;BR /&gt;i can't use maxcorrupt parameter in the rman script becoz corrupted blocks are large in number.&lt;BR /&gt;&lt;BR /&gt;SQL&amp;gt; select * from V$DATABASE_BLOCK_CORRUPTION ;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO&lt;BR /&gt;     ---------- ---------- ---------- ------------------ ---------&lt;BR /&gt;        18      49140     144917                  0 ALL ZERO&lt;BR /&gt;        18     262272          1                  0 ALL ZERO&lt;BR /&gt;        65     307485     216812                  0 ALL ZERO&lt;BR /&gt;        65     524416          1                  0 ALL ZERO&lt;BR /&gt;        73     340470     183827                  0 ALL ZERO&lt;BR /&gt;        73     524416          1                  0 ALL ZERO&lt;BR /&gt;        84     524288          1                  0 ALL ZERO&lt;BR /&gt;&lt;BR /&gt;Please help me how to resolve this issue.&lt;BR /&gt;&lt;BR /&gt;Version of oracle - oracle 10g&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Nirmal &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Jan 2008 08:37:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129402#M727681</guid>
      <dc:creator>Nirmalkumar</dc:creator>
      <dc:date>2008-01-15T08:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: Block corruption issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129403#M727682</link>
      <description>Your next move has a few choices.  One way (the old way) is to recover your files from before the corruption, and roll forward your changes from the archive logs until you are whole again.  If you've just spotted this error and it's new, you're in great shape to recover.  The second and easier way is that hopefully Rman will be able to handle this all for you, as long as the files from before the corruption exist in the backup catalog server somewhere.&lt;BR /&gt;&lt;BR /&gt;Good luck, and I hope you get your recovery working fine.&lt;BR /&gt;&lt;BR /&gt;Incidentally, since this is an HPUX forum, and not a Windows one - if you'd switch to a more robust OS, the chances of this kind of event happening would be seriously reduced.  You ever notice that the cheaper OSs(Windows, and less so, but still in that list, Linux) have more file system and data corruption?  I have, and no offense, but it just gets down to you get what you pay for...</description>
      <pubDate>Tue, 15 Jan 2008 17:26:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129403#M727682</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2008-01-15T17:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: Block corruption issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129404#M727683</link>
      <description>Hi Nirmal,&lt;BR /&gt;&lt;BR /&gt;Use dbv (usage "dbv FILE=t_db1.dbf BLOCKSIZE=&amp;lt;...&amp;gt; FEEDBACK=100") and post the result here please.&lt;BR /&gt;&lt;BR /&gt;Note: see the "Database Utilities" manual for better understanding of dbv utility.&lt;BR /&gt;&lt;BR /&gt;PS: please review your points assignment policy...&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Eric Antunes</description>
      <pubDate>Thu, 17 Jan 2008 09:22:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/block-corruption-issue/m-p/4129404#M727683</guid>
      <dc:creator>Eric Antunes</dc:creator>
      <dc:date>2008-01-17T09:22:47Z</dc:date>
    </item>
  </channel>
</rss>

