Re: Check for database corruption?

Unfortunately.. that doesn't really test for corruption, only invalid objects.. A few shops I know run a dbverify on all the datafiles every now and then, you might try that.. It is suppossed to be a complete checksum. I've heard a rumor that this isn't so, but never found any supporting documentation on that fact..

• Doug
• Oracle Certified DBA "If everything feels like it's under control, you're probably not going fast enough" - Mario Andretti

On Sat, 09 Dec 2000 04:07:33 GMT, gmei_at_my-deja.com wrote:

>Try run
>
>select * from all_objects where status='INVALID'
>
>and spool the result to a file, then mail this file to you every night.So
>that we can read the result every morning.
>
>Hope this helps.
>
>Guang
>
>
>In article <90rjtm$6pc$1_at_nnrp1.deja.com>,
> Aaron <asentell_at_my-deja.com> wrote:
>> I'm fairly new to Oracle but not to database administration. As a
>> Sybase DBA, I made sure that I ran a database consistency check on all
>> my production databases at least once a week. From what I've read and
>> seen thus far, however, this same level of precaution is not necessarily
>> required for Oracle, although I'm quite sure this is not Oracle's
>> official position.
>>
>> I want to get some input from DBAs who are out there in the trenches and
>> have experience with this. Is it worth the time to run "analyze
>> table...verify structure cascade" on a regular basis in production
>> databases? Note that we perform a full export every night in addition
>> to database backups.
>>
>> Thank you,
>> Aaron
>>
>> Sent via Deja.com http://www.deja.com/
>> Before you buy.
>>
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Fri Dec 08 2000 - 22:31:26 CST