Kbase 17915: SYSTEM ERROR (6028) and Its Possible Causes in the lbi File
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/11/1998 |
|
SYSTEM ERROR (6028) and Its Possible Causes in the lbi File
The following error shows itself every now and then, and there is not
currently very much documentation on it. It appears as follows:
SYSTEM ERROR: A/R block doesn't match caller's. Transaction
inconsistency. (6028)
Although the transaction entry in the error string may appear to be
a transaction in the database before image file, the problem really
exists within the client's local before image file.
An A/R unit is what is called an ACCEPT/REJECT unit, and it is the
mechanism by which we keep track of a client's transactions in the
db.lbi (local before image file). These units are similar to before
image notes in their purpose , however these units are
logged in a very different manner. Basically there is not a 1 to 1
relationship between a/r unit and transaction. Each subtransaction is
logged in its own a/r unit, and there is no dependency on begin or
end notes in the local before image file. There is more specific
information available on this concept in KB17828. This kbase deals
mostly with the SYSTEM ERROR: bfundo -- code (15), however it does
get into the internals of the lbi file pretty extensively.
The potential causes of this error are pretty straight forward. We
are using the a/r units as place holders in the lbi file, and we
report the transaction inconsistency when one of these units is not
where we expect it to be. If you see the error, there may be a problem
with the spot on disk (entire disk) where the lbi file resides. The
lbi, like the other client temp files, default to the local working
directory of the client, and space in this directory should be
checked as well if a scan disk doesn't show any problems.
This could also be due memory corruption at the time. If we are lost
in memory for whatever reason, then it is plausible that this kind of
error may be produced. If memory is reintialized, through a system
reboot for example, and the error persists then it is most likely a
physical problem where the lbi file is residing.
SDA 5/11/98