RE: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against
- From: "Marquez, Chris" <cmarquez@xxxxxxxxxxxxxxxx>
- To: <mark.powell@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 11 Aug 2005 15:33:24 -0400
Sorry should have said env info;
Oracle 9205
RMAN 9205
>>does rman backup blocks marked as non-recoverable?
never heard anything less than RMAN backing up all (used) blocks.
Maybe there is some skip|avoid RMAN syntax, but I'm not using any directly.
Chris Marquez
Oracle DBA
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Powell, Mark D
Sent: Thu 8/11/2005 3:19 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: ORA-1578...block corrupted...error is normal...a block...had a
NOLOGGING...operation performed against
Ques: What kind of backup: rman or manual? And what was the version of
Oracle, 8i?
If the answer is rman then the question becomes does rman backup blocks
marked as non-recoverable?
HTH -- Mark D Powell --
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Marquez, Chris
Sent: Thursday, August 11, 2005 2:11 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: ORA-1578...block corrupted...error is normal...a block...had a
NOLOGGING...operation performed against
I can NOT believe the if I used NOLOGGING to create and INDEX "long ago"
*and* had
many, many subsequent FULL BACKUPS that it could/did effect or error on
a future recovery?
Again, we are getting this error after full db recovery on indexes
created (NOLOGGING), well before the FULL backup and thus no "NOLOGGING"
objects in any of the arch logs applied...what gives?
Chris Marquez
Oracle DBA
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 59, block # 763411)
ORA-01110: data file 59: '/o04/oradata/orcl/e_indx_05.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
....
ORA-1578 is reported when a block is thought to be corrupt on read.
Note that in Oracle8i the ORA-1578 reports the RELATIVE FILE NUMBER
and not the ABSOLUTE FILE NUMBER. The error should be accompanied
by an ORA-1110 error indicating the absolute file number and name.
...
c) (oThis error is normal if accessing a block which has had
a NOLOGGINGr UNRECOVERABLE) operation performed against
it and has since been recovered. In Oracle8i this case also reports:
"ORA-26040: Data block was loaded using the NOLOGGING option"
Other related posts:
