Tom
This is because the index was created using the nologging option after the hot backup was taken. If the table was involved in a nologging operation , that also will have the same problem.
Thanks
Riyaj "Re-yas" Shamsudeen
Certified Oracle DBA
i2 technologies www.i2.com
| "Terrian, Tom" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 11/28/01 02:31 PM
|
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> cc: Subject: strange NOLOGGING error |
Can anyone explain this?
I got the following error after restoring a hotbackup data file:
ORA-01578: ORACLE data block corrupted (file # 13, block # 379)
ORA-01110: datafile 13: '/u11/oradata/grp1/DRMS_SM_01.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
Since the corruption was on an index, no problem, I just rebuilt it. However, I
was wondering why the table was not also corrupted with the index since they are
on the same file? Since someone must have done a direct load, why was the
recovery of the index corrupted but not the table?
Oracle 8.1.6.3.0
HPUX 11.0
Tom
Tom Terrian
Oracle DBA
WPAFB - DAASC
[EMAIL PROTECTED]
937-656-3844
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Terrian, Tom
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
