MaxDB 7.6.06.03 - ERR 53133 help!!!

[Former Member]

Hello all,

i'll be very thankful if anybody could help.

we have developed billing softaware on MaxDB 7.6.06.03 (before was Sap early version). With Telco Billing all was OK (not too much records - CDRs), but now we developed for WiMax and have about 3 mln Cdrs per day. Copying, updating or deleting a big amount of records we got message:

2010-01-30 01:18:20 0x1E14 ERR 53133 DATACACH Second exclusive request on same page

2010-01-30 01:18:20 0x1E14 ERR 53133 DATACACH PAGENO: 1651732

2010-01-30 01:18:20 0x1E14 ERR 53133 DATACACH CBLOCKPTR: 0X7FFF68A5080

2010-01-30 01:18:20 0x1E14 ERR 53000 B*TREE 070300000000000008FB000000000000

2010-01-30 01:18:20 0x1E14 ERR 53000 B*TREE Index Root 821542

2010-01-30 01:18:20 0x1E14 ERR 3 Admin Database state: OFFLINE

2010-01-30 01:18:20 0x1E14 ERR 2 Admin + A fatal error caused EMERGENCY SHUTDOWN. core is written

2010-01-30 01:18:20 0x1E14 ERR 18196 DBCRASH vabort:Emergency Shutdown, Kernel_Administration.cpp: 619

2010-01-30 01:18:20 0x256C ERR 19999 BTRACE Using 'imagehlp.dll' version: 4.0.5

Our customer suggest change DB, but after 7 years exploitation...

Thanks in advance.

[Former Member]

Markus, Lars, NOW really thanks for Your comments.

Just last question: where can I find prices, conditions for upgrading to commercial version os MAXDb?

Regards

[lbreddemann]

Please see the [WIKI|http://wiki.sdn.sap.com/wiki/display/MaxDB/FAQ#FAQ-HowtogetsupportifSAPMaxDBisusedwithnonSAPapplications%3F] on that.

regards,

Lars

[Former Member]

Mister Lars,

if You can not help - please, tease another user.

One more time - DB must be available EVERY MILISECOND. I can not to see to monitor 24 hours per day (now is third day!!!)

Maybe there is persons who realy can help?????

Thanks

[lbreddemann]

> Mister Lars,

>

> if You can not help - please, tease another user.

> One more time - DB must be available EVERY MILISECOND. I can not to see to monitor 24 hours per day (now is third day!!!)

If this is the case, then choosing a solution without professional vendor support is a bad choice.

Sorry that you feel teased about this - but that's how it is.

> Maybe there is persons who realy can help?????

Well, buying support would help in this case, because then you would get the already available bugfix for this.

There isn't a workaround available - so basically you're stuck here.

regards,

Lars

[markus_doehr2]

Arturas,

> if You can not help - please, tease another user.

> One more time - DB must be available EVERY MILISECOND. I can not to see to monitor 24 hours per day (now is third day!!!)

Just in case you didn't notice: Lars is one of the support people @ SAP for MaxDB. He would help you if you'd have a support contract. If that system is that critical it's just grossly negligent to not have one. Nobody is blaming or teasing you personally, it's just that there is no solution available in the version you have and to get a fixed version you need to pay; it's that simple.

> Maybe there is persons who realy can help?????

The only "help" would be providing you with a fixed version. I'd highly suggest you contact your manager so that he can do a contract (however that looks like) to avoid such problems in the future.

Markus

[Former Member]

To Lars,

if You put in mobile sim card with PREPAID agreement You will not be able to do a call if providers DB crashes (in DB they have account credits!!!!!). Low severity?

Thanks for Your "advice"

[lbreddemann]

if You put in mobile sim card with PREPAID agreement You will not be able to do a call if providers DB crashes (in DB they have account credits!!!!!). Low severity?

No support contract for a mission critical application?

How severe can this be?

Besides, this error does not seem to occur very often in SAP systems.

I've only seen a few calls until now.

You don't loose data.

You don't corrupt data.

Therefore I don't see that this bug is anymore critical than other db crashes.

regards,

Lars

[Former Member]

Thanks Ivan,

after 6 or 7 years work with SAP and not just SAP, I saw very many bugs, but this bug's severity is such high...

For Billing of Prepaid system DB must be alive every milisecond, I cant reindex tables after every crash.

Thanks anyway.............

[lbreddemann]

> after 6 or 7 years work with SAP and not just SAP, I saw very many bugs, but this bug's severity is such high...

And guess what?

Paying customers actually get the bug fix right away...

> For Billing of Prepaid system DB must be alive every milisecond, I cant reindex tables after every crash.

Get a bit into drama mode?

Just ONE index has to be rebuild in case such a crash occurs.

Besides, it's not even a super severe bug - compared to the HOT NEWS bugs we had for Oracle 10g in the last two years, this one is just "not nice!".

regards,

Lars

[Former Member]

hello ,

this looks like PTS described here:

http://pts:1080/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1201789

solved in 7.6.6.8

unfortunatley currently there is no comunity version released with the fix.

Our customer suggest change DB, but after 7 years exploitation...

if you plann to switch DB anytime you hit some bug, you will have hard life ...

Regards

Ivan

-

---

Workaround: You must delete and recreate the relevant index. However,

the shutdown may occur again when you subsequently access the index.

You can determine the relevant index using the index root number that

was logged and the following SQL statement:

select i.tablename, i.indexname, f.root, f.clustered

from files f, indexes i

where f.root = <index root number> and

f.fileid = i.fileid

-

---