B*TREE Free page failed

[Former Member]

Dear all,

customer is loading some data into production system. We experienced an emergency shutdown of the database.

In knldiag is visible:

2009-09-28 10:26:57 9876 ERR 53000 B*TREE Free page failed; 1020

2009-09-28 10:26:57 9876 ERR 3 Admin Database state: OFFLINE

2009-09-28 10:26:57 9876 ERR 2 Admin + A fatal error caused EMERGENCY SHUTDOWN. core is written

2009-09-28 10:26:57 9876 ERR 11196 DBCRASH vabort:Emergency Shutdown, Kernel_Administration.cpp: 619

Any idea ?

Thank you.

Pavol

[Former Member · Accepted solution]

Hello Lars, <br>

<br>

please see:

<br><br>

2009-09-28 10:26:57 9876 ERR 53000 B*TREE Free page failed; 1020<br>

2009-09-28 10:26:57 9876 ERR 3 Admin Database state: OFFLINE<br>

2009-09-28 10:26:57 9876 ERR 2 Admin + A fatal error caused EMERGENCY SHUTDOWN. core is written<br>

2009-09-28 10:26:57 9876 ERR 11196 DBCRASH vabort:Emergency Shutdown, Kernel_Administration.cpp: 619<br>

2009-09-28 10:26:57 9876 ERR 11599 BTRACE -

---

> Emergency Stack Back Trace <----<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (0):0xef15b5<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (1):0xef1619<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (2):0xef1762<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (3):0xef1797<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (4):0xf143e7<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (5):0xe26c2d<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (6):0xdeb5db<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (7):0xab82e3<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (8):0xa84cef<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (9):0x9b74d3<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (10):0xa41555<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (11):0xa3e567<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (12):0xa406cf<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (13):0x9a419f<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (14):0x950501<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (15):0x946e94<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (16):0x946ef9<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (17):0x8d7026<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (18):0x65c447<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (19):0x65c8aa<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (20):0x7843f2<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (21):0x785710<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (22):0x779cc6<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (23):0x77abc8<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (24):0x83acdf<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (25):0x83b6bb<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (26):0x83c74b<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (27):0x83f2cd<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (28):0xdfc754<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (29):0xdfc933<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (30):0xe8a6b8<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (31):0xf3bc27<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (32):0xf3bfb9<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (33):0xee5343<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (34):0x2b47452e0143<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE (35):0x2b4745b00b8d<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE -

---

> Module List <----<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |.text Start |.text End | Module File Name<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x0000000000400000|0x000000000111a000| /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002aabc6ffa000|0x00002aabc7215000| /sapdb/P01/db/lib/liboms.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b47451be000|0x00002b47451d9000| /lib64/ld-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b47452da000|0x00002b47452ee000| /lib64/libpthread-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b47453f3000|0x00002b47453f5000| /lib64/libdl-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b47454f7000|0x00002b47454ff000| /lib64/librt-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b4745601000|0x00002b47456c4000| /usr/lib64/libstdc++.so.5.0.7<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b47457dd000|0x00002b4745831000| /lib64/libm-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b4745932000|0x00002b474593f000| /lib64/libgcc_s.so.1<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b4745a40000|0x00002b4745b76000| /lib64/libc-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE |0x00002b4745c76000|0x00002b4745c79000| /lib64/libc-2.4.so<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE -

---

> Symbolic Stack Back Trace <----<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 0: 0x0000000000ef0c4d eo670_UnixTraceStack +0x01ad<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 1: 0x0000000000ef1619 eo670_CTraceContextStackOCB +0x0009<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 2: 0x0000000000ef1762 eo670_CTraceStackOCB +0x0032<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 3: 0x0000000000ef1797 eo670_CTraceStack +0x0017<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 4: 0x0000000000f143e7 vabort +0x0027<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 5: 0x0000000000e26c2d Z9RTECrashRK20SAPDBErr_MessageList +0x008d<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 6: 0x0000000000deb5db<br> ZN21KernelAdministration7OfflineERK20SAPDBErr_MessageListbb +0x02cb<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 7: 0x0000000000ab82e3 gg999Abort +0x0243<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 8: 0x0000000000a84cef g01abort +0x013f<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 9: 0x00000000009b74d3 b13free_node +0x0073<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 10: 0x0000000000a41555 ZN23cbd403OverFlowInvQueueD1Ev +0x0075<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 11: 0x0000000000a3e567 ZN17cbd403InvListSet17bd403_RemoveListsEi +0x0057<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 12: 0x0000000000a406cf<br> Z28bd403MergePrimKeysInInvListsR17cbd300InvCurrentS0_PhiS1_iS1_iS1_iRi +0x0a6f<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 13: 0x00000000009a419f b03MergeInvLists +0x051f<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 14: 0x0000000000950501 k73_index_range +0x0671<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 15: 0x0000000000946e94 k720_select +0x06b4<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 16: 0x0000000000946ef9 k720_single_select +0x0019<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 17: 0x00000000008d7026 k05functions +0x09e6<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 18: 0x000000000065c447 a06lsend_mess_buf +0x0297<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 19: 0x000000000065c8aa a06dml_send_mess_buf +0x003a<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 20: 0x00000000007843f2 a505most_execute +0x0af2<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 21: 0x0000000000785710 a505loop_most_execute +0x0360<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 22: 0x0000000000779cc6 a501exec_with_change_rec +0x05d6<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 23: 0x000000000077abc8 a501execute +0x0518<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 24: 0x000000000083acdf ak92analyze_messagetype +0x03cf<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 25: 0x000000000083b6bb a92_mode_analyzer +0x009b<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 26: 0x000000000083c74b ak93one_command +0x049b<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 27: 0x000000000083f2cd a93_user_commands +0x056d<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 28: 0x0000000000dfc754 Z7SQLTaskR20takall_command_globRhb +0x0074<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 29: 0x0000000000dfc933 Z11KernelMainR13RTETask_ITask +0x01b3<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 30: 0x0000000000e8a6b8 RTETask_TaskMain +0x0038<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 31: 0x0000000000f3bc27 Z23en88CallKernelTaskMainP9TASK_TYPE<br> +0x00c7<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE 32: 0x0000000000f3bfb9 en88_RunPthreadTask +0x0039<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE /sapdb/P01/db/pgm/kernel<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE Frameinfo [0x0]<br>

2009-09-28 10:26:58 9876 ERR 11599 BTRACE -

---

> End of Stack Back Trace <----<br>

2009-09-28 10:27:00 9665 11561 COMMUNIC Connecting T217 dbp0104 19501<br>

2009-09-28 10:27:03 9876 11987 dump_rte rtedump written to file 'rtedump'<br>

2009-09-28 10:27:04 9876 ERR 7 Messages Begin of dump of registered messages<br>

2009-09-28 10:27:04 9876 ERR 2 Admin A fatal error caused EMERGENCY SHUTDOWN. core is written<br>

2009-09-28 10:27:04 9876 ERR 2 Admin A fatal error caused EMERGENCY SHUTDOWN. core is written<br>

2009-09-28 10:27:04 9876 ERR 8 Messages End of the message list registry dump<br>

2009-09-28 10:27:04 9876 12820 EXCEPT calling ak dump for T202<br>

2009-09-28 10:27:04 9876 ERR 51105 AK CACHE AK00001.dmp written: 0<br>

2009-09-28 10:27:04 9876 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 202<br>

2009-09-28 10:27:04 9876 12696 DBSTATE Change DbState to 'KILL'(29)<br>

2009-09-28 10:27:04 9876 12697 DBSTATE Resuming tracewriter<br>

2009-09-28 10:27:04 9876 12825 TASKING state 29 before shutkill(1)<br>

2009-09-28 10:27:04 9876 WNG 11824 COMMUNIC Releasing T202 database shutdown<br>

2009-09-28 10:27:04 9876 WNG 11824 COMMUNIC Releasing T203 database shutdown<br>

2009-09-28 10:27:04 9876 WNG 11824 COMMUNIC Releasing T204 database shutdown<br>

2009-09-28 10:27:04 9876 WNG 11824 COMMUNIC Releasing T206 database shutdown<br>

<br>

Edited by: Pavol Simko on Sep 28, 2009 11:09 PM

Edited by: Pavol Simko on Sep 28, 2009 11:10 PM

[lbreddemann · Accepted solution]

BINGO!

Comparing the (slightly reformatted) stack back trace with the one from the error description (check the webpts if you want to do it yourself), clearly shows that you hit the mentioned bug.

---

> Symbolic Stack Back Trace <---- 0: eo670_UnixTraceStack +0x01ad 1: eo670_CTraceContextStackOCB +0x0009 2: eo670_CTraceStackOCB +0x0032 3: eo670_CTraceStack +0x0017 4: vabort +0x0027 5: Z9RTECrashRK20SAPDBErr_MessageList +0x008d 6: ZN21KernelAdministration7OfflineERK20SAPDBErr_MessageListbb +0x02cb 7: gg999Abort +0x0243 8: g01abort +0x013f 9: b13free_node +0x0073 10: ZN23cbd403OverFlowInvQueueD1Ev +0x0075 11: ZN17cbd403InvListSet17bd403_RemoveListsEi +0x0057 12: Z28bd403MergePrimKeysInInvListsR17cbd300InvCurrentS0_PhiS1_iS1_iS1_iRi +0x0a6f 13: b03MergeInvLists +0x051f 14: k73_index_range +0x0671 15: k720_select +0x06b4 16: k720_single_select +0x0019 17: k05functions +0x09e6 18: a06lsend_mess_buf +0x0297 19: a06dml_send_mess_buf +0x003a 20: a505most_execute +0x0af2 21: a505loop_most_execute +0x0360 22: a501exec_with_change_rec +0x05d6 23: a501execute +0x0518 24: ak92analyze_messagetype +0x03cf 25: a92_mode_analyzer +0x009b 26: ak93one_command +0x049b 27: a93_user_commands +0x056d 28: Z7SQLTaskR20takall_command_globRhb +0x0074 29: Z11KernelMainR13RTETask_ITask +0x01b3 30: RTETask_TaskMain +0x0038 31: Z23en88CallKernelTaskMainP9TASK_TYPE+0x00c7 32: en88_RunPthreadTask +0x0039 -

---

> End of Stack Back Trace <----

Therefore: no corruption in your data area!

regards,

Lars

[Former Member]

Lars,

thank you very much for your time and help!

Pavol

[Former Member]

Thank you again,

we are running on 7.6.6.3. Hope we are safe.

Are there any known reasons why this corruption could occur ?

Pavol

[lbreddemann]

Hi Pavel,

before you take the downtime, please check whether there is a symbolic call stack in with the crash message in the knldiag file.

I remembered that there was a bug (PTS 1195292, fixed in 7.6.06. Build 7) that occurs with merged index lists.

This means: there is no permanent corruption in your database and you can fix the issue by applying the current patch.

As a workaround you could also set OPTIM_MAX_MERGE parameter to 0.

But to be sure on this, I need to see the call stack...

regards,

Lars

p.s.

concerning the check data - yes you are safe with your version.

For more information check notes

852168 Content Server: Caution with VERIFY/CHECK DATA

1366652 MaxDB Version 7.7: Do not cancel CHECK DATA in ADMIN mode

[Former Member]

Thank you Lars,

could there be relation between this emergency shutdown and my action shortly before shutdown when I added new data volume ?

Is there a much difference in execution time of check data in online state and admin with update ? (I need to plan the downtime)

Stupid question. but : Could I be sure that I will do not loose any data afters this check with update in admin mode ? (First, in the ADMIN operational state, the database system carries out the same checks as in the ONLINE operational state.

If no errors occur during this data check, the database system cleans up the converter using the results of the checks: it deletes all pages that it did not read during the checks, to which there are no longer any references to the converter

)

Pavol

[lbreddemann]

> could there be relation between this emergency shutdown and my action shortly before shutdown when I added new data volume ?

Unlikely, very unlikely.

> Is there a much difference in execution time of check data in online state and admin with update ? (I need to plan the downtime)

Nope, execution times should be similar.

> Stupid question. but : Could I be sure that I will do not loose any data afters this check with update in admin mode ?

Usually: yes, you can be sure about that.

Unfortunately there had been bugs that would e.g. lead to data loss if you cancel the check data.

What version are you runing on?

> If no errors occur during this data check, the database system cleans up the converter using the results of the checks: it deletes all pages that it did not read during the checks, to which there are no longer any references to the converter

So what? If the pages are not referenced via the converter anymore, there is no way whatsoever to touch this data again. The data is already gone before you start Check Data!

regards,

Lars

[Former Member]

Hello Lars,

thank you dor the answer. We are running check data online every weekend when there is almost no activity in the system scheduled via DB13.

Should also log from CHECK DATA, executed online, show us the corruptions right ?

I understand it will not repair anything (clear converter...) in online state.

Thank you.

Pavol

[lbreddemann]

Correct.

Anyhow, since the error occured during a free page operation, it might be that the page is now not linked to any B*TREE anymore but not yet correctly re-entered to the freespace management.

Therefore a CHECK DATA in ADMIN mode is adviseable here.

regards,

Lars

[lbreddemann]

> 2009-09-28 10:26:57 9876 ERR 53000 B*TREE Free page failed; 1020

>

> Any idea ?

Sure - could be a database corruption.

Run a CHECK DATA WITH UPDATE in ADMIN mode and check for error messages.

regards,

Lars