Kbase P118050: What are the possible causes for BI corruption?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/02/2009 |
|
Status: Verified
GOAL:
What are the possible causes for BI corruption?
GOAL:
What is the list of likely causes for BI corruption?
GOAL:
What can cause a BI file to become corrupted?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
FIX:
Although the Before-Imaging feature of Progress databases is a mechanism intended to provide crash recovery, it is not itself fail safe. A number of causes can incur corruption in the BI area of a database. These causes include:
bad RAM causes the data to be corrupted in RAM and the incorrect data written to the BI extents on disk.
a bad hard disk causes the data to be corrupted during the read (it is not written reliably on the hard disk medium).
a system or hard disk operation was forcefully interrupted during a write operation, causing a BI block to be incompletely written. This is a common cause of BI corruption.
a system or hard disk operation was forcefully interrupted during a file system update, causing a file system corruption. Although this usually does not corrupt a database, it may happen that during the file system recovery at boot an overly conservative recovery mechanism modified data in the database files. Refer to the operating system vendor for more information about the possible consequences of file system corruption.
a missing .lk file or other administrative mistakes can allow to run multiple database servers on a single set of database files. This causes BI and data corruption in the database.