F
Calendar Server Utilities

This appendix contains full instructions on the usage and syntax of all utilities shipped with your calendar server. Note that the installation script does not install UNIX-only utilities on Windows NT platforms. All utilities are installed in the $ORACLE_HOME/ocal/bin directory.

The following table lists all utilities in alphabetical order.

Table F-1 Calendar server utilities

Script	Function
UNIACCESSRIGHTS	Manage access rights between users.
UNIADDNODE	Create a new calendar server node or re-initialize an existing one
UNIADMRIGHTS	Manage the administration rights of users.
UNIARCH (UNIX ONLY)	Create a tar archive of the calendar server.
UNIB2LENDIAN	Convert a calendar server node database from a format for big-endian processors to a format for little-endian processors.
UNICHECK (UNIX ONLY)	Verify the calendar server file system.
UNICKSUM	Generate a checksum for a file.
UNICLEAN (UNIX ONLY)	Clean up the calendar server file system (remove transient files and set permissions).
UNICPINR	Copy resource data from a file created by unicpoutr to a calendar server node.
UNICPINU	Copy the contents of a file of user data created by unicpoutu to a calendar server node.
UNICPOUTR	Copy resource data from a calendar server node into a file.
UNICPOUTU	Copy user data from a calendar server node to a file.
UNICPR	Format of the file created by unicpoutr and read by unicpinr.
UNICPU	Format of the file created by unicpoutu and read by unicpinu.
UNIDBBACKUP	Create an archive of the calendar server.
UNIDBCONV	Convert a version 2.50 or 2.60 node database to a 2.61 node database.
UNIDBFIX	Check, repair, defragment and maintain a calendar server node database.
UNIDBRESTORE	Restore the contents of a calendar server from a backup created by unidbbackup.
UNIDB2LDIF	Convert a calendar server node database from a format for little-endian Windows NT processors to a format for little-endian UNIX processors and vice-versa.
UNIDSACISETUP	Set the access control information in the directory server for the calendar server ADMIN group. (External directories only, not available for Oracle Internet Directory)
UNIDSDIFF	Find and delete differences between a calendar server node and a directory server. (external directory only)
UNIDSSEARCH	List all users in a directory server who are not calendar server users (external directory only).
UNIDSSYNC	Synchronize the information in a calendar server node with that in a directory server (external directory only).
UNIDSUP	Report the status of the directory server (external directory only).
UNIENCRYPT	Encrypt a password for inclusion in a calendar server configuration file
UNIGROUP	Create, modify and delete administrative and public groups
UNIICAL	Import iCAL VEVENTs into an agenda.
UNIL2BENDIAN	Convert a calendar server node database from a format for little-endian processors to a format for big-endian processors.
UNILOGONS	Display calendar server SIGNON/SIGNOFF statistics.
UNIMMIMPSRV	To import data from MeetingMaker servers to Oracle Calendar Server.
UNIMVUSER	Move a user from one calendar server node to another.
UNINODE	Administer a calendar server node network.
UNIOIDCONF	Utility used by the installation process to configure Calendar Server with Oracle internet Directory.
UNIPASSWD	Change a user password on a calendar server database. Internal directory servers only.
UNIPING	Ping a calendar server node or nodes.
UNIREQDUMP	View, and optionally delete, requests in the queue of the Corporate-Wide Services (CWS) daemon.
UNIRESTORE	Restore a user's calendar data from a backup
UNIRMOLD	Remove old events and tasks from agendas in a calendar server database.
UNIRNDEL	Delete a remote node from a local calendar server node database.
UNIRNSYNCH	Propagate deletions in the local information of one node to another node in the network.
UNISIZEOF	Compute the size of the calendar server installation.
UNISLICE (UNIX ONLY)	Extract information from calendar server log files.
UNISNAPSHOT	Compile calendar server information for diagnostic purposes.
UNISNCDUMP	Retrieve statistics from the calendar server's Synchronous Network Connection daemon/service.
UNISTART	Start up a node, the calendar server or some components only.
UNISTAT	Produce a report on a calendar server node.
UNISTATS	Display summary statistics of the data in a calendar server statistics (stats.log) file.
UNISTATUS	Determine the status of the calendar server.
UNISTOP	Shut down a node, the calendar server or some components only.
UNISTRCONV	Convert a string to UTF-8
UNISYNCREFRESH	Refresh synchronization records.
UNITZINFO	Print information about a calendar server time zone.
UNIUSER	List, add, or delete calendar users, resources or event calendars; modify the information associated with them.
UNIVERSION	Verify the version of the calendar server and its components.
UNIWHO	Display information on signed-on calendar users.

UNIACCESSRIGHTS

uniaccessrights - Grant access rights to agendas of users, resources or event calendars.

SYNTAX

uniaccessrights -ls -grantee <user> -grantor <user> 
[-n <node-ID>] [-host <hostname>] [[-p <psw>] [-uid <uid>] | [-krb]]
[-designate] [-eventview] [-taskview] [-scheduling]

uniaccessrights -mod -grantee <user>  -grantor <user>  
[-n <node-ID>] [-host <hostname>] [[-p <psw>] [-uid <uid>] | [-krb]]
[-designate <modifier>] [-taskview <modifier>] [-eventview <modifier>]  
[-scheduling <modifier>]

uniaccessrights -reset -grantee <user>  -grantor <user>  
[-n <node-ID>] [-host <hostname>] [[-p <psw>] [-uid <uid>] | [-krb]]
[-designate] | [-taskview] | [-eventview] | [-scheduling]]

uniaccessrights -info [-n <node-ID>] [-host <hostname>] 
[[-p <psw>] [-uid <uid>] | [-krb]]
[[-designate] | [-taskview] | [-eventview] | [-scheduling]]

uniaccessrights -v 
uniaccessrights -h 

DESCRIPTION

This utility allows the administrator to grant a user access rights to another user's, resource's or event calendar's calendar data, as well as to modify or revoke these rights. It can also be used to set access rights to users in bulk.

The access rights that can be granted from one user, resource or event calendar (grantor) to another (grantee) are:

• designate access to the grantor's calendar data (-designate)
• viewing grantor's calendar events (-eventview)
• viewing grantor's tasks (-taskview)
• the right to invite the grantor to meetings (-scheduling)

Note that the -ls option is mutually exclusive with the -mod option, and with the -reset option.

The calendar server must be up to run uniaccessrights.

OPTIONS

-designate

<modifier>

Change the designate rights. A designate is a user who has been assigned the right to modify the agenda of another user or resource. Use this flag to give or remove designate access to the grantor's calendar data. See FORMAT OF THE <modifier> ARGUMENT for details on the <modifier> argument.

-eventview

<modifier>

Change the calendar event viewing rights. Use this flag to set viewing rights to the grantor's agenda entries. See FORMAT OF THE <modifier> ARGUMENT for details on the <modifier> argument.

-grantor

<user>

Specify the user who is granting the rights for access to his calendar. The grantor can also be a resource or event calendar. If more than one match for the user is found in the database, uniaccessrights fails. An action (-mod/-reset/-ls) must be specified along with this option. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.

-grantee

<user>

Specify the user or users to whom the access rights are granted. If more than one match for the user is found in the database, you will be prompted to choose from three options: (Q)uit, (P)rompt or (A)pply to all. Enter Q if you do not want to grant access to all matching users. Enter P is you wish to be prompted for each matching user. Enter A and the specified access rights will be granted to all matching users. An action (-mod/-reset/-ls) must be specified along with this option. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.

-host

<hostname>

Specify the host. Required if the host is remote. To specify a port number use the following format for the <hostname> parameter: "hostname:port".

-info

Print the keys and values that can be used as valid arguments for specifying the <modifier> strings. The values listed in the <modifier> following tables will be displayed.

-krb

Use automatic Kerberos login. This option cannot be used with the -p and -uid options.

-ls

List the rights that the grantor has currently granted to the grantee for the specified access type. Use one or more of the options -designate, -eventview, -taskview or -scheduling to specify which rights to display. If none are specified, all rights are displayed. A grantee must be specified. The default rights that the grantor has granted will be displayed with the heading "Grantee: Everyone".

-mod

Change the access rights to be granted by a user to another user. Used with the -grantor and -grantee options. Use the options -designate, -eventview, -taskview or -scheduling to specify which rights to modify.

-n

<node-ID>

Specify the node. Required if more than one node exists on the host.

-p

<psw>

Provide the administrator's password; required if one is set. If this option is not used and a password is required, uniaccessrights prompts the user for it.

-reset

Reset an access right to the grantor's default. Used with the -grantor and -grantee options. Use the -ls option to display a user's default rights.

-scheduling

<modifier>

Change the scheduling rights. Use this flag to grant a user (grantee) the right to invite another user (grantor). See FORMAT OF THE <modifier> ARGUMENT for details on the <modifier> argument.

-taskview

<modifier>

Change the task viewing rights. Use this flag to set viewing rights to the grantor's tasks. See FORMAT OF THE <modifier> ARGUMENT for details on the <modifier> argument.

-uid

<user-ID>

The administrator's user ID. If none is specified the SysOp is used.

-v

Print the current version number of uniaccessrights.

-h

Print a usage message explaining how to run uniaccessrights.

FORMATS

FORMAT OF THE <user> ARGUMENT

This argument can represent a user, a resource or an event calendar. The <user> argument is a string of the form "key=value/key=value/...", where "key" is one of those listed in the following table, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".

If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they may need to be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.

Some example specifications are: "S=Kilpi/G=Eeva", "S=B*/G=Nicole/O=Acme", "O=Acme/ID=1111/OU1=authors"

Table F-2 Accepted keys

Key	X.400 Field
S	Surname
G	Given name
I	Initials
ID	Identifier
UID	User unique identifier
R	Resource name
N	Resource number
X	Generation
N	Event calendar name
OU1	Organizational Unit 1
OU2	Organizational Unit 2
OU3	Organizational Unit 3
OU4	Organizational Unit 4
O	Organization
C	Country
A	Administration domain
P	Private domain

FORMAT OF THE <modifier> ARGUMENT

The <modifier> argument is a string of the form "key=value/key=value/...", where "key" is one of those listed in the following table, and "value" is any of the possible values listed in the following table for each key. Both "key" and "value" are case insensitive.

For the -designate option, use "NONE" if you wish to give no access to the type of calendar entries specified by the key. Use "REPLY" to give the right to reply to invitations for this type of calendar entries. Use "MODIFY" to give the right to modify any details of the specified calendar entries that the grantor owns (created). Use "VIEWTIMES" to give the designate user the right to see the start and end times of a given type of event. Use the key and value "ALL=true" to give the grantee designate rights to all calendar data. Use the key and value "ALL=false" to remove all designate rights. Granting designate rights to a user must include the right to modify at least one type of event.

For the -eventview and -taskview options, use "NONE" if you don't wish the grantee to view any calendar entries of the type specified by the key. Use "TIMES" to give the right to see the times of the events. Use "ALL" to give the right to see any details of the specified calendar entries that are in the grantor's agenda. Public entries in a user's agenda are always viewable by other users.

The only right that can be set for the -scheduling option is the right to invite a user. Use "CANBOOKME=true" to give the right to the grantee to invite the grantor.

Table F-3 Accepted keys and values for -designate option

Key	Possible values
ALL	[true, false]
PUBLICEVENT	[NONE, REPLY, VIEWTIMES, MODIFY]
CONFIDENTIALEVENT	[NONE, REPLY, VIEWTIMES, MODIFY]
PERSONALEVENT	[NONE, REPLY, VIEWTIMES, MODIFY]
NORMALEVENT	[NONE, REPLY, VIEWTIMES, MODIFY]
PUBLICTASK	[NONE, MODIFY]
CONFIDENTIALTASK	[NONE, MODIFY]
PERSONALTASK	[NONE, MODIFY]
NORMALTASK	[NONE, MODIFY]

Table F-4 Accepted keys and values for -eventview option

Key	Values
ALL	[true, false]
CONFIDENTIAL	[NONE, TIMES, ALL]
PERSONAL	[NONE, TIMES, ALL]
NORMAL	[NONE, TIMES, ALL]

Table F-5 Accepted keys and values for -taskview option

Key	Values
ALL	[true, false]
CONFIDENTIAL	[NONE, ALL]
PERSONAL	[NONE, ALL]
NORMAL	[NONE, ALL]

Table F-6 Accepted keys and values for -scheduling options

Key	Values
CANBOOKME	[true, false]

EXAMPLES

• List the access rights that Don Martin has granted.:

  % uniaccessrights -ls -host gravel -grantor "S=Martin/G=Don" -p sysOpPsw
  
  

• Grant to Mr. O'Brian the right to view personal events in Don Martin's agenda and the right to view his tasks:

  % uniaccessrights -mod -grantee "S=OBrian" -grantor "S=Martin/G=Don" -host 
  gravel -p sysop1 -eventview "PERSONAL=ALL" -taskview "all=true"
  

• Grant to Mr. O'Brian the following designate access rights to Don Martin's agenda: the right to reply to invitations to confidential events that Don received and the right to modify public events that Don created:

  % uniaccessrights -mod -grantee "S=OBrian" -grantor "S=Martin/G=Don" -host 
  gravel -p sysop1 -designate 
  "CONFIDENTIALEVENT=REPLY/PUBLICEVENT=MODIFY/PERSONALEVENT=VIEWTIMES" 
  
  

• Grant to multiple users (who have an OU1 value of "IS") full designate rights access to Don's calendar data:

  % uniaccessrights -mod -grantee "OU1=IS" -grantor "S=Martin/G=Don" -host 
  gravel -p sysop1 -designate "ALL=true"
  

  If more than one user match the grantee specified, you will be prompted with a choice of actions:

  uniaccessright: Found 4 users that match the grantee filter. 
       uniaccessright: (Q)uit/(P)rompt/(A)pply to all [q,p,a] : a 
  
  

• Set scheduling rights such that students will not be allowed to invite Professor Smith:

  % uniaccessrights -mod -grantor "S=Smith/G=John/JOB-TITLE=Professor" 
  -grantee "OU2=student" -host gravel -p sysop1 -scheduling "canbookme=false" 
  
  

• Give user John Smith the designate right to modify public events in the event calendar "Montreal Jazz Festival":

  % uniaccessrights -mod -grantee "S=Smith/G=John" -grantor "N=Montreal Jazz 
  Festival" -host gravel -p sysopPsw -n 24 -designate "PUBLICEVENT=MODIFY"
  
  

• List all designate access rights user John Smith has granted:

  % uniaccessrights -ls -grantor "S=Smith/G=John" -grantee "S=*" -host gravel 
  -p sysopPsw -n 24 -designate
  
  

• List all task viewing access rights user John Smith has granted to Mr. Kusuma:

  % uniaccessrights -ls -grantor "S=Smith/G=John" -grantee "S=Kusuma" -host 
  gravel -p sysopPsw -n 24 -taskview "ALL=true"
  

EXIT STATUS

Exit values are:

0 Success

1 Failure

2 Usage error

UNIADDNODE

uniaddnode - Create a new calendar server node or re-initialize an existing one.

SYNTAX

Internal Directory (no external directory)

uniaddnode -n <node-ID> [-t <timezone>] [-a <nodealias>] [-p <sysOpPsw] 
[-r] [-y]
uniaddnode -sn <startNode-ID> [-num <numberOfNodes>] [-p <sysOpPsw] [-y]
uniaddnode -v 
uniaddnode -h 

External Directory Server

uniaddnode -n <node-ID> -w <DmPsw> [-p <SysOpPsw>] [-t <timezone>] [-a 
<nodealias>] [-r] [-y]
uniaddnode -sn <startNode-ID> [-num <numberOfNodes>] -w <DmPsw> [-p <SysOpPsw>] 
[-y]
uniaddnode -v 
uniaddnode -h 

DESCRIPTION

This utility creates and initializes a new calendar server node.

It can also be used to re-initialize an existing node. Before re-initializing a node, the user accounts must be deleted from the node's calendar database. This will ensure a proper clean-up of the user accounts information in any connected nodes and in the LDAP directory if one exists.

The usage varies slightly when no external LDAP directory is used.

uniaddnode runs only when the calendar server is down.

OPTIONS

-a

<nodealias>

Specify an alias for the node. <nodealias> is a descriptive word which cannot contain spaces.

-n

<node-ID>

Specify the node-ID. The node-ID must be unique across all nodes in the network. The -n option is optional when connected to the Oracle Internet Directory where if no node-ID is specified, a random node-ID will be generated.

-p

<SysOpPsw>

Provide a Sysop password for the node.

With the Oracle Internet Directory, all nodes share the same password. If the password is not provided on the command line, prompting for it occurs.

When not connected to an Oracle Internet Directory, if no password is specified, the password is set as empty.

-r

Re-initialize the node.

Note that in the case of a directory server, all users and resources must first be removed from the node before it can be re-initialized.

-t

<timezone>

Specify a time zone for the node. The default is the time zone set during installation of the calendar server. Time zones can be obtained from the unitzinfo utility, the $ORACLE_HOME/ocal/misc/timezone.ini file, or the calendar server Reference Manual, Appendix G, "Time Zone Table".

-w

<DmPsw>

Provide the directory server manager password for unrestricted access (i.e. the password associated with the value of the [LDAP] mgrdn parameter in the unison.ini file). If the password is not specified on the command line, prompting for it occurs. This parameter is only required for installations using an external LDAP directory server other than the Oracle Internet Directory.

-sn

<startNode-ID>

Specify the node-ID of the first node to be initialized. The node-ID must be unique across all nodes in the network. Use -num to specify how many node-IDs to be initialized. The node-IDs will be generated automatically starting with the specified start node-ID.

-num

<numberOfNodes>

Used with the -sn option to specify the number of node-IDs to be generated for the node initialization.

-y

Used with the -r option to auto-confirm the re-initialization.

-v

Print the current version number of uniaddnode.

-h

Print a usage message explaining how to run uniaddnode.

EXAMPLES

• Create a node with node ID "44", an alias of "admin", and the time zone of New York City for a calendar server using a directory server:

  % uniaddnode -n 44 -a admin -t EST5EDT -w DmPsw -p sysOpPsw
  unidsndini: working, please wait ...
  Creation of reserved users successful.
  Creation of Administrators group successful.
  uniaddnode: unidsndini done
  uniaddnode: unidbi done
  
  

  The following entry now appears in the [<YOURNODEID>] section of the $ORACLE_HOME/ocal/misc/unison.ini file.

  [44]
  name = <internally-assigned value>
  version = A.02.62
  aliases = admin
  timezone = EST5EDT
  

FILES

$ORACLE_HOME/ocal/misc/unison.ini 

This is the calendar server configuration file. For each new node, a node entry is created in this file by the uniaddnode utility.

EXIT STATUS

Exit values are:

0 Success

Any non-zero value signals an error.

UNIADMRIGHTS

uniadmrights - Manage the administration rights of users.

SYNTAX

uniadmrights -info [-n <node-ID>] [-host <hostname>] 
[[-p <psw>] [-uid <uid>] | [-krb]]

uniadmrights -ls -u <user> [-n <node-ID>] [-host <hostname>] 
[[-p <psw>] [-uid <uid>] | [-krb]]
uniadmrights -scope <scope> -u <user> [-n <node-ID>] [-host <hostname>] 
[[-p <psw>] [-uid <uid>] | [-krb]]

uniadmrights -u <user> [-n <node-ID>] [-host <hostname>] 
[[-p <psw>] [-uid <uid>] | [-krb]]
[-user <rightsFilter>] [-resource <rightsFilter>] [-eventcal <rightsFilter>] 
[-admgrp <rightsFilter>] [-pubgrp <rightsFilter>]  [-node <rightsFilter>] 
[-server <rightsFilter>] [-csm <rightsFilter>]


uniadmrights -v 
uniadmrights -h 

DESCRIPTION

This utility allows the SYSOP to grant certain administration rights to users as well as to revoke these rights. It can also be used to determine the rights held by each user.

The existing rights are granted on a per-node basis and apply to various groups of administration rights:

• user administration
• resource administration
• event calendar administration
• administrative groups management
• public groups management
• node administration
• server administration
• CSM (Calendar Server Manager daemon) administration

By default, uniadmrights option -ls lists all rights that have been granted by the SYSOP to a user. Note that the -ls option is mutually exclusive with the other options.

The calendar server must be up to run uniadmrights.

OPTIONS

-admgrp

<rightsFilter>

Specify the administrative groups management rights. Use this option to give rights to manage administrative groups. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-csm

<rightsFilter>

Give or revoke access to the CSM (Calendar Server Manager). Use this option to give the right to start and stop a calendar server or to disable a node. Cannot be used with -ls.

These rights however will still require that the administrator user know the CSM uid and password. See uninode, unistart, unistop. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-eventcal

<rightsFilter>

Specify the event calendar administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-host

<hostname>

Specify the host. Required if the host is remote. To specify a port number use the following format for the hostname parameter: "hostname:port".

-krb

Use automatic Kerberos login. This option cannot be used with the -p and -uid options.

-ls

List all rights granted to the specified user.

-n

<node-ID>

Specify the node. Required if more than one node exists on the host.

-node

<rightsFilter>

Specify the node level administration rights. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-p

<psw>

Provide the administrator's password; required if one is set. If this option is not used and a password is required, uniadmrights prompts the user for it.

-pubgrp

<rightsFilter>

Specify the public groups management rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-resource

<rightsFilter>

Specify the resource administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-scope

<scope>

Specify the scope of the administration rights. There are two possible values for <scope>: node or network. Use node if the rights are to be limited to the specified node. Use network if the administrative rights can be applied to any node of the network (all nodes connected to the specified node). The scope will apply to all groups of rights granted to this user.

-server

<rightsFilter>

Specify the server administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-u

<user>

Specify the user whose administrative rights will be modified or simply listed (-ls). If more than one match for the user is found in the database, uniadmrights fails. The specified right(s) will be granted to the user. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.

-uid

<user-ID>

The administrator's user ID. If none is specified the SysOp is used.

-user

<rightsFilter>

Specify the user administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.

-v

Print the current version number of uniadmrights.

-h

Print a usage message explaining how to run uniadmrights.

FORMATS

FORMAT OF THE <user> ARGUMENT

The <user> argument is a string of the form "key=value/key=value/...", where "key" is one of those listed in the following table, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".

If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they may need to be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.

Some example specifications are: "S=Kilpi/G=Eeva", "S=B*/G=Nicole/O=Acme", "O=Acme/ID=1111/OU1=authors"

Table F-7 Accepted keys

Key	X.400 Field
S	Surname
G	Given name
I	Initials
ID	Identifier
UID	User unique identifier
X	Generation
OU1	Organizational Unit 1
OU2	Organizational Unit 2
OU3	Organizational Unit 3
OU4	Organizational Unit 4
O	Organization
C	Country
A	Administration domain
P	Private domain

FORMAT OF THE <rightsFilter> ARGUMENT

The <rightsFilter> argument is a string of the form "key=value/key=value/...", where "key" is one of those listed in the following table, and "value" is any of the possible values listed in the following table for each key. Both "key" and "value" are case insensitive.

Use the key and value "ALL=true" to give all the administrative rights of the specified group of administration rights to the specified user. Use the key and value "ALL=false" to remove all the rights.

Table F-8 Accepted keys and values for -user option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Create	[true, false]	Create user accounts
Modify	[true, false]	Modify user account information
Delete	[true, false]	Delete user accounts
Enable	[true, false]	Enable or disable user accounts
Setrights	[true, false]	Grant administration rights to a user
Setdesignate	[true, false]	Set designate rights for users
Setviewing	[true, false]	Grant viewing rights to a user's calendar data
Setattribute	[true, false]	Change user attributes
Password	[true, false]	Change user passwords
Transferevent	[true, false]	Transfer event ownership from one user to another

Table F-9 Accepted keys and values for -resource option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Create	[true, false]	Create resource accounts
Modify	[true, false]	Modify resource account information
Delete	[true, false]	Delete resource accounts
Enable	[true, false]	Enable or disable resource accounts
Setdesignate	[true, false]	Set designate rights for resources
Setviewing	[true, false]	Grant viewing rights of a resource's calendar data
Setattribute	[true, false]	Change resource attributes
Password	[true, false]	Change resource passwords
Transferevent	[true, false]	Transfer event ownership from one resource to another

Table F-10 Accepted keys and values for -eventcal option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Create	[true, false]	Create event calendar accounts
Modify	[true, false]	Modify event calendar account information
Delete	[true, false]	Delete event calendar accounts
Enable	[true, false]	Enable or disable event calendar accounts
Setdesignate	[true, false]	Set designate rights for event calendars
Setviewing	[true, false]	Grant viewing rights of an event calendar's calendar data
Setattribute	[true, false]	Change event calendar attributes
Password	[true, false]	Change event calendar passwords
Manageevent	[true, false]	Manage event calendar's entries

Table F-11 Accepted keys and values for -admgrp option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Create	[true, false]	Create administrative groups
Modify	[true, false]	Modify administrative groups
Delete	[true, false]	Delete administrative groups
Attach	[true, false]	Add a user to an administrative group
Detach	[true, false]	Remove a user from an administrative group

Table F-12 Accepted keys and values for -pubgrp option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Create	[true, false]	Create public groups
Modify	[true, false]	Modify public groups
Delete	[true, false]	Delete public groups
Attach	[true, false]	Add a user to a public group
Detach	[true, false]	Remove a user from a group

Table F-13 Accepted keys and values for -node option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Edit-item-ini	[true, false]	Using the Calendar Administrator WEB interface, Edit the user.ini, resource.ini or eventcal.ini files
Restore	[true, false]	Restore a user
Holiday	[true, false]	Manage holidays
Modify	[true, false]	Change the node information in the unison.ini (alias, time zone, etc.) using the Calendar Administrator WEB interface

Table F-14 Accepted keys and values for -server option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Edit-unison-ini	[true, false]	Update the unison.ini file

Table F-15 Accepted keys and values for -csm option

Key	Possible values	Description
All	[true, false]	All rights listed in this table
Access	[true, false]	Access the CSM to start and stop servers and nodes.

EXAMPLES

• List all administration rights of user Alice Smith:

  % uniadmrights -ls -u "S=Smith/G=Alice" -host gravel -p psw -n 203
  
  

• Grant holiday administration rights to Don Martin in R&D, at node 80:

  % uniadmrights -u "S=Martin/G=Don/OU1=r&d" -node "holiday=true" -n 80 - krb
  
  

• Set the scope for Don Martin in R&D to all nodes of the same network as node 80:

  % uniadmrights -u "S=Martin/G=Don/OU1=r&d" -n 80 - krb -scope "network"
  
  

• Grant the right to create and delete administrative groups and the right to create user accounts to Don Martin in R&D, at node 80:

  % uniadmrights -u "S=Martin/G=Don/OU1=r&d" -user "create=true" -admgrp 
  "create=true/delete=true" -n 80 - krb
  
  

• Remove all user administration rights from Joan Bean on host montreal:

  % uniadmrights -u "S=Bean/G=Joan" -user "all=false" -host montreal -p psw
  

WARNINGS

Directory Server Warning

It is important to understand the implications of the directory server configuration for calendar server utilities.

In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.

EXIT STATUS

Exit values are:

0 Success

1 Failure

2 Usage error

UNIARCH (UNIX ONLY)

uniarch - Create a tar archive of the calendar server.

SYNTAX

uniarch [-d] [-y] [-t | -f <filename>] [-p <path>] [-u <user>] [-g <group>]

uniarch -v 
uniarch -h 

DESCRIPTION

uniarch creates a backup of the calendar server. By default, the entire $ORACLE_HOME/ocal directory is archived.

You must invoke uniarch from outside of the directory or directories it is backing up. For example, to back up the entire calendar server, you invoke uniarch from outside of the $ORACLE_HOME/ocal directory.

uniarch can only be run if the calendar server is down.

OPTIONS

-d

Back up only the contents of $ORACLE_HOME/ocal/db/nodes, the calendar server database.

-f

<filename>

Specify the name of the archive file. If this option is not used, prompting for the filename occurs.

-t

Force the tar default device to be used for the archive destination file.

-y

By default, uniarch asks for confirmation before proceeding with the creation of the archive. This option tells uniarch to automatically proceed, without prompting for confirmation. Default if there is no tty associated with the calling process.

-g

<group>

Specify the unix group.

-p

<path>

Specify the path to the server directory which contains the db directory (such as -p "$ORACLE_HOME/ocal").

-u

<user>

Specify the unix user.

-v

Print the current version number of uniarch.

-h

Print a usage message explaining how to run uniarch.

EXAMPLES

• Archive the entire $ORACLE_HOME/ocal directory:

  % uniarch
  uniarch: working, please wait ...
  uniarch: input tar archive destination file name: jan07-99.bkup
  uniarch: archive "$ORACLE_HOME/ocal" and redirect to "jan07-99.bkup"? (y/n)
  uniarch: archive completed
  
  

• Archive only the calendar server database, supplying the name of the destination archive file on the command line:

  % uniarch -d -f jan07-99-db.bkup
  uniarch: working, please wait ...
  uniarch: archive "$ORACLE_HOME/ocal/db/nodes" and redirect to 
  "jan07-99-db.bkup"? (y/n)
  
  uniarch: archive completed
  

EXIT STATUS

Exit values are:

0 Success

1 Failure

2 Usage error

3 User interrupt

UNIB2LENDIAN

unib2lendian - Convert a calendar server node database from a format for big-endian UNIX processors to a format for little-endian Windows NT processors. For more details on this utility, contact Oracle support.

SYNTAX

unib2lendian [-n <node-ID>]
unib2lendian -v 
unib2lendian -h 

DESCRIPTION

unib2lendian is used when migrating a node database from a calendar server running on a big-endian UNIX machine such as Solaris, HP-UX or AIX, to one running on a little-endian Windows NT machine.

This utility converts the *.dat files of the node database from big-endian to little-endian format. The conversion is executed on a copy of the files, leaving the original database untouched. The *.dat files are the only ones necessary to convert; the remaining files are built on the destination machine.

unil2bendian is the complementary utility for converting files from little-endian to big-endian format.

unib2lendian can only be run when the calendar server is down.

OPTIONS

-n

<node-ID>

Specify a node to convert. Required if more than one node exists on the local host.

-v

Print the current version number of unib2lendian

-h

Print a usage message explaining how to run unib2lendian.

EXAMPLES

MIGRATING A NODE FROM A BIG-ENDIAN TO A LITTLE-ENDIAN MACHINE

The following example converts node 45, and moves it from a calendar server running on a big-endian machine to a calendar server running on a little-endian system.

1. Stop the calendar server on both machines. Do not restart either server until instructed to later in this procedure.
2. Run unib2lendian on the target node.

   unib2lendian -n 45
   

   The converted copy of the node can be found in the $ORACLE_HOME/ocal/db/nodes/<N#>/perm_conv directory, where <N#> is the value of the name parameter in the unison.ini section corresponding to the target node.

3. Copy the section corresponding to the target node in the old host's $ORACLE_HOME/ocal/misc/unison.ini file to the unison.ini file on the new host. For example:

   [45]
   name = N1
   version = A.02.50
   

   Delete this section from the unison.ini file on the old host.

4. Copy all *.dat files in the perm_conv directory to the $ORACLE_HOME/ocal/db/nodes/<N#>/perm directory on the little-endian system.
5. On the new host, copy the $ORACLE_HOME/ocal/db/nodes/nempty/perm/unison.dbd and $ORACLE_HOME/ocal/db/nodes/nempty/perm/vista.ctb files into the $ORACLE_HOME/ocal/db/nodes/<N#>/perm directory.
6. Create a tmp directory for the new node, and copy the necessary files.

   % cd $ORACLE_HOME/ocal/db/nodes/<N#>
   % mkdir tmp
   % cd tmp
   % copy $ORACLE_HOME/ocal/db/nodes/nempty/tmp/set.dat
   % copy $ORACLE_HOME/ocal/db/nodes/nempty/tmp/set.key
   % copy $ORACLE_HOME/ocal/db/nodes/nempty/tmp/unitmp.dbd
   

7. If the target node is part of a node network, you MUST update the network information before restarting the calendar server.

   Warning: Failure to carry out this step may result in data loss and/or database corruption.

   First, stop all calendar servers in the node network.

   Use unidbfix to export the information in the remotenode.dat file to EACH and EVERY node's remotenode.ini file. For example, if the network were to consist of nodes 30, 35, 40, 45 and 50:

   % unidbfix -export -n 30
   % unidbfix -export -n 35
   % unidbfix -export -n 40
   % unidbfix -export -n 45
   % unidbfix -export -n 50
   

   Remember that unidbfix must be run on each node's local host.

   Edit the $ORACLE_HOME/ocal/db/nodes/<Nx>/perm/remotenode.ini file for each node in the network, and change the host name associated with node 45.

   If moving to a little-endian Unix host, run uniclean on node 45 to ensure that file ownership and permissions for the copied files are set correctly.

   Run unidbfix -k on node 45 to create key files.

   Use unidbfix -import to update the remotenode.dat file with the new information in the remotenode.ini files.

   % unidbfix -import -n 30
   % unidbfix -import -n 35
   % unidbfix -import -n 40
   % unidbfix -import -n 45
   % unidbfix -import -n 50
   

   This also rebuilds the key files for each node.

   Update the $ORACLE_HOME/ocal/misc/nodes.ini file to reflect the change in host names for node 45.

8. Restart all calendar servers.

EXIT STATUS

Exit values are:

0 Success

1 Failed to convert the database

2 Usage error

SEE ALSO

unidbfix, unistart, unistop, uninode

UNICHECK (UNIX ONLY)

unicheck - Verify the calendar server file system.

SYNTAX

unicheck [-nowarn] [-nodb | -maxdb <n>] [-c]

unicheck -v 
unicheck -h 

DESCRIPTION

unicheck verifies the calendar server file system. The utility first checks that the version of the calendar server is intended to run on the local operating system. If this is not the case, unicheck prompts the user to determine whether or not they wish to continue. If the version runs on the local operating system, unicheck then verifies:

1. that all necessary files and directories are present
2. that the permissions, and owner and group information are correctly set on the files and directories.

Any discrepancies are reported. Unless an entire file or directory is missing, any problems found are fixed running uniclean.

unicheck should be run periodically to ensure that the file system is in good order.

unicheck can be run whether the calendar server is up or down.

OPTIONS

-maxdb

<n>

Specifies the maximum number of node databases unicheck should consider. For example, if <n>=30, unicheck checks the files of only the first 30 nodes databases.

-nowarn

Do not print warning messages (error messages are still printed).

-nodb

Do not check database files.

-c

Computes a system-independent checksum for each static file. If this option is used, output should be redirected to a file for future use.

-v

Print the current version number of unicheck.

-h

Print a usage message explaining how to run unicheck.

EXAMPLES

• Run unicheck (for brevity, sections of the output have been replaced by [...]):

  % unicheck
  unicheck: checking all directories
  unicheck: checking directory "$ORACLE_HOME/ocal"
  unicheck: checking directory "$ORACLE_HOME/ocal/tmp"
  [...]
  unicheck: checking files in directory "$ORACLE_HOME/ocal/bin"
  unicheck: checking files in directory "$ORACLE_HOME/ocal/misc"
  [...]
  unicheck: checking versions of files in directory "$ORACLE_HOME/ocal/bin"
  unicheck: check completed
  
  

• Run unicheck, suppressing any warning messages and computing a checksum for each file (for brevity, sections of the output have been replaced by [...]):

  % unicheck -nowarn -c 
  unicheck: checking all directories
  unicheck: checking directory "$ORACLE_HOME/ocal"
  unicheck: checking directory "$ORACLE_HOME/ocal/tmp"
  [...]
  unicheck: checking files in directory "$ORACLE_HOME/ocal/bin"
  unicheck: checking files in directory "$ORACLE_HOME/ocal/misc"
  unicheck: checking files in directory "$ORACLE_HOME/ocal/man"
  [...]
  unicheck: checking versions of files in directory "$ORACLE_HOME/ocal/bin"
  unicheck: computing checksums
  unicksum: checksum of the file "$ORACLE_HOME/ocal/misc/timezone.ini" is 
  17289
  unicksum: checksum of the file "$ORACLE_HOME/ocal/bin/addme" is 33775
  [...]
  unicheck: check completed
  

EXIT STATUS

Exit values are:

0 Success

1 Failure

2 Usage error

3 User interrupt

UNICKSUM

unicksum - Generate a checksum for a file.

SYNTAX

unicksum <filename>

unicksum -v 
unicksum -h 

DESCRIPTION

unicksum generates a checksum for a file that is used to determine whether or not differences exist between two instances of the same file.

unicksum can be run when the calendar server is up or down.

OPTIONS

-v

Print the version number of unicksum.

-h

Print a usage message explaining how to run unicksum.

EXAMPLES

• Generate a checksum for the unitzinfo executable:

  % unicksum unitzinfo
  unicksum: checksum of the file "unitzinfo" is 18187
  

EXIT STATUS

Exit values are:

0 Success

1 Failure

2 Usage error

3 User interrupt

UNICLEAN (UNIX ONLY)

uniclean - Clean up the calendar server file system.

SYNTAX

uniclean 

uniclean -v 
uniclean -h 

DESCRIPTION

uniclean cleans up the calendar server file system by removing some transient files and ensuring file/directory and owner/group permissions are properly set.

uniclean can be run when the calendar server is up or down.

OPTIONS

-v

Print the current version number of uniclean.

-h

Print a usage message explaining how to run uniclean.

EXIT STATUS

Exit values are:

0 Success

1 Failure

2 Usage error

3 User interrupt

SEE ALSO

unicheck

UNICPINR

unicpinr - Copy resource data from a file created by unicpoutr to a calendar server node.

SYNTAX

unicpinr [-add] [-f <filename>] [-start <day> <month> <year>] [-end <day> 
<month> <year>] [-host <hostname>] -n <Node-ID> [-p <SysOpPsw>]

unicpinr [-add] [-start <day> <month> <year>] [-end <day> <month> <year>] [-host 
<hostname>] -n <Node-ID> [-p <SysOpPsw>] < [<filename>]

unicpinr -ls [<filename(s)>]

unicpinr -v 
unicpinr -h 

DESCRIPTION

Copies a file containing resource data (created with the unicpoutr utility) into a calendar server node. The utility can be used in conjunction with unicpoutr to move a resource from one node to another, or to add the agenda of one resource to that of another (see EXAMPLES).

By default, the resource specified in the file must already exist in the destination calendar server node. If this is not the case, the -add option is used to add it.

unicpinr can only be run if the calendar server is up.

It is important to understand how unicpinr handles the information in the file during the copy into the destination node.

• Resource identifier

  These are the values for the keys R, N, CA, S, G, ID, LOC, PHONE, FAX (see RESOURCE IDENTIFIER KEYS for details on these keys). Only non-null values are output to the file by unicpoutr so not all keys may have a value in the file.

  unicpinr uses these values to uniquely identify an existing resource in the destination node.

• Password and agenda-specific preferences

  Where the resource already exists in the destination node, these values are already set and unicpinr does NOT overwrite them with those in the input file.

• Agenda information

  Where a resource already exists in the destination node, unicpinr simply adds the agenda information in the input file to the existing agenda.

  All events listed in the file are copied into the destination node with the resource as the owner. Where appropriate, the description of each event contains extra data indicating the invitees to the event, their status, and the original creator and owner. Recurring or repeating instances of an event are disconnected from each other and copied in as individual events.

  The -start and -end options can be used to import only those events that fall within the specified time.

  Note: The unicpinr utility does not consult the resource.ini files when importing resources.

OPTIONS

-add

Add the resource to the database before copying in the file. It is an error to specify this option if the resource already exists in the node. In the case of a directory server, the resource is created under the baseDN.

-end

<day> <month> <year>

Set the end dates of the events to be processed. By default, all events in the file are created; this option and the -start option allow you to exclude certain events. Dates must be expressed in the form "day month year". Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.

-f

<filename>

Specify the input file name. The file must have been created with the unicpoutr utility. By default, standard input is used.

-host