Kbase P26622: Is the database log file able to grow beyond 2GB?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/07/2009 |
|
Status: Verified
GOAL:
Will the database log file (.lg) be able to grow beyond 2GB?
GOAL:
How to manage the database lg file size ?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
The 2 gig limit on the .lg file should not a problem, provided that the OS allows filesizes above this value.
Progress does not open the .lg file with large file support enabled, as it does for other database files. So, regardless of whether largefilesupport is enabled on the database or not, the O/S (except Linux) will happily write to it past the 2 gig "limit".
The key here is that this file is opened for sequential writing. The O/S will not enforce the 2 gig limit in this case, so there should not be any problem (except on Linux) with the .lg growing this large.
However, the question is somewhat pedantic. A log file that grows this large is essentially unmanageable in terms of readablility. It really should be archived and truncated with the prolog utility as part of the backup strategy.