Page 1 of 1
TSQL Error : 005 Can't read 0x7012 bytes at 0xDFA in KDBF
Posted: Tue Sep 03, 2002 7:29 pm
by gazim
I am getting this following error message when I try run a sql statement using tsql. I am using Texis Version July 2002 on Sun Solaris. I will appreciate your help on this matter. Thanks in advance.
texisuser >>tsql "select DOCID from tbldoc"
Texis Version 04.00.1019027849(20020417) Copyright (c) 1988-2002 Thunderstone EPI
005 Can't read 0x7012 bytes at 0xDFA in KDBF file /database/enron/tbldoc/SYSINDEX.tbl: er
ror 0: Unknown (Read past EOF) in the function read_rest_data
000 Could not open SYSINDEX in the function ddopen
000 Couldn't connect to . in the function SQLConnect
TSQL Error : 005 Can't read 0x7012 bytes at 0xDFA in KDBF
Posted: Tue Sep 03, 2002 10:00 pm
by mark
Sounds like SYSINDEX is corrupt. The usual cause for something like that is disk I/O errors or disk full errors. Use kdbfchk to repair it.
TSQL Error : 005 Can't read 0x7012 bytes at 0xDFA in KDBF
Posted: Tue Sep 03, 2002 10:19 pm
by gazim
We have encountered the same error in the past. kdbfchk didn't seem to help. I just ran
$ mv SYSINDEX.tbl bad-SYSINDEX.tbl
$ kdbfchk -o bad-SYSINDEX.tbl SYSINDEX.tbl
Checking file SYSINDEX.tbl: Reading free tree and list
0% 50% 100%
-------------------------------------------------------------------------------
Scanning for orphaned free tree pages
0% 50% 100%
###############################################################################
Free tree and list appear intact
Repairing KDBF file
0% 50% 100%
###############################################################################
Bad block summary:
1 data block deleted
1 free block pad inserted
*** Corruption detected ***
myserver >>
This did not fix the problem.
for your reference:
http://thunderstone.master.com/texis/ma ... 3ca4b5a511
TSQL Error : 005 Can't read 0x7012 bytes at 0xDFA in KDBF
Posted: Wed Sep 04, 2002 10:08 am
by Kai
Short of disk space or hardware problems we haven't seen this with SYSINDEX. If you open a tech support ticket and arrange to send the corrupted SYS file to us we can take a closer look and see if we can find another cause.