Path: news.cambrium.nl!textnews.cambrium.nl!feeder3.cambriumusenet.nl!feed.tweaknews.nl!postnews.google.com!a27g2000prj.googlegroups.com!not-for-mail
From: Noons <wizofoz2k@gmail.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: DBMS_REPAIR.CHECK_OBJECT
Date: Sun, 25 Apr 2010 17:00:21 -0700 (PDT)
Organization: http://groups.google.com
Lines: 23
Message-ID: <daae95ae-0c1c-49d0-ac22-ce3bbb49779c@a27g2000prj.googlegroups.com>
References: <74315004-fd10-4876-9d82-8ceca5d8d2bc@g11g2000yqe.googlegroups.com> 
 <8a76cb22-17bf-4972-a202-9e4614f9e5e2@z11g2000yqz.googlegroups.com> 
 <ea7f1d55-1d8c-4478-9f58-c448b5ca58f4@g11g2000yqe.googlegroups.com>
NNTP-Posting-Host: 203.158.46.14
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1272240021 13380 127.0.0.1 (26 Apr 2010 00:00:21 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 26 Apr 2010 00:00:21 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: a27g2000prj.googlegroups.com; posting-host=203.158.46.14; 
 posting-account=oJZDiQoAAAD-FXU2V1mvdIjuYivOHSlr
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.19) 
 Gecko/2010031422 Firefox/3.0.19 (.NET CLR 3.5.30729),gzip(gfe)
Xref:  news.cambrium.nl

On Apr 26, 1:57=A0am, zigzagdna <zigzag...@yahoo.com> wrote:

> > Can you run rman backup to disk and at least get rman to tell you how
> > many bad blocks you have?
>
> Only one block is corrupted. Oracle 11g provdies various health
> monitors and only one block is shown as corrupted. My export dump
> fails for one table. One can reterive dthat table from a prevous
> export backup, but that will require some loss in data. =A0I am trying
> to figure what is the value of dbms_repair.

A while ago I recovered most of a release 7 table with the same
problem.
If you can somehow mark that block as bad, the export will proceed
ignoring it.  That means you can then try to recover most of the
missing block's rows with the help of a prior export.
In v7 there was an event one could turn on to force export to ignore
bad blocks and proceed with the rest.  Perhaps that still works in
11?  Or else some variation of dbms_repair to mark that block as
ignored?
FWIW: the url to the post on bad blocks in V7 is
http://dbasrus.blogspot.com/2007_05_01_archive.html
HTH
