From: "Gary Healy (Powerup)" <ghealy@powerup.com.au>
Subject: Re: Error: ORA-01002: fetch out of sequence
Date: 2000/07/07
Message-ID: <3965d5db@grissom>#1/1
Distribution: world
References: <8jr01g$5ge$1@nnrp1.deja.com> <3964EEEB.9A393A6F@netspace.net.au>
X-Original-NNTP-Posting-Host: ts53036.powerup.com.au
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Trace: ozemail.com.au 962975196 203.32.8.130 (Fri, 07 Jul 2000 23:06:36 EST)
Organization: OzEmail Ltd, Australia
X-MSMail-Priority: Normal
NNTP-Posting-Date: Fri, 07 Jul 2000 23:06:36 EST
Newsgroups: comp.databases.oracle.server


This error can occur if you are using a combination of
1. Setting transaction to use specific rollback segment
2. Committing within loop
3. Performing Update where current of

Gary.
Joseph Li <lijoecyn@netspace.net.au> wrote in message
news:3964EEEB.9A393A6F@netspace.net.au...
> I have thrown away the hardcopy manual. So here is from the
> Documentation CD :-
>
> =====================================================================
>
> ORA-01002: fetch out of sequence
>
> Cause: In a host language program, a FETCH call was issued out of
> sequence. A successful parse-and-execute call must
> be issued before a fetch. This can occur if an attempt was made to FETCH
> from an active set after all records have been
> fetched. This may be caused by fetching from a SELECT FOR UPDATE cursor
> after a commit. A PL/SQL cursor loop
> implicitly does fetches and may also cause this error.
>
> Action: Parse and execute a SQL statement before attempting to fetch the
> data.
>
> =======================================================================
>
> Looks like you might have to look at the stored procedure code.
>
> rgds
> Joseph
>
> kimathi@my-deja.com wrote:
>
> > I get the following error from a stored procedure call.
> > Any hints what may be wrong?
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>