Writes to Databases May Cause Corruption When the Filesystem is Full (Out of Available Disk Space)
Last updated on OCTOBER 09, 2017
Applies to:Berkeley DB - Version 3.0.55 and later
Information in this document applies to any platform.
- When the disk becomes full, and there is no more available disk space to complete write operations (transaction commits, checkpoints, trickles, database syncs etc), error 28 (ENOSPC) is returned, "No space left on device".
- Further writes in the log files or database files aren't possible. The databases may become corrupted unless the application is transaction protected.
The problem is not generated by any changes in the implementation of the Berkeley DB APIs.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms