Thanks for the suggestion. The documentation says the dbms_repair
ignores "out-of-line" lobs. Our corrupted block is an out-of-line lob,
so I don't think this will work for us. I passed this on to Oracle
Support anyway, to see what they will do.
> It's either DBMS_REPAIR or your harvest has failed
Hmmmm, that is interesting. The name of the product is Harvest, and the
vendor is CA.
From: Mladen Gogala [mailto:mgogala@(protected)]
Sent: Monday, October 23, 2006 9:36 PM
To: Sam Bootsma
Subject: Re: Help - Corrupted Block - Lob Segment - NOLOGGING
On 10/23/2006 02:46:43 PM, Sam Bootsma wrote:
> Documents are stored in a BLOB column in an Oracle table. It is NOT
> stored "in_row" and logging is turned off (for performance reasons
> told me).
The problem with "NOLOGGING" is the fact that your blocks are no longer
by logging mechanism, which means that you cannot recover them. That's
for performance - until you have to recover. The general advice for
nologging is to
to use it for things that can be easily re-created, like indexes or
> We recently encountered a bad block, and I have since determined there
> are additional bad blocks, but it is just one block that is
> giving us a problem.
> When a user attempts to check an object into the repository, they
> get the error message:
> E03020003: Database Error: [CAI/PT][ODBC Oracle 8
: ORACLE data block corrupted (file # 31,
> # 123533)
: data file 31: '/san1/oradata/PROD/harvestblob01.dbf'
: Data block was loaded using the NOLOGGING option
It's either DBMS_REPAIR or your harvest has failed. Position of a DBA is
to the position of a director of FEMA. It's a very comfortable position,
strikes.....May Bacchus, the god of harvest be with you.