Deleting the Derby transaction log to silence errors will corrupt the database
Never delete or manipulate *ANY* files in a Derby database directory structure. Doing so will corrupt the database.
The bottom line: Never delete or manipulate *ANY* files in a Derby database directory structure. Doing so will corrupt the database.
The problem: Some Derby users have discovered that deleting the files in the log subdirectory of the database will silence recovery errors and allow access the database. Removing the logfiles, even on a database that is not reporting problems, will corrupt the database. The data integrity and possibly the internal structure of the database will be irreparably damaged. Such corruptions are silent and could go unnoticed for long periods of time.
Please help: If you find any documents that recommend removing files from the Derby database folders please report them to the Derby Community (see below) or correct these reference.
Critical Best Practice: Make regular backups of your databases. Restoring the database from backup is the only way to recover a corrupt system.
Report problems or ask questions: Obtain assistance, post information or ask questions regarding Cloudscape or Derby via the Apache Derby maillists.
More support for:
Software version: 5, 10
Operating system(s): AIX, IBM i, Linux, Solaris, Windows, iOS, z/OS
Software edition: All Editions
Reference #: 1261294
Modified date: 21 July 2010