Database Crash 7.6.06.03

[Former Member]

Hi folks,

Mi database that was working flawlessly since sveral years start crashing ramdomly last week.

Knldiag.err show that messages:

2012-06-04 17:15:00     0x1504 ERR 20011 MOVECODE Bad parameter: source size [8192000] dest size [20], source addr [0X22E45F89]+2, dest addr [0X22E3B830]+1, 79 bytes

2012-06-04 17:15:00     0x1504 ERR 20011 MOVECODE  to copy

2012-06-04 17:15:00     0x1504 ERR 20011 MOVECODE Bad parameter: source size [8192000] dest size [20], source addr [0X22E45F89]+2, dest addr [0X22E3B830]+1, 79 bytes

2012-06-04 17:15:00     0x1504 ERR 20011 MOVECODE  to copy

2012-06-04 17:15:00     0x1504 ERR 18196 DBCRASH  vabort:Emergency Shutdown, SAPDB_PascalMoveKernel.cpp: 464

2012-06-04 17:15:00     0x1504 ERR 18196 DBCRASH  vabort:Emergency Shutdown, SAPDB_PascalMoveKernel.cpp: 464

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   Using 'imagehlp.dll' version: 4.0.5

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   SymbolSearchPath:  d:\sdb\data\wrk\TORPEDO;C:\Program Files\SDB\7600\pgm;C:\Program Files\SDB\7600\symbols;C:\Progr

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE                      am Files\SDB\7600\symbols;C:\Program Files\SDB\7600\sap;C:\WINDOWS;C:\Program Files\SDB\7600\sap

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE                      \

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   ----> Register Dump <----

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE     Eax=0x22e3b624 Ebx=0x22e3b7bc Ecx=0x00000000 Edx=0x7c82845c Esi=0x00000000 Edi=0x39636108

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE     Eip=0x77e4bef7 Esp=0x22e3b620 Ebp=0x22e3b674

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE     Cs=0x6176001b  Ss=0x6e650023  Ds=0x35310023  Es=0x31200023  Fs=0x2d36003b  Gs=0x32310000  Efl=0x0246

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   ----> Module List <----

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   |.text Start |.text End   | Module File Name

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x00400000 | 0x00b83000 | C:\Program Files\SDB\7600\pgm\kernel.exe

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x1dd10000 | 0x1de48000 | C:\Program Files\SDB\7600\pgm\liboms.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x1de50000 | 0x1dea6000 | C:\WINDOWS\system32\MSVCR71.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x1dec0000 | 0x1dfc0000 | C:\Program Files\SDB\7600\pgm\dbghelp.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x1e0c0000 | 0x1e0ea000 | C:\WINDOWS\system32\imagehlp.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x71b20000 | 0x71b61000 | C:\WINDOWS\System32\mswsock.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x71bb0000 | 0x71bb9000 | C:\WINDOWS\system32\WSOCK32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x71bf0000 | 0x71bf8000 | C:\WINDOWS\system32\WS2HELP.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x71c00000 | 0x71c17000 | C:\WINDOWS\system32\WS2_32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x76290000 | 0x762ad000 | C:\WINDOWS\system32\IMM32.DLL

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x76ed0000 | 0x76efa000 | C:\WINDOWS\system32\DNSAPI.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x76f10000 | 0x76f3e000 | C:\WINDOWS\system32\WLDAP32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x76f50000 | 0x76f63000 | C:\WINDOWS\system32\Secur32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x76f70000 | 0x76f77000 | C:\WINDOWS\System32\winrnr.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x76f80000 | 0x76f85000 | C:\WINDOWS\system32\rasadhlp.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77380000 | 0x77411000 | C:\WINDOWS\system32\USER32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77420000 | 0x77523000 | C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   :            :            : x-ww_05FDF087\comctl32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77670000 | 0x777a9000 | C:\WINDOWS\system32\ole32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77ba0000 | 0x77bfa000 | C:\WINDOWS\system32\msvcrt.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77c00000 | 0x77c49000 | C:\WINDOWS\system32\GDI32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77c50000 | 0x77cf0000 | C:\WINDOWS\system32\RPCRT4.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x77e40000 | 0x77f42000 | C:\WINDOWS\system32\kernel32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x7c800000 | 0x7c8c3000 | C:\WINDOWS\system32\ntdll.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x7c8d0000 | 0x7d0cf000 | C:\WINDOWS\system32\SHELL32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x7d180000 | 0x7d1d2000 | C:\WINDOWS\system32\SHLWAPI.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   | 0x7d1e0000 | 0x7d27c000 | C:\WINDOWS\system32\ADVAPI32.dll

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE   ----> Stack Back Trace <----

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE     kernel32!RaiseException + 60 bytes

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE         SFrame:  IP:77e4bef7 RA:006aee0c FP:22e3b674 SP:22e3b620

2012-06-04 17:15:00     0x142C ERR 19999 BTRACE         Params:  01:e000aaaa 02:00000000 03:00000000 04:00000000

2012-06-04 17:15:02     0x142C ERR 19999 BTRACE     kernel!sql50k_abort + 28 bytes

....

2012-06-04 17:15:03     0x16DC ERR 19999 BTRACE   Mini dump file 'KnlMini.dmp' written!

I've checked the database structure, backup/recreate/restore the database, but it keep crashing.

I've activated all database traces, but the .prt file is too huge (52 mb) and not very readable.

There are several applications connected on this database, and none of them have been updated.

How can i find what's wrong ?

TIA

Frédéric DEMILLY.

[Former Member · Accepted solution]

Hi Frédéric,

I checked the error message system WebPTS of MaxDb http://maxdb.sap.com/webpts and could find some known bugs with MaxDb Version 7.6.06.03.

e.g.: Number: 1230917 , 1209883, 1189760 ....

This problem is not related to a structure problem in the database but a software bug of MaxDB which can be solved in the current version of SAP MaxDb Version 7.6.06.22.

Do you have access to the SAP SWDC? Then you should download the newest patch of SAP MaxDb version 7.6.06. and do an update as soon as possible to avoid further problems

Regards, Christiane

[Former Member · Accepted solution]

Hi Christiane,

Thanks for your reply.

I don't think i've access to SWDC, since i use the community edition of MaxDB, and the last version available is 7.6.06.10..

I've already tried to migrate our test database to 7.7, but after that roles didn't work anymore (i don't know why), so i'm stuck with version 7.6.

Isn't there a way for me to download the last 7.6 version ?

Frédéric.

[Former Member · Accepted solution]

Hi Frederic,

thanks for the information We will deliver 7.6.06.22 as soon as possible for the community.

Regards, Christiane

[Former Member · Accepted solution]

That's a great news.

In the mean time i've migrated the database to 7.6.06.10, i hope this will solve my probleme (i'll migrate to 7.6.06.22 as soon as it will be available).

Frédéric.

[Former Member · Accepted solution]

I've just another question: the database run flawlessly during several years, and now it crash 1 to 3 time a day.

There wasn't any database nor application upgrade.

What can i do to find witch query is responsible for the crash ?

TIA

Frédéric.

[Former Member · Accepted solution]

Hi Frederic,

such kind of problem can be caused by the number of data which has to be processed. So it is not caused by changes of application or database code

To find out which SQL stamtent is causing the crash you could switch on the database kernel trace with option default and order. When the database crashes the next time save the file knltrace first before you restart the database again. with the command xkernprot <filename> akbmx the knltrace file is converted into a readable file. This file has to be analyzed by the MaxDb development team to get an idea which statement why causes the problem.

Regards, Christiane

[Former Member · Accepted solution]

The database just crash again, and this time i think i found which task cause this trouble.

This is the only one (and the only apps) who use cursors...

I've converted knltrace.dat with xkernprot, which give my a 77+ Mb .prt file. How can i submit it ? I didn't find the link on this site.

What should i search for in this file ?

In the mean time i'll rewrite my query without cursor, i hope this will work again.

Frédéric.

[Former Member · Accepted solution]

Hi Frederic,

the log file should contain the SQL command which causes the crash. You already know the SQL command? Then you know the table name as well - so the easyeast way would be to search for the tablename.

Regards, Christiane

[Former Member · Accepted solution]

Hi Christiane,

I've finaly found the query that crash (sometime) the database:

insert into msg_envoi(ma_i_num,lc_c_code,tr_c_code,me_c_idrsc1,me_c_idrsc2,me_c_idrsc3,me_c_donnees) select ma_i_num,lc_c_dest,tr_c_code,ma_c_idrsc,ma_c_idrsc2,ma_c_idrsc3,ma_c_donnees from msg_attn where ma_l_traite = false and lc_c_dest is not null ignore duplicates

I dont know how i can rewrite this quesry, so i've change my program so this query work on less records.

No crash to report since this update.

I'm now working on my programs logics to make this query obsolete.

Thanks for your precious help.

Frédéric.

[Former Member · Accepted solution]

Hi Frederic,

sounds good - It would be interesting to check if the priginal coding is working fine with 7.6.06.22 - unfortunately this version is not available so far for download but it is in process tp provide this version.

let's us keep in contact.

Regards, Christiane

[Former Member · Accepted solution]

I'll upgrade our test server as soon as the version is available for download.

But it would be hard to test, because the code involved run on a scheduled task every minute from 01:00am to 23:00 pm, and the database crashed "only" 3 or 4 time a day, and the problem only appear on the production one (but there is far less activity).

I can provide the knltrace.* files if necessary, i juste didn't find the link to do this.

Frédéric.

[Former Member · Accepted solution]

Hi Frederic,       

  I just want to iform you about the availability of our current MaxDb version 7.6.

You can download this version now.

Regards, Christiane

[Former Member · Accepted solution]

Hi Christiane,

I've downloaded this version yesterday, i'm upgrading the test database.

I'll do some regression tests (i've find a query that work with 7.6.06.03 and not with 7.6.06.10), and if everything is OK i'll upgrade production one ASAP.

Frédéric.