Derby properties

The Derby properties are used for configuring the system and database, as well as for diagnostics such as logging statements, and monitoring and tracing locks.

The table later in this topic lists all the core Derby properties.

Derby also supports a number of properties that are specific to the Network Server. For information about these properties, see "Setting Network Server properties" in the Derby Server and Administration Guide.

For information on how to set Derby properties, see "Setting Derby properties" in the Derby Developer's Guide.

To disable or turn off a database-wide property setting, set its value to null. To determine the result of this action, recall that the search order for properties is as follows (as stated in "Precedence of properties" in the Derby Developer's Guide).

1. System-wide properties set programmatically (as a command-line option to the JVM when starting the application or within application code); not consulted if derby.database.propertiesOnly is set to true
2. Database-wide properties
3. System-wide properties set in the derby.properties file; not consulted if derby.database.propertiesOnly is set to true

Setting the database-wide property to null has the effect of removing the property from the list of database properties and restoring the system property setting from derby.properties if there is one. As always, if no value can be determined from the search, the built-in default applies.

For example, the following code fragment turns off a previous database-wide setting of the derby.database.fullAccessUsers property:

Statement s = conn.createStatement();
s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +
    "'derby.database.fullAccessUsers', null)");

If the property is a static one, the null setting does not take effect until you reboot the database. Moreover, the static property derby.database.sqlAuthorization cannot be disabled after it has been enabled, even with a reboot.

The following table summarizes the general Derby properties. In the Scope column of this table, S stands for system-wide, D stands for database-wide, and C indicates the value persists with newly created conglomerates.

There are additional properties associated with the Derby tools. For more information about tool-specific properties, see the Derby Tools and Utilities Guide.

• derby.authentication.builtin.algorithm
  
• derby.authentication.ldap.searchAuthDN
  
• derby.authentication.ldap.searchAuthPW
  
• derby.authentication.ldap.searchBase
  
• derby.authentication.ldap.searchFilter
  
• derby.authentication.provider
  
• derby.authentication.server
  
• derby.connection.requireAuthentication
  
• derby.database.classpath
  
• derby.database.defaultConnectionMode
  
• derby.database.forceDatabaseLock
  
• derby.database.fullAccessUsers
  
• derby.database.noAutoBoot
  
• derby.database.propertiesOnly
  
• derby.database.readOnlyAccessUsers
  
• derby.database.sqlAuthorization
  
• derby.infolog.append
  
• derby.jdbc.xaTransactionTimeout
  
• derby.language.logQueryPlan
  
• derby.language.logStatementText
  
• derby.locks.deadlockTimeout
  
• derby.locks.deadlockTrace
  
• derby.locks.escalationThreshold
  
• derby.locks.monitor
  
• derby.locks.waitTimeout
  
• derby.replication.logBufferSize
  
• derby.replication.maxLogShippingInterval
  
• derby.replication.minLogShippingInterval
  
• derby.replication.verbose
  
• derby.storage.initialPages
  
• derby.storage.minimumRecordSize
  
• derby.storage.pageCacheSize
  
• derby.storage.pageReservedSpace
  
• derby.storage.pageSize
  
• derby.storage.rowLocking
  
• derby.storage.tempDirectory
  
• derby.stream.error.extendedDiagSeverityLevel
  
• derby.stream.error.field
  
• derby.stream.error.file
  
• derby.stream.error.logBootTrace
  
• derby.stream.error.logSeverityLevel
  
• derby.stream.error.method
  
• derby.system.bootAll
  
• derby.system.durability
  
• derby.system.home
  
• derby.user.UserName