Configuring Periodic Deadlock Checking for the Berkeley Databases

You can configure the Calendar Server to periodically check for deadlocks in the Berkeley databases.

It is possible for the Berkeley databases to get into a deadlocked state, thus preventing access to them. To detect this state as early as possible, enable periodic checking for deadlocks.

To Enable Periodic Checking of Berkeley Databases for Deadlocks

1. Log in as an administrator with permission to change the configuration.

2. Change to the /etc/opt/SUNWics5/cal/config directory.

3. Save your old ics.conf file by copying and renaming it.

4. Edit the parameter shown in the following table:

   Parameter	Description/Default
   local.caldb.deadlock.autodetect	Periodically checks if the Berkeley database is in a deadlock state and, if so, instructs the database to reset. The default value is “no” (not enabled).

5. Save the file as ics.conf.

6. Restart Calendar Server.

   cal_svr_base/SUNWics5/cal/sbin/start-cal

Troubleshooting

For information about how to reset Berkeley databases once deadlocked, see Detecting Database CorruptionList of Available Tools in the Troubleshooting chapter.