> -----Original Message-----
> From: Juchem, Matthias
> Sent: Dienstag, 17. September 2002 21:23
>
> Hi Daniel.
>
> > -----Original Message-----
> > From: Dittmar, Daniel
> > Sent: Tuesday, September 17, 2002 9:01 PM
>
> > Juchem, Matthias wrote:
> > > At
> > http://sapdb.org/htmhelp/e6/155a65fb7511d1a96c00a0c9449261/fra
> > meset.htm, what does "Reparse the statement" mean?
> > >
> > > Simply re-executing the statement does not help...
> > >
> > > Or does this refer to prepared statements?
> >
> > This is indeed an error that appears in connection with prepared
> > statements. When the prepared statement is no longer valid
> > (e.g. because
> > the table structure has changed), the kernel will issue a
> -8 and the
> > interface is supposed to reprepare the statement internally and to
> > reexecute the statement. This error code should never see the
> > light of
> > the day.
>
> Hmm. I use Perl DBD::ODBC with unixODBC, with prepared statements.
>
> But: This error also occures when the program connects to the
> DB, prepares the statement and executes it once. The
> statement simply calls an DBPROC with does some inserts into
> a view, so the tables structures do not change.
>
> Does SAP DB cache prepared statements between database sessions?
>
> Is there a workaround for this? If there's an updated version
> of unixODBC, I'll upgrade in a few days, maybe it helps.
>
With some help from Matthias we found out that using a sequence
in a dbproc will result in the error -8 if the sequence was dropped
and recreated after dbproc creation.
As a workaround you could recreate the dbproc.
With one of the next versions we will fix the bug but no schedule by now.
Thanks to Matthias for reporting this bug.
Holger
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
