PingDirectory

Changing the LDAP changelog database location

If you have disk space issues, you can change the on-disk location of the LDAP changelog database.

The changelog backend supports a db-directory property that specifies the absolute or relative path (relative to the local server root) to the file system directory that is used to hold the Oracle Berkeley DB Java Edition database files containing the data for this backend.

If you change the changelog database location, you must stop and restart the PingDirectory server for the change to take effect. If the changelog backend is already enabled, then the database files must be manually moved or copied to the new location while the server is stopped.

Changing the LDAP changelog location using dsconfig non-interactive mode

Steps

  1. Use dsconfig to change the database location for the LDAP changelog, which by default is at <server-root>/db.

    Example:

    The following command sets the LDAP changelog backend to <server-root>/db2.

    $ bin/dsconfig set-backend-prop --backend-name changelog \
  --set "db-directory:db2" --set "enabled:true"

    Remember to include the LDAP connection parameters, such as host name, port, bindDN, and bindPassword.

    The database files are stored under <server-root>/db2/changelog. The files for this backend are stored in a sub-directory named after the backend-id property.

  2. Stop and restart the server.

    Because the LDAP changelog backend was previous disabled, you do not need to manually relocate any existing database files.

    Example:

    $ bin/stop-server
$ bin/start-server

Resetting the LDAP changelog location using dsconfig non-interactive mode

Steps

  1. If you have changed the LDAP changelog location, to reset it to its original location, use dsconfig.

    Example:

    The following command resets the LDAP changelog backend to <server-root>/db location.

    $ bin/dsconfig set-backend-prop --backend-name changelog \
  --reset "db-directory"

    Remember to include the LDAP connection parameters such as host name, port, bindDN, and bindPassword.

  2. If the LDAP changelog backend at the previous location is enabled:

    1. Stop the server.

    2. Copy the database files to the new LDAP changelog location.

    3. Restart the server.

      The server attempts to use whatever it finds in the configured location when it starts. If there is nothing there, it creates an empty database.