Kbase P166383: Database crashed after reaching maximum size of a variable bi file, 2gb.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/07/2010 |
|
Status: Verified
SYMPTOM(s):
Database crashed after reaching maximum size of a variable bi file, 2gb.
(10601) SYSTEM ERROR: Attempted to exceed maximum size on file <path>.b2.
(854) ** Insufficient disk space to extend the before-image file.
(5028) SYSTEM ERROR: Releasing regular latch. latchId: 4
(2249) Begin ABNORMAL shutdown code 2
FACT(s) (Environment):
Large files is enabled on the Operating System
Ulimit is set to unlimited
Large files had been enabled for this database.
Performed a dump and load of large file enabled database
Database log file does not show that large files is enabled on startup of the database
UNIX
OpenEdge 10.x
CAUSE:
Database is dumped and loaded every six months. Since a dump and load creates a new database, large files will need to be enabled for the new database. They failed to re-enable large files on the newly created database post dump and load, thus the 2GB file limit was imposed on the bi file.
FIX:
Re-enable large files by running proutil dbname -C enablelargefiles and restart the database.