PROTECTED]
Subject: Re: Database Verification
Date: Sat, 18 Jan 2003 22:58:43 -0800
MIME-Version: 1.0
Received: from newsfeed.cts.com ([209.68.248.164]) by
mc1-f6.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Sun, 19 Jan
2003 00:05:17 -0800
Received: from fatcity.UUCP (uucp@localhost
can do,
no
one else.
Thanks for the tip.
Arup
From: Tim Gorman [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: Database Verification
Date: Sat, 18 Jan 2003 22:58:43 -0800
MIME-Version: 1.0
Received: from
Oooo yea another nice feature...
RF
-Original Message-
Sent: Sunday, January 19, 2003 12:59 AM
To: Multiple recipients of list ORACLE-L
Don't forget about the more important issue of detecting corrupted archived
redo logfiles. Datafile corruption can be bad; redo log file
Don't forget about the more important issue of detecting corrupted archived
redo logfiles. Datafile corruption can be bad; redo log file corruption is
always disastrous, especially if undetected until recovery time...
RMAN checks archivelogs for corruption while backing them up.
- Original
I am considering the appropriate way to do database
corruption prevention.
Should I use one or more of the following as a
proactive measure ?
a) Export
b) DBVerify
c) Analyze table table_name validate structure
cascade
Any advice ?
Thanks,
PH
Pui Ho,
The only way you can be
I would do all three. A good backup stategy is only good if you read all
your data all the time. You can have corrupt data that doesn't get read and
doesn't cause a problem for weeks, month, years. By that time you have no
backup that does not contain corrupt data. Export to a null file to
(d) All of the above
i) Export to /dev/null will go through all the fields of all the tables, all
the rows, but will not scan indexes
ii) Dbverify will scan for block corruptions but not logical corruptions.
iii) Analyze will check for table-index logical corruption.
Practically, you could just
Subject: RE: Database Verification
Sent by:
[EMAIL PROTECTED
We had a corrupt index block which caused an ORA-600 which was not noticed
and eventually brought down the database.
We do lots of checks now. (d) All of the above.
R. Smith
-Original Message-
Sent: Friday, January 17, 2003 8:19 AM
To: Multiple recipients of list ORACLE-L
(d) All of
No need to do any of this if you are using RMAN. With each backup, RMAN
checks each block backed up for any corruption. Corruption will be reported
and you
can opt to allow a certain amount of it or none.
Rf
Robert G. Freeman
Technical Management Consultant
TUSC - The Oracle Experts
Pui Ho,
Stephane raises a good point, unfortunately, many operations groups
stop at the backup. It is not the responsibility of operations to backup the
database/system. It is the responsibility of operations to recover the
database/system. There are many stories of backups that execute
Title: RE: Database Verification
FWIW:
The other answers have been correct as to what to do to check for corruption.
As far as preventing it?? I don't know of a way you can PREVENT it from happening. When it happens, it's usually something out of your hands (bad hardware, glitch in OS
Use Rman.
Rman automatically detects and reports corrupt blocks.
right Robert? :)
Tom Mercadante
Oracle Certified Professional
-Original Message-
Sent: Friday, January 17, 2003 7:28 AM
To: Multiple recipients of list ORACLE-L
I am considering the appropriate way to do database
If I recall correctly, RMAN checks for corruption.
-Original Message-
I am considering the appropriate way to do database corruption prevention.
Should I use one or more of the following as a proactive measure ?
a) Export
b) DBVerify
c) Analyze table table_name validate
Robert,
Surprising
Robert G. Freeman
Technical Management Consultant
TUSC - The Oracle Experts www.tusc.com
When did you join TUSC? It looks that all guru's are joining TUSC.
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Robert,
What if the RMAN incremental facility is used and the blocks get corrupted
in an unchanged space? Will RMAN then identify the corruption?
Arup
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Friday, January 17, 2003 10:39 AM
No need to do
And in the extreme end of the spectrum, you might want to learn about block
dumps in order to be prepared for the day when you have a corrupted block.
The block dumps can show people - who know what they're looking for, ie have
prepared - a lot of useful information. Might be a valuable piece
17 matches
Mail list logo
