It seems that a file can be "fuzzied" for various reasons. Being in
hot backup mode is but one of them. The fact that you could, prior to
9i, depend on this column to determine if a file belongs to a
tablespace that is in hot backup mode, was actually due to a bug
(1158714). It is now being reported correctly in 9i. Guess you will
have to depend on v$backup.status from now on.
"xueyang" <xueyangy_at_singnet.com.sg> wrote in message news:<aqt52u$kjg$1_at_mawar.singnet.com.sg>...
> And I find the fuzzy column is null in a 8.1.6 db.
> Anyone can tell me the difference?
>
> TIA
> "xueyang" <xueyangy_at_singnet.com.sg> wrote in message
> news:aqt3ua$kgg$1_at_mawar.singnet.com.sg...
> > Hi,
> >
> > I read from oracle document that says the fuzzy column'value is changed
> from
> > null to 'YES' when you issue alter tablespace begin backup.
> > But when i go to my 9.2.0 database, do nothing but issue 'select fuzzy
> from
> > v$datafile_header', all values are 'YES' and i am sure no one doing the
> > backup.
> > Any can tell me why that is?
> >
> > TIA
> >
> >
Received on Wed Nov 13 2002 - 11:11:14 CST
