Kbase P12309: 6109 error when truncating the bi. OS copy of bi file fails
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/21/2003 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
FACT(s) (Environment):
Progress 8.x
SYMPTOM(s):
Database crashed.
Truncate of BI file fails.
Unable to read extent header, ret = <return-value> file = <file-name>. (6109)
OS copy if bi file to another file system failed with an Operating System error.
Force into database failed.
The file system where the bi file resides is corrupted.
File system where bi files are stored are inaccessibly.
FIX:
At this point it is strongly suggested that a backup of the database be restored. We can not guarantee that your database will be usable. As a last resort and if a backup can not be restored the following can be attempted. **Make backup of existing database files.***
1. Prostrct create a test database with the same amount and settings of the bi files as defined in the database structure file.
example: prostrct create dbname dbname.st
2. Rename and OS copy the newly created bi files into a working file system that does not have problems.
3. Modify the structure file of the database to point to the newly defined bi files.
4. Run prostrct repair against the database.
example: prostrct repair dbname
5. Run prostrct unlock against the database. The should result in output stating that bi inconsistences have been found and fixed.
example: prostrct unlock dbname
6. Force into the database using the truncate -F command.
example: proutil dbname -C truncate BI -F
7. Dump and reload database.