Kbase P117457: bkset: Extent <file-name> is below size <file-size> (9444) not resolved with forced truncate of bi f
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/21/2006 |
|
Status: Unverified
SYMPTOM(s):
Force truncate does not resolve bkset: Extent <file-name> is below size <file-size>. (9444)
Can not get into database
bkset: Extent <file-name> is below size <file-size>. (9444)
bkset: Extent <dbname>.b1 is below size 1024065536. (9444)
CAUSE:
Cause of bi-extent truncation is unknown at time of writing.
FIX:
The supported resolution is to go to backup. If no backup is available you can try the following steps. If you are able to recover the database note the the database is corrupt and you MUST dump and load its contents.
This only applies if the bi file is listed in the 9444 error message.
Before going further make an OS copy of the database.
1. Using the current <dbname>.st file create a new database. Note you will have to edit this file to change the extent paths if the database is built is a different directory that the current database and rename the file <newDatebaseName>.st.
2. Prostrct create <newDatabaseName> <newDatabaseName>.st
3. Copy the copy/rename the newly created bi file so you are replacing the problem file listed in the 9444 error message.
4. prostrct unlock <databasename>
5. Proutil <databasename> -C truncate bi -F
The database should now be able to start without getting the 9444 error message. You can now dump and load this database.