22.5.4 Preventing Service Interruptions When Your Database is Corrupted (Read-only Mode)

This sections covers how to keep your corrupted database accessible while you are in recovery mode and includes the following topics:

• 22.5.4.1 Using Read-only Mode

• To Put a Database in Read-only Mode

22.5.4.1 Using Read-only Mode

If you are encountering database corruption, one way to prevent service interruptions is to put your database in read-only mode. This mode allows end users to read database entries, but does not allow additions, modifications, or deletions. If an end user attempts to add, modify or delete any calendar data, the system gives an error message. In addition, administrator tools that add, modify or delete calendar events and todos will not work while the database is in read-only mode.

If the database is corrupted to the point that it can’t be read, you must interrupt service long enough to restore a backup. The quickest way to restore a backup is to have a good hot backup. See 22.5.8.1 Before You Restore.

To Put a Database in Read-only Mode

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

2. Stop Calendar Server services by issuing the stop-cal command.

3. At a command line, change to the directory where the ics.conf is located:

   cd /etc/opt/SUNWics5/config

4. Specify read-only mode for the calendar, by setting the parameter as follows:

   caldb.berkeleydb.readonly=”yes”

5. Restart Calendar Server by issuing the start-cal command.

   cal-svr-base/SUNWics5/cal/sbin/start-cal

   You must restart the services in order for the ics.conf changes to take effect.