Oninit cdi / Archive
Talk to an expert →

Given a page number how to allocated which table

Posted in 2007

Topics: Backup & Restore, Storage & Space Management, Error Codes & Troubleshooting, Jobs, Consulting & Announcements

PATRICK LEY — — source: IIUG Forums & Mailing Lists

Greeting all, Recently when my customer trying to run a backup (using onbar) it hit by page corruption issues. The content of the af file Archive detects that page 0x47f804d0 is corrupt. c000000255ddb400: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb410: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb420: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb430: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb440: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb450: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb460: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb470: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb480: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb490: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4a0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4b0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4c0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4d0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4e0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4f0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb500: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb510: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb520: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb530: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb540: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb550: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb560: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb570: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb580: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb590: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5a0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5b0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5c0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5d0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5e0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5f0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb600: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb610: 00000000 00000000 00000000 00000000 ........ ........ 21:16:07 21:16:07 IBM Informix Dynamic Server Version 9.30.FC6X9 Software Serial Number ACP#J267193 21:16:07 Assert Failed: Archive detects that page 0x47f804d0 is corrupt. 21:16:07 Who: Session(125100, informix@metrica2, 3334, 687102488) Thread(223801, arcbackup1, c00000028ca14458, 20) File: rsarcbu.c Line: 2611 21:16:07 Stack for thread: 223801 arcbackup1 base: 0xc00000025c31f000 len: 135168 pc: 0x0000000000000000 tos: 0xc00000025c320580 state: running vp: 20 ( 0) 0x40000000008f3734 legacy_hp_afstack + 0x24c [/apps/informix/ids.93/bin/oninit] ( 1) 0x40000000008f2d28 afstack + 0x78 [/apps/informix/ids.93/bin/oninit] ( 2) 0x40000000008f2440 afhandler + 0xc90 [/apps/informix/ids.93/bin/oninit] ( 3) 0x40000000008f173c afwarn_interface + 0x4c [/apps/informix/ids.93/bin/oninit] ( 4) 0x40000000007e58b8 arc_pages + 0x330 [/apps/informix/ids.93/bin/oninit] ( 5) 0x40000000007e54d8 arc_dbspace + 0x70 [/apps/informix/ids.93/bin/oninit] ( 6) 0x40000000007e463c arc_scanner + 0x46c [/apps/informix/ids.93/bin/oninit] ( 7) 0x400000000043b038 startup + 0xb8 [/apps/informix/ids.93/bin/oninit] ( 8) 0x400000000032379c resume + 0x10c [/apps/informix/ids.93/bin/oninit] base: 0xc00000025c31f000 len: 135168 pc: 0x0000000000000000 tos: 0xc00000025c320580 state: running Question : 1. Based on the page number above, how do we know this page is belongs to which table? Input is much appreciated. Thanks.

↪ replying to PATRICK LEY
ART KAGEL, — — source: IIUG Forums & Mailing Lists

Compare the page number to the extents in sysmaster:sysextents (or to an oncheck -pe report by hand). Depending on the version: Version < 9.40: Convert the page number to decimal and: select dbsname, tabname from sysextents where -pagenumber- between start and (start + size); Version >= 9.40 select dbsname, tabname from sysextents where chunk = physchunk( -pagenumber- ) and physpage( -pagenumber- ) between offset and (offset + size); Art S. Kagel ----- Original Message ----- From: Patrick Ley <ids@iiug.org> To: ids@iiug.org At: 10/10 5:55:44 Greeting all, Recently when my customer trying to run a backup (using onbar) it hit by page corruption issues. The content of the af file Archive detects that page 0x47f804d0 is corrupt. c000000255ddb400: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb410: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb420: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb430: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb440: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb450: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb460: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb470: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb480: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb490: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4a0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4b0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4c0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4d0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4e0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb4f0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb500: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb510: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb520: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb530: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb540: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb550: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb560: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb570: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb580: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb590: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5a0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5b0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5c0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5d0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5e0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb5f0: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb600: 00000000 00000000 00000000 00000000 ........ ........ c000000255ddb610: 00000000 00000000 00000000 00000000 ........ ........ 21:16:07 21:16:07 IBM Informix Dynamic Server Version 9.30.FC6X9 Software Serial Number ACP#J267193 21:16:07 Assert Failed: Archive detects that page 0x47f804d0 is corrupt. 21:16:07 Who: Session(125100, informix@metrica2, 3334, 687102488) Thread(223801, arcbackup1, c00000028ca14458, 20) File: rsarcbu.c Line: 2611 21:16:07 Stack for thread: 223801 arcbackup1 base: 0xc00000025c31f000 len: 135168 pc: 0x0000000000000000 tos: 0xc00000025c320580 state: running vp: 20 ( 0) 0x40000000008f3734 legacy_hp_afstack + 0x24c [/apps/informix/ids.93/bin/oninit] ( 1) 0x40000000008f2d28 afstack + 0x78 [/apps/informix/ids.93/bin/oninit] ( 2) 0x40000000008f2440 afhandler + 0xc90 [/apps/informix/ids.93/bin/oninit] ( 3) 0x40000000008f173c afwarn_interface + 0x4c [/apps/informix/ids.93/bin/oninit] ( 4) 0x40000000007e58b8 arc_pages + 0x330 [/apps/informix/ids.93/bin/oninit] ( 5) 0x40000000007e54d8 arc_dbspace + 0x70 [/apps/informix/ids.93/bin/oninit] ( 6) 0x40000000007e463c arc_scanner + 0x46c [/apps/informix/ids.93/bin/oninit] ( 7) 0x400000000043b038 startup + 0xb8 [/apps/informix/ids.93/bin/oninit] ( 8) 0x400000000032379c resume + 0x10c [/apps/informix/ids.93/bin/oninit] base: 0xc00000025c31f000 len: 135168 pc: 0x0000000000000000 tos: 0xc00000025c320580 state: running Question : 1. Based on the page number above, how do we know this page is belongs to which table? Input is much appreciated. Thanks. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Glossary