Sun Java System Calendar Server 6 2005Q4 Administration Guide

Using csdb to Manage Calendar Databases

To administer database files, use the Calendar Server utility csdb. This section contains topics:

How csdb Groups Database Files

The calendar database utility csdb treats the database files as three logical databases:

Calendar Database (caldb)

The caldb consists of all the .db files and the _db.*files found in the database directory. The following is the default location for the calendar database files (as well as the cld_cache and ldap_cache subdirectories):


If you prefer, you can specify a different directory when running the Calendar Server configuration program ( For information about the configuration program, refer to Chapter 3, Calendar Server Configuration Program (

The following table describes the calendar database (caldb) files:

Table 16–1 Calendar Server Database Files




Calendar properties for all calendars. Includes the calendar ID (calid), calendar name, Access Control List (ACL), and owner.


Events for all calendars. 


Todos (tasks) for all calendars. 


Alarms for all events and todos (tasks). 


Queue of scheduling requests for the group scheduling engine (GSE). 


Journals for calendars. Journals are not implemented in the current release. 


Database version identifier. 


Recurring events. 


Deleted events and todos (tasks). See also Chapter 18, Administering the Delete Log Database

Session Database (sessdb)

The session database consists of all files located in the following directories: /opt/SUNWics5/cal/lib/admin/session/ and /opt/SUNWics5/cal/lib/http/session/

Statistical Database (statdb)

The statistical database consists of all files found in the counter directory:


csdb Can Target Specific Databases

The csdb utility -t option allows you to specify a target database:

If you do not include the -t option, csdb operates on all three databases, except for check and rebuild which operate only on the calendar database.