What is error 6028?Although the "
Transaction inconsistency" entry in the 6028 error string may first appear to refer to a transaction in the database Before Image file (.bi), it is referring to the client's
local before image file (.lbi) where the A/R block acts as a placeholder for a sub transaction. For further clarification on the two, refer to Article:
What is the A/R block in error 6028?An A/R unit is an ACCEPT/REJECT unit. It is the mechanism by which the AVM keeps track of a client's transactions in the lbi (local before image) file. While these units are similar to database before image notes in their purpose; they are logged in a very different manner:
- There is no 1 to 1 relationship between an A/R unit and the transaction.
- Each sub transaction is logged in its own A/R unit
- There is no dependency on Begin or End notes in the local before image file.
Known causes of error 6028The potential causes of this error can be pretty straight forward. Understanding that the AVM is using A/R units as place holders in the lbi file and error 6028 reports the transaction inconsistency when one of these A/R units is not where it is expected to be when reading from the lbi file or writing to it. The lbi, like the other client temp files, default to the local working directory of the client when not otherwise defining these to be created elsewhere using the -T client startup parameter.
- The client-temp directory (-T) location (local directory by default if not using -T):
- Check available space in this directory - the client could be running low on space in the directory that they are writing their client-temp files to at the time which needs to be freed up or hitting a user quota / ulimit -a in the local directory.
- Review read/write permissions for that user session on the client-temp directory (-T) or network write /read permission on a shared drive when application code needs to copy or read a file from a remote location.
- Non-Progress software touching the lbi client-temp file at the time it is being read. Typically, this is due to not adding the working directory or directory defined in the -T client startup parameter to AntiVirus Software exclusions. Refer to the example analyzed in Article Certain clients terminate with error 6028
- Assure a scan disk doesn't show any problems - there could for example be a problem with a spot on disk where the lbi file resides, which can also manifest with memory corruption symptoms.
