[DERBY-6327] Give applications a way to request that Derby consistency-check crashed databases.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.11.1.1
• Component/s: SQL, Store
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 30/Aug/13 15:00
• Updated: 30/Aug/13 19:18

Description

It is common for operating systems to scan/repair the entire file system after a machine crash. Similarly, it may be possible/desirable for Derby to consistency-check conglomerates when a database is booted after coming down ungracefully. A couple issues are worth considering:

1) This could be an expensive operation on a large database.

2) Derby can't tell the difference between a machine crash and an application crash.

The behavior change would be noticeable for complex, crash-prone applications with large databases. That argues against making this the default behavior. Applications would need to opt into this extra consistency checking.

This enhancement request comes out of a discussion on DERBY-5221.

Issue Links

• relates to: DERBY-5221 Database cannot be started after shutdown due to ClassNotFoundException: ERROR XBM0U: No class was registered for identifier 33089