RE: [U2] Corrupt file
The fix worked beautifully and quick too. Thank you very much for your assistance. I have added your procedure to our notes for future reference. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colin Alfke Sent: Thursday, April 24, 2008 9:36 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Corrupt file Wyatt; guide and verify2 simply find the corruption. dumpgroup/fixgroup and fixfile are used to correct the file. fixfile takes the output from guide and does it's own dumpgroup and fixgroup. I use dump/fixgroup mostly because I like to see what's happening. My steps: 1. get exclusive access to the file 2. create OS level copy of the file 3. use "RECORD" to get the other items in the group (RECORD OPEN.MO 082352500) within UniData 4. Dump the group (DUMPGROUP OPEN.MO 1327 -dopenmo1327) from the OS prompt 5. Fix the group (FIXGROUP OPEN.MO 1327 -iopenmo1327) also from the OS prompt (the options are lowercase and can not have a space after them) 6. verify the file is OK (GUIDE OPEN.MO -O) from the OS 7. verify that your data is all there using the list of items from step 3. Edit the records. You can create a VOC entry to your backup copy to compare if things don't look right. There is a section in the Administering UniData document on File Corruption that explains all of the above. There is also an "Advanced File Fixing for UniData" document. I'm not sure if I got it from the website or the support disc that they send out. hth Colin Alfke Calgary, Canada -Original Message- From: Buffington, Wyatt We are running UniData 6.0.4 on an HP.UX 11 and the following error keeps appearing: 2:blk check error in U_catch_tuple for file 'OPEN.MO', key '082352500', number=1327 I have run following command: :!guide OPEN.MO -o OPEN.MO Basic statistics: File type... Dynamic Hashing File size [dat001].. 8129536 [over001]. 43686912 File modulo. 7937 File minimum modulo. 7937 File split factor... 60 File merge factor... 40 File hash type.. 1 File block size. 1024 File Integrity: Group 1327, block 1328, record number 3 = "082352500" offset occurs in wrong order 35587084 Group 1327, block 34753, record number 3 = "082352500" offset error 35587084 Group 1327, block 34753, record number 2 = "076754900" record length of 414 is wrong. Group 1327, block 34753, record number 3 = "082352500" record length of 1035 is wrong. Group 1327, block 34753 bytes used 1449 and bytes left 989 are inconsistent Free blocks in overflow file(s). 7982 Management advice: This file's integrity has been compromised, please repair it. Files processed:1 Errors encountered: 5 We need to fix this problem, but the manuals are pretty vague on what steps are required. Do I use 'guide' and 'fixfile' or do I use 'verify2', 'dumpgroup' and 'fixgroup'? Can anyone help me with this? Wyatt Buffington --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Corrupt file
Wyatt; guide and verify2 simply find the corruption. dumpgroup/fixgroup and fixfile are used to correct the file. fixfile takes the output from guide and does it's own dumpgroup and fixgroup. I use dump/fixgroup mostly because I like to see what's happening. My steps: 1. get exclusive access to the file 2. create OS level copy of the file 3. use "RECORD" to get the other items in the group (RECORD OPEN.MO 082352500) within UniData 4. Dump the group (DUMPGROUP OPEN.MO 1327 -dopenmo1327) from the OS prompt 5. Fix the group (FIXGROUP OPEN.MO 1327 -iopenmo1327) also from the OS prompt (the options are lowercase and can not have a space after them) 6. verify the file is OK (GUIDE OPEN.MO -O) from the OS 7. verify that your data is all there using the list of items from step 3. Edit the records. You can create a VOC entry to your backup copy to compare if things don't look right. There is a section in the Administering UniData document on File Corruption that explains all of the above. There is also an "Advanced File Fixing for UniData" document. I'm not sure if I got it from the website or the support disc that they send out. hth Colin Alfke Calgary, Canada -Original Message- From: Buffington, Wyatt We are running UniData 6.0.4 on an HP.UX 11 and the following error keeps appearing: 2:blk check error in U_catch_tuple for file 'OPEN.MO', key '082352500', number=1327 I have run following command: :!guide OPEN.MO -o OPEN.MO Basic statistics: File type... Dynamic Hashing File size [dat001].. 8129536 [over001]. 43686912 File modulo. 7937 File minimum modulo. 7937 File split factor... 60 File merge factor... 40 File hash type.. 1 File block size. 1024 File Integrity: Group 1327, block 1328, record number 3 = "082352500" offset occurs in wrong order 35587084 Group 1327, block 34753, record number 3 = "082352500" offset error 35587084 Group 1327, block 34753, record number 2 = "076754900" record length of 414 is wrong. Group 1327, block 34753, record number 3 = "082352500" record length of 1035 is wrong. Group 1327, block 34753 bytes used 1449 and bytes left 989 are inconsistent Free blocks in overflow file(s). 7982 Management advice: This file's integrity has been compromised, please repair it. Files processed:1 Errors encountered: 5 We need to fix this problem, but the manuals are pretty vague on what steps are required. Do I use 'guide' and 'fixfile' or do I use 'verify2', 'dumpgroup' and 'fixgroup'? Can anyone help me with this? Wyatt Buffington --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Corrupt file
Wyatt, A simple memresize or RESIZE should clear these errors up. "Buffington, Wyatt" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 04/24/2008 09:54 AM Please respond to u2-users@listserver.u2ug.org To cc Subject [U2] Corrupt file We are running UniData 6.0.4 on an HP.UX 11 and the following error keeps appearing: 2:blk check error in U_catch_tuple for file 'OPEN.MO', key '082352500', number=1327 I have run following command: :!guide OPEN.MO -o OPEN.MO Basic statistics: File type... Dynamic Hashing File size [dat001].. 8129536 [over001]. 43686912 File modulo. 7937 File minimum modulo. 7937 File split factor... 60 File merge factor... 40 File hash type.. 1 File block size. 1024 File Integrity: Group 1327, block 1328, record number 3 = "082352500" offset occurs in wrong order 35587084 Group 1327, block 34753, record number 3 = "082352500" offset error 35587084 Group 1327, block 34753, record number 2 = "076754900" record length of 414 is wrong. Group 1327, block 34753, record number 3 = "082352500" record length of 1035 is wrong. Group 1327, block 34753 bytes used 1449 and bytes left 989 are inconsistent Free blocks in overflow file(s). 7982 Management advice: This file's integrity has been compromised, please repair it. Files processed:1 Errors encountered: 5 We need to fix this problem, but the manuals are pretty vague on what steps are required. Do I use 'guide' and 'fixfile' or do I use 'verify2', 'dumpgroup' and 'fixgroup'? Can anyone help me with this? Wyatt Buffington --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
