Sun Java System Calendar Server 6.3 Administration Guide

D.14 csrename

The csrename utility allows you to rename one or more calendar users. This utility renames calendar users as follows:

The csrename utility is located in the following directory:


D.14.1 Requirements

Before you run csrename, you must first:

To run csrename, you must log in as icsuser (or as the Calendar Server runtime user ID specified during configuration). If you run csrename as superuser (root), you might need to reset the permissions for the new database files. To modify the LDAP directory server attributes, you must also have administrative rights for that directory.

If your Calendar Server installation has a front-end/back-end server configuration, you must run csrename on each back-end server.

D.14.2 Syntax

Use the following syntax to run csrename:

csrename [-t DestinationDB] 
         [-c ConfigFile]
         [-e ErrorFile] 
          -m MappingFile 
         rename [DB|LDAP]

table lists the options for this utility and gives a description of each.

Table D–25 Options for csrename



-t DestinationDB

Specifies the destination directory where csrename generates the new database with the converted user names. The default is MigratedDB. After csrename is finished, the caldb.berkeleydb.homedir.path parameter in the ics.conf file must point to the destination database. Either reset caldb.berkeleydb.homedir.path to point to the destination database directory, or move the destination database files to the directory indicated by the parameter.

-c ConfigFile

An input parameter that specifies a Calendar Server configuration file. The default is the ics.conf file. The csrename utility uses the caldb.berkeleydb.homedir.path parameter in the configuration file to determine the location of the input calendar database. The default location of the calendar database is /var/opt/SUNWics5/csdb.

-e ErrorFile

The file where csrename writes any errors or database entries that cannot be resolved. The default is MigrateError.

-m MappingFile

Specifies an input mapping file. The default is MigrateMapping. The input mapping file is a text file that maps existing user ID's to new user ID's. You must create the mapping file before you run csrename. Specify one entry per line with a space between the old and new values.

For example: 

tchang tc897675

jsmith js963123

bkamdar bk548769

If upon auditing your results, you find that one or more of your intended name changes was omitted, you can fix the error by creating a new mapping file with only the missed names in it and rerunning csrename.


Specifies the database that gets updated: 

DB converts user ID's in the new calendar database only (default).

LDAP converts user ID's in both the new calendar database and the LDAP directory server attributes.

D.14.3 Examples