Gerald Nowitzky wrote:
...
> >Yes, you will see the last row which was inserted half and half
> >primary data inserted / secondary data not inserted leading to
> >that ... error -9049.
>
> This means that the table data row has been written, but not
> the key / index
> information, is it?
> (Gerald)
In your case (and in the reproducable one I had) : YES.
Yes, only because the primary data found a nice place in a page
(or got the last free page available), but the index info needed
a new page, too, but there was none available any more.
An error occured which resulted (correctly) in the rollback of
the statement. Unfortunately the rollback was confused because
of this half there - half not there-record and did not handle it
correctly.
In case even the primary data could not find enough free space
for being stored, no problem had occured.
Elke
SAP Labs Berlin
> ----- Original Message -----
> From: Zabach, Elke
> To: 'Gerald Nowitzky' ; [EMAIL PROTECTED]
> Sent: Monday, June 02, 2003 5:02 PM
> Subject: RE: BUG on implicit rollback after error in INSERT
>
>
> Gerald Nowitzky wrote:
>
> >
> > Hi!
> > I have got a table containing 1.5 mio rows and wanted to
> > build some kind of
> > lookup-table for it:
> >
> > CREATE TABLE "DBA"."MSGOWNER"
> > (
> > "OWNER_ID" Integer,
> > "MSG_KEY" Integer
> > )
> >
> > Then I created an Index
> > CREATE INDEX "IDX_MSGOWNER_OWNER" ON
> "DBA"."MSGOWNER"("OWNER_ID" ASC)
> > and tried to fill the table using
> >
> > insert into msgowner select msg_from,msg_key from messenger
> >
> > I ended up in a
> > General error;-904 POS(1) Space for result tables exhausted.
> >
> > Ok so far. Now here the strange part begins:
> > 1) a "Select * from msgowner" still returned one single row.
> > I guess it was
> > the last one, the insert was able generate.
> >
> > 2) after that I tried to delete it using "delete from
> > msgowner" and ended up
> > in a
> > General error;-9049 POS(1) System error: BD Primkey from inv
> > in primtree not
> > found.
> >
> > After that I tried to delete the row again; this time it worked.
> >
> > knldiag didn't show anything else despite the error.
> > (Gerald)
>
> Sorry for the delay.
> The guy checking log-things did not take care for your problem,
> now I checked and could reproduce.
> Yes, you will see the last row which was inserted half and half
> primary data inserted / secondary data not inserted leading to
> that ... error -9049.
>
> I hope the developer will be able to correct this as soon as possible.
>
> Elke
> SAP Labs Berlin
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
>
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
