RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against

  • From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
  • To: "Jared Still" <jkstill@xxxxxxxxx>
  • Date: Tue, 23 Aug 2005 14:54:54 -0700

Thanks Jared, I'll do some more tests to see if I can figure out exactly what's 
going on.  I suspect that the direct-insert is minimally logged as it says in 
the documentation, but perhaps there is still a signifcant amount from 
dictionary updates due to block splits and other recursive activity, and when 
you recover, the direct-inserted blocks are corrupt, but the select statement 
you ran for the regular (non-direct, logged) insert did not need to touch those 
corrupt blocks so it completed just fine - but if you forced a full index scan, 
you would see the corruption.
 

-----Original Message-----
From: Jared Still [mailto:jkstill@xxxxxxxxx]
Sent: Tuesday, August 23, 2005 2:47 PM
To: Allen, Brandon
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: ORA-1578...block corrupted...error is normal...a block...had a 
NOLOGGING...operation performed against


v$datafile
FILE_NAME
----------------------------------------------------------------------------------------------------
STATUS  UNRECOVERABLE_TIME  UNRECOVERABLE_CHANGE#
------- ------------------- ---------------------
/u01/oradata/dv03/test01.dbf
ONLINE  08/23/2005 12:33:51            1039632753

---------------------------------------------------------------

14:44:28 SQL>l
  1* select * from v$backup_corruption
14:44:29 SQL>/
 
no rows selected
 
--------------------------------------------------------------

DBV: I have not included any dbv output.
dbv reports every file I test as corrupt ( including SYSTEM)
This is with the database shutdown.
Don't know what the problem there is, but I'm not going to 
pursue it right now.

Jared




On 8/23/05, Allen, Brandon < Brandon.Allen@xxxxxxxxxxx> wrote: 


Thanks for the great test case Jared - just a few questions:
 
Can you check the following to see if there is any indication of corruption due 
to the recovery through the nologging operation:
 
 - v$datafile: unrecoverable_time & unrecoverable_change# columns
 - v$backup_corruption
 - run dbverify on the datafile
 
Have you submitted your case to Oracle support to see if it is a bug, or if 
we're all missing something?
 
Thanks again,
Brandon
 

-----Original Message-----
From: Jared Still [mailto: jkstill@xxxxxxxxx]
Sent: Tuesday, August 23, 2005 12:46 PM
To: Hemant K Chitale
Cc: Allen, Brandon; cmarquez@xxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: ORA-1578...block corrupted...error is normal...a block...had a 
NOLOGGING...operation performed against




On 8/23/05, Hemant K Chitale < hkchital@xxxxxxxxxxxxxx> wrote: 


Jared,

You ARE right.  You really don't need to retest it.  


Maybe not, but I want to.



Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.




-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist



Other related posts: