Jason T
Marcotte wrote:
> On Win XP SAP 7.4.3
Build 17, I'm getting an Invalid sequence for DML and DDL statements
(-3007)
> when attempting a select from a given table. The error comes up via both JDBC and ODBC
> calls with any select from the problem table.
>
> Documentation gives very little information on this error - it simply states
> "Repeat the QUERY and FETCH" which obviously does no good.
> The problem goes away by dropping and recreating the table,
> but that's not ideal by any stretch of the imagination.
>
> Is this an error at the parse phase? ie if I flush the sql pool, might that help?
> Typically, when there's DB catalog corruption, I get an AK catalog error -
> but could this be the problem nonetheless?
>
> Any insight would be appreciated.
> when attempting a select from a given table. The error comes up via both JDBC and ODBC
> calls with any select from the problem table.
>
> Documentation gives very little information on this error - it simply states
> "Repeat the QUERY and FETCH" which obviously does no good.
> The problem goes away by dropping and recreating the table,
> but that's not ideal by any stretch of the imagination.
>
> Is this an error at the parse phase? ie if I flush the sql pool, might that help?
> Typically, when there's DB catalog corruption, I get an AK catalog error -
> but could this be the problem nonetheless?
>
> Any insight would be appreciated.
usually
this error should not be reproducable with several select at different
times.
If this
occurs, the catalog is somehow confused, but you will usually have no
chance
to
influence this by flushing or the like. And there are possibilities where
no
AK catalog
error, but that one mentioned above will occur.
It sounds
as if you had this error several times, each time starting with
a
freshly
created table, doing something and then resulting in that error
reproducable.
Is that
true, can you reproduce that effect from scratch
table?
Or. if you
cannot reproduce it from scratch, can you please make up
your
mind what
you did between the last correct
insert/update/delete/select
on that
table and that error, all commands (even those resulting in an
error)
done for
that table explicitly or implictly (dropping a foreign key or the
whole
table with
a foreign key in, where your special table is the referenced
one)
are of
interest.
Then we/I
would be VERY interested in that table/index/foreign key definition and the
doing
between
creation of that table/last good command and that error. Perhaps some
sequence of ddl/dml
is able to
confuse the catalog.
Elke
SAP Labs
Berlin
