Kbase 4851: bug 90-01-18-06 Index refers to bad recid
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/15/2000 |
|
bug 90-01-18-06 Index refers to bad recid
900122-dah01bug 90-01-18-06 Index refers to bad recid
This bug exists in the current release of v5, i.e. 5.2G, and all
version of v5 prior to 5.2G. This bug does not exist in v4.
How to create bug:
This bug only occurs when doing deletes or changing key values in
MULTI-USER given the following conditions:
a) The index must be a UNIQUE key
b) The user must delete or change ALL the keys within 1 index
block. This is highly probable if the user deletes any
contiguous series of records.
Splitting the delete up over several transactions or over
several days won't help.
How to avoid the bug:
Do the deletes or changes described above in SINGLE-USER.
** For example, if a user creates sales-orders with sequential key
values, and (in multi-user) deletes old sales-orders as they are
completed, THEN, THE USER WILL EVENTUALLY RUN INTO THIS BUG.
The bug is only visible in SINGLE-USER:
Namely, if you delete records of a file in multi-user and then try
to access them in single-user you will encounter the error:
System Error: Index refers to bad recid. Entry Ignored
This seems strange but true... the damage occurs in multiuser but is
only visible in single-user....
If, in single-user, you encounter the bug, you can run
proutil dbname -C idxbuild against the offending file and index to
fix the database until the next time you rerun the described deletes
or changes in multiuser.
How to AVOID the bug:
1. Only run the deletion program(s) in single-user.
2. If that is a problem, only run your subsequent accesses to these
files in multi-user.
The bug will be fixed in v5.2H and later revs of PROGRESS. If your
production situation is such that the "How to AVOID" is not possible,
please contact PROGRESS Software Technical Support.
Progress Software Technical Support Note # 4851