ERR 53000 B*TREE problems with MaxDB 7.5.0.38

[Former Member]

Hello,

in the last days we had 2 db crashes and we don't know the reason. In the knldiag.err we have the following entries:

.....

2008-03-28 21:33:06 0x538 ERR 53000 B*TREE No separator found #; 8

2008-03-28 21:33:06 0x538 ERR 18196 DBCRASH vabort:Emergency Shutdown, vgg01.c: 5402

2008-03-31 09:50:22 --- Starting GMT 2008-03-31 07:50:22 7.5.0 Build 038-123-133-420

2008-03-31 10:03:19 ___ Stopping GMT 2008-03-31 08:03:19 7.5.0 Build 038-123-133-420

2008-03-31 10:05:31 --- Starting GMT 2008-03-31 08:05:31 7.5.0 Build 038-123-133-420

2008-03-31 21:37:08 0xC80 ERR 53000 B*TREE IdxOrder.SubNode invalid; 772928

2008-03-31 21:37:08 0xC80 ERR 18196 DBCRASH vabort:Emergency Shutdown, vgg01.c: 5402

2008-04-01 09:44:48 --- Starting GMT 2008-04-01 07:44:48

I think there's a problem with an index (because of message "IdxOrder.SubNode...) or is there a problem with physical memory ?

In DBM-GUI there are no indexes marked as bad...

any help appreciated......GERD KOENIG.....

[Former Member]

has been handled by the customer itself...

[martin_koerner]

Dear Mr. Koenig,

to clarify what's going on here a deeper investigation is required. Are you an SAP customer with access to the Support Portal? In this case I recommend to open a support ticket on BC-DB-SDB. One of the MaxDB support staff will connect to the affected database and analyze via this way.

Best regards,

Martin Koerner

[Former Member]

Hi Mr Koerner,

thanks for answering quickly.

We don't have a contract with sap, and this database runs on a server of one of our customers (connect via vpn) where we perform some administration tasks. So access would be also a problem.

some more hints...?

thanks...::GERD KOENIG::..

[martin_koerner]

Hi Mr Koenig,

ok, then we have to wait for the next shutdown. Please activate database kernel trace in Database Manager GUI (DBMGUI):

#1: Check, Database Trace

#2: activate checkbox for option "default",

#3: in symbol toolbar click on the "green ball" (Selected Items On).

If the database shutdown occurs again, please proceed as follows in Database Manager GUI before you restart the database:

#1: Check, Database Trace

#2: choose tab "Trace File"

#3: activate the checkboxes for a, b, k, m, s

#4: click on the green check mark in symbol toolbar

Now the trace log file will be created. It is named :<Database name>.prt and located in rundirectory (by default: /sapdb/data/wrk/<SID>)

This file please zip and send to me.

Best regards,

Martin

[Former Member]

Hello,

I performed the steps described by you and zipped some files for further analysis (already sent to you).

bye...GERD KOENIG...

[martin_koerner]

Hello Mr Koenig,

unfortunately the trace log file is empty. Is it possible to reproduce the error

via a specific action, e.g. an SQL query?

Best regards,

Martin Koerner

[Former Member]

Hi,

we try to find a way to reproduce the error.

so long....GERD KOENIG...

[martin_koerner]

Dear Mr. Koenig,

to clarify what's going on here a deeper investigation is required. Are you an SAP customer