Hi Elke,
sorry for this spam mailing! Seems that I am not very talented to use my mail client
;-)
If your kernel programer needs a vtrace to analyze the problem he should get one! But:
as I am out of office for some days I can send the trace file soonest on Monday to
you. I hope it is o.k. for you?
kind regards
Frank Schimmelpfennig
PHILIPS Semiconductors Hamburg
ATO-Hamburg IT&DataSupport
Tel.: +49 40 5613 -1835, Fax: -3020
"Zabach, Elke"
<elke.zabach@sap To: Frank
Schimmelpfennig/HBG/SC/PHILIPS@EMEA1
.com> [EMAIL PROTECTED]
cc:
04.06.2002 06:55 Subject: RE: SYSERROR -9232 KB
Nil transindex (3rd attempt)
Classification:
[EMAIL PROTECTED] wrote:
> sorry I had to cut down the attached files in order to pass
> the filters of the mailing list ;-)
>
> Here is my question:
>
> While testing our database application in some kind of
> "stress test" we got back a system error -9232 KB Nil
> transindex (full message: (-9232):System error: KB Nil
> transindex). Analyzing the database via DBMGUI and the
> knldiag and the knldiag.err files
> (see the extracts of thoses files in the attached archive) I
> saw that data devspace is nearly exhausted (we forgot to size
> up this test instance (v7.3.0.18) for this tests which lasted
> nearly 2.5 days:-( ).
>
> Looking through the documentation and the mailing list
> archive I found no hint about this system error -9232. Is
> there someone who can give me a hint what is the meanig of it?
Thank you sending several times, twice with appended info, once without.
When I checked the knldiag, I saw move-error
MOVE VAK262.18: 1[8064]->8065[6834] len:-1230
SYSERROR -9111 Move error
This bug was fixed with 7.3.0.23.
Because of the bad check in 7.3.0.23, skip it and use 7.3.0.24
For your -9232-error: even the guys responsible for this part of the code
has no good idea why this error occurs in your special case. There are
several places in the code where this error is set, but which one is the
one in your case??
He asked for a vtrace. Mhm, you told us that the test lasted 2,5 days.
And I am not sure if you are willing and have the time to test again with
vtrace, flush it after receiving the error and send the trace to us.
With this we will have a chance to find out what happens, without this,
we will not have. It is up to you to size up your database and forget this
behaviour or to try again and hope that the trace will show us what is/was
going on.
Elke
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
