Re: I'm doomed, right?

"Yong Huang" <yong321_at_yahoo.com> wrote in message news:b3cb12d6.0110060619.6382e171_at_posting.google.com...
> I guess what I'm more interested in this comparison is like: dbv could
> give false positive while export shows corruption-type errors in a
> datafile.

DBV doesn't give false positives. At least, I've never heard of it doing so. I guess all applications might throw a glitch or two and it *could* happen. Then again, the world *could* end tomorrow at 7.39pm.

>Again, I suppose the database is already open and
> controlfiles and logfiles are known to be good. I only want to compare
> the integrity check on datafiles.
>

Export is doing selects (sort of), dbv isn't. The hit on the system is likely to be much lighter with dbv than with export. The 'goodness' of the integrity check each can do is identical.

> BTW, if I remember right you can export the SYS schema if you specify
> owner=sys. full=y won't do that.

Are you being deliberately perverse or does it just come naturally? From the bottom of this post, Jonathan's first line reads "I would go for a full database export...". It therefore follows that the inability to export SYS's schema relates to full exports, since that was the context of this thread.

Whatever: unless you propose to check the integrity of your data files by doing a mix of database and schema-level exports, you can't use export to check large swathes of the SYSTEM data file. With dbv, you can. In one pass.

HJR
>
> Yong Huang
> yong321_at_yahoo.com
>
> "Howard J. Rogers" <howardjr_at_www.com> wrote in message
news:<3bbe911a$1_at_news.iprimus.com.au>...
> > Export can only be run against a database that is fully open. DBV can
be
> > run against any datafile, whether hot or cold, open, closed, or
indifferent.
> > A full database export will check everything; DBV can be used to check
just
> > a part of a data file (from block X to block Y). Export can't be
applied to
> > objects owned by SYS. DBV can check the entire SYSTEM datafile. Export
> > can't check your backups, DBV can.
> >
> > Regards
> > HJR
> > --
> > Resources for OracleT: www.geocities.com/howardjr2000
> > =========================================
> >
> >
> > "Yong Huang" <yong321_at_yahoo.com> wrote in message
> > news:b3cb12d6.0110052003.5c08715d_at_posting.google.com...
> > > Jonathan,
> > >
> > > How do you compare using dbv and using exp to /dev/null to verify
> > > datafiles? One of them is more reliable than the other? Or one is
> > > recommended in such and such scenario while the other in another?
> > > Suppose the database is open and controlfiles, logfiles are known to
> > > be good.
> > >
> > > Yong Huang
> > > yong321_at_yahoo.com
> > >
> > > "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message
> > news:<1002304053.22582.0.nnrp-14.9e984b29_at_news.demon.co.uk>...
> > > > I would go for a full database export to /dev/null.
> > > > This will physical verify all the user data, and
> > > > most of the data dictionary.
Received on Sun Oct 07 2001 - 07:38:20 CDT