Removing Unused Space From the Database

After long and continued use, the principal database on the primary server can grow large due to unused space. When a principal is deleted, the space that the record occupied is not removed. Instead, the space is reserved and marked as "available". Therefore, with extended use, the database can grow very large. Correct the situation by loading all existing principals into a new database. You must perform this process after hours to limit the impact on users.

To create a new database and load existing records:

On the primary security server, stop the services and daemons:
- run this command as root a user,
  /sbin/init.d/krbsrv stop
Make an archive of the principal.* files found on the primary server.
Dump the database:
- run this command as a root user,
  /opt/krb5/admin/kdb_dump -f /tmp/filename
Delete the old database
- run this command,
  # rm /opt/krb5/principal*
Create a new database, using the same master password and encryption type as when the database was originally created
- run this command,
  # /opt/krb5/admin/kdb_create -s -e enctype
Load the dump file
- run this command,
  # /opt/krb5/admin/kdb_load -f /tmp/filename
Restart the services and daemons,
- run this command,
  /sbin/init.d/krbsrv start
Remove the /tmp/filename file after you have verified that the new database is functioning without problems.

Removing Unused Space From the Database

Technical documentation

» Table of Contents

» Glossary

» Index