Subject | Re: [ib-support] corrupt data base |
---|---|
Author | Ann W. Harrison |
Post date | 2001-12-18T20:17:58Z |
At 07:34 PM 12/18/2001 +0000, William Hill wrote:
an ice storm. Run gbak with the -v switch and determine where
the error occurs. If the error is not in the metadata, you can
run gbak with the -m switch to create an empty database and
pump all the data except the broken table(s?) into the new
database. If the broken table(s?) have a primary key, you can
probe on the key to determine the key values of the broken
record(s?) - e.g. where pk < 'M' - if that gets the error then
where pk < 'G' - you remember, a binary search...
Or you can contact me directly - I have some tools that help
repair databases.
Regards,
Ann
www.ibphoenix.com
We have answers.
>I set the db to read only using gfix -mode read_onlyOK, that's the way these things go - like clearing trails after
>
>Then, using gbak -b I get the following error report:-
>
>gbak: ERROR: internal gds software consistency check (wrong record length
>(183))
an ice storm. Run gbak with the -v switch and determine where
the error occurs. If the error is not in the metadata, you can
run gbak with the -m switch to create an empty database and
pump all the data except the broken table(s?) into the new
database. If the broken table(s?) have a primary key, you can
probe on the key to determine the key values of the broken
record(s?) - e.g. where pk < 'M' - if that gets the error then
where pk < 'G' - you remember, a binary search...
Or you can contact me directly - I have some tools that help
repair databases.
Regards,
Ann
www.ibphoenix.com
We have answers.