Java DB

Apache Derby

Derby Server and Administration Guide

Derby Getting Started
Derby Reference Manual
Derby Developer's Guide
Derby Performance Tuning
Derby Server and Admin Guide
Derby Tools and Utilities
Derby Server and Admin Guide
-Part one: Derby Server Guide
-Derby in a multi-user environment
-Using the Network Server with preexisting Derby applications
-The Network Server and JVMs
-Installing required jar files and adding them to the classpath
-Starting the Network Server
-Shutting down the Network Server
-Obtaining system information
-Accessing the Network Server by using the network client driver
-Accessing the Network Server by using a DataSource object
-XA and the Network Server
-Using the Derby tools with the Network Server
-Differences between running Derby in embedded mode and using the Network Server
-Setting port numbers
-Managing the Derby Network Server
-Managing the Derby Network Server remotely by using the servlet interface
-Derby Network Server advanced topics
-Derby Network Server sample programs
-Part two: Derby Administration Guide
-Checking database consistency
-Backing up and restoring databases
-Replicating databases
-Logging on a separate device
-Obtaining locking information
-Reclaiming unused space

 

When the log is in a non-default location

Note: Read Logging on a separate device to find out about the default location of the database log.

If you put the database log in a non-default location prior to backing up the database, be aware of the following requirements:

  • If you are using an operating system command to back up the database, you must explicitly copy the log file as well, as shown in the following example:
    xcopy d:\mydatabases\sample c:\mybackups\2005-06-01\sample /s /i
    xcopy h:\janet\tourslog\log c:\mybackups\2005-06-01\sample\log /s /i

If you are not using Windows, substitute the appropriate operating system command for copying a directory and all of its contents to a new location.

  • Edit the logDevice entry in service.properties of the database backup so that it points to the correct location for the log. In the previous example, the log was moved to the default location for a log, so you can remove the logDevice entry entirely, or leave the logDevice entry as is and wait until the database is restored to edit the entry.

See Logging on a separate device for information about putting the log in a non-default location.

 

javadb@jdbcurl.com