Kbase P22954: Database extents filled up all space on drives causing database shutdown with error 6091.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/04/2010 |
|
Status: Verified
SYMPTOM(s):
Database extents filled up all space on drives causing database shutdown with error 6091.
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset 2147467264, file <file-name>.db. (6091)
Verified all space used on volume where variable database extents are writing to.
CAUSE:
If database extent files fill up all available hard drive space the database broker is programmed to shutdown the database.
To correct this problem additional disk space must be provided for the database to continue to grow.
FIX:
If additional space exists in other locations on the system the variable extent files of the database may be moved with operating system tools and the Progress / OpenEdge utility prostrct may be used to update the database from a revised copy of the database .st file.
Example:
If the database was originally positioned in the following way:
/usr1/db/mydb.db
/usr1/db/mydb.d1
/usr1/db/mydb.d2
/usr1/db/mydb.b1
and the /usr1/db directory (mount point) ran out of space.
Use the operating system copy/move program to relocate the file(s) to a new location.
Then re-imprint the new file locations into the database .db file using the prostrct tool with the repair option.
Prostrct requires that an update be made to the .st file with the corrected file position information.
Simple Example of original mydb.st
b /usr1/db/mydb.b1
d /usr1/db/mydb.d1 f 1024000
d /usr1/db/mydb.d2
Simple Example of modified mydb.st:
Example of original mydb.st
b /usr1/db/mydb.b1
d /usr2/db/mydb.d1 f 1024000
d /usr3/db/mydb.d2
After the operating system tools have been used to move the database files, and updates have been made to the database .st file give the following command:
prostrct repair <dbname> <modified st file name>
Example:
prostrct repair /usr1/db/mydb /tmp/mydb.st
To verify the prostrct repair has been successful use the prostrct tool with the list option to verify.
Example:
prostrct list /usr1/db/mydb /tmp/verify.st
Review the verify.st file to confirm the appropriate file locations are now stored in the database .db file.
Prostrct repair will ignore new names of area(s).
If these need to be corrected, then a dump and load method or possibly a probkup/prorest will need to be employed to a new structure.