Re: Urgent: Problem with Cursor for UPDATE

Yes I know what you say.

But the problem is that we have one database where we can use SELECT FOR UPDATE with COMMIT without error "Fetch out of secuence" and other one that the same program fails with "Fetch out of secuence" and I don't know why.

Any one knows anything ????

Thanks.

Elias.

"Nuno Souto" <nsouto_at_nsw.bigpond.net.au.nospam> escribió en el mensaje news:3b050f80.12803935_at_news-server...
> On Fri, 18 May 2001 12:46:40 +0200, "Elias Alpuente"
> <ealpuente_at_isoco.com> wrote:
>
> >We have a stored procedure with a cursor for update on one table.
> >This cursor fetch a row and update it with WHERE CURRENT OF
> >clause. We make a COMMIT each 500 rows procesed.
> >
>
> That kills it. You must not use a CURRENT OF after a commit.
> Particularly if what you are updating is the table where you are doing
> the CURRENT OF. Might work sometimes, but ORACLE specifically advises
> against it. It's in the "manuel".
>
> In Steve's site, www.ixora.com.au, there is plenty of info on this.
>
>
> Cheers
> Nuno Souto
> nsouto_at_bigpond.net.au.nospam
> http://www.users.bigpond.net.au/the_Den/index.html
Received on Fri May 18 2001 - 10:18:09 CDT