[DERBY-1479] Release note for DERBY-541 on 10.1.3.1 release page

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0, 10.1.2.1, 10.1.3.1
• Fix Version/s: 10.1.3.1
• Component/s: Documentation
• Issue & fix info: Release Note Needed
• Assignee: Samuel Andrew McIntyre
• Reporter: Samuel Andrew McIntyre
• Created: 06/Jul/06 13:13
• Updated: 31/Jul/06 21:38
• Resolved: 31/Jul/06 21:38

Description

The documentation currently does not address the need to upgrade databases in jars when connecting to a newer version of Derby.

For example, attempting to connect to a database in a jar created with Derby 10.0 fails when trying to connect with Derby 10.1. The following error is thrown:

ERROR XJ040: Failed to start database 'jar:(pathtojarfile)pathinjar', see the next exception for details.
ERROR 40XD1: Container was opened in read-only mode.

Issue Links

• is duplicated by: DERBY-541 Read-only databases fail to boot after soft upgrade. Raises error message: 40XD1: Container was opened in read-only mode.