Kbase 17828: SYSTEM ERROR:bfundo--(15)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
SYSTEM ERROR:bfundo--(15)
This error occcurs due to an internal problem with the lbi file, or
local before image file which is a temporary file created by and for
all clients to the database. This knowledgebase article will attempt
to explain what goes wrong internally as well as some potential
causes of the problem.
-THERE IS NO CONNECTION BETWEEN THE LBI AND THE BI FILES-
When we see the SYSTEM ERROR:bfundo--(15) we are in the process of
backing out an accept/reject (AR) unit, which is simply a sub
transaction. Each unit, or subtansaction is individually "undo-able",
and it is very important to distinguish between transactions in the
lbi file versus those of the database bi file.
The database.bi file keeps track of the whole transaction, which
may contain a series of sub transactions. We can use a customer and
all their respective orders in a database as an example. The bi file
sees the creation of the customer and all orders placed for that
customer as one transaction assuming we are entering the customer for
the first time. The lbi file on the other hand sees the creation of
the customer as well as the creation if each record as an individual
"undo-able" entity and it marks the start of one of these sub
transactions at each REPEAT/FOR-EACH/DO TRANS/....END block in the
4GL. The lbi file marks the start of a sub transaction with what's
called an accept/reject unit (AR unit).
When we see the error, we are in process of backing out AR units and
we have hit an unknown action to backout. This is somewhat similar to
an invalid note in the bi file and the potential causes of that apply
directly here. Either the lbi file itself is corrupted, or the disk it
resides on is having a problem of some sort. One cause COULD be that
the client is running low on space in the directory they are writing
the temp files to (local directory by default if not using the -T). If
this is the case then either move the files with the -T or free up
some space in the local directory. THIS IS NOT BI CORRUPTION.
NOTE: The lbi file is specific to the client session and is eliminated
when the client process ends, either normally or abnormally and is
NOT used at all during database crash recovery.
The most important distinction to be made is that the database.bi file
sees the main transaction as the start/end point of the transaction
while the lbi file sees each component of the transaction
(subtransactions) as seperate entities and distinguishes them by
keeping track of the accept/reject (AR) units.
These are just some distinctions to be made between two Progress files
that share similar names but very different architectures.
SDA 4/6/98
Progress Software Technical Support Note # 17828