two different bugs. Jonathan is referring to an export bug that may be
affectingthe OP, Pete is referring to a damn good reason to patch 9.0.1
namely bug 2121935 (which curiously is not publicly accessible) but note
185074.1 which deals with it is.
I'd just get off the 9.01 release entirely.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
"Mark D Powell" <Mark.Powell_at_eds.com> wrote in message
news:2687bb95.0302061031.514742fd_at_posting.google.com...
> Connor McDonald <connor_mcdonald_at_yahoo.com> wrote in message
news:<3E426BFE.5847_at_yahoo.com>...
> > Pete Sharman wrote:
> > >
> > > In article <e20868e8.0302051037.3fbd25c6_at_posting.google.com>,
bsarma_at_basit.com
> > > says...
> > > >
> > > >Greetings,
> > > >
> > > >Oracle Release 9.0.1.0.0 EE and IBM RS6000 AIX 4.3.3 64bit
> > >
> > > Arghhh! Please patch to 9.0.1.3 ASAP to get past a wee small security
bug.
> > >
> > > Pete
> > >
> > > HTH. Additions and corrections welcome.
> > >
> > > Pete
> > >
> > > SELECT standard_disclaimer, witty_remark FROM company_requirements;
> >
> > I thought it was a patch on top of 9013 to avoid the security bug - I
> > don't think 9013 contains it (or has this changed?)
> >
> > cheers
> > connor
>
> I tried searching metalink on the bug number Jonathan posted and got
> no hits; however I did get a hit on the alert number which in turn
> contained the bug number and the link brought it up. The bug was
> updated on Jan. 6, 2003 and says fixed in product version 10.0. The
> bug 2598387 appears to have been introduced with 8.1.7.3 and exists in
> all vesions through at least 9.2.0.1 per the text. The work around
> provided is to set ORA_OCI_NO_OPTIMIZED_FETCH=1.
>
> IMHO this is a bug that needs fixing in the current versions.
>
> -- Mark D Powell --
Received on Thu Feb 06 2003 - 13:57:39 CST
