deleted key not found

[John Esak]

The DKNF bugs were fixed. I don't think there are any extant leftovers. If
you are getting this error, your problem is most likely within your
programming.  The cause is usually not protecting your lookups correctly
with the -p option. (Lookups that modify the recored  that is.)  

 

The DKNF errror is almost never directly related to the record number
reported. Rather, that is where the problem becomes bad enough to issue the
report and the actual bad record or records  in the index have come before
the notification. So, in some cases, previously corrupted indexes  getting
worse generate DKNF at some point.

 

I'm not sure what bugs related to DKNF (if any) were fixed since 5.0.9, but
you absolutely can not hope to have these problems go away without being on
the most current version of your release. For 5.0 that would be 5.0.14
before the new licensing and backward compatible bug fixes & features, and
5.0.15 after them.  The most current version of filePro is 5.6.6.  Sorry to
say, but trying to fix these errors without updating to one of these
versions would be essentially futile..

 

Ken Brody has released many emails and I think a definitive document
somewhere about the need to use the -p flag correctly in all cases. 

 

However, if you want to cause an immediate DKNF error which can also be
immediately fixed. Do this. Pick an indexed field. Go into Define Files and
change the length of this field. Do *NOT* go in to Define Indexes and
correct the index to the new length as you should. Instead, go into the file
and DELETE some record. You will most likely immediately get a DKNF error.
If you are lucky, this may have been what you've done recently. Obviously,
to correct the problem, set the index length to properly match the new size
of the field and re-index.

 

Otherwise, again, start looking for misuse or non-use of the -p throughout
related files.

 

Good luck,

John Esak

 

 

 

  _____  

From: filepro-list-bounces+john=valar.com at lists.celestial.com
[mailto:filepro-list-bounces+john=valar.com at lists.celestial.com] On Behalf
Of scooter6 at gmail.com
Sent: Saturday, October 20, 2007 12:42 AM
To: Filepro-List at Lists. Celestial. Com
Subject: deleted key not found

 

Running SCO Unix with filePro 5.0.09R4

 

During night time processes, I have been getting a lot of deleted key not
found errors..

I haven't seen these in a long time...

 

Deleted key not found

Index= letters/index.D

Key="         "

recno=2501

tptr= 8, 12, 1, 207, 0

 

I don't see any issue with recno 2501 in the letters file -- it is doing a
lookup based on acct #

to another file - and that acct number is there.....

 

I thought these issues were resolved in a previous bug/fix from an earlier
version?

What causes this?

thanks

 

Scott Ullmann

Newtown, PA

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20071020/d86ab856/attachment.html