Re: Help - Corrupted Block - Lob Segment - NOLOGGING

  • From: Mladen Gogala <mgogala@xxxxxxxxxxx>
  • To: sbootsma@xxxxxxxxxxxxxx
  • Date: Mon, 23 Oct 2006 21:35:32 -0400

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 they
> 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 excellent
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 MV's.

> We recently encountered a bad block, and I have since determined there
> are additional bad blocks, but it is just one block that is continually
> giving us a problem.
> When a user attempts to check an object into the repository, they often
> get the error message:
> E03020003: Database Error: [CAI/PT][ODBC Oracle 8
> driver][Oracle]ORA-01578: ORACLE data block corrupted (file # 31, block
> # 123533)
> ORA-01110: data file 31: '/san1/oradata/PROD/harvestblob01.dbf'
> ORA-26040: 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, until 
strikes.....May Bacchus, the god of harvest be with you. 
Mladen Gogala


Other related posts: