Creating and preparing the database for read-only use

To create databases for use on read-only media:

  1. Create and populate the database on read-write media.
  2. Commit all transactions and shut down Derby in the prescribed manner (see Shutting down Derby or an individual database). If you do not shut down Derby in the prescribed manner, Derby will need to perform recovery the next time the system boots. Derby cannot perform recovery on read-only media.
  3. Delete the tmp directory if one was created within your database directory. If you include this directory, Derby will attempt to delete it and will return errors when attempting to boot a database on read-only media.
  4. For the read-only database, set the property to a writable location. Derby needs to write to temporary files for large sorts required by such SQL statements as ORDER BY, UNION, DISTINCT, and GROUP BY. For more information about this property, see Tuning Derby.
  5. Configure the database to send error messages to a writable file or to an output stream. For information, see Tuning Derby.
Be sure to set these properties so that they are deployed with the database. For more information, see Embedded systems and properties.
Related concepts
Accessing a read-only database in a zip/jar file
Databases on read-only media and DatabaseMetaData
Related tasks
Deploying the database on the read-only media
Transferring read-only databases to archive (jar or zip) files
Accessing databases within a jar file using the classpath